From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Mika Westerberg <mika.westerberg@iki.fi>, linux-input@vger.kernel.org
Subject: Re: [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs
Date: Thu, 4 Feb 2010 00:53:56 -0800 [thread overview]
Message-ID: <20100204085355.GA8003@core.coreip.homeip.net> (raw)
In-Reply-To: <1264713666.12714.1.camel@localhost.localdomain>
On Thu, Jan 28, 2010 at 11:21:06PM +0200, Artem Bityutskiy wrote:
> On Wed, 2009-12-16 at 00:25 -0800, Dmitry Torokhov wrote:
> > On Tue, Dec 15, 2009 at 09:05:07AM +0200, Mika Westerberg wrote:
> > > On Wed, Dec 02, 2009 at 10:26:41PM -0800, Dmitry Torokhov wrote:
> > > > On Thu, Dec 03, 2009 at 08:19:12AM +0200, Mika Westerberg wrote:
> > > > > On Tue, Dec 01, 2009 at 03:53:45PM +0200, Mika Westerberg wrote:
> > > > > >
> > > > > > This is third version of the series. Purpose of this patch is to allow
> > > > > > userland to disable GPIO buttons interrupting the CPU. There is now sysfs
> > > > > > interface that can be used to control the buttons by key code or by switch
> > > > > > code.
> > > > > >
> > > > > > I merged those previous 2 patches as one. This is because it made little
> > > > > > sense of having separate patch for adding the 'can_disable' field.
> > > > > >
> > > > > > Changes in v3:
> > > > > > - merged previous 2 patches into one
> > > > > > - buttons have 'can_disable' field instead of irqflags field
> > > > > >
> > > > > > Tested with RX-51.
> > > > >
> > > > > Hi Dmitry,
> > > > >
> > > > > Any comments on this? Is it OK to be applied or do I need to change
> > > > > something.
> > > > >
> > > >
> > > > Hi Mika,
> > > >
> > > > SOrry, I am still pondering how to go about it. I am sure that the sysfs
> > > > interface is proper, so at this point it is just implementation details
> > > > that I am not quite sure yet...
> > >
> > > Hi Dmitry,
> > >
> > > Have you decided yet what to do with these patches?
> > >
> >
> > Hi Mika,
> >
> > Sorry, not yet, have been busy with some other stuff ;(
>
> Hi Dmitry,
>
> any news? We missed 2.6.33, and the next merge window is coming ...
>
Artem, Mika,
I was hoping to do something different about the new 'can_disable' flag
but unfortunately I don't have enough time and I already sat on the
patch for way too long. :(
It is applied to my 'next' branch and should get pulled into 2.6.34.
Thank you for your patience and sorry about the delay.
--
Dmitry
next prev parent reply other threads:[~2010-02-04 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 13:53 [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Mika Westerberg
2009-12-01 13:53 ` [PATCH v3 1/1] Input: gpio-keys - added support for disabling gpios through sysfs Mika Westerberg
2009-12-03 6:19 ` [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Mika Westerberg
2009-12-03 6:26 ` Dmitry Torokhov
2009-12-03 8:09 ` Mika Westerberg
2009-12-15 7:05 ` Mika Westerberg
2009-12-16 8:25 ` Dmitry Torokhov
2010-01-10 11:45 ` Artem Bityutskiy
2010-01-28 21:21 ` Artem Bityutskiy
2010-02-04 8:53 ` Dmitry Torokhov [this message]
2010-02-04 9:22 ` Artem Bityutskiy
2010-02-04 18:00 ` Mika Westerberg
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=20100204085355.GA8003@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
/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).