linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.
Date: Sat, 11 Apr 2015 01:14:45 +0200	[thread overview]
Message-ID: <201504110114.45676@pali> (raw)
In-Reply-To: <55285797.1080303@dell.com>

[-- Attachment #1: Type: Text/Plain, Size: 2504 bytes --]

On Saturday 11 April 2015 01:07:03 Mario Limonciello wrote:
> On 04/10/2015 05:39 PM, Pali Rohár wrote:
> > On Wednesday 25 February 2015 21:45:22 Pali Rohár wrote:
> > Hello Mario,
> > have you patched synaptics driver with some resetafter
> > parameter? And have some team in dell found reason for
> > invalid packets?
> 
> Hi Pali,
> 
> The reason was found for the invalid packets in PS2 mode, but
> I can't go into the details about it publicly.
> 
> I think it's better to not bother including my proposed
> solution, however.  The vector of users in PS2 mode should be
> very small now. Here's why:
> With no kernel command line options applied the touchpad will
> run in I2C mode with the current kernel.  The only reason
> that users were being exposed to the PS2 mode was if they ran
> with the kernel command line option acpi_osi="!Windows 2013".
>  This was required with BIOS A01 due to the problem with I2S
> audio.  This I2S audio problem has been resolved for BIOS A02
> and BIOS A03.  With no options applied on the kernel command
> line the system will run in I2C touchpad and HDA audio. All
> new machines will be coming with A03 or later.  Users with
> earlier versions have been advised to upgrade to fix this
> among other issues.
> 
> The HDA audio will work correctly for output with 4.0.  It
> will work properly for input when these two patches are
> applied (which will land in 4.1)
> 
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/c
> ommit/?h=for-next&id=e1e62b98ebddc3234f3259019d3236f66fc667f8
> 
> and
> 
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/c
> ommit/?h=for-next&id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec
> 
> 
> If the patch to disambiguate the value of _REV() lands in 4.1
> the audio will begin to operate fully in I2S mode and the
> necessary support will be included in 4.1 as well.
> 
> So with all those factors I feel that it's a very low risk
> that users will end up in PS2 mode with the current
> development focus kernels.
> 
> Thanks,

I could see problem with using older kernels which are in more 
stable or LTS distribution versions...

But it is nice that problems are fixes for future 4.0/4.1 
versions.

And if you located reason for invalid packets in PS/2 mode, will 
you fix it in some new bios versions?

Can you comment if this is also same problem with invalid packets 
on E6440/E7440 machines?

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-04-10 23:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  1:43 [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode Mario Limonciello
2015-02-19 17:16 ` Dmitry Torokhov
2015-02-19 18:16   ` Mario Limonciello
2015-02-20 18:47     ` Dmitry Torokhov
2015-02-20 19:24       ` Pali Rohár
2015-02-20 19:56         ` Mario Limonciello
2015-02-20 20:41           ` Pali Rohár
2015-02-20 21:21             ` Mario Limonciello
2015-02-20 21:31               ` Benjamin Tissoires
2015-02-20 21:40                 ` Mario Limonciello
2015-02-20 21:46                   ` Pali Rohár
2015-02-20 21:54                     ` Mario Limonciello
2015-02-22 16:55               ` Pali Rohár
2015-02-23 23:31                 ` Mario Limonciello
2015-02-24  0:01                   ` Pali Rohár
2015-02-25 18:16                     ` [SUSPECT SPAM] " Mario Limonciello
2015-02-24  0:51                 ` Dmitry Torokhov
2015-02-25 18:26                   ` Mario Limonciello
2015-02-25 18:48             ` Mario Limonciello
2015-02-25 20:45               ` Pali Rohár
2015-03-14 19:17                 ` Benjamin Tissoires
2015-03-16 14:29                   ` Mario Limonciello
2015-03-16 14:40                     ` Benjamin Tissoires
2015-03-16 17:10                     ` Jason Ekstrand
2015-03-16 18:50                       ` Mario Limonciello
2015-03-16 20:42                         ` Jason Ekstrand
2015-03-16 20:50                           ` Mario Limonciello
2015-03-16 20:57                             ` Jason Ekstrand
2015-03-16 21:07                               ` Benjamin Tissoires
2015-03-17  0:45                                 ` Mario Limonciello
2015-04-10 22:39                 ` Pali Rohár
2015-04-10 23:07                   ` Mario Limonciello
2015-04-10 23:14                     ` Pali Rohár [this message]
2015-04-10 23:32                       ` Mario Limonciello
2015-04-11  2:19                         ` Ben Gamari
2015-04-13 18:55                           ` Mario Limonciello
2015-03-21 17:21           ` Ben Gamari

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=201504110114.45676@pali \
    --to=pali.rohar@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario_limonciello@dell.com \
    /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).