From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jun Yi <yijun@loongson.cn>
Subject: drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 11 Nov 2023 15:36:55 +0800 [thread overview]
Message-ID: <202311111512.IuUi0ceL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3ca112b71f35dd5d99fc4571a56b5fc6f0c15814
commit: a275a82dcd4024c75337db15d59ed039c31e21da LoongArch: Use alternative to optimize libraries
date: 11 months ago
config: loongarch-randconfig-r133-20231107 (https://download.01.org/0day-ci/archive/20231111/202311111512.IuUi0ceL-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231111/202311111512.IuUi0ceL-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/202311111512.IuUi0ceL-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/video/fbdev/atmel_lcdfb.c:354:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected char [noderef] __iomem *screen_base @@ got void * @@
drivers/video/fbdev/atmel_lcdfb.c:354:27: sparse: expected char [noderef] __iomem *screen_base
drivers/video/fbdev/atmel_lcdfb.c:354:27: sparse: got void *
>> drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *__s @@ got char [noderef] __iomem *screen_base @@
drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: expected void *__s
drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: got char [noderef] __iomem *screen_base
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void *cpu_addr @@ got char [noderef] __iomem *screen_base @@
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: expected void *cpu_addr
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: got char [noderef] __iomem *screen_base
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void *cpu_addr @@ got char [noderef] __iomem *screen_base @@
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: expected void *cpu_addr
drivers/video/fbdev/atmel_lcdfb.c:333:59: sparse: got char [noderef] __iomem *screen_base
vim +362 drivers/video/fbdev/atmel_lcdfb.c
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 336
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 337 /**
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 338 * atmel_lcdfb_alloc_video_memory - Allocate framebuffer memory
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 339 * @sinfo: the frame buffer to allocate memory for
1d01e83557105e drivers/video/atmel_lcdfb.c Krzysztof Helt 2009-07-08 340 *
1d01e83557105e drivers/video/atmel_lcdfb.c Krzysztof Helt 2009-07-08 341 * This function is called only from the atmel_lcdfb_probe()
1d01e83557105e drivers/video/atmel_lcdfb.c Krzysztof Helt 2009-07-08 342 * so no locking by fb_info->mm_lock around smem_len setting is needed.
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 343 */
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 344 static int atmel_lcdfb_alloc_video_memory(struct atmel_lcdfb_info *sinfo)
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 345 {
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 346 struct fb_info *info = sinfo->info;
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 347 struct fb_var_screeninfo *var = &info->var;
ea757acad5a518 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 348 unsigned int smem_len;
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 349
ea757acad5a518 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 350 smem_len = (var->xres_virtual * var->yres_virtual
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 351 * ((var->bits_per_pixel + 7) / 8));
ea757acad5a518 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 352 info->fix.smem_len = max(smem_len, sinfo->smem_len);
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 353
f6e45661f9be54 drivers/video/fbdev/atmel_lcdfb.c Luis R. Rodriguez 2016-01-22 354 info->screen_base = dma_alloc_wc(info->device, info->fix.smem_len,
f6e45661f9be54 drivers/video/fbdev/atmel_lcdfb.c Luis R. Rodriguez 2016-01-22 355 (dma_addr_t *)&info->fix.smem_start,
f6e45661f9be54 drivers/video/fbdev/atmel_lcdfb.c Luis R. Rodriguez 2016-01-22 356 GFP_KERNEL);
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 357
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 358 if (!info->screen_base) {
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 359 return -ENOMEM;
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 360 }
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 361
01d3a5e7fab773 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-04-28 @362 memset(info->screen_base, 0, info->fix.smem_len);
01d3a5e7fab773 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-04-28 363
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 364 return 0;
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 365 }
14340586148e7c drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 366
:::::: The code at line 362 was first introduced by commit
:::::: 01d3a5e7fab7732cfc5d5d4533e9378ea435295a atmel_lcdfb: don't initialize a pre-allocated framebuffer
:::::: TO: Haavard Skinnemoen <hskinnemoen@atmel.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-11 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 7:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-17 2:26 drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2023-11-15 10:18 kernel test robot
2023-11-08 16:49 kernel test robot
2023-11-08 1:14 kernel test robot
2020-08-24 13:34 kernel test robot
2020-08-09 4:24 kernel test robot
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=202311111512.IuUi0ceL-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yijun@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