[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160513204436.GC7600@lunn.ch>
Date: Fri, 13 May 2016 22:44:36 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc: Roger Quadros <rogerq@...com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, grant.likely@...aro.org,
robh+dt@...nel.org, devicetree@...r.kernel.org,
f.fainelli@...il.com, netdev@...r.kernel.org,
frowand.list@...il.com, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH RFT 1/2] phylib: add device reset GPIO support
> >Another issue is that on some boards we have one reset line tied to
> >multiple PHYs.How do we prevent multiple resets being taking place when each of
> >the PHYs are registered?
>
> My patch just doesn't address this case -- it's about the
> individual resets only.
This actually needs to be addresses a layer above. What you have is a
bus reset, not a device reset. So the gpio line is associated to the
mdio bus, not a PHY. Either your MDIO driver needs to handle the gpio
line, or in __mdio_register(), before it starts looking at the
children.
Andrew
Powered by blists - more mailing lists