Skip to contentSkip to conversation

RFC: V4L2_PIX_FMT_NV16: should it allow padding after each plane?

DISCUSSION Hans Verkuil 2 participants 2 messages Aug 31, 2016 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

The NV16 documentation allows for padding after each line:

https://hverkuil.home.xs4all.nl/spec/uapi/v4l/pixfmt-nv16.html

But I have one case where there is also padding after each plane.

Can we fold that into the existing NV16 format? I.e., in that case the size of each plane is sizeimage / 2.

Or do I have to make a new NV16PAD format that allows such padding?

I am in favor of extending the NV16 specification since I believe it makes sense, but I want to know what others think.

Regards,

Hans

#1 lore raw

Hi Hans,

Quoted 8 lines · Hans Verkuil

The NV16 documentation allows for padding after each line:

https://hverkuil.home.xs4all.nl/spec/uapi/v4l/pixfmt-nv16.html

But I have one case where there is also padding after each plane.

Can we fold that into the existing NV16 format? I.e., in that case the size of each plane is sizeimage / 2.

I can't see any harm in doing so. It likely catches most of the alignment requirements.

That still probably doesn't catch all the possible cases but we always do have the option of creating another format in that case.

Quoted 5 lines

Or do I have to make a new NV16PAD format that allows such padding?

I am in favor of extending the NV16 specification since I believe it makes sense, but I want to know what others think.

Signature · 4 lines
Regards,

Sakari Ailus
e-mail: [email protected]	XMPP: [email protected]