linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: liam.girdwood@wolfsonmicro.com, alsa-devel@alsa-project.org,
	broonie@opensource.wolfsonmicro.com, timur@freescale.com,
	linuxppc-dev@ozlabs.org
Subject: Re: [alsa-devel] [PATCH 2/3] ALSA SoC: Add mpc5200-psc I2S driver
Date: Thu, 3 Jul 2008 10:28:09 -0600	[thread overview]
Message-ID: <20080703162809.GH2284@secretlab.ca> (raw)
In-Reply-To: <9e4733910807020651u368763en9362653ed613b2d1@mail.gmail.com>

On Wed, Jul 02, 2008 at 09:51:59AM -0400, Jon Smirl wrote:
> DMA, needs to be split out. Efika is AC97 on the MPC5200 and needs to
> share DMA code. The new Phytec pcm030 baseboard is AC97 too.

I agree, but I'm not sure the best way to organize a split.  I'm not
doing anything with the Efika at the moment and I haven't dug into the
details of what needs to be done for AC97.

> What does the device tree look like?

Here is the relevant excerpt, but it is not documented yet.  I haven't
made any attempt encode the layout into the device tree (clocking, etc.)

	spi@f00 {
		#address-cells = <1>;
		#size-cells = <0>;
		compatible = "fsl,mpc5200b-spi","fsl,mpc5200-spi";
		reg = <0xf00 0x20>;
		num-slaves = <32>;
		interrupts = <2 13 0 2 14 0>;
		interrupt-parent = <&mpc5200_pic>;

		codec1: codec@2 {
			compatible = "ti,tlv320aic26";
			linux,modalias = "tlv320aic26";
			max-speed = <1000000>;
			reg = <2>;
		};

		codec2: codec@3 {
			compatible = "ti,tlv320aic26";
			linux,modalias = "tlv320aic26";
			max-speed = <1000000>;
			reg = <3>;
		};
	};

	i2s@2200 {		// PSC2
		compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s";
		cell-index = <1>;
		reg = <0x2200 0x100>;
		interrupts = <2 2 0>;
		interrupt-parent = <&mpc5200_pic>;
		codec-handle = <&codec1>;
	};
	i2s@2400 {		// PSC3
		compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s";
		cell-index = <2>;
		reg = <0x2400 0x100>;
		interrupts = <2 3 0>;
		interrupt-parent = <&mpc5200_pic>;
		codec-handle = <&codec2>;
	};

  reply	other threads:[~2008-07-03 16:28 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 [this message]
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
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=20080703162809.GH2284@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jonsmirl@gmail.com \
    --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).