From: Kartik Rajput <kkartik@nvidia.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: lenb@kernel.org, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] ACPI: bus: Use OF match data for PRP0001 matched devices
Date: Thu, 8 Jan 2026 16:48:14 +0530 [thread overview]
Message-ID: <3207ed15-cdaa-40d4-bce2-9add6a7bc3e8@nvidia.com> (raw)
In-Reply-To: <aV5T3Lh4TxvpOZi4@kekkonen.localdomain>
On 07/01/26 18:08, Sakari Ailus wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Kartik,
>
> On Wed, Jan 07, 2026 at 05:33:18PM +0530, Kartik Rajput wrote:
>> When a device is matched via PRP0001, the driver's OF (DT) match table
>> must be used to obtain the device match data. If a driver provides both
>> an acpi_match_table and an of_match_table, the current
>> acpi_device_get_match_data() path consults the driver's acpi_match_table
>> and returns NULL (no ACPI ID matches).
>>
>> Explicitly detect PRP0001 and fetch match data from the driver's
>> of_match_table via acpi_of_device_get_match_data().
>>
>> Fixes: 886ca88be6b3 ("ACPI / bus: Respect PRP0001 when retrieving device match data")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
>> ---
>> Changes in v2:
>> * Fix build errors.
>
> Thanks for the update.
>
>> ---
>> drivers/acpi/bus.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
>> index 5e110badac7b..6658c4339656 100644
>> --- a/drivers/acpi/bus.c
>> +++ b/drivers/acpi/bus.c
>> @@ -1031,8 +1031,9 @@ const void *acpi_device_get_match_data(const struct device *dev)
>> {
>> const struct acpi_device_id *acpi_ids = dev->driver->acpi_match_table;
>> const struct acpi_device_id *match;
>> + struct acpi_device *adev = ACPI_COMPANION(dev);
>>
>> - if (!acpi_ids)
>> + if (!strcmp(ACPI_DT_NAMESPACE_HID, acpi_device_hid(adev)))
>
> I'd swap the arguments to have the static one on the right, i.e.
>
> if (!strcmp(acpi_device_hid(adev), ACPI_DT_NAMESPACE_HID))
>
> The patch looks good apart from that IMO.
>
>> return acpi_of_device_get_match_data(dev);
>>
>> match = acpi_match_device(acpi_ids, dev);
>
> --
> Kind regards,
>
> Sakari Ailus
Hi Sakari,
Thanks for reviewing the patch!
I will make this change in the next version of this patch.
Thanks,
Kartik
next prev parent reply other threads:[~2026-01-08 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 12:03 [PATCH v2] ACPI: bus: Use OF match data for PRP0001 matched devices Kartik Rajput
2026-01-07 12:38 ` Sakari Ailus
2026-01-08 11:18 ` Kartik Rajput [this message]
2026-01-07 12:54 ` Rafael J. Wysocki
2026-01-08 11:23 ` Kartik Rajput
2026-01-07 15:47 ` Andy Shevchenko
2026-01-08 12:27 ` Kartik Rajput
2026-01-08 18:05 ` Andy Shevchenko
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=3207ed15-cdaa-40d4-bce2-9add6a7bc3e8@nvidia.com \
--to=kkartik@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jonathanh@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.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