[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231027081855.GK3208943@black.fi.intel.com>
Date: Fri, 27 Oct 2023 11:18:55 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Raag Jadav <raag.jadav@...el.com>
Cc: rafael@...nel.org, len.brown@...el.com,
andriy.shevchenko@...ux.intel.com, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
mallikarjunappa.sangannavar@...el.com, bala.senthil@...el.com
Subject: Re: [PATCH v2] ACPI: LPSS: use acpi_dev_uid_match() for matching _UID
On Thu, Oct 26, 2023 at 02:03:35PM +0530, Raag Jadav wrote:
> Now that we have a standard ACPI helper, we can use acpi_dev_uid_match()
> for matching _UID as per the original logic before commit 2a036e489eb1
> ("ACPI: LPSS: Refactor _UID handling to use acpi_dev_uid_to_integer()"),
> instead of treating it as an integer.
>
> Signed-off-by: Raag Jadav <raag.jadav@...el.com>
> Acked-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
The change still looks good to me, however I wonder if we could maybe
improve acpi_dev_uid_match() to support both data types possible for
_UID? This of course is separate patch (unless there are objections).
There is the _Generic() thing and I think that can be used to make
acpi_dev_uid_match()
which takes either u64 (or maybe even unsigned int) or const char * and
based on that picks the correct implementation. Not sure if that's
possible, did not check but it would allow us to use one function
everywhere instead of acpi_dev_uid_to_integer() and
acpi_dev_uid_match().
Powered by blists - more mailing lists