Searched full:load (Results 1 – 25 of 388) sorted by relevance
12345678910>>...16
| /Documentation/isdn/ |
| D | avmb1.rst | 27 You need at least /dev/capi20 to load the firmware.
46 if you configure as modules load the modules this way::
54 if you have an B1-PCI card load the module b1pci.o::
58 and load the firmware with::
60 avmcapictrl load /lib/isdn/b1.t4 1
62 if you have an B1-ISA card load the module b1isa.o
67 and load the firmware by calling::
69 avmcapictrl load /lib/isdn/b1.t4 1
71 if you have an T1-ISA card load the module t1isa.o
76 and load the firmware by calling::
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-pisosr.txt | 15 - load-gpios : GPIO pin specifier attached to load enable, this
17 load input pin values into the the device.
29 load-gpios = <&gpio2 23 GPIO_ACTIVE_LOW>;
|
| /Documentation/devicetree/bindings/rtc/ |
| D | nxp,pcf8523.txt | 8 - quartz-load-femtofarads: The capacitive load of the quartz(x-tal),
17 quartz-load-femtofarads = <7000>;
|
| D | nxp,pcf85063.txt | 12 - quartz-load-femtofarads: The capacitive load of the quartz(x-tal),
21 quartz-load-femtofarads = <12500>;
|
| /Documentation/ |
| D | memory-barriers.txt | 59 - Read memory barriers vs load speculation.
161 STORE A=3, STORE B=4, y=LOAD A->3, x=LOAD B->4
162 STORE A=3, STORE B=4, x=LOAD B->4, y=LOAD A->3
163 STORE A=3, y=LOAD A->3, STORE B=4, x=LOAD B->4
164 STORE A=3, y=LOAD A->3, x=LOAD B->2, STORE B=4
165 STORE A=3, x=LOAD B->2, STORE B=4, y=LOAD A->3
166 STORE A=3, x=LOAD B->2, y=LOAD A->3, STORE B=4
167 STORE B=4, STORE A=3, y=LOAD A->3, x=LOAD B->4
200 Note that CPU 2 will never try and load C into D because the CPU will load P
201 into Q before issuing the load of *Q.
[all …]
|
| /Documentation/x86/ |
| D | mds.rst | 14 - Microarchitectural Load Port Data Sampling (MLPDS) (CVE-2018-12127)
18 dependent load (store-to-load forwarding) as an optimization. The forward
19 can also happen to a faulting or assisting load operation for a different
27 to a memory or I/O operation. Fill buffers can forward data to a load
30 can then be forwarded to a faulting or assisting load operation, which can
34 MLPDS leaks Load Port Data. Load ports are used to perform load operations
36 file or a subsequent operation. In some implementations the Load Port can
39 exploited eventually. Load ports are shared between Hyper-Threads so cross
42 MDSUM is a special case of MSBDS, MFBDS and MLPDS. An uncacheable load from
54 - to control the load to trigger a fault or assist
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | max2175.txt | 22 - maxim,refout-load : load capacitance value (in picofarads) on reference
23 output drive level. The possible load values are:
51 maxim,refout-load = <10>;
|
| /Documentation/networking/device_drivers/dec/ |
| D | dmfe.txt | 18 didn't compile this driver as a module, it will automatically load itself on boot and print a
23 If you compiled this driver as a module, you have to load it on boot.You can load it with command :
27 This way it will autodetect the device mode.This is the suggested way to load the module.Or you can…
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-counter-104-quad-8 | 6 non-synchronous load mode.
21 non-synchronous or synchronous load mode. Synchronous load mode
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 35 1. load this module
36 2. use i2cset (from the i2c-tools project) to pre-load some data
37 3. load the target chip driver module
41 can load register values automatically from a chip dump.
|
| /Documentation/media/v4l-drivers/ |
| D | cafe_ccic.rst | 30 Load time options
33 There are a few load-time options, most of which can be changed after
38 then worst-case-sized buffers will be allocated at module load time.
43 option is only consulted for load-time allocation; when buffers are
|
| /Documentation/arm/sa1100/ |
| D | assabet.rst | 91 load zImage -r -b 0x100000
95 load -m ymodem -r -b 0x100000
108 load ramdisk_image.gz -r -b 0x800000
115 fis load "Linux kernel"
138 To load this file::
140 load sample_img.jffs2 -r -b 0x100000
144 RedBoot> load sample_img.jffs2 -r -b 0x100000
202 fis load "Linux kernel"
228 >> load zImage -r -b 0x100000
229 >> load ramdisk_ks.gz -r -b 0x800000
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cpusets.rst | 181 - cpuset.sched_load_balance flag: if set, load balance within CPUs on that cpuset
197 children of that task, to a cpuset allows organizing the work load
281 the system load imposed by a batch scheduler monitoring this
379 The kernel scheduler (kernel/sched/core.c) automatically load balances
385 The algorithmic cost of load balancing and its impact on key shared
389 domains such that it only load balances within each sched domain.
392 domain and hence won't be load balanced.
396 two domains won't be load balanced to the other one.
400 the isolated CPUs will not participate in load balancing, and will not
403 This default load balancing across all CPUs is not well suited for
[all …]
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 16 explicitly set. A sched domain's span means "balance process load among these
28 is treated as one entity. The load of a group is defined as the sum of the
29 load of each of its member CPUs, and only when the load of a group becomes
34 rebalancing event for the current runqueue has arrived. The actual load
|
| /Documentation/translations/ko_KR/ |
| D | memory-barriers.txt | 190 STORE A=3, STORE B=4, y=LOAD A->3, x=LOAD B->4
191 STORE A=3, STORE B=4, x=LOAD B->4, y=LOAD A->3
192 STORE A=3, y=LOAD A->3, STORE B=4, x=LOAD B->4
193 STORE A=3, y=LOAD A->3, x=LOAD B->2, STORE B=4
194 STORE A=3, x=LOAD B->2, STORE B=4, y=LOAD A->3
195 STORE A=3, x=LOAD B->2, y=LOAD A->3, STORE B=4
196 STORE B=4, STORE A=3, y=LOAD A->3, x=LOAD B->4
247 STORE *A = 5, x = LOAD *D
248 x = LOAD *D, STORE *A = 5
265 Q = LOAD P, D = LOAD *Q
[all …]
|
| /Documentation/networking/ |
| D | devlink-params.txt | 48 Load firmware version preferred by the driver.
50 Load firmware currently stored in flash.
52 Load firmware currently available on host's disk.
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,cdce925.txt | 25 - xtal-load-pf: Crystal load-capacitor value to fine-tune performance on a
45 xtal-load-pf = <5>;
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 24 the load time. It'd be safer to plug in the joystick device before
67 additional modules. Load the corresponding module to add the gameport
82 support, so you don't have to load ns558 module. Just load "joydev"
90 Instead, you need to load "ns558" module in addition to "joydev" and
|
| /Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 21 manually load the firmware. Read below for more details.
69 to load and indicate when firmware is ready. The sysfs directory is created
82 To load firmware using the sysfs interface we expose a loading indicator,
93 The firmware device used to help load firmware using sysfs is only created if
103 Will clean any previous partial load at once and make the firmware API
119 Since a device is created for the sysfs interface to help load firmware as a
186 load firmware for you through a custom path.
196 solution will have as much time as it needs to load firmware.
|
| /Documentation/devicetree/bindings/ufs/ |
| D | ufs-qcom.txt | 28 - vdda-phy-max-microamp : specifies max. load that can be drawn from phy supply
29 - vdda-pll-max-microamp : specifies max. load that can be drawn from pll supply
31 - vddp-ref-clk-max-microamp : specifies max. load that can be drawn from this supply
|
| /Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 277 [Note that some governors are modular and it may be necessary to load a
402 Per-Entity Load Tracking (PELT) metric for the root control group of the
403 given CPU as the CPU utilization estimate (see the *Per-entity load tracking*
441 This governor uses CPU load as a CPU frequency selection metric.
443 In order to estimate the current CPU load, it measures the time elapsed between
446 time to the total CPU time is taken as an estimate of the load.
448 If this governor is attached to a policy shared by multiple CPUs, the load is
449 estimated for all of them and the greatest result is taken as the load estimate
457 irregular. Also, it affects its own CPU load metric by running code that
461 It generally selects CPU frequencies proportional to the estimated load, so that
[all …]
|
| /Documentation/sphinx/ |
| D | load_config.py | 12 u"""Load an additional configuration file into *namespace*.
46 # If there is an extra conf.py file, load it
48 sys.stdout.write("load additional sphinx-config: %s\n" % config_file)
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 51 keyctl add trusted name "load hex_blob [pcrlock=pcrnum]" ring
99 keyctl add encrypted name "load hex_blob" ring
139 Load a trusted key from the saved blob::
141 $ keyctl add trusted kmk "load `cat kmk.blob`" @u
192 Load an encrypted key "evm" from saved blob::
194 $ keyctl add encrypted evm "load `cat evm.blob`" @u
|
| /Documentation/leds/ |
| D | leds-lp5521.rst | 31 disabled, load, run
33 store program (visible only in engine load mode)
38 echo "load" > engine3_mode
|
| /Documentation/riscv/ |
| D | boot-image-header.rst | 17 u64 text_offset; /* Image load offset, little endian */
36 in order to load it as an EFI application. In order to support EFI stub,
61 - Image size is mandatory for boot loader to load kernel image. Booting will
|
12345678910>>...16