Linux clock framework development
 help / color / mirror / Atom feed
From: Imran Shaik <imran.shaik@oss.qualcomm.com>
To: Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Taniya Das <quic_tdas@quicinc.com>,
	Melody Olvera <quic_molvera@quicinc.com>,
	Ajit Pandey <quic_ajipan@quicinc.com>,
	Imran Shaik <quic_imrashai@quicinc.com>,
	Luca Weiss <luca.weiss@fairphone.com>
Cc: Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
	Taniya Das <taniya.das@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] clk: qcom: gcc-sm4450: Update the SDCC RCGs to use shared_floor_ops
Date: Wed, 26 Nov 2025 14:19:27 +0530	[thread overview]
Message-ID: <5ddaa17f-931e-4883-a91d-89f60b392c44@oss.qualcomm.com> (raw)
In-Reply-To: <20251126-sdcc_shared_floor_ops-v1-3-9038430dfed4@oss.qualcomm.com>



On 11/26/2025 9:45 AM, Jagadeesh Kona wrote:
> Use shared_floor_ops for the SDCC RCGs so the RCG is safely parked
> during disable and the new parent configuration is programmed in
> hardware only when the new parent is enabled, avoiding cases where
> the RCG configuration fails to update.
> 
> Fixes: c32c4ef98bac ("clk: qcom: Add GCC driver support for SM4450")
> Signed-off-by: Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
> ---
>  drivers/clk/qcom/gcc-sm4450.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
Reviewed-by: Imran Shaik <imran.shaik@oss.qualcomm.com>

Thanks,
Imran

  parent reply	other threads:[~2025-11-26  8:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  4:15 [PATCH 0/5] clk: qcom: gcc: Update the SDCC RCGs to use shared_floor_ops Jagadeesh Kona
2025-11-26  4:15 ` [PATCH 1/5] clk: qcom: gcc-sm8450: " Jagadeesh Kona
2025-11-26  7:42   ` Dmitry Baryshkov
2025-11-26  8:47   ` Imran Shaik
2025-11-26  9:42   ` Taniya Das
2025-11-26  4:15 ` [PATCH 2/5] clk: qcom: gcc-sm8750: " Jagadeesh Kona
2025-11-26  7:42   ` Dmitry Baryshkov
2025-11-26  8:49   ` Imran Shaik
2025-11-26  9:44   ` Taniya Das
2025-11-26  4:15 ` [PATCH 3/5] clk: qcom: gcc-sm4450: " Jagadeesh Kona
2025-11-26  8:44   ` Dmitry Baryshkov
2025-11-26  8:49   ` Imran Shaik [this message]
2025-11-26  9:44   ` Taniya Das
2025-11-26  4:15 ` [PATCH 4/5] clk: qcom: gcc-sdx75: " Jagadeesh Kona
2025-11-26  8:44   ` Dmitry Baryshkov
2025-11-26  8:48   ` Imran Shaik
2025-11-26  9:44   ` Taniya Das
2025-11-26  4:15 ` [PATCH 5/5] clk: qcom: gcc-milos: " Jagadeesh Kona
2025-11-26  8:44   ` Dmitry Baryshkov
2025-11-26  8:49   ` Imran Shaik
2025-11-26  9:45   ` Taniya Das
2025-11-26  8:50 ` [PATCH 0/5] clk: qcom: gcc: " Imran Shaik
2025-11-26 17:34   ` Jagadeesh Kona
2025-11-26  9:11 ` Vladimir Zapolskiy

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=5ddaa17f-931e-4883-a91d-89f60b392c44@oss.qualcomm.com \
    --to=imran.shaik@oss.qualcomm.com \
    --cc=ajit.pandey@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=jagadeesh.kona@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=lumag@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_ajipan@quicinc.com \
    --cc=quic_imrashai@quicinc.com \
    --cc=quic_molvera@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=sboyd@kernel.org \
    --cc=taniya.das@oss.qualcomm.com \
    --cc=vkoul@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