From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Oleksii Onchul <oleksiionchul@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Add Xiaomi 11 Lite 5G NE
Date: Mon, 13 Jul 2026 09:52:30 +0200 [thread overview]
Message-ID: <3f923649-34ff-4089-87e2-8989dae335ca@oss.qualcomm.com> (raw)
In-Reply-To: <20260711184934.55701-3-oleksiionchul@gmail.com>
On 7/11/26 8:49 PM, Oleksii Onchul wrote:
> Add initial support for the Xiaomi 11 Lite 5G NE, codenamed lisa.
>
> The supported hardware includes regulators, UFS, SD card, USB, GPU,
> remote processors, Wi-Fi, Bluetooth, touchscreen, flash LED, thermal
> sensors and the hardware buttons.
>
> Signed-off-by: Oleksii Onchul <oleksiionchul@gmail.com>
> ---
[...]
> + chosen {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + stdout-path = "serial0:115200n8";
> +
> + framebuffer0: framebuffer@e1000000 {
> + compatible = "simple-framebuffer";
> + reg = <0x0 0xe1000000 0x0 (1080 * 2400 * 4)>;
Please use memory-region instead
[...]
> + ramoops@a9000000 {
> + compatible = "ramoops";
> + reg = <0x0 0xa9000000 0x0 0x200000>;
> + pmsg-size = <0x200000>;
> + mem-type = <0x02>;
Let's make mem-type decimal. Don't you need ecc-size for reliability?
[...]
> + regulators {
> + vreg_l1p: ldo1 {
> + regulator-name = "vreg_l1p";
> + regulator-min-microvolt = <1000000>;
> + regulator-max-microvolt = <1200000>;
> + regulator-always-on;
Many/all of these shouldn't be always on. This PMIC normally only
powers cameras, so dropping this should be fine
[...]
> +&ipa {
> + qcom,gsi-loader = "self";
> + memory-region = <&ipa_fw_mem>;
These two fill be folded into the SoC DTSI soon
https://lore.kernel.org/all/20260517-ipa-loader-v1-0-3c3764c1b4a3@oss.qualcomm.com/
[...]
> +&tlmm {
> + /*
> + * 32-33: SMB1394 (SPMI)
> + * 56-59: fingerprint reader (SPI)
> + */
> + gpio-reserved-ranges = <32 2>, <48 4>, <56 4>;
What about the <48 4> range?
as a nit, other files place the comments inline with the ranges:
gpio-reserved-ranges = <4 4>, /* EC TZ Secure I3C */
<10 2>, /* OOB UART */
<44 4>; /* Security SPI (TPM) */
[...]
> +&usb_1 {
> + /* USB 2.0 only */
Did you test that (with an actual USB3 cable)?
Konrad
next prev parent reply other threads:[~2026-07-13 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 18:49 [PATCH 0/2] arm64: dts: qcom: Add Xiaomi 11 Lite 5G NE Oleksii Onchul
2026-07-11 18:49 ` [PATCH 1/2] dt-bindings: arm: " Oleksii Onchul
2026-07-13 7:43 ` Krzysztof Kozlowski
2026-07-11 18:49 ` [PATCH 2/2] arm64: dts: " Oleksii Onchul
2026-07-11 19:11 ` sashiko-bot
2026-07-13 7:43 ` Krzysztof Kozlowski
2026-07-13 7:52 ` Konrad Dybcio [this message]
2026-07-13 14:10 ` Alex
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=3f923649-34ff-4089-87e2-8989dae335ca@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=oleksiionchul@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox