From: franck.lenormand@oss.nxp.com
To: shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com
Cc: franck.lenormand@oss.nxp.com, kernel@pengutronix.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
aisheng.dong@nxp.com, abel.vesa@nxp.com, Anson.Huang@nxp.com,
linux@rempel-privat.de, leonard.crestez@nxp.com,
daniel.baluta@nxp.com, qiangqing.zhang@nxp.com, peng.fan@nxp.com
Subject: [PATCH v2 3/5] dt-bindings: firmware: imx-scu: Add SECVIO resource
Date: Tue, 21 Jul 2020 17:20:33 +0200 [thread overview]
Message-ID: <1595344835-67746-4-git-send-email-franck.lenormand@oss.nxp.com> (raw)
In-Reply-To: <1595344835-67746-1-git-send-email-franck.lenormand@oss.nxp.com>
From: Franck LENORMAND <franck.lenormand@oss.nxp.com>
The SNVS can trigger interruption when detecting a SECurity
VIOlation.
This patch adds the definition of the resource.
Signed-off-by: Franck LENORMAND <franck.lenormand@oss.nxp.com>
---
include/dt-bindings/firmware/imx/rsrc.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/dt-bindings/firmware/imx/rsrc.h b/include/dt-bindings/firmware/imx/rsrc.h
index 54278d5..fe5f25f 100644
--- a/include/dt-bindings/firmware/imx/rsrc.h
+++ b/include/dt-bindings/firmware/imx/rsrc.h
@@ -1,7 +1,7 @@
/* SPDX-License-Identifier: GPL-2.0+ */
/*
* Copyright (C) 2016 Freescale Semiconductor, Inc.
- * Copyright 2017-2018 NXP
+ * Copyright 2017-2018, 2020 NXP
*/
#ifndef __DT_BINDINGS_RSCRC_IMX_H
@@ -50,6 +50,7 @@
#define IMX_SC_R_DC_1_BLIT2 38
#define IMX_SC_R_DC_1_BLIT_OUT 39
#define IMX_SC_R_DC_1_WARP 42
+#define IMX_SC_R_SECVIO 44
#define IMX_SC_R_DC_1_VIDEO0 45
#define IMX_SC_R_DC_1_VIDEO1 46
#define IMX_SC_R_DC_1_FRAC0 47
--
2.7.4
next prev parent reply other threads:[~2020-07-21 15:20 UTC|newest]
Thread overview: 18+ 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 ` [PATCH v2 1/5] firmware: imx: scu-seco: Add SEcure Controller APIS franck.lenormand
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-10-18 4:48 ` Aisheng Dong
2020-07-21 15:20 ` franck.lenormand [this message]
2020-10-18 4:50 ` [PATCH v2 3/5] dt-bindings: firmware: imx-scu: Add SECVIO resource Aisheng Dong
2020-07-21 15:20 ` [PATCH v2 4/5] dt-bindings: arm: imx: Documentation of the SC secvio driver franck.lenormand
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-08-19 13:31 ` Shawn Guo
2020-09-07 9:49 ` Franck Lenormand (OSS)
2020-10-18 5:21 ` Aisheng Dong
2020-10-18 9:31 ` Borislav Petkov
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-19 13:23 ` Shawn Guo
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=1595344835-67746-4-git-send-email-franck.lenormand@oss.nxp.com \
--to=franck.lenormand@oss.nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--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 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 NNTP newsgroup(s).