Hi everyone, While working on the rkvdec H.264 decoder for ChromeOS, I noticed some behavioral differences compared to Hantro and Cedrus: 1. The driver always overrides the sizeimage setting given by userspace for the output format. This results in insufficient buffer space when running the ChromeOS video_decode_accelerator_tests test program, likely due to a small initial resolution followed by dynamic resolution change. 2. Doesn't support dynamic resolution change. This small series fixes both and aligns the behavior with the other two stateless decoder drivers. This was tested on the downstream ChromeOS 5.10 kernel with ChromeOS. Also compiled tested on mainline but I don't have any other RK3399 devices set up to test video stuff, so testing would be very much appreciated. Also, I'm not sure if user applications are required to check the value of sizeimage upon S_FMT return. If the value is different or too small, what can the application do besides fail? AFAICT it can't split the data of one frame (or slice) between different buffers. Andrzej, I believe the second patch would conflict with your VP9 series. Regards ChenYu Chen-Yu Tsai (2): media: rkvdec: Do not override sizeimage for output format media: rkvdec: Support dynamic resolution changes drivers/staging/media/rkvdec/rkvdec-h264.c | 5 +-- drivers/staging/media/rkvdec/rkvdec.c | 40 +++++++++++----------- 2 files changed, 23 insertions(+), 22 deletions(-) -- 2.33.0.882.g93a45727a2-goog
