Searched full:full (Results 1 – 25 of 788) sorted by relevance
12345678910>>...32
| /Documentation/scheduler/ |
| D | membarrier.rst | 14 require each architecture to have a full memory barrier after coming from
16 rq_lock(); smp_mb__after_spinlock() in __schedule(). The barrier matches a full
24 require each architecture to have a full memory barrier after updating rq->curr,
28 - alpha, arc, arm, hexagon, mips rely on the full barrier implied by
31 - arm64 relies on the full barrier implied by switch_to().
33 - powerpc, riscv, s390, sparc, x86 rely on the full barrier implied by
34 switch_mm(), if mm is not NULL; they rely on the full barrier implied
38 The barrier matches a full barrier in the proximity of the membarrier system call
|
| /Documentation/networking/device_drivers/ethernet/3com/ |
| D | 3c509.rst | 29 - 3c509B (later revision of the ISA card; supports full-duplex)
31 - 3c589B (later revision of the 3c589; supports full-duplex)
47 needed except to enable full-duplex mode (see below). An example of the syntax
62 Full-duplex mode
65 The v1.18c driver added support for the 3c509B's full-duplex capabilities.
66 In order to enable and successfully use full-duplex mode, three conditions
69 (a) You must have a Etherlink III card model whose hardware supports full-
71 positively known to support full-duplex are the 3c509B (ISA bus) and 3c589B
73 full-duplex mode; these include the original 3c509 (no "B"), the original
78 AUI and 10base2 network cabling is physically incapable of full-duplex
[all …]
|
| D | vortex.rst | 128 0x0200 Force full duplex mode.
136 will force full-duplex 100base-TX, rather than allowing the usual
148 full-duplex mode. Please use this in preference to the ``options``
156 Sets full duplex mode for all 3c59x NICs in the machine. Entries
166 full duplex mode.
177 The driver preallocates 32 full-sized (1536 byte) network buffers
179 whether to leave the packet in its full-sized buffer, or to allocate
276 the same network being in full-duplex mode, while this host is in
278 half-duplex mode or fix this host to run in full-duplex mode.
280 As a last resort, you can force the 3c59x driver into full-duplex mode
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
30 to receive data from the hardware. A "full" descriptor has data in it,
32 descriptor is neither empty or full; it is simply not ready. It may
39 buffers, and marks them "full". The OS follows up, taking the full
46 marks it full, and advances the GDACTDPA by one. Thus, when there is
47 flowing RX traffic, every descr behind it should be marked "full",
53 hardware is ahead, the tail pointer will be pointing at a "full"
56 all of the descrs in front of the tail pointer should be "full", and
102 The status x4... corresponds to "full" and status xa... corresponds
109 "full" == SPIDER_NET_DESCR_FRAME_END == 0x4
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-ehci_hcd | 9 "companion" full/low-speed USB-1.1 controllers. When a
11 to the EHCI controller; when a full- or low-speed device
16 at full speed, which can be accomplished by forcing the
24 port 4 on bus 2 to run at full speed::
40 connect at full speed.
|
| D | sysfs-driver-ufs | 20 device descriptor parameters. The full information about
30 device descriptor parameters. The full information about
40 the UFS device descriptor parameters. The full information
51 The full information about the descriptor could be found
61 the UFS device descriptor parameters. The full information
72 The full information about the descriptor could be found
83 parameters. The full information about the descriptor could
95 parameters. The full information about the descriptor could
106 the UFS device descriptor parameters. The full information
116 the UFS device descriptor parameters. The full information
[all …]
|
| /Documentation/devicetree/bindings/iio/afe/ |
| D | voltage-divider.yaml | 14 interesting voltage is often the voltage over the full resistance
55 Resistance Rout over which the output voltage is measured. See full-ohms.
57 full-ohms:
59 Resistance R + Rout for the full divider. The io-channel is scaled by
66 - full-ohms
95 full-ohms = <222>; /* 200 + 22 */
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq27xxx.yaml | 64 - energy-full-design-microwatt-hours
65 - charge-full-design-microamp-hours
67 Both or neither of the *-full-design-*-hours properties must be set.
81 energy-full-design-microwatt-hours = <5290000>;
82 charge-full-design-microamp-hours = <1430000>;
|
| /Documentation/devicetree/bindings/phy/ |
| D | mscc,vsc7514-serdes.yaml | 23 half/full-duplex and 1000Mbps in full-duplex mode while SERDES6G supports
24 10/100Mbps in half/full-duplex and 1000/2500Mbps in full-duplex mode.
|
| /Documentation/devicetree/bindings/net/ |
| D | qcom,qca807x.yaml | 73 qcom,dac-full-amplitude:
75 Set Analog MDI driver amplitude to FULL.
80 With this enabled and qcom,dac-full-bias-current
85 qcom,dac-full-bias-current:
87 Set Analog MDI driver bias current to FULL.
105 - With both FULL amplitude and FULL bias current: bias current
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | cirrus,clps711x-intc.txt | 25 13: URXINT1 UART1 receive FIFO half full
29 17: SS2RX SSI2 receive FIFO half or greater full
32 29: URXINT2 UART2 receive FIFO half full
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 20 establishes the full supervisor context and that event return
21 establishes the full user context.
53 Full supervisor/user context
56 FRED event delivery atomically save and restore full supervisor/user
65 FRED always restores the full value of %rsp, thus ESPFIX is no longer
|
| /Documentation/accounting/ |
| D | psi.rst | 43 full avg10=0.00 avg60=0.00 avg300=0.00 total=0
48 The "full" line indicates the share of time in which all non-idle
55 stall state is tracked separately and exported in the "full" averages.
57 CPU full is undefined at the system level, but has been reported
83 <some|full> <stall amount in us> <time window in us>
87 1sec time window. Writing "full 50000 1000000" into /proc/pressure/io
88 would add 50ms threshold for full io stall measured within 1sec time window.
|
| /Documentation/input/devices/ |
| D | yealink.rst | 10 - keyboard full support, yealink.ko / input event API
11 - LCD full support, yealink.ko / sysfs API
12 - LED full support, yealink.ko / sysfs API
13 - dialtone full support, yealink.ko / sysfs API
14 - ringtone full support, yealink.ko / sysfs API
15 - audio playback full support, snd_usb_audio.ko / alsa API
16 - audio record full support, snd_usb_audio.ko / alsa API
|
| /Documentation/litmus-tests/atomic/ |
| D | cmpxchg-fail-unordered-1.litmus | 7 * full barrier. (In contrast, a successful cmpxchg() does act as a
8 * full barrier.)
|
| /Documentation/images/ |
| D | COPYING-logo | 1 This is the full-colour version of the currently unofficial Linux logo
9 you want to use it for: for the full range of logos take a look at
|
| /Documentation/power/ |
| D | power_supply_class.rst | 83 this attribute represents operating status (charging, full,
107 "full"/"empty" at normal conditions. Yes, there is no direct relation
125 design charge values, when battery considered full/empty.
132 became full/empty". It also could mean "value of charge when battery
133 considered full/empty at given conditions (temperature, age)".
141 be negative; there is no empty or full value. It is only useful for
213 seconds left for battery to be considered full
273 in percents, but provides charge_{now,full,empty}. Should I calculate
285 voltage and so on. But full-fledged battery model is likely not subject
|
| /Documentation/networking/device_drivers/can/ |
| D | can327.rst | 29 into full fledged (as far as possible) CAN interfaces.
33 order to fake full-duplex operation.
187 If the ELM327's internal UART sending buffer runs full, it will abort
188 the monitoring mode, print "BUFFER FULL" and drop back into command
193 12 34 56 78 8 DEADBEEF123 BUFFER FULL
212 Once the bus goes silent, or an error occurs (such as BUFFER FULL),
223 No full duplex operation is supported. The driver will switch
291 load, resulting in the "``BUFFER FULL``" message. Using the hardware
314 the host (BUFFER FULL).
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-dma.yaml | 35 0x0: 1/4 full FIFO
36 0x1: 1/2 full FIFO
37 0x2: 3/4 full FIFO
38 0x3: full FIFO
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta350.txt | 23 0: 2-channel (full-bridge) power, 2-channel data-out
24 1: 2 (half-bridge). 1 (full-bridge) on-board power
25 2: 2 Channel (Full-Bridge) Power, 1 Channel FFX
53 - "full-power-mode"
121 // (full-bridge) power,
|
| D | st,sta32x.txt | 27 0: 2-channel (full-bridge) power, 2-channel data-out
28 1: 2 (half-bridge). 1 (full-bridge) on-board power
29 2: 2 Channel (Full-Bridge) Power, 1 Channel FFX
91 // (full-bridge) power,
|
| /Documentation/networking/devlink/ |
| D | iosm.rst | 25 - erase_full_flash parameter is used to check if full erase is required for
27 If set, Full nand erase command will be sent to the device. By default,
75 2) If user want to do a full erase, below command need to be issued to set the
76 erase full flash param (To be set only if full erase required).
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 7 by the device itself. The full description of the bitfields
21 by the device itself. The full description of the bitfields
|
| /Documentation/devicetree/bindings/display/connector/ |
| D | dp-connector.yaml | 20 - full-size
46 type = "full-size";
|
| /Documentation/spi/ |
| D | spidev.rst | 7 full duplex transfers and device I/O configuration are also available.
113 the chipselect is deactivated between those operations. Full-duplex access,
131 which will return (RD) or assign (WR) the full SPI transfer mode,
174 FULL DUPLEX CHARACTER DEVICE API
178 full duplex programming interface. (Although it doesn't perform a full duplex
190 To make a full duplex request, provide both rx_buf and tx_buf for the
|
12345678910>>...32