[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ybsi00/CAd7oVl17@lunn.ch>
Date: Thu, 16 Dec 2021 12:28:19 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Francesco Dolcini <francesco.dolcini@...adex.com>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
Joakim Zhang <qiangqing.zhang@....com>,
Philippe Schenker <philippe.schenker@...adex.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
Heiner Kallweit <hkallweit1@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Fabio Estevam <festevam@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: fec: reset phy on resume after power-up
On Thu, Dec 16, 2021 at 12:24:33PM +0100, Francesco Dolcini wrote:
> On Thu, Dec 16, 2021 at 11:24:24AM +0100, Andrew Lunn wrote:
> > I think you need to move the regulator into phylib, so the PHY driver
> > can do the right thing. It is really the only entity which knows what
> > is the correct thing to do.
> Do you believe that the right place is the phylib and not the phy driver?
> Is this generic enough?
It is split. phylib can do the lookup in DT, get the regulator and
provide a helper to enable/disable it. So very similar to the reset.
The phy driver would then use the helpers. It probably needs to look
into the phydev structure to see what is actually available, is there
a reset, a regulator etc, and then decide what is best to do given the
available resources.
Andrew
Powered by blists - more mailing lists