procfile.rst 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238
  1. ==========================
  2. Proc Files of ALSA Drivers
  3. ==========================
  4. Takashi Iwai <[email protected]>
  5. General
  6. =======
  7. ALSA has its own proc tree, /proc/asound. Many useful information are
  8. found in this tree. When you encounter a problem and need debugging,
  9. check the files listed in the following sections.
  10. Each card has its subtree cardX, where X is from 0 to 7. The
  11. card-specific files are stored in the ``card*`` subdirectories.
  12. Global Information
  13. ==================
  14. cards
  15. Shows the list of currently configured ALSA drivers,
  16. index, the id string, short and long descriptions.
  17. version
  18. Shows the version string and compile date.
  19. modules
  20. Lists the module of each card
  21. devices
  22. Lists the ALSA native device mappings.
  23. meminfo
  24. Shows the status of allocated pages via ALSA drivers.
  25. Appears only when ``CONFIG_SND_DEBUG=y``.
  26. hwdep
  27. Lists the currently available hwdep devices in format of
  28. ``<card>-<device>: <name>``
  29. pcm
  30. Lists the currently available PCM devices in format of
  31. ``<card>-<device>: <id>: <name> : <sub-streams>``
  32. timer
  33. Lists the currently available timer devices
  34. oss/devices
  35. Lists the OSS device mappings.
  36. oss/sndstat
  37. Provides the output compatible with /dev/sndstat.
  38. You can symlink this to /dev/sndstat.
  39. Card Specific Files
  40. ===================
  41. The card-specific files are found in ``/proc/asound/card*`` directories.
  42. Some drivers (e.g. cmipci) have their own proc entries for the
  43. register dump, etc (e.g. ``/proc/asound/card*/cmipci`` shows the register
  44. dump). These files would be really helpful for debugging.
  45. When PCM devices are available on this card, you can see directories
  46. like pcm0p or pcm1c. They hold the PCM information for each PCM
  47. stream. The number after ``pcm`` is the PCM device number from 0, and
  48. the last ``p`` or ``c`` means playback or capture direction. The files in
  49. this subtree is described later.
  50. The status of MIDI I/O is found in ``midi*`` files. It shows the device
  51. name and the received/transmitted bytes through the MIDI device.
  52. When the card is equipped with AC97 codecs, there are ``codec97#*``
  53. subdirectories (described later).
  54. When the OSS mixer emulation is enabled (and the module is loaded),
  55. oss_mixer file appears here, too. This shows the current mapping of
  56. OSS mixer elements to the ALSA control elements. You can change the
  57. mapping by writing to this device. Read OSS-Emulation.txt for
  58. details.
  59. PCM Proc Files
  60. ==============
  61. ``card*/pcm*/info``
  62. The general information of this PCM device: card #, device #,
  63. substreams, etc.
  64. ``card*/pcm*/xrun_debug``
  65. This file appears when ``CONFIG_SND_DEBUG=y`` and
  66. ``CONFIG_SND_PCM_XRUN_DEBUG=y``.
  67. This shows the status of xrun (= buffer overrun/xrun) and
  68. invalid PCM position debug/check of ALSA PCM middle layer.
  69. It takes an integer value, can be changed by writing to this
  70. file, such as::
  71. # echo 5 > /proc/asound/card0/pcm0p/xrun_debug
  72. The value consists of the following bit flags:
  73. * bit 0 = Enable XRUN/jiffies debug messages
  74. * bit 1 = Show stack trace at XRUN / jiffies check
  75. * bit 2 = Enable additional jiffies check
  76. When the bit 0 is set, the driver will show the messages to
  77. kernel log when an xrun is detected. The debug message is
  78. shown also when the invalid H/W pointer is detected at the
  79. update of periods (usually called from the interrupt
  80. handler).
  81. When the bit 1 is set, the driver will show the stack trace
  82. additionally. This may help the debugging.
  83. Since 2.6.30, this option can enable the hwptr check using
  84. jiffies. This detects spontaneous invalid pointer callback
  85. values, but can be lead to too much corrections for a (mostly
  86. buggy) hardware that doesn't give smooth pointer updates.
  87. This feature is enabled via the bit 2.
  88. ``card*/pcm*/sub*/info``
  89. The general information of this PCM sub-stream.
  90. ``card*/pcm*/sub*/status``
  91. The current status of this PCM sub-stream, elapsed time,
  92. H/W position, etc.
  93. ``card*/pcm*/sub*/hw_params``
  94. The hardware parameters set for this sub-stream.
  95. ``card*/pcm*/sub*/sw_params``
  96. The soft parameters set for this sub-stream.
  97. ``card*/pcm*/sub*/prealloc``
  98. The buffer pre-allocation information.
  99. ``card*/pcm*/sub*/xrun_injection``
  100. Triggers an XRUN to the running stream when any value is
  101. written to this proc file. Used for fault injection.
  102. This entry is write-only.
  103. AC97 Codec Information
  104. ======================
  105. ``card*/codec97#*/ac97#?-?``
  106. Shows the general information of this AC97 codec chip, such as
  107. name, capabilities, set up.
  108. ``card*/codec97#0/ac97#?-?+regs``
  109. Shows the AC97 register dump. Useful for debugging.
  110. When CONFIG_SND_DEBUG is enabled, you can write to this file for
  111. changing an AC97 register directly. Pass two hex numbers.
  112. For example,
  113. ::
  114. # echo 02 9f1f > /proc/asound/card0/codec97#0/ac97#0-0+regs
  115. USB Audio Streams
  116. =================
  117. ``card*/stream*``
  118. Shows the assignment and the current status of each audio stream
  119. of the given card. This information is very useful for debugging.
  120. HD-Audio Codecs
  121. ===============
  122. ``card*/codec#*``
  123. Shows the general codec information and the attribute of each
  124. widget node.
  125. ``card*/eld#*``
  126. Available for HDMI or DisplayPort interfaces.
  127. Shows ELD(EDID Like Data) info retrieved from the attached HDMI sink,
  128. and describes its audio capabilities and configurations.
  129. Some ELD fields may be modified by doing ``echo name hex_value > eld#*``.
  130. Only do this if you are sure the HDMI sink provided value is wrong.
  131. And if that makes your HDMI audio work, please report to us so that we
  132. can fix it in future kernel releases.
  133. Sequencer Information
  134. =====================
  135. seq/drivers
  136. Lists the currently available ALSA sequencer drivers.
  137. seq/clients
  138. Shows the list of currently available sequencer clients and
  139. ports. The connection status and the running status are shown
  140. in this file, too.
  141. seq/queues
  142. Lists the currently allocated/running sequencer queues.
  143. seq/timer
  144. Lists the currently allocated/running sequencer timers.
  145. seq/oss
  146. Lists the OSS-compatible sequencer stuffs.
  147. Help For Debugging?
  148. ===================
  149. When the problem is related with PCM, first try to turn on xrun_debug
  150. mode. This will give you the kernel messages when and where xrun
  151. happened.
  152. If it's really a bug, report it with the following information:
  153. - the name of the driver/card, show in ``/proc/asound/cards``
  154. - the register dump, if available (e.g. ``card*/cmipci``)
  155. when it's a PCM problem,
  156. - set-up of PCM, shown in hw_parms, sw_params, and status in the PCM
  157. sub-stream directory
  158. when it's a mixer problem,
  159. - AC97 proc files, ``codec97#*/*`` files
  160. for USB audio/midi,
  161. - output of ``lsusb -v``
  162. - ``stream*`` files in card directory
  163. The ALSA bug-tracking system is found at:
  164. https://bugtrack.alsa-project.org/alsa-bug/