[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcGopXaksmvXP_vMM-iGK0o_g5Fw_F5zvH+PXcCUx_cDQ@mail.gmail.com>
Date: Fri, 26 Aug 2022 18:18:20 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jean Delvare <jdelvare@...e.de>
Cc: linux-iio <linux-iio@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH] iio:accel:dmard06: Optimize when CONFIG_OF isn't set
On Fri, Aug 26, 2022 at 1:46 PM Jean Delvare <jdelvare@...e.de> wrote:
> On Thu, 25 Aug 2022 23:12:43 +0300, Andy Shevchenko wrote:
> > On Thu, Aug 25, 2022 at 3:54 PM Jean Delvare <jdelvare@...e.de> wrote:
...
> Now I'm curious, is there a well-defined subset of device names that
> can be found in an ACPI table? If not, does that mean that any driver
> with an OF entry could match,
Yes, anything can be matched by ACPI with any of the compatible strings.
> therefore of_match_ptr() should be
> removed from the kernel entirely?
In most cases yes, like for discrete components that can be connected
to any SoC on ACPI/DT/whatever platform. But for some cases it still
makes sense: platform is known to never be non-OF, component is known
to be used only on such platforms, etc.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists