From: sashiko-bot@kernel.org
To: "Aurelien Jarno" <aurelien@aurel32.net>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/5] riscv: dts: spacemit: enable the i2c2 adapter on K3 Pico-ITX board
Date: Sat, 20 Jun 2026 06:29:47 +0000 [thread overview]
Message-ID: <20260620062948.0A1161F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260620062238.3199108-3-aurelien@aurel32.net>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The pinctrl subnode is named `i2c2-0-pins` but belongs to the `i2c2-1-cfg` parent node.
- [Low] Missing space before the assignment operator in `bias-pull-up= <0>;`.
--
commit 4dc6c92d42831e85b38f3350c15707d0e2b3af18
Author: Aurelien Jarno <aurelien@aurel32.net>
riscv: dts: spacemit: enable the i2c2 adapter on K3 Pico-ITX board
This commit defines the I2C2 pinctrl properties and enables the adapter
on the K3 Pico-ITX board. It will be used by the 24c02 eeprom.
> diff --git a/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi b/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
> index 23899d3f308a0..c9fe9c2e5aeee 100644
> --- a/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi
[ ... ]
> @@ -45,6 +45,17 @@ gmac0-phy-0-pins {
> };
> };
>
> + /omit-if-no-ref/
> + i2c2_1_cfg: i2c2-1-cfg {
> + i2c2-0-pins {
[Severity: Low]
This isn't a bug, but should this subnode be named i2c2-1-pins to match
the i2c2-1-cfg parent node? It seems to diverge from the standard naming
pattern where the suffix of the parent and child matches.
> + pinmux = <K3_PADCONF(46, 5)>, /* i2c2 scl */
> + <K3_PADCONF(47, 5)>; /* i2c2 sda */
> +
> + bias-pull-up= <0>;
[Severity: Low]
This isn't a bug, but there is a missing space before the equals sign
here, which diverges from the spacing used in the surrounding code.
> + drive-strength = <25>;
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260620062238.3199108-1-aurelien@aurel32.net?part=2
next prev parent reply other threads:[~2026-06-20 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260620062238.3199108-1-aurelien@aurel32.net>
2026-06-20 6:22 ` [PATCH 1/5] riscv: dts: spacemit: set console baud rate on K3 Pico-ITX board Aurelien Jarno
2026-06-20 9:03 ` Guodong Xu
2026-06-20 6:22 ` [PATCH 2/5] riscv: dts: spacemit: enable the i2c2 adapter " Aurelien Jarno
2026-06-20 6:29 ` sashiko-bot [this message]
2026-06-21 13:14 ` Aurelien Jarno
2026-06-20 6:22 ` [PATCH 3/5] riscv: dts: spacemit: add 24c02 eeprom " Aurelien Jarno
2026-06-20 6:22 ` [PATCH 4/5] riscv: dts: spacemit: add i2c aliases " Aurelien Jarno
2026-06-20 6:22 ` [PATCH 5/5] riscv: dts: spacemit: improve RTL8211F PHY configuration " Aurelien Jarno
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=20260620062948.0A1161F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=aurelien@aurel32.net \
--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