2023-03-31 05:28:57

by Saba Kareem, Syed

[permalink] [raw]
Subject: [PATCH] ASoC: amd: ps: update the acp clock source.

Updating the clock source from ACLK to default clock

Signed-off-by: Syed Saba Kareem <[email protected]>
---
sound/soc/amd/ps/pci-ps.c | 2 --
1 file changed, 2 deletions(-)

diff --git a/sound/soc/amd/ps/pci-ps.c b/sound/soc/amd/ps/pci-ps.c
index e86f23d97584..688a1d4643d9 100644
--- a/sound/soc/amd/ps/pci-ps.c
+++ b/sound/soc/amd/ps/pci-ps.c
@@ -91,7 +91,6 @@ static int acp63_init(void __iomem *acp_base, struct device *dev)
dev_err(dev, "ACP reset failed\n");
return ret;
}
- acp63_writel(0x03, acp_base + ACP_CLKMUX_SEL);
acp63_enable_interrupts(acp_base);
return 0;
}
@@ -106,7 +105,6 @@ static int acp63_deinit(void __iomem *acp_base, struct device *dev)
dev_err(dev, "ACP reset failed\n");
return ret;
}
- acp63_writel(0, acp_base + ACP_CLKMUX_SEL);
acp63_writel(0, acp_base + ACP_CONTROL);
return 0;
}
--
2.25.1


2023-03-31 16:18:43

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] ASoC: amd: ps: update the acp clock source.

On Fri, 31 Mar 2023 10:50:23 +0530, Syed Saba Kareem wrote:
> Updating the clock source from ACLK to default clock
>
>

Applied to

broonie/sound.git for-next

Thanks!

[1/1] ASoC: amd: ps: update the acp clock source.
commit: a4d432e9132c0b29d857b09ca2ec4c1f455b5948

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark