From: kernel test robot <lkp@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, uma.shankar@intel.com,
arun.r.murthy@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout
Date: Sat, 21 Dec 2024 01:54:14 +0800 [thread overview]
Message-ID: <202412210137.vRBJlttZ-lkp@intel.com> (raw)
In-Reply-To: <20241213060317.2674290-3-suraj.kandpal@intel.com>
Hi Suraj,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.13-rc3 next-20241220]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-dp-Add-the-DPCD-register-required-for-Extended-wake-timeout/20241213-140525
base: linus/master
patch link: https://lore.kernel.org/r/20241213060317.2674290-3-suraj.kandpal%40intel.com
patch subject: [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout
config: i386-randconfig-013-20241220 (https://download.01.org/0day-ci/archive/20241221/202412210137.vRBJlttZ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241221/202412210137.vRBJlttZ-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/202412210137.vRBJlttZ-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/display/intel_dp_link_training.c: In function 'intel_dp_lttpr_wake_timeout_setup':
>> drivers/gpu/drm/i915/display/intel_dp_link_training.c:148:69: error: initialized field overwritten [-Werror=override-init]
148 | [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_20_MS] = 20,
| ^~
drivers/gpu/drm/i915/display/intel_dp_link_training.c:148:69: note: (near initialization for 'timeout_mapping[1]')
cc1: all warnings being treated as errors
vim +148 drivers/gpu/drm/i915/display/intel_dp_link_training.c
136
137 void intel_dp_lttpr_wake_timeout_setup(struct intel_dp *intel_dp)
138 {
139 struct intel_display *display = to_intel_display(intel_dp);
140 u8 val = 1;
141 int ret;
142
143 if (intel_dp_lttpr_transparent_mode_enabled(intel_dp)) {
144 static const u8 timeout_mapping[] = {
145 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_1_MS] = 1,
146 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_20_MS] = 20,
147 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_40_MS] = 40,
> 148 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_20_MS] = 20,
149 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_80_MS] = 80,
150 [DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_100_MS] = 100,
151 };
152
153 ret = drm_dp_dpcd_readb(&intel_dp->aux,
154 DP_EXTENDED_DPRX_SLEEP_WAKE_TIMEOUT_REQUEST, &val);
155 if (ret != 1) {
156 drm_dbg_kms(display->drm,
157 "Failed to read Extended sleep wake timeout request\n");
158 return;
159 }
160
161 val = (val < sizeof(timeout_mapping) && timeout_mapping[val]) ?
162 timeout_mapping[val] : 1;
163
164 drm_dp_dpcd_writeb(&intel_dp->aux, DP_EXTENDED_DPRX_SLEEP_WAKE_TIMEOUT_GRANT,
165 DP_DPRX_SLEEP_WAKE_TIMEOUT_PERIOD_GRANTED);
166 } else {
167 ret = drm_dp_dpcd_readb(&intel_dp->aux,
168 DP_PHY_REPEATER_EXTENDED_WAIT_TIMEOUT, &val);
169 if (ret != 1) {
170 drm_dbg_kms(display->drm,
171 "Failed to read Extended sleep wake timeout request\n");
172 return;
173 }
174
175 val = (val & DP_EXTENDED_WAKE_TIMEOUT_REQUEST_MASK) ?
176 (val & DP_EXTENDED_WAKE_TIMEOUT_REQUEST_MASK) * 10 : 1;
177
178 drm_dp_dpcd_writeb(&intel_dp->aux, DP_PHY_REPEATER_EXTENDED_WAIT_TIMEOUT,
179 DP_EXTENDED_WAKE_TIMEOUT_GRANT);
180 }
181 }
182
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-20 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 6:03 [PATCH 0/2] Extended Wake Timeout Suraj Kandpal
2024-12-13 6:03 ` [PATCH 1/2] drm/dp: Add the DPCD register required for Extended wake timeout Suraj Kandpal
2024-12-13 6:03 ` [PATCH 2/2] drm/i915/lttpr: Enable Extended Wake Timeout Suraj Kandpal
2024-12-20 17:54 ` kernel test robot [this message]
2024-12-21 0:49 ` kernel test robot
2024-12-21 1:42 ` kernel test robot
2024-12-13 6:29 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-13 6:29 ` ✓ CI.checkpatch: " Patchwork
2024-12-13 6:30 ` ✓ CI.KUnit: " Patchwork
2024-12-13 6:48 ` ✓ CI.Build: " Patchwork
2024-12-13 6:51 ` ✓ CI.Hooks: " Patchwork
2024-12-13 6:52 ` ✗ CI.checksparse: warning " Patchwork
2024-12-13 7:43 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-13 12:41 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-01-17 5:48 [PATCH 0/2] " Suraj Kandpal
2025-01-17 5:48 ` [PATCH 2/2] drm/i915/lttpr: Enable " Suraj Kandpal
2025-01-17 6:19 ` Dmitry Baryshkov
2025-01-21 4:44 ` Kandpal, Suraj
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=202412210137.vRBJlttZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@intel.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