From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: linus.walleij@linaro.org
Cc: lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
gnurou@gmail.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: [PATCH 3/3] mfd: arizona: Update GPIO binding for newly supported flag
Date: Tue, 16 May 2017 16:31:54 +0100 [thread overview]
Message-ID: <1494948714-15203-3-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1494948714-15203-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
Update the device tree binding to show that the new GPIO_SLEEP flags are
now supported in the flags field of the GPIO binding for Arizona
devices.
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
---
Documentation/devicetree/bindings/mfd/arizona.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
index 8f2e282..1729133 100644
--- a/Documentation/devicetree/bindings/mfd/arizona.txt
+++ b/Documentation/devicetree/bindings/mfd/arizona.txt
@@ -30,7 +30,10 @@ Required properties:
- gpio-controller : Indicates this device is a GPIO controller.
- #gpio-cells : Must be 2. The first cell is the pin number and the
- second cell is used to specify optional parameters (currently unused).
+ second cell is used to specify optional parameters, the following flags
+ are supported:
+ "GPIO_SLEEP_MAY_LOOSE_OUTPUT" the output of this GPIO does not need to
+ be maintained whilst the CODEC is in low power mode.
- AVDD-supply, DBVDD1-supply, CPVDD-supply : Power supplies for the device,
as covered in Documentation/devicetree/bindings/regulator/regulator.txt
--
2.1.4
next prev parent reply other threads:[~2017-05-16 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 15:31 [PATCH 1/3] gpio: Add new flags to control sleep status of GPIOs Charles Keepax
2017-05-16 15:31 ` Charles Keepax [this message]
2017-05-23 0:16 ` [PATCH 3/3] mfd: arizona: Update GPIO binding for newly supported flag Rob Herring
[not found] ` <1494948714-15203-3-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-22 11:07 ` Lee Jones
2017-05-22 11:07 ` Lee Jones
2017-05-23 8:49 ` Linus Walleij
2017-05-23 9:00 ` Charles Keepax
[not found] ` <1494948714-15203-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-05-16 15:31 ` [PATCH 2/3] gpio: arizona: Add support for GPIOs that need to be maintained Charles Keepax
2017-05-23 8:46 ` Linus Walleij
2017-05-23 8:56 ` Charles Keepax
2017-05-23 8:39 ` [PATCH 1/3] gpio: Add new flags to control sleep status of GPIOs Linus Walleij
[not found] ` <CACRpkdbiyZ9jPnuaX9OuYjVbrUYxtpqO-XMqb75ScCEH-=kOEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-23 8:51 ` Lee Jones
2017-05-23 13:38 ` Rob Herring
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=1494948714-15203-3-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=robh+dt@kernel.org \
/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).