All of lore.kernel.org
 help / color / mirror / Atom feed
From: aluvalasaitejaintel <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e70640: emulator: add generic HW rfkill test tool
Date: Wed, 30 Sep 2026 07:10:18 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1176664/000000-e70640@github.com> (raw)

  Branch: refs/heads/1176664
  Home:   https://github.com/bluez/bluez
  Commit: e706401fd86e46a6e3240fc8eed880d0f8d7bebc
      https://github.com/bluez/bluez/commit/e706401fd86e46a6e3240fc8eed880d0f8d7bebc
  Author: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
  Date:   2026-09-30 (Wed, 30 Sep 2026)

  Changed paths:
    M Makefile.tools
    A emulator/hci_rfkill.c

  Log Message:
  -----------
  emulator: add generic HW rfkill test tool

Add emulator/hci_rfkill, a standalone tool that drives the
force_hw_rfkill debugfs hook for an hciN device and verifies the
reported hardware-block state against /sys/class/rfkill. The hook
exercises the generic net/bluetooth rfkill path for any HCI transport;
it does not test the driver's hardware interrupt or register handling.

Support assert-only, deassert-only, and toggle modes. Validate the
hciN argument before using it in filesystem paths. In toggle mode,
if asserting the block was written successfully but subsequent
verification fails, still attempt a verified unblock while preserving
the failure result. Do not attempt an unblock when the assert write
itself fails.

The optional -r/--restore mode snapshots the adapter's up/down state
via HCIGETDEVINFO and restores it via HCIDEVUP/HCIDEVDOWN, following
the raw HCI control-socket approach used by tools/hciconfig.c.

Usage: hci_rfkill [-e|-d|-t] [-r] hciN

Signed-off-by: Sai Teja Aluvala <aluvala.sai.teja@intel.com>



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-09-30 14:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/1176664/000000-e70640@github.com \
    --to=noreply@github.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 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.