RE: [PATCH try #3] Blackfin BF54x Input Keypad controller driver

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Hennerich, Michael
Date: Thursday, October 11, 2007 - 12:18 pm

>From: Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com]
Kernel;
driver
&pdev->dev;"

Hi Dmitry,

Thanks for your excellent feedback and support.

We do a pretty similar thing like the omap keypad driver.
Our keycodes do not exceed KEY_MAX but we encode the ROW and COL into
the keycode matrix, in order simplify things in a "normal use case"? .
What we store is u32, 16-bit for the keycode and the upper for private
use. My understanding is that we then have to set input->keycodesize
also being u32.

Otherwise the generic input layer might get screwed up?!

Am I wrong here, or do I miss something?
Either this is a valid use case or I was inspired by a bad example.

Best regards,
Michael




{
omap-keypad.o
modify
by
pdata-
sizeof(unsigned
MAX_MULT) {
pdata\n");
TIME_SCALE)
TIME_SCALE) <<
pdata->rows],
pdata->cols],
input->keybit);
error);
|
bf54x_kpad-
b/include/asm-
16) |
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
RE: [PATCH try #3] Blackfin BF54x Input Keypad controller ..., Hennerich, Michael, (Thu Oct 11, 12:18 pm)
Re: [PATCH try #3] Blackfin BF54x Input Keypad controller ..., Dmitry Torokhov, (Thu Oct 11, 12:58 pm)