devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@openedev.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org,
	Michael Trimarchi <michael@amarulasolutions.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Matteo Lisi <matteo.lisi@engicam.com>
Subject: [PATCH v4 0/7] arm: dts: imx6q-icore: Add LVDS display nodes
Date: Wed,  8 Mar 2017 12:45:13 +0530	[thread overview]
Message-ID: <1488957320-5552-1-git-send-email-jagan@openedev.com> (raw)

From: root <root@b1eb17b01b40.(none)>

This series adds support for lvds display, touchscreen nodes on dts for
Engicam i.CoreM6 Quad boards along with selecting few touchscreen driver
configs to imx_v6_v7_defconfig so-that select by default.

Jagan Teki (7):
  arm: dts: imx6qdl-icore: Add backlight support for lvds
  arm: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual OpenFrame Cap 10.1
    initial support
  arm: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual OpenFrame Cap 12.3
    initial support
  arm: dts: imx6q-icore: Add LVDS support
  arm: dts: imx6q-icore: Add touchscreen node
  arm: imx_v6_v7_defconfig: Select max11801_ts touchscreen driver
  arm: imx_v6_v7_defconfig: Select hid-multitouchdriver

 arch/arm/boot/dts/Makefile                |  2 +
 arch/arm/boot/dts/imx6q-icore-ofcap10.dts | 76 +++++++++++++++++++++++++++++++
 arch/arm/boot/dts/imx6q-icore-ofcap12.dts | 76 +++++++++++++++++++++++++++++++
 arch/arm/boot/dts/imx6q-icore.dts         | 34 ++++++++++++++
 arch/arm/boot/dts/imx6qdl-icore.dtsi      | 20 ++++++++
 arch/arm/configs/imx_v6_v7_defconfig      |  2 +
 6 files changed, 210 insertions(+)
 create mode 100644 arch/arm/boot/dts/imx6q-icore-ofcap10.dts
 create mode 100644 arch/arm/boot/dts/imx6q-icore-ofcap12.dts

-- 
1.9.1

                 reply	other threads:[~2017-03-08  7:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1488957320-5552-1-git-send-email-jagan@openedev.com \
    --to=jagan@openedev.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo.lisi@engicam.com \
    --cc=michael@amarulasolutions.com \
    --cc=shawnguo@kernel.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).