From: kernel test robot <lkp@intel.com>
To: Sui Jingfeng <suijingfeng@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 505/4327] drivers/gpu/drm/loongson/lsdc_benchmark.c:27:35: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Wed, 26 Jul 2023 00:39:56 +0800 [thread overview]
Message-ID: <202307260047.7VI2QNNG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1e25dd7772483f477f79986d956028e9f47f990a
commit: f39db26c54281da6a785259498ca74b5e470476f [505/4327] drm: Add kms driver for loongson display controller
config: sparc64-randconfig-r091-20230725 (https://download.01.org/0day-ci/archive/20230726/202307260047.7VI2QNNG-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230726/202307260047.7VI2QNNG-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/202307260047.7VI2QNNG-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/loongson/lsdc_benchmark.c:27:35: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *dst @@ got void *kptr @@
drivers/gpu/drm/loongson/lsdc_benchmark.c:27:35: sparse: expected void volatile [noderef] __iomem *dst
drivers/gpu/drm/loongson/lsdc_benchmark.c:27:35: sparse: got void *kptr
>> drivers/gpu/drm/loongson/lsdc_benchmark.c:42:51: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const volatile [noderef] __iomem *src @@ got void *kptr @@
drivers/gpu/drm/loongson/lsdc_benchmark.c:42:51: sparse: expected void const volatile [noderef] __iomem *src
drivers/gpu/drm/loongson/lsdc_benchmark.c:42:51: sparse: got void *kptr
vim +27 drivers/gpu/drm/loongson/lsdc_benchmark.c
12
13 typedef void (*lsdc_copy_proc_t)(struct lsdc_bo *src_bo,
14 struct lsdc_bo *dst_bo,
15 unsigned int size,
16 int n);
17
18 static void lsdc_copy_gtt_to_vram_cpu(struct lsdc_bo *src_bo,
19 struct lsdc_bo *dst_bo,
20 unsigned int size,
21 int n)
22 {
23 lsdc_bo_kmap(src_bo);
24 lsdc_bo_kmap(dst_bo);
25
26 while (n--)
> 27 memcpy_toio(dst_bo->kptr, src_bo->kptr, size);
28
29 lsdc_bo_kunmap(src_bo);
30 lsdc_bo_kunmap(dst_bo);
31 }
32
33 static void lsdc_copy_vram_to_gtt_cpu(struct lsdc_bo *src_bo,
34 struct lsdc_bo *dst_bo,
35 unsigned int size,
36 int n)
37 {
38 lsdc_bo_kmap(src_bo);
39 lsdc_bo_kmap(dst_bo);
40
41 while (n--)
> 42 memcpy_fromio(dst_bo->kptr, src_bo->kptr, size);
43
44 lsdc_bo_kunmap(src_bo);
45 lsdc_bo_kunmap(dst_bo);
46 }
47
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-25 16:41 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=202307260047.7VI2QNNG-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suijingfeng@loongson.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 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).