or hantro HW
>> since it
>> isn't something that could be done on kernel side.
>
>But since hantro is very common, any userland decoder will need to calculate
>this anyway.
>So perhaps it is better to have this as part of the decode_params?
>
>I'd l
ikewise if output_flag_present_flag is false pic_output_flag will not
be coded, so maybe express it as "after slice_type" rather than "before
pic_output_flag"?
Regards
John Cox
>+.. note::
>+
>+This control is not yet part of the public kernel API and
>+