From: kernel test robot <lkp@intel.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/dma/sun6i-dma.c:244:45: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 28 Jun 2020 15:42:42 +0800 [thread overview]
Message-ID: <202006281538.RRezNsh5%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6088 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to define address spaces
date: 10 days ago
config: arm64-randconfig-s032-20200628 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-dirty
git checkout 670d0a4b10704667765f7d18f7592993d02783aa
# save the attached .config to linux build tree
make W=1 C=1 ARCH=arm64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
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 >>)
>> drivers/dma/sun6i-dma.c:244:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile *x @@ got void [noderef] __iomem *base @@
drivers/dma/sun6i-dma.c:244:45: sparse: expected void const volatile *x
drivers/dma/sun6i-dma.c:244:45: sparse: got void [noderef] __iomem *base
--
>> sound/soc/mediatek/common/mtk-afe-fe-dai.c:142:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem * @@ got unsigned char *dma_area @@
>> sound/soc/mediatek/common/mtk-afe-fe-dai.c:142:9: sparse: expected void volatile [noderef] __iomem *
sound/soc/mediatek/common/mtk-afe-fe-dai.c:142:9: sparse: got unsigned char *dma_area
--
>> sound/soc/mediatek/common/mtk-btcvsd.c:1365:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned int [usertype] *bt_reg_pkt_r @@ got void [noderef] __iomem * @@
sound/soc/mediatek/common/mtk-btcvsd.c:1365:30: sparse: expected unsigned int [usertype] *bt_reg_pkt_r
>> sound/soc/mediatek/common/mtk-btcvsd.c:1365:30: sparse: got void [noderef] __iomem *
>> sound/soc/mediatek/common/mtk-btcvsd.c:1367:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned int [usertype] *bt_reg_pkt_w @@ got void [noderef] __iomem * @@
sound/soc/mediatek/common/mtk-btcvsd.c:1367:30: sparse: expected unsigned int [usertype] *bt_reg_pkt_w
sound/soc/mediatek/common/mtk-btcvsd.c:1367:30: sparse: got void [noderef] __iomem *
>> sound/soc/mediatek/common/mtk-btcvsd.c:1369:28: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned int [usertype] *bt_reg_ctl @@ got void [noderef] __iomem * @@
sound/soc/mediatek/common/mtk-btcvsd.c:1369:28: sparse: expected unsigned int [usertype] *bt_reg_ctl
sound/soc/mediatek/common/mtk-btcvsd.c:1369:28: sparse: got void [noderef] __iomem *
--
>> drivers/mmc/host/meson-gx-mmc.c:1175:34: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *bounce_buf @@ got void [noderef] __iomem * @@
drivers/mmc/host/meson-gx-mmc.c:1175:34: sparse: expected void *bounce_buf
>> drivers/mmc/host/meson-gx-mmc.c:1175:34: sparse: got void [noderef] __iomem *
vim +244 drivers/dma/sun6i-dma.c
555859308723d8 Maxime Ripard 2014-07-17 240
555859308723d8 Maxime Ripard 2014-07-17 241 static inline void sun6i_dma_dump_chan_regs(struct sun6i_dma_dev *sdev,
555859308723d8 Maxime Ripard 2014-07-17 242 struct sun6i_pchan *pchan)
555859308723d8 Maxime Ripard 2014-07-17 243 {
42c0d54e623695 Vinod Koul 2014-07-28 @244 phys_addr_t reg = virt_to_phys(pchan->base);
555859308723d8 Maxime Ripard 2014-07-17 245
555859308723d8 Maxime Ripard 2014-07-17 246 dev_dbg(sdev->slave.dev, "Chan %d reg: %pa\n"
555859308723d8 Maxime Ripard 2014-07-17 247 "\t___en(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 248 "\tpause(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 249 "\tstart(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 250 "\t__cfg(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 251 "\t__src(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 252 "\t__dst(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 253 "\tcount(%04x): \t0x%08x\n"
555859308723d8 Maxime Ripard 2014-07-17 254 "\t_para(%04x): \t0x%08x\n\n",
555859308723d8 Maxime Ripard 2014-07-17 255 pchan->idx, ®,
555859308723d8 Maxime Ripard 2014-07-17 256 DMA_CHAN_ENABLE,
555859308723d8 Maxime Ripard 2014-07-17 257 readl(pchan->base + DMA_CHAN_ENABLE),
555859308723d8 Maxime Ripard 2014-07-17 258 DMA_CHAN_PAUSE,
555859308723d8 Maxime Ripard 2014-07-17 259 readl(pchan->base + DMA_CHAN_PAUSE),
555859308723d8 Maxime Ripard 2014-07-17 260 DMA_CHAN_LLI_ADDR,
555859308723d8 Maxime Ripard 2014-07-17 261 readl(pchan->base + DMA_CHAN_LLI_ADDR),
555859308723d8 Maxime Ripard 2014-07-17 262 DMA_CHAN_CUR_CFG,
555859308723d8 Maxime Ripard 2014-07-17 263 readl(pchan->base + DMA_CHAN_CUR_CFG),
555859308723d8 Maxime Ripard 2014-07-17 264 DMA_CHAN_CUR_SRC,
555859308723d8 Maxime Ripard 2014-07-17 265 readl(pchan->base + DMA_CHAN_CUR_SRC),
555859308723d8 Maxime Ripard 2014-07-17 266 DMA_CHAN_CUR_DST,
555859308723d8 Maxime Ripard 2014-07-17 267 readl(pchan->base + DMA_CHAN_CUR_DST),
555859308723d8 Maxime Ripard 2014-07-17 268 DMA_CHAN_CUR_CNT,
555859308723d8 Maxime Ripard 2014-07-17 269 readl(pchan->base + DMA_CHAN_CUR_CNT),
555859308723d8 Maxime Ripard 2014-07-17 270 DMA_CHAN_CUR_PARA,
555859308723d8 Maxime Ripard 2014-07-17 271 readl(pchan->base + DMA_CHAN_CUR_PARA));
555859308723d8 Maxime Ripard 2014-07-17 272 }
555859308723d8 Maxime Ripard 2014-07-17 273
:::::: The code at line 244 was first introduced by commit
:::::: 42c0d54e62369584f2491f072f405602ff504e0e dmaengine: sun6i: fix build failure on x86, xilinx targets
:::::: TO: Vinod Koul <vinod.koul@intel.com>
:::::: CC: Vinod Koul <vinod.koul@intel.com>
---
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: 38247 bytes --]
next reply other threads:[~2020-06-28 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 7:42 kernel test robot [this message]
2020-08-24 19:12 kernel test robot
2020-11-15 7:00 kernel test robot
2021-11-20 0:50 kernel test robot
2021-11-25 15:56 kernel test robot
2022-01-01 14:27 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=202006281538.RRezNsh5%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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
Powered by JetHome