<?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: mipi-dsi signal problem</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853196#M222894</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please enable panel-lvds driver.&lt;/P&gt;
&lt;PRE class="bp-text bp-text-plain hljs bp-is-scrollable" tabindex="0"&gt;&lt;CODE class="bp-text-code txt"&gt;CONFIG_DRM_PANEL_LVDS &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Apr 2024 07:14:36 GMT</pubDate>
    <dc:creator>Zhiming_Liu</dc:creator>
    <dc:date>2024-04-24T07:14:36Z</dc:date>
    <item>
      <title>mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1852463#M222855</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I want to use sn65dsi84 to display single dsi as dual lvds on my custom board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;My development environment is imx8qxp in linux kernel 5.15.71.&lt;/P&gt;&lt;P&gt;The problem is that no mipi-dsi signal on board.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I referred to the settings from the imx8qxp-mek.dts file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;This is configuration of my dts.&lt;/P&gt;&lt;P&gt;-------------------------------&lt;/P&gt;&lt;P&gt;&amp;amp;mipi1_dphy {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; status = "okay";&lt;BR /&gt;};&lt;/P&gt;&lt;DIV&gt;&amp;amp;mipi1_dsi_host {&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;status = "okay";&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;fsl,clock-drop-level = &amp;lt;2&amp;gt;;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;panel@0 {&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; compatible = "panel-lvds";&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; /* Physical dimensions of active area */&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; width-mm = &amp;lt;338&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; height-mm = &amp;lt;270&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; data-mapping = "vesa-24";&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; panel-timing {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; /* the hactive and porches in the datasheet are for a single LVDS channel */&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; /* since we use dual LVDS channel, Horizontal paramter and clock must double*/&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; clock-frequency = &amp;lt;41238000&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; hactive = &amp;lt;640&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; hsync-len = &amp;lt;10&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; hfront-porch = &amp;lt;70&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; hback-porch = &amp;lt;70&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; vactive = &amp;lt;1024&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; vsync-len = &amp;lt;10&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; vfront-porch = &amp;lt;5&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; vback-porch = &amp;lt;5&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ports {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; #address-cells = &amp;lt;1&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; #size-cells = &amp;lt;0&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; port@0 {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; reg = &amp;lt;0&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; dual-lvds-odd-pixels;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; panel_in_a: endpoint {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; remote-endpoint = &amp;lt;&amp;amp;bridge_out_a&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; port@1 {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; reg = &amp;lt;1&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; dual-lvds-even-pixels;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; panel_in_b: endpoint {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; remote-endpoint = &amp;lt;&amp;amp;bridge_out_b&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; port {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; dsi_out_port: endpoint {&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; remote-endpoint = &amp;lt;&amp;amp;bridge_in&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; data-lanes = &amp;lt;0 1 2 3&amp;gt;;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp; &amp;nbsp; };&lt;/DIV&gt;&lt;DIV&gt;};&lt;/DIV&gt;&lt;DIV&gt;-------------------------------&lt;/DIV&gt;&lt;DIV&gt;However, I cannot get a signal from mipi-dsi.&lt;/DIV&gt;&lt;DIV&gt;Is there any missing point?&lt;/DIV&gt;&lt;DIV&gt;Thank you in advance.&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 Apr 2024 00:02:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1852463#M222855</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-24T00:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1852953#M222882</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer below rules.&lt;/P&gt;
