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, vilhelm.gray@gmail.com
Cc: fabrice.gasnier@st.com, linaro-kernel@lists.linaro.org,
benjamin.gaignard@linaro.org,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v2 0/2] iio: stm32 trigger: Add quadrature device and counter
Date: Fri, 24 Mar 2017 15:00:41 +0100 [thread overview]
Message-ID: <1490364043-16339-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.
version 2:
- since iio: Generalize counting direction modes commit of version has being
pushed in iio.git testing branch I have remove it from this serie.
- split the original attribute in 2: one for quadrature modes and one for
enable modes.
- add scale info
- change modes to more generic names to be able to merge them with 104-quad-8
in the futur.
Benjamin Gaignard (2):
iio: stm32 trigger: Add quadrature encoder device
iio: stm32 trigger: Add counter enable modes
.../ABI/testing/sysfs-bus-iio-timer-stm32 | 55 ++++
drivers/iio/trigger/stm32-timer-trigger.c | 314 ++++++++++++++++++++-
include/linux/mfd/stm32-timers.h | 2 +
3 files changed, 365 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-24 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 14:00 Benjamin Gaignard [this message]
2017-03-24 14:00 ` [PATCH v2 1/2] iio: stm32 trigger: Add quadrature encoder device Benjamin Gaignard
2017-03-25 18:26 ` Jonathan Cameron
2017-03-25 23:12 ` Michael Welling
2017-03-25 23:23 ` Michael Welling
2017-03-24 14:00 ` [PATCH v2 2/2] iio: stm32 trigger: Add counter enable modes Benjamin Gaignard
2017-03-25 18:29 ` 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=1490364043-16339-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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.