From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Taniya Das <taniya.das@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: sm8750: Add camera clock controller
Date: Fri, 20 Feb 2026 15:25:03 +0100 [thread overview]
Message-ID: <a39f5526-8727-4fb6-9a93-36f412b93f88@oss.qualcomm.com> (raw)
In-Reply-To: <c8e9eb0c-9c49-401d-ae4e-21dcb1e1e843@oss.qualcomm.com>
On 2/20/26 3:23 PM, Taniya Das wrote:
>
>
> On 2/20/2026 4:25 PM, Konrad Dybcio wrote:
>> On 2/20/26 11:28 AM, Taniya Das wrote:
>>> The camera clock controller is split into cambistmclk and camcc. The
>>> cambist clock controller handles the mclks and the rest of the clocks of
>>> camera are part of the camcc clock controller.
>>> Add the camcc clock controller device node for SM8750 SoC.
>>>
>>> Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
>>> ---
>>> Changes in v2:
>>> - Update the MxC phandle to use MX for camcc node.
>>
>> My point was that both MXC and MXA are used
>>
>
> My bad, even I think I got confused with this. We really do not need MxA
> voting as it is always ON. We can sustain with MxC only.
Does that mean we don't even need any particular RPMH level on MxA
for this usecase, just for it to be on (which as you said it always is)?
Konrad
next prev parent reply other threads:[~2026-02-20 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 10:28 Taniya Das
2026-02-20 10:55 ` Konrad Dybcio
2026-02-20 14:23 ` Taniya Das
2026-02-20 14:25 ` Konrad Dybcio [this message]
2026-02-20 14:28 ` Taniya Das
2026-02-20 14:36 ` Konrad Dybcio
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=a39f5526-8727-4fb6-9a93-36f412b93f88@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®