From: Sonny Sasaka <sonnysasaka@chromium.org>
To: linux-bluetooth-@vger.kernel.org, linux-bluetooth@vger.kernel.org
Cc: Sonny Sasaka <sonnysasaka@chromium.org>,
Alain Michaud <alainm@chromium.org>
Subject: [PATCH BlueZ 1/3] doc: Add "AllowInternalProfiles" property to org.bluez.Device1
Date: Mon, 13 Jul 2020 13:14:39 -0700 [thread overview]
Message-ID: <20200713201441.235959-2-sonnysasaka@chromium.org> (raw)
In-Reply-To: <20200713201441.235959-1-sonnysasaka@chromium.org>
Reviewed-by: Alain Michaud <alainm@chromium.org>
---
doc/device-api.txt | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 4e824d2de..5c2b2b26b 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -189,6 +189,19 @@ Properties string Address [readonly]
drivers will also be removed and no new ones will
be probed as long as the device is blocked.
+ boolean AllowInternalProfiles [readwrite]
+
+ If set to true, connection to this device will activate
+ BlueZ internal profiles (e.g. A2DP, HOG, Battery).
+ If set to false, internal profiles will not be activated
+ allowing the client to handle profiles which would
+ otherwise be controlled by internal handlers.
+ The default is configurable in main.conf.
+
+ Write operation to this property can only be accepted
+ when the device is not connected, otherwise
+ org.bluez.Error.Failed is returned.
+
boolean WakeAllowed [readwrite]
If set to true this device will be allowed to wake the
--
2.26.2
next prev parent reply other threads:[~2020-07-13 20:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 20:14 [PATCH BlueZ 0/3] Per-device option to enable/disable internal profiles Sonny Sasaka
2020-07-13 20:14 ` Sonny Sasaka [this message]
2020-07-13 20:14 ` [PATCH BlueZ 2/3] device: Add "AllowInternalProfiles" property to org.bluez.Device1 Sonny Sasaka
2020-07-13 20:14 ` [PATCH BlueZ 3/3] client: Add set-allow-internal-profiles command Sonny Sasaka
2020-07-13 20:35 ` [PATCH BlueZ 0/3] Per-device option to enable/disable internal profiles Luiz Augusto von Dentz
2020-07-13 22:04 ` Sonny Sasaka
2020-07-13 22:59 ` Luiz Augusto von Dentz
2020-07-13 23:48 ` Sonny Sasaka
2020-07-14 5:28 ` Luiz Augusto von Dentz
2020-07-14 20:55 ` Sonny Sasaka
2020-07-15 16:25 ` Luiz Augusto von Dentz
2020-07-15 20:13 ` Sonny Sasaka
2020-07-15 21:08 ` Luiz Augusto von Dentz
2020-07-15 22:29 ` Sonny Sasaka
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=20200713201441.235959-2-sonnysasaka@chromium.org \
--to=sonnysasaka@chromium.org \
--cc=alainm@chromium.org \
--cc=linux-bluetooth-@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.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.