From 52cd4dacd0ee89a3785f661592d515537180fe64 Mon Sep 17 00:00:00 2001 From: Umang Jain Date: Fri, 8 Apr 2022 15:51:45 +0530 Subject: ipa: vimc: Establish logical order of operations It is preferred that the interface definition should represent the logical order in which the operations will be called. The patch has no functional changes. Signed-off-by: Umang Jain Reviewed-by: Kieran Bingham Reviewed-by: Paul Elder --- include/libcamera/ipa/vimc.mojom | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'include') diff --git a/include/libcamera/ipa/vimc.mojom b/include/libcamera/ipa/vimc.mojom index e5ac3609..cdc03ffb 100644 --- a/include/libcamera/ipa/vimc.mojom +++ b/include/libcamera/ipa/vimc.mojom @@ -30,6 +30,7 @@ interface IPAVimcInterface { mapBuffers(array buffers); unmapBuffers(array ids); + [async] queueRequest(uint32 frame, libcamera.ControlList controls); /* * The vimc driver doesn't use parameters buffers. To maximize coverage * of unit tests that rely on the VIMC pipeline handler, we still define @@ -37,7 +38,6 @@ interface IPAVimcInterface { * handle parameters at runtime. */ [async] fillParams(uint32 frame, uint32 bufferId); - [async] queueRequest(uint32 frame, libcamera.ControlList controls); }; interface IPAVimcEventInterface { -- cgit v1.2.1