Home
last modified time | relevance | path

Searched +full:try +full:- +full:power +full:- +full:role (Results 1 – 24 of 24) sorted by relevance

/Documentation/devicetree/bindings/usb/
Dqcom,pmic-typec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/qcom,pmic-typec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC based USB Type-C block
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Qualcomm PMIC Type-C block
18 - enum:
19 - qcom,pmi632-typec
20 - qcom,pm8150b-typec
[all …]
Dwillsemi,wusb3801.yaml1 # 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
11 supports role and plug orientation detection using the CC pins. It is
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#
[all …]
Drichtek,rt1711h.txt4 - compatible : Must be "richtek,rt1711h".
5 - reg : Must be 0x4e, it's slave address of RT1711H.
6 - interrupts : <a b> where a is the interrupt number and b represents an
9 Required sub-node:
10 - connector: The "usb-c-connector" attached to the tcpci chip, the bindings
12 Documentation/devicetree/bindings/connector/usb-connector.yaml
18 interrupt-parent = <&gpio26>;
22 compatible = "usb-c-connector";
23 label = "USB-C";
24 data-role = "dual";
[all …]
Danalogix,anx7411.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analogix ANX7411 Type-C controller
10 - Xin Ji <xji@analogixsemi.com>
15 - analogix,anx7411
25 $ref: ../connector/usb-connector.yaml
29 const: usb-c-connector
32 - compatible
33 - reg
[all …]
Drichtek,rt1711h.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
10 - Gene Chen <gene_chen@richtek.com>
13 The RT1711H is a 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 …]
Dmaxim,max33359.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim TCPCI Type-C PD controller
10 - Badhri Jagan Sridharan <badhri@google.com>
12 description: Maxim TCPCI Type-C PD controller
17 - maxim,max33359
27 $ref: ../connector/usb-connector.yaml#
32 - compatible
33 - reg
[all …]
Dnxp,ptn5110.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP PTN5110 Type-C Port Controller
10 - Li Jun <jun.li@nxp.com>
15 - const: nxp,ptn5110
16 - const: tcpci
26 $ref: /schemas/connector/usb-connector.yaml#
30 - compatible
31 - reg
[all …]
Dfcs,fusb302.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Fairchild FUSB302 Type-C Port controller
10 - Rob Herring <robh@kernel.org>
22 vbus-supply:
23 description: VBUS power supply
27 $ref: /schemas/connector/usb-connector.yaml#
31 - compatible
32 - reg
[all …]
Dmediatek,mt6360-tcpc.yaml1 # 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 …]
/Documentation/devicetree/bindings/chrome/
Dgoogle,cros-ec-typec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/chrome/google,cros-ec-typec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benson Leung <bleung@chromium.org>
11 - Prashant Malani <pmalani@chromium.org>
17 cros-ec node like google,cros-ec-spi.
21 const: google,cros-ec-typec
23 '#address-cells':
26 '#size-cells':
[all …]
/Documentation/ABI/testing/
Dsysfs-class-typec1 USB Type-C port devices (eg. /sys/class/typec/port0/)
8 requesting data role swapping on the port. Swapping is supported
11 notified about role changes so that poll(2) on the attribute
12 wakes up. Change on the role will also generate uevent
13 KOBJ_CHANGE on the port. The current role is show in brackets,
22 The supported power roles. This attribute can be used to request
23 power role swap on the port. Swapping is supported as
26 notified about role changes so that poll(2) on the attribute
27 wakes up. Change on the role will also generate uevent
28 KOBJ_CHANGE. The current role is show in brackets, for example
[all …]
Dsysfs-bus-pci4 Contact: linux-pci@vger.kernel.org
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-pci@vger.kernel.org
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
[all …]
/Documentation/devicetree/bindings/connector/
Dusb-connector.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
20 - enum:
21 - usb-a-connector
22 - usb-b-connector
23 - usb-c-connector
25 - items:
[all …]
/Documentation/driver-api/usb/
Dtypec.rst3 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 …]
Ddwc3.rst15 1. Peripheral-only configuration
16 2. Host-only configuration
17 3. Dual-Role configuration
46 pipe - ep0)
49 4. Scatter-list support
54 8. Link Power Management
58 These features have all been exercised with many of the **in-tree**
67 for new-comers to read the code and understand how it behaves.
83 ---------------------------------
88 receive a Mass Storage *CBW* [#cbw]_, req->length must either be set
[all …]
/Documentation/devicetree/bindings/mfd/
Dmediatek,mt6370.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
13 MT6370 is a highly-integrated smart power management IC, which includes a
14 single cell Li-Ion/Li-Polymer switching battery charger, a USB Type-C &
15 Power Delivery (PD) controller, dual flash LED current sources, a RGB LED
26 wakeup-source: true
31 interrupt-controller: true
33 "#interrupt-cells":
[all …]
Dmediatek,mt6360.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Gene Chen <gene_chen@richtek.com>
25 wakeup-source: true
30 interrupt-names:
33 interrupt-controller: true
35 "#interrupt-cells":
41 $ref: /schemas/regulator/mt6360-regulator.yaml#
44 $ref: /schemas/power/supply/mt6360_charger.yaml#
[all …]
/Documentation/maintainer/
Dfeature-and-driver-maintainers.rst1 .. SPDX-License-Identifier: GPL-2.0
34 reviewers should try to respond quicker than what is the usual patch
36 may range from two working days for fast-paced subsystems (e.g. networking)
40 --------------------------
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
46 `lei <https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started>`_.
52 -------
56 multiple drivers - whether to provide a review is left to the maintainer.
58 When there are multiple maintainers for a piece of code an ``Acked-by``
59 or ``Reviewed-by`` tag (or review comments) from a single maintainer is
[all …]
/Documentation/driver-api/driver-model/
Dplatform.rst6 platform bus: platform_device, and platform_driver. This pseudo-bus
8 like those used to integrate peripherals on many system-on-chip
16 entities in the system. This includes legacy port-based devices and
18 into system-on-chip platforms. What they usually have in common
39 provide probe() and remove() methods. They support power management
62 Or, in common situations where the device is known not to be hot-pluggable,
86 As a rule, platform specific (and often board-specific) setup code will
102 a kernel for a specific target board. Such board-specific kernels are
111 which are normally kept off until they're actively needed (to save power).
113 calls to clk_get(&pdev->dev, clock_name) return them as needed.
[all …]
/Documentation/admin-guide/pm/
Dcpuidle.rst1 .. SPDX-License-Identifier: GPL-2.0
24 generally allows power drawn by the processor to be reduced and, in consequence,
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
46 Second, if the processor is multi-core, each core in it is able to follow at
61 Finally, each core in a multi-core processor may be able to follow more than one
66 multiple individual single-core "processors", referred to as *hardware threads*
67 (or hyper-threads specifically on Intel hardware), that each can follow one
78 ---------
[all …]
/Documentation/networking/device_drivers/can/ctu/
Dctucanfd-driver.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
59 it allows for device hot-plug.
[all …]
/Documentation/driver-api/surface_aggregator/
Dinternal.rst1 .. SPDX-License-Identifier: GPL-2.0+
54 internal-api
63 Lower-level packet transport is implemented in the *packet transport layer
68 packet payloads to higher-level layers.
71 around command-type packet payloads, i.e. requests (sent from host to EC),
90 Refer to Documentation/driver-api/surface_aggregator/client.rst for
93 that chapter and the Documentation/driver-api/surface_aggregator/ssh.rst
104 -------
153 ------------
163 re-submitted to this queue due to timeouts or NAK packets sent by the EC.
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]
/Documentation/filesystems/xfs/
Dxfs-online-fsck-design.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
66 - Examine resource usage.
79 cross-references different types of metadata records with each other to look
[all …]