From: Stefan Eichenberger <eichest@gmail.com>
To: francesco.dolcini@toradex.com, sbabic@nabladev.com,
festevam@gmail.com, uboot-imx@nxp.com, trini@konsulko.com,
franz.schnyder@toradex.com, emanuele.ghidoli@toradex.com,
stefan.eichenberger@toradex.com, ernest.vanhoecke@toradex.com,
alice.guo@nxp.com, peng.fan@nxp.com
Cc: u-boot@lists.u-boot-project.org
Subject: [PATCH v1 0/2] Cleanup i.MX95 based Toradex boards
Date: Wed, 19 Aug 2026 15:38:35 +0200 [thread overview]
Message-ID: <20260819133900.167046-1-eichest@gmail.com> (raw)
This series removes two leftovers from the Toradex i.MX95 board support.
The first patch drops CONFIG_SPI from the aquila-imx95, verdin-imx95 and
toradex-smarc-imx95 defconfigs. It has been set since the initial board
support, but none of the boards selects an SPI controller or slave
driver, so SPI is not usable in U-Boot on them anyway.
The second patch removes the WDOG_BASE_ADDR definition from
verdin-imx95.h. The ULP watchdog driver takes its base address from the
devicetree now, and the macro it expanded to no longer exists, so the
definition is dangling.
Neither patch changes behaviour, they only drop unused configuration.
All three boards were build tested.
Stefan Eichenberger (2):
configs: {aquila, verdin, toradex-smarc}-imx95: remove CONFIG_SPI
imx: verdin-imx95: remove unused WDOG_BASE_ADDR
configs/aquila-imx95_defconfig | 1 -
configs/toradex-smarc-imx95_defconfig | 1 -
configs/verdin-imx95_defconfig | 1 -
include/configs/verdin-imx95.h | 2 --
4 files changed, 5 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-19 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 13:38 Stefan Eichenberger [this message]
2026-08-19 13:38 ` [PATCH v1 1/2] configs: {aquila, verdin, toradex-smarc}-imx95: remove CONFIG_SPI Stefan Eichenberger
2026-08-19 13:38 ` [PATCH v1 2/2] imx: verdin-imx95: remove unused WDOG_BASE_ADDR Stefan Eichenberger
2026-08-19 13:43 ` [PATCH v1 0/2] Cleanup i.MX95 based Toradex boards Francesco Dolcini
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=20260819133900.167046-1-eichest@gmail.com \
--to=eichest@gmail.com \
--cc=alice.guo@nxp.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=ernest.vanhoecke@toradex.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=franz.schnyder@toradex.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@nabladev.com \
--cc=stefan.eichenberger@toradex.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=uboot-imx@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox