public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anshul Dalal <anshuld@ti.com>
To: <s-vadapalli@ti.com>
Cc: <jerome.forissier@arm.com>, <srk@ti.com>, <trini@konsulko.com>,
	<u-boot@lists.denx.de>, Anshul Dalal <anshuld@ti.com>
Subject: Re: [PATCH] net: phy: dp83867: default to 2ns delay if unspecified in device-tree
Date: Thu, 9 Apr 2026 12:57:00 +0530	[thread overview]
Message-ID: <20260409072659.509356-2-anshuld@ti.com> (raw)
In-Reply-To: <20260406124559.2481344-1-s-vadapalli@ti.com>

On Mon, 06 Apr 2026 18:15:57 +0530, Siddharth Vadapalli <s-vadapalli@ti.com> wrote:
> Since Linux commit c360eb0c3ccb ("dt-bindings: net: ethernet-controller:
> Add informative text about RGMII delays"), the interpretation of RGMII
> delays has changed. Prior to the commit, the RGMII Variant among "rgmii",
> "rgmii-id", "rgmii-rxid" and "rgmii-txid" clearly specified whether it is
> the MAC or the PHY that "should" add the delay. However, post that commit,
> the RGMII Variant only specifies whether or not there is a delay on the
> PCB traces between the MAC and the PHY, leaving it open as to who adds the
> delay.
> 
> Hence, instead of enforcing the existence of the device-tree properties
> "ti,rx-internal-delay" and "ti,tx-internal-delay", default to a delay
> of 2ns, while continuing to override this delay with the aforementioned
> properties, if they exist in the device-tree.
> 
> This is in line with the Linux driver implementation updated by commit
> 6bf78849371d ("net: phy: dp83867: use 2ns delay if not specified in DTB").
> 
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>

Reviewed-by: Anshul Dalal <anshuld@ti.com>

--
Anshul Dalal <anshuld@ti.com>

      reply	other threads:[~2026-04-09  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 12:45 [PATCH] net: phy: dp83867: default to 2ns delay if unspecified in device-tree Siddharth Vadapalli
2026-04-09  7:27 ` Anshul Dalal [this message]

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=20260409072659.509356-2-anshuld@ti.com \
    --to=anshuld@ti.com \
    --cc=jerome.forissier@arm.com \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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