From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
<cros-qcom-dts-watchers@chromium.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 09/14] arm64: dts: qcom: sm6350: add refgen regulator and use it for DSI
Date: Tue, 23 Sep 2025 09:17:17 +0200 [thread overview]
Message-ID: <DCZZV93PMWRZ.1J9IZBZYP5RGM@fairphone.com> (raw)
In-Reply-To: <20250921-refgen-v1-9-9d93e64133ea@oss.qualcomm.com>
Hi Dmitry,
On Sun Sep 21, 2025 at 9:09 AM CEST, Dmitry Baryshkov wrote:
> Add the refgen regulator block and use it for the DSI controller.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/sm6350.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi b/arch/arm64/boot/dts/qcom/sm6350.dtsi
> index 8459b27cacc72a4827a2e289e669163ad6250059..dd009569a6683a25f13b068e3e0bd8746b2ac501 100644
> --- a/arch/arm64/boot/dts/qcom/sm6350.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm6350.dtsi
> @@ -1768,6 +1768,12 @@ usb_1_hsphy: phy@88e3000 {
> resets = <&gcc GCC_QUSB2PHY_PRIM_BCR>;
> };
>
> + refgen: regulator@88e7000 {
> + compatible = "qcom,sm6350-refgen-regulator",
> + "qcom,sm8250-refgen-regulator";
> + reg = <0x0 0x088e7000 0x0 0x84>;
Are you sure the size is 0x84? Downstream and hwio_bitra_V1.cmm would
suggest size to be 0x60.
For sc7280, hwio_kodiak_E5.0.cmm does say 0x84 for refgen.
Apart from that, it's also what I have lying around somewhere, should've
upstreamed this already.
Reviewed-by: Luca Weiss <luca.weiss@fairphone.com>
Regards
Luca
> + };
> +
> usb_1_qmpphy: phy@88e8000 {
> compatible = "qcom,sm6350-qmp-usb3-dp-phy";
> reg = <0x0 0x088e8000 0x0 0x3000>;
> @@ -2360,6 +2366,8 @@ mdss_dsi0: dsi@ae94000 {
> phys = <&mdss_dsi0_phy>;
> phy-names = "dsi";
>
> + refgen-supply = <&refgen>;
> +
> #address-cells = <1>;
> #size-cells = <0>;
>
next prev parent reply other threads:[~2025-09-23 7:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 7:09 [PATCH 00/14] arm64: dts: qcom: add refgen regulators where applicable Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 01/14] regulator: dt-bindings: qcom,sdm845-refgen-regulator: document more platforms Dmitry Baryshkov
2025-09-22 20:36 ` Rob Herring (Arm)
2025-09-21 7:09 ` [PATCH 02/14] arm64: dts: qcom: lemans: move USB PHYs to a proper place Dmitry Baryshkov
2025-09-24 13:15 ` Konrad Dybcio
2025-09-21 7:09 ` [PATCH 03/14] arm64: dts: qcom: lemans: add refgen regulator and use it for DSI Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 04/14] arm64: dts: qcom: sc7180: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 05/14] arm64: dts: qcom: sc7280: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 06/14] arm64: dts: qcom: sc8180x: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 07/14] arm64: dts: qcom: sdm670: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 08/14] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 09/14] arm64: dts: qcom: sm6350: " Dmitry Baryshkov
2025-09-23 7:17 ` Luca Weiss [this message]
2025-09-26 13:27 ` Konrad Dybcio
2025-09-26 13:44 ` Dmitry Baryshkov
2025-09-26 13:48 ` Konrad Dybcio
2025-09-21 7:09 ` [PATCH 10/14] arm64: dts: qcom: sm8150: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 11/14] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 12/14] arm64: dts: qcom: qcs8300: add refgen regulator Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 13/14] arm64: dts: qcom: sc8280xp: " Dmitry Baryshkov
2025-09-21 7:09 ` [PATCH 14/14] arm64: dts: qcom: sm6375: " Dmitry Baryshkov
2025-09-23 15:31 ` (subset) [PATCH 00/14] arm64: dts: qcom: add refgen regulators where applicable Mark Brown
2025-09-24 10:13 ` Konrad Dybcio
2025-09-24 17:32 ` Dmitry Baryshkov
2025-09-24 18:13 ` Konrad Dybcio
2025-10-27 22:36 ` Bjorn Andersson
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=DCZZV93PMWRZ.1J9IZBZYP5RGM@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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