Hi Jerry,
I have a quick try by updating dst-csi-port mapping to CSI-E, but the camera driver would report error when starting streaming.
v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=5
[ 123.292451] bwmgr API not supported
[ 123.847777] max9296 34-0048: max9296_get_available_pipe: all pipes are busy
[ 123.854979] imx390 34-001b: imx390_start_streaming: error setting stream
[ 123.861914] imx390 34-001b: Error turning on streaming
[ 125.795777] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 125.804934] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 125.815808] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 125.823546] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=4, csi_port=4
[ 125.834243] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 125.841971] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 4 vc- 0
[ 125.852727] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
I had a search online about the max9296 CSI port E and found that it’s used to specify the max9296 CSI port in 4x2 mode. In our configuration, we use the max9296 2x4 mode, so I think the dst-csi-port in our configure should be CSI-A.
BTW, I found a similar issue that was reported in the community and @ShanCCC mentioned it could be the MAX9296 configure cause the problem. Do you have any detail information about which max9296 configure that I need to double check?
Thanks