[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14c8dbbc-92d1-4d51-9986-a6f2ef1c3e52@lunn.ch>
Date: Sat, 25 Nov 2023 18:06:02 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Jakub Kicinski <kuba@...nel.org>,
Marek BehĂșn <kabel@...nel.org>,
netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 01/10] net: phy: add possible interfaces
On Fri, Nov 24, 2023 at 12:27:52PM +0000, Russell King (Oracle) wrote:
> Add a possible_interfaces member to struct phy_device to indicate which
> interfaces a clause 45 PHY may switch between depending on the media.
> This must be populated by the PHY driver by the time the .config_init()
> method completes according to the PHYs host-side configuration.
>
> For example, the Marvell 88x3310 PHY can switch between 10GBASE-R,
> 5GBASE-R, 2500BASE-X, and SGMII on the host side depending on the media
> side speed, so all these interface modes are set in the
> possible_interfaces member.
>
> This allows phylib users (such as phylink) to know in advance which
> interface modes to expect, which allows them to appropriately restrict
> the advertised link modes according to the capabilities of other parts
> of the link.
>
> Tested-by: Luo Jie <quic_luoj@...cinc.com>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@...linux.org.uk>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists