Skip to content

Commit cbc1b25

Browse files
committed
developer_guides: firmware: update the components part
The UUID now is ready on topology and driver, update the documentation part. Signed-off-by: Keyon Jie <yang.jie@linux.intel.com>
1 parent 8d7dda6 commit cbc1b25

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

developer_guides/firmware/components/component-overview.rst

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,12 @@ uAPI to create a component of that ``type``. It also provides an entry point
2424
to the component ops implementation.
2525

2626
UUIDs (Universally Unique Identifiers) provide a more scalable and
27-
collision-free way of component identification. UUIDs are currently used by
28-
the tracing subsystem while both the topology and driver still depend on
29-
``type`` to define topology and create component instances. UUIDs are
30-
expected to replace the ``type`` in these parts as well.
27+
collision-free way of component identification. UUIDs are currently used as
28+
the standard interface by all users of the SOF firmware, including the
29+
tracing subsystem, the topology .m4 files, and the Linux topology driver.
30+
Using the ``type`` to define topology and create component is still supported
31+
today, but the ``type`` could be moved out of the IPC struct in the future,
32+
so allocating UUID for the new added component driver is strongly recommended.
3133

3234
The UUID entry declared in the FW code contains the identifier value as well
3335
as the object which is the component name in this case. Both are

0 commit comments

Comments
 (0)