From: Chris Zhong <zyw@rock-chips.com>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: heiko@sntech.de, dianders@chromium.org, dtor@chromium.org,
djkurtz@chromium.org, sonnyrao@chromium.org,
linux-rockchip@lists.infradead.org,
Sebastian Reichel <sre@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-pm@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] power: gpio-charger: support disable the wakeup event
Date: Tue, 10 Feb 2015 18:50:32 +0800 [thread overview]
Message-ID: <54D9E278.2030205@rock-chips.com> (raw)
In-Reply-To: <CALT56yO5JNB7bucSn53wcnoUWFzkLCCpWe13JhsG1ty7L5v3zw@mail.gmail.com>
On 02/10/2015 04:42 PM, Dmitry Eremin-Solenikov wrote:
> Hello,
>
> 2015-02-10 11:12 GMT+03:00 Chris Zhong <zyw@rock-chips.com>:
>> Support disable the wakeup event of gpio-charger by setting device tree.
> I have the feelink, that this should be a userspace setting, rather than
> a kernel/device-tree policy. In the end, the device tree is a hardware
> description
> and a hardware is capable of waking up the device.
Ah, you are right, I think I should modify it in userspace.
Thank you.
>
>> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>
prev parent reply other threads:[~2015-02-10 10:50 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
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 [this message]
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=54D9E278.2030205@rock-chips.com \
--to=zyw@rock-chips.com \
--cc=dbaryshkov@gmail.com \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dtor@chromium.org \
--cc=dwmw2@infradead.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sonnyrao@chromium.org \
--cc=sre@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 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.