From: "Heiko Stübner" <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: robh+dt@kernel.org, broonie@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bardliao@realtek.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] dt-bindings: sound: add devicetree document for rt5616
Date: Mon, 21 Dec 2015 15:10:57 +0100 [thread overview]
Message-ID: <1511057.C46mHiuCd6@diego> (raw)
In-Reply-To: <1450703894-32623-2-git-send-email-wxt@rock-chips.com>
Am Montag, 21. Dezember 2015, 21:18:14 schrieb Caesar Wang:
> Add the description for rt5616 codec.
>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
> ---
>
> Documentation/devicetree/bindings/sound/rt5616.txt | 38
> ++++++++++++++++++++++ 1 file changed, 38 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..af96207
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/rt5616.txt
> @@ -0,0 +1,38 @@
> +RT5616 audio CODEC
> +
> +This device supports I2C only.
> +
> +Required properties:
> +
> +- compatible : "realtek,rt5616".
> +
> +- reg : The I2C address of the device.
> +
> +Optional properties:
you don't have optional properties, so that headline should probably also not
be here.
Heiko
next prev parent reply other threads:[~2015-12-21 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 13:18 [PATCH 1/2] ASoC: rt5616: add an of_match table Caesar Wang
2015-12-21 13:18 ` [PATCH 2/2] dt-bindings: sound: add devicetree document for rt5616 Caesar Wang
2015-12-21 14:10 ` Heiko Stübner [this message]
2015-12-21 14:44 ` Caesar Wang
2015-12-21 14:56 ` [PATCH v1 " Caesar Wang
2015-12-21 21:15 ` Frank Rowand
2015-12-22 0:54 ` Caesar Wang
2015-12-22 1:50 ` Bard Liao
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=1511057.C46mHiuCd6@diego \
--to=heiko@sntech.de \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wxt@rock-chips.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