POWER GATED COMMUNICATION CONTROLLER

Abstract

A method includes detecting a communication event over a communication bus 130 coupled to a device, and in response to detecting the communication event, deactivating a module of the device. The method may further include sending a data throttle packet over the communication bus 130 while the deactivated module reactivates.

Description

BACKGROUND

With more electronic devices relying on battery power, power consumption is becoming a more important criterion in the design of electronic devices and peripheral devices that connect to electronic devices. One area that consumes power in electronic devices is communication controllers, such as a Universal Serial Bus (USB), serial, or parallel communication controller. These controllers may require peripheral devices to respond repeatedly to polling from a host device. In some instances, an entire device controller on a peripheral device may be powered simply to respond to polling from a host device.

A conventional technique to reduce power consumption in devices, such as peripheral device controllers, is clock gating. In this technique, the clock to the individual elements in a peripheral device controller is stopped. This reduces the dynamic power, which is the power dissipated by circuits when the circuits are switching and active. However, with device controllers being designed with smaller technologies, such as 90 nm technologies and smaller, leakage power, the power dissipated by circuits when the circuits are inactive or not switching, may result in more power dissipation than dynamic power dissipation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an example system according to sonic embodiments.

FIG. 1B is a block diagram illustrating further details of the example system of FIG. 1A according to some embodiments.

FIG. 2 is a flow chart of an example method according to some embodiments.

FIG. 3 is a flow chart of another example method according to some embodiments.

FIG. 4 is a flow chart of yet another example method according to some embodiments.

FIG. 5 is a block diagram of an example system that incorporates the example system of FIG. 1B according to some embodiments.

DETAILED DESCRIPTION

FIG. 1A is a block diagram of an example system 100 according to some embodiments. The system 100 may be associated with a peripheral device that may be adapted to communicate with a host device 160 over a communication bus 130 using, for example, a serial, parallel, or Universal Serial Bus (USB) interface, such as an interface defined by the USB 2.0 standard (April 2000). For example, the system 100 may include a communication control unit 102 to support communication between the host device 160 and the system 100 over the communication bus 130. For example, in some embodiments, the communication control unit 102 may support communications between a peripheral device, such as but not limited to, a mouse, keyboard, memory device, or printer and a host device, such as but not limited to, a desktop, laptop, tablet, smart phone or other computing unit. Furthermore, in some embodiments, the communication control unit 102 may support communications between two computing units, such as, tablets, smart phones, or laptops, where one of the computing units acts as a peripheral device and one of the computing units acts as a host device.

Note that the communication control unit 102 may be associated with a peripheral device that communicates through the communication control unit 102 with the host device 160. In some embodiments, the host device 160 may control the communication bus 130. In these and other embodiments, the communication control unit 102 may be unable to send packets over the communication bus 130 or generate an interrupt independent of the host device 160. For the communication control unit 102 to send packets to the host device 160 or generate an interrupt, the communication control unit 102 must wait to receive an inquiry from the host device 160 asking if the communication control unit 102 is ready to receive packets or has packets to send to the host device 160. This may be referred to as the host device 160 polling the communication control unit 102.

In some embodiments, to reduce latency and maintain adequate data transfer, the host device 160 may poll the communication control unit 102 at set intervals or at undefined intervals. In particular, in applications where the communication control unit 102 is associated with a peripheral device that generates large amounts of data in a short time frame, the host device 160 may poll the communication control unit 102 more frequently to ensure adequate data transfer between the host device 160 and the peripheral device. The communication control unit 102 may be required to respond to the polling of the host device 160, even if the communication control unit 102 has not received data from its associated peripheral device to send to the host device 160 or cannot receive data from the host device 160.

In some embodiments, the communication control unit 102 may detect the occurrence of certain communication events between the host device 160 and the communication control unit 102 and deactivate a portion of the communication control unit 102 to reduce the power consumption of the system 100. In some embodiments, while portions of the communication control unit 102 are deactivated, the communication control unit 102 may continue to respond to polling by the host device 160. Furthermore, the communication control unit 102 may, upon detecting or determining a reactivation event, reactivate the deactivated portions of the communication control unit 102. While the deactivated portions of the communication control unit 102 are reactivating, the communication control unit 102 may continue to respond to polling by the host device 160 by sending data throttle packets. By deactivating portions of the communication control unit 102, the power consumed by the communication control unit 102 may be reduced.

