From: Jeff Garzik <jgarzik@pobox.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: netdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: de2104x: fix power management
Date: Sat, 25 Sep 2010 13:16:56 -0400 [thread overview]
Message-ID: <4C9E2E88.3080101@pobox.com> (raw)
In-Reply-To: <201009251157.07197.linux@rainbow-software.org>
On 09/25/2010 05:57 AM, Ondrej Zary wrote:
> At least my 21041 cards come out of suspend with bus mastering disabled so
> they did not work after resume(no data transferred).
> After adding pci_set_master(), the driver oopsed immediately on resume -
> because de_clean_rings() is called on suspend but de_init_rings() call
> was missing in resume.
>
> Also disable link (reset SIA) before sleep (de4x5 does this too).
>
> Signed-off-by: Ondrej Zary<linux@rainbow-software.org>
>
> --- linux-2.6.36-rc3-/drivers/net/tulip/de2104x.c 2010-09-25 11:27:26.000000000 +0200
> +++ linux-2.6.36-rc3/drivers/net/tulip/de2104x.c 2010-09-25 11:29:22.000000000 +0200
> @@ -1231,6 +1231,7 @@ static void de_adapter_sleep (struct de_
> if (de->de21040)
> return;
>
> + dw32(CSR13, 0); /* Reset phy */
> pci_read_config_dword(de->pdev, PCIPM,&pmctl);
> pmctl |= PM_Sleep;
> pci_write_config_dword(de->pdev, PCIPM, pmctl);
> @@ -2166,6 +2167,8 @@ static int de_resume (struct pci_dev *pd
> dev_err(&dev->dev, "pci_enable_device failed in resume\n");
> goto out;
> }
> + pci_set_master(pdev);
> + de_init_rings(de);
> de_init_hw(de);
> out_attach:
> netif_device_attach(dev);
Acked-by: Jeff Garzik <jgarzik@redhat.com>
IMO suspend/resume could use another look; if netif_running is false
(interface is down), de2104x does not put the PCI device to sleep, which
seems strange.
I also wonder if rtnl_lock() couldn't be eliminated, as other net
drivers don't need it in suspend/resume.
next prev parent reply other threads:[~2010-09-25 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 9:57 de2104x: fix power management Ondrej Zary
2010-09-25 17:16 ` Jeff Garzik [this message]
2010-09-26 22:49 ` 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=4C9E2E88.3080101@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=netdev@vger.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