From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Liam Girdwood <lgirdwood@gmail.com>,
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>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH v3 3/5] ASoC: dt-bindings: wm8904: Add DMIC, GPIO, MIC and EQ support
Date: Tue, 11 Mar 2025 13:46:58 +0000 [thread overview]
Message-ID: <0898b492-71ed-4df3-bf81-c3965e4c7ec7@sirena.org.uk> (raw)
In-Reply-To: <20250311-solid-poetic-camel-77a29b@krzk-bin>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Tue, Mar 11, 2025 at 09:42:45AM +0100, Krzysztof Kozlowski wrote:
> On Fri, Mar 07, 2025 at 02:52:42PM +0100, Francesco Dolcini wrote:
> > + wlf,in1l-as-dmicdat1:
> > + type: boolean
> > + description:
> > + Use IN1L/DMICDAT1 as DMICDAT1, enabling the DMIC input path.
> > + wlf,in1r-as-dmicdat2:
> > + type: boolean
> > + description:
> > + Use IN1R/DMICDAT2 as DMICDAT2, enabling the DMIC input path.
> Are these two properties mutually exclusive?
No, it's one property each for the left and right channels.
> > + wlf,drc-cfg-names:
> > + $ref: /schemas/types.yaml#/definitions/string-array
> No constraints, so I assume you can have here any number of items?
Yes.
> > + description:
> > + List of strings for the available DRC modes.
> Why the actual names are not defined? Why do you need this property if
> they are not defined (thus driver does not request this by the name)?
The driver displays the list of names to the end user for them to choose
between.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-11 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:52 [PATCH v3 0/5] ASoC: wm8904: Add DMIC and DRC support Francesco Dolcini
2025-03-07 13:52 ` [PATCH v3 1/5] of: Add of_property_read_u16_index Francesco Dolcini
2025-03-07 13:52 ` [PATCH v3 2/5] ASoC: wm8904: Don't touch GPIO configs set to 0xFFFF Francesco Dolcini
2025-03-07 13:52 ` [PATCH v3 3/5] ASoC: dt-bindings: wm8904: Add DMIC, GPIO, MIC and EQ support Francesco Dolcini
2025-03-11 8:42 ` Krzysztof Kozlowski
2025-03-11 13:46 ` Mark Brown [this message]
2025-03-11 17:59 ` Rob Herring
2025-03-12 8:39 ` Krzysztof Kozlowski
2025-03-12 8:48 ` Ernest Van Hoecke
2025-03-12 8:41 ` Krzysztof Kozlowski
2025-03-07 13:52 ` [PATCH v3 4/5] ASoC: wm8904: get platform data from DT Francesco Dolcini
2025-03-07 13:52 ` [PATCH v3 5/5] ASoC: wm8904: add DMIC support Francesco Dolcini
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=0898b492-71ed-4df3-bf81-c3965e4c7ec7@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--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=krzk@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
all inboxes | Powered by JetHome®