1 # ALSA soundcard-configuration
16 tristate "Sequencer support"
19 Say Y or M to enable MIDI sequencer and router support. This
20 feature allows routing and enqueueing of MIDI events. Events
21 can be processed at a given time.
23 Many programs require this feature, so you should enable it
24 unless you know what you're doing.
27 tristate "Sequencer dummy client"
28 depends on SND_SEQUENCER
30 Say Y here to enable the dummy sequencer client. This client
31 is a simple MIDI-through client: all normal input events are
32 redirected to the output port immediately.
34 You don't need this unless you want to connect many MIDI
35 devices or applications together.
37 To compile this driver as a module, choose M here: the module
38 will be called snd-seq-dummy.
44 tristate "OSS Mixer API"
47 To enable OSS mixer API emulation (/dev/mixer*), say Y here
48 and read <file:Documentation/sound/alsa/OSS-Emulation.txt>.
50 Many programs still use the OSS API, so say Y.
52 To compile this driver as a module, choose M here: the module
53 will be called snd-mixer-oss.
56 tristate "OSS PCM (digital audio) API"
60 To enable OSS digital audio (PCM) emulation (/dev/dsp*), say Y
61 here and read <file:Documentation/sound/alsa/OSS-Emulation.txt>.
63 Many programs still use the OSS API, so say Y.
65 To compile this driver as a module, choose M here: the module
66 will be called snd-pcm-oss.
68 config SND_PCM_OSS_PLUGINS
69 bool "OSS PCM (digital audio) API - Include plugin system"
70 depends on SND_PCM_OSS
73 If you disable this option, the ALSA's OSS PCM API will not
74 support conversion of channels, formats and rates. It will
75 behave like most of new OSS/Free drivers in 2.4/2.6 kernels.
77 config SND_SEQUENCER_OSS
78 bool "OSS Sequencer API"
79 depends on SND_SEQUENCER
82 Say Y here to enable OSS sequencer emulation (both
83 /dev/sequencer and /dev/music interfaces).
85 Many programs still use the OSS API, so say Y.
87 If you choose M in "Sequencer support" (SND_SEQUENCER),
88 this will be compiled as a module. The module will be called
92 tristate "RTC Timer support"
96 Say Y here to enable RTC timer support for ALSA. ALSA uses
97 the RTC timer as a precise timing source and maps the RTC
98 timer to ALSA's timer interface. The ALSA sequencer code also
99 can use this timing source.
101 To compile this driver as a module, choose M here: the module
102 will be called snd-rtctimer.
104 config SND_SEQ_RTCTIMER_DEFAULT
105 bool "Use RTC as default sequencer timer"
106 depends on SND_RTCTIMER && SND_SEQUENCER
109 Say Y here to use the RTC timer as the default sequencer
110 timer. This is strongly recommended because it ensures
111 precise MIDI timing even when the system timer runs at less
116 config SND_DYNAMIC_MINORS
117 bool "Dynamic device file minor numbers"
119 If you say Y here, the minor numbers of ALSA device files in
120 /dev/snd/ are allocated dynamically. This allows you to have
121 more than 8 sound cards, but requires a dynamic device file
124 If you are unsure about this, say N here.
126 config SND_SUPPORT_OLD_API
127 bool "Support old ALSA API"
130 Say Y here to support the obsolete ALSA PCM API (ver.0.9.0 rc3
133 config SND_VERBOSE_PROCFS
134 bool "Verbose procfs contents"
138 Say Y here to include code for verbose procfs contents (provides
139 useful information to developers when a problem occurs). On the
140 other side, it makes the ALSA subsystem larger.
142 config SND_VERBOSE_PRINTK
143 bool "Verbose printk"
145 Say Y here to enable verbose log messages. These messages
146 will help to identify source file and position containing
149 You don't need this unless you're debugging ALSA.
154 Say Y here to enable ALSA debug code.
156 config SND_DEBUG_VERBOSE
157 bool "More verbose debug"
160 Say Y here to enable extra-verbose debugging messages.
162 Let me repeat: it enables EXTRA-VERBOSE DEBUGGING messages.
163 So, say Y only if you are ready to be annoyed.
165 config SND_PCM_XRUN_DEBUG
166 bool "Enable PCM ring buffer overrun/underrun debugging"
168 depends on SND_DEBUG && SND_VERBOSE_PROCFS
170 Say Y to enable the PCM ring buffer overrun/underrun debugging.
171 It is usually not required, but if you have trouble with
172 sound clicking when system is loaded, it may help to determine
173 the process or driver which causes the scheduling gaps.