FIG. 1B is a block diagram illustrating further details of the example system 100 of FIG. 1A according to some embodiments. The system 100 may include the communication control unit 102 and a power supply unit 150 that provides power to and receives commands from the communication control unit 102. The communication control unit 102 includes a communication module 110, a power control module 120, and may include various other modules, such as first and second modules 140, 142. The first and second modules 140, 142 are illustrated only to depict other modules within the communication control unit 102. In some embodiments, the communication control unit 102 may have more or less than two modules. In some embodiments, the first and second modules 140, 142 may be the same or different and may be a buffer memory, control status registers, interface module for communication with a peripheral device, data transfer communication protocol modules, or some other module in the communication control unit 102.

In some embodiments, the communication module 110 and the power control module 120 may be implemented in hardware, programmable devices, or sonic combination of both. In some embodiments, the communication module 110 and the power control module 120 may not be separate modules and the functionality of both modules may be implemented in the same module.

The communication module 110 is coupled to the communications bus 130 and may be configured to handle communication protocols for communicating with the host device 160. In particular, the communication module 110 may be configured to receive packets from and send packets to the host device 160 and respond appropriately to inquiry packets from the host device 160 in accordance with a predetermined protocol. Packets may include any packets sent over the communication bus 130. For example, packets may include polling and/or inquiry packets, such as token packets, packets for initializing the communication control unit 102, handshaking packets, data packets, and other packets sent between the communication control unit 102 and the host device 160.

The example communication module 110 also includes first and second endpoints 112, 114. Each of the first and second endpoints 112, 114 may be recognized by the host device 160 as a separate terminal communicating with the host device 160. For example, a peripheral device connected to the communication control unit 102 may contain two devices that communicate with the host device 160. Each of the devices may be assigned one of the first or second endpoints 112, 114 for communicating with the host device 160. By providing both the first and second endpoints 112, 114, the communication control unit 102 may handle communications between both devices and the host device 160. In some embodiments, the communication module 110 may contain more or less than two endpoints.

The power control module 120 is coupled to the communication module 110 and the power supply unit 150. The power control module 120 may be configured to detect a communication event occurring over the communication bus 130. The power control module 120 may detect a communication event over the communication bus 130 by intercepting the communications over the control bus 130 or by interfacing with the communication module 110.

Note that the communication event is not a command, suggestion, or any indication from the host device 160, or a peripheral device, that the communication control unit 102 should reduce power consumption, operate in a power saving mode, power down, sleep, hibernate, or anything of the like. For example, if the communication control unit 102 was part of a USB device controller, the communication event may not be a command from the host controller for the USB device controller to operate in a low power or suspend mode. Nor would the communication event be a command from the peripheral device connected to the USB device controller to enter a low power or suspend mode.

The communication event may instead relate to a sequence, pattern, timing, or otherwise, of packets sent or received by the communication control unit 102 during normal operation. For example, in some embodiments, a communication event may occur when the communication control unit 102 sends a certain number of packets indicating that the communication control unit 102 has no data to send to the host device 160 within a certain period. Or a communication event may occur when the communication control unit 102 sends a consecutive number of the same or similar types of packets. In these and other embodiments, the communication control unit 102 may be responding to the same inquiry packet received from the host device 160. In some embodiments, a communication event may occur when the interval between the same or similar types of packets received by the communication control unit 102 is greater than a predefine interval. Other sequences, patterns, timings and the like may also be used to indicate a communication event.

In response to detecting a communication event, the power control module 120 may deactivate the first module 140, the second module 142, or both of the first and second modules 140, 142. In some embodiments, the power control module 120 may deactivate the first and second modules 140, 142 by directing the power supply unit 150 to shut off the power to the first and second modules 140, 142 by shutting off the voltage and/or current to power supply lines 154 and 152 respectively, while maintaining voltage and/or current on a power supply line 156. In some embodiments, where the communication control unit 102 contains more or less modules than just the first and second modules 140, 142, the power control module 120 may deactivate one or more of the modules within the communication control unit 102. In some embodiments, the power control module 120 may deactivate all of the modules in the communication control unit 102 that are not required to respond to one or more specific inquiries from the host device 160. For example, in some embodiments, if the communication control unit 102 was part of a USB device controller, the power control module 120 may deactivate all modules that are not required to receive a polling token from the host device 160 and respond with a packet indicating that the communication control unit 102 has no data to send to the host device 160, such as a NAK packet.

In some embodiments, the power control module 120 may also be configured to detect a reactivation event and reactivate one or both of the first and second modules 140, 142 that have been deactivated. In some embodiments, a reactivation event may include the communication control unit 102 receiving a certain type of packet from the host device 160 or data from a peripheral device.

