Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <YszNfq4b6MkeoCJC@google.com>
In-Reply-To: <YszNfq4b6MkeoCJC@google.com>
From:   Angela Czubak <acz@semihalf.com>
Date:   Mon, 18 Jul 2022 10:49:10 +0200
Message-ID: <CAB4aORWRWBj8a5d=0Jy8-+xARNuStH5R1AZrvhLuG5T6_5DVDg@mail.gmail.com>
Subject: Re: [PATCH] Input: properly queue synthetic events
To:     Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc:     "open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
        Hans de Goede <hdegoede@redhat.com>,
        Peter Hutterer <peter.hutterer@who-t.net>,
        Benjamin Tissoires <benjamin.tissoires@redhat.com>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jul 12, 2022 at 3:25 AM Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> We should not be passing synthetic events (such as autorepeat events)
> out of order with the events coming from the hardware device, but rather
> add them to pending events and flush them all at once.
>
> This also fixes an issue with timestamps for key release events carrying
> stale data from the previous autorepeat event.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

Reviewed-by: Angela Czubak <acz@semihalf.com>

Regards,
Angela Czubak