From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 229/229] drivers/gpu/drm/mediatek/mtk_dp_v2.c:3370:12: warning: variable 'data' set but not used
Date: Wed, 12 Feb 2025 06:31:04 +0800 [thread overview]
Message-ID: <202502120603.J6VilCJI-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 69fc64873274f4b1c5a6c4617cc39b8d59fafbdf
commit: 8fd26707ff2ec98f3a31cafc54c74a1399171b24 [229/229] CHROMIUM: drm/mediatek: Add dp and dp_intf base
config: arm64-randconfig-001-20250212 (https://download.01.org/0day-ci/archive/20250212/202502120603.J6VilCJI-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250212/202502120603.J6VilCJI-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/202502120603.J6VilCJI-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/mediatek/mtk_dp_v2.c: In function 'mtk_dp_video_config_v2':
>> drivers/gpu/drm/mediatek/mtk_dp_v2.c:3370:12: warning: variable 'data' set but not used [-Wunused-but-set-variable]
3370 | u8 data;
| ^~~~
drivers/gpu/drm/mediatek/mtk_dp_v2.c: At top level:
drivers/gpu/drm/mediatek/mtk_dp_v2.c:4043:18: warning: initialized field overwritten [-Woverride-init]
4043 | .reset = drm_atomic_helper_connector_reset,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/mediatek/mtk_dp_v2.c:4043:18: note: (near initialization for 'mtk_dp_con_funcs.reset')
drivers/gpu/drm/mediatek/mtk_dp_v2.c: In function 'mtk_dp_bridge_atomic_get_input_bus_fmts_v2':
drivers/gpu/drm/mediatek/mtk_dp_v2.c:4285:43: warning: variable 'state' set but not used [-Wunused-but-set-variable]
4285 | struct drm_dp_mst_topology_state *state;
| ^~~~~
--
>> drivers/gpu/drm/mediatek/mtk_dpi_v2.c:175: warning: Function parameter or member 'use_version_2' not described in 'mtk_dpi_conf'
vim +/data +3370 drivers/gpu/drm/mediatek/mtk_dp_v2.c
3365
3366 static void mtk_dp_video_config_v2(struct mtk_dp *mtk_dp, const enum dp_encoder_id encoder_id)
3367 {
3368 struct dp_timing_parameter *dp_timing = &mtk_dp->info[encoder_id].dp_output_timing;
3369 struct videomode vm = {0};
> 3370 u8 data;
3371
3372 if (!mtk_dp->dp_ready) {
3373 dev_err(mtk_dp->dev, "%s, DP is not ready\n", __func__);
3374 return;
3375 }
3376
3377 data = mtk_dp->dsc_enable[encoder_id];
3378
3379 mtk_dp_mn_overwrite_v2(mtk_dp, encoder_id, false, 0x0, 0x8000);
3380
3381 vm.hactive = mtk_dp->mode[encoder_id].hdisplay;
3382 vm.hfront_porch = mtk_dp->mode[encoder_id].hsync_start - mtk_dp->mode[encoder_id].hdisplay;
3383 vm.hsync_len = mtk_dp->mode[encoder_id].hsync_end - mtk_dp->mode[encoder_id].hsync_start;
3384 vm.hback_porch = mtk_dp->mode[encoder_id].htotal - mtk_dp->mode[encoder_id].hsync_end;
3385 vm.vactive = mtk_dp->mode[encoder_id].vdisplay;
3386 vm.vfront_porch = mtk_dp->mode[encoder_id].vsync_start - mtk_dp->mode[encoder_id].vdisplay;
3387 vm.vsync_len = mtk_dp->mode[encoder_id].vsync_end - mtk_dp->mode[encoder_id].vsync_start;
3388 vm.vback_porch = mtk_dp->mode[encoder_id].vtotal - mtk_dp->mode[encoder_id].vsync_end;
3389 vm.pixelclock = mtk_dp->mode[encoder_id].clock * 1000;
3390
3391 dp_timing->frame_rate = mtk_dp->mode[encoder_id].clock * 1000 /
3392 mtk_dp->mode[encoder_id].htotal / mtk_dp->mode[encoder_id].vtotal;
3393 dp_timing->htt = mtk_dp->mode[encoder_id].htotal;
3394 dp_timing->hbp = vm.hback_porch;
3395 dp_timing->hsw = vm.hsync_len;
3396 dp_timing->hsp = mtk_dp->mode[encoder_id].flags & DRM_MODE_FLAG_PHSYNC;
3397 dp_timing->hfp = vm.hfront_porch;
3398 dp_timing->hde = vm.hactive;
3399 dp_timing->vtt = mtk_dp->mode[encoder_id].vtotal;
3400 dp_timing->vbp = vm.vback_porch;
3401 dp_timing->vsw = vm.vsync_len;
3402 dp_timing->vsp = mtk_dp->mode[encoder_id].flags & DRM_MODE_FLAG_PVSYNC;
3403 dp_timing->vfp = vm.vfront_porch;
3404 dp_timing->vde = vm.vactive;
3405
3406 dev_dbg(mtk_dp->dev, "frame_rate:%d\n", dp_timing->frame_rate);
3407 dev_dbg(mtk_dp->dev, "htt:%d\n", dp_timing->htt);
3408 dev_dbg(mtk_dp->dev, "hbp:%d\n", dp_timing->hbp);
3409 dev_dbg(mtk_dp->dev, "hsw:%d\n", dp_timing->hsw);
3410 dev_dbg(mtk_dp->dev, "hsp:%d\n", dp_timing->hsp);
3411 dev_dbg(mtk_dp->dev, "hfp:%d\n", dp_timing->hfp);
3412 dev_dbg(mtk_dp->dev, "hde:%d\n", dp_timing->hde);
3413 dev_dbg(mtk_dp->dev, "vtt:%d\n", dp_timing->vtt);
3414 dev_dbg(mtk_dp->dev, "vbp:%d\n", dp_timing->vbp);
3415 dev_dbg(mtk_dp->dev, "vsw:%d\n", dp_timing->vsw);
3416 dev_dbg(mtk_dp->dev, "vsp:%d\n", dp_timing->vsp);
3417 dev_dbg(mtk_dp->dev, "vfp:%d\n", dp_timing->vfp);
3418 dev_dbg(mtk_dp->dev, "vde:%d\n", dp_timing->vde);
3419
3420 mtk_dp_mn_calculate_v2(mtk_dp, encoder_id);
3421
3422 /* interlace not support */
3423 dp_timing->video_ip_mode = DP_VIDEO_PROGRESSIVE;
3424 mtk_dp_msa_set_v2(mtk_dp, encoder_id);
3425
3426 mtk_dp_set_misc_v2(mtk_dp, encoder_id);
3427 if (mtk_dp->info[encoder_id].pattern_gen)
3428 mtk_dp_pg_type_sel_v2(mtk_dp, encoder_id,
3429 DP_PG_VERTICAL_COLOR_BAR,
3430 DP_PG_PURECOLOR_BLUE,
3431 0xfff,
3432 DP_PG_LOCATION_ALL);
3433
3434 if (!mtk_dp->dsc_enable[encoder_id]) {
3435 mtk_dp_color_set_depth_v2(mtk_dp, encoder_id, mtk_dp->info[encoder_id].depth);
3436 mtk_dp_color_set_format_v2(mtk_dp, encoder_id, mtk_dp->info[encoder_id].format);
3437 }
3438 }
3439
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-11 22:31 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=202502120603.J6VilCJI-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.