All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Ravindra <ravindra@intel.com>
Cc: linux-bluetooth@vger.kernel.org, lsa.uz@pm.me,
	pmenzel@molgen.mpg.de, marcel@holtmann.org, luiz.dentz@gmail.com,
	kiran.k@intel.com, chethan.tumkur.narayan@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows
Date: Tue, 29 Sep 2026 15:10:12 +0000	[thread overview]
Message-ID: <179069461202.983246.15242898200206126696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928171003.2925480-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 22:39:59 +0530 you wrote:
> This series fixes the suspend/resume path of btintel_pcie.
> 
> Patch 1 refreshes the boot-stage register before the fallback state check.
> Patch 2 distinguishes S0ix from S3/S4 and routes thaw through a normal D0
> transition. Patch 3 verifies the state after GP0 and completes any missing
> RX or mailbox setup. It also serializes the alive-context claim between the
> GP0 handler and the PM fallback so only one path reinitializes the RX ring.
> Patch 4 clears the GP0 cause with a direct W1C write.
> 
> [...]

Here is the summary with links:
  - [v6,1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
    https://git.kernel.org/bluetooth/bluetooth-next/c/20dfccf8d854
  - [v6,2/4] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4
    https://git.kernel.org/bluetooth/bluetooth-next/c/79463c0de429
  - [v6,3/4] Bluetooth: btintel_pcie: verify and serialize D-state transitions
    https://git.kernel.org/bluetooth/bluetooth-next/c/7ec2ab118e34
  - [v6,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



      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 17:09 [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows Ravindra
2026-09-28 17:10 ` [PATCH v6 1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Ravindra
2026-09-28 21:29   ` Bluetooth: btintel_pcie: fix D-state transitions and PM flows bluez.test.bot
2026-09-28 17:10 ` [PATCH v6 2/4] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4 Ravindra
2026-09-28 17:10 ` [PATCH v6 3/4] Bluetooth: btintel_pcie: verify and serialize D-state transitions Ravindra
2026-09-28 17:10 ` [PATCH v6 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write Ravindra
2026-09-28 21:14 ` [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows Sergey Lebedev
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=179069461202.983246.15242898200206126696.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=linux-kernel@vger.kernel.org \
    --cc=lsa.uz@pm.me \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=ravindra@intel.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.