Skip to content

vsp2driver: Support to convert full-range YCbCr buffers - #1

Open
eucan wants to merge 1 commit into
renesas-rcar:rcar-gen3from
eucan:Support-full-color-range-YUV
Open

vsp2driver: Support to convert full-range YCbCr buffers#1
eucan wants to merge 1 commit into
renesas-rcar:rcar-gen3from
eucan:Support-full-color-range-YUV

Conversation

@eucan

@eucan eucan commented Jun 21, 2018

Copy link
Copy Markdown

The vsp2driver is supporting BT.601 and BT.709 colorspaces.
Specifications of both standards mentions that
default quantization for YCbCr buffers limited range, and
it is full range for RGB buffers.

Nevertheless vsp2 device supports to correctly convert
full range YCbCr buffers to RGB. We need to set clrcng
of vsp_src_t data structure to 0x01 to specify our buffers
as full range.

v4l2_pix_format_mplane data structure has the necessary
information about quantization. We need to use this
information to correctly set quantization for YCbCr to
RGB conversion.

Signed-off-by: Emre Ucan eucan@de.adit-jv.com
Signed-off-by: Steve Longerbeam steve_longerbeam@mentor.com

The vsp2driver is supporting BT.601 and BT.709 colorspaces.
Specifications of both standards mentions that
default quantization for YCbCr buffers limited range, and
it is full range for RGB buffers.

Nevertheless vsp2 device supports to correctly convert
full range YCbCr buffers to RGB. We need to set clrcng
of vsp_src_t data structure to 0x01 to specify our buffers
as full range.

v4l2_pix_format_mplane data structure has the necessary
information about quantization. We need to use this
information to correctly set quantization for YCbCr to
RGB conversion.

Signed-off-by: Emre Ucan <eucan@de.adit-jv.com>
Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant