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 4/5] doc/device-api: Add WakeCapable
Date: Mon, 27 Jan 2020 18:05:04 -0800 [thread overview]
Message-ID: <20200127180433.BlueZ.v3.4.I5b076d560ee47afa4c9a8d5602aebf67ffd3d131@changeid> (raw)
In-Reply-To: <20200128020505.239349-1-abhishekpandit@chromium.org>
Add documentation for WakeCapable, which allows a device to wake the
system from suspend.
---
Changes in v3:
* Added documentation for WakeCapable
Changes in v2: None
doc/device-api.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 65d8fee37..492a7f8c7 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -189,6 +189,11 @@ Properties string Address [readonly]
drivers will also be removed and no new ones will
be probed as long as the device is blocked.
+ boolean WakeCapable [readwrite]
+
+ If set to true this device will be allowed to wake the
+ host processor from system suspend.
+
string Alias [readwrite]
The name alias for the remote device. The alias can
--
2.25.0.341.g760bfbb309-goog
next prev parent 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 ` [BlueZ PATCH v3 1/5] mgmt: Add docs for Set Wake Capable Abhishek Pandit-Subedi
2020-01-29 4:33 ` 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 ` Abhishek Pandit-Subedi [this message]
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.4.I5b076d560ee47afa4c9a8d5602aebf67ffd3d131@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).