From: Daniel Mack <daniel@caiaq.de>
To: hartleys <hartleys@visionengravers.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] generic driver for rotary encoders on GPIOs
Date: Fri, 27 Feb 2009 19:34:49 +0100 [thread overview]
Message-ID: <20090227183449.GD8855@buzzloop.caiaq.de> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901349198@mi8nycmail19.Mi8.com>
On Fri, Feb 27, 2009 at 01:30:15PM -0500, hartleys wrote:
> On Friday, February 27, 2009 11:01 AM, Daniel Mack wrote:
> > This patch adds a generic driver for rotary encoders connected to
> > GPIO pins of a system. It relies on gpiolib and generic hardware
> > irqs. The documentation that also comes with this patch explains
> > the concept and how to use the driver.
> >
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > ---
> > new version as discussed on linux-input.
>
> Works great now on the ep93xx with no changes.
Glad to hear that :)
> I have a minor patch to it that allows the platform init to configure
> the absolute/relative axis to report the encoder on. If you would like
> to see it I can put together a patch.
Yes, and probably just post it as follow-up as soon as this one has been
commited. I'm new to this list, so I don't know who can/will/wants to do
this?
> Also, any ideas if the driver could be modified to support more that one
> rotary encoder?
>
> It might be possible to load driver multiple times, once for each
> encoder, but then all the events show up in different /dev/input/event*
> places.
That would have been my idea as well. It doesn't really matter how many
input devices you listen to from user space and as the number of
encoders on a certain board is not dynamic, I don't see much reason to
put any efford in this ;)
Daniel
next prev parent reply other threads:[~2009-02-27 18:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 18:00 [PATCH] generic driver for rotary encoders on GPIOs Daniel Mack
2009-02-26 18:42 ` Daniel Mack
2009-02-27 3:18 ` hartleys
2009-02-27 6:43 ` Daniel Mack
2009-02-27 8:48 ` Daniel Mack
2009-02-27 17:13 ` hartleys
2009-02-27 17:17 ` Daniel Mack
2009-02-27 18:00 ` Daniel Mack
2009-02-27 18:30 ` hartleys
2009-02-27 18:34 ` Daniel Mack [this message]
2009-02-27 20:15 ` hartleys
2009-03-02 14:43 ` Daniel Mack
2009-03-03 8:52 ` Dmitry Torokhov
2009-03-03 9:03 ` Dmitry Torokhov
2009-03-03 9:59 ` Daniel Mack
2009-03-04 8:48 ` Dmitry Torokhov
2009-03-04 9:50 ` Daniel Mack
2009-03-04 17:02 ` hartleys
2009-03-04 17:20 ` Daniel Mack
2009-03-07 17:06 ` Daniel Mack
2009-04-13 23:06 ` [PATCH] add REL_* axes support to the rotary encoder driver H Hartley Sweeten
2009-04-14 5:50 ` Daniel Mack
2009-04-14 15:33 ` H Hartley Sweeten
2009-04-16 2:08 ` Dmitry Torokhov
2009-04-16 2:24 ` H Hartley Sweeten
2009-04-16 2:33 ` Dmitry Torokhov
2009-04-16 3:11 ` H Hartley Sweeten
2009-04-16 6:35 ` Daniel Mack
2009-04-16 8:05 ` Daniel Mack
2009-04-16 16:48 ` H Hartley Sweeten
2009-04-16 8:39 ` Daniel Mack
2009-04-16 17:09 ` H Hartley Sweeten
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=20090227183449.GD8855@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=hartleys@visionengravers.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.