Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4978444imm; Tue, 31 Jul 2018 03:34:45 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfwSOeatYh+Fldn0kpiw7gHBe3WDE+wSV+KWlynceh1T+1C9K67GBKtAwDKh3cpPL0yKxZq X-Received: by 2002:a63:91c8:: with SMTP id l191-v6mr19396782pge.180.1533033284941; Tue, 31 Jul 2018 03:34:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533033284; cv=none; d=google.com; s=arc-20160816; b=nMpDbeHUvKXB0CXrS77ku1cODvboKr7H0UdEp0hankpJbJHt5TgZIHmOxfpTx+CTys eZkUCSuDkmlfzc5RNzPhLwtSQ1HIpEAjjs6dhDbQAo6qqOydHntLczYRDLSTOHboNHOF R6J9YtYiPLb4XpAvVKNf6uQiR6Z0kMUnaRvGEHcVqVpTFch+m+PYU23aaOp9M6QsjMKw bKIP047YDaBc4vQ5h6Ma5jGCgi3Mlyg7+HHDzjlBHlIeUq6mz0iJiNJMxPo4X2HIi2QN o/NXXYkoh9AuCyA/JnpCHM8Wc4jaKZ7V2ngdicXPUZvyPoqmxgnlPVEE/ov/TREVcY9H gvvQ== 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 :arc-authentication-results; bh=KMqhvPRaH8zV1L2vqHPN2nZvb7cA3DqxamNdpAwsAN0=; b=y2mGIlyah3cfnBE8flD9x5JGG2c2l/VYqzkVnFfN98t5V77UST9HtovSVq+NFJ+4j3 gxFSTGAyTf4lWvKgGFT7iLqqPMOaRwBnnjQnyumtIoEbLoz4+IZC8/ArC0OP4ZOKSv5s 6H4+DVNxfu5uYb/ez9fQ1gVfKt0hmBvqbVMY8b4BVB7P/FkY1bE/3gY9IWDnqc5hAgZ2 du6c+hUFxDssHM/2Y7XUq1CPxVWjUo1KbekKqGoMDC1/WGD5Me71JwSONPNW2dCtAxdg CKF1/k1peVscDL/RvKv1UpEwn9HwIjOK2CztKXnnnTHF23vvM4oSaLKliVOR81nle4rU FaMA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bg9-v6si13037370plb.243.2018.07.31.03.34.29; Tue, 31 Jul 2018 03:34:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731864AbeGaMMm (ORCPT + 99 others); Tue, 31 Jul 2018 08:12:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:39146 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730422AbeGaMMm (ORCPT ); Tue, 31 Jul 2018 08:12:42 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id A4502AFE4; Tue, 31 Jul 2018 10:33:00 +0000 (UTC) Date: Tue, 31 Jul 2018 12:32:59 +0200 Message-ID: From: Takashi Iwai To: Mark Brown Cc: "Agrawal, Akshu" , Pierre-Louis Bossart , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , Alexander.Deucher@amd.com, djkurtz@chromium.org, Liam Girdwood , open list Subject: Re: [alsa-devel] [PATCH] ASoC: soc-pcm: Use delay set in pointer function In-Reply-To: <20180731101943.GB5719@sirena.org.uk> References: <1532686422-1790-1-git-send-email-akshu.agrawal@amd.com> <66c8b8c4-bdd0-0129-5e5b-850890cfdb8d@linux.intel.com> <20180730155030.GP5789@sirena.org.uk> <7a88c7b4-d31d-b044-bb8e-a866d49d1256@amd.com> <5b3249cb-6212-6a14-b644-7548cf0ad00c@amd.com> <20180731101943.GB5719@sirena.org.uk> 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/26 (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 Tue, 31 Jul 2018 12:19:43 +0200, Mark Brown wrote: > > On Tue, Jul 31, 2018 at 11:25:11AM +0200, Takashi Iwai wrote: > > > It's not necessary that all CPU dais provide the pointer callback. > > My suggestion is that, if CPU dai *wants* to provide the base delay, > > it must be tied with the position value, hence it should provide the > > pointer callback. If CPU dai has a pointer callback, > > snd_soc_pcm_pointer() skips the component pointer callback but uses > > CPU dai pointer callback instead. > > However since it's not supposed to be providing any DMA a CPU DAI really > shouldn't be doing this... Well, if so, the CPU dai also cannot get the exact base delay corresponding to the reported position, either, no? Takashi