From: Caesar Wang <wxt@rock-chips.com>
To: broonie@kernel.org, robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.or, heiko@sntech.de,
bardliao@realtek.com, Caesar Wang <wxt@rock-chips.com>
Subject: [PATCH v2 2/2] dt-bindings: sound: add devicetree document for rt5616
Date: Tue, 22 Dec 2015 13:45:03 +0800 [thread overview]
Message-ID: <1450763103-21073-2-git-send-email-wxt@rock-chips.com> (raw)
In-Reply-To: <1450763103-21073-1-git-send-email-wxt@rock-chips.com>
Add the description for rt5616 codec.
Signed-off-by: Caesar Wang <wxt@rock-chips.com>
---
Changes in v2:
- As Frank comments, rt5616@1b to instead of rt5616.
- Update the Pins device from Bard.
Changes in v1:
- As Heiko comments, remove the not exist option properties.
Documentation/devicetree/bindings/sound/rt5616.txt | 26 ++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/rt5616.txt
diff --git a/Documentation/devicetree/bindings/sound/rt5616.txt b/Documentation/devicetree/bindings/sound/rt5616.txt
new file mode 100644
index 0000000..efc48c6
--- /dev/null
+++ b/Documentation/devicetree/bindings/sound/rt5616.txt
@@ -0,0 +1,26 @@
+RT5616 audio CODEC
+
+This device supports I2C only.
+
+Required properties:
+
+- compatible : "realtek,rt5616".
+
+- reg : The I2C address of the device.
+
+Pins on the device (for linking into audio routes) for RT5616:
+
+ * IN1P
+ * IN2P
+ * IN2N
+ * LOUTL
+ * LOUTR
+ * HPOL
+ * HPOR
+
+Example:
+
+codec: rt5616@1b {
+ compatible = "realtek,rt5616";
+ reg = <0x1b>;
+};
--
1.9.1
next prev parent reply other threads:[~2015-12-22 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 5:45 [PATCH v2 1/2] ASoC: rt5616: add an of_match table Caesar Wang
2015-12-22 5:45 ` Caesar Wang [this message]
[not found] ` <1450763103-21073-2-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-12-22 23:53 ` [PATCH v2 2/2] dt-bindings: sound: add devicetree document for rt5616 Mark Brown
2015-12-23 0:37 ` Rob Herring
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=1450763103-21073-2-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=alsa-devel@alsa-project.or \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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