From: Andrew Lunn <andrew@lunn.ch>
To: Bhadram Varka <vbhadram@nvidia.com>
Cc: Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jingju Hou <Jingju.Hou@synaptics.com>
Subject: Re: [PATCH] net: phy: marvell: clear wol event before setting it
Date: Thu, 19 Apr 2018 13:33:12 +0200 [thread overview]
Message-ID: <20180419113312.GA17888@lunn.ch> (raw)
In-Reply-To: <1c3a4b66-b10c-adc9-b7e4-57b46f5c86e5@nvidia.com>
> >IIRC, the phy irq isn't necessary for WOL. The phy interrupt pin isn't
> >necessarily taken as "interrupt"
> Please correct me if I am wrong. In this case how the system will wake up
> from the SC7.There has to be wake capable irq/gpio pin to do this operation.
>
Hi Bhadram
I've seem implementations where the line from the PHY is connected to
the power supply. It simply turns the power on. No interrupt needed.
Andrew
next prev parent reply other threads:[~2018-04-19 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 8:02 [PATCH] net: phy: marvell: clear wol event before setting it Jisheng Zhang
2018-04-19 8:38 ` Bhadram Varka
2018-04-19 8:53 ` Jisheng Zhang
2018-04-19 9:00 ` Bhadram Varka
2018-04-19 9:09 ` Jisheng Zhang
2018-04-19 10:05 ` Bhadram Varka
2018-04-19 11:33 ` Andrew Lunn [this message]
2018-04-19 12:18 ` Andrew Lunn
2018-04-26 5:40 ` Bhadram Varka
2018-04-26 6:15 ` Jisheng Zhang
2018-04-26 6:26 ` Bhadram Varka
2018-04-26 7:09 ` Bhadram Varka
2018-04-27 7:25 ` Jisheng Zhang
2018-04-30 13:17 ` Andrew Lunn
2018-04-26 7:56 ` Jisheng Zhang
2018-04-26 12:40 ` Andrew Lunn
2018-04-27 3:52 ` Bhadram Varka
2018-04-27 7:23 ` Jisheng Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180419113312.GA17888@lunn.ch \
--to=andrew@lunn.ch \
--cc=Jingju.Hou@synaptics.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vbhadram@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).