All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brent Lu <brent.lu@intel.com>
To: alsa-devel@alsa-project.org
Cc: "Cezary Rojewski" <cezary.rojewski@intel.com>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Liam Girdwood" <liam.r.girdwood@linux.intel.com>,
	"Peter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
	"Bard Liao" <yung-chuan.liao@linux.intel.com>,
	"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
	"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
	"Brent Lu" <brent.lu@intel.com>,
	linux-kernel@vger.kernel.org,
	"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>
Subject: [PATCH 02/12] ASoC: Intel: avs-dmic: remove redundant dapm routes
Date: Mon, 12 Jun 2023 19:09:48 +0800	[thread overview]
Message-ID: <20230612110958.592674-3-brent.lu@intel.com> (raw)
In-Reply-To: <20230612110958.592674-1-brent.lu@intel.com>

Two routes "DMIC Rx<-Capture" and "DMIC WoV Rx<-Capture" are created
by snd_soc_dapm_connect_dai_link_widgets() automatically. Remove the
duplicate routes.

Signed-off-by: Brent Lu <brent.lu@intel.com>
---
 sound/soc/intel/avs/boards/dmic.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/sound/soc/intel/avs/boards/dmic.c b/sound/soc/intel/avs/boards/dmic.c
index 90a921638572..c270646faf86 100644
--- a/sound/soc/intel/avs/boards/dmic.c
+++ b/sound/soc/intel/avs/boards/dmic.c
@@ -44,8 +44,6 @@ static const struct snd_soc_dapm_widget card_widgets[] = {
 
 static const struct snd_soc_dapm_route card_routes[] = {
 	{"DMic", NULL, "SoC DMIC"},
-	{"DMIC Rx", NULL, "Capture"},
-	{"DMIC WoV Rx", NULL, "Capture"},
 };
 
 static int avs_dmic_probe(struct platform_device *pdev)
-- 
2.34.1


  parent reply	other threads:[~2023-06-12  3:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 11:09 [PATCH 00/12] ASoC: Intel: avs: remove redundant dapm routes Brent Lu
2023-06-12 11:09 ` [PATCH 01/12] ASoC: Intel: avs-da7219: " Brent Lu
2023-06-12 11:09 ` Brent Lu [this message]
2023-06-12 11:09 ` [PATCH 03/12] ASoC: Intel: avs-hdaudio: " Brent Lu
2023-06-12 11:09 ` [PATCH 04/12] ASoC: Intel: avs-max98357a: " Brent Lu
2023-06-12 11:09 ` [PATCH 05/12] ASoC: Intel: avs-max98373: " Brent Lu
2023-06-12 11:09 ` [PATCH 06/12] ASoC: Intel: avs-max98927: " Brent Lu
2023-06-12 11:09 ` [PATCH 07/12] ASoC: Intel: avs-nau8825: " Brent Lu
2023-06-12 11:09 ` [PATCH 08/12] ASoC: Intel: avs-rt274: " Brent Lu
2023-06-12 11:09 ` [PATCH 09/12] ASoC: Intel: avs-rt286: " Brent Lu
2023-06-12 11:09 ` [PATCH 10/12] ASoC: Intel: avs-rt298: " Brent Lu
2023-06-12 11:09 ` [PATCH 11/12] ASoC: Intel: avs-rt5682: " Brent Lu
2023-06-12 11:09 ` [PATCH 12/12] ASoC: Intel: avs-ssm4567: " Brent Lu
2023-06-12 17:35 ` [PATCH 00/12] ASoC: Intel: avs: " 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=20230612110958.592674-3-brent.lu@intel.com \
    --to=brent.lu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.