Kevin Hilman wrote:
Artem Bityutskiy <dedekind@xxxxxxxxxxxxx> writes:
Hi,
On Wed, 2009-04-15 at 09:22 -0600, Paul Walmsley wrote:
stil thinking about it. These messages have made it easy to catch bugs
with the PM code in the past (e.g., sad2d). Making them debug-level will
require booting a kernel with clock debugging specifically
compiled in. So I wonder if there might be a better way to deal with
these...
Yeah, I see your concern. I'm your user, and from my perspective this is
an excessive output to slow serial line.
If you do not want re-compilation, I may send a different patch
like this:
- printk(KERN_INFO "Disabling unused clock \"%s\"\n", clk->name);
+ printk(KERN_DEBUG "Disabling unused clock \"%s\"\n", clk->name);
in which case you would not loose the messages, but the messages
would not go to the serial line.
I prefer this method as well since i can see them simply by adding
debug to the cmdline.
Fine with me, thanks for looking at this.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
