Classification

The AudioManagement offers classification for sources and sinks. It can be used to group sources and sinks together and link certain behaviors to these groups. An example for such a use is to group all interrupt sources in a class together and let the AudioManagerController react different for this class.
Elements can only have one class at a time. The AudioManagerDaemon will take care of registration of sourceClasses, sinkClasses and will assign unique IDs, but the parameters of the Classes itself are product specific and have to be interpreted by the AudioManagerController. This concept allows for very individual implementations of system behaviors.
Since Classes are held in the database, Classes can be registered and deregistered during runtime, it is recommended that the AudioManagerController enters all source & sink classes at start-up into the database.A ClassProperty exists out of an enumeration (am_CustomClassProperty_t, project specific) and a corresponding value (integer) that is interpreted by the AudioManagerController according to am_CustomClassProperty_t.
There is no restriction to the number of properties a class can have and how many classes can exist in a system.

Attributes

am::am_SourceClass_s describes the attributes of a source class
am::am_SinkClass_s describes the attributes of a sink class