From: Robin Getz <rgetz@blackfin.uclinux.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bryan Wu <cooloney@kernel.org>,
khali@linux-fr.org, andre@bitwigglers.org,
linux-input@vger.kernel.org, i2c@lm-sensors.org,
linux-kernel@vger.kernel.org, vapier.adi@gmail.com,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH 1/1] Input/Joystick Driver: add support AD7142 joystickdriver (v2)
Date: Sat, 26 Apr 2008 21:09:09 -0400 [thread overview]
Message-ID: <200804262109.09596.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <20080425113501.ZZRA012@mailhub.coreip.homeip.net>
On Fri 25 Apr 2008 11:39, Dmitry Torokhov pondered:
> On Fri, Apr 25, 2008 at 06:09:52PM +0800, Bryan Wu wrote:
> > On Sat, Apr 19, 2008 at 1:15 AM, Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > > Hi Bryan,
> > >
> > > Why don't you use REL_X/REL_Y to report directional movement? Using
> > > buttons for that is pretty unusual.
> > >
> >
> > In our development board, it includes UP/DOWN/LEFT/RIGHT 4 buttons. So
> > this driver matches this.
> > Please found some information about the hardware as below:
> >
> http://docs.blackfin.uclinux.org/doku.php?id=capacitance_touch_sensors&s
> []=ad7142
>
> What is the expected behaviur when a person touches one of these
> buttons?
It depends on the design of the button on the target hardware. They can be
pretty much any number of different shapes and sizes. Buttons, wheels,
scroll-bar, joypad, and touchpad shapes can be laid out as traces on the
sensor PCB. While we tested/wrote something for what we had hardware to
verify, it is not restricted to this.
As Bryan indicated - have a look at:
http://docs.blackfin.uclinux.org/doku.php?id=capacitance_touch_sensors#overview
for a variety of options.
> Is it generatig a left/rigth mouse button clocks or moving a
> pointer in some direction? Judging by the category of the devices you
> are placing it in (joystick) it seems that latter is what you want,
> therefore it should generate REL_X and REL_Y events. Otherwise it
> should probably be called a button driver and live either in
> drivers/input/keyboard or driver/input/misc. Do you agree?
If someone makes a joypad, it is a joypad. If someone makes a button, it is a
button. The specific ad7142_work function will need to be modified to match
the hardware design.
So, I am not sure where it should live - maybe driver/input/misc since it can
be so many different things. The issue (in my mind) is how it gets exposed to
userspace. If someone makes a joypad - they want it to show up as a joystick,
so they don't have to modify any standard userspace applications to use it.
-Robin
next prev parent reply other threads:[~2008-04-27 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 18:38 [PATCH 1/1] Input/Joystick Driver: add support AD7142 joystick driver (v2) Bryan Wu
[not found] ` <1206643110-8789-1-git-send-email-cooloney-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2008-04-18 17:15 ` Dmitry Torokhov
2008-04-25 10:09 ` Bryan Wu
2008-04-25 15:39 ` Dmitry Torokhov
2008-04-27 1:09 ` Robin Getz [this message]
2008-04-27 13:52 ` Bryan Wu
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=200804262109.09596.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=andre@bitwigglers.org \
--cc=cooloney@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=vapier.adi@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).