Searched +full:entry +full:- +full:method (Results 1 – 25 of 122) sorted by relevance
12345
| /Documentation/arch/powerpc/ |
| D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
8 was decided to enforce some strict rules regarding the kernel entry and
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
10 become the ppc32 kernel entry point and the way a new platform should be added
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
19 of a device-tree whose format is defined after Open Firmware specification.
21 doesn't require the device-tree to represent every device in the system and only
34 Entry point
37 There is one single entry point to the kernel, at the start
[all …]
|
| D | hvcs.rst | 24 3.1 Built-in:
55 major and minor numbers are associated with each vty-server. Directions
68 built into the kernel. If not, the default can be over-ridden by inserting
71 3.1 Built-in:
72 -------------
77 Device Drivers --->
78 Character devices --->
84 -----------
89 Device Drivers --->
90 Character devices --->
[all …]
|
| /Documentation/devicetree/bindings/cpu/ |
| D | idle-states.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
11 - Anup Patel <anup@brainfault.org>
15 1 - Introduction
18 ARM and RISC-V systems contain HW capable of managing power consumption
19 dynamically, where cores can be put in different low-power states (ranging
22 run-time, can be specified through device tree bindings representing the
[all …]
|
| D | cpu-capacity.txt | 6 1 - Introduction
15 2 - CPU capacity definition
19 heterogeneity. Such heterogeneity can come from micro-architectural differences
23 capture a first-order approximation of the relative performance of CPUs.
29 * A "single-threaded" or CPU affine benchmark
43 3 - capacity-dmips-mhz
46 capacity-dmips-mhz is an optional cpu node [1] property: u32 value
51 capacity-dmips-mhz property is all-or-nothing: if it is specified for a cpu
54 available, final capacities are calculated by directly using capacity-dmips-
58 4 - Examples
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
15 processors") can be used by Linux to initiate various CPU-centric power
25 r0 => 32-bit Function ID / return value
26 {r1 - r3} => Parameters
40 - description:
44 - description:
52 - const: arm,psci-0.2
[all …]
|
| /Documentation/locking/ |
| D | ww-mutex-design.rst | 2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.rst first, as it applies to wait/wound mutexes too.
7 Motivation for WW-Mutexes
8 -------------------------
37 and the deadlock handling approach is called Wait-Die. The name is based on
41 and dies. Hence Wait-Die.
42 There is also another algorithm called Wound-Wait:
46 transaction. Hence Wound-Wait.
48 However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
49 compared to Wait-Die, but is, on the other hand, associated with more work than
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | domain-idle-state.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
18 const: domain-idle-states
21 "^(cpu|cluster|domain)-":
29 const: domain-idle-state
31 entry-latency-us:
34 state. Note that, the exit-latency-us duration may be guaranteed only
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-toshiba_acpi | 8 * 0x1 -> FN-Z
9 * 0x2 -> AUTO (also called TIMER)
10 * 0x8 -> ON
11 * 0x10 -> OFF
14 parameters, kernel 3.15 only accepts the first two (FN-Z and
26 valid values range from 0-60.
29 type and the range accepted for type 2 is 1-60.
30 See the entry named "kbd_type"
37 Description: This file shows the absolute position of the built-in
47 * 0 -> OFF
[all …]
|
| D | sysfs-class-firmware-attributes | 1 What: /sys/class/firmware-attributes/*/attributes/*/
13 and will accept UTF-8 input.
21 - enumeration: a set of pre-defined valid values
22 - integer: a range of numerical values
23 - string
26 -----------------
27 - ordered-list - a set of ordered list valid values
54 "enumeration"-type specific properties:
59 semi-colon (``;``).
61 "integer"-type specific properties:
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | rpc-cache.rst | 21 - mapping from IP address to client name
22 - mapping from client name and filesystem to export options
23 - mapping from UID to list of GIDs, to work around NFS's limitation
25 - mappings between local UID/GID and remote UID/GID for sites that
27 - mapping from network identify to public key for crypto authentication.
31 - general cache lookup with correct locking
32 - supporting 'NEGATIVE' as well as positive entries
33 - allowing an EXPIRED time on cache items, and removing
34 items after they expire, and are no longer in-use.
35 - making requests to user-space to fill in cache entries
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 method tracing facility.
20 ACPICA provides method tracing capability. And two functions are
24 -----------
28 ACPI_DEBUG_PRINT() macro can be reduced at 2 levels - per-component
30 /sys/module/acpi/parameters/debug_layer) and per-type level (known as
33 But when the particular layer/level is applied to the control method
37 logs when the control method evaluation is started, and disable the
38 detailed logging when the control method evaluation is stopped.
52 control method is being evaluated::
[all …]
|
| /Documentation/PCI/ |
| D | pci-iov-howto.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 :Authors: - Yu Zhao <yu.zhao@intel.com>
10 - Donald Dutile <ddutile@redhat.com>
15 What is SR-IOV
16 --------------
18 Single Root I/O Virtualization (SR-IOV) is a PCI Express Extended
34 How can I enable SR-IOV capability
35 ----------------------------------
37 Multiple methods are available for SR-IOV enablement.
38 In the first method, the device driver (PF driver) will control the
[all …]
|
| /Documentation/devicetree/bindings/soc/loongson/ |
| D | loongson,ls2k-pmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/loongson/loongson,ls2k-pmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Loongson-2 Power Manager controller
10 - Yinbo Zhu <zhuyinbo@loongson.cn>
15 - items:
16 - const: loongson,ls2k0500-pmc
17 - const: syscon
18 - items:
[all …]
|
| /Documentation/arch/x86/ |
| D | entry_64.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
14 kernel code. Most of these entry points are registered in
15 arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
18 syscall entry points and thus provides for 32-bit processes the
19 ability to execute syscalls when running on 64-bit kernels.
25 - system_call: syscall instruction from 64-bit code.
27 - entry_INT80_compat: int 0x80 from 32-bit or 64-bit code; compat syscall
[all …]
|
| /Documentation/security/ |
| D | IMA-templates.rst | 41 mechanism) to generate a new measurement entry by using the template
46 a given template but, instead, it simply calls the ``init()`` method of the template
48 (pointer to allocated data and data length) in the measurement entry structure.
51 The functions ``ima[_ascii]_measurements_show()`` retrieve, for each entry,
52 the template descriptor used to produce that entry and call the show()
53 method for each item of the array of template fields structures.
65 - 'd': the digest of the event (i.e. the digest of a measured file),
67 - 'n': the name of the event (i.e. the file name), with size up to 255 bytes;
68 - 'd-ng': the digest of the event, calculated with an arbitrary hash
70 - 'd-ngv2': same as d-ng, but prefixed with the "ima" or "verity" digest type
[all …]
|
| /Documentation/networking/device_drivers/ethernet/davicom/ |
| D | dm9000.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>
13 ------------
15 This file describes how to use the DM9000 platform-device based network driver
25 ----------------------------
37 An example from arch/arm/mach-s3c/mach-bast.c is::
91 -------------
122 Switch to using the simpler PHY polling method which does not
127 The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
133 ----------------------
[all …]
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-mediatek-hw.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cpufreq/cpufreq-mediatek-hw.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Yuan <hector.yuan@mediatek.com>
19 const: mediatek,cpufreq-hw
26 each frequency domain. Each entry corresponds to
29 "#performance-domain-cells":
37 - compatible
38 - reg
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | numa.txt | 6 1 - Introduction
18 2 - numa-node-id
23 a node id is a 32-bit integer.
26 numa-node-id property which contains the node id of the device.
30 numa-node-id = <0>;
33 numa-node-id = <1>;
36 3 - distance-map
39 The optional device tree node distance-map describes the relative
42 - compatible : Should at least contain "numa-distance-map-v1".
44 - distance-matrix
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 28 a reset of last resort, and will require a complete re-init.
29 This can be useful as a method of recovery if the device is
30 non-responsive, or as a means of loading new firmware as a
37 Description: Writing a non-zero value to this file will force devices to
38 enter EDL (Emergency Download) mode. This entry only exists for
|
| /Documentation/core-api/ |
| D | maple_tree.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
13 The Maple Tree is a B-Tree data type which is optimized for storing
14 non-overlapping ranges, including ranges of size 1. The tree was designed to
15 be simple to use and does not require a user written search method. It
17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
24 use the normal API. An :ref:`maple-tree-advanced-api` exists for more complex
34 :ref:`maple-tree-advanced-api`, but are blocked by the normal API.
39 Pre-allocating of nodes is also supported using the
40 :ref:`maple-tree-advanced-api`. This is useful for users who must guarantee a
45 .. _maple-tree-normal-api:
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
33 ---------------
50 ----------
54 structure. Devices form one global device list and per-network device lists
58 ----------
67 The RapidIO subsystem defines the format and initialization method for subsystem
68 specific switch drivers that are designed to provide hardware-specific
[all …]
|
| /Documentation/filesystems/ |
| D | vfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Copyright (C) 1999 Richard Gooch
10 - Copyright (C) 2005 Pekka Enberg
26 Directory Entry Cache (dcache)
27 ------------------------------
31 to search through the directory entry cache (also known as the dentry
32 cache or dcache). This provides a very fast look-up mechanism to
44 ----------------
54 To look up an inode requires that the VFS calls the lookup() method of
55 the parent directory inode. This method is installed by the specific
[all …]
|
| /Documentation/arch/arm/ |
| D | booting.rst | 9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
28 ---------------------------
39 the RAM in the machine, or any other method the boot loader designer
44 -----------------------------
60 Documentation/admin-guide/kernel-parameters.rst.
64 --------------------------
69 MANDATORY except for DT-only platforms
72 method. Whether this is a hard coded value or some algorithm that
75 value to the kernel. (see linux/arch/arm/tools/mach-types). This
78 For DT-only platforms, the machine type will be determined by device
[all …]
|
| D | arm.rst | 9 ---------------------
21 If you wish to cross-compile, then alter the following lines in the top
36 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
40 CROSS_COMPILE=arm-linux-
48 ---------------
54 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
64 -------------
66 Several new include directories have been created under include/asm-arm,
67 which are there to reduce the clutter in the top-level directory. These
71 `arch-*` machine/platform specific header files
[all …]
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]
|
12345