From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Jiakun Shuai <shuaijiakun1288@phytium.com.cn>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 2516/2516] drivers/gpu/drm/ast/ast_mm.c:91:39: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Tue, 3 Dec 2024 20:49:19 +0800 [thread overview]
Message-ID: <202412032029.eVzOP3UR-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: f030ffc8e0c6dac3503bebddbf49cc339003fcdb
commit: 968ee436e4d0ce09994f74015dc163ef280ccc1e [2516/2516] drm/ast: Fixed display error for ps23xx when using ast bmc card
config: x86_64-randconfig-121-20241203 (https://download.01.org/0day-ci/archive/20241203/202412032029.eVzOP3UR-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241203/202412032029.eVzOP3UR-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/202412032029.eVzOP3UR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/ast/ast_mm.c:91:39: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/gpu/drm/ast/ast_mm.c:91:39: sparse: expected void *addr
drivers/gpu/drm/ast/ast_mm.c:91:39: sparse: got void [noderef] __iomem *
vim +91 drivers/gpu/drm/ast/ast_mm.c
76
77 static int ast_driver_io_mem_reserve(struct ttm_bo_device *bdev,
78 struct ttm_resource *mem)
79 {
80 struct drm_vram_mm *vmm = drm_vram_mm_of_bdev(bdev);
81 size_t bus_size = (size_t)mem->num_pages << PAGE_SHIFT;
82
83 switch (mem->mem_type) {
84 case TTM_PL_SYSTEM: /* nothing to do */
85 break;
86 case TTM_PL_VRAM:
87 mem->bus.offset = (mem->start << PAGE_SHIFT) + vmm->vram_base;
88 mem->bus.is_iomem = true;
89
90 mem->placement = TTM_PL_FLAG_UNCACHED;
> 91 mem->bus.addr = ioremap(mem->bus.offset, bus_size);
92
93 if (!mem->bus.addr)
94 return -ENOMEM;
95
96 break;
97 default:
98 return -EINVAL;
99 }
100
101 return 0;
102 }
103
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-03 12:49 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=202412032029.eVzOP3UR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shuaijiakun1288@phytium.com.cn \
/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.