From: Patrick Lai <plai@codeaurora.org>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: ucm: hardware resource arbitration
Date: Mon, 10 Sep 2012 23:49:51 -0700 [thread overview]
Message-ID: <504EDF0F.70809@codeaurora.org> (raw)
Hi,
I have two use cases which can acquire same CODEC path but they cannot
run concurrently through mixing. When such scenario does arise,
arbitration is required based on priority of use cases. On the other
hand, same use cases on different platform may use different CODEC
paths so arbitration is not required. In order to decide whether
arbitration is required, I think the best place to do so is in UCM. I
looked at existing UCM APIs but I do not believe existing APIs have
concept of arbitration built in. If I am wrong, how can I handle
arbitration with existing UCM APIs. If I am correct, is there anyone
looking to expand UCM APIs for similar scenario?
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:[~2012-09-11 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:49 Patrick Lai [this message]
2012-09-12 13:53 ` ucm: hardware resource arbitration Tanu Kaskinen
2012-09-12 22:51 ` Patrick Lai
2012-09-16 6:40 ` Tanu Kaskinen
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=504EDF0F.70809@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@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).