Default setting of MIPI-CSI2 virtual channel 0

cancel
Showing results for 
Search instead for 
Did you mean: 

Default setting of MIPI-CSI2 virtual channel 0

Jump to solution
1,189 Views
torus1000
Contributor V

Hi all.
I have a question about MIPI-CSI2 setting of i.MX6 linuxBSP.

Refer to Figure 19-1 "CSI2IPU gasket connectivity" i.MX6DQ Reference Manual (rev.2  7/2014),
VC0/VC1/VC2/VC3 assigned to IPU1_CSI0/IPU1_CSI1/IPU2_CSI0/IPU2_CSI1 respectively.

On the other hands. default setting in <linux>/arch/arm/mach-mx6/board-

mx6q_sabresd.c seems VC0 assigned to IPU1_CSI1 as following;

mipi_csi2_pdate={
    ipu_id = 0;
    csi_id = 1;
    v_channel = 0; ...

(Q) Which one is correct a) VC0 merely connect to IPU1_CSI0 or
    b) VC0 is one of choice for IPU1_CSI1?

If my assumptions were wrong, please let me know.

Thanks.

Labels (2)
0 Kudos
1 Solution
152 Views
Yuri
NXP TechSupport
NXP TechSupport

If we look at MIPI CSI2 configurations of different designs all looks quite reasonable :

1.

(board-mx6q) arm2 :

( static struct mipi_csi2_platform_data mipi_csi2_pdata = { )

        .ipu_id  = 0,

        .csi_id = 0,

        .v_channel = 0,

        …

2.

sabreauto :

        .ipu_id  = 0,

        .csi_id = 1,

        .v_channel = 1,

        …

3.

sabrelite :

        .ipu_id  = 0,

        .csi_id = 0,

        .v_channel = 0,

        …

But sabresd configuration was changed after “…-dual-camera-support.patch” :

        .ipu_id  = 0,

        .csi_id = 1,

        .v_channel = 0,

        …

So, this is correct only for dual camera configuration.

Please pay attention, on the Community thread, special patch is suggested, which

provides reasonable values again :

-    .csi_id = 1,

+    .csi_id = 0,

     .v_channel = 0, 

“Some Experience When Enable MIPI Camera”

https://community.freescale.com/thread/307065

https://community.freescale.com/servlet/JiveServlet/download/328301-260577/0001-support-mipi-and-par...

Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
2 Replies
153 Views
Yuri
NXP TechSupport
NXP TechSupport

If we look at MIPI CSI2 configurations of different designs all looks quite reasonable :

1.

(board-mx6q) arm2 :

( static struct mipi_csi2_platform_data mipi_csi2_pdata = { )

        .ipu_id  = 0,

        .csi_id = 0,

        .v_channel = 0,

        …

2.

sabreauto :

        .ipu_id  = 0,

        .csi_id = 1,

        .v_channel = 1,

        …

3.

sabrelite :

        .ipu_id  = 0,

        .csi_id = 0,

        .v_channel = 0,

        …

But sabresd configuration was changed after “…-dual-camera-support.patch” :

        .ipu_id  = 0,

        .csi_id = 1,

        .v_channel = 0,

        …

So, this is correct only for dual camera configuration.

Please pay attention, on the Community thread, special patch is suggested, which

provides reasonable values again :

-    .csi_id = 1,

+    .csi_id = 0,

     .v_channel = 0, 

“Some Experience When Enable MIPI Camera”

https://community.freescale.com/thread/307065

https://community.freescale.com/servlet/JiveServlet/download/328301-260577/0001-support-mipi-and-par...

Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
152 Views
torus1000
Contributor V

Dear Yuri,

Thank you for your clear answer.

I made a big mistake because my customer used not ltib but yocto.

Could you explain one more time with yocto source?

Sorry for waste your time. I think dtsi include same information.

Here: fsl-release-bsp/build/tmp/work/imx6qsabresd-poky-*/linux-imx/3.10.17-r0/git/arch/arm/boot/dts/imx6q*sd.dtsi

Thanks.

0 Kudos