All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akshay Bhat <akshay.bhat@timesys.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: imx IPU2 video out
Date: Wed, 21 Oct 2015 14:41:17 -0400	[thread overview]
Message-ID: <5627DC4D.3050200@timesys.com> (raw)
In-Reply-To: <CAOMZO5B1PALj+pvL9x2JD2bCrPk98azD=-mrGewnwnS1VcUzmA@mail.gmail.com>



On 10/21/2015 02:03 PM, Fabio Estevam wrote:
> On Wed, Oct 21, 2015 at 3:47 PM, Akshay Bhat <akshay.bhat@timesys.com> wrote:
>
>> Currently on our setup since LVDS and HDMI use the same IPU, there are clock
>> conflicts at 1080p when setting DI frequency resulting in HDMI display not
>> showing anything, hence the need to use the 2nd IPU.
>
> Maybe LVDS and HDMI are trying to use the same clock source.
>
> Take a look at how we solved this for mx6dl-sabresd:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/imx6qdl-sabresd.dtsi?id=d28be499c45e6e16d7a042ce280eb872dc06952b
>
> Regards,
>
> Fabio Estevam
>

Fabio, I did pull in that patch; however our pixel clock frequency is 
greater than 68.57 MHz so it did not work. When I assigned LVDS to IPU2 
(by forcing it in the dtsi file); then I was able to get 1080p 
resolution on both displays. If it helps I can send a clock dump of the 
working case (2 different IPU's) and not working case (single IPU) with 
your patch applied.

We do have another board which has 65MHz pixel clock and your patch 
helped us get simultaneous LVDS and HDMI output on it :)

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

      reply	other threads:[~2015-10-21 18:41 UTC|newest]

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

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=5627DC4D.3050200@timesys.com \
    --to=akshay.bhat@timesys.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.