| /linux-3.3/drivers/mtd/nand/ |
| D | Kconfig | 150 will be called bf5xx-nand.
226 selected to save power. This will mean there is a small delay
227 when the is NAND chip selected or released, but will save
272 By default, the probe for DiskOnChip devices will look for a
278 (Note that on PowerPC, the normal probe will only check at
288 By default, the probe for DiskOnChip devices will look for a
304 Linux will not write BBT data into this area.
306 are detected by Linux, they will not be recorded in the BBT, which
309 in Linux or other operating systems) will not use the reserved area.
335 capabilities; enabling this option will allow you to use
[all …]
|
| /linux-3.3/Documentation/filesystems/caching/ |
| D | operations.txt | 30 and FS-Cache will create operations and pass them off to the appropriate cache
97 will be given to keventd to process. Such an operation is not permitted
110 will be given to the slow work facility to process. Such an operation is
158 If successful, both functions will assign the operation to the specified
159 object and return 0. -ENOBUFS will be returned if the object specified is
162 The operation manager will defer operations on an object that is still
163 undergoing lookup or creation. The operation will also be deferred if an
166 If the operation is asynchronous, the manager will retain a reference to
199 When used in asynchronous mode, the worker thread pool will invoke the
210 The caller holds a reference on the operation, and will invoke
|
| /linux-3.3/drivers/staging/tidspbridge/ |
| D | Kconfig | 45 In case of DSP fatal error, BRIDGE driver will try to
57 the next 128-Byte boundary will be loaded and written back as well.
59 byte alignment, buffers failing this check will be rejected.
67 will caught the interrupt and try to recover DSP.
75 counter is not reset the wdt overflow interrupt will be triggered
83 error, this will require a bridge restart to recover.
|
| /linux-3.3/arch/ia64/ |
| D | Kconfig | 134 If you say N, all options in this submenu will be skipped and disabled.
167 will run on any supported IA-64 system. However, if you configure
168 a kernel for your specific system, it will be faster and smaller.
212 Selecting this option will optimize the kernel for use on sn2 based
213 systems, but the resulting kernel binary will not run on other
224 Selecting this option will optimize the kernel for use on UV based
225 systems, but the resulting kernel binary will not run on other
364 If you say N here, the kernel will run on single and multiprocessor
365 systems, but will use only one CPU of a multiprocessor system. If
366 you say Y here, the kernel will run on many, but not all,
[all …]
|
| /linux-3.3/security/keys/ |
| D | keyctl.c | 138 * If a key is found, it will be attached to the destination keyring if there's
139 * one specified and the serial number of the key will be returned.
141 * If no key is found, /sbin/request-key will be invoked if _callout_info is
142 * non-NULL in an attempt to create a key. The _callout_info string will be
144 * _callout_info string is "" then it will be changed to "-".
235 * If successful, the ID of the requested keyring will be returned.
261 * permission for it to be joined. Session keyrings without this permit will
264 * If successful, the ID of the joined session keyring will be returned.
296 * If successful, 0 will be returned. If the key type does not support
297 * updating, then -EOPNOTSUPP will be returned.
[all …]
|
| /linux-3.3/Documentation/ |
| D | robust-futex-ABI.txt | 30 to do so, then improperly listed locks will not be cleaned up on exit,
49 compatibility mode, will attempt to process both lists on each task
55 as described below. If the list is empty, the pointer will point
59 address of the associated 'lock entry', plus or minus, of what will
79 robust_futexes. The kernel will only be able to wakeup the next thread
87 the kernel will walk this list, mark any such locks with a bit
100 It is anticipated that threads will use robust_futexes embedded in
152 On exit, the kernel will consider the address stored in
156 exiting threads TID, then the kernel will do two things:
159 wakeup on that address, which will waken the next thread that has
[all …]
|
| /linux-3.3/drivers/watchdog/ |
| D | booke_wdt.c | 28 /* If the kernel parameter wdt=1, the watchdog will be enabled at boot.
30 * For E500 cpus the wdt_period sets which bit changing from 0->1 will
31 * trigger a watchog timeout. This watchdog timeout will occur 3 times, the
32 * first time nothing will happen, the second time a watchdog exception will
33 * occur, and the final time the board will reset.
50 * corresponding to the reset time. There will be a watchdog
57 * at least 1. This will still result in a very long timeout.
74 * This procedure will find the highest period which will give a timeout
76 * and a parameter of 2 secs, then this procedure will return a value of 38.
|
| /linux-3.3/arch/arm/plat-spear/ |
| D | padmux.c | 40 * It will set mode of operation in hardware.
65 * It will enable pads for all required peripherals once and only once.
67 * Conflicts between peripherals are not handled and peripherals will be
69 * In case of conflicts last peripheral enabled will be present.
117 /* this will ensure that multiplexing can't be changed now */ in pmx_devs_enable()
127 * Also this must be called only once. This will allocate memory for pmx
128 * structure, will call pmx_mode_set, will call pmx_devs_enable.
|
| /linux-3.3/drivers/net/ethernet/smsc/ |
| D | Kconfig | 16 kernel: saying N will just cause the configurator to skip all
17 the questions about SMC/Western Digital cards. If you say Y, you will
35 will be called smc9194.
53 The module will be called smc91x. If you want to compile it as a
66 To compile this driver as a module, choose M here: the module will be
94 This driver is also available as a module. The module will be
110 will be called smsc911x.
132 This driver is also available as a module. The module will be
|
| /linux-3.3/Documentation/scheduler/ |
| D | sched-bwc.txt | 14 hierarchy will be throttled and are not allowed to run again until the next
39 Writing any (valid) positive value(s) will enact the specified bandwidth limit.
45 Writing any negative value to cpu.cfs_quota_us will remove the bandwidth limit
48 Any updates to a group's bandwidth specification will result in it becoming
61 Larger slice values will reduce transfer overheads, while smaller values allow
90 In case b) above, even though the child may have runtime remaining it will not
97 If period is 250ms and quota is also 250ms, the group will get
115 With 50ms period, 10ms quota will be equivalent to 20% of 1 CPU.
|
| /linux-3.3/drivers/usb/class/ |
| D | Kconfig | 16 /proc/bus/usb/devices, then your modem will not work with this
20 module will be called cdc-acm.
30 module will be called usblp.
41 module will be called cdc-wdm.
52 module will be called usbtmc.
|
| /linux-3.3/include/linux/ |
| D | zlib.h | 6 warranty. In no event will the authors be held liable for any damages
56 (deflation) but other algorithms will be added later and will have the same
112 The opaque value provided by the application will be passed as the first
122 exactly 65536 bytes, but will not be required to allocate more than this
140 #define Z_PARTIAL_FLUSH 1 /* will be removed, use Z_SYNC_FLUSH instead */
213 perform any compression: this will be done by deflate().
230 processing will resume at this point for the next call of deflate().
324 accordingly; otherwise the allocation will be deferred to the first call of
332 the zlib header if present: this will be done by inflate(). (So next_in and
350 will resume at this point for the next call of inflate().
[all …]
|
| /linux-3.3/scripts/dtc/libfdt/ |
| D | libfdt.h | 15 * This library is distributed in the hope that it will be useful,
247 * On success, *address and *size will contain the address and size of
281 * address, in which case fdt_subnode_offset() will find the subnode
283 * which case fdt_subnode_offset() will find an arbitrary subnode
326 * @lenp: pointer to an integer variable (will be overwritten) or NULL
350 * @lenp: pointer to an integer variable (will be overwritten) or NULL
387 * @lenp: pointer to an integer variable (will be overwritten) or NULL
390 * named 'name' of the node at offset nodeoffset (this will be a
435 * @buf: character buffer to contain the returned path (will be overwritten)
450 * characters and will not fit in the given buffer.
[all …]
|
| /linux-3.3/Documentation/cgroups/ |
| D | blkio-controller.txt | 61 blkio.disk_sectors files of both test1 and test2 groups. This will tell how
82 Above will put a limit of 1MB/second on reads happening for root group
101 So this patch will allow creation of cgroup hierarhcy but at the backend
102 everything will be treated as flat. So if somebody created a hierarchy like
111 CFQ and throttling will practically treat all groups at same level.
118 and also introduce a new cgroup file "use_hierarchy" which will control
254 will only report the group_wait_time accumulated till the last time it
255 got a timeslice and will not include the current delta.
263 the stat will only report the empty_time accumulated till the last
264 time it had a pending request and will not include the current delta.
[all …]
|
| D | cpusets.txt | 57 CPUs or Memory Nodes not in that cpuset. The scheduler will not
59 vector, and the kernel page allocator will not allocate a page on a
261 computing jobs that will dramatically fail to meet required performance
273 systems that enable this feature will compute the metric.
311 the kernel will spread the file system buffers (page cache) evenly
316 then the kernel will spread some file system related slab caches,
335 mempolicies will not notice any change in these calls as a result of
355 PF_SPREAD_SLAB, and appropriately marked slab caches will allocate
378 CPU will look for tasks on other more overloaded CPUs and move those
414 scheduler will avoid load balancing across the CPUs in that cpuset,
[all …]
|
| /linux-3.3/sound/usb/ |
| D | Kconfig | 22 will be called snd-usb-audio.
33 will be called snd-ua101.
46 will be called snd-usb-usx2y.
73 will be called snd-usb-caiaq.
101 will be called snd-usb-us122l.
112 You will need firmware files in order to be able to use the device
|
| /linux-3.3/drivers/xen/xenbus/ |
| D | xenbus_client.c | 95 * success, or -errno on error. On success, the given @path will be saved as
96 * @watch->node, and remains the caller's to free. On error, @watch->node will
97 * be NULL, the device will switch to %XenbusStateClosing, and the error will
133 * (@path/@path2) will be saved as @watch->node, and becomes the caller's to
134 * kfree(). On error, watch->node will be NULL, so the caller has nothing to
135 * free, the device will switch to %XenbusStateClosing, and the error will be
175 to it, as the device will be tearing down, and we don't want to in __xenbus_switch_state()
179 function will not take a caller's Xenstore transaction in __xenbus_switch_state()
229 * Return 0 on success, or -errno on error. On error, the device will switch
230 * to XenbusStateClosing, and the error will be saved in the store.
[all …]
|
| /linux-3.3/arch/tile/include/hv/ |
| D | hypervisor.h | 8 * This program is distributed in the hope that it will be useful, but
102 * These numbers are part of the binary API and will not be changed
509 * @param tile Tile which will receive the IPI.
622 * Once this service completes, page_table will be used to translate
742 * [start, start + size) will be flushed from the TLB.
867 * If an out-of-range idx value is specified, the returned size will be zero.
869 * returned size is zero. There will always be at least one valid range.
968 * If an out-of-range idx value is specified, the returned size will be zero.
970 * returned size is zero. There will always be at least one valid range.
1004 * If an out-of-range idx value is specified, the returned size will be zero.
[all …]
|
| /linux-3.3/Documentation/power/ |
| D | runtime_pm.txt | 61 callback, the PM core will invoke the corresponding driver callback stored in
66 and bus type. Moreover, the high-priority one will always take precedence over
90 device will not process data and will not communicate with the CPU(s) and
100 -EAGAIN, the PM core regards this as a fatal error and will refuse to run
111 that remote wakeup will be enabled for the device. Generally, remote wakeup
128 fatal error and will refuse to run the helper functions described in Section
158 ->runtime_idle() (although ->runtime_idle() will not be started while any
162 devices (i.e. the PM core will only execute ->runtime_idle() or
172 PM core will only execute ->runtime_resume() for the devices the runtime
179 to execute it, ->runtime_idle() will not be executed for the same device.
[all …]
|
| D | pm_qos_interface.txt | 38 Will insert an element into the list for that identified PM QoS class with the
45 Will update the list element pointed to by the handle with the new target value
50 Will remove the element. After removal it will update the aggregate target and
103 Will insert an element into the list for that identified device with the
110 Will update the list element pointed to by the handle with the new target value
115 Will remove the element. After removal it will update the aggregate target and
|
| /linux-3.3/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 57 and will end up initialising all compiled machines' pm init!
86 1) The uart drivers will disable the clocks to the UART blocks when
88 access to the UARTs will cause the debug to stop.
90 2) Whilst the pm code itself will attempt to re-enable the UART clocks,
129 will mean that the CRC data block will take more memory, but will
|
| /linux-3.3/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 7 Note that the driver's will not load on the "wrong" hardware,
12 is not available in all processors. The drivers will refuse
18 Frequency transitions will be unavailable if the BIOS does
33 The powernow-k8 driver will attempt to use ACPI if so configured,
35 The powernow-k7 driver will try to use the PSB support first, and
|
| /linux-3.3/Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 8 physical address of the page. The kernel will then attempt
10 dropping it if possible. The kernel will then be placed
18 kernel will never kill anything for this, but rather
31 kernel will then attempt to hard-offline the page, by
34 any processes owning the page. The kernel will avoid
|
| /linux-3.3/include/linux/decompress/ |
| D | generic.h | 16 *posp - if non-null, input position (number of bytes read) will be
21 *If len = 0, inbuf can be NULL, in which case the decompressor will allocate
23 *fill will be called (repeatedly...) to read data, at most XXX_IOBUF_SIZE
28 *output. If flush != NULL, the output buffer will be allocated by the
29 *decompressor (outbuf = NULL), and the flush function will be called to
|
| /linux-3.3/arch/sh/mm/ |
| D | Kconfig | 15 turning this off will boot the kernel on these machines with the
55 The physical memory (RAM) start address will be automatically
61 value on any of the known systems will only lead to disaster.
90 If you say Y here, physical addressing will be extended to
92 29-bit physical addressing will be used.
103 This will enable support for the kernel mapping a vDSO page
264 Selecting this option will configure the caches in write-through
267 Since there's sill some aliasing issues on SH-4, this option will
|