summaryrefslogtreecommitdiff
path: root/.mailmap
diff options
context:
space:
mode:
authorMian Yousaf Kaukab <ykaukab@suse.de>2021-06-29 17:06:43 +0200
committerAlexandre Belloni <alexandre.belloni@bootlin.com>2021-07-10 02:58:31 +0200
commit2f8619846755176a6720c71d580ffd09394a74bc (patch)
treec832f56ee347eb057be9f040d67bde40b2047aaa /.mailmap
parent37aadf9b2a7ea64a358ea7532d7f477fe6837ef1 (diff)
rtc: pcf2127: handle timestamp interrupts
commit 03623b4b041c ("rtc: pcf2127: add tamper detection support") added support for timestamp interrupts. However they are not being handled in the irq handler. If a timestamp interrupt occurs it results in kernel disabling the interrupt and displaying the call trace: [ 121.145580] irq 78: nobody cared (try booting with the "irqpoll" option) ... [ 121.238087] [<00000000c4d69393>] irq_default_primary_handler threaded [<000000000a90d25b>] pcf2127_rtc_irq [rtc_pcf2127] [ 121.248971] Disabling IRQ #78 Handle timestamp interrupts in pcf2127_rtc_irq(). Save time stamp before clearing TSF1 and TSF2 flags so that it can't be overwritten. Set a flag to mark if the timestamp is valid and only report to sysfs if the flag is set. To mimic the hardware behavior, don’t save another timestamp until the first one has been read by the userspace. However, if the alarm irq is not configured, keep the old way of handling timestamp interrupt in the timestamp0 sysfs calls. Signed-off-by: Mian Yousaf Kaukab <ykaukab@suse.de> Reviewed-by: Bruno Thomsen <bruno.thomsen@gmail.com> Tested-by: Bruno Thomsen <bruno.thomsen@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Link: https://lore.kernel.org/r/20210629150643.31551-1-ykaukab@suse.de
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions