From: Wolfram Sang <wsa@the-dreams.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Christian Ruppert <christian.ruppert@alitech.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Pavel Roskin <plroskin@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: designware: Do not use parameters from ACPI on Dell Inspiron 7348
Date: Sat, 17 Oct 2015 19:57:26 +0200 [thread overview]
Message-ID: <20151017175726.GB3359@katana> (raw)
In-Reply-To: <1443085614-101362-1-git-send-email-mika.westerberg@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Thu, Sep 24, 2015 at 12:06:54PM +0300, Mika Westerberg wrote:
> ACPI SSCN/FMCN methods were originally added because then the platform can
> provide the most accurate HCNT/LCNT values to the driver. However, this
> seems not to be true for Dell Inspiron 7348 where using these causes the
> touchpad to fail in boot:
>
> i2c_hid i2c-DLL0675:00: failed to retrieve report from device.
> i2c_designware INT3433:00: i2c_dw_handle_tx_abort: lost arbitration
> i2c_hid i2c-DLL0675:00: failed to retrieve report from device.
> i2c_designware INT3433:00: controller timed out
>
> The values received from ACPI are (in fast mode):
>
> HCNT: 72
> LCNT: 160
>
> this translates to following timings (input clock is 100MHz on Broadwell):
>
> tHIGH: 720 ns (spec min 600 ns)
> tLOW: 1600 ns (spec min 1300 ns)
> Bus period: 2920 ns (assuming 300 ns tf and tr)
> Bus speed: 342.5 kHz
>
> Both tHIGH and tLOW are within the I2C specification.
>
> The calculated values when ACPI parameters are not used are (in fast mode):
>
> HCNT: 87
> LCNT: 159
>
> which translates to:
>
> tHIGH: 870 ns (spec min 600 ns)
> tLOW: 1590 ns (spec min 1300 ns)
> Bus period 3060 ns (assuming 300 ns tf and tr)
> Bus speed 326.8 kHz
>
> These values are also within the I2C specification.
>
> Since both ACPI and calculated values meet the I2C specification timing
> requirements it is hard to say why the touchpad does not function properly
> with the ACPI values except that the bus speed is higher in this case (but
> still well below the max 400kHz).
>
> Solve this by adding DMI quirk to the driver that disables using ACPI
> parameters on this particulare machine.
>
> Reported-by: Pavel Roskin <plroskin@gmail.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied to for-current with Pavel's Tested-by:, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-10-17 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 9:06 [PATCH] i2c: designware: Do not use parameters from ACPI on Dell Inspiron 7348 Mika Westerberg
2015-10-15 11:40 ` Wolfram Sang
2015-10-17 16:19 ` Pavel Roskin
2015-10-17 17:57 ` Wolfram Sang [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=20151017175726.GB3359@katana \
--to=wsa@the-dreams.de \
--cc=christian.ruppert@alitech.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=plroskin@gmail.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