diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2009-04-27 15:06:31 +0200 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2009-06-12 18:01:47 +0200 |
commit | 19f594600110377ec4037fdf7fb93a25ec516212 (patch) | |
tree | bf88707b65f0138b754d896300976e474098a50d /Documentation/usb/WUSB-Design-overview.txt | |
parent | 19af5cdb7c79ff5ec96a99893ffb7f894f4a3dc1 (diff) | |
download | linux-19f594600110377ec4037fdf7fb93a25ec516212.tar.gz linux-19f594600110377ec4037fdf7fb93a25ec516212.tar.xz |
trivial: Miscellaneous documentation typo fixes
Fix various typos in documentation txts.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/usb/WUSB-Design-overview.txt')
-rw-r--r-- | Documentation/usb/WUSB-Design-overview.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/usb/WUSB-Design-overview.txt b/Documentation/usb/WUSB-Design-overview.txt index 4c3d62c7843a..c480e9c32dbd 100644 --- a/Documentation/usb/WUSB-Design-overview.txt +++ b/Documentation/usb/WUSB-Design-overview.txt @@ -84,7 +84,7 @@ The different logical parts of this driver are: *UWB*: the Ultra-Wide-Band stack -- manages the radio and associated spectrum to allow for devices sharing it. Allows to - control bandwidth assingment, beaconing, scanning, etc + control bandwidth assignment, beaconing, scanning, etc * @@ -184,7 +184,7 @@ and sends the replies and notifications back to the API [/uwb_rc_neh_grok()/]. Notifications are handled to the UWB daemon, that is chartered, among other things, to keep the tab of how the UWB radio neighborhood looks, creating and destroying devices as they show up or -dissapear. +disappear. Command execution is very simple: a command block is sent and a event block or reply is expected back. For sending/receiving command/events, a @@ -333,7 +333,7 @@ read descriptors and move our data. *Device life cycle and keep alives* -Everytime there is a succesful transfer to/from a device, we update a +Every time there is a successful transfer to/from a device, we update a per-device activity timestamp. If not, every now and then we check and if the activity timestamp gets old, we ping the device by sending it a Keep Alive IE; it responds with a /DN_Alive/ pong during the DNTS (this @@ -411,7 +411,7 @@ context (wa_xfer) and submit it. When the xfer is done, our callback is called and we assign the status bits and release the xfer resources. In dequeue() we are basically cancelling/aborting the transfer. We issue -a xfer abort request to the HC, cancell all the URBs we had submitted +a xfer abort request to the HC, cancel all the URBs we had submitted and not yet done and when all that is done, the xfer callback will be called--this will call the URB callback. |