4ca052b4ea
Some devices reference an output terminal as the source of extension units. This is incorrect, as output terminals only have an input pin, and thus can't be connected to any entity in the forward direction. The resulting topology would cause issues when registering the media controller graph. To avoid this problem, connect the extension unit to the source of the output terminal instead. While at it, and while no device has been reported to be affected by this issue, also handle forward scans where two output terminals would be connected together, and skip the terminals found through such an invalid connection. Reported-and-tested-by: John Nealy <jnealy3@yahoo.com> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| uvc_ctrl.c | ||
| uvc_debugfs.c | ||
| uvc_driver.c | ||
| uvc_entity.c | ||
| uvc_isight.c | ||
| uvc_metadata.c | ||
| uvc_queue.c | ||
| uvc_status.c | ||
| uvc_v4l2.c | ||
| uvc_video.c | ||
| uvcvideo.h | ||