tjh.dev / kernel
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: Move "sercomm,scpart-id" to partition.yaml

Defining child node properties specific to the parent schema doesn't work
unless all the child node properties are known. They aren't known because
any partition can define its own properties. The solution to this is
typically something like spi-peripheral-props.yaml, but that's overkill for
this single property. Just move it to partition.yaml instead.

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

authored by

Rob Herring (Arm) and committed by
Miquel Raynal ac83f4fa 30f138c0

+9 -10
-10
Documentation/devicetree/bindings/mtd/partitions/fixed-partitions.yaml
··· 33 33 "@[0-9a-f]+$": 34 34 $ref: partition.yaml# 35 35 36 - properties: 37 - sercomm,scpart-id: 38 - description: Partition id in Sercomm partition map. Mtd parser 39 - uses this id to find a record in the partition map containing 40 - offset and size of the current partition. The values from 41 - partition map overrides partition offset and size defined in 42 - reg property of the dts. Frequently these values are the same, 43 - but may differ if device has bad eraseblocks on a flash. 44 - $ref: /schemas/types.yaml#/definitions/uint32 45 - 46 36 required: 47 37 - "#address-cells" 48 38 - "#size-cells"
+9
Documentation/devicetree/bindings/mtd/partitions/partition.yaml
··· 126 126 - xz 127 127 - zstd 128 128 129 + sercomm,scpart-id: 130 + description: Partition id in Sercomm partition map. Mtd parser 131 + uses this id to find a record in the partition map containing 132 + offset and size of the current partition. The values from 133 + partition map overrides partition offset and size defined in 134 + reg property of the dts. Frequently these values are the same, 135 + but may differ if device has bad eraseblocks on a flash. 136 + $ref: /schemas/types.yaml#/definitions/uint32 137 + 129 138 if: 130 139 not: 131 140 required: [ reg ]