diff options
author | Tony Lindgren <tony@atomide.com> | 2013-12-18 13:13:21 -0800 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2013-12-18 13:13:21 -0800 |
commit | 0f0cfc69547ea3e26f53e50eae2f25fe6ea1a77d (patch) | |
tree | 788e0f90131af80999abb3ccbb50e29bb035cd0c /arch/arm/mach-omap2/board-am3517evm.c | |
parent | adfe9361b236154215d4b0fc8b6d79995394b15c (diff) | |
download | blackbird-obmc-linux-0f0cfc69547ea3e26f53e50eae2f25fe6ea1a77d.tar.gz blackbird-obmc-linux-0f0cfc69547ea3e26f53e50eae2f25fe6ea1a77d.zip |
ARM: dts: Add support for sbc-3xxx with cm-t3730
This adds support for CompuLab SBC-T3530, also known as cm-t3730:
http://compulab.co.il/products/sbcs/sbc-t3530/
It seems that with the sbc-3xxx mainboard is also used on
SBC-T3517 and SBC-T3730 with just a different CPU module:
http://compulab.co.il/products/sbcs/sbc-t3517/
http://compulab.co.il/products/sbcs/sbc-t3730/
So let's add a common omap3-sb-t35.dtsi and then separate SoC
specific omap3-sbc-t3730.dts, omap3-sbc-t3530.dts and
omap3-sbc-t3517.dts.
I've tested this with SBC-T3730 as that's the only one I have.
At least serial, both Ethernet controllers, MMC, and wl12xx WLAN
work.
Note that WLAN seems to be different for SBC-T3530. And SBC-T3517
may need some changes for the EMAC Ethernet if that's used
instead of the smsc911x.
Cc: devicetree@vger.kernel.org
Cc: Mike Rapoport <mike@compulab.co.il>
Acked-by: Igor Grinberg <grinberg@compulab.co.il>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/board-am3517evm.c')
0 files changed, 0 insertions, 0 deletions