From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: 劉嘉駿 <scott.liu@emc.com.tw>,
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: Re: How my i2c device bring up?
Date: Wed, 17 May 2017 14:55:41 +0300 [thread overview]
Message-ID: <9c683d1f-06c6-eadb-d9be-5ff22845181f@linux.intel.com> (raw)
In-Reply-To: <032401d2cee9$6ab6ea80$4024bf80$@emc.com.tw>
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
next prev parent reply other threads:[~2017-05-17 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:41 How my i2c device bring up? 劉嘉駿
2017-05-17 11:55 ` Jarkko Nikula [this message]
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=9c683d1f-06c6-eadb-d9be-5ff22845181f@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--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 \
--cc=scott.liu@emc.com.tw \
/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).