From: Heiko Stuebner <heiko@sntech.de>
To: John Clark <inindev@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, John Clark <inindev@gmail.com>
Subject: Re: [PATCH v1 2/2] arm64: dts: rockchip: Add FriendlyElec NanoPi M5 support
Date: Fri, 20 Jun 2025 11:12:29 +0200 [thread overview]
Message-ID: <2432603.PIDvDuAF1L@phil> (raw)
In-Reply-To: <20250616212214.139585-3-inindev@gmail.com>
Hi,
Am Montag, 16. Juni 2025, 23:22:14 Mitteleuropäische Sommerzeit schrieb John Clark:
> Add device tree for FriendlyElec NanoPi M5 with Rockchip RK3576 SoC
> (4x Cortex-A72, 4x Cortex-A53, Mali-G52 MC3 GPU, 6 TOPS NPU). Enables
> basic booting and connectivity.
>
> Supported features:
> - RK3576 SoC
> - 4GB/8GB/16GB LPDDR4X/LPDDR5 RAM
> - 16MB SPI Nor Flash
> - 2x 1Gbps Ethernet
> - 2x USB 3.2 Gen 1 Type-A ports
> - microSD UHS-I
> - M.2 M-Key PCIe 2.1 x1 NVMe support
> - HDMI 1.4/2.0 (up to 4096x2304@60Hz)
> - 30-pin GPIO (2x SPI, 4x UART, 3x I2C, 5x PWM, 20x GPIO)
> - Debug UART
> - RTC with HYM8563TS
> - Power via USB-C (PD, 6V~20V)
>
> Signed-off-by: John Clark <inindev@gmail.com>
> ---
apart from the schema problems, Rob's bot found, I saw some additional
nitpicks below.
[...]
> + sound {
[...]
> + };
> +
> + vcc_12v_dcin: regulator-vcc-12v-dcin {
nodes without addresses should get sorted by nodename
aka regulator-* before sound.
Phandles count into the sorting only below in the
&phandle {}; parts
> + compatible = "regulator-fixed";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <12000000>;
> + regulator-max-microvolt = <12000000>;
> + regulator-name = "vcc_12v_dcin";
blank lines between properties and subnodes please.
same for other regulators below and also the pmic.
> + regulator-state-mem {
> + regulator-on-in-suspend;
> + };
> + };
> +
> +&fspi1m1_pins {
> + rockchip,pins =
> + /* clk, d0~4 */
comment could state a tiny bit more what is changed compared to
the "original" pin settings
> + <1 RK_PD5 3 &pcfg_pull_none>,
> + <1 RK_PC4 3 &pcfg_pull_none>,
> + <1 RK_PC5 3 &pcfg_pull_none>,
> + <1 RK_PC6 3 &pcfg_pull_none>,
> + <1 RK_PC7 3 &pcfg_pull_none>;
> +};
> +&saradc {
> + status = "okay";
> + vref-supply = <&vcca_1v8_s0>;
status is the last property
> +};
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: John Clark <inindev@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, John Clark <inindev@gmail.com>
Subject: Re: [PATCH v1 2/2] arm64: dts: rockchip: Add FriendlyElec NanoPi M5 support
Date: Fri, 20 Jun 2025 11:12:29 +0200 [thread overview]
Message-ID: <2432603.PIDvDuAF1L@phil> (raw)
In-Reply-To: <20250616212214.139585-3-inindev@gmail.com>
Hi,
Am Montag, 16. Juni 2025, 23:22:14 Mitteleuropäische Sommerzeit schrieb John Clark:
> Add device tree for FriendlyElec NanoPi M5 with Rockchip RK3576 SoC
> (4x Cortex-A72, 4x Cortex-A53, Mali-G52 MC3 GPU, 6 TOPS NPU). Enables
> basic booting and connectivity.
>
> Supported features:
> - RK3576 SoC
> - 4GB/8GB/16GB LPDDR4X/LPDDR5 RAM
> - 16MB SPI Nor Flash
> - 2x 1Gbps Ethernet
> - 2x USB 3.2 Gen 1 Type-A ports
> - microSD UHS-I
> - M.2 M-Key PCIe 2.1 x1 NVMe support
> - HDMI 1.4/2.0 (up to 4096x2304@60Hz)
> - 30-pin GPIO (2x SPI, 4x UART, 3x I2C, 5x PWM, 20x GPIO)
> - Debug UART
> - RTC with HYM8563TS
> - Power via USB-C (PD, 6V~20V)
>
> Signed-off-by: John Clark <inindev@gmail.com>
> ---
apart from the schema problems, Rob's bot found, I saw some additional
nitpicks below.
[...]
> + sound {
[...]
> + };
> +
> + vcc_12v_dcin: regulator-vcc-12v-dcin {
nodes without addresses should get sorted by nodename
aka regulator-* before sound.
Phandles count into the sorting only below in the
&phandle {}; parts
> + compatible = "regulator-fixed";
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-min-microvolt = <12000000>;
> + regulator-max-microvolt = <12000000>;
> + regulator-name = "vcc_12v_dcin";
blank lines between properties and subnodes please.
same for other regulators below and also the pmic.
> + regulator-state-mem {
> + regulator-on-in-suspend;
> + };
> + };
> +
> +&fspi1m1_pins {
> + rockchip,pins =
> + /* clk, d0~4 */
comment could state a tiny bit more what is changed compared to
the "original" pin settings
> + <1 RK_PD5 3 &pcfg_pull_none>,
> + <1 RK_PC4 3 &pcfg_pull_none>,
> + <1 RK_PC5 3 &pcfg_pull_none>,
> + <1 RK_PC6 3 &pcfg_pull_none>,
> + <1 RK_PC7 3 &pcfg_pull_none>;
> +};
> +&saradc {
> + status = "okay";
> + vref-supply = <&vcca_1v8_s0>;
status is the last property
> +};
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-06-20 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 21:22 [PATCH v1 0/2] Add FriendlyElec NanoPi M5 support for Rockchip RK3576 John Clark
2025-06-16 21:22 ` John Clark
2025-06-16 21:22 ` [PATCH v1 1/2] dt-bindings: arm: rockchip: add FriendlyElec NanoPi M5 board John Clark
2025-06-16 21:22 ` John Clark
2025-06-16 21:22 ` [PATCH v1 2/2] arm64: dts: rockchip: Add FriendlyElec NanoPi M5 support John Clark
2025-06-16 21:22 ` John Clark
2025-06-20 9:12 ` Heiko Stuebner [this message]
2025-06-20 9:12 ` Heiko Stuebner
2025-06-17 14:20 ` [PATCH v1 0/2] Add FriendlyElec NanoPi M5 support for Rockchip RK3576 Rob Herring (Arm)
2025-06-17 14:20 ` Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-06-17 17:21 [PATCH v1 2/2] arm64: dts: rockchip: Add FriendlyElec NanoPi M5 support kernel test robot
2025-06-17 19:17 kernel test robot
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=2432603.PIDvDuAF1L@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inindev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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.