public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Bjorn Helgaas" <helgaas@kernel.org>,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Chen Yu" <yu.c.chen@intel.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Linux PCI" <linux-pci@vger.kernel.org>,
	"Alex Hung" <alexhung@gmail.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	"AceLan Kao" <acelan.kao@canonical.com>
Subject: Re: [PATCH v1 0/4] ACPI: scan: Handle generic system devices directly
Date: Tue, 16 Dec 2025 08:03:02 -0600	[thread overview]
Message-ID: <e019cbdb-5152-40fc-a3c8-76b360fdd6ad@kernel.org> (raw)
In-Reply-To: <7888874.EvYhyI6sBW@rafael.j.wysocki>

On 12/15/25 7:31 AM, Rafael J. Wysocki wrote:
> Hi All,
> 
> As per the changelog of patch [1/4], there is a long-standing problem with ACPI
> device enumeration that if the given device has a compatible ID which is one of
> the generic system resource device IDs (PNP0C01 and PNP0C02), it will be claimed
> by the PNP scan handler and it will not be represented as a platform device, so
> it cannot be handled by a platform driver.
> 
> Obviously, PNP0C01 and PNP0C02 need to be removed from acpi_pnp_device_ids[] to
> address this problem, but it cannot be done without making any other changes
> due to the way the legacy PNP system driver works (see the changelog of patch
> [1/4] for details) and the approach used in patch [1/4] is to reserve the
> "motherboard resources" directly in the ACPI core without creating platform
> devices for "system" devices (whose _HID is either PNP0C01 or PNP0C02).  The
> new code doing works along the lines of the PNP system driver to avoid
> regressions.
> 
> The remaining patches in the series are simplifications that can be done on
> top of the first one.
> 
> Patches [2-3/4] remove platform device creation code from Intel HID and VBTN
> drivers that don't need to worry about _CID including PNP0C02 any more.
> 
> Patch [4/4] drops acpi_nonpnp_device_ids[] that was added as a workaround for
> the issue at hand in the first place.
> 
> Thanks!
> 
> 
> 
> 

For the series:

Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>

      parent reply	other threads:[~2025-12-16 14:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 13:31 [PATCH v1 0/4] ACPI: scan: Handle generic system devices directly Rafael J. Wysocki
2025-12-15 13:34 ` [PATCH v1 1/4] ACPI: PNP: Drop PNP0C01 and PNP0C02 from acpi_pnp_device_ids[] Rafael J. Wysocki
2025-12-15 21:18   ` Mario Limonciello
2025-12-16 11:44     ` Rafael J. Wysocki
2025-12-28 19:11   ` Andy Shevchenko
2025-12-29 13:12     ` Rafael J. Wysocki
2025-12-29 13:58       ` Andy Shevchenko
2025-12-15 13:35 ` [PATCH v1 2/4] platform/x86/intel/hid: Stop creating a platform device Rafael J. Wysocki
2025-12-28 19:13   ` Andy Shevchenko
2025-12-29 13:07     ` Rafael J. Wysocki
2025-12-29 13:59       ` Andy Shevchenko
2025-12-15 13:35 ` [PATCH v1 3/4] platform/x86/intel/vbtn: " Rafael J. Wysocki
2025-12-28 19:14   ` Andy Shevchenko
2025-12-15 13:36 ` [PATCH v1 4/4] ACPI: PNP: Drop acpi_nonpnp_device_ids[] Rafael J. Wysocki
2025-12-16 14:03 ` Mario Limonciello [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=e019cbdb-5152-40fc-a3c8-76b360fdd6ad@kernel.org \
    --to=superm1@kernel.org \
    --cc=acelan.kao@canonical.com \
    --cc=alexhung@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hansg@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=yu.c.chen@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