From: "J, KEERTHY" <j-keerthy@ti.com> To: Kevin Hilman <khilman@ti.com> Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, 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) Date: Fri, 1 Jun 2012 09:15:45 +0530 [thread overview] Message-ID: <CAJ6a13YzgxK1QJVLd+ZKRM=w4mM3P3YXicwdazpBaRDqdUDHqA@mail.gmail.com> (raw) In-Reply-To: <874nqwynxd.fsf@ti.com> On Fri, Jun 1, 2012 at 4:10 AM, Kevin Hilman <khilman@ti.com> wrote: > Kevin Hilman <khilman@ti.com> writes: > >> "J, KEERTHY" <j-keerthy@ti.com> writes: >> >>> On Tue, May 15, 2012 at 11:16 AM, J, KEERTHY <j-keerthy@ti.com> wrote: >>>> On Tue, May 8, 2012 at 5:21 AM, Kevin Hilman <khilman@ti.com> wrote: >>>>> Rafael, >>>>> >>>>> Keerthy <j-keerthy@ti.com> writes: >>>>> >>>>>> From: J Keerthy <j-keerthy@ti.com> >>>>>> >>>>>> 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
WARNING: multiple messages have this Message-ID (diff)
From: j-keerthy@ti.com (J, KEERTHY) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) Date: Fri, 1 Jun 2012 09:15:45 +0530 [thread overview] Message-ID: <CAJ6a13YzgxK1QJVLd+ZKRM=w4mM3P3YXicwdazpBaRDqdUDHqA@mail.gmail.com> (raw) In-Reply-To: <874nqwynxd.fsf@ti.com> On Fri, Jun 1, 2012 at 4:10 AM, Kevin Hilman <khilman@ti.com> wrote: > Kevin Hilman <khilman@ti.com> writes: > >> "J, KEERTHY" <j-keerthy@ti.com> writes: >> >>> On Tue, May 15, 2012 at 11:16 AM, J, KEERTHY <j-keerthy@ti.com> wrote: >>>> On Tue, May 8, 2012 at 5:21 AM, Kevin Hilman <khilman@ti.com> wrote: >>>>> Rafael, >>>>> >>>>> Keerthy <j-keerthy@ti.com> writes: >>>>> >>>>>> From: J Keerthy <j-keerthy@ti.com> >>>>>> >>>>>> 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
next prev parent reply other threads:[~2012-06-01 3:45 UTC|newest] Thread overview: 144+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-26 17:40 [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 01/10] ARM: OMAP2+: SmartReflex: move the smartreflex header to include/linux/power Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 02/10] ARM: OMAP3+: SmartReflex: class drivers should use struct omap_sr * Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 03/10] ARM: OMAP2+: smartreflex: Use the names from hwmod data instead of voltage domains Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 04/10] ARM: OMAP3: hwmod: rename the smartreflex entries Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-05-04 8:30 ` AnilKumar, Chimata 2012-05-04 8:30 ` AnilKumar, Chimata 2012-05-04 8:30 ` AnilKumar, Chimata 2012-05-04 10:11 ` J, KEERTHY 2012-05-04 10:11 ` J, KEERTHY 2012-05-04 10:11 ` J, KEERTHY 2012-05-07 23:39 ` Kevin Hilman 2012-05-07 23:39 ` Kevin Hilman 2012-05-07 23:39 ` Kevin Hilman 2012-05-07 23:55 ` Kevin Hilman 2012-05-07 23:55 ` Kevin Hilman 2012-05-07 23:55 ` Kevin Hilman 2012-05-08 3:44 ` J, KEERTHY 2012-05-08 3:44 ` J, KEERTHY 2012-05-08 3:44 ` J, KEERTHY 2012-04-26 17:40 ` [PATCH V3 05/10] ARM: OMAP2+: SmartReflex: introduce a busy loop condition test macro Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-05-04 9:12 ` AnilKumar, Chimata 2012-05-04 9:12 ` AnilKumar, Chimata 2012-05-04 9:12 ` AnilKumar, Chimata 2012-05-07 5:21 ` J, KEERTHY 2012-05-07 5:21 ` J, KEERTHY 2012-05-07 5:21 ` J, KEERTHY 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-10 6:19 ` J, KEERTHY 2012-05-10 6:19 ` J, KEERTHY 2012-05-10 6:19 ` J, KEERTHY 2012-04-26 17:40 ` [PATCH V3 06/10] ARM: OMAP2+: Voltage: Move the omap_volt_data structure to plat Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 07/10] ARM: OMAP2+: SmartReflex: Use per-OPP data structure Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-05-10 19:11 ` Guyotte, Greg 2012-05-10 19:11 ` Guyotte, Greg 2012-05-10 19:11 ` Guyotte, Greg 2012-05-11 3:51 ` J, KEERTHY 2012-05-11 3:51 ` J, KEERTHY 2012-05-11 3:51 ` J, KEERTHY 2012-04-26 17:40 ` [PATCH V3 08/10] ARM: OMAP2+: SmartReflex: Create per-opp debugfs node for errminlimit Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 09/10] ARM: OMAP2+: SmartReflex: add POWER_AVS Kconfig options Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` [PATCH V3 10/10] ARM: OMAP: SmartReflex: Move smartreflex driver to drivers/ Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 17:40 ` Keerthy 2012-04-26 19:11 ` [PATCH V3 00/10] PM: Create the AVS(Adaptive Voltage Scaling) Mark Brown 2012-04-26 19:11 ` Mark Brown 2012-04-26 19:11 ` Mark Brown 2012-04-27 5:39 ` J, KEERTHY 2012-04-27 5:39 ` J, KEERTHY 2012-04-27 17:56 ` Mark Brown 2012-04-27 17:56 ` Mark Brown 2012-04-27 17:56 ` Mark Brown 2012-04-27 21:01 ` Kevin Hilman 2012-04-27 21:01 ` Kevin Hilman 2012-04-27 21:01 ` Kevin Hilman 2012-04-30 4:25 ` J, KEERTHY 2012-04-30 4:25 ` J, KEERTHY 2012-04-30 4:25 ` J, KEERTHY 2012-04-30 9:54 ` Mark Brown 2012-04-30 9:54 ` Mark Brown 2012-04-30 9:54 ` Mark Brown 2012-04-30 21:51 ` Kevin Hilman 2012-04-30 21:51 ` Kevin Hilman 2012-04-30 21:51 ` Kevin Hilman 2012-05-02 5:04 ` J, KEERTHY 2012-05-02 5:04 ` J, KEERTHY 2012-05-02 5:04 ` J, KEERTHY 2012-05-04 5:05 ` J, KEERTHY 2012-05-04 5:05 ` J, KEERTHY 2012-05-04 5:05 ` J, KEERTHY 2012-05-04 8:21 ` AnilKumar, Chimata 2012-05-04 8:21 ` AnilKumar, Chimata 2012-05-04 8:21 ` AnilKumar, Chimata 2012-05-07 23:48 ` Kevin Hilman 2012-05-07 23:48 ` Kevin Hilman 2012-05-07 23:48 ` Kevin Hilman 2012-05-08 3:48 ` J, KEERTHY 2012-05-08 3:48 ` J, KEERTHY 2012-05-08 3:48 ` J, KEERTHY 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-08 10:17 ` AnilKumar, Chimata 2012-05-08 20:38 ` Woodruff, Richard 2012-05-08 20:38 ` Woodruff, Richard 2012-05-08 20:38 ` Woodruff, Richard 2012-05-08 22:16 ` [linux-pm] " Kevin Hilman 2012-05-08 22:16 ` Kevin Hilman 2012-05-08 22:16 ` Kevin Hilman 2012-05-09 0:39 ` Woodruff, Richard 2012-05-09 0:39 ` Woodruff, Richard 2012-05-09 0:39 ` Woodruff, Richard 2012-05-09 8:19 ` [linux-pm] " Koen Kooi 2012-05-09 8:19 ` Koen Kooi 2012-05-09 8:19 ` Koen Kooi 2012-05-09 18:29 ` Kevin Hilman 2012-05-09 18:29 ` Kevin Hilman 2012-05-09 18:29 ` Kevin Hilman 2012-05-23 13:27 ` Menon, Nishanth 2012-05-23 13:27 ` Menon, Nishanth 2012-05-23 13:27 ` Menon, Nishanth 2012-05-24 23:16 ` [linux-pm] " Kevin Hilman 2012-05-24 23:16 ` Kevin Hilman 2012-05-24 23:16 ` Kevin Hilman 2012-05-07 23:51 ` Kevin Hilman 2012-05-07 23:51 ` Kevin Hilman 2012-05-07 23:51 ` Kevin Hilman 2012-05-15 5:46 ` J, KEERTHY 2012-05-15 5:46 ` J, KEERTHY 2012-05-15 5:46 ` J, KEERTHY 2012-05-23 4:51 ` J, KEERTHY 2012-05-23 4:51 ` J, KEERTHY 2012-05-24 17:24 ` Kevin Hilman 2012-05-24 17:24 ` Kevin Hilman 2012-05-24 17:24 ` Kevin Hilman 2012-05-31 22:40 ` Kevin Hilman 2012-05-31 22:40 ` Kevin Hilman 2012-05-31 22:40 ` Kevin Hilman 2012-06-01 3:45 ` J, KEERTHY [this message] 2012-06-01 3:45 ` J, KEERTHY 2012-04-26 18:05 Keerthy 2012-04-26 18:05 ` Keerthy 2012-04-26 18:05 ` Keerthy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAJ6a13YzgxK1QJVLd+ZKRM=w4mM3P3YXicwdazpBaRDqdUDHqA@mail.gmail.com' \ --to=j-keerthy@ti.com \ --cc=greg@kroah.com \ --cc=j-pihet@ti.com \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux-pm@lists.linux-foundation.org \ --cc=rjw@sisk.pl \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.