From: Ashish Kumar <Ashish.Kumar@nxp.com>
To: devicetree@vger.kernel.org
Cc: bbrezillon@kernel.org, Kuldeep Singh <kuldeep.singh@nxp.com>,
Ashish Kumar <ashish.kumar@nxp.com>,
broonie@kernel.org, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [Patch v3 1/2] dt-bindings: spi: spi-fsl-qspi: Add ls2080a compatibility string to bindings
Date: Wed, 19 Jun 2019 16:41:53 +0530 [thread overview]
Message-ID: <1560942714-13330-2-git-send-email-Ashish.Kumar@nxp.com> (raw)
In-Reply-To: <1560942714-13330-1-git-send-email-Ashish.Kumar@nxp.com>
There are 2 version of QSPI-IP, according to which controller registers sets
can be big endian or little endian.There are some other minor changes like
RX fifo depth etc.
The big endian version uses driver compatible "fsl,ls1021a-qspi" and
little endian version uses driver compatible "fsl,ls2080a-qspi"
Signed-off-by: Kuldeep Singh <kuldeep.singh@nxp.com>
Signed-off-by: Ashish Kumar <ashish.kumar@nxp.com>
---
v3:
Rebase to top
v2:
Convert to patch series and rebasing done on top of tree
Documentation/devicetree/bindings/spi/spi-fsl-qspi.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/spi/spi-fsl-qspi.txt b/Documentation/devicetree/bindings/spi/spi-fsl-qspi.txt
index e8f1d62..6d7c9ec 100644
--- a/Documentation/devicetree/bindings/spi/spi-fsl-qspi.txt
+++ b/Documentation/devicetree/bindings/spi/spi-fsl-qspi.txt
@@ -3,9 +3,8 @@
Required properties:
- compatible : Should be "fsl,vf610-qspi", "fsl,imx6sx-qspi",
"fsl,imx7d-qspi", "fsl,imx6ul-qspi",
- "fsl,ls1021a-qspi"
+ "fsl,ls1021a-qspi", "fsl,ls2080a-qspi"
or
- "fsl,ls2080a-qspi" followed by "fsl,ls1021a-qspi",
"fsl,ls1043a-qspi" followed by "fsl,ls1021a-qspi"
- reg : the first contains the register location and length,
the second contains the memory mapping address and length
--
2.7.4
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-06-19 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:11 [PATCH] drivers: mtd: spi-nor: Add flash property for mt25qu512a and mt35xu02g Ashish Kumar
2019-06-19 11:11 ` Ashish Kumar [this message]
2019-07-09 20:08 ` [Patch v3 1/2] dt-bindings: spi: spi-fsl-qspi: Add ls2080a compatibility string to bindings Rob Herring
2019-07-29 9:11 ` [EXT] " Ashish Kumar
2019-07-31 23:26 ` Leo Li
2019-08-01 7:09 ` Ashish Kumar
2019-08-01 15:22 ` Han Xu
2019-08-05 9:08 ` [EXT] " Ashish Kumar
2019-08-05 11:13 ` Mark Brown
2019-06-19 11:11 ` [Patch v3 2/2] dt-bindings: spi: spi-fsl-qspi: Add bindings of ls1088a and ls1012a Ashish Kumar
2019-07-09 20:08 ` Rob Herring
2019-07-29 9:08 ` [EXT] " Ashish Kumar
2019-07-31 23:28 ` Leo Li
2019-08-01 7:09 ` Ashish Kumar
2019-08-01 15:24 ` Han Xu
2019-08-05 9:07 ` [EXT] " Ashish Kumar
2019-08-05 11:13 ` Mark Brown
2019-06-21 5:37 ` [PATCH] drivers: mtd: spi-nor: Add flash property for mt25qu512a and mt35xu02g Vignesh Raghavendra
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=1560942714-13330-2-git-send-email-Ashish.Kumar@nxp.com \
--to=ashish.kumar@nxp.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuldeep.singh@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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).