Skip to content

ACP stack improvements and add SoundWire IO support for ACP7.0 & ACP7.1 platforms#5392

Closed
vijendarmukunda wants to merge 9 commits intothesofproject:topic/sof-devfrom
vijendarmukunda:topic/sof-dev
Closed

ACP stack improvements and add SoundWire IO support for ACP7.0 & ACP7.1 platforms#5392
vijendarmukunda wants to merge 9 commits intothesofproject:topic/sof-devfrom
vijendarmukunda:topic/sof-dev

Conversation

@vijendarmukunda
Copy link
Copy Markdown

This patch series contains

  • ACP sof stack improvements
  • Add support for ACP7.1 platform.
  • Soundwire IO support for ACP7.0 & ACP7.1 platforms

@vijendarmukunda
Copy link
Copy Markdown
Author

@bardliao @ranj063 @plbossart Could you please help to review the patches?

Copy link
Copy Markdown
Collaborator

@ranj063 ranj063 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good except for a couple of nits @vijendarmukunda

Else condition is not required after break/return statement.
Remove else condition in resume callback.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Add missing acp descriptor field acp_error_stat for ACP7.0 platform.

Fixes: 490be7b ("ASoC: SOF: amd: add support for acp7.0 based platform")

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Add SOF support for ACP7.1 platform.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Update SoundWire specific acp descriptor structure fields for
ACP7.0 & ACP7.1 platforms.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
As per design flow for ACP7.0 & ACP7.1 platforms, enable ACP_PME_EN
register for below scenarios.
1. During acp init sequence
2. During resume sequence for SoundWire ClockStop power mode.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Below mentioned register sequence should be part of acp init
sequence.
1) Set ACP clock mux selection register to ACP_ACLK clock
source.
2) Enable ACP global interrupt enable register
3) Enable ACP error interrupt mask.
ACP reset sequence should contain code related to asserting
acp soft reset and release the soft reset.
Move the rest of the registers programming to acp init sequence.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Enable SoundWire host wake interrupt mask during acp init
sequence based on wake enable checks for each SoundWire manager
instance for ACP7.0 & ACP7.1 platforms.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Add SoundWire wake interrupt handling for ACP7.0 & ACP7.1
platforms.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Add build support for SoundWire for ACP7.0/ACP7.1 platforms.

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
@vijendarmukunda
Copy link
Copy Markdown
Author

@ranj063 : If you don't have further review comments, Could you please approve the PR?

@ranj063
Copy link
Copy Markdown
Collaborator

ranj063 commented May 1, 2025

@ranj063 : If you don't have further review comments, Could you please approve the PR?

done @vijendarmukunda. Will you take care of sending it upstream?

@vijendarmukunda
Copy link
Copy Markdown
Author

vijendarmukunda commented May 1, 2025

@ranj063 : If you don't have further review comments, Could you please approve the PR?

done @vijendarmukunda. Will you take care of sending it upstream?

@ranj063 Once this PR gets merged. I will send the patch series to mailing list. Does anything got changed in the work flow?

@ranj063
Copy link
Copy Markdown
Collaborator

ranj063 commented May 1, 2025

@ranj063 : If you don't have further review comments, Could you please approve the PR?

done @vijendarmukunda. Will you take care of sending it upstream?

@ranj063 Once this PR gets merged. I will send the patch series to mailing list. Does anything got changed in the work flow?

@bardliao how do you want to handle this?

@vijendarmukunda
Copy link
Copy Markdown
Author

vijendarmukunda commented May 1, 2025

@ranj063 : If you don't have further review comments, Could you please approve the PR?

done @vijendarmukunda. Will you take care of sending it upstream?

@ranj063 Once this PR gets merged. I will send the patch series to mailing list. Does anything got changed in the work flow?

@bardliao how do you want to handle this?

@bardliao : Once the PR gets merged, If patches upstream taken care automatically. Then its fine. I won't send patch series to mailing list explicitly.

@bardliao
Copy link
Copy Markdown
Collaborator

