[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <797fe98f-ab65-8633-dadc-beed56d251d0@maxlinear.com>
Date: Fri, 4 Jun 2021 12:52:02 +0000
From: Liang Xu <lxu@...linear.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "hkallweit1@...il.com" <hkallweit1@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"vee.khee.wong@...ux.intel.com" <vee.khee.wong@...ux.intel.com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
Hauke Mehrtens <hmehrtens@...linear.com>,
Thomas Mohren <tmohren@...linear.com>
Subject: Re: [PATCH v2] net: phy: add Maxlinear GPY115/21x/24x driver
On 4/6/2021 8:15 pm, Andrew Lunn wrote:
> This email was sent from outside of MaxLinear.
>
>
>> +config MXL_GPHY
>> + tristate "Maxlinear PHYs"
>> + help
>> + Support for the Maxlinear GPY115, GPY211, GPY212, GPY215,
>> + GPY241, GPY245 PHYs.
> Do these PHYs have unique IDs in register 2 and 3? What is the format
> of these IDs?
>
> The OUI is fixed. But often the rest is split into two. The higher
> part indicates the product, and the lower part is the revision. We
> then have a struct phy_driver for each product, and the mask is used
> to match on all the revisions of the product.
>
> Andrew
>
Register 2, Register 3 bit 10~15 - OUI
Register 3 bit 4~9 - product number
Register 3 bit 0~3 - revision number
These PHYs have same ID in register 2 and 3.
Powered by blists - more mailing lists