mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ho Jie Feng <hjf3108@gmail.com>, dri-devel@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	cyrozap@gmail.com,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/trigger5: Add MCT Trigger 5 USB display driver
Date: Fri, 11 Sep 2026 20:08:19 +0800	[thread overview]
Message-ID: <202609111951.Hco6MgXH-lkp@intel.com> (raw)
In-Reply-To: <20260910171709.396071-1-hjf3108@gmail.com>

Hi Ho,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 3ab04dcce43cd4fdaed94f08f4e6289be4921ea4]

url:    https://github.com/intel-lab-lkp/linux/commits/Ho-Jie-Feng/drm-trigger5-Add-MCT-Trigger-5-USB-display-driver/20260911-011705
base:   3ab04dcce43cd4fdaed94f08f4e6289be4921ea4
patch link:    https://lore.kernel.org/r/20260910171709.396071-1-hjf3108%40gmail.com
patch subject: [PATCH] drm/trigger5: Add MCT Trigger 5 USB display driver
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20260911/202609111951.Hco6MgXH-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260911/202609111951.Hco6MgXH-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/202609111951.Hco6MgXH-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/trigger5/trigger5_drv.c:435:19: warning: result of comparison of constant 65536 with expression of type 'const u16' (aka 'const unsigned short') is always false [-Wtautological-constant-out-of-range-compare]
     435 |             mode->htotal > U16_MAX + 1)
         |             ~~~~~~~~~~~~ ^ ~~~~~~~~~~~
   drivers/gpu/drm/trigger5/trigger5_drv.c:440:19: warning: result of comparison of constant 65536 with expression of type 'const u16' (aka 'const unsigned short') is always false [-Wtautological-constant-out-of-range-compare]
     440 |             mode->vtotal > U16_MAX + 1)
         |             ~~~~~~~~~~~~ ^ ~~~~~~~~~~~
   2 warnings generated.


vim +435 drivers/gpu/drm/trigger5/trigger5_drv.c

   420	
   421	static enum drm_mode_status
   422	trigger5_crtc_mode_valid(struct drm_crtc *crtc,
   423				 const struct drm_display_mode *mode)
   424	{
   425		struct trigger5_pll pll;
   426		size_t frame_len, payload_len;
   427		u64 err, ppm;
   428	
   429		/*
   430		 * The protocol stores totals, sync pulses, and back porches minus one
   431		 * in 16-bit fields.
   432		 */
   433		if (mode->hsync_end <= mode->hsync_start ||
   434		    mode->htotal <= mode->hsync_end ||
 > 435		    mode->htotal > U16_MAX + 1)
   436			return MODE_H_ILLEGAL;
   437	
   438		if (mode->vsync_end <= mode->vsync_start ||
   439		    mode->vtotal <= mode->vsync_end ||
   440		    mode->vtotal > U16_MAX + 1)
   441			return MODE_V_ILLEGAL;
   442	
   443		payload_len = array3_size(mode->hdisplay, mode->vdisplay, 3);
   444		frame_len = size_add(payload_len, sizeof(struct trigger5_bulk_header));
   445		if (frame_len > SZ_16M)
   446			return MODE_MEM;
   447	
   448		err = trigger5_calculate_pll(&pll, mode->clock);
   449		ppm = div64_u64(err * 1000, mode->clock);
   450		if (ppm > 10000)
   451			return MODE_CLOCK_RANGE;
   452	
   453		return MODE_OK;
   454	}
   455	

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

  reply	other threads:[~2026-09-11 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 17:17 Ho Jie Feng
2026-09-11 12:08 ` kernel test robot [this message]
2026-09-14 13:19 ` [PATCH v2] " Ho Jie Feng

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=202609111951.Hco6MgXH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@gmail.com \
    --cc=cyrozap@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hjf3108@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=simona@ffwll.ch \
    --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

all inboxes | Powered by JetHome®