All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-omap@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH v2 0/9] PM: Create the AVS class of drivers
Date: Wed, 18 Apr 2012 11:30:00 -0700	[thread overview]
Message-ID: <878vhski53.fsf@ti.com> (raw)
In-Reply-To: <1332173578-27422-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 19 Mar 2012 17:12:49 +0100")

Rafael,

jean.pihet@newoldbits.com writes:

> From: Jean Pihet <j-pihet@ti.com>
>
> AVS 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).
> AVS is also called SmartReflex on OMAP devices.
>
> To that end, create the AVS framework in drivers/power/avs and
> move the OMAP SmartReflex code to the new directory.

I've done a review of this series and had a few very minor comments.

Once those are addressed, are you OK with us moving this AVS driver
under drivers/power?

Thanks,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] PM: Create the AVS class of drivers
Date: Wed, 18 Apr 2012 11:30:00 -0700	[thread overview]
Message-ID: <878vhski53.fsf@ti.com> (raw)
In-Reply-To: <1332173578-27422-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 19 Mar 2012 17:12:49 +0100")

Rafael,

jean.pihet at newoldbits.com writes:

> From: Jean Pihet <j-pihet@ti.com>
>
> AVS 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).
> AVS is also called SmartReflex on OMAP devices.
>
> To that end, create the AVS framework in drivers/power/avs and
> move the OMAP SmartReflex code to the new directory.

I've done a review of this series and had a few very minor comments.

Once those are addressed, are you OK with us moving this AVS driver
under drivers/power?

Thanks,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@ti.com>
To: jean.pihet@newoldbits.com
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH v2 0/9] PM: Create the AVS class of drivers
Date: Wed, 18 Apr 2012 11:30:00 -0700	[thread overview]
Message-ID: <878vhski53.fsf@ti.com> (raw)
In-Reply-To: <1332173578-27422-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Mon, 19 Mar 2012 17:12:49 +0100")

Rafael,

jean.pihet@newoldbits.com writes:

> From: Jean Pihet <j-pihet@ti.com>
>
> AVS 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).
> AVS is also called SmartReflex on OMAP devices.
>
> To that end, create the AVS framework in drivers/power/avs and
> move the OMAP SmartReflex code to the new directory.

I've done a review of this series and had a few very minor comments.

Once those are addressed, are you OK with us moving this AVS driver
under drivers/power?

Thanks,

Kevin


  parent reply	other threads:[~2012-04-18 18:30 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 16:12 [PATCH v2 0/9] PM: Create the AVS class of drivers jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 1/9] ARM: OMAP3+: voltage: export functions to plat/voltage.h jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-04-18 17:27   ` Kevin Hilman
2012-04-18 17:27     ` Kevin Hilman
2012-04-18 20:36     ` Jean Pihet
2012-04-18 20:36       ` Jean Pihet
2012-04-18 20:36       ` Jean Pihet
2012-03-19 16:12 ` [PATCH 2/9] ARM: OMAP2+: SmartReflex: move the driver specific macros in include/linux/power jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-04-04 19:10   ` Trilok Soni
2012-04-04 19:10     ` Trilok Soni
2012-04-04 19:41     ` Cousson, Benoit
2012-04-04 19:41       ` Cousson, Benoit
2012-04-04 19:41       ` Cousson, Benoit
2012-04-05  6:53       ` Trilok Soni
2012-04-05  6:53         ` Trilok Soni
2012-04-05  8:59         ` Jean Pihet
2012-04-05  8:59           ` Jean Pihet
2012-04-05  9:35           ` Trilok Soni
2012-04-05  9:35             ` Trilok Soni
2012-04-19 13:54             ` Arnd Bergmann
2012-04-19 13:54               ` Arnd Bergmann
2012-04-19 16:02               ` Jean Pihet
2012-04-19 16:02                 ` Jean Pihet
2012-04-19 16:02                 ` Jean Pihet
2012-04-19 17:06               ` Kevin Hilman
2012-04-19 17:06                 ` Kevin Hilman
2012-04-19 17:06                 ` Kevin Hilman
2012-03-19 16:12 ` [PATCH 3/9] ARM: OMAP3+: SmartReflex: class drivers should use struct omap_sr * jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 4/9] ARM: OMAP2+: smartreflex: Use the names from hwmod data instead of voltage domains jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 5/9] ARM: OMAP3: hwmod: rename the smartreflex entries jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-04-18 17:33   ` Kevin Hilman
2012-04-18 17:33     ` Kevin Hilman
2012-04-18 20:41     ` Jean Pihet
2012-04-18 20:41       ` Jean Pihet
2012-04-18 20:41       ` Jean Pihet
2012-03-19 16:12 ` [PATCH 6/9] ARM: OMAP2+: SmartReflex: introduce a busy loop condition test macro jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 7/9] ARM: OMAP2+: SmartReflex: Use per-OPP data structure jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-04-18 18:21   ` Kevin Hilman
2012-04-18 18:21     ` Kevin Hilman
2012-04-18 20:52     ` Jean Pihet
2012-04-18 20:52       ` Jean Pihet
2012-04-18 20:52       ` Jean Pihet
2012-03-19 16:12 ` [PATCH 8/9] ARM: OMAP2+: SmartReflex: add POWER_AVS Kconfig options jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 9/9] ARM: OMAP: SmartReflex: Move smartreflex driver to drivers/ jean.pihet
2012-03-19 16:12   ` jean.pihet at newoldbits.com
2012-04-18 18:17   ` Kevin Hilman
2012-04-18 18:17     ` Kevin Hilman
2012-04-03 11:14 ` [PATCH v2 0/9] PM: Create the AVS class of drivers Jean Pihet
2012-04-03 11:14   ` Jean Pihet
2012-04-03 11:14   ` Jean Pihet
2012-04-18  8:04 ` Jean Pihet
2012-04-18  8:04   ` Jean Pihet
2012-04-19  0:08   ` Greg KH
2012-04-19  0:08     ` Greg KH
2012-04-18 18:29 ` Kevin Hilman
2012-04-18 18:29   ` Kevin Hilman
2012-04-18 18:30 ` Kevin Hilman [this message]
2012-04-18 18:30   ` Kevin Hilman
2012-04-18 18:30   ` Kevin Hilman
2012-04-18 18:49   ` Rafael J. Wysocki
2012-04-18 18:49     ` Rafael J. Wysocki
2012-04-18 18:49     ` Rafael J. Wysocki

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=878vhski53.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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: link
Be 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.