All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Abel Vesa <abel.vesa@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: [sre-misc:thinkpad-t14s-x1e 57/95] drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:486:3: error: initializer element is not a compile-time constant
Date: Sat, 30 Aug 2025 04:23:34 +0800	[thread overview]
Message-ID: <202508300416.siXP5kl7-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-misc.git thinkpad-t14s-x1e
head:   9dd4135e4233415f1082b5addd91211121dad8af
commit: 298f529d0c46850b0d6d48f29d085aab13509929 [57/95] phy: qcom-mipi-csi2: Add a CSI2 MIPI D-PHY driver
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20250830/202508300416.siXP5kl7-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250830/202508300416.siXP5kl7-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/202508300416.siXP5kl7-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:486:3: error: initializer element is not a compile-time constant
                   zero,
                   ^~~~
   1 error generated.


vim +486 drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c

   464	
   465	const struct mipi_csi2phy_soc_cfg mipi_csi2_dphy_4nm_x1e = {
   466		.ops = &phy_qcom_mipi_csi2_ops_3ph_1_0,
   467		.reg_info = {
   468			.init_seq = lane_regs_x1e80100,
   469			.lane_array_size = ARRAY_SIZE(lane_regs_x1e80100),
   470			.offset = 0x1000,
   471			.generation = GEN2,
   472		},
   473		.supply_names = (const char *[]){
   474			"vdda-0p8",
   475			"vdda-1p2"
   476		},
   477		.num_supplies = 2,
   478		.clk_names = (const char *[]) {
   479			"camnoc_axi",
   480			"cpas_ahb",
   481			"csiphy",
   482			"csiphy_timer"
   483		},
   484		.num_clk = 4,
   485		.clk_freq = {
 > 486			zero,

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-08-29 20:24 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=202508300416.siXP5kl7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=abel.vesa@linaro.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=neil.armstrong@linaro.org \
    --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.