---
doc/mgmt-api.txt | 95 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index 42e467fab261..3669604a806c 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -3138,6 +3138,84 @@ Read Security Information Command
Invalid Index
+Read Experimental Features Information Command
+==============================================
+
+ Command Code: 0x0049
+ Controller Index: <controller id>
+ Command Parameters:
+ Return Parameters: Feature_Count (2 Octets)
+ Feature1 {
+ UUID (16 Octets)
+ Flags (4 Octets)
+ }
+ Feature2 { }
+ ...
+
+ This command is used to retrieve the supported experimental features
+ by the host stack.
+
+ The UUID values are not defined here. They can change over time and
+ are on purpose not stable. Features that mature will be removed at
+ some point. The mapping of feature UUID to the actual functionality
+ of a given feature is out of scope here.
+
+ The following bits are defined for the Flags parameter:
+
+ 0 Feature active
+ 1 Change allowed during powered
+ 2 Causes change in supported settings
+
+ This command generates a Command Complete event on success or
+ a Command Status event on failure.
+
+ Possible errors: Invalid Parameters
+ Invalid Index
+
+
+Set Experimental Feature Command
+================================
+
+ Command Code: 0x004a
+ Controller Index: <controller id>
+ Command Paramters: UUID (16 Octets)
+ Action (1 Octet)
+ Return Parameters: Flags (4 Octets)
+
+ This command is used to change the setting of an experimental feature
+ of the host stack.
+
+ The UUID value must be a supported value returned from the Read
+ Experimental Features Information command.
+
+ The Action parameter is UUID specific, but in most cases it will be
+ just a simple on/off toggle with these values:
+
+ 0x00 Disable feature
+ 0x01 Enable feature
+
+ It depends on the feature if the command can be used when the
+ controller is powered up. See Flags parameter of Read Experimental
+ Features Information command for details if the controller has
+ to be powered down first.
+
+ The following bits are defined for the Flags return parameter:
+
+ 0 Feature active
+ 1 Allowed during powered
+ 2 Supported settings changed
+
+ When a feature causes the change of supported settings, then it is
+ a good idea to re-read the controller information.
+
+ This command generates a Command Complete event on success or
+ a Command Status event on failure.
+
+ Possible errors: Invalid Parameters
+ Not Powered
+ Invalid Index
+
+
Command Complete Event
======================
@@ -4021,3 +4099,20 @@ PHY Configuration Changed Event
one through which the change was triggered.
Refer Get PHY Configuration command for PHYs parameter.
+
+
+Experimental Feature Changed Event
+==================================
+
+ Event Code: 0x0027
+ Controller Index: <controller id>
+ Event Parameters: UUID (16 Octets)
+ Flags (4 Octets)
+
+ This event indicates that the status of an experimental feature
+ has been changed.
+
+ The event will only be sent to management sockets other than the
+ one through which the change was triggered.
+
+ Refer to Set Experimental Feature command for the Flags parameter.
--
2.26.2
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While we are preparing for reviewing the patches, we found the following
issue/warning.
Test Result:
Checkpatch Failed
Patch Title:
doc: Add commands and event for experimental feature configuration
Output:
WARNING:TYPO_SPELLING: 'Paramters' may be misspelled - perhaps 'Parameters'?
#56: FILE: doc/mgmt-api.txt:3181:
+ Command Paramters: UUID (16 Octets)
- total: 0 errors, 1 warnings, 104 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
Your patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
For more details about BlueZ coding style guide, please find it
in doc/coding-style.txt
---
Regards,
Linux Bluetooth