About the frame rate reduction problem of capture processing using CSI of Jetson TX2

I modified it as follows and made it work

CONTROL, MATCH_STATE_EN);

That could be a solution. Could you also try below.

@@ -206,7 +211,7 @@ static bool vi_notify_wait(struct tegra_channel *chan,
         */
        for (i = 0; i < chan->valid_ports; i++) {
                err = nvhost_syncpt_wait_timeout_ext(chan->vi->ndev,
-                               chan->syncpt[i][SOF_SYNCPT_IDX], thresh[i],
+                               chan->syncpt[i][FE_SYNCPT_IDX], thresh[i],
                                chan->timeout, NULL, NULL);
                if (unlikely(err)) {
                        dev_err(chan->vi->dev,

Thank you for your advice
I will try your measures.

There is another column of similar issues.
Are we the first solution?

I don’t remember public this before. Should be the first solution for this kind of issue.

How to disable single shot mode, is this a permanent measure?
I would like to hear your opinions.

Try configure the CHANNEDL_COMMAND to AUTOLOAD.

     for (i = 0; i < chan->valid_ports; i++) {
                vi4_channel_write(chan, chan->vnc_id[i],
                        CHANNEL_COMMAND, AUTOLOAD);
                vi4_channel_write(chan, chan->vnc_id[i],
                        CONTROL, SINGLESHOT | MATCH_STATE_EN);
        }

I have already tried the operation by AUTOLOAD.
This measure did not meet expectations

Hello Shane CCC

After that, we continued to check the operation with the single shot mode setting.
I think there is no problem as a countermeasure, but can I treat it as a permanent solution?

Program the REG as below should be

VI_CH0_CONTROL_0.ENABLE = 1; VI_CH0_CONTROL_0.SINGLESHOT= 0

Does that mean Fix as the default for TX2?

Don’t understand you question.
The default driver was programmed as SINGLESHOT.

My question,
Are the following measures treated as formal measures?

VI_CH0_CONTROL_0.ENABLE = 1; VI_CH0_CONTROL_0.SINGLESHOT = 0

Suppose yes.