From: kernel test robot <lkp@intel.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>,
Arnd Bergmann <arnd@arndb.de>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: drivers/remoteproc/stm32_rproc.c:139:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Tue, 30 Aug 2022 12:32:32 +0800 [thread overview]
Message-ID: <202208301242.YC5114Ec-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dcf8e5633e2e69ad60b730ab5905608b756a032f
commit: d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee ARM: mm: kill unused runtime hook arch_iounmap()
date: 9 weeks ago
config: arm-randconfig-s031-20220829 (https://download.01.org/0day-ci/archive/20220830/202208301242.YC5114Ec-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm SHELL=/bin/bash drivers/remoteproc/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <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 *io_addr @@ got void *va @@
drivers/remoteproc/stm32_rproc.c:139:20: sparse: expected void volatile [noderef] __iomem *io_addr
drivers/remoteproc/stm32_rproc.c:139:20: sparse: got void *va
drivers/remoteproc/stm32_rproc.c:632:17: sparse: sparse: cast removes address space '__iomem' of expression
vim +139 drivers/remoteproc/stm32_rproc.c
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://01.org/lkp
next reply other threads:[~2022-08-30 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 6:27 drivers/remoteproc/stm32_rproc.c:139:20: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2023-07-30 0:16 kernel test robot
2023-11-08 1:04 kernel test robot
2023-11-18 3:49 kernel test robot
2023-11-29 10:44 kernel test robot
2023-12-01 12:05 kernel test robot
2023-12-05 23:34 kernel test robot
2023-12-07 21:26 kernel test robot
2023-12-14 16:40 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=202208301242.YC5114Ec-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
/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