From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<nuno.sa@analog.com>, <dragos.bogdan@analog.com>
Subject: Re: [PATCH v2 0/5] iio: Add output buffer support
Date: Thu, 18 Feb 2021 13:38:04 +0000 [thread overview]
Message-ID: <20210218133804.60d7eca7@archlinux> (raw)
In-Reply-To: <20210217083438.37865-1-alexandru.ardelean@analog.com>
On Wed, 17 Feb 2021 10:34:33 +0200
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> This patchset is based on the new multibuffer set.
> It doesn't require the high-speed/mmap interface.
> That will come later on a v2.
>
> Changelog v1 -> v2:
> * https://lore.kernel.org/linux-iio/20210212102021.47276-4-alexandru.ardelean@analog.com/T/#u
> * removed DMA patches for now
> * in patch 'iio: Add output buffer support'
> - added /sys/bus/iio/devices/iio:deviceX/bufferY/direction attribute
> - thinking about this, an update to the new buffer infrastructure is
> required when adding ADDAC/MxFE/transceivers; right now there is no
> problem, because we have only ADCs and DACs; but when we get
> transceivers, a bufferY/ directory needs to filter in/out
> scan_elements/ ; this only occured to me recently (it's one of those
> things that pops up later in mind)
For that we can rely on review in the short term, but agreed a sanity
check that everything matches would make sense.
> * added 'iio: Documentation: update definitions for bufferY and scan_elements'
> - seems I forgot this on the original multibuffer patchset
Likewise. :) Who needs docs?
> * added 'iio: triggered-buffer: extend support to configure output buffers'
> - basically output triggered buffer support
> * added 'iio: dac: ad5686: Add PWM as a trigger source'
> - this is a first user of this infrastructure
>
> Alexandru Ardelean (2):
> iio: Documentation: update definitions for bufferY and scan_elements
> iio: triggered-buffer: extend support to configure output buffers
>
> Lars-Peter Clausen (2):
> iio: Add output buffer support
> iio: kfifo-buffer: Add output buffer support
>
> Mircea Caprioru (1):
> iio: dac: ad5686: Add PWM as a trigger source
>
> Documentation/ABI/testing/sysfs-bus-iio | 92 +++++++++++
> drivers/iio/accel/adxl372.c | 1 +
> drivers/iio/accel/bmc150-accel-core.c | 1 +
> drivers/iio/adc/at91-sama5d2_adc.c | 4 +-
> .../buffer/industrialio-triggered-buffer.c | 8 +-
> drivers/iio/buffer/kfifo_buf.c | 50 ++++++
> .../cros_ec_sensors/cros_ec_sensors_core.c | 1 +
> .../common/hid-sensors/hid-sensor-trigger.c | 5 +-
> drivers/iio/dac/ad5686-spi.c | 2 +-
> drivers/iio/dac/ad5686.c | 146 +++++++++++++++++-
> drivers/iio/dac/ad5686.h | 7 +-
> drivers/iio/dac/ad5696-i2c.c | 2 +-
> drivers/iio/industrialio-buffer.c | 128 ++++++++++++++-
> include/linux/iio/buffer.h | 7 +
> include/linux/iio/buffer_impl.h | 11 ++
> include/linux/iio/triggered_buffer.h | 11 +-
> 16 files changed, 459 insertions(+), 17 deletions(-)
>
prev parent reply other threads:[~2021-02-18 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 8:34 [PATCH v2 0/5] iio: Add output buffer support Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 1/5] iio: Documentation: update definitions for bufferY and scan_elements Alexandru Ardelean
2021-02-18 12:19 ` Jonathan Cameron
2021-02-18 13:36 ` Jonathan Cameron
2021-04-01 13:44 ` Mauro Carvalho Chehab
2021-04-01 15:00 ` Jonathan Cameron
2021-02-17 8:34 ` [PATCH v2 2/5] iio: Add output buffer support Alexandru Ardelean
2021-02-18 13:42 ` Jonathan Cameron
2021-02-19 8:45 ` Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 3/5] iio: kfifo-buffer: " Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 4/5] iio: triggered-buffer: extend support to configure output buffers Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 5/5] iio: dac: ad5686: Add PWM as a trigger source Alexandru Ardelean
2021-02-18 14:05 ` Jonathan Cameron
2021-02-18 14:35 ` Rob Herring
2021-02-19 8:49 ` Alexandru Ardelean
2021-02-23 16:37 ` Lars-Peter Clausen
2021-02-27 15:45 ` Jonathan Cameron
2021-02-18 13:38 ` 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=20210218133804.60d7eca7@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=dragos.bogdan@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox