gmane.linux.kernel.input

Re: Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4

Jiri Kosina — 2013-06-19T21:54:51


Thanks. I am applying this with Jan's Tested-by: (and I am also extending 
the comnent preceeding the condition to better explain this case).

Re: Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4

Jan Kandziora — 2013-06-19T16:42:51

Am 19.06.2013 17:56, schrieb Benjamin Tissoires:
It works. Many thanks for making a patch that quick.

Kind regards

Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4

Benjamin Tissoires — 2013-06-19T15:56:56

Hi Jan,

On 06/19/2013 11:23 AM, Jan Kandziora wrote:

Thanks for the logs. The problem comes from a commit introduced in 3.3 which discards the BTN_LEFT information.

If possible, can you apply and test the following patch?

Cheers,
Benjamin

From: Benjamin Tissoires <benjamin.tissoires< at >redhat.com>
Date: Wed, 19 Jun 2013 17:49:05 +0200
Subject: [PATCH] HID: input: fix false positive out of range values

Commit 6da7066906e977d42104a859c490f5f9a300488c introduced in 3.3
"HID: ignore absolute values which don't fit between logical min and max"
prevents some Posiflex touch screen to work because they do not provide
logical min and max for their buttons.
Thus, logical min and max are at 0, discarding the buttons events, and
preventing the device to report appropriate X Y.

Adding a check on "min < max" solves the problem.

Reported-by: Jan Kandziora <jjj< at >gmx.de>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires< at >redhat.com>
---
 drivers/hid/hid-input.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drive

Re: [PATCH V3 5/5] input: pxa27x-keypad: add device tree support

Gerhard Sittig — 2013-06-19T11:13:41

Actually there is, but under a different (more user friendly)
name:  See the 'debounce-delay-ms' property in
Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
which gets referenced in the matrix_keypad_parse_dt() routine in
the drivers/input/keyboard/matrix_keypad.c source file.  Ah, your
last sentence mentions that fact.

But when you introduce DT support into an existing driver which
previously used platform data, then there is no problem with
backwards compatibility in .dts files.  So I suggest to go with
the "debounce-delay-ms" name since it better reflects to the .dts
author (hardware engineer) which unit the number is supposed to
be specified in.


Note that I've recently worked on extending the matrix keypad
input driver (doc improvements, software polling, binary encoded
column selection), but haven't submitted the patch series yet
since it's perfectly operational on the target which motivated
the extension but wasn't tested yet on any other platform or
matrix setup -- I currently lack

Re: [PATCH V3 5/5] input: pxa27x-keypad: add device tree support

Arnd Bergmann — 2013-06-19T09:25:26

I'd suggest using "debounce-interval" as in gpio-keys then, since that
is the most generic driver.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH V3 5/5] input: pxa27x-keypad: add device tree support

Chao Xie — 2013-06-19T08:38:38

I searched at drivers/input and Documents.
Two drivers use "debounce-interval", gpio-keys.c and stmpe-keypad.c.
They describe the meanings of "debounce-interval" at its own document file.
Some other drivers uses "xxx,debounce-delay-ms" or "debounce-delay-ms"
So it seems that there is no generic prop name for this debounce interval.

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

Re: [PATCH V3 5/5] input: pxa27x-keypad: add device tree support

Marek Vasut — 2013-06-19T08:22:51

Dear Chao Xie,


Is there no generic prop name for this debounce interval?

Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4

Benjamin Tissoires — 2013-06-19T07:50:19

Hi Jan,

On Wed, Jun 19, 2013 at 9:12 AM, Jan Kandziora <jjj< at >gmx.de> wrote:

If your device is handled through hid-generic, it should be easy to
debug it remotely.


Ok, I will need at least the dmesg log and the output of hid-recorder
[1] if your device is handled through hid-generic.
Hid-replay will then allow me to virtually plug your device on my
laptop so that I can replay and find out why the btn_left events are
not emitted anymore.

Cheers,
Benjamin

[1] http://bentiss.github.io/hid-replay-docs/

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

Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4

Jan Kandziora — 2013-06-19T07:12:05

Hello,

I have a Posiflex 7215 POS system which has a USB touchscreen controller
onboard. I've done a kernel update from 2.6.35.4 to 3.9.4 and the touch
stopped working correctly. I tried with the generic usb hid driver, the
usbtouchscreen driver doesn't support this usb id. Evtest says:


# evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xd3a product 0xa000 version 0x110
Input device name: "Posiflex Inc. USB TOUCH V390"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value   2184
      Min        0
      Max     4095
    Event code 1 (Y)
      Value   3801
      Min        0
      Max     4095
  Event type 4 (Misc)
    Event code 4 (ScanCode)
Testing ... (interrupt to exit)

Event: time 1371798299.337455, type 3 (Absolute), code 0 (X), value 1596
Event: time 1371798299.337455, type 3 (Absolute), code 1 (Y), value 1

Re: [PATCH 3/3] Input: tps6507x-ts - convert to polled input device infrastructure

Dmitry Torokhov — 2013-06-19T06:17:32

Linux-next should work, I do not have anything else for this driver
pending in my queue.

Thanks.

Re: [PATCH] Input: Added hovering capability

Dmitry Torokhov — 2013-06-19T06:13:54

Applied, thanks.

Re: [PATCH v2 1/2] input: document gamepad API and add extra keycodes

Jiri Kosina — 2013-06-18T23:30:43


I definitely need to have Dmitry's Ack for this. If he's OK with 1/2, I am 
fine with 2/2 patch for wiimote and will happily take it through my tree.

Thanks.

Re: [PATCH V3 3/5] arm: pxa: use matrix_keymap for all boards

Arnd Bergmann — 2013-06-18T14:02:16

Acked-by: Arnd Bergmann <arnd< at >arndb.de>

