| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20200403115238.4cvlz4fxldw7knsh@ubsrv2.baikal.int>
Date: Fri, 3 Apr 2020 14:52:38 +0300
From: Sergey Semin <Sergey.Semin@...kalelectronics.ru>
To: Rob Herring <robh@...nel.org>
CC: Mark Rutland <mark.rutland@....com>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Paul Burton <paulburton@...nel.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
<soc@...nel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/6] dt-bindings: Add Baikal-T1 L2-cache Control Block
dts bindings file
On Thu, Mar 12, 2020 at 04:23:35PM -0500, Rob Herring wrote:
> On Fri, Mar 06, 2020 at 04:07:18PM +0300, Sergey.Semin@...kalelectronics.ru wrote:
> > From: Serge Semin <Sergey.Semin@...kalelectronics.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@...kalelectronics.ru>
> > Signed-off-by: Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>
> > Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
> > Cc: Paul Burton <paulburton@...nel.org>
> > Cc: Ralf Baechle <ralf@...ux-mips.org>
> > Cc: Arnd Bergmann <arnd@...db.de>
> > Cc: Olof Johansson <olof@...om.net>
> > Cc: soc@...nel.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
>
> Dual license
Ok.
>
> > +#
> > +# 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@...il.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
>
> Why is this conditional? Different h/w?
>
Seeing the config register has got a few other CPU parameters to tune
I meant to have both syscon and syscon-less compatible nodes supported
For the same reason there is "allOf" with "syscon.yaml" reference above.
This P5600 CM2 L2-Cach RAM setting is a part of the Baikal-T1 System
Control Module, in particular the register lives someplace amongst Clock
Control Unit and System-specific settings. Seeing the clock and
system-specific parameters are almost always redistributed to a
dedicated registers set, in my first System Control Module DT node design
I was going to split the functionality up into the dedicated sub-nodes.
If there are some mixed parameters declared in the corresponding
registers set, I marked these nodes with additional "syscon". I
thoroughly described that design in RFC: https://lkml.org/lkml/2020/3/22/393
sent To: you.
Seeing there are others indirectly related to the System Controller DT node
design issues I've been addressed in the framework of other patchsets, I
also suggested an alternative design in that RFC text. So should you have
any comments, please send your response right there. I am currently in a bit
of frustration, since noone has sent any comments to the RFC, which stops me
from moving on with fixing the patchsets issues. Though I am pretty sure,
that the alternative design would be better accepted by you and community,
so if no comments pop up in the RFC soon, I'll start implementing it.
The alternative solution "/* System Controller DT Nodes II */" in the
RFC includes having a common "syscon"-compatible node representing the
Baikal-T1 System Controller, while sub-nodes like Clocks Control Units and this
L2-cache RAM control block would import a regmap from that "syscon"
(using a standard syscon_node_to_regmap()-like method). This will solve a
multiple issues raised in others patchsets and the problem you noted here.
Please also note, that following Arnd Bergmann suggestion, I'll move
this driver to the drivers/memory subsystem. So the binding file will be
also moved to Documentation/devicetree/bindings/memory-controllers.
Similarly the ehb-drivers and bindings will be moved to the drivers/bus
and Documentation/devicetree/bindings/bus/ directories respectively.
> > +
> > + reg:
> > + description: MMIO register with MIPS P5600 CM2 L2-cache RAM settings.
>
> You can drop this.
Ok.
>
> > + 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
>
> These should be at the same level as 'default' or default moved here (I
> prefer the former). IOW, only $ref has to be under 'allOf'.
Ok.
>
> > +
> > + 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@...4D028 {
>
> lowercase hex.
Ok. I'll do this to the next example case as well.
Regards,
-Sergey
>
> > + 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@...4D028 {
> > + 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
> >
Powered by blists - more mailing lists