Implement FlexConnect (VPAC VISS+MSC) GStreamer plugin

[PrathamTI]

Implement FlexConnect hardware-accelerated ISP pipeline combining VISS and MSC in a single
GStreamer element for TI AM62A and compatible platforms.

This implementation is based on the official TI FlexConnect kernel node enabled in TI Processor
SDK RTOS[0].

Current Implementation:

1. Single output stream support - FlexConnect can take raw Bayer camera input and produce one processed output stream (e.g., 1920x1080 NV12 or GRAY8)

2. Two output formats supported - NV12: Standard color format (YUV 4:2:0) for display/encode - GRAY8: 8-bit grayscale for computer vision applications

3. Mutliple camera suppor - Flexconnect is supported on multiple camera (e.g IMX219, IMX390, etc)

TODO:

1. Multiple output stream support
2. Add support for TIVX_VPAC_FC_MSC_CMD_SET_CROP_PARAMS control command.

[0] https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/tiovx/docs/user_guide/hwa__vpac__fc_8h_source.html

[cshilwant]

@PrathamTI For SITSW-8156, are you planning to add tests for this new plugin via [0]?

[0] - https://github.com/TexasInstruments/edgeai-gst-plugins/tree/main/tests/check

[cshilwant]

In commit message,

3. Mutliple camera suppor --> 3. Mutliple camera support

[PrathamTI]

@PrathamTI For SITSW-8156, are you planning to add tests for this new plugin via [0]?

[0] - https://github.com/TexasInstruments/edgeai-gst-plugins/tree/main/tests/check

Yes, planning on adding tests after the bug is resolved

[cshilwant]

Yes, planning on adding tests after the bug is resolved

@PrathamTI Bisecting the color artifacts issue in imaging and resolving the crop params control command bug might take some time.

However, I noticed that the tests under edgeai-gst-plugins/tests/check use fakesink, which actually unblocks us for adding tests...since the color artifacts we're observing are specific to kmssink. Given this, the bug shouldn't block us from adding tests under edgeai-gst-plugins/tree/main/tests/check & close SITSW-8156

Adding unit tests for tiovxfcvissmsc now would help us validate the pipeline behavior for each RC through automation. Without these tests in place, we'd need to perform manual validation for every RC going forward (something we can avoid by adding automated unit tests now)

If you don't have the implementation ready yet, you can check out gsttiovxisp.c to get started. We should also evaluate how many positive and negative tests from tiovxisp can be reused for tiovxfcvissmsc and then identify what additional tests specific to tiovxfcvissmsc need to be added.

[PrathamTI]

Yes, planning on adding tests after the bug is resolved

@PrathamTI Bisecting the color artifacts issue in imaging and resolving the crop params control command bug might take some time.

However, I noticed that the tests under edgeai-gst-plugins/tests/check use fakesink, which actually unblocks us for adding tests...since the color artifacts we're observing are specific to kmssink. Given this, the bug shouldn't block us from adding tests under edgeai-gst-plugins/tree/main/tests/check & close SITSW-8156

Adding unit tests for tiovxfcvissmsc now would help us validate the pipeline behavior for each RC through automation. Without these tests in place, we'd need to perform manual validation for every RC going forward (something we can avoid by adding automated unit tests now)

If you don't have the implementation ready yet, you can check out gsttiovxisp.c to get started. We should also evaluate how many positive and negative tests from tiovxisp can be reused for tiovxfcvissmsc and then identify what additional tests specific to tiovxfcvissmsc need to be added.

Good Idea
I'll work on this after this sprint