From: Ryan Brue <ryanbrue.dev@gmail.com>
To: devnull+getfeus.gmail.com@kernel.org
Cc: Xiandong.Wang@mediatek.com, andrew-ct.chen@mediatek.com,
getfeus@gmail.com, houlong.wei@mediatek.com,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
mchehab@kernel.org, minghsiu.tsai@mediatek.com
Subject: Re: [PATCH RFC v3] media: mediatek: mdp: Keep component suppliers powered while streaming
Date: Fri, 13 Nov 2026 00:46:04 -0600 [thread overview]
Message-ID: <9accec98-c16e-4815-a479-b84fc39e4580@gmail.com> (raw)
In-Reply-To: <20261111-rfc-v2-generated-v3-1-e49697d20806@gmail.com>
Hi Youngjoon,
I hit the same thing on another MT8173 device, an Amazon Fire HD 10
(2017) tablet (board DTS still under review), on v7.4-rc2 with VPU
firmware 1.2.0, every job took about 1.9 s, the firmware reported
success and the CAPTURE planes stayed zero, for MT21 input and for plain
NV12 -> YV12. LARB4 was off during the job.
With v3 applied (one context fixup for devm_kzalloc_obj() on rc2), all
seven sibling blocks bind, and MT21 -> NV12M at 1280x736 from the
decoder matches a software decode byte for byte for H.264 Baseline, Main
and High, VP8 and VP9 (30 frames each). LARB4 suspends again after
streaming, there were no IOMMU faults, and a system suspend/resume with
the driver loaded left conversion byte-exact afterwards.
Tested-by: Ryan Brue <ryanbrue.dev@gmail.com>
Best Regards,
Ryan Brue
next prev parent reply other threads:[~2026-11-13 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:39 [RFC PATCH] media: mediatek: mdp: Keep component suppliers powered while streaming getfeus
2026-11-11 6:41 ` [PATCH RFC v2] " Youngjoon Lee via B4 Relay
2026-11-11 9:43 ` [PATCH RFC v3] " Youngjoon Lee via B4 Relay
2026-11-13 6:46 ` Ryan Brue [this message]
2026-11-13 11:40 ` YoungJoon Lee
2026-11-13 14:28 ` Ryan Brue
2026-11-11 7:57 ` 回复: [RFC PATCH] " Xiandong Wang (王先冬)
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=9accec98-c16e-4815-a479-b84fc39e4580@gmail.com \
--to=ryanbrue.dev@gmail.com \
--cc=Xiandong.Wang@mediatek.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=devnull+getfeus.gmail.com@kernel.org \
--cc=getfeus@gmail.com \
--cc=houlong.wei@mediatek.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=minghsiu.tsai@mediatek.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