From: kernel test robot <lkp@intel.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 17 Dec 2023 10:26:10 +0800 [thread overview]
Message-ID: <202312171050.VRjziNZK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3b8a9b2e6809d281890dd0a1102dc14d2cd11caf
commit: 59c1ad914ef2d3470f74c626ece9521dbc9645a3 video: fbdev: atmel_lcdfb: add COMPILE_TEST support
date: 4 years, 6 months ago
config: arc-randconfig-r111-20231107 (https://download.01.org/0day-ci/archive/20231217/202312171050.VRjziNZK-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231217/202312171050.VRjziNZK-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/202312171050.VRjziNZK-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 *ptr @@ got char [noderef] __iomem *screen_base @@
drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: expected void *ptr
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
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 336
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 337 /**
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 338 * atmel_lcdfb_alloc_video_memory - Allocate framebuffer memory
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 339 * @sinfo: the frame buffer to allocate memory for
1d01e83557105e7 drivers/video/atmel_lcdfb.c Krzysztof Helt 2009-07-08 340 *
1d01e83557105e7 drivers/video/atmel_lcdfb.c Krzysztof Helt 2009-07-08 341 * This function is called only from the atmel_lcdfb_probe()
1d01e83557105e7 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.
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 343 */
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 344 static int atmel_lcdfb_alloc_video_memory(struct atmel_lcdfb_info *sinfo)
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 345 {
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 346 struct fb_info *info = sinfo->info;
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 347 struct fb_var_screeninfo *var = &info->var;
ea757acad5a5183 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 348 unsigned int smem_len;
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 349
ea757acad5a5183 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 350 smem_len = (var->xres_virtual * var->yres_virtual
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 351 * ((var->bits_per_pixel + 7) / 8));
ea757acad5a5183 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-08-12 352 info->fix.smem_len = max(smem_len, sinfo->smem_len);
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 353
f6e45661f9be546 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,
f6e45661f9be546 drivers/video/fbdev/atmel_lcdfb.c Luis R. Rodriguez 2016-01-22 355 (dma_addr_t *)&info->fix.smem_start,
f6e45661f9be546 drivers/video/fbdev/atmel_lcdfb.c Luis R. Rodriguez 2016-01-22 356 GFP_KERNEL);
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 357
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 358 if (!info->screen_base) {
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 359 return -ENOMEM;
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 360 }
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 361
01d3a5e7fab7732 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-04-28 @362 memset(info->screen_base, 0, info->fix.smem_len);
01d3a5e7fab7732 drivers/video/atmel_lcdfb.c Haavard Skinnemoen 2008-04-28 363
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 364 return 0;
14340586148e7c8 drivers/video/atmel_lcdfb.c Nicolas Ferre 2007-05-10 365 }
14340586148e7c8 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-12-17 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 2:26 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 10:18 drivers/video/fbdev/atmel_lcdfb.c:362:20: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2023-11-14 20:56 kernel test robot
2023-11-15 7:55 ` Liu, Yujie
2023-11-11 7:36 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-24 13:34 ` kernel test robot
2020-08-09 4:24 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=202312171050.VRjziNZK-lkp@intel.com \
--to=lkp@intel.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--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.