From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Luca Weiss <luca@z3ntu.xyz>, linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/11] arm64: dts: qcom: Add SM7225 device tree
Date: Sun, 3 Oct 2021 13:32:06 +0200 [thread overview]
Message-ID: <cef85f62-7d26-593a-0d71-c5513254e2c5@somainline.org> (raw)
In-Reply-To: <20211003083141.613509-11-luca@z3ntu.xyz>
On 03.10.2021 10:31, Luca Weiss wrote:
> The Snapdragon 750G (sm7225) is software-wise very similar to Snapdragon
> 690 (sm6350) with minor differences in clock speeds and as added here,
> it uses the Kryo 570 instead of Kryo 560.
>
> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> ---
> arch/arm64/boot/dts/qcom/sm7225.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/sm7225.dtsi
>
> diff --git a/arch/arm64/boot/dts/qcom/sm7225.dtsi b/arch/arm64/boot/dts/qcom/sm7225.dtsi
> new file mode 100644
> index 000000000000..7b2a002ca7ff
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm7225.dtsi
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) 2021, Luca Weiss <luca@z3ntu.xyz>
> + */
> +
> +#include "sm6350.dtsi"
> +
> +/* SM7225 uses Kryo 570 instead of Kryo 560 */
> +&CPU0 { compatible = "qcom,kryo570"; };
> +&CPU1 { compatible = "qcom,kryo570"; };
> +&CPU2 { compatible = "qcom,kryo570"; };
> +&CPU3 { compatible = "qcom,kryo570"; };
> +&CPU4 { compatible = "qcom,kryo570"; };
> +&CPU5 { compatible = "qcom,kryo570"; };
> +&CPU6 { compatible = "qcom,kryo570"; };
> +&CPU7 { compatible = "qcom,kryo570"; };
>
As we discussed in private, we discovered after some poking on the Xperia 10 III and FP4, Qualcomm decided to use the "lagoon" codename for at least 3 SoCs, two of which are 6350 and 7225, with the third (and possibly more, eh...) yet to be discovered. For now we can tell the max GPU clock is over 50% higher on the 7225, but we'll get to know more differences as we progress forward.
Reviewed-by: Konrad Dybcio <konrad.dybcio@somainline.org>
Konrad
next prev parent reply other threads:[~2021-10-03 11:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 8:31 [PATCH 00/11] Initial Fairphone 4 support Luca Weiss
2021-10-03 8:31 ` [PATCH 01/11] clk: qcom: add select QCOM_GDSC for SM6350 Luca Weiss
2021-10-03 11:21 ` Konrad Dybcio
2021-10-03 8:31 ` [PATCH 02/11] dt-bindings: regulator: qcom,rpmh: Add compatible for PM6350 Luca Weiss
2021-10-03 8:31 ` [PATCH 03/11] regulator: qcom-rpmh: Add PM6350 regulators Luca Weiss
2021-10-04 12:37 ` Mark Brown
2021-10-04 20:44 ` Luca Weiss
2021-10-04 21:18 ` Mark Brown
2021-10-03 8:31 ` [PATCH 04/11] dt-bindings: pinctrl: qcom,pmic-gpio: Add compatible for PM6350 Luca Weiss
2021-10-03 8:31 ` [PATCH 05/11] pinctrl: qcom: spmi-gpio: " Luca Weiss
2021-10-03 8:31 ` [PATCH 06/11] arm64: dts: qcom: Add PM6350 PMIC Luca Weiss
2021-10-03 11:23 ` Konrad Dybcio
2021-10-03 8:31 ` [PATCH 07/11] arm64: dts: qcom: sm6350: add debug uart Luca Weiss
2021-10-03 8:31 ` [PATCH 08/11] dt-bindings: arm: cpus: Add Kryo 570 CPUs Luca Weiss
2021-10-03 8:31 ` [PATCH 09/11] dt-bindings: arm: qcom: Document sm7225 and fairphone,fp4 board Luca Weiss
2021-10-03 8:31 ` [PATCH 10/11] arm64: dts: qcom: Add SM7225 device tree Luca Weiss
2021-10-03 11:32 ` Konrad Dybcio [this message]
2021-10-03 8:31 ` [PATCH 11/11] arm64: dts: qcom: sm7225: Add device tree for Fairphone 4 Luca Weiss
2021-10-03 11:35 ` Konrad Dybcio
2021-10-31 22:10 ` [PATCH 00/11] Initial Fairphone 4 support Pavel Machek
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=cef85f62-7d26-593a-0d71-c5513254e2c5@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).