These are simple data acquistion boards, not HID devices and are handled
by the vmk80xx comedi driver. At least one of them (10cf:5500)
misidentifies itself as a HID in its USB interface descriptor. Ignore
all these devices.
Signed-off-by: Ian Abbott abbo...@mev.co.uk
---
Hi Simon,
On Tue, Feb 12, 2013 at 06:42:25PM -0800, Simon Glass wrote:
We now have a binding which adds two parameters to the matrix keypad DT
node. This is separate from the GPIO-driven matrix keypad binding, and
unfortunately incompatible, since that uses row-gpios/col-gpios for the
row and
Hi SImon,
On Tue, Feb 12, 2013 at 06:42:26PM -0800, Simon Glass wrote:
Use the key-matrix layer to interpret key scan information from the EC
and inject input based on the FDT-supplied key map. This driver registers
itself with the ChromeOS EC driver to perform communications.
Additional
Hi Daniel,
On Fri, Feb 01, 2013 at 04:11:44PM +0800, Daniel Kurtz wrote:
As soon as the irq is request, input event interrupts could occur that
the isr should handle. Similarly, if there are input events queued up
in the device output buffer, it will send them immediately when we
drain the
On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an i2c_client which has one of the Atmel Bootloader i2c addresses.
In this case,
On Fri, Feb 01, 2013 at 04:11:48PM +0800, Daniel Kurtz wrote:
After firmware update, the device may have a completely different object
table which corresponds to an input device with different properties.
So, destroy the old state before firmware update, and completely
reinitialize the driver
On Fri, Feb 01, 2013 at 04:28:32PM +0800, Daniel Kurtz wrote:
The input fuzz algorithm does a pretty good job filtering out small
jitter on input samples.
However, there is a subtle problem when fuzz is used with mt drivers that
also use input_mt_report_pointer_emulation() to report legacy
On Wed, Feb 13, 2013 at 1:46 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an
On Sun, Feb 10, 2013 at 12:15:40PM -0800, Benson Leung wrote:
This patch adds support for the Cypress APA Smbus Trackpad type,
which uses a modified register map that fits within the
limitations of the smbus protocol.
Devices that use this protocol include:
CYTRA-116001-00 - Samsung Series
On Fri, Feb 01, 2013 at 04:29:00PM +0800, Daniel Kurtz wrote:
Investigating the following gesture highlighted two slight implementation
errors with choosing which slots to report in which slot when multiple
contacts are present:
Action SGM AGM (MTB slot:Contact)
1. Touch
Hi Dmitry,
On Wed, Feb 13, 2013 at 11:43 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Simon,
On Tue, Feb 12, 2013 at 06:42:25PM -0800, Simon Glass wrote:
We now have a binding which adds two parameters to the matrix keypad DT
node. This is separate from the GPIO-driven matrix
Hi Dmitry,
On Wed, Feb 13, 2013 at 12:02 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi SImon,
On Tue, Feb 12, 2013 at 06:42:26PM -0800, Simon Glass wrote:
Use the key-matrix layer to interpret key scan information from the EC
and inject input based on the FDT-supplied key map. This
Use the key-matrix layer to interpret key scan information from the EC
and inject input based on the FDT-supplied key map. This driver registers
itself with the ChromeOS EC driver to perform communications.
The matrix-keypad FDT binding is used with a small addition to control
ghosting.
We now have a binding which adds two parameters to the matrix keypad DT
node. This is separate from the GPIO-driven matrix keypad binding, and
unfortunately incompatible, since that uses row-gpios/col-gpios for the
row and column counts.
So the easiest option here is to provide a function for
On Wed, 13 Feb 2013 21:08:20 -0800 Andrew de los Reyes wrote:
/**
+ * hid_device_io_start - enable HID input during probe, remove
+ *
+ * @hid - the device
+ *
+ * This should only be called during probe or remove. It will allow
+ * incoming packets to be delivered to
15 matches
Mail list logo