RFC: Leave sysfs nodes alone during hotplug

[skannan at codeaurora.org]

Viresh Kumar wrote:
> On 8 July 2014 04:10, Todd Poynor <toddpoynor at google.com> 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.
>

Looks like there's enough interest. I'll also try to send out a patch of
what I think a simplified CPUfreq should look like.

-Saravana

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation