All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: alsa-devel@alsa-project.org
Cc: alsa-devel@vger.kernel.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC/multi-component: fix au1x platform
Date: Thu, 19 Aug 2010 15:35:56 +0100	[thread overview]
Message-ID: <20100819143555.GB29453@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTik_VdzUEZ0+079iZciOryRbFNDyjE-jdzJXztcW@mail.gmail.com>

On Thu, Aug 19, 2010 at 04:30:10PM +0200, Manuel Lauss wrote:
> On Thu, Aug 19, 2010 at 4:06 PM, Mark Brown

> > As far as your comments about multiple cards go this should now be
> > supported, though the fact that you're modifying the static data for the
> > DAI means that the aux1x drivers probably don't support this or only
> > support it in a limited fashion.

> The hardware does support it with the issue you mentioned fixed, but the
> global "soc_ac97_ops" needs to go away first.  The alchemy line can
> support up to 4 independent ac97 "cards" with certain models.

So this comment only applies to the AC97 DAIs, not the I2S ones?
Actually, even for AC97 I'd expect things to work fine off the top of my
head - while you are forced to use the same ops for everything the ops
is just a vtable which I'd expect to be the same for all DAIs?

  reply	other threads:[~2010-08-19 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 13:21 [PATCH] ASoC/multi-component: fix au1x platform Manuel Lauss
2010-08-19 14:06 ` Mark Brown
2010-08-19 14:30   ` Manuel Lauss
2010-08-19 14:35     ` Mark Brown [this message]
2010-08-19 14:39       ` Manuel Lauss
2010-08-19 14:48         ` Mark Brown
2010-08-19 14:58           ` Manuel Lauss
2010-08-19 15:17             ` Manuel Lauss
2010-08-19 15:52             ` Mark Brown
2010-08-19 15:59               ` Manuel Lauss
2010-08-19 16:06                 ` Mark Brown
2010-08-19 16:21                   ` Manuel Lauss

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=20100819143555.GB29453@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-devel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.