From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5114AC433E0 for ; Thu, 30 Jul 2020 08:41:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2C429206E6 for ; Thu, 30 Jul 2020 08:41:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728910AbgG3IlK (ORCPT ); Thu, 30 Jul 2020 04:41:10 -0400 Received: from mga12.intel.com ([192.55.52.136]:60603 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725892AbgG3IlJ (ORCPT ); Thu, 30 Jul 2020 04:41:09 -0400 IronPort-SDR: jR2QrQsU2d2iIhC8sDIpO3tXKK1g9S++y+FmXVchQiCMX3x2NzCPxkm3eDVDQtC1scVmuEgmvw xXqpbRuTdF3w== X-IronPort-AV: E=McAfee;i="6000,8403,9697"; a="131120151" X-IronPort-AV: E=Sophos;i="5.75,413,1589266800"; d="scan'208";a="131120151" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Jul 2020 01:41:09 -0700 IronPort-SDR: rbKpV/B1Z7+Dqz1XsWN76n1nNT7gZylJ/EOiDhfngjZpDyBE4qGmNDDrN9Da5ahR1x5Ms/WScL R/H1csJg6SlA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,413,1589266800"; d="scan'208";a="304501983" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by orsmga002.jf.intel.com with ESMTP; 30 Jul 2020 01:41:04 -0700 Received: from andy by smile with local (Exim 4.94) (envelope-from ) id 1k147c-004smT-2N; Thu, 30 Jul 2020 11:41:04 +0300 Date: Thu, 30 Jul 2020 11:41:04 +0300 From: Andy Shevchenko To: Brent Lu Cc: alsa-devel@alsa-project.org, Cezary Rojewski , Pierre-Louis Bossart , Liam Girdwood , Jie Yang , Mark Brown , Jaroslav Kysela , Takashi Iwai , Kuninori Morimoto , Ranjani Sridharan , linux-kernel@vger.kernel.org, Daniel Stuart , Yu-Hsuan Hsu , Guennadi Liakhovetski , Kai Vehmanen , Sam McNally , Damian van Soelen Subject: Re: [PATCH v2 0/2] Add period size constraint for Atom Chromebook Message-ID: <20200730084104.GE3703480@smile.fi.intel.com> References: <1596096815-32043-1-git-send-email-brent.lu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1596096815-32043-1-git-send-email-brent.lu@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 30, 2020 at 04:13:33PM +0800, 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. You missed my tags, any reason why? -- With Best Regards, Andy Shevchenko