All of lore.kernel.org
 help / color / mirror / Atom feed
From: bhupesh.sharma@freescale.com (Bhupesh Sharma)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v7 3/5] Documentation: DT: Add entry for FSL Management Complex
Date: Sun, 25 Jan 2015 02:42:51 +0530	[thread overview]
Message-ID: <1422133973-16460-4-git-send-email-bhupesh.sharma@freescale.com> (raw)
In-Reply-To: <1422133973-16460-1-git-send-email-bhupesh.sharma@freescale.com>

This patch adds a devicetree binding documentation for FSL's
Management Complex.

Management Complex is a hardware resource manager that manages
specialized hardware objects used in network-oriented packet
processing applications

Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
---
 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      |   40 ++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt

diff --git a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
new file mode 100644
index 0000000..c7a26ca
--- /dev/null
+++ b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
@@ -0,0 +1,40 @@
+* Freescale Management Complex
+
+The Freescale Management Complex (fsl-mc) is a hardware resource
+manager that manages specialized hardware objects used in
+network-oriented packet processing applications. After the fsl-mc
+block is enabled, pools of hardware resources are available, such as
+queues, buffer pools, I/O interfaces. These resources are building
+blocks that can be used to create functional hardware objects/devices
+such as network interfaces, crypto accelerator instances, L2 switches,
+etc.
+
+Required properties:
+
+    - compatible
+        Value type: <string>
+        Definition: Must be "fsl,qoriq-mc".  A Freescale Management Complex
+                    compatible with this binding must have Block Revision
+                    Registers BRR1 and BRR2 at offset 0x0BF8 and 0x0BFC in
+                    the MC control register region.
+
+    - reg
+        Value type: <prop-encoded-array>
+        Definition: A standard property.  Specifies one or two regions
+                    defining the MC's registers:
+
+                       -the first region is the command portal for the
+                        this machine and must always be present
+
+                       -the second region is the MC control registers. This
+                        region may not be present in some scenarios, such
+                        as in the device tree presented to a virtual machine.
+
+Example:
+
+        fsl_mc: fsl-mc at 80c000000 {
+                compatible = "fsl,qoriq-mc";
+                reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal base */
+                      <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
+        };
+
-- 
1.7.9.5

  parent reply	other threads:[~2015-01-24 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 21:12 [RESEND PATCH v7 0/5] ARM64: Add support for FSL's LS2085A SoC Bhupesh Sharma
2015-01-24 21:12 ` [RESEND PATCH v7 1/5] Documentation: DT: Add bindings for FSL NS16550A UART Bhupesh Sharma
2015-01-27 23:06   ` Olof Johansson
2015-01-24 21:12 ` [RESEND PATCH v7 2/5] Documentation: DT: Add entry for FSL LS2085A SoC and Simulator model Bhupesh Sharma
2015-01-27 23:05   ` Olof Johansson
2015-01-24 21:12 ` Bhupesh Sharma [this message]
2015-01-27 23:05   ` [RESEND PATCH v7 3/5] Documentation: DT: Add entry for FSL Management Complex Olof Johansson
2015-01-24 21:12 ` [RESEND PATCH v7 4/5] arm64: Add DTS support for FSL's LS2085A SoC Bhupesh Sharma
2015-01-27 23:08   ` Olof Johansson
2015-01-24 21:12 ` [RESEND PATCH v7 5/5] arm64: Add support for FSL's LS2085A SoC in Kconfig and defconfig Bhupesh Sharma
2015-01-27 23:12   ` Olof Johansson

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=1422133973-16460-4-git-send-email-bhupesh.sharma@freescale.com \
    --to=bhupesh.sharma@freescale.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 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.