linux-kernel - [PATCH v3 0/2] Add Microchip IPC remoteproc support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260126120658.1674253-1-valentina.fernandezalanis@microchip.com>
Date: Mon, 26 Jan 2026 12:06:56 +0000
From: Valentina Fernandez <valentina.fernandezalanis@...rochip.com>
To: <andersson@...nel.org>, <mathieu.poirier@...aro.org>, <robh@...nel.org>,
	<krzk+dt@...nel.org>, <conor+dt@...nel.org>,
	<valentina.fernandezalanis@...rochip.com>
CC: <linux-remoteproc@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: [PATCH v3 0/2] Add Microchip IPC remoteproc support

Hello all,

This series adds support for the Microchip Inter-Processor
Communication (IPC) remoteproc platform driver.

Microchip RISC-V SoCs typically contain one or more clusters. Clusters
can operate in Asymmetric Multi-Processing (AMP) mode, where individual
cores or groups of cores run as independent software contexts.

The configuration is flexible, as the set of cores or clusters that can
be controlled as remote processors may vary, and memory regions used
for firmware as well as mailbox assignments depend on the system
design.

Communication with remote cores or clusters is abstracted using ecalls
to the platform's Supervisor Binary Interface (SBI) firmware, through
which the state of remote cores or clusters are controlled.

Changes in v3:
- dt-bindings:
  - Improve commit message and property descriptions as per feedback.
  - Add cpu property and update memory region descriptions.
  - Implement conditional to handle required properties
  - Implement conditionals on vring memory regions

- mchp_remoteproc driver:
  - Drop "ipc_sbi" from Makefile and rename driver file
    to mchp_remoteproc.c
  - Add support for using remote cluster CPU ID for life
    cycle management via SBI interface
  - Improve documentation for early and late boot use cases
  - Improve resource table mapping and error handling
- Link to v2: https://lore.kernel.org/r/20251121142157.3582463-1-valentina.fernandezalanis@microchip.com/

Changes in v2:
 - simplify memory region handling with memory-region-names
 - rename compatible to "microchip,ipc-sbi-remoteproc"
 - rephrase dt binding commit  subject, message and description property
 - drop microchip,auto-boot and microchip,skip-ready-wait properties
 - fix memory-region constraints and add memory-region-names
 - fix binding example and add examples for all use cases
 - Link to v1: https://lore.kernel.org/r/20240912170025.455167-6-valentina.fernandezalanis@microchip.com/

Thanks,
Valentina

Valentina Fernandez (2):
  dt-bindings: remoteproc: add Microchip IPC remoteproc
  remoteproc: add support for Microchip IPC remoteproc platform driver

 .../microchip,ipc-sbi-remoteproc.yaml         | 131 ++++
 drivers/remoteproc/Kconfig                    |  12 +
 drivers/remoteproc/Makefile                   |   1 +
 drivers/remoteproc/mchp_remoteproc.c          | 613 ++++++++++++++++++
 4 files changed, 757 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/microchip,ipc-sbi-remoteproc.yaml
 create mode 100644 drivers/remoteproc/mchp_remoteproc.c

-- 
2.34.1