All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatol Pomozov <anatol.pomozov@gmail.com>
To: linux-sound@vger.kernel.org
Subject: A few questions about soc/alsa
Date: Fri, 05 Sep 2014 23:02:53 +0000	[thread overview]
Message-ID: <CAOMFOmXe7rcvZfp+n+CWDEQUwU=wRWJCZytWRCCBLOfJ4xKv3A@mail.gmail.com> (raw)

Hi

I just started working on soc audio for one board and trying to learn
more about soc/alsa implementation details (kernel 3.14).

My board uses Realtek 5677 driver (is it upstream since 3.14). SOC
connects to codec via I2S1 bus. Codec connects to speaker amplifier
(Analog Devices SM4567) via I2S2.

[SOC] <= I2S1 => [Realtek RT5677] <= I2S2 => [Speaker Amp SM4567]

Now I am trying to add the board driver fooboard_rt5677.c and my first
question is how DAI links the board driver should describe?


static struct snd_soc_dai_link fooboard_rt5677_dai[] = {
{
.name = "RT5677",
.stream_name = "RT5677 PCM",
.codec_dai_name = "rt5677-aif1",
.init = fooboard_rt5677_asoc_init,
.ops = &fooboard_rt5677_ops,
.dai_fmt = SND_SOC_DAIFMT_I2S | SND_SOC_DAIFMT_NB_NF | SND_SOC_DAIFMT_CBS_CFS,
}
}


Should I add I2S2 interface to snd_soc_dai_link array? What this array
after all? Does it describe *all* digital interfaces or only those
that are connected to the CPU?

If latter then I2S2 should not be in this array. But in this case who
should configure I2S2 bus and when? Does it happen when audio route
AIF1=>RT5677=>AIF2 becomes active? Could anyone point to the code
where such activation happens? Are there any existing soc examples
with configuration like in my case (i2s2 bus is for a speaker amp)?





Are there any good sources of information about alsa/soc besides
Documentation/sound/alsa/soc? Any books/articles that might be useful
for a rookie?

                 reply	other threads:[~2014-09-05 23:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAOMFOmXe7rcvZfp+n+CWDEQUwU=wRWJCZytWRCCBLOfJ4xKv3A@mail.gmail.com' \
    --to=anatol.pomozov@gmail.com \
    --cc=linux-sound@vger.kernel.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 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.