From: Jonathan Cameron <jic23@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Vinod Koul" <vkoul@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Nuno Sa" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v10 4/6] iio: buffer-dma: Enable support for DMABUFs
Date: Sun, 9 Jun 2024 10:55:01 +0100 [thread overview]
Message-ID: <20240609105501.0f836684@jic23-huawei> (raw)
In-Reply-To: <20240605110845.86740-5-paul@crapouillou.net>
On Wed, 5 Jun 2024 13:08:43 +0200
Paul Cercueil <paul@crapouillou.net> wrote:
> Implement iio_dma_buffer_attach_dmabuf(), iio_dma_buffer_detach_dmabuf()
> and iio_dma_buffer_transfer_dmabuf(), which can then be used by the IIO
> DMA buffer implementations.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
>
Same thing on SoB.
Also another missing structure field related docs comment inline.
> diff --git a/include/linux/iio/buffer-dma.h b/include/linux/iio/buffer-dma.h
> index 6e27e47077d5..e54158e53fd6 100644
> --- a/include/linux/iio/buffer-dma.h
> +++ b/include/linux/iio/buffer-dma.h
> @@ -7,6 +7,7 @@
> #ifndef __INDUSTRIALIO_DMA_BUFFER_H__
> #define __INDUSTRIALIO_DMA_BUFFER_H__
>
> +#include <linux/atomic.h>
> #include <linux/list.h>
> #include <linux/kref.h>
> #include <linux/spinlock.h>
> @@ -16,6 +17,9 @@
> struct iio_dma_buffer_queue;
> struct iio_dma_buffer_ops;
> struct device;
> +struct dma_buf_attachment;
> +struct dma_fence;
> +struct sg_table;
>
> /**
> * enum iio_block_state - State of a struct iio_dma_buffer_block
> @@ -41,6 +45,8 @@ enum iio_block_state {
> * @queue: Parent DMA buffer queue
> * @kref: kref used to manage the lifetime of block
> * @state: Current state of the block
> + * @cyclic: True if this is a cyclic buffer
> + * @fileio: True if this buffer is used for fileio mode
kernel doc needs to be complete. So missing attach, sg_table and fence.
> */
> struct iio_dma_buffer_block {
> /* May only be accessed by the owner of the block */
> @@ -63,6 +69,14 @@ struct iio_dma_buffer_block {
> * queue->list_lock if the block is not owned by the core.
> */
> enum iio_block_state state;
> +
> + bool cyclic;
> + bool fileio;
> +
> + struct dma_buf_attachment *attach;
> + struct sg_table *sg_table;
> +
> + struct dma_fence *fence;
> };
next prev parent reply other threads:[~2024-06-09 9:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 11:08 [PATCH v10 0/6] iio: new DMABUF based API v10 Paul Cercueil
2024-06-05 11:08 ` [PATCH v10 1/6] dmaengine: Add API function dmaengine_prep_peripheral_dma_vec() Paul Cercueil
2024-06-11 16:29 ` Vinod Koul
2024-06-05 11:08 ` [PATCH v10 2/6] dmaengine: dma-axi-dmac: Implement device_prep_peripheral_dma_vec Paul Cercueil
2024-06-05 11:08 ` [PATCH v10 3/6] iio: core: Add new DMABUF interface infrastructure Paul Cercueil
2024-06-09 9:53 ` Jonathan Cameron
2024-06-15 11:07 ` Paul Cercueil
2024-06-17 6:24 ` Nuno Sá
2024-06-17 6:56 ` Markus Elfring
2024-06-18 9:25 ` Paul Cercueil
2024-06-05 11:08 ` [PATCH v10 4/6] iio: buffer-dma: Enable support for DMABUFs Paul Cercueil
2024-06-09 9:55 ` Jonathan Cameron [this message]
2024-06-05 11:08 ` [PATCH v10 5/6] iio: buffer-dmaengine: Support new DMABUF based userspace API Paul Cercueil
2024-06-05 11:08 ` [PATCH v10 6/6] Documentation: iio: Document high-speed DMABUF based API Paul Cercueil
2024-06-06 17:32 ` Randy Dunlap
2024-06-07 7:44 ` Paul Cercueil
2024-06-08 23:44 ` Randy Dunlap
2024-06-09 9:58 ` [PATCH v10 0/6] iio: new DMABUF based API v10 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=20240609105501.0f836684@jic23-huawei \
--to=jic23@kernel.org \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lars@metafoo.de \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=paul@crapouillou.net \
--cc=sumit.semwal@linaro.org \
--cc=vkoul@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.