In some embodiments, a reactivation event may depend on the previously detected communication event. For example, in some embodiments, if the detected communication event occurred because the communication control unit 102 indicated that it had no data to send to the host device 160, the reactivation event may be the communication control unit 102 receiving data from a peripheral device or the communication control unit 102 receiving a different inquiry from the host device 160, such as if the communication control unit 102 is available to receive data from the host device 160.

As another example, in some embodiments, if the detected communication event occurred because the intervals between packets from the host device 160 were greater than a predefined interval, the reactivation event may be the communication control unit 102 receiving data from a peripheral device, or a packet from the host device 160, during the interval between packets or an end of a deactivation period.

In some embodiments, if the reactivation event involved the communication control unit 102 receiving a packet from the host device 160 indicating that the host device 160 had data to send to the communication control unit 102, the power control module 120 may direct the communication module 110 to send a data throttle packet in response to the host device 160. The data throttle packet may indicate to the host device 160 that the communication control unit 102 is not ready to receive data from the host device 160. Thus, the data throttle packet may “throttle” or slow down a data transfer because the data throttle packet may cause the host device 160 to wait to send the data to the communication control unit 102. By causing the host device 160 to wait to send data, the communication control unit 102 may help to ensure that the deactivated first and second modules 140, 142 have reactivated and stabilized before a data transfer occurs.

In some embodiments, the power cont of module 120 may also monitor the communication bus 130 while one or both of the first and second modules 140, 142 reactivate. If the power control module 120 detects an inquiry packet from the host device 160, such as a polling packet, during the reactivation of the first and second modules 140, 142, the power control module 120 may direct the communication module 110 to send a data throttle packet to the host device 160 over the communication bus 130 to continue to allow the first and second modules 140, 142 to reactivate and stabilize before a data transfer occurs.

By throttling data transfers, the deactivation and reactivation of the first and second modules 140, 142 may be performed independently and without knowledge by the host device 160 or a peripheral device. If data transfers are not throttled while the first and second modules 140, 142 reactivate, the first and second modules 140, 142 may not be completely reactivated once a data transfers begins because the host device 160 and/or peripheral device may not be aware that the modules 140, 142 were deactivated and now reactivating. As a result, data and/or packets may be lost. Throttling data transfers may help the communication control unit 102 to maintain proper transfer protocols with the host device 160 and/or peripheral device without having to indicate to the host device 160 and/or peripheral device that the modules 140, 142 were deactivated or requiring support to deactivate and reactivate the modules 140, 142.

By deactivating one or both of the first and second modules 140, 142, the communication control unit 102 may reduce the amount of power consumed by the system 100. In some embodiments, where the communication control unit 102 is part of a USB device controller, depending on the application, the load, and the technology used to manufacture the USB device, deactivating one or more modules of the communication control unit 102 may reduce power consumption of the communication control unit 102 from between 15% to 90%, and on average may reduce the power consumption by approximately 40%.

FIG. 2 is a flow chart of an example method 200 according to some embodiments. The method 200 may be performed, for example, by the system 100, or more particularly, by the communication control unit 102, described with respect to FIGS. 1A and 1B. The flow charts described herein do not necessarily imply a fixed order to the actions, and embodiments may be performed in any order that may be practicable. Note that any of the methods described herein may be performed by hardware, software (including microcode), or a combination of hardware and software. For example, a storage medium may store thereon instructions that when executed by a machine result performance according to any of the embodiments described herein.

At 210, a communication event may be detected. The communication event may be related to a sequence, pattern, timing, or otherwise, of packets sent or received over a communication bus during normal operation. The communication event is not a command, suggestion, or any indication from a host device or a peripheral device communicating over the communication bus, for a communication control unit that handles communications over the communication bus, to reduce power or operate in a power saving mode. The communication event may indicate that given the current state of the communication control unit that certain modules within the communication control unit are not in need and may be deactivated.

In some embodiments, the communication event may occur when a number of packets sent over the communication bus exceeds a predetermined threshold. In some embodiments, for the packets to be counted, the packets may need be the same types and/or consecutive. Furthermore, in some embodiments, each packet may be sent in reply to an inquiry packet received over the communication bus.

In some embodiments, the communication event may occur when an interval between the first and second packets received over the communication bus, is longer than a reactivation latency of modules that may be deactivated. In some embodiments, the first and second packets may be received at the same or distinct communication endpoints.

At 220, one or more modules of the communication control unit may be deactivated in response to the communication event. In some embodiments, deactivating the modules may include eliminating voltage and/or current to the modules. For example, the voltage and/or current may be shut-off to the modules by switching external power rails. By deactivating the modules, the power used by the communication control unit may be reduced.

At 230, the one or more deactivated modules may be reactivated. Based on the current state of the communication control unit, the deactivated modules may need to be utilized. In some embodiments, the deactivated modules may be reactivated by supplying voltage and/or current to the deactivated modules. In some embodiments, only the deactivated modules that need to be utilized may be reactivated.

At 240, throttle data packets may be sent over the communication bus while the deactivating modules are reactivating. In some embodiments, the deactivated modules may have reactivation latency. During the latency period, the throttle data packets may be sent to delay data transfers between the communication control unit and the host device so that the deactivated modules may be fully activated during subsequent data. transfer between the host device and the communication control unit.

In some embodiments, the method 200 may include additional actions. For example, the method 200 may also include detecting a reactivation event. The one or more deactivated modules may be reactivated when the reactivation event is detected. In sonic embodiments, the reactivation event may include the communication control unit receiving data to send over the communication bus or a change in an inquiry received over the communication bus. In some embodiments, the reactivation event may include the communication control unit receiving a third packet between the first and second packets or an end of a deactivation period.

In some embodiments, the method 200 may also include additional actions performed between detecting the deactivation event and deactivating one or more modules. For example, in some embodiments, after detecting the deactivation event, clock signals to the modules to be deactivated are stopped. Next, isolation cells may be activated on the outputs of the modules to be deactivated. The isolation cells may be used to control the data values that may be seen by the deactivated modules when they are reactivated. Once the isolation cells are activated, the voltage and/or current to the modules to be deactivated may be shut-off to deactivate the modules.

In these and other embodiments, after the reactivation event, the voltage and/or current may be supplied to the deactivated modules. The isolation cells may also be deactivated and the clock signals may then be supplied to the deactivated modules to reactivate the modules.

FIG. 3 is a flow Chart of an example method 300 according to some embodiments. The method 300 may be performed, for example, by the system 100, or more particularly, by the communication control unit 102, described with respect to FIGS. 1A and 1B. The method 300 may be used to deactivate modules in a communication control unit when a timing interval between received packets is shorter than a reactivation latency of the deactivated modules.

At 302, normal operations may be performed and all modules may be activated. At 310, incoming and outgoing packets may be detected. For example, a power control module within the communication control unit may detect the incoming and outgoing packets. In some embodiments, an incoming inquiry packet may first be detected and then an outgoing response packet may be detected to determine a certain condition within the communication control unit. For example, if the communication control unit was a USB device controller, a received IN token packet and a sent NAK handshake packet may be detected. This may indicate that the host device and USB device controllers have no data to send to each other.

At 316, a consecutive number of the same received and/or sent packets may be counted. If the number of consecutive packets counted exceeds a predetermined threshold, the method 300 may proceed to 326. Otherwise, the method 300 proceeds to 302 and performs normal operations. The threshold number of packets may vary based on operational performance requirements, power requirements, and other needs. For example, in some embodiments, the threshold number may be 3, 5, 10, 15, or some other number of packets.

At 326, a module in the communication control unit that may not be required to receive and send packets of the type that were counted at 316 may be deactivated.

At 330, monitoring for a reactivation event may occur. While monitoring for the reactivation event, packets, which do not cause a reactivation event, may continue to be received and packets may be sent in response. For example, packets of the type counted at 316 may not cause a reactivation event.

At 336, the deactivated modules may be reactivated once a reactivation event occurs. The reactivation event may indicate that the status of the communication control unit or host device has changed. For example, if the communication control unit was a USB device controller, a reactivation event may occur if either the USB device controller or host device has data to send to the other. If the reactivation event is the recite of a packet indicating the host device has data to transfer to the communication control unit, the power control module may direct a throttle data packet to be sent to the host device. For example, if the communication control unit was a USB device controller and the host device sent an OUT token packet, a USB device controller may send a NAK handshake packet to report that the device controller cannot receive data, thereby throttling the data exchange between the device controller and the host device.

At 340, it may be determined if the deactivated modules are reactivated and ready. If the modules are completely reactivated, the method 300 may proceed to 302. If the modules are not completely reactivated, the method 300 may proceed to 346.

At 346, it may be determined if a packet has been received while the modules are reactivating. If a packet has been received, the method 300 may proceed to 350, otherwise the method may proceed back to 340.

