Some devices can implement a physical switch to disable the input of the
camera on demand. Think of it like an elegant privacy sticker.
The system can read the status of the privacy switch via a GPIO.
The ACPI table maps this GPIO to the USB device via _CRS and _DSD
descriptors, so the kernel can find it.
The userspace applications need to know if the privacy pin is enabled
or not.
The obvious way to show it to userspace is via the V4L2_CID_PRIVACY control.
This patchset implement this functionality.
v4: Implement UVC_QUIRK_PRIVACY_DURING_STREAM
v3: Thanks to all the comments from Joe Perches
- Rework of printk macros
v2: Thanks to all the comments from Laurent!
- move guid to unit
- support entities with no pads
- CodeStyle
- Irq handling
- pr_cont
- new ids
Ricardo Ribalda (9):
media: uvcvideo: Move guid to entity
media: uvcvideo: Allow external entities
media: uvcvideo: Allow entities with no pads
media: uvcvideo: Entity defined get_info and get_cur
media: uvcvideo: Implement UVC_EXT_GPIO_UNIT
media: uvcvideo: Add Privacy control based on EXT_GPIO
media: uvcvideo: Use dev_ printk aliases
media: uvcvideo: New macro uvc_trace_cont
media: uvcvideo: Implement UVC_QUIRK_PRIVACY_DURING_STREAM
drivers/media/usb/uvc/uvc_ctrl.c | 80 ++++---
drivers/media/usb/uvc/uvc_driver.c | 322 +++++++++++++++++++++++------
drivers/media/usb/uvc/uvc_entity.c | 10 +-
drivers/media/usb/uvc/uvc_queue.c | 3 +
drivers/media/usb/uvc/uvc_status.c | 13 +-
drivers/media/usb/uvc/uvc_video.c | 51 ++---
drivers/media/usb/uvc/uvcvideo.h | 54 +++--
7 files changed, 389 insertions(+), 144 deletions(-)
--
2.29.2.684.gfbc64c5ab5-goog