linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>,
	liam.girdwood@wolfsonmicro.com, alsa-devel@alsa-project.org,
	linuxppc-dev@ozlabs.org, timur@freescale.com
Subject: Re: [alsa-devel] [PATCH 2/3] ALSA SoC: Add mpc5200-psc I2S driver
Date: Mon, 7 Jul 2008 09:23:24 -0400	[thread overview]
Message-ID: <9e4733910807070623u4c17b319p48e96a3022f3459b@mail.gmail.com> (raw)
In-Reply-To: <20080707105905.GA19240@rakim.wolfsonmicro.main>

On 7/7/08, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Sun, Jul 06, 2008 at 01:56:48PM -0400, Jon Smirl wrote:
>
>  > The driver is assuming a capture stream exists. My codec is output only.
>
>
> While the driver declares a capture stream the core doesn't require that
>  both capture and playback be available - it will cope with a capture
>  only or a playback only DAI (this is fairly common due to DAC only and
>  ADC only parts).  Unless there's some other issue specific to this
>  driver?

Yes, it GPFs allocating a a DMA buffer on the null capture stream pointer.

>
>  > I'm using external clocking, but the driver should support using the
>  > mpc5200 for clocking. That's a little complicated since you have to
>  > compute the divisors. For example the Phytec pcm030 board has a
>  > 33.3333Mhz xtal and runs at 400Mhz.
>
>
> This is desirable, though it shouldn't be an obstacle for merging if the
>  driver only supports running in slave mode.
>
>
>  > In order to reduce options, can the psc-i2s driver always try to use
>  > mpc5200 clocking, then let the codec or fabric driver override it?
>
>
> The clocking should always be under the control of the machine driver
>  with the codec and platform drivers exporting the required dividers and
>  PLLs/FLLs.  Neither the platform driver nor the codec driver are really
>  in a position to know how a given board is wired up and what
>  interdependencies or external requirements there are.
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2008-07-07 13:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 23:53 [PATCH 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Grant Likely
2008-07-01 23:53 ` [PATCH 2/3] ALSA SoC: Add mpc5200-psc I2S driver Grant Likely
2008-07-02 10:34   ` [alsa-devel] " Liam Girdwood
2008-07-02 13:51   ` Jon Smirl
2008-07-03 16:28     ` Grant Likely
2008-07-04 11:03       ` Timur Tabi
2008-07-04 14:41         ` Grant Likely
2008-07-05  1:28         ` David Gibson
2008-07-02 15:19   ` Jon Smirl
2008-07-03 16:30     ` Grant Likely
2008-07-06 17:56   ` Jon Smirl
2008-07-07 10:59     ` Mark Brown
2008-07-07 13:23       ` Jon Smirl [this message]
2008-07-12  6:26         ` Grant Likely
2008-07-07 16:32   ` Jon Smirl
2008-07-12  6:30     ` Grant Likely
2008-07-09  8:22   ` new to sound world
2008-07-01 23:53 ` [PATCH 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Grant Likely
2008-07-02 10:48   ` [alsa-devel] " Liam Girdwood
2008-07-12  6:00     ` Grant Likely
2008-07-12 17:36       ` Mark Brown
2008-07-12 18:13         ` Grant Likely
2008-07-17 23:31         ` Grant Likely
2008-07-18  9:58           ` Mark Brown
2008-07-18 16:14             ` Grant Likely
2008-07-02 13:52   ` Jon Smirl
2008-07-02 16:08     ` Liam Girdwood
2008-07-04 20:49   ` Mark Brown
2008-07-04 23:44     ` Grant Likely
2008-07-02  9:50 ` [alsa-devel] [PATCH 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Takashi Iwai
2008-07-02 15:48   ` Grant Likely
2008-07-02 15:57     ` Liam Girdwood
2008-07-02 13:50 ` Jon Smirl
2008-07-02 15:27 ` Jon Smirl
2008-07-03 16:33   ` Grant Likely
2008-07-04 11:05     ` 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=9e4733910807070623u4c17b319p48e96a3022f3459b@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=grant.likely@secretlab.ca \
    --cc=liam.girdwood@wolfsonmicro.com \
    --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 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).