From: Rob Herring <robh@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: vigneshr@ti.com, richard@nod.at, miquel.raynal@bootlin.com,
joern@lazybastard.org, kernel@axis.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, frowand.list@gmail.com,
krzysztof.kozlowski@canonical.com
Subject: Re: [PATCH 2/4] dt-bindings: reserved-memory: Add phram
Date: Thu, 10 Mar 2022 14:58:58 -0600 [thread overview]
Message-ID: <YipmkgOuLZGVqH7S@robh.at.kernel.org> (raw)
In-Reply-To: <20220307141549.2732179-3-vincent.whitchurch@axis.com>
On Mon, Mar 07, 2022 at 03:15:47PM +0100, Vincent Whitchurch wrote:
> Add bindings to allow MTD/block devices to be created in reserved-memory
> regions using the "phram" driver.
What does 'ph' mean? Please define somewhere for the binding.
>
> This allows things like partitioning to be specified via the existing
> devicetree bindings.
>
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> .../bindings/reserved-memory/phram.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/phram.yaml
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/phram.yaml b/Documentation/devicetree/bindings/reserved-memory/phram.yaml
> new file mode 100644
> index 000000000000..92e7a80ee87a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reserved-memory/phram.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/reserved-memory/phram.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MTD/block device in RAM
> +
> +description: |
> + Use the reserved memory region as an MTD or block device.
> +
> + If no-map is not set, cached mappings will be used for the memory region.
> +
> +maintainers:
> + - Vincent Whitchurch <vincent.whitchurch@axis.com>
> +
> +allOf:
> + - $ref: "reserved-memory.yaml"
> + - $ref: "../mtd/mtd.yaml"
/schemas/mtd/mtd.yaml
> +
> +properties:
> + compatible:
> + const: phram
> +
> + reg:
> + description: region of memory that contains the MTD/block device
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + reserved-memory {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + phram: flash@12340000 {
> + compatible = "phram";
> + label = "rootfs";
That's an odd example...
> + reg = <0x12340000 0x00800000>;
> + };
> + };
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2022-03-10 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 14:15 [PATCH 0/4] mtd: phram improvements Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 1/4] mtd: core: Check devicetree alias for index Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 2/4] dt-bindings: reserved-memory: Add phram Vincent Whitchurch
2022-03-10 20:58 ` Rob Herring [this message]
2022-03-11 10:13 ` Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 3/4] mtd: phram: Allow probing via reserved-memory Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 4/4] mtd: phram: Allow cached mappings Vincent Whitchurch
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=YipmkgOuLZGVqH7S@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=joern@lazybastard.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=vincent.whitchurch@axis.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