Lines Matching refs:codec
17 the codec chips on the HD-audio bus. Linux provides a single driver
27 codec and optionally one modem codec. In theory, there might be
32 The snd-hda-intel driver has several different codec parsers depending
33 on the codec. It has a generic parser as a fallback, but this
35 parser, usually the codec-specific parser (coded in patch_*.c) is used
36 for the codec-specific implementations. The details about the
37 codec-specific problems are explained in the later sections.
88 A less often but a more severe problem is the codec probing. When
89 BIOS reports the available codec slots wrongly, the driver gets
90 confused and tries to access the non-existing codec slot. This often
92 with the codec chips. The symptom appears usually as error messages
102 It means that the codec response isn't notified via an IRQ. The
108 accessing a non-existing codec slot.
111 codec slots via `probe_mask` option. It's a bitmask, and each bit
112 corresponds to the codec slot. For example, to probe only the first
120 driver to probe the codec slots the hardware doesn't report for use.
122 Then the rest 8 bits are passed as the codec slots to probe
124 the codec slots 0 and 1 no matter what the hardware reports.
149 unsupported codec features or the mismatched device configuration.
150 Most of codec-specific code has several preset models, either to
167 that the driver is broken. Many codec-drivers provide the automatic
170 The HD-audio codec has usually "pin" widgets, and BIOS sets the default
174 However -- some codec-support codes, such as patch_analog.c, don't
184 (or codec SSID) from the existing one, you may have a good chance to
186 preset model instead of PCI (and codec-) SSID look-up.
188 What `model` option values are available depends on the codec chip.
189 Check your codec chip from the codec proc file (see "Codec Proc-File"
190 section below). It will show the vendor/product name of your codec
193 and `model` options belonging to each codec. For example, for Realtek
194 ALC262 codec chip, pass `model=ultra` for devices that are compatible
198 non-working HD-audio hardware is to check HD-audio codec and several
203 - when 'nofixup' is passed, the device-specific fixups in the codec
205 - when `generic` is passed, the codec-specific parser is skipped and
229 not on every preset model or codec-support code.
241 certain GPIO. If the codec pin supports EAPD, you have a better
250 codec-communication stall. Some examples are found in
281 is implemented on some codec models but not on every model. Partly
290 codec verbs to the device. Some tools are available: hda-emu and
311 options. Note that each of them corresponds to the codec chip, not
318 (one per each codec), and you have a raw access to the device via
320 codec slot #2 of the first card (#0). For debug-tools such as
335 The codec proc-file is a treasure-chest for debugging HD-audio.
336 It shows most of useful information of each codec widget.
338 The proc file is located in /proc/asound/card*/codec#*, one file per
339 each codec slot. You can know the codec vendor, product id and
345 to the emulator as the primary codec information. See the debug tools
356 codec dynamically without reloading the driver. The following sysfs
357 files are available under each codec-hwdep device directory (e.g.
361 Shows the 32bit codec vendor-id hex number. You can change the
364 Shows the 32bit codec subsystem-id hex number. You can change the
367 Shows the 32bit codec revision-id hex number. You can change the
374 Shows the codec name string. Can be changed by writing to this
384 Shows / stores hint strings for codec parsers for any use.
390 Shows the pin default values set by the codec parser explicitly.
401 Triggers the codec re-configuration. When any value is written to
402 this file, the driver re-initialize and parses the codec tree
406 Resets the codec, removes the mixer elements and PCM stuff of the
407 specified codec, and clear all init verbs and hints.
420 The codec parser have several switches and adjustment knobs for
421 matching better with the actual codec or device behavior. Many of
425 the codec parser will skip the features like auto-mute or mic
485 codec. This can work basically like the reconfiguration via sysfs in
486 the above, but it does it before the first codec configuration.
491 [codec]
508 The file needs to have a line `[codec]`. The next line should contain
509 three numbers indicating the codec vendor-id (0x12345678 in the
510 example), the codec subsystem-id (0xabcd1234) and the address (2) of
511 the codec. The rest patch entries are applied to this specified codec
512 until another codec entry is given. Passing 0 or a negative number to
517 The `[model]` line allows to change the model name of the each codec.
529 Another example to override the codec vendor id from 0x12345678 to
532 [codec]
539 In the similar way, you can override the codec subsystem_id via
541 Also, the codec chip name can be rewritten via `[chip_name]` line.
543 [codec]
603 traces the response from RIRB (only when read from the codec driver).
615 trace what codec command is sent, enable the tracepoint like:
631 Here `[0:0]` indicates the card number and the codec address, and
632 `val` shows the value sent to the codec, respectively. The value is
683 compare the codec registers directly.
708 including the codec proc files, mixer outputs and the control
720 the mixer and PCM but just tries to probe the codec slot. After
721 probing, the proc file is available, so you can get the raw codec
727 to determine the BIOS codec initialization.
733 codec directly. You can execute a raw HD-audio codec verb with this.
738 widget NID, the verb and the parameter. When you access to the codec
802 codec-node connection of a codec chip. It's especially useful when
803 you analyze or debug a codec without a proper datasheet. The program
804 parses the given codec proc file and converts to SVG via graphiz
815 to debug an HD-audio codec without the real hardware. Thus, it
817 dumps the codec register changes and the ALSA-driver internal changes
820 The program requires a codec proc-file to simulate. Get a proc file
821 for the target codec beforehand, or pick up an example codec from the
822 codec proc collections in the tarball. Then, run the program with the
823 proc file, and the hda-emu program will start parsing the codec file