From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, s.hauer@pengutronix.de,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH, v2] input/imx2x: generic keypad handler for i.MX SoCs
Date: Mon, 20 Apr 2009 13:08:56 +0200 [thread overview]
Message-ID: <200904201308.56564.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20090418231549.GB32346@dtor-d630.eng.vmware.com>
> I see. Then I would say that you need to supply both - kemap
> and an optional function to mangle scancode if needed.
The hardware supports an keypad with up to 8x8 keys: 256 keys. So
you want me to setup a keymap table with 256 entries in the
driver. And then either user-space or board-support code will
populate this table?
I won't need that for my board, but I can see how this makes the
driver more generally usable. So I can live with that. :-)
What I'd do is: if the keymap table entry is empty, then call the
board-specific handler function if it's defined.
next prev parent reply other threads:[~2009-04-20 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 14:40 [PATCH, v2] input/imx2x: generic keypad handler for i.MX SoCs Holger Schurig
2009-04-17 14:55 ` Holger Schurig
2009-04-17 15:47 ` Lothar Waßmann
2009-04-17 19:23 ` Holger Schurig
2009-04-18 7:51 ` Russell King - ARM Linux
2009-04-17 15:58 ` Paulius Zaleckas
2009-04-17 19:26 ` Holger Schurig
2009-04-17 16:04 ` Dmitry Torokhov
2009-04-17 19:40 ` Holger Schurig
2009-04-18 23:15 ` Dmitry Torokhov
2009-04-20 11:08 ` Holger Schurig [this message]
2009-04-18 14:27 ` Sascha Hauer
2009-06-05 9:51 ` Martin Fuzzey
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=200904201308.56564.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).