From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/11] LVDS Display Bridge support for i.MX
Date: Wed, 27 Mar 2013 18:30:34 +0100 [thread overview]
Message-ID: <1364405445-5271-1-git-send-email-p.zabel@pengutronix.de> (raw)
Hi,
the following patches add support for LVDS displays on
i.MX53 and i.MX6q boards.
The clock patches are needed because the LVDS serial clock
needs to be in lockstep with the IPU display interface clock
providing the pixel data. A fixed factor of 7:1 (or 3.5:1 in
dual link mode) needs to be maintained. This is achieved on
i.MX by clocking the LDB DI clock directly from a PLL, and
manually setting the 3.5/7:1 divider depending on dual/single
link mode. The IPU display interface clock is then sourced
from the divided LDB clock.
Changes since v1:
- Added device-tree bindings documentation
- Dropped remains of GPIO handling from LDB driver, sorry about that
regards
Philipp
---
.../devicetree/bindings/staging/imx-drm/ldb.txt | 99 ++++
arch/arm/boot/dts/imx51.dtsi | 2 +
arch/arm/boot/dts/imx53.dtsi | 34 ++
arch/arm/boot/dts/imx6q.dtsi | 17 +
arch/arm/boot/dts/imx6qdl.dtsi | 26 +
arch/arm/mach-imx/clk-imx51-imx53.c | 19 +-
arch/arm/mach-imx/clk-imx6q.c | 43 +-
arch/arm/mach-imx/clk.h | 17 +
arch/arm/mach-imx/common.h | 1 +
arch/arm/mach-imx/mach-imx6q.c | 2 +-
drivers/staging/imx-drm/Kconfig | 7 +
drivers/staging/imx-drm/Makefile | 1 +
drivers/staging/imx-drm/imx-ldb.c | 611 +++++++++++++++++++++
13 files changed, 854 insertions(+), 25 deletions(-)
next reply other threads:[~2013-03-27 17:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 17:30 Philipp Zabel [this message]
2013-03-27 17:30 ` [PATCH v2 01/11] staging: drm/imx: Add LDB support Philipp Zabel
2013-03-27 18:40 ` Martin Fuzzey
2013-03-28 10:06 ` Philipp Zabel
2013-03-28 6:08 ` Shawn Guo
2013-03-28 9:58 ` Philipp Zabel
2013-03-27 17:30 ` [PATCH v2 02/11] ARM i.MX5: Move IPU clock lookups into device tree Philipp Zabel
2013-03-28 7:04 ` Shawn Guo
2013-03-27 17:30 ` [PATCH v2 03/11] ARM i.MX6q: export imx6q_revision Philipp Zabel
2013-03-28 7:04 ` Shawn Guo
2013-03-27 17:30 ` [PATCH v2 04/11] ARM i.MX6q: Add audio/video PLL post dividers for i.MX6q rev 1.1 Philipp Zabel
2013-03-28 7:20 ` Shawn Guo
2013-03-28 9:58 ` Philipp Zabel
2013-03-28 14:43 ` Shawn Guo
2013-03-28 15:22 ` Philipp Zabel
2013-03-27 17:30 ` [PATCH v2 05/11] ARM i.MX6q: set the LDB serial clock parent to the video PLL Philipp Zabel
2013-03-27 17:30 ` [PATCH v2 06/11] ARM i.MX: Add imx_clk_divider_flags and imx_clk_mux_flags Philipp Zabel
2013-03-28 7:39 ` Shawn Guo
2013-03-27 17:30 ` [PATCH v2 07/11] ARM i.MX53: fix ldb di divider and selector clocks Philipp Zabel
2013-03-28 7:40 ` Shawn Guo
2013-03-27 17:30 ` [PATCH v2 08/11] ARM i.MX6q: " Philipp Zabel
2013-03-28 7:40 ` Shawn Guo
2013-03-27 17:30 ` [PATCH v2 09/11] ARM i.MX53: Add IOMUXC GPR to device tree Philipp Zabel
2013-03-27 17:30 ` [PATCH v2 10/11] ARM i.MX53: Add LDB device " Philipp Zabel
2013-03-27 18:43 ` Martin Fuzzey
2013-03-28 7:32 ` Shawn Guo
2013-03-28 8:41 ` Martin Fuzzey
2013-03-28 9:58 ` Philipp Zabel
2013-03-27 17:30 ` [PATCH v2 11/11] ARM i.MX6q: " Philipp Zabel
2013-03-28 7:51 ` Shawn Guo
2013-03-28 9:58 ` Philipp Zabel
2013-03-28 14:50 ` Shawn Guo
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=1364405445-5271-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).