ipa: rkisp1: agc: Store per-frame information in frame context
Rework the algorithm's usage of the active state to store the value of controls for the last queued request in the queueRequest() function, and store a copy of the values in the corresponding frame context. The frame context is used in the prepare() function to populate the ISP parameters with values corresponding to the right frame. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
This commit is contained in:
parent
b3724d3766
commit
310b7a6a30
5 changed files with 66 additions and 31 deletions
|
@ -333,9 +333,9 @@ void IPARkISP1::processStatsBuffer(const uint32_t frame, const uint32_t bufferId
|
|||
reinterpret_cast<rkisp1_stat_buffer *>(
|
||||
mappedBuffers_.at(bufferId).planes()[0].data());
|
||||
|
||||
context_.activeState.sensor.exposure =
|
||||
frameContext.sensor.exposure =
|
||||
sensorControls.get(V4L2_CID_EXPOSURE).get<int32_t>();
|
||||
context_.activeState.sensor.gain =
|
||||
frameContext.sensor.gain =
|
||||
camHelper_->gain(sensorControls.get(V4L2_CID_ANALOGUE_GAIN).get<int32_t>());
|
||||
|
||||
unsigned int aeState = 0;
|
||||
|
@ -350,8 +350,14 @@ void IPARkISP1::processStatsBuffer(const uint32_t frame, const uint32_t bufferId
|
|||
|
||||
void IPARkISP1::setControls(unsigned int frame)
|
||||
{
|
||||
uint32_t exposure = context_.activeState.agc.exposure;
|
||||
uint32_t gain = camHelper_->gainCode(context_.activeState.agc.gain);
|
||||
/*
|
||||
* \todo The frame number is most likely wrong here, we need to take
|
||||
* internal sensor delays and other timing parameters into account.
|
||||
*/
|
||||
|
||||
IPAFrameContext &frameContext = context_.frameContexts.get(frame);
|
||||
uint32_t exposure = frameContext.agc.exposure;
|
||||
uint32_t gain = camHelper_->gainCode(frameContext.agc.gain);
|
||||
|
||||
ControlList ctrls(ctrls_);
|
||||
ctrls.set(V4L2_CID_EXPOSURE, static_cast<int32_t>(exposure));
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue