-
Notifications
You must be signed in to change notification settings - Fork 349
[RFC] Topology for synchronize playback #2542
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
[RFC] Topology for synchronize playback #2542
Conversation
lgirdwood
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.
Needs more comments.
tools/topology/m4/dai.m4
Outdated
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.
Can you add some comments here on usage and what its for.
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.
can we rename this to pipe-dai-playback.m4
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.
can we rename this to pipe-dai-playback.m4
There is another pipe-dai-playback.m4 in the same folder already.
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.
pipe-dai-endpoint
aacf770 to
70b0a19
Compare
So we can set scheduling component when adding a DAI. Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
70b0a19 to
f3342c0
Compare
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 comment is wrong
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.
besides this is hardly a pipeline with the SectionGraph defined elsewhere. All you have is a buffer?
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.
besides this is hardly a pipeline with the SectionGraph defined elsewhere. All you have is a buffer?
I will have a buffer with a pipeline id which is required for connecting to a demux.
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.
is this needed if you're not using the N_DAI_OUT here?
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.
is this needed if you're not using the N_DAI_OUT here?
Yeah, we don't need it. Thanks @ranj063
This is basically the same as pipe-dai-playback.m4, but use SCHED_COMP instead of N_DAI_OUT. Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
This will create a basic pipeline with a buffer only. Note that we don't implement a SectionGraph to connect the buffer to its starting component, we should define it manually. Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
Now kernel expots one PCM with two CPU dais. So use demux to play with two DAIs. Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
f3342c0 to
e1ec084
Compare
The PR is to implement a topology for synchronize playback. We use demux to duplicate audio data for two DAIs.