At 350, a data throttle packet may be sent to the host device to throttle outgoing or incoming data. The method 300 may then proceed back to 340, to wait for the deactivated modules to reactivate. Thus, the method 300 may continually check for packets and respond to any received packets while waiting for the deactivated modules to reactivate.

The method 300 may be used to deactivate modules when a timing interval between packets from a host device is shorter than a reactivation latency of modules that may be deactivated. For example, the method 300 may be implemented in a system with a high-speed USB device controller with a normal or high polling rate. Thus, the modules within the communication control unit may be deactivated during intervals when the host device polls the communication control unit but no data is being transferred, thereby reducing power consumption.

FIG. 4 is a flow chart of an example method 400 according to some embodiments. The method 400 may be performed, for example, by the system 100, or more particularly, by the communication control unit 102, described with respect to FIGS. 1A and 1B. The method 400 may be used to deactivate modules within a communication control unit during an interval between packets received by the communication control unit, when the interval between the packets is greater than a reactivation latency of the deactivated modules.

At 402, normal operations may be performed and all modules may be activated. At 406, a first packet may be received at a first endpoint. After the first packet is received, at 410, a counter may be started. At 416, a second packet may be received at either the first endpoint or another endpoint. After the second packet is received, at 420, it may be determined if the counter indicates that an interval between the first and second packets is greater than a reactivation latency of one or more modules within the communication control unit. If the material is not greater than the reactivation latency, the method 400 may proceed to 410. Otherwise, the method 400 may proceed to 426.

At 426, one or more modules may be deactivated. In particular, modules with reactivation latencies less than the interval between the first and second packets may be deactivated. Thus, in some embodiments, depending on the reactivation latencies of the modules, some modules may be deactivated while other modules are not. A deactivation interval equal to the interval between the packets, minus the reactivation latency of the deactivated modules, may also be determined. A deactivation interval counter may also be started to indicate the start of the deactivation interval.

At 430, it be determined if a reactivation event has occurred. For example, a reactivation may include receiving a packet during the deactivation interval. If no reactivation event has occurred, the method 400 may proceed to 436. Otherwise, the method 400 may proceed to 450.

At 436, it may be determined if the deactivation interval has lapsed. If the deactivation interval has lapsed, the method 400 proceeds to 440. Otherwise, the method 400 may proceed to 430. Thus, the deactivated modules may remain deactivated until a reactivation event occurs or the deactivation interval lapses.

At 440, the deactivate modules may be reactivated. At 446, a packet may be received and a packet may be sent in response. The method 400 may then proceed to 426. Thus, the deactivated modules may be cyclically activated and deactivated.

At 450, the deactivated modules may be activated. At 456, it may be determined if the deactivated modules are reactivated and ready. If the modules are completely reactivated, the method 400 may proceed to 402. If the modules are not completely reactivated, the method 400 may proceed to 460.

At 460, it may be determined if a packet has been received while the modules are reactivating. If a packet has been received, the method 400 may proceed to 466, otherwise the method 400 may proceed back to 456.

At 466, a data throttle packet may be sent to the host controller to throttle outgoing or incoming data. The method 400 may then proceed back to 456 to wait for the deactivated modules to reactivate. Thus, when a reactivation eve occurs, the method 400 may continually check for packets and responds to any received packets while waiting for the modules to reactivate.

The method 400 may thus be used to deactivate one or more modules within the communication control unit when the interval between packets from a host device is larger than the reactivation latency of the modules, thereby reducing power consumption.

FIG. 5 is a block diagram of an example system 500 that incorporates the example system 100 of FIG. 1B, according to some embodiments. The system 500 may include a circuit 510 coupled to the communication control unit 102. The circuit 510 may be any circuit that generates data to send to and receive data from the host device 160. The communication control unit 102 may operate as communication circuitry to allow data transfers between the circuit 510 and the host device 160. For example, in some embodiments, the circuit 510 may be the circuitry in a mouse, keyboard, memory device, or printer and the host device 160 may be a desktop, laptop, tablet, smart phone or other computing unit. According to some embodiments, the host device 160 may include a display port (e.g., to be attached to one or more monitors). Furthermore, in some embodiments, the circuit 510 and the host device 160 may both be computing units, such as, tablets, smart phones, or laptops, where the circuit 510 acts as a peripheral device and the host device 160, as a host. In some embodiments, the circuit 510 and host device 160 may be connected using the USB protocol. In these and other embodiments, the communication control unit 102 may act as a USB device controller.

