From: kernel test robot <lkp@intel.com>
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, Sebastian Reichel <sre@kernel.org>,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: [sre-misc:thinkpad-t14s-x1e 27/106] drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:440:34: sparse: sparse: symbol 'phy_qcom_mipi_csi2_ops_3ph_1_0' was not declared. Should it be static?
Date: Wed, 15 Apr 2026 22:46:25 +0800 [thread overview]
Message-ID: <202604152215.ouAFAN60-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-misc.git thinkpad-t14s-x1e
head: f1da547e2fdb6a7e05855a3bd78da0681cd32d77
commit: 729b50da9ca6685cb749bd328730a7e9655e9572 [27/106] phy: qcom-mipi-csi2: Add a CSI2 MIPI D-PHY driver
config: alpha-randconfig-r122-20260415 (https://download.01.org/0day-ci/archive/20260415/202604152215.ouAFAN60-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604152215.ouAFAN60-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/202604152215.ouAFAN60-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:440:34: sparse: sparse: symbol 'phy_qcom_mipi_csi2_ops_3ph_1_0' was not declared. Should it be static?
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:451:36: sparse: sparse: symbol 'dphy_4nm_x1e_csiphy' was not declared. Should it be static?
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:458:36: sparse: sparse: symbol 'dphy_4nm_x1e_csiphy_timer' was not declared. Should it be static?
vim +/phy_qcom_mipi_csi2_ops_3ph_1_0 +440 drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c
439
> 440 const struct mipi_csi2phy_hw_ops phy_qcom_mipi_csi2_ops_3ph_1_0 = {
441 .hw_version_read = phy_qcom_mipi_csi2_hw_version_read,
442 .reset = phy_qcom_mipi_csi2_reset,
443 .lanes_enable = phy_qcom_mipi_csi2_lanes_enable,
444 .lanes_disable = phy_qcom_mipi_csi2_lanes_disable,
445 .isr = phy_qcom_mipi_csi2_isr,
446 .init = phy_qcom_mipi_csi2_init,
447 };
448
449 const struct mipi_csi2phy_clk_freq zero = { 0 };
450
> 451 const struct mipi_csi2phy_clk_freq dphy_4nm_x1e_csiphy = {
452 .freq = {
453 300000000, 400000000, 480000000
454 },
455 .num_freq = 3,
456 };
457
> 458 const struct mipi_csi2phy_clk_freq dphy_4nm_x1e_csiphy_timer = {
459 .freq = {
460 266666667, 400000000
461 },
462 .num_freq = 2,
463 };
464
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-15 14:47 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=202604152215.ouAFAN60-lkp@intel.com \
--to=lkp@intel.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sre@kernel.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 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.