[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfPvCD7xpp73jbya4ONN=wxpVGNpOfNeqZYjfyirms0PA@mail.gmail.com>
Date: Tue, 3 Jul 2018 20:41:00 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Srinath Mannam <srinath.mannam@...adcom.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, Ray Jui <ray.jui@...adcom.com>,
vladimir.olovyannikov@...adcom.com, vikram.prakash@...adcom.com,
scott.branden@...adcom.com,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] ACPI: bus: match of_device_id using acpi device
On Tue, Jul 3, 2018 at 12:22 PM, Srinath Mannam
<srinath.mannam@...adcom.com> wrote:
> This patch provides a function, to get of_device_id after
> matching with ACPI device _DSD object compatible property
> in the case driver does not contain acpi_device_id list
> and driver probe called for ACPI device ID PRP0001 with
> compatible property match with of_device_id compatible.
I don't see any usefulness of this function. Care to provide a real use case?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists