| /linux/drivers/usb/typec/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
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
19 5V, up to 20V, and current up to 5A over the cable. The USB Power
[all …]
|
| H A D | pd.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * USB Power Delivery sysfs entries
33 /* -------------------------------------------------------------------------- */
39 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_DUAL_ROLE)); in dual_role_power_show()
46 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_SUSPEND)); in usb_suspend_supported_show()
53 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_HIGHER_CAP)); in higher_capability_show()
60 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_EXTPOWER)); in unconstrained_power_show()
67 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_USB_COMM)); in usb_communication_capable_show()
74 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_DATA_SWAP)); in dual_role_data_show()
82 return sysfs_emit(buf, "%u\n", !!(to_pdo(dev)->pdo & PDO_FIXED_UNCHUNK_EXT)); in unchunked_extended_messages_supported_show()
[all …]
|
| H A D | class.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * USB Type-C Connector Class
29 /* ------------------------------------------------------------------------- */
66 return partner->identity; in get_pd_identity()
70 return cable->identity; in get_pd_identity()
77 struct typec_port *port = to_typec_port(dev->parent); in get_pd_product_type()
85 if (port->data_role == TYPEC_HOST) in get_pd_product_type()
86 ptype = product_type_ufp[PD_IDH_PTYPE(id->id_header)]; in get_pd_product_type()
88 ptype = product_type_dfp[PD_IDH_DFP_PTYPE(id->id_header)]; in get_pd_product_type()
91 ptype = product_type_cable[PD_IDH_PTYPE(id->id_header)]; in get_pd_product_type()
[all …]
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 PSE Power Interface (PSE PI) Documentation
6 The Power Sourcing Equipment Power Interface (PSE PI) plays a pivotal role in
7 the architecture of Power over Ethernet (PoE) systems. It is essentially a
8 blueprint that outlines how one or multiple power sources are connected to the
9 eight-pin modular jack, commonly known as the Ethernet RJ45 port. This
10 connection scheme is crucial for enabling the delivery of power alongside data
14 ---------------------------
19 - Section "33.2.3 PI pin assignments" covers the pin assignments for PoE
20 systems that utilize two pairs for power delivery.
[all …]
|
| H A D | introduction.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Power Sourcing Equipment (PSE) in IEEE 802.3 Standard
7 --------
9 Power Sourcing Equipment (PSE) is essential in networks for delivering power
11 switches and hubs that supply power to Powered Devices (PDs) such as IP
15 ----------------
18 power alongside data over Ethernet cables, typically associated with Power over
21 PoDL PSE, or Power over Data Lines PSE, specifically denotes PSEs operating
22 with single balanced twisted-pair PHYs, as per Clause 104 of IEEE 802.3. PoDL
23 is significant in contexts like automotive and industrial controls where power
[all …]
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | mediatek,mt6370-tcpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/mediatek,mt6370-tcpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediatTek MT6370 Type-C Port Switch and Power Delivery controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 MediaTek MT6370 is a multi-functional device.
15 regulators (DSV/VIBLDO), and TypeC Port Switch with Power Delivery controller.
16 This document only describes MT6370 Type-C Port Switch and
17 Power Delivery controller.
[all …]
|
| H A D | mediatek,mt6360-tcpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/mediatek,mt6360-tcpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Mediatek MT6360 Type-C Port Switch and Power Delivery controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 Mediatek MT6360 is a multi-functional device. It integrates charger, ADC, flash, RGB indicators,
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.
20 - mediatek,mt6360-tcpc
[all …]
|
| H A D | ti,tps6598x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
21 - ti,tps6598x
22 - apple,cd321x
23 - ti,tps25750
28 - description: main PD controller address
[all …]
|
| H A D | willsemi,wusb3801.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: WUSB3801 Type-C port controller
10 The Will Semiconductor WUSB3801 is a USB Type-C port controller which
12 compatible with the USB Type-C Cable and Connector Specification v1.2.
15 - Samuel Holland <samuel@sholland.org>
20 - willsemi,wusb3801
30 $ref: ../connector/usb-connector.yaml#
33 The managed USB Type-C connector. Since WUSB3801 does not support
[all …]
|
| H A D | richtek,rt1719.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1719 sink-only Type-C PD controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT1719 is a sink-only USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
15 and orientation. It integrates the physical layer of the USB BMC power
16 delivery protocol to allow up to 100W of power. The BMC PD block enables full
17 support for alternative interfaces of the Type-C specification.
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | other.json | 3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 … was running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, …
16 …as running with power-delivery for license level 1. This includes high current AVX 256-bit instru…
25 …as running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture…
30 … "BriefDescription": "Core cycles the core was throttled due to a pending power level request.",
34 …"PublicDescription": "Core cycles the out-of-order engine was throttled due to a pending power lev…
|
| /linux/Documentation/ABI/testing/ |
| H A 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
23 What: /sys/class/usb_power_delivery/.../source-capabilities
28 set of Power Data Objects (PDO), each representing a type of
29 power supply. The order of the PDO objects is defined in the USB
30 Power Delivery Specification. Each PDO - power supply - will
33 power supply type name (":" as delimiter).
37 What: /sys/class/usb_power_delivery/.../sink-capabilities
42 of Power Data Objects (PDO) just like with source capabilities,
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | other.json | 3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 … was running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, …
16 …as running with power-delivery for license level 1. This includes high current AVX 256-bit instru…
25 …as running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture…
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | other.json | 3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 … was running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, …
16 …as running with power-delivery for license level 1. This includes high current AVX 256-bit instru…
25 …as running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture…
30 …"BriefDescription": "Counts miscellaneous requests, such as I/O and un-cacheable accesses that hav…
|
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | other.json | 3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 … was running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, …
16 …as running with power-delivery for license level 1. This includes high current AVX 256-bit instru…
25 …as running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture…
30 …"BriefDescription": "Counts miscellaneous requests, such as I/O and un-cacheable accesses that hav…
|
| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | other.json | 3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 … was running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, …
16 …as running with power-delivery for license level 1. This includes high current AVX 256-bit instru…
25 …as running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture…
30 …"BriefDescription": "Counts miscellaneous requests, such as I/O and un-cacheable accesses that hav…
|
| /linux/drivers/usb/typec/tcpm/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
28 Type-C functionalities.
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 3 USB Type-C connector class
7 ------------
9 The typec class is meant for describing the USB Type-C ports in a system to the
14 The platforms are expected to register every USB Type-C port they have with the
15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
18 considers the component registering the USB Type-C ports with the class as "port
26 attributes are described in Documentation/ABI/testing/sysfs-class-typec.
29 --------------------
36 "port0-partner". Full path to the device would be
37 /sys/class/typec/port0/port0-partner/.
[all …]
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 The Digital TV frontend API was designed to support three groups of delivery
11 delivery systems are supported:
13 - Terrestrial systems: DVB-T, DVB-T2, ATSC, ATSC M/H, ISDB-T, DVB-H,
16 - Cable systems: DVB-C Annex A/C, ClearQAM (DVB-C Annex B)
18 - Satellite systems: DVB-S, DVB-S2, DVB Turbo, ISDB-S, DSS
20 The Digital TV frontend controls several sub-devices including:
22 - Tuner
24 - Digital TV demodulator
26 - Low noise amplifier (LNA)
[all …]
|
| H A D | frontend-stat-properties.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _frontend-stat-properties:
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
32 - ``svalue`` or ``uvalue``, where ``svalue`` is for signed values of
36 - ``scale`` - Scale for the value. It can be:
38 - ``FE_SCALE_NOT_AVAILABLE`` - The parameter is supported by the
42 - ``FE_SCALE_DECIBEL`` - parameter is a signed value, measured in
45 - ``FE_SCALE_RELATIVE`` - parameter is a unsigned value, where 0
[all …]
|
| /linux/drivers/usb/typec/tipd/ |
| H A D | trace.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * TI TPS6598x USB Power Delivery Controller Trace Support
|
| /linux/include/linux/platform_data/ |
| H A D | cros_usbpd_notify.h | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * ChromeOS EC Power Delivery Notifier Driver
|
| /linux/include/linux/usb/ |
| H A D | pd_vdo.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Copyright 2015-2017 Google, Inc
22 * ----------
27 * <10:8> :: object position (1-7 valid ... used for enter/exit mode only)
86 * SVDM Identity request -> response
90 * Response is 4 data objects for Power Delivery 2.0 and Passive Cables for
91 * Power Delivery 3.0. Active Cables in Power Delivery 3.0 have 5 data objects.
112 * --------------------
120 * <15:0> :: USB-IF assigned VID for this cable vendor
163 * -------------
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | richtek,rt6190.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT6190 4-Switch BuckBoost controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT6190 is 4-Switch BuckBoost controller designed for converting input
18 power delivery product.
21 https://www.richtek.com/assets/product_file/RT6190/DS6190-02.pdf
24 - $ref: regulator.yaml#
29 - richtek,rt6190
[all …]
|
| /linux/Documentation/devicetree/bindings/net/pse-pd/ |
| H A D | pse-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/pse-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Power Sourcing Equipment (PSE).
9 description: Binding for the Power Sourcing Equipment (PSE) as defined in the
11 power over twisted pair/ethernet cable. The ethernet-pse nodes should be
12 used to describe PSE controller and referenced by the ethernet-phy node.
15 - Oleksij Rempel <o.rempel@pengutronix.de>
16 - Kory Maincent <kory.maincent@bootlin.com>
[all …]
|