linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peichen Huang <peichen.huang@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alex Deucher <alexander.deucher@amd.com>,
	Cruise Hung <cruise.hung@amd.com>
Subject: [linux-next:master 12891/13109] drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_dpia_bw.c:548:24: warning: arithmetic between different enumeration types ('const enum dc_link_rate' and 'const enum dc_lane_count')
Date: Thu, 11 Jan 2024 04:59:27 +0800	[thread overview]
Message-ID: <202401110427.FNT67xeQ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   8cb47d7cd090a690c1785385b2f3d407d4a53ad0
commit: 5f3bce13266e6fe2f7a46f94d8bc94d5274e276b [12891/13109] drm/amd/display: Request usb4 bw for mst streams
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20240111/202401110427.FNT67xeQ-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240111/202401110427.FNT67xeQ-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/202401110427.FNT67xeQ-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_dpia_bw.c:548:24: warning: arithmetic between different enumeration types ('const enum dc_link_rate' and 'const enum dc_lane_count') [-Wenum-enum-conversion]
     548 |                         link_cap->link_rate * link_cap->lane_count * LINK_RATE_REF_FREQ_IN_KHZ * 8;
         |                         ~~~~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~~~~~~~~
   1 warning generated.


vim +548 drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_dpia_bw.c

   531	
   532	int link_dp_dpia_get_dp_overhead_in_dp_tunneling(struct dc_link *link)
   533	{
   534		int dp_overhead = 0, link_mst_overhead = 0;
   535	
   536		if (!get_bw_alloc_proceed_flag((link)))
   537			return dp_overhead;
   538	
   539		/* if its mst link, add MTPH overhead */
   540		if ((link->type == dc_connection_mst_branch) &&
   541			!link->dpcd_caps.channel_coding_cap.bits.DP_128b_132b_SUPPORTED) {
   542			/* For 8b/10b encoding: MTP is 64 time slots long, slot 0 is used for MTPH
   543			 * MST overhead is 1/64 of link bandwidth (excluding any overhead)
   544			 */
   545			const struct dc_link_settings *link_cap =
   546				dc_link_get_link_cap(link);
   547			uint32_t link_bw_in_kbps =
 > 548				link_cap->link_rate * link_cap->lane_count * LINK_RATE_REF_FREQ_IN_KHZ * 8;

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


                 reply	other threads:[~2024-01-10 21:00 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=202401110427.FNT67xeQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=cruise.hung@amd.com \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peichen.huang@amd.com \
    /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