linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Alex Courbot <acourbot@nvidia.com>, Jean Pihet <j-pihet@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Stephen Warren <swarren@nvidia.com>,
	Thierry Reding <thierry.reding@avionic-design.de>,
	Simon Glass <sjg@chromium.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>, Liam Girdwood <lrg@ti.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-pm@vger.kernel.org
Subject: Gethering power management/policy hw drivers under drivers/power/? (Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences)
Date: Sun, 29 Jul 2012 19:40:52 -0700	[thread overview]
Message-ID: <20120730024049.GA10442@lizard> (raw)
In-Reply-To: <5015E8AE.8060404@nvidia.com>

On Mon, Jul 30, 2012 at 10:51:42AM +0900, Alex Courbot wrote:
[...]
> On the other hand I have just noticed that the apparently unrelated
> Adaptive Voltage Scaling driver just appeared in drivers/power/avs.
> So if Anton and David are ok with this, maybe I could put the power
> sequences code in its own subdirectory within drivers/power.

Well, currently drivers/power/ is indeed just for power supply class
subsystem and drivers. But if the trend is to gather power management
("policy") stuff under one directory, i.e.

drivers/
  power/
    supplies/    <- former "power supply class and drivers"
    regulators/
    idle/
    cpuidle/
    cpufreq/
    devfreq/
    avs/
    ...

That would probably make sense, we could easily see the big picture.
But if we're not going to do this long-term, I would suggest to stick
to just a new directory under drivers (and move drivers/power/avs/ to
drivers/avs).

Cc'ing some more people...

Thanks,

p.s. Jean, why am I the last person who discovers drivers/power/avs/?
Would be nice to Cc me on such patches; by moving AVS under
drivers/power/ you effectively nominated me as its maintainer. :-)

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

  reply	other threads:[~2012-07-30  2:44 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 12:05 [RFC][PATCH v3 0/3] Power sequences with PWM and DT support Alexandre Courbot
2012-07-27 12:05 ` [RFC][PATCH v3 1/3] runtime interpreted power sequences Alexandre Courbot
2012-07-27 18:19   ` Greg Kroah-Hartman
2012-07-30  1:51     ` Alex Courbot
2012-07-30  2:40       ` Anton Vorontsov [this message]
2012-07-30 20:59         ` Gethering power management/policy hw drivers under drivers/power/? (Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences) Rafael J. Wysocki
2012-08-01  0:51           ` Anton Vorontsov
2012-08-06  8:45         ` Pihet-XID, Jean
2012-07-27 18:20   ` [RFC][PATCH v3 1/3] runtime interpreted power sequences Greg Kroah-Hartman
2012-07-30 11:00   ` Simon Glass
2012-07-31  8:37     ` Alex Courbot
2012-07-31  9:13       ` Thierry Reding
2012-07-31 10:11         ` Alex Courbot
2012-07-31 10:46           ` Thierry Reding
2012-07-31 14:23       ` Mark Brown
2012-07-30 11:33   ` Thierry Reding
2012-07-31  9:51     ` Alex Courbot
2012-07-31 10:19       ` Thierry Reding
2012-08-01  2:50         ` Alex Courbot
2012-08-01  7:17           ` Thierry Reding
2012-07-31 14:11       ` Mark Brown
2012-07-30 15:44   ` Rob Herring
2012-07-30 15:47     ` Mark Brown
2012-07-31  9:16       ` Thierry Reding
2012-07-30 22:26     ` Stephen Warren
2012-07-31 10:15       ` Alex Courbot
2012-07-30 22:45   ` Stephen Warren
2012-07-31 10:32     ` Alex Courbot
2012-07-31 10:56       ` Thierry Reding
2012-07-31 12:22         ` Mitch Bradley
2012-07-31 12:38           ` Thierry Reding
2012-07-31 12:55             ` Mitch Bradley
2012-08-01  1:47               ` Alex Courbot
2012-08-01  2:15                 ` Mitch Bradley
2012-08-01  1:42           ` Alex Courbot
2012-07-31 14:13         ` Mark Brown
2012-07-31 14:22           ` Thierry Reding
2012-07-31 14:26             ` Mark Brown
2012-07-31 14:32               ` Thierry Reding
2012-07-31 15:39                 ` Mark Brown
2012-07-31 16:19                   ` Greg Kroah-Hartman
2012-07-31 16:22                     ` Mark Brown
2012-07-31 16:42                       ` Greg Kroah-Hartman
2012-07-31 16:50                         ` Mark Brown
2012-08-01  7:41                   ` Thierry Reding
2012-08-01 13:26                     ` Mark Brown
2012-08-01 13:38                       ` Thierry Reding
2012-08-01 13:55                         ` Mark Brown
2012-08-01 14:01                           ` Thierry Reding
2012-07-31 16:34       ` Stephen Warren
2012-08-02  8:00     ` Alex Courbot
2012-08-02  8:21       ` Thierry Reding
2012-08-02  8:27         ` Alex Courbot
2012-08-02  8:45           ` Thierry Reding
2012-08-02  9:20             ` Alex Courbot
2012-08-02 18:11         ` Mark Brown
2012-08-03  1:15           ` Alex Courbot
2012-08-04 14:12             ` Mark Brown
2012-08-06  2:27               ` Alex Courbot
2012-08-06 16:16                 ` Stephen Warren
2012-08-07  5:10                   ` Alex Courbot
2012-07-27 12:05 ` [RFC][PATCH v3 2/3] pwm_backlight: use " Alexandre Courbot
2012-07-27 12:05 ` [RFC][PATCH v3 3/3] tegra: add pwm backlight device tree nodes Alexandre Courbot
  -- strict thread matches above, loose matches on Subject: below --
2012-07-30  3:04 Gethering power management/policy hw drivers under drivers/power/? (Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences) 함명주

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=20120730024049.GA10442@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dwmw2@infradead.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=j-pihet@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@sisk.pl \
    --cc=rob.herring@calxeda.com \
    --cc=sjg@chromium.org \
    --cc=swarren@nvidia.com \
    --cc=thierry.reding@avionic-design.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).