From: kernel test robot <lkp@intel.com>
To: "Chin-Ting Kuo" <chin-ting_kuo@aspeedtech.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [broonie-spi:for-6.20 2/42] drivers/spi/spi-aspeed-smc.c:909:17: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Mon, 18 May 2026 05:04:23 +0800 [thread overview]
Message-ID: <202605180441.uD3toFRJ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-6.20
head: 40534d19ed2afb880ecf202dab26a8e7a5808d16
commit: 04f7516ab70f7b82aae1d2830af2ee6f17f3fe98 [2/42] spi: aspeed: Add support for non-spi-mem devices
config: sh-randconfig-r132-20260518 (https://download.01.org/0day-ci/archive/20260518/202605180441.uD3toFRJ-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 10.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260518/202605180441.uD3toFRJ-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/202605180441.uD3toFRJ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-aspeed-smc.c:909:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *ptr @@ got void *dst @@
drivers/spi/spi-aspeed-smc.c:909:17: sparse: expected void const volatile [noderef] __iomem *ptr
drivers/spi/spi-aspeed-smc.c:909:17: sparse: got void *dst
drivers/spi/spi-aspeed-smc.c:939:46: sparse: sparse: cast removes address space '__iomem' of expression
drivers/spi/spi-aspeed-smc.c:1469:61: sparse: sparse: undefined identifier 'cols'
drivers/spi/spi-aspeed-smc.c:1469:61: sparse: sparse: bad constant expression type
drivers/spi/spi-aspeed-smc.c:1469:55: sparse: sparse: undefined identifier 'rows'
drivers/spi/spi-aspeed-smc.c:1469:55: sparse: sparse: bad constant expression type
vim +909 drivers/spi/spi-aspeed-smc.c
890
891 static void aspeed_spi_user_transfer_tx(struct aspeed_spi *aspi,
892 struct spi_device *spi,
893 const u8 *tx_buf, u8 *rx_buf,
894 void *dst, u32 len)
895 {
896 const struct aspeed_spi_data *data = aspi->data;
897 bool full_duplex_transfer = data->full_duplex && tx_buf == rx_buf;
898 u32 i;
899
900 if (full_duplex_transfer &&
901 !!(spi->mode & (SPI_TX_DUAL | SPI_TX_QUAD |
902 SPI_RX_DUAL | SPI_RX_QUAD))) {
903 dev_err(aspi->dev,
904 "full duplex is only supported for single IO mode\n");
905 return;
906 }
907
908 for (i = 0; i < len; i++) {
> 909 writeb(tx_buf[i], dst);
910 if (full_duplex_transfer)
911 rx_buf[i] = readb(aspi->regs + FULL_DUPLEX_RX_DATA);
912 }
913 }
914
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-17 21:04 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=202605180441.uD3toFRJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=linux-spi@vger.kernel.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