From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAP4: mcbsp: Enable FIFO usage
Date: Fri, 16 Dec 2011 09:36:00 -0800 [thread overview]
Message-ID: <20111216173600.GB32251@atomide.com> (raw)
In-Reply-To: <1323941547-7714-2-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [111215 01:01]:
> All McBSP instances on OMAP4 has 128 word long FIFO
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Please merge via ASoC tree:
Acked-by: Tony Lindgren <tony@atomide.com>
> ---
> arch/arm/mach-omap2/mcbsp.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/mcbsp.c b/arch/arm/mach-omap2/mcbsp.c
> index 292eee3..857860b 100644
> --- a/arch/arm/mach-omap2/mcbsp.c
> +++ b/arch/arm/mach-omap2/mcbsp.c
> @@ -153,6 +153,9 @@ static int omap_init_mcbsp(struct omap_hwmod *oh, void *unused)
> else
> /* The FIFO has 128 locations */
> pdata->buffer_size = 0x80;
> + } else if (oh->class->rev == MCBSP_CONFIG_TYPE4) {
> + /* The FIFO has 128 locations for all instances */
> + pdata->buffer_size = 0x80;
> }
>
> if (oh->class->rev >= MCBSP_CONFIG_TYPE3)
> --
> 1.7.8
>
next prev parent reply other threads:[~2011-12-16 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 9:32 [PATCH 0/2] OMAP4: McBSP: ASoC: Fix FIFO configuration Peter Ujfalusi
2011-12-15 9:32 ` [PATCH 1/2] OMAP4: mcbsp: Enable FIFO usage Peter Ujfalusi
2011-12-16 17:36 ` Tony Lindgren [this message]
2011-12-17 9:24 ` Mark Brown
2011-12-15 9:32 ` [PATCH 2/2] ASoC: omap-mcbsp: Enable FIFO usage on OMAP4 Peter Ujfalusi
2011-12-17 9:32 ` 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=20111216173600.GB32251@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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).