All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH][ASoC v2] Update Freescale MPC8610HPCD fabric driver to support multiple codecs
Date: Fri, 13 Jun 2008 07:11:59 -0500	[thread overview]
Message-ID: <4852640F.8050808@freescale.com> (raw)
In-Reply-To: <9e4733910806121957y3a8a15dawb50af2d2bb0d7d0b@mail.gmail.com>

Jon Smirl wrote:
> I've been out of the loop for a few months working on something else.
> I just looked at this driver. My understanding of the fabric driver is
> different than the way you implemented it. 

Well, my fabric driver does work, so it can't be that different. :-)

> I thought the fabric driver
> would only contain the essence of code specific to the board. 

No, the fabric driver also tells ASoC how the other three drivers are 
connected.  That is, it tells ASoC "please connect SSI1 to the codec at 
address 4F, and here's the DMA information that the SSI driver needs".

> In my model a lot of the code in your fabric driver would be pushed
> into the ssi driver. So if you used ssi and a codec in the standard
> manner, the board wouldn't need a fabric driver at all. That would
> probably be the case for most AC97/HDA systems.

The SSI driver is only concerned with talking to an SSI.  I don't see 
how you could get away with no fabric driver.  That just isn't the model.

> My fabric driver contains code for hooking processor GPIOs up to the
> codec, initializing an external clock generator, etc. All of the code
> for parsing the device tree and setting up DMA is in the ssi driver.

That's how my driver *used* to be.  With ASoC V2, I chose to move some 
of that code from the SSI driver into the fabric driver.  It just makes 
more sense to me.

  parent reply	other threads:[~2008-06-13 12:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13  0:01 [PATCH][ASoC v2] Update Freescale MPC8610HPCD fabric driver to support multiple codecs Timur Tabi
2008-06-13  2:22 ` Jon Smirl
2008-06-13 12:08   ` Timur Tabi
2008-06-13  2:57 ` Jon Smirl
2008-06-13  3:16   ` Jon Smirl
2008-06-13  3:36     ` Jon Smirl
2008-06-13 12:17       ` Timur Tabi
2008-06-13 15:04         ` Mark Brown
2008-06-13 15:10           ` Jon Smirl
2008-06-13 15:13             ` Timur Tabi
2008-06-13 15:26               ` Jon Smirl
2008-06-13 15:57                 ` Mark Brown
2008-06-13 16:59                   ` Jon Smirl
2008-06-13 18:40                     ` Timur Tabi
2008-06-13 18:59                     ` Mark Brown
2008-06-13 19:25                       ` Jon Smirl
2008-06-13 20:04                         ` Liam Girdwood
2008-06-13 22:42                           ` Mark Brown
2008-06-13 12:11   ` Timur Tabi [this message]
2008-06-13 13:42   ` Mark Brown
2008-06-13 14:10     ` Jon Smirl
2008-06-13 14:26       ` Timur Tabi
2008-06-13 14:29         ` Jon Smirl
2008-06-13 14:32           ` Timur Tabi
2008-06-13 14:36             ` Jon Smirl
2008-06-13 14:39               ` Timur Tabi
2008-06-13  9:53 ` 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=4852640F.8050808@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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.