summaryrefslogtreecommitdiff
path: root/utils/update-kernel-headers.sh
diff options
context:
space:
mode:
authorKieran Bingham <kieran.bingham@ideasonboard.com>2020-07-13 09:51:51 +0100
committerKieran Bingham <kieran.bingham@ideasonboard.com>2021-08-12 08:07:25 +0100
commitf96f797b7a5b5298091ee9706dbdab44980e1f6e (patch)
tree3a5791fd4fc61ce32a254db36c0aeefe5701a27f /utils/update-kernel-headers.sh
parent925df9477587765dfb9b5d0293a1e7ddfc7bda4d (diff)
libcamera: pipeline: vivid: Configure the device
When the configurations have been generated and validated, they can be applied to a device. Vivid supports only a single stream, so it directly obtains the first StreamConfiguration from the CameraConfiguration. The VIVID catpure device is a V4L2Video device, so we generate a V4L2DeviceFormat to apply directly to the capture device node. Note that we explicitly convert the libcamera Format stored in cfg.pixelFormat to a V4L2PixelFormat using the helpers provided by the V4L2VideoDevice to ensure that any multiplanar formats are handled correctly and accordingly. Following the call to set the format using the Kernel API, if the format has been adjusted in any way by the kernel driver, then we have failed to correctly handle the validation stages, and thus the configure operation is idendified has having failed. Finally stream specific data can be directly stored and set as reflecting the state of the stream. [NOTE: the cfg.setStream() call here associates the stream to the StreamConfiguration however that should quite likely be done as part of the validation process. TBD] Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Diffstat (limited to 'utils/update-kernel-headers.sh')
0 files changed, 0 insertions, 0 deletions