linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
To: linux-sound@vger.kernel.org, krzk+dt@kernel.org
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
	conor+dt@kernel.org, drake@endlessm.com, katsuhiro@katsuster.net,
	matteomartelli3@gmail.com, zhoubinbin@loongson.cn,
	KCHSU0@nuvoton.com, patches@opensource.cirrus.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah@kernel.org, jihed.chaibi.dev@gmail.com
Subject: [PATCH v2 2/3] ASoC: dt-bindings: nuvoton,nau8825: Document routing strings
Date: Wed,  3 Sep 2025 18:01:18 +0200	[thread overview]
Message-ID: <20250903160119.83625-3-jihed.chaibi.dev@gmail.com> (raw)
In-Reply-To: <20250903160119.83625-1-jihed.chaibi.dev@gmail.com>

Add a list of the nau8825 pin names to the binding's description to make
it self-contained and improve the user experience for board developers.

Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>

---
Changes in v2:
 - Rephrased description to refer to device pins  instead of the
   driver.
---
 .../devicetree/bindings/sound/nuvoton,nau8825.yaml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/Documentation/devicetree/bindings/sound/nuvoton,nau8825.yaml b/Documentation/devicetree/bindings/sound/nuvoton,nau8825.yaml
index a54f194a0b4..4ebbcb4e605 100644
--- a/Documentation/devicetree/bindings/sound/nuvoton,nau8825.yaml
+++ b/Documentation/devicetree/bindings/sound/nuvoton,nau8825.yaml
@@ -9,6 +9,20 @@ title: NAU8825 audio CODEC
 maintainers:
   - John Hsu <KCHSU0@nuvoton.com>
 
+description: |
+  NAU8825 audio CODEC
+
+  Pins on the device (for linking into audio routes):
+
+    Outputs:
+      * HPOL    : Headphone Left Output
+      * HPOR    : Headphone Right Output
+      * MICBIAS : Microphone Bias Output
+
+    Inputs:
+      * MICP    : Analog Microphone Positive Input
+      * MICN    : Analog Microphone Negative Input
+
 allOf:
   - $ref: dai-common.yaml#
 
-- 
2.39.5


  parent reply	other threads:[~2025-09-03 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 16:01 [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for various codecs Jihed Chaibi
2025-09-03 16:01 ` [PATCH v2 1/3] ASoC: dt-bindings: everest,es8316: Document routing strings Jihed Chaibi
2025-09-03 23:55   ` Rob Herring (Arm)
2025-09-04 11:47   ` Binbin Zhou
2025-09-03 16:01 ` Jihed Chaibi [this message]
2025-09-03 23:55   ` [PATCH v2 2/3] ASoC: dt-bindings: nuvoton,nau8825: " Rob Herring (Arm)
2025-09-03 16:01 ` [PATCH v2 3/3] ASoC: dt-bindings: wlf,wm8960: Document routing strings (pin names) Jihed Chaibi
2025-09-03 23:55   ` Rob Herring (Arm)
2025-09-04  8:42   ` Charles Keepax
2025-09-04 18:09 ` [PATCH v2 0/3] ASoC: dt-bindings: Document routing strings for various codecs 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=20250903160119.83625-3-jihed.chaibi.dev@gmail.com \
    --to=jihed.chaibi.dev@gmail.com \
    --cc=KCHSU0@nuvoton.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drake@endlessm.com \
    --cc=katsuhiro@katsuster.net \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=matteomartelli3@gmail.com \
    --cc=patches@opensource.cirrus.com \
    --cc=robh@kernel.org \
    --cc=shuah@kernel.org \
    --cc=zhoubinbin@loongson.cn \
    /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).