devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Nas Chung <nas.chung@chipsnmedia.com>,
	mchehab@kernel.org, hverkuil@xs4all.nl,
	sebastian.fricke@collabora.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	jackson.lee@chipsnmedia.com, lafley.kim@chipsnmedia.com
Subject: Re: [PATCH v2 0/8] Add support for Wave6 video codec driver
Date: Wed, 3 Sep 2025 23:47:09 +0200	[thread overview]
Message-ID: <f03d0ae0-d28b-4b06-8f63-9d06f15c0522@mailbox.org> (raw)
In-Reply-To: <20250422093119.595-1-nas.chung@chipsnmedia.com>

On 4/22/25 11:31 AM, Nas Chung wrote:
> This patch series introduces support for the Chips&Media Wave6 video
> codec IP, a completely different hardware architecture compared to Wave5.
> 
> The wave6 driver is a M2M stateful encoder/decoder driver.
> It supports various video formats, including H.264 and H.265,
> for both encoding and decoding.
> While other versions of the Wave6 IP may support VP9 decoding and
> AV1 decoding and encoding those formats are not implemented or validated
> in this driver at this time.
> 
> On NXP i.MX SoCs, the Wave6 IP functionality is split between two regions:
> VPU Control region, Manages shared resources such as firmware memory.
> VPU Core region, Provides encoding and decoding capabilities.
> The VPU core cannot operate independently without the VPU control region.
> 
> This driver has been tested with GStreamer on:
> - NXP i.MX95 board
> - pre-silicon FPGA environment
> 
> Test results for decoder fluster:
> - JVT-AVC_V1, Ran 77/135 tests successfully              in 35.519 secs
> - JVT-FR-EXT, Ran 25/69 tests successfully               in 17.725 secs
> - JCT-VC-HEVC_V1, Ran 132/147 tests successfully         in 81.549 secs
> - All failures are due to unsupported hardware features:
> -- 10bit, Resolutions higher than 4K, FMO, MBAFF
> -- Extended profile, Field encoding and High422 sreams.
> 
> Test results for v4l2-compliance:
> v4l2-compliance 1.29.0-5359, 64 bits, 64-bit time_t
> v4l2-compliance SHA: 2a91a869eb8a 2025-04-12 11:35:53
> 
> Compliance test for wave6-dec device /dev/video0:
>                  fail: ../utils/v4l2-compliance/v4l2-test-controls.cpp(1180): !have_source_change || !have_eos
>          test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: FAIL
> Total for wave6-dec device /dev/video0: 48, Succeeded: 47, Failed: 1, Warnings: 0
> 
> Compliance test for wave6-enc device /dev/video1:
>                  fail: ../utils/v4l2-compliance/v4l2-test-controls.cpp(1169): node->codec_mask & STATEFUL_ENCODER
>          test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: FAIL
> Total for wave6-enc device /dev/video1: 48, Succeeded: 47, Failed: 1, Warnings: 0
> 
> Note: the failures are all related with the eos event.

For what its worth, the whole series:

Tested-by: Marek Vasut <marek.vasut@mailbox.org> # NXP i.MX95 rev. A0

  parent reply	other threads:[~2025-09-03 21:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  9:31 [PATCH v2 0/8] Add support for Wave6 video codec driver Nas Chung
2025-04-22  9:31 ` [PATCH v2 1/8] media: v4l2-common: Add YUV24 format info Nas Chung
2025-04-24 15:43   ` Nicolas Dufresne
2025-04-22  9:31 ` [PATCH v2 2/8] dt-bindings: media: nxp: Add Wave6 video codec device Nas Chung
2025-04-25 10:34   ` Krzysztof Kozlowski
2025-05-09  9:59     ` Nas Chung
2025-05-09 10:11       ` Krzysztof Kozlowski
2025-05-13  7:39         ` Nas Chung
2025-05-16 12:55           ` Krzysztof Kozlowski
2025-05-19  5:08             ` Nas Chung
2025-05-20  6:27               ` Krzysztof Kozlowski
2025-05-20  8:31                 ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 3/8] media: chips-media: wave6: Add Wave6 driver Nas Chung
2025-04-24 17:36   ` Nicolas Dufresne
2025-05-14  8:09     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 4/8] media: chips-media: wave6: Add Wave6 control driver Nas Chung
2025-04-29 20:47   ` Nicolas Dufresne
2025-05-14 10:15     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 5/8] media: chips-media: wave6: Add Wave6 VPU interface Nas Chung
2025-05-01 17:42   ` Nicolas Dufresne
2025-05-16  8:08     ` Nas Chung
2025-04-22  9:31 ` [PATCH v2 6/8] media: chips-media: wave6: Improve debugging capabilities Nas Chung
2025-04-22  9:31 ` [PATCH v2 7/8] media: chips-media: wave6: Add v4l2 m2m driver support Nas Chung
2025-04-22  9:31 ` [PATCH v2 8/8] media: chips-media: wave6: Add Wave6 core driver Nas Chung
2025-09-03 21:47 ` Marek Vasut [this message]
2025-09-04 13:25   ` [PATCH v2 0/8] Add support for Wave6 video codec driver Nicolas Dufresne
2025-09-04 15:32     ` Marek Vasut
2025-09-04 15:54       ` Nicolas Dufresne
2025-09-05  1:22         ` [EXT] " Ming Qian
2025-09-06 21:32         ` Marek Vasut

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=f03d0ae0-d28b-4b06-8f63-9d06f15c0522@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=krzk+dt@kernel.org \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=robh@kernel.org \
    --cc=sebastian.fricke@collabora.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;
as well as URLs for NNTP newsgroup(s).