Re: writing an alsa driver

[Liam Girdwood <liam.r.girdwood@linux.intel.com>]

On Tue, 2015-06-23 at 11:09 +0200, Michele Curti wrote:
> On Mon, Jun 15, 2015 at 06:04:28PM +0100, Liam Girdwood wrote:
> > 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.
> >
> 
> Hi,
> an update, thanks to Vinod now the driver compiles enabling only the (new)
> CONFIG_SND_SOC_INTEL_BYTCR_RT5645_MACH option.
> 
> The sound card shows up:
> [zio@asus ~]$ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: baytrailcraudio [baytrailcraudio], device 0: Baytrail Audio (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> 
> There are a lot of errors about missing backend dai:
> [    7.195570]  Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port

This usually means that no DAPM route has been configured to route the
audio from the PCM FE to the BE DAI link. Can you check your mixer
settings with alsamixer and make sure a route exists. The DSP is in
between the FE and BE so it's the DSP mixers that would need to be
configured.

Btw, there is some debugFS files to help display the routing status for
each widget so this can be used to check your DAPM DSP driver graph.

Liam