[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<BYAPR12MB47731D5AAC7091F89C2CA9AC9E749@BYAPR12MB4773.namprd12.prod.outlook.com>
Date: Thu, 11 May 2023 16:17:21 +0000
From: "Katakam, Harini" <harini.katakam@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: "hkallweit1@...il.com" <hkallweit1@...il.com>, "linux@...linux.org.uk"
<linux@...linux.org.uk>, "davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>, "edumazet@...gle.com"
<edumazet@...gle.com>, "pabeni@...hat.com" <pabeni@...hat.com>,
"vladimir.oltean@....com" <vladimir.oltean@....com>,
"wsa+renesas@...g-engineering.com" <wsa+renesas@...g-engineering.com>,
"simon.horman@...igine.com" <simon.horman@...igine.com>, "mkl@...gutronix.de"
<mkl@...gutronix.de>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"harinikatakamlinux@...il.com" <harinikatakamlinux@...il.com>, "Simek,
Michal" <michal.simek@....com>, "Pandey, Radhey Shyam"
<radhey.shyam.pandey@....com>
Subject: RE: [PATCH net-next v3 3/3] phy: mscc: Add support for VSC8531_02
Hi Andrew,
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: Thursday, May 11, 2023 7:42 PM
> To: Katakam, Harini <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; Simek, Michal <michal.simek@....com>;
> Pandey, Radhey Shyam <radhey.shyam.pandey@....com>
> Subject: Re: [PATCH net-next v3 3/3] phy: mscc: Add support for VSC8531_02
>
> On Thu, May 11, 2023 at 05:38:08PM +0530, Harini Katakam wrote:
> > Add support for VSC8531_02 (Rev 2) device. Use exact PHY ID match.
> >
> > Signed-off-by: Harini Katakam <harini.katakam@....com>
> > ---
> > v3 - Patch split
> >
> > drivers/net/phy/mscc/mscc.h | 1 +
> > drivers/net/phy/mscc/mscc_main.c | 26 ++++++++++++++++++++++++--
> > 2 files changed, 25 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/phy/mscc/mscc.h b/drivers/net/phy/mscc/mscc.h
> > index ab6c0b7c2136..6a0521ff61d2 100644
> > --- a/drivers/net/phy/mscc/mscc.h
> > +++ b/drivers/net/phy/mscc/mscc.h
> > @@ -281,6 +281,7 @@ enum rgmii_clock_delay {
> > #define PHY_ID_VSC8514 0x00070670
> > #define PHY_ID_VSC8530 0x00070560
> > #define PHY_ID_VSC8531 0x00070570
> > +#define PHY_ID_VSC8531_02 0x00070572
>
> Does PHY_ID_VSC8531_01 exist? The current code would support that,
> where as now i don't think any entry will match.
Yes, PHY_ID_VSC8531_01 exists:
https://ww1.microchip.com/downloads/en/DeviceDoc/VMDS-10494.pdf
And I'm sorry I realize now that this patch breaks that version.
Also considering your RC on the other thread,
" Just to make it clear why the existing PHY_ID_VSC853/0xfffffff0 is not sufficient."
Currently there is no difference in the phy driver structure between
VSC8531 and VSC8531_02. Let me double check the identification on
my board and skip this patch if possible. The RGMII delay support in
2/3 is generic anyway.
Regards,
Harini
Powered by blists - more mailing lists