From: Jonathan Cameron <jic23@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Fabrice Gasnier <fabrice.gasnier@st.com>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH v1 0/2] iio: Add parent_trigger attribute to triggers
Date: Sat, 11 Feb 2017 10:23:27 +0000 [thread overview]
Message-ID: <d6bc74a2-9899-5f33-f04e-66da6209daf9@kernel.org> (raw)
In-Reply-To: <CA+M3ks5DzaXwmnnoin9kVUtV+sX5wXiiDz54=c541Huggi4a-Q@mail.gmail.com>
On 06/02/17 14:43, Benjamin Gaignard wrote:
> 2017-02-06 15:26 GMT+01:00 Lars-Peter Clausen <lars@metafoo.de>:
>> On 02/06/2017 03:21 PM, Benjamin Gaignard wrote:
>>> 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.
>>
>> Can you explain how this is different to assigning the parent_trigger
>> directly to the device?
>>
>
> It is the same but done on trigger structure without need to have an iio device.
>
> While writing stm32 trigger driver Jonathan explain me that I can't use an iio
> device without channel to chain my hardware blocks.
> Since my hardware allows to chain triggers, Jonathan suggest to create this
> parent_trigger attribute to ab able to link the triggers.
>
I think Lars was looking for the more general explanation. How does
one trigger drive another one? What does that mean?
prev parent reply other threads:[~2017-02-11 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:21 [PATCH v1 0/2] iio: Add parent_trigger attribute to triggers Benjamin Gaignard
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 [this message]
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=d6bc74a2-9899-5f33-f04e-66da6209daf9@kernel.org \
--to=jic23@kernel.org \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=fabrice.gasnier@st.com \
--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).