From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH v3 2/3] ASoC: soc-dapm: API to attach DAPM_SUPPLY to be used for dai
Date: Fri, 26 Aug 2011 20:05:02 +0100 [thread overview]
Message-ID: <20110826190420.GA2943@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1314365603-8947-3-git-send-email-peter.ujfalusi@ti.com>
On Fri, Aug 26, 2011 at 04:33:22PM +0300, Peter Ujfalusi wrote:
> There are cpu dais, which require special ordering during stream
> stop (OMAP4's McPDM interface for example) in a system level.
> OMAP4 McPDM required to be stopped after the attached codec's
> (twl6040) DAC/ADC has been stopped.
> This requironment can be solved with a use of DAPM_SUPPLY
> widget attached to the codec's ADC/DAC from machine driver.
This wasn't really what I meant - what I meant was that we ought to be
able to change the ordering of DAPM with regard to the stream shutdown
without having to have anything more than flags in the devices that can
or need to do it (I'd expect more the CODECs more than the CPUs).
next prev parent reply other threads:[~2011-08-26 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 13:33 [PATCH v3 0/3] ASoC: omap-mcpdm: New McPDM driver Peter Ujfalusi
2011-08-26 13:33 ` [PATCH v3 1/3] ASoC: DAPM: Add private data pointer for DAPM widget Peter Ujfalusi
2011-08-26 13:33 ` [PATCH v3 2/3] ASoC: soc-dapm: API to attach DAPM_SUPPLY to be used for dai Peter Ujfalusi
2011-08-26 19:05 ` Mark Brown [this message]
2011-08-29 8:22 ` Péter Ujfalusi
2011-08-29 9:16 ` Mark Brown
2011-08-29 11:41 ` Péter Ujfalusi
2011-09-03 6:31 ` Mark Brown
2011-09-06 10:21 ` Péter Ujfalusi
2011-09-06 15:09 ` Mark Brown
2011-08-26 13:33 ` [PATCH v3 3/3] ASoC: omap-mcpdm: Replace legacy driver 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=20110826190420.GA2943@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 \
/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).