Hisilicon VI access video process

Catalog

1. Access multi-channel video , It must be clear Vi Dev Number ,Mipi Number ,Pipe Number ,chn No. relationship ;

2. equipment /PIPE/ Channel number selection

problem 1: How to determine different video access MIPI Number and Vi Dev( equipment ) No. corresponds to ;

problem 2: PIPE How to determine the number ;

problem 3:chn How to confirm ;

3. Software summary :

4. Add

1. Access multi-channel video , It must be clear Vi Dev Number ,Mipi Number ,Pipe Number ,chn No. relationship ;

  Know the process from the above figure :sensor->mipi->Dev->Pipe->phy chn

2. equipment /PIPE/ Channel number selection

Look at the picture below , List the equipment /PIPE/ The maximum supported number of channel numbers ;

So here comes the question , Most chips have more than one device /PIPE/ Channel number , How can I find the right one ?

problem 1: How to determine different video access MIPI Number And Vi Dev( equipment ) No. corresponds to ;

Documents have :

            Hi3559AV100ES Of Dev Can work with any MIPI Set binding , The binding relationship cannot be dynamically modified ; The corresponding interface is HI_MPI_VI_SetMipiBindDev;

            Most of the other chips Dev And MIPI The binding relationship is fixed ,  The binding relationship cannot be dynamically modified ;

Judging from the following table , Cannot be dynamically bound VI DEV and MIPI The numbers are equal ;

  It can be seen from the table : If the chip is to be connected DC Interface ,VI DEV Can only be 3,DC Number is 2;  To dock MIPI Interface ,VI DEV It can be 0~4;

problem 2: PIPE How to determine the number ;

With hi3516 For example , pipe The maximum number is 4; namely pipe0~pipe3;

VI_PIPE_ATTR_S There are some restrictions in attributes !

  Know from the table , To access YUV data , pipe The number can only be 2;  To access raw, all pipe all ok;

Device number binding pipe The interface of No. is : HI_MPI_VI_SetDevBindPipe;

problem 3:chn How to confirm ;

From the maximum value of the channel number , If only 1 individual , fill 0 that will do ; Multiple decisions ;

Just the one in front mipi Number /dev Number /pipe There is a difference on the number , So even chn The same whole passage is also different ;

Such as : mipi0--> dev0--->pipe2-->chn0 ;

      mipi1--> dev1--->pipe0-->chn0;

3. Software summary :

(a) combo_dev_attr_t Attribute devno It can be understood as mipi Number , except Hi3559AV100ES Outside , The mipi Number and vi DEV Same number ;

(b) mipi Number and vi DEV Sign Division Hi3559AV100ES The outside is fixed , No need to bind ; Means the corresponding mipi No. 1 has data , Then it is equivalent to the corresponding vi DEV There are also data on No ;

(c) HI_MPI_VI_SetDevBindPipe Interface implementation VI DEV Number and PIPE Binding of number ; So the corresponding PIPE There's data ;

(d) PIPE Have the data , You can go through dump Tool view, etc , Follow up strategy ;

4. Add

problem : vi_put_original_node_to_line_input_pic_queue [line]:2539 [info]:pipe 2 no space to receive this frm!
    
     Premise : Connected to two different video data ; One way through isp, The other does not need ;
    
     The phenomenon : Debug the two video displays separately ok, When connected together isp Video OK , The other can only reach vi pipe;
     Handle : Active call HI_MPI_VI_GetPipeFrame, After obtaining the frame data , Again HI_MPI_VPSS_SendFrame Pass to vpss;
    
     The problem is solved , The principle is not clear !
 

Next : Hayes vpss Before and after binding relationship

Hayes vpss Summary of binding relationship _ Days before the sea wide blog -CSDN Blog _vpss