| /linux-4.4.14/arch/cris/include/arch-v32/arch/ |
| D | uaccess.h | 162 #define __asm_copy_user_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
172 : "=b" (to), "=b" (from), "=r" (ret) \
173 : "0" (to), "1" (from), "2" (ret) \
176 #define __asm_copy_from_user_1(to, from, ret) \ argument
177 __asm_copy_user_cont(to, from, ret, \
185 #define __asm_copy_from_user_2x_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
186 __asm_copy_user_cont(to, from, ret, \
197 #define __asm_copy_from_user_2(to, from, ret) \ argument
198 __asm_copy_from_user_2x_cont(to, from, ret, "", "", "")
200 #define __asm_copy_from_user_3(to, from, ret) \ argument
[all …]
|
| /linux-4.4.14/arch/cris/include/arch-v10/arch/ |
| D | uaccess.h | 156 #define __asm_copy_user_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
167 : "=r" (to), "=r" (from), "=r" (ret) \
168 : "0" (to), "1" (from), "2" (ret) \
171 #define __asm_copy_from_user_1(to, from, ret) \ argument
172 __asm_copy_user_cont(to, from, ret, \
179 #define __asm_copy_from_user_2x_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
180 __asm_copy_user_cont(to, from, ret, \
187 #define __asm_copy_from_user_2(to, from, ret) \ argument
188 __asm_copy_from_user_2x_cont(to, from, ret, "", "", "")
190 #define __asm_copy_from_user_3(to, from, ret) \ argument
[all …]
|
| /linux-4.4.14/arch/metag/lib/ |
| D | usercopy.c | 27 #define __asm_copy_user_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
40 : "=r" (to), "=r" (from), "=r" (ret) \
41 : "0" (to), "1" (from), "2" (ret) \
45 #define __asm_copy_to_user_1(to, from, ret) \ argument
46 __asm_copy_user_cont(to, from, ret, \
53 #define __asm_copy_to_user_2x_cont(to, from, ret, COPY, FIXUP, TENTRY) \ argument
54 __asm_copy_user_cont(to, from, ret, \
61 #define __asm_copy_to_user_2(to, from, ret) \ argument
62 __asm_copy_to_user_2x_cont(to, from, ret, "", "", "")
64 #define __asm_copy_to_user_3(to, from, ret) \ argument
[all …]
|
| /linux-4.4.14/arch/cris/include/asm/ |
| D | uaccess.h | 193 extern unsigned long __copy_user(void __user *to, const void *from, unsigned long n);
194 extern unsigned long __copy_user_zeroing(void *to, const void __user *from, unsigned long n);
195 extern unsigned long __do_clear_user(void __user *to, unsigned long n);
198 __generic_copy_to_user(void __user *to, const void *from, unsigned long n) in __generic_copy_to_user() argument
200 if (access_ok(VERIFY_WRITE, to, n)) in __generic_copy_to_user()
201 return __copy_user(to, from, n); in __generic_copy_to_user()
206 __generic_copy_from_user(void *to, const void __user *from, unsigned long n) in __generic_copy_from_user() argument
209 return __copy_user_zeroing(to, from, n); in __generic_copy_from_user()
214 __generic_clear_user(void __user *to, unsigned long n) in __generic_clear_user() argument
216 if (access_ok(VERIFY_WRITE, to, n)) in __generic_clear_user()
[all …]
|
| /linux-4.4.14/arch/m68k/hp300/ |
| D | hp300map.map | 11 # be saved by mapping AltGr to Alt (and adapting a few entries):
185 compose '`' 'A' to '�'
186 compose '`' 'a' to '�'
187 compose '\'' 'A' to '�'
188 compose '\'' 'a' to '�'
189 compose '^' 'A' to '�'
190 compose '^' 'a' to '�'
191 compose '~' 'A' to '�'
192 compose '~' 'a' to '�'
193 compose '"' 'A' to '�'
[all …]
|
| /linux-4.4.14/fs/xfs/libxfs/ |
| D | xfs_inode_buf.c | 199 xfs_icdinode_t *to, in xfs_dinode_from_disk() argument
202 to->di_magic = be16_to_cpu(from->di_magic); in xfs_dinode_from_disk()
203 to->di_mode = be16_to_cpu(from->di_mode); in xfs_dinode_from_disk()
204 to->di_version = from ->di_version; in xfs_dinode_from_disk()
205 to->di_format = from->di_format; in xfs_dinode_from_disk()
206 to->di_onlink = be16_to_cpu(from->di_onlink); in xfs_dinode_from_disk()
207 to->di_uid = be32_to_cpu(from->di_uid); in xfs_dinode_from_disk()
208 to->di_gid = be32_to_cpu(from->di_gid); in xfs_dinode_from_disk()
209 to->di_nlink = be32_to_cpu(from->di_nlink); in xfs_dinode_from_disk()
210 to->di_projid_lo = be16_to_cpu(from->di_projid_lo); in xfs_dinode_from_disk()
[all …]
|
| D | xfs_sb.c | 352 struct xfs_sb *to, in __xfs_sb_from_disk() argument
356 to->sb_magicnum = be32_to_cpu(from->sb_magicnum); in __xfs_sb_from_disk()
357 to->sb_blocksize = be32_to_cpu(from->sb_blocksize); in __xfs_sb_from_disk()
358 to->sb_dblocks = be64_to_cpu(from->sb_dblocks); in __xfs_sb_from_disk()
359 to->sb_rblocks = be64_to_cpu(from->sb_rblocks); in __xfs_sb_from_disk()
360 to->sb_rextents = be64_to_cpu(from->sb_rextents); in __xfs_sb_from_disk()
361 memcpy(&to->sb_uuid, &from->sb_uuid, sizeof(to->sb_uuid)); in __xfs_sb_from_disk()
362 to->sb_logstart = be64_to_cpu(from->sb_logstart); in __xfs_sb_from_disk()
363 to->sb_rootino = be64_to_cpu(from->sb_rootino); in __xfs_sb_from_disk()
364 to->sb_rbmino = be64_to_cpu(from->sb_rbmino); in __xfs_sb_from_disk()
[all …]
|
| D | xfs_da_format.c | 139 xfs_dir2_inou_t *to, in xfs_dir2_sf_put_ino() argument
145 put_unaligned_be64(ino, &to->i8.i); in xfs_dir2_sf_put_ino()
147 put_unaligned_be32(ino, &to->i4.i); in xfs_dir2_sf_put_ino()
454 struct xfs_dir3_icleaf_hdr *to, in xfs_dir2_leaf_hdr_from_disk() argument
457 to->forw = be32_to_cpu(from->hdr.info.forw); in xfs_dir2_leaf_hdr_from_disk()
458 to->back = be32_to_cpu(from->hdr.info.back); in xfs_dir2_leaf_hdr_from_disk()
459 to->magic = be16_to_cpu(from->hdr.info.magic); in xfs_dir2_leaf_hdr_from_disk()
460 to->count = be16_to_cpu(from->hdr.count); in xfs_dir2_leaf_hdr_from_disk()
461 to->stale = be16_to_cpu(from->hdr.stale); in xfs_dir2_leaf_hdr_from_disk()
463 ASSERT(to->magic == XFS_DIR2_LEAF1_MAGIC || in xfs_dir2_leaf_hdr_from_disk()
[all …]
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-upload.txt | 1 This document describes how to upload the cx2341x firmware to the card.
3 How to find
7 on how to obtain the firmware.
16 How to load
19 - Issue the FWapi command to stop the encoder if it is running. Wait for the
20 command to complete.
21 - Issue the FWapi command to stop the decoder if it is running. Wait for the
22 command to complete.
23 - Issue the I2C command to the digitizer to stop emitting VSYNC events.
24 - Issue the FWapi command to halt the encoder's firmware.
[all …]
|
| /linux-4.4.14/arch/x86/include/asm/ |
| D | uaccess_32.h | 14 (void __user *to, const void *from, unsigned long n);
16 (void *to, const void __user *from, unsigned long n);
18 (void *to, const void __user *from, unsigned long n);
20 (void *to, const void __user *from, unsigned long n);
22 (void *to, const void __user *from, unsigned long n);
44 __copy_to_user_inatomic(void __user *to, const void *from, unsigned long n) in __copy_to_user_inatomic() argument
51 __put_user_size(*(u8 *)from, (u8 __user *)to, in __copy_to_user_inatomic()
55 __put_user_size(*(u16 *)from, (u16 __user *)to, in __copy_to_user_inatomic()
59 __put_user_size(*(u32 *)from, (u32 __user *)to, in __copy_to_user_inatomic()
63 __put_user_size(*(u64 *)from, (u64 __user *)to, in __copy_to_user_inatomic()
[all …]
|
| D | string_32.h | 32 static __always_inline void *__memcpy(void *to, const void *from, size_t n) in __memcpy() argument
42 : "0" (n / 4), "g" (n), "1" ((long)to), "2" ((long)from) in __memcpy()
44 return to; in __memcpy()
51 static __always_inline void *__constant_memcpy(void *to, const void *from, in __constant_memcpy() argument
56 return to; in __constant_memcpy()
60 *(char *)to = *(char *)from; in __constant_memcpy()
61 return to; in __constant_memcpy()
63 *(short *)to = *(short *)from; in __constant_memcpy()
64 return to; in __constant_memcpy()
66 *(int *)to = *(int *)from; in __constant_memcpy()
[all …]
|
| /linux-4.4.14/arch/x86/kernel/ |
| D | signal_compat.c | 4 int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from) in copy_siginfo_to_user32() argument
9 if (!access_ok(VERIFY_WRITE, to, sizeof(compat_siginfo_t))) in copy_siginfo_to_user32()
18 put_user_ex(from->si_signo, &to->si_signo); in copy_siginfo_to_user32()
19 put_user_ex(from->si_errno, &to->si_errno); in copy_siginfo_to_user32()
20 put_user_ex((short)from->si_code, &to->si_code); in copy_siginfo_to_user32()
23 put_user_ex(from->si_pid, &to->si_pid); in copy_siginfo_to_user32()
24 put_user_ex(from->si_uid, &to->si_uid); in copy_siginfo_to_user32()
25 put_user_ex(ptr_to_compat(from->si_ptr), &to->si_ptr); in copy_siginfo_to_user32()
32 &to->_sifields._pad[0]); in copy_siginfo_to_user32()
37 put_user_ex(from->si_syscall, &to->si_syscall); in copy_siginfo_to_user32()
[all …]
|
| /linux-4.4.14/arch/m68k/include/asm/ |
| D | uaccess_mm.h | 202 unsigned long __generic_copy_from_user(void *to, const void __user *from, unsigned long n);
203 unsigned long __generic_copy_to_user(void __user *to, const void *from, unsigned long n);
205 #define __constant_copy_from_user_asm(res, to, from, tmp, n, s1, s2, s3)\ argument
235 : "+d" (res), "+&a" (to), "+a" (from), "=&d" (tmp) \
239 __constant_copy_from_user(void *to, const void __user *from, unsigned long n) in __constant_copy_from_user() argument
245 __get_user_asm(res, *(u8 *)to, (u8 __user *)from, u8, b, d, 1); in __constant_copy_from_user()
248 __get_user_asm(res, *(u16 *)to, (u16 __user *)from, u16, w, r, 2); in __constant_copy_from_user()
251 __constant_copy_from_user_asm(res, to, from, tmp, 3, w, b,); in __constant_copy_from_user()
254 __get_user_asm(res, *(u32 *)to, (u32 __user *)from, u32, l, r, 4); in __constant_copy_from_user()
257 __constant_copy_from_user_asm(res, to, from, tmp, 5, l, b,); in __constant_copy_from_user()
[all …]
|
| D | uaccess_no.h | 130 #define copy_from_user(to, from, n) (memcpy(to, from, n), 0) argument
131 #define copy_to_user(to, from, n) (memcpy(to, from, n), 0) argument
133 #define __copy_from_user(to, from, n) copy_from_user(to, from, n) argument
134 #define __copy_to_user(to, from, n) copy_to_user(to, from, n) argument
138 #define copy_to_user_ret(to,from,n,retval) ({ if (copy_to_user(to,from,n)) return retval; }) argument
140 #define copy_from_user_ret(to,from,n,retval) ({ if (copy_from_user(to,from,n)) return retval; }) argument
173 __clear_user(void *to, unsigned long n) in __clear_user() argument
175 memset(to, 0, n); in __clear_user()
179 #define clear_user(to,n) __clear_user(to,n) argument
|
| /linux-4.4.14/drivers/tty/vt/ |
| D | defkeymap.map | 11 # be saved by mapping AltGr to Alt (and adapting a few entries):
290 compose '`' 'A' to '�'
291 compose '`' 'a' to '�'
292 compose '\'' 'A' to '�'
293 compose '\'' 'a' to '�'
294 compose '^' 'A' to '�'
295 compose '^' 'a' to '�'
296 compose '~' 'A' to '�'
297 compose '~' 'a' to '�'
298 compose '"' 'A' to '�'
[all …]
|
| /linux-4.4.14/arch/x86/lib/ |
| D | usercopy_32.c | 71 clear_user(void __user *to, unsigned long n) in clear_user() argument
74 if (access_ok(VERIFY_WRITE, to, n)) in clear_user()
75 __do_clear_user(to, n); in clear_user()
92 __clear_user(void __user *to, unsigned long n) in __clear_user() argument
94 __do_clear_user(to, n); in __clear_user()
101 __copy_user_intel(void __user *to, const void *from, unsigned long size) in __copy_user_intel() argument
199 : "1"(to), "2"(from), "0"(size) in __copy_user_intel()
205 __copy_user_zeroing_intel(void *to, const void __user *from, unsigned long size) in __copy_user_zeroing_intel() argument
291 : "1"(to), "2"(from), "0"(size) in __copy_user_zeroing_intel()
301 static unsigned long __copy_user_zeroing_intel_nocache(void *to, in __copy_user_zeroing_intel_nocache() argument
[all …]
|
| D | mmx_32.c | 28 void *_mmx_memcpy(void *to, const void *from, size_t len) in _mmx_memcpy() argument
34 return __memcpy(to, from, len); in _mmx_memcpy()
36 p = to; in _mmx_memcpy()
79 : : "r" (from), "r" (to) : "memory"); in _mmx_memcpy()
82 to += 64; in _mmx_memcpy()
103 : : "r" (from), "r" (to) : "memory"); in _mmx_memcpy()
106 to += 64; in _mmx_memcpy()
111 __memcpy(to, from, len & 63); in _mmx_memcpy()
158 static void fast_copy_page(void *to, void *from) in fast_copy_page() argument
204 _ASM_EXTABLE(1b, 3b) : : "r" (from), "r" (to) : "memory"); in fast_copy_page()
[all …]
|
| D | usercopy_64.c | 49 unsigned long clear_user(void __user *to, unsigned long n) in clear_user() argument
51 if (access_ok(VERIFY_WRITE, to, n)) in clear_user()
52 return __clear_user(to, n); in clear_user()
57 unsigned long copy_in_user(void __user *to, const void __user *from, unsigned len) in copy_in_user() argument
59 if (access_ok(VERIFY_WRITE, to, len) && access_ok(VERIFY_READ, from, len)) { in copy_in_user()
60 return copy_user_generic((__force void *)to, (__force void *)from, len); in copy_in_user()
72 copy_user_handle_tail(char *to, char *from, unsigned len) in copy_user_handle_tail() argument
74 for (; len; --len, to++) { in copy_user_handle_tail()
79 if (__put_user_nocheck(c, to, sizeof(char))) in copy_user_handle_tail()
85 if (!__addr_ok(to)) in copy_user_handle_tail()
[all …]
|
| /linux-4.4.14/fs/nls/ |
| D | Kconfig | 10 as the ability of some filesystems to use native languages
26 system (if different) to store data (filenames) on a disk.
44 in so-called DOS codepages. You need to include the appropriate
45 codepage if you want to be able to read/write these filenames on
46 DOS/Windows partitions correctly. This does apply to the filenames
47 only, not to the file contents. You can include several codepages;
48 say Y here if you want to include the DOS codepage that is used in
56 in so-called DOS codepages. You need to include the appropriate
57 codepage if you want to be able to read/write these filenames on
58 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
|
| /linux-4.4.14/arch/arm64/kernel/ |
| D | io.c | 26 void __memcpy_fromio(void *to, const volatile void __iomem *from, size_t count) in __memcpy_fromio() argument
29 !IS_ALIGNED((unsigned long)to, 8))) { in __memcpy_fromio()
30 *(u8 *)to = __raw_readb(from); in __memcpy_fromio()
32 to++; in __memcpy_fromio()
37 *(u64 *)to = __raw_readq(from); in __memcpy_fromio()
39 to += 8; in __memcpy_fromio()
44 *(u8 *)to = __raw_readb(from); in __memcpy_fromio()
46 to++; in __memcpy_fromio()
55 void __memcpy_toio(volatile void __iomem *to, const void *from, size_t count) in __memcpy_toio() argument
57 while (count && (!IS_ALIGNED((unsigned long)to, 8) || in __memcpy_toio()
[all …]
|
| /linux-4.4.14/arch/sh/kernel/ |
| D | io.c | 19 void memcpy_fromio(void *to, const volatile void __iomem *from, unsigned long count) in memcpy_fromio() argument
27 (((u32)to & 0x1f) == 0) && (((u32)from & 0x3) == 0)) { in memcpy_fromio()
53 : "=&r" (to), "=&r" (count), in memcpy_fromio()
56 : "7"(from), "0" (to), "1" (count) in memcpy_fromio()
61 if ((((u32)to | (u32)from) & 0x3) == 0) { in memcpy_fromio()
63 *(u32 *)to = *(volatile u32 *)from; in memcpy_fromio()
64 to += 4; in memcpy_fromio()
70 *(u8 *)to = *(volatile u8 *)from; in memcpy_fromio()
71 to++; in memcpy_fromio()
82 void memcpy_toio(volatile void __iomem *to, const void *from, unsigned long count) in memcpy_toio() argument
[all …]
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | kstrdup.cocci | 17 expression from,to;
22 - to = kmalloc(strlen(from) + 1,flag);
23 + to = kstrdup(from, flag);
24 ... when != \(from = E1 \| to = E1 \)
25 if (to==NULL || ...) S
26 ... when != \(from = E2 \| to = E2 \)
27 - strcpy(to, from);
30 expression x,from,to;
37 - to = \(kmalloc\|kzalloc\)(x,flag);
38 + to = kstrdup(from, flag);
[all …]
|
| D | memdup.cocci | 17 expression from,to;
22 to = \(kmalloc@p\|kzalloc@p\)(strlen(from) + 1,flag);
25 expression x,from,to;
32 to = \(kmalloc@p\|kzalloc@p\)(x,flag);
35 expression from,to,size,flag;
40 - to = \(kmalloc@p\|kzalloc@p\)(size,flag);
41 + to = kmemdup(from,size,flag);
42 if (to==NULL || ...) S
43 - memcpy(to, from, size);
46 expression from,to,size,flag;
[all …]
|
| D | memdup_user.cocci | 2 /// This is a little bit restricted to reduce false positives
18 expression from,to,size,flag;
22 - to = \(kmalloc\|kzalloc\)(size,flag);
23 + to = memdup_user(from,size);
25 - to==NULL
26 + IS_ERR(to)
30 + PTR_ERR(to)
33 - if (copy_from_user(to, from, size) != 0) {
40 expression from,to,size,flag;
45 * to = \(kmalloc@p\|kzalloc@p\)(size,flag);
[all …]
|
| /linux-4.4.14/arch/mn10300/include/asm/ |
| D | uaccess.h | 295 #define __copy_user(to, from, size) \ argument
298 void *__to = to; \
323 #define __copy_user_zeroing(to, from, size) \ argument
326 void *__to = to; \
363 unsigned long __generic_copy_from_user_nocheck(void *to, const void *from, in __generic_copy_from_user_nocheck() argument
366 __copy_user_zeroing(to, from, n); in __generic_copy_from_user_nocheck()
371 unsigned long __generic_copy_to_user_nocheck(void *to, const void *from, in __generic_copy_to_user_nocheck() argument
374 __copy_user(to, from, n); in __generic_copy_to_user_nocheck()
382 #define __constant_copy_user(to, from, size) \
400 : "d"(size), "d"(to), "d"(from) \
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.txt | 4 IO domain voltages on some Rockchip SoCs are variable but need to be
9 - If the regulator hooked up to a pin like SDMMC0_VDD is 3.3V then
10 bit 7 of GRF_IO_VSEL needs to be 0. If the regulator hooked up to
11 that same pin is 1.8V then bit 7 of GRF_IO_VSEL needs to be 1.
15 hooked up to the pins.
18 - any logic for deciding what voltage we should set regulators to
38 - rockchip,grf: phandle to the syscon managing the "general register files"
43 to report their voltage. The IO Voltage Domain for any non-specified
47 - ap0-supply: The supply connected to AP0_VCC.
48 - ap1-supply: The supply connected to AP1_VCC.
[all …]
|
| /linux-4.4.14/arch/m68k/lib/ |
| D | memcpy.c | 10 void *memcpy(void *to, const void *from, size_t n) in memcpy() argument
12 void *xto = to; in memcpy()
17 if ((long)to & 1) { in memcpy()
18 char *cto = to; in memcpy()
21 to = cto; in memcpy()
27 char *cto = to; in memcpy()
34 if (n > 2 && (long)to & 2) { in memcpy()
35 short *sto = to; in memcpy()
38 to = sto; in memcpy()
44 long *lto = to; in memcpy()
[all …]
|
| /linux-4.4.14/drivers/net/fddi/skfp/ |
| D | pmf.c | 560 char *to ; in smt_add_para() local
583 to = (char *) (pcon->pc_p) ; /* destination pointer */ in smt_add_para()
586 pa = (struct smt_para *) to ; /* type/length pointer */ in smt_add_para()
587 to += PARA_LEN ; /* skip smt_para */ in smt_add_para()
596 to[0] = 0 ; in smt_add_para()
597 to[1] = 0 ; in smt_add_para()
598 to[2] = 0 ; in smt_add_para()
599 to[3] = index ; in smt_add_para()
601 to += 4 ; in smt_add_para()
676 *(u32 *)to = 0 ; in smt_add_para()
[all …]
|
| /linux-4.4.14/Documentation/networking/ |
| D | operstates.txt | 6 <dev> up or down" and reflects whether the administrator wants to use
10 - ethernet requires to be plugged into the switch and, depending on
12 to be performed before user data can be transferred. Operational state
13 shows the ability of an interface to transmit this user data.
15 Thanks to 802.1X, userspace must be granted the possibility to
25 operation RTM_GETLINK. It is also possible to subscribe to RTMGRP_LINK
26 to be notified of updates. This is important for setting from userspace.
35 flag to determine whether they should use the interface.
53 Interface is unable to transfer data on L1, f.e. ethernet is not
62 protocol to establish. (802.1X)
[all …]
|
| D | ppp_generic.txt | 12 * the interface to the networking code
15 * the interface to pppd, via a /dev/ppp character device
23 mechanism for transporting PPP frames from one machine to another. A
26 to be able to send PPP frames, receive PPP frames, and optionally
31 This architecture makes it possible to implement PPP multilink in a
32 natural and straightforward way, by allowing more than one channel to
33 be linked to each ppp network interface unit. The generic layer is
42 functions used to communicate between the generic PPP layer and PPP
45 Each channel has to provide two functions to the generic PPP layer,
48 * start_xmit() is called by the generic layer when it has a frame to
[all …]
|
| D | rds.txt | 5 This readme tries to provide some background on the hows and whys of RDS,
16 applications to use a single socket to talk to any other process in the
18 to N*N if you use a connection-oriented socket transport like TCP.
20 RDS is not Infiniband-specific; it was designed to support different
21 transports. The current implementation used to support RDS over TCP as well
22 as IB. Work is in progress to support RDS over iWARP, and using DCE to
23 guarantee no dropped packets on Ethernet, it may be possible to use RDS over
29 RDS uses IPv4 addresses and 16bit port numbers to identify
35 transport has to be IP-based. In fact, RDS over IB uses a
36 reliable IB connection; the IP address is used exclusively to
[all …]
|
| D | ipddp.txt | 9 AppleTalk-IP (IPDDP) is the method computers connected to AppleTalk
10 networks can use to communicate via IP. AppleTalk-IP is simply IP datagrams
13 Through this driver you can either allow your Linux box to communicate
26 AppleTalk-IP decapsulation needs to be compiled into your kernel. You
27 will need to turn on AppleTalk-IP driver support. Then you will need to
28 select ONE of the two options; IP to AppleTalk-IP encapsulation support or
29 AppleTalk-IP to IP decapsulation support. If you compile the driver
30 statically you will only be able to use the driver for the function you have
32 select what mode you want it to run in via a module loading param.
34 AppleTalk-IP to IP decapsulation.
[all …]
|
| D | netlink_mmap.txt | 1 This file documents how to use memory mapped I/O with netlink.
8 Memory mapped netlink I/O can be used to increase throughput and decrease
17 The RX ring is used by the kernel to directly construct netlink messages into
20 syscalls have to be issued by user-space to get more message.
22 The TX ring is used to process messages directly from user-space memory, the
29 In order to use memory mapped netlink I/O, user-space needs three main changes:
32 - conversion of the RX path to get messages from the ring instead of recvmsg()
33 - conversion of the TX path to construct messages into the ring
35 Ring setup is done using setsockopt() to provide the ring parameters to the
36 kernel, then a call to mmap() to map the ring into the processes address space:
[all …]
|
| D | phy.txt | 9 to a MAC layer, which communicates with the physical connection through a
12 cable), and provides a register interface to allow drivers to determine what
13 settings were chosen, and to configure what settings are allowed.
15 While these devices are distinct from the network devices, and conform to a
16 standard layout for the registers, it has been common practice to integrate
19 sometimes quite different) ethernet controllers connected to the same
20 management bus, it is difficult to ensure safe use of the bus.
30 Basically, this layer is meant to provide an interface to PHY devices which
31 allows network driver writers to write as little code as possible, while
36 Most network devices are connected to a PHY by means of a management bus.
[all …]
|
| D | xfrm_sync.txt | 6 The end goal for syncing is to be able to insert attributes + generate
7 events so that the an SA can be safely moved from one machine to another
9 The idea is to synchronize the SA so that the takeover machine can do
10 the processing of the SA as accurate as possible if it has access to it.
12 We already have the ability to generate SA add/del/upd events.
13 These patches add ability to sync and have accurate lifetime byte (to
14 ensure proper decay of SAs) and replay counters to avoid replay attacks
19 it is possible for a lot of the events to be generated.
20 For this reason, we also add a nagle-like algorithm to restrict
21 the events. i.e we are going to set thresholds to say "let me
[all …]
|
| D | decnet.txt | 13 Be sure to turn on the following options:
16 CONFIG_PROC_FS (to see what's going on)
19 if you want to try out router support (not properly debugged yet)
22 CONFIG_DECNET_ROUTER (to be able to add/delete routes)
28 that you need it, in general you won't and it can cause ifconfig to
32 want to configure an endnode, then the simplified procedure is as follows:
39 to set the MAC address, see the next section. Also all configurations which
47 which is that its added to the addresses on the loopback device.
50 were added to the loopback device. In 2.5, any local interface address
51 can be used to loop back to the local machine. Of course this does not
[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.
11 While the driver will attempt to autoprobe the I/O port address, IRQ
13 this reason, you should be prepared to supply these parameters
14 yourself. (see "Card Configuration" below for how to determine or
18 as the following to your /etc/lilo.conf:
24 the driver will try to determine them itself.
34 need to add a line such as:
38 The address is unimportant - however, the card needs to be configured
42 attached to a network that includes AppleTalk routers or not. If,
[all …]
|
| D | e100.txt | 24 For questions related to hardware requirements, refer to the documentation
39 For more information on how to identify your adapter, go to the Adapter &
44 For the latest Intel network drivers for Linux, refer to the following
46 networking link on the left to search for your adapter:
57 structure that describes a receive buffer and its attributes to the network
58 controller. The data in the descriptor is used by the controller to write
59 data from the controller to host memory. In the 3.x.x driver the valid range
66 structure that describes a transmit buffer and its attributes to the network
67 controller. The data in the descriptor is used by the controller to read
68 data from the host memory to the controller. In the 3.x.x driver the valid
[all …]
|
| D | rxrpc.txt | 6 that can be used to perform RxRPC remote operations. This is done over sockets
7 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
40 layer which renders structured data to binary blobs and back again using XDR
64 to speed up subsequent calls.
66 (4) A secure protocol, using the Linux kernel's key retention facility to
71 left to the application. AF_RXRPC only deals in blobs. Even the operation ID
81 to use - currently only PF_INET is supported.
95 currently), and uses this to provide network transport. UDP ports, for
99 endpoint, thus allowing the endpoints to be shared, even to the same
102 (*) Each connection goes to a particular "service". A connection may not go
[all …]
|
| /linux-4.4.14/arch/alpha/kernel/ |
| D | io.c | 420 void memcpy_fromio(void *to, const volatile void __iomem *from, long count) in memcpy_fromio() argument
425 if (count >= 8 && ((u64)to & 7) == ((u64)from & 7)) { in memcpy_fromio()
428 *(u64 *)to = __raw_readq(from); in memcpy_fromio()
430 to += 8; in memcpy_fromio()
436 if (count >= 4 && ((u64)to & 3) == ((u64)from & 3)) { in memcpy_fromio()
439 *(u32 *)to = __raw_readl(from); in memcpy_fromio()
441 to += 4; in memcpy_fromio()
447 if (count >= 2 && ((u64)to & 1) == ((u64)from & 1)) { in memcpy_fromio()
450 *(u16 *)to = __raw_readw(from); in memcpy_fromio()
452 to += 2; in memcpy_fromio()
[all …]
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.char | 7 console driver which dumps all printk messages to stderr.
12 The User-Mode Linux environment allows you to create virtual serial
13 lines on the UML that are usually made to show up on the host as
17 information and command line examples of how to use this facility.
25 lines to a device similar to /dev/null. Data written to it disappears
26 and there is never any data to be read.
32 lines to host portals. They may be accessed with 'telnet <host>
34 attached to a single portal, although what UML device you get when
35 you telnet to that portal will be unpredictable.
36 It is safe to say 'Y' here.
[all …]
|
| D | Kconfig.net | 9 While the User-Mode port cannot directly talk to any physical
12 kernels can talk to each other, the host, and with the host's help,
19 If you'd like to be able to enable networking in the User-Mode
21 enable at least one of the following transport options to actually
29 running UML to exchange packets with its host over one of the
33 Ethernet network, it's in fact communicating over a point-to-point
42 has examples of the UML command line to use to enable Ethertap
45 If you'd like to set up an IP network with the host and/or the
46 outside world, say Y to this, the Daemon Transport and/or the
55 The UML TUN/TAP network transport allows a UML instance to exchange
[all …]
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | configfs-spear-pcie-gadget | 7 Interface is used to configure selected dual mode PCIe controller
8 as device and then program its various registers to configure it
10 This interfaces can be used to show spear's PCIe device capability.
18 link ... used to enable ltssm and read its status.
19 int_type ...used to configure and read type of supported
21 no_of_msi ... used to configure number of MSI vector needed and
22 to read no of MSI granted.
23 inta ... write 1 to assert INTA and 0 to de-assert.
24 send_msi ... write MSI vector to be sent.
25 vendor_id ... used to write and read vendor id (hex)
[all …]
|
| D | sysfs-devices-power | 6 allowing the user space to check and modify some power
14 space to check if the device is enabled to wake up the system
15 from sleep states, such as the memory sleep state (suspend to
16 RAM) and hibernation (suspend to disk), and to enable or disable
17 it to do that as desired.
20 used to activate the system from a sleep state. Such devices
24 + "enabled\n" to issue the events;
25 + "disabled\n" not to do so;
29 "disabled" to it.
33 be enabled to wake up the system from sleep states.
[all …]
|
| D | sysfs-bus-pci-drivers-ehci_hcd | 11 to the EHCI controller; when a full- or low-speed device
12 is plugged in, the connection is routed to the companion
15 Sometimes you want to force a high-speed device to connect
17 connection to be routed to the companion controller.
18 That's what this file does. Writing a port number to the
19 file causes connections on that port to be routed to the
21 number returns the port to normal operation.
23 For example: To force the high-speed device attached to
24 port 4 on bus 2 to run at full speed:
28 To return the port to high-speed operation:
[all …]
|
| D | sysfs-power | 6 provide a unified interface to the power management
20 states from the deepest ("mem", always present) to the
26 "mem" - "suspend-to-RAM", present if supported.
28 "freeze" - "suspend-to-idle", always present.
30 Writing to this file one of these strings causes the system to
33 "suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean.
40 suspend-to-disk mechanism. Reading from this file returns
41 the name of the method by which the system will be put to
43 'firmware' - means that the memory image will be saved to disk
47 the system will be put to sleep by the platform driver (e.g.
[all …]
|
| D | sysfs-firmware-gsmi | 7 triggers. Some of the callbacks are similar to those
8 provided by the EFI runtime services page, but due to
14 is limited to handling the system event log and getting
15 access to EFI-style variables stored in nvram.
24 for more information on how to interact with
30 the firmware to be timestamped and appended to
33 platform to platform. The only kernel-enforced
40 Writing any value to this file will cause the
41 entire firmware configuration to be reset to
43 a reboot is required for the configuration to be
[all …]
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 4 The leds timer trigger does not currently have an interface to activate
6 specifying how long a state to be on, and the second for how long the state
7 to be off. The delay_on value specifies the time period an LED should stay
10 gets deactivated. There is no provision for one time activation to implement
11 features that require an on or off state to be held just once and then stay in
14 Without one shot timer interface, user space can still use timer trigger to
15 set a timer to hold a state, however when user space application crashes or
21 PMIC. There is a need to activate one shot timer to control the vibrate
22 feature, to prevent user space crashes leaving the phone in vibrate mode
23 permanently causing the battery to drain.
[all …]
|
| /linux-4.4.14/arch/tile/kernel/ |
| D | compat_signal.c | 52 int copy_siginfo_to_user32(struct compat_siginfo __user *to, const siginfo_t *from) in copy_siginfo_to_user32() argument
56 if (!access_ok(VERIFY_WRITE, to, sizeof(struct compat_siginfo))) in copy_siginfo_to_user32()
64 err = __put_user(from->si_signo, &to->si_signo); in copy_siginfo_to_user32()
65 err |= __put_user(from->si_errno, &to->si_errno); in copy_siginfo_to_user32()
66 err |= __put_user((short)from->si_code, &to->si_code); in copy_siginfo_to_user32()
69 err |= __put_user(from->si_pid, &to->si_pid); in copy_siginfo_to_user32()
70 err |= __put_user(from->si_uid, &to->si_uid); in copy_siginfo_to_user32()
71 err |= __put_user(from->si_int, &to->si_int); in copy_siginfo_to_user32()
78 &to->_sifields._pad[0]); in copy_siginfo_to_user32()
83 err |= __put_user(from->si_utime, &to->si_utime); in copy_siginfo_to_user32()
[all …]
|
| /linux-4.4.14/arch/parisc/kernel/ |
| D | signal32.c | 278 copy_siginfo_from_user32 (siginfo_t *to, compat_siginfo_t __user *from) in copy_siginfo_from_user32() argument
286 err = __get_user(to->si_signo, &from->si_signo); in copy_siginfo_from_user32()
287 err |= __get_user(to->si_errno, &from->si_errno); in copy_siginfo_from_user32()
288 err |= __get_user(to->si_code, &from->si_code); in copy_siginfo_from_user32()
290 if (to->si_code < 0) in copy_siginfo_from_user32()
291 err |= __copy_from_user(&to->_sifields._pad, &from->_sifields._pad, SI_PAD_SIZE); in copy_siginfo_from_user32()
293 switch (to->si_code >> 16) { in copy_siginfo_from_user32()
295 err |= __get_user(to->si_utime, &from->si_utime); in copy_siginfo_from_user32()
296 err |= __get_user(to->si_stime, &from->si_stime); in copy_siginfo_from_user32()
297 err |= __get_user(to->si_status, &from->si_status); in copy_siginfo_from_user32()
[all …]
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 7.AdvancedTopics | 4 works. There is still more to learn, however! This section will cover a
5 number of topics which can be helpful for developers wanting to become a
12 application. While BitKeeper was controversial, the approach to software
15 project. In current times, there are several free alternatives to
22 still being civilized by its developers. This document will not attempt to
23 teach the reader how to use git; that would be sufficient material for a
26 wish to come up to speed with git will find more information at:
34 The first order of business is to read the above sites and get a solid
35 understanding of how git works before trying to use it to make patches
36 available to others. A git-using developer should be able to obtain a copy
[all …]
|
| D | 3.Early-stage | 4 to jump right in and start coding. As with any significant project,
13 clear description of the problem to be solved. In some cases, this step is
15 example. In others, though, it is tempting to confuse the real problem
16 with the proposed solution, and that can lead to difficulties.
19 sought a way to run applications without dropouts or other artifacts caused
21 kernel module intended to hook into the Linux Security Module (LSM)
22 framework; this module could be configured to give specific applications
23 access to the realtime scheduler. This module was implemented and sent to
26 To the audio developers, this security module was sufficient to solve their
28 misuse of the LSM framework (which is not intended to confer privileges
[all …]
|
| D | 6.Followthrough | 6 developers can make is to conclude that their work is now done. In truth,
8 with, possibly, quite a bit of work yet to be done.
13 code. You, as the author of that code, will be expected to work with the
14 kernel community to ensure that your code is up to the kernel's quality
15 standards. A failure to participate in this process is quite likely to
28 value and why you went to the trouble of writing it. But that value
30 like to maintain a kernel with this code in it five or ten years later?
31 Many of the changes you may be asked to make - from coding style tweaks
32 to substantial rewrites - come from the understanding that Linux will
40 impulse to respond in kind. Code review is about the code, not about
[all …]
|
| /linux-4.4.14/Documentation/power/ |
| D | interface.txt | 4 The power management subsystem provides a unified sysfs interface to
10 returns what states are supported, which is hard-coded to 'freeze',
11 'standby' (Power-On Suspend), 'mem' (Suspend-to-RAM), and 'disk'
12 (Suspend-to-Disk).
14 Writing to this file one of those strings causes the system to
20 /sys/power/disk controls the operating mode of the suspend-to-disk
21 mechanism. Suspend-to-disk can be handled in several ways. We have a
22 few options for putting the system to sleep - using the platform driver
26 Additionally, /sys/power/disk can be used to turn on one of the two testing
27 modes of the suspend-to-disk mechanism: 'testproc' or 'test'. If the
[all …]
|
| D | suspend-and-interrupts.txt | 17 trigger and if any devices have not been suspended properly yet, it is better to
21 In some cases they would attempt to access, for example, memory address spaces
22 of suspended devices and cause unpredictable behavior to ensue as a result.
23 Unfortunately, such problems are very difficult to debug and the introduction
25 resume, was the only practical way to mitigate them.
28 of resuming devices (that is, before starting to execute ->resume_early
38 brought back online. That applies to timer interrupts in the first place,
39 but also to IPIs and to some other special-purpose interrupts.
41 The IRQF_NO_SUSPEND flag is used to indicate that to the IRQ subsystem when
42 requesting a special-purpose interrupt. It causes suspend_device_irqs() to
[all …]
|
| D | states.txt | 5 The kernel supports up to four system sleep states generically, although three
6 of them depend on the platform support code to implement the low-level details
9 The states are represented by strings that can be read or written to the
16 available non-hibernation sleep states from the deepest to the shallowest,
20 in /sys/power/state in addition to "mem". If the system supports three
22 addition to "mem" and "standby".
32 It allows more energy to be saved relative to runtime idle by freezing user
37 This state can be used for platforms without Power-On Suspend/Suspend-to-RAM
38 support, or it can be used in addition to Suspend-to-RAM (memory sleep)
39 to provide reduced resume latency. It is always supported.
[all …]
|
| D | swsusp-dmcrypt.txt | 4 How to use dm-crypt and swsusp together:
12 You know how to create or how to modify an initrd.
19 At this point you want to encrypt your swap, too. Still you want to
20 be able to suspend using swsusp. This, however, means that you
21 have to be able to either enter a passphrase or that you read
23 or an usb stick prior to resume. So you need an initrd, that sets
24 up dm-crypt and then asks swsusp to resume from the encrypted
28 a way that the swap device you suspend to/resume from has
30 within your running system. The easiest way to achieve this is
31 to always set up this swap device first with dmsetup, so that
[all …]
|
| D | swsusp.txt | 19 * (*) suspend/resume support is needed to make it safe.
27 You need to append resume=/dev/your_swap_partition to kernel command
36 . If you would like to write hibernation image to swap and then suspend
37 to RAM (provided your platform supports it), you can try
42 support. For suspend and resume to work, make sure your disk drivers
43 are built into kernel -- not modules. [There's way to make
47 If you want to limit the suspend image size to N bytes, do
51 before suspend (it is limited to 500 MB by default).
64 that this be done prior to remounting any filesystems (even as
72 Idea and goals to achieve
[all …]
|
| D | basic-pm-debugging.txt | 4 1. Testing hibernation (aka suspend to disk or STD)
6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
11 and the system should create a hibernation image, reboot, resume and get back to
13 hibernation is most likely to work correctly. Still, you need to repeat the
17 modes causes the PM core to skip some platform-related callbacks which on ACPI
18 systems might be necessary to make hibernation work. Thus, if your machine fails
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
33 (it is similar to the "reboot" mode, but it requires you to press the power
34 button to make the system resume).
36 If neither "platform" nor "shutdown" hibernation mode works, you will need to
[all …]
|
| D | pci.txt | 5 An overview of concepts and the Linux kernel's interfaces related to PCI power
9 This document only covers the aspects of power management specific to PCI
10 devices. For general description of the kernel's interfaces related to device
11 power management refer to Documentation/power/devices.txt and
27 In general, power management is a feature allowing one to save energy by putting
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
34 state). This may happen when there are some data for the device to handle or
35 as a result of an external event requiring the device to be active, which may
41 approach, that is referred to as the native PCI power management (native PCI PM)
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | HOWTO | 5 instructions on how to become a Linux kernel developer and how to learn
6 to work with the Linux kernel development community. It tries to not
7 contain anything related to the technical aspects of kernel programming,
11 to the maintainer of this file, who is listed at the bottom of the
18 So, you want to learn how to become a Linux kernel developer? Or you
20 device." This document's goal is to teach you everything you need to
21 know to achieve this by describing the process you need to go through,
22 and hints on how to work with the community. It will also try to
28 you plan to do low-level development for that architecture. Though they
36 adheres to the ISO C89 standard, it uses a number of extensions that are
[all …]
|
| D | futex-requeue-pi.txt | 4 Requeueing of tasks from a non-PI futex to a PI futex requires
5 special handling in order to ensure the underlying rt_mutex is never
8 brevity, this action will be referred to as "requeue_pi" throughout
16 pthread_cond_broadcast() must resort to waking all the tasks waiting
17 on a pthread_condvar and letting them try to sort out which task
18 gets to run first in classic thundering-herd formation. An ideal
20 rest to the natural wakeup inherent in unlocking the mutex
47 has waiters. Note that pthread_cond_wait() attempts to lock the
48 mutex only after it has returned to user space. This will leave the
52 In order to support PI-aware pthread_condvar's, the kernel needs to
[all …]
|
| D | unaligned-memory-access.txt | 5 when it comes to memory access. This document presents some details about
6 unaligned accesses, why you need to write code that doesn't cause them,
7 and how to write such code!
13 Unaligned memory accesses occur when you try to read N bytes of data starting
21 or write a number of bytes to or from memory (e.g. movb, movw, movl in x86
22 assembly). As will become clear, it is relatively easy to spot C statements
23 which will compile to multiple-byte memory access instructions, namely when
30 The rule mentioned above forms what we refer to as natural alignment:
40 to achieve full portability.
47 to architecture. It would be easy to write a whole document on the differences
[all …]
|
| D | dma-buf-sharing.txt | 8 This document serves as a guide to device-driver writers on what is the dma-buf
9 buffer sharing API, how to use it for exporting and using shared buffers.
11 Any device driver which wishes to be a part of DMA buffer sharing, can do so as
14 Say a driver A wants to use buffers created by driver B, then we call B as the
19 - allows other users to share the buffer by using dma_buf sharing APIs,
27 - doesn't need to worry about how the buffer is allocated, or where.
28 - needs a mechanism to get access to the scatterlist that makes up this buffer
37 1. Exporter announces that it wishes to export a buffer
39 passes it around to potential buffer-users based on use case
40 3. Each buffer-user 'connects' itself to the buffer
[all …]
|
| D | applying-patches.txt | 9 A frequently asked question on the Linux Kernel Mailing List is how to apply
10 a patch to the kernel or, more specifically, what base kernel a patch for
11 one of the many trees/branches should be applied to. Hopefully this document
12 will explain this to you.
14 In addition to explaining how to apply and revert patches, a brief
15 description of the different kernel trees (and examples of how to apply
24 To correctly apply a patch you need to know what base it was generated from
26 should both be present in the patch file metadata or be possible to deduce
33 (or patch) file and makes the changes to the source tree described in it.
35 Patches for the Linux kernel are generated relative to the parent directory
[all …]
|
| D | DMA-attributes.txt | 11 to a memory region with the DMA_ATTR_WRITE_BARRIER attribute forces
12 all pending DMA writes to complete, and thus provides a mechanism to
14 bridges. This barrier is not specific to a particular type of
15 interconnect, it applies to the system as a whole, and so its
17 the way from the DMA device to memory.
20 useful, suppose that a device does a DMA write to indicate that data is
28 DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
31 Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
38 DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
39 buffered to improve performance.
[all …]
|
| D | kobject.txt | 1 Everything you never wanted to know about kobjects, ksets, and ktypes
14 all of which make reference to each other. In an attempt to make things
21 objects to be arranged into hierarchies), a specific type, and,
29 If it does, the reference counting for the object is sure to be messed
34 what happens to the kobject when it is created and destroyed.
37 or belong to different ktypes. The kset is the basic container type for
43 of those directories corresponds to a kobject in the same kset.
45 We'll look at how to create and manipulate all of these types. A bottom-up
46 approach will be taken, so we'll go back to kobjects.
51 It is rare for kernel code to create a standalone kobject, with one major
[all …]
|
| D | svga.txt | 9 to usage of the BIOS, the selection is limited to boot time (before the
13 ** enter `scan' on the video mode prompt, pick the mode you want to use,
15 ** set the vga parameter to this number (converted to decimal first).
17 The video mode to be used is selected by a kernel parameter which can be
29 0..35 - Menu item number (when you have used the menu to view the list of
31 to use). 0..9 correspond to "0".."9", 10..35 to "a".."z". Warning: the
34 better to use absolute mode numbers instead.
38 hexadecimal numbers -- you have to convert it to decimal manually.
42 The ASK_VGA mode causes the kernel to offer a video mode menu upon
43 bootup. It displays a "Press <RETURN> to see video modes available, <SPACE>
[all …]
|
| D | SubmittingPatches | 2 How to Get Your Change Into the Linux Kernel
8 For a person or company who wishes to submit a change to the Linux
16 Documentation/SubmitChecklist for a list of items to check before
22 control system; if you use git to prepare your patches, you'll find much
23 of the mechanical work done for you, though you'll still need to prepare
36 git to obtain one. You'll want to start with the mainline repository,
41 Note, however, that you may not want to develop against the mainline tree
42 directly. Most subsystem maintainers run their own trees and want to see
44 in the MAINTAINERS file to find that tree, or simply ask the maintainer if
47 It is still possible to download kernel releases via tarballs (as described
[all …]
|
| D | dcdbas.txt | 4 systems management software such as Dell OpenManage to perform system
11 is expected to make use of this driver, and it may include the use of this
14 The Dell libsmbios project aims towards providing access to as much BIOS
25 the SMI and provides a way for the application to generate the SMI.
27 software to perform these system management interrupts:
34 Systems management software must perform the following steps to execute
38 2) Write system management command to smi_data.
39 3) Write "1" to smi_request to generate a calling interface SMI or
40 "2" to generate a raw SMI.
48 to perform a power cycle or power off of the system after the OS has finished
[all …]
|
| D | ManagementStyle | 5 on who you ask) management style for the linux kernel. It's meant to
6 mirror the CodingStyle document to some degree, and mainly written to
9 Management style is very personal and much harder to quantify than
11 to do with reality. It started as a lark, but that doesn't mean that it
12 might not actually be true. You'll have to decide for yourself.
18 These suggestions may or may not apply to you.
24 making it painfully obvious to the questioner that we don't have a clue
25 to what the answer is.
34 manager must be to make it. That's very deep and obvious, but it's not
37 The name of the game is to _avoid_ having to make a decision. In
[all …]
|
| D | bcache.txt | 10 in erase block sized buckets, and it uses a hybrid btree/log to track cached
11 extants (which can be anywhere from a single sector to the bucket size). It's
12 designed to avoid random writes at all costs; it fills up an erase block
15 Both writethrough and writeback caching are supported. Writeback defaults to
16 off, but can be switched on and off arbitrarily at runtime. Bcache goes to
17 great lengths to protect your data - it reliably handles unclean shutdown. (It
22 dirty data to the backing device is always done sequentially, scanning from the
23 start to the end of the index.
26 to caching large sequential IO. Bcache detects sequential IO and skips it;
32 In the event of a data IO error on the flash it will try to recover by reading
[all …]
|
| D | kernel-per-CPU-kthreads.txt | 4 options to control their OS jitter. Note that non-per-CPU kthreads are
6 them to a "housekeeping" CPU dedicated to such work.
11 o Documentation/IRQ-affinity.txt: Binding interrupts to sets of CPUs.
13 o Documentation/cgroups: Using cgroups to bind tasks to sets of CPUs.
15 o man taskset: Using the taskset command to bind tasks to sets
19 call to bind tasks to sets of CPUs.
22 writing "0" to offline and "1" to online.
24 o In order to locate kernel-generated OS jitter on CPU N:
52 1. Use irq affinity to force the irq threads to execute on
60 2. Use irq affinity to force Bluetooth-related interrupts to
[all …]
|
| D | lockup-watchdogs.txt | 5 The Linux kernel can act as a watchdog to detect both soft and hard
8 A 'softlockup' is defined as a bug that causes the kernel to loop in
10 details), without giving other tasks a chance to run. The current
12 will stay locked up. Alternatively, the kernel can be configured to
18 A 'hardlockup' is defined as a bug that causes the CPU to loop in
20 details), without letting other interrupts have a chance to run.
21 Similarly to the softlockup case, the current stack trace is displayed
30 to cause the system to reboot automatically after a specified amount
40 A periodic hrtimer runs to generate interrupts and kick the watchdog
42 (compile-time initialized to 10 and configurable through sysctl of the
[all …]
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | hwmon-kernel-api.txt | 10 drivers that want to use the hardware monitoring framework.
14 to communicate with a hardware monitoring device. If you want to know this
17 For additional guidelines on how to write and improve hwmon drivers, please
41 of this function is a pointer to the parent device.
42 This function returns a pointer to the newly created hardware monitoring device
44 monitoring sysfs attributes are expected to have been created and attached to
45 the parent device prior to calling hwmon_device_register. A name attribute must
48 hwmon_device_register_with_groups is similar to hwmon_device_register. However,
49 it has additional parameters. The name parameter is a pointer to the hwmon
51 pointing to this name. The drvdata parameter is the pointer to the local
[all …]
|
| D | sht15 | 41 chip. These coefficients are used to internally calibrate the signals from the
49 * The regulator supply name is set to "vcc".
51 status register to its hardware default value, but the driver will try to
58 set it to true to enable CRC validation of the readings (default to false).
60 flag to indicate not to reload from OTP (default to false).
62 flag to indicate the temp/humidity resolution to use (default to false).
69 * heater_enable: write 1 in this attribute to enable the on-chip heater,
70 0 to disable it. Be careful not to enable the heater
|
| /linux-4.4.14/arch/score/include/asm/ |
| D | uaccess.h | 296 extern int __copy_tofrom_user(void *to, const void *from, unsigned long len);
299 copy_from_user(void *to, const void *from, unsigned long len) in copy_from_user() argument
304 return __copy_tofrom_user(to, from, len); in copy_from_user()
308 return __copy_tofrom_user(to, from, len - over) + over; in copy_from_user()
314 copy_to_user(void *to, const void *from, unsigned long len) in copy_to_user() argument
318 if (access_ok(VERIFY_WRITE, to, len)) in copy_to_user()
319 return __copy_tofrom_user(to, from, len); in copy_to_user()
321 if ((unsigned long)to < TASK_SIZE) { in copy_to_user()
322 over = (unsigned long)to + len - TASK_SIZE; in copy_to_user()
323 return __copy_tofrom_user(to, from, len - over) + over; in copy_to_user()
[all …]
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.lpfc | 5 Changes from 20050323 to 20050413
7 * Changed version number to 8.0.28
10 * Removed pci dma sync calls to coherent/consistent pci memory.
13 * Removed sysfs attributes that are used to dump the various
17 to luns on nodes in NPR or other relevant states (PLOGI,
23 * Removed extraneous calls to lpfc_sli_next_iotag which should
29 if we timed out waiting for command to complete after abort was
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
45 driver has already returned the command to the midlayer.
47 Changes from 20050308 to 20050323
[all …]
|
| D | ChangeLog.megaraid_sas | 12 4. Add missing initial call to megasas_get_ld_vf_affiliation().
23 2. Fix megasas_ioc_init_fusion to use local stack variable.
24 3. Return leaked MPT frames to MPT command pool.
47 3. Update balance count in driver to be in sync of firmware.
51 7. Add support to display Customer branding details in syslog.
52 8. Set IoFlags to enable Fast Path for JBODs for Invader/Fury(12 Gb/s)
57 11.Add support to differentiate between iMR and MR Firmware.
106 2. Mask off flags in ioctl path to prevent memory scribble with older
116 2. Increase default cmds per lun to 256.
130 1. Fix FastPath I/O to work with degraded RAID 1.
[all …]
|
| D | tmscsim.txt | 25 It has originally written by C.L. Huang from the Tekram corp. to support the
27 scsi = SCSI driver, m = AMD (?) as opposed to w for the DC390W/U/F
34 general AM53C974 based adapters and some possibilities to configure it were
45 The numbering scheme isn't consistent. The first versions went from 1.00 to
46 1.12, then 1.20a to 1.20t. Finally I decided to use the ncr53c8xx scheme. So
47 the next revisions will be 2.0a to 2.0X (stable), 2.1a to 2.1X (experimental),
48 2.2a to 2.2X (stable, again) etc. (X = anything between a and z.) If I send
49 fixes to people for testing, I create intermediate versions with a digit
56 linux/drivers/scsi, you basically have to do nothing special to use this
57 driver. Of course you have to choose to compile SCSI support and DC390(T)
[all …]
|
| /linux-4.4.14/Documentation/frv/ |
| D | gdbstub.txt | 7 port. This permits GDB to single step through the kernel, set breakpoints and
9 permits the NMI interrupt button or serial port events to jump the kernel into
19 PDK there is no externally accessible serial port and the serial port to
32 and copy the configuration that you wish to use to .config. Then reconfigure
37 Set this to "Y". This causes all C and Assembly files to be compiled
38 to include debugging information.
42 Set this to "Y". This causes the GDB stub to be compiled into the
47 Set this to "Y" if you want the GDB stub to activate as soon as possible
48 and wait for GDB to connect. This allows you to start tracing right from
53 Set this to "Y" if you wish to be able to use "console=gdb0" on the
[all …]
|
| D | atomic-ops.txt | 6 instruction. Unfortunately, this alone can't be used to implement the following operations:
8 (*) Atomic add to memory
16 On such CPUs, the standard way of emulating such operations in uniprocessor mode is to disable
17 interrupts, but on the FR-V CPUs, modifying the PSR takes a lot of clock cycles, and it has to be
26 To get around this, the following algorithm has been implemented. It operates in a way similar to
29 (*) The CCCR.CC3 register is reserved within the kernel to act as an atomic modify abort flag.
31 (*) In the exception prologues run on kernel->kernel entry, CCCR.CC3 is set to 0 (Undefined
36 (1) Set ICC3.Z to true and set CC3 to True (ORCC/CKEQ/ORCR).
38 (2) Load the value currently in the memory to be modified into a register.
40 (3) Make changes to the value.
[all …]
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 4 Introduction to Re-logging in XFS
9 logged are made up of the changes to in-core structures rather than on-disk
11 logged. The reason for these differences is to reduce the amount of log space
18 modifications to a single object to be carried in the log at any given time.
19 This allows the log to avoid needing to flush each change to disk before
20 recording a new change to the object. XFS does this via a method called
22 new change to the object is recorded with a *new copy* of all the existing
23 changes in the new transaction that is written to the log.
25 That is, if we have a sequence of changes A through to F, and the object was
26 written to disk after change D, we would see in the log the following series
[all …]
|
| D | vfs.txt | 19 interface to userspace programs. It also provides an abstraction
20 within the kernel which allows different filesystem implementations to
32 calls. The pathname argument that is passed to them is used by the VFS
33 to search through the directory entry cache (also known as the dentry
34 cache or dcache). This provides a very fast look-up mechanism to
36 in RAM and are never saved to disc: they exist only for performance.
38 The dentry cache is meant to be a view into your entire filespace. As
40 some bits of the cache are missing. In order to resolve your pathname
41 into a dentry, the VFS may have to resort to creating dentries along
49 An individual dentry usually has a pointer to an inode. Inodes are
[all …]
|
| D | autofs4-mount-control.txt | 8 There is a problem with active restarts in autofs (that is to say
12 directory that is being managed in order to be able to issue control
13 operations. Using a file descriptor gives ioctl operations access to
18 mount itself which prevents us being able to use open(2) to obtain a
21 Currently autofs uses "umount -l" (lazy umount) to clear active mounts
23 needs to walk back up the mount tree to construct a path, such as
28 The actual problem with autofs is that it can't reconnect to existing
29 mounts. Immediately one thinks of just adding the ability to remount
67 use the follow_link inode operation to trigger the mount.
92 to mount and umount all of the offsets as a single unit. Not really a
[all …]
|
| D | gfs2.txt | 6 GFS is a cluster file system. It allows a cluster of computers to
8 iSCSI, NBD, etc). GFS reads and writes to the block device like a local
9 file system, but also uses a lock module to allow the computers coordinate
11 features of GFS is perfect consistency -- changes made to the file system
17 lock_nolock -- allows gfs to be used as a local file system
31 If you are using Fedora, you need to install the gfs2-utils package
32 and, for lock_dlm, you will also need to install the cman package
40 fsck.gfs2 to repair a filesystem
41 gfs2_grow to expand a filesystem online
42 gfs2_jadd to add journals to a filesystem online
[all …]
|
| /linux-4.4.14/Documentation/isdn/ |
| D | INTERFACE | 11 register_isdn() with a pointer to that struct. Prior to that, it has
12 to preset some of the fields of isdn_if. The LL sets the rest of
19 made to the interface. Before it went into kernel, the package
37 the version number. If that number starts with 0, it refers to the old,
39 above, it refers to the revision of the corresponding module.
40 ***CHANGEIx refers to the revision number of the isdnif.h
46 This field has to be set by the HL-driver to the number of channels
47 supported prior to calling register_isdn(). Upon return of the call,
48 the LL puts an id there, which has to be used by the HL-driver when
55 Also to be preset by the HL-driver. With this value the HL-driver
[all …]
|
| D | README.sc | 1 Welcome to Beta Release 2 of the combination ISDN driver for SpellCaster's
4 guaranteed to fail. If you have a DataCommute/PRI installed in the test
6 be usable. To see what we have done to Beta Release 2, see section 3.
12 our own option and without warranty. If you choose to assume all and
13 total risk by using this driver, we encourage you to join the beta
16 To join the Linux beta mailing list, send a message to:
18 contents of the message. Do not include a signature. If you choose to
19 remove yourself from this list at a later date, send another message to
28 1.3 How do I setup my system with the correct software to use
36 2.5 What to do if it doesn't load
[all …]
|
| D | INTERFACE.CAPI | 1 Kernel CAPI Interface to Hardware Drivers
8 to access ISDN equipment connected to basic rate interfaces (BRI) and primary
13 lingo) with Kernel CAPI to indicate their readiness to provide their service
14 to CAPI applications. CAPI applications also register with Kernel CAPI,
16 application registration to an available device, forwarding it to the
27 Kernel CAPI function register_capi_driver() with a pointer to a struct
29 driver, and optionally a pointer to a callback function, add_card(). The
31 with a pointer to the same struct capi_driver.
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
39 detach_capi_ctr() with a pointer to the same struct capi_ctr.
[all …]
|
| /linux-4.4.14/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 48 * 01-09-01 01.01.03 Added more definitions to the system interface section
50 * 01-25-01 01.01.04 Changed MPI_VERSION_MINOR from 0x00 to 0x01.
58 * MPI_DOORBELL_USED, to better match the spec.
60 * Changed MPI_VERSION_MINOR from 0x01 to 0x02.
63 * 11-01-01 01.02.03 Changed name to MPI_FUNCTION_SCSI_ENCLOSURE_PROCESSOR.
107 * 06-06-00 01.00.01 Added CurReplyFrameSize field to _MSG_IOC_FACTS_REPLY.
112 * 06-30-00 01.00.03 Added MaxLanBuckets to _PORT_FACT_REPLY structure.
116 * _MSG_EVENT_ACK_REPLY structure to match specification.
118 * Added a value for Manufacturer to WhoInit
123 * Added ImageType to FwUpload reply.
[all …]
|
| /linux-4.4.14/include/asm-generic/ |
| D | uaccess.h | 79 static inline __must_check long __copy_from_user(void *to, in __copy_from_user() argument
85 *(u8 *)to = *(u8 __force *)from; in __copy_from_user()
88 *(u16 *)to = *(u16 __force *)from; in __copy_from_user()
91 *(u32 *)to = *(u32 __force *)from; in __copy_from_user()
95 *(u64 *)to = *(u64 __force *)from; in __copy_from_user()
103 memcpy(to, (const void __force *)from, n); in __copy_from_user()
109 static inline __must_check long __copy_to_user(void __user *to, in __copy_to_user() argument
115 *(u8 __force *)to = *(u8 *)from; in __copy_to_user()
118 *(u16 __force *)to = *(u16 *)from; in __copy_to_user()
121 *(u32 __force *)to = *(u32 *)from; in __copy_to_user()
[all …]
|
| /linux-4.4.14/drivers/net/slip/ |
| D | Kconfig | 9 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
10 connect to your Internet service provider or to connect to some
11 other local Unix box or if you want to configure your Linux box as a
12 Slip/CSlip server for other people to dial in. SLIP (Serial Line
13 Internet Protocol) is a protocol used to send Internet traffic over
18 Normally, your access provider has to support SLIP in order for you
19 to be able to use it, but there is now a SLIP emulator called SLiRP
22 allows you to use SLIP over a regular dial up shell connection. If
23 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
25 <http://www.tldp.org/docs.html#howto>, explains how to
[all …]
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | sh_mobile_ceu_camera.txt | 50 (1) to (1') - whole max width or height
51 (1) to (2) - sensor cropped left or top
52 (2) to (2') - sensor cropped width or height
53 (3) to (3') - sensor scale
54 (3) to (4) - CEU cropped left or top
55 (4) to (4') - CEU cropped width or height
56 (5) to (5') - reverse sensor scale applied to CEU cropped width or height
57 (2) to (5) - reverse sensor scale applied to CEU cropped left or top
58 (6) to (6') - CEU scale - user window
75 3. Calculate new combined scales from "effective" input window to requested user
[all …]
|
| D | uvcvideo.txt | 7 Questions and remarks can be sent to the Linux UVC development mailing list at
20 - through mappings of XU controls to V4L2 controls
23 The first one allows generic V4L2 applications to use XU controls by mapping
27 The second mechanism requires uvcvideo-specific knowledge for the application to
28 access XU controls but exposes the entire UVC XU concept to user space for
36 The UVC driver provides an API for user space applications to define so-called
38 ranges thereof to be mapped to new V4L2 controls. Such controls appear and
43 The ioctl used to create these control mappings is called UVCIOC_CTRL_MAP.
44 Previous driver versions (before 0.2.0) required another ioctl to be used
45 beforehand (UVCIOC_CTRL_ADD) to pass XU control information to the UVC driver.
[all …]
|
| D | v4l2-framework.txt | 11 The V4L2 drivers tend to be very complex due to the complexity of the
16 Especially the fact that V4L2 drivers have to setup supporting ICs to
18 Usually these ICs are connected to the main bridge driver through one or
22 For a long time the framework was limited to the video_device struct for
26 This meant that all drivers had to do the setup of device instances and
27 connecting to sub-devices themselves. Some of this is quite complicated
28 to do right and many drivers never did do it correctly.
30 There is also a lot of common code that could never be refactored due to
34 need and this same framework should make it much easier to refactor
37 A good example to look at as a reference is the v4l2-pci-skeleton.c
[all …]
|
| /linux-4.4.14/Documentation/RCU/ |
| D | torture.txt | 8 be loaded to run a torture test. The test periodically outputs
15 It is also possible to specify CONFIG_RCU_TORTURE_TEST=y, which will
17 the CONFIG_RCU_TORTURE_TEST_RUNNABLE config option is used to specify
18 whether the RCU torture tests are to be started immediately during
20 to enable them. This /proc file can be used to repeatedly pause and
24 You will normally -not- want to start the RCU torture tests during boot
40 to force_quiescent_state() within a burst.
43 of calls to force_quiescent_state().
55 irqreader Says to invoke RCU readers from irq level. This is currently
56 done via timers. Defaults to "1" for variants of RCU that
[all …]
|
| D | checklist.txt | 10 0. Is RCU being applied to a read-mostly situation? If the data
28 RCU does allow -readers- to run (almost) naked, but -writers- must
33 c. restricting updates to a single task.
35 If you choose #b, be prepared to describe how you have handled
37 them -- even x86 allows later loads to be reordered to precede
38 earlier stores), and be prepared to explain why this added
39 complexity is worthwhile. If you choose #c, be prepared to
42 information relating to itself that other tasks can read, there
47 to prevent grace periods from ending prematurely, which
60 The whole point of RCU is to permit readers to run without
[all …]
|
| D | arrayRCU.txt | 1 Using RCU to Protect Read-Mostly Arrays
4 Although RCU is more commonly used to protect linked lists, it can
5 also be used to protect arrays. Three situations are as follows:
13 Each of these three situations involves an RCU-protected pointer to an
14 array that is separately indexed. It might be tempting to consider use
15 of RCU to instead protect the index into an array, however, this use
20 arrays prove to be particularly valuable (which they have not thus far),
21 explicit cooperation from the compiler will be required to permit them
22 to be safely used.
33 to other array-of-list situations, such as radix trees.
[all …]
|
| D | UP.txt | 6 is that since there is only one CPU, it should not be necessary to
7 wait for anything else to get done, since there are no other CPUs for
8 anything else to be happening on. Although this approach will -sort- -of-
20 which deletes element B, and then invokes call_rcu() to free element B
23 Now, if call_rcu() were to directly invoke its arguments, then upon return
41 deletes element B from the list, then passes it to call_rcu() for deferred
43 RCU usage, since call_rcu() must wait for a grace period to elapse.
44 Therefore, in this case, allowing call_rcu() to immediately invoke
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/networking/caif/ |
| D | spi_porting.txt | 5 Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
6 Two extra GPIOs have been added in order to negotiate the transfers
9 Please note that running as a slave implies that you need to keep up
18 SPI slave device part, which is the module that you have to write if
19 you want to run SPI CAIF on a new hardware. This part takes care of
20 the physical hardware, both with regard to SPI and to GPIOs.
26 In order to implement a SPI device you will, as a minimum,
27 need to implement the following
32 This function is called by the CAIF SPI interface to give
33 you a chance to set up your hardware to be ready to receive
[all …]
|
| /linux-4.4.14/arch/arc/include/asm/ |
| D | uaccess.h | 166 __arc_copy_from_user(void *to, const void __user *from, unsigned long n) in __arc_copy_from_user() argument
177 if (((unsigned long)to & 0x3) || ((unsigned long)from & 0x3)) { in __arc_copy_from_user()
203 "=&r" (tmp), "+r" (to), "+r" (from) in __arc_copy_from_user()
244 : "+r" (res), "+r"(to), "+r"(from), in __arc_copy_from_user()
268 : "+r" (res), "+r"(to), "+r"(from), in __arc_copy_from_user()
289 : "+r" (res), "+r"(to), "+r"(from), "=r"(tmp1) in __arc_copy_from_user()
309 : "+r" (res), "+r"(to), "+r"(from), "=r"(tmp1) in __arc_copy_from_user()
327 : "+r" (res), "+r"(to), "+r"(from), "=r"(tmp1) in __arc_copy_from_user()
383 : "=r" (res), "+r"(to), "+r"(from), "+r"(n), "=r"(val), in __arc_copy_from_user()
392 extern unsigned long slowpath_copy_to_user(void __user *to, const void *from,
[all …]
|
| /linux-4.4.14/net/core/ |
| D | dev_addr_lists.c | 537 int dev_uc_sync(struct net_device *to, struct net_device *from) in dev_uc_sync() argument
541 if (to->addr_len != from->addr_len) in dev_uc_sync()
544 netif_addr_lock_nested(to); in dev_uc_sync()
545 err = __hw_addr_sync(&to->uc, &from->uc, to->addr_len); in dev_uc_sync()
547 __dev_set_rx_mode(to); in dev_uc_sync()
548 netif_addr_unlock(to); in dev_uc_sync()
567 int dev_uc_sync_multiple(struct net_device *to, struct net_device *from) in dev_uc_sync_multiple() argument
571 if (to->addr_len != from->addr_len) in dev_uc_sync_multiple()
574 netif_addr_lock_nested(to); in dev_uc_sync_multiple()
575 err = __hw_addr_sync_multiple(&to->uc, &from->uc, to->addr_len); in dev_uc_sync_multiple()
[all …]
|
| /linux-4.4.14/block/ |
| D | bounce.c | 53 static void bounce_copy_vec(struct bio_vec *to, unsigned char *vfrom) in bounce_copy_vec() argument
59 vto = kmap_atomic(to->bv_page); in bounce_copy_vec()
60 memcpy(vto + to->bv_offset, vfrom, to->bv_len); in bounce_copy_vec()
67 #define bounce_copy_vec(to, vfrom) \ argument
68 memcpy(page_address((to)->bv_page) + (to)->bv_offset, vfrom, (to)->bv_len)
102 static void copy_to_high_bio_irq(struct bio *to, struct bio *from) in copy_to_high_bio_irq() argument
108 bio_for_each_segment(tovec, to, iter) { in copy_to_high_bio_irq()
187 struct bio_vec *to, from; in __blk_queue_bounce() local
199 bio_for_each_segment_all(to, bio, i) { in __blk_queue_bounce()
200 struct page *page = to->bv_page; in __blk_queue_bounce()
[all …]
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | provider.txt | 10 They have a given number of channels to use for the DMA transfers, and
14 to serve several to any requests. To simplify, channels are the
18 The request lines actually correspond to physical lines going from the
19 DMA-eligible devices to the controller itself. Whenever the device
20 will want to start a transfer, it will assert a DMA request (DRQ) by
25 byte of data from one buffer to another, until the transfer size has
29 require a specific number of bits to be transferred in a single
30 cycle. For example, we may want to transfer as much data as the
31 physical bus allows to maximize performances when doing a simple
33 that requires data to be written exactly 16 or 24 bits at a time. This
[all …]
|
| /linux-4.4.14/Documentation/x86/ |
| D | intel_mpx.txt | 6 that can be used in conjunction with compiler changes to check memory
8 usurped at runtime due to buffer overflow or underflow.
14 For more information, please refer to Intel(R) Architecture Instruction
19 possible to use SDE (Intel(R) Software Development Emulator) instead, which
24 2. How to get the advantage of MPX
27 For MPX to work, changes are required in the kernel, binutils and compiler.
30 There are a lot of moving parts of this to all work right. The following
31 is how we expect the compiler, application and kernel to work together.
37 points the "bndcfgu" register to the directory (must also set the valid
39 that the app will be using MPX. The app must be careful not to access
[all …]
|
| /linux-4.4.14/arch/c6x/include/asm/ |
| D | uaccess.h | 25 static inline __must_check long __copy_from_user(void *to, in __copy_from_user() argument
34 *(u8 *)to = *(u8 __force *)from; in __copy_from_user()
41 : "A"(to), "a"(from) in __copy_from_user()
49 : "a"(to), "a"(from) in __copy_from_user()
57 memcpy(to, (const void __force *)from, n); in __copy_from_user()
61 static inline __must_check long __copy_to_user(void __user *to, in __copy_to_user() argument
70 *(u8 __force *)to = *(u8 *)from; in __copy_to_user()
77 : "a"(to), "a"(from) in __copy_to_user()
85 : "a"(to), "a"(from) in __copy_to_user()
93 memcpy((void __force *)to, from, n); in __copy_to_user()
|
| /linux-4.4.14/arch/s390/lib/ |
| D | uaccess.c | 105 unsigned long __copy_from_user(void *to, const void __user *from, unsigned long n) in __copy_from_user() argument
108 return copy_from_user_mvcos(to, from, n); in __copy_from_user()
109 return copy_from_user_mvcp(to, from, n); in __copy_from_user()
178 unsigned long __copy_to_user(void __user *to, const void *from, unsigned long n) in __copy_to_user() argument
181 return copy_to_user_mvcos(to, from, n); in __copy_to_user()
182 return copy_to_user_mvcs(to, from, n); in __copy_to_user()
186 static inline unsigned long copy_in_user_mvcos(void __user *to, const void __user *from, in copy_in_user_mvcos() argument
204 : "+a" (size), "+a" (to), "+a" (from), "+a" (tmp1), "=a" (tmp2) in copy_in_user_mvcos()
209 static inline unsigned long copy_in_user_mvc(void __user *to, const void __user *from, in copy_in_user_mvc() argument
236 : "+a" (size), "+a" (to), "+a" (from), "=a" (tmp1) in copy_in_user_mvc()
[all …]
|
| /linux-4.4.14/Documentation/vm/ |
| D | transhuge.txt | 24 factor will affect all subsequent accesses to the memory for the whole
34 miss is going to run faster.
39 hugepage knowledge fall back to breaking a transparent hugepage and
55 to avoid unmovable pages to fragment all the memory but such a tweak
56 is not specific to transparent hugepage support and it's a generic
57 feature that applies to all dynamic high order allocations in the
61 regions but it'd be ideal to move it to tmpfs and the pagecache
65 if compared to the reservation approach of hugetlbfs by allowing all
66 unused memory to be used as cache or other movable (or even unmovable
67 entities). It doesn't require reservation to prevent hugepage
[all …]
|
| D | page_migration | 9 The main intend of page migration is to reduce the latency of memory access
10 by moving pages near to the processor where the process accessing that memory
13 Page migration allows a process to manually relocate the node on which its
18 process that are located on the from nodes to the destination nodes.
22 which provides an interface similar to other numa functionality for page
28 a process to a processor on a distant node. A batch scheduler or an
30 nearer to the new processor. The kernel itself does only provide
35 accesses and may use the result to move pages to more advantageous
39 sections of nodes. Paul Jackson has equipped cpusets with the ability to
40 move pages when a task is moved to another cpuset (See
[all …]
|
| D | balance | 7 sleep due to holding a spinlock or is in interrupt context. The second may
8 be that the caller is willing to fail the allocation without incurring the
11 the caller may also wish to avoid waking kswapd.
13 __GFP_IO allocation requests are made to prevent file system deadlocks.
16 to be doing balancing. Page reclamation can be kicked off lazily, that
20 That being said, the kernel should try to fulfill requests for direct
22 the dma pool, so as to keep the dma pool filled for dma requests (atomic
23 or not). A similar argument applies to highmem and direct mapped pages.
24 OTOH, if there is a lot of free dma pages, it is preferable to satisfy
32 been running production machines of varying memory sizes, and seems to be
[all …]
|
| D | frontswap.txt | 6 and the only necessary changes to the core kernel for transcendent memory;
13 a "backing" store for a swap device. The storage is assumed to be
15 to the requirements of transcendent memory (such as Xen's "tmem", or
19 links itself to frontswap by calling frontswap_register_ops to set the
21 conform to certain policies as follows:
23 An "init" prepares the device to receive frontswap pages associated
25 copy the page to transcendent memory and associate it with the type and
31 to refuse further stores with that swap type.
35 to swap out a page, it first attempts to use frontswap. If the store returns
36 success, the data has been successfully saved to transcendent memory and
[all …]
|
| D | numa | 10 or more CPUs, local memory, and/or IO buses. For brevity and to
19 point-to-point link are common types of NUMA system interconnects. Both of
20 these types of interconnects can be aggregated to create NUMA platforms with
25 to and accessible from any CPU attached to any cell and cache coherency
30 cell containing the target memory. For example, access to memory by CPUs
31 attached to the same cell will experience faster access times and higher
32 bandwidths than accesses to memory on other, remote cells. NUMA platforms
35 Platform vendors don't build NUMA systems just to make software developers'
36 lives interesting. Rather, this architecture is a means to provide scalable
37 memory bandwidth. However, to achieve scalable memory bandwidth, system and
[all …]
|
| D | ksm.txt | 1 How to use the Kernel Samepage Merging feature
5 added to the Linux kernel in 2.6.32. See mm/ksm.c for its implementation,
11 copied if a process later wants to update its content).
14 Kernel Shared Memory), to fit more virtual machines into physical memory,
15 by sharing the data common between them. But it can be useful to any
24 has advised to be likely candidates for merging, by using the madvise(2)
27 The app may call int madvise(addr, length, MADV_UNMERGEABLE) to cancel
39 MADV_UNMERGEABLE is applied to a range which was never MADV_MERGEABLE.
47 restricting its use to areas likely to benefit. KSM's scans may use a lot
53 pages_to_scan - how many present pages to scan before ksmd goes to sleep
[all …]
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | backend-api.txt | 5 The FS-Cache system provides an API by which actual caches can be supplied to
6 FS-Cache for it to then serve out to network filesystems and other interested
17 cache the backend wants to make available. For instance, CacheFS does this in
29 (*) "cache" is a pointer to the cache definition;
31 (*) "ops" is a pointer to the table of operations that the backend supports on
38 The cache should then be registered with FS-Cache by passing a pointer to the
39 previously initialised cache definition to:
47 (*) "fsdef" which should point to the object representation for the FS-Cache
49 here. FS-Cache keeps the caller's reference to the index object if
54 identifier is set to name the underlying block device and the tag can be
[all …]
|
| D | netfs-api.txt | 10 FS-Cache to make finding objects faster and to make retiring of groups of
15 need to care.
70 (3) The cookie representing the primary index will be allocated according to
73 For example, kAFS (linux/fs/afs/) uses the following definitions to describe
91 (2) To make it easier to discard a subset of all the files cached based around
92 a particular key - for instance to mirror the removal of an AFS volume.
94 However, since it's unlikely that any two netfs's are going to want to define
95 their index hierarchies in quite the same way, FS-Cache tries to impose as few
105 (1) Any index containing non-index objects should be restricted to a single
110 (2) The entry data must be atomically journallable, so it is limited to about
[all …]
|
| D | operations.txt | 29 This facility is available to and expected to be be used by the cache backends,
30 and FS-Cache will create operations and pass them off to the appropriate cache
52 Someone wanting to issue an operation should allocate something with this
58 with the operation to be initialised and the release function to use.
60 The op->flags parameter should be set to indicate the CPU time provision and
66 FSCACHE_OP_WAITING may be set in op->flags prior to each submission of the
79 may decide it wants to handle an operation itself without deferring it to
88 If this option is to be used, FSCACHE_OP_WAITING must be set in op->flags
90 to be cleared before proceeding:
97 will be given to keventd to process. Such an operation is not permitted
[all …]
|
| D | object.txt | 27 struct and are referred to as cookies.
32 are expected to embed them in their own representations. These are referred to
87 As far as the netfs API goes, the netfs is only actually permitted to see
88 pointers to the cookies. The cookies themselves and any objects attached to
98 object->state. A cookie may point to a set of objects that are in different
104 (1) Preparation: states that wait for the parent objects to become ready. The
106 be created or accessed with respect to its parent object.
111 (3) Normal running: states that allow netfs operations on objects to proceed
119 In most cases, transitioning between states is in response to signalled events.
130 The work to be done by the various states was given CPU time by the threads of
[all …]
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 8 MOST defines the protocol, hardware and software layers necessary to allow
12 also supports various speed grades up to 150 Mbps.
16 Cars continue to evolve into sophisticated consumer electronics platforms,
17 increasing the demand for reliable and simple solutions to support audio,
18 video and data communications. MOST can be used to connect multiple
19 consumer devices via optical or electrical physical layers directly to one
22 audio/video streaming. Therefore, the driver perfectly fits to the mission
23 of Automotive Grade Linux to create open source software solutions for
32 modules can arbitrarily be combined to meet the needs of the desired
33 system architecture. A module of the hardware layer is referred to as an
[all …]
|
| /linux-4.4.14/arch/arm/nwfpe/ |
| D | ChangeLog | 2 * Reformat all but softfloat files to get a consistent coding style.
4 * Removed dead code and fixed function protypes to match definitions.
13 - add new method to obtain integer register values.
19 It is used by users of ptrace to examine the values of the
20 floating point registers. Therefore, any changes to the
22 within) have to be well thought out.
24 * Since 128-bit float requires the FPA11 structure to change
26 and needs various things to be re-worked so that we won't
29 * The changes are designed to break any patch that goes on top
34 * fpmodule.c - Changed version number to 0.95
[all …]
|
| /linux-4.4.14/Documentation/gpio/ |
| D | drivers-on-gpio.txt | 9 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 i.e. a LED will turn on/off in response to a GPIO line going high or low
17 can generate interrupts in response to a key press. Also supports debounce.
20 GPIO line cannot generate interrupts, so it needs to be periodically polled
23 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
24 up to three buttons by simply using GPIOs and no mouse port. You can cut the
25 mouse cable and connect the wires to GPIO lines or solder a mouse connector
26 to the lines for a more permanent solution of this type.
28 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
29 an external speaker connected to a GPIO line.
[all …]
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | serial-u16550.txt | 5 The adaptor module parameter allows you to select either:
14 switches on the Midiator to match the driver mode you select.
17 (midiCnD0-midiCnD15). Whenever you write to a different substream, the driver
19 number plus 1. Roland modules use this command to switch between different
21 substream. The driver provides no way to send F5 00 (no selection) or to not
22 send the F5 NN command sequence at all; perhaps it ought to.
35 module parameter is automatically set to 1. The driver sends the same data to
37 parameter to match (A=19200, B=9600).
46 the outs module parameter is automatically set to 1. The driver sends
47 the same data to all four MIDI Out connectors at full MIDI speed.
[all …]
|
| D | SB-Live-mixer.txt | 6 The EMU10K1 chips have a DSP part which can be programmed to support
19 (index 0) for a given card) allows to forward 48kHz, stereo, 16-bit
20 little endian streams without any modifications to the digital output
22 to 8 raw PCM devices operating at 48kHz, 16-bit little endian. It would
23 be easy to add support for multichannel devices to the current code,
27 Look to tram_poke routines in lowlevel/emu10k1/emufx.c for more details.
38 (set to maximal or minimal value without checking of overflow).
43 DAC - digital to analog converter
44 ADC - analog to digital converter
51 Each of the synthesizer voices can feed its output to these accumulators
[all …]
|
| D | Audigy-mixer.txt | 7 The EMU10K2 chips have a DSP part which can be programmed to support
24 (set to maximal or minimal value without checking of overflow).
29 DAC - digital to analog converter
30 ADC - analog to digital converter
37 Each of the synthesizer voices can feed its output to these accumulators
42 This control is used to attenuate samples for left and right front PCM FX-bus
44 samples for 5.1 playback. The result samples are forwarded to the front DAC PCM
49 This control is used to attenuate samples for left and right surround PCM FX-bus
51 samples for 5.1 playback. The result samples are forwarded to the surround DAC PCM
56 This control is used to attenuate samples for center PCM FX-bus accumulator.
[all …]
|
| D | compress_offload.txt | 10 returned values in frames are the norm, making it a challenge to
11 extend the existing API to compressed data streams.
16 reduction of power consumption compared to host-based
22 ALSA PCM interface, a new 'Compressed Data' API is introduced to
26 Intel Moorestown SOC, with many corrections required to upstream the
36 may vary from frame-to-frame. As a result, it is not possible to
38 compressed data. Dedicated mechanisms are required to allow for
57 cycles. The new API needs to provide a generic way of listing these
61 hardware acceleration, where PCM samples are provided back to
63 streaming compressed data to a DSP, with the assumption that the
[all …]
|
| /linux-4.4.14/arch/powerpc/include/asm/ |
| D | uaccess.h | 318 extern unsigned long __copy_tofrom_user(void __user *to,
323 static inline unsigned long copy_from_user(void *to, in copy_from_user() argument
329 return __copy_tofrom_user((__force void __user *)to, from, n); in copy_from_user()
332 return __copy_tofrom_user((__force void __user *)to, from, in copy_from_user()
338 static inline unsigned long copy_to_user(void __user *to, in copy_to_user() argument
343 if (access_ok(VERIFY_WRITE, to, n)) in copy_to_user()
344 return __copy_tofrom_user(to, (__force void __user *)from, n); in copy_to_user()
345 if ((unsigned long)to < TASK_SIZE) { in copy_to_user()
346 over = (unsigned long)to + n - TASK_SIZE; in copy_to_user()
347 return __copy_tofrom_user(to, (__force void __user *)from, in copy_to_user()
[all …]
|
| /linux-4.4.14/Documentation/fb/ |
| D | deferred_io.txt | 4 Deferred IO is a way to delay and repurpose IO. It uses host memory as a
5 buffer and the MMU pagefault as a pretrigger for when to perform the device
11 - userspace app tries to write to mmaped vaddress
14 - we get page_mkwrite where we add this page to a list
15 - schedule a workqueue task to be run after a delay
16 - app continues writing to that page with no additional cost. this is
20 the real work talking to the device.
21 - app tries to write to the address (that has now been mkcleaned)
24 As can be seen from above, one benefit is roughly to allow bursty framebuffer
25 writes to occur at minimum cost. Then after some time when hopefully things
[all …]
|
| D | udlfb.txt | 9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
10 monitor with no CPU involvement until a pixel has to change.
13 result with a local shadow of the remote hardware framebuffer to identify
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
27 * Ability to add a nearly arbitrary number of displays to any USB 2.0
35 one-to-one with the fbdev interface, making the driver quite small and
36 tight relative to the functionality it provides.
38 from user mode to talk to the device, without needing to know anything
46 Writes need to be detected and encoded into USB bulk transfers by the CPU.
49 interface to allow mmap clients to report damage, for the benefit
[all …]
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 4 Your guide to the ancient and twisted locking policies of the tty layer and
13 discipline must be ready to use and it is possible it will get used before
16 and writing over an existing ldisc will cause demons to eat your computer.
22 In order to remove a line discipline call tty_unregister_ldisc().
32 about to enter and exit although this detail matters not).
39 open() - Called when the line discipline is attached to
44 in the tty_struct to the maximum amount of data
45 the line discipline is willing to accept from the
46 driver with a single call to receive_buf().
56 The line discipline should cease I/O to the tty.
[all …]
|
| /linux-4.4.14/drivers/net/wireless/mwifiex/ |
| D | README | 7 # is available by writing to the Free Software Foundation, Inc.,
22 a) Copy sd8787.bin to /lib/firmware/mrvl/ directory,
45 The above command can be used to connect to an AP with a particular SSID.
48 …Note: Every time before connecting to an AP scan command (iw dev mlan0 scan) should be used by use…
51 This command will be used to disconnect from an AP.
55 The command will be used to join or create an ibss. Optionally, operating frequency,
60 The command will be used to leave an ibss network.
63 The command will be used to get the connection status. The command will return parameters
75 Mount debugfs to /debugfs mount point:
83 The command will be used to change the regulatory domain.
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxlflash.txt | 5 Accelerator Power Interface), which is available to certain PCIe slots
7 protocol through PCIe that allow PCIe adapters to look like special
9 memory and generate page faults. As a result, the host interface to
10 an adapter running in CAPI mode does not require the data buffers to
11 be mapped to the device's memory (IOMMU bypass) nor does it require
12 memory to be pinned.
17 model, allowing for drivers to look similar to other native PCI
21 directly talk to a device (network or storage) bypassing the typical
23 user space application direct access to Flash storage.
36 - Any flash device (LUN) can be configured to be accessed as a
[all …]
|
| D | hvcs.txt | 34 "hvcs". The IBM hvcs provides a tty driver interface to allow Linux user
35 space applications access to the system consoles of logically partitioned
39 firmware interfaces to virtual terminal devices.
47 This driver was written to operate solely on IBM Power5 ppc64 hardware
48 though some care was taken to abstract the architecture dependent firmware
61 for 64 of these major/minor numbers by default to use for hvcs device node
71 The following menuconfig example demonstrates selecting to build this
83 The following menuconfig example demonstrates selecting to build this
112 to allow. This can always be changed by modifying the constant in the
115 NOTE: The length of time it takes to insmod the driver seems to be related
[all …]
|
| D | firmware-assisted-dump.txt | 6 The goal of firmware-assisted dump is to enable the dump of
7 a crashed system, and to do so from a fully-reset system, and
8 to minimize the total elapsed time until the system is back
11 - Firmware assisted dump (fadump) infrastructure is intended to replace
18 - Unlike phyp dump, userspace tool does not need to refer any sysfs
20 - Unlike phyp dump, fadump allows user to release all the memory reserved
35 is immediately available to the running kernel. And therefore,
36 unlike kdump, fadump doesn't need a 2nd reboot to get back
37 the system to the production configuration.
50 or 256MB) of RAM to the previous registered region. It will
[all …]
|
| D | eeh-pci-error-recovery.txt | 16 hardware features allow PCI bus errors to be cleared and a PCI
17 card to be "rebooted", without also having to reboot the operating
20 This is in contrast to traditional PCI error handling, where the
21 PCI chip is wired directly to the CPU, and an error would cause
23 Another "traditional" technique is to ignore such errors, which
24 can lead to data corruption, both of user data or of kernel data,
28 the OS the ability to "reboot"/recover individual PCI devices.
36 EEH was originally designed to guard against hardware failure, such
39 "real life" are due to either poorly seated PCI cards, or,
40 unfortunately quite commonly, due to device driver bugs, device firmware
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
11 controlled, so the only chance to keep them working is by using this driver.
16 is usually 1:1 for hardware to LED signals, but through the activity/link
19 controlled you are still able to make it blink or light it up if it isn't,
20 but you can't turn it off if the hardware decides to light it up. For this
44 - reg : LED pin number (only LEDs 0 to 23 are valid).
47 a) Optional properties for sub-nodes related to software controlled LEDs:
[all …]
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace-design.txt | 16 Ideally, everyone who wishes to retain performance while supporting tracing in
17 their kernel should make it all the way to dynamic ftrace support.
31 You will need to implement the mcount and the ftrace_stub functions.
38 We'll make the assumption below that the symbol is "mcount" just to keep things
44 you to bang ideas off of. Typically, register usage (argument/scratch/etc...)
45 is a major issue at this point, especially in relation to the location of the
46 mcount call (before/after function prologue). You might also want to look at
51 to see if it is set to ftrace_stub. If it is, there is nothing for you to do,
54 the "frompc" while the second argument is the "selfpc" (adjusted to remove the
58 mcount(), the arguments mcount() will pass to the tracer are:
[all …]
|
| D | stm.txt | 8 these masters and channels are statically allocated to certain
9 hardware trace sources, others are available to software. Software
10 trace sources are usually free to pick for themselves any
15 order for the decoder to be able to make sense of the trace that
16 involves multiple trace sources, it needs to be able to map those
17 master/channel pairs to the trace sources that it understands.
19 For instance, it is helpful to know that syslog messages come on
21 48 to 63 and channels 0 to 127.
25 identifiers to ranges of masters and channels. If these rules (policy)
26 are consistent with what decoder expects, it will be able to properly
[all …]
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 1 The cgroup freezer is useful to batch job management system which start
2 and stop sets of tasks in order to schedule the resources of a machine
3 according to the desires of a system administrator. This sort of program
4 is often used on HPC clusters to schedule access to the cluster as a
5 whole. The cgroup freezer uses cgroups to describe the set of tasks to
7 a means to start and stop the tasks composing the job.
10 of tasks. The freezer allows the checkpoint code to obtain a consistent
11 image of the tasks by attempting to force the tasks in a cgroup into a
13 walk /proc or invoke a kernel interface to gather information about the
15 recoverable error occur. This also allows the checkpointed tasks to be
[all …]
|
| /linux-4.4.14/net/dccp/ |
| D | options.c | 269 void dccp_encode_value_var(const u64 value, u8 *to, const u8 len) in dccp_encode_value_var() argument
272 *to++ = (value & 0xFF0000000000ull) >> 40; in dccp_encode_value_var()
274 *to++ = (value & 0xFF00000000ull) >> 32; in dccp_encode_value_var()
276 *to++ = (value & 0xFF000000) >> 24; in dccp_encode_value_var()
278 *to++ = (value & 0xFF0000) >> 16; in dccp_encode_value_var()
280 *to++ = (value & 0xFF00) >> 8; in dccp_encode_value_var()
282 *to++ = (value & 0xFF); in dccp_encode_value_var()
295 unsigned char *to; in dccp_insert_option() local
302 to = skb_push(skb, len + 2); in dccp_insert_option()
303 *to++ = option; in dccp_insert_option()
[all …]
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig.txt | 3 Use "make help" to list all of the possible configuration targets.
6 have embedded help text. Be sure to check it for navigation,
17 for you, so you may find that you need to see what NEW kernel
34 This environment variable can be used to specify a default kernel config
35 file name to override the default name of ".config".
40 break symlinks when .config is a symlink to somewhere else.
57 that contains config symbols that the user requires to be set to a
61 (corresponding to the *config command that was used) for symbol values
62 that are to be forced. If this file is not found, it checks for a
63 file named "all.config" to contain forced values.
[all …]
|
| D | kbuild.txt | 6 is used by modprobe to deterministically resolve aliases that match
12 by modprobe to not fail when trying to load something builtin.
19 Additional options to pass when preprocessing. The preprocessing options
25 Additional options to the assembler (for built-in and modules).
29 Additional module specific options to use for $(AS).
38 Additional options to the C compiler (for built-in and modules).
42 Additional options for $(CC) when used to compile
47 Additional module specific options to use for $(CC).
55 Additional options passed to final link of vmlinux.
65 Set the directory to look for the kernel source when building external
[all …]
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 9 Reiser, or authorized to be licensed by him, have been in the past,
10 and likely will be in the future, licensed to other parties under
11 other licenses. If you add your code to governed files, and don't
12 want it to be owned by Hans Reiser, put your copyright label on that
15 Reiser, and by adding your code to it, widely distributing it to
19 to license code labeled as owned by you on your behalf other than
20 under the GPL, because he wants to know if it is okay to do so and put
21 a check in the mail to you (for non-trivial improvements) when he
22 makes his next sale. He makes no guarantees as to the amount if any,
23 though he feels motivated to motivate contributors, and you can surely
[all …]
|
| /linux-4.4.14/arch/blackfin/include/asm/ |
| D | uaccess.h | 166 #define __copy_from_user(to, from, n) copy_from_user(to, from, n) argument
167 #define __copy_to_user(to, from, n) copy_to_user(to, from, n) argument
171 #define copy_to_user_ret(to, from, n, retval) ({ if (copy_to_user(to, from, n))\ argument
174 #define copy_from_user_ret(to, from, n, retval) ({ if (copy_from_user(to, from, n))\ argument
178 copy_from_user(void *to, const void __user *from, unsigned long n) in copy_from_user() argument
181 memcpy(to, (const void __force *)from, n); in copy_from_user()
188 copy_to_user(void __user *to, const void *from, unsigned long n) in copy_to_user() argument
190 if (access_ok(VERIFY_WRITE, to, n)) in copy_to_user()
191 memcpy((void __force *)to, from, n); in copy_to_user()
243 __clear_user(void __user *to, unsigned long n) in __clear_user() argument
[all …]
|
| /linux-4.4.14/Documentation/block/ |
| D | data-integrity.txt | 4 Modern filesystems feature checksumming of data and metadata to
8 application tried to write is most likely lost.
10 The solution is to ensure that the disk is actually storing what the
11 application meant it to. Recent additions to both the SCSI family
13 as SATA/T13 (External Path Protection) try to remedy this by adding
14 support for appending integrity metadata to an I/O. The integrity
18 for some protection schemes also that the I/O is written to the right
36 allow the operating system to interact with the integrity metadata
37 (IMD). We have been working with several FC/SAS HBA vendors to enable
38 the protection information to be transferred to and from their
[all …]
|
| D | biodoc.txt | 15 context of the bio rewrite. The idea is to bring out some of the key
18 Please mail corrections & suggestions to suparna@in.ibm.com.
37 The following people helped with fixes/contributions to the bio patches
45 1. Scope for tuning of logic to various needs
52 1.3 Direct access/bypass to lower layers for diagnostics and special
73 5.2 Prepare for transition to 64 bit sector_t
88 1. Scope for tuning the generic logic to satisfy various requirements
90 The block layer design supports adaptable abstractions to handle common
91 processing with the ability to tune the logic to an appropriate extent
93 One of the objectives of the rewrite was to increase the degree of tunability
[all …]
|
| /linux-4.4.14/arch/powerpc/lib/ |
| D | usercopy_64.c | 12 unsigned long copy_from_user(void *to, const void __user *from, unsigned long n) in copy_from_user() argument
15 n = __copy_from_user(to, from, n); in copy_from_user()
17 memset(to, 0, n); in copy_from_user()
21 unsigned long copy_to_user(void __user *to, const void *from, unsigned long n) in copy_to_user() argument
23 if (likely(access_ok(VERIFY_WRITE, to, n))) in copy_to_user()
24 n = __copy_to_user(to, from, n); in copy_to_user()
28 unsigned long copy_in_user(void __user *to, const void __user *from, in copy_in_user() argument
33 access_ok(VERIFY_WRITE, to, n))) in copy_in_user()
34 n =__copy_tofrom_user(to, from, n); in copy_in_user()
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Kconfig | 16 connected through a parallel port. If you chose to build PARIDE
17 support into your kernel, you may answer Y here to build in the
18 parallel port IDE driver, otherwise you should answer M to build
30 connected through a parallel port. If you chose to build PARIDE
31 support into your kernel, you may answer Y here to build in the
32 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
37 you have such a CD-ROM drive, you should also say Y or M to "ISO
46 connected through a parallel port. If you chose to build PARIDE
47 support into your kernel, you may answer Y here to build in the
49 to build it as a loadable module. The module will be called pf.
[all …]
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 16 Clock scaling allows you to change the clock speed of the CPUs on the
17 fly. This is a nice method to save battery power, because the lower
40 cpu frequency scaling algorithms only offer the CPU to be set to one
41 frequency. In order to offer dynamic frequency scaling, the cpufreq
42 core must be able to tell these drivers of a "target frequency". So
43 these specific drivers will be transformed to offer a "->target/target_index"
47 How to decide what frequency within the CPUfreq policy should be used?
50 set the frequency statically to the lowest or highest frequency,
54 around. Using such a generic interface as cpufreq offers to scaling
60 CPU can be set to switch independently | CPU can only be set
[all …]
|
| D | cpu-drivers.txt | 15 Clock scaling allows you to change the clock speed of the CPUs on the
16 fly. This is a nice method to save battery power, because the lower
37 So, you just got a brand-new CPU / chipset with datasheets and want to
54 cpufreq_driver.init - A pointer to the per-CPU initialization
57 cpufreq_driver.verify - A pointer to a "verification" function.
65 cpufreq_driver.exit - A pointer to a per-CPU cleanup
69 cpufreq_driver.stop_cpu - A pointer to a per-CPU stop function
73 cpufreq_driver.resume - A pointer to a per-CPU resume function
76 and/or policy is restored by a call to
79 cpufreq_driver.attr - A pointer to a NULL-terminated list of
[all …]
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 9 When the kernel has several packets to send out over a network
10 device, it has to decide which ones to send first, which ones to
11 delay, and which ones to drop. This is the job of the queueing
12 disciplines, several different algorithms for how to do this
17 able to choose from among several alternative algorithms which can
18 then be attached to different network devices. This is useful for
20 need a certain minimum data flow rate, or if you need to limit the
22 This code is considered to be experimental.
30 This Quality of Service (QoS) support will enable you to use
32 (RSVP) on your Linux router if you also say Y to the corresponding
[all …]
|
| /linux-4.4.14/arch/microblaze/include/asm/ |
| D | uaccess.h | 122 extern unsigned long __copy_tofrom_user(void __user *to,
126 static inline unsigned long __must_check __clear_user(void __user *to, in __clear_user() argument
139 : "=r"(n), "=r"(to) \ in __clear_user()
140 : "0"(n), "1"(to) in __clear_user()
145 static inline unsigned long __must_check clear_user(void __user *to, in clear_user() argument
149 if (unlikely(!access_ok(VERIFY_WRITE, to, n))) in clear_user()
152 return __clear_user(to, n); in clear_user()
367 #define __copy_from_user(to, from, n) \ argument
368 __copy_tofrom_user((__force void __user *)(to), \
370 #define __copy_from_user_inatomic(to, from, n) \ argument
[all …]
|
| /linux-4.4.14/arch/mips/include/asm/ |
| D | uaccess.h | 813 #define __invoke_copy_to_user(to, from, n) \ argument
819 __cu_to_r = (to); \
831 #define __invoke_copy_to_kernel(to, from, n) \ argument
832 __invoke_copy_to_user(to, from, n)
851 #define __copy_to_user(to, from, n) \ argument
857 __cu_to = (to); \
872 #define __copy_to_user_inatomic(to, from, n) \ argument
878 __cu_to = (to); \
890 #define __copy_from_user_inatomic(to, from, n) \ argument
896 __cu_to = (to); \
[all …]
|
| /linux-4.4.14/Documentation/i2c/ |
| D | slave-interface | 7 functionality. For that to work, one needs slave support in the bus driver plus
35 is that i2c slave backends have their own address space. So, you have to add
36 0x1000 to the address you would originally request. An example for
42 Each backend should come with separate documentation to describe its specific
57 The bus driver sends an event to the backend using the following function:
62 types described hereafter. 'val' holds an u8 value for the data byte to be
63 read/written and is thus bidirectional. The pointer to val must always be
75 Another I2C master wants to write data to us. This event should be sent once
77 there is nothing to process or return. Wakeup or initialization probably needs
78 to be done, though.
[all …]
|
| D | old-module-parameters | 4 Up to kernel 2.6.32, many i2c drivers used helper macros provided by
5 <linux/i2c.h> which created standard module parameters to let the user
6 control how the driver would probe i2c buses and attach to devices. These
7 parameters were known as "probe" (to let the driver probe for an extra
8 address), "force" (to forcibly attach the driver to a given device) and
9 "ignore" (to prevent a driver from probing a given address).
11 With the conversion of the i2c subsystem to the standard device driver
17 Below is a mapping from the old module parameters to the new interface.
19 Attaching a driver to an I2C device
30 Preventing a driver from attaching to an I2C device
[all …]
|
| /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.
10 Every bio that is mapped by the target is referred to the policy.
13 Currently there's no way for the policy to issue background work,
14 e.g. to start writing back dirty blocks that are going to be evicte
18 to get fooled by many small bios. For this reason the core target
19 issues periodic ticks to the policy. It's suggested that the policy
22 trying to see when the io scheduler has let the ios run.
39 on hit count on entry. The policy aims to take different cache miss
40 costs into account and to adjust to varying load patterns automatically.
[all …]
|
| D | log-writes.txt | 4 This target takes 2 devices, one to pass all IO to normally, and one to log all
5 of the write operations to. This is intended for file system developers wishing
6 to verify the integrity of metadata or data as the file system is written to.
8 able to take arbitrary data from userspace to insert into the log. The data
9 that is in the WRITE requests is copied into the log to make the replay happen
17 next REQ_FLUSH request. This is to make it easier for userspace to replay the
18 log in a way that correlates to what is on disk and not what is in cache, to
19 make it easier to detect improper waiting/flushing.
21 This works by attaching all WRITE requests to a list once the write completes.
24 completed WRITEs, at the time the REQ_FLUSH is issued, are added in order to
[all …]
|
| D | switch.txt | 9 It maps I/O to underlying block devices efficiently when there is a large
22 spreading are hidden from initiators connected to this storage system.
25 session is connected to an eth port on a single member. Data to a LUN
28 forwarding is invisible to the initiator. The storage layout is also
29 dynamic, and the blocks stored on disk may be moved from member to
30 member as needed to balance the load.
34 is possible to set up multiple iSCSI sessions to use multiple network
35 interfaces on both the host and target to take advantage of the
37 robin algorithm to send I/O across all paths and let the storage array
38 members forward it as necessary, but there is a performance advantage to
[all …]
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-rt-group.txt | 28 resolution, or the time it takes to handle the budget refresh itself.
42 Realtime scheduling is all about determinism, a group has to be able to rely on
43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
54 the other realtime groups will not be permitted to use.
56 Any time not allocated to a realtime group will be used to run normal priority
62 have to play some music and respond to input, leaving it with around 80% CPU
67 limit. Now if the audio thread needs to refill the DMA buffer every 0.005s, but
68 needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
73 realtime tasks have explicitly allocated the CPU time they need to perform
77 lack an EDF scheduler to make non-uniform periods usable.
[all …]
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | Kconfig | 8 video console for blind people. If built in to the
10 boot up to shutdown. For more information on Speakup,
13 can subscribe to.
25 must answer either y or m to at least one of the
36 requires software to be pre-loaded on to the card before
40 If you are not a blind person, or don't have access to
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
[all …]
|
| /linux-4.4.14/drivers/staging/panel/ |
| D | Kconfig | 5 Say Y here if you have an HD44780 or KS-0074 LCD connected to your
8 keypad through /dev/keypad (10, 185). Both require misc device to be
19 This is the index of the parallel port the panel is connected to. One
21 and LCD are connected to two separate ports, you have to start two
33 used to define an approximative configuration, completed by a few
43 Custom configurations allow you to define how your display is
44 wired to the parallel port, and how it works. This is only intended
53 This enables and configures a keypad connected to the parallel port.
70 This enables and configures an LCD connected to the parallel port.
72 '\e[L' which are specific to the LCD, and a few ANSI codes. The
[all …]
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | fault_injection.txt | 5 may be difficult to reproduce. Forcing these errors in a controlled environment
7 production system. Injecting an error on the Linux NFS server will allow us to
8 observe how the client reacts and if it manages to recover its state correctly.
10 NFSD_FAULT_INJECTION must be selected when configuring the kernel to use this
19 On the server, mount the debugfs filesystem to <debug_dir> and ls
21 injecting faults on the NFS server. As root, write a number n to the file
22 corresponding to the action you want the server to take. The server will then
23 process the first n items it finds. So if you want to forget 5 locks, echo '5'
24 to <debug_dir>/nfsd/forget_locks. A value of 0 will tell the server to forget
28 Go back to work on the client and check if the client recovered from the error
[all …]
|
| D | rpc-server-gss.txt | 5 This document gives references to the standards and protocols used to
8 NFSv4.1 and higher don't require the client to act as a server for the
21 The RPCGSS Authentication method describes a way to perform GSSAPI
37 performance-sensitive. The latter is simpler and needs to be very fast.
40 kernel, but leave the initial context establishment to userspace. We
41 need upcalls to request userspace to perform context establishment.
47 to talk to a custom daemon called rpc.svcgssd that is provide by the
55 beyond 64KiB in size due to various authorization extensions attacked to
56 the Kerberos tickets, that needs to be sent through the GSS layer in
57 order to perform context establishment.
[all …]
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 5 profile will be read next. The data has to be 3 bytes long.
17 The data has to be 3 bytes long.
26 The data has to be 125 bytes long.
27 Before reading this file, control has to be written to select
28 which profile to read.
36 in written data. The data has to be 95 bytes long.
37 Before reading this file, control has to be written to select
38 which profile to read.
46 written data. The data has to be 35 bytes long.
47 Before reading this file, control has to be written to select
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 6 profile. This value is persistent, so its equivalent to the
24 windows and application keys, to prevent accidental presses.
26 written data. The data has to be 6 bytes long.
27 Before reading this file, control has to be written to select
28 which profile to read.
36 in written data. The data has to be 6 bytes long.
37 Before reading this file, control has to be written to select
38 which profile to read.
46 in written data. The data has to be 65 bytes long.
47 Before reading this file, control has to be written to select
[all …]
|
| /linux-4.4.14/drivers/net/ppp/ |
| D | Kconfig | 6 tristate "PPP (point-to-point protocol) support"
9 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
24 example. If you want to use PPP over phone lines or other
25 asynchronous serial lines, you need to say Y (or M) here and also to
27 synchronous lines, you should say Y (or M) here and to "Support
30 If you said Y to "Version information on all symbols" above, then
42 the LZW compression method to compress each PPP packet before it is
44 (usually your ISP) has to support the BSD-Compress compression
45 method as well for this to be useful. Even if they don't support it,
46 it is safe to say Y here.
[all …]
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 4 to more strictly handle corrupt frames.
8 Fix append problem to Samba servers (files opened with O_APPEND could
10 mounting to OS/400 Netserve. Fix oops in cifs_get_tcp_session.
14 cifs_put_smb_ses. Fix mmap to work on directio mounts (needed
20 Set s_maxbytes to smaller (the max that vfs can handle) so that
23 ntlmv2. Fix 2nd mount to same server but with different port to
34 uids to be overridden). Add support for scope mount parm. Improve
35 hard link detection to use same inode for both. Do not set
42 Guard against buffer overruns in various UCS-2 to UTF-8 string conversions
45 to DFS target. Convert string conversion functions from Unicode to more
[all …]
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 1 This directory attempts to document the ABI between the Linux kernel and
2 userspace, and the relative stability of these interfaces. Due to the
8 of stability according to the rules described below.
14 defined to be stable. Userspace programs are free to use these
17 (like syscalls) are expected to never change and always be
21 This directory documents interfaces that are felt to be stable,
23 The interface can be changed to add new features, but the
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
29 strongly encouraged to add their name to the description of
[all …]
|
| /linux-4.4.14/sound/soc/tegra/ |
| D | Kconfig | 17 Say Y or M if you want to add support for codecs attached to the
18 Tegra20 AC97 interface. You will also need to select the individual
19 machine drivers to support below.
25 Say Y or M if you want to add support for the Tegra20 DAS module.
26 You will also need to select the individual machine drivers to
34 Say Y or M if you want to add support for codecs attached to the
35 Tegra20 I2S interface. You will also need to select the individual
36 machine drivers to support below.
43 Say Y or M if you want to add support for the Tegra20 SPDIF interface.
44 You will also need to select the individual machine drivers to support
[all …]
|
| /linux-4.4.14/ |
| D | REPORTING-BUGS | 10 backported to it.
14 Alternatively, you can attempt to run one of the supported stable or -rc
16 to reproduce the bug on the latest -rc kernel.
19 How to report Linux kernel bugs
27 increases your chances of getting your bug fixed. Simply posting to the
28 generic linux-kernel mailing list (LKML) may cause your bug report to be
31 Instead, try to figure out which kernel subsystem is causing the issue,
33 maintainer doesn't answer, then expand your scope to mailing lists like
37 Identify who to notify
41 bug report. Some maintainers prefer bugs to be reported via bugzilla
[all …]
|
| D | COPYING | 6 Foundation, but the instance of code that it refers to (the Linux
22 Everyone is permitted to copy and distribute verbatim copies
27 The licenses for most software are designed to take away your
28 freedom to share and change it. By contrast, the GNU General Public
29 License is intended to guarantee your freedom to share and change free
30 software--to make sure the software is free for all its users. This
31 General Public License applies to most of the Free Software
32 Foundation's software and to any other program whose authors commit to
34 the GNU Library General Public License instead.) You can apply it to
37 When we speak of free software, we are referring to freedom, not
[all …]
|
| /linux-4.4.14/drivers/bluetooth/ |
| D | Kconfig | 27 This driver is required if you want to use Bluetooth devices with
30 Say Y here to compile support for Bluetooth USB devices into the
31 kernel or say M to compile it as module (btusb).
42 Say Y here to compile support for Broadcom protocol.
53 Say Y here to compile support for Realtek protocol.
60 This driver is required if you want to use Bluetooth device with
63 Say Y here to compile support for Bluetooth SDIO devices into the
64 kernel or say M to compile it as module (btsdio).
71 This driver is required if you want to use Bluetooth devices with
76 Say Y here to compile support for Bluetooth UART devices into the
[all …]
|
| /linux-4.4.14/arch/frv/include/asm/ |
| D | uaccess.h | 267 #define __copy_from_user_inatomic(to, from, n) __memcpy_user((to), ____force(from), (n)) argument
268 #define __copy_to_user_inatomic(to, from, n) __memcpy_user(____force(to), (from), (n)) argument
273 #define __copy_from_user_inatomic(to, from, n) (memcpy((to), ____force(from), (n)), 0) argument
274 #define __copy_to_user_inatomic(to, from, n) (memcpy(____force(to), (from), (n)), 0) argument
281 __copy_to_user(void __user *to, const void *from, unsigned long n) in __copy_to_user() argument
284 return __copy_to_user_inatomic(to, from, n); in __copy_to_user()
288 __copy_from_user(void *to, const void __user *from, unsigned long n) in __copy_from_user() argument
291 return __copy_from_user_inatomic(to, from, n); in __copy_from_user()
294 static inline long copy_from_user(void *to, const void __user *from, unsigned long n) in copy_from_user() argument
299 ret = __copy_from_user(to, from, n); in copy_from_user()
[all …]
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 6 user mappings, and similar to be cached in the kernel for the use of
9 Keyrings are permitted; these are a special type of key that can hold links to
54 Userspace programs can use a key's serial numbers as a way to gain access
55 to it, subject to permission checking.
68 type provides an operation to perform a match between the description on a
72 are used to control what a process may do to a key from userspace, and
73 whether a kernel service will be able to find the key.
75 (*) Each key can be set to expire at a specific time by the key type's
79 actual "key". In the case of a keyring, this is a list of keys to which
90 Similarly, when userspace wants to read back the contents of the key, if
[all …]
|
| /linux-4.4.14/Documentation/nfc/ |
| D | nfc-hci.txt | 12 to HCI commands and events.
18 routed through netlink sockets to NFC Core and then to HCI. From this point,
19 they are translated in a sequence of HCI commands sent to the HCI layer in the
24 and a translation will be forwarded to NFC Core as needed. There are hooks to
39 can pass that information to HCI core.
44 A gate defines the 'port' where some service can be found. In order to access
45 a service, one must create a pipe to that gate and open it. In this
47 This is consistent with the driver need to send commands to proprietary gates
48 without knowing the pipe connected to it.
54 the HCI management. This makes it easier to maintain a driver for a chip that
[all …]
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 15 to print messages very early in the bootup process.
21 unless you want to debug such a crash.
29 If you say Y here, it will be possible to use a 8250/16550 serial
41 it might be necessary or advantageous to either override the
42 default kernel command line or add a few extra options to it.
43 For such cases, this option allows you to hardcode your own
48 The built-in options will be concatenated to the default command
49 line if CMDLINE_OVERRIDE is set to 'N'. Otherwise, the default
60 On some platforms, there is currently no way for the boot loader to
61 pass arguments to the kernel. For these platforms, and for the cases
[all …]
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 14 to change your driver to use MSI or MSI-X and some basic diagnostics to
20 A Message Signaled Interrupt is a write from the device to a special
21 address which causes an interrupt to be received by the CPU.
24 in PCI 3.0 to allow each interrupt to be masked individually. The MSI-X
26 per device than MSI and allows interrupts to be independently configured.
39 with an interrupt, which leads to reduced performance for the system as
42 When a device writes data to memory, then raises a pin-based interrupt,
45 bridges). In order to ensure that all the data has arrived in memory,
54 Often drivers have to query the device to find out what event has
57 to be specialised to a different purpose. One possible design gives
[all …]
|
| /linux-4.4.14/sound/pci/hda/ |
| D | Kconfig | 15 Say Y here to include support for Intel "High Definition
19 to choose the appropriate codec options below.
29 Say Y here to support the HDA controller present in NVIDIA
33 present in some NVIDIA Tegra SoCs, used to communicate audio
34 to the HDMI output.
45 Say Y here to build a hwdep interface for HD-audio driver.
52 Say Y here to enable the HD-audio codec re-configuration feature.
53 This adds the sysfs interfaces to allow user to clear the whole
61 Say Y here to build a digital beep interface for HD-audio
62 driver. This interface is used to generate digital beeps.
[all …]
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 5 This document attempts to describe the existing locking rules for
6 JFFS2. It is not expected to remain perfectly up to date, but ought to
13 The alloc_sem is a per-filesystem mutex, used primarily to ensure
23 have been properly linked into the data structures for the inode to
25 nodes to an inode may obsolete old ones, and by holding the alloc_sem
29 don't actually get erased until the write-buffer has been flushed to
33 the alloc_sem is also used to protect the wbuf-related members of the
34 jffs2_sb_info structure. Atomically reading the wbuf_len member to see
48 The reason that the i_sem itself isn't used for this purpose is to
50 before calling a function which may need to allocate space. The
[all …]
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | design-patterns.txt | 6 It is likely that subsystem maintainers will ask driver developers to
7 conform to these design patterns.
17 only be probed() once on a certain system (singletons), it is custom to assume
18 that the device the driver binds to will appear in several instances. This
19 means that the probe() function and all callbacks need to be reentrant.
21 The most common way to achieve this is to use the state container design
42 Of course it is then necessary to always pass this instance of the
43 state around to all functions that need access to the state and its members.
46 pass around a pointer to struct foo like this:
62 This way you always get a pointer back to the correct instance of foo in
[all …]
|
| /linux-4.4.14/security/selinux/ |
| D | Kconfig | 9 If you are unsure how to answer this question, answer N.
17 to be disabled at boot. If this option is selected, SELinux
19 command line. The purpose of this option is to allow a single
20 kernel image to be distributed with SELinux built in, but not
23 If you are unsure how to answer this question, answer N.
32 'selinux', which allows SELinux to be disabled at boot. If this
33 option is set to 0 (zero), the SELinux kernel parameter will
34 default to 0, disabling SELinux at bootup. If this option is
35 set to 1 (one), the SELinux kernel parameter will default to 1,
38 If you are unsure how to answer this question, answer 1.
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8192e/ |
| D | license | 2 "This software program is licensed subject to the GNU General Public License
13 Everyone is permitted to copy and distribute verbatim copies of this license
18 The licenses for most software are designed to take away your freedom to
20 to guarantee your freedom to share and change free software--to make sure
22 to most of the Free Software Foundation's software and to any other program
23 whose authors commit to using it. (Some other Free Software Foundation
25 can apply it to your programs, too.
27 When we speak of free software, we are referring to freedom, not price. Our
28 General Public Licenses are designed to make sure that you have the freedom
29 to distribute copies of free software (and charge for this service if you
[all …]
|
| /linux-4.4.14/sound/soc/blackfin/ |
| D | Kconfig | 7 Say Y or M if you want to add support for codecs attached to
10 You will also need to select the audio interfaces to support below.
20 Say Y if you want to add support for the Analog Devices
29 Say Y if you want to add support for the Analog Devices EVAL-ADAU1701MINIZ
30 board connected to one of the Blackfin evaluation boards like the
39 Say Y if you want to add support for the Analog Devices EVAL-ADAU1373
40 board connected to one of the Blackfin evaluation boards like the
43 Note: This driver assumes that first ADAU1373 DAI is connected to the
52 Say Y if you want to add support for the Analog Devices EVAL-ADAU1X61
53 board connected to one of the Blackfin evaluation boards like the
[all …]
|
| /linux-4.4.14/arch/mn10300/lib/ |
| D | usercopy.c | 15 __generic_copy_to_user(void *to, const void *from, unsigned long n) in __generic_copy_to_user() argument
17 if (access_ok(VERIFY_WRITE, to, n)) in __generic_copy_to_user()
18 __copy_user(to, from, n); in __generic_copy_to_user()
23 __generic_copy_from_user(void *to, const void *from, unsigned long n) in __generic_copy_from_user() argument
26 __copy_user_zeroing(to, from, n); in __generic_copy_from_user()
116 __clear_user(void *to, unsigned long n) in __clear_user() argument
118 __do_clear_user(to, n); in __clear_user()
123 clear_user(void *to, unsigned long n) in clear_user() argument
125 if (access_ok(VERIFY_WRITE, to, n)) in clear_user()
126 __do_clear_user(to, n); in clear_user()
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | compat_signal.c | 64 int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from) in copy_siginfo_to_user32() argument
75 err = __put_user(from->si_signo, &to->si_signo); in copy_siginfo_to_user32()
76 err |= __put_user(from->si_errno, &to->si_errno); in copy_siginfo_to_user32()
77 err |= __put_user((short)from->si_code, &to->si_code); in copy_siginfo_to_user32()
79 err |= __copy_to_user(&to->_sifields._pad, &from->_sifields._pad, SI_PAD_SIZE); in copy_siginfo_to_user32()
84 err |= __put_user(from->si_int, &to->si_int); in copy_siginfo_to_user32()
87 err |= __put_user(from->si_pid, &to->si_pid); in copy_siginfo_to_user32()
88 err |= __put_user(from->si_uid, &to->si_uid); in copy_siginfo_to_user32()
91 err |= __put_user(from->si_pid, &to->si_pid); in copy_siginfo_to_user32()
92 err |= __put_user(from->si_uid, &to->si_uid); in copy_siginfo_to_user32()
[all …]
|
| /linux-4.4.14/Documentation/arm/ |
| D | README | 10 In order to compile ARM Linux, you will need a compiler capable of
11 generating ARM ELF code with GNU extensions. GCC 3.3 is known to be
15 To build ARM Linux natively, you shouldn't have to alter the ARCH = line
20 If you wish to cross-compile, then alter the following lines in the top
30 to
31 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
35 Do a 'make config', followed by 'make Image' to build the kernel
43 Please send patches to the patch system. For more information, see
45 explanation as to what the patch does and why it is needed.
47 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | copying | 6 Everyone is permitted to copy and distribute verbatim copies
11 The licenses for most software are designed to take away your
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
14 software--to make sure the software is free for all its users. This
15 General Public License applies to most of the Free Software
16 Foundation's software and to any other program whose authors commit to
18 the GNU Library General Public License instead.) You can apply it to
21 When we speak of free software, we are referring to freedom, not
22 price. Our General Public Licenses are designed to make sure that you
[all …]
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | COPYING | 6 Everyone is permitted to copy and distribute verbatim copies
11 The licenses for most software are designed to take away your
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
14 software--to make sure the software is free for all its users. This
15 General Public License applies to most of the Free Software
16 Foundation's software and to any other program whose authors commit to
18 the GNU Library General Public License instead.) You can apply it to
21 When we speak of free software, we are referring to freedom, not
22 price. Our General Public Licenses are designed to make sure that you
[all …]
|
| D | INSTALL | 8 unlimited permission to copy, distribute and modify it.
16 instructions specific to this package.
18 The `configure' shell script attempts to guess correct values for
20 those values to create a `Makefile' in each directory of the package.
23 you can run in the future to recreate the current configuration, and a
29 the results of its tests to speed up reconfiguring. Caching is
30 disabled by default to prevent problems with accidental use of stale
33 If you need to do unusual things to compile the package, please try
34 to figure out how `configure' could check whether to do them, and mail
35 diffs or instructions to the address given in the `README' so they can
[all …]
|
| /linux-4.4.14/Documentation/crypto/ |
| D | asymmetric-keys.txt | 19 The "asymmetric" key type is designed to be a container for the keys used in
24 associated with the key and provides operations to describe and destroy it.
29 it would also be possible to provide access to cryptographic hardware (such as
30 a TPM) that might be used to both retain the relevant key and perform
32 merely be an interface to the TPM driver.
35 for extracting information from the blobs of data passed to the instantiation
36 function. The first data parser that recognises the blob gets to set the
40 key, or it may interpret it as a reference to a key held somewhere else in the
49 the opportunity to pre-parse a key and to determine the description the key
52 This can then be used to refer to the key, either by complete match or by
[all …]
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | DSS | 11 currently side by side, you can choose which one to use.
24 - Use DISPC to update any of the outputs
25 - Use CPU to update RFBI or DSI output
30 - Adjusting DSS FCK to find a good pixel clock
31 - Use DSI DPLL to create DSS FCK
46 flexible way to enable non-common multi-display configuration. In addition to
53 well. Hence, it is relevant to update the DSS device driver to provide an audio
57 The audio_enable function is intended to prepare the relevant
59 some IP, enabling companion chips, etc). It is intended to be called before
61 intended to be called after audio_stop.
[all …]
|
| /linux-4.4.14/arch/m32r/lib/ |
| D | usercopy.c | 15 __generic_copy_to_user(void __user *to, const void *from, unsigned long n) in __generic_copy_to_user() argument
18 if (access_ok(VERIFY_WRITE, to, n)) in __generic_copy_to_user()
19 __copy_user(to,from,n); in __generic_copy_to_user()
24 __generic_copy_from_user(void *to, const void __user *from, unsigned long n) in __generic_copy_from_user() argument
26 prefetchw(to); in __generic_copy_from_user()
28 __copy_user_zeroing(to,from,n); in __generic_copy_from_user()
30 memset(to, 0, n); in __generic_copy_from_user()
224 clear_user(void __user *to, unsigned long n) in clear_user() argument
226 if (access_ok(VERIFY_WRITE, to, n)) in clear_user()
227 __do_clear_user(to, n); in clear_user()
[all …]
|
| /linux-4.4.14/arch/arm/mach-omap2/ |
| D | pm44xx.c | 47 const char *to; member
172 {.from = "mpuss_clkdm", .to = "l3_emif_clkdm"},
173 {.from = "mpuss_clkdm", .to = "l3_1_clkdm"},
174 {.from = "mpuss_clkdm", .to = "l3_2_clkdm"},
175 {.from = "ducati_clkdm", .to = "l3_1_clkdm"},
176 {.from = "ducati_clkdm", .to = "l3_2_clkdm"},
181 {.from = "mpu_clkdm", .to = "emif_clkdm"},
192 struct clockdomain *from, *to; in omap4plus_init_static_deps() local
199 to = clkdm_lookup(map->to); in omap4plus_init_static_deps()
200 if (!from || !to) { in omap4plus_init_static_deps()
[all …]
|
| /linux-4.4.14/arch/metag/include/asm/ |
| D | uaccess.h | 200 extern unsigned long __must_check __copy_user_zeroing(void *to,
205 copy_from_user(void *to, const void __user *from, unsigned long n) in copy_from_user() argument
208 return __copy_user_zeroing(to, from, n); in copy_from_user()
212 #define __copy_from_user(to, from, n) __copy_user_zeroing(to, from, n) argument
215 extern unsigned long __must_check __copy_user(void __user *to,
219 static inline unsigned long copy_to_user(void __user *to, const void *from, in copy_to_user() argument
222 if (access_ok(VERIFY_WRITE, to, n)) in copy_to_user()
223 return __copy_user(to, from, n); in copy_to_user()
227 #define __copy_to_user(to, from, n) __copy_user(to, from, n) argument
234 extern unsigned long __must_check __do_clear_user(void __user *to,
[all …]
|
| /linux-4.4.14/arch/xtensa/include/asm/ |
| D | uaccess.h | 392 extern unsigned __xtensa_copy_user(void *to, const void *from, unsigned n);
393 #define __copy_user(to, from, size) __xtensa_copy_user(to, from, size)
397 __generic_copy_from_user_nocheck(void *to, const void *from, unsigned long n)
399 return __copy_user(to, from, n);
403 __generic_copy_to_user_nocheck(void *to, const void *from, unsigned long n)
405 return __copy_user(to, from, n);
409 __generic_copy_to_user(void *to, const void *from, unsigned long n)
412 if (access_ok(VERIFY_WRITE, to, n))
413 return __copy_user(to, from, n);
418 __generic_copy_from_user(void *to, const void *from, unsigned long n)
[all …]
|
| /linux-4.4.14/tools/lguest/ |
| D | lguest.txt | 2 (___()'`; Rusty's Remarkably Unreliable Guide to Lguest
6 Lguest is designed to be a minimal 32-bit x86 hypervisor for the Linux kernel,
7 for Linux developers and users to experiment with virtualization with the
8 minimum of complexity. Nonetheless, it should have sufficient features to
9 make it useful for specific tasks, and, of course, you are encouraged to fork
16 - Simple program to create new guests.
21 - Fun to hack on.
22 - No ABI: being tied to a specific kernel anyway, you can change anything.
27 - The easiest way to run lguest is to use same kernel as guest and host.
28 You can configure them differently, but usually it's easiest not to.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 3 ARM provides idle-state node to define the cpuidle states, as defined in [1].
13 Standby: Standby does a little more in addition to architectural clock gating.
15 clocks. In addition to gating the clocks, QCOM cpus use this instruction as a
16 trigger to execute the SPM state machine. The SPM state machine waits for the
17 interrupt to trigger the core back in to active. This triggers the cache
18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
19 the SPM state machine out of its wait, the next step is to ensure that the
20 cache hierarchy is also out of standby, and then the cpu is allowed to resume
23 configured to execute this state by default and after executing every other
28 voltage may be reduced to the minimum value needed to keep the processor
[all …]
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 5 assigned by the kernel to all the virtual consoles during the boot process.
7 to exist. The system driver is persistent and it can never be unloaded, though
10 The second type has to be explicitly loaded and unloaded. This will be called
20 Modular drivers, from the programmer's point of view, has to call:
22 do_take_over_console() - load and bind driver to console layer
32 system which are named vtcon<n> where <n> is an integer from 0 to 15. Thus:
45 read, or acts to bind or unbind the driver to the virtual consoles
46 when written to. The possible values are:
49 to unbind
51 1 - means the driver is bound and if echo'ed, commands the driver to
[all …]
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | network_protocol.txt | 13 __u64 id; /* Object ID to operate on. Used for feedback.*/
25 @cmd - command number, which specifies command to be processed. Following
30 NETFS_WRITE_PAGE, /* Write data page to the server */
46 @ext - external flags. Used by different commands to specify some extra arguments
62 This command is used to sync content of the remote dir to the client.
64 @ext - length of the path to object.
66 @id - local inode number of the directory to read.
71 This command is used to read data from remote server.
76 @size - number of bytes to read plus length of the path to object.
81 Used to create object.
[all …]
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | Opti | 3 Note: parts of this README file apply also to other
7 added to the sound driver after Linux-2.1.91 was out.
14 Usually you do not need to set jumpers, etc. The sound driver
41 For the OPTi 931 you can answer 'n' to:
44 need to answer 'm' to the above question. In that case you will
45 also need to answer 'm' to:
52 In most systems with a PnP BIOS you do not need to use isapnp. The
54 to pick up the card and continue initialization.
56 If that fails, or if you have other PnP cards, you need to use isapnp
57 to initialize the card.
[all …]
|
| /linux-4.4.14/drivers/power/ |
| D | Kconfig | 4 Say Y here to enable power supply class support. This allows
14 Say Y here to enable debugging messages for power supply class
21 Say Y here to enable generic power driver for PDAs and phones with
22 one or two external power supplies (AC/USB) connected to main and
29 Say Y here to enable support APM status emulation using
36 Say Y here to enable support for the generic battery driver
37 which uses IIO framework to read adc.
43 Say Y here to enable support for the battery charger in the Maxim
50 Say Y here to enable support for the backup battery charger
57 Say Y here to enable support for the power management unit
[all …]
|
| /linux-4.4.14/drivers/net/irda/ |
| D | Kconfig | 10 Say Y here if you want to build support for the IrTTY line
12 will be called irtty-sir. IrTTY makes it possible to use Linux's
15 to this option. Using IrTTY will however limit the speed of the
16 connection to 115200 bps (IrDA SIR mode).
25 Say Y here if your want to enable SIR function on Blackfin UART
33 Note that you need to turn off one of the serial drivers for SIR
34 to use that UART.
72 Say Y here if your want to enable SIR function on SuperH UART
81 Say Y here if you have an infrared device that connects to your
83 or M to the driver for your particular dongle below.
[all …]
|