From: patchwork-bot+bluetooth@kernel.org
To: Doug Anderson <dianders@chromium.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
angelogioacchino.delregno@collabora.com, chris.lu@mediatek.com,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()
Date: Tue, 21 Jan 2025 16:40:34 +0000 [thread overview]
Message-ID: <173747763400.49514.16130463515349826883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250115193636.1.If8b655b5c6877bd9a1136ba0f1cd61cc6a4b6e9c@changeid>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 Jan 2025 19:36:36 -0800 you wrote:
> The documentation for usb_driver_claim_interface() says that "the
> device lock" is needed when the function is called from places other
> than probe(). This appears to be the lock for the USB interface
> device. The Mediatek btusb code gets called via this path:
>
> Workqueue: hci0 hci_power_on [bluetooth]
> Call trace:
> usb_driver_claim_interface
> btusb_mtk_claim_iso_intf
> btusb_mtk_setup
> hci_dev_open_sync
> hci_power_on
> process_scheduled_works
> worker_thread
> kthread
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()
https://git.kernel.org/bluetooth/bluetooth-next/c/ec5570088c6a
- [2/2] Bluetooth: btusb: mediatek: Add err code to btusb claim iso printout
https://git.kernel.org/bluetooth/bluetooth-next/c/6ca1c15fcb92
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:[~2025-01-21 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 3:36 [PATCH 1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() Douglas Anderson
2025-01-16 3:36 ` [PATCH 2/2] Bluetooth: btusb: mediatek: Add err code to btusb claim iso printout Douglas Anderson
2025-01-16 3:56 ` [1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() bluez.test.bot
2025-01-21 16: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=173747763400.49514.16130463515349826883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chris.lu@mediatek.com \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.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.