From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: linux-media <linux-media@vger.kernel.org>
Subject: i.MX8MP Hantro G2 HEVC decoding problems
Date: Mon, 03 Nov 2025 14:52:48 +0100 [thread overview]
Message-ID: <m31pmfp6j3.fsf@t19.piap.pl> (raw)
Hi,
I'm trying to decode H.265 full HD RTP stream on an i.MX8MP CPU. Should
I expect it to work, or is there something missing?
Small streams (640x360 etc.) are decoded. With 1080p, the board panics
or does something similar.
Generally Hantro G2 doesn't finish decoding some frame. I have a test
video - it can probably choke on random frames, including P-frames
(this is I/P-frame only stream, produced by the H2 counterpart).
The details are foggy at this point, but I'm receiving interrupts:
# dmesg | grep irq
...
[ 75.002276] hantro_g2_irq: 0x1100 masked 0x1000 <<< status registers,
shows decoding complete
[ 75.143611] hantro_g2_irq: 0x2101 masked 0x0 <<< this is the problem
What could that mean? DEC_E is probably "ERROR", lack of bit 12 is "not
ready", but why do I get this and what does bit 13 possibly mean?
#define G2_REG_INTERRUPT G2_SWREG(1)
#define G2_REG_INTERRUPT_DEC_RDY_INT BIT(12)
#define G2_REG_INTERRUPT_DEC_ABORT_E BIT(5)
#define G2_REG_INTERRUPT_DEC_IRQ_DIS BIT(4)
#define G2_REG_INTERRUPT_DEC_E BIT(0)
... then the condition doesn't seem to improve:
[ 95.198362] hantro_watchdog:126: frame processing timed out!
[ 95.323410] imx-pgc imx-pgc-domain.8: failed to power down ADB400
and it can randomly panic, show an SError, or do nothing of the sort.
How do I even start debugging such stuff?
H.264 doesn't have this problem.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next reply other threads:[~2025-11-03 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 13:52 Krzysztof Hałasa [this message]
2025-11-03 16:26 ` i.MX8MP Hantro G2 HEVC decoding problems Nicolas Dufresne
2025-11-04 8:12 ` Krzysztof Hałasa
2025-11-04 16:22 ` Nicolas Dufresne
2025-11-05 5:25 ` Krzysztof Hałasa
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=m31pmfp6j3.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.