summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+samsung@kernel.org>2019-07-06 12:38:56 -0400
committerMauro Carvalho Chehab <mchehab+samsung@kernel.org>2019-07-15 10:03:04 -0400
commiteddeed127b06ea2542dc18f2fe37d383b6369fec (patch)
tree5a563f053f5dc09eaf83f8affc7d34c8636833c2 /Documentation/admin-guide
parentc2746a1eb741759590e8766958232d06a71840d5 (diff)
docs: don't use nested tables
Nested tables aren't supported for pdf output on Sphinx 1.7.9: admin-guide/laptops/sonypi:: nested tables are not yet implemented. admin-guide/laptops/toshiba_haps:: nested tables are not yet implemented. driver-api/nvdimm/btt:: nested tables are not yet implemented. s390/debugging390:: nested tables are not yet implemented. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com> # laptops
Diffstat (limited to 'Documentation/admin-guide')
-rw-r--r--Documentation/admin-guide/laptops/sonypi.rst28
-rw-r--r--Documentation/admin-guide/laptops/toshiba_haps.rst8
2 files changed, 17 insertions, 19 deletions
diff --git a/Documentation/admin-guide/laptops/sonypi.rst b/Documentation/admin-guide/laptops/sonypi.rst
index 2a1975ed7ee4..c6eaaf48f7c1 100644
--- a/Documentation/admin-guide/laptops/sonypi.rst
+++ b/Documentation/admin-guide/laptops/sonypi.rst
@@ -53,7 +53,7 @@ module or sonypi.<param>=<value> on the kernel boot line when sonypi is
53statically linked into the kernel). Those options are: 53statically linked into the kernel). Those options are:
54 54
55 =============== ======================================================= 55 =============== =======================================================
56 minor: minor number of the misc device /dev/sonypi, 56 minor: minor number of the misc device /dev/sonypi,
57 default is -1 (automatic allocation, see /proc/misc 57 default is -1 (automatic allocation, see /proc/misc
58 or kernel logs) 58 or kernel logs)
59 59
@@ -89,24 +89,22 @@ statically linked into the kernel). Those options are:
89 set to 0xffffffff, meaning that all possible events 89 set to 0xffffffff, meaning that all possible events
90 will be tried. You can use the following bits to 90 will be tried. You can use the following bits to
91 construct your own event mask (from 91 construct your own event mask (from
92 drivers/char/sonypi.h): 92 drivers/char/sonypi.h)::
93 93
94 ======================== ====== 94 SONYPI_JOGGER_MASK 0x0001
95 SONYPI_JOGGER_MASK 0x0001 95 SONYPI_CAPTURE_MASK 0x0002
96 SONYPI_CAPTURE_MASK 0x0002 96 SONYPI_FNKEY_MASK 0x0004
97 SONYPI_FNKEY_MASK 0x0004 97 SONYPI_BLUETOOTH_MASK 0x0008
98 SONYPI_BLUETOOTH_MASK 0x0008 98 SONYPI_PKEY_MASK 0x0010
99 SONYPI_PKEY_MASK 0x0010 99 SONYPI_BACK_MASK 0x0020
100 SONYPI_BACK_MASK 0x0020 100 SONYPI_HELP_MASK 0x0040
101 SONYPI_HELP_MASK 0x0040 101 SONYPI_LID_MASK 0x0080
102 SONYPI_LID_MASK 0x0080 102 SONYPI_ZOOM_MASK 0x0100
103 SONYPI_ZOOM_MASK 0x0100 103 SONYPI_THUMBPHRASE_MASK 0x0200
104 SONYPI_THUMBPHRASE_MASK 0x0200
105 SONYPI_MEYE_MASK 0x0400 104 SONYPI_MEYE_MASK 0x0400
106 SONYPI_MEMORYSTICK_MASK 0x0800 105 SONYPI_MEMORYSTICK_MASK 0x0800
107 SONYPI_BATTERY_MASK 0x1000 106 SONYPI_BATTERY_MASK 0x1000
108 SONYPI_WIRELESS_MASK 0x2000 107 SONYPI_WIRELESS_MASK 0x2000
109 ======================== ======
110 108
111 useinput: if set (which is the default) two input devices are 109 useinput: if set (which is the default) two input devices are
112 created, one which interprets the jogdial events as 110 created, one which interprets the jogdial events as
diff --git a/Documentation/admin-guide/laptops/toshiba_haps.rst b/Documentation/admin-guide/laptops/toshiba_haps.rst
index 11dfc428c080..d28b6c3f2849 100644
--- a/Documentation/admin-guide/laptops/toshiba_haps.rst
+++ b/Documentation/admin-guide/laptops/toshiba_haps.rst
@@ -75,11 +75,11 @@ The sysfs files under /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/ are:
75protection_level The protection_level is readable and writeable, and 75protection_level The protection_level is readable and writeable, and
76 provides a way to let userspace query the current protection 76 provides a way to let userspace query the current protection
77 level, as well as set the desired protection level, the 77 level, as well as set the desired protection level, the
78 available protection levels are: 78 available protection levels are::
79 79
80 ============ ======= ========== ======== 80 ============ ======= ========== ========
81 0 - Disabled 1 - Low 2 - Medium 3 - High 81 0 - Disabled 1 - Low 2 - Medium 3 - High
82 ============ ======= ========== ======== 82 ============ ======= ========== ========
83 83
84reset_protection The reset_protection entry is writeable only, being "1" 84reset_protection The reset_protection entry is writeable only, being "1"
85 the only parameter it accepts, it is used to trigger 85 the only parameter it accepts, it is used to trigger