From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: kholk11@gmail.com
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
ccross@android.com, mark.rutland@arm.com, robh+dt@kernel.org,
agross@kernel.org, marijns95@gmail.com
Subject: Re: [PATCH 2/5] arm64: dts: pm8004: Add SPMI regulator and add phandles to lsids
Date: Sun, 20 Oct 2019 22:37:39 -0700 [thread overview]
Message-ID: <20191021053739.GH4500@tuxbook-pro> (raw)
In-Reply-To: <20191020150746.64114-3-kholk11@gmail.com>
On Sun 20 Oct 08:07 PDT 2019, kholk11@gmail.com wrote:
> From: AngeloGioacchino Del Regno <kholk11@gmail.com>
>
> Add the SPMI regulator node in the PM8004 LSID5 (as there is where
> it resides basically 99% of the times) and set the nodes to be
> disabled by default, as not all boards have both or one of the
> lsids specified in this generic pm8004 DT.
>
> While at it, also add nice phandles to the lsids specified in this
> DT, so that we can modify their configuration or add nodes to them
> from other DTs in a nicer and more human readable fashion.
>
Shouldn't all blocks of pm8004 be declared in this file?
> Signed-off-by: AngeloGioacchino Del Regno <kholk11@gmail.com>
> ---
> arch/arm64/boot/dts/qcom/pm8004.dtsi | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/pm8004.dtsi b/arch/arm64/boot/dts/qcom/pm8004.dtsi
> index 297b57bfa87a..0abd1abe12fc 100644
> --- a/arch/arm64/boot/dts/qcom/pm8004.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pm8004.dtsi
> @@ -4,17 +4,23 @@
>
> &spmi_bus {
>
> - pmic@4 {
> + pm8004_lsid4: pmic@4 {
> compatible = "qcom,pm8004", "qcom,spmi-pmic";
> reg = <0x4 SPMI_USID>;
> #address-cells = <1>;
> #size-cells = <0>;
> + status = "disabled";
I think you should just leave this enabled, boards that doesn't have a
pm8004 should be able to omit the include of this file.
> };
>
> - pmic@5 {
> + pm8004_lsid5: pmic@5 {
> compatible = "qcom,pm8004", "qcom,spmi-pmic";
> reg = <0x5 SPMI_USID>;
> #address-cells = <1>;
> #size-cells = <0>;
> + status = "disabled";
> +
> + pm8004_spmi_regulators: regulators {
> + compatible = "qcom,pm8004-regulators";
> + };
Looks good.
Regards,
bjorn
> };
> };
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-10-21 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 15:07 [PATCH 0/5] MSM8976/56 Sony Xperia Loire (X/XCompact) smartphones kholk11
2019-10-20 15:07 ` [PATCH 1/5] dt-bindings: iio: spmi-vadc: Add definitions for USB DP/DM VADCs kholk11
2019-10-29 15:28 ` Rob Herring
2019-10-20 15:07 ` [PATCH 2/5] arm64: dts: pm8004: Add SPMI regulator and add phandles to lsids kholk11
2019-10-21 5:37 ` Bjorn Andersson [this message]
2019-10-20 15:07 ` [PATCH 3/5] arm64: dts: qcom: Add configuration for PM8950 and PMI8950 peripherals kholk11
2019-10-21 5:38 ` Bjorn Andersson
2019-10-20 15:07 ` [PATCH 4/5] arm64: dts: qcom: Add MSM8976 SoC support dts files kholk11
2019-10-21 5:52 ` Bjorn Andersson
2019-10-21 7:50 ` AngeloGioacchino Del Regno
2019-10-20 15:07 ` [PATCH 5/5] arm64: dts: qcom: Add Sony Xperia (Loire) X and X Compact support kholk11
2019-10-21 6:04 ` 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=20191021053739.GH4500@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=ccross@android.com \
--cc=devicetree@vger.kernel.org \
--cc=kholk11@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijns95@gmail.com \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).