Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp659777pxu; Tue, 1 Dec 2020 23:22:16 -0800 (PST) X-Google-Smtp-Source: ABdhPJyVK72N8oqo4ePXl722eVHZDdV91BX7j0xGtB+9b2sHPWbL75ThzE9d/CqAkluVBVUXwEAK X-Received: by 2002:a17:906:f153:: with SMTP id gw19mr1113593ejb.272.1606893736061; Tue, 01 Dec 2020 23:22:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606893736; cv=none; d=google.com; s=arc-20160816; b=EdxXbzsncSXXgnUIKwhNAwn7R/lAfuIwYJ8TFAtztDNzmROFvBT6j6TccE8sd3dbxt KYVYgPS/S2tkC55BOSkj4O4uXYHzRu1Lopsr15O6GpO41xEyZ+WIr3c15uoU5nuoRC8v H0+6w6n804mdulag63pX13mDWn3naYsP0PUorNmWHz7jliFac7gG0+bQLevtEmVAyeaM Lg6QNDitYPFxvAhvolcniGkJCD+IhlhWL3BUsgK1NVhT8YGdEH+l6H1uM9WWHhoofeXG 2hoTlAPr5dnn13yza7rxJFMkouVfY0nuwiN5e1+HMWaWFaKdRip8CnsdTyT8AJ/GbajE +zkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature:date; bh=WtWEe8C3wFhUViS/1YKMgRK/uIrKBk3YPaXwDfTCLyc=; b=kTGeU8lTjpRgL+m+fM1EspiRWwlsXxxR/Phk1fDW7EK/5cTBOK3X2ZkP7T+/GT9Zc2 D6pZCu0yy7bFPjVRxK0zsmeAvf5Zes1LMyu9k5zyzLkVhx7A83+wLYR+ms7eyAHp+4m0 BnNuHdYneh/nmM2/+kxL9Xe8XAoHCt9HsAPH/bvMsQ5xzOiY9FUYtSdG6yMHjeGzdbUJ P1tyLnsOQ6CXrej+p0/2wgt1ZXLELZgPol1tW8MEenr3VCLzjiwEaW1MOLIPTugsxvuF BrxzhIICMZW7iTkQzq/r+DZgvM/CxPlEP8+vZbJEbW+UEiYuj1gNeF1DZ9fsyh5IEHmG S0/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vZHIb0b5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n12si546137eds.188.2020.12.01.23.21.52; Tue, 01 Dec 2020 23:22:16 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vZHIb0b5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387571AbgLBHU2 (ORCPT + 99 others); Wed, 2 Dec 2020 02:20:28 -0500 Received: from mail.kernel.org ([198.145.29.99]:42950 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbgLBHU1 (ORCPT ); Wed, 2 Dec 2020 02:20:27 -0500 Date: Wed, 2 Dec 2020 12:49:42 +0530 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606893587; bh=X4r+iT7gA+qhcSzwcOzyTZ4y8Ixf+TG2omJrcZ75MQI=; h=From:To:Cc:Subject:References:In-Reply-To:From; b=vZHIb0b5Hs/sFJWT6xZsyHskbCCcI1rZC8lJtJ/hWPaXKPn7ZjXC8AR599zWRNAxk 0qyp0ewnCHhC5ex8Xu3MNTbOMaTJIBowrTfCH9Qt1WS00iH4wEjRolFUpP8XXFVA3x dFOIOUphIrKPAo8dtVhBy0MfB8Ysp3akf4b/vTro= From: Vinod Koul To: Bard Liao Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, jank@cadence.com, srinivas.kandagatla@linaro.org, rander.wang@linux.intel.com, ranjani.sridharan@linux.intel.com, hui.wang@canonical.com, pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com, mengdong.lin@intel.com, bard.liao@intel.com Subject: Re: [PATCH] soundwire: master: use pm_runtime_set_active() on add Message-ID: <20201202071942.GH8403@vkoul-mobl> References: <20201124130742.10986-1-yung-chuan.liao@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201124130742.10986-1-yung-chuan.liao@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24-11-20, 21:07, Bard Liao wrote: > From: Pierre-Louis Bossart > > The 'master' device acts as a glue layer used during bus > initialization only, and it needs to be 'transparent' for pm_runtime > management. Its behavior should be that it becomes active when one of > its children becomes active, and suspends when all of its children are > suspended. > > In our tests on Intel platforms, we routinely see these sort of > warnings on the initial boot: > > [ 21.447345] rt715 sdw:3:25d:715:0: runtime PM trying to activate > child device sdw:3:25d:715:0 but parent (sdw-master-3) is not active > > This is root-caused to a missing setup to make the device 'active' on > probe. Since we don't want the device to remain active forever after > the probe, the autosuspend configuration is also enabled at the end of > the probe - the device will actually autosuspend only in the case > where there are no devices physically attached. In practice, the > master device will suspend when all its children are no longer active. Applied, thanks -- ~Vinod