From: Robert Marko <robimarko@gmail.com>
To: Chukun Pan <amadeus@jmu.edu.cn>, Bjorn Andersson <andersson@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] arm64: dts: qcom: ipq6018: add 1.2GHz CPU Frequency
Date: Wed, 6 Mar 2024 21:38:33 +0100 [thread overview]
Message-ID: <0b032929-f525-4b2e-a176-1a447cf0fa7f@gmail.com> (raw)
In-Reply-To: <20240306140306.876188-2-amadeus@jmu.edu.cn>
On 06. 03. 2024. 15:03, Chukun Pan wrote:
> Some IPQ6000 SoCs have CPU frequencies up to 1.2GHz,
> so add this frequency.
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> ---
> arch/arm64/boot/dts/qcom/ipq6018.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/ipq6018.dtsi b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
> index 4e29adea570a..7fdb119083a2 100644
> --- a/arch/arm64/boot/dts/qcom/ipq6018.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
> @@ -119,6 +119,13 @@ opp-1056000000 {
> clock-latency-ns = <200000>;
> };
>
> + opp-1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <850000>;
Can I ask the source of this voltage level?
Because, its not present in the downstream QCA tree at all.
Regards,
Robert
> + opp-supported-hw = <0x4>;
> + clock-latency-ns = <200000>;
> + };
> +
> opp-1320000000 {
> opp-hz = /bits/ 64 <1320000000>;
> opp-microvolt = <862500>;
next prev parent reply other threads:[~2024-03-06 20:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 14:03 [PATCH v2 0/4] arm64: dts: qcom: ipq6018: rework CPU Frequency Chukun Pan
2024-03-06 14:03 ` [PATCH v2 1/4] arm64: dts: qcom: ipq6018: add 1.2GHz " Chukun Pan
2024-03-06 14:33 ` Dmitry Baryshkov
2024-03-06 15:36 ` Chukun Pan
2024-03-06 19:34 ` Dmitry Baryshkov
2024-03-07 3:02 ` Chukun Pan
2024-03-07 7:29 ` Dmitry Baryshkov
2024-03-07 10:02 ` Chukun Pan
2024-03-07 10:13 ` Dmitry Baryshkov
2024-03-12 15:37 ` Kathiravan Thirumoorthy
2024-03-13 7:18 ` Chukun Pan
2024-03-13 9:32 ` Kathiravan Thirumoorthy
2024-03-06 16:20 ` Konrad Dybcio
2024-03-07 2:50 ` Chukun Pan
2024-03-06 20:38 ` Robert Marko [this message]
2024-03-07 3:26 ` Chukun Pan
2024-03-08 8:51 ` Robert Marko
2024-03-06 14:03 ` [PATCH v2 2/4] arm64: dts: qcom: ipq6018: add 1.5GHz " Chukun Pan
2024-03-06 14:36 ` Dmitry Baryshkov
2024-03-06 15:40 ` Chukun Pan
2024-03-06 19:36 ` Dmitry Baryshkov
2024-03-07 3:08 ` [PATCH v2 1/4] arm64: dts: qcom: ipq6018: add 1.2GHz " Chukun Pan
2024-03-06 16:20 ` [PATCH v2 2/4] arm64: dts: qcom: ipq6018: add 1.5GHz " Konrad Dybcio
2024-03-06 14:03 ` [PATCH v2 3/4] arm64: dts: qcom: ipq6018: move mp5496 regulator outside soc dtsi Chukun Pan
2024-03-06 14:38 ` Dmitry Baryshkov
2024-03-10 10:10 ` Chukun Pan
2024-03-06 14:03 ` [PATCH v2 4/4] arm64: dts: qcom: ipq6018-mp5496: add LDOA2 regulator Chukun Pan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b032929-f525-4b2e-a176-1a447cf0fa7f@gmail.com \
--to=robimarko@gmail.com \
--cc=amadeus@jmu.edu.cn \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox