Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Cc: kiran.k@intel.com, chethan.tumkur.narayan@intel.com,
	Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Subject: [PATCH v1 0/1] rfkill: expose hardware-only block state
Date: Wed, 30 Sep 2026 13:12:06 +0530	[thread overview]
Message-ID: <cover.1790752797.git.aluvala.sai.teja@intel.com> (raw)


This series adds a public rfkill helper for querying the hardware-only
block state.

The existing rfkill_blocked() helper reports the effective state, which
is set when either hardware or software rfkill is active. Callers that
need to distinguish those cases currently cannot do so because struct
rfkill is opaque.

Add rfkill_hard_blocked(), protected by the rfkill lock and available
with a CONFIG_RFKILL-disabled stub. The helper is used by a follow-up
Bluetooth debugfs test hook, which must verify hardware rfkill state
without confusing it with a software block.

The follow-up Bluetooth series will be submitted separately to
bluetooth-next and depends on this patch.

The patch has been prepared against wireless-next/main.

Changes in v1:
  - Initial version.

Sai Teja Aluvala (1):
  rfkill: add rfkill_hard_blocked() helper

 include/linux/rfkill.h | 12 ++++++++++++
 net/rfkill/core.c      | 13 +++++++++++++
 2 files changed, 25 insertions(+)


base-commit: 21b4248bfa0f410fa22202fc2c82f4808d672cda
-- 
2.53.0


             reply	other threads:[~2026-09-30  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  7:42 Sai Teja Aluvala [this message]
2026-09-30  7:42 ` [PATCH v1 1/1] rfkill: add rfkill_hard_blocked() helper Sai Teja Aluvala
2026-09-30 11:40   ` Johannes Berg

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.1790752797.git.aluvala.sai.teja@intel.com \
    --to=aluvala.sai.teja@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kiran.k@intel.com \
    --cc=linux-wireless@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