change log [v10->v9]:
1, change pr_err to dev_err.
2, add device_init_wakeup(,0) when device removes.
3, add ack by Dmitry.
change log [v9->v8]:
1, remove devm_xxx api.
2, fix the potential oops issue.
3, use __set_bit to set key_bit.
change log [v8->v7]:
1, remove file name in comments.
2, add e
add onkey support to MARVELL 88PM80X PMIC.
Signed-off-by: Qiao Zhou
Acked-by: Dmitry Torokhov
---
drivers/input/misc/88pm80x_onkey.c | 168
drivers/input/misc/Kconfig | 10 ++
drivers/input/misc/Makefile|1 +
3 files changed, 179 inser
On 13.07.2012 09:01, Dmitry Torokhov wrote:
> On Wed, May 02, 2012 at 09:36:51PM -0700, Dmitry Torokhov wrote:
>> Hi Sven,
>>
>> On Sat, Apr 07, 2012 at 08:38:33PM +0200, Sven Neumann wrote:
>>> Hi,
>>>
>>> On 07.04.12 09:02, Dmitry Torokhov wrote:
On Fri, Apr 06, 2012 at 10:40:07PM -0700, Olo
hid-picolcd and hid-wiimote do not allow any of hidinput, hiddev or hidraw
to claim the device but still want to remain on the bus. Hence, if a
driver uses the raw_event callback but no listener claimed the device, we
still leave it on the bus as the driver probably handles everything by
itself.
U
Hi David,
> hid-picolcd and hid-wiimote do not allow any of hidinput, hiddev or hidraw
> to claim the device but still want to remain on the bus. Hence, if a
> driver uses the raw_event callback but no listener claimed the device, we
> still leave it on the bus as the driver probably handles every
The profile sensor clickpad in a Cr-48 Chromebook does a reasonable job of
tracking individual fingers. This tracking isn't perfect, but, experiments
show that it works better than just passing "semi-mt" data to userspace,
and making userspace try to deduce where the fingers are given a bounding bo
