Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp399100imm; Tue, 15 May 2018 03:28:10 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpt7cAB6zeV2qR6KvcK5kI4u5xMAy33oII2wxhQEZCvNr7Lz71AcXu8KC2PxhwfRRn118B9 X-Received: by 2002:a62:4b8b:: with SMTP id d11-v6mr14519233pfj.244.1526380090215; Tue, 15 May 2018 03:28:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526380090; cv=none; d=google.com; s=arc-20160816; b=S71JV90GMzkrcoKWgW7P5FLAZCQweaiUpzMwcppVWbu/EKdDjVGCoMp2+FlxedJTPM A/82MfcQed0evGGEIDk/g+gkTkzGoH+Gr+BSFR0wgiDzoAENJGlgxS3k3Xcv3Ey6Zs+c pVu+VU6oYEMPZKS67wyi1MOt+srYEFyCmNFqMXJCDaVKLRiDHcUkpGJDXpwQ233hih0z 2sZECOb2rBt2+2g16v/2u2K9DgYVqpfFerKHY7g2x82c7CWp64q4VVVskdtVHiGITTL9 lJN10WMi5014b7FN8jV/Ls3b984ZnF+wKHjbvoQq7zg54ShZaCfOjC0IwZxnF5dOy9rb qfug== 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=ojoVXU0agXlJeUhyWZ1qfWIV5j914Qcz23qiqwu85mo=; b=RpdwOVVNFvbpEWVH8pC9Smz65SAA0WobIR0H74QAKDCieinrw+UhEHZWnxGK5hgp3q PZyzKtoxyA1gpHAloylqslQkICGHpDKtK43PWjqoLZGJQeO8lREc9iwT4Q/JQM0+L5FP HP/rdEL78KkSef+ZpqEY0mKDWBoLjc3i4js8VRB3+QSMufbd5cFv0z7/w/FRKC2x1WEL UwzFnzhkF3ukT/04oPAtFnOVGRbz5x9A74dduIZIiWm3UG7bMY6QoQ1+e0vFPBnDX8Q5 mGhxe8DKfQFPY+NGC514YX/EjjU349gmaT4xoeqapn4eSwwrwUlNohI0FYEG5yeZf1kp WyWQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w20-v6si11708667pfn.12.2018.05.15.03.27.56; Tue, 15 May 2018 03:28:10 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752821AbeEOKUn (ORCPT + 99 others); Tue, 15 May 2018 06:20:43 -0400 Received: from mga18.intel.com ([134.134.136.126]:40959 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752343AbeEOKUl (ORCPT ); Tue, 15 May 2018 06:20:41 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 May 2018 03:20:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,403,1520924400"; d="scan'208";a="55333502" Received: from mylly.fi.intel.com (HELO [10.237.72.56]) ([10.237.72.56]) by fmsmga001.fm.intel.com with ESMTP; 15 May 2018 03:20:36 -0700 Subject: Re: [BUG] i2c-hid: ELAN Touchpad does not work on ASUS X580GD To: Chris Chiu Cc: Daniel Drake , Jian-Hong Pan , Jiri Kosina , Benjamin Tissoires , Jani Nikula , Hans de Goede , 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: From: Jarkko Nikula Message-ID: <7728da79-8a7a-b87d-d09c-b36978b3032e@linux.intel.com> Date: Tue, 15 May 2018 13:20:58 +0300 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 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. -- Jarkko