-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Bluetooth: Separate ISO from AUDIO and HCI HOST only #31182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -222,6 +222,65 @@ config BT_DATA_LEN_UPDATE | |
| Enable support for Bluetooth v4.2 LE Data Length Update procedure. | ||
| endif # BT_CONN | ||
|
|
||
|
|
||
| config BT_ISO | ||
| bool "Bluetooth Isochronous Channel Support [EXPERIMENTAL]" | ||
| depends on BT_CONN | ||
| help | ||
| Select this to enable Isochronous Channel support. | ||
|
|
||
| if BT_ISO | ||
|
|
||
| config BT_ISO_MAX_CHAN | ||
| int "Maximum number of simultaneous ISO channels" | ||
| depends on BT_ISO | ||
| default BT_MAX_CONN | ||
| range 1 64 | ||
| help | ||
| Maximum number of simultaneous Bluetooth isochronous channels | ||
| supported. | ||
|
|
||
| config BT_ISO_TX_BUF_COUNT | ||
| int "Number of Isochronous TX buffers" | ||
|
||
| default 1 | ||
| range 1 255 | ||
| help | ||
| Number of buffers available for outgoing Isochronous channel SDUs. | ||
|
|
||
| config BT_ISO_TX_FRAG_COUNT | ||
| int "Number of ISO TX fragment buffers" | ||
|
||
| default 2 | ||
| range 0 255 | ||
| help | ||
| Number of buffers available for fragments of TX buffers. Warning: | ||
| setting this to 0 means that the application must ensure that | ||
| queued TX buffers never need to be fragmented, i.e. that the | ||
| controller's buffer size is large enough. If this is not ensured, | ||
| and there are no dedicated fragment buffers, a deadlock may occur. | ||
| In most cases the default value of 2 is a safe bet. | ||
|
|
||
| config BT_ISO_TX_MTU | ||
| int "Maximum supported MTU for Isochronous TX buffers" | ||
|
||
| default 251 | ||
| range 23 4095 | ||
| help | ||
| Maximum MTU for Isochronous channels TX buffers. | ||
|
|
||
| config BT_ISO_RX_BUF_COUNT | ||
| int "Number of Isochronous RX buffers" | ||
| default 1 | ||
| range 1 255 | ||
| help | ||
| Number of buffers available for incoming Isochronous channel SDUs. | ||
|
|
||
| config BT_ISO_RX_MTU | ||
| int "Maximum supported MTU for Isochronous RX buffers" | ||
| default 251 | ||
| range 23 4095 | ||
| help | ||
| Maximum MTU for Isochronous channels RX buffers. | ||
| endif # BT_ISO | ||
|
|
||
| # Workaround for not being able to have commas in macro arguments | ||
| DT_CHOSEN_Z_BT_C2H_UART := zephyr,bt-c2h-uart | ||
|
|
||
|
|
||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we will need to revisit this once there is more "meat" on the controller. For the controller it is more natural to model CISes/CIGs/BISes/BIGs than individual channels. But it looks reasonable enough for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. For the host, it doesn't matter if the ISO channel is for a BIS or a CIS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw., in a discussion with @asmk-ot it came up that this is actually useful as it is for the ISOAL in the controller