From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/2] ASoC: Intel: Fix Baytrail SST DSP firmware loading
Date: Tue, 13 May 2014 10:22:08 +0300 [thread overview]
Message-ID: <5371C820.6010207@linux.intel.com> (raw)
In-Reply-To: <20140512220945.GA12304@sirena.org.uk>
On 05/13/2014 01:09 AM, Mark Brown wrote:
> On Fri, May 09, 2014 at 04:47:43PM +0300, Jarkko Nikula wrote:
>> Commit 10df350977b1 ("ASoC: Intel: Fix Audio DSP usage when IOMMU is
>> enabled.") caused following regression in Baytrail SST:
>>
>> baytrail-pcm-audio baytrail-pcm-audio: error: DMA alloc failed
>> baytrail-pcm-audio baytrail-pcm-audio: error: failed to load firmware
> Is this needed on fix/intel? If so it doesn't apply there...
Indeed it doesn't. I accidentally made it on top of my suspend/resume
set and it appears to conflict without [PATCH 4/7] ASoC: Intel: Move
Baytrail extended fw address saving to sst_byt_boot()".
In case you are thinking to queue Liam's 10df350977b1 as a fix Is it ok
if I resend this on top of it and handle conflict when merging
origin/topic/intel?
--
Jarkko
next prev parent reply other threads:[~2014-05-13 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 13:47 [PATCH 1/2] ASoC: Intel: Fix Baytrail SST DSP firmware loading Jarkko Nikula
2014-05-09 13:47 ` [PATCH 2/2] ASoC: Intel: Use ACPI device for Baytrail PCM buffer allocation Jarkko Nikula
2014-05-12 22:10 ` Mark Brown
2014-05-13 7:30 ` Jarkko Nikula
2014-05-13 10:54 ` Mark Brown
2014-05-12 22:09 ` [PATCH 1/2] ASoC: Intel: Fix Baytrail SST DSP firmware loading Mark Brown
2014-05-13 7:22 ` Jarkko Nikula [this message]
2014-05-13 10:53 ` Mark Brown
2014-05-13 12:46 ` [PATCHv2] " Jarkko Nikula
2014-05-13 17:21 ` Mark Brown
2014-05-13 17:26 ` [PATCH 1/2] " Mark Brown
2014-05-14 6:18 ` Jarkko Nikula
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=5371C820.6010207@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.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