From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Stanislav Zaikin <zstaseg@gmail.com>, devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS
Date: Wed, 4 Feb 2026 13:20:42 +0100 [thread overview]
Message-ID: <125b00d1-d2d5-4490-b712-acc213a58d3c@oss.qualcomm.com> (raw)
In-Reply-To: <20260204115645.1343750-3-zstaseg@gmail.com>
On 2/4/26 12:56 PM, Stanislav Zaikin wrote:
> Xiaomi 12 Lite 5G is a handset released in 2022
>
> This commit has the following features working:
> - Display (with simple fb)
> - Touchscreen
> - UFS
> - Power and volume buttons
> - Pinctrl
> - RPM Regulators
> - Remoteprocs - wifi, bluetooth
> - USB (Device Mode)
>
> Signed-off-by: Stanislav Zaikin <zstaseg@gmail.com>
> ---
Hello, this looks good, couple nits
[...]
> + // S2B is really ebi.lvl but it's there for supply map completeness sake.
/* C-style comments */ are preferred
[...]
> + /* Mainline video_mem is downstream cvp_mem */
What does that mean? CVP is strongly connected with the video
hardware, but they're not quite the same
> + real_video_mem: video@8ad00000 {
> + reg = <0x0 0x8ad00000 0x0 0x500000>;
> + no-map;
> + };
> +
> + ipa_gsi_mem: ipa-gsi@8b710000 {
> + reg = <0x0 0x8b710000 0x0 0xa000>;
> + no-map;
> + };
> +
> + cdsp_mem: cdsp@9c700000 {
> + reg = <0x0 0x9c700000 0x0 0x1e00000>;
> + no-map;
> + };
> +
> + ramoops@a9000000 {
> + compatible = "ramoops";
> + reg = <0x0 0xa9000000 0x0 0x200000>;
> + pmsg-size = <0x200000>;
> + mem-type = <0x02>;
= <2> would be neater
If you have an easy way of modifying the (presumably) downstream-based
image which you use for ramoops, you may want to add ecc-size = <8>
too, so that it's more robust
[...]
> +&tlmm {
> + gpio-reserved-ranges = <32 2>, <48 4>, <56 4>;
Any chance you know what they're used for? (you can often correlate them
with QUP pinctrl entries, as they're often fingerprint scanner/NFC eSE
connections)
If you do, please sprinkle in some comments, like in x1-crd.dtsi
[...]
> +&usb_1 {
> + /* USB 2.0 only */
> + qcom,select-utmi-as-pipe-clk;
> +
> + dr_mode = "otg";
> + usb-role-switch;
> + maximum-speed = "high-speed";
> + /* Remove USB3 phy */
> + phys = <&usb_1_hsphy>;
> + phy-names = "usb2-phy";
Did you check whether that's the case with a ""real"" USB3 Type-C
cable? Does a Type-C dongle with a HDMI/DP output work if you plug it
in when running downstream?
Konrad
next prev parent reply other threads:[~2026-02-04 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 11:56 [PATCH 0/2] Add Xiaomi 12 Lite 5G (taoyao) device tree Stanislav Zaikin
2026-02-04 11:56 ` [PATCH 1/2] dt-bindings: arm: qcom: Add SM7325 Xiaomi 12 Lite 5G (taoyao) Stanislav Zaikin
2026-02-10 1:05 ` Rob Herring (Arm)
2026-02-04 11:56 ` [PATCH 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS Stanislav Zaikin
2026-02-04 12:20 ` Konrad Dybcio [this message]
2026-02-04 13:10 ` David Heidelberg
2026-02-06 13:23 ` Stanislav Zaikin
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=125b00d1-d2d5-4490-b712-acc213a58d3c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zstaseg@gmail.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®