All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/5] arm64: dts: qcom: Add MSM8976 SoC support dts files
Date: Sun, 20 Oct 2019 22:52:07 -0700	[thread overview]
Message-ID: <20191021055207.GJ4500@tuxbook-pro> (raw)
In-Reply-To: <20191020150746.64114-5-kholk11@gmail.com>

On Sun 20 Oct 08:07 PDT 2019, kholk11@gmail.com wrote:
[..]
> diff --git a/arch/arm64/boot/dts/qcom/msm8976-pins.dtsi b/arch/arm64/boot/dts/qcom/msm8976-pins.dtsi
> new file mode 100644
> index 000000000000..1abeba8b8d18
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/msm8976-pins.dtsi
> @@ -0,0 +1,2119 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (c) 2014-2015, The Linux Foundation. All rights reserved.
> + * Copyright (c) 2016-2019 AngeloGioacchino Del Regno <kholk11@gmail.com>
> + */
> +
> +&tlmm {

Please inline this in msm8974.dtsi, it makes it easier to find nodes
than when they are sprinkled in various *pins.dtsi files.


Note also that a lot of these configs are specific to loire, rather than
msm8976. So preferably they should be specified there instead of in the
platform.

> +	cdc_reset_ctrl {
> +		cdc_reset_line_sus: cdc_reset_sleep {
> +			mux {

You don't have to split mux and config into subnodes (you don't even
need the last level subnode anymore)...

> +				pins = "gpio133";
> +				function = "gpio";
> +			};
> +			config {
> +				pins = "gpio133";
> +				drive-strength = <16>;
> +				bias-disable;
> +				output-low;
> +			};
> +		};
[..]
> diff --git a/arch/arm64/boot/dts/qcom/msm8976.dtsi b/arch/arm64/boot/dts/qcom/msm8976.dtsi
[..]
> +	firmware {
> +		scm: scm {
> +			compatible = "qcom,scm";

Please add a more specific compatible as well.

> +			clocks = <&gcc GCC_CRYPTO_CLK>,
> +				 <&gcc GCC_CRYPTO_AXI_CLK>,
> +				 <&gcc GCC_CRYPTO_AHB_CLK>;
> +			clock-names = "core", "bus", "iface";
> +			#reset-cells = <1>;
> +
> +			qcom,dload-mode = <&tcsr 0x6100>;
> +		};
> +	};
[..]
> +	smd {
> +		compatible = "qcom,smd";
> +
> +		rpm {
> +			interrupts = <GIC_SPI 168 IRQ_TYPE_EDGE_RISING>;
> +			qcom,ipc = <&apcs 8 0>;
> +			qcom,smd-edge = <15>;
> +
> +			rpm_requests {
> +				compatible = "qcom,rpm-msm8976";
> +				qcom,smd-channels = "rpm_requests";
> +
> +				rpmcc: qcom,rpmcc {
> +					compatible = "qcom,rpmcc-msm8976";
> +					#clock-cells = <1>;
> +				};
> +
> +				rpmpd: power-controller {
> +					compatible = "qcom,msm8976-rpmpd";
> +					#power-domain-cells = <1>;
> +					operating-points-v2 = <&rpmpd_opp_table>;
> +				};
> +
> +				smd_rpm_regulators: pm8950-regulators {

We've seen several times before where devices of a specific platform
comes with different set of pmics, so please omit the pmic configuration
from msm8976.dtsi, give rpm_requests a label and add these regulators in
the loire.dtsi

> +					compatible = "qcom,rpm-pm8950-regulators";
> +
> +					pm8950_s1: s1 {};
> +					pm8950_s2: s2 {};
> +					pm8950_s3: s3 {};
> +					pm8950_s4: s4 {};
> +					pm8950_s5: s5 {};
> +					pm8950_s6: s6 {};
> +
> +					pm8950_l1: l1 {};
> +					pm8950_l2: l2 {};
> +					pm8950_l3: l3 {};
> +					pm8950_l4: l4 {};
> +					pm8950_l5: l5 {};
> +					pm8950_l6: l6 {};
> +					pm8950_l7: l7 {};
> +					pm8950_l8: l8 {};
> +					pm8950_l9: l9 {};
> +					pm8950_l10: l10 {};
> +					pm8950_l11: l11 {};
> +					pm8950_l12: l12 {};
> +					pm8950_l13: l13 {};
> +					pm8950_l14: l14 {};
> +					pm8950_l15: l15 {};
> +					pm8950_l16: l16 {};
> +					pm8950_l17: l17 {};
> +					pm8950_l18: l18 {};
> +					pm8950_l19: l19 {};
> +					pm8950_l20: l20 {};
> +					pm8950_l21: l21 {};
> +					pm8950_l22: l22 {};
> +					pm8950_l23: l23 {};
> +				};
> +			};
> +		};
> +	};
> +
> +	soc: soc {
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		ranges = <0 0 0 0xffffffff>;
> +		compatible = "simple-bus";
> +
> +		tcsr_mutex_regs: syscon@1905000 {
> +			compatible = "syscon";
> +			reg = <0x1905000 0x20000>;

Please pad the address to 8 digits (to make it easier for me to see if
things are sorted) and please sort all nodes based on address and then
by name.

> +		};
[..]
> +		smsm {

Non-mmio nodes should not live under /soc, please move them to /.

> +			compatible = "qcom,smsm";
> +
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			qcom,ipc-1 = <&apcs 8 12>;
> +			qcom,ipc-2 = <&apcs 8 9>;
> +			qcom,ipc-3 = <&apcs 8 18>;
> +
> +			apps_smsm: apps@0 {
> +				reg = <0>;
> +				#qcom,smem-state-cells = <1>;
> +			};
> +
> +			hexagon_smsm: hexagon@1 {
> +				reg = <1>;
> +				interrupts = <0 290 IRQ_TYPE_EDGE_RISING>;
> +
> +				interrupt-controller;
> +				#interrupt-cells = <2>;
> +			};
> +
> +			wcnss_smsm: wcnss@6 {
> +				reg = <6>;
> +				interrupts = <GIC_SPI 144 IRQ_TYPE_EDGE_RISING>;
> +
> +				interrupt-controller;
> +				#interrupt-cells = <2>;
> +			};
> +		};
[..]
> +
> +		hexagon@4080000 {

remoteproc@4080000

> +			compatible = "qcom,q6v5-pil";
> +			reg = <0x04080000 0x100>,
> +			      <0x04020000 0x040>;
> +
> +			reg-names = "qdsp6", "rmb";
> +
> +			interrupts-extended = <&intc 0 293 1>,
> +					      <&adsp_smp2p_in 0 0>,

The compatible indicates that this is the modem, but this says "adsp".
Can you please confirm the Hexagon configuration on this platform?

> +					      <&adsp_smp2p_in 2 0>,
> +					      <&adsp_smp2p_in 1 0>,
> +					      <&adsp_smp2p_in 3 0>;
> +			interrupt-names = "wdog", "fatal", "ready",
> +					  "handover", "stop-ack";
> +

Regards,
Bjorn

  reply	other threads:[~2019-10-21  5:52 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
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 [this message]
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=20191021055207.GJ4500@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.