lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 18 Sep 2020 17:22:18 -0700 (PDT) From: David Miller <davem@...emloft.net> To: f.fainelli@...il.com Cc: netdev@...r.kernel.org, opendmb@...il.com, andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk, kuba@...nel.org, bcm-kernel-feedback-list@...adcom.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next v2] net: phy: bcm7xxx: request and manage GPHY clock From: Florian Fainelli <f.fainelli@...il.com> Date: Wed, 16 Sep 2020 19:04:13 -0700 > 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> > --- > Changes in v2: > > - localize the changes exclusively within the PHY driver and do not > involve the MDIO driver at all. Using the ethernet-phyidAAAA.BBBB > compatible string we can get straight to the desired driver without > requiring clocks to be assumed on. Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists