linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Benjamin Tissoires <btissoir@redhat.com>,
	Peter Hutterer <peter.hutterer@redhat.com>,
	linux-input@vger.kernel.org, stable@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH v3] synaptics: Add min/max quirk for ThinkPad T431s, L440, L540, S1 Yoga and X1
Date: Sat, 19 Apr 2014 22:32:29 -0700	[thread overview]
Message-ID: <20140420053229.GC12454@core.coreip.homeip.net> (raw)
In-Reply-To: <534FF8E6.7060305@redhat.com>

On Thu, Apr 17, 2014 at 05:53:10PM +0200, Hans de Goede wrote:
> Hi,
> 
> On 04/17/2014 05:35 PM, Dmitry Torokhov wrote:
> > Hi Hans,
> > 
> > On Thu, Apr 17, 2014 at 01:41:43PM +0200, Hans de Goede wrote:
> >> We expect that all the Haswell series will need such quirks, sigh.
> > 
> > Given this statement do we really want this to be handled in kernel?
> 
> I know this answer won't make you happy, but short term: Yes, we are
> getting many many bugreports about this, ie:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1060885
> https://bugzilla.redhat.com/show_bug.cgi?id=1068716
> https://bugzilla.redhat.com/show_bug.cgi?id=1085582
> https://bugzilla.redhat.com/show_bug.cgi?id=1085697
> https://bugzilla.redhat.com/show_bug.cgi?id=1086227
> 
> And by extending the *already present* quirk table we can get this
> issue resolved quickly, and also resolve it for people running
> older kernels through the various stable series.
> 
> > Maybe we simply want udev to fix up the limits with EVIOSABS(),
> 
> Ah, I did not know that it is possible to fixup the min/max values
> from user space, that is good to know.
> 
> > similarly to how we adjust keymaps for laptops?
> 
> We're currently looking into various ways to make this less painful,
> specifically for most laptops the problem seems to be the min value
> and not the max value. And the troublesome min value is the synaptics
> driver default, not the one we get from the firmware. The problem is
> we never ask the firmware because even though it has the "I can report
> min values" capability bit, its "maximum understood request" number
> is too low, so one of our 2 checks for getting the min value is
> failing. If we remove that check some models do give us a proper
> range (but not all, ie the T440s is still wrong).
> 
> We're currently trying to figure out if it will be safe for all models
> to remove the "maximum understood request" number check. That should ie
> remove the quirk for the x240 and possible others.
> 
> An other option to make this better is to switch the quirks to using
> pnp-ids, ie the L440 and L540 share the same pnp-id. Once you've
> merged the firmware_id patches I can take a shot at simplifying the
> quirk table that way. Downside is that we then probably need to
> put the firmware_id patches in the various stable kernels.
> 
> Note that even if we end up moving this to userspace, then we still
> need the firmware_id, because I believe any userspace solution should
> be using pnp-ids too.
> 
> TL;DR: It is complicated and for now we would like to continue with
> the quirks as we've done sofar. We are aware that this is undesirable
> from a maintenance pov and are looking into making this better.

OK, fair enough. I applied the patch.

Thanks.

-- 
Dmitry

      reply	other threads:[~2014-04-20  5:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 11:41 [PATCH v3 0/1] synaptics: Add min/max quirk for ThinkPad T431s, L440, L540, Yoga and X1 Hans de Goede
2014-04-17 11:41 ` [PATCH v3] synaptics: Add min/max quirk for ThinkPad T431s, L440, L540, S1 " Hans de Goede
2014-04-17 15:35   ` Dmitry Torokhov
2014-04-17 15:53     ` Hans de Goede
2014-04-20  5:32       ` Dmitry Torokhov [this message]

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=20140420053229.GC12454@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=btissoir@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=peter.hutterer@redhat.com \
    --cc=stable@vger.kernel.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).