Home
last modified time | relevance | path

Searched refs:delivery (Results 1 – 25 of 85) sorted by relevance

1234

/linux/Documentation/arch/x86/x86_64/
H A Dfred.rst15 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 Dpse-pi.rst10 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 Dintroduction.rst24 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 Dfrontend-property-satellite-systems.rst6 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 Dfe-type-t.rst80 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 Dfrontend-property-terrestrial-systems.rst6 Properties used on terrestrial delivery systems
12 DVB-T delivery system
51 DVB-T2 delivery system
95 ISDB-T delivery system
184 ATSC delivery system
209 ATSC-MH delivery system
262 DTMB delivery system
H A Dfe_property_parameters.rst51 #. For satellite delivery systems, the frequency is in kHz.
53 #. For cable and terrestrial delivery systems, the frequency is in
56 #. On most delivery systems, the frequency is the center frequency
74 Specifies the frontend modulation type for delivery systems that
83 supported by each delivery system, as currently defined by specs.
105 delivery system enum value is used (SYS_DVBS2).
119 Should be set only for terrestrial delivery systems.
145 #. On Satellite and Cable delivery systems, the bandwidth depends on
179 Used on cable and satellite delivery systems.
189 Used on cable and satellite delivery systems.
[all …]
H A Dfrontend-property-cable-systems.rst6 Properties used on cable delivery systems
12 DVB-C delivery system
50 DVB-C Annex B delivery system
H A Ddvbproperty.rst18 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 Ddvb-frontend-parameters.rst13 per-system parameters. However, as newer delivery systems required more
19 existing delivery systems, and to add newer delivery systems.
H A Dfrontend.rst9 The Digital TV frontend API was designed to support three groups of delivery
11 delivery systems are supported:
H A Dlegacy_dvb_apis.rst11 The DVBv3 frontend API has issues with new delivery systems, including
H A Dfrontend-stat-properties.rst12 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 Dfe-get-property.rst40 depends on the delivery system and on the device:
/linux/net/sctp/
H A DKconfig26 -- sequenced delivery of user messages within multiple streams,
27 with an option for order-of-arrival delivery of individual user
/linux/Documentation/virt/kvm/x86/
H A Dmsr.rst214 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/testing/
H A Dsysfs-class-typec240 of showing the result of Discover Identity USB power delivery
242 delivery is supported, for example when USB power delivery
322 of showing the result of Discover Identity USB power delivery
324 delivery is supported, for example when USB power delivery
H A Dsysfs-class-fc_host21 These files contain the number of delivery related errors
H A Dsysfs-class-fc_remote_ports21 These files contain the number of delivery related errors
/linux/net/rds/
H A DKconfig8 sequenced delivery of datagrams over Infiniband or TCP.
/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8996-v3.0.dtsi15 * when it comes to voltage delivery to.. once again
/linux/Documentation/arch/riscv/
H A Dzicfiss.rst138 :c:macro:`SEGV_CPERR` and follow the normal course of signal delivery.
188 As part of signal delivery, the shadow stack token is saved on the
192 for signal delivery. During :c:macro:`sigreturn`, kernel will obtain
/linux/security/smack/
H A DKconfig51 receiving process. If this option is selected, the delivery
/linux/Documentation/ABI/obsolete/
H A Dsysfs-class-typec18 USB power delivery command.
/linux/Documentation/translations/zh_CN/core-api/irq/
H A Dirq-domain.rst196 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)

1234