From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: gcc-ipq5424: drop the CLK_IGNORE_UNUSED flag
Date: Tue, 2 Jun 2026 15:36:56 +0530 [thread overview]
Message-ID: <d2565822-ab8a-4dea-bafb-addd698cc35a@oss.qualcomm.com> (raw)
In-Reply-To: <4358d0b5-48ae-49f2-a50c-115a54958505@oss.qualcomm.com>
On 5/25/2026 10:49 PM, Kathiravan Thirumoorthy wrote:
>
> On 5/25/2026 8:55 PM, Dmitry Baryshkov wrote:
>> On Mon, May 25, 2026 at 08:35:16PM +0530, Kathiravan Thirumoorthy wrote:
>>> On 5/25/2026 3:39 PM, Dmitry Baryshkov wrote:
>>>> On Mon, May 25, 2026 at 03:07:17PM +0530, Kathiravan Thirumoorthy
>>>> wrote:
>>>>> Now that Linux has the consumer for the GPLL4, drop the
>>>> what is the consumer? When was it added?
>>> PCIe and USB are the major consumers, which got added with the below
>>> commits
>>> and landed in v6.16 and v6.14 respectively.
>>>
>>> ab7f31a3830d ("arm64: dts: qcom: ipq5424: Add PCIe PHYs and controller
>>> nodes")
>>>
>>> 113d52bdc820 ("arm64: dts: qcom: ipq5424: Add USB controller and phy
>>> nodes")
>>>
>>> While I was revisiting the code found that this flag is not removed.
>>> Hence I
>>> sent this.
>>>
>>> Shall I reword the commit message as below for the next spin?
>>>
>>> --
>>>
>>> Since PCIe and USB are enabled and consume GPLL4, there is no need to
>>> keep the CLK_IGNORE_UNUSED flag. Drop it.
>> Yes, it would be perfect. BTW: what happens if both are disabled (or not
>> probed at the boot time)?
>
> Until all the drivers probed, icc_sync_state() will not disable the
> ICC clocks which will in turn keep GPLL4 in ON state. If we disable
> the nodes, then system will go for the reboot without much information.
Dmitry, Do you have any further comments? Will that be okay if I can
send the V2 with updated commit message?
prev parent reply other threads:[~2026-06-02 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 9:37 Kathiravan Thirumoorthy
2026-05-25 10:09 ` Dmitry Baryshkov
2026-05-25 15:05 ` Kathiravan Thirumoorthy
2026-05-25 15:25 ` Dmitry Baryshkov
2026-05-25 17:19 ` Kathiravan Thirumoorthy
2026-06-02 10:06 ` Kathiravan Thirumoorthy [this message]
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=d2565822-ab8a-4dea-bafb-addd698cc35a@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®