opensbi.git/include/sbi_utils/mpxy, branch masterUnnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/opensbi.git/atom/include/sbi_utils/mpxy?h=master2025-06-24T03:12:27Zlib: utils: Add Implementation ID and Version as RPMI MPXY attributes2025-06-24T03:12:27ZRahul Pathakrpathak@ventanamicro.com2025-06-18T05:38:53Zurn:sha1:a5fdef45dbd50d40162852a2b7333135fe3439be
The latest frozen RPMI spec has added Implementation ID
and Implementation Version as message protocol specific
mpxy attributes. Add support for these.
Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Link: https://lore.kernel.org/r/20250618053854.2577299-1-rpathak@ventanamicro.com
Signed-off-by: Anup Patel <anup@brainfault.org>
lib: utils: Fix fdt_mpxy_init() not returning error code2025-05-20T05:50:57ZAlvin Changalvinga@andestech.com2025-04-30T09:10:07Zurn:sha1:2bb76326496440996b44bf20f3ceab127c7f72ae
It seems that current implementation doesn't fail on fdt_mpxy_init(),
because platforms might not have any MPXY devices. In fact, if there are
no MPXY devices, fdt_driver_init_all() will return SBI_OK.
More importantly, if there is any MPXY device which fails the
initialization, OpenSBI must check the error code and stop the booting.
Thus, this commit adds the return value for fdt_mpxy_init().
Signed-off-by: Alvin Chang <alvinga@andestech.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Link: https://lore.kernel.org/r/20250430091007.3768180-1-alvinga@andestech.com
Signed-off-by: Anup Patel <anup@brainfault.org>
lib: utils: Populate MPXY channel attributes from RPMI channel attributes2025-02-13T05:40:03ZAnup Patelapatel@ventanamicro.com2025-01-12T11:29:46Zurn:sha1:e4bc55930b1755f7ec045ba2ad158868e7f6dd5d
Use the RPMI mailbox channel attributes to populate MPXY channel
attributes instead of hard coding them.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>
lib: utils: Drop notifications from MPXY RPMI mailbox client2025-02-13T05:40:03ZAnup Patelapatel@ventanamicro.com2025-01-12T05:10:01Zurn:sha1:879ee6859cfb2d3241923af615f7f1e77aba32c5
Currently, the common MPXY RPMI mailbox client does not support
notifications so no need for dummy notifications support.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
lib: utils: Introduce optional MPXY RPMI service group operations2025-02-13T05:40:03ZAnup Patelapatel@ventanamicro.com2025-01-12T03:58:37Zurn:sha1:75c2057a6f95520fd9d2b07299d1dbb5de9113d1
Some of the RPMI service groups may need additional context and
special handling when transferring messages via underlying mailbox
channel so introduce optional MPXY RPMI service group operations
for this purpose.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>
lib: utils: Split the FDT MPXY RPMI mailbox client into two parts2025-02-13T05:40:03ZAnup Patelapatel@ventanamicro.com2025-01-11T09:08:34Zurn:sha1:d14340cb315195bd556ed89d5ca7a49335768ddc
Instead of having one common FDT MPXY RPMI mailbox client drivers
for various RPMI service groups, split this driver into two parts:
1) Common MPXY RPMI mailbox client library
2) MPXY driver for RPMI clock service group
The above split enables having a separate MPXY driver for each
RPMI clock service group and #1 (above) will allow code sharing
between various MPXY RPMI drivers.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>
lib: utils: Add simple FDT based MPXY driver framework2024-12-06T03:56:54ZAnup Patelapatel@ventanamicro.com2024-08-08T05:41:10Zurn:sha1:32577ec3a1eea116145089f9264e7f27582c396c
The generic platform can have multiple MPXY drivers so add a simple
FDT based MPXY driver framework.
Signed-off-by: Anup Patel <apatel@ventanamicro.com>