blackbird-op-linux/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.txt, branch master

dt-bindings: memory: tegra30: Convert to Tegra124 YAML

2019-10-29T19:22:34+00:00

The Tegra30 binding will actually differ from the Tegra124 a tad, in particular the EMEM configuration description. Hence rename the binding to Tegra124 during of the conversion to YAML. Reviewed-by: Rob Herring Signed-off-by: Dmitry Osipenko Reviewed-by: Rob Herring Signed-off-by: Thierry Reding

dt-bindings: memory: tegra: Document #reset-cells property of the Tegra30 MC

2018-04-27T09:14:12+00:00

Memory Controller has a memory client "hot reset" functionality, which resets the DMA interface of a memory client. So MC is a reset controller in addition to IOMMU. Signed-off-by: Dmitry Osipenko Reviewed-by: Rob Herring Signed-off-by: Thierry Reding

dt-bindings: memory: Add Tegra186 support

2017-12-13T11:53:43+00:00

As opposed to earlier incarnations, the memory controller on Tegra186 no longer implements an SMMU. Instead the SMMU is a regular ARM SMMU and in a separate IP block. However, the memory controller programs the SMMU stream IDs for each of the memory clients. Add a header file with definitions for each of these stream IDs and mark the #iommu-cells property as required on Tegra30 to Tegra210 in the device tree bindings. Signed-off-by: Thierry Reding

dt-bindings: tegra: Rename some bindings for consistency

2016-04-19T22:25:19+00:00

Device tree binding for NVIDIA Tegra have traditionally carried the "nvidia," vendor prefix in the filename. A couple of odd ones don't, so fix them up for consistency. Also rename existing bindings to reflect the first compatible value that they document. This wasn't done consistently either. Acked-by: Stephen Warren Signed-off-by: Thierry Reding Signed-off-by: Rob Herring