Skip to content
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

Bluetooth: CCP: Add support for set/get provider name #79324

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Thalley
Copy link
Collaborator

@Thalley Thalley commented Oct 2, 2024

Add support for setting and getting the bearer provider
name. For now the name will be duplicated by the TBS
implementation, but will be optimizied in the future
so only one copy of the name exists.

@Thalley Thalley force-pushed the ccp_server_name branch 12 times, most recently from a3736c9 to 45c90ee Compare October 9, 2024 15:10
@Thalley Thalley force-pushed the ccp_server_name branch 2 times, most recently from 32eb534 to cd67949 Compare November 12, 2024 10:55
@Thalley Thalley force-pushed the ccp_server_name branch 3 times, most recently from bb73153 to 8daccea Compare November 22, 2024 21:10
@Thalley Thalley self-assigned this Nov 26, 2024
The CCP API for the Call Control Profile works on top of the
TBS API, and will eventually replace parts of the TBS API.

Signed-off-by: Emil Gydesen <[email protected]>
Added initial CCP client implementation that simply
does discovery of TBS on a remote CCP server.

Signed-off-by: Emil Gydesen <[email protected]>
Add support for setting and getting the bearer provider
name. For now the name will be duplicated by the TBS
implementation, but will be optimizied in the future
so only one copy of the name exists.

Signed-off-by: Emil Gydesen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant