Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Adam Skladowski" <a39.skl@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 7/7] arm64: dts: qcom: Add Xiaomi Redmi 9T
Date: Thu, 20 Aug 2026 09:53:23 +0000	[thread overview]
Message-ID: <20260820095323.810081F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820-next-patches-v2-7-7130d68183d9@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Invalid `brightness-levels` property in `led-backlight` triggers boot warning and is ignored.
--

--- Patch [7]: [PATCH v2 7/7] arm64: dts: qcom: Add Xiaomi Redmi 9T ---
commit 98a4b41cf18b5589a5dbba3f7c9d120fe90da54f
Author: Adam Skladowski <a39.skl@gmail.com>

arm64: dts: qcom: Add Xiaomi Redmi 9T

This commit adds a devicetree for the Xiaomi Redmi 9T smartphone, which is 
based on the Bengal/SM6115 SoC. It introduces initial support for features 
like display, GPU, regulators, UFS, USB, and remoteprocs.

> diff --git a/arch/arm64/boot/dts/qcom/sm6115-xiaomi-lemon.dts b/arch/arm64/boot/dts/qcom/sm6115-xiaomi-lemon.dts
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm6115-xiaomi-lemon.dts

[ ... ]

> +	backlight_dsi: backlight-dsi {
> +		compatible = "led-backlight";
> +		leds = <&led_backlight>;
> +		brightness-levels = <255>;

[Severity: Low]
Does providing a single value to brightness-levels trigger a boot warning? 

The led-backlight driver typically expects brightness-levels to be an array 
of multiple values mapping an index to a brightness level. Providing a single 
element causes the driver to emit a "Not enough levels defined" warning during 
probe and ignores the property completely.

> +		default-brightness-level = <190>;
> +		/* Backlight controllers can differ between panel variants */
> +		status = "disabled";
> +	};

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260820-next-patches-v2-0-7130d68183d9@gmail.com?part=7

  reply	other threads:[~2026-08-20  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  9:42 [PATCH v2 0/7] arm64: dts: qcom: Add 3 new devices Adam Skladowski
2026-08-20  9:42 ` [PATCH v2 1/7] dt-bindings: vendor-prefixes: Add LeEco Adam Skladowski
2026-08-20  9:42 ` [PATCH v2 2/7] dt-bindings: arm: qcom: Document Motorola Moto One Adam Skladowski
2026-08-20  9:42 ` [PATCH v2 3/7] arm64: dts: qcom: Add Motorola One Adam Skladowski
2026-08-20  9:56   ` sashiko-bot
2026-08-20 10:17   ` Konrad Dybcio
2026-08-20 15:24     ` Adam Skladowski
2026-08-20 15:56       ` Konrad Dybcio
2026-08-20  9:42 ` [PATCH v2 4/7] dt-bindings: arm: qcom: Document LeEco Le2 Adam Skladowski
2026-08-20  9:42 ` [PATCH v2 5/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-20  9:59   ` sashiko-bot
2026-08-20 10:14   ` Konrad Dybcio
2026-08-20  9:42 ` [PATCH v2 6/7] dt-bindings: arm: qcom: Document Xiaomi Redmi 9T Adam Skladowski
2026-08-20  9:42 ` [PATCH v2 7/7] arm64: dts: qcom: Add " Adam Skladowski
2026-08-20  9:53   ` sashiko-bot [this message]
2026-08-20 10:14   ` Konrad Dybcio

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=20260820095323.810081F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=a39.skl@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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