From: kernel test robot <lkp@intel.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Stephen Boyd" <swboyd@chromium.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Taniya Das" <quic_tdas@quicinc.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Johan Hovold <johan+linaro@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v10 1/5] clk: qcom: regmap: add PHY clock source implementation
Date: Sun, 5 Jun 2022 23:24:23 +0800 [thread overview]
Message-ID: <202206052344.Lkv2vI5x-lkp@intel.com> (raw)
In-Reply-To: <20220603084454.1861142-2-dmitry.baryshkov@linaro.org>
Hi Dmitry,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v5.18]
[also build test ERROR on next-20220603]
[cannot apply to clk/clk-next helgaas-pci/next agross-msm/qcom/for-next]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Dmitry-Baryshkov/PCI-qcom-Rework-pipe_clk-pipe_clk_src-handling/20220605-164136
base: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
config: mips-randconfig-r005-20220605 (https://download.01.org/0day-ci/archive/20220605/202206052344.Lkv2vI5x-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 416a5080d89066029f9889dc23f94de47c2fa895)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
# https://github.com/intel-lab-lkp/linux/commit/4fbc2ca1313223feb409121fa1028557f72a310b
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Dmitry-Baryshkov/PCI-qcom-Rework-pipe_clk-pipe_clk_src-handling/20220605-164136
git checkout 4fbc2ca1313223feb409121fa1028557f72a310b
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/clk/qcom/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/qcom/clk-regmap-phy-mux.c:30:8: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
val = FIELD_GET(PHY_MUX_MASK, val);
^
>> drivers/clk/qcom/clk-regmap-phy-mux.c:44:7: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
FIELD_PREP(PHY_MUX_MASK, PHY_MUX_PHY_SRC));
^
drivers/clk/qcom/clk-regmap-phy-mux.c:54:7: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
FIELD_PREP(PHY_MUX_MASK, PHY_MUX_REF_SRC));
^
3 errors generated.
vim +/FIELD_GET +30 drivers/clk/qcom/clk-regmap-phy-mux.c
22
23 static int phy_mux_is_enabled(struct clk_hw *hw)
24 {
25 struct clk_regmap *clkr = to_clk_regmap(hw);
26 struct clk_regmap_phy_mux *phy_mux = to_clk_regmap_phy_mux(clkr);
27 unsigned int val;
28
29 regmap_read(clkr->regmap, phy_mux->reg, &val);
> 30 val = FIELD_GET(PHY_MUX_MASK, val);
31
32 WARN_ON(val != PHY_MUX_PHY_SRC && val != PHY_MUX_REF_SRC);
33
34 return val == PHY_MUX_PHY_SRC;
35 }
36
37 static int phy_mux_enable(struct clk_hw *hw)
38 {
39 struct clk_regmap *clkr = to_clk_regmap(hw);
40 struct clk_regmap_phy_mux *phy_mux = to_clk_regmap_phy_mux(clkr);
41
42 return regmap_update_bits(clkr->regmap, phy_mux->reg,
43 PHY_MUX_MASK,
> 44 FIELD_PREP(PHY_MUX_MASK, PHY_MUX_PHY_SRC));
45 }
46
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-06-05 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 8:44 [PATCH v10 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling Dmitry Baryshkov
2022-06-03 8:44 ` [PATCH v10 1/5] clk: qcom: regmap: add PHY clock source implementation Dmitry Baryshkov
2022-06-05 15:24 ` kernel test robot [this message]
2022-06-06 16:35 ` Johan Hovold
2022-06-03 8:44 ` [PATCH v10 2/5] clk: qcom: gcc-sm8450: use new clk_regmap_phy_mux_ops for PCIe pipe clocks Dmitry Baryshkov
2022-06-03 8:44 ` [PATCH v10 3/5] clk: qcom: gcc-sc7280: " Dmitry Baryshkov
2022-06-06 16:32 ` Johan Hovold
2022-06-03 8:44 ` [PATCH v10 4/5] PCI: qcom: Remove unnecessary pipe_clk handling Dmitry Baryshkov
2022-06-03 8:44 ` [PATCH v10 5/5] PCI: qcom: Drop manual pipe_clk_src handling Dmitry Baryshkov
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=202206052344.Lkv2vI5x-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=helgaas@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lorenzo.pieralisi@arm.com \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).