[bluez/bluez] b6ac5e: emulator: Add btdev_send_event

[bluez/bluez] b6ac5e: emulator: Add btdev_send_event

[IAROSLAV VOITOVYCH]

  Branch: refs/heads/1182788
  Home:   https://github.com/bluez/bluez
  Commit: b6ac5ee71f8a29a5b93dc01215ccc0f311e38acf
      https://github.com/bluez/bluez/commit/b6ac5ee71f8a29a5b93dc01215ccc0f311e38acf
  Author: Iaroslav Voitovych <yaroslav.voytovych@gmail.com>
  Date:   2026-10-10 (Sat, 10 Oct 2026)

  Changed paths:
    M emulator/btdev.c
    M emulator/btdev.h

  Log Message:
  -----------
  emulator: Add btdev_send_event

Allow a tester to send an arbitrary event from the emulated controller,
for instance from a command hook, so that the order of events around a
command can be chosen by the test.


  Commit: ba334e6c32d4bcc3a9dbc1b863e40985c57c345a
      https://github.com/bluez/bluez/commit/ba334e6c32d4bcc3a9dbc1b863e40985c57c345a
  Author: Iaroslav Voitovych <yaroslav.voytovych@gmail.com>
  Date:   2026-10-10 (Sat, 10 Oct 2026)

  Changed paths:
    M emulator/vhci.c
    M emulator/vhci.h

  Log Message:
  -----------
  emulator/vhci: Add vhci_set_quirk_simultaneous_discovery

Set or clear HCI_QUIRK_SIMULTANEOUS_DISCOVERY through the kernel's
quirk_simultaneous_discovery debugfs entry, which only accepts writes
while the controller is down.

This entry name is the longest so far: its path does not fit in the
64 byte buffer of vhci_debugfs_write() from hci1000 on, so size the
buffer with PATH_MAX and use snprintf().


  Commit: 17c1ddcf1e0b078aa8d8ee9cf892e1c4e784bd38
      https://github.com/bluez/bluez/commit/17c1ddcf1e0b078aa8d8ee9cf892e1c4e784bd38
  Author: Iaroslav Voitovych <yaroslav.voytovych@gmail.com>
  Date:   2026-10-10 (Sat, 10 Oct 2026)

  Changed paths:
    M tools/mgmt-tester.c

  Log Message:
  -----------
  mgmt-tester: Add simultaneous discovery stop tests

With HCI_QUIRK_SIMULTANEOUS_DISCOVERY, kernels without commit
96d006ae6445 ("Bluetooth: hci_event: fix simultaneous discovery stuck
in FINDING") stay in DISCOVERY_FINDING when the Inquiry Complete event
arrives after LE Set Scan Enable (disable) was sent but before its
Command Complete: no Discovering (disabled) event is sent and every
later Start Discovery fails with Busy.

Both tests set the quirk through debugfs and send the Inquiry Complete
themselves: one second into the discovery (Simultaneous Inquiry First,
the normal order) or from the LE Set Scan Enable (disable) command
hook, before its Command Complete (Simultaneous Inquiry Late). The LE
scan timeout itself is not shortened. One second after that command a
new Start Discovery probes the state; a test fails if no Discovering
(disabled) event came before the probe or if the probe does not
succeed. Without the kernel fix the Late test fails. If the debugfs
entry cannot be opened, the tests are reported as Not Run.


Compare: https://github.com/bluez/bluez/compare/b6ac5ee71f8a%5E...17c1ddcf1e0b

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