From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: dts: Add support for OMAP4 Variscite OM44 family
Date: Fri, 18 Apr 2014 08:57:22 -0700 [thread overview]
Message-ID: <20140418155721.GC5354@atomide.com> (raw)
In-Reply-To: <1397833849-22396-2-git-send-email-manabian@gmail.com>
* Joachim Eastwood <manabian@gmail.com> [140418 08:11]:
> Add support for VAR-SOM-OM44[1] SODIMM system on module from Variscite. SoM
> features a OMAP4460, 1GB RAM, Gigabit Ethernet (LAN7500) and optional WLAN/BT.
>
> Also add support for VAR-STK-OM44 development board from Variscite. This kit
> features a VAR-SOM-OM44 and the carrier board VAR-OM44CustomBoard[2]. The
> VAR-STK-OM44 is the same as VAR-DVK-OM44 but without the LCD display.
>
> omap4-var-stk-om44.dts replace the old and very limited omap4-var-som.dts.
>
> [1] http://www.variscite.com/products/system-on-module-som/cortex-a9/var-som-om44-cpu-ti-omap-4-omap4460
> [2] http://www.variscite.com/products/single-board-computers/var-om44customboard
>
> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
> ---
> .../devicetree/bindings/arm/omap/omap.txt | 3 +
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm/boot/dts/Makefile | 2 +-
> arch/arm/boot/dts/omap4-var-om44customboard.dtsi | 235 ++++++++++++++
> 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 | 16 +
> 7 files changed, 599 insertions(+), 97 deletions(-)
> create mode 100644 arch/arm/boot/dts/omap4-var-om44customboard.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
Hmm don't you still need to keep omap4-var-som.dts to build just the
core SoC module without any add-on boards?
Also, you might want to use the OMAP4_CORE_IOPAD and OMAP4_WKUP_IOPAD
macros in include/dt-bindings/pinctrl/omap.h to be able to check the
registers against the TRM easier as you can use the physical register
offset listed in the TRM.
Regards,
Tony
next prev parent reply other threads:[~2014-04-18 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 15:10 [PATCH 0/4] Support for Variscite OM44 modules and boards Joachim Eastwood
2014-04-18 15:10 ` [PATCH 1/4] ARM: dts: Add support for OMAP4 Variscite OM44 family Joachim Eastwood
2014-04-18 15:57 ` Tony Lindgren [this message]
2014-04-18 16:17 ` Joachim Eastwood
2014-04-18 17:29 ` Tony Lindgren
2014-04-18 18:03 ` Joachim Eastwood
2014-04-18 22:44 ` Tony Lindgren
2014-04-30 1:24 ` Joachim Eastwood
2014-04-30 6:19 ` Tomi Valkeinen
2014-04-18 15:10 ` [PATCH 2/4] ARM: dts: Add support for OMAP4 VAR-DVK-OM44 Joachim Eastwood
2014-04-18 15:10 ` [PATCH 3/4] ARM: dts: Add VAR-SOM-OM44 WLAN nodes Joachim Eastwood
2014-04-18 15:10 ` [PATCH 4/4] ARM: OMAP2+: Use pdata quirks for wl12xx on VAR-STK/DVK-OM44 Joachim Eastwood
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=20140418155721.GC5354@atomide.com \
--to=tony@atomide.com \
--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).