All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8610HPCD sound as module
Date: Thu, 11 Dec 2008 15:31:59 +0000	[thread overview]
Message-ID: <20081211153158.GF30808@sirena.org.uk> (raw)
In-Reply-To: <ed82fe3e0812110712r4baeea60ied52937aa434f48e@mail.gmail.com>

On Thu, Dec 11, 2008 at 09:12:54AM -0600, Timur Tabi wrote:
> On Thu, Dec 11, 2008 at 7:18 AM, Peter Czanik <pczanik@fang.fa.gau.hu> wrote:

> > As far as I can see from comments in the sources, it should work also as
> > a module. Any hints how to achieve that?

> The ASoC V2 version of the driver supports loading as a module.  ASoC
> V1 does not support loading sound drivers as modules, which is why I
> didn't implement that support in the V1 drivers.  The 2.6.27 kernel

ASoC v1 supports loading drivers as modules (and this is fairly heavily
used), though as you say the MPC8610 drivers don't support that.

> has ASoC V1.  ASoC V2 won't be integrated into the mainline until at
> least 2.6.29, and maybe even 2.6.30.  The ASoC V2 repository is
> available at http://opensource.wolfsonmicro.com/cgi-bin/gitweb.cgi?p=linux-2.6-asoc.git
> under the asoc-v2-dev branch.

At the minute there's code queued for merge which defers card
instantiation until DAIs and platforms have registered, allowing the
various parts of the system to probe through the normal mechanisms.
That's the most substantial of the outstanding changes.

  reply	other threads:[~2008-12-11 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 13:18 MPC8610HPCD sound as module Peter Czanik
2008-12-11 15:12 ` Timur Tabi
2008-12-11 15:31   ` Mark Brown [this message]
2008-12-11 15:40     ` Timur Tabi
2008-12-11 15:44       ` Mark Brown
2008-12-11 15:45         ` Timur Tabi
2008-12-11 18:52           ` Mark Brown
2008-12-11 19:17             ` Timur Tabi

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=20081211153158.GF30808@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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 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.