summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorRosen Penev <rosenp@gmail.com>2026-07-16 13:29:48 -0700
committerVinod Koul <vkoul@kernel.org>2026-07-17 17:50:19 +0530
commit68b7fbc235290937e4e2daa097896b6b94618f15 (patch)
treed87d4c8ad8dab5cb2b4abea396c0d399b01f549a /include/linux
parent416e9fd2059631405031aaa033a7a7851467be86 (diff)
dma: fsl_raid: keep MMIO bases as void __iomem and cast at access
The fsl_re_ctrl and fsl_re_chan_cfg structures describe memory-mapped RAID Engine registers accessed only via ioread32be()/iowrite32be(), yet the pointers to them (re_regs in struct fsl_re_drv_private, and jrregs in struct fsl_re_chan) were not __iomem-qualified, so sparse emitted "different address spaces" warnings for every register access. Store both MMIO bases as a plain void __iomem * and derive jrregs with void __iomem * arithmetic from re_regs, rather than carrying typed register struct pointers through the driver. Each function that touches the registers introduces a local typed pointer (struct fsl_re_ctrl __iomem *ctrl) and uses ->field, which is the idiomatic kernel pattern and keeps the registers' __iomem qualification intact. Reported-by: kernel test robot <lkp@intel.com> Link: https://lore.kernel.org/oe-kbuild-all/202008111749.yy85rFMD%25lkp@intel.com/ Assisted-by: opencode:hy3-free Signed-off-by: Rosen Penev <rosenp@gmail.com> Reviewed-by: Frank Li <Frank.Li@nxp.com> Link: https://patch.msgid.link/20260716202949.677290-4-rosenp@gmail.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions