ARM: dts: Various OMAP2+ device-tree updates
Subsystems (6)
v2 cover ARM: dts: Various OMAP2+ device-tree updates
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent before individually but re-sending here as a complete series for v3.10.
This is based upon Benoit's for_3.10/dts branch [1]. Branch available here [2].
V2 changes:
- Rebased on Benoit's for_3.10/dts branch
- Squashed patches adding support for OMAP3430 SDP board and patch to add flash support for OMAP3430 SDP board.
[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
[2] git://github.com/jonhunter/linux.git omap-dt-for-v3.10
Jon Hunter (8):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
ARM: dts: Add OMAP2 gpio bindings
ARM: dts: OMAP3+: Correct gpio #interrupts-cells property
ARM: dts: OMAP3: Add reg and interrupt properties for gpio
ARM: dts: OMAP3: Add support for OMAP3430 SDP board
arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/omap2.dtsi | 17 ++++ arch/arm/boot/dts/omap2420.dtsi | 55 +++++++++++++ arch/arm/boot/dts/omap2430.dtsi | 66 ++++++++++++++++ arch/arm/boot/dts/omap3.dtsi | 70 +++++++++++++++-- arch/arm/boot/dts/omap3430-sdp.dts | 141 ++++++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap4-panda-es.dts | 2 + arch/arm/boot/dts/omap4.dtsi | 64 +++++++++++++-- arch/arm/boot/dts/omap4460.dtsi | 18 +++++ arch/arm/boot/dts/omap5.dtsi | 68 ++++++++++++++-- arch/arm/mach-omap2/pmu.c | 14 +++- 11 files changed, 493 insertions(+), 23 deletions(-) create mode 100644 arch/arm/boot/dts/omap3430-sdp.dts create mode 100644 arch/arm/boot/dts/omap4460.dtsi
Signature · 1 line
1.7.10.4
PATCH v2 1/8 ARM: OMAP2+: Prepare for device-tree PMU support
If device-tree is present, then do not create the PMU device from within the OMAP specific PMU code. This is required to allow device-tree to create the PMU device from the PMU device-tree node.
PMU is not currently supported for OMAP4430 (due to a dependency on having a cross-trigger interface driver) and so ensure that this indicated on boot with or without device-tree.
--- arch/arm/mach-omap2/pmu.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
arch/arm/mach-omap2/pmu.c +11 -3
@@ -11,6 +11,8 @@* the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. */ +#include <linux/of.h> +#include <asm/pmu.h> #include "soc.h"
@@ -63,6 +65,15 @@ static int __init omap_init_pmu(void)unsigned oh_num;char **oh_names; +/* XXX Remove this check when the CTI driver is available */ +if (cpu_is_omap443x ()) { +pr_info ("ARM PMU: not yet supported on OMAP4430 due to missing CTI driver\n" ); +return 0 ; + } + +if (of_have_populated_dt ()) +return 0 ; +/* * To create an ARM-PMU device the following HWMODs * are required for the various OMAP2+ devices.
@@ -75,9 +86,6 @@ static int __init omap_init_pmu(void)if (cpu_is_omap443x ()) { oh_num =ARRAY_SIZE (omap4430_pmu_oh_names); oh_names = omap4430_pmu_oh_names; -/* XXX Remove the next two lines when CTI driver available */ -pr_info ("ARM PMU: not yet supported on OMAP4430 due to missing CTI driver\n" ); -return 0 ; }else if (cpu_is_omap34xx () ||cpu_is_omap44xx ()) { oh_num =ARRAY_SIZE (omap3_pmu_oh_names); oh_names = omap3_pmu_oh_names;
Signature · 1 line
1.7.10.4
PATCH v2 2/8 ARM: dts: OMAP2+: Add PMU nodes
In reply to Jon HunterAdd PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
Please note that the node for OMAP4460 has been placed in a separate header file for OMAP4460, because the node is not compatible with OMAP4430. The node for OMAP4430 is not included because PMU is not currently supported on OMAP4430 due to the absence of a cross-trigger interface driver.
--- arch/arm/boot/dts/omap2.dtsi | 5 +++++ arch/arm/boot/dts/omap3.dtsi | 6 ++++++ arch/arm/boot/dts/omap4-panda-es.dts | 2 ++ arch/arm/boot/dts/omap4460.dtsi | 18 ++++++++++++++++++ 4 files changed, 31 insertions(+) create mode 100644 arch/arm/boot/dts/omap4460.dtsi
arch/arm/boot/dts/omap2.dtsi +5 -0
@@ -26,6 +26,11 @@ }; }; + pmu { + compatible = "arm,arm1136-pmu"; + interrupts = <3>; + }; + soc { compatible = "ti,omap-infra"; mpu {
arch/arm/boot/dts/omap3.dtsi +6 -0
@@ -26,6 +26,12 @@ }; }; + pmu { + compatible = "arm,cortex-a8-pmu"; + interrupts = <3>; + ti,hwmods = "debugss"; + }; + /* * The soc node represents the soc top level view. It is uses for IPs * that are not memory mapped in the MPU view or for the MPU itself.
arch/arm/boot/dts/omap4-panda-es.dts +2 -0
@@ -5,7 +5,9 @@ * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. */ + /include/ "omap4-panda.dts" +/include/ "omap4460.dtsi" /* Audio routing is differnet between PandaBoard4430 and PandaBoardES */ &sound {
arch/arm/boot/dts/omap4460.dtsi new file +18 -0
@@ -0,0 +1,18 @@ +/* + * Device Tree Source for OMAP4460 SoC + * + * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ + * + * This file is licensed under the terms of the GNU General Public License + * version 2. This program is licensed "as is" without any warranty of any + * kind, whether express or implied. + */ + +/ { + pmu { + compatible = "arm,cortex-a9-pmu"; + interrupts = <0 54 0x4>, + <0 55 0x4>; + ti,hwmods = "debugss"; + }; +};
Signature · 1 line
1.7.10.4
PATCH v2 3/8 ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
In reply to Jon HunterAdd SDMA controller binding for OMAP2+ devices and populate DMA client information for SPI and MMC peripheral on OMAP3+ devices. Please note that OMAP24xx devices do not have SPI and MMC bindings available yet and so DMA client information is not populated.
--- arch/arm/boot/dts/omap2.dtsi | 12 ++++++++++++ arch/arm/boot/dts/omap3.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap4.dtsi | 41 +++++++++++++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap5.dtsi | 41 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 134 insertions(+)
arch/arm/boot/dts/omap2.dtsi +12 -0
@@ -54,6 +54,18 @@ reg = <0x480FE000 0x1000>; }; + sdma: dma-controller at 48056000 { + compatible = "ti,omap2430-sdma", "ti,omap2420-sdma"; + reg = <0x48056000 0x1000>; + interrupts = <12>, + <13>, + <14>, + <15>; + #dma-cells = <1>; + #dma-channels = <32>; + #dma-requests = <64>; + }; + uart1: serial at 4806a000 { compatible = "ti,omap2-uart"; ti,hwmods = "uart1";
arch/arm/boot/dts/omap3.dtsi +40 -0
@@ -81,6 +81,18 @@ reg = <0x48200000 0x1000>; }; + sdma: dma-controller at 48056000 { + compatible = "ti,omap3630-sdma", "ti,omap3430-sdma"; + reg = <0x48056000 0x1000>; + interrupts = <12>, + <13>, + <14>, + <15>; + #dma-cells = <1>; + #dma-channels = <32>; + #dma-requests = <96>; + }; + omap3_pmx_core: pinmux at 48002030 { compatible = "ti,omap3-padconf", "pinctrl-single"; reg = <0x48002030 0x05cc>;
@@ -198,6 +210,16 @@ #size-cells = <0>; ti,hwmods = "mcspi1"; ti,spi-num-cs = <4>; + dmas = <&sdma 35>, + <&sdma 36>, + <&sdma 37>, + <&sdma 38>, + <&sdma 39>, + <&sdma 40>, + <&sdma 41>, + <&sdma 42>; + dma-names = "tx0", "rx0", "tx1", "rx1", + "tx2", "rx2", "tx3", "rx3"; }; mcspi2: spi at 4809a000 {
@@ -206,6 +228,11 @@ #size-cells = <0>; ti,hwmods = "mcspi2"; ti,spi-num-cs = <2>; + dmas = <&sdma 43>, + <&sdma 44>, + <&sdma 45>, + <&sdma 46>; + dma-names = "tx0", "rx0", "tx1", "rx1"; }; mcspi3: spi at 480b8000 {
@@ -214,6 +241,11 @@ #size-cells = <0>; ti,hwmods = "mcspi3"; ti,spi-num-cs = <2>; + dmas = <&sdma 15>, + <&sdma 16>, + <&sdma 23>, + <&sdma 24>; + dma-names = "tx0", "rx0", "tx1", "rx1"; }; mcspi4: spi at 480ba000 {
@@ -222,22 +254,30 @@ #size-cells = <0>; ti,hwmods = "mcspi4"; ti,spi-num-cs = <1>; + dmas = <&sdma 70>, <&sdma 71>; + dma-names = "tx0", "rx0"; }; mmc1: mmc at 4809c000 { compatible = "ti,omap3-hsmmc"; ti,hwmods = "mmc1"; ti,dual-volt; + dmas = <&sdma 61>, <&sdma 62>; + dma-names = "tx", "rx"; }; mmc2: mmc at 480b4000 { compatible = "ti,omap3-hsmmc"; ti,hwmods = "mmc2"; + dmas = <&sdma 47>, <&sdma 48>; + dma-names = "tx", "rx"; }; mmc3: mmc at 480ad000 { compatible = "ti,omap3-hsmmc"; ti,hwmods = "mmc3"; + dmas = <&sdma 77>, <&sdma 78>; + dma-names = "tx", "rx"; }; wdt2: wdt at 48314000 {
arch/arm/boot/dts/omap4.dtsi +41 -0
101 lines not on this page · raw message
arch/arm/boot/dts/omap5.dtsi +41 -0
101 lines not on this page · raw message
Signature · 1 line
1.7.10.4
PATCH v2 4/8 ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
In reply to Jon HunterAdd the device-tree node for GPMC on OMAP2, OMAP4 and OMAP5 devices.
--- arch/arm/boot/dts/omap2420.dtsi | 11 +++++++++++ arch/arm/boot/dts/omap2430.dtsi | 11 +++++++++++ arch/arm/boot/dts/omap4.dtsi | 11 +++++++++++ arch/arm/boot/dts/omap5.dtsi | 11 +++++++++++ 4 files changed, 44 insertions(+)
arch/arm/boot/dts/omap2420.dtsi +11 -0
@@ -29,6 +29,17 @@ pinctrl-single,function-mask = <0x3f>; }; + gpmc: gpmc at 6800a000 { + compatible = "ti,omap2420-gpmc"; + reg = <0x6800a000 0x1000>; + #address-cells = <2>; + #size-cells = <1>; + interrupts = <20>; + gpmc,num-cs = <8>; + gpmc,num-waitpins = <4>; + ti,hwmods = "gpmc"; + }; + mcbsp1: mcbsp at 48074000 { compatible = "ti,omap2420-mcbsp"; reg = <0x48074000 0xff>;
arch/arm/boot/dts/omap2430.dtsi +11 -0
@@ -29,6 +29,17 @@ pinctrl-single,function-mask = <0x3f>; }; + gpmc: gpmc at 6e000000 { + compatible = "ti,omap2430-gpmc"; + reg = <0x6e000000 0x1000>; + #address-cells = <2>; + #size-cells = <1>; + interrupts = <20>; + gpmc,num-cs = <8>; + gpmc,num-waitpins = <4>; + ti,hwmods = "gpmc"; + }; + mcbsp1: mcbsp at 48074000 { compatible = "ti,omap2430-mcbsp"; reg = <0x48074000 0xff>;
arch/arm/boot/dts/omap4.dtsi +11 -0
@@ -196,6 +196,17 @@ #interrupt-cells = <1>; }; + gpmc: gpmc at 50000000 { + compatible = "ti,omap4430-gpmc"; + reg = <0x50000000 0x1000>; + #address-cells = <2>; + #size-cells = <1>; + interrupts = <0 20 0x4>; + gpmc,num-cs = <8>; + gpmc,num-waitpins = <4>; + ti,hwmods = "gpmc"; + }; + uart1: serial at 4806a000 { compatible = "ti,omap4-uart"; reg = <0x4806a000 0x100>;
arch/arm/boot/dts/omap5.dtsi +11 -0
@@ -208,6 +208,17 @@ #interrupt-cells = <1>; }; + gpmc: gpmc at 50000000 { + compatible = "ti,omap4430-gpmc"; + reg = <0x50000000 0x1000>; + #address-cells = <2>; + #size-cells = <1>; + interrupts = <0 20 0x4>; + gpmc,num-cs = <8>; + gpmc,num-waitpins = <4>; + ti,hwmods = "gpmc"; + }; + i2c1: i2c at 48070000 { compatible = "ti,omap4-i2c"; reg = <0x48070000 0x100>;
Signature · 1 line
1.7.10.4
PATCH v2 5/8 ARM: dts: Add OMAP2 gpio bindings
In reply to Jon HunterAdd gpios bindings for OMAP2420 and OMAP2430 devices.
--- arch/arm/boot/dts/omap2420.dtsi | 44 +++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap2430.dtsi | 55 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 99 insertions(+)
arch/arm/boot/dts/omap2420.dtsi +44 -0
@@ -29,6 +29,50 @@ pinctrl-single,function-mask = <0x3f>; }; + gpio1: gpio at 48018000 { + compatible = "ti,omap2-gpio"; + reg = <0x48018000 0x200>; + interrupts = <29>; + ti,hwmods = "gpio1"; + #gpio-cells = <2>; + gpio-controller; + #interrupt-cells = <2>; + interrupt-controller; + }; + + gpio2: gpio at 4801a000 { + compatible = "ti,omap2-gpio"; + reg = <0x4801a000 0x200>; + interrupts = <30>; + ti,hwmods = "gpio2"; + #gpio-cells = <2>; + gpio-controller; + #interrupt-cells = <2>; + interrupt-controller; + }; + + gpio3: gpio at 4801c000 { + compatible = "ti,omap2-gpio"; + reg = <0x4801c000 0x200>; + interrupts = <31>; + ti,hwmods = "gpio3"; + #gpio-cells = <2>; + gpio-controller; + #interrupt-cells = <2>; + interrupt-controller; + }; + + gpio4: gpio at 4801e000 { + compatible = "ti,omap2-gpio"; + reg = <0x4801e000 0x200>; + interrupts = <32>; + ti,hwmods = "gpio4"; + #gpio-cells = <2>; + gpio-controller; + #interrupt-cells = <2>; + interrupt-controller; + }; + gpmc: gpmc at 6800a000 { compatible = "ti,omap2420-gpmc"; reg = <0x6800a000 0x1000>;
arch/arm/boot/dts/omap2430.dtsi +55 -0
61 lines not on this page · raw message
Signature · 1 line
1.7.10.4
PATCH v2 6/8 ARM: dts: OMAP3+: Correct gpio #interrupts-cells property
In reply to Jon HunterThe OMAP gpio binding documention [1] states that the #interrupts-cells property for gpio controllers should be 2. Currently, for OMAP3+ devices the #interrupt-cells is set to 1. By setting this property to 2, it allows clients to pass a 2nd parameter indicating the sensitivity (level or edge) and polarity (high or low) of the interrupt. The OMAP gpio controllers support these options and so update the #interrupt-cells property for OMAP3+ devices to 2.
[1] Documentation/devicetree/bindings/gpio/gpio-omap.txt
--- arch/arm/boot/dts/omap3.dtsi | 12 ++++++------ arch/arm/boot/dts/omap4.dtsi | 12 ++++++------ arch/arm/boot/dts/omap5.dtsi | 16 ++++++++-------- 3 files changed, 20 insertions(+), 20 deletions(-)
arch/arm/boot/dts/omap3.dtsi +6 -6
@@ -117,7 +117,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio2: gpio at 49050000 {
@@ -126,7 +126,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio3: gpio at 49052000 {
@@ -135,7 +135,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio4: gpio at 49054000 {
@@ -144,7 +144,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio5: gpio at 49056000 {
@@ -153,7 +153,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio6: gpio at 49058000 {
@@ -162,7 +162,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; uart1: serial at 4806a000 {
arch/arm/boot/dts/omap4.dtsi +6 -6
@@ -138,7 +138,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio2: gpio at 48055000 {
@@ -149,7 +149,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio3: gpio at 48057000 {
@@ -160,7 +160,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio4: gpio at 48059000 {
@@ -171,7 +171,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio5: gpio at 4805b000 {
@@ -182,7 +182,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio6: gpio at 4805d000 {
@@ -193,7 +193,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpmc: gpmc at 50000000 {
arch/arm/boot/dts/omap5.dtsi +8 -8
@@ -128,7 +128,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio2: gpio at 48055000 {
@@ -139,7 +139,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio3: gpio at 48057000 {
@@ -150,7 +150,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio4: gpio at 48059000 {
@@ -161,7 +161,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio5: gpio at 4805b000 {
@@ -172,7 +172,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio6: gpio at 4805d000 {
@@ -183,7 +183,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio7: gpio at 48051000 {
@@ -194,7 +194,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpio8: gpio at 48053000 {
@@ -205,7 +205,7 @@ gpio-controller; #gpio-cells = <2>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; }; gpmc: gpmc at 50000000 {
Signature · 1 line
1.7.10.4
PATCH v2 7/8 ARM: dts: OMAP3: Add reg and interrupt properties for gpio
In reply to Jon HunterThe OMAP3 gpio bindings are currently missing the reg and interrupt properties and so add these properties.
--- arch/arm/boot/dts/omap3.dtsi | 12 ++++++++++++ 1 file changed, 12 insertions(+)
arch/arm/boot/dts/omap3.dtsi +12 -0
@@ -113,6 +113,8 @@ gpio1: gpio at 48310000 { compatible = "ti,omap3-gpio"; + reg = <0x48310000 0x200>; + interrupts = <29>; ti,hwmods = "gpio1"; gpio-controller; #gpio-cells = <2>;
@@ -122,6 +124,8 @@ gpio2: gpio at 49050000 { compatible = "ti,omap3-gpio"; + reg = <0x49050000 0x200>; + interrupts = <30>; ti,hwmods = "gpio2"; gpio-controller; #gpio-cells = <2>;
@@ -131,6 +135,8 @@ gpio3: gpio at 49052000 { compatible = "ti,omap3-gpio"; + reg = <0x49052000 0x200>; + interrupts = <31>; ti,hwmods = "gpio3"; gpio-controller; #gpio-cells = <2>;
@@ -140,6 +146,8 @@ gpio4: gpio at 49054000 { compatible = "ti,omap3-gpio"; + reg = <0x49054000 0x200>; + interrupts = <32>; ti,hwmods = "gpio4"; gpio-controller; #gpio-cells = <2>;
@@ -149,6 +157,8 @@ gpio5: gpio at 49056000 { compatible = "ti,omap3-gpio"; + reg = <0x49056000 0x200>; + interrupts = <33>; ti,hwmods = "gpio5"; gpio-controller; #gpio-cells = <2>;
@@ -158,6 +168,8 @@ gpio6: gpio at 49058000 { compatible = "ti,omap3-gpio"; + reg = <0x49058000 0x200>; + interrupts = <34>; ti,hwmods = "gpio6"; gpio-controller; #gpio-cells = <2>;
Signature · 1 line
1.7.10.4
PATCH v2 8/8 ARM: dts: OMAP3: Add support for OMAP3430 SDP board
In reply to Jon HunterAdds basic device-tree support for OMAP3430 SDP board which has 256MB of RAM, 128MB ONENAND flash, 256MB NAND flash and uses the TWL4030 power management IC.
--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/omap3430-sdp.dts | 141 ++++++++++++++++++++++++++++++++++++ 2 files changed, 142 insertions(+) create mode 100644 arch/arm/boot/dts/omap3430-sdp.dts
arch/arm/boot/dts/Makefile +1 -0
@@ -115,6 +115,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \ imx28-tx28.dtb dtb-$(CONFIG_ARCH_NOMADIK) += ste-nomadik-s8815.dtb dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \ + omap3430-sdp.dtb \ omap3-beagle.dtb \ omap3-beagle-xm.dtb \ omap3-evm.dtb \
arch/arm/boot/dts/omap3430-sdp.dts new file +141 -0
141 lines not on this page · raw message
Signature · 1 line
1.7.10.4
v2 cover ARM: dts: Various OMAP2+ device-tree updates
In reply to Jon HunterHi Jon,
Quoted 8 lines · Jon Hunter
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent before individually but re-sending here as a complete series for v3.10.
This is based upon Benoit's for_3.10/dts branch [1]. Branch available here [2].
Quoted 7 lines
V2 changes:
- Rebased on Benoit's for_3.10/dts branch
- Squashed patches adding support for OMAP3430 SDP board and patch to add flash support for OMAP3430 SDP board.[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
[2]git://github.com/jonhunter/linux.gitomap-dt-for-v3.10
Thanks for the repost. I've just applied your branch in my for_3.10/dts branch.
Regards,
Benoit
Quoted 25 lines
Jon Hunter (8):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
ARM: dts: Add OMAP2 gpio bindings
ARM: dts: OMAP3+: Correct gpio #interrupts-cells property
ARM: dts: OMAP3: Add reg and interrupt properties for gpio
ARM: dts: OMAP3: Add support for OMAP3430 SDP boardarch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/omap2.dtsi | 17 ++++ arch/arm/boot/dts/omap2420.dtsi | 55 +++++++++++++ arch/arm/boot/dts/omap2430.dtsi | 66 ++++++++++++++++ arch/arm/boot/dts/omap3.dtsi | 70 +++++++++++++++-- arch/arm/boot/dts/omap3430-sdp.dts | 141 ++++++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap4-panda-es.dts | 2 + arch/arm/boot/dts/omap4.dtsi | 64 +++++++++++++-- arch/arm/boot/dts/omap4460.dtsi | 18 +++++ arch/arm/boot/dts/omap5.dtsi | 68 ++++++++++++++-- arch/arm/mach-omap2/pmu.c | 14 +++- 11 files changed, 493 insertions(+), 23 deletions(-) create mode 100644 arch/arm/boot/dts/omap3430-sdp.dts create mode 100644 arch/arm/boot/dts/omap4460.dtsi
v2 cover ARM: dts: Various OMAP2+ device-tree updates
Hi Benoit,
Quoted 16 lines · Benoit Cousson
Hi Jon,
Quoted 13 lines · Jon Hunter
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent before individually but re-sending here as a complete series for v3.10.
This is based upon Benoit's for_3.10/dts branch [1]. Branch available here [2].
V2 changes:
- Rebased on Benoit's for_3.10/dts branch
- Squashed patches adding support for OMAP3430 SDP board and patch to add flash support for OMAP3430 SDP board.
Quoted 5 lines
Quoted 2 lines
[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
[2]git://github.com/jonhunter/linux.gitomap-dt-for-v3.10Thanks for the repost. I've just applied your branch in my for_3.10/dts branch.
I think you missed below patch which is needed for gpmc nand to work fine. Without this patch nand will not work on OMAP3430 SDP board.
Jon Hunter:-
ARM: OMAP2+: Fix-up gpmc merge error
Thanks,
Anil
v2 cover ARM: dts: Various OMAP2+ device-tree updates
Hi Anil,
Quoted 22 lines · Anil Kumar
Hi Benoit,
Quoted 19 lines · Benoit Cousson
Hi Jon,
Quoted 15 lines · Jon Hunter
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent before individually but re-sending here as a complete series for v3.10.
This is based upon Benoit's for_3.10/dts branch [1]. Branch available here [2].
V2 changes:
- Rebased on Benoit's for_3.10/dts branch
- Squashed patches adding support for OMAP3430 SDP board and patch to add flash support for OMAP3430 SDP board.[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
[2]git://github.com/jonhunter/linux.gitomap-dt-for-v3.10
Quoted 8 lines
Quoted 2 lines
Thanks for the repost. I've just applied your branch in my for_3.10/dts branch.
I think you missed below patch which is needed for gpmc nand to work fine. Without this patch nand will not work on OMAP3430 SDP board.
Jon Hunter:-
ARM: OMAP2+: Fix-up gpmc merge error
Well, that patch is not part of Jon's series and it looks like it was posted for 3.9-rc3.
BTW, Paul W is just reporting a regression about that patch.
Anyway, I'll rebase on top of -rc3 to get the latest fixes.
Regards,
Benoit