From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, "Rob Herring" <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<patches@opensource.cirrus.com>,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>,
<linux-sound@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Francesco Dolcini" <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v1 5/5] ASoC: wm8904: add DMIC support
Date: Mon, 17 Feb 2025 10:44:42 +0000 [thread overview]
Message-ID: <Z7MTGq9zBqWCJ4kt@opensource.cirrus.com> (raw)
In-Reply-To: <20250206163152.423199-6-francesco@dolcini.it>
On Thu, Feb 06, 2025 at 05:31:52PM +0100, Francesco Dolcini wrote:
> From: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
> +static const struct snd_soc_dapm_route dmic_intercon[] = {
> + { "DMIC Mux", "DMIC1", "IN1L" },
> + { "DMIC Mux", "DMIC2", "IN1R" },
> +
> + { "ADCL", NULL, "DMIC Mux" },
> + { "ADCR", NULL, "DMIC Mux" },
> +};
> +
> +static const struct snd_soc_dapm_route cin_intercon[] = {
> + { "Left Capture Input", "ADC", "Left Capture PGA" },
> + { "Left Capture Input", "DMIC", "IN1L" },
> + { "Right Capture Input", "ADC", "Right Capture PGA" },
> + { "Right Capture Input", "DMIC", "IN1R" },
Am I misunderstanding things or does something not quite look
right with the routes here? Shouldn't you end up with the these
three situations:
Analogue:
{ "Left Capture Input", "ADC", "Left Capture PGA" },
{ "Right Capture Input", "ADC", "Right Capture PGA" },
Digital in1l_as_dmicdat1:
{ "Left Capture Input", "DMIC", "IN1L" },
{ "Right Capture Input", "DMIC", "IN1L" },
Digital in1r_as_dmicdat2:
{ "Left Capture Input", "DMIC", "IN1R" },
{ "Right Capture Input", "DMIC", "IN1R" },
So I think you need to add the DMIC routes conditionally here.
Also is there not some part of the existing analogue routing that
needs disconnected in the DMIC cases? This only addes routes,
which feels like the existing analogue path is never
disconnected?
Thanks,
Charles
> +
> + { "ADCL", NULL, "Left Capture Input" },
> + { "ADCR", NULL, "Right Capture Input" },
> +};
prev parent reply other threads:[~2025-02-17 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 16:31 [PATCH v1 0/5] ASoC: wm8904: Add DMIC and DRC support Francesco Dolcini
2025-02-06 16:31 ` [PATCH v1 1/5] of: Add of_property_read_u16_index Francesco Dolcini
2025-02-11 22:08 ` Rob Herring (Arm)
2025-02-17 9:55 ` Charles Keepax
2025-02-06 16:31 ` [PATCH v1 2/5] ASoC: wm8904: Don't touch GPIO configs set to 0xFFFF Francesco Dolcini
2025-02-17 9:57 ` Charles Keepax
2025-02-06 16:31 ` [PATCH v1 3/5] ASoC: dt-bindings: wm8904: Add DMIC, GPIO, MIC and EQ support Francesco Dolcini
2025-02-11 22:19 ` Rob Herring
2025-02-11 22:31 ` Mark Brown
2025-02-17 10:05 ` Charles Keepax
2025-02-06 16:31 ` [PATCH v1 4/5] ASoC: wm8904: get platform data from DT Francesco Dolcini
2025-02-17 10:07 ` Charles Keepax
2025-02-06 16:31 ` [PATCH v1 5/5] ASoC: wm8904: add DMIC support Francesco Dolcini
2025-02-17 10:44 ` Charles Keepax [this message]
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=Z7MTGq9zBqWCJ4kt@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ernest.vanhoecke@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).