On 20/08/2025 11:37, Mike Looijmans wrote: > > Met vriendelijke groet / kind regards, > > Mike Looijmans > System Expert > > > TOPIC Embedded Products B.V. > Materiaalweg 4, 5681 RJ Best > The Netherlands > > T: +31 (0) 499 33 69 69 > E: mike.looijm...@topic.nl > W: www.topic.nl
Please fix your email client not to attach such top signature. ... >> >> Also, e.g. first file in iio/adc: >> adi,ad4000.yaml >> > I think I get it. Instead of having compatibles "a" and "b" the driver only > supports "a" in its match table, and the devicetree entry must be either > compatible="a"; or compatible="b","a". Using compatible="b"; would be > disallowed. > > 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 I don't understand why. I don't get what is input and output bus. Either devices are compatible or not. If you can check which device you have via registers, then usually they are compatible. Best regards, Krzysztof