bardliao commented May 2, 2025

@vijendarmukunda Please post them to the mailing list with our Reviewed-by tag. I will close the PR and get the commits from ASoC tree.

@bardliao bardliao closed this May 2, 2025
@vijendarmukunda
Copy link
Copy Markdown
Author

vijendarmukunda commented May 2, 2025

@vijendarmukunda Please post them to the mailing list with our Reviewed-by tag. I will close the PR and get the commits from ASoC tree.

Is it new process? is it applicable to all the Pull requests on SOF Linux?
This will create a problem for us. Assume that on top of any PR changes which is not merged in SOF github and available in Mark Brown's tree, if we want to create any new pull request in SOF linux, we need to wait till next merge windows for SOF github branch which gets rebased with Mark Brown's asoc tree.

@bardliao
Copy link
Copy Markdown
Collaborator

bardliao commented May 2, 2025

@vijendarmukunda Please post them to the mailing list with our Reviewed-by tag. I will close the PR and get the commits from ASoC tree.

Is it new process? is it applicable to all the Pull requests on SOF Linux?

@vijendarmukunda
No, it depends. In this case, all changes are in the sound/soc/sof/amd folder. And it can apply to Mark Brown's asoc tree. That's why I think it may be better to let you submit the patches. Like you are the maintainer of sof/amd.

This will create a problem for us. Assume that on top of any PR changes which is not merged in SOF github and available in Mark Brown's tree, if we want to create any new pull request in SOF linux, we need to wait till SOF github branch gets rebased with Mark Brown's asoc tree.

Good point. We are willing to submit all SOF patches. The point is that if it is merged to our repo, please let us submit the series. Otherwise, it may cause conflict when we do upstream merge. What do you think? Do you want us to merge this PR and submit the series to ASoC?

@bardliao bardliao reopened this May 2, 2025
@vijendarmukunda
Copy link
Copy Markdown
Author

@vijendarmukunda Please post them to the mailing list with our Reviewed-by tag. I will close the PR and get the commits from ASoC tree.

Is it new process? is it applicable to all the Pull requests on SOF Linux?

@vijendarmukunda No, it depends. In this case, all changes are in the sound/soc/sof/amd folder. And it can apply to Mark Brown's asoc tree. That's why I think it may be better to let you submit the patches. Like you are the maintainer of sof/amd.

This will create a problem for us. Assume that on top of any PR changes which is not merged in SOF github and available in Mark Brown's tree, if we want to create any new pull request in SOF linux, we need to wait till SOF github branch gets rebased with Mark Brown's asoc tree.

Good point. We are willing to submit all SOF patches. The point is that if it is merged to our repo, please let us submit the series. Otherwise, it may cause conflict when we do upstream merge. What do you think? Do you want us to merge this PR and submit the series to ASoC?

It make sense. we can decide based on case to case. Thanks We will push the patches to mailing list.

@bardliao
Copy link
Copy Markdown
Collaborator

bardliao commented May 2, 2025

@vijendarmukunda Please post them to the mailing list with our Reviewed-by tag. I will close the PR and get the commits from ASoC tree.

Is it new process? is it applicable to all the Pull requests on SOF Linux?

@vijendarmukunda No, it depends. In this case, all changes are in the sound/soc/sof/amd folder. And it can apply to Mark Brown's asoc tree. That's why I think it may be better to let you submit the patches. Like you are the maintainer of sof/amd.

This will create a problem for us. Assume that on top of any PR changes which is not merged in SOF github and available in Mark Brown's tree, if we want to create any new pull request in SOF linux, we need to wait till SOF github branch gets rebased with Mark Brown's asoc tree.

Good point. We are willing to submit all SOF patches. The point is that if it is merged to our repo, please let us submit the series. Otherwise, it may cause conflict when we do upstream merge. What do you think? Do you want us to merge this PR and submit the series to ASoC?

It make sense. we can decide based on case to case. Thanks We will push the patches to mailing list.

Ok, then I will close the PR. :)

@bardliao bardliao closed this May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants