Move it to a common file named `zephyr,memory-common.yaml`, which replaces `zephyr,memory-attr.yaml` and takes its contents as well. This is so that another binding, e.g., `vnd,memory-region`, can support being combined with the `zephyr,memory-region` binding like so: node@deadbeef { compatible = "vnd,memory-region", "zephyr,memory-region"; zephyr,memory-region = "NAME"; ... }; To allow this, edtlib would require `vnd,memory-region` to include the property definitions from this new common file. The same can't be done by including `zephyr,memory-region.yaml` directly because that file marks the property in question as always required, and it shouldn't be required whenever the `vnd,memory-region` compatible is used on its own. Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no>
30 lines
921 B
YAML
30 lines
921 B
YAML
# Copyright (c) 2023, Carlo Caione <ccaione@baylibre.com>
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
include: [base.yaml]
|
|
|
|
properties:
|
|
zephyr,memory-region:
|
|
type: string
|
|
description: |
|
|
Signify that this node should result in a dedicated linker script
|
|
memory region in the final executable. The region address and size
|
|
is taken from the <reg> property, while the name is the value of
|
|
this property.
|
|
|
|
zephyr,memory-region-mpu:
|
|
type: string
|
|
deprecated: true
|
|
description: |
|
|
Signify that this node should result in a dedicated MPU region.
|
|
Deprecated in favor of 'zephyr,memory-attr'.
|
|
|
|
zephyr,memory-attr:
|
|
type: int
|
|
description: |
|
|
Attribute or set of attributes (bitmask) for the memory region. See
|
|
'include/zephyr/dt-bindings/memory-attr/memory-attr.h' for a
|
|
comprehensive list with description of possible values.
|
|
|
|
reg:
|
|
required: true
|