From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vabhav Sharma <vabhav.sharma@nxp.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Franck LENORMAND <franck.lenormand@nxp.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Varun Sethi <V.Sethi@nxp.com>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
frank.li@nxp.com, daniel.baluta@nxp.com
Subject: Re: [PATCH 1/4] dt-bindings: firmware: secvio: Add device tree bindings
Date: Thu, 9 May 2024 07:53:42 +0200 [thread overview]
Message-ID: <750f5388-20f9-45a3-a1e6-ceac4b91329f@kernel.org> (raw)
In-Reply-To: <20240509-secvio-v1-1-90fbe2baeda2@nxp.com>
On 09/05/2024 02:45, Vabhav Sharma wrote:
> Document the secvio device tree bindings.
>
> The tampers are security feature available on i.MX products and
> managed by SNVS block.The tamper goal is to detect the variation
> of hardware or physical parameters, which can indicate an attack.
>
> The SNVS, which provides secure non-volatile storage, allows to
> detect some hardware attacks against the SoC.They are connected
> to the security-violation ports, which send an alert when an
> out-of-range value is detected.
>
> The "imx-secvio-sc" module is designed to report security violations
> and tamper triggering via SCU firmware to the user.
>
> Add the imx-scu secvio sub node and secvio sub node description.
>
> Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
> Signed-off-by: Vabhav Sharma <vabhav.sharma@nxp.com>
> ---
That's not v1, right? What changed? Why do we have to guess this?
This is thoroughly documented in kernel process so read the
documentation before posting.
> .../bindings/arm/freescale/fsl,scu-secvio.yaml | 35 ++++++++++++++++++++++
> .../devicetree/bindings/firmware/fsl,scu.yaml | 10 +++++++
> 2 files changed, 45 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,scu-secvio.yaml b/Documentation/devicetree/bindings/arm/freescale/fsl,scu-secvio.yaml
> new file mode 100644
> index 000000000000..30dc1e21f903
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,scu-secvio.yaml
> @@ -0,0 +1,35 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/freescale/fsl,scu-secvio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP i.MX Security Violation driver
Bindings are for hardware, not drivers. Describe hardware.
> +
> +maintainers:
> + - Franck LENORMAND <franck.lenormand@nxp.com>
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + Receive security violation from the SNVS via the SCU firmware. Allow to
> + register notifier for additional processing
Notifier? That's a Linux thing, how does it relate to the hardware?
> +
> +properties:
> + compatible:
> + enum:
> + - fsl,imx-sc-secvio
Missing SoC compatibles.
So no, that's just abuse of DT to instantiate driver.
NAK. Drop the binding.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-09 5:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 0:45 [PATCH 0/4] soc: imx: secvio: Add secvio support Vabhav Sharma
2024-05-09 0:45 ` [PATCH 1/4] dt-bindings: firmware: secvio: Add device tree bindings Vabhav Sharma
2024-05-09 3:06 ` Frank Li
2024-05-09 5:54 ` Krzysztof Kozlowski
2024-06-07 5:00 ` [EXT] " Vabhav Sharma
2024-06-07 5:08 ` Vabhav Sharma
2024-05-09 5:53 ` Krzysztof Kozlowski [this message]
2024-06-07 4:58 ` [EXT] " Vabhav Sharma
2024-06-07 7:07 ` Krzysztof Kozlowski
2024-06-12 7:20 ` Aisheng Dong
2024-06-13 6:13 ` Krzysztof Kozlowski
2024-06-13 8:48 ` Aisheng Dong
2024-06-16 7:33 ` Krzysztof Kozlowski
2024-06-17 10:11 ` Aisheng Dong
2024-06-17 12:11 ` Krzysztof Kozlowski
2024-05-09 0:45 ` [PATCH 2/4] firmware: imx: Add SC APIs required for secvio module Vabhav Sharma
2024-05-09 0:45 ` [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW Vabhav Sharma
2024-05-09 0:45 ` [PATCH 4/4] arm64: dts: imx8q: Add node for Security Violation Vabhav Sharma
2024-05-09 5:51 ` [PATCH 0/4] soc: imx: secvio: Add secvio support Krzysztof Kozlowski
2024-06-07 4:52 ` [EXT] " Vabhav Sharma
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=750f5388-20f9-45a3-a1e6-ceac4b91329f@kernel.org \
--to=krzk@kernel.org \
--cc=V.Sethi@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.com \
--cc=vabhav.sharma@nxp.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