From: kernel test robot <lkp@intel.com>
To: Wesley Cheng <quic_wcheng@quicinc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Krzysztof Kozlowski <krzk@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Melody Olvera <melody.olvera@oss.qualcomm.com>
Subject: [krzk-github:n/sm8750-audio-part-3 6/21] drivers/phy/qualcomm/phy-qcom-m31-eusb2.c:210:10: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations
Date: Fri, 23 May 2025 22:12:23 +0800 [thread overview]
Message-ID: <202505232228.17gTDAsa-lkp@intel.com> (raw)
tree: https://github.com/krzk/linux n/sm8750-audio-part-3
head: adac035ce9cf16b4bf5bcad64478178ae722e65e
commit: 053002707bd34cee1887aa5952f4a8e573eb419b [6/21] phy: qcom: Add M31 based eUSB2 PHY driver
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20250523/202505232228.17gTDAsa-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250523/202505232228.17gTDAsa-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/202505232228.17gTDAsa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/phy/qualcomm/phy-qcom-m31-eusb2.c:210:10: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
210 | FIELD_PREP(FSEL, data->fsel));
| ^
1 error generated.
vim +/FIELD_PREP +210 drivers/phy/qualcomm/phy-qcom-m31-eusb2.c
177
178 static int m31eusb2_phy_init(struct phy *uphy)
179 {
180 struct m31eusb2_phy *phy = phy_get_drvdata(uphy);
181 const struct m31_eusb2_priv_data *data = phy->data;
182 int ret;
183
184 ret = regulator_bulk_enable(M31_EUSB_NUM_VREGS, phy->vregs);
185 if (ret) {
186 dev_err(&uphy->dev, "failed to enable regulator, %d\n", ret);
187 return ret;
188 }
189
190 ret = phy_init(phy->repeater);
191 if (ret) {
192 dev_err(&uphy->dev, "repeater init failed. %d\n", ret);
193 goto disable_vreg;
194 }
195
196 ret = clk_prepare_enable(phy->clk);
197 if (ret) {
198 dev_err(&uphy->dev, "failed to enable cfg ahb clock, %d\n", ret);
199 goto disable_repeater;
200 }
201
202 /* Perform phy reset */
203 reset_control_assert(phy->reset);
204 udelay(5);
205 reset_control_deassert(phy->reset);
206
207 m31eusb2_phy_write_sequence(phy, data->setup_seq, data->setup_seq_nregs);
208 m31eusb2_phy_write_readback(phy->base,
209 USB_PHY_HS_PHY_CTRL_COMMON0, FSEL,
> 210 FIELD_PREP(FSEL, data->fsel));
211 m31eusb2_phy_write_sequence(phy, data->override_seq, data->override_seq_nregs);
212 m31eusb2_phy_write_sequence(phy, data->reset_seq, data->reset_seq_nregs);
213
214 return 0;
215
216 disable_repeater:
217 phy_exit(phy->repeater);
218 disable_vreg:
219 regulator_bulk_disable(M31_EUSB_NUM_VREGS, phy->vregs);
220
221 return 0;
222 }
223
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-23 14:13 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=202505232228.17gTDAsa-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=krzk@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=melody.olvera@oss.qualcomm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_wcheng@quicinc.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