From: codekipper@gmail.com (codekipper at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ASoC: sun4i-spdif: remove legacy dapm components
Date: Tue, 20 Dec 2016 15:49:13 +0100 [thread overview]
Message-ID: <20161220144914.30945-2-codekipper@gmail.com> (raw)
In-Reply-To: <20161220144914.30945-1-codekipper@gmail.com>
From: Marcus Cooper <codekipper@gmail.com>
The dapm components are now handled by the ALSA SoC SPDIF DIT driver
so can be removed.
Signed-off-by: Marcus Cooper <codekipper@gmail.com>
---
sound/soc/sunxi/sun4i-spdif.c | 8 --------
1 file changed, 8 deletions(-)
diff --git a/sound/soc/sunxi/sun4i-spdif.c b/sound/soc/sunxi/sun4i-spdif.c
index 88fbb3a1e660..048de15d6937 100644
--- a/sound/soc/sunxi/sun4i-spdif.c
+++ b/sound/soc/sunxi/sun4i-spdif.c
@@ -403,14 +403,6 @@ static struct snd_soc_dai_driver sun4i_spdif_dai = {
.name = "spdif",
};
-static const struct snd_soc_dapm_widget dit_widgets[] = {
- SND_SOC_DAPM_OUTPUT("spdif-out"),
-};
-
-static const struct snd_soc_dapm_route dit_routes[] = {
- { "spdif-out", NULL, "Playback" },
-};
-
static const struct of_device_id sun4i_spdif_of_match[] = {
{ .compatible = "allwinner,sun4i-a10-spdif", },
{ .compatible = "allwinner,sun6i-a31-spdif", },
--
2.11.0
next prev parent reply other threads:[~2016-12-20 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 14:49 [PATCH 0/2] ASoC: sun4i-spdif: Changes in preparation of supporting new SoCs codekipper at gmail.com
2016-12-20 14:49 ` codekipper at gmail.com [this message]
2016-12-20 19:11 ` [PATCH 1/2] ASoC: sun4i-spdif: remove legacy dapm components Maxime Ripard
2016-12-31 19:19 ` Applied "ASoC: sun4i-spdif: remove legacy dapm components" to the asoc tree Mark Brown
2016-12-20 14:49 ` [PATCH 2/2] ASoC: sun4i-spdif: Add quirks to the spdif driver codekipper at gmail.com
2016-12-20 19:12 ` Maxime Ripard
2016-12-31 19:19 ` Applied "ASoC: sun4i-spdif: Add quirks to the spdif driver" to the asoc tree Mark Brown
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=20161220144914.30945-2-codekipper@gmail.com \
--to=codekipper@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).