Browse Source

SVN checkout

SVN tells me this is pretty clean so I hope it really is.  And no, I
will definitely not convert the SVN repo to git.
Max Reitz 7 months ago
commit
6b001036d6
100 changed files with 10303 additions and 0 deletions
  1. 18
    0
      COPYING
  2. 4148
    0
      CREDITS
  3. 2
    0
      Documentation/.gitignore
  4. 438
    0
      Documentation/00-INDEX
  5. 87
    0
      Documentation/ABI/README
  6. 31
    0
      Documentation/ABI/obsolete/sysfs-bus-usb
  7. 53
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo
  8. 153
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku
  9. 145
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
  10. 105
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure
  11. 116
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
  12. 7
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua
  13. 123
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
  14. 178
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos
  15. 77
    0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu
  16. 8
    0
      Documentation/ABI/obsolete/sysfs-firmware-acpi
  17. 30
    0
      Documentation/ABI/obsolete/sysfs-gpio
  18. 12
    0
      Documentation/ABI/removed/devfs
  19. 14
    0
      Documentation/ABI/removed/dv1394
  20. 9
    0
      Documentation/ABI/removed/ip_queue
  21. 8
    0
      Documentation/ABI/removed/net_dma
  22. 10
    0
      Documentation/ABI/removed/o2cb
  23. 15
    0
      Documentation/ABI/removed/raw1394
  24. 13
    0
      Documentation/ABI/removed/sysfs-class-rfkill
  25. 16
    0
      Documentation/ABI/removed/video1394
  26. 104
    0
      Documentation/ABI/stable/firewire-cdev
  27. 10
    0
      Documentation/ABI/stable/o2cb
  28. 10
    0
      Documentation/ABI/stable/syscalls
  29. 22
    0
      Documentation/ABI/stable/sysfs-acpi-pmprofile
  30. 133
    0
      Documentation/ABI/stable/sysfs-bus-firewire
  31. 19
    0
      Documentation/ABI/stable/sysfs-bus-nvmem
  32. 140
    0
      Documentation/ABI/stable/sysfs-bus-usb
  33. 141
    0
      Documentation/ABI/stable/sysfs-bus-vmbus
  34. 11
    0
      Documentation/ABI/stable/sysfs-bus-w1
  35. 75
    0
      Documentation/ABI/stable/sysfs-bus-xen-backend
  36. 56
    0
      Documentation/ABI/stable/sysfs-class-backlight
  37. 818
    0
      Documentation/ABI/stable/sysfs-class-infiniband
  38. 88
    0
      Documentation/ABI/stable/sysfs-class-rfkill
  39. 185
    0
      Documentation/ABI/stable/sysfs-class-tpm
  40. 221
    0
      Documentation/ABI/stable/sysfs-class-ubi
  41. 93
    0
      Documentation/ABI/stable/sysfs-class-udc
  42. 24
    0
      Documentation/ABI/stable/sysfs-devices
  43. 93
    0
      Documentation/ABI/stable/sysfs-devices-node
  44. 25
    0
      Documentation/ABI/stable/sysfs-devices-system-cpu
  45. 77
    0
      Documentation/ABI/stable/sysfs-devices-system-xen_memory
  46. 15
    0
      Documentation/ABI/stable/sysfs-driver-aspeed-vuart
  47. 30
    0
      Documentation/ABI/stable/sysfs-driver-dma-ioatdma
  48. 189
    0
      Documentation/ABI/stable/sysfs-driver-ib_srp
  49. 8
    0
      Documentation/ABI/stable/sysfs-driver-qla2xxx
  50. 62
    0
      Documentation/ABI/stable/sysfs-driver-usb-usbtmc
  51. 15
    0
      Documentation/ABI/stable/sysfs-driver-w1_ds28e04
  52. 6
    0
      Documentation/ABI/stable/sysfs-driver-w1_ds28ea00
  53. 75
    0
      Documentation/ABI/stable/sysfs-firmware-efi-vars
  54. 41
    0
      Documentation/ABI/stable/sysfs-firmware-opal-dump
  55. 60
    0
      Documentation/ABI/stable/sysfs-firmware-opal-elog
  56. 87
    0
      Documentation/ABI/stable/sysfs-fs-orangefs
  57. 119
    0
      Documentation/ABI/stable/sysfs-hypervisor-xen
  58. 34
    0
      Documentation/ABI/stable/sysfs-module
  59. 58
    0
      Documentation/ABI/stable/sysfs-transport-srp
  60. 4
    0
      Documentation/ABI/stable/thermal-notification
  61. 28
    0
      Documentation/ABI/stable/vdso
  62. 36
    0
      Documentation/ABI/testing/configfs-acpi
  63. 34
    0
      Documentation/ABI/testing/configfs-iio
  64. 30
    0
      Documentation/ABI/testing/configfs-rdma_cm
  65. 31
    0
      Documentation/ABI/testing/configfs-spear-pcie-gadget
  66. 48
    0
      Documentation/ABI/testing/configfs-stp-policy
  67. 126
    0
      Documentation/ABI/testing/configfs-usb-gadget
  68. 8
    0
      Documentation/ABI/testing/configfs-usb-gadget-acm
  69. 16
    0
      Documentation/ABI/testing/configfs-usb-gadget-ecm
  70. 14
    0
      Documentation/ABI/testing/configfs-usb-gadget-eem
  71. 9
    0
      Documentation/ABI/testing/configfs-usb-gadget-ffs
  72. 11
    0
      Documentation/ABI/testing/configfs-usb-gadget-hid
  73. 8
    0
      Documentation/ABI/testing/configfs-usb-gadget-loopback
  74. 31
    0
      Documentation/ABI/testing/configfs-usb-gadget-mass-storage
  75. 12
    0
      Documentation/ABI/testing/configfs-usb-gadget-midi
  76. 15
    0
      Documentation/ABI/testing/configfs-usb-gadget-ncm
  77. 9
    0
      Documentation/ABI/testing/configfs-usb-gadget-obex
  78. 8
    0
      Documentation/ABI/testing/configfs-usb-gadget-phonet
  79. 9
    0
      Documentation/ABI/testing/configfs-usb-gadget-printer
  80. 17
    0
      Documentation/ABI/testing/configfs-usb-gadget-rndis
  81. 9
    0
      Documentation/ABI/testing/configfs-usb-gadget-serial
  82. 14
    0
      Documentation/ABI/testing/configfs-usb-gadget-sourcesink
  83. 14
    0
      Documentation/ABI/testing/configfs-usb-gadget-subset
  84. 6
    0
      Documentation/ABI/testing/configfs-usb-gadget-tcm
  85. 14
    0
      Documentation/ABI/testing/configfs-usb-gadget-uac1
  86. 12
    0
      Documentation/ABI/testing/configfs-usb-gadget-uac1_legacy
  87. 12
    0
      Documentation/ABI/testing/configfs-usb-gadget-uac2
  88. 265
    0
      Documentation/ABI/testing/configfs-usb-gadget-uvc
  89. 40
    0
      Documentation/ABI/testing/debugfs-cec-error-inj
  90. 91
    0
      Documentation/ABI/testing/debugfs-driver-genwqe
  91. 20
    0
      Documentation/ABI/testing/debugfs-ec
  92. 19
    0
      Documentation/ABI/testing/debugfs-ideapad
  93. 16
    0
      Documentation/ABI/testing/debugfs-olpc
  94. 45
    0
      Documentation/ABI/testing/debugfs-pfo-nx-crypto
  95. 19
    0
      Documentation/ABI/testing/debugfs-pktcdvd
  96. 41
    0
      Documentation/ABI/testing/dell-smbios-wmi
  97. 110
    0
      Documentation/ABI/testing/dev-kmsg
  98. 33
    0
      Documentation/ABI/testing/devlink-resource-mlxsw
  99. 59
    0
      Documentation/ABI/testing/evm
  100. 0
    0
      Documentation/ABI/testing/gpio-cdev

+ 18
- 0
COPYING View File

@@ -0,0 +1,18 @@
1
+The Linux Kernel is provided under:
2
+
3
+	SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
4
+
5
+Being under the terms of the GNU General Public License version 2 only,
6
+according with:
7
+
8
+	LICENSES/preferred/GPL-2.0
9
+
10
+With an explicit syscall exception, as stated at:
11
+
12
+	LICENSES/exceptions/Linux-syscall-note
13
+
14
+In addition, other licenses may also apply. Please see:
15
+
16
+	Documentation/process/license-rules.rst
17
+
18
+for more details.

+ 4148
- 0
CREDITS
File diff suppressed because it is too large
View File


+ 2
- 0
Documentation/.gitignore View File

@@ -0,0 +1,2 @@
1
+output
2
+*.pyc

+ 438
- 0
Documentation/00-INDEX View File

