summaryrefslogtreecommitdiffstats
path: root/arch/m68k/Kconfig.bus
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@linux-m68k.org>2018-04-05 23:55:11 +1000
committerGreg Ungerer <gerg@linux-m68k.org>2018-05-28 09:45:27 +1000
commitbe39cbcbd6cc94ed0e6daf3637cc092641254cf3 (patch)
tree95b17fb51ea556553e6a5ae2f37952851f839191 /arch/m68k/Kconfig.bus
parent4d53037876277fbba10f47de7b90d3a873c5d12b (diff)
downloadlinux-stable-be39cbcbd6cc94ed0e6daf3637cc092641254cf3.tar.gz
linux-stable-be39cbcbd6cc94ed0e6daf3637cc092641254cf3.tar.bz2
linux-stable-be39cbcbd6cc94ed0e6daf3637cc092641254cf3.zip
m68k: fix ioremapping for internal ColdFire peripherals
The ColdFire SoC internal peripherals are mapped into virtual address space using the ACR registers of the cache control unit. This means we are using a 1:1 physical:virtual mapping for them that does not rely on page table mappings. We can quickly determine if we are accessing an internal peripheral device given the physical or vitrual address using the same range check. The implications of this mapping is that an ioremap should return the physical address as the virtual mapping __iomem cookie as well. So fix ioremap() to deal with this on ColdFire. Of course you need to take care of this in the iounmap() path as well. Reported-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org> Reviewed-by: Angelo Dureghello <angelo@sysam.it> Tested-by: Angelo Dureghello <angelo@sysam.it>
Diffstat (limited to 'arch/m68k/Kconfig.bus')
0 files changed, 0 insertions, 0 deletions