On 20/10/16 13:07, Sekhar Nori wrote: > Per me, compatible property is an ordered list precisely for the reason > that things should continue to "work" with as closely matched driver as > possible. So even if someone is running a kernel which does not > recognize "ti,da850-tilcdc", it should still be able to probe the driver > based on "ti,am33xx-tilcdc" and provide as close to full functionality > as possible. > > That said, I will not insist on keeping it around if Tomi is > uncomfortable. And having read the binding documentation accepted by > Jyri, it actually says the compatible property should be __one of__ > "ti,am33xx-tilcdc" or "ti,da850-tilcdc". Well, they are just not compatible as far as I know. If the LCDC on DA850 would be identified as AM335x LCDC, and used as such, it would not work at all. They have different registers, AM335x LCDC has registers that do not exist on DA850. With our driver it happens to work, because the driver looks at the IP revision in the registers, and then decides that this IP is not AM335x LCDC even if the dts says so. But I see that as a driver "feature", nothing that the .dts can depend on. Perhaps it might work the other way around, using DA850 driver on AM335x, as DA850 LCDC is a kind of subset of AM335x LCDC. But I'm not sure even about that. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
