From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8650: Add initial Valve Deckard devicetree
Date: Tue, 22 Sep 2026 11:42:34 +0000 [thread overview]
Message-ID: <20260922114234.92CC21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922-topic-sm8650-deckard-initial-dt-v1-2-c25e7759d04a@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: incorrect regulator supply names for vishay,vcnl4040
--
commit 04ec091c4806a5aef627fbe5d3809fe2eef39d6e
Author: Neil Armstrong <neil.armstrong@linaro.org>
arm64: dts: qcom: sm8650: Add initial Valve Deckard devicetree
This commit adds the initial devicetree for the Valve "Steam Frame" (codename
Deckard), a VR headset based on the Snapdragon 8 Gen 3 SoC. It includes
definitions for reserved memory, regulators, GPIOs, UFS storage, USB,
Wi-Fi/Bluetooth, and I2C peripherals.
> diff --git a/arch/arm64/boot/dts/qcom/sm8650-valve-deckard.dts b/arch/arm64/boot/dts/qcom/sm8650-valve-deckard.dts
> new file mode 100644
> index 0000000000000..cd801359d2b57
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm8650-valve-deckard.dts
[ ... ]
> + light-sensor@60 {
> + compatible = "vishay,vcnl4040";
> + reg = <0x60>;
> +
> + vin0-supply = <&vreg_l2b_3p0>;
> + vin1-supply = <&vreg_l15b_1p8>;
[Severity: Medium]
Will the vcnl4000 driver be able to properly find and enable these regulators?
The driver expects the regulators to be named vdd, vio, and vled, but here
they are provided as vin0-supply and vin1-supply. Because they are not bound
to the names the driver expects, they might remain off or get disabled by a
late initcall, potentially causing the sensor to fail probing or I2C
communication.
> +
> + proximity-near-level = <220>;
> + };
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922-topic-sm8650-deckard-initial-dt-v1-0-c25e7759d04a@linaro.org?part=2
next prev parent reply other threads:[~2026-09-22 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:28 [PATCH 0/2] arm64: dts: qcom: sm8650: add support from Valve Deckard headset Neil Armstrong
2026-09-22 11:28 ` [PATCH 1/2] dt-bindings: arm: qcom: document the " Neil Armstrong
2026-09-22 11:28 ` [PATCH 2/2] arm64: dts: qcom: sm8650: Add initial Valve Deckard devicetree Neil Armstrong
2026-09-22 11:39 ` Konrad Dybcio
2026-09-22 11:46 ` Neil Armstrong
2026-09-22 11:52 ` Konrad Dybcio
2026-09-22 11:42 ` sashiko-bot [this message]
2026-09-22 11:48 ` Neil Armstrong
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=20260922114234.92CC21F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=neil.armstrong@linaro.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