From: Thierry Escande <thierry.escande@collabora.com>
To: Benson Leung <bleung@chromium.org>, Jonathan Cameron <jic23@kernel.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Gwendal Grignou <gwendal@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] platform/chrome: Support for cros_ec_accel_legacy driver
Date: Thu, 5 Oct 2017 18:02:33 +0200 [thread overview]
Message-ID: <1507219357-5722-1-git-send-email-thierry.escande@collabora.com> (raw)
Hi,
This series enables a driver for a legacy accelerometer driver used on
Chromebook devices with older EC firmware.
In addition to the cros_ec_accel_legacy driver, this series contains a
fix that registers the cros_ec_lpc driver on Chromebook devices that
does not have the GOOG0004 ACPI entry. In such case, the driver register
the device itself. This series also adds support to the cros_ec_lpc
driver for Glimmer based devices (Lenovo Yoga 11e).
The last patch is the code used to register this driver if the usual way
of registering the croc_ec sensors hub fails. In this case, the 2
accelerometers (base and lid) are registered using mfd_add_devices().
As there is work in progress to remove calls to mfd_add_devices() from
cros_ec_dev.c, this code is in a separate patch with the idea to make
that easier.
Changes in v3:
- Use kernel-doc notation for function headers
- Add more comment to sensor ID sysfs attribute documentation
- Restore accidentaly deleted comment for IIO_CHAN_INFO_CALIBBIAS handling in
iio_info write_raw() callback
Changes in v2:
- Reorganize code to avoid forward declarations
- Simplify capture buffer declaration (also helps to remove forward
declarations)
- Make use of iio_push_to_buffers_with_timestamp() and let the
framework hamdle timestamp copy into capture buffer
- Added missing sysfs attribute documentation
- Few cosmetic changes here and there
Enric Balletbo i Serra (1):
platform/chrome: cros_ec_lpc: Register the driver if ACPI entry is
missing.
Gwendal Grignou (1):
platform/chrome: Add cros_ec_accel_legacy driver
Thierry Escande (2):
platform/chrome: cros_ec_lpc: Add support for Google Glimmer
platform/chrome: Register cros_ec_accel_legacy driver
Documentation/ABI/testing/sysfs-bus-iio-cros-ec | 10 +
drivers/iio/accel/Kconfig | 11 +
drivers/iio/accel/Makefile | 2 +
drivers/iio/accel/cros_ec_accel_legacy.c | 420 ++++++++++++++++++++++++
drivers/platform/chrome/cros_ec_dev.c | 53 +++
drivers/platform/chrome/cros_ec_lpc.c | 41 ++-
6 files changed, 536 insertions(+), 1 deletion(-)
create mode 100644 drivers/iio/accel/cros_ec_accel_legacy.c
--
2.7.4
next reply other threads:[~2017-10-05 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:02 Thierry Escande [this message]
2017-10-05 16:02 ` [PATCH v3 1/4] platform/chrome: cros_ec_lpc: Register the driver if ACPI entry is missing Thierry Escande
2017-10-05 16:02 ` [PATCH v3 2/4] platform/chrome: cros_ec_lpc: Add support for Google Glimmer Thierry Escande
2017-10-05 16:02 ` [PATCH v3 3/4] platform/chrome: Add cros_ec_accel_legacy driver Thierry Escande
2017-10-06 13:00 ` Jonathan Cameron
2017-10-05 16:02 ` [PATCH v3 4/4] platform/chrome: Register " Thierry Escande
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=1507219357-5722-1-git-send-email-thierry.escande@collabora.com \
--to=thierry.escande@collabora.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@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
all inboxes | Powered by JetHome®