[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220914145506.GA2149379-robh@kernel.org>
Date: Wed, 14 Sep 2022 09:55:06 -0500
From: Rob Herring <robh@...nel.org>
To: Doug Berger <opendmb@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Frank Rowand <frowand.list@...il.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Muchun Song <songmuchun@...edance.com>,
Mike Rapoport <rppt@...nel.org>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>,
Borislav Petkov <bp@...e.de>,
"Paul E. McKenney" <paulmck@...nel.org>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>,
Randy Dunlap <rdunlap@...radead.org>,
Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
Florian Fainelli <f.fainelli@...il.com>,
David Hildenbrand <david@...hat.com>, Zi Yan <ziy@...dia.com>,
Oscar Salvador <osalvador@...e.de>,
Hari Bathini <hbathini@...ux.ibm.com>,
Kees Cook <keescook@...omium.org>,
- <devicetree-spec@...r.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Mel Gorman <mgorman@...e.de>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-mm@...ck.org, iommu@...ts.linux.dev
Subject: Re: [PATCH 16/21] dt-bindings: reserved-memory: introduce
designated-movable-block
On Tue, Sep 13, 2022 at 12:55:03PM -0700, Doug Berger wrote:
> Introduce designated-movable-block.yaml to document the
> devicetree binding for Designated Movable Block children of the
> reserved-memory node.
What is a Designated Movable Block? This patch needs to stand on its
own.
Why does this belong or need to be in DT?
>
> Signed-off-by: Doug Berger <opendmb@...il.com>
> ---
> .../designated-movable-block.yaml | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/designated-movable-block.yaml
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/designated-movable-block.yaml b/Documentation/devicetree/bindings/reserved-memory/designated-movable-block.yaml
> new file mode 100644
> index 000000000000..42f846069a2e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reserved-memory/designated-movable-block.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/reserved-memory/designated-movable-block.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: /reserved-memory Designated Movable Block node binding
> +
> +maintainers:
> + - devicetree-spec@...r.kernel.org
> +
> +allOf:
> + - $ref: "reserved-memory.yaml"
> +
> +properties:
> + compatible:
> + const: designated-movable-block
> + description:
> + This indicates a region of memory meant to be placed into
> + ZONE_MOVABLE.
Don't put Linuxisms into bindings.
> +
> +unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - reusable
> +
> +examples:
> + - |
> + reserved-memory {
> + #address-cells = <0x2>;
> + #size-cells = <0x2>;
> +
> + DMB0@...00000 {
> + compatible = "designated-movable-block";
> + reusable;
> + reg = <0x0 0x10800000 0x0 0x2d800000>;
> + };
> +
> + DMB1@...00000 {
> + compatible = "designated-movable-block";
> + reusable;
> + reg = <0x0 0x40000000 0x0 0x30000000>;
> + };
> +
> + DMB2@...00000 {
> + compatible = "designated-movable-block";
> + reusable;
> + reg = <0x0 0x80000000 0x0 0x2fc00000>;
> + };
> + };
> --
> 2.25.1
>
>
Powered by blists - more mailing lists