From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: lib-sysfs: Add 'wakeup' attribute
Date: Mon, 27 Oct 2014 10:55:50 -0700 [thread overview]
Message-ID: <7f23a896baa04960a1702335b3df0432@BL2FFO11FD060.protection.gbl> (raw)
In-Reply-To: <CACRpkdYh3bZLodeNYubu_WQ-O=5My0Jt=b3g2GT3Mvy2XZMrLg@mail.gmail.com>
On Mon, 2014-10-27 at 05:52PM +0100, Linus Walleij wrote:
> On Tue, Oct 14, 2014 at 1:50 AM, Soren Brinkmann
> <soren.brinkmann@xilinx.com> wrote:
>
> > Add an attribute 'wakeup' to the GPIO sysfs interface which allows
> > marking/unmarking a GPIO as wake IRQ.
> > The file 'wakeup' is created in each exported GPIOs directory, if an IRQ
> > is associated with that GPIO and the irqchip implements set_wake().
> > Writing 'enabled' to that file will enable wake for that GPIO, while
> > writing 'disabled' will disable wake.
> > Reading that file will return either 'disabled' or 'enabled' depening on
> > the currently set flag for the GPIO's IRQ.
> >
> > Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> > Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
> > ---
> > v2:
> > - fix error path to unlock mutex before return
>
> As you're adding an ABI, you should be patching
> Documentation/ABI/testing/sysfs-gpio and
> Documentation/gpio/sysfs.txt in this patch.
>
> While I *HATE* the idea of adding IRQ support to userspace
> for GPIOs, this "just" adds the wakeup capacity, so I guess I'm
> OK with it.
>
> Provided you add it to the ABI doc...
Thanks. I will add some documentation and sent a new patch.
Thanks,
Sören
prev parent reply other threads:[~2014-10-27 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 23:50 Soren Brinkmann
2014-10-27 16:52 ` Linus Walleij
2014-10-27 17:55 ` Sören Brinkmann [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=7f23a896baa04960a1702335b3df0432@BL2FFO11FD060.protection.gbl \
--to=soren.brinkmann@xilinx.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®