From: Joachim Eastwood <manabian@gmail.com>
To: tony@atomide.com, bcousson@baylibre.com
Cc: linux-arm-kernel@lists.infradead.org, paul@pwsan.com,
tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
Joachim Eastwood <manabian@gmail.com>
Subject: [PATCH v3 0/4] Support for Variscite OM44 modules and boards
Date: Mon, 12 May 2014 20:31:59 +0200 [thread overview]
Message-ID: <1399919523-20330-1-git-send-email-manabian@gmail.com> (raw)
Hello,
This patch set adds support for Variscite OM44 series of system on
modules and boards.
Changes v3:
* Use new OMAP4_IOPAD macro
* Add Tomi's Ack for patches with DSS DT nodes
* Rebase on Tony's omap-for-v3.16/dt branch
v2:
* Use OMAP IOPAD macros
Patch 1: Add support for the SoM itself and the reference carrier
board. Together these make the VAR-STK-OM44 dev kit.
Patch 2: Add support for VAR-DVK-OM44 which is just the STK with
a LCD display.
Patch 3: Nodes for WLAN/BT support.
Patch 4: Add quirks so that WLAN can be used. Still waiting for
proper DT bindings.
Since this patch set uses the new OMAP4_IOPAD macro the follow patch
must be applied: https://patchwork.kernel.org/patch/4160561/
Note that patch 1 and 2 relies upon the DSS panel and HDMI hpq DT
patches from Tomi Valkeinen. See Tomi's 3.16/omap branch.
The branch from Tomi mentioned above is destined for 3.16.
Joachim Eastwood (4):
ARM: dts: Add support for OMAP4 Variscite OM44 family
ARM: dts: Add support for OMAP4 VAR-DVK-OM44
ARM: dts: Add VAR-SOM-OM44 WLAN nodes
ARM: OMAP2+: Use pdata quirks for wl12xx on VAR-STK/DVK-OM44
.../devicetree/bindings/arm/omap/omap.txt | 6 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/omap4-var-dvk-om44.dts | 71 +++++
arch/arm/boot/dts/omap4-var-om44customboard.dtsi | 235 ++++++++++++++
arch/arm/boot/dts/omap4-var-som-om44-wlan.dtsi | 68 ++++
arch/arm/boot/dts/omap4-var-som-om44.dtsi | 343 +++++++++++++++++++++
arch/arm/boot/dts/omap4-var-som.dts | 96 ------
arch/arm/boot/dts/omap4-var-stk-om44.dts | 17 +
arch/arm/mach-omap2/pdata-quirks.c | 7 +
10 files changed, 750 insertions(+), 97 deletions(-)
create mode 100644 arch/arm/boot/dts/omap4-var-dvk-om44.dts
create mode 100644 arch/arm/boot/dts/omap4-var-om44customboard.dtsi
create mode 100644 arch/arm/boot/dts/omap4-var-som-om44-wlan.dtsi
create mode 100644 arch/arm/boot/dts/omap4-var-som-om44.dtsi
delete mode 100644 arch/arm/boot/dts/omap4-var-som.dts
create mode 100644 arch/arm/boot/dts/omap4-var-stk-om44.dts
--
1.8.0
next reply other threads:[~2014-05-12 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:31 Joachim Eastwood [this message]
2014-05-12 18:32 ` [PATCH v3 1/4] ARM: dts: Add support for OMAP4 Variscite OM44 family Joachim Eastwood
2014-05-12 18:32 ` [PATCH v3 2/4] ARM: dts: Add support for OMAP4 VAR-DVK-OM44 Joachim Eastwood
2014-05-12 18:32 ` [PATCH v3 3/4] ARM: dts: Add VAR-SOM-OM44 WLAN nodes Joachim Eastwood
2014-05-12 18:32 ` [PATCH v3 4/4] ARM: OMAP2+: Use pdata quirks for wl12xx on VAR-STK/DVK-OM44 Joachim Eastwood
2014-05-14 23:05 ` [PATCH v3 0/4] Support for Variscite OM44 modules and boards Tony Lindgren
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=1399919523-20330-1-git-send-email-manabian@gmail.com \
--to=manabian@gmail.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/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).