From: Fabien Lahoudere <fabien.lahoudere@collabora.com>
To: linux-iio@vger.kernel.org
Cc: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Subject: [RFC 0/1] Add new sysfs ABI for chromebook devices
Date: Fri, 3 May 2019 12:54:45 +0200 [thread overview]
Message-ID: <cover.1556873525.git.fabien.lahoudere@collabora.com> (raw)
Chromebooks embedded controller (EC) provides new field in the 3rd version of
its protocol. Those values need to be exposed as sysfs entries.
Minimum and maximum frequencies may probably be a standard iio ABI.
There is an existing ABI (sampling_frequency_available) but only for discrete
set of values.
We have different possible solution and I want to ask interested people for the
best one:
1. we keep the ABI proposed in this RFC (in the chromebook specific code)
2. we move min and max freq as 2 different standard ABI
3. we add a new standard iio ABI to set a range (sampling_frequency_range)
4. we change the 'sampling_frequency_available' ABI to return discrete values
like '2 4 6 8' or a range like '[2 - 8]'
5. the solution I didn't think about
Thanks
Gwendal Grignou (1):
iio: common: cros_ec_sensors: add extra sensor API
.../ABI/testing/sysfs-bus-iio-cros-ec | 24 ++++
.../cros_ec_sensors/cros_ec_sensors_core.c | 126 +++++++++++++++++-
.../linux/iio/common/cros_ec_sensors_core.h | 7 +
include/linux/mfd/cros_ec_commands.h | 21 +++
4 files changed, 177 insertions(+), 1 deletion(-)
--
2.19.2
next reply other threads:[~2019-05-03 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 10:54 Fabien Lahoudere [this message]
2019-05-03 10:54 ` [RFC 1/1] iio: common: cros_ec_sensors: add extra sensor API Fabien Lahoudere
2019-05-05 15:36 ` Jonathan Cameron
2019-05-25 0:28 ` Gwendal Grignou
2019-05-27 9:18 ` Jonathan Cameron
2019-05-30 4:28 ` Gwendal Grignou
2019-05-05 15:32 ` [RFC 0/1] Add new sysfs ABI for chromebook devices 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.1556873525.git.fabien.lahoudere@collabora.com \
--to=fabien.lahoudere@collabora.com \
--cc=linux-iio@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).