From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem
Date: Fri, 09 Aug 2013 11:34:30 +0200 [thread overview]
Message-ID: <5204B7A6.9050907@gmail.com> (raw)
In-Reply-To: <20130809091953.GO6427@sirena.org.uk>
On 08/09/13 11:19, Mark Brown wrote:
> On Fri, Aug 09, 2013 at 10:23:50AM +0200, Sebastian Hesselbarth wrote:
>> On 08/08/2013 01:22 PM, Jean-Francois Moine wrote:
>
>>> +i2s1: audio-controller at b4000 {
>>> + compatible = "mrvl,mvebu-audio";
>>> + reg = <0xb4000 0x2210>;
>>> + interrupts = <21>, <22>;
>>> + clocks = <&gate_clk 13>;
>>> + clock-names = "internal";
>>> +};
>
>> Also we will need some phandle reference to the audio codec here. As
>> this property is ongoing work in ASoC core, I suggest we wait for it
>> and propose a binding afterwards.
>
> No, as discussed this should be in the binding for the audio subsystem
> not in the binding for an individual component in that subsystem.
>
Mark,
I do understand there may be SoCs requiring sophisticated extra audio
nodes, but Marvell SoCs don't. I prefer having a single node for the
i2s controller *and* exploit the audio subsystem properties from that.
For Marvell audio, we only need a single node for all three ASoC
drivers. No other subsystem _requires_ you to have extra nodes for
it's needs. If you can provide interrupts, just have an interrupt-
controller property. If you can provide clocks, you can link to that
very node - no virtual device node required. Even for media they
do not insist on a virtual node but they do have generic properties
you can exploit.
If you insist on creating a virtual sound card node just because
ASoC wants it that way - okay, your call. But I don't see any value
in that.
Sebastian
next prev parent reply other threads:[~2013-08-09 9:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 11:22 [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem Jean-Francois Moine
2013-08-09 8:23 ` Sebastian Hesselbarth
2013-08-09 9:06 ` Jean-Francois Moine
2013-08-09 9:30 ` Russell King - ARM Linux
2013-08-10 9:16 ` Thomas Petazzoni
2013-08-09 9:19 ` Mark Brown
2013-08-09 9:34 ` Sebastian Hesselbarth [this message]
2013-08-09 9:43 ` Russell King - ARM Linux
2013-08-09 10:30 ` [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem [OT] Jean-Francois Moine
2013-08-09 11:01 ` [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem Sebastian Hesselbarth
2013-08-09 11:39 ` Mark Brown
2013-08-09 13:09 ` Russell King - ARM Linux
2013-08-09 18:00 ` Mark Brown
2013-08-09 18:25 ` Russell King - ARM Linux
2013-08-09 19:44 ` Mark Brown
2013-08-09 20:38 ` Russell King - ARM Linux
2013-08-09 23:42 ` Mark Brown
2013-08-10 9:31 ` Russell King - ARM Linux
2013-08-10 11:12 ` Mark Brown
2013-08-09 10:05 ` [alsa-devel] " Lars-Peter Clausen
2013-08-09 10:18 ` Mark Brown
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=5204B7A6.9050907@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).