From: kernel test robot <lkp@intel.com>
To: Ben Skeggs <bskeggs@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, Dave Airlie <airlied@redhat.com>
Subject: [jfern:nova-core-experiments 154/411] drivers/gpu/drm/nouveau/nvif/dispchan.c:93:9: sparse: sparse: cast removes address space '__iomem' of expression
Date: Sat, 8 Mar 2025 16:55:03 +0800 [thread overview]
Message-ID: <202503081649.TxBe0OC5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git nova-core-experiments
head: 3b93174b3502247b0c46bd54a7cf5f4105274edb
commit: b31c153a3d075fcae5f7fd482a74b060f5365081 [154/411] drm/nouveau/nvif: rework disp "new chan" apis
config: s390-randconfig-r133-20250308 (https://download.01.org/0day-ci/archive/20250308/202503081649.TxBe0OC5-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20250308/202503081649.TxBe0OC5-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/202503081649.TxBe0OC5-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/gpu/drm/nouveau/nvif/dispchan.c:36:34: sparse: sparse: subtraction of different types can't work (different address spaces)
>> drivers/gpu/drm/nouveau/nvif/dispchan.c:93:9: sparse: sparse: cast removes address space '__iomem' of expression
drivers/gpu/drm/nouveau/nvif/dispchan.c:107:34: sparse: sparse: subtraction of different types can't work (different address spaces)
drivers/gpu/drm/nouveau/nvif/dispchan.c:189:24: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned int [usertype] *bgn @@ got void [noderef] __iomem *ptr @@
vim +/__iomem +93 drivers/gpu/drm/nouveau/nvif/dispchan.c
71
72 static int
73 nvif_dispchan_wind(struct nvif_dispchan *chan)
74 {
75 struct nvif_push *push = &chan->push;
76
77 /* Wait for GET to depart from the beginning of the push buffer to
78 * prevent writing PUT == GET, which would be ignored by HW.
79 */
80 u32 get = NVIF_RV32(chan, NV507C, GET, PTR);
81 if (get == 0) {
82 /* Corner-case, HW idle, but non-committed work pending. */
83 if (push->hw.put == 0)
84 nvif_dispchan_kick(&chan->push);
85
86 if (nvif_msec(chan->disp->device, 2000,
87 if (NVIF_TV32(chan, NV507C, GET, PTR, >, 0))
88 break;
89 ) < 0)
90 return -ETIMEDOUT;
91 }
92
> 93 PUSH_RSVD(&chan->push, PUSH_JUMP(&chan->push, 0));
94 push->hw.cur = 0;
95 return 0;
96 }
97
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-08 8:56 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=202503081649.TxBe0OC5-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=bskeggs@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.