[PATCH v1 1/4] fbtft: Unorphan the driver

Andy Shevchenko andriy.shevchenko at linux.intel.com
Mon Jan 31 14:06:10 UTC 2022


On Mon, Jan 31, 2022 at 02:55:21PM +0100, Javier Martinez Canillas wrote:
> On 1/31/22 14:23, Andy Shevchenko wrote:
> > On Mon, Jan 31, 2022 at 01:08:32PM +0100, Javier Martinez Canillas wrote:

...

> > The tricky part is the PRP0001
> > ACPI PNP ID that allows to reuse it on ACPI-based platforms.
> 
> Oh, I wasn't aware about PRP0001. I've read about it at:
> 
> https://www.kernel.org/doc/Documentation/acpi/enumeration.txt

Yep!

The idea is that new drivers for discrete (and sometimes even on-SoC)
components should be platform-agnostic (means no strict OF / ACPI
dependencies), so anybody can prototype devices on either of the
platforms.

As a matter of fact IIO subsystem is leading in this by cleaning up
most of the drivers towards that goal.

OF/ACPI explicit dependency makes sense when we 100+% sure that
IP in question won't ever appear on the other type of platform
(which I believe is very rare nowadays for most of the components).

-- 
With Best Regards,
Andy Shevchenko




More information about the dri-devel mailing list