From mboxrd@z Thu Jan 1 00:00:00 1970 From: skannan@codeaurora.org Subject: Re: RFC: Leave sysfs nodes alone during hotplug Date: Tue, 8 Jul 2014 03:30:04 -0000 Message-ID: <533b04020d15a2f9ac0c582652f6e70f.squirrel@www.codeaurora.org> References: <53B5D22F.2070308@codeaurora.org> <53BAF540.9080904@codeaurora.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7BIT Return-path: In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Viresh Kumar Cc: Todd Poynor , Saravana Kannan , "Srivatsa S. Bhat" , "cpufreq@vger.kernel.org" , Linux PM mailing list , "linux-arm-msm@vger.kernel.org" , linux-arm-kernel , "Rafael J. Wysocki" , Ruchi Kandoi Viresh Kumar wrote: > On 8 July 2014 04:10, Todd Poynor 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