&lt;P&gt;1.Define&amp;nbsp;sn65dsi84 in i2c node&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;bridge@2c {
		compatible = "ti,sn65dsi84";
		reg = &amp;lt;0x2c&amp;gt;;
		enable-gpios = &amp;lt;&amp;amp;gpiof 15 GPIO_ACTIVE_HIGH&amp;gt;;

		ports {
			#address-cells = &amp;lt;1&amp;gt;;
			#size-cells = &amp;lt;0&amp;gt;;

			port@0 {
				reg = &amp;lt;0&amp;gt;;
				bridge_in: endpoint {
					remote-endpoint = &amp;lt;&amp;amp;dsi_out&amp;gt;;
					data-lanes = &amp;lt;1 2&amp;gt;;
				};
			};

			port@2 {
				reg = &amp;lt;2&amp;gt;;
				bridge_out: endpoint {
					remote-endpoint = &amp;lt;&amp;amp;panel_in_lvds&amp;gt;;
				};
			};
		};
	};&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;2. Define panel-lvds in root node , not mipi dsi node&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt; {&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;LI-CODE lang="markup"&gt;panel@0 {
        compatible = "panel-lvds";
 
        /* Physical dimensions of active area */
        width-mm = &amp;lt;338&amp;gt;;
        height-mm = &amp;lt;270&amp;gt;;
 
        data-mapping = "vesa-24";
 
        panel-timing {
            /* the hactive and porches in the datasheet are for a single LVDS channel */
            /* since we use dual LVDS channel, Horizontal paramter and clock must double*/
            clock-frequency = &amp;lt;41238000&amp;gt;;
            hactive = &amp;lt;640&amp;gt;;
            hsync-len = &amp;lt;10&amp;gt;;
            hfront-porch = &amp;lt;70&amp;gt;;
            hback-porch = &amp;lt;70&amp;gt;;
 
            vactive = &amp;lt;1024&amp;gt;;
            vsync-len = &amp;lt;10&amp;gt;;
            vfront-porch = &amp;lt;5&amp;gt;;
            vback-porch = &amp;lt;5&amp;gt;;
        };
 
        ports {
            #address-cells = &amp;lt;1&amp;gt;;
            #size-cells = &amp;lt;0&amp;gt;;
            port@0 {
                reg = &amp;lt;0&amp;gt;;
                dual-lvds-odd-pixels;
                panel_in_a: endpoint {
                    remote-endpoint = &amp;lt;&amp;amp;bridge_out_a&amp;gt;;
                };
            };
            port@1 {
                reg = &amp;lt;1&amp;gt;;
                dual-lvds-even-pixels;
                panel_in_b: endpoint {
                    remote-endpoint = &amp;lt;&amp;amp;bridge_out_b&amp;gt;;
                };
            };
        };
    };
 
    port {
        dsi_out_port: endpoint {
            remote-endpoint = &amp;lt;&amp;amp;bridge_in&amp;gt;;
            data-lanes = &amp;lt;0 1 2 3&amp;gt;;
        };
    };
};&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;3.Define mipi dsi out node in&amp;nbsp;mipi1_dsi_host&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;&amp;amp;mipi1_dsi_host {
	status = "okay";

	ports {
		port@1 {
			reg = &amp;lt;1&amp;gt;;
			mipi1_adv_out: endpoint {
				remote-endpoint = &amp;lt;&amp;amp;adv7535_1_in&amp;gt;;
			};
		};
	};
};&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2024 03:03:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1852953#M222882</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-24T03:03:52Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853027#M222885</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I tried running it after making some modifications, but it's not working properly.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Error running "drm_of_find_panel_or_bridge" function on "ti-sn65dsi83.c".&lt;/P&gt;&lt;P&gt;More specifically, it happened in the "of_drm_find_panel".&lt;/P&gt;&lt;P&gt;I think it's because of the incorrect kernel configuration.&lt;/P&gt;&lt;P&gt;So could you please check the attached config file(config.txt) and let me know what needs to be revised?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2024 04:52:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853027#M222885</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-24T04:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853196#M222894</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please enable panel-lvds driver.&lt;/P&gt;
&lt;PRE class="bp-text bp-text-plain hljs bp-is-scrollable" tabindex="0"&gt;&lt;CODE class="bp-text-code txt"&gt;CONFIG_DRM_PANEL_LVDS &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2024 07:14:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853196#M222894</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-24T07:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853335#M222906</link>
      <description>&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;Following your guide, there are no more errors.&lt;/P&gt;&lt;P&gt;However, it still doesn't work.&lt;/P&gt;&lt;P&gt;When I checked the dsi line with the oscilloscope, I couldn't see the signal.&lt;/P&gt;&lt;P&gt;Is there anything else I can look at about why the dsi signal is not transmitting?&lt;/P&gt;&lt;P&gt;And below is current drm list.&lt;/P&gt;&lt;P&gt;Also refer to the attached dts file(sn65dsi84.dts), panel-simple.c and kernel config(config.txt).&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;root@:~# ls -l /sys/class/drm/&lt;BR /&gt;total 0&lt;BR /&gt;lrwxrwxrwx 1 root root 0 Apr 28 17:42 card0 -&amp;gt; ../../devices/platform/display-subsystem/drm/card0&lt;BR /&gt;lrwxrwxrwx 1 root root 0 Apr 28 17:42 renderD128 -&amp;gt; ../../devices/platform/display-subsystem/drm/renderD128&lt;BR /&gt;-r--r--r-- 1 root root 4096 Apr 28 17:42 version&lt;BR /&gt;root@:~# ls -l /sys/class/drm/card0/&lt;BR /&gt;dev device/ power/ subsystem/ uevent&lt;BR /&gt;root@:~# ls -l /sys/class/drm/card0/&lt;BR /&gt;total 0&lt;BR /&gt;-r--r--r-- 1 root root 4096 May 5 09:56 dev&lt;BR /&gt;lrwxrwxrwx 1 root root 0 May 5 09:56 device -&amp;gt; ../../../display-subsystem&lt;BR /&gt;drwxr-xr-x 2 root root 0 May 5 09:56 power&lt;BR /&gt;lrwxrwxrwx 1 root root 0 Apr 28 17:42 subsystem -&amp;gt; ../../../../../class/drm&lt;BR /&gt;-rw-r--r-- 1 root root 4096 Apr 28 17:42 uevent&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2024 10:52:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1853335#M222906</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-24T10:52:47Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854112#M222938</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please use one typical timing for test and provide kernel log.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2024 00:27:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854112#M222938</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-25T00:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854401#M222959</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;Follwing your guide, but stiil it doesn't display.&lt;/P&gt;&lt;P&gt;Please check attached log(sn65dsi84_lvds.log).&lt;/P&gt;&lt;P&gt;And the previous panel-simple method was not possible, so I changed the driver to panel-lvds.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2024 06:46:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854401#M222959</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-25T06:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854480#M222964</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you add more log print in&amp;nbsp;sn65dsi83 driver and enable debug flag in drivers/gpu/drm/bridge/nwl-dsi.c ? Please check MIPI HOST driver status.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2024 07:41:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854480#M222964</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-25T07:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854660#M222975</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;I tried to enable debug flag in nwl-dsi.c like below, but it doesn't show debug message.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="hansung_jung_0-1714039680071.png" style="width: 326px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/275837i2089A031CAB5DEC1/image-dimensions/326x512?v=v2" width="326" height="512" role="button" title="hansung_jung_0-1714039680071.png" alt="hansung_jung_0-1714039680071.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;hansung_jung_0-1714039680071.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So could you please let me know how to enable debug flag in driver?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2024 10:10:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1854660#M222975</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-25T10:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1855177#M223005</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The log should contain 'imx-drm display-subsystem', need check dts nodes.&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[    3.155378] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[    3.163871] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[    3.171546] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[    3.179325] imx-drm display-subsystem: bound bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops)
