diff mbox series

[BlueZ,1/3] doc: Add "AllowInternalProfiles" property to org.bluez.Device1

Message ID 20200713201441.235959-2-sonnysasaka@chromium.org (mailing list archive)
State Rejected
Headers show
Series Per-device option to enable/disable internal profiles | expand

Commit Message

Sonny Sasaka July 13, 2020, 8:14 p.m. UTC
Reviewed-by: Alain Michaud <alainm@chromium.org>

---
 doc/device-api.txt | 13 +++++++++++++
 1 file changed, 13 insertions(+)
diff mbox series

Patch

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