[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5h8sf1caer.wl-tiwai@suse.de>
Date: Thu, 30 Jul 2020 17:03:40 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Brent Lu <brent.lu@...el.com>
Cc: alsa-devel@...a-project.org,
Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Jie Yang <yang.jie@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Sam McNally <sammc@...omium.org>,
Mark Brown <broonie@...nel.org>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Yu-Hsuan Hsu <yuhsuan@...omium.org>,
Daniel Stuart <daniel.stuart14@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Damian van Soelen <dj.vsoelen@...il.com>
Subject: Re: [PATCH v2 0/2] Add period size constraint for Atom Chromebook
On Thu, 30 Jul 2020 10:13:33 +0200,
Brent Lu wrote:
>
> Two different constraints are implemented: one is in platform's CPU
> DAI to enforce period sizes which are already used in Android BSP. The
> other is in Atom Chromebook's machine driver to use 240 as period size.
>
> Changes since v1:
> -Add comma at the end of media_period_size array declaration.
Is it a hardware restriction? Unless it's a must for some hardware
issues, enforcing such a small period size is nothing but a drawback
for a system without CRAS.
thanks,
Takashi
>
> Brent Lu (1):
> ASoC: intel: atom: Add period size constraint
>
> Yu-Hsuan Hsu (1):
> ASoC: Intel: Add period size constraint on strago board
>
> sound/soc/intel/atom/sst-mfld-platform-pcm.c | 15 +++++++++++++++
> sound/soc/intel/boards/cht_bsw_max98090_ti.c | 14 +++++++++++++-
> sound/soc/intel/boards/cht_bsw_rt5645.c | 14 +++++++++++++-
> 3 files changed, 41 insertions(+), 2 deletions(-)
>
> --
> 2.7.4
>
Powered by blists - more mailing lists