[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171129135536.GD32417@localhost>
Date: Wed, 29 Nov 2017 19:25:36 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Sinan Kaya <okaya@...eaurora.org>, dmaengine@...r.kernel.org,
timur@...eaurora.org,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org, robin.murphy@....com,
linux-kernel@...r.kernel.org,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH V3 2/4] ACPI / bus: introduce
acpi_device_get_match_data() function
On Sun, Nov 12, 2017 at 01:14:12AM +0100, Rafael J. Wysocki wrote:
> On Friday, November 10, 2017 3:35:41 AM CET Sinan Kaya wrote:
> > +linux-acpi@...r.kernel.org, +Rafael
>
> Thanks!
>
> > On 11/9/2017 9:32 PM, Sinan Kaya wrote:
> > > OF has of_device_get_match_data() function to extract driver specific data
> > > structure. Add a similar function for ACPI.
> > >
> > > Signed-off-by: Sinan Kaya <okaya@...eaurora.org>
> > > ---
> > > drivers/acpi/bus.c | 12 ++++++++++++
> > > include/linux/acpi.h | 6 ++++++
> > > 2 files changed, 18 insertions(+)
> > >
> > > diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> > > index 4d0979e..da29c10 100644
> > > --- a/drivers/acpi/bus.c
> > > +++ b/drivers/acpi/bus.c
> > > @@ -785,6 +785,18 @@ const struct acpi_device_id *acpi_match_device(const struct acpi_device_id *ids,
> > > }
> > > EXPORT_SYMBOL_GPL(acpi_match_device);
> > >
> > > +void *acpi_device_get_match_data(const struct device *dev)
> > > +{
> > > + const struct acpi_device_id *match;
> > > +
> > > + match = acpi_match_device(dev->driver->acpi_match_table, dev);
> > > + if (!match)
> > > + return NULL;
> > > +
> > > + return (void *)match->driver_data;
> > > +}
> > > +EXPORT_SYMBOL_GPL(acpi_device_get_match_data);
>
> While I understand that the name follows the OF convention, I have some
> doubts on whether it is the best one.
Perhpas acpi_get_match_data() ?
--
~Vinod
Powered by blists - more mailing lists