From: Ian Minett <ian_minett@creativelabs.com>
To: patch@alsa-project.org
Cc: alsa-devel@alsa-project.org, Ian Minett <ian_minett@creativelabs.com>
Subject: [PATCH 0/3] ALSA: Add DSP firmware loader
Date: Thu, 30 Aug 2012 13:21:03 -0700 [thread overview]
Message-ID: <1346358066-7851-1-git-send-email-ian_minett@creativelabs.com> (raw)
From: Ian Minett <ian_minett@creativelabs.com>
Hi Takashi,
Thanks for the recent code samples, they were very useful. We've built on them
to produce this latest patchset, incorporating the updates you provided to add the loader functions, and doing a minimal update to the CA0132 codec to use the new ops
to perform the firmware transfer.
Please let us know if any tweaks are needed to the update.
Thanks,
- Ian
Signed-off-by: Ian Minett <ian_minett@creativelabs.com>
---
1:
- memalloc.h
- pcm.h
- pcm_memory.c
- sgbuf.c
Include Takashi's updates:
Make snd_sgbuf_get_{ptr|addr}() available for non-SG cases.
Passing struct snd_dma_buffer pointer instead, so that they work no
matter whether real SG buffer is used or not.
2:
- hda_intel.c
- hda_codec.h
Include Takashi's updates:
Pass DMA buffer pointers in calls to setup_bdle().
Add new callback routines to controller to handle loading
firmware binaries.
Add new switch to Kconfig to enable DSP firmware loader.
3:
- patch_ca0132.c
- ca0132_regs.h
Add support for DSP firmware transfer to CA0132 codec:
Add transfer handler functions.
Call the new snd_hda_codec_load_dsp_xxx loader ops to control download.
Add chip access routines.
next reply other threads:[~2012-08-30 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 20:21 Ian Minett [this message]
2012-08-30 20:21 ` [PATCH 1/3] ALSA: Make snd_sgbuf_get_{ptr|addr}() available for non-SG cases Ian Minett
2012-08-30 20:21 ` [PATCH 2/3] ALSA: Add new DSP loader callback routines Ian Minett
2012-09-04 14:11 ` [PATCH 0/3] ALSA: Add DSP firmware loader 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=1346358066-7851-1-git-send-email-ian_minett@creativelabs.com \
--to=ian_minett@creativelabs.com \
--cc=alsa-devel@alsa-project.org \
--cc=patch@alsa-project.org \
/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).