linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6qdl-sabresd: Allow HDMI and LVDS to work simultaneously
Date: Wed, 24 Jun 2015 11:21:34 +0200	[thread overview]
Message-ID: <1435137694.4433.7.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5DvURaPsCsksfU2BRPxVwHRi8=z+PJEd2Feuuxuco0+wg@mail.gmail.com>

Hi Fabio,

Am Dienstag, den 23.06.2015, 13:32 -0300 schrieb Fabio Estevam:
> Hi Phillip,
> 
> On Tue, Jun 23, 2015 at 1:23 PM, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> 
> > Please remember that on i.MX6QDL in general we can't change the LDB
> > clock parent without risking a breakdown in the divider:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313618.html
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313619.html
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313620.html
> 
> Yes, I am aware of this issue.
> 
> However this patch does not make things worse with this respect.
> Instead of changing the LDB parent to PLL5 this patch changes to PLL3
> instead.

If we later make the ldb_di_sel muxes read-only (patch 2 above), this
change will not work anymore. If my (version of your initial) patch 3
gets accepted, the assigned-clock-parents property will keep working for
ldb_di_sel only if it is placed in the clks device tree node.

> > Has there been an erratum for this issue yet?
> 
> I was told we should see it online within a few weeks. Hopefully we
> would be able to revisit your patch series after this happens.

Good news, thank you.

regards
Philipp

      reply	other threads:[~2015-06-24  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 16:03 [PATCH] ARM: dts: imx6qdl-sabresd: Allow HDMI and LVDS to work simultaneously Fabio Estevam
2015-06-23 16:23 ` Philipp Zabel
2015-06-23 16:32   ` Fabio Estevam
2015-06-24  9:21     ` Philipp Zabel [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=1435137694.4433.7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).