From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Subject: drivers/remoteproc/stm32_rproc.c:122:12: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Fri, 3 Nov 2023 01:16:54 +0800 [thread overview]
Message-ID: <202311030102.xCXT8m70-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 21e80f3841c01aeaf32d7aee7bbc87b3db1aa0c6
commit: 03bd158e1535e68bcd2b1e095b0ebcad7c84bd20 remoteproc: stm32: use correct format strings on 64-bit
date: 4 months ago
config: nios2-randconfig-r132-20231102 (https://download.01.org/0day-ci/archive/20231103/202311030102.xCXT8m70-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231103/202311030102.xCXT8m70-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/202311030102.xCXT8m70-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 [noderef] __iomem *addr @@ got void *va @@
drivers/remoteproc/stm32_rproc.c:139:20: sparse: expected void [noderef] __iomem *addr
drivers/remoteproc/stm32_rproc.c:139:20: sparse: got void *va
>> drivers/remoteproc/stm32_rproc.c:644:17: sparse: sparse: cast removes address space '__iomem' of expression
vim +122 drivers/remoteproc/stm32_rproc.c
13140de09cc2dd Fabien Dessenne 2019-05-14 114
13140de09cc2dd Fabien Dessenne 2019-05-14 115 static int stm32_rproc_mem_alloc(struct rproc *rproc,
13140de09cc2dd Fabien Dessenne 2019-05-14 116 struct rproc_mem_entry *mem)
13140de09cc2dd Fabien Dessenne 2019-05-14 117 {
13140de09cc2dd Fabien Dessenne 2019-05-14 118 struct device *dev = rproc->dev.parent;
13140de09cc2dd Fabien Dessenne 2019-05-14 119 void *va;
13140de09cc2dd Fabien Dessenne 2019-05-14 120
03bd158e1535e6 Arnd Bergmann 2023-06-09 121 dev_dbg(dev, "map memory: %pad+%zx\n", &mem->dma, mem->len);
13140de09cc2dd Fabien Dessenne 2019-05-14 @122 va = ioremap_wc(mem->dma, mem->len);
13140de09cc2dd Fabien Dessenne 2019-05-14 123 if (IS_ERR_OR_NULL(va)) {
03bd158e1535e6 Arnd Bergmann 2023-06-09 124 dev_err(dev, "Unable to map memory region: %pad+0x%zx\n",
13140de09cc2dd Fabien Dessenne 2019-05-14 125 &mem->dma, mem->len);
13140de09cc2dd Fabien Dessenne 2019-05-14 126 return -ENOMEM;
13140de09cc2dd Fabien Dessenne 2019-05-14 127 }
13140de09cc2dd Fabien Dessenne 2019-05-14 128
13140de09cc2dd Fabien Dessenne 2019-05-14 129 /* Update memory entry va */
13140de09cc2dd Fabien Dessenne 2019-05-14 130 mem->va = va;
13140de09cc2dd Fabien Dessenne 2019-05-14 131
13140de09cc2dd Fabien Dessenne 2019-05-14 132 return 0;
13140de09cc2dd Fabien Dessenne 2019-05-14 133 }
13140de09cc2dd Fabien Dessenne 2019-05-14 134
13140de09cc2dd Fabien Dessenne 2019-05-14 135 static int stm32_rproc_mem_release(struct rproc *rproc,
13140de09cc2dd Fabien Dessenne 2019-05-14 136 struct rproc_mem_entry *mem)
13140de09cc2dd Fabien Dessenne 2019-05-14 137 {
13140de09cc2dd Fabien Dessenne 2019-05-14 138 dev_dbg(rproc->dev.parent, "unmap memory: %pa\n", &mem->dma);
13140de09cc2dd Fabien Dessenne 2019-05-14 @139 iounmap(mem->va);
13140de09cc2dd Fabien Dessenne 2019-05-14 140
13140de09cc2dd Fabien Dessenne 2019-05-14 141 return 0;
13140de09cc2dd Fabien Dessenne 2019-05-14 142 }
13140de09cc2dd Fabien Dessenne 2019-05-14 143
:::::: The code at line 122 was first introduced by commit
:::::: 13140de09cc2dd5e5166ad42292bb82af4e23cef remoteproc: stm32: add an ST stm32_rproc driver
:::::: TO: Fabien Dessenne <fabien.dessenne@st.com>
:::::: CC: Bjorn Andersson <bjorn.andersson@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-02 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 11:30 drivers/remoteproc/stm32_rproc.c:122:12: sparse: sparse: incorrect type in assignment (different address spaces) kernel test robot
2023-09-06 22:34 kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202311030102.xCXT8m70-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.