From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v1 6/7] ARM: tegra: lg-x3: Add haptic engine node
Date: Thu, 24 Sep 2026 09:15:55 +0000 [thread overview]
Message-ID: <20260924091555.BA77A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924090608.28734-7-clamor95@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: missing dt-binding schema for Imagis ISA1200 haptic engine
--
commit bcc2e5a5981cf130d7fde2c4cf8724ed6f15c474
Author: Svyatoslav Ryhel <clamor95@gmail.com>
ARM: tegra: lg-x3: Add haptic engine node
This commit adds a device tree node for the Imagis ISA1200 haptic motor
driver used in the tegra30-lg-x3 device.
> diff --git a/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi b/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
> index 14d4f992222c6..c7ad3819c21d9 100644
> --- a/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
> +++ b/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
> @@ -1568,6 +1568,30 @@ power-sensor@40 {
> vs-supply = <&vdd_3v0_sen>;
> };
>
> + haptic-engine@49 {
> + compatible = "imagis,isa1200";
> + reg = <0x49>;
> +
> + control-gpios = <&gpio TEGRA_GPIO(H, 1) GPIO_ACTIVE_HIGH>;
> +
> + pwms = <&pwm 3 53000>;
> +
> + vdd-supply = <&vdd_3v3_vbat>;
> + vddp-supply = <&vdd_1v8_vio>;
> +
> + imagis,clk-div = <128>;
> + imagis,pll-div = <1>;
> +
> + imagis,mode = <0>; /* LRA_MODE */
> + imagis,duty-cycle-ns = <1250>;
> +
> + ldo {
> + regulator-name = "vdd_vib";
> + regulator-min-microvolt = <2300000>;
> + regulator-max-microvolt = <2300000>;
> + };
> + };
[Severity: Medium]
Are the dt-binding schema and the driver for the "imagis,isa1200" compatible
string missing?
There appears to be no dt-binding schema (YAML or txt) documenting these
custom vendor properties (e.g., "imagis,clk-div", "imagis,mode") or the "ldo"
subnode, nor a driver that matches this compatible.
Adding undocumented properties and using magic values (e.g.,
`<0> /* LRA_MODE */` instead of a dt-binding macro) violates device tree
standards, causes `make dtbs_check` validation failures, and establishes an
unreviewed ABI.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924090608.28734-1-clamor95@gmail.com?part=6
next prev parent reply other threads:[~2026-09-24 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 9:06 [PATCH v1 0/7] ARM: tegra: lg-x3: Add newly supported devices and fixes Svyatoslav Ryhel
2026-09-24 9:06 ` [PATCH v1 1/7] ARM: tegra: lg-x3: Adjust WiFi node Svyatoslav Ryhel
2026-09-24 9:06 ` [PATCH v1 2/7] ARM: tegra: lg-x3: Remove pinctrl-* properties duplication Svyatoslav Ryhel
2026-09-24 9:06 ` [PATCH v1 3/7] ARM: tegra: lg-x3: Lower supported suspend mode Svyatoslav Ryhel
2026-09-24 9:06 ` [PATCH v1 4/7] ARM: tegra: lg-x3: Add light sensor node Svyatoslav Ryhel
2026-09-24 9:15 ` sashiko-bot
2026-09-24 9:06 ` [PATCH v1 5/7] ARM: tegra: lg-x3: Add flash LEDs controller node Svyatoslav Ryhel
2026-09-24 9:16 ` sashiko-bot
2026-09-24 9:06 ` [PATCH v1 6/7] ARM: tegra: lg-x3: Add haptic engine node Svyatoslav Ryhel
2026-09-24 9:15 ` sashiko-bot [this message]
2026-09-24 9:06 ` [PATCH v1 7/7] ARM: tegra: lg-x3: Add backlight LED controller node Svyatoslav Ryhel
2026-09-24 9:20 ` sashiko-bot
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=20260924091555.BA77A1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=clamor95@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