<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックRe: using mipi dsi for LCD display on imx6dl about android</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312841#M40985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Julio/NXP, did you ever find resolution to this issue? &amp;nbsp;I am trying to run a HX8363-A instead of a HX8369. &amp;nbsp;Although similar in number the command set is completely different between displays. &amp;nbsp;I created my own driver for HX8363-A and I can communicate in command mode. &amp;nbsp;I have verified on the screen that the settings are taking and I can read back correct values. &amp;nbsp;When I switch to video mode nothing is showing up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems PHY clock in video mode should be 250Mhz based on the documentation. &amp;nbsp;However I find I can only communicate with the device in LP command mode when the max PHY clock setting is between 650-1000. &amp;nbsp; Below 650 starts to get packet timeouts and settings don't take.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation for the HX8363 also states commands are sent in HS video mode only. &amp;nbsp;I'm not sure if that is a typo or true, but that would mean I shouldn't be using command mode at all and just injecting my setup packets in video mode . &amp;nbsp;Is that even possible on the i.MX6? &amp;nbsp;I tried simple commands like sleep out (11h) in video mode at 250Mhz PHY clock and they don't work. &amp;nbsp;However they don't error either.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Nov 2016 16:58:22 GMT</pubDate>
    <dc:creator>tommalnar</dc:creator>
    <dc:date>2016-11-21T16:58:22Z</dc:date>
    <item>
      <title>using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312835#M40979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;HI:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I am using a mipi dsi for lcd display on imx6dl about android.I have some problems to ask. I use the below pins:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_D0M&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_D0P&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_CLK0P&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_CLK0M&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_D1M&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DSI_D1P&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; firstly,i can't find the special pin definition in iomux-6dl.h&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; secondly, i would like to know how to set the UBOOT parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; thirdly,&amp;nbsp; How can i modified the kernel to do the mipi lcd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Can you anyone help me!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 01:40:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312835#M40979</guid>
      <dc:creator>tangyuan</dc:creator>
      <dc:date>2014-04-09T01:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312836#M40980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The MIPI DSI pins have no IOMUX, they are fixed for MIPI display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Freescale verified mipi display: drivers\video\mxc\mxcfb_hx8369_wvga.c&lt;/P&gt;&lt;P&gt;video=mxcfb0:dev=mipi_dsi,TRULY-WVGA,if=RGB24&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 06:04:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312836#M40980</guid>
      <dc:creator>qiang_li-mpu_se</dc:creator>
      <dc:date>2014-04-09T06:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312837#M40981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; qiang,Thank you very much.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.Your said:The MIPI DSI pins have no IOMUX.Your mean that I don't need defining pins in board-mx6dl_sabresd.c&lt;BR /&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.Before i do the lcd ,i remembered that i modified in below files:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; board-mx6q_sabresd.c and mxc_lcdif.c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I&amp;nbsp; put the LCD timing parameters in the file:mxc_lcdif.c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; just a example.&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;/* 800x480 @ 57 Hz , pixel clk @ 27MHz */&lt;/P&gt;&lt;P&gt;"CLAA-WVGA", 57, 800, 480, 37037, 40, 60, 10, 10, 20, 10,&lt;/P&gt;&lt;P&gt;FB_SYNC_CLK_LAT_FALL,&lt;/P&gt;&lt;P&gt;FB_VMODE_NONINTERLACED,&lt;/P&gt;&lt;P&gt;0,},&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; The word:Freescale verified mipi display: drivers\video\mxc\mxcfb_hx8369_wvga.c&lt;/P&gt;&lt;P&gt;&amp;nbsp; It told me that i need putting the mipi lcd timing parameters in the file mxcfb_hx8369_wvga.c?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static struct fb_videomode truly_lcd_modedb[] = {&lt;/P&gt;&lt;P&gt; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; "TRULY-WVGA", 64, 480, 800, 37880,&lt;/P&gt;&lt;P&gt;&amp;nbsp; 8, 8,&lt;/P&gt;&lt;P&gt;&amp;nbsp; 6, 6,&lt;/P&gt;&lt;P&gt;&amp;nbsp; 8, 6,&lt;/P&gt;&lt;P&gt;&amp;nbsp; FB_SYNC_OE_LOW_ACT,&lt;/P&gt;&lt;P&gt;&amp;nbsp; FB_VMODE_NONINTERLACED,&lt;/P&gt;&lt;P&gt;&amp;nbsp; 0,&lt;/P&gt;&lt;P&gt; },&lt;/P&gt;&lt;P&gt;};&amp;nbsp; This struct was defined in the file mxcfb_hx8396_wvga.c&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Best Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 06:30:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312837#M40981</guid>
      <dc:creator>tangyuan</dc:creator>
      <dc:date>2014-04-09T06:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312838#M40982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you don't need defining pins in board-mx6dl_sabresd.c for mipi display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And for mipi display, mxc_lcdif.c will not be used, you should reference to mxcfb_hx8369_wvga.c to implement a driver for your panel. Just modify the timing parameters in mxcfb_hx8369_wvga.c is not enough, the mipi display initialization codes are depends on panel, it is not common code for all panels.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 06:37:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312838#M40982</guid>
      <dc:creator>qiang_li-mpu_se</dc:creator>
      <dc:date>2014-04-09T06:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312839#M40983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; qiang:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I have a little understood.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Firstly, i need to implement a driver for my panel reference to mxcfb_hx8369_wvga.c.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Secondly, i think that in board-mx6q_sabresd.c if i need do as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp; static struct mipi_dsi_platform_data mipi_dsi_pdata = {&lt;/P&gt;&lt;P&gt; .ipu_id&amp;nbsp; = 0,&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt; .disp_id = 1,&lt;/P&gt;&lt;P&gt; .lcd_panel = "TRULY-WVGA",&lt;/P&gt;&lt;P&gt; .reset&amp;nbsp; = mx6_reset_mipi_dsi,&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static void mx6_reset_mipi_dsi(void)&lt;BR /&gt;{&lt;BR /&gt; gpio_set_value(SABRESD_DISP_PWR_EN, 1);&lt;BR /&gt; gpio_set_value(SABRESD_DISP_RST_B, 1);&lt;BR /&gt; udelay(10);&lt;BR /&gt; gpio_set_value(SABRESD_DISP_RST_B, 0);&lt;BR /&gt; udelay(50);&lt;BR /&gt; gpio_set_value(SABRESD_DISP_RST_B, 1);&lt;/P&gt;&lt;P&gt; /*&lt;BR /&gt;&amp;nbsp; * it needs to delay 120ms minimum for reset complete&lt;BR /&gt;&amp;nbsp; */&lt;BR /&gt; msleep(120);&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to ask the mipi_dsi_pdata can be defined above,&lt;/P&gt;&lt;P&gt;I feel that mx6_reset_mipi_dsi is necessary.&lt;/P&gt;&lt;P&gt;Because I guess&amp;nbsp; the RST_B and PWR EN is for my mipi lcd panel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 07:23:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312839#M40983</guid>
      <dc:creator>tangyuan</dc:creator>
      <dc:date>2014-04-09T07:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312840#M40984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Qiang Li,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 10pt; line-height: 1.5em;"&gt;I follow the suggestions from you and Tang to setup the timing in a MIPI-DSI panel.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 10pt; line-height: 1.5em;"&gt;For now, I can communicate with the panel controller in the "setup" functions at file &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;mxcfb_hx8369_wvga.c&lt;/SPAN&gt; (command mode). For example, I can get the status and config other registers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;However, the display don't show anything (video mode).&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;According with the panel controller, the clock period in HS mode must be greater than 4ns however in the scope I get 3ns. So, I think this could be the problem. To change this clock using the mipi_dsi driver, I change the variable "max_phy_clk", however, after this change, the LP clock is also changed and I cannot setup the panel register (in LP mode).&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Do you have any suggestions? For example, can I change the HS and LP clock independently?&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Thanks,&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;JC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2014 06:37:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312840#M40984</guid>
      <dc:creator>juliocruz</dc:creator>
      <dc:date>2014-06-05T06:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312841#M40985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Julio/NXP, did you ever find resolution to this issue? &amp;nbsp;I am trying to run a HX8363-A instead of a HX8369. &amp;nbsp;Although similar in number the command set is completely different between displays. &amp;nbsp;I created my own driver for HX8363-A and I can communicate in command mode. &amp;nbsp;I have verified on the screen that the settings are taking and I can read back correct values. &amp;nbsp;When I switch to video mode nothing is showing up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems PHY clock in video mode should be 250Mhz based on the documentation. &amp;nbsp;However I find I can only communicate with the device in LP command mode when the max PHY clock setting is between 650-1000. &amp;nbsp; Below 650 starts to get packet timeouts and settings don't take.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation for the HX8363 also states commands are sent in HS video mode only. &amp;nbsp;I'm not sure if that is a typo or true, but that would mean I shouldn't be using command mode at all and just injecting my setup packets in video mode . &amp;nbsp;Is that even possible on the i.MX6? &amp;nbsp;I tried simple commands like sleep out (11h) in video mode at 250Mhz PHY clock and they don't work. &amp;nbsp;However they don't error either.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Nov 2016 16:58:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312841#M40985</guid>
      <dc:creator>tommalnar</dc:creator>
      <dc:date>2016-11-21T16:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312842#M40986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If PHY clock was changed, you can try to change the followed setting, for example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-#define&amp;nbsp;DSI_CLKMGR_CFG_CLK_DIV&amp;nbsp;&amp;nbsp;(0x107)&lt;BR /&gt;+#define DSI_CLKMGR_CFG_CLK_DIV&amp;nbsp;&amp;nbsp;(0x104)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TX_ESC clock&amp;nbsp;and the MIPI LP clock are the same thing, so DSI_CLKMGR_CFG_CLK_DIV is used to control the LP clock frequency.&lt;/P&gt;&lt;P&gt;TX_ESC clock = PHY byte clock / (DSI_CLKMGR_CFG_CLK_DIV &amp;amp; 0xFF).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2016 01:54:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312842#M40986</guid>
      <dc:creator>qiang_li-mpu_se</dc:creator>
      <dc:date>2016-11-22T01:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: using mipi dsi for LCD display on imx6dl about android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312843#M40987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you so much Qiang Li!&lt;/P&gt;&lt;P&gt;That explains things and its now working for me. &amp;nbsp;I can lower the clock to 240Mhz and set&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;DSI_CLKMGR_CFG_CLK_DIV to 0x102 which is what the device likes in command mode and video mode. &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I just want to say the support from NXP in my experience is outstanding. &amp;nbsp;I hope your manager receives this message.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2016 02:31:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/using-mipi-dsi-for-LCD-display-on-imx6dl-about-android/m-p/312843#M40987</guid>
      <dc:creator>tommalnar</dc:creator>
      <dc:date>2016-11-22T02:31:02Z</dc:date>
    </item>
  </channel>
</rss>

