CLAIM FOR PRIORITY

[0001] This application claims the benefit of priority of U.S. Patent Application No.

16/458,024, filed on June 29, 2019, titled“POWER SAVING FOR TYPE-C CONNECTORS,” and which is incorporated by reference in entirety.

BACKGROUND

[0002] The Universal Serial Bus (USB) Type-C interface has grown in popularity.

Various systems may have multiple Type-C ports to meet user demands.

[0003] Based on a detection mechanism defined by the Type-C specification, when no device is attached to a Type-C port, the Configuration Channel (CC) lines of the Type-C port may toggle, which may begin as soon as a corresponding Power Delivery (PD) controller powers on and may proceed until a device is attached, even in Standby and Connected Standby states. Due to this toggling, the PD controller may draw power that amounts to a significant portion of the allowed power dissipation budgets of various systems (even in Standby and Connected Standby states).

[0003] Meanwhile, Type-C ports in a system support a Dual Role Port (DRP) feature by which a Type-C ports may become Upstream Facing Ports (UFPs) that take power, or Downstream Facing Ports (DFPs) that provide power. However, since both ends of Type- C cables are the same, it is possible to connect two Type-C ports of the same system to each other through a Type-C cable. When two Type-C ports of same system are connected together with a cable, one Type-C port may attempt to charge the other Type-C port, and power may be wasted and lost in the associated conversions.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The embodiments of the disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure. However, while the drawings are to aid in explanation and understanding, they are only an aid, and should not be taken to limit the disclosure to the specific embodiments depicted therein.

[0005] Fig. 1 illustrates a top view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure.

[0006] Fig. 2 illustrates a front perspective view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. [0007] Fig. 3 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure.

[0008] Fig. 4 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure.

[0009] Fig. 5 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure.

[0010] Figs. 6A-6B illustrate a design of systems with two Type-C ports, in accordance with some embodiments of the disclosure.

[0011] Figs. 7A-7B illustrate timing diagrams pertaining to two Type-C ports connected to the same system, in accordance with some embodiments of the disclosure.

[0012] Fig. 8 illustrates methods of saving power by turning off Power Delivery

(PD) controller Configuration Channel (CC) circuitry, in accordance with some embodiments of the disclosure.

[0013] Fig. 9 illustrates methods of saving power by synchronizing PD controller

CC circuitry, in accordance with some embodiments of the disclosure.

[0014] Fig. 10 illustrates a computer system or computing device with mechanisms to facilitate power saving in Type-C connectors, in accordance with some embodiments.

DETAILED DESCRIPTION

[0015] In the following description, numerous details are discussed to provide a more thorough explanation of embodiments of the present disclosure. It will be apparent to one skilled in the art, however, that embodiments of the present disclosure may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present disclosure.

[0016] Note that in the corresponding drawings of the embodiments, signals are represented with lines. Some lines may be thicker, to indicate a greater number of constituent signal paths, and/or have arrows at one or more ends, to indicate a direction of information flow. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme.

[0017] Throughout the specification, and in the claims, the term "connected" means a direct electrical, mechanical, or magnetic connection between the things that are connected, without any intermediary devices. The term "coupled" means either a direct electrical, mechanical, or magnetic connection between the things that are connected or an indirect connection through one or more passive or active intermediary devices. The term "circuit" or "module" may refer to one or more passive and/or active components that are arranged to cooperate with one another to provide a desired function. The term "signal" may refer to at least one current signal, voltage signal, magnetic signal, or data/clock signal. The meaning of "a," "an," and "the" include plural references. The meaning of "in" includes "in" and "on."

[0018] The terms "substantially," "close," "approximately," "near," and "about" generally refer to being within +/- 10% of a target value. Unless otherwise specified the use of the ordinal adjectives "first," "second," and "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0019] It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.

[0020] The terms "left," "right," "front," "back," "top," "bottom," "over," "under," and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions.

[0021] For purposes of the embodiments, the transistors in various circuits, modules, and logic blocks are Tunneling FETs (TFETs). Some transistors of various embodiments may comprise metal oxide semiconductor (MOS) transistors, which include drain, source, gate, and bulk terminals. The transistors may also include Tri-Gate and FinFFT transistors, Gate All Around Cylindrical Transistors, Square Wire, or Rectangular Ribbon Transistors or other devices implementing transistor functionality like carbon nanotubes or spintronic devices. MOSFET symmetrical source and drain terminals i.e., are identical terminals and are interchangeably used here. A TFET device, on the other hand, has asymmetric Source and Drain terminals. Those skilled in the art will appreciate that other transistors, for example, Bi-polar junction transistors-BJT PNP/NPN, BiCMOS, CMOS, etc., may be used for some transistors without departing from the scope of the disclosure.

