From: Sumit Garg <sumit.garg@kernel.org>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
u-boot@lists.denx.de, u-boot-qcom@groups.io
Subject: Re: [PATCH 4/6] clk/qcom: qcm2290: show clock name in set_rate()
Date: Thu, 10 Apr 2025 14:21:37 +0530 [thread overview]
Message-ID: <Z_eGmUkX4G_gF1ob@sumit-X1> (raw)
In-Reply-To: <20250409-livetree-fixup-v1-4-76dfea80b07f@linaro.org>
On Wed, Apr 09, 2025 at 07:17:27PM +0200, Caleb Connolly wrote:
> The device name is always clk_qcom... Not very useful.
>
> Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
> ---
> drivers/clk/qcom/clock-qcm2290.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
>
> diff --git a/drivers/clk/qcom/clock-qcm2290.c b/drivers/clk/qcom/clock-qcm2290.c
> index 1326b770c3ebd723120de4b6657aafac726023d6..fad104fb91aec8917de66b63dd546926c8856011 100644
> --- a/drivers/clk/qcom/clock-qcm2290.c
> +++ b/drivers/clk/qcom/clock-qcm2290.c
> @@ -87,9 +87,9 @@ static ulong qcm2290_set_rate(struct clk *clk, ulong rate)
> {
> struct msm_clk_priv *priv = dev_get_priv(clk->dev);
> const struct freq_tbl *freq;
>
> - debug("%s: clk %s rate %lu\n", __func__, clk->dev->name, rate);
> + debug("%s: clk %s rate %lu\n", __func__, qcm2290_clks[clk->id].name, rate);
>
> switch (clk->id) {
> case GCC_QUPV3_WRAP0_S4_CLK: /*UART2*/
> freq = qcom_find_freq(ftbl_gcc_qupv3_wrap0_s0_clk_src, rate);
>
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-04-10 8:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 17:17 [PATCH 0/6] Qualcomm: cleanup OF_LIVE fixup and fix RB1/2 Caleb Connolly
2025-04-09 17:17 ` [PATCH 1/6] event: signal when livetree has been built Caleb Connolly
2025-04-10 8:44 ` Sumit Garg
2025-04-10 8:54 ` Neil Armstrong
2025-04-10 11:27 ` Simon Glass
2025-04-10 13:00 ` Caleb Connolly
2025-04-10 13:07 ` Simon Glass
2025-04-10 14:04 ` Caleb Connolly
2025-04-10 14:15 ` Simon Glass
2025-04-10 15:41 ` Caleb Connolly
2025-04-10 21:25 ` Simon Glass
2025-04-11 11:52 ` Caleb Connolly
2025-04-11 18:30 ` Simon Glass
2025-04-09 17:17 ` [PATCH 2/6] mach-snapdragon: use EVT_OF_LIVE_INIT to apply DT fixups Caleb Connolly
2025-04-10 8:50 ` Sumit Garg
2025-04-10 8:54 ` Neil Armstrong
2025-04-09 17:17 ` [PATCH 3/6] mach-snapdragon: of_fixup: skip disabled USB nodes Caleb Connolly
2025-04-10 7:45 ` Neil Armstrong
2025-04-10 8:51 ` Sumit Garg
2025-04-09 17:17 ` [PATCH 4/6] clk/qcom: qcm2290: show clock name in set_rate() Caleb Connolly
2025-04-10 7:45 ` Neil Armstrong
2025-04-10 8:51 ` Sumit Garg [this message]
2025-04-09 17:17 ` [PATCH 5/6] mach-snapdragon: of_fixup: set dr_mode for RB1/2 boards Caleb Connolly
2025-04-10 7:46 ` Neil Armstrong
2025-04-10 9:04 ` Sumit Garg
2025-04-09 17:17 ` [PATCH 6/6] pinctrl: qcom: qcm2290: fix off by 1 in pin_count Caleb Connolly
2025-04-10 7:46 ` Neil Armstrong
2025-04-10 9:05 ` Sumit Garg
2025-04-10 8:41 ` [PATCH 0/6] Qualcomm: cleanup OF_LIVE fixup and fix RB1/2 Sumit Garg
2025-04-10 9:54 ` Caleb Connolly
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=Z_eGmUkX4G_gF1ob@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=lukma@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/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