All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Lebedev <lsa.uz@pm.me>
To: Ravindra <ravindra@intel.com>, linux-bluetooth@vger.kernel.org
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Kiran K <kiran.k@intel.com>,
	Chethan Tumkur Narayan <chethan.tumkur.narayan@intel.com>,
	"Vladimir V. Kondratyev" <vladimirkondratyev2@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows
Date: Mon, 28 Sep 2026 21:14:22 +0000	[thread overview]
Message-ID: <20260928211413.26759-1-lsa.uz@pm.me> (raw)
In-Reply-To: <20260928171003.2925480-1-ravindra@intel.com>

Ravindra,

Thank you for taking the race on and fixing it in 3/4.

I ran v6 on the Surface Pro 11 bench (BE201 8086:a876, s2idle, the same
base as for v4), with an instrumented copy that forces each path:

- plain cycles: the handler records D3 and re-arms RX, as before
- a gp0 dropped on the way down: one 200 ms timeout, the register read
  again, D3 recorded
- the handler's D0 or D3 case forced to break: the fallback records D3,
  or claims D0 and re-arms RX
- the race: the handler held in case D3 for 300 ms after deciding to
  claim D0, past the 200 ms wait. With v5 the fallback re-armed RX at
  203 ms and the handler again at 300 ms. With v6 the fallback waited on
  irq_lock, found D0 claimed and returned, and RX was re-armed once.

After every cycle Bluetooth answered an HCI command and scanned.

Tested-by: Sergey Lebedev <lsa.uz@pm.me>

Sergey


  parent reply	other threads:[~2026-09-28 21:14 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 ` Sergey Lebedev [this message]
2026-09-29 15:10 ` [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows patchwork-bot+bluetooth

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=20260928211413.26759-1-lsa.uz@pm.me \
    --to=lsa.uz@pm.me \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --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.