From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758923Ab2FADpr (ORCPT ); Thu, 31 May 2012 23:45:47 -0400 Received: from na3sys009aog137.obsmtp.com ([74.125.149.18]:34598 "EHLO na3sys009aog137.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758521Ab2FADpq convert rfc822-to-8bit (ORCPT ); Thu, 31 May 2012 23:45:46 -0400 MIME-Version: 1.0 In-Reply-To: <874nqwynxd.fsf@ti.com> References: <1335462041-4949-1-git-send-email-j-keerthy@ti.com> <87397by2h9.fsf@ti.com> <87obpdv6f4.fsf@ti.com> <874nqwynxd.fsf@ti.com> Date: Fri, 1 Jun 2012 09:15:45 +0530 Message-ID: Subject: Re: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) From: "J, KEERTHY" To: Kevin Hilman 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 1, 2012 at 4:10 AM, Kevin Hilman wrote: > Kevin Hilman writes: > >> "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/* > > OK, I had an off-line discussion with Rafael and he's OK that I take > these.  I will add an ack from Rafael and queue this series up for v3.6. Thanks Kevin. > > Thanks, > > Kevin -- Regards and Thanks, Keerthy From mboxrd@z Thu Jan 1 00:00:00 1970 From: j-keerthy@ti.com (J, KEERTHY) Date: Fri, 1 Jun 2012 09:15:45 +0530 Subject: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) In-Reply-To: <874nqwynxd.fsf@ti.com> References: <1335462041-4949-1-git-send-email-j-keerthy@ti.com> <87397by2h9.fsf@ti.com> <87obpdv6f4.fsf@ti.com> <874nqwynxd.fsf@ti.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Jun 1, 2012 at 4:10 AM, Kevin Hilman wrote: > Kevin Hilman writes: > >> "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/* > > OK, I had an off-line discussion with Rafael and he's OK that I take > these. ?I will add an ack from Rafael and queue this series up for v3.6. Thanks Kevin. > > Thanks, > > Kevin -- Regards and Thanks, Keerthy