From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>
Cc: alsa-devel@alsa-project.org, Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
devicetree-discuss@lists.ozlabs.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/9] ARM: OMAP: mcbsp: Enable FIFO use for OMAP2430
Date: Fri, 17 Aug 2012 17:03:23 +0300 [thread overview]
Message-ID: <502E4F2B.6060403@ti.com> (raw)
In-Reply-To: <502E43BC.30708@bitmer.com>
On 08/17/2012 04:14 PM, Jarkko Nikula wrote:
> On 08/17/2012 04:07 PM, Tony Lindgren wrote:
>> * Peter Ujfalusi <peter.ujfalusi@ti.com> [120816 06:41]:
>>> On OMAP2430 all McBSP ports have 128 word long buffer, enable the use of
>>> the FIFO for the audio stack.
>> Is this the case also for 2420? I thought some only had a FIFO at
>> one port?
>>
> IRCC (I don't have specs), nope. Only 2430 (as noted by Peter) and
> onwards have FIFO.
>
> But that's true that FIFO sizes differ between the ports. E.g. only
> ports 2 and 3 have 1024+128 deep FIFOs in OMAP3.
>
OMAP2420 McBSP does not have FIFO (the IP is closer to OMAP1 McBSP).
OMAP2430, OMAP4, OMAP5 has 128 word long FIFO on all McBSP ports.
On OMAP3: McBSP2 have 1024+256 (1280) word FIFO the rest of the ports have 128
long FIFO.
--
Péter
WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/9] ARM: OMAP: mcbsp: Enable FIFO use for OMAP2430
Date: Fri, 17 Aug 2012 17:03:23 +0300 [thread overview]
Message-ID: <502E4F2B.6060403@ti.com> (raw)
In-Reply-To: <502E43BC.30708@bitmer.com>
On 08/17/2012 04:14 PM, Jarkko Nikula wrote:
> On 08/17/2012 04:07 PM, Tony Lindgren wrote:
>> * Peter Ujfalusi <peter.ujfalusi@ti.com> [120816 06:41]:
>>> On OMAP2430 all McBSP ports have 128 word long buffer, enable the use of
>>> the FIFO for the audio stack.
>> Is this the case also for 2420? I thought some only had a FIFO at
>> one port?
>>
> IRCC (I don't have specs), nope. Only 2430 (as noted by Peter) and
> onwards have FIFO.
>
> But that's true that FIFO sizes differ between the ports. E.g. only
> ports 2 and 3 have 1024+128 deep FIFOs in OMAP3.
>
OMAP2420 McBSP does not have FIFO (the IP is closer to OMAP1 McBSP).
OMAP2430, OMAP4, OMAP5 has 128 word long FIFO on all McBSP ports.
On OMAP3: McBSP2 have 1024+256 (1280) word FIFO the rest of the ports have 128
long FIFO.
--
P?ter
next prev parent reply other threads:[~2012-08-17 14:03 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 13:40 [PATCH v3 0/9] ARM/ASoC: OMAP McBSP device tree support Peter Ujfalusi
2012-08-16 13:40 ` Peter Ujfalusi
2012-08-16 13:41 ` [PATCH v3 1/9] ARM/ASoC: omap-mcbsp: Move OMAP2+ clock parenting code to ASoC driver Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:06 ` Tony Lindgren
2012-08-17 13:06 ` Tony Lindgren
2012-08-22 19:10 ` Mark Brown
2012-08-22 19:10 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 2/9] ARM: OMAP: mcbsp: Enable FIFO use for OMAP2430 Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:07 ` Tony Lindgren
2012-08-17 13:07 ` Tony Lindgren
2012-08-17 13:14 ` Jarkko Nikula
2012-08-17 13:14 ` Jarkko Nikula
2012-08-17 14:03 ` Peter Ujfalusi [this message]
2012-08-17 14:03 ` Peter Ujfalusi
2012-08-18 6:08 ` Tony Lindgren
2012-08-18 6:08 ` Tony Lindgren
2012-08-18 15:58 ` Ujfalusi, Peter
2012-08-18 15:58 ` Ujfalusi, Peter
2012-08-20 6:57 ` Tony Lindgren
2012-08-20 6:57 ` Tony Lindgren
2012-08-22 19:11 ` Mark Brown
2012-08-22 19:11 ` Mark Brown
2012-08-22 21:01 ` Tony Lindgren
2012-08-22 21:01 ` Tony Lindgren
2012-08-16 13:41 ` [PATCH v3 3/9] ARM: OMAP: board-am3517evm: Configure McBSP1 CLKR/FSR signal source Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:07 ` Tony Lindgren
2012-08-17 13:07 ` Tony Lindgren
2012-08-22 19:12 ` Mark Brown
2012-08-22 19:12 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 4/9] ASoC: am3517evm: Do not configure McBSP1 CLKR/FSR signal muxing Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:08 ` Tony Lindgren
2012-08-17 13:08 ` Tony Lindgren
2012-08-22 19:13 ` Mark Brown
2012-08-22 19:13 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 5/9] ARM/ASoC: omap-mcbsp: Remove CLKR/FSR mux configuration code Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:08 ` Tony Lindgren
2012-08-17 13:08 ` Tony Lindgren
2012-08-22 19:15 ` Mark Brown
2012-08-22 19:15 ` Mark Brown
2012-08-23 8:12 ` Peter Ujfalusi
2012-08-23 8:12 ` Peter Ujfalusi
2012-08-16 13:41 ` [PATCH v3 6/9] ASoC: omap-mcbsp: Remove unused defines Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-22 19:15 ` Mark Brown
2012-08-22 19:15 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 7/9] ASoC: omap-mcbsp: Remove cpu_is_omap* checks from the code Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-22 19:15 ` Mark Brown
2012-08-22 19:15 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 8/9] ARM: OMAP2+: McBSP: Do not create legacy devices when booting with DT data Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-17 13:09 ` Tony Lindgren
2012-08-17 13:09 ` Tony Lindgren
2012-08-22 19:16 ` Mark Brown
2012-08-22 19:16 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 9/9] ASoC: omap-mcbsp: Add device tree bindings Peter Ujfalusi
2012-08-16 13:41 ` Peter Ujfalusi
2012-08-22 19:16 ` Mark Brown
2012-08-22 19:16 ` Mark Brown
2012-08-17 10:18 ` [PATCH v3 0/9] ARM/ASoC: OMAP McBSP device tree support Mark Brown
2012-08-17 10:18 ` Mark Brown
2012-08-17 13:10 ` Tony Lindgren
2012-08-17 13:10 ` Tony Lindgren
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=502E4F2B.6060403@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=tony@atomide.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.