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

Configure Feed

Select the types of activity you want to include in your feed.

dt-bindings: mtd: partitions: Combine simple partition bindings

Several partition node bindings are just a compatible plus properties
defined in partition.yaml. Move all of these bindings to a single schema
file.

Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

authored by

Rob Herring (Arm) and committed by
Miquel Raynal
125981ff a1fa0f8c

+62 -152
-53
Documentation/devicetree/bindings/mtd/partitions/binman.yaml
··· 1 - # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 2 - %YAML 1.2 3 - --- 4 - $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml# 5 - $schema: http://devicetree.org/meta-schemas/core.yaml# 6 - 7 - title: Binman entries 8 - 9 - description: | 10 - This corresponds to a binman 'entry'. It is a single partition which holds 11 - data of a defined type. 12 - 13 - Binman uses the type to indicate what data file / type to place in the 14 - partition. There are quite a number of binman-specific entry types, such as 15 - section, fill and files, to be added later. 16 - 17 - maintainers: 18 - - Simon Glass <sjg@chromium.org> 19 - 20 - allOf: 21 - - $ref: /schemas/mtd/partitions/partition.yaml# 22 - 23 - properties: 24 - compatible: 25 - enum: 26 - - u-boot # u-boot.bin from U-Boot project 27 - - tfa-bl31 # bl31.bin or bl31.elf from TF-A project 28 - 29 - required: 30 - - compatible 31 - 32 - unevaluatedProperties: false 33 - 34 - examples: 35 - - | 36 - partitions { 37 - compatible = "fixed-partitions"; 38 - #address-cells = <1>; 39 - #size-cells = <1>; 40 - 41 - partition@100000 { 42 - compatible = "u-boot"; 43 - reg = <0x100000 0xf00000>; 44 - align-size = <0x1000>; 45 - align-end = <0x10000>; 46 - }; 47 - 48 - partition@200000 { 49 - compatible = "tfa-bl31"; 50 - reg = <0x200000 0x100000>; 51 - align = <0x4000>; 52 - }; 53 - };
+1 -5
Documentation/devicetree/bindings/mtd/partitions/brcm,bcm4908-partitions.yaml
··· 29 29 30 30 patternProperties: 31 31 "^partition@[0-9a-f]+$": 32 - $ref: partition.yaml# 33 - properties: 34 - compatible: 35 - const: brcm,bcm4908-firmware 36 - unevaluatedProperties: false 32 + $ref: partition.yaml#/$defs/partition-node 37 33 38 34 required: 39 35 - "#address-cells"
-45
Documentation/devicetree/bindings/mtd/partitions/brcm,bcm963xx-imagetag.txt
··· 1 - Broadcom BCM963XX ImageTag Partition Container 2 - ============================================== 3 - 4 - Some Broadcom BCM63XX SoC based devices contain additional, non discoverable 5 - partitions or non standard bootloader partition sizes. For these a mixed layout 6 - needs to be used with an explicit firmware partition. 7 - 8 - The BCM963XX ImageTag is a simple firmware header describing the offsets and 9 - sizes of the rootfs and kernel parts contained in the firmware. 10 - 11 - Required properties: 12 - - compatible : must be "brcm,bcm963xx-imagetag" 13 - 14 - Example: 15 - 16 - flash@1e000000 { 17 - compatible = "cfi-flash"; 18 - reg = <0x1e000000 0x2000000>; 19 - bank-width = <2>; 20 - 21 - partitions { 22 - compatible = "fixed-partitions"; 23 - #address-cells = <1>; 24 - #size-cells = <1>; 25 - 26 - cfe@0 { 27 - reg = <0x0 0x10000>; 28 - read-only; 29 - }; 30 - 31 - firmware@10000 { 32 - reg = <0x10000 0x7d0000>; 33 - compatible = "brcm,bcm963xx-imagetag"; 34 - }; 35 - 36 - caldata@7e0000 { 37 - reg = <0x7e0000 0x10000>; 38 - read-only; 39 - }; 40 - 41 - nvram@7f0000 { 42 - reg = <0x7f0000 0x10000>; 43 - }; 44 - }; 45 - };
-44
Documentation/devicetree/bindings/mtd/partitions/seama.yaml
··· 1 - # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2 - %YAML 1.2 3 - --- 4 - $id: http://devicetree.org/schemas/mtd/partitions/seama.yaml# 5 - $schema: http://devicetree.org/meta-schemas/core.yaml# 6 - 7 - title: Seattle Image Partitions 8 - 9 - description: The SEAttle iMAge (SEAMA) partition is a type of partition 10 - used for NAND flash devices. This type of flash image is found in some 11 - D-Link routers such as DIR-645, DIR-842, DIR-859, DIR-860L, DIR-885L, 12 - DIR890L and DCH-M225, as well as in WD and NEC routers on the ath79 13 - (MIPS), Broadcom BCM53xx, and RAMIPS platforms. This partition type 14 - does not have children defined in the device tree, they need to be 15 - detected by software. 16 - 17 - allOf: 18 - - $ref: partition.yaml# 19 - 20 - maintainers: 21 - - Linus Walleij <linus.walleij@linaro.org> 22 - 23 - properties: 24 - compatible: 25 - const: seama 26 - 27 - required: 28 - - compatible 29 - 30 - unevaluatedProperties: false 31 - 32 - examples: 33 - - | 34 - partitions { 35 - compatible = "fixed-partitions"; 36 - #address-cells = <1>; 37 - #size-cells = <1>; 38 - 39 - partition@0 { 40 - compatible = "seama"; 41 - reg = <0x0 0x800000>; 42 - label = "firmware"; 43 - }; 44 - };
+61
Documentation/devicetree/bindings/mtd/partitions/simple-partition.yaml
··· 1 + # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 2 + %YAML 1.2 3 + --- 4 + $id: http://devicetree.org/schemas/mtd/partitions/simple-partition.yaml# 5 + $schema: http://devicetree.org/meta-schemas/core.yaml# 6 + 7 + title: Simple partition types 8 + 9 + description: 10 + Simple partition types which only define a "compatible" value and no custom 11 + properties. 12 + 13 + maintainers: 14 + - Rafał Miłecki <rafal@milecki.pl> 15 + - Simon Glass <sjg@chromium.org> 16 + 17 + allOf: 18 + - $ref: partition.yaml# 19 + 20 + properties: 21 + compatible: 22 + oneOf: 23 + - const: brcm,bcm4908-firmware 24 + description: 25 + Broadcom BCM4908 CFE bootloader firmware partition 26 + 27 + - const: brcm,bcm963xx-imagetag 28 + description: 29 + The BCM963XX ImageTag is a simple firmware header describing the 30 + offsets and sizes of the rootfs and kernel parts contained in the 31 + firmware. 32 + 33 + - const: seama 34 + description: 35 + The SEAttle iMAge (SEAMA) partition is a type of partition used for 36 + NAND flash devices. This type of flash image is found in some D-Link 37 + routers such as DIR-645, DIR-842, DIR-859, DIR-860L, DIR-885L, DIR890L 38 + and DCH-M225, as well as in WD and NEC routers on the ath79 (MIPS), 39 + Broadcom BCM53xx, and RAMIPS platforms. This partition type does not 40 + have children defined in the device tree, they need to be detected by 41 + software. 42 + 43 + - const: u-boot 44 + description: > 45 + u-boot.bin from U-Boot project. 46 + 47 + This corresponds to a binman 'entry'. It is a single partition which holds 48 + data of a defined type. 49 + 50 + Binman uses the type to indicate what data file / type to place in the 51 + partition. There are quite a number of binman-specific entry types, such as 52 + section, fill and files, to be added later. 53 + 54 + - const: tfa-bl31 55 + description: > 56 + bl31.bin or bl31.elf from TF-A project 57 + 58 + This corresponds to a binman 'entry'. It is a single partition which holds 59 + data of a defined type. 60 + 61 + unevaluatedProperties: false
-5
MAINTAINERS
··· 4403 4403 F: fs/bfs/ 4404 4404 F: include/uapi/linux/bfs_fs.h 4405 4405 4406 - BINMAN 4407 - M: Simon Glass <sjg@chromium.org> 4408 - S: Supported 4409 - F: Documentation/devicetree/bindings/mtd/partitions/binman* 4410 - 4411 4406 BITMAP API 4412 4407 M: Yury Norov <yury.norov@gmail.com> 4413 4408 R: Rasmus Villemoes <linux@rasmusvillemoes.dk>