From: "Shah, Tanmay" <tanmays@amd.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
"Shah, Tanmay" <tanmay.shah@amd.com>
Cc: linux-remoteproc <linux-remoteproc@vger.kernel.org>
Subject: Re: Fwd: [linux-next:master 2763/15982] drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Mon, 24 Aug 2026 13:58:45 -0500 [thread overview]
Message-ID: <4df5138c-dc37-4d09-9a9f-06b6453384fc@amd.com> (raw)
In-Reply-To: <CANLsYkxW7EeVQwH6pJryE6PzfVzVVodGCKbFOmycqffRLZ_SLA@mail.gmail.com>
On 8/19/2026 10:33 AM, Mathieu Poirier wrote:
> Tanmay - please have a look.
>
Ack. I will reproduce and send a fix.
Thanks,
Tanmay
> ---------- Forwarded message ---------
> From: kernel test robot <lkp@intel.com>
> Date: Tue, 18 Aug 2026 at 10:59
> Subject: [linux-next:master 2763/15982]
> drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse: sparse:
> incorrect type in initializer (different address spaces)
> To: Tanmay Shah <tanmay.shah@amd.com>
> Cc: <oe-kbuild-all@lists.linux.dev>, Mathieu Poirier
> <mathieu.poirier@linaro.org>
>
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: e6664f2b33db9b6811eb4cec109f06cb2b4f458d
> commit: 5ae3dc078874693a0a7fd1cf32660bd473fe544d [2763/15982]
> remoteproc: xlnx: Add crash detection mechanism
> config: arm64-randconfig-r111-20260818
> (https://download.01.org/0day-ci/archive/20260819/202608190009.uCbYi1Y5-lkp@intel.com/config)
> compiler: clang version 24.0.0git
> (https://github.com/llvm/llvm-project
> 844a18e753e822736c9805ab779144b647a2c186)
> rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
> sparse: v0.6.5-rc1
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20260819/202608190009.uCbYi1Y5-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/202608190009.uCbYi1Y5-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> drivers/remoteproc/xlnx_r5_remoteproc.c:571:20: sparse: sparse:
> cast removes address space '__iomem' of expression
> drivers/remoteproc/xlnx_r5_remoteproc.c:749:17: sparse: sparse:
> cast removes address space '__iomem' of expression
> drivers/remoteproc/xlnx_r5_remoteproc.c:773:24: sparse: sparse:
> cast removes address space '__iomem' of expression
> drivers/remoteproc/xlnx_r5_remoteproc.c:797:25: sparse: sparse:
> cast removes address space '__iomem' of expression
>>> drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void *rsc_offset @@ got void [noderef] __iomem * @@
> drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse:
> expected void *rsc_offset
> drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse: got
> void [noderef] __iomem *
>
> vim +837 drivers/remoteproc/xlnx_r5_remoteproc.c
>
> 832
> 833 static int zynqmp_r5_handle_rsc(struct rproc *rproc, u32
> rsc_type, void *rsc,
> 834 int offset, int avail)
> 835 {
> 836 struct zynqmp_r5_core *r5_core = rproc->priv;
> > 837 void *rsc_offset = (r5_core->rsc_tbl_va + offset);
> 838
> 839 if (rsc_type != XLNX_RPROC_FW_CRASH_REPORT)
> 840 return RSC_IGNORED;
> 841
> 842 r5_core->crash_report = rsc_offset;
> 843 /* reset all values */
> 844 r5_core->crash_report->crashed = false;
> 845 r5_core->crash_report->crash_reason = 0;
> 846 r5_core->crash_report->crash_reason_str[0] = '\0';
> 847
> 848 return RSC_HANDLED;
> 849 }
> 850
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-24 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 16:58 [linux-next:master 2763/15982] drivers/remoteproc/xlnx_r5_remoteproc.c:837:49: sparse: sparse: incorrect type in initializer (different address spaces) kernel test robot
2026-08-19 15:33 ` Fwd: " Mathieu Poirier
2026-08-24 18:58 ` Shah, Tanmay [this message]
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=4df5138c-dc37-4d09-9a9f-06b6453384fc@amd.com \
--to=tanmays@amd.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=tanmay.shah@amd.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.