From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: linux-kernel@vger.kernel.org, jic23@kernel.org,
linux-iio@vger.kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net
Cc: fabrice.gasnier@st.com, linaro-kernel@lists.linaro.org,
benjamin.gaignard@linaro.org,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v1 0/2] iio: stm32 trigger: Add counter device
Date: Wed, 1 Mar 2017 15:45:04 +0100 [thread overview]
Message-ID: <1488379506-23969-1-git-send-email-benjamin.gaignard@st.com> (raw)
A first encoder IIO driver (104-quad-8) with a count channel already exist.
STM32 driver have the same type of feature but with different counting modes.
Some parts, like counting direction (up/down) could be generalized so move the
corresponding documentation from driver file to sysfs-bus-iio.
Benjamin Gaignard (2):
iio: Generalize counting direction modes
iio: stm32 trigger: Add counter device
Documentation/ABI/testing/sysfs-bus-iio | 14 ++
.../ABI/testing/sysfs-bus-iio-counter-104-quad-8 | 8 -
.../ABI/testing/sysfs-bus-iio-timer-stm32 | 40 ++++
drivers/iio/trigger/stm32-timer-trigger.c | 231 ++++++++++++++++++++-
include/linux/mfd/stm32-timers.h | 2 +
5 files changed, 281 insertions(+), 14 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-01 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 14:45 Benjamin Gaignard [this message]
2017-03-01 14:45 ` [PATCH v1 1/2] iio: Generalize counting direction modes Benjamin Gaignard
2017-03-05 11:16 ` Jonathan Cameron
2017-03-01 14:45 ` [PATCH v1 2/2] iio: stm32 trigger: Add counter device Benjamin Gaignard
2017-03-05 12:04 ` Jonathan Cameron
2017-03-12 13:18 ` Benjamin Gaignard
2017-03-14 18:53 ` William Breathitt Gray
2017-03-17 14:36 ` Benjamin Gaignard
2017-03-20 13:25 ` William Breathitt Gray
2017-03-20 19:14 ` Jonathan Cameron
2017-03-20 18:53 ` Jonathan Cameron
2017-03-20 18:50 ` 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=1488379506-23969-1-git-send-email-benjamin.gaignard@st.com \
--to=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=fabrice.gasnier@st.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).