From: Andrew Lunn <andrew@lunn.ch>
To: "Song, Yoong Siang" <yoong.siang.song@intel.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
"Marek Behún" <kabel@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/1] net: phy: marvell10g: Add WAKE_PHY support to WOL event
Date: Mon, 16 Aug 2021 06:10:39 +0200 [thread overview]
Message-ID: <YRnlP/9oimKRbn0q@lunn.ch> (raw)
In-Reply-To: <PH0PR11MB4950EAF1FC749EAAE3FDFCB7D8FD9@PH0PR11MB4950.namprd11.prod.outlook.com>
On Mon, Aug 16, 2021 at 03:19:34AM +0000, Song, Yoong Siang wrote:
> > > How does this work if the driver has no interrupt support? What is the
> > > hardware setup this has been tested with?
> >
> > Hi Russell
> >
> > We already know from previous patches that the Intel hardware is broken,
> > and does not actually deliver the interrupt which caused the wake up. So i
> > assume this just continues on with the same broken hardware, but they have
> > a different PHY connected.
>
> Hi Russell & Andrew,
>
> This is tested on Intel Elkhart Lake (EHL) board. We are using polling mode.
> Both WoL interrupt and link change interrupt are the same pin which is
> routed to PMC. PMC will wake up the system when there is WoL event.
Is the PMC also an interrupt controller?
Andrew
prev parent reply other threads:[~2021-08-16 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 8:45 [PATCH net-next 1/1] net: phy: marvell10g: Add WAKE_PHY support to WOL event Song Yoong Siang
2021-08-14 17:19 ` Marek Behún
2021-08-14 17:26 ` Russell King (Oracle)
2021-08-14 18:04 ` Andrew Lunn
2021-08-14 19:49 ` Russell King (Oracle)
2021-08-16 3:52 ` Song, Yoong Siang
2021-08-16 4:15 ` Andrew Lunn
2021-08-16 5:40 ` Song, Yoong Siang
2021-08-16 7:14 ` Russell King (Oracle)
2021-08-16 8:03 ` Song, Yoong Siang
2021-08-16 8:18 ` Russell King (Oracle)
2021-08-16 8:56 ` Song, Yoong Siang
2021-08-16 9:54 ` Marek Behún
2021-08-16 15:02 ` Song, Yoong Siang
2021-08-16 15:27 ` Andrew Lunn
2021-08-20 1:22 ` Song, Yoong Siang
2021-08-16 3:19 ` Song, Yoong Siang
2021-08-16 4:10 ` Andrew Lunn [this message]
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=YRnlP/9oimKRbn0q@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=yoong.siang.song@intel.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).