From: Tomasz Figa <tfiga@chromium.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Yunke Cao <yunkec@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 0/3] media: videobuf2-core: attach once if multiple planes share the same dbuf
Date: Thu, 9 May 2024 01:02:48 +0900 [thread overview]
Message-ID: <CAAFQd5DOBwDAYr=EnLBEJOeMdqQhLkd+4gJ3BFZGw5jvHGvO2g@mail.gmail.com> (raw)
In-Reply-To: <863b76d9-a463-4bdb-a808-77d7b77c1722@xs4all.nl>
On Wed, Apr 24, 2024 at 7:25 PM Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
> Tomasz,
>
> I would appreciate it if you can review this series.
Sorry, I've been out for the last 2 weeks. Catching up now and should
get to this shortly.
Best,
Tomasz
>
> Regards,
>
> Hans
>
> On 03/04/2024 11:13, Yunke Cao wrote:
> > Hi,
> >
> > This patch set avoids attaching and mapping a dma_buf multiple times when
> > several planes in one vb2 buffer share the same dma_buf.
> >
> > 1/3 and 2/3 refactors __prepare_dmabuf()
> > 3/3 adds a flag to avoid duplicated attaching
> >
> > Changelog since v1:
> > - Add patch 1/3 to refactor __prepare_dmabuf()
> > - Add patch 2/3 to resolve Tomasz's comment on __vb2_buf_dmabuf_put()'s
> > iteration order
> > - Fix mem_priv in patch 3/3
> > - Rename duplicated_dbuf to dbuf_duplicated
> >
> > Yunke Cao (3):
> > media: videobuf2-core: release all planes first in __prepare_dmabuf()
> > media: videobuf2-core: reverse the iteration order in
> > __vb2_buf_dmabuf_put
> > media: videobuf2-core: attach once if multiple planes share the same
> > dbuf
> >
> > .../media/common/videobuf2/videobuf2-core.c | 97 +++++++++++--------
> > include/media/videobuf2-core.h | 3 +
> > 2 files changed, 62 insertions(+), 38 deletions(-)
> >
>
prev parent reply other threads:[~2024-05-08 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:13 [PATCH v2 0/3] media: videobuf2-core: attach once if multiple planes share the same dbuf Yunke Cao
2024-04-03 9:13 ` [PATCH v2 1/3] media: videobuf2-core: release all planes first in __prepare_dmabuf() Yunke Cao
2024-05-17 11:11 ` Tomasz Figa
2024-04-03 9:13 ` [PATCH v2 2/3] media: videobuf2-core: reverse the iteration order in __vb2_buf_dmabuf_put Yunke Cao
2024-04-24 10:24 ` Hans Verkuil
2024-05-17 11:14 ` Tomasz Figa
2024-04-03 9:13 ` [PATCH v2 3/3] media: videobuf2-core: attach once if multiple planes share the same dbuf Yunke Cao
2024-05-17 11:23 ` Tomasz Figa
2024-05-20 2:19 ` Yunke Cao
2024-04-24 10:25 ` [PATCH v2 0/3] " Hans Verkuil
2024-05-08 16:02 ` Tomasz Figa [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='CAAFQd5DOBwDAYr=EnLBEJOeMdqQhLkd+4gJ3BFZGw5jvHGvO2g@mail.gmail.com' \
--to=tfiga@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=yunkec@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).