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 Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 73F31CDB47E for ; Wed, 18 Oct 2023 05:30:05 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 34B51857; Wed, 18 Oct 2023 07:29:12 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 34B51857 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1697607002; bh=1/mW/bzeFJ8Aw6FXaWiwdS9K7P5WuBUcS5pi6y8F3Xw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe:From; b=cNooy7mGpaOYf26u+/SdXmFKOTl2p8Iu5ZXBA9U/wT1XR7grhtaBGPa8w4xx1eTCi WoRdoKswlkILCA0W9lhZ9cI2FEsxgoD06pqQSRMXCGHjgs9/2oICJ/5oDTvFRLhIdZ 6tcqfvBpBRNT2TxcinhRm+c/hWHZKLwD9lWFBgB8= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 5CD12F80553; Wed, 18 Oct 2023 07:29:00 +0200 (CEST) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id E5905F8025F; Wed, 18 Oct 2023 07:28:59 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 2A6D0F8025F; Wed, 18 Oct 2023 07:23:55 +0200 (CEST) Received: from muru.com (muru.com [72.249.23.125]) by alsa1.perex.cz (Postfix) with ESMTP id E0316F8019B for ; Wed, 18 Oct 2023 07:23:49 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz E0316F8019B Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 45DE78027; Wed, 18 Oct 2023 05:23:47 +0000 (UTC) Date: Wed, 18 Oct 2023 08:23:45 +0300 From: Tony Lindgren To: Andreas Kemnade Cc: =?utf-8?B?UMOpdGVy?= Ujfalusi , bcousson@baylibre.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz, tiwai@suse.com, jarkko.nikula@bitmer.com, dmitry.torokhov@gmail.com, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH 1/3] ASoC: ti: omap-mcbsp: Ignore errors for getting fck_src Message-ID: <20231018052345.GK34982@atomide.com> References: <20230705190324.355282-1-andreas@kemnade.info> <20230705190324.355282-2-andreas@kemnade.info> <7d58d52d-2087-45af-b29e-2515b63ead13@gmail.com> <20230920063353.GQ5285@atomide.com> <20230921121626.GT5285@atomide.com> <20231006102348.GK34982@atomide.com> <20231006213003.0fbac87a@aktux> <20231007062518.GM34982@atomide.com> <20231015234815.637f5c14@aktux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231015234815.637f5c14@aktux> Message-ID-Hash: J3JWI3YR4WSELLYAVXKNL43AJV322NSH X-Message-ID-Hash: J3JWI3YR4WSELLYAVXKNL43AJV322NSH X-MailFrom: tony@atomide.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: * Andreas Kemnade [231015 21:48]: > On Sat, 7 Oct 2023 09:25:18 +0300 > Tony Lindgren wrote: > > If so then the following might be a fix, not familiar with runtime PM > > done by ASoC though and not sure if some kind of locking would be > > needed here. > > > just checked: that one fixes the regression. runtime suspends again. OK good to hear. So is there some fixes tag for this one or where did this start happening? I'm not quite following how the dropping of platform data could have affected this, maybe it just hid the problem because of returning early? Regards, Tony