[bluez/bluez] abf5ba: adapter: Keep track of whether the adapter is rfki...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: abf5ba6b80add53a4617ffdd06ac2102095347c2
      https://github.com/bluez/bluez/commit/abf5ba6b80add53a4617ffdd06ac2102095347c2
  Author: Bastien Nocera <hadess@xxxxxxxxxx>
  Date:   2022-09-01 (Thu, 01 Sep 2022)

  Changed paths:
    M src/adapter.c
    M src/adapter.h
    M src/btd.h
    M src/rfkill.c

  Log Message:
  -----------
  adapter: Keep track of whether the adapter is rfkill'ed

Instead of only replying to D-Bus requests with an error saying the
adapter is blocked, keep track of the rfkill being enabled or disabled
so we know the rfkill state of the adapter at all times.


  Commit: 58021a665b7f608e20096328bb28e24d3fe8bf0d
      https://github.com/bluez/bluez/commit/58021a665b7f608e20096328bb28e24d3fe8bf0d
  Author: Bastien Nocera <hadess@xxxxxxxxxx>
  Date:   2022-09-01 (Thu, 01 Sep 2022)

  Changed paths:
    M src/adapter.c

  Log Message:
  -----------
  adapter: Implement PowerState property

This property should allow any program to show whether an adapter is in
the process of being turned on.

As turning on an adapter isn't instantaneous, it's important that the UI
reflects the transitional state of the adapter's power, and doesn't
assume the device is already turned on but not yet working, or still off
despite having requested for it to be turned on, in both cases making
the UI feel unresponsive.

This can also not be implemented in front-ends directly as, then,
the status of an adapter wouldn't be reflected correctly in the Settings
window if it's turned on in the system menu. Implementing it in the
front-ends would also preclude from having feedback about the state of
the adapter when bluetoothd is the one powering up the adapter after the
rfkill was unblocked.

See https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/121
and the original https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5773


  Commit: 48992da64f52a4ca73221689e9e116ae93e0ba03
      https://github.com/bluez/bluez/commit/48992da64f52a4ca73221689e9e116ae93e0ba03
  Author: Bastien Nocera <hadess@xxxxxxxxxx>
  Date:   2022-09-01 (Thu, 01 Sep 2022)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Print the PowerState property


  Commit: 6e49216ad47dc8ffd9cbf2066d13fd7b59613c98
      https://github.com/bluez/bluez/commit/6e49216ad47dc8ffd9cbf2066d13fd7b59613c98
  Author: Bastien Nocera <hadess@xxxxxxxxxx>
  Date:   2022-09-01 (Thu, 01 Sep 2022)

  Changed paths:
    M doc/adapter-api.txt

  Log Message:
  -----------
  adapter-api: Add PowerState property documentation


  Commit: 61f4f2895882a19c402e93ef4ba7bb6b802015a4
      https://github.com/bluez/bluez/commit/61f4f2895882a19c402e93ef4ba7bb6b802015a4
  Author: Bastien Nocera <hadess@xxxxxxxxxx>
  Date:   2022-09-01 (Thu, 01 Sep 2022)

  Changed paths:
    M src/adapter.c

  Log Message:
  -----------
  adapter: Fix typo in function name


Compare: https://github.com/bluez/bluez/compare/49b8c5901584...61f4f2895882



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux