From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: imx6: Fix procedure to switch the parent of LDB_DI_CLK
Date: Sun, 3 Aug 2014 09:27:11 +0800 [thread overview]
Message-ID: <20140803012710.GC2167@dragon> (raw)
In-Reply-To: <CAOMZO5DiYLwJkTrhCEn9rfrNsPmjBNDr8zeqs=DNKmpdKpCTqA@mail.gmail.com>
On Sat, Aug 02, 2014 at 05:24:31PM -0300, Fabio Estevam wrote:
> Hi Shawn,
>
> On Wed, Jul 2, 2014 at 7:53 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > From: Fabio Estevam <fabio.estevam@freescale.com>
> >
> > Due to incorrect placement of the clock gate cell in the ldb_di[x]_clk tree,
> > the glitchy parent mux of ldb_di[x]_clk can cause a glitch to enter the
> > ldb_di_ipu_div divider. If the divider gets locked up, no ldb_di[x]_clk is
> > generated, and the LVDS display will hang when the ipu_di_clk is sourced from
> > ldb_di_clk.
> >
> > To fix the problem, both the new and current parent of the ldb_di_clk should
> > be disabled before the switch. This patch ensures that correct steps are
> > followed when ldb_di_clk parent is switched in the beginning of boot.
> >
> > Signed-off-by: Ranjani Vaidyanathan <Ranjani.Vaidyanathan@freescale.com>
> > Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> > ---
> > Changes since v1:
> >
> > - Remove cpu_is_imx6dl() from disable_anatop_clocks.
> > - Do not use bit 31 of CCM_ANALOG_PFD_528n
>
> Any comment about this patch?
I believe that the agreement we reached during v1 review is we would
work around the issue in bootloader.
Shawn
prev parent reply other threads:[~2014-08-03 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 22:53 [PATCH v2] ARM: imx6: Fix procedure to switch the parent of LDB_DI_CLK Fabio Estevam
2014-08-02 20:24 ` Fabio Estevam
2014-08-03 1:27 ` Shawn Guo [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=20140803012710.GC2167@dragon \
--to=shawn.guo@freescale.com \
--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 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.