devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: peng.fan@oss.nxp.com, ohad@wizery.com,
	bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
	o.rempel@pengutronix.de, robh+dt@kernel.org,
	devicetree@vger.kernel.org
Cc: kbuild-all@lists.01.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com
Subject: Re: [PATCH V10 04/10] remoteproc: add is_iomem to da_to_va
Date: Tue, 9 Feb 2021 14:30:13 +0800	[thread overview]
Message-ID: <202102091436.eZcrMhQs-lkp@intel.com> (raw)
In-Reply-To: <1612774571-6134-5-git-send-email-peng.fan@oss.nxp.com>

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

Hi,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v5.11-rc6 next-20210125]
[cannot apply to remoteproc/for-next rpmsg/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210209-081535
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: x86_64-randconfig-s032-20210209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-215-g0fb77bb6-dirty
        # https://github.com/0day-ci/linux/commit/d6d510f24530c76a045a1a3fbc56ac411fd53809
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210209-081535
        git checkout d6d510f24530c76a045a1a3fbc56ac411fd53809
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64 

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/remoteproc_coredump.c:169:53: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void const volatile [noderef] __iomem * @@     got void *[assigned] ptr @@
   drivers/remoteproc/remoteproc_coredump.c:169:53: sparse:     expected void const volatile [noderef] __iomem *
   drivers/remoteproc/remoteproc_coredump.c:169:53: sparse:     got void *[assigned] ptr

vim +169 drivers/remoteproc/remoteproc_coredump.c

   150	
   151	static void rproc_copy_segment(struct rproc *rproc, void *dest,
   152				       struct rproc_dump_segment *segment,
   153				       size_t offset, size_t size)
   154	{
   155		void *ptr;
   156		bool is_iomem;
   157	
   158		if (segment->dump) {
   159			segment->dump(rproc, segment, dest, offset, size);
   160		} else {
   161			ptr = rproc_da_to_va(rproc, segment->da + offset, size, &is_iomem);
   162			if (!ptr) {
   163				dev_err(&rproc->dev,
   164					"invalid copy request for segment %pad with offset %zu and size %zu)\n",
   165					&segment->da, offset, size);
   166				memset(dest, 0xff, size);
   167			} else {
   168				if (is_iomem)
 > 169					memcpy_fromio(dest, ptr, size);
   170				else
   171					memcpy(dest, ptr, size);
   172			}
   173		}
   174	}
   175	

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

  reply	other threads:[~2021-02-09  6:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08  8:56 [PATCH V10 00/10] remoteproc: imx_rproc: support iMX8MQ/M peng.fan
2021-02-08  8:56 ` [PATCH V10 01/10] dt-bindings: remoteproc: convert imx rproc bindings to json-schema peng.fan
2021-02-10 17:37   ` Rob Herring
2021-02-13 11:26     ` Peng Fan
2021-02-08  8:56 ` [PATCH V10 02/10] dt-bindings: remoteproc: imx_rproc: add i.MX8MQ/M support peng.fan
2021-02-08  8:56 ` [PATCH V10 03/10] remoteproc: introduce is_iomem to rproc_mem_entry peng.fan
2021-02-08  8:56 ` [PATCH V10 04/10] remoteproc: add is_iomem to da_to_va peng.fan
2021-02-09  6:30   ` kernel test robot [this message]
2021-02-08  8:56 ` [PATCH V10 05/10] remoteproc: imx_rproc: correct err message peng.fan
2021-02-08  8:56 ` [PATCH V10 06/10] remoteproc: imx_rproc: use devm_ioremap peng.fan
2021-02-08  8:56 ` [PATCH V10 07/10] remoteproc: imx_rproc: add i.MX specific parse fw hook peng.fan
2021-02-08  8:56 ` [PATCH V10 08/10] remoteproc: imx_rproc: support i.MX8MQ/M peng.fan
2021-02-08  8:56 ` [PATCH V10 09/10] remoteproc: imx_rproc: ignore mapping vdev regions peng.fan
2021-02-08  8:56 ` [PATCH V10 10/10] remoteproc: imx_proc: enable virtio/mailbox peng.fan
  -- strict thread matches above, loose matches on Subject: below --
2021-02-15 12:34 [PATCH V10 00/10] remoteproc: imx_rproc: support iMX8MQ/M peng.fan
2021-02-15 12:34 ` [PATCH V10 04/10] remoteproc: add is_iomem to da_to_va peng.fan

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=202102091436.eZcrMhQs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel@pengutronix.de \
    --cc=mathieu.poirier@linaro.org \
    --cc=o.rempel@pengutronix.de \
    --cc=ohad@wizery.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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 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).