[PATCH 00/12] rtc: omap: fixes and power-off feature

From: Johan Hovold
Date: Thu Oct 09 2014 - 15:12:59 EST

This series fixes a few issues with the omap rtc-driver, cleans up a bit
and finally adds support for the PMIC control feature found in some
revisions of this RTC IP block.

Ultimately, this allows for powering off the Beaglebone and waking it up
again on RTC alarms.

I noticed yesterday that Lokesh Vutla recently posted some patches to
add regulator support to this driver. [1] While that series has some
issues that needs to be addressed, I still think it could be a good idea
to rebase my pmic_power_en patch on top of it as it adds some long
overdue device abstraction. That would be needed anyway in order to
support the new power-off infrastructure that's in the pipe in a clean
way. [2]

So my suggestion is to merge the first seven patches, rebase Lokesh
series on top of that, and then I rebase my final five patches on top
of that in turn. Hopefully, the new power-off handler call chain will
have stabilised by then.


[1] http://www.spinics.net/lists/devicetree/msg50869.html
[2] https://lkml.org/lkml/2014/10/7/30

Johan Hovold (12):
rtc: omap: fix clock-source configuration
rtc: omap: fix missing wakealarm attribute
rtc: omap: fix class-device registration
rtc: omap: remove unused register-base define
rtc: omap: remove redundant debug message
rtc: omap: use dev_info and dev_dbg
rtc: omap: silence bogus power-up reset message at probe
rtc: omap: restore irq state after reading TC registers
rtc: omap: add support for pmic_power_en
rtc: omap: enable wake-up from power off
ARM: dts: am33xx: update rtc node compatible property
ARM: dts: am335x-bone-common: enable power off and rtc wake up

Documentation/devicetree/bindings/rtc/rtc-omap.txt | 9 +-
arch/arm/boot/dts/am335x-bone-common.dtsi | 4 +
arch/arm/boot/dts/am33xx.dtsi | 2 +-
drivers/rtc/rtc-omap.c | 202 ++++++++++++++++-----
4 files changed, 173 insertions(+), 44 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/