€•JŒsphinx.addnodes”Œdocument”“”)�”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)�”}”(hhh]”(hŒ pending_xref”“”)�”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…”�”}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ(/translations/zh_CN/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)�”}”(hhh]”hŒChinese (Traditional)”…”�”}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/zh_TW/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒItalian”…”�”}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/it_IT/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒJapanese”…”�”}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/ja_JP/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒKorean”…”�”}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/ko_KR/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒPortuguese (Brazilian)”…”�”}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/pt_BR/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒSpanish”…”�”}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/sp_SP/sound/hd-audio/notes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)�”}”(hhh]”(hŒtitle”“”)�”}”(hŒMore Notes on HD-Audio Driver”h]”hŒMore Notes on HD-Audio Driver”…”�”}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒB/var/lib/git/docbuild/linux/Documentation/sound/hd-audio/notes.rst”h´KubhŒ paragraph”“”)�”}”(hŒTakashi Iwai ”h]”(hŒTakashi Iwai <”…”�”}”(hhÍh²hh³Nh´NubhŒ reference”“”)�”}”(hŒ tiwai@suse.de”h]”hŒ tiwai@suse.de”…”�”}”(hh×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:tiwai@suse.de”uh1hÕhhÍubhŒ>”…”�”}”(hhÍh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubh¶)�”}”(hhh]”(h»)�”}”(hŒGeneral”h]”hŒGeneral”…”�”}”(hhôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhñh²hh³hÊh´K ubhÌ)�”}”(hXrHD-audio is the new standard on-board audio component on modern PCs after AC97. Although Linux has been supporting HD-audio since long time ago, there are often problems with new machines. A part of the problem is broken BIOS, and the rest is the driver implementation. This document explains the brief trouble-shooting and debugging methods for the HD-audio hardware.”h]”hXrHD-audio is the new standard on-board audio component on modern PCs after AC97. Although Linux has been supporting HD-audio since long time ago, there are often problems with new machines. A part of the problem is broken BIOS, and the rest is the driver implementation. This document explains the brief trouble-shooting and debugging methods for the HD-audio hardware.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hhñh²hubhÌ)�”}”(hXcThe HD-audio component consists of two parts: the controller chip and the codec chips on the HD-audio bus. Linux provides a single driver for all controllers, snd-hda-intel. Although the driver name contains a word of a well-known hardware vendor, it's not specific to it but for all controller chips by other companies. Since the HD-audio controllers are supposed to be compatible, the single snd-hda-driver should work in most cases. But, not surprisingly, there are known bugs and issues specific to each controller type. The snd-hda-intel driver has a bunch of workarounds for these as described below.”h]”hXeThe HD-audio component consists of two parts: the controller chip and the codec chips on the HD-audio bus. Linux provides a single driver for all controllers, snd-hda-intel. Although the driver name contains a word of a well-known hardware vendor, it’s not specific to it but for all controller chips by other companies. Since the HD-audio controllers are supposed to be compatible, the single snd-hda-driver should work in most cases. But, not surprisingly, there are known bugs and issues specific to each controller type. The snd-hda-intel driver has a bunch of workarounds for these as described below.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khhñh²hubhÌ)�”}”(hXLA controller may have multiple codecs. Usually you have one audio codec and optionally one modem codec. In theory, there might be multiple audio codecs, e.g. for analog and digital outputs, and the driver might not work properly because of conflict of mixer elements. This should be fixed in future if such hardware really exists.”h]”hXLA controller may have multiple codecs. Usually you have one audio codec and optionally one modem codec. In theory, there might be multiple audio codecs, e.g. for analog and digital outputs, and the driver might not work properly because of conflict of mixer elements. This should be fixed in future if such hardware really exists.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khhñh²hubhÌ)�”}”(hX‹The snd-hda-intel driver has several different codec parsers depending on the codec. It has a generic parser as a fallback, but this functionality is fairly limited until now. Instead of the generic parser, usually the codec-specific parser (coded in patch_*.c) is used for the codec-specific implementations. The details about the codec-specific problems are explained in the later sections.”h]”hX‹The snd-hda-intel driver has several different codec parsers depending on the codec. It has a generic parser as a fallback, but this functionality is fairly limited until now. Instead of the generic parser, usually the codec-specific parser (coded in patch_*.c) is used for the codec-specific implementations. The details about the codec-specific problems are explained in the later sections.”…”�”}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K"hhñh²hubhÌ)�”}”(hŒ If you are interested in the deep debugging of HD-audio, read the HD-audio specification at first. The specification is found on Intel's web page, for example:”h]”hŒ¢If you are interested in the deep debugging of HD-audio, read the HD-audio specification at first. The specification is found on Intel’s web page, for example:”…”�”}”(hj:h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K)hhñh²hubhŒ bullet_list”“”)�”}”(hhh]”hŒ list_item”“”)�”}”(hŒ}https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf ”h]”hÌ)�”}”(hŒ{https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf”h]”hÖ)�”}”(hjUh]”hŒ{https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf”…”�”}”(hjWh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jUuh1hÕhjSubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K-hjOubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjJh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1jHh³hÊh´K-hhñh²hubeh}”(h]”Œgeneral”ah ]”h"]”Œgeneral”ah$]”h&]”uh1hµhh·h²hh³hÊh´K ubh¶)�”}”(hhh]”(h»)�”}”(hŒHD-Audio Controller”h]”hŒHD-Audio Controller”…”�”}”(hj„h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj�h²hh³hÊh´K1ubh¶)�”}”(hhh]”(h»)�”}”(hŒDMA-Position Problem”h]”hŒDMA-Position Problem”…”�”}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj’h²hh³hÊh´K4ubhÌ)�”}”(hXÛThe most common problem of the controller is the inaccurate DMA pointer reporting. The DMA pointer for playback and capture can be read in two ways, either via a LPIB register or via a position-buffer map. As default the driver tries to read from the io-mapped position-buffer, and falls back to LPIB if the position-buffer appears dead. However, this detection isn't perfect on some devices. In such a case, you can change the default method via ``position_fix`` option.”h]”(hXÅThe most common problem of the controller is the inaccurate DMA pointer reporting. The DMA pointer for playback and capture can be read in two ways, either via a LPIB register or via a position-buffer map. As default the driver tries to read from the io-mapped position-buffer, and falls back to LPIB if the position-buffer appears dead. However, this detection isn’t perfect on some devices. In such a case, you can change the default method via ”…”�”}”(hj£h²hh³Nh´NubhŒliteral”“”)�”}”(hŒ``position_fix``”h]”hŒ position_fix”…”�”}”(hj­h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj£ubhŒ option.”…”�”}”(hj£h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K5hj’h²hubhÌ)�”}”(hX‹``position_fix=1`` means to use LPIB method explicitly. ``position_fix=2`` means to use the position-buffer. ``position_fix=3`` means to use a combination of both methods, needed for some VIA controllers. The capture stream position is corrected by comparing both LPIB and position-buffer values. ``position_fix=4`` is another combination available for all controllers, and uses LPIB for the playback and the position-buffer for the capture streams. ``position_fix=5`` is specific to Intel platforms, so far, for Skylake and onward. It applies the delay calculation for the precise position reporting. ``position_fix=6`` is to correct the position with the fixed FIFO size, mainly targeted for the recent AMD controllers. 0 is the default value for all other controllers, the automatic check and fallback to LPIB as described in the above. If you get a problem of repeated sounds, this option might help.”h]”(j¬)�”}”(hŒ``position_fix=1``”h]”hŒposition_fix=1”…”�”}”(hjÉh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhŒ& means to use LPIB method explicitly. ”…”�”}”(hjÅh²hh³Nh´Nubj¬)�”}”(hŒ``position_fix=2``”h]”hŒposition_fix=2”…”�”}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhŒ# means to use the position-buffer. ”…”�”}”(hjÅh²hh³Nh´Nubj¬)�”}”(hŒ``position_fix=3``”h]”hŒposition_fix=3”…”�”}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhŒ« means to use a combination of both methods, needed for some VIA controllers. The capture stream position is corrected by comparing both LPIB and position-buffer values. ”…”�”}”(hjÅh²hh³Nh´Nubj¬)�”}”(hŒ``position_fix=4``”h]”hŒposition_fix=4”…”�”}”(hjÿh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhŒ‡ is another combination available for all controllers, and uses LPIB for the playback and the position-buffer for the capture streams. ”…”�”}”(hjÅh²hh³Nh´Nubj¬)�”}”(hŒ``position_fix=5``”h]”hŒposition_fix=5”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhŒ‡ is specific to Intel platforms, so far, for Skylake and onward. It applies the delay calculation for the precise position reporting. ”…”�”}”(hjÅh²hh³Nh´Nubj¬)�”}”(hŒ``position_fix=6``”h]”hŒposition_fix=6”…”�”}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÅubhX is to correct the position with the fixed FIFO size, mainly targeted for the recent AMD controllers. 0 is the default value for all other controllers, the automatic check and fallback to LPIB as described in the above. If you get a problem of repeated sounds, this option might help.”…”�”}”(hjÅh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K=hj’h²hubhÌ)�”}”(hXsIn addition to that, every controller is known to be broken regarding the wake-up timing. It wakes up a few samples before actually processing the data on the buffer. This caused a lot of problems, for example, with ALSA dmix or JACK. Since 2.6.27 kernel, the driver puts an artificial delay to the wake up timing. This delay is controlled via ``bdl_pos_adj`` option.”h]”(hX\In addition to that, every controller is known to be broken regarding the wake-up timing. It wakes up a few samples before actually processing the data on the buffer. This caused a lot of problems, for example, with ALSA dmix or JACK. Since 2.6.27 kernel, the driver puts an artificial delay to the wake up timing. This delay is controlled via ”…”�”}”(hj;h²hh³Nh´Nubj¬)�”}”(hŒ``bdl_pos_adj``”h]”hŒ bdl_pos_adj”…”�”}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj;ubhŒ option.”…”�”}”(hj;h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KOhj’h²hubhÌ)�”}”(hX9When ``bdl_pos_adj`` is a negative value (as default), it's assigned to an appropriate value depending on the controller chip. For Intel chips, it'd be 1 while it'd be 32 for others. Usually this works. Only in case it doesn't work and you get warning messages, you should change this parameter to other values.”h]”(hŒWhen ”…”�”}”(hj[h²hh³Nh´Nubj¬)�”}”(hŒ``bdl_pos_adj``”h]”hŒ bdl_pos_adj”…”�”}”(hjch²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj[ubhX- is a negative value (as default), it’s assigned to an appropriate value depending on the controller chip. For Intel chips, it’d be 1 while it’d be 32 for others. Usually this works. Only in case it doesn’t work and you get warning messages, you should change this parameter to other values.”…”�”}”(hj[h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KVhj’h²hubeh}”(h]”Œdma-position-problem”ah ]”h"]”Œdma-position problem”ah$]”h&]”uh1hµhj�h²hh³hÊh´K4ubh¶)�”}”(hhh]”(h»)�”}”(hŒCodec-Probing Problem”h]”hŒCodec-Probing Problem”…”�”}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjƒh²hh³hÊh´K^ubhÌ)�”}”(hX]A less often but a more severe problem is the codec probing. When BIOS reports the available codec slots wrongly, the driver gets confused and tries to access the non-existing codec slot. This often results in the total screw-up, and destructs the further communication with the codec chips. The symptom appears usually as error messages like: ::”h]”hXZA less often but a more severe problem is the codec probing. When BIOS reports the available codec slots wrongly, the driver gets confused and tries to access the non-existing codec slot. This often results in the total screw-up, and destructs the further communication with the codec chips. The symptom appears usually as error messages like:”…”�”}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K_hjƒh²hubhŒ literal_block”“”)�”}”(hŒ¶hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x12345678 hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x12345678”h]”hŒ¶hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x12345678 hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x12345678”…”�”}”hj¤sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j¢h³hÊh´Kghjƒh²hubhÌ)�”}”(hXThe first line is a warning, and this is usually relatively harmless. It means that the codec response isn't notified via an IRQ. The driver uses explicit polling method to read the response. It gives very slight CPU overhead, but you'd unlikely notice it.”h]”hXThe first line is a warning, and this is usually relatively harmless. It means that the codec response isn’t notified via an IRQ. The driver uses explicit polling method to read the response. It gives very slight CPU overhead, but you’d unlikely notice it.”…”�”}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Klhjƒh²hubhÌ)�”}”(hŒ¨The second line is, however, a fatal error. If this happens, usually it means that something is really wrong. Most likely you are accessing a non-existing codec slot.”h]”hŒ¨The second line is, however, a fatal error. If this happens, usually it means that something is really wrong. Most likely you are accessing a non-existing codec slot.”…”�”}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kqhjƒh²hubhÌ)�”}”(hXBThus, if the second error message appears, try to narrow the probed codec slots via ``probe_mask`` option. It's a bitmask, and each bit corresponds to the codec slot. For example, to probe only the first slot, pass ``probe_mask=1``. For the first and the third slots, pass ``probe_mask=5`` (where 5 = 1 | 4), and so on.”h]”(hŒTThus, if the second error message appears, try to narrow the probed codec slots via ”…”�”}”(hjÐh²hh³Nh´Nubj¬)�”}”(hŒ``probe_mask``”h]”hŒ probe_mask”…”�”}”(hjØh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÐubhŒy option. It’s a bitmask, and each bit corresponds to the codec slot. For example, to probe only the first slot, pass ”…”�”}”(hjÐh²hh³Nh´Nubj¬)�”}”(hŒ``probe_mask=1``”h]”hŒ probe_mask=1”…”�”}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÐubhŒ+. For the first and the third slots, pass ”…”�”}”(hjÐh²hh³Nh´Nubj¬)�”}”(hŒ``probe_mask=5``”h]”hŒ probe_mask=5”…”�”}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÐubhŒ (where 5 = 1 | 4), and so on.”…”�”}”(hjÐh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kuhjƒh²hubhÌ)�”}”(hŒlSince 2.6.29 kernel, the driver has a more robust probing method, so this error might happen rarely, though.”h]”hŒlSince 2.6.29 kernel, the driver has a more robust probing method, so this error might happen rarely, though.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K{hjƒh²hubhÌ)�”}”(hXŠOn a machine with a broken BIOS, sometimes you need to force the driver to probe the codec slots the hardware doesn't report for use. In such a case, turn the bit 8 (0x100) of ``probe_mask`` option on. Then the rest 8 bits are passed as the codec slots to probe unconditionally. For example, ``probe_mask=0x103`` will force to probe the codec slots 0 and 1 no matter what the hardware reports.”h]”(hŒ²On a machine with a broken BIOS, sometimes you need to force the driver to probe the codec slots the hardware doesn’t report for use. In such a case, turn the bit 8 (0x100) of ”…”�”}”(hj"h²hh³Nh´Nubj¬)�”}”(hŒ``probe_mask``”h]”hŒ probe_mask”…”�”}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj"ubhŒg option on. Then the rest 8 bits are passed as the codec slots to probe unconditionally. For example, ”…”�”}”(hj"h²hh³Nh´Nubj¬)�”}”(hŒ``probe_mask=0x103``”h]”hŒprobe_mask=0x103”…”�”}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj"ubhŒQ will force to probe the codec slots 0 and 1 no matter what the hardware reports.”…”�”}”(hj"h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K~hjƒh²hubeh}”(h]”Œcodec-probing-problem”ah ]”h"]”Œcodec-probing problem”ah$]”h&]”uh1hµhj�h²hh³hÊh´K^ubh¶)�”}”(hhh]”(h»)�”}”(hŒInterrupt Handling”h]”hŒInterrupt Handling”…”�”}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj\h²hh³hÊh´K‡ubhÌ)�”}”(hX%HD-audio driver uses MSI as default (if available) since 2.6.33 kernel as MSI works better on some machines, and in general, it's better for performance. However, Nvidia controllers showed bad regressions with MSI (especially in a combination with AMD chipset), thus we disabled MSI for them.”h]”hX'HD-audio driver uses MSI as default (if available) since 2.6.33 kernel as MSI works better on some machines, and in general, it’s better for performance. However, Nvidia controllers showed bad regressions with MSI (especially in a combination with AMD chipset), thus we disabled MSI for them.”…”�”}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kˆhj\h²hubhÌ)�”}”(hXThere seem also still other devices that don't work with MSI. If you see a regression wrt the sound quality (stuttering, etc) or a lock-up in the recent kernel, try to pass ``enable_msi=0`` option to disable MSI. If it works, you can add the known bad device to the blacklist defined in hda_intel.c. In such a case, please report and give the patch back to the upstream developer.”h]”(hŒ°There seem also still other devices that don’t work with MSI. If you see a regression wrt the sound quality (stuttering, etc) or a lock-up in the recent kernel, try to pass ”…”�”}”(hj{h²hh³Nh´Nubj¬)�”}”(hŒ``enable_msi=0``”h]”hŒ enable_msi=0”…”�”}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj{ubhŒÁ option to disable MSI. If it works, you can add the known bad device to the blacklist defined in hda_intel.c. In such a case, please report and give the patch back to the upstream developer.”…”�”}”(hj{h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KŽhj\h²hubeh}”(h]”Œinterrupt-handling”ah ]”h"]”Œinterrupt handling”ah$]”h&]”uh1hµhj�h²hh³hÊh´K‡ubeh}”(h]”Œhd-audio-controller”ah ]”h"]”Œhd-audio controller”ah$]”h&]”uh1hµhh·h²hh³hÊh´K1ubh¶)�”}”(hhh]”(h»)�”}”(hŒHD-Audio Codec”h]”hŒHD-Audio Codec”…”�”}”(hj®h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj«h²hh³hÊh´K—ubh¶)�”}”(hhh]”(h»)�”}”(hŒ Model Option”h]”hŒ Model Option”…”�”}”(hj¿h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj¼h²hh³hÊh´KšubhÌ)�”}”(hXThe most common problem regarding the HD-audio driver is the unsupported codec features or the mismatched device configuration. Most of codec-specific code has several preset models, either to override the BIOS setup or to provide more comprehensive features.”h]”hXThe most common problem regarding the HD-audio driver is the unsupported codec features or the mismatched device configuration. Most of codec-specific code has several preset models, either to override the BIOS setup or to provide more comprehensive features.”…”�”}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K›hj¼h²hubhÌ)�”}”(hŒ¯The driver checks PCI SSID and looks through the static configuration table until any matching entry is found. If you have a new machine, you may see a message like below: ::”h]”hŒ¬The driver checks PCI SSID and looks through the static configuration table until any matching entry is found. If you have a new machine, you may see a message like below:”…”�”}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hj¼h²hubj£)�”}”(hŒ%hda_codec: ALC880: BIOS auto-probing.”h]”hŒ%hda_codec: ALC880: BIOS auto-probing.”…”�”}”hjésbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´K¥hj¼h²hubhÌ)�”}”(hŒDMeanwhile, in the earlier versions, you would see a message like: ::”h]”hŒAMeanwhile, in the earlier versions, you would see a message like:”…”�”}”(hj÷h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K§hj¼h²hubj£)�”}”(hŒChda_codec: Unknown model for ALC880, trying auto-probe from BIOS...”h]”hŒChda_codec: Unknown model for ALC880, trying auto-probe from BIOS...”…”�”}”hjsbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´Kªhj¼h²hubhÌ)�”}”(hX‰Even if you see such a message, DON'T PANIC. Take a deep breath and keep your towel. First of all, it's an informational message, no warning, no error. This means that the PCI SSID of your device isn't listed in the known preset model (white-)list. But, this doesn't mean that the driver is broken. Many codec-drivers provide the automatic configuration mechanism based on the BIOS setup.”h]”hX‘Even if you see such a message, DON’T PANIC. Take a deep breath and keep your towel. First of all, it’s an informational message, no warning, no error. This means that the PCI SSID of your device isn’t listed in the known preset model (white-)list. But, this doesn’t mean that the driver is broken. Many codec-drivers provide the automatic configuration mechanism based on the BIOS setup.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¬hj¼h²hubhÌ)�”}”(hXæThe HD-audio codec has usually "pin" widgets, and BIOS sets the default configuration of each pin, which indicates the location, the connection type, the jack color, etc. The HD-audio driver can guess the right connection judging from these default configuration values. However -- some codec-support codes, such as patch_analog.c, don't support the automatic probing (yet as of 2.6.28). And, BIOS is often, yes, pretty often broken. It sets up wrong values and screws up the driver.”h]”hXìThe HD-audio codec has usually “pinâ€� widgets, and BIOS sets the default configuration of each pin, which indicates the location, the connection type, the jack color, etc. The HD-audio driver can guess the right connection judging from these default configuration values. However -- some codec-support codes, such as patch_analog.c, don’t support the automatic probing (yet as of 2.6.28). And, BIOS is often, yes, pretty often broken. It sets up wrong values and screws up the driver.”…”�”}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K³hj¼h²hubhÌ)�”}”(hXThe preset model (or recently called as "fix-up") is provided basically to overcome such a situation. When the matching preset model is found in the white-list, the driver assumes the static configuration of that preset with the correct pin setup, etc. Thus, if you have a newer machine with a slightly different PCI SSID (or codec SSID) from the existing one, you may have a good chance to reuse the same model. You can pass the ``model`` option to specify the preset model instead of PCI (and codec-) SSID look-up.”h]”(hX´The preset model (or recently called as “fix-upâ€�) is provided basically to overcome such a situation. When the matching preset model is found in the white-list, the driver assumes the static configuration of that preset with the correct pin setup, etc. Thus, if you have a newer machine with a slightly different PCI SSID (or codec SSID) from the existing one, you may have a good chance to reuse the same model. You can pass the ”…”�”}”(hj/h²hh³Nh´Nubj¬)�”}”(hŒ ``model``”h]”hŒmodel”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj/ubhŒM option to specify the preset model instead of PCI (and codec-) SSID look-up.”…”�”}”(hj/h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¼hj¼h²hubhÌ)�”}”(hXõWhat ``model`` option values are available depends on the codec chip. Check your codec chip from the codec proc file (see "Codec Proc-File" section below). It will show the vendor/product name of your codec chip. Then, see Documentation/sound/hd-audio/models.rst file, the section of HD-audio driver. You can find a list of codecs and ``model`` options belonging to each codec. For example, for Realtek ALC262 codec chip, pass ``model=ultra`` for devices that are compatible with Samsung Q1 Ultra.”h]”(hŒWhat ”…”�”}”(hjOh²hh³Nh´Nubj¬)�”}”(hŒ ``model``”h]”hŒmodel”…”�”}”(hjWh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjOubhXH option values are available depends on the codec chip. Check your codec chip from the codec proc file (see “Codec Proc-Fileâ€� section below). It will show the vendor/product name of your codec chip. Then, see Documentation/sound/hd-audio/models.rst file, the section of HD-audio driver. You can find a list of codecs and ”…”�”}”(hjOh²hh³Nh´Nubj¬)�”}”(hŒ ``model``”h]”hŒmodel”…”�”}”(hjih²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjOubhŒT options belonging to each codec. For example, for Realtek ALC262 codec chip, pass ”…”�”}”(hjOh²hh³Nh´Nubj¬)�”}”(hŒ``model=ultra``”h]”hŒ model=ultra”…”�”}”(hj{h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjOubhŒ7 for devices that are compatible with Samsung Q1 Ultra.”…”�”}”(hjOh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÅhj¼h²hubhÌ)�”}”(hŒñThus, the first thing you can do for any brand-new, unsupported and non-working HD-audio hardware is to check HD-audio codec and several different ``model`` option values. If you have any luck, some of them might suit with your device well.”h]”(hŒ“Thus, the first thing you can do for any brand-new, unsupported and non-working HD-audio hardware is to check HD-audio codec and several different ”…”�”}”(hj“h²hh³Nh´Nubj¬)�”}”(hŒ ``model``”h]”hŒmodel”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj“ubhŒU option values. If you have any luck, some of them might suit with your device well.”…”�”}”(hj“h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÎhj¼h²hubhÌ)�”}”(hŒ,There are a few special model option values:”h]”hŒ,There are a few special model option values:”…”�”}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÓhj¼h²hubjI)�”}”(hhh]”(jN)�”}”(hŒUwhen 'nofixup' is passed, the device-specific fixups in the codec parser are skipped.”h]”hÌ)�”}”(hŒUwhen 'nofixup' is passed, the device-specific fixups in the codec parser are skipped.”h]”hŒYwhen ‘nofixup’ is passed, the device-specific fixups in the codec parser are skipped.”…”�”}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÕhjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjÁh²hh³hÊh´NubjN)�”}”(hŒfwhen ``generic`` is passed, the codec-specific parser is skipped and only the generic parser is used. ”h]”hÌ)�”}”(hŒewhen ``generic`` is passed, the codec-specific parser is skipped and only the generic parser is used.”h]”(hŒwhen ”…”�”}”(hjàh²hh³Nh´Nubj¬)�”}”(hŒ ``generic``”h]”hŒgeneric”…”�”}”(hjèh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjàubhŒU is passed, the codec-specific parser is skipped and only the generic parser is used.”…”�”}”(hjàh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K×hjÜubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjÁh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´KÕhj¼h²hubhÌ)�”}”(hXŠA new style for the model option that was introduced since 5.15 kernel is to pass the PCI or codec SSID in the form of ``model=XXXX:YYYY`` where XXXX and YYYY are the sub-vendor and sub-device IDs in hex numbers, respectively. This is a kind of aliasing to another device; when this form is given, the driver will refer to that SSID as a reference to the quirk table. It'd be useful especially when the target quirk isn't listed in the model table. For example, passing model=103c:8862 will apply the quirk for HP ProBook 445 G8 (which isn't found in the model table as of writing) as long as the device is handled equivalently by the same driver.”h]”(hŒwA new style for the model option that was introduced since 5.15 kernel is to pass the PCI or codec SSID in the form of ”…”�”}”(hj h²hh³Nh´Nubj¬)�”}”(hŒ``model=XXXX:YYYY``”h]”hŒmodel=XXXX:YYYY”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj ubhX where XXXX and YYYY are the sub-vendor and sub-device IDs in hex numbers, respectively. This is a kind of aliasing to another device; when this form is given, the driver will refer to that SSID as a reference to the quirk table. It’d be useful especially when the target quirk isn’t listed in the model table. For example, passing model=103c:8862 will apply the quirk for HP ProBook 445 G8 (which isn’t found in the model table as of writing) as long as the device is handled equivalently by the same driver.”…”�”}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KÚhj¼h²hubeh}”(h]”Œ model-option”ah ]”h"]”Œ model option”ah$]”h&]”uh1hµhj«h²hh³hÊh´Kšubh¶)�”}”(hhh]”(h»)�”}”(hŒSpeaker and Headphone Output”h]”hŒSpeaker and Headphone Output”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj4h²hh³hÊh´KçubhÌ)�”}”(hXZOne of the most frequent (and obvious) bugs with HD-audio is the silent output from either or both of a built-in speaker and a headphone jack. In general, you should try a headphone output at first. A speaker output often requires more additional controls like the external amplifier bits. Thus a headphone output has a slightly better chance.”h]”hXZOne of the most frequent (and obvious) bugs with HD-audio is the silent output from either or both of a built-in speaker and a headphone jack. In general, you should try a headphone output at first. A speaker output often requires more additional controls like the external amplifier bits. Thus a headphone output has a slightly better chance.”…”�”}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kèhj4h²hubhÌ)�”}”(hX3Before making a bug report, double-check whether the mixer is set up correctly. The recent version of snd-hda-intel driver provides mostly "Master" volume control as well as "Front" volume (where Front indicates the front-channels). In addition, there can be individual "Headphone" and "Speaker" controls.”h]”hXCBefore making a bug report, double-check whether the mixer is set up correctly. The recent version of snd-hda-intel driver provides mostly “Masterâ€� volume control as well as “Frontâ€� volume (where Front indicates the front-channels). In addition, there can be individual “Headphoneâ€� and “Speakerâ€� controls.”…”�”}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kïhj4h²hubhÌ)�”}”(hŒqDitto for the speaker output. There can be "External Amplifier" switch on some codecs. Turn on this if present.”h]”hŒuDitto for the speaker output. There can be “External Amplifierâ€� switch on some codecs. Turn on this if present.”…”�”}”(hjah²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kõhj4h²hubhÌ)�”}”(hŒ·Another related problem is the automatic mute of speaker output by headphone plugging. This feature is implemented in most cases, but not on every preset model or codec-support code.”h]”hŒ·Another related problem is the automatic mute of speaker output by headphone plugging. This feature is implemented in most cases, but not on every preset model or codec-support code.”…”�”}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Køhj4h²hubhÌ)�”}”(hŒôIn anyway, try a different model option if you have such a problem. Some other models may match better and give you more matching functionality. If none of the available models works, send a bug report. See the bug report section for details.”h]”hŒôIn anyway, try a different model option if you have such a problem. Some other models may match better and give you more matching functionality. If none of the available models works, send a bug report. See the bug report section for details.”…”�”}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kühj4h²hubhÌ)�”}”(hŒNIf you are masochistic enough to debug the driver problem, note the following:”h]”hŒNIf you are masochistic enough to debug the driver problem, note the following:”…”�”}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj4h²hubjI)�”}”(hhh]”(jN)�”}”(hX4The speaker (and the headphone, too) output often requires the external amplifier. This can be set usually via EAPD verb or a certain GPIO. If the codec pin supports EAPD, you have a better chance via SET_EAPD_BTL verb (0x70c). On others, GPIO pin (mostly it's either GPIO0 or GPIO1) may turn on/off EAPD.”h]”hÌ)�”}”(hX4The speaker (and the headphone, too) output often requires the external amplifier. This can be set usually via EAPD verb or a certain GPIO. If the codec pin supports EAPD, you have a better chance via SET_EAPD_BTL verb (0x70c). On others, GPIO pin (mostly it's either GPIO0 or GPIO1) may turn on/off EAPD.”h]”hX6The speaker (and the headphone, too) output often requires the external amplifier. This can be set usually via EAPD verb or a certain GPIO. If the codec pin supports EAPD, you have a better chance via SET_EAPD_BTL verb (0x70c). On others, GPIO pin (mostly it’s either GPIO0 or GPIO1) may turn on/off EAPD.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjœubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj™h²hh³hÊh´NubjN)�”}”(hŒpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.”h]”hÌ)�”}”(hŒpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.”h]”hŒpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.”…”�”}”(hj¸h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj´ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj™h²hh³hÊh´NubjN)�”}”(hŒbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.”h]”hÌ)�”}”(hŒbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.”h]”hŒbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.”…”�”}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hjÌubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj™h²hh³hÊh´NubjN)�”}”(hŒÏVery rare but some devices don't accept the pin-detection verb until triggered. Issuing GET_PIN_SENSE verb (0xf09) may result in the codec-communication stall. Some examples are found in patch_realtek.c. ”h]”hÌ)�”}”(hŒÍVery rare but some devices don't accept the pin-detection verb until triggered. Issuing GET_PIN_SENSE verb (0xf09) may result in the codec-communication stall. Some examples are found in patch_realtek.c.”h]”hŒÏVery rare but some devices don’t accept the pin-detection verb until triggered. Issuing GET_PIN_SENSE verb (0xf09) may result in the codec-communication stall. Some examples are found in patch_realtek.c.”…”�”}”(hjèh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hjäubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj™h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´Mhj4h²hubeh}”(h]”Œspeaker-and-headphone-output”ah ]”h"]”Œspeaker and headphone output”ah$]”h&]”uh1hµhj«h²hh³hÊh´Kçubh¶)�”}”(hhh]”(h»)�”}”(hŒCapture Problems”h]”hŒCapture Problems”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj h²hh³hÊh´MubhÌ)�”}”(hXaThe capture problems are often because of missing setups of mixers. Thus, before submitting a bug report, make sure that you set up the mixer correctly. For example, both "Capture Volume" and "Capture Switch" have to be set properly in addition to the right "Capture Source" or "Input Source" selection. Some devices have "Mic Boost" volume or switch.”h]”hXuThe capture problems are often because of missing setups of mixers. Thus, before submitting a bug report, make sure that you set up the mixer correctly. For example, both “Capture Volumeâ€� and “Capture Switchâ€� have to be set properly in addition to the right “Capture Sourceâ€� or “Input Sourceâ€� selection. Some devices have “Mic Boostâ€� volume or switch.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj h²hubhÌ)�”}”(hXWhen the PCM device is opened via "default" PCM (without pulse-audio plugin), you'll likely have "Digital Capture Volume" control as well. This is provided for the extra gain/attenuation of the signal in software, especially for the inputs without the hardware volume control such as digital microphones. Unless really needed, this should be set to exactly 50%, corresponding to 0dB -- neither extra gain nor attenuation. When you use "hw" PCM, i.e., a raw access PCM, this control will have no influence, though.”h]”hXWhen the PCM device is opened via “defaultâ€� PCM (without pulse-audio plugin), you’ll likely have “Digital Capture Volumeâ€� control as well. This is provided for the extra gain/attenuation of the signal in software, especially for the inputs without the hardware volume control such as digital microphones. Unless really needed, this should be set to exactly 50%, corresponding to 0dB -- neither extra gain nor attenuation. When you use “hwâ€� PCM, i.e., a raw access PCM, this control will have no influence, though.”…”�”}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhj h²hubhÌ)�”}”(hŒšIt's known that some codecs / devices have fairly bad analog circuits, and the recorded sound contains a certain DC-offset. This is no bug of the driver.”h]”hŒœIt’s known that some codecs / devices have fairly bad analog circuits, and the recorded sound contains a certain DC-offset. This is no bug of the driver.”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M%hj h²hubhÌ)�”}”(hŒÀMost of modern laptops have no analog CD-input connection. Thus, the recording from CD input won't work in many cases although the driver provides it as the capture source. Use CDDA instead.”h]”hŒÂMost of modern laptops have no analog CD-input connection. Thus, the recording from CD input won’t work in many cases although the driver provides it as the capture source. Use CDDA instead.”…”�”}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M)hj h²hubhÌ)�”}”(hŒöThe automatic switching of the built-in and external mic per plugging is implemented on some codec models but not on every model. Partly because of my laziness but mostly lack of testers. Feel free to submit the improvement patch to the author.”h]”hŒöThe automatic switching of the built-in and external mic per plugging is implemented on some codec models but not on every model. Partly because of my laziness but mostly lack of testers. Feel free to submit the improvement patch to the author.”…”�”}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M-hj h²hubeh}”(h]”Œcapture-problems”ah ]”h"]”Œcapture problems”ah$]”h&]”uh1hµhj«h²hh³hÊh´Mubh¶)�”}”(hhh]”(h»)�”}”(hŒDirect Debugging”h]”hŒDirect Debugging”…”�”}”(hjlh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjih²hh³hÊh´M4ubhÌ)�”}”(hXiIf no model option gives you a better result, and you are a tough guy to fight against evil, try debugging via hitting the raw HD-audio codec verbs to the device. Some tools are available: hda-emu and hda-analyzer. The detailed description is found in the sections below. You'd need to enable hwdep for using these tools. See "Kernel Configuration" section.”h]”hXoIf no model option gives you a better result, and you are a tough guy to fight against evil, try debugging via hitting the raw HD-audio codec verbs to the device. Some tools are available: hda-emu and hda-analyzer. The detailed description is found in the sections below. You’d need to enable hwdep for using these tools. See “Kernel Configurationâ€� section.”…”�”}”(hjzh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M5hjih²hubeh}”(h]”Œdirect-debugging”ah ]”h"]”Œdirect debugging”ah$]”h&]”uh1hµhj«h²hh³hÊh´M4ubeh}”(h]”Œhd-audio-codec”ah ]”h"]”Œhd-audio codec”ah$]”h&]”uh1hµhh·h²hh³hÊh´K—ubh¶)�”}”(hhh]”(h»)�”}”(hŒ Other Issues”h]”hŒ Other Issues”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj˜h²hh³hÊh´M>ubh¶)�”}”(hhh]”(h»)�”}”(hŒKernel Configuration”h]”hŒKernel Configuration”…”�”}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj©h²hh³hÊh´MAubhÌ)�”}”(hŒ�In general, I recommend you to enable the sound debug option, ``CONFIG_SND_DEBUG=y``, no matter whether you are debugging or not.”h]”(hŒ>In general, I recommend you to enable the sound debug option, ”…”�”}”(hjºh²hh³Nh´Nubj¬)�”}”(hŒ``CONFIG_SND_DEBUG=y``”h]”hŒCONFIG_SND_DEBUG=y”…”�”}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjºubhŒ-, no matter whether you are debugging or not.”…”�”}”(hjºh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhj©h²hubhÌ)�”}”(hX+Don't forget to turn on the appropriate ``CONFIG_SND_HDA_CODEC_*`` options. Note that each of them corresponds to the codec chip, not the controller chip. Thus, even if lspci shows the Nvidia controller, you may need to choose the option for other vendors. If you are unsure, just select all yes.”h]”(hŒ*Don’t forget to turn on the appropriate ”…”�”}”(hjÚh²hh³Nh´Nubj¬)�”}”(hŒ``CONFIG_SND_HDA_CODEC_*``”h]”hŒCONFIG_SND_HDA_CODEC_*”…”�”}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÚubhŒé options. Note that each of them corresponds to the codec chip, not the controller chip. Thus, even if lspci shows the Nvidia controller, you may need to choose the option for other vendors. If you are unsure, just select all yes.”…”�”}”(hjÚh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MEhj©h²hubhÌ)�”}”(hX»``CONFIG_SND_HDA_HWDEP`` is a useful option for debugging the driver. When this is enabled, the driver creates hardware-dependent devices (one per each codec), and you have a raw access to the device via these device files. For example, ``hwC0D2`` will be created for the codec slot #2 of the first card (#0). For debug-tools such as hda-verb and hda-analyzer, the hwdep device has to be enabled. Thus, it'd be better to turn this on always.”h]”(j¬)�”}”(hŒ``CONFIG_SND_HDA_HWDEP``”h]”hŒCONFIG_SND_HDA_HWDEP”…”�”}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjúubhŒÖ is a useful option for debugging the driver. When this is enabled, the driver creates hardware-dependent devices (one per each codec), and you have a raw access to the device via these device files. For example, ”…”�”}”(hjúh²hh³Nh´Nubj¬)�”}”(hŒ ``hwC0D2``”h]”hŒhwC0D2”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjúubhŒÅ will be created for the codec slot #2 of the first card (#0). For debug-tools such as hda-verb and hda-analyzer, the hwdep device has to be enabled. Thus, it’d be better to turn this on always.”…”�”}”(hjúh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MKhj©h²hubhÌ)�”}”(hŒÜ``CONFIG_SND_HDA_RECONFIG`` is a new option, and this depends on the hwdep option above. When enabled, you'll have some sysfs files under the corresponding hwdep directory. See "HD-audio reconfiguration" section below.”h]”(j¬)�”}”(hŒ``CONFIG_SND_HDA_RECONFIG``”h]”hŒCONFIG_SND_HDA_RECONFIG”…”�”}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj(ubhŒÇ is a new option, and this depends on the hwdep option above. When enabled, you’ll have some sysfs files under the corresponding hwdep directory. See “HD-audio reconfigurationâ€� section below.”…”�”}”(hj(h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MShj©h²hubhÌ)�”}”(hŒh``CONFIG_SND_HDA_POWER_SAVE`` option enables the power-saving feature. See "Power-saving" section below.”h]”(j¬)�”}”(hŒ``CONFIG_SND_HDA_POWER_SAVE``”h]”hŒCONFIG_SND_HDA_POWER_SAVE”…”�”}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjDubhŒO option enables the power-saving feature. See “Power-savingâ€� section below.”…”�”}”(hjDh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MXhj©h²hubeh}”(h]”Œkernel-configuration”ah ]”h"]”Œkernel configuration”ah$]”h&]”uh1hµhj˜h²hh³hÊh´MAubh¶)�”}”(hhh]”(h»)�”}”(hŒCodec Proc-File”h]”hŒCodec Proc-File”…”�”}”(hjkh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjhh²hh³hÊh´M]ubhÌ)�”}”(hŒyThe codec proc-file is a treasure-chest for debugging HD-audio. It shows most of useful information of each codec widget.”h]”hŒyThe codec proc-file is a treasure-chest for debugging HD-audio. It shows most of useful information of each codec widget.”…”�”}”(hjyh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M^hjhh²hubhÌ)�”}”(hXHThe proc file is located in /proc/asound/card*/codec#*, one file per each codec slot. You can know the codec vendor, product id and names, the type of each widget, capabilities and so on. This file, however, doesn't show the jack sensing state, so far. This is because the jack-sensing might be depending on the trigger state.”h]”hXJThe proc file is located in /proc/asound/card*/codec#*, one file per each codec slot. You can know the codec vendor, product id and names, the type of each widget, capabilities and so on. This file, however, doesn’t show the jack sensing state, so far. This is because the jack-sensing might be depending on the trigger state.”…”�”}”(hj‡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mahjhh²hubhÌ)�”}”(hŒœThis file will be picked up by the debug tools, and also it can be fed to the emulator as the primary codec information. See the debug tools section below.”h]”hŒœThis file will be picked up by the debug tools, and also it can be fed to the emulator as the primary codec information. See the debug tools section below.”…”�”}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mghjhh²hubhÌ)�”}”(hŒÈThis proc file can be also used to check whether the generic parser is used. When the generic parser is used, the vendor/product ID name will appear as "Realtek ID 0262", instead of "Realtek ALC262".”h]”hŒÐThis proc file can be also used to check whether the generic parser is used. When the generic parser is used, the vendor/product ID name will appear as “Realtek ID 0262â€�, instead of “Realtek ALC262â€�.”…”�”}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mkhjhh²hubeh}”(h]”Œcodec-proc-file”ah ]”h"]”Œcodec proc-file”ah$]”h&]”uh1hµhj˜h²hh³hÊh´M]ubh¶)�”}”(hhh]”(h»)�”}”(hŒHD-Audio Reconfiguration”h]”hŒHD-Audio Reconfiguration”…”�”}”(hj¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj¹h²hh³hÊh´MqubhÌ)�”}”(hŒçThis is an experimental feature to allow you re-configure the HD-audio codec dynamically without reloading the driver. The following sysfs files are available under each codec-hwdep device directory (e.g. /sys/class/sound/hwC0D0):”h]”hŒçThis is an experimental feature to allow you re-configure the HD-audio codec dynamically without reloading the driver. The following sysfs files are available under each codec-hwdep device directory (e.g. /sys/class/sound/hwC0D0):”…”�”}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mrhj¹h²hubhŒdefinition_list”“”)�”}”(hhh]”(hŒdefinition_list_item”“”)�”}”(hŒrvendor_id Shows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.”h]”(hŒterm”“”)�”}”(hŒ vendor_id”h]”hŒ vendor_id”…”�”}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MxhjßubhŒ definition”“”)�”}”(hhh]”hÌ)�”}”(hŒhShows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.”h]”hŒhShows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.”…”�”}”(hjøh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mxhjõubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjßubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MxhjÚubjÞ)�”}”(hŒ{subsystem_id Shows the 32bit codec subsystem-id hex number. You can change the subsystem-id value by writing to this file.”h]”(jä)�”}”(hŒ subsystem_id”h]”hŒ subsystem_id”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M{hjubjô)�”}”(hhh]”hÌ)�”}”(hŒnShows the 32bit codec subsystem-id hex number. You can change the subsystem-id value by writing to this file.”h]”hŒnShows the 32bit codec subsystem-id hex number. You can change the subsystem-id value by writing to this file.”…”�”}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M{hj$ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M{hjÚh²hubjÞ)�”}”(hŒxrevision_id Shows the 32bit codec revision-id hex number. You can change the revision-id value by writing to this file.”h]”(jä)�”}”(hŒ revision_id”h]”hŒ revision_id”…”�”}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M~hjAubjô)�”}”(hhh]”hÌ)�”}”(hŒlShows the 32bit codec revision-id hex number. You can change the revision-id value by writing to this file.”h]”hŒlShows the 32bit codec revision-id hex number. You can change the revision-id value by writing to this file.”…”�”}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M~hjSubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjAubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M~hjÚh²hubjÞ)�”}”(hŒ)afg Shows the AFG ID. This is read-only.”h]”(jä)�”}”(hŒafg”h]”hŒafg”…”�”}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M€hjpubjô)�”}”(hhh]”hÌ)�”}”(hŒ%Shows the AFG ID. This is read-only.”h]”hŒ%Shows the AFG ID. This is read-only.”…”�”}”(hj…h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M�hj‚ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjpubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M€hjÚh²hubjÞ)�”}”(hŒ)mfg Shows the MFG ID. This is read-only.”h]”(jä)�”}”(hŒmfg”h]”hŒmfg”…”�”}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M‚hjŸubjô)�”}”(hhh]”hÌ)�”}”(hŒ%Shows the MFG ID. This is read-only.”h]”hŒ%Shows the MFG ID. This is read-only.”…”�”}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mƒhj±ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjŸubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M‚hjÚh²hubjÞ)�”}”(hŒJname Shows the codec name string. Can be changed by writing to this file.”h]”(jä)�”}”(hŒname”h]”hŒname”…”�”}”(hjÒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M…hjÎubjô)�”}”(hhh]”hÌ)�”}”(hŒEShows the codec name string. Can be changed by writing to this file.”h]”hŒEShows the codec name string. Can be changed by writing to this file.”…”�”}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M…hjàubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjÎubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M…hjÚh²hubjÞ)�”}”(hŒ\modelname Shows the currently set ``model`` option. Can be changed by writing to this file.”h]”(jä)�”}”(hŒ modelname”h]”hŒ modelname”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´Mˆhjýubjô)�”}”(hhh]”hÌ)�”}”(hŒRShows the currently set ``model`` option. Can be changed by writing to this file.”h]”(hŒShows the currently set ”…”�”}”(hj h²hh³Nh´Nubj¬)�”}”(hŒ ``model``”h]”hŒmodel”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj ubhŒ1 option. Can be changed by writing to this file.”…”�”}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mˆhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjýubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MˆhjÚh²hubjÞ)�”}”(hŒ¬init_verbs The extra verbs to execute at initialization. You can add a verb by writing to this file. Pass three numbers: nid, verb and parameter (separated with a space).”h]”(jä)�”}”(hŒ init_verbs”h]”hŒ init_verbs”…”�”}”(hjB h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MŒhj> ubjô)�”}”(hhh]”hÌ)�”}”(hŒ¡The extra verbs to execute at initialization. You can add a verb by writing to this file. Pass three numbers: nid, verb and parameter (separated with a space).”h]”hŒ¡The extra verbs to execute at initialization. You can add a verb by writing to this file. Pass three numbers: nid, verb and parameter (separated with a space).”…”�”}”(hjS h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M‹hjP ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhj> ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MŒhjÚh²hubjÞ)�”}”(hŒÅhints Shows / stores hint strings for codec parsers for any use. Its format is ``key = value``. For example, passing ``jack_detect = no`` will disable the jack detection of the machine completely.”h]”(jä)�”}”(hŒhints”h]”hŒhints”…”�”}”(hjq h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M�hjm ubjô)�”}”(hhh]”hÌ)�”}”(hŒ¿Shows / stores hint strings for codec parsers for any use. Its format is ``key = value``. For example, passing ``jack_detect = no`` will disable the jack detection of the machine completely.”h]”(hŒIShows / stores hint strings for codec parsers for any use. Its format is ”…”�”}”(hj‚ h²hh³Nh´Nubj¬)�”}”(hŒ``key = value``”h]”hŒ key = value”…”�”}”(hjŠ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj‚ ubhŒ. For example, passing ”…”�”}”(hj‚ h²hh³Nh´Nubj¬)�”}”(hŒ``jack_detect = no``”h]”hŒjack_detect = no”…”�”}”(hjœ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj‚ ubhŒ; will disable the jack detection of the machine completely.”…”�”}”(hj‚ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M�hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjm ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M�hjÚh²hubjÞ)�”}”(hŒIinit_pin_configs Shows the initial pin default config values set by BIOS.”h]”(jä)�”}”(hŒinit_pin_configs”h]”hŒinit_pin_configs”…”�”}”(hjÄ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M’hjÀ ubjô)�”}”(hhh]”hÌ)�”}”(hŒ8Shows the initial pin default config values set by BIOS.”h]”hŒ8Shows the initial pin default config values set by BIOS.”…”�”}”(hjÕ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M“hjÒ ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjÀ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M’hjÚh²hubjÞ)�”}”(hX driver_pin_configs Shows the pin default values set by the codec parser explicitly. This doesn't show all pin values but only the changed values by the parser. That is, if the parser doesn't change the pin default config values by itself, this will contain nothing.”h]”(jä)�”}”(hŒdriver_pin_configs”h]”hŒdriver_pin_configs”…”�”}”(hjó h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M—hjï ubjô)�”}”(hhh]”hÌ)�”}”(hŒ÷Shows the pin default values set by the codec parser explicitly. This doesn't show all pin values but only the changed values by the parser. That is, if the parser doesn't change the pin default config values by itself, this will contain nothing.”h]”hŒûShows the pin default values set by the codec parser explicitly. This doesn’t show all pin values but only the changed values by the parser. That is, if the parser doesn’t change the pin default config values by itself, this will contain nothing.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M•hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjï ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M—hjÚh²hubjÞ)�”}”(hX9user_pin_configs Shows the pin default config values to override the BIOS setup. Writing this (with two numbers, NID and value) appends the new value. The given will be used instead of the initial BIOS value at the next reconfiguration time. Note that this config will override even the driver pin configs, too.”h]”(jä)�”}”(hŒuser_pin_configs”h]”hŒuser_pin_configs”…”�”}”(hj" h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M�hj ubjô)�”}”(hhh]”hÌ)�”}”(hX(Shows the pin default config values to override the BIOS setup. Writing this (with two numbers, NID and value) appends the new value. The given will be used instead of the initial BIOS value at the next reconfiguration time. Note that this config will override even the driver pin configs, too.”h]”hX(Shows the pin default config values to override the BIOS setup. Writing this (with two numbers, NID and value) appends the new value. The given will be used instead of the initial BIOS value at the next reconfiguration time. Note that this config will override even the driver pin configs, too.”…”�”}”(hj3 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mšhj0 ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M�hjÚh²hubjÞ)�”}”(hŒÙreconfig Triggers the codec re-configuration. When any value is written to this file, the driver re-initialize and parses the codec tree again. All the changes done by the sysfs entries above are taken into account.”h]”(jä)�”}”(hŒreconfig”h]”hŒreconfig”…”�”}”(hjQ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M¢hjM ubjô)�”}”(hhh]”hÌ)�”}”(hŒÐTriggers the codec re-configuration. When any value is written to this file, the driver re-initialize and parses the codec tree again. All the changes done by the sysfs entries above are taken into account.”h]”hŒÐTriggers the codec re-configuration. When any value is written to this file, the driver re-initialize and parses the codec tree again. All the changes done by the sysfs entries above are taken into account.”…”�”}”(hjb h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hj_ ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjM ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M¢hjÚh²hubjÞ)�”}”(hŒ}clear Resets the codec, removes the mixer elements and PCM stuff of the specified codec, and clear all init verbs and hints. ”h]”(jä)�”}”(hŒclear”h]”hŒclear”…”�”}”(hj€ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M¦hj| ubjô)�”}”(hhh]”hÌ)�”}”(hŒvResets the codec, removes the mixer elements and PCM stuff of the specified codec, and clear all init verbs and hints.”h]”hŒvResets the codec, removes the mixer elements and PCM stuff of the specified codec, and clear all init verbs and hints.”…”�”}”(hj‘ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¥hjŽ ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhj| ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M¦hjÚh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jØhj¹h²hh³hÊh´NubhÌ)�”}”(hŒ¶For example, when you want to change the pin default configuration value of the pin widget 0x14 to 0x9993013f, and let the driver re-configure based on that state, run like below: ::”h]”hŒ³For example, when you want to change the pin default configuration value of the pin widget 0x14 to 0x9993013f, and let the driver re-configure based on that state, run like below:”…”�”}”(hj± h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¨hj¹h²hubj£)�”}”(hŒm# echo 0x14 0x9993013f > /sys/class/sound/hwC0D0/user_pin_configs # echo 1 > /sys/class/sound/hwC0D0/reconfig”h]”hŒm# echo 0x14 0x9993013f > /sys/class/sound/hwC0D0/user_pin_configs # echo 1 > /sys/class/sound/hwC0D0/reconfig”…”�”}”hj¿ sbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´M­hj¹h²hubeh}”(h]”Œhd-audio-reconfiguration”ah ]”h"]”Œhd-audio reconfiguration”ah$]”h&]”uh1hµhj˜h²hh³hÊh´Mqubh¶)�”}”(hhh]”(h»)�”}”(hŒ Hint Strings”h]”hŒ Hint Strings”…”�”}”(hjØ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÕ h²hh³hÊh´M²ubhÌ)�”}”(hXþThe codec parser have several switches and adjustment knobs for matching better with the actual codec or device behavior. Many of them can be adjusted dynamically via "hints" strings as mentioned in the section above. For example, by passing ``jack_detect = no`` string via sysfs or a patch file, you can disable the jack detection, thus the codec parser will skip the features like auto-mute or mic auto-switch. As a boolean value, either ``yes``, ``no``, ``true``, ``false``, ``1`` or ``0`` can be passed.”h]”(hŒøThe codec parser have several switches and adjustment knobs for matching better with the actual codec or device behavior. Many of them can be adjusted dynamically via “hintsâ€� strings as mentioned in the section above. For example, by passing ”…”�”}”(hjæ h²hh³Nh´Nubj¬)�”}”(hŒ``jack_detect = no``”h]”hŒjack_detect = no”…”�”}”(hjî h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ³ string via sysfs or a patch file, you can disable the jack detection, thus the codec parser will skip the features like auto-mute or mic auto-switch. As a boolean value, either ”…”�”}”(hjæ h²hh³Nh´Nubj¬)�”}”(hŒ``yes``”h]”hŒyes”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ, ”…”�”}”(hjæ h²hh³Nh´Nubj¬)�”}”(hŒ``no``”h]”hŒno”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ, ”…”�”}”hjæ sbj¬)�”}”(hŒ``true``”h]”hŒtrue”…”�”}”(hj$ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ, ”…”�”}”hjæ sbj¬)�”}”(hŒ ``false``”h]”hŒfalse”…”�”}”(hj6 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ, ”…”�”}”(hjæ h²hh³Nh´Nubj¬)�”}”(hŒ``1``”h]”hŒ1”…”�”}”(hjH h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ or ”…”�”}”(hjæ h²hh³Nh´Nubj¬)�”}”(hŒ``0``”h]”hŒ0”…”�”}”(hjZ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjæ ubhŒ can be passed.”…”�”}”(hjæ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M³hjÕ h²hubhÌ)�”}”(hŒ0The generic parser supports the following hints:”h]”hŒ0The generic parser supports the following hints:”…”�”}”(hjr h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¼hjÕ h²hubjÙ)�”}”(hhh]”(jÞ)�”}”(hŒgjack_detect (bool) specify whether the jack detection is available at all on this machine; default true”h]”(jä)�”}”(hŒjack_detect (bool)”h]”hŒjack_detect (bool)”…”�”}”(hj‡ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´M¿hjƒ ubjô)�”}”(hhh]”hÌ)�”}”(hŒTspecify whether the jack detection is available at all on this machine; default true”h]”hŒTspecify whether the jack detection is available at all on this machine; default true”…”�”}”(hj˜ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¿hj• ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjƒ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´M¿hj€ ubjÞ)�”}”(hŒJinv_jack_detect (bool) indicates that the jack detection logic is inverted”h]”(jä)�”}”(hŒinv_jack_detect (bool)”h]”hŒinv_jack_detect (bool)”…”�”}”(hj¶ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MÁhj² ubjô)�”}”(hhh]”hÌ)�”}”(hŒ3indicates that the jack detection logic is inverted”h]”hŒ3indicates that the jack detection logic is inverted”…”�”}”(hjÇ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÂhjÄ ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhj² ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MÁhj€ h²hubjÞ)�”}”(hŒltrigger_sense (bool) indicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verb”•Âòh]”(jä)�”}”(hŒtrigger_sense (bool)”h]”hŒtrigger_sense (bool)”…”�”}”(hjå h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MÄhjá ubjô)�”}”(hhh]”hÌ)�”}”(hŒWindicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verb”h]”hŒWindicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verb”…”�”}”(hjö h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÄhjó ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjá ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MÄhj€ h²hubjÞ)�”}”(hŒLinv_eapd (bool) indicates that the EAPD is implemented in the inverted logic”h]”(jä)�”}”(hŒinv_eapd (bool)”h]”hŒinv_eapd (bool)”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MÆhj ubjô)�”}”(hhh]”hÌ)�”}”(hŒhjWh²hubj£)�”}”(hŒl[codec] 0x12345678 0xabcd1234 2 [subsystem_id] 0xffff1111 [revision_id] 0x10 [chip_name] My-own NEWS-0002”h]”hŒl[codec] 0x12345678 0xabcd1234 2 [subsystem_id] 0xffff1111 [revision_id] 0x10 [chip_name] My-own NEWS-0002”…”�”}”hjÌsbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´MChjWh²hubhÌ)�”}”(hXThe hd-audio driver reads the file via request_firmware(). Thus, a patch file has to be located on the appropriate firmware path, typically, /lib/firmware. For example, when you pass the option ``patch=hda-init.fw``, the file /lib/firmware/hda-init.fw must be present.”h]”(hŒÄThe hd-audio driver reads the file via request_firmware(). Thus, a patch file has to be located on the appropriate firmware path, typically, /lib/firmware. For example, when you pass the option ”…”�”}”(hjÚh²hh³Nh´Nubj¬)�”}”(hŒ``patch=hda-init.fw``”h]”hŒpatch=hda-init.fw”…”�”}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÚubhŒ5, the file /lib/firmware/hda-init.fw must be present.”…”�”}”(hjÚh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MPhjWh²hubhÌ)�”}”(hXThe patch module option is specific to each card instance, and you need to give one file name for each instance, separated by commas. For example, if you have two cards, one for an on-board analog and one for an HDMI video board, you may pass patch option like below: ::”h]”hX The patch module option is specific to each card instance, and you need to give one file name for each instance, separated by commas. For example, if you have two cards, one for an on-board analog and one for an HDMI video board, you may pass patch option like below:”…”�”}”(hjúh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MVhjWh²hubj£)�”}”(hŒ5options snd-hda-intel patch=on-board-patch,hdmi-patch”h]”hŒ5options snd-hda-intel patch=on-board-patch,hdmi-patch”…”�”}”hjsbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´M\hjWh²hubeh}”(h]”Œearly-patching”ah ]”h"]”Œearly patching”ah$]”h&]”uh1hµhj˜h²hh³hÊh´Mubh¶)�”}”(hhh]”(h»)�”}”(hŒ Power-Saving”h]”hŒ Power-Saving”…”�”}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´M`ubhÌ)�”}”(hXThe power-saving is a kind of auto-suspend of the device. When the device is inactive for a certain time, the device is automatically turned off to save the power. The time to go down is specified via ``power_save`` module option, and this option can be changed dynamically via sysfs.”h]”(hŒËThe power-saving is a kind of auto-suspend of the device. When the device is inactive for a certain time, the device is automatically turned off to save the power. The time to go down is specified via ”…”�”}”(hj/h²hh³Nh´Nubj¬)�”}”(hŒ``power_save``”h]”hŒ power_save”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj/ubhŒE module option, and this option can be changed dynamically via sysfs.”…”�”}”(hj/h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mahjh²hubhÌ)�”}”(hŒ£The power-saving won't work when the analog loopback is enabled on some codecs. Make sure that you mute all unneeded signal routes when you want the power-saving.”h]”hŒ¥The power-saving won’t work when the analog loopback is enabled on some codecs. Make sure that you mute all unneeded signal routes when you want the power-saving.”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mghjh²hubhÌ)�”}”(hXÒThe power-saving feature might cause audible click noises at each power-down/up depending on the device. Some of them might be solvable, but some are hard, I'm afraid. Some distros such as openSUSE enables the power-saving feature automatically when the power cable is unplugged. Thus, if you hear noises, suspect first the power-saving. See /sys/module/snd_hda_intel/parameters/power_save to check the current value. If it's non-zero, the feature is turned on.”h]”hXÖThe power-saving feature might cause audible click noises at each power-down/up depending on the device. Some of them might be solvable, but some are hard, I’m afraid. Some distros such as openSUSE enables the power-saving feature automatically when the power cable is unplugged. Thus, if you hear noises, suspect first the power-saving. See /sys/module/snd_hda_intel/parameters/power_save to check the current value. If it’s non-zero, the feature is turned on.”…”�”}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mkhjh²hubhÌ)�”}”(hX”The recent kernel supports the runtime PM for the HD-audio controller chip, too. It means that the HD-audio controller is also powered up / down dynamically. The feature is enabled only for certain controller chips like Intel LynxPoint. You can enable/disable this feature forcibly by setting ``power_save_controller`` option, which is also available at /sys/module/snd_hda_intel/parameters directory.”h]”(hX(The recent kernel supports the runtime PM for the HD-audio controller chip, too. It means that the HD-audio controller is also powered up / down dynamically. The feature is enabled only for certain controller chips like Intel LynxPoint. You can enable/disable this feature forcibly by setting ”…”�”}”(hjkh²hh³Nh´Nubj¬)�”}”(hŒ``power_save_controller``”h]”hŒpower_save_controller”…”�”}”(hjsh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjkubhŒS option, which is also available at /sys/module/snd_hda_intel/parameters directory.”…”�”}”(hjkh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mshjh²hubeh}”(h]”Œ power-saving”ah ]”h"]”Œ power-saving”ah$]”h&]”uh1hµhj˜h²hh³hÊh´M`ubh¶)�”}”(hhh]”(h»)�”}”(hŒ Tracepoints”h]”hŒ Tracepoints”…”�”}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj“h²hh³hÊh´M|ubhÌ)�”}”(hX¥The hd-audio driver gives a few basic tracepoints. ``hda:hda_send_cmd`` traces each CORB write while ``hda:hda_get_response`` traces the response from RIRB (only when read from the codec driver). ``hda:hda_bus_reset`` traces the bus-reset due to fatal error, etc, ``hda:hda_unsol_event`` traces the unsolicited events, and ``hda:hda_power_down`` and ``hda:hda_power_up`` trace the power down/up via power-saving behavior.”h]”(hŒ3The hd-audio driver gives a few basic tracepoints. ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_send_cmd``”h]”hŒhda:hda_send_cmd”…”�”}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒ traces each CORB write while ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_get_response``”h]”hŒhda:hda_get_response”…”�”}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒG traces the response from RIRB (only when read from the codec driver). ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_bus_reset``”h]”hŒhda:hda_bus_reset”…”�”}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒ/ traces the bus-reset due to fatal error, etc, ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_unsol_event``”h]”hŒhda:hda_unsol_event”…”�”}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒ$ traces the unsolicited events, and ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_power_down``”h]”hŒhda:hda_power_down”…”�”}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒ and ”…”�”}”(hj¤h²hh³Nh´Nubj¬)�”}”(hŒ``hda:hda_power_up``”h]”hŒhda:hda_power_up”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hj¤ubhŒ3 trace the power down/up via power-saving behavior.”…”�”}”(hj¤h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M}hj“h²hubhÌ)�”}”(hŒ,Enabling all tracepoints can be done like ::”h]”hŒ)Enabling all tracepoints can be done like”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M…hj“h²hubj£)�”}”(hŒ0# echo 1 > /sys/kernel/tracing/events/hda/enable”h]”hŒ0# echo 1 > /sys/kernel/tracing/events/hda/enable”…”�”}”hj,sbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´Mˆhj“h²hubhÌ)�”}”(hŒ­then after some commands, you can traces from /sys/kernel/tracing/trace file. For example, when you want to trace what codec command is sent, enable the tracepoint like: ::”h]”hŒªthen after some commands, you can traces from /sys/kernel/tracing/trace file. For example, when you want to trace what codec command is sent, enable the tracepoint like:”…”�”}”(hj:h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MŠhj“h²hubj£)�”}”(hXÃ# cat /sys/kernel/tracing/trace # tracer: nop # # TASK-PID CPU# TIMESTAMP FUNCTION # | | | | | <...>-7807 [002] 105147.774889: hda_send_cmd: [0:0] val=e3a019 <...>-7807 [002] 105147.774893: hda_send_cmd: [0:0] val=e39019 <...>-7807 [002] 105147.999542: hda_send_cmd: [0:0] val=e3a01a <...>-7807 [002] 105147.999543: hda_send_cmd: [0:0] val=e3901a <...>-26764 [001] 349222.837143: hda_send_cmd: [0:0] val=e3a019 <...>-26764 [001] 349222.837148: hda_send_cmd: [0:0] val=e39019 <...>-26764 [001] 349223.058539: hda_send_cmd: [0:0] val=e3a01a <...>-26764 [001] 349223.058541: hda_send_cmd: [0:0] val=e3901a”h]”hXÃ# cat /sys/kernel/tracing/trace # tracer: nop # # TASK-PID CPU# TIMESTAMP FUNCTION # | | | | | <...>-7807 [002] 105147.774889: hda_send_cmd: [0:0] val=e3a019 <...>-7807 [002] 105147.774893: hda_send_cmd: [0:0] val=e39019 <...>-7807 [002] 105147.999542: hda_send_cmd: [0:0] val=e3a01a <...>-7807 [002] 105147.999543: hda_send_cmd: [0:0] val=e3901a <...>-26764 [001] 349222.837143: hda_send_cmd: [0:0] val=e3a019 <...>-26764 [001] 349222.837148: hda_send_cmd: [0:0] val=e39019 <...>-26764 [001] 349223.058539: hda_send_cmd: [0:0] val=e3a01a <...>-26764 [001] 349223.058541: hda_send_cmd: [0:0] val=e3901a”…”�”}”hjHsbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´M�hj“h²hubhÌ)�”}”(hX<Here ``[0:0]`` indicates the card number and the codec address, and ``val`` shows the value sent to the codec, respectively. The value is a packed value, and you can decode it via hda-decode-verb program included in hda-emu package below. For example, the value e3a019 is to set the left output-amp value to 25. ::”h]”(hŒHere ”…”�”}”(hjVh²hh³Nh´Nubj¬)�”}”(hŒ ``[0:0]``”h]”hŒ[0:0]”…”�”}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjVubhŒ6 indicates the card number and the codec address, and ”…”�”}”(hjVh²hh³Nh´Nubj¬)�”}”(hŒ``val``”h]”hŒval”…”�”}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjVubhŒî shows the value sent to the codec, respectively. The value is a packed value, and you can decode it via hda-decode-verb program included in hda-emu package below. For example, the value e3a019 is to set the left output-amp value to 25.”…”�”}”(hjVh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M�hj“h²hubj£)�”}”(hŒÛ% hda-decode-verb 0xe3a019 raw value = 0x00e3a019 cid = 0, nid = 0x0e, verb = 0x3a0, parm = 0x19 raw value: verb = 0x3a0, parm = 0x19 verbname = set_amp_gain_mute amp raw val = 0xa019 output, left, idx=0, mute=0, val=25”h]”hŒÛ% hda-decode-verb 0xe3a019 raw value = 0x00e3a019 cid = 0, nid = 0x0e, verb = 0x3a0, parm = 0x19 raw value: verb = 0x3a0, parm = 0x19 verbname = set_amp_gain_mute amp raw val = 0xa019 output, left, idx=0, mute=0, val=25”…”�”}”hjˆsbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´M¤hj“h²hubeh}”(h]”Œ tracepoints”ah ]”h"]”Œ tracepoints”ah$]”h&]”uh1hµhj˜h²hh³hÊh´M|ubh¶)�”}”(hhh]”(h»)�”}”(hŒDevelopment Tree”h]”hŒDevelopment Tree”…”�”}”(hj¡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjžh²hh³hÊh´M®ubhÌ)�”}”(hŒFThe latest development codes for HD-audio are found on sound git tree:”h]”hŒFThe latest development codes for HD-audio are found on sound git tree:”…”�”}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¯hjžh²hubjI)�”}”(hhh]”jN)�”}”(hŒ>git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git ”h]”hÌ)�”}”(hŒ=git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git”h]”hŒ=git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git”…”�”}”(hjÄh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M±hjÀubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj½h²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M±hjžh²hubhÌ)�”}”(hŒÑThe master branch or for-next branches can be used as the main development branches in general while the development for the current and next kernels are found in for-linus and for-next branches, respectively.”h]”hŒÑThe master branch or for-next branches can be used as the main development branches in general while the development for the current and next kernels are found in for-linus and for-next branches, respectively.”…”�”}”(hjÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M³hjžh²hubeh}”(h]”Œdevelopment-tree”ah ]”h"]”Œdevelopment tree”ah$]”h&]”uh1hµhj˜h²hh³hÊh´M®ubh¶)�”}”(hhh]”(h»)�”}”(hŒSending a Bug Report”h]”hŒSending a Bug Report”…”�”}”(hj÷h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjôh²hh³hÊh´MºubhÌ)�”}”(hŒ”If any model or module options don't work for your device, it's time to send a bug report to the developers. Give the following in your bug report:”h]”hŒ˜If any model or module options don’t work for your device, it’s time to send a bug report to the developers. Give the following in your bug report:”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M»hjôh²hubjI)�”}”(hhh]”(jN)�”}”(hŒ(Hardware vendor, product and model names”h]”hÌ)�”}”(hjh]”hŒ(Hardware vendor, product and model names”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M¿hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjh²hh³hÊh´NubjN)�”}”(hŒ@Kernel version (and ALSA-driver version if you built externally)”h]”hÌ)�”}”(hj/h]”hŒ@Kernel version (and ALSA-driver version if you built externally)”…”�”}”(hj1h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÀhj-ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjh²hh³hÊh´NubjN)�”}”(hŒa``alsa-info.sh`` output; run with ``--no-upload`` option. See the section below about alsa-info ”h]”hÌ)�”}”(hŒ```alsa-info.sh`` output; run with ``--no-upload`` option. See the section below about alsa-info”h]”(j¬)�”}”(hŒ``alsa-info.sh``”h]”hŒ alsa-info.sh”…”�”}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjHubhŒ output; run with ”…”�”}”(hjHh²hh³Nh´Nubj¬)�”}”(hŒ``--no-upload``”h]”hŒ --no-upload”…”�”}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjHubhŒ/ option. See the section below about alsa-info”…”�”}”(hjHh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÁhjDubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M¿hjôh²hubhÌ)�”}”(hŒ«If it's a regression, at best, send alsa-info outputs of both working and non-working kernels. This is really helpful because we can compare the codec registers directly.”h]”hŒ­If it’s a regression, at best, send alsa-info outputs of both working and non-working kernels. This is really helpful because we can compare the codec registers directly.”…”�”}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÄhjôh²hubhÌ)�”}”(hŒ'Send a bug report either the following:”h]”hŒ'Send a bug report either the following:”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÈhjôh²hubjÙ)�”}”(hhh]”(jÞ)�”}”(hŒ,kernel-bugzilla https://bugzilla.kernel.org/”h]”(jä)�”}”(hŒkernel-bugzilla”h]”hŒkernel-bugzilla”…”�”}”(hj¥h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MÊhj¡ubjô)�”}”(hhh]”hÌ)�”}”(hŒhttps://bugzilla.kernel.org/”h]”hÖ)�”}”(hj¸h]”hŒhttps://bugzilla.kernel.org/”…”�”}”(hjºh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¸uh1hÕhj¶ubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MËhj³ubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhj¡ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MÊhjžubjÞ)�”}”(hŒ+alsa-devel ML alsa-devel@alsa-project.org ”h]”(jä)�”}”(hŒ alsa-devel ML”h]”hŒ alsa-devel ML”…”�”}”(hjÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jãh³hÊh´MÎhjÚubjô)�”}”(hhh]”hÌ)�”}”(hŒalsa-devel@alsa-project.org”h]”hÖ)�”}”(hjñh]”hŒalsa-devel@alsa-project.org”…”�”}”(hjóh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:alsa-devel@alsa-project.org”uh1hÕhjïubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÍhjìubah}”(h]”h ]”h"]”h$]”h&]”uh1jóhjÚubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÝh³hÊh´MÎhjžh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jØhjôh²hh³hÊh´Nubeh}”(h]”Œsending-a-bug-report”ah ]”h"]”Œsending a bug report”ah$]”h&]”uh1hµhj˜h²hh³hÊh´Mºubeh}”(h]”Œ other-issues”ah ]”h"]”Œ other issues”ah$]”h&]”uh1hµhh·h²hh³hÊh´M>ubh¶)�”}”(hhh]”(h»)�”}”(hŒ Debug Tools”h]”hŒ Debug Tools”…”�”}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj*h²hh³hÊh´MÑubhÌ)�”}”(hŒLThis section describes some tools available for debugging HD-audio problems.”h]”hŒLThis section describes some tools available for debugging HD-audio problems.”…”�”}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÓhj*h²hubh¶)�”}”(hhh]”(h»)�”}”(hŒ alsa-info”h]”hŒ alsa-info”…”�”}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjIh²hh³hÊh´M×ubhÌ)�”}”(hŒ³The script ``alsa-info.sh`` is a very useful tool to gather the audio device information. It's included in alsa-utils package. The latest version can be found on git repository:”h]”(hŒ The script ”…”�”}”(hjZh²hh³Nh´Nubj¬)�”}”(hŒ``alsa-info.sh``”h]”hŒ alsa-info.sh”…”�”}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjZubhŒš is a very useful tool to gather the audio device information. It’s included in alsa-utils package. The latest version can be found on git repository:”…”�”}”(hjZh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MØhjIh²hubjI)�”}”(hhh]”jN)�”}”(hŒ*git://git.alsa-project.org/alsa-utils.git ”h]”hÌ)�”}”(hŒ)git://git.alsa-project.org/alsa-utils.git”h]”hŒ)git://git.alsa-project.org/alsa-utils.git”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÜhj}ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjzh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´MÜhjIh²hubhÌ)�”}”(hŒ?The script can be fetched directly from the following URL, too:”h]”hŒ?The script can be fetched directly from the following URL, too:”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MÞhjIh²hubjI)�”}”(hhh]”jN)�”}”(hŒ*https://www.alsa-project.org/alsa-info.sh ”h]”hÌ)�”}”(hŒ)https://www.alsa-project.org/alsa-info.sh”h]”hÖ)�”}”(hj²h]”hŒ)https://www.alsa-project.org/alsa-info.sh”…”�”}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j²uh1hÕhj°ubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Màhj¬ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj©h²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´MàhjIh²hubhÌ)�”}”(hX‘Run this script as root, and it will gather the important information such as the module lists, module parameters, proc file contents including the codec proc files, mixer outputs and the control elements. As default, it will store the information onto a web server on alsa-project.org. But, if you send a bug report, it'd be better to run with ``--no-upload`` option, and attach the generated file.”h]”(hX]Run this script as root, and it will gather the important information such as the module lists, module parameters, proc file contents including the codec proc files, mixer outputs and the control elements. As default, it will store the information onto a web server on alsa-project.org. But, if you send a bug report, it’d be better to run with ”…”�”}”(hjÔh²hh³Nh´Nubj¬)�”}”(hŒ``--no-upload``”h]”hŒ --no-upload”…”�”}”(hjÜh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjÔubhŒ' option, and attach the generated file.”…”�”}”(hjÔh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MâhjIh²hubhÌ)�”}”(hŒOThere are some other useful options. See ``--help`` option output for details.”h]”(hŒ*There are some other useful options. See ”…”�”}”(hjôh²hh³Nh´Nubj¬)�”}”(hŒ ``--help``”h]”hŒ--help”…”�”}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjôubhŒ option output for details.”…”�”}”(hjôh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MéhjIh²hubhÌ)�”}”(hXùWhen a probe error occurs or when the driver obviously assigns a mismatched model, it'd be helpful to load the driver with ``probe_only=1`` option (at best after the cold reboot) and run alsa-info at this state. With this option, the driver won't configure the mixer and PCM but just tries to probe the codec slot. After probing, the proc file is available, so you can get the raw codec information before modified by the driver. Of course, the driver isn't usable with ``probe_only=1``. But you can continue the configuration via hwdep sysfs file if hda-reconfig option is enabled. Using ``probe_only`` mask 2 skips the reset of HDA codecs (use ``probe_only=3`` as module option). The hwdep interface can be used to determine the BIOS codec initialization.”h]”(hŒ}When a probe error occurs or when the driver obviously assigns a mismatched model, it’d be helpful to load the driver with ”…”�”}”(hjh²hh³Nh´Nubj¬)�”}”(hŒ``probe_only=1``”h]”hŒ probe_only=1”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjubhXR option (at best after the cold reboot) and run alsa-info at this state. With this option, the driver won’t configure the mixer and PCM but just tries to probe the codec slot. After probing, the proc file is available, so you can get the raw codec information before modified by the driver. Of course, the driver isn’t usable with ”…”�”}”(hjh²hh³Nh´Nubj¬)�”}”(hŒ``probe_only=1``”h]”hŒ probe_only=1”…”�”}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjubhŒh. But you can continue the configuration via hwdep sysfs file if hda-reconfig option is enabled. Using ”…”�”}”(hjh²hh³Nh´Nubj¬)�”}”(hŒ``probe_only``”h]”hŒ probe_only”…”�”}”(hj@h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjubhŒ+ mask 2 skips the reset of HDA codecs (use ”…”�”}”(hjh²hh³Nh´Nubj¬)�”}”(hŒ``probe_only=3``”h]”hŒ probe_only=3”…”�”}”(hjRh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjubhŒ_ as module option). The hwdep interface can be used to determine the BIOS codec initialization.”…”�”}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MìhjIh²hubeh}”(h]”Œ alsa-info”ah ]”h"]”Œ alsa-info”ah$]”h&]”uh1hµhj*h²hh³hÊh´M×ubh¶)�”}”(hhh]”(h»)�”}”(hŒhda-verb”h]”hŒhda-verb”…”�”}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjrh²hh³hÊh´MûubhÌ)�”}”(hXhda-verb is a tiny program that allows you to access the HD-audio codec directly. You can execute a raw HD-audio codec verb with this. This program accesses the hwdep device, thus you need to enable the kernel config ``CONFIG_SND_HDA_HWDEP=y`` beforehand.”h]”(hŒÚhda-verb is a tiny program that allows you to access the HD-audio codec directly. You can execute a raw HD-audio codec verb with this. This program accesses the hwdep device, thus you need to enable the kernel config ”…”�”}”(hjƒh²hh³Nh´Nubj¬)�”}”(hŒ``CONFIG_SND_HDA_HWDEP=y``”h]”hŒCONFIG_SND_HDA_HWDEP=y”…”�”}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j«hjƒubhŒ beforehand.”…”�”}”(hjƒh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mühjrh²hubhÌ)�”}”(hXThe hda-verb program takes four arguments: the hwdep device file, the widget NID, the verb and the parameter. When you access to the codec on the slot 2 of the card 0, pass /dev/snd/hwC0D2 to the first argument, typically. (However, the real path name depends on the system.)”h]”hXThe hda-verb program takes four arguments: the hwdep device file, the widget NID, the verb and the parameter. When you access to the codec on the slot 2 of the card 0, pass /dev/snd/hwC0D2 to the first argument, typically. (However, the real path name depends on the system.)”…”�”}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjrh²hubhÌ)�”}”(hŒóThe second parameter is the widget number-id to access. The third parameter can be either a hex/digit number or a string corresponding to a verb. Similarly, the last parameter is the value to write, or can be a string for the parameter type.”h]”hŒóThe second parameter is the widget number-id to access. The third parameter can be either a hex/digit number or a string corresponding to a verb. Similarly, the last parameter is the value to write, or can be a string for the parameter type.”…”�”}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjrh²hubj£)�”}”(hX%% hda-verb /dev/snd/hwC0D0 0x12 0x701 2 nid = 0x12, verb = 0x701, param = 0x2 value = 0x0 % hda-verb /dev/snd/hwC0D0 0x0 PARAMETERS VENDOR_ID nid = 0x0, verb = 0xf00, param = 0x0 value = 0x10ec0262 % hda-verb /dev/snd/hwC0D0 2 set_a 0xb080 nid = 0x2, verb = 0x300, param = 0xb080 value = 0x0”h]”hX%% hda-verb /dev/snd/hwC0D0 0x12 0x701 2 nid = 0x12, verb = 0x701, param = 0x2 value = 0x0 % hda-verb /dev/snd/hwC0D0 0x0 PARAMETERS VENDOR_ID nid = 0x0, verb = 0xf00, param = 0x0 value = 0x10ec0262 % hda-verb /dev/snd/hwC0D0 2 set_a 0xb080 nid = 0x2, verb = 0x300, param = 0xb080 value = 0x0”…”�”}”hj¿sbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´Mhjrh²hubhÌ)�”}”(hŒúAlthough you can issue any verbs with this program, the driver state won't be always updated. For example, the volume values are usually cached in the driver, and thus changing the widget amp value directly via hda-verb won't change the mixer value.”h]”hŒþAlthough you can issue any verbs with this program, the driver state won’t be always updated. For example, the volume values are usually cached in the driver, and thus changing the widget amp value directly via hda-verb won’t change the mixer value.”…”�”}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mhjrh²hubhÌ)�”}”(hŒ3The hda-verb program is included now in alsa-tools:”h]”hŒ3The hda-verb program is included now in alsa-tools:”…”�”}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M hjrh²hubjI)�”}”(hhh]”jN)�”}”(hŒ*git://git.alsa-project.org/alsa-tools.git ”h]”hÌ)�”}”(hŒ)git://git.alsa-project.org/alsa-tools.git”h]”hŒ)git://git.alsa-project.org/alsa-tools.git”…”�”}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M"hjìubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjéh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M"hjrh²hubhÌ)�”}”(hŒ@Also, the old stand-alone package is found in the ftp directory:”h]”hŒ@Also, the old stand-alone package is found in the ftp directory:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M$hjrh²hubjI)�”}”(hhh]”jN)�”}”(hŒ*ftp://ftp.suse.com/pub/people/tiwai/misc/ ”h]”hÌ)�”}”(hŒ)ftp://ftp.suse.com/pub/people/tiwai/misc/”h]”hÖ)�”}”(hj!h]”hŒ)ftp://ftp.suse.com/pub/people/tiwai/misc/”…”�”}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j!uh1hÕhjubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M&hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M&hjrh²hubhÌ)�”}”(hŒ#Also a git repository is available:”h]”hŒ#Also a git repository is available:”…”�”}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M(hjrh²hubjI)�”}”(hhh]”jN)�”}”(hŒAgit://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-verb.git ”h]”hÌ)�”}”(hŒ@git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-verb.git”h]”hŒ@git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-verb.git”…”�”}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M*hjTubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjQh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M*hjrh²hubhÌ)�”}”(hŒGSee README file in the tarball for more details about hda-verb program.”h]”hŒGSee README file in the tarball for more details about hda-verb program.”…”�”}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M,hjrh²hubeh}”(h]”Œhda-verb”ah ]”h"]”Œhda-verb”ah$]”h&]”uh1hµhj*h²hh³hÊh´Mûubh¶)�”}”(hhh]”(h»)�”}”(hŒ hda-analyzer”h]”hŒ hda-analyzer”…”�”}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjˆh²hh³hÊh´M1ubhÌ)�”}”(hX+hda-analyzer provides a graphical interface to access the raw HD-audio control, based on pyGTK2 binding. It's a more powerful version of hda-verb. The program gives you an easy-to-use GUI stuff for showing the widget information and adjusting the amp values, as well as the proc-compatible output.”h]”hX-hda-analyzer provides a graphical interface to access the raw HD-audio control, based on pyGTK2 binding. It’s a more powerful version of hda-verb. The program gives you an easy-to-use GUI stuff for showing the widget information and adjusting the amp values, as well as the proc-compatible output.”…”�”}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M2hjˆh²hubhÌ)�”}”(hŒThe hda-analyzer:”h]”hŒThe hda-analyzer:”…”�”}”(hj§h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M8hjˆh²hubjI)�”}”(hhh]”jN)�”}”(hŒ?https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer ”h]”hÌ)�”}”(hŒ>https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer”h]”hÖ)�”}”(hj¾h]”hŒ>https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer”…”�”}”(hjÀh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¾uh1hÕhj¼ubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M:hj¸ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjµh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M:hjˆh²hubhÌ)�”}”(hŒ5is a part of alsa.git repository in alsa-project.org:”h]”hŒ5is a part of alsa.git repository in alsa-project.org:”…”�”}”(hjàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M<hjˆh²hubjI)�”}”(hhh]”jN)�”}”(hŒ$git://git.alsa-project.org/alsa.git ”h]”hÌ)�”}”(hŒ#git://git.alsa-project.org/alsa.git”h]”hŒ#git://git.alsa-project.org/alsa.git”…”�”}”(hjõh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M>hjñubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjîh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M>hjˆh²hubeh}”(h]”Œ hda-analyzer”ah ]”h"]”Œ hda-analyzer”ah$]”h&]”uh1hµhj*h²hh³hÊh´M1ubh¶)�”}”(hhh]”(h»)�”}”(hŒ Codecgraph”h]”hŒ Codecgraph”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´MAubhÌ)�”}”(hXCodecgraph is a utility program to generate a graph and visualizes the codec-node connection of a codec chip. It's especially useful when you analyze or debug a codec without a proper datasheet. The program parses the given codec proc file and converts to SVG via graphiz program.”h]”hXCodecgraph is a utility program to generate a graph and visualizes the codec-node connection of a codec chip. It’s especially useful when you analyze or debug a codec without a proper datasheet. The program parses the given codec proc file and converts to SVG via graphiz program.”…”�”}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MBhjh²hubhÌ)�”}”(hŒ7The tarball and GIT trees are found in the web page at:”h]”hŒ7The tarball and GIT trees are found in the web page at:”…”�”}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MHhjh²hubjI)�”}”(hhh]”jN)�”}”(hŒ!http://helllabs.org/codecgraph/ ”h]”hÌ)�”}”(hŒhttp://helllabs.org/codecgraph/”h]”hÖ)�”}”(hjMh]”hŒhttp://helllabs.org/codecgraph/”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jMuh1hÕhjKubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MJhjGubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjDh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´MJhjh²hubeh}”(h]”Œ codecgraph”ah ]”h"]”Œ codecgraph”ah$]”h&]”uh1hµhj*h²hh³hÊh´MAubh¶)�”}”(hhh]”(h»)�”}”(hŒhda-emu”h]”hŒhda-emu”…”�”}”(hjzh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjwh²hh³hÊh´MNubhÌ)�”}”(hX;hda-emu is an HD-audio emulator. The main purpose of this program is to debug an HD-audio codec without the real hardware. Thus, it doesn't emulate the behavior with the real audio I/O, but it just dumps the codec register changes and the ALSA-driver internal changes at probing and operating the HD-audio driver.”h]”hX=hda-emu is an HD-audio emulator. The main purpose of this program is to debug an HD-audio codec without the real hardware. Thus, it doesn’t emulate the behavior with the real audio I/O, but it just dumps the codec register changes and the ALSA-driver internal changes at probing and operating the HD-audio driver.”…”�”}”(hjˆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MOhjwh²hubhÌ)�”}”(hX9The program requires a codec proc-file to simulate. Get a proc file for the target codec beforehand, or pick up an example codec from the codec proc collections in the tarball. Then, run the program with the proc file, and the hda-emu program will start parsing the codec file and simulates the HD-audio driver:”h]”hX9The program requires a codec proc-file to simulate. Get a proc file for the target codec beforehand, or pick up an example codec from the codec proc collections in the tarball. Then, run the program with the proc file, and the hda-emu program will start parsing the codec file and simulates the HD-audio driver:”…”�”}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MUhjwh²hubj£)�”}”(hŒ¥% hda-emu codecs/stac9200-dell-d820-laptop # Parsing.. hda_codec: Unknown model for STAC9200, using BIOS defaults hda_codec: pin nid 08 bios pin config 40c003fa ....”h]”hŒ¥% hda-emu codecs/stac9200-dell-d820-laptop # Parsing.. hda_codec: Unknown model for STAC9200, using BIOS defaults hda_codec: pin nid 08 bios pin config 40c003fa ....”…”�”}”hj¤sbah}”(h]”h ]”h"]”h$]”h&]”j²j³uh1j¢h³hÊh´M]hjwh²hubhÌ)�”}”(hŒüThe program gives you only a very dumb command-line interface. You can get a proc-file dump at the current state, get a list of control (mixer) elements, set/get the control element value, simulate the PCM operation, the jack plugging simulation, etc.”h]”hŒüThe program gives you only a very dumb command-line interface. You can get a proc-file dump at the current state, get a list of control (mixer) elements, set/get the control element value, simulate the PCM operation, the jack plugging simulation, etc.”…”�”}”(hj²h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mdhjwh²hubhÌ)�”}”(hŒ1The program is found in the git repository below:”h]”hŒ1The program is found in the git repository below:”…”�”}”(hjÀh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mihjwh²hubjI)�”}”(hhh]”jN)�”}”(hŒ@git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-emu.git ”h]”hÌ)�”}”(hŒ?git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-emu.git”h]”hŒ?git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-emu.git”…”�”}”(hjÕh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´MkhjÑubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhjÎh²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´Mkhjwh²hubhÌ)�”}”(hŒISee README file in the repository for more details about hda-emu program.”h]”hŒISee README file in the repository for more details about hda-emu program.”…”�”}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mmhjwh²hubeh}”(h]”Œhda-emu”ah ]”h"]”Œhda-emu”ah$]”h&]”uh1hµhj*h²hh³hÊh´MNubh¶)�”}”(hhh]”(h»)�”}”(hŒhda-jack-retask”h]”hŒhda-jack-retask”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´MrubhÌ)�”}”(hX‰hda-jack-retask is a user-friendly GUI program to manipulate the HD-audio pin control for jack retasking. If you have a problem about the jack assignment, try this program and check whether you can get useful results. Once when you figure out the proper pin assignment, it can be fixed either in the driver code statically or via passing a firmware patch file (see "Early Patching" section).”h]”hX�hda-jack-retask is a user-friendly GUI program to manipulate the HD-audio pin control for jack retasking. If you have a problem about the jack assignment, try this program and check whether you can get useful results. Once when you figure out the proper pin assignment, it can be fixed either in the driver code statically or via passing a firmware patch file (see “Early Patchingâ€� section).”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mshjh²hubhÌ)�”}”(hŒ*The program is included in alsa-tools now:”h]”hŒ*The program is included in alsa-tools now:”…”�”}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Mzhjh²hubjI)�”}”(hhh]”jN)�”}”(hŒ)git://git.alsa-project.org/alsa-tools.git”h]”hÌ)�”}”(hj7h]”hŒ)git://git.alsa-project.org/alsa-tools.git”…”�”}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´M|hj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1jMhj2h²hh³hÊh´Nubah}”(h]”h ]”h"]”h$]”h&]”jwjxuh1jHh³hÊh´M|hjh²hubeh}”(h]”Œhda-jack-retask”ah ]”h"]”Œhda-jack-retask”ah$]”h&]”uh1hµhj*h²hh³hÊh´Mrubeh}”(h]”Œ debug-tools”ah ]”h"]”Œ debug tools”ah$]”h&]”uh1hµhh·h²hh³hÊh´MÑubeh}”(h]”Œmore-notes-on-hd-audio-driver”ah ]”h"]”Œmore notes on hd-audio driver”ah$]”h&]”uh1hµhhh²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”j�Œ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”}”(jgjdj~j{j¨j¥j€j}jYjVj j�j•j’j1j.jjjfjcj�jŠj'j$jejbj¶j³jÒ jÏ jTjQjjj�j�j›j˜jñjîjjj_j\jojlj…j‚jjjtjqjjÿjWjTuŒ nametypes”}”(jg‰j~‰j¨‰j€‰jY‰j ‰j•‰j1‰j‰jf‰j�‰j'‰je‰j¶‰jÒ ‰jT‰j‰j�‰j›‰jñ‰j‰j_‰jo‰j…‰j‰jt‰j‰jW‰uh}”(jdh·j{hñj¥j�j}j’jVjƒj�j\j’j«j.j¼jj4jcj jŠjij$j˜jbj©j³jhjÏ j¹jQjÕ jjWj�jj˜j“jîjžjjôj\j*jljIj‚jrjjˆjqjjÿjwjTjuŒ 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”]”(hŒsystem_message”“”)�”}”(hhh]”hÌ)�”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…”�”}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhjñubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”K¨Œsource”hÊuh1jïhj¼h²hh³hÊh´K¨ubjð)�”}”(hhh]”hÌ)�”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhj ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j Œline”M†Œsource”hÊuh1jïhj“h²hh³hÊh´M†ubeŒtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.