Linux bluetooth development
 help / color / mirror / Atom feed
From: Matthew Schwartz <matthew.schwartz@linux.dev>
To: linux-bluetooth@vger.kernel.org
Cc: Matthew Schwartz <matthew.schwartz@linux.dev>
Subject: [PATCH BlueZ 3/3] doc: Mark WakeAllowed as optional
Date: Sat, 25 Jul 2026 13:18:56 -0700	[thread overview]
Message-ID: <20260725201856.2142333-4-matthew.schwartz@linux.dev> (raw)
In-Reply-To: <20260725201856.2142333-1-matthew.schwartz@linux.dev>

WakeAllowed is only present on devices with a profile that supports
wake configuration, and now only when the adapter itself is able to
wake the host. Mark it optional like the other conditional Device1
properties and document when it is present.
---
 doc/org.bluez.Device.rst | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/org.bluez.Device.rst b/doc/org.bluez.Device.rst
index 3e6a30aaf..8b6b9e866 100644
--- a/doc/org.bluez.Device.rst
+++ b/doc/org.bluez.Device.rst
@@ -330,11 +330,14 @@ Examples:
 :bluetoothctl: > block [dev]
 :bluetoothctl: > unblock [dev]
 
-boolean WakeAllowed [readwrite]
-```````````````````````````````
+boolean WakeAllowed [readwrite, optional]
+`````````````````````````````````````````
 
 If set to true this device will be allowed to wake the host from system suspend.
 
+Only present on devices with a profile that supports wake configuration (e.g.
+HID) and when the host controller is configured to be able to wake the system.
+
 Examples:
 
 :bluetoothctl: > wake [dev] [on/off]
-- 
2.55.0


      parent reply	other threads:[~2026-07-25 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25 20:18 [PATCH BlueZ 0/3] Hide WakeAllowed when the adapter cannot wake the host Matthew Schwartz
2026-07-25 20:18 ` [PATCH BlueZ 1/3] adapter: Add btd_adapter_may_wake() Matthew Schwartz
2026-07-25 21:19   ` Hide WakeAllowed when the adapter cannot wake the host bluez.test.bot
2026-07-25 20:18 ` [PATCH BlueZ 2/3] device: Hide WakeAllowed when adapter cannot wake Matthew Schwartz
2026-07-25 20:18 ` Matthew Schwartz [this message]

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=20260725201856.2142333-4-matthew.schwartz@linux.dev \
    --to=matthew.schwartz@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox