From: Luca Weiss <luca@z3ntu.xyz>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Vladimir Lypak <vladimir.lypak@gmail.com>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/15] arm64: dts: qcom: Add MSM8953+PM8953 device tree
Date: Sun, 13 Feb 2022 21:25:24 +0100 [thread overview]
Message-ID: <2497719.tdWV9SEqCh@g550jk> (raw)
In-Reply-To: <YfhlCkb3XUvU8ae1@builder.lan>
Hi Bjorn,
On Montag, 31. Jänner 2022 23:39:06 CET Bjorn Andersson wrote:
> On Wed 12 Jan 13:41 CST 2022, Luca Weiss wrote:
> > From: Vladimir Lypak <vladimir.lypak@gmail.com>
> >
> > The combination MSM8953 + PM8953 is commonly used, so add a
> > device tree where common power supplies etc. can be configured.
> >
> > Signed-off-by: Vladimir Lypak <vladimir.lypak@gmail.com>
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > Reviewed-by: Konrad Dybcio <konrad.dybcio@somainline.org>
>
> I would prefer if we stick with the current scheme and just push this
> into the device dts (or possibly some vendor-common dtsi if that's
> applicable).
>
> Simply just to follow what we do on other platforms.
Sure, will do in v2.
>
>
> PS. I see some patches has been applied, but as you resubmit this
> series please split it per maintainer to make it obvious to each
> maintainer that they should pick their part(s).
What do you mean by this? Send one series per maintainer? Or something else?
Currently when making the patches I don't really "care" about who maintains
what, my git send-email setup picks the relevant people for CC.
Sometimes there's also multiple maintainers/trees listed for one file, not sure
what to do there...
Regards
Luca
>
> Thanks,
> Bjorn
>
> > ---
> >
> > arch/arm64/boot/dts/qcom/msm8953-pm8953.dtsi | 50 ++++++++++++++++++++
> > 1 file changed, 50 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/qcom/msm8953-pm8953.dtsi
> >
> > diff --git a/arch/arm64/boot/dts/qcom/msm8953-pm8953.dtsi
> > b/arch/arm64/boot/dts/qcom/msm8953-pm8953.dtsi new file mode 100644
> > index 000000000000..b5f20fc9488e
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/qcom/msm8953-pm8953.dtsi
> > @@ -0,0 +1,50 @@
> > +// SPDX-License-Identifier: BSD-3-Clause
> > +/* Copyright (c) 2022, The Linux Foundation. All rights reserved. */
> > +
> > +#include "msm8953.dtsi"
> > +#include "pm8953.dtsi"
> > +
> > +&hsusb_phy {
> > + vdd-supply = <&pm8953_l3>;
> > + vdda-pll-supply = <&pm8953_l7>;
> > + vdda-phy-dpdm-supply = <&pm8953_l13>;
> > +};
> > +
> > +&sdhc_1 {
> > + vmmc-supply = <&pm8953_l8>;
> > + vqmmc-supply = <&pm8953_l5>;
> > +};
> > +
> > +&sdhc_2 {
> > + vmmc-supply = <&pm8953_l11>;
> > + vqmmc-supply = <&pm8953_l12>;
> > +};
> > +
> > +&rpm_requests {
> > + smd_rpm_regulators: pm8953-regulators {
> > + compatible = "qcom,rpm-pm8953-regulators";
> > +
> > + pm8953_s1: s1 {};
> > + pm8953_s3: s3 {};
> > + pm8953_s4: s4 {};
> > +
> > + pm8953_l1: l1 {};
> > + pm8953_l2: l2 {};
> > + pm8953_l3: l3 {};
> > + pm8953_l5: l5 {};
> > + pm8953_l6: l6 {};
> > + pm8953_l7: l7 {};
> > + pm8953_l8: l8 {};
> > + pm8953_l9: l9 {};
> > + pm8953_l10: l10 {};
> > + pm8953_l11: l11 {};
> > + pm8953_l12: l12 {};
> > + pm8953_l13: l13 {};
> > + pm8953_l15: l15 {};
> > + pm8953_l16: l16 {};
> > + pm8953_l17: l17 {};
> > + pm8953_l19: l19 {};
> > + pm8953_l22: l22 {};
> > + pm8953_l23: l23 {};
> > + };
> > +};
next prev parent reply other threads:[~2022-02-13 20:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 19:40 [PATCH 00/15] Initial MSM8953 & Fairphone 3 support Luca Weiss
2022-01-12 19:40 ` [PATCH 01/15] dt-bindings: phy: qcom,qusb2: Document msm8953 compatible Luca Weiss
2022-01-27 5:30 ` Vinod Koul
2022-01-12 19:40 ` [PATCH 02/15] phy: qcom-qusb2: Add compatible for MSM8953 Luca Weiss
2022-01-27 5:30 ` Vinod Koul
2022-01-12 19:40 ` [PATCH 03/15] dt-bindings: mfd: qcom,tcsr: Document msm8953 compatible Luca Weiss
2022-02-09 2:12 ` Rob Herring
2022-02-15 12:58 ` Lee Jones
2022-01-12 19:40 ` [PATCH 04/15] mfd: qcom-spmi-pmic: Add pm8953 compatible Luca Weiss
2022-02-09 2:12 ` Rob Herring
2022-02-15 12:59 ` Lee Jones
2022-01-12 19:40 ` [PATCH 05/15] dt-bindings: mmc: sdhci-msm: Add msm8953 compatible Luca Weiss
2022-01-24 14:41 ` Ulf Hansson
2022-01-12 19:40 ` [PATCH 06/15] dt-bindings: thermal: tsens: " Luca Weiss
2022-01-20 10:58 ` Amit Kucheria
2022-02-09 2:13 ` Rob Herring
2022-01-12 19:40 ` [PATCH 07/15] dt-bindings: usb: qcom,dwc3: " Luca Weiss
2022-02-09 2:13 ` Rob Herring
2022-01-12 19:40 ` [PATCH 08/15] dt-bindings: pinctrl: qcom: msm8953: allow gpio-reserved-ranges Luca Weiss
2022-02-09 2:14 ` Rob Herring
2022-02-11 0:06 ` Linus Walleij
2022-01-12 19:40 ` [PATCH 09/15] rpmsg: smd: Drop unnecessary condition for channel creation Luca Weiss
2022-01-12 21:39 ` Stephan Gerhold
2022-01-16 16:08 ` Luca Weiss
2022-01-16 16:30 ` Stephan Gerhold
2022-01-31 22:32 ` Bjorn Andersson
2022-02-06 20:17 ` Luca Weiss
2022-02-13 20:51 ` Luca Weiss
2022-02-15 15:34 ` Bjorn Andersson
2022-01-31 22:34 ` Bjorn Andersson
2022-01-12 19:40 ` [PATCH 10/15] arm64: dts: qcom: Add MSM8953 device tree Luca Weiss
2022-02-15 16:40 ` Bjorn Andersson
2022-02-19 11:50 ` Luca Weiss
2022-01-12 19:41 ` [PATCH 11/15] arm64: dts: qcom: Add PM8953 PMIC Luca Weiss
2022-02-07 21:08 ` rayyan
2022-02-09 16:19 ` Rayyan Ansari
2022-01-12 19:41 ` [PATCH 12/15] arm64: dts: qcom: Add SDM632 device tree Luca Weiss
2022-02-15 16:31 ` Bjorn Andersson
2022-01-12 19:41 ` [PATCH 13/15] arm64: dts: qcom: Add MSM8953+PM8953 " Luca Weiss
2022-01-31 22:39 ` Bjorn Andersson
2022-02-13 20:25 ` Luca Weiss [this message]
2022-02-14 4:59 ` Bjorn Andersson
2022-01-12 19:41 ` [PATCH 14/15] dt-bindings: arm: qcom: Document sdm632 and fairphone,fp3 board Luca Weiss
2022-02-09 2:14 ` Rob Herring
2022-01-12 19:41 ` [PATCH 15/15] arm64: dts: qcom: sdm632: Add device tree for Fairphone 3 Luca Weiss
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=2497719.tdWV9SEqCh@g550jk \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vladimir.lypak@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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