Lines Matching full:widgets

19 DAPM is based on two basic elements, called widgets and routes:
23  * a **route** is an interconnection between widgets that exists when sound
28 the whole sound card, so some DAPM routes connect two widgets belonging to
72 DAPM Widgets
75 Audio DAPM widgets fall into a number of types:
102 	Power or clock supply widget used by other widgets.
142 (Widgets are defined in include/sound/soc-dapm.h)
144 Widgets can be added to the sound card by any of the component driver types.
146 build a list of widgets of the codecs and machines DAPM widgets.
148 Most widgets have a name, register, shift and invert. Some widgets have extra
152 Stream Domain Widgets
155 Stream Widgets relate to the stream power domain and only consist of ADCs
159 Stream widgets have the following format:
168 e.g. stream widgets for HiFi playback and capture
174 e.g. stream widgets for AIF
181 Path Domain Widgets
184 Path domain widgets have a ability to control or affect the audio signal or
210 Machine domain Widgets
213 Machine widgets are different from codec widgets in that they don't have a
239 The codec bias power domain has no widgets and is handled by the codec DAPM
244 Virtual Widgets
247 Sometimes widgets exist in the codec or machine audio graph that don't have any
259 In many cases the DAPM widgets are implemented statically in a ``static
293 In more complex cases the list of DAPM widgets and/or routes can be only
296 separate widgets and routes arrays implementing the case-specific features
304 Widgets are connected to each other within the codec, platform and machine by
306 order to create a graph of all audio paths between widgets.
309 audio system), as it requires joining widgets together via their audio signal
321 source widgets.  ::
334 When there is no path name connecting widgets (e.g. a direct connection) we
341 Finally, snd_soc_dapm_new_widgets() must be called after all widgets and
350 directly connect the codec pins to machine level widgets.
363 Endpoint Widgets
382 Widgets needing to implement a more complex behaviour than what DAPM can do
404 See soc-dapm.h for all other widgets that support events.
410 The following event types are supported by event widgets::