 |
nrfxlib API 2.7.99
|
|
nrfxlib API 2.7.99
|
| uint8_t sdc_hci_cmd_le_setup_iso_data_path | ( | const sdc_hci_cmd_le_setup_iso_data_path_t * | p_params, |
| sdc_hci_cmd_le_setup_iso_data_path_return_t * | p_return | ||
| ) |
#include <softdevice_controller/include/sdc_hci_cmd_le.h>
LE Setup ISO Data Path.
The description below is extracted from Core_v5.4, Vol 4, Part E, Section 7.8.109
The HCI_LE_Setup_ISO_Data_Path command is used to identify and create the isochronous data path between the Host and the Controller for a CIS, CIS configuration, or BIS identified by the Connection_Handle parameter. This command can also be used to configure a codec for each data path. When a connection is created no data paths are set up for that connection.
The input and output directions are defined from the perspective of the Controller, so "input" refers to data flowing from the Host to the Controller.
If the Host issues this command more than once for the same Connection_- Handle and direction before issuing the HCI_LE_Remove_ISO_Data_Path command for that Connection_Handle and direction, the Controller shall return the error code Command Disallowed (0x0C).
If the Host issues this command for a CIS on a Peripheral before it has issued the HCI_LE_Accept_CIS_Request command for that CIS, then the Controller shall return the error code Command Disallowed (0x0C).
The Data_Path_Direction parameter specifies the direction for which the data path is being configured.
The Data_Path_ID parameter specifies the data transport path used. When set to 0x00, the data path shall be over the HCI transport. When set to a value in the range 0x01 to 0xFE, the data path shall use a vendor-specific transport interface (e.g., a PCM interface) with logical transport numbers. The meanings of these logical transport numbers are vendor-specific.
If the Host issues this command for a vendor-specific data transport path that has not been configured, the Controller shall return the error code Command Disallowed (0x0C).
If the Host attempts to set a data path with a Connection Handle that does not exist or that is not for a CIS, CIS configuration, or BIS, the Controller shall return the error code Unknown Connection Identifier (0x02). If the Host attempts to set an output data path using a connection handle that is for an Isochronous Broadcaster, for an input data path on a Synchronized Receiver, or for a data path for the direction on a unidirectional CIS where BN is set to 0, the Controller shall return the error code Command Disallowed (0x0C).
The Codec_ID parameter specifies the coding format used over the air.
When Data_Path_Direction is set to 0x00 (input), the Controller_Delay param- eter specifies the delay at the data source from the reference time of an SDU to the CIG reference point (see [Vol 6] Part B, Section 4.5.14.1) or BIG anchor point (see [Vol 6] Part B, Section 4.4.6.4). When Data_Path_Direction is set to 0x01 (output), Controller_Delay specifies the delay from the SDU_Synchronization_Reference to the point in time at which the Controller begins to transfer the corresponding data to the data path interface. The Host should use the HCI_Read_Local_Supported_Controller_Delay command to obtain a suitable value for Controller_Delay.
Note: Controller vendors may provide additional guidance to the Host on how to select a suitable Controller_Delay value from the range of values provided by the HCI_Read_Local_Supported_Controller_Delay command for various configurations of the data path interface.
The Codec_Configuration parameter specifies codec-specific configuration information for the specified direction.
If the Host issues this command with Codec_Configuration_Length non-zero and Codec_ID set to transparent air mode, the Controller shall return the error code Invalid HCI Command Parameters (0x12).
If the Host issues this command with codec-related parameters that exceed the bandwidth and latency allowed on the established CIS or BIS identified by the Connection_Handle parameter, the Controller shall return the error code Invalid HCI Command Parameters (0x12).
Event(s) generated (unless masked away): When the HCI_LE_Setup_ISO_Data_Path command has completed, an HCI_Command_Complete event shall be generated.
| [in] | p_params | Input parameters. |
| [out] | p_return | Extra return parameters. |
| 0 | if success. |
1.9.6