Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
	chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v3] Bluetooth: btintel: Add UEFI standalone static SAR support
Date: Wed, 18 Nov 2026 14:10:05 +0000	[thread overview]
Message-ID: <179501100528.1728928.5021407494750896247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118115542.3167414-1-aluvala.sai.teja@intel.com>

Hello:

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

On Wed, 18 Nov 2026 17:25:42 +0530 you wrote:
> Scorpius Peak2 and later platforms, excluding BlazarI and BlazarIW,
> provide Bluetooth standalone static SAR sub-band limits (BSSS) through
> the UefiCnvBtBSSS UEFI variable. There is no corresponding ACPI BSSS
> configuration. Applying these limits requires SAR to be enabled in
> UefiCnvBtBRDS as well as in BSSS.
> 
> Read revision 2 UEFI BRDS and BSSS variables using their shared layout.
> Program the BRDS 2.4 GHz limits, then enable standalone SAR and write
> the BSSS per-chain sub-band limits. Send SAR initialization complete
> after any UEFI DDC attempt, including failures, while preserving the
> original error.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: btintel: Add UEFI standalone static SAR support
    https://git.kernel.org/bluetooth/bluetooth-next/c/4bc12982b9b6

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



      reply	other threads:[~2026-11-18 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  8:58 [PATCH v1] Bluetooth: btintel: Add UEFI standalone static SAR support Sai Teja Aluvala
2026-11-07 15:11 ` [v1] " bluez.test.bot
2026-11-08  9:36 ` [PATCH v2] " Sai Teja Aluvala
2026-11-08 15:36   ` [v2] " bluez.test.bot
2026-11-08 20:32   ` [PATCH v2] " Paul Menzel
2026-11-09  8:12     ` Aluvala Sai Teja
2026-11-18 11:55   ` [PATCH v3] " Sai Teja Aluvala
2026-11-18 14: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=179501100528.1728928.5021407494750896247.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=aluvala.sai.teja@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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