spa: add Capability and PeerCapability

Add a new SPA_TYPE_OBJECT_ParamDict object that contains a struct with
key/value pairs. We're using something similar for Tags but this is a
more generic version.

Make a new Capability param that uses the ParamDict object. This is
meant to be used to describe capabilities with the generic key/value
struct.

Make a new PeerParam object where the keys are generic ids of the peer
objects and the values any Pod. The idea is to use this object to store
a peer objects. Make some helpers to iterate the peers and their
objects.

Add a new PeerCapability param that uses the PeerParam object with
Capability objects. This can be used to send the collection of
Capabilities from all peers to a port. This is a bit like the tags but
in a more generic way. The tags could also be implemented in this new
generic way later.

Make the PeerFormats use the same PeerParam of Format objects.

The Capability param is set on ports. impl-link will collect all
Capability objects into a PeerCapability object and send this to the
peer. The difference with the Tag param is that these Capability params
are not in any way forwared on the node automatically (like what is done
in the loopback module) because they represent the capabilities of the
ports betweem the link.
This commit is contained in:
Wim Taymans 2025-11-14 10:34:49 +01:00
parent 8d59ad2713
commit 941fc5f51c
22 changed files with 635 additions and 47 deletions

View file

@ -127,7 +127,9 @@ PWTEST(utils_abi)
pwtest_int_eq(SPA_TYPE_OBJECT_ParamLatency, 0x4000b);
pwtest_int_eq(SPA_TYPE_OBJECT_ParamProcessLatency, 0x4000c);
pwtest_int_eq(SPA_TYPE_OBJECT_ParamTag, 0x4000d);
pwtest_int_eq(_SPA_TYPE_OBJECT_LAST, 0x4000e);
pwtest_int_eq(SPA_TYPE_OBJECT_PeerParam, 0x4000e);
pwtest_int_eq(SPA_TYPE_OBJECT_ParamDict, 0x4000f);
pwtest_int_eq(_SPA_TYPE_OBJECT_LAST, 0x40010);
pwtest_int_eq(SPA_TYPE_VENDOR_PipeWire, 0x02000000);
pwtest_int_eq(SPA_TYPE_VENDOR_Other, 0x7f000000);