mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
	 Michael Walle <mwalle@kernel.org>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>,
	 Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
	 Andrew Lunn <andrew@lunn.ch>,
	linux-phy@lists.infradead.org,  linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, nm@ti.com,  vigneshr@ti.com
Subject: Re: [PATCH v3] phy: ti: gmii-sel: Always write the RGMII ID setting
Date: Mon, 01 Sep 2025 22:33:55 +0530	[thread overview]
Message-ID: <175674623530.175374.344829536743551293.b4-ty@kernel.org> (raw)
In-Reply-To: <20250819065622.1019537-1-mwalle@kernel.org>


On Tue, 19 Aug 2025 08:56:22 +0200, Michael Walle wrote:
> Some SoCs are just validated with the TX delay enabled. With commit
> ca13b249f291 ("net: ethernet: ti: am65-cpsw: fixup PHY mode for fixed
> RGMII TX delay"), the network driver will patch the delay setting on the
> fly assuming that the TX delay setting is fixed. In reality, the TX
> delay is configurable and just skipped in the documentation. There are
> bootloaders, which will disable the TX delay and this will lead to a
> transmit path which doesn't add any delays at all.
> Fix that by always writing the RGMII_ID setting and report an error for
> unsupported RGMII delay modes.
> 
> [...]

Applied, thanks!

[1/1] phy: ti: gmii-sel: Always write the RGMII ID setting
      commit: a22d3b0d49d411e64ed07e30c2095035ecb30ed2

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2025-09-01 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  6:56 Michael Walle
2025-08-19  9:45 ` Maxime Chevallier
2025-08-22  1:18 ` Jakub Kicinski
2025-08-22  6:45   ` Michael Walle
2025-08-22 14:01     ` Jakub Kicinski
2025-09-01 17:03 ` Vinod Koul [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=175674623530.175374.344829536743551293.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=kishon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=mwalle@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@ti.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

all inboxes | Powered by JetHome®