All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aisheng Dong <aisheng.dong@nxp.com>
To: "Franck Lenormand (OSS)" <franck.lenormand@oss.nxp.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	dl-linux-imx <linux-imx@nxp.com>, Abel Vesa <abel.vesa@nxp.com>,
	Anson Huang <anson.huang@nxp.com>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Joakim Zhang <qiangqing.zhang@nxp.com>,
	Peng Fan <peng.fan@nxp.com>
Subject: RE: [PATCH v2 4/5] dt-bindings: arm: imx: Documentation of the SC secvio driver
Date: Sun, 18 Oct 2020 05:03:05 +0000	[thread overview]
Message-ID: <AM6PR04MB49666A87566154AF128DC47C80010@AM6PR04MB4966.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1595344835-67746-5-git-send-email-franck.lenormand@oss.nxp.com>

> From: Franck Lenormand (OSS) <franck.lenormand@oss.nxp.com>
> Sent: Tuesday, July 21, 2020 11:21 PM
> 
> This patch adds the documentation for the SECurity VIOlation driver using the
> SCU on imx8x and imx8q.
> 
> Signed-off-by: Franck LENORMAND <franck.lenormand@oss.nxp.com>
> ---
>  .../bindings/arm/freescale/fsl,imx-sc-secvio.yaml  | 34
> ++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644
> Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> 
> diff --git
> a/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> new file mode 100644
> index 0000000..59b9a86
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.
> +++ yaml
> @@ -0,0 +1,34 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) %YAML 1.2
> +---
> +$id:
> +http://devicetree.org/schemas/arm/freescale/fsl,imx-sc-secvio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP i.MX Security Violation driver
> +
> +maintainers:
> +  - Franck LENORMAND <franck.lenormand@nxp.com>
> +
> +description: |
> +  Receive security violation from the SNVS via the SCU firmware. Allow
> +to
> +  register notifier for additional processing
> +
> +properties:
> +  compatible:
> +    enum:
> +      - fsl,imx-sc-secvio
> +  nvmem:

Can we use standard nvmem-cells?
Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml

Regards
Aisheng

> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description:
> +      Phandle to the nvmem provider.
> +
> +required:
> +  - compatible
> +  - nvmem
> +
> +examples:
> +  - |
> +    sc_secvio: sc-secvio
> +        compatible = "fsl,imx-sc-secvio";
> +        nvmem = <&ocotp>
> +    };
> --
> 2.7.4


WARNING: multiple messages have this Message-ID (diff)
From: Aisheng Dong <aisheng.dong@nxp.com>
To: "Franck Lenormand (OSS)" <franck.lenormand@oss.nxp.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>
Cc: Peng Fan <peng.fan@nxp.com>,
	Joakim Zhang <qiangqing.zhang@nxp.com>,
	Abel Vesa <abel.vesa@nxp.com>, Anson Huang <anson.huang@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	dl-linux-imx <linux-imx@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v2 4/5] dt-bindings: arm: imx: Documentation of the SC secvio driver
Date: Sun, 18 Oct 2020 05:03:05 +0000	[thread overview]
Message-ID: <AM6PR04MB49666A87566154AF128DC47C80010@AM6PR04MB4966.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1595344835-67746-5-git-send-email-franck.lenormand@oss.nxp.com>

> From: Franck Lenormand (OSS) <franck.lenormand@oss.nxp.com>
> Sent: Tuesday, July 21, 2020 11:21 PM
> 
> This patch adds the documentation for the SECurity VIOlation driver using the
> SCU on imx8x and imx8q.
> 
> Signed-off-by: Franck LENORMAND <franck.lenormand@oss.nxp.com>
> ---
>  .../bindings/arm/freescale/fsl,imx-sc-secvio.yaml  | 34
> ++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644
> Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> 
> diff --git
> a/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
> new file mode 100644
> index 0000000..59b9a86
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.
> +++ yaml
> @@ -0,0 +1,34 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) %YAML 1.2
> +---
> +$id:
> +http://devicetree.org/schemas/arm/freescale/fsl,imx-sc-secvio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP i.MX Security Violation driver
> +
> +maintainers:
> +  - Franck LENORMAND <franck.lenormand@nxp.com>
> +
> +description: |
> +  Receive security violation from the SNVS via the SCU firmware. Allow
> +to
> +  register notifier for additional processing
> +
> +properties:
> +  compatible:
> +    enum:
> +      - fsl,imx-sc-secvio
> +  nvmem:

Can we use standard nvmem-cells?
Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml

Regards
Aisheng

> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description:
> +      Phandle to the nvmem provider.
> +
> +required:
> +  - compatible
> +  - nvmem
> +
> +examples:
> +  - |
> +    sc_secvio: sc-secvio
> +        compatible = "fsl,imx-sc-secvio";
> +        nvmem = <&ocotp>
> +    };
> --
> 2.7.4

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-18  5:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 15:20 [PATCH v2 0/5] Add support of SECVIO from SNVS on iMX8q/x franck.lenormand
2020-07-21 15:20 ` franck.lenormand
2020-07-21 15:20 ` [PATCH v2 1/5] firmware: imx: scu-seco: Add SEcure Controller APIS franck.lenormand
2020-07-21 15:20   ` franck.lenormand
2020-10-18  4:30   ` Aisheng Dong
2020-10-18  4:30     ` Aisheng Dong
2020-07-21 15:20 ` [PATCH v2 2/5] firmware: imx: scu-irq: Add API to retrieve status of IRQ franck.lenormand
2020-07-21 15:20   ` franck.lenormand
2020-10-18  4:48   ` Aisheng Dong
2020-10-18  4:48     ` Aisheng Dong
2020-07-21 15:20 ` [PATCH v2 3/5] dt-bindings: firmware: imx-scu: Add SECVIO resource franck.lenormand
2020-07-21 15:20   ` franck.lenormand
2020-10-18  4:50   ` Aisheng Dong
2020-10-18  4:50     ` Aisheng Dong
2020-07-21 15:20 ` [PATCH v2 4/5] dt-bindings: arm: imx: Documentation of the SC secvio driver franck.lenormand
2020-07-21 15:20   ` franck.lenormand
2020-10-18  5:03   ` Aisheng Dong [this message]
2020-10-18  5:03     ` Aisheng Dong
2020-07-21 15:20 ` [PATCH v2 5/5] soc: imx8: Add the SC SECVIO driver franck.lenormand
2020-07-21 15:20   ` franck.lenormand
2020-08-19 13:31   ` Shawn Guo
2020-08-19 13:31     ` Shawn Guo
2020-09-07  9:49     ` Franck Lenormand (OSS)
2020-09-07  9:49       ` Franck Lenormand (OSS)
2020-10-18  5:21     ` Aisheng Dong
2020-10-18  5:21       ` Aisheng Dong
2020-10-18  9:31       ` Borislav Petkov
2020-10-18  9:31         ` Borislav Petkov
2020-10-19  1:08         ` Peng Fan
2020-10-19  1:08           ` Peng Fan
2020-08-18  7:52 ` [PATCH v2 0/5] Add support of SECVIO from SNVS on iMX8q/x Franck LENORMAND (OSS)
2020-08-18  7:52   ` Franck LENORMAND (OSS)
2020-08-19 13:23   ` Shawn Guo
2020-08-19 13:23     ` Shawn Guo
2020-09-14  3:43     ` Aisheng Dong
2020-09-14  3:43       ` Aisheng Dong

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=AM6PR04MB49666A87566154AF128DC47C80010@AM6PR04MB4966.eurprd04.prod.outlook.com \
    --to=aisheng.dong@nxp.com \
    --cc=abel.vesa@nxp.com \
    --cc=anson.huang@nxp.com \
    --cc=daniel.baluta@nxp.com \
    --cc=festevam@gmail.com \
    --cc=franck.lenormand@oss.nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=peng.fan@nxp.com \
    --cc=qiangqing.zhang@nxp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.