| /linux-4.4.14/arch/xtensa/mm/ |
| D | init.c | 53 struct meminfo *it = NULL; in find_bank() local
57 it = sysmem.bank + i; in find_bank()
60 return it; in find_bank()
91 struct meminfo *it = NULL; in add_sysmem_bank() local
106 it = find_bank(start); in add_sysmem_bank()
108 if (it) in add_sysmem_bank()
109 bank_sz = it->end - it->start; in add_sysmem_bank()
111 if (it && bank_sz >= start - it->start) { in add_sysmem_bank()
112 if (end - it->start > bank_sz) in add_sysmem_bank()
113 it->end = end; in add_sysmem_bank()
[all …]
|
| /linux-4.4.14/drivers/staging/lustre/lustre/mdc/ |
| D | mdc_locks.c | 57 int it_disposition(struct lookup_intent *it, int flag) in it_disposition() argument
59 return it->d.lustre.it_disposition & flag; in it_disposition()
63 void it_set_disposition(struct lookup_intent *it, int flag) in it_set_disposition() argument
65 it->d.lustre.it_disposition |= flag; in it_set_disposition()
69 void it_clear_disposition(struct lookup_intent *it, int flag) in it_clear_disposition() argument
71 it->d.lustre.it_disposition &= ~flag; in it_clear_disposition()
75 int it_open_error(int phase, struct lookup_intent *it) in it_open_error() argument
77 if (it_disposition(it, DISP_OPEN_LEASE)) { in it_open_error()
79 return it->d.lustre.it_status; in it_open_error()
83 if (it_disposition(it, DISP_OPEN_OPEN)) { in it_open_error()
[all …]
|
| /linux-4.4.14/drivers/staging/lustre/lustre/lmv/ |
| D | lmv_intent.c | 55 int lmmsize, struct lookup_intent *it, in lmv_intent_remote() argument
81 if (it->it_op & IT_LOOKUP) in lmv_intent_remote()
82 it->it_op = IT_GETATTR; in lmv_intent_remote()
87 pmode = it->d.lustre.it_lock_mode; in lmv_intent_remote()
89 plock.cookie = it->d.lustre.it_lock_handle; in lmv_intent_remote()
90 it->d.lustre.it_lock_mode = 0; in lmv_intent_remote()
91 it->d.lustre.it_data = NULL; in lmv_intent_remote()
114 LASSERT(it->it_op & IT_OPEN); in lmv_intent_remote()
125 rc = md_intent_lock(tgt->ltd_exp, op_data, lmm, lmmsize, it, in lmv_intent_remote()
135 if (it->d.lustre.it_lock_mode != 0) { in lmv_intent_remote()
[all …]
|
| D | lmv_internal.h | 48 #define LL_IT2STR(it) \ argument
49 ((it) ? ldlm_it2str((it)->it_op) : "0")
54 void *lmm, int lmmsize, struct lookup_intent *it,
60 void *lmm, int lmmsize, struct lookup_intent *it,
66 void *lmm, int lmmsize, struct lookup_intent *it,
|
| /linux-4.4.14/drivers/staging/lustre/lustre/llite/ |
| D | dcache.c | 209 void ll_intent_drop_lock(struct lookup_intent *it) in ll_intent_drop_lock() argument
211 if (it->it_op && it->d.lustre.it_lock_mode) { in ll_intent_drop_lock()
214 handle.cookie = it->d.lustre.it_lock_handle; in ll_intent_drop_lock()
217 handle.cookie, it); in ll_intent_drop_lock()
218 ldlm_lock_decref(&handle, it->d.lustre.it_lock_mode); in ll_intent_drop_lock()
222 it->d.lustre.it_lock_mode = 0; in ll_intent_drop_lock()
223 if (it->d.lustre.it_remote_lock_mode != 0) { in ll_intent_drop_lock()
224 handle.cookie = it->d.lustre.it_remote_lock_handle; in ll_intent_drop_lock()
227 handle.cookie, it); in ll_intent_drop_lock()
229 it->d.lustre.it_remote_lock_mode); in ll_intent_drop_lock()
[all …]
|
| D | namei.c | 406 struct lookup_intent *it, in ll_lookup_it_finish() argument
415 CDEBUG(D_DENTRY, "it %p it_disposition %x\n", it, in ll_lookup_it_finish()
416 it->d.lustre.it_disposition); in ll_lookup_it_finish()
417 if (!it_disposition(it, DISP_LOOKUP_NEG)) { in ll_lookup_it_finish()
418 rc = ll_prep_inode(&inode, request, (*de)->d_sb, it); in ll_lookup_it_finish()
422 ll_set_lock_data(ll_i2sbi(parent)->ll_md_exp, inode, it, &bits); in ll_lookup_it_finish()
446 } else if (!it_disposition(it, DISP_LOOKUP_NEG) && in ll_lookup_it_finish()
447 !it_disposition(it, DISP_OPEN_CREATE)) { in ll_lookup_it_finish()
454 if (!it_disposition(it, DISP_LOOKUP_NEG)) { in ll_lookup_it_finish()
458 } else if (!it_disposition(it, DISP_OPEN_CREATE)) { in ll_lookup_it_finish()
[all …]
|
| D | file.c | 471 static int ll_och_fill(struct obd_export *md_exp, struct lookup_intent *it, in ll_och_fill() argument
474 struct ptlrpc_request *req = it->d.lustre.it_data; in ll_och_fill()
480 och->och_lease_handle.cookie = it->d.lustre.it_lock_handle; in ll_och_fill()
482 och->och_flags = it->it_flags; in ll_och_fill()
484 return md_set_open_replay_data(md_exp, och, it); in ll_och_fill()
487 static int ll_local_open(struct file *file, struct lookup_intent *it, in ll_local_open() argument
498 struct ptlrpc_request *req = it->d.lustre.it_data; in ll_local_open()
502 rc = ll_och_fill(ll_i2sbi(inode)->ll_md_exp, it, och); in ll_local_open()
512 fd->fd_omode = it->it_flags & (FMODE_READ | FMODE_WRITE | FMODE_EXEC); in ll_local_open()
532 struct lookup_intent *it, oit = { .it_op = IT_OPEN, in ll_file_open() local
[all …]
|
| /linux-4.4.14/drivers/staging/lustre/lustre/include/ |
| D | lustre_mdc.h | 82 struct lookup_intent *it) in mdc_get_rpc_lock() argument
84 if (it != NULL && (it->it_op == IT_GETATTR || it->it_op == IT_LOOKUP || in mdc_get_rpc_lock()
85 it->it_op == IT_LAYOUT)) in mdc_get_rpc_lock()
116 lck->rpcl_it = it; in mdc_get_rpc_lock()
120 struct lookup_intent *it) in mdc_put_rpc_lock() argument
122 if (it != NULL && (it->it_op == IT_GETATTR || it->it_op == IT_LOOKUP || in mdc_put_rpc_lock()
123 it->it_op == IT_LAYOUT)) in mdc_put_rpc_lock()
136 LASSERTF(it == lck->rpcl_it, "%p != %p\n", it, lck->rpcl_it); in mdc_put_rpc_lock()
172 int it_disposition(struct lookup_intent *it, int flag);
173 void it_clear_disposition(struct lookup_intent *it, int flag);
[all …]
|
| /linux-4.4.14/kernel/time/ |
| D | posix-cpu-timers.c | 88 if (timer->it.cpu.incr == 0) in bump_cpu_timer()
91 if (now < timer->it.cpu.expires) in bump_cpu_timer()
94 incr = timer->it.cpu.incr; in bump_cpu_timer()
95 delta = now + incr - timer->it.cpu.expires; in bump_cpu_timer()
105 timer->it.cpu.expires += incr; in bump_cpu_timer()
351 INIT_LIST_HEAD(&new_timer->it.cpu.entry); in posix_cpu_timer_create()
371 new_timer->it.cpu.task = p; in posix_cpu_timer_create()
393 struct task_struct *p = timer->it.cpu.task; in posix_cpu_timer_del()
407 WARN_ON_ONCE(!list_empty(&timer->it.cpu.entry)); in posix_cpu_timer_del()
409 if (timer->it.cpu.firing) in posix_cpu_timer_del()
[all …]
|
| D | itimer.c | 49 struct cpu_itimer *it = &tsk->signal->it[clock_id]; in get_cpu_itimer() local
53 cval = it->expires; in get_cpu_itimer()
54 cinterval = it->incr; in get_cpu_itimer()
150 struct cpu_itimer *it = &tsk->signal->it[clock_id]; in set_cpu_itimer() local
162 cval = it->expires; in set_cpu_itimer()
163 cinterval = it->incr; in set_cpu_itimer()
169 it->expires = nval; in set_cpu_itimer()
170 it->incr = ninterval; in set_cpu_itimer()
171 it->error = error; in set_cpu_itimer()
172 it->incr_error = incr_error; in set_cpu_itimer()
|
| D | posix-timers.c | 360 struct hrtimer *timer = &timr->it.real.timer; in schedule_next_timer()
362 if (timr->it.real.interval.tv64 == 0) in schedule_next_timer()
367 timr->it.real.interval); in schedule_next_timer()
449 timr = container_of(timer, struct k_itimer, it.real.timer); in posix_timer_fn()
452 if (timr->it.real.interval.tv64 != 0) in posix_timer_fn()
461 if (timr->it.real.interval.tv64 != 0) { in posix_timer_fn()
490 if (timr->it.real.interval.tv64 < kj.tv64) in posix_timer_fn()
496 timr->it.real.interval); in posix_timer_fn()
563 struct k_itimer *tmr = container_of(head, struct k_itimer, it.rcu); in k_itimer_rcu_free()
580 call_rcu(&tmr->it.rcu, k_itimer_rcu_free); in release_posix_timer()
[all …]
|
| /linux-4.4.14/drivers/gpu/drm/radeon/ |
| D | radeon_mn.c | 57 struct interval_tree_node it; member
79 it.rb) { in radeon_mn_destroy()
81 interval_tree_remove(&node->it, &rmn->objects); in radeon_mn_destroy()
127 struct interval_tree_node *it; in radeon_mn_invalidate_range_start() local
134 it = interval_tree_iter_first(&rmn->objects, start, end); in radeon_mn_invalidate_range_start()
135 while (it) { in radeon_mn_invalidate_range_start()
140 node = container_of(it, struct radeon_mn_node, it); in radeon_mn_invalidate_range_start()
141 it = interval_tree_iter_next(it, start, end); in radeon_mn_invalidate_range_start()
244 struct interval_tree_node *it; in radeon_mn_register() local
254 while ((it = interval_tree_iter_first(&rmn->objects, addr, end))) { in radeon_mn_register()
[all …]
|
| D | radeon_vm.c | 331 bo_va->it.start = 0; in radeon_vm_bo_add()
332 bo_va->it.last = 0; in radeon_vm_bo_add()
480 struct interval_tree_node *it; in radeon_vm_bo_set_addr() local
481 it = interval_tree_iter_first(&vm->va, soffset, eoffset); in radeon_vm_bo_set_addr()
482 if (it && it != &bo_va->it) { in radeon_vm_bo_set_addr()
484 tmp = container_of(it, struct radeon_bo_va, it); in radeon_vm_bo_set_addr()
488 soffset, tmp->bo, tmp->it.start, tmp->it.last); in radeon_vm_bo_set_addr()
495 if (bo_va->it.start || bo_va->it.last) { in radeon_vm_bo_set_addr()
504 tmp->it.start = bo_va->it.start; in radeon_vm_bo_set_addr()
505 tmp->it.last = bo_va->it.last; in radeon_vm_bo_set_addr()
[all …]
|
| /linux-4.4.14/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_mn.c | 57 struct interval_tree_node it; member
79 it.rb) { in amdgpu_mn_destroy()
81 interval_tree_remove(&node->it, &rmn->objects); in amdgpu_mn_destroy()
127 struct interval_tree_node *it; in amdgpu_mn_invalidate_range_start() local
134 it = interval_tree_iter_first(&rmn->objects, start, end); in amdgpu_mn_invalidate_range_start()
135 while (it) { in amdgpu_mn_invalidate_range_start()
140 node = container_of(it, struct amdgpu_mn_node, it); in amdgpu_mn_invalidate_range_start()
141 it = interval_tree_iter_next(it, start, end); in amdgpu_mn_invalidate_range_start()
245 struct interval_tree_node *it; in amdgpu_mn_register() local
255 while ((it = interval_tree_iter_first(&rmn->objects, addr, end))) { in amdgpu_mn_register()
[all …]
|
| D | amdgpu_vm.c | 726 nptes = mapping->it.last - mapping->it.start + 1; in amdgpu_vm_bo_update_mapping()
772 r = amdgpu_vm_update_ptes(adev, vm, ib, mapping->it.start, in amdgpu_vm_bo_update_mapping()
773 mapping->it.last + 1, addr + mapping->offset, in amdgpu_vm_bo_update_mapping()
1002 struct interval_tree_node *it; in amdgpu_vm_bo_map() local
1028 it = interval_tree_iter_first(&vm->va, saddr, eaddr); in amdgpu_vm_bo_map()
1030 if (it) { in amdgpu_vm_bo_map()
1032 tmp = container_of(it, struct amdgpu_bo_va_mapping, it); in amdgpu_vm_bo_map()
1036 tmp->it.start, tmp->it.last + 1); in amdgpu_vm_bo_map()
1048 mapping->it.start = saddr; in amdgpu_vm_bo_map()
1049 mapping->it.last = eaddr; in amdgpu_vm_bo_map()
[all …]
|
| /linux-4.4.14/drivers/char/ |
| D | mmtimer.c | 262 int nodeid = n->timer->it.mmtimer.node; in mmtimer_add_list()
263 unsigned long expires = n->timer->it.mmtimer.expires; in mmtimer_add_list()
275 if (expires < x->timer->it.mmtimer.expires) in mmtimer_add_list()
289 struct mmtimer, list)->timer->it.mmtimer.expires) in mmtimer_add_list()
311 if (!t->it.mmtimer.incr) { in mmtimer_set_next_timer()
314 t->it.mmtimer.expires, in mmtimer_set_next_timer()
324 expires = exp = t->it.mmtimer.expires; in mmtimer_set_next_timer()
333 to = ((u64)(expires - exp) / t->it.mmtimer.incr); in mmtimer_set_next_timer()
336 t->it.mmtimer.expires += t->it.mmtimer.incr * to; in mmtimer_set_next_timer()
337 exp = t->it.mmtimer.expires; in mmtimer_set_next_timer()
[all …]
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | Kconfig | 7 This is the Speakup screen reader. Think of it as a
9 kernel, it can speak everything on the text console from
48 synthesizer. You can say y to build it into the kernel,
49 or m to build it as a module. See the configuration
57 synthesizer. You can say y to build it into the kernel,
58 or m to build it as a module. See the configuration
65 synthesizer. You can say y to build it into the kernel,
66 or m to build it as a module. See the configuration
73 You can say y to build it into the kernel, or m to
74 build it as a module. See the configuration help on the
[all …]
|
| /linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 23 If you choose to build it as a module, it will be called rtl8192ce
34 If you choose to build it as a module, it will be called rtl8192se
45 If you choose to build it as a module, it will be called rtl8192de
58 If you choose to build it as a module, it will be called rtl8723ae
71 If you choose to build it as a module, it will be called rtl8723be
82 If you choose to build it as a module, it will be called rtl8188ee
94 If you choose to build it as a module, it will be called rtl8192ee
106 If you choose to build it as a module, it will be called rtl8821ae
118 If you choose to build it as a module, it will be called rtl8192cu
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | hpfs.txt | 9 is taken from it
16 Set owner/group/mode for files that do not have it specified in extended
25 - there is a list of text extensions (I thing it's better to not convert
27 change it in the source. Original readonly HPFS contained some strange
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
36 used for debugging (for example it checks if file is allocated in
37 bitmaps when accessing it).
41 When to mark filesystem dirty so that OS/2 checks it.
63 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | porting | 51 informative error value to report). Call it foo_fill_super(). Now declare
80 it by internal locking (most of filesystems couldn't care less) - you
88 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
98 individual fs sb_op functions. If you don't need it, remove it.
104 free to drop it...
116 an existing filesystem, set it according to ->fs_flags:
120 FS_LITTER is gone - just remove it from fs_flags.
126 went in - and hadn't been documented ;-/). Just remove it from fs_flags
144 Briefly it allows for the definition of decode_fh and encode_fh operations
175 When the inode has been created by iget5_locked(), it will be returned with the
[all …]
|
| D | xfs-self-describing-metadata.txt | 10 adequate for supporting PB scale filesystems with billions of inodes, however it
20 For example, it is entirely possible to manually use xfs_db and a bit of
22 determine the root cause of a corruption problem, but it is still mainly a
40 magic number in the metadata block, we have no other way of identifying what it
41 is supposed to be. We can't even identify if it is the right place. Put simply,
42 you can't look at a single metadata block in isolation and say "yes, it is
50 went wrong, but it is impossible to tell what order the blocks were linked into
70 numbers in the metadata objects. That is, if it has the current magic number,
71 the metadata isn't self identifying. If it contains a new magic number, it is
76 integrity checking. We cannot trust the metadata if we cannot verify that it has
[all …]
|
| D | sysfs-pci.txt | 5 that support it. For example, a given bus might look like this:
70 echoed into it, it will then return '5'. Echoing a '0' into it will decrease
71 the count. Even when it returns to 0, though, some of the initialisation
74 The 'rom' file is special in that it provides read-only access to the device's
76 should write the string "1" to the file to enable it before attempting a read
77 call, and disable it following the access by writing "0" to the file. Note
79 In the event a driver is not bound to the device, it can be enabled using the
85 PCI devices, the sysfs directory for it is removed, and the device will be
86 removed from any drivers attached to it. Removal of PCI root buses is
119 wishing to support legacy functionality should define it and provide
|
| D | romfs.txt | 17 with romfs, it needed 3079 blocks.
33 maybe even affs filesystem until you really know that you need it.
37 module. The kernel can be small enough, since it doesn't have other
43 purpose, just because it won't fit into ext2.
77 inspector. After that, in the 3rd longword, it contains the number of
83 the source. This algorithm was chosen because although it's not quite
84 reliable, it does not require any tables, and it is very simple.
111 and world executable if it is; except the character and block devices,
129 Note also that it is your responsibility to not create hard link
152 romfs has also a mailing list, and to date, it hasn't received any
[all …]
|
| D | ubifs.txt | 5 Block Images". UBIFS is a flash file system, which means it is designed
12 To make it more clear, here is a small comparison of MTD devices and
22 3 The whole eraseblock has to be erased before it becomes possible to
43 In a sense, UBIFS is a next generation of JFFS2 file-system, but it is
49 * JFFS2 does not have on-media index and has to build it while mounting,
52 so it mounts many times faster than JFFS2.
57 it possible to fit quite a lot of data to the flash.
64 UBIFS scales logarithmically (most of the data structures it uses are
71 The authors of UBIFS believe, that it is possible to develop UBI2 which
73 but it would be binary incompatible to UBI. So UBIFS would not need to be
[all …]
|
| D | directory-locking | 20 it. If source is a non-directory, lock it. If that means we need to
38 * If target exists, lock it. If source is a non-directory, lock
39 it. In case that means we need to lock both source and target,
59 the parent of object and it would have to lock the parent).
75 not contended, since any process blocked on it is not holding any locks.
83 Thus link creation can't be a part of deadlock - it can't be
84 blocked on source and it means that it doesn't hold any locks.
87 has a child that is also contended. Indeed, suppose that it is held by
110 source), such loop would have to contain these objects and the rest of it
118 While this locking scheme works for arbitrary DAGs, it relies on
[all …]
|
| D | automount-support.txt | 54 (it's only referenced by its parent vfsmount), then it will be deleted
58 some sort of timed event to drive it.
64 If a mountpoint is moved, it gets removed from the expiration list. If a bind
77 As an alternative, it is possible for userspace to request expiry of any
87 error will be given and it won't be unmounted.
89 Otherwise if it was already marked and it wasn't referenced, unmounting will
|
| D | ocfs2.txt | 6 also make it attractive for non-clustered use.
42 barrier=1 This enables/disables barriers. barrier=0 disables it,
43 barrier=1 enables it.
65 it is in use by another node, the first empty one found
73 will hurt performance, but it's good for data-safety.
74 Setting it to 0 will have the same effect as leaving
75 it at the default (5 seconds).
76 Setting it to very large values will improve
79 large, the fs will silently revert it to the default.
|
| /linux-4.4.14/drivers/net/wireless/mwifiex/ |
| D | Kconfig | 8 If you choose to build it as a module, it will be called
20 If you choose to build it as a module, it will be called
32 If you choose to build it as a module, it will be called
43 If you choose to build it as a module, it will be called
|
| /linux-4.4.14/drivers/staging/comedi/ |
| D | range.c | 60 struct comedi_rangeinfo it; in do_rangeinfo_ioctl() local
65 if (copy_from_user(&it, arg, sizeof(struct comedi_rangeinfo))) in do_rangeinfo_ioctl()
67 subd = (it.range_type >> 24) & 0xf; in do_rangeinfo_ioctl()
68 chan = (it.range_type >> 16) & 0xff; in do_rangeinfo_ioctl()
85 if (RANGE_LENGTH(it.range_type) != lr->length) { in do_rangeinfo_ioctl()
88 RANGE_LENGTH(it.range_type), in do_rangeinfo_ioctl()
89 lr->length, it.range_type); in do_rangeinfo_ioctl()
93 if (copy_to_user(it.range_ptr, lr->range, in do_rangeinfo_ioctl()
|
| /linux-4.4.14/drivers/net/wireless/ath/ath6kl/ |
| D | Kconfig | 9 If you choose to build it as a module, it will be called
20 choose to build it as a module, it will be called ath6kl_sdio.
30 Atheros AR6004 chipset and chipsets based on it running over
31 USB. If you choose to build it as a module, it will be
42 If unsure, say Y to make it easier to debug problems.
54 If unsure, say Y to make it easier to debug problems.
61 Enabling this makes it possible to change the regdomain in
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-c2port | 3 Contact: Rodolfo Giometti <giometti@linux.it>
11 Contact: Rodolfo Giometti <giometti@linux.it>
19 Contact: Rodolfo Giometti <giometti@linux.it>
27 Contact: Rodolfo Giometti <giometti@linux.it>
34 Contact: Rodolfo Giometti <giometti@linux.it>
42 Contact: Rodolfo Giometti <giometti@linux.it>
49 Contact: Rodolfo Giometti <giometti@linux.it>
56 Contact: Rodolfo Giometti <giometti@linux.it>
63 Contact: Rodolfo Giometti <giometti@linux.it>
71 Contact: Rodolfo Giometti <giometti@linux.it>
[all …]
|
| D | sysfs-platform-ts5500 | 6 Indicates the presence of an A/D Converter. If it is present,
7 it will display "1", otherwise "0".
14 Indicates the presence of an external reset. If it is present,
15 it will display "1", otherwise "0".
45 Indicates the presence of the RS485 option. If it is present,
46 it will display "1", otherwise "0".
53 Indicates the presence of the SRAM option. If it is present,
54 it will display "1", otherwise "0".
|
| D | sysfs-bus-rpmsg | 21 starts listening on one end of a channel, it assigns it with
27 of this channel. If it contains 0xffffffff, then an address
39 starts listening on one end of a channel, it assigns it with
45 of this channel. If it contains 0xffffffff, then an address
48 remote processor. This make it a local rpmsg server,
49 and it is listening for inbound messages that may be sent
50 from any remote rpmsg client; it is not bound to a single
65 or remote, starts listening on it for messages (and is thus
69 to the other processor, in order to let it know about the
|
| D | sysfs-pps | 3 Contact: Rodolfo Giometti <giometti@linux.it>
11 Contact: Rodolfo Giometti <giometti@linux.it>
19 Contact: Rodolfo Giometti <giometti@linux.it>
31 Contact: Rodolfo Giometti <giometti@linux.it>
43 Contact: Rodolfo Giometti <giometti@linux.it>
53 Contact: Rodolfo Giometti <giometti@linux.it>
60 Contact: Rodolfo Giometti <giometti@linux.it>
67 Contact: Rodolfo Giometti <giometti@linux.it>
|
| D | sysfs-devices-power | 17 it to do that as desired.
29 "disabled" to it.
52 the device is suspended causes it to be woken up.
68 + "disabled\n" to forbid it;
71 "enabled", or "disabled" to it.
74 of a device unless it is certain that all of the PM dependencies
77 device drivers and in that cases it should be safe to leave the
192 drivers do not want their device to suspend as soon as it
201 Not all drivers support this attribute. If it isn't supported,
202 attempts to read or write it will yield I/O errors.
[all …]
|
| D | sysfs-power | 59 seconds, unfreeze tasks and enable nonboot CPUs. If it is in
89 will not exceed this number. However, if it turns out to be
106 it contains '0' which may be changed to '1' by writing a
107 string representing a nonzero integer into it.
110 the machine, then reboot it and run
115 positives), it is possible that the last PM event point
120 CAUTION: Using it will cause your machine's real-time (CMOS)
129 across reboots when pm_trace has been used. More precisely it
136 kernel log (see /sys/power/pm_trace), is that it includes
139 Due to the small hash size necessary to fit in the RTC, it is
[all …]
|
| D | sysfs-devices-platform-docg3 | 8 which can cover any part of it, block aligned, called DPS.
9 The protection has information embedded whether it blocks reads,
23 which can cover any part of it, block aligned, called DPS.
24 The protection has information embedded whether it blocks reads,
|
| D | sysfs-memory-page-offline | 9 to soft-offline it, by moving the contents elsewhere or
10 dropping it if possible. The kernel will then be placed
14 Normally it's the base page size of the kernel, but
35 to access this page assuming it's poisoned by the
39 Normally it's the base page size of the kernel, but
|
| D | sysfs-driver-hid-picolcd | 4 Description: Make it possible to switch the PicoLCD device between LCD
31 Description: Make it possible to adjust defio refresh rate.
40 it only makes sense to adjust this value if only one or two
41 tiles get changed and it's not appropriate to expect the application
42 to flush it's tiny changes explicitely at higher than default rate.
|
| /linux-4.4.14/Documentation/ |
| D | ManagementStyle | 11 to do with reality. It started as a lark, but that doesn't mean that it
14 Btw, when talking about "kernel manager", it's all about the technical
21 People", and NOT read it. Burn it, it's a great symbolic gesture.
24 making it painfully obvious to the questioner that we don't have a clue
34 manager must be to make it. That's very deep and obvious, but it's not
71 a kernel manager have huge fiscal responsibility _anyway_, it's usually
78 you made a year ago wasn't a big decision after all, since it could be
83 - admitting you were an idiot is harder than it looks. We all like to
89 deleting it, you may have irrevocably lost the trust of that
98 your mind, and make people very _aware_ of that. And it's much easier
[all …]
|
| D | BUG-HUNTING | 13 -- Finding it the old way
23 Finding bugs is not always easy. Have a go though. If you can't find it don't
32 Often this is caused by udev. Check that first before blaming it on the
46 Steps to do it:
51 Finding it the old way
57 It's a brute force approach but it works pretty well.
61 . A reproducible bug - it has to happen predictably (sorry)
71 that, like 1.3.50. Build & test; if it works, pick the mid point
73 . You'll narrow it down to the kernel that introduced the bug. You
74 can probably do better than this but it gets tricky.
[all …]
|
| D | DMA-attributes.txt | 15 interconnect, it applies to the system as a whole, and so its
31 Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
41 Since it is optional for platforms to implement DMA_ATTR_WRITE_COMBINE,
49 consistent or non-consistent memory as it sees fit. By using this API,
63 can treat it as a cookie that must be passed to dma_mmap_attrs() and
67 Since it is optional for platforms to implement
82 (usually it means that the cache has been flushed or invalidated
87 large, so it is highly recommended to avoid it if possible.
89 the CPU cache for the given buffer assuming that it has been already
92 device domain after releasing a mapping for it. Use this attribute with
[all …]
|
| D | sgi-ioc4.txt | 2 it are in order.
6 and an external interrupt mechanism, it's not implemented as a
36 simply for historical reasons (it used to be the only IOC4 driver
37 component). There's not much to say about it other than it hooks
43 This is the serial driver for IOC4. There's not much to say about it
44 other than it hooks up to the ioc4 driver via the appropriate registration,
|
| D | bcache.txt | 1 Say you've got a big slow raid 6, and an X-25E or three. Wouldn't it be
9 It's designed around the performance characteristics of SSDs - it only allocates
10 in erase block sized buckets, and it uses a hybrid btree/log to track cached
12 designed to avoid random writes at all costs; it fills up an erase block
13 sequentially, then issues a discard before reusing it.
17 great lengths to protect your data - it reliably handles unclean shutdown. (It
26 to caching large sequential IO. Bcache detects sequential IO and skips it;
27 it also keeps a rolling average of the IO sizes per task, and as long as the
28 average is above the cutoff it will skip all IO from that task - instead of
32 In the event of a data IO error on the flash it will try to recover by reading
[all …]
|
| D | kref.txt | 20 You must initialize the kref after you allocate it. To do this, call
36 it can be passed to another thread of execution, you must
37 increment the refcount with kref_get() before passing it off:
47 holding a valid pointer, it is safe to do this without
51 without already holding a valid pointer, it must serialize access
55 For example, if you allocate some data and then pass it to another
98 This way, it doesn't matter what order the two threads handle the
100 any more and releasing it. The kref_get() does not require a lock,
121 bad style. Don't do it.
124 For instance, if you are done with an object and enqueuing it for
[all …]
|
| D | parport.txt | 42 If you use modprobe , you will find it useful to add lines as below to a
62 port is detected, the devices that are connected to it are analysed,
83 it auto-detects.
137 the port (it might not appear against any). The
165 advantage of COMPAT and ECP modes if it has an IRQ
177 peripherals. This is a port-wide setting, i.e. it
182 and driver can ignore it if it must.
185 port is registered, it picks up the default spintime.
186 When a new device is registered, it picks up the
194 is loaded it will create one lp device for each port found. You can
[all …]
|
| D | remoteproc.txt | 7 of operating system, whether it's Linux or any other flavor of real-time OS.
25 remoteproc will add those devices. This makes it possible to reuse the
32 - Boot a remote processor (i.e. load its firmware, power it on, ...).
51 rproc_shutdown() returns, and users can still use it with a subsequent
58 decrement it back once rproc isn't needed anymore.
73 * something went wrong. handle it and leave.
78 * our remote processor is now powered on... give it some work
81 /* let's shut it down now */
91 it yet. Required parameters are the underlying device, the
103 Note: _never_ directly deallocate @rproc, even if it was not registered
[all …]
|
| D | oops-tracing.txt | 3 the Oops" or "running it through ksymoops". If you post an Oops from 2.6 that
4 has been run through ksymoops, people will just tell you to repost it.
9 Find the Oops and send it to the maintainer of the kernel area that seems to be
11 If you are unsure send it to the person responsible for the code relevant to
12 what you were doing. If it occurs repeatably try and describe how to recreate
13 it. That's worth even more than the oops.
15 If you are totally stumped as to whom to send the report, send it to
23 handed to syslogd which writes it to a syslog file, typically
26 buffers and save it. Or you can cat /proc/kmsg > file, however you
31 (1) Hand copy the text from the screen and type it in after the machine
[all …]
|
| D | dma-buf-sharing.txt | 9 buffer sharing API, how to use it for exporting and using shared buffers.
29 in memory, mapped into its own address space, so it can access the same area
37 1. Exporter announces that it wishes to export a buffer
39 passes it around to potential buffer-users based on use case
43 6. when buffer-user is done using this buffer completely, it 'disconnects'
49 The buffer exporter announces its wish to export a buffer. In this, it
61 buffer, so it can be exported. On failure to allocate the dma_buf object,
62 it returns NULL.
70 zeroes it out and pre-populates exp_name in it.
88 it.
[all …]
|
| D | sysrq.txt | 7 regardless of whatever else it is doing, unless it is completely locked up.
88 'j' - Forcibly "Just thaw it" - filesystems frozen by the FIFREEZE ioctl.
107 'r' - Turns off keyboard raw mode and sets it to XLATE.
131 it so that only emergency messages like PANICs or OOPSes would
132 make it to your console.)
143 IMPORTANT: In its true form it is not a true SAK like the one in a :IMPORTANT
144 IMPORTANT: c2 compliant system, and it should not be mistaken as :IMPORTANT
146 It seems others find it useful as (System Attention Key) which is
156 sync(s) is great when your system is locked up, it allows you to sync your
173 are unable to kill any other way, especially if it's spawning other
[all …]
|
| D | volatile-considered-harmful.txt | 6 sometimes tempted to use it in kernel code when shared data structures are
37 compiler might think it knows what will be in shared_data, but the
38 spin_lock() call, since it acts as a memory barrier, will force it to
39 forget anything it knows. There will be no optimization problems with
45 can be working with it. While the lock is held, shared_data is not
66 hyperthreaded twin processor; it also happens to serve as a compiler
82 - The jiffies variable is special in that it can have a different value
83 every time it is referenced, but it can be read without any special
86 to be a "stupid legacy" issue (Linus's words) in this regard; fixing it
87 would be more trouble than it is worth.
|
| D | applying-patches.txt | 24 To correctly apply a patch you need to know what base it was generated from
33 (or patch) file and makes the changes to the source tree described in it.
39 kernel source directories it was generated against (or some other directory
45 in the patch file when applying it (the -p1 argument to `patch' does this).
51 You can revert (undo) it like this:
72 uncompress it before applying it, then you can feed it to patch like this
77 If you wish to uncompress the patch file by hand first before applying it
95 When patch applies a patch file it attempts to verify the sanity of the
101 If patch encounters something that doesn't look quite right it has two
102 options. It can either refuse to apply the changes and abort or it can try
[all …]
|
| D | IPMI.txt | 23 subject and I can't cover it all here!
29 things to have it work right depending on your hardware. Most of
37 Kernel code (like the watchdog) can still use it. If you need access
42 properly provides the SMBIOS info for IPMI, the driver will detect it
47 support this, but it is unknown if it will work on every board. For
49 figuring to see if it will work on your system if the SMBIOS/APCI
67 watchdog timer start as soon as it initializes. It also have a lot
69 Note that you can also have the watchdog continue to run if it is
70 closed (by default it is disabled on close). Go into the 'Watchdog
91 only need to take the pieces you need and you can use it in many
[all …]
|
| D | percpu-rw-semaphore.txt | 12 Locking for reading is very fast, it uses RCU and it avoids any atomic
14 writing is very expensive, it calls synchronize_rcu() that can take
18 The lock is initialized percpu_init_rwsem, it returns 0 on success and
|
| D | robust-futexes.txt | 13 someone else wants to grab it too) then the lock is marked with a value
15 syscall is used to wait for the other guy to release it. The kernel
16 creates a 'futex queue' internally, so that it can later on match up the
18 When the owner thread releases the futex, it notices (via the variable
22 state, and there's no in-kernel state associated with it. The kernel
38 There is a big conceptual problem with futex based mutexes though: it is
44 the one that crashes, so it has no opportunity to clean up. Catch-22.
58 - it has quite complex locking and race scenarios. The vma-based
77 normal kernels can turn it off, but worse than that: the overhead makes
97 walks the list [not trusting it], and marks all locks that are owned by
[all …]
|
| D | email-clients.txt | 10 If you are new to git then send your first patch to yourself. Save it
21 it makes quoting portions of the patch more difficult in the patch
44 xcutsel may work, but it's best to test this for yourself or just avoid
52 and successfully apply it with 'patch' before sending patches to Linux
112 enable it.
118 it as a draft. Once you pull it up again from your drafts it is now hard
143 make it more viewable.
147 "save as". You can use the whole email unmodified as a patch if it was
149 are actually viewing it in its own window -- there has been a request filed
157 Run away from it.
[all …]
|
| D | CodingStyle | 7 able to maintain, and I'd prefer it for most other things too. Please
11 and NOT read it. Burn them, it's a great symbolic gesture.
25 at your screen for 20 straight hours, you'll find it a lot easier to see
29 the code move too far to the right, and makes it hard to read on a
130 the cases where it is followed by a continuation of the same statement,
255 "count_active_users()" or similar, you should _not_ call it "cntusr()".
259 check those, and it only confuses the programmer. No wonder MicroSoft
263 some random integer loop counter, it should probably be called "i".
264 Calling it "loop_counter" is non-productive, if there is no chance of it
280 in the source, what does it mean?
[all …]
|
| D | HOWTO | 23 explain some of the reasons why the community works like it does.
35 The kernel is written using GNU C and the GNU toolchain. While it
36 adheres to the ISO C89 standard, it uses a number of extensions that are
42 and the extensions that it uses, and unfortunately there is no
75 new features are added to the kernel, it is recommended that new
78 userspace to change, it is recommended that you send the information or
97 rationale behind it. All new code is expected to follow the
100 review code if it is in the proper style.
108 - Who to send it to
111 will almost always prevent it.
[all …]
|
| D | bus-virt-phys-mapping.txt | 22 0 is what the CPU sees when it drives zeroes on the memory bus.
51 So when the CPU wants any bus master to write to physical memory 0, it
117 you can't use it from the bus master.
120 address in some cases, it's just not very often in normal code. The physical
124 management layer doesn't know about devices outside the CPU, so it
132 of a video graphics card it can be normal DRAM that is just used for a frame
136 whatever, and there is only one way to access it: the readb/writeb and
138 there is really nothing you can do with such an address: it's not
140 just dereference a pointer. (Sadly, on x86 it _is_ in the same memory space,
141 so on x86 it actually works to just deference a pointer, but it's not
[all …]
|
| /linux-4.4.14/drivers/staging/comedi/drivers/ |
| D | rti800.c | 262 static int rti800_attach(struct comedi_device *dev, struct comedi_devconfig *it) in rti800_attach() argument
269 ret = comedi_request_region(dev, it->options[0], 0x10); in rti800_attach()
281 devpriv->adc_2comp = (it->options[4] == 0); in rti800_attach()
282 devpriv->dac_2comp[0] = (it->options[6] == 0); in rti800_attach()
283 devpriv->dac_2comp[1] = (it->options[8] == 0); in rti800_attach()
295 s->n_chan = (it->options[2] ? 16 : 8); in rti800_attach()
298 s->range_table = (it->options[3] < ARRAY_SIZE(rti800_ai_ranges)) in rti800_attach()
299 ? rti800_ai_ranges[it->options[3]] in rti800_attach()
311 (it->options[5] < ARRAY_SIZE(rti800_ao_ranges)) in rti800_attach()
312 ? rti800_ao_ranges[it->options[5]] in rti800_attach()
[all …]
|
| D | ni_labpc.c | 85 static int labpc_attach(struct comedi_device *dev, struct comedi_devconfig *it) in labpc_attach() argument
87 unsigned int irq = it->options[1]; in labpc_attach()
88 unsigned int dma_chan = it->options[2]; in labpc_attach()
91 ret = comedi_request_region(dev, it->options[0], 0x20); in labpc_attach()
|
| D | dt2815.c | 146 static int dt2815_attach(struct comedi_device *dev, struct comedi_devconfig *it) in dt2815_attach() argument
154 ret = comedi_request_region(dev, it->options[0], 0x2); in dt2815_attach()
176 current_range_type = (it->options[3]) in dt2815_attach()
178 voltage_range_type = (it->options[2]) in dt2815_attach()
181 devpriv->range_type_list[i] = (it->options[5 + i]) in dt2815_attach()
196 program = (it->options[4] & 0x3) << 3 | 0x7; in dt2815_attach()
|
| D | pcl818.c | 910 struct comedi_devconfig *it) in pcl818_set_ai_range_table() argument
919 if (it->options[4] == 1 || it->options[4] == 10) { in pcl818_set_ai_range_table()
924 switch (it->options[4]) { in pcl818_set_ai_range_table()
980 static int pcl818_attach(struct comedi_device *dev, struct comedi_devconfig *it) in pcl818_attach() argument
992 ret = comedi_request_region(dev, it->options[0], in pcl818_attach()
998 if (it->options[1] >= 2 && it->options[1] <= 7) { in pcl818_attach()
999 ret = request_irq(it->options[1], pcl818_interrupt, 0, in pcl818_attach()
1002 dev->irq = it->options[1]; in pcl818_attach()
1006 if (dev->irq && board->has_fifo && it->options[2] == -1) in pcl818_attach()
1011 pcl818_alloc_dma(dev, it->options[2]); in pcl818_attach()
[all …]
|
| D | amplc_pc236.c | 49 static int pc236_attach(struct comedi_device *dev, struct comedi_devconfig *it) in pc236_attach() argument
58 ret = comedi_request_region(dev, it->options[0], 0x4); in pc236_attach()
62 return amplc_pc236_common_attach(dev, dev->iobase, it->options[1], 0); in pc236_attach()
|
| D | rti802.c | 77 static int rti802_attach(struct comedi_device *dev, struct comedi_devconfig *it) in rti802_attach() argument
84 ret = comedi_request_region(dev, it->options[0], 0x04); in rti802_attach()
110 devpriv->dac_coding[i] = (it->options[3 + 2 * i]) in rti802_attach()
112 devpriv->range_type_list[i] = (it->options[2 + 2 * i]) in rti802_attach()
|
| D | pcl724.c | 95 struct comedi_devconfig *it) in pcl724_attach() argument
110 (it->options[2] == 1 || it->options[2] == 96)) { in pcl724_attach()
115 ret = comedi_request_region(dev, it->options[0], iorange); in pcl724_attach()
|
| D | pcmad.c | 112 static int pcmad_attach(struct comedi_device *dev, struct comedi_devconfig *it) in pcmad_attach() argument
118 ret = comedi_request_region(dev, it->options[0], 0x04); in pcmad_attach()
128 if (it->options[1]) { in pcmad_attach()
139 s->range_table = it->options[2] ? &range_bipolar10 : &range_unipolar5; in pcmad_attach()
|
| D | das16.c | 905 static int das16_probe(struct comedi_device *dev, struct comedi_devconfig *it) in das16_probe() argument
959 struct comedi_devconfig *it, in das16_ai_range() argument
963 unsigned int min = it->options[4]; in das16_ai_range()
964 unsigned int max = it->options[5]; in das16_ai_range()
995 struct comedi_devconfig *it) in das16_ao_range() argument
997 unsigned int min = it->options[6]; in das16_ao_range()
998 unsigned int max = it->options[7]; in das16_ao_range()
1024 static int das16_attach(struct comedi_device *dev, struct comedi_devconfig *it) in das16_attach() argument
1034 if (it->options[3]) { in das16_attach()
1035 if (it->options[3] != 1 && it->options[3] != 10) { in das16_attach()
[all …]
|
| D | amplc_dio200.c | 250 static int dio200_attach(struct comedi_device *dev, struct comedi_devconfig *it) in dio200_attach() argument
254 ret = comedi_request_region(dev, it->options[0], 0x20); in dio200_attach()
258 return amplc_dio200_common_attach(dev, it->options[1], 0); in dio200_attach()
|
| D | aio_iiro_16.c | 175 struct comedi_devconfig *it) in aio_iiro_16_attach() argument
180 ret = comedi_request_region(dev, it->options[0], 0x8); in aio_iiro_16_attach()
190 if ((1 << it->options[1]) & 0xdcfc) { in aio_iiro_16_attach()
191 ret = request_irq(it->options[1], aio_iiro_16_cos, 0, in aio_iiro_16_attach()
194 dev->irq = it->options[1]; in aio_iiro_16_attach()
|
| D | pcl812.c | 1017 struct comedi_devconfig *it) in pcl812_set_ai_range_table() argument
1024 if (it->options[4] == 1) in pcl812_set_ai_range_table()
1030 switch (it->options[4]) { in pcl812_set_ai_range_table()
1055 if (it->options[1] == 1) in pcl812_set_ai_range_table()
1061 switch (it->options[1]) { in pcl812_set_ai_range_table()
1082 switch (it->options[1]) { in pcl812_set_ai_range_table()
1129 static int pcl812_attach(struct comedi_device *dev, struct comedi_devconfig *it) in pcl812_attach() argument
1142 ret = comedi_request_region(dev, it->options[0], 0x10); in pcl812_attach()
1153 if ((1 << it->options[1]) & board->irq_bits) { in pcl812_attach()
1154 ret = request_irq(it->options[1], pcl812_interrupt, 0, in pcl812_attach()
[all …]
|
| /linux-4.4.14/kernel/ |
| D | cgroup_freezer.c | 248 struct css_task_iter it; in update_if_frozen() local
271 css_task_iter_start(css, &it); in update_if_frozen()
273 while ((task = css_task_iter_next(&it))) { in update_if_frozen()
288 css_task_iter_end(&it); in update_if_frozen()
320 struct css_task_iter it; in freeze_cgroup() local
323 css_task_iter_start(&freezer->css, &it); in freeze_cgroup()
324 while ((task = css_task_iter_next(&it))) in freeze_cgroup()
326 css_task_iter_end(&it); in freeze_cgroup()
331 struct css_task_iter it; in unfreeze_cgroup() local
334 css_task_iter_start(&freezer->css, &it); in unfreeze_cgroup()
[all …]
|
| /linux-4.4.14/net/bridge/netfilter/ |
| D | Kconfig | 49 To compile it as a module, choose M here. If unsure, say N.
58 To compile it as a module, choose M here. If unsure, say N.
67 To compile it as a module, choose M here. If unsure, say N.
76 To compile it as a module, choose M here. If unsure, say N.
85 To compile it as a module, choose M here. If unsure, say N.
93 To compile it as a module, choose M here. If unsure, say N.
101 To compile it as a module, choose M here. If unsure, say N.
110 To compile it as a module, choose M here. If unsure, say N.
119 If you want to compile it as a module, say M here and read
130 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/Documentation/power/ |
| D | s2ram.txt | 11 simple module unload can fix it.
19 always it's a driver that is buggy. Thank God for the suspend/resume
21 way to debug these things, and it's actually pretty powerful (but
39 - if it doesn't come back up (which is usually the problem), reboot by
50 fix it, disable it, or trace into its resume function.
60 used to run with "radeonfb" (it's an ATI Radeon mobility). It turns out
61 that "radeonfb" simply cannot resume that device - it tries to set the
62 PLL's, and it just _hangs_. Using the regular VGA console and letting X
63 resume it instead works fine.
72 pm_trace is not compatible with asynchronous suspend, so it turns
[all …]
|
| D | userland-swsusp.txt | 7 done it already.
22 reading, it is considered to be in the suspend mode. Otherwise it is
43 from it (0) (after resume the system finds itself finishing the
46 it out of the kernel
49 uploaded snapshot image; before calling it you should transfer
58 this number, but if it turns out to be impossible, the kernel will
79 partitions the offset is always 0, but it is different from zero for
91 be preceded by the SNAPSHOT_FREEZE call and it is also necessary
95 to disk, and then the system is suspended to RAM (this makes it possible
111 Thus it is not necessary to use either SNAPSHOT_FREE or
[all …]
|
| D | swsusp.txt | 14 * it may cause some problems, too. If you change kernel command line
15 * between suspend and resume, it may do something wrong. If you change
16 * your hardware while system is suspended... well, it was not good idea;
17 * but it will probably only crash.
19 * (*) suspend/resume support is needed to make it safe.
37 to RAM (provided your platform supports it), you can try
51 before suspend (it is limited to 500 MB by default).
54 if found, it then checks the contents for the hibernation image signature.
55 If both are found, it resumes the hibernation image.
74 Nowadays it is common in several laptops that they have a suspend button. It
[all …]
|
| D | pci.txt | 31 Usually, a device is put into a low-power state when it is underutilized or
32 completely inactive. However, when it is necessary to use the device once
33 again, it has to be put back into the "fully functional" state (full-power
50 to put the device that sent it into the full-power state. However, the PCI Bus
54 even though a PCI device is set up to generate PMEs, it also may be necessary to
60 preparing the device to generate wakeup signals. In that case, however, it
76 but it is mandatory for PCI Express devices. If a device supports the PCI PM
77 Spec, it has an 8 byte power management capability field in its PCI
88 programmed to go into it. The second one, D3cold, is the state that PCI devices
95 time of this writing and therefore it is not covered by this document.
[all …]
|
| D | freezing-of-tasks.txt | 10 II. How does it work?
23 sets this variable. After this, it executes try_to_freeze_tasks() that sends a
28 it loop until PF_FROZEN is cleared for it. Then, we say that the task is
39 signal-handling code, but the freezable kernel threads need to call it
92 directly is not allowed). From this point it is regarded as freezable
145 a kernel thread that belongs to a device driver accesses the device directly, it
146 in principle needs to know when the device is suspended, so that it doesn't try
147 to access it at that time. However, if the kernel thread is freezable, it will
148 be frozen before the driver's .suspend() callback is executed and it will be
149 thawed after the driver's .resume() callback has run, so it won't be accessing
[all …]
|
| D | swsusp-and-swap-files.txt | 4 The Linux kernel handles swap files almost in the same way as it handles swap
9 holds it. From the swsusp's point of view (1) is not a problem, because it is
14 help of appropriate filesystem driver. Unfortunately, however, it requires the
16 journaled, it cannot be mounted during resume from disk. For this reason to
24 1) Create the swap file and make it active, eg.
53 Now, swsusp will use the swap file in the same way in which it would use a swap
55 /proc/swaps) so that it can be used for suspending.
|
| D | suspend-and-cpuhotplug.txt | 7 infrastructure uses it internally? And where do they share common code?
62 code | and releases it when done] | O
63 | While it is at it, notifications |
131 code | and releases it when done]
132 | While it is at it, notifications
139 [That's it!, for
176 This is the most common situation and it is quite straightforward: we want
180 and thereby in applying the correct microcode revision to it.
202 Hence, when a new CPU is brought online, since the kernel finds that it
203 doesn't have the microcode image, it does the CPU type/model discovery
[all …]
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-light | 34 it comes back in SI units, it should also include _input else it
35 should include _raw to signify it is not in SI units.
54 value is returned in SI units, it should also include _input
55 but if it is not, then it should include _raw.
64 value is not in SI units, then it should include _raw.
96 value is not in SI units (irradiance, uW/mm^2), then it should
104 light sensor. If it comes back in SI units, it should also
105 include _input else it should include _raw to signify it is not
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-request-key.txt | 47 does not need to link the key to a keyring to prevent it from being immediately
49 it's up to the caller to destroy the key.
80 a suitable key there. If there is, it returns the key. If there isn't,
84 (3) request_key() sees that A doesn't have the desired key yet, so it creates
105 This will permit it to then search the keyrings of process A with the
106 UID, GID, groups and security info of process A as if it was process A,
109 (8) The program then does what it must to get the data with which to
110 instantiate key U, using key W as a reference (perhaps it contacts a
113 (9) Upon instantiating key U, auth key V is automatically revoked so that it
122 context specified by auth key X will still be process A, as it was in auth key
[all …]
|
| /linux-4.4.14/Documentation/fmc/ |
| D | fmc-write-eeprom.txt | 5 write it to the internal EEPROM of the mezzanine card. This driver uses
8 Overwriting the EEPROM is not something you should do daily, and it is
10 module makes it unlikely for the random user to change a working EEPROM.
20 such argument is received, it doesn't write anything to EEPROM
23 * If the file name ends with `.bin' it is written verbatim starting
26 * If the file name ends with `.tlv' it is interpreted as
27 type-length-value (i.e., it allows writev(2)-like operation).
29 * If the file name doesn't match any of the patterns above, it is
41 include the header (it is the actual number of bytes to be written).
59 the image starting at offset 0, it will deregister and register again
[all …]
|
| D | fmc-trivial.txt | 5 interrupt handler. I used it to verify the basic mechanism of the FMC
8 The module implements the generic FMC parameters, so it can program a
9 different gateware file in each card. The whole list of parameters it
|
| /linux-4.4.14/net/netfilter/ipvs/ |
| D | Kconfig | 23 If you want to compile it in kernel, say Y. To compile it as a
58 performance on it. You can adapt the table size yourself, according
64 should be not far less than 200x200, it is good to set the table
119 If you want to compile it in kernel, say Y. To compile it as a
132 If you want to compile it in kernel, say Y. To compile it as a
142 If you want to compile it in kernel, say Y. To compile it as a
152 If you want to compile it in kernel, say Y. To compile it as a
162 If you want to compile it in kernel, say Y. To compile it as a
173 If you want to compile it in kernel, say Y. To compile it as a
187 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /linux-4.4.14/Documentation/networking/ |
| D | netdev-FAQ.txt | 35 Q: How often do changes from these trees make it to the mainline Linus tree?
41 the merge window is closed, and it is called/tagged "-rc1". No new
81 and note the top of the "tags" section. If it is rc1, it is early
82 in the dev cycle. If it was tagged rc7 a week ago, then a release
95 manually change it yourself with whatever MUA you are comfortable with.
97 Q: I sent a patch and I'm wondering what happened to it. How can I tell
98 whether it got merged?
125 off to Greg. If Greg already has the patch, then it will be here:
137 Q: I see a network patch and I think it should be backported to stable.
138 Should I request it via "stable@vger.kernel.org" like the references in
[all …]
|
| D | driver.txt | 7 there is no way your device can tell ahead of time when it's
10 Instead it must maintain the queue properly. For example,
20 /* This is a hard error log it. */
49 /* This is a hard error log it. */
66 ndo_start_xmit method, it is your driver's responsibility to free
69 For example, this means that it is not allowed for your TX
77 to free it up.
82 be verified. For example, for ethernet check it with
|
| D | dmfe.txt | 5 This program is free software; you can redistribute it and/or
6 modify it under the terms of the GNU General Public License
10 This program is distributed in the hope that it will be useful,
18 didn't compile this driver as a module, it will automatically load itself on boot and print a
23 If you compiled this driver as a module, you have to load it on boot.You can load it with command :
27 This way it will autodetect the device mode.This is the suggested way to load the module.Or you can…
|
| D | eql.txt | 9 your link, in which it will help them out. This driver has been tested
13 source trees. (Yes, it worked fine.)
19 and have a ISP that is flexible, it is now possible to bind modems
27 balancing, but I do know that the PortMaster does it, and does it
28 almost as well as the eql driver seems to do it (-- Unfortunately, in
31 and 14.4 Kbps connection. However, I am not sure that it really is
32 the PortMaster, or if it's Linux's TCP drivers. I'm told that Linux's
36 I suggest to ISPs out there that it would probably be fair to charge
53 driver folded into it, get your copy of the driver from
97 so quickly."--) . How you configure it for other "connection"
[all …]
|
| D | ltpc.txt | 3 In order to use it, you will need at least version 1.3.3 of the
6 driver applies only to the one with the 65c02 processor chip on it.
8 To include it in the kernel, select the CONFIG_LTPC switch in the
9 configuration dialog. You can also compile it as a module.
39 with ifconfig so that Netatalk can find it.
52 present; otherwise, it refuses to seed. This is a hack, and a more
54 sure you have the correct name for the dummy interface - If it's
55 compiled as a module, you will need to refer to it as "dummy0" or some
59 it, then you don't need to fool around with this -- the appropriate
97 Yes, it is possible to do IP over LocalTalk. However, you can't just
[all …]
|
| D | policy-routing.txt | 5 I.e. it is tree of nodes (destination prefix, tos, metric)
67 We scan rules list, and if a rule is matched, apply it.
68 If a route is found, return it.
69 If it is not found or a THROW node was matched, continue
86 route maintenance, but it is ideal for manual configuration.
98 domains. Unfortunately, it is not widely used in the Internet.
128 I listed it just to show the power of new routing code.
136 Gated does not understand classes, but it will work
143 If it is set, locally originated packets are routed
146 I set it to FALSE by default.
|
| D | openvswitch.txt | 12 within a bridge). Each datapath also has associated with it a "flow
18 When a packet arrives on a vport, the kernel module processes it by
19 extracting its flow key and looking it up in the flow table. If there
20 is a matching flow, it executes the associated actions. If there is
21 no match, it queues the packet to userspace for processing (as part of
31 kernel module to remain relevant, it must be possible for newer
39 kernel module passes a packet to userspace, it also passes along the
40 flow key that it parsed from the packet. Userspace then extracts its
41 own notion of a flow key from the packet and compares it against the
49 headers but userspace stopped at the Ethernet type (because it
[all …]
|
| D | dns_resolver.txt | 25 set. The features it does support include:
77 it doesn't find it, it upcalls to userspace to make a new DNS query, which
91 The options parameter may be NULL or it may be a set of options
95 for the default query type it is just a list of comma-separated IPv4 and
105 The kernel maintains an internal keyring in which it caches looked up keys.
125 When dns_query() is invoked, it calls request_key() to search the local
126 keyrings for a cached DNS result. If that fails to find one, it upcalls to
140 lowest TTL of all the records it has extracted a result from. This means that
141 the key will be discarded and recreated when the data it holds has expired.
|
| D | spider_net.txt | 28 to receive data from the hardware. A "full" descriptor has data in it,
30 descriptor is neither empty or full; it is simply not ready. It may
31 not even have a data buffer in it, or is otherwise unusable.
44 marks it full, and advances the GDACTDPA by one. Thus, when there is
45 flowing RX traffic, every descr behind it should be marked "full",
46 and everything in front of it should be "empty". If the hardware
47 discovers that the current descr is not empty, it will signal an
52 descr. The OS will process this descr, and then mark it "not-in-use",
55 all of those behind it should be "not-in-use". When RX traffic is not
64 dma-mapping it so as to make it visible to the hardware. The OS will
[all …]
|
| D | rxrpc.txt | 57 making the session part of it a Linux network protocol (AF_RXRPC).
138 initiated by the first data packet on it arriving. If security is
142 upon it use that same security. In the event that the server lets a
183 the last call currently using it has completed in case a new call is made
184 that could reuse it.
187 time [tunable] after the last connection using it discarded, in case a new
188 connection is made that could use it.
195 (*) A server-side connection is shared if the client says it is.
231 the tag is guaranteed not to be seen again, and so it can be used to pin
266 (*) When the kernel has received and set up an incoming call, it sends a
[all …]
|
| D | tuntap.txt | 38 mkdir /dev/net (if it doesn't exist already)
53 support is enabled in your kernel. The kernel should load it on
60 If you do it the latter way, you have to load the module every time you
61 need it, if you do it the other way it will be automatically loaded when
161 calling it with IFF_DETACH_QUEUE flag, the queue were disabled. And when
162 calling it with IFF_ATTACH_QUEUE flag, the queue were enabled. The queue were
163 enabled by default after it was created through TUNSETIFF.
166 enable is true we enable it, otherwise we disable it
208 the kernel sends an IPX packet to tap0, it is passed to the application
209 (VTun for example). The application encrypts, compresses and sends it to
[all …]
|
| D | LICENSE.qlcnic | 17 of this license document, but changing it is not allowed.
22 freedom to share and change it. By contrast, the GNU General Public
27 using it. (Some other Free Software Foundation software is covered by
28 the GNU Lesser General Public License instead.) You can apply it to
34 this service if you wish), that you receive source code or can get it
35 if you want it, that you can change the software or use pieces of it
41 distribute copies of the software, or if you modify it.
63 program proprietary. To prevent this, we have made it clear that any
73 a notice placed by the copyright holder saying it may be distributed
77 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | LICENSE.qlge | 17 of this license document, but changing it is not allowed.
22 freedom to share and change it. By contrast, the GNU General Public
27 using it. (Some other Free Software Foundation software is covered by
28 the GNU Lesser General Public License instead.) You can apply it to
34 this service if you wish), that you receive source code or can get it
35 if you want it, that you can change the software or use pieces of it
41 distribute copies of the software, or if you modify it.
63 program proprietary. To prevent this, we have made it clear that any
73 a notice placed by the copyright holder saying it may be distributed
77 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | PLIP.txt | 29 It's cheap, it's available everywhere, and it's easy.
31 The PLIP cable is all that's needed to connect two Linux boxes, and it
55 it *is* getting late. EOB)
67 When a parallel port used for a PLIP driver has an IRQ configured to it, the
68 PLIP driver is signaled whenever data is sent to it via the cable, such that
71 However, on some machines it is hard, if not impossible, to configure an IRQ
72 to a certain parallel port, mainly because it is used by some other device.
75 and if such data is available, process it. This mode is less efficient than
91 On an i386, for example, 10^6/100 = 10000usec. It is easy to see that it is
93 the timeout is only 500usec long. As a result, it is required to change the
[all …]
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-lp3944.txt | 11 Antonio Ospite <ospite@studenti.unina.it>
17 DIM modes; it could even be used as a gpio expander but this driver assumes it
25 Setting a led in DIM0 or DIM1 mode makes it blink according to the pattern.
28 LP3944 can be found on Motorola A910 smartphone, where it drives the rgb
34 The chip is used mainly in embedded contexts, so this driver expects it is
47 and register it in the platform init function
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | relocate_kernel.S | 62 tml %r5,0x1 # is it a destination page?
65 nill %r6,0xf000 # mask it out and...
68 tml %r5,0x2 # is it a indirection page?
71 lgr %r2,%r5 # move it into the right register,
74 tml %r5,0x4 # is it the done indicator?
75 je .source_test # NO! Well, then it should be the source indicator...
76 j .done # ok, lets finish it here...
78 tml %r5,0x8 # it should be a source indicator...
79 je .top # NO, ignore it...
|
| /linux-4.4.14/sound/usb/ |
| D | pcm.c | 868 struct snd_interval *it = hw_param_interval(params, SNDRV_PCM_HW_PARAM_RATE); in hw_check_valid_format() local
890 if (fp->rate_min > it->max || (fp->rate_min == it->max && it->openmax)) { in hw_check_valid_format()
891 hwc_debug(" > check: rate_min %d > max %d\n", fp->rate_min, it->max); in hw_check_valid_format()
894 if (fp->rate_max < it->min || (fp->rate_max == it->min && it->openmin)) { in hw_check_valid_format()
895 hwc_debug(" > check: rate_max %d < min %d\n", fp->rate_max, it->min); in hw_check_valid_format()
914 struct snd_interval *it = hw_param_interval(params, SNDRV_PCM_HW_PARAM_RATE); in hw_rule_rate() local
918 hwc_debug("hw_rule_rate: (%d,%d)\n", it->min, it->max); in hw_rule_rate()
937 it->empty = 1; in hw_rule_rate()
942 if (it->min < rmin) { in hw_rule_rate()
943 it->min = rmin; in hw_rule_rate()
[all …]
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 20 is discovered) and it is registered with sysfs. Its attributes then
41 it by doing
47 subsystems. Once a client subsystem is loaded, it will appear as a
64 When an item needs to be destroyed, remove it with rmdir(2). An
65 item cannot be destroyed if any other item has a link to it (via
71 access remote block devices. Call it FakeNBD. FakeNBD uses configfs
74 the driver about it. Here's where configfs comes in.
76 When the FakeNBD driver is loaded, it registers itself with configfs.
84 it is a uuid or a disk name:
99 That's it. That's all there is. Now the device is configured, via the
[all …]
|
| /linux-4.4.14/net/netfilter/ipset/ |
| D | Kconfig | 11 To compile it as a module, choose M here. If unsure, say N.
34 To compile it as a module, choose M here. If unsure, say N.
43 To compile it as a module, choose M here. If unsure, say N.
52 To compile it as a module, choose M here. If unsure, say N.
62 To compile it as a module, choose M here. If unsure, say N.
71 To compile it as a module, choose M here. If unsure, say N.
80 To compile it as a module, choose M here. If unsure, say N.
90 To compile it as a module, choose M here. If unsure, say N.
100 To compile it as a module, choose M here. If unsure, say N.
109 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/gpu/drm/i915/ |
| D | i915_gem_userptr.c | 58 struct interval_tree_node it; member
132 if (mo->it.last < start || mo->it.start > end) in i915_gem_userptr_mn_invalidate_range_start()
138 struct interval_tree_node *it; in i915_gem_userptr_mn_invalidate_range_start() local
140 it = interval_tree_iter_first(&mn->objects, start, end); in i915_gem_userptr_mn_invalidate_range_start()
141 while (it) { in i915_gem_userptr_mn_invalidate_range_start()
142 mo = container_of(it, struct i915_mmu_object, it); in i915_gem_userptr_mn_invalidate_range_start()
144 it = interval_tree_iter_next(it, start, end); in i915_gem_userptr_mn_invalidate_range_start()
185 struct interval_tree_node *it; in i915_mmu_notifier_add() local
202 it = interval_tree_iter_first(&mn->objects, in i915_mmu_notifier_add()
203 mo->it.start, mo->it.last); in i915_mmu_notifier_add()
[all …]
|
| /linux-4.4.14/arch/x86/kvm/ |
| D | paging_tmpl.h | 557 struct kvm_shadow_walk_iterator it; in FNAME() local
578 for (shadow_walk_init(&it, vcpu, addr); in FNAME()
579 shadow_walk_okay(&it) && it.level > gw->level; in FNAME()
580 shadow_walk_next(&it)) { in FNAME()
583 clear_sp_write_flooding_count(it.sptep); in FNAME()
584 drop_large_spte(vcpu, it.sptep); in FNAME()
587 if (!is_shadow_present_pte(*it.sptep)) { in FNAME()
588 table_gfn = gw->table_gfn[it.level - 2]; in FNAME()
589 sp = kvm_mmu_get_page(vcpu, table_gfn, addr, it.level-1, in FNAME()
590 false, access, it.sptep); in FNAME()
[all …]
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 20 device is still attached or perhaps it was removed and a different
26 though they had disconnected. This is always safe and it is the
33 it.
49 it's as though you had unplugged all the USB devices. Yes, it's
61 the system can't be suspended at all. (All right, it _can_ be
62 suspended -- but it will crash as soon as it wakes up, which isn't
74 reset or otherwise had lost power) then it applies a persistence check
77 can't work once the power session is gone. Instead it issues a USB
83 kernel treats the device as though it had merely been reset instead of
101 devices for which it is enabled. You can enable the feature by doing
[all …]
|
| D | gadget_multi.txt | 9 In it's standard configuration it provides a single USB configuration
22 To make use of the gadget one needs to make it work on host side --
29 to Linux host it does not need any additional drivers on Linux host
54 create a proper INF -- and of course, if you do submit it!
61 For mass storage it is trivial since Windows detect it's an interface
74 RNDIS was not the first interface. You do not need to worry abut it
87 interface numbers hard-coded in them (it's not hard to change those
110 Knowing how MacOS is based on BSD and BSD is an Open Source it is
111 believed that it should (read: "I have no idea whether it will") work
142 [6] To put it in some other nice words, Windows failed to respond to
|
| D | WUSB-Design-overview.txt | 7 This program is free software; you can redistribute it and/or
8 modify it under the terms of the GNU General Public License version
11 This program is distributed in the hope that it will be useful,
86 associated spectrum to allow for devices sharing it. Allows to
114 whose root port is the radio and the WUSB devices connect to it.
115 To the system it looks like a separate USB host. The driver (will)
117 for which the root hub is the radio...To reiterate: it is a USB
123 package provides a driver for it (it looks like a network
131 wired devices, but it is connected to your PC connected via Wireless
132 USB. To the system it looks like yet another USB host. To the untrained
[all …]
|
| D | authorization.txt | 10 As of now, when a USB device is connected it is configured and
13 then it be possible to use it.
44 can be connected (for example, it is a kiosk machine with a visible
66 to break it). If you need something secure, use crypto and Certificate
72 echo 1 > authorized # temporarily authorize it
73 # FIXME: make sure none can mount it
80 # Other stuff so others can use it
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | operations.txt | 24 FS-Cache has an asynchronous operations handling facility that it uses for its
53 struct embedded in it. They should initialise it by calling:
79 may decide it wants to handle an operation itself without deferring it to
89 before submitting the operation, and the operating thread must wait for it
96 (2) The operation may be fast asynchronous (FSCACHE_OP_FAST), in which case it
109 (3) The operation may be slow asynchronous (FSCACHE_OP_SLOW), in which case it
141 (1) The submitting thread must allocate the operation and initialise it
167 it, so the caller should put their reference to it by passing it to:
172 operation with FSCACHE_OP_MYTHREAD, then it should monitor
176 When it has finished doing its processing, it should call
[all …]
|
| D | object.txt | 37 or even by no objects (it may not be cached).
89 those cookies are hidden from it.
101 Each state has an action associated with it that is invoked when the machine
105 representations are hierarchical, and it is expected that an object must
120 When a state has finished processing, it will usually set the mask of events in
121 which it is interested (object->event_mask) and relinquish the worker thread.
158 The object state machine has a set of states that it can be in. There are
165 the cache, it is expected that it will not be possible to look an object
176 object is represented there, and if it is, to see if it's valid (coherency
221 The object is undergoing invalidation. When the state comes here, it
[all …]
|
| D | netfs-api.txt | 14 may or may not have anything associated with it, but the netfs doesn't
91 (2) To make it easier to discard a subset of all the files cached based around
94 However, since it's unlikely that any two netfs's are going to want to define
96 restraints as possible on how an index is structured and where it is placed in
98 it's not recommended.
110 (2) The entry data must be atomically journallable, so it is limited to about
188 If this function is not supplied or if it returns NULL then the first
195 cookie acquisition function and the maximum length of key data that it may
197 return the quantity it wrote.
212 it may provide. It should write the auxiliary data into the given buffer
[all …]
|
| D | cachefiles.txt | 48 and whilst it is open, a cache is at least partially in existence. The daemon
49 opens this and sends commands down it to control the cache.
54 the filesystem, shrinking the cache by culling the objects it contains to make
55 space if necessary - see the "Cache Culling" section. This means it can be
131 configures the cache and tells it to begin caching. At that point the cache
226 their atimes have changed or if the kernel module says it is still using them.
233 The CacheFiles module will create two directories in the directory it was
241 kernel module moves any retired or culled objects that it can't simply unlink
260 If an object has children, then it will be represented as a directory.
274 If the key is so long that it exceeds NAME_MAX with the decorations added on to
[all …]
|
| D | backend-api.txt | 6 FS-Cache for it to then serve out to network filesystems and other interested
50 successful and will release it upon withdrawal of the cache.
57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
101 and is for use by the cache as it sees fit.
144 that refer to a particular object. In such a case it should be printed
147 Each object contains a pointer to the cookie that represents the object it
148 is backing. An object should retired when put_object() is called if it is
165 FS-Cache has a pool of threads that it uses to give CPU time to the
169 rid of it when its usage count reaches 0.
172 appropriate flag before enqueuing it with fscache_enqueue_operation(). If
[all …]
|
| /linux-4.4.14/arch/tile/kernel/ |
| D | stack.c | 83 unsigned long sp = kbt->it.sp; in valid_fault_handler()
127 (kbt->it.pc == ((ulong)kbt->task->mm->context.vdso_base + in is_sigreturn()
135 BacktraceIterator *b = &kbt->it; in valid_sigframe()
167 backtrace_init(&kbt->it, read_memory_func, kbt, in KBacktraceIterator_restart()
181 } while (backtrace_next(&kbt->it)); in KBacktraceIterator_next_item_inclusive()
255 backtrace_init(&kbt->it, read_memory_func, kbt, pc, lr, sp, r52); in KBacktraceIterator_init()
268 unsigned long old_pc = kbt->it.pc, old_sp = kbt->it.sp; in KBacktraceIterator_next()
270 if (!backtrace_next(&kbt->it) && !KBacktraceIterator_restart(kbt)) { in KBacktraceIterator_next()
275 if (old_pc == kbt->it.pc && old_sp == kbt->it.sp) { in KBacktraceIterator_next()
387 unsigned long address = kbt->it.pc; in tile_show_stack()
[all …]
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | NOTES | 2 been able to track it down yet. This does not occur with the emulator
5 I also found one oddity in the emulator. I don't think it is serious but
6 will point it out. The ARM calling conventions require floating point
9 function, and an ldfe instruction to restore it before returning.
11 I was looking at some code, that calculated a double result, stored it in f4
19 emulator sees a multiply of a double and extended, it promotes the double to
28 moved to f4 to preserve it over the log(y) call. The division will be done
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | binding.txt | 5 driver that can control it. Bus drivers have typically handled this
15 type in the system. When device_register is called for a device, it is
18 for a driver, it is inserted at the end of this list. These are the
26 to find one that supports it. In order to determine that, the device
30 algorithm, it is up to the bus driver to provide a callback to compare
38 chance to verify that it really does support the hardware, and that
39 it's in a working state.
45 the class to which it belongs. Device drivers belong to one and only one
48 and actually register it with the class, which happens with the
90 When a device is removed, the reference count for it will eventually
[all …]
|
| D | driver.txt | 19 also initialize the devclass field (when it arrives), so it may obtain
28 driver. This declaration is hypothetical only; it relies on the driver
46 typically defines an array of device IDs that it supports. The format
75 even a bit ugly. So far, it's the best way we've found to do what we want...
109 complexity and code size, it is recommended that they are converted as
115 Once the object has been registered, it may access the common fields of
124 node access, and does proper reference counting on each device as it
125 accesses it.
137 directory will contain symlinks to the directories of devices it
156 it's a version the driver can handle, that driver data structures can
[all …]
|
| /linux-4.4.14/Documentation/scsi/ |
| D | qlogicfas.txt | 16 Nor does it support the PCI-Basic, which is supported by the
28 the Linux PCMCIA driver, you will have to adjust it or otherwise stop
29 it from configuring the card.
31 I am working with the PCMCIA group to make it more flexible, but that
37 configuration. As shipped, it provides a balance between speed and
46 if you have reliable hardware and connections it may be more useful to
51 Make sure it works properly under DOS. You should also do an initial FDISK
66 realbig.doc realbig.doc". Then do it after the computer gets warm.
71 that it gets a false ACK causing an extra byte to be inserted into the
77 Remember, if it doesn't work under DOS, it probably won't work under
|
| D | LICENSE.qla4xxx | 18 of this license document, but changing it is not allowed.
23 freedom to share and change it. By contrast, the GNU General Public
28 using it. (Some other Free Software Foundation software is covered by
29 the GNU Lesser General Public License instead.) You can apply it to
35 this service if you wish), that you receive source code or can get it
36 if you want it, that you can change the software or use pieces of it
42 distribute copies of the software, or if you modify it.
64 program proprietary. To prevent this, we have made it clear that any
74 a notice placed by the copyright holder saying it may be distributed
78 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | LICENSE.qla2xxx | 19 of this license document, but changing it is not allowed.
24 freedom to share and change it. By contrast, the GNU General Public
29 using it. (Some other Free Software Foundation software is covered by
30 the GNU Lesser General Public License instead.) You can apply it to
36 this service if you wish), that you receive source code or can get it
37 if you want it, that you can change the software or use pieces of it
43 distribute copies of the software, or if you modify it.
65 program proprietary. To prevent this, we have made it clear that any
75 a notice placed by the copyright holder saying it may be distributed
79 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | in2000.txt | 7 recent kernels, it has failed to function at all when
11 with. Done some heavy testing and it looks very good.
30 Also put all the header data in in2000.h where it belongs.
33 and 2.1.45 (or is it .46?) - this makes things much easier
58 I _think_ it may have been a little too lax, causing an
61 with it, start by doing 'cat /proc/scsi/in2000/0'. You
62 can also use it to change a few run-time parameters on
63 the fly, but it's mostly for debugging. The curious
65 in2000.c file to get an understanding of what it's all
66 about; I figure that people who are really into it will
[all …]
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | platform_no_drv_owner.cocci | 1 /// Remove .owner field if calls are used which set it automatically
126 msg = "No need to set .owner here. The core will do it."
133 msg = "No need to set .owner here. The core will do it."
140 msg = "No need to set .owner here. The core will do it."
147 msg = "No need to set .owner here. The core will do it."
156 msg = "No need to set .owner here. The core will do it."
163 msg = "No need to set .owner here. The core will do it."
170 msg = "No need to set .owner here. The core will do it."
177 msg = "No need to set .owner here. The core will do it."
|
| /linux-4.4.14/arch/mn10300/mm/ |
| D | cache.inc | 6 * This program is free software; you can redistribute it and/or
7 * modify it under the terms of the GNU General Public Licence
20 # On some cores it is necessary to disable the icache whilst we do this.
39 # and wait for it to calm down
55 # and reenable it
81 # On some cores it is necessary to disable the dcache whilst we do this.
100 # and wait for it to calm down
116 # and reenable it
|
| /linux-4.4.14/Documentation/RCU/ |
| D | UP.txt | 6 is that since there is only one CPU, it should not be necessary to
9 work a surprising amount of the time, it is a very bad idea in general.
19 is referencing element B when it is interrupted by softirq processing,
35 by having call_rcu() directly invoke its arguments only if it was called
39 elements A, B, and C in process contexts, but that it invokes a function
40 on each element as it is scanned. Suppose further that this function
41 deletes element B from the list, then passes it to call_rcu() for deferred
42 freeing. This may be a bit unconventional, but it is perfectly legal
45 its arguments would cause it to fail to make the fundamental guarantee
49 Quick Quiz #1: why is it -not- legal to invoke synchronize_rcu() in
[all …]
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | submitting-patches | 26 architecture. If run-time testing was not achieved, it should be written
30 CONFIG_SMP, make sure it compiles for all configuration variants.
42 your patch into a cleanup part and the actual addition. This makes it easier
52 formatting is clean. If unsure about formatting in your new driver, run it
54 cleanup, but it is a good start.
67 may save a line or so in the source, it obfuscates the code and makes code
74 * If the driver has a detect function, make sure it is silent. Debug messages
75 and messages printed after a successful detection are acceptable, but it
86 discouraged as it is known to cause trouble with other (non-hwmon) I2C
92 only do it after you have already gathered enough data to be certain that the
[all …]
|
| D | adm1025 | 16 * No temperature offset register, but we don't use it anyway.
17 * No INT mode for pin 16. We don't play with it anyway.
41 it is not a choice you have to make as the user. The choice was already
45 process, assuming that the BIOS set it up properly beforehand. If it turns
50 only in that it has "open-drain VID inputs while the ADM1025 has on-chip
|
| /linux-4.4.14/Documentation/trace/ |
| D | ring-buffer-design.txt | 64 but a writer may interrupt another writer, but it must finish writing
82 cannot preempt/interrupt a writer, but it may read/consume from the
105 to read from the buffer, if its page is empty (like it is on start-up),
106 it will swap its page with the head_page. The old reader page will
112 it wants with it, as long as a writer has left that page.
115 show the head page in the buffer, it is for demonstrating a swap
192 When the writer leaves the page, it simply goes into the ring buffer
215 is finished writing data into that position, it commits the write.
218 transaction. If another write happens it must finish before continuing
283 preempted another write is committed, it only becomes a pending commit
[all …]
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | VIBRA16 | 10 Playing with a SB Vibra 16x soundcard we found it very difficult
15 (tried it with a 2.2.2-ac7), nor in the commercial OSS package (it reports
16 it as half-duplex soundcard). Oh, I almost forgot, the RedHat sndconfig
17 failed detecting it ;)
19 8-bit and a 16-bit dma, which we could not allocate for vibra... it supports
47 # Joystick device - only if you need it :-/
|
| D | SoundPro | 15 The chip emulates a WSS as well as a SB16, but it has certain differences
24 Detection should work, but it hasn't been widely tested, so it might still
26 parameters for ad1848. Please let me know if it happens to you, so I can
29 The chip is capable of doing full-duplex, but since the driver sees it as an
30 AD1848, it cannot take advantage of this. Moreover, the full-duplex mode is
31 not achievable through the WSS interface, b/c it needs a dma16 line which is
34 it might be possible to do the same thing under Linux. You can try loading
36 recording. I don't know if this works, b/c I haven't tested it. Anyway, if
37 you try it, be very careful: the SB16 mixer *mostly* works, but certain
41 no idea if the driver will work with it. I suspect it won't.
|
| D | AudioExcelDSP16 | 6 Please, read the head of the source before using it. It contain useful
14 and, if you want it, the Roland MPU-401 (do not use the Sound Blaster MPU-401,
17 of the Audio Excel initialization: it must be the same as the SBPRO (or MSS)
18 setup. If the parameters are different, correct it.
21 check off all the configuration items before re-configure it.
71 information about it, please let me know.
85 the audio card and will recognize and attach it.
92 > To: riccardo@cdc8g5.cdc.polimi.it (Riccardo Facchetti)
101 fizban@tin.it
|
| /linux-4.4.14/Documentation/vm/ |
| D | page_owner.txt | 14 using it for analyzing who allocate each page is rather complex. We need
17 buffer for later analysis and it would change system behviour with more
18 possibility rather than just keeping it in memory, so bad for debugging.
25 page owner is disabled in default. So, if you'd like to use it, you need
28 boot option, runtime overhead is marginal. If disabled in runtime, it
31 the page allocator hotpath and if it returns false then allocation is
47 230 bytes and only half of it is in hotpath. Building the kernel with
48 page owner and turning it on if needed would be great option to debug
55 they would have no owner information. To fix it up, these early allocated
57 Although it doesn't mean that they have the right owner information,
|
| D | transhuge.txt | 12 Currently it only works for anonymous memory mappings but in the
13 future it can expand over the pagecache layer starting with tmpfs.
16 factors. The first factor is almost completely irrelevant and it's not
17 of significant interest because it'll also have the downside of
53 - it doesn't require memory reservation and in turn it uses hugepages
56 is not specific to transparent hugepage support and it's a generic
61 regions but it'd be ideal to move it to tmpfs and the pagecache
71 advantage of it.
82 large region but only touch 1 byte of it, in that case a 2M page might
83 be allocated instead of a 4k page for no good. This is why it's
[all …]
|
| D | idle_page_tracking.txt | 14 it consists of the only read-write file, /sys/kernel/mm/page_idle/bitmap.
21 A page is considered idle if it has not been accessed since it was marked idle
62 considered referenced if it has been recently accessed via a process address
63 space, in which case one or more PTEs it is mapped to will have the Accessed bit
71 because a process needs filesystem metadata stored in it (e.g. lists a
77 exceeding the dirty memory limit, it is not marked referenced.
84 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
94 it only works with pages that are on an LRU list, other pages are silently
95 ignored. That means it will ignore a user memory page if it is isolated, but
96 since there are usually not many of them, it should not affect the overall
|
| D | frontswap.txt | 12 Frontswap is so named because it can be thought of as the opposite of
20 frontswap_ops funcs appropriately and the functions it provides must
25 copy the page to transcendent memory and associate it with the type and
34 succeed. So when the kernel finds itself in a situation where it needs
35 to swap out a page, it first attempts to use frontswap. If the store returns
95 i.e. when system A is overcommitted, it can swap to system B, and
104 it well with no kernel changes have essentially failed (except in some
129 request (i.e. provides no memory despite claiming it might),
157 accessible by the kernel. Exactly how much memory it provides is
167 consults with the frontswap backend and if the backend says it does NOT
[all …]
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 115 13.13 When you run UML, it immediately segfaults
163 hardware, it talks to a `real' Linux kernel (called the `host kernel'
197 6. You can use it as a sandbox for testing new apps.
237 3. Make a directory and unpack the kernel into it.
285 you want to change something, go ahead, it probably won't hurt
376 4. boot the kernel on it
435 Booting UML is straightforward. Simply run 'linux': it will try to
437 run it as root. If your root filesystem is not named `root_fs', then
465 variety of commands and utilities installed (and it is fairly easy to
476 /dev and /etc/inittab runs a getty on it) will come up in its own
[all …]
|
| /linux-4.4.14/arch/arm64/kvm/ |
| D | emulate.c | 87 unsigned long it; in kvm_condition_valid32() local
89 it = ((cpsr >> 8) & 0xFC) | ((cpsr >> 25) & 0x3); in kvm_condition_valid32()
92 if (it == 0) in kvm_condition_valid32()
96 cond = (it >> 4); in kvm_condition_valid32()
|
| /linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/ |
| D | alloc.c | 250 struct mlx4_zone_entry *it; in mlx4_zone_add_one() local
270 list_for_each_entry(it, &zone_alloc->prios, prio_list) in mlx4_zone_add_one()
271 if (it->priority >= priority) in mlx4_zone_add_one()
274 if (&it->prio_list == &zone_alloc->prios || it->priority > priority) in mlx4_zone_add_one()
275 list_add_tail(&zone->prio_list, &it->prio_list); in mlx4_zone_add_one()
276 list_add_tail(&zone->list, &it->list); in mlx4_zone_add_one()
308 struct mlx4_zone_entry *it; in __mlx4_zone_remove_one_entry() local
310 list_for_each_entry(it, &zone_alloc->prios, prio_list) { in __mlx4_zone_remove_one_entry()
311 u32 cur_mask = mlx4_bitmap_masked_value(it->bitmap, (u32)-1); in __mlx4_zone_remove_one_entry()
362 struct mlx4_zone_entry *it = curr_node; in __mlx4_alloc_from_zone() local
[all …]
|
| /linux-4.4.14/Documentation/input/ |
| D | input-programming.txt | 76 First it has to include the <linux/input.h> file, which interfaces to the
80 booting the kernel, it grabs the required resources (it should also check
83 Then it allocates a new input device structure with input_allocate_device()
85 parts of the input systems what it is - what events can be generated or
109 which upon every interrupt from the button checks its state and reports it
131 In case the driver has to repeatedly poll the device, because it doesn't
132 have an interrupt coming from it and the polling is too expensive to be done
133 all the time, or if the device uses a valuable resource (eg. interrupt), it
134 can use the open and close callback to know when it can stop polling or
135 release the interrupt and when it must resume polling or grab the interrupt
[all …]
|
| D | cd32.txt | 2 joypad connected to the parallel port. Thought I'd share it with you so
3 you can add it to the list of supported joysticks (hopefully someone will
4 find it useful).
|
| D | input.txt | 8 This program is free software; you can redistribute it and/or modify it
13 This program is distributed in the hope that it will be useful, but
32 devices under Linux. While it is currently used only on for USB input
34 most of the existing input system, which is why it lives in
38 loaded before any other of the input modules - it serves as a way of
71 The commands to create it by hand are:
78 XFree to this device to use it - GPM should be called like:
104 and because the USB HID specification isn't simple, it needs to be this big.
106 Currently, it handles USB mice, joysticks, gamepads, steering wheels
113 interface, but for the UPSs and LCDs it doesn't make much sense. For this,
[all …]
|
| D | ff.txt | 12 (as it is already the case), but to really enable the rendering of force
30 should keep a hand on your device, in order to avoid it to break down if
36 2.1 Does it work ?
83 supports it yet.
118 stops the effect if it was playing.
168 and I think it should be an effect, which computation depends on the game
169 type. But you can enable it if you want.
186 setting the id field to -1, you set it to the wanted effect id.
190 case, the driver stops the effect, up-load it, and restart it.
192 Therefore it is recommended to dynamically change direction while the effect
[all …]
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | README | 5 for them sysctl files? If anybody really needs it, it's all in
12 Furthermore, the programmers who built sysctl have built it to
13 be actually used, not just for the fun of programming it :-)
21 2. it's free
30 it. Not only to have a great laugh, but also to make sure that
44 don't even need special tools to do it!
75 really like to hear about it :-)
|
| /linux-4.4.14/Documentation/i2c/ |
| D | fault-codes | 14 result for an operation ... it doesn't indicate that anything is wrong
19 the right fault code, so that it can (in turn) behave correctly.
82 it needs to do so.
86 of a transfer didn't get an ACK. While it might just mean
87 an I2C device was temporarily not responding, usually it
95 that it doesn't, or can't, support.
100 have verified that functionality was supported before it
104 messages, it should return this when asked to perform a
105 transaction it can't. (These limitations can't be seen in
107 that if an adapter supports I2C it supports all of I2C.)
[all …]
|
| D | i2c-stub | 13 quick commands to the specified addresses; it will respond to the other
15 arrays in memory. It will also spam the kernel logs for every command it
59 If your target driver polls some byte or word waiting for it to change, the
60 stub could lock it up. Use i2cset to unlock it.
62 If you spam it hard enough, printk can be lossy. This module really wants
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 7 This program is free software; you can redistribute it and/or modify
8 it under the terms of the GNU General Public License as published by
12 This program is distributed in the hope that it will be useful,
27 can use it to adjust system clock time.
32 case when a new pulse arrives the system must apply to it a timestamp
33 and record it for userland.
47 At startup it needs a file descriptor as argument for the function
52 useful besides(!) the gathering of timestamps as it is the central
112 parameters for the device should be (it is obvious that these parameters
125 (pps_ktimer_echo(), passing to it the "ptr" pointer) if the user
[all …]
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-piix4 | 39 functionality. Among other things, it implements the PCI bus. One of its
41 SMBus - you can not access it on I2C levels. The good news is that it
43 timing problems. The bad news is that non-SMBus devices connected to it can
44 confuse it mightily. Yes, this is known to happen...
46 Do 'lspci -v' and see whether it contains an entry like this:
58 try to enable it. THIS IS VERY DANGEROUS! If the BIOS did not set up a
63 'force' foes, but it will also set a new base I/O port address. The SMBus
69 The PIIX4E is just an new version of the PIIX4; it is supported as well.
78 secondary controller, it will be detected by this driver as
90 2) Now you just need to change the value in 0xD2 register. Get it first with
[all …]
|
| /linux-4.4.14/ |
| D | COPYING | 6 Foundation, but the instance of code that it refers to (the Linux
7 kernel) is copyrighted by me and others who actually wrote it.
23 of this license document, but changing it is not allowed.
28 freedom to share and change it. By contrast, the GNU General Public
33 using it. (Some other Free Software Foundation software is covered by
34 the GNU Library General Public License instead.) You can apply it to
40 this service if you wish), that you receive source code or can get it
41 if you want it, that you can change the software or use pieces of it
47 distribute copies of the software, or if you modify it.
69 program proprietary. To prevent this, we have made it clear that any
[all …]
|
| /linux-4.4.14/fs/befs/ |
| D | ChangeLog | 50 * Fixed a longstanding bug in befs_find_key() that would result in it
51 finding the first key that is a substring of the string it is searching
86 * Remove the typedef of struct super_block to vfs_sb, as it offended
107 dir.c, namei.c befs_fs.h to account for it. [WD]
126 in directories. A cleaner solution will come after I've thought about it
141 callback defined in your address_space_ops, even if it just uses the
197 * Removed all the Read-Write stuff. I'll redo it when it is time to add
206 * Made it an option to use the old non-pagecache befs_file_read() for
217 I've done some serious testing on it now (on my box anyhow), and it
219 correct (see TODO list). But it isn't 1.0 yet. I think 0.4 gives me some
[all …]
|
| /linux-4.4.14/drivers/char/tpm/ |
| D | Kconfig | 12 say Yes and it will be accessible from within Linux. For
33 specification (TPM2.0) say Yes and it will be accessible from
41 If you have an Atmel I2C TPM security chip say Yes and it will be
52 Specification 0.20 say Yes and it will be accessible from within
62 Nuvoton Technology Corp. say Yes and it will be accessible
72 say Yes and it will be accessible from within Linux. To
80 If you have a TPM security chip from Atmel say Yes and it
89 (either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it
100 If you have IBM virtual TPM (VTPM) support say Yes and it
110 say Yes and it will be accessible from within Linux. See
[all …]
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | videobuf | 22 address spaces. (Almost) all user-space buffers are like this, but it
24 it is possible. Unfortunately, it is not always possible; working with
43 functionality is considered to be deprecated for most use, but it still
83 check it for rationality and adjust it if need be. As a practical rule, a
92 VIDEOBUF_NEEDS_INIT, the driver should pass it to:
101 When a buffer is queued for I/O, it is passed to buf_queue(), which should
102 put it onto the driver's list of available buffers and set its state to
104 held; if it tries to acquire it as well things will come to a screeching
106 wait on the first buffer in the queue; placing other buffers in front of it
111 then pass it to the appropriate free routine(s):
[all …]
|
| D | README.saa7134 | 3 What is it?
32 driver. "modprobe saa7134" should load it. Depending on the card you
41 forget to tell me what it changes / which problem it fixes / whatever
42 it is good for ...
|
| /linux-4.4.14/drivers/net/wireless/ath/wil6210/ |
| D | Kconfig | 14 If you choose to build it as a module, it will be called
25 it saves extra target transaction;
28 self-clear when accessed for debug purposes, it makes
42 If unsure, say Y to make it easier to debug problems.
|
| /linux-4.4.14/arch/arm/probes/ |
| D | decode.h | 60 unsigned long it = cpsr & mask; in it_advance() local
61 it <<= 1; in it_advance()
62 it |= it >> (27 - 10); /* Carry ITSTATE<2> to correct place */ in it_advance()
63 it &= mask; in it_advance()
65 cpsr |= it; in it_advance()
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | boost.txt | 11 very moment, but only that the CPU _may_ raise the frequency at it's
19 if the whole chip is not fully utilized and below it's intended thermal
22 On Intel CPUs this is called "Turbo Boost", AMD calls it "Turbo-Core",
39 2. To examine the impact of the boosting functionality it is helpful
52 driver exports a sysfs knob to enable or disable it. There is a file:
67 not necessarily mean that it will occur every time even using the exact
79 which was simply reflected into each CPU's file. Writing a 0 or 1 into it
82 on AMD CPUs, though it is now protected by a config switch
91 Technically it is possible to switch the boosting functionality at least
93 does not support it, but this may be implemented in the future.
|
| /linux-4.4.14/drivers/isdn/hisax/ |
| D | Kconfig | 96 See <file:Documentation/isdn/README.HiSax> on how to configure it
106 See <file:Documentation/isdn/README.HiSax> on how to configure it
115 See <file:Documentation/isdn/README.HiSax> on how to configure it.
122 configure it.
130 See <file:Documentation/isdn/README.HiSax> on how to configure it
139 See <file:Documentation/isdn/README.HiSax> on how to configure it.
145 See <file:Documentation/isdn/README.HiSax> on how to configure it.
153 See <file:Documentation/isdn/README.HiSax> on how to configure it
163 See <file:Documentation/isdn/README.HiSax> on how to configure it
173 See <file:Documentation/isdn/README.HiSax> on how to configure it
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | copying | 7 of this license document, but changing it is not allowed.
12 freedom to share and change it. By contrast, the GNU General Public
17 using it. (Some other Free Software Foundation software is covered by
18 the GNU Library General Public License instead.) You can apply it to
24 this service if you wish), that you receive source code or can get it
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
53 program proprietary. To prevent this, we have made it clear that any
63 a notice placed by the copyright holder saying it may be distributed
67 that is to say, a work containing the Program or a portion of it,
[all …]
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | COPYING | 7 of this license document, but changing it is not allowed.
12 freedom to share and change it. By contrast, the GNU General Public
17 using it. (Some other Free Software Foundation software is covered by
18 the GNU Library General Public License instead.) You can apply it to
24 this service if you wish), that you receive source code or can get it
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
53 program proprietary. To prevent this, we have made it clear that any
63 a notice placed by the copyright holder saying it may be distributed
67 that is to say, a work containing the Program or a portion of it,
[all …]
|
| D | INSTALL | 8 unlimited permission to copy, distribute and modify it.
22 definitions. Finally, it creates a shell script `config.status' that
38 may remove or edit it.
42 you want to change it or regenerate `configure' using a newer version
50 Running `configure' might take a while. While running, it prints
51 some messages telling which features it is checking for.
66 for the package's developers. If you use it, you may have to get
98 With a non-GNU `make', it is safer to compile the package for one
122 If the package supports it, you can cause programs to be installed
137 find the X include and library files automatically, but if it doesn't,
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8192e/ |
| D | license | 14 document, but changing it is not allowed.
19 share and change it. By contrast, the GNU General Public License is intended
23 whose authors commit to using it. (Some other Free Software Foundation
25 can apply it to your programs, too.
30 wish), that you receive source code or can get it if you want it, that you
31 can change the software or use pieces of it in new free programs; and that
37 copies of the software, or if you modify it.
58 proprietary. To prevent this, we have made it clear that any patent must be
67 placed by the copyright holder saying it may be distributed under the
71 work containing the Program or a portion of it, either verbatim or with
[all …]
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-nice-design.txt | 8 scheduler, (otherwise we'd have done it long ago) because nice level
16 understand it, the timeslice graph went like this (cheesy ASCII art
40 HZ=1000 it caused 1 jiffy to be 1 msec, which meant 0.1% CPU usage which
41 we felt to be a bit excessive. Excessive _not_ because it's too small of
42 a CPU utilization, but because it causes too frequent (once per
51 terms of CPU utilization, we only got complaints about it (still) being
54 To sum it up: we always wanted to make nice levels more consistent, but
56 coupling to timeslices and granularity it was not really viable.
75 depend on the nice level of the parent shell - if it was at nice -10 the
76 CPU split was different than if it was at +5 or +10.
[all …]
|
| D | sched-domains.txt | 7 A domain's span MUST be a superset of it child's span (this restriction could
10 although strictly it doesn't have to, but this could lead to a case where some
34 The latter function takes two arguments: the current CPU and whether it was idle
37 While doing that, it checks to see if the current domain has exhausted its
38 rebalance interval. If so, it runs load_balance() on that domain. It then checks
39 the parent sched_domain (if it exists), and the parent of the parent and so
43 If it succeeds, it looks for the busiest runqueue of all the CPUs' runqueues in
44 that group. If it manages to find such a runqueue, it locks both our initial
45 CPU's runqueue and the newly found busiest one and starts moving tasks from it
|
| D | completion.txt | 77 most likely a bug as it re-initializes the queue to an empty queue and
105 For a thread of execution to wait for some concurrent work to finish, it
120 immediately as all dependencies are satisfied if not it will block until
124 so it can only be called safely when you know that interrupts are enabled.
125 Calling it from hard-irq or irqs-off atomic contexts will result in
162 while waiting it will return -ERESTARTSYS; 0 otherwise.
168 (in jiffies). If timeout occurs it returns 0 else the remaining time in
178 TASK_INTERRUPTIBLE. If a signal was received it will return -ERESTARTSYS;
179 otherwise it returns 0 if the completion timed out or the remaining time in
183 designated tasks state and will return -ERESTARTSYS if it is interrupted or
[all …]
|
| D | sched-arch.txt | 30 clear it.
32 3. When cpu_idle finds (need_resched() == 'true'), it should call
38 need_resched, it prevents losing an interrupt).
51 although it may be reasonable to do some background work or enter
55 an interrupt sleep, it needs to be cleared then a memory
68 ia64 - is safe_halt call racy vs interrupts? (does it sleep?) (See #4a)
|
| /linux-4.4.14/drivers/usb/storage/ |
| D | Kconfig | 40 If this driver is compiled as a module, it will be named ums-realtek.
54 If this driver is compiled as a module, it will be named ums-datafab.
63 If this driver is compiled as a module, it will be named ums-freecom.
81 If this driver is compiled as a module, it will be named ums-isd200.
104 If this driver is compiled as a module, it will be named ums-usbat.
114 If this driver is compiled as a module, it will be named ums-sddr09.
123 If this driver is compiled as a module, it will be named ums-sddr55.
132 If this driver is compiled as a module, it will be named ums-jumpshot.
144 If this driver is compiled as a module, it will be named ums-alauda.
159 If this driver is compiled as a module, it will be named ums-onetouch.
[all …]
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | Kconfig | 26 To compile it as a module, choose M here. If unsure, say N.
134 To compile it as a module, choose M here. If unsure, say N.
145 To compile it as a module, choose M here. If unsure, say N.
155 To compile it as a module, choose M here. If unsure, say N.
164 To compile it as a module, choose M here. If unsure, say N.
173 To compile it as a module, choose M here. If unsure, say N.
191 To compile it as a module, choose M here. If unsure, say N.
199 To compile it as a module, choose M here. If unsure, say N.
209 To compile it as a module, choose M here. If unsure, say N.
219 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/arch/mn10300/kernel/ |
| D | mn10300-watchdog-low.S | 8 # This program is free software; you can redistribute it and/or
9 # modify it under the terms of the GNU General Public Licence
49 # - kept to absolute minimum (unfortunately, it's prototyped in linux/nmi.h so
50 # we can't inline it)
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | cdns,xtensa-pic.txt | 8 When it's 1, the first cell is the internal IRQ number.
9 When it's 2, the first cell is the IRQ number, and the second cell
10 specifies whether it's internal (0) or external (1).
12 core variants it may be mapped to different internal IRQ.
|
| /linux-4.4.14/drivers/net/irda/ |
| D | Kconfig | 11 discipline. To compile it as a module, choose M here: the module
12 will be called irtty-sir. IrTTY makes it possible to use Linux's
31 Saying M, it will be built as a module named bfin_sir.
94 JetEye PC dongle. To compile it as a module, choose M here. The ESI
105 IR220L+ dongles. To compile it as a module, choose M here. The
116 dongle. To compile it as a module, choose M here. The Tekram dongle
128 To compile it as a module, choose M here.
135 dongle. To compile it as a module, choose M here. The Parallax
146 dongle. To compile it as a module, choose M here. The MA600 dongle
159 dongle. If you want to compile it as a module, choose M here.
[all …]
|
| /linux-4.4.14/arch/ia64/kernel/ |
| D | mca.c | 360 #define IA64_LOG_ALLOCATE(it, size) \ argument
361 {ia64_state_log[it].isl_log[IA64_LOG_CURR_INDEX(it)] = \
363 ia64_state_log[it].isl_log[IA64_LOG_NEXT_INDEX(it)] = \
365 #define IA64_LOG_LOCK_INIT(it) spin_lock_init(&ia64_state_log[it].isl_lock) argument
366 #define IA64_LOG_LOCK(it) spin_lock_irqsave(&ia64_state_log[it].isl_lock, s) argument
367 #define IA64_LOG_UNLOCK(it) spin_unlock_irqrestore(&ia64_state_log[it].isl_lock,s) argument
368 #define IA64_LOG_NEXT_INDEX(it) ia64_state_log[it].isl_index argument
369 #define IA64_LOG_CURR_INDEX(it) 1 - ia64_state_log[it].isl_index argument
370 #define IA64_LOG_INDEX_INC(it) \ argument
371 {ia64_state_log[it].isl_index = 1 - ia64_state_log[it].isl_index; \
[all …]
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | get_op.S | 46 | normalized number it becomes a denormalized number. The
431 | ;know if it should set ete15 or fpte15
432 | ;ie, it doesn't know if this is the
498 bnes try_zero |if not equal, it is not special
501 bnes try_zero |if not on, it is not special
504 bnes fix_nan |if non-zero, it is a NaN
506 bnes fix_nan |if non-zero, it is a NaN
511 orl #snaniop_mask,USER_FPSR(%a6) |always set snan if it is so
535 fmovemx %fp0-%fp1,-(%a7) |save fp0 - decbin returns in it
550 bnes mtry_zero |if not equal, it is not special
[all …]
|
| /linux-4.4.14/Documentation/fb/ |
| D | tridentfb.txt | 26 How to use it?
38 noaccel - turns off acceleration (when it doesn't work for your card)
48 look at the driver output to see what it says when initializing.
51 more memory than it actually has. For instance mine is 192K less than
59 nativex - the width in pixels of the flat panel.If you know it (usually 1024
60 800 or 1280) and it is not what the driver seems to detect use it.
|
| D | matroxfb.txt | 22 How to use it?
82 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
98 mode for console. You can do it at boot time by using videomode
101 Switching to another console and back fixes it. I hope that it is SVGALib's
115 it always probe for memory. Default is to use whole detected
120 configuration, you can override it by this (you cannot override
129 it is autodetected for intel's 82437. In this case device does
130 not comply to PCI 2.1 specs (it will not guarantee that every
137 enable VGA I/O if BIOS did not it (it is not safe to enable it in
145 it if you have G100 and/or if driver cannot detect memory, you see
[all …]
|
| /linux-4.4.14/net/core/ |
| D | netclassid_cgroup.c | 72 struct css_task_iter it; in update_classid() local
75 css_task_iter_start(css, &it); in update_classid()
76 while ((p = css_task_iter_next(&it))) { in update_classid()
81 css_task_iter_end(&it); in update_classid()
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | nbd.txt | 7 What is it: With this compiled in the kernel (or as a module), Linux
9 the client computer wants to read, e.g., /dev/nb0, it sends a
13 Unlike NFS, it is possible to put any filesystem on it, etc.
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | locking.txt | 16 shadow page table is present and it is caused by write-protect, that means
23 the gfn is writable on guest mmu and it is not write-protected by shadow
61 For direct sp, we can easily avoid it since the spte of direct sp is fixed
66 - The pfn is writable that means it can not be shared between different gfns
79 But it is not true after fast page fault since the spte can be marked
114 if it can be updated out of mmu-lock, see spte_has_volatile_bits(), it means,
127 Since the spte is "volatile" if it can be updated out of mmu-lock, we always
157 Comment: it is a spinlock since it is used in mmu notifier.
168 if it is needed by multiple functions.
174 Comment: This is a per-CPU lock and it is used for VT-d posted-interrupts.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | exynos_thermal_emulation | 17 When it's enabled, sysfs node will be created as
21 temperature you want to update to sysfs node, it automatically enable emulation mode and
22 current temperature will be changed into it.
28 mode at the same time. (Or you have to keep the mode enabling.) If you don't, it fails to
30 this node gives users the right to change termerpature only. Just one interface makes it more
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 55 To compile it as a module, choose M here. If unsure, say N.
133 the flow-stop time (once it has been destroyed) via Connection
165 If you want to compile it as a module, say M here and read
176 To compile it as a module, choose M here. If unsure, say N.
191 To compile it as a module, choose M here. If unsure, say N.
205 To compile it as a module, choose M here. If unsure, say N.
213 important VoIP protocols, it is widely used by voice hardware and
225 To compile it as a module, choose M here. If unsure, say N.
240 To compile it as a module, choose M here. If unsure, say N.
262 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 40 the latter, since it makes troubleshooting a lot easier. The built-in
45 don't know how to set it properly in the driver. The options are:
59 the cam is a bit slow or momentarily busy. However, on slow machines it
61 reasonable. You can set it between 2 and 5.
71 However, it doesn't really buffer images, it just gives you a bit more
75 The absolute maximum is 10, but don't set it too high! Every buffer takes
100 High compression takes less bandwidth of course, but it could also
120 the LED never goes on, making it suitable for silent surveillance.
134 never know what device a camera gets assigned; it depends on module load
136 and the phase of the moon (i.e. it can be random). With this option you
[all …]
|
| /linux-4.4.14/arch/cris/boot/compressed/ |
| D | README | 4 This can be slightly confusing because it's a process with many steps.
20 Be careful - it assumes some things about free locations in DRAM. It
21 assumes the DRAM starts at 0x40000000 and that it is at least 8 MB,
22 so it puts its code at 0x40700000, and initial stack at 0x40800000.
|
| /linux-4.4.14/Documentation/w1/slaves/ |
| D | w1_ds2406 | 13 These chips also provide 128 bytes of OTP EPROM, but reading/writing it is
15 can be provided with power on a dedicated input. In TO-92 form, it provides
18 The driver provides two sysfs files. state is readable; it gives the
22 respectively. Bits 2-7 are ignored, so it's safe to write ASCII data.
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
47 This is usually a subnode of ocp2scp to which it is connected.
84 PHY). If "id" is not provided, it is set to default value of '1'.
89 This is usually a subnode of ocp2scp to which it is connected.
|
| /linux-4.4.14/Documentation/crypto/ |
| D | descore-readme.txt | 7 This program is free software; you can redistribute it and/or modify
8 it under the terms of the GNU Library General Public License as published by
12 This program is distributed in the hope that it will be useful,
40 up in a parameterized fashion so it can easily be modified by speed-daemon
41 hackers in pursuit of that last microsecond. You will find it more
88 it's a bit weak on common low-level optimizations which is why
89 it's 39%-106% slower. because he was interested in fast crypt(3) and
98 crypt function and i didn't feel like ripping it out and measuring
111 when the machine's architecture allows it.
115 as in crypt above, the des routine is buried in a loop. it's
[all …]
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 5.Posting | 23 When posting code which is not yet considered ready for inclusion, it is a
76 out how to do it in the way that the community expects. There are a few
91 verified to do what it says it does.
96 good chance that it will be passed over and the important fix will be
106 - Do not overdo it, though. One developer once posted a set of edits
109 be reasonably large as long as it still contains a single *logical*
122 done. When done properly, though, it is time well spent.
134 but it never hurts to add it when in doubt.
137 enough for a reader who sees it with no other context to figure out the
138 scope of the patch; it is the line that will show up in the "short form"
[all …]
|
| D | 8.Conclusion | 52 Congratulations to anybody who has made it through this long-winded
53 document. Hopefully it has provided a helpful understanding of how the
56 In the end, it's the participation that matters. Any open source software
57 project is no more than the sum of what its contributors put into it. The
58 Linux kernel has progressed as quickly and as well as it has because it has
60 working to make it better. The kernel is a premier example of what can be
|
| D | 4.Coding | 6 (or not) into the mainline tree. So it is the quality of this code which
30 before they will even review it. A code base as large as the kernel
31 requires some uniformity of code to make it possible for developers to
32 quickly understand any part of it. So there is no longer room for
48 on it for other reasons, but coding style changes should not be made for
54 80-column limit, for example), just do it.
69 in case somebody eventually needs to use the extra flexibility that it
72 never noticed - because it has never been used. Or, when the need for
73 extra flexibility arises, it does not do so in a way which matches the
84 from another kernel subsystem, it is time to ask whether it would, in fact,
[all …]
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 19 it is not recommended because it looks ugly on some machines and
29 If you say Y here, it will be possible to use a 8250/16550 serial
39 For most systems, it is firmware or second stage bootloader that
41 it might be necessary or advantageous to either override the
42 default kernel command line or add a few extra options to it.
98 debug it.
102 debug it. for example, add a new serial port support just as
126 force it to always emit branches with delay slots, and make no use
135 it to make use of compact branch instructions where it deems them
144 force it to always emit compact branches, making no use of branch
|
| /linux-4.4.14/drivers/bluetooth/ |
| D | Kconfig | 31 kernel or say M to compile it as module (btusb).
64 kernel or say M to compile it as module (btsdio).
77 kernel or say M to compile it as module (hci_uart).
129 The HCI Three-wire UART Transport Layer makes it possible to
182 kernel or say M to compile it as module (bcm203x).
194 kernel or say M to compile it as module (bpa10x).
207 kernel or say M to compile it as module (bfusb).
220 kernel or say M to compile it as module (dtl1_cs).
234 kernel or say M to compile it as module (bt3c_cs).
247 kernel or say M to compile it as module (bluecard_cs).
[all …]
|
| /linux-4.4.14/firmware/ |
| D | README.AddingFirmware | 29 that it is redistributable. If the licence is long and involved, it's
30 permitted to include it in a separate file and refer to it from the
32 And if it were possible, a changelog of the firmware itself.
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.wimax | 15 common services, the APIs it currently provides are very minimal.
16 However, it is done in such a way that it is easily extensible to
51 directory named wimax:DEVICENAME to be created; optionally, it might
52 create more subentries below it.
72 level; by writing to it, you can set it.
|
| /linux-4.4.14/Documentation/acpi/ |
| D | scan_handlers.txt | 27 Similarly, if the device node represents a PCI interrupt link, it is necessary
28 to configure that link so that the kernel can use it.
49 device nodes in the given namespace scope with the driver core. Then, it tries
54 for carrying out any additional configuration tasks related to it. It also will
57 handler that has claimed it.
59 If the .attach() callback returns 0, it means that the device node is not
61 handler in the list. If it returns a (negative) error code, that means that
67 scope (if they have scan handlers). Next, it unregisters all of the device
77 first time and they cannot be removed from it.
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 18 We reference the header for the inode pointing to it, across each
19 outstanding RPC call that references it (LAYOUTGET, LAYOUTRETURN,
25 keeps it in the list.
48 pointing to it.
53 bit which holds it in the pnfs_layout_hdr's list. When the final lseg
83 If Kernel does not find the osd_login_prog path it will zero it out
85 to the objlayoutdriver.osd_login_prog Kernel parameter to re-enable it.
96 The client does not interpret this string it is
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | cache-policies.txt | 4 Try to keep transactionality out of it. The core is careful to
6 makes it easier to write the policies.
17 Because we map bios, rather than requests it's easy for the policy
51 considered sequential it will bypass the cache. The random threshold
68 count of a block not in the cache goes above this threshold it gets
98 SMQ uses 28bit indexes to implement it's data structures rather than
114 SMQ does not maintain a hit count, instead it swaps hit entries with
122 different block to get promoted to the cache it's hit count has to
123 exceed the lowest currently in the cache. This means it can take a
129 away. In addition it tracks performance of the hotspot queue, which
[all …]
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 43 it is possible that the interrupt may arrive before all the data has
75 and it may depend on some other options also being set. For example,
104 If this function returns a positive number it indicates the number of
107 updates dev->irq to be the lowest of the new interrupts assigned to it.
113 If this function returns a negative number, it indicates an error and
153 interrupts it could request a particular number of interrupts by passing
190 If this function returns a negative number, it indicates an error and
203 Calling it restores dev->irq to the pin-based interrupt number and frees
208 on any interrupt for which it previously called request_irq().
221 If this function returns a negative number, it indicates the device is
[all …]
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 25 most of the time it can't be helped. Anytime a high priority process wants
37 meantime, B executes, and since B is of a higher priority than C, it preempts C,
38 but by doing so, it is in fact preempting A which is a higher priority process.
68 of A. So now if B becomes runnable, it would not preempt C, since C now has
69 the high priority of A. As soon as C releases the lock, it loses its
97 a process being blocked on the mutex, it is fine to allocate
163 also call it the Top of the chain) must be equal to or higher in priority
166 Also since a mutex may have more than one process blocked on it, we can
189 The implementation of plist is out of scope for this document, but it is
190 very important to understand what it does.
[all …]
|
| /linux-4.4.14/arch/arm64/boot/dts/qcom/ |
| D | apq8016-sbc.dts | 4 * This program is free software; you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License version 2 and
8 * This program is distributed in the hope that it will be useful,
|
| D | msm8916-mtp.dts | 4 * This program is free software; you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License version 2 and
8 * This program is distributed in the hope that it will be useful,
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | mt6592-evb.dts | 5 * This program is free software; you can redistribute it and/or modify
6 * it under the terms of the GNU General Public License version 2 as
9 * This program is distributed in the hope that it will be useful,
|
| D | mt8127-moose.dts | 5 * This program is free software; you can redistribute it and/or modify
6 * it under the terms of the GNU General Public License version 2 as
9 * This program is distributed in the hope that it will be useful,
|