From: kernel test robot <lkp@intel.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/remoteproc/mtk_scp.c:306:39: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Wed, 18 Nov 2020 14:03:28 +0800 [thread overview]
Message-ID: <202011181425.dYApaLAF-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8318 bytes --]
Hi Bjorn,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0fa8ee0d9ab95c9350b8b84574824d9a384a9f7d
commit: 141bc97c1bfe31397b2a12e5676d0c2692c8e07e remoteproc/mediatek: Remove non-standard dsb()
date: 5 weeks ago
config: mips-randconfig-s032-20201117 (attached as .config)
compiler: mips-linux-gcc (GCC) 9.3.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.3-107-gaf3512a6-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141bc97c1bfe31397b2a12e5676d0c2692c8e07e
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 141bc97c1bfe31397b2a12e5676d0c2692c8e07e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
command-line: note: in included file:
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_ACQUIRE redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_SEQ_CST redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_ACQ_REL redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_RELEASE redefined
builtin:0:0: sparse: this was the original definition
>> drivers/remoteproc/mtk_scp.c:306:39: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void *addr @@
>> drivers/remoteproc/mtk_scp.c:306:39: sparse: expected void volatile [noderef] __iomem *mem
drivers/remoteproc/mtk_scp.c:306:39: sparse: got void *addr
drivers/remoteproc/mtk_scp.c:307:19: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void *addr @@
drivers/remoteproc/mtk_scp.c:307:19: sparse: expected void volatile [noderef] __iomem *mem
drivers/remoteproc/mtk_scp.c:307:19: sparse: got void *addr
drivers/remoteproc/mtk_scp.c:314:19: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void *addr @@
drivers/remoteproc/mtk_scp.c:314:19: sparse: expected void volatile [noderef] __iomem *mem
drivers/remoteproc/mtk_scp.c:314:19: sparse: got void *addr
drivers/remoteproc/mtk_scp.c:316:39: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void *addr @@
drivers/remoteproc/mtk_scp.c:316:39: sparse: expected void volatile [noderef] __iomem *mem
drivers/remoteproc/mtk_scp.c:316:39: sparse: got void *addr
drivers/remoteproc/mtk_scp.c:327:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:327:44: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:327:44: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:328:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:328:44: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:328:44: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:329:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:329:44: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:329:44: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:330:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:330:44: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:330:44: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:331:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:331:44: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:331:44: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:431:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:431:45: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:431:45: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:432:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:432:45: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:432:45: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:433:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:433:45: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:433:45: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:434:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:434:45: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:434:45: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:435:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/mtk_scp.c:435:45: sparse: expected void *addr
drivers/remoteproc/mtk_scp.c:435:45: sparse: got void [noderef] __iomem *
drivers/remoteproc/mtk_scp.c:559:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *cpu_addr @@ got void * @@
drivers/remoteproc/mtk_scp.c:559:23: sparse: expected void [noderef] __iomem *cpu_addr
drivers/remoteproc/mtk_scp.c:559:23: sparse: got void *
drivers/remoteproc/mtk_scp.c:572:56: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void *cpu_addr @@ got void [noderef] __iomem *cpu_addr @@
drivers/remoteproc/mtk_scp.c:572:56: sparse: expected void *cpu_addr
drivers/remoteproc/mtk_scp.c:572:56: sparse: got void [noderef] __iomem *cpu_addr
vim +306 drivers/remoteproc/mtk_scp.c
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 300
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 301 static void mt8192_power_on_sram(void *addr)
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 302 {
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 303 int i;
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 304
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 305 for (i = 31; i >= 0; i--)
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 @306 writel(GENMASK(i, 0), addr);
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 307 writel(0, addr);
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 308 }
fd0b6c1ff85a489 Pi-Hsun Shih 2020-09-21 309
:::::: The code at line 306 was first introduced by commit
:::::: fd0b6c1ff85a489bcf1bcf58af64da1aeffd39f0 remoteproc/mediatek: Add support for mt8192 SCP
:::::: TO: Pi-Hsun Shih <pihsun@chromium.org>
:::::: CC: Bjorn Andersson <bjorn.andersson@linaro.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33903 bytes --]
next reply other threads:[~2020-11-18 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 6:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-01 14:33 drivers/remoteproc/mtk_scp.c:306:39: sparse: sparse: incorrect type in argument 2 (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=202011181425.dYApaLAF-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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