Methodology for managing power consumption in an application

• US 7,080,267 B2
• Filed: 06/13/2003
• Issued: 07/18/2006
• Est. Priority Date: 08/01/2002
• Status: Active Grant

• Current Assignee: Texas Instruments, Inc.
• Original Assignee: Texas Instruments, Inc.
• Inventors: Sarathy, Vijaya B. P., Cyran, Robert J., Gary, Scott P.
• Primary Examiner(s): Lee, Thomas
• Assistant Examiner(s): SURYAWANSHI, SURESH
• Application Number:
  US10/461,025
• Publication Number:
  US 20040025067A1
• Time in Patent Office: 1,131 Days
• Field of Search: 713/300, 713/320, 709/224, 709/203, 719/318
• US Class Current: 713/300
• CPC Class Codes: G06F 8/4432 Reducing the energy consumption
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Methods and systems are provided for dynamically managing power consumption in a digital system. These methods and systems broadly provide for permitting clients executing on a digital system to register for notification of power event and to request that power events occur. Registered clients are notified when a power event is requested and the requested power event is caused to occur. Power events are selected from a group comprising setpoint change, enter deep sleep mode, enter snooze mode, and change to power supply status. There may also be user-defined custom power events. If the requested power event is a setpoint change, a check is made to verify that each of the registered clients can operate at the requested setpoint. The digital system may be comprised of processor with a single processing core with a single clock or a processor with multiple processing cores and multiple clocks.

Claims

1. A method for managing power consumption in a digital system comprising the steps of:

registering a plurality of clients for notification of power events;

receiving a request for a power event from a first client;

notifying each of the registered clients of the power event before the power event occurs if the registered client requested to be notified before the occurrence of the power event; and

causing the power event to occur;

notifying each of the registered clients after the power event occurs that the power event has occurred if the registered client requested to be notified after the occurrence of the power event.

2. The method of claim 1 further comprising the step of unregistering a client of the plurality of clients when the client no longer wants notification of power events.

3. The method of claim 1 wherein:

the step of receiving a request for a power event from a first client includes further receiving a notification timeout period;

receiving a response from at least a second client that the second client is not ready for the power event to occur;

causing the power event to occur after the second client indicates that the second client is ready for the power event to occur; and

wherein if the second client does not indicate that the second client is ready for the power event to occur within the notification timeout period, the notifying the first client is that the timeout period has elapsed.

4. The method of claim 1 wherein:

said step of registering a plurality of clients for notification of power events includes registering an indication of voltage/frequency setpoints supported by the client;

storing configuration data indicative of valid set points for each registered client;

the requested power event comprises a setpoint change; and

the method further comprises the step of verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

the steps of notifying the registered clients and causing the power event to occur are executed only if all registered clients are verified to operate at the requested setpoint.

5. The method of claim 1 wherein

the step of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification;

and

the step of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

6. A digital system in which power consumption is dynamically managed during the operation of the digital system comprising:

a processor;

one or more peripheral devices coupled to the processor;

an operating system executable by the processor;

an application executable on the operating system; and

a power management module incorporated in the digital system wherein the power management module is an adjunct to the operating system and provides power management functionality for the digital system, said power management functionality including

registering a plurality of clients for notification of power events;

receiving a request for a power event from a first client;

notifying each of the registered clients of the power event before the power event occurs if the registered client requested to be notified before the occurrence of the power event; and

causing the power event to occur;

notifying each of the registered clients after the power event occurs that the power event has occurred if the registered client requested to be notified after the occurrence of the power event.

7. The digital system of claim 6 wherein the power management module provides one or more methods for power management selected from the group consisting of:

causing a power-saving function to be called when the digital system is booted, invoking application specific sleep modes, registering of clients for notification of one or more power events and notifying the registered clients of power events for which the registered clients requested notification; and

idling one or more specified clock domains.

17. The digital system of claim 6 wherein said power management functionality further including:

unregistering a client of the plurality of clients when the client no longer wants notification of power events.

18. The digital system of claim 6 wherein:

said power management functionality wherein the functionality of receiving a request for a power event from a first client includes receiving a notification timeout period;

said power management functionality further including receiving a response from at least a second client that the second client is not ready for the power event to occur;

said power management functionality further including causing the power event to occur after the second client indicates that the second client is ready for the power event to occur; and

said power management functionality further including if the second client does not indicate that the second client is ready for the power event to occur within the notification timeout period, the notifying the first client that the timeout period has elapsed.

19. The digital system of claim 6 wherein:

said power management functionality wherein said functionality of registering a plurality of clients for notification of power events includes registering an indication of voltage/frequency setpoints supported by the client;

said power management functionality further including storing configuration data indicative of valid set points for each registered client;

said power management functionality further including the requested power event comprises a setpoint change; and

said power management functionality further including the method further comprises the step of verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

said power management functionality wherein the functionality of notifying the registered clients and causing the power event to occur are executed only if all registered clients are verified to operate at the requested setpoint.

20. The digital system of claim 6 wherein:

said power management functionality wherein the functionality of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification; and

said power management functionality wherein the functionality of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

8. A method for managing power consumption in a digital system comprising the steps of:

registering a plurality of clients for notification of power events;

receiving a request for a power event from a first client including receiving a notification timeout period;

