[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <abe49f9e-a1c4-424a-a96f-0793c0fab57f@lunn.ch>
Date: Wed, 19 Feb 2025 21:42:22 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Wei Fang <wei.fang@....com>
Cc: claudiu.manoil@....com, vladimir.oltean@....com, xiaoning.wang@....com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, ioana.ciornei@....com,
yangbo.lu@....com, michal.swiatkowski@...ux.intel.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
imx@...ts.linux.dev, stable@...r.kernel.org
Subject: Re: [PATCH v2 net 8/9] net: enetc: correct the EMDIO base offset for
ENETC v4
On Wed, Feb 19, 2025 at 01:42:46PM +0800, Wei Fang wrote:
> In addition to centrally managing external PHYs through EMIDO device,
> each ENETC has a set of EMDIO registers to access and manage its own
> external PHY. When adding i.MX95 ENETC support, the EMDIO base offset
> was forgot to be updated, which will result in ENETC being unable to
> manage its external PHY through its own EMDIO registers.
So this never worked?
If it never worked, does it actually bother anybody?
Stable rules say:
It must either fix a real bug that bothers people or just add a device ID.
Andrew
Powered by blists - more mailing lists