Linux clock framework development
 help / color / mirror / Atom feed
From: Imran Shaik <imran.shaik@oss.qualcomm.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: Taniya Das <quic_tdas@quicinc.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Jagadeesh Kona <quic_jkona@quicinc.com>,
	linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/6] clk: qcom: camcc-sm8550: Specify Titan GDSC power domain as a parent to other
Date: Thu, 11 Sep 2025 16:38:51 +0530	[thread overview]
Message-ID: <10c0d04b-2c8c-4cf4-bb99-acf74f420341@oss.qualcomm.com> (raw)
In-Reply-To: <20250911011218.861322-2-vladimir.zapolskiy@linaro.org>



On 9/11/2025 6:42 AM, Vladimir Zapolskiy wrote:
> Make Titan GDSC power domain as a parent of all other GDSC power domains
> provided by the SM8550 camera clock controller to enforce a correct
> sequence of enabling and disabling power domains by the consumers.
> 
> Fixes: ccc4e6a061a2 ("clk: qcom: camcc-sm8550: Add camera clock controller driver for SM8550")
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
>  drivers/clk/qcom/camcc-sm8550.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
Reviewed-by: Imran Shaik <imran.shaik@oss.qualcomm.com>

Thanks,
Imran

  parent reply	other threads:[~2025-09-11 11:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  1:12 [PATCH 0/6] Specify Titan GDSC power domain as a parent to other Vladimir Zapolskiy
2025-09-11  1:12 ` [PATCH 1/6] clk: qcom: camcc-sm8550: " Vladimir Zapolskiy
2025-09-11  9:29   ` Konrad Dybcio
2025-09-11 11:08   ` Imran Shaik [this message]
2025-09-12  2:09   ` Bjorn Andersson
2025-09-12  6:23     ` Vladimir Zapolskiy
2025-09-16 15:38       ` Bjorn Andersson
2025-09-12 10:02   ` Bryan O'Donoghue
2025-09-11  1:12 ` [PATCH 2/6] clk: qcom: camcc-sm6350: " Vladimir Zapolskiy
2025-09-11  9:27   ` Konrad Dybcio
2025-09-11 11:09   ` Imran Shaik
2025-09-11 11:39   ` Luca Weiss
2025-09-12 10:09   ` Bryan O'Donoghue
2025-09-11  1:12 ` [PATCH 3/6] clk: qcom: camcc-sdm845: " Vladimir Zapolskiy
2025-09-11  9:28   ` Konrad Dybcio
2025-09-11 11:09   ` Imran Shaik
2025-09-12 10:13   ` Bryan O'Donoghue
2025-09-12 10:14   ` Bryan O'Donoghue
2025-09-11  1:12 ` [PATCH 4/6] clk: qcom: camcc-sm7150: Specify Titan GDSC power domain as a parent to IPEx and BPS Vladimir Zapolskiy
2025-09-11  9:28   ` Konrad Dybcio
2025-09-11 11:09   ` Imran Shaik
2025-09-12 10:13   ` Bryan O'Donoghue
2025-09-12 10:14   ` Bryan O'Donoghue
2025-09-11  1:12 ` [PATCH 5/6] clk: qcom: camcc-sm8250: Specify Titan GDSC power domain as a parent to IPE/BPS/SBI Vladimir Zapolskiy
2025-09-11  9:28   ` Konrad Dybcio
2025-09-11 11:09   ` Imran Shaik
2025-09-12 10:15   ` Bryan O'Donoghue
2025-09-11  1:12 ` [PATCH 6/6] clk: qcom: camcc-sm8450: " Vladimir Zapolskiy
2025-09-11  9:29   ` Konrad Dybcio
2025-09-11 11:09   ` Imran Shaik
2025-09-12 10:16   ` 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=10c0d04b-2c8c-4cf4-bb99-acf74f420341@oss.qualcomm.com \
    --to=imran.shaik@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=sboyd@kernel.org \
    --cc=vladimir.zapolskiy@linaro.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