From: Jordan Crouse <jorcrous@amazon.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: qcom: camcc-sm8250: Use clk_rcg2_shared_ops for some RCGs
Date: Wed, 22 Jan 2025 22:23:03 +0000 [thread overview]
Message-ID: <20250122222303.GA29229@amazon.com> (raw)
In-Reply-To: <fye2hzgb7pbd7mc7txdl6c57uohrs224ivicgwy3xxqzximard@gvwsey2yqgin>
On Thu, Jan 23, 2025 at 12:12:46AM +0200, Dmitry Baryshkov wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Wed, Jan 22, 2025 at 09:34:27PM +0000, Jordan Crouse wrote:
> > Update some RCGs on the sm8250 camera clock controller to use
> > clk_rcg2_shared_ops. The shared_ops ensure the RCGs get parked
> > to the XO during clock disable to prevent the clocks from locking up
> > when the GDSC is enabled. These mirror similar fixes for other controllers
> > such as commit 8d4025943e13 ("clk: qcom: camcc-sc7180: Use runtime PM ops
> > instead of clk ones").
>
> I'm not sure, how the mentioned commit is relevant to this fix.
> Did you mean e5c359f70e4b ("clk: qcom: camcc: Update the clock ops for the SC7180")?
Oops, yep. Great catch. v2 coming.
Jordan
next prev parent reply other threads:[~2025-01-22 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 21:34 [PATCH] clk: qcom: camcc-sm8250: Use clk_rcg2_shared_ops for some RCGs Jordan Crouse
2025-01-22 22:12 ` Dmitry Baryshkov
2025-01-22 22:23 ` Jordan Crouse [this message]
2025-01-23 11:31 ` Bryan O'Donoghue
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=20250122222303.GA29229@amazon.com \
--to=jorcrous@amazon.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--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