All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Shadura <andrew.shadura@collabora.co.uk>
To: Jiri Kosina <jikos@kernel.org>,
	Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: Linux Input Mailing List <linux-input@vger.kernel.org>
Subject: Re: [PATCH v2] HID: report only one button for PenMount 6000 USB touchscreen controller
Date: Thu, 10 Mar 2016 17:11:40 +0100	[thread overview]
Message-ID: <56E19CBC.60107@collabora.co.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1603101710430.3656@cbobk.fhfr.pm>


[-- Attachment #1.1: Type: text/plain, Size: 2655 bytes --]

On 10/03/16 17:11, Jiri Kosina wrote:
> On Thu, 10 Mar 2016, Christian Gmeiner wrote:
> 
>> > 2016-03-10 12:46 GMT+01:00 Andrew Shadura <andrew.shadura@collabora.co.uk>:
>>> > > On 12/01/16 15:59, Andrew Shadura wrote:
>>>> > >> On 27/11/15 16:18, Christian Gmeiner wrote:
>>>>>> > >>> > 2015-11-24 13:24 GMT+01:00 Andrew Shadura <andrew.shadura@collabora.co.uk>:
>>>>>>>> > >>>> >> On 29/10/15 16:00, Andrew Shadura wrote:
>>>>>>>>>> > >>>>> >>> PenMount 6000 USB resistive touchscreen controller reports it has three
>>>>>>>>>> > >>>>> >>> buttons, while in reality it doesn't have any and doesn't support active
>>>>>>>>>> > >>>>> >>> styli, and only generates touch events.
>>>>>>>>>> > >>>>> >>>
>>>>>>>>>> > >>>>> >>> In penmount_input_mapping(), map only the first button (with code 0),
>>>>>>>>>> > >>>>> >>> ignore the rest.
>>>>>>>>>> > >>>>> >>>
>>>>>>>>>> > >>>>> >>> Signed-off-by: Andrew Shadura <andrew.shadura@collabora.co.uk>
>>>>>>>> > >>>> >>
>>>>>>>> > >>>> >> Any news on this patch? It'd be cool if it could be merged.
>>>>>> > >>> >
>>>>>> > >>> > I try to get access to the hardware and will test it.
>>>> > >> Christian, have you had a chance to test the patch?
>>> > >
>>> > > Ping, once again. Any progress on this?
>> > 
>> > Sorry for the long delay. I have applied your patch and the touch
>> > works as expected.
>> > 
>> > No device specified, trying to scan all of /dev/input/event*
>> > Available devices:
>> > /dev/input/event0:      Power Button
>> > /dev/input/event1:      Lid Switch
>> > /dev/input/event2:      Sleep Button
>> > /dev/input/event3:      Video Bus
>> > /dev/input/event4:      DIALOGUE INC PenMount USB
>> > Select the device event number [0-4]: 4
>> > Input driver version is 1.0.1
>> > Input device ID: bus 0x3 vendor 0x14e1 product 0x6000 version 0x101
>> > Input device name: "DIALOGUE INC PenMount USB"
>> > Supported events:
>> >   Event type 0 (EV_SYN)
>> >   Event type 1 (EV_KEY)
>> >     Event code 330 (BTN_TOUCH)
>> >   Event type 3 (EV_ABS)
>> >     Event code 0 (ABS_X)
>> >       Value      0
>> >       Min        0
>> >       Max     1023
>> >     Event code 1 (ABS_Y)
>> >       Value      0
>> >       Min        0
>> >       Max     1023
>> >   Event type 4 (EV_MSC)
>> >     Event code 4 (MSC_SCAN)
>> > Properties:
>> > Testing ... (interrupt to exit)
>> > 
>> > Tested-by: Christian Gmeiner <c.gmeiner@bachmann.info
> Could you guys please bounce / resend the patch to me? I don't seem to 
> see it in my inbox.

It's in the patchwork here:

https://patchwork.kernel.org/patch/7519541/

-- 
Cheers,
  Andrew


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-10 16:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 15:09 [PATCH v2] HID: report only one button for PenMount 6000 USB touchscreen controller Andrew Shadura
2015-11-24 12:24 ` Andrew Shadura
2015-11-27 15:18   ` Christian Gmeiner
2016-01-12 14:59     ` Andrew Shadura
2016-03-10 11:46       ` Andrew Shadura
2016-03-10 13:47         ` Christian Gmeiner
2016-03-10 16:11           ` Jiri Kosina
2016-03-10 16:11             ` Andrew Shadura [this message]
2016-03-10 16:18               ` Jiri Kosina
2016-03-14 13:47                 ` Andrew Shadura
  -- strict thread matches above, loose matches on Subject: below --
2015-11-19 15:04 Andrew Shadura

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E19CBC.60107@collabora.co.uk \
    --to=andrew.shadura@collabora.co.uk \
    --cc=christian.gmeiner@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.