From: 劉嘉駿 <scott.liu@emc.com.tw>
To: linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-input@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
benjamin.tissoires@gmail.com, jeff.chuang@emc.com.tw
Subject: How my i2c device bring up?
Date: Wed, 17 May 2017 16:41:45 +0800 [thread overview]
Message-ID: <032401d2cee9$6ab6ea80$4024bf80$@emc.com.tw> (raw)
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
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
[-- Attachment #2: Kernel_log.bz2 --]
[-- Type: application/octet-stream, Size: 33789 bytes --]
[-- Attachment #3: dsdt.dsl.bz2 --]
[-- Type: application/octet-stream, Size: 84878 bytes --]
[-- Attachment #4: Chromum_v4.4.52_dev_bus_i2c_devices_0517.jpg --]
[-- Type: image/jpeg, Size: 22465 bytes --]
[-- Attachment #5: Ubuntu_16.04_Kernel-v.4.4_0517.jpg --]
[-- Type: image/jpeg, Size: 37460 bytes --]
next reply other threads:[~2017-05-17 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:41 劉嘉駿 [this message]
2017-05-17 11:55 ` How my i2c device bring up? Jarkko Nikula
2017-05-18 11:09 ` 劉嘉駿
2017-05-19 6:42 ` 劉嘉駿
2017-05-19 8:23 ` Jarkko Nikula
2017-05-19 8:38 ` 劉嘉駿
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='032401d2cee9$6ab6ea80$4024bf80$@emc.com.tw' \
--to=scott.liu@emc.com.tw \
--cc=benjamin.tissoires@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff.chuang@emc.com.tw \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).