From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Jaska Uimonen <jaska.uimonen@intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: SOF: define INFO_ flags in dsp_ops
Date: Thu, 24 Oct 2019 12:49:43 +0100 [thread overview]
Message-ID: <20191024114943.GC46373@sirena.co.uk> (raw)
In-Reply-To: <20191022193955.21766-2-pierre-louis.bossart@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 329 bytes --]
On Tue, Oct 22, 2019 at 02:39:54PM -0500, Pierre-Louis Bossart wrote:
> Currently the INFO_ flags such as PAUSE/NO_PERIOD_WAKEUP are defined
> in the SOF PCM core, which doesn't scale. To account for platform
> variations, these flags need to be set in DSP ops.
This doesn't apply against current code, please check and resend.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-24 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 19:39 [alsa-devel] [PATCH 0/2] ASoC: SOF: make hw_info platform specific Pierre-Louis Bossart
2019-10-22 19:39 ` [alsa-devel] [PATCH 1/2] ASoC: SOF: define INFO_ flags in dsp_ops Pierre-Louis Bossart
2019-10-24 11:49 ` Mark Brown [this message]
2019-10-22 19:39 ` [alsa-devel] [PATCH 2/2] ASoC: SOF: Intel: only support INFO_BATCH for legacy platforms Pierre-Louis Bossart
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=20191024114943.GC46373@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jaska.uimonen@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
/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