From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dmitriy Vasil'ev <tech@digiton.ru>
Cc: linux-input@vger.kernel.org
Subject: Re: rotary encoder
Date: Wed, 30 Jun 2010 12:54:34 -0700 [thread overview]
Message-ID: <20100630195433.GB12366@core.coreip.homeip.net> (raw)
In-Reply-To: <30BA0A72AA534DE289E9DA5963938449@tech>
On Wed, Jun 30, 2010 at 01:33:25PM +0400, Dmitriy Vasil'ev wrote:
> >the separate gpio/irq for press button is
> >better handled as a separate input device by gpio_keys driver.
> >
> >Thanks.
> >
> >--
> >Dmitry
>
> Small note:
>
> if you use two separate drivers for rotary encoder and it's button,
> you must work with two device nodes in user space.
Yes.
> If user space driver working with one device node, this more usable.
Not really. Having to deal with multiple input devices is something
that you have to handle. Hotplug, USB (taht sometimes splits its
interfaces into several logical devices), etc - devices are coming
and going and you simply have to handle this.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-06-30 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7A46ED6446BE4CF7AAC51205F1B5A88B@tech>
2010-06-02 13:20 ` rotary encoder Daniel Mack
[not found] ` <BA41AF5D757645AD94502E4B0A29158A@tech>
2010-06-02 13:52 ` Daniel Mack
[not found] ` <888FDE7800AB4E278ED6DF185FEDC869@tech>
2010-06-17 10:10 ` Daniel Mack
[not found] ` <B221BAA24375436992F7587DF15BB812@tech>
2010-06-17 11:21 ` Daniel Mack
2010-06-17 11:29 ` Dmitriy Vasil'ev
2010-06-17 11:37 ` Daniel Mack
2010-06-17 11:55 ` Dmitriy Vasil'ev
2010-06-17 12:00 ` Daniel Mack
2010-06-28 18:22 ` Dmitry Torokhov
2010-06-28 18:32 ` Daniel Mack
2010-06-29 15:06 ` Dmitriy Vasil'ev
2010-06-30 8:40 ` Dmitry Torokhov
2010-06-30 9:33 ` Dmitriy Vasil'ev
2010-06-30 19:54 ` Dmitry Torokhov [this message]
2013-05-21 8:38 rotary_encoder Christian Gmeiner
2013-05-21 19:13 ` rotary_encoder Dmitry Torokhov
[not found] <4BE96550.9020800@solutionsradio.com>
2010-05-11 14:17 ` Rotary encoder Daniel Mack
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=20100630195433.GB12366@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=tech@digiton.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.