Hi Dmitry!
thanks for your suggestions, will include them into the next patch update.
On 05/17/2012 07:38 PM, Dmitry Torokhov wrote:
>> + of_property_read_u32(np, "keypad,num-rows", &rows);
>> + of_property_read_u32(np, "keypad,num-columns", &columns);
>> + if (!rows || rows != columns) {
>> + dev_err(dev, "rows and columns must be specified and be equal!\n");
>
> Why?
The LPC32xx key scanner hardware is always configured with a square
matrix (rows == columns). So I had the choice to force "keypad,num-rows"
== "keypad,num-columns" (as done currently) to show potential error to
the DTS/DTB provider, or ignore problems here and use
max("keypad,num-rows", "keypad,num-columns") for actual hardware setup.
(You can and will leave out unconnected keys in the keymap anyway.)
So do you think we should change my current approach here?
Thanks in advance,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
