Searched +full:entry +full:- +full:method (Results 1 – 25 of 102) sorted by relevance
12345
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,nsp-cpu-method.txt | 1 Broadcom Northstar Plus SoC CPU Enable Method
2 ---------------------------------------------
3 This binding defines the enable method used for starting secondary
7 The enable method is specified by defining the following required
9 - enable-method = "brcm,bcm-nsp-smp";
10 - secondary-boot-reg = <...>;
12 The secondary-boot-reg property is a u32 value that specifies the
14 entry point for a secondary CPU. This entry is cpu node specific
16 is a dual core CPU SoC, this entry should be added to cpu1 node.
21 #address-cells = <1>;
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 6 1 - Introduction
10 where cores can be put in different low-power states (ranging from simple
12 the range of dynamic idle states that a processor can enter at run-time, can be
19 - Running
20 - Idle_standby
21 - Idle_retention
22 - Sleep
23 - Off
29 wake-up capabilities, hence it is not considered in this document).
31 Idle state parameters (e.g. entry latency) are platform specific and need to be
[all …]
|
| 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
37 - description:
41 - description:
43 const: arm,psci-0.2
[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/locking/ |
| D | ww-mutex-design.rst | 2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.txt 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/ABI/testing/ |
| D | sysfs-driver-toshiba_acpi | 7 * 0x1 -> FN-Z
8 * 0x2 -> AUTO (also called TIMER)
9 * 0x8 -> ON
10 * 0x10 -> OFF
12 parameters, kernel 3.15 only accepts the first two (FN-Z and
24 valid values range from 0-60.
27 type and the range accepted for type 2 is 1-60.
28 See the entry named "kbd_type"
35 Description: This file shows the absolute position of the built-in
44 * 0 -> OFF
[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 …]
|
| D | enumeration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 that are accessed through memory-mapped registers.
15 In order to support this and re-use the existing drivers as much as
18 - Devices that have no bus connector resource are represented as
21 - Devices behind real busses where there is a connector resource
33 This means that when ACPI_HANDLE(dev) returns non-NULL the device was
35 device-specific configuration. There is an example of this below.
42 for the device and add supported ACPI IDs. If this same IP-block is used on
43 some other non-ACPI platform, the driver might work out of the box or needs
122 entry of the FixedDMA resource array, "rx" means the second entry. The table
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | rpc-cache.txt | 15 - mapping from IP address to client name
16 - mapping from client name and filesystem to export options
17 - mapping from UID to list of GIDs, to work around NFS's limitation
19 - mappings between local UID/GID and remote UID/GID for sites that
21 - mapping from network identify to public key for crypto authentication.
24 - general cache lookup with correct locking
25 - supporting 'NEGATIVE' as well as positive entries
26 - allowing an EXPIRED time on cache items, and removing
27 items after they expire, and are no longer in-use.
28 - making requests to user-space to fill in cache entries
[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/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
71 - 'd-modsig': the digest of the event without the appended modsig;
[all …]
|
| /Documentation/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 …]
|
| D | kernel-stacks.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Kernel stacks on x86-64 bit
37 per CPU interrupt nest counter. This is needed because x86-64 "IST"
48 An IST is selected by a non-zero value in the IST field of an
49 interrupt-gate descriptor. When an interrupt occurs and the hardware
53 will switch back to the per-thread stack. If software wants to allow
55 entry to and exit from the interrupt handler. (This is occasionally
60 NMI. arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
61 pointers on entry to and exit from all IST events, in theory allowing
70 Used for interrupt 8 - Double Fault Exception (#DF).
[all …]
|
| /Documentation/powerpc/ |
| 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/networking/device_drivers/davicom/ |
| D | dm9000.txt | 5 Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>
9 ------------
11 This file describes how to use the DM9000 platform-device based network driver
21 ----------------------------
33 An example from arch/arm/mach-s3c2410/mach-bast.c is:
87 -------------
118 Switch to using the simpler PHY polling method which does not
123 The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
129 ----------------------
135 For the internal PHY, the original (and currently default) method is
[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/arm64/ |
| D | booting.rst | 13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in non-secure
33 ---------------------------
41 the RAM in the machine, or any other method the boot loader designer
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
91 - As of v3.17, all fields are little endian unless stated otherwise.
[all …]
|
| D | arm-acpi.rst | 22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
44 - ACPI’s OSPM defines a power management model that constrains what the
48 - In the enterprise server environment, ACPI has established bindings (such
54 - Choosing a single interface to describe the abstraction between a platform
60 - The new ACPI governance process works well and Linux is now at the same
86 interfaces -- one for Linux and one for Windows.
[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/filesystems/caching/ |
| D | backend-api.txt | 2 FS-CACHE CACHE BACKEND API
5 The FS-Cache system provides an API by which actual caches can be supplied to
6 FS-Cache for it to then serve out to network filesystems and other interested
9 This API is declared in <linux/fscache-cache.h>.
34 (*) "idfmt" is a format and printf-style arguments for constructing a label
38 The cache should then be registered with FS-Cache by passing a pointer to the
47 (*) "fsdef" which should point to the object representation for the FS-Cache
49 here. FS-Cache keeps the caller's reference to the index object if
57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
80 the cache method to be invoked, or
[all …]
|
| /Documentation/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/admin-guide/laptops/ |
| D | sony-laptop.rst | 5 - Copyright (C) 2004- 2005 Stelian Pop <stelian@popies.net>
6 - Copyright (C) 2007 Mattia Dongili <malattia@linux.it>
8 This mini-driver drives the SNC and SPIC device present in the ACPI BIOS of the
11 obsoleted by sony-laptop now.
14 ------------------
24 are indexes to the table "sony_laptop_input_keycode_map" in the sony-laptop.c
29 ------------------
45 ------------------
46 Loading the sony-laptop module will create a
47 /sys/devices/platform/sony-laptop/
[all …]
|
| /Documentation/vm/ |
| D | zswap.rst | 12 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles
13 for potentially reduced swap I/O. This trade-off can also result in a
32 drastically reducing life-shortening writes.
74 means the compression ratio will always be 2:1 or worse (because of half-full
76 storage method, and it can achieve greater storage densities. However,
81 of the swap entry, a combination of the swap type and swap offset, to the zpool
83 with a red-black tree per swap type. The swap offset is the search key for the
86 During a page fault on a PTE that is a swap entry, frontswap calls the zswap
92 via frontswap, to free the compressed entry.
97 * max_pool_percent - The maximum percentage of memory that the compressed
[all …]
|
12345