Commit f04d51404f51 (HID: driver for PS2/3 Buzz controllers) introduced
an input_mapping() callback, but set the return value to -1 to all devices
except the Buzz controllers. The result of this is that the Sixaxis input
device is not populated, making it useless.
Signed-off-by: Benjamin
On Wed, 24 Jul 2013, Benjamin Tissoires wrote:
Commit f04d51404f51 (HID: driver for PS2/3 Buzz controllers) introduced
an input_mapping() callback, but set the return value to -1 to all devices
except the Buzz controllers. The result of this is that the Sixaxis input
device is not populated,
Hi Henrik,
On Fri, Jul 19, 2013 at 11:04 PM, rydb...@euromail.se wrote:
Hi Benjamin,
Some multitouch screens do not like to be polled for input reports.
However, the Win8 spec says that all touches should be sent during
each report, making the initialization of reports unnecessary.
The
Hi Jiri,
It's been a long time since I told you that I was about to work on the devres
API...
So here are the first patches.
My deductions are that it is safe to run devm_* functions within the hid
subsystem.
With this, we can simplify a little the error path of some drivers. The gain
is more
HID special drivers can use safely the devres API.
Use it to remove 25 lines of code and to clean up a little the error paths.
Besides the pur kzalloc - devm_kzalloc conversions, I changed the
place of the allocation of the new name. Doing this right in
mt_input_configured() removes the kstrdup
It is safe to use devres allocation within the hid subsystem:
- the devres release is called _after_ the call to .remove(), meaning
that no freed pointers will exists while removing the device
- if a .probe() fails, devres releases all the allocated ressources
before going to the next driver:
On Wed, Jul 24, 2013 at 6:29 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
It is safe to use devres allocation within the hid subsystem:
- the devres release is called _after_ the call to .remove(), meaning
that no freed pointers will exists while removing the device
- if a
On Tue, Jun 18, 2013 at 11:51 AM, Jiri Kosina jkos...@suse.cz wrote:
On Thu, 13 Jun 2013, Benjamin Tissoires wrote:
Add device tree based support for HID over I2C devices.
Tested on an Odroid-X board with a Synaptics touchpad.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
On Wed, Jul 24, 2013 at 5:37 PM, Andy Shevchenko
andy.shevche...@gmail.com wrote:
On Wed, Jul 24, 2013 at 6:29 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
It is safe to use devres allocation within the hid subsystem:
- the devres release is called _after_ the call to .remove(),
On Wed, Jul 24, 2013 at 6:29 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
HID special drivers can use safely the devres API.
Use it to remove 25 lines of code and to clean up a little the error paths.
Besides the pur kzalloc - devm_kzalloc conversions, I changed the
Typo 'pur'
Use bitfiled instead of hardcoded values to set KBD_CTRL, use BIT macro,
remove unused defines.
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/input/keyboard/omap4-keypad.c | 25 +++--
1 files changed, 11 insertions(+),
Replace unclear hardcoded values with bit field, convert to threaded IRQ and
clear interrupts when open the keypad.
Based on top of v3.11-rc2.
Tested on OMAP4 SDP.
Illia Smyrnov (3):
Input: omap-keypad: Cleanup - use bitfiled instead of hardcoded
values
Input: omap-keypad: Convert to
Clear interrupts when open keypad.
According to TRM, the recommended way for keyboard controller
initialization is clear the interrupt-status register, then set up
certain keyboard events for generating an interrupt request and
set up expected source of wake-up event that generates a wake-up
Convert to use threaded IRQ.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Illia Smyrnov illia.smyr...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/input/keyboard/omap4-keypad.c | 29 -
1 files changed, 20 insertions(+), 9 deletions(-)
diff --git
Hi,
On Wed, Jul 24, 2013 at 06:54:53PM +0300, Illia Smyrnov wrote:
Clear interrupts when open keypad.
According to TRM, the recommended way for keyboard controller
initialization is clear the interrupt-status register, then set up
certain keyboard events for generating an interrupt request
On Wed, Jul 24, 2013 at 5:44 PM, Andy Shevchenko
andy.shevche...@gmail.com wrote:
On Wed, Jul 24, 2013 at 6:29 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
HID special drivers can use safely the devres API.
Use it to remove 25 lines of code and to clean up a little the error
It is safe to use devres allocation within the hid subsystem:
- the devres release is called _after_ the call to .remove(), meaning
that no freed pointers will exists while removing the device
- if a .probe() fails, devres releases all the allocated ressources
before going to the next driver:
Hi guys,
this is the v2 of this series.
Cheers,
Benjamin
changes since v1:
- make the exit code of probe() in hid-a4tech.c returning 0
- fix a typo in the commit message of 2/2
Benjamin Tissoires (2):
HID: trivial devm conversion for special hid drivers
HID: multitouch: devm conversion
HID special drivers can use safely the devres API.
Use it to remove 25 lines of code and to clean up a little the error paths.
Besides the basic kzalloc - devm_kzalloc conversions, I changed the
place of the allocation of the new name. Doing this right in
mt_input_configured() removes the kstrdup
On Wed, Jul 24, 2013 at 8:38 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
It is safe to use devres allocation within the hid subsystem:
- the devres release is called _after_ the call to .remove(), meaning
that no freed pointers will exists while removing the device
- if a
Provide a .remove function so that we can unregister the input device.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
drivers/input/touchscreen/egalax_ts.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/input/touchscreen/egalax_ts.c
Hi Fabio,
On Wednesday, July 24, 2013 05:46:09 PM Fabio Estevam wrote:
Provide a .remove function so that we can unregister the input device.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
drivers/input/touchscreen/egalax_ts.c | 11 +++
1 file changed, 11
I haven't heard back from anyone after making the last modifications
a week ago. If it's all good with you Rob, please ack it so that
Dmitry can pick it up on his side.
Thanks,
Mathieu.
From 37318cb3c6339747f4e96e09f07f732a395a5ae1 Mon Sep 17 00:00:00 2001
From: Mathieu J. Poirier
Sorry about the noise - device tree mailing has changed.
I haven't heard back from anyone after making the last modifications
a week ago. If it's all good with you Rob, please ack it so that
Dmitry can pick it up on his side.
Thanks,
Mathieu.
From 37318cb3c6339747f4e96e09f07f732a395a5ae1 Mon
From: Fabio Estevam fabio.este...@freescale.com
Converting to devm functions can make the code smaller and cleaner.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
drivers/input/touchscreen/max11801_ts.c | 37 -
1 file changed, 9 insertions(+), 28
Hi,
New USB input driver for eBeam devices.
Currently supported (tested) :
- Luidia eBeam classic projection and edge projection models
- Nec interactive solution NP01Wi1 NP01Wi2 accessories.
From basic usb point of view, all these devices are
indistinguishable : they have the same usb ids and
Signed-off-by: Yann Cantin yann.can...@laposte.net
---
drivers/hid/hid-core.c | 3 +++
drivers/hid/hid-ids.h | 3 +++
2 files changed, 6 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 36668d1..da5dfa0 100644
--- a/drivers/hid/hid-core.c
+++
Signed-off-by: Yann Cantin yann.can...@laposte.net
---
Documentation/ABI/testing/sysfs-driver-ebeam | 53 ++
drivers/input/misc/Kconfig | 22 +
drivers/input/misc/Makefile | 1 +
drivers/input/misc/ebeam.c | 763 +++
28 matches
Mail list logo
