From: Bin Du <Bin.Du@amd.com>
To: Seifelden Abdelmonem <saif.elden.hatim@gmail.com>,
Nirujogi Pratap <pratap.nirujogi@amd.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Sultan Alsawaf <sultan@kerneltoast.com>,
Svetoslav Stoilov <Svetoslav.Stoilov@amd.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, "Chan,
Benjamin (Koon Pan)" <Benjamin.Chan@amd.com>,
"Li, King" <King.Li@amd.com>
Subject: Re: [PATCH 2/2] media: amd: isp4: return capture buffers with V4L2_FIELD_NONE
Date: Tue, 27 Oct 2026 16:51:50 +0800 [thread overview]
Message-ID: <71ecb260-ce13-4107-8c97-7d1d75899b48@amd.com> (raw)
In-Reply-To: <20261026182442.229869-3-saif.elden.hatim@gmail.com>
Reviewed-by: Bin Du <bin.du@amd.com>
On 10/27/2026 2:24 AM, Seifelden Abdelmonem wrote:
>
> isp4vid_handle_frame_done() marks every completed buffer as
> V4L2_FIELD_ANY. V4L2_FIELD_ANY is only valid as a request from the
> application; a dequeued buffer must report the field order of the
> image it contains. v4l2-compliance therefore fails the first MMAP
> streaming test:
>
> fail: v4l2-test-buffers.cpp(419): g_field() == V4L2_FIELD_ANY
> fail: v4l2-test-buffers.cpp(1280): buf.check(q, last_seq)
> fail: v4l2-test-buffers.cpp(1735): captureBufs(...)
> test MMAP (no poll, REQBUFS): FAIL
>
> The ISP only produces progressive frames, and the format ioctls already
> report V4L2_FIELD_NONE (isp4vid_fmt_default). Use V4L2_FIELD_NONE for
> the returned buffers as well. With this change that test passes.
>
> Fixes: 2ccf48af2270 ("media: platform: amd: isp4 video node and buffers handling added")
> Signed-off-by: Seifelden Abdelmonem <saif.elden.hatim@gmail.com>
> ---
> Testing and AI use: see the cover letter.
>
> drivers/media/platform/amd/isp4/isp4_video.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/amd/isp4/isp4_video.c b/drivers/media/platform/amd/isp4/isp4_video.c
> index 58ea8d6ac..b8af3c766 100644
> --- a/drivers/media/platform/amd/isp4/isp4_video.c
> +++ b/drivers/media/platform/amd/isp4/isp4_video.c
> @@ -72,7 +72,7 @@ void isp4vid_handle_frame_done(struct isp4vid_dev *isp_vdev,
> /* Fill the buffer */
> isp4vid_buf->vb2.vb2_buf.timestamp = ktime_get_ns();
> isp4vid_buf->vb2.sequence = isp_vdev->sequence++;
> - isp4vid_buf->vb2.field = V4L2_FIELD_ANY;
> + isp4vid_buf->vb2.field = V4L2_FIELD_NONE;
>
> vb2_set_plane_payload(&isp4vid_buf->vb2.vb2_buf,
> 0, isp_vdev->format.sizeimage);
> --
> 2.56.0
prev parent reply other threads:[~2026-10-27 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 18:24 [PATCH 0/2] media: amd: isp4: two fixes found on the ROG Flow Z13 Seifelden Abdelmonem
2026-10-26 18:24 ` [PATCH 1/2] media: amd: isp4: hold buf_list_lock while sending buffers at stream start Seifelden Abdelmonem
2026-10-27 8:51 ` Bin Du
2026-10-26 18:24 ` [PATCH 2/2] media: amd: isp4: return capture buffers with V4L2_FIELD_NONE Seifelden Abdelmonem
2026-10-27 8:51 ` Bin Du [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=71ecb260-ce13-4107-8c97-7d1d75899b48@amd.com \
--to=bin.du@amd.com \
--cc=Benjamin.Chan@amd.com \
--cc=King.Li@amd.com \
--cc=Svetoslav.Stoilov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pratap.nirujogi@amd.com \
--cc=saif.elden.hatim@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sultan@kerneltoast.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®