diff options
| author | Chen-Yu Tsai <wenst@chromium.org> | 2022-07-06 09:21:34 +0100 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@kernel.org> | 2022-07-08 18:06:56 +0100 |
| commit | f1748f8f8174a65a885a8e6c0dc11658a6705ac2 (patch) | |
| tree | 89e77b4d39896297bf225e3056bf585779a63103 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 106be65a4119b299c676fcedd247e3ca67186f59 (diff) | |
| download | linux-f1748f8f8174a65a885a8e6c0dc11658a6705ac2.tar.gz linux-f1748f8f8174a65a885a8e6c0dc11658a6705ac2.zip | |
media: mediatek: vcodec: decoder: Fix 4K frame size enumeration
This partially reverts commit b018be06f3c7 ("media: mediatek: vcodec:
Read max resolution from dec_capability"). In this commit, the maximum
resolution ended up being a function of both the firmware capability and
the current set format.
However, frame size enumeration for output (coded) formats should not
depend on the format set, but should return supported resolutions for
the format requested by userspace.
Fix this so that the driver returns the supported resolutions correctly,
even if the instance only has default settings, or if the output format
is currently set to VP8F, which does not support 4K.
This adds an copy of special casing for !VP8 and 4K support. The other
existing copy will be removed when .max_{width,height} are removed from
|struct mtk_vcodec_ctx| in a subsequent patch.
Fixes: b018be06f3c7 ("media: mediatek: vcodec: Read max resolution from dec_capability")
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Tested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions