From: matthieu castet <castet.matthieu-GANU6spQydw@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: akpm-3NddpPZAyC0@public.gmane.org, "Brown,
Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org
Subject: Re: [patch 5/5] PNPACPI: clean blacklist
Date: Tue, 13 Sep 2005 11:34:01 +0200 [thread overview]
Message-ID: <43269D09.506@free.fr> (raw)
In-Reply-To: <59D45D057E9702469E5775CBB56411F165A95B@pdsmsx406>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hi Shaohua,
Li, Shaohua wrote:
> Hi matthieu,
>
>>From: matthieu castet <castet.matthieu-GANU6spQydw@public.gmane.org>
> PNPACPI will call an 'acpi_register_gsi' for device's IRQ. If you remove
> PIC/TIMER from the list, their irq will be called. It sounds not safe to
> me, especially, in the ioapic mode.
Yes, I remembered this yesterday. I started to try to understand how
work acpi_register_gsi and if it was safe.
I was wondering if we shouln't call it only when a driver register the
device (to do something like pci_enable), but it will need pnp layer
modification.
I updated the patch in order to keep PIC and TIMER.
> It's meaningless to export PCI root to PNP layer to me. Could we remove
> it?
I know, but it is already in pnpbios and I believe we should only put
device that are problematic.
Thanks,
Matthieu
[-- Attachment #2: pnpacpi_clean_blacklist.patch --]
[-- Type: text/x-patch, Size: 1037 bytes --]
Index: linux-2.6.13rc/drivers/pnp/pnpacpi/core.c
===================================================================
--- linux-2.6.13rc.orig/drivers/pnp/pnpacpi/core.c 2005-08-28 19:26:35.000000000 +0200
+++ linux-2.6.13rc/drivers/pnp/pnpacpi/core.c 2005-09-13 11:31:15.000000000 +0200
@@ -27,12 +27,15 @@
static int num = 0;
+/* We need only to blacklist devices that have already an acpi driver that
+ * can't use pnp layer. We don't need to blacklist device that are directly
+ * used by the kernel (PCI root, ...), as it is harmless and there were
+ * already present in pnpbios. But there is an exception for devices that
+ * have irqs (PIC, Timer) because we call acpi_register_gsi.
+ * Finaly only devices that have a CRS method need to be in this list.
+ */
static char __initdata excluded_id_list[] =
- "PNP0C0A," /* Battery */
- "PNP0C0C,PNP0C0E,PNP0C0D," /* Button */
"PNP0C09," /* EC */
- "PNP0C0B," /* Fan */
- "PNP0A03," /* PCI root */
"PNP0C0F," /* Link device */
"PNP0000," /* PIC */
"PNP0100," /* Timer */
next prev parent reply other threads:[~2005-09-13 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 8:17 [patch 5/5] PNPACPI: clean blacklist Li, Shaohua
2005-09-13 9:34 ` matthieu castet [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 5:38 akpm-3NddpPZAyC0
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=43269D09.506@free.fr \
--to=castet.matthieu-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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