mailbox.txt: standardize document format

Each text file under Documentation follows a different
format. Some doesn't even have titles!

Change its representation to follow the adopted standard,
using ReST markups for it to be parseable by Sphinx:

- Add markups for section titles;
- Use :Author: for authorship;
- Mark literal block as such and ident it.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

Documentation/mailbox.txt

-		The Common Mailbox Framework
-		Jassi Brar <jaswinder.singh@linaro.org>
+============================
+The Common Mailbox Framework
+============================
 
- This document aims to help developers write client and controller
+:Author: Jassi Brar <jaswinder.singh@linaro.org>
+
+This document aims to help developers write client and controller
 drivers for the API. But before we start, let us note that the
 client (especially) and controller drivers are likely going to be
 very platform specific because the remote firmware is likely to be
@@ -13,14 +16,17 @@ similar copies of code written for each platform. Having said that,
 nothing prevents the remote f/w to also be Linux based and use the
 same api there. However none of that helps us locally because we only
 ever deal at client's protocol level.
- Some of the choices made during implementation are the result of this
+
+Some of the choices made during implementation are the result of this
 peculiarity of this "common" framework.
 
 
 
-	Part 1 - Controller Driver (See include/linux/mailbox_controller.h)
+Controller Driver (See include/linux/mailbox_controller.h)
+==========================================================
 
- Allocate mbox_controller and the array of mbox_chan.
+
+Allocate mbox_controller and the array of mbox_chan.
 Populate mbox_chan_ops, except peek_data() all are mandatory.
 The controller driver might know a message has been consumed
 by the remote by getting an IRQ or polling some hardware flag
@@ -30,27 +36,30 @@ the controller driver should set via 'txdone_irq' or 'txdone_poll'
 or neither.
 
 
-	Part 2 - Client Driver (See include/linux/mailbox_client.h)
+Client Driver (See include/linux/mailbox_client.h)
+==================================================
+
 
- The client might want to operate in blocking mode (synchronously
+The client might want to operate in blocking mode (synchronously
 send a message through before returning) or non-blocking/async mode (submit
 a message and a callback function to the API and return immediately).
 
+::
 
-struct demo_client {
+	struct demo_client {
 		struct mbox_client cl;
 		struct mbox_chan *mbox;
 		struct completion c;
 		bool async;
 		/* ... */
-};
+	};
 
-/*
+	/*
 	* This is the handler for data received from remote. The behaviour is purely
 	* dependent upon the protocol. This is just an example.
 	*/
-static void message_from_remote(struct mbox_client *cl, void *mssg)
-{
+	static void message_from_remote(struct mbox_client *cl, void *mssg)
+	{
 		struct demo_client *dc = container_of(cl, struct demo_client, cl);
 		if (dc->async) {
 			if (is_an_ack(mssg)) {
@@ -63,16 +72,16 @@ static void message_from_remote(struct mbox_client *cl, void *mssg)
 			/* Remote f/w sends only ACK packets on this channel */
 			return;
 		}
-}
+	}
 
-static void sample_sent(struct mbox_client *cl, void *mssg, int r)
-{
+	static void sample_sent(struct mbox_client *cl, void *mssg, int r)
+	{
 		struct demo_client *dc = container_of(cl, struct demo_client, cl);
 		complete(&dc->c);
-}
+	}
 
-static void client_demo(struct platform_device *pdev)
-{
+	static void client_demo(struct platform_device *pdev)
+	{
 		struct demo_client *dc_sync, *dc_async;
 		/* The controller already knows async_pkt and sync_pkt */
 		struct async_pkt ap;
@@ -117,4 +126,4 @@ static void client_demo(struct platform_device *pdev)
 
 		/* Now wait for async chan to be done */
 		wait_for_completion(&dc_async->c);
-}
+	}