From: jackson.lee <jackson.lee@chipsnmedia.com>
To: Brandon Brnich <b-brnich@ti.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"bob.beckett@collabora.com" <bob.beckett@collabora.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
lafley.kim <lafley.kim@chipsnmedia.com>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
Nas Chung <nas.chung@chipsnmedia.com>
Subject: RE: [PATCH v0 0/4] bug fixes
Date: Tue, 9 Jun 2026 00:31:08 +0000 [thread overview]
Message-ID: <SLXP216MB1148C7C5EBC8DBBC19AF9881ED1D2@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <06f8d2b9-89f3-4951-a001-9a89149ae315@ti.com>
Hi Brandon
> -----Original Message-----
> From: Brandon Brnich <b-brnich@ti.com>
> Sent: Monday, June 8, 2026 11:16 PM
> 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
> <lafley.kim@chipsnmedia.com>; hverkuil@xs4all.nl; Nas Chung
> <nas.chung@chipsnmedia.com>
> Subject: Re: [PATCH v0 0/4] bug fixes
>
> 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?
I'll add the test report in the next version of the patch series.
Thanks
>
> 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(-)
> >
prev parent reply other threads:[~2026-06-09 0:31 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 ` [PATCH v0 0/4] bug fixes Brandon Brnich
2026-06-09 0:31 ` jackson.lee [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=SLXP216MB1148C7C5EBC8DBBC19AF9881ED1D2@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM \
--to=jackson.lee@chipsnmedia.com \
--cc=b-brnich@ti.com \
--cc=bob.beckett@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--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®