From: Heorhi Valakhanovich <valahanovich@tut.by>
To: Jiri Kosina <jikos@kernel.org>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
dmitry.torokhov@gmail.com, wbauer@tmo.at,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v2] HID: input: fix a4tech horizontal wheel custom usage
Date: Sun, 25 Aug 2019 23:50:23 +0300 [thread overview]
Message-ID: <b72a0562-262e-5373-e2a2-5c1b1e5ca37a@tut.by> (raw)
In-Reply-To: <nycvar.YFH.7.76.1908051437490.5899@cbobk.fhfr.pm>
On 8/5/19 3:38 PM, Jiri Kosina wrote:
> On Thu, 1 Aug 2019, Nicolas Saenz Julienne wrote:
>
>>> Some a4tech mice use the 'GenericDesktop.00b8' usage to inform whether
>>> the previous wheel report was horizontal or vertical. Before
>>> c01908a14bf73 ("HID: input: add mapping for "Toggle Display" key") this
>>> usage was being mapped to 'Relative.Misc'. After the patch it's simply
>>> ignored (usage->type == 0 & usage->code == 0). Which ultimately makes
>>> hid-a4tech ignore the WHEEL/HWHEEL selection event, as it has no
>>> usage->type.
>>>
>>> We shouldn't rely on a mapping for that usage as it's nonstandard and
>>> doesn't really map to an input event. So we bypass the mapping and make
>>> sure the custom event handling properly handles both reports.
>>>
>>> Fixes: c01908a14bf73 ("HID: input: add mapping for "Toggle Display" key")
>>> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
>>> ---
>>
>> It would be nice for this patch not to get lost. It fixes issues both repoted
>> on opensuse and fedora.
>
> Sorry for the delay. I've now queued the patch. Thanks for fixing this,
>
Any plans to apply this patch on top of 5.2.* and 5.1.* ?
prev parent reply other threads:[~2019-08-25 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:13 Nicolas Saenz Julienne
2019-06-11 14:42 ` Benjamin Tissoires
2019-06-13 11:48 ` Wolfgang Bauer
2019-06-14 13:36 ` Benjamin Tissoires
2019-06-14 14:25 ` Nicolas Saenz Julienne
2019-07-05 10:28 ` Nicolas Saenz Julienne
2019-07-18 15:46 ` Jeremy Cline
2019-06-14 12:00 ` Wolfgang Bauer
2019-08-01 10:56 ` Nicolas Saenz Julienne
2019-08-05 12:38 ` Jiri Kosina
2019-08-25 20:50 ` Heorhi Valakhanovich [this message]
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=b72a0562-262e-5373-e2a2-5c1b1e5ca37a@tut.by \
--to=valahanovich@tut.by \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=wbauer@tmo.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®