From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Nikula Subject: Re: How my i2c device bring up? Date: Wed, 17 May 2017 14:55:41 +0300 Message-ID: <9c683d1f-06c6-eadb-d9be-5ff22845181f@linux.intel.com> References: <032401d2cee9$6ab6ea80$4024bf80$@emc.com.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=big5; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <032401d2cee9$6ab6ea80$4024bf80$@emc.com.tw> Sender: linux-acpi-owner@vger.kernel.org To: =?UTF-8?B?5YqJ5ZiJ6ae/?= , linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org, linux-input@vger.kernel.org Cc: Dmitry Torokhov , benjamin.tissoires@gmail.com, jeff.chuang@emc.com.tw List-Id: linux-input@vger.kernel.org Hi On 05/17/2017 11:41 AM, ¼B¹ÅÂ@ wrote: > > I have tried to install three versions of Chromium OS(R58-9334, R59-9351, > R60-9554) respectively, > all of them runs kernel v4.4 and all of them can see nothing for my device > by ¡§ls /sys/bus/i2c/devices¡¨. > The output file is as ¡§Chromum_v4.4.52_dev_bus_i2c_devices_0517.jpg¡¨. > I guess the underlying drivers(I2C bus, ACPI DSDT table) could be failed to > recognize my I2C device. > Is this Intel Skylake ix-6xxx based laptop? My guess is that based on your finding that i2c touchscreen works in Ubuntu that Chromium kernel may not have needed drivers enabled. If you have access to kernel config of Chromium image could you check does it have these MFD_INTEL_LPSS configurations on? I have them as built-in but should work when built as modules too. CONFIG_MFD_INTEL_LPSS=y CONFIG_MFD_INTEL_LPSS_ACPI=y CONFIG_MFD_INTEL_LPSS_PCI=y I suppose these I2C_DESIGNWARE options are already on since I know there are Intel Baytrail based Chromebooks out there. CONFIG_I2C_DESIGNWARE_CORE=m CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DESIGNWARE_PCI=m CONFIG_I2C_DESIGNWARE_BAYTRAIL=y -- Jarkko