@@ -0,0 +1,438 @@
1
+
2
+This is a brief list of all the files in ./linux/Documentation and what
3
+they contain. If you add a documentation file, please list it here in
4
+alphabetical order as well, or risk being hunted down like a rabid dog.
5
+Please keep the descriptions small enough to fit on one line.
6
+							 Thanks -- Paul G.
7
+
8
+Following translations are available on the WWW:
9
+
10
+   - Japanese, maintained by the JF Project (jf@listserv.linux.or.jp), at
11
+     http://linuxjf.sourceforge.jp/
12
+
13
+00-INDEX
14
+	- this file.
15
+ABI/
16
+	- info on kernel <-> userspace ABI and relative interface stability.
17
+CodingStyle
18
+	- nothing here, just a pointer to process/coding-style.rst.
19
+DMA-API.txt
20
+	- DMA API, pci_ API & extensions for non-consistent memory machines.
21
+DMA-API-HOWTO.txt
22
+	- Dynamic DMA mapping Guide
23
+DMA-ISA-LPC.txt
24
+	- How to do DMA with ISA (and LPC) devices.
25
+DMA-attributes.txt
26
+	- listing of the various possible attributes a DMA region can have
27
+EDID/
28
+	- directory with info on customizing EDID for broken gfx/displays.
29
+IPMI.txt
30
+	- info on Linux Intelligent Platform Management Interface (IPMI) Driver.
31
+IRQ-affinity.txt
32
+	- how to select which CPU(s) handle which interrupt events on SMP.
33
+IRQ-domain.txt
34
+	- info on interrupt numbering and setting up IRQ domains.
35
+IRQ.txt
36
+	- description of what an IRQ is.
37
+Intel-IOMMU.txt
38
+	- basic info on the Intel IOMMU virtualization support.
39
+Makefile
40
+	- It's not of interest for those who aren't touching the build system.
41
+PCI/
42
+	- info related to PCI drivers.
43
+RCU/
44
+	- directory with info on RCU (read-copy update).
45
+SAK.txt
46
+	- info on Secure Attention Keys.
47
+SM501.txt
48
+	- Silicon Motion SM501 multimedia companion chip
49
+SubmittingPatches
50
+	- nothing here, just a pointer to process/coding-style.rst.
51
+accounting/
52
+	- documentation on accounting and taskstats.
53
+acpi/
54
+	- info on ACPI-specific hooks in the kernel.
55
+admin-guide/
56
+	- info related to Linux users and system admins.
57
+aoe/
58
+	- description of AoE (ATA over Ethernet) along with config examples.
59
+arm/
60
+	- directory with info about Linux on the ARM architecture.
61
+arm64/
62
+	- directory with info about Linux on the 64 bit ARM architecture.
63
+auxdisplay/
64
+	- misc. LCD driver documentation (cfag12864b, ks0108).
65
+backlight/
66
+	- directory with info on controlling backlights in flat panel displays
67
+bcache.txt
68
+	- Block-layer cache on fast SSDs to improve slow (raid) I/O performance.
69
+block/
70
+	- info on the Block I/O (BIO) layer.
71
+blockdev/
72
+	- info on block devices & drivers
73
+bt8xxgpio.txt
74
+	- info on how to modify a bt8xx video card for GPIO usage.
75
+btmrvl.txt
76
+	- info on Marvell Bluetooth driver usage.
77
+bus-devices/
78
+	- directory with info on TI GPMC (General Purpose Memory Controller)
79
+bus-virt-phys-mapping.txt
80
+	- how to access I/O mapped memory from within device drivers.
81
+cachetlb.txt
82
+	- describes the cache/TLB flushing interfaces Linux uses.
83
+cdrom/
84
+	- directory with information on the CD-ROM drivers that Linux has.
85
+cgroup-v1/
86
+	- cgroups v1 features, including cpusets and memory controller.
87
+cgroup-v2.txt
88
+	- cgroups v2 features, including cpusets and memory controller.
89
+circular-buffers.txt
90
+	- how to make use of the existing circular buffer infrastructure
91
+clk.txt
92
+	- info on the common clock framework
93
+cma/
94
+	- Continuous Memory Area (CMA) debugfs interface.
95
+conf.py
96
+	- It's not of interest for those who aren't touching the build system.
97
+connector/
98
+	- docs on the netlink based userspace<->kernel space communication mod.
99
+console/
100
+	- documentation on Linux console drivers.
101
+core-api/
102
+	- documentation on kernel core components.
103
+cpu-freq/
104
+	- info on CPU frequency and voltage scaling.
105
+cpu-hotplug.txt
106
+	- document describing CPU hotplug support in the Linux kernel.
107
+cpu-load.txt
108
+	- document describing how CPU load statistics are collected.
109
+cpuidle/
110
+	- info on CPU_IDLE, CPU idle state management subsystem.
111
+cputopology.txt
112
+	- documentation on how CPU topology info is exported via sysfs.
113
+crc32.txt
114
+	- brief tutorial on CRC computation
115
+crypto/
116
+	- directory with info on the Crypto API.
117
+dcdbas.txt
118
+	- information on the Dell Systems Management Base Driver.
119
+debugging-modules.txt
120
+	- some notes on debugging modules after Linux 2.6.3.
121
+debugging-via-ohci1394.txt
122
+	- how to use firewire like a hardware debugger memory reader.
123
+dell_rbu.txt
124
+	- document demonstrating the use of the Dell Remote BIOS Update driver.
125
+dev-tools/
126
+	- directory with info on development tools for the kernel.
127
+device-mapper/
128
+	- directory with info on Device Mapper.
129
+dmaengine/
130
+	- the DMA engine and controller API guides.
131
+devicetree/
132
+	- directory with info on device tree files used by OF/PowerPC/ARM
133
+digsig.txt
134
+	-info on the Digital Signature Verification API
135
+dma-buf-sharing.txt
136
+	- the DMA Buffer Sharing API Guide
137
+docutils.conf
138
+	- nothing here. Just a configuration file for docutils.
139
+dontdiff
140
+	- file containing a list of files that should never be diff'ed.
141
+driver-api/
142
+	- the Linux driver implementer's API guide.
143
+driver-model/
144
+	- directory with info about Linux driver model.
145
+early-userspace/
146
+	- info about initramfs, klibc, and userspace early during boot.
147
+efi-stub.txt
148
+	- How to use the EFI boot stub to bypass GRUB or elilo on EFI systems.
149
+eisa.txt
150
+	- info on EISA bus support.
151
+extcon/
152
+	- directory with porting guide for Android kernel switch driver.
153
+isa.txt
154
+	- info on EISA bus support.
155
+fault-injection/
156
+	- dir with docs about the fault injection capabilities infrastructure.
157
+fb/
158
+	- directory with info on the frame buffer graphics abstraction layer.
159
+features/
160
+	- status of feature implementation on different architectures.
161
+filesystems/
162
+	- info on the vfs and the various filesystems that Linux supports.
163
+firmware_class/
164
+	- request_firmware() hotplug interface info.
165
+flexible-arrays.txt
166
+	- how to make use of flexible sized arrays in linux
167
+fmc/
168
+	- information about the FMC bus abstraction
169
+fpga/
170
+	- FPGA Manager Core.
171
+futex-requeue-pi.txt
172
+	- info on requeueing of tasks from a non-PI futex to a PI futex
173
+gcc-plugins.txt
174
+	- GCC plugin infrastructure.
175
+gpio/
176
+	- gpio related documentation
177
+gpu/
178
+	- directory with information on GPU driver developer's guide.
179
+hid/
180
+	- directory with information on human interface devices
181
+highuid.txt
182
+	- notes on the change from 16 bit to 32 bit user/group IDs.
183
+hwspinlock.txt
184
+	- hardware spinlock provides hardware assistance for synchronization
185
+timers/
186
+	- info on the timer related topics
187
+hw_random.txt
188
+	- info on Linux support for random number generator in i8xx chipsets.
189
+hwmon/
190
+	- directory with docs on various hardware monitoring drivers.
191
+i2c/
192
+	- directory with info about the I2C bus/protocol (2 wire, kHz speed).
193
+x86/i386/
194
+	- directory with info about Linux on Intel 32 bit architecture.
195
+ia64/
196
+	- directory with info about Linux on Intel 64 bit architecture.
197
+ide/
198
+	- Information regarding the Enhanced IDE drive.
199
+iio/
200
+	- info on industrial IIO configfs support.
201
+index.rst
202
+	- main index for the documentation at ReST format.
203
+infiniband/
204
+	- directory with documents concerning Linux InfiniBand support.
205
+input/
206
+	- info on Linux input device support.
207
+intel_txt.txt
208
+	- info on intel Trusted Execution Technology (intel TXT).
209
+io-mapping.txt
210
+	- description of io_mapping functions in linux/io-mapping.h
211
+io_ordering.txt
212
+	- info on ordering I/O writes to memory-mapped addresses.
213
+ioctl/
214
+	- directory with documents describing various IOCTL calls.
215
+iostats.txt
216
+	- info on I/O statistics Linux kernel provides.
217
+irqflags-tracing.txt
218
+	- how to use the irq-flags tracing feature.
219
+isapnp.txt
220
+	- info on Linux ISA Plug & Play support.
221
+isdn/
222
+	- directory with info on the Linux ISDN support, and supported cards.
223
+kbuild/
224
+	- directory with info about the kernel build process.
225
+kdump/
226
+	- directory with mini HowTo on getting the crash dump code to work.
227
+doc-guide/
228
+	- how to write and format reStructuredText kernel documentation
229
+kernel-per-CPU-kthreads.txt
230
+	- List of all per-CPU kthreads and how they introduce jitter.
231
+kobject.txt
232
+	- info of the kobject infrastructure of the Linux kernel.
233
+kprobes.txt
234
+	- documents the kernel probes debugging feature.
235
+kref.txt
236
+	- docs on adding reference counters (krefs) to kernel objects.
237
+laptops/
238
+	- directory with laptop related info and laptop driver documentation.
239
+ldm.txt
240
+	- a brief description of LDM (Windows Dynamic Disks).
241
+leds/
242
+	- directory with info about LED handling under Linux.
243
+livepatch/
244
+	- info on kernel live patching.
245
+locking/
246
+	- directory with info about kernel locking primitives
247
+lockup-watchdogs.txt
248
+	- info on soft and hard lockup detectors (aka nmi_watchdog).
249
+logo.gif
250
+	- full colour GIF image of Linux logo (penguin - Tux).
251
+logo.txt
252
+	- info on creator of above logo & site to get additional images from.
253
+lsm.txt
254
+	- Linux Security Modules: General Security Hooks for Linux
255
+lzo.txt
256
+	- kernel LZO decompressor input formats
257
+m68k/
258
+	- directory with info about Linux on Motorola 68k architecture.
259
+mailbox.txt
260
+	- How to write drivers for the common mailbox framework (IPC).
261
+md/
262
+	- directory with info about Linux Software RAID
263
+media/
264
+	- info on media drivers: uAPI, kAPI and driver documentation.
265
+memory-barriers.txt
266
+	- info on Linux kernel memory barriers.
267
+memory-devices/
268
+	- directory with info on parts like the Texas Instruments EMIF driver
269
+memory-hotplug.txt
270
+	- Hotpluggable memory support, how to use and current status.
271
+men-chameleon-bus.txt
272
+	- info on MEN chameleon bus.
273
+mic/
274
+	- Intel Many Integrated Core (MIC) architecture device driver.
275
+mips/
276
+	- directory with info about Linux on MIPS architecture.
277
+misc-devices/
278
+	- directory with info about devices using the misc dev subsystem
279
+mmc/
280
+	- directory with info about the MMC subsystem
281
+mtd/
282
+	- directory with info about memory technology devices (flash)
283
+namespaces/
284
+	- directory with various information about namespaces
285
+netlabel/
286
+	- directory with information on the NetLabel subsystem.
287
+networking/
288
+	- directory with info on various aspects of networking with Linux.
289
+nfc/
290
+	- directory relating info about Near Field Communications support.
291
+nios2/
292
+	- Linux on the Nios II architecture.
293
+nommu-mmap.txt
294
+	- documentation about no-mmu memory mapping support.
295
+numastat.txt
296
+	- info on how to read Numa policy hit/miss statistics in sysfs.
297
+ntb.txt
298
+	- info on Non-Transparent Bridge (NTB) drivers.
299
+nvdimm/
300
+	- info on non-volatile devices.
301
+nvmem/
302
+	- info on non volatile memory framework.
303
+output/
304
+	- default directory where html/LaTeX/pdf files will be written.
305
+padata.txt
306
+	- An introduction to the "padata" parallel execution API
307
+parisc/
308
+	- directory with info on using Linux on PA-RISC architecture.
309
+parport-lowlevel.txt
310
+	- description and usage of the low level parallel port functions.
311
+pcmcia/
312
+	- info on the Linux PCMCIA driver.
313
+percpu-rw-semaphore.txt
314
+	- RCU based read-write semaphore optimized for locking for reading
315
+perf/
316
+	- info about the APM X-Gene SoC Performance Monitoring Unit (PMU).
317
+phy/
318
+	- ino on Samsung USB 2.0 PHY adaptation layer.
319
+phy.txt
320
+	- Description of the generic PHY framework.
321
+pi-futex.txt
322
+	- documentation on lightweight priority inheritance futexes.
323
+pinctrl.txt
324
+	- info on pinctrl subsystem and the PINMUX/PINCONF and drivers
325
+platform/
326
+	- List of supported hardware by compal and Dell laptop.
327
+pnp.txt
328
+	- Linux Plug and Play documentation.
329
+power/
330
+	- directory with info on Linux PCI power management.
331
+powerpc/
332
+	- directory with info on using Linux with the PowerPC.
333
+prctl/
334
+	- directory with info on the priveledge control subsystem
335
+preempt-locking.txt
336
+	- info on locking under a preemptive kernel.
337
+process/
338
+	- how to work with the mainline kernel development process.
339
+pps/
340
+	- directory with information on the pulse-per-second support
341
+pti/
342
+	- directory with info on Intel MID PTI.
343
+ptp/
344
+	- directory with info on support for IEEE 1588 PTP clocks in Linux.
345
+pwm.txt
346
+	- info on the pulse width modulation driver subsystem
347
+rapidio/
348
+	- directory with info on RapidIO packet-based fabric interconnect
349
+rbtree.txt
350
+	- info on what red-black trees are and what they are for.
351
+remoteproc.txt
352
+	- info on how to handle remote processor (e.g. AMP) offloads/usage.
353
+rfkill.txt
354
+	- info on the radio frequency kill switch subsystem/support.
355
+robust-futex-ABI.txt
356
+	- documentation of the robust futex ABI.
357
+robust-futexes.txt
358
+	- a description of what robust futexes are.
359
+rpmsg.txt
360
+	- info on the Remote Processor Messaging (rpmsg) Framework
361
+rtc.txt
362
+	- notes on how to use the Real Time Clock (aka CMOS clock) driver.
363
+s390/
364
+	- directory with info on using Linux on the IBM S390.
365
+scheduler/
366
+	- directory with info on the scheduler.
367
+scsi/
368
+	- directory with info on Linux scsi support.
369
+security/
370
+	- directory that contains security-related info
371
+serial/
372
+	- directory with info on the low level serial API.
373
+sgi-ioc4.txt
374
+	- description of the SGI IOC4 PCI (multi function) device.
375
+sh/
376
+	- directory with info on porting Linux to a new architecture.
377
+smsc_ece1099.txt
378
+	-info on the smsc Keyboard Scan Expansion/GPIO Expansion device.
379
+sound/
380
+	- directory with info on sound card support.
381
+spi/
382
+	- overview of Linux kernel Serial Peripheral Interface (SPI) support.
383
+sphinx/
384
+	- no documentation here, just files required by Sphinx toolchain.
385
+sphinx-static/
386
+	- no documentation here, just files required by Sphinx toolchain.
387
+static-keys.txt
388
+	- info on how static keys allow debug code in hotpaths via patching
389
+svga.txt
390
+	- short guide on selecting video modes at boot via VGA BIOS.
391
+sync_file.txt
392
+	- Sync file API guide.
393
+sysctl/
394
+	- directory with info on the /proc/sys/* files.
395
+target/
396
+	- directory with info on generating TCM v4 fabric .ko modules
397
+tee.txt
398
+	- info on the TEE subsystem and drivers
399
+this_cpu_ops.txt
400
+	- List rationale behind and the way to use this_cpu operations.
401
+thermal/
402
+	- directory with information on managing thermal issues (CPU/temp)
403
+trace/
404
+	- directory with info on tracing technologies within linux
405
+translations/
406
+	- translations of this document from English to another language
407
+unaligned-memory-access.txt
408
+	- info on how to avoid arch breaking unaligned memory access in code.
409
+unshare.txt
410
+	- description of the Linux unshare system call.
411
+usb/
412
+	- directory with info regarding the Universal Serial Bus.
413
+vfio.txt
414
+	- info on Virtual Function I/O used in guest/hypervisor instances.
415
+video-output.txt
416
+	- sysfs class driver interface to enable/disable a video output device.
417
+virtual/
418
+	- directory with information on the various linux virtualizations.
419
+vm/
420
+	- directory with info on the Linux vm code.
421
+w1/
422
+	- directory with documents regarding the 1-wire (w1) subsystem.
423
+watchdog/
424
+	- how to auto-reboot Linux if it has "fallen and can't get up". ;-)
425
+wimax/
426
+	- directory with info about Intel Wireless Wimax Connections
427
+core-api/workqueue.rst
428
+	- information on the Concurrency Managed Workqueue implementation
429
+x86/x86_64/
430
+	- directory with info on Linux support for AMD x86-64 (Hammer) machines.
431
+xillybus.txt
432
+	- Overview and basic ui of xillybus driver
433
+xtensa/
434
+	- directory with documents relating to arch/xtensa port/implementation
435
+xz.txt
436
+	- how to make use of the XZ data compression within linux kernel
437
+zorro.txt
438
+	- info on writing drivers for Zorro bus devices found on Amigas.

+ 87
- 0
Documentation/ABI/README View File

@@ -0,0 +1,87 @@
1
+This directory attempts to document the ABI between the Linux kernel and
2
+userspace, and the relative stability of these interfaces.  Due to the
3
+everchanging nature of Linux, and the differing maturity levels, these
4
+interfaces should be used by userspace programs in different ways.
5
+
6
+We have four different levels of ABI stability, as shown by the four
7
+different subdirectories in this location.  Interfaces may change levels
8
+of stability according to the rules described below.
9
+
10
+The different levels of stability are:
11
+
12
+  stable/
13
+	This directory documents the interfaces that the developer has
14
+	defined to be stable.  Userspace programs are free to use these
15
+	interfaces with no restrictions, and backward compatibility for
16
+	them will be guaranteed for at least 2 years.  Most interfaces
17
+	(like syscalls) are expected to never change and always be
18
+	available.
19
+
20
+  testing/
21
+	This directory documents interfaces that are felt to be stable,
22
+	as the main development of this interface has been completed.
23
+	The interface can be changed to add new features, but the
24
+	current interface will not break by doing this, unless grave
25
+	errors or security problems are found in them.  Userspace
26
+	programs can start to rely on these interfaces, but they must be
27
+	aware of changes that can occur before these interfaces move to
28
+	be marked stable.  Programs that use these interfaces are
29
+	strongly encouraged to add their name to the description of
30
+	these interfaces, so that the kernel developers can easily
31
+	notify them if any changes occur (see the description of the
32
+	layout of the files below for details on how to do this.)
33
+
34
+  obsolete/
35
+  	This directory documents interfaces that are still remaining in
36
+	the kernel, but are marked to be removed at some later point in
37
+	time.  The description of the interface will document the reason
38
+	why it is obsolete and when it can be expected to be removed.
39
+
40
+  removed/
41
+	This directory contains a list of the old interfaces that have
42
+	been removed from the kernel.
43
+
44
+Every file in these directories will contain the following information:
45
+
46
+What:		Short description of the interface
47
+Date:		Date created
48
+KernelVersion:	Kernel version this feature first showed up in.
49
+Contact:	Primary contact for this interface (may be a mailing list)
50
+Description:	Long description of the interface and how to use it.
51
+Users:		All users of this interface who wish to be notified when
52
+		it changes.  This is very important for interfaces in
53
+		the "testing" stage, so that kernel developers can work
54
+		with userspace developers to ensure that things do not
55
+		break in ways that are unacceptable.  It is also
56
+		important to get feedback for these interfaces to make
57
+		sure they are working in a proper way and do not need to
58
+		be changed further.
59
+
60
+
61
+How things move between levels:
62
+
63
+Interfaces in stable may move to obsolete, as long as the proper
64
+notification is given.
65
+
66
+Interfaces may be removed from obsolete and the kernel as long as the
67
+documented amount of time has gone by.
68
+
69
+Interfaces in the testing state can move to the stable state when the
70
+developers feel they are finished.  They cannot be removed from the
71
+kernel tree without going through the obsolete state first.
72
+
73
+It's up to the developer to place their interfaces in the category they
74
+wish for it to start out in.
75
+
76
+
77
+Notable bits of non-ABI, which should not under any circumstances be considered
78
+stable:
79
+
80
+- Kconfig.  Userspace should not rely on the presence or absence of any
81
+  particular Kconfig symbol, in /proc/config.gz, in the copy of .config
82
+  commonly installed to /boot, or in any invocation of the kernel build
83
+  process.
84
+
85
+- Kernel-internal symbols.  Do not rely on the presence, absence, location, or
86
+  type of any kernel symbol, either in System.map files or the kernel binary
87
+  itself.  See Documentation/process/stable-api-nonsense.rst.

+ 31
- 0
Documentation/ABI/obsolete/sysfs-bus-usb View File

@@ -0,0 +1,31 @@
1
+What:		/sys/bus/usb/devices/.../power/level
2
+Date:		March 2007
3
+KernelVersion:	2.6.21
4
+Contact:	Alan Stern <stern@rowland.harvard.edu>
5
+Description:
6
+		Each USB device directory will contain a file named
7
+		power/level.  This file holds a power-level setting for
8
+		the device, either "on" or "auto".
9
+
10
+		"on" means that the device is not allowed to autosuspend,
11
+		although normal suspends for system sleep will still
12
+		be honored.  "auto" means the device will autosuspend
13
+		and autoresume in the usual manner, according to the
14
+		capabilities of its driver.
15
+
16
+		During normal use, devices should be left in the "auto"
17
+		level.  The "on" level is meant for administrative uses.
18
+		If you want to suspend a device immediately but leave it
19
+		free to wake up in response to I/O requests, you should
20
+		write "0" to power/autosuspend.
21
+
22
+		Device not capable of proper suspend and resume should be
23
+		left in the "on" level.  Although the USB spec requires
24
+		devices to support suspend/resume, many of them do not.
25
+		In fact so many don't that by default, the USB core
26
+		initializes all non-hub devices in the "on" level.  Some
27
+		drivers may change this setting when they are bound.
28
+
29
+		This file is deprecated and will be removed after 2010.
30
+		Use the power/control file instead; it does exactly the
31
+		same thing.

+ 53
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo View File

@@ -0,0 +1,53 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/actual_profile
2
+Date:		Januar 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 1-5.
5
+		When read, this attribute returns the number of the actual
6
+		profile which is also the profile that's active on device startup.
7
+		When written this attribute activates the selected profile
8
+		immediately.
9
+Users:		http://roccat.sourceforge.net
10
+
11
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/button
12
+Date:		Januar 2011
13
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
14
+Description:	The keyboard can store short macros with consist of 1 button with
15
+		several modifier keys internally.
16
+		When written, this file lets one set the sequence for a specific
17
+		button for a specific profile. Button and profile numbers are
18
+		included in written data. The data has to be 24 bytes long.
19
+		This file is writeonly.
20
+Users:		http://roccat.sourceforge.net
21
+
22
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/info
23
+Date:		Januar 2011
24
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
25
+Description:	When read, this file returns some info about the device like the
26
+		installed firmware version.
27
+		The size of the data is 8 bytes in size.
28
+		This file is readonly.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/key_mask
32
+Date:		Januar 2011
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	The keyboard lets the user deactivate 5 certain keys like the
35
+		windows and application keys, to protect the user from the outcome
36
+		of accidentally pressing them.
37
+		The integer value of this attribute has bits 0-4 set depending
38
+		on the state of the corresponding key.
39
+		When read, this file returns the current state of the buttons.
40
+		When written, the given buttons are activated/deactivated
41
+		immediately.
42
+Users:		http://roccat.sourceforge.net
43
+
44
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/mode_key
45
+Date:		Januar 2011
46
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
47
+Description:	The keyboard has a condensed layout without num-lock key.
48
+		Instead it uses a mode-key which activates a gaming mode where
49
+		the assignment of the number block changes.
50
+		The integer value of this attribute ranges from 0 (OFF) to 1 (ON).
51
+		When read, this file returns the actual state of the key.
52
+		When written, the key is activated/deactivated immediately.
53
+Users:		http://roccat.sourceforge.net

+ 153
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku View File

@@ -0,0 +1,153 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/actual_profile
2
+Date:		June 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 0-4.
5
+		When read, this attribute returns the number of the actual
6
+		profile. This value is persistent, so its equivalent to the
7
+		profile that's active when the device is powered on next time.
8
+		When written, this file sets the number of the startup profile
9
+		and the device activates this profile immediately.
10
+Users:		http://roccat.sourceforge.net
11
+
12
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/info
13
+Date:		June 2011
14
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
15
+Description:	When read, this file returns general data like firmware version.
16
+		The data is 6 bytes long.
17
+		This file is readonly.
18
+Users:		http://roccat.sourceforge.net
19
+
20
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/key_mask
21
+Date:		June 2011
22
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
23
+Description:	When written, this file lets one deactivate certain keys like
24
+		windows and application keys, to prevent accidental presses.
25
+		Profile number for which this settings occur is included in
26
+		written data. The data has to be 6 bytes long.
27
+		Before reading this file, control has to be written to select
28
+		which profile to read.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_capslock
32
+Date:		June 2011
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	When written, this file lets one set the function of the
35
+		capslock key for a specific profile. Profile number is included
36
+		in written data. The data has to be 6 bytes long.
37
+		Before reading this file, control has to be written to select
38
+		which profile to read.
39
+Users:		http://roccat.sourceforge.net
40
+
41
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_easyzone
42
+Date:		June 2011
43
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
44
+Description:	When written, this file lets one set the function of the
45
+		easyzone keys for a specific profile. Profile number is included
46
+		in written data. The data has to be 65 bytes long.
47
+		Before reading this file, control has to be written to select
48
+		which profile to read.
49
+Users:		http://roccat.sourceforge.net
50
+
51
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_function
52
+Date:		June 2011
53
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
54
+Description:	When written, this file lets one set the function of the
55
+		function keys for a specific profile. Profile number is included
56
+		in written data. The data has to be 41 bytes long.
57
+		Before reading this file, control has to be written to select
58
+		which profile to read.
59
+Users:		http://roccat.sourceforge.net
60
+
61
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_macro
62
+Date:		June 2011
63
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
64
+Description:	When written, this file lets one set the function of the macro
65
+		keys for a specific profile. Profile number is included in
66
+		written data. The data has to be 35 bytes long.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_media
72
+Date:		June 2011
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	When written, this file lets one set the function of the media
75
+		keys for a specific profile. Profile number is included in
76
+		written data. The data has to be 29 bytes long.
77
+		Before reading this file, control has to be written to select
78
+		which profile to read.
79
+Users:		http://roccat.sourceforge.net
80
+
81
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_thumbster
82
+Date:		June 2011
83
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
84
+Description:	When written, this file lets one set the function of the
85
+		thumbster keys for a specific profile. Profile number is included
86
+		in written data. The data has to be 23 bytes long.
87
+		Before reading this file, control has to be written to select
88
+		which profile to read.
89
+Users:		http://roccat.sourceforge.net
90
+
91
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/last_set
92
+Date:		June 2011
93
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
94
+Description:	When written, this file lets one set the time in secs since
95
+		epoch in which the last configuration took place.
96
+		The data has to be 20 bytes long.
97
+Users:		http://roccat.sourceforge.net
98
+
99
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/light
100
+Date:		June 2011
101
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
102
+Description:	When written, this file lets one set the backlight intensity for
103
+		a specific profile. Profile number is included in written data.
104
+		The data has to be 10 bytes long for Isku, IskuFX needs	16 bytes
105
+		of data.
106
+		Before reading this file, control has to be written to select
107
+		which profile to read.
108
+Users:		http://roccat.sourceforge.net
109
+
110
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/macro
111
+Date:		June 2011
112
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
113
+Description:	When written, this file lets one store macros with max 500
114
+		keystrokes for a specific button for a specific profile.
115
+		Button and profile numbers are included in written data.
116
+		The data has to be 2083 bytes long.
117
+		Before reading this file, control has to be written to select
118
+		which profile and key to read.
119
+Users:		http://roccat.sourceforge.net
120
+
121
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/reset
122
+Date:		November 2012
123
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
124
+Description:	When written, this file lets one reset the device.
125
+		The data has to be 3 bytes long.
126
+		This file is writeonly.
127
+Users:		http://roccat.sourceforge.net
128
+
129
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/control
130
+Date:		June 2011
131
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
132
+Description:	When written, this file lets one select which data from which
133
+		profile will be	read next. The data has to be 3 bytes long.
134
+		This file is writeonly.
135
+Users:		http://roccat.sourceforge.net
136
+
137
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/talk
138
+Date:		June 2011
139
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
140
+Description:	When written, this file lets one trigger easyshift functionality
141
+		from the host.
142
+		The data has to be 16 bytes long.
143
+		This file is writeonly.
144
+Users:		http://roccat.sourceforge.net
145
+
146
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/talkfx
147
+Date:		February 2013
148
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
149
+Description:	When written, this file lets one trigger temporary color schemes
150
+		from the host.
151
+		The data has to be 16 bytes long.
152
+		This file is writeonly.
153
+Users:		http://roccat.sourceforge.net

+ 145
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus View File

@@ -0,0 +1,145 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/actual_profile
2
+Date:		October 2010
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 0-4.
5
+                When read, this attribute returns the number of the actual
6
+                profile. This value is persistent, so its equivalent to the
7
+                profile that's active when the mouse is powered on next time.
8
+		When written, this file sets the number of the startup profile
9
+		and the mouse activates this profile immediately.
10
+Users:		http://roccat.sourceforge.net
11
+
12
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/startup_profile
13
+Date:		October 2010
14
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
15
+Description:	The integer value of this attribute ranges from 0-4.
16
+                When read, this attribute returns the number of the actual
17
+                profile. This value is persistent, so its equivalent to the
18
+                profile that's active when the mouse is powered on next time.
19
+		When written, this file sets the number of the startup profile
20
+		and the mouse activates this profile immediately.
21
+		Please use actual_profile, it does the same thing.
22
+Users:		http://roccat.sourceforge.net
23
+
24
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/firmware_version
25
+Date:		October 2010
26
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
27
+Description:	When read, this file returns the raw integer version number of the
28
+		firmware reported by the mouse. Using the integer value eases
29
+		further usage in other programs. To receive the real version
30
+		number the decimal point has to be shifted 2 positions to the
31
+		left. E.g. a returned value of 121 means 1.21
32
+		This file is readonly.
33
+		Please read binary attribute info which contains firmware version.
34
+Users:		http://roccat.sourceforge.net
35
+
36
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/info
37
+Date:		November 2012
38
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
39
+Description:	When read, this file returns general data like firmware version.
40
+		When written, the device can be reset.
41
+		The data is 8 bytes long.
42
+Users:		http://roccat.sourceforge.net
43
+
44
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/macro
45
+Date:		October 2010
46
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
47
+Description:	The mouse can store a macro with max 500 key/button strokes
48
+		internally.
49
+		When written, this file lets one set the sequence for a specific
50
+		button for a specific profile. Button and profile numbers are
51
+		included in written data. The data has to be 2082 bytes long.
52
+		This file is writeonly.
53
+Users:		http://roccat.sourceforge.net
54
+
55
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_buttons
56
+Date:		August 2010
57
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
58
+Description:	The mouse can store 5 profiles which can be switched by the
59
+		press of a button. A profile is split in settings and buttons.
60
+		profile_buttons holds information about button layout.
61
+		When written, this file lets one write the respective profile
62
+		buttons back to the mouse. The data has to be 77 bytes long.
63
+		The mouse will reject invalid data.
64
+		Which profile to write is determined by the profile number
65
+		contained in the data.
66
+		Before reading this file, control has to be written to select
67
+		which profile to read.
68
+Users:		http://roccat.sourceforge.net
69
+
70
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_buttons
71
+Date:		August 2010
72
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
73
+Description:	The mouse can store 5 profiles which can be switched by the
74
+		press of a button. A profile is split in settings and buttons.
75
+		profile_buttons holds information about button layout.
76
+		When read, these files return the respective profile buttons.
77
+		The returned data is 77 bytes in size.
78
+		This file is readonly.
79
+		Write control to select profile and read profile_buttons instead.
80
+Users:		http://roccat.sourceforge.net
81
+
82
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_settings
83
+Date:		October 2010
84
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
85
+Description:	The mouse can store 5 profiles which can be switched by the
86
+		press of a button. A profile is split in settings and buttons.
87
+		profile_settings holds information like resolution, sensitivity
88
+		and light effects.
89
+		When written, this file lets one write the respective profile
90
+		settings back to the mouse. The data has to be 43 bytes long.
91
+		The mouse will reject invalid data.
92
+		Which profile to write is determined by the profile number
93
+		contained in the data.
94
+		Before reading this file, control has to be written to select
95
+		which profile to read.
96
+Users:		http://roccat.sourceforge.net
97
+
98
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_settings
99
+Date:		August 2010
100
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
101
+Description:	The mouse can store 5 profiles which can be switched by the
102
+		press of a button. A profile is split in settings and buttons.
103
+		profile_settings holds information like resolution, sensitivity
104
+		and light effects.
105
+		When read, these files return the respective profile settings.
106
+		The returned data is 43 bytes in size.
107
+		This file is readonly.
108
+		Write control to select profile and read profile_settings instead.
109
+Users:		http://roccat.sourceforge.net
110
+
111
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/sensor
112
+Date:		October 2010
113
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
114
+Description:	The mouse has a tracking- and a distance-control-unit. These
115
+		can be activated/deactivated and the lift-off distance can be
116
+		set. The data has to be 6 bytes long.
117
+		This file is writeonly.
118
+Users:		http://roccat.sourceforge.net
119
+
120
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/talk
121
+Date:		May 2011
122
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
123
+Description:	Used to active some easy* functions of the mouse from outside.
124
+		The data has to be 16 bytes long.
125
+		This file is writeonly.
126
+Users:		http://roccat.sourceforge.net
127
+
128
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu
129
+Date:		October 2010
130
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
131
+Description:	When written a calibration process for the tracking control unit
132
+		can be initiated/cancelled. Also lets one read/write sensor
133
+		registers.
134
+		The data has to be 4 bytes long.
135
+Users:		http://roccat.sourceforge.net
136
+
137
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu_image
138
+Date:		October 2010
139
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
140
+Description:	When read the mouse returns a 30x30 pixel image of the
141
+		sampled underground. This works only in the course of a
142
+		calibration process initiated with tcu.
143
+		The returned data is 1028 bytes in size.
144
+		This file is readonly.
145
+Users:		http://roccat.sourceforge.net

+ 105
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure View File

@@ -0,0 +1,105 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/actual_profile
2
+Date:		December 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The mouse can store 5 profiles which can be switched by the
5
+		press of a button. actual_profile holds number of actual profile.
6
+		This value is persistent, so its value determines the profile
7
+		that's active when the mouse is powered on next time.
8
+		When written, the mouse activates the set profile immediately.
9
+		The data has to be 3 bytes long.
10
+		The mouse will reject invalid data.
11
+Users:		http://roccat.sourceforge.net
12
+
13
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/control
14
+Date:		December 2012
15
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
16
+Description:	When written, this file lets one select which data from which
17
+		profile will be	read next. The data has to be 3 bytes long.
18
+		This file is writeonly.
19
+Users:		http://roccat.sourceforge.net
20
+
21
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/info
22
+Date:		December 2012
23
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
24
+Description:	When read, this file returns general data like firmware version.
25
+		When written, the device can be reset.
26
+		The data is 6 bytes long.
27
+Users:		http://roccat.sourceforge.net
28
+
29
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/macro
30
+Date:		December 2012
31
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
32
+Description:	The mouse can store a macro with max 500 key/button strokes
33
+		internally.
34
+		When written, this file lets one set the sequence for a specific
35
+		button for a specific profile. Button and profile numbers are
36
+		included in written data. The data has to be 2082 bytes long.
37
+		This file is writeonly.
38
+Users:		http://roccat.sourceforge.net
39
+
40
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/profile_buttons
41
+Date:		December 2012
42
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
43
+Description:	The mouse can store 5 profiles which can be switched by the
44
+		press of a button. A profile is split in settings and buttons.
45
+		profile_buttons holds information about button layout.
46
+		When written, this file lets one write the respective profile
47
+		buttons back to the mouse. The data has to be 59 bytes long.
48
+		The mouse will reject invalid data.
49
+		Which profile to write is determined by the profile number
50
+		contained in the data.
51
+		Before reading this file, control has to be written to select
52
+		which profile to read.
53
+Users:		http://roccat.sourceforge.net
54
+
55
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/profile_settings
56
+Date:		December 2012
57
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
58
+Description:	The mouse can store 5 profiles which can be switched by the
59
+		press of a button. A profile is split in settings and buttons.
60
+		profile_settings holds information like resolution, sensitivity
61
+		and light effects.
62
+		When written, this file lets one write the respective profile
63
+		settings back to the mouse. The data has to be 31 bytes long.
64
+		The mouse will reject invalid data.
65
+		Which profile to write is determined by the profile number
66
+		contained in the data.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/sensor
72
+Date:		December 2012
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	The mouse has a tracking- and a distance-control-unit. These
75
+		can be activated/deactivated and the lift-off distance can be
76
+		set. The data has to be 6 bytes long.
77
+		This file is writeonly.
78
+Users:		http://roccat.sourceforge.net
79
+
80
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/talk
81
+Date:		December 2012
82
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
83
+Description:	Used to active some easy* functions of the mouse from outside.
84
+		The data has to be 16 bytes long.
85
+		This file is writeonly.
86
+Users:		http://roccat.sourceforge.net
87
+
88
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/tcu
89
+Date:		December 2012
90
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
91
+Description:	When written a calibration process for the tracking control unit
92
+		can be initiated/cancelled. Also lets one read/write sensor
93
+		registers.
94
+		The data has to be 4 bytes long.
95
+Users:		http://roccat.sourceforge.net
96
+
97
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/tcu_image
98
+Date:		December 2012
99
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
100
+Description:	When read the mouse returns a 30x30 pixel image of the
101
+		sampled underground. This works only in the course of a
102
+		calibration process initiated with tcu.
103
+		The returned data is 1028 bytes in size.
104
+		This file is readonly.
105
+Users:		http://roccat.sourceforge.net

+ 116
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus View File

@@ -0,0 +1,116 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_cpi
2
+Date:		January 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 1-4.
5
+		When read, this attribute returns the number of the active
6
+		cpi level.
7
+		This file is readonly.
8
+		Has never been used. If bookkeeping is done, it's done in userland tools.
9
+Users:		http://roccat.sourceforge.net
10
+
11
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_profile
12
+Date:		January 2011
13
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
14
+Description:	The integer value of this attribute ranges from 0-4.
15
+		When read, this attribute returns the number of the active
16
+		profile.
17
+		When written, the mouse activates this profile immediately.
18
+		The profile that's active when powered down is the same that's
19
+		active when the mouse is powered on.
20
+Users:		http://roccat.sourceforge.net
21
+
22
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x
23
+Date:		January 2011
24
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
25
+Description:	The integer value of this attribute ranges from 1-10.
26
+		When read, this attribute returns the number of the actual
27
+		sensitivity in x direction.
28
+		This file is readonly.
29
+		Has never been used. If bookkeeping is done, it's done in userland tools.
30
+Users:		http://roccat.sourceforge.net
31
+
32
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_y
33
+Date:		January 2011
34
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
35
+Description:	The integer value of this attribute ranges from 1-10.
36
+		When read, this attribute returns the number of the actual
37
+		sensitivity in y direction.
38
+		This file is readonly.
39
+		Has never been used. If bookkeeping is done, it's done in userland tools.
40
+Users:		http://roccat.sourceforge.net
41
+
42
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/firmware_version
43
+Date:		January 2011
44
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
45
+Description:	When read, this file returns the raw integer version number of the
46
+		firmware reported by the mouse. Using the integer value eases
47
+		further usage in other programs. To receive the real version
48
+		number the decimal point has to be shifted 2 positions to the
49
+		left. E.g. a returned value of 121 means 1.21
50
+		This file is readonly.
51
+		Obsoleted by binary sysfs attribute "info".
52
+Users:		http://roccat.sourceforge.net
53
+
54
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/info
55
+Date:		November 2012
56
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
57
+Description:	When read, this file returns general data like firmware version.
58
+		When written, the device can be reset.
59
+		The data is 6 bytes long.
60
+Users:		http://roccat.sourceforge.net
61
+
62
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_buttons
63
+Date:		January 2011
64
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
65
+Description:	The mouse can store 5 profiles which can be switched by the
66
+		press of a button. A profile is split in settings and buttons.
67
+		profile_buttons holds information about button layout.
68
+		When written, this file lets one write the respective profile
69
+		buttons back to the mouse. The data has to be 23 bytes long.
70
+		The mouse will reject invalid data.
71
+		Which profile to write is determined by the profile number
72
+		contained in the data.
73
+		Before reading this file, control has to be written to select
74
+		which profile to read.
75
+Users:		http://roccat.sourceforge.net
76
+
77
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_buttons
78
+Date:		January 2011
79
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
80
+Description:	The mouse can store 5 profiles which can be switched by the
81
+		press of a button. A profile is split in settings and buttons.
82
+		profile_buttons holds information about button layout.
83
+		When read, these files return the respective profile buttons.
84
+		The returned data is 23 bytes in size.
85
+		This file is readonly.
86
+		Write control to select profile and read profile_buttons instead.
87
+Users:		http://roccat.sourceforge.net
88
+
89
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_settings
90
+Date:		January 2011
91
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
92
+Description:	The mouse can store 5 profiles which can be switched by the
93
+		press of a button. A profile is split in settings and buttons.
94
+		profile_settings holds information like resolution, sensitivity
95
+		and light effects.
96
+		When written, this file lets one write the respective profile
97
+		settings back to the mouse. The data has to be 16 bytes long.
98
+		The mouse will reject invalid data.
99
+		Which profile to write is determined by the profile number
100
+		contained in the data.
101
+		Before reading this file, control has to be written to select
102
+		which profile to read.
103
+Users:		http://roccat.sourceforge.net
104
+
105
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_settings
106
+Date:		January 2011
107
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
108
+Description:	The mouse can store 5 profiles which can be switched by the
109
+		press of a button. A profile is split in settings and buttons.
110
+		profile_settings holds information like resolution, sensitivity
111
+		and light effects.
112
+		When read, these files return the respective profile settings.
113
+		The returned data is 16 bytes in size.
114
+		This file is readonly.
115
+		Write control to select profile and read profile_settings instead.
116
+Users:		http://roccat.sourceforge.net

+ 7
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua View File

@@ -0,0 +1,7 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/control
2
+Date:		October 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	When written, cpi, button and light settings can be configured.
5
+		When read, actual cpi setting and sensor data are returned.
6
+		The data has to be 8 bytes long.
7
+Users:		http://roccat.sourceforge.net

+ 123
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra View File

@@ -0,0 +1,123 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_cpi
2
+Date:		August 2010
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	It is possible to switch the cpi setting of the mouse with the
5
+		press of a button.
6
+		When read, this file returns the raw number of the actual cpi
7
+		setting reported by the mouse. This number has to be further
8
+		processed to receive the real dpi value.
9
+
10
+		VALUE DPI
11
+		1     400
12
+		2     800
13
+		4     1600
14
+
15
+		This file is readonly.
16
+		Has never been used. If bookkeeping is done, it's done in userland tools.
17
+Users:		http://roccat.sourceforge.net
18
+
19
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_profile
20
+Date:		August 2010
21
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
22
+Description:	When read, this file returns the number of the actual profile in
23
+		range 0-4.
24
+		This file is readonly.
25
+		Please use binary attribute "settings" which provides this information.
26
+Users:		http://roccat.sourceforge.net
27
+
28
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/firmware_version
29
+Date:		August 2010
30
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
31
+Description:	When read, this file returns the raw integer version number of the
32
+		firmware reported by the mouse. Using the integer value eases
33
+		further usage in other programs. To receive the real version
34
+		number the decimal point has to be shifted 2 positions to the
35
+		left. E.g. a returned value of 138 means 1.38
36
+		This file is readonly.
37
+		Please use binary attribute "info" which provides this information.
38
+Users:		http://roccat.sourceforge.net
39
+
40
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/info
41
+Date:		November 2012
42
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
43
+Description:	When read, this file returns general data like firmware version.
44
+		When written, the device can be reset.
45
+		The data is 6 bytes long.
46
+Users:		http://roccat.sourceforge.net
47
+
48
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_buttons
49
+Date:		August 2010
50
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
51
+Description:	The mouse can store 5 profiles which can be switched by the
52
+		press of a button. A profile is split in settings and buttons.
53
+		profile_buttons holds information about button layout.
54
+		When written, this file lets one write the respective profile
55
+		buttons back to the mouse. The data has to be 19 bytes long.
56
+		The mouse will reject invalid data.
57
+		Which profile to write is determined by the profile number
58
+		contained in the data.
59
+		Before reading this file, control has to be written to select
60
+		which profile to read.
61
+Users:		http://roccat.sourceforge.net
62
+
63
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_buttons
64
+Date:		August 2010
65
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
66
+Description:	The mouse can store 5 profiles which can be switched by the
67
+		press of a button. A profile is split in settings and buttons.
68
+		profile_buttons holds information about button layout.
69
+		When read, these files return the respective profile buttons.
70
+		The returned data is 19 bytes in size.
71
+		This file is readonly.
72
+		Write control to select profile and read profile_buttons instead.
73
+Users:		http://roccat.sourceforge.net
74
+
75
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_settings
76
+Date:		August 2010
77
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
78
+Description:	The mouse can store 5 profiles which can be switched by the
79
+		press of a button. A profile is split in settings and buttons.
80
+		profile_settings holds information like resolution, sensitivity
81
+		and light effects.
82
+		When written, this file lets one write the respective profile
83
+		settings back to the mouse. The data has to be 13 bytes long.
84
+		The mouse will reject invalid data.
85
+		Which profile to write is determined by the profile number
86
+		contained in the data.
87
+		Before reading this file, control has to be written to select
88
+		which profile to read.
89
+Users:		http://roccat.sourceforge.net
90
+
91
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_settings
92
+Date:		August 2010
93
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
94
+Description:	The mouse can store 5 profiles which can be switched by the
95
+		press of a button. A profile is split in settings and buttons.
96
+		profile_settings holds information like resolution, sensitivity
97
+		and light effects.
98
+		When read, these files return the respective profile settings.
99
+		The returned data is 13 bytes in size.
100
+		This file is readonly.
101
+		Write control to select profile and read profile_settings instead.
102
+Users:		http://roccat.sourceforge.net
103
+
104
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/settings
105
+Date:		August 2010
106
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
107
+Description:	When read, this file returns the settings stored in the mouse.
108
+		The size of the data is 3 bytes and holds information on the
109
+		startup_profile.
110
+		When written, this file lets write settings back to the mouse.
111
+		The data has to be 3 bytes long. The mouse will reject invalid
112
+		data.
113
+Users:		http://roccat.sourceforge.net
114
+
115
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/startup_profile
116
+Date:		August 2010
117
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
118
+Description:	The integer value of this attribute ranges from 0-4.
119
+                When read, this attribute returns the number of the profile
120
+                that's active when the mouse is powered on.
121
+		This file is readonly.
122
+		Please use binary attribute "settings" which provides this information.
123
+Users:		http://roccat.sourceforge.net

+ 178
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos View File

@@ -0,0 +1,178 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/control
2
+Date:		October 2013
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	When written, this file lets one select which data from which
5
+		profile will be	read next. The data has to be 3 bytes long.
6
+		This file is writeonly.
7
+Users:		http://roccat.sourceforge.net
8
+
9
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/profile
10
+Date:		October 2013
11
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
12
+Description:	The mouse can store 5 profiles which can be switched by the
13
+		press of a button. profile holds index of actual profile.
14
+		This value is persistent, so its value determines the profile
15
+		that's active when the device is powered on next time.
16
+		When written, the device activates the set profile immediately.
17
+		The data has to be 3 bytes long.
18
+		The device will reject invalid data.
19
+Users:		http://roccat.sourceforge.net
20
+
21
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_primary
22
+Date:		October 2013
23
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
24
+Description:	When written, this file lets one set the default of all keys for
25
+		a specific profile. Profile index is included in written data.
26
+		The data has to be 125 bytes long.
27
+		Before reading this file, control has to be written to select
28
+		which profile to read.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_function
32
+Date:		October 2013
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	When written, this file lets one set the function of the
35
+		function keys for a specific profile. Profile index is included
36
+		in written data. The data has to be 95 bytes long.
37
+		Before reading this file, control has to be written to select
38
+		which profile to read.
39
+Users:		http://roccat.sourceforge.net
40
+
41
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_macro
42
+Date:		October 2013
43
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
44
+Description:	When written, this file lets one set the function of the macro
45
+		keys for a specific profile. Profile index is included in
46
+		written data. The data has to be 35 bytes long.
47
+		Before reading this file, control has to be written to select
48
+		which profile to read.
49
+Users:		http://roccat.sourceforge.net
50
+
51
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_thumbster
52
+Date:		October 2013
53
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
54
+Description:	When written, this file lets one set the function of the
55
+		thumbster keys for a specific profile. Profile index is included
56
+		in written data. The data has to be 23 bytes long.
57
+		Before reading this file, control has to be written to select
58
+		which profile to read.
59
+Users:		http://roccat.sourceforge.net
60
+
61
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_extra
62
+Date:		October 2013
63
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
64
+Description:	When written, this file lets one set the function of the
65
+		capslock and function keys for a specific profile. Profile index
66
+		is included in written data. The data has to be 8 bytes long.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_easyzone
72
+Date:		October 2013
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	When written, this file lets one set the function of the
75
+		easyzone keys for a specific profile. Profile index is included
76
+		in written data. The data has to be 294 bytes long.
77
+		Before reading this file, control has to be written to select
78
+		which profile to read.
79
+Users:		http://roccat.sourceforge.net
80
+
81
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/key_mask
82
+Date:		October 2013
83
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
84
+Description:	When written, this file lets one deactivate certain keys like
85
+		windows and application keys, to prevent accidental presses.
86
+		Profile index for which this settings occur is included in
87
+		written data. The data has to be 6 bytes long.
88
+		Before reading this file, control has to be written to select
89
+		which profile to read.
90
+Users:		http://roccat.sourceforge.net
91
+
92
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light
93
+Date:		October 2013
94
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
95
+Description:	When written, this file lets one set the backlight intensity for
96
+		a specific profile. Profile index is included in written data.
97
+		This attribute is only valid for the glow and pro variant.
98
+		The data has to be 16 bytes long.
99
+		Before reading this file, control has to be written to select
100
+		which profile to read.
101
+Users:		http://roccat.sourceforge.net
102
+
103
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/macro
104
+Date:		October 2013
105
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
106
+Description:	When written, this file lets one store macros with max 480
107
+		keystrokes for a specific button for a specific profile.
108
+		Button and profile indexes are included in written data.
109
+		The data has to be 2002 bytes long.
110
+		Before reading this file, control has to be written to select
111
+		which profile and key to read.
112
+Users:		http://roccat.sourceforge.net
113
+
114
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/info
115
+Date:		October 2013
116
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
117
+Description:	When read, this file returns general data like firmware version.
118
+		The data is 8 bytes long.
119
+		This file is readonly.
120
+Users:		http://roccat.sourceforge.net
121
+
122
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/reset
123
+Date:		October 2013
124
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
125
+Description:	When written, this file lets one reset the device.
126
+		The data has to be 3 bytes long.
127
+		This file is writeonly.
128
+Users:		http://roccat.sourceforge.net
129
+
130
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/talk
131
+Date:		October 2013
132
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
133
+Description:	When written, this file lets one trigger easyshift functionality
134
+		from the host.
135
+		The data has to be 16 bytes long.
136
+		This file is writeonly.
137
+Users:		http://roccat.sourceforge.net
138
+
139
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light_control
140
+Date:		October 2013
141
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
142
+Description:	When written, this file lets one switch between stored and custom
143
+		light settings.
144
+		This attribute is only valid for the pro variant.
145
+		The data has to be 8 bytes long.
146
+		This file is writeonly.
147
+Users:		http://roccat.sourceforge.net
148
+
149
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/stored_lights
150
+Date:		October 2013
151
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
152
+Description:	When written, this file lets one set per-key lighting for different
153
+		layers.
154
+		This attribute is only valid for the pro variant.
155
+		The data has to be 1382 bytes long.
156
+		Before reading this file, control has to be written to select
157
+		which profile to read.
158
+Users:		http://roccat.sourceforge.net
159
+
160
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/custom_lights
161
+Date:		October 2013
162
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
163
+Description:	When written, this file lets one set the actual per-key lighting.
164
+		This attribute is only valid for the pro variant.
165
+		The data has to be 20 bytes long.
166
+		This file is writeonly.
167
+Users:		http://roccat.sourceforge.net
168
+
169
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light_macro
170
+Date:		October 2013
171
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
172
+Description:	When written, this file lets one set a light macro that is looped
173
+		whenever the device gets in dimness mode.
174
+		This attribute is only valid for the pro variant.
175
+		The data has to be 2002 bytes long.
176
+		Before reading this file, control has to be written to select
177
+		which profile to read.
178
+Users:		http://roccat.sourceforge.net

+ 77
- 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu View File

@@ -0,0 +1,77 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons
2
+Date:		Mai 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The mouse can store 5 profiles which can be switched by the
5
+		press of a button. A profile is split into general settings and
6
+		button settings. The buttons variable holds information about
7
+		button layout. When written, this file lets one write the
8
+		respective profile buttons to the mouse. The data has to be
9
+		47 bytes long.
10
+		The mouse will reject invalid data.
11
+		Which profile to write is determined by the profile number
12
+		contained in the data.
13
+		Before reading this file, control has to be written to select
14
+		which profile to read.
15
+Users:		http://roccat.sourceforge.net
16
+
17
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
18
+Date:		Mai 2012
19
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
20
+Description:	When written, this file lets one select which data from which
21
+		profile will be	read next. The data has to be 3 bytes long.
22
+		This file is writeonly.
23
+Users:		http://roccat.sourceforge.net
24
+
25
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/general
26
+Date:		Mai 2012
27
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
28
+Description:	The mouse can store 5 profiles which can be switched by the
29
+		press of a button. A profile is split into general settings and
30
+		button settings. A profile holds information like resolution,
31
+		sensitivity and light effects.
32
+		When written, this file lets one write the respective profile
33
+		settings back to the mouse. The data has to be 43 bytes long.
34
+		The mouse will reject invalid data.
35
+		Which profile to write is determined by the profile number
36
+		contained in the data.
37
+		This file is writeonly.
38
+Users:		http://roccat.sourceforge.net
39
+
40
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
41
+Date:		Mai 2012
42
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
43
+Description:	When read, this file returns general data like firmware version.
44
+		When written, the device can be reset.
45
+		The data is 8 bytes long.
46
+Users:		http://roccat.sourceforge.net
47
+
48
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
49
+Date:		Mai 2012
50
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
51
+Description:	When written, this file lets one store macros with max 500
52
+		keystrokes for a specific button for a specific profile.
53
+		Button and profile numbers are included in written data.
54
+		The data has to be 2083 bytes long.
55
+		Before reading this file, control has to be written to select
56
+		which profile and key to read.
57
+Users:		http://roccat.sourceforge.net
58
+
59
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
60
+Date:		Mai 2012
61
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
62
+Description:	The mouse can store 5 profiles which can be switched by the
63
+		press of a button. profile holds number of actual profile.
64
+		This value is persistent, so its value determines the profile
65
+		that's active when the mouse is powered on next time.
66
+		When written, the mouse activates the set profile immediately.
67
+		The data has to be 3 bytes long.
68
+		The mouse will reject invalid data.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/sensor
72
+Date:		July 2012
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	The mouse has a Avago ADNS-3090 sensor.
75
+		This file allows reading and writing of the mouse sensors registers.
76
+		The data has to be 4 bytes long.
77
+Users:		http://roccat.sourceforge.net

+ 8
- 0
Documentation/ABI/obsolete/sysfs-firmware-acpi View File

@@ -0,0 +1,8 @@
1
+What:		/sys/firmware/acpi/hotplug/force_remove
2
+Date:		Mar 2017
3
+Contact:	Rafael J. Wysocki <rafael.j.wysocki@intel.com>
4
+Description:
5
+		Since the force_remove is inherently broken and dangerous to
6
+		use for some hotplugable resources like memory (because ignoring
7
+		the offline failure might lead to memory corruption and crashes)
8
+		enabling this knob is not safe and thus unsupported.

+ 30
- 0
Documentation/ABI/obsolete/sysfs-gpio View File

@@ -0,0 +1,30 @@
1
+What:		/sys/class/gpio/
2
+Date:		July 2008
3
+KernelVersion:	2.6.27
4
+Contact:	Linus Walleij <linusw@kernel.org>
5
+Description:
6
+
7
+  As a Kconfig option, individual GPIO signals may be accessed from
8
+  userspace.  GPIOs are only made available to userspace by an explicit
9
+  "export" operation.  If a given GPIO is not claimed for use by
10
+  kernel code, it may be exported by userspace (and unexported later).
11
+  Kernel code may export it for complete or partial access.
12
+
13
+  GPIOs are identified as they are inside the kernel, using integers in
14
+  the range 0..INT_MAX.  See Documentation/gpio/gpio.txt for more information.
15
+
16
+    /sys/class/gpio
17
+	/export ... asks the kernel to export a GPIO to userspace
18
+	/unexport ... to return a GPIO to the kernel
19
+	/gpioN ... for each exported GPIO #N OR
20
+	/<LINE-NAME> ... for a properly named GPIO line
21
+	    /value ... always readable, writes fail for input GPIOs
22
+	    /direction ... r/w as: in, out (default low); write: high, low
23
+	    /edge ... r/w as: none, falling, rising, both
24
+	/gpiochipN ... for each gpiochip; #N is its first GPIO
25
+	    /base ... (r/o) same as N
26
+	    /label ... (r/o) descriptive, not necessarily unique
27
+	    /ngpio ... (r/o) number of GPIOs; numbered N to N + (ngpio - 1)
28
+
29
+  This ABI is deprecated and will be removed after 2020. It is
30
+  replaced with the GPIO character device.

+ 12
- 0
Documentation/ABI/removed/devfs View File

@@ -0,0 +1,12 @@
1
+What:		devfs
2
+Date:		July 2005 (scheduled), finally removed in kernel v2.6.18
3
+Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4
+Description:
5
+	devfs has been unmaintained for a number of years, has unfixable
6
+	races, contains a naming policy within the kernel that is
7
+	against the LSB, and can be replaced by using udev.
8
+	The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
9
+	along with the assorted devfs function calls throughout the
10
+	kernel tree.
11
+
12
+Users:

+ 14
- 0
Documentation/ABI/removed/dv1394 View File

@@ -0,0 +1,14 @@
1
+What:		dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/dv1394/* were character device files, one for each FireWire
6
+	controller and for NTSC and PAL respectively, from which DV data
7
+	could be received by read() or transmitted by write().  A few
8
+	ioctl()s allowed limited control.
9
+	This special-purpose interface has been superseded by libraw1394 +
10
+	libiec61883 which are functionally equivalent, support HDV, and
11
+	transparently work on top of the newer firewire kernel drivers.
12
+
13
+Users:
14
+	ffmpeg/libavformat (if configured for DV1394)

+ 9
- 0
Documentation/ABI/removed/ip_queue View File

@@ -0,0 +1,9 @@
1
+What:		ip_queue
2
+Date:		finally removed in kernel v3.5.0
3
+Contact:	Pablo Neira Ayuso <pablo@netfilter.org>
4
+Description:
5
+	ip_queue has been replaced by nfnetlink_queue which provides
6
+	more advanced queueing mechanism to user-space. The ip_queue
7
+	module was already announced to become obsolete years ago.
8
+
9
+Users:

+ 8
- 0
Documentation/ABI/removed/net_dma View File

@@ -0,0 +1,8 @@
1
+What:		tcp_dma_copybreak sysctl
2
+Date:		Removed in kernel v3.13
3
+Contact:	Dan Williams <dan.j.williams@intel.com>
4
+Description:
5
+	Formerly the lower limit, in bytes, of the size of socket reads
6
+	that will be offloaded to a DMA copy engine.  Removed due to
7
+	coherency issues of the cpu potentially touching the buffers
8
+	while dma is in flight.

+ 10
- 0
Documentation/ABI/removed/o2cb View File

@@ -0,0 +1,10 @@
1
+What:		/sys/o2cb symlink
2
+Date:		May 2011
3
+KernelVersion:	3.0
4
+Contact:	ocfs2-devel@oss.oracle.com
5
+Description:	This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is
6
+		removed when new versions of ocfs2-tools which know to look
7
+		in /sys/fs/o2cb are sufficiently prevalent. Don't code new
8
+		software to look here, it should try /sys/fs/o2cb instead.
9
+Users:		ocfs2-tools. It's sufficient to mail proposed changes to
10
+		ocfs2-devel@oss.oracle.com.

+ 15
- 0
Documentation/ABI/removed/raw1394 View File

@@ -0,0 +1,15 @@
1
+What:		raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/raw1394 was a character device file that allowed low-level
6
+	access to FireWire buses.  Its major drawbacks were its inability
7
+	to implement sensible device security policies, and its low level
8
+	of abstraction that required userspace clients to duplicate much
9
+	of the kernel's ieee1394 core functionality.
10
+	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
11
+	firewire-core.
12
+
13
+Users:
14
+	libraw1394 (works with firewire-cdev too, transparent to library ABI
15
+	users)

+ 13
- 0
Documentation/ABI/removed/sysfs-class-rfkill View File

@@ -0,0 +1,13 @@
1
+rfkill - radio frequency (RF) connector kill switch support
2
+
3
+For details to this subsystem look at Documentation/rfkill.txt.
4
+
5
+What:		/sys/class/rfkill/rfkill[0-9]+/claim
6
+Date:		09-Jul-2007
7
+KernelVersion	v2.6.22
8
+Contact:	linux-wireless@vger.kernel.org
9
+Description:	This file was deprecated because there no longer was a way to
10
+		claim just control over a single rfkill instance.
11
+		This file was scheduled to be removed in 2012, and was removed
12
+		in 2016.
13
+Values: 	0: Kernel handles events

+ 16
- 0
Documentation/ABI/removed/video1394 View File

@@ -0,0 +1,16 @@
1
+What:		video1394 (a.k.a. "OHCI-1394 Video support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/video1394/* were character device files, one for each FireWire
6
+	controller, which were used for isochronous I/O.  It was added as an
7
+	alternative to raw1394's isochronous I/O functionality which had
8
+	performance issues in its first generation.  Any video1394 user had
9
+	to use raw1394 + libraw1394 too because video1394 did not provide
10
+	asynchronous I/O for device discovery and configuration.
11
+	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
12
+	firewire-core.
13
+
14
+Users:
15
+	libdc1394 (works with firewire-cdev too, transparent to library ABI
16
+	users)

+ 104
- 0
Documentation/ABI/stable/firewire-cdev View File

@@ -0,0 +1,104 @@
1
+What:		/dev/fw[0-9]+
2
+Date:		May 2007
3
+KernelVersion:	2.6.22
4
+Contact:	linux1394-devel@lists.sourceforge.net
5
+Description:
6
+		The character device files /dev/fw* are the interface between
7
+		firewire-core and IEEE 1394 device drivers implemented in
8
+		userspace.  The ioctl(2)- and read(2)-based ABI is defined and
9
+		documented in <linux/firewire-cdev.h>.
10
+
11
+		This ABI offers most of the features which firewire-core also
12
+		exposes to kernelspace IEEE 1394 drivers.
13
+
14
+		Each /dev/fw* is associated with one IEEE 1394 node, which can
15
+		be remote or local nodes.  Operations on a /dev/fw* file have
16
+		different scope:
17
+		  - The 1394 node which is associated with the file:
18
+			  - Asynchronous request transmission
19
+			  - Get the Configuration ROM
20
+			  - Query node ID
21
+			  - Query maximum speed of the path between this node
22
+			    and local node
23
+		  - The 1394 bus (i.e. "card") to which the node is attached to:
24
+			  - Isochronous stream transmission and reception
25
+			  - Asynchronous stream transmission and reception
26
+			  - Asynchronous broadcast request transmission
27
+			  - PHY packet transmission and reception
28
+			  - Allocate, reallocate, deallocate isochronous
29
+			    resources (channels, bandwidth) at the bus's IRM
30
+			  - Query node IDs of local node, root node, IRM, bus
31
+			    manager
32
+			  - Query cycle time
33
+			  - Bus reset initiation, bus reset event reception
34
+		  - All 1394 buses:
35
+			  - Allocation of IEEE 1212 address ranges on the local
36
+			    link layers, reception of inbound requests to such
37
+			    an address range, asynchronous response transmission
38
+			    to inbound requests
39
+			  - Addition of descriptors or directories to the local
40
+			    nodes' Configuration ROM
41
+
42
+		Due to the different scope of operations and in order to let
43
+		userland implement different access permission models, some
44
+		operations are restricted to /dev/fw* files that are associated
45
+		with a local node:
46
+			  - Addition of descriptors or directories to the local
47
+			    nodes' Configuration ROM
48
+			  - PHY packet transmission and reception
49
+
50
+		A /dev/fw* file remains associated with one particular node
51
+		during its entire life time.  Bus topology changes, and hence
52
+		node ID changes, are tracked by firewire-core.  ABI users do not
53
+		need to be aware of topology.
54
+
55
+		The following file operations are supported:
56
+
57
+		open(2)
58
+		Currently the only useful flags are O_RDWR.
59
+
60
+		ioctl(2)
61
+		Initiate various actions.  Some take immediate effect, others
62
+		are performed asynchronously while or after the ioctl returns.
63
+		See the inline documentation in <linux/firewire-cdev.h> for
64
+		descriptions of all ioctls.
65
+
66
+		poll(2), select(2), epoll_wait(2) etc.
67
+		Watch for events to become available to be read.
68
+
69
+		read(2)
70
+		Receive various events.  There are solicited events like
71
+		outbound asynchronous transaction completion or isochronous
72
+		buffer completion, and unsolicited events such as bus resets,
73
+		request reception, or PHY packet reception.  Always use a read
74
+		buffer which is large enough to receive the largest event that
75
+		could ever arrive.  See <linux/firewire-cdev.h> for descriptions
76
+		of all event types and for which ioctls affect reception of
77
+		events.
78
+
79
+		mmap(2)
80
+		Allocate a DMA buffer for isochronous reception or transmission
81
+		and map it into the process address space.  The arguments should
82
+		be used as follows:  addr = NULL, length = the desired buffer
83
+		size, i.e. number of packets times size of largest packet,
84
+		prot = at least PROT_READ for reception and at least PROT_WRITE
85
+		for transmission, flags = MAP_SHARED, fd = the handle to the
86
+		/dev/fw*, offset = 0.
87
+
88
+		Isochronous reception works in packet-per-buffer fashion except
89
+		for multichannel reception which works in buffer-fill mode.
90
+
91
+		munmap(2)
92
+		Unmap the isochronous I/O buffer from the process address space.
93
+
94
+		close(2)
95
+		Besides stopping and freeing I/O contexts that were associated
96
+		with the file descriptor, back out any changes to the local
97
+		nodes' Configuration ROM.  Deallocate isochronous channels and
98
+		bandwidth at the IRM that were marked for kernel-assisted
99
+		re- and deallocation.
100
+
101
+Users:		libraw1394
102
+		libdc1394
103
+		libhinawa
104
+		tools like linux-firewire-utils, fwhack, ...

+ 10
- 0
Documentation/ABI/stable/o2cb View File

@@ -0,0 +1,10 @@
1
+What:		/sys/fs/o2cb/ (was /sys/o2cb)
2
+Date:		Dec 2005
3
+KernelVersion:	2.6.16
4
+Contact:	ocfs2-devel@oss.oracle.com
5
+Description:	Ocfs2-tools looks at 'interface-revision' for versioning
6
+		information. Each logmask/ file controls a set of debug prints
7
+		and can be written into with the strings "allow", "deny", or
8
+		"off". Reading the file returns the current state.
9
+Users:		ocfs2-tools. It's sufficient to mail proposed changes to
10
+		ocfs2-devel@oss.oracle.com.

+ 10
- 0
Documentation/ABI/stable/syscalls View File

@@ -0,0 +1,10 @@
1
+What:		The kernel syscall interface
2
+Description:
3
+	This interface matches much of the POSIX interface and is based
4
+	on it and other Unix based interfaces.  It will only be added to
5
+	over time, and not have things removed from it.
6
+
7
+	Note that this interface is different for every architecture
8
+	that Linux supports.  Please see the architecture-specific
9
+	documentation for details on the syscall numbers that are to be
10
+	mapped to each syscall.

+ 22
- 0
Documentation/ABI/stable/sysfs-acpi-pmprofile View File

@@ -0,0 +1,22 @@
1
+What: 		/sys/firmware/acpi/pm_profile
2
+Date:		03-Nov-2011
3
+KernelVersion:	v3.2
4
+Contact:	linux-acpi@vger.kernel.org
5
+Description: 	The ACPI pm_profile sysfs interface exports the platform
6
+		power management (and performance) requirement expectations
7
+		as provided by BIOS. The integer value is directly passed as
8
+		retrieved from the FADT ACPI table.
9
+Values:         For possible values see ACPI specification:
10
+		5.2.9 Fixed ACPI Description Table (FADT)
11
+		Field: Preferred_PM_Profile
12
+
13
+		Currently these values are defined by spec:
14
+		0 Unspecified
15
+		1 Desktop
16
+		2 Mobile
17
+		3 Workstation
18
+		4 Enterprise Server
19
+		5 SOHO Server
20
+		6 Appliance PC
21
+		7 Performance Server
22
+		>7 Reserved

+ 133
- 0
Documentation/ABI/stable/sysfs-bus-firewire View File

@@ -0,0 +1,133 @@
1
+What:		/sys/bus/firewire/devices/fw[0-9]+/
2
+Date:		May 2007
3
+KernelVersion:	2.6.22
4
+Contact:	linux1394-devel@lists.sourceforge.net
5
+Description:
6
+		IEEE 1394 node device attributes.
7
+		Read-only.  Mutable during the node device's lifetime.
8
+		See IEEE 1212 for semantic definitions.
9
+
10
+		config_rom
11
+			Contents of the Configuration ROM register.
12
+			Binary attribute; an array of host-endian u32.
13
+
14
+		guid
15
+			The node's EUI-64 in the bus information block of
16
+			Configuration ROM.
17
+			Hexadecimal string representation of an u64.
18
+
19
+
20
+What:		/sys/bus/firewire/devices/fw[0-9]+/units
21
+Date:		June 2009
22
+KernelVersion:	2.6.31
23
+Contact:	linux1394-devel@lists.sourceforge.net
24
+Description:
25
+		IEEE 1394 node device attribute.
26
+		Read-only.  Mutable during the node device's lifetime.
27
+		See IEEE 1212 for semantic definitions.
28
+
29
+		units
30
+			Summary of all units present in an IEEE 1394 node.
31
+			Contains space-separated tuples of specifier_id and
32
+			version of each unit present in the node.  Specifier_id
33
+			and version are hexadecimal string representations of
34
+			u24 of the respective unit directory entries.
35
+			Specifier_id and version within each tuple are separated
36
+			by a colon.
37
+
38
+Users:		udev rules to set ownership and access permissions or ACLs of
39
+		/dev/fw[0-9]+ character device files
40
+
41
+
42
+What:		/sys/bus/firewire/devices/fw[0-9]+/is_local
43
+Date:		July 2012
44
+KernelVersion:	3.6
45
+Contact:	linux1394-devel@lists.sourceforge.net
46
+Description:
47
+		IEEE 1394 node device attribute.
48
+		Read-only and immutable.
49
+Values:		1: The sysfs entry represents a local node (a controller card).
50
+		0: The sysfs entry represents a remote node.
51
+
52
+
53
+What:		/sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/
54
+Date:		May 2007
55
+KernelVersion:	2.6.22
56
+Contact:	linux1394-devel@lists.sourceforge.net
57
+Description:
58
+		IEEE 1394 unit device attributes.
59
+		Read-only.  Immutable during the unit device's lifetime.
60
+		See IEEE 1212 for semantic definitions.
61
+
62
+		modalias
63
+			Same as MODALIAS in the uevent at device creation.
64
+
65
+		rom_index
66
+			Offset of the unit directory within the parent device's
67
+			(node device's) Configuration ROM, in quadlets.
68
+			Decimal string representation.
69
+
70
+
71
+What:		/sys/bus/firewire/devices/*/
72
+Date:		May 2007
73
+KernelVersion:	2.6.22
74
+Contact:	linux1394-devel@lists.sourceforge.net
75
+Description:
76
+		Attributes common to IEEE 1394 node devices and unit devices.
77
+		Read-only.  Mutable during the node device's lifetime.
78
+		Immutable during the unit device's lifetime.
79
+		See IEEE 1212 for semantic definitions.
80
+
81
+		These attributes are only created if the root directory of an
82
+		IEEE 1394 node or the unit directory of an IEEE 1394 unit
83
+		actually contains according entries.
84
+
85
+		hardware_version
86
+			Hexadecimal string representation of an u24.
87
+
88
+		hardware_version_name
89
+			Contents of a respective textual descriptor leaf.
90
+
91
+		model
92
+			Hexadecimal string representation of an u24.
93
+
94
+		model_name
95
+			Contents of a respective textual descriptor leaf.
96
+
97
+		specifier_id
98
+			Hexadecimal string representation of an u24.
99
+			Mandatory in unit directories according to IEEE 1212.
100
+
101
+		vendor
102
+			Hexadecimal string representation of an u24.
103
+			Mandatory in the root directory according to IEEE 1212.
104
+
105
+		vendor_name
106
+			Contents of a respective textual descriptor leaf.
107
+
108
+		version
109
+			Hexadecimal string representation of an u24.
110
+			Mandatory in unit directories according to IEEE 1212.
111
+
112
+
113
+What:		/sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
114
+		formerly
115
+		/sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
116
+Date:		Feb 2004
117
+KernelVersion:	2.6.4
118
+Contact:	linux1394-devel@lists.sourceforge.net
119
+Description:
120
+		SCSI target port identifier and logical unit identifier of a
121
+		logical unit of an SBP-2 target.  The identifiers are specified
122
+		in SAM-2...SAM-4 annex A.  They are persistent and world-wide
123
+		unique properties the SBP-2 attached target.
124
+
125
+		Read-only attribute, immutable during the target's lifetime.
126
+		Format, as exposed by firewire-sbp2 since 2.6.22, May 2007:
127
+		Colon-separated hexadecimal string representations of
128
+			u64 EUI-64 : u24 directory_ID : u16 LUN
129
+		without 0x prefixes, without whitespace.  The former sbp2 driver
130
+		(removed in 2.6.37 after being superseded by firewire-sbp2) used
131
+		a somewhat shorter format which was not as close to SAM.
132
+
133
+Users:		udev rules to create /dev/disk/by-id/ symlinks

