From: kernel test robot <lkp@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-gfx-trybot@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ankit.k.nautiyal@intel.com, swati2.sharma@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/i915/dp: Ignore HPD when in DPLL enable/disable cycle
Date: Wed, 22 Apr 2026 10:03:31 +0800 [thread overview]
Message-ID: <202604220938.18Kkm7Pt-lkp@intel.com> (raw)
In-Reply-To: <20260417080118.2352283-1-suraj.kandpal@intel.com>
Hi Suraj,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-i915/for-linux-next]
[also build test ERROR on drm-i915/for-linux-next-fixes drm-tip/drm-tip linus/master v7.0 next-20260421]
[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-i915-dp-Ignore-HPD-when-in-DPLL-enable-disable-cycle/20260422-031647
base: https://gitlab.freedesktop.org/drm/i915/kernel.git for-linux-next
patch link: https://lore.kernel.org/r/20260417080118.2352283-1-suraj.kandpal%40intel.com
patch subject: [PATCH] drm/i915/dp: Ignore HPD when in DPLL enable/disable cycle
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260422/202604220938.18Kkm7Pt-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260422/202604220938.18Kkm7Pt-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/202604220938.18Kkm7Pt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/i915/display/intel_dp.c:6834:62: error: too few arguments provided to function-like macro invocation
6834 | drm_dbg_kms("Ignoring HPD since DPLL is getting disabled\n");
| ^
include/drm/drm_print.h:652:9: note: macro 'drm_dbg_kms' defined here
652 | #define drm_dbg_kms(drm, fmt, ...) \
| ^
>> drivers/gpu/drm/i915/display/intel_dp.c:6834:3: error: use of undeclared identifier 'drm_dbg_kms'
6834 | drm_dbg_kms("Ignoring HPD since DPLL is getting disabled\n");
| ^
2 errors generated.
vim +6834 drivers/gpu/drm/i915/display/intel_dp.c
6825
6826 enum irqreturn
6827 intel_dp_hpd_pulse(struct intel_digital_port *dig_port, bool long_hpd)
6828 {
6829 struct intel_display *display = to_intel_display(dig_port);
6830 struct intel_dp *intel_dp = &dig_port->dp;
6831 u8 dpcd[DP_RECEIVER_CAP_SIZE];
6832
6833 if (atomic_read(&dig_port->link_teardown)) {
> 6834 drm_dbg_kms("Ignoring HPD since DPLL is getting disabled\n");
6835 return IRQ_NONE;
6836 }
6837
6838 if (dig_port->base.type == INTEL_OUTPUT_EDP &&
6839 (long_hpd ||
6840 intel_display_rpm_suspended(display) ||
6841 !intel_pps_have_panel_power_or_vdd(intel_dp))) {
6842 /*
6843 * vdd off can generate a long/short pulse on eDP which
6844 * would require vdd on to handle it, and thus we
6845 * would end up in an endless cycle of
6846 * "vdd off -> long/short hpd -> vdd on -> detect -> vdd off -> ..."
6847 */
6848 drm_dbg_kms(display->drm,
6849 "ignoring %s hpd on eDP [ENCODER:%d:%s]\n",
6850 long_hpd ? "long" : "short",
6851 dig_port->base.base.base.id,
6852 dig_port->base.base.name);
6853 return IRQ_HANDLED;
6854 }
6855
6856 drm_dbg_kms(display->drm, "got hpd irq on [ENCODER:%d:%s] - %s\n",
6857 dig_port->base.base.base.id,
6858 dig_port->base.base.name,
6859 long_hpd ? "long" : "short");
6860
6861 /*
6862 * TBT DP tunnels require the GFX driver to read out the DPRX caps in
6863 * response to long HPD pulses. The DP hotplug handler does that,
6864 * however the hotplug handler may be blocked by another
6865 * connector's/encoder's hotplug handler. Since the TBT CM may not
6866 * complete the DP tunnel BW request for the latter connector/encoder
6867 * waiting for this encoder's DPRX read, perform a dummy read here.
6868 */
6869 if (long_hpd) {
6870 intel_dp_dpcd_set_probe(intel_dp, true);
6871
6872 intel_dp_read_dprx_caps(intel_dp, dpcd);
6873
6874 intel_dp->reset_link_params = true;
6875 intel_dp_invalidate_source_oui(intel_dp);
6876
6877 return IRQ_NONE;
6878 }
6879
6880 if (intel_dp->is_mst) {
6881 if (!intel_dp_check_mst_status(intel_dp))
6882 return IRQ_NONE;
6883 } else if (!intel_dp_short_pulse(intel_dp)) {
6884 return IRQ_NONE;
6885 }
6886
6887 return IRQ_HANDLED;
6888 }
6889
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-04-22 2:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260417080118.2352283-1-suraj.kandpal@intel.com>]
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=202604220938.18Kkm7Pt-lkp@intel.com \
--to=lkp@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx-trybot@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suraj.kandpal@intel.com \
--cc=swati2.sharma@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