Add SharedSplitControlC, for N clients needing shared access to something.

[tinyos-2.x.git] / doc / txt / tep114.txt

diff --git a/doc/txt/tep114.txt b/doc/txt/tep114.txt
index 70dff839515797a801b4748681b5a98ab5e8f887..235bf78794a73a5b690b3739c806501bc70de4e9 100644 (file)
--- a/doc/txt/tep114.txt
+++ b/doc/txt/tep114.txt
@@ -5,15 +5,10 @@ SIDs: Source and Sink Independent Drivers
 :TEP: 114
 :Group: Core Working Group
 :Type: Documentary 
-:Status: Draft
+:Status: Final
 :TinyOS-Version: 2.x
 :Author: Gilman Tolle, Philip Levis, and David Gay
 
-:Draft-Created: 30-Oct-2005
-:Draft-Version: $Revision$
-:Draft-Modified: $Date$
-:Draft-Discuss: TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu>
-
 .. Note::
 
    This memo documents a part of TinyOS for the TinyOS Community, and
@@ -54,13 +49,12 @@ and sensor values are always 16 bits, although only some subset of the
 bits may be significant (e.g., a 12-bit value).
 
 Because sensing is an integral part of high-level application logic,
-the asynchronicity of these events means that high-level components
-must work with atomic section, even if the sampling rate is very low
+having asynchronous events means that high-level components
+must work with atomic sections, even if the sampling rate is very low
 (e.g., every five minutes) and so could be easily placed in a
 task. Race conditions are problematic and possible in any real time
 multi-tasking design. Race conditions are a failure in design, and
-especially difficult to detect at low sampling rates. Careful and
-skillful design review practices flush out race conditions early on.
+especially difficult to detect at low sampling rates. 
 
 Additionally, not all sensors require ADC conversions from the MCU.
 Many sensors today are digital. To sample these sensors, the MCU sends
@@ -135,7 +129,7 @@ If the ``result`` parameter of the ``Read.readDone`` and
 ``val`` parameter MUST be filled with zeroes.
 
 If the call to ``read`` has returned SUCCESS, but the ``readDone``
-event has not yet been signalled, then a subsequent call to ``read``
+event has not yet been signaled, then a subsequent call to ``read``
 MUST return EBUSY or FAIL.  This simple locking technique, as opposed
 to a more complex system in which multiple read/readDone pairs may be
 outstanding, is intended to reduce the complexity of SID client code.
@@ -230,7 +224,7 @@ building a linked list.
 
 After posting at least one buffer, the client can call read() with a
 specified sample period in terms of microseconds. The driver then
-begins to fill the buffers in the queue, signalling the bufferDone()
+begins to fill the buffers in the queue, signaling the bufferDone()
 event when a buffer has been filled. The client MAY call postBuffer()
 after read() in order to provide the device with new storage for
 future reads.
@@ -284,12 +278,12 @@ connect a sensor into a more general system.
 ====================================================================
 
 | Gilman Tolle
-| 2168 Shattuck Ave.
-| Arched Rock Corporation
-| Berkeley, CA 94704
+| 501 2nd St. Ste 410
+| Arch Rock Corporation
+| San Francisco, CA 94107
 |
-| phone - +1 510 981 8714
-| email - gtolle@archedrock.com
+| phone - +1 415 692 0828
+| email - gtolle@archrock.com
 |
 |
 | Philip Levis
@@ -311,7 +305,7 @@ connect a sensor into a more general system.
 | email - david.e.gay@intel.com
 |
 
-6. Citations
+7. Citations
 ============================================================================
 
 .. [1] TEP 108: Resource Arbitration.