From: Patrick Lai <plai@codeaurora.org>
To: alsa-devel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, lrg@slimlogic.co.uk,
broonie@opensource.wolfsonmicro.com
Subject: [QUERY] Download calibration data to co-processor
Date: Mon, 24 Jan 2011 22:13:33 -0800 [thread overview]
Message-ID: <4D3E6A0D.40308@codeaurora.org> (raw)
Hi,
I am looking for ways to download audio calibration data to a
co-processor under ALSA framework. I would like to know if there is
already a precedent which handles this use case. I considered
request_firmware() approach but there are few drawbacks to this
approach. The audio calibration data size can be substantial
as number of audio use cases grows. It also requires co-processor
perform extensive parsing of data. Furthermore, host processor and
co-processor need to establish common use case definitions so
co-processor know what chunk of calibration data to apply in certain
scenario such as device switch.
If there is no precedent, my idea is to apply calibration data through
sysfs. After introduction of ASoC multi-component architecture, PCM
stream created from dailink is registered as device. So, there is syfs
entry for each dailink. If ALSA ASoC can provide API for
drivers(platform/CPU) to register additional attributes to the PCM
device, this approach gives user-space application the ability to push
down new calibration as audio situation changes. I believe it's a viable
solution to my problem and perhaps can be useful to other systems as well.
Your feedback is appreciated.
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2011-01-25 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 6:13 Patrick Lai [this message]
2011-01-25 13:36 ` [QUERY] Download calibration data to co-processor Mark Brown
2011-01-26 7:58 ` Patrick Lai
2011-01-26 13:10 ` Mark Brown
2011-01-26 13:10 ` Mark Brown
2011-01-26 7:58 ` Patrick Lai
2011-01-25 13:36 ` Mark Brown
2011-01-25 6:13 Patrick Lai
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=4D3E6A0D.40308@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.