From: Vignesh R <vigneshr@ti.com>
To: Vignesh R <vigneshr@ti.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Rob Herring <robh+dt@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, <linux-mtd@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<tudor.ambarus@microchip.com>, <nsekhar@ti.com>
Subject: [RFC PATCH 2/5] dt-bindings: mtd: Add binding documentation for Hyperbus memory devices
Date: Tue, 19 Feb 2019 12:06:04 +0530 [thread overview]
Message-ID: <20190219063607.29949-3-vigneshr@ti.com> (raw)
In-Reply-To: <20190219063607.29949-1-vigneshr@ti.com>
Add DT binding documentation for Hyperbus memory devices. For now only
Hyperflash is supported.
Signed-off-by: Vignesh R <vigneshr@ti.com>
---
Documentation/devicetree/bindings/mtd/cypress,hyperbus.txt | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperbus.txt
diff --git a/Documentation/devicetree/bindings/mtd/cypress,hyperbus.txt b/Documentation/devicetree/bindings/mtd/cypress,hyperbus.txt
new file mode 100644
index 000000000000..cb408f80b868
--- /dev/null
+++ b/Documentation/devicetree/bindings/mtd/cypress,hyperbus.txt
@@ -0,0 +1,6 @@
+Bindings for Hyperflash NOR flash chips compliant with Cypress Hyperbus
+specification and supports Cypress CFI specification 1.5 command set.
+
+Required properties:
+- compatible : "cypress,hyperflash" for Hyperflash NOR chips
+- reg : Address where flash's memory mapped space
--
2.20.1
next prev parent reply other threads:[~2019-02-19 6:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 6:36 [RFC PATCH 0/5] MTD: Add Initial Hyperbus support Vignesh R
2019-02-19 6:36 ` [RFC PATCH 1/5] mtd: cfi_cmdset_0002: Add support for polling status register Vignesh R
2019-02-23 18:41 ` Sergei Shtylyov
2019-02-23 18:44 ` Sergei Shtylyov
2019-02-19 6:36 ` Vignesh R [this message]
2019-02-19 6:36 ` [RFC PATCH 3/5] mtd: Add support for Hyperbus memory devices Vignesh R
2019-02-23 20:19 ` Sergei Shtylyov
2019-02-25 18:21 ` Vignesh R
2019-02-25 19:33 ` Sergei Shtylyov
2019-02-26 10:26 ` Vignesh R
2019-02-26 11:08 ` Sergei Shtylyov
2019-02-26 11:00 ` Vignesh R
2019-02-25 18:26 ` Sergei Shtylyov
2019-02-26 18:16 ` Sergei Shtylyov
2019-02-27 9:52 ` Vignesh Raghavendra
2019-02-27 9:59 ` Boris Brezillon
2019-02-27 10:12 ` Vignesh Raghavendra
2019-02-19 6:36 ` [RFC PATCH 4/5] dt-bindings: mtd: Add bindings for TI's AM654 Hyperbus memory controller Vignesh R
2019-02-19 6:36 ` [RFC PATCH 5/5] mtd: hyperbus: Add driver for TI's " Vignesh R
2019-02-24 14:06 ` Sergei Shtylyov
2019-02-25 16:29 ` Sergei Shtylyov
2019-02-26 10:18 ` Vignesh R
2019-02-26 18:28 ` Sergei Shtylyov
2019-02-19 7:24 ` [RFC PATCH 0/5] MTD: Add Initial Hyperbus support Vignesh R
2019-02-19 7:52 ` Boris Brezillon
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=20190219063607.29949-3-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=arnd@arndb.de \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=nsekhar@ti.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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 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).