[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <badce6b1-c614-4fc2-b3a2-5b1b5c011a80@lunn.ch>
Date: Tue, 21 Nov 2023 20:53:54 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: net: renesas,ethertsn: Add bindings for
Ethernet TSN
> > > + renesas,rx-internal-delay:
> > > + type: boolean
> > > + description:
> > > + Enable internal Rx clock delay, typically 1.8ns.
> >
> > Why this is bool, not delay in ns?
>
> The TSN is only capable of enabling or disable internal delays, not set
> how long the delay is. The documentation states that the delay depends
> on the electronic characteristics of the particular board, but states
> that they typically are 1.8ns for Rx and 2.0ns for Tx.
Do you have a board that actually requires this?
In general, we try to have the PHY add the delay, not the MAC. So i
would start with hard coding the delay to 0ns, and only implement
these properties if you have a board where the PHY cannot add the
delay.
Andrew
Powered by blists - more mailing lists