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: Add parent_trigger attribute to triggers
Date: Mon, 6 Feb 2017 15:21:50 +0100 [thread overview]
Message-ID: <1486390912-24362-1-git-send-email-benjamin.gaignard@st.com> (raw)
Thoses patches add parent_trigger attribute to IIO triggers.
The goal is to allow triggers to use triggers like is this done for iio
devices.
With this patch it will be possible to chain triggers, for example
stm32 triggers could be used as clock of an other triggers:
echo "tim1_trgo" > trigger0/parent_trigger.
Similary to what already exist to validate a device, a new (optional)
validate_trigger function is added in iio_trigger structure and should be
filled by drivers.
Benjamin Gaignard (2):
iio: Allow triggers to be used as parent of others triggers
iio: stm32 trigger: Implement validate_trigger function
.../ABI/testing/sysfs-bus-iio-timer-stm32 | 26 ++++++
.../ABI/testing/sysfs-bus-iio-trigger-sysfs | 8 ++
drivers/iio/industrialio-trigger.c | 68 ++++++++++++++
drivers/iio/trigger/stm32-timer-trigger.c | 104 +++++++++++++++++++++
include/linux/iio/trigger.h | 6 +-
5 files changed, 211 insertions(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2017-02-06 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:21 Benjamin Gaignard [this message]
2017-02-06 14:21 ` [PATCH v1 1/2] iio: Allow triggers to be used as parent of others triggers Benjamin Gaignard
2017-02-11 10:54 ` Jonathan Cameron
2017-02-06 14:21 ` [PATCH v1 2/2] iio: stm32 trigger: Implement validate_trigger function Benjamin Gaignard
2017-02-11 11:14 ` Jonathan Cameron
2017-02-06 14:26 ` [PATCH v1 0/2] iio: Add parent_trigger attribute to triggers Lars-Peter Clausen
2017-02-06 14:43 ` Benjamin Gaignard
2017-02-11 10:23 ` 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=1486390912-24362-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).