mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-04 16:15:11 +00:00
0f0cfc6954
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>
30 lines
No EOL
630 B
Text
30 lines
No EOL
630 B
Text
/*
|
|
* Suppport for CompuLab SBC-T3730 with CM-T3730
|
|
*/
|
|
|
|
#include "omap3-cm-t3730.dts"
|
|
#include "omap3-sb-t35.dtsi"
|
|
|
|
/ {
|
|
model = "CompuLab SBC-T3730 with CM-T3730";
|
|
compatible = "compulab,omap3-sbc-t3730", "compulab,omap3-cm-t3730", "ti,omap36xx", "ti,omap3";
|
|
};
|
|
|
|
&gpmc {
|
|
ranges = <5 0 0x2c000000 0x01000000>,
|
|
<4 0 0x2d000000 0x01000000>;
|
|
};
|
|
|
|
&smsc2 {
|
|
pinctrl-names = "default";
|
|
pinctrl-0 = <&smsc2_pins>;
|
|
};
|
|
|
|
&omap3_pmx_core {
|
|
smsc2_pins: pinmux_smsc2_pins {
|
|
pinctrl-single,pins = <
|
|
0x86 (PIN_OUTPUT | MUX_MODE0) /* gpmc_ncs4.gpmc_ncs4 */
|
|
0xa2 (PIN_INPUT_PULLUP | MUX_MODE4) /* gpmc_wait3.gpio_65 */
|
|
>;
|
|
};
|
|
}; |