| /linux-3.3/lib/ |
| D | Kconfig | 33 tristate "CRC-CCITT functions"
36 modules require CRC-CCITT functions, but a module built outside
38 functions require M here.
41 tristate "CRC16 functions"
44 modules require CRC16 functions, but a module built outside
46 functions require M here.
56 tristate "CRC ITU-T V.41 functions"
59 modules require CRC ITU-T V.41 functions, but a module built outside
61 functions require M here.
64 tristate "CRC32 functions"
[all …]
|
| /linux-3.3/Documentation/ |
| D | sgi-ioc4.txt | 4 First, even though the IOC4 performs multiple functions, such as an
8 standpoint is that all these functions share a single IRQ, and
12 functions, meaning that there's no clear "owning" device driver.
23 the PCI resources that are shared between the IOC4 functions.
25 This driver also provides registration functions that the other
39 remove functions.
45 probe, and remove functions.
|
| D | kernel-doc-nano-HOWTO.txt | 8 but consistent and extractable documentation of the functions and
10 a consistent style for documenting functions and their parameters,
22 In order to provide good documentation of kernel functions and data
26 We definitely need kernel-doc formatted documentation for functions
30 functions externally visible to other kernel files (not marked
112 form of block comments above functions. The components of this system
132 and external functions.
133 It invokes kernel-doc, giving it the list of functions that
268 Beside functions you can also write documentation for structs, unions,
303 instead of being kernel-doc for functions, structures, unions,
[all …]
|
| D | unshare.txt | 93 changes to copy_* functions utilized by clone/fork system call.
183 versions. Helper functions of clone (copy_*) could not be used
201 Therefore code from copy_* functions that allocated and duplicated
202 current context structure was moved into new dup_* functions. Now,
203 copy_* functions call dup_* functions to allocate and duplicate
221 a) Reorganization of existing copy_* functions
223 c) unshare helper functions for each different process context
226 7.1) Reorganization of copy_* functions
232 These dup_* functions allocated and duplicated the appropriate
233 context structure. The reorganized copy_* functions invoked
[all …]
|
| D | SM501.txt | 8 asynchronous serial ports, audio functions, and a dual display video interface.
9 The device may be connected by PCI or local bus with varying functions enabled.
40 as this is by-far the most resource-sensitive of the on-chip functions.
51 functions, which are transient and thus their location is less critical
|
| D | padata.txt | 39 There are functions for enabling and disabling the instance:
44 These functions are setting or clearing the "PADATA_INIT" flag;
45 if that flag is not set, other functions will refuse to work.
51 The list of CPUs to be used can be adjusted with these functions:
69 To simply add or remove one CPU from a certain cpumask the functions
109 parallel() and serial() functions should be provided. Those functions will
|
| /linux-3.3/tools/perf/Documentation/ |
| D | perf-script-perl.txt | 91 to every event as arguments but are available as library functions.
126 The rest of the script can contain handler functions and support
127 functions in any order.
129 Aside from the event handler functions discussed above, every script
130 can implement a set of optional functions:
164 built-in perf script Perl modules and their associated functions.
169 The following sections describe the functions and variables available
170 via the various Perf::Trace::* Perl modules. To use the functions and
177 These functions provide some essential functions to user scripts.
179 The *flag_str* and *symbol_str* functions provide human-readable
[all …]
|
| D | perf-script-python.txt | 28 provides more details on each step and lists the library functions
125 # be retrieved using Python functions of the form common_*(context).
126 # See the perf-script-python Documentation for the list of available functions.
165 Following that are a couple generated functions, trace_begin() and
170 Following those are the 'event handler' functions generated one for
171 every event in the 'perf record' output. The handler functions take
177 The final couple of functions are, like the begin and end functions,
211 trace_unhandled() functions, which we won't be using. That leaves us
489 to every event as arguments but are available as library functions.
527 The rest of the script can contain handler functions and support
[all …]
|
| /linux-3.3/Documentation/arm/OMAP/ |
| D | omap_pm | 6 authors use these functions to communicate minimum latency or
32 five power management functions for driver code:
50 Further documentation for all OMAP PM interface functions can be
63 Driver usage of the OMAP PM functions
66 As the 'pdata' in the above examples indicates, these functions are
69 files to point to the corresponding OMAP PM functions:
72 not support these functions should leave these function pointers set
78 The most common usage of these functions will probably be to specify
107 Other specialized interface functions
110 The five functions listed above are intended to be usable by any
[all …]
|
| /linux-3.3/Documentation/power/ |
| D | opp.txt | 28 OPP library provides a set of helper functions to organize and query the OPP
58 operational functions operate only on available opps:
63 be used for opp_enable/disable functions to make an opp available as required.
66 get_opp_count if opp_enable/disable functions are invoked for a device, the
74 OPP library uses RCU for exclusivity. RCU allows the query functions to operate
85 mutex to implment RCU updater strategy. These functions should *NOT* be called
86 under RCU locks and other contexts that prevent blocking functions in RCU or
96 OPPs dynamically using the opp_enable / disable functions.
101 with the opp_enable/disable functions. OPP library internally stores
125 frequency back to the corresponding OPP, OPP library provides handy functions
[all …]
|
| /linux-3.3/tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 4 This module contains utility functions for use with perf script.
8 'used', while Util.pm contains useful but optional utility functions
14 want to add new Perl functions that end up accessing C data in the
15 perf executable, you add desciptions of the new functions here.
18 $context, to all handler functions.
|
| /linux-3.3/Documentation/blackfin/ |
| D | bfin-gpio-notes.txt | 23 multi-functions. They can be configured as peripheral, or just as GPIO,
45 The request functions will record the function state for a certain pin,
46 the free functions will clear its function state.
50 These functions are wrapped by other functions, most of the users need not
|
| /linux-3.3/Documentation/networking/ |
| D | vxge.txt | 22 The functions share a 10GbE link and the pci-e bus, but hardly anything else
34 ii) Multi function mode (up to 17 functions)
37 - Single Root mode: v1.0 (up to 17 functions)
38 - Multi-Root mode: v1.0 (up to 17 functions)
71 Specifies maximum device functions to be enabled.
|
| /linux-3.3/drivers/staging/vme/ |
| D | vme_api.txt | 111 required. These functions should be passed the pointer to the resource provided
132 Once a master window has been assigned the following functions can be used to
147 These functions return 0 on success or an error code should the call fail.
153 The following functions can be used to read from and write to configured master
154 windows. These functions return the number of bytes copied:
170 This functions by reading the offset, applying the mask. If the bits selected in
187 Once a slave window has been assigned the following functions can be used to
202 These functions return 0 on success or an error code should the call fail.
209 buffers which will be accessible by the VME bridge. These functions do not have
239 The following functions are provided to create and destroy DMA lists. Execution
[all …]
|
| /linux-3.3/kernel/ |
| D | Kconfig.locks | 91 # lock_* functions are inlined when:
94 # trylock_* functions are inlined when:
97 # unlock and unlock_irq functions are inlined when:
102 # unlock_bh and unlock_irqrestore functions are inlined when:
|
| /linux-3.3/kernel/gcov/ |
| D | gcc_3_4.c | 115 ((char *) info->functions + fn * get_fn_size(info)); in get_fn_info()
145 dup->functions = kmemdup(info->functions, info->n_functions * in gcov_info_dup()
147 if (!dup->functions) in gcov_info_dup()
179 kfree(info->functions); in gcov_info_free()
|
| /linux-3.3/arch/c6x/lib/ |
| D | divi.S | 20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
|
| D | remu.S | 20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
41 ;; The ABI seems designed to prevent these functions calling each other,
|
| D | remi.S | 20 ;; ABI considerations for the divide functions
27 ;; In our implementation, divu and remu are leaf functions,
29 ;; A0 is not clobbered by any of the functions.
|
| /linux-3.3/Documentation/trace/ |
| D | tracepoints.txt | 8 connect probe functions to them and provides some examples of probe
9 functions.
92 put in inline functions, inlined static functions, and unrolled loops
93 as well as regular functions.
|
| /linux-3.3/Documentation/hwmon/ |
| D | lm87 | 64 The LM87 has four pins which can serve one of two possible functions,
67 Some functions share pins, so not all functions are available at the same
73 For reference, here is the list of exclusive functions:
|
| /linux-3.3/Documentation/arm/Samsung-S3C24XX/ |
| D | GPIO.txt | 22 of the GPIO functions such as reading and writing a pin will
25 Once all the extant drivers have been converted, the functions
29 The following functions now either have a s3c_ specific variant
92 The GPIO management functions are defined in the hardware
97 header on how the GPIO functions (and others) work.
99 Whilst a number of these functions do make some checks on what
109 the GPIO functions which pin is to be used.
|
| /linux-3.3/drivers/staging/speakup/ |
| D | TODO | 19 Some places are currently using in_atomic() because speakup functions
24 There is a duplication of the selection functions in selections.c. These
25 functions should get exported from drivers/char/selection.c (clear_selection
|
| /linux-3.3/fs/befs/ |
| D | ChangeLog | 22 * Segregated the functions that interface directly with the linux vfs
76 * Made functions in endian.h to do the correct byteswapping, no matter
84 Uses the functions from endian.h [WD]
94 * Cleanup of NLS functions (util.c) [WD]
113 * Added new debug/warning/error print functions in debug.c.
166 * Converted all non vfs-callback functions to use befs_sb_info as the
178 * Added functions to get the private superblock and inode structures from
200 * Removed prototypes for functions who's definitions have been removed
267 * Added B+tree reading functions (in btree.c).
300 * Created io.c, for io related functions.
[all …]
|
| /linux-3.3/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 92 with receive and transmit functions.
95 CAIF payload with receive and transmit functions.
99 to the called function (except for framing layers' receive functions
105 The CAIF protocol can be divided into two parts: Support functions and Protocol
106 Implementation. The support functions include:
109 CAIF Packet has functions for creating, destroying and adding content
|