On 08/02/14 06:47, Thomas Abraham wrote: > On Fri, Feb 7, 2014 at 11:32 PM, Sudeep Holla <Sudeep.Holla@xxxxxxx> wrote: >> On 07/02/14 17:37, Nishanth Menon wrote: >>> On Fri, Feb 7, 2014 at 11:31 AM, Sudeep Holla <Sudeep.Holla@xxxxxxx> wrote: >> >> [...] >> >>>> Yes I think its counter-intuitive as it's visible to the userspace(list of >>>> frequencies and the boost parameters are exposed through sysfs) >>> >>> That will be a different problem -> as currently every single >>> frequency in the cpufreq list has ability to be marked as boost >>> frequency - if userspace does not maintain that, then, IMHO, fix the >>> userspace :D >>> >> >> /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies gives >> the list of frequencies based on the state of the boost feature at anytime. > > The list of frequencies in > /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies > does not change based in the state of the boost feature (enabled or > disabled). But the scaling_max_frequency and scaling_min_frequency are > updated based on the set of available + boost frequencies available. > Ah ok, sorry just glanced the code and misunderstood it. It make sense to update only max_frequency. Regards, Sudeep -- 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
