summaryrefslogtreecommitdiff
path: root/src/ipa/rkisp1/data/imx219.yaml
diff options
context:
space:
mode:
authorJacopo Mondi <jacopo@jmondi.org>2022-11-04 10:09:08 +0100
committerJacopo Mondi <jacopo@jmondi.org>2022-11-23 18:44:36 +0100
commit855228f7d5243278459f32fc372cbbecbde9cdfc (patch)
tree5ad408fa4732656bd1268a8c5ca68f4c41b308d2 /src/ipa/rkisp1/data/imx219.yaml
parent29d6d0e93b0193b70c6c0564eb424f2b6accf4a8 (diff)
ipa: rkisp1: Use IPAConfig in IPA::configure()
The RkISP1 implementation of IPA::configure() still uses the legacy interface where sensor controls (and eventually lens controls) are passed from the pipeline handler to the IPA in a map. Since the introduction of mojom-based IPA interface definition, it is possible to define custom data types and use them in the interface definition between the pipeline handler and the IPA. Align the RkISP1 IPA::configure() implementation with the one in the IPU3 IPA module by using a custom data type instead of relying on a map to pass controls to the IPA. Signed-off-by: Jacopo Mondi <jacopo@jmondi.org> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'src/ipa/rkisp1/data/imx219.yaml')
0 files changed, 0 insertions, 0 deletions