From: Lars-Peter Clausen <lars@metafoo.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
zhuzhenhua@allwinnertech.com, Mark Brown <broonie@kernel.org>,
kevin.z.m.zh@gmail.com, sunny@allwinnertech.com,
shuge@allwinnertech.com
Subject: Re: integration into ASoC
Date: Mon, 10 Mar 2014 18:23:10 +0100 [thread overview]
Message-ID: <531DF4FE.2020405@metafoo.de> (raw)
In-Reply-To: <20140310164307.GH2815@lukather>
On 03/10/2014 05:43 PM, Maxime Ripard wrote:
>>>
>>>> Right now ASoC expects you to specify a DAI link for a PCM
>>>> device. The DAI link connects the DAIs of two components typically
>>>> the SoC side and a external CODEC. In your case you do not have the
>>>> external CODEC. You can solve this by using a dummy CODEC or
>>>> splitting things up and register both the CODEC and the CPU DAI from
>>>> the same driver.
>>>
>>> That would probably be the best solution, yes.
>>>
>>>> But I'm currently working on a patchset that will eventually allow
>>>> these kind of devices to be supported more naturally. It will allow
>>>> to register them as one component that won't need the CODEC
>>>> component to work.
>>>
>>> Great! Do you have a branch with that work somewhere?
>>
>> Not yet. But I hope to get there in the next weeks.
>
> Could you put me in Cc whenever you post them for feedback/testing?
Sure. I just had a quick peek at the datasheet and I think you should be
able to get away with implementing this as a CODEC driver for now and use
the dummy-dai for the CPU side in you DAI link.
- Lars
prev parent reply other threads:[~2014-03-10 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:53 integration into ASoC Maxime Ripard
2014-03-07 17:12 ` Lars-Peter Clausen
2014-03-09 7:48 ` Mark Brown
2014-03-10 10:11 ` Maxime Ripard
2014-03-10 9:50 ` Maxime Ripard
2014-03-10 10:15 ` Lars-Peter Clausen
2014-03-10 16:43 ` Maxime Ripard
2014-03-10 17:23 ` Lars-Peter Clausen [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=531DF4FE.2020405@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kevin.z.m.zh@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=shuge@allwinnertech.com \
--cc=sunny@allwinnertech.com \
--cc=zhuzhenhua@allwinnertech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox