Revert "dm crypt: export sysfs of kcryptd workqueue"

[linux-2.6-microblaze.git] / Documentation / devicetree / bindings / memory-controllers / mediatek,smi-common.txt

diff --git a/Documentation/devicetree/bindings/memory-controllers/mediatek,smi-common.txt b/Documentation/devicetree/bindings/memory-controllers/mediatek,smi-common.txt
index b645736..dbafffe 100644 (file)
--- a/Documentation/devicetree/bindings/memory-controllers/mediatek,smi-common.txt
+++ b/Documentation/devicetree/bindings/memory-controllers/mediatek,smi-common.txt
@@ -5,7 +5,7 @@ The hardware block diagram please check bindings/iommu/mediatek,iommu.txt
 Mediatek SMI have two generations of HW architecture, here is the list
 which generation the SoCs use:
 generation 1: mt2701 and mt7623.
 Mediatek SMI have two generations of HW architecture, here is the list
 which generation the SoCs use:
 generation 1: mt2701 and mt7623.

-generation 2: mt2712, mt6779, mt8173 and mt8183.
+generation 2: mt2712, mt6779, mt8167, mt8173 and mt8183.

 
 There's slight differences between the two SMI, for generation 2, the
 register which control the iommu port is at each larb's register base. But
 
 There's slight differences between the two SMI, for generation 2, the
 register which control the iommu port is at each larb's register base. But


@@ -20,6 +20,7 @@ Required properties:
        "mediatek,mt2712-smi-common"
        "mediatek,mt6779-smi-common"
        "mediatek,mt7623-smi-common", "mediatek,mt2701-smi-common"
        "mediatek,mt2712-smi-common"
        "mediatek,mt6779-smi-common"
        "mediatek,mt7623-smi-common", "mediatek,mt2701-smi-common"

+       "mediatek,mt8167-smi-common"

        "mediatek,mt8173-smi-common"
        "mediatek,mt8183-smi-common"
 - reg : the register and size of the SMI block.
        "mediatek,mt8173-smi-common"
        "mediatek,mt8183-smi-common"
 - reg : the register and size of the SMI block.