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 3/5] client: Display wake allowed property with info
Date: Thu, 19 Mar 2020 18:50:21 -0700 [thread overview]
Message-ID: <20200319185000.BlueZ.v4.3.I80d0e557c53f464415742324eb3ff2cc4cdcbc2a@changeid> (raw)
In-Reply-To: <20200320015023.85896-1-abhishekpandit@chromium.org>
Display whether the device is configured as wake allowed when queried
with cmd_info.
---
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.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 ` [BlueZ PATCH v4 1/5] mgmt: Update docs for Add Device Abhishek Pandit-Subedi
2020-03-25 19:57 ` 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 ` Abhishek Pandit-Subedi [this message]
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.3.I80d0e557c53f464415742324eb3ff2cc4cdcbc2a@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).