mti,mips-cm.yaml 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  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. title: MIPS Coherence Manager
  7. description:
  8. The Coherence Manager (CM) is responsible for establishing the
  9. global ordering of requests from all elements of the system and
  10. sending the correct data back to the requester. It supports Cache
  11. to Cache transfers.
  12. https://training.mips.com/cps_mips/PDF/CPS_Introduction.pdf
  13. https://training.mips.com/cps_mips/PDF/Coherency_Manager.pdf
  14. maintainers:
  15. - Jiaxun Yang <jiaxun.yang@flygoat.com>
  16. properties:
  17. compatible:
  18. oneOf:
  19. - const: mti,mips-cm
  20. - const: mobileye,eyeq6-cm
  21. description:
  22. On EyeQ6 the HCI (Hardware Cache Initialization) information for
  23. the L2 cache in multi-cluster configuration is broken.
  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. maxItems: 1
  34. required:
  35. - compatible
  36. additionalProperties: false
  37. examples:
  38. - |
  39. coherency-manager@1fbf8000 {
  40. compatible = "mti,mips-cm";
  41. reg = <0x1bde8000 0x8000>;
  42. };
  43. - |
  44. coherency-manager {
  45. compatible = "mobileye,eyeq6-cm";
  46. };
  47. ...