From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: renesas,ethertsn: Add bindings for Ethernet TSN
Date: Tue, 21 Nov 2023 13:44:20 +0100 [thread overview]
Message-ID: <ZVymJF2dd7XssGaQ@oden.dyn.berto.se> (raw)
In-Reply-To: <2ffb39c3-7939-46f2-8ca9-2b2cb44caaff@linaro.org>
Hello Krzysztof,
On 2023-11-21 13:20:54 +0100, Krzysztof Kozlowski wrote:
> On 21/11/2023 13:10, Niklas Söderlund wrote:
> >>> +
> >>> + 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.
>
> I don't understand that part. If you cannot configure the internal
> delay, how could it depend on the board characteristics?
Each of these two properties reflect a single bit in the device
configuration space. If the bit is set the {Rx,Tx} delay mode is active
or disabled. The documentation for the bit simply states,
Tx clock internal Delay Mode
This bit can add internal Tx clock delay typ 2.0ns*.
*Refer to Electrical Characteristics for details.
Same paragraph for Rx but a typical 1.8ns delay.
>
> >
> > I looked at the generic properties {rx,tx}-internal-delay-ps but they
> > are of int type. So I opted for a vendor specific bool property. Do you
> > think a better route is to use the generic property and force the value
> > to be either 0 or the typical delay?
> >
> >> Why this is property of a board (not SoC)?
> >
> > I'm sorry I don't understand this question.
>
> Why setting internal delay is specific to a board, not to a SoC? Why
> each board would need to configure it? On which parts of hardware on the
> board does this depend?
Ahh, I think I understand. It is per board as I understand the
documentation. It depends on the electrical characteristics of the
board.
Maybe updating the description would help, how about?
Enable internal Rx clock delay. Typically 1.8ns but depends on
electrical characteristics of the board.
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2023-11-21 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 16:07 [PATCH] dt-bindings: net: renesas,ethertsn: Add bindings for Ethernet TSN Niklas Söderlund
2023-11-21 7:45 ` Krzysztof Kozlowski
2023-11-21 8:00 ` Geert Uytterhoeven
2023-11-21 8:40 ` Krzysztof Kozlowski
2023-11-21 8:45 ` Geert Uytterhoeven
2023-11-21 12:11 ` Niklas Söderlund
2023-11-21 12:10 ` Niklas Söderlund
2023-11-21 12:20 ` Krzysztof Kozlowski
2023-11-21 12:44 ` Niklas Söderlund [this message]
2023-11-21 12:53 ` Krzysztof Kozlowski
2023-11-21 16:11 ` Geert Uytterhoeven
2023-11-21 16:32 ` Niklas Söderlund
2023-11-21 19:53 ` Andrew Lunn
2023-11-22 7:40 ` Geert Uytterhoeven
2023-11-22 13:57 ` Andrew Lunn
2023-11-22 15:41 ` Geert Uytterhoeven
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=ZVymJF2dd7XssGaQ@oden.dyn.berto.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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 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).