Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Pankaj Gupta <pankaj.gupta@nxp.com>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	imx@lists.linux.dev,  Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	 linux-kernel@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	 linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org,  Rob Herring <robh+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v2 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc
Date: Thu, 23 May 2024 07:25:27 -0500	[thread overview]
Message-ID: <171646712724.2026308.5404698488082776575.robh@kernel.org> (raw)
In-Reply-To: <20240523-imx-se-if-v2-2-5a6fd189a539@nxp.com>


On Thu, 23 May 2024 16:19:33 +0530, Pankaj Gupta wrote:
> The NXP security hardware IP(s) like: i.MX EdgeLock Enclave, V2X etc.,
> creates an embedded secure enclave within the SoC boundary to enable
> features like:
> - HSM
> - SHE
> - V2X
> 
> Secure-Enclave(s) communication interface are typically via message
> unit, i.e., based on mailbox linux kernel driver. This driver enables
> communication ensuring well defined message sequence protocol between
> Application Core and enclave's firmware.
> 
> Driver configures multiple misc-device on the MU, for multiple
> user-space applications, to be able to communicate over single MU.
> 
> It exists on some i.MX processors. e.g. i.MX8ULP, i.MX93 etc.
> 
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
> ---
>  .../devicetree/bindings/firmware/fsl,imx-se.yaml   | 154 +++++++++++++++++++++
>  1 file changed, 154 insertions(+)
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:

dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/firmware/fsl,imx-se.example.dtb: /example-2/firmware/v2x-if@0: failed to match any schema with compatible: ['fsl,imx95-v2x']
Documentation/devicetree/bindings/firmware/fsl,imx-se.example.dtb: /example-2/firmware/v2x-if@1: failed to match any schema with compatible: ['fsl,imx95-v2x']
Documentation/devicetree/bindings/firmware/fsl,imx-se.example.dtb: /example-2/firmware/v2x-if@2: failed to match any schema with compatible: ['fsl,imx95-v2x']

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240523-imx-se-if-v2-2-5a6fd189a539@nxp.com

The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.

If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:

pip3 install dtschema --upgrade

Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.


  reply	other threads:[~2024-05-23 12:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 10:49 [PATCH v2 0/5] Communication Interface to NXP secure-enclave HW IP like Edgelock Enclave Pankaj Gupta
2024-05-23 10:49 ` [PATCH v2 1/5] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2024-05-23 10:49 ` [PATCH v2 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2024-05-23 12:25   ` Rob Herring (Arm) [this message]
2024-05-23 12:30     ` [EXT] " Pankaj Gupta
2024-05-23 10:49 ` [PATCH v2 3/5] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2024-05-23 10:49 ` [PATCH v2 4/5] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2024-05-23 13:23   ` Sascha Hauer
2024-05-23 13:43     ` [EXT] " Pankaj Gupta
2024-05-23 18:35       ` Sascha Hauer
2024-05-24  9:07   ` Sascha Hauer
2024-06-14  8:56     ` [EXT] " Pankaj Gupta
2024-05-24 10:34   ` Sascha Hauer
2024-05-24 12:08     ` [EXT] " Pankaj Gupta
2024-05-24 12:25       ` Sascha Hauer
2024-06-14  9:05         ` Pankaj Gupta
2024-05-24 10:47   ` Sascha Hauer
2024-05-24 12:08     ` [EXT] " Pankaj Gupta
2024-05-23 10:49 ` [PATCH v2 5/5] firmware: imx: adds miscdev Pankaj Gupta
2024-05-24  8:23   ` Sascha Hauer
2024-05-24 12:03     ` [EXT] " Pankaj Gupta
2024-05-24 12:43       ` Sascha Hauer
2024-06-01  4:38         ` Pankaj Gupta
2024-06-03 16:22   ` Amit Singh Tomar
2024-06-05  9:15     ` [EXT] " Pankaj Gupta

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=171646712724.2026308.5404698488082776575.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.gupta@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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