dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Akshay Bhat <akshay.bhat@timesys.com>
To: dri-devel@lists.freedesktop.org
Subject: imx IPU2 video out
Date: Tue, 20 Oct 2015 10:22:13 -0400	[thread overview]
Message-ID: <56264E15.4090908@timesys.com> (raw)

Hi,

We are trying to use IPU2 DI0 for LVDS and IPU1 DI0 for HDMI on a iMX6Q 
based board. Below is the ldb entry in device tree and with these 
settings the LVDS is still being mapped to IPU1. Is there something 
missing/incorrect in the dts entry? The board is running 4.3-rc5 kernel.

&ldb {
         assigned-clocks = <&clks IMX6QDL_CLK_LDB_DI0_SEL>,
                           <&clks IMX6QDL_CLK_LDB_DI1_SEL>;
         assigned-clock-parents = <&clks IMX6QDL_CLK_PLL3_USB_OTG>,
                                  <&clks IMX6QDL_CLK_PLL3_USB_OTG>;
         fsl,dual-channel;
         status = "okay";

         lvds0: lvds-channel@0 {
                 fsl,data-mapping = "spwg";
                 fsl,data-width = <24>;
                 status = "okay";
                 display-timings {
                         native-mode = <&timing0>;
                         timing0: stdp4028 {
                                 clock-frequency = <137143857>;
                                 hactive = <1920>;
                                 vactive = <1080>;
                                 hback-porch = <100>;
                                 hfront-porch = <40>;
                                 vback-porch = <30>;
                                 vfront-porch = <3>;
                                 hsync-len = <10>;
                                 vsync-len = <2>;
                         };
                 };
                 port@2 {
                         reg = <2>;
                         lvds0_in: endpoint {
                                 remote-endpoint = <&ipu2_di0_lvds0>;
                         };
                 };
         };
};

I have also tried 2 other settings with the same result:
&ldb {
..............
                 port {
                         lvds0_in: endpoint {
                                 remote-endpoint = <&ipu2_di0_lvds0>;
                         };
                 };
};

and also:
&ldb {
..............
                 port {
                         lvds0_in: endpoint {
                                 remote-endpoint = <&ipu2_di0_disp0>;
                         };
                 };
};

&ipu2_di0_disp0 {
         remote-endpoint = <&lvds0_in>;
};

If i dump the clock tree, the use count for ipu2_diX interface show ipu2 
is not being used.
clock                    parent                   use      rate
ipu1_di0                 clk                       1  148500000
ipu1_di1                 clk                       1  137142857
ipu2_di0                 clk                       0   49500000
ipu2_di1                 clk                       0   49500000

Thanks,
Akshay
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-10-20 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 14:22 Akshay Bhat [this message]
2015-10-21  9:54 ` imx IPU2 video out Lucas Stach
2015-10-21 17:47   ` Akshay Bhat
2015-10-21 18:03     ` Fabio Estevam
2015-10-21 18:41       ` Akshay Bhat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56264E15.4090908@timesys.com \
    --to=akshay.bhat@timesys.com \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox