[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD6_Bostr0-k4SPO8vnz51hP41-dM0hzDyE7ewdwbq6LLJD38A@mail.gmail.com>
Date: Tue, 23 Jan 2018 13:42:45 +0100
From: Marco Martin <notmart@...il.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Pali Rohár <pali.rohar@...il.com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Bhushan Shah <bhush94@...il.com>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Mario Limonciello <mario.limonciello@...l.com>,
Mario Limonciello <mario_limonciello@...l.com>
Subject: Re: [PATCH] Support intel-vbtn based tablet mode switch
On Tue, Jan 23, 2018 at 12:46 AM, Dmitry Torokhov
<dmitry.torokhov@...il.com> wrote:
>> @@ -81,6 +86,7 @@ static void notify_handler(acpi_handle handle, u32 event, void *context)
>> return;
>> }
>> } else if (sparse_keymap_report_event(priv->input_dev, event, 1, true)) {
>> + input_sync(priv->input_dev);
>
> I do not understand why this is needed, as sparse keymap should issue
> sync for you. From sparse_keymap_report_entry():
indeed, I was testing on a 4.13 build, the sync there was pushed in
november only for 4.14, i've rebuilt it now on 4.14 and my sync is not
needed anymore
> Can be shorter:
>
> input_report_switch(priv->input_dev, SW_TABLET_MODE,
> obj->integer.value & TABLET_MODE_FLAG);
>
> You also need:
>
> input_sync(priv->input_dev);
in v3 this shorter version and doesn't report the capability if it's
the wrong type
--
Marco Martin
Powered by blists - more mailing lists