From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: jhovold@gmail.com, linux-input@vger.kernel.org
Subject: Re: rotary_encoder
Date: Tue, 21 May 2013 12:13:22 -0700 [thread overview]
Message-ID: <2575756.Fe0zP7tL6X@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <CAH9NwWdZ0uj7pCtB6TOtTbGP7iU4HBYd2nBWajvARO6haOn1iw@mail.gmail.com>
On Tuesday, May 21, 2013 10:38:44 AM Christian Gmeiner wrote:
> Hi
>
> I have a device with a rotary encoder and I got the device working with
> the generic driver for rotary encoders connected to GPIO lines. Now my
> goal is to send two different key codes - depending on the rotation
> direction.
>
> left ->ALT + tab
> right -> tab
>
> Is there a way to extend the current encoder, which is accepted for mainline
> inclusion or should I do this step in user space?
Userspace please.
--
Dmitry
next prev parent reply other threads:[~2013-05-21 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 8:38 rotary_encoder Christian Gmeiner
2013-05-21 19:13 ` Dmitry Torokhov [this message]
[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
[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=2575756.Fe0zP7tL6X@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=jhovold@gmail.com \
--cc=linux-input@vger.kernel.org \
/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.