aboutsummaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorRussell King - ARM Linux <linux@arm.linux.org.uk>2012-11-18 16:29:44 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-12-10 10:45:07 -0800
commit31a2aa119dd0b760b0931e6dfa0847a697d6d7d6 (patch)
tree37a7e3ce25434993760ca261c598a57f59dca298 /mm
parent3bbbcb136d00b0718e63f7fd633f098e0889c3d1 (diff)
downloadkernel_samsung_smdk4412-31a2aa119dd0b760b0931e6dfa0847a697d6d7d6.zip
kernel_samsung_smdk4412-31a2aa119dd0b760b0931e6dfa0847a697d6d7d6.tar.gz
kernel_samsung_smdk4412-31a2aa119dd0b760b0931e6dfa0847a697d6d7d6.tar.bz2
Dove: Attempt to fix PMU/RTC interrupts
commit 5d3df935426271016b895aecaa247101b4bfa35e upstream. Fix the acknowledgement of PMU interrupts on Dove: some Dove hardware has not been sensibly designed so that interrupts can be handled in a race free manner. The PMU is one such instance. The pending (aka 'cause') register is a bunch of RW bits, meaning that these bits can be both cleared and set by software (confirmed on the Armada-510 on the cubox.) Hardware sets the appropriate bit when an interrupt is asserted, and software is required to clear the bits which are to be processed. If we write ~(1 << bit), then we end up asserting every other interrupt except the one we're processing. So, we need to do a read-modify-write cycle to clear the asserted bit. However, any interrupts which occur in the middle of this cycle will also be written back as zero, which will also clear the new interrupts. The upshot of this is: there is _no_ way to safely clear down interrupts in this register (and other similarly behaving interrupt pending registers on this device.) The patch below at least stops us creating new interrupts. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Jason Cooper <jason@lakedaemon.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions