Jacopo Mondi 7fde7c7aeb ipa: proxy_worker: Reset ControlSerializer on worker ... When running the IPA in isolated mode, each side of the IPC boundary has an instance of the ControlSerializer class which is used to serializer/deserialize controls before transmitting them on the wire. The IPAProxyWorker, which creates and manages the process the IPA runs in, does not reset its ControlSerializer upon an IPA::configure() call, while the IPAProxy does, effectively creating a misalignment between the two sides of the fence. This obviously creates issues as one side of the IPC runs with a populated and possibly stale cache of ControlInfoMap references, while the other side gets reset every time a new configuration is applied to the Camera. Fix that by resetting the IPAProxyWorker ControlSerializer on an IPA configure() call. This change fixes an issue which is easily triggered by running two consecutive capture sessions with the IPA running in isolated mode: ERROR Serializer control_serializer.cpp:520 Can't deserialize ControlList: unknown ControlInfoMap Fixes: 7832e19a59 ("utils: ipc: add templates for code generation for IPC mechanism") Signed-off-by: Jacopo Mondi <jacopo@jmondi.org> Reviewed-by: Umang Jain <umang.jain@ideasonboard.com> Reviewed-by: Paul Elder <paul.elder@ideasonboard.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>		2021-09-27 14:35:51 +02:00
..
libcamera_templates	ipa: proxy_worker: Reset ControlSerializer on worker	2021-09-27 14:35:51 +02:00
meson.build	meson: ipa, proxy: Generate headers and proxy with mojo	2021-02-16 19:21:39 +09:00
mojom_libcamera_generator.py	utils: ipc: mojo: Error if ControlInfoMap/List doesn't prefix libcamera	2021-06-01 18:52:05 +09:00