drivers/remoteproc/stm32_rproc.c:139:20: sparse: sparse: incorrect type in argument 1 (different address spaces)

kernel test robot
2023-11-29T10:46:21Z

head: 18d46e76d7c2eedd8577fae67e3f1d4db25018b0
commit: 03bd158e1535e68bcd2b1e095b0ebcad7c84bd20 remoteproc: stm32: use correct format strings on 64-bit
date: 5 months ago
config: microblaze-randconfig-r034-20230909 (https://download.01.org/0day-ci/archive/20231129/202311291623.yfI5obiT-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20231129/202311291623.yfI5obiT-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311291623.yfI5obiT-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/stm32_rproc.c:122:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *va @@ got void [noderef] __iomem * @@
drivers/remoteproc/stm32_rproc.c:122:12: sparse: expected void *va
drivers/remoteproc/stm32_rproc.c:122:12: sparse: got void [noderef] __iomem *
>> drivers/remoteproc/stm32_rproc.c:139:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *va @@
drivers/remoteproc/stm32_rproc.c:139:20: sparse: expected void volatile [noderef] __iomem *addr