From: Alexander <subaparts@yandex.ru>
To: Fabio Estevam <festevam@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Does anyone really have success experience with SPI codecs with new name-based SOC API?
Date: Thu, 02 Dec 2010 23:35:59 +0300 [thread overview]
Message-ID: <1291322159.1469.38.camel@r60e> (raw)
In-Reply-To: <AANLkTimPf9MUOtcVs7Yuf6MAftj6LErGXiLCCs6Q5DAp@mail.gmail.com>
On Thu, 2010-12-02 at 16:12 -0200, Fabio Estevam wrote:
> On Thu, Nov 18, 2010 at 9:31 AM, Alexander <subaparts@yandex.ru> wrote:
> > Does anyone really have success experience with SPI codecs with new
> > name-based SOC API?
> > There are really few SPI codecs in ASoC subsystem, so I wonder if only I
> > cannot bind my SPI codec to machine driver.
> >
> > The codec is registered with name spi0.0 it's the behavior of SPI
> > subsystem, I suppose. So the form is %s%d.%d and not %s.%d as supposed
> > in fmt_single_name() in soc_core.c
> >
> Have you managed to bind the SPI codec? I am trying the same thing
> here. Please let me know.
I've received a reply from Dimitris Papastamos, SoC subsystem developer,
and he written, that I should use it as is, ie spi0.0
So I'm finished with names and successfully binded it as
codecname==spi0.0
But for now, I have no sound anyway, it seems that something in SPI path
is broken (but I suppose, not in my code, as it works on 2.6.36-rc6), I
cannot see any communications going to codec with oscilloscope.
So I'm trying to figure it out now...
Best regards,
Alexander A. Sverdlin.
prev parent reply other threads:[~2010-12-02 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 11:31 Does anyone really have success experience with SPI codecs with new name-based SOC API? Alexander
2010-11-22 2:01 ` Dimitris Papastamos
2010-11-22 2:07 ` Dimitris Papastamos
2010-12-02 18:12 ` Fabio Estevam
2010-12-02 20:35 ` 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=1291322159.1469.38.camel@r60e \
--to=subaparts@yandex.ru \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@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;
as well as URLs for NNTP newsgroup(s).