Add a new RTC driver for recent mvebu SoCs
Subsystems (4)
v4 cover Add a new RTC driver for recent mvebu SoCs
Hi,
The Marvell Armada 38x SoCs contains an RTC which differs from the RTC used in the other mvebu SoCs until now. This forth version of the patch set adds support for this new IP and enable it in the Device Tree of the Armada 38x SoC.
Thanks,
Gr?gory
Changelog
v3 -> v4:
- Formatted the device tree binding documentation in a better way
- Renamed the soc-int regmap to rtc-soc because this group of register was not only about the interrupt.
- Fixed the rtc_delayed_write function. I found the exact description of the WA to use, and the wait should really be after the write.
v2 -> v3:
- Fixed the reg-names description in the dt binding documentation
- Used the delayed version of the writel in everyplace.
v1 -> v2:
- Used reg-names to identify the registers in the device tree
- Changed the space into tab in the MAINTAINERS file
- Emphasized that the 5s wait was only needed between two consecutive writes
- Reduced the wait in the set_time function, 100ms were enough
- If no interrupt was available, then disable the alarm related functions
- Fixed the critical sections
- Updated the mvebu_v7_defconfig by enabling the new RTC support
Gregory CLEMENT (5):
rtc: armada38x: Add the device tree binding documentation drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs
MAINTAINERS: Add the RTC driver for the Armada38x
ARM: mvebu: add Device Tree description of RTC on Armada 38x
ARM: mvebu: enable Armada 38x RTC driver in mvebu_v7_defconfig
.../devicetree/bindings/rtc/armada-380-rtc.txt | 22 ++ MAINTAINERS | 1 + arch/arm/boot/dts/armada-38x.dtsi | 7 + arch/arm/configs/mvebu_v7_defconfig | 1 + drivers/rtc/Kconfig | 10 + drivers/rtc/Makefile | 1 + drivers/rtc/rtc-armada38x.c | 320 +++++++++++++++++++++ 7 files changed, 362 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/armada-380-rtc.txt create mode 100644 drivers/rtc/rtc-armada38x.c
Signature · 1 line
1.9.1
PATCH v4 1/5 rtc: armada38x: Add the device tree binding documentation
The Armada 38x SoCs come with a new RTC which differs from the one used in the other mvebu SoCs until now. This patch describes the binding of this RTC.
--- .../devicetree/bindings/rtc/armada-380-rtc.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/armada-380-rtc.txt
Documentation/devicetree/bindings/rtc/armada-380-rtc.txt new file +22 -0
@@ -0,0 +1,22 @@ +* Real Time Clock of the Armada 38x SoCs + +RTC controller for the Armada 38x SoCs + +Required properties: +- compatible : Should be "marvell,armada-380-rtc" +- reg: a list of base address and size pairs, one for each entry in + reg-names +- reg names: should contain: + * "rtc" for the RTC registers + * "rtc-soc" for the SoC related registers and among them the one + related to the interrupt. +- interrupts: IRQ line for the RTC. + +Example: + +rtc at a3800 { + compatible = "marvell,armada-380-rtc"; + reg = <0xa3800 0x20>, <0x184a0 0x0c>; + reg-names = "rtc", "rtc-soc"; + interrupts = <GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>; +};
Signature · 1 line
1.9.1
PATCH v4 2/5 drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs
In reply to Gregory CLEMENTThe new mvebu SoCs come with a new RTC driver. This patch adds the support for this new IP which is currently found in the Armada 38x SoCs.
This RTC provides two alarms, but only the first one is used in the driver. The RTC also allows using periodic interrupts.
--- drivers/rtc/Kconfig | 10 ++ drivers/rtc/Makefile | 1 + drivers/rtc/rtc-armada38x.c | 320 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 331 insertions(+) create mode 100644 drivers/rtc/rtc-armada38x.c
drivers/rtc/Kconfig +10 -0
@@ -1269,6 +1269,16 @@ config RTC_DRV_MV This driver can also be built as a module. If so, the module will be called rtc-mv. +config RTC_DRV_ARMADA38X + tristate "Armada 38x Marvell SoC RTC" + depends on ARCH_MVEBU + help + If you say yes here you will get support for the in-chip RTC + that can be found in the Armada 38x Marvell's SoC device + + This driver can also be built as a module. If so, the module + will be called armada38x-rtc. + config RTC_DRV_PS3 tristate "PS3 RTC" depends on PPC_PS3
drivers/rtc/Makefile +1 -0
@@ -24,6 +24,7 @@ obj-$(CONFIG_RTC_DRV_88PM860X) += rtc-88pm860x.o obj-$(CONFIG_RTC_DRV_88PM80X) += rtc-88pm80x.o obj-$(CONFIG_RTC_DRV_AB3100) += rtc-ab3100.o obj-$(CONFIG_RTC_DRV_AB8500) += rtc-ab8500.o +obj-$(CONFIG_RTC_DRV_ARMADA38X) += rtc-armada38x.o obj-$(CONFIG_RTC_DRV_AS3722) += rtc-as3722.o obj-$(CONFIG_RTC_DRV_AT32AP700X)+= rtc-at32ap700x.o obj-$(CONFIG_RTC_DRV_AT91RM9200)+= rtc-at91rm9200.o
drivers/rtc/rtc-armada38x.c new file +320 -0
320 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v4 2/5 drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs
Hi Gregory,
Quoted 7 lines · Gregory CLEMENT
The new mvebu SoCs come with a new RTC driver. This patch adds the support for this new IP which is currently found in the Armada 38x SoCs.
This RTC provides two alarms, but only the first one is used in the driver. The RTC also allows using periodic interrupts.
Quoted 7 lines
Signed-off-by Gregory CLEMENT <[email protected]>--- drivers/rtc/Kconfig | 10 ++ drivers/rtc/Makefile | 1 + drivers/rtc/rtc-armada38x.c | 320 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 331 insertions(+) create mode 100644 drivers/rtc/rtc-armada38x.c
FWIW:
Cheers,
a+
PATCH v4 3/5 MAINTAINERS: Add the RTC driver for the Armada38x
In reply to Gregory CLEMENTPut it in the mvebu entry.
--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
@@ -1157,6 +1157,7 @@ M: Sebastian Hesselbarth <[email protected]> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers) S: Maintained F: arch/arm/mach-mvebu/ +F: drivers/rtc/armada38x-rtc ARM/Marvell Berlin SoC support M: Sebastian Hesselbarth <[email protected]>
Signature · 1 line
1.9.1
PATCH v4 4/5 ARM: mvebu: add Device Tree description of RTC on Armada 38x
In reply to Gregory CLEMENTThe Marvell Armada 38x SoCs contains an RTC which differs from the RTC used in the other mvebu SoCs until now. This commit adds the Device Tree description of this interface at the SoC level.
--- arch/arm/boot/dts/armada-38x.dtsi | 7 +++++++ 1 file changed, 7 insertions(+)
arch/arm/boot/dts/armada-38x.dtsi +7 -0
@@ -466,6 +466,13 @@ clocks = <&gateclk 4>; }; + rtc at a3800 { + compatible = "marvell,armada-380-rtc"; + reg = <0xa3800 0x20>, <0x184a0 0x0c>; + reg-names = "rtc", "rtc-soc"; + interrupts = <GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>; + }; + sata at a8000 { compatible = "marvell,armada-380-ahci"; reg = <0xa8000 0x2000>;
Signature · 1 line
1.9.1
PATCH v4 5/5 ARM: mvebu: enable Armada 38x RTC driver in mvebu_v7_defconfig
In reply to Gregory CLEMENTNow that the Armada 38x RTC driver has been pushed, let's enable it in mvebu_v7_defconfig.
--- arch/arm/configs/mvebu_v7_defconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm/configs/mvebu_v7_defconfig +1 -0
@@ -112,6 +112,7 @@ CONFIG_LEDS_TRIGGER_HEARTBEAT=y CONFIG_RTC_CLASS=y CONFIG_RTC_DRV_S35390A=y CONFIG_RTC_DRV_MV=y +CONFIG_RTC_DRV_ARMADA38X=y CONFIG_DMADEVICES=y CONFIG_MV_XOR=y # CONFIG_IOMMU_SUPPORT is not set
Signature · 1 line
1.9.1
v4 cover Add a new RTC driver for recent mvebu SoCs
In reply to Gregory CLEMENTHi,
Quoted 6 lines · Gregory CLEMENT
Hi,
The Marvell Armada 38x SoCs contains an RTC which differs from the RTC used in the other mvebu SoCs until now. This forth version of the patch set adds support for this new IP and enable it in the Device Tree of the Armada 38x SoC.
This last version of this series have been sent 3 weeks ago. Is there an hope to be merged in 3.20 ?
Should they go through via Andrew Morten's tree ?
Thanks,
Gregory
Quoted 51 lines
Thanks,
Gr?gory
Changelog
v3 -> v4:
- Formatted the device tree binding documentation in a better way
- Renamed the soc-int regmap to rtc-soc because this group of register was not only about the interrupt.
- Fixed thertc_delayed_writefunction. I found the exact description of the WA to use, and the wait should really be after the write.v2 -> v3:
- Fixed the reg-names description in the dt binding documentation
- Used the delayed version of the writel in everyplace.v1 -> v2:
- Used reg-names to identify the registers in the device tree
- Changed the space into tab in theMAINTAINERSfile
- Emphasized that the 5s wait was only needed between two consecutive writes
- Reduced the wait in theset_timefunction, 100ms were enough
- If no interrupt was available, then disable the alarm related functions
- Fixed the critical sections
- Updated themvebu_v7_defconfigby enabling the new RTC supportGregory CLEMENT (5):
rtc: armada38x: Add the device tree binding documentationdrivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs
MAINTAINERS: Add the RTC driver for the Armada38x
ARM: mvebu: add Device Tree description of RTC on Armada 38x
ARM: mvebu: enable Armada 38x RTC driver inmvebu_v7_defconfig.../devicetree/bindings/rtc/armada-380-rtc.txt | 22 ++ MAINTAINERS | 1 + arch/arm/boot/dts/armada-38x.dtsi | 7 + arch/arm/configs/mvebu_v7_defconfig | 1 + drivers/rtc/Kconfig | 10 + drivers/rtc/Makefile | 1 + drivers/rtc/rtc-armada38x.c | 320 +++++++++++++++++++++ 7 files changed, 362 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/armada-380-rtc.txt create mode 100644 drivers/rtc/rtc-armada38x.c
Signature · 4 lines
Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com