Commit 27bfb201 authored by Rafał Miłecki's avatar Rafał Miłecki Committed by Miquel Raynal
Browse files

dt-bindings: mtd: partitions: add binding for U-Boot bootloader



Right now there is no (known) real reason for a custom binding for
standard U-Boot partitions. Broadcom's U-Boot however requires extra
handling - looking for environment variables subblocks. This commit adds
Broadcom specific binding.

Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
Reviewed-by: default avatarRob Herring <robh@kernel.org>
Signed-off-by: default avatarMiquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220711153041.6036-1-zajec5@gmail.com
parent 568035b0
Loading
Loading
Loading
Loading
+49 −0
Original line number Diff line number Diff line
# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
%YAML 1.2
---
$id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: U-Boot bootloader partition

description: |
  U-Boot is a bootlodaer commonly used in embedded devices. It's almost always
  located on some kind of flash device.

  Device configuration is stored as a set of environment variables that are
  located in a (usually standalone) block of data.

maintainers:
  - Rafał Miłecki <rafal@milecki.pl>

allOf:
  - $ref: partition.yaml#

properties:
  compatible:
    oneOf:
      - const: brcm,u-boot
        description: |
          Broadcom stores environment variables inside a U-Boot partition. They
          can be identified by a custom header with magic value.

unevaluatedProperties: false

examples:
  - |
    partitions {
        compatible = "fixed-partitions";
        #address-cells = <1>;
        #size-cells = <1>;

        partition@0 {
            compatible = "brcm,u-boot";
            reg = <0x0 0x100000>;
            label = "u-boot";
        };

        partition@100000 {
            reg = <0x100000 0x1ff00000>;
            label = "firmware";
        };
    };