From: Gwendal Grignou <gwendal@chromium.org>
To: jic23@kernel.org, bleung@chromium.org,
enric.balletbo@collabora.com, groeck@chromium.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Gwendal Grignou <gwendal@chromium.org>
Subject: [PATCH 0/2] Support accelerometers for veyron_minnie
Date: Thu, 20 Jun 2019 11:52:57 -0700 [thread overview]
Message-ID: <20190620185259.142133-1-gwendal@chromium.org> (raw)
veyron_minnie - ASUS Chromebook Flip C100PA - embedded controller
controls two accelerometers, one in the lid, one in the base.
However, the EC firmware does not follow the new interface that
cros_ec_accel driver use.
Extend the legacy driver used on glimmer - Lenovo ThinkPad 11e
Chromebook - to veyron_minnie.
veyron_minnie being ARM based, issue command over the I2C bus to the EC
instead of relying on the shared registers over LPC.
Gwendal Grignou (2):
iio: cros_ec: Add sign vector in core for backward compatibility
iio: cros_ec : Extend legacy support to ARM device
drivers/iio/accel/Kconfig | 4 +-
drivers/iio/accel/cros_ec_accel_legacy.c | 353 ++++--------------
.../cros_ec_sensors/cros_ec_sensors_core.c | 5 +-
.../linux/iio/common/cros_ec_sensors_core.h | 1 +
4 files changed, 84 insertions(+), 279 deletions(-)
--
2.22.0.410.gd8fdbe21b5-goog
next reply other threads:[~2019-06-20 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 18:52 Gwendal Grignou [this message]
2019-06-20 18:52 ` [PATCH 1/2] iio: cros_ec: Add sign vector in core for backward compatibility Gwendal Grignou
2019-06-20 21:46 ` Doug Anderson
2019-06-21 2:25 ` Gwendal Grignou
2019-06-20 18:52 ` [PATCH 2/2] iio: cros_ec : Extend legacy support to ARM device Gwendal Grignou
2019-06-21 2:41 [PATCH 0/2] Support accelerometers for veyron_minnie Gwendal Grignou
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=20190620185259.142133-1-gwendal@chromium.org \
--to=gwendal@chromium.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).