From: Chukun Pan <amadeus@jmu.edu.cn>
To: dmitry.baryshkov@linaro.org
Cc: amadeus@jmu.edu.cn, andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, konrad.dybcio@linaro.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: qcom: ipq6018: separate CPU OPP tables
Date: Thu, 1 Feb 2024 12:00:20 +0800 [thread overview]
Message-ID: <20240201040020.73949-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <CAA8EJpoMXkAd3EBf=p+nig8VWzY9tiUAWhfGJn3XOX1uSa=22Q@mail.gmail.com>
Hi, Dmitry
> Straight to the board files, please, no need for additional includes.
Is it possible to move the mp5496 node to mp5496.dtsi?
Because ipq9574 also uses this mp5496 pmic.
&rpm_requests {
regulators {
compatible = "qcom,rpm-mp5496-regulators";
mp5496_s1: s1 {
regulator-min-microvolt = <725000>;
regulator-max-microvolt = <1075000>;
status = "disabled";
};
mp5496_s2: s2 {
regulator-min-microvolt = <725000>;
regulator-max-microvolt = <1062500>;
status = "disabled";
};
mp5496_l2: l2 {
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
status = "disabled";
};
};
};
> From your patches I had the feeling that you still want to limit the
> high-frequency OPP entries if there is no PMIC.
Sorry for this misunderstanding, the cpu max frequency is determined
by the cpu_speed_bin. It's just that the efuse of the board I have
without pmic are all 1.2GHz.
Thanks,
Chukun
--
2.25.1
next prev parent reply other threads:[~2024-02-01 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 10:20 [PATCH 1/3] arm64: dts: qcom: ipq6018: separate CPU OPP tables Chukun Pan
2024-01-31 10:20 ` [PATCH 2/3] arm64: dts: qcom: ipq6018: add ipq6000 " Chukun Pan
2024-01-31 12:07 ` Bryan O'Donoghue
2024-01-31 12:26 ` Dmitry Baryshkov
2024-01-31 10:20 ` [PATCH 3/3] arm64: dts: qcom: ipq6018: add CPU OPP tables for 1.5GHz Chukun Pan
2024-01-31 12:25 ` [PATCH 1/3] arm64: dts: qcom: ipq6018: separate CPU OPP tables Dmitry Baryshkov
2024-02-01 3:08 ` Chukun Pan
2024-02-01 3:15 ` Dmitry Baryshkov
2024-02-01 4:00 ` Chukun Pan [this message]
2024-02-01 4:38 ` Dmitry Baryshkov
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=20240201040020.73949-1-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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+dt@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