From: Rob Herring <robh@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Michael Walle" <mwalle@kernel.org>,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Tom Rini" <trini@konsulko.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dhruva Gole" <d-gole@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: mtd: partitions: Add binman compatible
Date: Tue, 24 Oct 2023 10:57:28 -0500 [thread overview]
Message-ID: <20231024155728.GA3707756-robh@kernel.org> (raw)
In-Reply-To: <20231009220436.2164245-1-sjg@chromium.org>
On Mon, Oct 09, 2023 at 04:04:13PM -0600, Simon Glass wrote:
> Add a compatible string for binman, so we can extend fixed-partitions
> in various ways.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v4:
> - Change subject line
>
> Changes in v3:
> - Drop fixed-partition additional compatible string
> - Drop fixed-partitions from the example
> - Mention use of compatible instead of label
>
> Changes in v2:
> - Drop mention of 'enhanced features' in fixed-partitions.yaml
> - Mention Binman input and output properties
> - Use plain partition@xxx for the node name
>
> .../bindings/mtd/partitions/binman.yaml | 63 +++++++++++++++++++
> .../bindings/mtd/partitions/partitions.yaml | 1 +
> MAINTAINERS | 5 ++
> 3 files changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/partitions/binman.yaml
>
> diff --git a/Documentation/devicetree/bindings/mtd/partitions/binman.yaml b/Documentation/devicetree/bindings/mtd/partitions/binman.yaml
> new file mode 100644
> index 000000000000..7d6c8bd738f5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/partitions/binman.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2023 Google LLC
> +
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mtd/partitions/binman.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Binman firmware layout
> +
> +maintainers:
> + - Simon Glass <sjg@chromium.org>
> +
> +select: false
> +
> +description: |
> + The binman node provides a layout for firmware, used when packaging firmware
> + from multiple projects. It is based on fixed-partitions, with some
> + extensions, but uses 'compatible' to indicate the contents of the node, to
> + avoid perturbing or confusing existing installations which use 'label' for a
> + particular purpose.
> +
> + Binman supports properties used as inputs to the firmware-packaging process,
> + such as those which control alignment of partitions. This binding addresses
> + these 'input' properties. For example, it is common for the 'reg' property
> + (an 'output' property) to be set by Binman, based on the alignment requested
> + in the input.
> +
> + Once processing is complete, input properties have mostly served their
> + purpose, at least until the firmware is repacked later, e.g. due to a
> + firmware update. The 'fixed-partitions' binding should provide enough
> + information to read the firmware at runtime, including decompression if
> + needed.
> +
> + Documentation for Binman is available at:
> +
> + https://u-boot.readthedocs.io/en/latest/develop/package/binman.html
> +
> + with the current image-description format at:
> +
> + https://u-boot.readthedocs.io/en/latest/develop/package/binman.html#image-description-format
> +
> +allOf:
> + - $ref: /schemas/mtd/partitions/fixed-partitions.yaml#
> +
> +properties:
> + compatible:
> + const: binman
This couldn't possibly pass validation. Including fixed-partitions.yaml
says the compatible must be one thing and this says something else.
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + partitions {
> + compatible = "binman";
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + partition@100000 {
> + label = "u-boot";
> + reg = <0x100000 0xf00000>;
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/mtd/partitions/partitions.yaml b/Documentation/devicetree/bindings/mtd/partitions/partitions.yaml
> index 1dda2c80747b..849fd15d085c 100644
> --- a/Documentation/devicetree/bindings/mtd/partitions/partitions.yaml
> +++ b/Documentation/devicetree/bindings/mtd/partitions/partitions.yaml
> @@ -15,6 +15,7 @@ maintainers:
>
> oneOf:
> - $ref: arm,arm-firmware-suite.yaml
> + - $ref: binman.yaml
> - $ref: brcm,bcm4908-partitions.yaml
> - $ref: brcm,bcm947xx-cfe-partitions.yaml
> - $ref: fixed-partitions.yaml
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c934244acc31..ebc8158fe67d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3536,6 +3536,11 @@ F: Documentation/filesystems/bfs.rst
> F: fs/bfs/
> F: include/uapi/linux/bfs_fs.h
>
> +BINMAN
> +M: Simon Glass <sjg@chromium.org>
> +S: Supported
> +F: Documentation/devicetree/bindings/mtd/partitions/binman*
> +
> BITMAP API
> M: Yury Norov <yury.norov@gmail.com>
> R: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> --
> 2.42.0.609.gbb76f46606-goog
>
prev parent reply other threads:[~2023-10-24 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 22:04 [PATCH v4 1/3] dt-bindings: mtd: partitions: Add binman compatible Simon Glass
2023-10-09 22:04 ` [PATCH v4 2/3] dt-bindings: mtd: binman-partition: Add binman compatibles Simon Glass
2023-10-24 16:16 ` Rob Herring
2023-10-24 21:40 ` Simon Glass
2023-10-25 8:11 ` Miquel Raynal
2023-10-25 20:58 ` Simon Glass
2023-10-09 22:04 ` [PATCH v4 3/3] dt-bindings: mtd: binman-partitions: Add alignment properties Simon Glass
2023-10-24 16:29 ` Rob Herring
2023-10-24 15:57 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231024155728.GA3707756-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).