From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
nsekhar@ti.com, robh+dt@kernel.org
Cc: devicetree@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
linux@arm.linux.org.uk, pawel.moll@arm.com,
khilman@deeprootsystems.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/6] ARM: DTS: da850-evm: Add node for tlv320aic3106 codec
Date: Thu, 31 Jul 2014 18:24:26 +0400 [thread overview]
Message-ID: <53DA519A.4090905@cogentembedded.com> (raw)
In-Reply-To: <1406801934-23334-6-git-send-email-peter.ujfalusi@ti.com>
Hello.
On 07/31/2014 02:18 PM, Peter Ujfalusi wrote:
> The board uses aic3106 for audio.
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> arch/arm/boot/dts/da850-evm.dts | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
> diff --git a/arch/arm/boot/dts/da850-evm.dts b/arch/arm/boot/dts/da850-evm.dts
> index 09118c72e83f..b9ef2be0b145 100644
> --- a/arch/arm/boot/dts/da850-evm.dts
> +++ b/arch/arm/boot/dts/da850-evm.dts
> @@ -51,6 +51,20 @@
> tps: tps@48 {
> reg = <0x48>;
> };
> + tlv320aic3106: tlv320aic3106@1b {
The "reg" property is <0x18>, why the unit-address part of a name is
different? Also, the ePAPR standard [1] says:
The name of a node should be somewhat generic, reflecting the function of the
device and not its precise programming model.
> + #sound-dai-cells = <0>;
> + compatible = "ti,tlv320aic3106";
> + reg = <0x18>;
> + status = "okay";
> +
> + /* Regulators */
> + IOVDD-supply = <&vdcdc2_reg>;
> + /* Derived from VBAT: Baseboard 3.3V / 1.8V */
> + AVDD-supply = <&vbat>;
> + DRVDD-supply = <&vbat>;
> + DVDD-supply = <&vbat>;
> + };
> +
[1] http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf
WBR, Sergei
next prev parent reply other threads:[~2014-07-31 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 10:18 [PATCH 0/6] ARM: DT/davinci: Audio for da850-evm in DT boot Peter Ujfalusi
2014-07-31 10:18 ` [PATCH 1/6] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entry for mcasp0 Peter Ujfalusi
2014-07-31 10:18 ` [PATCH 2/6] ARM: DTS: da850: Add node for edma0 Peter Ujfalusi
2014-07-31 14:26 ` Sergei Shtylyov
2014-08-01 5:09 ` Peter Ujfalusi
2014-08-01 6:18 ` Sekhar Nori
2014-07-31 10:18 ` [PATCH 3/6] ARM: DTS: da850: Add node for McASP Peter Ujfalusi
2014-07-31 10:18 ` [PATCH 4/6] ARM: DTS: da850-evm: Enable McASP via DT boot Peter Ujfalusi
2014-07-31 10:18 ` [PATCH 5/6] ARM: DTS: da850-evm: Add node for tlv320aic3106 codec Peter Ujfalusi
2014-07-31 14:24 ` Sergei Shtylyov [this message]
2014-08-01 5:22 ` Peter Ujfalusi
2014-08-01 12:49 ` Sergei Shtylyov
2014-08-01 13:02 ` Peter Ujfalusi
2014-08-01 13:13 ` Sergei Shtylyov
2014-08-01 13:34 ` Peter Ujfalusi
2014-08-04 9:09 ` Peter Ujfalusi
2014-07-31 10:18 ` [PATCH 6/6] ARM: DTS: da850-evm: Enable audio via simple-card Peter Ujfalusi
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=53DA519A.4090905@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=peter.ujfalusi@ti.com \
--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