From: kbuild test robot <lkp@intel.com>
Cc: linux-fbdev@vger.kernel.org, kbuild-all@lists.01.org,
Thomas Zimmermann <tzimmermann@suse.de>,
b.zolnierkie@samsung.com, airlied@linux.ie,
gregkh@linuxfoundation.org, michel@daenzer.net, corbet@lwn.net,
malat@debian.org, dri-devel@lists.freedesktop.org,
sean@poorly.run
Subject: Re: [PATCH v2 08/15] drm/fbconv: Add plane-state check and update
Date: Tue, 15 Oct 2019 17:28:50 +0000 [thread overview]
Message-ID: <201910160147.NR8eNv8Z%lkp@intel.com> (raw)
In-Reply-To: <20191014140416.28517-9-tzimmermann@suse.de>
Hi Thomas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc3 next-20191014]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Thomas-Zimmermann/DRM-fbconv-helpers-for-converting-fbdev-drivers/20191015-152231
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_fbconv_helper.c:981:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] <asn:2> *dst @@ got n:2> *dst @@
>> drivers/gpu/drm/drm_fbconv_helper.c:981:39: sparse: expected void [noderef] <asn:2> *dst
>> drivers/gpu/drm/drm_fbconv_helper.c:981:39: sparse: got void *dst
drivers/gpu/drm/drm_fbconv_helper.c:985:51: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] <asn:2> *dst @@ got n:2> *dst @@
drivers/gpu/drm/drm_fbconv_helper.c:985:51: sparse: expected void [noderef] <asn:2> *dst
drivers/gpu/drm/drm_fbconv_helper.c:985:51: sparse: got void *dst
drivers/gpu/drm/drm_fbconv_helper.c:990:51: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] <asn:2> *dst @@ got n:2> *dst @@
drivers/gpu/drm/drm_fbconv_helper.c:990:51: sparse: expected void [noderef] <asn:2> *dst
drivers/gpu/drm/drm_fbconv_helper.c:990:51: sparse: got void *dst
>> drivers/gpu/drm/drm_fbconv_helper.c:1291:21: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *screen_base @@ got char [noderef] <asvoid *screen_base @@
>> drivers/gpu/drm/drm_fbconv_helper.c:1291:21: sparse: expected void *screen_base
>> drivers/gpu/drm/drm_fbconv_helper.c:1291:21: sparse: got char [noderef] <asn:2> *screen_base
>> drivers/gpu/drm/drm_fbconv_helper.c:1294:29: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *screen_base @@ got void [noderef] <asvoid *screen_base @@
drivers/gpu/drm/drm_fbconv_helper.c:1294:29: sparse: expected void *screen_base
>> drivers/gpu/drm/drm_fbconv_helper.c:1294:29: sparse: got void [noderef] <asn:2> *
>> drivers/gpu/drm/drm_fbconv_helper.c:1318:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] <asn:2> *addr @@ got n:2> *addr @@
>> drivers/gpu/drm/drm_fbconv_helper.c:1318:25: sparse: expected void volatile [noderef] <asn:2> *addr
>> drivers/gpu/drm/drm_fbconv_helper.c:1318:25: sparse: got void *screen_base
drivers/gpu/drm/drm_fbconv_helper.c:1346:38: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] <asn:2> *addr @@ got n:2> *addr @@
drivers/gpu/drm/drm_fbconv_helper.c:1346:38: sparse: expected void volatile [noderef] <asn:2> *addr
drivers/gpu/drm/drm_fbconv_helper.c:1346:38: sparse: got void *screen_base
vim +981 drivers/gpu/drm/drm_fbconv_helper.c
956
957 /**
958 * drm_fbconv_blit_rect - copy an area of pixel data from a framebuffer
959 * to the hardware buffer
960 * @dst: the on-screen hardware buffer
961 * @vaddr: the source buffer in kernel address space
962 * @fb: the framebuffer of the source buffer
963 * @rect: the area to copy
964 * Returns:
965 * 0 on success, or
966 * a negative error code otherwise.
967 *
968 * This function copies the pixel data from a DRM framebuffer to a hardware
969 * buffer; doing necessary format conversion in the process. Not all
970 * combinations of source and destination formats are currently supported.
971 */
972 int drm_fbconv_blit_rect(void *dst, void *vaddr, struct drm_framebuffer *fb,
973 struct drm_rect *rect)
974 {
975 struct drm_device *dev = fb->dev;
976
977 if (!vaddr)
978 return 0; /* no framebuffer set for plane; no error */
979
980 if (dev->mode_config.preferred_depth = (fb->format->cpp[0] * 8))
> 981 drm_fb_memcpy_dstclip(dst, vaddr, fb, rect);
982
983 else if (fb->format->cpp[0] = 4 &&
984 dev->mode_config.preferred_depth = 16)
> 985 drm_fb_xrgb8888_to_rgb565_dstclip(dst, fb->pitches[0],
986 vaddr, fb, rect, false);
987
988 else if (fb->format->cpp[0] = 4 &&
989 dev->mode_config.preferred_depth = 24)
> 990 drm_fb_xrgb8888_to_rgb888_dstclip(dst, fb->pitches[0],
991 vaddr, fb, rect);
992
993 else {
994 /* TODO: add the missing conversion */
995 DRM_ERROR("fbconv: mismatching pixel formats\n");
996 return -EINVAL;
997 }
998
999 return 0;
1000 }
1001 EXPORT_SYMBOL(drm_fbconv_blit_rect);
1002
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-10-15 17:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 14:04 [PATCH v2 00/15] DRM fbconv helpers for converting fbdev drivers Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 01/15] fbdev: Export fb_check_foreignness() Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 02/15] fbdev: Export FBPIXMAPSIZE Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 03/15] drm/simple-kms-helper: Add mode_fixup() to simple display pipe Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 04/15] drm: Add fbconv helper module Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 05/15] drm/fbconv: Add DRM <-> fbdev pixel-format conversion Thomas Zimmermann
2019-10-14 20:30 ` Sam Ravnborg
2019-10-15 5:48 ` Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 06/15] drm/fbconv: Add mode conversion DRM <-> fbdev Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 07/15] drm/fbconv: Add modesetting infrastructure Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 08/15] drm/fbconv: Add plane-state check and update Thomas Zimmermann
2019-10-15 8:30 ` kbuild test robot
2019-10-15 17:28 ` kbuild test robot [this message]
2019-10-14 14:04 ` [PATCH v2 09/15] drm/fbconv: Mode-setting pipeline enable / disable Thomas Zimmermann
2022-05-28 20:17 ` Geert Uytterhoeven
2022-05-30 7:47 ` Thomas Zimmermann
2022-05-30 8:34 ` Geert Uytterhoeven
2022-07-01 20:01 ` Geert Uytterhoeven
2019-10-14 14:04 ` [PATCH v2 10/15] drm/fbconv: Reimplement several fbdev interfaces Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 11/15] drm/fbconv: Add helpers for init and cleanup of fb_info structures Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 12/15] drm/fbconv: Add helper documentation Thomas Zimmermann
2019-10-15 8:40 ` kbuild test robot
2019-10-14 14:04 ` [PATCH v2 13/15] staging: Add mgakms driver Thomas Zimmermann
2019-10-14 14:04 ` [PATCH v2 15/15] staging/mgakms: Update matroxfb driver code for DRM Thomas Zimmermann
2019-10-17 16:19 ` kbuild test robot
2019-10-14 20:36 ` [PATCH v2 00/15] DRM fbconv helpers for converting fbdev drivers Sam Ravnborg
2019-10-15 6:11 ` Thomas Zimmermann
[not found] ` <20191014140416.28517-15-tzimmermann@suse.de>
2019-10-15 11:48 ` [PATCH v2 14/15] staging/mgakms: Import matroxfb driver source code Ville Syrjälä
2019-10-15 12:46 ` Thomas Zimmermann
2019-10-15 14:33 ` [PATCH v2 00/15] DRM fbconv helpers for converting fbdev drivers Daniel Vetter
2019-10-15 17:28 ` Thomas Zimmermann
2019-10-15 17:48 ` Daniel Vetter
2019-10-15 18:05 ` Greg KH
2019-10-15 18:13 ` Ville Syrjälä
2019-10-15 18:28 ` Ville Syrjälä
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=201910160147.NR8eNv8Z%lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=malat@debian.org \
--cc=michel@daenzer.net \
--cc=sean@poorly.run \
--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 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).