sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget(/translations/zh_CN/sound/hd-audio/notesmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget(/translations/zh_TW/sound/hd-audio/notesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget(/translations/it_IT/sound/hd-audio/notesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget(/translations/ja_JP/sound/hd-audio/notesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget(/translations/ko_KR/sound/hd-audio/notesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget(/translations/sp_SP/sound/hd-audio/notesmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhsection)}(hhh](htitle)}(hMore Notes on HD-Audio Driverh]hMore Notes on HD-Audio Driver}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhB/var/lib/git/docbuild/linux/Documentation/sound/hd-audio/notes.rsthKubh paragraph)}(hTakashi Iwai h](hTakashi Iwai <}(hhhhhNhNubh reference)}(h tiwai@suse.deh]h tiwai@suse.de}(hhhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:tiwai@suse.deuh1hhhubh>}(hhhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hhh](h)}(hGeneralh]hGeneral}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhK 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.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(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.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(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.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hXThe 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]hXThe 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK"hhhhubh)}(hIf 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]hIf 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&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK)hhhhubh bullet_list)}(hhh]h list_item)}(h\https://www.intel.com/content/www/us/en/standards/high-definition-audio-specification.html h]h)}(hZhttps://www.intel.com/content/www/us/en/standards/high-definition-audio-specification.htmlh]h)}(hjAh]hZhttps://www.intel.com/content/www/us/en/standards/high-definition-audio-specification.html}(hjChhhNhNubah}(h]h ]h"]h$]h&]refurijAuh1hhj?ubah}(h]h ]h"]h$]h&]uh1hhhhK-hj;ubah}(h]h ]h"]h$]h&]uh1j9hj6hhhhhNubah}(h]h ]h"]h$]h&]bullet*uh1j4hhhK-hhhhubeh}(h]generalah ]h"]generalah$]h&]uh1hhhhhhhhK ubh)}(hhh](h)}(hHD-Audio Controllerh]hHD-Audio Controller}(hjphhhNhNubah}(h]h ]h"]h$]h&]uh1hhjmhhhhhK1ubh)}(hhh](h)}(hDMA-Position Problemh]hDMA-Position Problem}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhj~hhhhhK4ubh)}(hXThe 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](hXThe 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 }(hjhhhNhNubhliteral)}(h``position_fix``h]h position_fix}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh option.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK5hj~hhubh)}(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]hposition_fix=1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh& means to use LPIB method explicitly. }(hjhhhNhNubj)}(h``position_fix=2``h]hposition_fix=2}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh# means to use the position-buffer. }(hjhhhNhNubj)}(h``position_fix=3``h]hposition_fix=3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh 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. }(hjhhhNhNubj)}(h``position_fix=4``h]hposition_fix=4}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh is another combination available for all controllers, and uses LPIB for the playback and the position-buffer for the capture streams. }(hjhhhNhNubj)}(h``position_fix=5``h]hposition_fix=5}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh is specific to Intel platforms, so far, for Skylake and onward. It applies the delay calculation for the precise position reporting. }(hjhhhNhNubj)}(h``position_fix=6``h]hposition_fix=6}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhX 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.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK=hj~hhubh)}(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'hhhNhNubj)}(h``bdl_pos_adj``h]h bdl_pos_adj}(hj/hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj'ubh option.}(hj'hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKOhj~hhubh)}(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](hWhen }(hjGhhhNhNubj)}(h``bdl_pos_adj``h]h bdl_pos_adj}(hjOhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjGubhX- 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.}(hjGhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKVhj~hhubeh}(h]dma-position-problemah ]h"]dma-position problemah$]h&]uh1hhjmhhhhhK4ubh)}(hhh](h)}(hCodec-Probing Problemh]hCodec-Probing Problem}(hjrhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjohhhhhK^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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK_hjohhubh literal_block)}(hhda_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=0x12345678h]hhda_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}hjsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1jhhhKghjohhubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKlhjohhubh)}(hThe 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]hThe 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKqhjohhubh)}(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](hTThus, if the second error message appears, try to narrow the probed codec slots via }(hjhhhNhNubj)}(h``probe_mask``h]h probe_mask}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhy option. It’s a bitmask, and each bit corresponds to the codec slot. For example, to probe only the first slot, pass }(hjhhhNhNubj)}(h``probe_mask=1``h]h probe_mask=1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh+. For the first and the third slots, pass }(hjhhhNhNubj)}(h``probe_mask=5``h]h probe_mask=5}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh (where 5 = 1 | 4), and so on.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKuhjohhubh)}(hlSince 2.6.29 kernel, the driver has a more robust probing method, so this error might happen rarely, though.h]hlSince 2.6.29 kernel, the driver has a more robust probing method, so this error might happen rarely, though.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK{hjohhubh)}(hXOn 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](hOn 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 }(hjhhhNhNubj)}(h``probe_mask``h]h probe_mask}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhg option on. Then the rest 8 bits are passed as the codec slots to probe unconditionally. For example, }(hjhhhNhNubj)}(h``probe_mask=0x103``h]hprobe_mask=0x103}(hj(hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhQ will force to probe the codec slots 0 and 1 no matter what the hardware reports.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK~hjohhubeh}(h]codec-probing-problemah ]h"]codec-probing problemah$]h&]uh1hhjmhhhhhK^ubh)}(hhh](h)}(hInterrupt Handlingh]hInterrupt Handling}(hjKhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjHhhhhhKubh)}(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.}(hjYhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjHhhubh)}(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](hThere 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 }(hjghhhNhNubj)}(h``enable_msi=0``h]h enable_msi=0}(hjohhhNhNubah}(h]h ]h"]h$]h&]uh1jhjgubh 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.}(hjghhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjHhhubeh}(h]interrupt-handlingah ]h"]interrupt handlingah$]h&]uh1hhjmhhhhhKubeh}(h]hd-audio-controllerah ]h"]hd-audio controllerah$]h&]uh1hhhhhhhhK1ubh)}(hhh](h)}(hHD-Audio Codech]hHD-Audio Codec}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(h Model Optionh]h Model Option}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hThe 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]hThe 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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj)}(h%hda_codec: ALC880: BIOS auto-probing.h]h%hda_codec: ALC880: BIOS auto-probing.}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjhhubh)}(hDMeanwhile, in the earlier versions, you would see a message like: ::h]hAMeanwhile, in the earlier versions, you would see a message like:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj)}(hChda_codec: Unknown model for ALC880, trying auto-probe from BIOS...h]hChda_codec: Unknown model for ALC880, trying auto-probe from BIOS...}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjhhubh)}(hXEven 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]hXEven 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXThe 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]hXThe 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 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(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 re-use the same model. You can pass the ``model`` option to specify the preset model instead of PCI (and codec-) SSID look-up.h](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 re-use the same model. You can pass the }(hjhhhNhNubj)}(h ``model``h]hmodel}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhM option to specify the preset model instead of PCI (and codec-) SSID look-up.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXWhat ``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](hWhat }(hj;hhhNhNubj)}(h ``model``h]hmodel}(hjChhhNhNubah}(h]h ]h"]h$]h&]uh1jhj;ubhXH 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 }(hj;hhhNhNubj)}(h ``model``h]hmodel}(hjUhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj;ubhT options belonging to each codec. For example, for Realtek ALC262 codec chip, pass }(hj;hhhNhNubj)}(h``model=ultra``h]h model=ultra}(hjghhhNhNubah}(h]h ]h"]h$]h&]uh1jhj;ubh7 for devices that are compatible with Samsung Q1 Ultra.}(hj;hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hThus, 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](hThus, 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 }(hjhhhNhNubj)}(h ``model``h]hmodel}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhU option values. If you have any luck, some of them might suit with your device well.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h,There are a few special model option values:h]h,There are a few special model option values:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj5)}(hhh](j:)}(hUwhen 'nofixup' is passed, the device-specific fixups in the codec parser are skipped.h]h)}(hUwhen 'nofixup' is passed, the device-specific fixups in the codec parser are skipped.h]hYwhen ‘nofixup’ is passed, the device-specific fixups in the codec parser are skipped.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(hfwhen ``generic`` is passed, the codec-specific parser is skipped and only the generic parser is used. h]h)}(hewhen ``generic`` is passed, the codec-specific parser is skipped and only the generic parser is used.h](hwhen }(hjhhhNhNubj)}(h ``generic``h]hgeneric}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhU is passed, the codec-specific parser is skipped and only the generic parser is used.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubeh}(h]h ]h"]h$]h&]jcjduh1j4hhhKhjhhubh)}(hXA 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](hwA 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 }(hjhhhNhNubj)}(h``model=XXXX:YYYY``h]hmodel=XXXX:YYYY}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhX 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.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h] model-optionah ]h"] model optionah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hSpeaker and Headphone Outputh]hSpeaker and Headphone Output}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhKubh)}(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.}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(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.}(hj?hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hqDitto for the speaker output. There can be "External Amplifier" switch on some codecs. Turn on this if present.h]huDitto for the speaker output. There can be “External Amplifier” switch on some codecs. Turn on this if present.}(hjMhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hAnother 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]hAnother 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.}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hIn 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]hIn 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.}(hjihhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hNIf you are masochistic enough to debug the driver problem, note the following:h]hNIf you are masochistic enough to debug the driver problem, note the following:}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj hhubj5)}(hhh](j:)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(hpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.h]h)}(hpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.h]hpSome Realtek codecs require special vendor-specific coefficients to turn on the amplifier. See patch_realtek.c.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(hbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.h]h)}(hbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.h]hbIDT codecs may have extra power-enable/disable controls on each analog pin. See patch_sigmatel.c.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(hVery 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)}(hVery 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]hVery 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubeh}(h]h ]h"]h$]h&]jcjduh1j4hhhMhj hhubeh}(h]speaker-and-headphone-outputah ]h"]speaker and headphone outputah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hCapture Problemsh]hCapture Problems}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hIt'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]hIt’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.}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM%hjhhubh)}(hMost 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]hMost 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.}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM)hjhhubh)}(hThe 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]hThe 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.}(hj?hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM-hjhhubeh}(h]capture-problemsah ]h"]capture problemsah$]h&]uh1hhjhhhhhMubh)}(hhh](h)}(hDirect Debuggingh]hDirect Debugging}(hjXhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjUhhhhhM4ubh)}(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.}(hjfhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM5hjUhhubeh}(h]direct-debuggingah ]h"]direct debuggingah$]h&]uh1hhjhhhhhM4ubeh}(h]hd-audio-codecah ]h"]hd-audio codecah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h Other Issuesh]h Other Issues}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhM>ubh)}(hhh](h)}(hKernel Configurationh]hKernel Configuration}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMAubh)}(hIn 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, }(hjhhhNhNubj)}(h``CONFIG_SND_DEBUG=y``h]hCONFIG_SND_DEBUG=y}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh-, no matter whether you are debugging or not.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMBhjhhubh)}(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 }(hjhhhNhNubj)}(h``CONFIG_SND_HDA_CODEC_*``h]hCONFIG_SND_HDA_CODEC_*}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh 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.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMEhjhhubh)}(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]hCONFIG_SND_HDA_HWDEP}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh 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, }(hjhhhNhNubj)}(h ``hwC0D2``h]hhwC0D2}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh 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.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMKhjhhubh)}(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]hCONFIG_SND_HDA_RECONFIG}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh 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.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMShjhhubh)}(hh``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]hCONFIG_SND_HDA_POWER_SAVE}(hj4hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj0ubhO option enables the power-saving feature. See “Power-saving” section below.}(hj0hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMXhjhhubeh}(h]kernel-configurationah ]h"]kernel configurationah$]h&]uh1hhjhhhhhMAubh)}(hhh](h)}(hCodec Proc-Fileh]hCodec Proc-File}(hjWhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjThhhhhM]ubh)}(hyThe codec proc-file is a treasure-chest for debugging HD-audio. It shows most of useful information of each codec widget.h]hyThe codec proc-file is a treasure-chest for debugging HD-audio. It shows most of useful information of each codec widget.}(hjehhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM^hjThhubh)}(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.}(hjshhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMahjThhubh)}(hThis 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]hThis 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMghjThhubh)}(hThis 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]hThis 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”.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMkhjThhubeh}(h]codec-proc-fileah ]h"]codec proc-fileah$]h&]uh1hhjhhhhhM]ubh)}(hhh](h)}(hHD-Audio Reconfigurationh]hHD-Audio Reconfiguration}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMqubh)}(hThis 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]hThis 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):}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMrhjhhubhdefinition_list)}(hhh](hdefinition_list_item)}(hrvendor_id Shows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.h](hterm)}(h vendor_idh]h vendor_id}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMxhjubh definition)}(hhh]h)}(hhShows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.h]hhShows the 32bit codec vendor-id hex number. You can change the vendor-id value by writing to this file.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMxhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMxhjubj)}(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_idh]h subsystem_id}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhM{hjubj)}(hhh]h)}(hnShows the 32bit codec subsystem-id hex number. You can change the subsystem-id value by writing to this file.h]hnShows the 32bit codec subsystem-id hex number. You can change the subsystem-id value by writing to this file.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM{hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhM{hjhhubj)}(hxrevision_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_idh]h revision_id}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhM~hj-ubj)}(hhh]h)}(hlShows the 32bit codec revision-id hex number. You can change the revision-id value by writing to this file.h]hlShows the 32bit codec revision-id hex number. You can change the revision-id value by writing to this file.}(hjBhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM~hj?ubah}(h]h ]h"]h$]h&]uh1jhj-ubeh}(h]h ]h"]h$]h&]uh1jhhhM~hjhhubj)}(h)afg Shows the AFG ID. This is read-only.h](j)}(hafgh]hafg}(hj`hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj\ubj)}(hhh]h)}(h%Shows the AFG ID. This is read-only.h]h%Shows the AFG ID. This is read-only.}(hjqhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjnubah}(h]h ]h"]h$]h&]uh1jhj\ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(h)mfg Shows the MFG ID. This is read-only.h](j)}(hmfgh]hmfg}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(h%Shows the MFG ID. This is read-only.h]h%Shows the MFG ID. This is read-only.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(hJname Shows the codec name string. Can be changed by writing to this file.h](j)}(hnameh]hname}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(hEShows the codec name string. Can be changed by writing to this file.h]hEShows the codec name string. Can be changed by writing to this file.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(h\modelname Shows the currently set ``model`` option. Can be changed by writing to this file.h](j)}(h modelnameh]h modelname}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(hRShows the currently set ``model`` option. Can be changed by writing to this file.h](hShows the currently set }(hjhhhNhNubj)}(h ``model``h]hmodel}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh1 option. Can be changed by writing to this file.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(hinit_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_verbsh]h init_verbs}(hj. hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj* ubj)}(hhh]h)}(hThe 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]hThe 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).}(hj? hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj< ubah}(h]h ]h"]h$]h&]uh1jhj* ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(hhints 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)}(hhintsh]hhints}(hj] hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjY ubj)}(hhh]h)}(hShows / 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](hIShows / stores hint strings for codec parsers for any use. Its format is }(hjn hhhNhNubj)}(h``key = value``h]h key = value}(hjv hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjn ubh. For example, passing }(hjn hhhNhNubj)}(h``jack_detect = no``h]hjack_detect = no}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjn ubh; will disable the jack detection of the machine completely.}(hjn hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhjk ubah}(h]h ]h"]h$]h&]uh1jhjY ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(hIinit_pin_configs Shows the initial pin default config values set by BIOS.h](j)}(hinit_pin_configsh]hinit_pin_configs}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubj)}(hhh]h)}(h8Shows the initial pin default config values set by BIOS.h]h8Shows the initial pin default config values set by BIOS.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(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)}(hdriver_pin_configsh]hdriver_pin_configs}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubj)}(hhh]h)}(hShows 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]hShows 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 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(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)}(huser_pin_configsh]huser_pin_configs}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj 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.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(hreconfig 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)}(hreconfigh]hreconfig}(hj= hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj9 ubj)}(hhh]h)}(hTriggers 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]hTriggers 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.}(hjN hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjK ubah}(h]h ]h"]h$]h&]uh1jhj9 ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubj)}(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)}(hclearh]hclear}(hjl hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjh ubj)}(hhh]h)}(hvResets the codec, removes the mixer elements and PCM stuff of the specified codec, and clear all init verbs and hints.h]hvResets the codec, removes the mixer elements and PCM stuff of the specified codec, and clear all init verbs and hints.}(hj} hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjz ubah}(h]h ]h"]h$]h&]uh1jhjh ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubeh}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(hFor 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]hFor 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 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hm# echo 0x14 0x9993013f > /sys/class/sound/hwC0D0/user_pin_configs # echo 1 > /sys/class/sound/hwC0D0/reconfigh]hm# echo 0x14 0x9993013f > /sys/class/sound/hwC0D0/user_pin_configs # echo 1 > /sys/class/sound/hwC0D0/reconfig}hj sbah}(h]h ]h"]h$]h&]jjuh1jhhhMhjhhubeh}(h]hd-audio-reconfigurationah ]h"]hd-audio reconfigurationah$]h&]uh1hhjhhhhhMqubh)}(hhh](h)}(h Hint Stringsh]h Hint Strings}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhMubh)}(hXThe 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](hThe 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 hhhNhNubj)}(h``jack_detect = no``h]hjack_detect = no}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj 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 hhhNhNubj)}(h``yes``h]hyes}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh, }(hj hhhNhNubj)}(h``no``h]hno}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh, }hj sbj)}(h``true``h]htrue}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh, }hj sbj)}(h ``false``h]hfalse}(hj" hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh, }(hj hhhNhNubj)}(h``1``h]h1}(hj4 hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh or }(hj hhhNhNubj)}(h``0``h]h0}(hjF hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj ubh can be passed.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj hhubh)}(h0The generic parser supports the following hints:h]h0The generic parser supports the following hints:}(hj^ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj hhubj)}(hhh](j)}(hgjack_detect (bool) specify whether the jack detection is available at all on this machine; default trueh](j)}(hjack_detect (bool)h]hjack_detect (bool)}(hjs hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjo ubj)}(hhh]h)}(hTspecify whether the jack detection is available at all on this machine; default trueh]hTspecify whether the jack detection is available at all on this machine; default true}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhjo ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjl ubj)}(hJinv_jack_detect (bool) indicates that the jack detection logic is invertedh](j)}(hinv_jack_detect (bool)h]hinv_jack_detect (bool)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubj)}(hhh]h)}(h3indicates that the jack detection logic is invertedh]h3indicates that the jack detection logic is inverted}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjl hhubj)}(hltrigger_sense (bool) indicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verbh](j)}(htrigger_sense (bool)h]htrigger_sense (bool)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubj)}(hhh]h)}(hWindicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verbh]hWindicates that the jack detection needs the explicit call of AC_VERB_SET_PIN_SENSE verb}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhhhMhjl hhubj)}(hLinv_eapd (bool) indicates that the EAPD is implemented in the inverted logich](j)}(hinv_eapd (bool)h]hinv_eapd (bool)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubj)}(hhh]h)}(hhjChhubj)}(hl[codec] 0x12345678 0xabcd1234 2 [subsystem_id] 0xffff1111 [revision_id] 0x10 [chip_name] My-own NEWS-0002h]hl[codec] 0x12345678 0xabcd1234 2 [subsystem_id] 0xffff1111 [revision_id] 0x10 [chip_name] My-own NEWS-0002}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhMChjChhubh)}(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](hThe 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 }(hjhhhNhNubj)}(h``patch=hda-init.fw``h]hpatch=hda-init.fw}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh5, the file /lib/firmware/hda-init.fw must be present.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMPhjChhubh)}(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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMVhjChhubj)}(h5options snd-hda-intel patch=on-board-patch,hdmi-patchh]h5options snd-hda-intel patch=on-board-patch,hdmi-patch}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhM\hjChhubeh}(h]early-patchingah ]h"]early patchingah$]h&]uh1hhjhhhhhMubh)}(hhh](h)}(h Power-Savingh]h Power-Saving}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhM`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](hThe 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 }(hjhhhNhNubj)}(h``power_save``h]h power_save}(hj#hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhE module option, and this option can be changed dynamically via sysfs.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMahj hhubh)}(hThe 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]hThe 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.}(hj;hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMghj hhubh)}(hXThe 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]hXThe 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.}(hjIhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMkhj hhubh)}(hXThe 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 }(hjWhhhNhNubj)}(h``power_save_controller``h]hpower_save_controller}(hj_hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjWubhS option, which is also available at /sys/module/snd_hda_intel/parameters directory.}(hjWhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMshj hhubeh}(h] power-savingah ]h"] power-savingah$]h&]uh1hhjhhhhhM`ubh)}(hhh](h)}(h Tracepointsh]h Tracepoints}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhM|ubh)}(hXThe 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](h3The hd-audio driver gives a few basic tracepoints. }(hjhhhNhNubj)}(h``hda:hda_send_cmd``h]hhda:hda_send_cmd}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh traces each CORB write while }(hjhhhNhNubj)}(h``hda:hda_get_response``h]hhda:hda_get_response}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhG traces the response from RIRB (only when read from the codec driver). }(hjhhhNhNubj)}(h``hda:hda_bus_reset``h]hhda:hda_bus_reset}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh/ traces the bus-reset due to fatal error, etc, }(hjhhhNhNubj)}(h``hda:hda_unsol_event``h]hhda:hda_unsol_event}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh$ traces the unsolicited events, and }(hjhhhNhNubj)}(h``hda:hda_power_down``h]hhda:hda_power_down}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh and }(hjhhhNhNubj)}(h``hda:hda_power_up``h]hhda:hda_power_up}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh3 trace the power down/up via power-saving behavior.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhM}hjhhubh)}(h,Enabling all tracepoints can be done like ::h]h)Enabling all tracepoints can be done like}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(h0# echo 1 > /sys/kernel/tracing/events/hda/enableh]h0# echo 1 > /sys/kernel/tracing/events/hda/enable}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhMhjhhubh)}(hthen 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]hthen 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&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(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=e3901ah]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}hj4sbah}(h]h ]h"]h$]h&]jjuh1jhhhMhjhhubh)}(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](hHere }(hjBhhhNhNubj)}(h ``[0:0]``h]h[0:0]}(hjJhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjBubh6 indicates the card number and the codec address, and }(hjBhhhNhNubj)}(h``val``h]hval}(hj\hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjBubh 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.}(hjBhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(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=25h]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}hjtsbah}(h]h ]h"]h$]h&]jjuh1jhhhMhjhhubeh}(h] tracepointsah ]h"] tracepointsah$]h&]uh1hhjhhhhhM|ubh)}(hhh](h)}(hDevelopment Treeh]hDevelopment Tree}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hFThe latest development codes for HD-audio are found on sound git tree:h]hFThe latest development codes for HD-audio are found on sound git tree:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj5)}(hhh]j:)}(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.gith]h=git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhMhjhhubh)}(hThe 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]hThe 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubeh}(h]development-treeah ]h"]development treeah$]h&]uh1hhjhhhhhMubh)}(hhh](h)}(hSending a Bug Reporth]hSending a Bug Report}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hIf 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]hIf 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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj5)}(hhh](j:)}(h(Hardware vendor, product and model namesh]h)}(hjh]h(Hardware vendor, product and model names}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(h@Kernel version (and ALSA-driver version if you built externally)h]h)}(hjh]h@Kernel version (and ALSA-driver version if you built externally)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubj:)}(ha``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-infoh](j)}(h``alsa-info.sh``h]h alsa-info.sh}(hj8hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj4ubh output; run with }(hj4hhhNhNubj)}(h``--no-upload``h]h --no-upload}(hjJhhhNhNubah}(h]h ]h"]h$]h&]uh1jhj4ubh/ option. See the section below about alsa-info}(hj4hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj0ubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubeh}(h]h ]h"]h$]h&]jcjduh1j4hhhMhjhhubh)}(hIf 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]hIf 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.}(hjnhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h'Send a bug report either the following:h]h'Send a bug report either the following:}(hj|hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hhh](j)}(h,kernel-bugzilla https://bugzilla.kernel.org/h](j)}(hkernel-bugzillah]hkernel-bugzilla}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(hhttps://bugzilla.kernel.org/h]h)}(hjh]hhttps://bugzilla.kernel.org/}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1hhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(h+alsa-devel ML alsa-devel@alsa-project.org h](j)}(h alsa-devel MLh]h alsa-devel ML}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjubj)}(hhh]h)}(halsa-devel@alsa-project.orgh]h)}(hjh]halsa-devel@alsa-project.org}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri"mailto:alsa-devel@alsa-project.orguh1hhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhMhjhhubeh}(h]h ]h"]h$]h&]uh1jhjhhhhhNubeh}(h]sending-a-bug-reportah ]h"]sending a bug reportah$]h&]uh1hhjhhhhhMubeh}(h] other-issuesah ]h"] other issuesah$]h&]uh1hhhhhhhhM>ubh)}(hhh](h)}(h Debug Toolsh]h Debug Tools}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hLThis section describes some tools available for debugging HD-audio problems.h]hLThis section describes some tools available for debugging HD-audio problems.}(hj'hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hhh](h)}(h alsa-infoh]h alsa-info}(hj8hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj5hhhhhMubh)}(hThe 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 }(hjFhhhNhNubj)}(h``alsa-info.sh``h]h alsa-info.sh}(hjNhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjFubh 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:}(hjFhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj5hhubj5)}(hhh]j:)}(h*git://git.alsa-project.org/alsa-utils.git h]h)}(h)git://git.alsa-project.org/alsa-utils.gith]h)git://git.alsa-project.org/alsa-utils.git}(hjmhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjiubah}(h]h ]h"]h$]h&]uh1j9hjfhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhMhj5hhubh)}(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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj5hhubj5)}(hhh]j:)}(h*https://www.alsa-project.org/alsa-info.sh h]h)}(h)https://www.alsa-project.org/alsa-info.shh]h)}(hjh]h)https://www.alsa-project.org/alsa-info.sh}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1hhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhMhj5hhubh)}(hXRun 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 }(hjhhhNhNubj)}(h``--no-upload``h]h --no-upload}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh' option, and attach the generated file.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj5hhubh)}(hOThere are some other useful options. See ``--help`` option output for details.h](h*There are some other useful options. See }(hjhhhNhNubj)}(h ``--help``h]h--help}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh option output for details.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj5hhubh)}(hXWhen 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 }(hjhhhNhNubj)}(h``probe_only=1``h]h probe_only=1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhXR 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 }(hjhhhNhNubj)}(h``probe_only=1``h]h probe_only=1}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubhh. But you can continue the configuration via hwdep sysfs file if hda-reconfig option is enabled. Using }(hjhhhNhNubj)}(h``probe_only``h]h probe_only}(hj,hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh+ mask 2 skips the reset of HDA codecs (use }(hjhhhNhNubj)}(h``probe_only=3``h]h probe_only=3}(hj>hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjubh_ as module option). The hwdep interface can be used to determine the BIOS codec initialization.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj5hhubeh}(h] alsa-infoah ]h"] alsa-infoah$]h&]uh1hhjhhhhhMubh)}(hhh](h)}(hhda-verbh]hhda-verb}(hjahhhNhNubah}(h]h ]h"]h$]h&]uh1hhj^hhhhhMubh)}(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](hhda-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 }(hjohhhNhNubj)}(h``CONFIG_SND_HDA_HWDEP=y``h]hCONFIG_SND_HDA_HWDEP=y}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1jhjoubh beforehand.}(hjohhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMhj^hhubh)}(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.)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj^hhubh)}(hThe 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]hThe 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj^hhubj)}(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 = 0x0h]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}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhMhj^hhubh)}(hAlthough 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]hAlthough 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj^hhubh)}(h3The hda-verb program is included now in alsa-tools:h]h3The hda-verb program is included now in alsa-tools:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hj^hhubj5)}(hhh]j:)}(h*git://git.alsa-project.org/alsa-tools.git h]h)}(h)git://git.alsa-project.org/alsa-tools.gith]h)git://git.alsa-project.org/alsa-tools.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM"hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM"hj^hhubh)}(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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM$hj^hhubj5)}(hhh]j:)}(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/}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurij uh1hhj ubah}(h]h ]h"]h$]h&]uh1hhhhM&hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM&hj^hhubh)}(h#Also a git repository is available:h]h#Also a git repository is available:}(hj/hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM(hj^hhubj5)}(hhh]j:)}(hAgit://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.gith]h@git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-verb.git}(hjDhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM*hj@ubah}(h]h ]h"]h$]h&]uh1j9hj=hhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM*hj^hhubh)}(hGSee README file in the tarball for more details about hda-verb program.h]hGSee README file in the tarball for more details about hda-verb program.}(hj^hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM,hj^hhubeh}(h]hda-verbah ]h"]hda-verbah$]h&]uh1hhjhhhhhMubh)}(hhh](h)}(h hda-analyzerh]h hda-analyzer}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjthhhhhM1ubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM2hjthhubh)}(hThe hda-analyzer:h]hThe hda-analyzer:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM8hjthhubj5)}(hhh]j:)}(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-analyzerh]h)}(hjh]h>https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1hhjubah}(h]h ]h"]h$]h&]uh1hhhhM:hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM:hjthhubh)}(h5is a part of alsa.git repository in alsa-project.org:h]h5is a part of alsa.git repository in alsa-project.org:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM<hjthhubj5)}(hhh]j:)}(h$git://git.alsa-project.org/alsa.git h]h)}(h#git://git.alsa-project.org/alsa.gith]h#git://git.alsa-project.org/alsa.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM>hjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM>hjthhubeh}(h] hda-analyzerah ]h"] hda-analyzerah$]h&]uh1hhjhhhhhM1ubh)}(hhh](h)}(h Codecgraphh]h Codecgraph}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMAubh)}(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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMBhjhhubh)}(h7The tarball and GIT trees are found in the web page at:h]h7The tarball and GIT trees are found in the web page at:}(hj"hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMHhjhhubj5)}(hhh]j:)}(h!http://helllabs.org/codecgraph/ h]h)}(hhttp://helllabs.org/codecgraph/h]h)}(hj9h]hhttp://helllabs.org/codecgraph/}(hj;hhhNhNubah}(h]h ]h"]h$]h&]refurij9uh1hhj7ubah}(h]h ]h"]h$]h&]uh1hhhhMJhj3ubah}(h]h ]h"]h$]h&]uh1j9hj0hhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhMJhjhhubeh}(h] codecgraphah ]h"] codecgraphah$]h&]uh1hhjhhhhhMAubh)}(hhh](h)}(hhda-emuh]hhda-emu}(hjfhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjchhhhhMNubh)}(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.}(hjthhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMOhjchhubh)}(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:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMUhjchhubj)}(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 ....}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhM]hjchhubh)}(hThe 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]hThe 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.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMdhjchhubh)}(h1The program is found in the git repository below:h]h1The program is found in the git repository below:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMihjchhubj5)}(hhh]j:)}(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.gith]h?git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-emu.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMkhjubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhMkhjchhubh)}(hISee README file in the repository for more details about hda-emu program.h]hISee README file in the repository for more details about hda-emu program.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMmhjchhubeh}(h]hda-emuah ]h"]hda-emuah$]h&]uh1hhjhhhhhMNubh)}(hhh](h)}(hhda-jack-retaskh]hhda-jack-retask}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMrubh)}(hXhda-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]hXhda-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).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMshjhhubh)}(h*The program is included in alsa-tools now:h]h*The program is included in alsa-tools now:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMzhjhhubj5)}(hhh]j:)}(h)git://git.alsa-project.org/alsa-tools.gith]h)}(hj#h]h)git://git.alsa-project.org/alsa-tools.git}(hj%hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM|hj!ubah}(h]h ]h"]h$]h&]uh1j9hjhhhhhNubah}(h]h ]h"]h$]h&]jcjduh1j4hhhM|hjhhubeh}(h]hda-jack-retaskah ]h"]hda-jack-retaskah$]h&]uh1hhjhhhhhMrubeh}(h] debug-toolsah ]h"] debug toolsah$]h&]uh1hhhhhhhhMubeh}(h]more-notes-on-hd-audio-driverah ]h"]more notes on hd-audio driverah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksentryfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjyerror_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceh _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}nameids}(jSjPjjjgjjjljijEjBjjjj~jjjjjRjOjyjvjjjQjNjjj j j@j=jjj|jyjjjjj jjKjHj[jXjqjnjjj`j]jjjCj@u nametypes}(jSjjjjljEjjjjjRjyjjQjj j@jj|jjj jKj[jqjj`jjCuh}(jPhjghjjmjij~jBjojjHj~jjjjj jOjjvjUjjjNjjjTj jj=j jjCjyj jjjjjjjHjjXj5jnj^jjtj]jjjcj@ju footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages](hsystem_message)}(hhh]h)}(hfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.h]hhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypeINFOlineKsourcehuh1jhjhhhhhKubj)}(hhh]h)}(hfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.h]hhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypejlineMsourcehuh1jhjhhhhhMubetransform_messages] transformerN include_log] decorationNhhub.