On Wed, Oct 22, 2014 at 12:18:49PM +0200, Johan Hovold wrote:
On Fri, Oct 10, 2014 at 01:07:27PM -0500, Felipe Balbi wrote:
On Thu, Oct 09, 2014 at 09:06:31PM +0200, Johan Hovold wrote:
- /* clear pending irqs, and set 1/second periodic,
- * which we'll use instead of update irqs
+
On Fri, Oct 10, 2014 at 01:07:27PM -0500, Felipe Balbi wrote:
On Thu, Oct 09, 2014 at 09:06:31PM +0200, Johan Hovold wrote:
- /* clear pending irqs, and set 1/second periodic,
-* which we'll use instead of update irqs
+ /*
+* disable interrupts
+*
+* NOTE: ALARM2
On Fri, Oct 10, 2014 at 01:07:27PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Oct 09, 2014 at 09:06:31PM +0200, Johan Hovold wrote:
@@ -124,11 +138,18 @@
*/
#define OMAP_RTC_HAS_POWER_UP_RESETBIT(3)
+/*
+ * Some RTC IP revisions can control an external PMIC via the
Hi,
On Thu, Oct 09, 2014 at 09:06:31PM +0200, Johan Hovold wrote:
@@ -124,11 +138,18 @@
*/
#define OMAP_RTC_HAS_POWER_UP_RESET BIT(3)
+/*
+ * Some RTC IP revisions can control an external PMIC via the pmic_power_en
+ * pin.
+ */
+#define OMAP_RTC_HAS_PMIC_MODE BIT(4)
Add new property ti,system-power-controller to register the RTC as a
power-off handler.
Some RTC IP revisions can control an external PMIC via the pmic_power_en
pin, which can be configured to transition to OFF on ALARM2 events and
back to ON on subsequent ALARM (wakealarm) events.
This is based