[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175674623530.175374.344829536743551293.b4-ty@kernel.org>
Date: Mon, 01 Sep 2025 22:33:55 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Kishon Vijay Abraham I <kishon@...nel.org>,
Michael Walle <mwalle@...nel.org>
Cc: Siddharth Vadapalli <s-vadapalli@...com>,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
Andrew Lunn <andrew@...n.ch>, linux-phy@...ts.infradead.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, nm@...com,
vigneshr@...com
Subject: Re: [PATCH v3] phy: ti: gmii-sel: Always write the RGMII ID
setting
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
Powered by blists - more mailing lists