All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@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,
	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, 18 Jun 2015 16:44:51 +0530	[thread overview]
Message-ID: <20150618111451.GH28601@localhost> (raw)
In-Reply-To: <20150617213410.GA907@asus>

On Wed, Jun 17, 2015 at 11:34:10PM +0200, Michele Curti wrote:
> On Wed, Jun 17, 2015 at 10:16:15AM +0100, Liam Girdwood wrote:
> > On Tue, 2015-06-16 at 22:50 +0200, Michele Curti wrote:
> > > On Mon, Jun 15, 2015 at 06:04:28PM +0100, Liam Girdwood wrote:
> > > > 
> > > > 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.
> > > >
> > > 
> > > Sure!
> > > 
> > > A note, without enabling the config option SND_SOC_INTEL_SST the driver
> > > will not compile/install but it seems strange because when doing a 
> > > menuconfig the machine driver option is available even if the 
> > > SND_SOC_INTEL_SST option is not selcted (I copied the Kconfig part 
> > > from the SND_SOC_INTEL_BYTCR_RT5640_MACH one).
Only selecting the SND_SOC_INTEL_BYTCR_RT5640_MACH should do, rest is auto
selected

> > 
> > Is the BYTCR_RT5640 building for you ? This driver family uses the
> > SND_SST_MFLD_PLATFORM instead of the SND_SOC_INTEL_SST platform.
> 
> Mmmh.. indeed no.. I tried with a clean linux-next, doing a make clean and
> selecting the SND_SOC_INTEL_BYTCR_RT5640_MACH option using menuconfig:
> 
> [zio@asus linux-next]$ grep BYTCR_RT5640 .config
> CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m
> [zio@asus linux-next]$ grep SND_SST_MFLD_PLATFORM .config
> CONFIG_SND_SST_MFLD_PLATFORM=m
> [zio@asus linux-next]$ 
> 
> But when I do a make the driver don't compile
> 
> [zio@asus linux-next]$ ls sound/soc/intel/boards/*.o
> ls: cannot access sound/soc/intel/boards/*.o: No such file or directory
> 
> And when I do a make install the only (sound) installed modules are
> 
>   INSTALL sound/core/snd-compress.ko
>   INSTALL sound/core/snd-pcm.ko
>   INSTALL sound/core/snd-timer.ko
>   INSTALL sound/core/snd.ko
>   INSTALL sound/soc/codecs/snd-soc-rl6231.ko
>   INSTALL sound/soc/codecs/snd-soc-rt5640.ko
>   INSTALL sound/soc/intel/atom/snd-soc-sst-mfld-platform.ko
>   INSTALL sound/soc/intel/atom/sst/snd-intel-sst-acpi.ko
>   INSTALL sound/soc/intel/atom/sst/snd-intel-sst-core.ko
>   INSTALL sound/soc/snd-soc-core.ko
>   INSTALL sound/soundcore.ko
>   DEPMOD  4.1.0-rc8-next-20150617-asus
I am using Marks next

$ grep BYTCR_RT5640 .config
CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m
$ grep SND_SST_MFLD_PLATFORM .config
CONFIG_SND_SST_MFLD_PLATFORM=m
$ ls sound/soc/intel/boards/*.o
sound/soc/intel/boards/built-in.o      sound/soc/intel/boards/skl_rt286.o
sound/soc/intel/boards/snd-soc-sst-bytcr-rt5640.o
sound/soc/intel/boards/bytcr_rt5640.o
sound/soc/intel/boards/snd-soc-skl_rt286.o

So these did get built for me

-- 
~Vinod

  reply	other threads:[~2015-06-18 11:13 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 [this message]
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
  -- 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=20150618111451.GH28601@localhost \
    --to=vinod.koul@intel.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=michele.curti@gmail.com \
    --cc=tiwai@suse.de \
    /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.