From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Ben Levinsky <ben.levinsky@xilinx.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-remoteproc <linux-remoteproc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH v26 0/5] Add initial zynqmp R5 remoteproc driver
Date: Tue, 23 Feb 2021 09:34:00 -0700 [thread overview]
Message-ID: <CANLsYkzkmRGsiJWnFmjdEg=yfAxbhYeu6bhW92HiKk1ugdyeww@mail.gmail.com> (raw)
In-Reply-To: <20210223154447.13247-1-ben.levinsky@xilinx.com>
Good morning,
I have received your patchset but currently don't see having the time
to look at it before the middle of March.
Thanks,
Mathieu
On Tue, 23 Feb 2021 at 08:44, Ben Levinsky <ben.levinsky@xilinx.com> wrote:
>
> R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
> remotproc driver, we can boot the R5 sub-system in two different
> configurations -
> * Split
> * Lockstep
>
> The Xilinx R5 Remoteproc Driver boots the R5's via calls to the Xilinx
> Platform Management Unit that handles the R5 configuration, memory access
> and R5 lifecycle management. The interface to this manager is done in this
> driver via zynqmp_pm_* function calls.
>
> v26:
> - add prepare and unprepare to handle Xilinx platform management's
> request_node and release node using each core's list of srams
> that is constructed in each core's zynqmp_r5_probe.
> - add new field sram to zynqmp_r5_rproc to store each core's srams
> being used as described in device tree. This helps to reduce unneeded looping
> of the sram prop in device tree. As now only zynqmp_r5_probe has to parse
> and validate each core's sram property. The ensuing prepare, unprepare
> and parse_fw logic are now much simpler.
> - similarly add 'size' field to struct sram_addr_data to simplify
> prepare, unprepare and parse_fw.
>
> Previous version:
> https://patchwork.kernel.org/project/linux-remoteproc/list/?series=412083
>
>
> Ben Levinsky (5):
> firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU
> configuration.
> firmware: xilinx: Add shutdown/wakeup APIs
> firmware: xilinx: Add RPU configuration APIs
> dt-bindings: remoteproc: Add documentation for ZynqMP R5 rproc
> bindings
> remoteproc: Add initial zynqmp R5 remoteproc driver
>
> .../xilinx,zynqmp-r5-remoteproc.yaml | 223 ++++
> drivers/firmware/xilinx/zynqmp.c | 96 ++
> drivers/remoteproc/Kconfig | 8 +
> drivers/remoteproc/Makefile | 1 +
> drivers/remoteproc/zynqmp_r5_remoteproc.c | 954 ++++++++++++++++++
> include/linux/firmware/xlnx-zynqmp.h | 64 ++
> 6 files changed, 1356 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/remoteproc/xilinx,zynqmp-r5-remoteproc.yaml
> create mode 100644 drivers/remoteproc/zynqmp_r5_remoteproc.c
>
> --
> 2.17.1
>
prev parent reply other threads:[~2021-02-23 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 15:44 [PATCH v26 0/5] Add initial zynqmp R5 remoteproc driver Ben Levinsky
2021-02-23 15:44 ` [PATCH v26 1/5] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Ben Levinsky
2021-02-23 15:44 ` [PATCH v26 2/5] firmware: xilinx: Add shutdown/wakeup APIs Ben Levinsky
2021-02-23 15:44 ` [PATCH v26 3/5] firmware: xilinx: Add RPU configuration APIs Ben Levinsky
2021-02-23 15:44 ` [PATCH v26 4/5] dt-bindings: remoteproc: Add documentation for ZynqMP R5 rproc bindings Ben Levinsky
2021-02-23 15:44 ` [PATCH v26 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver Ben Levinsky
2021-03-08 19:00 ` Mathieu Poirier
2021-03-11 23:47 ` Ben Levinsky
2021-03-15 17:25 ` Mathieu Poirier
2021-03-15 21:42 ` Ben Levinsky
2021-03-17 16:22 ` Mathieu Poirier
2021-03-09 16:53 ` Mathieu Poirier
2021-03-11 23:49 ` Ben Levinsky
2021-03-15 17:37 ` Mathieu Poirier
2021-03-15 21:32 ` Ben Levinsky
2021-03-17 16:27 ` Mathieu Poirier
2021-03-19 17:46 ` Ben Levinsky
2021-03-22 0:10 ` Ben Levinsky
2021-02-23 16:34 ` Mathieu Poirier [this message]
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='CANLsYkzkmRGsiJWnFmjdEg=yfAxbhYeu6bhW92HiKk1ugdyeww@mail.gmail.com' \
--to=mathieu.poirier@linaro.org \
--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=michal.simek@xilinx.com \
/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).