[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <428db3e5-fb22-45a3-8d75-85cfbf67fe56@lunn.ch>
Date: Thu, 11 May 2023 16:05:41 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Harini Katakam <harini.katakam@....com>
Cc: hkallweit1@...il.com, linux@...linux.org.uk, davem@...emloft.net,
kuba@...nel.org, edumazet@...gle.com, pabeni@...hat.com,
vladimir.oltean@....com, wsa+renesas@...g-engineering.com,
simon.horman@...igine.com, mkl@...gutronix.de,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
harinikatakamlinux@...il.com, michal.simek@....com,
radhey.shyam.pandey@....com
Subject: Re: [PATCH net-next v3 1/3] phy: mscc: Use PHY_ID_MATCH_VENDOR to
minimize PHY ID table
On Thu, May 11, 2023 at 05:38:06PM +0530, Harini Katakam wrote:
> All the PHY devices variants specified have the same mask and
> hence can be simplified to one vendor look up for 0x00070400.
> Any individual config can be identified by PHY_ID_MATCH_EXACT
> in the respective structure.
>
> Signed-off-by: Harini Katakam <harini.katakam@....com>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists