From: Sameer Pujar <spujar@nvidia.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<broonie@kernel.org>, <treding@gmail.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <jonathanh@nvidia.com>,
<linux-tegra@vger.kernel.org>, Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH 1/2] arm64: defconfig: Enable couple of audio codecs
Date: Fri, 30 Sep 2022 19:26:33 +0530 [thread overview]
Message-ID: <1664546194-735-2-git-send-email-spujar@nvidia.com> (raw)
In-Reply-To: <1664546194-735-1-git-send-email-spujar@nvidia.com>
Enable RT5640 and TAS2552 audio codec drivers.
NVIDIA Jetson platforms have 40-pin GPIO expanders where custom
audio cards can be connected. Support for above codecs is typically
required. Also NVIDIA Jetson AGX Orin platform has RT5640 as onboard
codec. To support these enable driver build for these codecs.
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index a943883..b682318 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -843,9 +843,11 @@ CONFIG_SND_SOC_GTM601=m
CONFIG_SND_SOC_MSM8916_WCD_ANALOG=m
CONFIG_SND_SOC_MSM8916_WCD_DIGITAL=m
CONFIG_SND_SOC_PCM3168A_I2C=m
+CONFIG_SND_SOC_RT5640=m
CONFIG_SND_SOC_RT5659=m
CONFIG_SND_SOC_SIMPLE_AMPLIFIER=m
CONFIG_SND_SOC_SIMPLE_MUX=m
+CONFIG_SND_SOC_TAS2552=m
CONFIG_SND_SOC_TAS571X=m
CONFIG_SND_SOC_TLV320AIC32X4_I2C=m
CONFIG_SND_SOC_WCD9335=m
--
2.7.4
next prev parent reply other threads:[~2022-09-30 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 13:56 [PATCH 0/2] Audio configs for NVIDIA Jetson platforms Sameer Pujar
2022-09-30 13:56 ` Sameer Pujar [this message]
2022-09-30 13:56 ` [PATCH 2/2] arm64: defconfig: Enable SND_ALOOP Sameer Pujar
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=1664546194-735-2-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@gmail.com \
--cc=will@kernel.org \
/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