Linux clock framework development
 help / color / mirror / Atom feed
From: Taniya Das <quic_tdas@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Taniya Das <taniya.das@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
	Imran Shaik <imran.shaik@oss.qualcomm.com>,
	Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@linaro.org>
Subject: Re: [PATCH v3] clk: qcom: gcc-qcs615: Update the SDCC clock to use shared_floor_ops
Date: Wed, 29 Oct 2025 16:01:03 +0530	[thread overview]
Message-ID: <557ff048-7e5d-409e-bf21-98328a834bc8@quicinc.com> (raw)
In-Reply-To: <c361ea17-7480-4a10-b446-5072e8edd76d@oss.qualcomm.com>



On 10/29/2025 3:17 PM, Konrad Dybcio wrote:
> I noticed none of SM8[1234567]50 / hamoa / glymur uses _shared_ here.. 
> 
> I see that e.g. SM8250's downstream sets it though - should some of
> these be fixed up too?

I wanted to fix them as well, just trying to check the downstream
history of these clocks and then update them.

Regards,
Taniya.


  reply	other threads:[~2025-10-29 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  9:37 [PATCH v3] clk: qcom: gcc-qcs615: Update the SDCC clock to use shared_floor_ops Taniya Das
2025-10-29  9:47 ` Konrad Dybcio
2025-10-29 10:31   ` Taniya Das [this message]
2025-10-30  9:17     ` Konrad Dybcio
2025-10-30  5:10 ` Imran Shaik
2025-10-30 16:25 ` Bjorn Andersson

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=557ff048-7e5d-409e-bf21-98328a834bc8@quicinc.com \
    --to=quic_tdas@quicinc.com \
    --cc=abel.vesa@linaro.org \
    --cc=ajit.pandey@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=imran.shaik@oss.qualcomm.com \
    --cc=jagadeesh.kona@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=taniya.das@oss.qualcomm.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