From: <Sergey.Semin@baikalelectronics.ru>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Serge Semin <fancer.lancer@gmail.com>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Burton <paulburton@kernel.org>,
Ralf Baechle <ralf@linux-mips.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>, <soc@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/6] dt-bindings: Add Baikal-T1 L2-cache Control Block dts bindings file
Date: Fri, 6 Mar 2020 16:07:18 +0300 [thread overview]
Message-ID: <20200306130734.194288030794@mail.baikalelectronics.ru> (raw)
In-Reply-To: <20200306130721.10347-1-Sergey.Semin@baikalelectronics.ru>
From: Serge Semin <Sergey.Semin@baikalelectronics.ru>
There is a single register provided by the SoC system controller,
which can be used to tune the L2-cache up. It only provides a way
to change the L2-RAM access latencies. So aside from the MMIO region
with that setting and "be,bt1-l2-ctl" compatible string the device
node can be optionally equipped with the properties of Tag/Data/WS
latencies.
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Signed-off-by: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>
Cc: soc@kernel.org
---
.../bindings/soc/baikal-t1/be,bt1-l2-ctl.yaml | 108 ++++++++++++++++++
1 file changed, 108 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/baikal-t1/be,bt1-l2-ctl.yaml
diff --git a/Documentation/devicetree/bindings/soc/baikal-t1/be,bt1-l2-ctl.yaml b/Documentation/devicetree/bindings/soc/baikal-t1/be,bt1-l2-ctl.yaml
new file mode 100644
index 000000000000..8769b3fa517c
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/baikal-t1/be,bt1-l2-ctl.yaml
@@ -0,0 +1,108 @@
+# SPDX-License-Identifier: GPL-2.0
+#
+# Copyright (C) 2020 BAIKAL ELECTRONICS, JSC
+#
+# Baikal-T1 L2-cache Control Block Device Tree Bindings.
+#
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/soc/baikal-t1/be,bt1-l2-ctl.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Baikal-T1 L2-cache Control Block
+
+maintainers:
+ - Serge Semin <fancer.lancer@gmail.com>
+
+description: |
+ Baikal-T1 exposes a few settings to tune the MIPS P5600 CM2 L2-cache
+ performance up. In particular it's possible to change the Tag, Data and
+ Way-select RAM access latencies. This bindings file describes the system
+ controller block, which provides an interface to set the tuning up.
+
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: syscon
+ then:
+ $ref: ../../mfd/syscon.yaml#
+ else:
+ properties:
+ reg-io-width: false
+
+ little-endian: false
+
+properties:
+ compatible:
+ oneOf:
+ - description: P5600 CM2 L2-cache RAM external configuration block.
+ const: be,bt1-l2-ctl
+ - description: P5600 CM2 L2-cache RAM system controller block.
+ items:
+ - const: be,bt1-l2-ctl
+ - const: syscon
+
+ reg:
+ description: MMIO register with MIPS P5600 CM2 L2-cache RAM settings.
+ maxItems: 1
+
+ be,l2-ws-latency:
+ description: Cycles of latency for Way-select RAM accesses.
+ default: 0
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/uint32
+ - minimum: 0
+ maximum: 3
+
+ be,l2-tag-latency:
+ description: Cycles of latency for Tag RAM accesses.
+ default: 0
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/uint32
+ - minimum: 0
+ maximum: 3
+
+ be,l2-data-latency:
+ description: Cycles of latency for Data RAM accesses.
+ default: 1
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/uint32
+ - minimum: 0
+ maximum: 3
+
+ reg-io-width:
+ const: 4
+
+ little-endian: true
+
+additionalProperties: false
+
+required:
+ - compatible
+ - reg
+
+examples:
+ - |
+ l2_ctl1: l2@1F04D028 {
+ compatible = "be,bt1-l2-ctl";
+ reg = <0x1F04D028 0x004>;
+
+ be,l2-ws-latency = <0>;
+ be,l2-tag-latency = <0>;
+ be,l2-data-latency = <1>;
+ };
+ - |
+ l2_ctl2: l2@1F04D028 {
+ compatible = "be,bt1-l2-ctl", "syscon";
+ reg = <0x1F04D028 0x004>;
+
+ be,l2-ws-latency = <0>;
+ be,l2-tag-latency = <0>;
+ be,l2-data-latency = <1>;
+
+ little-endian;
+ reg-io-width = <4>;
+ };
+...
--
2.25.1
next prev parent reply other threads:[~2020-03-06 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200306130721.10347-1-Sergey.Semin@baikalelectronics.ru>
2020-03-06 13:07 ` [PATCH 1/6] dt-bindings: Add Baikal-T1 AXI-bus EHB dts bindings file Sergey.Semin
2020-03-06 13:07 ` [PATCH 2/6] dt-bindings: Add Baikal-T1 APB-bus " Sergey.Semin
2020-03-09 18:07 ` Rob Herring
2020-03-06 13:07 ` Sergey.Semin [this message]
2020-03-12 21:23 ` [PATCH 3/6] dt-bindings: Add Baikal-T1 L2-cache Control Block " Rob Herring
2020-04-03 11:52 ` Sergey Semin
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=20200306130734.194288030794@mail.baikalelectronics.ru \
--to=sergey.semin@baikalelectronics.ru \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).