All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Re: Dynamically registering a codec
Date: Thu, 14 May 2009 19:38:51 +0100	[thread overview]
Message-ID: <20090514183850.GA13483@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <9e4733910905141057t64c515a2n8473a26da852fdfd@mail.gmail.com>

On Thu, May 14, 2009 at 01:57:37PM -0400, Jon Smirl wrote:

> Now I see what you mean. I need to make the codec into a device so
> that I can dynamically load and find it. On PowerPC the codecs don't
> have to be compiled in, they can be on an initrd.

This is the case for all platforms, it's not in any way PowerPC specific.

>                                                   The code in
> of_simple will find the right driver and get it into memory. The
> platform device is what triggers the kernel to go searching for the
> module on initrd.

On every other platform the codec driver is linked to directly by the
machine driver so loading the machine driver will also cause the codec
driver to be loaded - at this stage of_simple isn't involved at all
except in that it has removed the usual way of getting the codec driver
loaded for AC97 devices.

> This isn't platform specific, other platforms could implement this but
> they don't have anything like a device tree telling them which modules
> to load. A device tree is a probing mechanism for devices that can't
> be probed.

Other platforms use platform devices in just the same way, they just
happen to set them up in a C file rather than a .dts file.  The
mechanisms for loading things after that are identical.  What's PowerPC
specific here is that you are trying to use this of-simple mechainsm and
that's defeating the way this is handled for AC97 codec drivers.

Please re-read my comments about the specific problems with AC97 - this
is key here.

  parent reply	other threads:[~2009-05-14 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 19:18 Dynamically registering a codec Jon Smirl
2009-05-13 22:44 ` Mark Brown
2009-05-14 15:44   ` Jon Smirl
2009-05-14 16:15     ` Mark Brown
2009-05-14 16:43       ` Jon Smirl
2009-05-14 17:40         ` Mark Brown
2009-05-14 17:57           ` Jon Smirl
2009-05-14 18:15             ` Jon Smirl
2009-05-14 18:49               ` Mark Brown
2009-05-14 18:38             ` Mark Brown [this message]
2009-05-14 18:56               ` Jon Smirl
2009-05-14 19:13                 ` Mark Brown

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=20090514183850.GA13483@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonsmirl@gmail.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.