public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: lamikr <lamikr@cc.jyu.fi>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] keypad: platform_data and 24xx support -exp
Date: Fri, 20 Jan 2006 15:02:57 -0800	[thread overview]
Message-ID: <20060120230257.GC6683@atomide.com> (raw)
In-Reply-To: <43C85C21.6030202@cc.jyu.fi>

Hi Mika,

* lamikr <lamikr@cc.jyu.fi> [060113 17:57]:
> Has anybody needed a joypad driver for the omap-boards? 
> I have made changes to keypad driver so that it will support h6300 joypad ok, but I think my approach is a little bit hackish.
> The iPAQ h6300 joypad has 5 sensors that are located in following diagonal locations
> 
> 	UL - Up/Left
> 	DL - Down/Left
> 	DR - Down/Right
> 	UR - Up/Right
> 	CT - Center
> 
> If I press the key-pad for example to North, the joypad will generate 3 keydown events. (CT, UL and UR)
> Same logic applies to all 4 main directions both when the key is pressed down or released.
> Therefore I have put the driver to listen the real sensor events, but instead of sending them to userspace
> I will calculate a "virtual" key event (up, right, down or left) and send that to the userspace.
> 
> I am not yet proposing this patch to be applied to omap kernel, but would anyway like to hear
> some suggestions how to handle this kind of situation.

Maybe you could update it now against the current git tree?

Now that all the key mappings are done in board-*.c files it should be
easy to add support for h6300 too.

Tony

  reply	other threads:[~2006-01-20 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10 13:02 [PATCH] keypad: platform_data and 24xx support -exp Komal Shah
2006-01-14  0:37 ` Tony Lindgren
2006-01-14  2:04   ` lamikr
2006-01-20 23:02     ` Tony Lindgren [this message]
2006-01-20 23:27       ` lamikr

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=20060120230257.GC6683@atomide.com \
    --to=tony@atomide.com \
    --cc=lamikr@cc.jyu.fi \
    --cc=linux-omap-open-source@linux.omap.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