-
Notifications
You must be signed in to change notification settings - Fork 349
topology2: add deepbuffer to nocodec #6508
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
Conversation
fe21cea to
533a9d3
Compare
533a9d3 to
5d59951
Compare
|
updated. Validated each tplg file and tested sdw on device. |
|
@RanderWang conflicts. |
2fe3c0b to
a5ff23b
Compare
|
@lgirdwood conflict was caused by chain dma. please first merge #6514. |
a5ff23b to
dcba930
Compare
|
@lgirdwood conflict fixed |
plbossart
left a comment
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.
mostly good but this needs serious polish to make it shiny clean
dcba930 to
9c88102
Compare
plbossart
left a comment
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'd like the deep-buffer size to be configurable per product. There's no good reason to force everyone to use 100ms upfront.
|
Actually rebase necessary @RanderWang, looks like there are conflicts? We should also check why we have two TIMEOUTS on 2 out of 3 nocodec test devices. it's a troubling coincidence, isn't it? |
|
SOFCI TEST |
|
@lgirdwood all ipc4 test pass now |
plbossart
left a comment
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.
Let's try to use the same indices for PCMs so that the external view of the topology remains the same.
62e1d68 to
912177e
Compare
|
update deep buffer pcm index to 31 according to topology1 |
|
except that we didn't follow the convention for all cases in topology1. We should probably update this for compatibility, it has no impact on UCM/users since it's a developer-only config. Can you do this with a follow-up patch @RanderWang ? |
plbossart
left a comment
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.
this looks good but two issues to be aware of before merging @lgirdwood
a) this will conflict with @ranj063 cleanup patch #6592
b) adding a 100ms buffer in the firmware is likely to expose some issues, I would run a daily test on this PR to avoid breaking CI too much.
|
@mengdonglin can we schedule a daily test for this PR as requested by @plbossart ? (can be next week, we can merge the cleanup #6592 first) |
|
@RanderWang good for rebase now |
e023252 to
decfc9c
Compare
|
@RanderWang let us know the results of the daily test with this PR |
sure, I sent the status to you |
|
@RanderWang @ranj063 pls let me know when ready to merge. |
|
@RanderWang conflicts |
It will be shared by I2S, HDA and SDW platforms Signed-off-by: Rander Wang <rander.wang@intel.com>
Deep buffer is mixed with ssp0 stream. Signed-off-by: Rander Wang <rander.wang@intel.com>
Deep buffer is mixed with Jack out. Signed-off-by: Rander Wang <rander.wang@intel.com>
Deep buffer is mixed with HDA analog. Signed-off-by: Rander Wang <rander.wang@intel.com>
decfc9c to
a0a365a
Compare
|
@lgirdwood updated. Now it passes all ipc4 test on TGL, but some cases are failed on MTL for power management issue |
|
Could this PR cause this recent TGL IPC4 regression? It's the only significant PR that was merged recently. |
|
I triggered a test plan in ci 18496, check-kmod-load-unload-after-playback passed. Maybe it can result to this bug but it should be in low rate. It will enabled D0i3 if only deepbuffer stream is working. |
|
it's a fairly high rate: |
No description provided.