From: Tony Lindgren <tony@atomide.com>
To: Artem Bityutskiy <dedekind@yandex.ru>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: lessen amount of noisy messages
Date: Wed, 15 Apr 2009 11:43:48 -0700 [thread overview]
Message-ID: <20090415184347.GJ2167@atomide.com> (raw)
In-Reply-To: <49E605FD.2020509@yandex.ru>
* Artem Bityutskiy <dedekind@yandex.ru> [090415 09:06]:
> Artem Bityutskiy wrote:
>> Disabling unused clock "gpt2_ick"
>> Disabling unused clock "gpt3_ick"
>> Disabling unused clock "gpt4_ick"
>> Disabling unused clock "gpt5_ick"
>> Disabling unused clock "gpt6_ick"
>> Disabling unused clock "gpt7_ick"
>> Disabling unused clock "gpt8_ick"
>> Disabling unused clock "gpt9_ick"
>> Disabling unused clock "gpio2_dbck"
>> Disabling unused clock "gpio3_dbck"
>> Disabling unused clock "gpio4_dbck"
>> Disabling unused clock "gpio5_dbck"
>> Disabling unused clock "gpio6_dbck"
>> Disabling unused clock "gpt9_fck"
>> Disabling unused clock "gpt8_fck"
>> Disabling unused clock "gpt7_fck"
>> Disabling unused clock "gpt6_fck"
>> Disabling unused clock "gpt5_fck"
>> Disabling unused clock "gpt4_fck"
>> Disabling unused clock "gpt3_fck"
>> Disabling unused clock "gpt2_fck"
>> Disabling unused clock "wdt2_ick"
>> Disabling unused clock "wdt2_fck"
>> Disabling unused clock "gpio1_dbck"
>> Disabling unused clock "rng_ick"
>> Disabling unused clock "ssi_ick"
>> Disabling unused clock "gpt10_ick"
>> Disabling unused clock "gpt11_ick"
>> Disabling unused clock "uart1_ick"
>> Disabling unused clock "uart2_ick"
>> Disabling unused clock "usbtll_ick"
>> Disabling unused clock "ssi_ssr_fck"
>> Disabling unused clock "uart1_fck"
>> Disabling unused clock "uart2_fck"
>> Disabling unused clock "usbtll_fck"
>> Disabling unused clock "ts_fck"
>> Disabling unused clock "cpefuse_fck"
>> Disabling unused clock "gpt11_fck"
>> Disabling unused clock "gpt10_fck"
>> Disabling unused clock "dpll5_ck"
>> Disabling unused clock "dpll4_m6x2_ck"
>> Disabling unused clock "dpll4_m5x2_ck"
>> Disabling unused clock "dpll3_m3x2_ck"
>> Disabling unused clock "sys_clkout1"
>>
>> The messages have KERN_INFO level and if you have serial
>> console, they normally go there. I do not think it is good
>> idea to print that much stuff there. Moreover, messages
>> are not properly prefixed and for mortals it is not
>> immeadietly clear where they come from.
>>
>> Let's give them debugging level instead.
>>
>> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
>> ---
>> arch/arm/mach-omap2/clock.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c
>> index 4247a15..c4169ee 100644
>> --- a/arch/arm/mach-omap2/clock.c
>> +++ b/arch/arm/mach-omap2/clock.c
>> @@ -1035,7 +1035,7 @@ void omap2_clk_disable_unused(struct clk *clk)
>> if ((regval32 & (1 << clk->enable_bit)) == v)
>> return;
>> - printk(KERN_INFO "Disabling unused clock \"%s\"\n", clk->name);
>> + printk(KERN_DEBUG "Disabling unused clock \"%s\"\n", clk->name);
>> if (cpu_is_omap34xx()) {
>> omap2_clk_enable(clk);
>> omap2_clk_disable(clk);
>
> Few notes. I'm just trying to clean up our system, because
> it prints too much to serial line. The clocks prints are
> not very bad, but I still find them a little bit excessive.
> Thus, suggested a patch.
>
> But if you think PM is in a stage when it still needs
> some debugging printing, I'm not going to insist, of course.
> You could do this later, when stuff is more stable.
These lines have been very informative when the boot fails
mysteriously. But I'd be fine seeing it only if debug is
specified in cmdline.
Tony
next prev parent reply other threads:[~2009-04-15 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 14:41 [PATCH] OMAP3: lessen amount of noisy messages Artem Bityutskiy
2009-04-15 12:22 ` Artem Bityutskiy
2009-04-15 13:57 ` Kim Kyuwon
2009-04-15 15:22 ` Paul Walmsley
2009-04-15 15:42 ` Artem Bityutskiy
2009-04-15 16:06 ` Artem Bityutskiy
2009-04-15 18:43 ` Tony Lindgren [this message]
2009-04-17 7:34 ` Paul Walmsley
2009-04-17 13:41 ` Kevin Hilman
2009-04-17 14:26 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090415184347.GJ2167@atomide.com \
--to=tony@atomide.com \
--cc=dedekind@yandex.ru \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox