summaryrefslogtreecommitdiffstats
path: root/target/linux/cns3xxx/patches-3.3/108-cns3xxx_pcie-abort.patch
diff options
context:
space:
mode:
authornbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2012-10-10 11:38:58 +0000
committernbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2012-10-10 11:38:58 +0000
commit6e65867e28ad4054982e9ce04adcb60ba83099ab (patch)
tree4e15dd00380aef9f0a40541e99e0cdc8b04219bd /target/linux/cns3xxx/patches-3.3/108-cns3xxx_pcie-abort.patch
parent029910ac71c96e4e853f990925f604f8b168ec3f (diff)
cns3xxx: Fix laguna arm11mpcore watchdog
The ARM11MPCore Timer/Watchdog registers start at offset 0x600 which is where all mpcore-wdt boards point the driver base too. I believe this is wrong because 0x600 is aliased to the timer/watchdog of the 'current CPU' where 0x700 is CPU0's timer/watchdog, and 0x800 is CPU1's timer/watchdog. Thus if your timer/watchdog application is switching between CPU's it can end up writing to the wrong CPU's registers which results in random board resets from watchdog timeouts etc. This patch forces the timer/watchdog driver to use CPU0's registers always. Its my opinion that other mpcore-wdt boards should be doing the same thing. Signed-off-by: Tim Harvey <tharvey@gateworks.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33683 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/cns3xxx/patches-3.3/108-cns3xxx_pcie-abort.patch')
0 files changed, 0 insertions, 0 deletions