From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd: Fix release quirk for Dell models
Date: Mon, 6 Apr 2015 10:06:10 +0200 [thread overview]
Message-ID: <201504061006.10853@pali> (raw)
In-Reply-To: <20150405235343.GA5313@dtor-ws>
[-- Attachment #1: Type: Text/Plain, Size: 2319 bytes --]
On Monday 06 April 2015 01:53:43 Dmitry Torokhov wrote:
> On Mon, Apr 06, 2015 at 12:00:32AM +0200, Pali Rohár wrote:
> > On Sunday 05 April 2015 23:48:33 Dmitry Torokhov wrote:
> > > Hi Pali,
> > >
> > > On Sun, Mar 29, 2015 at 04:36:19PM +0200, Pali Rohár wrote:
> > > > This patch fixes commit 61579ba83934 ("Input: atkbd -
> > > > expand Latitude's force release quirk to other Dells").
> > > > Before that commit release quirks were called for all
> > > > Dell Latitude models. After that commit only for
> > > > Portable Dell devices. But lot of Latitude models are
> > > > Laptop or Notebook DMI devices so quirks are not
> > > > called.
> > > >
> > > > Release quirks are still needed also for new Dell
> > > > Latitude models, so this patch enables quirks for all
> > > > Portable, Laptop, Notebook and Sub-Notebook Dell
> > > > devices.
> > >
> > > Does Dell use all these types for their laptops? What
> > > models do you know that need this quirk?
> > >
> > > Thanks.
> >
> > I do not if Dell use all types, but months ago Matthew wrote
> > to include also other numbers not only 9 (Laptop) and you
> > agreed.
>
> Hmm, I tried looking back but I could not quite find the
> discussion.
>
Search for Message-ID: <20141222175632.GB18556@dtor-ws>
(this should be unique identifier for emails)
> > I do not know exact list of models which needs these quirks,
> > but before that commit (61579ba83934) it was used for all
> > Latitude models. At least I see that switches do not
> > generate release events and on older Latitude machines some
> > Fn keys do not generate them too.
>
> So the question is still: what models do need this quirk and
> what chassis type they are used.
>
My model:
$ cat /sys/class/dmi/id/chassis_type
9
$ cat /sys/class/dmi/id/sys_vendor
Dell Inc.
$ cat /sys/class/dmi/id/product_name
Latitude E6440
> Regardless, I have not accepted quirks for force_release and
> atkbd keymaps for many years now as the task to adjust both
> keymap and force_release list has been offloaded to udev.
>
> Thanks.
Ok, and what to do with kernel regressions? As before commit
61579ba83934 it worked, because quirk was called for all Latitude
(independently on chassis_type).
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-04-06 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:36 [PATCH] Input: atkbd: Fix release quirk for Dell models Pali Rohár
2015-04-04 22:48 ` Pali Rohár
2015-04-05 21:48 ` Dmitry Torokhov
2015-04-05 22:00 ` Pali Rohár
2015-04-05 23:53 ` Dmitry Torokhov
2015-04-06 8:06 ` Pali Rohár [this message]
2015-04-06 16:20 ` Dmitry Torokhov
2015-04-08 20:54 ` Pali Rohár
2015-04-09 16:57 ` Dmitry Torokhov
2015-04-09 17:00 ` Pali Rohár
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=201504061006.10853@pali \
--to=pali.rohar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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;
as well as URLs for NNTP newsgroup(s).