Searched full:delivery (Results 1 – 25 of 80) sorted by relevance
1234
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 4 Flexible Return and Event Delivery (FRED)
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
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-type-t.rst | 28 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` equivalent
76 ioctl's, using the :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
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
91 :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` property.
|
| D | frontend-property-satellite-systems.rst | 6 Properties used on satellite delivery systems
12 DVB-S delivery system
19 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
49 DVB-S2 delivery system
71 Turbo code delivery system
82 ISDB-S delivery system
89 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
|
| D | frontend-property-cable-systems.rst | 6 Properties used on cable delivery systems
12 DVB-C delivery system
26 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
50 DVB-C Annex B delivery system
60 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
|
| D | frontend-property-terrestrial-systems.rst | 6 Properties used on terrestrial delivery systems
12 DVB-T delivery system
19 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
51 DVB-T2 delivery system
61 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
95 ISDB-T delivery system
126 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
184 ATSC delivery system
191 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
209 ATSC-MH delivery system
[all …]
|
| 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.
23 instead, in order to be able to support the newer System Delivery like
|
| 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.
55 :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` = SYS_DVBC_ANNEX_A
|
| D | fe_property_parameters.rst | 51 #. 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
180 Used on cable and satellite delivery systems.
190 Used on cable and satellite delivery systems.
[all …]
|
| D | frontend.rst | 9 The Digital TV frontend API was designed to support three groups of delivery
11 delivery systems are supported:
|
| D | legacy_dvb_apis.rst | 11 The DVBv3 frontend API has issues with new delivery systems, including
|
| 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
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-typec | 57 when both the port and the partner support USB Power Delivery.
75 Power Delivery communication is used for negotiating the levels,
107 Revision number of the supported USB Power Delivery
108 specification, or 0.0 when USB Power Delivery is not supported.
111 - "2.0": USB Power Delivery Release 2.0
112 - "3.0": USB Power Delivery Release 3.0
113 - "3.1": USB Power Delivery Release 3.1
119 Revision number of the supported USB Power Delivery
121 Power Delivery is not supported.
124 - "2.0": USB Power Delivery Release 2.0
[all …]
|
| D | sysfs-class-usb_power_delivery | 5 Directory for USB Power Delivery devices.
11 File showing the USB Power Delivery Specification Revision used
19 specific revision of the USB Power Delivery Specification. In
30 Power Delivery Specification. Each PDO - power supply - will
58 The device "1:fixed_supply" is special. USB Power Delivery
|
| D | sysfs-class-fc_host | 21 These files contain the number of delivery related errors
|
| D | sysfs-class-fc_remote_ports | 21 These files contain the number of delivery related errors
|
| /Documentation/devicetree/bindings/usb/ |
| D | mediatek,mt6370-tcpc.yaml | 7 title: MediatTek MT6370 Type-C Port Switch and Power Delivery controller
15 regulators (DSV/VIBLDO), and TypeC Port Switch with Power Delivery controller.
17 Power Delivery controller.
|
| D | mediatek,mt6360-tcpc.yaml | 7 title: Mediatek MT6360 Type-C Port Switch and Power Delivery controller
14 regulators (BUCKs/LDOs), and TypeC Port Switch with Power Delivery controller.
15 This document only describes MT6360 Type-C Port Switch and Power Delivery controller.
|
| D | richtek,rt1711h.yaml | 7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
16 delivery protocol to allow up to 100W of power. The BMC PD block enables full
|
| D | ti,tps6598x.yaml | 7 title: Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
13 Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ce4100-lapic.yaml | 43 description: Intel defines a few possible interrupt delivery
45 delivery modes are possible.
47 Virtual Wire Mode - use lapic as virtual wire interrupt delivery mode.
51 But if this optional boolean property is set, then the interrupt delivery
|
| /Documentation/networking/pse-pd/ |
| 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 …]
|
| 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
|
| /Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 101 delivery support.
107 Type-C Cable and Connector specification, when Power Delivery is not
116 description: Set this property if the Type-C connector has no power delivery support.
120 # delivery support.
125 "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
137 "USB Power Delivery Specification Revision 2.0, Version 1.3" chapter 6.4.4.3.1 Discover
216 of "USB Power Delivery Specification Revision 3.0, Version 1.2" provides the
235 state as defined in 7.4.2 Sink Electrical Parameters of USB Power Delivery Specification
243 description: A child node to contain all the selectable USB Power Delivery capabilities.
249 Power Delivery capability.
[all …]
|
| /Documentation/driver-api/usb/ |
| D | typec.rst | 42 Delivery Specification ch. 2.4) will be named "port0-plug0" and on the SOP
90 If the partner is USB Power Delivery capable, and the port driver is able to
102 After successful connection of a cable that supports USB Power Delivery
108 latest USB Power Delivery specification.
123 If the cable is USB Power Delivery capable, and the port driver is able to show
158 Delivery Structured VDM Discover SVIDs message, each SVID needs to be
|
| /Documentation/virt/kvm/x86/ |
| 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.
|
1234