linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Huang <bilhuang@nvidia.com>
To: <sameo@linux.intel.com>, <grant.likely@secretlab.ca>,
	<rob.herring@calxeda.com>, <rob@landley.net>
Cc: <broonie@opensource.wolfsonmicro.com>, <ldewangan@nvidia.com>,
	<thierry.reding@avionic-design.de>, <swarren@wwwdotorg.org>,
	<xxie@nvidia.com>, <lrg@slimlogic.co.uk>, <jhovold@gmail.com>,
	<kyle.manna@fuel7.com>, <rklein@nvidia.com>,
	<devicetree-discuss@lists.ozlabs.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Bill Huang <bilhuang@nvidia.com>
Subject: [PATCH v2 0/2] mfd: dt: add power off support for Tegra20/Tegra30
Date: Sun, 19 Aug 2012 18:07:54 -0700	[thread overview]
Message-ID: <1345424876-4365-1-git-send-email-bilhuang@nvidia.com> (raw)

This patch series add new property into regulator DT for telling whether or not
to hook pmic's power off routine to system call "pm_power_off".

Patch 1 add power off support for Tegra20 boards using TPS6586x
Patch 2 add power off support for Tegra30 boards using TPS65910

Verified on Seaboard (Tegra20) and Cardhu (Tegra30)

V2:
* Take multiple pmic instances into consideration while assigning global variables
  as per suggestion from Thierry Reding <thierry.reding@avionic-design.de>

V1:
* Based on master branch of sameo/mfd-2.6.git

Bill Huang (2):
  mfd: dt: tps6586x: Add power off control
  mfd: dt: tps65910: add power off control

 Documentation/devicetree/bindings/mfd/tps65910.txt |    4 +++
 .../devicetree/bindings/regulator/tps6586x.txt     |    6 +++++
 drivers/mfd/tps6586x.c                             |   19 +++++++++++++++++
 drivers/mfd/tps65910.c                             |   22 ++++++++++++++++++++
 include/linux/mfd/tps6586x.h                       |    1 +
 include/linux/mfd/tps65910.h                       |    3 ++
 6 files changed, 55 insertions(+), 0 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2012-08-20  1:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  1:07 Bill Huang [this message]
2012-08-20  1:07 ` [PATCH v2 1/2] mfd: dt: tps6586x: Add power off control Bill Huang
2012-08-20 11:34   ` Thierry Reding
2012-08-22 12:07     ` Bill Huang
2012-08-25  0:36       ` Bill Huang
2012-08-25  3:34         ` Stephen Warren
2012-08-27  5:40           ` Bill Huang
2012-09-05  0:28             ` Bill Huang
2012-08-20  1:07 ` [PATCH v2 2/2] mfd: dt: tps65910: add " Bill Huang
2012-09-11 10:25 ` [PATCH v2 0/2] mfd: dt: add power off support for Tegra20/Tegra30 Bill Huang
2012-09-11 10:46   ` Thierry Reding
2012-09-11 15:15     ` Stephen Warren
2012-09-11 16:08       ` Samuel Ortiz
2012-09-11 16:26         ` Stephen Warren
2012-09-11 18:56           ` Samuel Ortiz
2012-09-11 16:07 ` Samuel Ortiz

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=1345424876-4365-1-git-send-email-bilhuang@nvidia.com \
    --to=bilhuang@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jhovold@gmail.com \
    --cc=kyle.manna@fuel7.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=rklein@nvidia.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=sameo@linux.intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@avionic-design.de \
    --cc=xxie@nvidia.com \
    /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).