From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Zhang Jiaxi <Z1529105815@outlook.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" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 2/2] arm64: dts: qcom: Add a minimal Xiaomi Warsaw description
Date: Wed, 21 Oct 2026 12:32:45 +0200 [thread overview]
Message-ID: <d5d28d79-474a-40bf-b511-e20fb0897b91@oss.qualcomm.com> (raw)
In-Reply-To: <20261016-b4-warsaw-minimal-usb2-v2-2-1b03496396b4@outlook.com>
On 10/16/26 5:53 PM, Zhang Jiaxi wrote:
> From: Jiaxi Zhang <z1529105815@outlook.com>
>
> Add the Warsaw board identity, reference clocks, PM8550/PMK8550
> devices, key wiring and inherited debug UART route. Describe the board
> from the SoC and PMIC includes instead of inheriting all MTP devices.
[...]
> + model = "Xiaomi Warsaw";
Google suggests that's "REDMI K90 Ultra", we usually put marketing
names in the model field
[...]
> +&qupv3_1 {
> + status = "okay";
> +};
> +
> +&uart7 {
> + status = "okay";
> +};
This node (and apps_rsc below) is out of alphabetical sorting order,
please touch that up:
https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
> +
> +&tlmm {
> + /* GPIOs reserved by the Warsaw firmware. */
> + gpio-reserved-ranges = <36 4>, <48 4>, <74 1>;
Do we know what they correspond do? It's commongly NFC eSE, FP
scanner etc. If you do, please add a comment like the one in
glymur-crd.dtsi
[...]
> +&spmi_bus {
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + pmic@7 {
#include "pmih0108-kaanapali.dtsi" instead
[...]
> +&usb {
> + phys = <&usb_hsphy>;
> + phy-names = "usb2-phy";
> + dr_mode = "peripheral";
> + maximum-speed = "high-speed";
> + qcom,select-utmi-as-pipe-clk;
> +
> + status = "okay";
No SuperSpeed / DP altmode on this one?
Konrad
next prev parent reply other threads:[~2026-10-21 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:51 [PATCH RFC v2 0/2] arm64: dts: qcom: introduce minimal Xiaomi Warsaw support Zhang Jiaxi
2026-10-16 15:53 ` [PATCH RFC v2 1/2] dt-bindings: arm: qcom: Add Xiaomi Warsaw Zhang Jiaxi
2026-10-16 15:53 ` [PATCH RFC v2 2/2] arm64: dts: qcom: Add a minimal Xiaomi Warsaw description Zhang Jiaxi
2026-10-21 10:32 ` Konrad Dybcio [this message]
2026-10-21 12:52 ` Zhang Jiaxi
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=d5d28d79-474a-40bf-b511-e20fb0897b91@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Z1529105815@outlook.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 \
/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®