]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
media: atomisp: gate ref and tnr frame config behind ISP enable flags
authorJose A. Perez de Azpillaga <azpijr@gmail.com>
Sun, 5 Apr 2026 09:30:43 +0000 (11:30 +0200)
committerSakari Ailus <sakari.ailus@linux.intel.com>
Wed, 20 May 2026 08:29:31 +0000 (11:29 +0300)
commite4e6bc933a63a2a4ed576e6449e455993f79cedd
tree17de6ed2d027fc324fbdcd2340ecdc9d231e6883
parentc06b73f1e19176c0534cd4e1ee0afc044e9774d6
media: atomisp: gate ref and tnr frame config behind ISP enable flags

The FIXME comment noted that delay_frames can be NULL for certain
pipeline configurations, without knowing why. The reason is that when a
binary does not enable ref_frame, delay frame allocation is
intentionally skipped to save memory, leaving the pointers NULL by
design.

The ISP feature flags in binary->info->sp.enable accurately reflect
which features are active for a given binary. Using enable.ref_frame and
enable.tnr as the predicate for their respective configuration steps
ensures the configuration path stays in sync with what was actually
built into the pipeline

Signed-off-by: Jose A. Perez de Azpillaga <azpijr@gmail.com>
Reviewed-by: Andy Shevchenko <andy@kernel.org>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
drivers/staging/media/atomisp/pci/sh_css_sp.c