From: lamikr <lamikr@cc.jyu.fi>
To: Devendra Kumar Madhesia <devendra.madhesia@flextronicssoftware.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: How to use omap keypad driver function
Date: Sat, 19 Aug 2006 19:14:34 +0300 [thread overview]
Message-ID: <44E738EA.2080904@cc.jyu.fi> (raw)
In-Reply-To: <OF3B719B48.C78BC6D7-ON652571CF.003E457F-652571CF.003EE797@flextronicssoftware.com>
Devendra Kumar Madhesia wrote:
>
>
> Hi,
> Thanks for giving such useful idea.
>
> But I have also some doubt.
> The omap keypad driver is based on interrupt.
> Will this idea also useful for omap keypad driver?
>
> Plz find source code for omap keypad driver from:
> /usr/src/armlinux/linux-2.6.16/drivers/input/keyboard/omap-keypad.c
>
> Best Regards,
> Devendra
>
Yes, that driver receives creates /dev/input/event(number) to userspace.
(by calling input_allocate_device() method)
and starts listening irq's from the key presses. When it receives irq,
it checks which key was really pressed and uses
input_report_key() method for passing that information to userspace via
/dev/input/event(number) interface.
Note that in this level, you can desire which key events you send to
userspace. In my device I have for example an joypad
that sends always couple of irq's to driver and sending them directly to
userspace would mess apps like gpe-window manager.
(For me the press to right would generate "up-right" and "bottom-right"
events, and instead of passing them, I only send one event
indicating that "right" key were pressed.)
I have not send that driver to omap list because I am not sure would the
omap-keypad driver be the best location for that code.
Mika
next prev parent reply other threads:[~2006-08-19 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 13:54 How to use omap keypad driver function Devendra Kumar Madhesia
2006-08-19 0:26 ` andrzej zaborowski
2006-08-19 11:25 ` Devendra Kumar Madhesia
2006-08-19 16:14 ` lamikr [this message]
2006-08-22 12:00 ` Devendra Kumar Madhesia
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=44E738EA.2080904@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=devendra.madhesia@flextronicssoftware.com \
--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