xref: /freebsd/sys/contrib/device-tree/Bindings/mips/mti,mips-cm.yaml (revision 8ccc0d235c226d84112561d453c49904398d085c)
1*8ccc0d23SEmmanuel Vadot# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2*8ccc0d23SEmmanuel Vadot%YAML 1.2
3*8ccc0d23SEmmanuel Vadot---
4*8ccc0d23SEmmanuel Vadot$id: http://devicetree.org/schemas/mips/mti,mips-cm.yaml#
5*8ccc0d23SEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml#
6*8ccc0d23SEmmanuel Vadot
7*8ccc0d23SEmmanuel Vadottitle: MIPS Coherence Manager
8*8ccc0d23SEmmanuel Vadot
9*8ccc0d23SEmmanuel Vadotdescription:
10*8ccc0d23SEmmanuel Vadot  The Coherence Manager (CM) is responsible for establishing the
11*8ccc0d23SEmmanuel Vadot  global ordering of requests from all elements of the system and
12*8ccc0d23SEmmanuel Vadot  sending the correct data back to the requester. It supports Cache
13*8ccc0d23SEmmanuel Vadot  to Cache transfers.
14*8ccc0d23SEmmanuel Vadot  https://training.mips.com/cps_mips/PDF/CPS_Introduction.pdf
15*8ccc0d23SEmmanuel Vadot  https://training.mips.com/cps_mips/PDF/Coherency_Manager.pdf
16*8ccc0d23SEmmanuel Vadot
17*8ccc0d23SEmmanuel Vadotmaintainers:
18*8ccc0d23SEmmanuel Vadot  - Jiaxun Yang <jiaxun.yang@flygoat.com>
19*8ccc0d23SEmmanuel Vadot
20*8ccc0d23SEmmanuel Vadotproperties:
21*8ccc0d23SEmmanuel Vadot  compatible:
22*8ccc0d23SEmmanuel Vadot    oneOf:
23*8ccc0d23SEmmanuel Vadot      - const: mti,mips-cm
24*8ccc0d23SEmmanuel Vadot      - const: mobileye,eyeq6-cm
25*8ccc0d23SEmmanuel Vadot        description:
26*8ccc0d23SEmmanuel Vadot          On EyeQ6 the HCI (Hardware Cache Initialization) information for
27*8ccc0d23SEmmanuel Vadot          the L2 cache in multi-cluster configuration is broken.
28*8ccc0d23SEmmanuel Vadot
29*8ccc0d23SEmmanuel Vadot  reg:
30*8ccc0d23SEmmanuel Vadot    description:
31*8ccc0d23SEmmanuel Vadot      Base address and size of the Global Configuration Registers
32*8ccc0d23SEmmanuel Vadot      referred to as CMGCR.They are the system programmer's interface
33*8ccc0d23SEmmanuel Vadot      to the Coherency Manager. Their location in the memory map is
34*8ccc0d23SEmmanuel Vadot      determined at core build time. In a functional system, the base
35*8ccc0d23SEmmanuel Vadot      address is provided by the Coprocessor 0, but some
36*8ccc0d23SEmmanuel Vadot      System-on-Chip (SoC) designs may not provide an accurate address
37*8ccc0d23SEmmanuel Vadot      that needs to be described statically.
38*8ccc0d23SEmmanuel Vadot
39*8ccc0d23SEmmanuel Vadot    maxItems: 1
40*8ccc0d23SEmmanuel Vadot
41*8ccc0d23SEmmanuel Vadotrequired:
42*8ccc0d23SEmmanuel Vadot  - compatible
43*8ccc0d23SEmmanuel Vadot
44*8ccc0d23SEmmanuel VadotadditionalProperties: false
45*8ccc0d23SEmmanuel Vadot
46*8ccc0d23SEmmanuel Vadotexamples:
47*8ccc0d23SEmmanuel Vadot  - |
48*8ccc0d23SEmmanuel Vadot    coherency-manager@1fbf8000 {
49*8ccc0d23SEmmanuel Vadot      compatible = "mti,mips-cm";
50*8ccc0d23SEmmanuel Vadot      reg = <0x1bde8000 0x8000>;
51*8ccc0d23SEmmanuel Vadot    };
52*8ccc0d23SEmmanuel Vadot
53*8ccc0d23SEmmanuel Vadot  - |
54*8ccc0d23SEmmanuel Vadot    coherency-manager {
55*8ccc0d23SEmmanuel Vadot      compatible = "mobileye,eyeq6-cm";
56*8ccc0d23SEmmanuel Vadot    };
57*8ccc0d23SEmmanuel Vadot...
58