[    3.187908] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /bus@56220000/dsi_host@56228000 to encoder DSI-89: -19
[    3.199019] imx-drm display-subsystem: bound 56228000.dsi_host (ops nwl_dsi_component_ops)
[    3.207751] imx-drm display-subsystem: bound bus@56220000:ldb@562410e0 (ops imx8qxp_ldb_ops)
[    3.216240] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /bus@56220000/dsi_host@56248000 to encoder DSI-89: -19
[    3.227335] imx-drm display-subsystem: bound 56248000.dsi_host (ops nwl_dsi_component_ops)
[    3.236054] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please include&amp;nbsp;evk dts in your dts or add dc/dpu node like&amp;nbsp;mek.dts&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 01:18:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1855177#M223005</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-26T01:18:26Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1855472#M223034</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;Referring to imx8qxp-ss-lvds.dtsi and imx8qxp-ss-dc.dtsi, I tried to activate&amp;nbsp;&lt;SPAN&gt;'imx-drm display-subsystem' in 2 ways, but it is failed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The first way is to add 'display-subsystem' in existing dts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please refer to the attached subsystem.dts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In this case, 'imx-drm display-subsystem' log is not displayed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The second way is to use dpu, refer to the attached 'dpu_subsystem.dts'.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This causes kernel panic.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am not familiar with it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So would you please let me know how to enable 'display-subsystem'.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 08:35:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1855472#M223034</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-26T08:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1856100#M223072</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131196"&gt;@hansung_jung&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you using linux-imx? You can modify imx8qxp-mek.dts and add this video bridge based on ADV7535. Then you don't need modify any driver config and device tree node.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Apr 2024 02:24:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1856100#M223072</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-04-28T02:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1857074#M223130</link>
      <description>&lt;P&gt;Thanks to your reply.&lt;/P&gt;&lt;P&gt;As you said, I use linux-imx.&lt;/P&gt;&lt;P&gt;However, base image is different from imx8qxp-mek.dts.&lt;/P&gt;&lt;P&gt;Even I tried to reference the imx8qxp-mek image as much as possible, but display-subsystem log is not displayed.&lt;/P&gt;&lt;P&gt;I think due to a slight difference, my board doesn't work.&lt;/P&gt;&lt;P&gt;Anyway, thanks to your help, it is very helpful to me.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2024 00:52:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1857074#M223130</guid>
      <dc:creator>hansung_jung</dc:creator>
      <dc:date>2024-04-30T00:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1881201#M224561</link>
      <description>&lt;P&gt;I get the similar error&lt;/P&gt;&lt;P&gt;[drm:drm_bridge_attach] *ERROR* failed to attach bridge /bus@56220000/dsi_host@56228000 to encoder DSI-89: -517&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;dts:&lt;/P&gt;&lt;DIV&gt;&amp;amp;mipi0_dphy {&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;status = "okay";&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;};&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;amp;mipi0_dsi_host {&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;status = "okay";&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;ports {&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/delete-node/ port@1;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;port@1 {&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;reg = &amp;lt;1&amp;gt;;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;mipi0_dsi_out: endpoint {&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;remote-endpoint = &amp;lt;&amp;amp;edp_bridge_in&amp;gt;;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;};&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;};&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;};&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;};&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 05:56:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1881201#M224561</guid>
      <dc:creator>sean33996</dc:creator>
      <dc:date>2024-06-05T05:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: mipi-dsi signal problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1881210#M224564</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/223541"&gt;@sean33996&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Modify your edp driver like this patch about lt9211, -517 is caused by incorrect driver sequence.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Patch-for-LT9211-bridge-on-i-MX/ta-p/1685417" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Patch-for-LT9211-bridge-on-i-MX/ta-p/1685417&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 05:59:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/mipi-dsi-signal-problem/m-p/1881210#M224564</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2024-06-05T05:59:41Z</dc:date>
    </item>
  </channel>
</rss>