[0022] For the purposes of the present disclosure, the phrases "A and/or B" and "A or B" mean (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, and/or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

[0023] In addition, the various elements of combinatorial logic and sequential logic discussed in the present disclosure may pertain both to physical structures (such as AND gates, OR gates, or XOR gates), or to synthesized or otherwise optimized collections of devices implementing the logical structures that are Boolean equivalents of the logic under discussion.

[0024] A first variety of embodiments may pertain to Power saving in Standby and

Connected Standby modes by turning OFF PD (Power Delivery) controller Configuration Channel (CC) Logic. The USB Type-C specification defines a detection mechanism. When no device is attached to a Type-C port, CC lines of the Type-C port may toggle at about a 100 millisecond (ms) time period, with a duty cycle of 30% to 70%, and may wait for a complementary termination pull-up (RP) or pull-down (RD) upon a device being attached. (E.g., the port may toggle the CC lines between DFP (for exposing a pull-up on a CC line) and UFP (for exposing a pull-down on a CC line), to support a Dual Role Port (DRP) feature). CC line toggling may start as soon as a corresponding PD controller is powered and may proceed until a device is attached.

[0025] A PD controller may be disposed to being on (and thus, to toggling CC lines) even in Standby and Connected Standby states. Meanwhile, due to the toggling of the CC lines, the PD controller may draw an amount of power between 0.5 milliwatts (mW) and 2.0 mW, depending on the PD controller used in the system.

[0026] In complying with industry Connected Standby definitions, for many or most mobile devices, an allowed power dissipation budget may be 5.0 mW. For tablets & dual display devices, an allowed power dissipation budget may be 16 mW, and for personal computers (PCs) and laptops, an allowed power dissipation budget may be around 80 mW. Power dissipation may also depend upon the capacity of battery in the device.

[0027] In general, mobile and tablet devices may have one Type-C port with a PD controller. If the PD controller alone consumes from 0.5 mW to 2.0 mW, that may amount to about 10% to 40% of a system budget power from an allowed power dissipation budget of 5.0 mW for the Connected Standby mode. Meanwhile, since laptops may have three or more Type-C ports, power consumption of an associated PD controller may be from 1.5 mW to 6.0 mW.

[0028] Since Type-C PD controllers may consume more power in Connected

Standby and Standby modes, there may be an advantage in reducing PD controller power when no device is attached.

[0029] For the first variety of embodiments, one of the four ground pins available in the Type-C connector may be used to identify if any device is being attached or detached to the Type-C port (e.g., the Type-C receptacle connector). This ground pin may be used an active-low connection-detection pin (DET#), and may be connected to a PD controller.

When a Type-C connector plug is inserted into a Type-C connector receptacle, the DET# signal may be pulled low, and the PD Controller may thereby determine that a plug event has occurred and may subsequently toggles the CC lines.

[0030] Since the mechanisms disclosed herein may use one of the ground pins from the Type-C Connector for detection of device plug-in events, in order to compensate the return current carrying capacity among the ground pins, the shield pins may be used as ground. In general, the shield pins of Type-C connectors may be tied to ground.

[0031] Advantages of the methods and mechanisms disclosed herein may include:

(1) reduction or elimination of power loss in a Connected Standby state, due to the PD controller not consuming additional power to drive CC lines; (2) these mechanisms may not call for a change of electro-mechanical specifications for Type-C connectors; and (3) since the mechanisms may merely need to connect a pull-up resistor on the PCB of the DET# pin (e.g., one of the ground pins of the Type-C connector), implementation may be

straightforward.

[0032] The proposed mechanisms and methods may to the CC logic in a sleep mode and may inhibit toggling of the CC lines until a Type-C plug is inserted. Once the PD controller detects that a Type-C connector plug has been inserted, CC lines may then be toggled by PD controller.

[0033] Fig. 1 illustrates a top view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. A Type-C connector plug 100 may comprise a metal case 110 and grounding 120. In various embodiments, metal case 110 (which may be a shield) may be grounded on plug 100.

[0034] Fig. 2 illustrates a front perspective view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. A Type-C connector receptacle 200 may comprise a Printed Circuit Board (PCB) 210, a case 220, and various pins 230.

Connector receptacle 200 is shown in the proximity of a Type-C connector plug 290 (which may be substantially similar to connector plug 100).

[0035] In various embodiments, a metal case of a Type-C connector plug (e.g., metal case 110) may be mated with a shield of a Type-C connector receptacle (e.g., case 220), which may be grounded on a PCB of the system (e.g., PCB 210) with connector shield pins. On the other side, a metal case on the Type-C connector plug (e.g., metal case 110) may be grounded on a PCB of the Type-C plug.

[0036] For the Type-C connector plug PCB, one side of the PCB may be connected to Type-C connector plug pins (including shield pins), and the other side of the PCB may be connected to wires of the Type-C connector cable. This may advantageously ensure that a ground return current carrying capability of the Type-C connector cable and the Type-C connector satisfy the specification.

[0037] In various embodiments, the Type-C receptacle connector may have power pins and ground pins that are of longer lengths compared to other signal pins (e.g., CC signal pins, USB pins, and so forth). Accordingly, the power pins and ground pins may mate first when a Type-C connector plug is inserted, and break last when the Type-C connector plug is removed. A typical differential in contact time between the power pins and the signals pins may be on the order of milliseconds. This time may be sufficient to wake a CC control logic and start to toggle the CC lines before the CC pins contact Type-C connector plug.

Accordingly, the mechanisms disclosed herein may advantageously not add delay to Type-C CC detection mechanisms.

[0038] Fig. 3 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. A design 300 may comprise a PD controller 310, a CC logic 320, a receptacle pinout 330, CC lines 340, a DET# line 350, and a pull-up resistor Rpu 360.

[0039] PD controller 310 may comprise CC logic 320. CC lines 340 (e.g., a CC_1 line and a CC_2 line) may extend between CC pins of receptacle pinout 330 on one end, and PD controller 310 and/or CC logic 320 on the other end. DET# line 350 may extend between one of four ground pins of receptacle pinout 330 on one end (e.g., pin B12, or Al, or A12, or Bl), and PD controller 310 and/or CC logic 320 on the other end. Rpu 360 may extend between DET# line 350 on one and a supply voltage Vcc on the other end.

[0040] Accordingly, in DET# 350 may by default be pulled up to Vcc. When a

Type-C connector plug is inserted into the Type-C connector receptacle, the Type-C connector plug will pull DET# 350 to a low voltage value (e.g., because ground pins on the Type-C connector plug PCB may be grounded, and may make DET# 350 transition to the low voltage value as soon as the Type-C connector plug is inserted). As soon as DET# 350 goes low, PD controller 310 may toggling CC lines 340 for orientation and/or role identification.

[0041] Since the mechanisms disclosed herein may be using one of the ground pins

(e.g., of receptacle pinout 330) for determining Type-C connector plug insertion into a Type- C connector receptacle, it may reduce a return current carrying capability of a Type-C connector. In various embodiments, this may be compensated by shield pins of the Type-C connector receptacle. In general, all shield pins of the Type-C connector receptacle may be tied to ground.

[0042] Fig. 4 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. A design 400 may comprise a PD controller 410, a CC logic 420, a receptacle pinout 430, CC lines 440, a DET# line 450, and a pull-up resistor Rpu 460. These portions of design 400 may be substantially similar to similarly-named portions of design 300.

[0043] However, in contrast to design 300, design 400 comprises a switch 472, which may be operable to couple or connect the corresponding ground pin of receptacle pinout 430 (e.g., pin B 12, or Al, or A12, or Bl) either to ground, or to DET# line 450.

Switch 472 may be controlled by a SW_CNTRL line 474 from PD controller 410.

[0044] When a Type-C connector plug is inserted into the Type-C connector receptacle, PD controller 410 may control switch 472 such that DET# line 450 from PD controller 410 is connected to the corresponding ground pin of receptacle pinout 430 (e.g., pin B12). By default, when no Type-C connector plug is inserted, DET# line 450 may be pulled to Vcc, which may make PD controller 410 not toggle CC lines 440. As soon as a Type-C connector plug is inserted into the Type-C connector receptacle, DET# line 450 may be pulled to a low voltage level. When PD controller 410 sees that low voltage level on DET# line 450 (which may be 0 volts (V), or a voltage corresponding with a logic 0), PD controller 410 may start to toggle CC lines 440. Once a device is attached with the help of CC lines 440, PD controller 410 may drive SW_CNTRL line 474 to make the corresponding ground pin of receptacle pinout 430 (e.g., pin B 12) connected to ground instead of DET# line 450.

[0045] In some embodiments, Type-C connector receptacles may be modified by adding a spring case contact and a pin for the spring case contact. The pin of the spring case contact may again connect to PD controller 410, and the pin may be pulled to Vcc. When no Type-C connector plug is inserted, the spring may be ideal and PD controller 410 may refrain from toggling the CC logic. As soon as a Type-C connector plug is inserted into the Type-C connector receptacle, the plug may push the spring and make contact with the metal case, which may make PD controller 410 see a low voltage level (e.g., 0 V, or a logic 0) on the spring contact pin. Then PD controller 410 may then start toggling CC logic 420 for orientation and/or role identification.

[0046] For some embodiments (e.g., near-future embodiments), one or more pins may be added to Type-C connector receptacles for the detection of Type-C connector plug insertion.

[0047] Fig. 5 illustrates a schematic view of a Type-C receptacle connector, in accordance with some embodiments of the disclosure. A design 500 may comprise a PD controller 510, a CC logic 520, a receptacle pinout 530, CC lines 540, a DET# line 550, and a pull-up resistor Rpu 560. These portions of design 500 may be substantially similar to similarly-named portions of design 300.

[0048] However, in contrast to design 300, design 500 comprises a switch 582 and a control logic 584. When no Type-C connector plug is inserted into the Type-C connector receptacle, since control logic 584 and other end of the Type-C connector have no connection, with the help of Rpu 560, DET# line 550 may be sampled high by PD controller 510. When no Type-C connector plug is inserted, PD controller 510 may disable CC logic 520 (e.g., to save the power).

[0049] When a Type-C connector plug is inserted into the Type-C connector receptacle, the corresponding ground pin of receptacle pinout 530 (e.g., pin B 12) may get connected to ground internally in the Type-C connector plug. Control logic 584 may connect the corresponding ground pin (e.g., pin B 12) to a board ground, and at the same time, DET# line 550 may be sampled low by PD controller 510. Once DET# signal 550 is low, PD controller 510 may start toggling CC logic 540 for orientation.

[0050] The mechanisms may accordingly refrain from using CC logic 520 for disabling ground connection, providing a fully-hardware mechanism which may

advantageously not depend upon PD firmware and/or any other platform component.

[0051] With respect to Figs. 3-5, in a variety of embodiments, an apparatus may comprise an interface to a CC signal path (e.g., to one of CC lines 340) and to a ground signal path (e.g., a corresponding ground pin, such as pin B12) of a USB Type-C connector port, a first circuitry, and a second circuitry. The first circuitry (which may be substantially similar to, e.g., CC logic 320) may be operable to place toggled values on the CC signal path. The second circuitry (which may be a wire or a signal path of design 300) may be operable to couple the ground signal path to a detection signal path. The placement of the toggled values on the CC signal path may be enabled (e.g., by a PD controller 310) when the detection signal path carries a first value (e.g., a logic low level, or a value of“0”) corresponding with the USB Type-C connector port being connected to a USB Type-C device. In contrast, the placement of the toggled values on the CC signal path may be disabled when the detection signal path carries a second value (e.g., a value other than a logic low value, such as a logic high value, or a value of“1”) corresponding with the USB Type-C connector port not being connected to a USB Type-C device.

[0052] In some embodiments, the first circuitry may be part of a PD controller. For some embodiments, a power delivered to the first circuitry may be disabled when the detection signal path carries the second value. In some embodiments, the CC signal path may be a first CC signal path (e.g., a“CC1” signal path); and the interface may also be to a second CC signal path (e.g., a“CC2” signal path).

[0053] For some embodiments, the first circuitry may place toggled values on the second CC signal path. In some embodiments, the placement of the toggled values on the second CC signal path may be enabled when the detection signal path carries the first value, and the placement of the toggled values on the second CC signal path may be disabled when the detection signal path carries the second value.

[0054] In some embodiments, the detection signal path may be coupled by a resistor element to a power supply voltage rail VCC. Some embodiments may comprise a software- controllable signal coupled to the second circuitry (e.g., SW_CNTRL line 474). Upon the software-controllable signal having a predetermined value, the second circuitry may be operable to place the first value on the detection signal path.

[0055] A second variety of embodiments may pertain to Power saving in Standby and Connected Standby modes by synchronizing PD controller CC Logic. All Type-C ports in a system may support DRP (Dual Role Port) roles. In one role, if an external Type-C wall adaptor is connected (for example), the system may become a UFP and may start taking power from the wall adaptor. In another role, on the same port, when a flash drive is connected (for example), the system may become a DFP, and may start providing power to the flash drive. Moreover, in comparison with legacy Type-A (Host) to Type-B (Slave) cables, both ends of Type-C cables are the same, which may advantageously make connection of any two Type-C ports easy.

[0056] Meanwhile, systems may have multiple Type-C ports. For example, some systems may have one Type-C port for charging, one Type-C port for external display, and another Type-C port for connecting low speed peripherals (e.g., a mouse or a keyboard).

[0057] Since all Type-C ports support the DRP feature, and due to the similarity of the two ends of Type-C cables, it is possible to physically connect two Type-C ports of the same system to each other through a Type-C cable. In accordance with the DRP feature, both ports may then toggle between an offer to play the UFP role and an offer to play the DFP role. If the ports are toggling between offering to play the UFP role and offering to play the DFP role asynchronously with respect to each other, there may be a time when their offers are not conflicting (e.g., complementary termination is detected).

[0058] Accordingly, when two Type-C ports of same system are connected together with a cable, they may eventually connect such that one Type-C port may charge the other Type-C port. Since the received power generally goes through a battery charger (either buck or boost), power losses may be increased due to the conversion. This may in turn reduce the battery life of the system without doing any work. (In general, charger efficiency may be around 90%, and 5 V regulator may be around 85%. The remaining 10% of the charger and 15% of the 5 V regulator may be converted as a power loss.)

[0059] When connected in such a way, it may be advantageous for one Type-C port to not charge another Type-C port of the same system (which may contribute to power loss due to, for example, buck and boost action by the charger). In other words, it may be advantageous for the DRP-capable Type-C ports of a system to not negotiate between themselves and conclude that one Type-C port should supply power to the other Type-C port.

[0060] For the second variety of embodiments, synchronization between PD controllers of the same system may be implemented so that both ports may offer to play the same role, or expose the same role (e.g., the UFP role or the DFP role) at any point of time. When a first port of the system offers to play the DFP role, if the second port is synchronized with the first port, the second port may also offer to play the DFP role. Similarly, when the first port of the system offers to play the UFP role, if the second port is synchronized with the first port, the second port may also offer to play the UFP role. Accordingly, when the first port and the second part are synchronized, if a user connects a Type-C cable between Type-C ports of same system, the ports may both remain nonfunctional, and may instead endlessly negotiate between themselves regarding which will be the DFP and which will be the UFP.

[0061] Advantages of the mechanisms and methods disclosed herein may include:

(1) reduction or elimination of power loss due to one Type-C port of the system supplying power to another Type-C port of the system; (2) straightforward implementation, which may use merely one common synchronization signal between PD controllers of different ports; and (3) users may potentially recognize that the nonfunctional ports indicate an invalid connection of Type-C ports, and may cease and/or refrain from connecting the ports in that manner.

[0062] Moreover, there may be various advantages to implementing the mechanisms and methods disclosed herein in hardware. First of all, for software implementations, a PD controller may go to an attach state and may activate a Type-C state machine that may be implemented in a microcontroller. For such PD controllers, power consumption in the attach state may be from around 3.0 mW to 6.0 mW (compared to around 0.5 mW in a non-attach state), and an additional 1.0 mW may be consumed by Rp and Rd voltage-divider resistors (PD controllers being attached). Since two PD controllers are looped back, the power consumption may be double (e.g., from around 7.0 mW to 13.0 mW). This power consumption may exist until a user disconnects. Such power consumption levels would be quite large considering the Connected Standby and Standby specifications. In comparison, a hardware-implementation PD controller might never go to an attach state, so power consumption may be negligible [0063] Secondly, software implementations may wake a system. In comparison, in hardware implementations, PD controllers might not come to know if any two Type-C ports are looped back with a cable, and may not go to an attach state. Waking the system from sleep states and Connected Standby states may accordingly be avoided.

[0064] Figs. 6A-6B illustrate a design of systems with two Type-C ports, in accordance with some embodiments of the disclosure. With respect to Fig. 6A, in a design 610, a first PD controller 611 and a second PD controller 612. First controller 611 may be coupled to a first USB Type-C connector port 613, and second controller 612 may be coupled to a second USB Type-C connector port 614. First Type-C connector port 613 may be connected to second Type-C connector port 614 via a Type-C cable 615.

[0065] In design 610, when a user connects Type-C ports of the same system to each other (whether intentionally or unintentionally), per specification, both may wait for complementary termination (e.g., they wait for the UFP/DFP roles of the DRP feature to be established). Eventually, if the ports are not synchronized, complementary termination may occur, at which point the ports will be connected.

[0066] Having established this kind of connection, one port may then become a sink for power (e.g., second Type-C connector port 614) and the other port may then become a source for power (e.g., first Type-C connector port 613). The same battery may then discharge, and charge again with the same power, which may result in a power loss to the system (e.g., due to power regulator conversion, such as buck and/or boost), and the battery life of system may be reduced without doing any work. (In general, charger efficiencies may be around 90%, and 5 V regulator efficiencies may be around 85%.)

[0067] With respect to Fig. 6B, in a design 620, a first PD controller 621 and a second PD controller 622. First PD controller 621 may be coupled to a first USB Type-C connector port 623, and second PD controller 622 may be coupled to a second USB Type-C connector port 624. First Type-C connector port 623 may be connected to second Type-C connector port 624 via a Type-C cable 625.

[0068] However, in comparison with design 610, design 620 also comprises an embedded controller 627 supplying a synchronization signal 626 to both first PD controller 621 and second PD controller 622. Synchronization signal 626 may accordingly be a common synchronization signal between all PD controllers for Type-C connector ports in a system. [0069] When the system is powered on, all PD controllers (e.g., first PD controller

621 and second PD controller 622) may wait for the assertion of synchronization signal 626 from embedded controller 627. As a result, the assertion of synchronization signal 626 will synchronize all PD controllers, which will in turn synchronize the CC-line signaling between the PD controllers and all the corresponding Type-c connector ports, which will result in the CC lines of the Type-C cable starting to toggle, and being toggled, at the same time and in the same manner. The Type-C connector ports may therefore fail to detect complementary termination, and may remain nonfunctional.

[0070] Accordingly, if a user connects two Type-C connector ports of the same system together (e.g., first Type-C connector port 623 to second Type-C connector port 624), whether intentionally or unintentionally, since both the corresponding PD controllers are synchronized, both the ports will be either be offering to play the DFP role or the UFP roles at any point of time. This situation will prevent the creation of a valid Type-C connection, in compliance with the Type-C specification. Both Type-C connection ports will thus not be connected, and a VBUS voltage will not be supplied (by either port and to either port).

[0071] In some systems, a synchronization signal may be driven by a general- purpose Input/Output signal from a chipset component (e.g., a Platform Controller Hub (PCH)), or by one of the PD controllers.

[0072] Figs. 7A-7B illustrate timing diagrams pertaining to two Type-C ports connected to the same system, in accordance with some embodiments of the disclosure. With respect to Fig. 7A, a timing diagram 710 (which may correspond with design 610) depicts a first CC signal 711 of a first Type-C connection port, a second CC signal 712 of a second Type-C connection port of the same system, and a VBUS signal 713.

[0073] As discussed herein, in general, all Type-C connector ports in a system support DRP roles (e.g., UFP and DFP). At a time when no devices are attached to the first Type-C connection port and the second Type-C connection port, the CC lines for those port (e.g., first CC signal 711 and second CC signal 712) may each toggle between offering to play the DFP role (e.g., by exposing a pull-up on a CC line) and offering to play the UFP role (e.g., by exposing a pull-down on a CC line), at a time interval specified or predetermined by the Type-C specification (e.g., a 100 ms time period, with a duty cycle that may vary from 30% to 70%). Meanwhile, VBUS for both ports (e.g., VBUS signal 713) may be disconnected from the Type-C connector ports and/or the corresponding PD controllers. [0074] At a later time, the Type-C connection ports may be connected to each other through a Type-C cable, and both Type-C connection ports may wait for complimentary termination to decide their roles. Once complementary termination is observed, first CC signal 711 and second CC signal 712 may stop toggling and may settle to a DC voltage level (e.g., based on pull-up and/or pull-down values for the CC lines). VBUS signal 713 may then be provided (e.g., by the first type-C connection port).

[0075] With respect to Fig. 7B, a timing diagram 720 (which may correspond with design 620) depicts a first CC signal 721 of a first Type-C connection port, a second CC signal 722 of a second Type-C connection port of the same system, and a VBUS signal 723.

[0076] In contrast with timing diagram 710, in timing diagram 720, first CC signal

721 and second CC signal 722 are being toggled by synchronized PD controllers. As a result, both first CC signal 721 and second CC signal 722 are toggling at the substantially the same time (e.g., with the same duty cycle), neither port find a complimentary termination, no Type- C connection is formed, CC detection will not work and VBUS will not be supplied.

[0077] With respect to Figs. 6A-7B, in a variety of embodiments, an apparatus may comprise a first interface to a CC signal path of a first USB Type-C connector port, a second interface to a CC signal path of a second USB Type-C connector port, a first circuitry (which may be substantially similar to, e.g., first PD controller 621), a second circuitry (which may be substantially similar to, e.g., second PD controller 622), and a third circuitry (which may be substantially similar to embedded controller 627). The first circuitry may be operable to place toggled values on the CC signal path of the first USB Type-C connector port, in accordance with a first duty cycle. The second circuitry may be operable to place toggled values on the CC signal path of the second USB Type-C connector port, in accordance with a second duty cycle. The third circuitry may be operable to provide a synchronization signal to the first circuitry and the second circuitry. The first circuitry may be operable to begin the first duty cycle based upon the assertion of the synchronization signal.

[0078] In some embodiments, the second circuitry may be operable to begin the second duty cycle based upon the assertion of the synchronization signal. For some embodiments, the third circuitry may comprise an embedded controller that provides the synchronization signal.

[0079] For some embodiments, the first interface may also be to a second CC signal path of the first USB Type-C connector port, and the second interface may also be to a second CC signal path of the second USB Type-C connector port. The first circuitry may be operable to place toggled values on the second CC signal path of the first USB Type-C connector port, in accordance with the first duty cycle, and the second circuitry may be operable to place toggled values on the second CC signal path of the second USB Type-C connector port, in accordance with the second duty cycle.

[0080] In some embodiments, a software-accessible interface to expose the synchronization signal to at least one of: software reads; and software writes. For some embodiments, a VBUS supply voltage rail is supplied for the first interface. In some embodiments, the assertion of the synchronization signal may prevent the VBUS supply voltage from being supplied to the first USB Type-C connector port.

[0081] Fig. 8 illustrates methods of saving power by turning off PD controller CC circuitry, in accordance with some embodiments of the disclosure. A method 800 may comprise a placing 810 and a coupling 815. For some embodiments, method 800 may comprise a placing 820.

[0082] In placing 810, toggled values may be placed on a CC signal path of an interface to a USB Type-C connector port. In coupling 815, a ground signal path of the interface to the USB Type-C connector port may be coupled to a detection signal path. The placement of the toggled values on the CC signal path may be enabled when the detection signal path carries a first value that corresponds with the USB Type-C connector port being connected to a USB Type-C device, and may be disabled when the detection signal path carries a second value that corresponds with the USB Type-C connector port not being connected to a USB Type-C device.

[0083] In some embodiments, the toggled values may be placed on the CC signal path of the interface via a CC logic, and the detection signal path may be coupled by a resistor element to a power supply voltage rail VCC. For some embodiments, a power delivered to the CC logic may be disabled when the detection signal path carries the second value. In some embodiments, the CC signal path may be a first CC signal path, and the interface may also be to a second CC signal path.

[0084] For placing 820, toggled values may be placed on the second CC signal path.

The placement of the toggled values on the second CC signal path may be enabled when the detection signal path carries the first value, and may be disabled when the detection signal path carries the second value. [0085] In some embodiments, upon a software-controllable signal having a predetermined value, the first value may be placed on the detection signal path.

[0086] Fig. 9 illustrates methods of saving power by synchronizing PD controller

CC circuitry, in accordance with some embodiments of the disclosure. A method 900 may comprise a placing 910 and a placing 915. In some embodiments, method 900 may comprise a supplying 920 and a supplying 925.

[0087] In placing 910, toggled values may be placed on a CC signal path of a first interface to a first USB Type-C connector port, in accordance with a first duty cycle. In placing 915, toggled values may be placed on a CC signal path of a second interface to a second USB Type-C connector port, in accordance with a second duty cycle. The first duty cycle may begin based upon the assertion of a synchronization signal.

[0088] In some embodiments, the second duty cycle may begin based upon the assertion of the synchronization signal. For some embodiments, an embedded controller may provide the synchronization signal.

[0089] In some embodiments, the first interface may also be to a second CC signal path of the first USB Type-C connector port, and the second interface may also be to a second CC signal path of the second USB Type-C connector port. For some embodiments, the toggled values may be placed on the second CC signal path of the first USB Type-C connector port, in accordance with the first duty cycle, and the toggled values may be placed on the second CC signal path of the second USB Type-C connector port, in accordance with the second duty cycle. In some embodiments, a software-accessible interface may expose the synchronization signal to software reads and/or software writes.

[0090] For some embodiments, in supplying 920, a VBUS supply voltage rail may be supplied for the first USB Type-C connector port. In some embodiments, the assertion of the synchronization signal may prevent the VBUS supply voltage from being supplied to the first USB Type-C connector port.

[0091] Although the actions in the flowcharts with reference to Figs. 8 and 9 are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed in Figs. 8 and 9 are optional in accordance with certain embodiments. The numbering of the actions presented is for the sake of clarity and is not intended to prescribe an order of operations in which the various actions must occur. Additionally, operations from the various flows may be utilized in a variety of combinations.

[0092] In some embodiments, an apparatus may comprise means for performing various actions and/or operations of the methods of Figs. 8 and 9.

[0093] Moreover, in some embodiments, machine readable storage media may have executable instructions that, when executed, cause one or more processors to perform an operation comprising a method of Figs. 8 and 9. Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any other tangible storage media or non-transitory storage media.

[0094] Fig. 10 illustrates a computer system or computing device with mechanisms to facilitate power saving in Type-C connectors, in accordance with some embodiments. It is pointed out that those elements of Fig. 10 having the same reference numbers (or names) as the elements of any other figure may operate or function in any manner similar to that described, but are not limited to such.

[0095] In some embodiments, a device 1000 may comprise an appropriate computing device, such as a computing tablet, a mobile phone or smart-phone, a laptop, a desktop, an Internet-of-Things (IOT) device, a server, a wearable device, a set-top box, a wireless-enabled e-reader, or the like. It will be understood that certain components are shown generally, and not all components of such a device are shown in device 1000.

[0096] In some embodiments, device 1000 may comprise a System-on-Chip (SoC)

1001. An example boundary of SoC 1001 is depicted using dotted lines in Fig. 10, with some example components depicted as being included within SoC 1001. However, SoC 1001 may include any appropriate components of device 1000.

[0097] In some embodiments, device 1000 may comprise a processor 1004.

Processor 1004 may include one or more physical devices, such as microprocessors, application processors, microcontrollers, programmable logic devices, processing cores, or other processing means. The processing operations performed by processor 1004 may include the execution of an operating system or an operating platform on which applications and/or device functions are, in turn, executed. The processing operations may include operations related to I/O (input/output) either with a human user or with other devices, operations related to power management, operations related to connecting computing device 1000 to another device, and/or the like. The processing operations may also include operations related to audio I/O and/or display I/O.

[0098] In some embodiments, processor 1004 may comprise multiple processing cores 1008a, 1008b, and 1008c (also referred to as cores). Although three cores 1008a,

1008b, and 1008c are depicted in Fig. 10, processor 1004 may include any appropriate number of cores, e.g., tens of cores or even hundreds of cores. Cores 1008a, 1008b, and/or 1008c may be implemented on a single integrated circuit (IC) chip. Moreover, the chip may include one or more shared and/or private caches, buses or interconnections, graphics and/or memory controllers, and/or other components.

[0099] In some embodiments, processor 1004 may comprise a cache 1006. In some embodiments, sections of cache 1006 may be dedicated to individual cores (e.g., a first section of cache 1006 may be dedicated to core 1008a, a second section of cache 1006 may be dedicated to core 1008b, and so on). For some embodiments, one or more sections of cache 1006 may be shared among two or more of the cores. Cache 1006 may be split into different levels, e.g., a level 1 (LI) cache, a level 2 (L2) cache, a level 3 (L3) cache, and so on.

[00100] In some embodiments, cores 1008a, 1008b, and/or 1008c may include a fetch unit to fetch instructions (including instructions with conditional branches) for execution by the core. The instructions may be fetched from a memory 1030 (which may comprise any of a variety of storage devices). Cores 1008a, 1008b, and/or 1008c may also include a decode unit to decode the fetched instruction. For some embodiments, the decode unit may decode fetched instruction into a plurality of micro-operations. Cores 1008a, 1008b, and/or 1008c may also include a schedule unit to perform various operations associated with storing decoded instructions. In some embodiments, the schedule unit may hold data from the decode unit until the instructions are ready for dispatch, e.g., until all source values of a decoded instruction become available. For some embodiments, the schedule unit may schedule and/or issue (or dispatch) decoded instructions to an execution unit for execution.

[00101] The execution unit may execute dispatched instructions after they are decoded (e.g., by the decode unit) and dispatched (e.g., by the schedule unit). In some embodiments, the execution unit may include more than one type of execution unit (such as an imaging computational unit, a graphics computational unit, a general-purpose computational unit, and so on). The execution unit may also perform various arithmetic operations such as addition, subtraction, multiplication, and/or division, and may include one or more arithmetic logic units (ALUs). For some embodiments, a co-processor (not shown) may perform various arithmetic operations in conjunction with the execution unit.

[00102] Furthermore, the execution unit may execute instructions out-of-order.

Accordingly, in some embodiments, cores 1008a, 1008b, and/or 1008c may comprise an out- of-order processor core. Cores 1008a, 1008b, and/or 1008c may also include a retirement unit. The retirement unit may retire executed instructions after they are committed. For some embodiments, retirement of the executed instructions may result in processor state being committed from the execution of the instructions, physical registers used by the instructions being de-allocated, and so on. Cores 1008a, 1008b, and/or 1008c may also include a bus unit to enable communication between components of the core and other components via one or more buses. Cores 1008a, 1008b, and/or 1008c may additionally include one or more registers to store data accessed by various components of the core (such as values related to assigned app priorities and/or sub-system states (modes) association.

[00103] In some embodiments, device 1000 may comprise one or more connectivity circuitries 1031, which may include hardware devices (e.g., wireless and/or wired connectors and communication hardware) and/or software components (e.g., drivers, protocol stacks, and so on) to enable device 1000 to communicate with external devices. Device 1000 may be separate from the external devices, such as other computing devices, wireless access points or base stations, and so on.

[00104] In some embodiments, connectivity circuitries 1031 may include circuitries directed toward multiple different types of connectivity (e.g., connectivity protocols). To generalize, connectivity circuitries 1031 may include cellular connectivity circuitries, wireless connectivity circuitries, and so on. Cellular connectivity circuitries of connectivity circuitries 1031 may refer generally to cellular network connectivity provided by wireless carriers, such as via GSM (global system for mobile communications) or variations or derivatives thereof, via CDMA (code division multiple access) or variations or derivatives thereof, via TDM (time division multiplexing) or variations or derivatives thereof, via 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications Systems (UMTS) system or variations or derivatives thereof, via 3GPP Long-Term Evolution (LTE) system or variations or derivatives thereof, via 3 GPP LTE- Advanced (LTE- A) system or variations or derivatives thereof, via Fifth Generation (5G) wireless system or variations or derivatives thereof, via 5G mobile networks system or variations or derivatives thereof, via 5G New Radio (NR) system or variations or derivatives thereof, or via other cellular service standards.

[00105] Wireless connectivity circuitries (or wireless interfaces) of connectivity circuitries 1031 may refer generally to wireless connectivity that is not cellular, and may include personal area networks (such as Bluetooth, Near Field, and so on), local area networks (such as Wi-Fi), wide area networks (such as WiMax), and/or other wireless communication. For some embodiments, connectivity circuitries 1031 may include a network interface, such as a wired or wireless interface, so that a system embodiment may be incorporated into a wireless device (for example, into a cell phone or a personal digital assistant).

[00106] In some embodiments, device 1000 may comprise a control hub 1032, which may represent hardware devices and/or software components related to interaction with one or more I/O devices. Control hub 1032 may be a chipset, a Platform Control Hub (PCH), and/or the like. Via control hub 1032, processor 1004 may communicate with a display 1022 (or one or more displays), one or more peripheral devices 1024, one or more storage devices 1028, one or more other external devices 1029, and so on.

[00107] Control hub 1032 may provide one or more connection points for additional devices that connect to device 1000, through which a user might interact with the system. In some embodiments, devices that can be attached to device 1000 (e.g., external devices 1029) may include microphone devices, speaker or stereo systems, audio devices, video systems or other display devices, keyboard or keypad devices, and/or other I/O devices for use with specific applications such as card readers or other devices.

[00108] As mentioned above, control hub 1032 can interact with audio devices, display 1022, and so on. In some embodiments, input through a microphone or other audio device may provide input or commands for one or more applications or functions of device 1000. Additionally, audio output may be provided instead of, or in addition to display output. For some embodiments, if display 1022 includes a touch screen, display 1022 may also act as an input device, which may be at least partially managed by control hub 1032. There may also be additional buttons or switches on computing device 1000 to provide I/O functions managed by control hub 1032. In some embodiments, control hub 1032 may manage devices such as accelerometers, cameras, light sensors or other environmental sensors, or other hardware that can be included in device 1000. The input may be part of direct user interaction, and may also provide environmental input to the system to influence its operations (such as filtering for noise, adjusting displays for brightness detection, applying a flash for a camera, or other features).

[00109] In some embodiments, control hub 1032 may couple to various devices using any appropriate communication protocol, e.g., PCIe (Peripheral Component Interconnect Express), USB (Universal Serial Bus), USB Type-C, Thunderbolt, High Definition

Multimedia Interface (HDMI), Firewire, and so on.

[00110] In some embodiments, display 1022 may represent hardware components

(e.g., display devices) and software components (e.g., drivers) that provide a visual and/or tactile display for a user to interact with device 1000. Display 1022 may include a display interface, a display screen, and/or hardware device used to provide a display to a user. In some embodiments, display 1022 may include a touch screen (or touch pad) device that provides both output and input to a user. In some embodiments, display 1022 may communicate directly with processor 1004. Display 1022 may be an internal display device (e.g., as in a mobile electronic device or a laptop device) or an external display device attached via a display interface (e.g., DisplayPort, and so on). For some embodiments, display 1022 may be a head mounted display (HMD) such as a stereoscopic display device for use in virtual reality (VR) applications or augmented reality (AR) applications.

[00111] In some embodiments, in addition to (or instead of) processor 1004, device

1000 may include a Graphics Processing Unit (GPU) (not depicted in the figure). The GPU may comprise one or more graphics processing cores, which may control one or more aspects of displaying contents on display 1022.

[00112] For some embodiments, control hub 1032 may include hardware interfaces and connectors, as well as software components (e.g., drivers, protocol stacks, and so on) to make peripheral connections, e.g., to peripheral devices 1024. In various embodiments, control hub 1032 may comprise mechanisms to facilitate power saving in Type-C connectors, as disclosed herein.

[00113] It will be understood that device 1000 could both be a peripheral device to other computing devices, as well as have peripheral devices connected to it. Device 1000 may have a“docking” connector to connect to other computing devices for purposes such as managing content (e.g., downloading and/or uploading, changing, and/or synchronizing content) on device 1000. Additionally, a docking connector may allow device 1000 to connect to certain peripherals that allow computing device 1000 to control content output (e.g., to audiovisual systems and/or other systems).

[00114] In addition to a proprietary docking connector or other proprietary connection hardware, device 1000 may make peripheral connections via common or standards-based connectors. Such connectors may include a Universal Serial Bus (USB) connector (which may include any of a number of different hardware interfaces), a USB Type-C connector, a DisplayPort connector or MiniDisplayPort (MDP) connector, a High Definition Multimedia Interface (HDMI) connector, a Firewire connector, or other types of connectors. Accordingly, peripheral devices 1024 may comprise Type-C connectors, as disclosed herein.

[00115] In some embodiments, connectivity circuitries 1031 may be coupled to control hub 1032, e.g., in addition to, or instead of, being coupled directly to processor 1004. In some embodiments, display 1022 may be coupled to control hub 1032, e.g., in addition to, or instead of, being coupled directly to processor 1004.

[00116] In some embodiments, device 1000 may comprise memory 1030, which may be coupled to processor 1004 via a memory interface 1034. Memory 1030 may include memory devices for storing information in device 1000. Memory devices may include nonvolatile memory devices (for which state might not change if power to the memory device is interrupted) and/or volatile memory devices (for which state may be indeterminate, or lost, if power to the memory device is interrupted). Memory 1030 may comprise a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, a flash memory device, a phase-change memory device, or another memory device (e.g., a memory device having performance suitable for serving as process memory). In some embodiments, memory 1030 may operate as system memory for device 1000, to store data and instructions for use when the one or more processors (e.g., processor 1004) executes an application or process. Memory 1030 may store application data, user data, music, photos, documents, or other data, as well as system data (whether long-term or temporary) related to the execution of the applications and functions of device 1000.

[00117] Elements of various embodiments and examples may also be provided as a machine -readable medium (e.g., memory 1030) for storing the computer-executable instructions (e.g., instructions to implement any other processes discussed herein). The machine -readable medium (e.g., memory 1030) may include, but is not limited to, flash memory, optical disks, CD-ROMs, DVD ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, phase change memory (PCM), or other types of machine-readable media suitable for storing electronic or computer-executable instructions. Some embodiments of the disclosure may be downloaded as a computer program (e.g., BIOS) which may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of data signals via a communication link (e.g., a modem or network connection).

[00118] In some embodiments, one or more measurement circuitries and/or sensors of device 1000 may comprise temperature measurement circuitries 1040, e.g., for measuring temperature of various components of device 1000. In some embodiments, temperature measurement circuitries 1040 may be embedded, or coupled or attached to various components, whose temperature are to be measured and monitored. For some embodiments, temperature measurement circuitries 1040 may measure temperatures of (or within) one or more of cores 1008a, 1008b, 1008c, a voltage regulator 1014, memory 1030, a mother-board of SoC 1001, and/or any other appropriate component of device 1000.

[00119] In some embodiments, the measurement circuitries and/or sensors of device

1000 may comprise one or more power measurement circuitries 1042, e.g., for measuring power consumed by one or more components of the device 1000. For some embodiments, power measurement circuitries 1042 may measure power, voltage, and/or current. In some embodiments, power measurement circuitries 1042 may be embedded, coupled, or attached to various components whose power, voltage, and/or current consumption are to be measured and monitored. For some embodiments, power measurement circuitries 1042 may measure: power, voltage, and/or current supplied by voltage regulator 1014 (which may comprise one or more voltage regulator); power supplied to SoC 1001; power supplied to device 1000; power consumed by processor 1004 (or any other component) of device 1000; and so on.

[00120] In some embodiments, device 1000 may comprise one or more voltage regulator circuitries in voltage regulator 1014. Voltage regulator 1014 may generate signals at appropriate voltage levels, which may be supplied to operate any appropriate components of the device 1000. As an example, voltage regulator 1014 is depicted as supplying one or more signals (e.g., voltage signals) to processor 1004 of device 1000. In some embodiments, voltage regulator 1014 may receive one or more Voltage Identification (VID) signals, and generates the voltage signals (e.g., to processor 1004) at appropriate levels, based on the VID signals. Various type of VRs may be utilized for voltage regulator 1014. In some embodiments, voltage regulator 1014 may include a“buck” voltage regulator, a“boost” voltage regulator, a combination of buck and boost voltage regulators, low dropout (LDO) regulators, switching DC-DC regulators, and so on. Buck voltage regulators may be used in power delivery applications in which an input voltage is transformed to an output voltage in a ratio that is smaller than unity. Boost voltage regulators may be used in power delivery applications in which an input voltage is transformed to an output voltage in a ratio that is larger than unity. In some embodiments, each processor core may have its own voltage regulator, which may be controlled by a Power Control Unit (PCU) 1010a, a PCU 1010b, and/or a Power Management Integrated Circuit (PMIC) 1012. In some embodiments, each core may have a network of distributed LDOs to provide efficient control for power management. The LDOs may be digital, analog, or a combination of digital or analog LDOs.

[00121] In some embodiments, device 1000 may comprise one or more clock generator circuitries in a clock generator 1016. Clock generator 1016 generates clock signals at appropriate frequency levels, which may be supplied to any appropriate components of device 1000. As an example, clock generator 1016 is depicted as supplying clock signals to processor 1004 of device 1000. In some embodiments, clock generator 1016 may receive one or more Frequency Identification (FID) signals, and may generate the clock signals at an appropriate frequency, based on the FID signals.

[00122] In some embodiments, device 1000 may comprise a battery 1018 supplying power to various components of device 1000. As an example, battery 1018 is depicted as supplying power to processor 1004. Although not depicted in the figures, device 1000 may comprise a charging circuitry, e.g., to recharge the battery based on an Alternating Current (AC) power supply received from an AC adapter.

[00123] In some embodiments, device 1000 may comprise PCU 1010a and/or PCU

1010b (which may also be referred to as Power Management Units (PMUs), Power

Controllers, and so on). In some embodiments, PCU 1010a may be implemented by one or more of cores 1008a, 1008b, and/or 1008c, as is symbolically depicted using a dotted box labelled PCU 1010a. For some embodiments, PCU 1010b may be implemented outside the cores, as is symbolically depicted using a dotted box labelled PCU 1010b. PCU 1010a and/or PCU 1010b may implement various power management operations for device 1000. PCU 1010a and/or PCU 1010b may include hardware interfaces, hardware circuitries, connectors, registers, and so on, as well as software components (e.g., drivers, protocol stacks), to implement various power management operations for device 1000.

[00124] In some embodiments, device 1000 may comprise PMIC 1012, e.g., to implement various power management operations for device 1000. In some embodiments, PMIC 1012 may be a Reconfigurable Power Management ICs (RPMICs) and/or an IMVP (Intel® Mobile Voltage Positioning). In some embodiments, the PMIC may be within an IC chip separate from processor 1004. The may implement various power management operations for device 1000. PMIC 1012 may include hardware interfaces, hardware circuitries, connectors, registers, and so on, as well as software components (e.g., drivers, protocol stacks), to implement various power management operations for device 1000. In various embodiments, PMIC 1012 may comprise mechanisms to facilitate power saving in Type-C connectors, as disclosed herein.

[00125] For some embodiments, device 1000 may comprise PCU 1010a, PCU 1010b, and/or PMIC 1012. In some embodiments, any one of PCU 1010a, PCU 1010b, and/or PMIC 1012 may be absent in device 1000, and hence, these components are depicted using dotted lines.

[00126] Various power management operations of device 1000 may be performed by

PCU 1010a, PCU 1010b, PMIC 1012, or by a combination thereof. For some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may select a power state (e.g., a P-state) for various components of device 1000. In some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may select a power state for various components of device 1000 (e.g., in accordance with the ACPI (Advanced Configuration and Power Interface) specification). In some embodiments, for example, PCU 1010a, PCU 1010b, and/or PMIC 1012 may cause various components of the device 1000 to transition to a sleep state, to an active state, to an appropriate C state (e.g., CO state, or another appropriate C state, in accordance with the ACPI specification), and so on.

[00127] For some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may control a voltage output by voltage regulator 1014 and/or a frequency of a clock signal output by the clock generator, e.g., by outputting the VID signals and/or the FID signals, respectively. In some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may control battery power usage, charging of battery 1018, and features related to power saving operation.

[00128] Clock generator 1016 may comprise a phase locked loop (PLL), frequency locked loop (FLL), or any suitable clock source. In some embodiments, each core of processor 1004 may have its own clock source. As such, each core may operate at a frequency independent of the frequency of operation of the other core. In some

embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may perform adaptive or dynamic frequency scaling or adjustment. For some embodiments, clock frequency of a processor core may be increased if the core is not operating at its maximum power consumption threshold or limit. In some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may determine the operating condition of each core of a processor, and may opportunistically adjust frequency and/or power supply voltage of that core without the core clocking source (e.g., a PLL of that core) losing lock when PCU 1010a, PCU 1010b, and/or PMIC 1012 determines that the core is operating below a target performance level. In some

embodiments, if a core is drawing current from a power supply rail less than a total current that is allocated for that core (or for processor 1004), then PCU 1010a, PCU 1010b, and/or PMIC 1012 may temporality increase the power draw for that core (or for processor 1004), for example, by increasing a clock frequency and/or a power supply voltage level, so that the core or processor 1004 can perform at a higher performance level. As such, in various embodiments, voltage and/or frequency may be increased temporality for processor 1004 without violating product reliability.

[00129] For some embodiments, PCU 1010a, PCU 1010b, and/or PMIC 1012 may perform power management operations, e.g., based at least in part on receiving measurements from power measurement circuitries 1042, temperature measurement circuitries 1040, charge level of battery 1018, and/or any other appropriate information that may be used for power management. To that end, PMIC 1012 may be communicatively coupled to one or more sensors to sense and/or detect various values of and/or variations in one or more factors having an effect on power and/or thermal behavior of the system or platform. Examples of the one or more factors may include electrical current, voltage droop, temperature, operating frequency, operating voltage, power consumption, inter-core communication activity, and so on. Sensors for one or more of these factors may be provided in physical proximity to (and/or in thermal contact with or thermally coupled to) one or more components or logic/IP blocks of a computing system (e.g., a computing system of device 1000). Additionally, in some embodiments, sensor(s) may be directly coupled to PCU 1010a, PCU 1010b, and/or PMIC 1012 to allow PCU 1010a, PCU 1010b, and/or PMIC 1012 to manage processor core energy at least in part based on value(s) detected by one or more of the sensors.

[00130] Also depicted is an example software stack of device 1000 (although not all elements of the software stack are depicted). In various embodiments, processor 1004 may execute application programs 1050, Operating System (OS) 1052, one or more Power Management (PM) specific application programs (e.g., generically referred to as PM applications 1058), and/or the like. PM applications 1058 may also be executed by PCU 1010a, PCU 1010b, and/or PMIC 1012. OS 1052 may also include one or more PM applications 1056a, 1056b, 1056c, and so on. OS 1052 may also include various drivers 1054a, 1054b, 1054c, and so on, some of which may be specific for power management purposes. In some embodiments, device 1000 may further comprise a Basic Input/Output System (BIOS) 1020. BIOS 1020 may communicate with OS 1052 (e.g., via one or more of drivers 1054a, 1054b, 1054c, and so on), communicate with processor 1004, and so on.

[00131] In various embodiments, one or more of PM applications 1058, drivers that

OS 1052 includes (e.g., drivers 1054a, 1054b, 1054c, and so on), PM applications that OS 1052 includes (e.g., PM applications 1056a, 1056b, 1056c, and so on), BIOS 1020, and so on may be used to implement power management specific tasks. For example, these components may be used to control voltage and/or frequency of various components of device 1000, to control wake-up state, sleep state, and/or any other appropriate power state of various components of device 1000, to control battery power usage, to control a charging of the battery 1018, to control features related to power saving operation, and so on.

[00132] Reference in the specification to "an embodiment," "one embodiment,"

"some embodiments," or "other embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments. The various appearances of "an embodiment," "one embodiment," or "some embodiments" are not necessarily all referring to the same embodiments. If the specification states a component, feature, structure, or characteristic "may," "might," or "could" be included, that particular component, feature, structure, or characteristic is not required to be included. If the specification or claim refers to "a" or "an" element, that does not mean there is only one of the elements. If the specification or claims refer to "an additional" element, that does not preclude there being more than one of the additional element.

[00133] Furthermore, the particular features, structures, functions, or characteristics may be combined in any suitable manner in one or more embodiments. For example, a first embodiment may be combined with a second embodiment anywhere the particular features, structures, functions, or characteristics associated with the two embodiments are not mutually exclusive.

[00134] While the disclosure has been described in conjunction with specific embodiments thereof, many alternatives, modifications and variations of such embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures e.g., Dynamic RAM (DRAM) may use the

embodiments discussed. The embodiments of the disclosure are intended to embrace all such alternatives, modifications, and variations as to fall within the broad scope of the appended claims.

[00135] In addition, well known power/ground connections to integrated circuit (IC) chips and other components may or may not be shown within the presented figures, for simplicity of illustration and discussion, and so as not to obscure the disclosure. Further, arrangements may be shown in block diagram form in order to avoid obscuring the disclosure, and also in view of the fact that specifics with respect to implementation of such block diagram arrangements are highly dependent upon the platform within which the present disclosure is to be implemented (i.e., such specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that the disclosure can be practiced without, or with variation of, these specific details. The description is thus to be regarded as illustrative instead of limiting.

[00138] An abstract is provided that will allow the reader to ascertain the nature and gist of the technical disclosure. The abstract is submitted with the understanding that it will not be used to limit the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.