| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A 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.
|
| H A 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 …]
|
| H A 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>`
|
| H A 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>`
|
| 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.
55 :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>` = SYS_DVBC_ANNEX_A
|
| H 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 …]
|
| 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.
23 instead, in order to be able to support the newer System Delivery like
|
| /openbmc/linux/drivers/usb/typec/ |
| H A D | Kconfig | 12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
16 USB Power Delivery Specification defines a protocol that can be used
18 partners. USB Power Delivery allows higher voltages then the normal
20 Delivery protocol is also used to negotiate the optional Alternate
21 Modes when they are supported. USB Power Delivery does not depend on
25 USB Type-C and USB Power Delivery Specifications define a set of state
30 Delivery controllers handle the state machines inside their firmware.
31 The USB Type-C and Power Delivery controllers usually function
|
| /openbmc/linux/include/linux/usb/ |
| H A D | typec.h | 104 * struct usb_pd_identity - USB Power Delivery identity data
110 * USB power delivery Discover Identity command response data.
112 * REVISIT: This is USB Power Delivery specific information, so this structure
113 * probable belongs to USB Power Delivery header file once we have them.
187 * @pd_revision: USB Power Delivery Specification revision if supported
201 * @usb_pd: USB Power Delivery support
204 * @pd_revision: USB Power Delivery Specification Revision if supported
229 * @pd_get: Get available USB Power Delivery Capabilities.
230 * @pd_set: Set USB Power Delivery Capabilities.
254 * @pd_revision: USB Power Delivery Specification revision if supported
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/connector/ |
| H A D | usb-connector.yaml | 102 delivery support.
108 Type-C Cable and Connector specification, when Power Delivery is not
117 description: Set this property if the Type-C connector has no power delivery support.
121 # delivery support.
125 in "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.2
137 "Universal Serial Bus Power Delivery Specification" chapter 6.4.1.3
150 "USB Power Delivery Specification Revision 3.0, Version 2.0 + ECNs 2020-12-10"
162 "USB Power Delivery Specification Revision 2.0, Version 1.3" chapter 6.4.4.3.1 Discover
208 of "USB Power Delivery Specification Revision 3.0, Version 1.2" provides the
227 state as defined in 7.4.2 Sink Electrical Parameters of USB Power Delivery Specification
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/usb/ |
| H A 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.
|
| H A 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.
|
| /openbmc/linux/net/sctp/ |
| H A D | ulpqueue.c | 122 /* Clear the partial delivery mode for this socket. Note: This
123 * assumes that no association is currently in partial delivery mode.
171 /* Clear the pd_mode and restart any pending messages waiting for delivery. */
207 /* If we are in partial delivery mode, post to the lobby until in sctp_ulpq_tail_event()
208 * partial delivery is cleared, unless, of course _this_ is in sctp_ulpq_tail_event()
209 * the association the cause of the partial delivery. in sctp_ulpq_tail_event()
216 /* If the association is in partial delivery, we in sctp_ulpq_tail_event()
244 /* Did we just complete partial delivery and need to get in sctp_ulpq_tail_event()
421 * There is a potential to do partial delivery if user sets in sctp_ulpq_retrieve_reassembled()
472 * We can trigger partial delivery only if framgent in sctp_ulpq_retrieve_reassembled()
[all …]
|
| /openbmc/linux/net/ipv4/ |
| H A D | tcp_rate.c | 6 * level, it operates by taking a delivery rate sample for each ACK.
13 * the estimator generates a delivery rate sample. Typically it uses the rate
37 /* Snapshot the current delivery information in the skb, to generate
44 /* In general we need to start delivery rate samples from the in tcp_rate_skb_sent()
73 * delivery information when the skb was last transmitted.
116 /* Update the connection delivery information and generate a rate sample. */
170 * measuring the delivery rate during loss recovery is crucial in tcp_rate_gen()
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | other.json | 6 …"PublicDescription": "Counts Core cycles where the core was running with power-delivery for baseli…
14 …"PublicDescription": "Counts Core cycles where the core was running with power-delivery for licens…
22 …"PublicDescription": "Core cycles where the core was running with power-delivery for license level…
|
| /openbmc/linux/include/xen/interface/hvm/ |
| H A D | params.h | 22 * val[55:0] is a delivery GSI. GSI 0 cannot be used, as it aliases val == 0,
28 * val[55:0] is a delivery PCI INTx line:
36 * if this delivery method is available.
63 * Do not advance a vcpu's time beyond the correct delivery time for
|
| /openbmc/linux/include/net/sctp/ |
| H A D | ulpqueue.h | 51 /* Perform partial delivery. */
54 /* Abort the partial delivery. */
57 /* Clear the partial data delivery condition on this socket. */
|
| /openbmc/linux/drivers/usb/typec/tcpm/ |
| H A D | Kconfig | 84 A Type-C port and Power Delivery driver which aggregates two
86 Type-C port controller and the Power Delivery PHY.
89 mode and Power Delivery support both for VBUS and VCONN.
|
| /openbmc/linux/drivers/usb/typec/tipd/ |
| H A D | Kconfig | 2 tristate "TI TPS6598x USB Power Delivery controller driver"
9 Delivery controller.
|
| /openbmc/linux/include/xen/interface/ |
| H A D | callback.h | 22 /* x86: Callback for event delivery. */
37 /* x86: Callback for NMI delivery. */
58 * NMI callbacks: event delivery is unconditionally disabled.
|
| /openbmc/linux/drivers/media/dvb-core/ |
| H A D | dvb_frontend.c | 189 * Due to DVBv3 API calls, a delivery system should be mapped into one of
190 * the 4 DVBv3 delivery systems (FE_QPSK, FE_QAM, FE_OFDM or FE_ATSC),
1021 dev_dbg(fe->dvb->device, "%s: Clearing cache for delivery system %d\n", in dvb_frontend_clear_cache()
1241 "%s: doesn't know how to handle a DVBv3 call to delivery system %i\n", in dtv_property_cache_sync()
1263 "%s: doesn't know how to handle a DVBv3 call to delivery system %i\n", in dtv_property_legacy_params_sync()
1616 * emulate_delivery_system - emulate a DVBv5 delivery system with a DVBv3 type
1620 * Provides emulation for delivery systems that are compatible with the old
1656 dev_dbg(fe->dvb->device, "%s: change delivery system on cache to %d\n", in emulate_delivery_system()
1663 * dvbv5_set_delivery_system - Sets the delivery system for a DVBv5 API call
1665 * @desired_system: delivery system requested by the user
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | other.json | 6 …"PublicDescription": "Core cycles where the core was running with power-delivery for baseline lice…
14 …"PublicDescription": "Core cycles where the core was running with power-delivery for license level…
22 …"PublicDescription": "Core cycles where the core was running with power-delivery for license level…
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A 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
|