updeshxp · ranon-rat · Feb 7, 2021 · Feb 7, 2021
diff --git a/Documentation/ABI/README → Documentation/ABI/README.md b/Documentation/ABI/README → Documentation/ABI/README.md
@@ -9,15 +9,15 @@ of stability according to the rules described below.
 
 The different levels of stability are:
 
-  stable/
+  - `stable/`
 	This directory documents the interfaces that the developer has
 	defined to be stable.  Userspace programs are free to use these
 	interfaces with no restrictions, and backward compatibility for
 	them will be guaranteed for at least 2 years.  Most interfaces
 	(like syscalls) are expected to never change and always be
 	available.
 
-  testing/
+  - `testing/`
 	This directory documents interfaces that are felt to be stable,
 	as the main development of this interface has been completed.
 	The interface can be changed to add new features, but the
@@ -31,34 +31,29 @@ The different levels of stability are:
 	notify them if any changes occur (see the description of the
 	layout of the files below for details on how to do this.)
 
-  obsolete/
+  - `obsolete/`
   	This directory documents interfaces that are still remaining in
 	the kernel, but are marked to be removed at some later point in
 	time.  The description of the interface will document the reason
 	why it is obsolete and when it can be expected to be removed.
 
-  removed/
+  - `removed/`
 	This directory contains a list of the old interfaces that have
 	been removed from the kernel.
 
 Every file in these directories will contain the following information:
 
-What:		Short description of the interface
-Date:		Date created
-KernelVersion:	Kernel version this feature first showed up in.
-Contact:	Primary contact for this interface (may be a mailing list)
-Description:	Long description of the interface and how to use it.
-Users:		All users of this interface who wish to be notified when
-		it changes.  This is very important for interfaces in
-		the "testing" stage, so that kernel developers can work
-		with userspace developers to ensure that things do not
-		break in ways that are unacceptable.  It is also
-		important to get feedback for these interfaces to make
-		sure they are working in a proper way and do not need to
-		be changed further.
 
+| What 			|		Short description of the interface|
+|--|--|
+| Date 			|	Date created|
+| KernelVersion |	Kernel version this feature first showed up in.|
+| Contact		|Primary contact for this interface (may be a mailing list)|
+| Description	|	Long description of the interface and how to use it.|
+| Users 		|		All users of this interface who wish to be notified when it changes.  This is very important for interfaces in the `testing` stage, so that kernel developerscan work with userspace developers to ensure that things do not break in ways that are unacceptable. It is also important to get feedback for these interfaces to make sure they are working in a properway and do not need to be changed further. |
 
-How things move between levels:
+
+# How things move between levels:
 
 Interfaces in stable may move to obsolete, as long as the proper
 notification is given.

diff --git a/Documentation/ABI/obsolete/sysfs-bus-usb b/Documentation/ABI/obsolete/sysfs-bus-usb
diff --git a/Documentation/ABI/obsolete/sysfs-bus-usb.md b/Documentation/ABI/obsolete/sysfs-bus-usb.md
@@ -0,0 +1,16 @@
+
+|||
+|--|--|
+|What:	|	/sys/bus/usb/devices/.../power/level
+|Date:	|	March 2007
+|KernelVersion:|	2.6.21
+|Contact:| 	Alan Stern <stern@rowland.harvard.edu>
+|Description:| Each USB device directory will contain a file named power/level.  This file holds a power-level setting for the device, either `on` or `auto`.
+- `on` means that the device is not allowed to autosuspend, although normal suspends for system sleep will still be honored.  `auto` means the device will autosuspend and autoresume in the usual manner, according to the capabilities of its driver. 
+- During normal use, devices should be left in the `auto` level.  The `on` level is meant for administrative uses. 
+- If you want to suspend a device immediately but leave it free to wake up in response to I/O requests, you should write `0` to power/autosuspend.  	
+- Device not capable of proper suspend and resume should be left in the `on` level. 
+- Although the USB spec requires devices to support suspend/resume, many of them do not. 	
+- In fact so many don't that by default, the USB core initializes all non-hub devices in the `on` level.  Some 	drivers may change this setting when they are bound.  	
+- This file is deprecated and will be removed after 2010. 
+- Use the power/control file instead; it does exactly the 	same thing. |
diff --git a/Documentation/android.txt → Documentation/android.md b/Documentation/android.txt → Documentation/android.md
@@ -1,6 +1,6 @@
-				=============
-				A N D R O I D
-				=============
+
+#	A N D R O I D
+
 
 Copyright (C) 2009 Google, Inc.
 Written by Mike Chan <mike@android.com>
@@ -16,7 +16,8 @@ CONTENTS:
 
 
 1. Android
-==========
+
+-------------
 
 Android (www.android.com) is an open source operating system for mobile devices.
 This document describes configurations needed to run the Android framework on
@@ -33,7 +34,7 @@ After building a standard defconfig, ensure that these options are enabled in
 your .config or defconfig if they are not already. Based off the msm_defconfig.
 You should keep the rest of the default options enabled in the defconfig
 unless you know what you are doing.
-
+```
 ANDROID_PARANOID_NETWORK
 ASHMEM
 CONFIG_FB_MODE_HELPERS
@@ -81,16 +82,18 @@ YAFFS_AUTO_YAFFS2
 YAFFS_FS
 YAFFS_YAFFS1
 YAFFS_YAFFS2
-
+```
 
 1.2 Required disabled config options
 ------------------------------------
+```
 CONFIG_YAFFS_DISABLE_LAZY_LOAD
 DNOTIFY
-
+```
 
 1.3 Recommended enabled config options
 ------------------------------
+```
 ANDROID_PMEM
 PSTORE_CONSOLE
 PSTORE_RAM
@@ -111,10 +114,9 @@ I2C_BOARDINFO
 LOG_BUF_SHIFT=17
 SERIAL_CORE
 SERIAL_CORE_CONSOLE
-
-
+```
 2. Contact
-==========
+-------------
 website: http://android.git.kernel.org
 
 mailing-lists: android-kernel@googlegroups.com