All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Coia Prant" <coiaprant@gmail.com>
Cc: wsa+renesas@sang-engineering.com, vkoul@kernel.org,
	olteanv@gmail.com, linux-phy@lists.infradead.org,
	robh@kernel.org, conor+dt@kernel.org, neil.armstrong@linaro.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v9 05/11] arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes
Date: Mon, 21 Sep 2026 17:03:42 +0000	[thread overview]
Message-ID: <20260921170343.4CA421F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920170116.3624104-6-coiaprant@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] DT style violation: non-reg nodes placed out of order
--

commit 1674fcfaeba70039871d92af0a02901f9d009886
Author: Coia Prant <coiaprant@gmail.com>

arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes

This commit adds the Synopsys DesignWare XPCS and two fixed-clock nodes for
GMAC reference clocks to the RK3568 device tree. It places the nodes and adds
necessary properties for board-level configuration.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> index 3bc653f027f1f..227d03e336043 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
[ ... ]
> @@ -110,6 +110,51 @@ sata0: sata@fc000000 {
>  		status = "disabled";
>  	};
>  
> +	xpcs: ethernet-pcs@fda00000 {
[ ... ]
> +		xpcs_mii3: ethernet-pcs-mii@3 {
> +			reg = <3>;
> +			status = "disabled";
> +		};
> +	};
> +
> +	clk_gmac0_xpcs_mii: clock-xpcs-gmac0 {
> +		compatible = "fixed-clock";
> +		clock-frequency = <125000000>;
> +		clock-output-names = "clk_gmac0_xpcs_mii";
> +		#clock-cells = <0>;
> +	};
> +
> +	clk_gmac1_xpcs_mii: clock-xpcs-gmac1 {
> +		compatible = "fixed-clock";
> +		clock-frequency = <125000000>;
> +		clock-output-names = "clk_gmac1_xpcs_mii";
> +		#clock-cells = <0>;
> +	};

[Severity: Low]
According to standard Device Tree coding style guidelines
(Documentation/devicetree/bindings/dts-coding-style.rst), should nodes
without a 'reg' property be placed at the top of the file (or the top of
the root node) and sorted alphabetically, before any nodes with a 'reg'
property?

These clock-xpcs-gmac0 and clock-xpcs-gmac1 nodes in
arch/arm64/boot/dts/rockchip/rk3568.dtsi lack a 'reg' property but are
placed directly after ethernet-pcs@fda00000 and before syscon@fdc70000.

Could these be moved to the top of the root node alongside other non-reg
nodes like opp-table?

> +
>  	pipe_phy_grf0: syscon@fdc70000 {
>  		compatible = "rockchip,rk3568-pipe-phy-grf", "syscon";
>  		reg = <0x0 0xfdc70000 0x0 0x1000>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260920170116.3624104-1-coiaprant@gmail.com?part=5

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Coia Prant" <coiaprant@gmail.com>
Cc: wsa+renesas@sang-engineering.com, vkoul@kernel.org,
	olteanv@gmail.com, linux-phy@lists.infradead.org,
	robh@kernel.org, conor+dt@kernel.org, neil.armstrong@linaro.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v9 05/11] arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes
Date: Mon, 21 Sep 2026 17:03:42 +0000	[thread overview]
Message-ID: <20260921170343.4CA421F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260920170116.3624104-6-coiaprant@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] DT style violation: non-reg nodes placed out of order
--

commit 1674fcfaeba70039871d92af0a02901f9d009886
Author: Coia Prant <coiaprant@gmail.com>

arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes

This commit adds the Synopsys DesignWare XPCS and two fixed-clock nodes for
GMAC reference clocks to the RK3568 device tree. It places the nodes and adds
necessary properties for board-level configuration.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> index 3bc653f027f1f..227d03e336043 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3568.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3568.dtsi
[ ... ]
> @@ -110,6 +110,51 @@ sata0: sata@fc000000 {
>  		status = "disabled";
>  	};
>  
> +	xpcs: ethernet-pcs@fda00000 {
[ ... ]
> +		xpcs_mii3: ethernet-pcs-mii@3 {
> +			reg = <3>;
> +			status = "disabled";
> +		};
> +	};
> +
> +	clk_gmac0_xpcs_mii: clock-xpcs-gmac0 {
> +		compatible = "fixed-clock";
> +		clock-frequency = <125000000>;
> +		clock-output-names = "clk_gmac0_xpcs_mii";
> +		#clock-cells = <0>;
> +	};
> +
> +	clk_gmac1_xpcs_mii: clock-xpcs-gmac1 {
> +		compatible = "fixed-clock";
> +		clock-frequency = <125000000>;
> +		clock-output-names = "clk_gmac1_xpcs_mii";
> +		#clock-cells = <0>;
> +	};

[Severity: Low]
According to standard Device Tree coding style guidelines
(Documentation/devicetree/bindings/dts-coding-style.rst), should nodes
without a 'reg' property be placed at the top of the file (or the top of
the root node) and sorted alphabetically, before any nodes with a 'reg'
property?

These clock-xpcs-gmac0 and clock-xpcs-gmac1 nodes in
arch/arm64/boot/dts/rockchip/rk3568.dtsi lack a 'reg' property but are
placed directly after ethernet-pcs@fda00000 and before syscon@fdc70000.

Could these be moved to the top of the root node alongside other non-reg
nodes like opp-table?

> +
>  	pipe_phy_grf0: syscon@fdc70000 {
>  		compatible = "rockchip,rk3568-pipe-phy-grf", "syscon";
>  		reg = <0x0 0xfdc70000 0x0 0x1000>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260920170116.3624104-1-coiaprant@gmail.com?part=5

  reply	other threads:[~2026-09-21 17:03 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 17:01 [PATCH net-next v9 00/11] net: pcs: add basic support for RK3568 XPCS Coia Prant
2026-09-20 17:01 ` Coia Prant
2026-09-20 17:01 ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 01/11] net: stmmac: move XPCS lifetime management to platform drivers Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 02/11] dt-bindings: phy: rockchip: naneng-combphy: add rockchip,sgmii-mac-sel property Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 03/11] phy: rockchip: naneng-combphy: add SGMII MAC selection for RK3568 Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 04/11] dt-bindings: net: pcs: add rockchip,rk3568-xpcs support Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 05/11] arm64: dts: rockchip: rk3568: add XPCS and fixed-clock nodes Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-21 17:03   ` sashiko-bot [this message]
2026-09-21 17:03     ` sashiko-bot
2026-09-21 17:32     ` Coia Prant
2026-09-21 17:32       ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 06/11] net: pcs: xpcs: add ANRESTART support for SGMII link recovery Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 07/11] net: pcs: xpcs: add Rockchip RK3568 platform glue driver Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 08/11] dt-bindings: net: rockchip-dwmac: document pcs-handle Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 09/11] net: stmmac: dwmac-rk: add SGMII support for RK3568 Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 10/11] arm64: dts: rockchip: rk3568-photonicat: enable SGMII LAN port Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01 ` [PATCH net-next v9 11/11] MAINTAINERS: add entry for Rockchip XPCS driver Coia Prant
2026-09-20 17:01   ` Coia Prant
2026-09-20 17:01   ` Coia Prant

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=20260921170343.4CA421F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=coiaprant@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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.