From: Stephen Warren <swarren@wwwdotorg.org>
To: sameo@linux.intel.com, broonie@opensource.wolfsonmicro.com,
lrg@slimlogic.co.uk
Cc: Bill Huang <bilhuang@nvidia.com>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, ldewangan@nvidia.com,
thierry.reding@avionic-design.de, xxie@nvidia.com,
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
Subject: Re: [PATCH 1/2] mfd: dt: tps6586x: Add power off control
Date: Fri, 17 Aug 2012 13:05:40 -0600 [thread overview]
Message-ID: <502E9604.4010701@wwwdotorg.org> (raw)
In-Reply-To: <1345194989-11614-2-git-send-email-bilhuang@nvidia.com>
On 08/17/2012 03:16 AM, Bill Huang wrote:
> Add DT property "ti,system-power-controller" telling whether or not this
> pmic is in charge of controlling the system power, so the power off
> routine can be hooked up to system call "pm_power_off".
>
> Based on the work by:
> Dan Willemsen <dwillemsen@nvidia.com>
>
> Signed-off-by: Bill Huang <bilhuang@nvidia.com>
Tested-by: Stephen Warren <swarren@wwwdotorg.org>
Note that this conflicts (only context in tps6586x.txt I think) with
commit b93fffb "regulator: tps6586x: add support for SYS rail" in the
regulator tree. Also note that the patch is based on linux-next, which
contains a mis-merge of tps6586x.txt from the regulator tree. In other
words, expect some slight conflicts when you apply this. Taking it
through the regulator tree would eliminate them.
next prev parent reply other threads:[~2012-08-17 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 9:16 [PATCH 0/2] mfd: dt: add power off support for Tegra20/Tegra30 Bill Huang
2012-08-17 9:16 ` [PATCH 1/2] mfd: dt: tps6586x: Add power off control Bill Huang
2012-08-17 10:41 ` Thierry Reding
2012-08-17 22:45 ` Bill Huang
2012-08-17 19:05 ` Stephen Warren [this message]
2012-08-17 9:16 ` [PATCH 2/2] mfd: dt: tps65910: add " Bill Huang
2012-08-17 10:42 ` Thierry Reding
2012-08-17 19:06 ` Stephen Warren
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=502E9604.4010701@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=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=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).