Bluetooth: controller: Avoid the use of weak functions for ISO data path
Avoid the use of weak functions and call the respective functions only if vendor-specific data path is supported. The weak dummy functions will not implement the desired behavior anyway. This change makes it explicit that these functions need to be implemented by the vendor. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com>
This commit is contained in:
parent
f7cf252a8c
commit
b525db221c
7 changed files with 51 additions and 69 deletions
|
@ -640,10 +640,14 @@ static void configure_data_path(struct net_buf *buf,
|
|||
|
||||
vs_config = &cmd->vs_config[0];
|
||||
|
||||
status = ll_configure_data_path(cmd->data_path_dir,
|
||||
cmd->data_path_id,
|
||||
cmd->vs_config_len,
|
||||
vs_config);
|
||||
if (IS_ENABLED(CONFIG_BT_CTLR_ISO_VENDOR_DATA_PATH)) {
|
||||
status = ll_configure_data_path(cmd->data_path_dir,
|
||||
cmd->data_path_id,
|
||||
cmd->vs_config_len,
|
||||
vs_config);
|
||||
} else {
|
||||
status = BT_HCI_ERR_INVALID_PARAM;
|
||||
}
|
||||
|
||||
rp = hci_cmd_complete(evt, sizeof(*rp));
|
||||
rp->status = status;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue