All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [broonie-misc:spi-5.15 28/30] drivers/spi/spi-rockchip-sfc.c:456:17: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 21 Aug 2021 19:04:13 +0800	[thread overview]
Message-ID: <202108211908.E2zAV1ne-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3025 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git spi-5.15
head:   7a4697b201a617907e4b440ae34df601d4755bef
commit: 0b89fc0a367edab09065af722894d186bd0ccb0d [28/30] spi: rockchip-sfc: add rockchip serial flash controller
config: arm-randconfig-s032-20210821 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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-348-gf0e6938b-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git/commit/?id=0b89fc0a367edab09065af722894d186bd0ccb0d
        git remote add broonie-misc https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git
        git fetch --no-tags broonie-misc spi-5.15
        git checkout 0b89fc0a367edab09065af722894d186bd0ccb0d
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm 

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/spi/spi-rockchip-sfc.c:456:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *to @@     got void *buffer @@
   drivers/spi/spi-rockchip-sfc.c:456:17: sparse:     expected void volatile [noderef] __iomem *to
   drivers/spi/spi-rockchip-sfc.c:456:17: sparse:     got void *buffer
>> drivers/spi/spi-rockchip-sfc.c:465:17: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void const volatile [noderef] __iomem *from @@     got void *buffer @@
   drivers/spi/spi-rockchip-sfc.c:465:17: sparse:     expected void const volatile [noderef] __iomem *from
   drivers/spi/spi-rockchip-sfc.c:465:17: sparse:     got void *buffer

vim +456 drivers/spi/spi-rockchip-sfc.c

   447	
   448	static int rockchip_sfc_xfer_data_dma(struct rockchip_sfc *sfc,
   449					      const struct spi_mem_op *op, u32 len)
   450	{
   451		int ret;
   452	
   453		dev_dbg(sfc->dev, "sfc xfer_dma len=%x\n", len);
   454	
   455		if (op->data.dir == SPI_MEM_DATA_OUT)
 > 456			memcpy_toio(sfc->buffer, op->data.buf.out, len);
   457	
   458		ret = rockchip_sfc_fifo_transfer_dma(sfc, sfc->dma_buffer, len);
   459		if (!wait_for_completion_timeout(&sfc->cp, msecs_to_jiffies(2000))) {
   460			dev_err(sfc->dev, "DMA wait for transfer finish timeout\n");
   461			ret = -ETIMEDOUT;
   462		}
   463		rockchip_sfc_irq_mask(sfc, SFC_IMR_DMA);
   464		if (op->data.dir == SPI_MEM_DATA_IN)
 > 465			memcpy_fromio(op->data.buf.in, sfc->buffer, len);
   466	
   467		return ret;
   468	}
   469	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38949 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Chris Morgan <macromorgan@hotmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>, Jon Lin <jon.lin@rock-chips.com>
Subject: [broonie-misc:spi-5.15 28/30] drivers/spi/spi-rockchip-sfc.c:456:17: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 21 Aug 2021 19:04:13 +0800	[thread overview]
Message-ID: <202108211908.E2zAV1ne-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git spi-5.15
head:   7a4697b201a617907e4b440ae34df601d4755bef
commit: 0b89fc0a367edab09065af722894d186bd0ccb0d [28/30] spi: rockchip-sfc: add rockchip serial flash controller
config: arm-randconfig-s032-20210821 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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-348-gf0e6938b-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git/commit/?id=0b89fc0a367edab09065af722894d186bd0ccb0d
        git remote add broonie-misc https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git
        git fetch --no-tags broonie-misc spi-5.15
        git checkout 0b89fc0a367edab09065af722894d186bd0ccb0d
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm 

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/spi/spi-rockchip-sfc.c:456:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *to @@     got void *buffer @@
   drivers/spi/spi-rockchip-sfc.c:456:17: sparse:     expected void volatile [noderef] __iomem *to
   drivers/spi/spi-rockchip-sfc.c:456:17: sparse:     got void *buffer
>> drivers/spi/spi-rockchip-sfc.c:465:17: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void const volatile [noderef] __iomem *from @@     got void *buffer @@
   drivers/spi/spi-rockchip-sfc.c:465:17: sparse:     expected void const volatile [noderef] __iomem *from
   drivers/spi/spi-rockchip-sfc.c:465:17: sparse:     got void *buffer

vim +456 drivers/spi/spi-rockchip-sfc.c

   447	
   448	static int rockchip_sfc_xfer_data_dma(struct rockchip_sfc *sfc,
   449					      const struct spi_mem_op *op, u32 len)
   450	{
   451		int ret;
   452	
   453		dev_dbg(sfc->dev, "sfc xfer_dma len=%x\n", len);
   454	
   455		if (op->data.dir == SPI_MEM_DATA_OUT)
 > 456			memcpy_toio(sfc->buffer, op->data.buf.out, len);
   457	
   458		ret = rockchip_sfc_fifo_transfer_dma(sfc, sfc->dma_buffer, len);
   459		if (!wait_for_completion_timeout(&sfc->cp, msecs_to_jiffies(2000))) {
   460			dev_err(sfc->dev, "DMA wait for transfer finish timeout\n");
   461			ret = -ETIMEDOUT;
   462		}
   463		rockchip_sfc_irq_mask(sfc, SFC_IMR_DMA);
   464		if (op->data.dir == SPI_MEM_DATA_IN)
 > 465			memcpy_fromio(op->data.buf.in, sfc->buffer, len);
   466	
   467		return ret;
   468	}
   469	

---
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: 38949 bytes --]

             reply	other threads:[~2021-08-21 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21 11:04 kernel test robot [this message]
2021-08-21 11:04 ` [broonie-misc:spi-5.15 28/30] drivers/spi/spi-rockchip-sfc.c:456:17: sparse: sparse: incorrect type in argument 1 (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=202108211908.E2zAV1ne-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.