All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Michele Curti <michele.curti@gmail.com>
Cc: Luka Karinja <luka.karinja@gmail.com>,
	Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, "Koul, Vinod" <vinod.koul@intel.com>,
	"Nikula, Jarkko" <jarkko.nikula@intel.com>,
	Bard Liao <bardliao@realtek.com>
Subject: Re: writing an alsa driver
Date: Mon, 15 Jun 2015 18:04:28 +0100	[thread overview]
Message-ID: <1434387868.2434.50.camel@loki> (raw)
In-Reply-To: <20150615164623.GA693@asus>

+ Vinod,

On Mon, 2015-06-15 at 18:46 +0200, Michele Curti wrote:
> On Sat, Jun 13, 2015 at 01:47:13PM +0000, Luka Karinja wrote:
> > Hey guys i have a T100TAF which also has z3735f & rt5648 and 
> > watching your development.
> > 
> > On the T100TA wich has the Z3740 and rt5645 a new /var/lib/alsa/asound.state
> > was needed to get the sound working.
> > It was making cracking sounds without it (saw in your previous post)
> > found here:
> > https://raw.githubusercontent.com/AdamWill/baytrail-m/master/alsa/t100_B.state
> > 
> > Eagerly following the development
> 
> Eheh :)
> 
> So far no news, sadly.
> 

We are also a little suspicious that this laptop is using SSP1 for the
I2S audio connection to the codec. The bad news is that the FW used by
this BYT ADSP driver does not support the SSP1 port. It's hard coded to
use SSP0 (Jarrko, please correct the port numbering if it's wrong).
There are going to be no further releases of this FW.

However, the other upstream BYT ADSP driver from Vinod's team is going
to support the other SSP ports. It currently only supports SSP0, but I
believe that a new FW will be released soon that will support SSP1.
Vinod do you know the new FW release date ?

Michele, can you change your machine driver to use the Vinods BYT DSP
PCM driver (base it on bytcr_rt5640.c). Please test probing/booting with
the current FW release from Vinod too. That way you should be ready to
integrate the new FW when it is released. Please also CC Vinod on any
issues you have getting the FW to boot using the new driver/FW.

Thanks

Liam

  reply	other threads:[~2015-06-15 17:04 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 [this message]
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
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
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=1434387868.2434.50.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=jarkko.nikula@intel.com \
    --cc=luka.karinja@gmail.com \
    --cc=michele.curti@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 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.