Commit a72ab251 authored by Anup Patel's avatar Anup Patel Committed by Paul Walmsley
Browse files

dt-bindings: Add RPMI system MSI message proxy bindings 



Add device tree bindings for the RPMI system MSI service group
based message proxy implemented by the SBI implementation (machine
mode firmware or hypervisor).

The RPMI system MSI service group is defined by the RISC-V
platform management interface (RPMI) specification.

Reviewed-by: default avatarAtish Patra <atishp@rivosinc.com>
Reviewed-by: default avatarConor Dooley <conor.dooley@microchip.com>
Signed-off-by: default avatarAnup Patel <apatel@ventanamicro.com>
Acked-by: default avatarJassi Brar <jassisinghbrar@gmail.com>
Link: https://lore.kernel.org/r/20250818040920.272664-12-apatel@ventanamicro.com


Signed-off-by: default avatarPaul Walmsley <pjw@kernel.org>
parent 5ba9f520

Documentation/devicetree/bindings/interrupt-controller/riscv,rpmi-mpxy-system-msi.yaml

0 → 100644
+67 −0
Original line number Diff line number Diff line 
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)

%YAML 1.2

---

$id: http://devicetree.org/schemas/interrupt-controller/riscv,rpmi-mpxy-system-msi.yaml#

$schema: http://devicetree.org/meta-schemas/core.yaml#



title: RISC-V RPMI system MSI service group based message proxy



maintainers:

  - Anup Patel <anup@brainfault.org>



description: |

  The RISC-V Platform Management Interface (RPMI) [1] defines a

  messaging protocol which is modular and extensible. The supervisor

  software can send/receive RPMI messages via SBI MPXY extension [2]

  or some dedicated supervisor-mode RPMI transport.



  The RPMI specification [1] defines system MSI service group which

  allow application processors to receive MSIs upon system events

  such as P2A doorbell, graceful shutdown/reboot request, CPU hotplug

  event, memory hotplug event, etc from the platform microcontroller.

  The SBI implementation (machine mode firmware or hypervisor) can

  implement an SBI MPXY channel to allow RPMI system MSI service

  group access to the supervisor software.



  ===========================================

  References

  ===========================================



  [1] RISC-V Platform Management Interface (RPMI) v1.0 (or higher)

      https://github.com/riscv-non-isa/riscv-rpmi/releases



  [2] RISC-V Supervisor Binary Interface (SBI) v3.0 (or higher)

      https://github.com/riscv-non-isa/riscv-sbi-doc/releases



properties:

  compatible:

    description:

      Intended for use by the SBI implementation.

    const: riscv,rpmi-mpxy-system-msi



  mboxes:

    maxItems: 1

    description:

      Mailbox channel of the underlying RPMI transport.



  riscv,sbi-mpxy-channel-id:

    $ref: /schemas/types.yaml#/definitions/uint32

    description:

      The SBI MPXY channel id to be used for providing RPMI access to

      the supervisor software.



required:

  - compatible

  - mboxes

  - riscv,sbi-mpxy-channel-id



additionalProperties: false



examples:

  - |

    interrupt-controller {

        compatible = "riscv,rpmi-mpxy-system-msi";

        mboxes = <&rpmi_shmem_mbox 0x2>;

        riscv,sbi-mpxy-channel-id = <0x2000>;

    };

...