mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brandon Brnich <b-brnich@ti.com>
To: Jackson.lee <jackson.lee@chipsnmedia.com>, <mchehab@kernel.org>,
	<hverkuil-cisco@xs4all.nl>, <nicolas.dufresne@collabora.com>,
	<bob.beckett@collabora.com>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lafley.kim@chipsnmedia.com>, <hverkuil@xs4all.nl>,
	<nas.chung@chipsnmedia.com>
Subject: Re: [PATCH v0 0/4] bug fixes
Date: Mon, 8 Jun 2026 09:16:10 -0500	[thread overview]
Message-ID: <06f8d2b9-89f3-4951-a001-9a89149ae315@ti.com> (raw)
In-Reply-To: <20260604020155.77-1-jackson.lee@chipsnmedia.com>

Hi Jackson,

On 6/3/26 21:01, Jackson.lee wrote:
> From: Jackson Lee <jackson.lee@chipsnmedia.com>
> 
> A few independent fixes for the Wave5 VPU driver, covering decode
> setup, m2m scheduling and stop_streaming robustness.

This series appears to fix some issues in v4l2-compliance report, can 
you add the updated report in the next iteration of this series to make 
sure everything is now fixed with latest v4l2-compliance tag?

Best,
Brandon

> 
> Jackson Lee (4):
>    media: chips-media: wave5: Guard bit depth check with
>      initial_info_obtained
>    media: chips-media: wave5: Set inst->std during default format
>      initialization
>    media: chips-media: wave5: avoid skipping device_run while VPU has
>      work
>    media: chips-media: wave5: Add interrupt timeout while stop_streaming
> 
>   .../chips-media/wave5/wave5-vpu-dec.c         | 20 +++++++++++++++----
>   .../chips-media/wave5/wave5-vpu-enc.c         |  6 ++++--
>   .../chips-media/wave5/wave5-vpuconfig.h       |  2 +-
>   3 files changed, 21 insertions(+), 7 deletions(-)
> 


  parent reply	other threads:[~2026-06-08 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  2:01 Jackson.lee
2026-06-04  2:01 ` [PATCH v0 1/4] media: chips-media: wave5: Guard bit depth check with initial_info_obtained Jackson.lee
2026-06-04  2:01 ` [PATCH v0 2/4] media: chips-media: wave5: Set inst->std during default format initialization Jackson.lee
2026-06-04  2:01 ` [PATCH v0 3/4] media: chips-media: wave5: avoid skipping device_run while VPU has work Jackson.lee
2026-06-04  2:01 ` [PATCH v0 4/4] media: chips-media: wave5: Add interrupt timeout while stop_streaming Jackson.lee
2026-06-08 14:16 ` Brandon Brnich [this message]
2026-06-09  0:31   ` [PATCH v0 0/4] bug fixes jackson.lee

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=06f8d2b9-89f3-4951-a001-9a89149ae315@ti.com \
    --to=b-brnich@ti.com \
    --cc=bob.beckett@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=nicolas.dufresne@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

all inboxes | Powered by JetHome®