All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Antoine Gouby <antoine.gouby@gmail.com>
Cc: "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
	u-boot@lists.denx.de, Stefano Babic <sbabic@nabladev.com>,
	Fabio Estevam <festevam@gmail.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Tom Rini <trini@konsulko.com>,
	Ernest Van Hoecke <ernest.vanhoecke@toradex.com>,
	Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
	Antoine Gouby <antoine.gouby@toradex.com>
Subject: Re: [PATCH 0/2] board: toradex: imx95: remove gpio1 reg
Date: Wed, 13 May 2026 19:13:11 +0800	[thread overview]
Message-ID: <agRcx1GtLEwuNHJp@shlinux89> (raw)
In-Reply-To: <20260506-v1-remove-gpio1-reg-v1-0-d5e09f936d90@toradex.com>

On Wed, May 06, 2026 at 01:42:19PM +0200, Antoine Gouby wrote:
>This series removes gpio1 reg from Toradex SMARC iMX95 and Verdin iMX95
>device trees.
>
>The RGPIO2P driver contains legacy handling for compatible combinations
>that expose two reg ranges (dual base) for i.MX8ULP and i.MX93.
>
>The i.MX95 GPIO controller exposes a single register range, so the 
>dual-base handling is unnecessary.
>
>On Verdin iMX95, the second address of the gpio1 reg node was incorrect.
>When used, it needs to be offsetted by 0x40 to start at the Port Data
>Output register.
>
>Signed-off-by: Antoine Gouby <antoine.gouby@toradex.com>

Reviewed-by: Peng Fan <peng.fan@nxp.com>

      parent reply	other threads:[~2026-05-13 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 11:42 [PATCH 0/2] board: toradex: imx95: remove gpio1 reg Antoine Gouby
2026-05-06 11:42 ` [PATCH 1/2] board: toradex: smarc-imx95: " Antoine Gouby
2026-05-06 11:42 ` [PATCH 2/2] board: toradex: verdin-imx95: " Antoine Gouby
2026-05-13 11:13 ` Peng Fan [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=agRcx1GtLEwuNHJp@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=antoine.gouby@gmail.com \
    --cc=antoine.gouby@toradex.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=sbabic@nabladev.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 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.