From: kernel test robot <lkp@intel.com>
To: jasperwang@tencent.com, kaixuxia@tencent.com,
frankjpliu@tencent.com, kasong@tencent.com,
sagazchen@tencent.com, kernelxing@tencent.com,
aurelianliu@tencent.com, jason.zeng@intel.com,
wu.zheng@intel.com, yingbao.jia@intel.com, pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [opencloudos:linux-5.4/lts/5.4.119-20.0009.phytium 16/41] drivers/usb/phytium/platform.c:176:12: warning: 'phytium_driver_resume' defined but not used
Date: Tue, 5 Mar 2024 08:12:05 +0800 [thread overview]
Message-ID: <202403050828.6BLMCvLE-lkp@intel.com> (raw)
tree: https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git linux-5.4/lts/5.4.119-20.0009.phytium
head: 974a90e098c75ef0e62d4bbbde4535368a61f98b
commit: cde7dabbe0c87fc60cd1ee483a20cf5c060fff0f [16/41] usb: phytium: Add support for Phytium USB controller This patch adds the Phytium USBHS DRD controller support.
config: arm64-randconfig-r051-20240305 (https://download.01.org/0day-ci/archive/20240305/202403050828.6BLMCvLE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240305/202403050828.6BLMCvLE-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/202403050828.6BLMCvLE-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/phytium/platform.c:176:12: warning: 'phytium_driver_resume' defined but not used [-Wunused-function]
176 | static int phytium_driver_resume(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~~~
>> drivers/usb/phytium/platform.c:158:12: warning: 'phytium_driver_suspend' defined but not used [-Wunused-function]
158 | static int phytium_driver_suspend(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/phytium_driver_resume +176 drivers/usb/phytium/platform.c
156
157 #ifdef CONFIG_PM
> 158 static int phytium_driver_suspend(struct device *dev)
159 {
160 struct phytium_cusb *config;
161 int ret = 0;
162
163 config = dev_get_drvdata(dev);
164
165 if (config->dr_mode == USB_DR_MODE_HOST ||
166 config->dr_mode == USB_DR_MODE_OTG)
167 ret = phytium_host_suspend(config);
168
169 if (config->dr_mode == USB_DR_MODE_PERIPHERAL ||
170 config->dr_mode == USB_DR_MODE_OTG)
171 ret = phytium_gadget_suspend(config);
172
173 return ret;
174 }
175
> 176 static int phytium_driver_resume(struct device *dev)
177 {
178 struct phytium_cusb *config;
179 int ret = 0;
180
181 config = dev_get_drvdata(dev);
182 if (config->dr_mode == USB_DR_MODE_HOST ||
183 config->dr_mode == USB_DR_MODE_OTG)
184 ret = phytium_host_resume(config);
185
186 if (config->dr_mode == USB_DR_MODE_PERIPHERAL ||
187 config->dr_mode == USB_DR_MODE_OTG)
188 ret = phytium_gadget_resume(config);
189
190 return ret;
191 }
192
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-05 0:12 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=202403050828.6BLMCvLE-lkp@intel.com \
--to=lkp@intel.com \
--cc=aurelianliu@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=jason.zeng@intel.com \
--cc=jasperwang@tencent.com \
--cc=kaixuxia@tencent.com \
--cc=kasong@tencent.com \
--cc=kernelxing@tencent.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pei.p.jia@intel.com \
--cc=sagazchen@tencent.com \
--cc=wu.zheng@intel.com \
--cc=yingbao.jia@intel.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 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.