[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201022133753.310506-1-ribalda@chromium.org>
Date: Thu, 22 Oct 2020 15:37:47 +0200
From: Ricardo Ribalda <ribalda@...omium.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: tfiga@...omium.org, Ricardo Ribalda <ribalda@...omium.org>
Subject: [PATCH 0/6] Show privacy_gpio as a v4l2_ctrl
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.
Ricardo Ribalda (6):
media: uvcvideo: Add UVC_CTRL_FLAG_ENTITY_GET_INFO
media: uvcvideo: Add UVC_CTRL_FLAG_ENTITY_GET_CUR
media: uvcvideo: Add UVC_GUID_EXT_GPIO_CONTROLLER
media: uvcvideo: Add Privacy control based on EXT_GPIO
media: uvcvideo: Implement UVC_GPIO_UNIT
media: uvcvideo: Handle IRQs from the privacy_pin
drivers/media/usb/uvc/uvc_ctrl.c | 56 ++++++++++++++--
drivers/media/usb/uvc/uvc_driver.c | 102 +++++++++++++++++++++++++++++
drivers/media/usb/uvc/uvcvideo.h | 14 ++++
include/uapi/linux/uvcvideo.h | 3 +
4 files changed, 169 insertions(+), 6 deletions(-)
--
2.29.0.rc1.297.gfa9743e501-goog
Powered by blists - more mailing lists