diff options
| author | Javier Martinez Canillas <[email protected]> | 2016-09-30 18:16:43 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2016-11-16 16:27:26 -0200 |
| commit | 8a661745b7adb0e3680af3840d4e5dac54afa3d8 (patch) | |
| tree | e8b76603cf86f6cf9a1deb69dc20ca4422862aa0 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | daba4dfbd298ac76e4064a97b88c717cacf43a6f (diff) | |
[media] exynos-gsc: fix supported RGB pixel format
The driver exposes 32-bit A/XRGB 8-8-8-8 as supported format but testing
shows that using this format produces frames with wrong colors. The test
was done with the following GStreamer pipeline:
$ gst-launch-1.0 videotestsrc num-buffers=20 ! video/x-raw,format=UYVY \
! v4l2video3convert ! video/x-raw,format=xRGB ! videoconvert ! kmssink
The manual seems to state that the Pixel Format are in Little Endianness
so instead use the 32-bit BGRA/X 8-8-8-8 pixel format. This format works
correctly when using the following pipeline:
$ gst-launch-1.0 videotestsrc num-buffers=20 ! video/x-raw,format=UYVY \
! v4l2video3convert ! video/x-raw,format=BGRx ! kmssink
This change is similar to commit 7f2816e51ea1 ("[media] s5p-fimc: Changed
RGB32 to BGR32") that fixed the same issue on a different Samsung driver.
Suggested-by: Nicolas Dufresne <[email protected]>
Signed-off-by: Javier Martinez Canillas <[email protected]>
Signed-off-by: Sylwester Nawrocki <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions