From: Dylan Reid <dgreid@chromium.org>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, Dylan Reid <dgreid@chromium.org>,
chee_kin@ctl.creative.com, ian_minett@creativelabs.com
Subject: [PATCH 0/3] ALSA: hda/ca0132 - Better handle a failed DSP firmware load.
Date: Thu, 14 Mar 2013 17:27:43 -0700 [thread overview]
Message-ID: <1363307266-30055-1-git-send-email-dgreid@chromium.org> (raw)
Enabling CONFIG_SND_HDA_CODEC_CA0132_DSP on the Chromebook Pixel leads
to 10+ a second delay between running aplay and hearing audio. This
was caused by the driver thinking the DSP was loaded when it had
actually failed. The first two patches avoid that situation, the DSP
still fails to load every time, but at least the system continues
without a painful delay. The third patch is just a cleanup that
touches the same state variable.
Dylan Reid (3):
ALSA: hda/ca0132 - Check if dspload_image succeeded.
ALSA: hda/ca0132 - Check download state of DSP.
ALSA: hda/ca0132 - Remove extra setting of dsp_state.
sound/pci/hda/patch_ca0132.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
--
1.8.1.3.605.g02339dd
next reply other threads:[~2013-03-15 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 0:27 Dylan Reid [this message]
2013-03-15 0:27 ` [PATCH 1/3] ALSA: hda/ca0132 - Check if dspload_image succeeded Dylan Reid
2013-03-15 0:27 ` [PATCH 2/3] ALSA: hda/ca0132 - Check download state of DSP Dylan Reid
2013-03-15 0:27 ` [PATCH 3/3] ALSA: hda/ca0132 - Remove extra setting of dsp_state Dylan Reid
2013-03-15 6:46 ` [PATCH 0/3] ALSA: hda/ca0132 - Better handle a failed DSP firmware load Takashi Iwai
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=1363307266-30055-1-git-send-email-dgreid@chromium.org \
--to=dgreid@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=chee_kin@ctl.creative.com \
--cc=ian_minett@creativelabs.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;
as well as URLs for NNTP newsgroup(s).