Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4497240imm; Fri, 18 May 2018 06:10:18 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrUb7iiaaepGmqmTqBrpYv7HpAtDpjbM+D1aylnKF3Rjdeu/rZWldr8JhMa+w+g6//9weJd X-Received: by 2002:a63:6807:: with SMTP id d7-v6mr7493657pgc.332.1526649018206; Fri, 18 May 2018 06:10:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526649018; cv=none; d=google.com; s=arc-20160816; b=ShBAbbX08hWVswOFYtPIg1+B3sz7pfl9HEOnnk8h/z6ROrePVJ66XW9bimbKHXR86j eY35GomWxe1pl3h5KmWfr643kOAWhG8lqzRKU1rgVZKZgoBMsTTjo775v2/jZCvLLaIv ffThJfE32KgWVOalcB6PfqjktxkWfjJlRQzmOU12iBAQ4NP1ytzA4nH/fuaJBsFvhQfC /6NEwnhN3gZ8FF2BFgT9HROI0H1fwh05IgaLWOh0d6N1bDuPG3Aic1G5FaVtNj7j0+U4 +lquUvUg+hisgMJoQcNTQHqowvUifzmuEVChybYEj7JhW2S/o2TjMODD44eGRAwuCZv6 X+Vg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=TNE038OFCcAl11akgtZzn4gTRb5wFZNO1lxio2KYGUc=; b=CV0DLQcZyiadu+NcC+GC6RFwYTurPQGVWOvA7zfC5qT+rvcuQ0zjfK+zDnglNLPgvw AKTzrA/8r4TXvgVGydBIVjKEHQ4B9YeTzsTrzKVzP+I2NKZ+Y8z3QAsrkyXtHq70TLs5 vrrNpDzWg3Ms+pzIE79EIQhymDRBrvWmDo/h2Pd+foCuMZa+aPQleu8OdQJSwWtGHX8s 5/kQXG9lE9qvXgxqAndfiwM+tyHZl4w1anP7aAx9gnFvmHqR1XlPROg/o8Cd7b7yOc8Q 2jXGMJAJuNGODrEHhv/oq1Eve4jS3Y+6pEwW8Xjx945g7MQDPfvcJYlLOmljlJKbaAMC 18Tg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id az8-v6si7523628plb.347.2018.05.18.06.10.04; Fri, 18 May 2018 06:10:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752503AbeERNJf (ORCPT + 99 others); Fri, 18 May 2018 09:09:35 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:39979 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752243AbeERNJc (ORCPT ); Fri, 18 May 2018 09:09:32 -0400 Received: by mail-wm0-f68.google.com with SMTP id j5-v6so15072003wme.5 for ; Fri, 18 May 2018 06:09:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TNE038OFCcAl11akgtZzn4gTRb5wFZNO1lxio2KYGUc=; b=VkB4jy70X5zylWMv6Ef/FKStereCDjod9coCP1gUNDKecXKPwOKvOGFJopsVmVDUnN TL2D8WcRvjiD8wK1BlrmzTmDW+FzNJzkLhTvBM/YPDzF1TPTe56HtMGMxxwwcTszxZZE teuB6nx+BuoevAG8FlJ0wArQCF6tcfhBpuLFUH2WMefS4tqahbkSia+gGAkG7H5JjVLt SjbN44MtrkyS7K8319SszOxOroY7xNHkDx0oWD0C0AJRDgWaGzsyqo9xVnfYlxE4YBq+ 0p5cmW23SzxMy5SK41BqfTtdul83gLLjzJzafGy+hTN+l657NUekUN/gSZUtT7VA/Ks5 rW0w== X-Gm-Message-State: ALKqPwfiUfXxbQA359EeN2A9d29sJcQ7lcIvrojaG4Jh47IdXgC8JPWf WKGDDZXvNtiDgINSiIT5B+rytg== X-Received: by 2002:a50:b384:: with SMTP id s4-v6mr10570825edd.28.1526648971646; Fri, 18 May 2018 06:09:31 -0700 (PDT) Received: from shalem.localdomain (546A5441.cm-12-3b.dynamic.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id b22-v6sm3772040edn.44.2018.05.18.06.09.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 06:09:30 -0700 (PDT) Subject: Re: [BUG] i2c-hid: ELAN Touchpad does not work on ASUS X580GD To: Jarkko Nikula , Andy Shevchenko , Chris Chiu Cc: Daniel Drake , Jian-Hong Pan , Jiri Kosina , Benjamin Tissoires , Jani Nikula , Dmitry Torokhov , Adrian Salido , Jason Gerecke , linux-input , Mika Westerberg , Wolfram Sang , linux-i2c@vger.kernel.org, Linux Kernel , Linux Upstreaming Team References: <7728da79-8a7a-b87d-d09c-b36978b3032e@linux.intel.com> <822d5f47cad46ca308d511f7f24cdbc5f4af38b9.camel@linux.intel.com> <9fd4cd99-5a4f-2d9e-88ba-18575e951490@linux.intel.com> From: Hans de Goede Message-ID: <9e49fc42-75be-3bd5-dfa4-9cc61348d501@redhat.com> Date: Fri, 18 May 2018 15:09:29 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9fd4cd99-5a4f-2d9e-88ba-18575e951490@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 18-05-18 12:58, Jarkko Nikula wrote: > 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. Ok, thank you for checking this. Regards, Hans