From: Olivier Moysan <olivier.moysan@st.com>
To: <linux@armlinux.org.uk>, <shawnguo@kernel.org>, <olof@lixom.net>,
<alexandre.torgue@st.com>, <krzk@kernel.org>,
<geert+renesas@glider.be>, <amelie.delaunay@st.com>,
<aisheng.dong@nxp.com>, <prabhakar.mahadev-lad.rj@bp.renesas.com>,
<christian.gmeiner@gmail.com>, <enric.balletbo@collabora.com>,
<lionel.debieve@st.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <olivier.moysan@st.com>
Subject: [PATCH v2 2/2] ARM: multi_v7_defconfig: enable dfsdm audio support
Date: Fri, 20 Nov 2020 10:15:06 +0100 [thread overview]
Message-ID: <20201120091506.18326-3-olivier.moysan@st.com> (raw)
In-Reply-To: <20201120091506.18326-1-olivier.moysan@st.com>
Add STM32 DFSDM audio support by enabling CONFIG_SND_SOC_STM32_DFSDM
as module.
Signed-off-by: Olivier Moysan <olivier.moysan@st.com>
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index b30a3bc6762b..083d5f4450f4 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -743,6 +743,7 @@ CONFIG_SND_SOC_STI=m
CONFIG_SND_SOC_STM32_SAI=m
CONFIG_SND_SOC_STM32_I2S=m
CONFIG_SND_SOC_STM32_SPDIFRX=m
+CONFIG_SND_SOC_STM32_DFSDM=m
CONFIG_SND_SUN4I_CODEC=m
CONFIG_SND_SOC_TEGRA=m
CONFIG_SND_SOC_TEGRA20_I2S=m
--
2.17.1
next prev parent reply other threads:[~2020-11-20 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 9:15 [PATCH v2 0/2] ARM: multi_v7_defconfig: enable dfsdm and spdifrx support Olivier Moysan
2020-11-20 9:15 ` [PATCH v2 1/2] ARM: multi_v7_defconfig: enable " Olivier Moysan
2020-11-20 9:15 ` Olivier Moysan [this message]
2020-11-20 9:18 ` [PATCH v2 2/2] ARM: multi_v7_defconfig: enable dfsdm audio support Krzysztof Kozlowski
2020-11-26 11:25 ` [PATCH v2 0/2] ARM: multi_v7_defconfig: enable dfsdm and spdifrx support Alexandre Torgue
2020-11-26 13:38 ` Olivier MOYSAN
2020-11-26 13:40 ` Alexandre Torgue
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=20201120091506.18326-3-olivier.moysan@st.com \
--to=olivier.moysan@st.com \
--cc=aisheng.dong@nxp.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=christian.gmeiner@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=geert+renesas@glider.be \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lionel.debieve@st.com \
--cc=olof@lixom.net \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).