From: Zhang Rui <rui.zhang@intel.com>
To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bhelgaas@google.com, matthew.garrett@nebula.com,
rafael.j.wysocki@intel.com, dmitry.torokhov@gmail.com,
Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH V4 04/11] ACPI: remove unsupported serial PNP ids from acpi pnp scan handler id lsit
Date: Mon, 17 Mar 2014 15:49:33 +0800 [thread overview]
Message-ID: <1395042580-3344-5-git-send-email-rui.zhang@intel.com> (raw)
In-Reply-To: <1395042580-3344-1-git-send-email-rui.zhang@intel.com>
The "serial" pnp driver supports some unknown PNP modems (PNPCXXX/PNPDXXX)
by matching magic strings in the pnp device name or the pnp device card name.
ACPI enumerated PNP device neither supports pnp card, nor supports those magic
strings in its device name, which means this mechamism never works for ACPI
enumerated PNPCXXX/PNPDXXX devices.
So it is safe to remove those two ids from the ACPI pnp scan handler id list.
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
---
drivers/acpi/acpi_pnp.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/acpi/acpi_pnp.c b/drivers/acpi/acpi_pnp.c
index 8c14006..8cf7d9d 100644
--- a/drivers/acpi/acpi_pnp.c
+++ b/drivers/acpi/acpi_pnp.c
@@ -300,8 +300,6 @@ static const struct acpi_device_id acpi_pnp_device_ids[] = {
{"LTS0001"}, /* LG C1 EXPRESS DUAL (C1-PB11A3) touch screen (actually a FUJ02E6 in disguise) */
{"WCI0003"}, /* Rockwell's (PORALiNK) 33600 INT PNP */
{"WEC1022"}, /* Winbond CIR port, should not be probed. We should keep track of it to prevent the legacy serial driver from probing it */
- {"PNPCXXX"}, /* Unknown PnP modems */
- {"PNPDXXX"}, /* More unknown PnP modems */
/* scl200wdt */
{"NSC0800"}, /* National Semiconductor PC87307/PC97307 watchdog component */
/* mpu401 */
--
1.7.9.5
next prev parent reply other threads:[~2014-03-17 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 7:49 [PATCH V4 00/11] ACPI: change the way of enumerating PNPACPI/Platform devices Zhang Rui
2014-03-17 7:49 ` [PATCH V4 01/11] ACPI: introduce .match() callback for ACPI scan handler Zhang Rui
2014-03-17 7:49 ` [PATCH V4 02/11] PNPACPI: use whilte list for pnpacpi device enumeration Zhang Rui
2014-03-17 7:49 ` [PATCH V4 03/11] ACPI: remove ids that does not comply with the ACPI PNP id rule Zhang Rui
2014-03-17 7:49 ` Zhang Rui [this message]
2014-03-17 7:49 ` [PATCH V4 05/11] ACPI: check and enumerate CMOS RTC devices explicitly Zhang Rui
2014-03-17 7:49 ` [PATCH V4 06/11] ACPI: introduce platform_id flag Zhang Rui
2014-03-17 7:49 ` [PATCH V4 07/11] ACPI: use platform bus as the default bus for _HID enumeration Zhang Rui
2014-03-24 2:00 ` Rafael J. Wysocki
2014-03-24 4:06 ` Zhang Rui
2014-03-31 5:24 ` Zhang Rui
2014-03-17 7:49 ` [PATCH V4 08/11] ACPI: introduce dummy lpss scan handler Zhang Rui
2014-03-17 7:49 ` [PATCH V4 09/11] ACPI: introduce acpi platform exclude id list Zhang Rui
2014-03-17 7:49 ` [PATCH V4 10/11] ACPI: introduce dummy container scan handler Zhang Rui
2014-03-17 7:49 ` [PATCH V4 11/11] ACPI: introduce dummy memory hotplug " Zhang Rui
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=1395042580-3344-5-git-send-email-rui.zhang@intel.com \
--to=rui.zhang@intel.com \
--cc=bhelgaas@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=rafael.j.wysocki@intel.com \
/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).