From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753254Ab1CFOUv (ORCPT ); Sun, 6 Mar 2011 09:20:51 -0500 Received: from na3sys009aog115.obsmtp.com ([74.125.149.238]:44905 "EHLO na3sys009aog115.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752543Ab1CFOUs (ORCPT ); Sun, 6 Mar 2011 09:20:48 -0500 From: Santosh Shilimkar References: <1290060899-9786-1-git-send-email-ccross@android.com><4D70BE9D.4000507@stericsson.com><4D714C17.7080102@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: Acvb9wghxONAoWNCRh21qYcPE9opAwAET2yg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Date: Sun, 6 Mar 2011 19:50:38 +0530 Message-ID: <7e9fafa016bfe536ccc373fc2cc7ba61@mail.gmail.com> Subject: RE: [PATCH] ARM: twd: Adjust localtimer frequency withcpufreqnotifiers To: Linus Walleij Cc: Russell King , Srinidhi KASAGAR , Harald Gustafsson , Linus Walleij , linux-kernel@vger.kernel.org, Rickard ANDERSSON , martin persson , Colin Cross , Varun Swara , Catalin Marinas , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > -----Original Message----- > From: linux-arm-kernel-bounces@lists.infradead.org [mailto:linux- > arm-kernel-bounces@lists.infradead.org] On Behalf Of Linus Walleij > Sent: Sunday, March 06, 2011 5:37 PM > To: Santosh Shilimkar > Cc: Russell King; Srinidhi KASAGAR; Harald Gustafsson; Linus > Walleij; linux-kernel@vger.kernel.org; Rickard ANDERSSON; martin > persson; Colin Cross; Varun Swara; Catalin Marinas; linux-arm- > kernel@lists.infradead.org > Subject: Re: [PATCH] ARM: twd: Adjust localtimer frequency > withcpufreqnotifiers > > On Sat, Mar 5, 2011 at 9:19 AM, Santosh Shilimkar > wrote: > > > While doing this patch for OMAP I also found that > > CPUFREQ notifiers does delays scaling timer frequency > > and there is a tick deviation(3-4 ms) around 1st tick and > > last tick around twd rescaling. > > Is this caused by ticks that have been programmed > already (based on the previous frequency) when the scaling > takes effect? (That's most likely I think.) > That's correct Linus. I noticed that Collin's patch reduces that problem a bit. In my patch I was always leaving the scaling to post notifier which actually aggravates the scenario. > The latter could be fixed by simply calling > schedule() for each CPU connected in the same core as > the TWD at the end of twd_update_cpu_frequency(), > couldn't it? > I don't think schedule will do any difference here because it's the actual tick duration which getting changed. The tick does happen as per the timer load value. Now it all depends at what point time in tick window the timer scaling happens. > Colin what do you say? > > > Another issue was not able to select higher fixed twd rate > > and found fix for the same. > > Can you send out the patch? > Sure. May be let's get all these twd scaling patches on the list. Rob's clock patches, Collin's notifier patch. And then I shall post the fix on top of that. Regards, Santosh