From: Tanmay Shah <tanmay.shah@xilinx.com>
To: <bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>,
<robh+dt@kernel.org>, <krzk+dt@kernel.org>,
<michal.simek@xilinx.com>
Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Ben Levinsky <ben.levinsky@xilinx.com>,
Tanmay Shah <tanmay.shah@xilinx.com>
Subject: [PATCH v5 3/6] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration.
Date: Wed, 18 May 2022 12:44:26 -0700 [thread overview]
Message-ID: <20220518194426.3784095-4-tanmay.shah@xilinx.com> (raw)
In-Reply-To: <20220518194426.3784095-1-tanmay.shah@xilinx.com>
From: Ben Levinsky <ben.levinsky@xilinx.com>
Add ZynqMP firmware ioctl enums for RPU configuration and TCM Nodes for
later use via request_node and release_node
Signed-off-by: Ben Levinsky <ben.levinsky@xilinx.com>
Signed-off-by: Tanmay Shah <tanmay.shah@xilinx.com>
---
Changes in v5:
- None
Changes in v4:
- None
Changes in v3:
- None
include/linux/firmware/xlnx-zynqmp.h | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/include/linux/firmware/xlnx-zynqmp.h b/include/linux/firmware/xlnx-zynqmp.h
index 14f00a7672d1..54331b726ab0 100644
--- a/include/linux/firmware/xlnx-zynqmp.h
+++ b/include/linux/firmware/xlnx-zynqmp.h
@@ -129,6 +129,10 @@ enum pm_ret_status {
};
enum pm_ioctl_id {
+ IOCTL_GET_RPU_OPER_MODE = 0,
+ IOCTL_SET_RPU_OPER_MODE = 1,
+ IOCTL_RPU_BOOT_ADDR_CONFIG = 2,
+ IOCTL_TCM_COMB_CONFIG = 3,
IOCTL_SD_DLL_RESET = 6,
IOCTL_SET_SD_TAPDELAY = 7,
IOCTL_SET_PLL_FRAC_MODE = 8,
@@ -166,6 +170,21 @@ enum pm_query_id {
PM_QID_CLOCK_GET_MAX_DIVISOR = 13,
};
+enum rpu_oper_mode {
+ PM_RPU_MODE_LOCKSTEP = 0,
+ PM_RPU_MODE_SPLIT = 1,
+};
+
+enum rpu_boot_mem {
+ PM_RPU_BOOTMEM_LOVEC = 0,
+ PM_RPU_BOOTMEM_HIVEC = 1,
+};
+
+enum rpu_tcm_comb {
+ PM_RPU_TCM_SPLIT = 0,
+ PM_RPU_TCM_COMB = 1,
+};
+
enum zynqmp_pm_reset_action {
PM_RESET_ACTION_RELEASE = 0,
PM_RESET_ACTION_ASSERT = 1,
--
2.25.1
next prev parent reply other threads:[~2022-05-18 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 19:44 [PATCH v5 0/6] Add Xilinx RPU subsystem support Tanmay Shah
2022-05-18 19:44 ` [PATCH v5 1/6] dt-bindings: remoteproc: Add Xilinx RPU subsystem bindings Tanmay Shah
2022-05-21 15:12 ` Krzysztof Kozlowski
2022-05-23 21:38 ` Tanmay Shah
2022-05-24 9:19 ` Krzysztof Kozlowski
2022-05-24 15:43 ` Tanmay Shah
2022-05-24 17:28 ` Krzysztof Kozlowski
2022-05-24 18:09 ` Tanmay Shah
2022-05-18 19:44 ` [PATCH v5 2/6] arm64: dts: xilinx: zynqmp: Add RPU subsystem device node Tanmay Shah
2022-05-18 19:44 ` Tanmay Shah [this message]
2022-05-18 19:44 ` [PATCH v5 4/6] firmware: xilinx: Add shutdown/wakeup APIs Tanmay Shah
2022-05-18 19:44 ` [PATCH v5 5/6] firmware: xilinx: Add RPU configuration APIs Tanmay Shah
2022-05-18 19:44 ` [PATCH v5 6/6] drivers: remoteproc: Add Xilinx r5 remoteproc driver Tanmay Shah
2022-05-19 10:19 ` [PATCH v5 0/6] Add Xilinx RPU subsystem support Mathieu Poirier
2022-05-20 3:10 ` tanmay.shah
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=20220518194426.3784095-4-tanmay.shah@xilinx.com \
--to=tanmay.shah@xilinx.com \
--cc=ben.levinsky@xilinx.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@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).