From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Robert Marko <robimarko@gmail.com>,
agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: qcom: ipq4019-ap.dk01.1: use existing labels for nodes
Date: Fri, 11 Aug 2023 23:27:16 +0200 [thread overview]
Message-ID: <52fada0e-eb54-48de-88a9-0747a15ed1ce@linaro.org> (raw)
In-Reply-To: <20230811210142.403160-1-robimarko@gmail.com>
On 11.08.2023 23:01, Robert Marko wrote:
> All of the nodes under soc already have existing labels so use those
> instead.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
dtx_diff returns an empty diff, nice
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Couple further suggestions:
- wdog can probably enabled unconditionally
- same for blsp dma since there's only one host so it must be
used by something
- same for crypto engine as it's a common piece of hw
- you can drop mux{}, pinmux{}, pinconf{} from pin nodes, just add
the properties directly under the pin nodes
- this devicetree could use some schema warnings cleanup (make dtbs_check
plus things like no underscores in node names)
Konrad
> .../boot/dts/qcom/qcom-ipq4019-ap.dk01.1.dtsi | 140 +++++++++---------
> 1 file changed, 69 insertions(+), 71 deletions(-)
>
> diff --git a/arch/arm/boot/dts/qcom/qcom-ipq4019-ap.dk01.1.dtsi b/arch/arm/boot/dts/qcom/qcom-ipq4019-ap.dk01.1.dtsi
> index 0505270cf508..0714616c9e45 100644
> --- a/arch/arm/boot/dts/qcom/qcom-ipq4019-ap.dk01.1.dtsi
> +++ b/arch/arm/boot/dts/qcom/qcom-ipq4019-ap.dk01.1.dtsi
> @@ -27,87 +27,85 @@ aliases {
> chosen {
> stdout-path = "serial0:115200n8";
> };
> +};
>
> - soc {
> - rng@22000 {
> - status = "okay";
> - };
> +&prng {
> + status = "okay";
> +};
>
> - pinctrl@1000000 {
> - serial_pins: serial_pinmux {
> - mux {
> - pins = "gpio60", "gpio61";
> - function = "blsp_uart0";
> - bias-disable;
> - };
> - };
> -
> - spi_0_pins: spi_0_pinmux {
> - pinmux {
> - function = "blsp_spi0";
> - pins = "gpio55", "gpio56", "gpio57";
> - };
> - pinmux_cs {
> - function = "gpio";
> - pins = "gpio54";
> - };
> - pinconf {
> - pins = "gpio55", "gpio56", "gpio57";
> - drive-strength = <12>;
> - bias-disable;
> - };
> - pinconf_cs {
> - pins = "gpio54";
> - drive-strength = <2>;
> - bias-disable;
> - output-high;
> - };
> - };
> +&tlmm {
> + serial_pins: serial_pinmux {
> + mux {
> + pins = "gpio60", "gpio61";
> + function = "blsp_uart0";
> + bias-disable;
> };
> + };
>
> - blsp_dma: dma-controller@7884000 {
> - status = "okay";
> + spi_0_pins: spi_0_pinmux {
> + pinmux {
> + function = "blsp_spi0";
> + pins = "gpio55", "gpio56", "gpio57";
> };
> -
> - spi@78b5000 {
> - pinctrl-0 = <&spi_0_pins>;
> - pinctrl-names = "default";
> - status = "okay";
> - cs-gpios = <&tlmm 54 GPIO_ACTIVE_HIGH>;
> -
> - mx25l25635e@0 {
> - #address-cells = <1>;
> - #size-cells = <1>;
> - reg = <0>;
> - compatible = "mx25l25635e";
> - spi-max-frequency = <24000000>;
> - };
> + pinmux_cs {
> + function = "gpio";
> + pins = "gpio54";
> };
> -
> - serial@78af000 {
> - pinctrl-0 = <&serial_pins>;
> - pinctrl-names = "default";
> - status = "okay";
> + pinconf {
> + pins = "gpio55", "gpio56", "gpio57";
> + drive-strength = <12>;
> + bias-disable;
> };
> -
> - cryptobam: dma-controller@8e04000 {
> - status = "okay";
> + pinconf_cs {
> + pins = "gpio54";
> + drive-strength = <2>;
> + bias-disable;
> + output-high;
> };
> + };
> +};
>
> - crypto@8e3a000 {
> - status = "okay";
> - };
> +&blsp_dma {
> + status = "okay";
> +};
>
> - watchdog@b017000 {
> - status = "okay";
> - };
> +&blsp1_spi1 {
> + pinctrl-0 = <&spi_0_pins>;
> + pinctrl-names = "default";
> + status = "okay";
> + cs-gpios = <&tlmm 54 GPIO_ACTIVE_HIGH>;
> +
> + mx25l25635e@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0>;
> + compatible = "mx25l25635e";
> + spi-max-frequency = <24000000>;
> + };
> +};
>
> - wifi@a000000 {
> - status = "okay";
> - };
> +&blsp1_uart1 {
> + pinctrl-0 = <&serial_pins>;
> + pinctrl-names = "default";
> + status = "okay";
> +};
>
> - wifi@a800000 {
> - status = "okay";
> - };
> - };
> +&cryptobam {
> + status = "okay";
> +};
> +
> +&crypto {
> + status = "okay";
> +};
> +
> +&watchdog {
> + status = "okay";
> +};
> +
> +&wifi0 {
> + status = "okay";
> +};
> +
> +&wifi1 {
> + status = "okay";
> };
next prev parent reply other threads:[~2023-08-11 21:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 21:01 [PATCH 1/2] ARM: dts: qcom: ipq4019-ap.dk01.1: use existing labels for nodes Robert Marko
2023-08-11 21:01 ` [PATCH 2/2] ARM: dts: qcom: ipq4019-ap.dk01.1: align flash node with bindings Robert Marko
2023-08-11 21:28 ` Konrad Dybcio
2023-08-11 21:35 ` Robert Marko
2023-08-11 22:56 ` Konrad Dybcio
2023-08-12 9:55 ` Robert Marko
2023-08-12 10:47 ` Konrad Dybcio
2023-08-12 14:07 ` Robert Marko
2023-08-12 14:08 ` Konrad Dybcio
2023-08-12 14:12 ` Robert Marko
2023-08-12 14:15 ` Konrad Dybcio
2023-08-14 10:54 ` Robert Marko
2023-08-11 21:27 ` Konrad Dybcio [this message]
2023-08-11 21:38 ` [PATCH 1/2] ARM: dts: qcom: ipq4019-ap.dk01.1: use existing labels for nodes Robert Marko
2024-01-28 17:45 ` (subset) " 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=52fada0e-eb54-48de-88a9-0747a15ed1ce@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
/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).