Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hdaudio(4) [netbsd man page]

HDAUDIO(4)						   BSD Kernel Interfaces Manual 						HDAUDIO(4)

NAME
hdaudio -- High Definition Audio device driver SYNOPSIS
hdaudio* at pci? dev ? function ? hdafg* at hdaudiobus? audio* at audiobus? options HDAUDIO_DEBUG options HDAUDIO_AFG_DEBUG DESCRIPTION
The hdaudio device driver is expected to support any PCI device which is compliant to the High Definition Audio Specification 1.0. It is a replacement for azalia(4). It was written from scratch following the Intel HD Audio and Microsoft Universal Audio Architecture specifica- tions. The driver consists of two interlinked components, which reflects the hardware design. The hdaudio component interfaces with a PCI/PCIe bus and provides an hdaudiobus(4) onto which different function groups attach. Each function group (e.g. audio, vendor-specific modem) is exported as a separate child device of the hdaudio controller. Audio function groups (a.k.a. audio codec) are exported as hdafg(4) devices. Audio codecs are available from a number of manufacturers and are made up of a number of widgets (e.g. audio mixer, output pin, analog-to- digital converter). The way the widgets are interlinked varies significantly between implementations. The tree of widgets must be parsed and mapped to mixer(4) controls. As part of this process, loops in the inter-codec links must be detected and muted, bi-directional pins must be set up appropriately and the locations of pins determined. Unlike the azalia(4) driver (which tends to generate a large number of unclearly named mixer(4) controls), hdaudio works backwards by starting with a list of desired, consistent and compatible mixer(4) controls and configuring/discovering appropriate widget link routes to fit. By following the published mechanisms for common implementations of widget parsing, it is expected that nearly all High Definition Audio devices will be supported without requiring per-device quirks. SEE ALSO
audio(4), mixer(4), pci(4), hdaudioctl(8), http://www.intel.com/standards/hdaudio/ http://www.microsoft.com/whdc/device/audio/ HISTORY
The hdaudio device driver appeared in NetBSD 5.1. AUTHORS
The hdaudio driver was written by Jared McNeill <jmcneill@NetBSD.org> under contract by Precedence Technologies Ltd <http://www.precedence.co.uk/>. The UAA-compliant widget parser is derived from the FreeBSD snd_hda(4) driver. BUGS
The following items are not yet implemented: o Improve power management support when driver is idle o Add support for non-PCM output formats o Handle unsolicited RIRB messages o Modem function groups BSD
September 28, 2010 BSD

Check Out this Related Man Page

oss_usb(7)							    OSS Devices 							oss_usb(7)

NAME
oss_usb - USB Audio/MIDI/Mixer driver DESCRIPTION
The Open Sound System driver for USB Audio and MIDI devices. AUDIO The Audio driver supports: o 8-96Khz Playback/Recording o 8 or 16 or 32 bits o 2, 4, 6 or 8 channel audio. o SPDIF digital output and Input o AC3 passthrough o Volume control and device input mixer MIDI The oss_usb driver supports all MIDI devices that are compatible with the official USB MIDI specification. In addition the driver supports few devices that use their own private protocol (including some Yamaha and Midiman models). USB MIXER The USB Audio mixer is a new type of mixer that doesn't have the normal volume controls found on AC97 or Legacy SB devices. The USB audio mixer provides control for selecting the Alternate device setting - this usually allows the device to be switched into a Professional audio mode (eg 24bit or 96Khz mode) ALTERNATIVE SETTINGS Some USB audio devices use a feature called as alternative settings for bandwidth management. Typically such devices have multiple high speed inputs and outputs that may require more bandwidth than provided by the USB bus. The alternative settings feature is used to select between multiple low speed devices or just few high speed devices. When the device has multiple alternative settings an "altsetting" selector will be visible in the control panel for the device (use oss- mix(1) or ossxmix(1) to change it). Alternative setting OFF means that all audio devices are disabled. The other settings provide different combinations of high/medium speed devices. You can use the ossinfo(1) command (ossinfo -a -v3) to find out the devices supported by the currently selected alternative settings and the capabilities of them. KNOWN BUGS
Under Linux it is necessary to run the ossdetect -d and ossdevlinks commands after an USB device has been hot-plugged. Alternatively you can execute soundoff and soundon to reload OSS. OPTIONS
None FILES
/etc/oss4/conf/oss_usb.conf Device configuration file AUTHOR
4Front Technologies 16 December 2012 oss_usb(7)
Man Page