linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Andy Shevchenko <andy@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Stefan Agner <stefan@agner.ch>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Marco Felsch <m.felsch@pengutronix.de>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v5 6/7] arm64: dts: imx8ulp: update gpio node
Date: Tue, 10 Oct 2023 09:44:00 +0800	[thread overview]
Message-ID: <20231010014400.GD819755@dragon> (raw)
In-Reply-To: <20231001-vf610-gpio-v5-6-8d873a8f224a@nxp.com>

On Sun, Oct 01, 2023 at 04:27:57PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> The i.MX8ULP GPIO supports two interrupts and one register base,
> the current fsl,imx7ulp-gpio compatible could work for i.MX8ULP in
> gpio-vf610.c driver, it is based on the base address are splited
> into two with offset added in device tree node. Now following
> hardware design, using one register base in device tree node.
> 
> This may break users who use compatible fsl,imx7ulp-gpio to enable
> i.MX8ULP GPIO.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>

Applied, thanks!

  reply	other threads:[~2023-10-10  1:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01  8:27 [PATCH v5 0/7] gpio: update i.MX93/8ULP and support i.MX95 Peng Fan (OSS)
2023-10-01  8:27 ` [PATCH v5 1/7] dt-bindings: gpio: vf610: update gpio-ranges Peng Fan (OSS)
2023-10-01  8:27 ` [PATCH v5 2/7] dt-bindings: gpio: vf610: correct i.MX8ULP and i.MX93 Peng Fan (OSS)
2023-10-01  8:27 ` [PATCH v5 3/7] dt-bindings: gpio: vf610: add i.MX95 compatible Peng Fan (OSS)
2023-10-01  8:27 ` [PATCH v5 4/7] gpio: vf610: add i.MX8ULP of_device_id entry Peng Fan (OSS)
2023-10-02  9:04   ` Bartosz Golaszewski
2023-10-02  9:43     ` Peng Fan
2023-10-04  5:04       ` Marco Felsch
2023-10-01  8:27 ` [PATCH v5 5/7] gpio: vf610: simplify code by dropping data check Peng Fan (OSS)
2023-10-01  8:27 ` [PATCH v5 6/7] arm64: dts: imx8ulp: update gpio node Peng Fan (OSS)
2023-10-10  1:44   ` Shawn Guo [this message]
2023-10-01  8:27 ` [PATCH v5 7/7] arm64: dts: imx93: " Peng Fan (OSS)
2023-10-10  1:44   ` Shawn Guo
2023-10-05 17:54 ` [PATCH v5 0/7] gpio: update i.MX93/8ULP and support i.MX95 Bartosz Golaszewski
2023-10-10  1:35 ` Peng Fan

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=20231010014400.GD819755@dragon \
    --to=shawnguo@kernel.org \
    --cc=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=stefan@agner.ch \
    /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;
as well as URLs for NNTP newsgroup(s).