Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4032960ybv; Mon, 10 Feb 2020 11:00:47 -0800 (PST) X-Google-Smtp-Source: APXvYqy/WRatGXV0jv++gzsA7tc9O46J7BKfxUOuhdEWEAxRBDOTx1VyduWNCH/6Qza+J4WIYvS5 X-Received: by 2002:aca:530e:: with SMTP id h14mr301767oib.105.1581361246889; Mon, 10 Feb 2020 11:00:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581361246; cv=none; d=google.com; s=arc-20160816; b=Xcr+iaQvQhBHNkxweS8CMK1GEr/26gM/fy2PQVdisy5crYNotWQYr54EPeLOlt46S2 C7TIXPb3gggsrvyE9DEpALe2aKZKml1cYyM7KSFkRJt8BN2eEYJpZKRSXmZq1IfXMBtW mQAwsxIfgIAdDoxuBY6u2iMSNuSuigvtUVgZJ5xuOZ+m2HkmcnzRWRzLdQUPpbmzDa9K 6jRsRcvJzIfri4a/L68mG8jiJOrJvYFvOVO3WAzX/3AlGVR4I7hmyurJv8qOpIOFiDmV 8fr2cR2aPeGqeGdNoqZVgj65acPwB9+JESxddXmTYLIZMoW96qL0anGjQ4Y8gLsTCGWR hziA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=zwM11VDZADcIWfLyZG3N7GGJPOMp6VVhjO147xLOoc0=; b=ezcL1G9m5wW+1eqfARoqUd41qnpTxlix5S7OeC+SBI9075PRHPOIvXpTdRAlr1P+fU x8rxDImCbwug6n3OWRTG1VwDSnnzMzO8uKodJMHxpNSHv0TmIiQuSIiDwUcYZp3oZfCA dYEvQ4ejpvsFu/rRMU82bJlNZKPgO/BOSAOzgc78VENcZA0wDJaJZg7gnsA6DRFfSScP QWEq7vTrX5AoLU97JbzGhdkwLjzVUajELdGcBvVVOPQ+bVwscfVnRl0TA1o4rM6JqDIs 5z/hdUWcxeplY/gHhilta6T0Q3+F9OkFF4Bni1U+yG0H0FKFzJd/vGToAmb4COURb1ke 2H5A== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o206si527007oih.143.2020.02.10.11.00.34; Mon, 10 Feb 2020 11:00:46 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727747AbgBJS7I (ORCPT + 99 others); Mon, 10 Feb 2020 13:59:08 -0500 Received: from foss.arm.com ([217.140.110.172]:37732 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727043AbgBJS7I (ORCPT ); Mon, 10 Feb 2020 13:59:08 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E06941FB; Mon, 10 Feb 2020 10:59:07 -0800 (PST) Received: from localhost (unknown [10.37.6.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 64BA93F68F; Mon, 10 Feb 2020 10:59:07 -0800 (PST) Date: Mon, 10 Feb 2020 18:59:05 +0000 From: Mark Brown To: Brent Lu Cc: alsa-devel@alsa-project.org, Support Opensource , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , linux-kernel@vger.kernel.org, cychiang@google.com, mac.chiang@intel.com Subject: Re: [PATCH] ASoC: da7219: check SRM lock in trigger callback Message-ID: <20200210185905.GD14166@sirena.org.uk> References: <1581322611-25695-1-git-send-email-brent.lu@intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="76DTJ5CE0DCVQemd" Content-Disposition: inline In-Reply-To: <1581322611-25695-1-git-send-email-brent.lu@intel.com> X-Cookie: No lifeguard on duty. User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --76DTJ5CE0DCVQemd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 10, 2020 at 04:16:51PM +0800, Brent Lu wrote: > Intel sst firmware turns on BCLK/WCLK in START Ioctl call which timing is > later than the DAPM SUPPLY event handler da7219_dai_event is called (in > PREPARED state). Therefore, the SRM lock check always fail. >=20 > Moving the check to trigger callback could ensure the SRM is locked before > DSP starts to process data and avoid possisble noise. Independently of any other discussion trigger is expected to run very fast so doesn't feel like a good place to do this - given that we're talking about doing this to avoid noise the mute operation seems like a more idiomatic place to do this, it exists to avoid playing back glitches from the digitial interface during startup. --76DTJ5CE0DCVQemd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl5Bp/kACgkQJNaLcl1U h9AW9ggAhE+Uf05vhaF0QzQQUHbDzslATig+bVtp+hnoVHtcvBpIiJfssALCeBlO 9ax23eqKKLc71AGPWz+0Q/SFXNKtQks8EcCVb3E7DtHCPuME2XweuKpUP3cChyIR PGC0auE4jAhRQYfUCHr/0h1mllN5eVB+CPIkvdlomAXdKVIIHh+RDfcWNzchlBqu iv7Z6JB30FDe21lVXVuVUsDCvRL/bGpq7Puo2gMlxbj/q0ZjHuUzzNxbbAb8qPQu Ck4FI/mgE+qoxGr1LvEmRU8/X9Z0FGRoA8j99UeYftSt338wTsYrMw9Q3vrrAwOJ vbWjkVfV4UqRZbk8c5Bm8D1weiYu/A== =kh32 -----END PGP SIGNATURE----- --76DTJ5CE0DCVQemd--