lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Sep 2013 21:52:31 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Russell King - ARM Linux <linux@....linux.org.uk> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Lists linaro-kernel <linaro-kernel@...ts.linaro.org>, Patch Tracking <patches@...aro.org>, "cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>, "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 206/228] cpufreq: sa11x0: remove calls to cpufreq_notify_transition() On 13 September 2013 21:45, Russell King - ARM Linux <linux@....linux.org.uk> wrote: > The patch to which I'm replying removes the above calls. These calls are > necessary to shutdown various bits of CPU-clock dependent hardware > before changing the CPU clock, and restore them - reconfiguring them > for the new clock rate after the transition has happened. > > So, if you're removing these calls, what replaces them? I don't see > anything which does without the above set. The other patch on which you commented about unnecessary read locks being taken: [PATCH 181/228] cpufreq: move freq change notifications to cpufreq That calls these notifiers, for all platforms except the ones that have set CPUFREQ_ASYNC_NOTIFICATION, before and after calling ->target_index().. And so functionally the code is supposed to be the same.. Unless I have done some stupid mistake.. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists