From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Uwe Bugla <uwe.bugla@gmx.de>, Takashi Iwai <tiwai@suse.de>,
Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] PNP: add ISAPnP MPU option quirks
Date: Sat, 10 May 2008 23:56:57 +0200 [thread overview]
Message-ID: <48261A29.9020308@keyaccess.nl> (raw)
In-Reply-To: <48261832.70006@keyaccess.nl>
On 10-05-08 23:48, Rene Herman wrote:
> PNP: add ISAPnP MPU option quirks.
>
> The AD181x and AZT230 chips don't support an IRQ-less MPU401 option
> but work fine without one. This adds (priority functional) IRQ-less
> options for each port option to help systems with few available IRQs.
>
> The AD1815 quirk can't use pnp_register_irq_resource() due to doubly
> penalizing the IRQ. Also, while not a practical issue due to no IRQ
> option being present for the dependents, this needs to add in front,
> not back.
>
> Doesn't use pnp_register_port_resource() for symetry with above.
>
> This does not delete the AD1815 independent option even though it
> should be empty after the IRQ transfer due to AD1816 coming with an
> empty but still present independent option by default.
>
> Was tested on AD1815, AD1816 and AZT230. The ALSA snd-ad1818a driver
Typo: AZT2320
> also support the AZT2002 ID for MPU401 but this doesn't as I was
> unable to test it.
>
> Signed-off-by: Rene Herman <rene.herman@gmail.com>
Rene.
prev parent reply other threads:[~2008-05-10 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 1:08 [PATCH 1/3] PNP: cleanup pnp_fixup_device() Rene Herman
2008-05-06 1:14 ` Rene Herman
2008-05-06 17:15 ` Bjorn Helgaas
2008-05-10 21:48 ` Rene Herman
[not found] ` <482614B3.4000908@gmail.com>
2008-05-10 21:48 ` [PATCH 2/3] PNP: add pnp_build_option() to the API Rene Herman
2008-05-10 21:48 ` [PATCH 3/3] PNP: add ISAPnP MPU option quirks Rene Herman
2008-05-10 21:56 ` Rene Herman [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=48261A29.9020308@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=uwe.bugla@gmx.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