blob: 4262a1c8773191f072b48277a5f42eb2b5d19cb7 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# ALSA soundcard-configuration
2config SND_TIMER
3 tristate
4 depends on SND
5
6config SND_PCM
7 tristate
8 select SND_TIMER
9 depends on SND
10
11config SND_HWDEP
12 tristate
13 depends on SND
14
15config SND_RAWMIDI
16 tristate
17 depends on SND
18
19config SND_SEQUENCER
20 tristate "Sequencer support"
21 depends on SND
22 select SND_TIMER
23 help
24 Say Y or M to enable MIDI sequencer and router support. This
25 feature allows routing and enqueueing of MIDI events. Events
26 can be processed at a given time.
27
28 Many programs require this feature, so you should enable it
29 unless you know what you're doing.
30
31config SND_SEQ_DUMMY
32 tristate "Sequencer dummy client"
33 depends on SND_SEQUENCER
34 help
35 Say Y here to enable the dummy sequencer client. This client
36 is a simple MIDI-through client: all normal input events are
37 redirected to the output port immediately.
38
39 You don't need this unless you want to connect many MIDI
40 devices or applications together.
41
42 To compile this driver as a module, choose M here: the module
43 will be called snd-seq-dummy.
44
45config SND_OSSEMUL
46 bool
47 depends on SND
48
49config SND_MIXER_OSS
50 tristate "OSS Mixer API"
51 depends on SND
52 select SND_OSSEMUL
53 help
54 To enable OSS mixer API emulation (/dev/mixer*), say Y here
55 and read <file:Documentation/sound/alsa/OSS-Emulation.txt>.
56
57 Many programs still use the OSS API, so say Y.
58
59 To compile this driver as a module, choose M here: the module
60 will be called snd-mixer-oss.
61
62config SND_PCM_OSS
63 tristate "OSS PCM (digital audio) API"
64 depends on SND
65 select SND_OSSEMUL
66 select SND_PCM
67 help
68 To enable OSS digital audio (PCM) emulation (/dev/dsp*), say Y
69 here and read <file:Documentation/sound/alsa/OSS-Emulation.txt>.
70
71 Many programs still use the OSS API, so say Y.
72
73 To compile this driver as a module, choose M here: the module
74 will be called snd-pcm-oss.
75
Jaroslav Kysela21a34792006-01-13 09:12:11 +010076config SND_PCM_OSS_PLUGINS
77 bool "OSS PCM (digital audio) API - Include plugin system"
78 depends on SND_PCM_OSS
79 default y
80 help
81 If you disable this option, the ALSA's OSS PCM API will not
82 support conversion of channels, formats and rates. It will
83 behave like most of new OSS/Free drivers in 2.4/2.6 kernels.
84
Linus Torvalds1da177e2005-04-16 15:20:36 -070085config SND_SEQUENCER_OSS
86 bool "OSS Sequencer API"
87 depends on SND && SND_SEQUENCER
88 select SND_OSSEMUL
89 help
90 Say Y here to enable OSS sequencer emulation (both
91 /dev/sequencer and /dev/music interfaces).
92
93 Many programs still use the OSS API, so say Y.
94
Frederik Deweerdtc2f60c52006-03-31 13:13:23 +020095 If you choose M in "Sequencer support" (SND_SEQUENCER),
96 this will be compiled as a module. The module will be called
97 snd-seq-oss.
Linus Torvalds1da177e2005-04-16 15:20:36 -070098
99config SND_RTCTIMER
100 tristate "RTC Timer support"
101 depends on SND && RTC
102 select SND_TIMER
103 help
104 Say Y here to enable RTC timer support for ALSA. ALSA uses
105 the RTC timer as a precise timing source and maps the RTC
106 timer to ALSA's timer interface. The ALSA sequencer code also
107 can use this timing source.
108
109 To compile this driver as a module, choose M here: the module
110 will be called snd-rtctimer.
111
Clemens Ladischa4f508b2005-09-06 08:00:19 +0200112config SND_SEQ_RTCTIMER_DEFAULT
113 bool "Use RTC as default sequencer timer"
114 depends on SND_RTCTIMER && SND_SEQUENCER
115 default y
116 help
117 Say Y here to use the RTC timer as the default sequencer
118 timer. This is strongly recommended because it ensures
119 precise MIDI timing even when the system timer runs at less
120 than 1000 Hz.
121
122 If in doubt, say Y.
123
Clemens Ladisch332682b2005-11-20 14:07:47 +0100124config SND_DYNAMIC_MINORS
125 bool "Dynamic device file minor numbers (EXPERIMENTAL)"
126 depends on SND && EXPERIMENTAL
127 help
128 If you say Y here, the minor numbers of ALSA device files in
129 /dev/snd/ are allocated dynamically. This allows you to have
130 more than 8 sound cards, but requires a dynamic device file
131 system like udev.
132
133 If you are unsure about this, say N here.
134
Takashi Iwai59d48582005-12-01 10:51:58 +0100135config SND_SUPPORT_OLD_API
136 bool "Support old ALSA API"
137 depends on SND
138 default y
139 help
140 Say Y here to support the obsolete ALSA PCM API (ver.0.9.0 rc3
141 or older).
142
Jaroslav Kysela21a34792006-01-13 09:12:11 +0100143config SND_VERBOSE_PROCFS
144 bool "Verbose procfs contents"
Takashi Iwaib7d90a32006-04-25 12:56:04 +0200145 depends on SND && PROC_FS
Jaroslav Kysela21a34792006-01-13 09:12:11 +0100146 default y
147 help
148 Say Y here to include code for verbose procfs contents (provides
149 usefull information to developers when a problem occurs). On the
150 other side, it makes the ALSA subsystem larger.
151
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152config SND_VERBOSE_PRINTK
153 bool "Verbose printk"
154 depends on SND
155 help
156 Say Y here to enable verbose log messages. These messages
157 will help to identify source file and position containing
158 printed messages.
159
160 You don't need this unless you're debugging ALSA.
161
162config SND_DEBUG
163 bool "Debug"
164 depends on SND
165 help
166 Say Y here to enable ALSA debug code.
167
Linus Torvalds1da177e2005-04-16 15:20:36 -0700168config SND_DEBUG_DETECT
169 bool "Debug detection"
170 depends on SND_DEBUG
171 help
172 Say Y here to enable extra-verbose log messages printed when
173 detecting devices.
Jaroslav Kysela61fb63c2006-04-24 21:57:16 +0200174
175config SND_PCM_XRUN_DEBUG
176 bool "Enable PCM ring buffer overrun/underrun debugging"
177 default n
Takashi Iwaib7d90a32006-04-25 12:56:04 +0200178 depends on SND_DEBUG && SND_VERBOSE_PROCFS
Jaroslav Kysela61fb63c2006-04-24 21:57:16 +0200179 help
180 Say Y to enable the PCM ring buffer overrun/underrun debugging.
181 It is usually not required, but if you have trouble with
182 sound clicking when system is loaded, it may help to determine
183 the process or driver which causes the scheduling gaps.