From: kernel test robot <lkp@intel.com>
To: Zsolt Kajtar <soci@c64.rulez.org>
Cc: oe-kbuild-all@lists.linux.dev, Helge Deller <deller@gmx.de>
Subject: [deller-fbdev:for-next 13/15] drivers/video/fbdev/core/fb_imageblit.h:332:14: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Sat, 8 Feb 2025 15:37:59 +0800 [thread overview]
Message-ID: <202502081503.sOVHPKm3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git for-next
head: 720fcad9d12e92368192689a90e2b932a1e44406
commit: d244899de08c324fdcf4dbed95ecb64ea292ff61 [13/15] fbdev: core: Use generic imageblit for as cfb_imageblit
config: microblaze-randconfig-r111-20250208 (https://download.01.org/0day-ci/archive/20250208/202502081503.sOVHPKm3-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250208/202502081503.sOVHPKm3-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/202502081503.sOVHPKm3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/video/fbdev/core/cfbimgblt.c: note: in included file:
>> drivers/video/fbdev/core/fb_imageblit.h:332:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned char [noderef] [usertype] __iomem *dst1 @@ got void * @@
drivers/video/fbdev/core/fb_imageblit.h:332:14: sparse: expected unsigned char [noderef] [usertype] __iomem *dst1
drivers/video/fbdev/core/fb_imageblit.h:332:14: sparse: got void *
vim +332 drivers/video/fbdev/core/fb_imageblit.h
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 310
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 311 void FB_IMAGEBLIT (struct fb_info *p, const struct fb_image *image)
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 312 {
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 313 u32 fgcolor, bgcolor, start_index, bitstart, pitch_index = 0;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 314 u32 bpl = sizeof(u32), bpp = p->var.bits_per_pixel;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 315 u32 width = image->width;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 316 u32 dx = image->dx, dy = image->dy;
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 317 u8 FB_MEM *dst1;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 318
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 319 if (p->state != FBINFO_STATE_RUNNING)
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 320 return;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 321
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 322 if ((p->flags & FBINFO_VIRTFB) != FB_SPACE)
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 323 fb_warn_once(p, "Framebuffer is not in " FB_SPACE_NAME
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 324 " address space.");
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 325
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 326 bitstart = (dy * p->fix.line_length * 8) + (dx * bpp);
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 327 start_index = bitstart & (32 - 1);
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 328 pitch_index = (p->fix.line_length & (bpl - 1)) * 8;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 329
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 330 bitstart /= 8;
d933e6d9f4eb8e Zsolt Kajtar 2025-02-07 331 bitstart &= ~(bpl - 1);
24d36dc5bee2bf Zsolt Kajtar 2025-02-07 @332 dst1 = (void __force *)FB_SCREEN_BASE(p) + bitstart;
:::::: The code at line 332 was first introduced by commit
:::::: 24d36dc5bee2bf0768f51e207925d044d7e66b6f fbdev: core: Make fb_imageblit generic
:::::: TO: Zsolt Kajtar <soci@c64.rulez.org>
:::::: CC: Helge Deller <deller@gmx.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-08 7:38 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=202502081503.sOVHPKm3-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=soci@c64.rulez.org \
/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.