All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] ASoC: dt-bindings: nvidia,tegra-audio-max9808x: document additional board pins
Date: Mon, 9 Feb 2026 20:48:46 -0600	[thread overview]
Message-ID: <20260210024846.GA2385273-robh@kernel.org> (raw)
In-Reply-To: <20260206173423.145954-6-clamor95@gmail.com>

On Fri, Feb 06, 2026 at 07:34:22PM +0200, Svyatoslav Ryhel wrote:
> Document additional board pins that may be used in routing.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
>  .../bindings/sound/nvidia,tegra-audio-max9808x.yaml          | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max9808x.yaml b/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max9808x.yaml
> index 241d20f3aad0..4957645a8e03 100644
> --- a/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max9808x.yaml
> +++ b/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max9808x.yaml
> @@ -35,10 +35,15 @@ properties:
>      items:
>        enum:
>          # Board Connectors
> +        - Speakers
>          - Int Spk
> +        - Headphone
> +        - Headphones
>          - Headphone Jack

Aren't all 3 of these the same thing?

>          - Earpiece
>          - Headset Mic
> +        - Mic Jack
> +        - Int Mic
>          - Internal Mic 1
>          - Internal Mic 2
>  
> -- 
> 2.51.0
> 

  reply	other threads:[~2026-02-10  2:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 17:34 [PATCH v2 0/5] ASoC: tegra: Add support for WM8962 and CPCAP codecs Svyatoslav Ryhel
2026-02-06 17:34 ` [PATCH v2 1/5] ASoC: dt-bindings: nvidia,tegra-audio: document CPCAP CODEC Svyatoslav Ryhel
2026-02-10  2:46   ` Rob Herring
2026-02-10  5:08     ` Svyatoslav Ryhel
2026-02-06 17:34 ` [PATCH v2 2/5] ASoC: tegra: Support CPCAP by machine driver Svyatoslav Ryhel
2026-02-06 17:34 ` [PATCH v2 3/5] ASoC: dt-bindings: nvidia,tegra-audio: document WM8962 CODEC Svyatoslav Ryhel
2026-02-06 17:34 ` [PATCH v2 4/5] ASoC: tegra: Support WM8962 by machine driver Svyatoslav Ryhel
2026-02-06 17:34 ` [PATCH v2 5/5] ASoC: dt-bindings: nvidia,tegra-audio-max9808x: document additional board pins Svyatoslav Ryhel
2026-02-10  2:48   ` Rob Herring [this message]
2026-02-10  5:04     ` Svyatoslav Ryhel
2026-02-11 21:13   ` Rob Herring (Arm)

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=20260210024846.GA2385273-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=broonie@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonasschwoebel@yahoo.de \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=thierry.reding@gmail.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 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.