From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Jean-Francois Moine <moinejf@free.fr>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem
Date: Fri, 9 Aug 2013 11:18:42 +0100 [thread overview]
Message-ID: <20130809101842.GR6427@sirena.org.uk> (raw)
In-Reply-To: <5204BF06.3060806@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-08-09 10:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 11:22 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
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 [this message]
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=20130809101842.GR6427@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tiwai@suse.de \
/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®