Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content
Commit 3edeca84 authored by En-Shuo Hsu's avatar En-Shuo Hsu Committed by En-Shuo Hsu
Browse files

floss: Add non-offload esco params

Currently, we rely on a compile time defined constant to determine which
data path to use for SCO.

The define statement is at system/stack/btm/btm_sco.h as

 #ifndef ESCO_DATA_PATH
 #ifdef OS_ANDROID
 #define ESCO_DATA_PATH ESCO_DATA_PATH_PCM
 #else
 #define ESCO_DATA_PATH ESCO_DATA_PATH_HCI
 #endif
 #endif

We later use the defined path in btm_sco.cc when setting up the SCO
connection by overriding the esco parameter as:
p_setup->input_data_path = p_setup->output_data_path = ESCO_DATA_PATH;

We have this implementation as there was no requirement for the stack to
support the data path configuration on running time. Also, there was no
corresponding codes for the non-offload path.

Adding an optional argument to get esco parameters for non-offload path.
This also prepares us to refine the existing implementation by removing
the definition of ESCO_DATA_PATH.

Bug: 225055249
Tag: #floss
Test: emerge-zork floss
Change-Id: I89ebbc7aea965606cad52d728d8badde334d7cbb
parent 27da261f
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment