> > +static struct snd_pcm_hardware snd_fsl_hardware = {
> > +   .info = SNDRV_PCM_INFO_INTERLEAVED |
> > +           SNDRV_PCM_INFO_BLOCK_TRANSFER |
> > +           SNDRV_PCM_INFO_MMAP |
> > +           SNDRV_PCM_INFO_MMAP_VALID |
> > +           SNDRV_PCM_INFO_PAUSE |
> > +           SNDRV_PCM_INFO_RESUME,
> > +   .formats = SNDRV_PCM_FMTBIT_S16_LE,
> > +   .rate_min = 8000,
> > +   .channels_min = 2,
> > +   .channels_max = 2,
> > +   .buffer_bytes_max = FSL_SAI_DMABUF_SIZE,
> > +   .period_bytes_min = 4096,
> > +   .period_bytes_max = FSL_SAI_DMABUF_SIZE / TCD_NUMBER,
> > +   .periods_min = TCD_NUMBER,
> > +   .periods_max = TCD_NUMBER,
> > +   .fifo_size = 0,
> > +};
> 
> There's a patch in -next that lets the generic dmaengine code figure out
> some settings from the dmacontroller rather than requiring the driver to
> explicitly provide configuration - it's "ASoC: dmaengine-pcm: Provide
> default config".  Please update your driver to use this, or let's work
> out what it doesn't do any try to fix it.
> 

I couldn't find the patch in the next and other trees.
Does this patch has been submitted to the -next tree ?
Or could you tell me how to find the patch please?

Thanks very much.


_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to