summaryrefslogtreecommitdiff
path: root/src/py/cam
diff options
context:
space:
mode:
authorJacopo Mondi <jacopo.mondi@ideasonboard.com>2024-10-16 16:00:13 +0200
committerJacopo Mondi <jacopo.mondi@ideasonboard.com>2024-11-25 11:14:52 +0100
commite07ac56066568957b708af88c6d9d66c7914ee65 (patch)
treecd81f9ac3f13a7d42a69cd1f819c2174a68ab9f0 /src/py/cam
parent9a5f91c78abc8985baff89563992be3644f861b0 (diff)
libipa: FCQueue: Make sure FrameContext#0 is initialized
Some IPA modules, like the RkISP1 one, call FCQueue::get(0) at IPA::start() time, before any frame context has been allocated with FCQueue::alloc() called at queueRequest() time. The FCQueue implementation aims to detect when a FrameContext is get() before it is alloc()-ated, Warns about it, and initializes the FrameContext before returning it. In case of frame#0, a get() preceding an alloc() call is not detected as the "frame == frameContext.frame" test returns success, as FrameContexts are zeroed by default. As a result, the first returned FrameContext is not initialized. Explicitly test for frame#0 to make sure the FrameContext is initialized if get(0) is called before alloc(0). To avoid re-initializing a frame context, in case alloc() has been called correctly before get(), introduce an "initialised" state variable that tracks the FrameContext initialisation state. Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com> Reviewed-by: Daniel Scally <dan.scally@ideasonboard.com> Reviewed-by: Stefan Klug <stefan.klug@ideasonboard.com>
Diffstat (limited to 'src/py/cam')
0 files changed, 0 insertions, 0 deletions