From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: "Michael Büsch" <m@bues.ch>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Gary.Zambrano@qlogic.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: [PATCH] SSB / B44: fix WOL for BCM4401
Date: Tue, 2 Dec 2014 23:01:29 +0300 [thread overview]
Message-ID: <20141202200129.GA4580@crion89> (raw)
In-Reply-To: <20141201221023.79ffb40d@wiggum>
On Mon, Dec 01, 2014 at 10:10:23PM +0100, Michael B?sch wrote:
> On Mon, 1 Dec 2014 23:46:38 +0300
> Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
>
> > Wake On Lan was not working on laptop DELL Vostro 1500.
> > If WOL was turned on, BCM4401 was powered up in suspend mode. LEDs blinked.
> > But the laptop could not be woken up with the Magic Packet. The reason for
> > that was that PCIE was not enabled as a system wakeup source and
> > therefore the host PCI bridge was not powered up in suspend mode.
> > PCIE was not enabled in suspend by PM because no child devices were
> > registered as wakeup source during suspend process.
> > On laptop BCM4401 is connected through the SSB bus, that is connected to the
> > PCI-Express bus. SSB and B44 did not use standard PM wakeup functions
> > and did not forward wakeup settings to their parents.
> > To fix that B44 driver enables PM wakeup and registers new wakeup source
> > using device_set_wakeup_enable(). Wakeup is automatically reported to the parent SSB
> > bus via power.wakeup_path. SSB bus enables wakeup for the parent PCI bridge, if there is any
> > child devices with enabled wakeup functionality. All other steps are
> > done by PM core code.
>
> Thanks, this looks good.
> I assume you tested this (I currently don't have a device to test this).
Sure, I've tested it. WOL from suspend is working and after resume from hibernate Ethernet is working too.
> Larry, Rafa?, any other b43 user:
> Can you please test whether this doesn't cause regressions for suspend/resume on b43?
> (Patch is attached as reference)
>
>
> > Signed-off-by: Andrey Skvortsov <Andrej.Skvortzov@gmail.com>
> > ---
> > drivers/net/ethernet/broadcom/b44.c | 2 ++
> > drivers/ssb/pcihost_wrapper.c | 33 ++++++++++++++++++++++-----------
> > 2 files changed, 24 insertions(+), 11 deletions(-)
--
Best regards,
Andrey Skvortsov
PGP Key ID: 0x57A3AEAD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20141202/1806ce02/attachment.sig>
next prev parent reply other threads:[~2014-12-02 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141201111125.GA11974@localhost.localdomain>
[not found] ` <1417466798-15735-1-git-send-email-Andrej.Skvortzov@gmail.com>
2014-12-01 21:10 ` [PATCH] SSB / B44: fix WOL for BCM4401 Michael Büsch
2014-12-02 20:01 ` Andrey Skvortsov [this message]
2014-12-02 20:12 ` Michael Büsch
2014-12-02 22:23 ` Larry Finger
2014-12-03 15:18 ` Michael Büsch
2014-12-03 16:14 ` John W. Linville
2014-12-03 16:23 ` Michael Büsch
2014-12-04 11:11 ` Andrey Skvortsov
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=20141202200129.GA4580@crion89 \
--to=andrej.skvortzov@gmail.com \
--cc=Gary.Zambrano@qlogic.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=zajec5@gmail.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).