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 11DE3C54EE9 for ; Tue, 20 Sep 2022 10:28:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230005AbiITK2O (ORCPT ); Tue, 20 Sep 2022 06:28:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38490 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230124AbiITK2K (ORCPT ); Tue, 20 Sep 2022 06:28:10 -0400 Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1C4157198F for ; Tue, 20 Sep 2022 03:28:08 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id t190so2101411pgd.9 for ; Tue, 20 Sep 2022 03:28:07 -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:subject:date; bh=TcKUfJUCCOHTt6fn38EmcwoVIyI3UzCr5ChNl1GM+/4=; b=H09M6qwa+9VSmywU31/7TR0CMSMpMjxVwKxascARmgmZH5aTqDvkCcYQ6dCKtuXnDZ 3P9q7oCP1POU+EuA0XJlffC8rU8PXBey2Cj9HBklpwC1YN3K4PGpMNeMv5IPCjY7GZgw dYVEA7+3EYio0butF+EJ+cMNCY2Ga583g+uFLn9EfvYAVXqqf2DRudZPQo1Uop1RUnEn sVMZCVkgaRb2zDVuSEdwuhjq2kZmxm9lOWSF7Mp/e2fM8SfK79vnMRsnTnDMZpMGSupr pbDkRAv6+TuSp6cu5VYw1uEksDZXIkXAS1d5s0ucavEmWhP041aq5jA9ggap6X9jSgSf HiVw== 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:subject:date; bh=TcKUfJUCCOHTt6fn38EmcwoVIyI3UzCr5ChNl1GM+/4=; b=HUfxv6oZzPB5uV7Ze5KxPyblxDWAS2+0lRKtYG7HvgZIHJhIsvLxVqbR3klJeBPCgj HYf+Mc7ZLCnh7OsP1eq8uoZ3UJiLpEq6UvaRv7ofyxyVpuqicG46WDrffFfKrOa7efCT uCgy9fSA77MfQef6Lwq8u5UhFbHJNu83tg0SsjK3FlvUwB9JGk4Xis7ya+vDmbzepxVY IcQDy/e5XPzcksujDtqAUsL15ILe2meIcBUFDVb9j3TSpZiFtSvUeD64JSrhXW/JrNnm YwcWNLGa/97xxAi3juYdNs0a05G9YTfitrxc8h/6JiMyWO7MqUSgSABLefBJZAqPd9bB dWEw== X-Gm-Message-State: ACrzQf0Sag3G1vQ8qzflkT/BGYQSFm8gkUVcUhvOjas32ZTb8IX96SdT M7spOZxZUnj9zcAD0o6ZzDmzMCyvOKAWxA== X-Google-Smtp-Source: AMsMyM760oD16hXPs+4JP05QAFv5/6I/Juk3967sI0Zs6Yd78edT73FvzRS2x3JB8oI+CSc0kKkYgA== X-Received: by 2002:a05:6a00:158f:b0:546:b777:af17 with SMTP id u15-20020a056a00158f00b00546b777af17mr22701543pfk.51.1663669687117; Tue, 20 Sep 2022 03:28:07 -0700 (PDT) Received: from localhost ([122.171.20.238]) by smtp.gmail.com with ESMTPSA id s17-20020a17090302d100b0016c9e5f290esm1089268plk.10.2022.09.20.03.28.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Sep 2022 03:28:06 -0700 (PDT) Date: Tue, 20 Sep 2022 15:58:03 +0530 From: Viresh Kumar To: Manivannan Sadhasivam Cc: Bjorn Andersson , 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: <20220920102803.rqj44xrz2szj3tqi@vireshk-i7> References: <20220715160933.GD12197@workstation> <20220718015742.uwskqo55qd67jx2w@vireshk-i7> <20220801023756.76jswkbwivuntqof@vireshk-i7> <20220830032456.z4olnogsyg32vhiz@builder.lan> <20220830054042.akj7pf366inelvpo@vireshk-i7> <20220830062050.GA7066@workstation> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220830062050.GA7066@workstation> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30-08-22, 11:50, Manivannan Sadhasivam wrote: > On Tue, Aug 30, 2022 at 11:10:42AM +0530, Viresh Kumar wrote: > > 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(). > > > > Okay. Then I think it is a fair argument to make qcom-cpufreq-hw as the > clock provider for CPUs. > > I will send the RFC soon. Ping. -- viresh