alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
	alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: dapm: Fix x86_64 build warning.
Date: Mon, 23 Apr 2012 17:10:41 +0100	[thread overview]
Message-ID: <20120423161040.GP8318@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hbomi5unn.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]

On Mon, Apr 23, 2012 at 05:34:36PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:

> > We should do though we don't currently - see the recent discussion about
> > the ice drivers.  There are some PC sound cards (mostly high end or old
> > ones, or tuner cards) which have a setup like ASoC where there's a CODEC
> > on an I2C bus and a "platform" which in this case is a PCI type device.
> > At a high level they look the same as embedded hardware with several
> > chips glued together in software.

> Right.  In near future, we'd need to move up/down some ASoC code
> pieces into ALSA core so that people won't misunderstand.

I think from a code structure point of view we're probably mostly fine
as is (in that ASoC is sitting in parallel with more integrated sound
card architectures) - except for DAPM mostly ASoC is just thin wrappers
for the core which split things up for multiple devices.  We'd need to
deal with that layering somehow if we were merging stuff in.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2012-04-23 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  9:31 [PATCH] ASoC: dapm: Fix x86_64 build warning Liam Girdwood
2012-04-23 12:16 ` Mark Brown
2012-04-23 12:22   ` Vinod Koul
2012-04-23 12:28     ` Mark Brown
2012-04-23 15:34       ` Takashi Iwai
2012-04-23 16:10         ` 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=20120423161040.GP8318@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@linux.intel.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;
as well as URLs for NNTP newsgroup(s).