From: timur@tabi.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 05/11] ASoC: fsl-ssi: Add support for imx-pcm-fiq
Date: Sun, 14 Apr 2013 08:37:21 -0500 [thread overview]
Message-ID: <516AB111.3000007@tabi.org> (raw)
In-Reply-To: <20130414103819.GA27394@pengutronix.de>
Markus Pargmann wrote:
> I do not think it is possible. For example imx27 ssi does support
> DMA but for specific boards we have to use fiq instead (phycore-ac97).
> So I would prefer to define the DMA in the chip dtsi file and choose
> fiq, if necessary, in the board dts.
I'm not completely familiar with the way i.MX SSI bindings work, but isn't
there some property that says, "this SSI needs to use this DMA channel"?
So if that property is missing, then it means that there's no link between
the SSI and a DMA channel, and so you need to use FIQ.
For example, for PowerPC bindings, we have this:
ssi at 16000 {
compatible = "fsl,mpc8610-ssi";
cell-index = <0>;
reg = <0x16000 0x100>;
interrupt-parent = <&mpic>;
interrupts = <62 2>;
fsl,mode = "i2s-slave";
codec-handle = <&cs4270>;
--> fsl,playback-dma = <&dma00>;
--> fsl,capture-dma = <&dma01>;
So on PowerPC, if these two properties are missing, then we would use
interrupt mode.
--
Timur Tabi
next prev parent reply other threads:[~2013-04-14 13:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 19:25 [PATCH v2 00/11] ASoC: fsl-ssi: ac97-slave support Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 01/11] ASoC: phycore-ac97: Add DT support Markus Pargmann
2013-04-08 2:52 ` Timur Tabi
2013-04-10 11:03 ` Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 02/11] ASoC: imx-pcm-dma: Add support for DMA init by device node Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 03/11] ASoC: imx-pcm-fiq: Introduce pcm-fiq-params Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 04/11] ASoC: fsl-ssi: Add SACNT definitions Markus Pargmann
2013-04-08 0:13 ` Timur Tabi
2013-04-07 19:25 ` [PATCH v2 05/11] ASoC: fsl-ssi: Add support for imx-pcm-fiq Markus Pargmann
2013-04-08 0:18 ` Timur Tabi
2013-04-14 10:38 ` Markus Pargmann
2013-04-14 13:37 ` Timur Tabi [this message]
2013-04-14 14:10 ` Markus Pargmann
2013-04-14 14:53 ` Timur Tabi
2013-04-14 15:20 ` Markus Pargmann
2013-04-14 15:25 ` Timur Tabi
2013-04-14 15:44 ` Markus Pargmann
2013-04-15 16:15 ` Mark Brown
2013-04-07 19:25 ` [PATCH v2 06/11] ASoC: fsl-ssi: Setup generic imx dma params Markus Pargmann
2013-04-08 2:50 ` Timur Tabi
2013-04-13 13:52 ` Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 07/11] ARM: imx: Export ac97 reset functions Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 08/11] ASoC: fsl-ssi: imx ac97 support Markus Pargmann
2013-04-08 2:49 ` Timur Tabi
2013-04-10 11:33 ` Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 09/11] ASoC: fsl: Kconfig: Use fsl-ssi for phycore-ac97 Markus Pargmann
2013-04-07 19:25 ` [PATCH v2 10/11] ASoC: fsl: Move fsl-ssi binding doc to sound/ Markus Pargmann
2013-04-08 0:20 ` Timur Tabi
2013-04-07 19:25 ` [PATCH v2 11/11] ASoC: fsl: Update fsl-ssi binding doc Markus Pargmann
2013-04-07 19:39 ` [alsa-devel] [PATCH v2 00/11] ASoC: fsl-ssi: ac97-slave support Lars-Peter Clausen
2013-04-07 20:08 ` Markus Pargmann
2013-04-07 20:35 ` Lars-Peter Clausen
2013-04-13 13:32 ` Markus Pargmann
2013-04-13 13:40 ` Lars-Peter Clausen
2013-04-13 13:55 ` Markus Pargmann
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=516AB111.3000007@tabi.org \
--to=timur@tabi.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).