diff options
| author | Milan Zamazal <mzamazal@redhat.com> | 2024-12-03 10:38:13 +0100 |
|---|---|---|
| committer | Kieran Bingham <kieran.bingham@ideasonboard.com> | 2024-12-03 14:30:18 +0000 |
| commit | 2a9b0b34f8cb2295cd41a5340a9d26231dcd3e4b (patch) | |
| tree | 4d59287880d6a4dd97523d40ae787c2f5316c819 /src/android/mm/cros_camera_buffer.cpp | |
| parent | a43ea7ff70e332ffe6b852a0aaeeb9aa877663cf (diff) | |
libcamera: software_isp: Actually apply black level from tuning data
The black level obtained from the tuning file in software ISP is
retrieved in init (because this is the standard algorithm method with
access to tuning data) and stored into context. But the context gets
reset in configure and the black level is lost and never applied.
Let's store the black level from the tuning file into an algorithm
instance variable and put it into the context only later in configure.
This is similar to what rkisp1 IPA does with the values obtained from
the tuning file.
Fixes: 41e3d61c745153779ed5a38634d7266bffd60d61 ("libcamera: software_isp: Clear IPA context on configure and stop")
Signed-off-by: Milan Zamazal <mzamazal@redhat.com>
Tested-by: Robert Mader <robert.mader@collabora.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Diffstat (limited to 'src/android/mm/cros_camera_buffer.cpp')
0 files changed, 0 insertions, 0 deletions