+ 19
- 0
Documentation/ABI/stable/sysfs-bus-nvmem View File

@@ -0,0 +1,19 @@
1
+What:		/sys/bus/nvmem/devices/.../nvmem
2
+Date:		July 2015
3
+KernelVersion:  4.2
4
+Contact:	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
5
+Description:
6
+		This file allows user to read/write the raw NVMEM contents.
7
+		Permissions for write to this file depends on the nvmem
8
+		provider configuration.
9
+
10
+		ex:
11
+		hexdump /sys/bus/nvmem/devices/qfprom0/nvmem
12
+
13
+		0000000 0000 0000 0000 0000 0000 0000 0000 0000
14
+		*
15
+		00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00
16
+		0000000 0000 0000 0000 0000 0000 0000 0000 0000
17
+		...
18
+		*
19
+		0001000

+ 140
- 0
Documentation/ABI/stable/sysfs-bus-usb View File

@@ -0,0 +1,140 @@
1
+What:		/sys/bus/usb/devices/.../power/persist
2
+Date:		May 2007
3
+KernelVersion:	2.6.23
4
+Contact:	Alan Stern <stern@rowland.harvard.edu>
5
+Description:
6
+		USB device directories can contain a file named power/persist.
7
+		The file holds a boolean value (0 or 1) indicating whether or
8
+		not the "USB-Persist" facility is enabled for the device.  For
9
+		hubs this facility is always enabled and their device
10
+		directories will not contain this file.
11
+
12
+		For more information, see Documentation/driver-api/usb/persist.rst.
13
+
14
+What:		/sys/bus/usb/devices/.../power/autosuspend
15
+Date:		March 2007
16
+KernelVersion:	2.6.21
17
+Contact:	Alan Stern <stern@rowland.harvard.edu>
18
+Description:
19
+		Each USB device directory will contain a file named
20
+		power/autosuspend.  This file holds the time (in seconds)
21
+		the device must be idle before it will be autosuspended.
22
+		0 means the device will be autosuspended as soon as
23
+		possible.  Negative values will prevent the device from
24
+		being autosuspended at all, and writing a negative value
25
+		will resume the device if it is already suspended.
26
+
27
+		The autosuspend delay for newly-created devices is set to
28
+		the value of the usbcore.autosuspend module parameter.
29
+
30
+What:		/sys/bus/usb/device/.../power/connected_duration
31
+Date:		January 2008
32
+KernelVersion:	2.6.25
33
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
34
+Description:
35
+		If CONFIG_PM is enabled, then this file is present.  When read,
36
+		it returns the total time (in msec) that the USB device has been
37
+		connected to the machine.  This file is read-only.
38
+Users:
39
+		PowerTOP <powertop@lists.01.org>
40
+		https://01.org/powertop/
41
+
42
+What:		/sys/bus/usb/device/.../power/active_duration
43
+Date:		January 2008
44
+KernelVersion:	2.6.25
45
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
46
+Description:
47
+		If CONFIG_PM is enabled, then this file is present.  When read,
48
+		it returns the total time (in msec) that the USB device has been
49
+		active, i.e. not in a suspended state.  This file is read-only.
50
+
51
+		Tools can use this file and the connected_duration file to
52
+		compute the percentage of time that a device has been active.
53
+		For example,
54
+		echo $((100 * `cat active_duration` / `cat connected_duration`))
55
+		will give an integer percentage.  Note that this does not
56
+		account for counter wrap.
57
+Users:
58
+		PowerTOP <powertop@lists.01.org>
59
+		https://01.org/powertop/
60
+
61
+What:		/sys/bus/usb/devices/<busnum>-<port[.port]>...:<config num>-<interface num>/supports_autosuspend
62
+Date:		January 2008
63
+KernelVersion:	2.6.27
64
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
65
+Description:
66
+		When read, this file returns 1 if the interface driver
67
+		for this interface supports autosuspend.  It also
68
+		returns 1 if no driver has claimed this interface, as an
69
+		unclaimed interface will not stop the device from being
70
+		autosuspended if all other interface drivers are idle.
71
+		The file returns 0 if autosuspend support has not been
72
+		added to the driver.
73
+Users:
74
+		USB PM tool
75
+		git://git.moblin.org/users/sarah/usb-pm-tool/
76
+
77
+What:		/sys/bus/usb/device/.../avoid_reset_quirk
78
+Date:		December 2009
79
+Contact:	Oliver Neukum <oliver@neukum.org>
80
+Description:
81
+		Writing 1 to this file tells the kernel that this
82
+		device will morph into another mode when it is reset.
83
+		Drivers will not use reset for error handling for
84
+		such devices.
85
+Users:
86
+		usb_modeswitch
87
+
88
+What:		/sys/bus/usb/devices/.../devnum
89
+KernelVersion:	since at least 2.6.18
90
+Description:
91
+		Device address on the USB bus.
92
+Users:
93
+		libusb
94
+
95
+What:		/sys/bus/usb/devices/.../bConfigurationValue
96
+KernelVersion:	since at least 2.6.18
97
+Description:
98
+		bConfigurationValue of the *active* configuration for the
99
+		device. Writing 0 or -1 to bConfigurationValue will reset the
100
+		active configuration (unconfigure the device). Writing
101
+		another value will change the active configuration.
102
+
103
+		Note that some devices, in violation of the USB spec, have a
104
+		configuration with a value equal to 0. Writing 0 to
105
+		bConfigurationValue for these devices will install that
106
+		configuration, rather then unconfigure the device.
107
+
108
+		Writing -1 will always unconfigure the device.
109
+Users:
110
+		libusb
111
+
112
+What:		/sys/bus/usb/devices/.../busnum
113
+KernelVersion:	2.6.22
114
+Description:
115
+		Bus-number of the USB-bus the device is connected to.
116
+Users:
117
+		libusb
118
+
119
+What:		/sys/bus/usb/devices/.../descriptors
120
+KernelVersion:	2.6.26
121
+Description:
122
+		Binary file containing cached descriptors of the device. The
123
+		binary data consists of the device descriptor followed by the
124
+		descriptors for each configuration of the device.
125
+		Note that the wTotalLength of the config descriptors can not
126
+		be trusted, as the device may have a smaller config descriptor
127
+		than it advertises. The bLength field of each (sub) descriptor
128
+		can be trusted, and can be used to seek forward one (sub)
129
+		descriptor at a time until the next config descriptor is found.
130
+		All descriptors read from this file are in bus-endian format
131
+Users:
132
+		libusb
133
+
134
+What:		/sys/bus/usb/devices/.../speed
135
+KernelVersion:	since at least 2.6.18
136
+Description:
137
+		Speed the device is connected with to the usb-host in
138
+		Mbit / second. IE one of 1.5 / 12 / 480 / 5000.
139
+Users:
140
+		libusb

