From: Raag Jadav <raag.jadav@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: rafael@kernel.org, len.brown@intel.com,
andriy.shevchenko@linux.intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
mallikarjunappa.sangannavar@intel.com, bala.senthil@intel.com
Subject: Re: [PATCH v2] ACPI: LPSS: use acpi_dev_uid_match() for matching _UID
Date: Fri, 27 Oct 2023 19:51:18 +0300 [thread overview]
Message-ID: <ZTvqYwFWm9PQeKIU@black.fi.intel.com> (raw)
In-Reply-To: <20231027142856.GL3208943@black.fi.intel.com>
On Fri, Oct 27, 2023 at 05:28:56PM +0300, Mika Westerberg wrote:
> On Fri, Oct 27, 2023 at 05:17:12PM +0300, Raag Jadav wrote:
> > Or perhaps something like,
> >
> > bool acpi_dev_uid_match(struct acpi_device *adev, const void *uid2, enum uid_type type)
> > {
> > u64 uid1_d, uid2_d;
> >
> > if (type == UID_TYPE_STR) {
> > char *uid2_s = (char *)uid2;
> > if (!(uid2_s && !kstrtou64(uid2_s, 0, &uid2_d)))
> > return false;
> > } else if (type == UID_TYPE_INT) {
> > u64 *uid2_p;
> > uid2_p = (u64 *)uid2;
> > uid2_d = *uid2_p;
> > } else {
> > return false;
> > }
> >
> > if (!acpi_dev_uid_to_integer(adev, &uid1_d) && uid1_d == uid2_d)
> > return true;
> > else
> > return false;
> > }
> >
> > Although this looks unnecessarily hideous.
>
> Indeed, but using the _Generic() you should be able to have
> a single acpi_dev_uid_match() to work for either type so:
>
> acpi_dev_uid_match(adev, "1")
>
> and
>
> acpi_dev_uid_match(adev, 1)
>
> would both work with type checkings etc.
>
> Not sure if this is worth the trouble though.
Well, in that case we can probably try both and hope for the best ;)
bool acpi_dev_uid_match(struct acpi_device *adev, const char *uid2)
{
const char *uid1 = acpi_device_uid(adev);
u64 uid1_d;
return uid1 && uid2 && (!strcmp(uid1, uid2) ||
(!kstrtou64(uid1, 0, &uid1_d) && uid1_d == (u64)uid2));
}
But I'm guessing the compiler wouldn't be very happy about this.
Raag
next prev parent reply other threads:[~2023-10-27 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:33 [PATCH v2] ACPI: LPSS: use acpi_dev_uid_match() for matching _UID Raag Jadav
2023-10-27 8:18 ` Mika Westerberg
2023-10-27 10:11 ` Raag Jadav
2023-10-27 14:17 ` Raag Jadav
2023-10-27 14:28 ` Mika Westerberg
2023-10-27 16:51 ` Raag Jadav [this message]
2023-10-27 17:19 ` Rafael J. Wysocki
2023-10-27 17:40 ` Rafael J. Wysocki
2023-10-28 8:58 ` Raag Jadav
2023-10-30 10:12 ` Andy Shevchenko
2023-10-30 16:00 ` Raag Jadav
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=ZTvqYwFWm9PQeKIU@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bala.senthil@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
/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