From: kernel test robot <lkp@intel.com>
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>,
marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, amitkumar.karwar@nxp.com,
neeraj.sanjaykale@nxp.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, sherry.sun@nxp.com,
rohit.fule@nxp.com
Subject: Re: [PATCH v2] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test
Date: Wed, 27 Dec 2023 19:41:20 +0800 [thread overview]
Message-ID: <202312271920.D4X4fO6I-lkp@intel.com> (raw)
In-Reply-To: <20231226113110.3923962-1-neeraj.sanjaykale@nxp.com>
Hi Neeraj,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth/master]
[also build test ERROR on bluetooth-next/master linus/master v6.7-rc7 next-20231222]
[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/Neeraj-Sanjay-Kale/Bluetooth-btnxpuart-Resolve-TX-timeout-error-in-power-save-stress-test/20231226-193718
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
patch link: https://lore.kernel.org/r/20231226113110.3923962-1-neeraj.sanjaykale%40nxp.com
patch subject: [PATCH v2] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231227/202312271920.D4X4fO6I-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231227/202312271920.D4X4fO6I-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/202312271920.D4X4fO6I-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/bluetooth/btnxpuart.c: In function 'ps_control':
>> drivers/bluetooth/btnxpuart.c:356:25: error: implicit declaration of function 'usleep'; did you mean 'fsleep'? [-Werror=implicit-function-declaration]
356 | usleep(2000); /* Allow chip to detect UART-break and enter sleep */
| ^~~~~~
| fsleep
cc1: some warnings being treated as errors
vim +356 drivers/bluetooth/btnxpuart.c
333
334 static void ps_control(struct hci_dev *hdev, u8 ps_state)
335 {
336 struct btnxpuart_dev *nxpdev = hci_get_drvdata(hdev);
337 struct ps_data *psdata = &nxpdev->psdata;
338 int status;
339
340 if (psdata->ps_state == ps_state ||
341 !test_bit(BTNXPUART_SERDEV_OPEN, &nxpdev->tx_state))
342 return;
343
344 mutex_lock(&psdata->ps_lock);
345 switch (psdata->cur_h2c_wakeupmode) {
346 case WAKEUP_METHOD_DTR:
347 if (ps_state == PS_STATE_AWAKE)
348 status = serdev_device_set_tiocm(nxpdev->serdev, TIOCM_DTR, 0);
349 else
350 status = serdev_device_set_tiocm(nxpdev->serdev, 0, TIOCM_DTR);
351 break;
352 case WAKEUP_METHOD_BREAK:
353 default:
354 if (ps_state == PS_STATE_AWAKE) {
355 status = serdev_device_break_ctl(nxpdev->serdev, 0);
> 356 usleep(2000); /* Allow chip to detect UART-break and enter sleep */
357 } else {
358 status = serdev_device_break_ctl(nxpdev->serdev, -1);
359 }
360 bt_dev_dbg(hdev, "Set UART break: %s, status=%d",
361 str_on_off(ps_state == PS_STATE_SLEEP), status);
362 break;
363 }
364 if (!status)
365 psdata->ps_state = ps_state;
366 mutex_unlock(&psdata->ps_lock);
367
368 if (ps_state == PS_STATE_AWAKE)
369 btnxpuart_tx_wakeup(nxpdev);
370 }
371
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-27 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 11:31 [PATCH v2] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test Neeraj Sanjay Kale
2023-12-27 2:35 ` kernel test robot
2023-12-27 11:41 ` 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=202312271920.D4X4fO6I-lkp@intel.com \
--to=lkp@intel.com \
--cc=amitkumar.karwar@nxp.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rohit.fule@nxp.com \
--cc=sherry.sun@nxp.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