Searched hist:"2 b5c18f9" (Results 1 – 1 of 1) sorted by relevance
/openbmc/linux/drivers/media/i2c/ |
H A D | ov5640.c | 2b5c18f9 Fri Jan 18 02:52:06 CST 2019 Chen-Yu Tsai <wens@csie.org> media: ov5640: Consolidate JPEG compression mode setting
The register value lists for all the supported resolution settings all include a register address/value pair for setting the JPEG compression mode. With the exception of 1080p (which sets mode 2), all resolutions use mode 3.
The only difference between mode 2 and mode 3 is that mode 2 may have padding data on the last line, while mode 3 does not add padding data.
As these register values were from dumps of running systems, and the difference between the modes is quite small, using mode 3 for all configurations should be OK.
[Sakari Ailus: Align OV5640_REG_JPG_MODE_SELECT register naming.]
Signed-off-by: Chen-Yu Tsai <wens@csie.org> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> 2b5c18f9 Fri Jan 18 02:52:06 CST 2019 Chen-Yu Tsai <wens@csie.org> media: ov5640: Consolidate JPEG compression mode setting The register value lists for all the supported resolution settings all include a register address/value pair for setting the JPEG compression mode. With the exception of 1080p (which sets mode 2), all resolutions use mode 3. The only difference between mode 2 and mode 3 is that mode 2 may have padding data on the last line, while mode 3 does not add padding data. As these register values were from dumps of running systems, and the difference between the modes is quite small, using mode 3 for all configurations should be OK. [Sakari Ailus: Align OV5640_REG_JPG_MODE_SELECT register naming.] Signed-off-by: Chen-Yu Tsai <wens@csie.org> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
|