From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [RFC 1/2] ASoC: soc-pcm: Add flag to ignore pmdown_time at pcm_close
Date: Fri, 14 Oct 2011 12:24:01 +0300 [thread overview]
Message-ID: <10992537.0jJ7E3VM1G@barack> (raw)
In-Reply-To: <20111013140003.GM1098@sirena.org.uk>
On Thursday 13 October 2011 15:00:03 Mark Brown wrote:
> On Thu, Oct 13, 2011 at 04:23:34PM +0300, Peter Ujfalusi wrote:
> > With this flag machine drivers can indicate that it is desired
> > to ignore the pmdown_time for DAPM shutdown sequence when
> > playback stream is stopped.
> > The DAPM sequence will be executed without delay in this case.
>
> Why make this a per-machine control? This seems like it'd be a property
> of the CODEC or possibly other chips rather than a machine specific thing?
I thought that depending on the environment we might need this or not for the
same component, and the best place for this is to be able to define it per dai
link.
However I can move the flag as per codec configuration (within snd_soc_codec
struct). Would that be better?
--
Péter
next prev parent reply other threads:[~2011-10-14 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:23 [RFC 0/2] ASoC: core: Ignoring pmdown_time for playback stream power down Peter Ujfalusi
2011-10-13 13:23 ` [RFC 1/2] ASoC: soc-pcm: Add flag to ignore pmdown_time at pcm_close Peter Ujfalusi
2011-10-13 14:00 ` Mark Brown
2011-10-14 9:24 ` Péter Ujfalusi [this message]
2011-10-14 9:38 ` Mark Brown
2011-10-14 10:27 ` Péter Ujfalusi
2011-10-13 13:23 ` [RFC 2/2] ASoC: sdp4430: Request core to inline the DAPM sequence Peter Ujfalusi
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=10992537.0jJ7E3VM1G@barack \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=misael.lopez@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 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.