Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp2085360ybg; Thu, 30 Jul 2020 09:58:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxaRYSxN/UcadeQIevnPiFHAafsCXeB+ACWm50tDZ05Sh+oyMuid3CZX2jojQ4u4iYs3tls X-Received: by 2002:a17:906:3c02:: with SMTP id h2mr3637462ejg.437.1596128322620; Thu, 30 Jul 2020 09:58:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596128322; cv=none; d=google.com; s=arc-20160816; b=gX1dg05flcXDop+WVACxgo4xLvHbC07SalUyJtjm/9SKr7Dye67Xd2Dy8puODBTS4N 7Jr61hGAuqq3flBhlrmSFMFojytTj8LlqPY35rrtrfXEErNa3+q7LQBJy5XnAWDI0OwY Yv8lx5GLb57jb7v8WjvtTZOkDDEjlQJHfqQzbdodYpYSeMh/ZmF4QT+KWQV2K1ETVozi o6FbH2xmojbfgaeN7FouADiAFZL+FR0IAZth2qYbVFV/zqWx0ppS/Qt0zHLTl2A0e8az QurhjpWJwpaKSJ9Z0i7qhjWIWNH3AYUA4MIuprEpP/gakUU4LcCjMnwASE8FT5P/1M1e qz+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=moHSUswzT2VMJ+dyYXjEUG4n250ASbdWuvjFGC9L9Cc=; b=ix9tFjRRqyQFstN8dwQGu2AkcDs6pwYm/N1hSFG5YQn4JJpwKBTVlZ2r6Uqj+Le6yc EtfhJn57ozk4GFRhgYd6vA7sqL3Ah0CSdLF/aNAPfzeEATAsSwwx0QB9HXeq5nh1Lmkx taL5WBOFQ81yjTys4mKsytRzcg0/7lTR6vVkAzwiPLp2cSYUyXyZJLfaH3yesF2opMzk g9Hlcl98rpYJCKOCLtn+N16rL6vB4c/tWQ1tsiHBKTxHqBT31223jrn1MC8Qc2mlrrjp BonTfLXHiynVdkJ5d5DhXI9kXuq4Jry3Yd/62V6/K196nbT3pM0APV5wqVAnh883FZz7 raZg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e8si3288825edv.104.2020.07.30.09.58.18; Thu, 30 Jul 2020 09:58:42 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729832AbgG3Q4E (ORCPT + 99 others); Thu, 30 Jul 2020 12:56:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:40178 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726353AbgG3Q4E (ORCPT ); Thu, 30 Jul 2020 12:56:04 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id F3F42AD11; Thu, 30 Jul 2020 16:56:15 +0000 (UTC) Date: Thu, 30 Jul 2020 18:56:03 +0200 Message-ID: From: Takashi Iwai To: Pierre-Louis Bossart Cc: "Lu, Brent" , "alsa-devel@alsa-project.org" , Guennadi Liakhovetski , "Rojewski, Cezary" , Kai Vehmanen , Kuninori Morimoto , Jie Yang , Takashi Iwai , "linux-kernel@vger.kernel.org" , Liam Girdwood , Sam McNally , Mark Brown , Ranjani Sridharan , Daniel Stuart , Andy Shevchenko , Yu-Hsuan Hsu , Damian van Soelen Subject: Re: [PATCH 2/2] ASoC: Intel: Add period size constraint on strago board In-Reply-To: References: <1596020585-11517-1-git-send-email-brent.lu@intel.com> <1596020585-11517-3-git-send-email-brent.lu@intel.com> <4fe97f63-e552-3b2f-803c-53894b196bfd@linux.intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Jul 2020 17:27:58 +0200, Pierre-Louis Bossart wrote: > > > > >> Is this patch required if you've already constrained the period sizes for the > >> platform driver in patch1? > > > > Yes or alsa will select 320 as default period size for it. > > ok, then that's a miss in your patch1. 320 samples is a multiple of > 1ms for 48kHz rates. I think it was valid only for the 16kHz VoIP > paths used in some versions of Android, but that we don't support in > the upstream code. > > To build on Takashi's answer, the real ask here is to require that the > period be a multiple of 1ms, because that's the fundamental > design/limitation of firmware. It doesn't matter if it's 48, 96, 192, > 240, 480, 960 samples. If the 1ms alignment is the condition, it can be better with a different hw_params constraint. We can use snd_pcm_hw_constraint_step() for such a purpose. thanks, Takashi