From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Taniya Das" <quic_tdas@quicinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Vladimir Zapolskiy" <vladimir.zapolskiy@linaro.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Jagadeesh Kona" <quic_jkona@quicinc.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-clk@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8550: Additionally manage MXC power domain in camcc
Date: Thu, 13 Mar 2025 08:52:06 +0100 [thread overview]
Message-ID: <D8EZ47Z557OX.37FDVYA5AHET0@fairphone.com> (raw)
In-Reply-To: <f41061a2-cf45-4588-8df7-22270c936ee2@quicinc.com>
Hi Taniya,
On Thu Mar 13, 2025 at 5:39 AM CET, Taniya Das wrote:
>
>
> On 3/4/2025 2:10 PM, Dmitry Baryshkov wrote:
>> On Tue, 4 Mar 2025 at 09:37, Vladimir Zapolskiy
>> <vladimir.zapolskiy@linaro.org> wrote:
>>>
>>> On 3/4/25 01:53, Dmitry Baryshkov wrote:
>>>> On Tue, Mar 04, 2025 at 12:55:21AM +0200, Vladimir Zapolskiy wrote:
>>>>> SM8550 Camera Clock Controller shall enable both MXC and MMCX power
>>>>> domains.
>>>>
>>>> Are those really required to access the registers of the cammcc? Or is
>>>> one of those (MXC?) required to setup PLLs? Also, is this applicable
>>>> only to sm8550 or to other similar clock controllers?
>>>
>>> Due to the described problem I experience a fatal CPU stall on SM8550-QRD,
>>> not on any SM8450 or SM8650 powered board for instance, however it does
>>> not exclude an option that the problem has to be fixed for other clock
>>> controllers, but it's Qualcomm to confirm any other touched platforms,
>>
>> Please work with Taniya to identify used power domains.
>>
>
> CAMCC requires both MMCX and MXC to be functional.
Could you check whether any clock controllers on SM6350/SM7225 (Bitra)
need multiple power domains, or in general which clock controller uses
which power domain.
That SoC has camcc, dispcc, gcc, gpucc, npucc and videocc.
That'd be highly appreciated since I've been hitting weird issues there
that could be explained by some missing power domains.
Regards
Luca
>
>>> for instance x1e80100-camcc has it resolved right at the beginning.
>>>
>>> To my understanding here 'required-opps' shall also be generalized, so
>>> the done copy from x1e80100-camcc was improper, and the latter dt-binding
>>> should be fixed.
>>
>> Yes
>>
>
> required-opps is not mandatory for MXC as we ensure that MxC would never
> hit retention.
>
> https://lore.kernel.org/r/20240625-avoid_mxc_retention-v2-1-af9c2f549a5f@quicinc.com
>
>
>>
>>
next prev parent reply other threads:[~2025-03-13 7:52 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 [this message]
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
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=D8EZ47Z557OX.37FDVYA5AHET0@fairphone.com \
--to=luca.weiss@fairphone.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_jkona@quicinc.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