From: kernel test robot <lkp@intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [krzk-github:n/sm8450 35/58] drivers/soundwire/qcom.c:332:13: warning: unused variable 'rd_fifo_outstanding_cmds'
Date: Wed, 26 Oct 2022 07:32:47 +0800 [thread overview]
Message-ID: <202210260744.8FahRB1R-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]
tree: https://github.com/krzk/linux n/sm8450
head: 57bf42faa17be40e013df8d598030f47956a7144
commit: 5ba47c0f678c51dc9359c8a7265d3b1cc81bbc48 [35/58] soundwire: qcom: wait for fifo to be empty before
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/krzk/linux/commit/5ba47c0f678c51dc9359c8a7265d3b1cc81bbc48
git remote add krzk-github https://github.com/krzk/linux
git fetch --no-tags krzk-github n/sm8450
git checkout 5ba47c0f678c51dc9359c8a7265d3b1cc81bbc48
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/soundwire/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/soundwire/qcom.c: In function 'swrm_wait_for_wr_fifo_done':
>> drivers/soundwire/qcom.c:332:13: warning: unused variable 'rd_fifo_outstanding_cmds' [-Wunused-variable]
332 | u32 rd_fifo_outstanding_cmds;
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/rd_fifo_outstanding_cmds +332 drivers/soundwire/qcom.c
328
329 static bool swrm_wait_for_wr_fifo_done(struct qcom_swrm_ctrl *swrm)
330 {
331 u32 fifo_outstanding_cmds, value;
> 332 u32 rd_fifo_outstanding_cmds;
333 int fifo_retry_count = SWR_OVERFLOW_RETRY_COUNT*2;
334
335 /* Check for fifo overflow during write */
336 swrm->reg_read(swrm, SWRM_CMD_FIFO_STATUS, &value);
337 fifo_outstanding_cmds = FIELD_GET(SWRM_WR_CMD_FIFO_CNT_MASK, value);
338
339 if (fifo_outstanding_cmds) {
340 while (fifo_retry_count) {
341 usleep_range(500, 510);
342 swrm->reg_read(swrm, SWRM_CMD_FIFO_STATUS, &value);
343 fifo_outstanding_cmds = FIELD_GET(SWRM_WR_CMD_FIFO_CNT_MASK, value);
344 fifo_retry_count--;
345 if (fifo_outstanding_cmds == 0)
346 return true;
347 }
348 } else {
349 return true;
350 }
351
352
353 return false;
354 }
355
--
0-DAY CI Kernel Test Service
https://01.org/lkp
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 70258 bytes --]
reply other threads:[~2022-10-25 23:33 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=202210260744.8FahRB1R-lkp@intel.com \
--to=lkp@intel.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=srinivas.kandagatla@linaro.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