sound/designs/midi-2.0.rst

72 Block information that are provided since UMP v1.1, and builds up the
75 builds the topology based on Group Terminal Block (GTB) information
115 Blocks, where UMP Block is an abstraction introduced in the ALSA UMP
117 Block corresponds to Function Block in UMP 1.1 specification.  When
118 UMP 1.1 Function Block information isn't available, it's filled
119 partially from Group Terminal Block (GTB) as defined in USB MIDI 2.0
136   Block 0 (ProtoZOA Main)
142   Block 1 (ProtoZOA Ext IN)
152 Those additional UMP Endpoint and UMP Block information can be
202     UMP Block 0: ProtoZOA Main [Active]
204     UMP Block 1: ProtoZOA Ext IN [Active]
206     UMP Block 2: ProtoZOA Ext OUT [Active]
232 The proc file above shows the UMP Block information, too.  The same
281 * Each UMP Block information can be obtained via another new ioctl
311   Block information of the specified UMP device via ALSA control API
369   For an Endpoint data, pass 0 to the `type` field, while for a Block
373 * With UMP 1.1, Function Block information may be changed
374   dynamically.  When the update of Function Block is received from the
441 subdirectory.  This defines the Function Block information::
488 Each Function Block may have different direction and UI-hint,
499 For example, to create a second Function Block for a keyboard::
511 For assigning a Function Block for MIDI 1.0 I/O, set up in `is_midi1`
528 MIDI 1.0 ports are set up from the config in each Function Block.
536 for the Function Block itself.
544 and create a new Function Block there.  For example, to create 4
545 Groups for the Function Block of this new Endpoint::