On 8 July 2014 04:10, Todd Poynor <[email protected]> wrote: > For Android's usage we're also interested in both: > > 1. not removing and recreating the cpufreq sysfs files for a CPU on > hotplug events (we currently use hotplug uevents to reset file > ownership such that power policy can be controlled by non-root). > > 2. not resetting the contents of policy files such as scaling_max_freq > (also fixed up from uevents) or stats files (we currently keep a > separate persistent time_in_state for battery accounting purposes).
So, we actually need to retain all the files. I will try to see this separately. Will add it in my todo list. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
