[Camera Driver] Building as Static v/s Dynamic module

[Ajith Raj <ajith.raj@broadcom.com>]

Hi Maintainers,

I was working on a CPI based camera driver based on soc_camera framework
which is compiled as a static module in kernel, due to the non-availability
of modprobe framework.
While I was pushing the changes, I got a question from the internel  code
review that why the driver is being compiled as static while all other
drivers available in the open source are compiled as dynamic .ko modules.

I understand that camera as a component need not have to be built static and
can be added later on the need basis. Is there any reason apart from this?
Since the modprobe framework is not available, if I build it as dynamic .ko
module, I need to insert all dependent modules independently and in the
right order. There are many;

videobuf2-dma-contig.ko, videobuf2-v4l2.ko, videobuf2-memops.ko,
videobuf2-vmalloc.ko, …..etc
v4l2-common.ko, v4l2-mem2mem.ko, v4l2-dv-timings.ko
soc_mediabus.ko,soc_camera.ko ,……etc
media.ko, videodev.ko

Do you see any issues in submitting camera as a static module?
Or it has to be dynamic? If so, could you please help me understand the
reasons.

Thanks in advance.

Regards,
Ajith