diff options
| author | Hans Verkuil <hans.verkuil@cisco.com> | 2016-06-28 11:32:36 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-07-12 13:33:56 -0300 |
| commit | 0a25a0125194639507cf24319d02f5de63d182b5 (patch) | |
| tree | f1195727ddcca9ba0c337c050e65ed23abf7b485 /drivers/media/i2c/adv7604.c | |
| parent | afd620f81bb02762b77fb76f29a0287cbce32e8c (diff) | |
[media] adv7511: fix quantization range handling
Commit 1fb69bfd29e4b2e5e93922105326dd6cbd5ef6eb (adv7511: improve
colorspace handling) introduced a number of bugs, specifically with
regards to YCbCr output and quantization range handling:
- if the output is not RGB, then disable the full-to-limited range
CSC matrix since that is meant for RGB formats. YCbCr formats are
always limited range, so there is nothing to convert. (OK, full
range YCbCr is possible, but we don't support that right now).
- the mediabus code that was passed to adv7511_set_fmt was always cleared
by the memset in adv7511_fill_format. This made it effectively impossible
to select YCbCr output.
- adv7511_set_fmt never updated the rgb quantization range.
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'drivers/media/i2c/adv7604.c')
0 files changed, 0 insertions, 0 deletions