From: sashiko-bot@kernel.org
To: "Chris Morgan" <macroalpha82@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH V6 6/6] arm64: dts: rockchip: Add Anbernic RG Vita-Pro
Date: Mon, 08 Jun 2026 18:12:43 +0000 [thread overview]
Message-ID: <20260608181244.047CC1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260608175521.67449-7-macroalpha82@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The SPI joysticks are inaccessible from userspace due to a missing SPI child node.
--
commit 2097a3f0d4026d4220ee53d9f1d7508fedf974d2
Author: Chris Morgan <macromorgan@hotmail.com>
arm64: dts: rockchip: Add Anbernic RG Vita-Pro
This commit adds a device tree for the Anbernic RG Vita-Pro based on the
Rockchip RK3576. It sets up definitions and configurations for various
hardware components like display, buttons, battery, and networking.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-anbernic-rg-vita-pro.dts b/arch/arm64/boot/dts/rockchip/rk3576-anbernic-rg-vita-pro.dts
> new file mode 100644
> index 0000000000000..344ba18705338
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3576-anbernic-rg-vita-pro.dts
> @@ -0,0 +1,1327 @@
[ ... ]
> +&spi1 {
> + num-cs = <1>;
> + pinctrl-0 = <&spi1m2_pins>, <&spi1m2_csn0>;
> + status = "okay";
> +
> + /* SPI controlled MCU for joystick and joystick LEDs. */
> +};
[Severity: High]
The commit message mentions "2 Analog joysticks controlled via userspace",
and this comment notes an SPI controlled MCU for the joystick. However,
there is no child node defined under this &spi1 controller.
Without a child node binding to a driver, the SPI core will not instantiate
a logical device, preventing userspace from communicating with the
joysticks. Could a spidev or similar child node be added here to expose the
interface?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260608175521.67449-1-macroalpha82@gmail.com?part=6
prev parent reply other threads:[~2026-06-08 18:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 17:55 [PATCH V6 0/6] Add Anbernic RG Vita-Pro Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 17:55 ` [PATCH V6 1/6] dt-bindings: power: supply: sgm41542: document sgm41542 Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 17:55 ` [PATCH V6 2/6] power: supply: sgm41542: Add SG Micro sgm41542 charger Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 18:09 ` sashiko-bot
2026-06-08 21:19 ` Sebastian Reichel
2026-06-08 21:19 ` Sebastian Reichel
2026-06-08 17:55 ` [PATCH V6 3/6] dt-bindings: display: panel: Add Anbernic TD4310 panel Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 17:55 ` [PATCH V6 4/6] drm/panel: anbernic-td4310: Add RG Vita Pro panel Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 18:06 ` sashiko-bot
2026-06-08 17:55 ` [PATCH V6 5/6] dt-bindings: arm: rockchip: Add Anbernic RG Vita-Pro Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 17:55 ` [PATCH V6 6/6] arm64: dts: " Chris Morgan
2026-06-08 17:55 ` Chris Morgan
2026-06-08 18:12 ` sashiko-bot [this message]
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=20260608181244.047CC1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=macroalpha82@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.