Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

dt-bindings: mtd: Remove useless file about partitions

There is already a real partitions.yaml file, so assuming everybody
knows hot to read yaml schema now, this text file is no longer needed,
so drop it.

Depending on the situation, the lines referring to this file are either
dropped or edited to point to mtd.yaml which includes partition{,s}.yaml.

Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/linux-mtd/20221114090315.848208-3-miquel.raynal@bootlin.com

+6 -42
+2 -4
Documentation/devicetree/bindings/mtd/atmel-nand.txt
··· 45 45 - atmel,rb: an integer identifying the native Ready/Busy pin. Only meaningful 46 46 on sama5 SoCs. 47 47 48 - All generic properties described in 49 - Documentation/devicetree/bindings/mtd/{common,nand}.txt also apply to the NAND 50 - device node, and NAND partitions should be defined under the NAND node as 51 - described in Documentation/devicetree/bindings/mtd/partition.txt. 48 + All generic properties are described in the generic yaml files under 49 + Documentation/devicetree/bindings/mtd/. 52 50 53 51 * ECC engine (PMECC) bindings: 54 52
-1
Documentation/devicetree/bindings/mtd/ingenic,nand.yaml
··· 34 34 type: object 35 35 description: 36 36 Node containing description of fixed partitions. 37 - See Documentation/devicetree/bindings/mtd/partition.txt 38 37 39 38 patternProperties: 40 39 "^nand@[a-f0-9]$":
+1 -1
Documentation/devicetree/bindings/mtd/lpc32xx-mlc.txt
··· 19 19 - nxp,wr_low: WR_LOW 20 20 21 21 Optional subnodes: 22 - - Partitions, see Documentation/devicetree/bindings/mtd/partition.txt 22 + - Partitions, see Documentation/devicetree/bindings/mtd/mtd.yaml 23 23 24 24 Example: 25 25
+1 -1
Documentation/devicetree/bindings/mtd/lpc32xx-slc.txt
··· 20 20 - nxp,rsetup: Read setup time (R_SETUP) 21 21 22 22 Optional subnodes: 23 - - Partitions, see Documentation/devicetree/bindings/mtd/partition.txt 23 + - Partitions, see Documentation/devicetree/bindings/mtd/mtd.yaml 24 24 25 25 Example: 26 26
+1 -1
Documentation/devicetree/bindings/mtd/mtk-nand.txt
··· 131 131 }; 132 132 133 133 NAND chip optional subnodes: 134 - - Partitions, see Documentation/devicetree/bindings/mtd/partition.txt 134 + - Partitions, see Documentation/devicetree/bindings/mtd/mtd.yaml 135 135 136 136 Example: 137 137 nand@0 {
-33
Documentation/devicetree/bindings/mtd/partition.txt
··· 1 - Flash partitions in device tree 2 - =============================== 3 - 4 - Flash devices can be partitioned into one or more functional ranges (e.g. "boot 5 - code", "nvram", "kernel"). 6 - 7 - Different devices may be partitioned in a different ways. Some may use a fixed 8 - flash layout set at production time. Some may use on-flash table that describes 9 - the geometry and naming/purpose of each functional region. It is also possible 10 - to see these methods mixed. 11 - 12 - To assist system software in locating partitions, we allow describing which 13 - method is used for a given flash device. To describe the method there should be 14 - a subnode of the flash device that is named 'partitions'. It must have a 15 - 'compatible' property, which is used to identify the method to use. 16 - 17 - When a single partition is represented with a DT node (it depends on a used 18 - format) it may also be described using above rules ('compatible' and optionally 19 - some extra properties / subnodes). It allows describing more complex, 20 - hierarchical (multi-level) layouts and should be used if there is some 21 - significant relation between partitions or some partition internally uses 22 - another partitioning method. 23 - 24 - Available bindings are listed in the "partitions" subdirectory. 25 - 26 - 27 - Deprecated: partitions defined in flash node 28 - ============================================ 29 - 30 - For backwards compatibility partitions as direct subnodes of the flash device are 31 - supported. This use is discouraged. 32 - NOTE: also for backwards compatibility, direct subnodes that have a compatible 33 - string are not considered partitions, as they may be used for other bindings.
+1 -1
drivers/mtd/parsers/Kconfig
··· 75 75 This provides a open firmware device tree partition parser 76 76 which derives the partition map from the children of the 77 77 flash memory node, as described in 78 - Documentation/devicetree/bindings/mtd/partition.txt. 78 + Documentation/devicetree/bindings/mtd/mtd.yaml. 79 79 80 80 config MTD_OF_PARTS_BCM4908 81 81 bool "BCM4908 partitioning support"