Commit eb79dbf6 authored by Hans Verkuil's avatar Hans Verkuil Committed by Mauro Carvalho Chehab

[media] vivid: use consistent colorspace/Y'CbCr Encoding strings

Keep the colorspace and encoding names consistent with what is
used elsewhere (primarily the utilities in v4l-utils.git).
Signed-off-by: default avatarHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
parent 68998ea2
...@@ -689,7 +689,7 @@ static const struct v4l2_ctrl_config vivid_ctrl_max_edid_blocks = { ...@@ -689,7 +689,7 @@ static const struct v4l2_ctrl_config vivid_ctrl_max_edid_blocks = {
static const char * const vivid_ctrl_colorspace_strings[] = { static const char * const vivid_ctrl_colorspace_strings[] = {
"SMPTE 170M", "SMPTE 170M",
"REC 709", "Rec. 709",
"sRGB", "sRGB",
"AdobeRGB", "AdobeRGB",
"BT.2020", "BT.2020",
...@@ -716,7 +716,7 @@ static const char * const vivid_ctrl_ycbcr_enc_strings[] = { ...@@ -716,7 +716,7 @@ static const char * const vivid_ctrl_ycbcr_enc_strings[] = {
"xvYCC 601", "xvYCC 601",
"xvYCC 709", "xvYCC 709",
"sYCC", "sYCC",
"BT.2020 Non-Constant Luminance", "BT.2020",
"BT.2020 Constant Luminance", "BT.2020 Constant Luminance",
"SMPTE 240M", "SMPTE 240M",
NULL, NULL,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment