From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Chris Healy <cphealy@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: DVI output on i.MX51 EVP board not working?
Date: Fri, 31 Mar 2017 17:58:20 +0200 [thread overview]
Message-ID: <20170331155820.GA12860@amethyst.visucore.com> (raw)
In-Reply-To: <1490954562.2371.31.camel@pengutronix.de>
Hello Philipp,
> Looking at the hardware user's guide [1] chapter 9 (VGA and DVI out), I
> notice that the TFP410PA bridge seems to be connected to the DISP2_DAT
> data lines, but uses the DISP1_H/V sync signals (which I can't believe
> is right), according to figure 9-1. But the device tree pin
> configuration configures the DISP1_DAT data lines with pinctrl_ipu_disp1
> instead. This pin configuration was moved there from imx51.dtsi, so I
> think it was just never adapted for this boards' quirks.
Interesting, thanks a lot for pointing that out.
The figure 1-3 on page 6 shows both Disp-1 and Disp-2 going to the DVI-I
connector, however the output of Disp-2 goes through the DAC so I suppose
that's for the VGA pins.
The figure 9-1 seems to be in conflict with that. DISP1_DAT isn't used at all
there, but DISP2_DAT (albeit different pin ranges) go to both the ADV7123 and
TFP410PA.
> It might also be useful to find out which GPIOs are connected to the
> TFP410 power down and reset lines.
Yes, indeed. Luckily it works in u-boot so that's a reference.
Regards,
Wladimir
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-31 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 5:36 DVI output on i.MX51 EVP board not working? Wladimir J. van der Laan
2017-03-31 10:02 ` Philipp Zabel
2017-03-31 15:58 ` Wladimir J. van der Laan [this message]
2017-04-01 21:40 ` Fabio Estevam
2017-04-02 14:03 ` Wladimir J. van der Laan
2017-04-05 12:50 ` Fabio Estevam
2017-04-05 13:05 ` Wladimir J. van der Laan
2017-04-05 13:11 ` Fabio Estevam
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=20170331155820.GA12860@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=cphealy@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@freescale.com \
--cc=p.zabel@pengutronix.de \
/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