| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAH=2NtxHXi1nduzRtVZA5YfMjWeCxPCC-y6gwTbT5nYH+OxqGw@mail.gmail.com>
Date: Mon, 14 Jun 2021 13:49:07 +0530
From: Bhupesh Sharma <bhupesh.sharma@...aro.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: linux-arm-msm@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Vinod Koul <vkoul@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Andy Gross <agross@...nel.org>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
bhupesh.linux@...il.com
Subject: Re: [PATCH 8/8] arm64: dts: qcom: sa8155p-adp: Add base dts file
Hello Bjorn,
On Fri, 11 Jun 2021 at 07:55, Bjorn Andersson
<bjorn.andersson@...aro.org> wrote:
>
> On Mon 07 Jun 06:38 CDT 2021, Bhupesh Sharma wrote:
>
> > Add base DTS file for sa8155p-adp and enable boot to console,
>
> Please spell out "sa8155-adp", i.e. "Add base DTS for SA8155p Automotive
> Development Platform."
Ok, will do.
> > tlmm reserved range and also include pmic file(s).
> >
> > SA8155p-adp board is based on sm8150 Qualcomm Snapdragon SoC.
> >
>
> It's not based on sm8150, it's based on sa8155p, so let's express this
> as "The SA8155p platform is similar to the SM8150, so use this as base
> for now", to document why we decided to do this.
>
> > Cc: Linus Walleij <linus.walleij@...aro.org>
> > Cc: Liam Girdwood <lgirdwood@...il.com>
> > Cc: Mark Brown <broonie@...nel.org>
> > Cc: Bjorn Andersson <bjorn.andersson@...aro.org>
> > Cc: Vinod Koul <vkoul@...nel.org>
> > Cc: Rob Herring <robh+dt@...nel.org>
> > Cc: Andy Gross <agross@...nel.org>
> > Cc: devicetree@...r.kernel.org
> > Cc: linux-kernel@...r.kernel.org
> > Cc: linux-gpio@...r.kernel.org
> > Cc: bhupesh.linux@...il.com
>
> This would go into the git history as "I specifically asked for input
> from these people", so please keep this list shorter (but for a change
> like this it's probably better to omit it completely)
Ok, will keep it shorter for future series.
> > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@...aro.org>
> > ---
> > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > arch/arm64/boot/dts/qcom/sa8155p-adp.dts | 363 +++++++++++++++++++++++
> > 2 files changed, 364 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> >
> > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> > index 456502aeee49..38d3a4728871 100644
> > --- a/arch/arm64/boot/dts/qcom/Makefile
> > +++ b/arch/arm64/boot/dts/qcom/Makefile
> > @@ -71,6 +71,7 @@ dtb-$(CONFIG_ARCH_QCOM) += sdm845-xiaomi-beryllium.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm850-lenovo-yoga-c630.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8150-hdk.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8150-mtp.dtb
> > +dtb-$(CONFIG_ARCH_QCOM) += sa8155p-adp.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8250-hdk.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8250-mtp.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8350-hdk.dtb
> > diff --git a/arch/arm64/boot/dts/qcom/sa8155p-adp.dts b/arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> > new file mode 100644
> > index 000000000000..470d740e060a
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> > @@ -0,0 +1,363 @@
> > +// SPDX-License-Identifier: BSD-3-Clause
> > +/*
> > + * Copyright (c) 2021, Linaro Limited
> > + */
> > +
> > +/dts-v1/;
> > +
> > +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> > +#include <dt-bindings/gpio/gpio.h>
> > +#include "sm8150.dtsi"
> > +#include "pmm8155au_1.dtsi"
> > +#include "pmm8155au_2.dtsi"
> > +
> > +/ {
> > + model = "Qualcomm Technologies, Inc. SA8155P ADP";
> > + compatible = "qcom,sa8155p-adp";
> > +
> > + aliases {
> > + serial0 = &uart2;
> > + };
> > +
> > + chosen {
> > + stdout-path = "serial0:115200n8";
> > + };
> > +
> > + vreg_3p3: vreg_3p3_regulator {
> > + compatible = "regulator-fixed";
> > + regulator-name = "vreg_3p3";
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + };
> > +
> > + /*
> > + * Apparently RPMh does not provide support for PM8150 S4 because it
> > + * is always-on; model it as a fixed regulator.
> > + */
>
> You can reduce this to
>
> /* S4A is always on and not controllable through RPMh */
>
Ok, I wanted to keep it similar to the comment we have for sm815o-mtp,
but this is fine as well.
> > + vreg_s4a_1p8: smps4 {
> > + compatible = "regulator-fixed";
> > + regulator-name = "vreg_s4a_1p8";
> > +
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > +
> > + regulator-always-on;
> > + regulator-boot-on;
> > +
> > + vin-supply = <&vreg_3p3>;
> > + };
> > +};
> > +
> > +&apps_rsc {
> > + pmm8155au-1-rpmh-regulators {
> > + compatible = "qcom,pmm8155au-1-rpmh-regulators";
> > + qcom,pmic-id = "a";
> > +
> > + vdd-s1-supply = <&vreg_3p3>;
> > + vdd-s2-supply = <&vreg_3p3>;
> > + vdd-s3-supply = <&vreg_3p3>;
> > + vdd-s4-supply = <&vreg_3p3>;
> > + vdd-s5-supply = <&vreg_3p3>;
> > + vdd-s6-supply = <&vreg_3p3>;
> > + vdd-s7-supply = <&vreg_3p3>;
> > + vdd-s8-supply = <&vreg_3p3>;
> > + vdd-s9-supply = <&vreg_3p3>;
> > + vdd-s10-supply = <&vreg_3p3>;
> > +
> > + vdd-l1-l8-l11-supply = <&vreg_s6a_0p92>;
> > + vdd-l2-l10-supply = <&vreg_3p3>;
> > + vdd-l3-l4-l5-l18-supply = <&vreg_s6a_0p92>;
> > + vdd-l6-l9-supply = <&vreg_s6a_0p92>;
> > + vdd-l7-l12-l14-l15-supply = <&vreg_s5a_2p04>;
> > + vdd-l13-l16-l17-supply = <&vreg_3p3>;
> > +
> > + vreg_s5a_2p04: smps5 {
> > + regulator-min-microvolt = <1904000>;
> > + regulator-max-microvolt = <2000000>;
> > + };
> > +
> > + vreg_s6a_0p92: smps6 {
> > + regulator-min-microvolt = <920000>;
> > + regulator-max-microvolt = <1128000>;
> > + };
> > +
> > + vdda_wcss_pll:
>
> This is the "label" of the pad which the regulator typically is
> connected to (rather than a denotion of which regulator it is). So even
> though we have these in some of the other boards, I would prefer if you
> skip them and only use the vreg_xyz_abc variant.
Ok.
> > + vreg_l1a_0p752: ldo1 {
> > + regulator-min-microvolt = <752000>;
> > + regulator-max-microvolt = <752000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> [..]
> > +&usb_1_dwc3 {
> > + dr_mode = "peripheral";
>
> We have enough pieces to handle mode switching on this platform, but as
> discussed, lets leave it as "peripheral" until your local setup is back
> online.
Sure, in later patches, I can try playing more with this configuration.
Regards,
Bhupesh
Powered by blists - more mailing lists