From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Nallasellan, Singaravelan" <singaravelan.nallasellan@intel.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
"Babu, Ramesh" <ramesh.babu@intel.com>,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH v2 1/2] ASoC: core: Add flag to ignore pmdown_time at pcm_close
Date: Sat, 22 Oct 2011 10:33:26 +0100 [thread overview]
Message-ID: <20111022093326.GA2890@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C8CB9611@bgsmsx502.gar.corp.intel.com>
On Sat, Oct 22, 2011 at 01:54:23AM +0530, Nallasellan, Singaravelan wrote:
When I said you shouldn't top post that's exactly what I meant! This is
basic mailing list etiquette for public Linux lists because for
example...
> Agree. System integrator may not like to delay closing modem ports for 6 seconds either. Need to close the ports immediately or delay.
...not having any context quoted means the reader can't easily tell wht
it is that you are agreeing with. You should also fix your mail client
to word wrap within paragraphs as I also mentioned.
> Do you suggest that we shouldn't delay in the driver and introduce delay in the user pace?
> I prefer to remove the delay altogether from the driver. Do you see any issue which might cause glitches?
The delay is very important for CPU use cases as brief gaps in playback
are extremely common there. The power up and power down are generally
noticable and to be avoided.
next prev parent reply other threads:[~2011-10-22 9:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:43 [PATCH v2 0/2] ASoC: core: Ignoring pmdown_time for playback stream power down Peter Ujfalusi
2011-10-14 11:43 ` [PATCH v2 1/2] ASoC: core: Add flag to ignore pmdown_time at pcm_close Peter Ujfalusi
2011-10-21 6:12 ` Babu, Ramesh
2011-10-21 8:53 ` Mark Brown
2011-10-21 9:10 ` Babu, Ramesh
2011-10-21 9:13 ` Mark Brown
2011-10-21 10:58 ` Babu, Ramesh
2011-10-21 11:26 ` Vinod Koul
2011-10-21 17:01 ` Nallasellan, Singaravelan
2011-10-21 19:41 ` Mark Brown
2011-10-21 20:24 ` Nallasellan, Singaravelan
2011-10-22 9:33 ` Mark Brown [this message]
2011-10-22 9:45 ` Mark Brown
2011-10-22 17:17 ` Vinod Koul
2011-10-23 14:00 ` Mark Brown
2011-10-24 2:55 ` Vinod Koul
2011-10-14 11:43 ` [PATCH v2 2/2] ASoC: twl6040: Request core to inline the DAPM sequence Peter Ujfalusi
2011-10-14 19:44 ` [PATCH v2 0/2] ASoC: core: Ignoring pmdown_time for playback stream power down 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=20111022093326.GA2890@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ramesh.babu@intel.com \
--cc=singaravelan.nallasellan@intel.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).