From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH V5] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register Date: Thu, 10 Oct 2013 10:15:40 -0700 Message-ID: <20131010171540.GG29913@atomide.com> References: <1381391028-4189-1-git-send-email-r.sricharan@ti.com> <5256A7AE.6000605@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:30400 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755363Ab3JJRPp (ORCPT ); Thu, 10 Oct 2013 13:15:45 -0400 Content-Disposition: inline In-Reply-To: <5256A7AE.6000605@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Santosh Shilimkar Cc: Sricharan R , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, nm@ti.com, Rajendra Nayak , Marc Zyngier , Mark Rutland * Santosh Shilimkar [131010 06:20]: > On Thursday 10 October 2013 03:43 AM, Sricharan R wrote: > > From: R Sricharan > > > > The realtime counter called master counter, produces the count > > used by the private timer peripherals in the MPU_CLUSTER. The > > CNTFRQ per cpu register is used to denote the frequency of the counter. > > Currently the frequency value is passed from the > > DT file, but this is not scalable when we have other non-DT guest > > OS. This register must be set to the right value by the > > secure rom code. Setting this register helps in propagating the right > > frequency value across OSes. > > > > More discussions and the reason for adding this in a non-DT > > way can be seen from below. > > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg93832.html > > > > So configuring this secure register for all the cpus here. > > > > Cc: Santosh Shilimkar > > Cc: Nishanth Menon > > Cc: Rajendra Nayak > > Cc: Marc Zyngier > > Cc: Mark Rutland > > Cc: Tony Lindgren > > Tested-by: Nishanth Menon > > Acked-by: Santosh Shilimkar > > Signed-off-by: Sricharan R > > --- > > [V5] Removed the use of extern variable in omap-smp.c > > as per suggestion from Santosh Shilimkar > > > Thanks for the updates Sricharan. Looks fine now. > > Tony, Can you apply this version if you are fine with it. Yes thanks looks good to me now. Applying into omap-for-v3.13/soc. Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 10 Oct 2013 10:15:40 -0700 Subject: [PATCH V5] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register In-Reply-To: <5256A7AE.6000605@ti.com> References: <1381391028-4189-1-git-send-email-r.sricharan@ti.com> <5256A7AE.6000605@ti.com> Message-ID: <20131010171540.GG29913@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Santosh Shilimkar [131010 06:20]: > On Thursday 10 October 2013 03:43 AM, Sricharan R wrote: > > From: R Sricharan > > > > The realtime counter called master counter, produces the count > > used by the private timer peripherals in the MPU_CLUSTER. The > > CNTFRQ per cpu register is used to denote the frequency of the counter. > > Currently the frequency value is passed from the > > DT file, but this is not scalable when we have other non-DT guest > > OS. This register must be set to the right value by the > > secure rom code. Setting this register helps in propagating the right > > frequency value across OSes. > > > > More discussions and the reason for adding this in a non-DT > > way can be seen from below. > > http://www.mail-archive.com/linux-omap at vger.kernel.org/msg93832.html > > > > So configuring this secure register for all the cpus here. > > > > Cc: Santosh Shilimkar > > Cc: Nishanth Menon > > Cc: Rajendra Nayak > > Cc: Marc Zyngier > > Cc: Mark Rutland > > Cc: Tony Lindgren > > Tested-by: Nishanth Menon > > Acked-by: Santosh Shilimkar > > Signed-off-by: Sricharan R > > --- > > [V5] Removed the use of extern variable in omap-smp.c > > as per suggestion from Santosh Shilimkar > > > Thanks for the updates Sricharan. Looks fine now. > > Tony, Can you apply this version if you are fine with it. Yes thanks looks good to me now. Applying into omap-for-v3.13/soc. Tony