From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Adam Skladowski <a39.skl@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 7/7] arm64: dts: qcom: Add Xiaomi Redmi 9T
Date: Mon, 17 Aug 2026 18:08:43 +0200 [thread overview]
Message-ID: <79c3c201-395b-4a89-bd4f-0e64a59a1fa8@oss.qualcomm.com> (raw)
In-Reply-To: <20260810-next-patches-v1-7-79a779d76173@gmail.com>
On 8/10/26 6:55 PM, Adam Skladowski wrote:
> Add a devicetree for the Xiaomi Redmi 9T smartphone, which is based
> on the Bengal/SM6115 SoC.
[...]
> + chosen {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> + framebuffer0: framebuffer@5c000000 {
Please add a \n above
> + compatible = "simple-framebuffer";
> + reg = <0 0x5c000000 0 (2340 * 1080 * 4)>;
> + width = <1080>;
> + height = <2340>;
> + stride = <(1080 * 4)>;
> + format = "a8r8g8b8";
> + clocks = <&gcc GCC_DISP_HF_AXI_CLK>;
> + };
> + };
> +
> + backlight_dsi: backlight-dsi {
> + compatible = "led-backlight";
> + leds = <&led_backlight>;
> + brightness-levels = <255>;
> + default-brightness-level = <190>;
> + /* Backlight controllers can differ between panel variants */
Should we at least enable it now to make the backlight level controllable?
> + status = "disabled";
> + };
> +
> + gpio-keys {
> + compatible = "gpio-keys";
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&vol_up_n>;
property-n
property-names
in this order please
[...]
> +&usb_dwc3 {
> + maximum-speed = "high-speed";
> + dr_mode = "peripheral";
> + /delete-property/ usb-role-switch;
> + phys = <&usb_hsphy>;
> + phy-names = "usb2-phy";
> + ports {
> + /delete-node/ port@1;
> + };
I think if you assign the supplies to the qmpphy none of this should be necessary
Konrad
prev parent reply other threads:[~2026-08-17 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 16:55 [PATCH 0/7] arm64: dts: qcom: Add 3 new devices Adam Skladowski
2026-08-10 16:55 ` [PATCH 1/7] dt-bindings: vendor-prefixes: Add LeEco Adam Skladowski
2026-08-14 10:33 ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 2/7] dt-bindings: arm: qcom: Document Motorola Moto One Adam Skladowski
2026-08-14 10:33 ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 3/7] arm64: dts: qcom: Add Motorola One Adam Skladowski
2026-08-10 17:29 ` sashiko-bot
2026-08-11 9:12 ` Dmitry Baryshkov
2026-08-17 15:59 ` Konrad Dybcio
2026-08-10 16:55 ` [PATCH 4/7] dt-bindings: arm: qcom: Document LeEco Le2 Adam Skladowski
2026-08-14 10:34 ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 5/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-10 17:49 ` sashiko-bot
2026-08-11 9:16 ` Dmitry Baryshkov
2026-08-17 15:57 ` Konrad Dybcio
2026-08-10 16:55 ` [PATCH 6/7] dt-bindings: arm: qcom: Document Xiaomi Redmi 9T Adam Skladowski
2026-08-14 10:34 ` Krzysztof Kozlowski
2026-08-10 16:55 ` [PATCH 7/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-11 9:19 ` Dmitry Baryshkov
2026-08-17 16:08 ` Konrad Dybcio [this message]
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=79c3c201-395b-4a89-bd4f-0e64a59a1fa8@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=a39.skl@gmail.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=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