From: Rafael J. Wysocki <[email protected]>
Subject: net (tg3): Fix failure to enable WoL by default when possible
tg3 is supposed to enable WoL by default on adapters which support
that, but it fails to do so unless the adapter's
/sys/devices/.../power/wakeup file contains 'enabled' during the
initialization of the adapter. Fix that by making tg3 update the
device's 'should_wakeup' bit automatically whenever WoL should be
enabled by default.
Signed-off-by: Rafael J. Wysocki <[email protected]>
---
drivers/net/tg3.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Index: linux-2.6/drivers/net/tg3.c
===================================================================
--- linux-2.6.orig/drivers/net/tg3.c
+++ linux-2.6/drivers/net/tg3.c
@@ -11296,9 +11296,10 @@ static void __devinit tg3_get_eeprom_hw_
if (val & VCPU_CFGSHDW_ASPM_DBNC)
tp->tg3_flags |= TG3_FLAG_ASPM_WORKAROUND;
if ((val & VCPU_CFGSHDW_WOL_ENABLE) &&
- (val & VCPU_CFGSHDW_WOL_MAGPKT) &&
- device_may_wakeup(&tp->pdev->dev))
+ (val & VCPU_CFGSHDW_WOL_MAGPKT)) {
tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
+ device_set_wakeup_enable(&tp->pdev->dev, true);
+ }
return;
}
On Monday, 8 of December 2008, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <[email protected]>
> Subject: net (tg3): Fix failure to enable WoL by default when possible
>
> tg3 is supposed to enable WoL by default on adapters which support
> that, but it fails to do so unless the adapter's
> /sys/devices/.../power/wakeup file contains 'enabled' during the
> initialization of the adapter. Fix that by making tg3 update the
> device's 'should_wakeup' bit automatically whenever WoL should be
> enabled by default.
This version of the patch is incomplete, because there's one more place where
an analogous change has to be made.
I'll send the updated patch in a reply to this message.
Thanks,
Rafael
> Signed-off-by: Rafael J. Wysocki <[email protected]>
> ---
> drivers/net/tg3.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> Index: linux-2.6/drivers/net/tg3.c
> ===================================================================
> --- linux-2.6.orig/drivers/net/tg3.c
> +++ linux-2.6/drivers/net/tg3.c
> @@ -11296,9 +11296,10 @@ static void __devinit tg3_get_eeprom_hw_
> if (val & VCPU_CFGSHDW_ASPM_DBNC)
> tp->tg3_flags |= TG3_FLAG_ASPM_WORKAROUND;
> if ((val & VCPU_CFGSHDW_WOL_ENABLE) &&
> - (val & VCPU_CFGSHDW_WOL_MAGPKT) &&
> - device_may_wakeup(&tp->pdev->dev))
> + (val & VCPU_CFGSHDW_WOL_MAGPKT)) {
> tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
> + device_set_wakeup_enable(&tp->pdev->dev, true);
> + }
> return;
> }
>
> --
From: Rafael J. Wysocki <[email protected]>
Subject: net (tg3): Fix failure to enable WoL by default when possible (rev. 2)
tg3 is supposed to enable WoL by default on adapters which support
that, but it fails to do so unless the adapter's
/sys/devices/.../power/wakeup file contains 'enabled' during the
initialization of the adapter. Fix that by making tg3 update the
device's 'should_wakeup' bit automatically whenever WoL should be
enabled by default.
Signed-off-by: Rafael J. Wysocki <[email protected]>
---
drivers/net/tg3.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
Index: linux-2.6/drivers/net/tg3.c
===================================================================
--- linux-2.6.orig/drivers/net/tg3.c
+++ linux-2.6/drivers/net/tg3.c
@@ -11296,9 +11296,10 @@ static void __devinit tg3_get_eeprom_hw_
if (val & VCPU_CFGSHDW_ASPM_DBNC)
tp->tg3_flags |= TG3_FLAG_ASPM_WORKAROUND;
if ((val & VCPU_CFGSHDW_WOL_ENABLE) &&
- (val & VCPU_CFGSHDW_WOL_MAGPKT) &&
- device_may_wakeup(&tp->pdev->dev))
+ (val & VCPU_CFGSHDW_WOL_MAGPKT)) {
tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
+ device_set_wakeup_enable(&tp->pdev->dev, true);
+ }
return;
}
@@ -11428,9 +11429,10 @@ static void __devinit tg3_get_eeprom_hw_
tp->tg3_flags &= ~TG3_FLAG_WOL_CAP;
if ((tp->tg3_flags & TG3_FLAG_WOL_CAP) &&
- (nic_cfg & NIC_SRAM_DATA_CFG_WOL_ENABLE) &&
- device_may_wakeup(&tp->pdev->dev))
+ (nic_cfg & NIC_SRAM_DATA_CFG_WOL_ENABLE)) {
tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
+ device_set_wakeup_enable(&tp->pdev->dev, true);
+ }
if (cfg2 & (1 << 17))
tp->tg3_flags2 |= TG3_FLG2_CAPACITIVE_COUPLING;
This has mostly been fixed up already in Dave Miller's tree. In that
tree, the WOL capability advertisements happens at the end of the
tg3_get_eeprom_hw_cfg() function.
Your patch did uncover a bug though. The removal of device_may_wakeup()
in the first hunk of your patch still needs to be done.
On Mon, Dec 08, 2008 at 03:52:55AM -0800, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <[email protected]>
> Subject: net (tg3): Fix failure to enable WoL by default when possible (rev. 2)
>
> tg3 is supposed to enable WoL by default on adapters which support
> that, but it fails to do so unless the adapter's
> /sys/devices/.../power/wakeup file contains 'enabled' during the
> initialization of the adapter. Fix that by making tg3 update the
> device's 'should_wakeup' bit automatically whenever WoL should be
> enabled by default.
>
> Signed-off-by: Rafael J. Wysocki <[email protected]>
> ---
> drivers/net/tg3.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> Index: linux-2.6/drivers/net/tg3.c
> ===================================================================
> --- linux-2.6.orig/drivers/net/tg3.c
> +++ linux-2.6/drivers/net/tg3.c
> @@ -11296,9 +11296,10 @@ static void __devinit tg3_get_eeprom_hw_
> if (val & VCPU_CFGSHDW_ASPM_DBNC)
> tp->tg3_flags |= TG3_FLAG_ASPM_WORKAROUND;
> if ((val & VCPU_CFGSHDW_WOL_ENABLE) &&
> - (val & VCPU_CFGSHDW_WOL_MAGPKT) &&
> - device_may_wakeup(&tp->pdev->dev))
> + (val & VCPU_CFGSHDW_WOL_MAGPKT)) {
> tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
> + device_set_wakeup_enable(&tp->pdev->dev, true);
> + }
> return;
> }
>
> @@ -11428,9 +11429,10 @@ static void __devinit tg3_get_eeprom_hw_
> tp->tg3_flags &= ~TG3_FLAG_WOL_CAP;
>
> if ((tp->tg3_flags & TG3_FLAG_WOL_CAP) &&
> - (nic_cfg & NIC_SRAM_DATA_CFG_WOL_ENABLE) &&
> - device_may_wakeup(&tp->pdev->dev))
> + (nic_cfg & NIC_SRAM_DATA_CFG_WOL_ENABLE)) {
> tp->tg3_flags |= TG3_FLAG_WOL_ENABLE;
> + device_set_wakeup_enable(&tp->pdev->dev, true);
> + }
>
> if (cfg2 & (1 << 17))
> tp->tg3_flags2 |= TG3_FLG2_CAPACITIVE_COUPLING;
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
From: "Matt Carlson" <[email protected]>
Date: Mon, 8 Dec 2008 11:04:03 -0800
> This has mostly been fixed up already in Dave Miller's tree. In that
> tree, the WOL capability advertisements happens at the end of the
> tg3_get_eeprom_hw_cfg() function.
>
> Your patch did uncover a bug though. The removal of device_may_wakeup()
> in the first hunk of your patch still needs to be done.
Ok, can someone post a patch that takes care of that against
net-next-2.6?
Thanks in advance!
On Tuesday, 9 of December 2008, David Miller wrote:
> From: "Matt Carlson" <[email protected]>
> Date: Mon, 8 Dec 2008 11:04:03 -0800
>
> > This has mostly been fixed up already in Dave Miller's tree. In that
> > tree, the WOL capability advertisements happens at the end of the
> > tg3_get_eeprom_hw_cfg() function.
> >
> > Your patch did uncover a bug though. The removal of device_may_wakeup()
> > in the first hunk of your patch still needs to be done.
>
> Ok, can someone post a patch that takes care of that against
> net-next-2.6?
Matt, are you going to take care of this or do you want me to do that?
Rafael
Sure. I'll do it. Standby.
On Tue, Dec 09, 2008 at 12:26:35PM -0800, Rafael J. Wysocki wrote:
> On Tuesday, 9 of December 2008, David Miller wrote:
> > From: "Matt Carlson" <[email protected]>
> > Date: Mon, 8 Dec 2008 11:04:03 -0800
> >
> > > This has mostly been fixed up already in Dave Miller's tree. In that
> > > tree, the WOL capability advertisements happens at the end of the
> > > tg3_get_eeprom_hw_cfg() function.
> > >
> > > Your patch did uncover a bug though. The removal of device_may_wakeup()
> > > in the first hunk of your patch still needs to be done.
> >
> > Ok, can someone post a patch that takes care of that against
> > net-next-2.6?
>
> Matt, are you going to take care of this or do you want me to do that?
>
> Rafael
>