From: kernel test robot <lkp@intel.com>
To: Daniel Baluta <daniel.baluta@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: drivers/remoteproc/imx_dsp_rproc.c:668:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 21 Mar 2026 01:17:38 +0800 [thread overview]
Message-ID: <202603210118.PhZohwTv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0e4f8f1a3d081e834be5fd0a62bdb2554fadd307
commit: a84a1e21c0678032f1185173f816cbb500a87877 remoteproc: imx_dsp_rproc: Fix multiple start/stop operations
date: 3 months ago
config: arm-randconfig-r111-20260320 (https://download.01.org/0day-ci/archive/20260321/202603210118.PhZohwTv-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260321/202603210118.PhZohwTv-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/202603210118.PhZohwTv-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/imx_dsp_rproc.c:653:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *va @@ got void [noderef] __iomem * @@
drivers/remoteproc/imx_dsp_rproc.c:653:12: sparse: expected void *va
drivers/remoteproc/imx_dsp_rproc.c:653:12: sparse: got void [noderef] __iomem *
>> drivers/remoteproc/imx_dsp_rproc.c:668:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *io_addr @@ got void *va @@
drivers/remoteproc/imx_dsp_rproc.c:668:20: sparse: expected void volatile [noderef] __iomem *io_addr
drivers/remoteproc/imx_dsp_rproc.c:668:20: sparse: got void *va
vim +668 drivers/remoteproc/imx_dsp_rproc.c
664
665 static int imx_dsp_rproc_mem_release(struct rproc *rproc,
666 struct rproc_mem_entry *mem)
667 {
> 668 iounmap(mem->va);
669
670 return 0;
671 }
672
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-20 17:17 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=202603210118.PhZohwTv-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.baluta@nxp.com \
--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
all inboxes | Powered by JetHome®