samsung,sysmmu.txt 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. Samsung Exynos IOMMU H/W, System MMU (System Memory Management Unit)
  2. Samsung's Exynos architecture contains System MMUs that enables scattered
  3. physical memory chunks visible as a contiguous region to DMA-capable peripheral
  4. devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth.
  5. System MMU is an IOMMU and supports identical translation table format to
  6. ARMv7 translation tables with minimum set of page properties including access
  7. permissions, shareability and security protection. In addition, System MMU has
  8. another capabilities like L2 TLB or block-fetch buffers to minimize translation
  9. latency.
  10. System MMUs are in many to one relation with peripheral devices, i.e. single
  11. peripheral device might have multiple System MMUs (usually one for each bus
  12. master), but one System MMU can handle transactions from only one peripheral
  13. device. The relation between a System MMU and the peripheral device needs to be
  14. defined in device node of the peripheral device.
  15. MFC in all Exynos SoCs and FIMD, M2M Scalers and G2D in Exynos5420 has 2 System
  16. MMUs.
  17. * MFC has one System MMU on its left and right bus.
  18. * FIMD in Exynos5420 has one System MMU for window 0 and 4, the other system MMU
  19. for window 1, 2 and 3.
  20. * M2M Scalers and G2D in Exynos5420 has one System MMU on the read channel and
  21. the other System MMU on the write channel.
  22. The drivers must consider how to handle those System MMUs. One of the idea is
  23. to implement child devices or sub-devices which are the client devices of the
  24. System MMU.
  25. Note:
  26. The current DT binding for the Exynos System MMU is incomplete.
  27. The following properties can be removed or changed, if found incompatible with
  28. the "Generic IOMMU Binding" support for attaching devices to the IOMMU.
  29. Required properties:
  30. - compatible: Should be "samsung,exynos-sysmmu"
  31. - reg: A tuple of base address and size of System MMU registers.
  32. - interrupt-parent: The phandle of the interrupt controller of System MMU
  33. - interrupts: An interrupt specifier for interrupt signal of System MMU,
  34. according to the format defined by a particular interrupt
  35. controller.
  36. - clock-names: Should be "sysmmu" if the System MMU is needed to gate its clock.
  37. Optional "master" if the clock to the System MMU is gated by
  38. another gate clock other than "sysmmu".
  39. Exynos4 SoCs, there needs no "master" clock.
  40. Exynos5 SoCs, some System MMUs must have "master" clocks.
  41. - clocks: Required if the System MMU is needed to gate its clock.
  42. - power-domains: Required if the System MMU is needed to gate its power.
  43. Please refer to the following document:
  44. Documentation/devicetree/bindings/power/pd-samsung.txt
  45. Examples:
  46. gsc_0: gsc@13e00000 {
  47. compatible = "samsung,exynos5-gsc";
  48. reg = <0x13e00000 0x1000>;
  49. interrupts = <0 85 0>;
  50. power-domains = <&pd_gsc>;
  51. clocks = <&clock CLK_GSCL0>;
  52. clock-names = "gscl";
  53. };
  54. sysmmu_gsc0: sysmmu@13E80000 {
  55. compatible = "samsung,exynos-sysmmu";
  56. reg = <0x13E80000 0x1000>;
  57. interrupt-parent = <&combiner>;
  58. interrupts = <2 0>;
  59. clock-names = "sysmmu", "master";
  60. clocks = <&clock CLK_SMMU_GSCL0>, <&clock CLK_GSCL0>;
  61. power-domains = <&pd_gsc>;
  62. };