+ 141
- 0
Documentation/ABI/stable/sysfs-bus-vmbus View File

@@ -0,0 +1,141 @@
1
+What:		/sys/bus/vmbus/devices/vmbus_*/id
2
+Date:		Jul 2009
3
+KernelVersion:	2.6.31
4
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
5
+Description:	The VMBus child_relid of the device's primary channel
6
+Users:		tools/hv/lsvmbus
7
+
8
+What:		/sys/bus/vmbus/devices/vmbus_*/class_id
9
+Date:		Jul 2009
10
+KernelVersion:	2.6.31
11
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
12
+Description:	The VMBus interface type GUID of the device
13
+Users:		tools/hv/lsvmbus
14
+
15
+What:		/sys/bus/vmbus/devices/vmbus_*/device_id
16
+Date:		Jul 2009
17
+KernelVersion:	2.6.31
18
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
19
+Description:	The VMBus interface instance GUID of the device
20
+Users:		tools/hv/lsvmbus
21
+
22
+What:		/sys/bus/vmbus/devices/vmbus_*/channel_vp_mapping
23
+Date:		Jul 2015
24
+KernelVersion:	4.2.0
25
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
26
+Description:	The mapping of which primary/sub channels are bound to which
27
+		Virtual Processors.
28
+		Format: <channel's child_relid:the bound cpu's number>
29
+Users:		tools/hv/lsvmbus
30
+
31
+What:		/sys/bus/vmbus/devices/vmbus_*/device
32
+Date:		Dec. 2015
33
+KernelVersion:	4.5
34
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
35
+Description:	The 16 bit device ID of the device
36
+Users:		tools/hv/lsvmbus and user level RDMA libraries
37
+
38
+What:		/sys/bus/vmbus/devices/vmbus_*/vendor
39
+Date:		Dec. 2015
40
+KernelVersion:	4.5
41
+Contact:	K. Y. Srinivasan <kys@microsoft.com>
42
+Description:	The 16 bit vendor ID of the device
43
+Users:		tools/hv/lsvmbus and user level RDMA libraries
44
+
45
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN
46
+Date:		September. 2017
47
+KernelVersion:	4.14
48
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
49
+Description:	Directory for per-channel information
50
+		NN is the VMBUS relid associtated with the channel.
51
+
52
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/cpu
53
+Date:		September. 2017
54
+KernelVersion:	4.14
55
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
56
+Description:	VCPU (sub)channel is affinitized to
57
+Users:		tools/hv/lsvmbus and other debugging tools
58
+
59
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/cpu
60
+Date:		September. 2017
61
+KernelVersion:	4.14
62
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
63
+Description:	VCPU (sub)channel is affinitized to
64
+Users:		tools/hv/lsvmbus and other debugging tools
65
+
66
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/in_mask
67
+Date:		September. 2017
68
+KernelVersion:	4.14
69
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
70
+Description:	Host to guest channel interrupt mask
71
+Users:		Debugging tools
72
+
73
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/latency
74
+Date:		September. 2017
75
+KernelVersion:	4.14
76
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
77
+Description:	Channel signaling latency
78
+Users:		Debugging tools
79
+
80
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/out_mask
81
+Date:		September. 2017
82
+KernelVersion:	4.14
83
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
84
+Description:	Guest to host channel interrupt mask
85
+Users:		Debugging tools
86
+
87
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/pending
88
+Date:		September. 2017
89
+KernelVersion:	4.14
90
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
91
+Description:	Channel interrupt pending state
92
+Users:		Debugging tools
93
+
94
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/read_avail
95
+Date:		September. 2017
96
+KernelVersion:	4.14
97
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
98
+Description:	Bytes available to read
99
+Users:		Debugging tools
100
+
101
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/write_avail
102
+Date:		September. 2017
103
+KernelVersion:	4.14
104
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
105
+Description:	Bytes available to write
106
+Users:		Debugging tools
107
+
108
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/events
109
+Date:		September. 2017
110
+KernelVersion:	4.14
111
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
112
+Description:	Number of times we have signaled the host
113
+Users:		Debugging tools
114
+
115
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/interrupts
116
+Date:		September. 2017
117
+KernelVersion:	4.14
118
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
119
+Description:	Number of times we have taken an interrupt (incoming)
120
+Users:		Debugging tools
121
+
122
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/subchannel_id
123
+Date:		January. 2018
124
+KernelVersion:	4.16
125
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
126
+Description:	Subchannel ID associated with VMBUS channel
127
+Users:		Debugging tools and userspace drivers
128
+
129
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/monitor_id
130
+Date:		January. 2018
131
+KernelVersion:	4.16
132
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
133
+Description:	Monitor bit associated with channel
134
+Users:		Debugging tools and userspace drivers
135
+
136
+What:		/sys/bus/vmbus/devices/vmbus_*/channels/NN/ring
137
+Date:		January. 2018
138
+KernelVersion:	4.16
139
+Contact:	Stephen Hemminger <sthemmin@microsoft.com>
140
+Description:	Binary file created by uio_hv_generic for ring buffer
141
+Users:		Userspace drivers

