drivers/remoteproc/ti_k3_r5_remoteproc.c:711:17: sparse: sparse: cast removes address space '__iomem' of expression

From: kernel test robot
Date: Wed Apr 06 2022 - 22:26:40 EST


tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3e732ebf7316ac83e8562db7e64cc68aec390a18
commit: 1168af40b1ad8cb2e78f4a70869fa4a076320e4f remoteproc: k3-r5: Add support for IPC-only mode for all R5Fs
date: 4 weeks ago
config: arm64-randconfig-s032-20220406 (https://download.01.org/0day-ci/archive/20220407/202204071033.j2idta4V-lkp@xxxxxxxxx/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1168af40b1ad8cb2e78f4a70869fa4a076320e4f
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 1168af40b1ad8cb2e78f4a70869fa4a076320e4f
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/remoteproc/ lib/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@xxxxxxxxx>


sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/ti_k3_r5_remoteproc.c:476:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *p @@ got void [noderef] __iomem *cpu_addr @@
drivers/remoteproc/ti_k3_r5_remoteproc.c:476:28: sparse: expected void *p
drivers/remoteproc/ti_k3_r5_remoteproc.c:476:28: sparse: got void [noderef] __iomem *cpu_addr
drivers/remoteproc/ti_k3_r5_remoteproc.c:479:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *p @@ got void [noderef] __iomem *cpu_addr @@
drivers/remoteproc/ti_k3_r5_remoteproc.c:479:28: sparse: expected void *p
drivers/remoteproc/ti_k3_r5_remoteproc.c:479:28: sparse: got void [noderef] __iomem *cpu_addr
>> drivers/remoteproc/ti_k3_r5_remoteproc.c:711:17: sparse: sparse: cast removes address space '__iomem' of expression

vim +/__iomem +711 drivers/remoteproc/ti_k3_r5_remoteproc.c

681
682 /*
683 * This function implements the .get_loaded_rsc_table() callback and is used
684 * to provide the resource table for the booted R5F in IPC-only mode. The K3 R5F
685 * firmwares follow a design-by-contract approach and are expected to have the
686 * resource table at the base of the DDR region reserved for firmware usage.
687 * This provides flexibility for the remote processor to be booted by different
688 * bootloaders that may or may not have the ability to publish the resource table
689 * address and size through a DT property. This callback is invoked only in
690 * IPC-only mode.
691 */
692 static struct resource_table *k3_r5_get_loaded_rsc_table(struct rproc *rproc,
693 size_t *rsc_table_sz)
694 {
695 struct k3_r5_rproc *kproc = rproc->priv;
696 struct device *dev = kproc->dev;
697
698 if (!kproc->rmem[0].cpu_addr) {
699 dev_err(dev, "memory-region #1 does not exist, loaded rsc table can't be found");
700 return ERR_PTR(-ENOMEM);
701 }
702
703 /*
704 * NOTE: The resource table size is currently hard-coded to a maximum
705 * of 256 bytes. The most common resource table usage for K3 firmwares
706 * is to only have the vdev resource entry and an optional trace entry.
707 * The exact size could be computed based on resource table address, but
708 * the hard-coded value suffices to support the IPC-only mode.
709 */
710 *rsc_table_sz = 256;
> 711 return (struct resource_table *)kproc->rmem[0].cpu_addr;
712 }
713

--
0-DAY CI Kernel Test Service
https://01.org/lkp