From: Lars-Peter Clausen <lars@metafoo.de>
To: Anatol Pomozov <anatol.pomozov@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: How to activate DAI link to dummy codec?
Date: Sat, 11 Jul 2015 11:58:49 +0200 [thread overview]
Message-ID: <55A0E8D9.2010801@metafoo.de> (raw)
In-Reply-To: <CAOMFOmUeF_LbfYyGGaCZG690Wow7FdiZtVTFHo7FyXdRMsYpnQ@mail.gmail.com>
On 07/10/2015 11:50 PM, Anatol Pomozov wrote:
> Hi
>
> I have following hardware configuration
>
> [SoC] <=> [RT5677] <=> [MAX98357A]
>
> MAX98357A is a simple speaker amplifier with I2S data interface and no
> I2C control. The chip automatically configures itself (rate/block
> frequency) when I2S is started streaming to the chip. This chip does
> not need a driver (there is nothing to configure) and we can use
> "dummy-codec" for it.
The dummy CODEC is only meant to be used in situations where there is no
actual hardware.
If there is actual hardware even if it does not have a control bus the
hardware will still have constraints like supported samplerates, etc. which
should be modeled. And the data flow graph also should be modeled using DAPM.
>
> There is a DAI link between RT5677 and MAX and it should be configured
> from RT5677 side. RT5677 is master here and it need to set I2S bus
> parameters. Configuration happens in rt5677 hw_params() function and
> it is triggered by dai link activation.
>
> My question is how to tell DAPM that I need to activate this link?
>
> If MAX98357A was a real codec then it would have an OUTPUT widget that
> I can activate, this would trigger dai link in between to be activated
> as well. But dummy codec does not have any widgets, so how I suppose
> to activate link to dummy codec?
You just gave the answer yourself, make it a real CODEC :)
- Lars
next prev parent reply other threads:[~2015-07-11 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 21:50 How to activate DAI link to dummy codec? Anatol Pomozov
2015-07-11 9:58 ` Lars-Peter Clausen [this message]
2015-07-11 23:37 ` Anatol Pomozov
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=55A0E8D9.2010801@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.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