[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111128090446.GB18919@core.coreip.homeip.net>
Date: Mon, 28 Nov 2011 01:04:46 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Greg KH <gregkh@...e.de>
Cc: NeilBrown <neilb@...e.de>,
Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>, myungjoo.ham@...il.com,
linux-kernel@...r.kernel.org, Mike Lockwood <lockwood@...roid.com>,
Arve Hjønnevåg <arve@...roid.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Donggeun Kim <dg77.kim@...sung.com>,
Grant Likely <grant.likely@...retlab.ca>,
Kalle Komierowski <karl.komierowski@...ricsson.com>,
Johan PALSSON <johan.palsson@...ricsson.com>,
Daniel WILLERUD <daniel.willerud@...ricsson.com>
Subject: Re: [RFC PATCH 0/3] introduce: Multistate Switch Class
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.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists