From: Philipp Zabel <p.zabel@pengutronix.de>
To: Gary Bisson <gary.bisson@boundarydevices.com>
Cc: dri-devel@lists.freedesktop.org, slongerbeam@gmail.com
Subject: Re: drm: imx: multi-display support questions
Date: Thu, 28 May 2015 12:58:32 +0200 [thread overview]
Message-ID: <1432810712.3228.37.camel@pengutronix.de> (raw)
In-Reply-To: <CAAMH-yt3jOc0i15jbh=N14x58xRS4oEKjyKYPg33UwdaS7wK0A@mail.gmail.com>
Hi Gary,
Am Mittwoch, den 27.05.2015, 15:31 +0200 schrieb Gary Bisson:
> > According to the kerneldoc comment for drm_fb_helper_initial_config
> > (which is used by imx-drm via drm_fbdev_cma_init), it should set up a
> > single /dev/fb cloned over all connectors. This works here with LVDS and
> > HDMI.
>
> Does it require the two displays to have the exact same resolution?
> I'm wondering what is wrong with my setup but with a 1024x768 LVDS and
> a 1920x1080 HDMI display no image is shown on the HDMI (no signal).
> The CRTC settings show that both have the same origin (0,0) so I
> expected the LVDS to display a part of what the HDMI *should* display.
No, but it does require the HDMI and LVDS display to use different clock
sources (unless LVDS serializer clock happens to be the same as the HDMI
pixel clock).
I wonder what we should do about this for devices that have both LVDS
and HDMI output and can only use PLL5 for both. Register a clock
notifier that vetoes changes?
[...]
> > For parallel and LVDS we'd either need to force the parallel panel to be
> > clocked by the IPU internal clock, or move one or the other external
> > clock source off of pll5_video.
>
> Do you have a preference for one solution over the other?
That depends on the board. Is there an LVDS display that can be driven
by a PLL other than PLL5? Since there is no sane way to change the
LDB_DI parent in a running system, that should be configured in the
device tree.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-28 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 14:47 drm: imx: multi-display support questions Gary Bisson
2015-05-27 9:38 ` Philipp Zabel
2015-05-27 13:31 ` Gary Bisson
2015-05-28 10:58 ` Philipp Zabel [this message]
2015-05-28 19:30 ` Eric Nelson
2015-05-29 9:30 ` Philipp Zabel
2015-05-30 16:27 ` Eric Nelson
2015-05-28 19:39 ` Fabio Estevam
2015-06-23 17:49 ` Fabio Estevam
2015-06-23 17:50 ` Fabio Estevam
2015-06-29 16:04 ` Gary Bisson
2015-06-29 16:08 ` Fabio Estevam
2015-06-29 16:12 ` Gary Bisson
2015-06-29 16:14 ` Fabio Estevam
2015-06-29 16:22 ` Eric Nelson
2015-06-29 17:57 ` Gary Bisson
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=1432810712.3228.37.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary.bisson@boundarydevices.com \
--cc=slongerbeam@gmail.com \
/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