Although particular system, hardware, and interface configurations have been described herein, embodiments may be performed with any other types of system, hardware, and/or interface configurations. Similarly, although specific methods have been described, any number of other types of methods might be performed in connection with embodiments described here.

The several embodiments described herein are solely for the purpose of illustration. Persons skilled in the art will recognize from this description that other embodiments may be practiced with modifications and alterations limited only by the claims.

Claims

1. A method, comprising:

detecting a communication event over a communication bus, the communication bus coupled to a device;

deactivating one or more modules of the device in response to the communication event;

reactivating the one or more deactivated modules; and

sending a data throttle packet over the communication bus in response to an inquiry received over the communication bus during at least a portion of reactivation of one or more deactivated modules.

2. The method of claim 1, wherein the modules are deactivated by eliminating voltage and/or current to the modules.

3. The method of claim 1, further comprising detecting a reactivation event, wherein the one or more deactivated modules are reactivated when the reactivation event is detected.

4. The method of claim 1, wherein the communication event occurs when a number of packets sent over the communication bus from the device exceeds a predetermined threshold.

5. The method of claim 4, wherein the packets are of a same type and consecutive.

6. The method of claim 4, wherein each packet is sent in reply to an inquiry received over the communication bus.

7. The method of claim 3, wherein the reactivation event comprises the device receiving data to send over the communication bus or a change in the inquiry received over the communication bus.

8.-11. (canceled)

12. An apparatus, comprising:

a communication module configured to send and receive packets over a communication bus; and

a power control module coupled to the communication module, the power control module configured to: detect a communication event over the communication bus; deactivate another module in response to the communication event; reactivate the deactivated module; and direct the communication module to send a data throttle packet over the communication bus, in response to an inquiry received over the communication bus, during at least a portion of reactivation of one or more deactivated module reactivates.

13. The apparatus of claim 12, wherein the power control module is to control a power supply to the communication module and another module, wherein to deactivate the other module, the power control module is to turn off a voltage and/or current to the other module.

14. The apparatus of claim 12, wherein the power control module is further configured to detect a reactivation event, wherein the deactivated module to be reactivated when the reactivation event is detected.

15. The apparatus of claim 12,

wherein the power control module is to detect a communication event when a number of packets sent by the communication module exceeds a predetermined threshold.

16. The apparatus of claim 15, wherein one or more packets are to be sent in reply to the communication module receiving an inquiry over the communication bus.

17. The apparatus of claim 16, wherein the reactivation event comprises receipt by the communication module of data to send over the communication bus or a change in the inquiry received by the communication module.

18.-21. (canceled)

22. A system comprising:

a display port;

a circuit; and

a communication control unit in communication with the circuit, wherein the communication control unit comprises: a communication module that sends and receives packets over a communication bus; a module coupled to the communication module; and a power control module coupled to the communication module, the power control module configured to: detect a communication event over the communication bus; deactivate the module in response to the communication event; reactivate the deactivated modules; and direct the communication module to send a data throttle packet over the communication bus, in response to an inquiry received over the communication bus, during at least a portion of reactivation of at one or more deactivated modules.

23. The system of claim 22, wherein the power control module is to detect a communication event when a number of packets sent by the communication module exceeds a predetermined threshold.

24. The method of claim 1, further comprising polling to determine if a communication control unit is ready to receive packets or has packets to send prior to detecting the communication event.

25. The method of claim 1, wherein the communication event relates to at least one of a sequence, a pattern and a timing of data packets sent or received.

26. The method of claim 1, further comprising slowing down a data transfer by sending the data throttle packet.

27. The method of claim 1, wherein deactivation and reactivation of the one or more modules is performed independently of a host device.

28. The apparatus claim 12, wherein the communication module is configured to send the data throttle packet to slow down a data transfer.

29. The apparatus of claim 12, wherein deactivation and reactivation of the one or more modules is performed independently of a host device.

30. The apparatus of claim 12, wherein the communication event relates to at least one of a sequence, a pattern and a timing of data packets sent or received.

31. The apparatus of claim 12, wherein the other module is deactivated during an interval when a host device polls the communication module, but data is being transferred.

32. The system of claim 22, wherein the communication module is configured to send the data throttle packet to slow down a data transfer.

33. The system of claim 22, wherein deactivation and reactivation of the one or more modules is performed independently of a host device.

34. The system of claim 22, wherein the communication event relates to at least one of a sequence, a pattern and a timing of data packets sent or received.

35. The system of claim 12, wherein the other module is deactivated during an interval when a host device polls the communication module, but data is being transferred.