From: Fabien Lahoudere <fabien.lahoudere@collabora.com>
To: unlisted-recipients:; (no To-header on input)
Cc: gwendal@chromium.org, egranata@chromium.org,
kernel@collabora.com,
Fabien Lahoudere <fabien.lahoudere@collabora.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Lee Jones <lee.jones@linaro.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nick Vaccaro <nvaccaro@chromium.org>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] counter: cros_ec: Add sync sensor driver
Date: Fri, 23 Aug 2019 14:41:26 +0200 [thread overview]
Message-ID: <cover.1566563833.git.fabien.lahoudere@collabora.com> (raw)
Some chromebook EC provides a counter to get all vsync coming from the back
camera.
This series introduces a patch coming from chromebook kernel 4.4 designed as an
IIO counter. As IIO counter will be deprecated in favor of counter, I rebase the
original patch and support the new counter API.
The serie need to be merged after https://lkml.org/lkml/2019/7/9/305
Changes since v1:
- Drop code related to IIO_COUNT
- Add external attribute to the counter driver
- Add cros_ec_sensors_sync.c to MAINTAINERS file
Gwendal Grignou (1):
counter: cros_ec: Add synchronization sensor
Documentation/driver-api/generic-counter.rst | 3 +
MAINTAINERS | 7 +
drivers/counter/Kconfig | 9 +
drivers/counter/Makefile | 1 +
drivers/counter/counter.c | 2 +
drivers/counter/cros_ec_sensors_sync.c | 208 ++++++++++++++++++
.../cros_ec_sensors/cros_ec_sensors_core.c | 1 +
drivers/mfd/cros_ec_dev.c | 3 +
include/linux/counter.h | 1 +
9 files changed, 235 insertions(+)
create mode 100644 drivers/counter/cros_ec_sensors_sync.c
--
2.20.1
next reply other threads:[~2019-08-23 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:41 Fabien Lahoudere [this message]
2019-08-23 12:41 ` [PATCH v2 1/1] counter: cros_ec: Add synchronization sensor Fabien Lahoudere
2019-08-24 19:48 ` kbuild test robot
2019-08-26 8:56 ` Jonathan Cameron
2019-08-29 11:10 ` Fabien Lahoudere
2019-09-24 14:20 ` Fabien Lahoudere
2019-09-24 14:52 ` William Breathitt Gray
2019-11-10 15:14 ` William Breathitt Gray
2019-11-11 11:49 ` Jonathan Cameron
2019-11-12 1:16 ` William Breathitt Gray
2020-04-08 17:10 ` Gwendal Grignou
2020-04-08 17:24 ` William Breathitt Gray
2019-08-29 11:34 ` William Breathitt Gray
2019-09-02 9:40 ` Lee Jones
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.1566563833.git.fabien.lahoudere@collabora.com \
--to=fabien.lahoudere@collabora.com \
--cc=bleung@chromium.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=egranata@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=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nvaccaro@chromium.org \
--cc=pmeerw@pmeerw.net \
--cc=vilhelm.gray@gmail.com \
/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).