summaryrefslogtreecommitdiff
path: root/drivers/phy/eswin/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@linux-m68k.org>2026-04-17 23:35:52 +1000
committerGreg Ungerer <gerg@kernel.org>2026-06-08 13:15:18 +1000
commit13cb6440d88eba1c368001dd344fb86e58ea2981 (patch)
tree1e3a6ea4ff2553fb13b0810c36ac68e47cc82c56 /drivers/phy/eswin/git@git.tavy.me:linux.git
parentcd309619573247084cd3c5bde26a1bcd4ac65eb4 (diff)
m68k: coldfire: create IO access functions for internal registers
The internal peripheral registers contained in all varieties of ColdFire SoCs require simple big endian access ranging in sizes from 8, 16 and 32 bit. Currently there is a mixture of IO access methods used across the various CPU support code, some using readx/writex and some using the simpler __raw_readx/__raw_writew. The readx/writex use cases are particularly kludgy in that they contain code to differentiate internal register access and other general attached peripheral register access - say on a PCI bus. In effect this means that the readx/writex family for ColdFire is non-standard. This ultimately ends up causing problems with definitions of other IO access support functions like ioreadx/ioreadxbe/iowritex/iowritexbe which in the generic case are defined in terms of readx/writex. Create a set of internal only register access methods to ultimately replace all internal register access code. The new access functions mirror the existing readx/writex family but using the preferred 8/16/32 suffixes. Reviewed-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
Diffstat (limited to 'drivers/phy/eswin/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions