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 A859BC43219 for ; Thu, 16 Dec 2021 14:19:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237862AbhLPOTN (ORCPT ); Thu, 16 Dec 2021 09:19:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41122 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229583AbhLPOTL (ORCPT ); Thu, 16 Dec 2021 09:19:11 -0500 Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7554C061574; Thu, 16 Dec 2021 06:19:10 -0800 (PST) Received: by mail-lf1-x12c.google.com with SMTP id t3so3560708lfe.12; Thu, 16 Dec 2021 06:19:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=FHZhtH3DW7AMrBjP8iVuxcvAkwhLC1m6PQhYldA9iJU=; b=kfQna7lwKWEWNyGl0m+WM04u4GvDzlfWdVJpaVjT3VLpr11FElsgNikURpISaLmqEB gSnfcAyYPclS/JMQBjs4BWeC4liYjwwJhGaI2CLj9zwVCtQp20VEezdXRdvXOfU+rQv+ cvdiG+BIckrRWvJ5LmWc6gi1KqhH5V1mE4tW41nr4+IFwNca4fR7ttL4xlWwn74TndKS G0whMZLLYcMsAAhjjKd4W8N2DSbx8f8iAVMtBkeyqMXniFfccMFxE6qkDTG53a+wbF/W fUHDrFY0WxEr+0Me59Iq1ISBYx2DSYnRx5jkh9GCiG6ldF+F7h4CTLIk/j1S9Ue9eW4l GW3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FHZhtH3DW7AMrBjP8iVuxcvAkwhLC1m6PQhYldA9iJU=; b=EKww2pebI/8EdJ2mCFlg0xUlm5l1n0Sv0XJDK0pCnBHi/RVg6O18cKNBrrcUKaxS+Q 7KC2rm/YnIR+aHINg09IfFWdfD/agGbk9uMQesP1eOh1sJ3u62oS0M4lqoqC+bYBLqII j4jAw0amS7Wjpbp1IY4Z5eIdrb+S1o/NTJ7A209n4BW6QIu25LA/UfCQN6TBwwwNl2gx HdGpQkWNT5FqNMYOxI8ffFYbS1xyj/5U3bu02eiw7XjgzGvCLdQeWOsxPfraIuDYZFom UQ58Tx1zCdMGzquE12BygpWzosJgyTe4nAHJgqVi0csXSuGzDG6c1FVEfM+yMwW8WvD8 VgPQ== X-Gm-Message-State: AOAM531y0OcgijHp5GgxhVXHW4hga+7QtuR2ZKpuBuJB6iBE/lXiJEaP IKNyvDXGrI3RuEZ5ThhVzEA= X-Google-Smtp-Source: ABdhPJwTCLw6X+g8WZv+7SknvWAEs+qjM7J+ZiSnSsKS4sTnaSQels7ZUzqMKyR6w73ajpLDsSHcBA== X-Received: by 2002:a19:8c48:: with SMTP id i8mr14971511lfj.179.1639664349109; Thu, 16 Dec 2021 06:19:09 -0800 (PST) Received: from [192.168.2.145] (94-29-63-156.dynamic.spd-mgts.ru. [94.29.63.156]) by smtp.googlemail.com with ESMTPSA id k14sm1148653ljk.57.2021.12.16.06.19.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Dec 2021 06:19:08 -0800 (PST) Subject: Re: [PATCH v16 00/40] NVIDIA Tegra power management patches for 5.17 To: Thierry Reding Cc: Jonathan Hunter , Ulf Hansson , Viresh Kumar , Stephen Boyd , Peter De Schrijver , Mikko Perttunen , Lee Jones , =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= , Nishanth Menon , Adrian Hunter , Michael Turquette , linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org, linux-pwm@vger.kernel.org, linux-mmc@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-clk@vger.kernel.org, David Heidelberg References: <20211130232347.950-1-digetx@gmail.com> <6baf6013-fbb2-b42f-5b26-2d10a2ca9374@gmail.com> From: Dmitry Osipenko Message-ID: Date: Thu, 16 Dec 2021 17:19:07 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 16.12.2021 16:14, Thierry Reding пишет: > On Wed, Dec 15, 2021 at 07:11:53PM +0300, Dmitry Osipenko wrote: >> 15.12.2021 18:55, Thierry Reding пишет: >>> On Wed, Dec 01, 2021 at 02:23:07AM +0300, Dmitry Osipenko wrote: >>>> This series adds runtime PM support to Tegra drivers and enables core >>>> voltage scaling for Tegra20/30 SoCs, resolving overheating troubles. >>>> >>>> All patches in this series are interdependent and should go via Tegra tree >>>> for simplicity. >>> >>> So these can be applied in any order without breaking anything? >> >> Please notice that the word is *inter* dependent, not *in* dependent. >> >> There is a build dependency for the patches. The first two "soc/tegra" >> must be applied first. > > Okay, so I've separated the first two patches out into a separate stable > branch that I can share between the Tegra and drm/tegra trees to pull in > the build dependency and then I've applied the driver patches to those > two trees and I've verified that the two branches build correctly. I've > not done any runtime testing, but I'll trust you on that. I only compile-tested VIC and NVDEC drivers, but they should be okay, and thus, everything should be good. >> The "soc/tegra: pmc: Enable core domain support for Tegra20 and Tegra30" >> *must* be the last applied patch if we want to preserve bisectability. >> The core voltage scaling can be enabled only once all the drivers got >> the power management support. >> >> The rest could be applied out-of-order. > > One last remaining question: I don't think I can apply that one patch if > it requires that all the others are enabled first because it would > basically create a circular dependency. > > Can I pick up the final 7 patches (the DT ones) independently of that > one patch without things breaking? If so, one option we could try is to > wait for both Tegra and drm/tegra trees to get merged into v5.17-rc1 and > then send that one patch (which is only a 4-line diff) right after > v5.17-rc1 so that it makes it into v5.17-rc2. That avoids the circular > dependency and should get everything enabled for v5.17. > > Do you see any problems with that? Deferring that one patch till v5.17-rc2 will work, thank you.