Channel direction was actually a source of confusion since the spec does actually define the data path direction from controller point of view meaning input actually means transmit and output receive, also direction can be configured with different QoS settings. To make these APIs less confusing and allow QoS to be configured independently they are now split into RX (receiving) and TX (transmission) settings including its data path. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> |
||
|---|---|---|
| .. | ||
| bredr.c | ||
| bt.c | ||
| bt.h | ||
| CMakeLists.txt | ||
| gatt.c | ||
| hci.c | ||
| hci.h | ||
| iso.c | ||
| Kconfig | ||
| l2cap.c | ||
| ll.c | ||
| ll.h | ||
| rfcomm.c | ||
| ticker.c | ||