From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Pavel Machek <pavel@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
alsa-devel@alsa-project.org
Subject: Re: [ACPI] Re: [PATCH] 2.6.13-rc3-git5: fix Bug #4416 (1/2)
Date: Thu, 28 Jul 2005 10:43:13 +0200 [thread overview]
Message-ID: <200507281043.14697.rjw@sisk.pl> (raw)
In-Reply-To: <s5hr7djtkvo.wl%tiwai@suse.de>
Hi,
On Thursday, 28 of July 2005 10:06, Takashi Iwai wrote:
> At Wed, 27 Jul 2005 22:52:49 +0200,
> Pavel Machek wrote:
> >
> > Hi!
> >
> > > > The following patch adds free_irq() and request_irq() to the suspend and
> > > > resume, respectively, routines in the snd_intel8x0 driver.
> > >
> > > The patch looks OK to me although I have some concerns.
> > >
> > > - The error in resume can't be handled properly.
> > >
> > > What should we do for the error of request_irq()?
> > >
> > > - Adding this to all drivers seem too much.
> >
> > There's probably no other way. Talk to Len Brown.
> >
> > > We just need to stop the irq processing until resume, so something
> > > like suspend_irq(irq, dev_id) and resume_irq(irq, dev_id) would be
> > > more uesful?
> >
> > Its more complex than that. Irq numbers may change during resume.
>
> Hmm, then the patch looks wrong. It assumes that the irq number is
> as same as before suspend.
Well, that''s the theory, but frankly I don't see a practical reason. I have never
seen this happening. Practically, for this to happen, you'll have to reconfigure
the BIOS accross suspend/resume which is dangerous anyway.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-07-28 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 10:47 [PATCH] 2.6.13-rc3-git5: fix Bug #4416 (0/2) Rafael J. Wysocki
[not found] ` <200507261247.05684.rjw-KKrjLPT3xs0@public.gmane.org>
2005-07-26 10:51 ` [PATCH] 2.6.13-rc3-git5: fix Bug #4416 (1/2) Rafael J. Wysocki
[not found] ` <200507261251.48291.rjw-KKrjLPT3xs0@public.gmane.org>
2005-07-27 8:53 ` [Alsa-devel] " Takashi Iwai
2005-07-27 20:52 ` [ACPI] " Pavel Machek
[not found] ` <20050727205249.GA708-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2005-07-28 8:06 ` Re: [Alsa-devel] " Takashi Iwai
[not found] ` <s5hr7djtkvo.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2005-07-28 8:31 ` Pavel Machek
2005-07-28 8:37 ` [ACPI] " Shaohua Li
2005-07-28 8:43 ` Rafael J. Wysocki [this message]
[not found] ` <200507281043.14697.rjw-KKrjLPT3xs0@public.gmane.org>
2005-07-28 8:48 ` Re: [Alsa-devel] " Shaohua Li
[not found] ` <1122540486.2903.8.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-07-28 11:18 ` Rafael J. Wysocki
2005-07-26 10:54 ` [PATCH] 2.6.13-rc3-git5: fix Bug #4416 (2/2) Rafael J. Wysocki
[not found] ` <200507261254.05507.rjw-KKrjLPT3xs0@public.gmane.org>
2005-07-26 12:25 ` Carl-Daniel Hailfinger
[not found] ` <42E62BB0.6010409-hi6Y0CQ0nG0@public.gmane.org>
2005-07-26 21:02 ` Rafael J. Wysocki
[not found] ` <200507262302.37488.rjw-KKrjLPT3xs0@public.gmane.org>
2005-07-26 21:11 ` Peter Buckingham
[not found] ` <42E6A6E7.5000402-1HAy0Et5u51Wk0Htik3J/w@public.gmane.org>
2005-07-26 21:37 ` Rafael J. Wysocki
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=200507281043.14697.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=tiwai@suse.de \
/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