Searched +full:group +full:- +full:index +full:- +full:bits (Results 1 – 25 of 61) sorted by relevance
123
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,imsics.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/riscv,imsics.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V Incoming MSI Controller (IMSIC)
10 - Anup Patel <anup@brainfault.org>
13 The RISC-V advanced interrupt architecture (AIA) defines a per-CPU incoming
14 MSI controller (IMSIC) for handling MSIs in a RISC-V platform. The RISC-V
15 AIA specification can be found at https://github.com/riscv/riscv-aia.
17 The IMSIC is a per-CPU (or per-HART) device with separate interrupt file
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | fsl,imx8qm-lvds-phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/fsl,imx8qm-lvds-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liu Ying <victor.liu@nxp.com>
14 It converts two groups of four 7/10 bits of CMOS data into two
15 groups of four data lanes of LVDS data streams. A phase-locked
16 transmit clock is transmitted in parallel with each group of
18 clock, 56/80 bits of input data are sampled and transmitted
30 - fsl,imx8qm-lvds-phy
[all …]
|
| D | phy-miphy28lp.txt | 8 - compatible : Should be "st,miphy28lp-phy".
9 - st,syscfg : Should be a phandle of the system configuration register group
10 which contain the SATA, PCIe or USB3 mode setting bits.
12 Required nodes : A sub-node is required for each channel the controller
14 'reg' and 'reg-names' properties are used inside these
19 - #phy-cells : Should be 1 (See second example)
21 - PHY_TYPE_SATA
22 - PHY_TYPE_PCI
23 - PHY_TYPE_USB3
24 - reg : Address and length of the register set for the device.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | switch.rst | 2 dm-switch
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
11 number of fixed-sized address regions but there is no simple pattern
13 dm-stripe.
16 ----------
19 frameless architecture. In this architecture, the storage group
24 The storage group exposes a single target discovery portal, no matter
34 the storage group and initiators. In a multipathing configuration, it
42 A device-mapper table already lets you map different regions of a
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | inodes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Index Nodes
4 -----------
15 links and is in general more seek-happy than ext4 due to its simpler
21 block group containing an inode can be calculated as
22 ``(inode_number - 1) / sb.s_inodes_per_group``, and the offset into the
23 group's table is ``(inode_number - 1) % sb.s_inodes_per_group``. There
31 .. list-table::
33 :header-rows: 1
36 * - Offset
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _frontend-stat-properties:
17 can use different modulation types for each group of carriers. On such
20 plus one metric per each carrier group (called "layer" on ISDB).
25 layer, starting from layer A(index 1), layer B (index 2) and so on.
32 - ``svalue`` or ``uvalue``, where ``svalue`` is for signed values of
36 - ``scale`` - Scale for the value. It can be:
38 - ``FE_SCALE_NOT_AVAILABLE`` - The parameter is supported by the
42 - ``FE_SCALE_DECIBEL`` - parameter is a signed value, measured in
45 - ``FE_SCALE_RELATIVE`` - parameter is a unsigned value, where 0
[all …]
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 9 are represented as being members of a sub-grouping domain. This performance
17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
23 ------
27 ------
28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
35 (domainID index) that represents the 1 based ordinal in the associativity lists.
39 { primary domainID index, secondary domainID index, tertiary domainID index.. }
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - KVM_DEV_TYPE_ARM_VGIC_V2 ARM Generic Interrupt Controller v2.0
13 controller, requiring emulated user-space devices to inject interrupts to the
18 device and guest ITS devices, see arm-vgic-v3.txt. It is not possible to
26 KVM_VGIC_V2_ADDR_TYPE_DIST (rw, 64-bit)
31 KVM_VGIC_V2_ADDR_TYPE_CPU (rw, 64-bit)
39 -E2BIG Address outside of addressable IPA range
40 -EINVAL Incorrectly aligned address
41 -EEXIST Address already configured
42 -ENXIO The group or attribute is unknown/unsupported for this device
[all …]
|
| D | arm-vgic-v3.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - KVM_DEV_TYPE_ARM_VGIC_V3 ARM Generic Interrupt Controller v3.0
12 will act as the VM interrupt controller, requiring emulated user-space devices
23 KVM_VGIC_V3_ADDR_TYPE_DIST (rw, 64-bit)
28 KVM_VGIC_V3_ADDR_TYPE_REDIST (rw, 64-bit)
35 KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION (rw, 64-bit)
38 bits: | 63 .... 52 | 51 .... 16 | 15 - 12 |11 - 0
39 values: | count | base | flags | index
41 - index encodes the unique redistributor region index
42 - flags: reserved for future use, currently 0
[all …]
|
| /Documentation/bpf/standardization/ |
| D | instruction-set.rst | 27 BCP 14 `<https://www.rfc-editor.org/info/rfc2119>`_
28 `<https://www.rfc-editor.org/info/rfc8174>`_
38 -----
51 .. table:: Meaning of bit-width notation
56 8 8 bits
57 16 16 bits
58 32 32 bits
59 64 64 bits
60 128 128 bits
63 For example, `u32` is a type whose valid values are all the 32-bit unsigned
[all …]
|
| /Documentation/bpf/ |
| D | map_devmap.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_DEVMAP`` was introduced in kernel version 4.14
10 - ``BPF_MAP_TYPE_DEVMAP_HASH`` was introduced in kernel version 5.4
15 the index to lookup a reference to a net device. While ``BPF_MAP_TYPE_DEVMAP_HASH``
21 - The key to a hash map doesn't have to be an ``ifindex``.
22 - While ``BPF_MAP_TYPE_DEVMAP_HASH`` allows for densely packing the net devices
31 ----------
34 .. code-block:: c
38 Redirect the packet to the endpoint referenced by ``map`` at index ``key``.
42 The lower two bits of *flags* are used as the return code if the map lookup
[all …]
|
| /Documentation/arch/x86/ |
| D | resctrl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
10 - Tony Luck <tony.luck@intel.com>
11 - Vikas Shivappa <vikas.shivappa@intel.com>
18 flag bits:
38 # mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps][,debug]] /sys/fs/resctrl
57 pseudo-locking is a unique way of using cache control to "pin" or
59 "Cache Pseudo-Locking".
88 The minimum number of consecutive bits which
96 own settings for cache use which can over-ride
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net | 35 Values vary based on the lower-level protocol used by the
54 01-80-C2-00-00-0X on a bridge device. Only values that set bits
59 Restricted bits:
62 0 01-80-C2-00-00-00 Bridge Group Address used for STP
63 1 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
64 2 01-80-C2-00-00-02 (Link Aggregation) 802.3ad
67 Any values not setting these bits can be used. Take special
68 care when forwarding control frames e.g. 802.1X-PAE or LLDP.
135 the device is not usable unless some supplicant-based
193 Indicates the system-wide interface unique index identifier as a
[all …]
|
| /Documentation/filesystems/ |
| D | ext2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
34 errors=remount-ro Remount the filesystem read-only on an error.
37 grpid, bsdgroups Give objects the same group ID as their parent.
38 nogrpid, sysvgroups New objects have the group ID of their creator.
40 nouid32 Use 16-bit UIDs and GIDs.
50 resgid=n The group ID which may use the reserved blocks.
65 grpquota Enable group disk quota support
84 ------
93 ------------
[all …]
|
| D | overlayfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
17 ---------------
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
43 The "xino" feature uses the high inode number bits for fsid, because the
44 underlying filesystems rarely use the high inode number bits. In case
45 the underlying inode number does overflow into the high xino bits, overlay
[all …]
|
| D | qnx6.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 ------
39 ---------------
65 Unused block pointers are always set to ~0 - regardless of root node,
79 0x1000 is the size reserved for each superblock - regardless of the
83 ------
85 Each object in the filesystem is represented by an inode. (index node)
89 The metadata about an object includes the permissions, owner, group, flags,
104 -----------
125 -------------
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
24 and bit-banged data signals:
27 gpio-controller;
28 #gpio-cells = <2>;
32 data-gpios = <&gpio1 12 0>,
44 recommended to use the two-cell approach.
48 include/dt-bindings/gpio/gpio.h whenever possible:
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | ethernet-phy.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/net/ethernet-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
14 # The dt-schema tools will generate a select statement first by using
21 pattern: "^ethernet-phy(@[a-f0-9]+)?$"
24 - $nodename
[all …]
|
| /Documentation/staging/ |
| D | crc32.rst | 5 A CRC is a long-division remainder. You add the CRC to the message,
11 protocols put the end-of-frame flag after the CRC.
15 - We're working in binary, so the digits are only 0 and 1, and
16 - When dividing polynomials, there are no carries. Rather than add and
21 To produce a 32-bit CRC, the divisor is actually a 33-bit CRC polynomial.
22 Since it's 33 bits long, bit 32 is always going to be set, so usually the
24 familiar with the IEEE 754 floating-point format, it's the same idea.)
26 Note that a CRC is computed over a string of *bits*, so you have
27 to decide on the endianness of the bits within each byte. To get
28 the best error-detecting properties, this should correspond to the
[all …]
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 7 --------
50 -------------------------------
62 effective GID, and supplementary group list).
66 independently enabled and disabled on per-thread basis for processes and
103 ---------------------------------
105 Mechanisms of capabilities, privileged capability-dumb files [6]_,
111 1. Create perf_users group of privileged Perf users, assign perf_users
112 group to Perf tool executable and limit access to the executable for
113 other users in the system who are not in the perf_users group:
118 # ls -alhF
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
82 … "ORCL,sun4v-dax-fc" is compatible with the "ORCL,sun4v-dax" interface, and includes additional CCB
[all …]
|
| /Documentation/userspace-api/netlink/ |
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
17 - the C uAPI header
18 …- documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/i…
19 - policy tables for input attribute validation
20 - operation tables
25 See :doc:`intro-specs` for a practical starting guide.
28 ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)``
40 - ``genetlink`` - most streamlined, should be used by all new families
41 - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
[all …]
|
| /Documentation/sound/designs/ |
| D | midi-2.0.rst | 12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
20 the events up to 16 "UMP Groups", where each UMP Group contain up to
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
69 `midi2_enable=0` option to snd-usb-audio driver module, too.
[all …]
|
| /Documentation/driver-api/ |
| D | vfio.rst | 2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
36 ---------------------------
42 as allowing a device read-write access to system memory imposes the
55 For instance, an individual device may be part of a larger multi-
59 could be anything from a multi-function PCI device with backdoors
[all …]
|
| /Documentation/virt/kvm/ |
| D | api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
13 - System ioctls: These query and set global attributes which affect the
17 - VM ioctls: These query and set attributes that affect an entire virtual
24 - vcpu ioctls: These query and set attributes that control the operation
32 - device ioctls: These query and set attributes that control the operation
80 facility that allows backward-compatible extensions to the API to be
104 the ioctl returns -ENOTTY.
122 -----------------------
139 -----------------
[all …]
|
123