linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wendy Liang <wendy.liang@xilinx.com>
To: <ohad@wizery.com>, <bjorn.andersson@linaro.org>,
	<michal.simek@xilinx.com>, <robh+dt@kernel.org>,
	<mark.rutland@arm.com>, <rajan.vaja@xilinx.com>,
	<jollys@xilinx.com>
Cc: <linux-remoteproc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Wendy Liang <jliang@xilinx.com>
Subject: [PATCH 1/7] firmware: xlnx-zynqmp: Add RPU ioctl enums
Date: Thu, 16 Aug 2018 00:06:24 -0700	[thread overview]
Message-ID: <1534403190-28523-2-git-send-email-jliang@xilinx.com> (raw)
In-Reply-To: <1534403190-28523-1-git-send-email-jliang@xilinx.com>

Add ZynqMP firmware ioctl enums for RPU configuration.

Signed-off-by: Wendy Liang <jliang@xilinx.com>
---
 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 a3ef7d6..9c4258f 100644
--- a/include/linux/firmware/xlnx-zynqmp.h
+++ b/include/linux/firmware/xlnx-zynqmp.h
@@ -59,6 +59,10 @@ enum pm_ret_status {
 };
 
 enum pm_ioctl_id {
+	IOCTL_GET_RPU_OPER_MODE = 0,
+	IOCTL_SET_RPU_OPER_MODE,
+	IOCTL_RPU_BOOT_ADDR_CONFIG,
+	IOCTL_TCM_COMB_CONFIG,
 	IOCTL_SET_PLL_FRAC_MODE = 8,
 	IOCTL_GET_PLL_FRAC_MODE,
 	IOCTL_SET_PLL_FRAC_DATA,
@@ -75,6 +79,21 @@ enum pm_query_id {
 	PM_QID_CLOCK_GET_NUM_CLOCKS = 12,
 };
 
+enum rpu_oper_mode {
+	PM_RPU_MODE_LOCKSTEP,
+	PM_RPU_MODE_SPLIT,
+};
+
+enum rpu_boot_mem {
+	PM_RPU_BOOTMEM_LOVEC,
+	PM_RPU_BOOTMEM_HIVEC,
+};
+
+enum rpu_tcm_comb {
+	PM_RPU_TCM_SPLIT,
+	PM_RPU_TCM_COMB,
+};
+
 /**
  * struct zynqmp_pm_query_data - PM query data
  * @qid:	query ID
-- 
2.7.4


  reply	other threads:[~2018-08-16  7:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  7:06 [PATCH 0/7] Add Xilinx ZynqMP R5 remoteproc driver Wendy Liang
2018-08-16  7:06 ` Wendy Liang [this message]
2018-08-16  7:06 ` [PATCH 2/7] firmware: xlnx-zynqmp: Add request ack enums Wendy Liang
2018-08-16  7:06 ` [PATCH 3/7] firmware: xilinx-zynqmp: Add request access capability macro Wendy Liang
2018-08-16  7:06 ` [PATCH 4/7] firmware: xlnx-zynqmp: Add request/release node Wendy Liang
2018-08-16  7:06 ` [PATCH 5/7] firmware: xlnx-zynqmp: Add shutdown/wakeup request Wendy Liang
2018-08-16  7:06 ` [PATCH 6/7] remoteproc: Add Xilinx ZynqMP R5 remoteproc Wendy Liang
2018-08-24 16:26   ` Wendy Liang
2018-09-10 17:16     ` Wendy Liang
2018-09-10 20:24   ` Loic PALLARDY
2018-09-10 22:09     ` Jiaying Liang
2018-09-11  7:30       ` Loic PALLARDY
2018-10-06  5:44   ` Bjorn Andersson
2018-08-16  7:06 ` [PATCH 7/7] Documentation: devicetree: Add Xilinx R5 rproc binding Wendy Liang
2018-08-17 15:09   ` Rob Herring
2018-08-20  5:54     ` Wendy Liang
2018-08-17 16:31   ` Moritz Fischer
2018-08-20  5:55     ` Wendy Liang
2018-10-06  5:50   ` Bjorn Andersson

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=1534403190-28523-2-git-send-email-jliang@xilinx.com \
    --to=wendy.liang@xilinx.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jliang@xilinx.com \
    --cc=jollys@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=ohad@wizery.com \
    --cc=rajan.vaja@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).