* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [190906 17:09]: > for i in 3430 34xx 3630 36xx; do echo $i $(fgrep '"'ti,omap$i'"' arch/arm/boot/dts/*.dts* | wc -l); done > > 3430 12 > 34xx 28 > 3630 3 > 36xx 23 > > which would indicate that 34xx and 36xx are more common. Right, but the xx variants are against the device tree naming and that's why we should get rid of them in the dts. The compatible should be named after the first instance like "ti,omap3430" and similar devices can just use that. > BTW there is also some code that does special SoC detection based on > soc_device_match(), mainly in omapdrm/dss. > > If we were to use this mechanism in the ti-cpufreq driver we could > match it to ti,omap3 and could avoid all these changes. > > But make it less maintainable and code more complex. Hmm right, yeah using soc_device_match() would remove this issue. It might be worth doing as these SoC variants do not change much and the code should not need updating. Up to you to decide. > I'll also take a look at omap.txt bindings since that likely needs > an update as well to better describe what the official ones are > and which are legacy. OK. Just limit the compatible changes to the ones that need to be modified for this series, the rest can be done with a separate patches. Regards, Tony
