Searched full:method (Results 1 – 25 of 356) sorted by relevance
12345678910>>...15
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 15 method tracing facility. 20 ACPICA provides method tracing capability. And two functions are 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:: 58 # echo "method" > /sys/module/acpi/parameters/trace_state 61 control method is being evaluated for the first time:: 67 # echo "method-once" > /sys/module/acpi/parameters/trace_state 74 Full path of a control method that can be found in the ACPI namespace. [all …]
|
| D | method-customizing.rst | 4 Linux ACPI Custom Control Method How To 14 1. override an existing method which may not work correctly, 16 2. insert a completely new method in order to create a missing 17 method such as _OFF, _ON, _STA, _INI, etc. 20 control method rather than override the entire DSDT, because kernel 25 - Only ACPI METHOD can be overridden, any other object types like 29 - The same ACPI control method can be overridden for many times, 38 1. override an existing method 43 c) rewrite the ASL code of the method and save it in a new file, 45 Here is an example of a customized \_SB._AC._PSR method:: [all …]
|
| D | acpi-lid.rst | 5 Special Usage Model of the ACPI Control Method Lid Device 15 using a control method lid device. To implement this, the AML tables issue 17 changed. The _LID control method for the lid device must be implemented to 20 For most platforms, both the _LID method and the lid notifications are 27 Restrictions of the returning value of the _LID control method 30 The _LID control method is described to return the "current" lid state. 34 _LID control method is evaluated during the runtime, the problem is its 35 initial returning value. When the AML tables implement this control method 57 This file actually calls the _LID control method described above. And given 74 A. button.lid_init_state=method: [all …]
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm11351-cpu-method.txt | 1 Broadcom Kona Family CPU Enable Method 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,bcm11351-cpu-method"; 33 enable-method = "brcm,bcm11351-cpu-method";
|
| D | brcm,bcm23550-cpu-method.txt | 1 Broadcom Kona Family CPU Enable Method 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,bcm23550"; 33 enable-method = "brcm,bcm23550";
|
| D | brcm,nsp-cpu-method.txt | 1 Broadcom Northstar Plus SoC CPU Enable Method 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"; 35 enable-method = "brcm,bcm-nsp-smp";
|
| D | brcm,bcm63138.txt | 14 'enable-method' property. 21 - enable-method: should be "brcm,bcm63138" 24 - enable-method: should be "brcm,bcm63138" 36 enable-method = "brcm,bcm63138"; 43 enable-method = "brcm,bcm63138";
|
| /Documentation/devicetree/bindings/arm/cpu-enable-method/ |
| D | marvell,berlin-smp | 2 Secondary CPU enable-method "marvell,berlin-smp" binding 5 This document describes the "marvell,berlin-smp" method for enabling secondary 6 CPUs. To apply to all CPUs, a single "marvell,berlin-smp" enable method should 9 Enable method name: "marvell,berlin-smp" 15 This enable method needs valid nodes compatible with "arm,cortex-a9-scu" and 23 enable-method = "marvell,berlin-smp";
|
| D | nuvoton,npcm750-smp | 2 Secondary CPU enable-method "nuvoton,npcm750-smp" binding 5 To apply to all CPUs, a single "nuvoton,npcm750-smp" enable method should be 8 Enable method name: "nuvoton,npcm750-smp" 14 This enable method needs valid nodes compatible with "arm,cortex-a9-scu" and 22 enable-method = "nuvoton,npcm750-smp";
|
| D | al,alpine-smp | 2 Secondary CPU enable-method "al,alpine-smp" binding 5 This document describes the "al,alpine-smp" method for 7 "al,alpine-smp" enable method should be defined in the 10 Enable method name: "al,alpine-smp" 16 This enable method requires valid nodes compatible with 45 enable-method = "al,alpine-smp";
|
| /Documentation/media/uapi/v4l/ |
| D | io.rst | 19 The classic I/O method using the :ref:`read() <func-read>` and 21 V4L2 device. When the driver does not support this method attempts to 24 Other methods must be negotiated. To select the streaming I/O method 27 method is not defined yet. 29 Video overlay can be considered another I/O method, although the 34 Generally exactly one I/O method, including overlay, is associated with 43 method (after first switching away from read/write) other than by
|
| /Documentation/devicetree/bindings/arm/ |
| D | cpus.yaml | 162 enable-method: 181 - brcm,bcm11351-cpu-method 208 Required for systems that have an "enable-method" 249 Required for systems that have an "enable-method" property 259 Required for systems that have an "enable-method" property 269 Optional for systems that have an "enable-method" 280 rockchip,pmu: [enable-method] 349 enable-method = "spin-table"; 357 enable-method = "spin-table"; 365 enable-method = "spin-table"; [all …]
|
| D | psci.yaml | 67 method: 68 description: The method of calling the PSCI firmware. 99 idle state nodes with entry-method property is set to "psci", as per 108 - method 128 method = "smc"; 141 method = "smc"; 158 method = "hvc";
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 12 Method 1a: Declare the I2C devices by bus number 15 This method is appropriate when the I2C bus is a system bus as is the case 55 Method 1b: Declare the I2C devices via devicetree 58 This method has the same implications as method 1a. The declaration of I2C 85 Method 1c: Declare the I2C devices via ACPI 92 Method 2: Instantiate the devices explicitly 95 This method is appropriate when a larger device uses an I2C bus for 99 bus in advance, so the method 1 described above can't be used. Instead, 159 Method 3: Probe an I2C bus for certain devices 177 * The I2C device driver must implement the detect() method, which [all …]
|
| D | old-module-parameters.rst | 16 "instantiating-devices", section "Method 4: Instantiate from user-space". 23 Old method (module parameters):: 29 New method (sysfs interface):: 36 Old method (module parameters):: 40 New method (sysfs interface)::
|
| /Documentation/PCI/ |
| D | pci-iov-howto.rst | 38 In the first method, the device driver (PF driver) will control the 43 In the second method, a write to the sysfs file sriov_numvfs will 44 enable and disable the VFs associated with a PCIe PF. This method 45 enables per-PF, VF enable/disable values versus the first method, 51 The second method is the recommended method for new/future VF devices. 68 (a) For the first method, in the driver:: 74 (b) For the second method, from sysfs:: 81 (a) For the first method, in the driver:: 85 (b) For the second method, from sysfs::
|
| D | acpi-info.rst | 12 method for accessing PCI config space below it, the address space windows 84 The PCIe spec requires the Enhanced Configuration Access Method (ECAM) 90 from either the static MCFG table or a _CBA method in the PNP0A03 device. 94 a _CBA method in the PNP0A03 device describes the ECAM space of a 128 sets those resources by calling the device’s _SRS control method. 155 address range reported in the MCFG table or by _CBA method (see Section 181 The _CBA (Memory mapped Configuration Base Address) control method is 185 control method evaluates to an Integer. 187 This control method appears under a host bridge object. When the _CBA 188 method appears under an active host bridge object, the operating system [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-acpi | 27 control method. 34 _STR control method, if present. 41 _ADR control method, which is present for ACPI device 50 _UID control method, if present. 58 object that has _EJ0 method. 65 functioning or present, if the method _STA is present. 93 hardware, if the _HRV control method is present. It is mostly
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.txt | 14 - method : The method of calling the OP-TEE Trusted OS. Permitted 29 method = "smc";
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-qcom-hw.txt | 57 enable-method = "psci"; 73 enable-method = "psci"; 86 enable-method = "psci"; 99 enable-method = "psci"; 112 enable-method = "psci"; 125 enable-method = "psci"; 138 enable-method = "psci"; 151 enable-method = "psci";
|
| /Documentation/devicetree/bindings/ |
| D | numa.txt | 134 enable-method = "psci"; 142 enable-method = "psci"; 149 enable-method = "psci"; 156 enable-method = "psci"; 163 enable-method = "psci"; 170 enable-method = "psci"; 177 enable-method = "psci"; 184 enable-method = "psci"; 191 enable-method = "psci"; 199 enable-method = "psci"; [all …]
|
| /Documentation/media/v4l-drivers/ |
| D | rcar-fdp1.rst | 27 recover missing lines. This method is also known as blending or Line 31 the current field. This method is also known as Field Averaging (FAV). 34 field is used to fill missing lines from the current field. This method 38 used to fill missing lines from the current field. This method is also
|
| /Documentation/filesystems/configfs/ |
| D | configfs.txt | 70 write_bin_attribute method will be invoked on the final close, therefore it is 192 method. This method is called when the config_item's reference count 212 If an attribute is readable and provides a ->show method, that method will 214 attribute is writable and provides a ->store method, that method will be 237 ct_item_ops->read_bin_attribute() method, that method will be called 282 ct_group_ops->make_item() method. If provided, this method is called from mkdir(2) in the group's … 293 config_item, it is not necessary for a separate drop_group() method. 296 the ct_group_ops->drop_item() method, and configfs will call 311 ct_group_ops->disconnect_notify() method. The method is called after 386 ct_item_ops->drop_link() methods. If the ->allow_link() method exists, [all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 67 The RapidIO subsystem defines the format and initialization method for subsystem 121 An enumeration/discovery method implementation and available input parameters 122 define how any given method can be attached to available RapidIO mports: 130 parameters. This was the original method used since introduction of RapidIO 131 subsystem. Now this method relies on enumerator module parameter which is 132 'rio-scan.scan' for existing basic enumeration/discovery method. 144 a command from user space. This initiation method provides more flexibility 175 to the method shown above, the host destination ID(s) can be specified using 204 Automatic enumeration/discovery start method is applicable only to built-in 206 enumeration/discovery start by existing basic enumerator method set use boot [all …]
|
| /Documentation/filesystems/caching/ |
| D | backend-api.txt | 80 the cache method to be invoked, or 168 method is called to give the op CPU time, and the release method to get 192 do this, the retrieval->op.processor method pointer should be set 211 the write_page() method on the object at appropriate times to effect 237 This method is used to allocate a cache object representation to back a 243 will call the lookup_complete() method to allow the cache to release the 251 This method is used to look up an object, given that the object is already 255 The method should call fscache_object_lookup_negative() as soon as 270 This method is called to ask the cache to release any resources it was 278 This method is called to increment the reference count on an object. It [all …]
|
12345678910>>...15