On 28 November 2014 at 17:21, Sudeep Holla <[email protected]> wrote: >> - Update those platforms to check if DT has "compatible" string in CPU >> node. >> If yes, don't create a device as this will be created by cpufreq-dt. >> > > This fixes how it will work with new DTs, how about old DTs ? > IMO we still need the blacklist kind of logic I sent before.
Yes.. > I don't think this is something acceptable, why will someone want to > lose a working feature with new kernel. If some platform maintainers care for cleaner/simpler code instead of backward compatibility .. For example, exynos has just started to use cpufreq-dt. Probably in 3.18 or may be 19 as well.. So, they might not care about backward compatibility at all.. Let me see if I can come up with a solution that looks reasonably clean. -- viresh -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
