[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2098a161-58c2-c3d8-0c4b-8ff0c20df934@gmail.com>
Date: Mon, 4 Oct 2021 13:35:40 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.4 29/56] net: phy: bcm7xxx: request and manage GPHY
clock
On 10/4/21 5:52 AM, Greg Kroah-Hartman wrote:
> From: Florian Fainelli <f.fainelli@...il.com>
>
> [ Upstream commit ba4ee3c053659119472135231dbef8f6880ce1fb ]
>
> The internal Gigabit PHY on Broadcom STB chips has a digital clock which
> drives its MDIO interface among other things, the driver now requests
> and manage that clock during .probe() and .remove() accordingly.
>
> Because the PHY driver can be probed with the clocks turned off we need
> to apply the dummy BMSR workaround during the driver probe function to
> ensure subsequent MDIO read or write towards the PHY will succeed.
>
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> Reviewed-by: Andrew Lunn <andrew@...n.ch>
> Signed-off-by: David S. Miller <davem@...emloft.net>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
Please drop this patch from the queue, this is not a bug fix for the 5.4
branch. If you would like me to send a patch for "net: phy: bcm7xxx:
Fixed indirect MMD operations", please let me know.
--
Florian
Powered by blists - more mailing lists