On 26 May 2014 18:05, Lucas Stach <l.stach@xxxxxxxxxxxxxx> wrote: > Ok I can push down the clock handling into the imx5 clk driver. Great !! > This leaves two more differences between imx5-cpufreq and cpufreq-cpu0: > > 1. Disabling of OPPs that could not be supported by the connected > regulator. I think this part can easily be made generic and pushed into > cpu0, as it should be beneficial to other SoCs too. Sure. > 2. Usage of a fixed max voltage, rather than a voltage-tolerance. i.MX5 > has a fixed maximum voltage, which is valid across all operating points. > I'm really opposed to using a tolerance value, where we instead could > have a well defined range. So for merging imx5-cpufreq into cpufreq-cpu0 > this driver really need to handle this case. > Does adding a separate property for this, while keeping the > voltage-tolerance for the existing users, sound like a change you would > accept? It looks you can just send voltage-tolerance to "zero" and this should work for you.. No need of another field. Thanks a lot for making our (/me & Rafael) life easier :) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
