From: Mark Brown <broonie@kernel.org>
To: Grant Likely <grant.likely@linaro.org>
Cc: Romain Perier <romain.perier@gmail.com>,
devicetree@vger.kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, heiko@sntech.de, robh@kernel.org,
mark.rutland@arm.com
Subject: Re: [RFC v3 PATCH 1/5] of: Add standard property for poweroff capability
Date: Wed, 15 Oct 2014 15:42:45 +0200 [thread overview]
Message-ID: <20141015134245.GH27755@sirena.org.uk> (raw)
In-Reply-To: <20141015124142.92D0EC40B00@trevor.secretlab.ca>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Wed, Oct 15, 2014 at 02:41:42PM +0200, Grant Likely wrote:
> , Romain Perier <romain.perier@gmail.com>
> wrote:
> > Several drivers create their own devicetree property when they register
> > poweroff capabilities. This is for example the case for mfd, regulator
> > or power drivers which define "vendor,system-power-controller" property.
> > This patch adds support for a standard property "poweroff-source"
> > which marks the device as able to shutdown the system.
> > Signed-off-by: Romain Perier <romain.perier@gmail.com>
> Acked-by: Grant Likely <grant.likely@linaro.org>
> And same for the documentation patches.
I guess I should apply these (except the DTS update) since the first
user that's being added is a regulator driver?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-15 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 6:31 Romain Perier
2014-10-14 6:31 ` [RFC PATCH v3 2/5] regulator: act8865: Add support to turn off all outputs Romain Perier
2014-10-14 6:31 ` [RFC PATCH v3 3/5] ARM: dts: rockchip: Enable power off in pmic for Radxa Rock Romain Perier
2014-10-14 6:31 ` [RFC PATCH v3 4/5] dt-bindings: Document the standard property "poweroff-source" Romain Perier
2014-10-14 6:31 ` [RFC PATCH v3 5/5] dt-bindings: Document the property poweroff-source for act8865 regulator Romain Perier
2014-10-15 12:41 ` [RFC v3 PATCH 1/5] of: Add standard property for poweroff capability Grant Likely
2014-10-15 13:42 ` Mark Brown [this message]
2014-10-15 13:56 ` Heiko Stübner
2014-10-15 14:03 ` Mark Brown
2014-10-17 6:01 ` PERIER Romain
2014-10-17 6:06 ` Heiko Stübner
2014-10-17 7:23 ` PERIER Romain
2014-10-21 13:29 ` PERIER Romain
2014-10-22 15:59 ` Mark Brown
2014-10-23 9:53 ` Johan Hovold
2014-10-25 7:28 ` Romain Perier
2014-10-25 8:37 ` Johan Hovold
2014-10-26 11:53 ` Heiko Stübner
2014-10-26 14:58 ` Romain Perier
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=20141015134245.GH27755@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=romain.perier@gmail.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
all inboxes | Powered by JetHome®