On Mon, Nov 18, 2013 at 10:41:36AM -0600, Nishanth Menon wrote: > In the case of mismatch, to consider that device tree may be wrong in > driver is also to assume that hardware was always configured correctly > and we assume description is the flawed data. No, I did not say that. IMO, when cpufreq-cpu0 sees a mismatch, it has no way to know or assume which one is correct and which is incorrect. The best thing it can do is to fail out without changing anything about running frequency and voltage. Shawn > That is just plain > wrong. we need to assume device tree is the correct description of the > hardware and any mismatch must be assumed as bad configuration - and > this is what the patch does. > > Now, if the description is wrong, that is a dts bug of it's own. > > If the suggestion is to improve my commit message, I am more than > happy to do so - please suggest how I could improve the same. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
