diff options
author | Christian Lütke-Stetzkamp <christian@lkamp.de> | 2018-04-24 20:01:26 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-04-25 15:36:19 +0200 |
commit | 0b78f05d510b01e353481f5bccb63661d2cb5c32 (patch) | |
tree | 562f4115a687b74f6644c60bb01dad77a640bfe2 /fs/crypto | |
parent | 78f350830eb3b1b5c03c591f58b22110454556c5 (diff) |
staging: mt7621-mmc: Correct datatypes for io and sanitize io access
Current code discard the address space information on the base address
of the mmc controller, that causes sparse warnings. It uses the raw
read write function, that is correct for the mips architecture (little
endian), but for portability the non-raw function should be used. Also
the clear/set bit macros do direct memory access, that is also correct
for mips, but not portable.
So the type of the base address is changed to void __iomem *, that is
the type returned by the ioremap function. The set/clear bit macros
are changed to functions, that use the portable read and write
functions. The use of the raw access functions is changed to use the
non-raw ones.
Signed-off-by: Christian Lütke-Stetzkamp <christian@lkamp.de>
Reviewed-by: NeilBrown <neil@brown.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/crypto')
0 files changed, 0 insertions, 0 deletions