| /Documentation/devicetree/bindings/timer/ |
| D | renesas,cmt.txt | 9 position of the channel in the CMT and don't match the channel numbers in the
15 - "renesas,r8a73a4-cmt0" for the 32-bit CMT0 device included in r8a73a4.
16 - "renesas,r8a73a4-cmt1" for the 48-bit CMT1 device included in r8a73a4.
17 - "renesas,r8a7740-cmt0" for the 32-bit CMT0 device included in r8a7740.
18 - "renesas,r8a7740-cmt1" for the 48-bit CMT1 device included in r8a7740.
19 - "renesas,r8a7740-cmt2" for the 32-bit CMT2 device included in r8a7740.
20 - "renesas,r8a7740-cmt3" for the 32-bit CMT3 device included in r8a7740.
21 - "renesas,r8a7740-cmt4" for the 32-bit CMT4 device included in r8a7740.
22 - "renesas,r8a7743-cmt0" for the 32-bit CMT0 device included in r8a7743.
23 - "renesas,r8a7743-cmt1" for the 48-bit CMT1 device included in r8a7743.
[all …]
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 10 mainline kernel in 2.6.20 although it is identical to the stats from version
11 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
16 In version 14 of schedstat, there is at least one level of domain
18 domain. Domains have no particular names in this implementation, but
23 field in the domain stats is a bit map indicating which cpus are affected
28 the change in the counters at each subsequent observation. A perl script
34 reason to change versions is changes in the output format. For those wishing
47 2) This field is a legacy array expiration count field used in the O(1)
59 7) sum of all time spent running by tasks on this processor (in jiffies)
60 8) sum of all time spent waiting to run by tasks on this processor (in
[all …]
|
| /Documentation/networking/ |
| D | altera_tse.txt | 16 the maintainer of this driver, found in MAINTAINERS.
30 The SGDMA component is to be deprecated in the near future (over the next 1-2
31 years as of this writing in early 2014) in favor of the MSGDMA component.
32 SGDMA support is included for existing designs and reference in case a
47 tested for 1Gbps. This support will be added in a future maintenance update.
56 dma_rx_num: Number of descriptors in the RX list (default is 64);
57 dma_tx_num: Number of descriptors in the TX list (default is 64).
60 Driver parameters can be also passed in command line by using:
70 completion in the context of the interrupt handling chain by recycling
85 for transmit operations, but will be added in a future maintenance release.
[all …]
|
| D | strparser.txt | 8 parser works in conjunction with an upper layer in the kernel to provide
13 The strparser works in one of two modes: receive callback or general
16 In receive callback mode, the strparser is called from the data_ready
20 In general mode, a sequence of skbs are fed to strparser from an
31 parsing (e.g. BPF parsing in case of KCM), and a rcv_msg function
43 callback mode; in general mode this is set to NULL. Callbacks
72 strp_process is called in general mode for a stream parser to
100 in the stream. The upper layer must implement this function. It
102 next application layer message in the stream.
104 The skb->cb in the input skb is a struct strp_msg. Only
[all …]
|
| D | checksum-offloads.rst | 11 This document describes a set of techniques in the Linux networking stack to
29 The interface for offloading a transmit checksum to a device is explained in
30 detail in comments near the top of include/linux/skbuff.h.
32 In brief, it allows to request the device fill in a single ones-complement
35 'IP-style' checksum) from csum_start to the end of the packet, and fill in the
39 the checksum field is included in the checksum computation, thus it can be used
44 encapsulation is used, the packet may have multiple checksum fields in
52 No offloading of the IP header checksum is performed; it is always done in
54 in cache, so summing it isn't expensive. It's also rather short.
61 A driver declares its offload capabilities in netdev->hw_features; see
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | dwc2.txt | 6 - brcm,bcm2835-usb: The DWC2 USB controller instance in the BCM2835 SoC.
7 - hisilicon,hi6220-usb: The DWC2 USB controller instance in the hi6220 SoC.
8 - rockchip,rk3066-usb: The DWC2 USB controller instance in the rk3066 Soc;
12 - "lantiq,arx100-usb": The DWC2 USB controller instance in Lantiq ARX SoCs;
13 - "lantiq,xrx200-usb": The DWC2 USB controller instance in Lantiq XRX SoCs;
14 - "amlogic,meson8-usb": The DWC2 USB controller instance in Amlogic Meson8 SoCs;
15 - "amlogic,meson8b-usb": The DWC2 USB controller instance in Amlogic Meson8b SoCs;
16 - "amlogic,meson-gxbb-usb": The DWC2 USB controller instance in Amlogic S905 SoCs;
17 - "amlogic,meson-g12a-usb": The DWC2 USB controller instance in Amlogic G12A SoCs;
18 - "amcc,dwc-otg": The DWC2 USB controller instance in AMCC Canyonlands 460EX SoCs;
[all …]
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 1 Rules on how to access information in sysfs
10 To minimize the risk of breaking users of sysfs, which are in most cases
24 implementation details in its own API. Therefore it is not better than
26 Also, it is not actively maintained, in the sense of reflecting the
29 violates many of the rules in this document.
40 interfaces, and such that you can rely on in userspace. Everything is
43 applications that look for devices in sysfs.
49 - identical to the DEVPATH value in the event sent from the kernel
51 - the unique key to the device at that point in time
59 - using or exposing symlink values as elements in a devpath string
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 29 registered in the userfaultfd that allows userland to efficiently
31 memory in the background
34 management of mremap/mprotect is that the userfaults in all their
35 operations never involve heavyweight structures like vmas (in fact the
69 virtual memory areas, UFFD_FEATURE_MISSING_HUGETLBFS will be set in
76 or shared memory need to set the corresponding flag in
81 UFFD_FEATURE_EVENT_* bits set. These events are described in more
82 detail below in "Non-cooperative userfaultfd" section.
85 be invoked (if present in the returned uffdio_api.ioctls bitmask) to
86 register a memory range in the userfaultfd by setting the
[all …]
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 9 two languages in one. One language describes dependency graphs consisting of
32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
40 The macro language in Kconfig processes the source file into the following
47 dependency as explained in kconfig-language.txt.
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
54 variable is expanded "in place" to yield a text string that may then be
55 expanded further. To get the value of a variable, enclose the variable name in
57 a syntax error. The curly brace form as in ${CC} is not supported either.
68 expanding it in any way. Instead, the expansion is performed when the variable
76 The variable reference can take parameters, in the following form::
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | pixfmt-intro.rst | 14 In order to exchange images between drivers and applications, it is
18 image data formats in V4L2.
21 formats are possible. In that case the application may depend on a codec
23 data can still be stored and retrieved in the proprietary format. For
25 Applications can still capture and save the data in the compressed
34 are always arranged in memory from left to right, and from top to
35 bottom. The first byte of data in the image buffer is always for the
44 In V4L2 each format has an identifier which looks like ``PIX_FMT_XXX``,
45 defined in the :ref:`videodev2.h <videodev>` header file. These
48 listed below, however they are not the same as those used in the Windows
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 15 One of them is based on using global low-power states of the whole system in
19 and the system stays in it until a special signal is received from one of
20 designated devices, triggering a transition to the ``working state`` in which
27 components of the system, as needed, in the working state. In consequence, if
28 this strategy is in use, the working state of the system usually does not
30 a metastate covering a range of different power states of the system in which
31 the individual components of it can be either ``active`` (in use) or
32 ``inactive`` (idle). If they are active, they have to be in power states
33 allowing them to process data and to be accessed by software. In turn, if they
34 are inactive, ideally, they should be in low-power states in which they may not
[all …]
|
| D | cpuidle.rst | 19 Modern processors are generally able to enter states in which the execution of
23 Since part of the processor hardware is not used in idle states, entering them
24 generally allows power drawn by the processor to be reduced and, in consequence,
35 work in the system). In its view, CPUs are *logical* units. That is, they need
37 software as individual single-core processors. In other words, a CPU is an
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
49 work physically in parallel with each other, so if each of them executes only
51 time. The entire cores are CPUs in that case and if the hardware is asked to
52 enter an idle state, that applies to the core that asked for it in the first
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 10 The _DSD (Device Specific Data) configuration object, introduced in ACPI 5.1,
12 namespace. In principle, the format of the data may be arbitrary, but it has to
15 the ACPI subsystem in the Linux kernel which automatically processes the data
22 In the ACPI _DSD context it is an element of the sub-package following the
23 generic Device Properties UUID in the _DSD return package as specified in the
27 that can be returned by _DSD in the Device Properties UUID sub-package for a
31 like a device. In the ACPI _DSD context it is the set of all properties that
32 can be returned in the Device Properties UUID sub-package for the device in
38 representation of property subsets is via the mechanism specified in the
51 _DSD properties are intended to be used in addition to, and not instead of, the
[all …]
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 8 Each FEK is in turn encrypted with a File Encryption Key Encryption Key (FEKEK)
9 either in kernel space or in user space with a daemon called 'ecryptfsd'. In
11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
12 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
17 FEK decryption is called authentication token and, currently, can be stored in a
18 kernel key of the 'user' type, inserted in the user's session specific keyring
23 format 'ecryptfs' in order to be used in conjunction with the eCryptfs
25 authentication token in its payload with a FEKEK randomly generated by the
28 In order to avoid known-plaintext attacks, the datablob obtained through
30 authentication token, which content is well known, but only the FEKEK in
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | renesas,mmcif.txt | 3 This file documents differences between the core properties in mmc.txt
11 - "renesas,mmcif-r7s72100" for the MMCIF found in r7s72100 SoCs
12 - "renesas,mmcif-r8a73a4" for the MMCIF found in r8a73a4 SoCs
13 - "renesas,mmcif-r8a7740" for the MMCIF found in r8a7740 SoCs
14 - "renesas,mmcif-r8a7743" for the MMCIF found in r8a7743 SoCs
15 - "renesas,mmcif-r8a7744" for the MMCIF found in r8a7744 SoCs
16 - "renesas,mmcif-r8a7745" for the MMCIF found in r8a7745 SoCs
17 - "renesas,mmcif-r8a7778" for the MMCIF found in r8a7778 SoCs
18 - "renesas,mmcif-r8a7790" for the MMCIF found in r8a7790 SoCs
19 - "renesas,mmcif-r8a7791" for the MMCIF found in r8a7791 SoCs
[all …]
|
| /Documentation/ABI/ |
| D | README | 4 interfaces should be used by userspace programs in different ways.
7 different subdirectories in this location. Interfaces may change levels
25 errors or security problems are found in them. Userspace
35 This directory documents interfaces that are still remaining in
36 the kernel, but are marked to be removed at some later point in
44 Every file in these directories will contain the following information:
48 KernelVersion: Kernel version this feature first showed up in.
52 it changes. This is very important for interfaces in
55 break in ways that are unacceptable. It is also
57 sure they are working in a proper way and do not need to
[all …]
|
| /Documentation/arm/ |
| D | booting.rst | 11 In order to boot ARM Linux, you require a boot loader, which is a small
36 kernel will use for volatile data storage in the system. It performs
37 this in a machine dependent manner. (It may use internal algorithms
39 the RAM in the machine, or any other method the boot loader designer
58 serial format options as described in
76 should be passed to the kernel in register r1.
92 boot data is passed to the kernel in register r2.
103 Any number of tags can be placed in the list. It is undefined
105 previous tag, or whether it replaces the information in its
120 The tagged list should be stored in system RAM.
[all …]
|
| D | cluster-pm-race-avoidance.rst | 12 algorithm in use.
18 In a system containing multiple CPUs, it is desirable to have the
22 In a system containing multiple clusters of CPUs, it is also desirable
28 means that we need some coordination in order to ensure that critical
37 methods of coordination are required in order to guarantee safe
40 The mechanism presented in this document describes a coherent memory
77 level. A CPU in this state is not necessarily being used
86 Each CPU has one of these states assigned to it at any point in time.
87 The CPU states are described in the "CPU state" section, below.
91 to introduce additional states in order to avoid races between different
[all …]
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 2 Tracepoints in ALSA
8 Tracepoints in ALSA PCM core
30 In a design of ALSA PCM core, data transmission is abstracted as PCM substream.
33 substream. In this procedure, PCM hardware parameters are decided by
37 The parameters are described in :c:type:`struct snd_pcm_hw_params`. This
49 Configurable. This type of parameter is described in
57 Configurable. This type of parameter is described in
80 Read-only. After returning from ioctl(2), buffer in user space for
90 Read-only. This value represents available bit width in MSB side of
93 it. Else, zero. But this behaviour depends on implementations in driver
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt2701-cs42448.txt | 11 - i2s1-in-sel-gpio1, i2s1-in-sel-gpio2: Should specify two gpio pins to
12 control I2S1-in mux.
31 "AIN2L", "Tuner In",
32 "AIN2R", "Tuner In",
33 "AIN3L", "Satellite Tuner In",
34 "AIN3R", "Satellite Tuner In",
35 "AIN3L", "AUX In",
36 "AIN3R", "AUX In";
41 i2s1-in-sel-gpio1 = <&pio 53 0>;
42 i2s1-in-sel-gpio2 = <&pio 54 0>;
|
| D | img,i2s-in.txt | 5 - compatible : Compatible list, must contain "img,i2s-in"
11 - clocks : Contains an entry for each entry in clock-names
16 - dmas: Contains an entry for each entry in dma-names.
21 - img,i2s-channels : Number of I2S channels instantiated in the I2S in block
25 - interrupts : Contains the I2S in interrupts. Depending on
29 in ascending channel order
31 - resets: Contains a phandle to the I2S in reset signal
37 i2s_in: i2s-in@18100800 {
38 compatible = "img,i2s-in";
|
| /Documentation/input/devices/ |
| D | edt-ft5x06.rst | 6 focaltec ft5x06 devices, since they contain vendor-specific firmware. In
18 allows setting the "click"-threshold in the range from 0 to 80.
21 allows setting the sensitivity in the range from 0 to 31. Note that
25 allows setting the edge compensation in the range from 0 to 31.
28 allows setting the report rate in the range from 3 to 14.
31 For debugging purposes the driver provides a few files in the debug
32 filesystem (if available in the kernel). In /sys/kernel/debug/edt_ft5x06
36 (readonly) contains the number of sensor fields in X- and
41 mode" by writing "1" or "0" to it. In factory mode (1) it is
42 possible to get the raw data from the sensor. Note that in factory
[all …]
|
| /Documentation/hid/ |
| D | hiddev.rst | 8 In addition to the normal input type HID devices, USB also uses the
29 In addition, other subsystems (apart from USB) can potentially feed
67 This description should be read in conjunction with the HID
75 each of which can have one or more "usages". In the hid-core,
85 the report. In its basic mode, the hiddev will make these individual
129 also returns the level the collection lives in the hierarchy.
130 The user passes in a hiddev_collection_info struct with the index
131 field set to the index that should be returned. The ioctl fills in
143 Gets a string descriptor from the device. The caller must fill in the
152 changes. Note that the use of this ioctl is unnecessary in general,
[all …]
|
| /Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 11 preallocated for application use. These huge pages are instantiated in a
18 done with a simple check in the code at mmap() time to determine if there
19 were enough free huge pages to cover the mapping. Like most things in the
22 available for page faults in that mapping. The description below attempts to
23 describe how huge page reserve processing is done in the v4.10 kernel.
52 There is one reserve map for each huge page mapping in the system.
64 region in the reserv_map may indicate reservations exist for the
67 These are stored in the bottom bits of the reservation map pointer.
79 details will be discussed in the "Freeing huge pages" section.
96 by files in the hugetlbfs filesystem, the hugetlbfs code ensures each inode
[all …]
|
| /Documentation/admin-guide/sysctl/ |
| D | user.rst | 11 This file contains the documentation for the sysctl files in
14 The files in this directory can be used to override the default
22 no program in normal operation should run into these limits.
25 the user in the user namespace who created the object and
26 verified to be below the per user limit in that user namespace.
30 in (user namespaces can be nested) and verified to be below the per user
31 limits in the user namespaces of those users.
36 Currently, these files are in /proc/sys/user:
41 The maximum number of cgroup namespaces that any user in the current
47 The maximum number of ipc namespaces that any user in the current
[all …]
|