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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 2 Jul 2014 09:02:13 +0530
From:	Viresh Kumar <>
To:	Mike Turquette <>
Cc:	Rob Herring <>,
	Grant Likely <>,
	Stephen Boyd <>,
	"Rafael J. Wysocki" <>,
	Shawn Guo <>,
	Lists linaro-kernel <>,
	"" <>,
	Linux Kernel Mailing List <>,
	Arvind Chauhan <>,
	<>,, Sachin Kamat <>,
	Thomas P Abraham <>,
	Nishanth Menon <>, Tomasz Figa <>,
	Mark Brown <>,
	Mark Rutland <>
Subject: Re: [PATCH 2/2] cpufreq: cpu0: Extend support beyond CPU0

On 2 July 2014 03:30, Mike Turquette <> wrote:
> I can't help but think this is a pretty ugly solution. Why not specify

Thanks :)

> the nature of the cpu clock(s) in DT directly? There was a thread
> already that discussed adding such a property to the CPU DT binding but
> it seems to have gone cold[1]. Furthermore my mailer sucks and I see now
> that my response to that thread never hit the list due to mangled
> headers. Here is a copy/paste of my response to the aforementioned
> thread:

Atleast I received it.

Yes, I do agree that we need to get this from the DT in more elegant
way but it is going to take some time in doing that, and probably some
people are working on it as that might be used in scheduler-cpufreq
coordination as well..

For now we can go ahead and make it workable, even if it isn't that
elegant and update it later on.

Thanks for your inputs.
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