From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, amitkumar.karwar@nxp.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
sherry.sun@nxp.com, rohit.fule@nxp.com
Subject: Re: [PATCH v3] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test
Date: Tue, 02 Jan 2024 17:40:53 +0000 [thread overview]
Message-ID: <170421725348.27590.16958999714015183552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231227132927.3938396-1-neeraj.sanjaykale@nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 27 Dec 2023 18:59:27 +0530 you wrote:
> This fixes the tx timeout issue seen while running a stress test on
> btnxpuart for couple of hours, such that the interval between two HCI
> commands coincide with the power save timeout value of 2 seconds.
>
> Test procedure using bash script:
> <load btnxpuart.ko>
> hciconfig hci0 up
> //Enable Power Save feature
> hcitool -i hci0 cmd 3f 23 02 00 00
> while (true)
> do
> hciconfig hci0 leadv
> sleep 2
> hciconfig hci0 noleadv
> sleep 2
> done
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test
https://git.kernel.org/bluetooth/bluetooth-next/c/c7ee0bc8db32
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-01-02 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 13:29 [PATCH v3] Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test Neeraj Sanjay Kale
2023-12-27 13:56 ` [v3] " bluez.test.bot
2024-01-02 17:40 ` patchwork-bot+bluetooth [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=170421725348.27590.16958999714015183552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).