* Added in-page TOC to all pages.
* Removed "Introduction" title from all pages.
diff --git a/pdk/docs/guide/wakelock.jd b/pdk/docs/guide/wakelock.jd
index 1d8b425..ee59053 100755
--- a/pdk/docs/guide/wakelock.jd
+++ b/pdk/docs/guide/wakelock.jd
@@ -3,14 +3,17 @@
@jd:body
+<div id="qv-wrapper">
+<div id="qv">
+<h2>In this document</h2>
<a name="toc"/>
-<div style="padding:10px">
- <a href="#intro">Introduction</a><BR>
- <a href="#driverAPI">Driver API</a><br/>
- <a href="#userspaceAPI">User Space API</a><br/>
+<ul>
+<li><a href="#driverAPI">Driver API</a></li>
+<li><a href="#userspaceAPI">User Space API</a></li>
+</ul>
+</div>
</div>
- <a name="userspaceAPI"></a><h2>Introduction</h2>
<p>A locked wakelock, depending on its type, prevents the system from entering suspend or other low-power states. This document describes how to employ wakelocks. </p>
<p>There are two settings for a wakelock:</p>
<ul>
@@ -45,9 +48,9 @@
process-input-events +++ +++
</pre>
-<a name="driverAPI"></a><h2>Driver API</h2>
+<a name="driverAPI"></a><h3>Driver API</h3>
<p>A driver can use the wakelock API by adding a wakelock variable to its state and calling <code>wake_lock_init</code>, as illustrated in the snippet below:</p>
-<pre class="prettify">
+<pre>
struct state {
struct wakelock wakelock;
}
@@ -60,18 +63,18 @@
}
</pre>
<p> When the driver determines that it needs to run (usually in an interrupt handler), it calls <code>wake_lock</code>:</p>
-<pre class="prettify">
+<pre>
wake_lock(&state->wakelock);
</pre>
<p>When it no longer needs to run, it calls <code>wake_unlock</code>:</p>
-<pre class="prettify">
+<pre>
wake_unlock(&state->wakelock);
</pre>
<p> It can also call <code>wake_lock_timeout</code> to release the wakelock after a delay:</p>
-<pre class="prettify">
+<pre>
wake_lock_timeout(&state->wakelock, HZ);
</pre>
<p> This works whether or not the wakelock is already held. It is useful if the driver woke up other parts of the system that do not use wakelocks but still need to run. Avoid this when possible, since it will waste power if the timeout is long or may fail to finish needed work if the timeout is short.</p>
-<a name="userspaceAPI"></a><h2>User-space API</h2>
+<a name="userspaceAPI"></a><h3>User-space API</h3>
<p>Write <code>lockname</code> or <code>lockname timeout</code> to <code>/sys/power/wake_lock</code> lock and, if needed, create a wakelock. The timeout here is specified in nanoseconds. Write <code>lockname</code> to <code>/sys/power/wake_unlock</code> to unlock a user wakelock.</p>
<p> Do not use randomly generated wakelock names as there is no API to free a user-space wakelock.</p>
\ No newline at end of file