From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-5.15 1/1] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:416:77: sparse: sparse: Using plain integer as NULL pointer
Date: Sun, 14 Dec 2025 10:01:06 +0800 [thread overview]
Message-ID: <202512141013.VJGKROW3-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-5.15
head: 65eb5a4a2e961a9252cefa9936c221b340ba0370
commit: 595b051c83a1374b1d53ab44de1c27ac60b95979 [1/1] drm/amd/display: Change the DMCUB mailbox memory location from FB to inbox
config: i386-randconfig-061-20251212 (https://download.01.org/0day-ci/archive/20251214/202512141013.VJGKROW3-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512141013.VJGKROW3-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/202512141013.VJGKROW3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:416:77: sparse: sparse: Using plain integer as NULL pointer
vim +416 drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c
389
390 enum dmub_status dmub_srv_calc_mem_info(struct dmub_srv *dmub,
391 const struct dmub_srv_memory_params *params,
392 struct dmub_srv_fb_info *out)
393 {
394 uint8_t *cpu_base;
395 uint64_t gpu_base;
396 uint32_t i;
397
398 if (!dmub->sw_init)
399 return DMUB_STATUS_INVALID;
400
401 memset(out, 0, sizeof(*out));
402
403 if (params->region_info->num_regions != DMUB_NUM_WINDOWS)
404 return DMUB_STATUS_INVALID;
405
406 cpu_base = (uint8_t *)params->cpu_fb_addr;
407 gpu_base = params->gpu_fb_addr;
408
409 for (i = 0; i < DMUB_NUM_WINDOWS; ++i) {
410 const struct dmub_region *reg =
411 ¶ms->region_info->regions[i];
412
413 out->fb[i].cpu_addr = cpu_base + reg->base;
414 out->fb[i].gpu_addr = gpu_base + reg->base;
415
> 416 if (i == DMUB_WINDOW_4_MAILBOX && params->cpu_inbox_addr != 0) {
417 out->fb[i].cpu_addr = (uint8_t *)params->cpu_inbox_addr + reg->base;
418 out->fb[i].gpu_addr = params->gpu_inbox_addr + reg->base;
419 }
420
421 out->fb[i].size = reg->top - reg->base;
422 }
423
424 out->num_fb = DMUB_NUM_WINDOWS;
425
426 return DMUB_STATUS_OK;
427 }
428
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-14 2:01 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=202512141013.VJGKROW3-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.