From: barnabas.czeman@mainlining.org
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Vladimir Lypak <vladimir.lypak@gmail.com>
Subject: Re: [PATCH v4 3/3] media: qcom: camss: Add MSM8953 resources
Date: Wed, 13 Nov 2024 11:58:32 +0100 [thread overview]
Message-ID: <c09f206bee80d2c3d632ef07a5d17e4c@mainlining.org> (raw)
In-Reply-To: <7f8172ee-8285-4e7c-8ba3-826a5516fa9b@linaro.org>
On 2024-11-13 10:53, Bryan O'Donoghue wrote:
> On 13/11/2024 08:01, barnabas.czeman@mainlining.org wrote:
>>> I see that you do reuse csiphy_res_8x16 for this platform support, in
>>> this case let me ask you to double check/test that the "vdda"
>>> regulator
>>> is actually a CSIPHY regulator, and if so, please move the
>>> registration
>>> of the regulators to csiphy_res_8x16 as a preceding change.
>> It is placed in CSID at downstream and this is the documentation of
>> the downstream property:
>> - qcom,mipi-csi-vdd-supply : should contain regulator to be used for
>> this csid core
>> so it should be a csid regulator as i understand.
>> It is also placed at CSIDs in msm8953-camera.dtsi
>
> No, the regulator(s) supply voltage to the PHY.
On sm8250 it is for csiphy but on older soc like on msm8953, msm8917,
msm8916
this regulator is placed in csid nodes.
https://git.codelinaro.org/clo/la/kernel/msm-4.9/-/blob/LA.UM.10.6.2.c26-01500-89xx.0/arch/arm64/boot/dts/qcom/msm8953-camera.dtsi#L96
There is no regulator in csiphy nodes only PM domains.
I will check later move the regulator to the csiphy.
>
> Make sure you have:
>
> commit 44fdbb9d1a3892db92b2c9cf5f46e32ca4095d92
> Author: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> Date: Fri Sep 27 00:19:56 2024 +0300
>
> media: qcom: camss: add management of supply regulators to CSIPHY
>
> and give the change a try.
>
> ---
> bod
next prev parent reply other threads:[~2024-11-13 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 9:45 [PATCH v4 0/3] Add MSM8953 camss support Barnabás Czémán
2024-11-03 9:45 ` [PATCH v4 1/3] media: qcom: camss: implement pm domain ops for VFE v4.1 Barnabás Czémán
2024-11-03 9:45 ` [PATCH v4 2/3] media: dt-bindings: Add qcom,msm8953-camss Barnabás Czémán
2024-11-03 16:09 ` Krzysztof Kozlowski
2024-11-13 4:47 ` Vladimir Zapolskiy
2024-11-03 9:45 ` [PATCH v4 3/3] media: qcom: camss: Add MSM8953 resources Barnabás Czémán
2024-11-13 4:58 ` Vladimir Zapolskiy
2024-11-13 8:01 ` barnabas.czeman
2024-11-13 9:53 ` Bryan O'Donoghue
2024-11-13 10:58 ` barnabas.czeman [this message]
2024-11-13 13:28 ` Vladimir Zapolskiy
2024-11-13 15:23 ` Bryan O'Donoghue
2024-11-13 15:32 ` barnabas.czeman
2024-11-13 21:14 ` Vladimir Zapolskiy
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=c09f206bee80d2c3d632ef07a5d17e4c@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.lypak@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.