From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2] clk: expand clk_ignore_unused mechanism to keep only a few clks on
Date: Wed, 22 Sep 2021 10:15:49 +0200 [thread overview]
Message-ID: <20210922081549.kit3lsek7lh6w6ji@pengutronix.de> (raw)
In-Reply-To: <20210819121403.337833-1-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hello,
On Thu, Aug 19, 2021 at 02:14:03PM +0200, Uwe Kleine-König wrote:
> Allow to pass an integer n that results in only keeping n unused clocks
> enabled.
>
> This helps to debug the problem if you only know that clk_ignore_unused
> helps but you have no clue yet which clock is the culprit.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
I consider this patch really helpful, it helped me to debug a clk issue
without having to recompile the kernel for each bisection step.
On #kernelnewbies I got some positive feedback for it (1629304050 < j_ey>
ukleinek: nice clk_ignore_unused patch, I added a pr_err there recently
to print the clocks that were being disabled).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-22 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 12:14 [PATCH v2] clk: expand clk_ignore_unused mechanism to keep only a few clks on Uwe Kleine-König
2021-09-22 8:15 ` Uwe Kleine-König [this message]
2021-10-14 15:43 ` Uwe Kleine-König
2022-05-25 8:17 ` Uwe Kleine-König
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=20210922081549.kit3lsek7lh6w6ji@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=corbet@lwn.net \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@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).