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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4FF7DFA3740 for ; Thu, 27 Oct 2022 16:34:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234923AbiJ0Qey (ORCPT ); Thu, 27 Oct 2022 12:34:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43164 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235951AbiJ0Qeu (ORCPT ); Thu, 27 Oct 2022 12:34:50 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3D42820F72 for ; Thu, 27 Oct 2022 09:34:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666888488; x=1698424488; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=ReW4mTL/Qrx5Ie4wYNRyXd3fjjAfU0EotIXdjdbjQJo=; b=TiG5/djuNiwXm9UndN9KcIMicSqCLxVD9ZEgVcp2Ve3zA/qCPEHn7bGL /TEqM651zPGCQCLNSbv9rd6pghCulApu8o6zAkdUArkAQ1Fa77MzGQziB 5tEHnYZ8ZKQOY+PPx/q4e24PjggBj4YT8KMDTlB1gDXHBSHKnDgte/z5d YJGOy4mhYjXWkVurvY1yvsORfUHa2HrN1Yw0G62S+SQdWtgyxifbak0Ge ZOj7/YldmeaVHbHA0HLb2K1IqI/VbyhcJiTSSdPfNDO/wZijAogzvCKzy 3vUM0OzytpIKVzPGB9Lrpw6B6T7wzWiU7w+Fav2kyMC85uKZXV1d6qgCq w==; X-IronPort-AV: E=McAfee;i="6500,9779,10513"; a="370339955" X-IronPort-AV: E=Sophos;i="5.95,218,1661842800"; d="scan'208";a="370339955" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Oct 2022 09:34:47 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10513"; a="807513294" X-IronPort-AV: E=Sophos;i="5.95,218,1661842800"; d="scan'208";a="807513294" Received: from djohn1-mobl1.amr.corp.intel.com (HELO [10.212.54.86]) ([10.212.54.86]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Oct 2022 09:34:46 -0700 Message-ID: Date: Thu, 27 Oct 2022 12:34:45 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.2.2 Subject: Re: [BUG][v6.1-rc2] [SOF] max98373 i2c-MX98373:00: Runtime PM usage count underflow! To: Lukasz Majczak , Mark Brown , Liam Girdwood Cc: alsa-devel@alsa-project.org, upstream@semihalf.com, Curtis Malainey , Takashi Iwai , LKML , Guenter Roeck References: Content-Language: en-US From: Pierre-Louis Bossart In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/27/22 12:12, Lukasz Majczak wrote: > Hi, > > I have noticed Runtime PM usage count underflow on my Chromebook (12th > Gen Intel(R) Core(TM) i3-1215U) running vanilla v6.1-rc2: > > [ 7.558178] max98373 i2c-MX98373:00: Runtime PM usage count underflow! > [ 7.558188] max98373 i2c-MX98373:01: Runtime PM usage count underflow! > [ 7.558206] snd-soc-dummy snd-soc-dummy: Runtime PM usage count underflow! > [ 7.558421] snd-soc-dummy snd-soc-dummy: Runtime PM usage count underflow! > > Link to the full dmesg: > https://gist.github.com/semihalf-majczak-lukasz/d6a6d61d5937f762a524ed50fed93f25 You need to apply this: [PATCH] Revert "ASoC: soc-component: using pm_runtime_resume_and_get instead of pm_runtime_get_sync"