From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>, linux-media@vger.kernel.org
Cc: mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
benjamin.gaignard@collabora.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, p.zabel@pengutronix.de,
sebastian.fricke@collabora.com, shawnguo@kernel.org,
ulf.hansson@linaro.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
l.stach@pengutronix.de, Frank.li@nxp.com, peng.fan@nxp.com,
eagle.zhou@nxp.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding
Date: Tue, 3 Feb 2026 15:13:21 +0800 [thread overview]
Message-ID: <ca3a8042-1394-4925-9c61-dbfcbf4cf7d9@oss.nxp.com> (raw)
In-Reply-To: <5e3431c69da07557edb20a252c4759be8c857f08.camel@ndufresne.ca>
Hi Nicolas,
On 2/3/2026 3:12 AM, Nicolas Dufresne wrote:
> Hi,
>
> Le lundi 02 février 2026 à 13:44 -0500, Nicolas Dufresne a écrit :
>>> This doesn't sound like just a VPU issue; it's related to the display or
>>> DDR.
>>> If not displayed, do the fluster test cases yield different results at
>>> 600MHz and 300MHz?
>>
>> Didn't you run these tests before sending ? I can try again, but in my
>> internal
>> notes, I wrote:
>>
>> > Tested that, and everything becomes unstable
>>
>> That was before I figure-out the IRQ handler didn't handle exception bits that
>> didn't stop the decoder (or dry IRQ, which strangely is common from the G2).
>
> Ran some fluster tests now. With this patch the results is not consistent
> anymore. Then I ran it with weston being started, and in the middle of the test
> the display turned black. Matches my past observation. We did reproduce this on
> BSP kernel too. When the display goes black, the recent hantro drivers reports:
>
> [ 827.581586] hantro-vpu 38310000.video-codec: frame decode timed out.
> [ 827.720201] hantro-vpu 38310000.video-codec: not all macroblocks were
> decoded.
>
>
> I have local patches to reduce the cascade of errors, so it likely survived
> longer then last time. I will send these patches soon. The "not all macroblocks
> were decoded." is triggered by a bit in the status register that is not
> documented in NXP TRM. I found that bit in some VC8000D documentation (the
> sucessor of G2). I concluded it was the same meaning after looking at the failed
> buffer visually, it is indeed missing couple of macroblocks near th end. Each
> time we see this error, the DCSS gives up and turn either black, or sometimes
> other color. The second case has been tracked to a DCSS Scaler underrun, the
> first we don't know.
>
> Fluster command ran (two threads, never completes):
>
> ./fluster.py run -d GStreamer-H.265-V4L2SL-Gst1.0 -ts JCT-VC-HEVC_V1 -j2 -t90
>
> Nicolas
My test results for fluster differ from yours.
On my end, the results for JCT-VC-HEVC_V1 are consistent at both 300MHz
and 600MHz.
And results remained unchanged after multiple tests.
I'm not sure what caused the differences between us.
Below are my test results:
600Mhz, 0.9v
cat /sys/kernel/debug/regulator/regulator_summary |grep SW1C
SW1C 0 1 0 unknown 900mV 0mA
825mV 1100mV
cat /sys/kernel/debug/clk/vpu_g2/clk_rate
600000000
./fluster.py run -ts JCT-VC-HEVC_V1 -d GStreamer-H.265-V4L2SL-Gst1.0
-j2 -t 90
****************************************************************************************************
Running test suite JCT-VC-HEVC_V1 with decoder
GStreamer-H.265-V4L2SL-Gst1.0
Using 2 parallel job(s)
****************************************************************************************************
Ran 139/147 tests successfully in 505.434 secs
Ran 139/147 tests successfully in 505.350 secs
Ran 139/147 tests successfully in 507.540 secs
600Mhz, 1.0v
cat /sys/kernel/debug/regulator/regulator_summary |grep SW1C
SW1C 0 1 0 unknown 1000mV 0mA
825mV 1100mV
cat /sys/kernel/debug/clk/vpu_g2/clk_rate
600000000
./fluster.py run -ts JCT-VC-HEVC_V1 -d GStreamer-H.265-V4L2SL-Gst1.0
-j2 -t 90
Ran 139/147 tests successfully in 506.901 secs
300Mhz, 0.9v
cat /sys/kernel/debug/regulator/regulator_summary |grep SW1C
SW1C 0 1 0 unknown 900mV 0mA
825mV 1100mV
cat /sys/kernel/debug/clk/vpu_g2/clk_rate
300000000
./fluster.py run -ts JCT-VC-HEVC_V1 -d GStreamer-H.265-V4L2SL-Gst1.0
-j2 -t 90
Ran 139/147 tests successfully in 506.063 secs
Downstream v4l2 driver
cat /sys/kernel/debug/regulator/regulator_summary |grep SW1C
SW1C 0 2 0 unknown 1000mV 0mA
825mV 1100mV
cat /sys/kernel/debug/clk/vpu_g2/clk_rate
600000000
./fluster.py run -ts JCT-VC-HEVC_V1 -d GStreamer-H.265-V4L2-Gst1.0 -j2
-t 90
Ran 136/147 tests successfully in 460.435 secs
Regards,
Ming
next prev parent reply other threads:[~2026-02-03 7:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 8:41 ming.qian
2026-01-30 9:09 ` Alexander Stein
2026-02-02 2:41 ` Peng Fan
2026-02-02 5:56 ` Ming Qian(OSS)
2026-01-30 14:47 ` Nicolas Dufresne
2026-02-02 7:44 ` Ming Qian(OSS)
2026-02-02 18:44 ` Nicolas Dufresne
2026-02-02 19:12 ` Nicolas Dufresne
2026-02-03 7:13 ` Ming Qian(OSS) [this message]
2026-02-03 8:31 ` Marco Felsch
2026-02-03 8:53 ` Ming Qian(OSS)
2026-02-03 15:40 ` Nicolas Dufresne
2026-02-04 2:13 ` Ming Qian(OSS)
2026-02-03 9:04 ` Lucas Stach
2026-02-03 9:33 ` Ming Qian(OSS)
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=ca3a8042-1394-4925-9c61-dbfcbf4cf7d9@oss.nxp.com \
--to=ming.qian@oss.nxp.com \
--cc=Frank.li@nxp.com \
--cc=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eagle.zhou@nxp.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.fricke@collabora.com \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®