Re: [PATCH v4 4/6] media: iris: add platform data for kaanapali

[Joonhoe Kim <26rote@gmail.com>]

On Thu, 01 Oct 2026 20:47:24 +0530, Vikash Garodia wrote:
> +	.inst_caps = &platform_inst_cap_sm8550,

I ran 8K streams on the Lenovo Y700 Gen 5 (TB323FU, Kaanapali), on
v7.3 with an earlier version of this platform data that also uses
platform_inst_cap_sm8550, plus local line buffer fixes for 10-bit
output. Streams of 7680x4320, 30 frames, made with ffmpeg's testsrc2
and software encoders; decoded output compared against the software
decoders:

- HEVC 8-bit, VP9, AV1 8-bit and AV1 10-bit decode: bit-exact.
- H.264 decode: 2 of 30 frames output, nothing in the kernel log.
- H.264 encode: 3 of 30 frames decodable; HEVC encode: no output.
- HEVC Main10 decode: reset the board until I applied commit
  200473c198b2 ("media: iris: Fix iova allocation from restrict
  region", not in v7.3); with it, the session fails with -ENOMEM:
  the 222 MiB co-located MV buffer finds no contiguous IOVA range
  after the 11 capture buffers.

At 1080p and 4K, H.264 and HEVC decode and encode pass, and HEVC
Main10 decodes bit-exact.

With the SM8550 instance caps, VIDIOC_ENUM_FRAMESIZES reports 96x96 -
8192x8192 on the decoder and on the encoder. If H.264 decode and
H.264/HEVC encode are limited below 8K on this SoC, could the platform
data advertise the limit per codec, so that userspace gets an error at
S_FMT instead of a silent failure?

Thanks,
Joonhoe Kim