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 7C5E8ECAAD1 for ; Tue, 30 Aug 2022 05:40:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229802AbiH3Fku (ORCPT ); Tue, 30 Aug 2022 01:40:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59582 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229585AbiH3Fkr (ORCPT ); Tue, 30 Aug 2022 01:40:47 -0400 Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6064684EE0 for ; Mon, 29 Aug 2022 22:40:45 -0700 (PDT) Received: by mail-pl1-x62d.google.com with SMTP id f24so7327154plr.1 for ; Mon, 29 Aug 2022 22:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=/AXxGSKHD9gHotHgPkcKQJDg7QFNUaxs4G1mHC7A7EM=; b=GZdC/rr42yOk2UFksu/R3G3rPbI2L9UJtIKaPIria2iMwQfoKStV/mLDhnoeMiWHwT 7u4Y7HYJD6VAZ7PmsZW1KcHuHnNAOtRAHAUA6mpvhVj2vskhNKnc6law/JlK2fu3+pVh 6jRCrLuXzaGl7Gi8XzAeWCwDHtOEqwzI24b6Q7tiUqR9iVshq/DN9yD5dDLLaN7CUk+s 12EjTAip3/Js0sVZ4iRH7jTIuo5GrPzOpZygmQPcTvqPnbB1R1GPTTRfm1qiToyL8Gy/ pPBfE1kQK6420hWrFUeTgvDk3zhmmjeWmWzF8Tb9TTOpKwTIjFQJ3O79Lgo5ZgIf9uQL hXFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=/AXxGSKHD9gHotHgPkcKQJDg7QFNUaxs4G1mHC7A7EM=; b=cUw9fu9cIZbbu6SaYjjRMJ59HgEqea6pYR6vumfGYr2QI14il28xZ6lmDVMsMYMD7+ AnDFoWYUZrQXLeNgcwrvtUeDa+ggsk1BTwNqI+MVrtgQMjc7tW+xDnwmFF6XGeDpl9E4 0zDSNWzL7p8dj1WUnbMQeXffdwYNhOqxV1R9a9rGQzVAUJXA/us6SI1GoLzccdZkeoZv S+9VqnV28KvJS7mG5LgPhbxLibqn479FesYhgd2X+cEpAfhlZHBSkm1Y411FraidcPuK W0lSpVcy549OoRPTnnJ6pj9izOTIh/YjVLX+oSPbBatnAYPNx1RC4cPzvdTdulO3uPhZ U5ow== X-Gm-Message-State: ACgBeo26FX4Mnw086S9LpqlKIr8qL/Z8ttQ3I94IcmwY9oYCa8qUli9+ OKlsGKXqnhA/b/8kqAVdjxchPw== X-Google-Smtp-Source: AA6agR4fz8JV9EJ3UVqdHB6K8oLv+ZN6CiYLpiAiB1jb8u1lfRtFBL6/xYco7Xh2MRfH9OHHAYnhzw== X-Received: by 2002:a17:902:d4c9:b0:172:f480:bdd with SMTP id o9-20020a170902d4c900b00172f4800bddmr19669902plg.170.1661838044911; Mon, 29 Aug 2022 22:40:44 -0700 (PDT) Received: from localhost ([122.171.18.80]) by smtp.gmail.com with ESMTPSA id l5-20020a170903120500b00174c1855cd9sm3787283plh.267.2022.08.29.22.40.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 Aug 2022 22:40:44 -0700 (PDT) Date: Tue, 30 Aug 2022 11:10:42 +0530 From: Viresh Kumar To: Bjorn Andersson Cc: Manivannan Sadhasivam , Bjorn Andersson , Andy Gross , Krzysztof Kozlowski , "Rafael J. Wysocki" , Rob Herring , Vincent Guittot , Johan Hovold , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [RFC PATCH 0/4] cpufreq: qcom-hw: Move clocks to CPU node Message-ID: <20220830054042.akj7pf366inelvpo@vireshk-i7> References: <20220715160933.GD12197@workstation> <20220718015742.uwskqo55qd67jx2w@vireshk-i7> <20220801023756.76jswkbwivuntqof@vireshk-i7> <20220830032456.z4olnogsyg32vhiz@builder.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220830032456.z4olnogsyg32vhiz@builder.lan> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29-08-22, 22:24, Bjorn Andersson wrote: > Conceptually, it sounds like a good idea to express the clock feeding > the CPU clusters, which is controlled by the OSM/EPSS. But do you > expect the OPP framework to actually do something with the clock, or > just to ensure that the relationship is properly described? No, the OPP core will never try to set the clock rate in your case, though it will do clk_get(). > FWIW, the possible discrepancy between the requested frequency and the > actual frequency comes from the fact that OSM/EPSS throttles the cluster > frequency based on a number of different factors (thermal, voltages > ...). > This is reported back to the kernel using the thermal pressure > interface. It would be quite interesting to see some investigation in > how efficient the kernel is at making use of this feedback. -- viresh