[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111130094609.GA19839@sirena.org.uk>
Date: Wed, 30 Nov 2011 09:46:09 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: MyungJoo Ham <myungjoo.ham@...il.com>
Cc: Greg KH <gregkh@...e.de>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
NeilBrown <neilb@...e.de>,
Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>, 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 Wed, Nov 30, 2011 at 03:58:54PM +0900, MyungJoo Ham wrote:
> On Wed, Nov 30, 2011 at 3:35 PM, Greg KH <gregkh@...e.de> wrote:
> > Actually, why can't we just use gpio as-is here and just treat these
> > devices as "generic" i/o "pins"?
> For userspace, GPIO should work.
> For device drivers, I'm not sure.
> In order to work for device drives, a GPIO event (GPIO Input goes L->H
> or H->L) should trigger events in other device drivers. The GPIO value
> can be set by the external-connector/multistate-switch driver
> (notifier) based on its own interrupts.
We also need some way to group things together so that we can understand
that we've got a single connector that can detect multiple things (eg,
understanding that a cable hsa audio and video capability).
--
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