From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] i.MX6 LDB mux/divider glitch workaround
Date: Mon, 11 Jan 2016 12:23:56 +0100 [thread overview]
Message-ID: <1452511439-10472-1-git-send-email-p.zabel@pengutronix.de> (raw)
Hi,
just so these don't get forgotten, these patches try to implement the
passed down workaround for a glitch caused by switching the ldb_di_sel
muxes which can lock up the ldb_di_ipu_div dividers.
As far as I am aware, this issue is still not mentioned in the chip
errata.
Changes since v1:
- Rebased onto v4.4
- Enabled workaround on i.MX6Q revision 1.0, too, but disabled the
PLL5_VIDEO_DIV parent in that case.
v1 can be found here:
https://patchwork.kernel.org/patch/5574731/
https://patchwork.kernel.org/patch/5574741/
https://patchwork.kernel.org/patch/5574751/
regards
Philipp
Fabio Estevam (1):
ARM: imx6: Fix procedure to switch the parent of LDB_DI_CLK
Philipp Zabel (2):
ARM: imx6: Mask mmdc_ch1 handshake for periph2_sel and
mmdc_ch1_axi_podf
ARM: imx6: Make the LDB_DI0 and LDB_DI1 clocks read-only.
drivers/clk/imx/clk-imx6q.c | 227 ++++++++++++++++++++++++++++++++++++++++++--
drivers/clk/imx/clk.h | 8 ++
2 files changed, 227 insertions(+), 8 deletions(-)
--
2.6.4
next reply other threads:[~2016-01-11 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 11:23 Philipp Zabel [this message]
2016-01-11 11:23 ` [PATCH v2 1/3] ARM: imx6: Mask mmdc_ch1 handshake for periph2_sel and mmdc_ch1_axi_podf Philipp Zabel
2016-01-11 11:23 ` [PATCH v2 2/3] ARM: imx6: Make the LDB_DI0 and LDB_DI1 clocks read-only Philipp Zabel
2016-01-11 11:23 ` [PATCH v2 3/3] ARM: imx6: Fix procedure to switch the parent of LDB_DI_CLK Philipp Zabel
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=1452511439-10472-1-git-send-email-p.zabel@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).