Thanks for the quick update.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] input: stmpe: Fix the touchscreen interrupt handling

Marek Vasut — 2013-06-18T12:01:13

Hi,


Absoluty, the feedback from the ST guys is completely imperative in this case.

Thank you!

Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] HID: i2c-hid: add DT bindings

Jiri Kosina — 2013-06-18T09:51:38


DT folks, any objections to this, please?

If not, I'd like to apply this for 3.11 into my tree.

Thanks.

Re: [PATCH] HID: roccat: check cdev_add return values

Jiri Kosina — 2013-06-18T09:01:38


Applied, thanks.

Re: [PATCH] input: stmpe: Fix the touchscreen interrupt handling

Samuel Ortiz — 2013-06-18T08:50:36

Hi Marek,

On Fri, May 17, 2013 at 01:25:11AM +0200, Marek Vasut wrote:
I am fine as long as we get feedback from Dmitry and the ST folks about
it.

Cheers,
Samuel.

Re: [PATCH] input: cros_ec_keyb_clear_keyboard() depends on CONFIG_PM_SLEEP

Geert Uytterhoeven — 2013-06-18T08:39:10

FWIW, I also have it in my exotic-arch-fixes branch, now destined for 3.11.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert< at >linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] input/joystick: Fix for xpad driver support of "Mad Catz Street Fighter IV FightPad" controllers

Shawn — 2013-06-18T04:38:33

From: shawn joseph <jms.576< at >gmail.com>

Added MAP_TRIGGERS_TO_BUTTONS for Mad Catz Street Fighter IV FightPad
device. This controller model was already supported by the xpad
driver, but none of the buttons work correctly without this change.
Tested on kernel version 3.9.5.
Signed-off-by: shawn joseph <jms.576< at >gmail.com>
---
--- linux-3.9.5/drivers/input/
joystick/xpad.c.orig      2013-06-16 15:09:47.974170141 -0400
+++ linux-3.9.5/drivers/input/joystick/xpad.c   2013-06-16
15:10:24.070611282 -0400
< at >< at > -137,7 +137,7 < at >< at > static const struct xpad_device {
        { 0x0738, 0x4540, "Mad Catz Beat Pad", MAP_DPAD_TO_BUTTONS,
XTYPE_XBOX },
        { 0x0738, 0x4556, "Mad Catz Lynx Wireless Controller", 0, XTYPE_XBOX },
        { 0x0738, 0x4716, "Mad Catz Wired Xbox 360 Controller", 0,
XTYPE_XBOX360 },
-       { 0x0738, 0x4728, "Mad Catz Street Fighter IV FightPad",
XTYPE_XBOX360 },
+       { 0x0738, 0x4728, "Mad Catz Street Fighter IV FightPad",
MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOX360 },
        { 0x0738, 0x4738, "Mad

[PATCH V3 2/5] arm: mmp: use matrix_keymap for all boards

Chao Xie — 2013-06-18T03:56:15

Compile passed for the configuration

pxa168_defconfig
  aspenite.c(MACH_ASPENITE), teton_bgs.c(MACH_TENTON_BGA)

Signed-off-by: Chao Xie <chao.xie< at >marvell.com>
---
 arch/arm/mach-mmp/aspenite.c  |   10 +++++++---
 arch/arm/mach-mmp/teton_bga.c |   10 +++++++---
 2 files changed, 14 insertions(+), 6 deletions(-)

diff --git a/arch/arm/mach-mmp/aspenite.c b/arch/arm/mach-mmp/aspenite.c
index 9f64d56..1e23346 100644
--- a/arch/arm/mach-mmp/aspenite.c
+++ b/arch/arm/mach-mmp/aspenite.c
< at >< at > -205,7 +205,7 < at >< at > struct pxa168fb_mach_info aspenite_lcd_info = {
 .invert_pixclock= 0,
 };
 
-static unsigned int aspenite_matrix_key_map[] = {
+static const unsigned int aspenite_matrix_key_map[] = {
 KEY(0, 6, KEY_UP),/* SW 4 */
 KEY(0, 7, KEY_DOWN),/* SW 5 */
 KEY(1, 6, KEY_LEFT),/* SW 6 */
< at >< at > -214,11 +214,15 < at >< at > static unsigned int aspenite_matrix_key_map[] = {
 KEY(4, 7, KEY_ESC),/* SW 9 */
 };
 
+static struct matrix_keymap_data aspenite_matrix_keymap_data = {
+.keymap= aspenite_matrix_key_map,
+.keymap_siz

[PATCH V3 0/5] input: pxa27x-keypad: enhancement and device tree support

Chao Xie — 2013-06-18T03:56:13

The patches include 2 parts
1. use matrix_keypad for matrix keyes support
2. add device tree support for pxa27x-keypad

V2->V1:
Do not copy the members from pdata. For device tree support,
directly allocate the pdata structure.

V3->V2
add matrix_keypad changes for all boards using pxa27x-keypad
under mach-pxa.
The patch "arm: pxa: use matrix_keymap for all boards" is new.
The patch "arm: mmp: use matrix_keymap for all boards" merges
previous changes for aspenite and teton_bga.
All other patches are not modified.

Chao Xie (5):
  input: pxa27x-keypad: use matrix_keymap for matrix keyes
  arm: mmp: use matrix_keymap for all boards
  arm: pxa: use matrix_keymap for all boards
  input: pxa27x-keypad: remove the unused members at platform data
  input: pxa27x-keypad: add device tree support

 .../devicetree/bindings/input/pxa27x-keypad.txt    |   60 +++++
 arch/arm/mach-mmp/aspenite.c                       |   10 +-
 arch/arm/mach-mmp/teton_bga.c                      |   10 +-
 arch/arm/mach-pxa/em-x270.c