From: Vijay Kumar Tumati <vijay.tumati@oss.qualcomm.com>
To: Bryan O'Donoghue <bod@nxsw.ie>, Bryan O'Donoghue <bod@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Date: Tue, 3 Mar 2026 10:03:35 -0800 [thread overview]
Message-ID: <d18ea7aa-67e8-4f8b-b2b3-0a7499ec836e@oss.qualcomm.com> (raw)
In-Reply-To: <676e2a9f-d274-40fa-988f-e9388ba40f71@nxsw.ie>
On 3/3/2026 1:30 AM, Bryan O'Donoghue wrote:
> On 03/03/2026 09:27, Bryan O'Donoghue wrote:
>> - MXA - first time I've heard of this rail, from memory I don't remember
>> having seen this in ipcat when I could do so.
>
> Yeah no MXA isn't a required vote.
>
> https://lore.kernel.org/linux-arm-msm/9ff1645f-b2c9-4c1a-ae2d-96af416b08d9@oss.qualcomm.com/
If I am not wrong, CAMCC only enables the power domains that source the
CAMCC block and it's register access. And for that, it only needs those
power domains to be just enabled without any performance vote. Based on
her comment, if MXA is always enabled (at min level), probably CAMCC
driver doesn't need to enable or scale it explicitly. However, the
camera devices that actually depend on this power domain for their core
functionality need to scale this per the core clock corner. I can double
check though.
>
> ---
> bod
>
Thanks,
Vijay.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-03-03 18:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:34 [PATCH v3 0/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-02-26 12:34 ` [PATCH v3 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema Bryan O'Donoghue
2026-02-27 9:41 ` Krzysztof Kozlowski
2026-02-27 9:47 ` Bryan O'Donoghue
2026-03-03 1:51 ` Vijay Kumar Tumati
2026-03-03 9:27 ` Bryan O'Donoghue
2026-03-03 18:08 ` Vijay Kumar Tumati
2026-03-03 18:58 ` Vijay Kumar Tumati
2026-03-03 22:53 ` Bryan O'Donoghue
2026-03-03 23:17 ` Vijay Kumar Tumati
2026-03-03 23:26 ` Bryan O'Donoghue
2026-03-03 23:50 ` Vijay Kumar Tumati
2026-03-04 0:02 ` Bryan O'Donoghue
2026-03-04 0:15 ` Vijay Kumar Tumati
2026-03-03 9:30 ` Bryan O'Donoghue
2026-03-03 12:34 ` Konrad Dybcio
2026-03-03 14:56 ` Bryan O'Donoghue
2026-03-04 10:32 ` Konrad Dybcio
2026-03-03 18:03 ` Vijay Kumar Tumati [this message]
2026-03-03 22:31 ` Dmitry Baryshkov
2026-03-03 23:24 ` Vijay Kumar Tumati
2026-03-03 23:49 ` Dmitry Baryshkov
2026-03-03 23:51 ` Vijay Kumar Tumati
2026-02-26 12:34 ` [PATCH v3 2/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-02-27 1:40 ` Dmitry Baryshkov
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=d18ea7aa-67e8-4f8b-b2b3-0a7499ec836e@oss.qualcomm.com \
--to=vijay.tumati@oss.qualcomm.com \
--cc=bod@kernel.org \
--cc=bod@nxsw.ie \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@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