I asked this because I have problem to bring my I2C device up on Chromium
OS.
I have a x86 laptop which works well on win10 OS with I2C-HID touchscreen
device.
Currently, I want to install Chromium OS on it with original set (No
retrofit required).
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.
Also I do some experiment by installed Ubuntu desktop version(16.04) with
kernel version v4.4 on the same laptop.
My device can be found and touchscreen works. Please refer to
"Ubuntu_16.04_Kernel-v.4.4_0517.jpg".
Attached files is my kernel log(kernel version: v4.4.52) and DSDT table, the
label [ELAN] is by me; please ignore it.
I am not familiar with I2C bus / ACPI driver, please let me know if any idea
or any logs you need.
Thanks.
BR,
Scott
From: Jarkko Nikula <hidden> Date: 2017-05-17 11:55:41
Hi
On 05/17/2017 11:41 AM, 劉嘉駿 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
Hi Jakko,
I am not happy because the internet & network are so slow..... :(
The kernel of those configurations are still on compile.
I have checked that my target platform is Intel Baytrail, so good
luck with me.
Thank you !
BR,
Scott
-----Original Message-----
From: Jarkko Nikula [mailto:jarkko.nikula@linux.intel.com]
Sent: Wednesday, May 17, 2017 7:56 PM
To: 劉嘉駿; 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
Subject: Re: How my i2c device bring up?
Hi
On 05/17/2017 11:41 AM, 劉嘉駿 wrote:
quoted
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
Hi Jarkko,
After enabled those configurations on, the touch works.
Chrome can recognize my touch device, thank you for help.
BR,
Scott
-----Original Message-----
From: Jarkko Nikula [mailto:jarkko.nikula@linux.intel.com]
Sent: Wednesday, May 17, 2017 7:56 PM
To: 劉嘉駿; 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
Subject: Re: How my i2c device bring up?
Hi
On 05/17/2017 11:41 AM, 劉嘉駿 wrote:
quoted
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
Nice to hear. Looks like those Chromium images don't support platforms
that
require those CONFIG_MFD_INTEL_LPSS options.
Those configurations are default in 64bits image.
The image was 32bits in the first place I built which
doesn't default set those configurations for Intel Baytrail.
Thanks.
Scott