From: kernel test robot <lkp@intel.com>
To: Suman Anna <s-anna@ti.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: drivers/remoteproc/ti_k3_dsp_remoteproc.c:432:17: sparse: sparse: cast removes address space '__iomem' of expression
Date: Tue, 19 Apr 2022 12:30:17 +0800 [thread overview]
Message-ID: <202204191250.9zqeCPVs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b2d229d4ddb17db541098b83524d901257e93845
commit: b8431920391d36c273f63a29eab0dfc7e884dd17 remoteproc: k3-dsp: Add support for IPC-only mode for all K3 DSPs
date: 5 weeks ago
config: arm64-randconfig-s031-20220419 (https://download.01.org/0day-ci/archive/20220419/202204191250.9zqeCPVs-lkp@intel.com/config)
compiler: aarch64-linux-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.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8431920391d36c273f63a29eab0dfc7e884dd17
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout b8431920391d36c273f63a29eab0dfc7e884dd17
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/remoteproc/
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/remoteproc/ti_k3_dsp_remoteproc.c:432:17: sparse: sparse: cast removes address space '__iomem' of expression
vim +/__iomem +432 drivers/remoteproc/ti_k3_dsp_remoteproc.c
402
403 /*
404 * This function implements the .get_loaded_rsc_table() callback and is used
405 * to provide the resource table for a booted DSP in IPC-only mode. The K3 DSP
406 * firmwares follow a design-by-contract approach and are expected to have the
407 * resource table at the base of the DDR region reserved for firmware usage.
408 * This provides flexibility for the remote processor to be booted by different
409 * bootloaders that may or may not have the ability to publish the resource table
410 * address and size through a DT property. This callback is invoked only in
411 * IPC-only mode.
412 */
413 static struct resource_table *k3_dsp_get_loaded_rsc_table(struct rproc *rproc,
414 size_t *rsc_table_sz)
415 {
416 struct k3_dsp_rproc *kproc = rproc->priv;
417 struct device *dev = kproc->dev;
418
419 if (!kproc->rmem[0].cpu_addr) {
420 dev_err(dev, "memory-region #1 does not exist, loaded rsc table can't be found");
421 return ERR_PTR(-ENOMEM);
422 }
423
424 /*
425 * NOTE: The resource table size is currently hard-coded to a maximum
426 * of 256 bytes. The most common resource table usage for K3 firmwares
427 * is to only have the vdev resource entry and an optional trace entry.
428 * The exact size could be computed based on resource table address, but
429 * the hard-coded value suffices to support the IPC-only mode.
430 */
431 *rsc_table_sz = 256;
> 432 return (struct resource_table *)kproc->rmem[0].cpu_addr;
433 }
434
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-19 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 4:30 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-04 11:58 drivers/remoteproc/ti_k3_dsp_remoteproc.c:432:17: sparse: sparse: cast removes address space '__iomem' of expression kernel test robot
2022-10-22 22:26 kernel test robot
2022-11-04 14:05 kernel test robot
2023-02-08 17:30 kernel test robot
2023-02-10 3:20 kernel test robot
2023-02-26 1:12 kernel test robot
2023-04-27 10:36 kernel test robot
2023-05-16 4:16 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=202204191250.9zqeCPVs-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-anna@ti.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.