+ 11
- 0
Documentation/ABI/stable/sysfs-bus-w1 View File

@@ -0,0 +1,11 @@
1
+What:		/sys/bus/w1/devices/.../w1_master_timeout_us
2
+Date:		April 2015
3
+Contact:	Dmitry Khromov <dk@icelogic.net>
4
+Description:	Bus scanning interval, microseconds component.
5
+		Some of 1-Wire devices commonly associated with physical access
6
+		control systems are attached/generate presence for as short as
7
+		100 ms - hence the tens-to-hundreds milliseconds scan intervals
8
+		are required.
9
+		see Documentation/w1/w1.generic for detailed information.
10
+Users:		any user space application which wants to know bus scanning
11
+		interval

+ 75
- 0
Documentation/ABI/stable/sysfs-bus-xen-backend View File

@@ -0,0 +1,75 @@
1
+What:		/sys/bus/xen-backend/devices/*/devtype
2
+Date:		Feb 2009
3
+KernelVersion:	2.6.38
4
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
5
+Description:
6
+                The type of the device.  e.g., one of: 'vbd' (block),
7
+                'vif' (network), or 'vfb' (framebuffer).
8
+
9
+What:		/sys/bus/xen-backend/devices/*/nodename
10
+Date:		Feb 2009
11
+KernelVersion:	2.6.38
12
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
13
+Description:
14
+                XenStore node (under /local/domain/NNN/) for this
15
+                backend device.
16
+
17
+What:		/sys/bus/xen-backend/devices/vbd-*/physical_device
18
+Date:		April 2011
19
+KernelVersion:	3.0
20
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
21
+Description:
22
+                The major:minor number (in hexidecimal) of the
23
+                physical device providing the storage for this backend
24
+                block device.
25
+
26
+What:		/sys/bus/xen-backend/devices/vbd-*/mode
27
+Date:		April 2011
28
+KernelVersion:	3.0
29
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
30
+Description:
31
+                Whether the block device is read-only ('r') or
32
+                read-write ('w').
33
+
34
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/f_req
35
+Date:		April 2011
36
+KernelVersion:	3.0
37
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
38
+Description:
39
+                Number of flush requests from the frontend.
40
+
41
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/oo_req
42
+Date:		April 2011
43
+KernelVersion:	3.0
44
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
45
+Description:
46
+                Number of requests delayed because the backend was too
47
+                busy processing previous requests.
48
+
49
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/rd_req
50
+Date:		April 2011
51
+KernelVersion:	3.0
52
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
53
+Description:
54
+                Number of read requests from the frontend.
55
+
56
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/rd_sect
57
+Date:		April 2011
58
+KernelVersion:	3.0
59
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
60
+Description:
61
+                Number of sectors read by the frontend.
62
+
63
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/wr_req
64
+Date:		April 2011
65
+KernelVersion:	3.0
66
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
67
+Description:
68
+                Number of write requests from the frontend.
69
+
70
+What:		/sys/bus/xen-backend/devices/vbd-*/statistics/wr_sect
71
+Date:		April 2011
72
+KernelVersion:	3.0
73
+Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
74
+Description:
75
+                Number of sectors written by the frontend.

