Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/mips/mti,mips-cm.yaml- Extension
.yaml- Size
- 1641 bytes
- Lines
- 58
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/mips/mti,mips-cm.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: MIPS Coherence Manager
description:
The Coherence Manager (CM) is responsible for establishing the
global ordering of requests from all elements of the system and
sending the correct data back to the requester. It supports Cache
to Cache transfers.
https://training.mips.com/cps_mips/PDF/CPS_Introduction.pdf
https://training.mips.com/cps_mips/PDF/Coherency_Manager.pdf
maintainers:
- Jiaxun Yang <jiaxun.yang@flygoat.com>
properties:
compatible:
oneOf:
- const: mti,mips-cm
- const: mobileye,eyeq6-cm
description:
On EyeQ6 the HCI (Hardware Cache Initialization) information for
the L2 cache in multi-cluster configuration is broken.
reg:
description:
Base address and size of the Global Configuration Registers
referred to as CMGCR.They are the system programmer's interface
to the Coherency Manager. Their location in the memory map is
determined at core build time. In a functional system, the base
address is provided by the Coprocessor 0, but some
System-on-Chip (SoC) designs may not provide an accurate address
that needs to be described statically.
maxItems: 1
required:
- compatible
additionalProperties: false
examples:
- |
coherency-manager@1fbf8000 {
compatible = "mti,mips-cm";
reg = <0x1bde8000 0x8000>;
};
- |
coherency-manager {
compatible = "mobileye,eyeq6-cm";
};
...
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.