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 v2 5/5] ASoC: wm8904: add DMIC support
Date: Tue, 4 Mar 2025 13:56:17 +0000 [thread overview]
Message-ID: <Z8cGgcq4ynfeCNKp@opensource.cirrus.com> (raw)
In-Reply-To: <20250224155500.52462-6-francesco@dolcini.it>
On Mon, Feb 24, 2025 at 04:55:00PM +0100, Francesco Dolcini wrote:
> From: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
>
> The WM8904 codec supports both ADC and DMIC inputs.
>
> Get input pin functionality from the platform data and add the necessary
> controls depending on the possible additional routing.
>
> The ADC and DMIC share the IN1L/DMICDAT1 and IN1R/DMICDAT2 pins.
>
> This leads to a few scenarios requiring different DAPM routing:
> - When both are connected to an analog input, only the ADC is used.
> - When one line is a DMIC and the other an analog input, the DMIC source
> is set from the platform data and a mux is added to select whether to
> use the ADC or DMIC.
> - When both are connected to a DMIC, another mux is added to this to
> select the DMIC source. Note that we still need to be able to select
> the ADC system for use with the IN2L, IN2R, IN3L and IN3R pins.
>
> Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> ---
Apologies for the delay, I think this looks good to me:
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2025-03-04 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 15:54 [PATCH v2 0/5] ASoC: wm8904: Add DMIC and DRC support Francesco Dolcini
2025-02-24 15:54 ` [PATCH v2 1/5] of: Add of_property_read_u16_index Francesco Dolcini
2025-02-24 15:54 ` [PATCH v2 2/5] ASoC: wm8904: Don't touch GPIO configs set to 0xFFFF Francesco Dolcini
2025-02-24 15:54 ` [PATCH v2 3/5] ASoC: dt-bindings: wm8904: Add DMIC, GPIO, MIC and EQ support Francesco Dolcini
2025-02-24 17:19 ` Rob Herring (Arm)
2025-02-25 8:41 ` Krzysztof Kozlowski
2025-02-27 15:34 ` Ernest Van Hoecke
2025-03-05 6:45 ` Krzysztof Kozlowski
2025-03-05 9:52 ` Charles Keepax
2025-03-05 13:18 ` Mark Brown
2025-02-24 15:54 ` [PATCH v2 4/5] ASoC: wm8904: get platform data from DT Francesco Dolcini
2025-02-24 15:55 ` [PATCH v2 5/5] ASoC: wm8904: add DMIC support Francesco Dolcini
2025-03-04 13:56 ` 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=Z8cGgcq4ynfeCNKp@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).