From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Caleb Crome <caleb@crome.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Need general idea how to architect driver for multi-codec board
Date: Fri, 3 Jun 2011 09:48:15 +0100 [thread overview]
Message-ID: <20110603084814.GB21286@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTinhMP143K5mAPPPc_R6N7Wxk8zZ3g@mail.gmail.com>
On Wed, Jun 01, 2011 at 03:17:10PM -0700, Caleb Crome wrote:
> Sorry to keep on this, but I'm really wedged. I can't tell if I'm trying
> to break new ground, or if I just don't know what I'm doing :-) Or both
> perhaps.
Like I said in my last mail you're probably trying to break new ground
here. You're trying to bind all the CODECs together and treat them as
one digital interface, currently the code does a series of point to
point links multiplexed on a bus only.
> I've got my multi-codec card instantiating (only 4 codecs here for
> simplicity -- there are really 8 total)
> # insmod tlv320aic3x_se.ko # <--- my custom version of aic3x driver.
That's not a good sign... If you've modified the driver you probably
want to look into submitting your modifications back upstream.
next prev parent reply other threads:[~2011-06-03 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:31 Need general idea how to architect driver for multi-codec board Caleb Crome
2011-05-11 17:50 ` Mark Brown
2011-05-11 18:29 ` Caleb Crome
2011-05-11 22:44 ` Caleb Crome
2011-05-26 21:23 ` Caleb Crome
2011-05-27 1:27 ` Mark Brown
2011-05-27 21:36 ` Caleb Crome
2011-05-28 1:34 ` Mark Brown
2011-06-01 22:17 ` Caleb Crome
2011-06-03 8:48 ` Mark Brown [this message]
2011-06-03 23:35 ` Caleb Crome
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=20110603084814.GB21286@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=caleb@crome.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