All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chu Guangqing <chuguangqing@inspur.com>,
	tzimmermann@suse.de, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, airlied@gmail.com, simona@ffwll.cc,
	dmitry.baryshkov@oss.qualcomm.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Chu Guangqing <chuguangqing@inspur.com>
Subject: Re: [PATCH v5 1/1] [DRIVER] gpu: drm: add support for Yhgc ZX1000 soc chipset
Date: Sun, 28 Sep 2025 04:40:26 +0800	[thread overview]
Message-ID: <202509280424.vdB0od7m-lkp@intel.com> (raw)
In-Reply-To: <20250925091715.12739-2-chuguangqing@inspur.com>

Hi Chu,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on linus/master v6.17-rc7]
[cannot apply to next-20250926]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Chu-Guangqing/gpu-drm-add-support-for-Yhgc-ZX1000-soc-chipset/20250925-172156
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:    https://lore.kernel.org/r/20250925091715.12739-2-chuguangqing%40inspur.com
patch subject: [PATCH v5 1/1] [DRIVER] gpu: drm: add support for Yhgc ZX1000 soc chipset
config: loongarch-randconfig-r123-20250927 (https://download.01.org/0day-ci/archive/20250928/202509280424.vdB0od7m-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250928/202509280424.vdB0od7m-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/202509280424.vdB0od7m-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/yhgch/yhgch_drm_de.c:65:41: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void [noderef] __iomem *vaddr_iomem @@     got void *addr_base @@
   drivers/gpu/drm/yhgch/yhgch_drm_de.c:65:41: sparse:     expected void [noderef] __iomem *vaddr_iomem
   drivers/gpu/drm/yhgch/yhgch_drm_de.c:65:41: sparse:     got void *addr_base
>> drivers/gpu/drm/yhgch/yhgch_drm_de.c:92:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void *addr_base @@     got void [noderef] __iomem *vram_base @@
   drivers/gpu/drm/yhgch/yhgch_drm_de.c:92:41: sparse:     expected void *addr_base
   drivers/gpu/drm/yhgch/yhgch_drm_de.c:92:41: sparse:     got void [noderef] __iomem *vram_base
>> drivers/gpu/drm/yhgch/yhgch_drm_de.c:123:10: sparse: sparse: Initializer entry defined twice
   drivers/gpu/drm/yhgch/yhgch_drm_de.c:126:9: sparse:   also defined here

vim +65 drivers/gpu/drm/yhgch/yhgch_drm_de.c

    58	
    59	static void yhgch_handle_damage(void *addr_base, struct iosys_map *src,
    60					struct drm_framebuffer *fb,
    61					struct drm_rect *clip)
    62	{
    63		struct iosys_map dst;
    64	
  > 65		iosys_map_set_vaddr_iomem(&dst, addr_base);
    66		iosys_map_incr(&dst, drm_fb_clip_offset(fb->pitches[0], fb->format, clip));
    67		drm_fb_memcpy(&dst, fb->pitches, src, fb, clip);
    68	}
    69	
    70	static void yhgch_plane_atomic_update(struct drm_plane *plane,
    71					      struct drm_atomic_state *state)
    72	{
    73		struct drm_plane_state *plane_state = drm_atomic_get_new_plane_state(state, plane);
    74		struct drm_framebuffer *fb = plane_state->fb;
    75		struct drm_plane_state *old_plane_state = drm_atomic_get_old_plane_state(state, plane);
    76		struct drm_shadow_plane_state *shadow_plane_state = to_drm_shadow_plane_state(plane_state);
    77		struct yhgch_drm_private *priv = to_yhgch_drm_private(plane->dev);
    78		struct drm_atomic_helper_damage_iter iter;
    79		struct drm_rect damage;
    80		u32 reg;
    81		s64 gpu_addr = 0;
    82		u32 line_l;
    83	
    84		if (!plane_state->crtc || !plane_state->fb)
    85			return;
    86	
    87		if (!plane_state->visible)
    88			return;
    89	
    90		drm_atomic_helper_damage_iter_init(&iter, old_plane_state, plane_state);
    91		drm_atomic_for_each_plane_damage(&iter, &damage) {
  > 92			yhgch_handle_damage(priv->vram_base, shadow_plane_state->data, fb, &damage);
    93		}
    94	
    95		fb->pitches[0] = (fb->pitches[0] + 15) & ~15;
    96	
    97		writel(gpu_addr, priv->mmio + YHGCH_CRT_FB_ADDRESS);
    98	
    99		reg = fb->width * fb->format->cpp[0];
   100	
   101		line_l = fb->pitches[0];
   102		writel(FIELD_PREP(YHGCH_CRT_FB_WIDTH_WIDTH_MASK, reg) |
   103		       FIELD_PREP(YHGCH_CRT_FB_WIDTH_OFFS_MASK, line_l),
   104		       priv->mmio + YHGCH_CRT_FB_WIDTH);
   105	
   106		/* SET PIXEL FORMAT */
   107		reg = readl(priv->mmio + YHGCH_CRT_DISP_CTL);
   108		reg &= ~YHGCH_CRT_DISP_CTL_FORMAT_MASK;
   109		reg |= FIELD_PREP(YHGCH_CRT_DISP_CTL_FORMAT_MASK,
   110				   fb->format->cpp[0] * 8 / 16);
   111		writel(reg, priv->mmio + YHGCH_CRT_DISP_CTL);
   112	}
   113	
   114	static const u32 channel_formats1[] = {
   115		DRM_FORMAT_RGB565, DRM_FORMAT_RGB888,
   116		DRM_FORMAT_XRGB8888,
   117	};
   118	
   119	static struct drm_plane_funcs yhgch_plane_funcs = {
   120		.update_plane = drm_atomic_helper_update_plane,
   121		.disable_plane = drm_atomic_helper_disable_plane,
   122		.destroy = drm_plane_cleanup,
 > 123		.reset = drm_atomic_helper_plane_reset,
   124		.atomic_duplicate_state = drm_atomic_helper_plane_duplicate_state,
   125		.atomic_destroy_state = drm_atomic_helper_plane_destroy_state,
   126		DRM_GEM_SHADOW_PLANE_FUNCS,
   127	};
   128	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-09-27 20:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  5:35 [PATCH 0/1] add Yhgch soc chipset support chuguangqing
2025-08-08  5:35 ` [PATCH 1/1] [DRIVER] gpu: drm: add support for Yhgc ZX1000 soc chipset chuguangqing
2025-08-27  9:17   ` Thomas Zimmermann
2025-09-03  5:45     ` [PATCH v2 0/1] " chuguangqing
2025-09-03  5:45       ` [PATCH v2 1/1] " chuguangqing
2025-09-04 11:19         ` Thomas Zimmermann
2025-09-10  2:23           ` [PATCH v3 0/1] " Chu Guangqing
2025-09-10  2:23             ` [PATCH v3 1/1] [DRIVER] " Chu Guangqing
2025-09-11  0:44               ` Dmitry Baryshkov
2025-09-11  7:25               ` Thomas Zimmermann
2025-09-24  6:49                 ` [PATCH v4 0/1] " Chu Guangqing
2025-09-24  6:49                   ` [PATCH v4 1/1] " Chu Guangqing
2025-09-25  4:15                     ` Dmitry Baryshkov
2025-09-25  9:17                       ` [PATCH v5 0/1] " Chu Guangqing
2025-09-25  9:17                         ` [PATCH v5 1/1] " Chu Guangqing
2025-09-25 22:20                           ` Dmitry Baryshkov
2025-09-28  6:05                             ` [PATCH v5 1/1] [DRIVER] gpu: drm: add support for Yhgc ZX1000 soc Chu Guangqing
2025-09-27 20:40                           ` kernel test robot [this message]
2025-09-25 22:15                         ` [PATCH v5 0/1] [DRIVER] gpu: drm: add support for Yhgc ZX1000 soc chipset Dmitry Baryshkov
2025-09-25  4:04                   ` [PATCH v4 " Dmitry Baryshkov
2025-08-08  7:15 ` [PATCH v1] [PATCH 0/1] add Yhgch soc chipset support - Supplementary Cc simona chuguangqing
2025-08-08  7:15   ` [PATCH 0/1] add Yhgch soc chipset support chuguangqing

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=202509280424.vdB0od7m-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@gmail.com \
    --cc=chuguangqing@inspur.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=simona@ffwll.cc \
    --cc=tzimmermann@suse.de \
    /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.