Searched full:entries (Results 1 – 25 of 598) sorted by relevance
12345678910>>...24
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-esrt | 13 Description: The number of entries in the ESRT
18 Description: The maximum number of entries that /could/ be registered
27 What: /sys/firmware/efi/esrt/entries/entry<N>/
31 subdirectory under entries/ .
32 example: /sys/firmware/efi/esrt/entries/entry0/
34 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_type
46 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_class
51 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_version
57 What: /sys/firmware/efi/esrt/entries/entry<N>/lowest_supported_fw_version
62 What: /sys/firmware/efi/esrt/entries/entry<N>/capsule_flags
[all …]
|
| D | sysfs-firmware-dmi-entries | 1 What: /sys/firmware/dmi/entries/
15 DMI is structured as a large table of entries, where
19 entries.
21 Some entries are required by the specification, but many
27 Multiple entries of the same type are allowed. In order
31 to say, if there are 'N' multiple entries with the same type
34 entries "T-0" through "T-(N-1)":
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 5 This directory exposes error log entries retrieved
13 Log entries may be purged by the service processor
15 Linux if there is no room for more log entries.
17 In the event that Linux has retrieved the log entries
19 the service processor needs more room for log entries,
24 entries, read them out and acknowledge them.
27 entries than firmware can, so after you acknowledge
|
| /Documentation/core-api/ |
| D | xarray.rst | 44 are used to distinguish value entries from normal pointers, so you must
45 decide whether they want to store value entries or tagged pointers in
49 conflict with value entries or internal entries.
51 An unusual feature of the XArray is the ability to create entries which
55 entries can be explicitly split into smaller entries, or storing ``NULL``
66 You can then set entries using xa_store() and get entries
84 You can copy entries out of the XArray into a plain array by calling
85 xa_extract(). Or you can iterate over the present entries in the XArray
107 If all entries in the array are ``NULL``, the xa_empty() function
110 Finally, you can remove all entries from an XArray by calling
[all …]
|
| D | maple_tree.rst | 16 supports iterating over a range of entries and going to the previous or next
30 (ie 2, 6, 10 .. 4094) for internal use. If the entries may use reserved
31 entries then the users can convert the entries using xa_mk_value() and convert
60 You can then set entries using mtree_store() or mtree_store_range().
87 Finally, you can remove all entries from a maple tree by calling
88 mtree_destroy(). If the maple tree entries are pointers, you may wish to free
89 the entries first.
158 You can set entries using mas_store(). mas_store() will overwrite any entry
|
| /Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 10 several device entries. Each device entry behaves as a pin.
12 As each pin may contain several device entries and each codec may contain
24 Each pin may have several device entries (virtual pins). On Intel platform,
25 the device entries number is dynamically changed. If DP MST hub is connected,
26 it is in DP MST mode, and the device entries number is 3. Otherwise, the
27 device entries number is 1.
29 To simplify the implementation, all the device entries will be initialized
35 device entries on the same pin have the same connection list.
|
| /Documentation/arch/x86/ |
| D | entry_64.rst | 4 Kernel Entries
7 This file documents some of the kernel entries in
23 Some of these entries are:
33 - interrupt: An array of entries. Every IDT vector that doesn't
44 There are a few complexities here. The different x86-64 entries
47 the IDT entries push an error code onto the stack; others don't.
48 IDT entries using the IST alternative stack mechanism need their own
99 Therefore, super-atomic entries (except NMI, which is handled separately)
107 We try to only use IST entries and the paranoid entry code for vectors
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 3 Directory Entries
8 filesystem. There can be many directory entries across the filesystem
11 such, directory entries are found by reading the data block(s)
18 By default, each directory lists its entries in an “almost-linear”
20 sense because directory entries are not split across filesystem blocks.
23 entries. The end of each per-block array is signified by reaching the
27 directory entries are signified by inode = 0. By default the filesystem
28 uses ``struct ext4_dir_entry_2`` for directory entries unless the
126 ``ext4_extended_dir_entry_2`` to ``ext4_dir_entry_2`` except for the entries
194 A linear array of directory entries isn't great for performance, so a
[all …]
|
| D | inlinedata.rst | 30 entries; see ``struct ext4_dir_entry``. If there is a “system.data”
34 entries cannot span the two.
36 Inline directory entries are not checksummed, as the inode checksum
|
| /Documentation/arch/arm64/ |
| D | hugetlbpage.rst | 11 - size of entries supported by the TLBs
19 block of memory. Regardless of the supported size of entries in TLB, block
26 The architecture provides a contiguous bit in the translation table entries
28 contiguous set of entries that can be cached in a single TLB entry.
31 pte (last) level. The number of supported contiguous entries varies by page size
|
| /Documentation/tools/rtla/ |
| D | common_hist_options.rst | 5 **-E**, **--entries** *N*
7 Set the number of entries of the histogram (default 256).
23 Print zero only entries.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 18 devices from the whitelist or add new entries. A child cgroup can
63 from their whitelist and all the locally set whitelist entries will be
64 re-evaluated. In case one of the locally set whitelist entries would provide
81 it'll propagate down and after revalidating B's entries, the whitelist entry
84 group whitelist entries denied devices
91 Notice that new whitelist entries will not be propagated::
97 group whitelist entries denied devices
107 group whitelist entries denied devices
111 but now it'll be possible to add new entries to B::
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-enc-index.rst | 42 written in the ``entries`` field, and initializes the ``entries_cap``
47 ``V4L2_ENC_IDX_ENTRIES`` entries from a driver buffer, which can hold up
48 to ``entries_cap`` entries. This number can be lower or higher than
50 read the meta data in time the oldest entries will be lost. When the
51 buffer is empty or no capturing/encoding is in progress, ``entries``
67 - ``entries``
68 - The number of entries the driver stored in the ``entry`` array.
71 - The number of entries the driver can buffer. Must be greater than
|
| /Documentation/networking/ |
| D | mpls-sysctl.rst | 11 Number of entries in the platform label table. It is not
15 A dense utilization of the entries in the platform label table
19 If the number of platform label table entries is set to 0 no
23 Reducing this value will remove all label routing entries that
|
| /Documentation/devicetree/bindings/media/ |
| D | mtk-cir.txt | 9 entries in clock-names property;
11 - "clk" entries: for MT7623 SoC
12 - "clk", "bus" entries: for MT7622 SoC
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 42 Three entries specifying the outgoing ipc bit used for signaling the
66 Each SMP2P pair contain a set of inbound and outbound entries, these are
83 The name of this entry, for inbound entries this will be used to
84 match against the remotely allocated entry and for outbound entries
85 this name is used for allocating entries.
91 Required for outgoing entries.
|
| /Documentation/arch/s390/ |
| D | pci.rst | 13 Command line parameters and debugfs entries
27 debugfs entries
45 Sysfs entries
48 Entries specific to zPCI functions and entries that hold zPCI information.
52 The slot entries are set up using the function identifier (FID) of the
|
| /Documentation/devicetree/bindings/pci/ |
| D | hisilicon-histb-pcie.txt | 14 - reg-names: Must include the following entries:
20 - interrupt-names: Must include "msi" entries.
23 - clock-name: Must include the following entries:
30 - reset-names: Must include the following entries:
|
| /Documentation/arch/x86/x86_64/ |
| D | machinecheck.rst | 18 log then mcelog should run to collect and decode machine check entries
24 The directory contains some configurable entries. See
27 TBD document entries for AMD threshold interrupt configuration
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 69 the entries (each hotspot block covers a larger area than a single
78 mq placed entries in different levels of the multiqueue structures
80 levels generally had the most entries, and the top ones had very
84 smq does not maintain a hit count, instead it swaps hit entries with
87 scheme we can decide how many entries occupy each multiqueue level,
99 performing badly then it starts moving entries more quickly between
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-mt7622.txt | 9 entries in clock-names property;
10 - clock-names : Should contain "rtc" entries
|
| /Documentation/netlink/specs/ |
| D | handshake.yaml | 19 entries: [ none, tlshd, max ]
24 entries: [ unspec, clienthello, serverhello ]
29 entries: [ unspec, unauth, psk, x509 ]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | lpc1857-eeprom.txt | 7 - reg-names: Must include the following entries.
11 - clock-names: Must include the following entries.
|
| /Documentation/devicetree/bindings/sound/ |
| D | nvidia,tegra30-ahub.txt | 10 - Tegra30 requires 2 entries, for the APBIF and AHUB/AUDIO register blocks.
15 - clock-names : Must include the following entries:
20 - reset-names : Must include the following entries:
49 - dma-names : Must include the following entries:
|
| /Documentation/devicetree/bindings/gpu/ |
| D | nvidia,gk20a.txt | 11 Must contain two entries:
16 - interrupt-names: Must include the following entries:
23 - clock-names: Must include the following entries:
34 - reset-names: Must include the following entries:
|
12345678910>>...24