From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Pritam Manohar Sutar'" <pritam.sutar@samsung.com>,
<krzk@kernel.org>, <s.nawrocki@samsung.com>,
<cw00.choi@samsung.com>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <sunyeal.hong@samsung.com>
Cc: <linux-samsung-soc@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <rosa.pila@samsung.com>,
<dev.tailor@samsung.com>, <faraz.ata@samsung.com>,
"'stable'" <stable@kernel.org>
Subject: RE: [PATCH v2] clk: samsung: correct clock summary for hsi1 block
Date: Sat, 10 May 2025 07:58:31 +0530 [thread overview]
Message-ID: <045701dbc153$3aa85bc0$aff91340$@samsung.com> (raw)
In-Reply-To: <20250506080154.3995512-1-pritam.sutar@samsung.com>
Hi Pritam
> -----Original Message-----
> From: Pritam Manohar Sutar <pritam.sutar@samsung.com>
> Sent: Tuesday, May 6, 2025 1:32 PM
> To: krzk@kernel.org; s.nawrocki@samsung.com; cw00.choi@samsung.com;
> alim.akhtar@samsung.com; mturquette@baylibre.com; sboyd@kernel.org;
> sunyeal.hong@samsung.com
> Cc: linux-samsung-soc@vger.kernel.org; linux-clk@vger.kernel.org; linux-
> arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> rosa.pila@samsung.com; dev.tailor@samsung.com;
> faraz.ata@samsung.com; Pritam Manohar Sutar
> <pritam.sutar@samsung.com>; stable <stable@kernel.org>
> Subject: [PATCH v2] clk: samsung: correct clock summary for hsi1 block
>
> clk_summary shows wrong value for "mout_hsi1_usbdrd_user".
> It shows 400Mhz instead of 40Mhz as below.
>
> dout_shared2_div4 1 1 0 400000000 0 0 50000 Y ...
> mout_hsi1_usbdrd_user 0 0 0 400000000 0 0 50000 Y ...
> dout_clkcmu_hsi1_usbdrd 0 0 0 40000000 0 0 50000 Y ...
>
> Correct the clk_tree by adding correct clock parent for
> "mout_hsi1_usbdrd_user".
>
> Post this change, clk_summary shows correct value.
>
> dout_shared2_div4 1 1 0 400000000 0 0 50000 Y ...
> mout_clkcmu_hsi1_usbdrd 0 0 0 400000000 0 0 50000 Y ...
> dout_clkcmu_hsi1_usbdrd 0 0 0 40000000 0 0 50000 Y ...
> mout_hsi1_usbdrd_user 0 0 0 40000000 0 0 50000 Y ...
>
> Fixes: 485e13fe2fb6 ("clk: samsung: add top clock support for ExynosAuto
> v920 SoC")
> Cc: stable <stable@kernel.org>
> Signed-off-by: Pritam Manohar Sutar <pritam.sutar@samsung.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
next prev parent reply other threads:[~2025-05-10 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250506075413epcas5p2ce0db6da9f359e9c3bb16b03c1a5eb4f@epcas5p2.samsung.com>
2025-05-06 8:01 ` [PATCH v2] clk: samsung: correct clock summary for hsi1 block Pritam Manohar Sutar
2025-05-10 2:28 ` Alim Akhtar [this message]
2025-05-12 6:29 ` Krzysztof Kozlowski
2025-05-12 6:38 ` Krzysztof Kozlowski
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='045701dbc153$3aa85bc0$aff91340$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=dev.tailor@samsung.com \
--cc=faraz.ata@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pritam.sutar@samsung.com \
--cc=rosa.pila@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=stable@kernel.org \
--cc=sunyeal.hong@samsung.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;
as well as URLs for NNTP newsgroup(s).