From: Rob Herring <robh@kernel.org>
To: Jacky Chou <jacky_chou@aspeedtech.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Po-Yu Chuang <ratbert@faraday-tech.com>,
Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, taoren@meta.com
Subject: Re: [PATCH net-next v5 1/4] dt-bindings: net: ftgmac100: Add delay properties for AST2600
Date: Tue, 9 Dec 2025 14:41:30 -0600 [thread overview]
Message-ID: <20251209204130.GA1056291-robh@kernel.org> (raw)
In-Reply-To: <20251205-rgmii_delay_2600-v5-1-bd2820ad3da7@aspeedtech.com>
On Fri, Dec 05, 2025 at 05:53:15PM +0800, Jacky Chou wrote:
> The AST2600 contains two dies, each with its own MAC, and these MACs
> require different delay configurations.
> Previously, these delay values were configured during the bootloader
> stage rather than in the driver. This change introduces the use of the
> standard properties defined in ethernet-controller.yaml to configure
> the delay values directly in the driver.
>
> Each Aspeed platform has its own delay step value. And for Aspeed platform,
> the total steps of RGMII delay configuraion is 32 steps, so the total delay
> is delay-step-ps * 32.
> Default delay values are declared so that tx-internal-delay-ps and
> rx-internal-delay-ps become optional. If these properties are not present,
> the driver will use the default values instead.
> Add conditional schema constraints for Aspeed AST2600 MAC controllers:
> - For MAC0/1, per delay step for rgmii is 45 ps
> - For MAC2/3, per delay step for rgmii is 250 ps
> - Both require the "aspeed,scu" and "aspeed,rgmii-delay-ps" properties.
> Other compatible values remain unrestricted.
>
> Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
> ---
> .../devicetree/bindings/net/faraday,ftgmac100.yaml | 27 ++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
> index d14410018bcf..00f7a0e56106 100644
> --- a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
> +++ b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
> @@ -69,6 +69,30 @@ properties:
> mdio:
> $ref: /schemas/net/mdio.yaml#
>
> + aspeed,scu:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Phandle to the SCU (System Control Unit) syscon node for Aspeed platform.
> + This reference is used by the MAC controller to configure the RGMII delays.
> +
> + rx-internal-delay-ps:
> + description:
> + RGMII Receive Clock Delay defined in pico seconds. There are 32
> + steps of RGMII delay for Aspeed platform. Each Aspeed platform has its
> + own delay step value, it is fixed by hardware design. Total delay is
> + calculated by delay-step * 32. A value of 0 ps will disable any
> + delay. The Default is no delay.
> + default: 0
> +
> + tx-internal-delay-ps:
> + description:
> + RGMII Transmit Clock Delay defined in pico seconds. There are 32
> + steps of RGMII delay for Aspeed platform. Each Aspeed platform has its
> + own delay step value, it is fixed by hardware design. Total delay is
> + calculated by delay-step * 32. A value of 0 ps will disable any
> + delay. The Default is no delay.
> + default: 0
> +
> required:
> - compatible
> - reg
> @@ -85,6 +109,9 @@ allOf:
> then:
> properties:
> resets: true
> + aspeed,scu: true
> + rx-internal-delay-ps: true
> + tx-internal-delay-ps: true
There is no need for these (including the 'resets'). Really, the 'if'
should be negated with a 'not' and this part dropped.
> else:
> properties:
> resets: false
But you need false entries here since these 3 properties are just for
ast2600.
Rob
next prev parent reply other threads:[~2025-12-09 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:53 [PATCH net-next v5 0/4] Add AST2600 RGMII delay into ftgmac100 Jacky Chou
2025-12-05 9:53 ` [PATCH net-next v5 1/4] dt-bindings: net: ftgmac100: Add delay properties for AST2600 Jacky Chou
2025-12-09 20:41 ` Rob Herring [this message]
2025-12-05 9:53 ` [PATCH net-next v5 2/4] ARM: dts: aspeed-g6: add aspeed,scu property for MAC Jacky Chou
2025-12-05 9:53 ` [PATCH net-next v5 3/4] net: ftgmac100: Add RGMII delay support for AST2600 Jacky Chou
2025-12-06 18:30 ` Andrew Lunn
2025-12-09 20:50 ` Rob Herring
2025-12-05 9:53 ` [PATCH net-next v5 4/4] ARM: dts: aspeed: ast2600-evb: Configure RGMII delay for MAC Jacky Chou
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=20251209204130.GA1056291-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ratbert@faraday-tech.com \
--cc=taoren@meta.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).