| Message ID | 1ac41372c213e96871df1e02cada2e1899f03a7b.1523301400.git.digetx@gmail.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | Memory controller hot reset | expand |
On Mon, Apr 09, 2018 at 10:28:23PM +0300, Dmitry Osipenko wrote: > There are two bindings for the same Memory Controller. One of the bindings > became obsolete long time ago and probably was left unnoticed, remove it > for consistency. > > Signed-off-by: Dmitry Osipenko <digetx@gmail.com> > Reviewed-by: Rob Herring <robh@kernel.org> > --- > .../bindings/arm/tegra/nvidia,tegra30-mc.txt | 18 ------------------ > 1 file changed, 18 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt Applied, thanks. Thierry
diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt deleted file mode 100644 index bdf1a612422b..000000000000 --- a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt +++ /dev/null @@ -1,18 +0,0 @@ -NVIDIA Tegra30 MC(Memory Controller) - -Required properties: -- compatible : "nvidia,tegra30-mc" -- reg : Should contain 4 register ranges(address and length); see the - example below. Note that the MC registers are interleaved with the - SMMU registers, and hence must be represented as multiple ranges. -- interrupts : Should contain MC General interrupt. - -Example: - memory-controller { - compatible = "nvidia,tegra30-mc"; - reg = <0x7000f000 0x010 - 0x7000f03c 0x1b4 - 0x7000f200 0x028 - 0x7000f284 0x17c>; - interrupts = <0 77 0x04>; - };