All of the Gen3 touchpads are fixed with I2C address 0x67, so correct the
reg value description from 0x24 to 0x67.
Signed-off-by: Dudley Du
---
Documentation/devicetree/bindings/input/cypress,cyapa.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/b
On Tue, 2015-09-15 at 12:44 -0400, Donavan Lance wrote:
> Adds support for Microsoft Type Cover 3 with 0x07e2 product ID.
>
> Signed-off-by: Donavan Lance
> ---
> drivers/hid/hid-core.c | 2 ++
> drivers/hid/hid-ids.h | 1 +
> drivers/hid/hid-microsoft.c | 2 ++
> drivers/
Hi Daniel,
It is better to change form "dev_err(&data->client->dev," to " dev_err(dev,"
Thanks
duson
-Original Message-
From: Daniel Drake [mailto:dr...@endlessm.com]
Sent: Thursday, September 17, 2015 9:18 PM
To: DusonLin
Cc: Dmitry Torokhov; João Paulo Rechi Vita; linux-input@vger.ke
From: Stephen Chandler Paul
Debugging input devices, specifically laptop touchpads, can be tricky
without having the physical device handy. Here we try to remedy that
with userio. This module allows an application to connect to a character
device provided by the kernel, and emulate any serio devi
The devicetree binding for gpio-keys-polled already allows specifying
what type of events (key / rel / abs) a button generates when pressed.
But for rel / abs axis we also need to specify which value this specific
gpio represents.
One usecase is digital joysticks / direction-pads which are hooked
Add support for EV_ABS / EV_REL events to the gpio-keys-polled driver.
Signed-off-by: Hans de Goede
---
Changes in v2:
-Fix commit message to actually describe what the patch does
(fix patch squashing fail)
---
drivers/input/keyboard/gpio_keys_polled.c | 88 +++
1 fi
On Thu, Sep 17, 2015 at 11:01 AM, Daniel Martin
wrote:
> Section "Event Computation" had this:
> ...
> ABS_MT_TOOL_X := C_X
> ABS_MT_TOOL_X := C_Y
>
> Replace the second ABS_MT_TOOL_X with ABS_MT_TOOL_Y.
>
> Signed-off-by: Daniel Martin
> ---
Acked-by: Benjamin Tissoires
> Documen
On Thu, Sep 17, 2015 at 11:02 AM, Daniel Martin
wrote:
> Just to prettify the log message. Otherwise it would be .
>
> Signed-off-by: Daniel Martin
> ---
Reviewed-by: Benjamin Tissoires
> drivers/hid/hid-core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/hid/hid-core.c
Hi,
On 09/17/2015 04:00 PM, Rob Herring wrote:
On 09/17/2015 02:35 PM, Hans de Goede wrote:
Hi,
On 09/17/2015 07:00 AM, Ian Campbell wrote:
On Wed, 2015-09-16 at 15:40 +0100, Ian Campbell wrote:
The intend of the symlink was that the conversion script would copy
the target,
rather then follo
Hi! The currently upstream version of this patch actually breaks
uinput, and causes the kernel to panic when attempting to run it under
qemu using spice. Here's a backtrace from kdb:
Stack traceback for pid 656
0x8800babed480 6561 12 R 0x8800babefa80
*spice-vdagentd
On 09/17/2015 02:35 PM, Hans de Goede wrote:
> Hi,
>
> On 09/17/2015 07:00 AM, Ian Campbell wrote:
>> On Wed, 2015-09-16 at 15:40 +0100, Ian Campbell wrote:
The intend of the symlink was that the conversion script would copy
the target,
rather then follow the symlink. This sorta ass
Hi,
On 09/17/2015 07:00 AM, Ian Campbell wrote:
On Wed, 2015-09-16 at 15:40 +0100, Ian Campbell wrote:
The intend of the symlink was that the conversion script would copy the target,
rather then follow the symlink. This sorta assumes that there are will be not
symlinks under dt-bindings which l
There is an undocumented upper bound for the total number of ff effects:
FF_GAIN (= 96).
This can be found as follows:
- user: write(EV_FF, effect_id, iterations)
calls kernel: ff->playback(effect_id, ...): starts effect "effect_id"
- user: write(EV_FF, FF_GAIN, gain)
calls kernel: ff->
This is a patch-set to improve the handling of max_effects in
ff-core and uinput.
Elias Vanderstuyft (2):
Input: Document and check on implicitly defined FF_MAX_EFFECTS
Input: uinput: Sanity check on ff_effects_max and EV_FF
drivers/input/ff-core.c | 5 +
drivers/input/misc/uinput.c
Currently the user can specify a non-zero value for ff_effects_max,
without setting the EV_FF bit.
Inversely,
the user can also set ff_effects_max to zero with the EV_FF bit set,
in this case the uninitialized method ff->upload can be dereferenced,
resulting in a kernel oops.
Instead of adding a c
Just like the EVIOCSABS(abs) macro, use the more compact
_IOW(..., type) instead of _IOC(_IOC_WRITE, ..., sizeof(type))
for the EVIOCSFF macro.
Signed-off-by: Elias Vanderstuyft
---
include/uapi/linux/input.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/
On Thu, Sep 17, 2015 at 11:25 AM, Benjamin Tissoires
wrote:
> Hi Daniel,
>
> On Thu, Sep 17, 2015 at 11:06 AM, Daniel Martin
> wrote:
>> The N-trig (1b96:1B05) is an I2C device. It can be found in a
>> Microsoft Surface Pro 3. Users reported that sometimes the touschscreen
>> gets stuck during wo
Hi Daniel,
On Thu, Sep 17, 2015 at 11:06 AM, Daniel Martin
wrote:
> The N-trig (1b96:1B05) is an I2C device. It can be found in a
> Microsoft Surface Pro 3. Users reported that sometimes the touschscreen
> gets stuck during work - not responding to touches anymore.
>
> Under certain circumstances
The N-trig (1b96:1B05) is an I2C device. It can be found in a
Microsoft Surface Pro 3. Users reported that sometimes the touschscreen
gets stuck during work - not responding to touches anymore.
Under certain circumstances the touschscreen sends "ghost" reports.
Reports for contacts that have been
Section "Event Computation" had this:
...
ABS_MT_TOOL_X := C_X
ABS_MT_TOOL_X := C_Y
Replace the second ABS_MT_TOOL_X with ABS_MT_TOOL_Y.
Signed-off-by: Daniel Martin
---
Documentation/input/multi-touch-protocol.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
Just to prettify the log message. Otherwise it would be .
Signed-off-by: Daniel Martin
---
drivers/hid/hid-core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index e6fce23..2636fac 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hi
On Thu, Sep 17, 2015 at 7:29 PM, Maxime Ripard
wrote:
> Hi Yassin,
>
> On Wed, Sep 16, 2015 at 12:05:55AM +1000, yassinjaf...@gmail.com wrote:
>> From: Yassin Jaffer
>>
>> Add Keypad controller node definition to the A20 SoC.
>>
>> Signed-off-by: Yassin Jaffer
>> ---
>> arch/arm/boot/dts/sun7i-
Hi,
On Wed, Sep 16, 2015 at 7:23 PM, DusonLin wrote:
> [Duson] I think it's better to change here " dev_err(dev,"
What do you prefer? dev_warn?
Thanks
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
More majo
Hi,
On Wed, Sep 16, 2015 at 12:05:56AM +1000, yassinjaf...@gmail.com wrote:
> From: Yassin Jaffer
>
> Allwinnner SUN4i Keypad controller is used to interface a SoC
> with a matrix-typekeypad device.
> The keypad controller supports multiple row and column lines.
> A key can be placed at each int
This patch implements a HID driver for the Corsair Vengeance K90 keyboard.
It fixes the behaviour of the keys using incorrect HID usage codes and exposes
the macro playback mode and current profile to the user space through sysfs
attributes. It also adds two LED class devices controlling the "re
I have split the special functions between backlight and macro functions. This
should make it easier to test new devices. I think the macro functions will
only be reused with the K95. While backlight is more common feature, though I
have no idea it is done with other Corsair hardware.
I have ch
Hi Yassin,
On Wed, Sep 16, 2015 at 12:05:55AM +1000, yassinjaf...@gmail.com wrote:
> From: Yassin Jaffer
>
> Add Keypad controller node definition to the A20 SoC.
>
> Signed-off-by: Yassin Jaffer
> ---
> arch/arm/boot/dts/sun7i-a20.dtsi | 9 +
> 1 file changed, 9 insertions(+)
>
> di
On Wed, 2015-09-16 at 15:40 +0100, Ian Campbell wrote:
> > The intend of the symlink was that the conversion script would copy the
> > target,
> > rather then follow the symlink. This sorta assumes that there are will be
> > not
> > symlinks under dt-bindings which link to files inside dt-binding
On 14 September 2015 at 16:37, Daniel Martin wrote:
> I've retried this issue with v4.2 and it still exists.
I've got it! The patch(es) should pop up soon.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vger.kernel.org
More majordom
When wakeup attribute is set, GPIO key is supposed to wake up
the system from system sleep state, So set IRQF_NO_SUSPEND
flag to keep IRQ enabled during suspend.
Signed-off-by: Qi Zheng
Signed-off-by: Aubrey Li
Signed-off-by: Qipeng Zha
---
drivers/input/keyboard/gpio_keys.c | 2 ++
1 file cha
30 matches
Mail list logo
