Searched full:api (Results 1 – 25 of 1616) sorted by relevance
12345678910>>...65
| /linux-3.3/drivers/media/radio/ |
| D | Kconfig | 52 that are compatible with the Video For Linux API. Information on
53 this API and pointers to "v4l" programs may be found at
54 <file:Documentation/video4linux/API.html>.
147 that are compatible with the Video For Linux 2 API. Information on
148 this API and pointers to "v4l2" programs may be found at
149 <file:Documentation/video4linux/API.html>.
178 that are compatible with the Video For Linux API. Information on
179 this API and pointers to "v4l" programs may be found at
180 <file:Documentation/video4linux/API.html>.
205 that are compatible with the Video For Linux API. Information on
[all …]
|
| /linux-3.3/Documentation/sound/alsa/ |
| D | compress_offload.txt | 8 Since its early days, the ALSA API was defined with PCM support or
11 extend the existing API to compressed data streams.
18 mostly because of a lack of a generic API available in the mainline
21 Rather than requiring a compability break with an API change of the
22 ALSA PCM interface, a new 'Compressed Data' API is introduced to
25 The design of this API was inspired by the 2-year experience with the
27 API in the mainline kernel instead of the staging tree and make it
49 - Focus on main formats. This API provides support for the most
57 cycles. The new API needs to provide a generic way of listing these
60 - Rendering/Grabbing only. This API does not provide any means of
[all …]
|
| /linux-3.3/Documentation/ |
| D | DMA-API.txt | 6 This document describes the DMA API. For a more gentle introduction
7 of the API (and actual examples) see
8 Documentation/DMA-API-HOWTO.txt.
10 This API is split into two pieces. Part I describes the API. Part II
11 describes the extensions to the API for supporting non-consistent
14 platforms) you should only use the API described in part I.
16 Part I - dma_ API
19 To get the dma_ API, you must #include <linux/dma-mapping.h>
76 To get this part of the dma_ API, you must #include <linux/dmapool.h>
141 internal API for use by the platform than an external API for use by
[all …]
|
| D | dma-buf-sharing.txt | 1 DMA Buffer Sharing API Guide
9 buffer sharing API, how to use it for exporting and using shared buffers.
33 For this first version, A buffer shared using the dma_buf sharing API:
38 The dma_buf buffer sharing API usage contains the following steps:
75 This API installs an fd for the anonymous file associated with this buffer;
86 This API will return a reference to the dma_buf, and increment refcount for
96 This API returns reference to an attachment structure, which is then used
111 access to the buffer using dma_buf_map_attachment API. At least one attach to
144 the exporter using the dma_buf_unmap_attachment API.
157 map_dma_buf, this API also must be implemented by the exporter.
[all …]
|
| D | dmaengine.txt | 1 DMA Engine API Guide
7 Documentation/crypto/async-tx-api.txt
10 Below is a guide to device driver writers on how to use the Slave-DMA API of the
25 To request a channel dma_request_channel() API is used.
83 A non-NULL return of this transfer API represents a "descriptor" for
120 Although the async_tx API specifies that completion callback
156 issue_pending API. If channel is idle then the first transaction in
188 description of this API.
198 using this API.
|
| /linux-3.3/Documentation/DocBook/ |
| D | regulator.tmpl | 5 <book id="regulator-api">
7 <title>Voltage and current regulator API</title>
92 The regulator API uses a number of terms which may not be
151 This offers a similar API to the kernel clock framework.
153 linkend='API-regulator-get'>get</link> and <link
154 linkend='API-regulator-put'>put</link> operations to acquire and
156 provided to <link linkend='API-regulator-enable'>enable</link>
157 and <link linkend='API-regulator-disable'>disable</link> the
167 A stub version of this API is provided when the regulator
175 The regulator API provides reference counted enabling and
[all …]
|
| D | alsa-driver-api.tmpl | 8 <book id="ALSA-Driver-API">
10 <title>The ALSA Driver API</title>
55 <chapter><title>PCM API</title>
68 <chapter><title>Control/Mixer API</title>
72 <sect1><title>AC97 Codec API</title>
76 <sect1><title>Virtual Master Control API</title>
81 <chapter><title>MIDI API</title>
82 <sect1><title>Raw MIDI API</title>
85 <sect1><title>MPU401-UART API</title>
89 <chapter><title>Proc Info API</title>
[all …]
|
| D | gadget.tmpl | 5 <book id="USB-Gadget-API">
7 <title>USB Gadget API for Linux</title>
59 API, for use within peripherals and other USB devices
61 It provides an overview of the API structure,
63 This is the first such API released on Linux to address
82 <listitem><para>Sharing data structures and API models with the
83 Linux-USB host side API. This helps the OTG support, and
94 <para>Most Linux developers will not be able to use this API, since they
108 <para>The gadget API resembles the host side Linux-USB API in that both
116 and assumptions that are inappropriate for a gadget API.
[all …]
|
| /linux-3.3/sound/core/ |
| D | Kconfig | 54 tristate "OSS Mixer API"
57 To enable OSS mixer API emulation (/dev/mixer*), say Y here
60 Many programs still use the OSS API, so say Y.
66 tristate "OSS PCM (digital audio) API"
73 Many programs still use the OSS API, so say Y.
79 bool "OSS PCM (digital audio) API - Include plugin system"
83 If you disable this option, the ALSA's OSS PCM API will not
88 bool "OSS Sequencer API"
95 Many programs still use the OSS API, so say Y.
135 (CONFIG_RTC_CLASS) since this requires the old API.
[all …]
|
| /linux-3.3/drivers/media/ |
| D | Kconfig | 21 bool "Media Controller API (EXPERIMENTAL)"
24 Enable the media controller API used to query media devices internal
27 This API is mostly used by camera interfaces in embedded platforms.
30 # V4L core and enabled API's
39 This kernel includes support for the new Video for Linux Two API,
57 bool "V4L2 sub-device userspace API (EXPERIMENTAL)"
60 Enables the V4L2 sub-device pad-level userspace API used to configure
63 This API is mostly used by camera interfaces in embedded platforms.
80 API specs and user tools are available from <http://www.linuxtv.org/>.
|
| /linux-3.3/Documentation/crypto/ |
| D | api-intro.txt | 2 Scatterlist Cryptographic API
6 The Scatterlist Crypto API takes page vectors (scatterlists) as
19 API.
26 Conceptually, the API layering looks like this:
28 [transform api] (user interface)
30 [algorithm api] (for registering algorithms)
32 The idea is to make the user interface and algorithm registration API
36 The API currently supports five main types of transforms: AEAD (Authenticated
50 Here's an example of how to use the API:
86 When using the API for ciphers, performance will be optimal if each
[all …]
|
| D | async-tx-api.txt | 1 Asynchronous Transfers/Transforms API
8 3.1 General format of the API
26 The async_tx API provides methods for describing a chain of asynchronous
30 that is written to the API can optimize for asynchronous operation and
31 the API will fit the chain of operations to the available offload
36 The API was initially designed to offload the memory copy and
42 1/ implicit synchronous path: users of the API do not need to know if
46 2/ cross channel dependency chains: the API allows a chain of dependent
48 API automatically handles cases where the transition from one operation
55 3.1 General format of the API:
[all …]
|
| /linux-3.3/Documentation/DocBook/media/v4l/ |
| D | planar-apis.xml | 10 <para>Initially, V4L2 API did not support multi-planar buffers and a set of
12 what is being referred to as the "multi-planar API".</para>
14 <para>Some of the V4L2 API calls and structures are interpreted differently,
15 depending on whether single- or multi-planar API is being used. An application
24 <para>Multi-planar API introduces new multi-planar formats. Those formats
26 the multi-planar API and a multi-planar format. Multi-planar API calls can
28 multi-planar API structures), while the single-planar API cannot
|
| D | dev-teletext.xml | 11 <para>The Teletext API was designed by Martin Buck. It was defined in
17 <para>Eventually the Teletext API was integrated into the V4L API
25 them. So the decision was made to finally remove support for the Teletext API in
29 <link linkend="sliced">sliced</link> VBI API.</para>
|
| /linux-3.3/Documentation/video4linux/cx2341x/ |
| D | fw-calling.txt | 1 This page describes how to make calls to the firmware api.
17 reserved for API calls. The second 10 are used by the firmware for event
39 The command is a 32-bit enumerator. The API specifics may be found in the
40 fw-*-api.txt documents.
47 these fields with result values returned by the call. The API specifics may be
48 found in the fw-*-api.txt documents.
54 To make an API call, the driver iterates over each mailbox looking for the
65 firmware which events it is interested in via an API call. That call tells the
|
| /linux-3.3/include/net/ |
| D | wimax.h | 3 * Kernel space API for accessing WiMAX devices
24 * The WiMAX stack provides an API for controlling and managing the
25 * system's WiMAX devices. This API affects the control plane; the
28 * Parts of the WiMAX stack API and notifications are exported to
33 * The API is standarized for all WiMAX devices and different drivers
41 * devices show in the market. This API is designed to be growable in
55 * Remember this is a very low level API that will to provide all of
57 * are the expected clients of it. They offer a higher level API that
74 * WiMAX devices have a state, and a kernel-only API allows the
78 * Most API calls will set the state automatically; in most cases
[all …]
|
| /linux-3.3/arch/arm/mach-omap2/ |
| D | voltage.c | 52 * API to get the current non-auto-compensated voltage for a voltage domain.
66 * voltdm_scale() - API to scale voltage of a particular voltage domain.
70 * This API should be called by the kernel to do the voltage scaling
84 pr_err("%s: No voltage scale API registered for vdd_%s\n", in voltdm_scale()
101 * This API finds out the correct voltage the voltage domain is supposed
125 * omap_voltage_get_volttable() - API to get the voltage table associated with a
129 * populated by this API
131 * This API populates the voltage table associated with a VDD into the
148 * omap_voltage_get_voltdata() - API to get the voltage table entry for a
153 * This API searches through the voltage table for the required voltage
[all …]
|
| /linux-3.3/Documentation/watchdog/ |
| D | 00-INDEX | 4 - how-to for converting old watchdog drivers to the new kernel API.
11 watchdog-api.txt
12 - description of the Linux Watchdog driver API.
13 watchdog-kernel-api.txt
14 - description of the Linux WatchDog Timer Driver Core kernel API.
|
| /linux-3.3/Documentation/fb/ |
| D | api.txt | 1 The Frame Buffer Device API
10 This document describes the frame buffer API used by applications to interact
14 Due to a lack of documentation in the original frame buffer API, drivers
16 the recommended API implementation, but applications should be prepared to
37 The driver supports the four character code (FOURCC) based format setting API.
234 legacy API and the FOURCC-based API.
237 The legacy API has been the only frame buffer format configuration API for a
238 long time and is thus widely used by application. It is the recommended API
280 The FOURCC-based API replaces format descriptions by four character codes
282 without explicitly describing it. This is the only API that supports YUV
[all …]
|
| /linux-3.3/Documentation/netlabel/ |
| D | introduction.txt | 13 layer, and the kernel security module API.
22 the NetLabel kernel security module API described below.
36 * Security Module API
38 The purpose of the NetLabel security module API is to provide a protocol
40 to protocol independence, the security module API is designed to be completely
44 Detailed information about the NetLabel security module API can be found in the
|
| /linux-3.3/Documentation/video4linux/ |
| D | API.html | 5 <title>V4L API</title>
12 … <a href="http://linuxtv.org/downloads/legacy/video4linux/API/V4L1_API.html">V4L original API</a>
15 Obsoleted by V4L2 API
20 <a href="http://v4l2spec.bytesex.org/spec-single/v4l2.html">V4L2 API</a>
|
| /linux-3.3/include/linux/ |
| D | of_gpio.h | 2 * OF helpers for the GPIO API
92 * of_get_gpio_flags() - Get a GPIO number and flags to use with GPIO API
97 * Returns GPIO number to use with Linux generic GPIO API, or one of the errno
108 * of_get_named_gpio() - Get a GPIO number to use with GPIO API
113 * Returns GPIO number to use with Linux generic GPIO API, or one of the errno
123 * of_get_gpio() - Get a GPIO number to use with GPIO API
127 * Returns GPIO number to use with Linux generic GPIO API, or one of the errno
|
| D | v4l2-subdev.h | 2 * V4L2 subdev userspace API
43 * @pad: pad number, as reported by the media API
56 * @pad: pad number, as reported by the media API
68 * @pad: pad number, as reported by the media API
81 * @pad: pad number, as reported by the media API
98 * @pad: pad number, as reported by the media API
109 * @pad: pad number, as reported by the media API
|
| /linux-3.3/arch/sparc/kernel/ |
| D | hvapi.c | 1 /* hvapi.c: Hypervisor API management.
12 /* If the hypervisor indicates that the API setting
14 * HV_ENOTSUPPORTED, we assume that API groups with the
79 /* Register a hypervisor API specification. It indicates the
80 * API group and desired major+minor.
82 * If an existing API registration exists '0' (success) will
87 * API group/major/minor with the hypervisor, and errors returned
195 prom_printf("HVAPI: Cannot register API group " in sun4v_hvapi_init()
|
| /linux-3.3/Documentation/DocBook/media/dvb/ |
| D | kdapi.xml | 1 <title>Kernel Demux API</title>
2 <para>The kernel demux API defines a driver-internal interface for registering low-level,
4 DVB device driver writers. The header file for this API is named <emphasis role="tt">demux.h</empha…
67 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
90 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
97 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
116 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
123 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
185 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
228 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
[all …]
|
12345678910>>...65