Skip to content

Pfc 2026 official#338

Open
davidplowman wants to merge 3 commits into
nextfrom
pfc_2026_official
Open

Pfc 2026 official#338
davidplowman wants to merge 3 commits into
nextfrom
pfc_2026_official

Conversation

@davidplowman
Copy link
Copy Markdown
Collaborator

This is the "official" version that has been reviewed and, I believe, now accepted upstream.

It returns ControlListSequence numbers (in the metadata) that are actually the request sequence number containing the control list that has just been applied (which will be an earlier request to the just-completed one that you are looking at).

In reality, I want a queue of ControlLists separate from the requests, and to use this to generate the ControlListSequence number. But I'm holding off there just for the moment until we can see where libcamera is going (as it seems there may be some movement on this topic).

As such, I'd actually advise against using this feature until things are a bit clearer there and in fact, there is currently no way to use it conveniently from Python. Nonetheless, it's good to have, at last, a step in the right direction with all this.

The queueCount_ value is redundant and can be removed.

The pipeline handler calls the push and applyControls functions in a
an interleaved manner, so queueCount_ was merely tracking writeCount_,
and is therefore unnecessary.

Signed-off-by: David Plowman <david.plowman@raspberrypi.com>
Reviewed-by: Naushir Patuck <naush@raspberrypi.com>
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
The ControlListSequence identifies the sequence number of the request
whose controls have been applied to the images in this request for the
first time.

Signed-off-by: David Plowman <david.plowman@raspberrypi.com>
Reviewed-by: Naushir Patuck <naush@raspberrypi.com>
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
When a request is about to be processed, this commit separates
"delayed controls" (camera-related ones that take "a few frames" to
apply) from "immediate controls" (ISP-related controls) that will
happen instantly. It does so in separate control list, so as to avoid
disturbing the request's original version.

The immediate controls are held back until the delayed controls that
they were submitted with, have happened. This means all the controls
submitted in a request happen atomically.

We therefore already have the sequence number of the request whose
controls have just been applied, so we additionally attach this to the
current request as "ControlId" metadata.

Signed-off-by: David Plowman <david.plowman@raspberrypi.com>
Reviewed-by: Naushir Patuck <naush@raspberrypi.com>
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant