Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Merge branch 'master' into enhance-xconfig-search

  • Loading branch information...
commit f2a21a8687ebc7256415257bea7c4cf33b8af3cc 2 parents ccc33a5 + d987569
Shlomi Fish authored

Showing 8,205 changed files with 10,189 additions and 1,667 deletions. Show diff stats Hide diff stats

  1. +5 0 Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
  2. +11 0 Documentation/ABI/stable/sysfs-bus-firewire
  3. +15 0 Documentation/ABI/stable/sysfs-driver-w1_ds28e04
  4. +1 1  Documentation/ABI/stable/vdso
  5. +20 9 Documentation/ABI/testing/dev-kmsg
  6. +0 21 Documentation/ABI/testing/sysfs-block-rssd
  7. +1 1  Documentation/ABI/testing/sysfs-block-zram
  8. +28 26 Documentation/ABI/testing/sysfs-bus-iio
  9. +37 0 Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
  10. +21 0 Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
  11. +61 0 Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
  12. +8 2 Documentation/ABI/testing/sysfs-bus-rbd
  13. +12 0 Documentation/ABI/testing/sysfs-bus-usb
  14. +1 1  Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
  15. +1 1  Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
  16. +9 8 Documentation/ABI/testing/sysfs-class-mtd
  17. +140 0 Documentation/ABI/testing/sysfs-devices-edac
  18. +44 0 Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb
  19. +20 0 Documentation/ABI/testing/sysfs-devices-system-xen_cpu
  20. +38 0 Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
  21. +77 0 Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
  22. +14 0 Documentation/ABI/testing/sysfs-kernel-iommu_groups
  23. +7 0 Documentation/ABI/testing/sysfs-platform-asus-wmi
  24. +13 0 Documentation/ABI/testing/sysfs-power
  25. +42 0 Documentation/DMA-attributes.txt
  26. +0 1  Documentation/DocBook/80211.tmpl
  27. +2 2 Documentation/DocBook/filesystems.tmpl
  28. +1 1  Documentation/DocBook/media/v4l/biblio.xml
  29. +13 4 Documentation/DocBook/media/v4l/common.xml
  30. +38 4 Documentation/DocBook/media/v4l/compat.xml
  31. +6 1 Documentation/DocBook/media/v4l/controls.xml
  32. +18 18 Documentation/DocBook/media/v4l/dev-subdev.xml
  33. +5 14 Documentation/DocBook/media/v4l/io.xml
  34. +2 2 Documentation/DocBook/media/v4l/pixfmt.xml
  35. +17 17 Documentation/DocBook/media/v4l/selection-api.xml
  36. +164 0 Documentation/DocBook/media/v4l/selections-common.xml
  37. +12 1 Documentation/DocBook/media/v4l/v4l2.xml
  38. +10 5 Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
  39. +1 1  Documentation/DocBook/media/v4l/vidioc-dqevent.xml
  40. +4 10 Documentation/DocBook/media/v4l/vidioc-dv-timings-cap.xml
  41. +179 0 Documentation/DocBook/media/v4l/vidioc-enum-freq-bands.xml
  42. +0 7 Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml
  43. +10 3 Documentation/DocBook/media/v4l/vidioc-g-frequency.xml
  44. +10 76 Documentation/DocBook/media/v4l/vidioc-g-selection.xml
  45. +32 6 Documentation/DocBook/media/v4l/vidioc-g-tuner.xml
  46. +3 6 Documentation/DocBook/media/v4l/vidioc-qbuf.xml
  47. +13 0 Documentation/DocBook/media/v4l/vidioc-querycap.xml
  48. +57 11 Documentation/DocBook/media/v4l/vidioc-s-hw-freq-seek.xml
  49. +8 71 Documentation/DocBook/media/v4l/vidioc-subdev-g-selection.xml
  50. +5 0 Documentation/IRQ-domain.txt
  51. +1 1  Documentation/ManagementStyle
  52. +20 19 Documentation/RCU/checklist.txt
  53. +4 11 Documentation/RCU/rcubarrier.txt
  54. +9 0 Documentation/RCU/torture.txt
  55. +3 3 Documentation/RCU/whatisRCU.txt
  56. +1 1  Documentation/arm/Samsung-S3C24XX/H1940.txt
  57. +1 1  Documentation/arm/Samsung-S3C24XX/SMDK2440.txt
  58. +7 0 Documentation/block/queue-sysfs.txt
  59. +7 20 Documentation/cgroups/cgroups.txt
  60. +45 0 Documentation/cgroups/hugetlb.txt
  61. +7 5 Documentation/cgroups/memory.txt
  62. +6 7 Documentation/connector/cn_test.c
  63. +26 0 Documentation/device-mapper/dm-raid.txt
  64. +3 4 Documentation/device-mapper/striped.txt
  65. +23 1 Documentation/device-mapper/thin-provisioning.txt
  66. +46 85 Documentation/device-mapper/verity.txt
  67. +2 0  Documentation/devices.txt
  68. +23 0 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt
  69. +11 0 Documentation/devicetree/bindings/arm/armada-370-xp-timer.txt
  70. +24 0 Documentation/devicetree/bindings/arm/armada-370-xp.txt
  71. +6 3 Documentation/devicetree/bindings/arm/atmel-aic.txt
  72. +15 0 Documentation/devicetree/bindings/arm/calxeda/l2ecc.txt
  73. +14 0 Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt
  74. +27 0 Documentation/devicetree/bindings/arm/davinci/cp-intc.txt
  75. +20 0 Documentation/devicetree/bindings/arm/mrvl/intc.txt
  76. +17 0 Documentation/devicetree/bindings/arm/mvebu-system-controller.txt
  77. +6 0 Documentation/devicetree/bindings/arm/olimex.txt
  78. +6 0 Documentation/devicetree/bindings/arm/omap/omap.txt
  79. +6 0 Documentation/devicetree/bindings/arm/primecell.txt
  80. +1 1  Documentation/devicetree/bindings/arm/tegra/{emc.txt → nvidia,tegra20-emc.txt}
  81. +1 1  Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-mc.txt
  82. +1 1  Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt
  83. +30 0 Documentation/devicetree/bindings/ata/cavium-compact-flash.txt
  84. +16 0 Documentation/devicetree/bindings/ata/marvell.txt
  85. +17 0 Documentation/devicetree/bindings/clock/calxeda.txt
  86. +117 0 Documentation/devicetree/bindings/clock/clock-bindings.txt
  87. +21 0 Documentation/devicetree/bindings/clock/fixed-clock.txt
  88. +19 0 Documentation/devicetree/bindings/fb/mxsfb.txt
  89. +49 0 Documentation/devicetree/bindings/gpio/cavium-octeon-gpio.txt
  90. +13 3 Documentation/devicetree/bindings/gpio/fsl-imx-gpio.txt
  91. +3 2 Documentation/devicetree/bindings/gpio/gpio-mxs.txt
  92. +1 1  Documentation/devicetree/bindings/gpio/gpio-nmk.txt
  93. +5 4 Documentation/devicetree/bindings/gpio/gpio-samsung.txt
  94. +1 1  Documentation/devicetree/bindings/gpio/led.txt
  95. +23 0 Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
  96. 0  Documentation/devicetree/bindings/gpio/{gpio_nvidia.txt → nvidia,tegra20-gpio.txt}
  97. +34 0 Documentation/devicetree/bindings/i2c/cavium-i2c.txt
  98. 0  Documentation/devicetree/bindings/{gpio/gpio_i2c.txt → i2c/gpio-i2c.txt}
  99. +3 0  Documentation/devicetree/bindings/i2c/i2c-mxs.txt
  100. +33 0 Documentation/devicetree/bindings/i2c/i2c-ocores.txt
  101. +18 1 Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
  102. +1 0  Documentation/devicetree/bindings/input/fsl-mma8450.txt
  103. +28 0 Documentation/devicetree/bindings/input/lpc32xx-key.txt
  104. 0  Documentation/devicetree/bindings/input/{tegra-kbc.txt → nvidia,tegra20-kbc.txt}
  105. +31 0 Documentation/devicetree/bindings/input/omap-keypad.txt
  106. +0 37 Documentation/devicetree/bindings/input/twl6040-vibra.txt
  107. +21 0 Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt
  108. +123 0 Documentation/devicetree/bindings/mfd/ab8500.txt
  109. +59 0 Documentation/devicetree/bindings/mfd/max77686.txt
  110. +2 2 Documentation/devicetree/bindings/mfd/mc13xxx.txt
  111. +78 14 Documentation/devicetree/bindings/mfd/tps65910.txt
  112. +1 1  Documentation/devicetree/bindings/mfd/twl6040.txt
  113. +126 0 Documentation/devicetree/bindings/mips/cavium/bootbus.txt
  114. +26 0 Documentation/devicetree/bindings/mips/cavium/ciu.txt
  115. +27 0 Documentation/devicetree/bindings/mips/cavium/ciu2.txt
  116. +21 0 Documentation/devicetree/bindings/mips/cavium/dma-engine.txt
  117. +46 0 Documentation/devicetree/bindings/mips/cavium/uctl.txt
  118. +21 0 Documentation/devicetree/bindings/misc/at25.txt
  119. +13 12 Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
  120. +5 7 Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.txt
  121. +4 4 Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt
  122. +7 3 Documentation/devicetree/bindings/mmc/mmc.txt
  123. +4 8 Documentation/devicetree/bindings/mmc/mmci.txt
  124. +3 5 Documentation/devicetree/bindings/mmc/mxs-mmc.txt
  125. +3 5 Documentation/devicetree/bindings/mmc/{nvidia-sdhci.txt → nvidia,tegra20-sdhci.txt}
  126. +21 0 Documentation/devicetree/bindings/mmc/sdhci-pxa.txt
  127. +3 4 Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
  128. +2 2 Documentation/devicetree/bindings/mtd/orion-nand.txt
  129. +1 1  Documentation/devicetree/bindings/mtd/partition.txt
  130. +29 0 Documentation/devicetree/bindings/net/broadcom-bcm87xx.txt
  131. +3 0  Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
  132. +27 0 Documentation/devicetree/bindings/net/cavium-mdio.txt
  133. +39 0 Documentation/devicetree/bindings/net/cavium-mix.txt
  134. +98 0 Documentation/devicetree/bindings/net/cavium-pip.txt
  135. +41 0 Documentation/devicetree/bindings/net/davinci_emac.txt
  136. +6 2 Documentation/devicetree/bindings/net/fsl-fec.txt
  137. +11 1 Documentation/devicetree/bindings/net/phy.txt
  138. +2 1  Documentation/devicetree/bindings/net/stmmac.txt
  139. 0  Documentation/devicetree/bindings/nvec/{nvec_nvidia.txt → nvidia,nvec.txt}
  140. +2 0  Documentation/devicetree/bindings/pinctrl/fsl,imx6q-pinctrl.txt
  141. +93 0 Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt
  142. +12 0 Documentation/devicetree/bindings/pwm/lpc32xx-pwm.txt
  143. +17 0 Documentation/devicetree/bindings/pwm/mxs-pwm.txt
  144. +18 0 Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt
  145. +57 0 Documentation/devicetree/bindings/pwm/pwm.txt
  146. +2 0  Documentation/devicetree/bindings/regulator/fixed-regulator.txt
  147. +5 0 Documentation/devicetree/bindings/regulator/regulator.txt
  148. +91 0 Documentation/devicetree/bindings/regulator/tps65217.txt
  149. +62 15 Documentation/devicetree/bindings/regulator/tps6586x.txt
  150. +0 1  Documentation/devicetree/bindings/regulator/twl-regulator.txt
  151. +25 0 Documentation/devicetree/bindings/rtc/dw-apb.txt
  152. +16 0 Documentation/devicetree/bindings/rtc/stmp3xxx-rtc.txt
  153. +19 0 Documentation/devicetree/bindings/serial/cavium-uart.txt
  154. 0  Documentation/devicetree/bindings/sound/{tegra-audio-alc5632.txt → nvidia,tegra-audio-alc5632.txt}
  155. 0  Documentation/devicetree/bindings/sound/{tegra-audio-trimslice.txt → nvidia,tegra-audio-trimslice.txt}
  156. 0  Documentation/devicetree/bindings/sound/{tegra-audio-wm8753.txt → nvidia,tegra-audio-wm8753.txt}
  157. 0  Documentation/devicetree/bindings/sound/{tegra-audio-wm8903.txt → nvidia,tegra-audio-wm8903.txt}
  158. 0  Documentation/devicetree/bindings/sound/{tegra20-das.txt → nvidia,tegra20-das.txt}
  159. 0  Documentation/devicetree/bindings/sound/{tegra20-i2s.txt → nvidia,tegra20-i2s.txt}
  160. +2 2 Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt
  161. 0  Documentation/devicetree/bindings/spi/{spi_nvidia.txt → nvidia,tegra20-spi.txt}
  162. +19 0 Documentation/devicetree/bindings/spi/spi-orion.txt
  163. +116 0 Documentation/devicetree/bindings/spi/spi-samsung.txt
  164. +14 0 Documentation/devicetree/bindings/thermal/spear-thermal.txt
  165. +27 0 Documentation/devicetree/bindings/tty/serial/fsl-mxs-auart.txt
  166. +1 0  Documentation/devicetree/bindings/tty/serial/of-serial.txt
  167. +18 0 Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
  168. +13 0 Documentation/devicetree/bindings/usb/mxs-phy.txt
  169. 0  Documentation/devicetree/bindings/usb/{tegra-usb.txt → nvidia,tegra20-ehci.txt}
  170. +1 0  Documentation/devicetree/bindings/vendor-prefixes.txt
  171. +28 0 Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt
  172. +14 0 Documentation/devicetree/bindings/watchdog/marvel.txt
  173. +14 0 Documentation/devicetree/bindings/watchdog/omap-wdt.txt
  174. +1 1  Documentation/devicetree/usage-model.txt
  175. +0 1  Documentation/dontdiff
  176. +41 1 Documentation/dvb/get_dvb_firmware
  177. +8 104 Documentation/edac.txt
  178. +27 0 Documentation/fault-injection/fault-injection.txt
  179. +99 0 Documentation/fault-injection/notifier-error-inject.txt
  180. +71 46 Documentation/feature-removal-schedule.txt
  181. +22 10 Documentation/filesystems/Locking
  182. +17 9 Documentation/filesystems/porting
  183. +29 10 Documentation/filesystems/vfs.txt
  184. +169 0 Documentation/hid/uhid.txt
  185. +61 0 Documentation/hwmon/da9052
  186. +37 0 Documentation/hwmon/hih6130
  187. +3 0  Documentation/hwmon/submitting-patches
  188. +10 3 Documentation/i2c/busses/i2c-i801
  189. +9 0 Documentation/i2c/busses/i2c-piix4
  190. +15 8 Documentation/i2c/writing-clients
  191. +54 0 Documentation/input/edt-ft5x06.txt
  192. +92 26 Documentation/input/multi-touch-protocol.txt
  193. +1 0  Documentation/ioctl/ioctl-number.txt
  194. +1 1  Documentation/kdump/kdump.txt
  195. +8 2 Documentation/kernel-parameters.txt
  196. +1 2  Documentation/laptops/asus-laptop.txt
  197. +6 6 Documentation/laptops/laptop-mode.txt
  198. +2 0  Documentation/leds/00-INDEX
  199. +80 0 Documentation/leds/leds-blinkm.txt
  200. +85 0 Documentation/leds/leds-lm3556.txt
  201. +59 0 Documentation/leds/ledtrig-oneshot.txt
  202. +7 7 Documentation/misc-devices/mei/mei.txt
  203. +5 0 Documentation/networking/batman-adv.txt
  204. +3 3 Documentation/networking/bonding.txt
  205. +10 3 Documentation/networking/bridge.txt
  206. +27 64 Documentation/networking/caif/Linux-CAIF.txt
  207. +162 24 Documentation/networking/can.txt
  208. +59 9 Documentation/networking/ip-sysctl.txt
  209. +1 1  Documentation/networking/openvswitch.txt
  210. +2 12 Documentation/networking/s2io.txt
  211. +30 6 Documentation/networking/stmmac.txt
  212. +0 7 Documentation/networking/vxge.txt
  213. +33 0 Documentation/nfc/nfc-hci.txt
  214. +5 4 Documentation/power/devices.txt
  215. +10 0 Documentation/power/power_supply_class.txt
  216. +5 0 Documentation/power/swsusp.txt
  217. +57 0 Documentation/prctl/no_new_privs.txt
  218. +15 0 Documentation/printk-formats.txt
  219. +76 0 Documentation/pwm.txt
  220. +39 0 Documentation/ramoops.txt
  221. +14 44 Documentation/remoteproc.txt
  222. +7 7 Documentation/security/Yama.txt
  223. +1 2  Documentation/sound/alsa/ALSA-Configuration.txt
  224. +15 3 Documentation/sound/alsa/HD-Audio-Models.txt
  225. +1 1  Documentation/sound/alsa/hdspm.txt
  226. +20 5 Documentation/stable_kernel_rules.txt
  227. +54 6 Documentation/sysctl/fs.txt
  228. +21 23 Documentation/sysctl/vm.txt
  229. +19 11 Documentation/thermal/sysfs-api.txt
  230. +226 0 Documentation/usb/mass-storage.txt
  231. +314 0 Documentation/vfio.txt
  232. +1 1  Documentation/video4linux/CARDLIST.au0828
  233. +1 0  Documentation/video4linux/CARDLIST.bttv
  234. +3 1 Documentation/video4linux/CARDLIST.cx23885
  235. +1 0  Documentation/video4linux/CARDLIST.saa7134
  236. +1 1  Documentation/video4linux/cpia2_overview.txt
  237. +1 1  Documentation/video4linux/stv680.txt
  238. +39 34 Documentation/video4linux/v4l2-framework.txt
  239. +51 0 Documentation/virtual/kvm/api.txt
  240. +129 1 Documentation/virtual/kvm/locking.txt
  241. +33 0 Documentation/virtual/kvm/msr.txt
  242. +0 2  Documentation/virtual/kvm/ppc-pv.txt
  243. +2 2 Documentation/vm/frontswap.txt
  244. +36 0 Documentation/w1/slaves/w1_ds28e04
  245. +38 65 Documentation/workqueue.txt
  246. +45 1 Documentation/x86/boot.txt
  247. +171 77 MAINTAINERS
  248. +14 14 Makefile
  249. +7 0 arch/Kconfig
  250. +1 0  arch/alpha/Kconfig
  251. +0 1  arch/alpha/include/asm/unistd.h
  252. +4 13 arch/alpha/kernel/pci.c
  253. +0 12 arch/alpha/kernel/smc37c669.c
  254. +76 8 arch/arm/Kconfig
  255. +35 0 arch/arm/Kconfig.debug
  256. +5 0 arch/arm/Makefile
  257. +60 2 arch/arm/boot/compressed/atags_to_fdt.c
  258. +113 0 arch/arm/boot/dts/aks-cdu.dts
  259. +20 0 arch/arm/boot/dts/am335x-bone.dts
  260. +20 0 arch/arm/boot/dts/am335x-evm.dts
  261. +158 0 arch/arm/boot/dts/am33xx.dtsi
  262. +32 0 arch/arm/boot/dts/am3517-evm.dts
  263. +42 0 arch/arm/boot/dts/armada-370-db.dts
  264. +68 0 arch/arm/boot/dts/armada-370-xp.dtsi
  265. +35 0 arch/arm/boot/dts/armada-370.dtsi
  266. +50 0 arch/arm/boot/dts/armada-xp-db.dts
  267. +55 0 arch/arm/boot/dts/armada-xp.dtsi
  268. +19 18 arch/arm/boot/dts/at91sam9260.dtsi
  269. +16 15 arch/arm/boot/dts/at91sam9263.dtsi
  270. +20 19 arch/arm/boot/dts/at91sam9g45.dtsi
  271. +15 15 arch/arm/boot/dts/at91sam9n12.dtsi
  272. +20 19 arch/arm/boot/dts/at91sam9x5.dtsi
  273. +97 10 arch/arm/boot/dts/db8500.dtsi
  274. +174 0 arch/arm/boot/dts/ea3250.dts
  275. +41 0 arch/arm/boot/dts/evk-pro3.dts
  276. +12 0 arch/arm/boot/dts/exynos4210-origen.dts
  277. +38 0 arch/arm/boot/dts/exynos4210-smdkv310.dts
  278. +47 0 arch/arm/boot/dts/exynos4210.dtsi
  279. +38 0 arch/arm/boot/dts/exynos5250-smdk5250.dts
  280. +36 0 arch/arm/boot/dts/exynos5250.dtsi
  281. +52 0 arch/arm/boot/dts/ge863-pro3.dtsi
  282. +102 1 arch/arm/boot/dts/highbank.dts
  283. +64 2 arch/arm/boot/dts/imx23-evk.dts
  284. +44 0 arch/arm/boot/dts/imx23-olinuxino.dts
  285. +78 0 arch/arm/boot/dts/imx23-stmp378x_devb.dts
  286. +180 39 arch/arm/boot/dts/imx23.dtsi
  287. +41 0 arch/arm/boot/dts/imx27-3ds.dts
  288. +12 6 arch/arm/boot/dts/imx27.dtsi
  289. +198 0 arch/arm/boot/dts/imx28-apx4devkit.dts
  290. +52 0 arch/arm/boot/dts/imx28-cfa10036.dts
  291. +164 0 arch/arm/boot/dts/imx28-evk.dts
  292. +210 0 arch/arm/boot/dts/imx28-m28evk.dts
  293. +97 0 arch/arm/boot/dts/imx28-tx28.dts
  294. +362 65 arch/arm/boot/dts/imx28.dtsi
  295. +31 0 arch/arm/boot/dts/imx31-bug.dts
  296. +88 0 arch/arm/boot/dts/imx31.dtsi
  297. +1 1  arch/arm/boot/dts/imx51-babbage.dts
  298. +12 8 arch/arm/boot/dts/imx51.dtsi
  299. +21 1 arch/arm/boot/dts/imx53-ard.dts
  300. +21 14 arch/arm/boot/dts/imx53.dtsi
  301. +6 0 arch/arm/boot/dts/imx6q-arm2.dts
  302. +34 0 arch/arm/boot/dts/imx6q-sabrelite.dts
  303. +104 16 arch/arm/boot/dts/imx6q.dtsi
  304. +27 37 arch/arm/boot/dts/kirkwood-dns320.dts
  305. +34 36 arch/arm/boot/dts/kirkwood-dns325.dts
  306. +69 0 arch/arm/boot/dts/kirkwood-dnskw.dtsi
  307. +51 1 arch/arm/boot/dts/kirkwood-dreamplug.dts
  308. +99 0 arch/arm/boot/dts/kirkwood-goflexnet.dts
  309. +39 1 arch/arm/boot/dts/kirkwood-ib62x0.dts
  310. +43 1 arch/arm/boot/dts/kirkwood-iconnect.dts
  311. +20 0 arch/arm/boot/dts/kirkwood-lschlv2.dts
  312. +20 0 arch/arm/boot/dts/kirkwood-lsxhl.dts
Sorry, we could not display the entire diff because too many files (8,205) changed.
5 Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
... ... @@ -0,0 +1,5 @@
  1 +What: /proc/sys/vm/nr_pdflush_threads
  2 +Date: June 2012
  3 +Contact: Wanpeng Li <liwp@linux.vnet.ibm.com>
  4 +Description: Since pdflush is replaced by per-BDI flusher, the interface of old pdflush
  5 + exported in /proc/sys/vm/ should be removed.
11 Documentation/ABI/stable/sysfs-bus-firewire
@@ -39,6 +39,17 @@ Users: udev rules to set ownership and access permissions or ACLs of
39 39 /dev/fw[0-9]+ character device files
40 40
41 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 +
42 53 What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/
43 54 Date: May 2007
44 55 KernelVersion: 2.6.22
15 Documentation/ABI/stable/sysfs-driver-w1_ds28e04
... ... @@ -0,0 +1,15 @@
  1 +What: /sys/bus/w1/devices/.../pio
  2 +Date: May 2012
  3 +Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
  4 +Description: read/write the contents of the two PIO's of the DS28E04-100
  5 + see Documentation/w1/slaves/w1_ds28e04 for detailed information
  6 +Users: any user space application which wants to communicate with DS28E04-100
  7 +
  8 +
  9 +
  10 +What: /sys/bus/w1/devices/.../eeprom
  11 +Date: May 2012
  12 +Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
  13 +Description: read/write the contents of the EEPROM memory of the DS28E04-100
  14 + see Documentation/w1/slaves/w1_ds28e04 for detailed information
  15 +Users: any user space application which wants to communicate with DS28E04-100
2  Documentation/ABI/stable/vdso
@@ -24,4 +24,4 @@ though.
24 24
25 25 (As of this writing, this ABI documentation as been confirmed for x86_64.
26 26 The maintainers of the other vDSO-using architectures should confirm
27   - that it is correct for their architecture.)
  27 + that it is correct for their architecture.)
29 Documentation/ABI/testing/dev-kmsg
@@ -58,16 +58,18 @@ Description: The /dev/kmsg character device node provides userspace access
58 58
59 59 The output format consists of a prefix carrying the syslog
60 60 prefix including priority and facility, the 64 bit message
61   - sequence number and the monotonic timestamp in microseconds.
62   - The values are separated by a ','. Future extensions might
63   - add more comma separated values before the terminating ';'.
64   - Unknown values should be gracefully ignored.
  61 + sequence number and the monotonic timestamp in microseconds,
  62 + and a flag field. All fields are separated by a ','.
  63 +
  64 + Future extensions might add more comma separated values before
  65 + the terminating ';'. Unknown fields and values should be
  66 + gracefully ignored.
65 67
66 68 The human readable text string starts directly after the ';'
67 69 and is terminated by a '\n'. Untrusted values derived from
68 70 hardware or other facilities are printed, therefore
69   - all non-printable characters in the log message are escaped
70   - by "\x00" C-style hex encoding.
  71 + all non-printable characters and '\' itself in the log message
  72 + are escaped by "\x00" C-style hex encoding.
71 73
72 74 A line starting with ' ', is a continuation line, adding
73 75 key/value pairs to the log message, which provide the machine
@@ -75,11 +77,11 @@ Description: The /dev/kmsg character device node provides userspace access
75 77 userspace.
76 78
77 79 Example:
78   - 7,160,424069;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
  80 + 7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
79 81 SUBSYSTEM=acpi
80 82 DEVICE=+acpi:PNP0A03:00
81   - 6,339,5140900;NET: Registered protocol family 10
82   - 30,340,5690716;udevd[80]: starting version 181
  83 + 6,339,5140900,-;NET: Registered protocol family 10
  84 + 30,340,5690716,-;udevd[80]: starting version 181
83 85
84 86 The DEVICE= key uniquely identifies devices the following way:
85 87 b12:8 - block dev_t
@@ -87,4 +89,13 @@ Description: The /dev/kmsg character device node provides userspace access
87 89 n8 - netdev ifindex
88 90 +sound:card0 - subsystem:devname
89 91
  92 + The flags field carries '-' by default. A 'c' indicates a
  93 + fragment of a line. All following fragments are flagged with
  94 + '+'. Note, that these hints about continuation lines are not
  95 + neccessarily correct, and the stream could be interleaved with
  96 + unrelated messages, but merging the lines in the output
  97 + usually produces better human readable results. A similar
  98 + logic is used internally when messages are printed to the
  99 + console, /proc/kmsg or the syslog() syscall.
  100 +
90 101 Users: dmesg(1), userspace kernel log consumers
21 Documentation/ABI/testing/sysfs-block-rssd
... ... @@ -1,26 +1,5 @@
1   -What: /sys/block/rssd*/registers
2   -Date: March 2012
3   -KernelVersion: 3.3
4   -Contact: Asai Thambi S P <asamymuthupa@micron.com>
5   -Description: This is a read-only file. Dumps below driver information and
6   - hardware registers.
7   - - S ACTive
8   - - Command Issue
9   - - Completed
10   - - PORT IRQ STAT
11   - - HOST IRQ STAT
12   - - Allocated
13   - - Commands in Q
14   -
15 1 What: /sys/block/rssd*/status
16 2 Date: April 2012
17 3 KernelVersion: 3.4
18 4 Contact: Asai Thambi S P <asamymuthupa@micron.com>
19 5 Description: This is a read-only file. Indicates the status of the device.
20   -
21   -What: /sys/block/rssd*/flags
22   -Date: May 2012
23   -KernelVersion: 3.5
24   -Contact: Asai Thambi S P <asamymuthupa@micron.com>
25   -Description: This is a read-only file. Dumps the flags in port and driver
26   - data structure
2  Documentation/ABI/testing/sysfs-block-zram
@@ -96,4 +96,4 @@ Description:
96 96 overhead, allocated for this disk. So, allocator space
97 97 efficiency can be calculated using compr_data_size and this
98 98 statistic.
99   - Unit: bytes
  99 + Unit: bytes
54 Documentation/ABI/testing/sysfs-bus-iio
@@ -40,9 +40,9 @@ Contact: linux-iio@vger.kernel.org
40 40 Description:
41 41 Some devices have internal clocks. This parameter sets the
42 42 resulting sampling frequency. In many devices this
43   - parameter has an effect on input filters etc rather than
  43 + parameter has an effect on input filters etc. rather than
44 44 simply controlling when the input is sampled. As this
45   - effects datardy triggers, hardware buffers and the sysfs
  45 + effects data ready triggers, hardware buffers and the sysfs
46 46 direct access interfaces, it may be found in any of the
47 47 relevant directories. If it effects all of the above
48 48 then it is to be found in the base device directory.
@@ -74,7 +74,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
74 74 KernelVersion: 2.6.35
75 75 Contact: linux-iio@vger.kernel.org
76 76 Description:
77   - Raw (unscaled no bias removal etc) voltage measurement from
  77 + Raw (unscaled no bias removal etc.) voltage measurement from
78 78 channel Y. In special cases where the channel does not
79 79 correspond to externally available input one of the named
80 80 versions may be used. The number must always be specified and
@@ -118,11 +118,11 @@ What: /sys/bus/iio/devices/iio:deviceX/in_temp_z_raw
118 118 KernelVersion: 2.6.35
119 119 Contact: linux-iio@vger.kernel.org
120 120 Description:
121   - Raw (unscaled no bias removal etc) temperature measurement.
  121 + Raw (unscaled no bias removal etc.) temperature measurement.
122 122 If an axis is specified it generally means that the temperature
123 123 sensor is associated with one part of a compound device (e.g.
124 124 a gyroscope axis). Units after application of scale and offset
125   - are milli degrees Celsuis.
  125 + are milli degrees Celsius.
126 126
127 127 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
128 128 KernelVersion: 2.6.38
@@ -148,10 +148,9 @@ KernelVersion: 2.6.35
148 148 Contact: linux-iio@vger.kernel.org
149 149 Description:
150 150 Angular velocity about axis x, y or z (may be arbitrarily
151   - assigned) Data converted by application of offset then scale to
152   - radians per second. Has all the equivalent parameters as
153   - per voltageY. Units after application of scale and offset are
154   - radians per second.
  151 + assigned). Has all the equivalent parameters as per voltageY.
  152 + Units after application of scale and offset are radians per
  153 + second.
155 154
156 155 What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
157 156 What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
@@ -161,7 +160,7 @@ Contact: linux-iio@vger.kernel.org
161 160 Description:
162 161 Inclination raw reading about axis x, y or z (may be
163 162 arbitrarily assigned). Data converted by application of offset
164   - and scale to Degrees.
  163 + and scale to degrees.
165 164
166 165 What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
167 166 What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
@@ -203,7 +202,7 @@ Contact: linux-iio@vger.kernel.org
203 202 Description:
204 203 If known for a device, offset to be added to <type>[Y]_raw prior
205 204 to scaling by <type>[Y]_scale in order to obtain value in the
206   - <type> units as specified in <type>[y]_raw documentation.
  205 + <type> units as specified in <type>[Y]_raw documentation.
207 206 Not present if the offset is always 0 or unknown. If Y or
208 207 axis <x|y|z> is not present, then the offset applies to all
209 208 in channels of <type>.
@@ -249,7 +248,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
249 248 KernelVersion: 2.6.35
250 249 Contact: linux-iio@vger.kernel.org
251 250 Description:
252   - Hardware applied calibration offset. (assumed to fix production
  251 + Hardware applied calibration offset (assumed to fix production
253 252 inaccuracies).
254 253
255 254 What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
@@ -266,7 +265,7 @@ what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
266 265 KernelVersion: 2.6.35
267 266 Contact: linux-iio@vger.kernel.org
268 267 Description:
269   - Hardware applied calibration scale factor. (assumed to fix
  268 + Hardware applied calibration scale factor (assumed to fix
270 269 production inaccuracies). If shared across all channels,
271 270 <type>_calibscale is used.
272 271
@@ -276,10 +275,10 @@ What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
276 275 What: /sys/.../iio:deviceX/out_voltageX_scale_available
277 276 What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
278 277 What: /sys/.../iio:deviceX/in_capacitance_scale_available
279   -KernelVersion: 2.635
  278 +KernelVersion: 2.6.35
280 279 Contact: linux-iio@vger.kernel.org
281 280 Description:
282   - If a discrete set of scale values are available, they
  281 + If a discrete set of scale values is available, they
283 282 are listed in this attribute.
284 283
285 284 What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
@@ -330,9 +329,11 @@ Contact: linux-iio@vger.kernel.org
330 329 Description:
331 330 Specifies the output powerdown mode.
332 331 DAC output stage is disconnected from the amplifier and
333   - 1kohm_to_gnd: connected to ground via an 1kOhm resistor
334   - 100kohm_to_gnd: connected to ground via an 100kOhm resistor
335   - three_state: left floating
  332 + 1kohm_to_gnd: connected to ground via an 1kOhm resistor,
  333 + 6kohm_to_gnd: connected to ground via a 6kOhm resistor,
  334 + 20kohm_to_gnd: connected to ground via a 20kOhm resistor,
  335 + 100kohm_to_gnd: connected to ground via an 100kOhm resistor,
  336 + three_state: left floating.
336 337 For a list of available output power down options read
337 338 outX_powerdown_mode_available. If Y is not present the
338 339 mode is shared across all outputs.
@@ -355,9 +356,10 @@ KernelVersion: 2.6.38
355 356 Contact: linux-iio@vger.kernel.org
356 357 Description:
357 358 Writing 1 causes output Y to enter the power down mode specified
358   - by the corresponding outY_powerdown_mode. Clearing returns to
359   - normal operation. Y may be suppressed if all outputs are
360   - controlled together.
  359 + by the corresponding outY_powerdown_mode. DAC output stage is
  360 + disconnected from the amplifier. Clearing returns to normal
  361 + operation. Y may be suppressed if all outputs are controlled
  362 + together.
361 363
362 364 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
363 365 KernelVersion: 3.4.0
@@ -421,12 +423,12 @@ Description:
421 423 different values, but the device can only enable both thresholds
422 424 or neither.
423 425 Note the driver will assume the last p events requested are
424   - to be enabled where p is however many it supports (which may
425   - vary depending on the exact set requested. So if you want to be
  426 + to be enabled where p is how many it supports (which may vary
  427 + depending on the exact set requested. So if you want to be
426 428 sure you have set what you think you have, check the contents of
427 429 these attributes after everything is configured. Drivers may
428 430 have to buffer any parameters so that they are consistent when
429   - a given event type is enabled a future point (and not those for
  431 + a given event type is enabled at a future point (and not those for
430 432 whatever event was previously enabled).
431 433
432 434 What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
@@ -702,7 +704,7 @@ What: /sys/.../buffer/scan_elements/in_anglvel_type
702 704 What: /sys/.../buffer/scan_elements/in_magn_type
703 705 What: /sys/.../buffer/scan_elements/in_incli_type
704 706 What: /sys/.../buffer/scan_elements/in_voltageY_type
705   -What: /sys/.../buffer/scan_elements/in_voltage-in_type
  707 +What: /sys/.../buffer/scan_elements/in_voltage_type
706 708 What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
707 709 What: /sys/.../buffer/scan_elements/in_timestamp_type
708 710 KernelVersion: 2.6.37
@@ -723,7 +725,7 @@ Description:
723 725 the buffer output value appropriately. The storagebits value
724 726 also specifies the data alignment. So s48/64>>2 will be a
725 727 signed 48 bit integer stored in a 64 bit location aligned to
726   - a a64 bit boundary. To obtain the clean value, shift right 2
  728 + a 64 bit boundary. To obtain the clean value, shift right 2
727 729 and apply a mask to zero the top 16 bits of the result.
728 730 For other storage combinations this attribute will be extended
729 731 appropriately.
37 Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
... ... @@ -0,0 +1,37 @@
  1 +What: /sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present
  2 +What: /sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present
  3 +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present
  4 +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present
  5 +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present
  6 +What: /sys/bus/iio/devices/iio:deviceX/vcxo_clk_present
  7 +KernelVersion: 3.4.0
  8 +Contact: linux-iio@vger.kernel.org
  9 +Description:
  10 + Reading returns either '1' or '0'.
  11 + '1' means that the clock in question is present.
  12 + '0' means that the clock is missing.
  13 +
  14 +What: /sys/bus/iio/devices/iio:deviceX/pllY_locked
  15 +KernelVersion: 3.4.0
  16 +Contact: linux-iio@vger.kernel.org
  17 +Description:
  18 + Reading returns either '1' or '0'. '1' means that the
  19 + pllY is locked.
  20 +
  21 +What: /sys/bus/iio/devices/iio:deviceX/store_eeprom
  22 +KernelVersion: 3.4.0
  23 +Contact: linux-iio@vger.kernel.org
  24 +Description:
  25 + Writing '1' stores the current device configuration into
  26 + on-chip EEPROM. After power-up or chip reset the device will
  27 + automatically load the saved configuration.
  28 +
  29 +What: /sys/bus/iio/devices/iio:deviceX/sync_dividers
  30 +KernelVersion: 3.4.0
  31 +Contact: linux-iio@vger.kernel.org
  32 +Description:
  33 + Writing '1' triggers the clock distribution synchronization
  34 + functionality. All dividers are reset and the channels start
  35 + with their predefined phase offsets (out_altvoltageY_phase).
  36 + Writing this file has the effect as driving the external
  37 + /SYNC pin low.
21 Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
... ... @@ -0,0 +1,21 @@
  1 +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution
  2 +KernelVersion: 3.4.0
  3 +Contact: linux-iio@vger.kernel.org
  4 +Description:
  5 + Stores channel Y frequency resolution/channel spacing in Hz.
  6 + The value given directly influences the MODULUS used by
  7 + the fractional-N PLL. It is assumed that the algorithm
  8 + that is used to compute the various dividers, is able to
  9 + generate proper values for multiples of channel spacing.
  10 +
  11 +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency
  12 +KernelVersion: 3.4.0
  13 +Contact: linux-iio@vger.kernel.org
  14 +Description:
  15 + Sets channel Y REFin frequency in Hz. In some clock chained
  16 + applications, the reference frequency used by the PLL may
  17 + change during runtime. This attribute allows the user to
  18 + adjust the reference frequency accordingly.
  19 + The value written has no effect until out_altvoltageY_frequency
  20 + is updated. Consider to use out_altvoltageY_powerdown to power
  21 + down the PLL and it's RFOut buffers during REFin changes.
61 Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
... ... @@ -0,0 +1,61 @@
  1 +What: /sys/.../events/in_illuminance0_thresh_either_en
  2 +Date: April 2012
  3 +KernelVersion: 3.5
  4 +Contact: Johan Hovold <jhovold@gmail.com>
  5 +Description:
  6 + Event generated when channel passes one of the four thresholds
  7 + in each direction (rising|falling) and a zone change occurs.
  8 + The corresponding light zone can be read from
  9 + in_illuminance0_zone.
  10 +
  11 +What: /sys/.../events/in_illuminance0_threshY_hysteresis
  12 +Date: May 2012
  13 +KernelVersion: 3.5
  14 +Contact: Johan Hovold <jhovold@gmail.com>
  15 +Description:
  16 + Get the hysteresis for thresholds Y, that is,
  17 + threshY_hysteresis = threshY_raising - threshY_falling
  18 +
  19 +What: /sys/.../events/illuminance_threshY_falling_value
  20 +What: /sys/.../events/illuminance_threshY_raising_value
  21 +Date: April 2012
  22 +KernelVersion: 3.5
  23 +Contact: Johan Hovold <jhovold@gmail.com>
  24 +Description:
  25 + Specifies the value of threshold that the device is comparing
  26 + against for the events enabled by
  27 + in_illuminance0_thresh_either_en (0..255), where Y in 0..3.
  28 +
  29 + Note that threshY_falling must be less than or equal to
  30 + threshY_raising.
  31 +
  32 + These thresholds correspond to the eight zone-boundary
  33 + registers (boundaryY_{low,high}) and define the five light
  34 + zones.
  35 +
  36 +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone
  37 +Date: April 2012
  38 +KernelVersion: 3.5
  39 +Contact: Johan Hovold <jhovold@gmail.com>
  40 +Description:
  41 + Get the current light zone (0..4) as defined by the
  42 + in_illuminance0_threshY_{falling,rising} thresholds.
  43 +
  44 +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw
  45 +Date: May 2012
  46 +KernelVersion: 3.5
  47 +Contact: Johan Hovold <jhovold@gmail.com>
  48 +Description:
  49 + Get output current for channel Y (0..255), that is,
  50 + out_currentY_currentZ_raw, where Z is the current zone.
  51 +
  52 +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_currentZ_raw
  53 +Date: May 2012
  54 +KernelVersion: 3.5
  55 +Contact: Johan Hovold <jhovold@gmail.com>
  56 +Description:
  57 + Set the output current for channel out_currentY when in zone
  58 + Z (0..255), where Y in 0..2 and Z in 0..4.
  59 +
  60 + These values correspond to the ALS-mapper target registers for
  61 + ALS-mapper Y + 1.
10 Documentation/ABI/testing/sysfs-bus-rbd
@@ -35,8 +35,14 @@ name
35 35
36 36 pool
37 37
38   - The pool where this rbd image resides. The pool-name pair is unique
39   - per rados system.
  38 + The name of the storage pool where this rbd image resides.
  39 + An rbd image name is unique within its pool.
  40 +
  41 +pool_id
  42 +
  43 + The unique identifier for the rbd image's pool. This is
  44 + a permanent attribute of the pool. A pool's id will never
  45 + change.
40 46
41 47 size
42 48
12 Documentation/ABI/testing/sysfs-bus-usb
@@ -208,3 +208,15 @@ Description:
208 208 such as ACPI. This file will read either "removable" or
209 209 "fixed" if the information is available, and "unknown"
210 210 otherwise.
  211 +
  212 +What: /sys/bus/usb/devices/.../ltm_capable
  213 +Date: July 2012
  214 +Contact: Sarah Sharp <sarah.a.sharp@linux.intel.com>
  215 +Description:
  216 + USB 3.0 devices may optionally support Latency Tolerance
  217 + Messaging (LTM). They indicate their support by setting a bit
  218 + in the bmAttributes field of their SuperSpeed BOS descriptors.
  219 + If that bit is set for the device, ltm_capable will read "yes".
  220 + If the device doesn't support LTM, the file will read "no".
  221 + The file will be present for all speeds of USB devices, and will
  222 + always read "no" for USB 1.1 and USB 2.0 devices.
2  Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
@@ -40,4 +40,4 @@ Description: Controls the decimal places on the device.
40 40 the value of 10 ** n. Assume this field has
41 41 the value k and has 1 or more decimal places set,
42 42 to set the mth place (where m is not already set),
43   - change this fields value to k + 10 ** m.
  43 + change this fields value to k + 10 ** m.
2  Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
@@ -53,4 +53,4 @@ Description:
53 53 Documentation/ABI/stable/sysfs-class-backlight.
54 54 It can be enabled by writing the value stored in
55 55 /sys/class/backlight/<backlight>/max_brightness to
56   - /sys/class/backlight/<backlight>/brightness.
  56 + /sys/class/backlight/<backlight>/brightness.
17 Documentation/ABI/testing/sysfs-class-mtd
@@ -142,13 +142,14 @@ KernelVersion: 3.4
142 142 Contact: linux-mtd@lists.infradead.org
143 143 Description:
144 144 This allows the user to examine and adjust the criteria by which
145   - mtd returns -EUCLEAN from mtd_read(). If the maximum number of
146   - bit errors that were corrected on any single region comprising
147   - an ecc step (as reported by the driver) equals or exceeds this
148   - value, -EUCLEAN is returned. Otherwise, absent an error, 0 is
149   - returned. Higher layers (e.g., UBI) use this return code as an
150   - indication that an erase block may be degrading and should be
151   - scrutinized as a candidate for being marked as bad.
  145 + mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the
  146 + maximum number of bit errors that were corrected on any single
  147 + region comprising an ecc step (as reported by the driver) equals
  148 + or exceeds this value, -EUCLEAN is returned. Otherwise, absent
  149 + an error, 0 is returned. Higher layers (e.g., UBI) use this
  150 + return code as an indication that an erase block may be
  151 + degrading and should be scrutinized as a candidate for being
  152 + marked as bad.
152 153
153 154 The initial value may be specified by the flash device driver.
154 155 If not, then the default value is ecc_strength.
@@ -167,7 +168,7 @@ Description:
167 168 block degradation, but high enough to avoid the consequences of
168 169 a persistent return value of -EUCLEAN on devices where sticky
169 170 bitflips occur. Note that if bitflip_threshold exceeds
170   - ecc_strength, -EUCLEAN is never returned by mtd_read().
  171 + ecc_strength, -EUCLEAN is never returned by the read operations.
171 172 Conversely, if bitflip_threshold is zero, -EUCLEAN is always
172 173 returned, absent a hard error.
173 174
140 Documentation/ABI/testing/sysfs-devices-edac
... ... @@ -0,0 +1,140 @@
  1 +What: /sys/devices/system/edac/mc/mc*/reset_counters
  2 +Date: January 2006
  3 +Contact: linux-edac@vger.kernel.org
  4 +Description: This write-only control file will zero all the statistical
  5 + counters for UE and CE errors on the given memory controller.
  6 + Zeroing the counters will also reset the timer indicating how
  7 + long since the last counter were reset. This is useful for
  8 + computing errors/time. Since the counters are always reset
  9 + at driver initialization time, no module/kernel parameter
  10 + is available.
  11 +
  12 +What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
  13 +Date: January 2006
  14 +Contact: linux-edac@vger.kernel.org
  15 +Description: This attribute file displays how many seconds have elapsed
  16 + since the last counter reset. This can be used with the error
  17 + counters to measure error rates.
  18 +
  19 +What: /sys/devices/system/edac/mc/mc*/mc_name
  20 +Date: January 2006
  21 +Contact: linux-edac@vger.kernel.org
  22 +Description: This attribute file displays the type of memory controller
  23 + that is being utilized.
  24 +
  25 +What: /sys/devices/system/edac/mc/mc*/size_mb
  26 +Date: January 2006
  27 +Contact: linux-edac@vger.kernel.org
  28 +Description: This attribute file displays, in count of megabytes, of memory
  29 + that this memory controller manages.
  30 +
  31 +What: /sys/devices/system/edac/mc/mc*/ue_count
  32 +Date: January 2006
  33 +Contact: linux-edac@vger.kernel.org
  34 +Description: This attribute file displays the total count of uncorrectable
  35 + errors that have occurred on this memory controller. If
  36 + panic_on_ue is set, this counter will not have a chance to
  37 + increment, since EDAC will panic the system
  38 +
  39 +What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count
  40 +Date: January 2006
  41 +Contact: linux-edac@vger.kernel.org
  42 +Description: This attribute file displays the number of UEs that have
  43 + occurred on this memory controller with no information as to
  44 + which DIMM slot is having errors.
  45 +
  46 +What: /sys/devices/system/edac/mc/mc*/ce_count
  47 +Date: January 2006
  48 +Contact: linux-edac@vger.kernel.org
  49 +Description: This attribute file displays the total count of correctable
  50 + errors that have occurred on this memory controller. This
  51 + count is very important to examine. CEs provide early
  52 + indications that a DIMM is beginning to fail. This count
  53 + field should be monitored for non-zero values and report
  54 + such information to the system administrator.
  55 +
  56 +What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count
  57 +Date: January 2006
  58 +Contact: linux-edac@vger.kernel.org
  59 +Description: This attribute file displays the number of CEs that
  60 + have occurred on this memory controller wherewith no
  61 + information as to which DIMM slot is having errors. Memory is
  62 + handicapped, but operational, yet no information is available
  63 + to indicate which slot the failing memory is in. This count
  64 + field should be also be monitored for non-zero values.
  65 +
  66 +What: /sys/devices/system/edac/mc/mc*/sdram_scrub_rate
  67 +Date: February 2007
  68 +Contact: linux-edac@vger.kernel.org
  69 +Description: Read/Write attribute file that controls memory scrubbing.
  70 + The scrubbing rate used by the memory controller is set by
  71 + writing a minimum bandwidth in bytes/sec to the attribute file.
  72 + The rate will be translated to an internal value that gives at
  73 + least the specified rate.
  74 + Reading the file will return the actual scrubbing rate employed.
  75 + If configuration fails or memory scrubbing is not implemented,
  76 + the value of the attribute file will be -1.
  77 +
  78 +What: /sys/devices/system/edac/mc/mc*/max_location
  79 +Date: April 2012
  80 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  81 + linux-edac@vger.kernel.org
  82 +Description: This attribute file displays the information about the last
  83 + available memory slot in this memory controller. It is used by
  84 + userspace tools in order to display the memory filling layout.
  85 +
  86 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/size
  87 +Date: April 2012
  88 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  89 + linux-edac@vger.kernel.org
  90 +Description: This attribute file will display the size of dimm or rank.
  91 + For dimm*/size, this is the size, in MB of the DIMM memory
  92 + stick. For rank*/size, this is the size, in MB for one rank
  93 + of the DIMM memory stick. On single rank memories (1R), this
  94 + is also the total size of the dimm. On dual rank (2R) memories,
  95 + this is half the size of the total DIMM memories.
  96 +
  97 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_dev_type
  98 +Date: April 2012
  99 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  100 + linux-edac@vger.kernel.org
  101 +Description: This attribute file will display what type of DRAM device is
  102 + being utilized on this DIMM (x1, x2, x4, x8, ...).
  103 +
  104 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_edac_mode
  105 +Date: April 2012
  106 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  107 + linux-edac@vger.kernel.org
  108 +Description: This attribute file will display what type of Error detection
  109 + and correction is being utilized. For example: S4ECD4ED would
  110 + mean a Chipkill with x4 DRAM.
  111 +
  112 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_label
  113 +Date: April 2012
  114 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  115 + linux-edac@vger.kernel.org
  116 +Description: This control file allows this DIMM to have a label assigned
  117 + to it. With this label in the module, when errors occur
  118 + the output can provide the DIMM label in the system log.
  119 + This becomes vital for panic events to isolate the
  120 + cause of the UE event.
  121 + DIMM Labels must be assigned after booting, with information
  122 + that correctly identifies the physical slot with its
  123 + silk screen label. This information is currently very
  124 + motherboard specific and determination of this information
  125 + must occur in userland at this time.
  126 +
  127 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_location
  128 +Date: April 2012
  129 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  130 + linux-edac@vger.kernel.org
  131 +Description: This attribute file will display the location (csrow/channel,
  132 + branch/channel/slot or channel/slot) of the dimm or rank.
  133 +
  134 +What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_mem_type
  135 +Date: April 2012
  136 +Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
  137 + linux-edac@vger.kernel.org
  138 +Description: This attribute file will display what type of memory is
  139 + currently on this csrow. Normally, either buffered or
  140 + unbuffered memory (for example, Unbuffered-DDR3).
44 Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb
... ... @@ -0,0 +1,44 @@
  1 +What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha
  2 +Date: May 2012
  3 +Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
  4 +Description:
  5 + This file is only available on fb[0-9] devices corresponding
  6 + to overlay planes.
  7 +
  8 + Stores the alpha blending value for the overlay. Values range
  9 + from 0 (transparent) to 255 (opaque). The value is ignored if
  10 + the mode is not set to Alpha Blending.
  11 +
  12 +What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode
  13 +Date: May 2012
  14 +Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
  15 +Description:
  16 + This file is only available on fb[0-9] devices corresponding
  17 + to overlay planes.
  18 +
  19 + Selects the composition mode for the overlay. Possible values
  20 + are
  21 +
  22 + 0 - Alpha Blending
  23 + 1 - ROP3
  24 +
  25 +What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position
  26 +Date: May 2012
  27 +Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
  28 +Description:
  29 + This file is only available on fb[0-9] devices corresponding
  30 + to overlay planes.
  31 +
  32 + Stores the x,y overlay position on the display in pixels. The
  33 + position format is `[0-9]+,[0-9]+'.
  34 +
  35 +What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3
  36 +Date: May 2012
  37 +Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
  38 +Description:
  39 + This file is only available on fb[0-9] devices corresponding
  40 + to overlay planes.
  41 +
  42 + Stores the raster operation (ROP3) for the overlay. Values
  43 + range from 0 to 255. The value is ignored if the mode is not
  44 + set to ROP3.
20 Documentation/ABI/testing/sysfs-devices-system-xen_cpu
... ... @@ -0,0 +1,20 @@
  1 +What: /sys/devices/system/xen_cpu/
  2 +Date: May 2012
  3 +Contact: Liu, Jinsong <jinsong.liu@intel.com>
  4 +Description:
  5 + A collection of global/individual Xen physical cpu attributes
  6 +
  7 + Individual physical cpu attributes are contained in
  8 + subdirectories named by the Xen's logical cpu number, e.g.:
  9 + /sys/devices/system/xen_cpu/xen_cpu#/
  10 +
  11 +
  12 +What: /sys/devices/system/xen_cpu/xen_cpu#/online
  13 +Date: May 2012
  14 +Contact: Liu, Jinsong <jinsong.liu@intel.com>
  15 +Description:
  16 + Interface to online/offline Xen physical cpus
  17 +
  18 + When running under Xen platform, it provide user interface
  19 + to online/offline physical cpus, except cpu0 due to several
  20 + logic restrictions and assumptions.
38 Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
... ... @@ -0,0 +1,38 @@
  1 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_to_select
  2 +Date: July 2011
  3 +Contact: linux-input@vger.kernel.org
  4 +Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be
  5 + is being controlled by press_speed.
  6 + Values are 0 or 1.
  7 +
  8 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging
  9 +Date: July 2011
  10 +Contact: linux-input@vger.kernel.org
  11 +Description: If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.
  12 + Values are 0 or 1.
  13 +
  14 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select
  15 +Date: July 2011
  16 +Contact: linux-input@vger.kernel.org
  17 +Description: For details regarding this setting please refer to http://www.pc.ibm.com/ww/healthycomputing/trkpntb.html
  18 + Values are 0 or 1.
  19 +
  20 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/select_right
  21 +Date: July 2011
  22 +Contact: linux-input@vger.kernel.org
  23 +Description: This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate
  24 + a left or right mouse button click.
  25 + Values are 0 or 1.
  26 +
  27 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity
  28 +Date: July 2011
  29 +Contact: linux-input@vger.kernel.org
  30 +Description: This file contains the trackpoint sensitivity.
  31 + Values are decimal integers from 1 (lowest sensitivity) to 255 (highest sensitivity).
  32 +
  33 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_speed
  34 +Date: July 2011
  35 +Contact: linux-input@vger.kernel.org
  36 +Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.
  37 + Values are decimal integers from 1 (slowest) to 255 (fastest).
  38 +
77 Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
... ... @@ -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. buttons holds informations about button layout.
  7 + When written, this file lets one write the respective profile
  8 + buttons to the mouse. The data has to be 47 bytes long.
  9 + The mouse will reject invalid data.
  10 + Which profile to write is determined by the profile number
  11 + contained in the data.
  12 + Before reading this file, control has to be written to select
  13 + which profile to read.
  14 +Users: http://roccat.sourceforge.net
  15 +
  16 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
  17 +Date: Mai 2012
  18 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  19 +Description: When written, this file lets one select which data from which
  20 + profile will be read next. The data has to be 3 bytes long.
  21 + This file is writeonly.
  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>/savu/roccatsavu<minor>/general
  25 +Date: Mai 2012
  26 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  27 +Description: The mouse can store 5 profiles which can be switched by the
  28 + press of a button. A profile is split into general settings and
  29 + button settings. profile holds informations like resolution, sensitivity
  30 + and light effects.
  31 + When written, this file lets one write the respective profile
  32 + settings back to the mouse. The data has to be 43 bytes long.
  33 + The mouse will reject invalid data.
  34 + Which profile to write is determined by the profile number
  35 + contained in the data.
  36 + This file is writeonly.
  37 +Users: http://roccat.sourceforge.net
  38 +
  39 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
  40 +Date: Mai 2012
  41 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  42 +Description: When read, this file returns general data like firmware version.
  43 + The data is 8 bytes long.
  44 + This file is readonly.
  45 +Users: http://roccat.sourceforge.net
  46 +
  47 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
  48 +Date: Mai 2012
  49 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  50 +Description: When written, this file lets one store macros with max 500
  51 + keystrokes for a specific button for a specific profile.
  52 + Button and profile numbers are included in written data.
  53 + The data has to be 2083 bytes long.
  54 + Before reading this file, control has to be written to select
  55 + which profile and key to read.
  56 +Users: http://roccat.sourceforge.net
  57 +
  58 +What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
  59 +Date: Mai 2012
  60 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  61 +Description: The mouse can store 5 profiles which can be switched by the
  62 + press of a button. profile holds number of actual profile.
  63 + This value is persistent, so its value determines the profile
  64 + that's active when the mouse is powered on next time.
  65 + When written, the mouse activates the set profile immediately.
  66 + The data has to be 3 bytes long.
  67 + The mouse will reject invalid data.
  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>/savu/roccatsavu<minor>/sensor
  71 +Date: July 2012
  72 +Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
  73 +Description: The mouse has a Avago ADNS-3090 sensor.
  74 + This file allows reading and writing of the mouse sensors registers.
  75 + The data has to be 4 bytes long.
  76 +Users: http://roccat.sourceforge.net
  77 +
14 Documentation/ABI/testing/sysfs-kernel-iommu_groups
... ... @@ -0,0 +1,14 @@
  1 +What: /sys/kernel/iommu_groups/
  2 +Date: May 2012
  3 +KernelVersion: v3.5
  4 +Contact: Alex Williamson <alex.williamson@redhat.com>
  5 +Description: /sys/kernel/iommu_groups/ contains a number of sub-
  6 + directories, each representing an IOMMU group. The
  7 + name of the sub-directory matches the iommu_group_id()
  8 + for the group, which is an integer value. Within each
  9 + subdirectory is another directory named "devices" with
  10 + links to the sysfs devices contained in this group.
  11 + The group directory also optionally contains a "name"
  12 + file if the IOMMU driver has chosen to register a more
  13 + common name for the group.
  14 +Users:
7 Documentation/ABI/testing/sysfs-platform-asus-wmi
@@ -29,3 +29,10 @@ KernelVersion: 2.6.39
29 29 Contact: "Corentin Chary" <corentincj@iksaif.net>
30 30 Description:
31 31 Control the card touchpad. 1 means on, 0 means off.
  32 +
  33 +What: /sys/devices/platform/<platform>/lid_resume
  34 +Date: May 2012
  35 +KernelVersion: 3.5
  36 +Contact: "AceLan Kao" <acelan.kao@canonical.com>
  37 +Description:
  38 + Resume on lid open. 1 means on, 0 means off.
13 Documentation/ABI/testing/sysfs-power
@@ -231,3 +231,16 @@ Description:
231 231 Reads from this file return a string consisting of the names of
232 232 wakeup sources created with the help of /sys/power/wake_lock
233 233