On 4/25/24 12:15 PM, Conor Dooley wrote:
On Wed, Apr 24, 2024 at 03:36:39PM -0500, Rob Herring wrote:
On Wed, 24 Apr 2024 14:06:09 -0500, Andrew Davis wrote:
From: Hari Nagalla <hnaga...@ti.com>
K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
The remote processor's life cycle management and IPC mechanisms are
similar across the R5F and M4F cores from remote processor driver
point of view. However, there are subtle differences in image loading
and starting the M4F subsystems.
The YAML binding document provides the various node properties to be
configured by the consumers of the M4F subsystem.
Signed-off-by: Martyn Welch <martyn.we...@collabora.com>
Signed-off-by: Hari Nagalla <hnaga...@ti.com>
Signed-off-by: Andrew Davis <a...@ti.com>
---
.../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 126 ++++++++++++++++++
1 file changed, 126 insertions(+)
create mode 100644
Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
doc reference errors (make refcheckdocs):
Warning: Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
references a file that doesn't exist:
Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml:
Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
The file is now in dt-schema:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/reserved-memory/reserved-memory.yaml
So should I use "reserved-memory/reserved-memory.yaml" here, or just
drop this line completely?
Andrew
