Messages in this thread | | | From | "Ismail, Mohammad Athari" <> | Subject | RE: [PATCH net] net: phy: reconfigure PHY WOL in resume if WOL option still enabled | Date | Thu, 8 Jul 2021 23:11:43 +0000 |
| |
> -----Original Message----- > From: Andrew Lunn <andrew@lunn.ch> > Sent: Thursday, July 8, 2021 9:11 PM > To: Ismail, Mohammad Athari <mohammad.athari.ismail@intel.com> > Cc: Heiner Kallweit <hkallweit1@gmail.com>; David S . Miller > <davem@davemloft.net>; Russell King <linux@armlinux.org.uk>; Jakub > Kicinski <kuba@kernel.org>; Florian Fainelli <f.fainelli@gmail.com>; > netdev@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH net] net: phy: reconfigure PHY WOL in resume if WOL > option still enabled > > > Hi Andrew, > > > > In our platform, the PHY interrupt pin is not connected to Host CPU. So, the > CPU couldn`t service the PHY interrupt. The PHY interrupt pin is connected to > a power management controller (PMC) as a HW wake up signal. The PMC > itself couldn't act as interrupt controller to service the PHY interrupt. > > > > During WOL event, the WOL signal is sent to PMC through the PHY interrupt > pin to wake up the PMC. Then, the PMC will wake up the Host CPU and the > whole system. > > How is the PMC connected to the host? LPC? At wake up can you ask it why it > woke you up? What event it was, power restored, power button press, or > WOL? Can the PMC generate interrupts over the LPC? What PMC is it? Is > there a datasheet for it? > > Getting your architecture correct will also solve your S3/S4 problems.
Hi Andrew,
I'll try to get more info from our architecture design team.
-Athari-
> > Andrew
| |