From: Mark Brown <broonie@kernel.org>
To: Daniel Mack <zonque@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
linux-gpio@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] drivers: misc: add gpio wakeup driver
Date: Wed, 2 Oct 2013 11:57:23 +0100 [thread overview]
Message-ID: <20131002105723.GA27287@sirena.org.uk> (raw)
In-Reply-To: <524AD693.6000304@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On Tue, Oct 01, 2013 at 04:05:07PM +0200, Daniel Mack wrote:
> On 01.10.2013 16:01, Fabio Estevam wrote:
> > Isn't it the same as the existing 'gpio-key,wakeup' ?
> Of course, I know the gpio-input driver can provide similar
> functionality. My intention was just provide a way to wake up the system
> without registering an input device for signals nobody is interested in
> eventually.
> Don't know if that's reason enough to add a new driver though.
It does seem somewhat sensible - the signal might not have a sensible
representation as an input device and the gpio-keys binding needs one.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-02 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 13:55 [PATCH] drivers: misc: add gpio wakeup driver Daniel Mack
2013-10-01 14:01 ` Fabio Estevam
2013-10-01 14:05 ` Daniel Mack
2013-10-02 10:57 ` Mark Brown [this message]
2013-10-02 11:02 ` Daniel Mack
2013-10-11 11:11 ` Linus Walleij
2013-10-11 11:40 ` Daniel Mack
2013-10-11 12:54 ` Linus Walleij
2013-10-15 19:32 ` Arnd Bergmann
2013-10-15 21:35 ` Linus Walleij
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=20131002105723.GA27287@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zonque@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;
as well as URLs for NNTP newsgroup(s).