From: Felipe Ferreri Tonello <eu@felipetonello.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ASoC: fsl: add imx-cs427x machine driver
Date: Tue, 26 Jan 2016 11:01:25 +0000 [thread overview]
Message-ID: <56A75205.8060000@felipetonello.com> (raw)
In-Reply-To: <CAOMZO5BjeDMqNgf-=tE7=pByJi+jJVA=G2bbtp+XJeYbpev6KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Hi Fabio,
On 26/01/16 09:47, Fabio Estevam wrote:
> Hi Felipe,
>
> On Tue, Jan 26, 2016 at 7:43 AM, Felipe Ferreri Tonello
> <eu@felipetonello.com> wrote:
>
>> I agree, but that how it is today. These platform drivers for imx are
>> similar but not identical. Looking at them I would guess that they have
>> 50 to 60% of duplicated code.
>
> Would simple-audio-card or fsl-asoc-card help in this case?
>
Actually yes, thanks! I didn't know about the existence of fsl-asoc-card.
I get some errors but I don't think they actually matter:
[ 19.734494] fsl-asrc 2034000.asrc: driver registered
[ 19.738707] fsl-asoc-card sound: ASoC: CPU DAI (null) not registered
[ 19.738717] fsl-asoc-card sound: snd_soc_register_card failed (-517)
[ 19.741556] fsl-asoc-card sound: ASoC: CPU DAI (null) not registered
[ 19.741564] fsl-asoc-card sound: snd_soc_register_card failed (-517)
[ 19.774591] fsl-asoc-card sound: cs4271-hifi <-> 2028000.ssi mapping ok
[ 19.781507] fsl-asoc-card sound: ASoC: no source widget found for
ASRC-Playback
[ 19.790065] fsl-asoc-card sound: ASoC: Failed to add route
ASRC-Playback -> direct -> CPU-Playback
[ 19.805349] fsl-asoc-card sound: ASoC: no sink widget found for
ASRC-Capture
[ 19.817222] fsl-asoc-card sound: ASoC: Failed to add route
CPU-Capture -> direct -> ASRC-Capture
The codec is producing sound, which is good. Any idea on why these
errors are been triggered?
--
Felipe
[-- Attachment #2: 0x92698E6A.asc --]
[-- Type: application/pgp-keys, Size: 7195 bytes --]
next prev parent reply other threads:[~2016-01-26 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 17:53 Felipe F. Tonello
2016-01-26 2:29 ` Rob Herring
2016-01-26 9:43 ` Felipe Ferreri Tonello
2016-01-26 9:47 ` Fabio Estevam
2016-01-26 11:01 ` Felipe Ferreri Tonello [this message]
2016-01-26 11:05 ` Fabio Estevam
2016-01-26 17:42 ` Nicolin Chen
2016-01-31 13:28 ` Fabio Estevam
2016-01-26 11:50 ` Mark Brown
2016-01-26 15:50 ` Rob Herring
2016-01-26 16:03 ` Mark Brown
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=56A75205.8060000@felipetonello.com \
--to=eu@felipetonello.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tiwai@suse.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
Powered by JetHome