Received-SPF: pass (google.com: domain of linux-kernel+bounces-160410-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 26 Apr 2024 17:52:39 +0100
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
Message-ID: <20240426-iodine-unclamped-c5b74361761d@spud>
References: <20240424190612.17349-1-afd@ti.com>
 <20240424190612.17349-2-afd@ti.com>
 <171399099843.670532.4326365049493230346.robh@kernel.org>
 <20240425-herself-brigade-5b6b53dc5133@spud>
 <35e37395-c6d9-42ef-839c-bac47b50f3bf@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="+4EvlqZoEW1CXVa2"
Content-Disposition: inline
In-Reply-To: <35e37395-c6d9-42ef-839c-bac47b50f3bf@ti.com>


--+4EvlqZoEW1CXVa2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
> > >=20
> > > On Wed, 24 Apr 2024 14:06:09 -0500, Andrew Davis wrote:
> > > > From: Hari Nagalla <hnagalla@ti.com>
> > > >=20
> > > > 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 loadi=
ng
> > > > and starting the M4F subsystems.
> > > >=20
> > > > The YAML binding document provides the various node properties to be
> > > > configured by the consumers of the M4F subsystem.
> > > >=20
> > > > 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/t=
i,k3-m4f-rproc.yaml
> > > >=20
> > >=20
> > > My bot found errors running 'make dt_binding_check' on your patch:
> > >=20
> > > yamllint warnings/errors:
> > >=20
> > > dtschema/dtc warnings/errors:
> > >=20
> > >=20
> > > doc reference errors (make refcheckdocs):
> > > Warning: Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc=
=2Eyaml references a file that doesn't exist: Documentation/devicetree/bind=
ings/reserved-memory/reserved-memory.yaml
> > > Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml: Do=
cumentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
> >=20
> > The file is now in dt-schema:
> > https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/=
reserved-memory/reserved-memory.yaml
>=20
> 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)"

--+4EvlqZoEW1CXVa2
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZivb1wAKCRB4tDGHoIJi
0sFAAQCE26iVq+TBfiAaSZAlbmVskHWiA0rzfsJCTpipRqEv1gD8DwDsmF1fYkkF
Y9pheRDvXsneCjGJmeN7gV3XdJj68QE=
=BPm1
-----END PGP SIGNATURE-----

--+4EvlqZoEW1CXVa2--