Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp623692pxa; Wed, 12 Aug 2020 09:41:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9tb4xmlYmWFfyUBJOeS40XepcvyqyfDfYUmnvHK18klOTOIkmMaxBGImD8Mx++9v9lJ79 X-Received: by 2002:a17:907:10db:: with SMTP id rv27mr651566ejb.350.1597250518222; Wed, 12 Aug 2020 09:41:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597250518; cv=none; d=google.com; s=arc-20160816; b=HDX4qJCGq/Onr5q7rqlBD991hsR/b3SwW9LM0g0qJtjjzFZ+rCC+lCM4XhFF3eTgTc 7SEKg4G1UlITvEIcPZZq/kISxOEV0bep1fCJVenZQJoaNeYtEMVS7XR1cOiUvgetATi4 gxekvLXvrz/h6wKKvsvvgoaWOEKQUSV5SN+VyGXnMGEYJxJ52XqdgArDQlAqfRBNm1sh /K7QNIER6XGsVuO/w6fWp6D63xYo9PPhLa4jxx9Ll/lYLcZcSLOQygQtvZDHRiE4r8Qo KGfk2T5Xay/fYBfDKQylSZDPaE0t1amv6Q0ErAiQQZnxk5JltzjSgZS77zQNMftKM6A0 Mtig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:ironport-sdr:ironport-sdr; bh=J+E9EP36PFuQ7afIdPJL2CwAneuGD4WlqmVfH4OLOI4=; b=N34tKh9GSqFDMjJe5PbMPr7e+6DBGcKsv1D02FMvTtUQlmYjMXsEKcUmQHZotXWz9e qQKXKbcY3myLiAc3CmSV5J+DhJBRcl+LvfDMSgjZ2vOVGV54HNZE5nHo7r2WUSjT7dNj t5K5G2u8jzM2aklR9e74xceUWFWdtjyIlcwcGHToV9GsPutupYvgnfF6C5qCWp6tFsvK 7cOHTY1hlS79nEN9UrKYQq1fesMpHKFeoIUp1FaVCyJqttoyx8N/WYMaeutbLzuLLFmu Nilsy1I+hEi7FJuVTaAU43lIdhWF020QiggUMms+9A7fdplEwYfSlNu1dcYupMPEbVh2 uQfQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g21si1643659ejx.56.2020.08.12.09.41.35; Wed, 12 Aug 2020 09:41:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726600AbgHLQi0 (ORCPT + 99 others); Wed, 12 Aug 2020 12:38:26 -0400 Received: from mga12.intel.com ([192.55.52.136]:32724 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725872AbgHLQiZ (ORCPT ); Wed, 12 Aug 2020 12:38:25 -0400 IronPort-SDR: ZUPIy3kd2tV02Mk48MYVnqpMzHRJYWhF+5HgEBp3ur+8py+AsfVQiBUppmTCRDKADZIT+QoI62 RLrcy7iVRLbQ== X-IronPort-AV: E=McAfee;i="6000,8403,9711"; a="133535379" X-IronPort-AV: E=Sophos;i="5.76,304,1592895600"; d="scan'208";a="133535379" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Aug 2020 09:38:25 -0700 IronPort-SDR: Ot9t+RPuVM04ujHrIjA/yFHnd3j6C8ApNIb/yJnjh59NLl4QSLTBu2gl/mqJMJI5JAajkcvWiG vTaGQIgcteXQ== X-IronPort-AV: E=Sophos;i="5.76,304,1592895600"; d="scan'208";a="495572467" Received: from mbharapa-mobl.amr.corp.intel.com (HELO [10.212.31.62]) ([10.212.31.62]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Aug 2020 09:38:23 -0700 Subject: Re: [PATCH v3 2/2] ASoC: Intel: Add period size constraint on strago board To: "Lu, Brent" , Takashi Iwai Cc: Yu-Hsuan Hsu , Guennadi Liakhovetski , "alsa-devel@alsa-project.org" , Andy Shevchenko , Kuninori Morimoto , Kai Vehmanen , "linux-kernel@vger.kernel.org" , "Rojewski, Cezary" , Jie Yang , Takashi Iwai , Liam Girdwood , Sam McNally , Mark Brown , Ranjani Sridharan , Daniel Stuart , "yuhsuan@google.com" , Damian van Soelen References: <3f3baf5e-f73d-9cd6-cbfb-36746071e126@linux.intel.com> <20200811145353.GG6967@sirena.org.uk> <20200811172209.GM6967@sirena.org.uk> From: Pierre-Louis Bossart Message-ID: <0714b222-d3fc-5744-1147-bfac7df2651e@linux.intel.com> Date: Wed, 12 Aug 2020 11:38:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/12/20 11:08 AM, Lu, Brent wrote: >>> >>> I also wonder what's really missing, too :) >>> >>> BTW, I took a look back at the thread, and CRAS seems using a very >>> large buffer, namely: >>> [ 52.434791] sound pcmC1D0p: PERIOD_SIZE [240:240] >>> [ 52.434802] sound pcmC1D0p: BUFFER_SIZE [204480:204480] >> >> yes, that's 852 periods and 4.260 seconds. Never seen such values :-) > > CRAS calls snd_pcm_hw_params_set_buffer_size_max() to use as large > buffer as possible. So the period size is an arbitrary number in different > platforms. Atom SST platform happens to be 256, and CML SOF platform > is 1056 for example. ok, but earlier in this thread it was mentioned that values such as 432 are not suitable. the statement above seems to mean the period actual value is a "don't care", so I don't quite see why this specific patch2 restricting the value to 240 is necessary. Patch1 is needed for sure, Patch2 is where Takashi and I are not convinced.