From: Thierry Escande <thierry.escande@collabora.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Pawel Osciak <pawel@osciak.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: [PATCH 0/2] [media] DMA direction support in vb2_queue
Date: Wed, 19 Oct 2016 10:24:15 +0200 [thread overview]
Message-ID: <1476865457-506-1-git-send-email-thierry.escande@collabora.com> (raw)
Hi,
This series adds a dma_dir field to the vb2_queue structure in order to
store the DMA direction once for all in vb2_queue_init();
It also adds a new capture_dma_bidirectional flag to the vb2_queue
structure allowing the hardware to read from the CAPTURE buffer. This
flag is ignored for OUTPUT queues. This is used on ChromeOS by the
rockchip-vpu driver.
Changes since v1:
- Renamed use_dma_bidirectional field as capture_dma_bidirectional
- Added a VB2_DMA_DIR() macro
Pawel Osciak (2):
[media] vb2: Store dma_dir in vb2_queue
[media] vb2: Add support for capture_dma_bidirectional queue flag
drivers/media/v4l2-core/videobuf2-core.c | 12 +++---------
drivers/media/v4l2-core/videobuf2-v4l2.c | 6 ++++++
include/media/videobuf2-core.h | 6 ++++++
3 files changed, 15 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-19 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 8:24 Thierry Escande [this message]
2016-10-19 8:24 ` [PATCH 1/2] [media] vb2: Store dma_dir " Thierry Escande
2016-10-19 21:29 ` Sakari Ailus
2016-10-20 8:20 ` Thierry Escande
2016-10-19 8:24 ` [PATCH 2/2] [media] vb2: Add support for capture_dma_bidirectional queue flag Thierry Escande
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 12:08 [PATCH 0/2] [media] DMA direction support in vb2_queue Thierry Escande
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=1476865457-506-1-git-send-email-thierry.escande@collabora.com \
--to=thierry.escande@collabora.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.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
all inboxes | Powered by JetHome®