[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep115.txt,1.7,1.8
Kevin Klues
klueska at users.sourceforge.net
Fri Sep 14 15:45:32 PDT 2007
Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv28561/txt
Modified Files:
tep115.txt
Log Message:
Update to TEP115
Index: tep115.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep115.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep115.txt 21 Feb 2007 19:08:56 -0000 1.7
--- tep115.txt 14 Sep 2007 22:45:30 -0000 1.8
***************
*** 33,37 ****
TinyOS platforms have limited energy. A unified power management
! strategy for all devices and peripherpals is not feasible, as
they vary significantly in warm-up times, power profiles, and
operation latencies. While some devices, such as
--- 33,37 ----
TinyOS platforms have limited energy. A unified power management
! strategy for all devices and peripherals is not feasible, as
they vary significantly in warm-up times, power profiles, and
operation latencies. While some devices, such as
***************
*** 40,47 ****
times, require external knowledge to do so.
! In TinyOS 1.x, an application is responsible for all power management.
Low-level subsystems, such as an SPI bus, are explicitly powered on
and off by higher level abstractions. This approach of deep calls
! to StdControl.start and StdControl.stop introduces strange behaviors
and can get in the way of power conservation. Turning off the radio
on the Telos platform, for example, turns off the SPI bus and therefore
--- 40,47 ----
times, require external knowledge to do so.
! In TinyOS 1.x, applications are responsible for all power management.
Low-level subsystems, such as an SPI bus, are explicitly powered on
and off by higher level abstractions. This approach of deep calls
! to ``StdControl.start()`` and ``StdControl.stop()`` introduces strange behaviors
and can get in the way of power conservation. Turning off the radio
on the Telos platform, for example, turns off the SPI bus and therefore
***************
*** 74,78 ****
control the power state of a dedicated physical device (as defined by
[TEP108]_). Whenever this client tells the device to power up or down
! it does so without delay (albeit that caused by hardware). This model
can be particularly useful when the control information driving the
selection of the proper power state of a device relies on external
--- 74,79 ----
control the power state of a dedicated physical device (as defined by
[TEP108]_). Whenever this client tells the device to power up or down
! it does so without delay (except for delays in the hardware of course).
! This model
can be particularly useful when the control information driving the
selection of the proper power state of a device relies on external
***************
*** 136,140 ****
The selection of the right interface depends on the
latencies involved in changing between these two states as well as the
! nature of the code (sync or async) executing any of the interfaces
commands.
--- 137,141 ----
The selection of the right interface depends on the
latencies involved in changing between these two states as well as the
! nature of the code (sync or async) executing any of the interface's
commands.
***************
*** 173,177 ****
Upon the successful return of a call to ``StdControl.stop()``, a
device MUST be completely powered down, and any calls to commands
! of other interfaces implemented by that device MUST return FAIL or EOFF.
If a device is not able to complete the ``StdControl.start()`` or
--- 174,179 ----
Upon the successful return of a call to ``StdControl.stop()``, a
device MUST be completely powered down, and any calls to commands
! of other interfaces implemented by that device that actually access
! the device hardware MUST return FAIL or EOFF.
If a device is not able to complete the ``StdControl.start()`` or
***************
*** 207,211 ****
When a device's powerup and powerdown times are non-negligible, the
! *``SplitControl``* interface MUST be used in place of the *``StdControl``*
interface. The definition of this interface can be seen below::
--- 209,213 ----
When a device's powerup and powerdown times are non-negligible, the
! *``SplitControl``* interface SHOULD be used in place of the *``StdControl``*
interface. The definition of this interface can be seen below::
***************
*** 221,230 ****
device on and ``SplitControl.stop()`` to power a device off. Calls to
either command return one of SUCCESS, FAIL, EBUSY, or
! EALREADY. SUCCESS indicates that the device has now started chaning
! its power mode and it will signal a corresponding completion event in
! the future. EBUSY indicates that the device is in the midst of the
! other operation (e.g., it is starting when stop is called or stopping
when start is called) and will not issue an event. EALREADY indicates
! that the device is already in that state; the call is erroneus and a
completion event will not be signaled. FAIL indicates that the
device's power state could not be changed. More explicitly:
--- 223,232 ----
device on and ``SplitControl.stop()`` to power a device off. Calls to
either command return one of SUCCESS, FAIL, EBUSY, or
! EALREADY. SUCCESS indicates that the device has now started changing
! its power state and will signal a corresponding completion event in
! the future. EBUSY indicates that the device is in the midst of either starting
! or stopping (e.g., it is starting when stop is called or stopping
when start is called) and will not issue an event. EALREADY indicates
! that the device is already in that state; the call is erroneous and a
completion event will not be signaled. FAIL indicates that the
device's power state could not be changed. More explicitly:
***************
*** 242,246 ****
Upon signalling a ``SplitControl.stopDone(SUCCESS)``, a device MUST be
completely powered down, and any subsequent calls to commands of other
! interfaces implemented by the device MUST return EOFF or FAIL.
If a device is powered on and a successful call to ``SplitControl.stop()``
--- 244,249 ----
Upon signalling a ``SplitControl.stopDone(SUCCESS)``, a device MUST be
completely powered down, and any subsequent calls to commands of other
! interfaces implemented by the device that actually access
! the device hardware MUST return EOFF or FAIL.
If a device is powered on and a successful call to ``SplitControl.stop()``
***************
*** 263,267 ****
will be signaled in the future.
! Calls to `SplitControl.start()`` when the device is started
or ``SplitControl.stop()`` while the device is stopped MUST
return EALREADY, indicating that the device is already in that
--- 266,270 ----
will be signaled in the future.
! Calls to ``SplitControl.start()`` when the device is started
or ``SplitControl.stop()`` while the device is stopped MUST
return EALREADY, indicating that the device is already in that
***************
*** 269,273 ****
or stopDone for stop) MUST NOT be signaled.
! Calls to `SplitControl.start()`` when the device is stopping or
``SplitControl.stop()`` while the device is starting MUST return
EBUSY, indicating that the device is busy performing a differnet
--- 272,276 ----
or stopDone for stop) MUST NOT be signaled.
! Calls to ``SplitControl.start()`` when the device is stopping or
``SplitControl.stop()`` while the device is starting MUST return
EBUSY, indicating that the device is busy performing a differnet
***************
*** 298,302 ****
}
}
!
3.3 Power Management with ``AsyncStdControl``
--- 301,326 ----
}
}
!
! .. Note::
!
! Other approaches were considered for the return values of
! ``SplitControl.start()`` and ``SplitControl.stop()``. One such
! approach would have replaced EBUSY with SUCCESS when
! ``SplitControl.start()`` was called while in the process of stopping
! and ``SplitControl.stop()`` was called while in the process of starting.
! However, implementing such an approach adds unwanted complexity to
! a device driver. It is unreasonable to expect the implementor of
! each driver to implement this functionality.
!
! Returning EBUSY is the most straightforward, unambiguous value
! that can be returned in such a situation. By returning
! EBUSY when a device is in a transitional state, the components
! built on top of a driver unambiguously know exactly why a call to
! ``start()`` or ``stop()`` did not succeed, and can take action accordingly.
! Since only ONE component should ever implement the ``SplitControl``
! interface for a given device, it isn't unreasonable to expect them
! to keep track of this return value themselves. There is, of course,
! nothing preventing someone from creating a component
! on top of each driver implementation that implements things differently.
3.3 Power Management with ``AsyncStdControl``
***************
*** 381,385 ****
architectural support for enforcing a meaningful *default* power-management
policy instead of passing that task on to the application programmer to be
! solved on a case-by-case basis.
--- 405,410 ----
architectural support for enforcing a meaningful *default* power-management
policy instead of passing that task on to the application programmer to be
! solved on a case-by-case basis. The following section discusses these power
! management policies and the components that implement them in greater detail.
***************
*** 390,394 ****
arbitration functionality required by shared resources, generic power
management policies are also offered to allow the power management of
! non-virtualised devices to be automatically control.
Through the use of the arbiter components described in [TEP108]_,
--- 415,419 ----
arbitration functionality required by shared resources, generic power
management policies are also offered to allow the power management of
! non-virtualised devices to be automatically controlled.
Through the use of the arbiter components described in [TEP108]_,
***************
*** 438,444 ****
Upon receiving this event, the *Power Manager* MUST power up the
resource through the StdControl-like interface provided by the lower level
! abstraction of the physical device. The *Power Manager* SHOULD release the
ownership of the resource (using the ``ResourceDefaultOwner.release()``
! command) but MUST wait until after the resource has been fully powered on
before doing so.
--- 463,469 ----
Upon receiving this event, the *Power Manager* MUST power up the
resource through the StdControl-like interface provided by the lower level
! abstraction of the physical device. The *Power Manager* MUST release the
ownership of the resource (using the ``ResourceDefaultOwner.release()``
! command) and MUST wait until after the resource has been fully powered on
before doing so.
***************
*** 538,542 ****
a *deferred* power control scheme, whereby devices are powered
on immediately after being requested, but powered off after
! some small delay from being released.
Each policy has three different implementations for use by each of
--- 563,568 ----
a *deferred* power control scheme, whereby devices are powered
on immediately after being requested, but powered off after
! some small delay from being released. This delay is configurable
! to meet the varying needs of different device drivers.
Each policy has three different implementations for use by each of
***************
*** 560,569 ****
====================================================================
| Kevin Klues
! | 503 Bryan Hall
! | Washington University
! | St. Louis, MO 63130
|
! | phone - +1-314-935-6355
! | email - klueska at cs.wustl.edu
|
| Vlado Handziski
--- 586,594 ----
====================================================================
| Kevin Klues
! | 444 Gates Hall
! | Stanford University
! | Stanford, CA 94305-9030
|
! | email - klueska at cs.stanford.edu
|
| Vlado Handziski
More information about the Tinyos-2-commits
mailing list