[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANLsYkwC0hW3YPmfxOCW+sQcNVVficvPX0+yhsTnKb70f_4taA@mail.gmail.com>
Date: Fri, 13 Sep 2024 08:44:58 -0600
From: Mathieu Poirier <mathieu.poirier@...aro.org>
To: Valentina Fernandez <valentina.fernandezalanis@...rochip.com>
Cc: paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
peterlin@...estech.com, dminus@...estech.com, conor.dooley@...rochip.com,
conor+dt@...nel.org, ycliang@...estech.com, jassisinghbrar@...il.com,
robh@...nel.org, krzk+dt@...nel.org, andersson@...nel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v1 0/5] Add Microchip IPC mailbox and remoteproc support
Hi Valentina,
On Thu, 12 Sept 2024 at 10:48, Valentina Fernandez
<valentina.fernandezalanis@...rochip.com> wrote:
>
> Hello all,
>
> This series adds support for the Microchip Inter-Processor Communication
> (IPC) mailbox controller, as well as an IPC remoteproc platform driver.
>
> Microchip's family of RISC-V SoCs typically has one or more clusters
> that can be configured to run in Asymmetric Multi-Processing (AMP) mode.
>
> The Microchip IPC is used to send messages between processors using
> an interrupt signaling mechanism. The driver uses the RISC-V Supervisor
> Binary Interface (SBI) to communicate with software running in machine
> mode (M-mode) to access the IPC hardware block.
>
> Additional details on the Microchip vendor extension and the IPC
> function IDs described in the driver can be found in the following
> documentation:
>
> https://github.com/linux4microchip/microchip-sbi-ecall-extension
>
> The IPC remoteproc platform driver allows for starting and stopping
> firmware on the remote cluster(s) and facilitates RPMsg communication.
> The remoteproc attach/detach operations are also supported for use cases
> where the firmware is loaded by the Hart Software Services
> (zero-stage bootloader) before Linux boots.
>
> Error Recovery and Power Management features are not currently
> supported in the remoteproc platform driver.
>
> The PIC64GX MPU has a Mi-V IHC block, this will be added to the PIC64GX
> dts after the initial upstreaming:
>
> https://patchwork.kernel.org/project/linux-riscv/patch/20240725121609.13101-18-pierre-henry.moussay@microchip.com/
>
> Thanks,
> Valentina
>
> Valentina Fernandez (5):
> riscv: asm: vendorid_list: Add Microchip Technology to the vendor list
> dt-bindings: mailbox: add binding for Microchip IPC mailbox driver
> mailbox: add Microchip IPC support
> dt-bindings: remoteproc: add binding for Microchip IPC remoteproc
> remoteproc: add support for Microchip IPC remoteproc platform driver
>
> .../bindings/mailbox/microchip,sbi-ipc.yaml | 115 ++++
> .../remoteproc/microchip,ipc-remoteproc.yaml | 84 +++
> arch/riscv/include/asm/vendorid_list.h | 1 +
> drivers/mailbox/Kconfig | 12 +
> drivers/mailbox/Makefile | 2 +
> drivers/mailbox/mailbox-mchp-ipc-sbi.c | 539 ++++++++++++++++++
> drivers/remoteproc/Kconfig | 12 +
> drivers/remoteproc/Makefile | 1 +
> drivers/remoteproc/mchp_ipc_remoteproc.c | 461 +++++++++++++++
> include/linux/mailbox/mchp-ipc.h | 23 +
> 10 files changed, 1250 insertions(+)
It might be easier to split this patchset in two and proceed
incrementally, i.e upstream the mailbox driver first and then the
remoteproc part.
Regards,
Mathieu
> create mode 100644 Documentation/devicetree/bindings/mailbox/microchip,sbi-ipc.yaml
> create mode 100644 Documentation/devicetree/bindings/remoteproc/microchip,ipc-remoteproc.yaml
> create mode 100644 drivers/mailbox/mailbox-mchp-ipc-sbi.c
> create mode 100644 drivers/remoteproc/mchp_ipc_remoteproc.c
> create mode 100644 include/linux/mailbox/mchp-ipc.h
>
> --
> 2.34.1
>
Powered by blists - more mailing lists