From: Max Kellermann <max.kellermann@gmail.com>
To: heiko@sntech.de, linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, bardliao@realtek.com,
oder_chiou@realtek.com, Max Kellermann <max.kellermann@gmail.com>
Subject: [PATCH] sound/soc/rockchip: add RT5640 codec option
Date: Wed, 28 Nov 2018 08:28:52 +0100 [thread overview]
Message-ID: <20181128072852.32760-1-max.kellermann@gmail.com> (raw)
The Firefly-RK3399 DeviceTree
(`arch/arm64/boot/dts/rockchip/rk3399-firefly.dts`) defines a
`simple-audio-card` device which selects a `realtek,rt5640` codec.
This codec however is inaccessible in the kernel configuration
(`SND_SOC_RT5640`) and thus cannot be used.
This patch adds a new configuration option named
`SND_SOC_ROCKCHIP_RT5640` which selects `SND_SOC_RT5640` and
`SND_SIMPLE_CARD`, but does nothing else.
It enables `SND_SIMPLE_CARD`, because that's what the Firefly has.
I'm not sure if there are Rockchip products which need a different
sound card driver with RT5640.
Signed-off-by: Max Kellermann <max.kellermann@gmail.com>
---
sound/soc/rockchip/Kconfig | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/sound/soc/rockchip/Kconfig b/sound/soc/rockchip/Kconfig
index 957046ac6c8c..ac2e27043107 100644
--- a/sound/soc/rockchip/Kconfig
+++ b/sound/soc/rockchip/Kconfig
@@ -42,6 +42,16 @@ config SND_SOC_ROCKCHIP_MAX98090
Say Y or M here if you want to add support for SoC audio on Rockchip
boards using the MAX98090 codec, such as Veyron.
+config SND_SOC_ROCKCHIP_RT5640
+ tristate "ASoC support for Rockchip boards using a RT5640 codec"
+ depends on SND_SOC_ROCKCHIP
+ select SND_SOC_ROCKCHIP_I2S
+ select SND_SOC_RT5640
+ select SND_SIMPLE_CARD
+ help
+ Say Y or M here if you want to add support for SoC audio on Rockchip
+ boards using the RT5640 codec, such as Firefly-RK3399.
+
config SND_SOC_ROCKCHIP_RT5645
tristate "ASoC support for Rockchip boards using a RT5645/RT5650 codec"
depends on SND_SOC_ROCKCHIP && I2C && GPIOLIB && CLKDEV_LOOKUP
--
2.19.2
reply other threads:[~2018-11-28 7:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181128072852.32760-1-max.kellermann@gmail.com \
--to=max.kellermann@gmail.com \
--cc=bardliao@realtek.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=oder_chiou@realtek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox