[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191023.204311.1181447784152558295.davem@davemloft.net>
Date: Wed, 23 Oct 2019 20:43:11 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: rentao.bupt@...il.com
Cc: andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
linux@...linux.org.uk, olteanv@...il.com,
arun.parameswaran@...adcom.com, justinpopo6@...il.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
openbmc@...ts.ozlabs.org
Subject: Re: [PATCH net-next v10 0/3] net: phy: support 1000Base-X
auto-negotiation for BCM54616S
From: rentao.bupt@...il.com
Date: Tue, 22 Oct 2019 11:31:05 -0700
> From: Tao Ren <rentao.bupt@...il.com>
>
> This patch series aims at supporting auto negotiation when BCM54616S is
> running in 1000Base-X mode: without the patch series, BCM54616S PHY driver
> would report incorrect link speed in 1000Base-X mode.
>
> Patch #1 (of 3) modifies assignment to OR when dealing with dev_flags in
> phy_attach_direct function, so that dev_flags updated in BCM54616S PHY's
> probe callback won't be lost.
>
> Patch #2 (of 3) adds several genphy_c37_* functions to support clause 37
> 1000Base-X auto-negotiation, and these functions are called in BCM54616S
> PHY driver.
>
> Patch #3 (of 3) detects BCM54616S PHY's operation mode and calls according
> genphy_c37_* functions to configure auto-negotiation and parse link
> attributes (speed, duplex, and etc.) in 1000Base-X mode.
Series applied to net-next, thank you.
Powered by blists - more mailing lists