Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Xuhua Zhang <zhangxuhua@kylinsec.com.cn>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_ll: Sleep while waiting for the controller to power up
Date: Tue, 08 Sep 2026 16:30:28 +0000	[thread overview]
Message-ID: <178888502815.3627954.2543217288175652376.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8A1A2E77C277A87D+20260907151245.13609-1-zhangxuhua@kylinsec.com.cn>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon,  7 Sep 2026 23:12:45 +0800 you wrote:
> ll_setup() busy-waits for 100 ms after asserting the controller enable
> GPIO on each firmware download attempt. With retries this can occupy
> the CPU for up to 400 ms.
> 
> The setup callback runs in sleepable context and already uses msleep(),
> gpiod_set_value_cansleep() and synchronous firmware commands. Replace
> mdelay(100) with msleep(100) so the CPU can run other work during the
> power-up delay. Keep the requested delay and subsequent CTS wait.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_ll: Sleep while waiting for the controller to power up
    https://git.kernel.org/bluetooth/bluetooth-next/c/1d978753498a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-08 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 15:12 [PATCH] Bluetooth: hci_ll: Sleep while waiting for the controller to power up Xuhua Zhang
2026-09-08 15:54 ` bluez.test.bot
2026-09-08 16:30 ` 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=178888502815.3627954.2543217288175652376.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=zhangxuhua@kylinsec.com.cn \
    /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