linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i.MX IPU SoC support
Date: Mon, 12 Nov 2012 16:23:22 +0100	[thread overview]
Message-ID: <1352733809-27230-1-git-send-email-s.hauer@pengutronix.de> (raw)

This series adds the necessary i.MX SoC stuff to make the IPU support
usable. Basically needed are the IPU devices in the devicetrees. This
series also adds display support for the i.MX51 babbage which then is
the first board for which the IPU driver works without out of tree
stuff.

Shawn, I already sent the MIPI setup patch some time ago. From what
I read I think we can agree on the approach on just setting the correct
register values in the SoC code, right?

Sascha

The following changes since commit 77b67063bb6bce6d475e910d3b886a606d0d91f7:

  Linux 3.7-rc5 (2012-11-11 13:44:33 +0100)

are available in the git repository at:

  git://git.pengutronix.de/git/imx/linux-2.6.git ipu

for you to fetch changes up to f774f0f776e282d6e0eb67dbf00703ed79b8bca2:

  ARM i.MX51 babbage: Add display support (2012-11-12 16:16:19 +0100)

----------------------------------------------------------------
Sascha Hauer (6):
      ARM i.MX51: setup MIPI during startup
      ARM i.MX5: switch IPU clk support to devicetree bindings
      ARM i.MX53: Add IPU support
      ARM i.MX51: Add IPU support
      ARM i.MX6: Add IPU support
      ARM i.MX51 babbage: Add display support

Steffen Trumtrar (1):
      ARM i.MX6: fix ldb_di_sel mux

 arch/arm/boot/dts/imx51-babbage.dts |   16 +++++++++
 arch/arm/boot/dts/imx51.dtsi        |   67 +++++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/imx53.dtsi        |    7 ++++
 arch/arm/boot/dts/imx6q.dtsi        |   18 ++++++++++
 arch/arm/mach-imx/clk-imx51-imx53.c |   19 +++++-----
 arch/arm/mach-imx/clk-imx6q.c       |    2 +-
 arch/arm/mach-imx/mm-imx5.c         |   20 +++++++++++
 7 files changed, 140 insertions(+), 9 deletions(-)

             reply	other threads:[~2012-11-12 15:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 15:23 Sascha Hauer [this message]
2012-11-12 15:23 ` [PATCH 1/7] ARM i.MX51: setup MIPI during startup Sascha Hauer
2012-11-12 15:23 ` [PATCH 2/7] ARM i.MX6: fix ldb_di_sel mux Sascha Hauer
2012-11-12 15:23 ` [PATCH 3/7] ARM i.MX5: switch IPU clk support to devicetree bindings Sascha Hauer
2012-12-11  5:57   ` Shawn Guo
2012-12-11  9:14     ` Sascha Hauer
2012-12-11 13:13       ` Shawn Guo
2012-11-12 15:23 ` [PATCH 4/7] ARM i.MX53: Add IPU support Sascha Hauer
2012-11-12 15:23 ` [PATCH 5/7] ARM i.MX51: " Sascha Hauer
2012-11-12 15:23 ` [PATCH 6/7] ARM i.MX6: " Sascha Hauer
2012-11-12 15:23 ` [PATCH 7/7] ARM i.MX51 babbage: Add display support Sascha Hauer
2012-11-12 21:40   ` Martin Fuzzey
2012-11-12 21:53     ` Fabio Estevam
2013-01-08 16:41   ` Fabio Estevam
2013-01-08 17:04     ` Fabio Estevam
2013-01-08 17:09       ` Marek Vasut
2013-01-08 17:23         ` Philipp Zabel
2013-01-08 17:29           ` Marek Vasut
2013-01-09  9:04             ` Philipp Zabel
2013-01-09  9:26               ` Marek Vasut
2013-01-09  9:46                 ` Philipp Zabel
2013-01-09 10:25                   ` Marek Vasut
2013-01-08 17:31           ` Fabio Estevam
2012-11-13  2:52 ` [PATCH] i.MX IPU SoC support 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=1352733809-27230-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@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).