DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns;
  h=X-LoopCount0:X-IronPort-AV:Message-ID:Date:From:
   Organization:User-Agent:MIME-Version:To:CC:Subject:
   References:In-Reply-To:Content-Type:
   Content-Transfer-Encoding;
  b=qwa9IZlTiAfWLaeAObeQ3eRkRLDkk8Dynax7ocvLJRGZ0Zs+m9sV3LcJ
   rdimI7EScz1lgz2k6w/fS4PAcZaGLscfRxWMuaBipUKbcUruoFUYst4ha
   i6YUcdG8IeI2jQjpKi4u/RBSyjMcjZYQE+t3qeUCw9IEzgovgm3FREc/9
   g=;
Message-ID: <54E62893.1060806@dell.com>
Date: Thu, 19 Feb 2015 12:16:51 -0600
From: Mario Limonciello <mario_limonciello@dell.com>
Organization: Dell Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Dmitry Torokhov <dmitry.torokhov@gmail.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.
References: <1424310180-2512-1-git-send-email-mario_limonciello@dell.com> <20150219171639.GB11113@dtor-glaptop>
In-Reply-To: <20150219171639.GB11113@dtor-glaptop>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1381
Lines: 21

Hi Dmitry,

On 02/19/2015 11:16 AM, Dmitry Torokhov wrote:
>
> What kind of glitch is this? Is there a certain pattern to it? Even if we do
> not reset the mouse the logs will be full of error messages.
>
> Thanks.
>
 From waveform capture data leaving the touchpad is valid, but when it is resent through the EC it's getting corrupted.  This isn't exclusive to Linux setting it up wrong or anything, it also happens on Windows.  On Windows 7 the touchpad driver does not issue a reset from the bad data however.

The glitch is more prevalent as the machine is turned on but seems to go away after it's been running a while.  We currently don't believe it to be a problem with the EC firmware, but we are still exploring other firmware based solutions.

Yes, the logs do fill up with error messages about the bad data within the first few minutes of usage.  In my opinion not freezing but getting errors in the log is better than freezing and getting errors in the log, so we're at least trying to provide a workaround for the problem.  If we come up with a firmware based solution I'd be happy to adjust or remove this later.

Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/