Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dmitry Yashin" <dmt.yashin@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: rockchip: add Forlinx FET3568-C
Date: Wed, 30 Sep 2026 09:46:13 +0000	[thread overview]
Message-ID: <20260930094614.573E81F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930-ok3568-c-v1-2-a0ffd55f5c95@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt: missing dt-bindings/leds/common.h include in rk3568-fet3568-c.dtsi
--

commit ad3d32e56e87934cf5904354535bfdac90366416
Author: Dmitry Yashin <dmt.yashin@gmail.com>

arm64: dts: rockchip: add Forlinx FET3568-C

This commit adds the device tree source for the Forlinx FET3568-C System on
Module based on the Rockchip RK3568 SoC. It configures the CPU, GPU, I2C,
PMIC, eMMC, and basic LED nodes for the SoM.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3568-fet3568-c.dtsi b/arch/arm64/boot/dts/rockchip/rk3568-fet3568-c.dtsi
> new file mode 100644
> index 0000000000000..258e7591063fb
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3568-fet3568-c.dtsi
> @@ -0,0 +1,331 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include "rk3568.dtsi"
> +
> +/ {
> +	compatible = "forlinx,fet3568-c", "rockchip,rk3568";

[ ... ]

> +	leds {
> +		compatible = "gpio-leds";
> +
> +		led-0 {
> +			color = <LED_COLOR_ID_BLUE>;
> +			default-state = "on";
> +			function = LED_FUNCTION_HEARTBEAT;

[Severity: Low]
This file uses LED_COLOR_ID_BLUE and LED_FUNCTION_HEARTBEAT but doesn't
include <dt-bindings/leds/common.h>. Could we include the header directly
in this .dtsi file so it is fully self-contained? Relying on parent .dts
files to include it can cause build failures if this file is included by
other boards.

> +			gpios = <&gpio0 RK_PB7 GPIO_ACTIVE_HIGH>;
> +			linux,default-trigger = "heartbeat";
> +			pinctrl-names = "default";
> +			pinctrl-0 = <&led0_pin>;
> +		};
> +	};
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-ok3568-c-v1-0-a0ffd55f5c95@gmail.com?part=2

  reply	other threads:[~2026-09-30  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  9:29 [PATCH 0/4] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-09-30  9:29 ` [PATCH 1/4] dt-bindings: arm: rockchip: add Forlinx FET3568-C Dmitry Yashin
2026-10-01  8:32   ` Krzysztof Kozlowski
2026-09-30  9:29 ` [PATCH 2/4] arm64: dts: " Dmitry Yashin
2026-09-30  9:46   ` sashiko-bot [this message]
2026-09-30  9:29 ` [PATCH 3/4] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-09-30  9:55   ` sashiko-bot
2026-09-30 19:19   ` Andrew Lunn
2026-09-30  9:29 ` [PATCH 4/4] arm64: dts: rockchip: add FIT-PCIE-SATA overlay Dmitry Yashin

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=20260930094614.573E81F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmt.yashin@gmail.com \
    --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