All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alexander <subaparts@yandex.ru>
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: Thu, 28 Oct 2010 19:33:03 +0100	[thread overview]
Message-ID: <20101028183302.GA14076@sirena.org.uk> (raw)
In-Reply-To: <1288281110.2098.47.camel@r60e>

On Thu, Oct 28, 2010 at 07:51:50PM +0400, Alexander wrote:

Please remember to always CC maintainers, messages sent only to the
mailing list are likely to get dropped on the floor.

> Oh, no, this part is correct, I'm sure.
> 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.

  reply	other threads:[~2010-10-28 18:33 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 [this message]
2010-10-28 22:24       ` Alexander

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=20101028183302.GA14076@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=subaparts@yandex.ru \
    --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.