Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Bjorn Andersson <andersson@kernel.org>
To:     robh+dt@kernel.org, rafael@kernel.org,
        Viresh Kumar <viresh.kumar@linaro.org>,
        krzysztof.kozlowski+dt@linaro.org,
        Manivannan Sadhasivam <mani@kernel.org>
Cc:     johan@kernel.org, linux-arm-msm@vger.kernel.org,
        linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
        linux-pm@vger.kernel.org
Subject: Re: (subset) [PATCH v7 0/4] qcom-cpufreq-hw: Add CPU clock provider support
Date:   Tue,  6 Dec 2022 12:19:25 -0600
Message-Id: <167035076342.3155086.18294541297387129551.b4-ty@kernel.org>
In-Reply-To: <20221117053145.10409-1-manivannan.sadhasivam@linaro.org>
References: <20221117053145.10409-1-manivannan.sadhasivam@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 17 Nov 2022 11:01:41 +0530, Manivannan Sadhasivam wrote:
> This series adds clock provider support to the Qcom CPUFreq driver for
> supplying the clocks to the CPU cores in Qcom SoCs.
> 
> The Qualcomm platforms making use of CPUFreq HW Engine (EPSS/OSM) supply
> clocks to the CPU cores. But this is not represented clearly in devicetree.
> There is no clock coming out of the CPUFreq HW node to the CPU. This created
> an issue [1] with the OPP core when a recent enhancement series was submitted.
> Eventhough the issue got fixed in the OPP framework in the meantime, that's
> not a proper solution and this series aims to fix it properly.
> 
> [...]

Applied, thanks!

[2/4] arm64: dts: qcom: sm8450: Supply clock from cpufreq node to CPUs
      commit: 8a8845e07b1164792a4dd5ad4d333d793828b366

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>