Solution: N810 keyboard regression

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Found the problem with the 2.6.29 N810 keyboard regression in this commit:
	commit c83702a764c3099df50f215b8e79e07344e34a1a
	Author: Felipe Balbi <felipe.balbi@xxxxxxxxx>
	Date:   Thu Feb 19 12:29:40 2009 +0000
	    input: lm8323: get rid of useless debug macro
	    we can use dev_vdbg() which is only true when VERBOSE is enabled.

Part of this commit removed the "default" values for platform parameters, but 
set the N810's size_y to 8 instead of the earlier default of 12. Changing this 
to 12 (patch to follow) fixes the keyboard regression. Note, the total keys on 
the N810 is in fact under 64, so 8x8 seems correct. Not sure why it doesn't 
work like that in practise. I did notice a curious line in the driver that 
might (or might not) be related/wrong...

drivers/input/keyboard/lm8323.c line 353:
	int keysize = (lm->size_x << 4) | lm->size_y;

Shouldn't this be lm->size_x * lm->size_y?

Luke
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux