linux-kernel - Re: [PATCH 1/3] ARM: dts: qcom: ipq8064: add v2 dtsi variant

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 8 Aug 2022 15:35:42 +0200
From:   Christian Marangi <ansuelsmth@...il.com>
To:     Konrad Dybcio <konrad.dybcio@...ainline.org>
Cc:     Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: qcom: ipq8064: add v2 dtsi variant

On Mon, Aug 08, 2022 at 12:55:36PM +0200, Konrad Dybcio wrote:
> 
> 
> On 7.08.2022 15:00, Christian Marangi wrote:
> > On Mon, Jul 18, 2022 at 06:18:24PM +0200, Christian Marangi wrote:
> >> Add ipq8064-v2.0 dtsi variant that differ from original ipq8064 SoC for
> >> some additional pcie, sata and usb configuration values, additional
> >> reserved memory and serial output.
> >>
> >> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>
> > 
> > Any news for this?Unless Qualcomm naming was different back then, you should simply merge
> all of these changes into ipq8064.dtsi, as v1 is often the pre-production,
> internal chip revision and only the last one (or the last and second-last)
> are shipped in production devices.
>

Mhh, this is not the case, there are dev board based on v1 and we also
have some device based on v1 (that have some difference for pci and usb)
One example is a Netgear r7500 where we have 2 revision one based on
ipq8064-v1.0 and one based on ipq8064-v2.0.

> > 
> >> ---
> >>  .../boot/dts/qcom-ipq8064-v2.0-smb208.dtsi    | 37 ++++++++++
> >>  arch/arm/boot/dts/qcom-ipq8064-v2.0.dtsi      | 69 +++++++++++++++++++
> >>  2 files changed, 106 insertions(+)
> >>  create mode 100644 arch/arm/boot/dts/qcom-ipq8064-v2.0-smb208.dtsi
> >>  create mode 100644 arch/arm/boot/dts/qcom-ipq8064-v2.0.dtsi
> >>
> >> diff --git a/arch/arm/boot/dts/qcom-ipq8064-v2.0-smb208.dtsi b/arch/arm/boot/dts/qcom-ipq8064-v2.0-smb208.dtsi
> >> new file mode 100644
> >> index 000000000000..0442580b22de
> >> --- /dev/null
> >> +++ b/arch/arm/boot/dts/qcom-ipq8064-v2.0-smb208.dtsi
> >> @@ -0,0 +1,37 @@
> >> +// SPDX-License-Identifier: GPL-2.0
> >> +
> >> +#include "qcom-ipq8064-v2.0.dtsi"
> >> +
> >> +&rpm {
> >> +	smb208_regulators: regulators {
> >> +		compatible = "qcom,rpm-smb208-regulators";
> >> +
> >> +		smb208_s1a: s1a {
> >> +			regulator-min-microvolt = <1050000>;
> >> +			regulator-max-microvolt = <1150000>;
> >> +
> >> +			qcom,switch-mode-frequency = <1200000>;
> >> +		};
> >> +
> >> +		smb208_s1b: s1b {
> >> +			regulator-min-microvolt = <1050000>;
> >> +			regulator-max-microvolt = <1150000>;
> >> +
> >> +			qcom,switch-mode-frequency = <1200000>;
> >> +		};
> >> +
> >> +		smb208_s2a: s2a {
> >> +			regulator-min-microvolt = < 800000>;
> >> +			regulator-max-microvolt = <1250000>;
> >> +
> >> +			qcom,switch-mode-frequency = <1200000>;
> >> +		};
> >> +
> >> +		smb208_s2b: s2b {
> >> +			regulator-min-microvolt = < 800000>;
> >> +			regulator-max-microvolt = <1250000>;
> >> +
> >> +			qcom,switch-mode-frequency = <1200000>;
> >> +		};
> >> +	};
> >> +};
> >> diff --git a/arch/arm/boot/dts/qcom-ipq8064-v2.0.dtsi b/arch/arm/boot/dts/qcom-ipq8064-v2.0.dtsi
> >> new file mode 100644
> >> index 000000000000..2f117d576daf
> >> --- /dev/null
> >> +++ b/arch/arm/boot/dts/qcom-ipq8064-v2.0.dtsi
> >> @@ -0,0 +1,69 @@
> >> +// SPDX-License-Identifier: GPL-2.0
> >> +
> >> +#include "qcom-ipq8064.dtsi"
> >> +
> >> +/ {
> >> +	model = "Qualcomm Technologies, Inc. IPQ8064-v2.0";
> >> +
> >> +	aliases {
> >> +		serial0 = &gsbi4_serial;
> >> +	};
> >> +
> >> +	chosen {
> >> +		stdout-path = "serial0:115200n8";
> >> +	};
> >> +
> >> +	reserved-memory {
> >> +		#address-cells = <1>;
> >> +		#size-cells = <1>;
> >> +		ranges;
> >> +
> >> +		rsvd@...00000 {
> >> +			reg = <0x41200000 0x300000>;
> >> +			no-map;
> >> +		};
> >> +	};
> >> +};
> >> +
> >> +&gsbi4 {
> >> +	qcom,mode = <GSBI_PROT_I2C_UART>;
> >> +	status = "okay";
> >> +
> >> +	serial@...40000 {
> >> +		status = "okay";
> >> +	};
> >> +	/*
> >> +	 * The i2c device on gsbi4 should not be enabled.
> >> +	 * On ipq806x designs gsbi4 i2c is meant for exclusive
> >> +	 * RPM usage. Turning this on in kernel manifests as
> >> +	 * i2c failure for the RPM.
> >> +	 */
> >> +};
> >> +
> >> +&pcie0 {
> >> +	compatible = "qcom,pcie-ipq8064-v2";
> >> +};
> >> +
> >> +&pcie1 {
> >> +	compatible = "qcom,pcie-ipq8064-v2";
> >> +};
> >> +
> >> +&pcie2 {
> >> +	compatible = "qcom,pcie-ipq8064-v2";
> >> +};
> >> +
> >> +&sata {
> >> +	ports-implemented = <0x1>;
> >> +};
> >> +
> >> +&ss_phy_0 {
> >> +	qcom,rx-eq = <2>;
> >> +	qcom,tx-deamp_3_5db = <32>;
> >> +	qcom,mpll = <5>;
> >> +};
> >> +
> >> +&ss_phy_1 {
> >> +	qcom,rx-eq = <2>;
> >> +	qcom,tx-deamp_3_5db = <32>;
> >> +	qcom,mpll = <5>;
> >> +};
> >> -- 
> >> 2.36.1
> >>
> > 

-- 
	Ansuel