From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Rob Clark <robdclark@chromium.org>,
Abhinav Kumar <abhinavk@codeaurora.org>
Subject: drivers/gpu/drm/msm/dp/dp_display.c:1045:21: warning: variable 'drm' set but not used
Date: Wed, 7 Jul 2021 15:16:21 +0800 [thread overview]
Message-ID: <202107071518.H0gciTmB-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4253 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 77d34a4683b053108ecd466cc7c4193b45805528
commit: eb9d6c7ebe44df4bf077e71de809bb7b216da38c drm/msm: pass dump state as a function argument
date: 2 weeks ago
config: arm64-buildonly-randconfig-r005-20210707 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb9d6c7ebe44df4bf077e71de809bb7b216da38c
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout eb9d6c7ebe44df4bf077e71de809bb7b216da38c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/msm/dp/dp_display.c: In function 'dp_display_usbpd_attention_cb':
drivers/gpu/drm/msm/dp/dp_display.c:506:19: warning: variable 'hpd' set but not used [-Wunused-but-set-variable]
506 | struct dp_usbpd *hpd;
| ^~~
drivers/gpu/drm/msm/dp/dp_display.c: In function 'msm_dp_snapshot':
>> drivers/gpu/drm/msm/dp/dp_display.c:1045:21: warning: variable 'drm' set but not used [-Wunused-but-set-variable]
1045 | struct drm_device *drm;
| ^~~
vim +/drm +1045 drivers/gpu/drm/msm/dp/dp_display.c
c943b4948b5848 Chandan Uddaraju 2020-08-27 1041
eb9d6c7ebe44df Dmitry Baryshkov 2021-04-27 1042 void msm_dp_snapshot(struct msm_disp_state *disp_state, struct msm_dp *dp)
0f6090f37f8018 Abhinav Kumar 2021-04-16 1043 {
0f6090f37f8018 Abhinav Kumar 2021-04-16 1044 struct dp_display_private *dp_display;
0f6090f37f8018 Abhinav Kumar 2021-04-16 @1045 struct drm_device *drm;
0f6090f37f8018 Abhinav Kumar 2021-04-16 1046
0f6090f37f8018 Abhinav Kumar 2021-04-16 1047 dp_display = container_of(dp, struct dp_display_private, dp_display);
0f6090f37f8018 Abhinav Kumar 2021-04-16 1048 drm = dp->drm_dev;
0f6090f37f8018 Abhinav Kumar 2021-04-16 1049
0f6090f37f8018 Abhinav Kumar 2021-04-16 1050 /*
0f6090f37f8018 Abhinav Kumar 2021-04-16 1051 * if we are reading registers we need the link clocks to be on
0f6090f37f8018 Abhinav Kumar 2021-04-16 1052 * however till DP cable is connected this will not happen as we
0f6090f37f8018 Abhinav Kumar 2021-04-16 1053 * do not know the resolution to power up with. Hence check the
0f6090f37f8018 Abhinav Kumar 2021-04-16 1054 * power_on status before dumping DP registers to avoid crash due
0f6090f37f8018 Abhinav Kumar 2021-04-16 1055 * to unclocked access
0f6090f37f8018 Abhinav Kumar 2021-04-16 1056 */
0f6090f37f8018 Abhinav Kumar 2021-04-16 1057 mutex_lock(&dp_display->event_mutex);
0f6090f37f8018 Abhinav Kumar 2021-04-16 1058
0f6090f37f8018 Abhinav Kumar 2021-04-16 1059 if (!dp->power_on) {
0f6090f37f8018 Abhinav Kumar 2021-04-16 1060 mutex_unlock(&dp_display->event_mutex);
0f6090f37f8018 Abhinav Kumar 2021-04-16 1061 return;
0f6090f37f8018 Abhinav Kumar 2021-04-16 1062 }
0f6090f37f8018 Abhinav Kumar 2021-04-16 1063
0f6090f37f8018 Abhinav Kumar 2021-04-16 1064 dp_catalog_snapshot(dp_display->catalog, disp_state);
0f6090f37f8018 Abhinav Kumar 2021-04-16 1065
0f6090f37f8018 Abhinav Kumar 2021-04-16 1066 mutex_unlock(&dp_display->event_mutex);
0f6090f37f8018 Abhinav Kumar 2021-04-16 1067 }
0f6090f37f8018 Abhinav Kumar 2021-04-16 1068
:::::: The code at line 1045 was first introduced by commit
:::::: 0f6090f37f801871b292c296ed34eb2b089a0477 drm/msm/dp: add API to take DP register snapshot
:::::: TO: Abhinav Kumar <abhinavk@codeaurora.org>
:::::: CC: Rob Clark <robdclark@chromium.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42139 bytes --]
reply other threads:[~2021-07-07 7:16 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=202107071518.H0gciTmB-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhinavk@codeaurora.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
/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®