| /linux/Documentation/arch/x86/x86_64/ |
| H A D | fred.rst | 15 delivery through the interrupt descriptor table (IDT event
16 delivery) and event return by the IRET instruction with lower
19 2) Improve software robustness by ensuring that event delivery
24 delivery and, for returning from events, two FRED return instructions.
25 FRED event delivery can effect a transition from ring 3 to ring 0, but
29 event delivery and the FRED return instructions are FRED transitions.
56 FRED event delivery atomically save and restore full supervisor/user
57 context upon event delivery and return. Thus it avoids the problem of
77 Because FRED event delivery from ring 3 and ERETU both swap the value
90 event delivery. If unchanged, the CPU keeps using the current event
[all …]
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 10 connection scheme is crucial for enabling the delivery of power alongside data
20 systems that utilize two pairs for power delivery.
33 assignments for power delivery, as described in the PSE PI for multi-pair
41 Ethernet cables. It details two main configurations for power delivery, known
51 The power delivery's polarity in this alternative can vary based on the MDI
91 - "-" indicates that the pin is not used for power delivery in that
129 the Ethernet PHY for data transmission and the PSE PI for power delivery.
160 power delivery through the data-carrying pairs of an Ethernet cable, suitable
181 - Pins 1 and 2, as well as pins 3 and 6, are utilized for power delivery in
192 additional power delivery capabilities such as 2-pair or 4-pair power delivery.
[all …]
|
| H A D | introduction.rst | 24 and data delivery over a single pair is advantageous.
29 Key addenda to the IEEE 802.3-2018 standard relevant to power delivery over
35 covered in Clause 33, increasing power delivery to up to 30W.
60 These entities enable power delivery using the same generic cabling as for data
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend-property-satellite-systems.rst | 6 Properties used on satellite delivery systems
12 DVB-S delivery system
49 DVB-S2 delivery system
71 Turbo code delivery system
82 ISDB-S delivery system
|
| H A D | fe-type-t.rst | 80 used to contain ``fe_type_t`` field to indicate the delivery systems,
83 is deprecated, as it can report just one delivery system, but some
84 devices support multiple delivery systems. Please use
87 On devices that support multiple delivery systems, struct
|
| H A D | frontend-property-cable-systems.rst | 6 Properties used on cable delivery systems
12 DVB-C delivery system
50 DVB-C Annex B delivery system
|
| H A D | dvbproperty.rst | 18 ATSC delivery systems grouped there. The problem is that, as the second
32 with supports all digital TV delivery systems.
43 3. Nowadays, most frontends support multiple delivery systems.
45 the multiple delivery systems supported by a frontend.
|
| H A D | dvb-frontend-parameters.rst | 13 per-system parameters. However, as newer delivery systems required more
19 existing delivery systems, and to add newer delivery systems.
|
| H A D | frontend.rst | 9 The Digital TV frontend API was designed to support three groups of delivery
11 delivery systems are supported:
|
| H A D | legacy_dvb_apis.rst | 11 The DVBv3 frontend API has issues with new delivery systems, including
|
| H A D | frontend-stat-properties.rst | 12 For most delivery systems, ``dtv_property.stat.len`` will be 1 if the
16 It should be noted, however, that new OFDM delivery systems like ISDB
22 So, in order to be consistent with other delivery systems, the first
|
| H A D | fe-get-property.rst | 40 depends on the delivery system and on the device:
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fc_host | 21 These files contain the number of delivery related errors
|
| H A D | sysfs-class-fc_remote_ports | 21 These files contain the number of delivery related errors
|
| /linux/net/rds/ |
| H A D | Kconfig | 8 sequenced delivery of datagrams over Infiniband or TCP.
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | msm8996-v3.0.dtsi | 15 * when it comes to voltage delivery to.. once again
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | msr.rst | 214 present in CPUID. Bit 3 enables interrupt based delivery of 'page ready'
219 #PF exception. During delivery of these events APF CR2 register contains
244 ready' APF delivery needs to be written to before enabling APF mechanism
250 bit 3 (interrupt based delivery) is not set APF events are not delivered.
359 Bits 0-7: APIC vector for delivery of 'page ready' APF events.
362 Interrupt vector for asynchnonous 'page ready' notifications delivery.
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-class-typec | 18 USB power delivery command.
|
| /linux/security/smack/ |
| H A D | Kconfig | 51 receiving process. If this option is selected, the delivery
|
| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| H A D | irq-domain.rst | 196 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
|
| /linux/Documentation/networking/ |
| H A D | tcp-thin.rst | 13 on the data delivery latency, packet loss can be devastating for
|
| H A D | representors.rst | 85 corresponds in hardware to delivery directly to the representee VF.
157 either packet metadata or queue configuration marking it for delivery to the
187 that representor netdevice. Thus, if the delivery part of the rule corresponds
193 it to the representee), hardware offload should interpret this as delivery to
|
| /linux/Documentation/devicetree/bindings/scsi/ |
| H A D | hisilicon-sas.txt | 19 - queue-count : number of delivery and completion queues in the controller
|
| /linux/arch/arc/kernel/ |
| H A D | entry.S | 261 ; such as rescheduling/signal-delivery etc.
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | vidtv.rst | 20 particular delivery system.
282 DVB API Version 5.11, Current v5 delivery system: DVBC/ANNEX_A
283 Supported delivery systems:
|