cannot set camera controls via v4l2 on Jetson + Raspberry Pi Cam v2


I am interested in taking a raw image with a set (hardcoded) exposure time. I am using the JetsonNano and Raspberry Pi v2 camera. I can successfully use v4l2-ctl API for image capture and have confirmed that the image data acquired is correct. However, I seem to be unable to influence any of the camera controls via the v4l2 API.

Here is what I am trying.

v4l2-ctl --set-ctrl bypass_mode=0 --set-ctrl=exposure=15 --stream-mmap --stream-to=- --stream-count=1

It takes a raw image but the exposure time that is used for image capture must be coming from an auto exposure setting as the image is not influenced by the very small exposure time (15).

When I run

v4l2-ctl --all

I get:

Driver Info (not using libv4l2):
	Driver name   : tegra-video
	Card type     : vi-output, imx219 6-0010
	Bus info      :
	Driver version: 4.9.140
	Capabilities  : 0x84200001
		Video Capture
		Extended Pix Format
		Device Capabilities
	Device Caps   : 0x04200001
		Video Capture
		Extended Pix Format
Priority: 2
Video input : 0 (Camera 0: no power)
Format Video Capture:
	Width/Height      : 3264/2464
	Pixel Format      : 'RG10'
	Field             : None
	Bytes per Line    : 6528
	Size Image        : 16084992
	Colorspace        : sRGB
	Transfer Function : Default (maps to sRGB)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
	Flags             : 

Camera Controls

                     group_hold 0x009a2003 (bool)   : default=0 value=0 flags=execute-on-write
                    sensor_mode 0x009a2008 (int64)  : min=0 max=0 step=0 default=0 value=0 flags=slider
                           gain 0x009a2009 (int64)  : min=0 max=0 step=0 default=0 value=16 flags=slider
                       exposure 0x009a200a (int64)  : min=0 max=0 step=0 default=0 value=15 flags=slider
                     frame_rate 0x009a200b (int64)  : min=0 max=0 step=0 default=0 value=2000000 flags=slider
                    bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=0
                override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
                   height_align 0x009a2066 (int)    : min=1 max=16 step=1 default=1 value=1
                     size_align 0x009a2067 (intmenu): min=0 max=2 default=0 value=0
               write_isp_format 0x009a2068 (bool)   : default=0 value=0
       sensor_signal_properties 0x009a2069 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
        sensor_image_properties 0x009a206a (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
      sensor_control_properties 0x009a206b (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
              sensor_dv_timings 0x009a206c (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
               low_latency_mode 0x009a206d (bool)   : default=0 value=0
                   sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=5 flags=read-only

I am wondering why the min and max values are 0 for so many of the controls. I am also wondering why my driver/camera seem to lack many other basic controls (such as auto_exposure, auto_gain, etc).

Thank you so much for your help!

Due to NV camera framework use argus to control the 3A, also v4l2-ctl only use to verify the sensor output correct frame data that could be the reason for that.