Received: by 10.223.185.116 with SMTP id b49csp6125579wrg; Wed, 28 Feb 2018 04:32:32 -0800 (PST) X-Google-Smtp-Source: AG47ELszYcR3R22Om8R6KNWaKj7HWfwX+XxmXOzGM4XKFj0HsYfAOrgvH27p6OsLMwiATY827vny X-Received: by 10.98.254.6 with SMTP id z6mr409235pfh.155.1519821152212; Wed, 28 Feb 2018 04:32:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519821152; cv=none; d=google.com; s=arc-20160816; b=B+2EBQohiWjLdzHUIW9UqcHU1MTGFlIvd5m3xigL4uqGxRgSnPfsWsiV3OmIkNF5z2 nSST+HsOC0Acj+F+gJnco9jzMA3tOWGQDgM8W7y3paxavq49S9Sd/pI543n8nKv85Pt1 WnnhNY+nu5X5AiKquzDxM15TEJ3xaObmMn4LMSE7ye33r/HS+TGdz4qMaTdVgi83N2Fj BS7poX1/mifvxXuhtrGiZUmIhtphsSvBeTqqklzt68tkSH4XF53WpGU5z0WOyZUpoXxU a+z3eY5h3bHum3AJRdi/7OyYmp2srBsU4dwOzh2U9/u+jYxMY5FmTzNdYeJrS8RRgoCn BxjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=CCAUgPFKQ+2dA9VWxQqdMg2Q82DjQLQ1OylW+Hf74/c=; b=MOp5FqQVPqKqU5ZvKjRvaOBX3b0ptOUJOec9RQylBQ7TF5sbf/Po/f6/HyOZ8G0Xpp Z2xEWlpRlGD6zvxYYsHy4+gMxBpBcMt7QswGbMmPWwX4xVN4oR8ag5cepO4Plaamb6Tw eiXTKSkw63X6kRjVufTHqjqpMm2VDVqXDtW7xx89UsixPCy4Kks4Do8sai1BhESolW14 JCck+VzL4+fswGVoKI5m9ofYy/7L+7j9HCbgvNPOA2fnNDiqsWeDoghSnQXmreA/4V6W 4GCGuaCg525ajLZikAAiId+43S2OgKuUrFC58FbsjlVFnhcIClR89MCug4q/N1pqIN+D ChbQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=a/n1e7GZ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j6si1153925pfa.413.2018.02.28.04.32.14; Wed, 28 Feb 2018 04:32:32 -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; dkim=pass header.i=@chromium.org header.s=google header.b=a/n1e7GZ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752513AbeB1MaP (ORCPT + 99 others); Wed, 28 Feb 2018 07:30:15 -0500 Received: from mail-vk0-f42.google.com ([209.85.213.42]:38500 "EHLO mail-vk0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752340AbeB1MaN (ORCPT ); Wed, 28 Feb 2018 07:30:13 -0500 Received: by mail-vk0-f42.google.com with SMTP id s1so1331084vke.5 for ; Wed, 28 Feb 2018 04:30:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CCAUgPFKQ+2dA9VWxQqdMg2Q82DjQLQ1OylW+Hf74/c=; b=a/n1e7GZQ+8WH7HAfhaR0dDqyTi3Upx/3ECbcUytmzlHlxdSW+ttXCVmlaTv5oXPS7 FeUdFoJyQUdLBKcNE26doBIGzI9Y9VOsEnYsdpbJltLwtHwXcfpRCtM5SkmbC741DFyB lagPFFGCYAFj6lZ7YeS/5kertqjbpdzgyRUMM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CCAUgPFKQ+2dA9VWxQqdMg2Q82DjQLQ1OylW+Hf74/c=; b=bU4pG7LAH7068xkwH+ONGExPGoMH3hrEzUi9cDCfBA3uundSXTkIS4NoCefwS0LIXJ nsQ8OdVxvPhDnrfytwCCwQni0lm1+Ikbx2AdbaKZvfHoyN0/jVtP01Z/F9GiSik5Y+ka JNwCMog5lKECPoCIxa52VXpxBc4RbXlY2TrJxYveMCrzN6Vy8porkeuAsedOdXq9SN69 BDAx6L8o14wBAZdJqgtv5clEBEQsRxyBqNACB2Qp6xANg5QP1FnNAS6aZM2nqZRImF4S pS9z5RwnX2HW2nxMOwLm4oD/ZYaNARfu2pEoUu+b0mspiZVvHe9WLSqxhl3WvDsXWFJq Xy2g== X-Gm-Message-State: APf1xPDLt466LEa8L0OhbUA55EG3QCicbMKPEaYIBVfK/uR5a/u7th3q nrGzYpxEda3s88SA+kjDEokRzVhICl4= X-Received: by 10.31.54.212 with SMTP id d203mr12773602vka.16.1519821012684; Wed, 28 Feb 2018 04:30:12 -0800 (PST) Received: from mail-ua0-f174.google.com (mail-ua0-f174.google.com. [209.85.217.174]) by smtp.gmail.com with ESMTPSA id a187sm942635vkf.47.2018.02.28.04.30.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Feb 2018 04:30:11 -0800 (PST) Received: by mail-ua0-f174.google.com with SMTP id b13so1383898uam.10 for ; Wed, 28 Feb 2018 04:30:11 -0800 (PST) X-Received: by 10.159.52.101 with SMTP id s37mr13510823uab.24.1519821010668; Wed, 28 Feb 2018 04:30:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.0.99 with HTTP; Wed, 28 Feb 2018 04:29:50 -0800 (PST) In-Reply-To: References: <20180228111113.13639-1-jeffy.chen@rock-chips.com> From: Tomasz Figa Date: Wed, 28 Feb 2018 21:29:50 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] soc: rockchip: power-domain: remove PM clocks To: Geert Uytterhoeven Cc: Jeffy Chen , Linux Kernel Mailing List , Dmitry Torokhov , Robin Murphy , Heiko Stuebner , Caesar Wang , Elaine Zhang , "open list:ARM/Rockchip SoC..." , Geert Uytterhoeven , Linux ARM , Ulf Hansson Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, On Wed, Feb 28, 2018 at 9:17 PM, Geert Uytterhoeven wrote: > Hi Jeffy, > > On Wed, Feb 28, 2018 at 12:11 PM, Jeffy Chen wrote: >> Currently we are adding all of the attached devices' clocks as pm clocks >> and enable them when powering on the power domain. >> >> This seems unnecessary, because those clocks are already controlled in >> the devices' drivers with better error handling. >> >> Tested on my chromebook minnie(rk3288) and chromebook kevin(rk3399). >> >> Signed-off-by: Jeffy Chen > > Thanks for your patch! > > Just wondering: so you prefer to handle the clocks explicitly in all drivers, > instead of delegating this task to Runtime PM? Is it already possible to gate clocks immediately when the device idles, but defer turning the power domain off until time long enough to cover the power down and up latency elapses? Also, how about systems where runtime PM is disabled? I think that's one of the reasons we control the clocks explicitly in the drivers anyway. Best regards, Tomasz