From: Marek Vasut <marex@nabladev.com>
To: Frank.Li@kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
Vincent Mailhol <mailhol@kernel.org>,
robh@kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
imx@lists.linux.dev, Oleksij Rempel <o.rempel@pengutronix.de>,
linux-can@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
Date: Thu, 17 Sep 2026 03:33:37 +0200 [thread overview]
Message-ID: <d300a86a-2704-41cd-8848-6b0871037ede@nabladev.com> (raw)
In-Reply-To: <20260917012032.982291F000FF@smtp.kernel.org>
On 9/17/26 3:20 AM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 7 potential issue(s) to consider:
> - [High] dts: imx95: I2C expanders stuck in reset due to gpio-hog mismatch
This is valid.
> - [Medium] dts: imx95: Incorrect PCAL6524 interrupt polarity
No, Hardware has inverter.
> - [Medium] dts: imx95: Ethernet PHY reset held active due to wrong polarity
No, inverter.
> - [Medium] dts: imx95: Missing pinctrl for Ethernet PHY interrupt
No, GPIO1 pinmux is set by SM.
> - [Medium] dts: imx95: M.2 Key-E (usdhc3) slot left unpowered
No.
> - [Medium] dts: imx95: reg_panel_vcc inverted polarity missing enable-active-high
No, Controlled via DTO.
> - [Low] dts: imx95: reg_pcie1 misnamed as Key-E instead of Key-M
This is valid.
prev parent reply other threads:[~2026-09-17 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 1:08 [PATCH 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563 Marek Vasut
2026-09-17 1:08 ` [PATCH 2/3] dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC Marek Vasut
2026-09-17 1:08 ` [PATCH 3/3] arm64: dts: imx95: Add support for " Marek Vasut
2026-09-17 1:20 ` sashiko-bot
2026-09-17 1:33 ` Marek Vasut [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=d300a86a-2704-41cd-8848-6b0871037ede@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=socketcan@hartkopp.net \
/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