[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <A51B9D28-88BF-42EB-9161-8E3081B128D2@canonical.com>
Date: Wed, 27 May 2020 14:19:16 +0800
From: Kai-Heng Feng <kai.heng.feng@...onical.com>
To: Benjamin Tissoires <benjamin.tissoires@...hat.com>
Cc: Jiri Kosina <jikos@...nel.org>,
"open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] HID: multitouch: Remove MT_CLS_WIN_8_DUAL
> On May 26, 2020, at 16:43, Benjamin Tissoires <benjamin.tissoires@...hat.com> wrote:
>
> On Tue, May 26, 2020 at 10:24 AM Jiri Kosina <jikos@...nel.org> wrote:
>>
>> On Tue, 14 Apr 2020, Kai-Heng Feng wrote:
>>
>>> After commit c23e2043d5f7 ("HID: multitouch: do not filter mice nodes"),
>>> MT_CLS_WIN_8 also supports mouse nodes, hence make MT_CLS_WIN_8_DUAL
>>> redundant.
>>>
>>> Remove MT_CLS_WIN_8_DUAL accordingly.
>>
>> Benjamin, can I get your Ack on this one please?
>
> Heh, funny enough I was trying to fix
> https://bugzilla.kernel.org/show_bug.cgi?id=207235 and was pondering
> this one too.
>
> To fix #207235, I'll likely need to add a new class and quirk in
> hid-multitouch. I can't really find a generic solution for now, and we
> better have a local quirk for the 2 devices we currently have and
> backport those to stable. However, this patch will likely conflict
> (trivially), with the new quirks, so I was thinking:
> - submitting my quick and dirty quirk and mark it to stable
> - apply this one on top of it (this one really doesn't need to go to stable)
>
> How does that sound?
Sounds good. I'll resend this patch once your patch lands in the tree.
Kai-Heng
>
> Cheers,
> Benjamin
>
>>
>> Thanks,
>>
>> --
>> Jiri Kosina
>> SUSE Labs
>>
>
Powered by blists - more mailing lists