[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230609152507.77649-1-andriy.shevchenko@linux.intel.com>
Date: Fri, 9 Jun 2023 18:25:04 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Damien Le Moal <dlemoal@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org
Cc: Hans de Goede <hdegoede@...hat.com>, Jens Axboe <axboe@...nel.dk>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>,
Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>
Subject: [PATCH v1 0/3] device property: Introduce device_is_compatible()
Introduce a new helper to tell if device (node) is compatible to the
given string value. This will help some drivers to get rid of unneeded
OF APIs/etc and in may help others to be agnostic to OF/ACPI.
While doing it, I have noticed that ACPI_DEVICE_CLASS() macro seems
defined in unsuitable location. Move it to the better one.
Last patch is an example of what the first two are doing.
The entire series can go, I believe, via ACPI (linux-pm) tree in case
the last patch gets tag from the respective maintainer.
Andy Shevchenko (3):
ACPI: Move ACPI_DEVICE_CLASS() to mod_devicetable.h
device property: Implement device_is_compatible()
ata: ahci_platform: Make code agnostic to OF/ACPI
drivers/ata/ahci_platform.c | 6 +++---
include/linux/acpi.h | 14 --------------
include/linux/mod_devicetable.h | 13 +++++++++++++
include/linux/property.h | 5 +++++
4 files changed, 21 insertions(+), 17 deletions(-)
--
2.40.0.1.gaa8946217a0b
Powered by blists - more mailing lists