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.
Hi Takashi,
This patch is cherry-picked from Chrome's branch which is originally implemented by google. They found this value works best with CRAS and these two machine drivers are for Chromebooks. Other BSW machine drivers are untouched.
Regards, Brent
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