From: Bob Copeland <me@bobcopeland.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
ath5k-devel@venema.h4ckr.net,
Alan Stern <stern@rowland.harvard.edu>,
linux-pci@vger.kernel.org
Subject: Re: [ath5k-devel] [linux-pm] PCI hotplug v.s. suspend
Date: Mon, 15 Jun 2009 21:01:01 -0400 [thread overview]
Message-ID: <20090616010101.GA11412@hash.localnet> (raw)
In-Reply-To: <200906152158.30989.rjw@sisk.pl>
On Mon, Jun 15, 2009 at 09:58:30PM +0200, Rafael J. Wysocki wrote:
> On Monday 15 June 2009, Alan Stern wrote:
> > I'm not sure whether the example is trustworthy. There was some
> > discussion quite a while ago regarding whether drivers should free
> > their IRQs during suspend, but I don't remember what the outcome was.
>
> No, they shouldn't.
>
> That's why we do the entire suspend_device_irqs() thing etc.
So, ath5k needs something like the following?
diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
index 55f7de0..0107cd6 100644
--- a/drivers/net/wireless/ath/ath5k/base.c
+++ b/drivers/net/wireless/ath/ath5k/base.c
@@ -665,7 +665,6 @@ ath5k_pci_suspend(struct pci_dev *pdev, pm_message_t state)
ath5k_led_off(sc);
- free_irq(pdev->irq, sc);
pci_save_state(pdev);
pci_disable_device(pdev);
pci_set_power_state(pdev, PCI_D3hot);
@@ -686,18 +685,8 @@ ath5k_pci_resume(struct pci_dev *pdev)
if (err)
return err;
- err = request_irq(pdev->irq, ath5k_intr, IRQF_SHARED, "ath", sc);
- if (err) {
- ATH5K_ERR(sc, "request_irq failed\n");
- goto err_no_irq;
- }
-
ath5k_led_enable(sc);
return 0;
-
-err_no_irq:
- pci_disable_device(pdev);
- return err;
}
#endif /* CONFIG_PM */
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-06-16 1:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:55 PCI hotplug v.s. suspend Alan Jenkins
2009-06-15 13:58 ` Alan Stern
2009-06-15 13:58 ` [linux-pm] " Alan Stern
2009-06-15 14:03 ` Alan Jenkins
2009-06-15 14:03 ` [linux-pm] " Alan Jenkins
2009-06-15 14:37 ` Alan Stern
2009-06-15 19:58 ` Rafael J. Wysocki
2009-06-15 20:34 ` Alan Stern
2009-06-15 20:51 ` Rafael J. Wysocki
2009-06-15 20:51 ` [linux-pm] " Rafael J. Wysocki
2009-06-15 20:34 ` Alan Stern
2009-06-16 1:01 ` [ath5k-devel] " Bob Copeland
2009-06-16 1:01 ` Bob Copeland [this message]
2009-06-18 11:51 ` [ath5k-devel] [linux-pm] " Alan Jenkins
2009-06-18 18:45 ` Alan Stern
2009-06-18 21:18 ` [ath5k-devel] " Alan Jenkins
2009-06-18 21:18 ` [ath5k-devel] [linux-pm] " Alan Jenkins
2009-06-19 8:34 ` [ath5k-devel] " Alan Jenkins
2009-06-19 8:34 ` [ath5k-devel] [linux-pm] " Alan Jenkins
2009-06-19 11:08 ` [ath5k-devel] " Bob Copeland
2009-06-19 11:08 ` [ath5k-devel] [linux-pm] " Bob Copeland
2009-06-18 18:45 ` [ath5k-devel] " Alan Stern
2009-06-18 11:51 ` Alan Jenkins
2009-06-15 19:58 ` Rafael J. Wysocki
2009-06-15 14:37 ` Alan Stern
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=20090616010101.GA11412@hash.localnet \
--to=me@bobcopeland.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.