From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: Separate dma driver for cpu_dais
Date: Wed, 17 Feb 2010 12:42:05 +0000 [thread overview]
Message-ID: <20100217124205.GA11510@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1b68c6791002170413o61958189y786b13477fd7e12a@mail.gmail.com>
On Wed, Feb 17, 2010 at 09:13:05PM +0900, jassi brar wrote:
> On Wed, Feb 17, 2010 at 7:42 PM, Mark Brown
> > So. Ideally for hardware mixing you'd represent the hardware mixing as
> > a device within ASoC but that's not currently supported - the multi
> > CODEC work should take care of it but it's not there yet.
> is that work visible on some branch in ur tree?
I'm not doing it, it's on Liam's list. I generally don't maintian
branches for anything.
> > Overall I don't see any immediate problem with supporting this in
> > mainline as-is from what I've looked at so far.
> I assume this is about dma_id flag?
The hardware mixing too, like I say it's the most trivial case possible
so doesn't run into many problems.
prev parent reply other threads:[~2010-02-17 12:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 2:39 Separate dma driver for cpu_dais jassi brar
2010-02-17 6:58 ` Joonyoung Shim
2010-02-17 7:24 ` jassi brar
2010-02-17 7:37 ` Joonyoung Shim
2010-02-17 10:52 ` Mark Brown
2010-02-17 12:15 ` jassi brar
2010-02-17 13:14 ` Mark Brown
2010-02-18 2:14 ` jassi brar
2010-02-18 9:35 ` Mark Brown
2010-02-18 9:42 ` jassi brar
2010-02-18 9:52 ` Mark Brown
2010-02-18 10:32 ` jassi brar
2010-02-18 10:57 ` Mark Brown
2010-02-18 11:59 ` jassi brar
2010-02-18 13:10 ` Mark Brown
2010-02-23 5:45 ` jassi brar
2010-02-23 10:37 ` Mark Brown
2010-02-19 9:48 ` jassi brar
2010-02-19 9:50 ` Mark Brown
2010-02-18 6:12 ` Joonyoung Shim
2010-02-18 9:42 ` Mark Brown
2010-02-17 10:42 ` Mark Brown
2010-02-17 12:13 ` jassi brar
2010-02-17 12:42 ` Mark Brown [this message]
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=20100217124205.GA11510@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jassisinghbrar@gmail.com \
--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.