From: kernel test robot <lkp@intel.com>
To: Julien Massot <julien.massot@iot.bzh>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: drivers/remoteproc/rcar_rproc.c:28:12: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Sat, 9 Dec 2023 21:33:20 +0800 [thread overview]
Message-ID: <202312092135.RU2Mc1xl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f2e8a57ee9036c7d5443382b6c3c09b51a92ec7e
commit: 285892a74f1370a12249f765c6a4e3b16194852e remoteproc: Add Renesas rcar driver
date: 2 years ago
config: openrisc-randconfig-r131-20231102 (https://download.01.org/0day-ci/archive/20231209/202312092135.RU2Mc1xl-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231209/202312092135.RU2Mc1xl-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/202312092135.RU2Mc1xl-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/rcar_rproc.c:28:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *va @@ got void [noderef] __iomem * @@
drivers/remoteproc/rcar_rproc.c:28:12: sparse: expected void *va
drivers/remoteproc/rcar_rproc.c:28:12: sparse: got void [noderef] __iomem *
drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *addr @@ got void *va @@
drivers/remoteproc/rcar_rproc.c:45:20: sparse: expected void [noderef] __iomem *addr
drivers/remoteproc/rcar_rproc.c:45:20: sparse: got void *va
vim +28 drivers/remoteproc/rcar_rproc.c
20
21 static int rcar_rproc_mem_alloc(struct rproc *rproc,
22 struct rproc_mem_entry *mem)
23 {
24 struct device *dev = &rproc->dev;
25 void *va;
26
27 dev_dbg(dev, "map memory: %pa+%zx\n", &mem->dma, mem->len);
> 28 va = ioremap_wc(mem->dma, mem->len);
29 if (!va) {
30 dev_err(dev, "Unable to map memory region: %pa+%zx\n",
31 &mem->dma, mem->len);
32 return -ENOMEM;
33 }
34
35 /* Update memory entry va */
36 mem->va = va;
37
38 return 0;
39 }
40
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-09 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 13:33 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-31 16:21 drivers/remoteproc/rcar_rproc.c:28:12: sparse: sparse: incorrect type in assignment (different address spaces) 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=202312092135.RU2Mc1xl-lkp@intel.com \
--to=lkp@intel.com \
--cc=julien.massot@iot.bzh \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.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;
as well as URLs for NNTP newsgroup(s).