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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 6 Apr 2017 19:48:50 +0300 From: Roger Quadros <rogerq@...com> To: Andrew Lunn <andrew@...n.ch> CC: <davem@...emloft.net>, <tony@...mide.com>, <nsekhar@...com>, <jsarha@...com>, <netdev@...r.kernel.org>, <linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] net: davinci_mdio: add GPIO reset logic On 06/04/17 15:05, Andrew Lunn wrote: >>> Do you really need more than one GPIO? A single gpio would make all >>> this code a lot simpler. >>> >> >> Yes we need. Some of our boards have separate GPIO RESET lines for >> different PHYs on the same MDIO bus. > > If you have a one-to-one mapping of GPIO and PHY, you should really be > modelling that differently. You want to be able to reset just a single > PHY, i.e. make it part of the PHY driver, or maybe the PHY core. > > Andrew > I'm not sure how it would be modelled. We have never had the need to reset just one PHY on the MDIO bus. Some boards have a single RESET line to multiple PHYs whereas others have individual RESET lines. In all cases we just want to do the RESET once per boot. cheers, -roger
Powered by blists - more mailing lists