From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/6] dt-bindings: media: Add qcom,x1e80100-camss binding
Date: Wed, 20 Nov 2024 23:27:48 +0000 [thread overview]
Message-ID: <91afb347-e8ee-4a97-bd8b-9a1413051cb9@linaro.org> (raw)
In-Reply-To: <bb58d02f-9ed6-476f-8bc6-ad56cb35e37f@linaro.org>
On 20/11/2024 23:02, Vladimir Zapolskiy wrote:
> like "vdd-csiphy-0p9-supply" and "vdd-csiphy-1p2-supply"?
In theory, however I'd like to avoid adding endless strings of new names
into the driver code for each different power input.
We can add this additional string name though in the interim between now
and refactor for the PHY API.
> Also you put a description like "supply to PHY refclk pll block", but if I
> remember correctly once you've said that the datasheet (of another SoC)
> does not give any clues about the usage of the supply, thus it invalidates
> the given description.
I'm surmising by extrapolation - that's "probably" what those are just
at different voltage levels based on previous iterations of this PHY.
I'm just as happy not to describe this or to describe it as no mor that
the 1.2v supply etc.
---
bod
next prev parent reply other threads:[~2024-11-20 23:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 13:10 [PATCH 0/6] Add dt-bindings and dtsi changes for CAMSS on x1e80100 silicon Bryan O'Donoghue
2024-11-19 13:10 ` [PATCH 1/6] dt-bindings: i2c: qcom-cci: Document x1e80100 compatible Bryan O'Donoghue
2024-11-20 8:49 ` Krzysztof Kozlowski
2024-11-20 14:35 ` Bryan O'Donoghue
2024-11-19 13:10 ` [PATCH 2/6] dt-bindings: media: Add qcom,x1e80100-camss binding Bryan O'Donoghue
2024-11-19 14:34 ` Vladimir Zapolskiy
2024-11-19 15:11 ` Bryan O'Donoghue
2024-11-20 23:02 ` Vladimir Zapolskiy
2024-11-20 23:27 ` Bryan O'Donoghue [this message]
2024-11-21 0:37 ` Vladimir Zapolskiy
2024-11-21 9:36 ` Bryan O'Donoghue
2024-11-20 8:55 ` Krzysztof Kozlowski
2024-11-19 13:10 ` [PATCH 3/6] dt-bindings: clock: qcom: Add second power-domain to CAMCC Bryan O'Donoghue
2024-11-19 14:47 ` Vladimir Zapolskiy
2024-11-19 15:12 ` Bryan O'Donoghue
2024-11-20 8:51 ` Krzysztof Kozlowski
2024-11-20 11:53 ` Dmitry Baryshkov
2024-11-19 13:10 ` [PATCH 4/6] arm64: dts: qcom: x1e80100: Add CAMCC block definition Bryan O'Donoghue
2024-12-02 14:27 ` Konrad Dybcio
2024-12-02 15:02 ` Dmitry Baryshkov
2024-12-02 15:30 ` Bryan O'Donoghue
2024-12-05 17:27 ` Konrad Dybcio
2024-11-19 13:10 ` [PATCH 5/6] arm64: dts: qcom: x1e80100: Add CCI definitions Bryan O'Donoghue
2024-11-19 14:42 ` Vladimir Zapolskiy
2024-12-07 11:59 ` Konrad Dybcio
2024-12-07 12:54 ` Bryan O'Donoghue
2024-11-19 13:10 ` [PATCH 6/6] arm64: dts: qcom: x1e80100: Add CAMSS block definition Bryan O'Donoghue
2024-11-19 14:44 ` Vladimir Zapolskiy
2024-11-19 15:14 ` Bryan O'Donoghue
2024-11-20 8:52 ` Krzysztof Kozlowski
2024-12-07 12:24 ` 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=91afb347-e8ee-4a97-bd8b-9a1413051cb9@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_jkona@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=todor.too@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox