From: Conor Dooley <conor@kernel.org>
To: Andrew Davis <afd@ti.com>
Cc: Rob Herring <robh@kernel.org>, Nishanth Menon <nm@ti.com>,
Bjorn Andersson <andersson@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Hari Nagalla <hnagalla@ti.com>,
linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-remoteproc@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-arm-kernel@lists.infradead.org,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH v8 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
Date: Fri, 26 Apr 2024 17:52:39 +0100 [thread overview]
Message-ID: <20240426-iodine-unclamped-c5b74361761d@spud> (raw)
In-Reply-To: <35e37395-c6d9-42ef-839c-bac47b50f3bf@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
On Thu, Apr 25, 2024 at 02:03:36PM -0500, Andrew Davis wrote:
> 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 <hnagalla@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.welch@collabora.com>
> > > > Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> > > > Signed-off-by: Andrew Davis <afd@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?
The only other example that I could find that didn't reference the text
binding (which points to dt-schema) said:
"(see reserved-memory/reserved-memory.yaml in dtschema project)"
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-04-26 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 19:06 [PATCH v8 0/4] TI K3 M4F support on AM62 SoCs Andrew Davis
2024-04-24 19:06 ` [PATCH v8 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Andrew Davis
2024-04-24 20:36 ` Rob Herring
2024-04-25 17:15 ` Conor Dooley
2024-04-25 19:03 ` Andrew Davis
2024-04-26 16:52 ` Conor Dooley [this message]
2024-04-25 17:16 ` Conor Dooley
2024-04-24 19:06 ` [PATCH v8 2/4] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Andrew Davis
2024-04-24 19:06 ` [PATCH v8 3/4] arm64: defconfig: Enable TI K3 M4 remoteproc driver Andrew Davis
2024-04-24 19:06 ` [PATCH v8 4/4] arm64: dts: ti: k3-am62: Add M4F remoteproc node Andrew Davis
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=20240426-iodine-unclamped-c5b74361761d@spud \
--to=conor@kernel.org \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).