diff options
author | Adam Goode <agoode@google.com> | 2020-08-23 03:21:33 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-10-29 09:03:08 +0100 |
commit | 56434ec03f8f892f9f7d71946c7503674d03fc8b (patch) | |
tree | a1fd440b8a3330115c48dc6de6f49161d3824079 /drivers/regulator | |
parent | b72a84acf9942a850b946b1f7a9f476faae24e61 (diff) | |
download | linux-stable-56434ec03f8f892f9f7d71946c7503674d03fc8b.tar.gz linux-stable-56434ec03f8f892f9f7d71946c7503674d03fc8b.tar.bz2 linux-stable-56434ec03f8f892f9f7d71946c7503674d03fc8b.zip |
media: uvcvideo: Ensure all probed info is returned to v4l2
[ Upstream commit 8a652a17e3c005dcdae31b6c8fdf14382a29cbbe ]
bFrameIndex and bFormatIndex can be negotiated by the camera during
probing, resulting in the camera choosing a different format than
expected. v4l2 can already accommodate such changes, but the code was
not updating the proper fields.
Without such a change, v4l2 would potentially interpret the payload
incorrectly, causing corrupted output. This was happening on the
Elgato HD60 S+, which currently always renegotiates to format 1.
As an aside, the Elgato firmware is buggy and should not be renegotating,
but it is still a valid thing for the camera to do. Both macOS and Windows
will properly probe and read uncorrupted images from this camera.
With this change, both qv4l2 and chromium can now read uncorrupted video
from the Elgato HD60 S+.
[Add blank lines, remove periods at the of messages]
Signed-off-by: Adam Goode <agoode@google.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions