Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
From:   Bjorn Andersson <andersson@kernel.org>
To:     agross@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org,
        krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
        linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org, Robert Marko <robimarko@gmail.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: ipq6018: use CPUFreq NVMEM
Date:   Sat,  2 Dec 2023 20:54:54 -0800
Message-ID: <170157925830.1717511.5547305071355382777.b4-ty@kernel.org>
In-Reply-To: <20231021120048.231239-1-robimarko@gmail.com>
References: <20231021120048.231239-1-robimarko@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Sat, 21 Oct 2023 14:00:07 +0200, Robert Marko wrote:
> IPQ6018 comes in multiple SKU-s and some of them dont support all of the
> OPP-s that are current set, so lets utilize CPUFreq NVMEM to allow only
> supported OPP-s based on the SoC dynamically.
> 
> As an example, IPQ6018 is generaly rated at 1.8GHz but some silicon only
> goes up to 1.5GHz and is marked as such via an eFuse.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: qcom: ipq6018: use CPUFreq NVMEM
      commit: 83afcf14edb9217e58837eb119da96d734a4b3b1

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