From: Brian Masney <bmasney@redhat.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: add debug message showing which unused clocks are disabled on boot
Date: Thu, 30 Mar 2023 10:05:37 -0400 [thread overview]
Message-ID: <ZCWXMXdaLdBb9KzL@x1> (raw)
In-Reply-To: <27ded6a4ebd67cef0d4b472a2aea442e.sboyd@kernel.org>
On Wed, Mar 29, 2023 at 02:49:50PM -0700, Stephen Boyd wrote:
> Quoting Brian Masney (2022-11-17 02:58:29)
> > The clk framework on bootup will automatically disable all unused clocks
> > on bootup unless the clk_ignore_unused kernel parameter is present.
> > Let's add a basic debugging log statement here that shows which clocks
> > are disabled. There is already tracepoint present here as well, but
> > there's nothing like a simple, good ol' fashioned printk for simplicity.
> >
> > Signed-off-by: Brian Masney <bmasney@redhat.com>
> > ---
>
> I'd like to see a documentation update instead that covers how to enable
> the tracepoint on the kernel commandline and have it print to the serial
> console.
Sure, I can do that. I see there's a section 'Disabling clock gating of
unused clocks' in Documentation/driver-api/clk.rst where I think this
would be appropriate.
Brian
next prev parent reply other threads:[~2023-03-30 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 10:58 [PATCH] clk: add debug message showing which unused clocks are disabled on boot Brian Masney
2023-03-29 21:49 ` Stephen Boyd
2023-03-30 14:05 ` Brian Masney [this message]
2023-04-11 19:30 ` Brian Masney
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=ZCWXMXdaLdBb9KzL@x1 \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).