From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Cc: alainm@chromium.org, marcel@holtmann.org,
chromeos-bluetooth-upstreaming@chromium.org,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Subject: [BlueZ PATCH v5 4/6] client: Display wake allowed property with info
Date: Mon, 22 Jun 2020 16:40:49 -0700 [thread overview]
Message-ID: <20200622164003.BlueZ.v5.4.I45dbf8ee15dff6c9346dc9754574a0be9bee1fa1@changeid> (raw)
In-Reply-To: <20200622234051.206800-1-abhishekpandit@chromium.org>
Display whether the device is configured as wake allowed when queried
with cmd_info.
---
Changes in v5: None
Changes in v4:
* Renamed WakeCapable to WakeAllowed
Changes in v3: None
Changes in v2:
* Newly added to show whether device is wake capable
* Removed automatically setting wake capable for HID devices
client/main.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/client/main.c b/client/main.c
index 422da5593..4953f50f0 100644
--- a/client/main.c
+++ b/client/main.c
@@ -1637,6 +1637,7 @@ static void cmd_info(int argc, char *argv[])
print_property(proxy, "Trusted");
print_property(proxy, "Blocked");
print_property(proxy, "Connected");
+ print_property(proxy, "WakeAllowed");
print_property(proxy, "LegacyPairing");
print_uuids(proxy);
print_property(proxy, "Modalias");
--
2.27.0.111.gc72c7da667-goog
next prev parent reply other threads:[~2020-06-22 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 23:40 [BlueZ PATCH v5 0/6] device: Allow devices to be marked as wake capable Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 1/6] mgmt: Add mgmt op and events for device flags Abhishek Pandit-Subedi
2020-06-22 23:49 ` device: Allow devices to be marked as wake capable bluez.test.bot
2020-06-22 23:40 ` [BlueZ PATCH v5 2/6] monitor: Decode device flags mgmt ops and event Abhishek Pandit-Subedi
2020-06-22 23:47 ` [BlueZ,v5,2/6] " bluez.test.bot
2020-06-22 23:40 ` [BlueZ PATCH v5 3/6] device: Support marking a device with wake allowed Abhishek Pandit-Subedi
2020-06-22 23:47 ` [BlueZ,v5,3/6] " bluez.test.bot
2020-06-23 0:10 ` [BlueZ PATCH v5 3/6] " Luiz Augusto von Dentz
2020-06-24 3:53 ` Abhishek Pandit-Subedi
2020-06-22 23:40 ` Abhishek Pandit-Subedi [this message]
2020-06-22 23:40 ` [BlueZ PATCH v5 5/6] doc/device-api: Add WakeAllowed Abhishek Pandit-Subedi
2020-06-22 23:40 ` [BlueZ PATCH v5 6/6] 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=20200622164003.BlueZ.v5.4.I45dbf8ee15dff6c9346dc9754574a0be9bee1fa1@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).