Hi Daniel, >>> This patch adds the following to mgmt-api: >>> - Add Extended Advertising Parameters Command >>> - Add Extended Advertising Data Command >>> - Changes Read Security Info to Read Controller Capabilities CMD >>> >>> Reviewed-by: Sonny Sasaka <sonnysasaka@xxxxxxxxxxxx> >>> Reviewed-by: Alain Michaud <alainm@xxxxxxxxxxxx> >>> --- >>> >>> Changes in v3: >>> - Removed Tx Power Selected MGMT event >>> - Changed Read Security Info cmd to Read Controller Capabilities >>> >>> Changes in v2: >>> - Removed extra space in Add Extended Advertising Parameters API >>> >>> doc/mgmt-api.txt | 229 +++++++++++++++++++++++++++++++++++++++++++++-- >>> 1 file changed, 223 insertions(+), 6 deletions(-) >>> >>> diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt >>> index ca0d38469..85aa8b797 100644 >>> --- a/doc/mgmt-api.txt >>> +++ b/doc/mgmt-api.txt >>> @@ -3110,19 +3110,19 @@ Set Wideband Speech Command >>> Invalid Index >>> >>> >>> -Read Security Information Command >>> +Read Controller Capabilities Command >>> ================================= >> >> I am fine with the name. Just extend the === to match the text above. >> >>> >>> Command Code: 0x0048 >>> Controller Index: <controller id> >>> Command Parameters: >>> - Return Parameters: Security_Data_Length (2 Octets) >>> - Security_Data (0-65535 Octets) >>> + Return Parameters: Capabilities_Data_Length (2 Octets) >>> + Capabilities_Data (0-65535 Octets) >>> >>> - This command is used to retrieve the supported security features >>> + This command is used to retrieve the supported capabilities >>> by the controller or the host stack. >>> >>> - The Security_Data_Length and Security_Data parameters provide >>> + The Capabilities_Data_Length and Capabilities_Data parameters provide >>> a list of security settings, features and information. It uses >>> the same format as EIR_Data, but with the namespace defined here. >>> >>> @@ -3131,6 +3131,8 @@ Read Security Information Command >>> 0x01 Flags >>> 0x02 Max Encryption Key Size (BR/EDR) >>> 0x03 Max Encryption Key Size (LE) >>> + 0x04 Min Supported LE Tx Power (dBm) >>> + 0x05 Max Supported LE Tx Power (dBm) >> >> I would actually prefer if we put them into a 2 octet size value. So two times s8 fields. And then just call it "Supported Tx Power (LE)”. >> >>> >>> Flags (data type 0x01) >>> >>> @@ -3146,6 +3148,15 @@ Read Security Information Command >>> present, then it is unknown what the max encryption key >>> size of the controller or host is in use. >>> >>> + Min/Max Supported LE Tx Power (data types 0x04 and 0x05) >>> + >>> + These fields indicate the supported range of LE Tx Power in >>> + dBm across all supported PHYs. These values are populated >>> + by the return of the LE Read Transmit Power HCI command. If >>> + this HCI command is not available, the values default to >>> + 0x7F, indicating HCI_TX_POWER_INVALID, as a valid range >>> + is not available. >>> + >> >> Actually no. If the command is not available or failed, then this field will not be present. Clearly indicate the absence. The should be a clear difference if the command is not available and the controller returning -127. >> >> Can we split this change into a separate patch please. >> >>> This command generates a Command Complete event on success or >>> a Command Status event on failure. >>> >>> @@ -3574,6 +3585,212 @@ Remove Advertisement Monitor Command >>> Busy >>> >>> >>> +Add Extended Advertising Parameters Command >>> +=========================================== >>> + >>> + Command Code: 0x0054 >>> + Controller Index: <controller id> >>> + Command Parameters: Instance (1 Octet) >>> + Flags (4 Octets) >>> + Params (2 Octets) >>> + Duration (2 Octets) >>> + Timeout (2 Octets) >>> + MinInterval (4 Octets) >>> + MaxInterval (4 Octets) >>> + TxPower (1 Octet) >>> + Return Parameters: Instance (1 Octet) >>> + TxPower (1 Octet) >> >> If we leave the Flags that tell what adv data and scan rsp data to add, then we should also return the leftover sizes of each fields so that the caller knows how much they can occupy. So that you don’t have to use Get Advertising Size Information command to get that information. We already know it at this point in time. > > Hi Marcel, I am happy to add the remaining space available for > advertising and scan response data to the response here. However, > userspace already has a local function, > advertising.c:calc_max_adv_len(), that computes the losses caused by > these flags. I imagine that this feature will be useful for any other > application not using userspace bluez so I will add it to the > response, but at the moment userspace does not need it. Please let me > know if you have any further thoughts on this point. I prefer that userspace does not have to guess or we have to keep kernel implementation in sync with usersapce. So if we tell userspace just what space it has available, that is cleaner. Regards Marcel
