Searched full:above (Results 1 – 25 of 961) sorted by relevance
12345678910>>...39
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 43 above 47-bit by default.
46 specifying hint address (with or without MAP_FIXED) above 47-bits.
48 If hint address set above 47-bit, but MAP_FIXED is not specified, we try
65 MPX (without MAWA extension) cannot handle addresses above 47-bit, so we
66 need to make sure that MPX cannot be enabled we already have VMA above
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power-wilco | 21 level is above charge_control_end_threshold.
32 Used when charge_type="Custom", as described above. Measured in
39 Used when charge_type="Custom", as described above. Measured in
|
| D | sysfs-platform-dfl-fme | 134 millidegrees Celsius. If temperature rises at or above this
143 millidegrees Celsius. If temperature rises at or above this
151 millidegrees Celsius. If temperature rises at or above this
159 Description: Read-only. It returns 1 if temperature is currently at or above
166 Description: Read-only. It returns 1 if temperature is currently at or above
192 threshold1 in uW. If power consumption rises at or above
205 threshold2 in uW. If power consumption rises at or above
218 above hardware threshold1 (see 'power1_max'), otherwise 0.
225 above hardware threshold2 (see 'power1_crit'), otherwise 0.
|
| D | dell-smbios-wmi | 24 the structure documented above.
27 determined above and allocated.
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 65 fe_code_rate_t fec_inner; /* forward error correction (see above) */
81 fe_code_rate_t fec_inner; /* forward error correction (see above) */
82 fe_modulation_t modulation; /* modulation type (see above) */
97 fe_modulation_t modulation; /* modulation type (see above) */
115 fe_modulation_t constellation; /* modulation type (see above) */
|
| /Documentation/devicetree/bindings/ata/ |
| D | ceva,ahci-1v84.yaml | 44 The fields for the above parameter must be as shown below:-
56 The fields for the above parameter must be as shown below:-
68 The fields for the above parameter must be as shown below:-
80 The fields for the above parameter must be as shown below:-
90 The fields for the above parameter must be as shown below:-
102 The fields for the above parameter must be as shown below:-
114 The fields for the above parameter must be as shown below:-
126 The fields for the above parameter must be as shown below:-
|
| /Documentation/core-api/ |
| D | unaligned-memory-access.rst | 28 The above may seem a little vague, as memory access can happen in different
39 The rule mentioned above forms what we refer to as natural alignment:
71 It should be obvious from the above that if your code causes unaligned
79 At first, the concepts above may seem a little hard to relate to actual
93 Let us assume that an instance of the above structure resides in memory
101 above case it would insert 2 bytes of padding in between field1 and field2.
114 On a related topic, with the above considerations in mind you may observe
118 above example is::
148 With the above in mind, let's move onto a real life example of a function
167 In the above function, when the hardware has efficient unaligned access
[all …]
|
| D | kref.rst | 131 In the above example, kref_put() will be called 2 times in both success
146 Don't assume you know what you are doing and use the above construct.
149 involved where the above may be legal) but someone else who doesn't
213 kfree() with the lock held in the example above (since it is kind of
237 The above example could also be optimized using kref_get_unless_zero() in
280 locking for lookups in the above example::
321 by using kfree_rcu(entry, rhead) as done above, or by calling synchronize_rcu()
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | rohm,bd99954.yaml | 71 # Current used at trickle-charge phase (8 in above chart)
76 # Current used at pre-charge phase (6 in above chart)
81 # Current used at fast charge constant current phase (5 in above chart)
86 # The constant voltage used in fast charging phase (4 in above chart)
92 # when battery voltage exceeds this limit voltage (3 in above chart)
112 # a charge cycle terminates when the battery voltage is above recharge
113 # threshold, and the current is below this setting (7 in above chart)
|
| /Documentation/misc-devices/ |
| D | bh1770glc.rst | 36 by using a delayed work. As long as there is proximity threshold above
79 All results above the value
80 trigs an interrupt. 65535 (i.e. sensor_range) disables the above
119 RW - Measurement rate (in Hz) when the level is above threshold
|
| D | apds990x.rst | 90 All results above the value
91 trigs an interrupt. 65535 (i.e. sensor_range) disables the above
120 In "periodic" mode the driver reports all values above
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-ima.rst | 180 dm_version_str := As described in the 'Table load' section above.
181 device_metadata := As described in the 'Table load' section above.
187 as described in the 'dm_table_load' above.
219 dm_version_str := As described in the 'Table load' section above.
221 … The format is same as 'device_metadata' described in the 'Table load' section above.
223 … The format is same as 'device_metadata' described in the 'Table load' section above.
225 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
227 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
259 dm_version_str := As described in the 'Table load' section above.
261 … The format is same as 'device_metadata' described in the 'Table load' section above.
[all …]
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 29 generic timing routine was developed to achieve above requirements.
174 some of the gpmc timings are missing above), and it will result in
176 mentioned above, refer timing routine for more details. To know what
179 IP details (link above).
|
| /Documentation/RCU/ |
| D | lockdep-splat.rst | 73 section, but the "other info" list above shows that this is not the
86 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the
87 list above).
105 above lockdep-RCU splat.
115 this change would also suppress the above lockdep-RCU splat.
|
| /Documentation/arch/arm/ |
| D | booting.rst | 142 A safe location is just above the 128MiB boundary from start of RAM.
157 A safe location is just above the device tree blob which itself will
158 be loaded just above the 128MiB boundary from the start of RAM as
159 recommended above.
176 that it is loaded above 32MiB in order to avoid the need to relocate
193 - r1 = machine type number discovered in (3) above.
221 If the kernel is entered in HYP mode, the above requirements apply to
|
| D | porting.rst | 80 Anything above TASK_SIZE is common to all processes. I'll call
99 The addresses must also be in the kernel segment (see above).
100 Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the
134 region above).
|
| /Documentation/hwmon/ |
| D | ds620.rst | 32 stays active until the temperature goes above temp1_max.
35 output pin becomes active when the temperature goes above temp1_max and stays
|
| D | ina3221.rst | 37 is above this value
41 average is above this value.
51 when the respective current is above this value
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 19 2) object creation. Locking rules: same as above, but the lock is taken
62 The rules above obviously guarantee that all directories that are going to be
66 If no directory is its own ancestor, the scheme above is deadlock-free.
116 (see above).
145 Notice that "directory" in the above == "anything that might have
|
| /Documentation/locking/ |
| D | spinlocks.rst | 18 The above is always safe. It will disable interrupts _locally_, but the
32 The above is usually pretty simple (you usually need and want only one
65 The routines look the same as above::
79 The above kind of lock may be useful for complex data structures like
100 The single spin-lock primitives above are by no means the only ones. They
|
| /Documentation/arch/mips/ |
| D | ingenic-tcu.rst | 15 (OST). It is a 32-bit programmable timer. On JZ4760B and above, it is
38 - On newest SoCs (JZ4750 and above), channels 1-2 operate as TCU2, the
48 - on newer SoCs (JZ4750 and above), channel 5 has its own interrupt;
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 11 Additionally to the properties specified in the above standards a host bridge
55 register of the bridge directly above this port. Otherwise, the bus
60 above this port, then phys.hi contains the 8-bit function number as
|
| /Documentation/hid/ |
| D | hiddev.rst | 127 This returns a superset of the information above, providing not only
186 use the relative IDs above to enumerate the valid IDs. The ioctl
195 report_type in this structure, as above. The field_index should also
210 usage to be retrieved can be specified as above, or the user can
220 the hiddev_usage_ref structure as above, but additionally fills in
235 that influence the read() call above. The flags are as follows:
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 21 It doesn't necessarily mean that EINJ is not supported if those above
60 The format of the file contents are as above, except present are only
66 are defined in the file available_error_type above.
76 Present for kernel versions 3.13 and above. Used to specify which
96 physical memory address. [Unless "flag" is set - see above]
100 Same use as param1 above. For example, if error type is of memory
|
| /Documentation/devicetree/bindings/timer/ |
| D | mediatek,mtk-timer.txt | 23 * "mediatek,mt6577-timer" for MT6577 and all above compatible timers (GPT)
32 * "mediatek,mt6765-timer" for MT6765 and all above compatible timers (SYST)
|
12345678910>>...39