Home
last modified time | relevance | path

Searched +full:indexed +full:- +full:array (Results 1 – 25 of 36) sorted by relevance

12

/Documentation/devicetree/bindings/usb/
Dgr-udc.txt11 - name : Should be "GAISLER_USBDC" or "01_021"
13 - reg : Address and length of the register set for the device
15 - interrupts : Interrupt numbers for this device. Either one interrupt number
21 - epobufsizes : Array of buffer sizes for OUT endpoints when they differ
22 from the default size of 1024. The array is indexed by the OUT endpoint
25 only for as many endpoints as the array contains.
27 - epibufsizes : Array of buffer sizes for IN endpoints when they differ
28 from the default size of 1024. The array is indexed by the IN endpoint
31 only for as many endpoints as the array contains.
/Documentation/ABI/testing/
Dsysfs-class-led-multicolor7 The multi_index array, when read, will output the LED colors
8 as an array of strings as they are indexed in the
12 Documentation/leds/leds-class-multicolor.rst.
19 This file contains array of integers. Order of components is
20 described by the multi_index array. The maximum intensity should
24 Documentation/leds/leds-class-multicolor.rst.
/Documentation/leds/
Dleds-class-multicolor.rst1 .. SPDX-License-Identifier: GPL-2.0
11 controlled via the multi_intensity array file and the latter is controlled
17 array. These files are children under the LED parent node created by the
18 led_class framework. The led_class framework is documented in led-class.rst
21 Each colored LED will be indexed under the multi_* files. The order of the
23 color name to indexed value.
25 The multi_index file is an array that contains the string list of the colors as
26 they are defined in each multi_* array file.
28 The multi_intensity is an array that can be read or written to for the
29 individual color intensities. All elements within this array must be written in
[all …]
/Documentation/netlink/specs/
Dnlctrl.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: genetlink-legacy
5 uapi-header: linux/genetlink.h
8 genetlink meta-family that exposes information about all genetlink
12 -
13 name: op-flags
15 enum-name:
17 - admin-perm
18 - cmd-cap-do
19 - cmd-cap-dump
[all …]
Dtc.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
12 -
16 -
19 -
23 -
26 -
29 -
32 -
35 -
[all …]
/Documentation/userspace-api/netlink/
Dgenetlink-legacy.rst1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 -------
29 --------------------
31 New Netlink families should use ``multi-attr`` to define arrays.
33 define array types reusing attribute type to carry information.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
41 [SOME-OTHER-ATTR]
42 [ARRAY-ATTR]
[all …]
/Documentation/devicetree/bindings/firmware/
Darm,scpi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Sudeep Holla <sudeep.holla@arm.com>
33 - const: arm,scpi # SCPI v1.0 and above
34 - const: arm,scpi-pre-1.0 # Unversioned SCPI before v1.0
35 - items:
36 - enum:
37 - amlogic,meson-gxbb-scpi
38 - const: arm,scpi-pre-1.0
[all …]
/Documentation/networking/
Dfib_trie.rst1 .. SPDX-License-Identifier: GPL-2.0
4 LC-trie implementation notes
8 ----------
15 An internal node, holding an array of child (leaf or tnode) pointers,
16 indexed through a subset of the key. See Level Compression.
19 ------------------------
22 child array - the "child index". See Level Compression.
26 the child array. See Path Compression.
29 Any given tnode is linked to from the child array of its parent, using
43 contain an arbitrarily large array of links to several children.
[all …]
/Documentation/userspace-api/media/drivers/
Ddw100.rst1 .. SPDX-License-Identifier: GPL-2.0
11 pixel macroblocks indexed using X, Y vertex coordinates.
15 <--------------------------------------->
17 ^ .-------.-------.-------.-------.-------.
21 a | .-------.-------.-------.-------.-------.
25 h | .-------.-------.-------.-------.-------.
29 h | .-------.-------.-------.-------.-------.
33 v '-------'-------'-------'-------'-------'
42 .----------------------.--------..----------------------.--------.
45 '----------------------'--------''----------------------'--------'
[all …]
/Documentation/netlink/
Dgenetlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
Dgenetlink-c.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-c.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
Dgenetlink-legacy.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
Dnetlink-raw.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
21 required: [ name, doc, attribute-sets, operations ]
31 enum: [ netlink-raw ] # Trim
32 # Start netlink-raw
34 description: Protocol number to use for netlink-raw
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smsm.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
25 '#address-cells':
28 qcom,local-host:
42 (0-indexed).
44 '#size-cells':
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-subdev-enum-frame-size.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_FRAME_SIZE - Enumerate media bus frame sizes
35 supported by a sub-device on the specified pad
41 The enumerations are defined by the driver, and indexed using the ``index`` field
59 Sub-devices that only support discrete frame sizes (such as most
64 supported. For instance, a scaler that uses a fixed-point scaling ratio
68 sub-device for an exact supported frame size.
71 pads of the sub-device, as well as on the current active links and the
80 .. flat-table:: struct v4l2_subdev_frame_size_enum
81 :header-rows: 0
[all …]
Dvidioc-subdev-enum-mbus-code.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_SUBDEV_ENUM_MBUS_CODE - Enumerate media bus formats
37 The enumerations are defined by the driver, and indexed using the ``index`` field
42 Therefore, to enumerate media bus formats available at a given sub-device pad,
58 other pads of the sub-device, as well as on the current active links.
66 .. flat-table:: struct v4l2_subdev_mbus_code_enum
67 :header-rows: 0
68 :stub-columns: 0
71 * - __u32
72 - ``pad``
[all …]
/Documentation/admin-guide/mm/
Dpagemap.rst12 physical frame each virtual page is mapped to. It contains one 64-bit
16 * Bits 0-54 page frame number (PFN) if present
17 * Bits 0-4 swap type if swapped
18 * Bits 5-54 swap offset if swapped
19 * Bit 55 pte is soft-dirty (see
20 Documentation/admin-guide/mm/soft-dirty.rst)
22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
23 Documentation/admin-guide/mm/userfaultfd.rst)
25 * Bits 59-60 zero
26 * Bit 61 page is file-page or shared-anon (since 3.5)
[all …]
/Documentation/filesystems/
Dorangefs.rst1 .. SPDX-License-Identifier: GPL-2.0
7 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal
51 On Fedora, install orangefs and orangefs-server::
53 dnf -y install orangefs orangefs-server
64 pvfs2-client-core.
68 pvfs2-server -f /etc/orangefs/orangefs.conf
72 systemctl start orangefs-server
76 pvfs2-ping -m /pvfsmnt
81 systemctl start orangefs-client
85 mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
[all …]
/Documentation/virt/acrn/
Dio-request.rst1 .. SPDX-License-Identifier: GPL-2.0
12 --------------
14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
16 256-byte structure buffer, which is 'struct acrn_io_request', that is filled by
18 VM. ACRN userspace in the Service VM first allocates a 4-KByte page and passes
20 used as an array of 16 I/O request slots with each I/O request slot being 256
21 bytes. This array is indexed by vCPU ID.
24 --------------
38 +------------------------------------------------------+
40 |+--------------------------------------------------+ |
[all …]
/Documentation/filesystems/ext4/
Ddirectory.rst1 .. SPDX-License-Identifier: GPL-2.0
4 -----------------
9 that reference the same inode number--these are known as hard links, and
18 By default, each directory lists its entries in an “almost-linear”
19 array. I write “almost” because it's not a linear array in the memory
22 data blocks and that each block contains a linear array of directory
23 entries. The end of each per-block array is signified by reaching the
36 .. list-table::
38 :header-rows: 1
40 * - Offset
[all …]
/Documentation/core-api/
Dassoc_array.rst2 Generic Associative Array Implementation
8 This associative array implementation is an object container with the following
18 2. Objects do not need to contain linkage blocks for use by the array. This
20 Rather, the array is made up of metadata blocks that point to objects.
22 3. Objects require index keys to locate them within the array.
25 already in the array will replace the old object.
32 7. Index keys can include a hash to scatter objects throughout the array.
34 8. The array can iterated over. The objects will not necessarily come out in
37 9. The array can be iterated over while it is being modified, provided the
43 10. Objects in the array can be looked up by means of their index key.
[all …]
Dswiotlb.rst1 .. SPDX-License-Identifier: GPL-2.0
19 These APIs use the device DMA attributes and kernel-wide settings to determine
30 ---------------
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
54 IOMMU access control is per-granule, the untrusted device can gain access to
60 ------------------
85 ------------------------------
89 pre-allocated at boot time (but see Dynamic swiotlb below). Because swiotlb
93 The need to pre-allocate the default swiotlb pool creates a boot-time tradeoff.
[all …]
/Documentation/admin-guide/device-mapper/
Dunstriped.rst2 Device-mapper "unstriped" target
8 The device-mapper "unstriped" target provides a transparent mechanism to
9 unstripe a device-mapper "striped" target to access the underlying disks
10 without having to touch the true backing block-device. It can also be
11 used to unstripe a hardware RAID-0 to access backing disks.
27 drive you wish to unstripe. This must be 0 indexed.
33 An example of undoing an existing dm-stripe
34 -------------------------------------------
41 underlying device on the striped array::
47 SEQ_END=$((${NUM}-1))
[all …]
/Documentation/devicetree/bindings/pinctrl/
Drenesas,rza1-ports.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-ports.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
16 Pin multiplexing and GPIO configuration is performed on a per-pin basis
17 writing configuration values to per-port register sets.
25 - const: renesas,r7s72100-ports # RZ/A1H
26 - items:
[all …]
/Documentation/devicetree/bindings/regulator/
Dti-abb-regulator.txt4 - compatible: Should be one of:
5 - "ti,abb-v1" for older SoCs like OMAP3
6 - "ti,abb-v2" for newer SoCs like OMAP4, OMAP5
7 - "ti,abb-v3" for a generic definition where setup and control registers are
9 - reg: Address and length of the register set for the device. It contains
10 the information of registers in the same order as described by reg-names
11 - reg-names: Should contain the reg names
12 - "base-address" - contains base address of ABB module (ti,abb-v1,ti,abb-v2)
13 - "control-address" - contains control register address of ABB module (ti,abb-v3)
14 - "setup-address" - contains setup register address of ABB module (ti,abb-v3)
[all …]

12