From: Andrew Lunn <andrew@lunn.ch>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, stefan@agner.ch,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 2/2] dt-bindings: gpio: vf610: update gpio-ranges
Date: Tue, 28 Mar 2023 16:48:02 +0200 [thread overview]
Message-ID: <de82d0ff-3e2f-4822-8430-13e2b1633b3a@lunn.ch> (raw)
In-Reply-To: <20230328052912.1957000-2-peng.fan@oss.nxp.com>
On Tue, Mar 28, 2023 at 01:29:12PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> 1 is not enough for i.MX9, enlarge it.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Documentation/devicetree/bindings/gpio/gpio-vf610.yaml | 3 ++-
I'm not that knowledgeable about i.MX9, but i thought vf610 was
Vybrid, which is not an i.MX9. Does i.MX9 reuse the Vybrid GPIO
controller? Is this change also valid for the Vybrid?
Andrew
next prev parent reply other threads:[~2023-03-28 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 5:29 [PATCH 1/2] dt-bindings: gpio: fsl-imx-gpio: " Peng Fan (OSS)
2023-03-28 5:29 ` [PATCH 2/2] dt-bindings: gpio: vf610: " Peng Fan (OSS)
2023-03-28 14:45 ` Krzysztof Kozlowski
2023-03-28 14:48 ` Andrew Lunn [this message]
2023-03-29 9:21 ` Peng Fan
2023-03-29 12:14 ` Andrew Lunn
2023-03-28 12:57 ` [PATCH 1/2] dt-bindings: gpio: fsl-imx-gpio: " Rob Herring
2023-03-28 13:57 ` Rob Herring
2023-03-28 14:48 ` Krzysztof Kozlowski
2023-03-28 14:47 ` Krzysztof Kozlowski
2023-03-31 12:22 ` Linus Walleij
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=de82d0ff-3e2f-4822-8430-13e2b1633b3a@lunn.ch \
--to=andrew@lunn.ch \
--cc=brgl@bgdev.pl \
--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=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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
all inboxes | Powered by JetHome®