From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: luiz.dentz@gmail.com, marcel@holtmann.org
Cc: alainm@chromium.org, chromeos-bluetooth-upstreaming@chromium.org,
linux-bluetooth@vger.kernel.org,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Subject: [BlueZ PATCH v4 1/5] mgmt: Update docs for Add Device
Date: Thu, 19 Mar 2020 18:50:19 -0700 [thread overview]
Message-ID: <20200319185000.BlueZ.v4.1.Idb4f0444e40064a861ee73b098264abd30114aaa@changeid> (raw)
In-Reply-To: <20200320015023.85896-1-abhishekpandit@chromium.org>
Update the docs for Add Device with information on flags mask and value.
Add information on the Wakeable flag that can be set to allow the device
to wake the system from suspend.
---
Changes in v4:
* Newly added support in Add Device for flags
Changes in v3: None
Changes in v2: None
doc/mgmt-api.txt | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 27a41f334..e99c23710 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -1997,6 +1997,8 @@ Add Device Command
Command Parameters: Address (6 Octets)
Address_Type (1 Octet)
Action (1 Octet)
+ Flags Mask (1 Octet)
+ Flags Value (1 Octet)
Return Parameters: Address (6 Octets)
Address_Type (1 Octet)
@@ -2014,6 +2016,9 @@ Add Device Command
1 Allow incoming connection
2 Auto-connect remote device
+ The following flags are supported:
+ 0x1 Wakeable
+
With the Action 0, when the device is found, a new Device Found
event will be sent indicating this device is available. This
action is only valid for LE Public and LE Random address types.
@@ -2036,6 +2041,13 @@ Add Device Command
connectable setting is off. This acts as list of known trusted
devices.
+ To set flags on the device, first set the bit in the mask for the
+ flag to set and then set or clear the bit in the value to indicate
+ whether the flag should be set.
+
+ The Wakeable flag controls whether this device can wake the system
+ from suspend.
+
This command can be used when the controller is not powered and
all settings will be programmed once powered.
--
2.25.1.696.g5e7596f4ac-goog
next prev parent reply other threads:[~2020-03-20 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 1:50 [BlueZ PATCH v4 0/5] device: Allow devices to be marked as wake capable Abhishek Pandit-Subedi
2020-03-20 1:50 ` Abhishek Pandit-Subedi [this message]
2020-03-25 19:57 ` [BlueZ PATCH v4 1/5] mgmt: Update docs for Add Device Luiz Augusto von Dentz
2020-03-25 21:25 ` Marcel Holtmann
2020-03-25 21:49 ` Abhishek Pandit-Subedi
2020-03-20 1:50 ` [BlueZ PATCH v4 2/5] device: Support marking a device with wake allowed Abhishek Pandit-Subedi
2020-03-25 19:54 ` Luiz Augusto von Dentz
2020-03-25 20:20 ` Abhishek Pandit-Subedi
2020-03-20 1:50 ` [BlueZ PATCH v4 3/5] client: Display wake allowed property with info Abhishek Pandit-Subedi
2020-03-20 1:50 ` [BlueZ PATCH v4 4/5] doc/device-api: Add WakeAllowed Abhishek Pandit-Subedi
2020-03-20 1:50 ` [BlueZ PATCH v4 5/5] input: Make HID devices support wake Abhishek Pandit-Subedi
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=20200319185000.BlueZ.v4.1.Idb4f0444e40064a861ee73b098264abd30114aaa@changeid \
--to=abhishekpandit@chromium.org \
--cc=alainm@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).