[PATCH v4 0/10] Second patchset for LPC32xx device tree conversion

From: Roland Stigge
Date: Thu Apr 19 2012 - 09:04:20 EST


This is the second patch set for device tree conversion of mach-lpc32xx. It
builds upon and requires the previously posted first set of 8 plus the GPIO
patch.

It touches different subsystems (USB/OHCI, input/touchscreen, iio/adc and
mach-lpc32) to be picked by the respective subsystem maintainer and probably
applied separately. (?)

Signed-off-by: Roland Stigge <stigge@xxxxxxxxx>

--

Applies to v3.4-rc3

Changes since v3:
* phy3250.c, clock.c: Cleaned up auxdata table by using generated device
names in clock table
* common.c: Removed trailing newline
* lpc32xx.dtsi: Documented SLC vs. MLC activation

Thanks to Arnd Bergmann for reviewing!

Roland Stigge (10):
ohci-nxp: Driver cleanup
ohci-nxp: Device tree support
ARM: LPC32xx: clock.c cleanup
ARM: LPC32xx: clock.c dma adjustment
ARM: LPC32xx: Remove obsolete platform Kconfig
input: Device tree support for LPC32xx touchscreen
iio: lpc32xx-adc: Remove driver conflict due to device tree
ARM: LPC32xx: DTS files for device tree conversion
ARM: LPC32xx: Device tree support
ARM: LPC32xx: Move common code to common.c

Documentation/devicetree/bindings/arm/lpc32xx-mic.txt | 38 +
Documentation/devicetree/bindings/arm/lpc32xx.txt | 8
Documentation/devicetree/bindings/input/touchscreen/lpc32xx-tsc.txt | 16
Documentation/devicetree/bindings/usb/ohci-nxp.txt | 16
arch/arm/Kconfig | 1
arch/arm/boot/dts/lpc32xx.dtsi | 303 ++++++++++
arch/arm/boot/dts/phy3250.dts | 115 +++
arch/arm/mach-lpc32xx/Kconfig | 26
arch/arm/mach-lpc32xx/clock.c | 77 +-
arch/arm/mach-lpc32xx/common.c | 192 ------
arch/arm/mach-lpc32xx/common.h | 14
arch/arm/mach-lpc32xx/irq.c | 78 +-
arch/arm/mach-lpc32xx/phy3250.c | 146 ++--
drivers/input/touchscreen/lpc32xx_ts.c | 10
drivers/staging/iio/adc/Kconfig | 8
drivers/usb/host/ohci-nxp.c | 55 +
16 files changed, 704 insertions(+), 399 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/