From: Hsia-Jun Li <randy.li@synaptics.com>
To: linux-media@vger.kernel.org
Cc: ayaka@soulik.info, hans.verkuil@cisco.com, tfiga@chromium.org,
mchehab@kernel.org, laurent.pinchart@ideasonboard.com,
hiroh@chromium.org, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, nicolas@ndufresne.ca
Subject: [PATCH 1/2] [RESEND] media: v4l2-mem2mem: allow device run without buf
Date: Tue, 4 Jul 2023 12:00:37 +0800 [thread overview]
Message-ID: <20230704040044.681850-2-randy.li@synaptics.com> (raw)
In-Reply-To: <20230704040044.681850-1-randy.li@synaptics.com>
From: Randy Li <ayaka@soulik.info>
For the decoder supports Dynamic Resolution Change,
we don't need to allocate any CAPTURE or graphics buffer
for them at inital CAPTURE setup step.
We need to make the device run or we can't get those
metadata.
Signed-off-by: Randy Li <ayaka@soulik.info>
---
drivers/media/v4l2-core/v4l2-mem2mem.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-mem2mem.c b/drivers/media/v4l2-core/v4l2-mem2mem.c
index 0cc30397fbad..c771aba42015 100644
--- a/drivers/media/v4l2-core/v4l2-mem2mem.c
+++ b/drivers/media/v4l2-core/v4l2-mem2mem.c
@@ -301,8 +301,9 @@ static void __v4l2_m2m_try_queue(struct v4l2_m2m_dev *m2m_dev,
dprintk("Trying to schedule a job for m2m_ctx: %p\n", m2m_ctx);
- if (!m2m_ctx->out_q_ctx.q.streaming
- || !m2m_ctx->cap_q_ctx.q.streaming) {
+ if (!(m2m_ctx->out_q_ctx.q.streaming || m2m_ctx->out_q_ctx.buffered)
+ || !(m2m_ctx->cap_q_ctx.q.streaming
+ || m2m_ctx->cap_q_ctx.buffered)) {
dprintk("Streaming needs to be on for both queues\n");
return;
}
--
2.17.1
next prev parent reply other threads:[~2023-07-04 4:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 4:00 [PATCH 0/2] Improve V4L2 M2M job scheduler Hsia-Jun Li
2023-07-04 4:00 ` Hsia-Jun Li [this message]
2023-07-07 19:14 ` [PATCH 1/2] [RESEND] media: v4l2-mem2mem: allow device run without buf Nicolas Dufresne
2023-07-12 9:31 ` Tomasz Figa
2023-07-12 9:44 ` Sebastian Fricke
2023-07-13 3:13 ` Tomasz Figa
2023-07-17 14:00 ` Nicolas Dufresne
2023-07-21 8:56 ` Hsia-Jun Li
2023-07-21 16:22 ` Nicolas Dufresne
2023-07-24 17:29 ` Randy Li
2023-07-04 4:00 ` [PATCH 2/2] media: v4l2-mem2mem: add a list for buf used by hw Hsia-Jun Li
2023-07-07 19:20 ` Nicolas Dufresne
2023-07-11 8:54 ` Randy Li
2023-07-11 6:26 ` Dan Carpenter
2023-07-12 9:33 ` Tomasz Figa
2023-07-17 7:14 ` Hsia-Jun Li
2023-07-27 7:25 ` Tomasz Figa
2023-07-27 7:33 ` Hsia-Jun Li
2023-07-27 7:54 ` Tomasz Figa
2023-07-17 14:07 ` Nicolas Dufresne
2023-07-18 3:53 ` Hsia-Jun Li
2023-07-27 7:43 ` Tomasz Figa
2023-07-27 16:58 ` Nicolas Dufresne
2023-07-28 4:43 ` Tomasz Figa
2023-07-28 7:08 ` Hsia-Jun Li
2023-07-28 7:26 ` Tomasz Figa
2023-07-28 7:37 ` Hsia-Jun Li
2023-07-28 16:19 ` Nicolas Dufresne
2023-08-03 16:16 ` Randy Li
2023-08-04 20:42 ` Nicolas Dufresne
2023-07-28 16:09 ` Nicolas Dufresne
2023-08-18 14:45 ` [PATCH 0/2] Improve V4L2 M2M job scheduler Hans Verkuil
2023-08-22 7:59 ` Tomasz Figa
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=20230704040044.681850-2-randy.li@synaptics.com \
--to=randy.li@synaptics.com \
--cc=ayaka@soulik.info \
--cc=hans.verkuil@cisco.com \
--cc=hiroh@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=tfiga@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