public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "anuj.aggarwal@ti.com" <anuj.aggarwal@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Wang, Jane" <jwang@ti.com>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix
Date: Fri, 20 Nov 2009 09:51:13 +0200	[thread overview]
Message-ID: <200911200951.13181.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <2ee9e08d0911191148x9da6112s960a283a7cffea7b@mail.gmail.com>

On Thursday 19 November 2009 21:48:26 ext Anuj Aggarwal wrote:
> [Anuj] Yes, w/o audio, it goes into suspend neatly.
> After going through the entire patch series "[PATCHv5 00/20] OMAP
> ASoC changes in DMA utilization", which I missed earlier, I found that the
> sysfs entry dma_op_mode can be toggled among element/frame/threshold,
> by default which is element hence not allowing the mcbsp driver to go into
> idle state. I changed that at run time and after that I am able to hit
> the suspend
> state while playing back audio (at least the log doesn't
> show that the system is not able to hit suspend).
> My question is: is sysfs the only way to choose threshold or can it be made
>  as default? I could not see that happening in the code so thinking of the
>  possible reason of choosing not to do so. Because the user who wants to
>  hit suspend will not like to issue driver specific commands. Any specific
>  reason of not doing that by default?

It is not selected as default on OMAP3, since it is a new feature, and we don't 
want to change the behavior of the audio. If the reports are positive regarding 
to the threshold mode, than we can make it as default on OMAP3, at least that is 
the plan AFAIK. 
In some cases the element mode is desirable over the threshold mode, and 
probably there are additional modes can be implemented for other cases, hence 
the sysfs interface is really useful feature.

Back than there were quite a bit of discussion here about the threshold mode: in 
the original series the threshold mode was the default, but we decided to not to 
do that before others have the chance to test it. We have been using the 
threshold mode without issues internally, so it should be really stable, but it 
is still a new mode, which can break other implementations.

So please test the threshold mode in your HW, and report if it is working there 
OK, if we have enough positive feedbacks, than we can make it as default.

-- 
Péter

  reply	other threads:[~2009-11-20  7:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 17:39 [PATCH 1/2] OMAP3: MCBSP: Suspend/resume failure fix Jane Wang
2009-11-13 17:49 ` Mark Brown
2009-11-13 17:52   ` Wang, Jane
2009-11-13 18:10     ` [alsa-devel] " Mark Brown
2009-11-14  8:20 ` Jarkko Nikula
2009-11-18 18:28   ` Aggarwal, Anuj
2009-11-18 18:49     ` Wang, Jane
2009-11-19  7:34     ` Jarkko Nikula
2009-11-19 19:48       ` Anuj Aggarwal
2009-11-20  7:51         ` Peter Ujfalusi [this message]
2009-11-20 13:53           ` Jarkko Nikula
2009-11-20 14:09             ` Eero Nurkkala
2009-11-20 14:47               ` [alsa-devel] " Anuj Aggarwal
2009-11-30 11:50                 ` Aggarwal, Anuj
2009-12-24 13:16                 ` Aggarwal, Anuj
2009-12-28  6:10                   ` Aggarwal, Anuj

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=200911200951.13181.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anuj.aggarwal@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jwang@ti.com \
    --cc=linux-omap@vger.kernel.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