All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Grazvydas Ignotas <notasas@gmail.com>
Subject: Re: [PATCH 3/3] ASoC: omap-mcbsp: Add period size protection mode
Date: Wed, 21 Mar 2012 11:46:12 +0200	[thread overview]
Message-ID: <4F69A364.6050206@ti.com> (raw)
In-Reply-To: <4F69A08B.5080100@bitmer.com>

On 03/21/2012 11:34 AM, Jarkko Nikula wrote:
> On 03/21/2012 11:16 AM, Peter Ujfalusi wrote:
>> Agreed. Let's drop this patch, and try to figure out something which can
>> be used by other platforms as well.
>>
>> I would keep the first two patch in this series..
>>
> I acked already 1/3 but 2/3 needs commit log update and change below
> looks suspicious for omap1 and 2.

True, I'll update the commit log for patch 2.

> @@ -120,6 +120,9 @@ static int omap_mcbsp_dai_startup(struct
> snd_pcm_substream *substream,
>  	if (!cpu_dai->active)
>  		err = omap_mcbsp_request(mcbsp);
> 
> +	if (!mcbsp->pdata->buffer_size)
> +		return err;

We only need to set the constraints on OMAP versions which have FIFO. If
buffer_size is 0 we can just return without going forward.
It removes one level of nested code in the function.

-- 
Péter

      reply	other threads:[~2012-03-21  9:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 11:13 [PATCH 0/3] ASoC: omap-mcbsp: Constraint handling changes Peter Ujfalusi
2012-03-20 11:13 ` [PATCH 1/3] ASoC: omap-mcbsp: buffer size constraint only applies to playback stream Peter Ujfalusi
2012-03-20 15:26   ` Mark Brown
2012-03-20 16:34     ` Jarkko Nikula
2012-03-20 11:13 ` [PATCH 2/3] ASoC: omap-mcbsp: Restructure omap_mcbsp_dai_startup code Peter Ujfalusi
2012-03-20 15:27   ` Mark Brown
2012-03-20 11:13 ` [PATCH 3/3] ASoC: omap-mcbsp: Add period size protection mode Peter Ujfalusi
2012-03-20 16:01   ` Mark Brown
2012-03-20 16:15     ` Grazvydas Ignotas
2012-03-20 17:04       ` Mark Brown
2012-03-20 17:27         ` Grazvydas Ignotas
2012-03-20 18:07           ` Trent Piepho
2012-03-20 18:12           ` Mark Brown
2012-03-21  8:23       ` Peter Ujfalusi
2012-03-21 11:55         ` Grazvydas Ignotas
2012-03-20 16:20   ` Jarkko Nikula
2012-03-20 16:42     ` Grazvydas Ignotas
2012-03-20 19:20       ` Jarkko Nikula
2012-03-20 19:47         ` Trent Piepho
2012-03-21  7:57           ` Peter Ujfalusi
2012-03-21  8:13             ` Jarkko Nikula
2012-03-21  8:21               ` Peter Ujfalusi
2012-03-21  8:03     ` Peter Ujfalusi
2012-03-21  8:32       ` Jarkko Nikula
2012-03-21  8:40         ` Mark Brown
2012-03-21  9:16           ` Peter Ujfalusi
2012-03-21  9:34             ` Jarkko Nikula
2012-03-21  9:46               ` Peter Ujfalusi [this message]

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=4F69A364.6050206@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lrg@ti.com \
    --cc=notasas@gmail.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.