On Wed, 2 Apr 2014 12:45:38 +0100 "Opensource [Anthony Olech]"
wrote:
> Setting the alarm to a time not on a minute boundary results in repeated
> interrupts being generated by the DA9052/3 PMIC device until the kernel
> RTC core sees that the alarm has rung. Sometimes the number and frequency
On Wed, 2 Apr 2014 12:45:38 +0100 Opensource [Anthony Olech]
anthony.olech.opensou...@diasemi.com wrote:
Setting the alarm to a time not on a minute boundary results in repeated
interrupts being generated by the DA9052/3 PMIC device until the kernel
RTC core sees that the alarm has rung.
rce
> Cc: linux-kernel@vger.kernel.org; rtc-li...@googlegroups.com; David Dajun
> Chen
> Subject: [PATCH V1] drivers/rtc: da9052: ALARM causes interrupt storm
>
> Setting the alarm to a time not on a minute boundary results in repeated
> interrupts being generated by the DA9052/3
@vger.kernel.org; rtc-li...@googlegroups.com; David Dajun
Chen
Subject: [PATCH V1] drivers/rtc: da9052: ALARM causes interrupt storm
Setting the alarm to a time not on a minute boundary results in repeated
interrupts being generated by the DA9052/3 PMIC device until the kernel RTC
core sees
Setting the alarm to a time not on a minute boundary results in repeated
interrupts being generated by the DA9052/3 PMIC device until the kernel
RTC core sees that the alarm has rung. Sometimes the number and frequency
of interrupts can cause the kernel to disable the IRQ line used by the
DA9052/3
Setting the alarm to a time not on a minute boundary results in repeated
interrupts being generated by the DA9052/3 PMIC device until the kernel
RTC core sees that the alarm has rung. Sometimes the number and frequency
of interrupts can cause the kernel to disable the IRQ line used by the
DA9052/3
6 matches
Mail list logo
