From: Joonyoung Shim <jy0922.shim@samsung.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
kyungmin.park@samsung.com
Subject: Re: Separate dma driver for cpu_dais
Date: Wed, 17 Feb 2010 16:37:21 +0900 [thread overview]
Message-ID: <4B7B9CB1.8080204@samsung.com> (raw)
In-Reply-To: <1b68c6791002162324kbeb220dm23031e3115e617ca@mail.gmail.com>
On 2/17/2010 4:24 PM, jassi brar wrote:
> On Wed, Feb 17, 2010 at 3:58 PM, Joonyoung Shim <jy0922.shim@samsung.com> wrote:
>> Additionally, i have one more question.
>>
>> At the ASoC, is there a situation to share the dai(cpu or codec)?
> Currently, ASOC doesn't allow sharing cpu or codec dai.
>
>> If the dai is shared, i just think the ASoC core cannot support it.
> Correct.
>
>> There is the case at the S5PC1XX, it supports the hardware mixing by
>> using two tx fifo. First Jassi implemented codes using each other cpu
>> dai as Jassi says at the above for the hardware mixing, but it should
>> share codec_dai and need some modification of ASoC core.
>> (I can see codes at the below url
>> http://git.kernel.org/?p=linux/kernel/git/kki_ap/linux-2.6-samsung.git)
>> Jassi, how do you think about this?
> Though outside this topic, please see latest code from samsung GIT.
> I already share wm8580 dai with I2S primary_fifo dai as well
> as secondary_fifo dai. I implemented temporary workaround to share
> dais(luckily codec_dai wasn't used in a way to make it impossible,
> though cpu_dai still can't be shared).
> Also, there is some reason I didn't point to our repository:- the code is
> not meant for mainline. It's just a 'workaround' for urgent requirement.
>
I think even if it is workaround, the codes orient should go to the
right side. Anyway, i just wonder about sharing the dai and supporting
it at the ASoC.
next prev parent reply other threads:[~2010-02-17 7:37 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 [this message]
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
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=4B7B9CB1.8080204@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassisinghbrar@gmail.com \
--cc=kyungmin.park@samsung.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.