From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Eric Gonçalves" <ghatto404@gmail.com>, linux-arm-msm@vger.kernel.org
Cc: devicetree@vger.kernel.org, konradybcio@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: add initial tree for Samsung Galaxy S22
Date: Mon, 16 Jun 2025 08:18:07 +0200 [thread overview]
Message-ID: <41d6142c-0198-4a39-b0f6-e3d292e10bf4@kernel.org> (raw)
In-Reply-To: <20250615205608.1133129-2-ghatto404@gmail.com>
On 15/06/2025 22:56, Eric Gonçalves wrote:
> Adds new device support for the Samsung Galaxy S22 (SM-S901E) phone
>
> Working features:
> - simple-framebuffer
> - side buttons
> - storage
> - usb
Thread and name your patches correctly, e.g. use b4 or git format-patch
-vX -2, and add changelog in cover letter or under '---' of individual
patches describing changes from previous version.
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
</form letter>
>
> Signed-off-by: Eric Gonçalves <ghatto404@gmail.com>
> ---
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../boot/dts/qcom/sm8450-samsung-r0q.dts | 365 ++++++++++++++++++
> 2 files changed, 366 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 669b888b27a1..cde80a17f2ab 100644
> --- a/arch/arm64/boot/dts/qcom/Makefile
> +++ b/arch/arm64/boot/dts/qcom/Makefile
> @@ -287,6 +287,7 @@ dtb-$(CONFIG_ARCH_QCOM) += sm8450-hdk.dtb
> dtb-$(CONFIG_ARCH_QCOM) += sm8450-qrd.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) += sm8450-samsung-r0q.dtb
> dtb-$(CONFIG_ARCH_QCOM) += sm8550-hdk.dtb
> dtb-$(CONFIG_ARCH_QCOM) += sm8550-mtp.dtb
> dtb-$(CONFIG_ARCH_QCOM) += sm8550-qrd.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..cb58626e879e
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm8450-samsung-r0q.dts
> @@ -0,0 +1,365 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (c) 2025, Eric Gonçalves <ghatto404@gmail.com>
> + * Copyright (c) 2025, Arthur Aligon <arthurus36.alt2@tutanota.com>
> + */
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/input/linux-event-codes.h>
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> +
> +#include "sm8450.dtsi"
> +#include "pm8350.dtsi"
> +#include "pm8350b.dtsi"
> +#include "pm8350c.dtsi"
> +#include "pm8450.dtsi"
> +#include "pmk8350.dtsi"
> +#include "pmr735a.dtsi"
> +
> +/delete-node/ &xbl_ramdump_mem;
> +/delete-node/ &xbl_sc_mem;
> +/delete-node/ &adsp_mem;
> +/delete-node/ &rmtfs_mem;
> +/delete-node/ &mte_mem;
> +/delete-node/ &trusted_apps_mem;
> +/delete-node/ &trusted_apps_ext_mem;
> +
> +/ {
> + chassis-type = "handset";
> + model = "Samsung Galaxy S22 (SM-S901E)";
> + compatible = "samsung,r0q", "qcom,sm8450";
> +
> + chosen {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + bootargs = "clk_ignore_unused pd_ignore_unused";
This is not really part of mainline DTS. If it is, then you need to
clearly document the reasons with comment.
> + linux,initrd-start = <0x00 0xb6915000>;
> + linux,initrd-end = <0x00 0xb7fff22c>;
Why this has to be in DTS?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-16 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 20:56 [PATCH v2] dt-bindings: arm: qcom: document r0q board binding Eric Gonçalves
2025-06-15 20:56 ` [PATCH v2] arm64: dts: qcom: add initial tree for Samsung Galaxy S22 Eric Gonçalves
2025-06-16 6:18 ` Krzysztof Kozlowski [this message]
2025-06-16 6:18 ` [PATCH v2] dt-bindings: arm: qcom: document r0q board binding Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 4:25 [PATCH v2] arm64: dts: qcom: add initial tree for Samsung Galaxy S22 kernel test robot
2025-06-16 20:31 kernel test robot
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=41d6142c-0198-4a39-b0f6-e3d292e10bf4@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghatto404@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.