Hi everyone, This patch series introduces basic kernel support for Allwinner's H3 SoC, mainly basic clocks and pinctrl. It also adds interrupts, timers, watchdog, RTC, dmaengine, MMC and UARTs, which are mostly compatible to those in earlier SoCs like A23 and A31, and can simply be reused. These patches are based on Maxime's sunxi/for-next branch from git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git Patch 1 adds machine support for the H3. Patch 2 adds support for the basic clocks. The AHB1/AHB2 split could need some discussion. Patch 3 adds the pin sets for the H3 main PIO. Patch 4 adds the H3 specific parameters to the sun6i dmaengine driver. Patch 5 adds the DTSI for the H3. Patch 6 adds a DT for the Orange Pi Plus SBC, which these patches were developed and tested with. Regards, Jens Jens Kuske (6): ARM: sunxi: Introduce Allwinner H3 support clk: sunxi: Add H3 clocks support pinctrl: sunxi: Add H3 PIO controller support dmaengine: sun6i: Add support for Allwinner H3 (sun8i) variant ARM: dts: sunxi: Add Allwinner H3 DTSI ARM: dts: sun8i: Add Orange Pi Plus support Documentation/devicetree/bindings/arm/sunxi.txt | 1 + Documentation/devicetree/bindings/clock/sunxi.txt | 7 + .../devicetree/bindings/dma/sun6i-dma.txt | 5 +- .../bindings/pinctrl/allwinner,sunxi-pinctrl.txt | 1 + arch/arm/boot/dts/Makefile | 3 +- arch/arm/boot/dts/sun8i-h3-orangepi-plus.dts | 82 ++++ arch/arm/boot/dts/sun8i-h3.dtsi | 468 ++++++++++++++++++ arch/arm/mach-sunxi/Kconfig | 2 +- arch/arm/mach-sunxi/sunxi.c | 3 +- drivers/clk/sunxi/clk-sunxi.c | 46 +- drivers/dma/sun6i-dma.c | 12 + drivers/pinctrl/sunxi/Kconfig | 4 + drivers/pinctrl/sunxi/Makefile | 1 + drivers/pinctrl/sunxi/pinctrl-sun8i-h3.c | 521 +++++++++++++++++++++ 14 files changed, 1151 insertions(+), 5 deletions(-) create mode 100644 arch/arm/boot/dts/sun8i-h3-orangepi-plus.dts create mode 100644 arch/arm/boot/dts/sun8i-h3.dtsi create mode 100644 drivers/pinctrl/sunxi/pinctrl-sun8i-h3.c -- 2.3.7 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
