From: Heiko Schocher <hs@denx.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Heiko Schocher <hs@denx.de>, Ashish Kumar <ashish.kumar@nxp.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Yogesh Gaur <yogeshgaur.83@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: [PATCH v2 2/4] dt-bindings: spi: add compatible entry for imx8mp in FlexSPI controller
Date: Tue, 9 Mar 2021 06:31:14 +0100 [thread overview]
Message-ID: <20210309053116.1486347-3-hs@denx.de> (raw)
In-Reply-To: <20210309053116.1486347-1-hs@denx.de>
add compatible entry "nxp,imx8mp-fspi" in NXP FlexSPI controller
Signed-off-by: Heiko Schocher <hs@denx.de>
---
(no changes since v1)
Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt b/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
index 7ac60d9fe3571..fd5f081f6d91b 100644
--- a/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
+++ b/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
@@ -4,6 +4,7 @@ Required properties:
- compatible : Should be "nxp,lx2160a-fspi"
"nxp,imx8qxp-fspi"
"nxp,imx8mm-fspi"
+ "nxp,imx8mp-fspi"
- reg : First contains the register location and length,
Second contains the memory mapping address and length
--
2.29.2
next prev parent reply other threads:[~2021-03-09 5:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 5:31 [PATCH v2 0/4] enable flexspi support on imx8mp Heiko Schocher
2021-03-09 5:31 ` [PATCH v2 1/4] spi: fspi: enable fspi driver for " Heiko Schocher
2021-03-09 5:31 ` Heiko Schocher [this message]
2021-03-09 5:56 ` [EXT] [PATCH v2 2/4] dt-bindings: spi: add compatible entry for imx8mp in FlexSPI controller Kuldeep Singh
2021-03-09 6:06 ` Heiko Schocher
2021-03-09 6:29 ` Kuldeep Singh
2021-03-09 6:44 ` Heiko Schocher
2021-03-09 8:19 ` [PATCH v2 0/4] enable flexspi support on imx8mp Marco Felsch
2021-03-09 8:41 ` Heiko Schocher
2021-03-15 6:47 ` Shawn Guo
2021-03-15 7:10 ` Heiko Schocher
2021-03-15 7:17 ` Shawn Guo
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=20210309053116.1486347-3-hs@denx.de \
--to=hs@denx.de \
--cc=ashish.kumar@nxp.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yogeshgaur.83@gmail.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;
as well as URLs for NNTP newsgroup(s).