| /Linux-v5.4/fs/nls/ |
| D | Kconfig | 44 native language character sets. These character sets are stored
46 codepage if you want to be able to read/write these filenames on
56 native language character sets. These character sets are stored
58 codepage if you want to be able to read/write these filenames on
68 native language character sets. These character sets are stored
70 codepage if you want to be able to read/write these filenames on
81 native language character sets. These character sets are stored in
83 codepage if you want to be able to read/write these filenames on
97 native language character sets. These character sets are stored in
99 codepage if you want to be able to read/write these filenames on
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /Linux-v5.4/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
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
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /Linux-v5.4/arch/h8300/include/asm/ |
| D | pgtable.h | 8 #define PAGE_NONE __pgprot(0) /* these mean nothing to NO_MM */
9 #define PAGE_SHARED __pgprot(0) /* these mean nothing to NO_MM */
10 #define PAGE_COPY __pgprot(0) /* these mean nothing to NO_MM */
11 #define PAGE_READONLY __pgprot(0) /* these mean nothing to NO_MM */
12 #define PAGE_KERNEL __pgprot(0) /* these mean nothing to NO_MM */
31 * These would be in other places but having them here reduces the diffs.
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | overview.txt | 12 devices. In some cases there is considerable overlap between these and
23 * Event chrdevs. These are similar to input in that they provide a
30 Note: A given device may have one or more event channel. These events are
34 fifo / ring buffers on the sensor chip. These greatly reduce the load
42 external signal (trigger). These triggers might be a data ready
45 capture or reading from a number of sensors. These triggers are
|
| /Linux-v5.4/include/linux/sunrpc/ |
| D | metrics.h | 11 * These statistics are not for detailed problem diagnosis, but simply
14 * These counters are not meant to be human-readable, but are meant to be
23 * arrays per-CPU because these counters are always modified behind locks.
39 * These counters give an idea about how many request
51 * These count how many bytes are sent and received for a
53 * particular procedure is putting on the network. These
71 * These statuses usually indicate error conditions.
|
| /Linux-v5.4/arch/mips/include/uapi/asm/ |
| D | mman.h | 13 * Protections are chosen from these bits, OR'd together. The
40 /* These are linux-specific */
75 #define MADV_WILLNEED 3 /* will need these pages */
76 #define MADV_DONTNEED 4 /* don't need these pages */
78 /* common parameters: try to keep these consistent across architectures */
80 #define MADV_REMOVE 9 /* remove these pages & resources */
98 #define MADV_COLD 20 /* deactivate these pages */
99 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /Linux-v5.4/Documentation/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
85 user_pac_address_keys and struct user_pac_generic_keys). These can be
94 requesting these two separate cpu features to be enabled. The current KVM
96 these userspace flags are checked before enabling pointer authentication.
98 if support is added in the future to allow these two features to be
105 Additionally, when these vcpu feature flags are not set then KVM will
|
| /Linux-v5.4/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /Linux-v5.4/drivers/scsi/arm/ |
| D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
51 Acorn system with one of these, say Y. If unsure, say N.
58 system with one of these, say Y, otherwise say N.
65 you have one of these, say Y. If unsure, say N.
76 Acorn system with one of these, say Y. If unsure, say N.
84 system with one of these, say Y. If unsure, say N.
|
| /Linux-v5.4/arch/xtensa/include/uapi/asm/ |
| D | mman.h | 19 * Protections are chosen from these bits, OR'd together. The
47 /* These are linux-specific */
84 #define MADV_WILLNEED 3 /* will need these pages */
85 #define MADV_DONTNEED 4 /* don't need these pages */
87 /* common parameters: try to keep these consistent across architectures */
89 #define MADV_REMOVE 9 /* remove these pages & resources */
106 #define MADV_COLD 20 /* deactivate these pages */
107 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /Linux-v5.4/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /Linux-v5.4/Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
87 What remains are variables that are updated rarely (e.g. GDT). These
98 access userspace memory without explicit expectation to do so. These
[all …]
|
| /Linux-v5.4/Documentation/arm/nwfpe/ |
| D | netwinder-fpe.rst | 28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
96 to the ARM manual. The manual notes these are defined only for single
110 These are fully implemented.
116 These are fully implemented.
121 These are implemented. URD is implemented using the same code as the RND
141 These are not implemented. They are not currently issued by the compiler,
[all …]
|
| /Linux-v5.4/Documentation/x86/ |
| D | intel-iommu.rst | 30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
49 but these are not global address spaces, but separate for each domain.
|
| /Linux-v5.4/arch/x86/kernel/ |
| D | irqinit.c | 33 * (these are usually mapped to vectors 0x30-0x3f)
37 * The IO-APIC gives us many more interrupt sources. Most of these
41 * of these. Plus, more powerful systems might have more than 64
44 * (these are usually mapped into the 0x30-0xff vector range)
85 * If these IRQ's are handled by legacy interrupt-controllers like PIC, in init_IRQ()
87 * these IRQ's are handled by more mordern controllers like IO-APIC, in init_IRQ()
|
| /Linux-v5.4/include/linux/ |
| D | nfs_iostat.h | 10 * Generally these are not for detailed problem diagnosis, but
13 * These counters are not meant to be human-readable, but are meant
40 * These counters give a view of the data throughput into and out
46 * These counters can also help characterize which access methods
55 * These count the number of pages read or written via nfs_readpage(),
77 * These counters provide a low-overhead way of monitoring client
|
| /Linux-v5.4/include/uapi/asm-generic/ |
| D | mman-common.h | 46 #define MADV_WILLNEED 3 /* will need these pages */
47 #define MADV_DONTNEED 4 /* don't need these pages */
49 /* common parameters: try to keep these consistent across architectures */
51 #define MADV_REMOVE 9 /* remove these pages & resources */
70 #define MADV_COLD 20 /* deactivate these pages */
71 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra194-pinmux.txt | 14 subnodes. Each of these subnodes represents some desired configuration for a
25 group. Valid values for these names are listed below.
60 These correspond to Tegra PADCTL_* (pinmux) registers.
64 These correspond to Tegra PADCTL_* (pinmux) registers. Any property
71 These registers controls a single pin for which a mux group exists.
83 these pins here.
|
| /Linux-v5.4/tools/include/uapi/asm-generic/ |
| D | mman-common.h | 46 #define MADV_WILLNEED 3 /* will need these pages */
47 #define MADV_DONTNEED 4 /* don't need these pages */
49 /* common parameters: try to keep these consistent across architectures */
51 #define MADV_REMOVE 9 /* remove these pages & resources */
70 #define MADV_COLD 20 /* deactivate these pages */
71 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /Linux-v5.4/arch/alpha/include/uapi/asm/ |
| D | mman.h | 23 /* These are linux-specific */
48 #define MADV_WILLNEED 3 /* will need these pages */
50 #define MADV_DONTNEED 6 /* don't need these pages */
54 #define MADV_REMOVE 9 /* remove these pages & resources */
71 #define MADV_COLD 20 /* deactivate these pages */
72 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /Linux-v5.4/Documentation/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-dbg-g-register.rst | 50 For driver debugging purposes these ioctls allow test applications to
57 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
81 These ioctls are optional, not all drivers may support them. However
82 when a driver supports these ioctls it must also support
84 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
90 We recommended the v4l2-dbg utility over calling these ioctls directly.
171 these ioctls.
|
| /Linux-v5.4/Documentation/i2c/ |
| D | fault-codes.rst | 21 In short, your I2C driver code may need to know these codes in order
28 These are returned as negative numbers from most calls, with zero or
30 numbers associated with these symbols differ between architectures,
34 codes that may be returned, and other cases where these codes should
35 be returned. However, drivers should not return other codes for these
58 on these as the only way to detect incorrect data transfers.
109 transaction it can't. (These limitations can't be seen in
|
| /Linux-v5.4/Documentation/RCU/ |
| D | rcu.rst | 25 barriers. The fact that these operations are quite expensive
35 Therefore, as soon as a CPU is seen passing through any of these
44 counters. These counters allow limited types of blocking within
47 critical sections. These variants of RCU detect grace periods
48 by sampling these counters.
79 Of these, one was allowed to lapse by the assignee, and the
|
