linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@0x0f.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, arnd@arndb.de,
	Rob Herring <robh@kernel.org>,
	maz@kernel.org, Daniel Palmer <daniel@0x0f.com>,
	linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
	robh+dt@kernel.org, w@1wt.eu, afaerber@suse.de
Subject: [PATCH v5 07/12] ARM: mstar: Add binding details for mstar,l3bridge
Date: Fri, 10 Jul 2020 18:45:39 +0900	[thread overview]
Message-ID: <20200710094544.430258-8-daniel@0x0f.com> (raw)
In-Reply-To: <20200710094544.430258-1-daniel@0x0f.com>

This adds a YAML description of the l3bridge node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs.

Signed-off-by: Daniel Palmer <daniel@0x0f.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
 .../bindings/misc/mstar,l3bridge.yaml         | 44 +++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/misc/mstar,l3bridge.yaml

diff --git a/Documentation/devicetree/bindings/misc/mstar,l3bridge.yaml b/Documentation/devicetree/bindings/misc/mstar,l3bridge.yaml
new file mode 100644
index 000000000000..cb7fd1cdfb1a
--- /dev/null
+++ b/Documentation/devicetree/bindings/misc/mstar,l3bridge.yaml
@@ -0,0 +1,44 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright 2020 thingy.jp.
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/misc/mstar,l3bridge.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: MStar/SigmaStar Armv7 SoC l3bridge
+
+maintainers:
+  - Daniel Palmer <daniel@thingy.jp>
+
+description: |
+  MStar/SigmaStar's Armv7 SoCs have a pipeline in the interface
+  between the CPU and memory. This means that before DMA capable
+  devices are allowed to run the pipeline must be flushed to ensure
+  everything is in memory.
+
+  The l3bridge region contains registers that allow such a flush
+  to be triggered.
+
+  This node is used by the platform code to find where the registers
+  are and install a barrier that triggers the required pipeline flush.
+
+properties:
+  compatible:
+    items:
+      - const: mstar,l3bridge
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    l3bridge: l3bridge@1f204400 {
+        compatible = "mstar,l3bridge";
+        reg = <0x1f204400 0x200>;
+    };
-- 
2.27.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-07-10  9:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  9:45 [PATCH v5 00/12] Initial MStar/Sigmastar ARMv7 SoC support Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 01/12] dt-bindings: vendor-prefixes: Add mstar vendor prefix Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 02/12] dt-bindings: vendor-prefixes: Add sstar " Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 03/12] dt-bindings: vendor-prefixes: Add 70mai " Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 04/12] dt-bindings: vendor-prefixes: Add thingy.jp prefix Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 05/12] dt-bindings: arm: Add mstar YAML schema Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 06/12] ARM: mstar: Add machine for MStar/Sigmastar Armv7 SoCs Daniel Palmer
2020-07-10  9:45 ` Daniel Palmer [this message]
2020-07-10  9:45 ` [PATCH v5 08/12] ARM: mstar: Add Armv7 base dtsi Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 09/12] ARM: mstar: Add infinity/infinity3 family dtsis Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 10/12] ARM: mstar: Add mercury5 series dtsis Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 11/12] ARM: mstar: Add dts for msc313(e) based BreadBee boards Daniel Palmer
2020-07-10  9:45 ` [PATCH v5 12/12] ARM: mstar: Add dts for 70mai midrive d08 Daniel Palmer
2020-07-24 14:37 ` [PATCH v5 00/12] Initial MStar/Sigmastar ARMv7 SoC support Arnd Bergmann
2020-07-25  4:44   ` Daniel Palmer

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=20200710094544.430258-8-daniel@0x0f.com \
    --to=daniel@0x0f.com \
    --cc=afaerber@suse.de \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=w@1wt.eu \
    /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).