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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 17 Jul 2014 05:58:22 +0530
From:	Viresh Kumar <>
To:	"Rafael J. Wysocki" <>
Cc:	Mike Turquette <>,
	Thomas Petazzoni <>,
	Stephen Boyd <>,
	Lists linaro-kernel <>,
	"" <>,
	Arvind Chauhan <>,
	"" <>,
	Sachin Kamat <>,
	Thomas P Abraham <>,
	Shawn Guo <>,
	Linux Kernel Mailing List <>,
	Nishanth Menon <>, Tomasz Figa <>,
	"" <>,
	Kukjin Kim <>,
	Michal Simek <>,
	Rob Herring <>,
	Santosh Shilimkar <>,
	Simon Horman <>
Subject: Re: [PATCH 00/14] cpufreq: cpu0: Extend support beyond CPU0, V2

On 17 July 2014 02:48, Rafael J. Wysocki <> wrote:
> I don't like that idea, but I wonder what other people think.

Hmm, the other thread around looking at the bindings is really slow.

One common thing around the platforms which want to use
cpufreq-cpu0 is they have different clocks for ALL CPUs.

I was wondering if instead of a clock-matching routine, we can provide
some temporary relief to them via some other means.

I meant we can allow cpufreq-cpu0/generic to either set policy->cpus
to ALL CPUs or just 1. So that existing and these new platforms can
atleast get going..

But don't know how should we do that. Not a binding ofcourse, a
Kconfig option could work but multiplatform stuff would break. What

Maybe platform data as we are handling cpufreq-cpu0 with a platform

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists