From: michal.simek@xilinx.com (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 5/7] devicetree: bindings: Add zynq ocmc node description
Date: Mon, 1 Dec 2014 14:24:56 +0100 [thread overview]
Message-ID: <a408c70d8ce54e47e1b400dc2523b7886bf7fcef.1417440250.git.michal.simek@xilinx.com> (raw)
In-Reply-To: <cover.1417440250.git.michal.simek@xilinx.com>
Add binding for Zynq On Chip Memory controller driver
which is taking care about On Chip Memory.
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---
Changes in v5:
- Separate binding from the driver
Changes in v4: None
Changes in v3: None
Changes in v2: None
.../devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt
diff --git a/Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt b/Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt
new file mode 100644
index 000000000000..dcf221e8a16e
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt
@@ -0,0 +1,17 @@
+Device tree bindings for Zynq's OCM controller
+
+The OCM is divided to 4 64kB segments which can be separately configured
+to low or high location. Location is controlled via SLCR.
+
+Required properties:
+ compatible: Compatibility string. Must be "xlnx,zynq-ocmc-1.0".
+ reg: Specify the base and size of the OCMC registers in the memory map.
+ E.g.: reg = <0xf800c000 0x1000>;
+
+Example:
+ocmc: memory-controller at f800c000 {
+ compatible = "xlnx,zynq-ocmc-1.0";
+ interrupt-parent = <&intc>;
+ interrupts = <0 3 4>;
+ reg = <0xf800c000 0x1000>;
+};
--
1.8.2.3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141201/7cce9ab8/attachment.sig>
next prev parent reply other threads:[~2014-12-01 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 13:24 [PATCH v5 0/7] Xilinx Zynq OCM support Michal Simek
2014-12-01 13:24 ` [PATCH v5 1/7] ARM: zynq: Extract smp related functions out of common.h Michal Simek
2014-12-01 13:24 ` [PATCH v5 2/7] ARM: zynq: Extract slcr " Michal Simek
2014-12-01 13:24 ` [PATCH v5 3/7] ARM: zynq: Move slcr.h and smp.h to generic location Michal Simek
2014-12-01 13:24 ` [PATCH v5 4/7] ARM: zynq: Extend SLCR driver to read OCM configuration Michal Simek
2014-12-01 13:24 ` Michal Simek [this message]
2014-12-01 13:24 ` [PATCH v5 6/7] ARM: zynq: Add OCM controller driver Michal Simek
2014-12-01 15:31 ` Arnd Bergmann
2014-12-02 10:52 ` Michal Simek
2014-12-01 13:24 ` [PATCH v5 7/7] ARM: zynq: DT: Add OCM controller node Michal Simek
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=a408c70d8ce54e47e1b400dc2523b7886bf7fcef.1417440250.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=linux-arm-kernel@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).