From: Michal Simek <michal.simek@xilinx.com>
To: Ben Levinsky <ben.levinsky@xilinx.com>, <mathieu.poirier@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v24 1/5] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration.
Date: Mon, 14 Dec 2020 12:52:28 +0100 [thread overview]
Message-ID: <bf2b1981-e2e2-750b-df71-1a230850e64d@xilinx.com> (raw)
In-Reply-To: <20201130155717.26008-2-ben.levinsky@xilinx.com>
On 30. 11. 20 16:57, Ben Levinsky wrote:
> 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>
> ---
> include/linux/firmware/xlnx-zynqmp.h | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/include/linux/firmware/xlnx-zynqmp.h b/include/linux/firmware/xlnx-zynqmp.h
> index 5968df82b991..0dd2d188f8aa 100644
> --- a/include/linux/firmware/xlnx-zynqmp.h
> +++ b/include/linux/firmware/xlnx-zynqmp.h
> @@ -104,6 +104,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,
> IOCTL_SET_PLL_FRAC_MODE,
> @@ -129,6 +133,21 @@ enum pm_query_id {
> PM_QID_CLOCK_GET_MAX_DIVISOR,
> };
>
> +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,
> PM_RESET_ACTION_ASSERT,
> @@ -273,6 +292,10 @@ enum zynqmp_pm_request_ack {
> };
>
> enum pm_node_id {
> + NODE_TCM_0_A = 0xf,
> + NODE_TCM_0_B = 0x10,
> + NODE_TCM_1_A = 0x11,
> + NODE_TCM_1_B = 0x12,
Please convert these hex to int to be aligned with the rest.
> NODE_SD_0 = 39,
> NODE_SD_1,
> };
>
When that fixed feel free to add.
Acked-by: Michal Simek <michal.simek@xilinx.com>
Thanks,
Michal
next prev parent reply other threads:[~2020-12-14 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 15:57 [PATCH v24 0/5] Provide basic driver to control Arm R5 co-processor found on Xilinx ZynqMP Ben Levinsky
2020-11-30 15:57 ` [PATCH v24 1/5] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Ben Levinsky
2020-12-14 11:52 ` Michal Simek [this message]
2020-11-30 15:57 ` [PATCH v24 2/5] firmware: xilinx: Add shutdown/wakeup APIs Ben Levinsky
2020-11-30 15:57 ` [PATCH v24 3/5] firmware: xilinx: Add RPU configuration APIs Ben Levinsky
2020-11-30 15:57 ` [PATCH v24 4/5] dt-bindings: remoteproc: Add documentation for ZynqMP R5 rproc bindings Ben Levinsky
2020-12-07 18:04 ` Mathieu Poirier
2020-12-07 20:58 ` Ben Levinsky
2020-11-30 15:57 ` [PATCH v24 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver Ben Levinsky
2020-12-07 21:08 ` Mathieu Poirier
2020-12-08 16:48 ` Mathieu Poirier
2020-12-09 19:00 ` Mathieu Poirier
2020-12-10 20:56 ` Mathieu Poirier
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=bf2b1981-e2e2-750b-df71-1a230850e64d@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=ben.levinsky@xilinx.com \
--cc=devicetree@vger.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 \
/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