+ 56
- 0
Documentation/ABI/stable/sysfs-class-backlight View File

@@ -0,0 +1,56 @@
1
+What:		/sys/class/backlight/<backlight>/bl_power
2
+Date:		April 2005
3
+KernelVersion:	2.6.12
4
+Contact:	Richard Purdie <rpurdie@rpsys.net>
5
+Description:
6
+		Control BACKLIGHT power, values are FB_BLANK_* from fb.h
7
+		 - FB_BLANK_UNBLANK (0)   : power on.
8
+		 - FB_BLANK_POWERDOWN (4) : power off
9
+Users:		HAL
10
+
11
+What:		/sys/class/backlight/<backlight>/brightness
12
+Date:		April 2005
13
+KernelVersion:	2.6.12
14
+Contact:	Richard Purdie <rpurdie@rpsys.net>
15
+Description:
16
+		Control the brightness for this <backlight>. Values
17
+		are between 0 and max_brightness. This file will also
18
+		show the brightness level stored in the driver, which
19
+		may not be the actual brightness (see actual_brightness).
20
+Users:		HAL
21
+
22
+What:		/sys/class/backlight/<backlight>/actual_brightness
23
+Date:		March 2006
24
+KernelVersion:	2.6.17
25
+Contact:	Richard Purdie <rpurdie@rpsys.net>
26
+Description:
27
+		Show the actual brightness by querying the hardware.
28
+Users:		HAL
29
+
30
+What:		/sys/class/backlight/<backlight>/max_brightness
31
+Date:		April 2005