Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hdaudio(4) [netbsd man page]

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

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), HISTORY
The hdaudio device driver appeared in NetBSD 5.1. AUTHORS
The hdaudio driver was written by Jared McNeill <> under contract by Precedence Technologies Ltd <>. 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

BTSCO(4)						   BSD Kernel Interfaces Manual 						  BTSCO(4)

btsco -- Bluetooth SCO Audio SYNOPSIS
btsco* at bthub? audio* at audiobus? DESCRIPTION
The btsco driver provides support for Bluetooth SCO Audio devices through the audio(4) driver. The btsco driver must be configured at run time with the btdevctl(8) program. The following properties are used by the btsco driver during autoconfiguration: local-bdaddr Local device address. remote-bdaddr Remote device address. service-name The btsco driver matches the 'HF' and 'HSET' services. For the 'HF' service, the btsco device will, on open(2), listen for incom- ing connections from the remote device. Otherwise, btsco will attempt to initiate a connection to the remote device. rfcomm-channel This integer value is not used directly, but will be stored and passed via the BTSCO_INFO ioctl as below: SCO connections require a baseband connection between the two devices before they can be created. The btsco driver does not create this, but can provide information to facilitate an application setting up a control channel prior to use, via the BTSCO_INFO ioctl(2) call on the mixer device, which returns a btsco_info structure as follows: #include <dev/bluetooth/btsco.h> struct btsco_info { bdaddr_t laddr; /* controller bdaddr */ bdaddr_t raddr; /* headset bdaddr */ uint8_t channel; /* RFCOMM channel */ int vgs; /* mixer index speaker */ int vgm; /* mixer index mic */ }; #define BTSCO_INFO _IOR('b', 16, struct btsco_info) The btsco driver can be configured to act in Connect or Listen mode. In Connect mode, the btsco driver will initiate a connection to the remote device on an open(2) call, whereas in Listen mode, open(2) will block until the remote device initiates the connection. SEE ALSO
bthset(1), ioctl(2), audio(4), bluetooth(4), bthub(4), btdevctl(8) HISTORY
The btsco driver was written for NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc. BUGS
btsco takes no notice of the HCI Voice Setting in the Bluetooth controller, and this must be 0x0060 (the default) as alternate values are currently unsupported. BSD
October 4, 2006 BSD
Man Page

Featured Tech Videos