forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 143
ASoC: SOF: ipc4: Add support for generic bytes control to support notifications #5531
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
Merged
bardliao
merged 8 commits into
thesofproject:topic/sof-dev
from
ujfalusi:peter/sof/pr/ipc4-generic-bytes-control-01
Oct 2, 2025
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
0354583
ASoC: SOF: ipc4-control: If there is no data do not send bytes update
ujfalusi 91e7ba4
ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls
ujfalusi 49dccfd
ASoC: SOF: ipc4-control: Use the correct size for scontrol->ipc_contr…
ujfalusi bbbde78
ASoC: SOF: ipc4-control: Keep the payload size up to date
ujfalusi 63231d5
ASoC: SOF: ipc4-topology: Set initial param_id for bytes control type
ujfalusi b055a0c
ASoC: SOF: ipc4: Support for sending payload along with LARGE_CONFIG_GET
ujfalusi 0ddf3f0
ASoC: SOF: ipc4: Add definition for generic bytes control
ujfalusi 1b03a2d
ASoC: SOF: ipc4-control: Add support for generic bytes control
ujfalusi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Ok this took a while to parse, but I think this is correct. So without this patch, incorrect amount was copied as:
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.
yes, around those lines, we should copy what is available and yes, max_size is the payload's maximum, not the kernel internal buffer's size.
It is really confusing and took quite a while to unravel this for fixing.
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.
fwiw, the max_size was always bigger than the real data+header, so it was working OK, but it was incorrect at the same time.