[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120730134804.GE4468@opensource.wolfsonmicro.com>
Date: Mon, 30 Jul 2012 14:48:04 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
STEricsson_nomadik_linux@...t.st.com, linus.walleij@...ricsson.com,
arnd@...db.de, olalilja@...oo.se, ola.o.lilja@...ricsson.com,
alsa-devel@...a-project.org, lrg@...com
Subject: Re: [PATCH 01/18] Documentation: Describe the ux500 realated audio
related DT nodes
On Mon, Jul 30, 2012 at 08:38:49AM +0100, Lee Jones wrote:
> On 29/07/12 21:31, Mark Brown wrote:
> >On Fri, Jul 27, 2012 at 01:45:45PM +0100, Lee Jones wrote:
> >>+ - Machine Driver : "stericsson,snd-soc-mop500"
> >>+ - CPU-side DAI : "stericsson,ux500-msp-i2s"
> >>+ - DMA (platform) : "stericsson,ux500-pcm"
> >>+ - Audio CODEC : "stericsson,ab8500-codec"
> >What is this a binding document for? It looks like the binding for a
> >machine driver...
> No, it's a binding document for all of the ux500 driver and CODEC
> blocks. Do you really want me to split it all up? I think the only
> component which could be sanely split-out is the ab8500-codec, which
> could (should?) live in [1].
Yes, of course! Each device will have a separate binding with different
requirements.
> These properties are relevant for some, but not all of the
> components above, hence why the are listed at 'optional properties'.
Which is part of the problem here, it makes it much harder to tell what
you need to do for the individual devices.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists