linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: luiz.dentz@gmail.com, marcel@holtmann.org, alainm@chromium.org
Cc: linux-bluetooth@vger.kernel.org,
	chromeos-bluetooth-upstreaming@chromium.org,
	Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Subject: [BlueZ PATCH v3 1/5] mgmt: Add docs for Set Wake Capable
Date: Mon, 27 Jan 2020 18:05:01 -0800	[thread overview]
Message-ID: <20200127180433.BlueZ.v3.1.I999b93b65e613324dbbd16a1cf493be72fa06ad1@changeid> (raw)
In-Reply-To: <20200128020505.239349-1-abhishekpandit@chromium.org>

Add docs for new management operation to mark a device as wake capable.

---

Changes in v3: None
Changes in v2:
* Separated docs/mgmt-api.txt into its own patch

 doc/mgmt-api.txt | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 1e59acc54..8a73a9bb9 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -3047,6 +3047,25 @@ Load Blocked Keys Command
 	Possible errors:	Invalid Parameters
 				Invalid Index
 
+Set Wake Capable Command
+===========================
+
+	Command Code:		0x0047
+	Controller Index:	<controller id>
+	Command Parameters:	Address (6 Octets)
+				Address_Type (1 Octet)
+				Wake Capable (1 Octet)
+	Return Parameters:	Address (6 Octets)
+				Address_Type (1 Octet)
+				Wake Capable (1 Octet)
+
+	This command sets whether a bluetooth device is capable of waking the
+	system from suspend. This property is used to set the event filter and
+	LE whitelist when the system enters suspend.
+
+	Possible errors:	Failed
+				Invalid Parameters
+				Invalid Index
 
 Command Complete Event
 ======================
-- 
2.25.0.341.g760bfbb309-goog


  reply	other threads:[~2020-01-28  2:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  2:05 [BlueZ PATCH v3 0/5] device: Allow devices to be marked as wake capable Abhishek Pandit-Subedi
2020-01-28  2:05 ` Abhishek Pandit-Subedi [this message]
2020-01-29  4:33   ` [BlueZ PATCH v3 1/5] mgmt: Add docs for Set Wake Capable Marcel Holtmann
2020-01-29 17:44     ` Abhishek Pandit-Subedi
2020-01-29 18:06       ` Marcel Holtmann
2020-01-29 18:45         ` Abhishek Pandit-Subedi
2020-01-29 19:03           ` Marcel Holtmann
2020-03-12  4:39             ` Abhishek Pandit-Subedi
2020-03-12 21:45               ` Abhishek Pandit-Subedi
2020-01-28  2:05 ` [BlueZ PATCH v3 2/5] device: Allow device to be marked as wake capable Abhishek Pandit-Subedi
2020-01-28 18:43   ` Abhishek Pandit-Subedi
2020-01-28  2:05 ` [BlueZ PATCH v3 3/5] client: Display wake capable property with info Abhishek Pandit-Subedi
2020-01-28  2:05 ` [BlueZ PATCH v3 4/5] doc/device-api: Add WakeCapable Abhishek Pandit-Subedi
2020-01-28  2:05 ` [BlueZ PATCH v3 5/5] input: Make HID devices wake capable Abhishek Pandit-Subedi
2020-01-28 20:31 ` [BlueZ PATCH v3 0/5] device: Allow devices to be marked as " Luiz Augusto von Dentz
2020-01-28 22:06   ` 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=20200127180433.BlueZ.v3.1.I999b93b65e613324dbbd16a1cf493be72fa06ad1@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).