public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, mchehab@kernel.org,
	hverkuil-cisco@xs4all.nl, nicolas@ndufresne.ca,
	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, ming.qian@oss.nxp.com
Subject: Re: [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding
Date: Mon, 2 Feb 2026 10:41:49 +0800	[thread overview]
Message-ID: <aYAO7fOmCYVmCDa5@shlinux89> (raw)
In-Reply-To: <5476502.mvXUDI8C0e@steina-w>

On Fri, Jan 30, 2026 at 10:09:46AM +0100, Alexander Stein wrote:
>Am Freitag, 30. Januar 2026, 09:41:31 CET schrieb ming.qian@oss.nxp.com:
>> From: Ming Qian <ming.qian@oss.nxp.com>
>> 
>> The VPU G2 clock was reduced from 600MHz to 300MHz in commit
>> b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
>> pixel errors with high-resolution HEVC postprocessor output.
>> 
>> However, testing shows the 300MHz clock rate is insufficient for
>> 4K60fps decoding and the original pixel errors no longer occur at
>> 600MHz with current drivers.
>> 
>> Test results with 3840x2160@60fps HEVC stream decoded to NV12
>> (the same scenario that exhibited pixel errors previously):
>> 
>> 300MHz performance:
>> - Severe frame dropping throughout playback
>> - Only 336 frames rendered in 11:53 (0.471 fps)
>> - Continuous "A lot of buffers are being dropped" warnings
>> - Completely unusable for 4K video
>> 
>> 600MHz performance:
>> - Smooth playback with only 1 frame dropped at startup
>> - 37981 frames rendered in 10:34 (59.857 fps)
>> - Achieves target 60fps performance
>> - No pixel errors or artifacts observed
>> 
>> Restore the clock to 600MHz to enable proper 4K60fps decoding
>> capability while maintaining stability.
>> 
>> Test pipeline:
>>   gst-launch-1.0 filesrc location=<4K60_HEVC.mkv> ! \
>>     video/x-matroska ! aiurdemux ! h265parse ! \
>>     v4l2slh265dec ! video/x-raw,format=NV12 ! \
>>     queue ! waylandsink
>> 
>> Fixes: b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock")
>> Signed-off-by: Ming Qian <ming.qian@oss.nxp.com>
>> ---
>>  arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> index 607962f807be..731142176625 100644
>> --- a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> @@ -960,7 +960,7 @@ pgc_vpu: power-domain@6 {
>>  									 <&clk IMX8MQ_SYS1_PLL_800M>,
>>  									 <&clk IMX8MQ_VPU_PLL>;
>>  						assigned-clock-rates = <600000000>,
>> -								       <300000000>,
>> +								       <600000000>,
>
>If I read the Datasheet correctly 600 MHz is only supported by overdrive
>mode (also depending on the VDD_VPU).
>Is this frequency really correct?

G1 and BUS clk were already set as Overdrive frequency.

This change is to only upgrading G2 from 300M to 600M.

So if your question is should we downgrade all to Nominal mode, I think
no. The freq could be override in board dts, or adding a new dts
as arch/arm64/boot/dts/freescale/imx8mp-nominal.dtsi

Regards
Peng

>
>Best regards,
>Alexander
>
>>  								       <800000000>,
>>  								       <0>;
>>  					};
>> 
>> base-commit: c824345288d11e269ce41b36c105715bc2286050
>> prerequisite-patch-id: 0000000000000000000000000000000000000000
>> 
>
>
>
>

  reply	other threads:[~2026-02-02  2:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  8:41 [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding ming.qian
2026-01-30  9:09 ` Alexander Stein
2026-02-02  2:41   ` Peng Fan [this message]
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)
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=aYAO7fOmCYVmCDa5@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=Frank.li@nxp.com \
    --cc=alexander.stein@ew.tq-group.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=ming.qian@oss.nxp.com \
    --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