This series introduces support for the Qualcomm SM7125 and the Xiaomi
SM7125 platform.
David Wronek (3):
dt-bindings: arm: qcom: Document SM7125 and xiaomi,joyeuse board
arm64: dts: qcom: pm6150: Add resin and rtc nodes
arm64: dts: qcom: Add support for the Xiaomi SM7125 platform
map220v (4):
dt-bindings: arm: qcom,ids: Add SoC ID for SM7125
soc: qcom: socinfo: Add SoC ID for SM7125
clk: qcom: gcc-sc7180: Fix up gcc_sdcc2_apps_clk_src
arm64: dts: qcom: Add SM7125 device tree
.../devicetree/bindings/arm/qcom.yaml | 6 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/pm6150.dtsi | 15 +
.../boot/dts/qcom/sm7125-xiaomi-joyeuse.dts | 16 +
.../boot/dts/qcom/sm7125-xiaomi-miatoll.dtsi | 420 ++++++++++++++++++
arch/arm64/boot/dts/qcom/sm7125.dtsi | 16 +
drivers/clk/qcom/gcc-sc7180.c | 1 +
drivers/soc/qcom/socinfo.c | 1 +
include/dt-bindings/arm/qcom,ids.h | 1 +
9 files changed, 477 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/sm7125-xiaomi-joyeuse.dts
create mode 100644 arch/arm64/boot/dts/qcom/sm7125-xiaomi-miatoll.dtsi
create mode 100644 arch/arm64/boot/dts/qcom/sm7125.dtsi
--
2.41.0
From: map220v <[email protected]>
The Snapdragon 720G (sm7125) is software-wise very similar to the
Snapdragon 7c with minor differences in clock speeds and as added here,
it uses the Kryo 465 instead of Kryo 468.
Signed-off-by: map220v <[email protected]>
Signed-off-by: David Wronek <[email protected]>
---
arch/arm64/boot/dts/qcom/sm7125.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/sm7125.dtsi
diff --git a/arch/arm64/boot/dts/qcom/sm7125.dtsi b/arch/arm64/boot/dts/qcom/sm7125.dtsi
new file mode 100644
index 000000000000..8d7a745014db
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/sm7125.dtsi
@@ -0,0 +1,16 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Copyright (c) 2023, map220v <[email protected]>
+ */
+
+#include "sc7180.dtsi"
+
+/* SM7125 uses Kryo 465 instead of Kryo 468 */
+&CPU0 { compatible = "qcom,kryo465"; };
+&CPU1 { compatible = "qcom,kryo465"; };
+&CPU2 { compatible = "qcom,kryo465"; };
+&CPU3 { compatible = "qcom,kryo465"; };
+&CPU4 { compatible = "qcom,kryo465"; };
+&CPU5 { compatible = "qcom,kryo465"; };
+&CPU6 { compatible = "qcom,kryo465"; };
+&CPU7 { compatible = "qcom,kryo465"; };
--
2.41.0
From: map220v <[email protected]>
Add the SoC ID for Qualcomm SM7125.
Signed-off-by: map220v <[email protected]>
Signed-off-by: David Wronek <[email protected]>
---
include/dt-bindings/arm/qcom,ids.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
index bcbe9ee2cdaf..6a8dd2e42b24 100644
--- a/include/dt-bindings/arm/qcom,ids.h
+++ b/include/dt-bindings/arm/qcom,ids.h
@@ -215,6 +215,7 @@
#define QCOM_ID_SDA429W 437
#define QCOM_ID_SM8350 439
#define QCOM_ID_QCM2290 441
+#define QCOM_ID_SM7125 443
#define QCOM_ID_SM6115 444
#define QCOM_ID_IPQ5010 446
#define QCOM_ID_IPQ5018 447
--
2.41.0
On 04/07/2023 18:31, David Wronek wrote:
> From: map220v <[email protected]>
>
> The Snapdragon 720G (sm7125) is software-wise very similar to the
> Snapdragon 7c with minor differences in clock speeds and as added here,
> it uses the Kryo 465 instead of Kryo 468.
>
> Signed-off-by: map220v <[email protected]>
> Signed-off-by: David Wronek <[email protected]>
> ---
> arch/arm64/boot/dts/qcom/sm7125.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/sm7125.dtsi
>
> diff --git a/arch/arm64/boot/dts/qcom/sm7125.dtsi b/arch/arm64/boot/dts/qcom/sm7125.dtsi
> new file mode 100644
> index 000000000000..8d7a745014db
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm7125.dtsi
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (c) 2023, map220v <[email protected]>
Really? No "* Copyright (c) 2021, The Linux Foundation. All rights
reserved."?
Was there originally, so I wonder...
https://github.com/map220v/sm7125-mainline/commit/e436882505300b41361c18bbd8516db543f7f07c
Best regards,
Krzysztof
On 04/07/2023 18:31, David Wronek wrote:
> From: map220v <[email protected]>
>
> Add the SoC ID for Qualcomm SM7125.
>
> Signed-off-by: map220v <[email protected]>
We accept known identities, but this looks like a nickname/pseudonym.
Are you sure you got such SoB from map220v?
None of the commits here:
https://github.com/map220v/sm7125-mainline/commits/a72q-6.0
have signed-off-by. Did you add it by yourself?
Best regards,
Krzysztof
On Wed, Jul 5, 2023 at 11:46 AM Krzysztof Kozlowski
<[email protected]> wrote:
>
> On 04/07/2023 18:31, David Wronek wrote:
> > From: map220v <[email protected]>
> >
> > Add the SoC ID for Qualcomm SM7125.
> >
> > Signed-off-by: map220v <[email protected]>
>
> We accept known identities, but this looks like a nickname/pseudonym.
> Are you sure you got such SoB from map220v?
>
> None of the commits here:
> https://github.com/map220v/sm7125-mainline/commits/a72q-6.0
> have signed-off-by. Did you add it by yourself?
>
> Best regards,
> Krzysztof
>
(Please ignore my E-Mail from before, I forgot to click "reply all")
I have asked map220v for permission to add their Signed-off-by to the commits
and this is the one they gave me. Is the nickname a problem?
Sincerely,
David
On 05/07/2023 17:48, David Wronek wrote:
> On Wed, Jul 5, 2023 at 11:46 AM Krzysztof Kozlowski
> <[email protected]> wrote:
>>
>> On 04/07/2023 18:31, David Wronek wrote:
>>> From: map220v <[email protected]>
>>>
>>> Add the SoC ID for Qualcomm SM7125.
>>>
>>> Signed-off-by: map220v <[email protected]>
>>
>> We accept known identities, but this looks like a nickname/pseudonym.
>> Are you sure you got such SoB from map220v?
>>
>> None of the commits here:
>> https://github.com/map220v/sm7125-mainline/commits/a72q-6.0
>> have signed-off-by. Did you add it by yourself?
>>
>> Best regards,
>> Krzysztof
>>
> (Please ignore my E-Mail from before, I forgot to click "reply all")
>
> I have asked map220v for permission to add their Signed-off-by to the commits
> and this is the one they gave me. Is the nickname a problem?
Yes, because it looks anonymous. We need known identity. Just take the
ownership of the patches...
Best regards,
Krzysztof