* [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
@ 2025-07-16 23:17 ` Violet
2025-07-17 14:26 ` Krzysztof Kozlowski
2025-07-16 23:17 ` [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
` (3 subsequent siblings)
4 siblings, 1 reply; 10+ messages in thread
From: Violet @ 2025-07-16 23:17 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
Add binding for the Samsung Galaxy S22 (SM-S901E) board, codenamed R0Q,
which is based on the Qualcomm Snapdragon 8 Gen 1 SoC.
Signed-off-by: Violet <violet@atl.tools>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index ae43b3556580..64455af6c44a 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1095,6 +1095,7 @@ properties:
- enum:
- qcom,sm8450-hdk
- qcom,sm8450-qrd
+ - samsung,r0q
- sony,pdx223
- sony,pdx224
- const: qcom,sm8450
--
2.50.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding
2025-07-16 23:17 ` [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding Violet
@ 2025-07-17 14:26 ` Krzysztof Kozlowski
0 siblings, 0 replies; 10+ messages in thread
From: Krzysztof Kozlowski @ 2025-07-17 14:26 UTC (permalink / raw)
To: Violet, Bjorn Andersson, Konrad Dybcio, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
On 17/07/2025 01:17, Violet wrote:
> Add binding for the Samsung Galaxy S22 (SM-S901E) board, codenamed R0Q,
> which is based on the Qualcomm Snapdragon 8 Gen 1 SoC.
>
> Signed-off-by: Violet <violet@atl.tools>
> ---
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
<form letter>
This is an automated instruction, just in case, because many review tags
are being ignored. If you know the process, you can skip it (please do
not feel offended by me posting it here - no bad intentions intended).
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Full context and explanation:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
</form letter>
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
2025-07-16 23:17 ` [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding Violet
@ 2025-07-16 23:17 ` Violet
2025-07-17 14:26 ` Krzysztof Kozlowski
2025-07-17 20:19 ` Konrad Dybcio
2025-07-17 6:16 ` [PATCH v6 0/2] " Krzysztof Kozlowski
` (2 subsequent siblings)
4 siblings, 2 replies; 10+ messages in thread
From: Violet @ 2025-07-16 23:17 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
Add new device support for the Samsung Galaxy S22 (SM-S901E) phone
What works:
- SimpleFB
- USB
Signed-off-by: Violet <violet@atl.tools>
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../boot/dts/qcom/sm8450-samsung-r0q.dts | 145 ++++++++++++++++++
2 files changed, 146 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
index 4bfa926b6a08..790613cabd08 100644
--- a/arch/arm64/boot/dts/qcom/Makefile
+++ b/arch/arm64/boot/dts/qcom/Makefile
@@ -287,6 +287,7 @@ dtb-$(CONFIG_ARCH_QCOM) += sm8350-sony-xperia-sagami-pdx214.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8350-sony-xperia-sagami-pdx215.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8450-hdk.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8450-qrd.dtb
+dtb-$(CONFIG_ARCH_QCOM) += sm8450-samsung-r0q.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8450-sony-xperia-nagara-pdx223.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8450-sony-xperia-nagara-pdx224.dtb
dtb-$(CONFIG_ARCH_QCOM) += sm8550-hdk.dtb
diff --git a/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts b/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
new file mode 100644
index 000000000000..3f793fe5cff8
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
@@ -0,0 +1,145 @@
+// SPDX-License-Identifier: GPL-2.0-only
+
+/dts-v1/;
+
+#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
+
+#include "sm8450.dtsi"
+#include "pm8350.dtsi"
+#include "pm8350c.dtsi"
+
+/ {
+ model = "Samsung Galaxy S22 5G";
+ compatible = "samsung,r0q", "qcom,sm8450";
+ chassis-type = "handset";
+
+ chosen {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+
+ framebuffer: framebuffer@b8000000 {
+ compatible = "simple-framebuffer";
+ reg = <0x0 0xb8000000 0x0 0x2b00000>;
+ width = <1080>;
+ height = <2340>;
+ stride = <(1080 * 4)>;
+ format = "a8r8g8b8";
+ };
+ };
+
+ vph_pwr: vph-pwr-regulator {
+ compatible = "regulator-fixed";
+ regulator-name = "vph_pwr";
+ regulator-min-microvolt = <3700000>;
+ regulator-max-microvolt = <3700000>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ reserved-memory {
+ /*
+ * The bootloader will only keep display hardware enabled
+ * if this memory region is named exactly 'splash_region'
+ */
+ splash-region@b8000000 {
+ reg = <0x0 0xb8000000 0x0 0x2b00000>;
+ no-map;
+ };
+ };
+};
+
+&apps_rsc {
+ regulators-0 {
+ compatible = "qcom,pm8350-rpmh-regulators";
+ qcom,pmic-id = "b";
+
+ vdd-s1-supply = <&vph_pwr>;
+ vdd-s2-supply = <&vph_pwr>;
+ vdd-s3-supply = <&vph_pwr>;
+ vdd-s4-supply = <&vph_pwr>;
+ vdd-s5-supply = <&vph_pwr>;
+ vdd-s6-supply = <&vph_pwr>;
+ vdd-s7-supply = <&vph_pwr>;
+ vdd-s8-supply = <&vph_pwr>;
+ vdd-s9-supply = <&vph_pwr>;
+ vdd-s10-supply = <&vph_pwr>;
+ vdd-s11-supply = <&vph_pwr>;
+ vdd-s12-supply = <&vph_pwr>;
+
+ vdd-l2-l7-supply = <&vreg_bob>;
+ vdd-l3-l5-supply = <&vreg_bob>;
+
+ vreg_l2b_3p07: ldo2 {
+ regulator-min-microvolt = <3072000>;
+ regulator-max-microvolt = <3072000>;
+ regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
+ };
+
+ vreg_l5b_0p88: ldo5 {
+ regulator-min-microvolt = <880000>;
+ regulator-max-microvolt = <888000>;
+ regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
+ };
+ };
+
+ regulators-1 {
+ compatible = "qcom,pm8350c-rpmh-regulators";
+ qcom,pmic-id = "c";
+
+ vdd-s1-supply = <&vph_pwr>;
+ vdd-s2-supply = <&vph_pwr>;
+ vdd-s3-supply = <&vph_pwr>;
+ vdd-s4-supply = <&vph_pwr>;
+ vdd-s5-supply = <&vph_pwr>;
+ vdd-s6-supply = <&vph_pwr>;
+ vdd-s7-supply = <&vph_pwr>;
+ vdd-s8-supply = <&vph_pwr>;
+ vdd-s9-supply = <&vph_pwr>;
+ vdd-s10-supply = <&vph_pwr>;
+
+ vdd-l1-l12-supply = <&vreg_bob>;
+ vdd-l2-l8-supply = <&vreg_bob>;
+ vdd-l3-l4-l5-l7-l13-supply = <&vreg_bob>;
+ vdd-l6-l9-l11-supply = <&vreg_bob>;
+
+ vdd-bob-supply = <&vph_pwr>;
+
+ vreg_bob: bob {
+ regulator-min-microvolt = <3008000>;
+ regulator-max-microvolt = <3960000>;
+ regulator-initial-mode = <RPMH_REGULATOR_MODE_AUTO>;
+ };
+
+ vreg_l1c_1p8: ldo1 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
+ };
+ };
+};
+
+&tlmm {
+ gpio-reserved-ranges = <36 4>, <50 1>;
+};
+
+&usb_1 {
+ /* USB 2.0 only */
+ qcom,select-utmi-as-pipe-clk;
+ status = "okay";
+};
+
+&usb_1_dwc3 {
+ dr_mode = "peripheral";
+ maximum-speed = "high-speed";
+ /* Remove USB3 phy */
+ phys = <&usb_1_hsphy>;
+ phy-names = "usb2-phy";
+};
+
+&usb_1_hsphy {
+ vdda-pll-supply = <&vreg_l5b_0p88>;
+ vdda18-supply = <&vreg_l1c_1p8>;
+ vdda33-supply = <&vreg_l2b_3p07>;
+ status = "okay";
+};
--
2.50.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 ` [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
@ 2025-07-17 14:26 ` Krzysztof Kozlowski
2025-07-17 20:19 ` Konrad Dybcio
1 sibling, 0 replies; 10+ messages in thread
From: Krzysztof Kozlowski @ 2025-07-17 14:26 UTC (permalink / raw)
To: Violet, Bjorn Andersson, Konrad Dybcio, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
On 17/07/2025 01:17, Violet wrote:
> Add new device support for the Samsung Galaxy S22 (SM-S901E) phone
>
> What works:
> - SimpleFB
> - USB
>
> Signed-off-by: Violet <violet@atl.tools>
> ---
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../boot/dts/qcom/sm8450-samsung-r0q.dts | 145 ++++++++++++++++++
> 2 files changed, 146 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 ` [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
2025-07-17 14:26 ` Krzysztof Kozlowski
@ 2025-07-17 20:19 ` Konrad Dybcio
2025-07-29 11:46 ` Violet
1 sibling, 1 reply; 10+ messages in thread
From: Konrad Dybcio @ 2025-07-17 20:19 UTC (permalink / raw)
To: Violet, Bjorn Andersson, Konrad Dybcio, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
On 7/17/25 1:17 AM, Violet wrote:
> Add new device support for the Samsung Galaxy S22 (SM-S901E) phone
>
> What works:
> - SimpleFB
> - USB
>
> Signed-off-by: Violet <violet@atl.tools>
> ---
[...]
> +&tlmm {
> + gpio-reserved-ranges = <36 4>, <50 1>;
Do you know what these are connected to?
We tend to document it, see e.g. x1-crd.dtsi
> +};
> +
> +&usb_1 {
> + /* USB 2.0 only */
> + qcom,select-utmi-as-pipe-clk;
Is that a hardware limitation? I thought these phones had the necessary
pins connected (for DeX)..
> + status = "okay";
A newline before 'status' is good practice, file-wide
Konrad
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-17 20:19 ` Konrad Dybcio
@ 2025-07-29 11:46 ` Violet
0 siblings, 0 replies; 10+ messages in thread
From: Violet @ 2025-07-29 11:46 UTC (permalink / raw)
To: Konrad Dybcio, Bjorn Andersson, Konrad Dybcio, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel
On 7/17/25 20:19, Konrad Dybcio wrote:
> On 7/17/25 1:17 AM, Violet wrote:
>> Add new device support for the Samsung Galaxy S22 (SM-S901E) phone
>>
>> What works:
>> - SimpleFB
>> - USB
>>
>> Signed-off-by: Violet <violet@atl.tools>
>> ---
> [...]
>
>> +&tlmm {
>> + gpio-reserved-ranges = <36 4>, <50 1>;
> Do you know what these are connected to?
>
> We tend to document it, see e.g. x1-crd.dtsi
>
>> +};
>> +
>> +&usb_1 {
>> + /* USB 2.0 only */
>> + qcom,select-utmi-as-pipe-clk;
> Is that a hardware limitation? I thought these phones had the necessary
> pins connected (for DeX)..
>
>> + status = "okay";
> A newline before 'status' is good practice, file-wide
>
> Konrad
Thank you, I'll fix these issues on the next patchset. Indeed it is not a
hardware limitation, I just kept it USB 2.0 for now to avoid any
potential issues with 3.0.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
2025-07-16 23:17 ` [PATCH v6 1/2] dt-bindings: arm: qcom: document r0q board binding Violet
2025-07-16 23:17 ` [PATCH v6 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
@ 2025-07-17 6:16 ` Krzysztof Kozlowski
2025-07-17 15:56 ` Rob Herring (Arm)
2025-07-30 9:21 ` Pavel Machek
4 siblings, 0 replies; 10+ messages in thread
From: Krzysztof Kozlowski @ 2025-07-17 6:16 UTC (permalink / raw)
To: Violet
Cc: Bjorn Andersson, Konrad Dybcio, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, linux-arm-msm, devicetree, linux-kernel
On Wed, Jul 16, 2025 at 11:17:08PM +0000, Violet wrote:
> Changes in v6:
> - Remove debug features (bootargs, etc) that slipped in the v5 DTS
> - Format and organize nodes correctly based on existing DTS,
> move "status = "okay";" to the bottom always
> - Solve "ddr_device_type" and "qcom,rmtfs-mem" warnings, the rest are
> from existing SoC .dtsi
> - Disable buttons, ufs and other features for later revision
How this can be v6? Someone (you?) sent last time v2?
Where is the rest of changelog? v1, v2, v3, v4, v5? Or at least lore
links to previous discussions and changelogs?
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
` (2 preceding siblings ...)
2025-07-17 6:16 ` [PATCH v6 0/2] " Krzysztof Kozlowski
@ 2025-07-17 15:56 ` Rob Herring (Arm)
2025-07-30 9:21 ` Pavel Machek
4 siblings, 0 replies; 10+ messages in thread
From: Rob Herring (Arm) @ 2025-07-17 15:56 UTC (permalink / raw)
To: Violet
Cc: Conor Dooley, linux-kernel, linux-arm-msm, Konrad Dybcio,
Krzysztof Kozlowski, devicetree, Bjorn Andersson
On Wed, 16 Jul 2025 23:17:08 +0000, Violet wrote:
> Changes in v6:
> - Remove debug features (bootargs, etc) that slipped in the v5 DTS
> - Format and organize nodes correctly based on existing DTS,
> move "status = "okay";" to the bottom always
> - Solve "ddr_device_type" and "qcom,rmtfs-mem" warnings, the rest are
> from existing SoC .dtsi
> - Disable buttons, ufs and other features for later revision
>
> Signed-off-by: Violet <violet@atl.tools>
>
> Violet (2):
> dt-bindings: arm: qcom: document r0q board binding
> arm64: dts: qcom: add initial support for Samsung Galaxy S22
>
> .../devicetree/bindings/arm/qcom.yaml | 1 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../boot/dts/qcom/sm8450-samsung-r0q.dts | 145 ++++++++++++++++++
> 3 files changed, 147 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
>
> --
> 2.50.1
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: attempting to guess base-commit...
Base: failed to guess base
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20250716231710.99983-1-violet@atl.tools:
arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dtb: clock-controller@aaf0000 (qcom,sm8450-videocc): power-domains: [[98, 6]] is too short
from schema $id: http://devicetree.org/schemas/clock/qcom,sm8450-videocc.yaml#
arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dtb: clock-controller@aaf0000 (qcom,sm8450-videocc): required-opps: [[55]] is too short
from schema $id: http://devicetree.org/schemas/clock/qcom,sm8450-videocc.yaml#
arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dtb: clock-controller@aaf0000 (qcom,sm8450-videocc): Unevaluated properties are not allowed ('power-domains', 'required-opps' were unexpected)
from schema $id: http://devicetree.org/schemas/clock/qcom,sm8450-videocc.yaml#
arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dtb: clock-controller@ade0000 (qcom,sm8450-camcc): power-domains: [[98, 6]] is too short
from schema $id: http://devicetree.org/schemas/clock/qcom,sm8450-camcc.yaml#
arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dtb: clock-controller@ade0000 (qcom,sm8450-camcc): required-opps: [[55]] is too short
from schema $id: http://devicetree.org/schemas/clock/qcom,sm8450-camcc.yaml#
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
2025-07-16 23:17 [PATCH v6 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Violet
` (3 preceding siblings ...)
2025-07-17 15:56 ` Rob Herring (Arm)
@ 2025-07-30 9:21 ` Pavel Machek
4 siblings, 0 replies; 10+ messages in thread
From: Pavel Machek @ 2025-07-30 9:21 UTC (permalink / raw)
To: Violet
Cc: Bjorn Andersson, Konrad Dybcio, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, linux-arm-msm, devicetree, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On Wed 2025-07-16 23:17:08, Violet wrote:
> Changes in v6:
> - Remove debug features (bootargs, etc) that slipped in the v5 DTS
> - Format and organize nodes correctly based on existing DTS,
> move "status = "okay";" to the bottom always
> - Solve "ddr_device_type" and "qcom,rmtfs-mem" warnings, the rest are
> from existing SoC .dtsi
> - Disable buttons, ufs and other features for later revision
>
> Signed-off-by: Violet <violet@atl.tools>
Is that a real name? Could we use real names in signoffs?
Thanks,
Pavel
> Violet (2):
> dt-bindings: arm: qcom: document r0q board binding
> arm64: dts: qcom: add initial support for Samsung Galaxy S22
>
> .../devicetree/bindings/arm/qcom.yaml | 1 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../boot/dts/qcom/sm8450-samsung-r0q.dts | 145 ++++++++++++++++++
> 3 files changed, 147 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
--
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread