[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130809101842.GR6427@sirena.org.uk>
Date: Fri, 9 Aug 2013 11:18:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Lars-Peter Clausen <lars@...afoo.de>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Jean-Francois Moine <moinejf@...e.fr>,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <rob.herring@...xeda.com>,
Russell King <rmk+kernel@....linux.org.uk>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [alsa-devel] [PATCH v4 1/1] ASoc: kirkwood: add DT support to
the mvebu audio subsystem
On Fri, Aug 09, 2013 at 12:05:58PM +0200, Lars-Peter Clausen wrote:
> On 08/09/2013 11:34 AM, Sebastian Hesselbarth wrote:
> > 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.
> It's not about SoCs, it's about the board. The audio fabric on a board can
> easily get complex enough to require its own driver. Speakers, mics, jacks
> and jack detection, external amplifiers, bluetooth, baseband, multiple
> CODECs. That's what the audio node describes.
Exactly - as I said earlier on this week the issue is that in many cases
there is enough going on in audio system design to make the PCB an
interesting bit of hardware that's worth describing in the device tree.
To repeat what I said before *please* go back and check the list
archives, we've been through this several times.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists