From: Jonathan Cameron <jic23@kernel.org> To: Paul Cercueil <paul@crapouillou.net> Cc: "Lars-Peter Clausen" <lars@metafoo.de>, "Vinod Koul" <vkoul@kernel.org>, "Michael Hennerich" <Michael.Hennerich@analog.com>, "Nuno Sá" <noname.nuno@gmail.com>, "Sumit Semwal" <sumit.semwal@linaro.org>, "Christian König" <christian.koenig@amd.com>, linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, linux-iio@vger.kernel.org, linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, "Alexandru Ardelean" <ardeleanalex@gmail.com> Subject: Re: [PATCH v3 06/11] iio: buffer-dmaengine: Enable write support Date: Sun, 16 Apr 2023 15:37:04 +0100 [thread overview] Message-ID: <20230416153704.35f5ff4d@jic23-huawei> (raw) In-Reply-To: <20230403154800.215924-7-paul@crapouillou.net> On Mon, 3 Apr 2023 17:47:55 +0200 Paul Cercueil <paul@crapouillou.net> wrote: > Use the iio_dma_buffer_write() and iio_dma_buffer_space_available() > functions provided by the buffer-dma core, to enable write support in > the buffer-dmaengine code. > > Signed-off-by: Paul Cercueil <paul@crapouillou.net> > Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com> > --- > drivers/iio/buffer/industrialio-buffer-dmaengine.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/iio/buffer/industrialio-buffer-dmaengine.c b/drivers/iio/buffer/industrialio-buffer-dmaengine.c > index 592d2aa9044c..866c8b84bb24 100644 > --- a/drivers/iio/buffer/industrialio-buffer-dmaengine.c > +++ b/drivers/iio/buffer/industrialio-buffer-dmaengine.c > @@ -123,12 +123,14 @@ static void iio_dmaengine_buffer_release(struct iio_buffer *buf) > > static const struct iio_buffer_access_funcs iio_dmaengine_buffer_ops = { > .read = iio_dma_buffer_read, > + .write = iio_dma_buffer_write, > .set_bytes_per_datum = iio_dma_buffer_set_bytes_per_datum, > .set_length = iio_dma_buffer_set_length, > .request_update = iio_dma_buffer_request_update, > .enable = iio_dma_buffer_enable, > .disable = iio_dma_buffer_disable, > .data_available = iio_dma_buffer_data_available, > + .space_available = iio_dma_buffer_space_available, Follow through from earlier patch. I would prefer it to be obvious hers that the two callbacks above are identical. Easiest way to expose that detail is to set the callbacks to the same function, but then it perhaps needs a rename so it isn't specific to one of the other. Jonathan > .release = iio_dmaengine_buffer_release, > > .modes = INDIO_BUFFER_HARDWARE,
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <jic23@kernel.org> To: Paul Cercueil <paul@crapouillou.net> Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, "Sumit Semwal" <sumit.semwal@linaro.org>, linaro-mm-sig@lists.linaro.org, "Alexandru Ardelean" <ardeleanalex@gmail.com>, "Vinod Koul" <vkoul@kernel.org>, "Nuno Sá" <noname.nuno@gmail.com>, dmaengine@vger.kernel.org, "Christian König" <christian.koenig@amd.com>, linux-media@vger.kernel.org Subject: Re: [PATCH v3 06/11] iio: buffer-dmaengine: Enable write support Date: Sun, 16 Apr 2023 15:37:04 +0100 [thread overview] Message-ID: <20230416153704.35f5ff4d@jic23-huawei> (raw) In-Reply-To: <20230403154800.215924-7-paul@crapouillou.net> On Mon, 3 Apr 2023 17:47:55 +0200 Paul Cercueil <paul@crapouillou.net> wrote: > Use the iio_dma_buffer_write() and iio_dma_buffer_space_available() > functions provided by the buffer-dma core, to enable write support in > the buffer-dmaengine code. > > Signed-off-by: Paul Cercueil <paul@crapouillou.net> > Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com> > --- > drivers/iio/buffer/industrialio-buffer-dmaengine.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/iio/buffer/industrialio-buffer-dmaengine.c b/drivers/iio/buffer/industrialio-buffer-dmaengine.c > index 592d2aa9044c..866c8b84bb24 100644 > --- a/drivers/iio/buffer/industrialio-buffer-dmaengine.c > +++ b/drivers/iio/buffer/industrialio-buffer-dmaengine.c > @@ -123,12 +123,14 @@ static void iio_dmaengine_buffer_release(struct iio_buffer *buf) > > static const struct iio_buffer_access_funcs iio_dmaengine_buffer_ops = { > .read = iio_dma_buffer_read, > + .write = iio_dma_buffer_write, > .set_bytes_per_datum = iio_dma_buffer_set_bytes_per_datum, > .set_length = iio_dma_buffer_set_length, > .request_update = iio_dma_buffer_request_update, > .enable = iio_dma_buffer_enable, > .disable = iio_dma_buffer_disable, > .data_available = iio_dma_buffer_data_available, > + .space_available = iio_dma_buffer_space_available, Follow through from earlier patch. I would prefer it to be obvious hers that the two callbacks above are identical. Easiest way to expose that detail is to set the callbacks to the same function, but then it perhaps needs a rename so it isn't specific to one of the other. Jonathan > .release = iio_dmaengine_buffer_release, > > .modes = INDIO_BUFFER_HARDWARE,
next prev parent reply other threads:[~2023-04-16 14:37 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-03 15:47 [PATCH v3 00/11] iio: new DMABUF based API, v3 Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-03 15:47 ` [PATCH v3 01/11] dmaengine: Add API function dmaengine_prep_slave_dma_array() Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-04 1:59 ` Hillf Danton 2023-04-04 7:42 ` Paul Cercueil 2023-04-04 7:42 ` Paul Cercueil 2023-04-04 8:54 ` Christian König 2023-04-04 8:54 ` Christian König 2023-04-12 17:23 ` Vinod Koul 2023-04-12 17:23 ` Vinod Koul 2023-04-13 7:59 ` Paul Cercueil 2023-04-13 7:59 ` Paul Cercueil 2023-04-03 15:47 ` [PATCH v3 02/11] dmaengine: dma-axi-dmac: Implement device_prep_slave_dma_array Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-03 15:47 ` [PATCH v3 03/11] iio: buffer-dma: Get rid of outgoing queue Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-16 14:24 ` Jonathan Cameron 2023-04-16 14:24 ` Jonathan Cameron 2023-04-18 8:08 ` Paul Cercueil 2023-04-18 8:08 ` Paul Cercueil 2023-05-01 16:25 ` Jonathan Cameron 2023-05-01 16:25 ` Jonathan Cameron 2023-04-03 15:47 ` [PATCH v3 04/11] iio: buffer-dma: Enable buffer write support Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-16 14:30 ` Jonathan Cameron 2023-04-16 14:30 ` Jonathan Cameron 2023-04-03 15:47 ` [PATCH v3 05/11] iio: buffer-dmaengine: Support specifying buffer direction Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-16 14:35 ` Jonathan Cameron 2023-04-16 14:35 ` Jonathan Cameron 2023-04-03 15:47 ` [PATCH v3 06/11] iio: buffer-dmaengine: Enable write support Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-16 14:37 ` Jonathan Cameron [this message] 2023-04-16 14:37 ` Jonathan Cameron 2023-04-03 15:47 ` [PATCH v3 07/11] iio: core: Add new DMABUF interface infrastructure Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-04 7:32 ` Nuno Sá 2023-04-04 7:55 ` Paul Cercueil 2023-04-04 8:21 ` Nuno Sá 2023-04-04 13:22 ` Lars-Peter Clausen 2023-04-16 15:04 ` Jonathan Cameron 2023-04-16 15:04 ` Jonathan Cameron 2023-04-03 15:47 ` [PATCH v3 08/11] iio: buffer-dma: split iio_dma_buffer_fileio_free() function Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-03 15:47 ` [PATCH v3 09/11] iio: buffer-dma: Enable support for DMABUFs Paul Cercueil 2023-04-03 15:47 ` Paul Cercueil 2023-04-16 15:10 ` Jonathan Cameron 2023-04-16 15:10 ` Jonathan Cameron 2023-04-03 15:49 ` [PATCH v3 10/11] iio: buffer-dmaengine: Support new DMABUF based userspace API Paul Cercueil 2023-04-03 15:49 ` Paul Cercueil 2023-04-03 15:49 ` [PATCH v3 11/11] Documentation: iio: Document high-speed DMABUF based API Paul Cercueil 2023-04-03 15:49 ` Paul Cercueil 2023-04-03 16:05 ` Jonathan Corbet 2023-04-03 16:05 ` Jonathan Corbet 2023-04-03 18:37 ` Paul Cercueil 2023-04-03 18:37 ` Paul Cercueil 2023-04-16 15:15 ` [PATCH v3 10/11] iio: buffer-dmaengine: Support new DMABUF based userspace API Jonathan Cameron 2023-04-16 15:15 ` Jonathan Cameron 2023-04-04 7:44 ` [PATCH v3 00/11] iio: new DMABUF based API, v3 Nuno Sá
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=20230416153704.35f5ff4d@jic23-huawei \ --to=jic23@kernel.org \ --cc=Michael.Hennerich@analog.com \ --cc=ardeleanalex@gmail.com \ --cc=christian.koenig@amd.com \ --cc=dmaengine@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=lars@metafoo.de \ --cc=linaro-mm-sig@lists.linaro.org \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=noname.nuno@gmail.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: linkBe 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.