From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Raihan Ahamed <raihan1999ahamed@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Kees Cook <kees@kernel.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: msm8953-lenovo-kuntao: Add initial device tree
Date: Mon, 3 Nov 2025 12:23:29 +0100 [thread overview]
Message-ID: <e516564b-5e43-4628-836c-ff227a68d20e@oss.qualcomm.com> (raw)
In-Reply-To: <20251031135506.214025-2-raihan1999ahamed@gmail.com>
On 10/31/25 2:51 PM, Raihan Ahamed wrote:
> Lenovo P2 is a handset using the MSM8953 SoC released in 2016
>
> Add a device tree with initial support for:
>
> - Enable accelerometer sensor
> - Enable pinctrl for GPIO keys
> - Enable gpu and add gpu_zap_shader
> - GPIO keys
> - SDHCI (internal and external storage)
> - USB Device Mode
> - WCNSS (WiFi/BT)
> - Regulators
>
> Signed-off-by: Raihan Ahamed <raihan1999ahamed@gmail.com>
> ---
[...]
> +++ b/arch/arm64/boot/dts/qcom/msm8953-lenovo-kuntao.dts
> @@ -0,0 +1,294 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2024, Raihan Ahamed <raihan1999ahamed@gmail.com>
> + */
> +/dts-v1/;
> +
> +#include "msm8953.dtsi"
> +#include "pm8953.dtsi"
> +#include "pmi8950.dtsi"
> +
> +/delete-node/ &qseecom_mem;
> +
> +/ {
> + model = "Lenovo P2";
> + compatible = "lenovo,kuntao", "qcom,msm8953";
> + chassis-type = "handset";
> + qcom,msm-id = <0x125 0x00>;
QCOM_ID_MSM8953 (dt-bindings/arm/qcom,ids.h)
> + qcom,board-id = <0x41 0x82b1 0x41 0x83b0>;
> +
> + gpio-keys {
> + compatible = "gpio-keys";
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&gpio_key_default>;
property-n
property-names
in this order, please
> +
> + key-volume-up {
> + label = "Volume Up";
> + gpios = <&tlmm 85 GPIO_ACTIVE_LOW>;
> + linux,code = <KEY_VOLUMEUP>;
> + debounce-interval = <15>;
> + };
> +
> + one-key-low-power {
> + label = "onekeylowpower";
> + gpios = <&tlmm 86 GPIO_ACTIVE_LOW>;
> + linux,code = <ABS_HAT1Y>;
> + debounce-interval = <15>;
> + };
> +
> + homepage {
> + label = "homepage";
> + gpios = <&tlmm 132 GPIO_ACTIVE_LOW>;
> + linux,code = <KEY_HOMEPAGE>;
> + debounce-interval = <15>;
> + gpio-key,wakeup;
> + };
Please sort these nodes without an address by their name> + };
> +
> + reserved-memory {
> + qseecom_mem: qseecom@84a00000 {
> + reg = <0x0 0x84a00000 0x0 0x1900000>;
> + no-map;
> + };
> +
> + ramoops@8ee00000 {
> + compatible = "ramoops";
> + reg = <0x0 0x8ee00000 0x0 0x80000>;
> + console-size = <0x40000>;
> + ftrace-size = <0x15000>;
> + record-size = <0x5000>;
> + pmsg-size = <0x2000>;
Usually ecc-size = <8> is desired, as the traces are often corrupted
[...]
> +&tlmm {
> + gpio-reserved-ranges = <0 4>, <135 4>;
Any chance you know what is on these GPIOs, and could document it (e.g.
like in x1-crd.dtsi)
Konrad
next prev parent reply other threads:[~2025-11-03 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 13:51 [PATCH v4 1/2] dt-bindings: arm: qcom: Add Lenovo P2 Raihan Ahamed
2025-10-31 13:51 ` [PATCH v4 2/2] arm64: dts: qcom: msm8953-lenovo-kuntao: Add initial device tree Raihan Ahamed
2025-11-03 11:23 ` Konrad Dybcio [this message]
2025-11-03 11:25 ` Krzysztof Kozlowski
2025-11-03 18:54 ` David Heidelberg
2025-11-02 16:14 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Add Lenovo P2 Krzysztof Kozlowski
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=e516564b-5e43-4628-836c-ff227a68d20e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raihan1999ahamed@gmail.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®