From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: MyungJoo Ham <myungjoo.ham@gmail.com>
Cc: Greg KH <gregkh@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
NeilBrown <neilb@suse.de>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Mike Lockwood <lockwood@android.com>,
Arve Hj?nnev?g <arve@android.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Donggeun Kim <dg77.kim@samsung.com>,
Grant Likely <grant.likely@secretlab.ca>,
Kalle Komierowski <karl.komierowski@stericsson.com>,
Johan PALSSON <johan.palsson@stericsson.com>,
Daniel WILLERUD <daniel.willerud@stericsson.com>
Subject: Re: [RFC PATCH 0/3] introduce: Multistate Switch Class
Date: Wed, 30 Nov 2011 09:46:09 +0000 [thread overview]
Message-ID: <20111130094609.GA19839@sirena.org.uk> (raw)
In-Reply-To: <CAJ0PZbR_N+=51AkcP5ijP31ka7G7EXbL8hSzK+umd_W6HPP2gg@mail.gmail.com>
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@suse.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).
next prev parent reply other threads:[~2011-11-30 9:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 2:03 MyungJoo Ham
2011-11-25 14:02 ` Arnd Bergmann
2011-11-26 5:46 ` MyungJoo Ham
2011-11-26 13:23 ` Kyungmin Park
2011-11-27 22:43 ` Linus Walleij
2011-11-27 23:08 ` Greg KH
2011-11-28 0:09 ` Dmitry Torokhov
2011-11-28 0:19 ` Greg KH
2011-11-28 9:03 ` Dmitry Torokhov
2011-11-28 1:31 ` NeilBrown
2011-11-28 7:27 ` Greg KH
2011-11-28 9:04 ` Dmitry Torokhov
2011-11-30 6:35 ` Greg KH
2011-11-30 6:58 ` MyungJoo Ham
2011-11-30 9:46 ` Mark Brown [this message]
2011-11-30 13:28 ` Linus Walleij
2011-11-30 23:04 ` NeilBrown
2011-12-01 13:38 ` Linus Walleij
2011-11-28 13:04 ` Linus Walleij
2011-11-28 15:09 ` Morten CHRISTIANSEN
2011-11-30 6:34 ` Greg KH
2011-11-28 17:53 ` Arnd Bergmann
2011-11-29 9:11 ` MyungJoo Ham
2011-11-29 9:45 ` Linus Walleij
2011-11-29 13:59 ` Arnd Bergmann
2011-11-29 17:05 ` Dmitry Torokhov
2011-11-30 2:58 ` NeilBrown
2011-11-30 6:40 ` MyungJoo Ham
2011-11-30 22:56 ` NeilBrown
2011-11-30 23:17 ` Mark Brown
2011-11-30 23:25 ` Dmitry Torokhov
2011-12-01 4:51 ` MyungJoo Ham
2011-12-01 5:21 ` NeilBrown
2011-12-01 11:34 ` Mark Brown
2011-12-05 3:04 ` NeilBrown
2011-12-05 12:06 ` Mark Brown
2011-12-05 19:38 ` NeilBrown
2011-12-05 19:45 ` Mark Brown
2011-12-01 4:46 ` MyungJoo Ham
2011-12-07 9:31 ` Linus Walleij
2011-12-08 4:42 ` Kyungmin Park
2011-11-26 15:32 ` Greg KH
2011-11-29 8:18 ` MyungJoo Ham
2011-11-28 18:23 ` Mark Brown
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=20111130094609.GA19839@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=daniel.willerud@stericsson.com \
--cc=dg77.kim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=johan.palsson@stericsson.com \
--cc=karl.komierowski@stericsson.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lockwood@android.com \
--cc=myungjoo.ham@gmail.com \
--cc=neilb@suse.de \
/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
all inboxes | Powered by JetHome®