Linux bluetooth development
 help / color / mirror / Atom feed
From: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org
Cc: kiran.k@intel.com, chethan.tumkur.narayan@intel.com,
	Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Subject: [PATCH v2 0/2] Bluetooth: add hardware rfkill handling
Date: Fri,  2 Oct 2026 07:13:56 +0530	[thread overview]
Message-ID: <cover.1790905146.git.aluvala.sai.teja@intel.com> (raw)

This series adds hardware rfkill handling for the Intel PCIe transport and
the Bluetooth-side notification path.

The resulting flow is:

  transport hardware event
    -> hci_rfkill_set_hw_state()
    -> rfkill hardware state
    -> hdev->rfkill_block work
    -> HCI_RFKILLED state and device power handling

For Intel PCIe controllers, the series adds GP2 and HW_RFKILL MSI-X
handling, IPC_CONTROL doorbell synchronization, delayed state checking,
reset/shutdown/remove lifecycle handling, and notification of the
generic HCI rfkill layer.

Compared with v1, this version drops the Bluetooth-specific debugfs test
hook, the redundant hdev->rfkill pointer-clear patch, and the separate
RFKILL-core helper dependency. The real btintel_pcie hardware event path
and HCI notification interface are retained.

Sai Teja Aluvala (2):
  Bluetooth: Add interface to allow stack to communicate hw rfkill
    events
  Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow

 drivers/bluetooth/btintel_pcie.c | 140 ++++++++++++++++++++++++++++++-
 drivers/bluetooth/btintel_pcie.h |  27 ++++++
 include/net/bluetooth/hci_core.h |   3 +
 net/bluetooth/hci_core.c         |  34 ++++++++
 4 files changed, 200 insertions(+), 4 deletions(-)


base-commit: 3b44711c52eaf62723a4a715e1b7b4e49f1595ce
-- 
2.53.0

             reply	other threads:[~2026-10-02  1:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  1:43 Sai Teja Aluvala [this message]
2026-10-02  1:43 ` [PATCH v2 1/2] Bluetooth: Add interface to allow stack to communicate hw rfkill events Sai Teja Aluvala
2026-10-02  3:14   ` Bluetooth: add hardware rfkill handling bluez.test.bot
2026-10-02  1:43 ` [PATCH v2 2/2] Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow Sai Teja Aluvala
2026-10-02 15:24 ` [PATCH v2 0/2] Bluetooth: add hardware rfkill handling Luiz Augusto von Dentz

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=cover.1790905146.git.aluvala.sai.teja@intel.com \
    --to=aluvala.sai.teja@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox