From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758654Ab2EXRYW (ORCPT ); Thu, 24 May 2012 13:24:22 -0400 Received: from na3sys009aog121.obsmtp.com ([74.125.149.145]:36698 "EHLO na3sys009aog121.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756965Ab2EXRYU convert rfc822-to-8bit (ORCPT ); Thu, 24 May 2012 13:24:20 -0400 From: Kevin Hilman To: "J\, KEERTHY" Cc: "Rafael J. Wysocki" , greg@kroah.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org, j-pihet@ti.com Subject: Re: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) Organization: Texas Instruments, Inc. References: <1335462041-4949-1-git-send-email-j-keerthy@ti.com> <87397by2h9.fsf@ti.com> Date: Thu, 24 May 2012 10:24:15 -0700 In-Reply-To: (KEERTHY J.'s message of "Wed, 23 May 2012 10:21:19 +0530") Message-ID: <87obpdv6f4.fsf@ti.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "J, KEERTHY" writes: > On Tue, May 15, 2012 at 11:16 AM, J, KEERTHY wrote: >> On Tue, May 8, 2012 at 5:21 AM, Kevin Hilman wrote: >>> Rafael, >>> >>> Keerthy writes: >>> >>>> From: J Keerthy >>>> >>>> AVS(Adaptive Voltage Scaling) is a power management technique which >>>> controls the operating voltage of a device in order to optimize (i.e. reduce) >>>> its power consumption. The voltage is adapted depending on static factors >>>> (chip manufacturing process) and dynamic factors (temperature >>>> depending performance). >>>> The TI AVS solution is named Smartreflex. >>>> >>>> To that end, create the AVS driver in drivers/power/avs and >>>> move the OMAP SmartReflex code to the new directory. The >>>> class driver is still retained in the mach-omap2 directory. >>> >>> How should we handle this for upstream? >>> >>> It does a bunch of cleanup under arch/arm then does the move to >>> drivers/power the end.  To avoid conflicts with other OMAP core changes, >>> I would suggest we take this through the OMAP tree. >>> >>> With your ack, I'd be glad to take it. >> >> Hello Rafael, >> >> A gentle ping on this series. > > Hi Greg, > > This series has Kevin's comments incorporated. > > Kevin, > > Can i have your Ack for this series? > Well, as mentioned above, I'm waiting for Rafael's ack, then I will merge it. Because of all the arch/arm/mach-omap2/* changes, I would like to merge this via the OMAP tree to avoid conflicts with other stuff we have changing in arch/arm/mach-omap2/* Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) Date: Thu, 24 May 2012 10:24:15 -0700 Message-ID: <87obpdv6f4.fsf@ti.com> References: <1335462041-4949-1-git-send-email-j-keerthy@ti.com> <87397by2h9.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: (KEERTHY J.'s message of "Wed, 23 May 2012 10:21:19 +0530") Sender: linux-omap-owner@vger.kernel.org To: "J, KEERTHY" Cc: "Rafael J. Wysocki" , greg@kroah.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org, j-pihet@ti.com List-Id: linux-pm@vger.kernel.org "J, KEERTHY" writes: > On Tue, May 15, 2012 at 11:16 AM, J, KEERTHY wrote= : >> On Tue, May 8, 2012 at 5:21 AM, Kevin Hilman wrote: >>> Rafael, >>> >>> Keerthy writes: >>> >>>> From: J Keerthy >>>> >>>> AVS(Adaptive Voltage Scaling) is a power management technique whic= h >>>> controls the operating voltage of a device in order to optimize (i= =2Ee. reduce) >>>> its power consumption. The voltage is adapted depending on static = factors >>>> (chip manufacturing process) and dynamic factors (temperature >>>> depending performance). >>>> The TI AVS solution is named Smartreflex. >>>> >>>> To that end, create the AVS driver in drivers/power/avs and >>>> move the OMAP SmartReflex code to the new directory. The >>>> class driver is still retained in the mach-omap2 directory. >>> >>> How should we handle this for upstream? >>> >>> It does a bunch of cleanup under arch/arm then does the move to >>> drivers/power the end. =C2=A0To avoid conflicts with other OMAP cor= e changes, >>> I would suggest we take this through the OMAP tree. >>> >>> With your ack, I'd be glad to take it. >> >> Hello Rafael, >> >> A gentle ping on this series. > > Hi Greg, > > This series has Kevin's comments incorporated. > > Kevin, > > Can i have your Ack for this series? > Well, as mentioned above, I'm waiting for Rafael's ack, then I will merge it. Because of all the arch/arm/mach-omap2/* changes, I would like to merge this via the OMAP tree to avoid conflicts with other stuff we have changing in arch/arm/mach-omap2/* Kevin -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@ti.com (Kevin Hilman) Date: Thu, 24 May 2012 10:24:15 -0700 Subject: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) In-Reply-To: (KEERTHY J.'s message of "Wed, 23 May 2012 10:21:19 +0530") References: <1335462041-4949-1-git-send-email-j-keerthy@ti.com> <87397by2h9.fsf@ti.com> Message-ID: <87obpdv6f4.fsf@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org "J, KEERTHY" writes: > On Tue, May 15, 2012 at 11:16 AM, J, KEERTHY wrote: >> On Tue, May 8, 2012 at 5:21 AM, Kevin Hilman wrote: >>> Rafael, >>> >>> Keerthy writes: >>> >>>> From: J Keerthy >>>> >>>> AVS(Adaptive Voltage Scaling) is a power management technique which >>>> controls the operating voltage of a device in order to optimize (i.e. reduce) >>>> its power consumption. The voltage is adapted depending on static factors >>>> (chip manufacturing process) and dynamic factors (temperature >>>> depending performance). >>>> The TI AVS solution is named Smartreflex. >>>> >>>> To that end, create the AVS driver in drivers/power/avs and >>>> move the OMAP SmartReflex code to the new directory. The >>>> class driver is still retained in the mach-omap2 directory. >>> >>> How should we handle this for upstream? >>> >>> It does a bunch of cleanup under arch/arm then does the move to >>> drivers/power the end. ?To avoid conflicts with other OMAP core changes, >>> I would suggest we take this through the OMAP tree. >>> >>> With your ack, I'd be glad to take it. >> >> Hello Rafael, >> >> A gentle ping on this series. > > Hi Greg, > > This series has Kevin's comments incorporated. > > Kevin, > > Can i have your Ack for this series? > Well, as mentioned above, I'm waiting for Rafael's ack, then I will merge it. Because of all the arch/arm/mach-omap2/* changes, I would like to merge this via the OMAP tree to avoid conflicts with other stuff we have changing in arch/arm/mach-omap2/* Kevin