Message ID | 20231020084732.17130-1-raag.jadav@intel.com |
---|---|
Headers | show |
Series | Refine _UID references across kernel | expand |
On Fri, Oct 20, 2023 at 02:17:25PM +0530, Raag Jadav wrote: > Introduce acpi_dev_uid_match() helper that matches the device with > supplied _UID string. ... > +/** > + * acpi_dev_uid_match - Match device by supplied UID > + * @adev: ACPI device to match. > + * @uid2: Unique ID of the device, pass NULL to not check _UID. > + * > + * Matches UID in @adev with given @uid2. Absence of @uid2 will be treated as > + * a match. If user wants to validate @uid2, it should be done before calling > + * this function. This behaviour is as needed by most of its current users. The "current" internally I applied to the result of the series. So reading this again I think the better wording is "potential". > + * > + * Returns: > + * - %true if matches or @uid2 is NULL. > + * - %false otherwise. > + */ ... > /** > * acpi_dev_hid_uid_match - Match device by supplied HID and UID > * @adev: ACPI device to match. > * @hid2: Hardware ID of the device. > * @uid2: Unique ID of the device, pass NULL to not check _UID. > * > - * Matches HID and UID in @adev with given @hid2 and @uid2. > - * Returns true if matches. > + * Matches HID and UID in @adev with given @hid2 and @uid2. Absence of @uid2 > + * will be treated as a match. If user wants to validate @uid2, it should be > + * done before calling this function. This behaviour is as needed by most of > + * its current users. Ditto. > + * Returns: > + * - %true if matches or @uid2 is NULL. > + * - %false otherwise. > */
On Fri, Oct 20, 2023 at 02:17:29PM +0530, Raag Jadav wrote: > Convert manual _UID references to use standard ACPI helpers. Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> ... > - if (!adev->pnp.unique_id || > - strcmp(adev->pnp.unique_id, override_status_ids[i].uid)) > + if (!acpi_dev_uid_match(adev, override_status_ids[i].uid)) The check for NULL argument inside that API does not affect the behaviour as otherwise it will be a crash with the current implementation. > continue;
On Fri, 20 Oct 2023 14:17:25 +0530 Raag Jadav <raag.jadav@intel.com> wrote: > Introduce acpi_dev_uid_match() helper that matches the device with > supplied _UID string. > > Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > Signed-off-by: Raag Jadav <raag.jadav@intel.com> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > /** > * acpi_dev_hid_uid_match - Match device by supplied HID and UID > * @adev: ACPI device to match. > * @hid2: Hardware ID of the device. > * @uid2: Unique ID of the device, pass NULL to not check _UID. > * > - * Matches HID and UID in @adev with given @hid2 and @uid2. > - * Returns true if matches. > + * Matches HID and UID in @adev with given @hid2 and @uid2. Absence of @uid2 > + * will be treated as a match. If user wants to validate @uid2, it should be > + * done before calling this function. This behaviour is as needed by most of > + * its current users. If there are other other users that need different behavior are they buggy? Also what behavior is this referring to? I'd just drop the at last sentence as confusing and not adding much. > + * > + * Returns: > + * - %true if matches or @uid2 is NULL. > + * - %false otherwise. > */ > bool acpi_dev_hid_uid_match(struct acpi_device *adev, > const char *hid2, const char *uid2) > { > const char *hid1 = acpi_device_hid(adev); > - const char *uid1 = acpi_device_uid(adev); > > if (strcmp(hid1, hid2)) > return false; > > - if (!uid2) > - return true; > - > - return uid1 && !strcmp(uid1, uid2); > + return acpi_dev_uid_match(adev, uid2); > } > EXPORT_SYMBOL(acpi_dev_hid_uid_match); > > diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h > index 254685085c82..d1fe6446ffe0 100644 > --- a/include/acpi/acpi_bus.h > +++ b/include/acpi/acpi_bus.h > @@ -760,6 +760,7 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev) > adev->power.states[ACPI_STATE_D3_HOT].flags.explicit_set); > } > > +bool acpi_dev_uid_match(struct acpi_device *adev, const char *uid2); > bool acpi_dev_hid_uid_match(struct acpi_device *adev, const char *hid2, const char *uid2); > int acpi_dev_uid_to_integer(struct acpi_device *adev, u64 *integer); > > diff --git a/include/linux/acpi.h b/include/linux/acpi.h > index afd94c9b8b8a..db3a33e19c97 100644 > --- a/include/linux/acpi.h > +++ b/include/linux/acpi.h > @@ -787,6 +787,11 @@ static inline bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) > > struct acpi_device; > > +static inline bool acpi_dev_uid_match(struct acpi_device *adev, const char *uid2) > +{ > + return false; > +} > + > static inline bool > acpi_dev_hid_uid_match(struct acpi_device *adev, const char *hid2, const char *uid2) > {
On Fri, Oct 20, 2023 at 12:38 PM Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote: > > On Fri, Oct 20, 2023 at 02:17:29PM +0530, Raag Jadav wrote: > > Convert manual _UID references to use standard ACPI helpers. > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > > ... > > > - if (!adev->pnp.unique_id || > > - strcmp(adev->pnp.unique_id, override_status_ids[i].uid)) > > + if (!acpi_dev_uid_match(adev, override_status_ids[i].uid)) > > The check for NULL argument inside that API does not affect the behaviour as > otherwise it will be a crash with the current implementation. What current implementation do you mean, exactly?