From: Fabien Lahoudere <fabien.lahoudere@collabora.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kernel@collabora.com,
Fabien Lahoudere <fabien.lahoudere@collabora.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Nick Vaccaro <nvaccaro@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/1] Expose cros_ec_sensors frequency range via iio sysfs
Date: Tue, 16 Jul 2019 11:11:05 +0200 [thread overview]
Message-ID: <cover.1563268064.git.fabien.lahoudere@collabora.com> (raw)
Chromebooks EC sensors must expose a range of frequencies for each sensors using
the standard ABI sampling_frquency_available.
This patch needs https://lkml.org/lkml/2019/7/2/345
Changes since v4:
- Remove trailing whitespace
- Use checkpatch.pl successfully
Changes since v3:
- Split patch 6
- Drop clean up patches
- Fix minor changes
Changes since v2:
- use read_avail callback
- rework core functions to avoid code duplication
Changes since v1:
- Add a cover letter
- Add Nick Vaccaro SoB to patch 1
- Drop fifo size related code
Fabien Lahoudere (1):
iio: common: cros_ec_sensors: Expose cros_ec_sensors frequency range
via iio sysfs
.../common/cros_ec_sensors/cros_ec_sensors.c | 3 +
.../cros_ec_sensors/cros_ec_sensors_core.c | 65 +++++++++++++++++++
drivers/iio/light/cros_ec_light_prox.c | 3 +
.../linux/iio/common/cros_ec_sensors_core.h | 21 ++++++
4 files changed, 92 insertions(+)
--
2.20.1
next reply other threads:[~2019-07-16 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 9:11 Fabien Lahoudere [this message]
2019-07-16 9:11 ` [PATCH v5 1/1] iio: common: cros_ec_sensors: Expose cros_ec_sensors frequency range via iio sysfs Fabien Lahoudere
2019-07-27 22:16 ` Jonathan Cameron
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=cover.1563268064.git.fabien.lahoudere@collabora.com \
--to=fabien.lahoudere@collabora.com \
--cc=allison@lohutok.net \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvaccaro@chromium.org \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
/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).