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

LE Audio: PACS: Server change location #42343

Closed
Thalley opened this issue Feb 1, 2022 · 0 comments · Fixed by #42593
Closed

LE Audio: PACS: Server change location #42343

Thalley opened this issue Feb 1, 2022 · 0 comments · Fixed by #42593
Assignees
Labels
area: API Changes to public APIs area: Bluetooth Audio area: Bluetooth Enhancement Changes/Updates/Additions to existing features

Comments

@Thalley
Copy link
Collaborator

Thalley commented Feb 1, 2022

Is your enhancement proposal related to a problem? Please describe.
The PACS location values are currently just Kconfig options, but as the capabilities can change, so can the location.

Describe the solution you'd like
The location should be writable by the PACS server. One way of doing that is to retrieve the location value from the application, similar to how PAC records are, instead of storing it in the service implementation.

Describe alternatives you've considered
Could also keep the location in the service implementation and provide a function to write it.

Additional context
N/A

@Thalley Thalley added Enhancement Changes/Updates/Additions to existing features area: Bluetooth Audio labels Feb 1, 2022
@Thalley Thalley self-assigned this Feb 1, 2022
@Thalley Thalley added area: API Changes to public APIs area: Bluetooth labels Feb 16, 2022
@carlescufi carlescufi moved this to Done in Bluetooth LE Audio May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: API Changes to public APIs area: Bluetooth Audio area: Bluetooth Enhancement Changes/Updates/Additions to existing features
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant