From: eugen.hristev@microchip.com (Eugen Hristev)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] iio: adc: sama5d2_adc hw triggers and buffers
Date: Wed, 19 Apr 2017 11:20:42 +0300 [thread overview]
Message-ID: <1492590045-17329-1-git-send-email-eugen.hristev@microchip.com> (raw)
This patch implements the hardware triggers support and
buffer management for sama5d2.
The DT modifications ( [PATCH 1/3] ARM: dts: at91: sama5d2_xplained:
enable ADTRG pin) are for demonstration purposes of the feature,
setting the pinctrl for the ADC hw trigger pin,should go through at91
maintainers.
I also increased the buffer size for the trigger name in the generic_buffer
application to cope with longer names and avoid stack smashing problem.
This is in patch [PATCH 3/3] iio: tools: generic_buffer: increase trigger length
Eugen Hristev (3):
ARM: dts: at91: sama5d2_xplained: enable ADTRG pin
iio: adc: at91-sama5d2_adc: add hw trigger and buffer support
iio: tools: generic_buffer: increase trigger length
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 16 ++-
drivers/iio/adc/at91-sama5d2_adc.c | 208 +++++++++++++++++++++++++++-
tools/iio/iio_utils.h | 2 +-
3 files changed, 220 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-19 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 8:20 Eugen Hristev [this message]
2017-04-19 8:20 ` [PATCH 1/3] ARM: dts: at91: sama5d2_xplained: enable ADTRG pin Eugen Hristev
2017-04-24 9:04 ` Ludovic Desroches
2017-04-19 8:20 ` [PATCH 2/3] iio: adc: at91-sama5d2_adc: add hw trigger and buffer support Eugen Hristev
2017-04-24 9:06 ` Ludovic Desroches
2017-04-27 5:18 ` Jonathan Cameron
2017-04-19 8:20 ` [PATCH 3/3] iio: tools: generic_buffer: increase trigger length Eugen Hristev
2017-04-20 16:06 ` Daniel Baluta
2017-04-27 5:19 ` 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=1492590045-17329-1-git-send-email-eugen.hristev@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).