Lines Matching full:widgets

54 widgets hereafter.
57 DAPM Widgets
60 Audio DAPM widgets fall into a number of types:-
87 	Power or clock supply widget used by other widgets.
127 (Widgets are defined in include/sound/soc-dapm.h)
129 Widgets can be added to the sound card by any of the component driver types.
131 build a list of widgets of the codecs and machines DAPM widgets.
133 Most widgets have a name, register, shift and invert. Some widgets have extra
137 Stream Domain Widgets
140 Stream Widgets relate to the stream power domain and only consist of ADCs
144 Stream widgets have the following format:-
153 e.g. stream widgets for HiFi playback and capture
159 e.g. stream widgets for AIF
166 Path Domain Widgets
169 Path domain widgets have a ability to control or affect the audio signal or
195 Machine domain Widgets
198 Machine widgets are different from codec widgets in that they don't have a
224 The codec bias power domain has no widgets and is handled by the codecs DAPM
229 Virtual Widgets
232 Sometimes widgets exist in the codec or machine audio map that don't have any
241 After all the widgets have been defined, they can then be added to the DAPM
248 Widgets are connected to each other within the codec, platform and machine by
250 order to create a map of all audio paths between widgets.
253 audio system), as it requires joining widgets together via their audio signal
266 connect the destination widget (wrt audio signal) with its source widgets.
280 When there is no path name connecting widgets (e.g. a direct connection) we
288 Finally, snd_soc_dapm_new_widgets(codec) must be called after all widgets and
297 directly connect the codec pins to machine level widgets.
310 Endpoint Widgets
329 Some widgets can register their interest with the DAPM core in PM events.
341   /* corgi machine dapm widgets */
345 Please see soc-dapm.h for all other widgets that support events.
351 The following event types are supported by event widgets.