From: patchwork-bot+bluetooth@kernel.org
To: Ravindra <ravindra@intel.com>
Cc: linux-bluetooth@vger.kernel.org, lsa.uz@pm.me,
vladimirkondratyev2@gmail.com, chethan.tumkur.narayan@intel.com,
kiran.k@intel.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v5 0/4] Bluetooth: btintel_pcie: fix D-state transition and PM flows
Date: Tue, 29 Sep 2026 15:10:18 +0000 [thread overview]
Message-ID: <179069461801.983246.2880891224850041177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928050344.2893790-1-ravindra@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 28 Sep 2026 10:33:40 +0530 you wrote:
> This series fixes the suspend/resume path of btintel_pcie.
>
> Patch 1 re-reads the boot stage register before the fallback state check,
> so a missed alive interrupt no longer leaves btintel_pcie_set_dxstate()
> testing a stale cache and aborting suspend with -EBUSY.
>
> Patch 2 distinguishes S0ix from S3/S4 so the controller is placed in the
> correct D-state, and routes .thaw through a normal D0 transition instead
> of an unnecessary FLR.
>
> [...]
Here is the summary with links:
- [v5,1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
https://git.kernel.org/bluetooth/bluetooth-next/c/20dfccf8d854
- [v5,2/4] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4
https://git.kernel.org/bluetooth/bluetooth-next/c/79463c0de429
- [v5,3/4] Bluetooth: btintel_pcie: verify state after alive interrupt
(no matching commit)
- [v5,4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write
https://git.kernel.org/bluetooth/bluetooth-next/c/6091d2771395
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:[~2026-09-29 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 5:03 [PATCH v5 0/4] Bluetooth: btintel_pcie: fix D-state transition and PM flows Ravindra
2026-09-28 5:03 ` [PATCH v5 1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Ravindra
2026-09-28 7:39 ` Bluetooth: btintel_pcie: fix D-state transition and PM flows bluez.test.bot
2026-09-28 5:03 ` [PATCH v5 2/4] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4 Ravindra
2026-09-28 5:03 ` [PATCH v5 3/4] Bluetooth: btintel_pcie: verify state after alive interrupt Ravindra
2026-09-28 16:59 ` Ravindra
2026-09-28 5:03 ` [PATCH v5 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write Ravindra
2026-09-29 15:10 ` 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=179069461801.983246.2880891224850041177.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=pmenzel@molgen.mpg.de \
--cc=ravindra@intel.com \
--cc=vladimirkondratyev2@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.