summaryrefslogtreecommitdiffstats
path: root/scripts/documentation-file-ref-check
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@linux-m68k.org>2020-06-13 17:17:52 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-08-26 10:40:55 +0200
commit7aca2f7d1710d05e7a0809ffce923e363081df25 (patch)
tree3cd88b9c39774ece17e28b6f728d1ba2df98b186 /scripts/documentation-file-ref-check
parent1a718d4caa1a0bed3cf3f37ac2815af8314002fb (diff)
downloadlinux-stable-7aca2f7d1710d05e7a0809ffce923e363081df25.tar.gz
linux-stable-7aca2f7d1710d05e7a0809ffce923e363081df25.tar.bz2
linux-stable-7aca2f7d1710d05e7a0809ffce923e363081df25.zip
m68knommu: fix overwriting of bits in ColdFire V3 cache control
[ Upstream commit bdee0e793cea10c516ff48bf3ebb4ef1820a116b ] The Cache Control Register (CACR) of the ColdFire V3 has bits that control high level caching functions, and also enable/disable the use of the alternate stack pointer register (the EUSP bit) to provide separate supervisor and user stack pointer registers. The code as it is today will blindly clear the EUSP bit on cache actions like invalidation. So it is broken for this case - and that will result in failed booting (interrupt entry and exit processing will be completely hosed). This only affects ColdFire V3 parts that support the alternate stack register (like the 5329 for example) - generally speaking new parts do, older parts don't. It has no impact on ColdFire V3 parts with the single stack pointer, like the 5307 for example. Fix the cache bit defines used, so they maintain the EUSP bit when carrying out cache actions through the CACR register. Signed-off-by: Greg Ungerer <gerg@linux-m68k.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/documentation-file-ref-check')
0 files changed, 0 insertions, 0 deletions