notifying each of the registered clients of the power event;

receiving a response from at least a second client that the second client is not ready for the power event to occur;

causing the power event to occur after the second client indicates that the second client is ready for the power event to occur; and

wherein if the second client does not indicate that the second client is ready for the power event to occur within the notification timeout period, the notifying the first client that the timeout period has elapsed.

9. The method of claim 8 further comprising the step of unregistering a client of the plurality of clients when the client no longer wants notification of power events.

10. The method of claim 8 wherein:

said step of registering a plurality of clients for notification of power events includes registering an indication of voltage/frequency setpoints supported by the client;

storing configuration data indicative of valid set points for each registered client;

the requested power event comprises a setpoint change; and

the method further comprises the step of verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

the steps of notifying the registered clients and causing the power event to occur are executed only if all registered clients can operate at the requested setpoint.

11. The method of claim 8 wherein

the step of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification;

and

the step of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

12. A method for managing power consumption in a digital system comprising the steps of:

registering a plurality of clients for notification of power events, said registering including an indication of voltage/frequency setpoints supported by the client;

storing configuration data indicative of valid set points for each registered client;

receiving a request for a power event from a first client;

notifying each of the registered clients of the power event;

the requested power event comprises a setpoint change; and

verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

notifying the registered clients and causing the power event to occur only if all registered clients are verified to operate at the requested setpoint.

13. The method of claim 12 further comprising the step of unregistering a client of the plurality of clients when the client no longer wants notification of power events.

14. The method of claim 12 wherein

the step of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification;

and

the step of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

15. A method for managing power consumption in a digital system comprising the steps of:

registering a plurality of clients for notification of only the power events for which the client desires notification; and

receiving a request for a power event from a first client;

causing the power event to occur; and

notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

16. The method of claim 15 further comprising the step of unregistering a client of the plurality of clients when the client no longer wants notification of power events.

21. A digital system in which power consumption is dynamically managed during the operation of the digital system comprising:

a processor;

one or more peripheral devices coupled to the processor;

an operating system executable by the processor;

an application executable on the operating system; and

a power management module incorporated in the digital system wherein the power management module is an adjunct to the operating system and provides power management functionality for the digital system, said power management functionality including

registering a plurality of clients for notification of power events including receiving a notification timeout period;

receiving a request for a power event from a first client;

notifying each of the registered clients of the power event; and

receiving a response from at least a second client that the second client is not ready for the power event to occur;

causing the power event to occur after the second client indicates that the second client is ready for the power event to occur; and

if the second client does not indicate that the second client is ready for the power event to occur within the notification timeout period, the notifying the first client that the timeout period has elapsed.

22. The digital system of claim 21 wherein said power management functionality further including:

unregistering a client of the plurality of clients when the client no longer wants notification of power events.

23. The digital system of claim 21 wherein:

said power management functionality wherein said functionality of registering a plurality of clients for notification of power events includes registering an indication of voltage/frequency setpoints supported by the client;

said power management functionality further including storing configuration data indicative of valid set points for each registered client;

said power management functionality further including the requested power event comprises a setpoint change; and

said power management functionality further including the method further comprises the step of verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

said power management functionality wherein the functionality of notifying the registered clients and causing the power event to occur are executed only if all registered clients are verified to operate at the requested setpoint.

24. The digital system of claim 21 wherein:

said power management functionality wherein the functionality of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification; and

said power management functionality wherein the functionality of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

25. A digital system in which power consumption is dynamically managed during the operation of the digital system comprising:

a processor;

one or more peripheral devices coupled to the processor;

an operating system executable by the processor;

an application executable on the operating system; and

a power management module incorporated in the digital system wherein the power management module is an adjunct to the operating system and provides power management functionality for the digital system, said power management functionality including

registering a plurality of clients for notification of power events, said registering including an indication of voltage/frequency setpoints supported by the client;

storing configuration data indicative of valid set points for each registered client;

receiving a request for a power event from a first client;

notifying each of the registered clients of the power event;

the requested power event comprises a setpoint change; and

verifying that each of the registered clients can operate at a setpoint requested by the first client by reference to said stored configuration data; and

notifying the registered clients and causing the power event to occur only if all registered clients are verified to operate at the requested setpoint.

26. The digital system of claim 25 wherein said power management functionality further including:

unregistering a client of the plurality of clients when the client no longer wants notification of power events.

27. The digital system of claim 25 wherein:

said power management functionality wherein the functionality of registering further comprises each client of the plurality of clients registering for notification of only the power events for which the client desires notification; and

said power management functionality wherein the functionality of notifying further comprises notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

28. A digital system in which power consumption is dynamically managed during the operation of the digital system comprising:

a processor;

one or more peripheral devices coupled to the processor;

an operating system executable by the processor;

an application executable on the operating system; and

a power management module incorporated in the digital system wherein the power management module is an adjunct to the operating system and provides power management functionality for the digital system, said power management functionality including

registering a plurality of clients for notification of only the power events for which the client desires notification; and

receiving a request for a power event from a first client;

causing the power event to occur; and

notifying each of the registered clients of the power event if the registered client registered for notification of the requested power event.

29. The digital system of claim 28 wherein said power management functionality further including:

unregistering a client of the plurality of clients when the client no longer wants notification of power events.