Repository navigation
Fix deep buffer playback pipelines for cavs - #4534
Conversation
|
fixes #4526 |
plbossart
left a comment
plbossart
left a comment
There was a problem hiding this comment.
Wondering if we can simplify by keeping the structure identical instead of special casing.
There was a problem hiding this comment.
why special-case? it'd be fine to use a mixer on all 3 dai pipelines, and only connect a second host pipeline for one of the mixers.
That way all 3 playback path have the same latency/processing/settings.
There was a problem hiding this comment.
that would also make the pipeline management less complicated with fewer options.
There was a problem hiding this comment.
@plbossart fixed now. here's how the tplg's look now
APL:
Rest:
There was a problem hiding this comment.
just what the doctor ordered. Thanks Ranjani.
…based pipelines Convert all playback pipelines to have a mixer so adding a deep-buffer pipeline will be simpler. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
on SSP5 for BXT and SSP0 for all others. Signed-off-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
319952a to
c4af135
Compare
Yes, will do! |
3 participants
APL cannot support 2 deep buffer playback PCM's. So fix this by adding only 1deep buffer playback PCM on SSP5 for APL and SSP0 for the rest