From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/11] arm64: dts: qcom: sm7225: align RPMh regulator nodes with bindings
Date: Fri, 27 Jan 2023 12:56:25 +0100 [thread overview]
Message-ID: <573c9b6f-984f-add4-7792-1df848918b5d@linaro.org> (raw)
In-Reply-To: <20230127114347.235963-7-krzysztof.kozlowski@linaro.org>
On 27.01.2023 12:43, Krzysztof Kozlowski wrote:
> Device node names should be generic and bindings expect certain pattern
> for RPMh regulator nodes.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts b/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> index b86a1c6f08be..52bb48c02536 100644
> --- a/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> +++ b/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> @@ -115,7 +115,7 @@ &adsp {
> };
>
> &apps_rsc {
> - pm6350-rpmh-regulators {
> + regulators-0 {
> compatible = "qcom,pm6350-rpmh-regulators";
> qcom,pmic-id = "a";
>
> @@ -244,7 +244,7 @@ vreg_l22a: ldo22 {
> };
> };
>
> - pm6150l-rpmh-regulators {
> + regulators-1 {
> compatible = "qcom,pm6150l-rpmh-regulators";
> qcom,pmic-id = "e";
>
next prev parent reply other threads:[~2023-01-27 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 11:43 [PATCH 01/11] ARM: dts: qcom-sdx55: " Krzysztof Kozlowski
2023-01-27 11:43 ` [PATCH 02/11] ARM: dts: qcom-sdx65: " Krzysztof Kozlowski
2023-01-27 11:51 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 03/11] arm64: dts: qcom: sa8295p-adp: " Krzysztof Kozlowski
2023-01-27 11:52 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 04/11] arm64: dts: qcom: sc7180: " Krzysztof Kozlowski
2023-01-27 11:52 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 05/11] arm64: dts: qcom: sc8280xp: " Krzysztof Kozlowski
2023-01-27 11:52 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 06/11] arm64: dts: qcom: sdm845: " Krzysztof Kozlowski
2023-01-27 11:53 ` Konrad Dybcio
2023-01-27 11:55 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 07/11] arm64: dts: qcom: sm7225: " Krzysztof Kozlowski
2023-01-27 11:56 ` Konrad Dybcio [this message]
2023-01-27 11:43 ` [PATCH 08/11] arm64: dts: qcom: sm8150: " Krzysztof Kozlowski
2023-01-27 11:56 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 09/11] arm64: dts: qcom: sm8250: " Krzysztof Kozlowski
2023-01-27 11:57 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 10/11] arm64: dts: qcom: sm8350: " Krzysztof Kozlowski
2023-01-27 11:57 ` Konrad Dybcio
2023-01-27 11:43 ` [PATCH 11/11] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2023-01-27 11:57 ` Konrad Dybcio
2023-01-27 11:51 ` [PATCH 01/11] ARM: dts: qcom-sdx55: " Konrad Dybcio
2023-02-09 4:23 ` (subset) " 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=573c9b6f-984f-add4-7792-1df848918b5d@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®