From: Vitor Soares <ivitro@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Vitor Soares <vitor.soares@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, ivitro@gmail.com
Subject: [PATCH v1 0/2] arm64: dts: imx95-toradex-smarc: Fix ethphy1 interrupt and GPIO labels
Date: Fri, 28 Nov 2025 15:00:26 +0000 [thread overview]
Message-ID: <20251128150030.35931-1-ivitro@gmail.com> (raw)
From: Vitor Soares <vitor.soares@toradex.com>
This series fixes the ethphy1 interrupt configuration and corrects GPIO
expander line names for the i.MX95 Toradex SMARC.
The first patch changes the interrupt trigger type from level-triggered
to edge-triggered to match the PCA9745 GPIO expander hardware
capabilities.
The second patch fixes the SMARC_SDIO_WP gpio-line-name position to
line 15.
Vitor Soares (2):
arm64: dts: freescale: imx95-toradex-smarc: use edge trigger for
ethphy1 interrupt
arm64: dts: freescale: imx95-toradex-smarc: fix SMARC_SDIO_WP label
position
arch/arm64/boot/dts/freescale/imx95-toradex-smarc.dtsi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-28 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 15:00 Vitor Soares [this message]
2025-11-28 15:00 ` [PATCH v1 1/2] arm64: dts: freescale: imx95-toradex-smarc: use edge trigger for ethphy1 interrupt Vitor Soares
2025-11-28 15:00 ` [PATCH v1 2/2] arm64: dts: freescale: imx95-toradex-smarc: fix SMARC_SDIO_WP label position Vitor Soares
2025-12-29 13:14 ` [PATCH v1 0/2] arm64: dts: imx95-toradex-smarc: Fix ethphy1 interrupt and GPIO labels Shawn Guo
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=20251128150030.35931-1-ivitro@gmail.com \
--to=ivitro@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vitor.soares@toradex.com \
/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.