From: kernel test robot <lkp@intel.com>
To: Udipto Goswami <quic_ugoswami@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
Udipto Goswami <quic_ugoswami@quicinc.com>
Subject: Re: [PATCH] phy: qcom-snps-femto-v2: Add load and voltage setting for LDO's used
Date: Fri, 3 May 2024 13:37:49 +0800 [thread overview]
Message-ID: <202405031311.9f1PrPou-lkp@intel.com> (raw)
In-Reply-To: <20240502123312.31083-1-quic_ugoswami@quicinc.com>
Hi Udipto,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.9-rc6 next-20240502]
[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/Udipto-Goswami/phy-qcom-snps-femto-v2-Add-load-and-voltage-setting-for-LDO-s-used/20240502-203521
base: linus/master
patch link: https://lore.kernel.org/r/20240502123312.31083-1-quic_ugoswami%40quicinc.com
patch subject: [PATCH] phy: qcom-snps-femto-v2: Add load and voltage setting for LDO's used
config: x86_64-buildonly-randconfig-003-20240503 (https://download.01.org/0day-ci/archive/20240503/202405031311.9f1PrPou-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240503/202405031311.9f1PrPou-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/202405031311.9f1PrPou-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/phy/qualcomm/phy-qcom-snps-femto-v2.c:168: warning: Function parameter or struct member 'vreg_list' not described in 'qcom_snps_hsphy'
vim +168 drivers/phy/qualcomm/phy-qcom-snps-femto-v2.c
df2217ff17a820 Krishna Kurapati 2022-09-06 136
51e8114f80d076 Wesley Cheng 2020-05-04 137 /**
51e8114f80d076 Wesley Cheng 2020-05-04 138 * struct qcom_snps_hsphy - snps hs phy attributes
51e8114f80d076 Wesley Cheng 2020-05-04 139 *
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 140 * @dev: device structure
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 141 *
51e8114f80d076 Wesley Cheng 2020-05-04 142 * @phy: generic phy
51e8114f80d076 Wesley Cheng 2020-05-04 143 * @base: iomapped memory space for snps hs phy
51e8114f80d076 Wesley Cheng 2020-05-04 144 *
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 145 * @num_clks: number of clocks
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 146 * @clks: array of clocks
51e8114f80d076 Wesley Cheng 2020-05-04 147 * @phy_reset: phy reset control
51e8114f80d076 Wesley Cheng 2020-05-04 148 * @vregs: regulator supplies bulk data
51e8114f80d076 Wesley Cheng 2020-05-04 149 * @phy_initialized: if PHY has been initialized correctly
dcbec046507615 Wesley Cheng 2020-06-25 150 * @mode: contains the current mode the PHY is in
2a881183dc5ab2 Krzysztof Kozlowski 2023-05-07 151 * @update_seq_cfg: tuning parameters for phy init
51e8114f80d076 Wesley Cheng 2020-05-04 152 */
51e8114f80d076 Wesley Cheng 2020-05-04 153 struct qcom_snps_hsphy {
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 154 struct device *dev;
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 155
51e8114f80d076 Wesley Cheng 2020-05-04 156 struct phy *phy;
51e8114f80d076 Wesley Cheng 2020-05-04 157 void __iomem *base;
51e8114f80d076 Wesley Cheng 2020-05-04 158
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 159 int num_clks;
8a0eb8f9b9a002 Adrien Thierry 2023-06-29 160 struct clk_bulk_data *clks;
51e8114f80d076 Wesley Cheng 2020-05-04 161 struct reset_control *phy_reset;
51e8114f80d076 Wesley Cheng 2020-05-04 162 struct regulator_bulk_data vregs[SNPS_HS_NUM_VREGS];
4dac559b5584a2 Udipto Goswami 2024-05-02 163 const struct qcom_snps_hsphy_regulator_data *vreg_list;
51e8114f80d076 Wesley Cheng 2020-05-04 164
51e8114f80d076 Wesley Cheng 2020-05-04 165 bool phy_initialized;
dcbec046507615 Wesley Cheng 2020-06-25 166 enum phy_mode mode;
df2217ff17a820 Krishna Kurapati 2022-09-06 167 struct phy_override_seq update_seq_cfg[NUM_HSPHY_TUNING_PARAMS];
51e8114f80d076 Wesley Cheng 2020-05-04 @168 };
51e8114f80d076 Wesley Cheng 2020-05-04 169
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-03 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:33 [PATCH] phy: qcom-snps-femto-v2: Add load and voltage setting for LDO's used Udipto Goswami
2024-05-02 13:12 ` Dmitry Baryshkov
2024-05-03 5:23 ` Udipto Goswami
2024-05-03 18:29 ` Dmitry Baryshkov
2024-05-07 11:43 ` Konrad Dybcio
2024-05-07 11:55 ` Dmitry Baryshkov
2024-05-07 13:41 ` Konrad Dybcio
2024-05-03 5:37 ` 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=202405031311.9f1PrPou-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_ugoswami@quicinc.com \
--cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox