[PATCH] ASoc: adi: Kconfig: Remove depends on for ADI reference designs
From: Bogdan Togorean bogdan.togorean@analog.com
Audio ADI reference designs are also used on some ZynqMP boards, and can also be used on Intel FPGA boards and also on some more complex FPGA combinations (FPGA cards connected through PCIe).
This change removes the dependency on Microblaze and Zynq architectures to allow the usage of this driver for the systems described above.
Signed-off-by: Bogdan Togorean bogdan.togorean@analog.com Signed-off-by: Alexandru Ardelean alexandru.ardelean@analog.com --- sound/soc/adi/Kconfig | 1 - 1 file changed, 1 deletion(-)
diff --git a/sound/soc/adi/Kconfig b/sound/soc/adi/Kconfig index e321e3b672da..0236dc5b4e9f 100644 --- a/sound/soc/adi/Kconfig +++ b/sound/soc/adi/Kconfig @@ -1,7 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only config SND_SOC_ADI tristate "Audio support for Analog Devices reference designs" - depends on MICROBLAZE || ARCH_ZYNQ || COMPILE_TEST help Audio support for various reference designs by Analog Devices.
On Tue, 10 Nov 2020 17:22:13 +0200, Alexandru Ardelean wrote:
Audio ADI reference designs are also used on some ZynqMP boards, and can also be used on Intel FPGA boards and also on some more complex FPGA combinations (FPGA cards connected through PCIe).
This change removes the dependency on Microblaze and Zynq architectures to allow the usage of this driver for the systems described above.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoc: adi: Kconfig: Remove depends on for ADI reference designs commit: e1ade4c55ae3559b082faf9f5207cc6caba1c546
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
participants (2)
-
Alexandru Ardelean -
Mark Brown