From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: David Dillow <dave@thedillows.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] 2.6.25 typhoon_resume - remove call to start_queue
Date: Fri, 25 Apr 2008 02:01:45 -0400 [thread overview]
Message-ID: <481173C9.2080509@pobox.com> (raw)
In-Reply-To: <20080421044415.GB15080@colo.lackof.org>
Grant Grundler wrote:
> Jeff,
>
> While trying to fix http://bugzilla.kernel.org/show_bug.cgi?id=8952
> I looked at a few other drivers to figure out what drivers _should_
> be doing for suspend/resume. I noticed typhoon driver is likely doing
> more than it needs to. Patch below is untested since I don't have the HW.
>
> Suspend/resume code across NIC drivers is fairly inconsistent.
> And I couldn't find any documentation on what the canonical sequence
> NICs need to do for suspend or resume. Is there any?
>
> Barring contrary advice, I'm going model the tulip suspend/resume
> fixes after tg3.c since a number of "modern" (< 5 years old) laptops
> have that and I'm silly enough to assume it works.
>
> thanks,
> grant
>
> ---
> Comments/code in netif_device_attach() suggest it is restarting the queue.
> Thus, typhoon_resume() doesn't need to call start_queue().
>
> Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
>
> diff --git a/drivers/net/typhoon.c b/drivers/net/typhoon.c
> index 333961b..c0dd25b 100644
> --- a/drivers/net/typhoon.c
> +++ b/drivers/net/typhoon.c
> @@ -2183,7 +2183,6 @@ typhoon_resume(struct pci_dev *pdev)
> }
>
> netif_device_attach(dev);
> - netif_start_queue(dev);
> return 0;
>
> reset:
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
applied
prev parent reply other threads:[~2008-04-25 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 4:44 [PATCH] 2.6.25 typhoon_resume - remove call to start_queue Grant Grundler
2008-04-21 5:57 ` David Miller
2008-04-21 14:35 ` David Dillow
2008-04-25 6:01 ` Jeff Garzik [this message]
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=481173C9.2080509@pobox.com \
--to=jgarzik@pobox.com \
--cc=dave@thedillows.org \
--cc=grundler@parisc-linux.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;
as well as URLs for NNTP newsgroup(s).