From: Mark Rutland <mark.rutland@arm.com>
To: Chris Zhong <zyw@rock-chips.com>
Cc: "heiko@sntech.de" <heiko@sntech.de>,
"dianders@chromium.org" <dianders@chromium.org>,
"dtor@chromium.org" <dtor@chromium.org>,
"djkurtz@chromium.org" <djkurtz@chromium.org>,
"sonnyrao@chromium.org" <sonnyrao@chromium.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Heiko Stuebner <heiko.stuebner@bq.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: add disable-wakeup property for gpio-charger
Date: Tue, 10 Feb 2015 12:00:30 +0000 [thread overview]
Message-ID: <20150210120030.GD6659@leverpostej> (raw)
In-Reply-To: <1423555945-24289-2-git-send-email-zyw@rock-chips.com>
On Tue, Feb 10, 2015 at 08:12:24AM +0000, Chris Zhong wrote:
> add disable-wakeup for gpio-charger, if you set this property, system
> will not wakeup by gpio-charger.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> ---
>
> Documentation/devicetree/bindings/power_supply/gpio-charger.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power_supply/gpio-charger.txt b/Documentation/devicetree/bindings/power_supply/gpio-charger.txt
> index adbb5dc..a46e9bc 100644
> --- a/Documentation/devicetree/bindings/power_supply/gpio-charger.txt
> +++ b/Documentation/devicetree/bindings/power_supply/gpio-charger.txt
> @@ -4,6 +4,7 @@ Required properties :
> - compatible : "gpio-charger"
> - gpios : GPIO indicating the charger presence.
> See GPIO binding in bindings/gpio/gpio.txt .
> + - gpio-charger,disable-wakeup : Boolean, charger does not wake-up the system.
When would the system wake up otherwise?
Also, "gpio-charger" is not a vendor prefix.
Mark.
> - charger-type : power supply type, one of
> unknown
> battery
> @@ -20,6 +21,7 @@ Example:
> compatible = "gpio-charger";
> charger-type = "usb-sdp";
> gpios = <&gpf0 2 0 0 0>;
> + gpio-charger,disable-wakeup;
> }
>
> battery {
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-02-10 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 8:12 [PATCH 0/2] Support disable the wakeup event of gpio-charger Chris Zhong
2015-02-10 8:12 ` [PATCH 1/2] dt-bindings: add disable-wakeup property for gpio-charger Chris Zhong
2015-02-10 12:00 ` Mark Rutland [this message]
2015-02-10 12:14 ` Heiko Stübner
2015-02-10 12:14 ` Heiko Stübner
2015-02-10 12:33 ` Mark Rutland
2015-02-10 8:12 ` [PATCH 2/2] power: gpio-charger: support disable the wakeup event Chris Zhong
2015-02-10 8:42 ` Dmitry Eremin-Solenikov
2015-02-10 10:50 ` Chris Zhong
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=20150210120030.GD6659@leverpostej \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dtor@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko.stuebner@bq.com \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sonnyrao@chromium.org \
--cc=zyw@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.