public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jagadeesh Kona <quic_jkona@quicinc.com>
To: Taniya Das <quic_tdas@quicinc.com>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-clk@vger.kernel.org>
Subject: Re: [PATCH 0/2] arm64: dts: qcom: sm8550: camcc: Manage MMCX and MXC
Date: Wed, 26 Mar 2025 17:16:11 +0530	[thread overview]
Message-ID: <5dac9f3e-731f-482f-98ff-10b521231001@quicinc.com> (raw)
In-Reply-To: <da67d3a1-e3df-4d01-a052-8c906172c51c@quicinc.com>



On 3/13/2025 5:08 PM, Taniya Das wrote:
> 
> 
> On 3/4/2025 4:25 AM, Vladimir Zapolskiy wrote:
>> It was discovered that on SM8550 platform Camera Clock controller shall
>> manage MMCX and MXC power domains, otherwise MMIO access to CCI or CAMSS
>> breaks the execution, the problem has been discussed with Jagadeesh at
>> https://lore.kernel.org/all/a5540676-9402-45c4-b647-02fdc2b92233@quicinc.com/
>>
>> Since 'power-domains' property becomes generalized, Rob asked to remove
>> its description, which is done in the first patch of the series, see
>> https://lore.kernel.org/all/20240927224833.GA159707-robh@kernel.org/
>>
>> Vladimir Zapolskiy (2):
>>   dt-bindings: clock: qcom: sm8450-camcc: Allow to specify two power domains
>>   arm64: dts: qcom: sm8550: Additionally manage MXC power domain in camcc
>>
> 
> Hi Vladimir, as we are preparing to submit the code for multi-power
> domain support for the clock controller in our series
> (https://lore.kernel.org/all/20250306-videocc-pll-multi-pd-voting-v2-0-0cd00612bc0e@quicinc.com),
> there has been a request to incorporate the CAMCC-related changes as
> well. If you are okay with us including this series changes(maintaining
> your authorship) in our series, then we can integrate them and address
> any comments in our next submission.
> 

Hi Vladimir,

I will be including your above 2 patches in the next version of my series[1] which adds
MXC PD support for SM8450, SM8650 camcc DT nodes since my series is dependent on above
bindings change. Doing so will fix the bot warnings reported[2] in this series as well
and I will fix if there are still any more warnings left and post.

[1] https://lore.kernel.org/all/cd092022-cf6d-421a-a29d-69f7f4f068b6@quicinc.com/
[2] https://lore.kernel.org/all/174105227313.195955.8409784191665720030.robh@kernel.org/

Thanks,
Jagadeesh

>>  .../devicetree/bindings/clock/qcom,sm8450-camcc.yaml          | 4 +---
>>  arch/arm64/boot/dts/qcom/sm8550.dtsi                          | 3 ++-
>>  2 files changed, 3 insertions(+), 4 deletions(-)
>>
> 
> 

      reply	other threads:[~2025-03-26 11:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 22:55 [PATCH 0/2] arm64: dts: qcom: sm8550: camcc: Manage MMCX and MXC Vladimir Zapolskiy
2025-03-03 22:55 ` [PATCH 1/2] dt-bindings: clock: qcom: sm8450-camcc: Allow to specify two power domains Vladimir Zapolskiy
2025-03-03 23:51   ` Dmitry Baryshkov
2025-03-04  0:31   ` Rob Herring (Arm)
2025-03-03 22:55 ` [PATCH 2/2] arm64: dts: qcom: sm8550: Additionally manage MXC power domain in camcc Vladimir Zapolskiy
2025-03-03 23:53   ` Dmitry Baryshkov
2025-03-04  8:30     ` Vladimir Zapolskiy
2025-03-04  8:37     ` Vladimir Zapolskiy
2025-03-04  8:40       ` Dmitry Baryshkov
2025-03-13  4:39         ` Taniya Das
2025-03-13  7:26           ` Dmitry Baryshkov
2025-03-13  7:52           ` Luca Weiss
2025-03-13 11:57             ` Taniya Das
2025-10-17 14:05               ` Luca Weiss
2025-10-20 12:21                 ` Konrad Dybcio
2025-10-20 13:00                   ` Bryan O'Donoghue
2025-10-21 10:07                     ` Luca Weiss
2025-10-21 10:36                   ` Luca Weiss
2025-10-21 10:39                     ` Konrad Dybcio
2025-10-21  9:48                 ` Vladimir Zapolskiy
2025-10-21  9:58                   ` Luca Weiss
2025-10-21 11:12                     ` Taniya Das
2025-10-21 14:24                       ` Luca Weiss
2025-10-21 14:56                         ` Luca Weiss
2025-10-22  6:27                           ` Taniya Das
2025-03-12 21:00     ` Bryan O'Donoghue
2025-03-13  4:39     ` Taniya Das
2025-03-13  9:10       ` Bryan O'Donoghue
2025-03-13  9:25         ` Bryan O'Donoghue
2025-03-13 11:32           ` Taniya Das
2025-03-04  1:38 ` [PATCH 0/2] arm64: dts: qcom: sm8550: camcc: Manage MMCX and MXC Rob Herring (Arm)
2025-03-13 11:38 ` Taniya Das
2025-03-26 11:46   ` Jagadeesh Kona [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=5dac9f3e-731f-482f-98ff-10b521231001@quicinc.com \
    --to=quic_jkona@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --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