From: "Zhang, Rui" <rui.zhang@intel.com>
To: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chen, Yu C" <yu.c.chen@intel.com>
Subject: Re: [PATCH v1] ACPI: PNP: Introduce list of known non-PNP devices
Date: Wed, 11 Jan 2023 07:25:10 +0000 [thread overview]
Message-ID: <c9acadcd3e19e7dafb8ba4cf1f0abb0200b18b1a.camel@intel.com> (raw)
In-Reply-To: <12149290.O9o76ZdvQC@kreacher>
On Tue, 2023-01-10 at 18:58 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> In some cases, PNP device IDs from acpi_pnp_device_ids[] are returned
> by
> _CID for devices for which matching platform drivers are present in
> the
> kernel and should be bound to them. However, the IDs coming from
> _CID
> cause the PNP scan handler to attach to those devices which prevents
> platform device objects from being created for them.
>
> Address this by introducing a list of known non-PNP device IDs into
> acpi_pnp.c such that if a device ID is there in that list, it cannot
> be
> attached to by the PNP scan handler and add the platform runtime
> update
> and telemetry device IDs to that list to start with.
>
> Reported-by: Chen Yu <yu.c.chen@intel.com>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/acpi/acpi_pnp.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> Index: linux-pm/drivers/acpi/acpi_pnp.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/acpi_pnp.c
> +++ linux-pm/drivers/acpi/acpi_pnp.c
> @@ -348,10 +348,22 @@ static bool acpi_pnp_match(const char *i
> return false;
> }
>
> +/*
> + * If one of the device IDs below is present in the list of device
> IDs of a
> + * given ACPI device object, the PNP scan handler will not attach to
> that
> + * object, because there is a proper non-PNP driver in the kernel
> for the
> + * device represented by it.
> + */
> +static const struct acpi_device_id acpi_nonpnp_device_ids[] = {
> + {"INTC1080"},
> + {"INTC1081"},
> + {""},
> +};
> +
> static int acpi_pnp_attach(struct acpi_device *adev,
> const struct acpi_device_id *id)
> {
> - return 1;
> + return !!acpi_match_device_ids(adev, acpi_nonpnp_device_ids);
acpi_match_device_ids() returns True if the id matches, and in this
case, acpi_pnp_attach() should return false, right?
thanks,
rui
> }
>
> static struct acpi_scan_handler acpi_pnp_handler = {
>
>
>
next prev parent reply other threads:[~2023-01-11 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 17:58 [PATCH v1] ACPI: PNP: Introduce list of known non-PNP devices Rafael J. Wysocki
2023-01-11 7:25 ` Zhang, Rui [this message]
2023-01-11 8:02 ` Zhang, Rui
2023-01-11 8:07 ` Zhang, Yang5
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=c9acadcd3e19e7dafb8ba4cf1f0abb0200b18b1a.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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