From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Chris Chiu <chiu@endlessm.com>
Cc: Daniel Drake <drake@endlessm.com>,
Jian-Hong Pan <jian-hong@endlessm.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jani Nikula <jani.nikula@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Adrian Salido <salidoa@google.com>,
Jason Gerecke <killertofu@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: [BUG] i2c-hid: ELAN Touchpad does not work on ASUS X580GD
Date: Fri, 18 May 2018 13:58:02 +0300 [thread overview]
Message-ID: <9fd4cd99-5a4f-2d9e-88ba-18575e951490@linux.intel.com> (raw)
In-Reply-To: <cabb42db7aec59f0b795a16809b0ccfaeddb2679.camel@linux.intel.com>
On 05/18/2018 01:20 PM, Andy Shevchenko wrote:
> On Fri, 2018-05-18 at 11:37 +0300, Andy Shevchenko wrote:
>> On Fri, 2018-05-18 at 09:48 +0200, Hans de Goede wrote:
>>
>>
>>> Could it be the i2c input clock definition in drivers/mfd/intel-
>>> lpss-
>>> pci.c
>>> is also wrong for Apollo Lake (N3450) ? There are lots of people
>>> having
>>> various issues with i2c attached touchpads on Apollo Lake devices,
>>> this bug:
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
>>>
>>> Is sort of a collection bug for these. Various models laptops, lots
>>> of
>>> reporters. Note not sure thie is an i2c-designware issue, but it
>>> would
>>> be good to double check the input clock on Apollo Lake.
>>>
>>> I've checked the datasheet and the datasheet mentions 133MHz as
>>> "serial input clk" in the lpio_bxt_regs Registers Summary, which is
>>> also part of the LPSS, no clk is mentioned in the "Summary of
>>> DW_apb_i2c_mem_map_DW_apb_i2c_addr_block1 Registers".
>>
>> The internal datasheet we have access to mentioned in this case for
>> Broxton and Cannonlake together. So, your assumption might be quite
>> close to the truth and the issue is inherited from Broxton.
>>
>
Nope. The specification I have mention the I2C input clock in Broxton is
fixed 133 MHz but in Cannon Lake it is derived through non-SW visible
divider.
> Hans, can your reporters try the following patch? Depending on the
> result I may send it out ASAP.
>
> --- a/drivers/mfd/intel-lpss-pci.c
> +++ b/drivers/mfd/intel-lpss-pci.c
> @@ -120,7 +120,7 @@ static struct property_entry apl_i2c_properties[] =
> {
> };
>
> static const struct intel_lpss_platform_info apl_i2c_info = {
> - .clk_rate = 133000000,
> + .clk_rate = 216000000,
> .properties = apl_i2c_properties,
> };
>
Nack. The Apollo Lake HW here shows expected I2C bus clock on
oscilloscope so it is indeed clocked at 133 MHz.
--
Jarkko
next prev parent reply other threads:[~2018-05-18 10:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 6:55 [BUG] i2c-hid: ELAN Touchpad does not work on ASUS X580GD Jian-Hong Pan
2018-05-07 8:07 ` Chris Chiu
2018-05-08 14:31 ` Jarkko Nikula
2018-05-08 15:47 ` Daniel Drake
2018-05-10 12:03 ` Chris Chiu
2018-05-14 14:20 ` Jarkko Nikula
2018-05-15 3:22 ` Chris Chiu
2018-05-15 10:20 ` Jarkko Nikula
2018-05-17 7:48 ` Jarkko Nikula
2018-05-17 9:05 ` Chris Chiu
2018-05-18 7:48 ` Hans de Goede
2018-05-18 8:37 ` Andy Shevchenko
2018-05-18 10:20 ` Andy Shevchenko
2018-05-18 10:58 ` Jarkko Nikula [this message]
2018-05-18 13:09 ` Hans de Goede
2018-05-18 13:15 ` Jarkko Nikula
2018-05-18 13:26 ` Hans de Goede
2018-05-19 11:58 ` Hans de Goede
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=9fd4cd99-5a4f-2d9e-88ba-18575e951490@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=chiu@endlessm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=drake@endlessm.com \
--cc=hdegoede@redhat.com \
--cc=jani.nikula@intel.com \
--cc=jian-hong@endlessm.com \
--cc=jikos@kernel.org \
--cc=killertofu@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=salidoa@google.com \
--cc=wsa@the-dreams.de \
/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).