Hi Tony,
If this is not too late, could you please pull the various OMAP device tree patches?
This series assume that all the drivers adaptation to DT are already merged and is based on my previous interrupt controller series.
It means it has a strong dependency with i2c tree, mfd tree and rtc tree.
I added as well the patch from Vaibhav for EVM early DT support.
Thanks,
Benoit
The following changes since commit 89f504c5376bb09bd08bb3a3fe4c80949a594069:
Benoit Cousson (1):
ARM: OMAP2+: board-generic: Use of_irq_init API
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git for_3.3/dt_i2c_twl_evm
Benoit Cousson (9):
ARM: OMAP2+: pm: Do not init statically the SR and voltage layer with DT
arm/dts: OMAP4: Add i2c controller nodes
arm/dts: OMAP3: Add i2c controller nodes
arm/dts: twl6030: Add DTS file for twl6030 PMIC
arm/dts: twl4030: Add DTS file for twl4030 PM + Audio IC
arm/dts: omap4-panda: Add twl6030 and i2c EEPROM
arm/dts: omap4-sdp: Add twl6030, i2c3 and i2c4 devices
arm/dts: omap3-beagle: Add twl4030 and i2c EEPROM
ARM: OMAP2+: board-generic: Remove i2c static init
Vaibhav Hiremath (1):
arm/dts: Add support for TI OMAP3 EVM board
arch/arm/boot/dts/omap3-beagle.dts | 29 +++++++++++++++++++
arch/arm/boot/dts/omap3-evm.dts | 20 +++++++++++++
arch/arm/boot/dts/omap3.dtsi | 21 ++++++++++++++
arch/arm/boot/dts/omap4-panda.dts | 34 ++++++++++++++++++++++
arch/arm/boot/dts/omap4-sdp.dts | 53 +++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/omap4.dtsi | 28 ++++++++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 21 ++++++++++++++
arch/arm/boot/dts/twl6030.dtsi | 22 ++++++++++++++
arch/arm/mach-omap2/board-generic.c | 48 +------------------------------
arch/arm/mach-omap2/pm.c | 8 +++++
10 files changed, 238 insertions(+), 46 deletions(-)
create mode 100644 arch/arm/boot/dts/omap3-evm.dts
create mode 100644 arch/arm/boot/dts/twl4030.dtsi
create mode 100644 arch/arm/boot/dts/twl6030.dtsi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
