From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754655Ab1K3Gfn (ORCPT ); Wed, 30 Nov 2011 01:35:43 -0500 Received: from cantor2.suse.de ([195.135.220.15]:54693 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754495Ab1K3Gfk (ORCPT ); Wed, 30 Nov 2011 01:35:40 -0500 Date: Wed, 30 Nov 2011 15:35:00 +0900 From: Greg KH To: Dmitry Torokhov Cc: NeilBrown , Linus Walleij , Arnd Bergmann , myungjoo.ham@gmail.com, linux-kernel@vger.kernel.org, Mike Lockwood , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Kyungmin Park , Donggeun Kim , Grant Likely , Kalle Komierowski , Johan PALSSON , Daniel WILLERUD Subject: Re: [RFC PATCH 0/3] introduce: Multistate Switch Class Message-ID: <20111130063500.GB12052@suse.de> References: <201111251402.28016.arnd@arndb.de> <20111127230836.GA29728@suse.de> <20111128123114.2601bd7c@notabene.brown> <20111128072713.GA17724@suse.de> <20111128090446.GB18919@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111128090446.GB18919@core.coreip.homeip.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 28, 2011 at 01:04:46AM -0800, Dmitry Torokhov wrote: > On Mon, Nov 28, 2011 at 04:27:13PM +0900, Greg KH wrote: > > On Mon, Nov 28, 2011 at 12:31:14PM +1100, NeilBrown wrote: > > > > > > My own thought is that this deserves a new device class which allows easy > > > hook-up of in-kernel signalling using notifications and which can be > > > exported as input devices in much the same way the 'gpio' devices can be > > > exported via gpio_keys. The switch could also optionally be exported through > > > sysfs much like gpio can be exported through sysfs. > > > > That might also work, but again, odds are the HID spec already defines > > this type of "switch", so why recreate it as a different type of device? > > HID does not map 1:1 on input. There are items in HID that are better > served by other subsystems. Ok fair enough. So, how do you want this type of interface to look like, uevents only? Or something like gpio? Actually, why can't we just use gpio as-is here and just treat these devices as "generic" i/o "pins"? thanks, greg k-h