All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>
Subject: ASoC: Dynamic CODEC DAI
Date: Mon, 28 Nov 2011 16:49:18 -0800	[thread overview]
Message-ID: <4ED42C0E.2080300@codeaurora.org> (raw)


Problem overview:

The CODEC which I am working on transports digital audio through
SLIMBUS instead of I2S. The concept of CODEC DAI does not apply too
well with SLIMBUS architecture as CODEC DAIs are typically defined base
on a set of I2S digital audio interface(bit clock, world select, sd
lines). On the CODEC, there are 10 digital capture ports. They can be
independently configured as mono channels or can be run-time grouped
together to function like multi-channel CODEC DAIs. On top of that,
only some ports out of 10 ports can accept all analog mic inputs or
digital mic inputs. Hence, even though the CODEC satisfies the
concurrent use cases it was designed for, software would have to be
articulate on grouping the ports in order to utilize all ports. So, I
cannot simply code up CODEC DAI definitions in the CODEC driver for a
particular machine. For now, I am looking for compile time grouping of
these ports as use cases are known at the time machine is designed.

Proposal:
I want to minimize amount of change to soc framework at the same time
meeting my requirement.

Here is my proposed design

In CODEC driver, I will declare codec dai for each port.
Then, I will enhance ASoC framework to take a list of CODEC DAIs and
pass list of CODEC DAIs back to callback function such as startup,
hw_param, prepare, trigger. I believe this approach will not require
massive amount of change to framework.

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.

             reply	other threads:[~2011-11-29  0:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  0:49 Patrick Lai [this message]
2011-11-29  0:58 ` ASoC: Dynamic CODEC DAI Patrick Lai
2011-11-29  1:19 ` Pierre-Louis Bossart
     [not found] ` <000001ccae35$0122cf60$03686e20$@bossart@linux.intel.com>
2011-11-29  6:14   ` Patrick Lai
2011-11-29 21:20     ` Pierre-Louis Bossart
2011-11-29 13:49 ` Mark Brown
2011-12-02  2:56   ` Patrick Lai
2011-12-02 10:11     ` Liam Girdwood
2011-12-05  7:22       ` Patrick Lai
2011-12-05 11:49         ` Mark Brown
2011-12-02 11:45     ` Mark Brown

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=4ED42C0E.2080300@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.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 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.