From: Alexander <subaparts@yandex.ru>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
Victor Rodriguez <vm.rod25@gmail.com>,
lrg@slimlogic.co.uk
Subject: Re: New SoC layer codec registration problem
Date: Fri, 29 Oct 2010 02:24:43 +0400 [thread overview]
Message-ID: <1288304683.2098.54.camel@r60e> (raw)
In-Reply-To: <20101028183302.GA14076@sirena.org.uk>
Hello!
On Thu, 2010-10-28 at 19:33 +0100, Mark Brown wrote:
> > The question is why fmt_single_name() picks up "spi0.0" instead of
> > "cs4271-codec", I've added some debug output. And this function relies
>
> We identify devices based on something unique per device so that if you
> have more than one device of the same type in a system the stack can
> tell them apart.
>
My machine driver contains the following structures:
---
static struct snd_soc_dai_link edb93xx_dai = {
.name = "CS4271",
.stream_name = "CS4271 HiFi",
.platform_name = "ep93xx-pcm-audio",
.cpu_dai_name = "ep93xx-i2s",
.codec_name = "cs4271-codec",
.codec_dai_name = "cs4271-hifi",
.ops = &edb93xx_ops,
};
static struct snd_soc_card snd_soc_edb93xx = {
.name = "EDB93XX",
.dai_link = &edb93xx_dai,
.num_links = 1,
};
---
And all other machine SoC drivers contain similar...
If instead I'll write
.codec_name = "spi0.0",
it will be strange... However it can work...
Alexander.
prev parent reply other threads:[~2010-10-28 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 9:12 New SoC layer codec registration problem Alexander
2010-10-28 14:07 ` Victor Rodriguez
2010-10-28 15:51 ` Alexander
2010-10-28 18:33 ` Mark Brown
2010-10-28 22:24 ` Alexander [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=1288304683.2098.54.camel@r60e \
--to=subaparts@yandex.ru \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=vm.rod25@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 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.