From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [PATCH v3 0/1] Input: gpio-keys: support for disabling GPIOs Date: Thu, 4 Feb 2010 00:53:56 -0800 Message-ID: <20100204085355.GA8003@core.coreip.homeip.net> References: <20091203061912.GA5626@gw.healthdatacare.com> <20091203062641.GH9121@core.coreip.homeip.net> <20091215070507.GD25613@gw.healthdatacare.com> <20091216082528.GI2699@core.coreip.homeip.net> <1264713666.12714.1.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-yx0-f189.google.com ([209.85.210.189]:48843 "EHLO mail-yx0-f189.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755590Ab0BDIyE (ORCPT ); Thu, 4 Feb 2010 03:54:04 -0500 Received: by yxe27 with SMTP id 27so1983258yxe.4 for ; Thu, 04 Feb 2010 00:54:02 -0800 (PST) Content-Disposition: inline In-Reply-To: <1264713666.12714.1.camel@localhost.localdomain> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Artem Bityutskiy Cc: Mika Westerberg , linux-input@vger.kernel.org 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