Home
last modified time | relevance | path

Searched +full:entry +full:- +full:name (Results 1 – 25 of 361) sorted by relevance

12345678910>>...15

/Documentation/ABI/testing/
Dsysfs-firmware-sgi_uv8 Under that directory are a number of read-only attributes::
17 The archtype entry contains the UV architecture type that
18 is used to select arch-dependent addresses and features.
20 UVsystab entry both passed from UV BIOS.
22 The hub_type entry is used to select the type of hub which is
26 The hubless entry basically is present and set only if there
27 is no hub. In this case the hub_type entry is not present.
29 The partition_id entry contains the partition id.
35 The coherence_id entry contains the coherence id.
40 The uv_type entry contains the hub revision number.
[all …]
Dsysfs-bus-rpmsg1 What: /sys/bus/rpmsg/devices/.../name
4 Contact: Ohad Ben-Cohen <ohad@wizery.com>
7 processor. Channels are identified with a (textual) name,
11 This sysfs entry contains the name of this channel.
16 Contact: Ohad Ben-Cohen <ohad@wizery.com>
26 This sysfs entry contains the src (local) rpmsg address
34 Contact: Ohad Ben-Cohen <ohad@wizery.com>
44 This sysfs entry contains the dst (remote) rpmsg address
56 Contact: Ohad Ben-Cohen <ohad@wizery.com>
59 processor. Channels are identified by a textual name (see
[all …]
Dsysfs-platform-kim6 Name of the UART device at which the WL128x chip
9 The device name flows down to architecture specific board
11 firmware. The name exposed is read from the user-space
19 The maximum reliable baud-rate the host can support.
20 Different platforms tend to have different high-speed
21 UART configurations, so the baud-rate needs to be set
22 locally and also sent across to the WL128x via a HCI-VS
23 command. The entry is read and made use by the user-space
32 entry most often should be 1, the host's UART is required
33 to have the capability of flow-control, or else this
[all …]
Dsysfs-firmware-dmi-entries16 each entry has a common header indicating the type and
17 length of the entry, as well as a firmware-provided
23 never expect to find a specific entry type on their
28 to handle these duplicate entry types, each entry is
30 derived from an entry type's ordinal position. That is
34 entries "T-0" through "T-(N-1)":
36 Example entry directories::
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
[all …]
Dsysfs-class-rtrs-server1 What: /sys/class/rtrs-server
6 directory entry with the name of that session is created in here.
8 What: /sys/class/rtrs-server/<session-name>/paths/
12 Description: When new path is created by writing to "add_path" entry on client side,
13 a directory entry named as <source address>@<destination address> is created
16 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/disconnect
21 Operations is non-blocking and returns control immediately to the caller.
23 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_name
27 Description: RO, Contains the name of HCA the connection established on.
29 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_port
[all …]
Dsysfs-firmware-qemu_fw_cfg11 useful as an out-of-band, asynchronous mechanism for providing
14 The authoritative guest-side hardware interface documentation
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
46 Each such fw_cfg sysfs entry has the following values exported
50 name The 56-byte nul-terminated ASCII string used as the
51 blob's 'file name' in the fw_cfg directory.
56 the parent directory name.
58 entry via the control register, and reading a number
63 **Listing fw_cfg blobs by file name**
67 QEMU developers have traditionally used path name semantics
[all …]
Dsysfs-class-vduse6 The vduse/ class sub-directory belongs to the VDUSE
15 This directory entry is created for the control device
18 What: /sys/class/vduse/<device-name>/
23 This directory entry is created when a VDUSE device is
26 What: /sys/class/vduse/<device-name>/msg_timeout
/Documentation/networking/devlink/
Ddevlink-resource.rst1 .. SPDX-License-Identifier: GPL-2.0
15 ``/IPv4/fib-rules`` as resources to limit the number of IPv4 FIB entries and
24 the ``fib`` sub-resource under the ``IPv4`` resource.
32 .. list-table:: List of Generic Resources
35 * - Name
36 - Description
37 * - ``physical_ports``
38 - A limited capacity of physical ports that the switch ASIC can support
41 -------------
49 name kvd size 245760 unit entry
[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
12 associated with a directory file for the particular directory entry that
18 By default, each directory lists its entries in an “almost-linear”
23 entries. The end of each per-block array is signified by reaching the
24 end of the block; the last entry in the block has a record length that
32 The original directory entry format is ``struct ext4_dir_entry``, which
36 .. list-table::
38 :header-rows: 1
[all …]
Dattributes.rst1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------
15 place is between the end of each inode entry and the beginning of the
16 next inode entry. For example, if inode.i_extra_isize = 28 and
17 sb.inode_size = 256, then there are 256 - (128 + 28) = 100 bytes
18 available for in-inode extended attribute storage. The second place
32 .. list-table::
34 :header-rows: 1
36 * - Offset
37 - Type
[all …]
/Documentation/devicetree/bindings/mtd/partitions/
Dpartition.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 In this specific case, a specific suffix is required to the node name.
16 Everything after 'partition-' will be used as the partition name to compare
19 be used instead of the node name to make the comparison.
26 - Rafał Miłecki <rafal@milecki.pl>
34 description: The label / name for this partition. If omitted, the label
35 is taken from the node name (excluding the unit address).
37 read-only:
[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.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
41 [SOME-OTHER-ATTR]
42 [ARRAY-ATTR]
47 where ``ARRAY-ATTR`` is the array entry type.
[all …]
Dc-code-gen.rst1 .. SPDX-License-Identifier: BSD-3-Clause
9 allowed in older families by the ``genetlink-c`` protocol level,
12 For brevity this document refers to ``name`` properties of various
14 of ``name`` in an attribute, and ``$family`` is the name of the
15 family (the global ``name`` property).
17 The upper case is used to denote literal values, e.g. ``$family-CMD``
22 and with dashes (``-``) replaced by underscores (``_``).
24 If the constructed name is a C keyword, an extra underscore is
25 appended (``do`` -> ``do_``).
30 ``c-family-name`` controls the name of the ``#define`` for the family
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smp2p.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>
16 of a single 32-bit value between two processors. Each value has a single
35 $ref: /schemas/types.yaml#/definitions/phandle-array
37 - items:
38 - description: phandle to a syscon node representing the APCS registers
[all …]
/Documentation/userspace-api/
Dvduse.rst2 VDUSE - "vDPA Device in Userspace"
9 possible to implement software-emulated vDPA devices in userspace. And
21 ----------------------------
28 2. Setup each virtqueue with ioctl(VDUSE_VQ_SETUP) on /dev/vduse/$NAME.
30 3. Begin processing VDUSE messages from /dev/vduse/$NAME. The first
41 2. Close the file descriptor referring to /dev/vduse/$NAME.
49 .. code-block:: c
51 static int netlink_add_vduse(const char *name, enum vdpa_command cmd)
59 return -ENOMEM;
75 NLA_PUT_STRING(msg, VDPA_ATTR_DEV_NAME, name);
[all …]
/Documentation/filesystems/
Dvfat.rst10 mount -t vfat /dev/fd0 /mnt
42 **-20**: If current process is in group of file's group ID,
45 **-2**: Other users can change timestamp.
61 **iocharset=<name>**
69 There is also an option of doing UTF-8 translations
76 UTF-8 is the filesystem safe version of Unicode that
79 If 'uni_xlate' gets set, UTF-8 gets disabled.
156 cases in presence of DST - time stamps in a different DST
161 allowed only if the extension part of the name is .EXE,
176 FAT has the ATTR_RO (read-only) attribute. On Windows,
[all …]
/Documentation/devicetree/bindings/crypto/
Domap-des.txt5 - compatible : Should contain "ti,omap4-des"
6 - ti,hwmods: Name of the hwmod associated with the DES module
7 - reg : Offset and length of the register set for the module
8 - interrupts : the interrupt-specifier for the DES module
9 - clocks : A phandle to the functional clock node of the DES module
10 corresponding to each entry in clock-names
11 - clock-names : Name of the functional clock, should be "fck"
14 - dmas: DMA specifiers for tx and rx dma. See the DMA client binding,
16 Each entry corresponds to an entry in dma-names
17 - dma-names: DMA request names should include "tx" and "rx" if present
[all …]
/Documentation/devicetree/bindings/hsi/
Domap-ssi.txt9 - compatible: Should include "ti,omap3-ssi" or "ti,omap4-hsi"
10 - reg-names: Contains the values "sys" and "gdd" (in this order).
11 - reg: Contains a matching register specifier for each entry
12 in reg-names.
13 - interrupt-names: Contains the value "gdd_mpu".
14 - interrupts: Contains matching interrupt information for each entry
15 in interrupt-names.
16 - ranges: Represents the bus address mapping between the main
18 - clock-names: Must include the following entries:
19 "ssi_ssr_fck": The OMAP clock of that name
[all …]
/Documentation/netlink/specs/
Ddevlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 name: devlink
5 protocol: genetlink-legacy
10 -
12 name: sb-pool-type
14 -
15 name: ingress
16 -
17 name: egress
18 -
[all …]
/Documentation/devicetree/bindings/sound/
Dimg,spdif-in.txt5 - compatible : Compatible list, must contain "img,spdif-in"
7 - #sound-dai-cells : Must be equal to 0
9 - reg : Offset and length of the register set for the device
11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names
18 - clock-names : Includes the following entries:
23 - resets: Should contain a phandle to the spdif in reset signal, if any
25 - reset-names: Should contain the reset signal name "rst", if a
28 - interrupts : Contains the spdif in interrupt, if present
[all …]
Dimg,parallel-out.txt5 - compatible : Compatible list, must contain "img,parallel-out".
7 - #sound-dai-cells : Must be equal to 0
9 - reg : Offset and length of the register set for the device.
11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names.
18 - clock-names : Includes the following entries:
22 - resets: Contains a phandle to the parallel out reset signal
24 - reset-names: Contains the reset signal name "rst"
28 - interrupts : Contains the parallel out interrupt, if present
[all …]
Dimg,spdif-out.txt5 - compatible : Compatible list, must contain "img,spdif-out"
7 - #sound-dai-cells : Must be equal to 0
9 - reg : Offset and length of the register set for the device
11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names.
18 - clock-names : Includes the following entries:
22 - resets: Contains a phandle to the spdif out reset signal
24 - reset-names: Contains the reset signal name "rst"
28 - interrupts : Contains the parallel out interrupt, if present
[all …]
Dimg,i2s-in.txt5 - compatible : Compatible list, must contain "img,i2s-in"
7 - #sound-dai-cells : Must be equal to 0
9 - reg : Offset and length of the register set for the device
11 - clocks : Contains an entry for each entry in clock-names
13 - clock-names : Must include the following entry:
16 - dmas: Contains an entry for each entry in dma-names.
18 - dma-names: Must include the following entry:
21 - img,i2s-channels : Number of I2S channels instantiated in the I2S in block
25 - interrupts : Contains the I2S in interrupts. Depending on
31 - resets: Contains a phandle to the I2S in reset signal
[all …]
/Documentation/admin-guide/nfs/
Dnfs-client.rst32 the local system's node name. System administrators, however, often do not
39 used together with a system's node name when an NFS client identifies itself to
40 a server. Thus, if the system's node name is not unique, its
71 …530 Section 6\: Filesystem Migration and Replication: https://tools.ietf.org/html/rfc3530#section-6
72 …lementation Guide for Referrals in NFSv4: https://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00
83 valid entry. If so, it returns that entry and exits.
85 (2) If no valid entry exists, the helper script '/sbin/nfs_cache_getent'
88 - the cache name, "dns_resolve"
89 - the hostname to resolve
92 writes the result into the rpc_pipefs pseudo-file
[all …]
/Documentation/devicetree/bindings/mmc/
Dusdhi6rol0.txt5 - compatible: must be
7 - interrupts: 3 interrupts, named "card detect", "data" and "SDIO" must be
9 - clocks: a clock binding for the IMCLK input
13 - vmmc-supply: a phandle of a regulator, supplying Vcc to the card
14 - vqmmc-supply: a phandle of a regulator, supplying VccQ to the card
15 - pinctrl-names: Can contain a "default" entry and a "state_uhs"
16 entry. The state_uhs entry is used together with the default
17 entry when the board requires distinct settings for UHS speeds.
19 - pinctrl-N: One property for each name listed in pinctrl-names, see
20 ../pinctrl/pinctrl-bindings.txt.
[all …]

12345678910>>...15