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 v6 4/6] client: Display wake allowed property with info
Date: Mon, 29 Jun 2020 16:02:21 -0700 [thread overview]
Message-ID: <20200629160206.BlueZ.v6.4.I45dbf8ee15dff6c9346dc9754574a0be9bee1fa1@changeid> (raw)
In-Reply-To: <20200629230223.3538949-1-abhishekpandit@chromium.org>
Display whether the device is configured as wake allowed when queried
with cmd_info.
---
Changes in v6: None
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.212.ge8ba1cc988-goog
next prev parent reply other threads:[~2020-06-29 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 23:02 [BlueZ PATCH v6 0/6] device: Allow devices to be marked as wake capable Abhishek Pandit-Subedi
2020-06-29 23:02 ` [BlueZ PATCH v6 1/6] mgmt: Add mgmt op and events for device flags Abhishek Pandit-Subedi
2020-06-29 23:19 ` device: Allow devices to be marked as wake capable bluez.test.bot
2020-06-29 23:02 ` [BlueZ PATCH v6 2/6] monitor: Decode device flags mgmt ops and event Abhishek Pandit-Subedi
2020-06-29 23:02 ` [BlueZ PATCH v6 3/6] device: Support marking a device with wake allowed Abhishek Pandit-Subedi
2020-06-29 23:17 ` [BlueZ,v6,3/6] " bluez.test.bot
2020-06-29 23:02 ` Abhishek Pandit-Subedi [this message]
2020-06-29 23:02 ` [BlueZ PATCH v6 5/6] doc/device-api: Add WakeAllowed Abhishek Pandit-Subedi
2020-06-29 23:02 ` [BlueZ PATCH v6 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=20200629160206.BlueZ.v6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.