From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 6/6] OMAP4460: Clock: Adding support for 4460 specific clocks Date: Thu, 6 Oct 2011 11:24:49 -0700 Message-ID: <20111006182448.GJ6324@atomide.com> References: <1316705361-12175-1-git-send-email-j-keerthy@ti.com> <1316705361-12175-7-git-send-email-j-keerthy@ti.com> <20111004004331.GR6324@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:25812 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754560Ab1JFSYw (ORCPT ); Thu, 6 Oct 2011 14:24:52 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Shilimkar, Santosh" Cc: Paul Walmsley , Keerthy , linux-omap@vger.kernel.org, rnayak@ti.com, b-cousson@ti.com, Vishwanath BS * Shilimkar, Santosh [111003 22:50]: > On Tue, Oct 4, 2011 at 9:21 AM, Paul Walmsley wrote: > > + Rajendra, Santosh, Beno=C3=AEt > > > > Hi > > > > On Mon, 3 Oct 2011, Tony Lindgren wrote: > > > >> * Paul Walmsley [110929 17:40]: > >> > On Thu, 22 Sep 2011, Keerthy wrote: > >> > > >> > > From: Vishwanath BS > >> > > > >> > > OMAP4460 specific clocks are not getting added as the > >> > > cpu_is_omap44xx is choosing only OMAP4430 specific clock nodes= =2E > >> > > Changing it to add to OMAP4460 specific clocks also. > >> > > This is clocks are required of temperature sensor. > >> > > > >> > > Signed-off-by: Vishwanath BS > >> > > Signed-off-by: Keerthy > >> > > Cc: paul@pwsan.com > >> > > >> > Thanks, this patch has been queued for 3.2. > >> > >> Should this be a fix for the -rc cycle instead? > > > > I don't think it's needed for the -rc series, since we don't have a= ny > > in-tree users of the 4460 temperature sensor. =C2=A0The only impact= I can see > > is if the bootloader enables the 4460 temperature sensor clock, and > > doesn't disable it. =C2=A0I assume that would probably prevent the = L4 WKUP > > clockdomain from entering clock stop, which would consume a little = more > > power. > > > You are correct Paul. It would have also gated the low power states > but at this point of time on mainline, we aren't supporting CORE/PER > low power states for OMAP44XX. >=20 > IIRC, boot-loader isn't enabling the temperature > sensor clock so this patch can wait for next merge window. OK thanks, sounds like v3.2 merge window is safe for this then. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html