4 bool "Enable sound support"
6 Support making sounds through an audio codec. This is normally a
7 beep at a chosen frequency for a selected length of time. However
8 the drivers support playing arbitrary sound samples using a
11 Note: At present the sound setup is somewhat tangled up in that the
12 audio codecs are called from the sound-i2s code. This could be
13 converted to driver model.
16 bool "Enable I2S support"
19 I2S is a serial bus often used to transmit audio data from the
20 SoC to the audio codec. This option enables sound support using
21 I2S. It calls either of the two supported codecs (no use is made
22 of driver model at present).
25 bool "Enable I2S support for Rockchip SoCs"
28 Rockchip SoCs support an I2S interface for sending audio data to an
29 audio codec. This option enables support for this, using one of the
30 available audio codec drivers. This driver does not make use of
31 DMA, but writes each word directly to the hardware.
34 bool "Enable I2C support for Samsung SoCs"
37 Samsung Exynos SoCs support an I2S interface for sending audio
38 data to an audio codec. This option enables support for this,
39 using one of the available audio codec drivers. Enabling this
40 option provides an implementation for sound_init() and
44 bool "Intel i8254 timer / beeper"
47 This enables support for a beeper that uses the i8254 timer chip.
48 This can emit beeps at a fixed frequency. It is possible to control
49 the length of the beeps, by turning a beep on, waiting for a period
50 of time, then turning it off.
52 This is quite an old feature, called PIT (Programmable Interval
53 Timer), but is nonetheless still available on modern x86 machines.
55 config SOUND_INTEL_HDA
56 bool "Intel HDA audio codec"
59 Most Intel chips have an HDA (High-definition audio) codec which can
60 be used by U-Boot to play simple beeps. This is also sometimes called
61 Azalia which was the development code-name. It requires setup
62 information in the device tree (see intel-hda.txt).
64 config SOUND_IVYBRIDGE
65 bool "Intel Ivybridge sound support"
67 select SOUND_INTEL_HDA
69 Enable sound output on supported Intel Ivybridge-based boards. This
70 driver uses Intel's High-definition Audio (HDA) architecture,
71 sometimes called Azalia. The audio codec is detected using a
72 semi-automatic mechanism.
75 bool "Enable I2S support for Nvidia Tegra SoCs"
79 Nvidia Tegra SoCs support several I2S interfaces for sending audio
80 data to an audio codec. This option enables support for this,
81 using one of the available audio codec drivers.
84 bool "Support Maxim max98088 audio codec"
87 Enable the max98088 audio codec. This is connected via I2S for
88 audio data and I2C for codec control. At present it only works
89 with the Samsung I2S driver.
92 bool "Support Maxim max98090 audio codec"
95 Enable the max98090 audio codec. This is connected via I2S for
96 audio data and I2C for codec control. At present it only works
97 with the Samsung I2S driver.
100 bool "Support Maxim max98095 audio codec"
103 Enable the max98095 audio codec. This is connected via I2S for
104 audio data and I2C for codec control. At present it only works
105 with the Samsung I2S driver.
108 bool "Support Realtek RT5677 audio codec"
111 Enable the Realtek RT5677 audio codec. This is an I2S device used on
112 some Chromebooks from around 2015 ('auron'). It is configured using
113 an I2C interface and supports multiple sound inputs and outputs,
114 including digital microphones.
117 bool "Support sandbox emulated audio codec"
118 depends on SANDBOX && SOUND
120 U-Boot sandbox can emulate a sound device using SDL, playing the
121 sound on the host machine. This option implements the sound_init()
122 and sound_play() functions for sandbox. Note that you must install
123 the SDL libraries for this to work.
126 bool "Support Wolfson Micro wm8994 audio codec"
127 depends on I2S_SAMSUNG
129 Enable the wm8994 audio codec. This is connected via I2S for
130 audio data and I2C for codec control. At present it only works
131 with the Samsung I2S driver.