From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: vinod.koul@intel.com, alsa-devel@alsa-project.org,
Lars-Peter Clausen <lars@metafoo.de>,
lgirdwood@gmail.com
Subject: Re: [alsa-devel] [PATCH v6 04/10] ASoC: Intel: mfld-pcm: add control for powering up/down dsp
Date: Wed, 17 Sep 2014 16:26:47 +0530 [thread overview]
Message-ID: <20140917105646.GB13006@vinod.koul@linux.intel.com> (raw)
In-Reply-To: <20140916190343.GC7960@sirena.org.uk>
On Tue, Sep 16, 2014 at 12:03:43PM -0700, Mark Brown wrote:
> On Tue, Sep 09, 2014 at 03:11:27PM +0530, Subhransu S. Prusty wrote:
>
> > @@ -129,6 +129,7 @@ struct sst_ops {
> > int (*stream_read_tstamp) (struct device *dev, struct pcm_stream_info *str_info);
> > int (*send_byte_stream)(struct device *dev, struct snd_sst_bytes_v2 *bytes);
> > int (*close) (struct device *dev, unsigned int str_id);
> > + int (*power)(struct device *dev, bool state);
>
> These seem to have a mix of )( and ) ( - it was a preexisting problem
> but still...
Will fix.
--
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-09-17 11:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 9:41 [PATCH v6 00/10] Add mrfld DSP topology and widgets Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 01/10] ASoC: Intel: mfld-pcm: don't call trigger ops to DSP for internal streams Subhransu S. Prusty
2014-09-16 18:54 ` Mark Brown
2014-09-09 9:41 ` [PATCH v6 02/10] ASoC: Intel: mrfld: add bytes control for modules Subhransu S. Prusty
2014-09-16 18:50 ` Mark Brown
2014-09-16 18:55 ` Mark Brown
2014-09-09 9:41 ` [PATCH v6 03/10] ASoC: Intel: mrfld: add the gain controls Subhransu S. Prusty
2014-09-16 19:00 ` Mark Brown
2014-09-09 9:41 ` [PATCH v6 04/10] ASoC: Intel: mfld-pcm: add control for powering up/down dsp Subhransu S. Prusty
2014-09-16 19:03 ` Mark Brown
2014-09-17 10:56 ` Subhransu S. Prusty [this message]
2014-09-17 10:56 ` Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 05/10] ASoC: Intel: mrfld: add DSP core controls Subhransu S. Prusty
2014-09-16 19:30 ` Mark Brown
2014-09-17 10:55 ` [alsa-devel] " Subhransu S. Prusty
2014-09-17 19:37 ` Mark Brown
2014-09-18 6:12 ` Vinod Koul
2014-09-18 17:28 ` Mark Brown
2014-09-19 8:10 ` Vinod Koul
2014-09-19 8:21 ` Vinod Koul
2014-09-23 1:57 ` Mark Brown
2014-09-23 3:52 ` Vinod Koul
2014-09-17 10:55 ` Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 06/10] ASoC: Export dapm_kcontrol_get_value Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 07/10] ASoC: Intel: mrfld: add the DSP DAPM widgets Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 08/10] ASoC: Intel: mfld-pcm: add FE and BE ops Subhransu S. Prusty
2014-09-09 9:41 ` [PATCH v6 09/10] ASoC: Intel: mrfld: Use snd_soc_dai_get_drvdata to derive drv data Subhransu S. Prusty
2014-09-16 23:40 ` Mark Brown
2014-09-09 9:41 ` [PATCH v6 10/10] ASoC: Intel: mrfld: add the DSP mixers Subhransu S. Prusty
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=20140917105646.GB13006@vinod.koul@linux.intel.com \
--to=subhransu.s.prusty@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=vinod.koul@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).