From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jsarha:topic/cros-sof-v4.14-rebase 2902/9999] drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c:291:21: warning: variable 'hw_mdp' set but not used
Date: Sat, 20 Jan 2024 02:20:39 +0800 [thread overview]
Message-ID: <202401200216.JpNgqjDF-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux topic/cros-sof-v4.14-rebase
head: 18a233f3f676a98dde00947535d99ab1a54da340
commit: 0cd2491bb127c67f683085510db07dd59f66d32f [2902/9999] FROMGIT: drm/msm/dpu: remove cdm block support from resource manager
config: arm-randconfig-001-20240118 (https://download.01.org/0day-ci/archive/20240120/202401200216.JpNgqjDF-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240120/202401200216.JpNgqjDF-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/202401200216.JpNgqjDF-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c: In function '_dpu_rm_hw_blk_create':
>> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c:291:21: warning: variable 'hw_mdp' set but not used [-Wunused-but-set-variable]
struct dpu_hw_mdp *hw_mdp;
^~~~~~
vim +/hw_mdp +291 drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c
4c774770eee65f Jeykumar Sankaran 2018-06-27 281
4c774770eee65f Jeykumar Sankaran 2018-06-27 282 static int _dpu_rm_hw_blk_create(
4c774770eee65f Jeykumar Sankaran 2018-06-27 283 struct dpu_rm *rm,
4c774770eee65f Jeykumar Sankaran 2018-06-27 284 struct dpu_mdss_cfg *cat,
4c774770eee65f Jeykumar Sankaran 2018-06-27 285 void __iomem *mmio,
4c774770eee65f Jeykumar Sankaran 2018-06-27 286 enum dpu_hw_blk_type type,
4c774770eee65f Jeykumar Sankaran 2018-06-27 287 uint32_t id,
4c774770eee65f Jeykumar Sankaran 2018-06-27 288 void *hw_catalog_info)
4c774770eee65f Jeykumar Sankaran 2018-06-27 289 {
4c774770eee65f Jeykumar Sankaran 2018-06-27 290 struct dpu_rm_hw_blk *blk;
4c774770eee65f Jeykumar Sankaran 2018-06-27 @291 struct dpu_hw_mdp *hw_mdp;
4c774770eee65f Jeykumar Sankaran 2018-06-27 292 void *hw;
4c774770eee65f Jeykumar Sankaran 2018-06-27 293
4c774770eee65f Jeykumar Sankaran 2018-06-27 294 hw_mdp = rm->hw_mdp;
4c774770eee65f Jeykumar Sankaran 2018-06-27 295
4c774770eee65f Jeykumar Sankaran 2018-06-27 296 switch (type) {
4c774770eee65f Jeykumar Sankaran 2018-06-27 297 case DPU_HW_BLK_LM:
4c774770eee65f Jeykumar Sankaran 2018-06-27 298 hw = dpu_hw_lm_init(id, mmio, cat);
4c774770eee65f Jeykumar Sankaran 2018-06-27 299 break;
4c774770eee65f Jeykumar Sankaran 2018-06-27 300 case DPU_HW_BLK_CTL:
4c774770eee65f Jeykumar Sankaran 2018-06-27 301 hw = dpu_hw_ctl_init(id, mmio, cat);
4c774770eee65f Jeykumar Sankaran 2018-06-27 302 break;
4c774770eee65f Jeykumar Sankaran 2018-06-27 303 case DPU_HW_BLK_PINGPONG:
4c774770eee65f Jeykumar Sankaran 2018-06-27 304 hw = dpu_hw_pingpong_init(id, mmio, cat);
4c774770eee65f Jeykumar Sankaran 2018-06-27 305 break;
4c774770eee65f Jeykumar Sankaran 2018-06-27 306 case DPU_HW_BLK_INTF:
4c774770eee65f Jeykumar Sankaran 2018-06-27 307 hw = dpu_hw_intf_init(id, mmio, cat);
4c774770eee65f Jeykumar Sankaran 2018-06-27 308 break;
4c774770eee65f Jeykumar Sankaran 2018-06-27 309 case DPU_HW_BLK_SSPP:
4c774770eee65f Jeykumar Sankaran 2018-06-27 310 /* SSPPs are not managed by the resource manager */
4c774770eee65f Jeykumar Sankaran 2018-06-27 311 case DPU_HW_BLK_TOP:
4c774770eee65f Jeykumar Sankaran 2018-06-27 312 /* Top is a singleton, not managed in hw_blks list */
4c774770eee65f Jeykumar Sankaran 2018-06-27 313 case DPU_HW_BLK_MAX:
4c774770eee65f Jeykumar Sankaran 2018-06-27 314 default:
4c774770eee65f Jeykumar Sankaran 2018-06-27 315 DPU_ERROR("unsupported block type %d\n", type);
4c774770eee65f Jeykumar Sankaran 2018-06-27 316 return -EINVAL;
4c774770eee65f Jeykumar Sankaran 2018-06-27 317 }
4c774770eee65f Jeykumar Sankaran 2018-06-27 318
4c774770eee65f Jeykumar Sankaran 2018-06-27 319 if (IS_ERR_OR_NULL(hw)) {
4c774770eee65f Jeykumar Sankaran 2018-06-27 320 DPU_ERROR("failed hw object creation: type %d, err %ld\n",
4c774770eee65f Jeykumar Sankaran 2018-06-27 321 type, PTR_ERR(hw));
4c774770eee65f Jeykumar Sankaran 2018-06-27 322 return -EFAULT;
4c774770eee65f Jeykumar Sankaran 2018-06-27 323 }
4c774770eee65f Jeykumar Sankaran 2018-06-27 324
4c774770eee65f Jeykumar Sankaran 2018-06-27 325 blk = kzalloc(sizeof(*blk), GFP_KERNEL);
4c774770eee65f Jeykumar Sankaran 2018-06-27 326 if (!blk) {
4c774770eee65f Jeykumar Sankaran 2018-06-27 327 _dpu_rm_hw_destroy(type, hw);
4c774770eee65f Jeykumar Sankaran 2018-06-27 328 return -ENOMEM;
4c774770eee65f Jeykumar Sankaran 2018-06-27 329 }
4c774770eee65f Jeykumar Sankaran 2018-06-27 330
4c774770eee65f Jeykumar Sankaran 2018-06-27 331 blk->type = type;
4c774770eee65f Jeykumar Sankaran 2018-06-27 332 blk->id = id;
4c774770eee65f Jeykumar Sankaran 2018-06-27 333 blk->hw = hw;
4c774770eee65f Jeykumar Sankaran 2018-06-27 334 list_add_tail(&blk->list, &rm->hw_blks[type]);
4c774770eee65f Jeykumar Sankaran 2018-06-27 335
4c774770eee65f Jeykumar Sankaran 2018-06-27 336 return 0;
4c774770eee65f Jeykumar Sankaran 2018-06-27 337 }
4c774770eee65f Jeykumar Sankaran 2018-06-27 338
:::::: The code at line 291 was first introduced by commit
:::::: 4c774770eee65f0c397d53d6ad82fd2b2db228ab UPSTREAM: drm/msm: Add SDM845 DPU support
:::::: TO: Jeykumar Sankaran <jsanka@codeaurora.org>
:::::: CC: chrome-bot <chrome-bot@chromium.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-19 18:21 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=202401200216.JpNgqjDF-lkp@intel.com \
--to=lkp@intel.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.