[Patch v4 0/5] Introduce keystone reset driver

From: Ivan Khoronzhuk
Date: Wed May 21 2014 - 10:30:32 EST


These patches introduce keystone reset driver.

The keystone SoC can be rebooted in several ways. By external reset
pin, by soft and by watchdogs. This driver allows software reset and reset
by one of the watchdogs. Also added opportunity to set soft/hard reset type.

Based on linux-next/master

v4..v3
Power: reset: keystone-reset: introduce keystone reset driver
- change to use syscon framework
- change to use regmap to access registers
Power: reset: add bindings for keystone reset driver
- deleted properties "reg", "reg-names"
- added properties "ti,syscon-pll", "ti,syscon-dev"
ARM: dts: keystone: update reset node to work with reset driver
- deleted properties "reg", "reg-names"
- added properties "ti,syscon-pll", "ti,syscon-dev"

v2..v3
Power: reset: keystone-reset: introduce keystone reset driver
- no functional changes, only sanity
Power: reset: add bindings for keystone reset driver
- corrected WDT numeration in examples
- extended description of wdt_list property

v1..v2
- re basedon on v3.15-rc1 without changes

Ivan Khoronzhuk (5):
Power: reset: keystone-reset: introduce keystone reset driver
Power: reset: add bindings for keystone reset driver
ARM: keystone: remove redundant reset stuff
ARM: dts: keystone: update reset node to work with reset driver
ARM: keystone: enable reset driver support

.../bindings/power/reset/keystone-reset.txt | 66 +++++++++
arch/arm/boot/dts/keystone.dtsi | 4 +-
arch/arm/configs/keystone_defconfig | 3 +
arch/arm/mach-keystone/keystone.c | 34 -----
drivers/power/reset/Kconfig | 8 ++
drivers/power/reset/Makefile | 1 +
drivers/power/reset/keystone-reset.c | 153 +++++++++++++++++++++
7 files changed, 234 insertions(+), 35 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power/reset/keystone-reset.txt
create mode 100644 drivers/power/reset/keystone-reset.c

--
1.8.3.2

--
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/