From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Shengjiu Wang <shengjiu.wang@freescale.com>,
Lars-Peter Clausen <lars@metafoo.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Markus Pargmann <mpa@pengutronix.de>,
Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: No sound captured with SGTL5000 on i.MX6 in I²S master mode
Date: Sun, 21 Sep 2014 20:41:44 -0700 [thread overview]
Message-ID: <20140922034143.GA3448@Asurada> (raw)
In-Reply-To: <CAOMZO5Buh9DSD3YSpnkRsczUMj0BAFuOk_uRj1GpLMBgV9N5PQ@mail.gmail.com>
On Mon, Sep 22, 2014 at 12:26:21AM -0300, Fabio Estevam wrote:
> On Thu, Sep 18, 2014 at 3:07 PM, Nicolin Chen <nicoleotsuka@gmail.com> wrote:
>
> > I plan to replace imx-sgtl5000 and imx-wm8962 with it as long as
> > people are happy about the new driver. Would you like to help me
> > testing it on sgtl5000 side when you have time? Because I only
> > have a board with WM8962.
>
> Just tested fsl-asoc-card with sgtl5000 and it worked fine on my imx53-qsb.
Thank you! Then I think we can enable it from the next release version.
> These messages are a bit annoying though:
>
> [ 1.786201] fsl-asoc-card sound: ASoC: no source widget found for
> ASRC-Playback
> [ 1.796065] fsl-asoc-card sound: ASoC: Failed to add route
> ASRC-Playback -> direct -> CPU-Playback
> [ 1.807571] fsl-asoc-card sound: ASoC: no sink widget found for ASRC-Capture
> [ 1.817112] fsl-asoc-card sound: ASoC: Failed to add route
> CPU-Capture -> direct -> ASRC-Capture
I'll try to find a way to circumvent the ASRC route for non-ASRC links.
Thanks,
Nicolin
next prev parent reply other threads:[~2014-09-22 3:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 12:56 No sound captured with SGTL5000 on i.MX6 in I²S master mode Jean-Michel Hautbois
2014-09-18 13:30 ` Fabio Estevam
2014-09-18 13:35 ` Michael Trimarchi
2014-09-18 13:45 ` Jean-Michel Hautbois
2014-09-18 13:55 ` Michael Trimarchi
2014-09-18 14:09 ` Jean-Michel Hautbois
2014-09-18 16:09 ` Jean-Michel Hautbois
2014-09-18 17:05 ` Nicolin Chen
2014-09-18 17:26 ` Michael Trimarchi
2014-09-18 17:45 ` Nicolin Chen
2014-09-18 18:03 ` Michael Trimarchi
2014-09-18 18:13 ` Nicolin Chen
2014-09-18 18:18 ` Michael Trimarchi
2014-09-18 17:28 ` Fabio Estevam
2014-09-18 17:49 ` Nicolin Chen
2014-09-18 17:58 ` Fabio Estevam
2014-09-18 18:07 ` Nicolin Chen
2014-09-18 18:14 ` Fabio Estevam
2014-09-18 18:39 ` Nicolin Chen
2014-09-18 23:35 ` Fabio Estevam
2014-09-18 23:50 ` Nicolin Chen
2014-09-19 7:42 ` Jean-Michel Hautbois
2014-09-19 7:52 ` Nicolin Chen
2014-09-19 9:18 ` Jean-Michel Hautbois
2014-09-19 12:53 ` Jean-Michel Hautbois
2014-10-09 14:02 ` Jean-Michel Hautbois
2014-10-09 14:18 ` Fabio Estevam
2014-10-09 14:26 ` Jean-Michel Hautbois
2014-10-09 15:06 ` Fabio Estevam
2014-10-09 15:14 ` Jean-Michel Hautbois
2014-10-09 15:19 ` Fabio Estevam
2014-10-10 15:49 ` Jean-Michel Hautbois
2014-10-10 15:54 ` Fabio Estevam
2014-09-22 3:26 ` Fabio Estevam
2014-09-22 3:41 ` Nicolin Chen [this message]
2014-09-18 17:19 ` Nicolin Chen
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=20140922034143.GA3448@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--cc=jean-michel.hautbois@vodalys.com \
--cc=lars@metafoo.de \
--cc=michael@amarulasolutions.com \
--cc=mpa@pengutronix.de \
--cc=shawn.guo@freescale.com \
--cc=shengjiu.wang@freescale.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).