From: kernel test robot <lkp@intel.com>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6299/12162] drivers/remoteproc/stm32_rproc.c:139:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 25 Jun 2023 04:42:13 +0800 [thread overview]
Message-ID: <202306250422.UozRcpxb-lkp@intel.com> (raw)
Hi Alexandre,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8d2be868b42c08290509c60515865f4de24ea704
commit: 9e4e24414cc6b45bd887d746a59691e295431ddf [6299/12162] arm64: introduce STM32 family on Armv8 architecture
config: arm64-randconfig-s043-20230625 (https://download.01.org/0day-ci/archive/20230625/202306250422.UozRcpxb-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230625/202306250422.UozRcpxb-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/202306250422.UozRcpxb-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
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 +139 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
13140de09cc2dd Fabien Dessenne 2019-05-14 121 dev_dbg(dev, "map memory: %pa+%x\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)) {
13140de09cc2dd Fabien Dessenne 2019-05-14 124 dev_err(dev, "Unable to map memory region: %pa+%x\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 139 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
reply other threads:[~2023-06-24 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202306250422.UozRcpxb-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox