These formats are compressed 12-bit raw bayer formats with four different
pixel orders. The pixel follow one another without any padding,
thus are packed in a 'linear' fashion.
Signed-off-by: Edgar Thier
---
drivers/media/usb/uvc/uvc_driver.c | 21 -
drivers/media/usb/uvc/uvc
These formats are compressed 12-bit raw bayer formats with four different
pixel orders. The pixel follow one another without any padding,
thus are packed in a 'linear' fashion.
Signed-off-by: Edgar Thier
---
Documentation/media/uapi/v4l/pixfmt-rgb.rst | 1 +
.../media/uapi/v4l/pixfmt-srggb12l
The hdpvr firmware reacts poorly to a fast close/open sequence. Delaying
a few seconds between the close and next open produces generally reliable
results. Rather than requiring user programs to implement this delay and
coordinate among themselves when the device is handed from one program to
ano
`hdpvr_read` attempts to restart streaming if the device is read while
it is both not ready and not disconnected. However, the device is often
still not ready immediately after the call to `hdpvr_start_streaming`
returns, causing the condition `if (buf->status != BUFSTAT_READY)` to
exit the loop w
Hello,
On 7/7/19 10:58 PM, Uwe Kleine-König wrote:
> From: Andreas Kemnade
>
> If the si2157 is behind a e.g. si2168, the si2157 will
> at least in some situations not be readable after the si268
> got the command 0101. It still accepts commands but the answer
> is just ff. So read the chip
Instead of failing silent give a hint what went wrong.
Signed-off-by: Uwe Kleine-König
---
drivers/media/usb/dvb-usb-v2/af9035.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/media/usb/dvb-usb-v2/af9035.c
b/drivers/media/usb/dvb-usb-v2/af9035.c
index de52309
From: Andreas Kemnade
If the si2157 is behind a e.g. si2168, the si2157 will
at least in some situations not be readable after the si268
got the command 0101. It still accepts commands but the answer
is just ff. So read the chip id before that so the
information is not lost.
The following li
