From: David Miller <davem@davemloft.net>
To: alexander.duyck@gmail.com
Cc: andy@greyhouse.net, john.ronciak@intel.com,
netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
peter.p.waskiewicz.jr@intel.com, stable@kernel.org
Subject: Re: [PATCH] igb/e1000e/e1000/e100: make wol usable
Date: Tue, 21 Jul 2009 20:56:45 -0700 (PDT) [thread overview]
Message-ID: <20090721.205645.234746177.davem@davemloft.net> (raw)
In-Reply-To: <5f2db9d90907212025k31c3a941v5fd1be9ed171e4c1@mail.gmail.com>
From: Alexander Duyck <alexander.duyck@gmail.com>
Date: Tue, 21 Jul 2009 20:25:31 -0700
> My understanding was that the can_wakeup was supposed to be
> initialized by pci_pm_init or platform_pci_wakeup_init based on the
> pci-e capabilities. Is this not the case? It seems like this is
> where you should be looking to determine why the the can_wakeup isn't
> being initialized correctly.
>
> The patch below won't solve the problem either. The problem is that
> the can_wakeup value is being disabled when the EEPROM doesn't support
> WOL.
>
> If you have to do this in the drivers, then my suggestion is to take a
> look at how ixgbe is doing it. You essentially need to initialize
> can_wakeup to true, and then set the should_wakeup attribute based on
> the EEPROM setting or via ethtool. This way you can still toggle the
> should_wakeup option without being blocked by the EEPROM disabling it.
It looks like the approach needs to be worked out still, so
I'm tossing these patches from patchwork.
Let me know when a more final fix is ready.
Thanks.
next prev parent reply other threads:[~2009-07-22 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 21:01 [PATCH] igb/e1000e/e1000/e100: make wol usable Andy Gospodarek
2009-07-21 21:59 ` Ronciak, John
2009-07-22 2:27 ` Andy Gospodarek
2009-07-22 3:25 ` Alexander Duyck
2009-07-22 3:56 ` David Miller [this message]
2009-07-22 19:34 ` Andy Gospodarek
2009-07-22 20:00 ` Waskiewicz Jr, Peter P
2009-07-22 23:43 ` Waskiewicz Jr, Peter P
2009-07-23 18:06 ` David Miller
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=20090721.205645.234746177.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=andy@greyhouse.net \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=stable@kernel.org \
/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