diff options
| author | Hugo Grostabussiat <bonstra@bonstra.fr.eu.org> | 2018-04-08 17:11:59 -0400 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2018-05-04 06:50:49 -0400 |
| commit | a8b48e224cad4ca39a147db282ec12d57336bb08 (patch) | |
| tree | 2e15dcfe8c4496b32cb0d35f056799acf3281496 /drivers/fmc | |
| parent | 8c42d2763c0ed7b5f1aff89e2a93487cfc5ec3cb (diff) | |
| download | linux-a8b48e224cad4ca39a147db282ec12d57336bb08.tar.bz2 | |
media: usbtv: Keep norm parameter specific
The user-supplied norm value gets overwritten by the generic .norm
member from the norm_params. That way, we lose the specific norm the
user may want to set.
For instance, if the user specifies V4L2_STD_PAL_60, the value actually
used will be V4L2_STD_525_60, which in the end will be as if the user
had specified V4L2_STD_NTSC, since this is always the first bitfield we
match the norm value against before configuring the hardware.
The norm_params array is only there to match a norm with an output
resolution. The norm value itself should not be changed.
Signed-off-by: Hugo Grostabussiat <bonstra@bonstra.fr.eu.org>
Signed-off-by: Hans Verkuil <hansverk@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Diffstat (limited to 'drivers/fmc')
0 files changed, 0 insertions, 0 deletions