linux-kernel - Re: [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq change

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 May 2011 12:20:46 +0530
From:	Santosh Shilimkar <santosh.shilimkar@...com>
To:	Colin Cross <ccross@...roid.com>
CC:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Russell King <linux@....linux.org.uk>,
	Rob Herring <robherring2@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq
 change

On 5/23/2011 10:48 AM, Colin Cross wrote:
> On Fri, May 20, 2011 at 11:29 PM, Santosh Shilimkar
> <santosh.shilimkar@...com>  wrote:
>> On 5/20/2011 5:54 AM, Colin Cross wrote:
>>>
>>> The localtimer's clock changes with the cpu clock.  After a
>>> cpufreq transition, update the clockevent's frequency and
>>> reprogram the next clock event.
>>>
>>> Adds a clock called "smp_twd" that is used to determine the
>>> twd frequency, which can also be used at init time to
>>> avoid calibrating the twd frequency.
>>>
>>> Clock changes are based on Rob Herring's work.
>>>
>>> Change-Id: I413b5cd07fb2b79bc9fad8b4bf257332d1da7bcd
>>> Signed-off-by: Colin Cross<ccross@...roid.com>
>>> Cc: Thomas Gleixner<tglx@...utronix.de>
>>> Cc: Russell King<linux@....linux.org.uk>
>>> Cc: Santosh Shilimkar<santosh.shilimkar@...com>
>>> Cc: Rob Herring<robherring2@...il.com>
>>> Tested-by: Linus Walleij<linus.walleij@...aro.org>
>>> ---
>>
>> Acked-by: Santosh Shilimkar<santosh.shilimkar@...com>
>>
>> What about the clock-node patches?
>> Do you want those to get merged via sub-arch tree's once this
>> patch + Thomas's new API gets merged ?
>
> The clock-node patches can be merged independently - twd scaling just
> won't work until they are both merged.
Yep. That should be ok.

Regards
Santosh
--
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/