summaryrefslogtreecommitdiff
path: root/src/qcam/assets/feathericons/chevrons-left.svg
diff options
context:
space:
mode:
authorJean-Michel Hautbois <jeanmichel.hautbois@ideasonboard.com>2021-11-10 20:40:18 +0100
committerJean-Michel Hautbois <jeanmichel.hautbois@ideasonboard.com>2021-11-15 11:00:05 +0100
commitca9adf6b920b6ac1476d7faad89f2c905b274640 (patch)
tree33b838ce58abfe45c74d9cce4198d483e1dd79bf /src/qcam/assets/feathericons/chevrons-left.svg
parent9bef4144c89cc0a1e2dc614cd4747247a2d9330c (diff)
ipa: ipu3: Cache line duration at configure call
We use the line duration several times in the IPAIPU3. Instead of recalculating it each time, cache the value as a utils::Duration. ExposureTime and FrameDuration units are in micro-seconds, cast the Duration accordingly. As sensorInfo is no longer used in updateSessionConfiguration remove the reference to it. Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com> Reviewed-by: Umang Jain <umang.jain@ideasonboard.com> Reviewed-by: Paul Elder <paul.elder@ideasonboard.com>
Diffstat (limited to 'src/qcam/assets/feathericons/chevrons-left.svg')
0 files changed, 0 insertions, 0 deletions
"hl com"> * multiple processes. * * Fences are most commonly used in association with frame buffers. A * FrameBuffer can be associated with a Fence so that the library can wait for * the Fence to be signalled before allowing the camera device to actually * access the memory area described by the FrameBuffer. * * \sa Request::addBuffer() * * By using a fence, applications can then synchronize between frame buffer * consumers and producers, as for example a display device and a camera, to * guarantee that a new data transfers only happen once the existing frames have * been displayed. * * A Fence can be realized by different event notification primitives, the most * common of which is represented by waiting for read events to happen on a