From: jeffy <jeffy.chen@rock-chips.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
heiko@sntech.de, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
dianders@chromium.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, mka@chromium.org,
dgreid@chromium.org
Subject: Re: [PATCH v8 1/2] ASoC: rt5514: Add devicetree bindings for rt5514-spi
Date: Wed, 06 Sep 2017 10:42:25 +0800 [thread overview]
Message-ID: <59AF6091.5000204@rock-chips.com> (raw)
In-Reply-To: <20170905175532.GA9393@google.com>
Hi Brian,
On 09/06/2017 01:55 AM, Brian Norris wrote:
>> +This device supports SPI only.
>> >+
>> >+Required properties:
>> >+
>> >+- compatible : "realtek,rt5514".
> You list one string here, but there's 2 in the example. The point of
> this exercise was to document (not just in an Example) the strings
> you're using.
Ok, will do.
>
>> >+
>> >+- reg : The SPI address of the device.
>> >+
>> >+Optional properties:
>> >+
>> >+- interrupt-parent: Should be the phandle for the interrupt controller
>> >+- interrupts: The interrupt number to the cpu. The interrupt specifier format
>> >+ depends on the interrupt controller.
>> >+
>> >+Example:
>> >+
>> >+codec: rt5514-spi@0 {
>> >+ compatible = "realtek,rt5514", "realtek,rt5514-spi";
>> >+ reg = <0>;
>> >+
>> >+ /* May run faster once verified. */
> Really? That was barely useful in the rk3399-gru DTSI, but it's
> definitely not worth sticking in an example.
>
> Also, you switch between tabs and spaces for indentation. Please be
> consistent. (And as with C code, I think the right answer is tabs?)
Oops, thanks for noticing.
>
>> >+ spi-max-frequency = <10000000>;
>> >+
>> >+ pinctrl-names = "default";
>> >+ pinctrl-0 = <&mic_int>;
>> >+
>> >+ interrupt-parent = <&gpio1>;
>> >+ interrupts = <13 IRQ_TYPE_LEVEL_HIGH>;
>> >+ wakeup-source;
>> >+};
>> >diff --git a/Documentation/devicetree/bindings/sound/rt5514.txt b/Documentation/devicetree/bindings/sound/rt5514.txt
>> >index 929ca6756b02..12a8c93a67cc 100644
>> >--- a/Documentation/devicetree/bindings/sound/rt5514.txt
>> >+++ b/Documentation/devicetree/bindings/sound/rt5514.txt
>> >@@ -28,6 +28,6 @@ Pins on the device (for linking into audio routes) for RT5514:
>> > Example:
>> >
>> > codec: rt5514@57 {
>> >- compatible = "realtek,rt5514";
>> >+ compatible = "realtek,rt5514", "realtek,rt5514-i2c";
> Example != Documentation. Please document the string properly.
Ok, will do.
>
> Brian
>
prev parent reply other threads:[~2017-09-06 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 4:24 [PATCH v8 1/2] ASoC: rt5514: Add devicetree bindings for rt5514-spi Jeffy Chen
2017-09-05 4:25 ` [PATCH v8 2/2] arm64: dts: rockchip: Update rt5514 devices' compatible for Gru Jeffy Chen
[not found] ` <20170905042500.25656-1-jeffy.chen-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-09-05 17:55 ` [PATCH v8 1/2] ASoC: rt5514: Add devicetree bindings for rt5514-spi Brian Norris
2017-09-06 2:42 ` jeffy [this message]
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=59AF6091.5000204@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).