On Wed, Aug 20, 2025 at 11:37:24AM +0200, Mike Looijmans wrote: > I actually planned (I have implemented it locally already for v3) for the > driver to check the chip type and complain if it doesn't match the > devicetree. If the wrong device is there, the most likely cause is that the > input and output buses got mixed up. That would also justify having separate > compatibles, right?
It's not the kernel's job to verify the devicetree, it should be assumed to be correct. You're ensuring that when another compatible device arrives later on that a new string in a binding will not be sufficient for the device to be supported and driver changes will be required to make it work.
signature.asc
Description: PGP signature
