linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 02/12] docs: driver-api: add iio hw consumer section
Date: Sun, 19 Nov 2017 12:31:15 +0000	[thread overview]
Message-ID: <20171119123115.06eb6d63@archlinux> (raw)
In-Reply-To: <1510222354-15290-3-git-send-email-arnaud.pouliquen@st.com>

On Thu, 9 Nov 2017 11:12:24 +0100
Arnaud Pouliquen <arnaud.pouliquen@st.com> wrote:

> This adds a section about the Hardware consumer
> Api of the IIO subsystem to the driver API
> documentation.
> 
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>

Good little bit of docs.  A couple of minor formatting
comments inline.

Jonathan

> ---
>  Documentation/driver-api/iio/hw-consumer.rst | 50 ++++++++++++++++++++++++++++
>  Documentation/driver-api/iio/index.rst       |  1 +
>  2 files changed, 51 insertions(+)
>  create mode 100644 Documentation/driver-api/iio/hw-consumer.rst
> 
> diff --git a/Documentation/driver-api/iio/hw-consumer.rst b/Documentation/driver-api/iio/hw-consumer.rst
> new file mode 100644
> index 0000000..b777133
> --- /dev/null
> +++ b/Documentation/driver-api/iio/hw-consumer.rst
> @@ -0,0 +1,50 @@
> +===========
> +HW consumer
> +===========
> +An IIO device can be directly connected to another device in hardware. in this
> +case the buffers between IIO provider and IIO consumer are handled by hardware.
> +The Industrial I/O hw consumer offers a way to bond these IIO devices without
> +software buffer for data. The implementation can be found under
> +:file:`drivers/iio/buffer/hw-consumer.c`
> +
> +
> +* struct :c:type:`iio_hw_consumer` ? Hardware consumer structure
> +* :c:func:`iio_hw_consumer_alloc` ? Allocate IIO hardware consumer
> +* :c:func:`iio_hw_consumer_free` ? Free IIO hardware consumer
> +* :c:func:`iio_hw_consumer_enable` ? Enable IIO hardware consumer
> +* :c:func:`iio_hw_consumer_disable` ? Disable IIO hardware consumer
> +
> +
> +HW consumer setup
> +=================
> +
> +As standard IIO device the implementation is based on IIO provider/consumer.
> +A typical IIO Hw conumer setup looks like this::

HW

> +
> +	static struct iio_hw_consumer *hwc;
> +
> +	static const struct iio_info adc_info = {
> +		.read_raw = adc_read_raw,
> +	};
> +
> +	static int adc_read_raw(struct iio_dev *indio_dev,
> +				struct iio_chan_spec const *chan, int *val,
> +				int *val2, long mask)
> +	{
> +		ret = iio_hw_consumer_enable(hwc);
> +
> +		/* Acquire data */

Blank line here to make it clear the Acquire data doesn't apply to
the line below but is representing a missing block.

> +		ret = iio_hw_consumer_disable(hwc);
> +	}
> +
> +	static int adc_probe(struct platform_device *pdev)
> +	{
> +		hwc = devm_iio_hw_consumer_alloc(&iio->dev);
> +	}
> +
> +More details
> +============
> +.. kernel-doc:: include/linux/iio/hw-consumer.h
> +.. kernel-doc:: drivers/iio/buffer/industrialio-hw-consumer.c
> +   :export:
> +
> diff --git a/Documentation/driver-api/iio/index.rst b/Documentation/driver-api/iio/index.rst
> index e5c3922..7fba341 100644
> --- a/Documentation/driver-api/iio/index.rst
> +++ b/Documentation/driver-api/iio/index.rst
> @@ -15,3 +15,4 @@ Contents:
>     buffers
>     triggers
>     triggered-buffers
> +   hw-consumer

  reply	other threads:[~2017-11-19 12:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 10:12 [PATCH v4 00/12] Add STM32 DFSDM support Arnaud Pouliquen
2017-11-09 10:12 ` [PATCH v4 01/12] iio: Add hardware consumer buffer support Arnaud Pouliquen
2017-11-19 12:32   ` Jonathan Cameron
2017-11-09 10:12 ` [PATCH v4 02/12] docs: driver-api: add iio hw consumer section Arnaud Pouliquen
2017-11-19 12:31   ` Jonathan Cameron [this message]
2017-11-09 10:12 ` [PATCH v4 03/12] IIO: hw_consumer: add devm_iio_hw_consumer_alloc Arnaud Pouliquen
2017-11-19 12:34   ` Jonathan Cameron
2017-11-24 14:48     ` Arnaud Pouliquen
2017-11-09 10:12 ` [PATCH v4 04/12] IIO: Add DT bindings for sigma delta adc modulator Arnaud Pouliquen
2018-01-10 11:13   ` Applied "IIO: Add DT bindings for sigma delta adc modulator" to the asoc tree Mark Brown
2017-11-09 10:12 ` [PATCH v4 05/12] IIO: ADC: add sigma delta modulator support Arnaud Pouliquen
2017-11-19 12:44   ` Jonathan Cameron
2017-11-09 10:12 ` [PATCH v4 06/12] IIO: add DT bindings for stm32 DFSDM filter Arnaud Pouliquen
2017-11-10 21:05   ` Rob Herring
2017-11-09 10:12 ` [PATCH v4 07/12] IIO: ADC: add stm32 DFSDM core support Arnaud Pouliquen
2017-11-19 12:54   ` Jonathan Cameron
2017-11-09 10:12 ` [PATCH v4 08/12] IIO: ADC: add STM32 DFSDM sigma delta ADC support Arnaud Pouliquen
2017-11-19 14:29   ` Jonathan Cameron
2017-11-24 14:49     ` Arnaud Pouliquen
2017-11-09 10:12 ` [PATCH v4 09/12] IIO: ADC: add stm32 DFSDM support for PDM microphone Arnaud Pouliquen
2017-11-19 14:18   ` Jonathan Cameron
2017-11-24 14:52     ` Arnaud Pouliquen
2017-11-25 14:36       ` Jonathan Cameron
2017-11-09 10:12 ` [PATCH v4 10/12] IIO: consumer: allow to set buffer sizes Arnaud Pouliquen
2017-11-19 14:19   ` Jonathan Cameron
2017-11-09 10:12 ` [PATCH v4 11/12] ASoC: add bindings for stm32 DFSDM filter Arnaud Pouliquen
2017-11-15 15:43   ` Rob Herring
2017-11-16 10:53     ` Arnaud Pouliquen
2017-11-09 10:12 ` [PATCH v4 12/12] ASoC: stm32: add DFSDM DAI support Arnaud Pouliquen

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=20171119123115.06eb6d63@archlinux \
    --to=jic23@kernel.org \
    --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).