tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

dt-bindings: mips: Document mti,mips-cm

Add device tree binding documentation for MIPS Coherence Manager. This
component enables support for SMP by providing each processor in the
system with a uniform view of memory. The Coherence Manager is
responsible for establishing the global ordering of requests from all
elements of the system and sending the correct data back to the
requester.

Based on the work of Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

authored by

Gregory CLEMENT and committed by
Thomas Bogendoerfer 21ebe64a 2398902f

+47
+47
Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
··· 1 + # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2 + %YAML 1.2 3 + --- 4 + $id: http://devicetree.org/schemas/mips/mti,mips-cm.yaml# 5 + $schema: http://devicetree.org/meta-schemas/core.yaml# 6 + 7 + title: MIPS Coherence Manager 8 + 9 + description: 10 + The Coherence Manager (CM) is responsible for establishing the 11 + global ordering of requests from all elements of the system and 12 + sending the correct data back to the requester. It supports Cache 13 + to Cache transfers. 14 + https://training.mips.com/cps_mips/PDF/CPS_Introduction.pdf 15 + https://training.mips.com/cps_mips/PDF/Coherency_Manager.pdf 16 + 17 + maintainers: 18 + - Jiaxun Yang <jiaxun.yang@flygoat.com> 19 + 20 + properties: 21 + compatible: 22 + const: mti,mips-cm 23 + 24 + reg: 25 + description: 26 + Base address and size of the Global Configuration Registers 27 + referred to as CMGCR.They are the system programmer's interface 28 + to the Coherency Manager. Their location in the memory map is 29 + determined at core build time. In a functional system, the base 30 + address is provided by the Coprocessor 0, but some 31 + System-on-Chip (SoC) designs may not provide an accurate address 32 + that needs to be described statically. 33 + 34 + maxItems: 1 35 + 36 + required: 37 + - compatible 38 + 39 + additionalProperties: false 40 + 41 + examples: 42 + - | 43 + coherency-manager@1fbf8000 { 44 + compatible = "mti,mips-cm"; 45 + reg = <0x1bde8000 0x8000>; 46 + }; 47 + ...