linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: drivers/remoteproc/ti_k3_r5_remoteproc.c:377:28: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 24 Apr 2021 21:00:17 +0800	[thread overview]
Message-ID: <202104242115.CspuZYlM-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   8db5efb83fa99e81c3f8dee92a6589b251f117f3
commit: 34f2653686fecc9bd5a4ee16724768c72953fb57 remoteproc: k3-r5: Initialize TCM memories for ECC
date:   6 months ago
config: arm64-randconfig-s032-20210424 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.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-341-g8af24329-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34f2653686fecc9bd5a4ee16724768c72953fb57
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 34f2653686fecc9bd5a4ee16724768c72953fb57
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=arm64 

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_r5_remoteproc.c:377:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void *p @@     got void [noderef] __iomem *cpu_addr @@
   drivers/remoteproc/ti_k3_r5_remoteproc.c:377:28: sparse:     expected void *p
   drivers/remoteproc/ti_k3_r5_remoteproc.c:377:28: sparse:     got void [noderef] __iomem *cpu_addr
   drivers/remoteproc/ti_k3_r5_remoteproc.c:380:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void *p @@     got void [noderef] __iomem *cpu_addr @@
   drivers/remoteproc/ti_k3_r5_remoteproc.c:380:28: sparse:     expected void *p
   drivers/remoteproc/ti_k3_r5_remoteproc.c:380:28: sparse:     got void [noderef] __iomem *cpu_addr

vim +377 drivers/remoteproc/ti_k3_r5_remoteproc.c

   346	
   347	/*
   348	 * The R5F cores have controls for both a reset and a halt/run. The code
   349	 * execution from DDR requires the initial boot-strapping code to be run
   350	 * from the internal TCMs. This function is used to release the resets on
   351	 * applicable cores to allow loading into the TCMs. The .prepare() ops is
   352	 * invoked by remoteproc core before any firmware loading, and is followed
   353	 * by the .start() ops after loading to actually let the R5 cores run.
   354	 */
   355	static int k3_r5_rproc_prepare(struct rproc *rproc)
   356	{
   357		struct k3_r5_rproc *kproc = rproc->priv;
   358		struct k3_r5_cluster *cluster = kproc->cluster;
   359		struct k3_r5_core *core = kproc->core;
   360		struct device *dev = kproc->dev;
   361		int ret;
   362	
   363		ret = (cluster->mode == CLUSTER_MODE_LOCKSTEP) ?
   364			k3_r5_lockstep_release(cluster) : k3_r5_split_release(core);
   365		if (ret) {
   366			dev_err(dev, "unable to enable cores for TCM loading, ret = %d\n",
   367				ret);
   368			return ret;
   369		}
   370	
   371		/*
   372		 * Zero out both TCMs unconditionally (access from v8 Arm core is not
   373		 * affected by ATCM & BTCM enable configuration values) so that ECC
   374		 * can be effective on all TCM addresses.
   375		 */
   376		dev_dbg(dev, "zeroing out ATCM memory\n");
 > 377		memset(core->mem[0].cpu_addr, 0x00, core->mem[0].size);
   378	
   379		dev_dbg(dev, "zeroing out BTCM memory\n");
   380		memset(core->mem[1].cpu_addr, 0x00, core->mem[1].size);
   381	
   382		return 0;
   383	}
   384	

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

             reply	other threads:[~2021-04-24 13:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 13:00 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-08  7:03 kernel test robot
2021-11-08  5:53 kernel test robot
2021-11-08  5:26 kernel test robot
2021-11-08  5:26 kernel test robot
2021-09-29  0:28 kernel test robot
2021-09-28 16:26 kernel test robot
2021-09-14 23:35 kernel test robot
2021-09-14 15:48 kernel test robot
2021-08-29  8:43 kernel test robot
2021-07-23 15:19 kernel test robot
2021-04-05  1:51 kernel test robot
2021-02-07 21:02 kernel test robot
2021-01-24 10:43 kernel test robot
2020-12-09 12:02 kernel test robot
2020-11-17 20:50 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=202104242115.CspuZYlM-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=mathieu.poirier@linaro.org \
    --cc=s-anna@ti.com \
    --subject='Re: drivers/remoteproc/ti_k3_r5_remoteproc.c:377:28: sparse: sparse: incorrect type in argument 1 (different address spaces)' \
    /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

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).