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 <umang.jain@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Reviewed-by: Paul Elder <paul.elder@ideasonboard.com>
This commit is contained in:
Umang Jain
2022-04-08 15:51:45 +05:30
parent 1724077225
commit 52cd4dacd0
2 changed files with 7 additions and 7 deletions
+1 -1
View File
@@ -30,6 +30,7 @@ interface IPAVimcInterface {
mapBuffers(array<libcamera.IPABuffer> buffers);
unmapBuffers(array<uint32> 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 {