Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4206200imm; Fri, 18 May 2018 00:50:31 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqwNCTe4sjPlF1FAT3NfHhOlxb6r7RzcpgMTVCk14hC7imvS1AtgEo6oAEVs3lwaPfH8MVA X-Received: by 2002:a63:7b0d:: with SMTP id w13-v6mr6628076pgc.221.1526629830972; Fri, 18 May 2018 00:50:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526629830; cv=none; d=google.com; s=arc-20160816; b=GWVYu3xv0UYpEHEYew+xs4hRU9IM4Xc3T2AiWwuASLpTE+x055jbo1nVCbv26Y3uF1 sx/mgoqOzOkytjHxAz43MnUHxANZmelv0tgzrmtTI9ShRoz3Q+JEOC2hHIl9xso1uIlm syNqRQGhGLPYY6SI2EvwlsttXPz9w+eg1Ih5lbRpjwqdVxz5mbW0SwVwkhZ9OqpUku4f 8uydiIldlfayCLo7Y8tSxVtdcuRmCkKrylwkINXFMQ8G2kTKVrX/DxFfo0C4zEd37rzI lx+XmeswOb9NsCi7S4NhT4TQOeFkJqerOGU2MdN5Vuly9vwqboYWL9BTJMqzepuLW3/O CEsg== 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=mrFhaSdxA3eMzm8n1XQYXxmQyLDpireTj2NplbcNn2Q=; b=QWO8wKb66Wwwed2JArmJ+acYx//fG3TpKh9xVjyAwLqGjQnGFcHaPH1G5q6BlLL90b BHM3V3GuFoZPWO7xYARh6zsUZkn/iQWS5e5G7llf8oCxgYOnZjLEoYkBn0YFfrubMYpd YKk5IkLiCmkEMsxpWbrhuzfAwnNKD4OZ2gqZR7EK7clRphawe/ZNryynMOxtu/u/WCgt OXbfbIh+MZBweyTyN9Gf1vhZz5ba6gCwUw0VX8Ewj1iTNd9HsQqVdZCvVk0xL27fzFhZ e311Vw4Voe9LDE4Pxk4GTN6L94NXgqcAK9sY8ma5IqEjg1Ik3h5kwEAfm8NeDMjk5Lnd WJ4g== 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 31-v6si7013642plh.552.2018.05.18.00.50.16; Fri, 18 May 2018 00:50:30 -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 S1751589AbeERHs1 (ORCPT + 99 others); Fri, 18 May 2018 03:48:27 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34094 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751049AbeERHsZ (ORCPT ); Fri, 18 May 2018 03:48:25 -0400 Received: by mail-wm0-f67.google.com with SMTP id a137-v6so2399522wme.1 for ; Fri, 18 May 2018 00:48:24 -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=mrFhaSdxA3eMzm8n1XQYXxmQyLDpireTj2NplbcNn2Q=; b=rW+86MCw3v0l/whmbXGk7d2txKqwh8FOr/5QfKJPL/MFmLec5iK6dmpEhwKRLkiRZm 80q0j59uEF1O379dJNGU/J15R5ZTVxdtTCpbBLiqj4ddLVig3rb5wbNkdZLFIDnWnAcE 3jhaLXV1bdw7drJmsj1lTr0BuBDh4H8+6+DQ+c+Y9vQQlbDrwNTVFV02i13aDyl/Wctl 3YBeVVtjh3N4GNK8JWD0sBgezLnUagBbz8gYXgHlid51SoUsC3FW17MsI+k2C+gsymRx e7e2afhVqQvHSCd1qAoY6EJu9mE/Fp7sd7BQzO5EirS1YH5B0Ty0EgKbAQHm0Ju/ir6o 6eRw== X-Gm-Message-State: ALKqPwfcq7CspWU1EAcTZKCov4hV88h/2Fwu5B4NSwlJ2SWmEPN3fEz7 PtsblrJah9f6OgcfNt7HludZBin5Bn4= X-Received: by 2002:a50:a107:: with SMTP id 7-v6mr10838017edj.280.1526629704348; Fri, 18 May 2018 00:48:24 -0700 (PDT) Received: from shalem.localdomain (546A5441.cm-12-3b.dynamic.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id e24-v6sm3391155edc.80.2018.05.18.00.48.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 00:48:23 -0700 (PDT) Subject: Re: [BUG] i2c-hid: ELAN Touchpad does not work on ASUS X580GD To: Jarkko Nikula , Chris Chiu Cc: Daniel Drake , Jian-Hong Pan , Jiri Kosina , Benjamin Tissoires , Jani Nikula , Dmitry Torokhov , Adrian Salido , Jason Gerecke , linux-input , Andy Shevchenko , Mika Westerberg , Wolfram Sang , linux-i2c@vger.kernel.org, Linux Kernel , Linux Upstreaming Team References: <7728da79-8a7a-b87d-d09c-b36978b3032e@linux.intel.com> From: Hans de Goede Message-ID: Date: Fri, 18 May 2018 09:48:22 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jarkko, et.al., On 17-05-18 09:48, Jarkko Nikula wrote: > Hi > > On 05/15/2018 01:20 PM, Jarkko Nikula wrote: >> On 05/15/2018 06:22 AM, Chris Chiu wrote: >>> What if I change the 120MHz to 180MHz and then make sure that the I2C operates >>> in target FS mode frequency 400kHz via scope? Would there be any side effect? >>> Maybe some other busses frequency could be also affected and causing some other >>> component malfunction? >>> >> Should be safe. It is only clock rate information when registering a fixed clock with known rate in intel-lpss.c and i2c-designware uses that info when calculating the timing parameters. I.e. it doesn't change any internal clocks. >> >> I'm trying to find a contact who can confirm what is the expected rate of I2C input clock and is it common to all Cannon Lake HW. >> > I got confirmation that input clock is actually even higher 216 Mhz. > > While checking does it cover all of those CNL CNL-LP and CNL-H PCI IDs may I add your Jian-Hong, Chris and Daniel email addresses to Repored-by tags in a fix patch? 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". Regards, Hans