From: Francesco Dolcini <francesco@dolcini.it>
To: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
Cc: Tom Rini <trini@konsulko.com>,
Stefano Babic <sbabic@nabladev.com>,
Fabio Estevam <festevam@gmail.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
Peng Fan <peng.fan@nxp.com>, Alice Guo <alice.guo@nxp.com>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/3] add Toradex Verdin iMX95 support
Date: Thu, 16 Apr 2026 11:03:56 +0200 [thread overview]
Message-ID: <20260416090356.GA33737@francesco-nb> (raw)
In-Reply-To: <20260416084535.1490476-1-ghidoliemanuele@gmail.com>
On Thu, Apr 16, 2026 at 10:45:22AM +0200, Emanuele Ghidoli wrote:
> From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
>
> This series adds initial U-Boot support for the Toradex Verdin iMX95.
>
> It also introduces a new RAM-size probing helper based on alias checks.
> On Verdin iMX95, the first DDR region is reserved for Cortex-M7 firmware and
> the get_ram_size() could not be used to detect the actual RAM size.
> Using explicit probe/alias pairs provides reliable size detection for the
> supported memory variants.
Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com>
prev parent reply other threads:[~2026-04-16 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 8:45 [PATCH v1 0/3] add Toradex Verdin iMX95 support Emanuele Ghidoli
2026-04-16 8:45 ` [PATCH v1 1/3] common: memsize: add RAM size probe based on alias detection Emanuele Ghidoli
2026-04-16 21:07 ` Simon Glass
2026-04-16 8:45 ` [PATCH v1 2/3] board: toradex: add Toradex Verdin iMX95 Emanuele Ghidoli
2026-04-16 21:08 ` Simon Glass
2026-04-16 8:45 ` [PATCH v1 3/3] toradex: tdx-cfg-block: add verdin imx95 0226, 0227 and 0228 pid4 Emanuele Ghidoli
2026-04-16 21:08 ` Simon Glass
2026-04-16 9:03 ` Francesco Dolcini [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=20260416090356.GA33737@francesco-nb \
--to=francesco@dolcini.it \
--cc=alice.guo@nxp.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=ghidoliemanuele@gmail.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@nabladev.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@oss.qualcomm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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