From: kernel test robot <lkp@intel.com>
To: Thangaraj Samynathan <thangaraj.s@microchip.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [broonie-spi:for-next 55/73] drivers/spi/spi-pci1xxxx.c:373:34: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Fri, 16 Feb 2024 12:32:10 +0800 [thread overview]
Message-ID: <202402161259.jvRF1aZx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
head: 0f99484fc9d2a777818fc43a32d26cded4f8e556
commit: 9538edeb72c989a4b90964ae4bba107eaf21a791 [55/73] spi: mchp-pci1xxxx: DMA support for copying data to and from SPI Buf
config: mips-randconfig-r113-20240215 (https://download.01.org/0day-ci/archive/20240216/202402161259.jvRF1aZx-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 1c10821022f1799452065fb57474e894e2562b7f)
reproduce: (https://download.01.org/0day-ci/archive/20240216/202402161259.jvRF1aZx-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/202402161259.jvRF1aZx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/spi/spi-pci1xxxx.c:369:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *base @@ got void [noderef] __iomem * @@
drivers/spi/spi-pci1xxxx.c:369:22: sparse: expected void *base
drivers/spi/spi-pci1xxxx.c:369:22: sparse: got void [noderef] __iomem *
drivers/spi/spi-pci1xxxx.c:371:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *base @@ got void [noderef] __iomem * @@
drivers/spi/spi-pci1xxxx.c:371:22: sparse: expected void *base
drivers/spi/spi-pci1xxxx.c:371:22: sparse: got void [noderef] __iomem *
>> drivers/spi/spi-pci1xxxx.c:373:34: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:373:34: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:373:34: sparse: got void *
drivers/spi/spi-pci1xxxx.c:374:26: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:374:26: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:374:26: sparse: got void *
drivers/spi/spi-pci1xxxx.c:375:46: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:375:46: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:375:46: sparse: got void *
drivers/spi/spi-pci1xxxx.c:376:46: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:376:46: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:376:46: sparse: got void *
drivers/spi/spi-pci1xxxx.c:378:21: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:378:21: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:378:21: sparse: got void *
drivers/spi/spi-pci1xxxx.c:380:21: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/spi/spi-pci1xxxx.c:380:21: sparse: expected void volatile [noderef] __iomem *mem
drivers/spi/spi-pci1xxxx.c:380:21: sparse: got void *
vim +373 drivers/spi/spi-pci1xxxx.c
362
363 static void pci1xxxx_spi_setup_dma_from_io(struct pci1xxxx_spi_internal *p,
364 dma_addr_t dma_addr, u32 len)
365 {
366 void *base;
367
368 if (!p->hw_inst)
> 369 base = p->parent->dma_offset_bar + SPI_DMA_CH0_WR_BASE;
370 else
371 base = p->parent->dma_offset_bar + SPI_DMA_CH1_WR_BASE;
372
> 373 writel(DMA_INTR_EN, base + SPI_DMA_CH_CTL1_OFFSET);
374 writel(len, base + SPI_DMA_CH_XFER_LEN_OFFSET);
375 writel(lower_32_bits(dma_addr), base + SPI_DMA_CH_DAR_LO_OFFSET);
376 writel(upper_32_bits(dma_addr), base + SPI_DMA_CH_DAR_HI_OFFSET);
377 writel(lower_32_bits(SPI_PERI_ADDR_BASE + SPI_MST_RSP_BUF_OFFSET(p->hw_inst)),
378 base + SPI_DMA_CH_SAR_LO_OFFSET);
379 writel(upper_32_bits(SPI_PERI_ADDR_BASE + SPI_MST_RSP_BUF_OFFSET(p->hw_inst)),
380 base + SPI_DMA_CH_SAR_HI_OFFSET);
381 }
382
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-16 4:32 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=202402161259.jvRF1aZx-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thangaraj.s@microchip.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;
as well as URLs for NNTP newsgroup(s).