mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: 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-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences
Date: Fri, 27 Jul 2012 11:20:23 -0700	[thread overview]
Message-ID: <20120727182023.GC23564@kroah.com> (raw)
In-Reply-To: <1343390750-3642-2-git-send-email-acourbot@nvidia.com>

On Fri, Jul 27, 2012 at 09:05:48PM +0900, Alexandre Courbot wrote:
> +++ b/include/linux/power_seq.h
> @@ -0,0 +1,139 @@
> +/*
> + * power_seq.h
> + *
> + * Simple interpreter for defining power sequences as platform data or device
> + * tree properties. Initially designed for use with backlight drivers.
> + *
> + * Power sequences are designed to replace the callbacks typically used in
> + * board-specific files that implement board-specific power sequences of devices
> + * such as backlights. A power sequence is an array of resources (which can a
> + * regulator, a GPIO, a PWM, ...) with an action to perform on it (enable or
> + * disable) and optional pre and post step delays. By having them interpreted
> + * instead of arbitrarily executed, it is possible to describe these in the
> + * device tree and thus remove board-specific code from the kernel.
> + *
> + * Author: Alexandre Courbot <acourbot@nvidia.com>
> + *
> + * Copyright (c) 2012 NVIDIA Corporation.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; version 2 of the License.
> + *
> + * This program is distributed in the hope that it will be useful, but WITHOUT
> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> + * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
> + * more details.
> + *
> + * You should have received a copy of the GNU General Public License along
> + * with this program; if not, write to the Free Software Foundation, Inc.,
> + * 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.

As I always say:
	Unless you want to track the office movements of the FSF for the
	next 40 years, and keep this file up to date, drop that last
	paragraph, it's pointless.


  parent reply	other threads:[~2012-07-27 18:20 UTC|newest]

Thread overview: 63+ 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       ` Gethering power management/policy hw drivers under drivers/power/? (Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences) Anton Vorontsov
2012-07-30 20:59         ` Rafael J. Wysocki
2012-08-01  0:51           ` Anton Vorontsov
2012-08-06  8:45         ` Pihet-XID, Jean
2012-07-27 18:20   ` Greg Kroah-Hartman [this message]
2012-07-30 11:00   ` [RFC][PATCH v3 1/3] runtime interpreted power sequences 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

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=20120727182023.GC23564@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acourbot@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --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

Powered by JetHome