From: Mark Brown <broonie@kernel.org>
To: Songjun Wu <songjun.wu@atmel.com>
Cc: nicolas.ferre@atmel.com, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: atmel-classd: DT binding for Class D audio amplifier driver
Date: Thu, 3 Sep 2015 12:43:16 +0100 [thread overview]
Message-ID: <20150903114316.GV12027@sirena.org.uk> (raw)
In-Reply-To: <1441086101-15303-3-git-send-email-songjun.wu@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Tue, Sep 01, 2015 at 01:41:41PM +0800, Songjun Wu wrote:
> +classd: classd@fc048000 {
> + compatible = "atmel,sama5d2-classd";
> + reg = <0xfc048000 0x100>;
> + interrupts = <59 IRQ_TYPE_LEVEL_HIGH 7>;
> + dmas = <&dma0
> + (AT91_XDMAC_DT_MEM_IF(0) | AT91_XDMAC_DT_PER_IF(1)
> + | AT91_XDMAC_DT_PERID(47))>;
> + dma-names = "tx";
> + clocks = <&classd_clk>, <&classd_gclk>, <&audio_pll_pmc>;
> + clock-names = "pclk", "gclk", "aclk";
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_classd_default>;
> + atmel,pwm-type = "diff";
> + atmel,non-overlap-time = <10>;
> +};
> +Example:
> +sound {
> + compatible = "atmel,asoc-classd";
> +
> + atmel,model = "classd @ SAMA5D2-Xplained";
> + atmel,audio-platform = <&classd>;
> + atmel,audio-cpu-dai-name = "fc048000.classd";
> + atmel,audio-codec = <&classd>;
> +};
Why is this a separate DT node? It seems that this IP is entirely self
contained so I'm not clear why we need a separate node for the card, the
card is usually a separate node because it ties together multiple
different devices in the system but that's not the case here.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-03 12:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 5:41 [PATCH 0/2] ASoC: atmel-classd: add the Audio Class D Amplifier Songjun Wu
2015-09-01 5:41 ` [PATCH 1/2] ASoC: atmel-classd: add the Audio Class D Amplifier code Songjun Wu
2015-09-03 11:37 ` Mark Brown
2015-09-06 9:44 ` Wu, Songjun
2015-09-07 16:23 ` Mark Brown
2015-09-08 9:36 ` Wu, Songjun
2015-09-08 12:23 ` Mark Brown
2015-09-09 3:16 ` Wu, Songjun
2015-09-09 9:52 ` Mark Brown
2015-09-10 2:31 ` Wu, Songjun
2015-09-11 10:34 ` Mark Brown
2015-09-14 6:34 ` Wu, Songjun
2015-09-01 5:41 ` [PATCH 2/2] ASoC: atmel-classd: DT binding for Class D audio amplifier driver Songjun Wu
2015-09-03 11:43 ` Mark Brown [this message]
2015-09-06 9:44 ` Wu, Songjun
2015-09-07 16:25 ` Mark Brown
2015-09-08 9:36 ` Wu, Songjun
2015-09-08 12:23 ` Mark Brown
2015-09-09 3:16 ` Wu, Songjun
2015-09-15 3:11 ` Wu, Songjun
2015-09-16 19:42 ` Mark Brown
2015-09-17 3:07 ` Wu, Songjun
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=20150903114316.GV12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=songjun.wu@atmel.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®