| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 20 The file system provides a name space similar to posix shared memory or
22 can use spu_create(2) to establish SPU contexts in the spufs root.
24 Every SPU context is represented by a directory containing a predefined
44 tem calls like read(2) or write(2), but often support only a subset of
49 All files that support the read(2) operation also support readv(2) and
50 all files that support the write(2) operation also support writev(2).
51 All files support the access(2) and stat(2) family of operations, but
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
64 accessed like a regular shared memory file and contains both code and
68 read(2), pread(2), write(2), pwrite(2), lseek(2)
[all …]
|
| /Documentation/filesystems/ |
| D | configfs.rst | 16 configfs is a ram-based filesystem that provides the converse of
17 sysfs's functionality. Where sysfs is a filesystem-based view of
18 kernel objects, configfs is a filesystem-based manager of kernel
21 With sysfs, an object is created in kernel (for example, when a device
24 readdir(3)/read(2). It may allow some attributes to be modified via
25 write(2). The important point is that the object is created and
27 representation, and sysfs is merely a window on all this.
29 A configfs config_item is created via an explicit userspace operation:
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
31 mkdir(2) time, and can be read or modified via read(2) and write(2).
[all …]
|
| D | hpfs.rst | 33 - there is a list of text extensions (I thing it's better to not convert
49 When to mark filesystem dirty so that OS/2 checks it.
57 one hour more, than under os/2, use timeshift=-3600.
63 As in OS/2, filenames are case insensitive. However, shell thinks that names
64 are case sensitive, so for example when you create a file FOO, you can use
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
71 well. If you create 'a. ...', the file 'a' will be created, but you can still
72 access it under names 'a.', 'a..', 'a . . . ' etc.
78 On HPFS partitions, OS/2 can associate to each file a special information called
81 variable length. OS/2 stores window and icon positions and file types there. So
[all …]
|
| D | dlmfs.rst | 8 A minimal DLM userspace interface implemented via a virtual file
30 DLM implementations should not be a major issue.
48 place. Please download ocfs2-tools from the above url and configure a
51 You'll want to start heartbeating on a volume which all the nodes in
69 system calls and presents a more traditional locking api.
71 dlmfs handles lock caching automatically for the user, so a lock
77 Also supported is a Trylock operation.
82 Lock value blocks can be read and written to a resource via read(2)
83 and write(2) against the fd obtained via your open(2) call. The
88 mkdir(2) signals dlmfs to join a domain (which will have the same name
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-service-time.rst | 5 dm-service-time is a path selector module for device-mapper targets,
6 which selects a path with the shortest estimated service time for
10 of in-flight I/Os on a path with the performance value of the path.
11 The performance value is a relative throughput value among all paths
12 in a path-group, and it can be specified as a table argument.
30 other paths having a positive value are available.
36 'A' if the path is active, 'F' if the path is failed.
51 Basically, dm-service-time selects a path having minimum service time
62 2. If the paths have the same 'in-flight-size', skip the division
78 In case that 2 paths (sda and sdb) are used with repeat_count == 128
[all …]
|
| D | switch.rst | 5 The device-mapper switch target creates a device that supports an
6 arbitrary mapping of fixed-size regions of I/O across a fixed set of
8 dynamically by sending the target a message.
10 It maps I/O to underlying block devices efficiently when there is a large
12 that would allow for a compact representation of the mapping such as
18 Dell EqualLogic and some other iSCSI storage arrays use a distributed
20 consists of a number of distinct storage arrays ("members") each having
21 independent controllers, disk storage and network adapters. When a LUN
24 The storage group exposes a single target discovery portal, no matter
26 session is connected to an eth port on a single member. Data to a LUN
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
22 A combined node shall be used instead of a device node and an interface node
23 for devices of class 0 or 9 (hub) with a single configuration and a single
26 A "hub node" is a combined node or an interface node that represents a USB
31 pattern: "^usb[0-9a-f]{1,4},[0-9a-f]{1,4}$"
37 but a device adhering to this binding may leave out all except
47 should be 2 for device nodes with interface nodes.
48 enum: [1, 2]
54 "^interface@[0-9a-f]{1,2}(,[0-9a-f]{1,2})$":
62 pattern: "^usbif[0-9a-f]{1,4},[0-9a-f]{1,4}.config[0-9a-f]{1,2}.[0-9a-f]{1,2}$"
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-rgb.rst | 9 These formats encode each pixel as a triplet of RGB values. They are packed
12 bits required to store a pixel is not aligned to a byte boundary, the data is
20 or a permutation thereof, collectively referred to as alpha formats) depend on
24 a meaningful value. Otherwise, when the device doesn't capture an alpha channel
25 but can set the alpha bit to a user-configurable value, the
28 the value specified by that control. Otherwise a corresponding format without
34 filled with meaningful values by applications. Otherwise a corresponding format
38 Formats that contain padding bits are named XRGB (or a permutation thereof).
44 - In all the tables that follow, bit 7 is the most significant bit in a byte.
46 respectively. 'a' denotes bits of the alpha component (if supported by the
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | xlnx,sd-fec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
14 The Soft Decision Forward Error Correction (SDFEC) Engine is a Hard IP block
16 The LDPC decode & encode functionality is capable of covering a range of
29 minItems: 2
44 - minItems: 2
69 a codeword-by-codeword basis. The Turbo code decoding is required by LTE
77 Configures the DIN AXI stream where a value of 1
78 configures a width of "1x128b", 2 a width of "2x128b" and 4 configures a width
81 enum: [ 1, 2, 4 ]
85 A value 0 indicates that the DIN_WORDS interface is
[all …]
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 15 Some Armv9 SoCs suffer from a big.LITTLE misfeature where only a subset
17 a system, Linux by default treats the asymmetry as a "mismatch" and
19 ``execve(2)`` of 32-bit ELF binaries, with the latter returning
20 ``-ENOEXEC``. If the mismatch is detected during late onlining of a
50 way as on a homogeneous system, with a few key differences relating to
65 ``execve(2)``
68 On a homogeneous system, the CPU affinity of a task is preserved across
69 ``execve(2)``. This is not always possible on an asymmetric system,
76 mask is saved. This saved mask is inherited over ``fork(2)`` and
77 preserved across ``execve(2)`` of 32-bit programs.
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | blocks.rst | 6 ext4 allocates storage space in units of “blocks”. A block is a group of
8 integral power of 2. Blocks are in turn grouped into larger units called
11 page size (i.e. 64KiB blocks on a i386 which only has 4KiB memory
12 pages). By default a filesystem can contain 2^32 blocks; if the '64bit'
13 feature is enabled, then a filesystem can have 2^64 blocks. The location
25 - 2KiB
29 - 2^32
30 - 2^32
31 - 2^32
32 - 2^32
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-port.rst | 9 ``devlink-port`` is a port that exists on the device. It has a logically
10 separate ingress/egress point of the device. A devlink port can be any one
11 of many flavours. A devlink port flavour along with port attributes
12 describe what a port represents.
14 A device driver that intends to publish a devlink port sets the
28 - This indicates a DSA interconnect port.
30 - This indicates a CPU port applicable only to DSA.
32 - This indicates an eswitch port representing a port of PCI
35 - This indicates an eswitch port representing a port of PCI
38 - This indicates an eswitch port representing a port of PCI
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tlv320adcx140.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause)
16 converter (ADC) with analog inputs supporting up to 2V RMS. The TLV320ADCX140
17 family supports line and microphone Inputs, and offers a programmable
61 2 - Set VREF to 1.375V
63 enum: [0, 1, 2]
75 PDMIN1 - PDMCLK latching edge used for channel 1 and 2 data
93 1 - GPIX is configured as a general-purpose input (GPI)
94 2 - GPIX is configured as a master clock input (MCLK)
96 4 - GPIX is configured as a PDM data input for channel 1 and channel
98 5 - GPIX is configured as a PDM data input for channel 3 and channel
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | brcm,iproc-clocks.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
19 ASIU clocks are a special case. These clocks are derived directly from the
60 most iProc PLLs, this is an onboard crystal with a fixed rate.
109 crystal N/A N/A N/A
111 armpll crystal N/A N/A
115 pwm crystal (ASIU) 2 BCM_CYGNUS_ASIU_PWM_CLK
119 250mhz genpll 2 BCM_CYGNUS_GENPLL_250MHZ_CLK
127 ddr_phy lcpll0 2 BCM_CYGNUS_LCPLL0_DDR_PHY_CLK
135 ch1_lcd mipipll 2 BCM_CYGNUS_MIPIPLL_CH1_LCD
143 ch1_audio audiopll 2 BCM_CYGNUS_AUDIOPLL_CH1
[all …]
|
| /Documentation/mm/ |
| D | mmu_notifier.rst | 4 When clearing a pte/pmd we are given a choice to notify the event through
9 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
10 process virtual address space). There is only 2 cases when you need to notify
11 those secondary TLB while holding page table lock when clearing a pte/pmd:
13 A) page backing address is free before mmu_notifier_invalidate_range_end()
14 B) a page table entry is updated to point to a new page (COW, write fault
17 Case A is obvious you do not want to take the risk for the device to write to
18 a page that might now be used by some completely different task.
27 If clearing the page table entry is not followed by a notify before setting
31 Consider the following scenario (device use a feature similar to ATS/PASID):
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 The Arm Message Handling Unit (MHU) Version 2 is a mailbox controller that has
20 be written to or read from. If a pair of MHU controllers is implemented
25 a "receiver" mailbox, otherwise a "sender".
37 bits in a channel window. A channel window can support up to 32 doorbells
39 may be transmitted through a shared memory region, wherein the MHU is used
43 # We need a select here so we don't match all nodes with 'arm,primecell'
90 This property allows a platform to describe how these channel windows are
96 The first field of a tuple signifies the transfer protocol, 0 is reserved
98 Using any other value in the first field of a tuple makes it invalid.
[all …]
|
| /Documentation/gpu/ |
| D | afbc.rst | 7 AFBC is a proprietary lossless image compression protocol and format.
21 AFBC streams can contain several components - where a component
22 corresponds to a color channel (i.e. R, G, B, X, A, Y, Cb, Cr).
33 * Component 2: B
44 * Component 2: B(8)
45 * Component 3: A(8)
51 * Component 2: B(8)
56 * Component 1: Cb(8, 2x1 subsampled)
57 * Component 2: Cr(8, 2x1 subsampled)
67 * Component 2: B(8)
[all …]
|
| /Documentation/devicetree/bindings/soundwire/ |
| D | soundwire-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 SoundWire busses can be described with a node for the SoundWire controller
15 device and a set of child nodes for each SoundWire slave on the bus.
22 const: 2
28 "^.*@[0-9a-f],[0-9a-f]$":
33 pattern: "^sdw[0-9a-f]{1}[0-9a-f]{4}[0-9a-f]{4}[0-9a-f]{2}$"
43 CID is 2 nibbles
65 #address-cells = <2>;
72 powerdown-gpios = <&wcdpinctrl 2 0>;
77 speaker@0,2 {
[all …]
|
| /Documentation/admin-guide/media/ |
| D | qcom_camss.rst | 20 The driver is implemented using as a reference the Qualcomm Camera Subsystem
30 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers.
31 A separate camera sensor can be connected to each of the CSIPHY module;
32 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application
33 layer of the CSI2 receivers. A CSID can decode data stream from any of the
34 CSIPHY. Each CSID also contains a TG (Test Generator) block which can generate
38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing
41 processing pipeline contains also a scale and crop module at the end. Three
60 - YUYV/UYVY/YVYU/VYUY (packed YUV 4:2:2 - V4L2_PIX_FMT_YUYV /
88 - YUYV/UYVY/YVYU/VYUY (packed YUV 4:2:2 - V4L2_PIX_FMT_YUYV /
[all …]
|
| D | imx.rst | 27 packed <--> planar conversion. The IDMAC can also perform a simple
32 camera sensors over Parallel, BT.656/1120, and MIPI CSI-2 buses.
52 rotation operation is carried out on 8x8 pixel blocks at a time. This
60 contains a Combiner that combines two image planes, with alpha blending
66 - MIPI CSI-2 Receiver for camera sensors with the MIPI CSI-2 bus
67 interface. This is a Synopsys DesignWare core.
69 to send to a CSI.
84 - Supports parallel, BT.565, and MIPI CSI-2 interfaces.
99 VDIC from memory buffers via a output/mem2mem devices.
101 - Includes a Frame Interval Monitor (FIM) that can correct vertical sync
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | example-schema.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
8 # $id is a unique identifier based on the filename. There may or may not be a
20 A more detailed multi-line description of the binding.
26 begin with a tab character.
29 # 'select' is a schema applied to a DT node to determine if this binding
33 # In this case, a 'false' schema will never match.
36 # A dictionary of DT properties for this binding schema
40 # In this case, it's needed to handle a variable number of values as there
41 # isn't another way to express a constraint of the last string value.
42 # The boolean schema must be a list of schemas.
[all …]
|
| /Documentation/power/regulator/ |
| D | overview.rst | 8 This framework is designed to provide a standard kernel interface to control
40 - Electronic device that is supplied power by a regulator.
54 output power of a regulator, switch or by another power
57 The supply regulator may be behind a switch(s). i.e.::
59 Regulator -+-> Switch-1 -+-> Switch-2 --> [Consumer A]
68 - Domain 2: Switch-2, Consumers B & C.
69 - Domain 3: Consumer A.
71 and this represents a "supplies" relationship:
73 Domain-1 --> Domain-2 --> Domain-3.
75 A power domain may have regulators that are supplied power
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | kontron,sl28cpld.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 watchdog, fan monitoring, PWM controller, interrupt controller and a
33 const: 2
41 "^gpio(@[0-9a-f]+)?$":
44 "^hwmon(@[0-9a-f]+)?$":
47 "^interrupt-controller(@[0-9a-f]+)?$":
50 "^pwm(@[0-9a-f]+)?$":
53 "^watchdog(@[0-9a-f]+)?$":
71 sl28cpld@4a {
91 #pwm-cells = <2>;
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,bcm2835-gpio.txt | 3 The BCM2835 GPIO module is a combined GPIO controller, (GPIO) interrupt
14 - gpio-controller: Marks the device node as a GPIO controller.
23 - #interrupt-cells : Should be 2.
28 2 = high-to-low edge triggered.
31 Valid combinations are 1, 2, 3, 4, 8.
33 Please refer to ../gpio/gpio.txt for a general description of GPIO bindings.
42 listed. In other words, a subnode that lists only a mux function implies no
43 information about any pull configuration. Similarly, a subnode that lists only
44 a pul parameter implies no information about the mux function.
65 - brcm,pins: An array of cells. Each cell contains the ID of a pin. Valid IDs
[all …]
|
| /Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 15 - #hwlock-cells: Specifies the number of cells needed to represent a
25 - hwlocks: List of phandle to a hwlock provider node and an
27 #hwlock-cells. The list can have just a single hwlock
29 a phandle and a corresponding args specifier.
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
39 The following example has a node requesting a hwlock in the bank defined by
40 the node hwlock1. hwlock1 is a hwlock provider with an argument specifier
45 hwlocks = <&hwlock1 2>;
49 2. Example of a node using multiple specific hwlocks:
[all …]
|