From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-mtd@lists.infradead.org
Cc: marex@denx.de, devicetree@vger.kernel.org, bbrezillon@kernel.org,
tudor.ambarus@microchip.com, linux-kernel@vger.kernel.org,
dinguyen@kernel.org, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: [PATCHv4 1/2] dt-bindings: cadence-quadspi: add options reset property
Date: Wed, 8 May 2019 08:43:37 -0500 [thread overview]
Message-ID: <20190508134338.20565-1-dinguyen@kernel.org> (raw)
The QSPI module can have an optional reset signals that will hold the
module in a reset state.
Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
---
v4: no change
v3: created base on review comments
v2: did not exist
v1: did not exist
---
Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
index 4345c3a6f530..b6264323a03c 100644
--- a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
+++ b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
@@ -35,6 +35,8 @@ custom properties:
(qspi_n_ss_out).
- cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
and first bit transfer.
+- resets : Must contain an entry for each entry in reset-names.
+ See ../reset/reset.txt for details.
Example:
@@ -50,6 +52,8 @@ Example:
cdns,fifo-depth = <128>;
cdns,fifo-width = <4>;
cdns,trigger-address = <0x00000000>;
+ resets = <&rst QSPI_RESET>, <&rst QSPI_OCP_RESET>;
+ reset-names = "qspi", "qspi-ocp";
flash0: n25q00@0 {
...
--
2.20.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-mtd@lists.infradead.org
Cc: dinguyen@kernel.org, marex@denx.de, tudor.ambarus@microchip.com,
dwmw2@infradead.org, computersforpeace@gmail.com,
bbrezillon@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCHv4 1/2] dt-bindings: cadence-quadspi: add options reset property
Date: Wed, 8 May 2019 08:43:37 -0500 [thread overview]
Message-ID: <20190508134338.20565-1-dinguyen@kernel.org> (raw)
The QSPI module can have an optional reset signals that will hold the
module in a reset state.
Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
---
v4: no change
v3: created base on review comments
v2: did not exist
v1: did not exist
---
Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
index 4345c3a6f530..b6264323a03c 100644
--- a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
+++ b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
@@ -35,6 +35,8 @@ custom properties:
(qspi_n_ss_out).
- cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
and first bit transfer.
+- resets : Must contain an entry for each entry in reset-names.
+ See ../reset/reset.txt for details.
Example:
@@ -50,6 +52,8 @@ Example:
cdns,fifo-depth = <128>;
cdns,fifo-width = <4>;
cdns,trigger-address = <0x00000000>;
+ resets = <&rst QSPI_RESET>, <&rst QSPI_OCP_RESET>;
+ reset-names = "qspi", "qspi-ocp";
flash0: n25q00@0 {
...
--
2.20.0
next reply other threads:[~2019-05-08 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 13:43 Dinh Nguyen [this message]
2019-05-08 13:43 ` [PATCHv4 1/2] dt-bindings: cadence-quadspi: add options reset property Dinh Nguyen
2019-05-08 13:43 ` [PATCHv4 2/2] mtd: spi-nor: cadence-quadspi: add reset control Dinh Nguyen
2019-05-08 13:43 ` Dinh Nguyen
2019-06-06 8:26 ` Tudor.Ambarus
2019-06-06 8:26 ` Tudor.Ambarus
2019-06-06 8:26 ` Tudor.Ambarus
2019-06-11 21:35 ` Dinh Nguyen
2019-06-11 21:35 ` Dinh Nguyen
2019-05-13 15:28 ` [PATCHv4 1/2] dt-bindings: cadence-quadspi: add options reset property Rob Herring
2019-05-13 15:28 ` Rob Herring
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=20190508134338.20565-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=tudor.ambarus@microchip.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.