-
Notifications
You must be signed in to change notification settings - Fork 142
ASoC: SOF: ipc4-topology/Intel: hda-pcm: Fix ChainDMA host buffer time and move constraint to period time #5540
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 |
|---|---|---|
|
|
@@ -70,8 +70,11 @@ | |
| #define SOF_IPC4_CHAIN_DMA_NODE_ID 0x7fffffff | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Minor nit in commit message: the firmware change was for a particular Intel platforms. But yeah, in practise it covers all platforms covered by this ipc4 kernel code at the moment.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the fw change was for all IPC4 platforms (all Intel platforms which can run IPC4), it is fair to say that for IPC4 the host buffer size has been 4ms and not 2ms.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, that is true, but it's just hard to verify this looking at the commit and then looking at the FW commit. Reader has to have outside information that Intel ACE variant happens to be the only IPC4 supporting platform and the various other platforms in SOF (with 2ms default) are never used in IPC4 mode.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. CAVS2.5 works (but not officially supported) with IPC4 and that also uses 4ms host buffer. At this time IPC4 as such uses 4ms host buffer on all supported platforms. Yes, we will have support for this information to be queried from firmware and can get rid of this define, but as far as IPC4 concerns, we have been mistakenly assumed 2ms host buffer when in fact IPC4 is using 4ms. |
||
| #define SOF_IPC4_INVALID_NODE_ID 0xffffffff | ||
|
|
||
| /* FW requires minimum 2ms DMA buffer size */ | ||
| #define SOF_IPC4_MIN_DMA_BUFFER_SIZE 2 | ||
| /* FW requires minimum 4ms DMA buffer size */ | ||
| #define SOF_IPC4_MIN_DMA_BUFFER_SIZE 4 | ||
ranj063 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| /* ChainDMA in fw uses 5ms DMA buffer */ | ||
| #define SOF_IPC4_CHAIN_DMA_BUFFER_SIZE 5 | ||
|
|
||
| /* | ||
| * The base of multi-gateways. Multi-gateways addressing starts from | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.