From: kernel test robot <lkp@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Subject: Re: [PATCH v2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value
Date: Wed, 11 Dec 2024 12:50:49 +0800 [thread overview]
Message-ID: <202412111422.EkKTeLIL-lkp@intel.com> (raw)
In-Reply-To: <20241209153418.49580-1-dnyaneshwar.bhadane@intel.com>
Hi Dnyaneshwar,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20241209]
[also build test ERROR on linus/master v6.13-rc2]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.13-rc2 v6.13-rc1 v6.12]
[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/Dnyaneshwar-Bhadane/drm-i915-cx0_phy-Update-HDMI-TMDS-C20-algorithm-value/20241209-233928
base: next-20241209
patch link: https://lore.kernel.org/r/20241209153418.49580-1-dnyaneshwar.bhadane%40intel.com
patch subject: [PATCH v2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20241211/202412111422.EkKTeLIL-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241211/202412111422.EkKTeLIL-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/202412111422.EkKTeLIL-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/display/intel_cx0_phy.c:13:
In file included from drivers/gpu/drm/i915/display/intel_de.h:9:
In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:16:
In file included from drivers/gpu/drm/xe/compat-i915-headers/intel_runtime_pm.h:10:
In file included from drivers/gpu/drm/xe/xe_device_types.h:9:
In file included from include/linux/pci.h:38:
In file included from include/linux/interrupt.h:22:
In file included from arch/riscv/include/asm/sections.h:9:
In file included from include/linux/mm.h:2287:
include/linux/vmstat.h:504:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
505 | item];
| ~~~~
include/linux/vmstat.h:511:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
512 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
include/linux/vmstat.h:524:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
525 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/i915/display/intel_cx0_phy.c:2201:7: error: call to undeclared function 'IS_METEORLAKE_U'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
2201 | if (IS_METEORLAKE_U(to_i915(display->drm)) ||
| ^
>> drivers/gpu/drm/i915/display/intel_cx0_phy.c:2202:7: error: call to undeclared function 'IS_ARROWLAKE_U'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
2202 | IS_ARROWLAKE_U(to_i915(display->drm)) ||
| ^
4 warnings and 2 errors generated.
vim +/IS_METEORLAKE_U +2201 drivers/gpu/drm/i915/display/intel_cx0_phy.c
2177
2178 static u16 intel_c20_hdmi_tmds_tx_cgf_1(struct intel_crtc_state *crtc_state)
2179 {
2180 struct intel_display *display = to_intel_display(crtc_state);
2181 struct pci_dev *pdev = NULL;
2182 u16 tx_misc;
2183 u16 tx_dcc_cal_dac_ctrl_range = 8;
2184 u16 tx_term_ctrl;
2185 u16 host_bridge_pci_dev_id;
2186
2187 if (IS_BATTLEMAGE(to_i915(display->drm))) {
2188 tx_misc = 0;
2189 tx_term_ctrl = 2;
2190 } else if (DISPLAY_VER(display) >= 20) {
2191 tx_misc = 5;
2192 tx_term_ctrl = 4;
2193 } else if (IS_METEORLAKE(to_i915(display->drm))) {
2194 /*
2195 * Some SoCs have the same drm PCI IDs, so differentiate based
2196 * on the host bridge device ID to use the correct txx_mics value.
2197 */
2198 while ((pdev = pci_get_class(PCI_CLASS_BRIDGE_HOST << 8, pdev)))
2199 host_bridge_pci_dev_id = pdev->device;
2200
> 2201 if (IS_METEORLAKE_U(to_i915(display->drm)) ||
> 2202 IS_ARROWLAKE_U(to_i915(display->drm)) ||
2203 (pdev && IS_ARROWLAKE_S_BY_HOST_BRIDGE_ID(host_bridge_pci_dev_id))) {
2204 tx_misc = 3;
2205 } else {
2206 tx_misc = 7;
2207 }
2208
2209 tx_term_ctrl = 2;
2210 }
2211 return (C20_PHY_TX_MISC(tx_misc) |
2212 C20_PHY_TX_DCC_CAL_RANGE(tx_dcc_cal_dac_ctrl_range) |
2213 C20_PHY_TX_DCC_BYPASS | C20_PHY_TX_TERM_CTL(tx_term_ctrl));
2214 }
2215
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-12-11 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 15:34 [PATCH v2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value Dnyaneshwar Bhadane
2024-12-09 18:14 ` ✗ Fi.CI.BUILD: failure for drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value (rev2) Patchwork
2024-12-09 22:46 ` [PATCH v2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value kernel test robot
2024-12-10 7:07 ` Bhadane, Dnyaneshwar
2024-12-10 3:55 ` kernel test robot
2024-12-10 9:17 ` Jani Nikula
2024-12-11 4:50 ` kernel test robot [this message]
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=202412111422.EkKTeLIL-lkp@intel.com \
--to=lkp@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=llvm@lists.linux.dev \
--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.