* [PATCH 1/2] tulip: explicity set to D0 power state during init
@ 2010-05-31 22:34 Steven Walter
2010-06-01 1:00 ` Grant Grundler
0 siblings, 1 reply; 4+ messages in thread
From: Steven Walter @ 2010-05-31 22:34 UTC (permalink / raw)
To: grundler, kyle, netdev; +Cc: Steven Walter
During the first suspend the chip would refuse to enter D3. Subsequent
suspends worked okay. During resume the chip is commanded into D0.
Doing so during initialization fixes the initial suspend.
Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
---
drivers/net/tulip/tulip_core.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/net/tulip/tulip_core.c b/drivers/net/tulip/tulip_core.c
index 3810db9..bb8c0ee 100644
--- a/drivers/net/tulip/tulip_core.c
+++ b/drivers/net/tulip/tulip_core.c
@@ -1380,6 +1380,13 @@ static int __devinit tulip_init_one (struct pci_dev *pdev,
return i;
}
+ /* The chip will fail to enter a low-power state later unless
+ * first explicitly commanded into D0 */
+ if (pci_set_power_state(pdev, PCI_D0)) {
+ printk (KERN_ERR PFX
+ "Failed to set power state to D0\n");
+ }
+
irq = pdev->irq;
/* alloc_etherdev ensures aligned and zeroed private structures */
--
1.6.3.3
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 1/2] tulip: explicity set to D0 power state during init
2010-05-31 22:34 Steven Walter
@ 2010-06-01 1:00 ` Grant Grundler
0 siblings, 0 replies; 4+ messages in thread
From: Grant Grundler @ 2010-06-01 1:00 UTC (permalink / raw)
To: Steven Walter; +Cc: grundler, kyle, netdev
On Mon, May 31, 2010 at 06:34:42PM -0400, Steven Walter wrote:
> During the first suspend the chip would refuse to enter D3. Subsequent
> suspends worked okay. During resume the chip is commanded into D0.
> Doing so during initialization fixes the initial suspend.
>
> Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
> ---
> drivers/net/tulip/tulip_core.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/tulip/tulip_core.c b/drivers/net/tulip/tulip_core.c
> index 3810db9..bb8c0ee 100644
> --- a/drivers/net/tulip/tulip_core.c
> +++ b/drivers/net/tulip/tulip_core.c
> @@ -1380,6 +1380,13 @@ static int __devinit tulip_init_one (struct pci_dev *pdev,
> return i;
> }
>
> + /* The chip will fail to enter a low-power state later unless
> + * first explicitly commanded into D0 */
> + if (pci_set_power_state(pdev, PCI_D0)) {
> + printk (KERN_ERR PFX
My only quibble is this message really isn't "KERN_ERR" worthy.
Can you explain why you think this should be ERR and not say, KERN_NOTICE?
(I'm looking at the definitions in include/linux/kernel.h of 2.6 source tree.)
If you want to repost with KERN_NOTICE, please include my S-O-B: line above.
thanks,
grant
> + "Failed to set power state to D0\n");
> + }
> +
> irq = pdev->irq;
>
> /* alloc_etherdev ensures aligned and zeroed private structures */
> --
> 1.6.3.3
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH 1/2] tulip: explicity set to D0 power state during init
[not found] <AANLkTilr33y7rlJpjto5blK4wXKaVst1O4IM0JgPNP7B@mail.gmail.com>
@ 2010-06-01 3:11 ` Steven Walter
2010-06-01 7:18 ` David Miller
0 siblings, 1 reply; 4+ messages in thread
From: Steven Walter @ 2010-06-01 3:11 UTC (permalink / raw)
To: grundler, kyle, netdev; +Cc: Steven Walter
During the first suspend the chip would refuse to enter D3. Subsequent
suspends worked okay. During resume the chip is commanded into D0.
Doing so during initialization fixes the initial suspend.
Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
---
drivers/net/tulip/tulip_core.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/net/tulip/tulip_core.c b/drivers/net/tulip/tulip_core.c
index 3810db9..ec013c2 100644
--- a/drivers/net/tulip/tulip_core.c
+++ b/drivers/net/tulip/tulip_core.c
@@ -1380,6 +1380,13 @@ static int __devinit tulip_init_one (struct pci_dev *pdev,
return i;
}
+ /* The chip will fail to enter a low-power state later unless
+ * first explicitly commanded into D0 */
+ if (pci_set_power_state(pdev, PCI_D0)) {
+ printk (KERN_NOTICE PFX
+ "Failed to set power state to D0\n");
+ }
+
irq = pdev->irq;
/* alloc_etherdev ensures aligned and zeroed private structures */
--
1.6.3.3
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 1/2] tulip: explicity set to D0 power state during init
2010-06-01 3:11 ` [PATCH 1/2] tulip: explicity set to D0 power state during init Steven Walter
@ 2010-06-01 7:18 ` David Miller
0 siblings, 0 replies; 4+ messages in thread
From: David Miller @ 2010-06-01 7:18 UTC (permalink / raw)
To: stevenrwalter; +Cc: grundler, kyle, netdev
From: Steven Walter <stevenrwalter@gmail.com>
Date: Mon, 31 May 2010 23:11:53 -0400
> During the first suspend the chip would refuse to enter D3. Subsequent
> suspends worked okay. During resume the chip is commanded into D0.
> Doing so during initialization fixes the initial suspend.
>
> Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
> Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
Applied.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-06-01 7:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTilr33y7rlJpjto5blK4wXKaVst1O4IM0JgPNP7B@mail.gmail.com>
2010-06-01 3:11 ` [PATCH 1/2] tulip: explicity set to D0 power state during init Steven Walter
2010-06-01 7:18 ` David Miller
2010-05-31 22:34 Steven Walter
2010-06-01 1:00 ` Grant Grundler
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).