From: Hans de Goede <hdegoede@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Barnabás Pőcze" <pobrn@protonmail.com>
Subject: Re: Keyboard regression by intel-vbtn
Date: Tue, 29 Sep 2020 16:19:47 +0200 [thread overview]
Message-ID: <d43d3049-64d5-1904-bea4-437956375d7a@redhat.com> (raw)
In-Reply-To: <bedb9d1b-3cca-43e2-ee44-1aac0e09a605@redhat.com>
Hi,
On 9/29/20 11:21 AM, Hans de Goede wrote:
<snip>
> Since the problem of wrongly reporting SW_TABLET_MODE=1 in combination
> with libinput, leads to a non-usable system. Where as OTOH many people will
> not even notice when SW_TABLET_MODE is not being reported, I believe it
> is best to move to a dmi based allow-list approach here, as we recently
> did for SW_TABLET_MODE reporting by the asus-wmi driver. Allowing:
>
> dmi chassis-types: 8 /* Portable */, 31 /* Convertible */, 32 /* Detachable */
> and the HP Stream x360 11-p000nd which has working intel-vbtn SW_TABLET_MODE
> support combined with a chassis-type of 10 /* Notebook */.
>
> I will prepare a patch for this right away.
Quick status update on this, it is taking a bit longer then
I was hoping for since I'm trying to make sure that I get
things right this time.
Checking the dmidecode-dumps database from:
https://github.com/linuxhw/DMI
It seems that a whole ton of Dell laptop models use 8 ("Portable") as
chassis-type. Most of which are NOT 2-in-1s. So the new plan is to only
put the 31 ("Convertible") and 32 ("Detachable") chassis-types on
the whitelist. I do have 1 Dell 2-in-1, a Dell Venue 11 Pro 7130
with the Portable chassis-type and a working tablet-mode-sw
through intel-vbtn. So I will put that specific model on the
allow-list separately.
> Note this patch will effectively replace:
> "platform/x86: intel-vbtn: Fix SW_TABLET_MODE always reporting 1 on the HP Pavilion 11 x360"
> We will no longer need this workaround with the allow list and I believe
> that it would be better to drop that one.
>
> Andy can you drop that one from your review-andy branch please?
Regards,
Hans
next prev parent reply other threads:[~2020-09-29 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:48 Takashi Iwai
2020-09-29 9:21 ` Hans de Goede
2020-09-29 9:29 ` Takashi Iwai
2020-09-29 9:59 ` Barnabás Pőcze
2020-09-29 10:17 ` Hans de Goede
2020-09-29 12:27 ` Limonciello, Mario
2020-09-29 12:54 ` Hans de Goede
2020-09-29 14:25 ` Limonciello, Mario
2020-09-29 16:53 ` Andy Shevchenko
2020-09-29 20:37 ` Limonciello, Mario
2020-09-29 20:47 ` Limonciello, Mario
2020-09-30 13:28 ` Hans de Goede
2020-09-30 15:12 ` Limonciello, Mario
2020-09-30 15:36 ` Hans de Goede
2020-09-30 16:02 ` Limonciello, Mario
2020-09-29 14:19 ` Hans de Goede [this message]
2020-09-30 13:21 ` Hans de Goede
2020-09-30 13:21 ` Hans de Goede
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=d43d3049-64d5-1904-bea4-437956375d7a@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=tiwai@suse.de \
/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®