From: kernel test robot <lkp@intel.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: oe-kbuild-all@lists.linux.dev,
Miquel Raynal <miquel.raynal@bootlin.com>,
David Regan <dregan@broadcom.com>
Subject: [mtd:nand/next 22/25] drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c:79:41: sparse: sparse: cast removes address space '__iomem' of expression
Date: Tue, 27 Feb 2024 09:34:17 +0800 [thread overview]
Message-ID: <202402270940.gmVLVRg0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next
head: 65a7f244b15684856241d04b8f3287d9124bd1ff
commit: c52c16d1bee5c3b074989e839eeceed2a0a8cc43 [22/25] mtd: rawnand: brcmnand: Add BCMBCA read data bus interface
config: riscv-randconfig-r131-20240227 (https://download.01.org/0day-ci/archive/20240227/202402270940.gmVLVRg0-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project edd4aee4dd9b5b98b2576a6f783e4086173d902a)
reproduce: (https://download.01.org/0day-ci/archive/20240227/202402270940.gmVLVRg0-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/202402270940.gmVLVRg0-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c:79:41: sparse: sparse: cast removes address space '__iomem' of expression
drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c:80:17: sparse: sparse: cast removes address space '__iomem' of expression
drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c:80:17: sparse: sparse: cast removes address space '__iomem' of expression
drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c:80:17: sparse: sparse: cast removes address space '__iomem' of expression
vim +/__iomem +79 drivers/mtd/nand/raw/brcmnand/bcmbca_nand.c
70
71 static void bcmbca_read_data_bus(struct brcmnand_soc *soc,
72 void __iomem *flash_cache, u32 *buffer, int fc_words)
73 {
74 /*
75 * memcpy can do unaligned aligned access depending on source
76 * and dest address, which is incompatible with nand cache. Fallback
77 * to the memcpy_fromio in such case
78 */
> 79 if (bcmbca_nand_is_buf_aligned((void *)flash_cache, buffer))
80 memcpy((void *)buffer, (void *)flash_cache, fc_words * 4);
81 else
82 memcpy_fromio((void *)buffer, flash_cache, fc_words * 4);
83 }
84
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-27 1:35 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=202402270940.gmVLVRg0-lkp@intel.com \
--to=lkp@intel.com \
--cc=dregan@broadcom.com \
--cc=miquel.raynal@bootlin.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=william.zhang@broadcom.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 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.