From: Michele Curti <michele.curti@gmail.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Luka Karinja <luka.karinja@gmail.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Nikula, Jarkko" <jarkko.nikula@intel.com>,
Bard Liao <bardliao@realtek.com>
Subject: Re: writing an alsa driver
Date: Thu, 25 Jun 2015 09:39:14 +0200 [thread overview]
Message-ID: <20150625073914.GA3833@dellaz> (raw)
In-Reply-To: <20150625032407.GQ19530@localhost>
On Thu, Jun 25, 2015 at 08:54:07AM +0530, Vinod Koul wrote:
> On Wed, Jun 24, 2015 at 08:21:20PM +0200, Michele Curti wrote:
> > > > There are a lot of errors about missing backend dai:
> > > > [ 7.195570] Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port
> > > So in this driver we use DPCM, which means that you have to route Front End
> > > to a BackEnd and then only you can open a device. Without linking to BE it
> > > will fail
> > >
> >
> > Yes, when Liam wrote about that I started to try to understand how to find the
> > right audio route/path, but I think it will take a while eheh :p
> >
> >
> > Thanks! So for now I tried to blindy launch these commands (apart for the
> > "Speaker L" and "Speaker R" controls, not present in the rt5645 codec) and
> > I got about a minute freeze at every boot and some new errors:
> >
> > [ 2.700127] sst-mfld-platform sst-mfld-platform: Slot control: codec_out tx interleaver slot 0 doesn't have DAPM widget!!!
> > [ 2.700177] sst-mfld-platform sst-mfld-platform: Slot control: codec_out tx interleaver slot 1 doesn't have DAPM widget!!!
> > [ 2.700226] sst-mfld-platform sst-mfld-platform: Slot control: codec_out tx interleaver slot 2 doesn't have DAPM widget!!!
> > [ 2.700276] sst-mfld-platform sst-mfld-platform: Slot control: codec_out tx interleaver slot 3 doesn't have DAPM widget!!!
> > [ 2.700321] sst-mfld-platform sst-mfld-platform: Slot control: codec_in rx deinterleaver codec_in0_0 doesn't have DAPM widget!!!
> > [ 2.700368] sst-mfld-platform sst-mfld-platform: Slot control: codec_in rx deinterleaver codec_in0_1 doesn't have DAPM widget!!!
> > [ 2.700417] sst-mfld-platform sst-mfld-platform: Slot control: codec_in rx deinterleaver codec_in1_0 doesn't have DAPM widget!!!
> > [ 2.700468] sst-mfld-platform sst-mfld-platform: Slot control: codec_in rx deinterleaver codec_in1_1 doesn't have DAPM widget!!!
> this is unexpected, I will check on this
>
> > ...
> > [ 7.970937] intel_sst_acpi 80860F28:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
> > [ 7.970964] intel_sst_acpi 80860F28:00: fw returned err -16
> Yes this is a problem, which FW are you using
>
> I am expecting you should be on
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/intel?id=d562a3b636325e969d4fdf60ec5e418a510f3510
Yes, I confirm it's the firmware I'm using, I did a diff to be sure :)
Thanks,
Michele
>
> > ...
> > [ 53.538117] Baytrail Audio Port: sst: error code = -22
> > [ 53.541909] bytx205_rt5645 bytx205_rt5645: BUG: pcmC0D0p:0, pos = -22, buffer size = 203830, period size = 1199
> This is impact of FW timeout
>
> --
> ~Vinod
next prev parent reply other threads:[~2015-06-25 7:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 14:52 writing an alsa driver Michele Curti
2015-05-23 16:32 ` Michele Curti
2015-05-27 6:45 ` Takashi Iwai
2015-05-27 8:54 ` Michele Curti
2015-05-27 18:41 ` Liam Girdwood
2015-05-27 20:13 ` Michele Curti
2015-05-28 11:31 ` Liam Girdwood
2015-05-28 12:53 ` Michele Curti
2015-05-28 13:21 ` Liam Girdwood
2015-05-28 19:17 ` Michele Curti
2015-05-29 9:42 ` Liam Girdwood
2015-05-29 13:17 ` Michele Curti
2015-06-01 11:06 ` Liam Girdwood
2015-06-04 7:09 ` Marcus Bannerman
2015-06-04 9:04 ` Michele Curti
2015-06-04 8:59 ` Michele Curti
2015-06-04 10:33 ` Liam Girdwood
2015-06-04 17:44 ` Juergen Bausa
2015-06-04 19:39 ` Michele Curti
2015-06-05 7:00 ` Jarkko Nikula
2015-06-08 8:26 ` Michele Curti
2015-06-08 8:49 ` Michele Curti
2015-06-13 13:47 ` Luka Karinja
2015-06-15 16:46 ` Michele Curti
2015-06-15 17:04 ` Liam Girdwood
2015-06-16 20:50 ` Michele Curti
2015-06-17 9:16 ` Liam Girdwood
2015-06-17 21:34 ` Michele Curti
2015-06-18 11:14 ` Vinod Koul
2015-06-18 18:47 ` Michele Curti
2015-06-19 7:54 ` Vinod Koul
2015-06-19 8:12 ` Michele Curti
2015-06-17 6:39 ` Jarkko Nikula
2015-06-23 9:09 ` Michele Curti
2015-06-23 9:51 ` Liam Girdwood
2015-06-24 10:21 ` Vinod Koul
2015-06-24 11:31 ` Antonio Ospite
2015-06-24 11:40 ` Liam Girdwood
2015-06-24 16:04 ` Vinod Koul
2015-06-24 18:21 ` Michele Curti
2015-06-25 3:24 ` Vinod Koul
2015-06-25 7:39 ` Michele Curti [this message]
2016-03-03 11:11 ` Michele Curti
2016-03-03 11:27 ` Vinod Koul
2016-03-03 13:08 ` Michele Curti
2016-03-03 16:20 ` Pierre-Louis Bossart
2016-03-04 11:07 ` Michele Curti
-- strict thread matches above, loose matches on Subject: below --
2015-07-22 20:05 Marco Bodega
2015-07-24 20:54 ` Michele Curti
2015-08-10 14:12 Johnny
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=20150625073914.GA3833@dellaz \
--to=michele.curti@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=jarkko.nikula@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=luka.karinja@gmail.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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).