€•ÏC      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ&/translations/zh_CN/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/zh_TW/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/it_IT/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ja_JP/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/ko_KR/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ&/translations/sp_SP/sound/soc/overview”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒALSA SoC Layer Overview”h]”hŒALSA SoC Layer Overview”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ@/var/lib/git/docbuild/linux/Documentation/sound/soc/overview.rst”h KubhŒ	paragraph”“”)”}”(hX7  The overall project goal of the ALSA System on Chip (ASoC) layer is to
provide better ALSA support for embedded system-on-chip processors (e.g.
pxa2xx, au1x00, iMX, etc) and portable audio codecs.  Prior to the ASoC
subsystem there was some support in the kernel for SoC audio, however it
had some limitations:-”h]”hX7  The overall project goal of the ALSA System on Chip (ASoC) layer is to
provide better ALSA support for embedded system-on-chip processors (e.g.
pxa2xx, au1x00, iMX, etc) and portable audio codecs.  Prior to the ASoC
subsystem there was some support in the kernel for SoC audio, however it
had some limitations:-”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhŒblock_quote”“”)”}”(hX  * Codec drivers were often tightly coupled to the underlying SoC
  CPU. This is not ideal and leads to code duplication - for example,
  Linux had different wm8731 drivers for 4 different SoC platforms.

* There was no standard method to signal user initiated audio events (e.g.
  Headphone/Mic insertion, Headphone/Mic detection after an insertion
  event). These are quite common events on portable devices and often require
  machine specific code to re-route audio, enable amps, etc., after such an
  event.

* Drivers tended to power up the entire codec when playing (or
  recording) audio. This is fine for a PC, but tends to waste a lot of
  power on portable devices. There was also no support for saving
  power via changing codec oversampling rates, bias currents, etc.

”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒÅCodec drivers were often tightly coupled to the underlying SoC
CPU. This is not ideal and leads to code duplication - for example,
Linux had different wm8731 drivers for 4 different SoC platforms.
”h]”h¸)”}”(hŒÄCodec drivers were often tightly coupled to the underlying SoC
CPU. This is not ideal and leads to code duplication - for example,
Linux had different wm8731 drivers for 4 different SoC platforms.”h]”hŒÄCodec drivers were often tightly coupled to the underlying SoC
CPU. This is not ideal and leads to code duplication - for example,
Linux had different wm8731 drivers for 4 different SoC platforms.”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhÔubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhhÏubhÓ)”}”(hX*  There was no standard method to signal user initiated audio events (e.g.
Headphone/Mic insertion, Headphone/Mic detection after an insertion
event). These are quite common events on portable devices and often require
machine specific code to re-route audio, enable amps, etc., after such an
event.
”h]”h¸)”}”(hX)  There was no standard method to signal user initiated audio events (e.g.
Headphone/Mic insertion, Headphone/Mic detection after an insertion
event). These are quite common events on portable devices and often require
machine specific code to re-route audio, enable amps, etc., after such an
event.”h]”hX)  There was no standard method to signal user initiated audio events (e.g.
Headphone/Mic insertion, Headphone/Mic detection after an insertion
event). These are quite common events on portable devices and often require
machine specific code to re-route audio, enable amps, etc., after such an
event.”…””}”(hhðhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhìubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhhÏubhÓ)”}”(hX  Drivers tended to power up the entire codec when playing (or
recording) audio. This is fine for a PC, but tends to waste a lot of
power on portable devices. There was also no support for saving
power via changing codec oversampling rates, bias currents, etc.

”h]”h¸)”}”(hX  Drivers tended to power up the entire codec when playing (or
recording) audio. This is fine for a PC, but tends to waste a lot of
power on portable devices. There was also no support for saving
power via changing codec oversampling rates, bias currents, etc.”h]”hX  Drivers tended to power up the entire codec when playing (or
recording) audio. This is fine for a PC, but tends to waste a lot of
power on portable devices. There was also no support for saving
power via changing codec oversampling rates, bias currents, etc.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhhÏubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1hÍhŸh¶h KhhÉubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒASoC Design”h]”hŒASoC Design”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj*  hžhhŸh¶h Kubh¸)”}”(hŒXThe ASoC layer is designed to address these issues and provide the following
features :-”h]”hŒXThe ASoC layer is designed to address these issues and provide the following
features :-”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj*  hžhubhÈ)”}”(hX  * Codec independence. Allows reuse of codec drivers on other platforms
  and machines.

* Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
  interface and codec registers its audio interface capabilities with the
  core and are subsequently matched and configured when the application
  hardware parameters are known.

* Dynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
  its minimum power state at all times. This includes powering up/down
  internal power blocks depending on the internal codec audio routing and any
  active streams.

* Pop and click reduction. Pops and clicks can be reduced by powering the
  codec up/down in the correct sequence (including using digital mute). ASoC
  signals the codec when to change power states.

* Machine specific controls: Allow machines to add controls to the sound card
  (e.g. volume control for speaker amplifier).
”h]”hÎ)”}”(hhh]”(hÓ)”}”(hŒSCodec independence. Allows reuse of codec drivers on other platforms
and machines.
”h]”h¸)”}”(hŒRCodec independence. Allows reuse of codec drivers on other platforms
and machines.”h]”hŒRCodec independence. Allows reuse of codec drivers on other platforms
and machines.”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K!hjP  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubhÓ)”}”(hŒðEasy I2S/PCM audio interface setup between codec and SoC. Each SoC
interface and codec registers its audio interface capabilities with the
core and are subsequently matched and configured when the application
hardware parameters are known.
”h]”h¸)”}”(hŒïEasy I2S/PCM audio interface setup between codec and SoC. Each SoC
interface and codec registers its audio interface capabilities with the
core and are subsequently matched and configured when the application
hardware parameters are known.”h]”hŒïEasy I2S/PCM audio interface setup between codec and SoC. Each SoC
interface and codec registers its audio interface capabilities with the
core and are subsequently matched and configured when the application
hardware parameters are known.”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K$hjh  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubhÓ)”}”(hŒíDynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
its minimum power state at all times. This includes powering up/down
internal power blocks depending on the internal codec audio routing and any
active streams.
”h]”h¸)”}”(hŒìDynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
its minimum power state at all times. This includes powering up/down
internal power blocks depending on the internal codec audio routing and any
active streams.”h]”hŒìDynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
its minimum power state at all times. This includes powering up/down
internal power blocks depending on the internal codec audio routing and any
active streams.”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K)hj€  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubhÓ)”}”(hŒÂPop and click reduction. Pops and clicks can be reduced by powering the
codec up/down in the correct sequence (including using digital mute). ASoC
signals the codec when to change power states.
”h]”h¸)”}”(hŒÁPop and click reduction. Pops and clicks can be reduced by powering the
codec up/down in the correct sequence (including using digital mute). ASoC
signals the codec when to change power states.”h]”hŒÁPop and click reduction. Pops and clicks can be reduced by powering the
codec up/down in the correct sequence (including using digital mute). ASoC
signals the codec when to change power states.”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K.hj˜  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubhÓ)”}”(hŒyMachine specific controls: Allow machines to add controls to the sound card
(e.g. volume control for speaker amplifier).
”h]”h¸)”}”(hŒxMachine specific controls: Allow machines to add controls to the sound card
(e.g. volume control for speaker amplifier).”h]”hŒxMachine specific controls: Allow machines to add controls to the sound card
(e.g. volume control for speaker amplifier).”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K2hj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubeh}”(h]”h ]”h"]”h$]”h&]”j"  j#  uh1hÍhŸh¶h K!hjI  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h K!hj*  hžhubh¸)”}”(hŒpTo achieve all this, ASoC basically splits an embedded audio system into
multiple re-usable component drivers :-”h]”hŒpTo achieve all this, ASoC basically splits an embedded audio system into
multiple re-usable component drivers :-”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K5hj*  hžhubhÈ)”}”(hX2  * Codec class drivers: The codec class driver is platform independent and
  contains audio controls, audio interface capabilities, codec DAPM
  definition and codec IO functions. This class extends to BT, FM and MODEM
  ICs if required. Codec class drivers should be generic code that can run
  on any architecture and machine.

* Platform class drivers: The platform class driver includes the audio DMA
  engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
  and any audio DSP drivers for that platform.

* Machine class driver: The machine driver class acts as the glue that
  describes and binds the other component drivers together to form an ALSA
  "sound card device". It handles any machine specific controls and
  machine level audio events (e.g. turning on an amp at start of playback).”h]”hÎ)”}”(hhh]”(hÓ)”}”(hX>  Codec class drivers: The codec class driver is platform independent and
contains audio controls, audio interface capabilities, codec DAPM
definition and codec IO functions. This class extends to BT, FM and MODEM
ICs if required. Codec class drivers should be generic code that can run
on any architecture and machine.
”h]”h¸)”}”(hX=  Codec class drivers: The codec class driver is platform independent and
contains audio controls, audio interface capabilities, codec DAPM
definition and codec IO functions. This class extends to BT, FM and MODEM
ICs if required. Codec class drivers should be generic code that can run
on any architecture and machine.”h]”hX=  Codec class drivers: The codec class driver is platform independent and
contains audio controls, audio interface capabilities, codec DAPM
definition and codec IO functions. This class extends to BT, FM and MODEM
ICs if required. Codec class drivers should be generic code that can run
on any architecture and machine.”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K8hjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjæ  ubhÓ)”}”(hŒÁPlatform class drivers: The platform class driver includes the audio DMA
engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
and any audio DSP drivers for that platform.
”h]”h¸)”}”(hŒÀPlatform class drivers: The platform class driver includes the audio DMA
engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
and any audio DSP drivers for that platform.”h]”hŒÀPlatform class drivers: The platform class driver includes the audio DMA
engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
and any audio DSP drivers for that platform.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K>hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjæ  ubhÓ)”}”(hX  Machine class driver: The machine driver class acts as the glue that
describes and binds the other component drivers together to form an ALSA
"sound card device". It handles any machine specific controls and
machine level audio events (e.g. turning on an amp at start of playback).”h]”h¸)”}”(hX  Machine class driver: The machine driver class acts as the glue that
describes and binds the other component drivers together to form an ALSA
"sound card device". It handles any machine specific controls and
machine level audio events (e.g. turning on an amp at start of playback).”h]”hX  Machine class driver: The machine driver class acts as the glue that
describes and binds the other component drivers together to form an ALSA
â€œsound card deviceâ€. It handles any machine specific controls and
machine level audio events (e.g. turning on an amp at start of playback).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KBhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjæ  ubeh}”(h]”h ]”h"]”h$]”h&]”j"  j#  uh1hÍhŸh¶h K8hjâ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h K8hj*  hžhubeh}”(h]”Œasoc-design”ah ]”h"]”Œasoc design”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubeh}”(h]”Œalsa-soc-layer-overview”ah ]”h"]”Œalsa soc layer overview”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jp  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jJ  jG  jB  j?  uŒ	nametypes”}”(jJ  ‰jB  ‰uh}”(jG  h£j?  j*  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.