On Thu, Oct 20, 2022 at 08:03:37PM +0300, Andy Shevchenko wrote: > On Thu, Oct 20, 2022 at 05:58:39PM +0100, Mark Brown wrote: > > The driver won't even match and therefore load if it doesn't have a > > lookup for the device with the current code, the type code comes from > > the match. If it has to go querying a device property then the driver > > can load but end up with a device property it hasn't ever heard of and > > end up misbehaving as a result. > That's how all MFD devices work nowadays, right? What's so special about > this driver? It's being used as a child by MFD. If what you are telling > is a real concern, we have to have a way to assure that all drivers that > are children of the MFDs should provide a match. IIRC there is no such > mechanism exists in the kernel these days. Most of the MFDs don't actually have multiple options for a given child driver, and it's common where there are multiple options to either bind with a different name representing the different child device or have something that looks like a switch statement for the IDs which will error out if it hits an ID that's not one the driver knows about (like spi-pxa2xx-pci does with lpss_spi_setup()).
Attachment:
signature.asc
Description: PGP signature
