From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Related to Keypad Driver ....
Date: Sat, 18 Oct 2008 08:26:07 -0700 (PDT) [thread overview]
Message-ID: <20047836.post@talk.nabble.com> (raw)
Hi all ...
If any of you have worked on key pad driver could you please guide me how to
write the same as in the most standard form ...
I have a CPLD from Whre i have to read the key physical status (debouncing
logic in CPLD itself) on interrupt this i have to pass to the application
which ever is using keys for its operation and control ....
The concern is this ...
What could the best way of passing the virtual key status to the application
and how it is done in linux drivers ???? How should i make the API waiting
for Key event and Getting Unblocked ???? Can i make the API as a thread
waiting for signal ??? The same API application could use ... How is it done
in Standard Keyboard Drivers ???
A code snipped or Documentation would really help me ...
I am not sure what way i should proceed ...If any one implemented a Keypad
driver or can suggest your experience
Thanks in Advance ...
Misbah <><
--
View this message in context: http://www.nabble.com/Related-to-Keypad-Driver-....-tp20047836p20047836.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
reply other threads:[~2008-10-18 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20047836.post@talk.nabble.com \
--to=misbah_khan@engineer.com \
--cc=linuxppc-embedded@ozlabs.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 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).