History

Merge tag 'v4.4-rc2' into drm-intel-next-queued

Linux 4.4-rc2 Backmerge to get at commit 1b0e3a049efe471c399674fd954500ce97438d30 Author: Imre Deak <imre.deak@intel.com> Date: Thu Nov 5 23:04:11 2015 +0200 drm/i915/skl: disable display side power well support for now so that we can proplery re-eanble skl power wells in -next. Conflicts are just adjacent lines changed, except for intel_fbdev.c where we need to interleave the changs. Nothing nefarious.

Daniel Vetter committed 10 years ago

Commit 92907cb2 parents 15fbfcc 1ec21839857 files · +471008 −237658Browse files

Unified · Split

3116 files
  1. .mailmap +1 −0
  2. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo +0 −0
  3. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku +0 −0
  4. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus +98 −1
  5. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure +0 −0
  6. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus +50 −0
  7. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua +0 −0
  8. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra +50 −0
  9. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos +0 −0
  10. Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu +0 −0
  11. Documentation/ABI/stable/sysfs-class-tpm +2 −2
  12. Documentation/ABI/stable/sysfs-firmware-opal-elog +1 −1
  13. Documentation/ABI/testing/configfs-stp-policy +48 −0
  14. Documentation/ABI/testing/sysfs-block +7 −0
  15. Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x +76 −7
  16. Documentation/ABI/testing/sysfs-bus-iio +32 −0
  17. Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 +43 −0
  18. Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x +7 −0
  19. Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc100x +9 −0
  20. Documentation/ABI/testing/sysfs-bus-iio-meas-spec +8 −0
  21. Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs +22 −0
  22. Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth +49 −0
  23. Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc +33 −0
  24. Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti +24 −0
  25. Documentation/ABI/testing/sysfs-bus-intel_th-output-devices +13 −0
  26. Documentation/ABI/testing/sysfs-bus-mei +7 −0
  27. Documentation/ABI/testing/sysfs-bus-usb +20 −0
  28. Documentation/ABI/testing/sysfs-class-fpga-manager +37 −0
  29. Documentation/ABI/testing/sysfs-class-mic.txt +19 −10
  30. Documentation/ABI/testing/sysfs-class-power +58 −0
  31. Documentation/ABI/testing/sysfs-class-stm +14 −0
  32. Documentation/ABI/testing/sysfs-class-stm_source +11 −0
  33. Documentation/ABI/testing/sysfs-driver-hid-corsair +15 −0
  34. Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus +0 −96
  35. Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus +0 −49
  36. Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra +0 −49
  37. Documentation/ABI/testing/sysfs-driver-ppi +12 −7
  38. Documentation/ABI/testing/sysfs-driver-st +12 −0
  39. Documentation/ABI/testing/sysfs-fs-f2fs +12 −0
  40. Documentation/ABI/testing/sysfs-power +12 −0
  41. Documentation/Changes +2 −1
  42. Documentation/DMA-API-HOWTO.txt +5 −0
  43. Documentation/DMA-API.txt +3 −16
  44. Documentation/DocBook/.gitignore +2 −0
  45. Documentation/DocBook/80211.tmpl +3 −2
  46. Documentation/DocBook/Makefile +7 −1
  47. Documentation/DocBook/alsa-driver-api.tmpl +2 −0
  48. Documentation/DocBook/device-drivers.tmpl +76 −5
  49. Documentation/DocBook/gpu.tmpl +101 −93
  50. Documentation/DocBook/iio.tmpl +1 −1
  51. Documentation/DocBook/media/dvb/dvbapi.xml +0 −3
  52. Documentation/DocBook/media/dvb/kdapi.xml +0 −2309
  53. Documentation/DocBook/media/v4l/biblio.xml +18 −0
  54. Documentation/DocBook/media/v4l/compat.xml +20 −0
  55. Documentation/DocBook/media/v4l/controls.xml +14 −0
  56. Documentation/DocBook/media/v4l/dev-sdr.xml +22 −10
  57. Documentation/DocBook/media/v4l/io.xml +8 −2
  58. Documentation/DocBook/media/v4l/pixfmt.xml +110 −1
  59. Documentation/DocBook/media/v4l/v4l2.xml +11 −2
  60. Documentation/DocBook/media/v4l/vidioc-encoder-cmd.xml +1 −1
  61. Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml +7 −0
  62. Documentation/DocBook/media/v4l/vidioc-g-fmt.xml +1 −1
  63. Documentation/DocBook/media/v4l/vidioc-g-modulator.xml +13 −1
  64. Documentation/DocBook/media/v4l/vidioc-g-tuner.xml +16 −0
  65. Documentation/DocBook/media/v4l/vidioc-querycap.xml +6 −0
  66. Documentation/DocBook/media/v4l/vidioc-queryctrl.xml +16 −5
  67. Documentation/DocBook/media_api.tmpl +1 −1
  68. Documentation/DocBook/writing-an-alsa-driver.tmpl +2 −17
  69. Documentation/IPMI.txt +5 −2
  70. Documentation/IRQ-domain.txt +4 −4
  71. Documentation/RCU/stallwarn.txt +7 −0
  72. Documentation/RCU/torture.txt +13 −26
  73. Documentation/RCU/trace.txt +16 −16
  74. Documentation/RCU/whatisRCU.txt +3 −3
  75. Documentation/SubmittingPatches +18 −5
  76. Documentation/acpi/enumeration.txt +8 −3
  77. Documentation/acpi/i2c-muxes.txt +58 −0
  78. Documentation/arm/OMAP/README +7 −0
  79. Documentation/arm/SA1100/Victor +0 −16
  80. Documentation/arm/Samsung/Bootloader-interface.txt +3 −2
  81. Documentation/arm/keystone/knav-qmss.txt +56 −0
  82. Documentation/arm/memory.txt +1 −1
  83. Documentation/arm/sunxi/README +1 −1
  84. Documentation/arm/uefi.txt +0 −4
  85. Documentation/arm64/booting.txt +16 −2
  86. Documentation/atomic_ops.txt +4 −0
  87. Documentation/block/pr.txt +119 −0
  88. Documentation/blockdev/zram.txt +40 −4
  89. Documentation/cgroups/blkio-controller.txt +1 −1
  90. Documentation/cgroups/cgroups.txt +4 −0
  91. Documentation/cgroups/freezer-subsystem.txt +1 −1
  92. Documentation/cgroups/unified-hierarchy.txt +15 −12
  93. Documentation/crypto/asymmetric-keys.txt +14 −13
  94. Documentation/device-mapper/delay.txt +1 −0
  95. Documentation/device-mapper/snapshot.txt +7 −3
  96. Documentation/devicetree/bindings/arm/amlogic.txt +8 −2
  97. Documentation/devicetree/bindings/arm/apm/scu.txt +17 −0
  98. Documentation/devicetree/bindings/arm/arm,scpi.txt +188 −0
  99. Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt +160 −2
  100. Documentation/devicetree/bindings/arm/bcm/brcm,nsp.txt +34 −0
  101. Documentation/devicetree/bindings/arm/coherency-fabric.txt +5 −0
  102. Documentation/devicetree/bindings/arm/cpus.txt +2 −0
  103. Documentation/devicetree/bindings/arm/fsl.txt +12 −4
  104. Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt +21 −0
  105. Documentation/devicetree/bindings/arm/keystone/keystone.txt +17 −3
  106. Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt +22 −0
  107. Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt +22 −0
  108. Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt +22 −0
  109. Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt +22 −0
  110. Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt +22 −0
  111. Documentation/devicetree/bindings/arm/mvebu-cpu-config.txt +20 −0
  112. Documentation/devicetree/bindings/arm/pmu.txt +3 −0
  113. Documentation/devicetree/bindings/arm/psci.txt +6 −0
  114. Documentation/devicetree/bindings/arm/rockchip.txt +11 −0
  115. Documentation/devicetree/bindings/arm/samsung-boards.txt +0 −27
  116. Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt +69 −0
  117. Documentation/devicetree/bindings/arm/shmobile.txt +4 −6
  118. Documentation/devicetree/bindings/arm/sunxi.txt +1 −0
  119. Documentation/devicetree/bindings/arm/tegra/nvidia,nvec.txt +0 −0
  120. Documentation/devicetree/bindings/arm/twd.txt +5 −0
  121. Documentation/devicetree/bindings/arm/uniphier/cache-uniphier.txt +60 −0
  122. Documentation/devicetree/bindings/ata/ahci-fsl-qoriq.txt +21 −0
  123. Documentation/devicetree/bindings/ata/ahci-platform.txt +0 −2
  124. Documentation/devicetree/bindings/board/fsl-board.txt +12 −2
  125. Documentation/devicetree/bindings/bus/sunxi-rsb.txt +47 −0
  126. Documentation/devicetree/bindings/chosen.txt +8 −0
  127. Documentation/devicetree/bindings/clock/at91-clock.txt +35 −0
  128. Documentation/devicetree/bindings/clock/brcm,bcm2835-cprman.txt +45 −0
  129. Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt +78 −0
  130. Documentation/devicetree/bindings/clock/qcom,gcc.txt +4 −0
  131. Documentation/devicetree/bindings/clock/qcom,mmcc.txt +4 −0
  132. Documentation/devicetree/bindings/clock/qoriq-clock.txt +50 −11
  133. Documentation/devicetree/bindings/clock/renesas,cpg-div6-clocks.txt +1 −1
  134. Documentation/devicetree/bindings/clock/renesas,cpg-mssr.txt +69 −0
  135. Documentation/devicetree/bindings/clock/silabs,si514.txt +24 −0
  136. Documentation/devicetree/bindings/clock/st/st,clkgen-pll.txt +1 −0
  137. Documentation/devicetree/bindings/crypto/fsl-sec4.txt +2 −2
  138. Documentation/devicetree/bindings/display/arm,pl11x.txt +0 −0
  139. Documentation/devicetree/bindings/display/armada/marvell,dove-lcd.txt +0 −0
  140. Documentation/devicetree/bindings/display/atmel,lcdc.txt +0 −0
  141. Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt +0 −0
  142. Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt +65 −0
  143. Documentation/devicetree/bindings/display/bridge/adi,adv7123.txt +0 −0
  144. Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt +0 −0
  145. Documentation/devicetree/bindings/display/bridge/dw_hdmi.txt +2 −2
  146. Documentation/devicetree/bindings/display/bridge/ps8622.txt +0 −0
  147. Documentation/devicetree/bindings/display/bridge/ptn3460.txt +0 −0
  148. Documentation/devicetree/bindings/display/bridge/tda998x.txt +0 −0
  149. Documentation/devicetree/bindings/display/bridge/thine,thc63lvdm83d.txt +0 −0
  150. Documentation/devicetree/bindings/display/cirrus,clps711x-fb.txt +1 −1
  151. Documentation/devicetree/bindings/display/connector/analog-tv-connector.txt +0 −0
  152. Documentation/devicetree/bindings/display/connector/dvi-connector.txt +0 −0
  153. Documentation/devicetree/bindings/display/connector/hdmi-connector.txt +0 −0
  154. Documentation/devicetree/bindings/display/connector/vga-connector.txt +0 −0
  155. Documentation/devicetree/bindings/display/exynos/exynos-mic.txt +0 −0
  156. Documentation/devicetree/bindings/display/exynos/exynos5433-decon.txt +0 −0
  157. Documentation/devicetree/bindings/display/exynos/exynos7-decon.txt +1 −1
  158. Documentation/devicetree/bindings/display/exynos/exynos_dp.txt +1 −1
  159. Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt +1 −1
  160. Documentation/devicetree/bindings/display/exynos/exynos_hdmi.txt +0 −0
  161. Documentation/devicetree/bindings/display/exynos/exynos_hdmiddc.txt +0 −0
  162. Documentation/devicetree/bindings/display/exynos/exynos_hdmiphy.txt +0 −0
  163. Documentation/devicetree/bindings/display/exynos/exynos_mixer.txt +0 −0
  164. Documentation/devicetree/bindings/display/exynos/samsung-fimd.txt +1 −1
  165. Documentation/devicetree/bindings/display/fsl,dcu.txt +0 −0
  166. Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt +1 −1
  167. Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt +0 −0
  168. Documentation/devicetree/bindings/display/imx/hdmi.txt +0 −0
  169. Documentation/devicetree/bindings/display/imx/ldb.txt +1 −1
  170. Documentation/devicetree/bindings/display/marvell,pxa2xx-lcdc.txt +34 −0
  171. Documentation/devicetree/bindings/display/mipi-dsi-bus.txt +0 −0
  172. Documentation/devicetree/bindings/display/msm/dsi.txt +1 −1
  173. Documentation/devicetree/bindings/display/msm/edp.txt +0 −0
  174. Documentation/devicetree/bindings/display/msm/gpu.txt +0 −0
  175. Documentation/devicetree/bindings/display/msm/hdmi.txt +3 −0
  176. Documentation/devicetree/bindings/display/msm/mdp.txt +2 −1
  177. Documentation/devicetree/bindings/display/mxsfb.txt +0 −0
  178. Documentation/devicetree/bindings/display/panel/ampire,am800480r3tmqwa1h.txt +0 −0
  179. Documentation/devicetree/bindings/display/panel/auo,b080uan01.txt +0 −0
  180. Documentation/devicetree/bindings/display/panel/auo,b101aw03.txt +0 −0
  181. Documentation/devicetree/bindings/display/panel/auo,b101ean01.txt +0 −0
  182. Documentation/devicetree/bindings/display/panel/auo,b101xtn01.txt +0 −0
  183. Documentation/devicetree/bindings/display/panel/auo,b116xw03.txt +0 −0
  184. Documentation/devicetree/bindings/display/panel/auo,b133htn01.txt +0 −0
  185. Documentation/devicetree/bindings/display/panel/auo,b133xtn01.txt +0 −0
  186. Documentation/devicetree/bindings/display/panel/avic,tm070ddh03.txt +0 −0
  187. Documentation/devicetree/bindings/display/panel/chunghwa,claa101wa01a.txt +0 −0
  188. Documentation/devicetree/bindings/display/panel/chunghwa,claa101wb03.txt +0 −0
  189. Documentation/devicetree/bindings/display/panel/display-timing.txt +0 −0
  190. Documentation/devicetree/bindings/display/panel/edt,et057090dhu.txt +0 −0
  191. Documentation/devicetree/bindings/display/panel/edt,et070080dh6.txt +0 −0
  192. Documentation/devicetree/bindings/display/panel/edt,etm0700g0dh6.txt +0 −0
  193. Documentation/devicetree/bindings/display/panel/foxlink,fl500wvr00-a0t.txt +0 −0
  194. Documentation/devicetree/bindings/display/panel/giantplus,gpg482739qs5.txt +0 −0
  195. Documentation/devicetree/bindings/display/panel/hannstar,hsd070pww1.txt +0 −0
  196. Documentation/devicetree/bindings/display/panel/hannstar,hsd100pxn1.txt +0 −0
  197. Documentation/devicetree/bindings/display/panel/hit,tx23d38vm0caa.txt +0 −0
  198. Documentation/devicetree/bindings/display/panel/innolux,at043tn24.txt +0 −0
  199. Documentation/devicetree/bindings/display/panel/innolux,g121i1-l01.txt +0 −0
  200. Documentation/devicetree/bindings/display/panel/innolux,n116bge.txt +0 −0
  201. Documentation/devicetree/bindings/display/panel/innolux,n156bge-l21.txt +0 −0
  202. Documentation/devicetree/bindings/display/panel/innolux,zj070na-01p.txt +0 −0
  203. Documentation/devicetree/bindings/display/panel/lg,lb070wv8.txt +0 −0
  204. Documentation/devicetree/bindings/display/panel/lg,ld070wx3-sl01.txt +0 −0
  205. Documentation/devicetree/bindings/display/panel/lg,lg4573.txt +0 −0
  206. Documentation/devicetree/bindings/display/panel/lg,lh500wx1-sd03.txt +0 −0
  207. Documentation/devicetree/bindings/display/panel/lg,lp129qe.txt +0 −0
  208. Documentation/devicetree/bindings/display/panel/lgphilips,lb035q02.txt +0 −0
  209. Documentation/devicetree/bindings/display/panel/nec,nl4827hc19-05b.txt +0 −0
  210. Documentation/devicetree/bindings/display/panel/okaya,rs800480t-7x0gp.txt +0 −0
  211. Documentation/devicetree/bindings/display/panel/ortustech,com43h4m85ulc.txt +0 −0
  212. Documentation/devicetree/bindings/display/panel/panasonic,vvx10f004b00.txt +0 −0
  213. Documentation/devicetree/bindings/display/panel/panel-dpi.txt +1 −1
  214. Documentation/devicetree/bindings/display/panel/panel-dsi-cm.txt +0 −0
  215. Documentation/devicetree/bindings/display/panel/samsung,ld9040.txt +1 −1
  216. Documentation/devicetree/bindings/display/panel/samsung,ltn101nt05.txt +0 −0
  217. Documentation/devicetree/bindings/display/panel/samsung,ltn140at29-301.txt +0 −0
  218. Documentation/devicetree/bindings/display/panel/samsung,s6e8aa0.txt +1 −1
  219. Documentation/devicetree/bindings/display/panel/sharp,lq101r1sx01.txt +0 −0
  220. Documentation/devicetree/bindings/display/panel/sharp,ls037v7dw01.txt +0 −0
  221. Documentation/devicetree/bindings/display/panel/shelly,sca07010-bfn-lnn.txt +0 −0
  222. Documentation/devicetree/bindings/display/panel/simple-panel.txt +0 −0
  223. Documentation/devicetree/bindings/display/panel/sony,acx565akm.txt +0 −0
  224. Documentation/devicetree/bindings/display/panel/toppoly,td028ttec1.txt +0 −0
  225. Documentation/devicetree/bindings/display/panel/tpo,td043mtea1.txt +0 −0
  226. Documentation/devicetree/bindings/display/renesas,du.txt +9 −5
  227. Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt +0 −0
  228. Documentation/devicetree/bindings/display/rockchip/rockchip-drm.txt +1 −1
  229. Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt +0 −0
  230. Documentation/devicetree/bindings/display/simple-framebuffer-sunxi.txt +0 −0
  231. Documentation/devicetree/bindings/display/simple-framebuffer.txt +0 −0
  232. Documentation/devicetree/bindings/display/sm501fb.txt +0 −0
  233. Documentation/devicetree/bindings/display/ssd1289fb.txt +0 −0
  234. Documentation/devicetree/bindings/display/ssd1307fb.txt +2 −1
  235. Documentation/devicetree/bindings/display/st,stih4xx.txt +2 −2
  236. Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.txt +0 −0
  237. Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt +1 −1
  238. Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt +1 −1
  239. Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt +0 −0
  240. Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt +1 −1
  241. Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt +1 −1
  242. Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt +1 −1
  243. Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt +1 −1
  244. Documentation/devicetree/bindings/display/ti/ti,opa362.txt +0 −0
  245. Documentation/devicetree/bindings/display/ti/ti,tfp410.txt +0 −0
  246. Documentation/devicetree/bindings/display/ti/ti,tpd12s015.txt +0 −0
  247. Documentation/devicetree/bindings/display/tilcdc/panel.txt +1 −1
  248. Documentation/devicetree/bindings/display/tilcdc/tfp410.txt +0 −0
  249. Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt +0 −0
  250. Documentation/devicetree/bindings/display/via,vt8500-fb.txt +0 −0
  251. Documentation/devicetree/bindings/display/wm,prizm-ge-rops.txt +0 −0
  252. Documentation/devicetree/bindings/display/wm,wm8505-fb.txt +0 −0
  253. Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt +13 −2
  254. Documentation/devicetree/bindings/dma/ti-edma.txt +116 −1
  255. Documentation/devicetree/bindings/edac/apm-xgene-edac.txt +23 −0
  256. Documentation/devicetree/bindings/eeprom/at25.txt +0 −0
  257. Documentation/devicetree/bindings/eeprom/eeprom.txt +0 −0
  258. Documentation/devicetree/bindings/extcon/extcon-arizona.txt +15 −0
  259. Documentation/devicetree/bindings/fpga/altera-socfpga-fpga-mgr.txt +1 −1
  260. Documentation/devicetree/bindings/fpga/xilinx-zynq-fpga-mgr.txt +19 −0
  261. Documentation/devicetree/bindings/gpio/gpio-mpc8xxx.txt +2 −2
  262. Documentation/devicetree/bindings/gpio/gpio-msm.txt +0 −26
  263. Documentation/devicetree/bindings/gpio/gpio-pca953x.txt +1 −0
  264. Documentation/devicetree/bindings/gpio/gpio-zynq.txt +9 −0
  265. Documentation/devicetree/bindings/gpio/gpio.txt +39 −2
  266. Documentation/devicetree/bindings/gpio/netxbig-gpio-ext.txt +22 −0
  267. Documentation/devicetree/bindings/hwmon/ina209.txt +0 −18
  268. Documentation/devicetree/bindings/hwmon/ina2xx.txt +1 −0
  269. Documentation/devicetree/bindings/hwmon/pwm-fan.txt +27 −2
  270. Documentation/devicetree/bindings/i2c/i2c-davinci.txt +3 −3
  271. Documentation/devicetree/bindings/i2c/i2c-imx.txt +9 −0
  272. Documentation/devicetree/bindings/i2c/i2c-rcar.txt +1 −0
  273. Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt +1 −0
  274. Documentation/devicetree/bindings/i2c/i2c-uniphier-f.txt +25 −0
  275. Documentation/devicetree/bindings/i2c/i2c-uniphier.txt +25 −0
  276. Documentation/devicetree/bindings/i2c/trivial-devices.txt +2 −1
  277. Documentation/devicetree/bindings/iio/accel/lis302.txt +0 −0
  278. Documentation/devicetree/bindings/iio/accel/mma8452.txt +24 −0
  279. Documentation/devicetree/bindings/iio/adc/hi8435.txt +21 −0
  280. Documentation/devicetree/bindings/iio/dac/ti,dac7512.txt +0 −0
  281. Documentation/devicetree/bindings/iio/light/apds9960.txt +22 −0
  282. Documentation/devicetree/bindings/iio/light/us5182d.txt +34 −0
  283. Documentation/devicetree/bindings/iio/pressure/bmp085.txt +0 −0
  284. Documentation/devicetree/bindings/input/ads7846.txt +2 −1
  285. Documentation/devicetree/bindings/input/cypress,cyapa.txt +1 −1
  286. Documentation/devicetree/bindings/input/da9062-onkey.txt +32 −0
  287. Documentation/devicetree/bindings/input/gpio-keys-polled.txt +9 −1
  288. Documentation/devicetree/bindings/input/gpio-keys.txt +1 −0
  289. Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt +1 −0
  290. Documentation/devicetree/bindings/input/hid-over-i2c.txt +0 −0
  291. Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt +2 −1
  292. Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt +1 −0
  293. Documentation/devicetree/bindings/input/rotary-encoder.txt +10 −0
  294. Documentation/devicetree/bindings/input/samsung-keypad.txt +2 −1
  295. Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt +5 −3
  296. Documentation/devicetree/bindings/input/touchscreen/focaltech-ft6236.txt +35 −0
  297. Documentation/devicetree/bindings/input/touchscreen/tsc2005.txt +28 −6
  298. Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt +0 −0
  299. Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt +20 −4
  300. Documentation/devicetree/bindings/interrupt-controller/arm,versatile-fpga-irq.txt +0 −0
  301. Documentation/devicetree/bindings/interrupt-controller/arm,vic.txt +0 −0
  302. Documentation/devicetree/bindings/interrupt-controller/axis,crisv32-intc.txt +0 −0
  303. Documentation/devicetree/bindings/interrupt-controller/img,meta-intc.txt +0 −0
  304. Documentation/devicetree/bindings/interrupt-controller/img,pdc-intc.txt +0 −0
  305. Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-ioapic.txt +0 −0
  306. Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt +0 −0
  307. Documentation/devicetree/bindings/interrupt-controller/mrvl,intc.txt +0 −0
  308. Documentation/devicetree/bindings/interrupt-controller/nxp,lpc3220-mic.txt +0 −0
  309. Documentation/devicetree/bindings/interrupt-controller/open-pic.txt +0 −0
  310. Documentation/devicetree/bindings/interrupt-controller/qca,ath79-misc-intc.txt +18 −2
  311. Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt +1 −0
  312. Documentation/devicetree/bindings/interrupt-controller/samsung,exynos4210-combiner.txt +0 −0
  313. Documentation/devicetree/bindings/interrupt-controller/snps,arc700-intc.txt +0 −0
  314. Documentation/devicetree/bindings/interrupt-controller/snps,archs-idu-intc.txt +0 −0
  315. Documentation/devicetree/bindings/interrupt-controller/snps,archs-intc.txt +0 −0
  316. Documentation/devicetree/bindings/interrupt-controller/st,spear3xx-shirq.txt +0 −0
  317. Documentation/devicetree/bindings/interrupt-controller/ti,c64x+megamod-pic.txt +0 −0
  318. Documentation/devicetree/bindings/interrupt-controller/ti,cp-intc.txt +0 −0
  319. Documentation/devicetree/bindings/interrupt-controller/ti,omap2-intc.txt +0 −0
  320. Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.txt +0 −0
  321. Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt +19 −0
  322. Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt +1 −1
  323. Documentation/devicetree/bindings/iommu/ti,omap-iommu.txt +27 −0
  324. Documentation/devicetree/bindings/leds/backlight/88pm860x.txt +0 −0
  325. Documentation/devicetree/bindings/leds/backlight/gpio-backlight.txt +0 −0
  326. Documentation/devicetree/bindings/leds/backlight/lp855x.txt +0 −0
  327. Documentation/devicetree/bindings/leds/backlight/max8925-backlight.txt +0 −0
  328. Documentation/devicetree/bindings/leds/backlight/pm8941-wled.txt +2 −0
  329. Documentation/devicetree/bindings/leds/backlight/pwm-backlight.txt +0 −0
  330. Documentation/devicetree/bindings/leds/backlight/sky81452-backlight.txt +0 −0
  331. Documentation/devicetree/bindings/leds/backlight/tps65217-backlight.txt +0 −0
  332. Documentation/devicetree/bindings/leds/leds-aat1290.txt +4 −4
  333. Documentation/devicetree/bindings/leds/leds-bcm6328.txt +10 −0
  334. Documentation/devicetree/bindings/leds/leds-netxbig.txt +92 −0
  335. Documentation/devicetree/bindings/mailbox/omap-mailbox.txt +8 −0
  336. Documentation/devicetree/bindings/mailbox/sti-mailbox.txt +51 −0
  337. Documentation/devicetree/bindings/media/exynos-jpeg-codec.txt +2 −1
  338. Documentation/devicetree/bindings/memory-controllers/arm,pl172.txt +5 −3
  339. Documentation/devicetree/bindings/memory-controllers/calxeda-ddr-ctrlr.txt +0 −0
  340. Documentation/devicetree/bindings/memory-controllers/renesas-memory-controllers.txt +3 −3
  341. Documentation/devicetree/bindings/mfd/arizona.txt +3 −12
  342. Documentation/devicetree/bindings/mfd/atmel-flexcom.txt +63 −0
  343. Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt +1 −1
  344. Documentation/devicetree/bindings/mfd/axp20x.txt +2 −2
  345. Documentation/devicetree/bindings/mfd/cros-ec.txt +4 −0
  346. Documentation/devicetree/bindings/mfd/da9150.txt +26 −7
  347. Documentation/devicetree/bindings/mfd/s2mps11.txt +21 −7
  348. Documentation/devicetree/bindings/mfd/sky81452.txt +1 −1
  349. Documentation/devicetree/bindings/mfd/tc3589x.txt +1 −0
  350. Documentation/devicetree/bindings/mips/img/xilfpga.txt +83 −0
  351. Documentation/devicetree/bindings/misc/sram.txt +16 −0
  352. Documentation/devicetree/bindings/mmc/fsl-esdhc.txt +2 −0
  353. Documentation/devicetree/bindings/mmc/mmc.txt +4 −2
  354. Documentation/devicetree/bindings/mmc/mtk-sd.txt +10 −1
  355. Documentation/devicetree/bindings/mmc/renesas,mmcif.txt +3 −2
  356. Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt +13 −0
  357. Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt +25 −0
  358. Documentation/devicetree/bindings/mtd/fsmc-nand.txt +6 −0
  359. Documentation/devicetree/bindings/mtd/partition.txt +42 −29
  360. Documentation/devicetree/bindings/mtd/vf610-nfc.txt +59 −0
  361. Documentation/devicetree/bindings/net/apm-xgene-enet.txt +10 −0
  362. Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt +23 −0
  363. Documentation/devicetree/bindings/net/can/sun4i_can.txt +36 −0
  364. Documentation/devicetree/bindings/net/cpsw.txt +13 −0
  365. Documentation/devicetree/bindings/net/fsl-tsec-phy.txt +4 −0
  366. Documentation/devicetree/bindings/net/hisilicon-hip04-net.txt +2 −2
  367. Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt +49 −0
  368. Documentation/devicetree/bindings/net/hisilicon-hns-mdio.txt +22 −0
  369. Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt +47 −0
  370. Documentation/devicetree/bindings/net/ieee802154/mrf24j40.txt +20 −0
  371. Documentation/devicetree/bindings/net/maxim,ds26522.txt +13 −0
  372. Documentation/devicetree/bindings/net/nfc/nfcmrvl.txt +59 −2
  373. Documentation/devicetree/bindings/net/nfc/st-nci-i2c.txt +7 −0
  374. Documentation/devicetree/bindings/net/nfc/st-nci-spi.txt +8 −1
  375. Documentation/devicetree/bindings/net/renesas,ravb.txt +62 −7
  376. Documentation/devicetree/bindings/net/smsc-lan87xx.txt +24 −0
  377. Documentation/devicetree/bindings/nvmem/imx-ocotp.txt +20 −0
  378. Documentation/devicetree/bindings/nvmem/mxs-ocotp.txt +25 −0
  379. Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt +38 −0
  380. Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt +19 −0
  381. Documentation/devicetree/bindings/pci/altera-pcie-msi.txt +28 −0
  382. Documentation/devicetree/bindings/pci/altera-pcie.txt +49 −0
  383. Documentation/devicetree/bindings/pci/arm,juno-r1-pcie.txt +10 −0
  384. Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt +20 −0
  385. Documentation/devicetree/bindings/pci/designware-pcie.txt +7 −5
  386. Documentation/devicetree/bindings/pci/hisilicon-pcie.txt +44 −0
  387. Documentation/devicetree/bindings/pci/host-generic-pci.txt +3 −2
  388. Documentation/devicetree/bindings/pci/layerscape-pci.txt +12 −2
  389. Documentation/devicetree/bindings/pci/pci-msi.txt +220 −0
  390. Documentation/devicetree/bindings/pci/pci.txt +2 −2
  391. Documentation/devicetree/bindings/pci/plda,xpressrich3-axi.txt +12 −0
  392. Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt +47 −0
  393. Documentation/devicetree/bindings/phy/calxeda-combophy.txt +0 −0
  394. Documentation/devicetree/bindings/phy/keystone-usb-phy.txt +0 −0
  395. Documentation/devicetree/bindings/phy/mxs-usb-phy.txt +0 −0
  396. Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.txt +0 −0
  397. Documentation/devicetree/bindings/phy/phy-mt65xx-usb.txt +68 −0
  398. Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txt +0 −0
  399. Documentation/devicetree/bindings/phy/samsung-phy.txt +3 −0
  400. Documentation/devicetree/bindings/pinctrl/allwinner,sunxi-pinctrl.txt +1 −0
  401. Documentation/devicetree/bindings/pinctrl/atmel,at91-pio4-pinctrl.txt +90 −0
  402. Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt +4 −1
  403. Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt +11 −5
  404. Documentation/devicetree/bindings/pinctrl/fsl,imx7d-pinctrl.txt +62 −1
  405. Documentation/devicetree/bindings/pinctrl/renesas,pfc-pinctrl.txt +1 −0
  406. Documentation/devicetree/bindings/power/bq24257.txt +48 −5
  407. Documentation/devicetree/bindings/power/da9150-fg.txt +23 −0
  408. Documentation/devicetree/bindings/power/pd-samsung.txt +2 −3
  409. Documentation/devicetree/bindings/power/wakeup-source.txt +71 −0
  410. Documentation/devicetree/bindings/power_supply/axp20x_usb_power.txt +34 −0
  411. Documentation/devicetree/bindings/power_supply/qcom_smbb.txt +131 −0
  412. Documentation/devicetree/bindings/power_supply/tps65217_charger.txt +12 −0
  413. Documentation/devicetree/bindings/powerpc/fsl/mpc512x_lpbfifo.txt +21 −0
  414. Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.txt +20 −0
  415. Documentation/devicetree/bindings/pwm/pwm-berlin.txt +17 −0
  416. Documentation/devicetree/bindings/pwm/pwm-mtk-disp.txt +42 −0
  417. Documentation/devicetree/bindings/pwm/pwm-sun4i.txt +2 −0
  418. Documentation/devicetree/bindings/pwm/renesas,pwm-rcar.txt +26 −0
  419. Documentation/devicetree/bindings/regulator/act8865-regulator.txt +3 −0
  420. Documentation/devicetree/bindings/regulator/anatop-regulator.txt +1 −0
  421. Documentation/devicetree/bindings/regulator/arizona-regulator.txt +17 −0
  422. Documentation/devicetree/bindings/regulator/max77802.txt +24 −1
  423. Documentation/devicetree/bindings/regulator/regulator.txt +1 −0
  424. Documentation/devicetree/bindings/regulator/tps65023.txt +60 −0
  425. Documentation/devicetree/bindings/rng/atmel-trng.txt +0 −0
  426. Documentation/devicetree/bindings/rng/brcm,iproc-rng200.txt +0 −0
  427. Documentation/devicetree/bindings/rng/omap_rng.txt +0 −0
  428. Documentation/devicetree/bindings/rng/samsung,exynos-rng4.txt +17 −0
  429. Documentation/devicetree/bindings/rng/st,rng.txt +15 −0
  430. Documentation/devicetree/bindings/rng/st,stm32-rng.txt +21 −0
  431. Documentation/devicetree/bindings/rng/timeriomem_rng.txt +0 −0
  432. Documentation/devicetree/bindings/rtc/dallas,ds1390.txt +18 −0
  433. Documentation/devicetree/bindings/rtc/isil,isl12057.txt +5 −5
  434. Documentation/devicetree/bindings/rtc/pcf8563.txt +25 −0
  435. Documentation/devicetree/bindings/rtc/rtc-opal.txt +3 −2
  436. Documentation/devicetree/bindings/serial/ingenic,uart.txt +2 −1
  437. Documentation/devicetree/bindings/serial/mrvl,pxa-ssp.txt +0 −1
  438. Documentation/devicetree/bindings/serial/pl011.txt +1 −1
  439. Documentation/devicetree/bindings/serial/qcom,msm-uartdm.txt +6 −0
  440. Documentation/devicetree/bindings/serial/renesas,sci-serial.txt +2 −0
  441. Documentation/devicetree/bindings/serial/snps-dw-apb-uart.txt +3 −0
  442. Documentation/devicetree/bindings/soc/mediatek/scpsys.txt +6 −4
  443. Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt +57 −0
  444. Documentation/devicetree/bindings/soc/rockchip/power_domain.txt +46 −0
  445. Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt +0 −1
  446. Documentation/devicetree/bindings/sound/ak4554.txt +0 −0
  447. Documentation/devicetree/bindings/sound/ak4613.txt +17 −0
  448. Documentation/devicetree/bindings/sound/ak4642.txt +21 −1
  449. Documentation/devicetree/bindings/sound/atmel-classd.txt +52 −0
  450. Documentation/devicetree/bindings/sound/da7213.txt +41 −0
  451. Documentation/devicetree/bindings/sound/da7219.txt +106 −0
  452. Documentation/devicetree/bindings/sound/fsl-asoc-card.txt +6 −4
  453. Documentation/devicetree/bindings/sound/nau8825.txt +102 −0
  454. Documentation/devicetree/bindings/sound/renesas,rsnd.txt +7 −0
  455. Documentation/devicetree/bindings/sound/rockchip-i2s.txt +2 −4
  456. Documentation/devicetree/bindings/sound/rockchip-spdif.txt +40 −0
  457. Documentation/devicetree/bindings/sound/rt5640.txt +6 −3
  458. Documentation/devicetree/bindings/sound/sun4i-codec.txt +27 −0
  459. Documentation/devicetree/bindings/sound/tdm-slot.txt +10 −1
  460. Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt +38 −0
  461. Documentation/devicetree/bindings/spi/sh-msiof.txt +1 −1
  462. Documentation/devicetree/bindings/spi/spi-mt65xx.txt +6 −3
  463. Documentation/devicetree/bindings/thermal/rockchip-thermal.txt +9 −2
  464. Documentation/devicetree/bindings/thermal/ti_soc_thermal.txt +14 −0
  465. Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt +5 −3
  466. Documentation/devicetree/bindings/ufs/ufs-qcom.txt +58 −0
  467. Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt +10 −1
  468. Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt +21 −6
  469. Documentation/devicetree/bindings/usb/dwc3.txt +7 −1
  470. Documentation/devicetree/bindings/usb/renesas_usbhs.txt +1 −0
  471. Documentation/devicetree/bindings/usb/samsung-usbphy.txt +0 −117
  472. Documentation/devicetree/bindings/vendor-prefixes.txt +10 −0
  473. Documentation/devicetree/bindings/w1/omap-hdq.txt +6 −1
  474. Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.txt +19 −0
  475. Documentation/dontdiff +0 −1
  476. Documentation/driver-model/platform.txt +14 −0
  477. Documentation/edac.txt +46 −0
  478. Documentation/email-clients.txt +37 −1
  479. Documentation/features/debug/KASAN/arch-support.txt +1 −1
  480. Documentation/features/vm/THP/arch-support.txt +1 −1
  481. Documentation/features/vm/pte_special/arch-support.txt +1 −1
  482. Documentation/filesystems/Makefile +0 −2
  483. Documentation/filesystems/configfs/Makefile +0 −3
  484. Documentation/filesystems/configfs/configfs.txt +11 −27
  485. Documentation/filesystems/configfs/configfs_example_explicit.c +0 −483
  486. Documentation/filesystems/debugfs.txt +1 −1
  487. Documentation/filesystems/f2fs.txt +2 −1
  488. Documentation/filesystems/gfs2-glocks.txt +3 −3
  489. Documentation/filesystems/nfs/nfsroot.txt +3 −0
  490. Documentation/filesystems/overlayfs.txt +2 −1
  491. Documentation/filesystems/path-lookup.md +1297 −0
  492. Documentation/filesystems/path-lookup.txt +1 −1
  493. Documentation/filesystems/proc.txt +29 −20
  494. Documentation/filesystems/sysfs-tagging.txt +7 −7
  495. Documentation/filesystems/sysfs.txt +5 −4
  496. Documentation/fpga/fpga-mgr.txt +171 −0
  497. Documentation/gpio/board.txt +7 −3
  498. Documentation/gpio/driver.txt +80 −0
  499. Documentation/gpio/sysfs.txt +3 −3
  500. Documentation/hw_random.txt +4 −4
  501. Documentation/hwmon/lm75 +3 −2
  502. Documentation/hwmon/max31790 +37 −0
  503. Documentation/hwmon/scpi-hwmon +33 −0
  504. Documentation/i2c/busses/i2c-i801 +3 −0
  505. Documentation/input/multi-touch-protocol.txt +1 −1
  506. Documentation/input/rotary-encoder.txt +7 −2
  507. Documentation/input/userio.txt +70 −0
  508. Documentation/ioctl/ioctl-number.txt +4 −0
  509. Documentation/kasan.txt +23 −23
  510. Documentation/kbuild/Kconfig.recursion-issue-01 +57 −0
  511. Documentation/kbuild/Kconfig.recursion-issue-02 +63 −0
  512. Documentation/kbuild/Kconfig.select-break +33 −0
  513. Documentation/kbuild/kconfig-language.txt +161 −0
  514. Documentation/kernel-docs.txt +7 −7
  515. Documentation/kernel-parameters.txt +48 −9
  516. Documentation/kselftest.txt +16 −0
  517. Documentation/locking/lockstat.txt +1 −1
  518. Documentation/locking/locktorture.txt +3 −0
  519. Documentation/lockup-watchdogs.txt +3 −2
  520. Documentation/memory-barriers.txt +33 −32
  521. Documentation/mic/mic_overview.txt +18 −13
  522. Documentation/mic/mpssd/mpss +2 −2
  523. Documentation/mic/mpssd/mpssd.c +230 −132
  524. Documentation/mic/mpssd/mpssd.h +1 −0
  525. Documentation/misc-devices/apds990x.txt +1 −1
  526. Documentation/misc-devices/isl29003 +1 −1
  527. Documentation/misc-devices/max6875 +1 −1
  528. Documentation/mmc/mmc-dev-attrs.txt +0 −10
  529. Documentation/networking/can.txt +78 −21
  530. Documentation/networking/filter.txt +3 −3
  531. Documentation/networking/ieee802154.txt +4 −4
  532. Documentation/networking/ip-sysctl.txt +22 −3
  533. Documentation/networking/ipvs-sysctl.txt +10 −0
  534. Documentation/networking/l2tp.txt +2 −5
  535. Documentation/networking/switchdev.txt +44 −21
  536. Documentation/networking/vrf.txt +299 −2
  537. Documentation/nvdimm/nvdimm.txt +28 −21
  538. Documentation/power/pci.txt +38 −13
  539. Documentation/printk-formats.txt +29 −0
  540. Documentation/ptp/testptp.c +1 −0
  541. Documentation/rbtree.txt +1 −1
  542. Documentation/scsi/st.txt +3 −1
  543. Documentation/security/Smack.txt +10 −0
  544. Documentation/security/keys.txt +25 −16
  545. Documentation/serial/driver +9 −1
  546. Documentation/serial/tty.txt +39 −21
  547. Documentation/sound/alsa/hda_codec.txt +0 −322
  548. Documentation/spi/pxa2xx +0 −6
  549. Documentation/sysctl/kernel.txt +12 −0
  550. Documentation/sysctl/vm.txt +1 −1
  551. Documentation/target/tcm_mod_builder.py +0 −17
  552. Documentation/trace/events.txt +18 −0
  553. Documentation/trace/ftrace.txt +23 −0
  554. Documentation/trace/intel_th.txt +99 −0
  555. Documentation/trace/stm.txt +80 −0
  556. Documentation/usb/authorization.txt +31 −0
  557. Documentation/video4linux/CARDLIST.saa7134 +1 −0
  558. Documentation/video4linux/v4l2-pci-skeleton.c +3 −1
  559. Documentation/virtual/kvm/api.txt +49 −7
  560. Documentation/virtual/kvm/arm/vgic-mapped-irqs.txt +187 −0
  561. Documentation/virtual/kvm/devices/arm-vgic.txt +10 −8
  562. Documentation/virtual/kvm/devices/vm.txt +1 −1
  563. Documentation/virtual/kvm/locking.txt +12 −0
  564. Documentation/virtual/kvm/ppc-pv.txt +1 −1
  565. Documentation/vm/balance +8 −6
  566. Documentation/vm/page_migration +12 −15
  567. Documentation/vm/slub.txt +59 −0
  568. Documentation/vm/split_page_table_lock +2 −2
  569. Documentation/vm/transhuge.txt +10 −0
  570. Documentation/vm/unevictable-lru.txt +19 −101
  571. Documentation/w1/masters/omap-hdq +6 −0
  572. Documentation/zh_CN/filesystems/sysfs.txt +1 −1
  573. MAINTAINERS +355 −83
  574. Makefile +14 −8
  575. README +1 −1
  576. arch/alpha/include/asm/atomic.h +4 −4
  577. arch/alpha/include/asm/word-at-a-time.h +2 −0
  578. arch/alpha/include/uapi/asm/mman.h +3 −0
  579. arch/arc/Kconfig +40 −0
  580. arch/arc/Makefile +1 −1
  581. arch/arc/boot/dts/Makefile +4 −2
  582. arch/arc/boot/dts/axc001.dtsi +1 −1
  583. arch/arc/boot/dts/axc003.dtsi +1 −1
  584. arch/arc/boot/dts/axc003_idu.dtsi +1 −1
  585. arch/arc/boot/dts/nsim_hs.dts +10 −2
  586. arch/arc/boot/dts/skeleton.dtsi +1 −1
  587. arch/arc/boot/dts/vdk_axc003.dtsi +1 −1
  588. arch/arc/boot/dts/vdk_axc003_idu.dtsi +1 −1
  589. arch/arc/configs/axs101_defconfig +0 −1
  590. arch/arc/configs/axs103_defconfig +0 −1
  591. arch/arc/configs/axs103_smp_defconfig +0 −1
  592. arch/arc/include/asm/Kbuild +1 −0
  593. arch/arc/include/asm/arcregs.h +3 −3
  594. arch/arc/include/asm/atomic.h +4 −4
  595. arch/arc/include/asm/cache.h +2 −0
  596. arch/arc/include/asm/cacheflush.h +4 −4
  597. arch/arc/include/asm/entry-compact.h +6 −7
  598. arch/arc/include/asm/highmem.h +61 −0
  599. arch/arc/include/asm/hugepage.h +81 −0
  600. arch/arc/include/asm/irq.h +1 −0
  601. arch/arc/include/asm/irqflags-compact.h +15 −1
  602. arch/arc/include/asm/kmap_types.h +18 −0
  603. arch/arc/include/asm/mach_desc.h +2 −8
  604. arch/arc/include/asm/mcip.h +0 −3
  605. arch/arc/include/asm/mmu.h +7 −0
  606. arch/arc/include/asm/page.h +7 −2
  607. arch/arc/include/asm/pgalloc.h +6 −6
  608. arch/arc/include/asm/pgtable.h +47 −41
  609. arch/arc/include/asm/processor.h +6 −5
  610. arch/arc/include/asm/setup.h +7 −0
  611. arch/arc/include/asm/smp.h +7 −0
  612. arch/arc/include/asm/tlbflush.h +5 −0
  613. arch/arc/include/uapi/asm/page.h +4 −7
  614. arch/arc/kernel/entry-arcv2.S +20 −1
  615. arch/arc/kernel/entry-compact.S +48 −24
  616. arch/arc/kernel/entry.S +0 −17
  617. arch/arc/kernel/head.S +27 −22
  618. arch/arc/kernel/intc-compact.c +13 −77
  619. arch/arc/kernel/irq.c +12 −8
  620. arch/arc/kernel/mcip.c +11 −35
  621. arch/arc/kernel/setup.c +2 −5
  622. arch/arc/kernel/smp.c +37 −29
  623. arch/arc/kernel/time.c +0 −3
  624. arch/arc/kernel/vmlinux.lds.S +1 −1
  625. arch/arc/lib/memcpy-archs.S +26 −26
  626. arch/arc/mm/Makefile +1 −0
  627. arch/arc/mm/cache.c +66 −25
  628. arch/arc/mm/fault.c +10 −3
  629. arch/arc/mm/highmem.c +140 −0
  630. arch/arc/mm/init.c +76 −28
  631. arch/arc/mm/tlb.c +191 −43
  632. arch/arc/mm/tlbex.S +39 −16
  633. arch/arc/plat-axs10x/axs10x.c +0 −8
  634. arch/arc/plat-sim/platform.c +0 −5
  635. arch/arm/Kconfig +8 −28
  636. arch/arm/Kconfig.debug +17 −27
  637. arch/arm/boot/dts/Makefile +52 −10
  638. arch/arm/boot/dts/am335x-base0033.dts +24 −24
  639. arch/arm/boot/dts/am335x-bone-common.dtsi +1 −2
  640. arch/arm/boot/dts/am335x-bonegreen.dts +53 −0
  641. arch/arm/boot/dts/am335x-evm.dts +1 −1
  642. arch/arm/boot/dts/am335x-evmsk.dts +1 −1
  643. arch/arm/boot/dts/am335x-igep0033.dtsi +20 −20
  644. arch/arm/boot/dts/am335x-phycore-som.dtsi +19 −17
  645. arch/arm/boot/dts/am335x-wega.dtsi +12 −1
  646. arch/arm/boot/dts/am4372.dtsi +1 −0
  647. arch/arm/boot/dts/am437x-gp-evm.dts +28 −3
  648. arch/arm/boot/dts/am437x-idk-evm.dts +1 −1
  649. arch/arm/boot/dts/am437x-sk-evm.dts +2 −2
  650. arch/arm/boot/dts/am43x-epos-evm.dts +1 −1
  651. arch/arm/boot/dts/am57xx-beagle-x15.dts +118 −2
  652. arch/arm/boot/dts/armada-370-db.dts +2 −1
  653. arch/arm/boot/dts/armada-370-dlink-dns327l.dts +2 −1
  654. arch/arm/boot/dts/armada-370-mirabox.dts +6 −1
  655. arch/arm/boot/dts/armada-370-netgear-rn102.dts +8 −1
  656. arch/arm/boot/dts/armada-370-netgear-rn104.dts +8 −1
  657. arch/arm/boot/dts/armada-370-rd.dts +2 −1
  658. arch/arm/boot/dts/armada-370-seagate-nas-2bay.dts +36 −0
  659. arch/arm/boot/dts/armada-370-seagate-nas-4bay.dts +133 −0
  660. arch/arm/boot/dts/armada-370-seagate-nas-xbay.dtsi +231 −0
  661. arch/arm/boot/dts/armada-370-seagate-personal-cloud-2bay.dts +51 −0
  662. arch/arm/boot/dts/armada-370-seagate-personal-cloud.dts +37 −0
  663. arch/arm/boot/dts/armada-370-seagate-personal-cloud.dtsi +178 −0
  664. arch/arm/boot/dts/armada-370-synology-ds213j.dts +2 −1
  665. arch/arm/boot/dts/armada-370.dtsi +37 −0
  666. arch/arm/boot/dts/armada-375-db.dts +3 −1
  667. arch/arm/boot/dts/armada-375.dtsi +33 −0
  668. arch/arm/boot/dts/armada-385-db-ap.dts +4 −2
  669. arch/arm/boot/dts/armada-385-linksys.dtsi +3 −1
  670. arch/arm/boot/dts/armada-388-db.dts +3 −1
  671. arch/arm/boot/dts/armada-388-gp.dts +17 −2
  672. arch/arm/boot/dts/armada-388-rd.dts +3 −1
  673. arch/arm/boot/dts/armada-38x.dtsi +33 −0
  674. arch/arm/boot/dts/armada-xp-axpwifiap.dts +3 −1
  675. arch/arm/boot/dts/armada-xp-db.dts +3 −1
  676. arch/arm/boot/dts/armada-xp-gp.dts +3 −1
  677. arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts +3 −1
  678. arch/arm/boot/dts/armada-xp-linksys-mamba.dts +3 −1
  679. arch/arm/boot/dts/armada-xp-matrix.dts +3 −1
  680. arch/arm/boot/dts/armada-xp-netgear-rn2120.dts +49 −41
  681. arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts +3 −1
  682. arch/arm/boot/dts/armada-xp-synology-ds414.dts +3 −1
  683. arch/arm/boot/dts/armada-xp.dtsi +35 −0
  684. arch/arm/boot/dts/at91-sama5d2_xplained.dts +118 −0
  685. arch/arm/boot/dts/at91-sama5d3_xplained.dts +1 −1
  686. arch/arm/boot/dts/at91-sama5d4_xplained.dts +1 −1
  687. arch/arm/boot/dts/at91-sama5d4ek.dts +27 −0
  688. arch/arm/boot/dts/at91rm9200.dtsi +4 −4
  689. arch/arm/boot/dts/at91sam9260.dtsi +1 −1
  690. arch/arm/boot/dts/at91sam9261.dtsi +1 −1
  691. arch/arm/boot/dts/at91sam9263.dtsi +1 −1
  692. arch/arm/boot/dts/at91sam9g45.dtsi +1 −1
  693. arch/arm/boot/dts/at91sam9m10g45ek.dts +2 −0
  694. arch/arm/boot/dts/at91sam9n12.dtsi +1 −1
  695. arch/arm/boot/dts/at91sam9n12ek.dts +2 −6
  696. arch/arm/boot/dts/at91sam9rl.dtsi +1 −1
  697. arch/arm/boot/dts/at91sam9x5.dtsi +3 −2
  698. arch/arm/boot/dts/at91sam9x5ek.dtsi +8 −0
  699. arch/arm/boot/dts/axp209.dtsi +5 −0
  700. arch/arm/boot/dts/axp22x.dtsi +143 −0
  701. arch/arm/boot/dts/bcm-cygnus.dtsi +175 −159
  702. arch/arm/boot/dts/bcm-nsp.dtsi +119 −0
  703. arch/arm/boot/dts/bcm2835-rpi-a-plus.dts +30 −0
  704. arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts +23 −0
  705. arch/arm/boot/dts/bcm2835-rpi-b.dts +1 −7
  706. arch/arm/boot/dts/bcm2835-rpi.dtsi +4 −0
  707. arch/arm/boot/dts/bcm2835.dtsi +39 −25
  708. arch/arm/boot/dts/bcm4708-netgear-r6250.dts +11 −0
  709. arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dts +1 −0
  710. arch/arm/boot/dts/bcm4709-netgear-r7000.dts +106 −0
  711. arch/arm/boot/dts/bcm7445.dtsi +84 −0
  712. arch/arm/boot/dts/bcm911360_entphn.dts +20 −8
  713. arch/arm/boot/dts/bcm911360k.dts +4 −5
  714. arch/arm/boot/dts/bcm958300k.dts +22 −22
  715. arch/arm/boot/dts/bcm958305k.dts +36 −4
  716. arch/arm/boot/dts/bcm958625k.dts +57 −0
  717. arch/arm/boot/dts/bcm9hmidc.dtsi +42 −0
  718. arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts +2 −1
  719. arch/arm/boot/dts/berlin2.dtsi +23 −0
  720. arch/arm/boot/dts/berlin2cd-google-chromecast.dts +2 −1
  721. arch/arm/boot/dts/berlin2cd.dtsi +20 −0
  722. arch/arm/boot/dts/berlin2q-marvell-dmp.dts +2 −1
  723. arch/arm/boot/dts/berlin2q.dtsi +26 −3
  724. arch/arm/boot/dts/cx92755.dtsi +7 −0
  725. arch/arm/boot/dts/cx92755_equinox.dts +9 −0
  726. arch/arm/boot/dts/dove.dtsi +13 −4
  727. arch/arm/boot/dts/dra7-evm.dts +218 −4
  728. arch/arm/boot/dts/dra7.dtsi +61 −0
  729. arch/arm/boot/dts/dra72-evm.dts +156 −6
  730. arch/arm/boot/dts/dra72x.dtsi +21 −0
  731. arch/arm/boot/dts/dra74x.dtsi +51 −0
  732. arch/arm/boot/dts/efm32gg-dk3750.dts +4 −4
  733. arch/arm/boot/dts/efm32gg.dtsi +16 −16
  734. arch/arm/boot/dts/emev2-kzm9d.dts +4 −4
  735. arch/arm/boot/dts/exynos3250-monk.dts +5 −4
  736. arch/arm/boot/dts/exynos3250-rinato.dts +6 −5
  737. arch/arm/boot/dts/exynos3250.dtsi +2 −2
  738. arch/arm/boot/dts/exynos4.dtsi +8 −0
  739. arch/arm/boot/dts/exynos4210-origen.dts +8 −7
  740. arch/arm/boot/dts/exynos4210-smdkv310.dts +2 −1
  741. arch/arm/boot/dts/exynos4210-trats.dts +16 −15
  742. arch/arm/boot/dts/exynos4210-universal_c210.dts +23 −21
  743. arch/arm/boot/dts/exynos4412-odroid-common.dtsi +10 −17
  744. arch/arm/boot/dts/exynos4412-odroidu3.dts +44 −1
  745. arch/arm/boot/dts/exynos4412-odroidx.dts +4 −4
  746. arch/arm/boot/dts/exynos4412-origen.dts +8 −7
  747. arch/arm/boot/dts/exynos4412-tiny4412.dts +5 −4
  748. arch/arm/boot/dts/exynos4412-trats2.dts +53 −87
  749. arch/arm/boot/dts/exynos4412.dtsi +1 −0
  750. arch/arm/boot/dts/exynos5250-arndale.dts +4 −4
  751. arch/arm/boot/dts/exynos5250-smdk5250.dts +9 −8
  752. arch/arm/boot/dts/exynos5250-snow-common.dtsi +684 −0
  753. arch/arm/boot/dts/exynos5250-snow-rev5.dts +47 −0
  754. arch/arm/boot/dts/exynos5250-snow.dts +4 −667
  755. arch/arm/boot/dts/exynos5250.dtsi +4 −0
  756. arch/arm/boot/dts/exynos5420-arndale-octa.dts +2 −1
  757. arch/arm/boot/dts/exynos5420-peach-pit.dts +10 −4
  758. arch/arm/boot/dts/exynos5420-smdk5420.dts +8 −6
  759. arch/arm/boot/dts/exynos5420.dtsi +1 −1
  760. arch/arm/boot/dts/exynos5422-odroidxu3-audio.dtsi +61 −0
  761. arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi +4 −99
  762. arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts +51 −0
  763. arch/arm/boot/dts/exynos5422-odroidxu3.dts +51 −0
  764. arch/arm/boot/dts/exynos5422-odroidxu4.dts +48 −0
  765. arch/arm/boot/dts/exynos5440-ssdk5440.dts +3 −2
  766. arch/arm/boot/dts/exynos5800-peach-pi.dts +10 −4
  767. arch/arm/boot/dts/hi3620-hi4511.dts +2 −1
  768. arch/arm/boot/dts/hisi-x5hd2-dkb.dts +1 −1
  769. arch/arm/boot/dts/imx23.dtsi +4 −2
  770. arch/arm/boot/dts/imx27.dtsi +12 −4
  771. arch/arm/boot/dts/imx28-evk.dts +1 −1
  772. arch/arm/boot/dts/imx28-m28evk.dts +1 −1
  773. arch/arm/boot/dts/imx28-tx28.dts +2 −1
  774. arch/arm/boot/dts/imx28.dtsi +4 −2
  775. arch/arm/boot/dts/imx31.dtsi +1 −1
  776. arch/arm/boot/dts/imx35.dtsi +1 −1
  777. arch/arm/boot/dts/imx50-evk.dts +1 −1
  778. arch/arm/boot/dts/imx53-qsrb.dts +1 −1
  779. arch/arm/boot/dts/imx53-smd.dts +1 −1
  780. arch/arm/boot/dts/imx53-tx53-x03x.dts +2 −1
  781. arch/arm/boot/dts/imx53.dtsi +1 −0
  782. arch/arm/boot/dts/imx6dl-nit6xlite.dts +49 −0
  783. arch/arm/boot/dts/imx6dl-nitrogen6x.dts +37 −7
  784. arch/arm/boot/dts/imx6dl-rex-basic.dts +1 −1
  785. arch/arm/boot/dts/imx6dl-sabrelite.dts +35 −5
  786. arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts +1 −1
  787. arch/arm/boot/dts/imx6q-gw5400-a.dts +1 −1
  788. arch/arm/boot/dts/imx6q-nitrogen6_max.dts +53 −0
  789. arch/arm/boot/dts/imx6q-nitrogen6x.dts +37 −7
  790. arch/arm/boot/dts/imx6q-rex-pro.dts +1 −1
  791. arch/arm/boot/dts/imx6q-sabrelite.dts +35 −5
  792. arch/arm/boot/dts/imx6qdl-aristainetos.dtsi +1 −1
  793. arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi +1 −1
  794. arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi +1 −1
  795. arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi +630 −0
  796. arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi +873 −0
  797. arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi +182 −7
  798. arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi +3 −3
  799. arch/arm/boot/dts/imx6qdl-rex.dtsi +0 −2
  800. arch/arm/boot/dts/imx6qdl-sabreauto.dtsi +1 −1
  801. arch/arm/boot/dts/imx6qdl-sabrelite.dtsi +111 −7
  802. arch/arm/boot/dts/imx6qdl-sabresd.dtsi +1 −1
  803. arch/arm/boot/dts/imx6qdl-tx6.dtsi +2 −1
  804. arch/arm/boot/dts/imx6qdl.dtsi +6 −6
  805. arch/arm/boot/dts/imx6sl-evk.dts +1 −1
  806. arch/arm/boot/dts/imx6sl.dtsi +20 −1
  807. arch/arm/boot/dts/imx6sx-sdb-reva.dts +2 −2
  808. arch/arm/boot/dts/imx6sx-sdb.dts +2 −2
  809. arch/arm/boot/dts/imx6sx-sdb.dtsi +1 −1
  810. arch/arm/boot/dts/imx6sx.dtsi +1 −1
  811. arch/arm/boot/dts/imx6ul-14x14-evk.dts +22 −0
  812. arch/arm/boot/dts/imx6ul.dtsi +29 −0
  813. arch/arm/boot/dts/imx7d-pinfunc.h +119 −3
  814. arch/arm/boot/dts/imx7d-sdb.dts +99 −1
  815. arch/arm/boot/dts/imx7d.dtsi +167 −2
  816. arch/arm/boot/dts/k2e-evm.dts +1 −1
  817. arch/arm/boot/dts/k2e-netcp.dtsi +23 −0
  818. arch/arm/boot/dts/k2e.dtsi +3 −0
  819. arch/arm/boot/dts/k2hk-evm.dts +1 −1
  820. arch/arm/boot/dts/k2hk-netcp.dtsi +24 −0
  821. arch/arm/boot/dts/k2hk.dtsi +3 −0
  822. arch/arm/boot/dts/k2l-evm.dts +1 −1
  823. arch/arm/boot/dts/k2l-netcp.dtsi +23 −0
  824. arch/arm/boot/dts/k2l.dtsi +3 −0
  825. arch/arm/boot/dts/keystone.dtsi +4 −3
  826. arch/arm/boot/dts/kirkwood-net5big.dts +60 −0
  827. arch/arm/boot/dts/kirkwood-netxbig.dtsi +80 −0
  828. arch/arm/boot/dts/kirkwood.dtsi +19 −10
  829. arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts +1 −1
  830. arch/arm/boot/dts/lpc18xx.dtsi +134 −0
  831. arch/arm/boot/dts/lpc4350-hitex-eval.dts +175 −0
  832. arch/arm/boot/dts/lpc4357-ea4357-devkit.dts +95 −0
  833. arch/arm/boot/dts/ls1021a-twr.dts +13 −0
  834. arch/arm/boot/dts/ls1021a.dtsi +44 −0
  835. arch/arm/boot/dts/meson.dtsi +12 −11
  836. arch/arm/boot/dts/meson8b-mxq.dts +67 −0
  837. arch/arm/boot/dts/meson8b-odroidc1.dts +67 −0
  838. arch/arm/boot/dts/meson8b.dtsi +186 −0
  839. arch/arm/boot/dts/mt8127.dtsi +27 −0
  840. arch/arm/boot/dts/mt8135-evbp1.dts +0 −23
  841. arch/arm/boot/dts/mt8135.dtsi +27 −0
  842. arch/arm/boot/dts/nspire.dtsi +1 −1
  843. arch/arm/boot/dts/omap2420-n8x0-common.dtsi +3 −3
  844. arch/arm/boot/dts/omap3-beagle-xm.dts +1 −1
  845. arch/arm/boot/dts/omap3-beagle.dts +1 −1
  846. arch/arm/boot/dts/omap3-cm-t3x.dtsi +1 −1
  847. arch/arm/boot/dts/omap3-devkit8000-lcd-common.dtsi +1 −1
  848. arch/arm/boot/dts/omap3-evm-37xx.dts +1 −1
  849. arch/arm/boot/dts/omap3-evm-common.dtsi +2 −2
  850. arch/arm/boot/dts/omap3-gta04.dtsi +5 −5
  851. arch/arm/boot/dts/omap3-gta04a5.dts +1 −1
  852. arch/arm/boot/dts/omap3-igep.dtsi +35 −35
  853. arch/arm/boot/dts/omap3-igep0020-common.dtsi +30 −30
  854. arch/arm/boot/dts/omap3-igep0020-rev-f.dts +1 −1
  855. arch/arm/boot/dts/omap3-igep0020.dts +1 −10
  856. arch/arm/boot/dts/omap3-igep0030-common.dtsi +1 −1
  857. arch/arm/boot/dts/omap3-igep0030-rev-g.dts +1 −1
  858. arch/arm/boot/dts/omap3-igep0030.dts +1 −1
  859. arch/arm/boot/dts/omap3-ldp.dts +1 −1
  860. arch/arm/boot/dts/omap3-lilly-a83x.dtsi +2 −2
  861. arch/arm/boot/dts/omap3-lilly-dbb056.dts +2 −2
  862. arch/arm/boot/dts/omap3-n950-n9.dtsi +1 −1
  863. arch/arm/boot/dts/omap3-overo-base.dtsi +1 −1
  864. arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi +1 −1
  865. arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi +1 −1
  866. arch/arm/boot/dts/omap3-pandora-common.dtsi +2 −2
  867. arch/arm/boot/dts/omap3-tao3530.dtsi +2 −2
  868. arch/arm/boot/dts/omap3-zoom3.dts +1 −1
  869. arch/arm/boot/dts/omap4-panda-common.dtsi +2 −2
  870. arch/arm/boot/dts/omap4-sdp.dts +3 −3
  871. arch/arm/boot/dts/omap4-var-som-om44-wlan.dtsi +1 −1
  872. arch/arm/boot/dts/omap4-var-som-om44.dtsi +1 −1
  873. arch/arm/boot/dts/omap4460.dtsi +1 −1
  874. arch/arm/boot/dts/omap5-board-common.dtsi +655 −0
  875. arch/arm/boot/dts/omap5-cm-t54.dts +1 −1
  876. arch/arm/boot/dts/omap5-igep0050.dts +54 −0
  877. arch/arm/boot/dts/omap5-uevm.dts +14 −604
  878. arch/arm/boot/dts/orion5x.dtsi +15 −7
  879. arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts +42 −6
  880. arch/arm/boot/dts/qcom-apq8064-ifc6410.dts +53 −7
  881. arch/arm/boot/dts/qcom-apq8064.dtsi +42 −1
  882. arch/arm/boot/dts/qcom-apq8084.dtsi +1 −0
  883. arch/arm/boot/dts/qcom-msm8974.dtsi +88 −7
  884. arch/arm/boot/dts/qcom-pm8941.dtsi +22 −2
  885. arch/arm/boot/dts/r8a7778-bockw-reference.dts +0 −139
  886. arch/arm/boot/dts/r8a7778.dtsi +1 −1
  887. arch/arm/boot/dts/r8a7779-marzen.dts +3 −3
  888. arch/arm/boot/dts/r8a7790-lager.dts +15 −1
  889. arch/arm/boot/dts/r8a7790.dtsi +2 −1
  890. arch/arm/boot/dts/r8a7791-koelsch.dts +8 −1
  891. arch/arm/boot/dts/r8a7791-porter.dts +282 −0
  892. arch/arm/boot/dts/r8a7791.dtsi +2 −1
  893. arch/arm/boot/dts/r8a7794-silk.dts +114 −0
  894. arch/arm/boot/dts/r8a7794.dtsi +318 −8
  895. arch/arm/boot/dts/r8a77xx-aa121td01-panel.dtsi +41 −0
  896. arch/arm/boot/dts/rk3066a-bqcurie2.dts +2 −0
  897. arch/arm/boot/dts/rk3066a-marsboard.dts +8 −0
  898. arch/arm/boot/dts/rk3066a-rayeager.dts +2 −0
  899. arch/arm/boot/dts/rk3188-radxarock.dts +21 −0
  900. arch/arm/boot/dts/rk3188.dtsi +20 −0
  901. arch/arm/boot/dts/rk3288-firefly.dtsi +52 −3
  902. arch/arm/boot/dts/rk3288-popmetal.dts +81 −4
  903. arch/arm/boot/dts/rk3288-rock2-som.dtsi +277 −0
  904. arch/arm/boot/dts/rk3288-rock2-square.dts +167 −0
  905. arch/arm/boot/dts/rk3288-veyron-jaq.dts +176 −0
  906. arch/arm/boot/dts/rk3288-veyron-sdmmc.dtsi +6 −1
  907. arch/arm/boot/dts/rk3288-veyron.dtsi +6 −12
  908. arch/arm/boot/dts/rk3288.dtsi +141 −13
  909. arch/arm/boot/dts/s3c2416.dtsi +1 −1
  910. arch/arm/boot/dts/s5pv210-aquila.dts +1 −1
  911. arch/arm/boot/dts/s5pv210-goni.dts +2 −2
  912. arch/arm/boot/dts/sama5d2-pinfunc.h +880 −0
  913. arch/arm/boot/dts/sama5d2.dtsi +165 −3
  914. arch/arm/boot/dts/sama5d3.dtsi +3 −2
  915. arch/arm/boot/dts/sama5d3_mci2.dtsi +3 −3
  916. arch/arm/boot/dts/sama5d3xmb.dtsi +2 −0
  917. arch/arm/boot/dts/sama5d4.dtsi +39 −10
  918. arch/arm/boot/dts/sh73a0-kzm9g.dts +1 −1
  919. arch/arm/boot/dts/socfpga.dtsi +71 −64
  920. arch/arm/boot/dts/socfpga_arria10.dtsi +8 −0
  921. arch/arm/boot/dts/socfpga_arria10_socdk.dtsi +27 −0
  922. arch/arm/boot/dts/ste-hrefv60plus.dtsi +1 −1
  923. arch/arm/boot/dts/ste-snowball.dts +5 −5
  924. arch/arm/boot/dts/stih407-b2120.dts +1 −0
  925. arch/arm/boot/dts/stih407-family.dtsi +86 −2
  926. arch/arm/boot/dts/stih407-pinctrl.dtsi +379 −11
  927. arch/arm/boot/dts/stih407.dtsi +0 −13
  928. arch/arm/boot/dts/stih410-b2120.dts +25 −0
  929. arch/arm/boot/dts/stih410.dtsi +11 −12
  930. arch/arm/boot/dts/stih418-b2199.dts +8 −0
  931. arch/arm/boot/dts/stih418-clock.dtsi +1 −1
  932. arch/arm/boot/dts/stih418.dtsi +6 −0
  933. arch/arm/boot/dts/stihxxx-b2120.dtsi +14 −0
  934. arch/arm/boot/dts/stm32f429.dtsi +7 −0
  935. arch/arm/boot/dts/sun4i-a10-a1000.dts +4 −0
  936. arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts +12 −0
  937. arch/arm/boot/dts/sun4i-a10-cubieboard.dts +4 −0
  938. arch/arm/boot/dts/sun4i-a10-gemei-g9.dts +4 −7
  939. arch/arm/boot/dts/sun4i-a10-inet1.dts +226 −0
  940. arch/arm/boot/dts/sun4i-a10-inet97fv2.dts +107 −10
  941. arch/arm/boot/dts/sun4i-a10-inet9f-rev03.dts +227 −0
  942. arch/arm/boot/dts/sun4i-a10-jesurun-q5.dts +15 −0
  943. arch/arm/boot/dts/sun4i-a10-marsboard.dts +23 −0
  944. arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts +12 −0
  945. arch/arm/boot/dts/sun4i-a10-pcduino.dts +48 −10
  946. arch/arm/boot/dts/sun4i-a10-pcduino2.dts +78 −0
  947. arch/arm/boot/dts/sun4i-a10-pov-protab2-ips9.dts +199 −0
  948. arch/arm/boot/dts/sun4i-a10.dtsi +31 −0
  949. arch/arm/boot/dts/sun5i-a10s-auxtek-t003.dts +159 −0
  950. arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts +1 −1
  951. arch/arm/boot/dts/sun5i-a10s-wobo-i5.dts +224 −0
  952. arch/arm/boot/dts/sun5i-a10s.dtsi +28 −7
  953. arch/arm/boot/dts/sun5i-a13-inet-98v-rev2.dts +227 −0
  954. arch/arm/boot/dts/sun5i-a13-q8-tablet.dts +60 −0
  955. arch/arm/boot/dts/sun5i-a13.dtsi +10 −0
  956. arch/arm/boot/dts/sun5i-q8-common.dtsi +180 −0
  957. arch/arm/boot/dts/sun5i-r8-chip.dts +218 −0
  958. arch/arm/boot/dts/sun5i-r8.dtsi +59 −0
  959. arch/arm/boot/dts/sun5i.dtsi +52 −0
  960. arch/arm/boot/dts/sun6i-a31-colombus.dts +36 −0
  961. arch/arm/boot/dts/sun6i-a31-hummingbird.dts +72 −60
  962. arch/arm/boot/dts/sun6i-a31.dtsi +28 −3
  963. arch/arm/boot/dts/sun6i-a31s-primo81.dts +255 −0
  964. arch/arm/boot/dts/sun6i-a31s-sina31s-core.dtsi +140 −0
  965. arch/arm/boot/dts/sun6i-a31s-sina31s.dts +153 −0
  966. arch/arm/boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts +194 −0
  967. arch/arm/boot/dts/sun6i-a31s-yones-toptech-bs1078-v2.dts +134 −0
  968. arch/arm/boot/dts/sun7i-a20-bananapi.dts +70 −4
  969. arch/arm/boot/dts/sun7i-a20-cubieboard2.dts +23 −0
  970. arch/arm/boot/dts/sun7i-a20-cubietruck.dts +4 −0
  971. arch/arm/boot/dts/sun7i-a20-olimex-som-evb.dts +198 −0
  972. arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts +12 −0
  973. arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts +47 −0
  974. arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts +6 −0
  975. arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts +29 −0
  976. arch/arm/boot/dts/sun7i-a20-orangepi.dts +29 −0
  977. arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts +54 −11
  978. arch/arm/boot/dts/sun7i-a20-pcduino3.dts +50 −4
  979. arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts +32 −1
  980. arch/arm/boot/dts/sun7i-a20-wits-pro-a20-dkt.dts +226 −0
  981. arch/arm/boot/dts/sun7i-a20.dtsi +40 −1
  982. arch/arm/boot/dts/sun8i-a23-a33.dtsi +45 −25
  983. arch/arm/boot/dts/sun8i-a23-gt90h-v4.dts +145 −0
  984. arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts +0 −54
  985. arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts +1 −0
  986. arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts +0 −136
  987. arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts +1 −0
  988. arch/arm/boot/dts/sun8i-a23-q8-tablet.dts +65 −0
  989. arch/arm/boot/dts/sun8i-a23.dtsi +25 −0
  990. arch/arm/boot/dts/sun8i-a33-et-q8-v1.6.dts +0 −88
  991. arch/arm/boot/dts/sun8i-a33-et-q8-v1.6.dts +1 −0
  992. arch/arm/boot/dts/sun8i-a33-ippo-q8h-v1.2.dts +0 −133
  993. arch/arm/boot/dts/sun8i-a33-ippo-q8h-v1.2.dts +1 −0
  994. arch/arm/boot/dts/sun8i-a33-q8-tablet.dts +65 −0
  995. arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts +4 −0
  996. arch/arm/boot/dts/sun8i-a33.dtsi +45 −0
  997. arch/arm/boot/dts/sun8i-q8-common.dtsi +101 −0
  998. arch/arm/boot/dts/sun9i-a80.dtsi +1 −1
  999. arch/arm/boot/dts/sunxi-q8-common.dtsi +83 −0
  1000. arch/arm/boot/dts/tegra114.dtsi +2 −0
  1001. arch/arm/boot/dts/tegra124-nyan.dtsi +14 −1
  1002. arch/arm/boot/dts/tegra124.dtsi +9 −13
  1003. arch/arm/boot/dts/tegra20.dtsi +4 −2
  1004. arch/arm/boot/dts/tegra30-apalis-eval.dts +9 −4
  1005. arch/arm/boot/dts/tegra30-apalis.dtsi +131 −83
  1006. arch/arm/boot/dts/tegra30-colibri-eval-v3.dts +5 −4
  1007. arch/arm/boot/dts/tegra30-colibri.dtsi +142 −54
  1008. arch/arm/boot/dts/tegra30.dtsi +7 −5
  1009. arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts +3 −5
  1010. arch/arm/boot/dts/uniphier-ph1-ld4.dtsi +16 −4
  1011. arch/arm/boot/dts/uniphier-ph1-ld6b-ref.dts +4 −6
  1012. arch/arm/boot/dts/uniphier-ph1-pro4-ref.dts +3 −5
  1013. arch/arm/boot/dts/uniphier-ph1-pro4.dtsi +17 −4
  1014. arch/arm/boot/dts/uniphier-ph1-pro5.dtsi +30 −4
  1015. arch/arm/boot/dts/uniphier-ph1-sld3-ref.dts +3 −5
  1016. arch/arm/boot/dts/uniphier-ph1-sld3.dtsi +17 −4
  1017. arch/arm/boot/dts/uniphier-ph1-sld8-ref.dts +3 −5
  1018. arch/arm/boot/dts/uniphier-ph1-sld8.dtsi +16 −4
  1019. arch/arm/boot/dts/uniphier-proxstream2-gentil.dts +78 −0
  1020. arch/arm/boot/dts/uniphier-proxstream2-vodka.dts +78 −0
  1021. arch/arm/boot/dts/uniphier-proxstream2.dtsi +19 −4
  1022. arch/arm/boot/dts/vf-colibri.dtsi +39 −0
  1023. arch/arm/boot/dts/vf500-colibri-eval-v3.dts +5 −0
  1024. arch/arm/boot/dts/vf500-colibri.dtsi +47 −0
  1025. arch/arm/boot/dts/vf610-twr.dts +47 −0
  1026. arch/arm/boot/dts/vfxxx.dtsi +11 −0
  1027. arch/arm/boot/dts/wm8750.dtsi +1 −1
  1028. arch/arm/boot/dts/zynq-7000.dtsi +5 −0
  1029. arch/arm/common/Kconfig +0 −3
  1030. arch/arm/common/Makefile +0 −1
  1031. arch/arm/common/edma.c +0 −1876
  1032. arch/arm/configs/at91_dt_defconfig +0 −15
  1033. arch/arm/configs/bockw_defconfig +0 −133
  1034. arch/arm/configs/exynos_defconfig +16 −4
  1035. arch/arm/configs/hisi_defconfig +0 −1
  1036. arch/arm/configs/imx_v6_v7_defconfig +1 −1
  1037. arch/arm/configs/keystone_defconfig +27 −27
  1038. arch/arm/configs/lpc18xx_defconfig +22 −5
  1039. arch/arm/configs/multi_v7_defconfig +47 −1
  1040. arch/arm/configs/mvebu_v7_defconfig +8 −1
  1041. arch/arm/configs/omap2plus_defconfig +1 −1
  1042. arch/arm/configs/qcom_defconfig +5 −3
  1043. arch/arm/configs/sama5_defconfig +6 −10
  1044. arch/arm/configs/shmobile_defconfig +3 −1
  1045. arch/arm/configs/socfpga_defconfig +2 −0
  1046. arch/arm/configs/sunxi_defconfig +4 −0
  1047. arch/arm/configs/tegra_defconfig +7 −3
  1048. arch/arm/include/asm/Kbuild +1 −0
  1049. arch/arm/include/asm/arch_gicv3.h +188 −0
  1050. arch/arm/include/asm/atomic.h +6 −6
  1051. arch/arm/include/asm/cmpxchg.h +12 −0
  1052. arch/arm/include/asm/hardware/cache-uniphier.h +46 −0
  1053. arch/arm/include/asm/highmem.h +0 −1
  1054. arch/arm/include/asm/irqflags.h +10 −0
  1055. arch/arm/include/asm/kvm_arm.h +20 −0
  1056. arch/arm/include/asm/kvm_host.h +4 −1
  1057. arch/arm/include/asm/mach/arch.h +1 −1
  1058. arch/arm/include/asm/mach/pci.h +0 −6
  1059. arch/arm/include/asm/memory.h +2 −0
  1060. arch/arm/include/asm/pgtable.h +1 −1
  1061. arch/arm/include/asm/smp.h +2 −2
  1062. arch/arm/include/asm/unistd.h +0 −7
  1063. arch/arm/include/asm/xen/hypervisor.h +10 −0
  1064. arch/arm/include/asm/xen/page-coherent.h +17 −9
  1065. arch/arm/include/asm/xen/page.h +15 −7
  1066. arch/arm/include/debug/at91.S +4 −14
  1067. arch/arm/kernel/bios32.c +8 −4
  1068. arch/arm/kernel/devtree.c +9 −3
  1069. arch/arm/kernel/entry-armv.S +3 −30
  1070. arch/arm/kernel/hw_breakpoint.c +0 −1
  1071. arch/arm/kernel/irq.c +3 −0
  1072. arch/arm/kernel/kgdb.c +12 −19
  1073. arch/arm/kernel/psci_smp.c +2 −2
  1074. arch/arm/kernel/smp.c +11 −1
  1075. arch/arm/kernel/smp_twd.c +5 −6
  1076. arch/arm/kernel/time.c +1 −1
  1077. arch/arm/kernel/traps.c +0 −52
  1078. arch/arm/kvm/Kconfig +3 −0
  1079. arch/arm/kvm/arm.c +61 −17
  1080. arch/arm/kvm/psci.c +5 −5
  1081. arch/arm/kvm/trace.h +7 −3
  1082. arch/arm/lib/clear_user.S +4 −0
  1083. arch/arm/mach-at91/Kconfig +3 −0
  1084. arch/arm/mach-at91/pm_suspend.S +2 −0
  1085. arch/arm/mach-bcm/Kconfig +16 −1
  1086. arch/arm/mach-bcm/Makefile +4 −1
  1087. arch/arm/mach-bcm/bcm_nsp.c +25 −0
  1088. arch/arm/mach-bcm/brcmstb.c +9 −0
  1089. arch/arm/mach-berlin/berlin.c +6 −0
  1090. arch/arm/mach-berlin/platsmp.c +35 −3
  1091. arch/arm/mach-cns3xxx/pcie.c +30 −41
  1092. arch/arm/mach-davinci/board-dm644x-evm.c +1 −3
  1093. arch/arm/mach-davinci/clock.c +11 −5
  1094. arch/arm/mach-davinci/devices-da8xx.c +45 −77
  1095. arch/arm/mach-davinci/dm355.c +21 −19
  1096. arch/arm/mach-davinci/dm365.c +10 −15
  1097. arch/arm/mach-davinci/dm644x.c +21 −19
  1098. arch/arm/mach-davinci/dm646x.c +22 −22
  1099. arch/arm/mach-digicolor/Kconfig +3 −0
  1100. arch/arm/mach-exynos/mcpm-exynos.c +26 −1
  1101. arch/arm/mach-exynos/pm_domains.c +3 −5
  1102. arch/arm/mach-exynos/regs-pmu.h +6 −0
  1103. arch/arm/mach-exynos/suspend.c +31 −27
  1104. arch/arm/mach-gemini/board-nas4220b.c +0 −1
  1105. arch/arm/mach-gemini/board-wbd111.c +0 −1
  1106. arch/arm/mach-gemini/board-wbd222.c +0 −1
  1107. arch/arm/mach-imx/common.h +1 −0
  1108. arch/arm/mach-imx/gpc.c +31 −32
  1109. arch/arm/mach-imx/mach-imx6q.c +1 −1
  1110. arch/arm/mach-imx/mach-imx6ul.c +9 −0
  1111. arch/arm/mach-imx/mach-imx7d.c +74 −0
  1112. arch/arm/mach-imx/pm-imx6.c +40 −6
  1113. arch/arm/mach-imx/suspend-imx6.S +3 −0
  1114. arch/arm/mach-keystone/keystone.c +3 −0
  1115. arch/arm/mach-mediatek/Makefile +3 −0
  1116. arch/arm/mach-mediatek/mediatek.c +27 −0
  1117. arch/arm/mach-mediatek/platsmp.c +141 −0
  1118. arch/arm/mach-meson/Kconfig +5 −0
  1119. arch/arm/mach-meson/meson.c +1 −0
  1120. arch/arm/mach-mvebu/Kconfig +0 −7
  1121. arch/arm/mach-mvebu/Makefile +0 −1
  1122. arch/arm/mach-mvebu/board-v7.c +0 −35
  1123. arch/arm/mach-mvebu/board.h +0 −21
  1124. arch/arm/mach-mvebu/coherency.c +60 −0
  1125. arch/arm/mach-mvebu/kirkwood.c +0 −4
  1126. arch/arm/mach-mvebu/netxbig.c +0 −191
  1127. arch/arm/mach-mvebu/pmsu.c +28 −5
  1128. arch/arm/mach-omap1/Kconfig +0 −7
  1129. arch/arm/mach-omap1/Makefile +0 −1
  1130. arch/arm/mach-omap1/board-voiceblue.c +0 −296
  1131. arch/arm/mach-omap1/include/mach/board-voiceblue.h +0 −19
  1132. arch/arm/mach-omap2/Kconfig +3 −1
  1133. arch/arm/mach-omap2/Makefile +0 −3
  1134. arch/arm/mach-omap2/board-generic.c +16 −6
  1135. arch/arm/mach-omap2/board-ldp.c +1 −1
  1136. arch/arm/mach-omap2/board-rx51.c +1 −1
  1137. arch/arm/mach-omap2/clkt34xx_dpll3m2.c +0 −122
  1138. arch/arm/mach-omap2/common.h +1 −2
  1139. arch/arm/mach-omap2/devices.c +0 −53
  1140. arch/arm/mach-omap2/id.c +15 −15
  1141. arch/arm/mach-omap2/omap-hotplug.c +1 −1
  1142. arch/arm/mach-omap2/omap-wakeupgen.c +32 −33
  1143. arch/arm/mach-omap2/omap_hwmod_33xx_43xx_interconnect_data.c +0 −20
  1144. arch/arm/mach-omap2/omap_hwmod_3xxx_data.c +0 −29
  1145. arch/arm/mach-omap2/omap_hwmod_44xx_data.c +0 −10
  1146. arch/arm/mach-omap2/omap_hwmod_54xx_data.c +1 −2
  1147. arch/arm/mach-omap2/omap_hwmod_7xx_data.c +0 −30
  1148. arch/arm/mach-omap2/pdata-quirks.c +8 −1
  1149. arch/arm/mach-omap2/pm44xx.c +1 −1
  1150. arch/arm/mach-omap2/powerdomains3xxx_data.c +1 −1
  1151. arch/arm/mach-omap2/soc.h +106 −89
  1152. arch/arm/mach-omap2/sram.c +0 −25
  1153. arch/arm/mach-omap2/sram.h +0 −14
  1154. arch/arm/mach-omap2/sram34xx.S +0 −346
  1155. arch/arm/mach-omap2/timer.c +73 −91
  1156. arch/arm/mach-omap2/vc.c +0 −4
  1157. arch/arm/mach-orion5x/Kconfig +3 −0
  1158. arch/arm/mach-orion5x/dns323-setup.c +3 −50
  1159. arch/arm/mach-orion5x/tsx09-common.c +4 −45
  1160. arch/arm/mach-prima2/hotplug.c +1 −1
  1161. arch/arm/mach-pxa/cm-x300.c +7 −2
  1162. arch/arm/mach-pxa/colibri-pxa270-income.c +7 −2
  1163. arch/arm/mach-pxa/devices.c +20 −0
  1164. arch/arm/mach-pxa/ezx.c +7 −2
  1165. arch/arm/mach-pxa/hx4700.c +0 −3
  1166. arch/arm/mach-pxa/icontrol.c +0 −2
  1167. arch/arm/mach-pxa/include/mach/magician.h +39 −31
  1168. arch/arm/mach-pxa/include/mach/pxa27x.h +1 −1
  1169. arch/arm/mach-pxa/lpd270.c +7 −2
  1170. arch/arm/mach-pxa/magician.c +422 −258
  1171. arch/arm/mach-pxa/mainstone.c +15 −4
  1172. arch/arm/mach-pxa/mioa701.c +9 −2
  1173. arch/arm/mach-pxa/palm27x.c +7 −2
  1174. arch/arm/mach-pxa/palmtc.c +7 −2
  1175. arch/arm/mach-pxa/palmte2.c +7 −2
  1176. arch/arm/mach-pxa/pcm990-baseboard.c +7 −2
  1177. arch/arm/mach-pxa/pxa27x.c +1 −1
  1178. arch/arm/mach-pxa/pxa3xx.c +5 −4
  1179. arch/arm/mach-pxa/raumfeld.c +13 −8
  1180. arch/arm/mach-pxa/tavorevb.c +9 −4
  1181. arch/arm/mach-pxa/viper.c +7 −2
  1182. arch/arm/mach-pxa/z2.c +9 −6
  1183. arch/arm/mach-pxa/zylonite.c +7 −2
  1184. arch/arm/mach-qcom/platsmp.c +1 −1
  1185. arch/arm/mach-realview/hotplug.c +1 −1
  1186. arch/arm/mach-rockchip/rockchip.c +1 −1
  1187. arch/arm/mach-s3c24xx/mach-h1940.c +7 −3
  1188. arch/arm/mach-s3c24xx/mach-rx1950.c +6 −2
  1189. arch/arm/mach-s3c64xx/dev-backlight.c +0 −4
  1190. arch/arm/mach-s3c64xx/mach-crag6410.c +9 −4
  1191. arch/arm/mach-s3c64xx/mach-hmt.c +7 −2
  1192. arch/arm/mach-s3c64xx/mach-smartq.c +9 −4
  1193. arch/arm/mach-s3c64xx/mach-smdk6410.c +9 −3
  1194. arch/arm/mach-shmobile/Kconfig +0 −73
  1195. arch/arm/mach-shmobile/Makefile +1 −13
  1196. arch/arm/mach-shmobile/Makefile.boot +0 −12
  1197. arch/arm/mach-shmobile/board-bockw-reference.c +0 −86
  1198. arch/arm/mach-shmobile/board-bockw.c +0 −737
  1199. arch/arm/mach-shmobile/clock-r8a7778.c +0 −342
  1200. arch/arm/mach-shmobile/clock.c +0 −47
  1201. arch/arm/mach-shmobile/clock.h +0 −42
  1202. arch/arm/mach-shmobile/common.h +0 −5
  1203. arch/arm/mach-shmobile/console.c +0 −27
  1204. arch/arm/mach-shmobile/intc.h +0 −295
  1205. arch/arm/mach-shmobile/platsmp-apmu.c +2 −2
  1206. arch/arm/mach-shmobile/pm-r8a7779.c +0 −99
  1207. arch/arm/mach-shmobile/pm-rmobile.c +6 −33
  1208. arch/arm/mach-shmobile/pm-rmobile.h +0 −9
  1209. arch/arm/mach-shmobile/r8a7778.h +0 −78
  1210. arch/arm/mach-shmobile/r8a7779.h +0 −8
  1211. arch/arm/mach-shmobile/setup-r8a7778.c +3 −560
  1212. arch/arm/mach-shmobile/setup-r8a7779.c +1 −1
  1213. arch/arm/mach-shmobile/setup-rcar-gen2.c +1 −1
  1214. arch/arm/mach-shmobile/sh-gpio.h +0 −29
  1215. arch/arm/mach-shmobile/timer.c +0 −21
  1216. arch/arm/mach-spear/hotplug.c +1 −1
  1217. arch/arm/mach-spear/spear13xx.c +1 −1
  1218. arch/arm/mach-sunxi/sunxi.c +3 −2
  1219. arch/arm/mach-tegra/board-paz00.c +2 −2
  1220. arch/arm/mach-tegra/hotplug.c +1 −1
  1221. arch/arm/mach-u300/core.c +1 −1
  1222. arch/arm/mach-u300/dummyspichip.c +0 −1
  1223. arch/arm/mach-uniphier/Makefile +1 −1
  1224. arch/arm/mach-uniphier/headsmp.S +43 −0
  1225. arch/arm/mach-uniphier/platsmp.c +155 −30
  1226. arch/arm/mach-ux500/hotplug.c +1 −1
  1227. arch/arm/mach-ux500/timer.c +1 −1
  1228. arch/arm/mach-vexpress/hotplug.c +1 −1
  1229. arch/arm/mach-zynq/common.c +1 −1
  1230. arch/arm/mm/Kconfig +10 −12
  1231. arch/arm/mm/Makefile +1 −0
  1232. arch/arm/mm/alignment.c +1 −1
  1233. arch/arm/mm/cache-uniphier.c +555 −0
  1234. arch/arm/mm/dma-mapping.c +10 −3
  1235. arch/arm/mm/fault.c +22 −0
  1236. arch/arm/mm/fault.h +1 −0
  1237. arch/arm/mm/highmem.c +0 −10
  1238. arch/arm/mm/mmu.c +4 −0
  1239. arch/arm/net/bpf_jit_32.c +35 −8
  1240. arch/arm/net/bpf_jit_32.h +5 −0
  1241. arch/arm/plat-orion/common.c +1 −1
  1242. arch/arm/plat-samsung/devs.c +3 −3
  1243. arch/arm/vdso/vdsomunge.c +13 −4
  1244. arch/arm/xen/enlighten.c +16 −4
  1245. arch/arm/xen/mm.c +30 −11
  1246. arch/arm/xen/p2m.c +3 −3
  1247. arch/arm64/Kconfig +80 −18
  1248. arch/arm64/Kconfig.debug +1 −5
  1249. arch/arm64/Kconfig.platforms +9 −3
  1250. arch/arm64/Makefile +8 −1
  1251. arch/arm64/boot/dts/Makefile +7 −0
  1252. arch/arm64/boot/dts/altera/Makefile +5 −0
  1253. arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi +358 −0
  1254. arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts +39 −0
  1255. arch/arm64/boot/dts/amd/amd-overdrive.dts +0 −1
  1256. arch/arm64/boot/dts/apm/Makefile +1 −0
  1257. arch/arm64/boot/dts/apm/apm-merlin.dts +72 −0
  1258. arch/arm64/boot/dts/apm/apm-mustang.dts +12 −0
  1259. arch/arm64/boot/dts/apm/apm-shadowcat.dtsi +271 −0
  1260. arch/arm64/boot/dts/apm/apm-storm.dtsi +55 −0
  1261. arch/arm64/boot/dts/arm/juno-base.dtsi +59 −0
  1262. arch/arm64/boot/dts/arm/juno-motherboard.dtsi +21 −6
  1263. arch/arm64/boot/dts/arm/juno-r1.dts +63 −7
  1264. arch/arm64/boot/dts/arm/juno.dts +43 −7
  1265. arch/arm64/boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts +1 −1
  1266. arch/arm64/boot/dts/arm/vexpress-v2m-rs1.dtsi +1 −0
  1267. arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi +103 −0
  1268. arch/arm64/boot/dts/exynos/exynos7.dtsi +7 −0
  1269. arch/arm64/boot/dts/freescale/Makefile +3 −1
  1270. arch/arm64/boot/dts/freescale/fsl-ls2080a-qds.dts +204 −0
  1271. arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts +166 −0
  1272. arch/arm64/boot/dts/freescale/fsl-ls2080a-simu.dts +15 −10
  1273. arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi +515 −0
  1274. arch/arm64/boot/dts/freescale/fsl-ls2085a.dtsi +0 −163
  1275. arch/arm64/boot/dts/hisilicon/Makefile +1 −1
  1276. arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts +5 −2
  1277. arch/arm64/boot/dts/hisilicon/hi6220.dtsi +42 −1
  1278. arch/arm64/boot/dts/hisilicon/hip05-d02.dts +36 −0
  1279. arch/arm64/boot/dts/hisilicon/hip05.dtsi +271 −0
  1280. arch/arm64/boot/dts/hisilicon/hip05_hns.dtsi +191 −0
  1281. arch/arm64/boot/dts/marvell/Makefile +1 −0
  1282. arch/arm64/boot/dts/marvell/berlin4ct-stb.dts +66 −0
  1283. arch/arm64/boot/dts/marvell/berlin4ct.dtsi +120 −0
  1284. arch/arm64/boot/dts/mediatek/mt8173-evb.dts +18 −0
  1285. arch/arm64/boot/dts/mediatek/mt8173.dtsi +57 −5
  1286. arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi +30 −0
  1287. arch/arm64/boot/dts/qcom/msm8916-pins.dtsi +74 −2
  1288. arch/arm64/boot/dts/qcom/msm8916.dtsi +47 −0
  1289. arch/arm64/configs/defconfig +23 −1
  1290. arch/arm64/crypto/aes-ce-cipher.c +1 −1
  1291. arch/arm64/include/asm/acpi.h +5 −1
  1292. arch/arm64/include/asm/arch_gicv3.h +170 −0
  1293. arch/arm64/include/asm/assembler.h +11 −0
  1294. arch/arm64/include/asm/atomic.h +60 −5
  1295. arch/arm64/include/asm/atomic_ll_sc.h +61 −39
  1296. arch/arm64/include/asm/atomic_lse.h +117 −78
  1297. arch/arm64/include/asm/barrier.h +10 −6
  1298. arch/arm64/include/asm/cache.h +1 −1
  1299. arch/arm64/include/asm/cacheflush.h +7 −0
  1300. arch/arm64/include/asm/cachetype.h +2 −2
  1301. arch/arm64/include/asm/cmpxchg.h +136 −143
  1302. arch/arm64/include/asm/compat.h +1 −2
  1303. arch/arm64/include/asm/cpu.h +4 −0
  1304. arch/arm64/include/asm/cpufeature.h +85 −9
  1305. arch/arm64/include/asm/cputype.h +9 −21
  1306. arch/arm64/include/asm/dcc.h +55 −0
  1307. arch/arm64/include/asm/dma-mapping.h +10 −18
  1308. arch/arm64/include/asm/fixmap.h +2 −5
  1309. arch/arm64/include/asm/hw_breakpoint.h +7 −2
  1310. arch/arm64/include/asm/hwcap.h +8 −0
  1311. arch/arm64/include/asm/irq.h +0 −14
  1312. arch/arm64/include/asm/kasan.h +38 −0
  1313. arch/arm64/include/asm/kernel-pgtable.h +83 −0
  1314. arch/arm64/include/asm/kvm_arm.h +16 −0
  1315. arch/arm64/include/asm/kvm_host.h +4 −1
  1316. arch/arm64/include/asm/memory.h +3 −4
  1317. arch/arm64/include/asm/mmu.h +8 −7
  1318. arch/arm64/include/asm/mmu_context.h +25 −88
  1319. arch/arm64/include/asm/page.h +9 −18
  1320. arch/arm64/include/asm/pgalloc.h +1 −0
  1321. arch/arm64/include/asm/pgtable-hwdef.h +45 −3
  1322. arch/arm64/include/asm/pgtable.h +32 −6
  1323. arch/arm64/include/asm/pmu.h +0 −83
  1324. arch/arm64/include/asm/processor.h +1 −1
  1325. arch/arm64/include/asm/ptrace.h +8 −8
  1326. arch/arm64/include/asm/string.h +16 −0
  1327. arch/arm64/include/asm/sysreg.h +152 −5
  1328. arch/arm64/include/asm/thread_info.h +3 −2
  1329. arch/arm64/include/asm/tlb.h +15 −11
  1330. arch/arm64/include/asm/tlbflush.h +12 −6
  1331. arch/arm64/include/asm/unistd.h +1 −1
  1332. arch/arm64/include/asm/unistd32.h +9 −0
  1333. arch/arm64/include/uapi/asm/kvm.h +1 −1
  1334. arch/arm64/include/uapi/asm/signal.h +3 −0
  1335. arch/arm64/kernel/Makefile +8 −3
  1336. arch/arm64/kernel/acpi.c +24 −20
  1337. arch/arm64/kernel/arm64ksyms.c +3 −0
  1338. arch/arm64/kernel/armv8_deprecated.c +9 −7
  1339. arch/arm64/kernel/asm-offsets.c +1 −1
  1340. arch/arm64/kernel/cpu_errata.c +10 −1
  1341. arch/arm64/kernel/cpufeature.c +842 −24
  1342. arch/arm64/kernel/cpuinfo.c +129 −132
  1343. arch/arm64/kernel/debug-monitors.c +18 −15
  1344. arch/arm64/kernel/efi-entry.S +5 −5
  1345. arch/arm64/kernel/efi.c +14 −27
  1346. arch/arm64/kernel/entry-ftrace.S +20 −2
  1347. arch/arm64/kernel/entry.S +2 −0
  1348. arch/arm64/kernel/fpsimd.c +5 −11
  1349. arch/arm64/kernel/head.S +39 −39
  1350. arch/arm64/kernel/hw_breakpoint.c +17 −2
  1351. arch/arm64/kernel/image.h +37 −1
  1352. arch/arm64/kernel/insn.c +3 −3
  1353. arch/arm64/kernel/irq.c +0 −62
  1354. arch/arm64/kernel/module.c +13 −3
  1355. arch/arm64/kernel/perf_event.c +208 −858
  1356. arch/arm64/kernel/process.c +3 −0
  1357. arch/arm64/kernel/psci.c +0 −14
  1358. arch/arm64/kernel/setup.c +8 −239
  1359. arch/arm64/kernel/smp.c +14 −10
  1360. arch/arm64/kernel/stacktrace.c +1 −5
  1361. arch/arm64/kernel/suspend.c +24 −10
  1362. arch/arm64/kernel/time.c +1 −7
  1363. arch/arm64/kernel/traps.c +10 −5
  1364. arch/arm64/kernel/vdso/Makefile +3 −0
  1365. arch/arm64/kernel/vmlinux.lds.S +5 −1
  1366. arch/arm64/kvm/Kconfig +9 −0
  1367. arch/arm64/kvm/hyp.S +8 −0
  1368. arch/arm64/kvm/reset.c +1 −1
  1369. arch/arm64/kvm/sys_regs.c +6 −6
  1370. arch/arm64/lib/copy_from_user.S +44 −34
  1371. arch/arm64/lib/copy_in_user.S +38 −29
  1372. arch/arm64/lib/copy_template.S +193 −0
  1373. arch/arm64/lib/copy_to_user.S +38 −29
  1374. arch/arm64/lib/memchr.S +1 −1
  1375. arch/arm64/lib/memcmp.S +1 −1
  1376. arch/arm64/lib/memcpy.S +30 −154
  1377. arch/arm64/lib/memmove.S +6 −3
  1378. arch/arm64/lib/memset.S +4 −1
  1379. arch/arm64/lib/strcmp.S +1 −1
  1380. arch/arm64/lib/strlen.S +1 −1
  1381. arch/arm64/lib/strncmp.S +1 −1
  1382. arch/arm64/mm/Makefile +3 −0
  1383. arch/arm64/mm/cache.S +5 −5
  1384. arch/arm64/mm/context.c +143 −93
  1385. arch/arm64/mm/dma-mapping.c +468 −12
  1386. arch/arm64/mm/dump.c +17 −1
  1387. arch/arm64/mm/fault.c +2 −1
  1388. arch/arm64/mm/init.c +13 −6
  1389. arch/arm64/mm/kasan_init.c +165 −0
  1390. arch/arm64/mm/mmu.c +105 −60
  1391. arch/arm64/mm/pageattr.c +1 −1
  1392. arch/arm64/mm/pgd.c +0 −2
  1393. arch/arm64/mm/proc.S +9 −5
  1394. arch/arm64/net/bpf_jit.h +2 −1
  1395. arch/arm64/net/bpf_jit_comp.c +78 −26
  1396. arch/avr32/boards/atngw100/mrmt.c +0 −1
  1397. arch/avr32/include/asm/Kbuild +1 −0
  1398. arch/avr32/include/asm/atomic.h +2 −2
  1399. arch/avr32/mach-at32ap/at32ap700x.c +1 −8
  1400. arch/blackfin/include/asm/Kbuild +1 −0
  1401. arch/c6x/include/asm/Kbuild +1 −0
  1402. arch/c6x/platforms/megamod-pic.c +1 −1
  1403. arch/cris/Kconfig +0 −1
  1404. arch/cris/arch-v10/kernel/head.S +0 −106
  1405. arch/cris/arch-v10/kernel/kgdb.c +36 −53
  1406. arch/cris/arch-v10/mm/init.c +3 −11
  1407. arch/cris/arch-v32/Kconfig +0 −89
  1408. arch/cris/arch-v32/drivers/Kconfig +0 −167
  1409. arch/cris/arch-v32/drivers/Makefile +0 −1
  1410. arch/cris/arch-v32/drivers/axisflashmap.c +6 −34
  1411. arch/cris/arch-v32/drivers/i2c.c +0 −751
  1412. arch/cris/arch-v32/drivers/i2c.h +0 −16
  1413. arch/cris/arch-v32/drivers/mach-a3/Makefile +0 −1
  1414. arch/cris/arch-v32/drivers/mach-a3/gpio.c +0 −999
  1415. arch/cris/arch-v32/drivers/mach-fs/Makefile +0 −1
  1416. arch/cris/arch-v32/drivers/mach-fs/gpio.c +0 −978
  1417. arch/cris/arch-v32/kernel/crisksyms.c +0 −3
  1418. arch/cris/arch-v32/kernel/debugport.c +0 −2
  1419. arch/cris/arch-v32/kernel/head.S +0 −4
  1420. arch/cris/arch-v32/kernel/irq.c +3 −3
  1421. arch/cris/arch-v32/kernel/kgdb.c +38 −58
  1422. arch/cris/arch-v32/kernel/setup.c +0 −8
  1423. arch/cris/arch-v32/mach-a3/Makefile +1 −1
  1424. arch/cris/arch-v32/mach-a3/io.c +0 −149
  1425. arch/cris/arch-v32/mach-fs/Kconfig +0 −19
  1426. arch/cris/arch-v32/mach-fs/Makefile +1 −1
  1427. arch/cris/arch-v32/mach-fs/io.c +0 −191
  1428. arch/cris/boot/dts/artpec3.dtsi +46 −0
  1429. arch/cris/boot/dts/dev88.dts +49 −0
  1430. arch/cris/boot/dts/etraxfs.dtsi +8 −0
  1431. arch/cris/boot/dts/include/dt-bindings +1 −0
  1432. arch/cris/boot/dts/p1343.dts +76 −0
  1433. arch/cris/boot/rescue/head_v10.S +0 −3
  1434. arch/cris/include/arch-v32/arch/io.h +0 −140
  1435. arch/cris/include/arch-v32/arch/irq.h +1 −1
  1436. arch/cris/include/asm/Kbuild +1 −0
  1437. arch/cris/include/asm/eshlibld.h +1 −2
  1438. arch/cris/include/asm/io.h +2 −0
  1439. arch/cris/include/uapi/asm/etraxgpio.h +0 −157
  1440. arch/cris/kernel/crisksyms.c +0 −2
  1441. arch/cris/kernel/time.c +0 −25
  1442. arch/frv/include/asm/Kbuild +1 −0
  1443. arch/frv/include/asm/atomic.h +2 −2
  1444. arch/frv/include/asm/highmem.h +0 −2
  1445. arch/frv/mm/highmem.c +0 −5
  1446. arch/h8300/Kconfig +1 −0
  1447. arch/h8300/Makefile +2 −0
  1448. arch/h8300/boot/compressed/Makefile +3 −2
  1449. arch/h8300/boot/compressed/head.S +2 −2
  1450. arch/h8300/boot/compressed/misc.c +1 −6
  1451. arch/h8300/boot/compressed/vmlinux.lds +1 −1
  1452. arch/h8300/boot/dts/Makefile +3 −0
  1453. arch/h8300/boot/dts/edosk2674.dts +3 −3
  1454. arch/h8300/include/asm/Kbuild +1 −0
  1455. arch/h8300/include/asm/atomic.h +2 −2
  1456. arch/h8300/include/asm/io.h +6 −6
  1457. arch/h8300/include/asm/thread_info.h +6 −8
  1458. arch/h8300/kernel/setup.c +2 −0
  1459. arch/h8300/kernel/vmlinux.lds.S +2 −2
  1460. arch/hexagon/include/asm/Kbuild +1 −0
  1461. arch/hexagon/include/asm/atomic.h +1 −1
  1462. arch/ia64/include/asm/Kbuild +1 −0
  1463. arch/ia64/include/asm/atomic.h +4 −4
  1464. arch/ia64/include/asm/pci.h +0 −5
  1465. arch/ia64/include/asm/unistd.h +1 −1
  1466. arch/ia64/include/uapi/asm/unistd.h +1 −0
  1467. arch/ia64/kernel/entry.S +1 −0
  1468. arch/ia64/pci/pci.c +100 −268
  1469. arch/m32r/include/asm/Kbuild +1 −0
  1470. arch/m32r/include/asm/atomic.h +2 −2
  1471. arch/m68k/configs/amiga_defconfig +8 −1
  1472. arch/m68k/configs/apollo_defconfig +8 −1
  1473. arch/m68k/configs/atari_defconfig +8 −1
  1474. arch/m68k/configs/bvme6000_defconfig +8 −1
  1475. arch/m68k/configs/hp300_defconfig +8 −1
  1476. arch/m68k/configs/mac_defconfig +8 −1
  1477. arch/m68k/configs/multi_defconfig +8 −1
  1478. arch/m68k/configs/mvme147_defconfig +8 −1
  1479. arch/m68k/configs/mvme16x_defconfig +8 −1
  1480. arch/m68k/configs/q40_defconfig +8 −1
  1481. arch/m68k/configs/sun3_defconfig +8 −1
  1482. arch/m68k/configs/sun3x_defconfig +8 −1
  1483. arch/m68k/emu/nfblock.c +2 −1
  1484. arch/m68k/include/asm/atomic.h +2 −2
  1485. arch/m68k/include/asm/linkage.h +30 −0
  1486. arch/m68k/include/asm/unistd.h +1 −1
  1487. arch/m68k/include/uapi/asm/unistd.h +19 −0
  1488. arch/m68k/kernel/syscalltable.S +19 −1
  1489. arch/m68k/mac/psc.c +1 −0
  1490. arch/m68k/sun3/idprom.c +1 −4
  1491. arch/metag/Makefile +1 −1
  1492. arch/metag/boot/dts/Makefile +3 −4
  1493. arch/metag/include/asm/Kbuild +1 −0
  1494. arch/metag/include/asm/atomic_lnkget.h +1 −1
  1495. arch/metag/include/asm/atomic_lock1.h +1 −1
  1496. arch/metag/include/asm/highmem.h +0 −1
  1497. arch/metag/include/asm/irq.h +6 −2
  1498. arch/metag/kernel/smp.c +2 −0
  1499. arch/metag/mm/highmem.c +0 −14
  1500. arch/microblaze/include/asm/Kbuild +1 −0
  1501. arch/microblaze/include/asm/highmem.h +0 −13
  1502. arch/microblaze/kernel/setup.c +1 −1
  1503. arch/mips/Kbuild +1 −0
  1504. arch/mips/Kbuild.platforms +1 −0
  1505. arch/mips/Kconfig +84 −4
  1506. arch/mips/Kconfig.debug +72 −0
  1507. arch/mips/Makefile +4 −0
  1508. arch/mips/ath79/irq.c +20 −2
  1509. arch/mips/ath79/setup.c +6 −1
  1510. arch/mips/bcm47xx/Kconfig +1 −0
  1511. arch/mips/bcm47xx/setup.c +18 −1
  1512. arch/mips/bcm47xx/sprom.c +22 −24
  1513. arch/mips/bcm63xx/boards/board_bcm963xx.c +7 −7
  1514. arch/mips/bcm63xx/cpu.c +6 −6
  1515. arch/mips/bcm63xx/dev-pcmcia.c +1 −1
  1516. arch/mips/bcm63xx/dev-spi.c +2 −40
  1517. arch/mips/bcm63xx/irq.c +1 −1
  1518. arch/mips/bcm63xx/setup.c +4 −4
  1519. arch/mips/bcm63xx/timer.c +1 −1
  1520. arch/mips/bmips/setup.c +0 −1
  1521. arch/mips/boot/dts/Makefile +4 −0
  1522. arch/mips/boot/dts/brcm/bcm7346.dtsi +112 −2
  1523. arch/mips/boot/dts/brcm/bcm7358.dtsi +60 −2
  1524. arch/mips/boot/dts/brcm/bcm7360.dtsi +60 −2
  1525. arch/mips/boot/dts/brcm/bcm7362.dtsi +92 −2
  1526. arch/mips/boot/dts/brcm/bcm7425.dtsi +42 −0
  1527. arch/mips/boot/dts/brcm/bcm97346dbsmb.dts +28 −0
  1528. arch/mips/boot/dts/brcm/bcm97358svmb.dts +16 −0
  1529. arch/mips/boot/dts/brcm/bcm97360svmb.dts +16 −0
  1530. arch/mips/boot/dts/brcm/bcm97362svmb.dts +20 −0
  1531. arch/mips/boot/dts/mti/malta.dts +4 −0
  1532. arch/mips/boot/dts/qca/ar9132.dtsi +1 −1
  1533. arch/mips/boot/dts/xilfpga/Makefile +9 −0
  1534. arch/mips/boot/dts/xilfpga/microAptiv.dtsi +21 −0
  1535. arch/mips/boot/dts/xilfpga/nexys4ddr.dts +46 −0
  1536. arch/mips/cavium-octeon/octeon-irq.c +2 −2
  1537. arch/mips/cavium-octeon/setup.c +10 −3
  1538. arch/mips/configs/bigsur_defconfig +6 −6
  1539. arch/mips/configs/bmips_be_defconfig +2 −1
  1540. arch/mips/configs/bmips_stb_defconfig +2 −1
  1541. arch/mips/configs/capcella_defconfig +3 −3
  1542. arch/mips/configs/e55_defconfig +3 −3
  1543. arch/mips/configs/fuloong2e_defconfig +5 −9
  1544. arch/mips/configs/lasat_defconfig +5 −5
  1545. arch/mips/configs/lemote2f_defconfig +3 −8
  1546. arch/mips/configs/malta_defconfig +2 −4
  1547. arch/mips/configs/malta_kvm_defconfig +9 −7
  1548. arch/mips/configs/malta_kvm_guest_defconfig +9 −7
  1549. arch/mips/configs/malta_qemu_32r6_defconfig +5 −6
  1550. arch/mips/configs/maltaaprp_defconfig +5 −6
  1551. arch/mips/configs/maltasmvp_eva_defconfig +5 −6
  1552. arch/mips/configs/maltaup_defconfig +5 −6
  1553. arch/mips/configs/maltaup_xpa_defconfig +9 −7
  1554. arch/mips/configs/mpc30x_defconfig +3 −3
  1555. arch/mips/configs/pistachio_defconfig +0 −1
  1556. arch/mips/configs/xilfpga_defconfig +40 −0
  1557. arch/mips/include/asm/Kbuild +1 −0
  1558. arch/mips/include/asm/abi.h +3 −2
  1559. arch/mips/include/asm/atomic.h +5 −5
  1560. arch/mips/include/asm/bcache.h +27 −0
  1561. arch/mips/include/asm/cdmm.h +11 −0
  1562. arch/mips/include/asm/clocksource.h +29 −0
  1563. arch/mips/include/asm/compat.h +34 −28
  1564. arch/mips/include/asm/cpu-features.h +4 −5
  1565. arch/mips/include/asm/cpu.h +1 −0
  1566. arch/mips/include/asm/debug.h +22 −0
  1567. arch/mips/include/asm/elf.h +7 −0
  1568. arch/mips/include/asm/fw/fw.h +0 −16
  1569. arch/mips/include/asm/highmem.h +0 −1
  1570. arch/mips/include/asm/io.h +1 −0
  1571. arch/mips/include/asm/kvm_host.h +2 −0
  1572. arch/mips/include/asm/maar.h +9 −0
  1573. arch/mips/include/asm/mach-bcm47xx/bcm47xx.h +0 −5
  1574. arch/mips/include/asm/mach-bcm63xx/bcm63xx_dev_spi.h +0 −44
  1575. arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h +14 −0
  1576. arch/mips/include/asm/mach-malta/malta-dtshim.h +29 −0
  1577. arch/mips/include/asm/mach-ralink/mt7620.h +1 −7
  1578. arch/mips/include/asm/mach-ralink/ralink_regs.h +17 −0
  1579. arch/mips/include/asm/mach-ralink/rt305x.h +6 −15
  1580. arch/mips/include/asm/mach-xilfpga/irq.h +18 −0
  1581. arch/mips/include/asm/mips-cm.h +109 −8
  1582. arch/mips/include/asm/mips-cpc.h +2 −1
  1583. arch/mips/include/asm/mipsregs.h +11 −9
  1584. arch/mips/include/asm/page.h +3 −2
  1585. arch/mips/include/asm/processor.h +1 −7
  1586. arch/mips/include/asm/vdso.h +123 −16
  1587. arch/mips/include/uapi/asm/Kbuild +1 −1
  1588. arch/mips/include/uapi/asm/auxvec.h +17 −0
  1589. arch/mips/include/uapi/asm/mman.h +6 −0
  1590. arch/mips/include/uapi/asm/swab.h +7 −12
  1591. arch/mips/include/uapi/asm/unistd.h +15 −6
  1592. arch/mips/jz4740/board-qi_lb60.c +9 −5
  1593. arch/mips/jz4740/gpio.c +1 −0
  1594. arch/mips/kernel/Makefile +1 −0
  1595. arch/mips/kernel/cps-vec-ns16550.S +202 −0
  1596. arch/mips/kernel/cps-vec.S +43 −13
  1597. arch/mips/kernel/cpu-probe.c +14 −10
  1598. arch/mips/kernel/csrc-r4k.c +44 −0
  1599. arch/mips/kernel/idle.c +14 −3
  1600. arch/mips/kernel/mips-cm.c +83 −31
  1601. arch/mips/kernel/mips-cpc.c +6 −0
  1602. arch/mips/kernel/mips-r2-to-r6-emul.c +1 −1
  1603. arch/mips/kernel/octeon_switch.S +1 −25
  1604. arch/mips/kernel/r2300_switch.S +1 −27
  1605. arch/mips/kernel/scall32-o32.S +19 −23
  1606. arch/mips/kernel/scall64-64.S +19 −22
  1607. arch/mips/kernel/scall64-n32.S +8 −14
  1608. arch/mips/kernel/scall64-o32.S +8 −14
  1609. arch/mips/kernel/segment.c +1 −1
  1610. arch/mips/kernel/setup.c +31 −8
  1611. arch/mips/kernel/signal.c +5 −7
  1612. arch/mips/kernel/signal32.c +2 −5
  1613. arch/mips/kernel/signal_n32.c +2 −3
  1614. arch/mips/kernel/smp-cps.c +30 −5
  1615. arch/mips/kernel/smp-gic.c +2 −0
  1616. arch/mips/kernel/smp.c +2 −0
  1617. arch/mips/kernel/spinlock_test.c +1 −3
  1618. arch/mips/kernel/stacktrace.c +15 −12
  1619. arch/mips/kernel/traps.c +5 −6
  1620. arch/mips/kernel/unaligned.c +1 −1
  1621. arch/mips/kernel/vdso.c +130 −77
  1622. arch/mips/kernel/vmlinux.lds.S +14 −1
  1623. arch/mips/kvm/locore.S +0 −8
  1624. arch/mips/lantiq/clk.c +17 −0
  1625. arch/mips/lantiq/clk.h +13 −0
  1626. arch/mips/lantiq/irq.c +4 −4
  1627. arch/mips/lantiq/prom.c +0 −2
  1628. arch/mips/lantiq/xway/clk.c +170 −10
  1629. arch/mips/lantiq/xway/prom.c +33 −2
  1630. arch/mips/lantiq/xway/reset.c +175 −21
  1631. arch/mips/lantiq/xway/sysctrl.c +262 −39
  1632. arch/mips/lib/Makefile +1 −1
  1633. arch/mips/lib/bswapdi.c +15 −0
  1634. arch/mips/lib/bswapsi.c +11 −0
  1635. arch/mips/loongson64/Kconfig +0 −5
  1636. arch/mips/loongson64/common/Makefile +1 −1
  1637. arch/mips/loongson64/common/env.c +3 −0
  1638. arch/mips/loongson64/lemote-2f/Makefile +1 −1
  1639. arch/mips/math-emu/me-debugfs.c +1 −1
  1640. arch/mips/mm/Makefile +1 −0
  1641. arch/mips/mm/dma-default.c +1 −1
  1642. arch/mips/mm/highmem.c +0 −13
  1643. arch/mips/mm/init.c +114 −63
  1644. arch/mips/mm/sc-debugfs.c +81 −0
  1645. arch/mips/mm/sc-mips.c +62 −3
  1646. arch/mips/mm/tlbex.c +62 −35
  1647. arch/mips/mti-malta/Makefile +12 −3
  1648. arch/mips/mti-malta/malta-dtshim.c +162 −0
  1649. arch/mips/mti-malta/malta-init.c +1 −0
  1650. arch/mips/mti-malta/malta-memory.c +2 −129
  1651. arch/mips/mti-malta/malta-setup.c +4 −1
  1652. arch/mips/mti-sead3/Makefile +0 −2
  1653. arch/mips/net/bpf_jit.c +1 −1
  1654. arch/mips/net/bpf_jit_asm.S +54 −9
  1655. arch/mips/netlogic/xlp/dt.c +0 −1
  1656. arch/mips/pci/pci-rt3883.c +2 −4
  1657. arch/mips/pistachio/init.c +0 −1
  1658. arch/mips/pistachio/time.c +1 −1
  1659. arch/mips/ralink/cevt-rt3352.c +1 −1
  1660. arch/mips/ralink/clk.c +1 −1
  1661. arch/mips/ralink/early_printk.c +26 −0
  1662. arch/mips/ralink/mt7620.c +50 −13
  1663. arch/mips/ralink/of.c +0 −2
  1664. arch/mips/ralink/prom.c +5 −0
  1665. arch/mips/ralink/reset.c +10 −3
  1666. arch/mips/ralink/rt288x.c +1 −0
  1667. arch/mips/ralink/rt305x.c +6 −7
  1668. arch/mips/ralink/rt3883.c +2 −0
  1669. arch/mips/txx9/generic/spi_eeprom.c +0 −1
  1670. arch/mips/vdso/.gitignore +4 −0
  1671. arch/mips/vdso/Makefile +160 −0
  1672. arch/mips/vdso/elf.S +68 −0
  1673. arch/mips/vdso/genvdso.c +293 −0
  1674. arch/mips/vdso/genvdso.h +187 −0
  1675. arch/mips/vdso/gettimeofday.c +232 −0
  1676. arch/mips/vdso/sigreturn.S +49 −0
  1677. arch/mips/vdso/vdso.h +89 −0
  1678. arch/mips/vdso/vdso.lds.S +105 −0
  1679. arch/mips/xilfpga/Kconfig +9 −0
  1680. arch/mips/xilfpga/Makefile +7 −0
  1681. arch/mips/xilfpga/Platform +3 −0
  1682. arch/mips/xilfpga/init.c +57 −0
  1683. arch/mips/xilfpga/intc.c +25 −0
  1684. arch/mips/xilfpga/time.c +41 −0
  1685. arch/mn10300/include/asm/Kbuild +1 −0
  1686. arch/mn10300/include/asm/atomic.h +2 −2
  1687. arch/nios2/include/asm/Kbuild +1 −0
  1688. arch/nios2/include/asm/cmpxchg.h +0 −47
  1689. arch/nios2/kernel/setup.c +1 −1
  1690. arch/nios2/kernel/time.c +1 −1
  1691. arch/nios2/lib/memmove.c +0 −2
  1692. arch/nios2/lib/memset.c +0 −2
  1693. arch/parisc/Kconfig +3 −0
  1694. arch/parisc/include/asm/atomic.h +1 −1
  1695. arch/parisc/include/asm/cache.h +5 −13
  1696. arch/parisc/include/asm/cacheflush.h +0 −1
  1697. arch/parisc/include/asm/compat.h +2 −2
  1698. arch/parisc/include/asm/hugetlb.h +85 −0
  1699. arch/parisc/include/asm/page.h +12 −1
  1700. arch/parisc/include/asm/pgalloc.h +1 −1
  1701. arch/parisc/include/asm/pgtable.h +22 −4
  1702. arch/parisc/include/asm/processor.h +0 −27
  1703. arch/parisc/include/uapi/asm/ipcbuf.h +12 −7
  1704. arch/parisc/include/uapi/asm/mman.h +3 −10
  1705. arch/parisc/include/uapi/asm/msgbuf.h +5 −5
  1706. arch/parisc/include/uapi/asm/posix_types.h +2 −0
  1707. arch/parisc/include/uapi/asm/sembuf.h +3 −3
  1708. arch/parisc/include/uapi/asm/shmbuf.h +4 −4
  1709. arch/parisc/include/uapi/asm/stat.h +0 −31
  1710. arch/parisc/include/uapi/asm/unistd.h +3 −1
  1711. arch/parisc/kernel/asm-offsets.c +8 −0
  1712. arch/parisc/kernel/entry.S +34 −22
  1713. arch/parisc/kernel/head.S +2 −2
  1714. arch/parisc/kernel/setup.c +13 −1
  1715. arch/parisc/kernel/syscall.S +2 −2
  1716. arch/parisc/kernel/syscall_table.S +2 −0
  1717. arch/parisc/kernel/traps.c +15 −20
  1718. arch/parisc/kernel/vmlinux.lds.S +6 −3
  1719. arch/parisc/mm/Makefile +1 −0
  1720. arch/parisc/mm/hugetlbpage.c +161 −0
  1721. arch/parisc/mm/init.c +33 −23
  1722. arch/powerpc/Kconfig +1 −1
  1723. arch/powerpc/Makefile +4 −2
  1724. arch/powerpc/boot/Makefile +3 −0
  1725. arch/powerpc/boot/dts/fsl/b4420qds.dts +2 −2
  1726. arch/powerpc/boot/dts/fsl/b4420si-post.dtsi +3 −1
  1727. arch/powerpc/boot/dts/fsl/b4420si-pre.dtsi +9 −4
  1728. arch/powerpc/boot/dts/fsl/b4860qds.dts +2 −2
  1729. arch/powerpc/boot/dts/fsl/b4860si-post.dtsi +22 −4
  1730. arch/powerpc/boot/dts/fsl/b4860si-pre.dtsi +15 −5
  1731. arch/powerpc/boot/dts/fsl/b4qds.dtsi +1 −1
  1732. arch/powerpc/boot/dts/fsl/b4si-post.dtsi +28 −5
  1733. arch/powerpc/boot/dts/fsl/bsc9131rdb.dts +2 −2
  1734. arch/powerpc/boot/dts/fsl/bsc9131rdb.dtsi +12 −0
  1735. arch/powerpc/boot/dts/fsl/bsc9132qds.dts +2 −2
  1736. arch/powerpc/boot/dts/fsl/bsc9132qds.dtsi +12 −0
  1737. arch/powerpc/boot/dts/fsl/c293pcie.dts +2 −2
  1738. arch/powerpc/boot/dts/fsl/cyrus_p5020.dts +155 −0
  1739. arch/powerpc/boot/dts/fsl/ge_imp3a.dts +2 −2
  1740. arch/powerpc/boot/dts/fsl/kmcoge4.dts +2 −2
  1741. arch/powerpc/boot/dts/fsl/mpc8536ds.dts +2 −2
  1742. arch/powerpc/boot/dts/fsl/mpc8536ds.dtsi +0 −0
  1743. arch/powerpc/boot/dts/fsl/mpc8536ds_36b.dts +2 −2
  1744. arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi +1 −1
  1745. arch/powerpc/boot/dts/fsl/mpc8540ads.dts +1 −1
  1746. arch/powerpc/boot/dts/fsl/mpc8541cds.dts +1 −1
  1747. arch/powerpc/boot/dts/fsl/mpc8544ds.dts +2 −2
  1748. arch/powerpc/boot/dts/fsl/mpc8544ds.dtsi +0 −0
  1749. arch/powerpc/boot/dts/fsl/mpc8548cds.dtsi +0 −0
  1750. arch/powerpc/boot/dts/fsl/mpc8548cds_32b.dts +2 −2
  1751. arch/powerpc/boot/dts/fsl/mpc8548cds_36b.dts +2 −2
  1752. arch/powerpc/boot/dts/fsl/mpc8555cds.dts +1 −1
  1753. arch/powerpc/boot/dts/fsl/mpc8560ads.dts +1 −1
  1754. arch/powerpc/boot/dts/fsl/mpc8568mds.dts +2 −2
  1755. arch/powerpc/boot/dts/fsl/mpc8569mds.dts +2 −2
  1756. arch/powerpc/boot/dts/fsl/mpc8572ds.dts +2 −2
  1757. arch/powerpc/boot/dts/fsl/mpc8572ds.dtsi +0 −0
  1758. arch/powerpc/boot/dts/fsl/mpc8572ds_36b.dts +2 −2
  1759. arch/powerpc/boot/dts/fsl/mpc8572ds_camp_core0.dts +0 −0
  1760. arch/powerpc/boot/dts/fsl/mpc8572ds_camp_core1.dts +0 −0
  1761. arch/powerpc/boot/dts/fsl/mpc8572si-post.dtsi +1 −1
  1762. arch/powerpc/boot/dts/fsl/mvme2500.dts +2 −2
  1763. arch/powerpc/boot/dts/fsl/oca4080.dts +2 −2
  1764. arch/powerpc/boot/dts/fsl/p1010rdb-pa.dts +2 −2
  1765. arch/powerpc/boot/dts/fsl/p1010rdb-pa.dtsi +0 −0
  1766. arch/powerpc/boot/dts/fsl/p1010rdb-pa_36b.dts +2 −2
  1767. arch/powerpc/boot/dts/fsl/p1010rdb-pb.dts +2 −2
  1768. arch/powerpc/boot/dts/fsl/p1010rdb-pb_36b.dts +2 −2
  1769. arch/powerpc/boot/dts/fsl/p1010rdb.dtsi +12 −0
  1770. arch/powerpc/boot/dts/fsl/p1010rdb_32b.dtsi +0 −0
  1771. arch/powerpc/boot/dts/fsl/p1010rdb_36b.dtsi +0 −0
  1772. arch/powerpc/boot/dts/fsl/p1020mbg-pc.dtsi +0 −0
  1773. arch/powerpc/boot/dts/fsl/p1020mbg-pc_32b.dts +2 −2
  1774. arch/powerpc/boot/dts/fsl/p1020mbg-pc_36b.dts +2 −2
  1775. arch/powerpc/boot/dts/fsl/p1020rdb-pc.dtsi +0 −0
  1776. arch/powerpc/boot/dts/fsl/p1020rdb-pc_32b.dts +2 −2
  1777. arch/powerpc/boot/dts/fsl/p1020rdb-pc_36b.dts +2 −2
  1778. arch/powerpc/boot/dts/fsl/p1020rdb-pc_camp_core0.dts +0 −0
  1779. arch/powerpc/boot/dts/fsl/p1020rdb-pc_camp_core1.dts +0 −0
  1780. arch/powerpc/boot/dts/fsl/p1020rdb-pd.dts +14 −2
  1781. arch/powerpc/boot/dts/fsl/p1020rdb.dts +2 −2
  1782. arch/powerpc/boot/dts/fsl/p1020rdb.dtsi +0 −0
  1783. arch/powerpc/boot/dts/fsl/p1020rdb_36b.dts +2 −2
  1784. arch/powerpc/boot/dts/fsl/p1020utm-pc.dtsi +0 −0
  1785. arch/powerpc/boot/dts/fsl/p1020utm-pc_32b.dts +2 −2
  1786. arch/powerpc/boot/dts/fsl/p1020utm-pc_36b.dts +2 −2
  1787. arch/powerpc/boot/dts/fsl/p1021mds.dts +2 −2
  1788. arch/powerpc/boot/dts/fsl/p1021rdb-pc.dtsi +12 −0
  1789. arch/powerpc/boot/dts/fsl/p1021rdb-pc_32b.dts +2 −2
  1790. arch/powerpc/boot/dts/fsl/p1021rdb-pc_36b.dts +2 −2
  1791. arch/powerpc/boot/dts/fsl/p1022ds.dtsi +12 −0
  1792. arch/powerpc/boot/dts/fsl/p1022ds_32b.dts +2 −2
  1793. arch/powerpc/boot/dts/fsl/p1022ds_36b.dts +2 −2
  1794. arch/powerpc/boot/dts/fsl/p1022rdk.dts +2 −2
  1795. arch/powerpc/boot/dts/fsl/p1022si-post.dtsi +2 −0
  1796. arch/powerpc/boot/dts/fsl/p1023rdb.dts +2 −2
  1797. arch/powerpc/boot/dts/fsl/p1024rdb.dtsi +0 −0
  1798. arch/powerpc/boot/dts/fsl/p1024rdb_32b.dts +2 −2
  1799. arch/powerpc/boot/dts/fsl/p1024rdb_36b.dts +2 −2
  1800. arch/powerpc/boot/dts/fsl/p1025rdb.dtsi +0 −0
  1801. arch/powerpc/boot/dts/fsl/p1025rdb_32b.dts +2 −2
  1802. arch/powerpc/boot/dts/fsl/p1025rdb_36b.dts +2 −2
  1803. arch/powerpc/boot/dts/fsl/p1025twr.dts +2 −2
  1804. arch/powerpc/boot/dts/fsl/p1025twr.dtsi +12 −0
  1805. arch/powerpc/boot/dts/fsl/p2020ds.dts +2 −2
  1806. arch/powerpc/boot/dts/fsl/p2020ds.dtsi +0 −0
  1807. arch/powerpc/boot/dts/fsl/p2020rdb-pc.dtsi +6 −6
  1808. arch/powerpc/boot/dts/fsl/p2020rdb-pc_32b.dts +2 −2
  1809. arch/powerpc/boot/dts/fsl/p2020rdb-pc_36b.dts +2 −2
  1810. arch/powerpc/boot/dts/fsl/p2020rdb.dts +2 −2
  1811. arch/powerpc/boot/dts/fsl/p2041rdb.dts +2 −2
  1812. arch/powerpc/boot/dts/fsl/p2041si-post.dtsi +28 −1
  1813. arch/powerpc/boot/dts/fsl/p2041si-pre.dtsi +9 −1
  1814. arch/powerpc/boot/dts/fsl/p3041ds.dts +2 −2
  1815. arch/powerpc/boot/dts/fsl/p3041si-post.dtsi +28 −1
  1816. arch/powerpc/boot/dts/fsl/p3041si-pre.dtsi +9 −1
  1817. arch/powerpc/boot/dts/fsl/p4080ds.dts +2 −2
  1818. arch/powerpc/boot/dts/fsl/p4080si-post.dtsi +47 −1
  1819. arch/powerpc/boot/dts/fsl/p4080si-pre.dtsi +14 −1
  1820. arch/powerpc/boot/dts/fsl/p5020ds.dts +2 −2
  1821. arch/powerpc/boot/dts/fsl/p5020si-post.dtsi +28 −1
  1822. arch/powerpc/boot/dts/fsl/p5020si-pre.dtsi +9 −1
  1823. arch/powerpc/boot/dts/fsl/p5040ds.dts +2 −2
  1824. arch/powerpc/boot/dts/fsl/p5040si-post.dtsi +55 −1
  1825. arch/powerpc/boot/dts/fsl/p5040si-pre.dtsi +16 −1
  1826. arch/powerpc/boot/dts/fsl/ppa8548.dts +2 −2
  1827. arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi +2 −1
  1828. arch/powerpc/boot/dts/fsl/qoriq-clockgen2.dtsi +2 −1
  1829. arch/powerpc/boot/dts/fsl/qoriq-fman-0-10g-0.dtsi +62 −0
  1830. arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-0.dtsi +69 −0
  1831. arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-1.dtsi +68 −0
  1832. arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-2.dtsi +68 −0
  1833. arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-3.dtsi +68 −0
  1834. arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-4.dtsi +68 −0
  1835. arch/powerpc/boot/dts/fsl/qoriq-fman-0.dtsi +101 −0
  1836. arch/powerpc/boot/dts/fsl/qoriq-fman-1-10g-0.dtsi +61 −0
  1837. arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-0.dtsi +68 −0
  1838. arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-1.dtsi +68 −0
  1839. arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-2.dtsi +68 −0
  1840. arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-3.dtsi +68 −0
  1841. arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-4.dtsi +68 −0
  1842. arch/powerpc/boot/dts/fsl/qoriq-fman-1.dtsi +101 −0
  1843. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-0-best-effort.dtsi +66 −0
  1844. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-0.dtsi +63 −0
  1845. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-1-best-effort.dtsi +66 −0
  1846. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-1.dtsi +63 −0
  1847. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-0.dtsi +62 −0
  1848. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-1.dtsi +62 −0
  1849. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-2.dtsi +62 −0
  1850. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-3.dtsi +62 −0
  1851. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-4.dtsi +62 −0
  1852. arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-5.dtsi +62 −0
  1853. arch/powerpc/boot/dts/fsl/qoriq-fman3-0.dtsi +106 −0
  1854. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-10g-0.dtsi +63 −0
  1855. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-10g-1.dtsi +63 −0
  1856. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-0.dtsi +62 −0
  1857. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-1.dtsi +62 −0
  1858. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-2.dtsi +62 −0
  1859. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-3.dtsi +62 −0
  1860. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-4.dtsi +62 −0
  1861. arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-5.dtsi +62 −0
  1862. arch/powerpc/boot/dts/fsl/qoriq-fman3-1.dtsi +106 −0
  1863. arch/powerpc/boot/dts/fsl/qoriq-fman3l-0.dtsi +94 −0
  1864. arch/powerpc/boot/dts/fsl/t1023rdb.dts +2 −2
  1865. arch/powerpc/boot/dts/fsl/t1023si-post.dtsi +19 −0
  1866. arch/powerpc/boot/dts/fsl/t1024qds.dts +2 −2
  1867. arch/powerpc/boot/dts/fsl/t1024rdb.dts +2 −2
  1868. arch/powerpc/boot/dts/fsl/t102xsi-pre.dtsi +6 −0
  1869. arch/powerpc/boot/dts/fsl/t1040d4rdb.dts +2 −2
  1870. arch/powerpc/boot/dts/fsl/t1040qds.dts +2 −2
  1871. arch/powerpc/boot/dts/fsl/t1040rdb.dts +2 −2
  1872. arch/powerpc/boot/dts/fsl/t1040si-post.dtsi +31 −0
  1873. arch/powerpc/boot/dts/fsl/t1042d4rdb.dts +2 −2
  1874. arch/powerpc/boot/dts/fsl/t1042qds.dts +2 −2
  1875. arch/powerpc/boot/dts/fsl/t1042rdb.dts +2 −2
  1876. arch/powerpc/boot/dts/fsl/t1042rdb_pi.dts +2 −2
  1877. arch/powerpc/boot/dts/fsl/t104xd4rdb.dtsi +10 −0
  1878. arch/powerpc/boot/dts/fsl/t104xqds.dtsi +0 −0
  1879. arch/powerpc/boot/dts/fsl/t104xrdb.dtsi +0 −0
  1880. arch/powerpc/boot/dts/fsl/t104xsi-pre.dtsi +8 −1
  1881. arch/powerpc/boot/dts/fsl/t2080qds.dts +2 −2
  1882. arch/powerpc/boot/dts/fsl/t2080rdb.dts +2 −2
  1883. arch/powerpc/boot/dts/fsl/t2081qds.dts +2 −2
  1884. arch/powerpc/boot/dts/fsl/t2081si-post.dtsi +43 −0
  1885. arch/powerpc/boot/dts/fsl/t208xqds.dtsi +0 −0
  1886. arch/powerpc/boot/dts/fsl/t208xrdb.dtsi +0 −0
  1887. arch/powerpc/boot/dts/fsl/t208xsi-pre.dtsi +11 −0
  1888. arch/powerpc/boot/dts/fsl/t4240qds.dts +2 −2
  1889. arch/powerpc/boot/dts/fsl/t4240rdb.dts +2 −2
  1890. arch/powerpc/boot/dts/fsl/t4240si-post.dtsi +87 −1
  1891. arch/powerpc/boot/dts/fsl/t4240si-pre.dtsi +21 −1
  1892. arch/powerpc/boot/dts/mpc5121.dtsi +9 −2
  1893. arch/powerpc/boot/dts/mpc5125twr.dts +10 −1
  1894. arch/powerpc/boot/dts/prpmc2800.dts +0 −297
  1895. arch/powerpc/boot/page.h +2 −2
  1896. arch/powerpc/boot/prpmc2800.c +0 −571
  1897. arch/powerpc/boot/wrapper +21 −4
  1898. arch/powerpc/configs/cell_defconfig +1 −1
  1899. arch/powerpc/configs/mpc512x_defconfig +1 −0
  1900. arch/powerpc/configs/ppc64_defconfig +1 −1
  1901. arch/powerpc/configs/ps3_defconfig +1 −6
  1902. arch/powerpc/configs/pseries_defconfig +1 −1
  1903. arch/powerpc/include/asm/cache.h +0 −7
  1904. arch/powerpc/include/asm/disassemble.h +5 −0
  1905. arch/powerpc/include/asm/exception-64e.h +8 −7
  1906. arch/powerpc/include/asm/highmem.h +0 −13
  1907. arch/powerpc/include/asm/kvm_host.h +2 −2
  1908. arch/powerpc/include/asm/machdep.h +7 −2
  1909. arch/powerpc/include/asm/mmu-hash64.h +1 −0
  1910. arch/powerpc/include/asm/mpc5121.h +59 −0
  1911. arch/powerpc/include/asm/mpc52xx_psc.h +0 −2
  1912. arch/powerpc/include/asm/msi_bitmap.h +1 −0
  1913. arch/powerpc/include/asm/page.h +25 −7
  1914. arch/powerpc/include/asm/pgtable-ppc64.h +9 −1
  1915. arch/powerpc/include/asm/pgtable.h +3 −3
  1916. arch/powerpc/include/asm/ppc-opcode.h +0 −17
  1917. arch/powerpc/include/asm/reg.h +0 −1
  1918. arch/powerpc/include/asm/reg_booke.h +6 −0
  1919. arch/powerpc/include/asm/systbl.h +13 −0
  1920. arch/powerpc/include/asm/unistd.h +1 −1
  1921. arch/powerpc/include/asm/word-at-a-time.h +5 −0
  1922. arch/powerpc/include/uapi/asm/mman.h +1 −0
  1923. arch/powerpc/include/uapi/asm/unistd.h +13 −0
  1924. arch/powerpc/kernel/crash.c +3 −3
  1925. arch/powerpc/kernel/dma.c +1 −1
  1926. arch/powerpc/kernel/eeh.c +4 −4
  1927. arch/powerpc/kernel/eeh_driver.c +22 −5
  1928. arch/powerpc/kernel/exceptions-64e.S +11 −6
  1929. arch/powerpc/kernel/head_64.S +39 −4
  1930. arch/powerpc/kernel/io-workarounds.c +1 −1
  1931. arch/powerpc/kernel/machine_kexec_64.c +18 −0
  1932. arch/powerpc/kernel/misc_64.S +59 −1
  1933. arch/powerpc/kernel/nvram_64.c +8 −7
  1934. arch/powerpc/kernel/paca.c +7 −2
  1935. arch/powerpc/kernel/pci-common.c +1 −0
  1936. arch/powerpc/kernel/prom.c +10 −8
  1937. arch/powerpc/kernel/prom_init.c +30 −10
  1938. arch/powerpc/kernel/rtas.c +3 −0
  1939. arch/powerpc/kernel/setup_64.c +24 −1
  1940. arch/powerpc/kernel/vdso32/Makefile +1 −1
  1941. arch/powerpc/kernel/vdso32/datapage.S +7 −5
  1942. arch/powerpc/kernel/vdso64/Makefile +1 −1
  1943. arch/powerpc/kernel/vdso64/datapage.S +7 −5
  1944. arch/powerpc/kernel/vmlinux.lds.S +6 −0
  1945. arch/powerpc/kvm/book3s_64_mmu_hv.c +3 −2
  1946. arch/powerpc/kvm/book3s_hv.c +2 −55
  1947. arch/powerpc/kvm/book3s_hv_rm_mmu.c +7 −3
  1948. arch/powerpc/kvm/book3s_hv_rmhandlers.S +34 −15
  1949. arch/powerpc/kvm/e500.c +2 −1
  1950. arch/powerpc/kvm/e500_emulate.c +19 −0
  1951. arch/powerpc/kvm/e500_mmu_host.c +3 −3
  1952. arch/powerpc/kvm/powerpc.c +3 −0
  1953. arch/powerpc/mm/fsl_booke_mmu.c +17 −9
  1954. arch/powerpc/mm/hash_native_64.c +11 −12
  1955. arch/powerpc/mm/hash_utils_64.c +4 −3
  1956. arch/powerpc/mm/hugetlbpage.c +35 −5
  1957. arch/powerpc/mm/mmu_decl.h +3 −1
  1958. arch/powerpc/mm/numa.c +2 −5
  1959. arch/powerpc/mm/slb.c +27 −22
  1960. arch/powerpc/mm/tlb_hash64.c +5 −4
  1961. arch/powerpc/mm/tlb_low_64e.S +17 −8
  1962. arch/powerpc/mm/tlb_nohash.c +34 −7
  1963. arch/powerpc/mm/tlb_nohash_low.S +63 −0
  1964. arch/powerpc/net/bpf_jit_comp.c +1 −1
  1965. arch/powerpc/perf/callchain.c +1 −1
  1966. arch/powerpc/perf/core-book3s.c +30 −6
  1967. arch/powerpc/perf/hv-24x7.c +164 −2
  1968. arch/powerpc/perf/power8-pmu.c +3 −0
  1969. arch/powerpc/platforms/512x/Kconfig +6 −0
  1970. arch/powerpc/platforms/512x/Makefile +1 −0
  1971. arch/powerpc/platforms/512x/mpc512x_lpbfifo.c +540 −0
  1972. arch/powerpc/platforms/52xx/mpc52xx_gpt.c +2 −4
  1973. arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c +1 −0
  1974. arch/powerpc/platforms/85xx/corenet_generic.c +11 −0
  1975. arch/powerpc/platforms/85xx/mpc85xx_mds.c +1 −1
  1976. arch/powerpc/platforms/85xx/mpc85xx_rdb.c +1 −1
  1977. arch/powerpc/platforms/85xx/p1022_ds.c +1 −1
  1978. arch/powerpc/platforms/85xx/p1022_rdk.c +1 −1
  1979. arch/powerpc/platforms/85xx/smp.c +79 −9
  1980. arch/powerpc/platforms/85xx/twr_p102x.c +1 −1
  1981. arch/powerpc/platforms/86xx/mpc8610_hpcd.c +1 −1
  1982. arch/powerpc/platforms/Kconfig.cputype +0 −11
  1983. arch/powerpc/platforms/cell/Kconfig +2 −2
  1984. arch/powerpc/platforms/cell/axon_msi.c +1 −1
  1985. arch/powerpc/platforms/cell/spider-pic.c +6 −3
  1986. arch/powerpc/platforms/maple/Kconfig +1 −1
  1987. arch/powerpc/platforms/pasemi/Kconfig +1 −1
  1988. arch/powerpc/platforms/pasemi/msi.c +4 −2
  1989. arch/powerpc/platforms/powermac/Kconfig +1 −1
  1990. arch/powerpc/platforms/powernv/eeh-powernv.c +35 −51
  1991. arch/powerpc/platforms/powernv/opal-irqchip.c +1 −1
  1992. arch/powerpc/platforms/powernv/opal.c +5 −2
  1993. arch/powerpc/platforms/powernv/setup.c +13 −8
  1994. arch/powerpc/platforms/powernv/smp.c +24 −5
  1995. arch/powerpc/platforms/ps3/Kconfig +1 −1
  1996. arch/powerpc/platforms/ps3/os-area.c +0 −5
  1997. arch/powerpc/platforms/pseries/Kconfig +1 −6
  1998. arch/powerpc/platforms/pseries/Makefile +3 −4
  1999. arch/powerpc/platforms/pseries/dlpar.c +5 −26
  2000. arch/powerpc/platforms/pseries/eeh_pseries.c +26 −34
  2001. arch/powerpc/platforms/pseries/hvcserver.c +1 −1
  2002. arch/powerpc/platforms/pseries/iommu.c +0 −10
  2003. arch/powerpc/platforms/pseries/of_helpers.c +38 −0
  2004. arch/powerpc/platforms/pseries/of_helpers.h +8 −0
  2005. arch/powerpc/platforms/pseries/reconfig.c +2 −32
  2006. arch/powerpc/platforms/pseries/setup.c +2 −16
  2007. arch/powerpc/sysdev/axonram.c +3 −2
  2008. arch/powerpc/sysdev/cpm_common.c +2 −1
  2009. arch/powerpc/sysdev/ehv_pic.c +2 −1
  2010. arch/powerpc/sysdev/fsl_msi.c +1 −1
  2011. arch/powerpc/sysdev/fsl_pci.c +63 −25
  2012. arch/powerpc/sysdev/i8259.c +2 −1
  2013. arch/powerpc/sysdev/ipic.c +2 −1
  2014. arch/powerpc/sysdev/mpc5xxx_clocks.c +1 −4
  2015. arch/powerpc/sysdev/mpc8xx_pic.c +1 −1
  2016. arch/powerpc/sysdev/mpic.c +6 −20
  2017. arch/powerpc/sysdev/mpic_msi.c +1 −1
  2018. arch/powerpc/sysdev/msi_bitmap.c +13 −5
  2019. arch/powerpc/sysdev/qe_lib/qe_ic.c +2 −1
  2020. arch/powerpc/xmon/nonstdio.c +62 −2
  2021. arch/powerpc/xmon/nonstdio.h +3 −0
  2022. arch/powerpc/xmon/xmon.c +75 −4
  2023. arch/s390/Kconfig +3 −0
  2024. arch/s390/boot/compressed/Makefile +1 −1
  2025. arch/s390/configs/default_defconfig +1 −1
  2026. arch/s390/configs/gcov_defconfig +1 −1
  2027. arch/s390/configs/performance_defconfig +1 −1
  2028. arch/s390/crypto/sha.h +1 −1
  2029. arch/s390/hypfs/hypfs_diag.c +9 −1
  2030. arch/s390/hypfs/hypfs_diag0c.c +2 −0
  2031. arch/s390/hypfs/hypfs_sprp.c +8 −1
  2032. arch/s390/hypfs/hypfs_vm.c +2 −0
  2033. arch/s390/include/asm/Kbuild +1 −0
  2034. arch/s390/include/asm/appldata.h +2 −0
  2035. arch/s390/include/asm/atomic.h +0 −2
  2036. arch/s390/include/asm/barrier.h +4 −4
  2037. arch/s390/include/asm/bitops.h +34 −21
  2038. arch/s390/include/asm/cio.h +11 −0
  2039. arch/s390/include/asm/cmb.h +1 −0
  2040. arch/s390/include/asm/cmpxchg.h +3 −27
  2041. arch/s390/include/asm/cpu_mf.h +0 −5
  2042. arch/s390/include/asm/ctl_reg.h +0 −2
  2043. arch/s390/include/asm/diag.h +29 −0
  2044. arch/s390/include/asm/elf.h +10 −3
  2045. arch/s390/include/asm/etr.h +6 −4
  2046. arch/s390/include/asm/fpu/api.h +30 −0
  2047. arch/s390/include/asm/fpu/internal.h +4 −47
  2048. arch/s390/include/asm/fpu/types.h +25 −0
  2049. arch/s390/include/asm/idle.h +2 −0
  2050. arch/s390/include/asm/ipl.h +2 −1
  2051. arch/s390/include/asm/irq.h +13 −1
  2052. arch/s390/include/asm/kvm_host.h +3 −1
  2053. arch/s390/include/asm/kvm_para.h +58 −9
  2054. arch/s390/include/asm/lowcore.h +9 −2
  2055. arch/s390/include/asm/nmi.h +55 −43
  2056. arch/s390/include/asm/numa.h +1 −1
  2057. arch/s390/include/asm/pci.h +4 −0
  2058. arch/s390/include/asm/pci_dma.h +5 −0
  2059. arch/s390/include/asm/pgtable.h +60 −6
  2060. arch/s390/include/asm/processor.h +32 −67
  2061. arch/s390/include/asm/ptrace.h +6 −5
  2062. arch/s390/include/asm/setup.h +27 −23
  2063. arch/s390/include/asm/spinlock.h +0 −3
  2064. arch/s390/include/asm/switch_to.h +1 −1
  2065. arch/s390/include/asm/thread_info.h +12 −10
  2066. arch/s390/include/asm/topology.h +1 −1
  2067. arch/s390/include/asm/trace/diag.h +43 −0
  2068. arch/s390/include/uapi/asm/unistd.h +10 −9
  2069. arch/s390/kernel/Makefile +2 −0
  2070. arch/s390/kernel/asm-offsets.c +149 −140
  2071. arch/s390/kernel/compat_signal.c +3 −4
  2072. arch/s390/kernel/compat_wrapper.c +1 −0
  2073. arch/s390/kernel/cpcmd.c +2 −0
  2074. arch/s390/kernel/crash_dump.c +4 −12
  2075. arch/s390/kernel/diag.c +133 −1
  2076. arch/s390/kernel/early.c +14 −1
  2077. arch/s390/kernel/entry.S +124 −136
  2078. arch/s390/kernel/entry.h +0 −3
  2079. arch/s390/kernel/head.S +12 −83
  2080. arch/s390/kernel/head64.S +6 −1
  2081. arch/s390/kernel/ipl.c +50 −24
  2082. arch/s390/kernel/irq.c +0 −1
  2083. arch/s390/kernel/nmi.c +61 −59
  2084. arch/s390/kernel/perf_cpum_cf.c +30 −5
  2085. arch/s390/kernel/perf_cpum_sf.c +6 −4
  2086. arch/s390/kernel/process.c +20 −23
  2087. arch/s390/kernel/processor.c +4 −1
  2088. arch/s390/kernel/ptrace.c +19 −33
  2089. arch/s390/kernel/runtime_instr.c +3 −61
  2090. arch/s390/kernel/s390_ksyms.c +1 −2
  2091. arch/s390/kernel/sclp.c +1 −1
  2092. arch/s390/kernel/setup.c +0 −3
  2093. arch/s390/kernel/signal.c +3 −4
  2094. arch/s390/kernel/smp.c +8 −2
  2095. arch/s390/kernel/syscalls.S +1 −0
  2096. arch/s390/kernel/time.c +21 −10
  2097. arch/s390/kernel/topology.c +16 −12
  2098. arch/s390/kernel/trace.c +29 −0
  2099. arch/s390/kernel/traps.c +1 −40
  2100. arch/s390/kernel/vdso.c +1 −1
  2101. arch/s390/kernel/vtime.c +37 −29
  2102. arch/s390/kvm/intercept.c +21 −21
  2103. arch/s390/kvm/interrupt.c +43 −73
  2104. arch/s390/kvm/kvm-s390.c +27 −37
  2105. arch/s390/kvm/kvm-s390.h +31 −4
  2106. arch/s390/kvm/priv.c +3 −16
  2107. arch/s390/lib/delay.c +14 −16
  2108. arch/s390/lib/find.c +1 −3
  2109. arch/s390/lib/spinlock.c +2 −2
  2110. arch/s390/mm/extmem.c +3 −0
  2111. arch/s390/mm/fault.c +5 −2
  2112. arch/s390/mm/hugetlbpage.c +2 −0
  2113. arch/s390/mm/init.c +3 −27
  2114. arch/s390/mm/mmap.c +9 −51
  2115. arch/s390/net/bpf_jit_comp.c +1 −1
  2116. arch/s390/numa/mode_emu.c +10 −4
  2117. arch/s390/numa/numa.c +2 −2
  2118. arch/s390/pci/pci_dma.c +76 −35
  2119. arch/s390/pci/pci_insn.c +3 −3
  2120. arch/score/include/asm/Kbuild +1 −0
  2121. arch/sh/boards/mach-rsk/setup.c +0 −3
  2122. arch/sh/include/asm/atomic.h +2 −2
  2123. arch/sh/include/asm/page.h +1 −0
  2124. arch/sh/kernel/cpu/sh5/unwind.c +1 −1
  2125. arch/sh/kernel/traps_64.c +1 −1
  2126. arch/sparc/crypto/aes_glue.c +2 −0
  2127. arch/sparc/crypto/camellia_glue.c +1 −0
  2128. arch/sparc/crypto/des_glue.c +2 −0
  2129. arch/sparc/include/asm/atomic_64.h +4 −4
  2130. arch/sparc/include/asm/topology_64.h +3 −0
  2131. arch/sparc/include/uapi/asm/asi.h +1 −1
  2132. arch/sparc/include/uapi/asm/mman.h +1 −0
  2133. arch/sparc/include/uapi/asm/unistd.h +2 −1
  2134. arch/sparc/kernel/iommu.c +6 −6
  2135. arch/sparc/kernel/ldc.c +1 −1
  2136. arch/sparc/kernel/pci.c +6 −1
  2137. arch/sparc/kernel/pci_common.c +15 −2
  2138. arch/sparc/kernel/pci_impl.h +1 −0
  2139. arch/sparc/kernel/pci_sun4v.c +9 −9
  2140. arch/sparc/kernel/perf_event.c +25 −7
  2141. arch/sparc/kernel/systbls_32.S +1 −1
  2142. arch/sparc/kernel/systbls_64.S +2 −2
  2143. arch/sparc/kernel/unaligned_64.c +15 −7
  2144. arch/sparc/lib/VISsave.S +5 −5
  2145. arch/sparc/mm/init_64.c +69 −1
  2146. arch/sparc/net/bpf_jit_comp.c +1 −1
  2147. arch/tile/gxio/mpipe.c +4 −29
  2148. arch/tile/include/asm/atomic.h +1 −1
  2149. arch/tile/include/asm/atomic_64.h +3 −3
  2150. arch/tile/include/asm/highmem.h +0 −1
  2151. arch/tile/include/asm/word-at-a-time.h +7 −1
  2152. arch/tile/include/uapi/asm/mman.h +1 −0
  2153. arch/tile/kernel/usb.c +1 −0
  2154. arch/tile/mm/highmem.c +0 −12
  2155. arch/um/Makefile +3 −3
  2156. arch/um/drivers/net_kern.c +9 −8
  2157. arch/um/include/asm/Kbuild +1 −0
  2158. arch/um/include/asm/ptrace-generic.h +2 −0
  2159. arch/um/include/shared/os.h +14 −5
  2160. arch/um/include/shared/skas/stub-data.h +4 −3
  2161. arch/um/include/shared/timer-internal.h +13 −0
  2162. arch/um/kernel/process.c +4 −4
  2163. arch/um/kernel/skas/clone.c +1 −5
  2164. arch/um/kernel/skas/mmu.c +3 −0
  2165. arch/um/kernel/skas/syscall.c +6 −15
  2166. arch/um/kernel/time.c +48 −25
  2167. arch/um/kernel/tlb.c +15 −1
  2168. arch/um/kernel/trap.c +1 −1
  2169. arch/um/os-Linux/helper.c +3 −3
  2170. arch/um/os-Linux/internal.h +0 −1
  2171. arch/um/os-Linux/main.c +4 −3
  2172. arch/um/os-Linux/process.c +6 −0
  2173. arch/um/os-Linux/signal.c +22 −19
  2174. arch/um/os-Linux/skas/process.c +17 −38
  2175. arch/um/os-Linux/time.c +126 −123
  2176. arch/unicore32/Kconfig +1 −1
  2177. arch/unicore32/include/asm/Kbuild +1 −0
  2178. arch/unicore32/kernel/puv3-nb0916.c +8 −2
  2179. arch/x86/Kconfig +53 −19
  2180. arch/x86/Kconfig.cpu +17 −7
  2181. arch/x86/Kconfig.debug +34 −1
  2182. arch/x86/Makefile +10 −2
  2183. arch/x86/boot/Makefile +2 −2
  2184. arch/x86/boot/compressed/eboot.c +26 −6
  2185. arch/x86/boot/header.S +1 −1
  2186. arch/x86/crypto/Makefile +8 −0
  2187. arch/x86/crypto/camellia_aesni_avx2_glue.c +2 −1
  2188. arch/x86/crypto/camellia_aesni_avx_glue.c +7 −1
  2189. arch/x86/crypto/cast5_avx_glue.c +2 −1
  2190. arch/x86/crypto/cast6_avx_glue.c +2 −1
  2191. arch/x86/crypto/chacha20_glue.c +1 −1
  2192. arch/x86/crypto/crc32c-pcl-intel-asm_64.S +1 −1
  2193. arch/x86/crypto/poly1305_glue.c +1 −1
  2194. arch/x86/crypto/serpent_avx2_glue.c +2 −1
  2195. arch/x86/crypto/serpent_avx_glue.c +2 −1
  2196. arch/x86/crypto/sha1_ni_asm.S +302 −0
  2197. arch/x86/crypto/sha1_ssse3_glue.c +251 −65
  2198. arch/x86/crypto/sha256_ni_asm.S +353 −0
  2199. arch/x86/crypto/sha256_ssse3_glue.c +285 −46
  2200. arch/x86/crypto/sha512_ssse3_glue.c +205 −46
  2201. arch/x86/crypto/twofish_avx_glue.c +1 −1
  2202. arch/x86/entry/common.c +216 −48
  2203. arch/x86/entry/entry_32.S +60 −122
  2204. arch/x86/entry/entry_64.S +2 −7
  2205. arch/x86/entry/entry_64_compat.S +134 −413
  2206. arch/x86/entry/syscall_32.c +3 −6
  2207. arch/x86/entry/syscall_64.c +2 −2
  2208. arch/x86/entry/syscalls/syscall_32.tbl +7 −6
  2209. arch/x86/entry/syscalls/syscall_64.tbl +1 −0
  2210. arch/x86/entry/vdso/Makefile +13 −26
  2211. arch/x86/entry/vdso/vdso2c.c +1 −1
  2212. arch/x86/entry/vdso/vdso32-setup.c +1 −27
  2213. arch/x86/entry/vdso/vdso32/int80.S +0 −56
  2214. arch/x86/entry/vdso/vdso32/syscall.S +0 −75
  2215. arch/x86/entry/vdso/vdso32/sysenter.S +0 −116
  2216. arch/x86/entry/vdso/vdso32/system_call.S +57 −0
  2217. arch/x86/entry/vdso/vdso32/vclock_gettime.c +2 −0
  2218. arch/x86/entry/vdso/vma.c +1 −12
  2219. arch/x86/entry/vsyscall/vsyscall_64.c +8 −1
  2220. arch/x86/ia32/ia32_signal.c +6 −6
  2221. arch/x86/include/asm/acpi.h +23 −0
  2222. arch/x86/include/asm/amd_nb.h +1 −1
  2223. arch/x86/include/asm/apic.h +55 −55
  2224. arch/x86/include/asm/atomic.h +2 −2
  2225. arch/x86/include/asm/atomic64_64.h +2 −2
  2226. arch/x86/include/asm/cpufeature.h +5 −2
  2227. arch/x86/include/asm/dwarf2.h +84 −0
  2228. arch/x86/include/asm/efi.h +3 −0
  2229. arch/x86/include/asm/elf.h +5 −5
  2230. arch/x86/include/asm/fpu/signal.h +1 −1
  2231. arch/x86/include/asm/fpu/types.h +103 −45
  2232. arch/x86/include/asm/fpu/xstate.h +10 −5
  2233. arch/x86/include/asm/highmem.h +0 −1
  2234. arch/x86/include/asm/hpet.h +3 −3
  2235. arch/x86/include/asm/i8259.h +1 −0
  2236. arch/x86/include/asm/ia32.h +2 −2
  2237. arch/x86/include/asm/irq_remapping.h +5 −5
  2238. arch/x86/include/asm/kdebug.h +0 −6
  2239. arch/x86/include/asm/kvm_emulate.h +10 −0
  2240. arch/x86/include/asm/kvm_host.h +48 −23
  2241. arch/x86/include/asm/mce.h +21 −13
  2242. arch/x86/include/asm/microcode.h +13 −13
  2243. arch/x86/include/asm/microcode_amd.h +2 −1
  2244. arch/x86/include/asm/microcode_intel.h +3 −7
  2245. arch/x86/include/asm/msr-index.h +10 −2
  2246. arch/x86/include/asm/numachip/numachip.h +1 −0
  2247. arch/x86/include/asm/numachip/numachip_csr.h +42 −111
  2248. arch/x86/include/asm/page_64_types.h +0 −3
  2249. arch/x86/include/asm/page_types.h +3 −0
  2250. arch/x86/include/asm/pgtable.h +28 −7
  2251. arch/x86/include/asm/pgtable_types.h +36 −4
  2252. arch/x86/include/asm/preempt.h +1 −4
  2253. arch/x86/include/asm/processor.h +3 −3
  2254. arch/x86/include/asm/pvclock-abi.h +1 −0
  2255. arch/x86/include/asm/sigcontext.h +2 −73
  2256. arch/x86/include/asm/sigframe.h +3 −5
  2257. arch/x86/include/asm/signal.h +1 −1
  2258. arch/x86/include/asm/string_64.h +2 −3
  2259. arch/x86/include/asm/switch_to.h +8 −4
  2260. arch/x86/include/asm/syscall.h +13 −1
  2261. arch/x86/include/asm/thread_info.h +0 −3
  2262. arch/x86/include/asm/trace/mpx.h +4 −3
  2263. arch/x86/include/asm/uaccess.h +7 −7
  2264. arch/x86/include/asm/uv/uv_hub.h +1 −1
  2265. arch/x86/include/asm/vdso.h +2 −8
  2266. arch/x86/include/asm/vmx.h +5 −1
  2267. arch/x86/include/asm/xen/hypercall.h +2 −2
  2268. arch/x86/include/asm/xen/hypervisor.h +5 −0
  2269. arch/x86/include/asm/xen/page.h +5 −3
  2270. arch/x86/include/uapi/asm/bitsperlong.h +1 −1
  2271. arch/x86/include/uapi/asm/hyperv.h +18 −0
  2272. arch/x86/include/uapi/asm/mce.h +1 −1
  2273. arch/x86/include/uapi/asm/sigcontext.h +307 −168
  2274. arch/x86/include/uapi/asm/sigcontext32.h +2 −71
  2275. arch/x86/include/uapi/asm/svm.h +1 −0
  2276. arch/x86/include/uapi/asm/vmx.h +3 −1
  2277. arch/x86/kernel/acpi/boot.c +18 −4
  2278. arch/x86/kernel/apic/apic.c +4 −4
  2279. arch/x86/kernel/apic/apic_numachip.c +160 −60
  2280. arch/x86/kernel/apic/io_apic.c +8 −2
  2281. arch/x86/kernel/apic/vector.c +5 −1
  2282. arch/x86/kernel/asm-offsets.c +9 −12
  2283. arch/x86/kernel/cpu/Makefile +1 −0
  2284. arch/x86/kernel/cpu/amd.c +13 −0
  2285. arch/x86/kernel/cpu/common.c +2 −2
  2286. arch/x86/kernel/cpu/intel.c +1 −0
  2287. arch/x86/kernel/cpu/intel_cacheinfo.c +4 −4
  2288. arch/x86/kernel/cpu/mcheck/mce.c +24 −10
  2289. arch/x86/kernel/cpu/mcheck/therm_throt.c +0 −8
  2290. arch/x86/kernel/cpu/microcode/Makefile +0 −3
  2291. arch/x86/kernel/cpu/microcode/amd.c +492 −17
  2292. arch/x86/kernel/cpu/microcode/amd_early.c +0 −440
  2293. arch/x86/kernel/cpu/microcode/core.c +169 −63
  2294. arch/x86/kernel/cpu/microcode/core_early.c +0 −170
  2295. arch/x86/kernel/cpu/microcode/intel.c +784 −7
  2296. arch/x86/kernel/cpu/microcode/intel_early.c +0 −808
  2297. arch/x86/kernel/cpu/microcode/intel_lib.c +0 −1
  2298. arch/x86/kernel/cpu/mshyperv.c +7 −5
  2299. arch/x86/kernel/cpu/perf_event.c +33 −6
  2300. arch/x86/kernel/cpu/perf_event.h +2 −1
  2301. arch/x86/kernel/cpu/perf_event_intel.c +15 −2
  2302. arch/x86/kernel/cpu/perf_event_intel_bts.c +13 −0
  2303. arch/x86/kernel/cpu/perf_event_intel_cstate.c +694 −0
  2304. arch/x86/kernel/cpu/perf_event_intel_ds.c +34 −6
  2305. arch/x86/kernel/cpu/perf_event_intel_lbr.c +6 −2
  2306. arch/x86/kernel/cpu/perf_event_intel_pt.c +4 −3
  2307. arch/x86/kernel/cpu/perf_event_intel_rapl.c +0 −6
  2308. arch/x86/kernel/cpu/perf_event_intel_uncore.c +58 −3
  2309. arch/x86/kernel/cpu/perf_event_intel_uncore.h +11 −1
  2310. arch/x86/kernel/cpu/perf_event_intel_uncore_snb.c +13 −3
  2311. arch/x86/kernel/cpu/perf_event_intel_uncore_snbep.c +25 −9
  2312. arch/x86/kernel/cpu/perf_event_msr.c +5 −6
  2313. arch/x86/kernel/cpu/scattered.c +1 −1
  2314. arch/x86/kernel/crash.c +3 −7
  2315. arch/x86/kernel/e820.c +1 −1
  2316. arch/x86/kernel/early-quirks.c +1 −1
  2317. arch/x86/kernel/early_printk.c +3 −3
  2318. arch/x86/kernel/fpu/init.c +4 −14
  2319. arch/x86/kernel/fpu/regset.c +2 −2
  2320. arch/x86/kernel/fpu/signal.c +10 −11
  2321. arch/x86/kernel/fpu/xstate.c +345 −54
  2322. arch/x86/kernel/ftrace.c +4 −0
  2323. arch/x86/kernel/head_32.S +2 −3
  2324. arch/x86/kernel/head_64.S +8 −0
  2325. arch/x86/kernel/hpet.c +14 −15
  2326. arch/x86/kernel/i8259.c +21 −8
  2327. arch/x86/kernel/irq_64.c +1 −1
  2328. arch/x86/kernel/kgdb.c +11 −6
  2329. arch/x86/kernel/kvmclock.c +35 −11
  2330. arch/x86/kernel/livepatch.c +5 −4
  2331. arch/x86/kernel/mcount_64.S +6 −0
  2332. arch/x86/kernel/pci-dma.c +4 −3
  2333. arch/x86/kernel/process.c +58 −0
  2334. arch/x86/kernel/process_32.c +0 −36
  2335. arch/x86/kernel/process_64.c +1 −33
  2336. arch/x86/kernel/quirks.c +1 −1
  2337. arch/x86/kernel/setup.c +66 −48
  2338. arch/x86/kernel/signal.c +6 −4
  2339. arch/x86/kernel/smpboot.c +11 −4
  2340. arch/x86/kernel/traps.c +2 −2
  2341. arch/x86/kernel/tsc.c +22 −13
  2342. arch/x86/kernel/verify_cpu.S +7 −5
  2343. arch/x86/kvm/Kconfig +2 −0
  2344. arch/x86/kvm/assigned-dev.c +37 −25
  2345. arch/x86/kvm/cpuid.c +3 −3
  2346. arch/x86/kvm/cpuid.h +37 −0
  2347. arch/x86/kvm/emulate.c +34 −11
  2348. arch/x86/kvm/hyperv.c +29 −2
  2349. arch/x86/kvm/i8254.c +3 −1
  2350. arch/x86/kvm/ioapic.c +6 −23
  2351. arch/x86/kvm/ioapic.h +8 −7
  2352. arch/x86/kvm/irq.c +30 −10
  2353. arch/x86/kvm/irq.h +26 −1
  2354. arch/x86/kvm/irq_comm.c +88 −41
  2355. arch/x86/kvm/lapic.c +106 −25
  2356. arch/x86/kvm/lapic.h +4 −3
  2357. arch/x86/kvm/mmu.c +58 −53
  2358. arch/x86/kvm/mmu.h +3 −3
  2359. arch/x86/kvm/paging_tmpl.h +10 −12
  2360. arch/x86/kvm/svm.c +54 −252
  2361. arch/x86/kvm/trace.h +51 −0
  2362. arch/x86/kvm/vmx.c +656 −200
  2363. arch/x86/kvm/x86.c +422 −157
  2364. arch/x86/kvm/x86.h +3 −3
  2365. arch/x86/lib/x86-opcode-map.txt +19 −5
  2366. arch/x86/math-emu/fpu_aux.c +70 −0
  2367. arch/x86/math-emu/fpu_emu.h +1 −1
  2368. arch/x86/math-emu/fpu_entry.c +31 −65
  2369. arch/x86/math-emu/fpu_proto.h +12 −0
  2370. arch/x86/math-emu/load_store.c +51 −12
  2371. arch/x86/math-emu/reg_compare.c +128 −0
  2372. arch/x86/mm/Makefile +1 −1
  2373. arch/x86/mm/dump_pagetables.c +78 −20
  2374. arch/x86/mm/gup.c +8 −10
  2375. arch/x86/mm/highmem_32.c +0 −14
  2376. arch/x86/mm/init.c +2 −4
  2377. arch/x86/mm/init_32.c +2 −0
  2378. arch/x86/mm/init_64.c +5 −3
  2379. arch/x86/mm/kasan_init_64.c +1 −1
  2380. arch/x86/mm/mpx.c +49 −13
  2381. arch/x86/mm/pageattr.c +56 −32
  2382. arch/x86/net/bpf_jit_comp.c +1 −1
  2383. arch/x86/pci/acpi.c +88 −208
  2384. arch/x86/pci/common.c +8 −0
  2385. arch/x86/pci/legacy.c +1 −1
  2386. arch/x86/platform/efi/efi-bgrt.c +7 −2
  2387. arch/x86/platform/efi/efi.c +70 −25
  2388. arch/x86/platform/intel-mid/intel-mid.c +1 −1
  2389. arch/x86/platform/intel-mid/sfi.c +1 −2
  2390. arch/x86/platform/uv/uv_nmi.c +30 −23
  2391. arch/x86/ras/Kconfig +1 −3
  2392. arch/x86/ras/mce_amd_inj.c +96 −7
  2393. arch/x86/um/asm/syscall.h +4 −0
  2394. arch/x86/um/ldt.c +4 −1
  2395. arch/x86/um/stub_32.S +0 −1
  2396. arch/x86/um/stub_64.S +1 −17
  2397. arch/x86/um/sys_call_table_32.c +3 −4
  2398. arch/x86/um/sys_call_table_64.c +3 −4
  2399. arch/x86/xen/enlighten.c +39 −0
  2400. arch/x86/xen/grant-table.c +1 −1
  2401. arch/x86/xen/mmu.c +1 −0
  2402. arch/x86/xen/p2m.c +31 −7
  2403. arch/x86/xen/setup.c +10 −16
  2404. arch/xtensa/Kconfig +16 −1
  2405. arch/xtensa/Makefile +4 −0
  2406. arch/xtensa/boot/boot-elf/boot.lds.S +0 −13
  2407. arch/xtensa/boot/boot-elf/bootstrap.S +0 −28
  2408. arch/xtensa/boot/dts/Makefile +6 −1
  2409. arch/xtensa/boot/dts/kc705_nommu.dts +17 −0
  2410. arch/xtensa/configs/iss_defconfig +0 −1
  2411. arch/xtensa/configs/nommu_kc705_defconfig +131 −0
  2412. arch/xtensa/include/asm/Kbuild +1 −0
  2413. arch/xtensa/include/asm/asmmacro.h +4 −3
  2414. arch/xtensa/include/asm/atomic.h +2 −2
  2415. arch/xtensa/include/asm/cacheasm.h +26 −0
  2416. arch/xtensa/include/asm/cacheflush.h +8 −98
  2417. arch/xtensa/include/asm/dma-mapping.h +10 −0
  2418. arch/xtensa/include/asm/initialize_mmu.h +9 −4
  2419. arch/xtensa/include/asm/io.h +0 −9
  2420. arch/xtensa/include/asm/pgtable.h +4 −0
  2421. arch/xtensa/include/asm/vectors.h +19 −9
  2422. arch/xtensa/include/uapi/asm/mman.h +6 −0
  2423. arch/xtensa/kernel/Makefile +1 −0
  2424. arch/xtensa/kernel/entry.S +6 −2
  2425. arch/xtensa/kernel/head.S +1 −1
  2426. arch/xtensa/kernel/mxhead.S +0 −23
  2427. arch/xtensa/kernel/pci-dma.c +31 −14
  2428. arch/xtensa/kernel/setup.c +9 −2
  2429. arch/xtensa/kernel/time.c +1 −1
  2430. arch/xtensa/kernel/vectors.S +3 −1
  2431. arch/xtensa/kernel/vmlinux.lds.S +2 −35
  2432. arch/xtensa/lib/usercopy.S +3 −3
  2433. arch/xtensa/platforms/iss/setup.c +2 −0
  2434. arch/xtensa/platforms/iss/simdisk.c +2 −1
  2435. arch/xtensa/platforms/xt2000/setup.c +2 −0
  2436. arch/xtensa/platforms/xtfpga/include/platform/hardware.h +4 −2
  2437. arch/xtensa/platforms/xtfpga/setup.c +2 −0
  2438. arch/xtensa/variants/de212/include/variant/core.h +594 −0
  2439. arch/xtensa/variants/de212/include/variant/tie-asm.h +170 −0
  2440. arch/xtensa/variants/de212/include/variant/tie.h +136 −0
  2441. block/bio-integrity.c +11 −6
  2442. block/bio.c +13 −13
  2443. block/blk-cgroup.c +1 −0
  2444. block/blk-core.c +161 −29
  2445. block/blk-integrity.c +86 −106
  2446. block/blk-ioc.c +1 −1
  2447. block/blk-lib.c +22 −9
  2448. block/blk-merge.c +25 −7
  2449. block/blk-mq-cpumap.c +5 −4
  2450. block/blk-mq-sysfs.c +32 −18
  2451. block/blk-mq-tag.c +26 −8
  2452. block/blk-mq-tag.h +2 −0
  2453. block/blk-mq.c +203 −153
  2454. block/blk-mq.h +2 −4
  2455. block/blk-sysfs.c +37 −2
  2456. block/blk-throttle.c +1 −1
  2457. block/blk.h +21 −0
  2458. block/cfq-iosched.c +2 −2
  2459. block/elevator.c +1 −1
  2460. block/genhd.c +2 −0
  2461. block/ioctl.c +230 −100
  2462. block/ioprio.c +4 −2
  2463. block/partition-generic.c +1 −0
  2464. block/scsi_ioctl.c +3 −3
  2465. block/t10-pi.c +4 −12
  2466. certs/.gitignore +4 −0
  2467. crypto/Kconfig +13 −4
  2468. crypto/Makefile +7 −3
  2469. crypto/ablkcipher.c +1 −1
  2470. crypto/ahash.c +2 −1
  2471. crypto/akcipher.c +0 −1
  2472. crypto/algapi.c +1 −1
  2473. crypto/algif_hash.c +10 −2
  2474. crypto/api.c +3 −3
  2475. crypto/asymmetric_keys/asymmetric_keys.h +0 −5
  2476. crypto/asymmetric_keys/asymmetric_type.c +26 −18
  2477. crypto/asymmetric_keys/pkcs7_verify.c +3 −2
  2478. crypto/asymmetric_keys/public_key.c +2 −2
  2479. crypto/asymmetric_keys/signature.c +1 −1
  2480. crypto/asymmetric_keys/x509_cert_parser.c +10 −8
  2481. crypto/asymmetric_keys/x509_parser.h +1 −0
  2482. crypto/asymmetric_keys/x509_public_key.c +8 −10
  2483. crypto/crypto_user.c +1 −1
  2484. crypto/jitterentropy-kcapi.c +0 −4
  2485. crypto/keywrap.c +419 −0
  2486. crypto/rsa.c +49 −34
  2487. crypto/rsa_helper.c +35 −7
  2488. crypto/rsakey.asn1 +0 −5
  2489. crypto/rsaprivkey.asn1 +11 −0
  2490. crypto/rsapubkey.asn1 +4 −0
  2491. crypto/skcipher.c +2 −2
  2492. crypto/tcrypt.c +13 −4
  2493. crypto/testmgr.c +47 −36
  2494. crypto/testmgr.h +68 −9
  2495. drivers/Kconfig +10 −0
  2496. drivers/Makefile +5 −0
  2497. drivers/acpi/Kconfig +26 −3
  2498. drivers/acpi/Makefile +1 −0
  2499. drivers/acpi/acpi_lpss.c +1 −1
  2500. drivers/acpi/acpi_pad.c +0 −2
  2501. drivers/acpi/acpi_platform.c +6 −1
  2502. drivers/acpi/acpi_pnp.c +2 −2
  2503. drivers/acpi/acpi_processor.c +18 −0
  2504. drivers/acpi/acpi_video.c +66 −12
  2505. drivers/acpi/acpica/Makefile +17 −1
  2506. drivers/acpi/acpica/acapps.h +1 −1
  2507. drivers/acpi/acpica/acdebug.h +6 −0
  2508. drivers/acpi/acpica/acglobal.h +7 −1
  2509. drivers/acpi/acpica/acinterp.h +0 −2
  2510. drivers/acpi/acpica/aclocal.h +16 −6
  2511. drivers/acpi/acpica/acnamesp.h +0 −4
  2512. drivers/acpi/acpica/acopcode.h +2 −2
  2513. drivers/acpi/acpica/acparser.h +0 −4
  2514. drivers/acpi/acpica/actables.h +1 −3
  2515. drivers/acpi/acpica/acutils.h +0 −2
  2516. drivers/acpi/acpica/amlcode.h +6 −5
  2517. drivers/acpi/acpica/dbcmds.c +1187 −0
  2518. drivers/acpi/acpica/dbconvert.c +484 −0
  2519. drivers/acpi/acpica/dbdisply.c +1108 −0
  2520. drivers/acpi/acpica/dbexec.c +764 −0
  2521. drivers/acpi/acpica/dbfileio.c +256 −0
  2522. drivers/acpi/acpica/dbhistry.c +239 −0
  2523. drivers/acpi/acpica/dbinput.c +1267 −0
  2524. drivers/acpi/acpica/dbmethod.c +369 −0
  2525. drivers/acpi/acpica/dbnames.c +947 −0
  2526. drivers/acpi/acpica/dbobject.c +533 −0
  2527. drivers/acpi/acpica/dbstats.c +546 −0
  2528. drivers/acpi/acpica/dbtest.c +1057 −0
  2529. drivers/acpi/acpica/dbutils.c +457 −0
  2530. drivers/acpi/acpica/dbxface.c +513 −0
  2531. drivers/acpi/acpica/evxface.c +1 −1
  2532. drivers/acpi/acpica/evxfevnt.c +1 −1
  2533. drivers/acpi/acpica/exconvrt.c +1 −0
  2534. drivers/acpi/acpica/exresolv.c +0 −1
  2535. drivers/acpi/acpica/exresop.c +2 −0
  2536. drivers/acpi/acpica/exstore.c +91 −29
  2537. drivers/acpi/acpica/exstoren.c +3 −2
  2538. drivers/acpi/acpica/nsdump.c +0 −6
  2539. drivers/acpi/acpica/nspredef.c +1 −1
  2540. drivers/acpi/acpica/pstree.c +0 −2
  2541. drivers/acpi/acpica/psutils.c +0 −2
  2542. drivers/acpi/acpica/rsdump.c +0 −3
  2543. drivers/acpi/acpica/rsutils.c +0 −2
  2544. drivers/acpi/acpica/rsxface.c +2 −2
  2545. drivers/acpi/acpica/tbfadt.c +5 −5
  2546. drivers/acpi/acpica/tbutils.c +2 −24
  2547. drivers/acpi/acpica/utdecode.c +17 −4
  2548. drivers/acpi/acpica/utfileio.c +6 −0
  2549. drivers/acpi/acpica/utinit.c +13 −2
  2550. drivers/acpi/acpica/utmutex.c +21 −0
  2551. drivers/acpi/acpica/utxface.c +1 −18
  2552. drivers/acpi/apei/ghes.c +7 −3
  2553. drivers/acpi/cppc_acpi.c +733 −0
  2554. drivers/acpi/device_pm.c +1 −18
  2555. drivers/acpi/device_sysfs.c +108 −12
  2556. drivers/acpi/ec.c +75 −40
  2557. drivers/acpi/ec_sys.c +1 −1
  2558. drivers/acpi/glue.c +7 −6
  2559. drivers/acpi/gsi.c +33 −21
  2560. drivers/acpi/internal.h +4 −4
  2561. drivers/acpi/nfit.c +246 −60
  2562. drivers/acpi/nfit.h +3 −1
  2563. drivers/acpi/osl.c +12 −14
  2564. drivers/acpi/pci_irq.c +1 −0
  2565. drivers/acpi/pci_link.c +14 −2
  2566. drivers/acpi/pci_root.c +204 −0
  2567. drivers/acpi/proc.c +1 −3
  2568. drivers/acpi/processor_driver.c +6 −0
  2569. drivers/acpi/property.c +358 −69
  2570. drivers/acpi/resource.c +6 −3
  2571. drivers/acpi/sbshc.c +7 −41
  2572. drivers/acpi/scan.c +85 −24
  2573. drivers/acpi/sleep.c +7 −2
  2574. drivers/acpi/sysfs.c +3 −0
  2575. drivers/acpi/tables.c +76 −18
  2576. drivers/acpi/thermal.c +6 −6
  2577. drivers/acpi/video_detect.c +18 −0
  2578. drivers/ata/Kconfig +9 −0
  2579. drivers/ata/Makefile +1 −0
  2580. drivers/ata/ahci.c +12 −0
  2581. drivers/ata/ahci.h +2 −0
  2582. drivers/ata/ahci_platform.c +0 −1
  2583. drivers/ata/ahci_qoriq.c +279 −0
  2584. drivers/ata/libahci.c +11 −19
  2585. drivers/ata/libata-scsi.c +33 −29
  2586. drivers/ata/pata_it821x.c +3 −3
  2587. drivers/ata/pata_macio.c +1 −0
  2588. drivers/ata/pata_pxa.c +59 −112
  2589. drivers/ata/pata_samsung_cf.c +1 −1
  2590. drivers/atm/iphase.c +3 −2
  2591. drivers/base/class.c +1 −1
  2592. drivers/base/core.c +1 −1
  2593. drivers/base/dd.c +2 −0
  2594. drivers/base/devres.c +10 −9
  2595. drivers/base/dma-contiguous.c +2 −2
  2596. drivers/base/pinctrl.c +13 −2
  2597. drivers/base/platform-msi.c +3 −3
  2598. drivers/base/platform.c +70 −10
  2599. drivers/base/power/Makefile +1 −1
  2600. drivers/base/power/clock_ops.c +7 −5
  2601. drivers/base/power/domain.c +85 −306
  2602. drivers/base/power/domain_governor.c +4 −16
  2603. drivers/base/power/generic_ops.c +20 −3
  2604. drivers/base/power/opp/Makefile +2 −0
  2605. drivers/base/power/opp/core.c +73 −353
  2606. drivers/base/power/opp/cpu.c +270 −0
  2607. drivers/base/power/opp/opp.h +146 −0
  2608. drivers/base/power/wakeirq.c +6 −0
  2609. drivers/base/power/wakeup.c +14 −2
  2610. drivers/base/property.c +100 −20
  2611. drivers/base/regmap/internal.h +6 −3
  2612. drivers/base/regmap/regcache-lzo.c +2 −2
  2613. drivers/base/regmap/regcache.c +12 −12
  2614. drivers/base/regmap/regmap-debugfs.c +12 −16
  2615. drivers/base/regmap/regmap-irq.c +38 −5
  2616. drivers/base/regmap/regmap.c +29 −12
  2617. drivers/base/soc.c +5 −16
  2618. drivers/bcma/main.c +2 −7
  2619. drivers/block/Kconfig +0 −11
  2620. drivers/block/Makefile +0 −2
  2621. drivers/block/brd.c +6 −2
  2622. drivers/block/drbd/drbd_bitmap.c +2 −2
  2623. drivers/block/drbd/drbd_int.h +1 −1
  2624. drivers/block/drbd/drbd_receiver.c +2 −1
  2625. drivers/block/drbd/drbd_req.c +2 −1
  2626. drivers/block/loop.c +222 −61
  2627. drivers/block/loop.h +7 −6
  2628. drivers/block/mtip32xx/mtip32xx.c +1 −1
  2629. drivers/block/nbd.c +30 −13
  2630. drivers/block/null_blk.c +3 −2
  2631. drivers/block/osdblk.c +1 −1
  2632. drivers/block/paride/pd.c +1 −1
  2633. drivers/block/pktcdvd.c +7 −9
  2634. drivers/block/ps3vram.c +4 −2
  2635. drivers/block/rbd.c +104 −87
  2636. drivers/block/rsxx/dev.c +3 −2
  2637. drivers/block/umem.c +2 −2
  2638. drivers/block/virtio_blk.c +1 −1
  2639. drivers/block/xen-blkback/blkback.c +7 −6
  2640. drivers/block/xen-blkback/common.h +13 −4
  2641. drivers/block/xen-blkback/xenbus.c +27 −22
  2642. drivers/block/xen-blkfront.c +372 −210
  2643. drivers/block/zram/zram_drv.c +17 −16
  2644. drivers/bluetooth/Kconfig +5 −3
  2645. drivers/bluetooth/ath3k.c +4 −0
  2646. drivers/bluetooth/bfusb.c +0 −11
  2647. drivers/bluetooth/bluecard_cs.c +1 −7
  2648. drivers/bluetooth/bpa10x.c +66 −120
  2649. drivers/bluetooth/bt3c_cs.c +9 −11
  2650. drivers/bluetooth/btbcm.c +65 −6
  2651. drivers/bluetooth/btintel.c +369 −0
  2652. drivers/bluetooth/btintel.h +42 −1
  2653. drivers/bluetooth/btmrvl_main.c +5 −28
  2654. drivers/bluetooth/btmrvl_sdio.c +48 −6
  2655. drivers/bluetooth/btsdio.c +1 −13
  2656. drivers/bluetooth/btuart_cs.c +2 −8
  2657. drivers/bluetooth/btusb.c +307 −61
  2658. drivers/bluetooth/btwilink.c +0 −13
  2659. drivers/bluetooth/dtl1_cs.c +0 −5
  2660. drivers/bluetooth/hci_ath.c +1 −0
  2661. drivers/bluetooth/hci_bcm.c +359 −87
  2662. drivers/bluetooth/hci_h4.c +1 −0
  2663. drivers/bluetooth/hci_h5.c +5 −5
  2664. drivers/bluetooth/hci_intel.c +516 −84
  2665. drivers/bluetooth/hci_ldisc.c +10 −14
  2666. drivers/bluetooth/hci_qca.c +11 −10
  2667. drivers/bluetooth/hci_uart.h +1 −1
  2668. drivers/bluetooth/hci_vhci.c +0 −8
  2669. drivers/bus/Kconfig +11 −1
  2670. drivers/bus/Makefile +1 −0
  2671. drivers/bus/arm-ccn.c +3 −2
  2672. drivers/bus/sunxi-rsb.c +783 −0
  2673. drivers/cdrom/cdrom.c +1 −0
  2674. drivers/char/agp/uninorth-agp.c +10 −6
  2675. drivers/char/efirtc.c +3 −10
  2676. drivers/char/hpet.c +3 −22
  2677. drivers/char/hw_random/Kconfig +23 −1
  2678. drivers/char/hw_random/Makefile +2 −0
  2679. drivers/char/hw_random/core.c +1 −1
  2680. drivers/char/hw_random/exynos-rng.c +49 −9
  2681. drivers/char/hw_random/mxc-rnga.c +4 −10
  2682. drivers/char/hw_random/octeon-rng.c +1 −11
  2683. drivers/char/hw_random/pasemi-rng.c +1 −0
  2684. drivers/char/hw_random/ppc4xx-rng.c +1 −0
  2685. drivers/char/hw_random/st-rng.c +151 −0
  2686. drivers/char/hw_random/stm32-rng.c +202 −0
  2687. drivers/char/ipmi/ipmi_si_intf.c +52 −30
  2688. drivers/char/ipmi/ipmi_ssif.c +5 −4
  2689. drivers/char/ipmi/ipmi_watchdog.c +7 −1
  2690. drivers/char/pcmcia/synclink_cs.c +0 −9
  2691. drivers/char/snsc.c +2 −3
  2692. drivers/char/tpm/st33zp24/Kconfig +1 −1
  2693. drivers/char/tpm/st33zp24/i2c.c +0 −1
  2694. drivers/char/tpm/st33zp24/spi.c +0 −1
  2695. drivers/char/tpm/tpm-chip.c +19 −9
  2696. drivers/char/tpm/tpm-interface.c +76 −0
  2697. drivers/char/tpm/tpm.h +123 −11
  2698. drivers/char/tpm/tpm2-cmd.c +254 −1
  2699. drivers/char/tpm/tpm_crb.c +15 −24
  2700. drivers/char/tpm/tpm_eventlog.c +56 −22
  2701. drivers/char/tpm/tpm_eventlog.h +6 −0
  2702. drivers/char/tpm/tpm_i2c_atmel.c +0 −1
  2703. drivers/char/tpm/tpm_i2c_infineon.c +0 −1
  2704. drivers/char/tpm/tpm_i2c_nuvoton.c +0 −1
  2705. drivers/char/tpm/tpm_ibmvtpm.c +1 −1
  2706. drivers/char/tpm/tpm_of.c +5 −4
  2707. drivers/char/tpm/tpm_ppi.c +11 −23
  2708. drivers/char/tpm/tpm_tis.c +170 −30
  2709. drivers/clk/Kconfig +25 −4
  2710. drivers/clk/Makefile +4 −2
  2711. drivers/clk/at91/Makefile +1 −0
  2712. drivers/clk/at91/clk-generated.c +306 −0
  2713. drivers/clk/at91/clk-peripheral.c +16 −8
  2714. drivers/clk/at91/clk-system.c +2 −1
  2715. drivers/clk/at91/clk-utmi.c +2 −2
  2716. drivers/clk/at91/pmc.c +21 −0
  2717. drivers/clk/at91/pmc.h +3 −0
  2718. drivers/clk/bcm/Kconfig +2 −4
  2719. drivers/clk/bcm/Makefile +4 −0
  2720. drivers/clk/bcm/clk-bcm2835.c +1575 −0
  2721. drivers/clk/bcm/clk-cygnus.c +80 −75
  2722. drivers/clk/bcm/clk-iproc-pll.c +110 −86
  2723. drivers/clk/bcm/clk-iproc.h +21 −1
  2724. drivers/clk/bcm/clk-ns2.c +288 −0
  2725. drivers/clk/bcm/clk-nsp.c +139 −0
  2726. drivers/clk/berlin/bg2.c +2 −2
  2727. drivers/clk/berlin/bg2q.c +8 −8
  2728. drivers/clk/clk-bcm2835.c +0 −55
  2729. drivers/clk/clk-divider.c +10 −10
  2730. drivers/clk/clk-fractional-divider.c +33 −20
  2731. drivers/clk/clk-max77802.c +1 −1
  2732. drivers/clk/clk-multiplier.c +130 −0
  2733. drivers/clk/clk-qoriq.c +1135 −219
  2734. drivers/clk/clk-scpi.c +325 −0
  2735. drivers/clk/clk-si514.c +379 −0
  2736. drivers/clk/clk-si5351.c +10 −7
  2737. drivers/clk/clk-xgene.c +0 −1
  2738. drivers/clk/clk.c +32 −6
  2739. drivers/clk/clkdev.c +2 −1
  2740. drivers/clk/h8300/clk-div.c +5 −1
  2741. drivers/clk/hisilicon/clk-hi6220-stub.c +1 −1
  2742. drivers/clk/imx/clk-imx25.c +12 −0
  2743. drivers/clk/imx/clk-imx27.c +16 −1
  2744. drivers/clk/imx/clk-imx31.c +31 −8
  2745. drivers/clk/imx/clk-imx35.c +37 −22
  2746. drivers/clk/imx/clk-imx51-imx53.c +16 −0
  2747. drivers/clk/imx/clk-imx6q.c +11 −1
  2748. drivers/clk/imx/clk-imx6sl.c +11 −1
  2749. drivers/clk/imx/clk-imx6sx.c +9 −0
  2750. drivers/clk/imx/clk-imx6ul.c +18 −0
  2751. drivers/clk/imx/clk-imx7d.c +14 −0
  2752. drivers/clk/imx/clk-pllv2.c +4 −8
  2753. drivers/clk/imx/clk-vf610.c +1 −0
  2754. drivers/clk/imx/clk.c +38 −0
  2755. drivers/clk/imx/clk.h +1 −0
  2756. drivers/clk/keystone/pll.c +1 −1
  2757. drivers/clk/mediatek/Makefile +1 −1
  2758. drivers/clk/mediatek/clk-apmixed.c +107 −0
  2759. drivers/clk/mediatek/clk-gate.c +1 −1
  2760. drivers/clk/mediatek/clk-mt8173.c +335 −12
  2761. drivers/clk/mediatek/clk-mtk.c +30 −6
  2762. drivers/clk/mediatek/clk-mtk.h +22 −2
  2763. drivers/clk/mediatek/clk-pll.c +1 −6
  2764. drivers/clk/mvebu/common.c +1 −1
  2765. drivers/clk/mxs/clk-frac.c +9 −3
  2766. drivers/clk/nxp/clk-lpc18xx-ccu.c +15 −2
  2767. drivers/clk/nxp/clk-lpc18xx-cgu.c +39 −3
  2768. drivers/clk/qcom/Kconfig +9 −0
  2769. drivers/clk/qcom/Makefile +1 −0
  2770. drivers/clk/qcom/clk-rcg.c +230 −0
  2771. drivers/clk/qcom/clk-rcg.h +7 −1
  2772. drivers/clk/qcom/clk-rcg2.c +162 −8
  2773. drivers/clk/qcom/common.c +32 −10
  2774. drivers/clk/qcom/common.h +2 −2
  2775. drivers/clk/qcom/gcc-apq8084.c +42 −7
  2776. drivers/clk/qcom/gcc-ipq806x.c +0 −7
  2777. drivers/clk/qcom/gcc-msm8660.c +0 −7
  2778. drivers/clk/qcom/gcc-msm8916.c +549 −20
  2779. drivers/clk/qcom/gcc-msm8960.c +18 −2
  2780. drivers/clk/qcom/gcc-msm8974.c +15 −7
  2781. drivers/clk/qcom/gdsc.c +237 −0
  2782. drivers/clk/qcom/gdsc.h +68 −0
  2783. drivers/clk/qcom/lcc-ipq806x.c +0 −7
  2784. drivers/clk/qcom/lcc-msm8960.c +0 −7
  2785. drivers/clk/qcom/mmcc-apq8084.c +87 −24
  2786. drivers/clk/qcom/mmcc-msm8960.c +404 −7
  2787. drivers/clk/qcom/mmcc-msm8974.c +81 −11
  2788. drivers/clk/rockchip/clk-mmc-phase.c +46 −19
  2789. drivers/clk/rockchip/clk-pll.c +74 −61
  2790. drivers/clk/rockchip/clk.c +4 −2
  2791. drivers/clk/samsung/clk-cpu.c +5 −5
  2792. drivers/clk/samsung/clk-exynos5250.c +13 −1
  2793. drivers/clk/samsung/clk-exynos7.c +319 −148
  2794. drivers/clk/shmobile/clk-mstp.c +5 −1
  2795. drivers/clk/shmobile/clk-r8a7778.c +4 −4
  2796. drivers/clk/sirf/clk-atlas7.c +200 −158
  2797. drivers/clk/st/clk-flexgen.c +4 −3
  2798. drivers/clk/st/clkgen-mux.c +3 −0
  2799. drivers/clk/st/clkgen-pll.c +461 −8
  2800. drivers/clk/st/clkgen.h +2 −0
  2801. drivers/clk/sunxi/Makefile +3 −0
  2802. drivers/clk/sunxi/clk-a10-codec.c +44 −0
  2803. drivers/clk/sunxi/clk-a10-mod1.c +81 −0
  2804. drivers/clk/sunxi/clk-a10-pll2.c +216 −0
  2805. drivers/clk/sunxi/clk-simple-gates.c +2 −0
  2806. drivers/clk/sunxi/clk-sun6i-apb0-gates.c +1 −0
  2807. drivers/clk/sunxi/clk-sun6i-apb0.c +1 −0
  2808. drivers/clk/sunxi/clk-sun6i-ar100.c +1 −0
  2809. drivers/clk/sunxi/clk-sun8i-apb0.c +1 −0
  2810. drivers/clk/sunxi/clk-sun9i-mmc.c +1 −0
  2811. drivers/clk/sunxi/clk-sunxi.c +1 −0
  2812. drivers/clk/tegra/clk-dfll.c +57 −57
  2813. drivers/clk/tegra/clk-emc.c +1 −3
  2814. drivers/clk/tegra/clk-tegra-audio.c +18 −7
  2815. drivers/clk/tegra/clk-tegra114.c +7 −1
  2816. drivers/clk/tegra/clk-tegra124.c +7 −1
  2817. drivers/clk/tegra/clk-tegra30.c +7 −1
  2818. drivers/clk/tegra/clk.h +67 −39
  2819. drivers/clk/tegra/cvb.c +0 −7
  2820. drivers/clk/ti/clk-3xxx.c +1 −1
  2821. drivers/clk/ti/clk-7xx.c +1 −17
  2822. drivers/clk/ti/clkt_dflt.c +2 −2
  2823. drivers/clk/versatile/Kconfig +1 −1
  2824. drivers/clk/versatile/clk-icst.c +3 −1
  2825. drivers/clocksource/Kconfig +22 −0
  2826. drivers/clocksource/Makefile +4 −1
  2827. drivers/clocksource/arm_arch_timer.c +1 −9
  2828. drivers/clocksource/arm_global_timer.c +7 −2
  2829. drivers/clocksource/clksrc-probe.c +5 −1
  2830. drivers/clocksource/em_sti.c +0 −2
  2831. drivers/clocksource/exynos_mct.c +8 −4
  2832. drivers/clocksource/fsl_ftm_timer.c +3 −3
  2833. drivers/clocksource/h8300_timer16.c +0 −1
  2834. drivers/clocksource/h8300_timer8.c +0 −1
  2835. drivers/clocksource/h8300_tpu.c +0 −1
  2836. drivers/clocksource/mips-gic-timer.c +4 −3
  2837. drivers/clocksource/mtk_timer.c +16 −10
  2838. drivers/clocksource/numachip.c +95 −0
  2839. drivers/clocksource/rockchip_timer.c +1 −1
  2840. drivers/clocksource/samsung_pwm_timer.c +1 −1
  2841. drivers/clocksource/sh_cmt.c +0 −1
  2842. drivers/clocksource/sh_mtu2.c +3 −1
  2843. drivers/clocksource/tango_xtal.c +66 −0
  2844. drivers/clocksource/tcb_clksrc.c +10 −2
  2845. drivers/clocksource/time-armada-370-xp.c +14 −0
  2846. drivers/clocksource/time-pistachio.c +2 −1
  2847. drivers/clocksource/timer-atmel-st.c +22 −9
  2848. drivers/clocksource/timer-digicolor.c +1 −1
  2849. drivers/clocksource/timer-imx-gpt.c +2 −1
  2850. drivers/clocksource/timer-keystone.c +1 −1
  2851. drivers/clocksource/timer-prima2.c +1 −1
  2852. drivers/clocksource/timer-ti-32k.c +126 −0
  2853. drivers/clocksource/vf_pit_timer.c +1 −1
  2854. drivers/connector/connector.c +2 −1
  2855. drivers/cpufreq/Kconfig.arm +28 −0
  2856. drivers/cpufreq/Makefile +3 −1
  2857. drivers/cpufreq/acpi-cpufreq.c +3 −0
  2858. drivers/cpufreq/arm_big_little.c +13 −9
  2859. drivers/cpufreq/arm_big_little.h +1 −1
  2860. drivers/cpufreq/arm_big_little_dt.c +2 −2
  2861. drivers/cpufreq/cppc_cpufreq.c +175 −0
  2862. drivers/cpufreq/cpufreq-dt.c +5 −5
  2863. drivers/cpufreq/cpufreq.c +23 −93
  2864. drivers/cpufreq/cpufreq_conservative.c +18 −13
  2865. drivers/cpufreq/cpufreq_governor.c +29 −36
  2866. drivers/cpufreq/cpufreq_governor.h +0 −1
  2867. drivers/cpufreq/cpufreq_ondemand.c +1 −9
  2868. drivers/cpufreq/cpufreq_opp.c +0 −114
  2869. drivers/cpufreq/exynos5440-cpufreq.c +3 −3
  2870. drivers/cpufreq/imx6q-cpufreq.c +48 −8
  2871. drivers/cpufreq/integrator-cpufreq.c +2 −0
  2872. drivers/cpufreq/intel_pstate.c +202 −83
  2873. drivers/cpufreq/mt8173-cpufreq.c +3 −3
  2874. drivers/cpufreq/powernv-cpufreq.c +8 −2
  2875. drivers/cpufreq/s5pv210-cpufreq.c +2 −2
  2876. drivers/cpufreq/scpi-cpufreq.c +124 −0
  2877. drivers/cpufreq/tegra20-cpufreq.c +0 −2
  2878. drivers/cpuidle/cpuidle-mvebu-v7.c +21 −25
  2879. drivers/crypto/Kconfig +3 −2
  2880. drivers/crypto/amcc/crypto4xx_core.c +2 −21
  2881. drivers/crypto/atmel-aes.c +14 −30
  2882. drivers/crypto/atmel-sha.c +14 −19
  2883. drivers/crypto/atmel-tdes.c +12 −23
  2884. drivers/crypto/bfin_crc.c +3 −22
  2885. drivers/crypto/caam/caamalg.c +171 −61
  2886. drivers/crypto/caam/caamhash.c +72 −59
  2887. drivers/crypto/caam/desc.h +0 −1
  2888. drivers/crypto/caam/sg_sw_sec4.h +2 −70
  2889. drivers/crypto/ccp/Kconfig +6 −7
  2890. drivers/crypto/ccp/ccp-crypto-aes-cmac.c +19 −1
  2891. drivers/crypto/ccp/ccp-crypto-main.c +4 −2
  2892. drivers/crypto/ccp/ccp-crypto-sha.c +13 −0
  2893. drivers/crypto/ccp/ccp-ops.c +69 −39
  2894. drivers/crypto/ccp/ccp-pci.c +1 −1
  2895. drivers/crypto/ccp/ccp-platform.c +12 −9
  2896. drivers/crypto/hifn_795x.c +0 −2
  2897. drivers/crypto/marvell/cesa.h +31 −24
  2898. drivers/crypto/marvell/cipher.c +7 −6
  2899. drivers/crypto/marvell/hash.c +226 −245
  2900. drivers/crypto/marvell/tdma.c +22 −20
  2901. drivers/crypto/n2_core.c +1 −1
  2902. drivers/crypto/nx/nx-842-powernv.c +2 −2
  2903. drivers/crypto/nx/nx-842-pseries.c +6 −2
  2904. drivers/crypto/picoxcell_crypto.c +1 −0
  2905. drivers/crypto/qat/qat_common/Makefile +9 −3
  2906. drivers/crypto/qat/qat_common/adf_common_drv.h +1 −3
  2907. drivers/crypto/qat/qat_common/adf_ctl_drv.c +1 −7
  2908. drivers/crypto/qat/qat_common/adf_init.c +3 −5
  2909. drivers/crypto/qat/qat_common/adf_sriov.c +2 −5
  2910. drivers/crypto/qat/qat_common/qat_algs.c +128 −50
  2911. drivers/crypto/qat/qat_common/qat_asym_algs.c +158 −55
  2912. drivers/crypto/qat/qat_common/qat_crypto.c +48 −31
  2913. drivers/crypto/qat/qat_common/qat_hal.c +2 −3
  2914. drivers/crypto/qat/qat_common/qat_rsakey.asn1 +0 −5
  2915. drivers/crypto/qat/qat_common/qat_rsaprivkey.asn1 +11 −0
  2916. drivers/crypto/qat/qat_common/qat_rsapubkey.asn1 +4 −0
  2917. drivers/crypto/qce/ablkcipher.c +10 −20
  2918. drivers/crypto/qce/cipher.h +0 −4
  2919. drivers/crypto/qce/dma.c +0 −52
  2920. drivers/crypto/qce/dma.h +0 −5
  2921. drivers/crypto/qce/sha.c +7 −11
  2922. drivers/crypto/qce/sha.h +0 −2
  2923. drivers/crypto/sahara.c +22 −86
  2924. drivers/crypto/talitos.c +18 −86
  2925. drivers/crypto/ux500/cryp/cryp_core.c +10 −61
  2926. drivers/crypto/ux500/hash/hash_core.c +8 −42
  2927. drivers/devfreq/devfreq.c +4 −3
  2928. drivers/dma-buf/fence.c +98 −0
  2929. drivers/dma/Kconfig +2 −2
  2930. drivers/dma/Makefile +1 −1
  2931. drivers/dma/acpi-dma.c +22 −14
  2932. drivers/dma/at_hdmac.c +140 −44
  2933. drivers/dma/at_hdmac_regs.h +4 −4
  2934. drivers/dma/at_xdmac.c +75 −66
  2935. drivers/dma/dmaengine.c +11 −5
  2936. drivers/dma/dw/core.c +39 −38
  2937. drivers/dma/dw/pci.c +7 −13
  2938. drivers/dma/dw/platform.c +16 −1
  2939. drivers/dma/edma.c +1606 −252
  2940. drivers/dma/fsldma.c +1 −0
  2941. drivers/dma/hsu/Kconfig +2 −7
  2942. drivers/dma/hsu/hsu.c +7 −17
  2943. drivers/dma/hsu/hsu.h +1 −0
  2944. drivers/dma/hsu/pci.c +1 −1
  2945. drivers/dma/idma64.c +20 −18
  2946. drivers/dma/idma64.h +5 −9
  2947. drivers/dma/imx-sdma.c +2 −5
  2948. drivers/dma/ioat/dma.c +2 −1
  2949. drivers/dma/ioat/dma.h +4 −2
  2950. drivers/dma/ioat/init.c +112 −2
  2951. drivers/dma/ioat/prep.c +34 −0
  2952. drivers/dma/mic_x100_dma.c +38 −1
  2953. drivers/dma/moxart-dma.c +1 −0
  2954. drivers/dma/mpc512x_dma.c +1 −0
  2955. drivers/dma/omap-dma.c +5 −1
  2956. drivers/dma/pxa_dma.c +25 −6
  2957. drivers/dma/sh/usb-dmac.c +8 −3
  2958. drivers/dma/sirf-dma.c +1 −0
  2959. drivers/dma/ste_dma40.c +1 −1
  2960. drivers/dma/sun4i-dma.c +3 −3
  2961. drivers/dma/sun6i-dma.c +1 −0
  2962. drivers/dma/ti-dma-crossbar.c +221 −30
  2963. drivers/dma/virt-dma.h +9 −9
  2964. drivers/dma/xgene-dma.c +19 −90
  2965. drivers/dma/xilinx/xilinx_vdma.c +1 −0
  2966. drivers/dma/zx296702_dma.c +2 −2
  2967. drivers/edac/Makefile +2 −0
  2968. drivers/edac/altera_edac.c +8 −12
  2969. drivers/edac/altera_edac.h +1 −4
  2970. drivers/edac/amd64_edac.c +28 −13
  2971. drivers/edac/amd64_edac.h +3 −55
  2972. drivers/edac/debugfs.c +163 −0
  2973. drivers/edac/edac_core.h +2 −0
  2974. drivers/edac/edac_mc.c +1 −1
  2975. drivers/edac/edac_mc_sysfs.c +28 −122
  2976. drivers/edac/edac_module.h +29 −5
  2977. drivers/edac/ghes_edac.c +2 −22
  2978. drivers/edac/i3200_edac.c +1 −1
  2979. drivers/edac/i5100_edac.c +19 −18
  2980. drivers/edac/ie31200_edac.c +1 −1
  2981. drivers/edac/ppc4xx_edac.c +1 −0
  2982. drivers/edac/sb_edac.c +4 −4
  2983. drivers/edac/x38_edac.c +1 −1
  2984. drivers/edac/xgene_edac.c +985 −208
  2985. drivers/extcon/extcon-arizona.c +124 −40
  2986. drivers/extcon/extcon-axp288.c +11 −24
  2987. drivers/extcon/extcon-gpio.c +70 −60
  2988. drivers/extcon/extcon-max14577.c +9 −8
  2989. drivers/extcon/extcon-max77693.c +17 −15
  2990. drivers/extcon/extcon-max77843.c +15 −12
  2991. drivers/extcon/extcon-max8997.c +11 −10
  2992. drivers/extcon/extcon-rt8973a.c +4 −3
  2993. drivers/extcon/extcon-sm5502.c +4 −3
  2994. drivers/extcon/extcon.c +32 −29
  2995. drivers/firewire/core-cdev.c +1 −1
  2996. drivers/firewire/ohci.c +5 −0
  2997. drivers/firmware/Kconfig +26 −0
  2998. drivers/firmware/Makefile +3 −1
  2999. drivers/firmware/arm_scpi.c +771 −0
  3000. drivers/firmware/efi/Kconfig +22 −0
  3001. drivers/firmware/efi/Makefile +9 −0
  3002. drivers/firmware/efi/efi-pstore.c +2 −1
  3003. drivers/firmware/efi/efi.c +82 −25
  3004. drivers/firmware/efi/esrt.c +3 −16
  3005. drivers/firmware/efi/fake_mem.c +238 −0
  3006. drivers/firmware/efi/libstub/Makefile +36 −6
  3007. drivers/firmware/efi/libstub/arm-stub.c +73 −15
  3008. drivers/firmware/efi/libstub/arm64-stub.c +12 −2
  3009. drivers/firmware/efi/libstub/fdt.c +0 −9
  3010. drivers/firmware/efi/libstub/string.c +57 −0
  3011. drivers/firmware/psci.c +98 −10
  3012. drivers/firmware/qcom_scm-32.c +3 −3
  3013. drivers/firmware/raspberrypi.c +260 −0
  3014. drivers/fpga/Kconfig +29 −0
  3015. drivers/fpga/Makefile +10 −0
  3016. drivers/fpga/fpga-mgr.c +380 −0
  3017. drivers/fpga/socfpga.c +616 −0
  3018. drivers/fpga/zynq-fpga.c +514 −0
  3019. drivers/gpio/Kconfig +103 −93
  3020. drivers/gpio/Makefile +3 −2
  3021. drivers/gpio/gpio-104-idio-16.c +216 −0
  3022. drivers/gpio/gpio-74x164.c +0 −1
  3023. drivers/gpio/gpio-altera.c +10 −5
  3024. drivers/gpio/gpio-amdpt.c +261 −0
  3025. drivers/gpio/gpio-arizona.c +2 −0
  3026. drivers/gpio/gpio-ath79.c +60 −59
  3027. drivers/gpio/gpio-etraxfs.c +17 −6
  3028. drivers/gpio/gpio-generic.c +19 −39
  3029. drivers/gpio/gpio-it87.c +411 −0
  3030. drivers/gpio/gpio-it8761e.c +0 −230
  3031. drivers/gpio/gpio-lpc18xx.c +2 −12
  3032. drivers/gpio/gpio-max7301.c +0 −1
  3033. drivers/gpio/gpio-max730x.c +0 −1
  3034. drivers/gpio/gpio-mc33880.c +0 −1
  3035. drivers/gpio/gpio-mcp23s08.c +0 −2
  3036. drivers/gpio/gpio-moxart.c +2 −12
  3037. drivers/gpio/gpio-msm-v2.c +0 −453
  3038. drivers/gpio/gpio-mvebu.c +2 −12
  3039. drivers/gpio/gpio-mxc.c +1 −1
  3040. drivers/gpio/gpio-omap.c +43 −39
  3041. drivers/gpio/gpio-pca953x.c +36 −9
  3042. drivers/gpio/gpio-pl061.c +74 −38
  3043. drivers/gpio/gpio-sodaville.c +1 −1
  3044. drivers/gpio/gpio-sx150x.c +14 −17
  3045. drivers/gpio/gpio-tb10x.c +2 −12
  3046. drivers/gpio/gpio-tz1090-pdc.c +2 −12
  3047. drivers/gpio/gpio-vf610.c +21 −22
  3048. drivers/gpio/gpio-xlp.c +11 −10
  3049. drivers/gpio/gpio-zx.c +4 −24
  3050. drivers/gpio/gpio-zynq.c +22 −10
  3051. drivers/gpio/gpiolib-acpi.c +129 −45
  3052. drivers/gpio/gpiolib-legacy.c +4 −4
  3053. drivers/gpio/gpiolib-of.c +10 −10
  3054. drivers/gpio/gpiolib.c +153 −25
  3055. drivers/gpio/gpiolib.h +12 −1
  3056. drivers/gpu/drm/Kconfig +2 −0
  3057. drivers/gpu/drm/Makefile +5 −1
  3058. drivers/gpu/drm/amd/amdgpu/amdgpu.h +88 −133
  3059. drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c +0 −1
  3060. drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v7.c +2 −2
  3061. drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c +2 −2
  3062. drivers/gpu/drm/amd/amdgpu/amdgpu_atombios.c +6 −2
  3063. drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c +2 −2
  3064. drivers/gpu/drm/amd/amdgpu/amdgpu_bios.c +0 −1
  3065. drivers/gpu/drm/amd/amdgpu/amdgpu_cgs.c +0 −39
  3066. drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c +106 −124
  3067. drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c +3 −0
  3068. drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +34 −13
  3069. drivers/gpu/drm/amd/amdgpu/amdgpu_display.c +6 −16
  3070. drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c +21 −11
  3071. drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c +17 −0
  3072. drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c +170 −310
  3073. drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c +32 −21
  3074. drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c +4 −4
  3075. drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c +40 −37
  3076. drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h +9 −5
  3077. drivers/gpu/drm/amd/amdgpu/amdgpu_object.c +2 −0
  3078. drivers/gpu/drm/amd/amdgpu/amdgpu_object.h +3 −4
  3079. drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c +11 −2
  3080. drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c +26 −45
  3081. drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c +16 −30
  3082. drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c +14 −19
  3083. drivers/gpu/drm/amd/amdgpu/amdgpu_semaphore.c +1 −1
  3084. drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c +34 −31
  3085. drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h +62 −44
  3086. drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c +6 −1
  3087. drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c +5 −0
  3088. drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c +5 −0
  3089. drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +101 −99
  3090. drivers/gpu/drm/amd/amdgpu/atom.c +51 −2
  3091. drivers/gpu/drm/amd/amdgpu/atom.h +1 −1
  3092. drivers/gpu/drm/amd/amdgpu/atombios_encoders.c +1 −2
  3093. drivers/gpu/drm/amd/amdgpu/ci_dpm.c +9 −7
  3094. drivers/gpu/drm/amd/amdgpu/cik.c +3 −0
  3095. drivers/gpu/drm/amd/amdgpu/cik_sdma.c +62 −87
  3096. drivers/gpu/drm/amd/amdgpu/cz_dpm.c +23 −8
  3097. drivers/gpu/drm/amd/amdgpu/cz_smc.c +48 −12
  3098. drivers/gpu/drm/amd/amdgpu/dce_v10_0.c +130 −137
  3099. drivers/gpu/drm/amd/amdgpu/dce_v11_0.c +149 −139
  3100. drivers/gpu/drm/amd/amdgpu/dce_v8_0.c +132 −137
  3101. drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c +0 −20
  3102. drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c +948 −284
  3103. drivers/gpu/drm/amd/amdgpu/gmc_v7_0.c +44 −15
  3104. drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c +57 −8
  3105. drivers/gpu/drm/amd/amdgpu/kv_dpm.c +9 −3
  3106. drivers/gpu/drm/amd/amdgpu/sdma_v2_4.c +72 −103
  3107. drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c +110 −103
  3108. drivers/gpu/drm/amd/amdgpu/uvd_v4_2.c +0 −1
  3109. drivers/gpu/drm/amd/amdgpu/uvd_v5_0.c +0 −1
  3110. drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c +0 −1
  3111. drivers/gpu/drm/amd/amdgpu/vce_v2_0.c +0 −1
  3112. drivers/gpu/drm/amd/amdgpu/vce_v3_0.c +3 −3
  3113. drivers/gpu/drm/amd/amdgpu/vi.c +42 −11
  3114. drivers/gpu/drm/amd/include/amd_shared.h +1 −0
  3115. drivers/gpu/drm/amd/include/asic_reg/gca/gfx_8_1_d.h +2791 −0
  3116. drivers/gpu/drm/amd/include/asic_reg/gca/gfx_8_1_enum.h +6808 −0
.mailmap+1−0
@@ -59,6 +59,7 @@ James Bottomley <jejb@mulgrave.(none)> · 58 unmodified lines
5959 James Bottomley <jejb@titanic.il.steeleye.com>
6060 James E Wilson <wilson@specifix.com>
6161 James Ketrenos <jketreno@io.(none)>
62+<javier@osg.samsung.com> <javier.martinez@collabora.co.uk>
6263 Jean Tourrilhes <jt@hpl.hp.com>
6364 Jeff Garzik <jgarzik@pretzel.yyz.us>
6465 Jens Axboe <axboe@suse.de>
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvorenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-arvo+0−0

File renamed without changes.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-iskurenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-isku+0−0

File renamed without changes.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus+98−1
@@ -1,3 +1,14 @@
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+
112 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/startup_profile
213 Date: October 2010
314 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -22,6 +33,40 @@ Description: When read, this file returns the raw integer version number of the · 18 unmodified lines
2233 Please read binary attribute info which contains firmware version.
2334 Users: http://roccat.sourceforge.net
2435
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+
2570 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
2671 Date: August 2010
2772 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -34,6 +79,22 @@ Description: The mouse can store 5 profiles which can be switched by the · 6 unmodified lines
3479 Write control to select profile and read profile_buttons instead.
3580 Users: http://roccat.sourceforge.net
3681
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+
3798 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
3899 Date: August 2010
39100 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -45,4 +106,40 @@ Description: The mouse can store 5 profiles which can be switched by the · 5 unmodified lines
45106 The returned data is 43 bytes in size.
46107 This file is readonly.
47108 Write control to select profile and read profile_settings instead.
48−Users: http://roccat.sourceforge.net
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
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepurerenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-konepure+0−0

File renamed without changes.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus+50−0
@@ -8,6 +8,17 @@ Description: The integer value of this attribute ranges from 1-4. · 7 unmodified lines
88 Has never been used. If bookkeeping is done, it's done in userland tools.
99 Users: http://roccat.sourceforge.net
1010
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+
1122 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x
1223 Date: January 2011
1324 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -40,6 +51,29 @@ Description: When read, this file returns the raw integer version number of the · 26 unmodified lines
4051 Obsoleted by binary sysfs attribute "info".
4152 Users: http://roccat.sourceforge.net
4253
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+
4377 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
4478 Date: January 2011
4579 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -52,6 +86,22 @@ Description: The mouse can store 5 profiles which can be switched by the · 6 unmodified lines
5286 Write control to select profile and read profile_buttons instead.
5387 Users: http://roccat.sourceforge.net
5488
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+
55105 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
56106 Date: January 2011
57107 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-luarenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-lua+0−0

File renamed without changes.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra+50−0
@@ -37,6 +37,29 @@ Description: When read, this file returns the raw integer version number of the · 36 unmodified lines
3737 Please use binary attribute "info" which provides this information.
3838 Users: http://roccat.sourceforge.net
3939
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+
4063 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
4164 Date: August 2010
4265 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -49,6 +72,22 @@ Description: The mouse can store 5 profiles which can be switched by the · 6 unmodified lines
4972 Write control to select profile and read profile_buttons instead.
5073 Users: http://roccat.sourceforge.net
5174
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+
5291 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
5392 Date: August 2010
5493 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -62,6 +101,17 @@ Description: The mouse can store 5 profiles which can be switched by the · 7 unmodified lines
62101 Write control to select profile and read profile_settings instead.
63102 Users: http://roccat.sourceforge.net
64103
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+
65115 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/startup_profile
66116 Date: August 2010
67117 Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryosrenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-ryos+0−0

File renamed without changes.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savurenamed from Documentation/ABI/testing/sysfs-driver-hid-roccat-savu+0−0

File renamed without changes.

Documentation/ABI/stable/sysfs-class-tpm+2−2
@@ -116,7 +116,7 @@ Description: The "pubek" property will return the TPM's public endorsement · 115 unmodified lines
116116 owner's authorization. Since the TPM driver doesn't store any
117117 secrets, it can't authorize its own request for the pubek,
118118 making it unaccessible. The public endorsement key is gener-
119− ated at TPM menufacture time and exists for the life of the
119+ ated at TPM manufacture time and exists for the life of the
120120 chip.
121121
122122 Example output:
@@ -163,7 +163,7 @@ Date: April 2006 · 40 unmodified lines
163163 KernelVersion: 2.6.17
164164 Contact: tpmdd-devel@lists.sf.net
165165 Description: The "temp_deactivated" property returns a '1' if the chip has
166− been temporarily dectivated, usually until the next power
166+ been temporarily deactivated, usually until the next power
167167 cycle. Whether a warm boot (reboot) will clear a TPM chip
168168 from a temp_deactivated state is platform specific.
169169
Documentation/ABI/stable/sysfs-firmware-opal-elog+1−1
@@ -57,4 +57,4 @@ Description: · 56 unmodified lines
5757 Shortly after acknowledging it, the log
5858 entry will be removed from sysfs.
5959 Reading this file will list the supported
60− operations (curently just acknowledge).
60+ operations (currently just acknowledge).
Documentation/ABI/testing/configfs-stp-policy+48−0
@@ -0,0 +1,48 @@
1+What: /config/stp-policy
2+Date: June 2015
3+KernelVersion: 4.3
4+Description:
5+ This group contains policies mandating Master/Channel allocation
6+ for software sources wishing to send trace data over an STM
7+ device.
8+
9+What: /config/stp-policy/<device>.<policy>
10+Date: June 2015
11+KernelVersion: 4.3
12+Description:
13+ This group is the root of a policy; its name is a concatenation
14+ of an stm device name to which this policy applies and an
15+ arbitrary string. If <device> part doesn't match an existing
16+ stm device, mkdir will fail with ENODEV; if that device already
17+ has a policy assigned to it, mkdir will fail with EBUSY.
18+
19+What: /config/stp-policy/<device>.<policy>/device
20+Date: June 2015
21+KernelVersion: 4.3
22+Description:
23+ STM device to which this policy applies, read only. Same as the
24+ <device> component of its parent directory.
25+
26+What: /config/stp-policy/<device>.<policy>/<node>
27+Date: June 2015
28+KernelVersion: 4.3
29+Description:
30+ Policy node is a string identifier that software clients will
31+ use to request a master/channel to be allocated and assigned to
32+ them.
33+
34+What: /config/stp-policy/<device>.<policy>/<node>/masters
35+Date: June 2015
36+KernelVersion: 4.3
37+Description:
38+ Range of masters from which to allocate for users of this node.
39+ Write two numbers: the first master and the last master number.
40+
41+What: /config/stp-policy/<device>.<policy>/<node>/channels
42+Date: June 2015
43+KernelVersion: 4.3
44+Description:
45+ Range of channels from which to allocate for users of this node.
46+ Write two numbers: the first channel and the last channel
47+ number.
48+
Documentation/ABI/testing/sysfs-block+7−0
@@ -60,6 +60,13 @@ Description: · 59 unmodified lines
6060 Indicates whether a storage device is capable of storing
6161 integrity metadata. Set if the device is T10 PI-capable.
6262
63+What: /sys/block/<disk>/integrity/protection_interval_bytes
64+Date: July 2015
65+Contact: Martin K. Petersen <martin.petersen@oracle.com>
66+Description:
67+ Describes the number of data bytes which are protected
68+ by one integrity tuple. Typically the device's logical
69+ block size.
6370
6471 What: /sys/block/<disk>/integrity/write_generate
6572 Date: June 2008
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x+76−7
@@ -8,13 +8,6 @@ Description: (RW) Enable/disable tracing on this specific trace entiry. · 7 unmodified lines
88 of coresight components linking the source to the sink is
99 configured and managed automatically by the coresight framework.
1010
11−What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/status
12−Date: November 2014
13−KernelVersion: 3.19
14−Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
15−Description: (R) List various control and status registers. The specific
16− layout and content is driver specific.
17−
1811 What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_idx
1912 Date: November 2014
2013 KernelVersion: 3.19
@@ -251,3 +244,79 @@ Date: November 2014 · 230 unmodified lines
251244 KernelVersion: 3.19
252245 Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
253246 Description: (RW) Define the event that controls the trigger.
247+
248+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cpu
249+Date: October 2015
250+KernelVersion: 4.4
251+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
252+Description: (RO) Holds the cpu number this tracer is affined to.
253+
254+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmccr
255+Date: September 2015
256+KernelVersion: 4.4
257+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
258+Description: (RO) Print the content of the ETM Configuration Code register
259+ (0x004). The value is read directly from the HW.
260+
261+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmccer
262+Date: September 2015
263+KernelVersion: 4.4
264+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
265+Description: (RO) Print the content of the ETM Configuration Code Extension
266+ register (0x1e8). The value is read directly from the HW.
267+
268+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmscr
269+Date: September 2015
270+KernelVersion: 4.4
271+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
272+Description: (RO) Print the content of the ETM System Configuration
273+ register (0x014). The value is read directly from the HW.
274+
275+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmidr
276+Date: September 2015
277+KernelVersion: 4.4
278+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
279+Description: (RO) Print the content of the ETM ID register (0x1e4). The
280+ value is read directly from the HW.
281+
282+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmcr
283+Date: September 2015
284+KernelVersion: 4.4
285+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
286+Description: (RO) Print the content of the ETM Main Control register (0x000).
287+ The value is read directly from the HW.
288+
289+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtraceidr
290+Date: September 2015
291+KernelVersion: 4.4
292+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
293+Description: (RO) Print the content of the ETM Trace ID register (0x200).
294+ The value is read directly from the HW.
295+
296+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmteevr
297+Date: September 2015
298+KernelVersion: 4.4
299+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
300+Description: (RO) Print the content of the ETM Trace Enable Event register
301+ (0x020). The value is read directly from the HW.
302+
303+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtsscr
304+Date: September 2015
305+KernelVersion: 4.4
306+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
307+Description: (RO) Print the content of the ETM Trace Start/Stop Conrol
308+ register (0x018). The value is read directly from the HW.
309+
310+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtecr1
311+Date: September 2015
312+KernelVersion: 4.4
313+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
314+Description: (RO) Print the content of the ETM Enable Conrol #1
315+ register (0x024). The value is read directly from the HW.
316+
317+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtecr2
318+Date: September 2015
319+KernelVersion: 4.4
320+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
321+Description: (RO) Print the content of the ETM Enable Conrol #2
322+ register (0x01c). The value is read directly from the HW.
Documentation/ABI/testing/sysfs-bus-iio+32−0
@@ -581,6 +581,7 @@ What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en · 580 unmodified lines
581581 What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
582582 What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
583583 What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
584+What: /sys/.../iio:deviceX/events/in_voltageY_thresh_either_en
584585 What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
585586 What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
586587 KernelVersion: 2.6.37
@@ -1459,3 +1460,34 @@ Description: · 872 unmodified lines
14591460 measurements and return the average value as output data. Each
14601461 value resulted from <type>[_name]_oversampling_ratio measurements
14611462 is considered as one sample for <type>[_name]_sampling_frequency.
1463+
1464+What: /sys/bus/iio/devices/iio:deviceX/in_concentration_raw
1465+What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_raw
1466+What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_raw
1467+What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_co2_raw
1468+What: /sys/bus/iio/devices/iio:deviceX/in_concentration_voc_raw
1469+What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_voc_raw
1470+KernelVersion: 4.3
1471+Contact: linux-iio@vger.kernel.org
1472+Description:
1473+ Raw (unscaled no offset etc.) percentage reading of a substance.
1474+
1475+What: /sys/bus/iio/devices/iio:deviceX/in_resistance_raw
1476+What: /sys/bus/iio/devices/iio:deviceX/in_resistanceX_raw
1477+What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw
1478+What: /sys/bus/iio/devices/iio:deviceX/out_resistanceX_raw
1479+KernelVersion: 4.3
1480+Contact: linux-iio@vger.kernel.org
1481+Description:
1482+ Raw (unscaled no offset etc.) resistance reading that can be processed
1483+ into an ohm value.
1484+
1485+What: /sys/bus/iio/devices/iio:deviceX/heater_enable
1486+KernelVersion: 4.1.0
1487+Contact: linux-iio@vger.kernel.org
1488+Description:
1489+ '1' (enable) or '0' (disable) specifying the enable
1490+ of heater function. Same reading values apply
1491+ This ABI is especially applicable for humidity sensors
1492+ to heatup the device and get rid of any condensation
1493+ in some humidity environment
Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435+43−0
@@ -0,0 +1,43 @@
1+What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_sensing_mode
2+Date: August 2015
3+KernelVersion: 4.2.0
4+Contact: source@cogentembedded.com
5+Description:
6+ Program sensor type for threshold detector inputs.
7+ Could be either "GND-Open" or "Supply-Open" mode. Y is a
8+ threshold detector input channel. Channels 0..7, 8..15, 16..23
9+ and 24..31 has common sensor types.
10+
11+What: /sys/bus/iio/devices/iio:deviceX/events/in_voltageY_thresh_falling_value
12+Date: August 2015
13+KernelVersion: 4.2.0
14+Contact: source@cogentembedded.com
15+Description:
16+ Channel Y low voltage threshold. If sensor input voltage goes lower then
17+ this value then the threshold falling event is pushed.
18+ Depending on in_voltageY_sensing_mode the low voltage threshold
19+ is separately set for "GND-Open" and "Supply-Open" modes.
20+ Channels 0..31 have common low threshold values, but could have different
21+ sensing_modes.
22+ The low voltage threshold range is between 2..21V.
23+ Hysteresis between low and high thresholds can not be lower then 2 and
24+ can not be odd.
25+ If falling threshold results hysteresis to odd value then rising
26+ threshold is automatically subtracted by one.
27+
28+What: /sys/bus/iio/devices/iio:deviceX/events/in_voltageY_thresh_rising_value
29+Date: August 2015
30+KernelVersion: 4.2.0
31+Contact: source@cogentembedded.com
32+Description:
33+ Channel Y high voltage threshold. If sensor input voltage goes higher then
34+ this value then the threshold rising event is pushed.
35+ Depending on in_voltageY_sensing_mode the high voltage threshold
36+ is separately set for "GND-Open" and "Supply-Open" modes.
37+ Channels 0..31 have common high threshold values, but could have different
38+ sensing_modes.
39+ The high voltage threshold range is between 3..22V.
40+ Hysteresis between low and high thresholds can not be lower then 2 and
41+ can not be odd.
42+ If rising threshold results hysteresis to odd value then falling
43+ threshold is automatically appended by one.
Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x+7−0
@@ -0,0 +1,7 @@
1+What: /sys/bus/iio/devices/iio:deviceX/in_concentration_VOC_short_raw
2+Date: September 2015
3+KernelVersion: 4.3
4+Contact: Matt Ranostay <mranostay@gmail.com>
5+Description:
6+ Get the raw calibration VOC value from the sensor.
7+ This value has little application outside of calibration.
Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc100x+9−0
@@ -0,0 +1,9 @@
1+What: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw
2+What: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw_available
3+KernelVersion: 4.3
4+Contact: linux-iio@vger.kernel.org
5+Description:
6+ Controls the heater device within the humidity sensor to get
7+ rid of excess condensation.
8+
9+ Valid control values are 0 = OFF, and 1 = ON.
Documentation/ABI/testing/sysfs-bus-iio-meas-spec+8−0
@@ -0,0 +1,8 @@
1+What: /sys/bus/iio/devices/iio:deviceX/battery_low
2+KernelVersion: 4.1.0
3+Contact: linux-iio@vger.kernel.org
4+Description:
5+ Reading returns either '1' or '0'. '1' means that the
6+ battery level supplied to sensor is below 2.25V.
7+ This ABI is available for tsys02d, htu21, ms8607
8+ This ABI is available for htu21, ms8607
Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs+22−0
@@ -18,3 +18,25 @@ Description: · 17 unmodified lines
1818 trigger. In order to associate the trigger with an IIO device
1919 one should write this name string to
2020 /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger.
21+
22+What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger
23+KernelVersion: 2.6.39
24+Contact: linux-iio@vger.kernel.org
25+Description:
26+ This attribute is provided by the iio-trig-sysfs stand-alone
27+ driver and it is used to activate the creation of a new trigger.
28+ In order to achieve this, one should write a positive integer
29+ into the associated file, which will serve as the id of the
30+ trigger. If the trigger with the specified id is already present
31+ in the system, an invalid argument message will be returned.
32+
33+What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger
34+KernelVersion: 2.6.39
35+Contact: linux-iio@vger.kernel.org
36+Description:
37+ This attribute is used to unregister and delete a previously
38+ created trigger from the list of available triggers. In order to
39+ achieve this, one should write a positive integer into the
40+ associated file, representing the id of the trigger that needs
41+ to be removed. If the trigger can't be found, an invalid
42+ argument message will be returned to the user.
Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth+49−0
@@ -0,0 +1,49 @@
1+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/masters/*
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description: (RW) Configure output ports for STP masters. Writing -1
6+ disables a master; any
7+
8+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_port
9+Date: June 2015
10+KernelVersion: 4.3
11+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
12+Description: (RO) Output port type:
13+ 0: not present,
14+ 1: MSU (Memory Storage Unit)
15+ 2: CTP (Common Trace Port)
16+ 4: PTI (MIPI PTI).
17+
18+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_drop
19+Date: June 2015
20+KernelVersion: 4.3
21+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
22+Description: (RW) Data retention policy setting: keep (0) or drop (1)
23+ incoming data while output port is in reset.
24+
25+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_null
26+Date: June 2015
27+KernelVersion: 4.3
28+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
29+Description: (RW) STP NULL packet generation: enabled (1) or disabled (0).
30+
31+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_flush
32+Date: June 2015
33+KernelVersion: 4.3
34+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
35+Description: (RW) Force flush data from byte packing buffer for the output
36+ port.
37+
38+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_reset
39+Date: June 2015
40+KernelVersion: 4.3
41+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
42+Description: (RO) Output port is in reset (1).
43+
44+What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_smcfreq
45+Date: June 2015
46+KernelVersion: 4.3
47+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
48+Description: (RW) STP sync packet frequency for the port. Specifies the
49+ number of clocks between mainenance packets.
Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc+33−0
@@ -0,0 +1,33 @@
1+What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/wrap
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description: (RW) Configure MSC buffer wrapping. 1 == wrapping enabled.
6+
7+What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/mode
8+Date: June 2015
9+KernelVersion: 4.3
10+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
11+Description: (RW) Configure MSC operating mode:
12+ - "single", for contiguous buffer mode (high-order alloc);
13+ - "multi", for multiblock mode;
14+ - "ExI", for DCI handler mode;
15+ - "debug", for debug mode.
16+ If operating mode changes, existing buffer is deallocated,
17+ provided there are no active users and tracing is not enabled,
18+ otherwise the write will fail.
19+
20+What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/nr_pages
21+Date: June 2015
22+KernelVersion: 4.3
23+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
24+Description: (RW) Configure MSC buffer size for "single" or "multi" modes.
25+ In single mode, this is a single number of pages, has to be
26+ power of 2. In multiblock mode, this is a comma-separated list
27+ of numbers of pages for each window to be allocated. Number of
28+ windows is not limited.
29+ Writing to this file deallocates existing buffer (provided
30+ there are no active users and tracing is not enabled) and then
31+ allocates a new one.
32+
33+
Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti+24−0
@@ -0,0 +1,24 @@
1+What: /sys/bus/intel_th/devices/<intel_th_id>-pti/mode
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description: (RW) Configure PTI output width. Currently supported values
6+ are 4, 8, 12, 16.
7+
8+What: /sys/bus/intel_th/devices/<intel_th_id>-pti/freerunning_clock
9+Date: June 2015
10+KernelVersion: 4.3
11+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
12+Description: (RW) 0: PTI trace clock acts as a strobe which only toggles
13+ when there is trace data to send. 1: PTI trace clock is a
14+ free-running clock.
15+
16+What: /sys/bus/intel_th/devices/<intel_th_id>-pti/clock_divider
17+Date: June 2015
18+KernelVersion: 4.3
19+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
20+Description: (RW) Configure PTI port clock divider:
21+ - 0: Intel TH clock rate,
22+ - 1: 1/2 Intel TH clock rate,
23+ - 2: 1/4 Intel TH clock rate,
24+ - 3: 1/8 Intel TH clock rate.
Documentation/ABI/testing/sysfs-bus-intel_th-output-devices+13−0
@@ -0,0 +1,13 @@
1+What: /sys/bus/intel_th/devices/<intel_th_id>-<device><id>/active
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description: (RW) Writes of 1 or 0 enable or disable trace output to this
6+ output device. Reads return current status.
7+
8+What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/port
9+Date: June 2015
10+KernelVersion: 4.3
11+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
12+Description: (RO) Port number, corresponding to this output device on the
13+ switch (GTH).
Documentation/ABI/testing/sysfs-bus-mei+7−0
@@ -19,3 +19,10 @@ KernelVersion: 4.2 · 18 unmodified lines
1919 Contact: Tomas Winkler <tomas.winkler@intel.com>
2020 Description: Stores mei client device uuid
2121 Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
22+
23+What: /sys/bus/mei/devices/.../version
24+Date: Aug 2015
25+KernelVersion: 4.3
26+Contact: Tomas Winkler <tomas.winkler@intel.com>
27+Description: Stores mei client protocol version
28+ Format: %d
Documentation/ABI/testing/sysfs-bus-usb+20−0
@@ -1,3 +1,23 @@
1+What: /sys/bus/usb/devices/INTERFACE/authorized
2+Date: August 2015
3+Description:
4+ This allows to authorize (1) or deauthorize (0)
5+ individual interfaces instead a whole device
6+ in contrast to the device authorization.
7+ If a deauthorized interface will be authorized
8+ so the driver probing must be triggered manually
9+ by writing INTERFACE to /sys/bus/usb/drivers_probe
10+ This allows to avoid side-effects with drivers
11+ that need multiple interfaces.
12+ A deauthorized interface cannot be probed or claimed.
13+
14+What: /sys/bus/usb/devices/usbX/interface_authorized_default
15+Date: August 2015
16+Description:
17+ This is used as value that determines if interfaces
18+ would be authorized by default.
19+ The value can be 1 or 0. It's by default 1.
20+
121 What: /sys/bus/usb/device/.../authorized
222 Date: July 2008
323 KernelVersion: 2.6.26
Documentation/ABI/testing/sysfs-class-fpga-manager+37−0
@@ -0,0 +1,37 @@
1+What: /sys/class/fpga_manager/<fpga>/name
2+Date: August 2015
3+KernelVersion: 4.3
4+Contact: Alan Tull <atull@opensource.altera.com>
5+Description: Name of low level fpga manager driver.
6+
7+What: /sys/class/fpga_manager/<fpga>/state
8+Date: August 2015
9+KernelVersion: 4.3
10+Contact: Alan Tull <atull@opensource.altera.com>
11+Description: Read fpga manager state as a string.
12+ The intent is to provide enough detail that if something goes
13+ wrong during FPGA programming (something that the driver can't
14+ fix) then userspace can know, i.e. if the firmware request
15+ fails, that could be due to not being able to find the firmware
16+ file.
17+
18+ This is a superset of FPGA states and fpga manager driver
19+ states. The fpga manager driver is walking through these steps
20+ to get the FPGA into a known operating state. It's a sequence,
21+ though some steps may get skipped. Valid FPGA states will vary
22+ by manufacturer; this is a superset.
23+
24+ * unknown = can't determine state
25+ * power off = FPGA power is off
26+ * power up = FPGA reports power is up
27+ * reset = FPGA held in reset state
28+ * firmware request = firmware class request in progress
29+ * firmware request error = firmware request failed
30+ * write init = preparing FPGA for programming
31+ * write init error = Error while preparing FPGA for
32+ programming
33+ * write = FPGA ready to receive image data
34+ * write error = Error while programming
35+ * write complete = Doing post programming steps
36+ * write complete error = Error while doing post programming
37+ * operating = FPGA is programmed and operating
Documentation/ABI/testing/sysfs-class-mic.txt+19−10
@@ -41,18 +41,15 @@ Description: · 40 unmodified lines
4141 When read, this entry provides the current state of an Intel
4242 MIC device in the context of the card OS. Possible values that
4343 will be read are:
44− "offline" - The MIC device is ready to boot the card OS. On
44+ "ready" - The MIC device is ready to boot the card OS. On
4545 reading this entry after an OSPM resume, a "boot" has to be
4646 written to this entry if the card was previously shutdown
4747 during OSPM suspend.
48− "online" - The MIC device has initiated booting a card OS.
48+ "booting" - The MIC device has initiated booting a card OS.
49+ "online" - The MIC device has completed boot and is online
4950 "shutting_down" - The card OS is shutting down.
51+ "resetting" - A reset has been initiated for the MIC device
5052 "reset_failed" - The MIC device has failed to reset.
51− "suspending" - The MIC device is currently being prepared for
52− suspend. On reading this entry, a "suspend" has to be written
53− to the state sysfs entry to ensure the card is shutdown during
54− OSPM suspend.
55− "suspended" - The MIC device has been suspended.
5653
5754 When written, this sysfs entry triggers different state change
5855 operations depending upon the current state of the card OS.
@@ -62,8 +59,6 @@ Description: · 3 unmodified lines
6259 sysfs entries.
6360 "reset" - Initiates device reset.
6461 "shutdown" - Initiates card OS shutdown.
65− "suspend" - Initiates card OS shutdown and also marks the card
66− as suspended.
6762
6863 What: /sys/class/mic/mic(x)/shutdown_status
6964 Date: October 2013
@@ -126,7 +121,7 @@ Description: · 56 unmodified lines
126121 the card. This sysfs entry can be written with the following
127122 valid strings:
128123 a) linux - Boot a Linux image.
129− b) elf - Boot an elf image for flash updates.
124+ b) flash - Boot an image for flash updates.
130125
131126 What: /sys/class/mic/mic(x)/log_buf_addr
132127 Date: October 2013
@@ -155,3 +150,17 @@ Description: · 22 unmodified lines
155150 daemon to set the log buffer length address. The correct log
156151 buffer length address to be written can be found in the
157152 System.map file of the card OS.
153+
154+What: /sys/class/mic/mic(x)/heartbeat_enable
155+Date: March 2015
156+KernelVersion: 3.20
157+Contact: Ashutosh Dixit <ashutosh.dixit@intel.com>
158+Description:
159+ The MIC drivers detect and inform user space about card crashes
160+ via a heartbeat mechanism (see the description of
161+ shutdown_status above). User space can turn off this
162+ notification by setting heartbeat_enable to 0 and enable it by
163+ setting this entry to 1. If this notification is disabled it is
164+ the responsibility of user space to detect card crashes via
165+ alternative means such as a network ping. This setting is
166+ enabled by default.
Documentation/ABI/testing/sysfs-class-power+58−0
@@ -74,3 +74,61 @@ Description: · 73 unmodified lines
7474
7575 Valid values:
7676 - 0 - 70 (minutes), step by 10 (rounded down)
77+
78+What: /sys/class/power_supply/bq24257-charger/ovp_voltage
79+Date: October 2015
80+KernelVersion: 4.4.0
81+Contact: Andreas Dannenberg <dannenberg@ti.com>
82+Description:
83+ This entry configures the overvoltage protection feature of bq24257-
84+ type charger devices. This feature protects the device and other
85+ components against damage from overvoltage on the input supply. See
86+ device datasheet for details.
87+
88+ Valid values:
89+ - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
90+ 10500000 (all uV)
91+
92+What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage
93+Date: October 2015
94+KernelVersion: 4.4.0
95+Contact: Andreas Dannenberg <dannenberg@ti.com>
96+Description:
97+ This entry configures the input dynamic power path management voltage of
98+ bq24257-type charger devices. Once the supply drops to the configured
99+ voltage, the input current limit is reduced down to prevent the further
100+ drop of the supply. When the IC enters this mode, the charge current is
101+ lower than the set value. See device datasheet for details.
102+
103+ Valid values:
104+ - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
105+ 4760000 (all uV)
106+
107+What: /sys/class/power_supply/bq24257-charger/high_impedance_enable
108+Date: October 2015
109+KernelVersion: 4.4.0
110+Contact: Andreas Dannenberg <dannenberg@ti.com>
111+Description:
112+ This entry allows enabling the high-impedance mode of bq24257-type
113+ charger devices. If enabled, it places the charger IC into low power
114+ standby mode with the switch mode controller disabled. When disabled,
115+ the charger operates normally. See device datasheet for details.
116+
117+ Valid values:
118+ - 1: enabled
119+ - 0: disabled
120+
121+What: /sys/class/power_supply/bq24257-charger/sysoff_enable
122+Date: October 2015
123+KernelVersion: 4.4.0
124+Contact: Andreas Dannenberg <dannenberg@ti.com>
125+Description:
126+ This entry allows enabling the sysoff mode of bq24257-type charger
127+ devices. If enabled and the input is removed, the internal battery FET
128+ is turned off in order to reduce the leakage from the BAT pin to less
129+ than 1uA. Note that on some devices/systems this disconnects the battery
130+ from the system. See device datasheet for details.
131+
132+ Valid values:
133+ - 1: enabled
134+ - 0: disabled
Documentation/ABI/testing/sysfs-class-stm+14−0
@@ -0,0 +1,14 @@
1+What: /sys/class/stm/<stm>/masters
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description:
6+ Shows first and last available to software master numbers on
7+ this STM device.
8+
9+What: /sys/class/stm/<stm>/channels
10+Date: June 2015
11+KernelVersion: 4.3
12+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
13+Description:
14+ Shows the number of channels per master on this STM device.
Documentation/ABI/testing/sysfs-class-stm_source+11−0
@@ -0,0 +1,11 @@
1+What: /sys/class/stm_source/<stm_source>/stm_source_link
2+Date: June 2015
3+KernelVersion: 4.3
4+Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
5+Description:
6+ stm_source device linkage to stm device, where its tracing data
7+ is directed. Reads return an existing connection or "<none>" if
8+ this stm_source is not connected to any stm device yet.
9+ Write an existing (registered) stm device's name here to
10+ connect that device. If a device is already connected to this
11+ stm_source, it will first be disconnected.
Documentation/ABI/testing/sysfs-driver-hid-corsair+15−0
@@ -0,0 +1,15 @@
1+What: /sys/bus/drivers/corsair/<dev>/macro_mode
2+Date: August 2015
3+KernelVersion: 4.2
4+Contact: Clement Vuchener <clement.vuchener@gmail.com>
5+Description: Get/set the current playback mode. "SW" for software mode
6+ where G-keys triggers their regular key codes. "HW" for
7+ hardware playback mode where the G-keys play their macro
8+ from the on-board memory.
9+
10+
11+What: /sys/bus/drivers/corsair/<dev>/current_profile
12+Date: August 2015
13+KernelVersion: 4.2
14+Contact: Clement Vuchener <clement.vuchener@gmail.com>
15+Description: Get/set the current selected profile. Values are from 1 to 3.
Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus+0−96
@@ -1,96 +0,0 @@
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>/info
13−Date: November 2012
14−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
15−Description: When read, this file returns general data like firmware version.
16− When written, the device can be reset.
17− The data is 8 bytes long.
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>/koneplus/roccatkoneplus<minor>/macro
21−Date: October 2010
22−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
23−Description: The mouse can store a macro with max 500 key/button strokes
24− internally.
25− When written, this file lets one set the sequence for a specific
26− button for a specific profile. Button and profile numbers are
27− included in written data. The data has to be 2082 bytes long.
28− This file is writeonly.
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>/koneplus/roccatkoneplus<minor>/profile_buttons
32−Date: August 2010
33−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
34−Description: The mouse can store 5 profiles which can be switched by the
35− press of a button. A profile is split in settings and buttons.
36− profile_buttons holds information about button layout.
37− When written, this file lets one write the respective profile
38− buttons back to the mouse. The data has to be 77 bytes long.
39− The mouse will reject invalid data.
40− Which profile to write is determined by the profile number
41− contained in the data.
42− Before reading this file, control has to be written to select
43− which profile to read.
44−Users: http://roccat.sourceforge.net
45−
46−What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_settings
47−Date: October 2010
48−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
49−Description: The mouse can store 5 profiles which can be switched by the
50− press of a button. A profile is split in settings and buttons.
51− profile_settings holds information like resolution, sensitivity
52− and light effects.
53− When written, this file lets one write the respective profile
54− settings back to the mouse. The data has to be 43 bytes long.
55− The mouse will reject invalid data.
56− Which profile to write is determined by the profile number
57− contained in the data.
58− Before reading this file, control has to be written to select
59− which profile to read.
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>/koneplus/roccatkoneplus<minor>/sensor
63−Date: October 2010
64−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
65−Description: The mouse has a tracking- and a distance-control-unit. These
66− can be activated/deactivated and the lift-off distance can be
67− set. The data has to be 6 bytes long.
68− This file is writeonly.
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>/koneplus/roccatkoneplus<minor>/talk
72−Date: May 2011
73−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
74−Description: Used to active some easy* functions of the mouse from outside.
75− The data has to be 16 bytes long.
76− This file is writeonly.
77−Users: http://roccat.sourceforge.net
78−
79−What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu
80−Date: October 2010
81−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
82−Description: When written a calibration process for the tracking control unit
83− can be initiated/cancelled. Also lets one read/write sensor
84− registers.
85− The data has to be 4 bytes long.
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>/koneplus/roccatkoneplus<minor>/tcu_image
89−Date: October 2010
90−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
91−Description: When read the mouse returns a 30x30 pixel image of the
92− sampled underground. This works only in the course of a
93− calibration process initiated with tcu.
94− The returned data is 1028 bytes in size.
95− This file is readonly.
96−Users: http://roccat.sourceforge.net
Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus+0−49
@@ -1,49 +0,0 @@
1−What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_profile
2−Date: January 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 active
6− profile.
7− When written, the mouse activates this profile immediately.
8− The profile that's active when powered down is the same that's
9− active when the mouse is powered on.
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>/kovaplus/roccatkovaplus<minor>/info
13−Date: November 2012
14−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
15−Description: When read, this file returns general data like firmware version.
16− When written, the device can be reset.
17− The data is 6 bytes long.
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>/kovaplus/roccatkovaplus<minor>/profile_buttons
21−Date: January 2011
22−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
23−Description: The mouse can store 5 profiles which can be switched by the
24− press of a button. A profile is split in settings and buttons.
25− profile_buttons holds information about button layout.
26− When written, this file lets one write the respective profile
27− buttons back to the mouse. The data has to be 23 bytes long.
28− The mouse will reject invalid data.
29− Which profile to write is determined by the profile number
30− contained in the data.
31− Before reading this file, control has to be written to select
32− which profile to read.
33−Users: http://roccat.sourceforge.net
34−
35−What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_settings
36−Date: January 2011
37−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
38−Description: The mouse can store 5 profiles which can be switched by the
39− press of a button. A profile is split in settings and buttons.
40− profile_settings holds information like resolution, sensitivity
41− and light effects.
42− When written, this file lets one write the respective profile
43− settings back to the mouse. The data has to be 16 bytes long.
44− The mouse will reject invalid data.
45− Which profile to write is determined by the profile number
46− contained in the data.
47− Before reading this file, control has to be written to select
48− which profile to read.
49−Users: http://roccat.sourceforge.net
Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra+0−49
@@ -1,49 +0,0 @@
1−What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/info
2−Date: November 2012
3−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4−Description: When read, this file returns general data like firmware version.
5− When written, the device can be reset.
6− The data is 6 bytes long.
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>/pyra/roccatpyra<minor>/profile_settings
10−Date: August 2010
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. A profile is split in settings and buttons.
14− profile_settings holds information like resolution, sensitivity
15− and light effects.
16− When written, this file lets one write the respective profile
17− settings back to the mouse. The data has to be 13 bytes long.
18− The mouse will reject invalid data.
19− Which profile to write is determined by the profile number
20− contained in the data.
21− Before reading this file, control has to be written to select
22− which profile to read.
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>/pyra/roccatpyra<minor>/profile_buttons
26−Date: August 2010
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 in settings and buttons.
30− profile_buttons holds information about button layout.
31− When written, this file lets one write the respective profile
32− buttons back to the mouse. The data has to be 19 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− Before reading this file, control has to be written to select
37− which profile to read.
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>/settings
41−Date: August 2010
42−Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
43−Description: When read, this file returns the settings stored in the mouse.
44− The size of the data is 3 bytes and holds information on the
45− startup_profile.
46− When written, this file lets write settings back to the mouse.
47− The data has to be 3 bytes long. The mouse will reject invalid
48− data.
49−Users: http://roccat.sourceforge.net
Documentation/ABI/testing/sysfs-driver-ppi+12−7
@@ -1,4 +1,4 @@
1−What: /sys/devices/pnp0/<bus-num>/ppi/
1+What: /sys/class/tpm/tpmX/ppi/
22 Date: August 2012
33 Kernel Version: 3.6
44 Contact: xiaoyan.zhang@intel.com
@@ -8,9 +8,14 @@ Description: · 3 unmodified lines
88 folder makes sense. The folder path can be got by command
99 'find /sys/ -name 'pcrs''. For the detail information of PPI,
1010 please refer to the PPI specification from
11+
1112 http://www.trustedcomputinggroup.org/
1213
13−What: /sys/devices/pnp0/<bus-num>/ppi/version
14+ In Linux 4.2 ppi was moved to the character device directory.
15+ A symlink from tpmX/device/ppi to tpmX/ppi to provide backwards
16+ compatibility.
17+
18+What: /sys/class/tpm/tpmX/ppi/version
1419 Date: August 2012
1520 Contact: xiaoyan.zhang@intel.com
1621 Description:
@@ -18,7 +23,7 @@ Description: · 1 unmodified line
1823 platform.
1924 This file is readonly.
2025
21−What: /sys/devices/pnp0/<bus-num>/ppi/request
26+What: /sys/class/tpm/tpmX/ppi/request
2227 Date: August 2012
2328 Contact: xiaoyan.zhang@intel.com
2429 Description:
@@ -28,7 +33,7 @@ Description: · 3 unmodified lines
2833 integer value range from 1 to 160, and 0 means no request.
2934 This file can be read and written.
3035
31−What: /sys/devices/pnp0/00:<bus-num>/ppi/response
36+What: /sys/class/tpm/tpmX/ppi/response
3237 Date: August 2012
3338 Contact: xiaoyan.zhang@intel.com
3439 Description:
@@ -37,7 +42,7 @@ Description: · 2 unmodified lines
3742 : <response description>".
3843 This file is readonly.
3944
40−What: /sys/devices/pnp0/<bus-num>/ppi/transition_action
45+What: /sys/class/tpm/tpmX/ppi/transition_action
4146 Date: August 2012
4247 Contact: xiaoyan.zhang@intel.com
4348 Description:
@@ -47,7 +52,7 @@ Description: · 3 unmodified lines
4752 description>".
4853 This file is readonly.
4954
50−What: /sys/devices/pnp0/<bus-num>/ppi/tcg_operations
55+What: /sys/class/tpm/tpmX/ppi/tcg_operations
5156 Date: August 2012
5257 Contact: xiaoyan.zhang@intel.com
5358 Description:
@@ -58,7 +63,7 @@ Description: · 4 unmodified lines
5863 This attribute is only supported by PPI version 1.2+.
5964 This file is readonly.
6065
61−What: /sys/devices/pnp0/<bus-num>/ppi/vs_operations
66+What: /sys/class/tpm/tpmX/ppi/vs_operations
6267 Date: August 2012
6368 Contact: xiaoyan.zhang@intel.com
6469 Description:
Documentation/ABI/testing/sysfs-driver-st+12−0
@@ -0,0 +1,12 @@
1+What: /sys/bus/scsi/drivers/st/debug_flag
2+Date: October 2015
3+Kernel Version: ?.?
4+Contact: shane.seymour@hpe.com
5+Description:
6+ This file allows you to turn debug output from the st driver
7+ off if you write a '0' to the file or on if you write a '1'.
8+ Note that debug output requires that the module be compiled
9+ with the #define DEBUG set to a non-zero value (this is the
10+ default). If DEBUG is set to 0 then this file will not
11+ appear in sysfs as its presence is conditional upon debug
12+ output support being compiled into the module.
Documentation/ABI/testing/sysfs-fs-f2fs+12−0
@@ -80,3 +80,15 @@ Date: February 2015 · 79 unmodified lines
8080 Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
8181 Description:
8282 Controls the trimming rate in batch mode.
83+
84+What: /sys/fs/f2fs/<disk>/cp_interval
85+Date: October 2015
86+Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
87+Description:
88+ Controls the checkpoint timing.
89+
90+What: /sys/fs/f2fs/<disk>/ra_nid_pages
91+Date: October 2015
92+Contact: "Chao Yu" <chao2.yu@samsung.com>
93+Description:
94+ Controls the count of nid pages to be readaheaded.
Documentation/ABI/testing/sysfs-power+12−0
@@ -256,3 +256,15 @@ Description: · 255 unmodified lines
256256 Writing a "1" enables this printing while writing a "0"
257257 disables it. The default value is "0". Reading from this file
258258 will display the current value.
259+
260+What: /sys/power/pm_wakeup_irq
261+Date: April 2015
262+Contact: Alexandra Yates <alexandra.yates@linux.intel.org>
263+Description:
264+ The /sys/power/pm_wakeup_irq file reports to user space the IRQ
265+ number of the first wakeup interrupt (that is, the first
266+ interrupt from an IRQ line armed for system wakeup) seen by the
267+ kernel during the most recent system suspend/resume cycle.
268+
269+ This output is useful for system wakeup diagnostics of spurious
270+ wakeup interrupts.
Documentation/Changes+2−1
@@ -43,7 +43,8 @@ o udev 081 # udevd --version · 42 unmodified lines
4343 o grub 0.93 # grub --version || grub-install --version
4444 o mcelog 0.6 # mcelog --version
4545 o iptables 1.4.2 # iptables -V
46−o openssl & libcrypto 1.0.1k # openssl version
46+o openssl & libcrypto 1.0.0 # openssl version
47+o bc 1.06.95 # bc --version
4748
4849
4950 Kernel compilation
Documentation/DMA-API-HOWTO.txt+5−0
@@ -681,6 +681,11 @@ or: · 680 unmodified lines
681681
682682 as appropriate.
683683
684+PLEASE NOTE: The 'nents' argument to dma_sync_sg_for_cpu() and
685+ dma_sync_sg_for_device() must be the same passed to
686+ dma_map_sg(). It is _NOT_ the count returned by
687+ dma_map_sg().
688+
684689 After the last DMA transfer call one of the DMA unmap routines
685690 dma_unmap_{single,sg}(). If you don't touch the data from the first
686691 dma_map_*() call till dma_unmap_*(), then you don't have to call the
Documentation/DMA-API.txt+3−16
@@ -141,19 +141,6 @@ memory back to the pool before you destroy it. · 140 unmodified lines
141141 Part Ic - DMA addressing limitations
142142 ------------------------------------
143143
144−int
145−dma_supported(struct device *dev, u64 mask)
146−
147−Checks to see if the device can support DMA to the memory described by
148−mask.
149−
150−Returns: 1 if it can and 0 if it can't.
151−
152−Notes: This routine merely tests to see if the mask is possible. It
153−won't change the current mask settings. It is more intended as an
154−internal API for use by the platform than an external API for use by
155−driver writers.
156−
157144 int
158145 dma_set_mask_and_coherent(struct device *dev, u64 mask)
159146
@@ -340,7 +327,7 @@ accessed sg->address and sg->length as shown above. · 180 unmodified lines
340327
341328 void
342329 dma_unmap_sg(struct device *dev, struct scatterlist *sg,
343− int nhwentries, enum dma_data_direction direction)
330+ int nents, enum dma_data_direction direction)
344331
345332 Unmap the previously mapped scatter/gather list. All the parameters
346333 must be the same as those and passed in to the scatter/gather mapping
@@ -356,10 +343,10 @@ void · 9 unmodified lines
356343 dma_sync_single_for_device(struct device *dev, dma_addr_t dma_handle, size_t size,
357344 enum dma_data_direction direction)
358345 void
359−dma_sync_sg_for_cpu(struct device *dev, struct scatterlist *sg, int nelems,
346+dma_sync_sg_for_cpu(struct device *dev, struct scatterlist *sg, int nents,
360347 enum dma_data_direction direction)
361348 void
362−dma_sync_sg_for_device(struct device *dev, struct scatterlist *sg, int nelems,
349+dma_sync_sg_for_device(struct device *dev, struct scatterlist *sg, int nents,
363350 enum dma_data_direction direction)
364351
365352 Synchronise a single contiguous or scatter/gather mapping for the CPU
Documentation/DocBook/.gitignore+2−0
@@ -11,5 +11,7 @@ · 10 unmodified lines
1111 *.png
1212 *.gif
1313 *.svg
14+*.proc
15+*.db
1416 media-indices.tmpl
1517 media-entities.tmpl
Documentation/DocBook/80211.tmpl+3−2
@@ -154,8 +154,9 @@ · 153 unmodified lines
154154 !Finclude/net/cfg80211.h cfg80211_scan_request
155155 !Finclude/net/cfg80211.h cfg80211_scan_done
156156 !Finclude/net/cfg80211.h cfg80211_bss
157−!Finclude/net/cfg80211.h cfg80211_inform_bss_width_frame
158−!Finclude/net/cfg80211.h cfg80211_inform_bss_width
157+!Finclude/net/cfg80211.h cfg80211_inform_bss
158+!Finclude/net/cfg80211.h cfg80211_inform_bss_frame_data
159+!Finclude/net/cfg80211.h cfg80211_inform_bss_data
159160 !Finclude/net/cfg80211.h cfg80211_unlink_bss
160161 !Finclude/net/cfg80211.h cfg80211_find_ie
161162 !Finclude/net/cfg80211.h ieee80211_bss_get_ie
Documentation/DocBook/Makefile+7−1
@@ -14,7 +14,7 @@ DOCBOOKS := z8530book.xml device-drivers.xml \ · 13 unmodified lines
1414 genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
1515 80211.xml debugobjects.xml sh.xml regulator.xml \
1616 alsa-driver-api.xml writing-an-alsa-driver.xml \
17− tracepoint.xml drm.xml media_api.xml w1.xml \
17+ tracepoint.xml gpu.xml media_api.xml w1.xml \
1818 writing_musb_glue_layer.xml crypto-API.xml iio.xml
1919
2020 include Documentation/DocBook/media/Makefile
@@ -69,6 +69,12 @@ installmandocs: mandocs · 48 unmodified lines
6969 KERNELDOCXMLREF = $(srctree)/scripts/kernel-doc-xml-ref
7070 KERNELDOC = $(srctree)/scripts/kernel-doc
7171 DOCPROC = $(objtree)/scripts/docproc
72+CHECK_LC_CTYPE = $(objtree)/scripts/check-lc_ctype
73+
74+# Use a fixed encoding - UTF-8 if the C library has support built-in
75+# or ASCII if not
76+LC_CTYPE := $(call try-run, LC_CTYPE=C.UTF-8 $(CHECK_LC_CTYPE),C.UTF-8,C)
77+export LC_CTYPE
7278
7379 XMLTOFLAGS = -m $(srctree)/$(src)/stylesheet.xsl
7480 XMLTOFLAGS += --skip-validation
Documentation/DocBook/alsa-driver-api.tmpl+2−0
@@ -112,6 +112,8 @@ · 111 unmodified lines
112112 !Esound/soc/soc-devres.c
113113 !Esound/soc/soc-io.c
114114 !Esound/soc/soc-pcm.c
115+!Esound/soc/soc-ops.c
116+!Esound/soc/soc-compress.c
115117 </sect1>
116118 <sect1><title>ASoC DAPM API</title>
117119 !Esound/soc/soc-dapm.c
Documentation/DocBook/device-drivers.tmpl+76−5
@@ -221,6 +221,9 @@ X!Isound/sound_firmware.c · 220 unmodified lines
221221 <title>Media Devices</title>
222222
223223 <sect1><title>Video2Linux devices</title>
224+!Iinclude/media/tuner.h
225+!Iinclude/media/tuner-types.h
226+!Iinclude/media/tveeprom.h
224227 !Iinclude/media/v4l2-async.h
225228 !Iinclude/media/v4l2-ctrls.h
226229 !Iinclude/media/v4l2-dv-timings.h
@@ -231,6 +234,7 @@ X!Isound/sound_firmware.c · 4 unmodified lines
231234 !Iinclude/media/v4l2-of.h
232235 !Iinclude/media/v4l2-subdev.h
233236 !Iinclude/media/videobuf2-core.h
237+!Iinclude/media/videobuf2-v4l2.h
234238 !Iinclude/media/videobuf2-memops.h
235239 </sect1>
236240 <sect1><title>Digital TV (DVB) devices</title>
@@ -239,15 +243,82 @@ X!Isound/sound_firmware.c · 2 unmodified lines
239243 !Idrivers/media/dvb-core/dvb_math.h
240244 !Idrivers/media/dvb-core/dvb_ringbuffer.h
241245 !Idrivers/media/dvb-core/dvbdev.h
242− </sect1>
243− <sect1><title>Remote Controller devices</title>
246+ <sect1><title>Digital TV Demux API</title>
247+ <para>The kernel demux API defines a driver-internal interface for
248+ registering low-level, hardware specific driver to a hardware
249+ independent demux layer. It is only of interest for Digital TV
250+ device driver writers. The header file for this API is named
251+ <constant>demux.h</constant> and located in
252+ <constant>drivers/media/dvb-core</constant>.</para>
253+
254+ <para>The demux API should be implemented for each demux in the
255+ system. It is used to select the TS source of a demux and to manage
256+ the demux resources. When the demux client allocates a resource via
257+ the demux API, it receives a pointer to the API of that
258+ resource.</para>
259+ <para>Each demux receives its TS input from a DVB front-end or from
260+ memory, as set via this demux API. In a system with more than one
261+ front-end, the API can be used to select one of the DVB front-ends
262+ as a TS source for a demux, unless this is fixed in the HW platform.
263+ The demux API only controls front-ends regarding to their connections
264+ with demuxes; the APIs used to set the other front-end parameters,
265+ such as tuning, are not defined in this document.</para>
266+ <para>The functions that implement the abstract interface demux should
267+ be defined static or module private and registered to the Demux
268+ core for external access. It is not necessary to implement every
269+ function in the struct <constant>dmx_demux</constant>. For example,
270+ a demux interface might support Section filtering, but not PES
271+ filtering. The API client is expected to check the value of any
272+ function pointer before calling the function: the value of NULL means
273+ that the &#8220;function is not available&#8221;.</para>
274+ <para>Whenever the functions of the demux API modify shared data,
275+ the possibilities of lost update and race condition problems should
276+ be addressed, e.g. by protecting parts of code with mutexes.</para>
277+ <para>Note that functions called from a bottom half context must not
278+ sleep. Even a simple memory allocation without using GFP_ATOMIC can
279+ result in a kernel thread being put to sleep if swapping is needed.
280+ For example, the Linux kernel calls the functions of a network device
281+ interface from a bottom half context. Thus, if a demux API function
282+ is called from network device code, the function must not sleep.
283+ </para>
284+ </sect1>
285+
286+ <section id="demux_callback_api">
287+ <title>Demux Callback API</title>
288+ <para>This kernel-space API comprises the callback functions that
289+ deliver filtered data to the demux client. Unlike the other DVB
290+ kABIs, these functions are provided by the client and called from
291+ the demux code.</para>
292+ <para>The function pointers of this abstract interface are not
293+ packed into a structure as in the other demux APIs, because the
294+ callback functions are registered and used independent of each
295+ other. As an example, it is possible for the API client to provide
296+ several callback functions for receiving TS packets and no
297+ callbacks for PES packets or sections.</para>
298+ <para>The functions that implement the callback API need not be
299+ re-entrant: when a demux driver calls one of these functions,
300+ the driver is not allowed to call the function again before
301+ the original call returns. If a callback is triggered by a
302+ hardware interrupt, it is recommended to use the Linux
303+ &#8220;bottom half&#8221; mechanism or start a tasklet instead of
304+ making the callback function call directly from a hardware
305+ interrupt.</para>
306+ <para>This mechanism is implemented by
307+ <link linkend='API-dmx-ts-cb'>dmx_ts_cb()</link> and
308+ <link linkend='API-dmx-section-cb'>dmx_section_cb()</link>.</para>
309+ </section>
310+
311+!Idrivers/media/dvb-core/demux.h
312+ </sect1>
313+ <sect1><title>Remote Controller devices</title>
244314 !Iinclude/media/rc-core.h
245− </sect1>
246− <sect1><title>Media Controller devices</title>
315+!Iinclude/media/lirc_dev.h
316+ </sect1>
317+ <sect1><title>Media Controller devices</title>
247318 !Iinclude/media/media-device.h
248319 !Iinclude/media/media-devnode.h
249320 !Iinclude/media/media-entity.h
250− </sect1>
321+ </sect1>
251322
252323 </chapter>
253324
Documentation/DocBook/gpu.tmplrenamed from Documentation/DocBook/drm.tmpl+101−93
@@ -2,9 +2,9 @@ · 1 unmodified line
22 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
33 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
44
5−<book id="drmDevelopersGuide">
5+<book id="gpuDevelopersGuide">
66 <bookinfo>
7− <title>Linux DRM Developer's Guide</title>
7+ <title>Linux GPU Driver Developer's Guide</title>
88
99 <authorgroup>
1010 <author>
@@ -40,6 +40,16 @@ · 29 unmodified lines
4040 </address>
4141 </affiliation>
4242 </author>
43+ <author>
44+ <firstname>Lukas</firstname>
45+ <surname>Wunner</surname>
46+ <contrib>vga_switcheroo documentation</contrib>
47+ <affiliation>
48+ <address>
49+ <email>lukas@wunner.de</email>
50+ </address>
51+ </affiliation>
52+ </author>
4353 </authorgroup>
4454
4555 <copyright>
@@ -51,6 +61,10 @@ · 5 unmodified lines
5161 <year>2012</year>
5262 <holder>Laurent Pinchart</holder>
5363 </copyright>
64+ <copyright>
65+ <year>2015</year>
66+ <holder>Lukas Wunner</holder>
67+ </copyright>
5468
5569 <legalnotice>
5670 <para>
@@ -69,6 +83,13 @@ · 12 unmodified lines
6983 <revremark>Added extensive documentation about driver internals.
7084 </revremark>
7185 </revision>
86+ <revision>
87+ <revnumber>1.1</revnumber>
88+ <date>2015-10-11</date>
89+ <authorinitials>LW</authorinitials>
90+ <revremark>Added vga_switcheroo documentation.
91+ </revremark>
92+ </revision>
7293 </revhistory>
7394 </bookinfo>
7495
@@ -78,9 +99,9 @@ · 3 unmodified lines
7899 <title>DRM Core</title>
79100 <partintro>
80101 <para>
81− This first part of the DRM Developer's Guide documents core DRM code,
82− helper libraries for writing drivers and generic userspace interfaces
83− exposed by DRM drivers.
102+ This first part of the GPU Driver Developer's Guide documents core DRM
103+ code, helper libraries for writing drivers and generic userspace
104+ interfaces exposed by DRM drivers.
84105 </para>
85106 </partintro>
86107
@@ -138,14 +159,10 @@ · 51 unmodified lines
138159 <para>
139160 At the core of every DRM driver is a <structname>drm_driver</structname>
140161 structure. Drivers typically statically initialize a drm_driver structure,
141− and then pass it to one of the <function>drm_*_init()</function> functions
142− to register it with the DRM subsystem.
143− </para>
144− <para>
145− Newer drivers that no longer require a <structname>drm_bus</structname>
146− structure can alternatively use the low-level device initialization and
147− registration functions such as <function>drm_dev_alloc()</function> and
148− <function>drm_dev_register()</function> directly.
162+ and then pass it to <function>drm_dev_alloc()</function> to allocate a
163+ device instance. After the device instance is fully initialized it can be
164+ registered (which makes it accessible from userspace) using
165+ <function>drm_dev_register()</function>.
149166 </para>
150167 <para>
151168 The <structname>drm_driver</structname> structure contains static
@@ -296,83 +313,12 @@ char *date;</synopsis> · 144 unmodified lines
296313 </sect3>
297314 </sect2>
298315 <sect2>
299− <title>Device Registration</title>
300− <para>
301− A number of functions are provided to help with device registration.
302− The functions deal with PCI and platform devices, respectively.
303− </para>
304−!Edrivers/gpu/drm/drm_pci.c
305−!Edrivers/gpu/drm/drm_platform.c
306− <para>
307− New drivers that no longer rely on the services provided by the
308− <structname>drm_bus</structname> structure can call the low-level
309− device registration functions directly. The
310− <function>drm_dev_alloc()</function> function can be used to allocate
311− and initialize a new <structname>drm_device</structname> structure.
312− Drivers will typically want to perform some additional setup on this
313− structure, such as allocating driver-specific data and storing a
314− pointer to it in the DRM device's <structfield>dev_private</structfield>
315− field. Drivers should also set the device's unique name using the
316− <function>drm_dev_set_unique()</function> function. After it has been
317− set up a device can be registered with the DRM subsystem by calling
318− <function>drm_dev_register()</function>. This will cause the device to
319− be exposed to userspace and will call the driver's
320− <structfield>.load()</structfield> implementation. When a device is
321− removed, the DRM device can safely be unregistered and freed by calling
322− <function>drm_dev_unregister()</function> followed by a call to
323− <function>drm_dev_unref()</function>.
324− </para>
316+ <title>Device Instance and Driver Handling</title>
317+!Pdrivers/gpu/drm/drm_drv.c driver instance overview
325318 !Edrivers/gpu/drm/drm_drv.c
326319 </sect2>
327320 <sect2>
328321 <title>Driver Load</title>
329− <para>
330− The <methodname>load</methodname> method is the driver and device
331− initialization entry point. The method is responsible for allocating and
332− initializing driver private data, performing resource allocation and
333− mapping (e.g. acquiring
334− clocks, mapping registers or allocating command buffers), initializing
335− the memory manager (<xref linkend="drm-memory-management"/>), installing
336− the IRQ handler (<xref linkend="drm-irq-registration"/>), setting up
337− vertical blanking handling (<xref linkend="drm-vertical-blank"/>), mode
338− setting (<xref linkend="drm-mode-setting"/>) and initial output
339− configuration (<xref linkend="drm-kms-init"/>).
340− </para>
341− <note><para>
342− If compatibility is a concern (e.g. with drivers converted over from
343− User Mode Setting to Kernel Mode Setting), care must be taken to prevent
344− device initialization and control that is incompatible with currently
345− active userspace drivers. For instance, if user level mode setting
346− drivers are in use, it would be problematic to perform output discovery
347− &amp; configuration at load time. Likewise, if user-level drivers
348− unaware of memory management are in use, memory management and command
349− buffer setup may need to be omitted. These requirements are
350− driver-specific, and care needs to be taken to keep both old and new
351− applications and libraries working.
352− </para></note>
353− <synopsis>int (*load) (struct drm_device *, unsigned long flags);</synopsis>
354− <para>
355− The method takes two arguments, a pointer to the newly created
356− <structname>drm_device</structname> and flags. The flags are used to
357− pass the <structfield>driver_data</structfield> field of the device id
358− corresponding to the device passed to <function>drm_*_init()</function>.
359− Only PCI devices currently use this, USB and platform DRM drivers have
360− their <methodname>load</methodname> method called with flags to 0.
361− </para>
362− <sect3>
363− <title>Driver Private Data</title>
364− <para>
365− The driver private hangs off the main
366− <structname>drm_device</structname> structure and can be used for
367− tracking various device-specific bits of information, like register
368− offsets, command buffer status, register state for suspend/resume, etc.
369− At load time, a driver may simply allocate one and set
370− <structname>drm_device</structname>.<structfield>dev_priv</structfield>
371− appropriately; it should be freed and
372− <structname>drm_device</structname>.<structfield>dev_priv</structfield>
373− set to NULL when the driver is unloaded.
374− </para>
375− </sect3>
376322 <sect3 id="drm-irq-registration">
377323 <title>IRQ Registration</title>
378324 <para>
@@ -465,6 +411,18 @@ char *date;</synopsis> · 86 unmodified lines
465411 </para>
466412 </sect3>
467413 </sect2>
414+ <sect2>
415+ <title>Bus-specific Device Registration and PCI Support</title>
416+ <para>
417+ A number of functions are provided to help with device registration.
418+ The functions deal with PCI and platform devices respectively and are
419+ only provided for historical reasons. These are all deprecated and
420+ shouldn't be used in new drivers. Besides that there's a few
421+ helpers for pci drivers.
422+ </para>
423+!Edrivers/gpu/drm/drm_pci.c
424+!Edrivers/gpu/drm/drm_platform.c
425+ </sect2>
468426 </sect1>
469427
470428 <!-- Internals: memory management -->
@@ -3646,10 +3604,11 @@ void (*postclose) (struct drm_device *, struct drm_file *);</synopsis> · 3175 unmodified lines
36463604 plane properties to default value, so that a subsequent open of the
36473605 device will not inherit state from the previous user. It can also be
36483606 used to execute delayed power switching state changes, e.g. in
3649− conjunction with the vga_switcheroo infrastructure. Beyond that KMS
3650− drivers should not do any further cleanup. Only legacy UMS drivers might
3651− need to clean up device state so that the vga console or an independent
3652− fbdev driver could take over.
3607+ conjunction with the vga_switcheroo infrastructure (see
3608+ <xref linkend="vga_switcheroo"/>). Beyond that KMS drivers should not
3609+ do any further cleanup. Only legacy UMS drivers might need to clean up
3610+ device state so that the vga console or an independent fbdev driver
3611+ could take over.
36533612 </para>
36543613 </sect2>
36553614 <sect2>
@@ -3747,11 +3706,14 @@ int num_ioctls;</synopsis> · 91 unmodified lines
37473706 </para></listitem>
37483707 <listitem><para>
37493708 DRM_UNLOCKED - The ioctl handler will be called without locking
3750− the DRM global mutex
3709+ the DRM global mutex. This is the enforced default for kms drivers
3710+ (i.e. using the DRIVER_MODESET flag) and hence shouldn't be used
3711+ any more for new drivers.
37513712 </para></listitem>
37523713 </itemizedlist>
37533714 </para>
37543715 </para>
3716+!Edrivers/gpu/drm/drm_ioctl.c
37553717 </sect2>
37563718 </sect1>
37573719 <sect1>
@@ -3949,8 +3911,8 @@ int num_ioctls;</synopsis> · 191 unmodified lines
39493911
39503912 <partintro>
39513913 <para>
3952− This second part of the DRM Developer's Guide documents driver code,
3953− implementation details and also all the driver-specific userspace
3914+ This second part of the GPU Driver Developer's Guide documents driver
3915+ code, implementation details and also all the driver-specific userspace
39543916 interfaces. Especially since all hardware-acceleration interfaces to
39553917 userspace are driver specific for efficiency and other reasons these
39563918 interfaces can be rather substantial. Hence every driver has its own
@@ -4279,4 +4241,50 @@ int num_ioctls;</synopsis> · 322 unmodified lines
42794241 </chapter>
42804242 !Cdrivers/gpu/drm/i915/i915_irq.c
42814243 </part>
4244+
4245+<part id="vga_switcheroo">
4246+ <title>vga_switcheroo</title>
4247+ <partintro>
4248+!Pdrivers/gpu/vga/vga_switcheroo.c Overview
4249+ </partintro>
4250+
4251+ <chapter id="modes_of_use">
4252+ <title>Modes of Use</title>
4253+ <sect1>
4254+ <title>Manual switching and manual power control</title>
4255+!Pdrivers/gpu/vga/vga_switcheroo.c Manual switching and manual power control
4256+ </sect1>
4257+ <sect1>
4258+ <title>Driver power control</title>
4259+!Pdrivers/gpu/vga/vga_switcheroo.c Driver power control
4260+ </sect1>
4261+ </chapter>
4262+
4263+ <chapter id="pubfunctions">
4264+ <title>Public functions</title>
4265+!Edrivers/gpu/vga/vga_switcheroo.c
4266+ </chapter>
4267+
4268+ <chapter id="pubstructures">
4269+ <title>Public structures</title>
4270+!Finclude/linux/vga_switcheroo.h vga_switcheroo_handler
4271+!Finclude/linux/vga_switcheroo.h vga_switcheroo_client_ops
4272+ </chapter>
4273+
4274+ <chapter id="pubconstants">
4275+ <title>Public constants</title>
4276+!Finclude/linux/vga_switcheroo.h vga_switcheroo_client_id
4277+!Finclude/linux/vga_switcheroo.h vga_switcheroo_state
4278+ </chapter>
4279+
4280+ <chapter id="privstructures">
4281+ <title>Private structures</title>
4282+!Fdrivers/gpu/vga/vga_switcheroo.c vgasr_priv
4283+!Fdrivers/gpu/vga/vga_switcheroo.c vga_switcheroo_client
4284+ </chapter>
4285+
4286+!Cdrivers/gpu/vga/vga_switcheroo.c
4287+!Cinclude/linux/vga_switcheroo.h
4288+</part>
4289+
42824290 </book>
Documentation/DocBook/iio.tmpl+1−1
@@ -578,7 +578,7 @@ · 577 unmodified lines
578578 work together.
579579 </para>
580580 <sect2 id="iiotrigbufsetup"> <title> IIO triggered buffer setup</title>
581−!Edrivers/iio/industrialio-triggered-buffer.c
581+!Edrivers/iio/buffer/industrialio-triggered-buffer.c
582582 !Finclude/linux/iio/iio.h iio_buffer_setup_ops
583583
584584
Documentation/DocBook/media/dvb/dvbapi.xml+0−3
@@ -125,9 +125,6 @@ Added ISDB-T test originally written by Patrick Boettcher · 124 unmodified lines
125125 &sub-audio;
126126 </section>
127127 </chapter>
128− <chapter id="dvb_kdapi">
129− &sub-kdapi;
130− </chapter>
131128 <chapter id="dvb_examples">
132129 &sub-examples;
133130 </chapter>
Documentation/DocBook/media/dvb/kdapi.xml+0−2309
@@ -1,2309 +0,0 @@
1−<title>Kernel Demux API</title>
2−<para>The kernel demux API defines a driver-internal interface for registering low-level,
3−hardware specific driver to a hardware independent demux layer. It is only of interest for
4−DVB device driver writers. The header file for this API is named <constant>demux.h</constant> and located in
5−<constant>">drivers/media/dvb-core</constant>.
6−</para>
7−<para>Maintainer note: This section must be reviewed. It is probably out of date.
8−</para>
9−
10−<section id="kernel_demux_data_types">
11−<title>Kernel Demux Data Types</title>
12−
13−
14−<section id="dmx_success_t">
15−<title>dmx_success_t</title>
16− <programlisting>
17− typedef enum {
18− DMX_OK = 0, /&#x22C6; Received Ok &#x22C6;/
19− DMX_LENGTH_ERROR, /&#x22C6; Incorrect length &#x22C6;/
20− DMX_OVERRUN_ERROR, /&#x22C6; Receiver ring buffer overrun &#x22C6;/
21− DMX_CRC_ERROR, /&#x22C6; Incorrect CRC &#x22C6;/
22− DMX_FRAME_ERROR, /&#x22C6; Frame alignment error &#x22C6;/
23− DMX_FIFO_ERROR, /&#x22C6; Receiver FIFO overrun &#x22C6;/
24− DMX_MISSED_ERROR /&#x22C6; Receiver missed packet &#x22C6;/
25− } dmx_success_t;
26−</programlisting>
27−
28−</section>
29−<section id="ts_filter_types">
30−<title>TS filter types</title>
31− <programlisting>
32− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
33− /&#x22C6; TS packet reception &#x22C6;/
34− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
35−
36− /&#x22C6; TS filter type for set_type() &#x22C6;/
37−
38− #define TS_PACKET 1 /&#x22C6; send TS packets (188 bytes) to callback (default) &#x22C6;/
39− #define TS_PAYLOAD_ONLY 2 /&#x22C6; in case TS_PACKET is set, only send the TS
40− payload (&#x003C;=184 bytes per packet) to callback &#x22C6;/
41− #define TS_DECODER 4 /&#x22C6; send stream to built-in decoder (if present) &#x22C6;/
42−</programlisting>
43−
44−</section>
45−<section id="dmx_ts_pes_t">
46−<title>dmx_ts_pes_t</title>
47−<para>The structure
48−</para>
49−<programlisting>
50− typedef enum
51− {
52− DMX_TS_PES_AUDIO, /&#x22C6; also send packets to audio decoder (if it exists) &#x22C6;/
53− DMX_TS_PES_VIDEO, /&#x22C6; ... &#x22C6;/
54− DMX_TS_PES_TELETEXT,
55− DMX_TS_PES_SUBTITLE,
56− DMX_TS_PES_PCR,
57− DMX_TS_PES_OTHER,
58− } dmx_ts_pes_t;
59−</programlisting>
60−<para>describes the PES type for filters which write to a built-in decoder. The correspond (and
61−should be kept identical) to the types in the demux device.
62−</para>
63−<programlisting>
64− struct dmx_ts_feed_s {
65− int is_filtering; /&#x22C6; Set to non-zero when filtering in progress &#x22C6;/
66− struct dmx_demux_s&#x22C6; parent; /&#x22C6; Back-pointer &#x22C6;/
67− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
68− int (&#x22C6;set) (struct dmx_ts_feed_s&#x22C6; feed,
69− __u16 pid,
70− size_t callback_length,
71− size_t circular_buffer_size,
72− int descramble,
73− struct timespec timeout);
74− int (&#x22C6;start_filtering) (struct dmx_ts_feed_s&#x22C6; feed);
75− int (&#x22C6;stop_filtering) (struct dmx_ts_feed_s&#x22C6; feed);
76− int (&#x22C6;set_type) (struct dmx_ts_feed_s&#x22C6; feed,
77− int type,
78− dmx_ts_pes_t pes_type);
79− };
80−
81− typedef struct dmx_ts_feed_s dmx_ts_feed_t;
82−</programlisting>
83− <programlisting>
84− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
85− /&#x22C6; PES packet reception (not supported yet) &#x22C6;/
86− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
87−
88− typedef struct dmx_pes_filter_s {
89− struct dmx_pes_s&#x22C6; parent; /&#x22C6; Back-pointer &#x22C6;/
90− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
91− } dmx_pes_filter_t;
92−</programlisting>
93− <programlisting>
94− typedef struct dmx_pes_feed_s {
95− int is_filtering; /&#x22C6; Set to non-zero when filtering in progress &#x22C6;/
96− struct dmx_demux_s&#x22C6; parent; /&#x22C6; Back-pointer &#x22C6;/
97− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
98− int (&#x22C6;set) (struct dmx_pes_feed_s&#x22C6; feed,
99− __u16 pid,
100− size_t circular_buffer_size,
101− int descramble,
102− struct timespec timeout);
103− int (&#x22C6;start_filtering) (struct dmx_pes_feed_s&#x22C6; feed);
104− int (&#x22C6;stop_filtering) (struct dmx_pes_feed_s&#x22C6; feed);
105− int (&#x22C6;allocate_filter) (struct dmx_pes_feed_s&#x22C6; feed,
106− dmx_pes_filter_t&#x22C6;&#x22C6; filter);
107− int (&#x22C6;release_filter) (struct dmx_pes_feed_s&#x22C6; feed,
108− dmx_pes_filter_t&#x22C6; filter);
109− } dmx_pes_feed_t;
110−</programlisting>
111− <programlisting>
112− typedef struct {
113− __u8 filter_value [DMX_MAX_FILTER_SIZE];
114− __u8 filter_mask [DMX_MAX_FILTER_SIZE];
115− struct dmx_section_feed_s&#x22C6; parent; /&#x22C6; Back-pointer &#x22C6;/
116− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
117− } dmx_section_filter_t;
118−</programlisting>
119− <programlisting>
120− struct dmx_section_feed_s {
121− int is_filtering; /&#x22C6; Set to non-zero when filtering in progress &#x22C6;/
122− struct dmx_demux_s&#x22C6; parent; /&#x22C6; Back-pointer &#x22C6;/
123− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
124− int (&#x22C6;set) (struct dmx_section_feed_s&#x22C6; feed,
125− __u16 pid,
126− size_t circular_buffer_size,
127− int descramble,
128− int check_crc);
129− int (&#x22C6;allocate_filter) (struct dmx_section_feed_s&#x22C6; feed,
130− dmx_section_filter_t&#x22C6;&#x22C6; filter);
131− int (&#x22C6;release_filter) (struct dmx_section_feed_s&#x22C6; feed,
132− dmx_section_filter_t&#x22C6; filter);
133− int (&#x22C6;start_filtering) (struct dmx_section_feed_s&#x22C6; feed);
134− int (&#x22C6;stop_filtering) (struct dmx_section_feed_s&#x22C6; feed);
135− };
136− typedef struct dmx_section_feed_s dmx_section_feed_t;
137−
138− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
139− /&#x22C6; Callback functions &#x22C6;/
140− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
141−
142− typedef int (&#x22C6;dmx_ts_cb) ( __u8 &#x22C6; buffer1,
143− size_t buffer1_length,
144− __u8 &#x22C6; buffer2,
145− size_t buffer2_length,
146− dmx_ts_feed_t&#x22C6; source,
147− dmx_success_t success);
148−
149− typedef int (&#x22C6;dmx_section_cb) ( __u8 &#x22C6; buffer1,
150− size_t buffer1_len,
151− __u8 &#x22C6; buffer2,
152− size_t buffer2_len,
153− dmx_section_filter_t &#x22C6; source,
154− dmx_success_t success);
155−
156− typedef int (&#x22C6;dmx_pes_cb) ( __u8 &#x22C6; buffer1,
157− size_t buffer1_len,
158− __u8 &#x22C6; buffer2,
159− size_t buffer2_len,
160− dmx_pes_filter_t&#x22C6; source,
161− dmx_success_t success);
162−
163− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
164− /&#x22C6; DVB Front-End &#x22C6;/
165− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
166−
167− typedef enum {
168− DMX_OTHER_FE = 0,
169− DMX_SATELLITE_FE,
170− DMX_CABLE_FE,
171− DMX_TERRESTRIAL_FE,
172− DMX_LVDS_FE,
173− DMX_ASI_FE, /&#x22C6; DVB-ASI interface &#x22C6;/
174− DMX_MEMORY_FE
175− } dmx_frontend_source_t;
176−
177− typedef struct {
178− /&#x22C6; The following char&#x22C6; fields point to NULL terminated strings &#x22C6;/
179− char&#x22C6; id; /&#x22C6; Unique front-end identifier &#x22C6;/
180− char&#x22C6; vendor; /&#x22C6; Name of the front-end vendor &#x22C6;/
181− char&#x22C6; model; /&#x22C6; Name of the front-end model &#x22C6;/
182− struct list_head connectivity_list; /&#x22C6; List of front-ends that can
183− be connected to a particular
184− demux &#x22C6;/
185− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
186− dmx_frontend_source_t source;
187− } dmx_frontend_t;
188−
189− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
190− /&#x22C6; MPEG-2 TS Demux &#x22C6;/
191− /&#x22C6;--------------------------------------------------------------------------&#x22C6;/
192−
193− /&#x22C6;
194− &#x22C6; Flags OR'ed in the capabilites field of struct dmx_demux_s.
195− &#x22C6;/
196−
197− #define DMX_TS_FILTERING 1
198− #define DMX_PES_FILTERING 2
199− #define DMX_SECTION_FILTERING 4
200− #define DMX_MEMORY_BASED_FILTERING 8 /&#x22C6; write() available &#x22C6;/
201− #define DMX_CRC_CHECKING 16
202− #define DMX_TS_DESCRAMBLING 32
203− #define DMX_SECTION_PAYLOAD_DESCRAMBLING 64
204− #define DMX_MAC_ADDRESS_DESCRAMBLING 128
205−</programlisting>
206−
207−</section>
208−<section id="demux_demux_t">
209−<title>demux_demux_t</title>
210− <programlisting>
211− /&#x22C6;
212− &#x22C6; DMX_FE_ENTRY(): Casts elements in the list of registered
213− &#x22C6; front-ends from the generic type struct list_head
214− &#x22C6; to the type &#x22C6; dmx_frontend_t
215− &#x22C6;.
216− &#x22C6;/
217−
218− #define DMX_FE_ENTRY(list) list_entry(list, dmx_frontend_t, connectivity_list)
219−
220− struct dmx_demux_s {
221− /&#x22C6; The following char&#x22C6; fields point to NULL terminated strings &#x22C6;/
222− char&#x22C6; id; /&#x22C6; Unique demux identifier &#x22C6;/
223− char&#x22C6; vendor; /&#x22C6; Name of the demux vendor &#x22C6;/
224− char&#x22C6; model; /&#x22C6; Name of the demux model &#x22C6;/
225− __u32 capabilities; /&#x22C6; Bitfield of capability flags &#x22C6;/
226− dmx_frontend_t&#x22C6; frontend; /&#x22C6; Front-end connected to the demux &#x22C6;/
227− struct list_head reg_list; /&#x22C6; List of registered demuxes &#x22C6;/
228− void&#x22C6; priv; /&#x22C6; Pointer to private data of the API client &#x22C6;/
229− int users; /&#x22C6; Number of users &#x22C6;/
230− int (&#x22C6;open) (struct dmx_demux_s&#x22C6; demux);
231− int (&#x22C6;close) (struct dmx_demux_s&#x22C6; demux);
232− int (&#x22C6;write) (struct dmx_demux_s&#x22C6; demux, const char&#x22C6; buf, size_t count);
233− int (&#x22C6;allocate_ts_feed) (struct dmx_demux_s&#x22C6; demux,
234− dmx_ts_feed_t&#x22C6;&#x22C6; feed,
235− dmx_ts_cb callback);
236− int (&#x22C6;release_ts_feed) (struct dmx_demux_s&#x22C6; demux,
237− dmx_ts_feed_t&#x22C6; feed);
238− int (&#x22C6;allocate_pes_feed) (struct dmx_demux_s&#x22C6; demux,
239− dmx_pes_feed_t&#x22C6;&#x22C6; feed,
240− dmx_pes_cb callback);
241− int (&#x22C6;release_pes_feed) (struct dmx_demux_s&#x22C6; demux,
242− dmx_pes_feed_t&#x22C6; feed);
243− int (&#x22C6;allocate_section_feed) (struct dmx_demux_s&#x22C6; demux,
244− dmx_section_feed_t&#x22C6;&#x22C6; feed,
245− dmx_section_cb callback);
246− int (&#x22C6;release_section_feed) (struct dmx_demux_s&#x22C6; demux,
247− dmx_section_feed_t&#x22C6; feed);
248− int (&#x22C6;descramble_mac_address) (struct dmx_demux_s&#x22C6; demux,
249− __u8&#x22C6; buffer1,
250− size_t buffer1_length,
251− __u8&#x22C6; buffer2,
252− size_t buffer2_length,
253− __u16 pid);
254− int (&#x22C6;descramble_section_payload) (struct dmx_demux_s&#x22C6; demux,
255− __u8&#x22C6; buffer1,
256− size_t buffer1_length,
257− __u8&#x22C6; buffer2, size_t buffer2_length,
258− __u16 pid);
259− int (&#x22C6;add_frontend) (struct dmx_demux_s&#x22C6; demux,
260− dmx_frontend_t&#x22C6; frontend);
261− int (&#x22C6;remove_frontend) (struct dmx_demux_s&#x22C6; demux,
262− dmx_frontend_t&#x22C6; frontend);
263− struct list_head&#x22C6; (&#x22C6;get_frontends) (struct dmx_demux_s&#x22C6; demux);
264− int (&#x22C6;connect_frontend) (struct dmx_demux_s&#x22C6; demux,
265− dmx_frontend_t&#x22C6; frontend);
266− int (&#x22C6;disconnect_frontend) (struct dmx_demux_s&#x22C6; demux);
267−
268−
269− /&#x22C6; added because js cannot keep track of these himself &#x22C6;/
270− int (&#x22C6;get_pes_pids) (struct dmx_demux_s&#x22C6; demux, __u16 &#x22C6;pids);
271− };
272− typedef struct dmx_demux_s dmx_demux_t;
273−</programlisting>
274−
275−</section>
276−<section id="demux_directory">
277−<title>Demux directory</title>
278− <programlisting>
279− /&#x22C6;
280− &#x22C6; DMX_DIR_ENTRY(): Casts elements in the list of registered
281− &#x22C6; demuxes from the generic type struct list_head&#x22C6; to the type dmx_demux_t
282− &#x22C6;.
283− &#x22C6;/
284−
285− #define DMX_DIR_ENTRY(list) list_entry(list, dmx_demux_t, reg_list)
286−
287− int dmx_register_demux (dmx_demux_t&#x22C6; demux);
288− int dmx_unregister_demux (dmx_demux_t&#x22C6; demux);
289− struct list_head&#x22C6; dmx_get_demuxes (void);
290−</programlisting>
291− </section></section>
292−<section id="demux_directory_api">
293−<title>Demux Directory API</title>
294−<para>The demux directory is a Linux kernel-wide facility for registering and accessing the
295−MPEG-2 TS demuxes in the system. Run-time registering and unregistering of demux drivers
296−is possible using this API.
297−</para>
298−<para>All demux drivers in the directory implement the abstract interface dmx_demux_t.
299−</para>
300−
301−<section
302−role="subsection"><title>dmx_register_demux()</title>
303−<para>DESCRIPTION
304−</para>
305−<informaltable><tgroup cols="1"><tbody><row><entry
306− align="char">
307−<para>This function makes a demux driver interface available to the Linux kernel. It is
308− usually called by the init_module() function of the kernel module that contains
309− the demux driver. The caller of this function is responsible for allocating
310− dynamic or static memory for the demux structure and for initializing its fields
311− before calling this function. The memory allocated for the demux structure
312− must not be freed before calling dmx_unregister_demux(),</para>
313−</entry>
314− </row></tbody></tgroup></informaltable>
315−<para>SYNOPSIS
316−</para>
317−<informaltable><tgroup cols="1"><tbody><row><entry
318− align="char">
319−<para>int dmx_register_demux ( dmx_demux_t &#x22C6;demux )</para>
320−</entry>
321− </row></tbody></tgroup></informaltable>
322−<para>PARAMETERS
323−</para>
324−<informaltable><tgroup cols="2"><tbody><row><entry
325− align="char">
326−<para>dmx_demux_t*
327− demux</para>
328−</entry><entry
329− align="char">
330−<para>Pointer to the demux structure.</para>
331−</entry>
332− </row></tbody></tgroup></informaltable>
333−<para>RETURNS
334−</para>
335−<informaltable><tgroup cols="2"><tbody><row><entry
336− align="char">
337−<para>0</para>
338−</entry><entry
339− align="char">
340−<para>The function was completed without errors.</para>
341−</entry>
342− </row><row><entry
343− align="char">
344−<para>-EEXIST</para>
345−</entry><entry
346− align="char">
347−<para>A demux with the same value of the id field already stored
348− in the directory.</para>
349−</entry>
350− </row><row><entry
351− align="char">
352−<para>-ENOSPC</para>
353−</entry><entry
354− align="char">
355−<para>No space left in the directory.</para>
356−</entry>
357− </row></tbody></tgroup></informaltable>
358−
359−</section><section
360−role="subsection"><title>dmx_unregister_demux()</title>
361−<para>DESCRIPTION
362−</para>
363−<informaltable><tgroup cols="1"><tbody><row><entry
364− align="char">
365−<para>This function is called to indicate that the given demux interface is no
366− longer available. The caller of this function is responsible for freeing the
367− memory of the demux structure, if it was dynamically allocated before calling
368− dmx_register_demux(). The cleanup_module() function of the kernel module
369− that contains the demux driver should call this function. Note that this function
370− fails if the demux is currently in use, i.e., release_demux() has not been called
371− for the interface.</para>
372−</entry>
373− </row></tbody></tgroup></informaltable>
374−<para>SYNOPSIS
375−</para>
376−<informaltable><tgroup cols="1"><tbody><row><entry
377− align="char">
378−<para>int dmx_unregister_demux ( dmx_demux_t &#x22C6;demux )</para>
379−</entry>
380− </row></tbody></tgroup></informaltable>
381−<para>PARAMETERS
382−</para>
383−<informaltable><tgroup cols="2"><tbody><row><entry
384− align="char">
385−<para>dmx_demux_t*
386− demux</para>
387−</entry><entry
388− align="char">
389−<para>Pointer to the demux structure which is to be
390− unregistered.</para>
391−</entry>
392− </row></tbody></tgroup></informaltable>
393−<para>RETURNS
394−</para>
395−<informaltable><tgroup cols="2"><tbody><row><entry
396− align="char">
397−<para>0</para>
398−</entry><entry
399− align="char">
400−<para>The function was completed without errors.</para>
401−</entry>
402− </row><row><entry
403− align="char">
404−<para>ENODEV</para>
405−</entry><entry
406− align="char">
407−<para>The specified demux is not registered in the demux
408− directory.</para>
409−</entry>
410− </row><row><entry
411− align="char">
412−<para>EBUSY</para>
413−</entry><entry
414− align="char">
415−<para>The specified demux is currently in use.</para>
416−</entry>
417− </row></tbody></tgroup></informaltable>
418−
419−</section><section
420−role="subsection"><title>dmx_get_demuxes()</title>
421−<para>DESCRIPTION
422−</para>
423−<informaltable><tgroup cols="1"><tbody><row><entry
424− align="char">
425−<para>Provides the caller with the list of registered demux interfaces, using the
426− standard list structure defined in the include file linux/list.h. The include file
427− demux.h defines the macro DMX_DIR_ENTRY() for converting an element of
428− the generic type struct list_head* to the type dmx_demux_t*. The caller must
429− not free the memory of any of the elements obtained via this function call.</para>
430−</entry>
431− </row></tbody></tgroup></informaltable>
432−<para>SYNOPSIS
433−</para>
434−<informaltable><tgroup cols="1"><tbody><row><entry
435− align="char">
436−<para>struct list_head &#x22C6;dmx_get_demuxes ()</para>
437−</entry>
438− </row></tbody></tgroup></informaltable>
439−<para>PARAMETERS
440−</para>
441−<informaltable><tgroup cols="2"><tbody><row><entry
442− align="char">
443−<para>none</para>
444−</entry>
445− </row></tbody></tgroup></informaltable>
446−<para>RETURNS
447−</para>
448−<informaltable><tgroup cols="2"><tbody><row><entry
449− align="char">
450−<para>struct list_head *</para>
451−</entry><entry
452− align="char">
453−<para>A list of demux interfaces, or NULL in the case of an
454− empty list.</para>
455−</entry>
456− </row></tbody></tgroup></informaltable>
457− </section></section>
458−<section id="demux_api">
459−<title>Demux API</title>
460−<para>The demux API should be implemented for each demux in the system. It is used to select
461−the TS source of a demux and to manage the demux resources. When the demux
462−client allocates a resource via the demux API, it receives a pointer to the API of that
463−resource.
464−</para>
465−<para>Each demux receives its TS input from a DVB front-end or from memory, as set via the
466−demux API. In a system with more than one front-end, the API can be used to select one of
467−the DVB front-ends as a TS source for a demux, unless this is fixed in the HW platform. The
468−demux API only controls front-ends regarding their connections with demuxes; the APIs
469−used to set the other front-end parameters, such as tuning, are not defined in this
470−document.
471−</para>
472−<para>The functions that implement the abstract interface demux should be defined static or
473−module private and registered to the Demux Directory for external access. It is not necessary
474−to implement every function in the demux_t struct, however (for example, a demux interface
475−might support Section filtering, but not TS or PES filtering). The API client is expected to
476−check the value of any function pointer before calling the function: the value of NULL means
477−&#8220;function not available&#8221;.
478−</para>
479−<para>Whenever the functions of the demux API modify shared data, the possibilities of lost
480−update and race condition problems should be addressed, e.g. by protecting parts of code with
481−mutexes. This is especially important on multi-processor hosts.
482−</para>
483−<para>Note that functions called from a bottom half context must not sleep, at least in the 2.2.x
484−kernels. Even a simple memory allocation can result in a kernel thread being put to sleep if
485−swapping is needed. For example, the Linux kernel calls the functions of a network device
486−interface from a bottom half context. Thus, if a demux API function is called from network
487−device code, the function must not sleep.
488−</para>
489−
490−
491−<section id="kdapi_fopen">
492−<title>open()</title>
493−<para>DESCRIPTION
494−</para>
495−<informaltable><tgroup cols="1"><tbody><row><entry
496− align="char">
497−<para>This function reserves the demux for use by the caller and, if necessary,
498− initializes the demux. When the demux is no longer needed, the function close()
499− should be called. It should be possible for multiple clients to access the demux
500− at the same time. Thus, the function implementation should increment the
501− demux usage count when open() is called and decrement it when close() is
502− called.</para>
503−</entry>
504− </row></tbody></tgroup></informaltable>
505−<para>SYNOPSIS
506−</para>
507−<informaltable><tgroup cols="1"><tbody><row><entry
508− align="char">
509−<para>int open ( demux_t&#x22C6; demux );</para>
510−</entry>
511− </row></tbody></tgroup></informaltable>
512−<para>PARAMETERS
513−</para>
514−<informaltable><tgroup cols="2"><tbody><row><entry
515− align="char">
516−<para>demux_t* demux</para>
517−</entry><entry
518− align="char">
519−<para>Pointer to the demux API and instance data.</para>
520−</entry>
521− </row></tbody></tgroup></informaltable>
522−<para>RETURNS
523−</para>
524−<informaltable><tgroup cols="2"><tbody><row><entry
525− align="char">
526−<para>0</para>
527−</entry><entry
528− align="char">
529−<para>The function was completed without errors.</para>
530−</entry>
531− </row><row><entry
532− align="char">
533−<para>-EUSERS</para>
534−</entry><entry
535− align="char">
536−<para>Maximum usage count reached.</para>
537−</entry>
538− </row><row><entry
539− align="char">
540−<para>-EINVAL</para>
541−</entry><entry
542− align="char">
543−<para>Bad parameter.</para>
544−</entry>
545− </row></tbody></tgroup></informaltable>
546−
547−</section>
548−<section id="kdapi_fclose">
549−<title>close()</title>
550−<para>DESCRIPTION
551−</para>
552−<informaltable><tgroup cols="1"><tbody><row><entry
553− align="char">
554−<para>This function reserves the demux for use by the caller and, if necessary,
555− initializes the demux. When the demux is no longer needed, the function close()
556− should be called. It should be possible for multiple clients to access the demux
557− at the same time. Thus, the function implementation should increment the
558− demux usage count when open() is called and decrement it when close() is
559− called.</para>
560−</entry>
561− </row></tbody></tgroup></informaltable>
562−<para>SYNOPSIS
563−</para>
564−<informaltable><tgroup cols="1"><tbody><row><entry
565− align="char">
566−<para>int close(demux_t&#x22C6; demux);</para>
567−</entry>
568− </row></tbody></tgroup></informaltable>
569−<para>PARAMETERS
570−</para>
571−<informaltable><tgroup cols="2"><tbody><row><entry
572− align="char">
573−<para>demux_t* demux</para>
574−</entry><entry
575− align="char">
576−<para>Pointer to the demux API and instance data.</para>
577−</entry>
578− </row></tbody></tgroup></informaltable>
579−<para>RETURNS
580−</para>
581−<informaltable><tgroup cols="2"><tbody><row><entry
582− align="char">
583−<para>0</para>
584−</entry><entry
585− align="char">
586−<para>The function was completed without errors.</para>
587−</entry>
588− </row><row><entry
589− align="char">
590−<para>-ENODEV</para>
591−</entry><entry
592− align="char">
593−<para>The demux was not in use.</para>
594−</entry>
595− </row><row><entry
596− align="char">
597−<para>-EINVAL</para>
598−</entry><entry
599− align="char">
600−<para>Bad parameter.</para>
601−</entry>
602− </row></tbody></tgroup></informaltable>
603−
604−</section>
605−<section id="kdapi_fwrite">
606−<title>write()</title>
607−<para>DESCRIPTION
608−</para>
609−<informaltable><tgroup cols="1"><tbody><row><entry
610− align="char">
611−<para>This function provides the demux driver with a memory buffer containing TS
612− packets. Instead of receiving TS packets from the DVB front-end, the demux
613− driver software will read packets from memory. Any clients of this demux
614− with active TS, PES or Section filters will receive filtered data via the Demux
615− callback API (see 0). The function returns when all the data in the buffer has
616− been consumed by the demux. Demux hardware typically cannot read TS from
617− memory. If this is the case, memory-based filtering has to be implemented
618− entirely in software.</para>
619−</entry>
620− </row></tbody></tgroup></informaltable>
621−<para>SYNOPSIS
622−</para>
623−<informaltable><tgroup cols="1"><tbody><row><entry
624− align="char">
625−<para>int write(demux_t&#x22C6; demux, const char&#x22C6; buf, size_t
626− count);</para>
627−</entry>
628− </row></tbody></tgroup></informaltable>
629−<para>PARAMETERS
630−</para>
631−<informaltable><tgroup cols="2"><tbody><row><entry
632− align="char">
633−<para>demux_t* demux</para>
634−</entry><entry
635− align="char">
636−<para>Pointer to the demux API and instance data.</para>
637−</entry>
638− </row><row><entry
639− align="char">
640−<para>const char* buf</para>
641−</entry><entry
642− align="char">
643−<para>Pointer to the TS data in kernel-space memory.</para>
644−</entry>
645− </row><row><entry
646− align="char">
647−<para>size_t length</para>
648−</entry><entry
649− align="char">
650−<para>Length of the TS data.</para>
651−</entry>
652− </row></tbody></tgroup></informaltable>
653−<para>RETURNS
654−</para>
655−<informaltable><tgroup cols="2"><tbody><row><entry
656− align="char">
657−<para>0</para>
658−</entry><entry
659− align="char">
660−<para>The function was completed without errors.</para>
661−</entry>
662− </row><row><entry
663− align="char">
664−<para>-ENOSYS</para>
665−</entry><entry
666− align="char">
667−<para>The command is not implemented.</para>
668−</entry>
669− </row><row><entry
670− align="char">
671−<para>-EINVAL</para>
672−</entry><entry
673− align="char">
674−<para>Bad parameter.</para>
675−</entry>
676− </row></tbody></tgroup></informaltable>
677−
678−</section><section
679−role="subsection"><title>allocate_ts_feed()</title>
680−<para>DESCRIPTION
681−</para>
682−<informaltable><tgroup cols="1"><tbody><row><entry
683− align="char">
684−<para>Allocates a new TS feed, which is used to filter the TS packets carrying a
685− certain PID. The TS feed normally corresponds to a hardware PID filter on the
686− demux chip.</para>
687−</entry>
688− </row></tbody></tgroup></informaltable>
689−<para>SYNOPSIS
690−</para>
691−<informaltable><tgroup cols="1"><tbody><row><entry
692− align="char">
693−<para>int allocate_ts_feed(dmx_demux_t&#x22C6; demux,
694− dmx_ts_feed_t&#x22C6;&#x22C6; feed, dmx_ts_cb callback);</para>
695−</entry>
696− </row></tbody></tgroup></informaltable>
697−<para>PARAMETERS
698−</para>
699−<informaltable><tgroup cols="2"><tbody><row><entry
700− align="char">
701−<para>demux_t* demux</para>
702−</entry><entry
703− align="char">
704−<para>Pointer to the demux API and instance data.</para>
705−</entry>
706− </row><row><entry
707− align="char">
708−<para>dmx_ts_feed_t**
709− feed</para>
710−</entry><entry
711− align="char">
712−<para>Pointer to the TS feed API and instance data.</para>
713−</entry>
714− </row><row><entry
715− align="char">
716−<para>dmx_ts_cb callback</para>
717−</entry><entry
718− align="char">
719−<para>Pointer to the callback function for passing received TS
720− packet</para>
721−</entry>
722− </row></tbody></tgroup></informaltable>
723−<para>RETURNS
724−</para>
725−<informaltable><tgroup cols="2"><tbody><row><entry
726− align="char">
727−<para>0</para>
728−</entry><entry
729− align="char">
730−<para>The function was completed without errors.</para>
731−</entry>
732− </row><row><entry
733− align="char">
734−<para>-EBUSY</para>
735−</entry><entry
736− align="char">
737−<para>No more TS feeds available.</para>
738−</entry>
739− </row><row><entry
740− align="char">
741−<para>-ENOSYS</para>
742−</entry><entry
743− align="char">
744−<para>The command is not implemented.</para>
745−</entry>
746− </row><row><entry
747− align="char">
748−<para>-EINVAL</para>
749−</entry><entry
750− align="char">
751−<para>Bad parameter.</para>
752−</entry>
753− </row></tbody></tgroup></informaltable>
754−
755−</section><section
756−role="subsection"><title>release_ts_feed()</title>
757−<para>DESCRIPTION
758−</para>
759−<informaltable><tgroup cols="1"><tbody><row><entry
760− align="char">
761−<para>Releases the resources allocated with allocate_ts_feed(). Any filtering in
762− progress on the TS feed should be stopped before calling this function.</para>
763−</entry>
764− </row></tbody></tgroup></informaltable>
765−<para>SYNOPSIS
766−</para>
767−<informaltable><tgroup cols="1"><tbody><row><entry
768− align="char">
769−<para>int release_ts_feed(dmx_demux_t&#x22C6; demux,
770− dmx_ts_feed_t&#x22C6; feed);</para>
771−</entry>
772− </row></tbody></tgroup></informaltable>
773−<para>PARAMETERS
774−</para>
775−<informaltable><tgroup cols="2"><tbody><row><entry
776− align="char">
777−<para>demux_t* demux</para>
778−</entry><entry
779− align="char">
780−<para>Pointer to the demux API and instance data.</para>
781−</entry>
782− </row><row><entry
783− align="char">
784−<para>dmx_ts_feed_t* feed</para>
785−</entry><entry
786− align="char">
787−<para>Pointer to the TS feed API and instance data.</para>
788−</entry>
789− </row></tbody></tgroup></informaltable>
790−<para>RETURNS
791−</para>
792−<informaltable><tgroup cols="2"><tbody><row><entry
793− align="char">
794−<para>0</para>
795−</entry><entry
796− align="char">
797−<para>The function was completed without errors.</para>
798−</entry>
799− </row><row><entry
800− align="char">
801−<para>-EINVAL</para>
802−</entry><entry
803− align="char">
804−<para>Bad parameter.</para>
805−</entry>
806− </row></tbody></tgroup></informaltable>
807−
808−</section><section
809−role="subsection"><title>allocate_section_feed()</title>
810−<para>DESCRIPTION
811−</para>
812−<informaltable><tgroup cols="1"><tbody><row><entry
813− align="char">
814−<para>Allocates a new section feed, i.e. a demux resource for filtering and receiving
815− sections. On platforms with hardware support for section filtering, a section
816− feed is directly mapped to the demux HW. On other platforms, TS packets are
817− first PID filtered in hardware and a hardware section filter then emulated in
818− software. The caller obtains an API pointer of type dmx_section_feed_t as an
819− out parameter. Using this API the caller can set filtering parameters and start
820− receiving sections.</para>
821−</entry>
822− </row></tbody></tgroup></informaltable>
823−<para>SYNOPSIS
824−</para>
825−<informaltable><tgroup cols="1"><tbody><row><entry
826− align="char">
827−<para>int allocate_section_feed(dmx_demux_t&#x22C6; demux,
828− dmx_section_feed_t &#x22C6;&#x22C6;feed, dmx_section_cb callback);</para>
829−</entry>
830− </row></tbody></tgroup></informaltable>
831−<para>PARAMETERS
832−</para>
833−<informaltable><tgroup cols="2"><tbody><row><entry
834− align="char">
835−<para>demux_t *demux</para>
836−</entry><entry
837− align="char">
838−<para>Pointer to the demux API and instance data.</para>
839−</entry>
840− </row><row><entry
841− align="char">
842−<para>dmx_section_feed_t
843− **feed</para>
844−</entry><entry
845− align="char">
846−<para>Pointer to the section feed API and instance data.</para>
847−</entry>
848− </row><row><entry
849− align="char">
850−<para>dmx_section_cb
851− callback</para>
852−</entry><entry
853− align="char">
854−<para>Pointer to the callback function for passing received
855− sections.</para>
856−</entry>
857− </row></tbody></tgroup></informaltable>
858−<para>RETURNS
859−</para>
860−<informaltable><tgroup cols="2"><tbody><row><entry
861− align="char">
862−<para>0</para>
863−</entry><entry
864− align="char">
865−<para>The function was completed without errors.</para>
866−</entry>
867− </row><row><entry
868− align="char">
869−<para>-EBUSY</para>
870−</entry><entry
871− align="char">
872−<para>No more section feeds available.</para>
873−</entry>
874− </row><row><entry
875− align="char">
876−<para>-ENOSYS</para>
877−</entry><entry
878− align="char">
879−<para>The command is not implemented.</para>
880−</entry>
881− </row><row><entry
882− align="char">
883−<para>-EINVAL</para>
884−</entry><entry
885− align="char">
886−<para>Bad parameter.</para>
887−</entry>
888− </row></tbody></tgroup></informaltable>
889−
890−</section><section
891−role="subsection"><title>release_section_feed()</title>
892−<para>DESCRIPTION
893−</para>
894−<informaltable><tgroup cols="1"><tbody><row><entry
895− align="char">
896−<para>Releases the resources allocated with allocate_section_feed(), including
897− allocated filters. Any filtering in progress on the section feed should be stopped
898− before calling this function.</para>
899−</entry>
900− </row></tbody></tgroup></informaltable>
901−<para>SYNOPSIS
902−</para>
903−<informaltable><tgroup cols="1"><tbody><row><entry
904− align="char">
905−<para>int release_section_feed(dmx_demux_t&#x22C6; demux,
906− dmx_section_feed_t &#x22C6;feed);</para>
907−</entry>
908− </row></tbody></tgroup></informaltable>
909−<para>PARAMETERS
910−</para>
911−<informaltable><tgroup cols="2"><tbody><row><entry
912− align="char">
913−<para>demux_t *demux</para>
914−</entry><entry
915− align="char">
916−<para>Pointer to the demux API and instance data.</para>
917−</entry>
918− </row><row><entry
919− align="char">
920−<para>dmx_section_feed_t
921− *feed</para>
922−</entry><entry
923− align="char">
924−<para>Pointer to the section feed API and instance data.</para>
925−</entry>
926− </row></tbody></tgroup></informaltable>
927−<para>RETURNS
928−</para>
929−<informaltable><tgroup cols="2"><tbody><row><entry
930− align="char">
931−<para>0</para>
932−</entry><entry
933− align="char">
934−<para>The function was completed without errors.</para>
935−</entry>
936− </row><row><entry
937− align="char">
938−<para>-EINVAL</para>
939−</entry><entry
940− align="char">
941−<para>Bad parameter.</para>
942−</entry>
943− </row></tbody></tgroup></informaltable>
944−
945−</section><section
946−role="subsection"><title>descramble_mac_address()</title>
947−<para>DESCRIPTION
948−</para>
949−<informaltable><tgroup cols="1"><tbody><row><entry
950− align="char">
951−<para>This function runs a descrambling algorithm on the destination MAC
952− address field of a DVB Datagram Section, replacing the original address
953− with its un-encrypted version. Otherwise, the description on the function
954− descramble_section_payload() applies also to this function.</para>
955−</entry>
956− </row></tbody></tgroup></informaltable>
957−<para>SYNOPSIS
958−</para>
959−<informaltable><tgroup cols="1"><tbody><row><entry
960− align="char">
961−<para>int descramble_mac_address(dmx_demux_t&#x22C6; demux, __u8
962− &#x22C6;buffer1, size_t buffer1_length, __u8 &#x22C6;buffer2,
963− size_t buffer2_length, __u16 pid);</para>
964−</entry>
965− </row></tbody></tgroup></informaltable>
966−<para>PARAMETERS
967−</para>
968−<informaltable><tgroup cols="2"><tbody><row><entry
969− align="char">
970−<para>dmx_demux_t
971− *demux</para>
972−</entry><entry
973− align="char">
974−<para>Pointer to the demux API and instance data.</para>
975−</entry>
976− </row><row><entry
977− align="char">
978−<para>__u8 *buffer1</para>
979−</entry><entry
980− align="char">
981−<para>Pointer to the first byte of the section.</para>
982−</entry>
983− </row><row><entry
984− align="char">
985−<para>size_t buffer1_length</para>
986−</entry><entry
987− align="char">
988−<para>Length of the section data, including headers and CRC,
989− in buffer1.</para>
990−</entry>
991− </row><row><entry
992− align="char">
993−<para>__u8* buffer2</para>
994−</entry><entry
995− align="char">
996−<para>Pointer to the tail of the section data, or NULL. The
997− pointer has a non-NULL value if the section wraps past
998− the end of a circular buffer.</para>
999−</entry>
1000− </row><row><entry
1001− align="char">
1002−<para>size_t buffer2_length</para>
1003−</entry><entry
1004− align="char">
1005−<para>Length of the section data, including headers and CRC,
1006− in buffer2.</para>
1007−</entry>
1008− </row><row><entry
1009− align="char">
1010−<para>__u16 pid</para>
1011−</entry><entry
1012− align="char">
1013−<para>The PID on which the section was received. Useful
1014− for obtaining the descrambling key, e.g. from a DVB
1015− Common Access facility.</para>
1016−</entry>
1017− </row></tbody></tgroup></informaltable>
1018−<para>RETURNS
1019−</para>
1020−<informaltable><tgroup cols="2"><tbody><row><entry
1021− align="char">
1022−<para>0</para>
1023−</entry><entry
1024− align="char">
1025−<para>The function was completed without errors.</para>
1026−</entry>
1027− </row><row><entry
1028− align="char">
1029−<para>-ENOSYS</para>
1030−</entry><entry
1031− align="char">
1032−<para>No descrambling facility available.</para>
1033−</entry>
1034− </row><row><entry
1035− align="char">
1036−<para>-EINVAL</para>
1037−</entry><entry
1038− align="char">
1039−<para>Bad parameter.</para>
1040−</entry>
1041− </row></tbody></tgroup></informaltable>
1042−
1043−</section><section
1044−role="subsection"><title>descramble_section_payload()</title>
1045−<para>DESCRIPTION
1046−</para>
1047−<informaltable><tgroup cols="1"><tbody><row><entry
1048− align="char">
1049−<para>This function runs a descrambling algorithm on the payload of a DVB
1050− Datagram Section, replacing the original payload with its un-encrypted
1051− version. The function will be called from the demux API implementation;
1052− the API client need not call this function directly. Section-level scrambling
1053− algorithms are currently standardized only for DVB-RCC (return channel
1054− over 2-directional cable TV network) systems. For all other DVB networks,
1055− encryption schemes are likely to be proprietary to each data broadcaster. Thus,
1056− it is expected that this function pointer will have the value of NULL (i.e.,
1057− function not available) in most demux API implementations. Nevertheless, it
1058− should be possible to use the function pointer as a hook for dynamically adding
1059− a &#8220;plug-in&#8221; descrambling facility to a demux driver.</para>
1060−</entry>
1061− </row><row><entry
1062− align="char">
1063−<para>While this function is not needed with hardware-based section descrambling,
1064− the descramble_section_payload function pointer can be used to override the
1065− default hardware-based descrambling algorithm: if the function pointer has a
1066− non-NULL value, the corresponding function should be used instead of any
1067− descrambling hardware.</para>
1068−</entry>
1069− </row></tbody></tgroup></informaltable>
1070−<para>SYNOPSIS
1071−</para>
1072−<informaltable><tgroup cols="1"><tbody><row><entry
1073− align="char">
1074−<para>int descramble_section_payload(dmx_demux_t&#x22C6; demux,
1075− __u8 &#x22C6;buffer1, size_t buffer1_length, __u8 &#x22C6;buffer2,
1076− size_t buffer2_length, __u16 pid);</para>
1077−</entry>
1078− </row></tbody></tgroup></informaltable>
1079−<para>PARAMETERS
1080−</para>
1081−<informaltable><tgroup cols="2"><tbody><row><entry
1082− align="char">
1083−<para>dmx_demux_t
1084− *demux</para>
1085−</entry><entry
1086− align="char">
1087−<para>Pointer to the demux API and instance data.</para>
1088−</entry>
1089− </row><row><entry
1090− align="char">
1091−<para>__u8 *buffer1</para>
1092−</entry><entry
1093− align="char">
1094−<para>Pointer to the first byte of the section.</para>
1095−</entry>
1096− </row><row><entry
1097− align="char">
1098−<para>size_t buffer1_length</para>
1099−</entry><entry
1100− align="char">
1101−<para>Length of the section data, including headers and CRC,
1102− in buffer1.</para>
1103−</entry>
1104− </row><row><entry
1105− align="char">
1106−<para>__u8 *buffer2</para>
1107−</entry><entry
1108− align="char">
1109−<para>Pointer to the tail of the section data, or NULL. The
1110− pointer has a non-NULL value if the section wraps past
1111− the end of a circular buffer.</para>
1112−</entry>
1113− </row><row><entry
1114− align="char">
1115−<para>size_t buffer2_length</para>
1116−</entry><entry
1117− align="char">
1118−<para>Length of the section data, including headers and CRC,
1119− in buffer2.</para>
1120−</entry>
1121− </row><row><entry
1122− align="char">
1123−<para>__u16 pid</para>
1124−</entry><entry
1125− align="char">
1126−<para>The PID on which the section was received. Useful
1127− for obtaining the descrambling key, e.g. from a DVB
1128− Common Access facility.</para>
1129−</entry>
1130− </row></tbody></tgroup></informaltable>
1131−<para>RETURNS
1132−</para>
1133−<informaltable><tgroup cols="2"><tbody><row><entry
1134− align="char">
1135−<para>0</para>
1136−</entry><entry
1137− align="char">
1138−<para>The function was completed without errors.</para>
1139−</entry>
1140− </row><row><entry
1141− align="char">
1142−<para>-ENOSYS</para>
1143−</entry><entry
1144− align="char">
1145−<para>No descrambling facility available.</para>
1146−</entry>
1147− </row><row><entry
1148− align="char">
1149−<para>-EINVAL</para>
1150−</entry><entry
1151− align="char">
1152−<para>Bad parameter.</para>
1153−</entry>
1154− </row></tbody></tgroup></informaltable>
1155−
1156−</section><section
1157−role="subsection"><title>add_frontend()</title>
1158−<para>DESCRIPTION
1159−</para>
1160−<informaltable><tgroup cols="1"><tbody><row><entry
1161− align="char">
1162−<para>Registers a connectivity between a demux and a front-end, i.e., indicates that
1163− the demux can be connected via a call to connect_frontend() to use the given
1164− front-end as a TS source. The client of this function has to allocate dynamic or
1165− static memory for the frontend structure and initialize its fields before calling
1166− this function. This function is normally called during the driver initialization.
1167− The caller must not free the memory of the frontend struct before successfully
1168− calling remove_frontend().</para>
1169−</entry>
1170− </row></tbody></tgroup></informaltable>
1171−<para>SYNOPSIS
1172−</para>
1173−<informaltable><tgroup cols="1"><tbody><row><entry
1174− align="char">
1175−<para>int add_frontend(dmx_demux_t &#x22C6;demux, dmx_frontend_t
1176− &#x22C6;frontend);</para>
1177−</entry>
1178− </row></tbody></tgroup></informaltable>
1179−<para>PARAMETERS
1180−</para>
1181−<informaltable><tgroup cols="2"><tbody><row><entry
1182− align="char">
1183−<para>dmx_demux_t*
1184− demux</para>
1185−</entry><entry
1186− align="char">
1187−<para>Pointer to the demux API and instance data.</para>
1188−</entry>
1189− </row><row><entry
1190− align="char">
1191−<para>dmx_frontend_t*
1192− frontend</para>
1193−</entry><entry
1194− align="char">
1195−<para>Pointer to the front-end instance data.</para>
1196−</entry>
1197− </row></tbody></tgroup></informaltable>
1198−<para>RETURNS
1199−</para>
1200−<informaltable><tgroup cols="2"><tbody><row><entry
1201− align="char">
1202−<para>0</para>
1203−</entry><entry
1204− align="char">
1205−<para>The function was completed without errors.</para>
1206−</entry>
1207− </row><row><entry
1208− align="char">
1209−<para>-EEXIST</para>
1210−</entry><entry
1211− align="char">
1212−<para>A front-end with the same value of the id field already
1213− registered.</para>
1214−</entry>
1215− </row><row><entry
1216− align="char">
1217−<para>-EINUSE</para>
1218−</entry><entry
1219− align="char">
1220−<para>The demux is in use.</para>
1221−</entry>
1222− </row><row><entry
1223− align="char">
1224−<para>-ENOMEM</para>
1225−</entry><entry
1226− align="char">
1227−<para>No more front-ends can be added.</para>
1228−</entry>
1229− </row><row><entry
1230− align="char">
1231−<para>-EINVAL</para>
1232−</entry><entry
1233− align="char">
1234−<para>Bad parameter.</para>
1235−</entry>
1236− </row></tbody></tgroup></informaltable>
1237−
1238−</section><section
1239−role="subsection"><title>remove_frontend()</title>
1240−<para>DESCRIPTION
1241−</para>
1242−<informaltable><tgroup cols="1"><tbody><row><entry
1243− align="char">
1244−<para>Indicates that the given front-end, registered by a call to add_frontend(), can
1245− no longer be connected as a TS source by this demux. The function should be
1246− called when a front-end driver or a demux driver is removed from the system.
1247− If the front-end is in use, the function fails with the return value of -EBUSY.
1248− After successfully calling this function, the caller can free the memory of
1249− the frontend struct if it was dynamically allocated before the add_frontend()
1250− operation.</para>
1251−</entry>
1252− </row></tbody></tgroup></informaltable>
1253−<para>SYNOPSIS
1254−</para>
1255−<informaltable><tgroup cols="1"><tbody><row><entry
1256− align="char">
1257−<para>int remove_frontend(dmx_demux_t&#x22C6; demux,
1258− dmx_frontend_t&#x22C6; frontend);</para>
1259−</entry>
1260− </row></tbody></tgroup></informaltable>
1261−<para>PARAMETERS
1262−</para>
1263−<informaltable><tgroup cols="2"><tbody><row><entry
1264− align="char">
1265−<para>dmx_demux_t*
1266− demux</para>
1267−</entry><entry
1268− align="char">
1269−<para>Pointer to the demux API and instance data.</para>
1270−</entry>
1271− </row><row><entry
1272− align="char">
1273−<para>dmx_frontend_t*
1274− frontend</para>
1275−</entry><entry
1276− align="char">
1277−<para>Pointer to the front-end instance data.</para>
1278−</entry>
1279− </row></tbody></tgroup></informaltable>
1280−<para>RETURNS
1281−</para>
1282−<informaltable><tgroup cols="2"><tbody><row><entry
1283− align="char">
1284−<para>0</para>
1285−</entry><entry
1286− align="char">
1287−<para>The function was completed without errors.</para>
1288−</entry>
1289− </row><row><entry
1290− align="char">
1291−<para>-EINVAL</para>
1292−</entry><entry
1293− align="char">
1294−<para>Bad parameter.</para>
1295−</entry>
1296− </row><row><entry
1297− align="char">
1298−<para>-EBUSY</para>
1299−</entry><entry
1300− align="char">
1301−<para>The front-end is in use, i.e. a call to connect_frontend()
1302− has not been followed by a call to disconnect_frontend().</para>
1303−</entry>
1304− </row></tbody></tgroup></informaltable>
1305−
1306−</section><section
1307−role="subsection"><title>get_frontends()</title>
1308−<para>DESCRIPTION
1309−</para>
1310−<informaltable><tgroup cols="1"><tbody><row><entry
1311− align="char">
1312−<para>Provides the APIs of the front-ends that have been registered for this demux.
1313− Any of the front-ends obtained with this call can be used as a parameter for
1314− connect_frontend().</para>
1315−</entry>
1316− </row><row><entry
1317− align="char">
1318−<para>The include file demux.h contains the macro DMX_FE_ENTRY() for
1319− converting an element of the generic type struct list_head* to the type
1320− dmx_frontend_t*. The caller must not free the memory of any of the elements
1321− obtained via this function call.</para>
1322−</entry>
1323− </row></tbody></tgroup></informaltable>
1324−<para>SYNOPSIS
1325−</para>
1326−<informaltable><tgroup cols="1"><tbody><row><entry
1327− align="char">
1328−<para>struct list_head&#x22C6; get_frontends(dmx_demux_t&#x22C6; demux);</para>
1329−</entry>
1330− </row></tbody></tgroup></informaltable>
1331−<para>PARAMETERS
1332−</para>
1333−<informaltable><tgroup cols="2"><tbody><row><entry
1334− align="char">
1335−<para>dmx_demux_t*
1336− demux</para>
1337−</entry><entry
1338− align="char">
1339−<para>Pointer to the demux API and instance data.</para>
1340−</entry>
1341− </row></tbody></tgroup></informaltable>
1342−<para>RETURNS
1343−</para>
1344−<informaltable><tgroup cols="2"><tbody><row><entry
1345− align="char">
1346−<para>dmx_demux_t*</para>
1347−</entry><entry
1348− align="char">
1349−<para>A list of front-end interfaces, or NULL in the case of an
1350− empty list.</para>
1351−</entry>
1352− </row></tbody></tgroup></informaltable>
1353−
1354−</section><section
1355−role="subsection"><title>connect_frontend()</title>
1356−<para>DESCRIPTION
1357−</para>
1358−<informaltable><tgroup cols="1"><tbody><row><entry
1359− align="char">
1360−<para>Connects the TS output of the front-end to the input of the demux. A demux
1361− can only be connected to a front-end registered to the demux with the function
1362− add_frontend().</para>
1363−</entry>
1364− </row><row><entry
1365− align="char">
1366−<para>It may or may not be possible to connect multiple demuxes to the same
1367− front-end, depending on the capabilities of the HW platform. When not used,
1368− the front-end should be released by calling disconnect_frontend().</para>
1369−</entry>
1370− </row></tbody></tgroup></informaltable>
1371−<para>SYNOPSIS
1372−</para>
1373−<informaltable><tgroup cols="1"><tbody><row><entry
1374− align="char">
1375−<para>int connect_frontend(dmx_demux_t&#x22C6; demux,
1376− dmx_frontend_t&#x22C6; frontend);</para>
1377−</entry>
1378− </row></tbody></tgroup></informaltable>
1379−<para>PARAMETERS
1380−</para>
1381−<informaltable><tgroup cols="2"><tbody><row><entry
1382− align="char">
1383−<para>dmx_demux_t*
1384− demux</para>
1385−</entry><entry
1386− align="char">
1387−<para>Pointer to the demux API and instance data.</para>
1388−</entry>
1389− </row><row><entry
1390− align="char">
1391−<para>dmx_frontend_t*
1392− frontend</para>
1393−</entry><entry
1394− align="char">
1395−<para>Pointer to the front-end instance data.</para>
1396−</entry>
1397− </row></tbody></tgroup></informaltable>
1398−<para>RETURNS
1399−</para>
1400−<informaltable><tgroup cols="2"><tbody><row><entry
1401− align="char">
1402−<para>0</para>
1403−</entry><entry
1404− align="char">
1405−<para>The function was completed without errors.</para>
1406−</entry>
1407− </row><row><entry
1408− align="char">
1409−<para>-EINVAL</para>
1410−</entry><entry
1411− align="char">
1412−<para>Bad parameter.</para>
1413−</entry>
1414− </row><row><entry
1415− align="char">
1416−<para>-EBUSY</para>
1417−</entry><entry
1418− align="char">
1419−<para>The front-end is in use.</para>
1420−</entry>
1421− </row></tbody></tgroup></informaltable>
1422−
1423−</section><section
1424−role="subsection"><title>disconnect_frontend()</title>
1425−<para>DESCRIPTION
1426−</para>
1427−<informaltable><tgroup cols="1"><tbody><row><entry
1428− align="char">
1429−<para>Disconnects the demux and a front-end previously connected by a
1430− connect_frontend() call.</para>
1431−</entry>
1432− </row></tbody></tgroup></informaltable>
1433−<para>SYNOPSIS
1434−</para>
1435−<informaltable><tgroup cols="1"><tbody><row><entry
1436− align="char">
1437−<para>int disconnect_frontend(dmx_demux_t&#x22C6; demux);</para>
1438−</entry>
1439− </row></tbody></tgroup></informaltable>
1440−<para>PARAMETERS
1441−</para>
1442−<informaltable><tgroup cols="2"><tbody><row><entry
1443− align="char">
1444−<para>dmx_demux_t*
1445− demux</para>
1446−</entry><entry
1447− align="char">
1448−<para>Pointer to the demux API and instance data.</para>
1449−</entry>
1450− </row></tbody></tgroup></informaltable>
1451−<para>RETURNS
1452−</para>
1453−<informaltable><tgroup cols="2"><tbody><row><entry
1454− align="char">
1455−<para>0</para>
1456−</entry><entry
1457− align="char">
1458−<para>The function was completed without errors.</para>
1459−</entry>
1460− </row><row><entry
1461− align="char">
1462−<para>-EINVAL</para>
1463−</entry><entry
1464− align="char">
1465−<para>Bad parameter.</para>
1466−</entry>
1467− </row></tbody></tgroup></informaltable>
1468− </section></section>
1469−<section id="demux_callback_api">
1470−<title>Demux Callback API</title>
1471−<para>This kernel-space API comprises the callback functions that deliver filtered data to the
1472−demux client. Unlike the other APIs, these API functions are provided by the client and called
1473−from the demux code.
1474−</para>
1475−<para>The function pointers of this abstract interface are not packed into a structure as in the
1476−other demux APIs, because the callback functions are registered and used independent
1477−of each other. As an example, it is possible for the API client to provide several
1478−callback functions for receiving TS packets and no callbacks for PES packets or
1479−sections.
1480−</para>
1481−<para>The functions that implement the callback API need not be re-entrant: when a demux
1482−driver calls one of these functions, the driver is not allowed to call the function again before
1483−the original call returns. If a callback is triggered by a hardware interrupt, it is recommended
1484−to use the Linux &#8220;bottom half&#8221; mechanism or start a tasklet instead of making the callback
1485−function call directly from a hardware interrupt.
1486−</para>
1487−
1488−<section
1489−role="subsection"><title>dmx_ts_cb()</title>
1490−<para>DESCRIPTION
1491−</para>
1492−<informaltable><tgroup cols="1"><tbody><row><entry
1493− align="char">
1494−<para>This function, provided by the client of the demux API, is called from the
1495− demux code. The function is only called when filtering on this TS feed has
1496− been enabled using the start_filtering() function.</para>
1497−</entry>
1498− </row><row><entry
1499− align="char">
1500−<para>Any TS packets that match the filter settings are copied to a circular buffer. The
1501− filtered TS packets are delivered to the client using this callback function. The
1502− size of the circular buffer is controlled by the circular_buffer_size parameter
1503− of the set() function in the TS Feed API. It is expected that the buffer1 and
1504− buffer2 callback parameters point to addresses within the circular buffer, but
1505− other implementations are also possible. Note that the called party should not
1506− try to free the memory the buffer1 and buffer2 parameters point to.</para>
1507−</entry>
1508− </row><row><entry
1509− align="char">
1510−<para>When this function is called, the buffer1 parameter typically points to the
1511− start of the first undelivered TS packet within a circular buffer. The buffer2
1512− buffer parameter is normally NULL, except when the received TS packets have
1513− crossed the last address of the circular buffer and &#8221;wrapped&#8221; to the beginning
1514− of the buffer. In the latter case the buffer1 parameter would contain an address
1515− within the circular buffer, while the buffer2 parameter would contain the first
1516− address of the circular buffer.</para>
1517−</entry>
1518− </row><row><entry
1519− align="char">
1520−<para>The number of bytes delivered with this function (i.e. buffer1_length +
1521− buffer2_length) is usually equal to the value of callback_length parameter
1522− given in the set() function, with one exception: if a timeout occurs before
1523− receiving callback_length bytes of TS data, any undelivered packets are
1524− immediately delivered to the client by calling this function. The timeout
1525− duration is controlled by the set() function in the TS Feed API.</para>
1526−</entry>
1527− </row><row><entry
1528− align="char">
1529−<para>If a TS packet is received with errors that could not be fixed by the TS-level
1530− forward error correction (FEC), the Transport_error_indicator flag of the TS
1531− packet header should be set. The TS packet should not be discarded, as
1532− the error can possibly be corrected by a higher layer protocol. If the called
1533− party is slow in processing the callback, it is possible that the circular buffer
1534− eventually fills up. If this happens, the demux driver should discard any TS
1535− packets received while the buffer is full. The error should be indicated to the
1536− client on the next callback by setting the success parameter to the value of
1537− DMX_OVERRUN_ERROR.</para>
1538−</entry>
1539− </row><row><entry
1540− align="char">
1541−<para>The type of data returned to the callback can be selected by the new
1542− function int (*set_type) (struct dmx_ts_feed_s* feed, int type, dmx_ts_pes_t
1543− pes_type) which is part of the dmx_ts_feed_s struct (also cf. to the
1544− include file ost/demux.h) The type parameter decides if the raw TS packet
1545− (TS_PACKET) or just the payload (TS_PACKET&#8212;TS_PAYLOAD_ONLY)
1546− should be returned. If additionally the TS_DECODER bit is set the stream
1547− will also be sent to the hardware MPEG decoder. In this case, the second
1548− flag decides as what kind of data the stream should be interpreted. The
1549− possible choices are one of DMX_TS_PES_AUDIO, DMX_TS_PES_VIDEO,
1550− DMX_TS_PES_TELETEXT, DMX_TS_PES_SUBTITLE,
1551− DMX_TS_PES_PCR, or DMX_TS_PES_OTHER.</para>
1552−</entry>
1553− </row></tbody></tgroup></informaltable>
1554−<para>SYNOPSIS
1555−</para>
1556−<informaltable><tgroup cols="1"><tbody><row><entry
1557− align="char">
1558−<para>int dmx_ts_cb(__u8&#x22C6; buffer1, size_t buffer1_length,
1559− __u8&#x22C6; buffer2, size_t buffer2_length, dmx_ts_feed_t&#x22C6;
1560− source, dmx_success_t success);</para>
1561−</entry>
1562− </row></tbody></tgroup></informaltable>
1563−<para>PARAMETERS
1564−</para>
1565−<informaltable><tgroup cols="2"><tbody><row><entry
1566− align="char">
1567−<para>__u8* buffer1</para>
1568−</entry><entry
1569− align="char">
1570−<para>Pointer to the start of the filtered TS packets.</para>
1571−</entry>
1572− </row><row><entry
1573− align="char">
1574−<para>size_t buffer1_length</para>
1575−</entry><entry
1576− align="char">
1577−<para>Length of the TS data in buffer1.</para>
1578−</entry>
1579− </row><row><entry
1580− align="char">
1581−<para>__u8* buffer2</para>
1582−</entry><entry
1583− align="char">
1584−<para>Pointer to the tail of the filtered TS packets, or NULL.</para>
1585−</entry>
1586− </row><row><entry
1587− align="char">
1588−<para>size_t buffer2_length</para>
1589−</entry><entry
1590− align="char">
1591−<para>Length of the TS data in buffer2.</para>
1592−</entry>
1593− </row><row><entry
1594− align="char">
1595−<para>dmx_ts_feed_t*
1596− source</para>
1597−</entry><entry
1598− align="char">
1599−<para>Indicates which TS feed is the source of the callback.</para>
1600−</entry>
1601− </row><row><entry
1602− align="char">
1603−<para>dmx_success_t
1604− success</para>
1605−</entry><entry
1606− align="char">
1607−<para>Indicates if there was an error in TS reception.</para>
1608−</entry>
1609− </row></tbody></tgroup></informaltable>
1610−<para>RETURNS
1611−</para>
1612−<informaltable><tgroup cols="2"><tbody><row><entry
1613− align="char">
1614−<para>0</para>
1615−</entry><entry
1616− align="char">
1617−<para>Continue filtering.</para>
1618−</entry>
1619− </row><row><entry
1620− align="char">
1621−<para>-1</para>
1622−</entry><entry
1623− align="char">
1624−<para>Stop filtering - has the same effect as a call to
1625− stop_filtering() on the TS Feed API.</para>
1626−</entry>
1627− </row></tbody></tgroup></informaltable>
1628−
1629−</section><section
1630−role="subsection"><title>dmx_section_cb()</title>
1631−<para>DESCRIPTION
1632−</para>
1633−<informaltable><tgroup cols="1"><tbody><row><entry
1634− align="char">
1635−<para>This function, provided by the client of the demux API, is called from the
1636− demux code. The function is only called when filtering of sections has been
1637− enabled using the function start_filtering() of the section feed API. When the
1638− demux driver has received a complete section that matches at least one section
1639− filter, the client is notified via this callback function. Normally this function is
1640− called for each received section; however, it is also possible to deliver multiple
1641− sections with one callback, for example when the system load is high. If an
1642− error occurs while receiving a section, this function should be called with
1643− the corresponding error type set in the success field, whether or not there is
1644− data to deliver. The Section Feed implementation should maintain a circular
1645− buffer for received sections. However, this is not necessary if the Section Feed
1646− API is implemented as a client of the TS Feed API, because the TS Feed
1647− implementation then buffers the received data. The size of the circular buffer
1648− can be configured using the set() function in the Section Feed API. If there
1649− is no room in the circular buffer when a new section is received, the section
1650− must be discarded. If this happens, the value of the success parameter should
1651− be DMX_OVERRUN_ERROR on the next callback.</para>
1652−</entry>
1653− </row></tbody></tgroup></informaltable>
1654−<para>SYNOPSIS
1655−</para>
1656−<informaltable><tgroup cols="1"><tbody><row><entry
1657− align="char">
1658−<para>int dmx_section_cb(__u8&#x22C6; buffer1, size_t
1659− buffer1_length, __u8&#x22C6; buffer2, size_t
1660− buffer2_length, dmx_section_filter_t&#x22C6; source,
1661− dmx_success_t success);</para>
1662−</entry>
1663− </row></tbody></tgroup></informaltable>
1664−<para>PARAMETERS
1665−</para>
1666−<informaltable><tgroup cols="2"><tbody><row><entry
1667− align="char">
1668−<para>__u8* buffer1</para>
1669−</entry><entry
1670− align="char">
1671−<para>Pointer to the start of the filtered section, e.g. within the
1672− circular buffer of the demux driver.</para>
1673−</entry>
1674− </row><row><entry
1675− align="char">
1676−<para>size_t buffer1_length</para>
1677−</entry><entry
1678− align="char">
1679−<para>Length of the filtered section data in buffer1, including
1680− headers and CRC.</para>
1681−</entry>
1682− </row><row><entry
1683− align="char">
1684−<para>__u8* buffer2</para>
1685−</entry><entry
1686− align="char">
1687−<para>Pointer to the tail of the filtered section data, or NULL.
1688− Useful to handle the wrapping of a circular buffer.</para>
1689−</entry>
1690− </row><row><entry
1691− align="char">
1692−<para>size_t buffer2_length</para>
1693−</entry><entry
1694− align="char">
1695−<para>Length of the filtered section data in buffer2, including
1696− headers and CRC.</para>
1697−</entry>
1698− </row><row><entry
1699− align="char">
1700−<para>dmx_section_filter_t*
1701− filter</para>
1702−</entry><entry
1703− align="char">
1704−<para>Indicates the filter that triggered the callback.</para>
1705−</entry>
1706− </row><row><entry
1707− align="char">
1708−<para>dmx_success_t
1709− success</para>
1710−</entry><entry
1711− align="char">
1712−<para>Indicates if there was an error in section reception.</para>
1713−</entry>
1714− </row></tbody></tgroup></informaltable>
1715−<para>RETURNS
1716−</para>
1717−<informaltable><tgroup cols="2"><tbody><row><entry
1718− align="char">
1719−<para>0</para>
1720−</entry><entry
1721− align="char">
1722−<para>Continue filtering.</para>
1723−</entry>
1724− </row><row><entry
1725− align="char">
1726−<para>-1</para>
1727−</entry><entry
1728− align="char">
1729−<para>Stop filtering - has the same effect as a call to
1730− stop_filtering() on the Section Feed API.</para>
1731−</entry>
1732− </row></tbody></tgroup></informaltable>
1733− </section></section>
1734−<section id="ts_feed_api">
1735−<title>TS Feed API</title>
1736−<para>A TS feed is typically mapped to a hardware PID filter on the demux chip.
1737−Using this API, the client can set the filtering properties to start/stop filtering TS
1738−packets on a particular TS feed. The API is defined as an abstract interface of the type
1739−dmx_ts_feed_t.
1740−</para>
1741−<para>The functions that implement the interface should be defined static or module private. The
1742−client can get the handle of a TS feed API by calling the function allocate_ts_feed() in the
1743−demux API.
1744−</para>
1745−
1746−<section
1747−role="subsection"><title>set()</title>
1748−<para>DESCRIPTION
1749−</para>
1750−<informaltable><tgroup cols="1"><tbody><row><entry
1751− align="char">
1752−<para>This function sets the parameters of a TS feed. Any filtering in progress on the
1753− TS feed must be stopped before calling this function.</para>
1754−</entry>
1755− </row></tbody></tgroup></informaltable>
1756−<para>SYNOPSIS
1757−</para>
1758−<informaltable><tgroup cols="1"><tbody><row><entry
1759− align="char">
1760−<para>int set ( dmx_ts_feed_t&#x22C6; feed, __u16 pid, size_t
1761− callback_length, size_t circular_buffer_size, int
1762− descramble, struct timespec timeout);</para>
1763−</entry>
1764− </row></tbody></tgroup></informaltable>
1765−<para>PARAMETERS
1766−</para>
1767−<informaltable><tgroup cols="2"><tbody><row><entry
1768− align="char">
1769−<para>dmx_ts_feed_t* feed</para>
1770−</entry><entry
1771− align="char">
1772−<para>Pointer to the TS feed API and instance data.</para>
1773−</entry>
1774− </row><row><entry
1775− align="char">
1776−<para>__u16 pid</para>
1777−</entry><entry
1778− align="char">
1779−<para>PID value to filter. Only the TS packets carrying the
1780− specified PID will be passed to the API client.</para>
1781−</entry>
1782− </row><row><entry
1783− align="char">
1784−<para>size_t
1785− callback_length</para>
1786−</entry><entry
1787− align="char">
1788−<para>Number of bytes to deliver with each call to the
1789− dmx_ts_cb() callback function. The value of this
1790− parameter should be a multiple of 188.</para>
1791−</entry>
1792− </row><row><entry
1793− align="char">
1794−<para>size_t
1795− circular_buffer_size</para>
1796−</entry><entry
1797− align="char">
1798−<para>Size of the circular buffer for the filtered TS packets.</para>
1799−</entry>
1800− </row><row><entry
1801− align="char">
1802−<para>int descramble</para>
1803−</entry><entry
1804− align="char">
1805−<para>If non-zero, descramble the filtered TS packets.</para>
1806−</entry>
1807− </row><row><entry
1808− align="char">
1809−<para>struct timespec
1810− timeout</para>
1811−</entry><entry
1812− align="char">
1813−<para>Maximum time to wait before delivering received TS
1814− packets to the client.</para>
1815−</entry>
1816− </row></tbody></tgroup></informaltable>
1817−<para>RETURNS
1818−</para>
1819−<informaltable><tgroup cols="2"><tbody><row><entry
1820− align="char">
1821−<para>0</para>
1822−</entry><entry
1823− align="char">
1824−<para>The function was completed without errors.</para>
1825−</entry>
1826− </row><row><entry
1827− align="char">
1828−<para>-ENOMEM</para>
1829−</entry><entry
1830− align="char">
1831−<para>Not enough memory for the requested buffer size.</para>
1832−</entry>
1833− </row><row><entry
1834− align="char">
1835−<para>-ENOSYS</para>
1836−</entry><entry
1837− align="char">
1838−<para>No descrambling facility available for TS.</para>
1839−</entry>
1840− </row><row><entry
1841− align="char">
1842−<para>-EINVAL</para>
1843−</entry><entry
1844− align="char">
1845−<para>Bad parameter.</para>
1846−</entry>
1847− </row></tbody></tgroup></informaltable>
1848−
1849−</section><section
1850−role="subsection"><title>start_filtering()</title>
1851−<para>DESCRIPTION
1852−</para>
1853−<informaltable><tgroup cols="1"><tbody><row><entry
1854− align="char">
1855−<para>Starts filtering TS packets on this TS feed, according to its settings. The PID
1856− value to filter can be set by the API client. All matching TS packets are
1857− delivered asynchronously to the client, using the callback function registered
1858− with allocate_ts_feed().</para>
1859−</entry>
1860− </row></tbody></tgroup></informaltable>
1861−<para>SYNOPSIS
1862−</para>
1863−<informaltable><tgroup cols="1"><tbody><row><entry
1864− align="char">
1865−<para>int start_filtering(dmx_ts_feed_t&#x22C6; feed);</para>
1866−</entry>
1867− </row></tbody></tgroup></informaltable>
1868−<para>PARAMETERS
1869−</para>
1870−<informaltable><tgroup cols="2"><tbody><row><entry
1871− align="char">
1872−<para>dmx_ts_feed_t* feed</para>
1873−</entry><entry
1874− align="char">
1875−<para>Pointer to the TS feed API and instance data.</para>
1876−</entry>
1877− </row></tbody></tgroup></informaltable>
1878−<para>RETURNS
1879−</para>
1880−<informaltable><tgroup cols="2"><tbody><row><entry
1881− align="char">
1882−<para>0</para>
1883−</entry><entry
1884− align="char">
1885−<para>The function was completed without errors.</para>
1886−</entry>
1887− </row><row><entry
1888− align="char">
1889−<para>-EINVAL</para>
1890−</entry><entry
1891− align="char">
1892−<para>Bad parameter.</para>
1893−</entry>
1894− </row></tbody></tgroup></informaltable>
1895−
1896−</section><section
1897−role="subsection"><title>stop_filtering()</title>
1898−<para>DESCRIPTION
1899−</para>
1900−<informaltable><tgroup cols="1"><tbody><row><entry
1901− align="char">
1902−<para>Stops filtering TS packets on this TS feed.</para>
1903−</entry>
1904− </row></tbody></tgroup></informaltable>
1905−<para>SYNOPSIS
1906−</para>
1907−<informaltable><tgroup cols="1"><tbody><row><entry
1908− align="char">
1909−<para>int stop_filtering(dmx_ts_feed_t&#x22C6; feed);</para>
1910−</entry>
1911− </row></tbody></tgroup></informaltable>
1912−<para>PARAMETERS
1913−</para>
1914−<informaltable><tgroup cols="2"><tbody><row><entry
1915− align="char">
1916−<para>dmx_ts_feed_t* feed</para>
1917−</entry><entry
1918− align="char">
1919−<para>Pointer to the TS feed API and instance data.</para>
1920−</entry>
1921− </row></tbody></tgroup></informaltable>
1922−<para>RETURNS
1923−</para>
1924−<informaltable><tgroup cols="2"><tbody><row><entry
1925− align="char">
1926−<para>0</para>
1927−</entry><entry
1928− align="char">
1929−<para>The function was completed without errors.</para>
1930−</entry>
1931− </row><row><entry
1932− align="char">
1933−<para>-EINVAL</para>
1934−</entry><entry
1935− align="char">
1936−<para>Bad parameter.</para>
1937−</entry>
1938− </row></tbody></tgroup></informaltable>
1939− </section></section>
1940−<section id="section_feed_api">
1941−<title>Section Feed API</title>
1942−<para>A section feed is a resource consisting of a PID filter and a set of section filters. Using this
1943−API, the client can set the properties of a section feed and to start/stop filtering. The API is
1944−defined as an abstract interface of the type dmx_section_feed_t. The functions that implement
1945−the interface should be defined static or module private. The client can get the handle of
1946−a section feed API by calling the function allocate_section_feed() in the demux
1947−API.
1948−</para>
1949−<para>On demux platforms that provide section filtering in hardware, the Section Feed API
1950−implementation provides a software wrapper for the demux hardware. Other platforms may
1951−support only PID filtering in hardware, requiring that TS packets are converted to sections in
1952−software. In the latter case the Section Feed API implementation can be a client of the TS
1953−Feed API.
1954−</para>
1955−
1956−</section>
1957−<section id="kdapi_set">
1958−<title>set()</title>
1959−<para>DESCRIPTION
1960−</para>
1961−<informaltable><tgroup cols="1"><tbody><row><entry
1962− align="char">
1963−<para>This function sets the parameters of a section feed. Any filtering in progress on
1964− the section feed must be stopped before calling this function. If descrambling
1965− is enabled, the payload_scrambling_control and address_scrambling_control
1966− fields of received DVB datagram sections should be observed. If either one is
1967− non-zero, the section should be descrambled either in hardware or using the
1968− functions descramble_mac_address() and descramble_section_payload() of the
1969− demux API. Note that according to the MPEG-2 Systems specification, only
1970− the payloads of private sections can be scrambled while the rest of the section
1971− data must be sent in the clear.</para>
1972−</entry>
1973− </row></tbody></tgroup></informaltable>
1974−<para>SYNOPSIS
1975−</para>
1976−<informaltable><tgroup cols="1"><tbody><row><entry
1977− align="char">
1978−<para>int set(dmx_section_feed_t&#x22C6; feed, __u16 pid, size_t
1979− circular_buffer_size, int descramble, int
1980− check_crc);</para>
1981−</entry>
1982− </row></tbody></tgroup></informaltable>
1983−<para>PARAMETERS
1984−</para>
1985−<informaltable><tgroup cols="2"><tbody><row><entry
1986− align="char">
1987−<para>dmx_section_feed_t*
1988− feed</para>
1989−</entry><entry
1990− align="char">
1991−<para>Pointer to the section feed API and instance data.</para>
1992−</entry>
1993− </row><row><entry
1994− align="char">
1995−<para>__u16 pid</para>
1996−</entry><entry
1997− align="char">
1998−<para>PID value to filter; only the TS packets carrying the
1999− specified PID will be accepted.</para>
2000−</entry>
2001− </row><row><entry
2002− align="char">
2003−<para>size_t
2004− circular_buffer_size</para>
2005−</entry><entry
2006− align="char">
2007−<para>Size of the circular buffer for filtered sections.</para>
2008−</entry>
2009− </row><row><entry
2010− align="char">
2011−<para>int descramble</para>
2012−</entry><entry
2013− align="char">
2014−<para>If non-zero, descramble any sections that are scrambled.</para>
2015−</entry>
2016− </row><row><entry
2017− align="char">
2018−<para>int check_crc</para>
2019−</entry><entry
2020− align="char">
2021−<para>If non-zero, check the CRC values of filtered sections.</para>
2022−</entry>
2023− </row></tbody></tgroup></informaltable>
2024−<para>RETURNS
2025−</para>
2026−<informaltable><tgroup cols="2"><tbody><row><entry
2027− align="char">
2028−<para>0</para>
2029−</entry><entry
2030− align="char">
2031−<para>The function was completed without errors.</para>
2032−</entry>
2033− </row><row><entry
2034− align="char">
2035−<para>-ENOMEM</para>
2036−</entry><entry
2037− align="char">
2038−<para>Not enough memory for the requested buffer size.</para>
2039−</entry>
2040− </row><row><entry
2041− align="char">
2042−<para>-ENOSYS</para>
2043−</entry><entry
2044− align="char">
2045−<para>No descrambling facility available for sections.</para>
2046−</entry>
2047− </row><row><entry
2048− align="char">
2049−<para>-EINVAL</para>
2050−</entry><entry
2051− align="char">
2052−<para>Bad parameters.</para>
2053−</entry>
2054− </row></tbody></tgroup></informaltable>
2055−
2056−</section><section
2057−role="subsection"><title>allocate_filter()</title>
2058−<para>DESCRIPTION
2059−</para>
2060−<informaltable><tgroup cols="1"><tbody><row><entry
2061− align="char">
2062−<para>This function is used to allocate a section filter on the demux. It should only be
2063− called when no filtering is in progress on this section feed. If a filter cannot be
2064− allocated, the function fails with -ENOSPC. See in section ?? for the format of
2065− the section filter.</para>
2066−</entry>
2067− </row><row><entry
2068− align="char">
2069−<para>The bitfields filter_mask and filter_value should only be modified when no
2070− filtering is in progress on this section feed. filter_mask controls which bits of
2071− filter_value are compared with the section headers/payload. On a binary value
2072− of 1 in filter_mask, the corresponding bits are compared. The filter only accepts
2073− sections that are equal to filter_value in all the tested bit positions. Any changes
2074− to the values of filter_mask and filter_value are guaranteed to take effect only
2075− when the start_filtering() function is called next time. The parent pointer in
2076− the struct is initialized by the API implementation to the value of the feed
2077− parameter. The priv pointer is not used by the API implementation, and can
2078− thus be freely utilized by the caller of this function. Any data pointed to by the
2079− priv pointer is available to the recipient of the dmx_section_cb() function call.</para>
2080−</entry>
2081− </row><row><entry
2082− align="char">
2083−<para>While the maximum section filter length (DMX_MAX_FILTER_SIZE) is
2084− currently set at 16 bytes, hardware filters of that size are not available on all
2085− platforms. Therefore, section filtering will often take place first in hardware,
2086− followed by filtering in software for the header bytes that were not covered
2087− by a hardware filter. The filter_mask field can be checked to determine how
2088− many bytes of the section filter are actually used, and if the hardware filter will
2089− suffice. Additionally, software-only section filters can optionally be allocated
2090− to clients when all hardware section filters are in use. Note that on most demux
2091− hardware it is not possible to filter on the section_length field of the section
2092− header &#8211; thus this field is ignored, even though it is included in filter_value and
2093− filter_mask fields.</para>
2094−</entry>
2095− </row></tbody></tgroup></informaltable>
2096−<para>SYNOPSIS
2097−</para>
2098−<informaltable><tgroup cols="1"><tbody><row><entry
2099− align="char">
2100−<para>int allocate_filter(dmx_section_feed_t&#x22C6; feed,
2101− dmx_section_filter_t&#x22C6;&#x22C6; filter);</para>
2102−</entry>
2103− </row></tbody></tgroup></informaltable>
2104−<para>PARAMETERS
2105−</para>
2106−<informaltable><tgroup cols="2"><tbody><row><entry
2107− align="char">
2108−<para>dmx_section_feed_t*
2109− feed</para>
2110−</entry><entry
2111− align="char">
2112−<para>Pointer to the section feed API and instance data.</para>
2113−</entry>
2114− </row><row><entry
2115− align="char">
2116−<para>dmx_section_filter_t**
2117− filter</para>
2118−</entry><entry
2119− align="char">
2120−<para>Pointer to the allocated filter.</para>
2121−</entry>
2122− </row></tbody></tgroup></informaltable>
2123−<para>RETURNS
2124−</para>
2125−<informaltable><tgroup cols="2"><tbody><row><entry
2126− align="char">
2127−<para>0</para>
2128−</entry><entry
2129− align="char">
2130−<para>The function was completed without errors.</para>
2131−</entry>
2132− </row><row><entry
2133− align="char">
2134−<para>-ENOSPC</para>
2135−</entry><entry
2136− align="char">
2137−<para>No filters of given type and length available.</para>
2138−</entry>
2139− </row><row><entry
2140− align="char">
2141−<para>-EINVAL</para>
2142−</entry><entry
2143− align="char">
2144−<para>Bad parameters.</para>
2145−</entry>
2146− </row></tbody></tgroup></informaltable>
2147−
2148−</section><section
2149−role="subsection"><title>release_filter()</title>
2150−<para>DESCRIPTION
2151−</para>
2152−<informaltable><tgroup cols="1"><tbody><row><entry
2153− align="char">
2154−<para>This function releases all the resources of a previously allocated section filter.
2155− The function should not be called while filtering is in progress on this section
2156− feed. After calling this function, the caller should not try to dereference the
2157− filter pointer.</para>
2158−</entry>
2159− </row></tbody></tgroup></informaltable>
2160−<para>SYNOPSIS
2161−</para>
2162−<informaltable><tgroup cols="1"><tbody><row><entry
2163− align="char">
2164−<para>int release_filter ( dmx_section_feed_t&#x22C6; feed,
2165− dmx_section_filter_t&#x22C6; filter);</para>
2166−</entry>
2167− </row></tbody></tgroup></informaltable>
2168−<para>PARAMETERS
2169−</para>
2170−<informaltable><tgroup cols="2"><tbody><row><entry
2171− align="char">
2172−<para>dmx_section_feed_t*
2173− feed</para>
2174−</entry><entry
2175− align="char">
2176−<para>Pointer to the section feed API and instance data.</para>
2177−</entry>
2178− </row><row><entry
2179− align="char">
2180−<para>dmx_section_filter_t*
2181− filter</para>
2182−</entry><entry
2183− align="char">
2184−<para>I/O Pointer to the instance data of a section filter.</para>
2185−</entry>
2186− </row></tbody></tgroup></informaltable>
2187−<para>RETURNS
2188−</para>
2189−<informaltable><tgroup cols="2"><tbody><row><entry
2190− align="char">
2191−<para>0</para>
2192−</entry><entry
2193− align="char">
2194−<para>The function was completed without errors.</para>
2195−</entry>
2196− </row><row><entry
2197− align="char">
2198−<para>-ENODEV</para>
2199−</entry><entry
2200− align="char">
2201−<para>No such filter allocated.</para>
2202−</entry>
2203− </row><row><entry
2204− align="char">
2205−<para>-EINVAL</para>
2206−</entry><entry
2207− align="char">
2208−<para>Bad parameter.</para>
2209−</entry>
2210− </row></tbody></tgroup></informaltable>
2211−
2212−</section><section
2213−role="subsection"><title>start_filtering()</title>
2214−<para>DESCRIPTION
2215−</para>
2216−<informaltable><tgroup cols="1"><tbody><row><entry
2217− align="char">
2218−<para>Starts filtering sections on this section feed, according to its settings. Sections
2219− are first filtered based on their PID and then matched with the section
2220− filters allocated for this feed. If the section matches the PID filter and
2221− at least one section filter, it is delivered to the API client. The section
2222− is delivered asynchronously using the callback function registered with
2223− allocate_section_feed().</para>
2224−</entry>
2225− </row></tbody></tgroup></informaltable>
2226−<para>SYNOPSIS
2227−</para>
2228−<informaltable><tgroup cols="1"><tbody><row><entry
2229− align="char">
2230−<para>int start_filtering ( dmx_section_feed_t&#x22C6; feed );</para>
2231−</entry>
2232− </row></tbody></tgroup></informaltable>
2233−<para>PARAMETERS
2234−</para>
2235−<informaltable><tgroup cols="2"><tbody><row><entry
2236− align="char">
2237−<para>dmx_section_feed_t*
2238− feed</para>
2239−</entry><entry
2240− align="char">
2241−<para>Pointer to the section feed API and instance data.</para>
2242−</entry>
2243− </row></tbody></tgroup></informaltable>
2244−<para>RETURNS
2245−</para>
2246−<informaltable><tgroup cols="2"><tbody><row><entry
2247− align="char">
2248−<para>0</para>
2249−</entry><entry
2250− align="char">
2251−<para>The function was completed without errors.</para>
2252−</entry>
2253− </row><row><entry
2254− align="char">
2255−<para>-EINVAL</para>
2256−</entry><entry
2257− align="char">
2258−<para>Bad parameter.</para>
2259−</entry>
2260− </row></tbody></tgroup></informaltable>
2261−
2262−</section><section
2263−role="subsection"><title>stop_filtering()</title>
2264−<para>DESCRIPTION
2265−</para>
2266−<informaltable><tgroup cols="1"><tbody><row><entry
2267− align="char">
2268−<para>Stops filtering sections on this section feed. Note that any changes to the
2269− filtering parameters (filter_value, filter_mask, etc.) should only be made when
2270− filtering is stopped.</para>
2271−</entry>
2272− </row></tbody></tgroup></informaltable>
2273−<para>SYNOPSIS
2274−</para>
2275−<informaltable><tgroup cols="1"><tbody><row><entry
2276− align="char">
2277−<para>int stop_filtering ( dmx_section_feed_t&#x22C6; feed );</para>
2278−</entry>
2279− </row></tbody></tgroup></informaltable>
2280−<para>PARAMETERS
2281−</para>
2282−<informaltable><tgroup cols="2"><tbody><row><entry
2283− align="char">
2284−<para>dmx_section_feed_t*
2285− feed</para>
2286−</entry><entry
2287− align="char">
2288−<para>Pointer to the section feed API and instance data.</para>
2289−</entry>
2290− </row></tbody></tgroup></informaltable>
2291−<para>RETURNS
2292−</para>
2293−<informaltable><tgroup cols="2"><tbody><row><entry
2294− align="char">
2295−<para>0</para>
2296−</entry><entry
2297− align="char">
2298−<para>The function was completed without errors.</para>
2299−</entry>
2300− </row><row><entry
2301− align="char">
2302−<para>-EINVAL</para>
2303−</entry><entry
2304− align="char">
2305−<para>Bad parameter.</para>
2306−</entry>
2307− </row></tbody></tgroup></informaltable>
2308−
2309−</section>
Documentation/DocBook/media/v4l/biblio.xml+18−0
@@ -177,6 +177,24 @@ Signal - NTSC for Studio Applications"</title> · 176 unmodified lines
177177 1125-Line High-Definition Production"</title>
178178 </biblioentry>
179179
180+ <biblioentry id="smpte431">
181+ <abbrev>SMPTE&nbsp;RP&nbsp;431-2</abbrev>
182+ <authorgroup>
183+ <corpauthor>Society of Motion Picture and Television Engineers
184+(<ulink url="http://www.smpte.org">http://www.smpte.org</ulink>)</corpauthor>
185+ </authorgroup>
186+ <title>SMPTE RP 431-2:2011 "D-Cinema Quality - Reference Projector and Environment"</title>
187+ </biblioentry>
188+
189+ <biblioentry id="smpte2084">
190+ <abbrev>SMPTE&nbsp;ST&nbsp;2084</abbrev>
191+ <authorgroup>
192+ <corpauthor>Society of Motion Picture and Television Engineers
193+(<ulink url="http://www.smpte.org">http://www.smpte.org</ulink>)</corpauthor>
194+ </authorgroup>
195+ <title>SMPTE ST 2084:2014 "High Dynamic Range Electro-Optical Transfer Function of Master Reference Displays"</title>
196+ </biblioentry>
197+
180198 <biblioentry id="srgb">
181199 <abbrev>sRGB</abbrev>
182200 <authorgroup>
Documentation/DocBook/media/v4l/compat.xml+20−0
@@ -2591,6 +2591,26 @@ and &v4l2-mbus-framefmt;. · 2590 unmodified lines
25912591 </orderedlist>
25922592 </section>
25932593
2594+ <section>
2595+ <title>V4L2 in Linux 4.4</title>
2596+ <orderedlist>
2597+ <listitem>
2598+ <para>Renamed <constant>V4L2_TUNER_ADC</constant> to
2599+<constant>V4L2_TUNER_SDR</constant>. The use of
2600+<constant>V4L2_TUNER_ADC</constant> is deprecated now.
2601+ </para>
2602+ </listitem>
2603+ <listitem>
2604+ <para>Added <constant>V4L2_CID_RF_TUNER_RF_GAIN</constant>
2605+RF Tuner control.</para>
2606+ </listitem>
2607+ <listitem>
2608+ <para>Added transmitter support for Software Defined Radio (SDR)
2609+Interface.</para>
2610+ </listitem>
2611+ </orderedlist>
2612+ </section>
2613+
25942614 <section id="other">
25952615 <title>Relation of V4L2 to other Linux multimedia APIs</title>
25962616
Documentation/DocBook/media/v4l/controls.xml+14−0
@@ -5417,6 +5417,18 @@ set. Unit is in Hz. The range and step are driver-specific.</entry> · 5416 unmodified lines
54175417 <row>
54185418 <entry spanname="descr">Enables/disables IF automatic gain control (AGC)</entry>
54195419 </row>
5420+ <row>
5421+ <entry spanname="id"><constant>V4L2_CID_RF_TUNER_RF_GAIN</constant>&nbsp;</entry>
5422+ <entry>integer</entry>
5423+ </row>
5424+ <row>
5425+ <entry spanname="descr">The RF amplifier is the very first
5426+amplifier on the receiver signal path, just right after the antenna input.
5427+The difference between the LNA gain and the RF gain in this document is that
5428+the LNA gain is integrated in the tuner chip while the RF gain is a separate
5429+chip. There may be both RF and LNA gain controls in the same device.
5430+The range and step are driver-specific.</entry>
5431+ </row>
54205432 <row>
54215433 <entry spanname="id"><constant>V4L2_CID_RF_TUNER_LNA_GAIN</constant>&nbsp;</entry>
54225434 <entry>integer</entry>
@@ -5425,6 +5437,8 @@ set. Unit is in Hz. The range and step are driver-specific.</entry> · 2 unmodified lines
54255437 <entry spanname="descr">LNA (low noise amplifier) gain is first
54265438 gain stage on the RF tuner signal path. It is located very close to tuner
54275439 antenna input. Used when <constant>V4L2_CID_RF_TUNER_LNA_GAIN_AUTO</constant> is not set.
5440+See <constant>V4L2_CID_RF_TUNER_RF_GAIN</constant> to understand how RF gain
5441+and LNA gain differs from the each others.
54285442 The range and step are driver-specific.</entry>
54295443 </row>
54305444 <row>
Documentation/DocBook/media/v4l/dev-sdr.xml+22−10
@@ -28,6 +28,16 @@ Devices supporting the SDR receiver interface set the · 27 unmodified lines
2828 <structfield>capabilities</structfield> field of &v4l2-capability;
2929 returned by the &VIDIOC-QUERYCAP; ioctl. That flag means the device has an
3030 Analog to Digital Converter (ADC), which is a mandatory element for the SDR receiver.
31+ </para>
32+ <para>
33+Devices supporting the SDR transmitter interface set the
34+<constant>V4L2_CAP_SDR_OUTPUT</constant> and
35+<constant>V4L2_CAP_MODULATOR</constant> flag in the
36+<structfield>capabilities</structfield> field of &v4l2-capability;
37+returned by the &VIDIOC-QUERYCAP; ioctl. That flag means the device has an
38+Digital to Analog Converter (DAC), which is a mandatory element for the SDR transmitter.
39+ </para>
40+ <para>
3141 At least one of the read/write, streaming or asynchronous I/O methods must
3242 be supported.
3343 </para>
@@ -39,15 +49,16 @@ be supported. · 5 unmodified lines
3949 <para>
4050 SDR devices can support <link linkend="control">controls</link>, and must
4151 support the <link linkend="tuner">tuner</link> ioctls. Tuner ioctls are used
42−for setting the ADC sampling rate (sampling frequency) and the possible RF tuner
43−frequency.
52+for setting the ADC/DAC sampling rate (sampling frequency) and the possible
53+radio frequency (RF).
4454 </para>
4555
4656 <para>
47−The <constant>V4L2_TUNER_ADC</constant> tuner type is used for ADC tuners, and
48−the <constant>V4L2_TUNER_RF</constant> tuner type is used for RF tuners. The
49−tuner index of the RF tuner (if any) must always follow the ADC tuner index.
50−Normally the ADC tuner is #0 and the RF tuner is #1.
57+The <constant>V4L2_TUNER_SDR</constant> tuner type is used for setting SDR
58+device ADC/DAC frequency, and the <constant>V4L2_TUNER_RF</constant>
59+tuner type is used for setting radio frequency.
60+The tuner index of the RF tuner (if any) must always follow the SDR tuner index.
61+Normally the SDR tuner is #0 and the RF tuner is #1.
5162 </para>
5263
5364 <para>
@@ -59,9 +70,9 @@ The &VIDIOC-S-HW-FREQ-SEEK; ioctl is not supported. · 5 unmodified lines
5970 <title>Data Format Negotiation</title>
6071
6172 <para>
62−The SDR capture device uses the <link linkend="format">format</link> ioctls to
63−select the capture format. Both the sampling resolution and the data streaming
64−format are bound to that selectable format. In addition to the basic
73+The SDR device uses the <link linkend="format">format</link> ioctls to
74+select the capture and output format. Both the sampling resolution and the data
75+streaming format are bound to that selectable format. In addition to the basic
6576 <link linkend="format">format</link> ioctls, the &VIDIOC-ENUM-FMT; ioctl
6677 must be supported as well.
6778 </para>
@@ -69,7 +80,8 @@ must be supported as well. · 1 unmodified line
6980 <para>
7081 To use the <link linkend="format">format</link> ioctls applications set the
7182 <structfield>type</structfield> field of a &v4l2-format; to
72−<constant>V4L2_BUF_TYPE_SDR_CAPTURE</constant> and use the &v4l2-sdr-format;
83+<constant>V4L2_BUF_TYPE_SDR_CAPTURE</constant> or
84+<constant>V4L2_BUF_TYPE_SDR_OUTPUT</constant> and use the &v4l2-sdr-format;
7385 <structfield>sdr</structfield> member of the <structfield>fmt</structfield>
7486 union as needed per the desired operation.
7587 Currently there is two fields, <structfield>pixelformat</structfield> and
Documentation/DocBook/media/v4l/io.xml+8−2
@@ -1006,8 +1006,14 @@ must set this to 0.</entry> · 1005 unmodified lines
10061006 <row>
10071007 <entry><constant>V4L2_BUF_TYPE_SDR_CAPTURE</constant></entry>
10081008 <entry>11</entry>
1009− <entry>Buffer for Software Defined Radio (SDR), see <xref
1010− linkend="sdr" />.</entry>
1009+ <entry>Buffer for Software Defined Radio (SDR) capture stream, see
1010+ <xref linkend="sdr" />.</entry>
1011+ </row>
1012+ <row>
1013+ <entry><constant>V4L2_BUF_TYPE_SDR_OUTPUT</constant></entry>
1014+ <entry>12</entry>
1015+ <entry>Buffer for Software Defined Radio (SDR) output stream, see
1016+ <xref linkend="sdr" />.</entry>
10111017 </row>
10121018 </tbody>
10131019 </tgroup>
Documentation/DocBook/media/v4l/pixfmt.xml+110−1
@@ -539,6 +539,10 @@ colorspaces except for BT.2020 which uses limited range R'G'B' quantization.</pa · 538 unmodified lines
539539 <entry><constant>V4L2_COLORSPACE_BT2020</constant></entry>
540540 <entry>See <xref linkend="col-bt2020" />.</entry>
541541 </row>
542+ <row>
543+ <entry><constant>V4L2_COLORSPACE_DCI_P3</constant></entry>
544+ <entry>See <xref linkend="col-dcip3" />.</entry>
545+ </row>
542546 <row>
543547 <entry><constant>V4L2_COLORSPACE_SMPTE240M</constant></entry>
544548 <entry>See <xref linkend="col-smpte-240m" />.</entry>
@@ -601,6 +605,14 @@ colorspaces except for BT.2020 which uses limited range R'G'B' quantization.</pa · 56 unmodified lines
601605 <entry><constant>V4L2_XFER_FUNC_NONE</constant></entry>
602606 <entry>Do not use a transfer function (i.e. use linear RGB values).</entry>
603607 </row>
608+ <row>
609+ <entry><constant>V4L2_XFER_FUNC_DCI_P3</constant></entry>
610+ <entry>Use the DCI-P3 transfer function.</entry>
611+ </row>
612+ <row>
613+ <entry><constant>V4L2_XFER_FUNC_SMPTE2084</constant></entry>
614+ <entry>Use the SMPTE 2084 transfer function.</entry>
615+ </row>
604616 </tbody>
605617 </tgroup>
606618 </table>
@@ -1154,6 +1166,68 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range · 547 unmodified lines
11541166 clamped to the range [-0.5&hellip;0.5]. The Yc'CbcCrc quantization is limited range.</para>
11551167 </section>
11561168
1169+ <section id="col-dcip3">
1170+ <title>Colorspace DCI-P3 (<constant>V4L2_COLORSPACE_DCI_P3</constant>)</title>
1171+ <para>The <xref linkend="smpte431" /> standard defines the colorspace used by cinema
1172+projectors that use the DCI-P3 colorspace.
1173+The default transfer function is <constant>V4L2_XFER_FUNC_DCI_P3</constant>.
1174+The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_709</constant>. Note that this
1175+colorspace does not specify a Y'CbCr encoding since it is not meant to be encoded
1176+to Y'CbCr. So this default Y'CbCr encoding was picked because it is the HDTV
1177+encoding. The default Y'CbCr quantization is limited range. The chromaticities of
1178+the primary colors and the white reference are:</para>
1179+ <table frame="none">
1180+ <title>DCI-P3 Chromaticities</title>
1181+ <tgroup cols="3" align="left">
1182+ &cs-str;
1183+ <thead>
1184+ <row>
1185+ <entry>Color</entry>
1186+ <entry>x</entry>
1187+ <entry>y</entry>
1188+ </row>
1189+ </thead>
1190+ <tbody valign="top">
1191+ <row>
1192+ <entry>Red</entry>
1193+ <entry>0.6800</entry>
1194+ <entry>0.3200</entry>
1195+ </row>
1196+ <row>
1197+ <entry>Green</entry>
1198+ <entry>0.2650</entry>
1199+ <entry>0.6900</entry>
1200+ </row>
1201+ <row>
1202+ <entry>Blue</entry>
1203+ <entry>0.1500</entry>
1204+ <entry>0.0600</entry>
1205+ </row>
1206+ <row>
1207+ <entry>White Reference</entry>
1208+ <entry>0.3140</entry>
1209+ <entry>0.3510</entry>
1210+ </row>
1211+ </tbody>
1212+ </tgroup>
1213+ </table>
1214+ <variablelist>
1215+ <varlistentry>
1216+ <term>Transfer function:</term>
1217+ <listitem>
1218+ <para>L' = L<superscript>1/2.6</superscript></para>
1219+ </listitem>
1220+ </varlistentry>
1221+ <varlistentry>
1222+ <term>Inverse Transfer function:</term>
1223+ <listitem>
1224+ <para>L = L'<superscript>2.6</superscript></para>
1225+ </listitem>
1226+ </varlistentry>
1227+ </variablelist>
1228+ <para>Y'CbCr encoding is not specified. V4L2 defaults to Rec. 709.</para>
1229+ </section>
1230+
11571231 <section id="col-smpte-240m">
11581232 <title>Colorspace SMPTE 240M (<constant>V4L2_COLORSPACE_SMPTE240M</constant>)</title>
11591233 <para>The <xref linkend="smpte240m" /> standard was an interim standard used during
@@ -1402,6 +1476,41 @@ and <constant>V4L2_QUANTIZATION_FULL_RANGE</constant>.</para> · 242 unmodified lines
14021476
14031477 </section>
14041478
1479+ <section>
1480+ <title>Detailed Transfer Function Descriptions</title>
1481+ <section id="xf-smpte-2084">
1482+ <title>Transfer Function SMPTE 2084 (<constant>V4L2_XFER_FUNC_SMPTE2084</constant>)</title>
1483+ <para>The <xref linkend="smpte2084" /> standard defines the transfer function used by
1484+High Dynamic Range content.</para>
1485+ <variablelist>
1486+ <varlistentry>
1487+ <term>Constants:</term>
1488+ <listitem>
1489+ <para>m1 = (2610 / 4096) / 4</para>
1490+ <para>m2 = (2523 / 4096) * 128</para>
1491+ <para>c1 = 3424 / 4096</para>
1492+ <para>c2 = (2413 / 4096) * 32</para>
1493+ <para>c3 = (2392 / 4096) * 32</para>
1494+ </listitem>
1495+ </varlistentry>
1496+ <varlistentry>
1497+ <term>Transfer function:</term>
1498+ <listitem>
1499+ <para>L' = ((c1 + c2 * L<superscript>m1</superscript>) / (1 + c3 * L<superscript>m1</superscript>))<superscript>m2</superscript></para>
1500+ </listitem>
1501+ </varlistentry>
1502+ </variablelist>
1503+ <variablelist>
1504+ <varlistentry>
1505+ <term>Inverse Transfer function:</term>
1506+ <listitem>
1507+ <para>L = (max(L'<superscript>1/m2</superscript> - c1, 0) / (c2 - c3 * L'<superscript>1/m2</superscript>))<superscript>1/m1</superscript></para>
1508+ </listitem>
1509+ </varlistentry>
1510+ </variablelist>
1511+ </section>
1512+ </section>
1513+
14051514 <section id="pixfmt-indexed">
14061515 <title>Indexed Format</title>
14071516
@@ -1623,7 +1732,7 @@ extended control <constant>V4L2_CID_MPEG_STREAM_TYPE</constant>, see · 215 unmodified lines
16231732 <section id="sdr-formats">
16241733 <title>SDR Formats</title>
16251734
1626− <para>These formats are used for <link linkend="sdr">SDR Capture</link>
1735+ <para>These formats are used for <link linkend="sdr">SDR</link>
16271736 interface only.</para>
16281737
16291738 &sub-sdr-cu08;
Documentation/DocBook/media/v4l/v4l2.xml+11−2
@@ -151,9 +151,18 @@ Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab, · 150 unmodified lines
151151 structs, ioctls) must be noted in more detail in the history chapter
152152 (compat.xml), along with the possible impact on existing drivers and
153153 applications. -->
154+ <revision>
155+ <revnumber>4.4</revnumber>
156+ <date>2015-05-26</date>
157+ <authorinitials>ap</authorinitials>
158+ <revremark>Renamed V4L2_TUNER_ADC to V4L2_TUNER_SDR.
159+Added V4L2_CID_RF_TUNER_RF_GAIN control.
160+Added transmitter support for Software Defined Radio (SDR) Interface.
161+ </revremark>
162+ </revision>
154163
155164 <revision>
156− <revnumber>3.21</revnumber>
165+ <revnumber>4.1</revnumber>
157166 <date>2015-02-13</date>
158167 <authorinitials>mcc</authorinitials>
159168 <revremark>Fix documentation for media controller device nodes and add support for DVB device nodes.
@@ -557,7 +566,7 @@ and discussions on the V4L mailing list.</revremark> · 397 unmodified lines
557566 </partinfo>
558567
559568 <title>Video for Linux Two API Specification</title>
560− <subtitle>Revision 3.19</subtitle>
569+ <subtitle>Revision 4.4</subtitle>
561570
562571 <chapter id="common">
563572 &sub-common;
Documentation/DocBook/media/v4l/vidioc-encoder-cmd.xml+1−1
@@ -130,7 +130,7 @@ encoding will continue until the end of the current <wordasword>Group · 129 unmodified lines
130130 Of Pictures</wordasword>, otherwise encoding will stop immediately.
131131 When the encoder is already stopped, this command does
132132 nothing. mem2mem encoders will send a <constant>V4L2_EVENT_EOS</constant> event
133−when the last frame has been decoded and all frames are ready to be dequeued and
133+when the last frame has been encoded and all frames are ready to be dequeued and
134134 will set the <constant>V4L2_BUF_FLAG_LAST</constant> buffer flag on the last
135135 buffer of the capture queue to indicate there will be no new buffers produced to
136136 dequeue. This buffer may be empty, indicated by the driver setting the
Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml+7−0
@@ -197,6 +197,13 @@ Valid if this control is of type <constant>V4L2_CTRL_TYPE_U8</constant>.</entry> · 196 unmodified lines
197197 <entry><structfield>p_u16</structfield></entry>
198198 <entry>A pointer to a matrix control of unsigned 16-bit values.
199199 Valid if this control is of type <constant>V4L2_CTRL_TYPE_U16</constant>.</entry>
200+ </row>
201+ <row>
202+ <entry></entry>
203+ <entry>__u32 *</entry>
204+ <entry><structfield>p_u32</structfield></entry>
205+ <entry>A pointer to a matrix control of unsigned 32-bit values.
206+Valid if this control is of type <constant>V4L2_CTRL_TYPE_U32</constant>.</entry>
200207 </row>
201208 <row>
202209 <entry></entry>
Documentation/DocBook/media/v4l/vidioc-g-fmt.xml+1−1
@@ -175,7 +175,7 @@ capture and output devices.</entry> · 174 unmodified lines
175175 <entry>&v4l2-sdr-format;</entry>
176176 <entry><structfield>sdr</structfield></entry>
177177 <entry>Definition of a data format, see
178−<xref linkend="pixfmt" />, used by SDR capture devices.</entry>
178+<xref linkend="pixfmt" />, used by SDR capture and output devices.</entry>
179179 </row>
180180 <row>
181181 <entry></entry>
Documentation/DocBook/media/v4l/vidioc-g-modulator.xml+13−1
@@ -78,6 +78,12 @@ different audio modulation if the request cannot be satisfied. However · 77 unmodified lines
7878 this is a write-only ioctl, it does not return the actual audio
7979 modulation selected.</para>
8080
81+ <para><link linkend="sdr">SDR</link> specific modulator types are
82+<constant>V4L2_TUNER_SDR</constant> and <constant>V4L2_TUNER_RF</constant>.
83+For SDR devices <structfield>txsubchans</structfield> field must be
84+initialized to zero.
85+The term 'modulator' means SDR transmitter in this context.</para>
86+
8187 <para>To change the radio frequency the &VIDIOC-S-FREQUENCY; ioctl
8288 is available.</para>
8389
@@ -140,7 +146,13 @@ indicator, for example a stereo pilot tone.</entry> · 56 unmodified lines
140146 </row>
141147 <row>
142148 <entry>__u32</entry>
143− <entry><structfield>reserved</structfield>[4]</entry>
149+ <entry><structfield>type</structfield></entry>
150+ <entry spanname="hspan">Type of the modulator, see <xref
151+ linkend="v4l2-tuner-type" />.</entry>
152+ </row>
153+ <row>
154+ <entry>__u32</entry>
155+ <entry><structfield>reserved</structfield>[3]</entry>
144156 <entry>Reserved for future extensions. Drivers and
145157 applications must set the array to zero.</entry>
146158 </row>
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml+16−0
@@ -80,6 +80,12 @@ if the requested mode is invalid or unsupported. Since this is a · 79 unmodified lines
8080 <!-- FIXME -->write-only ioctl, it does not return the actually
8181 selected audio mode.</para>
8282
83+ <para><link linkend="sdr">SDR</link> specific tuner types are
84+<constant>V4L2_TUNER_SDR</constant> and <constant>V4L2_TUNER_RF</constant>.
85+For SDR devices <structfield>audmode</structfield> field must be
86+initialized to zero.
87+The term 'tuner' means SDR receiver in this context.</para>
88+
8389 <para>To change the radio frequency the &VIDIOC-S-FREQUENCY; ioctl
8490 is available.</para>
8591
@@ -261,6 +267,16 @@ applications must set the array to zero.</entry> · 175 unmodified lines
261267 <entry>2</entry>
262268 <entry></entry>
263269 </row>
270+ <row>
271+ <entry><constant>V4L2_TUNER_SDR</constant></entry>
272+ <entry>4</entry>
273+ <entry></entry>
274+ </row>
275+ <row>
276+ <entry><constant>V4L2_TUNER_RF</constant></entry>
277+ <entry>5</entry>
278+ <entry></entry>
279+ </row>
264280 </tbody>
265281 </tgroup>
266282 </table>
Documentation/DocBook/media/v4l/vidioc-querycap.xml+6−0
@@ -306,6 +306,12 @@ modulator programming see · 305 unmodified lines
306306 <entry>0x00200000</entry>
307307 <entry>The device supports the &v4l2-pix-format; extended
308308 fields.</entry>
309+ </row>
310+ <row>
311+ <entry><constant>V4L2_CAP_SDR_OUTPUT</constant></entry>
312+ <entry>0x00400000</entry>
313+ <entry>The device supports the
314+<link linkend="sdr">SDR Output</link> interface.</entry>
309315 </row>
310316 <row>
311317 <entry><constant>V4L2_CAP_READWRITE</constant></entry>
Documentation/DocBook/media/v4l/vidioc-queryctrl.xml+16−5
@@ -101,8 +101,9 @@ prematurely end the enumeration).</para></footnote></para> · 100 unmodified lines
101101 next supported non-compound control, or <errorcode>EINVAL</errorcode>
102102 if there is none. In addition, the <constant>V4L2_CTRL_FLAG_NEXT_COMPOUND</constant>
103103 flag can be specified to enumerate all compound controls (i.e. controls
104−with type &ge; <constant>V4L2_CTRL_COMPOUND_TYPES</constant>). Specify both
105−<constant>V4L2_CTRL_FLAG_NEXT_CTRL</constant> and
104+with type &ge; <constant>V4L2_CTRL_COMPOUND_TYPES</constant> and/or array
105+control, in other words controls that contain more than one value).
106+Specify both <constant>V4L2_CTRL_FLAG_NEXT_CTRL</constant> and
106107 <constant>V4L2_CTRL_FLAG_NEXT_COMPOUND</constant> in order to enumerate
107108 all controls, compound or not. Drivers which do not support these flags yet
108109 always return <errorcode>EINVAL</errorcode>.</para>
@@ -422,7 +423,7 @@ the array to zero.</entry> · 313 unmodified lines
422423 <entry>any</entry>
423424 <entry>An integer-valued control ranging from minimum to
424425 maximum inclusive. The step value indicates the increment between
425−values which are actually different on the hardware.</entry>
426+values.</entry>
426427 </row>
427428 <row>
428429 <entry><constant>V4L2_CTRL_TYPE_BOOLEAN</constant></entry>
@@ -518,7 +519,7 @@ Older drivers which do not support this feature return an · 89 unmodified lines
518519 <entry>any</entry>
519520 <entry>An unsigned 8-bit valued control ranging from minimum to
520521 maximum inclusive. The step value indicates the increment between
521−values which are actually different on the hardware.
522+values.
522523 </entry>
523524 </row>
524525 <row>
@@ -528,7 +529,17 @@ values which are actually different on the hardware. · 3 unmodified lines
528529 <entry>any</entry>
529530 <entry>An unsigned 16-bit valued control ranging from minimum to
530531 maximum inclusive. The step value indicates the increment between
531−values which are actually different on the hardware.
532+values.
533+</entry>
534+ </row>
535+ <row>
536+ <entry><constant>V4L2_CTRL_TYPE_U32</constant></entry>
537+ <entry>any</entry>
538+ <entry>any</entry>
539+ <entry>any</entry>
540+ <entry>An unsigned 32-bit valued control ranging from minimum to
541+maximum inclusive. The step value indicates the increment between
542+values.
532543 </entry>
533544 </row>
534545 </tbody>
Documentation/DocBook/media_api.tmpl+1−1
@@ -38,7 +38,7 @@ · 37 unmodified lines
3838 <title>LINUX MEDIA INFRASTRUCTURE API</title>
3939
4040 <copyright>
41− <year>2009-2014</year>
41+ <year>2009-2015</year>
4242 <holder>LinuxTV Developers</holder>
4343 </copyright>
4444
Documentation/DocBook/writing-an-alsa-driver.tmpl+2−17
@@ -2181,10 +2181,6 @@ struct _snd_pcm_runtime { · 2180 unmodified lines
21812181 struct snd_pcm_hardware hw;
21822182 struct snd_pcm_hw_constraints hw_constraints;
21832183
2184− /* -- interrupt callbacks -- */
2185− void (*transfer_ack_begin)(struct snd_pcm_substream *substream);
2186− void (*transfer_ack_end)(struct snd_pcm_substream *substream);
2187−
21882184 /* -- timer -- */
21892185 unsigned int timer_resolution; /* timer resolution */
21902186
@@ -2209,9 +2205,8 @@ struct _snd_pcm_runtime { · 18 unmodified lines
22092205 For the operators (callbacks) of each sound driver, most of
22102206 these records are supposed to be read-only. Only the PCM
22112207 middle-layer changes / updates them. The exceptions are
2212− the hardware description (hw), interrupt callbacks
2213− (transfer_ack_xxx), DMA buffer information, and the private
2214− data. Besides, if you use the standard buffer allocation
2208+ the hardware description (hw) DMA buffer information and the
2209+ private data. Besides, if you use the standard buffer allocation
22152210 method via <function>snd_pcm_lib_malloc_pages()</function>,
22162211 you don't need to set the DMA buffer information by yourself.
22172212 </para>
@@ -2538,16 +2533,6 @@ struct _snd_pcm_runtime { · 320 unmodified lines
25382533 </para>
25392534 </section>
25402535
2541− <section id="pcm-interface-runtime-intr">
2542− <title>Interrupt Callbacks</title>
2543− <para>
2544− The field <structfield>transfer_ack_begin</structfield> and
2545− <structfield>transfer_ack_end</structfield> are called at
2546− the beginning and at the end of
2547− <function>snd_pcm_period_elapsed()</function>, respectively.
2548− </para>
2549− </section>
2550−
25512536 </section>
25522537
25532538 <section id="pcm-interface-operators">
Documentation/IPMI.txt+5−2
@@ -587,7 +587,7 @@ used to control it: · 586 unmodified lines
587587
588588 modprobe ipmi_watchdog timeout=<t> pretimeout=<t> action=<action type>
589589 preaction=<preaction type> preop=<preop type> start_now=x
590− nowayout=x ifnum_to_use=n
590+ nowayout=x ifnum_to_use=n panic_wdt_timeout=<t>
591591
592592 ifnum_to_use specifies which interface the watchdog timer should use.
593593 The default is -1, which means to pick the first one registered.
@@ -597,7 +597,9 @@ is the amount of seconds before the reset that the pre-timeout panic will · 3 unmodified lines
597597 occur (if pretimeout is zero, then pretimeout will not be enabled). Note
598598 that the pretimeout is the time before the final timeout. So if the
599599 timeout is 50 seconds and the pretimeout is 10 seconds, then the pretimeout
600−will occur in 40 second (10 seconds before the timeout).
600+will occur in 40 second (10 seconds before the timeout). The panic_wdt_timeout
601+is the value of timeout which is set on kernel panic, in order to let actions
602+such as kdump to occur during panic.
601603
602604 The action may be "reset", "power_cycle", or "power_off", and
603605 specifies what to do when the timer times out, and defaults to
@@ -634,6 +636,7 @@ for configuring the watchdog: · 30 unmodified lines
634636 ipmi_watchdog.preop=<preop type>
635637 ipmi_watchdog.start_now=x
636638 ipmi_watchdog.nowayout=x
639+ ipmi_watchdog.panic_wdt_timeout=<t>
637640
638641 The options are the same as the module parameter options.
639642
Documentation/IRQ-domain.txt+4−4
@@ -32,9 +32,9 @@ top of the irq_alloc_desc*() API. An irq_domain to manage mapping is · 31 unmodified lines
3232 preferred over interrupt controller drivers open coding their own
3333 reverse mapping scheme.
3434
35−irq_domain also implements translation from Device Tree interrupt
36−specifiers to hwirq numbers, and can be easily extended to support
37−other IRQ topology data sources.
35+irq_domain also implements translation from an abstract irq_fwspec
36+structure to hwirq numbers (Device Tree and ACPI GSI so far), and can
37+be easily extended to support other IRQ topology data sources.
3838
3939 === irq_domain usage ===
4040 An interrupt controller driver creates and registers an irq_domain by
@@ -184,7 +184,7 @@ There are four major interfaces to use hierarchy irq_domain: · 143 unmodified lines
184184 related resources associated with these interrupts.
185185 3) irq_domain_activate_irq(): activate interrupt controller hardware to
186186 deliver the interrupt.
187−3) irq_domain_deactivate_irq(): deactivate interrupt controller hardware
187+4) irq_domain_deactivate_irq(): deactivate interrupt controller hardware
188188 to stop delivering the interrupt.
189189
190190 Following changes are needed to support hierarchy irq_domain.
Documentation/RCU/stallwarn.txt+7−0
@@ -205,6 +205,13 @@ o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the · 204 unmodified lines
205205 behavior, you might need to replace some of the cond_resched()
206206 calls with calls to cond_resched_rcu_qs().
207207
208+o Booting Linux using a console connection that is too slow to
209+ keep up with the boot-time console-message rate. For example,
210+ a 115Kbaud serial console can be -way- too slow to keep up
211+ with boot-time message rates, and will frequently result in
212+ RCU CPU stall warning messages. Especially if you have added
213+ debug printk()s.
214+
208215 o Anything that prevents RCU's grace-period kthreads from running.
209216 This can result in the "All QSes seen" console-log message.
210217 This message will include information on when the kthread last
Documentation/RCU/torture.txt+13−26
@@ -166,40 +166,27 @@ test_no_idle_hz Whether or not to test the ability of RCU to operate in · 165 unmodified lines
166166
167167 torture_type The type of RCU to test, with string values as follows:
168168
169− "rcu": rcu_read_lock(), rcu_read_unlock() and call_rcu().
170−
171− "rcu_sync": rcu_read_lock(), rcu_read_unlock(), and
172− synchronize_rcu().
173−
174− "rcu_expedited": rcu_read_lock(), rcu_read_unlock(), and
175− synchronize_rcu_expedited().
169+ "rcu": rcu_read_lock(), rcu_read_unlock() and call_rcu(),
170+ along with expedited, synchronous, and polling
171+ variants.
176172
177173 "rcu_bh": rcu_read_lock_bh(), rcu_read_unlock_bh(), and
178− call_rcu_bh().
179−
180− "rcu_bh_sync": rcu_read_lock_bh(), rcu_read_unlock_bh(),
181− and synchronize_rcu_bh().
174+ call_rcu_bh(), along with expedited and synchronous
175+ variants.
182176
183− "rcu_bh_expedited": rcu_read_lock_bh(), rcu_read_unlock_bh(),
184− and synchronize_rcu_bh_expedited().
177+ "rcu_busted": This tests an intentionally incorrect version
178+ of RCU in order to help test rcutorture itself.
185179
186180 "srcu": srcu_read_lock(), srcu_read_unlock() and
187− call_srcu().
188−
189− "srcu_sync": srcu_read_lock(), srcu_read_unlock() and
190− synchronize_srcu().
191−
192− "srcu_expedited": srcu_read_lock(), srcu_read_unlock() and
193− synchronize_srcu_expedited().
181+ call_srcu(), along with expedited and
182+ synchronous variants.
194183
195184 "sched": preempt_disable(), preempt_enable(), and
196− call_rcu_sched().
197−
198− "sched_sync": preempt_disable(), preempt_enable(), and
199− synchronize_sched().
185+ call_rcu_sched(), along with expedited,
186+ synchronous, and polling variants.
200187
201− "sched_expedited": preempt_disable(), preempt_enable(), and
202− synchronize_sched_expedited().
188+ "tasks": voluntary context switch and call_rcu_tasks(),
189+ along with expedited and synchronous variants.
203190
204191 Defaults to "rcu".
205192
Documentation/RCU/trace.txt+16−16
@@ -56,14 +56,14 @@ rcuboost: · 55 unmodified lines
5656
5757 The output of "cat rcu/rcu_preempt/rcudata" looks as follows:
5858
59− 0!c=30455 g=30456 pq=1/0 qp=1 dt=126535/140000000000000/0 df=2002 of=4 ql=0/0 qs=N... b=10 ci=74572 nci=0 co=1131 ca=716
60− 1!c=30719 g=30720 pq=1/0 qp=0 dt=132007/140000000000000/0 df=1874 of=10 ql=0/0 qs=N... b=10 ci=123209 nci=0 co=685 ca=982
61− 2!c=30150 g=30151 pq=1/1 qp=1 dt=138537/140000000000000/0 df=1707 of=8 ql=0/0 qs=N... b=10 ci=80132 nci=0 co=1328 ca=1458
62− 3 c=31249 g=31250 pq=1/1 qp=0 dt=107255/140000000000000/0 df=1749 of=6 ql=0/450 qs=NRW. b=10 ci=151700 nci=0 co=509 ca=622
63− 4!c=29502 g=29503 pq=1/0 qp=1 dt=83647/140000000000000/0 df=965 of=5 ql=0/0 qs=N... b=10 ci=65643 nci=0 co=1373 ca=1521
64− 5 c=31201 g=31202 pq=1/0 qp=1 dt=70422/0/0 df=535 of=7 ql=0/0 qs=.... b=10 ci=58500 nci=0 co=764 ca=698
65− 6!c=30253 g=30254 pq=1/0 qp=1 dt=95363/140000000000000/0 df=780 of=5 ql=0/0 qs=N... b=10 ci=100607 nci=0 co=1414 ca=1353
66− 7 c=31178 g=31178 pq=1/0 qp=0 dt=91536/0/0 df=547 of=4 ql=0/0 qs=.... b=10 ci=109819 nci=0 co=1115 ca=969
59+ 0!c=30455 g=30456 cnq=1/0:1 dt=126535/140000000000000/0 df=2002 of=4 ql=0/0 qs=N... b=10 ci=74572 nci=0 co=1131 ca=716
60+ 1!c=30719 g=30720 cnq=1/0:0 dt=132007/140000000000000/0 df=1874 of=10 ql=0/0 qs=N... b=10 ci=123209 nci=0 co=685 ca=982
61+ 2!c=30150 g=30151 cnq=1/1:1 dt=138537/140000000000000/0 df=1707 of=8 ql=0/0 qs=N... b=10 ci=80132 nci=0 co=1328 ca=1458
62+ 3 c=31249 g=31250 cnq=1/1:0 dt=107255/140000000000000/0 df=1749 of=6 ql=0/450 qs=NRW. b=10 ci=151700 nci=0 co=509 ca=622
63+ 4!c=29502 g=29503 cnq=1/0:1 dt=83647/140000000000000/0 df=965 of=5 ql=0/0 qs=N... b=10 ci=65643 nci=0 co=1373 ca=1521
64+ 5 c=31201 g=31202 cnq=1/0:1 dt=70422/0/0 df=535 of=7 ql=0/0 qs=.... b=10 ci=58500 nci=0 co=764 ca=698
65+ 6!c=30253 g=30254 cnq=1/0:1 dt=95363/140000000000000/0 df=780 of=5 ql=0/0 qs=N... b=10 ci=100607 nci=0 co=1414 ca=1353
66+ 7 c=31178 g=31178 cnq=1/0:0 dt=91536/0/0 df=547 of=4 ql=0/0 qs=.... b=10 ci=109819 nci=0 co=1115 ca=969
6767
6868 This file has one line per CPU, or eight for this 8-CPU system.
6969 The fields are as follows:
@@ -188,14 +188,14 @@ o "ca" is the number of RCU callbacks that have been adopted by this · 118 unmodified lines
188188 Kernels compiled with CONFIG_RCU_BOOST=y display the following from
189189 /debug/rcu/rcu_preempt/rcudata:
190190
191− 0!c=12865 g=12866 pq=1/0 qp=1 dt=83113/140000000000000/0 df=288 of=11 ql=0/0 qs=N... kt=0/O ktl=944 b=10 ci=60709 nci=0 co=748 ca=871
192− 1 c=14407 g=14408 pq=1/0 qp=0 dt=100679/140000000000000/0 df=378 of=7 ql=0/119 qs=NRW. kt=0/W ktl=9b6 b=10 ci=109740 nci=0 co=589 ca=485
193− 2 c=14407 g=14408 pq=1/0 qp=0 dt=105486/0/0 df=90 of=9 ql=0/89 qs=NRW. kt=0/W ktl=c0c b=10 ci=83113 nci=0 co=533 ca=490
194− 3 c=14407 g=14408 pq=1/0 qp=0 dt=107138/0/0 df=142 of=8 ql=0/188 qs=NRW. kt=0/W ktl=b96 b=10 ci=121114 nci=0 co=426 ca=290
195− 4 c=14405 g=14406 pq=1/0 qp=1 dt=50238/0/0 df=706 of=7 ql=0/0 qs=.... kt=0/W ktl=812 b=10 ci=34929 nci=0 co=643 ca=114
196− 5!c=14168 g=14169 pq=1/0 qp=0 dt=45465/140000000000000/0 df=161 of=11 ql=0/0 qs=N... kt=0/O ktl=b4d b=10 ci=47712 nci=0 co=677 ca=722
197− 6 c=14404 g=14405 pq=1/0 qp=0 dt=59454/0/0 df=94 of=6 ql=0/0 qs=.... kt=0/W ktl=e57 b=10 ci=55597 nci=0 co=701 ca=811
198− 7 c=14407 g=14408 pq=1/0 qp=1 dt=68850/0/0 df=31 of=8 ql=0/0 qs=.... kt=0/W ktl=14bd b=10 ci=77475 nci=0 co=508 ca=1042
191+ 0!c=12865 g=12866 cnq=1/0:1 dt=83113/140000000000000/0 df=288 of=11 ql=0/0 qs=N... kt=0/O ktl=944 b=10 ci=60709 nci=0 co=748 ca=871
192+ 1 c=14407 g=14408 cnq=1/0:0 dt=100679/140000000000000/0 df=378 of=7 ql=0/119 qs=NRW. kt=0/W ktl=9b6 b=10 ci=109740 nci=0 co=589 ca=485
193+ 2 c=14407 g=14408 cnq=1/0:0 dt=105486/0/0 df=90 of=9 ql=0/89 qs=NRW. kt=0/W ktl=c0c b=10 ci=83113 nci=0 co=533 ca=490
194+ 3 c=14407 g=14408 cnq=1/0:0 dt=107138/0/0 df=142 of=8 ql=0/188 qs=NRW. kt=0/W ktl=b96 b=10 ci=121114 nci=0 co=426 ca=290
195+ 4 c=14405 g=14406 cnq=1/0:1 dt=50238/0/0 df=706 of=7 ql=0/0 qs=.... kt=0/W ktl=812 b=10 ci=34929 nci=0 co=643 ca=114
196+ 5!c=14168 g=14169 cnq=1/0:0 dt=45465/140000000000000/0 df=161 of=11 ql=0/0 qs=N... kt=0/O ktl=b4d b=10 ci=47712 nci=0 co=677 ca=722
197+ 6 c=14404 g=14405 cnq=1/0:0 dt=59454/0/0 df=94 of=6 ql=0/0 qs=.... kt=0/W ktl=e57 b=10 ci=55597 nci=0 co=701 ca=811
198+ 7 c=14407 g=14408 cnq=1/0:1 dt=68850/0/0 df=31 of=8 ql=0/0 qs=.... kt=0/W ktl=14bd b=10 ci=77475 nci=0 co=508 ca=1042
199199
200200 This is similar to the output discussed above, but contains the following
201201 additional fields:
Documentation/RCU/whatisRCU.txt+3−3
@@ -364,7 +364,7 @@ uses of RCU may be found in listRCU.txt, arrayRCU.txt, and NMI-RCU.txt. · 363 unmodified lines
364364 };
365365 DEFINE_SPINLOCK(foo_mutex);
366366
367− struct foo *gbl_foo;
367+ struct foo __rcu *gbl_foo;
368368
369369 /*
370370 * Create a new struct foo that is the same as the one currently
@@ -386,7 +386,7 @@ uses of RCU may be found in listRCU.txt, arrayRCU.txt, and NMI-RCU.txt. · 15 unmodified lines
386386
387387 new_fp = kmalloc(sizeof(*new_fp), GFP_KERNEL);
388388 spin_lock(&foo_mutex);
389− old_fp = gbl_foo;
389+ old_fp = rcu_dereference_protected(gbl_foo, lockdep_is_held(&foo_mutex));
390390 *new_fp = *old_fp;
391391 new_fp->a = new_a;
392392 rcu_assign_pointer(gbl_foo, new_fp);
@@ -487,7 +487,7 @@ The foo_update_a() function might then be written as follows: · 94 unmodified lines
487487
488488 new_fp = kmalloc(sizeof(*new_fp), GFP_KERNEL);
489489 spin_lock(&foo_mutex);
490− old_fp = gbl_foo;
490+ old_fp = rcu_dereference_protected(gbl_foo, lockdep_is_held(&foo_mutex));
491491 *new_fp = *old_fp;
492492 new_fp->a = new_a;
493493 rcu_assign_pointer(gbl_foo, new_fp);
Documentation/SubmittingPatches+18−5
@@ -659,8 +659,8 @@ succinct and descriptive, but that is what a well-written summary · 658 unmodified lines
659659 should do.
660660
661661 The "summary phrase" may be prefixed by tags enclosed in square
662−brackets: "Subject: [PATCH tag] <summary phrase>". The tags are not
663−considered part of the summary phrase, but describe how the patch
662+brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
663+not considered part of the summary phrase, but describe how the patch
664664 should be treated. Common tags might include a version descriptor if
665665 the multiple versions of the patch have been sent out in response to
666666 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
@@ -672,8 +672,8 @@ the patch series. · 5 unmodified lines
672672
673673 A couple of example Subjects:
674674
675− Subject: [patch 2/5] ext2: improve scalability of bitmap searching
676− Subject: [PATCHv2 001/207] x86: fix eflags tracking
675+ Subject: [PATCH 2/5] ext2: improve scalability of bitmap searching
676+ Subject: [PATCH v2 01/27] x86: fix eflags tracking
677677
678678 The "from" line must be the very first line in the message body,
679679 and has the form:
@@ -718,8 +718,21 @@ generates appropriate diffstats by default.) · 38 unmodified lines
718718 See more details on the proper patch format in the following
719719 references.
720720
721+15) Explicit In-Reply-To headers
722+--------------------------------
723+
724+It can be helpful to manually add In-Reply-To: headers to a patch
725+(e.g., when using "git send email") to associate the patch with
726+previous relevant discussion, e.g. to link a bug fix to the email with
727+the bug report. However, for a multi-patch series, it is generally
728+best to avoid using In-Reply-To: to link to older versions of the
729+series. This way multiple versions of the patch don't become an
730+unmanageable forest of references in email clients. If a link is
731+helpful, you can use the https://lkml.kernel.org/ redirector (e.g., in
732+the cover email text) to link to an earlier version of the patch series.
733+
721734
722−15) Sending "git pull" requests
735+16) Sending "git pull" requests
723736 -------------------------------
724737
725738 If you have a series of patches, it may be most convenient to have the
Documentation/acpi/enumeration.txt+8−3
@@ -347,13 +347,18 @@ For the first case, the MFD drivers do not need to do anything. The · 346 unmodified lines
347347 resulting child platform device will have its ACPI_COMPANION() set to point
348348 to the parent device.
349349
350−If the ACPI namespace has a device that we can match using an ACPI id,
351−the id should be set like:
350+If the ACPI namespace has a device that we can match using an ACPI id or ACPI
351+adr, the cell should be set like:
352+
353+ static struct mfd_cell_acpi_match my_subdevice_cell_acpi_match = {
354+ .pnpid = "XYZ0001",
355+ .adr = 0,
356+ };
352357
353358 static struct mfd_cell my_subdevice_cell = {
354359 .name = "my_subdevice",
355360 /* set the resources relative to the parent */
356− .acpi_pnpid = "XYZ0001",
361+ .acpi_match = &my_subdevice_cell_acpi_match,
357362 };
358363
359364 The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
Documentation/acpi/i2c-muxes.txt+58−0
@@ -0,0 +1,58 @@
1+ACPI I2C Muxes
2+--------------
3+
4+Describing an I2C device hierarchy that includes I2C muxes requires an ACPI
5+Device () scope per mux channel.
6+
7+Consider this topology:
8+
9++------+ +------+
10+| SMB1 |-->| MUX0 |--CH00--> i2c client A (0x50)
11+| | | 0x70 |--CH01--> i2c client B (0x50)
12++------+ +------+
13+
14+which corresponds to the following ASL:
15+
16+Device (SMB1)
17+{
18+ Name (_HID, ...)
19+ Device (MUX0)
20+ {
21+ Name (_HID, ...)
22+ Name (_CRS, ResourceTemplate () {
23+ I2cSerialBus (0x70, ControllerInitiated, I2C_SPEED,
24+ AddressingMode7Bit, "^SMB1", 0x00,
25+ ResourceConsumer,,)
26+ }
27+
28+ Device (CH00)
29+ {
30+ Name (_ADR, 0)
31+
32+ Device (CLIA)
33+ {
34+ Name (_HID, ...)
35+ Name (_CRS, ResourceTemplate () {
36+ I2cSerialBus (0x50, ControllerInitiated, I2C_SPEED,
37+ AddressingMode7Bit, "^CH00", 0x00,
38+ ResourceConsumer,,)
39+ }
40+ }
41+ }
42+
43+ Device (CH01)
44+ {
45+ Name (_ADR, 1)
46+
47+ Device (CLIB)
48+ {
49+ Name (_HID, ...)
50+ Name (_CRS, ResourceTemplate () {
51+ I2cSerialBus (0x50, ControllerInitiated, I2C_SPEED,
52+ AddressingMode7Bit, "^CH01", 0x00,
53+ ResourceConsumer,,)
54+ }
55+ }
56+ }
57+ }
58+}
Documentation/arm/OMAP/README+7−0
@@ -0,0 +1,7 @@
1+This file contains documentation for running mainline
2+kernel on omaps.
3+
4+KERNEL NEW DEPENDENCIES
5+v4.3+ Update is needed for custom .config files to make sure
6+ CONFIG_REGULATOR_PBIAS is enabled for MMC1 to work
7+ properly.
Documentation/arm/SA1100/Victor+0−16
@@ -1,16 +0,0 @@
1−Victor is known as a "digital talking book player" manufactured by
2−VisuAide, Inc. to be used by blind people.
3−
4−For more information related to Victor, see:
5−
6− http://www.humanware.com/en-usa/products
7−
8−Of course Victor is using Linux as its main operating system.
9−The Victor implementation for Linux is maintained by Nicolas Pitre:
10−
11− nico@visuaide.com
12− nico@fluxnic.net
13−
14−For any comments, please feel free to contact me through the above
15−addresses.
16−
Documentation/arm/Samsung/Bootloader-interface.txt+3−2
@@ -19,7 +19,7 @@ executing kernel. · 18 unmodified lines
1919 Address: sysram_ns_base_addr
2020 Offset Value Purpose
2121 =============================================================================
22−0x08 exynos_cpu_resume_ns System suspend
22+0x08 exynos_cpu_resume_ns, mcpm_entry_point System suspend
2323 0x0c 0x00000bad (Magic cookie) System suspend
2424 0x1c exynos4_secondary_startup Secondary CPU boot
2525 0x1c + 4*cpu exynos4_secondary_startup (Exynos4412) Secondary CPU boot
@@ -56,7 +56,8 @@ Offset Value Purpose · 30 unmodified lines
5656 Address: pmu_base_addr
5757 Offset Value Purpose
5858 =============================================================================
59−0x0908 Non-zero (only Exynos3250) Secondary CPU boot up indicator
59+0x0908 Non-zero Secondary CPU boot up indicator
60+ on Exynos3250 and Exynos542x
6061
6162
6263 4. Glossary
Documentation/arm/keystone/knav-qmss.txt+56−0
@@ -0,0 +1,56 @@
1+* Texas Instruments Keystone Navigator Queue Management SubSystem driver
2+
3+Driver source code path
4+ drivers/soc/ti/knav_qmss.c
5+ drivers/soc/ti/knav_qmss_acc.c
6+
7+The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
8+the main hardware sub system which forms the backbone of the Keystone
9+multi-core Navigator. QMSS consist of queue managers, packed-data structure
10+processors(PDSP), linking RAM, descriptor pools and infrastructure
11+Packet DMA.
12+The Queue Manager is a hardware module that is responsible for accelerating
13+management of the packet queues. Packets are queued/de-queued by writing or
14+reading descriptor address to a particular memory mapped location. The PDSPs
15+perform QMSS related functions like accumulation, QoS, or event management.
16+Linking RAM registers are used to link the descriptors which are stored in
17+descriptor RAM. Descriptor RAM is configurable as internal or external memory.
18+The QMSS driver manages the PDSP setups, linking RAM regions,
19+queue pool management (allocation, push, pop and notify) and descriptor
20+pool management.
21+
22+knav qmss driver provides a set of APIs to drivers to open/close qmss queues,
23+allocate descriptor pools, map the descriptors, push/pop to queues etc. For
24+details of the available APIs, please refers to include/linux/soc/ti/knav_qmss.h
25+
26+DT documentation is available at
27+Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
28+
29+Accumulator QMSS queues using PDSP firmware
30+============================================
31+The QMSS PDSP firmware support accumulator channel that can monitor a single
32+queue or multiple contiguous queues. drivers/soc/ti/knav_qmss_acc.c is the
33+driver that interface with the accumulator PDSP. This configures
34+accumulator channels defined in DTS (example in DT documentation) to monitor
35+1 or 32 queues per channel. More description on the firmware is available in
36+CPPI/QMSS Low Level Driver document (docs/CPPI_QMSS_LLD_SDS.pdf) at
37+ git://git.ti.com/keystone-rtos/qmss-lld.git
38+
39+k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
40+channels. This firmware is available under ti-keystone folder of
41+firmware.git at
42+ git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
43+
44+To use copy the firmware image to lib/firmware folder of the initramfs or
45+ubifs file system and provide a sym link to k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin
46+in the file system and boot up the kernel. User would see
47+
48+ "firmware file ks2_qmss_pdsp_acc48.bin downloaded for PDSP"
49+
50+in the boot up log if loading of firmware to PDSP is successful.
51+
52+Use of accumulated queues requires the firmware image to be present in the
53+file system. The driver doesn't acc queues to the supported queue range if
54+PDSP is not running in the SoC. The API call fails if there is a queue open
55+request to an acc queue and PDSP is not running. So make sure to copy firmware
56+to file system before using these queue types.
Documentation/arm/memory.txt+1−1
@@ -54,7 +54,7 @@ VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space. · 53 unmodified lines
5454 located here through iotable_init().
5555 VMALLOC_START is based upon the value
5656 of the high_memory variable, and VMALLOC_END
57− is equal to 0xff000000.
57+ is equal to 0xff800000.
5858
5959 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
6060 This maps the platforms RAM, and typically
Documentation/arm/sunxi/README+1−1
@@ -25,7 +25,7 @@ SunXi family · 24 unmodified lines
2525 + Datasheet
2626 http://dl.linux-sunxi.org/A10s/A10s%20Datasheet%20-%20v1.20%20%282012-03-27%29.pdf
2727
28− - Allwinner A13 (sun5i)
28+ - Allwinner A13 / R8 (sun5i)
2929 + Datasheet
3030 http://dl.linux-sunxi.org/A13/A13%20Datasheet%20-%20v1.12%20%282012-03-29%29.pdf
3131 + User Manual
Documentation/arm/uefi.txt+0−4
@@ -58,7 +58,3 @@ linux,uefi-mmap-desc-size | 32-bit | Size in bytes of each entry in the UEFI · 57 unmodified lines
5858 --------------------------------------------------------------------------------
5959 linux,uefi-mmap-desc-ver | 32-bit | Version of the mmap descriptor format.
6060 --------------------------------------------------------------------------------
61−linux,uefi-stub-kern-ver | string | Copy of linux_banner from build.
62−--------------------------------------------------------------------------------
63−
64−For verbose debug messages, specify 'uefi_debug' on the kernel command line.
Documentation/arm64/booting.txt+16−2
@@ -104,7 +104,12 @@ Header notes: · 103 unmodified lines
104104 - The flags field (introduced in v3.17) is a little-endian 64-bit field
105105 composed as follows:
106106 Bit 0: Kernel endianness. 1 if BE, 0 if LE.
107− Bits 1-63: Reserved.
107+ Bit 1-2: Kernel Page size.
108+ 0 - Unspecified.
109+ 1 - 4K
110+ 2 - 16K
111+ 3 - 64K
112+ Bits 3-63: Reserved.
108113
109114 - When image_size is zero, a bootloader should attempt to keep as much
110115 memory as possible free for use by the kernel immediately after the
@@ -173,13 +178,22 @@ Before jumping into the kernel, the following conditions must be met: · 62 unmodified lines
173178 the kernel image will be entered must be initialised by software at a
174179 higher exception level to prevent execution in an UNKNOWN state.
175180
176− For systems with a GICv3 interrupt controller:
181+ For systems with a GICv3 interrupt controller to be used in v3 mode:
177182 - If EL3 is present:
178183 ICC_SRE_EL3.Enable (bit 3) must be initialiased to 0b1.
179184 ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1.
180185 - If the kernel is entered at EL1:
181186 ICC.SRE_EL2.Enable (bit 3) must be initialised to 0b1
182187 ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b1.
188+ - The DT or ACPI tables must describe a GICv3 interrupt controller.
189+
190+ For systems with a GICv3 interrupt controller to be used in
191+ compatibility (v2) mode:
192+ - If EL3 is present:
193+ ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b0.
194+ - If the kernel is entered at EL1:
195+ ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b0.
196+ - The DT or ACPI tables must describe a GICv2 interrupt controller.
183197
184198 The requirements described above for CPU mode, caches, MMUs, architected
185199 timers, coherency and system registers apply to all CPUs. All CPUs must
Documentation/atomic_ops.txt+4−0
@@ -542,6 +542,10 @@ The routines xchg() and cmpxchg() must provide the same exact · 541 unmodified lines
542542 memory-barrier semantics as the atomic and bit operations returning
543543 values.
544544
545+Note: If someone wants to use xchg(), cmpxchg() and their variants,
546+linux/atomic.h should be included rather than asm/cmpxchg.h, unless
547+the code is in arch/* and can take care of itself.
548+
545549 Spinlocks and rwlocks have memory barrier expectations as well.
546550 The rule to follow is simple:
547551
Documentation/block/pr.txt+119−0
@@ -0,0 +1,119 @@
1+
2+Block layer support for Persistent Reservations
3+===============================================
4+
5+The Linux kernel supports a user space interface for simplified
6+Persistent Reservations which map to block devices that support
7+these (like SCSI). Persistent Reservations allow restricting
8+access to block devices to specific initiators in a shared storage
9+setup.
10+
11+This document gives a general overview of the support ioctl commands.
12+For a more detailed reference please refer the the SCSI Primary
13+Commands standard, specifically the section on Reservations and the
14+"PERSISTENT RESERVE IN" and "PERSISTENT RESERVE OUT" commands.
15+
16+All implementations are expected to ensure the reservations survive
17+a power loss and cover all connections in a multi path environment.
18+These behaviors are optional in SPC but will be automatically applied
19+by Linux.
20+
21+
22+The following types of reservations are supported:
23+--------------------------------------------------
24+
25+ - PR_WRITE_EXCLUSIVE
26+
27+ Only the initiator that owns the reservation can write to the
28+ device. Any initiator can read from the device.
29+
30+ - PR_EXCLUSIVE_ACCESS
31+
32+ Only the initiator that owns the reservation can access the
33+ device.
34+
35+ - PR_WRITE_EXCLUSIVE_REG_ONLY
36+
37+ Only initiators with a registered key can write to the device,
38+ Any initiator can read from the device.
39+
40+ - PR_EXCLUSIVE_ACCESS_REG_ONLY
41+
42+ Only initiators with a registered key can access the device.
43+
44+ - PR_WRITE_EXCLUSIVE_ALL_REGS
45+
46+ Only initiators with a registered key can write to the device,
47+ Any initiator can read from the device.
48+ All initiators with a registered key are considered reservation
49+ holders.
50+ Please reference the SPC spec on the meaning of a reservation
51+ holder if you want to use this type.
52+
53+ - PR_EXCLUSIVE_ACCESS_ALL_REGS
54+
55+ Only initiators with a registered key can access the device.
56+ All initiators with a registered key are considered reservation
57+ holders.
58+ Please reference the SPC spec on the meaning of a reservation
59+ holder if you want to use this type.
60+
61+
62+The following ioctl are supported:
63+----------------------------------
64+
65+1. IOC_PR_REGISTER
66+
67+This ioctl command registers a new reservation if the new_key argument
68+is non-null. If no existing reservation exists old_key must be zero,
69+if an existing reservation should be replaced old_key must contain
70+the old reservation key.
71+
72+If the new_key argument is 0 it unregisters the existing reservation passed
73+in old_key.
74+
75+
76+2. IOC_PR_RESERVE
77+
78+This ioctl command reserves the device and thus restricts access for other
79+devices based on the type argument. The key argument must be the existing
80+reservation key for the device as acquired by the IOC_PR_REGISTER,
81+IOC_PR_REGISTER_IGNORE, IOC_PR_PREEMPT or IOC_PR_PREEMPT_ABORT commands.
82+
83+
84+3. IOC_PR_RELEASE
85+
86+This ioctl command releases the reservation specified by key and flags
87+and thus removes any access restriction implied by it.
88+
89+
90+4. IOC_PR_PREEMPT
91+
92+This ioctl command releases the existing reservation referred to by
93+old_key and replaces it with a a new reservation of type for the
94+reservation key new_key.
95+
96+
97+5. IOC_PR_PREEMPT_ABORT
98+
99+This ioctl command works like IOC_PR_PREEMPT except that it also aborts
100+any outstanding command sent over a connection identified by old_key.
101+
102+6. IOC_PR_CLEAR
103+
104+This ioctl command unregisters both key and any other reservation key
105+registered with the device and drops any existing reservation.
106+
107+
108+Flags
109+-----
110+
111+All the ioctls have a flag field. Currently only one flag is supported:
112+
113+ - PR_FL_IGNORE_KEY
114+
115+ Ignore the existing reservation key. This is commonly supported for
116+ IOC_PR_REGISTER, and some implementation may support the flag for
117+ IOC_PR_RESERVE.
118+
119+For all unknown flags the kernel will return -EOPNOTSUPP.
Documentation/blockdev/zram.txt+40−4
@@ -14,8 +14,43 @@ Statistics for individual zram devices are exported through sysfs nodes at · 13 unmodified lines
1414
1515 * Usage
1616
17+There are several ways to configure and manage zram device(-s):
18+a) using zram and zram_control sysfs attributes
19+b) using zramctl utility, provided by util-linux (util-linux@vger.kernel.org).
20+
21+In this document we will describe only 'manual' zram configuration steps,
22+IOW, zram and zram_control sysfs attributes.
23+
24+In order to get a better idea about zramctl please consult util-linux
25+documentation, zramctl man-page or `zramctl --help'. Please be informed
26+that zram maintainers do not develop/maintain util-linux or zramctl, should
27+you have any questions please contact util-linux@vger.kernel.org
28+
1729 Following shows a typical sequence of steps for using zram.
1830
31+WARNING
32+=======
33+For the sake of simplicity we skip error checking parts in most of the
34+examples below. However, it is your sole responsibility to handle errors.
35+
36+zram sysfs attributes always return negative values in case of errors.
37+The list of possible return codes:
38+-EBUSY -- an attempt to modify an attribute that cannot be changed once
39+the device has been initialised. Please reset device first;
40+-ENOMEM -- zram was not able to allocate enough memory to fulfil your
41+needs;
42+-EINVAL -- invalid input has been provided.
43+
44+If you use 'echo', the returned value that is changed by 'echo' utility,
45+and, in general case, something like:
46+
47+ echo 3 > /sys/block/zram0/max_comp_streams
48+ if [ $? -ne 0 ];
49+ handle_error
50+ fi
51+
52+should suffice.
53+
1954 1) Load Module:
2055 modprobe zram num_devices=4
2156 This creates 4 devices: /dev/zram{0,1,2,3}
@@ -47,7 +82,7 @@ max_comp_streams adjustment. · 25 unmodified lines
4782
4883 3) Select compression algorithm
4984 Using comp_algorithm device attribute one can see available and
50− currently selected (shown in square brackets) compression algortithms,
85+ currently selected (shown in square brackets) compression algorithms,
5186 change selected compression algorithm (once the device is initialised
5287 there is no way to change compression algorithm).
5388
@@ -119,7 +154,7 @@ execute · 65 unmodified lines
119154 8) Stats:
120155 Per-device statistics are exported as various nodes under /sys/block/zram<id>/
121156
122−A brief description of exported device attritbutes. For more details please
157+A brief description of exported device attributes. For more details please
123158 read Documentation/ABI/testing/sysfs-block-zram.
124159
125160 Name access description
@@ -140,8 +175,9 @@ zero_pages RO the number of zero filled pages written to this disk · 14 unmodified lines
140175 orig_data_size RO uncompressed size of data stored in this disk
141176 compr_data_size RO compressed size of data stored in this disk
142177 mem_used_total RO the amount of memory allocated for this disk
143−mem_used_max RW the maximum amount memory zram have consumed to
144− store compressed data
178+mem_used_max RW the maximum amount of memory zram have consumed to
179+ store the data (to reset this counter to the actual
180+ current value, write 1 to this attribute)
145181 mem_limit RW the maximum amount of memory ZRAM can use to store
146182 the compressed data
147183 pages_compacted RO the number of pages freed during compaction
Documentation/cgroups/blkio-controller.txt+1−1
@@ -59,7 +59,7 @@ cgroups. Here is what you can do. · 58 unmodified lines
5959 - At macro level, first dd should finish first. To get more precise data, keep
6060 on looking at (with the help of script), at blkio.disk_time and
6161 blkio.disk_sectors files of both test1 and test2 groups. This will tell how
62− much disk time (in milli seconds), each group got and how many secotors each
62+ much disk time (in milliseconds), each group got and how many sectors each
6363 group dispatched to the disk. We provide fairness in terms of disk time, so
6464 ideally io.disk_time of cgroups should be in proportion to the weight.
6565
Documentation/cgroups/cgroups.txt+4−0
@@ -637,6 +637,10 @@ void exit(struct task_struct *task) · 636 unmodified lines
637637
638638 Called during task exit.
639639
640+void free(struct task_struct *task)
641+
642+Called when the task_struct is freed.
643+
640644 void bind(struct cgroup *root)
641645 (cgroup_mutex held by caller)
642646
Documentation/cgroups/freezer-subsystem.txt+1−1
@@ -50,7 +50,7 @@ being frozen. This allows the bash example above and gdb to run as · 49 unmodified lines
5050 expected.
5151
5252 The cgroup freezer is hierarchical. Freezing a cgroup freezes all
53−tasks beloning to the cgroup and all its descendant cgroups. Each
53+tasks belonging to the cgroup and all its descendant cgroups. Each
5454 cgroup has its own state (self-state) and the state inherited from the
5555 parent (parent-state). Iff both states are THAWED, the cgroup is
5656 THAWED.
Documentation/cgroups/unified-hierarchy.txt+15−12
@@ -107,12 +107,6 @@ root of unified hierarchy can be bound to other hierarchies. This · 106 unmodified lines
107107 allows mixing unified hierarchy with the traditional multiple
108108 hierarchies in a fully backward compatible way.
109109
110−For development purposes, the following boot parameter makes all
111−controllers to appear on the unified hierarchy whether supported or
112−not.
113−
114− cgroup__DEVEL__legacy_files_on_dfl
115−
116110 A controller can be moved across hierarchies only after the controller
117111 is no longer referenced in its current hierarchy. Because per-cgroup
118112 controller states are destroyed asynchronously and controllers may
@@ -341,11 +335,11 @@ is riddled with issues. · 222 unmodified lines
341335 unnecessarily complicated and probably done this way because event
342336 delivery itself was expensive.
343337
344−Unified hierarchy implements an interface file "cgroup.populated"
345−which can be used to monitor whether the cgroup's subhierarchy has
346−tasks in it or not. Its value is 0 if there is no task in the cgroup
347−and its descendants; otherwise, 1. poll and [id]notify events are
348−triggered when the value changes.
338+Unified hierarchy implements "populated" field in "cgroup.events"
339+interface file which can be used to monitor whether the cgroup's
340+subhierarchy has tasks in it or not. Its value is 0 if there is no
341+task in the cgroup and its descendants; otherwise, 1. poll and
342+[id]notify events are triggered when the value changes.
349343
350344 This is significantly lighter and simpler and trivially allows
351345 delegating management of subhierarchy - subhierarchy monitoring can
@@ -374,6 +368,10 @@ supported and the interface files "release_agent" and · 22 unmodified lines
374368
375369 - The "cgroup.clone_children" file is removed.
376370
371+- /proc/PID/cgroup keeps reporting the cgroup that a zombie belonged
372+ to before exiting. If the cgroup is removed before the zombie is
373+ reaped, " (deleted)" is appeneded to the path.
374+
377375
378376 5-3. Controller File Conventions
379377
@@ -435,6 +433,11 @@ may be specified in any order and not all pairs have to be specified. · 55 unmodified lines
435433 the first entry in the file. Specific entries can use "default" as
436434 its value to indicate inheritance of the default value.
437435
436+- For events which are not very high frequency, an interface file
437+ "events" should be created which lists event key value pairs.
438+ Whenever a notifiable event happens, file modified event should be
439+ generated on the file.
440+
438441
439442 5-4. Per-Controller Changes
440443
@@ -491,7 +494,7 @@ may be specified in any order and not all pairs have to be specified. · 50 unmodified lines
491494 ${R|W}BPS are read/write bytes per second and ${R|W}IOPS are
492495 read/write IOs per second. "max" indicates no limit. Writing
493496 to the file follows the same format but the individual
494− settings may be ommitted or specified in any order.
497+ settings may be omitted or specified in any order.
495498
496499 This file is available only on non-root cgroups.
497500
Documentation/crypto/asymmetric-keys.txt+14−13
@@ -186,7 +186,7 @@ and looks like the following: · 185 unmodified lines
186186 const struct public_key_signature *sig);
187187 };
188188
189−Asymmetric keys point to this with their type_data[0] member.
189+Asymmetric keys point to this with their payload[asym_subtype] member.
190190
191191 The owner and name fields should be set to the owning module and the name of
192192 the subtype. Currently, the name is only used for print statements.
@@ -269,8 +269,7 @@ mandatory: · 76 unmodified lines
269269
270270 struct key_preparsed_payload {
271271 char *description;
272− void *type_data[2];
273− void *payload;
272+ void *payload[4];
274273 const void *data;
275274 size_t datalen;
276275 size_t quotalen;
@@ -283,16 +282,18 @@ mandatory: · 6 unmodified lines
283282 not theirs.
284283
285284 If the parser is happy with the blob, it should propose a description for
286− the key and attach it to ->description, ->type_data[0] should be set to
287− point to the subtype to be used, ->payload should be set to point to the
288− initialised data for that subtype, ->type_data[1] should point to a hex
289− fingerprint and quotalen should be updated to indicate how much quota this
290− key should account for.
291−
292− When clearing up, the data attached to ->type_data[1] and ->description
293− will be kfree()'d and the data attached to ->payload will be passed to the
294− subtype's ->destroy() method to be disposed of. A module reference for
295− the subtype pointed to by ->type_data[0] will be put.
285+ the key and attach it to ->description, ->payload[asym_subtype] should be
286+ set to point to the subtype to be used, ->payload[asym_crypto] should be
287+ set to point to the initialised data for that subtype,
288+ ->payload[asym_key_ids] should point to one or more hex fingerprints and
289+ quotalen should be updated to indicate how much quota this key should
290+ account for.
291+
292+ When clearing up, the data attached to ->payload[asym_key_ids] and
293+ ->description will be kfree()'d and the data attached to
294+ ->payload[asm_crypto] will be passed to the subtype's ->destroy() method
295+ to be disposed of. A module reference for the subtype pointed to by
296+ ->payload[asym_subtype] will be put.
296297
297298
298299 If the data format is not recognised, -EBADMSG should be returned. If it
Documentation/device-mapper/delay.txt+1−0
@@ -8,6 +8,7 @@ Parameters: · 7 unmodified lines
88 <device> <offset> <delay> [<write_device> <write_offset> <write_delay>]
99
1010 With separate write parameters, the first set is only used for reads.
11+Offsets are specified in sectors.
1112 Delays are specified in milliseconds.
1213
1314 Example scripts
Documentation/device-mapper/snapshot.txt+7−3
@@ -41,9 +41,13 @@ useless and be disabled, returning errors. So it is important to monitor · 40 unmodified lines
4141 the amount of free space and expand the <COW device> before it fills up.
4242
4343 <persistent?> is P (Persistent) or N (Not persistent - will not survive
44−after reboot).
45−The difference is that for transient snapshots less metadata must be
46−saved on disk - they can be kept in memory by the kernel.
44+after reboot). O (Overflow) can be added as a persistent store option
45+to allow userspace to advertise its support for seeing "Overflow" in the
46+snapshot status. So supported store types are "P", "PO" and "N".
47+
48+The difference between persistent and transient is with transient
49+snapshots less metadata must be saved on disk - they can be kept in
50+memory by the kernel.
4751
4852
4953 * snapshot-merge <origin> <COW device> <persistent> <chunksize>
Documentation/devicetree/bindings/arm/amlogic.txt+8−2
@@ -9,6 +9,12 @@ Boards with the Amlogic Meson8 SoC shall have the following properties: · 8 unmodified lines
99 Required root node property:
1010 compatible: "amlogic,meson8";
1111
12+Boards with the Amlogic Meson8b SoC shall have the following properties:
13+ Required root node property:
14+ compatible: "amlogic,meson8b";
15+
1216 Board compatible values:
13− - "geniatech,atv1200"
14− - "minix,neo-x8"
17+ - "geniatech,atv1200" (Meson6)
18+ - "minix,neo-x8" (Meson8)
19+ - "tronfy,mxq" (Meson8b)
20+ - "hardkernel,odroid-c1" (Meson8b)
Documentation/devicetree/bindings/arm/apm/scu.txt+17−0
@@ -0,0 +1,17 @@
1+APM X-GENE SoC series SCU Registers
2+
3+This system clock unit contain various register that control block resets,
4+clock enable/disables, clock divisors and other deepsleep registers.
5+
6+Properties:
7+ - compatible : should contain two values. First value must be:
8+ - "apm,xgene-scu"
9+ second value must be always "syscon".
10+
11+ - reg : offset and length of the register set.
12+
13+Example :
14+ scu: system-clk-controller@17000000 {
15+ compatible = "apm,xgene-scu","syscon";
16+ reg = <0x0 0x17000000 0x0 0x400>;
17+ };
Documentation/devicetree/bindings/arm/arm,scpi.txt+188−0
@@ -0,0 +1,188 @@
1+System Control and Power Interface (SCPI) Message Protocol
2+----------------------------------------------------------
3+
4+Firmware implementing the SCPI described in ARM document number ARM DUI 0922B
5+("ARM Compute Subsystem SCP: Message Interface Protocols")[0] can be used
6+by Linux to initiate various system control and power operations.
7+
8+Required properties:
9+
10+- compatible : should be "arm,scpi"
11+- mboxes: List of phandle and mailbox channel specifiers
12+ All the channels reserved by remote SCP firmware for use by
13+ SCPI message protocol should be specified in any order
14+- shmem : List of phandle pointing to the shared memory(SHM) area between the
15+ processors using these mailboxes for IPC, one for each mailbox
16+ SHM can be any memory reserved for the purpose of this communication
17+ between the processors.
18+
19+See Documentation/devicetree/bindings/mailbox/mailbox.txt
20+for more details about the generic mailbox controller and
21+client driver bindings.
22+
23+Clock bindings for the clocks based on SCPI Message Protocol
24+------------------------------------------------------------
25+
26+This binding uses the common clock binding[1].
27+
28+Container Node
29+==============
30+Required properties:
31+- compatible : should be "arm,scpi-clocks"
32+ All the clocks provided by SCP firmware via SCPI message
33+ protocol much be listed as sub-nodes under this node.
34+
35+Sub-nodes
36+=========
37+Required properties:
38+- compatible : shall include one of the following
39+ "arm,scpi-dvfs-clocks" - all the clocks that are variable and index based.
40+ These clocks don't provide an entire range of values between the
41+ limits but only discrete points within the range. The firmware
42+ provides the mapping for each such operating frequency and the
43+ index associated with it. The firmware also manages the
44+ voltage scaling appropriately with the clock scaling.
45+ "arm,scpi-variable-clocks" - all the clocks that are variable and provide full
46+ range within the specified range. The firmware provides the
47+ range of values within a specified range.
48+
49+Other required properties for all clocks(all from common clock binding):
50+- #clock-cells : Should be 1. Contains the Clock ID value used by SCPI commands.
51+- clock-output-names : shall be the corresponding names of the outputs.
52+- clock-indices: The identifying number for the clocks(i.e.clock_id) in the
53+ node. It can be non linear and hence provide the mapping of identifiers
54+ into the clock-output-names array.
55+
56+SRAM and Shared Memory for SCPI
57+-------------------------------
58+
59+A small area of SRAM is reserved for SCPI communication between application
60+processors and SCP.
61+
62+Required properties:
63+- compatible : should be "arm,juno-sram-ns" for Non-secure SRAM on Juno
64+
65+The rest of the properties should follow the generic mmio-sram description
66+found in ../../misc/sysram.txt
67+
68+Each sub-node represents the reserved area for SCPI.
69+
70+Required sub-node properties:
71+- reg : The base offset and size of the reserved area with the SRAM
72+- compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based
73+ shared memory on Juno platforms
74+
75+Sensor bindings for the sensors based on SCPI Message Protocol
76+--------------------------------------------------------------
77+SCPI provides an API to access the various sensors on the SoC.
78+
79+Required properties:
80+- compatible : should be "arm,scpi-sensors".
81+- #thermal-sensor-cells: should be set to 1. This property follows the
82+ thermal device tree bindings[2].
83+
84+ Valid cell values are raw identifiers (Sensor
85+ ID) as used by the firmware. Refer to
86+ platform documentation for your
87+ implementation for the IDs to use. For Juno
88+ R0 and Juno R1 refer to [3].
89+
90+[0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html
91+[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
92+[2] Documentation/devicetree/bindings/thermal/thermal.txt
93+[3] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html
94+
95+Example:
96+
97+sram: sram@50000000 {
98+ compatible = "arm,juno-sram-ns", "mmio-sram";
99+ reg = <0x0 0x50000000 0x0 0x10000>;
100+
101+ #address-cells = <1>;
102+ #size-cells = <1>;
103+ ranges = <0 0x0 0x50000000 0x10000>;
104+
105+ cpu_scp_lpri: scp-shmem@0 {
106+ compatible = "arm,juno-scp-shmem";
107+ reg = <0x0 0x200>;
108+ };
109+
110+ cpu_scp_hpri: scp-shmem@200 {
111+ compatible = "arm,juno-scp-shmem";
112+ reg = <0x200 0x200>;
113+ };
114+};
115+
116+mailbox: mailbox0@40000000 {
117+ ....
118+ #mbox-cells = <1>;
119+};
120+
121+scpi_protocol: scpi@2e000000 {
122+ compatible = "arm,scpi";
123+ mboxes = <&mailbox 0 &mailbox 1>;
124+ shmem = <&cpu_scp_lpri &cpu_scp_hpri>;
125+
126+ clocks {
127+ compatible = "arm,scpi-clocks";
128+
129+ scpi_dvfs: scpi_clocks@0 {
130+ compatible = "arm,scpi-dvfs-clocks";
131+ #clock-cells = <1>;
132+ clock-indices = <0>, <1>, <2>;
133+ clock-output-names = "atlclk", "aplclk","gpuclk";
134+ };
135+ scpi_clk: scpi_clocks@3 {
136+ compatible = "arm,scpi-variable-clocks";
137+ #clock-cells = <1>;
138+ clock-indices = <3>, <4>;
139+ clock-output-names = "pxlclk0", "pxlclk1";
140+ };
141+ };
142+
143+ scpi_sensors0: sensors {
144+ compatible = "arm,scpi-sensors";
145+ #thermal-sensor-cells = <1>;
146+ };
147+};
148+
149+cpu@0 {
150+ ...
151+ reg = <0 0>;
152+ clocks = <&scpi_dvfs 0>;
153+};
154+
155+hdlcd@7ff60000 {
156+ ...
157+ reg = <0 0x7ff60000 0 0x1000>;
158+ clocks = <&scpi_clk 4>;
159+};
160+
161+thermal-zones {
162+ soc_thermal {
163+ polling-delay-passive = <100>;
164+ polling-delay = <1000>;
165+
166+ /* sensor ID */
167+ thermal-sensors = <&scpi_sensors0 3>;
168+ ...
169+ };
170+};
171+
172+In the above example, the #clock-cells is set to 1 as required.
173+scpi_dvfs has 3 output clocks namely: atlclk, aplclk, and gpuclk with 0,
174+1 and 2 as clock-indices. scpi_clk has 2 output clocks namely: pxlclk0
175+and pxlclk1 with 3 and 4 as clock-indices.
176+
177+The first consumer in the example is cpu@0 and it has '0' as the clock
178+specifier which points to the first entry in the output clocks of
179+scpi_dvfs i.e. "atlclk".
180+
181+Similarly the second example is hdlcd@7ff60000 and it has pxlclk1 as input
182+clock. '4' in the clock specifier here points to the second entry
183+in the output clocks of scpi_clocks i.e. "pxlclk1"
184+
185+The thermal-sensors property in the soc_thermal node uses the
186+temperature sensor provided by SCP firmware to setup a thermal
187+zone. The ID "3" is the sensor identifier for the temperature sensor
188+as used by the firmware.
Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt+160−2
@@ -20,6 +20,25 @@ system control is required: · 19 unmodified lines
2020 - compatible: "brcm,bcm<chip_id>-hif-cpubiuctrl", "syscon"
2121 - compatible: "brcm,bcm<chip_id>-hif-continuation", "syscon"
2222
23+hif-cpubiuctrl node
24+-------------------
25+SoCs with Broadcom Brahma15 ARM-based CPUs have a specific Bus Interface Unit
26+(BIU) block which controls and interfaces the CPU complex to the different
27+Memory Controller Ports (MCP), one per memory controller (MEMC). This BIU block
28+offers a feature called Write Pairing which consists in collapsing two adjacent
29+cache lines into a single (bursted) write transaction towards the memory
30+controller (MEMC) to maximize write bandwidth.
31+
32+Required properties:
33+
34+ - compatible: must be "brcm,bcm7445-hif-cpubiuctrl", "syscon"
35+
36+Optional properties:
37+
38+ - brcm,write-pairing:
39+ Boolean property, which when present indicates that the chip
40+ supports write-pairing.
41+
2342 example:
2443 rdb {
2544 #address-cells = <1>;
@@ -35,6 +54,7 @@ example: · 9 unmodified lines
3554 hif_cpubiuctrl: syscon@3e2400 {
3655 compatible = "brcm,bcm7445-hif-cpubiuctrl", "syscon";
3756 reg = <0x3e2400 0x5b4>;
57+ brcm,write-pairing;
3858 };
3959
4060 hif_continuation: syscon@452000 {
@@ -43,8 +63,7 @@ example: · 2 unmodified lines
4363 };
4464 };
4565
46−Lastly, nodes that allow for support of SMP initialization and reboot are
47−required:
66+Nodes that allow for support of SMP initialization and reboot are required:
4867
4968 smpboot
5069 -------
@@ -95,3 +114,142 @@ example: · 44 unmodified lines
95114 compatible = "brcm,brcmstb-reboot";
96115 syscon = <&sun_top_ctrl 0x304 0x308>;
97116 };
117+
118+
119+
120+Power management
121+----------------
122+
123+For power management (particularly, S2/S3/S5 system suspend), the following SoC
124+components are needed:
125+
126+= Always-On control block (AON CTRL)
127+
128+This hardware provides control registers for the "always-on" (even in low-power
129+modes) hardware, such as the Power Management State Machine (PMSM).
130+
131+Required properties:
132+- compatible : should contain "brcm,brcmstb-aon-ctrl"
133+- reg : the register start and length for the AON CTRL block
134+
135+Example:
136+
137+aon-ctrl@410000 {
138+ compatible = "brcm,brcmstb-aon-ctrl";
139+ reg = <0x410000 0x400>;
140+};
141+
142+= Memory controllers
143+
144+A Broadcom STB SoC typically has a number of independent memory controllers,
145+each of which may have several associated hardware blocks, which are versioned
146+independently (control registers, DDR PHYs, etc.). One might consider
147+describing these controllers as a parent "memory controllers" block, which
148+contains N sub-nodes (one for each controller in the system), each of which is
149+associated with a number of hardware register resources (e.g., its PHY). See
150+the example device tree snippet below.
151+
152+== MEMC (MEMory Controller)
153+
154+Represents a single memory controller instance.
155+
156+Required properties:
157+- compatible : should contain "brcm,brcmstb-memc" and "simple-bus"
158+
159+Should contain subnodes for any of the following relevant hardware resources:
160+
161+== DDR PHY control
162+
163+Control registers for this memory controller's DDR PHY.
164+
165+Required properties:
166+- compatible : should contain one of these
167+ "brcm,brcmstb-ddr-phy-v225.1"
168+ "brcm,brcmstb-ddr-phy-v240.1"
169+ "brcm,brcmstb-ddr-phy-v240.2"
170+
171+- reg : the DDR PHY register range
172+
173+== DDR SHIMPHY
174+
175+Control registers for this memory controller's DDR SHIMPHY.
176+
177+Required properties:
178+- compatible : should contain "brcm,brcmstb-ddr-shimphy-v1.0"
179+- reg : the DDR SHIMPHY register range
180+
181+== MEMC DDR control
182+
183+Sequencer DRAM parameters and control registers. Used for Self-Refresh
184+Power-Down (SRPD), among other things.
185+
186+Required properties:
187+- compatible : should contain "brcm,brcmstb-memc-ddr"
188+- reg : the MEMC DDR register range
189+
190+Example:
191+
192+memory_controllers {
193+ ranges;
194+ compatible = "simple-bus";
195+
196+ memc@0 {
197+ compatible = "brcm,brcmstb-memc", "simple-bus";
198+ ranges;
199+
200+ ddr-phy@f1106000 {
201+ compatible = "brcm,brcmstb-ddr-phy-v240.1";
202+ reg = <0xf1106000 0x21c>;
203+ };
204+
205+ shimphy@f1108000 {
206+ compatible = "brcm,brcmstb-ddr-shimphy-v1.0";
207+ reg = <0xf1108000 0xe4>;
208+ };
209+
210+ memc-ddr@f1102000 {
211+ reg = <0xf1102000 0x800>;
212+ compatible = "brcm,brcmstb-memc-ddr";
213+ };
214+ };
215+
216+ memc@1 {
217+ compatible = "brcm,brcmstb-memc", "simple-bus";
218+ ranges;
219+
220+ ddr-phy@f1186000 {
221+ compatible = "brcm,brcmstb-ddr-phy-v240.1";
222+ reg = <0xf1186000 0x21c>;
223+ };
224+
225+ shimphy@f1188000 {
226+ compatible = "brcm,brcmstb-ddr-shimphy-v1.0";
227+ reg = <0xf1188000 0xe4>;
228+ };
229+
230+ memc-ddr@f1182000 {
231+ reg = <0xf1182000 0x800>;
232+ compatible = "brcm,brcmstb-memc-ddr";
233+ };
234+ };
235+
236+ memc@2 {
237+ compatible = "brcm,brcmstb-memc", "simple-bus";
238+ ranges;
239+
240+ ddr-phy@f1206000 {
241+ compatible = "brcm,brcmstb-ddr-phy-v240.1";
242+ reg = <0xf1206000 0x21c>;
243+ };
244+
245+ shimphy@f1208000 {
246+ compatible = "brcm,brcmstb-ddr-shimphy-v1.0";
247+ reg = <0xf1208000 0xe4>;
248+ };
249+
250+ memc-ddr@f1202000 {
251+ reg = <0xf1202000 0x800>;
252+ compatible = "brcm,brcmstb-memc-ddr";
253+ };
254+ };
255+};
Documentation/devicetree/bindings/arm/bcm/brcm,nsp.txt+34−0
@@ -0,0 +1,34 @@
1+Broadcom Northstar Plus device tree bindings
2+--------------------------------------------
3+
4+Broadcom Northstar Plus family of SoCs are used for switching control
5+and management applications as well as residential router/gateway
6+applications. The SoC features dual core Cortex A9 ARM CPUs, integrating
7+several peripheral interfaces including multiple Gigabit Ethernet PHYs,
8+DDR3 memory, PCIE Gen-2, USB 2.0 and USB 3.0, serial and NAND flash,
9+SATA and several other IO controllers.
10+
11+Boards with Northstar Plus SoCs shall have the following properties:
12+
13+Required root node property:
14+
15+BCM58522
16+compatible = "brcm,bcm58522", "brcm,nsp";
17+
18+BCM58525
19+compatible = "brcm,bcm58525", "brcm,nsp";
20+
21+BCM58535
22+compatible = "brcm,bcm58535", "brcm,nsp";
23+
24+BCM58622
25+compatible = "brcm,bcm58622", "brcm,nsp";
26+
27+BCM58623
28+compatible = "brcm,bcm58623", "brcm,nsp";
29+
30+BCM58625
31+compatible = "brcm,bcm58625", "brcm,nsp";
32+
33+BCM88312
34+compatible = "brcm,bcm88312", "brcm,nsp";
Documentation/devicetree/bindings/arm/coherency-fabric.txt+5−0
@@ -27,6 +27,11 @@ Required properties: · 26 unmodified lines
2727 * For "marvell,armada-380-coherency-fabric", only one pair is needed
2828 for the per-CPU fabric registers.
2929
30+Optional properties:
31+
32+- broken-idle: boolean to set when the Idle mode is not supported by the
33+ hardware.
34+
3035 Examples:
3136
3237 coherency-fabric@d0020200 {
Documentation/devicetree/bindings/arm/cpus.txt+2−0
@@ -195,6 +195,8 @@ nodes to be present and contain the properties described below. · 194 unmodified lines
195195 "marvell,armada-380-smp"
196196 "marvell,armada-390-smp"
197197 "marvell,armada-xp-smp"
198+ "mediatek,mt6589-smp"
199+ "mediatek,mt81xx-tz-smp"
198200 "qcom,gcc-msm8660"
199201 "qcom,kpss-acc-v1"
200202 "qcom,kpss-acc-v2"
Documentation/devicetree/bindings/arm/fsl.txt+12−4
@@ -128,10 +128,18 @@ Example: · 127 unmodified lines
128128 reg = <0x0 0x1ee0000 0x0 0x10000>;
129129 };
130130
131−Freescale LS2085A SoC Device Tree Bindings
132−------------------------------------------
131+Freescale ARMv8 based Layerscape SoC family Device Tree Bindings
132+----------------------------------------------------------------
133133
134−LS2085A ARMv8 based Simulator model
134+LS2080A ARMv8 based Simulator model
135135 Required root node properties:
136− - compatible = "fsl,ls2085a-simu", "fsl,ls2085a";
136+ - compatible = "fsl,ls2080a-simu", "fsl,ls2080a";
137+
138+LS2080A ARMv8 based QDS Board
139+Required root node properties:
140+ - compatible = "fsl,ls2080a-qds", "fsl,ls2080a";
141+
142+LS2080A ARMv8 based RDB Board
143+Required root node properties:
144+ - compatible = "fsl,ls2080a-rdb", "fsl,ls2080a";
137145
Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt+21−0
@@ -20,6 +20,10 @@ HiKey Board · 19 unmodified lines
2020 Required root node properties:
2121 - compatible = "hisilicon,hi6220-hikey", "hisilicon,hi6220";
2222
23+HiP05 D02 Board
24+Required root node properties:
25+ - compatible = "hisilicon,hip05-d02";
26+
2327 Hisilicon system controller
2428
2529 Required properties:
@@ -166,6 +170,23 @@ Example: · 140 unmodified lines
166170 reboot-offset = <0x4>;
167171 };
168172
173+-----------------------------------------------------------------------
174+Hisilicon HiP05 PCIe-SAS system controller
175+
176+Required properties:
177+- compatible : "hisilicon,pcie-sas-subctrl", "syscon";
178+- reg : Register address and size
179+
180+The HiP05 PCIe-SAS system controller is shared by PCIe and SAS controllers in
181+HiP05 Soc to implement some basic configurations.
182+
183+Example:
184+ /* for HiP05 PCIe-SAS system */
185+ pcie_sas: system_controller@0xb0000000 {
186+ compatible = "hisilicon,pcie-sas-subctrl", "syscon";
187+ reg = <0xb0000000 0x10000>;
188+ };
189+
169190 -----------------------------------------------------------------------
170191 Hisilicon CPU controller
171192
Documentation/devicetree/bindings/arm/keystone/keystone.txt+17−3
@@ -9,12 +9,26 @@ Required properties: · 8 unmodified lines
99 the form "ti,keystone-*". Generic devices like gic, arch_timers, ns16550
1010 type UART should use the specified compatible for those devices.
1111
12+SoC families:
13+
14+- Keystone 2 generic SoC:
15+ compatible = "ti,keystone"
16+
17+SoCs:
18+
19+- Keystone 2 Hawking/Kepler
20+ compatible = "ti,k2hk", "ti,keystone"
21+- Keystone 2 Lamarr
22+ compatible = "ti,k2l", "ti,keystone"
23+- Keystone 2 Edison
24+ compatible = "ti,k2e", "ti,keystone"
25+
1226 Boards:
1327 - Keystone 2 Hawking/Kepler EVM
14− compatible = "ti,k2hk-evm","ti,keystone"
28+ compatible = "ti,k2hk-evm", "ti,k2hk", "ti,keystone"
1529
1630 - Keystone 2 Lamarr EVM
17− compatible = "ti,k2l-evm","ti,keystone"
31+ compatible = "ti,k2l-evm", "ti, k2l", "ti,keystone"
1832
1933 - Keystone 2 Edison EVM
20− compatible = "ti,k2e-evm","ti,keystone"
34+ compatible = "ti,k2e-evm", "ti,k2e", "ti,keystone"
Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt+22−0
@@ -0,0 +1,22 @@
1+Mediatek imgsys controller
2+============================
3+
4+The Mediatek imgsys controller provides various clocks to the system.
5+
6+Required Properties:
7+
8+- compatible: Should be:
9+ - "mediatek,mt8173-imgsys", "syscon"
10+- #clock-cells: Must be 1
11+
12+The imgsys controller uses the common clk binding from
13+Documentation/devicetree/bindings/clock/clock-bindings.txt
14+The available clocks are defined in dt-bindings/clock/mt*-clk.h.
15+
16+Example:
17+
18+imgsys: clock-controller@15000000 {
19+ compatible = "mediatek,mt8173-imgsys", "syscon";
20+ reg = <0 0x15000000 0 0x1000>;
21+ #clock-cells = <1>;
22+};
Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt+22−0
@@ -0,0 +1,22 @@
1+Mediatek mmsys controller
2+============================
3+
4+The Mediatek mmsys controller provides various clocks to the system.
5+
6+Required Properties:
7+
8+- compatible: Should be:
9+ - "mediatek,mt8173-mmsys", "syscon"
10+- #clock-cells: Must be 1
11+
12+The mmsys controller uses the common clk binding from
13+Documentation/devicetree/bindings/clock/clock-bindings.txt
14+The available clocks are defined in dt-bindings/clock/mt*-clk.h.
15+
16+Example:
17+
18+mmsys: clock-controller@14000000 {
19+ compatible = "mediatek,mt8173-mmsys", "syscon";
20+ reg = <0 0x14000000 0 0x1000>;
21+ #clock-cells = <1>;
22+};
Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt+22−0
@@ -0,0 +1,22 @@
1+Mediatek vdecsys controller
2+============================
3+
4+The Mediatek vdecsys controller provides various clocks to the system.
5+
6+Required Properties:
7+
8+- compatible: Should be:
9+ - "mediatek,mt8173-vdecsys", "syscon"
10+- #clock-cells: Must be 1
11+
12+The vdecsys controller uses the common clk binding from
13+Documentation/devicetree/bindings/clock/clock-bindings.txt
14+The available clocks are defined in dt-bindings/clock/mt*-clk.h.
15+
16+Example:
17+
18+vdecsys: clock-controller@16000000 {
19+ compatible = "mediatek,mt8173-vdecsys", "syscon";
20+ reg = <0 0x16000000 0 0x1000>;
21+ #clock-cells = <1>;
22+};
Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt+22−0
@@ -0,0 +1,22 @@
1+Mediatek vencltsys controller
2+============================
3+
4+The Mediatek vencltsys controller provides various clocks to the system.
5+
6+Required Properties:
7+
8+- compatible: Should be:
9+ - "mediatek,mt8173-vencltsys", "syscon"
10+- #clock-cells: Must be 1
11+
12+The vencltsys controller uses the common clk binding from
13+Documentation/devicetree/bindings/clock/clock-bindings.txt
14+The available clocks are defined in dt-bindings/clock/mt*-clk.h.
15+
16+Example:
17+
18+vencltsys: clock-controller@19000000 {
19+ compatible = "mediatek,mt8173-vencltsys", "syscon";
20+ reg = <0 0x19000000 0 0x1000>;
21+ #clock-cells = <1>;
22+};
Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt+22−0
@@ -0,0 +1,22 @@
1+Mediatek vencsys controller
2+============================
3+
4+The Mediatek vencsys controller provides various clocks to the system.
5+
6+Required Properties:
7+
8+- compatible: Should be:
9+ - "mediatek,mt8173-vencsys", "syscon"
10+- #clock-cells: Must be 1
11+
12+The vencsys controller uses the common clk binding from
13+Documentation/devicetree/bindings/clock/clock-bindings.txt
14+The available clocks are defined in dt-bindings/clock/mt*-clk.h.
15+
16+Example:
17+
18+vencsys: clock-controller@18000000 {
19+ compatible = "mediatek,mt8173-vencsys", "syscon";
20+ reg = <0 0x18000000 0 0x1000>;
21+ #clock-cells = <1>;
22+};
Documentation/devicetree/bindings/arm/mvebu-cpu-config.txt+20−0
@@ -0,0 +1,20 @@
1+MVEBU CPU Config registers
2+--------------------------
3+
4+MVEBU (Marvell SOCs: Armada 370/XP)
5+
6+Required properties:
7+
8+- compatible: one of:
9+ - "marvell,armada-370-cpu-config"
10+ - "marvell,armada-xp-cpu-config"
11+
12+- reg: Should contain CPU config registers location and length, in
13+ their per-CPU variant
14+
15+Example:
16+
17+ cpu-config@21000 {
18+ compatible = "marvell,armada-xp-cpu-config";
19+ reg = <0x21000 0x8>;
20+ };
Documentation/devicetree/bindings/arm/pmu.txt+3−0
@@ -7,7 +7,10 @@ representation in the device tree should be done as under:- · 6 unmodified lines
77 Required properties:
88
99 - compatible : should be one of
10+ "apm,potenza-pmu"
1011 "arm,armv8-pmuv3"
12+ "arm.cortex-a57-pmu"
13+ "arm.cortex-a53-pmu"
1114 "arm,cortex-a17-pmu"
1215 "arm,cortex-a15-pmu"
1316 "arm,cortex-a12-pmu"
Documentation/devicetree/bindings/arm/psci.txt+6−0
@@ -31,6 +31,10 @@ Main node required properties: · 30 unmodified lines
3131 support, but are permitted to be present for compatibility with
3232 existing software when "arm,psci" is later in the compatible list.
3333
34+ * "arm,psci-1.0" : for implementations complying to PSCI 1.0. PSCI 1.0 is
35+ backward compatible with PSCI 0.2 with minor specification updates,
36+ as defined in the PSCI specification[2].
37+
3438 - method : The method of calling the PSCI firmware. Permitted
3539 values are:
3640
@@ -100,3 +104,5 @@ Case 3: PSCI v0.2 and PSCI v0.1. · 63 unmodified lines
100104
101105 [1] Kernel documentation - ARM idle states bindings
102106 Documentation/devicetree/bindings/arm/idle-states.txt
107+[2] Power State Coordination Interface (PSCI) specification
108+ http://infocenter.arm.com/help/topic/com.arm.doc.den0022c/DEN0022C_Power_State_Coordination_Interface.pdf
Documentation/devicetree/bindings/arm/rockchip.txt+11−0
@@ -17,6 +17,10 @@ Rockchip platforms device tree bindings · 16 unmodified lines
1717 Required root node properties:
1818 - compatible = "radxa,rock", "rockchip,rk3188";
1919
20+- Radxa Rock2 Square board:
21+ Required root node properties:
22+ - compatible = "radxa,rock2-square", "rockchip,rk3288";
23+
2024 - Firefly Firefly-RK3288 board:
2125 Required root node properties:
2226 - compatible = "firefly,firefly-rk3288", "rockchip,rk3288";
@@ -31,6 +35,13 @@ Rockchip platforms device tree bindings · 8 unmodified lines
3135 Required root node properties:
3236 - compatible = "netxeon,r89", "rockchip,rk3288";
3337
38+- Google Jaq (Haier Chromebook 11 and more):
39+ Required root node properties:
40+ - compatible = "google,veyron-jaq-rev5", "google,veyron-jaq-rev4",
41+ "google,veyron-jaq-rev3", "google,veyron-jaq-rev2",
42+ "google,veyron-jaq-rev1", "google,veyron-jaq",
43+ "google,veyron", "rockchip,rk3288";
44+
3445 - Google Jerry (Hisense Chromebook C11 and more):
3546 Required root node properties:
3647 - compatible = "google,veyron-jerry-rev7", "google,veyron-jerry-rev6",
Documentation/devicetree/bindings/arm/samsung-boards.txt+0−27
@@ -1,27 +0,0 @@
1−* Samsung's Exynos SoC based boards
2−
3−Required root node properties:
4− - compatible = should be one or more of the following.
5− - "samsung,monk" - for Exynos3250-based Samsung Simband board.
6− - "samsung,rinato" - for Exynos3250-based Samsung Gear2 board.
7− - "samsung,smdkv310" - for Exynos4210-based Samsung SMDKV310 eval board.
8− - "samsung,trats" - for Exynos4210-based Tizen Reference board.
9− - "samsung,universal_c210" - for Exynos4210-based Samsung board.
10− - "samsung,smdk4412", - for Exynos4412-based Samsung SMDK4412 eval board.
11− - "samsung,trats2" - for Exynos4412-based Tizen Reference board.
12− - "samsung,smdk5250" - for Exynos5250-based Samsung SMDK5250 eval board.
13− - "samsung,xyref5260" - for Exynos5260-based Samsung board.
14− - "samsung,smdk5410" - for Exynos5410-based Samsung SMDK5410 eval board.
15− - "samsung,smdk5420" - for Exynos5420-based Samsung SMDK5420 eval board.
16− - "samsung,sd5v1" - for Exynos5440-based Samsung board.
17− - "samsung,ssdk5440" - for Exynos5440-based Samsung board.
18−
19−Optional:
20− - firmware node, specifying presence and type of secure firmware:
21− - compatible: only "samsung,secure-firmware" is currently supported
22− - reg: address of non-secure SYSRAM used for communication with firmware
23−
24− firmware@0203F000 {
25− compatible = "samsung,secure-firmware";
26− reg = <0x0203F000 0x1000>;
27− };
Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt+69−0
@@ -0,0 +1,69 @@
1+* Samsung's Exynos SoC based boards
2+
3+Required root node properties:
4+ - compatible = should be one or more of the following.
5+ - "samsung,monk" - for Exynos3250-based Samsung Simband board.
6+ - "samsung,rinato" - for Exynos3250-based Samsung Gear2 board.
7+ - "samsung,smdkv310" - for Exynos4210-based Samsung SMDKV310 eval board.
8+ - "samsung,trats" - for Exynos4210-based Tizen Reference board.
9+ - "samsung,universal_c210" - for Exynos4210-based Samsung board.
10+ - "samsung,smdk4412", - for Exynos4412-based Samsung SMDK4412 eval board.
11+ - "samsung,trats2" - for Exynos4412-based Tizen Reference board.
12+ - "samsung,smdk5250" - for Exynos5250-based Samsung SMDK5250 eval board.
13+ - "samsung,xyref5260" - for Exynos5260-based Samsung board.
14+ - "samsung,smdk5410" - for Exynos5410-based Samsung SMDK5410 eval board.
15+ - "samsung,smdk5420" - for Exynos5420-based Samsung SMDK5420 eval board.
16+ - "samsung,sd5v1" - for Exynos5440-based Samsung board.
17+ - "samsung,ssdk5440" - for Exynos5440-based Samsung board.
18+
19+* Other companies Exynos SoC based
20+ * FriendlyARM
21+ - "friendlyarm,tiny4412" - for Exynos4412-based FriendlyARM
22+ TINY4412 board.
23+
24+ * Google
25+ - "google,pi" - for Exynos5800-based Google Peach Pi
26+ Rev 10+ board,
27+ also: "google,pi-rev16", "google,pi-rev15", "google,pi-rev14",
28+ "google,pi-rev13", "google,pi-rev12", "google,pi-rev11",
29+ "google,pi-rev10", "google,peach".
30+
31+ - "google,pit" - for Exynos5420-based Google Peach Pit
32+ Rev 6+ (Exynos5420),
33+ also: "google,pit-rev16", "google,pit-rev15", "google,pit-rev14",
34+ "google,pit-rev13", "google,pit-rev12", "google,pit-rev11",
35+ "google,pit-rev10", "google,pit-rev9", "google,pit-rev8",
36+ "google,pit-rev7", "google,pit-rev6", "google,peach".
37+
38+ - "google,snow-rev4" - for Exynos5250-based Google Snow board,
39+ also: "google,snow"
40+ - "google,snow-rev5" - for Exynos5250-based Google Snow
41+ Rev 5+ board.
42+ - "google,spring" - for Exynos5250-based Google Spring board.
43+
44+ * Hardkernel
45+ - "hardkernel,odroid-u3" - for Exynos4412-based Hardkernel Odroid U3.
46+ - "hardkernel,odroid-x" - for Exynos4412-based Hardkernel Odroid X.
47+ - "hardkernel,odroid-x2" - for Exynos4412-based Hardkernel Odroid X2.
48+ - "hardkernel,odroid-xu3" - for Exynos5422-based Hardkernel Odroid XU3.
49+ - "hardkernel,odroid-xu3-lite" - for Exynos5422-based Hardkernel
50+ Odroid XU3 Lite board.
51+ - "hardkernel,odroid-xu4" - for Exynos5422-based Hardkernel Odroid XU4.
52+
53+ * Insignal
54+ - "insignal,arndale" - for Exynos5250-based Insignal Arndale board.
55+ - "insignal,arndale-octa" - for Exynos5420-based Insignal Arndale
56+ Octa board.
57+ - "insignal,origen" - for Exynos4210-based Insignal Origen board.
58+ - "insignal,origen4412 - for Exynos4412-based Insignal Origen board.
59+
60+
61+Optional nodes:
62+ - firmware node, specifying presence and type of secure firmware:
63+ - compatible: only "samsung,secure-firmware" is currently supported
64+ - reg: address of non-secure SYSRAM used for communication with firmware
65+
66+ firmware@0203F000 {
67+ compatible = "samsung,secure-firmware";
68+ reg = <0x0203F000 0x1000>;
69+ };
Documentation/devicetree/bindings/arm/shmobile.txt+4−6
@@ -39,8 +39,6 @@ Boards: · 38 unmodified lines
3939 compatible = "renesas,armadillo800eva"
4040 - BOCK-W
4141 compatible = "renesas,bockw", "renesas,r8a7778"
42− - BOCK-W - Reference Device Tree Implementation
43− compatible = "renesas,bockw-reference", "renesas,r8a7778"
4442 - Genmai (RTK772100BC00000BR)
4543 compatible = "renesas,genmai", "renesas,r7s72100"
4644 - Gose
@@ -57,7 +55,7 @@ Boards: · 10 unmodified lines
5755 compatible = "renesas,lager", "renesas,r8a7790"
5856 - Marzen
5957 compatible = "renesas,marzen", "renesas,r8a7779"
60−
61−Note: Reference Device Tree Implementations are temporary implementations
62− to ease the migration from platform devices to Device Tree, and are
63− intended to be removed in the future.
58+ - Porter (M2-LCDP)
59+ compatible = "renesas,porter", "renesas,r8a7791"
60+ - SILK (RTP0RC7794LCB00011S)
61+ compatible = "renesas,silk", "renesas,r8a7794"
Documentation/devicetree/bindings/arm/sunxi.txt+1−0
@@ -6,6 +6,7 @@ using one of the following compatible strings: · 5 unmodified lines
66 allwinner,sun4i-a10
77 allwinner,sun5i-a10s
88 allwinner,sun5i-a13
9+ allwinner,sun5i-r8
910 allwinner,sun6i-a31
1011 allwinner,sun7i-a20
1112 allwinner,sun8i-a23
Documentation/devicetree/bindings/arm/tegra/nvidia,nvec.txtrenamed from Documentation/devicetree/bindings/nvec/nvidia,nvec.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/arm/twd.txt+5−0
@@ -19,6 +19,11 @@ interrupts. · 18 unmodified lines
1919 - reg : Specify the base address and the size of the TWD timer
2020 register window.
2121
22+Optional
23+
24+- always-on : a boolean property. If present, the timer is powered through
25+ an always-on power domain, therefore it never loses context.
26+
2227 Example:
2328
2429 twd-timer@2c000600 {
Documentation/devicetree/bindings/arm/uniphier/cache-uniphier.txt+60−0
@@ -0,0 +1,60 @@
1+UniPhier outer cache controller
2+
3+UniPhier SoCs are integrated with a full-custom outer cache controller system.
4+All of them have a level 2 cache controller, and some have a level 3 cache
5+controller as well.
6+
7+Required properties:
8+- compatible: should be "socionext,uniphier-system-cache"
9+- reg: offsets and lengths of the register sets for the device. It should
10+ contain 3 regions: control register, revision register, operation register,
11+ in this order.
12+- cache-unified: specifies the cache is a unified cache.
13+- cache-size: specifies the size in bytes of the cache
14+- cache-sets: specifies the number of associativity sets of the cache
15+- cache-line-size: specifies the line size in bytes
16+- cache-level: specifies the level in the cache hierarchy. The value should
17+ be 2 for L2 cache, 3 for L3 cache, etc.
18+
19+Optional properties:
20+- next-level-cache: phandle to the next level cache if present. The next level
21+ cache should be also compatible with "socionext,uniphier-system-cache".
22+
23+The L2 cache must exist to use the L3 cache; the cache hierarchy must be
24+indicated correctly with "next-level-cache" properties.
25+
26+Example 1 (system with L2):
27+ l2: l2-cache@500c0000 {
28+ compatible = "socionext,uniphier-system-cache";
29+ reg = <0x500c0000 0x2000>, <0x503c0100 0x4>,
30+ <0x506c0000 0x400>;
31+ cache-unified;
32+ cache-size = <0x80000>;
33+ cache-sets = <256>;
34+ cache-line-size = <128>;
35+ cache-level = <2>;
36+ };
37+
38+Example 2 (system with L2 and L3):
39+ l2: l2-cache@500c0000 {
40+ compatible = "socionext,uniphier-system-cache";
41+ reg = <0x500c0000 0x2000>, <0x503c0100 0x8>,
42+ <0x506c0000 0x400>;
43+ cache-unified;
44+ cache-size = <0x200000>;
45+ cache-sets = <512>;
46+ cache-line-size = <128>;
47+ cache-level = <2>;
48+ next-level-cache = <&l3>;
49+ };
50+
51+ l3: l3-cache@500c8000 {
52+ compatible = "socionext,uniphier-system-cache";
53+ reg = <0x500c8000 0x2000>, <0x503c8100 0x8>,
54+ <0x506c8000 0x400>;
55+ cache-unified;
56+ cache-size = <0x400000>;
57+ cache-sets = <512>;
58+ cache-line-size = <256>;
59+ cache-level = <3>;
60+ };
Documentation/devicetree/bindings/ata/ahci-fsl-qoriq.txt+21−0
@@ -0,0 +1,21 @@
1+Binding for Freescale QorIQ AHCI SATA Controller
2+
3+Required properties:
4+ - reg: Physical base address and size of the controller's register area.
5+ - compatible: Compatibility string. Must be 'fsl,<chip>-ahci', where
6+ chip could be ls1021a, ls2080a, ls1043a etc.
7+ - clocks: Input clock specifier. Refer to common clock bindings.
8+ - interrupts: Interrupt specifier. Refer to interrupt binding.
9+
10+Optional properties:
11+ - dma-coherent: Enable AHCI coherent DMA operation.
12+ - reg-names: register area names when there are more than 1 register area.
13+
14+Examples:
15+ sata@3200000 {
16+ compatible = "fsl,ls1021a-ahci";
17+ reg = <0x0 0x3200000 0x0 0x10000>;
18+ interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
19+ clocks = <&platform_clk 1>;
20+ dma-coherent;
21+ };
Documentation/devicetree/bindings/ata/ahci-platform.txt+0−2
@@ -16,8 +16,6 @@ Required properties: · 15 unmodified lines
1616 - "snps,dwc-ahci"
1717 - "snps,exynos5440-ahci"
1818 - "snps,spear-ahci"
19− - "fsl,qoriq-ahci" : for qoriq series socs which include ls1021, ls2085, etc.
20− - "fsl,<chip>-ahci" : chip could be ls1021, ls2085 etc.
2119 - "generic-ahci"
2220 - interrupts : <interrupt mapping for SATA IRQ>
2321 - reg : <registers mapping>
Documentation/devicetree/bindings/board/fsl-board.txtrenamed from Documentation/devicetree/bindings/powerpc/fsl/board.txt+12−2
@@ -21,11 +21,14 @@ Example: · 20 unmodified lines
2121
2222 This is the memory-mapped registers for on board FPGA.
2323
24−Required properities:
24+Required properties:
2525 - compatible: should be a board-specific string followed by a string
2626 indicating the type of FPGA. Example:
27− "fsl,<board>-fpga", "fsl,fpga-pixis"
27+ "fsl,<board>-fpga", "fsl,fpga-pixis", or
28+ "fsl,<board>-fpga", "fsl,fpga-qixis"
2829 - reg: should contain the address and the length of the FPGA register set.
30+
31+Optional properties:
2932 - interrupt-parent: should specify phandle for the interrupt controller.
3033 - interrupts: should specify event (wakeup) IRQ.
3134
@@ -38,6 +41,13 @@ Example (P1022DS): · 6 unmodified lines
3841 interrupts = <8 8 0 0>;
3942 };
4043
44+Example (LS2080A-RDB):
45+
46+ cpld@3,0 {
47+ compatible = "fsl,ls2080ardb-fpga", "fsl,fpga-qixis";
48+ reg = <0x3 0 0x10000>;
49+ };
50+
4151 * Freescale BCSR GPIO banks
4252
4353 Some BCSR registers act as simple GPIO controllers, each such
Documentation/devicetree/bindings/bus/sunxi-rsb.txt+47−0
@@ -0,0 +1,47 @@
1+Allwinner Reduced Serial Bus (RSB) controller
2+
3+The RSB controller found on later Allwinner SoCs is an SMBus like 2 wire
4+serial bus with 1 master and up to 15 slaves. It is represented by a node
5+for the controller itself, and child nodes representing the slave devices.
6+
7+Required properties :
8+
9+ - reg : Offset and length of the register set for the controller.
10+ - compatible : Shall be "allwinner,sun8i-a23-rsb".
11+ - interrupts : The interrupt line associated to the RSB controller.
12+ - clocks : The gate clk associated to the RSB controller.
13+ - resets : The reset line associated to the RSB controller.
14+ - #address-cells : shall be 1
15+ - #size-cells : shall be 0
16+
17+Optional properties :
18+
19+ - clock-frequency : Desired RSB bus clock frequency in Hz. Maximum is 20MHz.
20+ If not set this defaults to 3MHz.
21+
22+Child nodes:
23+
24+An RSB controller node can contain zero or more child nodes representing
25+slave devices on the bus. Child 'reg' properties should contain the slave
26+device's hardware address. The hardware address is hardwired in the device,
27+which can normally be found in the datasheet.
28+
29+Example:
30+
31+ rsb@01f03400 {
32+ compatible = "allwinner,sun8i-a23-rsb";
33+ reg = <0x01f03400 0x400>;
34+ interrupts = <0 39 4>;
35+ clocks = <&apb0_gates 3>;
36+ clock-frequency = <3000000>;
37+ resets = <&apb0_rst 3>;
38+ #address-cells = <1>;
39+ #size-cells = <0>;
40+
41+ pmic@3e3 {
42+ compatible = "...";
43+ reg = <0x3e3>;
44+
45+ /* ... */
46+ };
47+ };
Documentation/devicetree/bindings/chosen.txt+8−0
@@ -44,3 +44,11 @@ Implementation note: Linux will look for the property "linux,stdout-path" or · 43 unmodified lines
4444 on PowerPC "stdout" if "stdout-path" is not found. However, the
4545 "linux,stdout-path" and "stdout" properties are deprecated. New platforms
4646 should only use the "stdout-path" property.
47+
48+linux,booted-from-kexec
49+-----------------------
50+
51+This property is set (currently only on PowerPC, and only needed on
52+book3e) by some versions of kexec-tools to tell the new kernel that it
53+is being booted by kexec, as the booting environment may differ (e.g.
54+a different secondary CPU release mechanism)
Documentation/devicetree/bindings/clock/at91-clock.txt+35−0
@@ -77,6 +77,9 @@ Required properties: · 76 unmodified lines
7777 "atmel,sama5d4-clk-h32mx":
7878 at91 h32mx clock
7979
80+ "atmel,sama5d2-clk-generated":
81+ at91 generated clock
82+
8083 Required properties for SCKC node:
8184 - reg : defines the IO memory reserved for the SCKC.
8285 - #size-cells : shall be 0 (reg is used to encode clk id).
@@ -461,3 +464,35 @@ For example: · 378 unmodified lines
461464 compatible = "atmel,sama5d4-clk-h32mx";
462465 clocks = <&mck>;
463466 };
467+
468+Required properties for generated clocks:
469+- #size-cells : shall be 0 (reg is used to encode clk id).
470+- #address-cells : shall be 1 (reg is used to encode clk id).
471+- clocks : shall be the generated clock source phandles.
472+ e.g. clocks = <&clk32k>, <&main>, <&plladiv>, <&utmi>, <&mck>, <&audio_pll_pmc>;
473+- name: device tree node describing a specific generated clock.
474+ * #clock-cells : from common clock binding; shall be set to 0.
475+ * reg: peripheral id. See Atmel's datasheets to get a full
476+ list of peripheral ids.
477+ * atmel,clk-output-range : minimum and maximum clock frequency
478+ (two u32 fields).
479+
480+For example:
481+ gck {
482+ compatible = "atmel,sama5d2-clk-generated";
483+ #address-cells = <1>;
484+ #size-cells = <0>;
485+ clocks = <&clk32k>, <&main>, <&plladiv>, <&utmi>, <&mck>, <&audio_pll_pmc>;
486+
487+ tcb0_gclk: tcb0_gclk {
488+ #clock-cells = <0>;
489+ reg = <35>;
490+ atmel,clk-output-range = <0 83000000>;
491+ };
492+
493+ pwm_gclk: pwm_gclk {
494+ #clock-cells = <0>;
495+ reg = <38>;
496+ atmel,clk-output-range = <0 83000000>;
497+ };
498+ };
Documentation/devicetree/bindings/clock/brcm,bcm2835-cprman.txt+45−0
@@ -0,0 +1,45 @@
1+Broadcom BCM2835 CPRMAN clocks
2+
3+This binding uses the common clock binding:
4+ Documentation/devicetree/bindings/clock/clock-bindings.txt
5+
6+The CPRMAN clock controller generates clocks in the audio power domain
7+of the BCM2835. There is a level of PLLs deriving from an external
8+oscillator, a level of PLL dividers that produce channels off of the
9+few PLLs, and a level of mostly-generic clock generators sourcing from
10+the PLL channels. Most other hardware components source from the
11+clock generators, but a few (like the ARM or HDMI) will source from
12+the PLL dividers directly.
13+
14+Required properties:
15+- compatible: Should be "brcm,bcm2835-cprman"
16+- #clock-cells: Should be <1>. The permitted clock-specifier values can be
17+ found in include/dt-bindings/clock/bcm2835.h
18+- reg: Specifies base physical address and size of the registers
19+- clocks: The external oscillator clock phandle
20+
21+Example:
22+
23+ clk_osc: clock@3 {
24+ compatible = "fixed-clock";
25+ reg = <3>;
26+ #clock-cells = <0>;
27+ clock-output-names = "osc";
28+ clock-frequency = <19200000>;
29+ };
30+
31+ clocks: cprman@7e101000 {
32+ compatible = "brcm,bcm2835-cprman";
33+ #clock-cells = <1>;
34+ reg = <0x7e101000 0x2000>;
35+ clocks = <&clk_osc>;
36+ };
37+
38+ i2c0: i2c@7e205000 {
39+ compatible = "brcm,bcm2835-i2c";
40+ reg = <0x7e205000 0x1000>;
41+ interrupts = <2 21>;
42+ clocks = <&clocks BCM2835_CLOCK_VPU>;
43+ #address-cells = <1>;
44+ #size-cells = <0>;
45+ };
Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt+78−0
@@ -130,3 +130,81 @@ These clock IDs are defined in: · 129 unmodified lines
130130 ch3_unused mipipll 4 BCM_CYGNUS_MIPIPLL_CH3_UNUSED
131131 ch4_unused mipipll 5 BCM_CYGNUS_MIPIPLL_CH4_UNUSED
132132 ch5_unused mipipll 6 BCM_CYGNUS_MIPIPLL_CH5_UNUSED
133+
134+Northstar and Northstar Plus
135+------
136+PLL and leaf clock compatible strings for Northstar and Northstar Plus are:
137+ "brcm,nsp-armpll"
138+ "brcm,nsp-genpll"
139+ "brcm,nsp-lcpll0"
140+
141+The following table defines the set of PLL/clock index and ID for Northstar and
142+Northstar Plus. These clock IDs are defined in:
143+ "include/dt-bindings/clock/bcm-nsp.h"
144+
145+ Clock Source Index ID
146+ --- ----- ----- ---------
147+ crystal N/A N/A N/A
148+
149+ armpll crystal N/A N/A
150+
151+ genpll crystal 0 BCM_NSP_GENPLL
152+ phy genpll 1 BCM_NSP_GENPLL_PHY_CLK
153+ ethernetclk genpll 2 BCM_NSP_GENPLL_ENET_SW_CLK
154+ usbclk genpll 3 BCM_NSP_GENPLL_USB_PHY_REF_CLK
155+ iprocfast genpll 4 BCM_NSP_GENPLL_IPROCFAST_CLK
156+ sata1 genpll 5 BCM_NSP_GENPLL_SATA1_CLK
157+ sata2 genpll 6 BCM_NSP_GENPLL_SATA2_CLK
158+
159+ lcpll0 crystal 0 BCM_NSP_LCPLL0
160+ pcie_phy lcpll0 1 BCM_NSP_LCPLL0_PCIE_PHY_REF_CLK
161+ sdio lcpll0 2 BCM_NSP_LCPLL0_SDIO_CLK
162+ ddr_phy lcpll0 3 BCM_NSP_LCPLL0_DDR_PHY_CLK
163+
164+Northstar 2
165+-----------
166+PLL and leaf clock compatible strings for Northstar 2 are:
167+ "brcm,ns2-genpll-scr"
168+ "brcm,ns2-genpll-sw"
169+ "brcm,ns2-lcpll-ddr"
170+ "brcm,ns2-lcpll-ports"
171+
172+The following table defines the set of PLL/clock index and ID for Northstar 2.
173+These clock IDs are defined in:
174+ "include/dt-bindings/clock/bcm-ns2.h"
175+
176+ Clock Source Index ID
177+ --- ----- ----- ---------
178+ crystal N/A N/A N/A
179+
180+ genpll_scr crystal 0 BCM_NS2_GENPLL_SCR
181+ scr genpll_scr 1 BCM_NS2_GENPLL_SCR_SCR_CLK
182+ fs genpll_scr 2 BCM_NS2_GENPLL_SCR_FS_CLK
183+ audio_ref genpll_scr 3 BCM_NS2_GENPLL_SCR_AUDIO_CLK
184+ ch3_unused genpll_scr 4 BCM_NS2_GENPLL_SCR_CH3_UNUSED
185+ ch4_unused genpll_scr 5 BCM_NS2_GENPLL_SCR_CH4_UNUSED
186+ ch5_unused genpll_scr 6 BCM_NS2_GENPLL_SCR_CH5_UNUSED
187+
188+ genpll_sw crystal 0 BCM_NS2_GENPLL_SW
189+ rpe genpll_sw 1 BCM_NS2_GENPLL_SW_RPE_CLK
190+ 250 genpll_sw 2 BCM_NS2_GENPLL_SW_250_CLK
191+ nic genpll_sw 3 BCM_NS2_GENPLL_SW_NIC_CLK
192+ chimp genpll_sw 4 BCM_NS2_GENPLL_SW_CHIMP_CLK
193+ port genpll_sw 5 BCM_NS2_GENPLL_SW_PORT_CLK
194+ sdio genpll_sw 6 BCM_NS2_GENPLL_SW_SDIO_CLK
195+
196+ lcpll_ddr crystal 0 BCM_NS2_LCPLL_DDR
197+ pcie_sata_usb lcpll_ddr 1 BCM_NS2_LCPLL_DDR_PCIE_SATA_USB_CLK
198+ ddr lcpll_ddr 2 BCM_NS2_LCPLL_DDR_DDR_CLK
199+ ch2_unused lcpll_ddr 3 BCM_NS2_LCPLL_DDR_CH2_UNUSED
200+ ch3_unused lcpll_ddr 4 BCM_NS2_LCPLL_DDR_CH3_UNUSED
201+ ch4_unused lcpll_ddr 5 BCM_NS2_LCPLL_DDR_CH4_UNUSED
202+ ch5_unused lcpll_ddr 6 BCM_NS2_LCPLL_DDR_CH5_UNUSED
203+
204+ lcpll_ports crystal 0 BCM_NS2_LCPLL_PORTS
205+ wan lcpll_ports 1 BCM_NS2_LCPLL_PORTS_WAN_CLK
206+ rgmii lcpll_ports 2 BCM_NS2_LCPLL_PORTS_RGMII_CLK
207+ ch2_unused lcpll_ports 3 BCM_NS2_LCPLL_PORTS_CH2_UNUSED
208+ ch3_unused lcpll_ports 4 BCM_NS2_LCPLL_PORTS_CH3_UNUSED
209+ ch4_unused lcpll_ports 5 BCM_NS2_LCPLL_PORTS_CH4_UNUSED
210+ ch5_unused lcpll_ports 6 BCM_NS2_LCPLL_PORTS_CH5_UNUSED
Documentation/devicetree/bindings/clock/qcom,gcc.txt+4−0
@@ -18,10 +18,14 @@ Required properties : · 17 unmodified lines
1818 - #clock-cells : shall contain 1
1919 - #reset-cells : shall contain 1
2020
21+Optional properties :
22+- #power-domain-cells : shall contain 1
23+
2124 Example:
2225 clock-controller@900000 {
2326 compatible = "qcom,gcc-msm8960";
2427 reg = <0x900000 0x4000>;
2528 #clock-cells = <1>;
2629 #reset-cells = <1>;
30+ #power-domain-cells = <1>;
2731 };
Documentation/devicetree/bindings/clock/qcom,mmcc.txt+4−0
@@ -14,10 +14,14 @@ Required properties : · 13 unmodified lines
1414 - #clock-cells : shall contain 1
1515 - #reset-cells : shall contain 1
1616
17+Optional properties :
18+- #power-domain-cells : shall contain 1
19+
1720 Example:
1821 clock-controller@4000000 {
1922 compatible = "qcom,mmcc-msm8960";
2023 reg = <0x4000000 0x1000>;
2124 #clock-cells = <1>;
2225 #reset-cells = <1>;
26+ #power-domain-cells = <1>;
2327 };
Documentation/devicetree/bindings/clock/qoriq-clock.txt+50−11
@@ -1,6 +1,6 @@
11 * Clock Block on Freescale QorIQ Platforms
22
3−Freescale qoriq chips take primary clocking input from the external
3+Freescale QorIQ chips take primary clocking input from the external
44 SYSCLK signal. The SYSCLK input (frequency) is multiplied using
55 multiple phase locked loops (PLL) to create a variety of frequencies
66 which can then be passed to a variety of internal logic, including
@@ -13,14 +13,16 @@ which the chip complies. · 6 unmodified lines
1313 Chassis Version Example Chips
1414 --------------- -------------
1515 1.0 p4080, p5020, p5040
16−2.0 t4240, b4860, t1040
16+2.0 t4240, b4860
1717
1818 1. Clock Block Binding
1919
2020 Required properties:
21−- compatible: Should contain a specific clock block compatible string
22− and a single chassis clock compatible string.
23− Clock block strings include, but not limited to, one of the:
21+- compatible: Should contain a chip-specific clock block compatible
22+ string and (if applicable) may contain a chassis-version clock
23+ compatible string.
24+
25+ Chip-specific strings are of the form "fsl,<chip>-clockgen", such as:
2426 * "fsl,p2041-clockgen"
2527 * "fsl,p3041-clockgen"
2628 * "fsl,p4080-clockgen"
@@ -30,15 +32,14 @@ Required properties: · 3 unmodified lines
3032 * "fsl,b4420-clockgen"
3133 * "fsl,b4860-clockgen"
3234 * "fsl,ls1021a-clockgen"
33− Chassis clock strings include:
35+ Chassis-version clock strings include:
3436 * "fsl,qoriq-clockgen-1.0": for chassis 1.0 clocks
3537 * "fsl,qoriq-clockgen-2.0": for chassis 2.0 clocks
3638 - reg: Describes the address of the device's resources within the
3739 address space defined by its parent bus, and resource zero
3840 represents the clock register set
39−- clock-frequency: Input system clock frequency
4041
41−Recommended properties:
42+Optional properties:
4243 - ranges: Allows valid translation between child's address space and
4344 parent's. Must be present if the device has sub-nodes.
4445 - #address-cells: Specifies the number of cells used to represent
@@ -47,8 +48,46 @@ Recommended properties: · 2 unmodified lines
4748 - #size-cells: Specifies the number of cells used to represent
4849 the size of an address. Must be present if the device has
4950 sub-nodes and set to 1 if present
51+- clock-frequency: Input system clock frequency (SYSCLK)
52+- clocks: If clock-frequency is not specified, sysclk may be provided
53+ as an input clock. Either clock-frequency or clocks must be
54+ provided.
55+
56+2. Clock Provider
57+
58+The clockgen node should act as a clock provider, though in older device
59+trees the children of the clockgen node are the clock providers.
60+
61+When the clockgen node is a clock provider, #clock-cells = <2>.
62+The first cell of the clock specifier is the clock type, and the
63+second cell is the clock index for the specified type.
64+
65+ Type# Name Index Cell
66+ 0 sysclk must be 0
67+ 1 cmux index (n in CLKCnCSR)
68+ 2 hwaccel index (n in CLKCGnHWACSR)
69+ 3 fman 0 for fm1, 1 for fm2
70+ 4 platform pll 0=pll, 1=pll/2, 2=pll/3, 3=pll/4
71+
72+3. Example
73+
74+ clockgen: global-utilities@e1000 {
75+ compatible = "fsl,p5020-clockgen", "fsl,qoriq-clockgen-1.0";
76+ clock-frequency = <133333333>;
77+ reg = <0xe1000 0x1000>;
78+ #clock-cells = <2>;
79+ };
80+
81+ fman@400000 {
82+ ...
83+ clocks = <&clockgen 3 0>;
84+ ...
85+ };
86+}
87+4. Legacy Child Nodes
5088
51−2. Clock Provider/Consumer Binding
89+NOTE: These nodes are deprecated. Kernels should continue to support
90+device trees with these nodes, but new device trees should not use them.
5291
5392 Most of the bindings are from the common clock binding[1].
5493 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
@@ -82,7 +121,7 @@ Recommended properties: · 27 unmodified lines
82121 - reg: Should be the offset and length of clock block base address.
83122 The length should be 4.
84123
85−Example for clock block and clock provider:
124+Legacy Example:
86125 / {
87126 clockgen: global-utilities@e1000 {
88127 compatible = "fsl,p5020-clockgen", "fsl,qoriq-clockgen-1.0";
@@ -142,7 +181,7 @@ Example for clock block and clock provider: · 53 unmodified lines
142181 };
143182 };
144183
145−Example for clock consumer:
184+Example for legacy clock consumer:
146185
147186 / {
148187 cpu0: PowerPC,e5500@0 {
Documentation/devicetree/bindings/clock/renesas,cpg-div6-clocks.txt+1−1
@@ -1,7 +1,7 @@
11 * Renesas CPG DIV6 Clock
22
33 The CPG DIV6 clocks are variable factor clocks provided by the Clock Pulse
4−Generator (CPG). They clock input is divided by a configurable factor from 1
4+Generator (CPG). Their clock input is divided by a configurable factor from 1
55 to 64.
66
77 Required Properties:
Documentation/devicetree/bindings/clock/renesas,cpg-mssr.txt+69−0
@@ -0,0 +1,69 @@
1+* Renesas Clock Pulse Generator / Module Standby and Software Reset
2+
3+On Renesas ARM SoCs (SH/R-Mobile, R-Car, RZ), the CPG (Clock Pulse Generator)
4+and MSSR (Module Standby and Software Reset) blocks are intimately connected,
5+and share the same register block.
6+
7+They provide the following functionalities:
8+ - The CPG block generates various core clocks,
9+ - The MSSR block provides two functions:
10+ 1. Module Standby, providing a Clock Domain to control the clock supply
11+ to individual SoC devices,
12+ 2. Reset Control, to perform a software reset of individual SoC devices.
13+
14+Required Properties:
15+ - compatible: Must be one of:
16+ - "renesas,r8a7795-cpg-mssr" for the r8a7795 SoC
17+
18+ - reg: Base address and length of the memory resource used by the CPG/MSSR
19+ block
20+
21+ - clocks: References to external parent clocks, one entry for each entry in
22+ clock-names
23+ - clock-names: List of external parent clock names. Valid names are:
24+ - "extal" (r8a7795)
25+ - "extalr" (r8a7795)
26+
27+ - #clock-cells: Must be 2
28+ - For CPG core clocks, the two clock specifier cells must be "CPG_CORE"
29+ and a core clock reference, as defined in
30+ <dt-bindings/clock/*-cpg-mssr.h>.
31+ - For module clocks, the two clock specifier cells must be "CPG_MOD" and
32+ a module number, as defined in the datasheet.
33+
34+ - #power-domain-cells: Must be 0
35+ - SoC devices that are part of the CPG/MSSR Clock Domain and can be
36+ power-managed through Module Standby should refer to the CPG device
37+ node in their "power-domains" property, as documented by the generic PM
38+ Domain bindings in
39+ Documentation/devicetree/bindings/power/power_domain.txt.
40+
41+
42+Examples
43+--------
44+
45+ - CPG device node:
46+
47+ cpg: clock-controller@e6150000 {
48+ compatible = "renesas,r8a7795-cpg-mssr";
49+ reg = <0 0xe6150000 0 0x1000>;
50+ clocks = <&extal_clk>, <&extalr_clk>;
51+ clock-names = "extal", "extalr";
52+ #clock-cells = <2>;
53+ #power-domain-cells = <0>;
54+ };
55+
56+
57+ - CPG/MSSR Clock Domain member device node:
58+
59+ scif2: serial@e6e88000 {
60+ compatible = "renesas,scif-r8a7795", "renesas,scif";
61+ reg = <0 0xe6e88000 0 64>;
62+ interrupts = <GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>;
63+ clocks = <&cpg CPG_MOD 310>;
64+ clock-names = "sci_ick";
65+ dmas = <&dmac1 0x13>, <&dmac1 0x12>;
66+ dma-names = "tx", "rx";
67+ power-domains = <&cpg>;
68+ status = "disabled";
69+ };
Documentation/devicetree/bindings/clock/silabs,si514.txt+24−0
@@ -0,0 +1,24 @@
1+Binding for Silicon Labs 514 programmable I2C clock generator.
2+
3+Reference
4+This binding uses the common clock binding[1]. Details about the device can be
5+found in the datasheet[2].
6+
7+[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
8+[2] Si514 datasheet
9+ http://www.silabs.com/Support%20Documents/TechnicalDocs/si514.pdf
10+
11+Required properties:
12+ - compatible: Shall be "silabs,si514"
13+ - reg: I2C device address.
14+ - #clock-cells: From common clock bindings: Shall be 0.
15+
16+Optional properties:
17+ - clock-output-names: From common clock bindings. Recommended to be "si514".
18+
19+Example:
20+ si514: clock-generator@55 {
21+ reg = <0x55>;
22+ #clock-cells = <0>;
23+ compatible = "silabs,si514";
24+ };
Documentation/devicetree/bindings/clock/st/st,clkgen-pll.txt+1−0
@@ -23,6 +23,7 @@ Required properties: · 22 unmodified lines
2323 "st,stih407-plls-c32-a9", "st,clkgen-plls-c32"
2424 "sst,plls-c32-cx_0", "st,clkgen-plls-c32"
2525 "sst,plls-c32-cx_1", "st,clkgen-plls-c32"
26+ "st,stih418-plls-c28-a9", "st,clkgen-plls-c32"
2627
2728 "st,stih415-gpu-pll-c32", "st,clkgengpu-pll-c32"
2829 "st,stih416-gpu-pll-c32", "st,clkgengpu-pll-c32"
Documentation/devicetree/bindings/crypto/fsl-sec4.txt+2−2
@@ -441,7 +441,7 @@ EXAMPLE: · 440 unmodified lines
441441 regmap = <&snvs>;
442442 interrupts = <0 4 0x4>
443443 linux,keycode = <116>; /* KEY_POWER */
444− wakeup;
444+ wakeup-source;
445445 };
446446
447447 =====================================================================
@@ -530,7 +530,7 @@ FULL EXAMPLE · 82 unmodified lines
530530 regmap = <&sec_mon>;
531531 interrupts = <0 4 0x4>;
532532 linux,keycode = <116>; /* KEY_POWER */
533− wakeup;
533+ wakeup-source;
534534 };
535535 };
536536
Documentation/devicetree/bindings/display/arm,pl11x.txtrenamed from Documentation/devicetree/bindings/video/arm,pl11x.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/armada/marvell,dove-lcd.txtrenamed from Documentation/devicetree/bindings/drm/armada/marvell,dove-lcd.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/atmel,lcdc.txtrenamed from Documentation/devicetree/bindings/video/atmel,lcdc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txtrenamed from Documentation/devicetree/bindings/drm/atmel/hlcdc-dc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt+65−0
@@ -0,0 +1,65 @@
1+Broadcom VC4 (VideoCore4) GPU
2+
3+The VC4 device present on the Raspberry Pi includes a display system
4+with HDMI output and the HVS (Hardware Video Scaler) for compositing
5+display planes.
6+
7+Required properties for VC4:
8+- compatible: Should be "brcm,bcm2835-vc4"
9+
10+Required properties for Pixel Valve:
11+- compatible: Should be one of "brcm,bcm2835-pixelvalve0",
12+ "brcm,bcm2835-pixelvalve1", or "brcm,bcm2835-pixelvalve2"
13+- reg: Physical base address and length of the PV's registers
14+- interrupts: The interrupt number
15+ See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
16+
17+Required properties for HVS:
18+- compatible: Should be "brcm,bcm2835-hvs"
19+- reg: Physical base address and length of the HVS's registers
20+- interrupts: The interrupt number
21+ See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
22+
23+Required properties for HDMI
24+- compatible: Should be "brcm,bcm2835-hdmi"
25+- reg: Physical base address and length of the two register ranges
26+ ("HDMI" and "HD", in that order)
27+- interrupts: The interrupt numbers
28+ See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
29+- ddc: phandle of the I2C controller used for DDC EDID probing
30+- clocks: a) hdmi: The HDMI state machine clock
31+ b) pixel: The pixel clock.
32+
33+Optional properties for HDMI:
34+- hpd-gpios: The GPIO pin for HDMI hotplug detect (if it doesn't appear
35+ as an interrupt/status bit in the HDMI controller
36+ itself). See bindings/pinctrl/brcm,bcm2835-gpio.txt
37+
38+Example:
39+pixelvalve@7e807000 {
40+ compatible = "brcm,bcm2835-pixelvalve2";
41+ reg = <0x7e807000 0x100>;
42+ interrupts = <2 10>; /* pixelvalve */
43+};
44+
45+hvs@7e400000 {
46+ compatible = "brcm,bcm2835-hvs";
47+ reg = <0x7e400000 0x6000>;
48+ interrupts = <2 1>;
49+};
50+
51+hdmi: hdmi@7e902000 {
52+ compatible = "brcm,bcm2835-hdmi";
53+ reg = <0x7e902000 0x600>,
54+ <0x7e808000 0x100>;
55+ interrupts = <2 8>, <2 9>;
56+ ddc = <&i2c2>;
57+ hpd-gpios = <&gpio 46 GPIO_ACTIVE_HIGH>;
58+ clocks = <&clocks BCM2835_PLLH_PIX>,
59+ <&clocks BCM2835_CLOCK_HSM>;
60+ clock-names = "pixel", "hdmi";
61+};
62+
63+vc4: gpu {
64+ compatible = "brcm,bcm2835-vc4";
65+};
Documentation/devicetree/bindings/display/bridge/adi,adv7123.txtrenamed from Documentation/devicetree/bindings/video/adi,adv7123.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/bridge/adi,adv7511.txtrenamed from Documentation/devicetree/bindings/video/adi,adv7511.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/bridge/dw_hdmi.txtrenamed from Documentation/devicetree/bindings/drm/bridge/dw_hdmi.txt+2−2
@@ -14,8 +14,8 @@ Required properties: · 13 unmodified lines
1414 -port@[X]: SoC specific port nodes with endpoint definitions as defined
1515 in Documentation/devicetree/bindings/media/video-interfaces.txt,
1616 please refer to the SoC specific binding document:
17− * Documentation/devicetree/bindings/drm/imx/hdmi.txt
18− * Documentation/devicetree/bindings/video/dw_hdmi-rockchip.txt
17+ * Documentation/devicetree/bindings/display/imx/hdmi.txt
18+ * Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt
1919
2020 Optional properties
2121 - reg-io-width: the width of the reg:1,4, default set to 1 if not present
Documentation/devicetree/bindings/display/bridge/ps8622.txtrenamed from Documentation/devicetree/bindings/video/bridge/ps8622.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/bridge/ptn3460.txtrenamed from Documentation/devicetree/bindings/video/bridge/ptn3460.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/bridge/tda998x.txtrenamed from Documentation/devicetree/bindings/drm/i2c/tda998x.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/bridge/thine,thc63lvdm83d.txtrenamed from Documentation/devicetree/bindings/video/thine,thc63lvdm83d+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/cirrus,clps711x-fb.txtrenamed from Documentation/devicetree/bindings/video/cirrus,clps711x-fb.txt+1−1
@@ -6,7 +6,7 @@ Required properties: · 5 unmodified lines
66 location and size of the framebuffer memory.
77 - clocks : phandle + clock specifier pair of the FB reference clock.
88 - display : phandle to a display node as described in
9− Documentation/devicetree/bindings/video/display-timing.txt.
9+ Documentation/devicetree/bindings/display/display-timing.txt.
1010 Additionally, the display node has to define properties:
1111 - bits-per-pixel: Bits per pixel.
1212 - ac-prescale : LCD AC bias frequency. This frequency is the required
Documentation/devicetree/bindings/display/connector/analog-tv-connector.txtrenamed from Documentation/devicetree/bindings/video/analog-tv-connector.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/connector/dvi-connector.txtrenamed from Documentation/devicetree/bindings/video/dvi-connector.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/connector/hdmi-connector.txtrenamed from Documentation/devicetree/bindings/video/hdmi-connector.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/connector/vga-connector.txtrenamed from Documentation/devicetree/bindings/video/vga-connector.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos-mic.txtrenamed from Documentation/devicetree/bindings/video/exynos-mic.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos5433-decon.txtrenamed from Documentation/devicetree/bindings/video/exynos5433-decon.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos7-decon.txtrenamed from Documentation/devicetree/bindings/video/exynos7-decon.txt+1−1
@@ -38,7 +38,7 @@ Optional Properties: · 37 unmodified lines
3838 Can be used in case timings cannot be provided otherwise
3939 or to override timings provided by the panel.
4040
41−[1]: Documentation/devicetree/bindings/video/display-timing.txt
41+[1]: Documentation/devicetree/bindings/display/display-timing.txt
4242
4343 Example:
4444
Documentation/devicetree/bindings/display/exynos/exynos_dp.txtrenamed from Documentation/devicetree/bindings/video/exynos_dp.txt+1−1
@@ -50,7 +50,7 @@ Required properties for dp-controller: · 49 unmodified lines
5050 number of lanes supported by the panel.
5151 LANE_COUNT1 = 1, LANE_COUNT2 = 2, LANE_COUNT4 = 4
5252 - display-timings: timings for the connected panel as described by
53− Documentation/devicetree/bindings/video/display-timing.txt
53+ Documentation/devicetree/bindings/display/display-timing.txt
5454
5555 Optional properties for dp-controller:
5656 -interlaced:
Documentation/devicetree/bindings/display/exynos/exynos_dsim.txtrenamed from Documentation/devicetree/bindings/video/exynos_dsim.txt+1−1
@@ -49,7 +49,7 @@ Video interfaces: · 48 unmodified lines
4949 mode
5050 - samsung,esc-clock-frequency: specifies DSI frequency in escape mode
5151
52−[1]: Documentation/devicetree/bindings/mipi/dsi/mipi-dsi-bus.txt
52+[1]: Documentation/devicetree/bindings/display/mipi-dsi-bus.txt
5353 [2]: Documentation/devicetree/bindings/media/video-interfaces.txt
5454
5555 Example:
Documentation/devicetree/bindings/display/exynos/exynos_hdmi.txtrenamed from Documentation/devicetree/bindings/video/exynos_hdmi.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos_hdmiddc.txtrenamed from Documentation/devicetree/bindings/video/exynos_hdmiddc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos_hdmiphy.txtrenamed from Documentation/devicetree/bindings/video/exynos_hdmiphy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/exynos_mixer.txtrenamed from Documentation/devicetree/bindings/video/exynos_mixer.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/exynos/samsung-fimd.txtrenamed from Documentation/devicetree/bindings/video/samsung-fimd.txt+1−1
@@ -82,7 +82,7 @@ in [2]. The following are properties specific to those nodes: · 81 unmodified lines
8282 3 - for parallel output,
8383 4 - for write-back interface
8484
85−[1]: Documentation/devicetree/bindings/video/display-timing.txt
85+[1]: Documentation/devicetree/bindings/display/display-timing.txt
8686 [2]: Documentation/devicetree/bindings/media/video-interfaces.txt
8787
8888 Example:
Documentation/devicetree/bindings/display/fsl,dcu.txtrenamed from Documentation/devicetree/bindings/video/fsl,dcu.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txtrenamed from Documentation/devicetree/bindings/video/fsl,imx-fb.txt+1−1
@@ -9,7 +9,7 @@ Required properties: · 8 unmodified lines
99
1010 Required nodes:
1111 - display: Phandle to a display node as described in
12− Documentation/devicetree/bindings/video/display-timing.txt
12+ Documentation/devicetree/bindings/display/display-timing.txt
1313 Additional, the display node has to define properties:
1414 - bits-per-pixel: Bits per pixel
1515 - fsl,pcr: LCDC PCR value
Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txtrenamed from Documentation/devicetree/bindings/drm/imx/fsl-imx-drm.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/imx/hdmi.txtrenamed from Documentation/devicetree/bindings/drm/imx/hdmi.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/imx/ldb.txtrenamed from Documentation/devicetree/bindings/drm/imx/ldb.txt+1−1
@@ -63,7 +63,7 @@ Required properties: · 62 unmodified lines
6363
6464 Optional properties (required if display-timings are used):
6565 - display-timings : A node that describes the display timings as defined in
66− Documentation/devicetree/bindings/video/display-timing.txt.
66+ Documentation/devicetree/bindings/display/display-timing.txt.
6767 - fsl,data-mapping : should be "spwg" or "jeida"
6868 This describes how the color bits are laid out in the
6969 serialized LVDS signal.
Documentation/devicetree/bindings/display/marvell,pxa2xx-lcdc.txt+34−0
@@ -0,0 +1,34 @@
1+PXA LCD Controller
2+------------------
3+
4+Required properties:
5+ - compatible : one of these
6+ "marvell,pxa2xx-lcdc",
7+ "marvell,pxa270-lcdc",
8+ "marvell,pxa300-lcdc"
9+ - reg : should contain 1 register range (address and length).
10+ - interrupts : framebuffer controller interrupt.
11+ - clocks: phandle to input clocks
12+
13+Required nodes:
14+ - port: connection to the LCD panel (see video-interfaces.txt)
15+ This node must have its properties bus-width and remote-endpoint set.
16+ If the panel is not a TFT color panel, then a "lcd-type" property in
17+ the panel should specify the panel type.
18+ This panel node should be in the board dts.
19+
20+Example:
21+ lcd-controller@40500000 {
22+ compatible = "marvell,pxa2xx-lcdc";
23+ reg = <0x44000000 0x10000>;
24+ interrupts = <17>;
25+ clocks = <&clks CLK_LCD>;
26+ status = "okay";
27+
28+ port {
29+ lcdc_out: endpoint {
30+ remote-endpoint = <&panel_in>;
31+ bus-width = <16>;
32+ };
33+ };
34+ };
Documentation/devicetree/bindings/display/mipi-dsi-bus.txtrenamed from Documentation/devicetree/bindings/mipi/dsi/mipi-dsi-bus.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/msm/dsi.txtrenamed from Documentation/devicetree/bindings/drm/msm/dsi.txt+1−1
@@ -28,7 +28,7 @@ Required properties: · 27 unmodified lines
2828
2929 Optional properties:
3030 - panel@0: Node of panel connected to this DSI controller.
31− See files in Documentation/devicetree/bindings/panel/ for each supported
31+ See files in Documentation/devicetree/bindings/display/panel/ for each supported
3232 panel.
3333 - qcom,dual-dsi-mode: Boolean value indicating if the DSI controller is
3434 driving a panel which needs 2 DSI links.
Documentation/devicetree/bindings/display/msm/edp.txtrenamed from Documentation/devicetree/bindings/drm/msm/edp.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/msm/gpu.txtrenamed from Documentation/devicetree/bindings/drm/msm/gpu.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/msm/hdmi.txtrenamed from Documentation/devicetree/bindings/drm/msm/hdmi.txt+3−0
@@ -2,6 +2,7 @@ Qualcomm adreno/snapdragon hdmi output · 1 unmodified line
22
33 Required properties:
44 - compatible: one of the following
5+ * "qcom,hdmi-tx-8996"
56 * "qcom,hdmi-tx-8994"
67 * "qcom,hdmi-tx-8084"
78 * "qcom,hdmi-tx-8974"
@@ -21,6 +22,7 @@ Required properties: · 13 unmodified lines
2122 Optional properties:
2223 - qcom,hdmi-tx-mux-en-gpio: hdmi mux enable pin
2324 - qcom,hdmi-tx-mux-sel-gpio: hdmi mux select pin
25+- power-domains: reference to the power domain(s), if available.
2426 - pinctrl-names: the pin control state names; should contain "default"
2527 - pinctrl-0: the default pinctrl state (active)
2628 - pinctrl-1: the "sleep" pinctrl state
@@ -35,6 +37,7 @@ Example: · 8 unmodified lines
3537 reg-names = "core_physical";
3638 reg = <0x04a00000 0x1000>;
3739 interrupts = <GIC_SPI 79 0>;
40+ power-domains = <&mmcc MDSS_GDSC>;
3841 clock-names =
3942 "core_clk",
4043 "master_iface_clk",
Documentation/devicetree/bindings/display/msm/mdp.txtrenamed from Documentation/devicetree/bindings/drm/msm/mdp.txt+2−1
@@ -11,13 +11,14 @@ Required properties: · 10 unmodified lines
1111 - clock-names: the following clocks are required:
1212 * "core_clk"
1313 * "iface_clk"
14− * "lut_clk"
1514 * "src_clk"
1615 * "hdmi_clk"
1716 * "mpd_clk"
1817
1918 Optional properties:
2019 - gpus: phandle for gpu device
20+- clock-names: the following clocks are optional:
21+ * "lut_clk"
2122
2223 Example:
2324
Documentation/devicetree/bindings/display/mxsfb.txtrenamed from Documentation/devicetree/bindings/fb/mxsfb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/ampire,am800480r3tmqwa1h.txtrenamed from Documentation/devicetree/bindings/panel/ampire,am800480r3tmqwa1h.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b080uan01.txtrenamed from Documentation/devicetree/bindings/panel/auo,b080uan01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b101aw03.txtrenamed from Documentation/devicetree/bindings/panel/auo,b101aw03.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b101ean01.txtrenamed from Documentation/devicetree/bindings/panel/auo,b101ean01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b101xtn01.txtrenamed from Documentation/devicetree/bindings/panel/auo,b101xtn01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b116xw03.txtrenamed from Documentation/devicetree/bindings/panel/auo,b116xw03.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b133htn01.txtrenamed from Documentation/devicetree/bindings/panel/auo,b133htn01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/auo,b133xtn01.txtrenamed from Documentation/devicetree/bindings/panel/auo,b133xtn01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/avic,tm070ddh03.txtrenamed from Documentation/devicetree/bindings/panel/avic,tm070ddh03.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/chunghwa,claa101wa01a.txtrenamed from Documentation/devicetree/bindings/panel/chunghwa,claa101wa01a.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/chunghwa,claa101wb03.txtrenamed from Documentation/devicetree/bindings/panel/chunghwa,claa101wb03.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/display-timing.txtrenamed from Documentation/devicetree/bindings/video/display-timing.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/edt,et057090dhu.txtrenamed from Documentation/devicetree/bindings/panel/edt,et057090dhu.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/edt,et070080dh6.txtrenamed from Documentation/devicetree/bindings/panel/edt,et070080dh6.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/edt,etm0700g0dh6.txtrenamed from Documentation/devicetree/bindings/panel/edt,etm0700g0dh6.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/foxlink,fl500wvr00-a0t.txtrenamed from Documentation/devicetree/bindings/panel/foxlink,fl500wvr00-a0t.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/giantplus,gpg482739qs5.txtrenamed from Documentation/devicetree/bindings/panel/giantplus,gpg482739qs5.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/hannstar,hsd070pww1.txtrenamed from Documentation/devicetree/bindings/panel/hannstar,hsd070pww1.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/hannstar,hsd100pxn1.txtrenamed from Documentation/devicetree/bindings/panel/hannstar,hsd100pxn1.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/hit,tx23d38vm0caa.txtrenamed from Documentation/devicetree/bindings/panel/hit,tx23d38vm0caa.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/innolux,at043tn24.txtrenamed from Documentation/devicetree/bindings/panel/innolux,at043tn24.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/innolux,g121i1-l01.txtrenamed from Documentation/devicetree/bindings/panel/innolux,g121i1-l01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/innolux,n116bge.txtrenamed from Documentation/devicetree/bindings/panel/innolux,n116bge.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/innolux,n156bge-l21.txtrenamed from Documentation/devicetree/bindings/panel/innolux,n156bge-l21.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/innolux,zj070na-01p.txtrenamed from Documentation/devicetree/bindings/panel/innolux,zj070na-01p.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lg,lb070wv8.txtrenamed from Documentation/devicetree/bindings/panel/lg,lb070wv8.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lg,ld070wx3-sl01.txtrenamed from Documentation/devicetree/bindings/panel/lg,ld070wx3-sl01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lg,lg4573.txtrenamed from Documentation/devicetree/bindings/panel/lg,lg4573.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lg,lh500wx1-sd03.txtrenamed from Documentation/devicetree/bindings/panel/lg,lh500wx1-sd03.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lg,lp129qe.txtrenamed from Documentation/devicetree/bindings/panel/lg,lp129qe.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/lgphilips,lb035q02.txtrenamed from Documentation/devicetree/bindings/video/lgphilips,lb035q02.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/nec,nl4827hc19-05b.txtrenamed from Documentation/devicetree/bindings/panel/nec,nl4827hc19-05b.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/okaya,rs800480t-7x0gp.txtrenamed from Documentation/devicetree/bindings/panel/okaya,rs800480t-7x0gp.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/ortustech,com43h4m85ulc.txtrenamed from Documentation/devicetree/bindings/panel/ortustech,com43h4m85ulc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/panasonic,vvx10f004b00.txtrenamed from Documentation/devicetree/bindings/panel/panasonic,vvx10f004b00.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/panel-dpi.txtrenamed from Documentation/devicetree/bindings/video/panel-dpi.txt+1−1
@@ -10,7 +10,7 @@ Optional properties: · 9 unmodified lines
1010
1111 Required nodes:
1212 - "panel-timing" containing video timings
13− (Documentation/devicetree/bindings/video/display-timing.txt)
13+ (Documentation/devicetree/bindings/display/display-timing.txt)
1414 - Video port for DPI input
1515
1616 Example
Documentation/devicetree/bindings/display/panel/panel-dsi-cm.txtrenamed from Documentation/devicetree/bindings/video/panel-dsi-cm.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/samsung,ld9040.txtrenamed from Documentation/devicetree/bindings/panel/samsung,ld9040.txt+1−1
@@ -20,7 +20,7 @@ The device node can contain one 'port' child node with one child · 19 unmodified lines
2020 'endpoint' node, according to the bindings defined in [3]. This
2121 node should describe panel's video bus.
2222
23−[1]: Documentation/devicetree/bindings/video/display-timing.txt
23+[1]: Documentation/devicetree/bindings/display/display-timing.txt
2424 [2]: Documentation/devicetree/bindings/spi/spi-bus.txt
2525 [3]: Documentation/devicetree/bindings/media/video-interfaces.txt
2626
Documentation/devicetree/bindings/display/panel/samsung,ltn101nt05.txtrenamed from Documentation/devicetree/bindings/panel/samsung,ltn101nt05.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/samsung,ltn140at29-301.txtrenamed from Documentation/devicetree/bindings/panel/samsung,ltn140at29-301.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/samsung,s6e8aa0.txtrenamed from Documentation/devicetree/bindings/panel/samsung,s6e8aa0.txt+1−1
@@ -21,7 +21,7 @@ The device node can contain one 'port' child node with one child · 20 unmodified lines
2121 'endpoint' node, according to the bindings defined in [2]. This
2222 node should describe panel's video bus.
2323
24−[1]: Documentation/devicetree/bindings/video/display-timing.txt
24+[1]: Documentation/devicetree/bindings/display/display-timing.txt
2525 [2]: Documentation/devicetree/bindings/media/video-interfaces.txt
2626
2727 Example:
Documentation/devicetree/bindings/display/panel/sharp,lq101r1sx01.txtrenamed from Documentation/devicetree/bindings/panel/sharp,lq101r1sx01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/sharp,ls037v7dw01.txtrenamed from Documentation/devicetree/bindings/video/sharp,ls037v7dw01.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/shelly,sca07010-bfn-lnn.txtrenamed from Documentation/devicetree/bindings/panel/shelly,sca07010-bfn-lnn.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/simple-panel.txtrenamed from Documentation/devicetree/bindings/panel/simple-panel.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/sony,acx565akm.txtrenamed from Documentation/devicetree/bindings/video/sony,acx565akm.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/toppoly,td028ttec1.txtrenamed from Documentation/devicetree/bindings/video/toppoly,td028ttec1.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/panel/tpo,td043mtea1.txtrenamed from Documentation/devicetree/bindings/video/tpo,td043mtea1.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/renesas,du.txtrenamed from Documentation/devicetree/bindings/video/renesas,du.txt+9−5
@@ -5,7 +5,9 @@ Required Properties: · 4 unmodified lines
55 - compatible: must be one of the following.
66 - "renesas,du-r8a7779" for R8A7779 (R-Car H1) compatible DU
77 - "renesas,du-r8a7790" for R8A7790 (R-Car H2) compatible DU
8− - "renesas,du-r8a7791" for R8A7791 (R-Car M2) compatible DU
8+ - "renesas,du-r8a7791" for R8A7791 (R-Car M2-W) compatible DU
9+ - "renesas,du-r8a7793" for R8A7793 (R-Car M2-N) compatible DU
10+ - "renesas,du-r8a7794" for R8A7794 (R-Car E2) compatible DU
911
1012 - reg: A list of base address and length of each memory resource, one for
1113 each entry in the reg-names property.
@@ -22,9 +24,9 @@ Required Properties: · 10 unmodified lines
2224 - clock-names: Name of the clocks. This property is model-dependent.
2325 - R8A7779 uses a single functional clock. The clock doesn't need to be
2426 named.
25− - R8A7790 and R8A7791 use one functional clock per channel and one clock
26− per LVDS encoder. The functional clocks must be named "du.x" with "x"
27− being the channel numerical index. The LVDS clocks must be named
27+ - R8A779[0134] use one functional clock per channel and one clock per LVDS
28+ encoder (if available). The functional clocks must be named "du.x" with
29+ "x" being the channel numerical index. The LVDS clocks must be named
2830 "lvds.x" with "x" being the LVDS encoder numerical index.
2931 - In addition to the functional and encoder clocks, all DU versions also
3032 support externally supplied pixel clocks. Those clocks are optional.
@@ -43,7 +45,9 @@ corresponding to each DU output. · 12 unmodified lines
4345 -----------------------------------------------------------------------------
4446 R8A7779 (H1) DPAD 0 DPAD 1 -
4547 R8A7790 (H2) DPAD LVDS 0 LVDS 1
46− R8A7791 (M2) DPAD LVDS 0 -
48+ R8A7791 (M2-W) DPAD LVDS 0 -
49+ R8A7793 (M2-N) DPAD LVDS 0 -
50+ R8A7794 (E2) DPAD 0 DPAD 1 -
4751
4852
4953 Example: R8A7790 (R-Car H2) DU
Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txtrenamed from Documentation/devicetree/bindings/video/dw_hdmi-rockchip.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/rockchip/rockchip-drm.txtrenamed from Documentation/devicetree/bindings/video/rockchip-drm.txt+1−1
@@ -9,7 +9,7 @@ Required properties: · 8 unmodified lines
99 - compatible: Should be "rockchip,display-subsystem"
1010 - ports: Should contain a list of phandles pointing to display interface port
1111 of vop devices. vop definitions as defined in
12− Documentation/devicetree/bindings/video/rockchip-vop.txt
12+ Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt
1313
1414 example:
1515
Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txtrenamed from Documentation/devicetree/bindings/video/rockchip-vop.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/simple-framebuffer-sunxi.txtrenamed from Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/simple-framebuffer.txtrenamed from Documentation/devicetree/bindings/video/simple-framebuffer.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/sm501fb.txtrenamed from Documentation/devicetree/bindings/fb/sm501fb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/ssd1289fb.txtrenamed from Documentation/devicetree/bindings/video/ssd1289fb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/ssd1307fb.txtrenamed from Documentation/devicetree/bindings/video/ssd1307fb.txt+2−1
@@ -2,7 +2,8 @@ · 1 unmodified line
22
33 Required properties:
44 - compatible: Should be "solomon,<chip>fb-<bus>". The only supported bus for
5− now is i2c, and the supported chips are ssd1305, ssd1306 and ssd1307.
5+ now is i2c, and the supported chips are ssd1305, ssd1306, ssd1307 and
6+ ssd1309.
67 - reg: Should contain address of the controller on the I2C bus. Most likely
78 0x3c or 0x3d
89 - pwm: Should contain the pwm to use according to the OF device tree PWM
Documentation/devicetree/bindings/display/st,stih4xx.txtrenamed from Documentation/devicetree/bindings/gpu/st,stih4xx.txt+2−2
@@ -61,7 +61,7 @@ STMicroelectronics stih4xx platforms · 60 unmodified lines
6161 - reg-names: names of the mapped memory regions listed in regs property in
6262 the same order.
6363 - interrupts : HDMI interrupt number to the CPU.
64− - interrupt-names: name of the interrupts listed in interrupts property in
64+ - interrupt-names: names of the interrupts listed in interrupts property in
6565 the same order
6666 - clocks: from common clock binding: handle hardware IP needed clocks, the
6767 number of clocks may depend of the SoC type.
@@ -95,7 +95,7 @@ sti-dvo: · 27 unmodified lines
9595 - clock-names: names of the clocks listed in clocks property in the same
9696 order.
9797 - pinctrl-0: pin control handle
98− - pinctrl-name: names of the pin control to use
98+ - pinctrl-names: names of the pin control states to use
9999 - sti,panel: phandle of the panel connected to the DVO output
100100
101101 sti-hqvdp:
Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.txtrenamed from Documentation/devicetree/bindings/mipi/nvidia,tegra114-mipi.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txtrenamed from Documentation/devicetree/bindings/gpu/nvidia,tegra20-host1x.txt+1−1
@@ -184,7 +184,7 @@ of the following host1x client modules: · 183 unmodified lines
184184 - avdd-dsi-supply: phandle of a supply that powers the DSI controller
185185 - nvidia,mipi-calibrate: Should contain a phandle and a specifier specifying
186186 which pads are used by this DSI output and need to be calibrated. See also
187− ../mipi/nvidia,tegra114-mipi.txt.
187+ ../display/tegra/nvidia,tegra114-mipi.txt.
188188
189189 Optional properties:
190190 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,dra7-dss.txt+1−1
@@ -1,7 +1,7 @@
11 Texas Instruments DRA7x Display Subsystem
22 =========================================
33
4−See Documentation/devicetree/bindings/video/ti,omap-dss.txt for generic
4+See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic
55 description about OMAP Display Subsystem bindings.
66
77 DSS Core
Documentation/devicetree/bindings/display/ti/ti,omap-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,omap-dss.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,omap2-dss.txt+1−1
@@ -1,7 +1,7 @@
11 Texas Instruments OMAP2 Display Subsystem
22 =========================================
33
4−See Documentation/devicetree/bindings/video/ti,omap-dss.txt for generic
4+See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic
55 description about OMAP Display Subsystem bindings.
66
77 DSS Core
Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,omap3-dss.txt+1−1
@@ -1,7 +1,7 @@
11 Texas Instruments OMAP3 Display Subsystem
22 =========================================
33
4−See Documentation/devicetree/bindings/video/ti,omap-dss.txt for generic
4+See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic
55 description about OMAP Display Subsystem bindings.
66
77 DSS Core
Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,omap4-dss.txt+1−1
@@ -1,7 +1,7 @@
11 Texas Instruments OMAP4 Display Subsystem
22 =========================================
33
4−See Documentation/devicetree/bindings/video/ti,omap-dss.txt for generic
4+See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic
55 description about OMAP Display Subsystem bindings.
66
77 DSS Core
Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txtrenamed from Documentation/devicetree/bindings/video/ti,omap5-dss.txt+1−1
@@ -1,7 +1,7 @@
11 Texas Instruments OMAP5 Display Subsystem
22 =========================================
33
4−See Documentation/devicetree/bindings/video/ti,omap-dss.txt for generic
4+See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic
55 description about OMAP Display Subsystem bindings.
66
77 DSS Core
Documentation/devicetree/bindings/display/ti/ti,opa362.txtrenamed from Documentation/devicetree/bindings/video/ti,opa362.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/ti/ti,tfp410.txtrenamed from Documentation/devicetree/bindings/video/ti,tfp410.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/ti/ti,tpd12s015.txtrenamed from Documentation/devicetree/bindings/video/ti,tpd12s015.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/tilcdc/panel.txtrenamed from Documentation/devicetree/bindings/drm/tilcdc/panel.txt+1−1
@@ -15,7 +15,7 @@ Required properties: · 14 unmodified lines
1515 - display-timings: typical videomode of lcd panel. Multiple video modes
1616 can be listed if the panel supports multiple timings, but the 'native-mode'
1717 should be the preferred/default resolution. Refer to
18− Documentation/devicetree/bindings/video/display-timing.txt for display
18+ Documentation/devicetree/bindings/display/display-timing.txt for display
1919 timing binding details.
2020
2121 Optional properties:
Documentation/devicetree/bindings/display/tilcdc/tfp410.txtrenamed from Documentation/devicetree/bindings/drm/tilcdc/tfp410.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/tilcdc/tilcdc.txtrenamed from Documentation/devicetree/bindings/drm/tilcdc/tilcdc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/via,vt8500-fb.txtrenamed from Documentation/devicetree/bindings/video/via,vt8500-fb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/wm,prizm-ge-rops.txtrenamed from Documentation/devicetree/bindings/video/wm,prizm-ge-rops.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/display/wm,wm8505-fb.txtrenamed from Documentation/devicetree/bindings/video/wm,wm8505-fb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt+13−2
@@ -2,9 +2,10 @@ Texas Instruments DMA Crossbar (DMA request router) · 1 unmodified line
22
33 Required properties:
44 - compatible: "ti,dra7-dma-crossbar" for DRA7xx DMA crossbar
5+ "ti,am335x-edma-crossbar" for AM335x and AM437x
56 - reg: Memory map for accessing module
6−- #dma-cells: Should be set to <1>.
7− Clients should use the crossbar request number (input)
7+- #dma-cells: Should be set to to match with the DMA controller's dma-cells
8+ for ti,dra7-dma-crossbar and <3> for ti,am335x-edma-crossbar.
89 - dma-requests: Number of DMA requests the crossbar can receive
910 - dma-masters: phandle pointing to the DMA controller
1011
@@ -14,6 +15,15 @@ The DMA controller node need to have the following poroperties: · 3 unmodified lines
1415 Optional properties:
1516 - ti,dma-safe-map: Safe routing value for unused request lines
1617
18+Notes:
19+When requesting channel via ti,dra7-dma-crossbar, the DMA clinet must request
20+the DMA event number as crossbar ID (input to the DMA crossbar).
21+
22+For ti,am335x-edma-crossbar: the meaning of parameters of dmas for clients:
23+dmas = <&edma_xbar 12 0 1>; where <12> is the DMA request number, <0> is the TC
24+the event should be assigned and <1> is the mux selection for in the crossbar.
25+When mux 0 is used the DMA channel can be requested directly from edma node.
26+
1727 Example:
1828
1929 /* DMA controller */
@@ -47,6 +57,7 @@ uart1: serial@4806a000 { · 27 unmodified lines
4757 ti,hwmods = "uart1";
4858 clock-frequency = <48000000>;
4959 status = "disabled";
60+ /* Requesting crossbar input 49 and 50 */
5061 dmas = <&sdma_xbar 49>, <&sdma_xbar 50>;
5162 dma-names = "tx", "rx";
5263 };
Documentation/devicetree/bindings/dma/ti-edma.txt+116−1
@@ -1,4 +1,119 @@
1−TI EDMA
1+Texas Instruments eDMA
2+
3+The eDMA3 consists of two components: Channel controller (CC) and Transfer
4+Controller(s) (TC). The CC is the main entry for DMA users since it is
5+responsible for the DMA channel handling, while the TCs are responsible to
6+execute the actual DMA tansfer.
7+
8+------------------------------------------------------------------------------
9+eDMA3 Channel Controller
10+
11+Required properties:
12+- compatible: "ti,edma3-tpcc" for the channel controller(s)
13+- #dma-cells: Should be set to <2>. The first number is the DMA request
14+ number and the second is the TC the channel is serviced on.
15+- reg: Memory map of eDMA CC
16+- reg-names: "edma3_cc"
17+- interrupts: Interrupt lines for CCINT, MPERR and CCERRINT.
18+- interrupt-names: "edma3_ccint", "emda3_mperr" and "edma3_ccerrint"
19+- ti,tptcs: List of TPTCs associated with the eDMA in the following form:
20+ <&tptc_phandle TC_priority_number>. The highest priority is 0.
21+
22+Optional properties:
23+- ti,hwmods: Name of the hwmods associated to the eDMA CC
24+- ti,edma-memcpy-channels: List of channels allocated to be used for memcpy, iow
25+ these channels will be SW triggered channels. The list must
26+ contain 16 bits numbers, see example.
27+- ti,edma-reserved-slot-ranges: PaRAM slot ranges which should not be used by
28+ the driver, they are allocated to be used by for example the
29+ DSP. See example.
30+
31+------------------------------------------------------------------------------
32+eDMA3 Transfer Controller
33+
34+Required properties:
35+- compatible: "ti,edma3-tptc" for the transfer controller(s)
36+- reg: Memory map of eDMA TC
37+- interrupts: Interrupt number for TCerrint.
38+
39+Optional properties:
40+- ti,hwmods: Name of the hwmods associated to the given eDMA TC
41+- interrupt-names: "edma3_tcerrint"
42+
43+------------------------------------------------------------------------------
44+Example:
45+
46+edma: edma@49000000 {
47+ compatible = "ti,edma3-tpcc";
48+ ti,hwmods = "tpcc";
49+ reg = <0x49000000 0x10000>;
50+ reg-names = "edma3_cc";
51+ interrupts = <12 13 14>;
52+ interrupt-names = "edma3_ccint", "emda3_mperr", "edma3_ccerrint";
53+ dma-requests = <64>;
54+ #dma-cells = <2>;
55+
56+ ti,tptcs = <&edma_tptc0 7>, <&edma_tptc1 7>, <&edma_tptc2 0>;
57+
58+ /* Channel 20 and 21 is allocated for memcpy */
59+ ti,edma-memcpy-channels = /bits/ 16 <20 21>;
60+ /* The following PaRAM slots are reserved: 35-45 and 100-110 */
61+ ti,edma-reserved-slot-ranges = /bits/ 16 <35 10>,
62+ /bits/ 16 <100 10>;
63+};
64+
65+edma_tptc0: tptc@49800000 {
66+ compatible = "ti,edma3-tptc";
67+ ti,hwmods = "tptc0";
68+ reg = <0x49800000 0x100000>;
69+ interrupts = <112>;
70+ interrupt-names = "edm3_tcerrint";
71+};
72+
73+edma_tptc1: tptc@49900000 {
74+ compatible = "ti,edma3-tptc";
75+ ti,hwmods = "tptc1";
76+ reg = <0x49900000 0x100000>;
77+ interrupts = <113>;
78+ interrupt-names = "edm3_tcerrint";
79+};
80+
81+edma_tptc2: tptc@49a00000 {
82+ compatible = "ti,edma3-tptc";
83+ ti,hwmods = "tptc2";
84+ reg = <0x49a00000 0x100000>;
85+ interrupts = <114>;
86+ interrupt-names = "edm3_tcerrint";
87+};
88+
89+sham: sham@53100000 {
90+ compatible = "ti,omap4-sham";
91+ ti,hwmods = "sham";
92+ reg = <0x53100000 0x200>;
93+ interrupts = <109>;
94+ /* DMA channel 36 executed on eDMA TC0 - low priority queue */
95+ dmas = <&edma 36 0>;
96+ dma-names = "rx";
97+};
98+
99+mcasp0: mcasp@48038000 {
100+ compatible = "ti,am33xx-mcasp-audio";
101+ ti,hwmods = "mcasp0";
102+ reg = <0x48038000 0x2000>,
103+ <0x46000000 0x400000>;
104+ reg-names = "mpu", "dat";
105+ interrupts = <80>, <81>;
106+ interrupt-names = "tx", "rx";
107+ status = "disabled";
108+ /* DMA channels 8 and 9 executed on eDMA TC2 - high priority queue */
109+ dmas = <&edma 8 2>,
110+ <&edma 9 2>;
111+ dma-names = "tx", "rx";
112+};
113+
114+------------------------------------------------------------------------------
115+DEPRECATED binding, new DTS files must use the ti,edma3-tpcc/ti,edma3-tptc
116+binding.
2117
3118 Required properties:
4119 - compatible : "ti,edma3"
Documentation/devicetree/bindings/edac/apm-xgene-edac.txt+23−0
@@ -5,6 +5,8 @@ The follow error types are supported: · 4 unmodified lines
55
66 memory controller - Memory controller
77 PMD (L1/L2) - Processor module unit (PMD) L1/L2 cache
8+ L3 - L3 cache controller
9+ SoC - SoC IP's such as Ethernet, SATA, and etc
810
911 The following section describes the EDAC DT node binding.
1012
@@ -30,6 +32,17 @@ Required properties for PMD subnode: · 19 unmodified lines
3032 - reg : First resource shall be the PMD resource.
3133 - pmd-controller : Instance number of the PMD controller.
3234
35+Required properties for L3 subnode:
36+- compatible : Shall be "apm,xgene-edac-l3" or
37+ "apm,xgene-edac-l3-v2".
38+- reg : First resource shall be the L3 EDAC resource.
39+
40+Required properties for SoC subnode:
41+- compatible : Shall be "apm,xgene-edac-soc-v1" for revision 1 or
42+ "apm,xgene-edac-l3-soc" for general value reporting
43+ only.
44+- reg : First resource shall be the SoC EDAC resource.
45+
3346 Example:
3447 csw: csw@7e200000 {
3548 compatible = "apm,xgene-csw", "syscon";
@@ -76,4 +89,14 @@ Example: · 40 unmodified lines
7689 reg = <0x0 0x7c000000 0x0 0x200000>;
7790 pmd-controller = <0>;
7891 };
92+
93+ edacl3@7e600000 {
94+ compatible = "apm,xgene-edac-l3";
95+ reg = <0x0 0x7e600000 0x0 0x1000>;
96+ };
97+
98+ edacsoc@7e930000 {
99+ compatible = "apm,xgene-edac-soc-v1";
100+ reg = <0x0 0x7e930000 0x0 0x1000>;
101+ };
79102 };
Documentation/devicetree/bindings/eeprom/at25.txtrenamed from Documentation/devicetree/bindings/misc/at25.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/eeprom/eeprom.txtrenamed from Documentation/devicetree/bindings/eeprom.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/extcon/extcon-arizona.txt+15−0
@@ -0,0 +1,15 @@
1+Cirrus Logic Arizona class audio SoCs
2+
3+These devices are audio SoCs with extensive digital capabilities and a range
4+of analogue I/O.
5+
6+This document lists Extcon specific bindings, see the primary binding document:
7+ ../mfd/arizona.txt
8+
9+Optional properties:
10+
11+ - wlf,hpdet-channel : Headphone detection channel.
12+ ARIZONA_ACCDET_MODE_HPL or 1 - Headphone detect mode is set to HPDETL
13+ ARIZONA_ACCDET_MODE_HPR or 2 - Headphone detect mode is set to HPDETR
14+ If this node is not mentioned or if the value is unknown, then
15+ headphone detection mode is set to HPDETL.
Documentation/devicetree/bindings/fpga/altera-socfpga-fpga-mgr.txt+1−1
@@ -9,7 +9,7 @@ Required properties: · 8 unmodified lines
99
1010 Example:
1111
12− hps_0_fpgamgr: fpgamgr@0xff706000 {
12+ hps_0_fpgamgr: fpgamgr@ff706000 {
1313 compatible = "altr,socfpga-fpga-mgr";
1414 reg = <0xFF706000 0x1000
1515 0xFFB90000 0x1000>;
Documentation/devicetree/bindings/fpga/xilinx-zynq-fpga-mgr.txt+19−0
@@ -0,0 +1,19 @@
1+Xilinx Zynq FPGA Manager
2+
3+Required properties:
4+- compatible: should contain "xlnx,zynq-devcfg-1.0"
5+- reg: base address and size for memory mapped io
6+- interrupts: interrupt for the FPGA manager device
7+- clocks: phandle for clocks required operation
8+- clock-names: name for the clock, should be "ref_clk"
9+- syscon: phandle for access to SLCR registers
10+
11+Example:
12+ devcfg: devcfg@f8007000 {
13+ compatible = "xlnx,zynq-devcfg-1.0";
14+ reg = <0xf8007000 0x100>;
15+ interrupts = <0 8 4>;
16+ clocks = <&clkc 12>;
17+ clock-names = "ref_clk";
18+ syscon = <&slcr>;
19+ };
Documentation/devicetree/bindings/gpio/gpio-mpc8xxx.txt+2−2
@@ -1,9 +1,9 @@
1−* Freescale MPC512x/MPC8xxx GPIO controller
1+* Freescale MPC512x/MPC8xxx/Layerscape GPIO controller
22
33 Required properties:
44 - compatible : Should be "fsl,<soc>-gpio"
55 The following <soc>s are known to be supported:
6− mpc5121, mpc5125, mpc8349, mpc8572, mpc8610, pq3, qoriq
6+ mpc5121, mpc5125, mpc8349, mpc8572, mpc8610, pq3, qoriq.
77 - reg : Address and length of the register set for the device
88 - interrupts : Should be the port interrupt shared by all 32 pins.
99 - #gpio-cells : Should be two. The first cell is the pin number and
Documentation/devicetree/bindings/gpio/gpio-msm.txt+0−26
@@ -1,26 +0,0 @@
1−MSM GPIO controller bindings
2−
3−Required properties:
4−- compatible:
5− - "qcom,msm-gpio" for MSM controllers
6−- #gpio-cells : Should be two.
7− - first cell is the pin number
8− - second cell is used to specify optional parameters (unused)
9−- gpio-controller : Marks the device node as a GPIO controller.
10−- #interrupt-cells : Should be 2.
11−- interrupt-controller: Mark the device node as an interrupt controller
12−- interrupts : Specify the TLMM summary interrupt number
13−- ngpio : Specify the number of MSM GPIOs
14−
15−Example:
16−
17− msmgpio: gpio@fd510000 {
18− compatible = "qcom,msm-gpio";
19− gpio-controller;
20− #gpio-cells = <2>;
21− interrupt-controller;
22− #interrupt-cells = <2>;
23− reg = <0xfd510000 0x4000>;
24− interrupts = <0 208 0>;
25− ngpio = <150>;
26− };
Documentation/devicetree/bindings/gpio/gpio-pca953x.txt+1−0
@@ -24,6 +24,7 @@ Required properties: · 23 unmodified lines
2424 ti,tca6408
2525 ti,tca6416
2626 ti,tca6424
27+ ti,tca9539
2728 exar,xra1202
2829
2930 Example:
Documentation/devicetree/bindings/gpio/gpio-zynq.txt+9−0
@@ -12,6 +12,13 @@ Required properties: · 11 unmodified lines
1212 - interrupts : Interrupt specifier (see interrupt bindings for
1313 details)
1414 - interrupt-parent : Must be core interrupt controller
15+- interrupt-controller : Marks the device node as an interrupt controller.
16+- #interrupt-cells : Should be 2. The first cell is the GPIO number.
17+ The second cell bits[3:0] is used to specify trigger type and level flags:
18+ 1 = low-to-high edge triggered.
19+ 2 = high-to-low edge triggered.
20+ 4 = active high level-sensitive.
21+ 8 = active low level-sensitive.
1522 - reg : Address and length of the register set for the device
1623
1724 Example:
@@ -22,5 +29,7 @@ Example: · 4 unmodified lines
2229 gpio-controller;
2330 interrupt-parent = <&intc>;
2431 interrupts = <0 20 4>;
32+ interrupt-controller;
33+ #interrupt-cells = <2>;
2534 reg = <0xe000a000 0x1000>;
2635 };
Documentation/devicetree/bindings/gpio/gpio.txt+39−2
@@ -54,9 +54,13 @@ only uses one. · 53 unmodified lines
5454
5555 gpio-specifier may encode: bank, pin position inside the bank,
5656 whether pin is open-drain and whether pin is logically inverted.
57+
5758 Exact meaning of each specifier cell is controller specific, and must
58−be documented in the device tree binding for the device. Use the macros
59−defined in include/dt-bindings/gpio/gpio.h whenever possible:
59+be documented in the device tree binding for the device.
60+
61+Most controllers are however specifying a generic flag bitfield
62+in the last cell, so for these, use the macros defined in
63+include/dt-bindings/gpio/gpio.h whenever possible:
6064
6165 Example of a node using GPIOs:
6266
@@ -67,6 +71,15 @@ Example of a node using GPIOs: · 4 unmodified lines
6771 GPIO_ACTIVE_HIGH is 0, so in this example gpio-specifier is "18 0" and encodes
6872 GPIO pin number, and GPIO flags as accepted by the "qe_pio_e" gpio-controller.
6973
74+Optional standard bitfield specifiers for the last cell:
75+
76+- Bit 0: 0 means active high, 1 means active low
77+- Bit 1: 1 means single-ended wiring, see:
78+ https://en.wikipedia.org/wiki/Single-ended_triode
79+ When used with active-low, this means open drain/collector, see:
80+ https://en.wikipedia.org/wiki/Open_collector
81+ When used with active-high, this means open source/emitter
82+
7083 1.1) GPIO specifier best practices
7184 ----------------------------------
7285
@@ -118,6 +131,30 @@ Every GPIO controller node must contain both an empty "gpio-controller" · 45 unmodified lines
118131 property, and a #gpio-cells integer property, which indicates the number of
119132 cells in a gpio-specifier.
120133
134+Optionally, a GPIO controller may have a "ngpios" property. This property
135+indicates the number of in-use slots of available slots for GPIOs. The
136+typical example is something like this: the hardware register is 32 bits
137+wide, but only 18 of the bits have a physical counterpart. The driver is
138+generally written so that all 32 bits can be used, but the IP block is reused
139+in a lot of designs, some using all 32 bits, some using 18 and some using
140+12. In this case, setting "ngpios = <18>;" informs the driver that only the
141+first 18 GPIOs, at local offset 0 .. 17, are in use.
142+
143+If these GPIOs do not happen to be the first N GPIOs at offset 0...N-1, an
144+additional bitmask is needed to specify which GPIOs are actually in use,
145+and which are dummies. The bindings for this case has not yet been
146+specified, but should be specified if/when such hardware appears.
147+
148+Example:
149+
150+gpio-controller@00000000 {
151+ compatible = "foo";
152+ reg = <0x00000000 0x1000>;
153+ gpio-controller;
154+ #gpio-cells = <2>;
155+ ngpios = <18>;
156+}
157+
121158 The GPIO chip may contain GPIO hog definitions. GPIO hogging is a mechanism
122159 providing automatic GPIO request and configuration as part of the
123160 gpio-controller's driver probe function.
Documentation/devicetree/bindings/gpio/netxbig-gpio-ext.txt+22−0
@@ -0,0 +1,22 @@
1+Binding for the GPIO extension bus found on some LaCie/Seagate boards
2+(Example: 2Big/5Big Network v2, 2Big NAS).
3+
4+Required properties:
5+- compatible: "lacie,netxbig-gpio-ext".
6+- addr-gpios: GPIOs representing the address register (LSB -> MSB).
7+- data-gpios: GPIOs representing the data register (LSB -> MSB).
8+- enable-gpio: latches the new configuration (address, data) on raising edge.
9+
10+Example:
11+
12+netxbig_gpio_ext: netxbig-gpio-ext {
13+ compatible = "lacie,netxbig-gpio-ext";
14+
15+ addr-gpios = <&gpio1 15 GPIO_ACTIVE_HIGH
16+ &gpio1 16 GPIO_ACTIVE_HIGH
17+ &gpio1 17 GPIO_ACTIVE_HIGH>;
18+ data-gpios = <&gpio1 12 GPIO_ACTIVE_HIGH
19+ &gpio1 13 GPIO_ACTIVE_HIGH
20+ &gpio1 14 GPIO_ACTIVE_HIGH>;
21+ enable-gpio = <&gpio0 29 GPIO_ACTIVE_HIGH>;
22+};
Documentation/devicetree/bindings/hwmon/ina209.txt+0−18
@@ -1,18 +0,0 @@
1−ina209 properties
2−
3−Required properties:
4−- compatible: Must be "ti,ina209"
5−- reg: I2C address
6−
7−Optional properties:
8−
9−- shunt-resistor
10− Shunt resistor value in micro-Ohm
11−
12−Example:
13−
14−temp-sensor@4c {
15− compatible = "ti,ina209";
16− reg = <0x4c>;
17− shunt-resistor = <5000>;
18−};
Documentation/devicetree/bindings/hwmon/ina2xx.txt+1−0
@@ -2,6 +2,7 @@ ina2xx properties · 1 unmodified line
22
33 Required properties:
44 - compatible: Must be one of the following:
5+ - "ti,ina209" for ina209
56 - "ti,ina219" for ina219
67 - "ti,ina220" for ina220
78 - "ti,ina226" for ina226
Documentation/devicetree/bindings/hwmon/pwm-fan.txt+27−2
@@ -3,10 +3,35 @@ Bindings for a fan connected to the PWM lines · 2 unmodified lines
33 Required properties:
44 - compatible : "pwm-fan"
55 - pwms : the PWM that is used to control the PWM fan
6+- cooling-levels : PWM duty cycle values in a range from 0 to 255
7+ which correspond to thermal cooling states
68
79 Example:
8− pwm-fan {
10+ fan0: pwm-fan {
911 compatible = "pwm-fan";
10− status = "okay";
12+ cooling-min-state = <0>;
13+ cooling-max-state = <3>;
14+ #cooling-cells = <2>;
1115 pwms = <&pwm 0 10000 0>;
16+ cooling-levels = <0 102 170 230>;
1217 };
18+
19+ thermal-zones {
20+ cpu_thermal: cpu-thermal {
21+ thermal-sensors = <&tmu 0>;
22+ polling-delay-passive = <0>;
23+ polling-delay = <0>;
24+ trips {
25+ cpu_alert1: cpu-alert1 {
26+ temperature = <100000>; /* millicelsius */
27+ hysteresis = <2000>; /* millicelsius */
28+ type = "passive";
29+ };
30+ };
31+ cooling-maps {
32+ map0 {
33+ trip = <&cpu_alert1>;
34+ cooling-device = <&fan0 0 1>;
35+ };
36+ };
37+ };
Documentation/devicetree/bindings/i2c/i2c-davinci.txt+3−3
@@ -1,10 +1,10 @@
1−* Texas Instruments Davinci I2C
1+* Texas Instruments Davinci/Keystone I2C
22
33 This file provides information, what the device node for the
4−davinci i2c interface contain.
4+davinci/keystone i2c interface contains.
55
66 Required properties:
7−- compatible: "ti,davinci-i2c";
7+- compatible: "ti,davinci-i2c" or "ti,keystone-i2c";
88 - reg : Offset and length of the register set for the device
99
1010 Recommended properties :
Documentation/devicetree/bindings/i2c/i2c-imx.txt+9−0
@@ -14,6 +14,10 @@ Optional properties: · 13 unmodified lines
1414 The absence of the propoerty indicates the default frequency 100 kHz.
1515 - dmas: A list of two dma specifiers, one for each entry in dma-names.
1616 - dma-names: should contain "tx" and "rx".
17+- scl-gpios: specify the gpio related to SCL pin
18+- sda-gpios: specify the gpio related to SDA pin
19+- pinctrl: add extra pinctrl to configure i2c pins to gpio function for i2c
20+ bus recovery, call it "gpio" state
1721
1822 Examples:
1923
@@ -37,4 +41,9 @@ i2c0: i2c@40066000 { /* i2c0 on vf610 */ · 17 unmodified lines
3741 dmas = <&edma0 0 50>,
3842 <&edma0 0 51>;
3943 dma-names = "rx","tx";
44+ pinctrl-names = "default", "gpio";
45+ pinctrl-0 = <&pinctrl_i2c1>;
46+ pinctrl-1 = <&pinctrl_i2c1_gpio>;
47+ scl-gpios = <&gpio5 26 GPIO_ACTIVE_HIGH>;
48+ sda-gpios = <&gpio5 27 GPIO_ACTIVE_HIGH>;
4049 };
Documentation/devicetree/bindings/i2c/i2c-rcar.txt+1−0
@@ -10,6 +10,7 @@ Required properties: · 9 unmodified lines
1010 "renesas,i2c-r8a7792"
1111 "renesas,i2c-r8a7793"
1212 "renesas,i2c-r8a7794"
13+ "renesas,i2c-r8a7795"
1314 - reg: physical base address of the controller and length of memory mapped
1415 region.
1516 - interrupts: interrupt specifier.
Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt+1−0
@@ -10,6 +10,7 @@ Required properties: · 9 unmodified lines
1010 - "renesas,iic-r8a7792" (R-Car V2H)
1111 - "renesas,iic-r8a7793" (R-Car M2-N)
1212 - "renesas,iic-r8a7794" (R-Car E2)
13+ - "renesas,iic-r8a7795" (R-Car H3)
1314 - "renesas,iic-sh73a0" (SH-Mobile AG5)
1415 - reg : address start and address range size of device
1516 - interrupts : interrupt of device
Documentation/devicetree/bindings/i2c/i2c-uniphier-f.txt+25−0
@@ -0,0 +1,25 @@
1+UniPhier I2C controller (FIFO-builtin)
2+
3+Required properties:
4+- compatible: should be "socionext,uniphier-fi2c".
5+- #address-cells: should be 1.
6+- #size-cells: should be 0.
7+- reg: offset and length of the register set for the device.
8+- interrupts: a single interrupt specifier.
9+- clocks: phandle to the input clock.
10+
11+Optional properties:
12+- clock-frequency: desired I2C bus frequency in Hz. The maximum supported
13+ value is 400000. Defaults to 100000 if not specified.
14+
15+Examples:
16+
17+ i2c0: i2c@58780000 {
18+ compatible = "socionext,uniphier-fi2c";
19+ reg = <0x58780000 0x80>;
20+ #address-cells = <1>;
21+ #size-cells = <0>;
22+ interrupts = <0 41 4>;
23+ clocks = <&i2c_clk>;
24+ clock-frequency = <100000>;
25+ };
Documentation/devicetree/bindings/i2c/i2c-uniphier.txt+25−0
@@ -0,0 +1,25 @@
1+UniPhier I2C controller (FIFO-less)
2+
3+Required properties:
4+- compatible: should be "socionext,uniphier-i2c".
5+- #address-cells: should be 1.
6+- #size-cells: should be 0.
7+- reg: offset and length of the register set for the device.
8+- interrupts: a single interrupt specifier.
9+- clocks: phandle to the input clock.
10+
11+Optional properties:
12+- clock-frequency: desired I2C bus frequency in Hz. The maximum supported
13+ value is 400000. Defaults to 100000 if not specified.
14+
15+Examples:
16+
17+ i2c0: i2c@58400000 {
18+ compatible = "socionext,uniphier-i2c";
19+ reg = <0x58400000 0x40>;
20+ #address-cells = <1>;
21+ #size-cells = <0>;
22+ interrupts = <0 41 1>;
23+ clocks = <&i2c_clk>;
24+ clock-frequency = <100000>;
25+ };
Documentation/devicetree/bindings/i2c/trivial-devices.txt+2−1
@@ -54,7 +54,6 @@ epson,rx8581 I2C-BUS INTERFACE REAL TIME CLOCK MODULE · 53 unmodified lines
5454 fsl,mag3110 MAG3110: Xtrinsic High Accuracy, 3D Magnetometer
5555 fsl,mc13892 MC13892: Power Management Integrated Circuit (PMIC) for i.MX35/51
5656 fsl,mma8450 MMA8450Q: Xtrinsic Low-power, 3-axis Xtrinsic Accelerometer
57−fsl,mma8452 MMA8452Q: 3-axis 12-bit / 8-bit Digital Accelerometer
5857 fsl,mpr121 MPR121: Proximity Capacitive Touch Sensor Controller
5958 fsl,sgtl5000 SGTL5000: Ultra Low-Power Audio Codec
6059 gmt,g751 G751: Digital Temperature Sensor and Thermal Watchdog with Two-Wire Interface
@@ -80,6 +79,7 @@ oki,ml86v7667 OKI ML86V7667 video decoder · 19 unmodified lines
8079 ovti,ov5642 OV5642: Color CMOS QSXGA (5-megapixel) Image Sensor with OmniBSI and Embedded TrueFocus
8180 pericom,pt7c4338 Real-time Clock Module
8281 plx,pex8648 48-Lane, 12-Port PCI Express Gen 2 (5.0 GT/s) Switch
82+pulsedlight,lidar-lite-v2 Pulsedlight LIDAR range-finding sensor
8383 ramtron,24c64 i2c serial eeprom (24cxx)
8484 ricoh,r2025sd I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
8585 ricoh,r2221tl I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
@@ -88,6 +88,7 @@ ricoh,rs5c372b I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC · 2 unmodified lines
8888 ricoh,rv5c386 I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
8989 ricoh,rv5c387a I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
9090 samsung,24ad0xd1 S524AD0XF1 (128K/256K-bit Serial EEPROM for Low Power)
91+sgx,vz89x SGX Sensortech VZ89X Sensors
9192 sii,s35390a 2-wire CMOS real-time clock
9293 skyworks,sky81452 Skyworks SKY81452: Six-Channel White LED Driver with Touch Panel Bias Supply
9394 st-micro,24c256 i2c serial eeprom (24cxx)
Documentation/devicetree/bindings/iio/accel/lis302.txtrenamed from Documentation/devicetree/bindings/misc/lis302.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/iio/accel/mma8452.txt+24−0
@@ -0,0 +1,24 @@
1+Freescale MMA8452Q, MMA8453Q, MMA8652FC or MMA8653FC triaxial accelerometer
2+
3+Required properties:
4+
5+ - compatible: should contain one of
6+ * "fsl,mma8452"
7+ * "fsl,mma8453"
8+ * "fsl,mma8652"
9+ * "fsl,mma8653"
10+ - reg: the I2C address of the chip
11+
12+Optional properties:
13+
14+ - interrupt-parent: should be the phandle for the interrupt controller
15+ - interrupts: interrupt mapping for GPIO IRQ
16+
17+Example:
18+
19+ mma8453fc@1d {
20+ compatible = "fsl,mma8453";
21+ reg = <0x1d>;
22+ interrupt-parent = <&gpio1>;
23+ interrupts = <5 0>;
24+ };
Documentation/devicetree/bindings/iio/adc/hi8435.txt+21−0
@@ -0,0 +1,21 @@
1+Holt Integrated Circuits HI-8435 threshold detector bindings
2+
3+Required properties:
4+ - compatible: should be "holt,hi8435"
5+ - reg: spi chip select number for the device
6+
7+Recommended properties:
8+ - spi-max-frequency: definition as per
9+ Documentation/devicetree/bindings/spi/spi-bus.txt
10+
11+Optional properties:
12+ - gpios: GPIO used for controlling the reset pin
13+
14+Example:
15+sensor@0 {
16+ compatible = "holt,hi8435";
17+ reg = <0>;
18+ gpios = <&gpio6 1 0>;
19+
20+ spi-max-frequency = <1000000>;
21+};
Documentation/devicetree/bindings/iio/dac/ti,dac7512.txtrenamed from Documentation/devicetree/bindings/misc/ti,dac7512.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/iio/light/apds9960.txt+22−0
@@ -0,0 +1,22 @@
1+* Avago APDS9960 gesture/RGB/ALS/proximity sensor
2+
3+http://www.avagotech.com/docs/AV02-4191EN
4+
5+Required properties:
6+
7+ - compatible: must be "avago,apds9960"
8+ - reg: the I2c address of the sensor
9+ - interrupt-parent: should be the phandle for the interrupt controller
10+ - interrupts : the sole interrupt generated by the device
11+
12+ Refer to interrupt-controller/interrupts.txt for generic interrupt client
13+ node bindings.
14+
15+Example:
16+
17+apds9960@39 {
18+ compatible = "avago,apds9960";
19+ reg = <0x39>;
20+ interrupt-parent = <&gpio1>;
21+ interrupts = <16 1>;
22+};
Documentation/devicetree/bindings/iio/light/us5182d.txt+34−0
@@ -0,0 +1,34 @@
1+* UPISEMI us5182d I2C ALS and Proximity sensor
2+
3+Required properties:
4+- compatible: must be "upisemi,usd5182"
5+- reg: the I2C address of the device
6+
7+Optional properties:
8+- upisemi,glass-coef: glass attenuation factor - compensation factor of
9+ resolution 1000 for material transmittance.
10+- upisemi,dark-ths: array of 8 elements containing 16-bit thresholds (adc
11+ counts) corresponding to every scale.
12+- upisemi,upper-dark-gain: 8-bit dark gain compensation factor(4 int and 4
13+ fractional bits - Q4.4) applied when light > threshold
14+- upisemi,lower-dark-gain: 8-bit dark gain compensation factor(4 int and 4
15+ fractional bits - Q4.4) applied when light < threshold
16+
17+If the optional properties are not specified these factors will default to the
18+values in the below example.
19+The glass-coef defaults to no compensation for the covering material.
20+The threshold array defaults to experimental values that work with US5182D
21+sensor on evaluation board - roughly between 12-32 lux.
22+There will be no dark-gain compensation by default when ALS > thresh
23+(0 * dark-gain), and a 1.35 compensation factor when ALS < thresh.
24+
25+Example:
26+
27+ usd5182@39 {
28+ compatible = "upisemi,usd5182";
29+ reg = <0x39>;
30+ upisemi,glass-coef = < 1000 >;
31+ upisemi,dark-ths = /bits/ 16 <170 200 512 512 800 2000 4000 8000>;
32+ upisemi,upper-dark-gain = /bits/ 8 <0x00>;
33+ upisemi,lower-dark-gain = /bits/ 8 <0x16>;
34+ };
Documentation/devicetree/bindings/iio/pressure/bmp085.txtrenamed from Documentation/devicetree/bindings/misc/bmp085.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/input/ads7846.txt+2−1
@@ -65,6 +65,7 @@ Optional properties: · 64 unmodified lines
6565 pendown-gpio GPIO handle describing the pin the !PENIRQ
6666 line is connected to.
6767 wakeup-source use any event on touchscreen as wakeup event.
68+ (Legacy property support: "linux,wakeup")
6869
6970
7071 Example for a TSC2046 chip connected to an McSPI controller of an OMAP SoC::
@@ -86,6 +87,6 @@ Example for a TSC2046 chip connected to an McSPI controller of an OMAP SoC:: · 15 unmodified lines
8687 ti,x-plate-ohms = /bits/ 16 <40>;
8788 ti,pressure-max = /bits/ 16 <255>;
8889
89− linux,wakeup;
90+ wakeup-source;
9091 };
9192 };
Documentation/devicetree/bindings/input/cypress,cyapa.txt+1−1
@@ -25,7 +25,7 @@ Example: · 24 unmodified lines
2525 /* Cypress Gen3 touchpad */
2626 touchpad@67 {
2727 compatible = "cypress,cyapa";
28− reg = <0x24>;
28+ reg = <0x67>;
2929 interrupt-parent = <&gpio>;
3030 interrupts = <2 IRQ_TYPE_EDGE_FALLING>; /* GPIO 2 */
3131 wakeup-source;
Documentation/devicetree/bindings/input/da9062-onkey.txt+32−0
@@ -0,0 +1,32 @@
1+* Dialog DA9062/63 OnKey Module
2+
3+This module is part of the DA9062/DA9063. For more details about entire
4+chips see Documentation/devicetree/bindings/mfd/da9062.txt and
5+Documentation/devicetree/bindings/mfd/da9063.txt
6+
7+This module provides KEY_POWER, KEY_SLEEP and events.
8+
9+Required properties:
10+
11+- compatible: should be one of:
12+ dlg,da9062-onkey
13+ dlg,da9063-onkey
14+
15+Optional properties:
16+
17+ - dlg,disable-key-power : Disable power-down using a long key-press. If this
18+ entry exists the OnKey driver will remove support for the KEY_POWER key
19+ press. If this entry does not exist then by default the key-press
20+ triggered power down is enabled and the OnKey will support both KEY_POWER
21+ and KEY_SLEEP.
22+
23+Example:
24+
25+ pmic0: da9062@58 {
26+
27+ onkey {
28+ compatible = "dlg,da9063-onkey";
29+ dlg,disable-key-power;
30+ };
31+
32+ };
Documentation/devicetree/bindings/input/gpio-keys-polled.txt+9−1
@@ -13,14 +13,22 @@ Subnode properties: · 12 unmodified lines
1313
1414 - gpios: OF device-tree gpio specification.
1515 - label: Descriptive name of the key.
16− - linux,code: Keycode to emit.
16+ - linux,code: Key / Axis code to emit.
1717
1818 Optional subnode-properties:
1919 - linux,input-type: Specify event type this button/key generates.
2020 If not specified defaults to <1> == EV_KEY.
21+ - linux,input-value: If linux,input-type is EV_ABS or EV_REL then this
22+ value is sent for events this button generates when pressed.
23+ EV_ABS/EV_REL axis will generate an event with a value of 0 when
24+ all buttons with linux,input-type == type and linux,code == axis
25+ are released. This value is interpreted as a signed 32 bit value,
26+ e.g. to make a button generate a value of -1 use:
27+ linux,input-value = <0xffffffff>; /* -1 */
2128 - debounce-interval: Debouncing interval time in milliseconds.
2229 If not specified defaults to 5.
2330 - wakeup-source: Boolean, button can wake-up the system.
31+ (Legacy property supported: "gpio-key,wakeup")
2432
2533 Example nodes:
2634
Documentation/devicetree/bindings/input/gpio-keys.txt+1−0
@@ -24,6 +24,7 @@ Optional subnode-properties: · 23 unmodified lines
2424 - debounce-interval: Debouncing interval time in milliseconds.
2525 If not specified defaults to 5.
2626 - wakeup-source: Boolean, button can wake-up the system.
27+ (Legacy property supported: "gpio-key,wakeup")
2728 - linux,can-disable: Boolean, indicates that button is connected
2829 to dedicated (not shared) interrupt which can be disabled to
2930 suppress events from the button.
Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt+1−0
@@ -20,6 +20,7 @@ Required Properties: · 19 unmodified lines
2020 Optional Properties:
2121 - linux,no-autorepeat: do no enable autorepeat feature.
2222 - wakeup-source: use any event on keypad as wakeup event.
23+ (Legacy property supported: "linux,wakeup")
2324 - debounce-delay-ms: debounce interval in milliseconds
2425 - col-scan-delay-us: delay, measured in microseconds, that is needed
2526 before we can scan keypad after activating column gpio
Documentation/devicetree/bindings/input/hid-over-i2c.txtrenamed from Documentation/devicetree/bindings/hid/hid-over-i2c.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt+2−1
@@ -29,7 +29,8 @@ matrix-keyboard bindings: · 28 unmodified lines
2929 - nvidia,debounce-delay-ms: delay in milliseconds per row scan for debouncing
3030 - nvidia,repeat-delay-ms: delay in milliseconds before repeat starts
3131 - nvidia,ghost-filter: enable ghost filtering for this device
32−- nvidia,wakeup-source: configure keyboard as a wakeup source for suspend/resume
32+- wakeup-source: configure keyboard as a wakeup source for suspend/resume
33+ (Legacy property supported: "nvidia,wakeup-source")
3334
3435 Example:
3536
Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt+1−0
@@ -37,6 +37,7 @@ PROPERTIES · 36 unmodified lines
3737 Usage: optional
3838 Value type: <bool>
3939 Definition: use any event on keypad as wakeup event.
40+ (Legacy property supported: "linux,keypad-wakeup")
4041
4142 - keypad,num-rows:
4243 Usage: required
Documentation/devicetree/bindings/input/rotary-encoder.txt+10−0
@@ -14,7 +14,17 @@ Optional properties: · 13 unmodified lines
1414 device, hence no steps need to be passed.
1515 - rotary-encoder,rollover: Automatic rollove when the rotary value becomes
1616 greater than the specified steps or smaller than 0. For absolute axis only.
17+- rotary-encoder,steps-per-period: Number of steps (stable states) per period.
18+ The values have the following meaning:
19+ 1: Full-period mode (default)
20+ 2: Half-period mode
21+ 4: Quarter-period mode
22+- wakeup-source: Boolean, rotary encoder can wake up the system.
23+
24+Deprecated properties:
1725 - rotary-encoder,half-period: Makes the driver work on half-period mode.
26+ This property is deprecated. Instead, a 'steps-per-period ' value should
27+ be used, such as "rotary-encoder,steps-per-period = <2>".
1828
1929 See Documentation/input/rotary-encoder.txt for more information.
2030
Documentation/devicetree/bindings/input/samsung-keypad.txt+2−1
@@ -38,6 +38,7 @@ Required Board Specific Properties: · 37 unmodified lines
3838
3939 Optional Properties:
4040 - wakeup-source: use any event on keypad as wakeup event.
41+ (Legacy property supported: "linux,input-wakeup")
4142
4243 Optional Properties specific to linux:
4344 - linux,keypad-no-autorepeat: do no enable autorepeat feature.
@@ -51,7 +52,7 @@ Example: · 7 unmodified lines
5152 samsung,keypad-num-rows = <2>;
5253 samsung,keypad-num-columns = <8>;
5354 linux,input-no-autorepeat;
54− linux,input-wakeup;
55+ wakeup-source;
5556
5657 pinctrl-names = "default";
5758 pinctrl-0 = <&keypad_rows &keypad_columns>;
Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt+5−3
@@ -5,6 +5,7 @@ There are 3 variants of the chip for various touch panel sizes · 4 unmodified lines
55 FT5206GE1 2.8" .. 3.8"
66 FT5306DE4 4.3" .. 7"
77 FT5406EE8 7" .. 8.9"
8+FT5506EEG 7" .. 8.9"
89
910 The software interface is identical for all those chips, so that
1011 currently there is no need for the driver to distinguish between the
@@ -17,6 +18,7 @@ Required properties: · 6 unmodified lines
1718 - compatible: "edt,edt-ft5206"
1819 or: "edt,edt-ft5306"
1920 or: "edt,edt-ft5406"
21+ or: "edt,edt-ft5506"
2022
2123 - reg: I2C slave address of the chip (0x38)
2224 - interrupt-parent: a phandle pointing to the interrupt controller
@@ -49,7 +51,7 @@ Example: · 26 unmodified lines
4951 pinctrl-names = "default";
5052 pinctrl-0 = <&edt_ft5x06_pins>;
5153 interrupt-parent = <&gpio2>;
52− interrupts = <5 0>;
53− reset-gpios = <&gpio2 6 1>;
54− wake-gpios = <&gpio4 9 0>;
54+ interrupts = <5 IRQ_TYPE_EDGE_FALLING>;
55+ reset-gpios = <&gpio2 6 GPIO_ACTIVE_LOW>;
56+ wake-gpios = <&gpio4 9 GPIO_ACTIVE_HIGH>;
5557 };
Documentation/devicetree/bindings/input/touchscreen/focaltech-ft6236.txt+35−0
@@ -0,0 +1,35 @@
1+* FocalTech FT6236 I2C touchscreen controller
2+
3+Required properties:
4+ - compatible : "focaltech,ft6236"
5+ - reg : I2C slave address of the chip (0x38)
6+ - interrupt-parent : a phandle pointing to the interrupt controller
7+ serving the interrupt for this chip
8+ - interrupts : interrupt specification for the touch controller
9+ interrupt
10+ - reset-gpios : GPIO specification for the RSTN input
11+ - touchscreen-size-x : horizontal resolution of touchscreen (in pixels)
12+ - touchscreen-size-y : vertical resolution of touchscreen (in pixels)
13+
14+Optional properties:
15+ - touchscreen-fuzz-x : horizontal noise value of the absolute input
16+ device (in pixels)
17+ - touchscreen-fuzz-y : vertical noise value of the absolute input
18+ device (in pixels)
19+ - touchscreen-inverted-x : X axis is inverted (boolean)
20+ - touchscreen-inverted-y : Y axis is inverted (boolean)
21+ - touchscreen-swapped-x-y: X and Y axis are swapped (boolean)
22+ Swapping is done after inverting the axis
23+
24+Example:
25+
26+ ft6x06@38 {
27+ compatible = "focaltech,ft6236";
28+ reg = <0x38>;
29+ interrupt-parent = <&gpio>;
30+ interrupts = <23 2>;
31+ touchscreen-size-x = <320>;
32+ touchscreen-size-y = <480>;
33+ touchscreen-inverted-x;
34+ touchscreen-swapped-x-y;
35+ };
Documentation/devicetree/bindings/input/touchscreen/tsc2005.txt+28−6
@@ -1,14 +1,15 @@
1−* Texas Instruments tsc2005 touchscreen controller
1+* Texas Instruments tsc2004 and tsc2005 touchscreen controllers
22
33 Required properties:
4− - compatible : "ti,tsc2005"
5− - reg : SPI device address
6− - spi-max-frequency : Maximal SPI speed
4+ - compatible : "ti,tsc2004" or "ti,tsc2005"
5+ - reg : Device address
76 - interrupts : IRQ specifier
8− - reset-gpios : GPIO specifier
9− - vio-supply : Regulator specifier
7+ - spi-max-frequency : Maximum SPI clocking speed of the device
8+ (for tsc2005)
109
1110 Optional properties:
11+ - vio-supply : Regulator specifier
12+ - reset-gpios : GPIO specifier for the controller reset line
1213 - ti,x-plate-ohms : integer, resistance of the touchscreen's X plates
1314 in ohm (defaults to 280)
1415 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
@@ -18,6 +19,27 @@ Optional properties: · 3 unmodified lines
1819
1920 Example:
2021
22+&i2c3 {
23+ tsc2004@48 {
24+ compatible = "ti,tsc2004";
25+ reg = <0x48>;
26+ vio-supply = <&vio>;
27+
28+ reset-gpios = <&gpio4 8 GPIO_ACTIVE_HIGH>;
29+ interrupts-extended = <&gpio1 27 IRQ_TYPE_EDGE_RISING>;
30+
31+ touchscreen-fuzz-x = <4>;
32+ touchscreen-fuzz-y = <7>;
33+ touchscreen-fuzz-pressure = <2>;
34+ touchscreen-size-x = <4096>;
35+ touchscreen-size-y = <4096>;
36+ touchscreen-max-pressure = <2048>;
37+
38+ ti,x-plate-ohms = <280>;
39+ ti,esd-recovery-timeout-ms = <8000>;
40+ };
41+}
42+
2143 &mcspi1 {
2244 tsc2005@0 {
2345 compatible = "ti,tsc2005";
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txtrenamed from Documentation/devicetree/bindings/arm/gic-v3.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/arm,gic.txtrenamed from Documentation/devicetree/bindings/arm/gic.txt+20−4
@@ -11,13 +11,14 @@ have PPIs or SGIs. · 10 unmodified lines
1111 Main node required properties:
1212
1313 - compatible : should be one of:
14− "arm,gic-400"
14+ "arm,arm1176jzf-devchip-gic"
15+ "arm,arm11mp-gic"
1516 "arm,cortex-a15-gic"
16− "arm,cortex-a9-gic"
1717 "arm,cortex-a7-gic"
18− "arm,arm11mp-gic"
18+ "arm,cortex-a9-gic"
19+ "arm,gic-400"
20+ "arm,pl390"
1921 "brcm,brahma-b15-gic"
20− "arm,arm1176jzf-devchip-gic"
2122 "qcom,msm-8660-qgic"
2223 "qcom,msm-qgic2"
2324 - interrupt-controller : Identifies the node as an interrupt controller
@@ -58,6 +59,21 @@ Optional · 34 unmodified lines
5859 regions, used when the GIC doesn't have banked registers. The offset is
5960 cpu-offset * cpu-nr.
6061
62+- clocks : List of phandle and clock-specific pairs, one for each entry
63+ in clock-names.
64+- clock-names : List of names for the GIC clock input(s). Valid clock names
65+ depend on the GIC variant:
66+ "ic_clk" (for "arm,arm11mp-gic")
67+ "PERIPHCLKEN" (for "arm,cortex-a15-gic")
68+ "PERIPHCLK", "PERIPHCLKEN" (for "arm,cortex-a9-gic")
69+ "clk" (for "arm,gic-400")
70+ "gclk" (for "arm,pl390")
71+
72+- power-domains : A phandle and PM domain specifier as defined by bindings of
73+ the power controller specified by phandle, used when the GIC
74+ is part of a Power or Clock Domain.
75+
76+
6177 Example:
6278
6379 intc: interrupt-controller@fff11000 {
Documentation/devicetree/bindings/interrupt-controller/arm,versatile-fpga-irq.txtrenamed from Documentation/devicetree/bindings/arm/versatile-fpga-irq.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/arm,vic.txtrenamed from Documentation/devicetree/bindings/arm/vic.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/axis,crisv32-intc.txtrenamed from Documentation/devicetree/bindings/cris/interrupts.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/img,meta-intc.txtrenamed from Documentation/devicetree/bindings/metag/meta-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/img,pdc-intc.txtrenamed from Documentation/devicetree/bindings/metag/pdc-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-ioapic.txtrenamed from Documentation/devicetree/bindings/x86/interrupt.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txtrenamed from Documentation/devicetree/bindings/arm/mediatek/mediatek,sysirq.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/mrvl,intc.txtrenamed from Documentation/devicetree/bindings/arm/mrvl/intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/nxp,lpc3220-mic.txtrenamed from Documentation/devicetree/bindings/arm/lpc32xx-mic.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/open-pic.txtrenamed from Documentation/devicetree/bindings/open-pic.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/qca,ath79-misc-intc.txt+18−2
@@ -4,8 +4,8 @@ The MISC interrupt controller is a secondary controller for lower priority · 3 unmodified lines
44 interrupt.
55
66 Required Properties:
7−- compatible: has to be "qca,<soctype>-cpu-intc", "qca,ar7100-misc-intc"
8− as fallback
7+- compatible: has to be "qca,<soctype>-cpu-intc", "qca,ar7100-misc-intc" or
8+ "qca,<soctype>-cpu-intc", "qca,ar7240-misc-intc"
99 - reg: Base address and size of the controllers memory area
1010 - interrupt-parent: phandle of the parent interrupt controller.
1111 - interrupts: Interrupt specifier for the controllers interrupt.
@@ -13,6 +13,9 @@ Required Properties: · 1 unmodified line
1313 - #interrupt-cells : Specifies the number of cells needed to encode interrupt
1414 source, should be 1
1515
16+Compatible fallback depends on the SoC. Use ar7100 for ar71xx and ar913x,
17+use ar7240 for all other SoCs.
18+
1619 Please refer to interrupts.txt in this directory for details of the common
1720 Interrupt Controllers bindings used by client devices.
1821
@@ -28,3 +31,16 @@ Example: · 9 unmodified lines
2831 interrupt-controller;
2932 #interrupt-cells = <1>;
3033 };
34+
35+Another example:
36+
37+ interrupt-controller@18060010 {
38+ compatible = "qca,ar9331-misc-intc", qca,ar7240-misc-intc";
39+ reg = <0x18060010 0x4>;
40+
41+ interrupt-parent = <&cpuintc>;
42+ interrupts = <6>;
43+
44+ interrupt-controller;
45+ #interrupt-cells = <1>;
46+ };
Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt+1−0
@@ -10,6 +10,7 @@ Required properties: · 9 unmodified lines
1010 - "renesas,irqc-r8a7792" (R-Car V2H)
1111 - "renesas,irqc-r8a7793" (R-Car M2-N)
1212 - "renesas,irqc-r8a7794" (R-Car E2)
13+ - "renesas,intc-ex-r8a7795" (R-Car H3)
1314 - #interrupt-cells: has to be <2>: an interrupt index and flags, as defined in
1415 interrupts.txt in this directory
1516 - clocks: Must contain a reference to the functional clock.
Documentation/devicetree/bindings/interrupt-controller/samsung,exynos4210-combiner.txtrenamed from Documentation/devicetree/bindings/arm/samsung/interrupt-combiner.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/snps,arc700-intc.txtrenamed from Documentation/devicetree/bindings/arc/interrupts.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/snps,archs-idu-intc.txtrenamed from Documentation/devicetree/bindings/arc/archs-idu-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/snps,archs-intc.txtrenamed from Documentation/devicetree/bindings/arc/archs-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/st,spear3xx-shirq.txtrenamed from Documentation/devicetree/bindings/arm/spear/shirq.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/ti,c64x+megamod-pic.txtrenamed from Documentation/devicetree/bindings/c6x/interrupt.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/ti,cp-intc.txtrenamed from Documentation/devicetree/bindings/arm/davinci/cp-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/ti,omap2-intc.txtrenamed from Documentation/devicetree/bindings/arm/omap/intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.txtrenamed from Documentation/devicetree/bindings/arm/vt8500/via,vt8500-intc.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt+19−0
@@ -36,5 +36,24 @@ the PCIe specification. · 35 unmodified lines
3636 NOTE: this only applies to the SMMU itself, not
3737 masters connected upstream of the SMMU.
3838
39+- msi-parent : See the generic MSI binding described in
40+ devicetree/bindings/interrupt-controller/msi.txt
41+ for a description of the msi-parent property.
42+
3943 - hisilicon,broken-prefetch-cmd
4044 : Avoid sending CMD_PREFETCH_* commands to the SMMU.
45+
46+** Example
47+
48+ smmu@2b400000 {
49+ compatible = "arm,smmu-v3";
50+ reg = <0x0 0x2b400000 0x0 0x20000>;
51+ interrupts = <GIC_SPI 74 IRQ_TYPE_EDGE_RISING>,
52+ <GIC_SPI 75 IRQ_TYPE_EDGE_RISING>,
53+ <GIC_SPI 77 IRQ_TYPE_EDGE_RISING>,
54+ <GIC_SPI 79 IRQ_TYPE_EDGE_RISING>;
55+ interrupt-names = "eventq", "priq", "cmdq-sync", "gerror";
56+ dma-coherent;
57+ #iommu-cells = <0>;
58+ msi-parent = <&its 0xff0000>;
59+ };
Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt+1−1
@@ -47,7 +47,7 @@ Required properties: · 46 unmodified lines
4747 - clocks: Required if the System MMU is needed to gate its clock.
4848 - power-domains: Required if the System MMU is needed to gate its power.
4949 Please refer to the following document:
50− Documentation/devicetree/bindings/arm/exynos/power_domain.txt
50+ Documentation/devicetree/bindings/power/pd-samsung.txt
5151
5252 Examples:
5353 gsc_0: gsc@13e00000 {
Documentation/devicetree/bindings/iommu/ti,omap-iommu.txt+27−0
@@ -4,6 +4,7 @@ Required properties: · 3 unmodified lines
44 - compatible : Should be one of,
55 "ti,omap2-iommu" for OMAP2/OMAP3 IOMMU instances
66 "ti,omap4-iommu" for OMAP4/OMAP5 IOMMU instances
7+ "ti,dra7-dsp-iommu" for DRA7xx DSP IOMMU instances
78 "ti,dra7-iommu" for DRA7xx IOMMU instances
89 - ti,hwmods : Name of the hwmod associated with the IOMMU instance
910 - reg : Address space for the configuration registers
@@ -19,6 +20,13 @@ Optional properties: · 9 unmodified lines
1920 Should be either 8 or 32 (default: 32)
2021 - ti,iommu-bus-err-back : Indicates the IOMMU instance supports throwing
2122 back a bus error response on MMU faults.
23+- ti,syscon-mmuconfig : Should be a pair of the phandle to the DSP_SYSTEM
24+ syscon node that contains the additional control
25+ register for enabling the MMU, and the MMU instance
26+ number (0-indexed) within the sub-system. This property
27+ is required for DSP IOMMU instances on DRA7xx SoCs. The
28+ instance number should be 0 for DSP MDMA MMUs and 1 for
29+ DSP EDMA MMUs.
2230
2331 Example:
2432 /* OMAP3 ISP MMU */
@@ -30,3 +38,22 @@ Example: · 5 unmodified lines
3038 ti,hwmods = "mmu_isp";
3139 ti,#tlb-entries = <8>;
3240 };
41+
42+ /* DRA74x DSP2 MMUs */
43+ mmu0_dsp2: mmu@41501000 {
44+ compatible = "ti,dra7-dsp-iommu";
45+ reg = <0x41501000 0x100>;
46+ interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
47+ ti,hwmods = "mmu0_dsp2";
48+ #iommu-cells = <0>;
49+ ti,syscon-mmuconfig = <&dsp2_system 0x0>;
50+ };
51+
52+ mmu1_dsp2: mmu@41502000 {
53+ compatible = "ti,dra7-dsp-iommu";
54+ reg = <0x41502000 0x100>;
55+ interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
56+ ti,hwmods = "mmu1_dsp2";
57+ #iommu-cells = <0>;
58+ ti,syscon-mmuconfig = <&dsp2_system 0x1>;
59+ };
Documentation/devicetree/bindings/leds/backlight/88pm860x.txtrenamed from Documentation/devicetree/bindings/video/backlight/88pm860x.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/gpio-backlight.txtrenamed from Documentation/devicetree/bindings/video/backlight/gpio-backlight.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/lp855x.txtrenamed from Documentation/devicetree/bindings/video/backlight/lp855x.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/max8925-backlight.txtrenamed from Documentation/devicetree/bindings/video/backlight/max8925-backlight.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/pm8941-wled.txtrenamed from Documentation/devicetree/bindings/video/backlight/pm8941-wled.txt+2−0
@@ -5,6 +5,8 @@ Required properties: · 4 unmodified lines
55 - reg: slave address
66
77 Optional properties:
8+- default-brightness: brightness value on boot, value from: 0-4095
9+ default: 2048
810 - label: The name of the backlight device
911 - qcom,cs-out: bool; enable current sink output
1012 - qcom,cabc: bool; enable content adaptive backlight control
Documentation/devicetree/bindings/leds/backlight/pwm-backlight.txtrenamed from Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/sky81452-backlight.txtrenamed from Documentation/devicetree/bindings/video/backlight/sky81452-backlight.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/backlight/tps65217-backlight.txtrenamed from Documentation/devicetree/bindings/video/backlight/tps65217-backlight.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/leds/leds-aat1290.txt+4−4
@@ -27,9 +27,9 @@ Required properties of the LED child node: · 26 unmodified lines
2727 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
2828 Maximum flash LED supply current can be calculated using
2929 following formula: I = 1A * 162kohm / Rset.
30−- flash-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
31− Maximum flash timeout can be calculated using following
32− formula: T = 8.82 * 10^9 * Ct.
30+- flash-max-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
31+ Maximum flash timeout can be calculated using following
32+ formula: T = 8.82 * 10^9 * Ct.
3333
3434 Optional properties of the LED child node:
3535 - label : see Documentation/devicetree/bindings/leds/common.txt
@@ -54,7 +54,7 @@ aat1290 { · 18 unmodified lines
5454 label = "aat1290-flash";
5555 led-max-microamp = <520833>;
5656 flash-max-microamp = <1012500>;
57− flash-timeout-us = <1940000>;
57+ flash-max-timeout-us = <1940000>;
5858 };
5959 };
6060
Documentation/devicetree/bindings/leds/leds-bcm6328.txt+10−0
@@ -29,6 +29,14 @@ Required properties: · 28 unmodified lines
2929 Optional properties:
3030 - brcm,serial-leds : Boolean, enables Serial LEDs.
3131 Default : false
32+ - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
33+ Default : false
34+ - brcm,serial-clk-low : Boolean, makes clock signal active low.
35+ Default : false
36+ - brcm,serial-dat-low : Boolean, makes data signal active low.
37+ Default : false
38+ - brcm,serial-shift-inv : Boolean, inverts Serial LEDs shift direction.
39+ Default : false
3240
3341 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
3442
@@ -110,6 +118,8 @@ Scenario 2 : BCM63268 with Serial/GPHY0 LEDs · 75 unmodified lines
110118 #size-cells = <0>;
111119 reg = <0x10001900 0x24>;
112120 brcm,serial-leds;
121+ brcm,serial-dat-low;
122+ brcm,serial-shift-inv;
113123
114124 gphy0_spd0@0 {
115125 reg = <0>;
Documentation/devicetree/bindings/leds/leds-netxbig.txt+92−0
@@ -0,0 +1,92 @@
1+Binding for the CPLD LEDs (GPIO extension bus) found on some LaCie/Seagate
2+boards (Example: 2Big/5Big Network v2, 2Big NAS).
3+
4+Required properties:
5+- compatible: "lacie,netxbig-leds".
6+- gpio-ext: Phandle for the gpio-ext bus.
7+
8+Optional properties:
9+- timers: Timer array. Each timer entry is represented by three integers:
10+ Mode (gpio-ext bus), delay_on and delay_off.
11+
12+Each LED is represented as a sub-node of the netxbig-leds device.
13+
14+Required sub-node properties:
15+- mode-addr: Mode register address on gpio-ext bus.
16+- mode-val: Mode to value mapping. Each entry is represented by two integers:
17+ A mode and the corresponding value on the gpio-ext bus.
18+- bright-addr: Brightness register address on gpio-ext bus.
19+- max-brightness: Maximum brightness value.
20+
21+Optional sub-node properties:
22+- label: Name for this LED. If omitted, the label is taken from the node name.
23+- linux,default-trigger: Trigger assigned to the LED.
24+
25+Example:
26+
27+netxbig-leds {
28+ compatible = "lacie,netxbig-leds";
29+
30+ gpio-ext = &gpio_ext;
31+
32+ timers = <NETXBIG_LED_TIMER1 500 500
33+ NETXBIG_LED_TIMER2 500 1000>;
34+
35+ blue-power {
36+ label = "netxbig:blue:power";
37+ mode-addr = <0>;
38+ mode-val = <NETXBIG_LED_OFF 0
39+ NETXBIG_LED_ON 1
40+ NETXBIG_LED_TIMER1 3
41+ NETXBIG_LED_TIMER2 7>;
42+ bright-addr = <1>;
43+ max-brightness = <7>;
44+ };
45+ red-power {
46+ label = "netxbig:red:power";
47+ mode-addr = <0>;
48+ mode-val = <NETXBIG_LED_OFF 0
49+ NETXBIG_LED_ON 2
50+ NETXBIG_LED_TIMER1 4>;
51+ bright-addr = <1>;
52+ max-brightness = <7>;
53+ };
54+ blue-sata0 {
55+ label = "netxbig:blue:sata0";
56+ mode-addr = <3>;
57+ mode-val = <NETXBIG_LED_OFF 0
58+ NETXBIG_LED_ON 7
59+ NETXBIG_LED_SATA 1
60+ NETXBIG_LED_TIMER1 3>;
61+ bright-addr = <2>;
62+ max-brightness = <7>;
63+ };
64+ red-sata0 {
65+ label = "netxbig:red:sata0";
66+ mode-addr = <3>;
67+ mode-val = <NETXBIG_LED_OFF 0
68+ NETXBIG_LED_ON 2
69+ NETXBIG_LED_TIMER1 4>;
70+ bright-addr = <2>;
71+ max-brightness = <7>;
72+ };
73+ blue-sata1 {
74+ label = "netxbig:blue:sata1";
75+ mode-addr = <4>;
76+ mode-val = <NETXBIG_LED_OFF 0
77+ NETXBIG_LED_ON 7
78+ NETXBIG_LED_SATA 1
79+ NETXBIG_LED_TIMER1 3>;
80+ bright-addr = <2>;
81+ max-brightness = <7>;
82+ };
83+ red-sata1 {
84+ label = "netxbig:red:sata1";
85+ mode-addr = <4>;
86+ mode-val = <NETXBIG_LED_OFF 0
87+ NETXBIG_LED_ON 2
88+ NETXBIG_LED_TIMER1 4>;
89+ bright-addr = <2>;
90+ max-brightness = <7>;
91+ };
92+};
Documentation/devicetree/bindings/mailbox/omap-mailbox.txt+8−0
@@ -75,6 +75,14 @@ data that represent the following: · 74 unmodified lines
7575 Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
7676 associated with generating a tx/rx fifo interrupt.
7777
78+Optional Properties:
79+--------------------
80+- ti,mbox-send-noirq: Quirk flag to allow the client user of this sub-mailbox
81+ to send messages without triggering a Tx ready interrupt,
82+ and to control the Tx ticker. Should be used only on
83+ sub-mailboxes used to communicate with WkupM3 remote
84+ processor on AM33xx/AM43xx SoCs.
85+
7886 Mailbox Users:
7987 ==============
8088 A device needing to communicate with a target processor device should specify
Documentation/devicetree/bindings/mailbox/sti-mailbox.txt+51−0
@@ -0,0 +1,51 @@
1+ST Microelectronics Mailbox Driver
2+
3+Each ST Mailbox IP currently consists of 4 instances of 32 channels. Messages
4+are passed between Application and Remote processors using shared memory.
5+
6+Controller
7+----------
8+
9+Required properties:
10+- compatible : Should be "st,stih407-mailbox"
11+- reg : Offset and length of the device's register set
12+- mbox-name : Name of the mailbox
13+- #mbox-cells: : Must be 2
14+ <&phandle instance channel direction>
15+ phandle : Label name of controller
16+ instance : Instance number
17+ channel : Channel number
18+
19+Optional properties
20+- interrupts : Contains the IRQ line for a Rx mailbox
21+
22+Example:
23+
24+mailbox0: mailbox@0 {
25+ compatible = "st,stih407-mailbox";
26+ reg = <0x08f00000 0x1000>;
27+ interrupts = <GIC_SPI 1 IRQ_TYPE_NONE>;
28+ #mbox-cells = <2>;
29+ mbox-name = "a9";
30+};
31+
32+Client
33+------
34+
35+Required properties:
36+- compatible : Many (See the client docs)
37+- reg : Shared (between Application and Remote) memory address
38+- mboxes : Standard property to specify a Mailbox (See ./mailbox.txt)
39+ Cells must match 'mbox-cells' (See Controller docs above)
40+
41+Optional properties
42+- mbox-names : Name given to channels seen in the 'mboxes' property.
43+
44+Example:
45+
46+mailbox_test {
47+ compatible = "mailbox_test";
48+ reg = <0x[shared_memory_address], [shared_memory_size]>;
49+ mboxes = <&mailbox2 0 1>, <&mailbox0 2 1>;
50+ mbox-names = "tx", "rx";
51+};
Documentation/devicetree/bindings/media/exynos-jpeg-codec.txt+2−1
@@ -4,7 +4,8 @@ Required properties: · 3 unmodified lines
44
55 - compatible : should be one of:
66 "samsung,s5pv210-jpeg", "samsung,exynos4210-jpeg",
7− "samsung,exynos3250-jpeg", "samsung,exynos5420-jpeg";
7+ "samsung,exynos3250-jpeg", "samsung,exynos5420-jpeg",
8+ "samsung,exynos5433-jpeg";
89 - reg : address and length of the JPEG codec IP register set;
910 - interrupts : specifies the JPEG codec IP interrupt;
1011 - clock-names : should contain:
Documentation/devicetree/bindings/memory-controllers/arm,pl172.txt+5−3
@@ -1,8 +1,9 @@
1−* Device tree bindings for ARM PL172 MultiPort Memory Controller
1+* Device tree bindings for ARM PL172/PL175/PL176 MultiPort Memory Controller
22
33 Required properties:
44
5−- compatible: "arm,pl172", "arm,primecell"
5+- compatible: Must be "arm,primecell" and exactly one from
6+ "arm,pl172", "arm,pl175" or "arm,pl176".
67
78 - reg: Must contains offset/length value for controller.
89
@@ -56,7 +57,8 @@ Optional child cs node config properties: · 47 unmodified lines
5657
5758 - mpmc,extended-wait: Enable extended wait.
5859
59−- mpmc,buffer-enable: Enable write buffer.
60+- mpmc,buffer-enable: Enable write buffer, option is not supported by
61+ PL175 and PL176 controllers.
6062
6163 - mpmc,write-protect: Enable write protect.
6264
Documentation/devicetree/bindings/memory-controllers/calxeda-ddr-ctrlr.txtrenamed from Documentation/devicetree/bindings/arm/calxeda/mem-ctrlr.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/memory-controllers/renesas-memory-controllers.txt+3−3
@@ -24,9 +24,9 @@ Required properties: · 23 unmodified lines
2424 Optional properties:
2525 - interrupts: Must contain a list of interrupt specifiers for memory
2626 controller interrupts, if available.
27− - interrupts-names: Must contain a list of interrupt names corresponding to
28− the interrupts in the interrupts property, if available.
29− Valid interrupt names are:
27+ - interrupt-names: Must contain a list of interrupt names corresponding to
28+ the interrupts in the interrupts property, if available.
29+ Valid interrupt names are:
3030 - "sec" (secure interrupt)
3131 - "temp" (normal (temperature) interrupt)
3232 - power-domains: Must contain a reference to the PM domain that the memory
Documentation/devicetree/bindings/mfd/arizona.txt+3−12
@@ -44,7 +44,6 @@ Required properties: · 43 unmodified lines
4444 Optional properties:
4545
4646 - wlf,reset : GPIO specifier for the GPIO controlling /RESET
47− - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA
4847
4948 - wlf,gpio-defaults : A list of GPIO configuration register values. Defines
5049 for the appropriate values can found in <dt-bindings/mfd/arizona.txt>. If
@@ -67,21 +66,13 @@ Optional properties: · 16 unmodified lines
6766 present, the number of values should be less than or equal to the
6867 number of inputs, unspecified inputs will use the chip default.
6968
70− - wlf,hpdet-channel : Headphone detection channel.
71− ARIZONA_ACCDET_MODE_HPL or 1 - Headphone detect mode is set to HPDETL
72− ARIZONA_ACCDET_MODE_HPR or 2 - Headphone detect mode is set to HPDETR
73− If this node is not mentioned or if the value is unknown, then
74− headphone detection mode is set to HPDETL.
75−
7669 - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if
7770 they are being externally supplied. As covered in
7871 Documentation/devicetree/bindings/regulator/regulator.txt
7972
80−Optional subnodes:
81− - ldo1 : Initial data for the LDO1 regulator, as covered in
82− Documentation/devicetree/bindings/regulator/regulator.txt
83− - micvdd : Initial data for the MICVDD regulator, as covered in
84− Documentation/devicetree/bindings/regulator/regulator.txt
73+Also see child specific device properties:
74+ Regulator - ../regulator/arizona-regulator.txt
75+ Extcon - ../extcon/extcon-arizona.txt
8576
8677 Example:
8778
Documentation/devicetree/bindings/mfd/atmel-flexcom.txt+63−0
@@ -0,0 +1,63 @@
1+* Device tree bindings for Atmel Flexcom (Flexible Serial Communication Unit)
2+
3+The Atmel Flexcom is just a wrapper which embeds a SPI controller, an I2C
4+controller and an USART. Only one function can be used at a time and is chosen
5+at boot time according to the device tree.
6+
7+Required properties:
8+- compatible: Should be "atmel,sama5d2-flexcom"
9+- reg: Should be the offset/length value for Flexcom dedicated
10+ I/O registers (without USART, TWI or SPI registers).
11+- clocks: Should be the Flexcom peripheral clock from PMC.
12+- #address-cells: Should be <1>
13+- #size-cells: Should be <1>
14+- ranges: Should be one range for the full I/O register region
15+ (including USART, TWI and SPI registers).
16+- atmel,flexcom-mode: Should be one of the following values:
17+ - <1> for USART
18+ - <2> for SPI
19+ - <3> for I2C
20+
21+Required child:
22+A single available child device of type matching the "atmel,flexcom-mode"
23+property.
24+
25+The phandle provided by the clocks property of the child is the same as one for
26+the Flexcom parent.
27+
28+For other properties, please refer to the documentations of the respective
29+device:
30+- ../serial/atmel-usart.txt
31+- ../spi/spi_atmel.txt
32+- ../i2c/i2c-at91.txt
33+
34+Example:
35+
36+flexcom@f8034000 {
37+ compatible = "atmel,sama5d2-flexcom";
38+ reg = <0xf8034000 0x200>;
39+ clocks = <&flx0_clk>;
40+ #address-cells = <1>;
41+ #size-cells = <1>;
42+ ranges = <0x0 0xf8034000 0x800>;
43+ atmel,flexcom-mode = <2>;
44+
45+ spi@400 {
46+ compatible = "atmel,at91rm9200-spi";
47+ reg = <0x400 0x200>;
48+ interrupts = <19 IRQ_TYPE_LEVEL_HIGH 7>;
49+ pinctrl-names = "default";
50+ pinctrl-0 = <&pinctrl_flx0_default>;
51+ #address-cells = <1>;
52+ #size-cells = <0>;
53+ clocks = <&flx0_clk>;
54+ clock-names = "spi_clk";
55+ atmel,fifo-size = <32>;
56+
57+ mtd_dataflash@0 {
58+ compatible = "atmel,at25f512b";
59+ reg = <0>;
60+ spi-max-frequency = <20000000>;
61+ };
62+ };
63+};
Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt+1−1
@@ -15,7 +15,7 @@ Required properties: · 14 unmodified lines
1515
1616 The HLCDC IP exposes two subdevices:
1717 - a PWM chip: see ../pwm/atmel-hlcdc-pwm.txt
18− - a Display Controller: see ../drm/atmel-hlcdc-dc.txt
18+ - a Display Controller: see ../display/atmel-hlcdc-dc.txt
1919
2020 Example:
2121
Documentation/devicetree/bindings/mfd/axp20x.txt+2−2
@@ -60,8 +60,8 @@ DCDC2 : DC-DC buck : vin2-supply · 59 unmodified lines
6060 DCDC3 : DC-DC buck : vin3-supply
6161 DCDC4 : DC-DC buck : vin4-supply
6262 DCDC5 : DC-DC buck : vin5-supply
63−DC1SW : On/Off Switch : dcdc1-supply : DCDC1 secondary output
64−DC5LDO : LDO : dcdc5-supply : input from DCDC5
63+DC1SW : On/Off Switch : : DCDC1 secondary output
64+DC5LDO : LDO : : input from DCDC5
6565 ALDO1 : LDO : aldoin-supply : shared supply
6666 ALDO2 : LDO : aldoin-supply : shared supply
6767 ALDO3 : LDO : aldoin-supply : shared supply
Documentation/devicetree/bindings/mfd/cros-ec.txt+4−0
@@ -34,6 +34,10 @@ Required properties (LPC): · 33 unmodified lines
3434 - compatible: "google,cros-ec-lpc"
3535 - reg: List of (IO address, size) pairs defining the interface uses
3636
37+Optional properties (all):
38+- google,has-vbc-nvram: Some implementations of the EC include a small
39+ nvram space used to store verified boot context data. This boolean flag
40+ is used to specify whether this nvram is present or not.
3741
3842 Example for I2C:
3943
Documentation/devicetree/bindings/mfd/da9150.txt+26−7
@@ -6,6 +6,7 @@ Device Description · 5 unmodified lines
66 ------ -----------
77 da9150-gpadc : General Purpose ADC
88 da9150-charger : Battery Charger
9+da9150-fg : Battery Fuel-Gauge
910
1011 ======
1112
@@ -16,13 +17,13 @@ Required properties: · 4 unmodified lines
1617 the IRQs from da9150 are delivered to.
1718 - interrupts: IRQ line info for da9150 chip.
1819 - interrupt-controller: da9150 has internal IRQs (own IRQ domain).
19− (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for
20+ (See ../interrupt-controller/interrupts.txt for
2021 further information relating to interrupt properties)
2122
2223 Sub-devices:
23−- da9150-gpadc: See Documentation/devicetree/bindings/iio/adc/da9150-gpadc.txt
24−- da9150-charger: See Documentation/devicetree/bindings/power/da9150-charger.txt
25−
24+- da9150-gpadc: See ../iio/adc/da9150-gpadc.txt
25+- da9150-charger: See ../power/da9150-charger.txt
26+- da9150-fg: See ../power/da9150-fg.txt
2627
2728 Example:
2829
@@ -34,10 +35,28 @@ Example: · 5 unmodified lines
3435 interrupt-controller;
3536
3637 gpadc: da9150-gpadc {
37− ...
38+ compatible = "dlg,da9150-gpadc";
39+ #io-channel-cells = <1>;
40+ };
41+
42+ charger {
43+ compatible = "dlg,da9150-charger";
44+
45+ io-channels = <&gpadc 0>,
46+ <&gpadc 2>,
47+ <&gpadc 8>,
48+ <&gpadc 5>;
49+ io-channel-names = "CHAN_IBUS",
50+ "CHAN_VBUS",
51+ "CHAN_TJUNC",
52+ "CHAN_VBAT";
3853 };
3954
40− da9150-charger {
41− ...
55+ fuel-gauge {
56+ compatible = "dlg,da9150-fuel-gauge";
57+
58+ dlg,update-interval = <10000>;
59+ dlg,warn-soc-level = /bits/ 8 <15>;
60+ dlg,crit-soc-level = /bits/ 8 <5>
4261 };
4362 };
Documentation/devicetree/bindings/mfd/s2mps11.txt+21−7
@@ -1,5 +1,5 @@
11
2−* Samsung S2MPS11, S2MPS13, S2MPS14 and S2MPU02 Voltage and Current Regulator
2+* Samsung S2MPS11/13/14/15 and S2MPU02 Voltage and Current Regulator
33
44 The Samsung S2MPS11 is a multi-function device which includes voltage and
55 current regulators, RTC, charger controller and other sub-blocks. It is
@@ -7,17 +7,28 @@ interfaced to the host controller using an I2C interface. Each sub-block is · 1 unmodified line
77 addressed by the host system using different I2C slave addresses.
88
99 Required properties:
10−- compatible: Should be "samsung,s2mps11-pmic" or "samsung,s2mps13-pmic"
11− or "samsung,s2mps14-pmic" or "samsung,s2mpu02-pmic".
10+- compatible: Should be one of the following
11+ - "samsung,s2mps11-pmic"
12+ - "samsung,s2mps13-pmic"
13+ - "samsung,s2mps14-pmic"
14+ - "samsung,s2mps15-pmic"
15+ - "samsung,s2mpu02-pmic".
1216 - reg: Specifies the I2C slave address of the pmic block. It should be 0x66.
1317
1418 Optional properties:
1519 - interrupt-parent: Specifies the phandle of the interrupt controller to which
1620 the interrupts from s2mps11 are delivered to.
1721 - interrupts: Interrupt specifiers for interrupt sources.
22+- samsung,s2mps11-wrstbi-ground: Indicates that WRSTBI pin of PMIC is pulled
23+ down. When the system is suspended it will always go down thus triggerring
24+ unwanted buck warm reset (setting buck voltages to default values).
25+- samsung,s2mps11-acokb-ground: Indicates that ACOKB pin of S2MPS11 PMIC is
26+ connected to the ground so the PMIC must manually set PWRHOLD bit in CTRL1
27+ register to turn off the power. Usually the ACOKB is pulled up to VBATT so
28+ when PWRHOLD pin goes low, the rising ACOKB will trigger power off.
1829
1930 Optional nodes:
20−- clocks: s2mps11, s2mps13 and s5m8767 provide three(AP/CP/BT) buffered 32.768
31+- clocks: s2mps11, s2mps13, s2mps15 and s5m8767 provide three(AP/CP/BT) buffered 32.768
2132 KHz outputs, so to register these as clocks with common clock framework
2233 instantiate a sub-node named "clocks". It uses the common clock binding
2334 documented in :
@@ -30,12 +41,13 @@ Optional nodes: · 6 unmodified lines
3041 the clock which they consume.
3142 Clock ID Devices
3243 ----------------------------------------------------------
33− 32KhzAP 0 S2MPS11, S2MPS13, S2MPS14, S5M8767
34− 32KhzCP 1 S2MPS11, S2MPS13, S5M8767
35− 32KhzBT 2 S2MPS11, S2MPS13, S2MPS14, S5M8767
44+ 32KhzAP 0 S2MPS11, S2MPS13, S2MPS14, S2MPS15, S5M8767
45+ 32KhzCP 1 S2MPS11, S2MPS13, S2MPS15, S5M8767
46+ 32KhzBT 2 S2MPS11, S2MPS13, S2MPS14, S2MPS15, S5M8767
3647
3748 - compatible: Should be one of: "samsung,s2mps11-clk", "samsung,s2mps13-clk",
3849 "samsung,s2mps14-clk", "samsung,s5m8767-clk"
50+ The s2msp15 uses the same compatible as s2mps13, as both provides similar clocks.
3951
4052 - regulators: The regulators of s2mps11 that have to be instantiated should be
4153 included in a sub-node named 'regulators'. Regulator nodes included in this
@@ -83,6 +95,7 @@ as per the datasheet of s2mps11. · 41 unmodified lines
8395 - S2MPS11: 1 to 38
8496 - S2MPS13: 1 to 40
8597 - S2MPS14: 1 to 25
98+ - S2MPS15: 1 to 27
8699 - S2MPU02: 1 to 28
87100 - Example: LDO1, LDO2, LDO28
88101 - BUCKn
@@ -90,6 +103,7 @@ as per the datasheet of s2mps11. · 1 unmodified line
90103 - S2MPS11: 1 to 10
91104 - S2MPS13: 1 to 10
92105 - S2MPS14: 1 to 5
106+ - S2MPS15: 1 to 10
93107 - S2MPU02: 1 to 7
94108 - Example: BUCK1, BUCK2, BUCK9
95109
Documentation/devicetree/bindings/mfd/sky81452.txt+1−1
@@ -6,7 +6,7 @@ Required properties: · 5 unmodified lines
66
77 Required child nodes:
88 - backlight : container node for backlight following the binding
9− in video/backlight/sky81452-backlight.txt
9+ in leds/backlight/sky81452-backlight.txt
1010 - regulator : container node for regulators following the binding
1111 in regulator/sky81452-regulator.txt
1212
Documentation/devicetree/bindings/mfd/tc3589x.txt+1−0
@@ -56,6 +56,7 @@ Optional nodes: · 55 unmodified lines
5656 bindings/input/matrix-keymap.txt
5757 - linux,no-autorepeat: do no enable autorepeat feature.
5858 - wakeup-source: use any event on keypad as wakeup event.
59+ (Legacy property supported: "linux,wakeup")
5960
6061 Example:
6162
Documentation/devicetree/bindings/mips/img/xilfpga.txt+83−0
@@ -0,0 +1,83 @@
1+Imagination University Program MIPSfpga
2+=======================================
3+
4+Under the Imagination University Program, a microAptiv UP core has been
5+released for academic usage.
6+
7+As we are dealing with a MIPS core instantiated on an FPGA, specifications
8+are fluid and can be varied in RTL.
9+
10+This binding document is provided as baseline guidance for the example
11+project provided by IMG.
12+
13+The example project runs on the Nexys4DDR board by Digilent powered by
14+the ARTIX-7 FPGA by Xilinx.
15+
16+Relevant details about the example project and the Nexys4DDR board:
17+
18+- microAptiv UP core m14Kc
19+- 50MHz clock speed
20+- 128Mbyte DDR RAM at 0x0000_0000
21+- 8Kbyte RAM at 0x1000_0000
22+- axi_intc at 0x1020_0000
23+- axi_uart16550 at 0x1040_0000
24+- axi_gpio at 0x1060_0000
25+- axi_i2c at 0x10A0_0000
26+- custom_gpio at 0x10C0_0000
27+- axi_ethernetlite at 0x10E0_0000
28+- 8Kbyte BootRAM at 0x1FC0_0000
29+
30+Required properties:
31+--------------------
32+ - compatible: Must include "digilent,nexys4ddr","img,xilfpga".
33+
34+CPU nodes:
35+----------
36+A "cpus" node is required. Required properties:
37+ - #address-cells: Must be 1.
38+ - #size-cells: Must be 0.
39+A CPU sub-node is also required for at least CPU 0. Required properties:
40+ - device_type: Must be "cpu".
41+ - compatible: Must be "mips,m14Kc".
42+ - reg: Must be <0>.
43+ - clocks: phandle to ext clock for fixed-clock received by MIPS core.
44+
45+Example:
46+
47+ compatible = "img,xilfpga","digilent,nexys4ddr";
48+ cpus {
49+ #address-cells = <1>;
50+ #size-cells = <0>;
51+
52+ cpu0: cpu@0 {
53+ device_type = "cpu";
54+ compatible = "mips,m14Kc";
55+ reg = <0>;
56+ clocks = <&ext>;
57+ };
58+ };
59+
60+ ext: ext {
61+ compatible = "fixed-clock";
62+ #clock-cells = <0>;
63+ clock-frequency = <50000000>;
64+ };
65+
66+Boot protocol:
67+--------------
68+
69+The BootRAM is a writeable "RAM" in FPGA at 0x1FC0_0000.
70+This is for easy reprogrammibility via JTAG.
71+
72+The BootRAM initializes the cache and the axi_uart peripheral.
73+
74+DDR initialization is already handled by a HW IP block.
75+
76+When the example project bitstream is loaded, the cpu_reset button
77+needs to be pressed.
78+
79+The bootram initializes the cache and axi_uart.
80+Then outputs MIPSFPGA\n\r on the serial port on the Nexys4DDR board.
81+
82+At this point, the board is ready to load the Linux kernel
83+vmlinux file via JTAG.
Documentation/devicetree/bindings/misc/sram.txt+16−0
@@ -33,6 +33,12 @@ Optional properties in the area nodes: · 32 unmodified lines
3333
3434 - compatible : standard definition, should contain a vendor specific string
3535 in the form <vendor>,[<device>-]<usage>
36+- pool : indicates that the particular reserved SRAM area is addressable
37+ and in use by another device or devices
38+- export : indicates that the reserved SRAM area may be accessed outside
39+ of the kernel, e.g. by bootloader or userspace
40+- label : the name for the reserved partition, if omitted, the label
41+ is taken from the node name excluding the unit address.
3642
3743 Example:
3844
@@ -48,4 +54,14 @@ sram: sram@5c000000 { · 9 unmodified lines
4854 compatible = "socvendor,smp-sram";
4955 reg = <0x100 0x50>;
5056 };
57+
58+ device-sram@1000 {
59+ reg = <0x1000 0x1000>;
60+ pool;
61+ };
62+
63+ exported@20000 {
64+ reg = <0x20000 0x20000>;
65+ export;
66+ };
5167 };
Documentation/devicetree/bindings/mmc/fsl-esdhc.txt+2−0
@@ -22,6 +22,8 @@ Optional properties: · 21 unmodified lines
2222 - voltage-ranges : two cells are required, first cell specifies minimum
2323 slot voltage (mV), second cell specifies maximum slot voltage (mV).
2424 Several ranges could be specified.
25+ - little-endian : If the host controller is little-endian mode, specify
26+ this property. The default endian mode is big-endian.
2527
2628 Example:
2729
Documentation/devicetree/bindings/mmc/mmc.txt+4−2
@@ -37,6 +37,7 @@ Optional properties: · 36 unmodified lines
3737 - sd-uhs-sdr104: SD UHS SDR104 speed is supported
3838 - sd-uhs-ddr50: SD UHS DDR50 speed is supported
3939 - cap-power-off-card: powering off the card is safe
40+- cap-mmc-hw-reset: eMMC hardware reset is supported
4041 - cap-sdio-irq: enable SDIO IRQ signalling on this interface
4142 - full-pwr-cycle: full power cycle of the card is supported
4243 - mmc-ddr-1_8v: eMMC high-speed DDR mode(1.8V I/O) is supported
@@ -67,7 +68,8 @@ polarity is in effect. · 24 unmodified lines
6768
6869 Optional SDIO properties:
6970 - keep-power-in-suspend: Preserves card power during a suspend/resume cycle
70−- enable-sdio-wakeup: Enables wake up of host system on SDIO IRQ assertion
71+- wakeup-source: Enables wake up of host system on SDIO IRQ assertion
72+ (Legacy property supported: "enable-sdio-wakeup")
7173
7274
7375 MMC power sequences:
@@ -117,7 +119,7 @@ sdhci@ab000000 { · 43 unmodified lines
117119 wp-gpios = <&gpio 70 0>;
118120 max-frequency = <50000000>;
119121 keep-power-in-suspend;
120− enable-sdio-wakeup;
122+ wakeup-source;
121123 mmc-pwrseq = <&sdhci0_pwrseq>
122124 }
123125
Documentation/devicetree/bindings/mmc/mtk-sd.txt+10−1
@@ -17,6 +17,11 @@ Required properties: · 16 unmodified lines
1717 - vmmc-supply: power to the Core
1818 - vqmmc-supply: power to the IO
1919
20+Optional properties:
21+- assigned-clocks: PLL of the source clock
22+- assigned-clock-parents: parent of source clock, used for HS400 mode to get 400Mhz source clock
23+- hs400-ds-delay: HS400 DS delay setting
24+
2025 Examples:
2126 mmc0: mmc@11230000 {
2227 compatible = "mediatek,mt8173-mmc", "mediatek,mt8135-mmc";
@@ -24,9 +29,13 @@ mmc0: mmc@11230000 { · 1 unmodified line
2429 interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_LOW>;
2530 vmmc-supply = <&mt6397_vemc_3v3_reg>;
2631 vqmmc-supply = <&mt6397_vio18_reg>;
27− clocks = <&pericfg CLK_PERI_MSDC30_0>, <&topckgen CLK_TOP_MSDC50_0_H_SEL>;
32+ clocks = <&pericfg CLK_PERI_MSDC30_0>,
33+ <&topckgen CLK_TOP_MSDC50_0_H_SEL>;
2834 clock-names = "source", "hclk";
2935 pinctrl-names = "default", "state_uhs";
3036 pinctrl-0 = <&mmc0_pins_default>;
3137 pinctrl-1 = <&mmc0_pins_uhs>;
38+ assigned-clocks = <&topckgen CLK_TOP_MSDC50_0_SEL>;
39+ assigned-clock-parents = <&topckgen CLK_TOP_MSDCPLL_D2>;
40+ hs400-ds-delay = <0x14015>;
3241 };
Documentation/devicetree/bindings/mmc/renesas,mmcif.txt+3−2
@@ -6,11 +6,12 @@ and the properties used by the MMCIF device. · 5 unmodified lines
66
77 Required properties:
88
9−- compatible: must contain one of the following
9+- compatible: should be "renesas,mmcif-<soctype>", "renesas,sh-mmcif" as a
10+ fallback. Examples with <soctype> are:
1011 - "renesas,mmcif-r8a7740" for the MMCIF found in r8a7740 SoCs
1112 - "renesas,mmcif-r8a7790" for the MMCIF found in r8a7790 SoCs
1213 - "renesas,mmcif-r8a7791" for the MMCIF found in r8a7791 SoCs
13− - "renesas,sh-mmcif" for the generic MMCIF
14+ - "renesas,mmcif-r8a7794" for the MMCIF found in r8a7794 SoCs
1415
1516 - clocks: reference to the functional clock
1617
Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt+13−0
@@ -14,6 +14,19 @@ Required Properties: · 13 unmodified lines
1414 before RK3288
1515 - "rockchip,rk3288-dw-mshc": for Rockchip RK3288
1616
17+Optional Properties:
18+* clocks: from common clock binding: if ciu_drive and ciu_sample are
19+ specified in clock-names, should contain handles to these clocks.
20+
21+* clock-names: Apart from the clock-names described in synopsys-dw-mshc.txt
22+ two more clocks "ciu-drive" and "ciu-sample" are supported. They are used
23+ to control the clock phases, "ciu-sample" is required for tuning high-
24+ speed modes.
25+
26+* rockchip,default-sample-phase: The default phase to set ciu_sample at
27+ probing, low speeds or in case where all phases work at tuning time.
28+ If not specified 0 deg will be used.
29+
1730 Example:
1831
1932 rkdwmmc0@12200000 {
Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt+25−0
@@ -75,6 +75,12 @@ Optional properties: · 74 unmodified lines
7575 * vmmc-supply: The phandle to the regulator to use for vmmc. If this is
7676 specified we'll defer probe until we can find this regulator.
7777
78+* dmas: List of DMA specifiers with the controller specific format as described
79+ in the generic DMA client binding. Refer to dma.txt for details.
80+
81+* dma-names: request names for generic DMA client binding. Must be "rx-tx".
82+ Refer to dma.txt for details.
83+
7884 Aliases:
7985
8086 - All the MSHC controller nodes should be represented in the aliases node using
@@ -95,6 +101,23 @@ board specific portions as listed below. · 14 unmodified lines
95101 #size-cells = <0>;
96102 };
97103
104+[board specific internal DMA resources]
105+
106+ dwmmc0@12200000 {
107+ clock-frequency = <400000000>;
108+ clock-freq-min-max = <400000 200000000>;
109+ num-slots = <1>;
110+ broken-cd;
111+ fifo-depth = <0x80>;
112+ card-detect-delay = <200>;
113+ vmmc-supply = <&buck8>;
114+ bus-width = <8>;
115+ cap-mmc-highspeed;
116+ cap-sd-highspeed;
117+ };
118+
119+[board specific generic DMA request binding]
120+
98121 dwmmc0@12200000 {
99122 clock-frequency = <400000000>;
100123 clock-freq-min-max = <400000 200000000>;
@@ -106,4 +129,6 @@ board specific portions as listed below. · 5 unmodified lines
106129 bus-width = <8>;
107130 cap-mmc-highspeed;
108131 cap-sd-highspeed;
132+ dmas = <&pdma 12>;
133+ dma-names = "rx-tx";
109134 };
Documentation/devicetree/bindings/mtd/fsmc-nand.txt+6−0
@@ -30,6 +30,12 @@ Optional properties: · 29 unmodified lines
3030 command is asserted. Zero means one cycle, 255 means 256
3131 cycles.
3232 - bank: default NAND bank to use (0-3 are valid, 0 is the default).
33+- nand-ecc-mode : see nand.txt
34+- nand-ecc-strength : see nand.txt
35+- nand-ecc-step-size : see nand.txt
36+
37+Can support 1-bit HW ECC (default) or if stronger correction is required,
38+software-based BCH.
3339
3440 Example:
3541
Documentation/devicetree/bindings/mtd/partition.txt+42−29
@@ -4,10 +4,17 @@ Partitions can be represented by sub-nodes of an mtd device. This can be used · 3 unmodified lines
44 on platforms which have strong conventions about which portions of a flash are
55 used for what purposes, but which don't use an on-flash partition table such
66 as RedBoot.
7−NOTE: if the sub-node has a compatible string, then it is not a partition.
87
9−#address-cells & #size-cells must both be present in the mtd device. There are
10−two valid values for both:
8+The partition table should be a subnode of the mtd node and should be named
9+'partitions'. Partitions are defined in subnodes of the partitions node.
10+
11+For backwards compatibility partitions as direct subnodes of the mtd device are
12+supported. This use is discouraged.
13+NOTE: also for backwards compatibility, direct subnodes that have a compatible
14+string are not considered partitions, as they may be used for other bindings.
15+
16+#address-cells & #size-cells must both be present in the partitions subnode of the
17+mtd device. There are two valid values for both:
1118 <1>: for partitions that require a single 32-bit cell to represent their
1219 size/address (aka the value is below 4 GiB)
1320 <2>: for partitions that require two 32-bit cells to represent their
@@ -28,44 +35,50 @@ Examples: · 14 unmodified lines
2835
2936
3037 flash@0 {
31− #address-cells = <1>;
32− #size-cells = <1>;
38+ partitions {
39+ #address-cells = <1>;
40+ #size-cells = <1>;
3341
34− partition@0 {
35− label = "u-boot";
36− reg = <0x0000000 0x100000>;
37− read-only;
38− };
42+ partition@0 {
43+ label = "u-boot";
44+ reg = <0x0000000 0x100000>;
45+ read-only;
46+ };
3947
40− uimage@100000 {
41− reg = <0x0100000 0x200000>;
48+ uimage@100000 {
49+ reg = <0x0100000 0x200000>;
50+ };
4251 };
4352 };
4453
4554 flash@1 {
46− #address-cells = <1>;
47− #size-cells = <2>;
55+ partitions {
56+ #address-cells = <1>;
57+ #size-cells = <2>;
4858
49− /* a 4 GiB partition */
50− partition@0 {
51− label = "filesystem";
52− reg = <0x00000000 0x1 0x00000000>;
59+ /* a 4 GiB partition */
60+ partition@0 {
61+ label = "filesystem";
62+ reg = <0x00000000 0x1 0x00000000>;
63+ };
5364 };
5465 };
5566
5667 flash@2 {
57− #address-cells = <2>;
58− #size-cells = <2>;
68+ partitions {
69+ #address-cells = <2>;
70+ #size-cells = <2>;
5971
60− /* an 8 GiB partition */
61− partition@0 {
62− label = "filesystem #1";
63− reg = <0x0 0x00000000 0x2 0x00000000>;
64− };
72+ /* an 8 GiB partition */
73+ partition@0 {
74+ label = "filesystem #1";
75+ reg = <0x0 0x00000000 0x2 0x00000000>;
76+ };
6577
66− /* a 4 GiB partition */
67− partition@200000000 {
68− label = "filesystem #2";
69− reg = <0x2 0x00000000 0x1 0x00000000>;
78+ /* a 4 GiB partition */
79+ partition@200000000 {
80+ label = "filesystem #2";
81+ reg = <0x2 0x00000000 0x1 0x00000000>;
82+ };
7083 };
7184 };
Documentation/devicetree/bindings/mtd/vf610-nfc.txt+59−0
@@ -0,0 +1,59 @@
1+Freescale's NAND flash controller (NFC)
2+
3+This variant of the Freescale NAND flash controller (NFC) can be found on
4+Vybrid (vf610), MPC5125, MCF54418 and Kinetis K70.
5+
6+Required properties:
7+- compatible: Should be set to "fsl,vf610-nfc".
8+- reg: address range of the NFC.
9+- interrupts: interrupt of the NFC.
10+- #address-cells: shall be set to 1. Encode the nand CS.
11+- #size-cells : shall be set to 0.
12+- assigned-clocks: main clock from the SoC, for Vybrid <&clks VF610_CLK_NFC>;
13+- assigned-clock-rates: The NAND bus timing is derived from this clock
14+ rate and should not exceed maximum timing for any NAND memory chip
15+ in a board stuffing. Typical NAND memory timings derived from this
16+ clock are found in the SoC hardware reference manual. Furthermore,
17+ there might be restrictions on maximum rates when using hardware ECC.
18+
19+- #address-cells, #size-cells : Must be present if the device has sub-nodes
20+ representing partitions.
21+
22+Required children nodes:
23+Children nodes represent the available nand chips. Currently the driver can
24+only handle one NAND chip.
25+
26+Required properties:
27+- compatible: Should be set to "fsl,vf610-nfc-cs".
28+- nand-bus-width: see nand.txt
29+- nand-ecc-mode: see nand.txt
30+
31+Required properties for hardware ECC:
32+- nand-ecc-strength: supported strengths are 24 and 32 bit (see nand.txt)
33+- nand-ecc-step-size: step size equals page size, currently only 2k pages are
34+ supported
35+- nand-on-flash-bbt: see nand.txt
36+
37+Example:
38+
39+ nfc: nand@400e0000 {
40+ compatible = "fsl,vf610-nfc";
41+ #address-cells = <1>;
42+ #size-cells = <0>;
43+ reg = <0x400e0000 0x4000>;
44+ interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
45+ clocks = <&clks VF610_CLK_NFC>;
46+ clock-names = "nfc";
47+ assigned-clocks = <&clks VF610_CLK_NFC>;
48+ assigned-clock-rates = <33000000>;
49+
50+ nand@0 {
51+ compatible = "fsl,vf610-nfc-nandcs";
52+ reg = <0>;
53+ nand-bus-width = <8>;
54+ nand-ecc-mode = "hw";
55+ nand-ecc-strength = <32>;
56+ nand-ecc-step-size = <2048>;
57+ nand-on-flash-bbt;
58+ };
59+ };
Documentation/devicetree/bindings/net/apm-xgene-enet.txt+10−0
@@ -37,6 +37,14 @@ Required properties for ethernet interfaces that have external PHY: · 36 unmodified lines
3737
3838 Optional properties:
3939 - status: Should be "ok" or "disabled" for enabled/disabled. Default is "ok".
40+- tx-delay: Delay value for RGMII bridge TX clock.
41+ Valid values are between 0 to 7, that maps to
42+ 417, 717, 1020, 1321, 1611, 1913, 2215, 2514 ps
43+ Default value is 4, which corresponds to 1611 ps
44+- rx-delay: Delay value for RGMII bridge RX clock.
45+ Valid values are between 0 to 7, that maps to
46+ 273, 589, 899, 1222, 1480, 1806, 2147, 2464 ps
47+ Default value is 2, which corresponds to 899 ps
4048
4149 Example:
4250 menetclk: menetclk {
@@ -72,5 +80,7 @@ Example: · 29 unmodified lines
7280
7381 /* Board-specific peripheral configurations */
7482 &menet {
83+ tx-delay = <4>;
84+ rx-delay = <2>;
7585 status = "ok";
7686 };
Documentation/devicetree/bindings/net/brcm,iproc-mdio.txt+23−0
@@ -0,0 +1,23 @@
1+* Broadcom iProc MDIO bus controller
2+
3+Required properties:
4+- compatible: should be "brcm,iproc-mdio"
5+- reg: address and length of the register set for the MDIO interface
6+- #size-cells: must be 1
7+- #address-cells: must be 0
8+
9+Child nodes of this MDIO bus controller node are standard Ethernet PHY device
10+nodes as described in Documentation/devicetree/bindings/net/phy.txt
11+
12+Example:
13+
14+mdio@18002000 {
15+ compatible = "brcm,iproc-mdio";
16+ reg = <0x18002000 0x8>;
17+ #size-cells = <1>;
18+ #address-cells = <0>;
19+
20+ enet-gphy@0 {
21+ reg = <0>;
22+ };
23+};
Documentation/devicetree/bindings/net/can/sun4i_can.txt+36−0
@@ -0,0 +1,36 @@
1+Allwinner A10/A20 CAN controller Device Tree Bindings
2+-----------------------------------------------------
3+
4+Required properties:
5+- compatible: "allwinner,sun4i-a10-can"
6+- reg: physical base address and size of the Allwinner A10/A20 CAN register map.
7+- interrupts: interrupt specifier for the sole interrupt.
8+- clock: phandle and clock specifier.
9+
10+Example
11+-------
12+
13+SoC common .dtsi file:
14+
15+ can0_pins_a: can0@0 {
16+ allwinner,pins = "PH20","PH21";
17+ allwinner,function = "can";
18+ allwinner,drive = <0>;
19+ allwinner,pull = <0>;
20+ };
21+...
22+ can0: can@01c2bc00 {
23+ compatible = "allwinner,sun4i-a10-can";
24+ reg = <0x01c2bc00 0x400>;
25+ interrupts = <0 26 4>;
26+ clocks = <&apb1_gates 4>;
27+ status = "disabled";
28+ };
29+
30+Board specific .dts file:
31+
32+ can0: can@01c2bc00 {
33+ pinctrl-names = "default";
34+ pinctrl-0 = <&can0_pins_a>;
35+ status = "okay";
36+ };
Documentation/devicetree/bindings/net/cpsw.txt+13−0
@@ -30,6 +30,13 @@ Optional properties: · 29 unmodified lines
3030 - dual_emac : Specifies Switch to act as Dual EMAC
3131 - syscon : Phandle to the system control device node, which is
3232 the control module device of the am33x
33+- mode-gpios : Should be added if one/multiple gpio lines are
34+ required to be driven so that cpsw data lines
35+ can be connected to the phy via selective mux.
36+ For example in dra72x-evm, pcf gpio has to be
37+ driven low so that cpsw slave 0 and phy data
38+ lines are connected via mux.
39+
3340
3441 Slave Properties:
3542 Required properties:
@@ -39,6 +46,12 @@ Required properties: · 3 unmodified lines
3946 Optional properties:
4047 - dual_emac_res_vlan : Specifies VID to be used to segregate the ports
4148 - mac-address : See ethernet.txt file in the same directory
49+- phy-handle : See ethernet.txt file in the same directory
50+
51+Slave sub-nodes:
52+- fixed-link : See fixed-link.txt file in the same directory
53+ Either the properties phy_id and phy-mode,
54+ or the sub-node fixed-link can be specified
4255
4356 Note: "ti,hwmods" field is used to fetch the base address and irq
4457 resources from TI, omap hwmod data base during device registration.
Documentation/devicetree/bindings/net/fsl-tsec-phy.txt+4−0
@@ -57,6 +57,10 @@ Properties: · 56 unmodified lines
5757 "rgmii-id", as all other connection types are detected by hardware.
5858 - fsl,magic-packet : If present, indicates that the hardware supports
5959 waking up via magic packet.
60+ - fsl,wake-on-filer : If present, indicates that the hardware supports
61+ waking up by Filer General Purpose Interrupt (FGPI) asserted on the
62+ Rx int line. This is an advanced power management capability allowing
63+ certain packet types (user) defined by filer rules to wake up the system.
6064 - bd-stash : If present, indicates that the hardware supports stashing
6165 buffer descriptors in the L2.
6266 - rx-stash-len : Denotes the number of bytes of a received buffer to stash
Documentation/devicetree/bindings/net/hisilicon-hip04-net.txt+2−2
@@ -32,13 +32,13 @@ Required properties: · 31 unmodified lines
3232
3333 Required properties:
3434
35−- compatible: should be "hisilicon,hip04-mdio".
35+- compatible: should be "hisilicon,mdio".
3636 - Inherits from MDIO bus node binding [2]
3737 [2] Documentation/devicetree/bindings/net/phy.txt
3838
3939 Example:
4040 mdio {
41− compatible = "hisilicon,hip04-mdio";
41+ compatible = "hisilicon,mdio";
4242 reg = <0x28f1000 0x1000>;
4343 #address-cells = <1>;
4444 #size-cells = <0>;
Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt+49−0
@@ -0,0 +1,49 @@
1+Hisilicon DSA Fabric device controller
2+
3+Required properties:
4+- compatible: should be "hisilicon,hns-dsaf-v1" or "hisilicon,hns-dsaf-v2".
5+ "hisilicon,hns-dsaf-v1" is for hip05.
6+ "hisilicon,hns-dsaf-v2" is for Hi1610 and Hi1612.
7+- dsa-name: dsa fabric name who provide this interface.
8+ should be "dsafX", X is the dsaf id.
9+- mode: dsa fabric mode string. only support one of dsaf modes like these:
10+ "2port-64vf",
11+ "6port-16rss",
12+ "6port-16vf".
13+- interrupt-parent: the interrupt parent of this device.
14+- interrupts: should contain the DSA Fabric and rcb interrupt.
15+- reg: specifies base physical address(es) and size of the device registers.
16+ The first region is external interface control register base and size.
17+ The second region is SerDes base register and size.
18+ The third region is the PPE register base and size.
19+ The fourth region is dsa fabric base register and size.
20+ The fifth region is cpld base register and size, it is not required if do not use cpld.
21+- phy-handle: phy handle of physicl port, 0 if not any phy device. see ethernet.txt [1].
22+- buf-size: rx buffer size, should be 16-1024.
23+- desc-num: number of description in TX and RX queue, should be 512, 1024, 2048 or 4096.
24+
25+[1] Documentation/devicetree/bindings/net/phy.txt
26+
27+Example:
28+
29+dsa: dsa@c7000000 {
30+ compatible = "hisilicon,hns-dsaf-v1";
31+ dsa_name = "dsaf0";
32+ mode = "6port-16rss";
33+ interrupt-parent = <&mbigen_dsa>;
34+ reg = <0x0 0xC0000000 0x0 0x420000
35+ 0x0 0xC2000000 0x0 0x300000
36+ 0x0 0xc5000000 0x0 0x890000
37+ 0x0 0xc7000000 0x0 0x60000>;
38+ phy-handle = <0 0 0 0 &soc0_phy4 &soc0_phy5 0 0>;
39+ interrupts = <131 4>,<132 4>, <133 4>,<134 4>,
40+ <135 4>,<136 4>, <137 4>,<138 4>,
41+ <139 4>,<140 4>, <141 4>,<142 4>,
42+ <143 4>,<144 4>, <145 4>,<146 4>,
43+ <147 4>,<148 4>, <384 1>,<385 1>,
44+ <386 1>,<387 1>, <388 1>,<389 1>,
45+ <390 1>,<391 1>,
46+ buf-size = <4096>;
47+ desc-num = <1024>;
48+ dma-coherent;
49+};
Documentation/devicetree/bindings/net/hisilicon-hns-mdio.txt+22−0
@@ -0,0 +1,22 @@
1+Hisilicon MDIO bus controller
2+
3+Properties:
4+- compatible: "hisilicon,mdio","hisilicon,hns-mdio".
5+- reg: The base address of the MDIO bus controller register bank.
6+- #address-cells: Must be <1>.
7+- #size-cells: Must be <0>. MDIO addresses have no size component.
8+
9+Typically an MDIO bus might have several children.
10+
11+Example:
12+ mdio@803c0000 {
13+ #address-cells = <1>;
14+ #size-cells = <0>;
15+ compatible = "hisilicon,hns-mdio","hisilicon,mdio";
16+ reg = <0x0 0x803c0000 0x0 0x10000>;
17+
18+ ethernet-phy@0 {
19+ ...
20+ reg = <0>;
21+ };
22+ };
Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt+47−0
@@ -0,0 +1,47 @@
1+Hisilicon Network Subsystem NIC controller
2+
3+Required properties:
4+- compatible: "hisilicon,hns-nic-v1" or "hisilicon,hns-nic-v2".
5+ "hisilicon,hns-nic-v1" is for hip05.
6+ "hisilicon,hns-nic-v2" is for Hi1610 and Hi1612.
7+- ae-name: accelerator name who provides this interface,
8+ is simply a name referring to the name of name in the accelerator node.
9+- port-id: is the index of port provided by DSAF (the accelerator). DSAF can
10+ connect to 8 PHYs. Port 0 to 1 are both used for adminstration purpose. They
11+ are called debug ports.
12+
13+ The remaining 6 PHYs are taken according to the mode of DSAF.
14+
15+ In NIC mode of DSAF, all 6 PHYs are taken as ethernet ports to the CPU. The
16+ port-id can be 2 to 7. Here is the diagram:
17+ +-----+---------------+
18+ | CPU |
19+ +-+-+-+---+-+-+-+-+-+-+
20+ | | | | | | | |
21+ debug service
22+ port port
23+ (0,1) (2-7)
24+
25+ In Switch mode of DSAF, all 6 PHYs are taken as physical ports connect to a
26+ LAN Switch while the CPU side assume itself have one single NIC connect to
27+ this switch. In this case, the port-id will be 2 only.
28+ +-----+---------------+
29+ | CPU |
30+ +-+-+-+---+-+-+-+-+-+-+
31+ | | service| port(2)
32+ debug +------------+
33+ port | switch |
34+ (0,1) +-+-+-+-+-+-++
35+ | | | | | |
36+ external port
37+
38+- local-mac-address: mac addr of the ethernet interface
39+
40+Example:
41+
42+ ethernet@0{
43+ compatible = "hisilicon,hns-nic-v1";
44+ ae-name = "dsaf0";
45+ port-id = <0>;
46+ local-mac-address = [a2 14 e4 4b 56 76];
47+ };
Documentation/devicetree/bindings/net/ieee802154/mrf24j40.txt+20−0
@@ -0,0 +1,20 @@
1+* MRF24J40 IEEE 802.15.4 *
2+
3+Required properties:
4+ - compatible: should be "microchip,mrf24j40", "microchip,mrf24j40ma",
5+ or "microchip,mrf24j40mc" depends on your transceiver
6+ board
7+ - spi-max-frequency: maximal bus speed, should be set something under or equal
8+ 10000000
9+ - reg: the chipselect index
10+ - interrupts: the interrupt generated by the device.
11+
12+Example:
13+
14+ mrf24j40ma@0 {
15+ compatible = "microchip,mrf24j40ma";
16+ spi-max-frequency = <8500000>;
17+ reg = <0>;
18+ interrupts = <19 8>;
19+ interrupt-parent = <&gpio3>;
20+ };
Documentation/devicetree/bindings/net/maxim,ds26522.txt+13−0
@@ -0,0 +1,13 @@
1+* Maxim (Dallas) DS26522 Dual T1/E1/J1 Transceiver
2+
3+Required properties:
4+- compatible: Should contain "maxim,ds26522".
5+- reg: SPI CS.
6+- spi-max-frequency: SPI clock.
7+
8+Example:
9+ slic@1 {
10+ compatible = "maxim,ds26522";
11+ reg = <1>;
12+ spi-max-frequency = <2000000>; /* input clock */
13+ };
Documentation/devicetree/bindings/net/nfc/nfcmrvl.txt+59−2
@@ -1,7 +1,10 @@
11 * Marvell International Ltd. NCI NFC Controller
22
33 Required properties:
4−- compatible: Should be "mrvl,nfc-uart".
4+- compatible: Should be:
5+ - "marvell,nfc-uart" or "mrvl,nfc-uart" for UART devices
6+ - "marvell,nfc-i2c" for I2C devices
7+ - "marvell,nfc-spi" for SPI devices
58
69 Optional SoC specific properties:
710 - pinctrl-names: Contains only one value - "default".
@@ -13,13 +16,19 @@ Optional UART-based chip specific properties: · 5 unmodified lines
1316 - flow-control: Specifies that the chip is using RTS/CTS.
1417 - break-control: Specifies that the chip needs specific break management.
1518
19+Optional I2C-based chip specific properties:
20+- i2c-int-falling: Specifies that the chip read event shall be trigged on
21+ falling edge.
22+- i2c-int-rising: Specifies that the chip read event shall be trigged on
23+ rising edge.
24+
1625 Example (for ARM-based BeagleBoard Black with 88W8887 on UART5):
1726
1827 &uart5 {
1928 status = "okay";
2029
2130 nfcmrvluart: nfcmrvluart@5 {
22− compatible = "mrvl,nfc-uart";
31+ compatible = "marvell,nfc-uart";
2332
2433 reset-n-io = <&gpio3 16 0>;
2534
@@ -27,3 +36,51 @@ Example (for ARM-based BeagleBoard Black with 88W8887 on UART5): · 1 unmodified line
2736 flow-control;
2837 }
2938 };
39+
40+
41+Example (for ARM-based BeagleBoard Black with 88W8887 on I2C1):
42+
43+&i2c1 {
44+ status = "okay";
45+ clock-frequency = <400000>;
46+
47+ nfcmrvli2c0: i2c@1 {
48+ compatible = "marvell,nfc-i2c";
49+
50+ reg = <0x8>;
51+
52+ /* I2C INT configuration */
53+ interrupt-parent = <&gpio3>;
54+ interrupts = <21 0>;
55+
56+ /* I2C INT trigger configuration */
57+ i2c-int-rising;
58+
59+ /* Reset IO */
60+ reset-n-io = <&gpio3 19 0>;
61+ };
62+};
63+
64+
65+Example (for ARM-based BeagleBoard Black on SPI0):
66+
67+&spi0 {
68+
69+ mrvlnfcspi0: spi@0 {
70+ compatible = "marvell,nfc-spi";
71+
72+ reg = <0>;
73+
74+ /* SPI Bus configuration */
75+ spi-max-frequency = <3000000>;
76+ spi-cpha;
77+ spi-cpol;
78+
79+ /* SPI INT configuration */
80+ interrupt-parent = <&gpio1>;
81+ interrupts = <17 0>;
82+
83+ /* Reset IO */
84+ reset-n-io = <&gpio3 19 0>;
85+ };
86+};
Documentation/devicetree/bindings/net/nfc/st-nci-i2c.txt+7−0
@@ -11,6 +11,10 @@ Required properties: · 10 unmodified lines
1111 Optional SoC Specific Properties:
1212 - pinctrl-names: Contains only one value - "default".
1313 - pintctrl-0: Specifies the pin control groups used for this controller.
14+- ese-present: Specifies that an ese is physically connected to the nfc
15+controller.
16+- uicc-present: Specifies that the uicc swp signal can be physically
17+connected to the nfc controller.
1418
1519 Example (for ARM-based BeagleBoard xM with ST21NFCB on I2C2):
1620
@@ -29,5 +33,8 @@ Example (for ARM-based BeagleBoard xM with ST21NFCB on I2C2): · 12 unmodified lines
2933 interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
3034
3135 reset-gpios = <&gpio5 29 GPIO_ACTIVE_HIGH>;
36+
37+ ese-present;
38+ uicc-present;
3239 };
3340 };
Documentation/devicetree/bindings/net/nfc/st-nci-spi.txt+8−1
@@ -2,7 +2,7 @@ · 1 unmodified line
22
33 Required properties:
44 - compatible: Should be "st,st21nfcb-spi"
5−- spi-max-frequency: Maximum SPI frequency (<= 10000000).
5+- spi-max-frequency: Maximum SPI frequency (<= 4000000).
66 - interrupt-parent: phandle for the interrupt gpio controller
77 - interrupts: GPIO interrupt to which the chip is connected
88 - reset-gpios: Output GPIO pin used to reset the ST21NFCB
@@ -10,6 +10,10 @@ Required properties: · 1 unmodified line
1010 Optional SoC Specific Properties:
1111 - pinctrl-names: Contains only one value - "default".
1212 - pintctrl-0: Specifies the pin control groups used for this controller.
13+- ese-present: Specifies that an ese is physically connected to the nfc
14+controller.
15+- uicc-present: Specifies that the uicc swp signal can be physically
16+connected to the nfc controller.
1317
1418 Example (for ARM-based BeagleBoard xM with ST21NFCB on SPI4):
1519
@@ -27,5 +31,8 @@ Example (for ARM-based BeagleBoard xM with ST21NFCB on SPI4): · 11 unmodified lines
2731 interrupts = <2 IRQ_TYPE_EDGE_RISING>;
2832
2933 reset-gpios = <&gpio5 29 GPIO_ACTIVE_HIGH>;
34+
35+ ese-present;
36+ uicc-present;
3037 };
3138 };
Documentation/devicetree/bindings/net/renesas,ravb.txt+62−7
@@ -6,8 +6,12 @@ interface contains. · 5 unmodified lines
66 Required properties:
77 - compatible: "renesas,etheravb-r8a7790" if the device is a part of R8A7790 SoC.
88 "renesas,etheravb-r8a7794" if the device is a part of R8A7794 SoC.
9+ "renesas,etheravb-r8a7795" if the device is a part of R8A7795 SoC.
910 - reg: offset and length of (1) the register block and (2) the stream buffer.
10−- interrupts: interrupt specifier for the sole interrupt.
11+- interrupts: A list of interrupt-specifiers, one for each entry in
12+ interrupt-names.
13+ If interrupt-names is not present, an interrupt specifier
14+ for a single muxed interrupt.
1115 - phy-mode: see ethernet.txt file in the same directory.
1216 - phy-handle: see ethernet.txt file in the same directory.
1317 - #address-cells: number of address cells for the MDIO bus, must be equal to 1.
@@ -18,6 +22,12 @@ Required properties: · 4 unmodified lines
1822 Optional properties:
1923 - interrupt-parent: the phandle for the interrupt controller that services
2024 interrupts for this device.
25+- interrupt-names: A list of interrupt names.
26+ For the R8A7795 SoC this property is mandatory;
27+ it should include one entry per channel, named "ch%u",
28+ where %u is the channel number ranging from 0 to 24.
29+ For other SoCs this property is optional; if present
30+ it should contain "mux" for a single muxed interrupt.
2131 - pinctrl-names: pin configuration state name ("default").
2232 - renesas,no-ether-link: boolean, specify when a board does not provide a proper
2333 AVB_LINK signal.
@@ -27,13 +37,46 @@ Optional properties: · 3 unmodified lines
2737 Example:
2838
2939 ethernet@e6800000 {
30− compatible = "renesas,etheravb-r8a7790";
31− reg = <0 0xe6800000 0 0x800>, <0 0xee0e8000 0 0x4000>;
40+ compatible = "renesas,etheravb-r8a7795";
41+ reg = <0 0xe6800000 0 0x800>, <0 0xe6a00000 0 0x10000>;
3242 interrupt-parent = <&gic>;
33− interrupts = <0 163 IRQ_TYPE_LEVEL_HIGH>;
34− clocks = <&mstp8_clks R8A7790_CLK_ETHERAVB>;
35− phy-mode = "rmii";
43+ interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>,
44+ <GIC_SPI 40 IRQ_TYPE_LEVEL_HIGH>,
45+ <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH>,
46+ <GIC_SPI 42 IRQ_TYPE_LEVEL_HIGH>,
47+ <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>,
48+ <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH>,
49+ <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>,
50+ <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>,
51+ <GIC_SPI 47 IRQ_TYPE_LEVEL_HIGH>,
52+ <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>,
53+ <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>,
54+ <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>,
55+ <GIC_SPI 51 IRQ_TYPE_LEVEL_HIGH>,
56+ <GIC_SPI 52 IRQ_TYPE_LEVEL_HIGH>,
57+ <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>,
58+ <GIC_SPI 54 IRQ_TYPE_LEVEL_HIGH>,
59+ <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>,
60+ <GIC_SPI 56 IRQ_TYPE_LEVEL_HIGH>,
61+ <GIC_SPI 57 IRQ_TYPE_LEVEL_HIGH>,
62+ <GIC_SPI 58 IRQ_TYPE_LEVEL_HIGH>,
63+ <GIC_SPI 59 IRQ_TYPE_LEVEL_HIGH>,
64+ <GIC_SPI 60 IRQ_TYPE_LEVEL_HIGH>,
65+ <GIC_SPI 61 IRQ_TYPE_LEVEL_HIGH>,
66+ <GIC_SPI 62 IRQ_TYPE_LEVEL_HIGH>,
67+ <GIC_SPI 63 IRQ_TYPE_LEVEL_HIGH>;
68+ interrupt-names = "ch0", "ch1", "ch2", "ch3",
69+ "ch4", "ch5", "ch6", "ch7",
70+ "ch8", "ch9", "ch10", "ch11",
71+ "ch12", "ch13", "ch14", "ch15",
72+ "ch16", "ch17", "ch18", "ch19",
73+ "ch20", "ch21", "ch22", "ch23",
74+ "ch24";
75+ clocks = <&mstp8_clks R8A7795_CLK_ETHERAVB>;
76+ power-domains = <&cpg_clocks>;
77+ phy-mode = "rgmii-id";
3678 phy-handle = <&phy0>;
79+
3780 pinctrl-0 = <&ether_pins>;
3881 pinctrl-names = "default";
3982 renesas,no-ether-link;
@@ -41,8 +84,20 @@ Example: · 1 unmodified line
4184 #size-cells = <0>;
4285
4386 phy0: ethernet-phy@0 {
87+ rxc-skew-ps = <900>;
88+ rxdv-skew-ps = <0>;
89+ rxd0-skew-ps = <0>;
90+ rxd1-skew-ps = <0>;
91+ rxd2-skew-ps = <0>;
92+ rxd3-skew-ps = <0>;
93+ txc-skew-ps = <900>;
94+ txen-skew-ps = <0>;
95+ txd0-skew-ps = <0>;
96+ txd1-skew-ps = <0>;
97+ txd2-skew-ps = <0>;
98+ txd3-skew-ps = <0>;
4499 reg = <0>;
45100 interrupt-parent = <&gpio2>;
46− interrupts = <15 IRQ_TYPE_LEVEL_LOW>;
101+ interrupts = <11 IRQ_TYPE_LEVEL_LOW>;
47102 };
48103 };
Documentation/devicetree/bindings/net/smsc-lan87xx.txt+24−0
@@ -0,0 +1,24 @@
1+SMSC LAN87xx Ethernet PHY
2+
3+Some boards require special tuning values. Configure them
4+through an Ethernet OF device node.
5+
6+Optional properties:
7+
8+- smsc,disable-energy-detect:
9+ If set, do not enable energy detect mode for the SMSC phy.
10+ default: enable energy detect mode
11+
12+Examples:
13+smsc phy with disabled energy detect mode on an am335x based board.
14+&davinci_mdio {
15+ pinctrl-names = "default", "sleep";
16+ pinctrl-0 = <&davinci_mdio_default>;
17+ pinctrl-1 = <&davinci_mdio_sleep>;
18+ status = "okay";
19+
20+ ethernetphy0: ethernet-phy@0 {
21+ reg = <0>;
22+ smsc,disable-energy-detect;
23+ };
24+};
Documentation/devicetree/bindings/nvmem/imx-ocotp.txt+20−0
@@ -0,0 +1,20 @@
1+Freescale i.MX6 On-Chip OTP Controller (OCOTP) device tree bindings
2+
3+This binding represents the on-chip eFuse OTP controller found on
4+i.MX6Q/D, i.MX6DL/S, i.MX6SL, and i.MX6SX SoCs.
5+
6+Required properties:
7+- compatible: should be one of
8+ "fsl,imx6q-ocotp" (i.MX6Q/D/DL/S),
9+ "fsl,imx6sl-ocotp" (i.MX6SL), or
10+ "fsl,imx6sx-ocotp" (i.MX6SX), followed by "syscon".
11+- reg: Should contain the register base and length.
12+- clocks: Should contain a phandle pointing to the gated peripheral clock.
13+
14+Example:
15+
16+ ocotp: ocotp@021bc000 {
17+ compatible = "fsl,imx6q-ocotp", "syscon";
18+ reg = <0x021bc000 0x4000>;
19+ clocks = <&clks IMX6QDL_CLK_IIM>;
20+ };
Documentation/devicetree/bindings/nvmem/mxs-ocotp.txt+25−0
@@ -0,0 +1,25 @@
1+On-Chip OTP Memory for Freescale i.MX23/i.MX28
2+
3+Required properties :
4+- compatible :
5+ - "fsl,imx23-ocotp" for i.MX23
6+ - "fsl,imx28-ocotp" for i.MX28
7+- #address-cells : Should be 1
8+- #size-cells : Should be 1
9+- reg : Address and length of OTP controller registers
10+- clocks : Should contain a reference to the hbus clock
11+
12+= Data cells =
13+Are child nodes of mxs-ocotp, bindings of which as described in
14+bindings/nvmem/nvmem.txt
15+
16+Example for i.MX28:
17+
18+ ocotp: ocotp@8002c000 {
19+ compatible = "fsl,imx28-ocotp", "fsl,ocotp";
20+ #address-cells = <1>;
21+ #size-cells = <1>;
22+ reg = <0x8002c000 0x2000>;
23+ clocks = <&clks 25>;
24+ status = "okay";
25+ };
Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt+38−0
@@ -0,0 +1,38 @@
1+= Rockchip eFuse device tree bindings =
2+
3+Required properties:
4+- compatible: Should be "rockchip,rockchip-efuse"
5+- reg: Should contain the registers location and exact eFuse size
6+- clocks: Should be the clock id of eFuse
7+- clock-names: Should be "pclk_efuse"
8+
9+= Data cells =
10+Are child nodes of eFuse, bindings of which as described in
11+bindings/nvmem/nvmem.txt
12+
13+Example:
14+
15+ efuse: efuse@ffb40000 {
16+ compatible = "rockchip,rockchip-efuse";
17+ reg = <0xffb40000 0x20>;
18+ #address-cells = <1>;
19+ #size-cells = <1>;
20+ clocks = <&cru PCLK_EFUSE256>;
21+ clock-names = "pclk_efuse";
22+
23+ /* Data cells */
24+ cpu_leakage: cpu_leakage {
25+ reg = <0x17 0x1>;
26+ };
27+ };
28+
29+= Data consumers =
30+Are device nodes which consume nvmem data cells.
31+
32+Example:
33+
34+ cpu_leakage {
35+ ...
36+ nvmem-cells = <&cpu_leakage>;
37+ nvmem-cell-names = "cpu_leakage";
38+ };
Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt+19−0
@@ -0,0 +1,19 @@
1+On-Chip OTP Memory for Freescale Vybrid
2+
3+Required Properties:
4+ compatible:
5+ - "fsl,vf610-ocotp" for VF5xx/VF6xx
6+ #address-cells : Should be 1
7+ #size-cells : Should be 1
8+ reg : Address and length of OTP controller and fuse map registers
9+ clocks : ipg clock we associate with the OCOTP peripheral
10+
11+Example for Vybrid VF5xx/VF6xx:
12+
13+ ocotp: ocotp@400a5000 {
14+ compatible = "fsl,vf610-ocotp";
15+ #address-cells = <1>;
16+ #size-cells = <1>;
17+ reg = <0x400a5000 0xCF0>;
18+ clocks = <&clks VF610_CLK_OCOTP>;
19+ };
Documentation/devicetree/bindings/pci/altera-pcie-msi.txt+28−0
@@ -0,0 +1,28 @@
1+* Altera PCIe MSI controller
2+
3+Required properties:
4+- compatible: should contain "altr,msi-1.0"
5+- reg: specifies the physical base address of the controller and
6+ the length of the memory mapped region.
7+- reg-names: must include the following entries:
8+ "csr": CSR registers
9+ "vector_slave": vectors slave port region
10+- interrupt-parent: interrupt source phandle.
11+- interrupts: specifies the interrupt source of the parent interrupt
12+ controller. The format of the interrupt specifier depends on the
13+ parent interrupt controller.
14+- num-vectors: number of vectors, range 1 to 32.
15+- msi-controller: indicates that this is MSI controller node
16+
17+
18+Example
19+msi0: msi@0xFF200000 {
20+ compatible = "altr,msi-1.0";
21+ reg = <0xFF200000 0x00000010
22+ 0xFF200010 0x00000080>;
23+ reg-names = "csr", "vector_slave";
24+ interrupt-parent = <&hps_0_arm_gic_0>;
25+ interrupts = <0 42 4>;
26+ msi-controller;
27+ num-vectors = <32>;
28+};
Documentation/devicetree/bindings/pci/altera-pcie.txt+49−0
@@ -0,0 +1,49 @@
1+* Altera PCIe controller
2+
3+Required properties:
4+- compatible : should contain "altr,pcie-root-port-1.0"
5+- reg: a list of physical base address and length for TXS and CRA.
6+- reg-names: must include the following entries:
7+ "Txs": TX slave port region
8+ "Cra": Control register access region
9+- interrupt-parent: interrupt source phandle.
10+- interrupts: specifies the interrupt source of the parent interrupt controller.
11+ The format of the interrupt specifier depends on the parent interrupt
12+ controller.
13+- device_type: must be "pci"
14+- #address-cells: set to <3>
15+- #size-cells: set to <2>
16+- #interrupt-cells: set to <1>
17+- ranges: describes the translation of addresses for root ports and standard
18+ PCI regions.
19+- interrupt-map-mask and interrupt-map: standard PCI properties to define the
20+ mapping of the PCIe interface to interrupt numbers.
21+
22+Optional properties:
23+- msi-parent: Link to the hardware entity that serves as the MSI controller for this PCIe
24+ controller.
25+- bus-range: PCI bus numbers covered
26+
27+Example
28+ pcie_0: pcie@0xc00000000 {
29+ compatible = "altr,pcie-root-port-1.0";
30+ reg = <0xc0000000 0x20000000>,
31+ <0xff220000 0x00004000>;
32+ reg-names = "Txs", "Cra";
33+ interrupt-parent = <&hps_0_arm_gic_0>;
34+ interrupts = <0 40 4>;
35+ interrupt-controller;
36+ #interrupt-cells = <1>;
37+ bus-range = <0x0 0xFF>;
38+ device_type = "pci";
39+ msi-parent = <&msi_to_gic_gen_0>;
40+ #address-cells = <3>;
41+ #size-cells = <2>;
42+ interrupt-map-mask = <0 0 0 7>;
43+ interrupt-map = <0 0 0 1 &pcie_0 1>,
44+ <0 0 0 2 &pcie_0 2>,
45+ <0 0 0 3 &pcie_0 3>,
46+ <0 0 0 4 &pcie_0 4>;
47+ ranges = <0x82000000 0x00000000 0x00000000 0xc0000000 0x00000000 0x10000000
48+ 0x82000000 0x00000000 0x10000000 0xd0000000 0x00000000 0x10000000>;
49+ };
Documentation/devicetree/bindings/pci/arm,juno-r1-pcie.txt+10−0
@@ -0,0 +1,10 @@
1+* ARM Juno R1 PCIe interface
2+
3+This PCIe host controller is based on PLDA XpressRICH3-AXI IP
4+and thus inherits all the common properties defined in plda,xpressrich3-axi.txt
5+as well as the base properties defined in host-generic-pci.txt.
6+
7+Required properties:
8+ - compatible: "arm,juno-r1-pcie"
9+ - dma-coherent: The host controller bridges the AXI transactions into PCIe bus
10+ in a manner that makes the DMA operations to appear coherent to the CPUs.
Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt+20−0
@@ -17,6 +17,21 @@ Optional properties: · 16 unmodified lines
1717 - phys: phandle of the PCIe PHY device
1818 - phy-names: must be "pcie-phy"
1919
20+- brcm,pcie-ob: Some iProc SoCs do not have the outbound address mapping done
21+by the ASIC after power on reset. In this case, SW needs to configure it
22+
23+If the brcm,pcie-ob property is present, the following properties become
24+effective:
25+
26+Required:
27+- brcm,pcie-ob-axi-offset: The offset from the AXI address to the internal
28+address used by the iProc PCIe core (not the PCIe address)
29+- brcm,pcie-ob-window-size: The outbound address mapping window size (in MB)
30+
31+Optional:
32+- brcm,pcie-ob-oarr-size: Some iProc SoCs need the OARR size bit to be set to
33+increase the outbound window size
34+
2035 Example:
2136 pcie0: pcie@18012000 {
2237 compatible = "brcm,iproc-pcie";
@@ -38,6 +53,11 @@ Example: · 15 unmodified lines
3853
3954 phys = <&phy 0 5>;
4055 phy-names = "pcie-phy";
56+
57+ brcm,pcie-ob;
58+ brcm,pcie-ob-oarr-size;
59+ brcm,pcie-ob-axi-offset = <0x00000000>;
60+ brcm,pcie-ob-window-size = <256>;
4161 };
4262
4363 pcie1: pcie@18013000 {
Documentation/devicetree/bindings/pci/designware-pcie.txt+7−5
@@ -15,14 +15,16 @@ Required properties: · 14 unmodified lines
1515 to define the mapping of the PCIe interface to interrupt
1616 numbers.
1717 - num-lanes: number of lanes to use
18−- clocks: Must contain an entry for each entry in clock-names.
19− See ../clocks/clock-bindings.txt for details.
20−- clock-names: Must include the following entries:
21− - "pcie"
22− - "pcie_bus"
2318
2419 Optional properties:
20+- num-lanes: number of lanes to use (this property should be specified unless
21+ the link is brought already up in BIOS)
2522 - reset-gpio: gpio pin number of power good signal
2623 - bus-range: PCI bus numbers covered (it is recommended for new devicetrees to
2724 specify this property, to keep backwards compatibility a range of 0x00-0xff
2825 is assumed if not present)
26+- clocks: Must contain an entry for each entry in clock-names.
27+ See ../clocks/clock-bindings.txt for details.
28+- clock-names: Must include the following entries:
29+ - "pcie"
30+ - "pcie_bus"
Documentation/devicetree/bindings/pci/hisilicon-pcie.txt+44−0
@@ -0,0 +1,44 @@
1+HiSilicon PCIe host bridge DT description
2+
3+HiSilicon PCIe host controller is based on Designware PCI core.
4+It shares common functions with PCIe Designware core driver and inherits
5+common properties defined in
6+Documentation/devicetree/bindings/pci/designware-pci.txt.
7+
8+Additional properties are described here:
9+
10+Required properties:
11+- compatible: Should contain "hisilicon,hip05-pcie".
12+- reg: Should contain rc_dbi, config registers location and length.
13+- reg-names: Must include the following entries:
14+ "rc_dbi": controller configuration registers;
15+ "config": PCIe configuration space registers.
16+- msi-parent: Should be its_pcie which is an ITS receiving MSI interrupts.
17+- port-id: Should be 0, 1, 2 or 3.
18+
19+Optional properties:
20+- status: Either "ok" or "disabled".
21+- dma-coherent: Present if DMA operations are coherent.
22+
23+Example:
24+ pcie@0xb0080000 {
25+ compatible = "hisilicon,hip05-pcie", "snps,dw-pcie";
26+ reg = <0 0xb0080000 0 0x10000>, <0x220 0x00000000 0 0x2000>;
27+ reg-names = "rc_dbi", "config";
28+ bus-range = <0 15>;
29+ msi-parent = <&its_pcie>;
30+ #address-cells = <3>;
31+ #size-cells = <2>;
32+ device_type = "pci";
33+ dma-coherent;
34+ ranges = <0x82000000 0 0x00000000 0x220 0x00000000 0 0x10000000>;
35+ num-lanes = <8>;
36+ port-id = <1>;
37+ #interrupts-cells = <1>;
38+ interrupts-map-mask = <0xf800 0 0 7>;
39+ interrupts-map = <0x0 0 0 1 &mbigen_pcie 1 10
40+ 0x0 0 0 2 &mbigen_pcie 2 11
41+ 0x0 0 0 3 &mbigen_pcie 3 12
42+ 0x0 0 0 4 &mbigen_pcie 4 13>;
43+ status = "ok";
44+ };
Documentation/devicetree/bindings/pci/host-generic-pci.txt+3−2
@@ -34,8 +34,9 @@ Properties of the host controller node: · 33 unmodified lines
3434 - #size-cells : Must be 2.
3535
3636 - reg : The Configuration Space base address and size, as accessed
37− from the parent bus.
38−
37+ from the parent bus. The base address corresponds to
38+ the first bus in the "bus-range" property. If no
39+ "bus-range" is specified, this will be bus 0 (the default).
3940
4041 Properties of the /chosen node:
4142
Documentation/devicetree/bindings/pci/layerscape-pci.txt+12−2
@@ -1,10 +1,20 @@
11 Freescale Layerscape PCIe controller
22
3−This PCIe host controller is based on the Synopsis Designware PCIe IP
3+This PCIe host controller is based on the Synopsys DesignWare PCIe IP
44 and thus inherits all the common properties defined in designware-pcie.txt.
55
6+This controller derives its clocks from the Reset Configuration Word (RCW)
7+which is used to describe the PLL settings at the time of chip-reset.
8+
9+Also as per the available Reference Manuals, there is no specific 'version'
10+register available in the Freescale PCIe controller register set,
11+which can allow determining the underlying DesignWare PCIe controller version
12+information.
13+
614 Required properties:
7−- compatible: should contain the platform identifier such as "fsl,ls1021a-pcie"
15+- compatible: should contain the platform identifier such as:
16+ "fsl,ls1021a-pcie", "snps,dw-pcie"
17+ "fsl,ls2080a-pcie", "snps,dw-pcie"
818 - reg: base addresses and lengths of the PCIe controller
919 - interrupts: A list of interrupt outputs of the controller. Must contain an
1020 entry for each entry in the interrupt-names property.
Documentation/devicetree/bindings/pci/pci-msi.txt+220−0
@@ -0,0 +1,220 @@
1+This document describes the generic device tree binding for describing the
2+relationship between PCI devices and MSI controllers.
3+
4+Each PCI device under a root complex is uniquely identified by its Requester ID
5+(AKA RID). A Requester ID is a triplet of a Bus number, Device number, and
6+Function number.
7+
8+For the purpose of this document, when treated as a numeric value, a RID is
9+formatted such that:
10+
11+* Bits [15:8] are the Bus number.
12+* Bits [7:3] are the Device number.
13+* Bits [2:0] are the Function number.
14+* Any other bits required for padding must be zero.
15+
16+MSIs may be distinguished in part through the use of sideband data accompanying
17+writes. In the case of PCI devices, this sideband data may be derived from the
18+Requester ID. A mechanism is required to associate a device with both the MSI
19+controllers it can address, and the sideband data that will be associated with
20+its writes to those controllers.
21+
22+For generic MSI bindings, see
23+Documentation/devicetree/bindings/interrupt-controller/msi.txt.
24+
25+
26+PCI root complex
27+================
28+
29+Optional properties
30+-------------------
31+
32+- msi-map: Maps a Requester ID to an MSI controller and associated
33+ msi-specifier data. The property is an arbitrary number of tuples of
34+ (rid-base,msi-controller,msi-base,length), where:
35+
36+ * rid-base is a single cell describing the first RID matched by the entry.
37+
38+ * msi-controller is a single phandle to an MSI controller
39+
40+ * msi-base is an msi-specifier describing the msi-specifier produced for the
41+ first RID matched by the entry.
42+
43+ * length is a single cell describing how many consecutive RIDs are matched
44+ following the rid-base.
45+
46+ Any RID r in the interval [rid-base, rid-base + length) is associated with
47+ the listed msi-controller, with the msi-specifier (r - rid-base + msi-base).
48+
49+- msi-map-mask: A mask to be applied to each Requester ID prior to being mapped
50+ to an msi-specifier per the msi-map property.
51+
52+- msi-parent: Describes the MSI parent of the root complex itself. Where
53+ the root complex and MSI controller do not pass sideband data with MSI
54+ writes, this property may be used to describe the MSI controller(s)
55+ used by PCI devices under the root complex, if defined as such in the
56+ binding for the root complex.
57+
58+
59+Example (1)
60+===========
61+
62+/ {
63+ #address-cells = <1>;
64+ #size-cells = <1>;
65+
66+ msi: msi-controller@a {
67+ reg = <0xa 0x1>;
68+ compatible = "vendor,some-controller";
69+ msi-controller;
70+ #msi-cells = <1>;
71+ };
72+
73+ pci: pci@f {
74+ reg = <0xf 0x1>;
75+ compatible = "vendor,pcie-root-complex";
76+ device_type = "pci";
77+
78+ /*
79+ * The sideband data provided to the MSI controller is
80+ * the RID, identity-mapped.
81+ */
82+ msi-map = <0x0 &msi_a 0x0 0x10000>,
83+ };
84+};
85+
86+
87+Example (2)
88+===========
89+
90+/ {
91+ #address-cells = <1>;
92+ #size-cells = <1>;
93+
94+ msi: msi-controller@a {
95+ reg = <0xa 0x1>;
96+ compatible = "vendor,some-controller";
97+ msi-controller;
98+ #msi-cells = <1>;
99+ };
100+
101+ pci: pci@f {
102+ reg = <0xf 0x1>;
103+ compatible = "vendor,pcie-root-complex";
104+ device_type = "pci";
105+
106+ /*
107+ * The sideband data provided to the MSI controller is
108+ * the RID, masked to only the device and function bits.
109+ */
110+ msi-map = <0x0 &msi_a 0x0 0x100>,
111+ msi-map-mask = <0xff>
112+ };
113+};
114+
115+
116+Example (3)
117+===========
118+
119+/ {
120+ #address-cells = <1>;
121+ #size-cells = <1>;
122+
123+ msi: msi-controller@a {
124+ reg = <0xa 0x1>;
125+ compatible = "vendor,some-controller";
126+ msi-controller;
127+ #msi-cells = <1>;
128+ };
129+
130+ pci: pci@f {
131+ reg = <0xf 0x1>;
132+ compatible = "vendor,pcie-root-complex";
133+ device_type = "pci";
134+
135+ /*
136+ * The sideband data provided to the MSI controller is
137+ * the RID, but the high bit of the bus number is
138+ * ignored.
139+ */
140+ msi-map = <0x0000 &msi 0x0000 0x8000>,
141+ <0x8000 &msi 0x0000 0x8000>;
142+ };
143+};
144+
145+
146+Example (4)
147+===========
148+
149+/ {
150+ #address-cells = <1>;
151+ #size-cells = <1>;
152+
153+ msi: msi-controller@a {
154+ reg = <0xa 0x1>;
155+ compatible = "vendor,some-controller";
156+ msi-controller;
157+ #msi-cells = <1>;
158+ };
159+
160+ pci: pci@f {
161+ reg = <0xf 0x1>;
162+ compatible = "vendor,pcie-root-complex";
163+ device_type = "pci";
164+
165+ /*
166+ * The sideband data provided to the MSI controller is
167+ * the RID, but the high bit of the bus number is
168+ * negated.
169+ */
170+ msi-map = <0x0000 &msi 0x8000 0x8000>,
171+ <0x8000 &msi 0x0000 0x8000>;
172+ };
173+};
174+
175+
176+Example (5)
177+===========
178+
179+/ {
180+ #address-cells = <1>;
181+ #size-cells = <1>;
182+
183+ msi_a: msi-controller@a {
184+ reg = <0xa 0x1>;
185+ compatible = "vendor,some-controller";
186+ msi-controller;
187+ #msi-cells = <1>;
188+ };
189+
190+ msi_b: msi-controller@b {
191+ reg = <0xb 0x1>;
192+ compatible = "vendor,some-controller";
193+ msi-controller;
194+ #msi-cells = <1>;
195+ };
196+
197+ msi_c: msi-controller@c {
198+ reg = <0xc 0x1>;
199+ compatible = "vendor,some-controller";
200+ msi-controller;
201+ #msi-cells = <1>;
202+ };
203+
204+ pci: pci@c {
205+ reg = <0xf 0x1>;
206+ compatible = "vendor,pcie-root-complex";
207+ device_type = "pci";
208+
209+ /*
210+ * The sideband data provided to MSI controller a is the
211+ * RID, but the high bit of the bus number is negated.
212+ * The sideband data provided to MSI controller b is the
213+ * RID, identity-mapped.
214+ * MSI controller c is not addressable.
215+ */
216+ msi-map = <0x0000 &msi_a 0x8000 0x08000>,
217+ <0x8000 &msi_a 0x0000 0x08000>,
218+ <0x0000 &msi_b 0x0000 0x10000>;
219+ };
220+};
Documentation/devicetree/bindings/pci/pci.txt+2−2
@@ -1,12 +1,12 @@
11 PCI bus bridges have standardized Device Tree bindings:
22
33 PCI Bus Binding to: IEEE Std 1275-1994
4−http://www.openfirmware.org/ofwg/bindings/pci/pci2_1.pdf
4+http://www.firmware.org/1275/bindings/pci/pci2_1.pdf
55
66 And for the interrupt mapping part:
77
88 Open Firmware Recommended Practice: Interrupt Mapping
9−http://www.openfirmware.org/1275/practice/imap/imap0_9d.pdf
9+http://www.firmware.org/1275/practice/imap/imap0_9d.pdf
1010
1111 Additionally to the properties specified in the above standards a host bridge
1212 driver implementation may support the following properties:
Documentation/devicetree/bindings/pci/plda,xpressrich3-axi.txt+12−0
@@ -0,0 +1,12 @@
1+* PLDA XpressRICH3-AXI host controller
2+
3+The PLDA XpressRICH3-AXI host controller can be configured in a manner that
4+makes it compliant with the SBSA[1] standard published by ARM Ltd. For those
5+scenarios, the host-generic-pci.txt bindings apply with the following additions
6+to the compatible property:
7+
8+Required properties:
9+ - compatible: should contain "plda,xpressrich3-axi" to identify the IP used.
10+
11+
12+[1] http://infocenter.arm.com/help/topic/com.arm.doc.den0029a/
Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt+47−0
@@ -0,0 +1,47 @@
1+Broadcom Cygnus PCIe PHY
2+
3+Required properties:
4+- compatible: must be "brcm,cygnus-pcie-phy"
5+- reg: base address and length of the PCIe PHY block
6+- #address-cells: must be 1
7+- #size-cells: must be 0
8+
9+Each PCIe PHY should be represented by a child node
10+
11+Required properties For the child node:
12+- reg: the PHY ID
13+0 - PCIe RC 0
14+1 - PCIe RC 1
15+- #phy-cells: must be 0
16+
17+Example:
18+ pcie_phy: phy@0301d0a0 {
19+ compatible = "brcm,cygnus-pcie-phy";
20+ reg = <0x0301d0a0 0x14>;
21+
22+ pcie0_phy: phy@0 {
23+ reg = <0>;
24+ #phy-cells = <0>;
25+ };
26+
27+ pcie1_phy: phy@1 {
28+ reg = <1>;
29+ #phy-cells = <0>;
30+ };
31+ };
32+
33+ /* users of the PCIe phy */
34+
35+ pcie0: pcie@18012000 {
36+ ...
37+ ...
38+ phys = <&pcie0_phy>;
39+ phy-names = "pcie-phy";
40+ };
41+
42+ pcie1: pcie@18013000 {
43+ ...
44+ ...
45+ phys = <pcie1_phy>;
46+ phy-names = "pcie-phy";
47+ };
Documentation/devicetree/bindings/phy/calxeda-combophy.txtrenamed from Documentation/devicetree/bindings/arm/calxeda/combophy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/phy/keystone-usb-phy.txtrenamed from Documentation/devicetree/bindings/usb/keystone-phy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/phy/mxs-usb-phy.txtrenamed from Documentation/devicetree/bindings/usb/mxs-phy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.txtrenamed from Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/phy/phy-mt65xx-usb.txt+68−0
@@ -0,0 +1,68 @@
1+mt65xx USB3.0 PHY binding
2+--------------------------
3+
4+This binding describes a usb3.0 phy for mt65xx platforms of Medaitek SoC.
5+
6+Required properties (controller (parent) node):
7+ - compatible : should be "mediatek,mt8173-u3phy"
8+ - reg : offset and length of register for phy, exclude port's
9+ register.
10+ - clocks : a list of phandle + clock-specifier pairs, one for each
11+ entry in clock-names
12+ - clock-names : must contain
13+ "u3phya_ref": for reference clock of usb3.0 analog phy.
14+
15+Required nodes : a sub-node is required for each port the controller
16+ provides. Address range information including the usual
17+ 'reg' property is used inside these nodes to describe
18+ the controller's topology.
19+
20+Required properties (port (child) node):
21+- reg : address and length of the register set for the port.
22+- #phy-cells : should be 1 (See second example)
23+ cell after port phandle is phy type from:
24+ - PHY_TYPE_USB2
25+ - PHY_TYPE_USB3
26+
27+Example:
28+
29+u3phy: usb-phy@11290000 {
30+ compatible = "mediatek,mt8173-u3phy";
31+ reg = <0 0x11290000 0 0x800>;
32+ clocks = <&apmixedsys CLK_APMIXED_REF2USB_TX>;
33+ clock-names = "u3phya_ref";
34+ #address-cells = <2>;
35+ #size-cells = <2>;
36+ ranges;
37+ status = "okay";
38+
39+ phy_port0: port@11290800 {
40+ reg = <0 0x11290800 0 0x800>;
41+ #phy-cells = <1>;
42+ status = "okay";
43+ };
44+
45+ phy_port1: port@11291000 {
46+ reg = <0 0x11291000 0 0x800>;
47+ #phy-cells = <1>;
48+ status = "okay";
49+ };
50+};
51+
52+Specifying phy control of devices
53+---------------------------------
54+
55+Device nodes should specify the configuration required in their "phys"
56+property, containing a phandle to the phy port node and a device type;
57+phy-names for each port are optional.
58+
59+Example:
60+
61+#include <dt-bindings/phy/phy.h>
62+
63+usb30: usb@11270000 {
64+ ...
65+ phys = <&phy_port0 PHY_TYPE_USB3>;
66+ phy-names = "usb3-0";
67+ ...
68+};
Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txtrenamed from Documentation/devicetree/bindings/usb/qcom,usb-8x16-phy.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/phy/samsung-phy.txt+3−0
@@ -44,6 +44,9 @@ Required properties: · 43 unmodified lines
4444 - the "ref" clock is used to get the rate of the clock provided to the
4545 PHY module
4646
47+Optional properties:
48+- vbus-supply: power-supply phandle for vbus power source
49+
4750 The first phandle argument in the PHY specifier identifies the PHY, its
4851 meaning is compatible dependent. For the currently supported SoCs (Exynos 4210
4952 and Exynos 4212) it is as follows:
Documentation/devicetree/bindings/pinctrl/allwinner,sunxi-pinctrl.txt+1−0
@@ -17,6 +17,7 @@ Required properties: · 16 unmodified lines
1717 "allwinner,sun8i-a23-pinctrl"
1818 "allwinner,sun8i-a23-r-pinctrl"
1919 "allwinner,sun8i-a33-pinctrl"
20+ "allwinner,sun8i-a83t-pinctrl"
2021
2122 - reg: Should contain the register physical address and length for the
2223 pin controller.
Documentation/devicetree/bindings/pinctrl/atmel,at91-pio4-pinctrl.txt+90−0
@@ -0,0 +1,90 @@
1+* Atmel PIO4 Controller
2+
3+The Atmel PIO4 controller is used to select the function of a pin and to
4+configure it.
5+
6+Required properties:
7+- compatible: "atmel,sama5d2-pinctrl".
8+- reg: base address and length of the PIO controller.
9+- interrupts: interrupt outputs from the controller, one for each bank.
10+- interrupt-controller: mark the device node as an interrupt controller.
11+- #interrupt-cells: should be two.
12+- gpio-controller: mark the device node as a gpio controller.
13+- #gpio-cells: should be two.
14+
15+Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
16+a general description of GPIO and interrupt bindings.
17+
18+Please refer to pinctrl-bindings.txt in this directory for details of the
19+common pinctrl bindings used by client devices.
20+
21+Subnode format
22+Each node (or subnode) will list the pins it needs and how to configured these
23+pins.
24+
25+ node {
26+ pinmux = <PIN_NUMBER_PINMUX>;
27+ GENERIC_PINCONFIG;
28+ };
29+
30+Required properties:
31+- pinmux: integer array. Each integer represents a pin number plus mux and
32+ioset settings. Use the macros from boot/dts/<soc>-pinfunc.h file to get the
33+right representation of the pin.
34+
35+Optional properties:
36+- GENERIC_PINCONFIG: generic pinconfig options to use, bias-disable,
37+bias-pull-down, bias-pull-up, drive-open-drain, input-schmitt-enable,
38+input-debounce, output-low, output-high.
39+
40+Example:
41+
42+#include <sama5d2-pinfunc.h>
43+
44+...
45+{
46+ pioA: pinctrl@fc038000 {
47+ compatible = "atmel,sama5d2-pinctrl";
48+ reg = <0xfc038000 0x600>;
49+ interrupts = <18 IRQ_TYPE_LEVEL_HIGH 7>,
50+ <68 IRQ_TYPE_LEVEL_HIGH 7>,
51+ <69 IRQ_TYPE_LEVEL_HIGH 7>,
52+ <70 IRQ_TYPE_LEVEL_HIGH 7>;
53+ interrupt-controller;
54+ #interrupt-cells = <2>;
55+ gpio-controller;
56+ #gpio-cells = <2>;
57+ clocks = <&pioA_clk>;
58+
59+ pinctrl_i2c0_default: i2c0_default {
60+ pinmux = <PIN_PD21__TWD0>,
61+ <PIN_PD22__TWCK0>;
62+ bias-disable;
63+ };
64+
65+ pinctrl_led_gpio_default: led_gpio_default {
66+ pinmux = <PIN_PB0>,
67+ <PIN_PB5>;
68+ bias-pull-up;
69+ };
70+
71+ pinctrl_sdmmc1_default: sdmmc1_default {
72+ cmd_data {
73+ pinmux = <PIN_PA28__SDMMC1_CMD>,
74+ <PIN_PA18__SDMMC1_DAT0>,
75+ <PIN_PA19__SDMMC1_DAT1>,
76+ <PIN_PA20__SDMMC1_DAT2>,
77+ <PIN_PA21__SDMMC1_DAT3>;
78+ bias-pull-up;
79+ };
80+
81+ ck_cd {
82+ pinmux = <PIN_PA22__SDMMC1_CK>,
83+ <PIN_PA30__SDMMC1_CD>;
84+ bias-disable;
85+ };
86+ };
87+ ...
88+ };
89+};
90+...
Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt+4−1
@@ -20,7 +20,10 @@ Required properties: · 19 unmodified lines
2020 "marvell,berlin2cd-soc-pinctrl",
2121 "marvell,berlin2cd-system-pinctrl",
2222 "marvell,berlin2q-soc-pinctrl",
23− "marvell,berlin2q-system-pinctrl"
23+ "marvell,berlin2q-system-pinctrl",
24+ "marvell,berlin4ct-avio-pinctrl",
25+ "marvell,berlin4ct-soc-pinctrl",
26+ "marvell,berlin4ct-system-pinctrl"
2427
2528 Required subnode-properties:
2629 - groups: a list of strings describing the group names.
Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt+11−5
@@ -3,8 +3,8 @@ Broadcom Cygnus GPIO/PINCONF Controller · 2 unmodified lines
33 Required properties:
44
55 - compatible:
6− Must be "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or
7− "brcm,cygnus-crmu-gpio"
6+ Must be "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio",
7+ "brcm,cygnus-crmu-gpio" or "brcm,iproc-gpio"
88
99 - reg:
1010 Define the base and range of the I/O address space that contains the Cygnus
@@ -26,9 +26,13 @@ Optional properties: · 15 unmodified lines
2626 - interrupt-controller:
2727 Specifies that the node is an interrupt controller
2828
29−- pinmux:
30− Specifies the phandle to the IOMUX device, where pins can be individually
31−muxed to GPIO
29+- gpio-ranges:
30+ Specifies the mapping between gpio controller and pin-controllers pins.
31+ This requires 4 fields in cells defined as -
32+ 1. Phandle of pin-controller.
33+ 2. GPIO base pin offset.
34+ 3 Pin-control base pin offset.
35+ 4. number of gpio pins which are linearly mapped from pin base.
3236
3337 Supported generic PINCONF properties in child nodes:
3438
@@ -78,6 +82,8 @@ Example: · 43 unmodified lines
7882 gpio-controller;
7983 interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
8084 interrupt-controller;
85+ gpio-ranges = <&pinctrl 0 42 1>,
86+ <&pinctrl 1 44 3>;
8187 };
8288
8389 /*
Documentation/devicetree/bindings/pinctrl/fsl,imx7d-pinctrl.txt+62−1
@@ -1,16 +1,42 @@
11 * Freescale i.MX7 Dual IOMUX Controller
22
3+iMX7D supports two iomuxc controllers, fsl,imx7d-iomuxc controller is similar
4+as previous iMX SoC generation and fsl,imx7d-iomuxc-lpsr which provides low
5+power state retention capabilities on gpios that are part of iomuxc-lpsr
6+(GPIO1_IO7..GPIO1_IO0). While iomuxc-lpsr provides its own set of registers for
7+mux and pad control settings, it shares the input select register from main
8+iomuxc controller for daisy chain settings, the fsl,input-sel property extends
9+fsl,imx-pinctrl driver to support iomuxc-lpsr controller.
10+
11+iomuxc_lpsr: iomuxc-lpsr@302c0000 {
12+ compatible = "fsl,imx7d-iomuxc-lpsr";
13+ reg = <0x302c0000 0x10000>;
14+ fsl,input-sel = <&iomuxc>;
15+};
16+
17+iomuxc: iomuxc@30330000 {
18+ compatible = "fsl,imx7d-iomuxc";
19+ reg = <0x30330000 0x10000>;
20+};
21+
22+Pheriparials using pads from iomuxc-lpsr support low state retention power
23+state, under LPSR mode GPIO's state of pads are retain.
24+
325 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
426 and usage.
527
628 Required properties:
7−- compatible: "fsl,imx7d-iomuxc"
29+- compatible: "fsl,imx7d-iomuxc" for main IOMUXC controller, or
30+ "fsl,imx7d-iomuxc-lpsr" for Low Power State Retention IOMUXC controller.
831 - fsl,pins: each entry consists of 6 integers and represents the mux and config
932 setting for one pin. The first 5 integers <mux_reg conf_reg input_reg mux_val
1033 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
1134 imx7d-pinfunc.h under device tree source folder. The last integer CONFIG is
1235 the pad setting value like pull-up on this pin. Please refer to i.MX7 Dual
1336 Reference Manual for detailed CONFIG settings.
37+- fsl,input-sel: required property for iomuxc-lpsr controller, this property is
38+ a phandle for main iomuxc controller which shares the input select register for
39+ daisy chain settings.
1440
1541 CONFIG bits definition:
1642 PAD_CTL_PUS_100K_DOWN (0 << 5)
@@ -25,3 +51,38 @@ PAD_CTL_DSE_X1 (0 << 0) · 8 unmodified lines
2551 PAD_CTL_DSE_X2 (1 << 0)
2652 PAD_CTL_DSE_X3 (2 << 0)
2753 PAD_CTL_DSE_X4 (3 << 0)
54+
55+Examples:
56+While iomuxc-lpsr is intended to be used by dedicated peripherals to take
57+advantages of LPSR power mode, is also possible that an IP to use pads from
58+any of the iomux controllers. For example the I2C1 IP can use SCL pad from
59+iomuxc-lpsr controller and SDA pad from iomuxc controller as:
60+
61+i2c1: i2c@30a20000 {
62+ pinctrl-names = "default";
63+ pinctrl-0 = <&pinctrl_i2c1_1 &pinctrl_i2c1_2>;
64+ status = "okay";
65+};
66+
67+iomuxc-lpsr@302c0000 {
68+ compatible = "fsl,imx7d-iomuxc-lpsr";
69+ reg = <0x302c0000 0x10000>;
70+ fsl,input-sel = <&iomuxc>;
71+
72+ pinctrl_i2c1_1: i2c1grp-1 {
73+ fsl,pins = <
74+ MX7D_PAD_GPIO1_IO04__I2C1_SCL 0x4000007f
75+ >;
76+ };
77+};
78+
79+iomuxc@30330000 {
80+ compatible = "fsl,imx7d-iomuxc";
81+ reg = <0x30330000 0x10000>;
82+
83+ pinctrl_i2c1_2: i2c1grp-2 {
84+ fsl,pins = <
85+ MX7D_PAD_I2C1_SDA__I2C1_SDA 0x4000007f
86+ >;
87+ };
88+};
Documentation/devicetree/bindings/pinctrl/renesas,pfc-pinctrl.txt+1−0
@@ -19,6 +19,7 @@ Required Properties: · 18 unmodified lines
1919 - "renesas,pfc-r8a7791": for R8A7791 (R-Car M2-W) compatible pin-controller.
2020 - "renesas,pfc-r8a7793": for R8A7793 (R-Car M2-N) compatible pin-controller.
2121 - "renesas,pfc-r8a7794": for R8A7794 (R-Car E2) compatible pin-controller.
22+ - "renesas,pfc-r8a7795": for R8A7795 (R-Car H3) compatible pin-controller.
2223 - "renesas,pfc-sh73a0": for SH73A0 (SH-Mobile AG5) compatible pin-controller.
2324
2425 - reg: Base address and length of each memory resource used by the pin
Documentation/devicetree/bindings/power/bq24257.txt+48−5
@@ -1,21 +1,64 @@
1−Binding for TI bq24257 Li-Ion Charger
1+Binding for TI bq24250/bq24251/bq24257 Li-Ion Charger
22
33 Required properties:
44 - compatible: Should contain one of the following:
5+ * "ti,bq24250"
6+ * "ti,bq24251"
57 * "ti,bq24257"
6−- reg: integer, i2c address of the device.
8+- reg: integer, i2c address of the device.
9+- interrupt-parent: Should be the phandle for the interrupt controller. Use in
10+ conjunction with "interrupts".
11+- interrupts: Interrupt mapping for GPIO IRQ (configure for both edges). Use in
12+ conjunction with "interrupt-parent".
713 - ti,battery-regulation-voltage: integer, maximum charging voltage in uV.
8−- ti,charge-current: integer, maximum charging current in uA.
9−- ti,termination-current: integer, charge will be terminated when current in
10− constant-voltage phase drops below this value (in uA).
14+- ti,charge-current: integer, maximum charging current in uA.
15+- ti,termination-current: integer, charge will be terminated when current in
16+ constant-voltage phase drops below this value (in uA).
17+
18+Optional properties:
19+- pg-gpios: GPIO used for connecting the bq2425x device PG (Power Good) pin.
20+ This pin is not available on all devices however it should be used if
21+ possible as this is the recommended way to obtain the charger's input PG
22+ state. If this pin is not specified a software-based approach for PG
23+ detection is used.
24+- ti,current-limit: The maximum current to be drawn from the charger's input
25+ (in uA). If this property is not specified, the input limit current is
26+ set automatically using USB D+/D- signal based charger type detection.
27+ If the hardware does not support the D+/D- based detection, a default
28+ of 500,000 is used (=500mA) instead.
29+- ti,ovp-voltage: Configures the over voltage protection voltage (in uV). If
30+ not specified a default of 6,5000,000 (=6.5V) is used.
31+- ti,in-dpm-voltage: Configures the threshold input voltage for the dynamic
32+ power path management (in uV). If not specified a default of 4,360,000
33+ (=4.36V) is used.
1134
1235 Example:
1336
1437 bq24257 {
1538 compatible = "ti,bq24257";
1639 reg = <0x6a>;
40+ interrupt-parent = <&gpio1>;
41+ interrupts = <16 IRQ_TYPE_EDGE_BOTH>;
42+
43+ pg-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
1744
1845 ti,battery-regulation-voltage = <4200000>;
1946 ti,charge-current = <1000000>;
2047 ti,termination-current = <50000>;
2148 };
49+
50+Example:
51+
52+bq24250 {
53+ compatible = "ti,bq24250";
54+ reg = <0x6a>;
55+ interrupt-parent = <&gpio1>;
56+ interrupts = <16 IRQ_TYPE_EDGE_BOTH>;
57+
58+ ti,battery-regulation-voltage = <4200000>;
59+ ti,charge-current = <500000>;
60+ ti,termination-current = <50000>;
61+ ti,current-limit = <900000>;
62+ ti,ovp-voltage = <9500000>;
63+ ti,in-dpm-voltage = <4440000>;
64+};
Documentation/devicetree/bindings/power/da9150-fg.txt+23−0
@@ -0,0 +1,23 @@
1+Dialog Semiconductor DA9150 Fuel-Gauge Power Supply bindings
2+
3+Required properties:
4+- compatible: "dlg,da9150-fuel-gauge" for DA9150 Fuel-Gauge Power Supply
5+
6+Optional properties:
7+- dlg,update-interval: Interval time (milliseconds) between battery level checks.
8+- dlg,warn-soc-level: Battery discharge level (%) where warning event raised.
9+ [1 - 100]
10+- dlg,crit-soc-level: Battery discharge level (%) where critical event raised.
11+ This value should be lower than the warning level.
12+ [1 - 100]
13+
14+
15+Example:
16+
17+ fuel-gauge {
18+ compatible = "dlg,da9150-fuel-gauge";
19+
20+ dlg,update-interval = <10000>;
21+ dlg,warn-soc-level = /bits/ 8 <15>;
22+ dlg,crit-soc-level = /bits/ 8 <5>;
23+ };
Documentation/devicetree/bindings/power/pd-samsung.txtrenamed from Documentation/devicetree/bindings/arm/exynos/power_domain.txt+2−3
@@ -43,9 +43,8 @@ Example: · 42 unmodified lines
4343 mfc_pd: power-domain@10044060 {
4444 compatible = "samsung,exynos4210-pd";
4545 reg = <0x10044060 0x20>;
46− clocks = <&clock CLK_FIN_PLL>, <&clock CLK_MOUT_SW_ACLK333>,
47− <&clock CLK_MOUT_USER_ACLK333>;
48− clock-names = "oscclk", "pclk0", "clk0";
46+ clocks = <&clock CLK_FIN_PLL>, <&clock CLK_MOUT_USER_ACLK333>;
47+ clock-names = "oscclk", "clk0";
4948 #power-domain-cells = <0>;
5049 };
5150
Documentation/devicetree/bindings/power/wakeup-source.txt+71−0
@@ -0,0 +1,71 @@
1+Specifying wakeup capability for devices
2+============================================
3+
4+Any device nodes
5+----------------
6+Nodes that describe devices which has wakeup capability must contain an
7+"wakeup-source" boolean property.
8+
9+Also, if device is marked as a wakeup source, then all the primary
10+interrupt(s) can be used as wakeup interrupt(s).
11+
12+However if the devices have dedicated interrupt as the wakeup source
13+then they need to specify/identify the same using device specific
14+interrupt name. In such cases only that interrupt can be used as wakeup
15+interrupt.
16+
17+List of legacy properties and respective binding document
18+---------------------------------------------------------
19+
20+1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
21+2. "gpio-key,wakeup" Documentation/devicetree/bindings/input/gpio-keys{,-polled}.txt
22+3. "has-tpo" Documentation/devicetree/bindings/rtc/rtc-opal.txt
23+4. "isil,irq2-can-wakeup-machine" Documentation/devicetree/bindings/rtc/isil,isl12057.txt
24+5. "linux,wakeup" Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
25+ Documentation/devicetree/bindings/mfd/tc3589x.txt
26+ Documentation/devicetree/bindings/input/ads7846.txt
27+6. "linux,keypad-wakeup" Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
28+7. "linux,input-wakeup" Documentation/devicetree/bindings/input/samsung-keypad.txt
29+8. "nvidia,wakeup-source" Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt
30+
31+Examples
32+--------
33+
34+1. With "wakeup" interrupt name
35+
36+ device@10000 {
37+ compatible = "vendor,device-id";
38+ reg = <0x10000 0x1000>;
39+ interrupts = <0 19 4>, <0 21 4>, <0 22 4>;
40+ interrupt-names = "ack", "err", "wakeup";
41+ wakeup-source;
42+ };
43+
44+2. Without "wakeup" interrupt name
45+
46+ embedded-controller {
47+ compatible = "google,cros-ec-i2c";
48+ reg = <0x1e>;
49+ interrupts = <6 0>;
50+ interrupt-parent = <&gpx1>;
51+ pinctrl-names = "default";
52+ pinctrl-0 = <&ec_irq>;
53+ wakeup-source;
54+ };
55+
56+3. Without interrupts
57+
58+ gpio_keys {
59+ compatible = "gpio-keys";
60+ #address-cells = <1>;
61+ #size-cells = <0>;
62+
63+ button@1 {
64+ debounce_interval = <50>;
65+ wakeup-source;
66+ linux,code = <116>;
67+ label = "POWER";
68+ gpios = <&iofpga_gpio0 0 0x4>;
69+ };
70+ [....]
71+ };
Documentation/devicetree/bindings/power_supply/axp20x_usb_power.txt+34−0
@@ -0,0 +1,34 @@
1+AXP20x USB power supply
2+
3+Required Properties:
4+-compatible: "x-powers,axp202-usb-power-supply"
5+
6+This node is a subnode of the axp20x PMIC.
7+
8+Example:
9+
10+axp209: pmic@34 {
11+ compatible = "x-powers,axp209";
12+ reg = <0x34>;
13+ interrupt-parent = <&nmi_intc>;
14+ interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
15+ interrupt-controller;
16+ #interrupt-cells = <1>;
17+
18+ regulators {
19+ x-powers,dcdc-freq = <1500>;
20+
21+ vdd_cpu: dcdc2 {
22+ regulator-always-on;
23+ regulator-min-microvolt = <1000000>;
24+ regulator-max-microvolt = <1450000>;
25+ regulator-name = "vdd-cpu";
26+ };
27+
28+ ...
29+ };
30+
31+ usb-power-supply: usb-power-supply {
32+ compatible = "x-powers,axp202-usb-power-supply";
33+ };
34+};
Documentation/devicetree/bindings/power_supply/qcom_smbb.txt+131−0
@@ -0,0 +1,131 @@
1+Qualcomm Switch-Mode Battery Charger and Boost
2+
3+PROPERTIES
4+- compatible:
5+ Usage: required
6+ Value type: <stringlist>
7+ Description: Must be one of:
8+ - "qcom,pm8941-charger"
9+
10+- reg:
11+ Usage: required
12+ Value type: <prop-encoded-array>
13+ Description: Base address of registers for SMBB block
14+
15+- interrupts:
16+ Usage: required
17+ Value type: <prop-encoded-array>
18+ Description: The format of the specifier is defined by the binding document
19+ describing the node's interrupt parent. Must contain one
20+ specifier for each of the following interrupts, in order:
21+ - charge done
22+ - charge fast mode
23+ - charge trickle mode
24+ - battery temperature ok
25+ - battery present
26+ - charger disconnected
27+ - USB-in valid
28+ - DC-in valid
29+
30+- interrupt-names:
31+ Usage: required
32+ Value type: <stringlist>
33+ Description: Must contain the following list, strictly ordered:
34+ "chg-done",
35+ "chg-fast",
36+ "chg-trkl",
37+ "bat-temp-ok",
38+ "bat-present",
39+ "chg-gone",
40+ "usb-valid",
41+ "dc-valid"
42+
43+- qcom,fast-charge-current-limit:
44+ Usage: optional (default: 1A, or pre-configured value)
45+ Value type: <u32>; uA; range [100mA : 3A]
46+ Description: Maximum charge current; May be clamped to safety limits.
47+
48+- qcom,fast-charge-low-threshold-voltage:
49+ Usage: optional (default: 3.2V, or pre-configured value)
50+ Value type: <u32>; uV; range [2.1V : 3.6V]
51+ Description: Battery voltage limit above which fast charging may operate;
52+ Below this value linear or switch-mode auto-trickle-charging
53+ will operate.
54+
55+- qcom,fast-charge-high-threshold-voltage:
56+ Usage: optional (default: 4.2V, or pre-configured value)
57+ Value type: <u32>; uV; range [3.24V : 5V]
58+ Description: Battery voltage limit below which fast charging may operate;
59+ The fast charger will attempt to charge the battery to this
60+ voltage. May be clamped to safety limits.
61+
62+- qcom,fast-charge-safe-voltage:
63+ Usage: optional (default: 4.2V, or pre-configured value)
64+ Value type: <u32>; uV; range [3.24V : 5V]
65+ Description: Maximum safe battery voltage; May be pre-set by bootloader, in
66+ which case, setting this will harmlessly fail. The property
67+ 'fast-charge-high-watermark' will be clamped by this value.
68+
69+- qcom,fast-charge-safe-current:
70+ Usage: optional (default: 1A, or pre-configured value)
71+ Value type: <u32>; uA; range [100mA : 3A]
72+ Description: Maximum safe battery charge current; May pre-set by bootloader,
73+ in which case, setting this will harmlessly fail. The property
74+ 'qcom,fast-charge-current-limit' will be clamped by this value.
75+
76+- qcom,auto-recharge-threshold-voltage:
77+ Usage: optional (default: 4.1V, or pre-configured value)
78+ Value type: <u32>; uV; range [3.24V : 5V]
79+ Description: Battery voltage limit below which auto-recharge functionality
80+ will restart charging after end-of-charge; The high cutoff
81+ limit for auto-recharge is 5% above this value.
82+
83+- qcom,minimum-input-voltage:
84+ Usage: optional (default: 4.3V, or pre-configured value)
85+ Value type: <u32>; uV; range [4.2V : 9.6V]
86+ Description: Input voltage level above which charging may operate
87+
88+- qcom,dc-current-limit:
89+ Usage: optional (default: 100mA, or pre-configured value)
90+ Value type: <u32>; uA; range [100mA : 2.5A]
91+ Description: Default DC charge current limit
92+
93+- qcom,disable-dc:
94+ Usage: optional (default: false)
95+ Value type: boolean: <u32> or <empty>
96+ Description: Disable DC charger
97+
98+- qcom,jeita-extended-temp-range:
99+ Usage: optional (default: false)
100+ Value type: boolean: <u32> or <empty>
101+ Description: Enable JEITA extended temperature range; This does *not*
102+ adjust the maximum charge voltage or current in the extended
103+ temperature range. It only allows charging when the battery
104+ is in the extended temperature range. Voltage/current
105+ regulation must be done externally to fully comply with
106+ the JEITA safety guidelines if this flag is set.
107+
108+EXAMPLE
109+charger@1000 {
110+ compatible = "qcom,pm8941-charger";
111+ reg = <0x1000 0x700>;
112+ interrupts = <0x0 0x10 7 IRQ_TYPE_EDGE_BOTH>,
113+ <0x0 0x10 5 IRQ_TYPE_EDGE_BOTH>,
114+ <0x0 0x10 4 IRQ_TYPE_EDGE_BOTH>,
115+ <0x0 0x12 1 IRQ_TYPE_EDGE_BOTH>,
116+ <0x0 0x12 0 IRQ_TYPE_EDGE_BOTH>,
117+ <0x0 0x13 2 IRQ_TYPE_EDGE_BOTH>,
118+ <0x0 0x13 1 IRQ_TYPE_EDGE_BOTH>,
119+ <0x0 0x14 1 IRQ_TYPE_EDGE_BOTH>;
120+ interrupt-names = "chg-done",
121+ "chg-fast",
122+ "chg-trkl",
123+ "bat-temp-ok",
124+ "bat-present",
125+ "chg-gone",
126+ "usb-valid",
127+ "dc-valid";
128+
129+ qcom,fast-charge-current-limit = <1000000>;
130+ qcom,dc-charge-current-limit = <1000000>;
131+};
Documentation/devicetree/bindings/power_supply/tps65217_charger.txt+12−0
@@ -0,0 +1,12 @@
1+TPS65217 Charger
2+
3+Required Properties:
4+-compatible: "ti,tps65217-charger"
5+
6+This node is a subnode of the tps65217 PMIC.
7+
8+Example:
9+
10+ tps65217-charger {
11+ compatible = "ti,tps65090-charger";
12+ };
Documentation/devicetree/bindings/powerpc/fsl/mpc512x_lpbfifo.txt+21−0
@@ -0,0 +1,21 @@
1+Freescale MPC512x LocalPlus Bus FIFO (called SCLPC in the Reference Manual)
2+
3+Required properties:
4+- compatible: should be "fsl,mpc512x-lpbfifo";
5+- reg: should contain the offset and length of SCLPC register set;
6+- interrupts: should contain the interrupt specifier for SCLPC; syntax of an
7+ interrupt client node is described in interrupt-controller/interrupts.txt;
8+- dmas: should contain the DMA specifier for SCLPC as described at
9+ dma/dma.txt and dma/mpc512x-dma.txt;
10+- dma-names: should be "rx-tx";
11+
12+Example:
13+
14+ sclpc@10100 {
15+ compatible = "fsl,mpc512x-lpbfifo";
16+ reg = <0x10100 0x50>;
17+ interrupts = <7 0x8>;
18+ dmas = <&dma0 26>;
19+ dma-names = "rx-tx";
20+ };
21+
Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.txt+20−0
@@ -0,0 +1,20 @@
1+Broadcom BCM7038 PWM controller (BCM7xxx Set Top Box PWM controller)
2+
3+Required properties:
4+
5+- compatible: must be "brcm,bcm7038-pwm"
6+- reg: physical base address and length for this controller
7+- #pwm-cells: should be 2. See pwm.txt in this directory for a description
8+ of the cells format
9+- clocks: a phandle to the reference clock for this block which is fed through
10+ its internal variable clock frequency generator
11+
12+
13+Example:
14+
15+ pwm: pwm@f0408000 {
16+ compatible = "brcm,bcm7038-pwm";
17+ reg = <0xf0408000 0x28>;
18+ #pwm-cells = <2>;
19+ clocks = <&upg_fixed>;
20+ };
Documentation/devicetree/bindings/pwm/pwm-berlin.txt+17−0
@@ -0,0 +1,17 @@
1+Berlin PWM controller
2+
3+Required properties:
4+- compatible: should be "marvell,berlin-pwm"
5+- reg: physical base address and length of the controller's registers
6+- clocks: phandle to the input clock
7+- #pwm-cells: should be 3. See pwm.txt in this directory for a description of
8+ the cells format.
9+
10+Example:
11+
12+pwm: pwm@f7f20000 {
13+ compatible = "marvell,berlin-pwm";
14+ reg = <0xf7f20000 0x40>;
15+ clocks = <&chip_clk CLKID_CFG>;
16+ #pwm-cells = <3>;
17+}
Documentation/devicetree/bindings/pwm/pwm-mtk-disp.txt+42−0
@@ -0,0 +1,42 @@
1+MediaTek display PWM controller
2+
3+Required properties:
4+ - compatible: should be "mediatek,<name>-disp-pwm":
5+ - "mediatek,mt8173-disp-pwm": found on mt8173 SoC.
6+ - "mediatek,mt6595-disp-pwm": found on mt6595 SoC.
7+ - reg: physical base address and length of the controller's registers.
8+ - #pwm-cells: must be 2. See pwm.txt in this directory for a description of
9+ the cell format.
10+ - clocks: phandle and clock specifier of the PWM reference clock.
11+ - clock-names: must contain the following:
12+ - "main": clock used to generate PWM signals.
13+ - "mm": sync signals from the modules of mmsys.
14+ - pinctrl-names: Must contain a "default" entry.
15+ - pinctrl-0: One property must exist for each entry in pinctrl-names.
16+ See pinctrl/pinctrl-bindings.txt for details of the property values.
17+
18+Example:
19+ pwm0: pwm@1401e000 {
20+ compatible = "mediatek,mt8173-disp-pwm",
21+ "mediatek,mt6595-disp-pwm";
22+ reg = <0 0x1401e000 0 0x1000>;
23+ #pwm-cells = <2>;
24+ clocks = <&mmsys CLK_MM_DISP_PWM026M>,
25+ <&mmsys CLK_MM_DISP_PWM0MM>;
26+ clock-names = "main", "mm";
27+ pinctrl-names = "default";
28+ pinctrl-0 = <&disp_pwm0_pins>;
29+ };
30+
31+ backlight_lcd: backlight_lcd {
32+ compatible = "pwm-backlight";
33+ pwms = <&pwm0 0 1000000>;
34+ brightness-levels = <
35+ 0 16 32 48 64 80 96 112
36+ 128 144 160 176 192 208 224 240
37+ 255
38+ >;
39+ default-brightness-level = <9>;
40+ power-supply = <&mt6397_vio18_reg>;
41+ enable-gpios = <&pio 95 GPIO_ACTIVE_HIGH>;
42+ };
Documentation/devicetree/bindings/pwm/pwm-sun4i.txt+2−0
@@ -3,6 +3,8 @@ Allwinner sun4i and sun7i SoC PWM controller · 2 unmodified lines
33 Required properties:
44 - compatible: should be one of:
55 - "allwinner,sun4i-a10-pwm"
6+ - "allwinner,sun5i-a10s-pwm"
7+ - "allwinner,sun5i-a13-pwm"
68 - "allwinner,sun7i-a20-pwm"
79 - reg: physical base address and length of the controller's registers
810 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
Documentation/devicetree/bindings/pwm/renesas,pwm-rcar.txt+26−0
@@ -0,0 +1,26 @@
1+* Renesas R-Car PWM Timer Controller
2+
3+Required Properties:
4+- compatible: should be "renesas,pwm-rcar" and one of the following.
5+ - "renesas,pwm-r8a7778": for R-Car M1A
6+ - "renesas,pwm-r8a7779": for R-Car H1
7+ - "renesas,pwm-r8a7790": for R-Car H2
8+ - "renesas,pwm-r8a7791": for R-Car M2-W
9+ - "renesas,pwm-r8a7794": for R-Car E2
10+- reg: base address and length of the registers block for the PWM.
11+- #pwm-cells: should be 2. See pwm.txt in this directory for a description of
12+ the cells format.
13+- clocks: clock phandle and specifier pair.
14+- pinctrl-0: phandle, referring to a default pin configuration node.
15+- pinctrl-names: Set to "default".
16+
17+Example: R8A7790 (R-Car H2) PWM Timer node
18+
19+ pwm0: pwm@e6e30000 {
20+ compatible = "renesas,pwm-r8a7790", "renesas,pwm-rcar";
21+ reg = <0 0xe6e30000 0 0x8>;
22+ #pwm-cells = <2>;
23+ clocks = <&mstp5_clks R8A7790_CLK_PWM>;
24+ pinctrl-0 = <&pwm0_pins>;
25+ pinctrl-names = "default";
26+ };
Documentation/devicetree/bindings/regulator/act8865-regulator.txt+3−0
@@ -8,6 +8,8 @@ Required properties: · 7 unmodified lines
88 Optional properties:
99 - system-power-controller: Telling whether or not this pmic is controlling
1010 the system power. See Documentation/devicetree/bindings/power/power-controller.txt .
11+- active-semi,vsel-high: Indicates the VSEL pin is high.
12+ If this property is missing, assume the VSEL pin is low(0).
1113
1214 Optional input supply properties:
1315 - for act8600:
@@ -49,6 +51,7 @@ Example: · 35 unmodified lines
4951 pmic: act8865@5b {
5052 compatible = "active-semi,act8865";
5153 reg = <0x5b>;
54+ active-semi,vsel-high;
5255 status = "disabled";
5356
5457 regulators {
Documentation/devicetree/bindings/regulator/anatop-regulator.txt+1−0
@@ -13,6 +13,7 @@ Optional properties: · 12 unmodified lines
1313 - anatop-delay-reg-offset: Anatop MFD step time register offset
1414 - anatop-delay-bit-shift: Bit shift for the step time register
1515 - anatop-delay-bit-width: Number of bits used in the step time register
16+- vin-supply: The supply for this regulator
1617
1718 Any property defined as part of the core regulator
1819 binding, defined in regulator.txt, can also be used.
Documentation/devicetree/bindings/regulator/arizona-regulator.txt+17−0
@@ -0,0 +1,17 @@
1+Cirrus Logic Arizona class audio SoCs
2+
3+These devices are audio SoCs with extensive digital capabilities and a range
4+of analogue I/O.
5+
6+This document lists regulator specific bindings, see the primary binding
7+document:
8+ ../mfd/arizona.txt
9+
10+Optional properties:
11+ - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA
12+
13+Optional subnodes:
14+ - ldo1 : Initial data for the LDO1 regulator, as covered in
15+ Documentation/devicetree/bindings/regulator/regulator.txt
16+ - micvdd : Initial data for the MICVDD regulator, as covered in
17+ Documentation/devicetree/bindings/regulator/regulator.txt
Documentation/devicetree/bindings/regulator/max77802.txt+24−1
@@ -8,7 +8,28 @@ regulators that can be controlled over I2C. · 7 unmodified lines
88
99 Following properties should be present in main device node of the MFD chip.
1010
11−Optional node:
11+Optional properties:
12+- inb1-supply: The input supply for BUCK1
13+- inb2-supply: The input supply for BUCK2
14+- inb3-supply: The input supply for BUCK3
15+- inb4-supply: The input supply for BUCK4
16+- inb5-supply: The input supply for BUCK5
17+- inb6-supply: The input supply for BUCK6
18+- inb7-supply: The input supply for BUCK7
19+- inb8-supply: The input supply for BUCK8
20+- inb9-supply: The input supply for BUCK9
21+- inb10-supply: The input supply for BUCK10
22+- inl1-supply: The input supply for LDO8 and LDO15
23+- inl2-supply: The input supply for LDO17, LDO27, LDO30 and LDO35
24+- inl3-supply: The input supply for LDO3, LDO5, LDO6 and LDO7
25+- inl4-supply: The input supply for LDO10, LDO11, LDO13 and LDO14
26+- inl5-supply: The input supply for LDO9 and LDO19
27+- inl6-supply: The input supply for LDO4, LDO21, LDO24 and LDO33
28+- inl7-supply: The input supply for LDO18, LDO20, LDO28 and LDO29
29+- inl9-supply: The input supply for LDO12, LDO23, LDO25, LDO26, LDO32 and LDO34
30+- inl10-supply: The input supply for LDO1 and LDO2
31+
32+Optional nodes:
1233 - regulators : The regulators of max77802 have to be instantiated
1334 under subnode named "regulators" using the following format.
1435
@@ -58,6 +79,8 @@ Example: · 43 unmodified lines
5879 #address-cells = <1>;
5980 #size-cells = <0>;
6081
82+ inb1-supply = <&parent_reg>;
83+
6184 regulators {
6285 ldo1_reg: LDO1 {
6386 regulator-name = "vdd_1v0";
Documentation/devicetree/bindings/regulator/regulator.txt+1−0
@@ -11,6 +11,7 @@ Optional properties: · 10 unmodified lines
1111 - regulator-always-on: boolean, regulator should never be disabled
1212 - regulator-boot-on: bootloader/firmware enabled regulator
1313 - regulator-allow-bypass: allow the regulator to go into bypass mode
14+- regulator-allow-set-load: allow the regulator performance level to be configured
1415 - <name>-supply: phandle to the parent supply/regulator node
1516 - regulator-ramp-delay: ramp delay for regulator(in uV/uS)
1617 For hardware which supports disabling ramp rate, it should be explicitly
Documentation/devicetree/bindings/regulator/tps65023.txt+60−0
@@ -0,0 +1,60 @@
1+TPS65023 family of regulators
2+
3+Required properties:
4+- compatible: Must be one of the following.
5+ "ti,tps65020",
6+ "ti,tps65021",
7+ "ti,tps65023",
8+- reg: I2C slave address
9+- regulators: list of regulators provided by this controller, must be named
10+ after their hardware counterparts: VDCDC[1-3] and LDO[1-2]
11+- regulators: This is the list of child nodes that specify the regulator
12+ initialization data for defined regulators. The definition for each of
13+ these nodes is defined using the standard binding for regulators found at
14+ Documentation/devicetree/bindings/regulator/regulator.txt.
15+
16+Each regulator is defined using the standard binding for regulators.
17+
18+Example:
19+
20+ tps65023@48 {
21+ compatible = "ti,tps65023";
22+ reg = <0x48>;
23+
24+ regulators {
25+ VDCDC1 {
26+ regulator-name = "vdd_mpu";
27+ regulator-always-on;
28+ regulator-min-microvolt = <1200000>;
29+ regulator-max-microvolt = <1200000>;
30+ };
31+
32+ VDCDC2 {
33+ regulator-name = "vdd_core";
34+ regulator-always-on;
35+ regulator-min-microvolt = <3300000>;
36+ regulator-max-microvolt = <3300000>;
37+ };
38+
39+ VDCDC3 {
40+ regulator-name = "vdd_io";
41+ regulator-always-on;
42+ regulator-min-microvolt = <1800000>;
43+ regulator-max-microvolt = <1800000>;
44+ };
45+
46+ LDO1 {
47+ regulator-name = "vdd_usb18";
48+ regulator-always-on;
49+ regulator-min-microvolt = <1800000>;
50+ regulator-max-microvolt = <1800000>;
51+ };
52+
53+ LDO2 {
54+ regulator-name = "vdd_usb33";
55+ regulator-always-on;
56+ regulator-min-microvolt = <3300000>;
57+ regulator-max-microvolt = <3300000>;
58+ };
59+ };
60+ };
Documentation/devicetree/bindings/rng/atmel-trng.txtrenamed from Documentation/devicetree/bindings/hwrng/atmel-trng.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/rng/brcm,iproc-rng200.txtrenamed from Documentation/devicetree/bindings/hwrng/brcm,iproc-rng200.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/rng/omap_rng.txtrenamed from Documentation/devicetree/bindings/hwrng/omap_rng.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/rng/samsung,exynos-rng4.txt+17−0
@@ -0,0 +1,17 @@
1+Exynos Pseudo Random Number Generator
2+
3+Required properties:
4+
5+- compatible : Should be "samsung,exynos4-rng".
6+- reg : Specifies base physical address and size of the registers map.
7+- clocks : Phandle to clock-controller plus clock-specifier pair.
8+- clock-names : "secss" as a clock name.
9+
10+Example:
11+
12+ rng@10830400 {
13+ compatible = "samsung,exynos4-rng";
14+ reg = <0x10830400 0x200>;
15+ clocks = <&clock CLK_SSS>;
16+ clock-names = "secss";
17+ };
Documentation/devicetree/bindings/rng/st,rng.txt+15−0
@@ -0,0 +1,15 @@
1+STMicroelectronics HW Random Number Generator
2+----------------------------------------------
3+
4+Required parameters:
5+compatible : Should be "st,rng"
6+reg : Base address and size of IP's register map.
7+clocks : Phandle to device's clock (See: ../clocks/clock-bindings.txt)
8+
9+Example:
10+
11+rng@fee80000 {
12+ compatible = "st,rng";
13+ reg = <0xfee80000 0x1000>;
14+ clocks = <&clk_sysin>;
15+}
Documentation/devicetree/bindings/rng/st,stm32-rng.txt+21−0
@@ -0,0 +1,21 @@
1+STMicroelectronics STM32 HW RNG
2+===============================
3+
4+The STM32 hardware random number generator is a simple fixed purpose IP and
5+is fully separated from other crypto functions.
6+
7+Required properties:
8+
9+- compatible : Should be "st,stm32-rng"
10+- reg : Should be register base and length as documented in the datasheet
11+- interrupts : The designated IRQ line for the RNG
12+- clocks : The clock needed to enable the RNG
13+
14+Example:
15+
16+ rng: rng@50060800 {
17+ compatible = "st,stm32-rng";
18+ reg = <0x50060800 0x400>;
19+ interrupts = <80>;
20+ clocks = <&rcc 0 38>;
21+ };
Documentation/devicetree/bindings/rng/timeriomem_rng.txtrenamed from Documentation/devicetree/bindings/hwrng/timeriomem_rng.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/rtc/dallas,ds1390.txt+18−0
@@ -0,0 +1,18 @@
1+* Dallas DS1390 SPI Serial Real-Time Clock
2+
3+Required properties:
4+- compatible: Should contain "dallas,ds1390".
5+- reg: SPI address for chip
6+
7+Optional properties:
8+- trickle-resistor-ohms : Selected resistor for trickle charger
9+ Values usable for ds1390 are 250, 2000, 4000
10+ Should be given if trickle charger should be enabled
11+- trickle-diode-disable : Do not use internal trickle charger diode
12+ Should be given if internal trickle charger diode should be disabled
13+Example:
14+ ds1390: rtc@68 {
15+ compatible = "dallas,ds1390";
16+ trickle-resistor-ohms = <250>;
17+ reg = <0>;
18+ };
Documentation/devicetree/bindings/rtc/isil,isl12057.txt+5−5
@@ -5,7 +5,7 @@ consisting of a compatible field, an address and possibly an interrupt · 4 unmodified lines
55 line).
66
77 Nonetheless, it also supports an option boolean property
8−("isil,irq2-can-wakeup-machine") to handle the specific use-case found
8+("wakeup-source") to handle the specific use-case found
99 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104
1010 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
1111 (associated with the alarm supported by the driver) is not connected
@@ -22,9 +22,9 @@ Required properties supported by the device: · 10 unmodified lines
2222
2323 Optional properties:
2424
25− - "isil,irq2-can-wakeup-machine": mark the chip as a wakeup source,
26− independently of the availability of an IRQ line connected to the
27− SoC.
25+ - "wakeup-source": mark the chip as a wakeup source, independently of
26+ the availability of an IRQ line connected to the SoC.
27+ (Legacy property supported: "isil,irq2-can-wakeup-machine")
2828
2929 - "interrupt-parent", "interrupts": for passing the interrupt line
3030 of the SoC connected to IRQ#2 of the RTC chip.
@@ -74,5 +74,5 @@ PMIC, allowing the device to be started based on configured alarm: · 43 unmodified lines
7474 isl12057: isl12057@68 {
7575 compatible = "isil,isl12057";
7676 reg = <0x68>;
77− isil,irq2-can-wakeup-machine;
77+ wakeup-source;
7878 };
Documentation/devicetree/bindings/rtc/pcf8563.txt+25−0
@@ -0,0 +1,25 @@
1+* Philips PCF8563/Epson RTC8564 Real Time Clock
2+
3+Philips PCF8563/Epson RTC8564 Real Time Clock
4+
5+Required properties:
6+see: Documentation/devicetree/bindings/i2c/trivial-devices.txt
7+
8+Optional property:
9+- #clock-cells: Should be 0.
10+- clock-output-names:
11+ overwrite the default clock name "pcf8563-clkout"
12+
13+Example:
14+
15+pcf8563: pcf8563@51 {
16+ compatible = "nxp,pcf8563";
17+ reg = <0x51>;
18+ #clock-cells = <0>;
19+};
20+
21+device {
22+...
23+ clocks = <&pcf8563>;
24+...
25+};
Documentation/devicetree/bindings/rtc/rtc-opal.txt+3−2
@@ -5,12 +5,13 @@ Required properties: · 4 unmodified lines
55 - comapatible: Should be "ibm,opal-rtc"
66
77 Optional properties:
8−- has-tpo: Decides if the wakeup is supported or not.
8+- wakeup-source: Decides if the wakeup is supported or not
9+ (Legacy property supported: "has-tpo")
910
1011 Example:
1112 rtc {
1213 compatible = "ibm,opal-rtc";
13− has-tpo;
14+ wakeup-source;
1415 phandle = <0x10000029>;
1516 linux,phandle = <0x10000029>;
1617 };
Documentation/devicetree/bindings/serial/ingenic,uart.txt+2−1
@@ -1,7 +1,8 @@
11 * Ingenic SoC UART
22
33 Required properties:
4−- compatible : "ingenic,jz4740-uart" or "ingenic,jz4780-uart"
4+- compatible : "ingenic,jz4740-uart", "ingenic,jz4760-uart",
5+ "ingenic,jz4775-uart" or "ingenic,jz4780-uart"
56 - reg : offset and length of the register set for the device.
67 - interrupts : should contain uart interrupt.
78 - clocks : phandles to the module & baud clocks.
Documentation/devicetree/bindings/serial/mrvl,pxa-ssp.txt+0−1
@@ -10,7 +10,6 @@ Required properties: · 9 unmodified lines
1010 mvrl,pxa168-ssp
1111 mrvl,pxa910-ssp
1212 mrvl,ce4100-ssp
13− mrvl,lpss-ssp
1413
1514 - reg: The memory base
1615 - dmas: Two dma phandles, one for rx, one for tx
Documentation/devicetree/bindings/serial/pl011.txt+1−1
@@ -19,7 +19,7 @@ Optional properties: · 18 unmodified lines
1919 must correspond to the PCLK clocking the internal logic
2020 of the block. Just listing one clock (the first one) is
2121 deprecated.
22−- clocks-names:
22+- clock-names:
2323 When present, the first clock listed must be named
2424 "uartclk" and the second clock listed must be named
2525 "apb_pclk"
Documentation/devicetree/bindings/serial/qcom,msm-uartdm.txt+6−0
@@ -26,6 +26,12 @@ Required properties: · 25 unmodified lines
2626 Optional properties:
2727 - dmas: Should contain dma specifiers for transmit and receive channels
2828 - dma-names: Should contain "tx" for transmit and "rx" for receive channels
29+- qcom,tx-crci: Identificator <u32> for Client Rate Control Interface to be
30+ used with TX DMA channel. Required when using DMA for transmission
31+ with UARTDM v1.3 and bellow.
32+- qcom,rx-crci: Identificator <u32> for Client Rate Control Interface to be
33+ used with RX DMA channel. Required when using DMA for reception
34+ with UARTDM v1.3 and bellow.
2935
3036 Note: Aliases may be defined to ensure the correct ordering of the UARTs.
3137 The alias serialN will result in the UART being assigned port N. If any
Documentation/devicetree/bindings/serial/renesas,sci-serial.txt+2−0
@@ -23,6 +23,8 @@ Required properties: · 22 unmodified lines
2323 - "renesas,scifa-r8a7794" for R8A7794 (R-Car E2) SCIFA compatible UART.
2424 - "renesas,scifb-r8a7794" for R8A7794 (R-Car E2) SCIFB compatible UART.
2525 - "renesas,hscif-r8a7794" for R8A7794 (R-Car E2) HSCIF compatible UART.
26+ - "renesas,scif-r8a7795" for R8A7795 (R-Car H3) SCIF compatible UART.
27+ - "renesas,hscif-r8a7795" for R8A7795 (R-Car H3) HSCIF compatible UART.
2628 - "renesas,scifa-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFA compatible UART.
2729 - "renesas,scifb-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFB compatible UART.
2830 - "renesas,scif" for generic SCIF compatible UART.
Documentation/devicetree/bindings/serial/snps-dw-apb-uart.txt+3−0
@@ -15,6 +15,9 @@ The supplying peripheral clock can also be handled, needing a second property · 14 unmodified lines
1515 Required elements: "baudclk", "apb_pclk"
1616
1717 Optional properties:
18+- snps,uart-16550-compatible : reflects the value of UART_16550_COMPATIBLE
19+ configuration parameter. Define this if your UART does not implement the busy
20+ functionality.
1821 - resets : phandle to the parent reset controller.
1922 - reg-shift : quantity to shift the register offsets by. If this property is
2023 not present then the register offsets are not shifted.
Documentation/devicetree/bindings/soc/mediatek/scpsys.txt+6−4
@@ -17,9 +17,9 @@ Required properties: · 16 unmodified lines
1717 - reg: Address range of the SCPSYS unit
1818 - infracfg: must contain a phandle to the infracfg controller
1919 - clock, clock-names: clocks according to the common clock binding.
20− The clocks needed "mm" and "mfg". These are the
21− clocks which hardware needs to be enabled before
22− enabling certain power domains.
20+ The clocks needed "mm", "mfg", "venc" and "venc_lt".
21+ These are the clocks which hardware needs to be enabled
22+ before enabling certain power domains.
2323
2424 Example:
2525
@@ -30,7 +30,9 @@ Example: · 4 unmodified lines
3030 infracfg = <&infracfg>;
3131 clocks = <&clk26m>,
3232 <&topckgen CLK_TOP_MM_SEL>;
33− clock-names = "mfg", "mm";
33+ <&topckgen CLK_TOP_VENC_SEL>,
34+ <&topckgen CLK_TOP_VENC_LT_SEL>;
35+ clock-names = "mfg", "mm", "venc", "venc_lt";
3436 };
3537
3638 Example consumer:
Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt+57−0
@@ -0,0 +1,57 @@
1+Qualcomm Shared Memory Manager binding
2+
3+This binding describes the Qualcomm Shared Memory Manager, used to share data
4+between various subsystems and OSes in Qualcomm platforms.
5+
6+- compatible:
7+ Usage: required
8+ Value type: <stringlist>
9+ Definition: must be:
10+ "qcom,smem"
11+
12+- memory-region:
13+ Usage: required
14+ Value type: <prop-encoded-array>
15+ Definition: handle to memory reservation for main SMEM memory region.
16+
17+- qcom,rpm-msg-ram:
18+ Usage: required
19+ Value type: <prop-encoded-array>
20+ Definition: handle to RPM message memory resource
21+
22+- hwlocks:
23+ Usage: required
24+ Value type: <prop-encoded-array>
25+ Definition: reference to a hwspinlock used to protect allocations from
26+ the shared memory
27+
28+= EXAMPLE
29+The following example shows the SMEM setup for MSM8974, with a main SMEM region
30+at 0xfa00000 and the RPM message ram at 0xfc428000:
31+
32+ reserved-memory {
33+ #address-cells = <1>;
34+ #size-cells = <1>;
35+ ranges;
36+
37+ smem_region: smem@fa00000 {
38+ reg = <0xfa00000 0x200000>;
39+ no-map;
40+ };
41+ };
42+
43+ smem@fa00000 {
44+ compatible = "qcom,smem";
45+
46+ memory-region = <&smem_region>;
47+ qcom,rpm-msg-ram = <&rpm_msg_ram>;
48+
49+ hwlocks = <&tcsr_mutex 3>;
50+ };
51+
52+ soc {
53+ rpm_msg_ram: memory@fc428000 {
54+ compatible = "qcom,rpm-msg-ram";
55+ reg = <0xfc428000 0x4000>;
56+ };
57+ };
Documentation/devicetree/bindings/soc/rockchip/power_domain.txt+46−0
@@ -0,0 +1,46 @@
1+* Rockchip Power Domains
2+
3+Rockchip processors include support for multiple power domains which can be
4+powered up/down by software based on different application scenes to save power.
5+
6+Required properties for power domain controller:
7+- compatible: Should be one of the following.
8+ "rockchip,rk3288-power-controller" - for RK3288 SoCs.
9+- #power-domain-cells: Number of cells in a power-domain specifier.
10+ Should be 1 for multiple PM domains.
11+- #address-cells: Should be 1.
12+- #size-cells: Should be 0.
13+
14+Required properties for power domain sub nodes:
15+- reg: index of the power domain, should use macros in:
16+ "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power domain.
17+- clocks (optional): phandles to clocks which need to be enabled while power domain
18+ switches state.
19+
20+Example:
21+
22+ power: power-controller {
23+ compatible = "rockchip,rk3288-power-controller";
24+ #power-domain-cells = <1>;
25+ #address-cells = <1>;
26+ #size-cells = <0>;
27+
28+ pd_gpu {
29+ reg = <RK3288_PD_GPU>;
30+ clocks = <&cru ACLK_GPU>;
31+ };
32+ };
33+
34+Node of a device using power domains must have a power-domains property,
35+containing a phandle to the power device node and an index specifying which
36+power domain to use.
37+The index should use macros in:
38+ "include/dt-bindings/power/rk3288-power.h" - for rk3288 type power domain.
39+
40+Example of the node using power domain:
41+
42+ node {
43+ /* ... */
44+ power-domains = <&power RK3288_PD_GPU>;
45+ /* ... */
46+ };
Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt+0−1
@@ -221,7 +221,6 @@ qmss: qmss@2a40000 { · 220 unmodified lines
221221 #size-cells = <1>;
222222 ranges;
223223 pdsp0@0x2a10000 {
224− firmware = "keystone/qmss_pdsp_acc48_k2_le_1_0_0_8.fw";
225224 reg = <0x2a10000 0x1000>,
226225 <0x2a0f000 0x100>,
227226 <0x2a0c000 0x3c8>,
Documentation/devicetree/bindings/sound/ak4554.txtrenamed from Documentation/devicetree/bindings/sound/ak4554.c+0−0

File renamed without changes.

Documentation/devicetree/bindings/sound/ak4613.txt+17−0
@@ -0,0 +1,17 @@
1+AK4613 I2C transmitter
2+
3+This device supports I2C mode only.
4+
5+Required properties:
6+
7+- compatible : "asahi-kasei,ak4613"
8+- reg : The chip select number on the I2C bus
9+
10+Example:
11+
12+&i2c {
13+ ak4613: ak4613@0x10 {
14+ compatible = "asahi-kasei,ak4613";
15+ reg = <0x10>;
16+ };
17+};
Documentation/devicetree/bindings/sound/ak4642.txt+21−1
@@ -7,7 +7,14 @@ Required properties: · 6 unmodified lines
77 - compatible : "asahi-kasei,ak4642" or "asahi-kasei,ak4643" or "asahi-kasei,ak4648"
88 - reg : The chip select number on the I2C bus
99
10−Example:
10+Optional properties:
11+
12+ - #clock-cells : common clock binding; shall be set to 0
13+ - clocks : common clock binding; MCKI clock
14+ - clock-frequency : common clock binding; frequency of MCKO
15+ - clock-output-names : common clock binding; MCKO clock name
16+
17+Example 1:
1118
1219 &i2c {
1320 ak4648: ak4648@0x12 {
@@ -15,3 +22,16 @@ Example: · 1 unmodified line
1522 reg = <0x12>;
1623 };
1724 };
25+
26+Example 2:
27+
28+&i2c {
29+ ak4643: codec@12 {
30+ compatible = "asahi-kasei,ak4643";
31+ reg = <0x12>;
32+ #clock-cells = <0>;
33+ clocks = <&audio_clock>;
34+ clock-frequency = <12288000>;
35+ clock-output-names = "ak4643_mcko";
36+ };
37+};
Documentation/devicetree/bindings/sound/atmel-classd.txt+52−0
@@ -0,0 +1,52 @@
1+* Atmel ClassD driver under ALSA SoC architecture
2+
3+Required properties:
4+- compatible
5+ Should be "atmel,sama5d2-classd".
6+- reg
7+ Should contain ClassD registers location and length.
8+- interrupts
9+ Should contain the IRQ line for the ClassD.
10+- dmas
11+ One DMA specifiers as described in atmel-dma.txt and dma.txt files.
12+- dma-names
13+ Must be "tx".
14+- clock-names
15+ Tuple listing input clock names.
16+ Required elements: "pclk", "gclk" and "aclk".
17+- clocks
18+ Please refer to clock-bindings.txt.
19+
20+Optional properties:
21+- pinctrl-names, pinctrl-0
22+ Please refer to pinctrl-bindings.txt.
23+- atmel,model
24+ The user-visible name of this sound complex.
25+ The default value is "CLASSD".
26+- atmel,pwm-type
27+ PWM modulation type, "single" or "diff".
28+ The default value is "single".
29+- atmel,non-overlap-time
30+ Set non-overlapping time, the unit is nanosecond(ns).
31+ There are four values,
32+ <5>, <10>, <15>, <20>, the default value is <10>.
33+ Non-overlapping will be disabled if not specified.
34+
35+Example:
36+classd: classd@fc048000 {
37+ compatible = "atmel,sama5d2-classd";
38+ reg = <0xfc048000 0x100>;
39+ interrupts = <59 IRQ_TYPE_LEVEL_HIGH 7>;
40+ dmas = <&dma0
41+ (AT91_XDMAC_DT_MEM_IF(0) | AT91_XDMAC_DT_PER_IF(1)
42+ | AT91_XDMAC_DT_PERID(47))>;
43+ dma-names = "tx";
44+ clocks = <&classd_clk>, <&classd_gclk>, <&audio_pll_pmc>;
45+ clock-names = "pclk", "gclk", "aclk";
46+
47+ pinctrl-names = "default";
48+ pinctrl-0 = <&pinctrl_classd_default>;
49+ atmel,model = "classd @ SAMA5D2-Xplained";
50+ atmel,pwm-type = "diff";
51+ atmel,non-overlap-time = <10>;
52+};
Documentation/devicetree/bindings/sound/da7213.txt+41−0
@@ -0,0 +1,41 @@
1+Dialog Semiconductor DA7213 Audio Codec bindings
2+
3+======
4+
5+Required properties:
6+- compatible : Should be "dlg,da7213"
7+- reg: Specifies the I2C slave address
8+
9+Optional properties:
10+- clocks : phandle and clock specifier for codec MCLK.
11+- clock-names : Clock name string for 'clocks' attribute, should be "mclk".
12+
13+- dlg,micbias1-lvl : Voltage (mV) for Mic Bias 1
14+ [<1600>, <2200>, <2500>, <3000>]
15+- dlg,micbias2-lvl : Voltage (mV) for Mic Bias 2
16+ [<1600>, <2200>, <2500>, <3000>]
17+- dlg,dmic-data-sel : DMIC channel select based on clock edge.
18+ ["lrise_rfall", "lfall_rrise"]
19+- dlg,dmic-samplephase : When to sample audio from DMIC.
20+ ["on_clkedge", "between_clkedge"]
21+- dlg,dmic-clkrate : DMIC clock frequency (Hz).
22+ [<1500000>, <3000000>]
23+
24+======
25+
26+Example:
27+
28+ codec_i2c: da7213@1a {
29+ compatible = "dlg,da7213";
30+ reg = <0x1a>;
31+
32+ clocks = <&clks 201>;
33+ clock-names = "mclk";
34+
35+ dlg,micbias1-lvl = <2500>;
36+ dlg,micbias2-lvl = <2500>;
37+
38+ dlg,dmic-data-sel = "lrise_rfall";
39+ dlg,dmic-samplephase = "between_clkedge";
40+ dlg,dmic-clkrate = <3000000>;
41+ };
Documentation/devicetree/bindings/sound/da7219.txt+106−0
@@ -0,0 +1,106 @@
1+Dialog Semiconductor DA7219 Audio Codec bindings
2+
3+DA7219 is an audio codec with advanced accessory detect features.
4+
5+======
6+
7+Required properties:
8+- compatible : Should be "dlg,da7219"
9+- reg: Specifies the I2C slave address
10+
11+- interrupt-parent : Specifies the phandle of the interrupt controller to which
12+ the IRQs from DA7219 are delivered to.
13+- interrupts : IRQ line info for DA7219.
14+ (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for
15+ further information relating to interrupt properties)
16+
17+- VDD-supply: VDD power supply for the device
18+- VDDMIC-supply: VDDMIC power supply for the device
19+- VDDIO-supply: VDDIO power supply for the device
20+ (See Documentation/devicetree/bindings/regulator/regulator.txt for further
21+ information relating to regulators)
22+
23+Optional properties:
24+- interrupt-names : Name associated with interrupt line. Should be "wakeup" if
25+ interrupt is to be used to wake system, otherwise "irq" should be used.
26+- wakeup-source: Flag to indicate this device can wake system (suspend/resume).
27+
28+- clocks : phandle and clock specifier for codec MCLK.
29+- clock-names : Clock name string for 'clocks' attribute, should be "mclk".
30+
31+- dlg,ldo-lvl : Required internal LDO voltage (mV) level for digital engine
32+ [<1050>, <1100>, <1200>, <1400>]
33+- dlg,micbias-lvl : Voltage (mV) for Mic Bias
34+ [<1800>, <2000>, <2200>, <2400>, <2600>]
35+- dlg,mic-amp-in-sel : Mic input source type
36+ ["diff", "se_p", "se_n"]
37+
38+======
39+
40+Child node - 'da7219_aad':
41+
42+Optional properties:
43+- dlg,micbias-pulse-lvl : Mic bias higher voltage pulse level (mV).
44+ [<2800>, <2900>]
45+- dlg,micbias-pulse-time : Mic bias higher voltage pulse duration (ms)
46+- dlg,btn-cfg : Periodic button press measurements for 4-pole jack (ms)
47+ [<2>, <5>, <10>, <50>, <100>, <200>, <500>]
48+- dlg,mic-det-thr : Impedance threshold for mic detection measurement (Ohms)
49+ [<200>, <500>, <750>, <1000>]
50+- dlg,jack-ins-deb : Debounce time for jack insertion (ms)
51+ [<5>, <10>, <20>, <50>, <100>, <200>, <500>, <1000>]
52+- dlg,jack-det-rate: Jack type detection latency (3/4 pole)
53+ ["32ms_64ms", "64ms_128ms", "128ms_256ms", "256ms_512ms"]
54+- dlg,jack-rem-deb : Debounce time for jack removal (ms)
55+ [<1>, <5>, <10>, <20>]
56+- dlg,a-d-btn-thr : Impedance threshold between buttons A and D
57+ [0x0 - 0xFF]
58+- dlg,d-b-btn-thr : Impedance threshold between buttons D and B
59+ [0x0 - 0xFF]
60+- dlg,b-c-btn-thr : Impedance threshold between buttons B and C
61+ [0x0 - 0xFF]
62+- dlg,c-mic-btn-thr : Impedance threshold between button C and Mic
63+ [0x0 - 0xFF]
64+- dlg,btn-avg : Number of 8-bit readings for averaged button measurement
65+ [<1>, <2>, <4>, <8>]
66+- dlg,adc-1bit-rpt : Repeat count for 1-bit button measurement
67+ [<1>, <2>, <4>, <8>]
68+
69+======
70+
71+Example:
72+
73+ codec: da7219@1a {
74+ compatible = "dlg,da7219";
75+ reg = <0x1a>;
76+
77+ interrupt-parent = <&gpio6>;
78+ interrupts = <11 IRQ_TYPE_LEVEL_HIGH>;
79+
80+ VDD-supply = <&reg_audio>;
81+ VDDMIC-supply = <&reg_audio>;
82+ VDDIO-supply = <&reg_audio>;
83+
84+ clocks = <&clks 201>;
85+ clock-names = "mclk";
86+
87+ dlg,ldo-lvl = <1200>;
88+ dlg,micbias-lvl = <2600>;
89+ dlg,mic-amp-in-sel = "diff";
90+
91+ da7219_aad {
92+ dlg,btn-cfg = <50>;
93+ dlg,mic-det-thr = <500>;
94+ dlg,jack-ins-deb = <20>;
95+ dlg,jack-det-rate = "32ms_64ms";
96+ dlg,jack-rem-deb = <1>;
97+
98+ dlg,a-d-btn-thr = <0xa>;
99+ dlg,d-b-btn-thr = <0x16>;
100+ dlg,b-c-btn-thr = <0x21>;
101+ dlg,c-mic-btn-thr = <0x3E>;
102+
103+ dlg,btn-avg = <4>;
104+ dlg,adc-1bit-rpt = <1>;
105+ };
106+ };
Documentation/devicetree/bindings/sound/fsl-asoc-card.txt+6−4
@@ -13,13 +13,15 @@ So having this generic sound card allows all Freescale SoC users to benefit · 12 unmodified lines
1313 from the simplification of a new card support and the capability of the wide
1414 sample rates support through ASRC.
1515
16−Note: The card is initially designed for those sound cards who use I2S and
17− PCM DAI formats. However, it'll be also possible to support those non
18− I2S/PCM type sound cards, such as S/PDIF audio and HDMI audio, as long
19− as the driver has been properly upgraded.
16+Note: The card is initially designed for those sound cards who use AC'97, I2S
17+ and PCM DAI formats. However, it'll be also possible to support those non
18+ AC'97/I2S/PCM type sound cards, such as S/PDIF audio and HDMI audio, as
19+ long as the driver has been properly upgraded.
2020
2121
2222 The compatible list for this generic sound card currently:
23+ "fsl,imx-audio-ac97"
24+
2325 "fsl,imx-audio-cs42888"
2426
2527 "fsl,imx-audio-wm8962"
Documentation/devicetree/bindings/sound/nau8825.txt+102−0
@@ -0,0 +1,102 @@
1+Nuvoton NAU8825 audio codec
2+
3+This device supports I2C only.
4+
5+Required properties:
6+ - compatible : Must be "nuvoton,nau8825"
7+
8+ - reg : the I2C address of the device. This is either 0x1a (CSB=0) or 0x1b (CSB=1).
9+
10+Optional properties:
11+ - nuvoton,jkdet-enable: Enable jack detection via JKDET pin.
12+ - nuvoton,jkdet-pull-enable: Enable JKDET pin pull. If set - pin pull enabled,
13+ otherwise pin in high impedance state.
14+ - nuvoton,jkdet-pull-up: Pull-up JKDET pin. If set then JKDET pin is pull up, otherwise pull down.
15+ - nuvoton,jkdet-polarity: JKDET pin polarity. 0 - active high, 1 - active low.
16+
17+ - nuvoton,vref-impedance: VREF Impedance selection
18+ 0 - Open
19+ 1 - 25 kOhm
20+ 2 - 125 kOhm
21+ 3 - 2.5 kOhm
22+
23+ - nuvoton,micbias-voltage: Micbias voltage level.
24+ 0 - VDDA
25+ 1 - VDDA
26+ 2 - VDDA * 1.1
27+ 3 - VDDA * 1.2
28+ 4 - VDDA * 1.3
29+ 5 - VDDA * 1.4
30+ 6 - VDDA * 1.53
31+ 7 - VDDA * 1.53
32+
33+ - nuvoton,sar-threshold-num: Number of buttons supported
34+ - nuvoton,sar-threshold: Impedance threshold for each button. Array that contains up to 8 buttons configuration. SAR value is calculated as
35+ SAR = 255 * MICBIAS / SAR_VOLTAGE * R / (2000 + R)
36+ where MICBIAS is configured by 'nuvoton,micbias-voltage', SAR_VOLTAGE is configured by 'nuvoton,sar-voltage', R - button impedance.
37+ Refer datasheet section 10.2 for more information about threshold calculation.
38+
39+ - nuvoton,sar-hysteresis: Button impedance measurement hysteresis.
40+
41+ - nuvoton,sar-voltage: Reference voltage for button impedance measurement.
42+ 0 - VDDA
43+ 1 - VDDA
44+ 2 - VDDA * 1.1
45+ 3 - VDDA * 1.2
46+ 4 - VDDA * 1.3
47+ 5 - VDDA * 1.4
48+ 6 - VDDA * 1.53
49+ 7 - VDDA * 1.53
50+
51+ - nuvoton,sar-compare-time: SAR compare time
52+ 0 - 500 ns
53+ 1 - 1 us
54+ 2 - 2 us
55+ 3 - 4 us
56+
57+ - nuvoton,sar-sampling-time: SAR sampling time
58+ 0 - 2 us
59+ 1 - 4 us
60+ 2 - 8 us
61+ 3 - 16 us
62+
63+ - nuvoton,short-key-debounce: Button short key press debounce time.
64+ 0 - 30 ms
65+ 1 - 50 ms
66+ 2 - 100 ms
67+ 3 - 30 ms
68+
69+ - nuvoton,jack-insert-debounce: number from 0 to 7 that sets debounce time to 2^(n+2) ms
70+ - nuvoton,jack-eject-debounce: number from 0 to 7 that sets debounce time to 2^(n+2) ms
71+
72+ - clocks: list of phandle and clock specifier pairs according to common clock bindings for the
73+ clocks described in clock-names
74+ - clock-names: should include "mclk" for the MCLK master clock
75+
76+Example:
77+
78+ headset: nau8825@1a {
79+ compatible = "nuvoton,nau8825";
80+ reg = <0x1a>;
81+ interrupt-parent = <&gpio>;
82+ interrupts = <TEGRA_GPIO(E, 6) IRQ_TYPE_LEVEL_LOW>;
83+ nuvoton,jkdet-enable;
84+ nuvoton,jkdet-pull-enable;
85+ nuvoton,jkdet-pull-up;
86+ nuvoton,jkdet-polarity = <GPIO_ACTIVE_LOW>;
87+ nuvoton,vref-impedance = <2>;
88+ nuvoton,micbias-voltage = <6>;
89+ // Setup 4 buttons impedance according to Android specification
90+ nuvoton,sar-threshold-num = <4>;
91+ nuvoton,sar-threshold = <0xc 0x1e 0x38 0x60>;
92+ nuvoton,sar-hysteresis = <1>;
93+ nuvoton,sar-voltage = <0>;
94+ nuvoton,sar-compare-time = <0>;
95+ nuvoton,sar-sampling-time = <0>;
96+ nuvoton,short-key-debounce = <2>;
97+ nuvoton,jack-insert-debounce = <7>;
98+ nuvoton,jack-eject-debounce = <7>;
99+
100+ clock-names = "mclk";
101+ clocks = <&tegra_car TEGRA210_CLK_CLK_OUT_2>;
102+ };
Documentation/devicetree/bindings/sound/renesas,rsnd.txt+7−0
@@ -4,10 +4,12 @@ Required properties: · 3 unmodified lines
44 - compatible : "renesas,rcar_sound-<soctype>", fallbacks
55 "renesas,rcar_sound-gen1" if generation1, and
66 "renesas,rcar_sound-gen2" if generation2
7+ "renesas,rcar_sound-gen3" if generation3
78 Examples with soctypes are:
89 - "renesas,rcar_sound-r8a7778" (R-Car M1A)
910 - "renesas,rcar_sound-r8a7790" (R-Car H2)
1011 - "renesas,rcar_sound-r8a7791" (R-Car M2-W)
12+ - "renesas,rcar_sound-r8a7795" (R-Car H3)
1113 - reg : Should contain the register physical address.
1214 required register is
1315 SRU/ADG/SSI if generation1
@@ -30,6 +32,11 @@ Required properties: · 16 unmodified lines
3032 - rcar_sound,dai : DAI contents.
3133 The number of DAI subnode should be same as HW.
3234 see below for detail.
35+- #sound-dai-cells : it must be 0 if your system is using single DAI
36+ it must be 1 if your system is using multi DAI
37+- #clock-cells : it must be 0 if your system has audio_clkout
38+ it must be 1 if your system has audio_clkout0/1/2/3
39+- clock-frequency : for all audio_clkout0/1/2/3
3340
3441 SSI subnode properties:
3542 - interrupts : Should contain SSI interrupt for PIO transfer
Documentation/devicetree/bindings/sound/rockchip-i2s.txt+2−4
@@ -12,8 +12,6 @@ Required properties: · 11 unmodified lines
1212 - reg: physical base address of the controller and length of memory mapped
1313 region.
1414 - interrupts: should contain the I2S interrupt.
15−- #address-cells: should be 1.
16−- #size-cells: should be 0.
1715 - dmas: DMA specifiers for tx and rx dma. See the DMA client binding,
1816 Documentation/devicetree/bindings/dma/dma.txt
1917 - dma-names: should include "tx" and "rx".
@@ -21,6 +19,7 @@ Required properties: · 1 unmodified line
2119 - clock-names: should contain followings:
2220 - "i2s_hclk": clock for I2S BUS
2321 - "i2s_clk" : clock for I2S controller
22+- rockchip,capture-channels: max capture channels, if not set, 2 channels default.
2423
2524 Example for rk3288 I2S controller:
2625
@@ -28,10 +27,9 @@ i2s@ff890000 { · 1 unmodified line
2827 compatible = "rockchip,rk3288-i2s", "rockchip,rk3066-i2s";
2928 reg = <0xff890000 0x10000>;
3029 interrupts = <GIC_SPI 85 IRQ_TYPE_LEVEL_HIGH>;
31− #address-cells = <1>;
32− #size-cells = <0>;
3330 dmas = <&pdma1 0>, <&pdma1 1>;
3431 dma-names = "tx", "rx";
3532 clock-names = "i2s_hclk", "i2s_clk";
3633 clocks = <&cru HCLK_I2S0>, <&cru SCLK_I2S0>;
34+ rockchip,capture-channels = <2>;
3735 };
Documentation/devicetree/bindings/sound/rockchip-spdif.txt+40−0
@@ -0,0 +1,40 @@
1+* Rockchip SPDIF transceiver
2+
3+The S/PDIF audio block is a stereo transceiver that allows the
4+processor to receive and transmit digital audio via an coaxial cable or
5+a fibre cable.
6+
7+Required properties:
8+
9+- compatible: should be one of the following:
10+ - "rockchip,rk3288-spdif", "rockchip,rk3188-spdif" or
11+ "rockchip,rk3066-spdif"
12+- reg: physical base address of the controller and length of memory mapped
13+ region.
14+- interrupts: should contain the SPDIF interrupt.
15+- dmas: DMA specifiers for tx dma. See the DMA client binding,
16+ Documentation/devicetree/bindings/dma/dma.txt
17+- dma-names: should be "tx"
18+- clocks: a list of phandle + clock-specifier pairs, one for each entry
19+ in clock-names.
20+- clock-names: should contain following:
21+ - "hclk": clock for SPDIF controller
22+ - "mclk" : clock for SPDIF bus
23+
24+Required properties on RK3288:
25+ - rockchip,grf: the phandle of the syscon node for the general register
26+ file (GRF)
27+
28+Example for the rk3188 SPDIF controller:
29+
30+spdif: spdif@0x1011e000 {
31+ compatible = "rockchip,rk3188-spdif", "rockchip,rk3066-spdif";
32+ reg = <0x1011e000 0x2000>;
33+ interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
34+ dmas = <&dmac1_s 8>;
35+ dma-names = "tx";
36+ clock-names = "hclk", "mclk";
37+ clocks = <&cru HCLK_SPDIF>, <&cru SCLK_SPDIF>;
38+ status = "disabled";
39+ #sound-dai-cells = <0>;
40+};
Documentation/devicetree/bindings/sound/rt5640.txt+6−3
@@ -14,7 +14,8 @@ Optional properties: · 13 unmodified lines
1414
1515 - realtek,in1-differential
1616 - realtek,in2-differential
17− Boolean. Indicate MIC1/2 input are differential, rather than single-ended.
17+- realtek,in3-differential
18+ Boolean. Indicate MIC1/2/3 input are differential, rather than single-ended.
1819
1920 - realtek,ldo1-en-gpios : The GPIO that controls the CODEC's LDO1_EN pin.
2021
@@ -24,9 +25,11 @@ Pins on the device (for linking into audio routes) for RT5639/RT5640: · 3 unmodified lines
2425 * DMIC2
2526 * MICBIAS1
2627 * IN1P
27− * IN1R
28+ * IN1N
2829 * IN2P
29− * IN2R
30+ * IN2N
31+ * IN3P
32+ * IN3N
3033 * HPOL
3134 * HPOR
3235 * LOUTL
Documentation/devicetree/bindings/sound/sun4i-codec.txt+27−0
@@ -0,0 +1,27 @@
1+* Allwinner A10 Codec
2+
3+Required properties:
4+- compatible: must be either "allwinner,sun4i-a10-codec" or
5+ "allwinner,sun7i-a20-codec"
6+- reg: must contain the registers location and length
7+- interrupts: must contain the codec interrupt
8+- dmas: DMA channels for tx and rx dma. See the DMA client binding,
9+ Documentation/devicetree/bindings/dma/dma.txt
10+- dma-names: should include "tx" and "rx".
11+- clocks: a list of phandle + clock-specifer pairs, one for each entry
12+ in clock-names.
13+- clock-names: should contain followings:
14+ - "apb": the parent APB clock for this controller
15+ - "codec": the parent module clock
16+
17+Example:
18+codec: codec@01c22c00 {
19+ #sound-dai-cells = <0>;
20+ compatible = "allwinner,sun7i-a20-codec";
21+ reg = <0x01c22c00 0x40>;
22+ interrupts = <0 30 4>;
23+ clocks = <&apb0_gates 0>, <&codec_clk>;
24+ clock-names = "apb", "codec";
25+ dmas = <&dma 0 19>, <&dma 0 19>;
26+ dma-names = "rx", "tx";
27+};
Documentation/devicetree/bindings/sound/tdm-slot.txt+10−1
@@ -4,11 +4,15 @@ This specifies audio DAI's TDM slot. · 3 unmodified lines
44
55 TDM slot properties:
66 dai-tdm-slot-num : Number of slots in use.
7−dai-tdm-slot-width : Width in bits for each slot.
7+dai-tdm-slot-width : Width in bits for each slot.
8+dai-tdm-slot-tx-mask : Transmit direction slot mask, optional
9+dai-tdm-slot-rx-mask : Receive direction slot mask, optional
810
911 For instance:
1012 dai-tdm-slot-num = <2>;
1113 dai-tdm-slot-width = <8>;
14+ dai-tdm-slot-tx-mask = <0 1>;
15+ dai-tdm-slot-rx-mask = <1 0>;
1216
1317 And for each spcified driver, there could be one .of_xlate_tdm_slot_mask()
1418 to specify a explicit mapping of the channels and the slots. If it's absent
@@ -18,3 +22,8 @@ tx and rx masks. · 3 unmodified lines
1822 For snd_soc_of_xlate_tdm_slot_mask(), the tx and rx masks will use a 1 bit
1923 for an active slot as default, and the default active bits are at the LSB of
2024 the masks.
25+
26+The explicit masks are given as array of integers, where the first
27+number presents bit-0 (LSB), second presents bit-1, etc. Any non zero
28+number is considered 1 and 0 is 0. snd_soc_of_xlate_tdm_slot_mask()
29+does not do anything, if either mask is set non zero value.
Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt+38−0
@@ -0,0 +1,38 @@
1+Broadcom BCM2835 auxiliar SPI1/2 controller
2+
3+The BCM2835 contains two forms of SPI master controller, one known simply as
4+SPI0, and the other known as the "Universal SPI Master"; part of the
5+auxiliary block. This binding applies to the SPI1/2 controller.
6+
7+Required properties:
8+- compatible: Should be "brcm,bcm2835-aux-spi".
9+- reg: Should contain register location and length for the spi block
10+- interrupts: Should contain shared interrupt of the aux block
11+- clocks: The clock feeding the SPI controller - needs to
12+ point to the auxiliar clock driver of the bcm2835,
13+ as this clock will enable the output gate for the specific
14+ clock.
15+- cs-gpios: the cs-gpios (native cs is NOT supported)
16+ see also spi-bus.txt
17+
18+Example:
19+
20+spi1@7e215080 {
21+ compatible = "brcm,bcm2835-aux-spi";
22+ reg = <0x7e215080 0x40>;
23+ interrupts = <1 29>;
24+ clocks = <&aux_clocks BCM2835_AUX_CLOCK_SPI1>;
25+ #address-cells = <1>;
26+ #size-cells = <0>;
27+ cs-gpios = <&gpio 18>, <&gpio 17>, <&gpio 16>;
28+};
29+
30+spi2@7e2150c0 {
31+ compatible = "brcm,bcm2835-aux-spi";
32+ reg = <0x7e2150c0 0x40>;
33+ interrupts = <1 29>;
34+ clocks = <&aux_clocks BCM2835_AUX_CLOCK_SPI2>;
35+ #address-cells = <1>;
36+ #size-cells = <0>;
37+ cs-gpios = <&gpio 43>, <&gpio 44>, <&gpio 45>;
38+};
Documentation/devicetree/bindings/spi/sh-msiof.txt+1−1
@@ -51,7 +51,7 @@ Optional properties, deprecated for soctype-specific bindings: · 50 unmodified lines
5151 - renesas,tx-fifo-size : Overrides the default tx fifo size given in words
5252 (default is 64)
5353 - renesas,rx-fifo-size : Overrides the default rx fifo size given in words
54− (default is 64, or 256 on R-Car Gen2)
54+ (default is 64)
5555
5656 Pinctrl properties might be needed, too. See
5757 Documentation/devicetree/bindings/pinctrl/renesas,*.
Documentation/devicetree/bindings/spi/spi-mt65xx.txt+6−3
@@ -29,8 +29,11 @@ Required properties: · 28 unmodified lines
2929 muxes clock, and "spi-clk" for the clock gate.
3030
3131 Optional properties:
32+-cs-gpios: see spi-bus.txt, only required for MT8173.
33+
3234 - mediatek,pad-select: specify which pins group(ck/mi/mo/cs) spi
33− controller used, this value should be 0~3, only required for MT8173.
35+ controller used. This is a array, the element value should be 0~3,
36+ only required for MT8173.
3437 0: specify GPIO69,70,71,72 for spi pins.
3538 1: specify GPIO102,103,104,105 for spi pins.
3639 2: specify GPIO128,129,130,131 for spi pins.
@@ -49,7 +52,7 @@ spi: spi@1100a000 { · 12 unmodified lines
4952 <&topckgen CLK_TOP_SPI_SEL>,
5053 <&pericfg CLK_PERI_SPI0>;
5154 clock-names = "parent-clk", "sel-clk", "spi-clk";
52−
53− mediatek,pad-select = <0>;
55+ cs-gpios = <&pio 105 GPIO_ACTIVE_LOW>, <&pio 72 GPIO_ACTIVE_LOW>;
56+ mediatek,pad-select = <1>, <0>;
5457 status = "disabled";
5558 };
Documentation/devicetree/bindings/thermal/rockchip-thermal.txt+9−2
@@ -12,6 +12,11 @@ Required properties: · 11 unmodified lines
1212 - resets : Must contain an entry for each entry in reset-names.
1313 See ../reset/reset.txt for details.
1414 - reset-names : Must include the name "tsadc-apb".
15+- pinctrl-names : The pin control state names;
16+- pinctrl-0 : The "init" pinctrl state, it will be set before device probe.
17+- pinctrl-1 : The "default" pinctrl state, it will be set after reset the
18+ TSADC controller.
19+- pinctrl-2 : The "sleep" pinctrl state, it will be in for suspend.
1520 - #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description.
1621 - rockchip,hw-tshut-temp : The hardware-controlled shutdown temperature value.
1722 - rockchip,hw-tshut-mode : The hardware-controlled shutdown mode 0:CRU 1:GPIO.
@@ -27,8 +32,10 @@ tsadc: tsadc@ff280000 { · 9 unmodified lines
2732 clock-names = "tsadc", "apb_pclk";
2833 resets = <&cru SRST_TSADC>;
2934 reset-names = "tsadc-apb";
30− pinctrl-names = "default";
31− pinctrl-0 = <&otp_out>;
35+ pinctrl-names = "init", "default", "sleep";
36+ pinctrl-0 = <&otp_gpio>;
37+ pinctrl-1 = <&otp_out>;
38+ pinctrl-2 = <&otp_gpio>;
3239 #thermal-sensor-cells = <1>;
3340 rockchip,hw-tshut-temp = <95000>;
3441 rockchip,hw-tshut-mode = <0>;
Documentation/devicetree/bindings/thermal/ti_soc_thermal.txt+14−0
@@ -10,6 +10,8 @@ to the silicon temperature. · 9 unmodified lines
1010
1111 Required properties:
1212 - compatible : Should be:
13+ - "ti,omap34xx-bandgap" : for OMAP34xx bandgap
14+ - "ti,omap36xx-bandgap" : for OMAP36xx bandgap
1315 - "ti,omap4430-bandgap" : for OMAP4430 bandgap
1416 - "ti,omap4460-bandgap" : for OMAP4460 bandgap
1517 - "ti,omap4470-bandgap" : for OMAP4470 bandgap
@@ -25,6 +27,18 @@ to each bandgap version, because the mapping may change from · 9 unmodified lines
2527 soc to soc, apart of depending on available features.
2628
2729 Example:
30+OMAP34xx:
31+bandgap {
32+ reg = <0x48002524 0x4>;
33+ compatible = "ti,omap34xx-bandgap";
34+};
35+
36+OMAP36xx:
37+bandgap {
38+ reg = <0x48002524 0x4>;
39+ compatible = "ti,omap36xx-bandgap";
40+};
41+
2842 OMAP4430:
2943 bandgap {
3044 reg = <0x4a002260 0x4 0x4a00232C 0x4>;
Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt+5−3
@@ -3,10 +3,12 @@ Mediatek MT6577, MT6572 and MT6589 Timers · 2 unmodified lines
33
44 Required properties:
55 - compatible should contain:
6− * "mediatek,mt6589-timer" for MT6589 compatible timers
76 * "mediatek,mt6580-timer" for MT6580 compatible timers
8− * "mediatek,mt6577-timer" for all compatible timers (MT6589, MT6580,
9− MT6577)
7+ * "mediatek,mt6589-timer" for MT6589 compatible timers
8+ * "mediatek,mt8127-timer" for MT8127 compatible timers
9+ * "mediatek,mt8135-timer" for MT8135 compatible timers
10+ * "mediatek,mt8173-timer" for MT8173 compatible timers
11+ * "mediatek,mt6577-timer" for MT6577 and all above compatible timers
1012 - reg: Should contain location and length for timers register.
1113 - clocks: Clocks driving the timer hardware. This list should include two
1214 clocks. The order is system clock and as second clock the RTC clock.
Documentation/devicetree/bindings/ufs/ufs-qcom.txt+58−0
@@ -0,0 +1,58 @@
1+* Qualcomm Technologies Inc Universal Flash Storage (UFS) PHY
2+
3+UFSPHY nodes are defined to describe on-chip UFS PHY hardware macro.
4+Each UFS PHY node should have its own node.
5+
6+To bind UFS PHY with UFS host controller, the controller node should
7+contain a phandle reference to UFS PHY node.
8+
9+Required properties:
10+- compatible : compatible list, contains "qcom,ufs-phy-qmp-20nm"
11+ or "qcom,ufs-phy-qmp-14nm" according to the relevant phy in use.
12+- reg : should contain PHY register address space (mandatory),
13+- reg-names : indicates various resources passed to driver (via reg proptery) by name.
14+ Required "reg-names" is "phy_mem".
15+- #phy-cells : This property shall be set to 0
16+- vdda-phy-supply : phandle to main PHY supply for analog domain
17+- vdda-pll-supply : phandle to PHY PLL and Power-Gen block power supply
18+- clocks : List of phandle and clock specifier pairs
19+- clock-names : List of clock input name strings sorted in the same
20+ order as the clocks property. "ref_clk_src", "ref_clk",
21+ "tx_iface_clk" & "rx_iface_clk" are mandatory but
22+ "ref_clk_parent" is optional
23+
24+Optional properties:
25+- vdda-phy-max-microamp : specifies max. load that can be drawn from phy supply
26+- vdda-pll-max-microamp : specifies max. load that can be drawn from pll supply
27+- vddp-ref-clk-supply : phandle to UFS device ref_clk pad power supply
28+- vddp-ref-clk-max-microamp : specifies max. load that can be drawn from this supply
29+- vddp-ref-clk-always-on : specifies if this supply needs to be kept always on
30+
31+Example:
32+
33+ ufsphy1: ufsphy@0xfc597000 {
34+ compatible = "qcom,ufs-phy-qmp-20nm";
35+ reg = <0xfc597000 0x800>;
36+ reg-names = "phy_mem";
37+ #phy-cells = <0>;
38+ vdda-phy-supply = <&pma8084_l4>;
39+ vdda-pll-supply = <&pma8084_l12>;
40+ vdda-phy-max-microamp = <50000>;
41+ vdda-pll-max-microamp = <1000>;
42+ clock-names = "ref_clk_src",
43+ "ref_clk_parent",
44+ "ref_clk",
45+ "tx_iface_clk",
46+ "rx_iface_clk";
47+ clocks = <&clock_rpm clk_ln_bb_clk>,
48+ <&clock_gcc clk_pcie_1_phy_ldo >,
49+ <&clock_gcc clk_ufs_phy_ldo>,
50+ <&clock_gcc clk_gcc_ufs_tx_cfg_clk>,
51+ <&clock_gcc clk_gcc_ufs_rx_cfg_clk>;
52+ };
53+
54+ ufshc@0xfc598000 {
55+ ...
56+ phys = <&ufsphy1>;
57+ phy-names = "ufsphy";
58+ };
Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt+10−1
@@ -4,11 +4,18 @@ UFSHC nodes are defined to describe on-chip UFS host controllers. · 3 unmodified lines
44 Each UFS controller instance should have its own node.
55
66 Required properties:
7−- compatible : compatible list, contains "jedec,ufs-1.1"
7+- compatible : must contain "jedec,ufs-1.1", may also list one or more
8+ of the following:
9+ "qcom,msm8994-ufshc"
10+ "qcom,msm8996-ufshc"
11+ "qcom,ufshc"
812 - interrupts : <interrupt mapping for UFS host controller IRQ>
913 - reg : <registers mapping>
1014
1115 Optional properties:
16+- phys : phandle to UFS PHY node
17+- phy-names : the string "ufsphy" when is found in a node, along
18+ with "phys" attribute, provides phandle to UFS PHY node
1219 - vdd-hba-supply : phandle to UFS host controller supply regulator node
1320 - vcc-supply : phandle to VCC supply regulator node
1421 - vccq-supply : phandle to VCCQ supply regulator node
@@ -54,4 +61,6 @@ Example: · 39 unmodified lines
5461 clocks = <&core 0>, <&ref 0>, <&iface 0>;
5562 clock-names = "core_clk", "ref_clk", "iface_clk";
5663 freq-table-hz = <100000000 200000000>, <0 0>, <0 0>;
64+ phys = <&ufsphy1>;
65+ phy-names = "ufsphy";
5766 };
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt+21−6
@@ -27,10 +27,6 @@ Optional properties: · 26 unmodified lines
2727 - vbus-supply: reference to the VBUS regulator
2828 - maximum-speed: limit the maximum connection speed to "full-speed".
2929 - tpl-support: TPL (Targeted Peripheral List) feature for targeted hosts
30−- fsl,usbmisc: (FSL only) phandler of non-core register device, with one
31− argument that indicate usb controller index
32−- disable-over-current: (FSL only) disable over current detect
33−- external-vbus-divider: (FSL only) enables off-chip resistor divider for Vbus
3430 - itc-setting: interrupt threshold control register control, the setting
3531 should be aligned with ITC bits at register USBCMD.
3632 - ahb-burst-config: it is vendor dependent, the required value should be
@@ -41,11 +37,28 @@ Optional properties: · 4 unmodified lines
4137 - tx-burst-size-dword: it is vendor dependent, the tx burst size in dword
4238 (4 bytes), This register represents the maximum length of a the burst
4339 in 32-bit words while moving data from system memory to the USB
44− bus, changing this value takes effect only the SBUSCFG.AHBBRST is 0.
40+ bus, the value of this property will only take effect if property
41+ "ahb-burst-config" is set to 0, if this property is missing the reset
42+ default of the hardware implementation will be used.
4543 - rx-burst-size-dword: it is vendor dependent, the rx burst size in dword
4644 (4 bytes), This register represents the maximum length of a the burst
4745 in 32-bit words while moving data from the USB bus to system memory,
48− changing this value takes effect only the SBUSCFG.AHBBRST is 0.
46+ the value of this property will only take effect if property
47+ "ahb-burst-config" is set to 0, if this property is missing the reset
48+ default of the hardware implementation will be used.
49+- extcon: phandles to external connector devices. First phandle should point to
50+ external connector, which provide "USB" cable events, the second should point
51+ to external connector device, which provide "USB-HOST" cable events. If one
52+ of the external connector devices is not required, empty <0> phandle should
53+ be specified.
54+- phy-clkgate-delay-us: the delay time (us) between putting the PHY into
55+ low power mode and gating the PHY clock.
56+
57+i.mx specific properties
58+- fsl,usbmisc: phandler of non-core register device, with one
59+ argument that indicate usb controller index
60+- disable-over-current: disable over current detect
61+- external-vbus-divider: enables off-chip resistor divider for Vbus
4962
5063 Example:
5164
@@ -62,4 +75,6 @@ Example: · 10 unmodified lines
6275 ahb-burst-config = <0x0>;
6376 tx-burst-size-dword = <0x10>; /* 64 bytes */
6477 rx-burst-size-dword = <0x10>;
78+ extcon = <0>, <&usb_id>;
79+ phy-clkgate-delay-us = <400>;
6580 };
Documentation/devicetree/bindings/usb/dwc3.txt+7−1
@@ -1,6 +1,7 @@
11 synopsys DWC3 CORE
22
3−DWC3- USB3 CONTROLLER
3+DWC3- USB3 CONTROLLER. Complies to the generic USB binding properties
4+ as described in 'usb/generic.txt'
45
56 Required properties:
67 - compatible: must be "snps,dwc3"
@@ -35,11 +36,16 @@ Optional properties: · 28 unmodified lines
3536 LTSSM during USB3 Compliance mode.
3637 - snps,dis_u3_susphy_quirk: when set core will disable USB3 suspend phy.
3738 - snps,dis_u2_susphy_quirk: when set core will disable USB2 suspend phy.
39+ - snps,dis_enblslpm_quirk: when set clears the enblslpm in GUSB2PHYCFG,
40+ disabling the suspend signal to the PHY.
3841 - snps,is-utmi-l1-suspend: true when DWC3 asserts output signal
3942 utmi_l1_suspend_n, false when asserts utmi_sleep_n
4043 - snps,hird-threshold: HIRD threshold
4144 - snps,hsphy_interface: High-Speed PHY interface selection between "utmi" for
4245 UTMI+ and "ulpi" for ULPI when the DWC_USB3_HSPHY_INTERFACE has value 3.
46+ - snps,quirk-frame-length-adjustment: Value for GFLADJ_30MHZ field of GFLADJ
47+ register for post-silicon frame length adjustment when the
48+ fladj_30mhz_sdbnd signal is invalid or incorrect.
4349
4450 This is usually a subnode to DWC3 glue to which it is connected.
4551
Documentation/devicetree/bindings/usb/renesas_usbhs.txt+1−0
@@ -5,6 +5,7 @@ Required properties: · 4 unmodified lines
55 - "renesas,usbhs-r8a7790"
66 - "renesas,usbhs-r8a7791"
77 - "renesas,usbhs-r8a7794"
8+ - "renesas,usbhs-r8a7795"
89 - reg: Base address and length of the register for the USBHS
910 - interrupts: Interrupt specifier for the USBHS
1011 - clocks: A list of phandle + clock specifier pairs
Documentation/devicetree/bindings/usb/samsung-usbphy.txt+0−117
@@ -1,117 +0,0 @@
1−SAMSUNG USB-PHY controllers
2−
3−** Samsung's usb 2.0 phy transceiver
4−
5−The Samsung's usb 2.0 phy transceiver is used for controlling
6−usb 2.0 phy for s3c-hsotg as well as ehci-s5p and ohci-exynos
7−usb controllers across Samsung SOCs.
8−TODO: Adding the PHY binding with controller(s) according to the under
9−development generic PHY driver.
10−
11−Required properties:
12−
13−Exynos4210:
14−- compatible : should be "samsung,exynos4210-usb2phy"
15−- reg : base physical address of the phy registers and length of memory mapped
16− region.
17−- clocks: Clock IDs array as required by the controller.
18−- clock-names: names of clock correseponding IDs clock property as requested
19− by the controller driver.
20−
21−Exynos5250:
22−- compatible : should be "samsung,exynos5250-usb2phy"
23−- reg : base physical address of the phy registers and length of memory mapped
24− region.
25−
26−Optional properties:
27−- #address-cells: should be '1' when usbphy node has a child node with 'reg'
28− property.
29−- #size-cells: should be '1' when usbphy node has a child node with 'reg'
30− property.
31−- ranges: allows valid translation between child's address space and parent's
32− address space.
33−
34−- The child node 'usbphy-sys' to the node 'usbphy' is for the system controller
35− interface for usb-phy. It should provide the following information required by
36− usb-phy controller to control phy.
37− - reg : base physical address of PHY_CONTROL registers.
38− The size of this register is the total sum of size of all PHY_CONTROL
39− registers that the SoC has. For example, the size will be
40− '0x4' in case we have only one PHY_CONTROL register (e.g.
41− OTHERS register in S3C64XX or USB_PHY_CONTROL register in S5PV210)
42− and, '0x8' in case we have two PHY_CONTROL registers (e.g.
43− USBDEVICE_PHY_CONTROL and USBHOST_PHY_CONTROL registers in exynos4x).
44− and so on.
45−
46−Example:
47− - Exynos4210
48−
49− usbphy@125B0000 {
50− #address-cells = <1>;
51− #size-cells = <1>;
52− compatible = "samsung,exynos4210-usb2phy";
53− reg = <0x125B0000 0x100>;
54− ranges;
55−
56− clocks = <&clock 2>, <&clock 305>;
57− clock-names = "xusbxti", "otg";
58−
59− usbphy-sys {
60− /* USB device and host PHY_CONTROL registers */
61− reg = <0x10020704 0x8>;
62− };
63− };
64−
65−
66−** Samsung's usb 3.0 phy transceiver
67−
68−Starting exynso5250, Samsung's SoC have usb 3.0 phy transceiver
69−which is used for controlling usb 3.0 phy for dwc3-exynos usb 3.0
70−controllers across Samsung SOCs.
71−
72−Required properties:
73−
74−Exynos5250:
75−- compatible : should be "samsung,exynos5250-usb3phy"
76−- reg : base physical address of the phy registers and length of memory mapped
77− region.
78−- clocks: Clock IDs array as required by the controller.
79−- clock-names: names of clocks correseponding to IDs in the clock property
80− as requested by the controller driver.
81−
82−Optional properties:
83−- #address-cells: should be '1' when usbphy node has a child node with 'reg'
84− property.
85−- #size-cells: should be '1' when usbphy node has a child node with 'reg'
86− property.
87−- ranges: allows valid translation between child's address space and parent's
88− address space.
89−
90−- The child node 'usbphy-sys' to the node 'usbphy' is for the system controller
91− interface for usb-phy. It should provide the following information required by
92− usb-phy controller to control phy.
93− - reg : base physical address of PHY_CONTROL registers.
94− The size of this register is the total sum of size of all PHY_CONTROL
95− registers that the SoC has. For example, the size will be
96− '0x4' in case we have only one PHY_CONTROL register (e.g.
97− OTHERS register in S3C64XX or USB_PHY_CONTROL register in S5PV210)
98− and, '0x8' in case we have two PHY_CONTROL registers (e.g.
99− USBDEVICE_PHY_CONTROL and USBHOST_PHY_CONTROL registers in exynos4x).
100− and so on.
101−
102−Example:
103− usbphy@12100000 {
104− compatible = "samsung,exynos5250-usb3phy";
105− reg = <0x12100000 0x100>;
106− #address-cells = <1>;
107− #size-cells = <1>;
108− ranges;
109−
110− clocks = <&clock 1>, <&clock 286>;
111− clock-names = "ext_xtal", "usbdrd30";
112−
113− usbphy-sys {
114− /* USB device and host PHY_CONTROL registers */
115− reg = <0x10040704 0x8>;
116− };
117− };
Documentation/devicetree/bindings/vendor-prefixes.txt+10−0
@@ -34,6 +34,7 @@ avago Avago Technologies · 33 unmodified lines
3434 avic Shanghai AVIC Optoelectronics Co., Ltd.
3535 axis Axis Communications AB
3636 bosch Bosch Sensortec GmbH
37+boundary Boundary Devices Inc.
3738 brcm Broadcom Corporation
3839 buffalo Buffalo, Inc.
3940 calxeda Calxeda
@@ -51,6 +52,7 @@ cirrus Cirrus Logic, Inc. · 11 unmodified lines
5152 cloudengines Cloud Engines, Inc.
5253 cnm Chips&Media, Inc.
5354 cnxt Conexant Systems, Inc.
55+compulab CompuLab Ltd.
5456 cortina Cortina Systems, Inc.
5557 cosmic Cosmic Circuits
5658 crystalfontz Crystalfontz America, Inc.
@@ -82,6 +84,7 @@ everspin Everspin Technologies, Inc. · 25 unmodified lines
8284 excito Excito
8385 fcs Fairchild Semiconductor
8486 firefly Firefly
87+focaltech FocalTech Systems Co.,Ltd
8588 fsl Freescale Semiconductor
8689 GEFanuc GE Fanuc Intelligent Platforms Embedded Systems, Inc.
8790 gef GE Fanuc Intelligent Platforms Embedded Systems, Inc.
@@ -101,6 +104,7 @@ himax Himax Technologies, Inc. · 13 unmodified lines
101104 hisilicon Hisilicon Limited.
102105 hit Hitachi Ltd.
103106 hitex Hitex Development Tools
107+holt Holt Integrated Circuits, Inc.
104108 honeywell Honeywell
105109 hp Hewlett Packard
106110 i2se I2SE GmbH
@@ -168,7 +172,9 @@ pericom Pericom Technology Inc. · 61 unmodified lines
168172 phytec PHYTEC Messtechnik GmbH
169173 picochip Picochip Ltd
170174 plathome Plat'Home Co., Ltd.
175+plda PLDA
171176 pixcir PIXCIR MICROELECTRONICS Co., Ltd
177+pulsedlight PulsedLight, Inc
172178 powervr PowerVR (deprecated, use img)
173179 qca Qualcomm Atheros, Inc.
174180 qcom Qualcomm Technologies, Inc
@@ -191,7 +197,9 @@ sbs Smart Battery System · 16 unmodified lines
191197 schindler Schindler
192198 seagate Seagate Technology PLC
193199 semtech Semtech Corporation
200+sgx SGX Sensortech
194201 sharp Sharp Corporation
202+sigma Sigma Designs, Inc.
195203 sil Silicon Image
196204 silabs Silicon Laboratories
197205 siliconmitus Silicon Mitus, Inc.
@@ -222,7 +230,9 @@ toradex Toradex AG · 24 unmodified lines
222230 toshiba Toshiba Corporation
223231 toumaz Toumaz
224232 tplink TP-LINK Technologies Co., Ltd.
233+tronfy Tronfy
225234 truly Truly Semiconductors Limited
235+upisemi uPI Semiconductor Corp.
226236 usi Universal Scientific Industrial Co., Ltd.
227237 v3 V3 Semiconductor
228238 variscite Variscite Ltd.
Documentation/devicetree/bindings/w1/omap-hdq.txt+6−1
@@ -1,11 +1,15 @@
11 * OMAP HDQ One wire bus master controller
22
33 Required properties:
4−- compatible : should be "ti,omap3-1w"
4+- compatible : should be "ti,omap3-1w" or "ti,am4372-hdq"
55 - reg : Address and length of the register set for the device
66 - interrupts : interrupt line.
77 - ti,hwmods : "hdq1w"
88
9+Optional properties:
10+- ti,mode: should be "hdq": HDQ mode "1w": one-wire mode.
11+ If not specified HDQ mode is implied.
12+
913 Example:
1014
1115 - From omap3.dtsi
@@ -14,4 +18,5 @@ Example: · 2 unmodified lines
1418 reg = <0x480b2000 0x1000>;
1519 interrupts = <58>;
1620 ti,hwmods = "hdq1w";
21+ ti,mode = "hdq";
1722 };
Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.txt+19−0
@@ -0,0 +1,19 @@
1+BCM7038 Watchdog timer
2+
3+Required properties:
4+
5+- compatible : should be "brcm,bcm7038-wdt"
6+- reg : Specifies base physical address and size of the registers.
7+
8+Optional properties:
9+
10+- clocks: The clock running the watchdog. If no clock is found the
11+ driver will default to 27000000 Hz.
12+
13+Example:
14+
15+watchdog@f040a7e8 {
16+ compatible = "brcm,bcm7038-wdt";
17+ clocks = <&upg_fixed>;
18+ reg = <0xf040a7e8 0x16>;
19+};
Documentation/dontdiff+0−1
@@ -165,7 +165,6 @@ mach-types.h · 164 unmodified lines
165165 machtypes.h
166166 map
167167 map_hugetlb
168−media
169168 mconf
170169 miboot*
171170 mk_elfconfig
Documentation/driver-model/platform.txt+14−0
@@ -63,6 +63,20 @@ runtime memory footprint: · 62 unmodified lines
6363 int platform_driver_probe(struct platform_driver *drv,
6464 int (*probe)(struct platform_device *))
6565
66+Kernel modules can be composed of several platform drivers. The platform core
67+provides helpers to register and unregister an array of drivers:
68+
69+ int __platform_register_drivers(struct platform_driver * const *drivers,
70+ unsigned int count, struct module *owner);
71+ void platform_unregister_drivers(struct platform_driver * const *drivers,
72+ unsigned int count);
73+
74+If one of the drivers fails to register, all drivers registered up to that
75+point will be unregistered in reverse order. Note that there is a convenience
76+macro that passes THIS_MODULE as owner parameter:
77+
78+ #define platform_register_driver(drivers, count)
79+
6680
6781 Device Enumeration
6882 ~~~~~~~~~~~~~~~~~~
Documentation/edac.txt+46−0
@@ -744,6 +744,52 @@ exports one · 743 unmodified lines
744744 possible that some errors could be lost. With rdimm's, they display the
745745 contents of the registers
746746
747+AMD64_EDAC REFERENCE DOCUMENTS USED
748+-----------------------------------
749+amd64_edac module is based on the following documents
750+(available from http://support.amd.com/en-us/search/tech-docs):
751+
752+1. Title: BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD
753+ Opteron Processors
754+ AMD publication #: 26094
755+ Revision: 3.26
756+ Link: http://support.amd.com/TechDocs/26094.PDF
757+
758+2. Title: BIOS and Kernel Developer's Guide for AMD NPT Family 0Fh
759+ Processors
760+ AMD publication #: 32559
761+ Revision: 3.00
762+ Issue Date: May 2006
763+ Link: http://support.amd.com/TechDocs/32559.pdf
764+
765+3. Title: BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h
766+ Processors
767+ AMD publication #: 31116
768+ Revision: 3.00
769+ Issue Date: September 07, 2007
770+ Link: http://support.amd.com/TechDocs/31116.pdf
771+
772+4. Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 15h
773+ Models 30h-3Fh Processors
774+ AMD publication #: 49125
775+ Revision: 3.06
776+ Issue Date: 2/12/2015 (latest release)
777+ Link: http://support.amd.com/TechDocs/49125_15h_Models_30h-3Fh_BKDG.pdf
778+
779+5. Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 15h
780+ Models 60h-6Fh Processors
781+ AMD publication #: 50742
782+ Revision: 3.01
783+ Issue Date: 7/23/2015 (latest release)
784+ Link: http://support.amd.com/TechDocs/50742_15h_Models_60h-6Fh_BKDG.pdf
785+
786+6. Title: BIOS and Kernel Developer's Guide (BKDG) for AMD Family 16h
787+ Models 00h-0Fh Processors
788+ AMD publication #: 48751
789+ Revision: 3.03
790+ Issue Date: 2/23/2015 (latest release)
791+ Link: http://support.amd.com/TechDocs/48751_16h_bkdg.pdf
792+
747793 CREDITS:
748794 ========
749795
Documentation/email-clients.txt+37−1
@@ -176,11 +176,47 @@ To use 'vim' with mutt: · 175 unmodified lines
176176 if you want to include the patch inline.
177177 (a)ttach works fine without "set paste".
178178
179+You can also generate patches with 'git format-patch' and then use Mutt
180+to send them:
181+ $ mutt -H 0001-some-bug-fix.patch
182+
179183 Config options:
180184 It should work with default settings.
181185 However, it's a good idea to set the "send_charset" to:
182186 set send_charset="us-ascii:utf-8"
183187
188+Mutt is highly customizable. Here is a minimum configuration to start
189+using Mutt to send patches through Gmail:
190+
191+# .muttrc
192+# ================ IMAP ====================
193+set imap_user = 'yourusername@gmail.com'
194+set imap_pass = 'yourpassword'
195+set spoolfile = imaps://imap.gmail.com/INBOX
196+set folder = imaps://imap.gmail.com/
197+set record="imaps://imap.gmail.com/[Gmail]/Sent Mail"
198+set postponed="imaps://imap.gmail.com/[Gmail]/Drafts"
199+set mbox="imaps://imap.gmail.com/[Gmail]/All Mail"
200+
201+# ================ SMTP ====================
202+set smtp_url = "smtp://username@smtp.gmail.com:587/"
203+set smtp_pass = $imap_pass
204+set ssl_force_tls = yes # Require encrypted connection
205+
206+# ================ Composition ====================
207+set editor = `echo \$EDITOR`
208+set edit_headers = yes # See the headers when editing
209+set charset = UTF-8 # value of $LANG; also fallback for send_charset
210+# Sender, email address, and sign-off line must match
211+unset use_domain # because joe@localhost is just embarrassing
212+set realname = "YOUR NAME"
213+set from = "username@gmail.com"
214+set use_from = yes
215+
216+The Mutt docs have lots more information:
217+ http://dev.mutt.org/trac/wiki/UseCases/Gmail
218+ http://dev.mutt.org/doc/manual.html
219+
184220 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
185221 Pine (TUI)
186222
@@ -220,7 +256,7 @@ to coerce it into behaving. · 33 unmodified lines
220256 Compose dialog.
221257
222258 Please note that "external editor" requires that your editor must not
223− fork, or in other words, the editor must not return before closing.
259+ fork, or in other words, the editor must not return before closing.
224260 You may have to pass additional flags or change the settings of your
225261 editor. Most notably if you are using gvim then you must pass the -f
226262 option to gvim by putting "/usr/bin/gvim -f" (if the binary is in
Documentation/features/debug/KASAN/arch-support.txt+1−1
@@ -9,7 +9,7 @@ · 8 unmodified lines
99 | alpha: | TODO |
1010 | arc: | TODO |
1111 | arm: | TODO |
12− | arm64: | TODO |
12+ | arm64: | ok |
1313 | avr32: | TODO |
1414 | blackfin: | TODO |
1515 | c6x: | TODO |
Documentation/features/vm/THP/arch-support.txt+1−1
@@ -7,7 +7,7 @@ · 6 unmodified lines
77 | arch |status|
88 -----------------------
99 | alpha: | TODO |
10− | arc: | .. |
10+ | arc: | ok |
1111 | arm: | ok |
1212 | arm64: | ok |
1313 | avr32: | .. |
Documentation/features/vm/pte_special/arch-support.txt+1−1
@@ -7,7 +7,7 @@ · 6 unmodified lines
77 | arch |status|
88 -----------------------
99 | alpha: | TODO |
10− | arc: | TODO |
10+ | arc: | ok |
1111 | arm: | ok |
1212 | arm64: | ok |
1313 | avr32: | TODO |
Documentation/filesystems/Makefile+0−2
@@ -1,5 +1,3 @@
1−subdir-y := configfs
2−
31 # List of programs to build
42 hostprogs-y := dnotify_test
53
Documentation/filesystems/configfs/Makefile+0−3
@@ -1,3 +0,0 @@
1−ifneq ($(CONFIG_CONFIGFS_FS),)
2−obj-m += configfs_example_explicit.o configfs_example_macros.o
3−endif
Documentation/filesystems/configfs/configfs.txt+11−27
@@ -160,12 +160,6 @@ among other things. For that, it needs a type. · 159 unmodified lines
160160
161161 struct configfs_item_operations {
162162 void (*release)(struct config_item *);
163− ssize_t (*show_attribute)(struct config_item *,
164− struct configfs_attribute *,
165− char *);
166− ssize_t (*store_attribute)(struct config_item *,
167− struct configfs_attribute *,
168− const char *, size_t);
169163 int (*allow_link)(struct config_item *src,
170164 struct config_item *target);
171165 int (*drop_link)(struct config_item *src,
@@ -183,9 +177,7 @@ The most basic function of a config_item_type is to define what · 11 unmodified lines
183177 operations can be performed on a config_item. All items that have been
184178 allocated dynamically will need to provide the ct_item_ops->release()
185179 method. This method is called when the config_item's reference count
186−reaches zero. Items that wish to display an attribute need to provide
187−the ct_item_ops->show_attribute() method. Similarly, storing a new
188−attribute value uses the store_attribute() method.
180+reaches zero.
189181
190182 [struct configfs_attribute]
191183
@@ -193,6 +185,8 @@ attribute value uses the store_attribute() method. · 1 unmodified line
193185 char *ca_name;
194186 struct module *ca_owner;
195187 umode_t ca_mode;
188+ ssize_t (*show)(struct config_item *, char *);
189+ ssize_t (*store)(struct config_item *, const char *, size_t);
196190 };
197191
198192 When a config_item wants an attribute to appear as a file in the item's
@@ -202,10 +196,10 @@ config_item_type->ct_attrs. When the item appears in configfs, the · 3 unmodified lines
202196 attribute file will appear with the configfs_attribute->ca_name
203197 filename. configfs_attribute->ca_mode specifies the file permissions.
204198
205−If an attribute is readable and the config_item provides a
206−ct_item_ops->show_attribute() method, that method will be called
207−whenever userspace asks for a read(2) on the attribute. The converse
208−will happen for write(2).
199+If an attribute is readable and provides a ->show method, that method will
200+be called whenever userspace asks for a read(2) on the attribute. If an
201+attribute is writable and provides a ->store method, that method will be
202+be called whenever userspace asks for a write(2) on the attribute.
209203
210204 [struct config_group]
211205
@@ -311,20 +305,10 @@ the subsystem must be ready for it. · 99 unmodified lines
311305 [An Example]
312306
313307 The best example of these basic concepts is the simple_children
314−subsystem/group and the simple_child item in configfs_example_explicit.c
315−and configfs_example_macros.c. It shows a trivial object displaying and
316−storing an attribute, and a simple group creating and destroying these
317−children.
318−
319−The only difference between configfs_example_explicit.c and
320−configfs_example_macros.c is how the attributes of the childless item
321−are defined. The childless item has extended attributes, each with
322−their own show()/store() operation. This follows a convention commonly
323−used in sysfs. configfs_example_explicit.c creates these attributes
324−by explicitly defining the structures involved. Conversely
325−configfs_example_macros.c uses some convenience macros from configfs.h
326−to define the attributes. These macros are similar to their sysfs
327−counterparts.
308+subsystem/group and the simple_child item in
309+samples/configfs/configfs_sample.c. It shows a trivial object displaying
310+and storing an attribute, and a simple group creating and destroying
311+these children.
328312
329313 [Hierarchy Navigation and the Subsystem Mutex]
330314
Documentation/filesystems/configfs/configfs_example_explicit.c+0−483
@@ -1,483 +0,0 @@
1−/*
2− * vim: noexpandtab ts=8 sts=0 sw=8:
3− *
4− * configfs_example_explicit.c - This file is a demonstration module
5− * containing a number of configfs subsystems. It explicitly defines
6− * each structure without using the helper macros defined in
7− * configfs.h.
8− *
9− * This program is free software; you can redistribute it and/or
10− * modify it under the terms of the GNU General Public
11− * License as published by the Free Software Foundation; either
12− * version 2 of the License, or (at your option) any later version.
13− *
14− * This program is distributed in the hope that it will be useful,
15− * but WITHOUT ANY WARRANTY; without even the implied warranty of
16− * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17− * General Public License for more details.
18− *
19− * You should have received a copy of the GNU General Public
20− * License along with this program; if not, write to the
21− * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
22− * Boston, MA 021110-1307, USA.
23− *
24− * Based on sysfs:
25− * sysfs is Copyright (C) 2001, 2002, 2003 Patrick Mochel
26− *
27− * configfs Copyright (C) 2005 Oracle. All rights reserved.
28− */
29−
30−#include <linux/init.h>
31−#include <linux/module.h>
32−#include <linux/slab.h>
33−
34−#include <linux/configfs.h>
35−
36−
37−
38−/*
39− * 01-childless
40− *
41− * This first example is a childless subsystem. It cannot create
42− * any config_items. It just has attributes.
43− *
44− * Note that we are enclosing the configfs_subsystem inside a container.
45− * This is not necessary if a subsystem has no attributes directly
46− * on the subsystem. See the next example, 02-simple-children, for
47− * such a subsystem.
48− */
49−
50−struct childless {
51− struct configfs_subsystem subsys;
52− int showme;
53− int storeme;
54−};
55−
56−struct childless_attribute {
57− struct configfs_attribute attr;
58− ssize_t (*show)(struct childless *, char *);
59− ssize_t (*store)(struct childless *, const char *, size_t);
60−};
61−
62−static inline struct childless *to_childless(struct config_item *item)
63−{
64− return item ? container_of(to_configfs_subsystem(to_config_group(item)), struct childless, subsys) : NULL;
65−}
66−
67−static ssize_t childless_showme_read(struct childless *childless,
68− char *page)
69−{
70− ssize_t pos;
71−
72− pos = sprintf(page, "%d\n", childless->showme);
73− childless->showme++;
74−
75− return pos;
76−}
77−
78−static ssize_t childless_storeme_read(struct childless *childless,
79− char *page)
80−{
81− return sprintf(page, "%d\n", childless->storeme);
82−}
83−
84−static ssize_t childless_storeme_write(struct childless *childless,
85− const char *page,
86− size_t count)
87−{
88− unsigned long tmp;
89− char *p = (char *) page;
90−
91− tmp = simple_strtoul(p, &p, 10);
92− if ((*p != '\0') && (*p != '\n'))
93− return -EINVAL;
94−
95− if (tmp > INT_MAX)
96− return -ERANGE;
97−
98− childless->storeme = tmp;
99−
100− return count;
101−}
102−
103−static ssize_t childless_description_read(struct childless *childless,
104− char *page)
105−{
106− return sprintf(page,
107−"[01-childless]\n"
108−"\n"
109−"The childless subsystem is the simplest possible subsystem in\n"
110−"configfs. It does not support the creation of child config_items.\n"
111−"It only has a few attributes. In fact, it isn't much different\n"
112−"than a directory in /proc.\n");
113−}
114−
115−static struct childless_attribute childless_attr_showme = {
116− .attr = { .ca_owner = THIS_MODULE, .ca_name = "showme", .ca_mode = S_IRUGO },
117− .show = childless_showme_read,
118−};
119−static struct childless_attribute childless_attr_storeme = {
120− .attr = { .ca_owner = THIS_MODULE, .ca_name = "storeme", .ca_mode = S_IRUGO | S_IWUSR },
121− .show = childless_storeme_read,
122− .store = childless_storeme_write,
123−};
124−static struct childless_attribute childless_attr_description = {
125− .attr = { .ca_owner = THIS_MODULE, .ca_name = "description", .ca_mode = S_IRUGO },
126− .show = childless_description_read,
127−};
128−
129−static struct configfs_attribute *childless_attrs[] = {
130− &childless_attr_showme.attr,
131− &childless_attr_storeme.attr,
132− &childless_attr_description.attr,
133− NULL,
134−};
135−
136−static ssize_t childless_attr_show(struct config_item *item,
137− struct configfs_attribute *attr,
138− char *page)
139−{
140− struct childless *childless = to_childless(item);
141− struct childless_attribute *childless_attr =
142− container_of(attr, struct childless_attribute, attr);
143− ssize_t ret = 0;
144−
145− if (childless_attr->show)
146− ret = childless_attr->show(childless, page);
147− return ret;
148−}
149−
150−static ssize_t childless_attr_store(struct config_item *item,
151− struct configfs_attribute *attr,
152− const char *page, size_t count)
153−{
154− struct childless *childless = to_childless(item);
155− struct childless_attribute *childless_attr =
156− container_of(attr, struct childless_attribute, attr);
157− ssize_t ret = -EINVAL;
158−
159− if (childless_attr->store)
160− ret = childless_attr->store(childless, page, count);
161− return ret;
162−}
163−
164−static struct configfs_item_operations childless_item_ops = {
165− .show_attribute = childless_attr_show,
166− .store_attribute = childless_attr_store,
167−};
168−
169−static struct config_item_type childless_type = {
170− .ct_item_ops = &childless_item_ops,
171− .ct_attrs = childless_attrs,
172− .ct_owner = THIS_MODULE,
173−};
174−
175−static struct childless childless_subsys = {
176− .subsys = {
177− .su_group = {
178− .cg_item = {
179− .ci_namebuf = "01-childless",
180− .ci_type = &childless_type,
181− },
182− },
183− },
184−};
185−
186−
187−/* ----------------------------------------------------------------- */
188−
189−/*
190− * 02-simple-children
191− *
192− * This example merely has a simple one-attribute child. Note that
193− * there is no extra attribute structure, as the child's attribute is
194− * known from the get-go. Also, there is no container for the
195− * subsystem, as it has no attributes of its own.
196− */
197−
198−struct simple_child {
199− struct config_item item;
200− int storeme;
201−};
202−
203−static inline struct simple_child *to_simple_child(struct config_item *item)
204−{
205− return item ? container_of(item, struct simple_child, item) : NULL;
206−}
207−
208−static struct configfs_attribute simple_child_attr_storeme = {
209− .ca_owner = THIS_MODULE,
210− .ca_name = "storeme",
211− .ca_mode = S_IRUGO | S_IWUSR,
212−};
213−
214−static struct configfs_attribute *simple_child_attrs[] = {
215− &simple_child_attr_storeme,
216− NULL,
217−};
218−
219−static ssize_t simple_child_attr_show(struct config_item *item,
220− struct configfs_attribute *attr,
221− char *page)
222−{
223− ssize_t count;
224− struct simple_child *simple_child = to_simple_child(item);
225−
226− count = sprintf(page, "%d\n", simple_child->storeme);
227−
228− return count;
229−}
230−
231−static ssize_t simple_child_attr_store(struct config_item *item,
232− struct configfs_attribute *attr,
233− const char *page, size_t count)
234−{
235− struct simple_child *simple_child = to_simple_child(item);
236− unsigned long tmp;
237− char *p = (char *) page;
238−
239− tmp = simple_strtoul(p, &p, 10);
240− if (!p || (*p && (*p != '\n')))
241− return -EINVAL;
242−
243− if (tmp > INT_MAX)
244− return -ERANGE;
245−
246− simple_child->storeme = tmp;
247−
248− return count;
249−}
250−
251−static void simple_child_release(struct config_item *item)
252−{
253− kfree(to_simple_child(item));
254−}
255−
256−static struct configfs_item_operations simple_child_item_ops = {
257− .release = simple_child_release,
258− .show_attribute = simple_child_attr_show,
259− .store_attribute = simple_child_attr_store,
260−};
261−
262−static struct config_item_type simple_child_type = {
263− .ct_item_ops = &simple_child_item_ops,
264− .ct_attrs = simple_child_attrs,
265− .ct_owner = THIS_MODULE,
266−};
267−
268−
269−struct simple_children {
270− struct config_group group;
271−};
272−
273−static inline struct simple_children *to_simple_children(struct config_item *item)
274−{
275− return item ? container_of(to_config_group(item), struct simple_children, group) : NULL;
276−}
277−
278−static struct config_item *simple_children_make_item(struct config_group *group, const char *name)
279−{
280− struct simple_child *simple_child;
281−
282− simple_child = kzalloc(sizeof(struct simple_child), GFP_KERNEL);
283− if (!simple_child)
284− return ERR_PTR(-ENOMEM);
285−
286− config_item_init_type_name(&simple_child->item, name,
287− &simple_child_type);
288−
289− simple_child->storeme = 0;
290−
291− return &simple_child->item;
292−}
293−
294−static struct configfs_attribute simple_children_attr_description = {
295− .ca_owner = THIS_MODULE,
296− .ca_name = "description",
297− .ca_mode = S_IRUGO,
298−};
299−
300−static struct configfs_attribute *simple_children_attrs[] = {
301− &simple_children_attr_description,
302− NULL,
303−};
304−
305−static ssize_t simple_children_attr_show(struct config_item *item,
306− struct configfs_attribute *attr,
307− char *page)
308−{
309− return sprintf(page,
310−"[02-simple-children]\n"
311−"\n"
312−"This subsystem allows the creation of child config_items. These\n"
313−"items have only one attribute that is readable and writeable.\n");
314−}
315−
316−static void simple_children_release(struct config_item *item)
317−{
318− kfree(to_simple_children(item));
319−}
320−
321−static struct configfs_item_operations simple_children_item_ops = {
322− .release = simple_children_release,
323− .show_attribute = simple_children_attr_show,
324−};
325−
326−/*
327− * Note that, since no extra work is required on ->drop_item(),
328− * no ->drop_item() is provided.
329− */
330−static struct configfs_group_operations simple_children_group_ops = {
331− .make_item = simple_children_make_item,
332−};
333−
334−static struct config_item_type simple_children_type = {
335− .ct_item_ops = &simple_children_item_ops,
336− .ct_group_ops = &simple_children_group_ops,
337− .ct_attrs = simple_children_attrs,
338− .ct_owner = THIS_MODULE,
339−};
340−
341−static struct configfs_subsystem simple_children_subsys = {
342− .su_group = {
343− .cg_item = {
344− .ci_namebuf = "02-simple-children",
345− .ci_type = &simple_children_type,
346− },
347− },
348−};
349−
350−
351−/* ----------------------------------------------------------------- */
352−
353−/*
354− * 03-group-children
355− *
356− * This example reuses the simple_children group from above. However,
357− * the simple_children group is not the subsystem itself, it is a
358− * child of the subsystem. Creation of a group in the subsystem creates
359− * a new simple_children group. That group can then have simple_child
360− * children of its own.
361− */
362−
363−static struct config_group *group_children_make_group(struct config_group *group, const char *name)
364−{
365− struct simple_children *simple_children;
366−
367− simple_children = kzalloc(sizeof(struct simple_children),
368− GFP_KERNEL);
369− if (!simple_children)
370− return ERR_PTR(-ENOMEM);
371−
372− config_group_init_type_name(&simple_children->group, name,
373− &simple_children_type);
374−
375− return &simple_children->group;
376−}
377−
378−static struct configfs_attribute group_children_attr_description = {
379− .ca_owner = THIS_MODULE,
380− .ca_name = "description",
381− .ca_mode = S_IRUGO,
382−};
383−
384−static struct configfs_attribute *group_children_attrs[] = {
385− &group_children_attr_description,
386− NULL,
387−};
388−
389−static ssize_t group_children_attr_show(struct config_item *item,
390− struct configfs_attribute *attr,
391− char *page)
392−{
393− return sprintf(page,
394−"[03-group-children]\n"
395−"\n"
396−"This subsystem allows the creation of child config_groups. These\n"
397−"groups are like the subsystem simple-children.\n");
398−}
399−
400−static struct configfs_item_operations group_children_item_ops = {
401− .show_attribute = group_children_attr_show,
402−};
403−
404−/*
405− * Note that, since no extra work is required on ->drop_item(),
406− * no ->drop_item() is provided.
407− */
408−static struct configfs_group_operations group_children_group_ops = {
409− .make_group = group_children_make_group,
410−};
411−
412−static struct config_item_type group_children_type = {
413− .ct_item_ops = &group_children_item_ops,
414− .ct_group_ops = &group_children_group_ops,
415− .ct_attrs = group_children_attrs,
416− .ct_owner = THIS_MODULE,
417−};
418−
419−static struct configfs_subsystem group_children_subsys = {
420− .su_group = {
421− .cg_item = {
422− .ci_namebuf = "03-group-children",
423− .ci_type = &group_children_type,
424− },
425− },
426−};
427−
428−/* ----------------------------------------------------------------- */
429−
430−/*
431− * We're now done with our subsystem definitions.
432− * For convenience in this module, here's a list of them all. It
433− * allows the init function to easily register them. Most modules
434− * will only have one subsystem, and will only call register_subsystem
435− * on it directly.
436− */
437−static struct configfs_subsystem *example_subsys[] = {
438− &childless_subsys.subsys,
439− &simple_children_subsys,
440− &group_children_subsys,
441− NULL,
442−};
443−
444−static int __init configfs_example_init(void)
445−{
446− int ret;
447− int i;
448− struct configfs_subsystem *subsys;
449−
450− for (i = 0; example_subsys[i]; i++) {
451− subsys = example_subsys[i];
452−
453− config_group_init(&subsys->su_group);
454− mutex_init(&subsys->su_mutex);
455− ret = configfs_register_subsystem(subsys);
456− if (ret) {
457− printk(KERN_ERR "Error %d while registering subsystem %s\n",
458− ret,
459− subsys->su_group.cg_item.ci_namebuf);
460− goto out_unregister;
461− }
462− }
463−
464− return 0;
465−
466−out_unregister:
467− for (i--; i >= 0; i--)
468− configfs_unregister_subsystem(example_subsys[i]);
469−
470− return ret;
471−}
472−
473−static void __exit configfs_example_exit(void)
474−{
475− int i;
476−
477− for (i = 0; example_subsys[i]; i++)
478− configfs_unregister_subsystem(example_subsys[i]);
479−}
480−
481−module_init(configfs_example_init);
482−module_exit(configfs_example_exit);
483−MODULE_LICENSE("GPL");
Documentation/filesystems/debugfs.txt+1−1
@@ -105,7 +105,7 @@ a variable of type size_t. · 104 unmodified lines
105105 Boolean values can be placed in debugfs with:
106106
107107 struct dentry *debugfs_create_bool(const char *name, umode_t mode,
108− struct dentry *parent, u32 *value);
108+ struct dentry *parent, bool *value);
109109
110110 A read on the resulting file will yield either Y (for non-zero values) or
111111 N, followed by a newline. If written to, it will accept either upper- or
Documentation/filesystems/f2fs.txt+2−1
@@ -102,7 +102,8 @@ background_gc=%s Turn on/off cleaning operations, namely garbage · 101 unmodified lines
102102 collection, triggered in background when I/O subsystem is
103103 idle. If background_gc=on, it will turn on the garbage
104104 collection and if background_gc=off, garbage collection
105− will be truned off.
105+ will be truned off. If background_gc=sync, it will turn
106+ on synchronous garbage collection running in background.
106107 Default value for this option is on. So garbage
107108 collection is on by default.
108109 disable_roll_forward Disable the roll-forward recovery routine
Documentation/filesystems/gfs2-glocks.txt+3−3
@@ -5,7 +5,7 @@ This documents the basic principles of the glock state machine · 4 unmodified lines
55 internals. Each glock (struct gfs2_glock in fs/gfs2/incore.h)
66 has two main (internal) locks:
77
8− 1. A spinlock (gl_spin) which protects the internal state such
8+ 1. A spinlock (gl_lockref.lock) which protects the internal state such
99 as gl_state, gl_target and the list of holders (gl_holders)
1010 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other
1111 threads from making calls to the DLM, etc. at the same time. If a
@@ -82,8 +82,8 @@ rather than via the glock. · 70 unmodified lines
8282
8383 Locking rules for glock operations:
8484
85−Operation | GLF_LOCK bit lock held | gl_spin spinlock held
86−-----------------------------------------------------------------
85+Operation | GLF_LOCK bit lock held | gl_lockref.lock spinlock held
86+-------------------------------------------------------------------------
8787 go_xmote_th | Yes | No
8888 go_xmote_bh | Yes | No
8989 go_inval | Yes | No
Documentation/filesystems/nfs/nfsroot.txt+3−0
@@ -157,6 +157,9 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>: · 156 unmodified lines
157157 both: use both BOOTP and RARP but not DHCP
158158 (old option kept for backwards compatibility)
159159
160+ if dhcp is used, the client identifier can be used by following
161+ format "ip=dhcp,client-id-type,client-id-value"
162+
160163 Default: any
161164
162165 <dns0-ip> IP address of first nameserver.
Documentation/filesystems/overlayfs.txt+2−1
@@ -1,4 +1,5 @@
1−Written by: Neil Brown <neilb@suse.de>
1+Written by: Neil Brown
2+Please see MAINTAINERS file for where to send questions.
23
34 Overlay Filesystem
45 ==================
Documentation/filesystems/path-lookup.md+1297−0
@@ -0,0 +1,1297 @@
1+<head>
2+<style> p { max-width:50em} ol, ul {max-width: 40em}</style>
3+</head>
4+
5+Pathname lookup in Linux.
6+=========================
7+
8+This write-up is based on three articles published at lwn.net:
9+
10+- <https://lwn.net/Articles/649115/> Pathname lookup in Linux
11+- <https://lwn.net/Articles/649729/> RCU-walk: faster pathname lookup in Linux
12+- <https://lwn.net/Articles/650786/> A walk among the symlinks
13+
14+Written by Neil Brown with help from Al Viro and Jon Corbet.
15+
16+Introduction
17+------------
18+
19+The most obvious aspect of pathname lookup, which very little
20+exploration is needed to discover, is that it is complex. There are
21+many rules, special cases, and implementation alternatives that all
22+combine to confuse the unwary reader. Computer science has long been
23+acquainted with such complexity and has tools to help manage it. One
24+tool that we will make extensive use of is "divide and conquer". For
25+the early parts of the analysis we will divide off symlinks - leaving
26+them until the final part. Well before we get to symlinks we have
27+another major division based on the VFS's approach to locking which
28+will allow us to review "REF-walk" and "RCU-walk" separately. But we
29+are getting ahead of ourselves. There are some important low level
30+distinctions we need to clarify first.
31+
32+There are two sorts of ...
33+--------------------------
34+
35+[`openat()`]: http://man7.org/linux/man-pages/man2/openat.2.html
36+
37+Pathnames (sometimes "file names"), used to identify objects in the
38+filesystem, will be familiar to most readers. They contain two sorts
39+of elements: "slashes" that are sequences of one or more "`/`"
40+characters, and "components" that are sequences of one or more
41+non-"`/`" characters. These form two kinds of paths. Those that
42+start with slashes are "absolute" and start from the filesystem root.
43+The others are "relative" and start from the current directory, or
44+from some other location specified by a file descriptor given to a
45+"xxx`at`" system call such as "[`openat()`]".
46+
47+[`execveat()`]: http://man7.org/linux/man-pages/man2/execveat.2.html
48+
49+It is tempting to describe the second kind as starting with a
50+component, but that isn't always accurate: a pathname can lack both
51+slashes and components, it can be empty, in other words. This is
52+generally forbidden in POSIX, but some of those "xxx`at`" system calls
53+in Linux permit it when the `AT_EMPTY_PATH` flag is given. For
54+example, if you have an open file descriptor on an executable file you
55+can execute it by calling [`execveat()`] passing the file descriptor,
56+an empty path, and the `AT_EMPTY_PATH` flag.
57+
58+These paths can be divided into two sections: the final component and
59+everything else. The "everything else" is the easy bit. In all cases
60+it must identify a directory that already exists, otherwise an error
61+such as `ENOENT` or `ENOTDIR` will be reported.
62+
63+The final component is not so simple. Not only do different system
64+calls interpret it quite differently (e.g. some create it, some do
65+not), but it might not even exist: neither the empty pathname nor the
66+pathname that is just slashes have a final component. If it does
67+exist, it could be "`.`" or "`..`" which are handled quite differently
68+from other components.
69+
70+[POSIX]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12
71+
72+If a pathname ends with a slash, such as "`/tmp/foo/`" it might be
73+tempting to consider that to have an empty final component. In many
74+ways that would lead to correct results, but not always. In
75+particular, `mkdir()` and `rmdir()` each create or remove a directory named
76+by the final component, and they are required to work with pathnames
77+ending in "`/`". According to [POSIX]
78+
79+> A pathname that contains at least one non- &lt;slash> character and
80+> that ends with one or more trailing &lt;slash> characters shall not
81+> be resolved successfully unless the last pathname component before
82+> the trailing <slash> characters names an existing directory or a
83+> directory entry that is to be created for a directory immediately
84+> after the pathname is resolved.
85+
86+The Linux pathname walking code (mostly in `fs/namei.c`) deals with
87+all of these issues: breaking the path into components, handling the
88+"everything else" quite separately from the final component, and
89+checking that the trailing slash is not used where it isn't
90+permitted. It also addresses the important issue of concurrent
91+access.
92+
93+While one process is looking up a pathname, another might be making
94+changes that affect that lookup. One fairly extreme case is that if
95+"a/b" were renamed to "a/c/b" while another process were looking up
96+"a/b/..", that process might successfully resolve on "a/c".
97+Most races are much more subtle, and a big part of the task of
98+pathname lookup is to prevent them from having damaging effects. Many
99+of the possible races are seen most clearly in the context of the
100+"dcache" and an understanding of that is central to understanding
101+pathname lookup.
102+
103+More than just a cache.
104+-----------------------
105+
106+The "dcache" caches information about names in each filesystem to
107+make them quickly available for lookup. Each entry (known as a
108+"dentry") contains three significant fields: a component name, a
109+pointer to a parent dentry, and a pointer to the "inode" which
110+contains further information about the object in that parent with
111+the given name. The inode pointer can be `NULL` indicating that the
112+name doesn't exist in the parent. While there can be linkage in the
113+dentry of a directory to the dentries of the children, that linkage is
114+not used for pathname lookup, and so will not be considered here.
115+
116+The dcache has a number of uses apart from accelerating lookup. One
117+that will be particularly relevant is that it is closely integrated
118+with the mount table that records which filesystem is mounted where.
119+What the mount table actually stores is which dentry is mounted on top
120+of which other dentry.
121+
122+When considering the dcache, we have another of our "two types"
123+distinctions: there are two types of filesystems.
124+
125+Some filesystems ensure that the information in the dcache is always
126+completely accurate (though not necessarily complete). This can allow
127+the VFS to determine if a particular file does or doesn't exist
128+without checking with the filesystem, and means that the VFS can
129+protect the filesystem against certain races and other problems.
130+These are typically "local" filesystems such as ext3, XFS, and Btrfs.
131+
132+Other filesystems don't provide that guarantee because they cannot.
133+These are typically filesystems that are shared across a network,
134+whether remote filesystems like NFS and 9P, or cluster filesystems
135+like ocfs2 or cephfs. These filesystems allow the VFS to revalidate
136+cached information, and must provide their own protection against
137+awkward races. The VFS can detect these filesystems by the
138+`DCACHE_OP_REVALIDATE` flag being set in the dentry.
139+
140+REF-walk: simple concurrency management with refcounts and spinlocks
141+--------------------------------------------------------------------
142+
143+With all of those divisions carefully classified, we can now start
144+looking at the actual process of walking along a path. In particular
145+we will start with the handling of the "everything else" part of a
146+pathname, and focus on the "REF-walk" approach to concurrency
147+management. This code is found in the `link_path_walk()` function, if
148+you ignore all the places that only run when "`LOOKUP_RCU`"
149+(indicating the use of RCU-walk) is set.
150+
151+[Meet the Lockers]: https://lwn.net/Articles/453685/
152+
153+REF-walk is fairly heavy-handed with locks and reference counts. Not
154+as heavy-handed as in the old "big kernel lock" days, but certainly not
155+afraid of taking a lock when one is needed. It uses a variety of
156+different concurrency controls. A background understanding of the
157+various primitives is assumed, or can be gleaned from elsewhere such
158+as in [Meet the Lockers].
159+
160+The locking mechanisms used by REF-walk include:
161+
162+### dentry->d_lockref ###
163+
164+This uses the lockref primitive to provide both a spinlock and a
165+reference count. The special-sauce of this primitive is that the
166+conceptual sequence "lock; inc_ref; unlock;" can often be performed
167+with a single atomic memory operation.
168+
169+Holding a reference on a dentry ensures that the dentry won't suddenly
170+be freed and used for something else, so the values in various fields
171+will behave as expected. It also protects the `->d_inode` reference
172+to the inode to some extent.
173+
174+The association between a dentry and its inode is fairly permanent.
175+For example, when a file is renamed, the dentry and inode move
176+together to the new location. When a file is created the dentry will
177+initially be negative (i.e. `d_inode` is `NULL`), and will be assigned
178+to the new inode as part of the act of creation.
179+
180+When a file is deleted, this can be reflected in the cache either by
181+setting `d_inode` to `NULL`, or by removing it from the hash table
182+(described shortly) used to look up the name in the parent directory.
183+If the dentry is still in use the second option is used as it is
184+perfectly legal to keep using an open file after it has been deleted
185+and having the dentry around helps. If the dentry is not otherwise in
186+use (i.e. if the refcount in `d_lockref` is one), only then will
187+`d_inode` be set to `NULL`. Doing it this way is more efficient for a
188+very common case.
189+
190+So as long as a counted reference is held to a dentry, a non-`NULL` `->d_inode`
191+value will never be changed.
192+
193+### dentry->d_lock ###
194+
195+`d_lock` is a synonym for the spinlock that is part of `d_lockref` above.
196+For our purposes, holding this lock protects against the dentry being
197+renamed or unlinked. In particular, its parent (`d_parent`), and its
198+name (`d_name`) cannot be changed, and it cannot be removed from the
199+dentry hash table.
200+
201+When looking for a name in a directory, REF-walk takes `d_lock` on
202+each candidate dentry that it finds in the hash table and then checks
203+that the parent and name are correct. So it doesn't lock the parent
204+while searching in the cache; it only locks children.
205+
206+When looking for the parent for a given name (to handle "`..`"),
207+REF-walk can take `d_lock` to get a stable reference to `d_parent`,
208+but it first tries a more lightweight approach. As seen in
209+`dget_parent()`, if a reference can be claimed on the parent, and if
210+subsequently `d_parent` can be seen to have not changed, then there is
211+no need to actually take the lock on the child.
212+
213+### rename_lock ###
214+
215+Looking up a given name in a given directory involves computing a hash
216+from the two values (the name and the dentry of the directory),
217+accessing that slot in a hash table, and searching the linked list
218+that is found there.
219+
220+When a dentry is renamed, the name and the parent dentry can both
221+change so the hash will almost certainly change too. This would move the
222+dentry to a different chain in the hash table. If a filename search
223+happened to be looking at a dentry that was moved in this way,
224+it might end up continuing the search down the wrong chain,
225+and so miss out on part of the correct chain.
226+
227+The name-lookup process (`d_lookup()`) does _not_ try to prevent this
228+from happening, but only to detect when it happens.
229+`rename_lock` is a seqlock that is updated whenever any dentry is
230+renamed. If `d_lookup` finds that a rename happened while it
231+unsuccessfully scanned a chain in the hash table, it simply tries
232+again.
233+
234+### inode->i_mutex ###
235+
236+`i_mutex` is a mutex that serializes all changes to a particular
237+directory. This ensures that, for example, an `unlink()` and a `rename()`
238+cannot both happen at the same time. It also keeps the directory
239+stable while the filesystem is asked to look up a name that is not
240+currently in the dcache.
241+
242+This has a complementary role to that of `d_lock`: `i_mutex` on a
243+directory protects all of the names in that directory, while `d_lock`
244+on a name protects just one name in a directory. Most changes to the
245+dcache hold `i_mutex` on the relevant directory inode and briefly take
246+`d_lock` on one or more the dentries while the change happens. One
247+exception is when idle dentries are removed from the dcache due to
248+memory pressure. This uses `d_lock`, but `i_mutex` plays no role.
249+
250+The mutex affects pathname lookup in two distinct ways. Firstly it
251+serializes lookup of a name in a directory. `walk_component()` uses
252+`lookup_fast()` first which, in turn, checks to see if the name is in the cache,
253+using only `d_lock` locking. If the name isn't found, then `walk_component()`
254+falls back to `lookup_slow()` which takes `i_mutex`, checks again that
255+the name isn't in the cache, and then calls in to the filesystem to get a
256+definitive answer. A new dentry will be added to the cache regardless of
257+the result.
258+
259+Secondly, when pathname lookup reaches the final component, it will
260+sometimes need to take `i_mutex` before performing the last lookup so
261+that the required exclusion can be achieved. How path lookup chooses
262+to take, or not take, `i_mutex` is one of the
263+issues addressed in a subsequent section.
264+
265+### mnt->mnt_count ###
266+
267+`mnt_count` is a per-CPU reference counter on "`mount`" structures.
268+Per-CPU here means that incrementing the count is cheap as it only
269+uses CPU-local memory, but checking if the count is zero is expensive as
270+it needs to check with every CPU. Taking a `mnt_count` reference
271+prevents the mount structure from disappearing as the result of regular
272+unmount operations, but does not prevent a "lazy" unmount. So holding
273+`mnt_count` doesn't ensure that the mount remains in the namespace and,
274+in particular, doesn't stabilize the link to the mounted-on dentry. It
275+does, however, ensure that the `mount` data structure remains coherent,
276+and it provides a reference to the root dentry of the mounted
277+filesystem. So a reference through `->mnt_count` provides a stable
278+reference to the mounted dentry, but not the mounted-on dentry.
279+
280+### mount_lock ###
281+
282+`mount_lock` is a global seqlock, a bit like `rename_lock`. It can be used to
283+check if any change has been made to any mount points.
284+
285+While walking down the tree (away from the root) this lock is used when
286+crossing a mount point to check that the crossing was safe. That is,
287+the value in the seqlock is read, then the code finds the mount that
288+is mounted on the current directory, if there is one, and increments
289+the `mnt_count`. Finally the value in `mount_lock` is checked against
290+the old value. If there is no change, then the crossing was safe. If there
291+was a change, the `mnt_count` is decremented and the whole process is
292+retried.
293+
294+When walking up the tree (towards the root) by following a ".." link,
295+a little more care is needed. In this case the seqlock (which
296+contains both a counter and a spinlock) is fully locked to prevent
297+any changes to any mount points while stepping up. This locking is
298+needed to stabilize the link to the mounted-on dentry, which the
299+refcount on the mount itself doesn't ensure.
300+
301+### RCU ###
302+
303+Finally the global (but extremely lightweight) RCU read lock is held
304+from time to time to ensure certain data structures don't get freed
305+unexpectedly.
306+
307+In particular it is held while scanning chains in the dcache hash
308+table, and the mount point hash table.
309+
310+Bringing it together with `struct nameidata`
311+--------------------------------------------
312+
313+[First edition Unix]: http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/u2.s
314+
315+Throughout the process of walking a path, the current status is stored
316+in a `struct nameidata`, "namei" being the traditional name - dating
317+all the way back to [First Edition Unix] - of the function that
318+converts a "name" to an "inode". `struct nameidata` contains (among
319+other fields):
320+
321+### `struct path path` ###
322+
323+A `path` contains a `struct vfsmount` (which is
324+embedded in a `struct mount`) and a `struct dentry`. Together these
325+record the current status of the walk. They start out referring to the
326+starting point (the current working directory, the root directory, or some other
327+directory identified by a file descriptor), and are updated on each
328+step. A reference through `d_lockref` and `mnt_count` is always
329+held.
330+
331+### `struct qstr last` ###
332+
333+This is a string together with a length (i.e. _not_ `nul` terminated)
334+that is the "next" component in the pathname.
335+
336+### `int last_type` ###
337+
338+This is one of `LAST_NORM`, `LAST_ROOT`, `LAST_DOT`, `LAST_DOTDOT`, or
339+`LAST_BIND`. The `last` field is only valid if the type is
340+`LAST_NORM`. `LAST_BIND` is used when following a symlink and no
341+components of the symlink have been processed yet. Others should be
342+fairly self-explanatory.
343+
344+### `struct path root` ###
345+
346+This is used to hold a reference to the effective root of the
347+filesystem. Often that reference won't be needed, so this field is
348+only assigned the first time it is used, or when a non-standard root
349+is requested. Keeping a reference in the `nameidata` ensures that
350+only one root is in effect for the entire path walk, even if it races
351+with a `chroot()` system call.
352+
353+The root is needed when either of two conditions holds: (1) either the
354+pathname or a symbolic link starts with a "'/'", or (2) a "`..`"
355+component is being handled, since "`..`" from the root must always stay
356+at the root. The value used is usually the current root directory of
357+the calling process. An alternate root can be provided as when
358+`sysctl()` calls `file_open_root()`, and when NFSv4 or Btrfs call
359+`mount_subtree()`. In each case a pathname is being looked up in a very
360+specific part of the filesystem, and the lookup must not be allowed to
361+escape that subtree. It works a bit like a local `chroot()`.
362+
363+Ignoring the handling of symbolic links, we can now describe the
364+"`link_path_walk()`" function, which handles the lookup of everything
365+except the final component as:
366+
367+> Given a path (`name`) and a nameidata structure (`nd`), check that the
368+> current directory has execute permission and then advance `name`
369+> over one component while updating `last_type` and `last`. If that
370+> was the final component, then return, otherwise call
371+> `walk_component()` and repeat from the top.
372+
373+`walk_component()` is even easier. If the component is `LAST_DOTS`,
374+it calls `handle_dots()` which does the necessary locking as already
375+described. If it finds a `LAST_NORM` component it first calls
376+"`lookup_fast()`" which only looks in the dcache, but will ask the
377+filesystem to revalidate the result if it is that sort of filesystem.
378+If that doesn't get a good result, it calls "`lookup_slow()`" which
379+takes the `i_mutex`, rechecks the cache, and then asks the filesystem
380+to find a definitive answer. Each of these will call
381+`follow_managed()` (as described below) to handle any mount points.
382+
383+In the absence of symbolic links, `walk_component()` creates a new
384+`struct path` containing a counted reference to the new dentry and a
385+reference to the new `vfsmount` which is only counted if it is
386+different from the previous `vfsmount`. It then calls
387+`path_to_nameidata()` to install the new `struct path` in the
388+`struct nameidata` and drop the unneeded references.
389+
390+This "hand-over-hand" sequencing of getting a reference to the new
391+dentry before dropping the reference to the previous dentry may
392+seem obvious, but is worth pointing out so that we will recognize its
393+analogue in the "RCU-walk" version.
394+
395+Handling the final component.
396+-----------------------------
397+
398+`link_path_walk()` only walks as far as setting `nd->last` and
399+`nd->last_type` to refer to the final component of the path. It does
400+not call `walk_component()` that last time. Handling that final
401+component remains for the caller to sort out. Those callers are
402+`path_lookupat()`, `path_parentat()`, `path_mountpoint()` and
403+`path_openat()` each of which handles the differing requirements of
404+different system calls.
405+
406+`path_parentat()` is clearly the simplest - it just wraps a little bit
407+of housekeeping around `link_path_walk()` and returns the parent
408+directory and final component to the caller. The caller will be either
409+aiming to create a name (via `filename_create()`) or remove or rename
410+a name (in which case `user_path_parent()` is used). They will use
411+`i_mutex` to exclude other changes while they validate and then
412+perform their operation.
413+
414+`path_lookupat()` is nearly as simple - it is used when an existing
415+object is wanted such as by `stat()` or `chmod()`. It essentially just
416+calls `walk_component()` on the final component through a call to
417+`lookup_last()`. `path_lookupat()` returns just the final dentry.
418+
419+`path_mountpoint()` handles the special case of unmounting which must
420+not try to revalidate the mounted filesystem. It effectively
421+contains, through a call to `mountpoint_last()`, an alternate
422+implementation of `lookup_slow()` which skips that step. This is
423+important when unmounting a filesystem that is inaccessible, such as
424+one provided by a dead NFS server.
425+
426+Finally `path_openat()` is used for the `open()` system call; it
427+contains, in support functions starting with "`do_last()`", all the
428+complexity needed to handle the different subtleties of O_CREAT (with
429+or without O_EXCL), final "`/`" characters, and trailing symbolic
430+links. We will revisit this in the final part of this series, which
431+focuses on those symbolic links. "`do_last()`" will sometimes, but
432+not always, take `i_mutex`, depending on what it finds.
433+
434+Each of these, or the functions which call them, need to be alert to
435+the possibility that the final component is not `LAST_NORM`. If the
436+goal of the lookup is to create something, then any value for
437+`last_type` other than `LAST_NORM` will result in an error. For
438+example if `path_parentat()` reports `LAST_DOTDOT`, then the caller
439+won't try to create that name. They also check for trailing slashes
440+by testing `last.name[last.len]`. If there is any character beyond
441+the final component, it must be a trailing slash.
442+
443+Revalidation and automounts
444+---------------------------
445+
446+Apart from symbolic links, there are only two parts of the "REF-walk"
447+process not yet covered. One is the handling of stale cache entries
448+and the other is automounts.
449+
450+On filesystems that require it, the lookup routines will call the
451+`->d_revalidate()` dentry method to ensure that the cached information
452+is current. This will often confirm validity or update a few details
453+from a server. In some cases it may find that there has been change
454+further up the path and that something that was thought to be valid
455+previously isn't really. When this happens the lookup of the whole
456+path is aborted and retried with the "`LOOKUP_REVAL`" flag set. This
457+forces revalidation to be more thorough. We will see more details of
458+this retry process in the next article.
459+
460+Automount points are locations in the filesystem where an attempt to
461+lookup a name can trigger changes to how that lookup should be
462+handled, in particular by mounting a filesystem there. These are
463+covered in greater detail in autofs4.txt in the Linux documentation
464+tree, but a few notes specifically related to path lookup are in order
465+here.
466+
467+The Linux VFS has a concept of "managed" dentries which is reflected
468+in function names such as "`follow_managed()`". There are three
469+potentially interesting things about these dentries corresponding
470+to three different flags that might be set in `dentry->d_flags`:
471+
472+### `DCACHE_MANAGE_TRANSIT` ###
473+
474+If this flag has been set, then the filesystem has requested that the
475+`d_manage()` dentry operation be called before handling any possible
476+mount point. This can perform two particular services:
477+
478+It can block to avoid races. If an automount point is being
479+unmounted, the `d_manage()` function will usually wait for that
480+process to complete before letting the new lookup proceed and possibly
481+trigger a new automount.
482+
483+It can selectively allow only some processes to transit through a
484+mount point. When a server process is managing automounts, it may
485+need to access a directory without triggering normal automount
486+processing. That server process can identify itself to the `autofs`
487+filesystem, which will then give it a special pass through
488+`d_manage()` by returning `-EISDIR`.
489+
490+### `DCACHE_MOUNTED` ###
491+
492+This flag is set on every dentry that is mounted on. As Linux
493+supports multiple filesystem namespaces, it is possible that the
494+dentry may not be mounted on in *this* namespace, just in some
495+other. So this flag is seen as a hint, not a promise.
496+
497+If this flag is set, and `d_manage()` didn't return `-EISDIR`,
498+`lookup_mnt()` is called to examine the mount hash table (honoring the
499+`mount_lock` described earlier) and possibly return a new `vfsmount`
500+and a new `dentry` (both with counted references).
501+
502+### `DCACHE_NEED_AUTOMOUNT` ###
503+
504+If `d_manage()` allowed us to get this far, and `lookup_mnt()` didn't
505+find a mount point, then this flag causes the `d_automount()` dentry
506+operation to be called.
507+
508+The `d_automount()` operation can be arbitrarily complex and may
509+communicate with server processes etc. but it should ultimately either
510+report that there was an error, that there was nothing to mount, or
511+should provide an updated `struct path` with new `dentry` and `vfsmount`.
512+
513+In the latter case, `finish_automount()` will be called to safely
514+install the new mount point into the mount table.
515+
516+There is no new locking of import here and it is important that no
517+locks (only counted references) are held over this processing due to
518+the very real possibility of extended delays.
519+This will become more important next time when we examine RCU-walk
520+which is particularly sensitive to delays.
521+
522+RCU-walk - faster pathname lookup in Linux
523+==========================================
524+
525+RCU-walk is another algorithm for performing pathname lookup in Linux.
526+It is in many ways similar to REF-walk and the two share quite a bit
527+of code. The significant difference in RCU-walk is how it allows for
528+the possibility of concurrent access.
529+
530+We noted that REF-walk is complex because there are numerous details
531+and special cases. RCU-walk reduces this complexity by simply
532+refusing to handle a number of cases -- it instead falls back to
533+REF-walk. The difficulty with RCU-walk comes from a different
534+direction: unfamiliarity. The locking rules when depending on RCU are
535+quite different from traditional locking, so we will spend a little extra
536+time when we come to those.
537+
538+Clear demarcation of roles
539+--------------------------
540+
541+The easiest way to manage concurrency is to forcibly stop any other
542+thread from changing the data structures that a given thread is
543+looking at. In cases where no other thread would even think of
544+changing the data and lots of different threads want to read at the
545+same time, this can be very costly. Even when using locks that permit
546+multiple concurrent readers, the simple act of updating the count of
547+the number of current readers can impose an unwanted cost. So the
548+goal when reading a shared data structure that no other process is
549+changing is to avoid writing anything to memory at all. Take no
550+locks, increment no counts, leave no footprints.
551+
552+The REF-walk mechanism already described certainly doesn't follow this
553+principle, but then it is really designed to work when there may well
554+be other threads modifying the data. RCU-walk, in contrast, is
555+designed for the common situation where there are lots of frequent
556+readers and only occasional writers. This may not be common in all
557+parts of the filesystem tree, but in many parts it will be. For the
558+other parts it is important that RCU-walk can quickly fall back to
559+using REF-walk.
560+
561+Pathname lookup always starts in RCU-walk mode but only remains there
562+as long as what it is looking for is in the cache and is stable. It
563+dances lightly down the cached filesystem image, leaving no footprints
564+and carefully watching where it is, to be sure it doesn't trip. If it
565+notices that something has changed or is changing, or if something
566+isn't in the cache, then it tries to stop gracefully and switch to
567+REF-walk.
568+
569+This stopping requires getting a counted reference on the current
570+`vfsmount` and `dentry`, and ensuring that these are still valid -
571+that a path walk with REF-walk would have found the same entries.
572+This is an invariant that RCU-walk must guarantee. It can only make
573+decisions, such as selecting the next step, that are decisions which
574+REF-walk could also have made if it were walking down the tree at the
575+same time. If the graceful stop succeeds, the rest of the path is
576+processed with the reliable, if slightly sluggish, REF-walk. If
577+RCU-walk finds it cannot stop gracefully, it simply gives up and
578+restarts from the top with REF-walk.
579+
580+This pattern of "try RCU-walk, if that fails try REF-walk" can be
581+clearly seen in functions like `filename_lookup()`,
582+`filename_parentat()`, `filename_mountpoint()`,
583+`do_filp_open()`, and `do_file_open_root()`. These five
584+correspond roughly to the four `path_`* functions we met earlier,
585+each of which calls `link_path_walk()`. The `path_*` functions are
586+called using different mode flags until a mode is found which works.
587+They are first called with `LOOKUP_RCU` set to request "RCU-walk". If
588+that fails with the error `ECHILD` they are called again with no
589+special flag to request "REF-walk". If either of those report the
590+error `ESTALE` a final attempt is made with `LOOKUP_REVAL` set (and no
591+`LOOKUP_RCU`) to ensure that entries found in the cache are forcibly
592+revalidated - normally entries are only revalidated if the filesystem
593+determines that they are too old to trust.
594+
595+The `LOOKUP_RCU` attempt may drop that flag internally and switch to
596+REF-walk, but will never then try to switch back to RCU-walk. Places
597+that trip up RCU-walk are much more likely to be near the leaves and
598+so it is very unlikely that there will be much, if any, benefit from
599+switching back.
600+
601+RCU and seqlocks: fast and light
602+--------------------------------
603+
604+RCU is, unsurprisingly, critical to RCU-walk mode. The
605+`rcu_read_lock()` is held for the entire time that RCU-walk is walking
606+down a path. The particular guarantee it provides is that the key
607+data structures - dentries, inodes, super_blocks, and mounts - will
608+not be freed while the lock is held. They might be unlinked or
609+invalidated in one way or another, but the memory will not be
610+repurposed so values in various fields will still be meaningful. This
611+is the only guarantee that RCU provides; everything else is done using
612+seqlocks.
613+
614+As we saw above, REF-walk holds a counted reference to the current
615+dentry and the current vfsmount, and does not release those references
616+before taking references to the "next" dentry or vfsmount. It also
617+sometimes takes the `d_lock` spinlock. These references and locks are
618+taken to prevent certain changes from happening. RCU-walk must not
619+take those references or locks and so cannot prevent such changes.
620+Instead, it checks to see if a change has been made, and aborts or
621+retries if it has.
622+
623+To preserve the invariant mentioned above (that RCU-walk may only make
624+decisions that REF-walk could have made), it must make the checks at
625+or near the same places that REF-walk holds the references. So, when
626+REF-walk increments a reference count or takes a spinlock, RCU-walk
627+samples the status of a seqlock using `read_seqcount_begin()` or a
628+similar function. When REF-walk decrements the count or drops the
629+lock, RCU-walk checks if the sampled status is still valid using
630+`read_seqcount_retry()` or similar.
631+
632+However, there is a little bit more to seqlocks than that. If
633+RCU-walk accesses two different fields in a seqlock-protected
634+structure, or accesses the same field twice, there is no a priori
635+guarantee of any consistency between those accesses. When consistency
636+is needed - which it usually is - RCU-walk must take a copy and then
637+use `read_seqcount_retry()` to validate that copy.
638+
639+`read_seqcount_retry()` not only checks the sequence number, but also
640+imposes a memory barrier so that no memory-read instruction from
641+*before* the call can be delayed until *after* the call, either by the
642+CPU or by the compiler. A simple example of this can be seen in
643+`slow_dentry_cmp()` which, for filesystems which do not use simple
644+byte-wise name equality, calls into the filesystem to compare a name
645+against a dentry. The length and name pointer are copied into local
646+variables, then `read_seqcount_retry()` is called to confirm the two
647+are consistent, and only then is `->d_compare()` called. When
648+standard filename comparison is used, `dentry_cmp()` is called
649+instead. Notably it does _not_ use `read_seqcount_retry()`, but
650+instead has a large comment explaining why the consistency guarantee
651+isn't necessary. A subsequent `read_seqcount_retry()` will be
652+sufficient to catch any problem that could occur at this point.
653+
654+With that little refresher on seqlocks out of the way we can look at
655+the bigger picture of how RCU-walk uses seqlocks.
656+
657+### `mount_lock` and `nd->m_seq` ###
658+
659+We already met the `mount_lock` seqlock when REF-walk used it to
660+ensure that crossing a mount point is performed safely. RCU-walk uses
661+it for that too, but for quite a bit more.
662+
663+Instead of taking a counted reference to each `vfsmount` as it
664+descends the tree, RCU-walk samples the state of `mount_lock` at the
665+start of the walk and stores this initial sequence number in the
666+`struct nameidata` in the `m_seq` field. This one lock and one
667+sequence number are used to validate all accesses to all `vfsmounts`,
668+and all mount point crossings. As changes to the mount table are
669+relatively rare, it is reasonable to fall back on REF-walk any time
670+that any "mount" or "unmount" happens.
671+
672+`m_seq` is checked (using `read_seqretry()`) at the end of an RCU-walk
673+sequence, whether switching to REF-walk for the rest of the path or
674+when the end of the path is reached. It is also checked when stepping
675+down over a mount point (in `__follow_mount_rcu()`) or up (in
676+`follow_dotdot_rcu()`). If it is ever found to have changed, the
677+whole RCU-walk sequence is aborted and the path is processed again by
678+REF-walk.
679+
680+If RCU-walk finds that `mount_lock` hasn't changed then it can be sure
681+that, had REF-walk taken counted references on each vfsmount, the
682+results would have been the same. This ensures the invariant holds,
683+at least for vfsmount structures.
684+
685+### `dentry->d_seq` and `nd->seq`. ###
686+
687+In place of taking a count or lock on `d_reflock`, RCU-walk samples
688+the per-dentry `d_seq` seqlock, and stores the sequence number in the
689+`seq` field of the nameidata structure, so `nd->seq` should always be
690+the current sequence number of `nd->dentry`. This number needs to be
691+revalidated after copying, and before using, the name, parent, or
692+inode of the dentry.
693+
694+The handling of the name we have already looked at, and the parent is
695+only accessed in `follow_dotdot_rcu()` which fairly trivially follows
696+the required pattern, though it does so for three different cases.
697+
698+When not at a mount point, `d_parent` is followed and its `d_seq` is
699+collected. When we are at a mount point, we instead follow the
700+`mnt->mnt_mountpoint` link to get a new dentry and collect its
701+`d_seq`. Then, after finally finding a `d_parent` to follow, we must
702+check if we have landed on a mount point and, if so, must find that
703+mount point and follow the `mnt->mnt_root` link. This would imply a
704+somewhat unusual, but certainly possible, circumstance where the
705+starting point of the path lookup was in part of the filesystem that
706+was mounted on, and so not visible from the root.
707+
708+The inode pointer, stored in `->d_inode`, is a little more
709+interesting. The inode will always need to be accessed at least
710+twice, once to determine if it is NULL and once to verify access
711+permissions. Symlink handling requires a validated inode pointer too.
712+Rather than revalidating on each access, a copy is made on the first
713+access and it is stored in the `inode` field of `nameidata` from where
714+it can be safely accessed without further validation.
715+
716+`lookup_fast()` is the only lookup routine that is used in RCU-mode,
717+`lookup_slow()` being too slow and requiring locks. It is in
718+`lookup_fast()` that we find the important "hand over hand" tracking
719+of the current dentry.
720+
721+The current `dentry` and current `seq` number are passed to
722+`__d_lookup_rcu()` which, on success, returns a new `dentry` and a
723+new `seq` number. `lookup_fast()` then copies the inode pointer and
724+revalidates the new `seq` number. It then validates the old `dentry`
725+with the old `seq` number one last time and only then continues. This
726+process of getting the `seq` number of the new dentry and then
727+checking the `seq` number of the old exactly mirrors the process of
728+getting a counted reference to the new dentry before dropping that for
729+the old dentry which we saw in REF-walk.
730+
731+### No `inode->i_mutex` or even `rename_lock` ###
732+
733+A mutex is a fairly heavyweight lock that can only be taken when it is
734+permissible to sleep. As `rcu_read_lock()` forbids sleeping,
735+`inode->i_mutex` plays no role in RCU-walk. If some other thread does
736+take `i_mutex` and modifies the directory in a way that RCU-walk needs
737+to notice, the result will be either that RCU-walk fails to find the
738+dentry that it is looking for, or it will find a dentry which
739+`read_seqretry()` won't validate. In either case it will drop down to
740+REF-walk mode which can take whatever locks are needed.
741+
742+Though `rename_lock` could be used by RCU-walk as it doesn't require
743+any sleeping, RCU-walk doesn't bother. REF-walk uses `rename_lock` to
744+protect against the possibility of hash chains in the dcache changing
745+while they are being searched. This can result in failing to find
746+something that actually is there. When RCU-walk fails to find
747+something in the dentry cache, whether it is really there or not, it
748+already drops down to REF-walk and tries again with appropriate
749+locking. This neatly handles all cases, so adding extra checks on
750+rename_lock would bring no significant value.
751+
752+`unlazy walk()` and `complete_walk()`
753+-------------------------------------
754+
755+That "dropping down to REF-walk" typically involves a call to
756+`unlazy_walk()`, so named because "RCU-walk" is also sometimes
757+referred to as "lazy walk". `unlazy_walk()` is called when
758+following the path down to the current vfsmount/dentry pair seems to
759+have proceeded successfully, but the next step is problematic. This
760+can happen if the next name cannot be found in the dcache, if
761+permission checking or name revalidation couldn't be achieved while
762+the `rcu_read_lock()` is held (which forbids sleeping), if an
763+automount point is found, or in a couple of cases involving symlinks.
764+It is also called from `complete_walk()` when the lookup has reached
765+the final component, or the very end of the path, depending on which
766+particular flavor of lookup is used.
767+
768+Other reasons for dropping out of RCU-walk that do not trigger a call
769+to `unlazy_walk()` are when some inconsistency is found that cannot be
770+handled immediately, such as `mount_lock` or one of the `d_seq`
771+seqlocks reporting a change. In these cases the relevant function
772+will return `-ECHILD` which will percolate up until it triggers a new
773+attempt from the top using REF-walk.
774+
775+For those cases where `unlazy_walk()` is an option, it essentially
776+takes a reference on each of the pointers that it holds (vfsmount,
777+dentry, and possibly some symbolic links) and then verifies that the
778+relevant seqlocks have not been changed. If there have been changes,
779+it, too, aborts with `-ECHILD`, otherwise the transition to REF-walk
780+has been a success and the lookup process continues.
781+
782+Taking a reference on those pointers is not quite as simple as just
783+incrementing a counter. That works to take a second reference if you
784+already have one (often indirectly through another object), but it
785+isn't sufficient if you don't actually have a counted reference at
786+all. For `dentry->d_lockref`, it is safe to increment the reference
787+counter to get a reference unless it has been explicitly marked as
788+"dead" which involves setting the counter to `-128`.
789+`lockref_get_not_dead()` achieves this.
790+
791+For `mnt->mnt_count` it is safe to take a reference as long as
792+`mount_lock` is then used to validate the reference. If that
793+validation fails, it may *not* be safe to just drop that reference in
794+the standard way of calling `mnt_put()` - an unmount may have
795+progressed too far. So the code in `legitimize_mnt()`, when it
796+finds that the reference it got might not be safe, checks the
797+`MNT_SYNC_UMOUNT` flag to determine if a simple `mnt_put()` is
798+correct, or if it should just decrement the count and pretend none of
799+this ever happened.
800+
801+Taking care in filesystems
802+---------------------------
803+
804+RCU-walk depends almost entirely on cached information and often will
805+not call into the filesystem at all. However there are two places,
806+besides the already-mentioned component-name comparison, where the
807+file system might be included in RCU-walk, and it must know to be
808+careful.
809+
810+If the filesystem has non-standard permission-checking requirements -
811+such as a networked filesystem which may need to check with the server
812+- the `i_op->permission` interface might be called during RCU-walk.
813+In this case an extra "`MAY_NOT_BLOCK`" flag is passed so that it
814+knows not to sleep, but to return `-ECHILD` if it cannot complete
815+promptly. `i_op->permission` is given the inode pointer, not the
816+dentry, so it doesn't need to worry about further consistency checks.
817+However if it accesses any other filesystem data structures, it must
818+ensure they are safe to be accessed with only the `rcu_read_lock()`
819+held. This typically means they must be freed using `kfree_rcu()` or
820+similar.
821+
822+[`READ_ONCE()`]: https://lwn.net/Articles/624126/
823+
824+If the filesystem may need to revalidate dcache entries, then
825+`d_op->d_revalidate` may be called in RCU-walk too. This interface
826+*is* passed the dentry but does not have access to the `inode` or the
827+`seq` number from the `nameidata`, so it needs to be extra careful
828+when accessing fields in the dentry. This "extra care" typically
829+involves using `ACCESS_ONCE()` or the newer [`READ_ONCE()`] to access
830+fields, and verifying the result is not NULL before using it. This
831+pattern can be see in `nfs_lookup_revalidate()`.
832+
833+A pair of patterns
834+------------------
835+
836+In various places in the details of REF-walk and RCU-walk, and also in
837+the big picture, there are a couple of related patterns that are worth
838+being aware of.
839+
840+The first is "try quickly and check, if that fails try slowly". We
841+can see that in the high-level approach of first trying RCU-walk and
842+then trying REF-walk, and in places where `unlazy_walk()` is used to
843+switch to REF-walk for the rest of the path. We also saw it earlier
844+in `dget_parent()` when following a "`..`" link. It tries a quick way
845+to get a reference, then falls back to taking locks if needed.
846+
847+The second pattern is "try quickly and check, if that fails try
848+again - repeatedly". This is seen with the use of `rename_lock` and
849+`mount_lock` in REF-walk. RCU-walk doesn't make use of this pattern -
850+if anything goes wrong it is much safer to just abort and try a more
851+sedate approach.
852+
853+The emphasis here is "try quickly and check". It should probably be
854+"try quickly _and carefully,_ then check". The fact that checking is
855+needed is a reminder that the system is dynamic and only a limited
856+number of things are safe at all. The most likely cause of errors in
857+this whole process is assuming something is safe when in reality it
858+isn't. Careful consideration of what exactly guarantees the safety of
859+each access is sometimes necessary.
860+
861+A walk among the symlinks
862+=========================
863+
864+There are several basic issues that we will examine to understand the
865+handling of symbolic links: the symlink stack, together with cache
866+lifetimes, will help us understand the overall recursive handling of
867+symlinks and lead to the special care needed for the final component.
868+Then a consideration of access-time updates and summary of the various
869+flags controlling lookup will finish the story.
870+
871+The symlink stack
872+-----------------
873+
874+There are only two sorts of filesystem objects that can usefully
875+appear in a path prior to the final component: directories and symlinks.
876+Handling directories is quite straightforward: the new directory
877+simply becomes the starting point at which to interpret the next
878+component on the path. Handling symbolic links requires a bit more
879+work.
880+
881+Conceptually, symbolic links could be handled by editing the path. If
882+a component name refers to a symbolic link, then that component is
883+replaced by the body of the link and, if that body starts with a '/',
884+then all preceding parts of the path are discarded. This is what the
885+"`readlink -f`" command does, though it also edits out "`.`" and
886+"`..`" components.
887+
888+Directly editing the path string is not really necessary when looking
889+up a path, and discarding early components is pointless as they aren't
890+looked at anyway. Keeping track of all remaining components is
891+important, but they can of course be kept separately; there is no need
892+to concatenate them. As one symlink may easily refer to another,
893+which in turn can refer to a third, we may need to keep the remaining
894+components of several paths, each to be processed when the preceding
895+ones are completed. These path remnants are kept on a stack of
896+limited size.
897+
898+There are two reasons for placing limits on how many symlinks can
899+occur in a single path lookup. The most obvious is to avoid loops.
900+If a symlink referred to itself either directly or through
901+intermediaries, then following the symlink can never complete
902+successfully - the error `ELOOP` must be returned. Loops can be
903+detected without imposing limits, but limits are the simplest solution
904+and, given the second reason for restriction, quite sufficient.
905+
906+[outlined recently]: http://thread.gmane.org/gmane.linux.kernel/1934390/focus=1934550
907+
908+The second reason was [outlined recently] by Linus:
909+
910+> Because it's a latency and DoS issue too. We need to react well to
911+> true loops, but also to "very deep" non-loops. It's not about memory
912+> use, it's about users triggering unreasonable CPU resources.
913+
914+Linux imposes a limit on the length of any pathname: `PATH_MAX`, which
915+is 4096. There are a number of reasons for this limit; not letting the
916+kernel spend too much time on just one path is one of them. With
917+symbolic links you can effectively generate much longer paths so some
918+sort of limit is needed for the same reason. Linux imposes a limit of
919+at most 40 symlinks in any one path lookup. It previously imposed a
920+further limit of eight on the maximum depth of recursion, but that was
921+raised to 40 when a separate stack was implemented, so there is now
922+just the one limit.
923+
924+The `nameidata` structure that we met in an earlier article contains a
925+small stack that can be used to store the remaining part of up to two
926+symlinks. In many cases this will be sufficient. If it isn't, a
927+separate stack is allocated with room for 40 symlinks. Pathname
928+lookup will never exceed that stack as, once the 40th symlink is
929+detected, an error is returned.
930+
931+It might seem that the name remnants are all that needs to be stored on
932+this stack, but we need a bit more. To see that, we need to move on to
933+cache lifetimes.
934+
935+Storage and lifetime of cached symlinks
936+---------------------------------------
937+
938+Like other filesystem resources, such as inodes and directory
939+entries, symlinks are cached by Linux to avoid repeated costly access
940+to external storage. It is particularly important for RCU-walk to be
941+able to find and temporarily hold onto these cached entries, so that
942+it doesn't need to drop down into REF-walk.
943+
944+[object-oriented design pattern]: https://lwn.net/Articles/446317/
945+
946+While each filesystem is free to make its own choice, symlinks are
947+typically stored in one of two places. Short symlinks are often
948+stored directly in the inode. When a filesystem allocates a `struct
949+inode` it typically allocates extra space to store private data (a
950+common [object-oriented design pattern] in the kernel). This will
951+sometimes include space for a symlink. The other common location is
952+in the page cache, which normally stores the content of files. The
953+pathname in a symlink can be seen as the content of that symlink and
954+can easily be stored in the page cache just like file content.
955+
956+When neither of these is suitable, the next most likely scenario is
957+that the filesystem will allocate some temporary memory and copy or
958+construct the symlink content into that memory whenever it is needed.
959+
960+When the symlink is stored in the inode, it has the same lifetime as
961+the inode which, itself, is protected by RCU or by a counted reference
962+on the dentry. This means that the mechanisms that pathname lookup
963+uses to access the dcache and icache (inode cache) safely are quite
964+sufficient for accessing some cached symlinks safely. In these cases,
965+the `i_link` pointer in the inode is set to point to wherever the
966+symlink is stored and it can be accessed directly whenever needed.
967+
968+When the symlink is stored in the page cache or elsewhere, the
969+situation is not so straightforward. A reference on a dentry or even
970+on an inode does not imply any reference on cached pages of that
971+inode, and even an `rcu_read_lock()` is not sufficient to ensure that
972+a page will not disappear. So for these symlinks the pathname lookup
973+code needs to ask the filesystem to provide a stable reference and,
974+significantly, needs to release that reference when it is finished
975+with it.
976+
977+Taking a reference to a cache page is often possible even in RCU-walk
978+mode. It does require making changes to memory, which is best avoided,
979+but that isn't necessarily a big cost and it is better than dropping
980+out of RCU-walk mode completely. Even filesystems that allocate
981+space to copy the symlink into can use `GFP_ATOMIC` to often successfully
982+allocate memory without the need to drop out of RCU-walk. If a
983+filesystem cannot successfully get a reference in RCU-walk mode, it
984+must return `-ECHILD` and `unlazy_walk()` will be called to return to
985+REF-walk mode in which the filesystem is allowed to sleep.
986+
987+The place for all this to happen is the `i_op->follow_link()` inode
988+method. In the present mainline code this is never actually called in
989+RCU-walk mode as the rewrite is not quite complete. It is likely that
990+in a future release this method will be passed an `inode` pointer when
991+called in RCU-walk mode so it both (1) knows to be careful, and (2) has the
992+validated pointer. Much like the `i_op->permission()` method we
993+looked at previously, `->follow_link()` would need to be careful that
994+all the data structures it references are safe to be accessed while
995+holding no counted reference, only the RCU lock. Though getting a
996+reference with `->follow_link()` is not yet done in RCU-walk mode, the
997+code is ready to release the reference when that does happen.
998+
999+This need to drop the reference to a symlink adds significant
1000+complexity. It requires a reference to the inode so that the
1001+`i_op->put_link()` inode operation can be called. In REF-walk, that
1002+reference is kept implicitly through a reference to the dentry, so
1003+keeping the `struct path` of the symlink is easiest. For RCU-walk,
1004+the pointer to the inode is kept separately. To allow switching from
1005+RCU-walk back to REF-walk in the middle of processing nested symlinks
1006+we also need the seq number for the dentry so we can confirm that
1007+switching back was safe.
1008+
1009+Finally, when providing a reference to a symlink, the filesystem also
1010+provides an opaque "cookie" that must be passed to `->put_link()` so that it
1011+knows what to free. This might be the allocated memory area, or a
1012+pointer to the `struct page` in the page cache, or something else
1013+completely. Only the filesystem knows what it is.
1014+
1015+In order for the reference to each symlink to be dropped when the walk completes,
1016+whether in RCU-walk or REF-walk, the symlink stack needs to contain,
1017+along with the path remnants:
1018+
1019+- the `struct path` to provide a reference to the inode in REF-walk
1020+- the `struct inode *` to provide a reference to the inode in RCU-walk
1021+- the `seq` to allow the path to be safely switched from RCU-walk to REF-walk
1022+- the `cookie` that tells `->put_path()` what to put.
1023+
1024+This means that each entry in the symlink stack needs to hold five
1025+pointers and an integer instead of just one pointer (the path
1026+remnant). On a 64-bit system, this is about 40 bytes per entry;
1027+with 40 entries it adds up to 1600 bytes total, which is less than
1028+half a page. So it might seem like a lot, but is by no means
1029+excessive.
1030+
1031+Note that, in a given stack frame, the path remnant (`name`) is not
1032+part of the symlink that the other fields refer to. It is the remnant
1033+to be followed once that symlink has been fully parsed.
1034+
1035+Following the symlink
1036+---------------------
1037+
1038+The main loop in `link_path_walk()` iterates seamlessly over all
1039+components in the path and all of the non-final symlinks. As symlinks
1040+are processed, the `name` pointer is adjusted to point to a new
1041+symlink, or is restored from the stack, so that much of the loop
1042+doesn't need to notice. Getting this `name` variable on and off the
1043+stack is very straightforward; pushing and popping the references is
1044+a little more complex.
1045+
1046+When a symlink is found, `walk_component()` returns the value `1`
1047+(`0` is returned for any other sort of success, and a negative number
1048+is, as usual, an error indicator). This causes `get_link()` to be
1049+called; it then gets the link from the filesystem. Providing that
1050+operation is successful, the old path `name` is placed on the stack,
1051+and the new value is used as the `name` for a while. When the end of
1052+the path is found (i.e. `*name` is `'\0'`) the old `name` is restored
1053+off the stack and path walking continues.
1054+
1055+Pushing and popping the reference pointers (inode, cookie, etc.) is more
1056+complex in part because of the desire to handle tail recursion. When
1057+the last component of a symlink itself points to a symlink, we
1058+want to pop the symlink-just-completed off the stack before pushing
1059+the symlink-just-found to avoid leaving empty path remnants that would
1060+just get in the way.
1061+
1062+It is most convenient to push the new symlink references onto the
1063+stack in `walk_component()` immediately when the symlink is found;
1064+`walk_component()` is also the last piece of code that needs to look at the
1065+old symlink as it walks that last component. So it is quite
1066+convenient for `walk_component()` to release the old symlink and pop
1067+the references just before pushing the reference information for the
1068+new symlink. It is guided in this by two flags; `WALK_GET`, which
1069+gives it permission to follow a symlink if it finds one, and
1070+`WALK_PUT`, which tells it to release the current symlink after it has been
1071+followed. `WALK_PUT` is tested first, leading to a call to
1072+`put_link()`. `WALK_GET` is tested subsequently (by
1073+`should_follow_link()`) leading to a call to `pick_link()` which sets
1074+up the stack frame.
1075+
1076+### Symlinks with no final component ###
1077+
1078+A pair of special-case symlinks deserve a little further explanation.
1079+Both result in a new `struct path` (with mount and dentry) being set
1080+up in the `nameidata`, and result in `get_link()` returning `NULL`.
1081+
1082+The more obvious case is a symlink to "`/`". All symlinks starting
1083+with "`/`" are detected in `get_link()` which resets the `nameidata`
1084+to point to the effective filesystem root. If the symlink only
1085+contains "`/`" then there is nothing more to do, no components at all,
1086+so `NULL` is returned to indicate that the symlink can be released and
1087+the stack frame discarded.
1088+
1089+The other case involves things in `/proc` that look like symlinks but
1090+aren't really.
1091+
1092+> $ ls -l /proc/self/fd/1
1093+> lrwx------ 1 neilb neilb 64 Jun 13 10:19 /proc/self/fd/1 -> /dev/pts/4
1094+
1095+Every open file descriptor in any process is represented in `/proc` by
1096+something that looks like a symlink. It is really a reference to the
1097+target file, not just the name of it. When you `readlink` these
1098+objects you get a name that might refer to the same file - unless it
1099+has been unlinked or mounted over. When `walk_component()` follows
1100+one of these, the `->follow_link()` method in "procfs" doesn't return
1101+a string name, but instead calls `nd_jump_link()` which updates the
1102+`nameidata` in place to point to that target. `->follow_link()` then
1103+returns `NULL`. Again there is no final component and `get_link()`
1104+reports this by leaving the `last_type` field of `nameidata` as
1105+`LAST_BIND`.
1106+
1107+Following the symlink in the final component
1108+--------------------------------------------
1109+
1110+All this leads to `link_path_walk()` walking down every component, and
1111+following all symbolic links it finds, until it reaches the final
1112+component. This is just returned in the `last` field of `nameidata`.
1113+For some callers, this is all they need; they want to create that
1114+`last` name if it doesn't exist or give an error if it does. Other
1115+callers will want to follow a symlink if one is found, and possibly
1116+apply special handling to the last component of that symlink, rather
1117+than just the last component of the original file name. These callers
1118+potentially need to call `link_path_walk()` again and again on
1119+successive symlinks until one is found that doesn't point to another
1120+symlink.
1121+
1122+This case is handled by the relevant caller of `link_path_walk()`, such as
1123+`path_lookupat()` using a loop that calls `link_path_walk()`, and then
1124+handles the final component. If the final component is a symlink
1125+that needs to be followed, then `trailing_symlink()` is called to set
1126+things up properly and the loop repeats, calling `link_path_walk()`
1127+again. This could loop as many as 40 times if the last component of
1128+each symlink is another symlink.
1129+
1130+The various functions that examine the final component and possibly
1131+report that it is a symlink are `lookup_last()`, `mountpoint_last()`
1132+and `do_last()`, each of which use the same convention as
1133+`walk_component()` of returning `1` if a symlink was found that needs
1134+to be followed.
1135+
1136+Of these, `do_last()` is the most interesting as it is used for
1137+opening a file. Part of `do_last()` runs with `i_mutex` held and this
1138+part is in a separate function: `lookup_open()`.
1139+
1140+Explaining `do_last()` completely is beyond the scope of this article,
1141+but a few highlights should help those interested in exploring the
1142+code.
1143+
1144+1. Rather than just finding the target file, `do_last()` needs to open
1145+ it. If the file was found in the dcache, then `vfs_open()` is used for
1146+ this. If not, then `lookup_open()` will either call `atomic_open()` (if
1147+ the filesystem provides it) to combine the final lookup with the open, or
1148+ will perform the separate `lookup_real()` and `vfs_create()` steps
1149+ directly. In the later case the actual "open" of this newly found or
1150+ created file will be performed by `vfs_open()`, just as if the name
1151+ were found in the dcache.
1152+
1153+2. `vfs_open()` can fail with `-EOPENSTALE` if the cached information
1154+ wasn't quite current enough. Rather than restarting the lookup from
1155+ the top with `LOOKUP_REVAL` set, `lookup_open()` is called instead,
1156+ giving the filesystem a chance to resolve small inconsistencies.
1157+ If that doesn't work, only then is the lookup restarted from the top.
1158+
1159+3. An open with O_CREAT **does** follow a symlink in the final component,
1160+ unlike other creation system calls (like `mkdir`). So the sequence:
1161+
1162+ > ln -s bar /tmp/foo
1163+ > echo hello > /tmp/foo
1164+
1165+ will create a file called `/tmp/bar`. This is not permitted if
1166+ `O_EXCL` is set but otherwise is handled for an O_CREAT open much
1167+ like for a non-creating open: `should_follow_link()` returns `1`, and
1168+ so does `do_last()` so that `trailing_symlink()` gets called and the
1169+ open process continues on the symlink that was found.
1170+
1171+Updating the access time
1172+------------------------
1173+
1174+We previously said of RCU-walk that it would "take no locks, increment
1175+no counts, leave no footprints." We have since seen that some
1176+"footprints" can be needed when handling symlinks as a counted
1177+reference (or even a memory allocation) may be needed. But these
1178+footprints are best kept to a minimum.
1179+
1180+One other place where walking down a symlink can involve leaving
1181+footprints in a way that doesn't affect directories is in updating access times.
1182+In Unix (and Linux) every filesystem object has a "last accessed
1183+time", or "`atime`". Passing through a directory to access a file
1184+within is not considered to be an access for the purposes of
1185+`atime`; only listing the contents of a directory can update its `atime`.
1186+Symlinks are different it seems. Both reading a symlink (with `readlink()`)
1187+and looking up a symlink on the way to some other destination can
1188+update the atime on that symlink.
1189+
1190+[clearest statement]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_08
1191+
1192+It is not clear why this is the case; POSIX has little to say on the
1193+subject. The [clearest statement] is that, if a particular implementation
1194+updates a timestamp in a place not specified by POSIX, this must be
1195+documented "except that any changes caused by pathname resolution need
1196+not be documented". This seems to imply that POSIX doesn't really
1197+care about access-time updates during pathname lookup.
1198+
1199+[Linux 1.3.87]: https://git.kernel.org/cgit/linux/kernel/git/history/history.git/diff/fs/ext2/symlink.c?id=f806c6db77b8eaa6e00dcfb6b567706feae8dbb8
1200+
1201+An examination of history shows that prior to [Linux 1.3.87], the ext2
1202+filesystem, at least, didn't update atime when following a link.
1203+Unfortunately we have no record of why that behavior was changed.
1204+
1205+In any case, access time must now be updated and that operation can be
1206+quite complex. Trying to stay in RCU-walk while doing it is best
1207+avoided. Fortunately it is often permitted to skip the `atime`
1208+update. Because `atime` updates cause performance problems in various
1209+areas, Linux supports the `relatime` mount option, which generally
1210+limits the updates of `atime` to once per day on files that aren't
1211+being changed (and symlinks never change once created). Even without
1212+`relatime`, many filesystems record `atime` with a one-second
1213+granularity, so only one update per second is required.
1214+
1215+It is easy to test if an `atime` update is needed while in RCU-walk
1216+mode and, if it isn't, the update can be skipped and RCU-walk mode
1217+continues. Only when an `atime` update is actually required does the
1218+path walk drop down to REF-walk. All of this is handled in the
1219+`get_link()` function.
1220+
1221+A few flags
1222+-----------
1223+
1224+A suitable way to wrap up this tour of pathname walking is to list
1225+the various flags that can be stored in the `nameidata` to guide the
1226+lookup process. Many of these are only meaningful on the final
1227+component, others reflect the current state of the pathname lookup.
1228+And then there is `LOOKUP_EMPTY`, which doesn't fit conceptually with
1229+the others. If this is not set, an empty pathname causes an error
1230+very early on. If it is set, empty pathnames are not considered to be
1231+an error.
1232+
1233+### Global state flags ###
1234+
1235+We have already met two global state flags: `LOOKUP_RCU` and
1236+`LOOKUP_REVAL`. These select between one of three overall approaches
1237+to lookup: RCU-walk, REF-walk, and REF-walk with forced revalidation.
1238+
1239+`LOOKUP_PARENT` indicates that the final component hasn't been reached
1240+yet. This is primarily used to tell the audit subsystem the full
1241+context of a particular access being audited.
1242+
1243+`LOOKUP_ROOT` indicates that the `root` field in the `nameidata` was
1244+provided by the caller, so it shouldn't be released when it is no
1245+longer needed.
1246+
1247+`LOOKUP_JUMPED` means that the current dentry was chosen not because
1248+it had the right name but for some other reason. This happens when
1249+following "`..`", following a symlink to `/`, crossing a mount point
1250+or accessing a "`/proc/$PID/fd/$FD`" symlink. In this case the
1251+filesystem has not been asked to revalidate the name (with
1252+`d_revalidate()`). In such cases the inode may still need to be
1253+revalidated, so `d_op->d_weak_revalidate()` is called if
1254+`LOOKUP_JUMPED` is set when the look completes - which may be at the
1255+final component or, when creating, unlinking, or renaming, at the penultimate component.
1256+
1257+### Final-component flags ###
1258+
1259+Some of these flags are only set when the final component is being
1260+considered. Others are only checked for when considering that final
1261+component.
1262+
1263+`LOOKUP_AUTOMOUNT` ensures that, if the final component is an automount
1264+point, then the mount is triggered. Some operations would trigger it
1265+anyway, but operations like `stat()` deliberately don't. `statfs()`
1266+needs to trigger the mount but otherwise behaves a lot like `stat()`, so
1267+it sets `LOOKUP_AUTOMOUNT`, as does "`quotactl()`" and the handling of
1268+"`mount --bind`".
1269+
1270+`LOOKUP_FOLLOW` has a similar function to `LOOKUP_AUTOMOUNT` but for
1271+symlinks. Some system calls set or clear it implicitly, while
1272+others have API flags such as `AT_SYMLINK_FOLLOW` and
1273+`UMOUNT_NOFOLLOW` to control it. Its effect is similar to
1274+`WALK_GET` that we already met, but it is used in a different way.
1275+
1276+`LOOKUP_DIRECTORY` insists that the final component is a directory.
1277+Various callers set this and it is also set when the final component
1278+is found to be followed by a slash.
1279+
1280+Finally `LOOKUP_OPEN`, `LOOKUP_CREATE`, `LOOKUP_EXCL`, and
1281+`LOOKUP_RENAME_TARGET` are not used directly by the VFS but are made
1282+available to the filesystem and particularly the `->d_revalidate()`
1283+method. A filesystem can choose not to bother revalidating too hard
1284+if it knows that it will be asked to open or create the file soon.
1285+These flags were previously useful for `->lookup()` too but with the
1286+introduction of `->atomic_open()` they are less relevant there.
1287+
1288+End of the road
1289+---------------
1290+
1291+Despite its complexity, all this pathname lookup code appears to be
1292+in good shape - various parts are certainly easier to understand now
1293+than even a couple of releases ago. But that doesn't mean it is
1294+"finished". As already mentioned, RCU-walk currently only follows
1295+symlinks that are stored in the inode so, while it handles many ext4
1296+symlinks, it doesn't help with NFS, XFS, or Btrfs. That support
1297+is not likely to be long delayed.
Documentation/filesystems/path-lookup.txt+1−1
@@ -379,4 +379,4 @@ Papers and other documentation on dcache locking · 378 unmodified lines
379379
380380 2. http://lse.sourceforge.net/locking/dcache/dcache.html
381381
382−
382+3. path-lookup.md in this directory.
Documentation/filesystems/proc.txt+29−20
@@ -140,7 +140,8 @@ Table 1-1: Process specific entries in /proc · 139 unmodified lines
140140 stat Process status
141141 statm Process memory status information
142142 status Process status in human readable form
143− wchan If CONFIG_KALLSYMS is set, a pre-decoded wchan
143+ wchan Present with CONFIG_KALLSYMS=y: it shows the kernel function
144+ symbol the task is blocked in - or "0" if not blocked.
144145 pagemap Page table
145146 stack Report full stack trace, enable via CONFIG_STACKTRACE
146147 smaps a extension based on maps, showing the memory consumption of
@@ -174,6 +175,7 @@ read the file /proc/PID/status: · 27 unmodified lines
174175 VmLib: 1412 kB
175176 VmPTE: 20 kb
176177 VmSwap: 0 kB
178+ HugetlbPages: 0 kB
177179 Threads: 1
178180 SigQ: 0/28578
179181 SigPnd: 0000000000000000
@@ -237,6 +239,7 @@ Table 1-2: Contents of the status files (as of 4.1) · 57 unmodified lines
237239 VmPTE size of page table entries
238240 VmPMD size of second level page tables
239241 VmSwap size of swap usage (the number of referred swapents)
242+ HugetlbPages size of hugetlb memory portions
240243 Threads number of threads
241244 SigQ number of signals queued/max. number for queue
242245 SigPnd bitmap of pending signals for the thread
@@ -310,7 +313,7 @@ Table 1-4: Contents of the stat files (as of 2.6.30-rc7) · 67 unmodified lines
310313 blocked bitmap of blocked signals
311314 sigign bitmap of ignored signals
312315 sigcatch bitmap of caught signals
313− wchan address where process went to sleep
316+ 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
314317 0 (place holder)
315318 0 (place holder)
316319 exit_signal signal to send to parent thread on exit
@@ -423,12 +426,15 @@ Private_Clean: 0 kB · 106 unmodified lines
423426 Private_Dirty: 0 kB
424427 Referenced: 892 kB
425428 Anonymous: 0 kB
429+AnonHugePages: 0 kB
430+Shared_Hugetlb: 0 kB
431+Private_Hugetlb: 0 kB
426432 Swap: 0 kB
427433 SwapPss: 0 kB
428434 KernelPageSize: 4 kB
429435 MMUPageSize: 4 kB
430−Locked: 374 kB
431−VmFlags: rd ex mr mw me de
436+Locked: 0 kB
437+VmFlags: rd ex mr mw me dw
432438
433439 the first of these lines shows the same information as is displayed for the
434440 mapping in /proc/PID/maps. The remaining lines show the size of the mapping
@@ -448,9 +454,14 @@ accessed. · 13 unmodified lines
448454 "Anonymous" shows the amount of memory that does not belong to any file. Even
449455 a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE
450456 and a page is modified, the file page is replaced by a private anonymous copy.
451−"Swap" shows how much would-be-anonymous memory is also used, but out on
452−swap.
457+"AnonHugePages" shows the ammount of memory backed by transparent hugepage.
458+"Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by
459+hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical
460+reasons. And these are not included in {Shared,Private}_{Clean,Dirty} field.
461+"Swap" shows how much would-be-anonymous memory is also used, but out on swap.
453462 "SwapPss" shows proportional swap share of this mapping.
463+"Locked" indicates whether the mapping is locked in memory or not.
464+
454465 "VmFlags" field deserves a separate description. This member represents the kernel
455466 flags associated with the particular virtual memory area in two letter encoded
456467 manner. The codes are the following:
@@ -474,7 +485,6 @@ manner. The codes are the following: · 17 unmodified lines
474485 ac - area is accountable
475486 nr - swap space is not reserved for the area
476487 ht - area uses huge tlb pages
477− nl - non-linear mapping
478488 ar - architecture specific flag
479489 dd - do not include area into core dump
480490 sd - soft-dirty flag
@@ -814,9 +824,6 @@ varies by architecture and compile options. The following is from a · 333 unmodified lines
814824
815825 > cat /proc/meminfo
816826
817−The "Locked" indicates whether the mapping is locked in memory or not.
818−
819−
820827 MemTotal: 16344972 kB
821828 MemFree: 13634064 kB
822829 MemAvailable: 14836172 kB
@@ -1598,16 +1605,16 @@ Documentation/accounting. · 775 unmodified lines
15981605 ---------------------------------------------------------------
15991606 When a process is dumped, all anonymous memory is written to a core file as
16001607 long as the size of the core file isn't limited. But sometimes we don't want
1601−to dump some memory segments, for example, huge shared memory. Conversely,
1602−sometimes we want to save file-backed memory segments into a core file, not
1603−only the individual files.
1608+to dump some memory segments, for example, huge shared memory or DAX.
1609+Conversely, sometimes we want to save file-backed memory segments into a core
1610+file, not only the individual files.
16041611
16051612 /proc/<pid>/coredump_filter allows you to customize which memory segments
16061613 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
16071614 of memory types. If a bit of the bitmask is set, memory segments of the
16081615 corresponding memory type are dumped, otherwise they are not dumped.
16091616
1610−The following 7 memory types are supported:
1617+The following 9 memory types are supported:
16111618 - (bit 0) anonymous private memory
16121619 - (bit 1) anonymous shared memory
16131620 - (bit 2) file-backed private memory
@@ -1616,20 +1623,22 @@ The following 7 memory types are supported: · 2 unmodified lines
16161623 effective only if the bit 2 is cleared)
16171624 - (bit 5) hugetlb private memory
16181625 - (bit 6) hugetlb shared memory
1626+ - (bit 7) DAX private memory
1627+ - (bit 8) DAX shared memory
16191628
16201629 Note that MMIO pages such as frame buffer are never dumped and vDSO pages
16211630 are always dumped regardless of the bitmask status.
16221631
1623− Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only
1624− effected by bit 5-6.
1632+ Note that bits 0-4 don't affect hugetlb or DAX memory. hugetlb memory is
1633+ only affected by bit 5-6, and DAX is only affected by bits 7-8.
16251634
1626−Default value of coredump_filter is 0x23; this means all anonymous memory
1627−segments and hugetlb private memory are dumped.
1635+The default value of coredump_filter is 0x33; this means all anonymous memory
1636+segments, ELF header pages and hugetlb private memory are dumped.
16281637
16291638 If you don't want to dump all shared memory segments attached to pid 1234,
1630−write 0x21 to the process's proc file.
1639+write 0x31 to the process's proc file.
16311640
1632− $ echo 0x21 > /proc/1234/coredump_filter
1641+ $ echo 0x31 > /proc/1234/coredump_filter
16331642
16341643 When a new process is created, the process inherits the bitmask status from its
16351644 parent. It is useful to set up coredump_filter before the program runs.
Documentation/filesystems/sysfs-tagging.txt+7−7
@@ -17,13 +17,13 @@ the sysfs directory entries we ensure that we don't have conflicts · 16 unmodified lines
1717 in the directories and applications only see a limited set of
1818 the network devices.
1919
20−Each sysfs directory entry may be tagged with zero or one
21−namespaces. A sysfs_dirent is augmented with a void *s_ns. If a
22−directory entry is tagged, then sysfs_dirent->s_flags will have a
23−flag between KOBJ_NS_TYPE_NONE and KOBJ_NS_TYPES, and s_ns will
24−point to the namespace to which it belongs.
20+Each sysfs directory entry may be tagged with a namespace via the
21+void *ns member of its kernfs_node. If a directory entry is tagged,
22+then kernfs_node->flags will have a flag between KOBJ_NS_TYPE_NONE
23+and KOBJ_NS_TYPES, and ns will point to the namespace to which it
24+belongs.
2525
26−Each sysfs superblock's sysfs_super_info contains an array void
26+Each sysfs superblock's kernfs_super_info contains an array void
2727 *ns[KOBJ_NS_TYPES]. When a task in a tagging namespace
2828 kobj_nstype first mounts sysfs, a new superblock is created. It
2929 will be differentiated from other sysfs mounts by having its
@@ -31,7 +31,7 @@ s_fs_info->ns[kobj_nstype] set to the new namespace. Note that · 1 unmodified line
3131 through bind mounting and mounts propagation, a task can easily view
3232 the contents of other namespaces' sysfs mounts. Therefore, when a
3333 namespace exits, it will call kobj_ns_exit() to invalidate any
34−sysfs_dirent->s_ns pointers pointing to it.
34+kernfs_node->ns pointers pointing to it.
3535
3636 Users of this interface:
3737 - define a type in the kobj_ns_type enumeration.
Documentation/filesystems/sysfs.txt+5−4
@@ -40,7 +40,7 @@ ancestors of object hierarchies; i.e. the subsystems the objects · 39 unmodified lines
4040 belong to.
4141
4242 Sysfs internally stores a pointer to the kobject that implements a
43−directory in the sysfs_dirent object associated with the directory. In
43+directory in the kernfs_node object associated with the directory. In
4444 the past this kobject pointer has been used by sysfs to do reference
4545 counting directly on the kobject whenever the file is opened or closed.
4646 With the current sysfs implementation the kobject reference count is
@@ -191,9 +191,10 @@ implementations: · 144 unmodified lines
191191 be called again, rearmed, to fill the buffer.
192192
193193 - On write(2), sysfs expects the entire buffer to be passed during the
194− first write. Sysfs then passes the entire buffer to the store()
195− method.
196−
194+ first write. Sysfs then passes the entire buffer to the store() method.
195+ A terminating null is added after the data on stores. This makes
196+ functions like sysfs_streq() safe to use.
197+
197198 When writing sysfs files, userspace processes should first read the
198199 entire file, modify the values it wishes to change, then write the
199200 entire buffer back.
Documentation/fpga/fpga-mgr.txt+171−0
@@ -0,0 +1,171 @@
1+FPGA Manager Core
2+
3+Alan Tull 2015
4+
5+Overview
6+========
7+
8+The FPGA manager core exports a set of functions for programming an FPGA with
9+an image. The API is manufacturer agnostic. All manufacturer specifics are
10+hidden away in a low level driver which registers a set of ops with the core.
11+The FPGA image data itself is very manufacturer specific, but for our purposes
12+it's just binary data. The FPGA manager core won't parse it.
13+
14+
15+API Functions:
16+==============
17+
18+To program the FPGA from a file or from a buffer:
19+-------------------------------------------------
20+
21+ int fpga_mgr_buf_load(struct fpga_manager *mgr, u32 flags,
22+ const char *buf, size_t count);
23+
24+Load the FPGA from an image which exists as a buffer in memory.
25+
26+ int fpga_mgr_firmware_load(struct fpga_manager *mgr, u32 flags,
27+ const char *image_name);
28+
29+Load the FPGA from an image which exists as a file. The image file must be on
30+the firmware search path (see the firmware class documentation).
31+
32+For both these functions, flags == 0 for normal full reconfiguration or
33+FPGA_MGR_PARTIAL_RECONFIG for partial reconfiguration. If successful, the FPGA
34+ends up in operating mode. Return 0 on success or a negative error code.
35+
36+
37+To get/put a reference to a FPGA manager:
38+-----------------------------------------
39+
40+ struct fpga_manager *of_fpga_mgr_get(struct device_node *node);
41+
42+ void fpga_mgr_put(struct fpga_manager *mgr);
43+
44+Given a DT node, get an exclusive reference to a FPGA manager or release
45+the reference.
46+
47+
48+To register or unregister the low level FPGA-specific driver:
49+-------------------------------------------------------------
50+
51+ int fpga_mgr_register(struct device *dev, const char *name,
52+ const struct fpga_manager_ops *mops,
53+ void *priv);
54+
55+ void fpga_mgr_unregister(struct device *dev);
56+
57+Use of these two functions is described below in "How To Support a new FPGA
58+device."
59+
60+
61+How to write an image buffer to a supported FPGA
62+================================================
63+/* Include to get the API */
64+#include <linux/fpga/fpga-mgr.h>
65+
66+/* device node that specifies the FPGA manager to use */
67+struct device_node *mgr_node = ...
68+
69+/* FPGA image is in this buffer. count is size of the buffer. */
70+char *buf = ...
71+int count = ...
72+
73+/* flags indicates whether to do full or partial reconfiguration */
74+int flags = 0;
75+
76+int ret;
77+
78+/* Get exclusive control of FPGA manager */
79+struct fpga_manager *mgr = of_fpga_mgr_get(mgr_node);
80+
81+/* Load the buffer to the FPGA */
82+ret = fpga_mgr_buf_load(mgr, flags, buf, count);
83+
84+/* Release the FPGA manager */
85+fpga_mgr_put(mgr);
86+
87+
88+How to write an image file to a supported FPGA
89+==============================================
90+/* Include to get the API */
91+#include <linux/fpga/fpga-mgr.h>
92+
93+/* device node that specifies the FPGA manager to use */
94+struct device_node *mgr_node = ...
95+
96+/* FPGA image is in this file which is in the firmware search path */
97+const char *path = "fpga-image-9.rbf"
98+
99+/* flags indicates whether to do full or partial reconfiguration */
100+int flags = 0;
101+
102+int ret;
103+
104+/* Get exclusive control of FPGA manager */
105+struct fpga_manager *mgr = of_fpga_mgr_get(mgr_node);
106+
107+/* Get the firmware image (path) and load it to the FPGA */
108+ret = fpga_mgr_firmware_load(mgr, flags, path);
109+
110+/* Release the FPGA manager */
111+fpga_mgr_put(mgr);
112+
113+
114+How to support a new FPGA device
115+================================
116+To add another FPGA manager, write a driver that implements a set of ops. The
117+probe function calls fpga_mgr_register(), such as:
118+
119+static const struct fpga_manager_ops socfpga_fpga_ops = {
120+ .write_init = socfpga_fpga_ops_configure_init,
121+ .write = socfpga_fpga_ops_configure_write,
122+ .write_complete = socfpga_fpga_ops_configure_complete,
123+ .state = socfpga_fpga_ops_state,
124+};
125+
126+static int socfpga_fpga_probe(struct platform_device *pdev)
127+{
128+ struct device *dev = &pdev->dev;
129+ struct socfpga_fpga_priv *priv;
130+ int ret;
131+
132+ priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
133+ if (!priv)
134+ return -ENOMEM;
135+
136+ /* ... do ioremaps, get interrupts, etc. and save
137+ them in priv... */
138+
139+ return fpga_mgr_register(dev, "Altera SOCFPGA FPGA Manager",
140+ &socfpga_fpga_ops, priv);
141+}
142+
143+static int socfpga_fpga_remove(struct platform_device *pdev)
144+{
145+ fpga_mgr_unregister(&pdev->dev);
146+
147+ return 0;
148+}
149+
150+
151+The ops will implement whatever device specific register writes are needed to
152+do the programming sequence for this particular FPGA. These ops return 0 for
153+success or negative error codes otherwise.
154+
155+The programming sequence is:
156+ 1. .write_init
157+ 2. .write (may be called once or multiple times)
158+ 3. .write_complete
159+
160+The .write_init function will prepare the FPGA to receive the image data.
161+
162+The .write function writes a buffer to the FPGA. The buffer may be contain the
163+whole FPGA image or may be a smaller chunk of an FPGA image. In the latter
164+case, this function is called multiple times for successive chunks.
165+
166+The .write_complete function is called after all the image has been written
167+to put the FPGA into operating mode.
168+
169+The ops include a .state function which will read the hardware FPGA manager and
170+return a code of type enum fpga_mgr_states. It doesn't result in a change in
171+hardware state.
Documentation/gpio/board.txt+7−3
@@ -21,8 +21,8 @@ exact way to do it depends on the GPIO controller providing the GPIOs, see the · 20 unmodified lines
2121 device tree bindings for your controller.
2222
2323 GPIOs mappings are defined in the consumer device's node, in a property named
24−either <function>-gpios or <function>-gpio, where <function> is the function
25−the driver will request through gpiod_get(). For example:
24+<function>-gpios, where <function> is the function the driver will request
25+through gpiod_get(). For example:
2626
2727 foo_device {
2828 compatible = "acme,foo";
@@ -31,9 +31,13 @@ the driver will request through gpiod_get(). For example: · 2 unmodified lines
3131 <&gpio 16 GPIO_ACTIVE_HIGH>, /* green */
3232 <&gpio 17 GPIO_ACTIVE_HIGH>; /* blue */
3333
34− power-gpio = <&gpio 1 GPIO_ACTIVE_LOW>;
34+ power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
3535 };
3636
37+Properties named <function>-gpio are also considered valid and old bindings use
38+it but are only supported for compatibility reasons and should not be used for
39+newer bindings since it has been deprecated.
40+
3741 This property will make GPIOs 15, 16 and 17 available to the driver under the
3842 "led" function, and GPIO 1 as the "power" GPIO:
3943
Documentation/gpio/driver.txt+80−0
@@ -62,6 +62,11 @@ Any debugfs dump method should normally ignore signals which haven't been · 61 unmodified lines
6262 requested as GPIOs. They can use gpiochip_is_requested(), which returns either
6363 NULL or the label associated with that GPIO when it was requested.
6464
65+RT_FULL: GPIO driver should not use spinlock_t or any sleepable APIs
66+(like PM runtime) in its gpio_chip implementation (.get/.set and direction
67+control callbacks) if it is expected to call GPIO APIs from atomic context
68+on -RT (inside hard IRQ handlers and similar contexts). Normally this should
69+not be required.
6570
6671 GPIO drivers providing IRQs
6772 ---------------------------
@@ -73,6 +78,13 @@ The IRQ portions of the GPIO block are implemented using an irqchip, using · 5 unmodified lines
7378 the header <linux/irq.h>. So basically such a driver is utilizing two sub-
7479 systems simultaneously: gpio and irq.
7580
81+RT_FULL: GPIO driver should not use spinlock_t or any sleepable APIs
82+(like PM runtime) as part of its irq_chip implementation on -RT.
83+- spinlock_t should be replaced with raw_spinlock_t [1].
84+- If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
85+ and .irq_bus_unlock() callbacks, as these are the only slowpath callbacks
86+ on an irqchip. Create the callbacks if needed [2].
87+
7688 GPIO irqchips usually fall in one of two categories:
7789
7890 * CHAINED GPIO irqchips: these are usually the type that is embedded on
@@ -93,6 +105,38 @@ GPIO irqchips usually fall in one of two categories: · 14 unmodified lines
93105 Chained GPIO irqchips typically can NOT set the .can_sleep flag on
94106 struct gpio_chip, as everything happens directly in the callbacks.
95107
108+ RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
109+ As result, spinlock_t or any sleepable APIs (like PM runtime) can't be used
110+ in chained IRQ handler.
111+ if required (and if it can't be converted to the nested threaded GPIO irqchip)
112+ - chained IRQ handler can be converted to generic irq handler and this way
113+ it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
114+ (for example, see [3]).
115+ Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,
116+ so IRQ core will complain if it will be called from IRQ handler wich is forced
117+ thread. The "fake?" raw lock can be used to W/A this problem:
118+
119+ raw_spinlock_t wa_lock;
120+ static irqreturn_t omap_gpio_irq_handler(int irq, void *gpiobank)
121+ unsigned long wa_lock_flags;
122+ raw_spin_lock_irqsave(&bank->wa_lock, wa_lock_flags);
123+ generic_handle_irq(irq_find_mapping(bank->chip.irqdomain, bit));
124+ raw_spin_unlock_irqrestore(&bank->wa_lock, wa_lock_flags);
125+
126+* GENERIC CHAINED GPIO irqchips: these are the same as "CHAINED GPIO irqchips",
127+ but chained IRQ handlers are not used. Instead GPIO IRQs dispatching is
128+ performed by generic IRQ handler which is configured using request_irq().
129+ The GPIO irqchip will then end up calling something like this sequence in
130+ its interrupt handler:
131+
132+ static irqreturn_t gpio_rcar_irq_handler(int irq, void *dev_id)
133+ for each detected GPIO IRQ
134+ generic_handle_irq(...);
135+
136+ RT_FULL: Such kind of handlers will be forced threaded on -RT, as result IRQ
137+ core will complain that generic_handle_irq() is called with IRQ enabled and
138+ the same W/A as for "CHAINED GPIO irqchips" can be applied.
139+
96140 * NESTED THREADED GPIO irqchips: these are off-chip GPIO expanders and any
97141 other GPIO irqchip residing on the other side of a sleeping bus. Of course
98142 such drivers that need slow bus traffic to read out IRQ status and similar,
@@ -133,6 +177,13 @@ To use the helpers please keep the following in mind: · 34 unmodified lines
133177 the irqchip can initialize. E.g. .dev and .can_sleep shall be set up
134178 properly.
135179
180+- Nominally set all handlers to handle_bad_irq() in the setup call and pass
181+ handle_bad_irq() as flow handler parameter in gpiochip_irqchip_add() if it is
182+ expected for GPIO driver that irqchip .set_type() callback have to be called
183+ before using/enabling GPIO IRQ. Then set the handler to handle_level_irq()
184+ and/or handle_edge_irq() in the irqchip .set_type() callback depending on
185+ what your controller supports.
186+
136187 It is legal for any IRQ consumer to request an IRQ from any irqchip no matter
137188 if that is a combined GPIO+IRQ driver. The basic premise is that gpio_chip and
138189 irq_chip are orthogonal, and offering their services independent of each
@@ -169,6 +220,31 @@ When implementing an irqchip inside a GPIO driver, these two functions should · 30 unmodified lines
169220 typically be called in the .startup() and .shutdown() callbacks from the
170221 irqchip.
171222
223+Real-Time compliance for GPIO IRQ chips
224+---------------------------------------
225+
226+Any provider of irqchips needs to be carefully tailored to support Real Time
227+preemption. It is desireable that all irqchips in the GPIO subsystem keep this
228+in mind and does the proper testing to assure they are real time-enabled.
229+So, pay attention on above " RT_FULL:" notes, please.
230+The following is a checklist to follow when preparing a driver for real
231+time-compliance:
232+
233+- ensure spinlock_t is not used as part irq_chip implementation;
234+- ensure that sleepable APIs are not used as part irq_chip implementation.
235+ If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
236+ and .irq_bus_unlock() callbacks;
237+- Chained GPIO irqchips: ensure spinlock_t or any sleepable APIs are not used
238+ from chained IRQ handler;
239+- Generic chained GPIO irqchips: take care about generic_handle_irq() calls and
240+ apply corresponding W/A;
241+- Chained GPIO irqchips: get rid of chained IRQ handler and use generic irq
242+ handler if possible :)
243+- regmap_mmio: Sry, but you are in trouble :( if MMIO regmap is used as for
244+ GPIO IRQ chip implementation;
245+- Test your driver with the appropriate in-kernel real time test cases for both
246+ level and edge IRQs.
247+
172248
173249 Requesting self-owned GPIO pins
174250 -------------------------------
@@ -190,3 +266,7 @@ gpiochip_free_own_desc(). · 15 unmodified lines
190266 These functions must be used with care since they do not affect module use
191267 count. Do not use the functions to request gpio descriptors not owned by the
192268 calling driver.
269+
270+[1] http://www.spinics.net/lists/linux-omap/msg120425.html
271+[2] https://lkml.org/lkml/2015/9/25/494
272+[3] https://lkml.org/lkml/2015/9/25/495
Documentation/gpio/sysfs.txt+3−3
@@ -20,14 +20,14 @@ userspace GPIO can be used to determine system configuration data that · 19 unmodified lines
2020 standard kernels won't know about. And for some tasks, simple userspace
2121 GPIO drivers could be all that the system really needs.
2222
23−DO NOT ABUSE SYFS TO CONTROL HARDWARE THAT HAS PROPER KERNEL DRIVERS.
23+DO NOT ABUSE SYSFS TO CONTROL HARDWARE THAT HAS PROPER KERNEL DRIVERS.
2424 PLEASE READ THE DOCUMENT NAMED "drivers-on-gpio.txt" IN THIS DOCUMENTATION
2525 DIRECTORY TO AVOID REINVENTING KERNEL WHEELS IN USERSPACE. I MEAN IT.
2626 REALLY.
2727
2828 Paths in Sysfs
2929 --------------
30−There are three kinds of entry in /sys/class/gpio:
30+There are three kinds of entries in /sys/class/gpio:
3131
3232 - Control interfaces used to get userspace control over GPIOs;
3333
@@ -106,7 +106,7 @@ read-only attributes: · 72 unmodified lines
106106
107107 "label" ... provided for diagnostics (not always unique)
108108
109− "ngpio" ... how many GPIOs this manges (N to N + ngpio - 1)
109+ "ngpio" ... how many GPIOs this manages (N to N + ngpio - 1)
110110
111111 Board documentation should in most cases cover what GPIOs are used for
112112 what purposes. However, those numbers are not always stable; GPIOs on
Documentation/hw_random.txt+4−4
@@ -3,7 +3,7 @@ Introduction: · 2 unmodified lines
33 The hw_random framework is software that makes use of a
44 special hardware feature on your CPU or motherboard,
55 a Random Number Generator (RNG). The software has two parts:
6− a core providing the /dev/hw_random character device and its
6+ a core providing the /dev/hwrng character device and its
77 sysfs support, plus a hardware-specific driver that plugs
88 into that core.
99
@@ -14,7 +14,7 @@ Introduction: · 4 unmodified lines
1414
1515 http://sourceforge.net/projects/gkernel/
1616
17− Those tools use /dev/hw_random to fill the kernel entropy pool,
17+ Those tools use /dev/hwrng to fill the kernel entropy pool,
1818 which is used internally and exported by the /dev/urandom and
1919 /dev/random special files.
2020
@@ -32,13 +32,13 @@ Theory of operation: · 11 unmodified lines
3232 The rng-tools package uses such tests in "rngd", and lets you
3333 run them by hand with a "rngtest" utility.
3434
35− /dev/hw_random is char device major 10, minor 183.
35+ /dev/hwrng is char device major 10, minor 183.
3636
3737 CLASS DEVICE. There is a /sys/class/misc/hw_random node with
3838 two unique attributes, "rng_available" and "rng_current". The
3939 "rng_available" attribute lists the hardware-specific drivers
4040 available, while "rng_current" lists the one which is currently
41− connected to /dev/hw_random. If your system has more than one
41+ connected to /dev/hwrng. If your system has more than one
4242 RNG available, you may change the one used by writing a name from
4343 the list in "rng_available" into "rng_current".
4444
Documentation/hwmon/lm75+3−2
@@ -42,8 +42,8 @@ Supported chips: · 41 unmodified lines
4242 Addresses scanned: none
4343 Datasheet: Publicly available at the ST website
4444 http://www.st.com/internet/analog/product/121769.jsp
45− * Texas Instruments TMP100, TMP101, TMP105, TMP112, TMP75, TMP175, TMP275
46− Prefixes: 'tmp100', 'tmp101', 'tmp105', 'tmp112', 'tmp175', 'tmp75', 'tmp275'
45+ * Texas Instruments TMP100, TMP101, TMP105, TMP112, TMP75, TMP75C, TMP175, TMP275
46+ Prefixes: 'tmp100', 'tmp101', 'tmp105', 'tmp112', 'tmp175', 'tmp75', 'tmp75c', 'tmp275'
4747 Addresses scanned: none
4848 Datasheet: Publicly available at the Texas Instruments website
4949 http://www.ti.com/product/tmp100
@@ -51,6 +51,7 @@ Supported chips: · 1 unmodified line
5151 http://www.ti.com/product/tmp105
5252 http://www.ti.com/product/tmp112
5353 http://www.ti.com/product/tmp75
54+ http://www.ti.com/product/tmp75c
5455 http://www.ti.com/product/tmp175
5556 http://www.ti.com/product/tmp275
5657 * NXP LM75B
Documentation/hwmon/max31790+37−0
@@ -0,0 +1,37 @@
1+Kernel driver max31790
2+======================
3+
4+Supported chips:
5+ * Maxim MAX31790
6+ Prefix: 'max31790'
7+ Addresses scanned: -
8+ Datasheet: http://pdfserv.maximintegrated.com/en/ds/MAX31790.pdf
9+
10+Author: Il Han <corone.il.han@gmail.com>
11+
12+
13+Description
14+-----------
15+
16+This driver implements support for the Maxim MAX31790 chip.
17+
18+The MAX31790 controls the speeds of up to six fans using six independent
19+PWM outputs. The desired fan speeds (or PWM duty cycles) are written
20+through the I2C interface. The outputs drive "4-wire" fans directly,
21+or can be used to modulate the fan's power terminals using an external
22+pass transistor.
23+
24+Tachometer inputs monitor fan tachometer logic outputs for precise (+/-1%)
25+monitoring and control of fan RPM as well as detection of fan failure.
26+Six pins are dedicated tachometer inputs. Any of the six PWM outputs can
27+also be configured to serve as tachometer inputs.
28+
29+
30+Sysfs entries
31+-------------
32+
33+fan[1-12]_input RO fan tachometer speed in RPM
34+fan[1-12]_fault RO fan experienced fault
35+fan[1-6]_target RW desired fan speed in RPM
36+pwm[1-6]_enable RW regulator mode, 0=disabled, 1=manual mode, 2=rpm mode
37+pwm[1-6] RW fan target duty cycle (0-255)
Documentation/hwmon/scpi-hwmon+33−0
@@ -0,0 +1,33 @@
1+Kernel driver scpi-hwmon
2+========================
3+
4+Supported chips:
5+ * Chips based on ARM System Control Processor Interface
6+ Addresses scanned: -
7+ Datasheet: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/index.html
8+
9+Author: Punit Agrawal <punit.agrawal@arm.com>
10+
11+Description
12+-----------
13+
14+This driver supports hardware monitoring for SoC's based on the ARM
15+System Control Processor (SCP) implementing the System Control
16+Processor Interface (SCPI). The following sensor types are supported
17+by the SCP -
18+
19+ * temperature
20+ * voltage
21+ * current
22+ * power
23+
24+The SCP interface provides an API to query the available sensors and
25+their values which are then exported to userspace by this driver.
26+
27+Usage Notes
28+-----------
29+
30+The driver relies on device tree node to indicate the presence of SCPI
31+support in the kernel. See
32+Documentation/devicetree/bindings/arm/arm,scpi.txt for details of the
33+devicetree node.
Documentation/i2c/busses/i2c-i801+3−0
@@ -30,6 +30,9 @@ Supported adapters: · 29 unmodified lines
3030 * Intel BayTrail (SOC)
3131 * Intel Sunrise Point-H (PCH)
3232 * Intel Sunrise Point-LP (PCH)
33+ * Intel DNV (SOC)
34+ * Intel Broxton (SOC)
35+ * Intel Lewisburg (PCH)
3336 Datasheets: Publicly available at the Intel website
3437
3538 On Intel Patsburg and later chipsets, both the normal host SMBus controller
Documentation/input/multi-touch-protocol.txt+1−1
@@ -361,7 +361,7 @@ For win8 devices with both T and C coordinates, the position mapping is · 360 unmodified lines
361361 ABS_MT_POSITION_X := T_X
362362 ABS_MT_POSITION_Y := T_Y
363363 ABS_MT_TOOL_X := C_X
364− ABS_MT_TOOL_X := C_Y
364+ ABS_MT_TOOL_Y := C_Y
365365
366366 Unfortunately, there is not enough information to specify both the touching
367367 ellipse and the tool ellipse, so one has to resort to approximations. One
Documentation/input/rotary-encoder.txt+7−2
@@ -9,8 +9,9 @@ peripherals with two wires. The outputs are phase-shifted by 90 degrees · 8 unmodified lines
99 and by triggering on falling and rising edges, the turn direction can
1010 be determined.
1111
12−Some encoders have both outputs low in stable states, whereas others also have
13−a stable state with both outputs high (half-period mode).
12+Some encoders have both outputs low in stable states, others also have
13+a stable state with both outputs high (half-period mode) and some have
14+a stable state in all steps (quarter-period mode).
1415
1516 The phase diagram of these two outputs look like this:
1617
@@ -32,6 +33,9 @@ The phase diagram of these two outputs look like this: · 15 unmodified lines
3233 |<-->|
3334 one step (half-period mode)
3435
36+ |<>|
37+ one step (quarter-period mode)
38+
3539 For more information, please see
3640 https://en.wikipedia.org/wiki/Rotary_encoder
3741
@@ -109,6 +113,7 @@ static struct rotary_encoder_platform_data my_rotary_encoder_info = { · 71 unmodified lines
109113 .inverted_a = 0,
110114 .inverted_b = 0,
111115 .half_period = false,
116+ .wakeup_source = false,
112117 };
113118
114119 static struct platform_device rotary_encoder_device = {
Documentation/input/userio.txt+70−0
@@ -0,0 +1,70 @@
1+ The userio Protocol
2+ (c) 2015 Stephen Chandler Paul <thatslyude@gmail.com>
3+ Sponsored by Red Hat
4+--------------------------------------------------------------------------------
5+
6+1. Introduction
7+~~~~~~~~~~~~~~~
8+ This module is intended to try to make the lives of input driver developers
9+easier by allowing them to test various serio devices (mainly the various
10+touchpads found on laptops) without having to have the physical device in front
11+of them. userio accomplishes this by allowing any privileged userspace program
12+to directly interact with the kernel's serio driver and control a virtual serio
13+port from there.
14+
15+2. Usage overview
16+~~~~~~~~~~~~~~~~~
17+ In order to interact with the userio kernel module, one simply opens the
18+/dev/userio character device in their applications. Commands are sent to the
19+kernel module by writing to the device, and any data received from the serio
20+driver is read as-is from the /dev/userio device. All of the structures and
21+macros you need to interact with the device are defined in <linux/userio.h> and
22+<linux/serio.h>.
23+
24+3. Command Structure
25+~~~~~~~~~~~~~~~~~~~~
26+ The struct used for sending commands to /dev/userio is as follows:
27+
28+ struct userio_cmd {
29+ __u8 type;
30+ __u8 data;
31+ };
32+
33+ "type" describes the type of command that is being sent. This can be any one
34+of the USERIO_CMD macros defined in <linux/userio.h>. "data" is the argument
35+that goes along with the command. In the event that the command doesn't have an
36+argument, this field can be left untouched and will be ignored by the kernel.
37+Each command should be sent by writing the struct directly to the character
38+device. In the event that the command you send is invalid, an error will be
39+returned by the character device and a more descriptive error will be printed
40+to the kernel log. Only one command can be sent at a time, any additional data
41+written to the character device after the initial command will be ignored.
42+ To close the virtual serio port, just close /dev/userio.
43+
44+4. Commands
45+~~~~~~~~~~~
46+
47+4.1 USERIO_CMD_REGISTER
48+~~~~~~~~~~~~~~~~~~~~~~~
49+ Registers the port with the serio driver and begins transmitting data back and
50+forth. Registration can only be performed once a port type is set with
51+USERIO_CMD_SET_PORT_TYPE. Has no argument.
52+
53+4.2 USERIO_CMD_SET_PORT_TYPE
54+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55+ Sets the type of port we're emulating, where "data" is the port type being
56+set. Can be any of the macros from <linux/serio.h>. For example: SERIO_8042
57+would set the port type to be a normal PS/2 port.
58+
59+4.3 USERIO_CMD_SEND_INTERRUPT
60+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
61+ Sends an interrupt through the virtual serio port to the serio driver, where
62+"data" is the interrupt data being sent.
63+
64+5. Userspace tools
65+~~~~~~~~~~~~~~~~~~
66+ The userio userspace tools are able to record PS/2 devices using some of the
67+debugging information from i8042, and play back the devices on /dev/userio. The
68+latest version of these tools can be found at:
69+
70+ https://github.com/Lyude/ps2emu
Documentation/ioctl/ioctl-number.txt+4−0
@@ -81,6 +81,9 @@ Code Seq#(hex) Include File Comments · 80 unmodified lines
8181 0x22 all scsi/sg.h
8282 '#' 00-3F IEEE 1394 Subsystem Block for the entire subsystem
8383 '$' 00-0F linux/perf_counter.h, linux/perf_event.h
84+'%' 00-0F include/uapi/linux/stm.h
85+ System Trace Module subsystem
86+ <mailto:alexander.shishkin@linux.intel.com>
8487 '&' 00-07 drivers/firewire/nosy-user.h
8588 '1' 00-1F <linux/timepps.h> PPS kit from Ulrich Windl
8689 <ftp://ftp.de.kernel.org/pub/linux/daemons/ntp/PPS/>
@@ -149,6 +152,7 @@ Code Seq#(hex) Include File Comments · 62 unmodified lines
149152 'K' all linux/kd.h
150153 'L' 00-1F linux/loop.h conflict!
151154 'L' 10-1F drivers/scsi/mpt2sas/mpt2sas_ctl.h conflict!
155+'L' 20-2F linux/lightnvm.h
152156 'L' E0-FF linux/ppdd.h encrypted disk device driver
153157 <http://linux01.gwdg.de/~alatham/ppdd.html>
154158 'M' all linux/soundcard.h conflict!
Documentation/kasan.txt+23−23
@@ -1,36 +1,34 @@
1−Kernel address sanitizer
2−================
1+KernelAddressSanitizer (KASAN)
2+==============================
33
44 0. Overview
55 ===========
66
7−Kernel Address sanitizer (KASan) is a dynamic memory error detector. It provides
7+KernelAddressSANitizer (KASAN) is a dynamic memory error detector. It provides
88 a fast and comprehensive solution for finding use-after-free and out-of-bounds
99 bugs.
1010
11−KASan uses compile-time instrumentation for checking every memory access,
12−therefore you will need a gcc version of 4.9.2 or later. KASan could detect out
13−of bounds accesses to stack or global variables, but only if gcc 5.0 or later was
14−used to built the kernel.
11+KASAN uses compile-time instrumentation for checking every memory access,
12+therefore you will need a GCC version 4.9.2 or later. GCC 5.0 or later is
13+required for detection of out-of-bounds accesses to stack or global variables.
1514
16−Currently KASan is supported only for x86_64 architecture and requires that the
17−kernel be built with the SLUB allocator.
15+Currently KASAN is supported only for x86_64 architecture and requires the
16+kernel to be built with the SLUB allocator.
1817
1918 1. Usage
20−=========
19+========
2120
2221 To enable KASAN configure kernel with:
2322
2423 CONFIG_KASAN = y
2524
26−and choose between CONFIG_KASAN_OUTLINE and CONFIG_KASAN_INLINE. Outline/inline
27−is compiler instrumentation types. The former produces smaller binary the
28−latter is 1.1 - 2 times faster. Inline instrumentation requires a gcc version
29−of 5.0 or later.
25+and choose between CONFIG_KASAN_OUTLINE and CONFIG_KASAN_INLINE. Outline and
26+inline are compiler instrumentation types. The former produces smaller binary
27+the latter is 1.1 - 2 times faster. Inline instrumentation requires a GCC
28+version 5.0 or later.
3029
3130 Currently KASAN works only with the SLUB memory allocator.
32−For better bug detection and nicer report, enable CONFIG_STACKTRACE and put
33−at least 'slub_debug=U' in the boot cmdline.
31+For better bug detection and nicer reporting, enable CONFIG_STACKTRACE.
3432
3533 To disable instrumentation for specific files or directories, add a line
3634 similar to the following to the respective kernel Makefile:
@@ -42,7 +40,7 @@ similar to the following to the respective kernel Makefile: · 5 unmodified lines
4240 KASAN_SANITIZE := n
4341
4442 1.1 Error reports
45−==========
43+=================
4644
4745 A typical out of bounds access report looks like this:
4846
@@ -119,14 +117,16 @@ Memory state around the buggy address: · 70 unmodified lines
119117 ffff8800693bc800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
120118 ==================================================================
121119
122−First sections describe slub object where bad access happened.
123−See 'SLUB Debug output' section in Documentation/vm/slub.txt for details.
120+The header of the report discribe what kind of bug happened and what kind of
121+access caused it. It's followed by the description of the accessed slub object
122+(see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and
123+the description of the accessed memory page.
124124
125125 In the last section the report shows memory state around the accessed address.
126−Reading this part requires some more understanding of how KASAN works.
126+Reading this part requires some understanding of how KASAN works.
127127
128−Each 8 bytes of memory are encoded in one shadow byte as accessible,
129−partially accessible, freed or they can be part of a redzone.
128+The state of each 8 aligned bytes of memory is encoded in one shadow byte.
129+Those 8 bytes can be accessible, partially accessible, freed or be a redzone.
130130 We use the following encoding for each shadow byte: 0 means that all 8 bytes
131131 of the corresponding memory region are accessible; number N (1 <= N <= 7) means
132132 that the first N bytes are accessible, and other (8 - N) bytes are not;
@@ -139,7 +139,7 @@ the accessed address is partially accessible. · 6 unmodified lines
139139
140140
141141 2. Implementation details
142−========================
142+=========================
143143
144144 From a high level, our approach to memory error detection is similar to that
145145 of kmemcheck: use shadow memory to record whether each byte of memory is safe
Documentation/kbuild/Kconfig.recursion-issue-01+57−0
@@ -0,0 +1,57 @@
1+# Simple Kconfig recursive issue
2+# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3+#
4+# Test with:
5+#
6+# make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
7+#
8+# This Kconfig file has a simple recursive dependency issue. In order to
9+# understand why this recursive dependency issue occurs lets consider what
10+# Kconfig needs to address. We iterate over what Kconfig needs to address
11+# by stepping through the questions it needs to address sequentially.
12+#
13+# * What values are possible for CORE?
14+#
15+# CORE_BELL_A_ADVANCED selects CORE, which means that it influences the values
16+# that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
17+# CORE must be 'y' too.
18+#
19+# * What influences CORE_BELL_A_ADVANCED ?
20+#
21+# As the name implies CORE_BELL_A_ADVANCED is an advanced feature of
22+# CORE_BELL_A so naturally it depends on CORE_BELL_A. So if CORE_BELL_A is 'y'
23+# we know CORE_BELL_A_ADVANCED can be 'y' too.
24+#
25+# * What influences CORE_BELL_A ?
26+#
27+# CORE_BELL_A depends on CORE, so CORE influences CORE_BELL_A.
28+#
29+# But that is a problem, because this means that in order to determine
30+# what values are possible for CORE we ended up needing to address questions
31+# regarding possible values of CORE itself again. Answering the original
32+# question of what are the possible values of CORE would make the kconfig
33+# tools run in a loop. When this happens Kconfig exits and complains about
34+# the "recursive dependency detected" error.
35+#
36+# Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
37+# obvious that an easy to solution to this problem should just be the removal
38+# of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already
39+# since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
40+# so trivial to resolve, we provide another example below of practical
41+# implications of this recursive issue where the solution is perhaps not so
42+# easy to understand. Note that matching semantics on the dependency on
43+# CORE also consist of a solution to this recursive problem.
44+
45+mainmenu "Simple example to demo kconfig recursive dependency issue"
46+
47+config CORE
48+ tristate
49+
50+config CORE_BELL_A
51+ tristate
52+ depends on CORE
53+
54+config CORE_BELL_A_ADVANCED
55+ tristate
56+ depends on CORE_BELL_A
57+ select CORE
Documentation/kbuild/Kconfig.recursion-issue-02+63−0
@@ -0,0 +1,63 @@
1+# Cumulative Kconfig recursive issue
2+# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3+#
4+# Test with:
5+#
6+# make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
7+#
8+# The recursive limitations with Kconfig has some non intuitive implications on
9+# kconfig sematics which are documented here. One known practical implication
10+# of the recursive limitation is that drivers cannot negate features from other
11+# drivers if they share a common core requirement and use disjoint semantics to
12+# annotate those requirements, ie, some drivers use "depends on" while others
13+# use "select". For instance it means if a driver A and driver B share the same
14+# core requirement, and one uses "select" while the other uses "depends on" to
15+# annotate this, all features that driver A selects cannot now be negated by
16+# driver B.
17+#
18+# A perhaps not so obvious implication of this is that, if semantics on these
19+# core requirements are not carefully synced, as drivers evolve features
20+# they select or depend on end up becoming shared requirements which cannot be
21+# negated by other drivers.
22+#
23+# The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
24+# describes a simple driver core layout of example features a kernel might
25+# have. Let's assume we have some CORE functionality, then the kernel has a
26+# series of bells and whistles it desires to implement, its not so advanced so
27+# it only supports bells at this time: CORE_BELL_A and CORE_BELL_B. If
28+# CORE_BELL_A has some advanced feature CORE_BELL_A_ADVANCED which selects
29+# CORE_BELL_A then CORE_BELL_A ends up becoming a common BELL feature which
30+# other bells in the system cannot negate. The reason for this issue is
31+# due to the disjoint use of semantics on expressing each bell's relationship
32+# with CORE, one uses "depends on" while the other uses "select". Another
33+# more important reason is that kconfig does not check for dependencies listed
34+# under 'select' for a symbol, when such symbols are selected kconfig them
35+# as mandatory required symbols. For more details on the heavy handed nature
36+# of select refer to Documentation/kbuild/Kconfig.select-break
37+#
38+# To fix this the "depends on CORE" must be changed to "select CORE", or the
39+# "select CORE" must be changed to "depends on CORE".
40+#
41+# For an example real world scenario issue refer to the attempt to remove
42+# "select FW_LOADER" [0], in the end the simple alternative solution to this
43+# problem consisted on matching semantics with newly introduced features.
44+#
45+# [0] http://lkml.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com
46+
47+mainmenu "Simple example to demo cumulative kconfig recursive dependency implication"
48+
49+config CORE
50+ tristate
51+
52+config CORE_BELL_A
53+ tristate
54+ depends on CORE
55+
56+config CORE_BELL_A_ADVANCED
57+ tristate
58+ select CORE_BELL_A
59+
60+config CORE_BELL_B
61+ tristate
62+ depends on !CORE_BELL_A
63+ select CORE
Documentation/kbuild/Kconfig.select-break+33−0
@@ -0,0 +1,33 @@
1+# Select broken dependency issue
2+# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3+#
4+# Test with:
5+#
6+# make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.select-break menuconfig
7+#
8+# kconfig will not complain and enable this layout for configuration. This is
9+# currently a feature of kconfig, given select was designed to be heavy handed.
10+# Kconfig currently does not check the list of symbols listed on a symbol's
11+# "select" list, this is done on purpose to help load a set of known required
12+# symbols. Because of this use of select should be used with caution. An
13+# example of this issue is below.
14+#
15+# The option B and C are clearly contradicting with respect to A.
16+# However, when A is set, C can be set as well because Kconfig does not
17+# visit the dependencies of the select target (in this case B). And since
18+# Kconfig does not visit the dependencies, it breaks the dependencies of B
19+# (!A).
20+
21+mainmenu "Simple example to demo kconfig select broken dependency issue"
22+
23+config A
24+ bool "CONFIG A"
25+
26+config B
27+ bool "CONFIG B"
28+ depends on !A
29+
30+config C
31+ bool "CONFIG C"
32+ depends on A
33+ select B
Documentation/kbuild/kconfig-language.txt+161−0
@@ -393,3 +393,164 @@ config FOO · 392 unmodified lines
393393 depends on BAR && m
394394
395395 limits FOO to module (=m) or disabled (=n).
396+
397+Kconfig recursive dependency limitations
398+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
399+
400+If you've hit the Kconfig error: "recursive dependency detected" you've run
401+into a recursive dependency issue with Kconfig, a recursive dependency can be
402+summarized as a circular dependency. The kconfig tools need to ensure that
403+Kconfig files comply with specified configuration requirements. In order to do
404+that kconfig must determine the values that are possible for all Kconfig
405+symbols, this is currently not possible if there is a circular relation
406+between two or more Kconfig symbols. For more details refer to the "Simple
407+Kconfig recursive issue" subsection below. Kconfig does not do recursive
408+dependency resolution; this has a few implications for Kconfig file writers.
409+We'll first explain why this issues exists and then provide an example
410+technical limitation which this brings upon Kconfig developers. Eager
411+developers wishing to try to address this limitation should read the next
412+subsections.
413+
414+Simple Kconfig recursive issue
415+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
416+
417+Read: Documentation/kbuild/Kconfig.recursion-issue-01
418+
419+Test with:
420+
421+make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
422+
423+Cumulative Kconfig recursive issue
424+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
425+
426+Read: Documentation/kbuild/Kconfig.recursion-issue-02
427+
428+Test with:
429+
430+make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
431+
432+Practical solutions to kconfig recursive issue
433+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
434+
435+Developers who run into the recursive Kconfig issue have three options
436+at their disposal. We document them below and also provide a list of
437+historical issues resolved through these different solutions.
438+
439+ a) Remove any superfluous "select FOO" or "depends on FOO"
440+ b) Match dependency semantics:
441+ b1) Swap all "select FOO" to "depends on FOO" or,
442+ b2) Swap all "depends on FOO" to "select FOO"
443+
444+The resolution to a) can be tested with the sample Kconfig file
445+Documentation/kbuild/Kconfig.recursion-issue-01 through the removal
446+of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already
447+since CORE_BELL_A depends on CORE. At times it may not be possible to remove
448+some dependency criteria, for such cases you can work with solution b).
449+
450+The two different resolutions for b) can be tested in the sample Kconfig file
451+Documentation/kbuild/Kconfig.recursion-issue-02.
452+
453+Below is a list of examples of prior fixes for these types of recursive issues;
454+all errors appear to involve one or more select's and one or more "depends on".
455+
456+commit fix
457+====== ===
458+06b718c01208 select A -> depends on A
459+c22eacfe82f9 depends on A -> depends on B
460+6a91e854442c select A -> depends on A
461+118c565a8f2e select A -> select B
462+f004e5594705 select A -> depends on A
463+c7861f37b4c6 depends on A -> (null)
464+80c69915e5fb select A -> (null) (1)
465+c2218e26c0d0 select A -> depends on A (1)
466+d6ae99d04e1c select A -> depends on A
467+95ca19cf8cbf select A -> depends on A
468+8f057d7bca54 depends on A -> (null)
469+8f057d7bca54 depends on A -> select A
470+a0701f04846e select A -> depends on A
471+0c8b92f7f259 depends on A -> (null)
472+e4e9e0540928 select A -> depends on A (2)
473+7453ea886e87 depends on A > (null) (1)
474+7b1fff7e4fdf select A -> depends on A
475+86c747d2a4f0 select A -> depends on A
476+d9f9ab51e55e select A -> depends on A
477+0c51a4d8abd6 depends on A -> select A (3)
478+e98062ed6dc4 select A -> depends on A (3)
479+91e5d284a7f1 select A -> (null)
480+
481+(1) Partial (or no) quote of error.
482+(2) That seems to be the gist of that fix.
483+(3) Same error.
484+
485+Future kconfig work
486+~~~~~~~~~~~~~~~~~~~
487+
488+Work on kconfig is welcomed on both areas of clarifying semantics and on
489+evaluating the use of a full SAT solver for it. A full SAT solver can be
490+desirable to enable more complex dependency mappings and / or queries,
491+for instance on possible use case for a SAT solver could be that of handling
492+the current known recursive dependency issues. It is not known if this would
493+address such issues but such evaluation is desirable. If support for a full SAT
494+solver proves too complex or that it cannot address recursive dependency issues
495+Kconfig should have at least clear and well defined semantics which also
496+addresses and documents limitations or requirements such as the ones dealing
497+with recursive dependencies.
498+
499+Further work on both of these areas is welcomed on Kconfig. We elaborate
500+on both of these in the next two subsections.
501+
502+Semantics of Kconfig
503+~~~~~~~~~~~~~~~~~~~~
504+
505+The use of Kconfig is broad, Linux is now only one of Kconfig's users:
506+one study has completed a broad analysis of Kconfig use in 12 projects [0].
507+Despite its widespread use, and although this document does a reasonable job
508+in documenting basic Kconfig syntax a more precise definition of Kconfig
509+semantics is welcomed. One project deduced Kconfig semantics through
510+the use of the xconfig configurator [1]. Work should be done to confirm if
511+the deduced semantics matches our intended Kconfig design goals.
512+
513+Having well defined semantics can be useful for tools for practical
514+evaluation of depenencies, for instance one such use known case was work to
515+express in boolean abstraction of the inferred semantics of Kconfig to
516+translate Kconfig logic into boolean formulas and run a SAT solver on this to
517+find dead code / features (always inactive), 114 dead features were found in
518+Linux using this methodology [1] (Section 8: Threats to validity).
519+
520+Confirming this could prove useful as Kconfig stands as one of the the leading
521+industrial variability modeling languages [1] [2]. Its study would help
522+evaluate practical uses of such languages, their use was only theoretical
523+and real world requirements were not well understood. As it stands though
524+only reverse engineering techniques have been used to deduce semantics from
525+variability modeling languages such as Kconfig [3].
526+
527+[0] http://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf
528+[1] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
529+[2] http://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf
530+[3] http://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf
531+
532+Full SAT solver for Kconfig
533+~~~~~~~~~~~~~~~~~~~~~~~~~~~
534+
535+Although SAT solvers [0] haven't yet been used by Kconfig directly, as noted in
536+the previous subsection, work has been done however to express in boolean
537+abstraction the inferred semantics of Kconfig to translate Kconfig logic into
538+boolean formulas and run a SAT solver on it [1]. Another known related project
539+is CADOS [2] (former VAMOS [3]) and the tools, mainly undertaker [4], which has
540+been introduced first with [5]. The basic concept of undertaker is to exract
541+variability models from Kconfig, and put them together with a propositional
542+formula extracted from CPP #ifdefs and build-rules into a SAT solver in order
543+to find dead code, dead files, and dead symbols. If using a SAT solver is
544+desirable on Kconfig one approach would be to evaluate repurposing such efforts
545+somehow on Kconfig. There is enough interest from mentors of existing projects
546+to not only help advise how to integrate this work upstream but also help
547+maintain it long term. Interested developers should visit:
548+
549+http://kernelnewbies.org/KernelProjects/kconfig-sat
550+
551+[0] http://www.cs.cornell.edu/~sabhar/chapters/SATSolvers-KR-Handbook.pdf
552+[1] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
553+[2] https://cados.cs.fau.de
554+[3] https://vamos.cs.fau.de
555+[4] https://undertaker.cs.fau.de
556+[5] https://www4.cs.fau.de/Publications/2011/tartler_11_eurosys.pdf
Documentation/kernel-docs.txt+7−7
@@ -696,18 +696,18 @@ · 695 unmodified lines
696696 Memory related patches, HOWTOs, links, mm developers... Don't miss
697697 it if you are interested in memory management development!
698698
699− * Name: "Kernel Newbies IRC Channel"
699+ * Name: "Kernel Newbies IRC Channel and Website"
700700 URL: http://www.kernelnewbies.org
701701 Keywords: IRC, newbies, channel, asking doubts.
702− Description: #kernelnewbies on irc.openprojects.net. From the web
703− page: "#kernelnewbies is an IRC network dedicated to the 'newbie'
702+ Description: #kernelnewbies on irc.oftc.net.
703+ #kernelnewbies is an IRC network dedicated to the 'newbie'
704704 kernel hacker. The audience mostly consists of people who are
705705 learning about the kernel, working on kernel projects or
706706 professional kernel hackers that want to help less seasoned kernel
707− people. [...] #kernelnewbies is on the Open Projects IRC Network,
708− try irc.openprojects.net or irc.<country>.openprojects.net as your
709− server and then /join #kernelnewbies". It also hosts articles,
710− documents, FAQs...
707+ people.
708+ #kernelnewbies is on the OFTC IRC Network.
709+ Try irc.oftc.net as your server and then /join #kernelnewbies.
710+ The kernelnewbies website also hosts articles, documents, FAQs...
711711
712712 * Name: "linux-kernel mailing list archives and search engines"
713713 URL: http://vger.kernel.org/vger-lists.html
Documentation/kernel-parameters.txt+48−9
@@ -167,7 +167,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 166 unmodified lines
167167
168168 acpi= [HW,ACPI,X86,ARM64]
169169 Advanced Configuration and Power Interface
170− Format: { force | off | strict | noirq | rsdt }
170+ Format: { force | off | strict | noirq | rsdt |
171+ copy_dsdt }
171172 force -- enable ACPI if default was off
172173 off -- disable ACPI if default was on
173174 noirq -- do not use ACPI for IRQ routing
@@ -789,8 +790,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 615 unmodified lines
789790 is passed, kernel could allocate physical memory region
790791 above 4G, that cause second kernel crash on system
791792 that require some amount of low memory, e.g. swiotlb
792− requires at least 64M+32K low memory. Kernel would
793− try to allocate 72M below 4G automatically.
793+ requires at least 64M+32K low memory, also enough extra
794+ low memory is needed to make sure DMA buffers for 32-bit
795+ devices won't run out. Kernel would try to allocate at
796+ at least 256M below 4G automatically.
794797 This one let user to specify own low range under 4G
795798 for second kernel instead.
796799 0: to disable low allocation.
@@ -974,6 +977,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 177 unmodified lines
974977
975978 earlycon= [KNL] Output early console device and options.
976979
980+ When used with no options, the early console is
981+ determined by the stdout-path property in device
982+ tree's chosen node.
983+
977984 cdns,<addr>
978985 Start an early, polled-mode console on a cadence serial
979986 port at the specified address. The cadence serial port
@@ -1026,6 +1033,13 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 46 unmodified lines
10261033 serial port must already be setup and configured.
10271034 Options are not yet supported.
10281035
1036+ lpuart,<addr>
1037+ lpuart32,<addr>
1038+ Use early console provided by Freescale LP UART driver
1039+ found on Freescale Vybrid and QorIQ LS1021A processors.
1040+ A valid base address must be provided, and the serial
1041+ port must already be setup and configured.
1042+
10291043 earlyprintk= [X86,SH,BLACKFIN,ARM,M68k]
10301044 earlyprintk=vga
10311045 earlyprintk=efi
@@ -1097,6 +1111,21 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 65 unmodified lines
10971111 you are really sure that your UEFI does sane gc and
10981112 fulfills the spec otherwise your board may brick.
10991113
1114+ efi_fake_mem= nn[KMG]@ss[KMG]:aa[,nn[KMG]@ss[KMG]:aa,..] [EFI; X86]
1115+ Add arbitrary attribute to specific memory range by
1116+ updating original EFI memory map.
1117+ Region of memory which aa attribute is added to is
1118+ from ss to ss+nn.
1119+ If efi_fake_mem=2G@4G:0x10000,2G@0x10a0000000:0x10000
1120+ is specified, EFI_MEMORY_MORE_RELIABLE(0x10000)
1121+ attribute is added to range 0x100000000-0x180000000 and
1122+ 0x10a0000000-0x1120000000.
1123+
1124+ Using this parameter you can do debugging of EFI memmap
1125+ related feature. For example, you can do debugging of
1126+ Address Range Mirroring feature even if your box
1127+ doesn't support it.
1128+
11001129 eisa_irq_edge= [PARISC,HW]
11011130 See header of drivers/parisc/eisa.c.
11021131
@@ -1249,6 +1278,11 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 146 unmodified lines
12491278 Format: <unsigned int> such that (rxsize & ~0x1fffc0) == 0.
12501279 Default: 1024
12511280
1281+ hardlockup_all_cpu_backtrace=
1282+ [KNL] Should the hard-lockup detector generate
1283+ backtraces on all cpus.
1284+ Format: <integer>
1285+
12521286 hashdist= [KNL,NUMA] Large hashes allocated during boot
12531287 are distributed across NUMA nodes. Defaults on
12541288 for 64-bit NUMA, off otherwise.
@@ -1556,6 +1590,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 301 unmodified lines
15561590 nosid disable Source ID checking
15571591 no_x2apic_optout
15581592 BIOS x2APIC opt-out request will be ignored
1593+ nopost disable Interrupt Posting
15591594
15601595 iomem= Disable strict checking of access to MMIO memory
15611596 strict regions from userspace.
@@ -2317,11 +2352,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 755 unmodified lines
23172352 nmi_watchdog= [KNL,BUGS=X86] Debugging features for SMP kernels
23182353 Format: [panic,][nopanic,][num]
23192354 Valid num: 0 or 1
2320− 0 - turn nmi_watchdog off
2321− 1 - turn nmi_watchdog on
2355+ 0 - turn hardlockup detector in nmi_watchdog off
2356+ 1 - turn hardlockup detector in nmi_watchdog on
23222357 When panic is specified, panic when an NMI watchdog
23232358 timeout occurs (or 'nopanic' to override the opposite
2324− default).
2359+ default). To disable both hard and soft lockup detectors,
2360+ please see 'nowatchdog'.
23252361 This is useful when you use a panic=... timeout and
23262362 need the box quickly up again.
23272363
@@ -3077,9 +3113,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted. · 749 unmodified lines
30773113 cache-to-cache transfer latencies.
30783114
30793115 rcutree.rcu_fanout_leaf= [KNL]
3080− Increase the number of CPUs assigned to each
3081− leaf rcu_node structure. Useful for very large
3082− systems.
3116+ Change the number of CPUs assigned to each
3117+ leaf rcu_node structure. Useful for very
3118+ large systems, which will choose the value 64,
3119+ and for NUMA systems with large remote-access
3120+ latencies, which will choose a value aligned
3121+ with the appropriate hardware boundaries.
30833122
30843123 rcutree.jiffies_till_sched_qs= [KNL]
30853124 Set required age in jiffies for a
Documentation/kselftest.txt+16−0
@@ -54,6 +54,22 @@ To run the hotplug tests: · 53 unmodified lines
5454 - note that some tests will require root privileges.
5555
5656
57+Install selftests
58+=================
59+
60+You can use kselftest_install.sh tool installs selftests in default
61+location which is tools/testing/selftests/kselftest or an user specified
62+location.
63+
64+To install selftests in default location:
65+ $ cd tools/testing/selftests
66+ $ ./kselftest_install.sh
67+
68+To install selftests in an user specified location:
69+ $ cd tools/testing/selftests
70+ $ ./kselftest_install.sh install_dir
71+
72+
5773 Contributing new tests
5874 ======================
5975
Documentation/locking/lockstat.txt+1−1
@@ -12,7 +12,7 @@ Because things like lock contention can severely impact performance. · 11 unmodified lines
1212 - HOW
1313
1414 Lockdep already has hooks in the lock functions and maps lock instances to
15−lock classes. We build on that (see Documentation/lokcing/lockdep-design.txt).
15+lock classes. We build on that (see Documentation/locking/lockdep-design.txt).
1616 The graph below shows the relation between the lock functions and the various
1717 hooks therein.
1818
Documentation/locking/locktorture.txt+3−0
@@ -52,6 +52,9 @@ torture_type Type of lock to torture. By default, only spinlocks will · 51 unmodified lines
5252
5353 o "mutex_lock": mutex_lock() and mutex_unlock() pairs.
5454
55+ o "rtmutex_lock": rtmutex_lock() and rtmutex_unlock()
56+ pairs. Kernel must have CONFIG_RT_MUTEX=y.
57+
5558 o "rwsem_lock": read/write down() and up() semaphore pairs.
5659
5760 torture_runnable Start locktorture at boot time in the case where the
Documentation/lockup-watchdogs.txt+3−2
@@ -20,8 +20,9 @@ kernel mode for more than 10 seconds (see "Implementation" below for · 19 unmodified lines
2020 details), without letting other interrupts have a chance to run.
2121 Similarly to the softlockup case, the current stack trace is displayed
2222 upon detection and the system will stay locked up unless the default
23−behavior is changed, which can be done through a compile time knob,
24−"BOOTPARAM_HARDLOCKUP_PANIC", and a kernel parameter, "nmi_watchdog"
23+behavior is changed, which can be done through a sysctl,
24+'hardlockup_panic', a compile time knob, "BOOTPARAM_HARDLOCKUP_PANIC",
25+and a kernel parameter, "nmi_watchdog"
2526 (see "Documentation/kernel-parameters.txt" for details).
2627
2728 The panic option can be used in combination with panic_timeout (this
Documentation/memory-barriers.txt+33−32
@@ -617,16 +617,16 @@ case what's actually required is: · 616 unmodified lines
617617 However, stores are not speculated. This means that ordering -is- provided
618618 for load-store control dependencies, as in the following example:
619619
620− q = READ_ONCE_CTRL(a);
620+ q = READ_ONCE(a);
621621 if (q) {
622622 WRITE_ONCE(b, p);
623623 }
624624
625625 Control dependencies pair normally with other types of barriers. That
626−said, please note that READ_ONCE_CTRL() is not optional! Without the
627−READ_ONCE_CTRL(), the compiler might combine the load from 'a' with
628−other loads from 'a', and the store to 'b' with other stores to 'b',
629−with possible highly counterintuitive effects on ordering.
626+said, please note that READ_ONCE() is not optional! Without the
627+READ_ONCE(), the compiler might combine the load from 'a' with other
628+loads from 'a', and the store to 'b' with other stores to 'b', with
629+possible highly counterintuitive effects on ordering.
630630
631631 Worse yet, if the compiler is able to prove (say) that the value of
632632 variable 'a' is always non-zero, it would be well within its rights
@@ -636,15 +636,12 @@ as follows: · 3 unmodified lines
636636 q = a;
637637 b = p; /* BUG: Compiler and CPU can both reorder!!! */
638638
639−Finally, the READ_ONCE_CTRL() includes an smp_read_barrier_depends()
640−that DEC Alpha needs in order to respect control depedencies.
641−
642−So don't leave out the READ_ONCE_CTRL().
639+So don't leave out the READ_ONCE().
643640
644641 It is tempting to try to enforce ordering on identical stores on both
645642 branches of the "if" statement as follows:
646643
647− q = READ_ONCE_CTRL(a);
644+ q = READ_ONCE(a);
648645 if (q) {
649646 barrier();
650647 WRITE_ONCE(b, p);
@@ -658,7 +655,7 @@ branches of the "if" statement as follows: · 7 unmodified lines
658655 Unfortunately, current compilers will transform this as follows at high
659656 optimization levels:
660657
661− q = READ_ONCE_CTRL(a);
658+ q = READ_ONCE(a);
662659 barrier();
663660 WRITE_ONCE(b, p); /* BUG: No ordering vs. load from a!!! */
664661 if (q) {
@@ -688,7 +685,7 @@ memory barriers, for example, smp_store_release(): · 23 unmodified lines
688685 In contrast, without explicit memory barriers, two-legged-if control
689686 ordering is guaranteed only when the stores differ, for example:
690687
691− q = READ_ONCE_CTRL(a);
688+ q = READ_ONCE(a);
692689 if (q) {
693690 WRITE_ONCE(b, p);
694691 do_something();
@@ -697,14 +694,14 @@ ordering is guaranteed only when the stores differ, for example: · 2 unmodified lines
697694 do_something_else();
698695 }
699696
700−The initial READ_ONCE_CTRL() is still required to prevent the compiler
701−from proving the value of 'a'.
697+The initial READ_ONCE() is still required to prevent the compiler from
698+proving the value of 'a'.
702699
703700 In addition, you need to be careful what you do with the local variable 'q',
704701 otherwise the compiler might be able to guess the value and again remove
705702 the needed conditional. For example:
706703
707− q = READ_ONCE_CTRL(a);
704+ q = READ_ONCE(a);
708705 if (q % MAX) {
709706 WRITE_ONCE(b, p);
710707 do_something();
@@ -717,7 +714,7 @@ If MAX is defined to be 1, then the compiler knows that (q % MAX) is · 6 unmodified lines
717714 equal to zero, in which case the compiler is within its rights to
718715 transform the above code into the following:
719716
720− q = READ_ONCE_CTRL(a);
717+ q = READ_ONCE(a);
721718 WRITE_ONCE(b, p);
722719 do_something_else();
723720
@@ -728,7 +725,7 @@ is gone, and the barrier won't bring it back. Therefore, if you are · 4 unmodified lines
728725 relying on this ordering, you should make sure that MAX is greater than
729726 one, perhaps as follows:
730727
731− q = READ_ONCE_CTRL(a);
728+ q = READ_ONCE(a);
732729 BUILD_BUG_ON(MAX <= 1); /* Order load from a with store to b. */
733730 if (q % MAX) {
734731 WRITE_ONCE(b, p);
@@ -745,7 +742,7 @@ of the 'if' statement. · 10 unmodified lines
745742 You must also be careful not to rely too much on boolean short-circuit
746743 evaluation. Consider this example:
747744
748− q = READ_ONCE_CTRL(a);
745+ q = READ_ONCE(a);
749746 if (q || 1 > 0)
750747 WRITE_ONCE(b, 1);
751748
@@ -753,7 +750,7 @@ Because the first condition cannot fault and the second condition is · 1 unmodified line
753750 always true, the compiler can transform this example as following,
754751 defeating control dependency:
755752
756− q = READ_ONCE_CTRL(a);
753+ q = READ_ONCE(a);
757754 WRITE_ONCE(b, 1);
758755
759756 This example underscores the need to ensure that the compiler cannot
@@ -767,7 +764,7 @@ x and y both being zero: · 7 unmodified lines
767764
768765 CPU 0 CPU 1
769766 ======================= =======================
770− r1 = READ_ONCE_CTRL(x); r2 = READ_ONCE_CTRL(y);
767+ r1 = READ_ONCE(x); r2 = READ_ONCE(y);
771768 if (r1 > 0) if (r2 > 0)
772769 WRITE_ONCE(y, 1); WRITE_ONCE(x, 1);
773770
@@ -796,11 +793,6 @@ site: https://www.cl.cam.ac.uk/~pes20/ppcmem/index.html. · 22 unmodified lines
796793
797794 In summary:
798795
799− (*) Control dependencies must be headed by READ_ONCE_CTRL().
800− Or, as a much less preferable alternative, interpose
801− smp_read_barrier_depends() between a READ_ONCE() and the
802− control-dependent write.
803−
804796 (*) Control dependencies can order prior loads against later stores.
805797 However, they do -not- guarantee any other sort of ordering:
806798 Not prior loads against later loads, nor prior stores against
@@ -816,14 +808,13 @@ In summary: · 9 unmodified lines
816808 between the prior load and the subsequent store, and this
817809 conditional must involve the prior load. If the compiler is able
818810 to optimize the conditional away, it will have also optimized
819− away the ordering. Careful use of READ_ONCE_CTRL() READ_ONCE(),
820− and WRITE_ONCE() can help to preserve the needed conditional.
811+ away the ordering. Careful use of READ_ONCE() and WRITE_ONCE()
812+ can help to preserve the needed conditional.
821813
822814 (*) Control dependencies require that the compiler avoid reordering the
823− dependency into nonexistence. Careful use of READ_ONCE_CTRL()
824− or smp_read_barrier_depends() can help to preserve your control
825− dependency. Please see the Compiler Barrier section for more
826− information.
815+ dependency into nonexistence. Careful use of READ_ONCE() or
816+ atomic{,64}_read() can help to preserve your control dependency.
817+ Please see the Compiler Barrier section for more information.
827818
828819 (*) Control dependencies pair normally with other types of barriers.
829820
@@ -1710,6 +1701,17 @@ There are some more advanced barrier functions: · 880 unmodified lines
17101701 operations" subsection for information on where to use these.
17111702
17121703
1704+ (*) lockless_dereference();
1705+ This can be thought of as a pointer-fetch wrapper around the
1706+ smp_read_barrier_depends() data-dependency barrier.
1707+
1708+ This is also similar to rcu_dereference(), but in cases where
1709+ object lifetime is handled by some mechanism other than RCU, for
1710+ example, when the objects removed only when the system goes down.
1711+ In addition, lockless_dereference() is used in some data structures
1712+ that can be used both with and without RCU.
1713+
1714+
17131715 (*) dma_wmb();
17141716 (*) dma_rmb();
17151717
@@ -1789,7 +1791,6 @@ The Linux kernel has a number of locking constructs: · 73 unmodified lines
17891791 (*) mutexes
17901792 (*) semaphores
17911793 (*) R/W semaphores
1792− (*) RCU
17931794
17941795 In all cases there are variants on "ACQUIRE" operations and "RELEASE" operations
17951796 for each construct. These operations all imply certain barriers:
Documentation/mic/mic_overview.txt+18−13
@@ -28,6 +28,10 @@ The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a · 27 unmodified lines
2828 low level communications API across PCIe currently implemented for MIC.
2929 More details are available at scif_overview.txt.
3030
31+The Coprocessor State Management (COSM) driver on the host allows for
32+boot, shutdown and reset of Intel MIC devices. It communicates with a COSM
33+"client" driver on the MIC cards over SCIF to perform these functions.
34+
3135 Here is a block diagram of the various components described above. The
3236 virtio backends are situated on the host rather than the card given better
3337 single threaded performance for the host compared to MIC, the ability of
@@ -51,19 +55,20 @@ the fact that the virtio block storage backend can only be on the host. · 17 unmodified lines
5155 | | | Virtio over PCIe IOCTLs |
5256 | | +--------------------------+
5357 +-----------+ | | | +-----------+
54−| MIC DMA | | +----------+ | +-----------+ | | MIC DMA |
55−| Driver | | | SCIF | | | SCIF | | | Driver |
56−+-----------+ | +----------+ | +-----------+ | +-----------+
57− | | | | | | |
58−+---------------+ | +-----+-----+ | +-----+-----+ | +---------------+
59−|MIC virtual Bus| | |SCIF HW Bus| | |SCIF HW BUS| | |MIC virtual Bus|
60−+---------------+ | +-----------+ | +-----+-----+ | +---------------+
61− | | | | | | |
62− | +--------------+ | | | +---------------+ |
63− | |Intel MIC | | | | |Intel MIC | |
64− +---|Card Driver +----+ | | |Host Driver | |
65− +--------------+ | +----+---------------+-----+
66− | | |
58+| MIC DMA | | +------+ | +------+ +------+ | | MIC DMA |
59+| Driver | | | SCIF | | | SCIF | | COSM | | | Driver |
60++-----------+ | +------+ | +------+ +--+---+ | +-----------+
61+ | | | | | | | |
62++---------------+ | +------+ | +--+---+ +--+---+ | +----------------+
63+|MIC virtual Bus| | |SCIF | | |SCIF | | COSM | | |MIC virtual Bus |
64++---------------+ | |HW Bus| | |HW Bus| | Bus | | +----------------+
65+ | | +------+ | +--+---+ +------+ | |
66+ | | | | | | | |
67+ | +-----------+---+ | | | +---------------+ |
68+ | |Intel MIC | | | | |Intel MIC | |
69+ +---|Card Driver | | | | |Host Driver | |
70+ +------------+--------+ | +----+---------------+-----+
71+ | | |
6772 +-------------------------------------------------------------+
6873 | |
6974 | PCIe Bus |
Documentation/mic/mpssd/mpss+2−2
@@ -119,10 +119,10 @@ stop() · 118 unmodified lines
119119 # Wait for the cards to go offline
120120 for f in $sysfs/*
121121 do
122− while [ "`cat $f/state`" != "offline" ]
122+ while [ "`cat $f/state`" != "ready" ]
123123 do
124124 sleep 1
125− echo -e "Waiting for "`basename $f`" to go offline"
125+ echo -e "Waiting for "`basename $f`" to become ready"
126126 done
127127 done
128128
Documentation/mic/mpssd/mpssd.c+230−132
@@ -43,7 +43,7 @@ · 42 unmodified lines
4343 #include <linux/mic_common.h>
4444 #include <tools/endian.h>
4545
46−static void init_mic(struct mic_info *mic);
46+static void *init_mic(void *arg);
4747
4848 static FILE *logfp;
4949 static struct mic_info mic_list;
@@ -116,19 +116,18 @@ static struct { · 66 unmodified lines
116116 .num = htole16(MIC_VRING_ENTRIES),
117117 },
118118 #if GSO_ENABLED
119− .host_features = htole32(
119+ .host_features = htole32(
120120 1 << VIRTIO_NET_F_CSUM |
121121 1 << VIRTIO_NET_F_GSO |
122122 1 << VIRTIO_NET_F_GUEST_TSO4 |
123123 1 << VIRTIO_NET_F_GUEST_TSO6 |
124− 1 << VIRTIO_NET_F_GUEST_ECN |
125− 1 << VIRTIO_NET_F_GUEST_UFO),
124+ 1 << VIRTIO_NET_F_GUEST_ECN),
126125 #else
127126 .host_features = 0,
128127 #endif
129128 };
130129
131−static const char *mic_config_dir = "/etc/sysconfig/mic";
130+static const char *mic_config_dir = "/etc/mpss";
132131 static const char *virtblk_backend = "VIRTBLK_BACKEND";
133132 static struct {
134133 struct mic_device_desc dd;
@@ -192,7 +191,7 @@ tap_configure(struct mic_info *mic, char *dev) · 57 unmodified lines
192191 return ret;
193192 }
194193
195− snprintf(ipaddr, IFNAMSIZ, "172.31.%d.254/24", mic->id);
194+ snprintf(ipaddr, IFNAMSIZ, "172.31.%d.254/24", mic->id + 1);
196195
197196 pid = fork();
198197 if (pid == 0) {
@@ -255,8 +254,7 @@ static int tun_alloc(struct mic_info *mic, char *dev) · 56 unmodified lines
255254 return err;
256255 }
257256 #if GSO_ENABLED
258− offload = TUN_F_CSUM | TUN_F_TSO4 | TUN_F_TSO6 |
259− TUN_F_TSO_ECN | TUN_F_UFO;
257+ offload = TUN_F_CSUM | TUN_F_TSO4 | TUN_F_TSO6 | TUN_F_TSO_ECN;
260258
261259 err = ioctl(fd, TUNSETOFFLOAD, offload);
262260 if (err < 0) {
@@ -332,7 +330,6 @@ static struct mic_device_desc *get_device_desc(struct mic_info *mic, int type) · 69 unmodified lines
332330 return d;
333331 }
334332 mpsslog("%s %s %d not found\n", mic->name, __func__, type);
335− assert(0);
336333 return NULL;
337334 }
338335
@@ -415,6 +412,13 @@ mic_virtio_copy(struct mic_info *mic, int fd, · 76 unmodified lines
415412 return ret;
416413 }
417414
415+static inline unsigned _vring_size(unsigned int num, unsigned long align)
416+{
417+ return ((sizeof(struct vring_desc) * num + sizeof(__u16) * (3 + num)
418+ + align - 1) & ~(align - 1))
419+ + sizeof(__u16) * 3 + sizeof(struct vring_used_elem) * num;
420+}
421+
418422 /*
419423 * This initialization routine requires at least one
420424 * vring i.e. vr0. vr1 is optional.
@@ -426,8 +430,9 @@ init_vr(struct mic_info *mic, int fd, int type, · 5 unmodified lines
426430 int vr_size;
427431 char *va;
428432
429− vr_size = PAGE_ALIGN(vring_size(MIC_VRING_ENTRIES,
430− MIC_VIRTIO_RING_ALIGN) + sizeof(struct _mic_vring_info));
433+ vr_size = PAGE_ALIGN(_vring_size(MIC_VRING_ENTRIES,
434+ MIC_VIRTIO_RING_ALIGN) +
435+ sizeof(struct _mic_vring_info));
431436 va = mmap(NULL, MIC_DEVICE_PAGE_END + vr_size * num_vq,
432437 PROT_READ, MAP_SHARED, fd, 0);
433438 if (MAP_FAILED == va) {
@@ -439,25 +444,25 @@ init_vr(struct mic_info *mic, int fd, int type, · 5 unmodified lines
439444 set_dp(mic, type, va);
440445 vr0->va = (struct mic_vring *)&va[MIC_DEVICE_PAGE_END];
441446 vr0->info = vr0->va +
442− vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN);
447+ _vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN);
443448 vring_init(&vr0->vr,
444449 MIC_VRING_ENTRIES, vr0->va, MIC_VIRTIO_RING_ALIGN);
445450 mpsslog("%s %s vr0 %p vr0->info %p vr_size 0x%x vring 0x%x ",
446451 __func__, mic->name, vr0->va, vr0->info, vr_size,
447− vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN));
452+ _vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN));
448453 mpsslog("magic 0x%x expected 0x%x\n",
449454 le32toh(vr0->info->magic), MIC_MAGIC + type);
450455 assert(le32toh(vr0->info->magic) == MIC_MAGIC + type);
451456 if (vr1) {
452457 vr1->va = (struct mic_vring *)
453458 &va[MIC_DEVICE_PAGE_END + vr_size];
454− vr1->info = vr1->va + vring_size(MIC_VRING_ENTRIES,
459+ vr1->info = vr1->va + _vring_size(MIC_VRING_ENTRIES,
455460 MIC_VIRTIO_RING_ALIGN);
456461 vring_init(&vr1->vr,
457462 MIC_VRING_ENTRIES, vr1->va, MIC_VIRTIO_RING_ALIGN);
458463 mpsslog("%s %s vr1 %p vr1->info %p vr_size 0x%x vring 0x%x ",
459464 __func__, mic->name, vr1->va, vr1->info, vr_size,
460− vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN));
465+ _vring_size(MIC_VRING_ENTRIES, MIC_VIRTIO_RING_ALIGN));
461466 mpsslog("magic 0x%x expected 0x%x\n",
462467 le32toh(vr1->info->magic), MIC_MAGIC + type + 1);
463468 assert(le32toh(vr1->info->magic) == MIC_MAGIC + type + 1);
@@ -466,16 +471,21 @@ done: · 2 unmodified lines
466471 return va;
467472 }
468473
469−static void
474+static int
470475 wait_for_card_driver(struct mic_info *mic, int fd, int type)
471476 {
472477 struct pollfd pollfd;
473478 int err;
474479 struct mic_device_desc *desc = get_device_desc(mic, type);
480+ __u8 prev_status;
475481
482+ if (!desc)
483+ return -ENODEV;
484+ prev_status = desc->status;
476485 pollfd.fd = fd;
477486 mpsslog("%s %s Waiting .... desc-> type %d status 0x%x\n",
478487 mic->name, __func__, type, desc->status);
488+
479489 while (1) {
480490 pollfd.events = POLLIN;
481491 pollfd.revents = 0;
@@ -487,8 +497,13 @@ wait_for_card_driver(struct mic_info *mic, int fd, int type) · 5 unmodified lines
487497 }
488498
489499 if (pollfd.revents) {
490− mpsslog("%s %s Waiting... desc-> type %d status 0x%x\n",
491− mic->name, __func__, type, desc->status);
500+ if (desc->status != prev_status) {
501+ mpsslog("%s %s Waiting... desc-> type %d "
502+ "status 0x%x\n",
503+ mic->name, __func__, type,
504+ desc->status);
505+ prev_status = desc->status;
506+ }
492507 if (desc->status & VIRTIO_CONFIG_S_DRIVER_OK) {
493508 mpsslog("%s %s poll.revents %d\n",
494509 mic->name, __func__, pollfd.revents);
@@ -499,6 +514,7 @@ wait_for_card_driver(struct mic_info *mic, int fd, int type) · 4 unmodified lines
499514 }
500515 }
501516 }
517+ return 0;
502518 }
503519
504520 /* Spin till we have some descriptors */
@@ -575,9 +591,16 @@ virtio_net(void *arg) · 70 unmodified lines
575591 __func__, strerror(errno));
576592 continue;
577593 }
578− if (!(desc->status & VIRTIO_CONFIG_S_DRIVER_OK))
579− wait_for_card_driver(mic, mic->mic_net.virtio_net_fd,
580− VIRTIO_ID_NET);
594+ if (!(desc->status & VIRTIO_CONFIG_S_DRIVER_OK)) {
595+ err = wait_for_card_driver(mic,
596+ mic->mic_net.virtio_net_fd,
597+ VIRTIO_ID_NET);
598+ if (err) {
599+ mpsslog("%s %s %d Exiting...\n",
600+ mic->name, __func__, __LINE__);
601+ break;
602+ }
603+ }
581604 /*
582605 * Check if there is data to be read from TUN and write to
583606 * virtio net fd if there is.
@@ -786,10 +809,16 @@ virtio_console(void *arg) · 202 unmodified lines
786809 strerror(errno));
787810 continue;
788811 }
789− if (!(desc->status & VIRTIO_CONFIG_S_DRIVER_OK))
790− wait_for_card_driver(mic,
791− mic->mic_console.virtio_console_fd,
792− VIRTIO_ID_CONSOLE);
812+ if (!(desc->status & VIRTIO_CONFIG_S_DRIVER_OK)) {
813+ err = wait_for_card_driver(mic,
814+ mic->mic_console.virtio_console_fd,
815+ VIRTIO_ID_CONSOLE);
816+ if (err) {
817+ mpsslog("%s %s %d Exiting...\n",
818+ mic->name, __func__, __LINE__);
819+ break;
820+ }
821+ }
793822
794823 if (console_poll[MONITOR_FD].revents & POLLIN) {
795824 copy.iov = iov0;
@@ -1048,8 +1077,9 @@ stop_virtblk(struct mic_info *mic) · 252 unmodified lines
10481077 {
10491078 int vr_size, ret;
10501079
1051− vr_size = PAGE_ALIGN(vring_size(MIC_VRING_ENTRIES,
1052− MIC_VIRTIO_RING_ALIGN) + sizeof(struct _mic_vring_info));
1080+ vr_size = PAGE_ALIGN(_vring_size(MIC_VRING_ENTRIES,
1081+ MIC_VIRTIO_RING_ALIGN) +
1082+ sizeof(struct _mic_vring_info));
10531083 ret = munmap(mic->mic_virtblk.block_dp,
10541084 MIC_DEVICE_PAGE_END + vr_size * virtblk_dev_page.dd.num_vq);
10551085 if (ret < 0)
@@ -1131,6 +1161,10 @@ write_status(int fd, __u8 *status) · 75 unmodified lines
11311161 return ioctl(fd, MIC_VIRTIO_COPY_DESC, &copy);
11321162 }
11331163
1164+#ifndef VIRTIO_BLK_T_GET_ID
1165+#define VIRTIO_BLK_T_GET_ID 8
1166+#endif
1167+
11341168 static void *
11351169 virtio_block(void *arg)
11361170 {
@@ -1297,12 +1331,7 @@ reset(struct mic_info *mic) · 160 unmodified lines
12971331 mpsslog("%s: %s %d state %s\n",
12981332 mic->name, __func__, __LINE__, state);
12991333
1300− /*
1301− * If the shutdown was initiated by OSPM, the state stays
1302− * in "suspended" which is also a valid condition for reset.
1303− */
1304− if ((!strcmp(state, "offline")) ||
1305− (!strcmp(state, "suspended"))) {
1334+ if (!strcmp(state, "ready")) {
13061335 free(state);
13071336 break;
13081337 }
@@ -1331,34 +1360,50 @@ get_mic_shutdown_status(struct mic_info *mic, char *shutdown_status) · 22 unmodified lines
13311360 assert(0);
13321361 };
13331362
1334−static int get_mic_state(struct mic_info *mic, char *state)
1363+static int get_mic_state(struct mic_info *mic)
13351364 {
1336− if (!strcmp(state, "offline"))
1337− return MIC_OFFLINE;
1338− if (!strcmp(state, "online"))
1339− return MIC_ONLINE;
1340− if (!strcmp(state, "shutting_down"))
1341− return MIC_SHUTTING_DOWN;
1342− if (!strcmp(state, "reset_failed"))
1343− return MIC_RESET_FAILED;
1344− if (!strcmp(state, "suspending"))
1345− return MIC_SUSPENDING;
1346− if (!strcmp(state, "suspended"))
1347− return MIC_SUSPENDED;
1348− mpsslog("%s: BUG invalid state %s\n", mic->name, state);
1349− /* Invalid state */
1350− assert(0);
1365+ char *state = NULL;
1366+ enum mic_states mic_state;
1367+
1368+ while (!state) {
1369+ state = readsysfs(mic->name, "state");
1370+ sleep(1);
1371+ }
1372+ mpsslog("%s: %s %d state %s\n",
1373+ mic->name, __func__, __LINE__, state);
1374+
1375+ if (!strcmp(state, "ready")) {
1376+ mic_state = MIC_READY;
1377+ } else if (!strcmp(state, "booting")) {
1378+ mic_state = MIC_BOOTING;
1379+ } else if (!strcmp(state, "online")) {
1380+ mic_state = MIC_ONLINE;
1381+ } else if (!strcmp(state, "shutting_down")) {
1382+ mic_state = MIC_SHUTTING_DOWN;
1383+ } else if (!strcmp(state, "reset_failed")) {
1384+ mic_state = MIC_RESET_FAILED;
1385+ } else if (!strcmp(state, "resetting")) {
1386+ mic_state = MIC_RESETTING;
1387+ } else {
1388+ mpsslog("%s: BUG invalid state %s\n", mic->name, state);
1389+ assert(0);
1390+ }
1391+
1392+ free(state);
1393+ return mic_state;
13511394 };
13521395
13531396 static void mic_handle_shutdown(struct mic_info *mic)
13541397 {
13551398 #define SHUTDOWN_TIMEOUT 60
1356− int i = SHUTDOWN_TIMEOUT, ret, stat = 0;
1399+ int i = SHUTDOWN_TIMEOUT;
13571400 char *shutdown_status;
13581401 while (i) {
13591402 shutdown_status = readsysfs(mic->name, "shutdown_status");
1360− if (!shutdown_status)
1403+ if (!shutdown_status) {
1404+ sleep(1);
13611405 continue;
1406+ }
13621407 mpsslog("%s: %s %d shutdown_status %s\n",
13631408 mic->name, __func__, __LINE__, shutdown_status);
13641409 switch (get_mic_shutdown_status(mic, shutdown_status)) {
@@ -1377,94 +1422,110 @@ static void mic_handle_shutdown(struct mic_info *mic) · 12 unmodified lines
13771422 i--;
13781423 }
13791424 reset:
1380− ret = kill(mic->pid, SIGTERM);
1381− mpsslog("%s: %s %d kill pid %d ret %d\n",
1382− mic->name, __func__, __LINE__,
1383− mic->pid, ret);
1384− if (!ret) {
1385− ret = waitpid(mic->pid, &stat,
1386− WIFSIGNALED(stat));
1387− mpsslog("%s: %s %d waitpid ret %d pid %d\n",
1388− mic->name, __func__, __LINE__,
1389− ret, mic->pid);
1390− }
1391− if (ret == mic->pid)
1392− reset(mic);
1425+ if (!i)
1426+ mpsslog("%s: %s %d timing out waiting for shutdown_status %s\n",
1427+ mic->name, __func__, __LINE__, shutdown_status);
1428+ reset(mic);
13931429 }
13941430
1395−static void *
1396−mic_config(void *arg)
1431+static int open_state_fd(struct mic_info *mic)
13971432 {
1398− struct mic_info *mic = (struct mic_info *)arg;
1399− char *state = NULL;
14001433 char pathname[PATH_MAX];
1401− int fd, ret;
1402− struct pollfd ufds[1];
1403− char value[4096];
1434+ int fd;
14041435
14051436 snprintf(pathname, PATH_MAX - 1, "%s/%s/%s",
14061437 MICSYSFSDIR, mic->name, "state");
14071438
14081439 fd = open(pathname, O_RDONLY);
1409− if (fd < 0) {
1440+ if (fd < 0)
14101441 mpsslog("%s: opening file %s failed %s\n",
14111442 mic->name, pathname, strerror(errno));
1412− goto error;
1443+ return fd;
1444+}
1445+
1446+static int block_till_state_change(int fd, struct mic_info *mic)
1447+{
1448+ struct pollfd ufds[1];
1449+ char value[PAGE_SIZE];
1450+ int ret;
1451+
1452+ ufds[0].fd = fd;
1453+ ufds[0].events = POLLERR | POLLPRI;
1454+ ret = poll(ufds, 1, -1);
1455+ if (ret < 0) {
1456+ mpsslog("%s: %s %d poll failed %s\n",
1457+ mic->name, __func__, __LINE__, strerror(errno));
1458+ return ret;
1459+ }
1460+
1461+ ret = lseek(fd, 0, SEEK_SET);
1462+ if (ret < 0) {
1463+ mpsslog("%s: %s %d Failed to seek to 0: %s\n",
1464+ mic->name, __func__, __LINE__, strerror(errno));
1465+ return ret;
1466+ }
1467+
1468+ ret = read(fd, value, sizeof(value));
1469+ if (ret < 0) {
1470+ mpsslog("%s: %s %d Failed to read sysfs entry: %s\n",
1471+ mic->name, __func__, __LINE__, strerror(errno));
1472+ return ret;
1473+ }
1474+
1475+ return 0;
1476+}
1477+
1478+static void *
1479+mic_config(void *arg)
1480+{
1481+ struct mic_info *mic = (struct mic_info *)arg;
1482+ int fd, ret, stat = 0;
1483+
1484+ fd = open_state_fd(mic);
1485+ if (fd < 0) {
1486+ mpsslog("%s: %s %d open state fd failed %s\n",
1487+ mic->name, __func__, __LINE__, strerror(errno));
1488+ goto exit;
14131489 }
14141490
14151491 do {
1416− ret = lseek(fd, 0, SEEK_SET);
1492+ ret = block_till_state_change(fd, mic);
14171493 if (ret < 0) {
1418− mpsslog("%s: Failed to seek to file start '%s': %s\n",
1419− mic->name, pathname, strerror(errno));
1420− goto close_error1;
1494+ mpsslog("%s: %s %d block_till_state_change error %s\n",
1495+ mic->name, __func__, __LINE__, strerror(errno));
1496+ goto close_exit;
14211497 }
1422− ret = read(fd, value, sizeof(value));
1423− if (ret < 0) {
1424− mpsslog("%s: Failed to read sysfs entry '%s': %s\n",
1425− mic->name, pathname, strerror(errno));
1426− goto close_error1;
1427− }
1428−retry:
1429− state = readsysfs(mic->name, "state");
1430− if (!state)
1431− goto retry;
1432− mpsslog("%s: %s %d state %s\n",
1433− mic->name, __func__, __LINE__, state);
1434− switch (get_mic_state(mic, state)) {
1498+
1499+ switch (get_mic_state(mic)) {
14351500 case MIC_SHUTTING_DOWN:
14361501 mic_handle_shutdown(mic);
1437− goto close_error;
1438− case MIC_SUSPENDING:
1439− mic->boot_on_resume = 1;
1440− setsysfs(mic->name, "state", "suspend");
1441− mic_handle_shutdown(mic);
1442− goto close_error;
1443− case MIC_OFFLINE:
1502+ break;
1503+ case MIC_READY:
1504+ case MIC_RESET_FAILED:
1505+ ret = kill(mic->pid, SIGTERM);
1506+ mpsslog("%s: %s %d kill pid %d ret %d\n",
1507+ mic->name, __func__, __LINE__,
1508+ mic->pid, ret);
1509+ if (!ret) {
1510+ ret = waitpid(mic->pid, &stat,
1511+ WIFSIGNALED(stat));
1512+ mpsslog("%s: %s %d waitpid ret %d pid %d\n",
1513+ mic->name, __func__, __LINE__,
1514+ ret, mic->pid);
1515+ }
14441516 if (mic->boot_on_resume) {
14451517 setsysfs(mic->name, "state", "boot");
14461518 mic->boot_on_resume = 0;
14471519 }
1448− break;
1520+ goto close_exit;
14491521 default:
14501522 break;
14511523 }
1452− free(state);
1453−
1454− ufds[0].fd = fd;
1455− ufds[0].events = POLLERR | POLLPRI;
1456− ret = poll(ufds, 1, -1);
1457− if (ret < 0) {
1458− mpsslog("%s: poll failed %s\n",
1459− mic->name, strerror(errno));
1460− goto close_error1;
1461− }
14621524 } while (1);
1463−close_error:
1464− free(state);
1465−close_error1:
1525+
1526+close_exit:
14661527 close(fd);
1467−error:
1528+exit:
14681529 init_mic(mic);
14691530 pthread_exit(NULL);
14701531 }
@@ -1477,15 +1538,15 @@ set_cmdline(struct mic_info *mic) · 6 unmodified lines
14771538
14781539 len = snprintf(buffer, PATH_MAX,
14791540 "clocksource=tsc highres=off nohz=off ");
1480− len += snprintf(buffer + len, PATH_MAX - len,
1541+ len += snprintf(buffer + len, PATH_MAX,
14811542 "cpufreq_on;corec6_off;pc3_off;pc6_off ");
1482− len += snprintf(buffer + len, PATH_MAX - len,
1543+ len += snprintf(buffer + len, PATH_MAX,
14831544 "ifcfg=static;address,172.31.%d.1;netmask,255.255.255.0",
1484− mic->id);
1545+ mic->id + 1);
14851546
14861547 setsysfs(mic->name, "cmdline", buffer);
14871548 mpsslog("%s: Command line: \"%s\"\n", mic->name, buffer);
1488− snprintf(buffer, PATH_MAX, "172.31.%d.1", mic->id);
1549+ snprintf(buffer, PATH_MAX, "172.31.%d.1", mic->id + 1);
14891550 mpsslog("%s: IPADDR: \"%s\"\n", mic->name, buffer);
14901551 }
14911552
@@ -1541,8 +1602,6 @@ set_log_buf_info(struct mic_info *mic) · 49 unmodified lines
15411602 close(fd);
15421603 }
15431604
1544−static void init_mic(struct mic_info *mic);
1545−
15461605 static void
15471606 change_virtblk_backend(int x, siginfo_t *siginfo, void *p)
15481607 {
@@ -1553,8 +1612,16 @@ change_virtblk_backend(int x, siginfo_t *siginfo, void *p) · 4 unmodified lines
15531612 }
15541613
15551614 static void
1556−init_mic(struct mic_info *mic)
1615+set_mic_boot_params(struct mic_info *mic)
1616+{
1617+ set_log_buf_info(mic);
1618+ set_cmdline(mic);
1619+}
1620+
1621+static void *
1622+init_mic(void *arg)
15571623 {
1624+ struct mic_info *mic = (struct mic_info *)arg;
15581625 struct sigaction ignore = {
15591626 .sa_flags = 0,
15601627 .sa_handler = SIG_IGN
@@ -1564,7 +1631,7 @@ init_mic(struct mic_info *mic) · 3 unmodified lines
15641631 .sa_sigaction = change_virtblk_backend,
15651632 };
15661633 char buffer[PATH_MAX];
1567− int err;
1634+ int err, fd;
15681635
15691636 /*
15701637 * Currently, one virtio block device is supported for each MIC card
@@ -1577,12 +1644,38 @@ init_mic(struct mic_info *mic) · 6 unmodified lines
15771644 * the MIC daemon.
15781645 */
15791646 sigaction(SIGUSR1, &ignore, NULL);
1647+retry:
1648+ fd = open_state_fd(mic);
1649+ if (fd < 0) {
1650+ mpsslog("%s: %s %d open state fd failed %s\n",
1651+ mic->name, __func__, __LINE__, strerror(errno));
1652+ sleep(2);
1653+ goto retry;
1654+ }
1655+
1656+ if (mic->restart) {
1657+ snprintf(buffer, PATH_MAX, "boot");
1658+ setsysfs(mic->name, "state", buffer);
1659+ mpsslog("%s restarting mic %d\n",
1660+ mic->name, mic->restart);
1661+ mic->restart = 0;
1662+ }
1663+
1664+ while (1) {
1665+ while (block_till_state_change(fd, mic)) {
1666+ mpsslog("%s: %s %d block_till_state_change error %s\n",
1667+ mic->name, __func__, __LINE__, strerror(errno));
1668+ sleep(2);
1669+ continue;
1670+ }
1671+
1672+ if (get_mic_state(mic) == MIC_BOOTING)
1673+ break;
1674+ }
15801675
15811676 mic->pid = fork();
15821677 switch (mic->pid) {
15831678 case 0:
1584− set_log_buf_info(mic);
1585− set_cmdline(mic);
15861679 add_virtio_device(mic, &virtcons_dev_page.dd);
15871680 add_virtio_device(mic, &virtnet_dev_page.dd);
15881681 err = pthread_create(&mic->mic_console.console_thread, NULL,
@@ -1612,24 +1705,29 @@ init_mic(struct mic_info *mic) · 23 unmodified lines
16121705 mic->name, mic->id, errno);
16131706 break;
16141707 default:
1615− if (mic->restart) {
1616− snprintf(buffer, PATH_MAX, "boot");
1617− setsysfs(mic->name, "state", buffer);
1618− mpsslog("%s restarting mic %d\n",
1619− mic->name, mic->restart);
1620− mic->restart = 0;
1621− }
1622− pthread_create(&mic->config_thread, NULL, mic_config, mic);
1708+ err = pthread_create(&mic->config_thread, NULL,
1709+ mic_config, mic);
1710+ if (err)
1711+ mpsslog("%s mic_config pthread_create failed %s\n",
1712+ mic->name, strerror(err));
16231713 }
1714+
1715+ return NULL;
16241716 }
16251717
16261718 static void
16271719 start_daemon(void)
16281720 {
16291721 struct mic_info *mic;
1722+ int err;
16301723
1631− for (mic = mic_list.next; mic != NULL; mic = mic->next)
1632− init_mic(mic);
1724+ for (mic = mic_list.next; mic; mic = mic->next) {
1725+ set_mic_boot_params(mic);
1726+ err = pthread_create(&mic->init_thread, NULL, init_mic, mic);
1727+ if (err)
1728+ mpsslog("%s init_mic pthread_create failed %s\n",
1729+ mic->name, strerror(err));
1730+ }
16331731
16341732 while (1)
16351733 sleep(60);
Documentation/mic/mpssd/mpssd.h+1−0
@@ -86,6 +86,7 @@ struct mic_info { · 85 unmodified lines
8686 int id;
8787 char *name;
8888 pthread_t config_thread;
89+ pthread_t init_thread;
8990 pid_t pid;
9091 struct mic_console_info mic_console;
9192 struct mic_net_info mic_net;
Documentation/misc-devices/apds990x.txt+1−1
@@ -30,7 +30,7 @@ lead to false interrupt, but that doesn't harm. · 29 unmodified lines
3030
3131 ALS contains 4 different gain steps. Driver automatically
3232 selects suitable gain step. After each measurement, reliability of the results
33−is estimated and new measurement is trigged if necessary.
33+is estimated and new measurement is triggered if necessary.
3434
3535 Platform data can provide tuned values to the conversion formulas if
3636 values are known. Otherwise plain sensor default values are used.
Documentation/misc-devices/isl29003+1−1
@@ -29,7 +29,7 @@ Detection · 28 unmodified lines
2929
3030 The ISL29003 does not have an ID register which could be used to identify
3131 it, so the detection routine will just try to read from the configured I2C
32−addess and consider the device to be present as soon as it ACKs the
32+address and consider the device to be present as soon as it ACKs the
3333 transfer.
3434
3535
Documentation/misc-devices/max6875+1−1
@@ -22,7 +22,7 @@ At reset, the MAX6875 reads the configuration EEPROM into its configuration · 21 unmodified lines
2222 registers. The chip then begins to operate according to the values in the
2323 registers.
2424
25−The Maxim MAX6874 is a similar, mostly compatible device, with more intputs
25+The Maxim MAX6874 is a similar, mostly compatible device, with more inputs
2626 and outputs:
2727 vin gpi vout
2828 MAX6874 6 4 8
Documentation/mmc/mmc-dev-attrs.txt+0−10
@@ -72,13 +72,3 @@ Note on raw_rpmb_size_mult: · 71 unmodified lines
7272 "raw_rpmb_size_mult" is a mutliple of 128kB block.
7373 RPMB size in byte is calculated by using the following equation:
7474 RPMB partition size = 128kB x raw_rpmb_size_mult
75−
76−SD/MMC/SDIO Clock Gating Attribute
77−==================================
78−
79−Read and write access is provided to following attribute.
80−This attribute appears only if CONFIG_MMC_CLKGATE is enabled.
81−
82− clkgate_delay Tune the clock gating delay with desired value in milliseconds.
83−
84−echo <desired delay> > /sys/class/mmc_host/mmcX/clkgate_delay
Documentation/networking/can.txt+78−21
@@ -681,7 +681,7 @@ solution for a couple of reasons: · 680 unmodified lines
681681 addr.can_family = AF_CAN;
682682 addr.can_ifindex = ifr.ifr_ifindex;
683683
684− connect(s, (struct sockaddr *)&addr, sizeof(addr))
684+ connect(s, (struct sockaddr *)&addr, sizeof(addr));
685685
686686 (..)
687687
@@ -1018,25 +1018,34 @@ solution for a couple of reasons: · 330 unmodified lines
10181018
10191019 $ ip link set can0 type can help
10201020 Usage: ip link set DEVICE type can
1021− [ bitrate BITRATE [ sample-point SAMPLE-POINT] ] |
1022− [ tq TQ prop-seg PROP_SEG phase-seg1 PHASE-SEG1
1023− phase-seg2 PHASE-SEG2 [ sjw SJW ] ]
1024−
1025− [ loopback { on | off } ]
1026− [ listen-only { on | off } ]
1027− [ triple-sampling { on | off } ]
1028−
1029− [ restart-ms TIME-MS ]
1030− [ restart ]
1031−
1032− Where: BITRATE := { 1..1000000 }
1033− SAMPLE-POINT := { 0.000..0.999 }
1034− TQ := { NUMBER }
1035− PROP-SEG := { 1..8 }
1036− PHASE-SEG1 := { 1..8 }
1037− PHASE-SEG2 := { 1..8 }
1038− SJW := { 1..4 }
1039− RESTART-MS := { 0 | NUMBER }
1021+ [ bitrate BITRATE [ sample-point SAMPLE-POINT] ] |
1022+ [ tq TQ prop-seg PROP_SEG phase-seg1 PHASE-SEG1
1023+ phase-seg2 PHASE-SEG2 [ sjw SJW ] ]
1024+
1025+ [ dbitrate BITRATE [ dsample-point SAMPLE-POINT] ] |
1026+ [ dtq TQ dprop-seg PROP_SEG dphase-seg1 PHASE-SEG1
1027+ dphase-seg2 PHASE-SEG2 [ dsjw SJW ] ]
1028+
1029+ [ loopback { on | off } ]
1030+ [ listen-only { on | off } ]
1031+ [ triple-sampling { on | off } ]
1032+ [ one-shot { on | off } ]
1033+ [ berr-reporting { on | off } ]
1034+ [ fd { on | off } ]
1035+ [ fd-non-iso { on | off } ]
1036+ [ presume-ack { on | off } ]
1037+
1038+ [ restart-ms TIME-MS ]
1039+ [ restart ]
1040+
1041+ Where: BITRATE := { 1..1000000 }
1042+ SAMPLE-POINT := { 0.000..0.999 }
1043+ TQ := { NUMBER }
1044+ PROP-SEG := { 1..8 }
1045+ PHASE-SEG1 := { 1..8 }
1046+ PHASE-SEG2 := { 1..8 }
1047+ SJW := { 1..4 }
1048+ RESTART-MS := { 0 | NUMBER }
10401049
10411050 - Display CAN device details and statistics:
10421051
@@ -1178,7 +1187,55 @@ solution for a couple of reasons: · 135 unmodified lines
11781187 The CAN device MTU can be retrieved e.g. with a SIOCGIFMTU ioctl() syscall.
11791188 N.B. CAN FD capable devices can also handle and send legacy CAN frames.
11801189
1181− FIXME: Add details about the CAN FD controller configuration when available.
1190+ When configuring CAN FD capable CAN controllers an additional 'data' bitrate
1191+ has to be set. This bitrate for the data phase of the CAN FD frame has to be
1192+ at least the bitrate which was configured for the arbitration phase. This
1193+ second bitrate is specified analogue to the first bitrate but the bitrate
1194+ setting keywords for the 'data' bitrate start with 'd' e.g. dbitrate,
1195+ dsample-point, dsjw or dtq and similar settings. When a data bitrate is set
1196+ within the configuration process the controller option "fd on" can be
1197+ specified to enable the CAN FD mode in the CAN controller. This controller
1198+ option also switches the device MTU to 72 (CANFD_MTU).
1199+
1200+ The first CAN FD specification presented as whitepaper at the International
1201+ CAN Conference 2012 needed to be improved for data integrity reasons.
1202+ Therefore two CAN FD implementations have to be distinguished today:
1203+
1204+ - ISO compliant: The ISO 11898-1:2015 CAN FD implementation (default)
1205+ - non-ISO compliant: The CAN FD implementation following the 2012 whitepaper
1206+
1207+ Finally there are three types of CAN FD controllers:
1208+
1209+ 1. ISO compliant (fixed)
1210+ 2. non-ISO compliant (fixed, like the M_CAN IP core v3.0.1 in m_can.c)
1211+ 3. ISO/non-ISO CAN FD controllers (switchable, like the PEAK PCAN-USB FD)
1212+
1213+ The current ISO/non-ISO mode is announced by the CAN controller driver via
1214+ netlink and displayed by the 'ip' tool (controller option FD-NON-ISO).
1215+ The ISO/non-ISO-mode can be altered by setting 'fd-non-iso {on|off}' for
1216+ switchable CAN FD controllers only.
1217+
1218+ Example configuring 500 kbit/s arbitration bitrate and 4 Mbit/s data bitrate:
1219+
1220+ $ ip link set can0 up type can bitrate 500000 sample-point 0.75 \
1221+ dbitrate 4000000 dsample-point 0.8 fd on
1222+ $ ip -details link show can0
1223+ 5: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 72 qdisc pfifo_fast state UNKNOWN \
1224+ mode DEFAULT group default qlen 10
1225+ link/can promiscuity 0
1226+ can <FD> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
1227+ bitrate 500000 sample-point 0.750
1228+ tq 50 prop-seg 14 phase-seg1 15 phase-seg2 10 sjw 1
1229+ pcan_usb_pro_fd: tseg1 1..64 tseg2 1..16 sjw 1..16 brp 1..1024 \
1230+ brp-inc 1
1231+ dbitrate 4000000 dsample-point 0.800
1232+ dtq 12 dprop-seg 7 dphase-seg1 8 dphase-seg2 4 dsjw 1
1233+ pcan_usb_pro_fd: dtseg1 1..16 dtseg2 1..8 dsjw 1..4 dbrp 1..1024 \
1234+ dbrp-inc 1
1235+ clock 80000000
1236+
1237+ Example when 'fd-non-iso on' is added on this switchable CAN FD adapter:
1238+ can <FD,FD-NON-ISO> state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
11821239
11831240 6.7 Supported CAN hardware
11841241
Documentation/networking/filter.txt+3−3
@@ -596,9 +596,9 @@ skb pointer). All constraints and restrictions from bpf_check_classic() apply · 595 unmodified lines
596596 before a conversion to the new layout is being done behind the scenes!
597597
598598 Currently, the classic BPF format is being used for JITing on most of the
599−architectures. Only x86-64 performs JIT compilation from eBPF instruction set,
600−however, future work will migrate other JIT compilers as well, so that they
601−will profit from the very same benefits.
599+architectures. x86-64, aarch64 and s390x perform JIT compilation from eBPF
600+instruction set, however, future work will migrate other JIT compilers as well,
601+so that they will profit from the very same benefits.
602602
603603 Some core changes of the new internal format:
604604
Documentation/networking/ieee802154.txt+4−4
@@ -7,11 +7,11 @@ Introduction · 6 unmodified lines
77 The IEEE 802.15.4 working group focuses on standardization of bottom
88 two layers: Medium Access Control (MAC) and Physical (PHY). And there
99 are mainly two options available for upper layers:
10− - ZigBee - proprietary protocol from ZigBee Alliance
11− - 6LowPAN - IPv6 networking over low rate personal area networks
10+ - ZigBee - proprietary protocol from the ZigBee Alliance
11+ - 6LoWPAN - IPv6 networking over low rate personal area networks
1212
13−The Linux-ZigBee project goal is to provide complete implementation
14−of IEEE 802.15.4 and 6LoWPAN protocols. IEEE 802.15.4 is a stack
13+The linux-wpan project goal is to provide a complete implementation
14+of the IEEE 802.15.4 and 6LoWPAN protocols. IEEE 802.15.4 is a stack
1515 of protocols for organizing Low-Rate Wireless Personal Area Networks.
1616
1717 The stack is composed of three main parts:
Documentation/networking/ip-sysctl.txt+22−3
@@ -384,6 +384,14 @@ tcp_mem - vector of 3 INTEGERs: min, pressure, max · 383 unmodified lines
384384 Defaults are calculated at boot time from amount of available
385385 memory.
386386
387+tcp_min_rtt_wlen - INTEGER
388+ The window length of the windowed min filter to track the minimum RTT.
389+ A shorter window lets a flow more quickly pick up new (higher)
390+ minimum RTT when it is moved to a longer path (e.g., due to traffic
391+ engineering). A longer window makes the filter more resistant to RTT
392+ inflations such as transient congestion. The unit is seconds.
393+ Default: 300
394+
387395 tcp_moderate_rcvbuf - BOOLEAN
388396 If set, TCP performs receive buffer auto-tuning, attempting to
389397 automatically size the buffer (no greater than tcp_rmem[2]) to
@@ -425,6 +433,15 @@ tcp_orphan_retries - INTEGER · 35 unmodified lines
425433 you should think about lowering this value, such sockets
426434 may consume significant resources. Cf. tcp_max_orphans.
427435
436+tcp_recovery - INTEGER
437+ This value is a bitmap to enable various experimental loss recovery
438+ features.
439+
440+ RACK: 0x1 enables the RACK loss detection for fast detection of lost
441+ retransmissions and tail drops.
442+
443+ Default: 0x1
444+
428445 tcp_reordering - INTEGER
429446 Initial reordering level of packets in a TCP stream.
430447 TCP stack can then dynamically adjust flow reordering level
@@ -692,7 +709,7 @@ tcp_limit_output_bytes - INTEGER · 261 unmodified lines
692709 typical pfifo_fast qdiscs.
693710 tcp_limit_output_bytes limits the number of bytes on qdisc
694711 or device to reduce artificial RTT/cwnd and reduce bufferbloat.
695− Default: 131072
712+ Default: 262144
696713
697714 tcp_challenge_ack_limit - INTEGER
698715 Limits number of Challenge ACK sent per second, as recommended
@@ -1199,7 +1216,8 @@ tag - INTEGER · 500 unmodified lines
11991216 xfrm4_gc_thresh - INTEGER
12001217 The threshold at which we will start garbage collecting for IPv4
12011218 destination cache entries. At twice this value the system will
1202− refuse new allocations.
1219+ refuse new allocations. The value must be set below the flowcache
1220+ limit (4096 * number of online cpus) to take effect.
12031221
12041222 igmp_link_local_mcast_reports - BOOLEAN
12051223 Enable IGMP reports for link local multicast groups in the
@@ -1645,7 +1663,8 @@ ratelimit - INTEGER · 439 unmodified lines
16451663 xfrm6_gc_thresh - INTEGER
16461664 The threshold at which we will start garbage collecting for IPv6
16471665 destination cache entries. At twice this value the system will
1648− refuse new allocations.
1666+ refuse new allocations. The value must be set below the flowcache
1667+ limit (4096 * number of online cpus) to take effect.
16491668
16501669
16511670 IPv6 Update by:
Documentation/networking/ipvs-sysctl.txt+10−0
@@ -157,6 +157,16 @@ expire_quiescent_template - BOOLEAN · 156 unmodified lines
157157 persistence template if it is to be used to schedule a new
158158 connection and the destination server is quiescent.
159159
160+ignore_tunneled - BOOLEAN
161+ 0 - disabled (default)
162+ not 0 - enabled
163+
164+ If set, ipvs will set the ipvs_property on all packets which are of
165+ unrecognized protocols. This prevents us from routing tunneled
166+ protocols like ipip, which is useful to prevent rescheduling
167+ packets that have been tunneled to the ipvs host (i.e. to prevent
168+ ipvs routing loops when ipvs is also acting as a real server).
169+
160170 nat_icmp_send - BOOLEAN
161171 0 - disabled (default)
162172 not 0 - enabled
Documentation/networking/l2tp.txt+2−5
@@ -213,15 +213,12 @@ To create an L2TPv3 ethernet pseudowire between local host 192.168.1.1 · 212 unmodified lines
213213 and peer 192.168.1.2, using IP addresses 10.5.1.1 and 10.5.1.2 for the
214214 tunnel endpoints:-
215215
216−# modprobe l2tp_eth
217−# modprobe l2tp_netlink
218−
219216 # ip l2tp add tunnel tunnel_id 1 peer_tunnel_id 1 udp_sport 5000 \
220217 udp_dport 5000 encap udp local 192.168.1.1 remote 192.168.1.2
221218 # ip l2tp add session tunnel_id 1 session_id 1 peer_session_id 1
222−# ifconfig -a
219+# ip -s -d show dev l2tpeth0
223220 # ip addr add 10.5.1.2/32 peer 10.5.1.1/32 dev l2tpeth0
224−# ifconfig l2tpeth0 up
221+# ip li set dev l2tpeth0 up
225222
226223 Choose IP addresses to be the address of a local IP interface and that
227224 of the remote system. The IP addresses of the l2tpeth0 interface can be
Documentation/networking/switchdev.txt+44−21
@@ -115,7 +115,7 @@ Switch ID · 114 unmodified lines
115115 ^^^^^^^^^
116116
117117 The switchdev driver must implement the switchdev op switchdev_port_attr_get
118−for SWITCHDEV_ATTR_PORT_PARENT_ID for each port netdev, returning the same
118+for SWITCHDEV_ATTR_ID_PORT_PARENT_ID for each port netdev, returning the same
119119 physical ID for each port of a switch. The ID must be unique between switches
120120 on the same system. The ID does not need to be unique between switches on
121121 different systems.
@@ -178,7 +178,7 @@ entries are installed, for example, using iproute2 bridge cmd: · 56 unmodified lines
178178 bridge fdb add ADDR dev DEV [vlan VID] [self]
179179
180180 The driver should use the helper switchdev_port_fdb_xxx ops for ndo_fdb_xxx
181−ops, and handle add/delete/dump of SWITCHDEV_OBJ_PORT_FDB object using
181+ops, and handle add/delete/dump of SWITCHDEV_OBJ_ID_PORT_FDB object using
182182 switchdev_port_obj_xxx ops.
183183
184184 XXX: what should be done if offloading this rule to hardware fails (for
@@ -233,26 +233,27 @@ the bridge's FDB. It's possible, but not optimal, to enable learning on the · 48 unmodified lines
233233 device port and on the bridge port, and disable learning_sync.
234234
235235 To support learning and learning_sync port attributes, the driver implements
236−switchdev op switchdev_port_attr_get/set for SWITCHDEV_ATTR_PORT_BRIDGE_FLAGS.
237−The driver should initialize the attributes to the hardware defaults.
236+switchdev op switchdev_port_attr_get/set for
237+SWITCHDEV_ATTR_PORT_ID_BRIDGE_FLAGS. The driver should initialize the attributes
238+to the hardware defaults.
238239
239240 FDB Ageing
240241 ^^^^^^^^^^
241242
242−There are two FDB ageing models supported: 1) ageing by the device, and 2)
243−ageing by the kernel. Ageing by the device is preferred if many FDB entries
244−are supported. The driver calls call_switchdev_notifiers(SWITCHDEV_FDB_DEL,
245−...) to age out the FDB entry. In this model, ageing by the kernel should be
246−turned off. XXX: how to turn off ageing in kernel on a per-port basis or
247−otherwise prevent the kernel from ageing out the FDB entry?
248−
249−In the kernel ageing model, the standard bridge ageing mechanism is used to age
250−out stale FDB entries. To keep an FDB entry "alive", the driver should refresh
251−the FDB entry by calling call_switchdev_notifiers(SWITCHDEV_FDB_ADD, ...). The
243+The bridge will skip ageing FDB entries marked with NTF_EXT_LEARNED and it is
244+the responsibility of the port driver/device to age out these entries. If the
245+port device supports ageing, when the FDB entry expires, it will notify the
246+driver which in turn will notify the bridge with SWITCHDEV_FDB_DEL. If the
247+device does not support ageing, the driver can simulate ageing using a
248+garbage collection timer to monitor FBD entries. Expired entries will be
249+notified to the bridge using SWITCHDEV_FDB_DEL. See rocker driver for
250+example of driver running ageing timer.
251+
252+To keep an NTF_EXT_LEARNED entry "alive", the driver should refresh the FDB
253+entry by calling call_switchdev_notifiers(SWITCHDEV_FDB_ADD, ...). The
252254 notification will reset the FDB entry's last-used time to now. The driver
253255 should rate limit refresh notifications, for example, no more than once a
254−second. If the FDB entry expires, fdb_delete is called to remove entry from
255−the device.
256+second. (The last-used time is visible using the bridge -s fdb option).
256257
257258 STP State Change on Port
258259 ^^^^^^^^^^^^^^^^^^^^^^^^
@@ -260,7 +261,7 @@ STP State Change on Port · 1 unmodified line
260261 Internally or with a third-party STP protocol implementation (e.g. mstpd), the
261262 bridge driver maintains the STP state for ports, and will notify the switch
262263 driver of STP state change on a port using the switchdev op
263−switchdev_attr_port_set for SWITCHDEV_ATTR_PORT_STP_UPDATE.
264+switchdev_attr_port_set for SWITCHDEV_ATTR_PORT_ID_STP_UPDATE.
264265
265266 State is one of BR_STATE_*. The switch driver can use STP state updates to
266267 update ingress packet filter list for the port. For example, if port is
@@ -277,8 +278,8 @@ Flooding L2 domain · 10 unmodified lines
277278 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
278279 and unknown unicast packets to all ports in domain, if allowed by port's
279280 current STP state. The switch driver, knowing which ports are within which
280−vlan L2 domain, can program the switch device for flooding. The packet should
281−also be sent to the port netdev for processing by the bridge driver. The
281+vlan L2 domain, can program the switch device for flooding. The packet may
282+be sent to the port netdev for processing by the bridge driver. The
282283 bridge should not reflood the packet to the same ports the device flooded,
283284 otherwise there will be duplicate packets on the wire.
284285
@@ -297,6 +298,9 @@ packets up to the bridge driver for flooding. This is not ideal as the number · 12 unmodified lines
297298 of ports scale in the L2 domain as the device is much more efficient at
298299 flooding packets that software.
299300
301+If supported by the device, flood control can be offloaded to it, preventing
302+certain netdevs from flooding unicast traffic for which there is no FDB entry.
303+
300304 IGMP Snooping
301305 ^^^^^^^^^^^^^
302306
@@ -316,9 +320,9 @@ SWITCHDEV_OBJ_IPV[4|6]_FIB object using switchdev_port_obj_xxx ops. · 13 unmodified lines
316320 switchdev_port_obj_add is used for both adding a new FIB entry to the device,
317321 or modifying an existing entry on the device.
318322
319−XXX: Currently, only SWITCHDEV_OBJ_IPV4_FIB objects are supported.
323+XXX: Currently, only SWITCHDEV_OBJ_ID_IPV4_FIB objects are supported.
320324
321−SWITCHDEV_OBJ_IPV4_FIB object passes:
325+SWITCHDEV_OBJ_ID_IPV4_FIB object passes:
322326
323327 struct switchdev_obj_ipv4_fib { /* IPV4_FIB */
324328 u32 dst;
@@ -369,3 +373,22 @@ The driver can monitor for updates to arp_tbl using the netevent notifier · 44 unmodified lines
369373 NETEVENT_NEIGH_UPDATE. The device can be programmed with resolved nexthops
370374 for the routes as arp_tbl updates. The driver implements ndo_neigh_destroy
371375 to know when arp_tbl neighbor entries are purged from the port.
376+
377+Transaction item queue
378+^^^^^^^^^^^^^^^^^^^^^^
379+
380+For switchdev ops attr_set and obj_add, there is a 2 phase transaction model
381+used. First phase is to "prepare" anything needed, including various checks,
382+memory allocation, etc. The goal is to handle the stuff that is not unlikely
383+to fail here. The second phase is to "commit" the actual changes.
384+
385+Switchdev provides an inftrastructure for sharing items (for example memory
386+allocations) between the two phases.
387+
388+The object created by a driver in "prepare" phase and it is queued up by:
389+switchdev_trans_item_enqueue()
390+During the "commit" phase, the driver gets the object by:
391+switchdev_trans_item_dequeue()
392+
393+If a transaction is aborted during "prepare" phase, switchdev code will handle
394+cleanup of the queued-up objects.
Documentation/networking/vrf.txt+299−2
@@ -90,7 +90,304 @@ or to specify the output device using cmsg and IP_PKTINFO. · 89 unmodified lines
9090
9191 Limitations
9292 -----------
93−VRF device currently only works for IPv4. Support for IPv6 is under development.
94−
9593 Index of original ingress interface is not available via cmsg. Will address
9694 soon.
95+
96+################################################################################
97+
98+Using iproute2 for VRFs
99+=======================
100+VRF devices do *not* have to start with 'vrf-'. That is a convention used here
101+for emphasis of the device type, similar to use of 'br' in bridge names.
102+
103+1. Create a VRF
104+
105+ To instantiate a VRF device and associate it with a table:
106+ $ ip link add dev NAME type vrf table ID
107+
108+ Remember to add the ip rules as well:
109+ $ ip ru add oif NAME table 10
110+ $ ip ru add iif NAME table 10
111+ $ ip -6 ru add oif NAME table 10
112+ $ ip -6 ru add iif NAME table 10
113+
114+ Without the rules route lookups are not directed to the table.
115+
116+ For example:
117+ $ ip link add dev vrf-blue type vrf table 10
118+ $ ip ru add pref 200 oif vrf-blue table 10
119+ $ ip ru add pref 200 iif vrf-blue table 10
120+ $ ip -6 ru add pref 200 oif vrf-blue table 10
121+ $ ip -6 ru add pref 200 iif vrf-blue table 10
122+
123+
124+2. List VRFs
125+
126+ To list VRFs that have been created:
127+ $ ip [-d] link show type vrf
128+ NOTE: The -d option is needed to show the table id
129+
130+ For example:
131+ $ ip -d link show type vrf
132+ 11: vrf-mgmt: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
133+ link/ether 72:b3:ba:91:e2:24 brd ff:ff:ff:ff:ff:ff promiscuity 0
134+ vrf table 1 addrgenmode eui64
135+ 12: vrf-red: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
136+ link/ether b6:6f:6e:f6:da:73 brd ff:ff:ff:ff:ff:ff promiscuity 0
137+ vrf table 10 addrgenmode eui64
138+ 13: vrf-blue: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
139+ link/ether 36:62:e8:7d:bb:8c brd ff:ff:ff:ff:ff:ff promiscuity 0
140+ vrf table 66 addrgenmode eui64
141+ 14: vrf-green: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
142+ link/ether e6:28:b8:63:70:bb brd ff:ff:ff:ff:ff:ff promiscuity 0
143+ vrf table 81 addrgenmode eui64
144+
145+
146+ Or in brief output:
147+
148+ $ ip -br link show type vrf
149+ vrf-mgmt UP 72:b3:ba:91:e2:24 <NOARP,MASTER,UP,LOWER_UP>
150+ vrf-red UP b6:6f:6e:f6:da:73 <NOARP,MASTER,UP,LOWER_UP>
151+ vrf-blue UP 36:62:e8:7d:bb:8c <NOARP,MASTER,UP,LOWER_UP>
152+ vrf-green UP e6:28:b8:63:70:bb <NOARP,MASTER,UP,LOWER_UP>
153+
154+
155+3. Assign a Network Interface to a VRF
156+
157+ Network interfaces are assigned to a VRF by enslaving the netdevice to a
158+ VRF device:
159+ $ ip link set dev NAME master VRF-NAME
160+
161+ On enslavement connected and local routes are automatically moved to the
162+ table associated with the VRF device.
163+
164+ For example:
165+ $ ip link set dev eth0 master vrf-mgmt
166+
167+
168+4. Show Devices Assigned to a VRF
169+
170+ To show devices that have been assigned to a specific VRF add the master
171+ option to the ip command:
172+ $ ip link show master VRF-NAME
173+
174+ For example:
175+ $ ip link show master vrf-red
176+ 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vrf-red state UP mode DEFAULT group default qlen 1000
177+ link/ether 02:00:00:00:02:02 brd ff:ff:ff:ff:ff:ff
178+ 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vrf-red state UP mode DEFAULT group default qlen 1000
179+ link/ether 02:00:00:00:02:03 brd ff:ff:ff:ff:ff:ff
180+ 7: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master vrf-red state DOWN mode DEFAULT group default qlen 1000
181+ link/ether 02:00:00:00:02:06 brd ff:ff:ff:ff:ff:ff
182+
183+
184+ Or using the brief output:
185+ $ ip -br link show master vrf-red
186+ eth1 UP 02:00:00:00:02:02 <BROADCAST,MULTICAST,UP,LOWER_UP>
187+ eth2 UP 02:00:00:00:02:03 <BROADCAST,MULTICAST,UP,LOWER_UP>
188+ eth5 DOWN 02:00:00:00:02:06 <BROADCAST,MULTICAST>
189+
190+
191+5. Show Neighbor Entries for a VRF
192+
193+ To list neighbor entries associated with devices enslaved to a VRF device
194+ add the master option to the ip command:
195+ $ ip [-6] neigh show master VRF-NAME
196+
197+ For example:
198+ $ ip neigh show master vrf-red
199+ 10.2.1.254 dev eth1 lladdr a6:d9:c7:4f:06:23 REACHABLE
200+ 10.2.2.254 dev eth2 lladdr 5e:54:01:6a:ee:80 REACHABLE
201+
202+ $ ip -6 neigh show master vrf-red
203+ 2002:1::64 dev eth1 lladdr a6:d9:c7:4f:06:23 REACHABLE
204+
205+
206+6. Show Addresses for a VRF
207+
208+ To show addresses for interfaces associated with a VRF add the master
209+ option to the ip command:
210+ $ ip addr show master VRF-NAME
211+
212+ For example:
213+ $ ip addr show master vrf-red
214+ 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vrf-red state UP group default qlen 1000
215+ link/ether 02:00:00:00:02:02 brd ff:ff:ff:ff:ff:ff
216+ inet 10.2.1.2/24 brd 10.2.1.255 scope global eth1
217+ valid_lft forever preferred_lft forever
218+ inet6 2002:1::2/120 scope global
219+ valid_lft forever preferred_lft forever
220+ inet6 fe80::ff:fe00:202/64 scope link
221+ valid_lft forever preferred_lft forever
222+ 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vrf-red state UP group default qlen 1000
223+ link/ether 02:00:00:00:02:03 brd ff:ff:ff:ff:ff:ff
224+ inet 10.2.2.2/24 brd 10.2.2.255 scope global eth2
225+ valid_lft forever preferred_lft forever
226+ inet6 2002:2::2/120 scope global
227+ valid_lft forever preferred_lft forever
228+ inet6 fe80::ff:fe00:203/64 scope link
229+ valid_lft forever preferred_lft forever
230+ 7: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master vrf-red state DOWN group default qlen 1000
231+ link/ether 02:00:00:00:02:06 brd ff:ff:ff:ff:ff:ff
232+
233+ Or in brief format:
234+ $ ip -br addr show master vrf-red
235+ eth1 UP 10.2.1.2/24 2002:1::2/120 fe80::ff:fe00:202/64
236+ eth2 UP 10.2.2.2/24 2002:2::2/120 fe80::ff:fe00:203/64
237+ eth5 DOWN
238+
239+
240+7. Show Routes for a VRF
241+
242+ To show routes for a VRF use the ip command to display the table associated
243+ with the VRF device:
244+ $ ip [-6] route show table ID
245+
246+ For example:
247+ $ ip route show table vrf-red
248+ prohibit default
249+ broadcast 10.2.1.0 dev eth1 proto kernel scope link src 10.2.1.2
250+ 10.2.1.0/24 dev eth1 proto kernel scope link src 10.2.1.2
251+ local 10.2.1.2 dev eth1 proto kernel scope host src 10.2.1.2
252+ broadcast 10.2.1.255 dev eth1 proto kernel scope link src 10.2.1.2
253+ broadcast 10.2.2.0 dev eth2 proto kernel scope link src 10.2.2.2
254+ 10.2.2.0/24 dev eth2 proto kernel scope link src 10.2.2.2
255+ local 10.2.2.2 dev eth2 proto kernel scope host src 10.2.2.2
256+ broadcast 10.2.2.255 dev eth2 proto kernel scope link src 10.2.2.2
257+
258+ $ ip -6 route show table vrf-red
259+ local 2002:1:: dev lo proto none metric 0 pref medium
260+ local 2002:1::2 dev lo proto none metric 0 pref medium
261+ 2002:1::/120 dev eth1 proto kernel metric 256 pref medium
262+ local 2002:2:: dev lo proto none metric 0 pref medium
263+ local 2002:2::2 dev lo proto none metric 0 pref medium
264+ 2002:2::/120 dev eth2 proto kernel metric 256 pref medium
265+ local fe80:: dev lo proto none metric 0 pref medium
266+ local fe80:: dev lo proto none metric 0 pref medium
267+ local fe80::ff:fe00:202 dev lo proto none metric 0 pref medium
268+ local fe80::ff:fe00:203 dev lo proto none metric 0 pref medium
269+ fe80::/64 dev eth1 proto kernel metric 256 pref medium
270+ fe80::/64 dev eth2 proto kernel metric 256 pref medium
271+ ff00::/8 dev vrf-red metric 256 pref medium
272+ ff00::/8 dev eth1 metric 256 pref medium
273+ ff00::/8 dev eth2 metric 256 pref medium
274+
275+
276+8. Route Lookup for a VRF
277+
278+ A test route lookup can be done for a VRF by adding the oif option to ip:
279+ $ ip [-6] route get oif VRF-NAME ADDRESS
280+
281+ For example:
282+ $ ip route get 10.2.1.40 oif vrf-red
283+ 10.2.1.40 dev eth1 table vrf-red src 10.2.1.2
284+ cache
285+
286+ $ ip -6 route get 2002:1::32 oif vrf-red
287+ 2002:1::32 from :: dev eth1 table vrf-red proto kernel src 2002:1::2 metric 256 pref medium
288+
289+
290+9. Removing Network Interface from a VRF
291+
292+ Network interfaces are removed from a VRF by breaking the enslavement to
293+ the VRF device:
294+ $ ip link set dev NAME nomaster
295+
296+ Connected routes are moved back to the default table and local entries are
297+ moved to the local table.
298+
299+ For example:
300+ $ ip link set dev eth0 nomaster
301+
302+--------------------------------------------------------------------------------
303+
304+Commands used in this example:
305+
306+cat >> /etc/iproute2/rt_tables <<EOF
307+1 vrf-mgmt
308+10 vrf-red
309+66 vrf-blue
310+81 vrf-green
311+EOF
312+
313+function vrf_create
314+{
315+ VRF=$1
316+ TBID=$2
317+ # create VRF device
318+ ip link add vrf-${VRF} type vrf table ${TBID}
319+
320+ # add rules that direct lookups to vrf table
321+ ip ru add pref 200 oif vrf-${VRF} table ${TBID}
322+ ip ru add pref 200 iif vrf-${VRF} table ${TBID}
323+ ip -6 ru add pref 200 oif vrf-${VRF} table ${TBID}
324+ ip -6 ru add pref 200 iif vrf-${VRF} table ${TBID}
325+
326+ if [ "${VRF}" != "mgmt" ]; then
327+ ip route add table ${TBID} prohibit default
328+ fi
329+ ip link set dev vrf-${VRF} up
330+ ip link set dev vrf-${VRF} state up
331+}
332+
333+vrf_create mgmt 1
334+ip link set dev eth0 master vrf-mgmt
335+
336+vrf_create red 10
337+ip link set dev eth1 master vrf-red
338+ip link set dev eth2 master vrf-red
339+ip link set dev eth5 master vrf-red
340+
341+vrf_create blue 66
342+ip link set dev eth3 master vrf-blue
343+
344+vrf_create green 81
345+ip link set dev eth4 master vrf-green
346+
347+
348+Interface addresses from /etc/network/interfaces:
349+auto eth0
350+iface eth0 inet static
351+ address 10.0.0.2
352+ netmask 255.255.255.0
353+ gateway 10.0.0.254
354+
355+iface eth0 inet6 static
356+ address 2000:1::2
357+ netmask 120
358+
359+auto eth1
360+iface eth1 inet static
361+ address 10.2.1.2
362+ netmask 255.255.255.0
363+
364+iface eth1 inet6 static
365+ address 2002:1::2
366+ netmask 120
367+
368+auto eth2
369+iface eth2 inet static
370+ address 10.2.2.2
371+ netmask 255.255.255.0
372+
373+iface eth2 inet6 static
374+ address 2002:2::2
375+ netmask 120
376+
377+auto eth3
378+iface eth3 inet static
379+ address 10.2.3.2
380+ netmask 255.255.255.0
381+
382+iface eth3 inet6 static
383+ address 2002:3::2
384+ netmask 120
385+
386+auto eth4
387+iface eth4 inet static
388+ address 10.2.4.2
389+ netmask 255.255.255.0
390+
391+iface eth4 inet6 static
392+ address 2002:4::2
393+ netmask 120
Documentation/nvdimm/nvdimm.txt+28−21
@@ -62,6 +62,12 @@ DAX: File system extensions to bypass the page cache and block layer to · 61 unmodified lines
6262 mmap persistent memory, from a PMEM block device, directly into a
6363 process address space.
6464
65+DSM: Device Specific Method: ACPI method to to control specific
66+device - in this case the firmware.
67+
68+DCR: NVDIMM Control Region Structure defined in ACPI 6 Section 5.2.25.5.
69+It defines a vendor-id, device-id, and interface format for a given DIMM.
70+
6571 BTT: Block Translation Table: Persistent memory is byte addressable.
6672 Existing software may have an expectation that the power-fail-atomicity
6773 of writes is at least one sector, 512 bytes. The BTT is an indirection
@@ -133,16 +139,16 @@ device driver: · 65 unmodified lines
133139 registered, can be immediately attached to nd_pmem.
134140
135141 2. BLK (nd_blk.ko): This driver performs I/O using a set of platform
136− defined apertures. A set of apertures will all access just one DIMM.
137− Multiple windows allow multiple concurrent accesses, much like
142+ defined apertures. A set of apertures will access just one DIMM.
143+ Multiple windows (apertures) allow multiple concurrent accesses, much like
138144 tagged-command-queuing, and would likely be used by different threads or
139145 different CPUs.
140146
141147 The NFIT specification defines a standard format for a BLK-aperture, but
142148 the spec also allows for vendor specific layouts, and non-NFIT BLK
143− implementations may other designs for BLK I/O. For this reason "nd_blk"
144− calls back into platform-specific code to perform the I/O. One such
145− implementation is defined in the "Driver Writer's Guide" and "DSM
149+ implementations may have other designs for BLK I/O. For this reason
150+ "nd_blk" calls back into platform-specific code to perform the I/O.
151+ One such implementation is defined in the "Driver Writer's Guide" and "DSM
146152 Interface Example".
147153
148154
@@ -152,7 +158,7 @@ Why BLK? · 3 unmodified lines
152158 While PMEM provides direct byte-addressable CPU-load/store access to
153159 NVDIMM storage, it does not provide the best system RAS (recovery,
154160 availability, and serviceability) model. An access to a corrupted
155−system-physical-address address causes a cpu exception while an access
161+system-physical-address address causes a CPU exception while an access
156162 to a corrupted address through an BLK-aperture causes that block window
157163 to raise an error status in a register. The latter is more aligned with
158164 the standard error model that host-bus-adapter attached disks present.
@@ -162,7 +168,7 @@ data could be interleaved in an opaque hardware specific manner across · 3 unmodified lines
162168 several DIMMs.
163169
164170 PMEM vs BLK
165−BLK-apertures solve this RAS problem, but their presence is also the
171+BLK-apertures solve these RAS problems, but their presence is also the
166172 major contributing factor to the complexity of the ND subsystem. They
167173 complicate the implementation because PMEM and BLK alias in DPA space.
168174 Any given DIMM's DPA-range may contribute to one or more
@@ -220,8 +226,8 @@ socket. Each unique interface (BLK or PMEM) to DPA space is identified · 51 unmodified lines
220226 by a region device with a dynamically assigned id (REGION0 - REGION5).
221227
222228 1. The first portion of DIMM0 and DIMM1 are interleaved as REGION0. A
223− single PMEM namespace is created in the REGION0-SPA-range that spans
224− DIMM0 and DIMM1 with a user-specified name of "pm0.0". Some of that
229+ single PMEM namespace is created in the REGION0-SPA-range that spans most
230+ of DIMM0 and DIMM1 with a user-specified name of "pm0.0". Some of that
225231 interleaved system-physical-address range is reclaimed as BLK-aperture
226232 accessed space starting at DPA-offset (a) into each DIMM. In that
227233 reclaimed space we create two BLK-aperture "namespaces" from REGION2 and
@@ -230,13 +236,13 @@ by a region device with a dynamically assigned id (REGION0 - REGION5). · 2 unmodified lines
230236
231237 2. In the last portion of DIMM0 and DIMM1 we have an interleaved
232238 system-physical-address range, REGION1, that spans those two DIMMs as
233− well as DIMM2 and DIMM3. Some of REGION1 allocated to a PMEM namespace
234− named "pm1.0" the rest is reclaimed in 4 BLK-aperture namespaces (for
239+ well as DIMM2 and DIMM3. Some of REGION1 is allocated to a PMEM namespace
240+ named "pm1.0", the rest is reclaimed in 4 BLK-aperture namespaces (for
235241 each DIMM in the interleave set), "blk2.1", "blk3.1", "blk4.0", and
236242 "blk5.0".
237243
238244 3. The portion of DIMM2 and DIMM3 that do not participate in the REGION1
239− interleaved system-physical-address range (i.e. the DPA address below
245+ interleaved system-physical-address range (i.e. the DPA address past
240246 offset (b) are also included in the "blk4.0" and "blk5.0" namespaces.
241247 Note, that this example shows that BLK-aperture namespaces don't need to
242248 be contiguous in DPA-space.
@@ -252,15 +258,15 @@ LIBNVDIMM Kernel Device Model and LIBNDCTL Userspace API · 9 unmodified lines
252258
253259 What follows is a description of the LIBNVDIMM sysfs layout and a
254260 corresponding object hierarchy diagram as viewed through the LIBNDCTL
255−api. The example sysfs paths and diagrams are relative to the Example
261+API. The example sysfs paths and diagrams are relative to the Example
256262 NVDIMM Platform which is also the LIBNVDIMM bus used in the LIBNDCTL unit
257263 test.
258264
259265 LIBNDCTL: Context
260−Every api call in the LIBNDCTL library requires a context that holds the
266+Every API call in the LIBNDCTL library requires a context that holds the
261267 logging parameters and other library instance state. The library is
262268 based on the libabc template:
263−https://git.kernel.org/cgit/linux/kernel/git/kay/libabc.git/
269+https://git.kernel.org/cgit/linux/kernel/git/kay/libabc.git
264270
265271 LIBNDCTL: instantiate a new library context example
266272
@@ -409,7 +415,7 @@ Bit 31:28 Reserved · 142 unmodified lines
409415 LIBNVDIMM/LIBNDCTL: Region
410416 ----------------------
411417
412−A generic REGION device is registered for each PMEM range orBLK-aperture
418+A generic REGION device is registered for each PMEM range or BLK-aperture
413419 set. Per the example there are 6 regions: 2 PMEM and 4 BLK-aperture
414420 sets on the "nfit_test.0" bus. The primary role of regions are to be a
415421 container of "mappings". A mapping is a tuple of <DIMM,
@@ -509,7 +515,7 @@ At first glance it seems since NFIT defines just PMEM and BLK interface · 93 unmodified lines
509515 types that we should simply name REGION devices with something derived
510516 from those type names. However, the ND subsystem explicitly keeps the
511517 REGION name generic and expects userspace to always consider the
512−region-attributes for 4 reasons:
518+region-attributes for four reasons:
513519
514520 1. There are already more than two REGION and "namespace" types. For
515521 PMEM there are two subtypes. As mentioned previously we have PMEM where
@@ -698,8 +704,8 @@ static int configure_namespace(struct ndctl_region *region, · 182 unmodified lines
698704
699705 Why the Term "namespace"?
700706
701− 1. Why not "volume" for instance? "volume" ran the risk of confusing ND
702− as a volume manager like device-mapper.
707+ 1. Why not "volume" for instance? "volume" ran the risk of confusing
708+ ND (libnvdimm subsystem) to a volume manager like device-mapper.
703709
704710 2. The term originated to describe the sub-devices that can be created
705711 within a NVME controller (see the nvme specification:
@@ -774,13 +780,14 @@ block" needs to be destroyed. Note, that to destroy a BTT the media · 68 unmodified lines
774780 needs to be written in raw mode. By default, the kernel will autodetect
775781 the presence of a BTT and disable raw mode. This autodetect behavior
776782 can be suppressed by enabling raw mode for the namespace via the
777−ndctl_namespace_set_raw_mode() api.
783+ndctl_namespace_set_raw_mode() API.
778784
779785
780786 Summary LIBNDCTL Diagram
781787 ------------------------
782788
783−For the given example above, here is the view of the objects as seen by the LIBNDCTL api:
789+For the given example above, here is the view of the objects as seen by the
790+LIBNDCTL API:
784791 +---+
785792 |CTX| +---------+ +--------------+ +---------------+
786793 +-+-+ +-> REGION0 +---> NAMESPACE0.0 +--> PMEM8 "pm0.0" |
Documentation/power/pci.txt+38−13
@@ -979,20 +979,45 @@ every time right after the runtime_resume() callback has returned · 978 unmodified lines
979979 (alternatively, the runtime_suspend() callback will have to check if the
980980 device should really be suspended and return -EAGAIN if that is not the case).
981981
982−The runtime PM of PCI devices is disabled by default. It is also blocked by
983−pci_pm_init() that runs the pm_runtime_forbid() helper function. If a PCI
984−driver implements the runtime PM callbacks and intends to use the runtime PM
985−framework provided by the PM core and the PCI subsystem, it should enable this
986−feature by executing the pm_runtime_enable() helper function. However, the
987−driver should not call the pm_runtime_allow() helper function unblocking
988−the runtime PM of the device. Instead, it should allow user space or some
989−platform-specific code to do that (user space can do it via sysfs), although
990−once it has called pm_runtime_enable(), it must be prepared to handle the
982+The runtime PM of PCI devices is enabled by default by the PCI core. PCI
983+device drivers do not need to enable it and should not attempt to do so.
984+However, it is blocked by pci_pm_init() that runs the pm_runtime_forbid()
985+helper function. In addition to that, the runtime PM usage counter of
986+each PCI device is incremented by local_pci_probe() before executing the
987+probe callback provided by the device's driver.
988+
989+If a PCI driver implements the runtime PM callbacks and intends to use the
990+runtime PM framework provided by the PM core and the PCI subsystem, it needs
991+to decrement the device's runtime PM usage counter in its probe callback
992+function. If it doesn't do that, the counter will always be different from
993+zero for the device and it will never be runtime-suspended. The simplest
994+way to do that is by calling pm_runtime_put_noidle(), but if the driver
995+wants to schedule an autosuspend right away, for example, it may call
996+pm_runtime_put_autosuspend() instead for this purpose. Generally, it
997+just needs to call a function that decrements the devices usage counter
998+from its probe routine to make runtime PM work for the device.
999+
1000+It is important to remember that the driver's runtime_suspend() callback
1001+may be executed right after the usage counter has been decremented, because
1002+user space may already have cuased the pm_runtime_allow() helper function
1003+unblocking the runtime PM of the device to run via sysfs, so the driver must
1004+be prepared to cope with that.
1005+
1006+The driver itself should not call pm_runtime_allow(), though. Instead, it
1007+should let user space or some platform-specific code do that (user space can
1008+do it via sysfs as stated above), but it must be prepared to handle the
9911009 runtime PM of the device correctly as soon as pm_runtime_allow() is called
992−(which may happen at any time). [It also is possible that user space causes
993−pm_runtime_allow() to be called via sysfs before the driver is loaded, so in
994−fact the driver has to be prepared to handle the runtime PM of the device as
995−soon as it calls pm_runtime_enable().]
1010+(which may happen at any time, even before the driver is loaded).
1011+
1012+When the driver's remove callback runs, it has to balance the decrementation
1013+of the device's runtime PM usage counter at the probe time. For this reason,
1014+if it has decremented the counter in its probe callback, it must run
1015+pm_runtime_get_noresume() in its remove callback. [Since the core carries
1016+out a runtime resume of the device and bumps up the device's usage counter
1017+before running the driver's remove callback, the runtime PM of the device
1018+is effectively disabled for the duration of the remove execution and all
1019+runtime PM helper functions incrementing the device's usage counter are
1020+then effectively equivalent to pm_runtime_get_noresume().]
9961021
9971022 The runtime PM framework works by processing requests to suspend or resume
9981023 devices, or to check if they are idle (in which cases it is reasonable to
Documentation/printk-formats.txt+29−0
@@ -23,6 +23,10 @@ Example: · 22 unmodified lines
2323
2424 Reminder: sizeof() result is of type size_t.
2525
26+The kernel's printf does not support %n. For obvious reasons, floating
27+point formats (%e, %f, %g, %a) are also not recognized. Use of any
28+unsupported specifier or length qualifier results in a WARN and early
29+return from vsnprintf.
2630
2731 Raw pointer value SHOULD be printed with %p. The kernel supports
2832 the following extended format specifiers for pointer types:
@@ -119,6 +123,7 @@ Raw buffer as an escaped string: · 90 unmodified lines
119123 If field width is omitted the 1 byte only will be escaped.
120124
121125 Raw buffer as a hex string:
126+
122127 %*ph 00 01 02 ... 3f
123128 %*phC 00:01:02: ... :3f
124129 %*phD 00-01-02- ... -3f
@@ -234,6 +239,7 @@ UUID/GUID addresses: · 109 unmodified lines
234239 Passed by reference.
235240
236241 dentry names:
242+
237243 %pd{,2,3,4}
238244 %pD{,2,3,4}
239245
@@ -256,6 +262,8 @@ struct va_format: · 16 unmodified lines
256262 va_list *va;
257263 };
258264
265+ Implements a "recursive vsnprintf".
266+
259267 Do not use this feature without some mechanism to verify the
260268 correctness of the format string and va_list arguments.
261269
@@ -284,6 +292,27 @@ bitmap and its derivatives such as cpumask and nodemask: · 22 unmodified lines
284292
285293 Passed by reference.
286294
295+Network device features:
296+
297+ %pNF 0x000000000000c000
298+
299+ For printing netdev_features_t.
300+
301+ Passed by reference.
302+
303+Command from struct task_struct
304+
305+ %pT ls
306+
307+ For printing executable name excluding path from struct
308+ task_struct.
309+
310+ Passed by reference.
311+
312+If you add other %p extensions, please extend lib/test_printf.c with
313+one or more test cases, if at all feasible.
314+
315+
287316 Thank you for your cooperation and attention.
288317
289318
Documentation/ptp/testptp.c+1−0
@@ -18,6 +18,7 @@ · 17 unmodified lines
1818 * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
1919 */
2020 #define _GNU_SOURCE
21+#define __SANE_USERSPACE_TYPES__ /* For PPC64, to get LL64 types */
2122 #include <errno.h>
2223 #include <fcntl.h>
2324 #include <inttypes.h>
Documentation/rbtree.txt+1−1
@@ -203,7 +203,7 @@ functions with the user provided augmentation callback when inserting · 202 unmodified lines
203203 and erasing nodes.
204204
205205 C files implementing augmented rbtree manipulation must include
206−<linux/rbtree_augmented.h> instead of <linus/rbtree.h>. Note that
206+<linux/rbtree_augmented.h> instead of <linux/rbtree.h>. Note that
207207 linux/rbtree_augmented.h exposes some rbtree implementations details
208208 you are not expected to rely on; please stick to the documented APIs
209209 there and do not include <linux/rbtree_augmented.h> from header files
Documentation/scsi/st.txt+3−1
@@ -569,7 +569,9 @@ Debugging code is now compiled in by default but debugging is turned off · 568 unmodified lines
569569 with the kernel module parameter debug_flag defaulting to 0. Debugging
570570 can still be switched on and off with an ioctl. To enable debug at
571571 module load time add debug_flag=1 to the module load options, the
572−debugging output is not voluminous.
572+debugging output is not voluminous. Debugging can also be enabled
573+and disabled by writing a '0' (disable) or '1' (enable) to the sysfs
574+file /sys/bus/scsi/drivers/st/debug_flag.
573575
574576 If the tape seems to hang, I would be very interested to hear where
575577 the driver is waiting. With the command 'ps -l' you can see the state
Documentation/security/Smack.txt+10−0
@@ -255,6 +255,16 @@ unconfined · 254 unmodified lines
255255 the access permitted if it wouldn't be otherwise. Note that this
256256 is dangerous and can ruin the proper labeling of your system.
257257 It should never be used in production.
258+relabel-self
259+ This interface contains a list of labels to which the process can
260+ transition to, by writing to /proc/self/attr/current.
261+ Normally a process can change its own label to any legal value, but only
262+ if it has CAP_MAC_ADMIN. This interface allows a process without
263+ CAP_MAC_ADMIN to relabel itself to one of labels from predefined list.
264+ A process without CAP_MAC_ADMIN can change its label only once. When it
265+ does, this list will be cleared.
266+ The values are set by writing the desired labels, separated
267+ by spaces, to the file or cleared by writing "-" to the file.
258268
259269 If you are using the smackload utility
260270 you can add access rules in /etc/smack/accesses. They take the form:
Documentation/security/keys.txt+25−16
@@ -1049,12 +1049,12 @@ search a specific keyring, so using keyrings in this way is of limited utility. · 1048 unmodified lines
10491049 NOTES ON ACCESSING PAYLOAD CONTENTS
10501050 ===================================
10511051
1052−The simplest payload is just a number in key->payload.value. In this case,
1053−there's no need to indulge in RCU or locking when accessing the payload.
1052+The simplest payload is just data stored in key->payload directly. In this
1053+case, there's no need to indulge in RCU or locking when accessing the payload.
10541054
1055−More complex payload contents must be allocated and a pointer to them set in
1056−key->payload.data. One of the following ways must be selected to access the
1057−data:
1055+More complex payload contents must be allocated and pointers to them set in the
1056+key->payload.data[] array. One of the following ways must be selected to
1057+access the data:
10581058
10591059 (1) Unmodifiable key type.
10601060
@@ -1092,6 +1092,13 @@ data: · 31 unmodified lines
10921092 the payload. key->datalen cannot be relied upon to be consistent with the
10931093 payload just dereferenced if the key's semaphore is not held.
10941094
1095+ Note that key->payload.data[0] has a shadow that is marked for __rcu
1096+ usage. This is called key->payload.rcu_data0. The following accessors
1097+ wrap the RCU calls to this element:
1098+
1099+ rcu_assign_keypointer(struct key *key, void *data);
1100+ void *rcu_dereference_key(struct key *key);
1101+
10951102
10961103 ===================
10971104 DEFINING A KEY TYPE
@@ -1143,8 +1150,7 @@ The structure has a number of fields, some of which are mandatory: · 45 unmodified lines
11431150
11441151 struct key_preparsed_payload {
11451152 char *description;
1146− void *type_data[2];
1147− void *payload;
1153+ union key_payload payload;
11481154 const void *data;
11491155 size_t datalen;
11501156 size_t quotalen;
@@ -1160,10 +1166,9 @@ The structure has a number of fields, some of which are mandatory: · 9 unmodified lines
11601166 attached as a string to the description field. This will be used for the
11611167 key description if the caller of add_key() passes NULL or "".
11621168
1163− The method can attach anything it likes to type_data[] and payload. These
1164− are merely passed along to the instantiate() or update() operations. If
1165− set, the expiry time will be applied to the key if it is instantiated from
1166− this data.
1169+ The method can attach anything it likes to payload. This is merely passed
1170+ along to the instantiate() or update() operations. If set, the expiry
1171+ time will be applied to the key if it is instantiated from this data.
11671172
11681173 The method should return 0 if successful or a negative error code
11691174 otherwise.
@@ -1172,11 +1177,10 @@ The structure has a number of fields, some of which are mandatory: · 2 unmodified lines
11721177 (*) void (*free_preparse)(struct key_preparsed_payload *prep);
11731178
11741179 This method is only required if the preparse() method is provided,
1175− otherwise it is unused. It cleans up anything attached to the
1176− description, type_data and payload fields of the key_preparsed_payload
1177− struct as filled in by the preparse() method. It will always be called
1178− after preparse() returns successfully, even if instantiate() or update()
1179− succeed.
1180+ otherwise it is unused. It cleans up anything attached to the description
1181+ and payload fields of the key_preparsed_payload struct as filled in by the
1182+ preparse() method. It will always be called after preparse() returns
1183+ successfully, even if instantiate() or update() succeed.
11801184
11811185
11821186 (*) int (*instantiate)(struct key *key, struct key_preparsed_payload *prep);
@@ -1197,6 +1201,11 @@ The structure has a number of fields, some of which are mandatory: · 14 unmodified lines
11971201
11981202 It is safe to sleep in this method.
11991203
1204+ generic_key_instantiate() is provided to simply copy the data from
1205+ prep->payload.data[] to key->payload.data[], with RCU-safe assignment on
1206+ the first element. It will then clear prep->payload.data[] so that the
1207+ free_preparse method doesn't release the data.
1208+
12001209
12011210 (*) int (*update)(struct key *key, const void *data, size_t datalen);
12021211
Documentation/serial/driver+9−1
@@ -439,11 +439,13 @@ Modem control lines via GPIO · 438 unmodified lines
439439
440440 Some helpers are provided in order to set/get modem control lines via GPIO.
441441
442−mctrl_gpio_init(dev, idx):
442+mctrl_gpio_init(port, idx):
443443 This will get the {cts,rts,...}-gpios from device tree if they are
444444 present and request them, set direction etc, and return an
445445 allocated structure. devm_* functions are used, so there's no need
446446 to call mctrl_gpio_free().
447+ As this sets up the irq handling make sure to not handle changes to the
448+ gpio input lines in your driver, too.
447449
448450 mctrl_gpio_free(dev, gpios):
449451 This will free the requested gpios in mctrl_gpio_init().
@@ -458,3 +460,9 @@ mctrl_gpio_set(gpios, mctrl): · 8 unmodified lines
458460
459461 mctrl_gpio_get(gpios, mctrl):
460462 This will update mctrl with the gpios values.
463+
464+mctrl_gpio_enable_ms(gpios):
465+ Enables irqs and handling of changes to the ms lines.
466+
467+mctrl_gpio_disable_ms(gpios):
468+ Disables irqs and handling of changes to the ms lines.
Documentation/serial/tty.txt+39−21
@@ -39,8 +39,13 @@ TTY side interfaces: · 38 unmodified lines
3939 open() - Called when the line discipline is attached to
4040 the terminal. No other call into the line
4141 discipline for this tty will occur until it
42− completes successfully. Returning an error will
43− prevent the ldisc from being attached. Can sleep.
42+ completes successfully. Should initialize any
43+ state needed by the ldisc, and set receive_room
44+ in the tty_struct to the maximum amount of data
45+ the line discipline is willing to accept from the
46+ driver with a single call to receive_buf().
47+ Returning an error will prevent the ldisc from
48+ being attached. Can sleep.
4449
4550 close() - This is called on a terminal when the line
4651 discipline is being unplugged. At the point of
@@ -52,9 +57,16 @@ hangup() - Called when the tty line is hung up. · 5 unmodified lines
5257 No further calls into the ldisc code will occur.
5358 The return value is ignored. Can sleep.
5459
55−write() - A process is writing data through the line
56− discipline. Multiple write calls are serialized
57− by the tty layer for the ldisc. May sleep.
60+read() - (optional) A process requests reading data from
61+ the line. Multiple read calls may occur in parallel
62+ and the ldisc must deal with serialization issues.
63+ If not defined, the process will receive an EIO
64+ error. May sleep.
65+
66+write() - (optional) A process requests writing data to the
67+ line. Multiple write calls are serialized by the
68+ tty layer for the ldisc. If not defined, the
69+ process will receive an EIO error. May sleep.
5870
5971 flush_buffer() - (optional) May be called at any point between
6072 open and close, and instructs the line discipline
@@ -69,27 +81,33 @@ set_termios() - (optional) Called on termios structure changes. · 8 unmodified lines
6981 termios semaphore so allowed to sleep. Serialized
7082 against itself only.
7183
72−read() - Move data from the line discipline to the user.
73− Multiple read calls may occur in parallel and the
74− ldisc must deal with serialization issues. May
75− sleep.
76−
77−poll() - Check the status for the poll/select calls. Multiple
78− poll calls may occur in parallel. May sleep.
84+poll() - (optional) Check the status for the poll/select
85+ calls. Multiple poll calls may occur in parallel.
86+ May sleep.
7987
80−ioctl() - Called when an ioctl is handed to the tty layer
81− that might be for the ldisc. Multiple ioctl calls
82− may occur in parallel. May sleep.
88+ioctl() - (optional) Called when an ioctl is handed to the
89+ tty layer that might be for the ldisc. Multiple
90+ ioctl calls may occur in parallel. May sleep.
8391
84−compat_ioctl() - Called when a 32 bit ioctl is handed to the tty layer
85− that might be for the ldisc. Multiple ioctl calls
86− may occur in parallel. May sleep.
92+compat_ioctl() - (optional) Called when a 32 bit ioctl is handed
93+ to the tty layer that might be for the ldisc.
94+ Multiple ioctl calls may occur in parallel.
95+ May sleep.
8796
8897 Driver Side Interfaces:
8998
90−receive_buf() - Hand buffers of bytes from the driver to the ldisc
91− for processing. Semantics currently rather
92− mysterious 8(
99+receive_buf() - (optional) Called by the low-level driver to hand
100+ a buffer of received bytes to the ldisc for
101+ processing. The number of bytes is guaranteed not
102+ to exceed the current value of tty->receive_room.
103+ All bytes must be processed.
104+
105+receive_buf2() - (optional) Called by the low-level driver to hand
106+ a buffer of received bytes to the ldisc for
107+ processing. Returns the number of bytes processed.
108+
109+ If both receive_buf() and receive_buf2() are
110+ defined, receive_buf2() should be preferred.
93111
94112 write_wakeup() - May be called at any point between open and close.
95113 The TTY_DO_WRITE_WAKEUP flag indicates if a call
Documentation/sound/alsa/hda_codec.txt+0−322
@@ -1,322 +0,0 @@
1−Notes on Universal Interface for Intel High Definition Audio Codec
2−------------------------------------------------------------------
3−
4−Takashi Iwai <tiwai@suse.de>
5−
6−
7−[Still a draft version]
8−
9−
10−General
11−=======
12−
13−The snd-hda-codec module supports the generic access function for the
14−High Definition (HD) audio codecs. It's designed to be independent
15−from the controller code like ac97 codec module. The real accessors
16−from/to the controller must be implemented in the lowlevel driver.
17−
18−The structure of this module is similar with ac97_codec module.
19−Each codec chip belongs to a bus class which communicates with the
20−controller.
21−
22−
23−Initialization of Bus Instance
24−==============================
25−
26−The card driver has to create struct hda_bus at first. The template
27−struct should be filled and passed to the constructor:
28−
29−struct hda_bus_template {
30− void *private_data;
31− struct pci_dev *pci;
32− const char *modelname;
33− struct hda_bus_ops ops;
34−};
35−
36−The card driver can set and use the private_data field to retrieve its
37−own data in callback functions. The pci field is used when the patch
38−needs to check the PCI subsystem IDs, so on. For non-PCI system, it
39−doesn't have to be set, of course.
40−The modelname field specifies the board's specific configuration. The
41−string is passed to the codec parser, and it depends on the parser how
42−the string is used.
43−These fields, private_data, pci and modelname are all optional.
44−
45−The ops field contains the callback functions as the following:
46−
47−struct hda_bus_ops {
48− int (*command)(struct hda_codec *codec, hda_nid_t nid, int direct,
49− unsigned int verb, unsigned int parm);
50− unsigned int (*get_response)(struct hda_codec *codec);
51− void (*private_free)(struct hda_bus *);
52−#ifdef CONFIG_SND_HDA_POWER_SAVE
53− void (*pm_notify)(struct hda_codec *codec);
54−#endif
55−};
56−
57−The command callback is called when the codec module needs to send a
58−VERB to the controller. It's always a single command.
59−The get_response callback is called when the codec requires the answer
60−for the last command. These two callbacks are mandatory and have to
61−be given.
62−The third, private_free callback, is optional. It's called in the
63−destructor to release any necessary data in the lowlevel driver.
64−
65−The pm_notify callback is available only with
66−CONFIG_SND_HDA_POWER_SAVE kconfig. It's called when the codec needs
67−to power up or may power down. The controller should check the all
68−belonging codecs on the bus whether they are actually powered off
69−(check codec->power_on), and optionally the driver may power down the
70−controller side, too.
71−
72−The bus instance is created via snd_hda_bus_new(). You need to pass
73−the card instance, the template, and the pointer to store the
74−resultant bus instance.
75−
76−int snd_hda_bus_new(struct snd_card *card, const struct hda_bus_template *temp,
77− struct hda_bus **busp);
78−
79−It returns zero if successful. A negative return value means any
80−error during creation.
81−
82−
83−Creation of Codec Instance
84−==========================
85−
86−Each codec chip on the board is then created on the BUS instance.
87−To create a codec instance, call snd_hda_codec_new().
88−
89−int snd_hda_codec_new(struct hda_bus *bus, unsigned int codec_addr,
90− struct hda_codec **codecp);
91−
92−The first argument is the BUS instance, the second argument is the
93−address of the codec, and the last one is the pointer to store the
94−resultant codec instance (can be NULL if not needed).
95−
96−The codec is stored in a linked list of bus instance. You can follow
97−the codec list like:
98−
99− struct hda_codec *codec;
100− list_for_each_entry(codec, &bus->codec_list, list) {
101− ...
102− }
103−
104−The codec isn't initialized at this stage properly. The
105−initialization sequence is called when the controls are built later.
106−
107−
108−Codec Access
109−============
110−
111−To access codec, use snd_hda_codec_read() and snd_hda_codec_write().
112−snd_hda_param_read() is for reading parameters.
113−For writing a sequence of verbs, use snd_hda_sequence_write().
114−
115−There are variants of cached read/write, snd_hda_codec_write_cache(),
116−snd_hda_sequence_write_cache(). These are used for recording the
117−register states for the power-management resume. When no PM is needed,
118−these are equivalent with non-cached version.
119−
120−To retrieve the number of sub nodes connected to the given node, use
121−snd_hda_get_sub_nodes(). The connection list can be obtained via
122−snd_hda_get_connections() call.
123−
124−When an unsolicited event happens, pass the event via
125−snd_hda_queue_unsol_event() so that the codec routines will process it
126−later.
127−
128−
129−(Mixer) Controls
130−================
131−
132−To create mixer controls of all codecs, call
133−snd_hda_build_controls(). It then builds the mixers and does
134−initialization stuff on each codec.
135−
136−
137−PCM Stuff
138−=========
139−
140−snd_hda_build_pcms() gives the necessary information to create PCM
141−streams. When it's called, each codec belonging to the bus stores
142−codec->num_pcms and codec->pcm_info fields. The num_pcms indicates
143−the number of elements in pcm_info array. The card driver is supposed
144−to traverse the codec linked list, read the pcm information in
145−pcm_info array, and build pcm instances according to them.
146−
147−The pcm_info array contains the following record:
148−
149−/* PCM information for each substream */
150−struct hda_pcm_stream {
151− unsigned int substreams; /* number of substreams, 0 = not exist */
152− unsigned int channels_min; /* min. number of channels */
153− unsigned int channels_max; /* max. number of channels */
154− hda_nid_t nid; /* default NID to query rates/formats/bps, or set up */
155− u32 rates; /* supported rates */
156− u64 formats; /* supported formats (SNDRV_PCM_FMTBIT_) */
157− unsigned int maxbps; /* supported max. bit per sample */
158− struct hda_pcm_ops ops;
159−};
160−
161−/* for PCM creation */
162−struct hda_pcm {
163− char *name;
164− struct hda_pcm_stream stream[2];
165−};
166−
167−The name can be passed to snd_pcm_new(). The stream field contains
168−the information for playback (SNDRV_PCM_STREAM_PLAYBACK = 0) and
169−capture (SNDRV_PCM_STREAM_CAPTURE = 1) directions. The card driver
170−should pass substreams to snd_pcm_new() for the number of substreams
171−to create.
172−
173−The channels_min, channels_max, rates and formats should be copied to
174−runtime->hw record. They and maxbps fields are used also to compute
175−the format value for the HDA codec and controller. Call
176−snd_hda_calc_stream_format() to get the format value.
177−
178−The ops field contains the following callback functions:
179−
180−struct hda_pcm_ops {
181− int (*open)(struct hda_pcm_stream *info, struct hda_codec *codec,
182− struct snd_pcm_substream *substream);
183− int (*close)(struct hda_pcm_stream *info, struct hda_codec *codec,
184− struct snd_pcm_substream *substream);
185− int (*prepare)(struct hda_pcm_stream *info, struct hda_codec *codec,
186− unsigned int stream_tag, unsigned int format,
187− struct snd_pcm_substream *substream);
188− int (*cleanup)(struct hda_pcm_stream *info, struct hda_codec *codec,
189− struct snd_pcm_substream *substream);
190−};
191−
192−All are non-NULL, so you can call them safely without NULL check.
193−
194−The open callback should be called in PCM open after runtime->hw is
195−set up. It may override some setting and constraints additionally.
196−Similarly, the close callback should be called in the PCM close.
197−
198−The prepare callback should be called in PCM prepare. This will set
199−up the codec chip properly for the operation. The cleanup should be
200−called in hw_free to clean up the configuration.
201−
202−The caller should check the return value, at least for open and
203−prepare callbacks. When a negative value is returned, some error
204−occurred.
205−
206−
207−Proc Files
208−==========
209−
210−Each codec dumps the widget node information in
211−/proc/asound/card*/codec#* file. This information would be really
212−helpful for debugging. Please provide its contents together with the
213−bug report.
214−
215−
216−Power Management
217−================
218−
219−It's simple:
220−Call snd_hda_suspend() in the PM suspend callback.
221−Call snd_hda_resume() in the PM resume callback.
222−
223−
224−Codec Preset (Patch)
225−====================
226−
227−To set up and handle the codec functionality fully, each codec may
228−have a codec preset (patch). It's defined in struct hda_codec_preset:
229−
230− struct hda_codec_preset {
231− unsigned int id;
232− unsigned int mask;
233− unsigned int subs;
234− unsigned int subs_mask;
235− unsigned int rev;
236− const char *name;
237− int (*patch)(struct hda_codec *codec);
238− };
239−
240−When the codec id and codec subsystem id match with the given id and
241−subs fields bitwise (with bitmask mask and subs_mask), the callback
242−patch is called. The patch callback should initialize the codec and
243−set the codec->patch_ops field. This is defined as below:
244−
245− struct hda_codec_ops {
246− int (*build_controls)(struct hda_codec *codec);
247− int (*build_pcms)(struct hda_codec *codec);
248− int (*init)(struct hda_codec *codec);
249− void (*free)(struct hda_codec *codec);
250− void (*unsol_event)(struct hda_codec *codec, unsigned int res);
251− #ifdef CONFIG_PM
252− int (*suspend)(struct hda_codec *codec, pm_message_t state);
253− int (*resume)(struct hda_codec *codec);
254− #endif
255− #ifdef CONFIG_SND_HDA_POWER_SAVE
256− int (*check_power_status)(struct hda_codec *codec,
257− hda_nid_t nid);
258− #endif
259− };
260−
261−The build_controls callback is called from snd_hda_build_controls().
262−Similarly, the build_pcms callback is called from
263−snd_hda_build_pcms(). The init callback is called after
264−build_controls to initialize the hardware.
265−The free callback is called as a destructor.
266−
267−The unsol_event callback is called when an unsolicited event is
268−received.
269−
270−The suspend and resume callbacks are for power management.
271−They can be NULL if no special sequence is required. When the resume
272−callback is NULL, the driver calls the init callback and resumes the
273−registers from the cache. If other handling is needed, you'd need to
274−write your own resume callback. There, the amp values can be resumed
275−via
276− void snd_hda_codec_resume_amp(struct hda_codec *codec);
277−and the other codec registers via
278− void snd_hda_codec_resume_cache(struct hda_codec *codec);
279−
280−The check_power_status callback is called when the amp value of the
281−given widget NID is changed. The codec code can turn on/off the power
282−appropriately from this information.
283−
284−Each entry can be NULL if not necessary to be called.
285−
286−
287−Generic Parser
288−==============
289−
290−When the device doesn't match with any given presets, the widgets are
291−parsed via th generic parser (hda_generic.c). Its support is
292−limited: no multi-channel support, for example.
293−
294−
295−Digital I/O
296−===========
297−
298−Call snd_hda_create_spdif_out_ctls() from the patch to create controls
299−related with SPDIF out.
300−
301−
302−Helper Functions
303−================
304−
305−snd_hda_get_codec_name() stores the codec name on the given string.
306−
307−snd_hda_check_board_config() can be used to obtain the configuration
308−information matching with the device. Define the model string table
309−and the table with struct snd_pci_quirk entries (zero-terminated),
310−and pass it to the function. The function checks the modelname given
311−as a module parameter, and PCI subsystem IDs. If the matching entry
312−is found, it returns the config field value.
313−
314−snd_hda_add_new_ctls() can be used to create and add control entries.
315−Pass the zero-terminated array of struct snd_kcontrol_new
316−
317−Macros HDA_CODEC_VOLUME(), HDA_CODEC_MUTE() and their variables can be
318−used for the entry of struct snd_kcontrol_new.
319−
320−The input MUX helper callbacks for such a control are provided, too:
321−snd_hda_input_mux_info() and snd_hda_input_mux_put(). See
322−patch_realtek.c for example.
Documentation/spi/pxa2xx+0−6
@@ -22,15 +22,10 @@ Typically a SPI master is defined in the arch/.../mach-*/board-*.c as a · 21 unmodified lines
2222 found in include/linux/spi/pxa2xx_spi.h:
2323
2424 struct pxa2xx_spi_master {
25− u32 clock_enable;
2625 u16 num_chipselect;
2726 u8 enable_dma;
2827 };
2928
30−The "pxa2xx_spi_master.clock_enable" field is used to enable/disable the
31−corresponding SSP peripheral block in the "Clock Enable Register (CKEN"). See
32−the "PXA2xx Developer Manual" section "Clocks and Power Management".
33−
3429 The "pxa2xx_spi_master.num_chipselect" field is used to determine the number of
3530 slave device (chips) attached to this SPI master.
3631
@@ -57,7 +52,6 @@ static struct resource pxa_spi_nssp_resources[] = { · 20 unmodified lines
5752 };
5853
5954 static struct pxa2xx_spi_master pxa_nssp_master_info = {
60− .clock_enable = CKEN_NSSP, /* NSSP Peripheral clock */
6155 .num_chipselect = 1, /* Matches the number of chips attached to NSSP */
6256 .enable_dma = 1, /* Enables NSSP DMA */
6357 };
Documentation/sysctl/kernel.txt+12−0
@@ -33,6 +33,7 @@ show up in /proc/sys/kernel: · 32 unmodified lines
3333 - domainname
3434 - hostname
3535 - hotplug
36+- hardlockup_all_cpu_backtrace
3637 - hung_task_panic
3738 - hung_task_check_count
3839 - hung_task_timeout_secs
@@ -292,6 +293,17 @@ Information Service) or YP (Yellow Pages) domainname. These two · 253 unmodified lines
292293 domain names are in general different. For a detailed discussion
293294 see the hostname(1) man page.
294295
296+==============================================================
297+hardlockup_all_cpu_backtrace:
298+
299+This value controls the hard lockup detector behavior when a hard
300+lockup condition is detected as to whether or not to gather further
301+debug information. If enabled, arch-specific all-CPU stack dumping
302+will be initiated.
303+
304+0: do nothing. This is the default behavior.
305+
306+1: on detection capture more debug information.
295307 ==============================================================
296308
297309 hotplug:
Documentation/sysctl/vm.txt+1−1
@@ -639,7 +639,7 @@ and don't use much of it. · 638 unmodified lines
639639 The default value is 0.
640640
641641 See Documentation/vm/overcommit-accounting and
642−security/commoncap.c::cap_vm_enough_memory() for more information.
642+mm/mmap.c::__vm_enough_memory() for more information.
643643
644644 ==============================================================
645645
Documentation/target/tcm_mod_builder.py+0−17
@@ -203,8 +203,6 @@ def tcm_mod_build_configfs(proto_ident, fabric_mod_dir_var, fabric_mod_name): · 202 unmodified lines
203203 buf += "#include <scsi/scsi_proto.h>\n\n"
204204 buf += "#include <target/target_core_base.h>\n"
205205 buf += "#include <target/target_core_fabric.h>\n"
206− buf += "#include <target/target_core_fabric_configfs.h>\n"
207− buf += "#include <target/configfs_macros.h>\n\n"
208206 buf += "#include \"" + fabric_mod_name + "_base.h\"\n"
209207 buf += "#include \"" + fabric_mod_name + "_fabric.h\"\n\n"
210208
@@ -283,19 +281,6 @@ def tcm_mod_build_configfs(proto_ident, fabric_mod_dir_var, fabric_mod_name): · 72 unmodified lines
283281 buf += " struct " + fabric_mod_name + "_" + fabric_mod_port + ", " + fabric_mod_port + "_wwn);\n"
284282 buf += " kfree(" + fabric_mod_port + ");\n"
285283 buf += "}\n\n"
286− buf += "static ssize_t " + fabric_mod_name + "_wwn_show_attr_version(\n"
287− buf += " struct target_fabric_configfs *tf,\n"
288− buf += " char *page)\n"
289− buf += "{\n"
290− buf += " return sprintf(page, \"" + fabric_mod_name.upper() + " fabric module %s on %s/%s\"\n"
291− buf += " \"on \"UTS_RELEASE\"\\n\", " + fabric_mod_name.upper() + "_VERSION, utsname()->sysname,\n"
292− buf += " utsname()->machine);\n"
293− buf += "}\n\n"
294− buf += "TF_WWN_ATTR_RO(" + fabric_mod_name + ", version);\n\n"
295− buf += "static struct configfs_attribute *" + fabric_mod_name + "_wwn_attrs[] = {\n"
296− buf += " &" + fabric_mod_name + "_wwn_version.attr,\n"
297− buf += " NULL,\n"
298− buf += "};\n\n"
299284
300285 buf += "static const struct target_core_fabric_ops " + fabric_mod_name + "_ops = {\n"
301286 buf += " .module = THIS_MODULE,\n"
@@ -328,8 +313,6 @@ def tcm_mod_build_configfs(proto_ident, fabric_mod_dir_var, fabric_mod_name): · 26 unmodified lines
328313 buf += " .fabric_drop_wwn = " + fabric_mod_name + "_drop_" + fabric_mod_port + ",\n"
329314 buf += " .fabric_make_tpg = " + fabric_mod_name + "_make_tpg,\n"
330315 buf += " .fabric_drop_tpg = " + fabric_mod_name + "_drop_tpg,\n"
331− buf += "\n"
332− buf += " .tfc_wwn_attrs = " + fabric_mod_name + "_wwn_attrs,\n"
333316 buf += "};\n\n"
334317
335318 buf += "static int __init " + fabric_mod_name + "_init(void)\n"
Documentation/trace/events.txt+18−0
@@ -288,6 +288,24 @@ prev_pid == 0 · 287 unmodified lines
288288 # cat sched_wakeup/filter
289289 common_pid == 0
290290
291+5.4 PID filtering
292+-----------------
293+
294+The set_event_pid file in the same directory as the top events directory
295+exists, will filter all events from tracing any task that does not have the
296+PID listed in the set_event_pid file.
297+
298+# cd /sys/kernel/debug/tracing
299+# echo $$ > set_event_pid
300+# echo 1 > events/enabled
301+
302+Will only trace events for the current task.
303+
304+To add more PIDs without losing the PIDs already included, use '>>'.
305+
306+# echo 123 244 1 >> set_event_pid
307+
308+
291309 6. Event triggers
292310 =================
293311
Documentation/trace/ftrace.txt+23−0
@@ -204,6 +204,12 @@ of ftrace. Here is a list of some of the key files: · 203 unmodified lines
204204
205205 Have the function tracer only trace a single thread.
206206
207+ set_event_pid:
208+
209+ Have the events only trace a task with a PID listed in this file.
210+ Note, sched_switch and sched_wake_up will also trace events
211+ listed in this file.
212+
207213 set_graph_function:
208214
209215 Set a "trigger" function where tracing should start
@@ -2437,6 +2443,23 @@ The following commands are supported: · 2227 unmodified lines
24372443
24382444 echo '!writeback*:mod:ext3' >> set_ftrace_filter
24392445
2446+ Mod command supports module globbing. Disable tracing for all
2447+ functions except a specific module:
2448+
2449+ echo '!*:mod:!ext3' >> set_ftrace_filter
2450+
2451+ Disable tracing for all modules, but still trace kernel:
2452+
2453+ echo '!*:mod:*' >> set_ftrace_filter
2454+
2455+ Enable filter only for kernel:
2456+
2457+ echo '*write*:mod:!*' >> set_ftrace_filter
2458+
2459+ Enable filter for module globbing:
2460+
2461+ echo '*write*:mod:*snd*' >> set_ftrace_filter
2462+
24402463 - traceon/traceoff
24412464 These commands turn tracing on and off when the specified
24422465 functions are hit. The parameter determines how many times the
Documentation/trace/intel_th.txt+99−0
@@ -0,0 +1,99 @@
1+Intel(R) Trace Hub (TH)
2+=======================
3+
4+Overview
5+--------
6+
7+Intel(R) Trace Hub (TH) is a set of hardware blocks that produce,
8+switch and output trace data from multiple hardware and software
9+sources over several types of trace output ports encoded in System
10+Trace Protocol (MIPI STPv2) and is intended to perform full system
11+debugging. For more information on the hardware, see Intel(R) Trace
12+Hub developer's manual [1].
13+
14+It consists of trace sources, trace destinations (outputs) and a
15+switch (Global Trace Hub, GTH). These devices are placed on a bus of
16+their own ("intel_th"), where they can be discovered and configured
17+via sysfs attributes.
18+
19+Currently, the following Intel TH subdevices (blocks) are supported:
20+ - Software Trace Hub (STH), trace source, which is a System Trace
21+ Module (STM) device,
22+ - Memory Storage Unit (MSU), trace output, which allows storing
23+ trace hub output in system memory,
24+ - Parallel Trace Interface output (PTI), trace output to an external
25+ debug host via a PTI port,
26+ - Global Trace Hub (GTH), which is a switch and a central component
27+ of Intel(R) Trace Hub architecture.
28+
29+Common attributes for output devices are described in
30+Documentation/ABI/testing/sysfs-bus-intel_th-output-devices, the most
31+notable of them is "active", which enables or disables trace output
32+into that particular output device.
33+
34+GTH allows directing different STP masters into different output ports
35+via its "masters" attribute group. More detailed GTH interface
36+description is at Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth.
37+
38+STH registers an stm class device, through which it provides interface
39+to userspace and kernelspace software trace sources. See
40+Documentation/tracing/stm.txt for more information on that.
41+
42+MSU can be configured to collect trace data into a system memory
43+buffer, which can later on be read from its device nodes via read() or
44+mmap() interface.
45+
46+On the whole, Intel(R) Trace Hub does not require any special
47+userspace software to function; everything can be configured, started
48+and collected via sysfs attributes, and device nodes.
49+
50+[1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
51+
52+Bus and Subdevices
53+------------------
54+
55+For each Intel TH device in the system a bus of its own is
56+created and assigned an id number that reflects the order in which TH
57+devices were emumerated. All TH subdevices (devices on intel_th bus)
58+begin with this id: 0-gth, 0-msc0, 0-msc1, 0-pti, 0-sth, which is
59+followed by device's name and an optional index.
60+
61+Output devices also get a device node in /dev/intel_thN, where N is
62+the Intel TH device id. For example, MSU's memory buffers, when
63+allocated, are accessible via /dev/intel_th0/msc{0,1}.
64+
65+Quick example
66+-------------
67+
68+# figure out which GTH port is the first memory controller:
69+
70+$ cat /sys/bus/intel_th/devices/0-msc0/port
71+0
72+
73+# looks like it's port 0, configure master 33 to send data to port 0:
74+
75+$ echo 0 > /sys/bus/intel_th/devices/0-gth/masters/33
76+
77+# allocate a 2-windowed multiblock buffer on the first memory
78+# controller, each with 64 pages:
79+
80+$ echo multi > /sys/bus/intel_th/devices/0-msc0/mode
81+$ echo 64,64 > /sys/bus/intel_th/devices/0-msc0/nr_pages
82+
83+# enable wrapping for this controller, too:
84+
85+$ echo 1 > /sys/bus/intel_th/devices/0-msc0/wrap
86+
87+# and enable tracing into this port:
88+
89+$ echo 1 > /sys/bus/intel_th/devices/0-msc0/active
90+
91+# .. send data to master 33, see stm.txt for more details ..
92+# .. wait for traces to pile up ..
93+# .. and stop the trace:
94+
95+$ echo 0 > /sys/bus/intel_th/devices/0-msc0/active
96+
97+# and now you can collect the trace from the device node:
98+
99+$ cat /dev/intel_th0/msc0 > my_stp_trace
Documentation/trace/stm.txt+80−0
@@ -0,0 +1,80 @@
1+System Trace Module
2+===================
3+
4+System Trace Module (STM) is a device described in MIPI STP specs as
5+STP trace stream generator. STP (System Trace Protocol) is a trace
6+protocol multiplexing data from multiple trace sources, each one of
7+which is assigned a unique pair of master and channel. While some of
8+these masters and channels are statically allocated to certain
9+hardware trace sources, others are available to software. Software
10+trace sources are usually free to pick for themselves any
11+master/channel combination from this pool.
12+
13+On the receiving end of this STP stream (the decoder side), trace
14+sources can only be identified by master/channel combination, so in
15+order for the decoder to be able to make sense of the trace that
16+involves multiple trace sources, it needs to be able to map those
17+master/channel pairs to the trace sources that it understands.
18+
19+For instance, it is helpful to know that syslog messages come on
20+master 7 channel 15, while arbitrary user applications can use masters
21+48 to 63 and channels 0 to 127.
22+
23+To solve this mapping problem, stm class provides a policy management
24+mechanism via configfs, that allows defining rules that map string
25+identifiers to ranges of masters and channels. If these rules (policy)
26+are consistent with what decoder expects, it will be able to properly
27+process the trace data.
28+
29+This policy is a tree structure containing rules (policy_node) that
30+have a name (string identifier) and a range of masters and channels
31+associated with it, located in "stp-policy" subsystem directory in
32+configfs. The topmost directory's name (the policy) is formatted as
33+the STM device name to which this policy applies and and arbitrary
34+string identifier separated by a stop. From the examle above, a rule
35+may look like this:
36+
37+$ ls /config/stp-policy/dummy_stm.my-policy/user
38+channels masters
39+$ cat /config/stp-policy/dummy_stm.my-policy/user/masters
40+48 63
41+$ cat /config/stp-policy/dummy_stm.my-policy/user/channels
42+0 127
43+
44+which means that the master allocation pool for this rule consists of
45+masters 48 through 63 and channel allocation pool has channels 0
46+through 127 in it. Now, any producer (trace source) identifying itself
47+with "user" identification string will be allocated a master and
48+channel from within these ranges.
49+
50+These rules can be nested, for example, one can define a rule "dummy"
51+under "user" directory from the example above and this new rule will
52+be used for trace sources with the id string of "user/dummy".
53+
54+Trace sources have to open the stm class device's node and write their
55+trace data into its file descriptor. In order to identify themselves
56+to the policy, they need to do a STP_POLICY_ID_SET ioctl on this file
57+descriptor providing their id string. Otherwise, they will be
58+automatically allocated a master/channel pair upon first write to this
59+file descriptor according to the "default" rule of the policy, if such
60+exists.
61+
62+Some STM devices may allow direct mapping of the channel mmio regions
63+to userspace for zero-copy writing. One mappable page (in terms of
64+mmu) will usually contain multiple channels' mmios, so the user will
65+need to allocate that many channels to themselves (via the
66+aforementioned ioctl() call) to be able to do this. That is, if your
67+stm device's channel mmio region is 64 bytes and hardware page size is
68+4096 bytes, after a successful STP_POLICY_ID_SET ioctl() call with
69+width==64, you should be able to mmap() one page on this file
70+descriptor and obtain direct access to an mmio region for 64 channels.
71+
72+For kernel-based trace sources, there is "stm_source" device
73+class. Devices of this class can be connected and disconnected to/from
74+stm devices at runtime via a sysfs attribute.
75+
76+Examples of STM devices are Intel(R) Trace Hub [1] and Coresight STM
77+[2].
78+
79+[1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
80+[2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
Documentation/usb/authorization.txt+31−0
@@ -90,3 +90,34 @@ etc, but you get the idea. Anybody with access to a device gadget kit · 89 unmodified lines
9090 can fake descriptors and device info. Don't trust that. You are
9191 welcome.
9292
93+
94+Interface authorization
95+-----------------------
96+There is a similar approach to allow or deny specific USB interfaces.
97+That allows to block only a subset of an USB device.
98+
99+Authorize an interface:
100+$ echo 1 > /sys/bus/usb/devices/INTERFACE/authorized
101+
102+Deauthorize an interface:
103+$ echo 0 > /sys/bus/usb/devices/INTERFACE/authorized
104+
105+The default value for new interfaces
106+on a particular USB bus can be changed, too.
107+
108+Allow interfaces per default:
109+$ echo 1 > /sys/bus/usb/devices/usbX/interface_authorized_default
110+
111+Deny interfaces per default:
112+$ echo 0 > /sys/bus/usb/devices/usbX/interface_authorized_default
113+
114+Per default the interface_authorized_default bit is 1.
115+So all interfaces would authorized per default.
116+
117+Note:
118+If a deauthorized interface will be authorized so the driver probing must
119+be triggered manually by writing INTERFACE to /sys/bus/usb/drivers_probe
120+
121+For drivers that need multiple interfaces all needed interfaces should be
122+authroized first. After that the drivers should be probed.
123+This avoids side effects.
Documentation/video4linux/CARDLIST.saa7134+1−0
@@ -193,3 +193,4 @@ · 192 unmodified lines
193193 192 -> AverMedia AverTV Satellite Hybrid+FM A706 [1461:2055]
194194 193 -> WIS Voyager or compatible [1905:7007]
195195 194 -> AverMedia AverTV/505 [1461:a10a]
196+195 -> Leadtek Winfast TV2100 FM [107d:6f3a]
Documentation/video4linux/v4l2-pci-skeleton.c+3−1
@@ -37,6 +37,7 @@ · 36 unmodified lines
3737 #include <media/v4l2-dv-timings.h>
3838 #include <media/v4l2-ctrls.h>
3939 #include <media/v4l2-event.h>
40+#include <media/videobuf2-v4l2.h>
4041 #include <media/videobuf2-dma-contig.h>
4142
4243 MODULE_DESCRIPTION("V4L2 PCI Skeleton Driver");
@@ -162,10 +163,11 @@ static irqreturn_t skeleton_irq(int irq, void *dev_id) · 119 unmodified lines
162163 * minimum number: many DMA engines need a minimum of 2 buffers in the
163164 * queue and you need to have another available for userspace processing.
164165 */
165−static int queue_setup(struct vb2_queue *vq, const struct v4l2_format *fmt,
166+static int queue_setup(struct vb2_queue *vq, const void *parg,
166167 unsigned int *nbuffers, unsigned int *nplanes,
167168 unsigned int sizes[], void *alloc_ctxs[])
168169 {
170+ const struct v4l2_format *fmt = parg;
169171 struct skeleton *skel = vb2_get_drv_priv(vq);
170172
171173 skel->field = skel->format.field;
Documentation/virtual/kvm/api.txt+49−7
@@ -401,10 +401,9 @@ Capability: basic · 400 unmodified lines
401401 Architectures: x86, ppc, mips
402402 Type: vcpu ioctl
403403 Parameters: struct kvm_interrupt (in)
404−Returns: 0 on success, -1 on error
404+Returns: 0 on success, negative on failure.
405405
406−Queues a hardware interrupt vector to be injected. This is only
407−useful if in-kernel local APIC or equivalent is not used.
406+Queues a hardware interrupt vector to be injected.
408407
409408 /* for KVM_INTERRUPT */
410409 struct kvm_interrupt {
@@ -414,7 +413,14 @@ struct kvm_interrupt { · 3 unmodified lines
414413
415414 X86:
416415
417−Note 'irq' is an interrupt vector, not an interrupt pin or line.
416+Returns: 0 on success,
417+ -EEXIST if an interrupt is already enqueued
418+ -EINVAL the the irq number is invalid
419+ -ENXIO if the PIC is in the kernel
420+ -EFAULT if the pointer is invalid
421+
422+Note 'irq' is an interrupt vector, not an interrupt pin or line. This
423+ioctl is useful if the in-kernel PIC is not used.
418424
419425 PPC:
420426
@@ -1598,7 +1604,7 @@ provided event instead of triggering an exit. · 1177 unmodified lines
15981604 struct kvm_ioeventfd {
15991605 __u64 datamatch;
16001606 __u64 addr; /* legal pio/mmio address */
1601− __u32 len; /* 1, 2, 4, or 8 bytes */
1607+ __u32 len; /* 0, 1, 2, 4, or 8 bytes */
16021608 __s32 fd;
16031609 __u32 flags;
16041610 __u8 pad[36];
@@ -1621,6 +1627,10 @@ to the registered address is equal to datamatch in struct kvm_ioeventfd. · 16 unmodified lines
16211627 For virtio-ccw devices, addr contains the subchannel id and datamatch the
16221628 virtqueue index.
16231629
1630+With KVM_CAP_IOEVENTFD_ANY_LENGTH, a zero length ioeventfd is allowed, and
1631+the kernel will ignore the length of guest write and may get a faster vmexit.
1632+The speedup may only apply to specific architectures, but the ioeventfd will
1633+work anyway.
16241634
16251635 4.60 KVM_DIRTY_TLB
16261636
@@ -1774,7 +1784,7 @@ has been called, this interface is completely emulated within the kernel. · 147 unmodified lines
17741784 To use this to emulate the LINT1 input with KVM_CREATE_IRQCHIP, use the
17751785 following algorithm:
17761786
1777− - pause the vpcu
1787+ - pause the vcpu
17781788 - read the local APIC's state (KVM_GET_LAPIC)
17791789 - check whether changing LINT1 will queue an NMI (see the LVT entry for LINT1)
17801790 - if so, issue KVM_NMI
@@ -2798,7 +2808,7 @@ Returns: = 0 on success, · 1017 unmodified lines
27982808 < 0 on generic error (e.g. -EFAULT or -ENOMEM),
27992809 > 0 if an exception occurred while walking the page tables
28002810
2801−Read or write data from/to the logical (virtual) memory of a VPCU.
2811+Read or write data from/to the logical (virtual) memory of a VCPU.
28022812
28032813 Parameters are specified via the following structure:
28042814
@@ -3309,6 +3319,18 @@ Valid values for 'type' are: · 504 unmodified lines
33093319 to ignore the request, or to gather VM memory core dump and/or
33103320 reset/shutdown of the VM.
33113321
3322+ /* KVM_EXIT_IOAPIC_EOI */
3323+ struct {
3324+ __u8 vector;
3325+ } eoi;
3326+
3327+Indicates that the VCPU's in-kernel local APIC received an EOI for a
3328+level-triggered IOAPIC interrupt. This exit only triggers when the
3329+IOAPIC is implemented in userspace (i.e. KVM_CAP_SPLIT_IRQCHIP is enabled);
3330+the userspace IOAPIC should process the EOI and retrigger the interrupt if
3331+it is still asserted. Vector is the LAPIC interrupt vector for which the
3332+EOI was received.
3333+
33123334 /* Fix the size of the union. */
33133335 char padding[256];
33143336 };
@@ -3627,6 +3649,26 @@ struct { · 312 unmodified lines
36273649
36283650 KVM handlers should exit to userspace with rc = -EREMOTE.
36293651
3652+7.5 KVM_CAP_SPLIT_IRQCHIP
3653+
3654+Architectures: x86
3655+Parameters: args[0] - number of routes reserved for userspace IOAPICs
3656+Returns: 0 on success, -1 on error
3657+
3658+Create a local apic for each processor in the kernel. This can be used
3659+instead of KVM_CREATE_IRQCHIP if the userspace VMM wishes to emulate the
3660+IOAPIC and PIC (and also the PIT, even though this has to be enabled
3661+separately).
3662+
3663+This capability also enables in kernel routing of interrupt requests;
3664+when KVM_CAP_SPLIT_IRQCHIP only routes of KVM_IRQ_ROUTING_MSI type are
3665+used in the IRQ routing table. The first args[0] MSI routes are reserved
3666+for the IOAPIC pins. Whenever the LAPIC receives an EOI for these routes,
3667+a KVM_EXIT_IOAPIC_EOI vmexit will be reported to userspace.
3668+
3669+Fails if VCPU has already been created, or if the irqchip is already in the
3670+kernel (i.e. KVM_CREATE_IRQCHIP has already been called).
3671+
36303672
36313673 8. Other capabilities.
36323674 ----------------------
Documentation/virtual/kvm/arm/vgic-mapped-irqs.txt+187−0
@@ -0,0 +1,187 @@
1+KVM/ARM VGIC Forwarded Physical Interrupts
2+==========================================
3+
4+The KVM/ARM code implements software support for the ARM Generic
5+Interrupt Controller's (GIC's) hardware support for virtualization by
6+allowing software to inject virtual interrupts to a VM, which the guest
7+OS sees as regular interrupts. The code is famously known as the VGIC.
8+
9+Some of these virtual interrupts, however, correspond to physical
10+interrupts from real physical devices. One example could be the
11+architected timer, which itself supports virtualization, and therefore
12+lets a guest OS program the hardware device directly to raise an
13+interrupt at some point in time. When such an interrupt is raised, the
14+host OS initially handles the interrupt and must somehow signal this
15+event as a virtual interrupt to the guest. Another example could be a
16+passthrough device, where the physical interrupts are initially handled
17+by the host, but the device driver for the device lives in the guest OS
18+and KVM must therefore somehow inject a virtual interrupt on behalf of
19+the physical one to the guest OS.
20+
21+These virtual interrupts corresponding to a physical interrupt on the
22+host are called forwarded physical interrupts, but are also sometimes
23+referred to as 'virtualized physical interrupts' and 'mapped interrupts'.
24+
25+Forwarded physical interrupts are handled slightly differently compared
26+to virtual interrupts generated purely by a software emulated device.
27+
28+
29+The HW bit
30+----------
31+Virtual interrupts are signalled to the guest by programming the List
32+Registers (LRs) on the GIC before running a VCPU. The LR is programmed
33+with the virtual IRQ number and the state of the interrupt (Pending,
34+Active, or Pending+Active). When the guest ACKs and EOIs a virtual
35+interrupt, the LR state moves from Pending to Active, and finally to
36+inactive.
37+
38+The LRs include an extra bit, called the HW bit. When this bit is set,
39+KVM must also program an additional field in the LR, the physical IRQ
40+number, to link the virtual with the physical IRQ.
41+
42+When the HW bit is set, KVM must EITHER set the Pending OR the Active
43+bit, never both at the same time.
44+
45+Setting the HW bit causes the hardware to deactivate the physical
46+interrupt on the physical distributor when the guest deactivates the
47+corresponding virtual interrupt.
48+
49+
50+Forwarded Physical Interrupts Life Cycle
51+----------------------------------------
52+
53+The state of forwarded physical interrupts is managed in the following way:
54+
55+ - The physical interrupt is acked by the host, and becomes active on
56+ the physical distributor (*).
57+ - KVM sets the LR.Pending bit, because this is the only way the GICV
58+ interface is going to present it to the guest.
59+ - LR.Pending will stay set as long as the guest has not acked the interrupt.
60+ - LR.Pending transitions to LR.Active on the guest read of the IAR, as
61+ expected.
62+ - On guest EOI, the *physical distributor* active bit gets cleared,
63+ but the LR.Active is left untouched (set).
64+ - KVM clears the LR on VM exits when the physical distributor
65+ active state has been cleared.
66+
67+(*): The host handling is slightly more complicated. For some forwarded
68+interrupts (shared), KVM directly sets the active state on the physical
69+distributor before entering the guest, because the interrupt is never actually
70+handled on the host (see details on the timer as an example below). For other
71+forwarded interrupts (non-shared) the host does not deactivate the interrupt
72+when the host ISR completes, but leaves the interrupt active until the guest
73+deactivates it. Leaving the interrupt active is allowed, because Linux
74+configures the physical GIC with EOIMode=1, which causes EOI operations to
75+perform a priority drop allowing the GIC to receive other interrupts of the
76+default priority.
77+
78+
79+Forwarded Edge and Level Triggered PPIs and SPIs
80+------------------------------------------------
81+Forwarded physical interrupts injected should always be active on the
82+physical distributor when injected to a guest.
83+
84+Level-triggered interrupts will keep the interrupt line to the GIC
85+asserted, typically until the guest programs the device to deassert the
86+line. This means that the interrupt will remain pending on the physical
87+distributor until the guest has reprogrammed the device. Since we
88+always run the VM with interrupts enabled on the CPU, a pending
89+interrupt will exit the guest as soon as we switch into the guest,
90+preventing the guest from ever making progress as the process repeats
91+over and over. Therefore, the active state on the physical distributor
92+must be set when entering the guest, preventing the GIC from forwarding
93+the pending interrupt to the CPU. As soon as the guest deactivates the
94+interrupt, the physical line is sampled by the hardware again and the host
95+takes a new interrupt if and only if the physical line is still asserted.
96+
97+Edge-triggered interrupts do not exhibit the same problem with
98+preventing guest execution that level-triggered interrupts do. One
99+option is to not use HW bit at all, and inject edge-triggered interrupts
100+from a physical device as pure virtual interrupts. But that would
101+potentially slow down handling of the interrupt in the guest, because a
102+physical interrupt occurring in the middle of the guest ISR would
103+preempt the guest for the host to handle the interrupt. Additionally,
104+if you configure the system to handle interrupts on a separate physical
105+core from that running your VCPU, you still have to interrupt the VCPU
106+to queue the pending state onto the LR, even though the guest won't use
107+this information until the guest ISR completes. Therefore, the HW
108+bit should always be set for forwarded edge-triggered interrupts. With
109+the HW bit set, the virtual interrupt is injected and additional
110+physical interrupts occurring before the guest deactivates the interrupt
111+simply mark the state on the physical distributor as Pending+Active. As
112+soon as the guest deactivates the interrupt, the host takes another
113+interrupt if and only if there was a physical interrupt between injecting
114+the forwarded interrupt to the guest and the guest deactivating the
115+interrupt.
116+
117+Consequently, whenever we schedule a VCPU with one or more LRs with the
118+HW bit set, the interrupt must also be active on the physical
119+distributor.
120+
121+
122+Forwarded LPIs
123+--------------
124+LPIs, introduced in GICv3, are always edge-triggered and do not have an
125+active state. They become pending when a device signal them, and as
126+soon as they are acked by the CPU, they are inactive again.
127+
128+It therefore doesn't make sense, and is not supported, to set the HW bit
129+for physical LPIs that are forwarded to a VM as virtual interrupts,
130+typically virtual SPIs.
131+
132+For LPIs, there is no other choice than to preempt the VCPU thread if
133+necessary, and queue the pending state onto the LR.
134+
135+
136+Putting It Together: The Architected Timer
137+------------------------------------------
138+The architected timer is a device that signals interrupts with level
139+triggered semantics. The timer hardware is directly accessed by VCPUs
140+which program the timer to fire at some point in time. Each VCPU on a
141+system programs the timer to fire at different times, and therefore the
142+hardware is multiplexed between multiple VCPUs. This is implemented by
143+context-switching the timer state along with each VCPU thread.
144+
145+However, this means that a scenario like the following is entirely
146+possible, and in fact, typical:
147+
148+1. KVM runs the VCPU
149+2. The guest programs the time to fire in T+100
150+3. The guest is idle and calls WFI (wait-for-interrupts)
151+4. The hardware traps to the host
152+5. KVM stores the timer state to memory and disables the hardware timer
153+6. KVM schedules a soft timer to fire in T+(100 - time since step 2)
154+7. KVM puts the VCPU thread to sleep (on a waitqueue)
155+8. The soft timer fires, waking up the VCPU thread
156+9. KVM reprograms the timer hardware with the VCPU's values
157+10. KVM marks the timer interrupt as active on the physical distributor
158+11. KVM injects a forwarded physical interrupt to the guest
159+12. KVM runs the VCPU
160+
161+Notice that KVM injects a forwarded physical interrupt in step 11 without
162+the corresponding interrupt having actually fired on the host. That is
163+exactly why we mark the timer interrupt as active in step 10, because
164+the active state on the physical distributor is part of the state
165+belonging to the timer hardware, which is context-switched along with
166+the VCPU thread.
167+
168+If the guest does not idle because it is busy, the flow looks like this
169+instead:
170+
171+1. KVM runs the VCPU
172+2. The guest programs the time to fire in T+100
173+4. At T+100 the timer fires and a physical IRQ causes the VM to exit
174+ (note that this initially only traps to EL2 and does not run the host ISR
175+ until KVM has returned to the host).
176+5. With interrupts still disabled on the CPU coming back from the guest, KVM
177+ stores the virtual timer state to memory and disables the virtual hw timer.
178+6. KVM looks at the timer state (in memory) and injects a forwarded physical
179+ interrupt because it concludes the timer has expired.
180+7. KVM marks the timer interrupt as active on the physical distributor
181+7. KVM enables the timer, enables interrupts, and runs the VCPU
182+
183+Notice that again the forwarded physical interrupt is injected to the
184+guest without having actually been handled on the host. In this case it
185+is because the physical interrupt is never actually seen by the host because the
186+timer is disabled upon guest return, and the virtual forwarded interrupt is
187+injected on the KVM guest entry path.
Documentation/virtual/kvm/devices/arm-vgic.txt+10−8
@@ -44,28 +44,29 @@ Groups: · 43 unmodified lines
4444 Attributes:
4545 The attr field of kvm_device_attr encodes two values:
4646 bits: | 63 .... 40 | 39 .. 32 | 31 .... 0 |
47− values: | reserved | cpu id | offset |
47+ values: | reserved | vcpu_index | offset |
4848
4949 All distributor regs are (rw, 32-bit)
5050
5151 The offset is relative to the "Distributor base address" as defined in the
5252 GICv2 specs. Getting or setting such a register has the same effect as
53− reading or writing the register on the actual hardware from the cpu
54− specified with cpu id field. Note that most distributor fields are not
55− banked, but return the same value regardless of the cpu id used to access
56− the register.
53+ reading or writing the register on the actual hardware from the cpu whose
54+ index is specified with the vcpu_index field. Note that most distributor
55+ fields are not banked, but return the same value regardless of the
56+ vcpu_index used to access the register.
5757 Limitations:
5858 - Priorities are not implemented, and registers are RAZ/WI
5959 - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2.
6060 Errors:
61− -ENODEV: Getting or setting this register is not yet supported
61+ -ENXIO: Getting or setting this register is not yet supported
6262 -EBUSY: One or more VCPUs are running
63+ -EINVAL: Invalid vcpu_index supplied
6364
6465 KVM_DEV_ARM_VGIC_GRP_CPU_REGS
6566 Attributes:
6667 The attr field of kvm_device_attr encodes two values:
6768 bits: | 63 .... 40 | 39 .. 32 | 31 .... 0 |
68− values: | reserved | cpu id | offset |
69+ values: | reserved | vcpu_index | offset |
6970
7071 All CPU interface regs are (rw, 32-bit)
7172
@@ -91,8 +92,9 @@ Groups: · 19 unmodified lines
9192 - Priorities are not implemented, and registers are RAZ/WI
9293 - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2.
9394 Errors:
94− -ENODEV: Getting or setting this register is not yet supported
95+ -ENXIO: Getting or setting this register is not yet supported
9596 -EBUSY: One or more VCPUs are running
97+ -EINVAL: Invalid vcpu_index supplied
9698
9799 KVM_DEV_ARM_VGIC_GRP_NR_IRQS
98100 Attributes:
Documentation/virtual/kvm/devices/vm.txt+1−1
@@ -74,7 +74,7 @@ struct kvm_s390_vm_cpu_processor { · 73 unmodified lines
7474
7575 KVM does not enforce or limit the cpu model data in any form. Take the information
7676 retrieved by means of KVM_S390_VM_CPU_MACHINE as hint for reasonable configuration
77−setups. Instruction interceptions triggered by additionally set facilitiy bits that
77+setups. Instruction interceptions triggered by additionally set facility bits that
7878 are not handled by KVM need to by imlemented in the VM driver code.
7979
8080 Parameters: address of buffer to store/set the processor related cpu
Documentation/virtual/kvm/locking.txt+12−0
@@ -166,3 +166,15 @@ Comment: The srcu read lock must be held while accessing memslots (e.g. · 165 unmodified lines
166166 MMIO/PIO address->device structure mapping (kvm->buses).
167167 The srcu index can be stored in kvm_vcpu->srcu_idx per vcpu
168168 if it is needed by multiple functions.
169+
170+Name: blocked_vcpu_on_cpu_lock
171+Type: spinlock_t
172+Arch: x86
173+Protects: blocked_vcpu_on_cpu
174+Comment: This is a per-CPU lock and it is used for VT-d posted-interrupts.
175+ When VT-d posted-interrupts is supported and the VM has assigned
176+ devices, we put the blocked vCPU on the list blocked_vcpu_on_cpu
177+ protected by blocked_vcpu_on_cpu_lock, when VT-d hardware issues
178+ wakeup notification event since external interrupts from the
179+ assigned devices happens, we will find the vCPU on the list to
180+ wakeup.
Documentation/virtual/kvm/ppc-pv.txt+1−1
@@ -110,7 +110,7 @@ Flags are passed to the host in the low 12 bits of the Effective Address. · 109 unmodified lines
110110
111111 The following flags are currently available for a guest to expose:
112112
113− MAGIC_PAGE_FLAG_NOT_MAPPED_NX Guest handles NX bits correclty wrt magic page
113+ MAGIC_PAGE_FLAG_NOT_MAPPED_NX Guest handles NX bits correctly wrt magic page
114114
115115 MSR bits
116116 ========
Documentation/vm/balance+8−6
@@ -1,12 +1,14 @@
11 Started Jan 2000 by Kanoj Sarcar <kanoj@sgi.com>
22
3−Memory balancing is needed for non __GFP_WAIT as well as for non
4−__GFP_IO allocations.
3+Memory balancing is needed for !__GFP_ATOMIC and !__GFP_KSWAPD_RECLAIM as
4+well as for non __GFP_IO allocations.
55
6−There are two reasons to be requesting non __GFP_WAIT allocations:
7−the caller can not sleep (typically intr context), or does not want
8−to incur cost overheads of page stealing and possible swap io for
9−whatever reasons.
6+The first reason why a caller may avoid reclaim is that the caller can not
7+sleep due to holding a spinlock or is in interrupt context. The second may
8+be that the caller is willing to fail the allocation without incurring the
9+overhead of page reclaim. This may happen for opportunistic high-order
10+allocation requests that have order-0 fallback options. In such cases,
11+the caller may also wish to avoid waking kswapd.
1012
1113 __GFP_IO allocation requests are made to prevent file system deadlocks.
1214
Documentation/vm/page_migration+12−15
@@ -92,29 +92,26 @@ Steps: · 91 unmodified lines
9292
9393 2. Insure that writeback is complete.
9494
95−3. Prep the new page that we want to move to. It is locked
96− and set to not being uptodate so that all accesses to the new
97− page immediately lock while the move is in progress.
95+3. Lock the new page that we want to move to. It is locked so that accesses to
96+ this (not yet uptodate) page immediately lock while the move is in progress.
9897
99−4. The new page is prepped with some settings from the old page so that
100− accesses to the new page will discover a page with the correct settings.
101−
102−5. All the page table references to the page are converted
103− to migration entries or dropped (nonlinear vmas).
104− This decrease the mapcount of a page. If the resulting
105− mapcount is not zero then we do not migrate the page.
106− All user space processes that attempt to access the page
107− will now wait on the page lock.
98+4. All the page table references to the page are converted to migration
99+ entries. This decreases the mapcount of a page. If the resulting
100+ mapcount is not zero then we do not migrate the page. All user space
101+ processes that attempt to access the page will now wait on the page lock.
108102
109−6. The radix tree lock is taken. This will cause all processes trying
103+5. The radix tree lock is taken. This will cause all processes trying
110104 to access the page via the mapping to block on the radix tree spinlock.
111105
112−7. The refcount of the page is examined and we back out if references remain
106+6. The refcount of the page is examined and we back out if references remain
113107 otherwise we know that we are the only one referencing this page.
114108
115−8. The radix tree is checked and if it does not contain the pointer to this
109+7. The radix tree is checked and if it does not contain the pointer to this
116110 page then we back out because someone else modified the radix tree.
117111
112+8. The new page is prepped with some settings from the old page so that
113+ accesses to the new page will discover a page with the correct settings.
114+
118115 9. The radix tree is changed to point to the new page.
119116
120117 10. The reference count of the old page is dropped because the radix tree
Documentation/vm/slub.txt+59−0
@@ -280,4 +280,63 @@ of other objects. · 279 unmodified lines
280280
281281 slub_debug=FZ,dentry
282282
283+Extended slabinfo mode and plotting
284+-----------------------------------
285+
286+The slabinfo tool has a special 'extended' ('-X') mode that includes:
287+ - Slabcache Totals
288+ - Slabs sorted by size (up to -N <num> slabs, default 1)
289+ - Slabs sorted by loss (up to -N <num> slabs, default 1)
290+
291+Additionally, in this mode slabinfo does not dynamically scale sizes (G/M/K)
292+and reports everything in bytes (this functionality is also available to
293+other slabinfo modes via '-B' option) which makes reporting more precise and
294+accurate. Moreover, in some sense the `-X' mode also simplifies the analysis
295+of slabs' behaviour, because its output can be plotted using the
296+slabinfo-gnuplot.sh script. So it pushes the analysis from looking through
297+the numbers (tons of numbers) to something easier -- visual analysis.
298+
299+To generate plots:
300+a) collect slabinfo extended records, for example:
301+
302+ while [ 1 ]; do slabinfo -X >> FOO_STATS; sleep 1; done
303+
304+b) pass stats file(-s) to slabinfo-gnuplot.sh script:
305+ slabinfo-gnuplot.sh FOO_STATS [FOO_STATS2 .. FOO_STATSN]
306+
307+The slabinfo-gnuplot.sh script will pre-processes the collected records
308+and generates 3 png files (and 3 pre-processing cache files) per STATS
309+file:
310+ - Slabcache Totals: FOO_STATS-totals.png
311+ - Slabs sorted by size: FOO_STATS-slabs-by-size.png
312+ - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
313+
314+Another use case, when slabinfo-gnuplot can be useful, is when you need
315+to compare slabs' behaviour "prior to" and "after" some code modification.
316+To help you out there, slabinfo-gnuplot.sh script can 'merge' the
317+`Slabcache Totals` sections from different measurements. To visually
318+compare N plots:
319+
320+a) Collect as many STATS1, STATS2, .. STATSN files as you need
321+ while [ 1 ]; do slabinfo -X >> STATS<X>; sleep 1; done
322+
323+b) Pre-process those STATS files
324+ slabinfo-gnuplot.sh STATS1 STATS2 .. STATSN
325+
326+c) Execute slabinfo-gnuplot.sh in '-t' mode, passing all of the
327+generated pre-processed *-totals
328+ slabinfo-gnuplot.sh -t STATS1-totals STATS2-totals .. STATSN-totals
329+
330+This will produce a single plot (png file).
331+
332+Plots, expectedly, can be large so some fluctuations or small spikes
333+can go unnoticed. To deal with that, `slabinfo-gnuplot.sh' has two
334+options to 'zoom-in'/'zoom-out':
335+ a) -s %d,%d overwrites the default image width and heigh
336+ b) -r %d,%d specifies a range of samples to use (for example,
337+ in `slabinfo -X >> FOO_STATS; sleep 1;' case, using
338+ a "-r 40,60" range will plot only samples collected
339+ between 40th and 60th seconds).
340+
283341 Christoph Lameter, May 30, 2007
342+Sergey Senozhatsky, October 23, 2015
Documentation/vm/split_page_table_lock+2−2
@@ -54,8 +54,8 @@ everything required is done by pgtable_page_ctor() and pgtable_page_dtor(), · 53 unmodified lines
5454 which must be called on PTE table allocation / freeing.
5555
5656 Make sure the architecture doesn't use slab allocator for page table
57−allocation: slab uses page->slab_cache and page->first_page for its pages.
58−These fields share storage with page->ptl.
57+allocation: slab uses page->slab_cache for its pages.
58+This field shares storage with page->ptl.
5959
6060 PMD split lock only makes sense if you have more than two page table
6161 levels.
Documentation/vm/transhuge.txt+10−0
@@ -170,6 +170,16 @@ A lower value leads to gain less thp performance. Value of · 169 unmodified lines
170170 max_ptes_none can waste cpu time very little, you can
171171 ignore it.
172172
173+max_ptes_swap specifies how many pages can be brought in from
174+swap when collapsing a group of pages into a transparent huge page.
175+
176+/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap
177+
178+A higher value can cause excessive swap IO and waste
179+memory. A lower value can prevent THPs from being
180+collapsed, resulting fewer pages being collapsed into
181+THPs, and lower memory access performance.
182+
173183 == Boot parameter ==
174184
175185 You can change the sysfs boot time defaults of Transparent Hugepage
Documentation/vm/unevictable-lru.txt+19−101
@@ -531,83 +531,20 @@ map. · 530 unmodified lines
531531
532532 try_to_unmap() is always called, by either vmscan for reclaim or for page
533533 migration, with the argument page locked and isolated from the LRU. Separate
534−functions handle anonymous and mapped file pages, as these types of pages have
535−different reverse map mechanisms.
536−
537− (*) try_to_unmap_anon()
538−
539− To unmap anonymous pages, each VMA in the list anchored in the anon_vma
540− must be visited - at least until a VM_LOCKED VMA is encountered. If the
541− page is being unmapped for migration, VM_LOCKED VMAs do not stop the
542− process because mlocked pages are migratable. However, for reclaim, if
543− the page is mapped into a VM_LOCKED VMA, the scan stops.
544−
545− try_to_unmap_anon() attempts to acquire in read mode the mmap semaphore of
546− the mm_struct to which the VMA belongs. If this is successful, it will
547− mlock the page via mlock_vma_page() - we wouldn't have gotten to
548− try_to_unmap_anon() if the page were already mlocked - and will return
549− SWAP_MLOCK, indicating that the page is unevictable.
550−
551− If the mmap semaphore cannot be acquired, we are not sure whether the page
552− is really unevictable or not. In this case, try_to_unmap_anon() will
553− return SWAP_AGAIN.
554−
555− (*) try_to_unmap_file() - linear mappings
556−
557− Unmapping of a mapped file page works the same as for anonymous mappings,
558− except that the scan visits all VMAs that map the page's index/page offset
559− in the page's mapping's reverse map priority search tree. It also visits
560− each VMA in the page's mapping's non-linear list, if the list is
561− non-empty.
562−
563− As for anonymous pages, on encountering a VM_LOCKED VMA for a mapped file
564− page, try_to_unmap_file() will attempt to acquire the associated
565− mm_struct's mmap semaphore to mlock the page, returning SWAP_MLOCK if this
566− is successful, and SWAP_AGAIN, if not.
567−
568− (*) try_to_unmap_file() - non-linear mappings
569−
570− If a page's mapping contains a non-empty non-linear mapping VMA list, then
571− try_to_un{map|lock}() must also visit each VMA in that list to determine
572− whether the page is mapped in a VM_LOCKED VMA. Again, the scan must visit
573− all VMAs in the non-linear list to ensure that the pages is not/should not
574− be mlocked.
575−
576− If a VM_LOCKED VMA is found in the list, the scan could terminate.
577− However, there is no easy way to determine whether the page is actually
578− mapped in a given VMA - either for unmapping or testing whether the
579− VM_LOCKED VMA actually pins the page.
580−
581− try_to_unmap_file() handles non-linear mappings by scanning a certain
582− number of pages - a "cluster" - in each non-linear VMA associated with the
583− page's mapping, for each file mapped page that vmscan tries to unmap. If
584− this happens to unmap the page we're trying to unmap, try_to_unmap() will
585− notice this on return (page_mapcount(page) will be 0) and return
586− SWAP_SUCCESS. Otherwise, it will return SWAP_AGAIN, causing vmscan to
587− recirculate this page. We take advantage of the cluster scan in
588− try_to_unmap_cluster() as follows:
589−
590− For each non-linear VMA, try_to_unmap_cluster() attempts to acquire the
591− mmap semaphore of the associated mm_struct for read without blocking.
592−
593− If this attempt is successful and the VMA is VM_LOCKED,
594− try_to_unmap_cluster() will retain the mmap semaphore for the scan;
595− otherwise it drops it here.
596−
597− Then, for each page in the cluster, if we're holding the mmap semaphore
598− for a locked VMA, try_to_unmap_cluster() calls mlock_vma_page() to
599− mlock the page. This call is a no-op if the page is already locked,
600− but will mlock any pages in the non-linear mapping that happen to be
601− unlocked.
602−
603− If one of the pages so mlocked is the page passed in to try_to_unmap(),
604− try_to_unmap_cluster() will return SWAP_MLOCK, rather than the default
605− SWAP_AGAIN. This will allow vmscan to cull the page, rather than
606− recirculating it on the inactive list.
607−
608− Again, if try_to_unmap_cluster() cannot acquire the VMA's mmap sem, it
609− returns SWAP_AGAIN, indicating that the page is mapped by a VM_LOCKED
610− VMA, but couldn't be mlocked.
534+functions handle anonymous and mapped file and KSM pages, as these types of
535+pages have different reverse map lookup mechanisms, with different locking.
536+In each case, whether rmap_walk_anon() or rmap_walk_file() or rmap_walk_ksm(),
537+it will call try_to_unmap_one() for every VMA which might contain the page.
538+
539+When trying to reclaim, if try_to_unmap_one() finds the page in a VM_LOCKED
540+VMA, it will then mlock the page via mlock_vma_page() instead of unmapping it,
541+and return SWAP_MLOCK to indicate that the page is unevictable: and the scan
542+stops there.
543+
544+mlock_vma_page() is called while holding the page table's lock (in addition
545+to the page lock, and the rmap lock): to serialize against concurrent mlock or
546+munlock or munmap system calls, mm teardown (munlock_vma_pages_all), reclaim,
547+holepunching, and truncation of file pages and their anonymous COWed pages.
611548
612549
613550 try_to_munlock() REVERSE MAP SCAN
@@ -623,29 +560,15 @@ all PTEs from the page. For this purpose, the unevictable/mlock infrastructure · 9 unmodified lines
623560 introduced a variant of try_to_unmap() called try_to_munlock().
624561
625562 try_to_munlock() calls the same functions as try_to_unmap() for anonymous and
626−mapped file pages with an additional argument specifying unlock versus unmap
563+mapped file and KSM pages with a flag argument specifying unlock versus unmap
627564 processing. Again, these functions walk the respective reverse maps looking
628−for VM_LOCKED VMAs. When such a VMA is found for anonymous pages and file

39 more lines aren’t shown here.

Documentation/w1/masters/omap-hdq+6−0

This diff is large: its 10 lines aren’t shown here.

Documentation/zh_CN/filesystems/sysfs.txt+1−1

This diff is large: its 9 lines aren’t shown here.

MAINTAINERS+355−83

This diff is large: its 1090 lines aren’t shown here.

Makefile+14−8

This diff is large: its 78 lines aren’t shown here.

README+1−1

This diff is large: its 9 lines aren’t shown here.

arch/alpha/include/asm/atomic.h+4−4

This diff is large: its 16 lines aren’t shown here.

arch/alpha/include/asm/word-at-a-time.h+2−0

This diff is large: its 7 lines aren’t shown here.

arch/alpha/include/uapi/asm/mman.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arc/Kconfig+40−0

This diff is large: its 75 lines aren’t shown here.

arch/arc/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arc/boot/dts/Makefile+4−2

This diff is large: its 15 lines aren’t shown here.

arch/arc/boot/dts/axc001.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/boot/dts/axc003.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/boot/dts/axc003_idu.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/boot/dts/nsim_hs.dts+10−2

This diff is large: its 28 lines aren’t shown here.

arch/arc/boot/dts/skeleton.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/boot/dts/vdk_axc003.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/boot/dts/vdk_axc003_idu.dtsi+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/configs/axs101_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/configs/axs103_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/configs/axs103_smp_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arc/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/arc/include/asm/arcregs.h+3−3

This diff is large: its 20 lines aren’t shown here.

arch/arc/include/asm/atomic.h+4−4

This diff is large: its 32 lines aren’t shown here.

arch/arc/include/asm/cache.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arc/include/asm/cacheflush.h+4−4

This diff is large: its 15 lines aren’t shown here.

arch/arc/include/asm/entry-compact.h+6−7

This diff is large: its 20 lines aren’t shown here.

arch/arc/include/asm/highmem.h+61−0

This diff is large: its 62 lines aren’t shown here.

arch/arc/include/asm/hugepage.h+81−0

This diff is large: its 82 lines aren’t shown here.

arch/arc/include/asm/irq.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arc/include/asm/irqflags-compact.h+15−1

This diff is large: its 35 lines aren’t shown here.

arch/arc/include/asm/kmap_types.h+18−0

This diff is large: its 19 lines aren’t shown here.

arch/arc/include/asm/mach_desc.h+2−8

This diff is large: its 28 lines aren’t shown here.

arch/arc/include/asm/mcip.h+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arc/include/asm/mmu.h+7−0

This diff is large: its 28 lines aren’t shown here.

arch/arc/include/asm/page.h+7−2

This diff is large: its 36 lines aren’t shown here.

arch/arc/include/asm/pgalloc.h+6−6

This diff is large: its 46 lines aren’t shown here.

arch/arc/include/asm/pgtable.h+47−41

This diff is large: its 201 lines aren’t shown here.

arch/arc/include/asm/processor.h+6−5

This diff is large: its 26 lines aren’t shown here.

arch/arc/include/asm/setup.h+7−0

This diff is large: its 12 lines aren’t shown here.

arch/arc/include/asm/smp.h+7−0

This diff is large: its 20 lines aren’t shown here.

arch/arc/include/asm/tlbflush.h+5−0

This diff is large: its 25 lines aren’t shown here.

arch/arc/include/uapi/asm/page.h+4−7

This diff is large: its 25 lines aren’t shown here.

arch/arc/kernel/entry-arcv2.S+20−1

This diff is large: its 35 lines aren’t shown here.

arch/arc/kernel/entry-compact.S+48−24

This diff is large: its 140 lines aren’t shown here.

arch/arc/kernel/entry.S+0−17

This diff is large: its 24 lines aren’t shown here.

arch/arc/kernel/head.S+27−22

This diff is large: its 81 lines aren’t shown here.

arch/arc/kernel/intc-compact.c+13−77

This diff is large: its 110 lines aren’t shown here.

arch/arc/kernel/irq.c+12−8

This diff is large: its 37 lines aren’t shown here.

arch/arc/kernel/mcip.c+11−35

This diff is large: its 74 lines aren’t shown here.

arch/arc/kernel/setup.c+2−5

This diff is large: its 22 lines aren’t shown here.

arch/arc/kernel/smp.c+37−29

This diff is large: its 105 lines aren’t shown here.

arch/arc/kernel/time.c+0−3

This diff is large: its 8 lines aren’t shown here.

arch/arc/kernel/vmlinux.lds.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arc/lib/memcpy-archs.S+26−26

This diff is large: its 169 lines aren’t shown here.

arch/arc/mm/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/arc/mm/cache.c+66−25

This diff is large: its 250 lines aren’t shown here.

arch/arc/mm/fault.c+10−3

This diff is large: its 27 lines aren’t shown here.

arch/arc/mm/highmem.c+140−0

This diff is large: its 141 lines aren’t shown here.

arch/arc/mm/init.c+76−28

This diff is large: its 173 lines aren’t shown here.

arch/arc/mm/tlb.c+191−43

This diff is large: its 419 lines aren’t shown here.

arch/arc/mm/tlbex.S+39−16

This diff is large: its 103 lines aren’t shown here.

arch/arc/plat-axs10x/axs10x.c+0−8

This diff is large: its 22 lines aren’t shown here.

arch/arc/plat-sim/platform.c+0−5

This diff is large: its 17 lines aren’t shown here.

arch/arm/Kconfig+8−28

This diff is large: its 102 lines aren’t shown here.

arch/arm/Kconfig.debug+17−27

This diff is large: its 75 lines aren’t shown here.

arch/arm/boot/dts/Makefile+52−10

This diff is large: its 224 lines aren’t shown here.

arch/arm/boot/dts/am335x-base0033.dts+24−24

This diff is large: its 64 lines aren’t shown here.

arch/arm/boot/dts/am335x-bone-common.dtsi+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/am335x-bonegreen.dts+53−0

This diff is large: its 54 lines aren’t shown here.

arch/arm/boot/dts/am335x-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/am335x-evmsk.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/am335x-igep0033.dtsi+20−20

This diff is large: its 62 lines aren’t shown here.

arch/arm/boot/dts/am335x-phycore-som.dtsi+19−17

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/am335x-wega.dtsi+12−1

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/am4372.dtsi+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/am437x-gp-evm.dts+28−3

This diff is large: its 74 lines aren’t shown here.

arch/arm/boot/dts/am437x-idk-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/am437x-sk-evm.dts+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/am43x-epos-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/am57xx-beagle-x15.dts+118−2

This diff is large: its 170 lines aren’t shown here.

arch/arm/boot/dts/armada-370-db.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/armada-370-dlink-dns327l.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/armada-370-mirabox.dts+6−1

This diff is large: its 21 lines aren’t shown here.

arch/arm/boot/dts/armada-370-netgear-rn102.dts+8−1

This diff is large: its 23 lines aren’t shown here.

arch/arm/boot/dts/armada-370-netgear-rn104.dts+8−1

This diff is large: its 23 lines aren’t shown here.

arch/arm/boot/dts/armada-370-rd.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-nas-2bay.dts+36−0

This diff is large: its 37 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-nas-4bay.dts+133−0

This diff is large: its 134 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-nas-xbay.dtsi+231−0

This diff is large: its 232 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-personal-cloud-2bay.dts+51−0

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-personal-cloud.dts+37−0

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/armada-370-seagate-personal-cloud.dtsi+178−0

This diff is large: its 179 lines aren’t shown here.

arch/arm/boot/dts/armada-370-synology-ds213j.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/armada-370.dtsi+37−0

This diff is large: its 51 lines aren’t shown here.

arch/arm/boot/dts/armada-375-db.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-375.dtsi+33−0

This diff is large: its 46 lines aren’t shown here.

arch/arm/boot/dts/armada-385-db-ap.dts+4−2

This diff is large: its 20 lines aren’t shown here.

arch/arm/boot/dts/armada-385-linksys.dtsi+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-388-db.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-388-gp.dts+17−2

This diff is large: its 34 lines aren’t shown here.

arch/arm/boot/dts/armada-388-rd.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-38x.dtsi+33−0

This diff is large: its 47 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-axpwifiap.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-db.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-gp.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-linksys-mamba.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-matrix.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-netgear-rn2120.dts+49−41

This diff is large: its 119 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp-synology-ds414.dts+3−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/armada-xp.dtsi+35−0

This diff is large: its 56 lines aren’t shown here.

arch/arm/boot/dts/at91-sama5d2_xplained.dts+118−0

This diff is large: its 165 lines aren’t shown here.

arch/arm/boot/dts/at91-sama5d3_xplained.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91-sama5d4_xplained.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91-sama5d4ek.dts+27−0

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/at91rm9200.dtsi+4−4

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/at91sam9260.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9261.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9263.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9g45.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9m10g45ek.dts+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9n12.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9n12ek.dts+2−6

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/at91sam9rl.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/at91sam9x5.dtsi+3−2

This diff is large: its 26 lines aren’t shown here.

arch/arm/boot/dts/at91sam9x5ek.dtsi+8−0

This diff is large: its 22 lines aren’t shown here.

arch/arm/boot/dts/axp209.dtsi+5−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/axp22x.dtsi+143−0

This diff is large: its 144 lines aren’t shown here.

arch/arm/boot/dts/bcm-cygnus.dtsi+175−159

This diff is large: its 380 lines aren’t shown here.

arch/arm/boot/dts/bcm-nsp.dtsi+119−0

This diff is large: its 120 lines aren’t shown here.

arch/arm/boot/dts/bcm2835-rpi-a-plus.dts+30−0

This diff is large: its 31 lines aren’t shown here.

arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts+23−0

This diff is large: its 24 lines aren’t shown here.

arch/arm/boot/dts/bcm2835-rpi-b.dts+1−7

This diff is large: its 13 lines aren’t shown here.

arch/arm/boot/dts/bcm2835-rpi.dtsi+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/bcm2835.dtsi+39−25

This diff is large: its 131 lines aren’t shown here.

arch/arm/boot/dts/bcm4708-netgear-r6250.dts+11−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/bcm4709-netgear-r7000.dts+106−0

This diff is large: its 107 lines aren’t shown here.

arch/arm/boot/dts/bcm7445.dtsi+84−0

This diff is large: its 98 lines aren’t shown here.

arch/arm/boot/dts/bcm911360_entphn.dts+20−8

This diff is large: its 44 lines aren’t shown here.

arch/arm/boot/dts/bcm911360k.dts+4−5

This diff is large: its 16 lines aren’t shown here.

arch/arm/boot/dts/bcm958300k.dts+22−22

This diff is large: its 65 lines aren’t shown here.

arch/arm/boot/dts/bcm958305k.dts+36−4

This diff is large: its 55 lines aren’t shown here.

arch/arm/boot/dts/bcm958625k.dts+57−0

This diff is large: its 58 lines aren’t shown here.

arch/arm/boot/dts/bcm9hmidc.dtsi+42−0

This diff is large: its 43 lines aren’t shown here.

arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/berlin2.dtsi+23−0

This diff is large: its 44 lines aren’t shown here.

arch/arm/boot/dts/berlin2cd-google-chromecast.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/berlin2cd.dtsi+20−0

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/berlin2q-marvell-dmp.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/berlin2q.dtsi+26−3

This diff is large: its 71 lines aren’t shown here.

arch/arm/boot/dts/cx92755.dtsi+7−0

This diff is large: its 14 lines aren’t shown here.

arch/arm/boot/dts/cx92755_equinox.dts+9−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/dove.dtsi+13−4

This diff is large: its 33 lines aren’t shown here.

arch/arm/boot/dts/dra7-evm.dts+218−4

This diff is large: its 291 lines aren’t shown here.

arch/arm/boot/dts/dra7.dtsi+61−0

This diff is large: its 89 lines aren’t shown here.

arch/arm/boot/dts/dra72-evm.dts+156−6

This diff is large: its 230 lines aren’t shown here.

arch/arm/boot/dts/dra72x.dtsi+21−0

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/dra74x.dtsi+51−0

This diff is large: its 69 lines aren’t shown here.

arch/arm/boot/dts/efm32gg-dk3750.dts+4−4

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/efm32gg.dtsi+16−16

This diff is large: its 141 lines aren’t shown here.

arch/arm/boot/dts/emev2-kzm9d.dts+4−4

This diff is large: its 33 lines aren’t shown here.

arch/arm/boot/dts/exynos3250-monk.dts+5−4

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/exynos3250-rinato.dts+6−5

This diff is large: its 45 lines aren’t shown here.

arch/arm/boot/dts/exynos3250.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/exynos4.dtsi+8−0

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/exynos4210-origen.dts+8−7

This diff is large: its 67 lines aren’t shown here.

arch/arm/boot/dts/exynos4210-smdkv310.dts+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/exynos4210-trats.dts+16−15

This diff is large: its 134 lines aren’t shown here.

arch/arm/boot/dts/exynos4210-universal_c210.dts+23−21

This diff is large: its 176 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-odroid-common.dtsi+10−17

This diff is large: its 102 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-odroidu3.dts+44−1

This diff is large: its 56 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-odroidx.dts+4−4

This diff is large: its 34 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-origen.dts+8−7

This diff is large: its 37 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-tiny4412.dts+5−4

This diff is large: its 39 lines aren’t shown here.

arch/arm/boot/dts/exynos4412-trats2.dts+53−87

This diff is large: its 470 lines aren’t shown here.

arch/arm/boot/dts/exynos4412.dtsi+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/exynos5250-arndale.dts+4−4

This diff is large: its 22 lines aren’t shown here.

arch/arm/boot/dts/exynos5250-smdk5250.dts+9−8

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/exynos5250-snow-common.dtsi+684−0

This diff is large: its 685 lines aren’t shown here.

arch/arm/boot/dts/exynos5250-snow-rev5.dts+47−0

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/exynos5250-snow.dts+4−667

This diff is large: its 703 lines aren’t shown here.

arch/arm/boot/dts/exynos5250.dtsi+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/exynos5420-arndale-octa.dts+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/exynos5420-peach-pit.dts+10−4

This diff is large: its 56 lines aren’t shown here.

arch/arm/boot/dts/exynos5420-smdk5420.dts+8−6

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/exynos5420.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/exynos5422-odroidxu3-audio.dtsi+61−0

This diff is large: its 62 lines aren’t shown here.

arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi+4−99

This diff is large: its 152 lines aren’t shown here.

arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts+51−0

This diff is large: its 60 lines aren’t shown here.

arch/arm/boot/dts/exynos5422-odroidxu3.dts+51−0

This diff is large: its 66 lines aren’t shown here.

arch/arm/boot/dts/exynos5422-odroidxu4.dts+48−0

This diff is large: its 49 lines aren’t shown here.

arch/arm/boot/dts/exynos5440-ssdk5440.dts+3−2

This diff is large: its 23 lines aren’t shown here.

arch/arm/boot/dts/exynos5800-peach-pi.dts+10−4

This diff is large: its 56 lines aren’t shown here.

arch/arm/boot/dts/hi3620-hi4511.dts+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/hisi-x5hd2-dkb.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx23.dtsi+4−2

This diff is large: its 14 lines aren’t shown here.

arch/arm/boot/dts/imx27.dtsi+12−4

This diff is large: its 44 lines aren’t shown here.

arch/arm/boot/dts/imx28-evk.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx28-m28evk.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx28-tx28.dts+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/imx28.dtsi+4−2

This diff is large: its 14 lines aren’t shown here.

arch/arm/boot/dts/imx31.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx35.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx50-evk.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx53-qsrb.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx53-smd.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx53-tx53-x03x.dts+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/imx53.dtsi+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/imx6dl-nit6xlite.dts+49−0

This diff is large: its 50 lines aren’t shown here.

arch/arm/boot/dts/imx6dl-nitrogen6x.dts+37−7

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/imx6dl-rex-basic.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6dl-sabrelite.dts+35−5

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6q-gw5400-a.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6q-nitrogen6_max.dts+53−0

This diff is large: its 54 lines aren’t shown here.

arch/arm/boot/dts/imx6q-nitrogen6x.dts+37−7

This diff is large: its 59 lines aren’t shown here.

arch/arm/boot/dts/imx6q-rex-pro.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6q-sabrelite.dts+35−5

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-aristainetos.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi+630−0

This diff is large: its 631 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi+873−0

This diff is large: its 874 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi+182−7

This diff is large: its 270 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi+3−3

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-rex.dtsi+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-sabreauto.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-sabrelite.dtsi+111−7

This diff is large: its 161 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-sabresd.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl-tx6.dtsi+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/imx6qdl.dtsi+6−6

This diff is large: its 23 lines aren’t shown here.

arch/arm/boot/dts/imx6sl-evk.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6sl.dtsi+20−1

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/imx6sx-sdb-reva.dts+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/imx6sx-sdb.dts+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/imx6sx-sdb.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6sx.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/imx6ul-14x14-evk.dts+22−0

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/imx6ul.dtsi+29−0

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/imx7d-pinfunc.h+119−3

This diff is large: its 150 lines aren’t shown here.

arch/arm/boot/dts/imx7d-sdb.dts+99−1

This diff is large: its 133 lines aren’t shown here.

arch/arm/boot/dts/imx7d.dtsi+167−2

This diff is large: its 206 lines aren’t shown here.

arch/arm/boot/dts/k2e-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/k2e-netcp.dtsi+23−0

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/k2e.dtsi+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/k2hk-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/k2hk-netcp.dtsi+24−0

This diff is large: its 46 lines aren’t shown here.

arch/arm/boot/dts/k2hk.dtsi+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/k2l-evm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/k2l-netcp.dtsi+23−0

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/k2l.dtsi+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/keystone.dtsi+4−3

This diff is large: its 35 lines aren’t shown here.

arch/arm/boot/dts/kirkwood-net5big.dts+60−0

This diff is large: its 67 lines aren’t shown here.

arch/arm/boot/dts/kirkwood-netxbig.dtsi+80−0

This diff is large: its 94 lines aren’t shown here.

arch/arm/boot/dts/kirkwood.dtsi+19−10

This diff is large: its 50 lines aren’t shown here.

arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/lpc18xx.dtsi+134−0

This diff is large: its 292 lines aren’t shown here.

arch/arm/boot/dts/lpc4350-hitex-eval.dts+175−0

This diff is large: its 210 lines aren’t shown here.

arch/arm/boot/dts/lpc4357-ea4357-devkit.dts+95−0

This diff is large: its 123 lines aren’t shown here.

arch/arm/boot/dts/ls1021a-twr.dts+13−0

This diff is large: its 20 lines aren’t shown here.

arch/arm/boot/dts/ls1021a.dtsi+44−0

This diff is large: its 86 lines aren’t shown here.

arch/arm/boot/dts/meson.dtsi+12−11

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/meson8b-mxq.dts+67−0

This diff is large: its 68 lines aren’t shown here.

arch/arm/boot/dts/meson8b-odroidc1.dts+67−0

This diff is large: its 68 lines aren’t shown here.

arch/arm/boot/dts/meson8b.dtsi+186−0

This diff is large: its 187 lines aren’t shown here.

arch/arm/boot/dts/mt8127.dtsi+27−0

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/mt8135-evbp1.dts+0−23

This diff is large: its 175 lines aren’t shown here.

arch/arm/boot/dts/mt8135.dtsi+27−0

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/nspire.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap2420-n8x0-common.dtsi+3−3

This diff is large: its 13 lines aren’t shown here.

arch/arm/boot/dts/omap3-beagle-xm.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-beagle.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-cm-t3x.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-devkit8000-lcd-common.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-evm-37xx.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-evm-common.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/omap3-gta04.dtsi+5−5

This diff is large: its 24 lines aren’t shown here.

arch/arm/boot/dts/omap3-gta04a5.dts+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep.dtsi+35−35

This diff is large: its 138 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0020-common.dtsi+30−30

This diff is large: its 79 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0020-rev-f.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0020.dts+1−10

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0030-common.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0030-rev-g.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-igep0030.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-ldp.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-lilly-a83x.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/omap3-lilly-dbb056.dts+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/omap3-n950-n9.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-overo-base.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap3-pandora-common.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/omap3-tao3530.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/omap3-zoom3.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap4-panda-common.dtsi+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/omap4-sdp.dts+3−3

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/omap4-var-som-om44-wlan.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap4-var-som-om44.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap4460.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap5-board-common.dtsi+655−0

This diff is large: its 656 lines aren’t shown here.

arch/arm/boot/dts/omap5-cm-t54.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/omap5-igep0050.dts+54−0

This diff is large: its 55 lines aren’t shown here.

arch/arm/boot/dts/omap5-uevm.dts+14−604

This diff is large: its 641 lines aren’t shown here.

arch/arm/boot/dts/orion5x.dtsi+15−7

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts+42−6

This diff is large: its 98 lines aren’t shown here.

arch/arm/boot/dts/qcom-apq8064-ifc6410.dts+53−7

This diff is large: its 117 lines aren’t shown here.

arch/arm/boot/dts/qcom-apq8064.dtsi+42−1

This diff is large: its 76 lines aren’t shown here.

arch/arm/boot/dts/qcom-apq8084.dtsi+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/qcom-msm8974.dtsi+88−7

This diff is large: its 143 lines aren’t shown here.

arch/arm/boot/dts/qcom-pm8941.dtsi+22−2

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/r8a7778-bockw-reference.dts+0−139

This diff is large: its 140 lines aren’t shown here.

arch/arm/boot/dts/r8a7778.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/r8a7779-marzen.dts+3−3

This diff is large: its 16 lines aren’t shown here.

arch/arm/boot/dts/r8a7790-lager.dts+15−1

This diff is large: its 44 lines aren’t shown here.

arch/arm/boot/dts/r8a7790.dtsi+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/r8a7791-koelsch.dts+8−1

This diff is large: its 23 lines aren’t shown here.

arch/arm/boot/dts/r8a7791-porter.dts+282−0

This diff is large: its 283 lines aren’t shown here.

arch/arm/boot/dts/r8a7791.dtsi+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/r8a7794-silk.dts+114−0

This diff is large: its 136 lines aren’t shown here.

arch/arm/boot/dts/r8a7794.dtsi+318−8

This diff is large: its 363 lines aren’t shown here.

arch/arm/boot/dts/r8a77xx-aa121td01-panel.dtsi+41−0

This diff is large: its 42 lines aren’t shown here.

arch/arm/boot/dts/rk3066a-bqcurie2.dts+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/rk3066a-marsboard.dts+8−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/boot/dts/rk3066a-rayeager.dts+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/rk3188-radxarock.dts+21−0

This diff is large: its 42 lines aren’t shown here.

arch/arm/boot/dts/rk3188.dtsi+20−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/boot/dts/rk3288-firefly.dtsi+52−3

This diff is large: its 111 lines aren’t shown here.

arch/arm/boot/dts/rk3288-popmetal.dts+81−4

This diff is large: its 153 lines aren’t shown here.

arch/arm/boot/dts/rk3288-rock2-som.dtsi+277−0

This diff is large: its 278 lines aren’t shown here.

arch/arm/boot/dts/rk3288-rock2-square.dts+167−0

This diff is large: its 168 lines aren’t shown here.

arch/arm/boot/dts/rk3288-veyron-jaq.dts+176−0

This diff is large: its 177 lines aren’t shown here.

arch/arm/boot/dts/rk3288-veyron-sdmmc.dtsi+6−1

This diff is large: its 22 lines aren’t shown here.

arch/arm/boot/dts/rk3288-veyron.dtsi+6−12

This diff is large: its 40 lines aren’t shown here.

arch/arm/boot/dts/rk3288.dtsi+141−13

This diff is large: its 280 lines aren’t shown here.

arch/arm/boot/dts/s3c2416.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/s5pv210-aquila.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/s5pv210-goni.dts+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/sama5d2-pinfunc.h+880−0

This diff is large: its 881 lines aren’t shown here.

arch/arm/boot/dts/sama5d2.dtsi+165−3

This diff is large: its 231 lines aren’t shown here.

arch/arm/boot/dts/sama5d3.dtsi+3−2

This diff is large: its 26 lines aren’t shown here.

arch/arm/boot/dts/sama5d3_mci2.dtsi+3−3

This diff is large: its 13 lines aren’t shown here.

arch/arm/boot/dts/sama5d3xmb.dtsi+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/sama5d4.dtsi+39−10

This diff is large: its 113 lines aren’t shown here.

arch/arm/boot/dts/sh73a0-kzm9g.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/socfpga.dtsi+71−64

This diff is large: its 192 lines aren’t shown here.

arch/arm/boot/dts/socfpga_arria10.dtsi+8−0

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/socfpga_arria10_socdk.dtsi+27−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/boot/dts/ste-hrefv60plus.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/ste-snowball.dts+5−5

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/stih407-b2120.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/stih407-family.dtsi+86−2

This diff is large: its 170 lines aren’t shown here.

arch/arm/boot/dts/stih407-pinctrl.dtsi+379−11

This diff is large: its 490 lines aren’t shown here.

arch/arm/boot/dts/stih407.dtsi+0−13

This diff is large: its 20 lines aren’t shown here.

arch/arm/boot/dts/stih410-b2120.dts+25−0

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/stih410.dtsi+11−12

This diff is large: its 66 lines aren’t shown here.

arch/arm/boot/dts/stih418-b2199.dts+8−0

This diff is large: its 21 lines aren’t shown here.

arch/arm/boot/dts/stih418-clock.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/stih418.dtsi+6−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/boot/dts/stihxxx-b2120.dtsi+14−0

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/stm32f429.dtsi+7−0

This diff is large: its 14 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-a1000.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-chuwi-v7-cw0825.dts+12−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-cubieboard.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-gemei-g9.dts+4−7

This diff is large: its 32 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-inet1.dts+226−0

This diff is large: its 227 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-inet97fv2.dts+107−10

This diff is large: its 161 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-inet9f-rev03.dts+227−0

This diff is large: its 228 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-jesurun-q5.dts+15−0

This diff is large: its 37 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-marsboard.dts+23−0

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts+12−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-pcduino.dts+48−10

This diff is large: its 99 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-pcduino2.dts+78−0

This diff is large: its 79 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10-pov-protab2-ips9.dts+199−0

This diff is large: its 200 lines aren’t shown here.

arch/arm/boot/dts/sun4i-a10.dtsi+31−0

This diff is large: its 59 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a10s-auxtek-t003.dts+159−0

This diff is large: its 160 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a10s-wobo-i5.dts+224−0

This diff is large: its 225 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a10s.dtsi+28−7

This diff is large: its 63 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a13-inet-98v-rev2.dts+227−0

This diff is large: its 228 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a13-q8-tablet.dts+60−0

This diff is large: its 61 lines aren’t shown here.

arch/arm/boot/dts/sun5i-a13.dtsi+10−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/boot/dts/sun5i-q8-common.dtsi+180−0

This diff is large: its 181 lines aren’t shown here.

arch/arm/boot/dts/sun5i-r8-chip.dts+218−0

This diff is large: its 219 lines aren’t shown here.

arch/arm/boot/dts/sun5i-r8.dtsi+59−0

This diff is large: its 60 lines aren’t shown here.

arch/arm/boot/dts/sun5i.dtsi+52−0

This diff is large: its 87 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31-colombus.dts+36−0

This diff is large: its 63 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31-hummingbird.dts+72−60

This diff is large: its 187 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31.dtsi+28−3

This diff is large: its 66 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31s-primo81.dts+255−0

This diff is large: its 256 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31s-sina31s-core.dtsi+140−0

This diff is large: its 141 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31s-sina31s.dts+153−0

This diff is large: its 154 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts+194−0

This diff is large: its 195 lines aren’t shown here.

arch/arm/boot/dts/sun6i-a31s-yones-toptech-bs1078-v2.dts+134−0

This diff is large: its 135 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-bananapi.dts+70−4

This diff is large: its 114 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-cubieboard2.dts+23−0

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-cubietruck.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-olimex-som-evb.dts+198−0

This diff is large: its 199 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts+12−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts+47−0

This diff is large: its 83 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts+29−0

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-orangepi.dts+29−0

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts+54−11

This diff is large: its 114 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-pcduino3.dts+50−4

This diff is large: its 103 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts+32−1

This diff is large: its 62 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20-wits-pro-a20-dkt.dts+226−0

This diff is large: its 227 lines aren’t shown here.

arch/arm/boot/dts/sun7i-a20.dtsi+40−1

This diff is large: its 83 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-a33.dtsi+45−25

This diff is large: its 115 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-gt90h-v4.dts+145−0

This diff is large: its 146 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts+0−54

This diff is large: its 55 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-ippo-q8h-v1.2.dts+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts+0−136

This diff is large: its 137 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-q8-tablet.dts+65−0

This diff is large: its 66 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23.dtsi+25−0

This diff is large: its 32 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-et-q8-v1.6.dts+0−88

This diff is large: its 89 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-et-q8-v1.6.dts+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-ippo-q8h-v1.2.dts+0−133

This diff is large: its 134 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-ippo-q8h-v1.2.dts+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-q8-tablet.dts+65−0

This diff is large: its 66 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a33.dtsi+45−0

This diff is large: its 59 lines aren’t shown here.

arch/arm/boot/dts/sun8i-q8-common.dtsi+101−0

This diff is large: its 102 lines aren’t shown here.

arch/arm/boot/dts/sun9i-a80.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/sunxi-q8-common.dtsi+83−0

This diff is large: its 84 lines aren’t shown here.

arch/arm/boot/dts/tegra114.dtsi+2−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/tegra124-nyan.dtsi+14−1

This diff is large: its 36 lines aren’t shown here.

arch/arm/boot/dts/tegra124.dtsi+9−13

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/tegra20.dtsi+4−2

This diff is large: its 21 lines aren’t shown here.

arch/arm/boot/dts/tegra30-apalis-eval.dts+9−4

This diff is large: its 42 lines aren’t shown here.

arch/arm/boot/dts/tegra30-apalis.dtsi+131−83

This diff is large: its 396 lines aren’t shown here.

arch/arm/boot/dts/tegra30-colibri-eval-v3.dts+5−4

This diff is large: its 31 lines aren’t shown here.

arch/arm/boot/dts/tegra30-colibri.dtsi+142−54

This diff is large: its 317 lines aren’t shown here.

arch/arm/boot/dts/tegra30.dtsi+7−5

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts+3−5

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-ld4.dtsi+16−4

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-ld6b-ref.dts+4−6

This diff is large: its 30 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-pro4-ref.dts+3−5

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-pro4.dtsi+17−4

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-pro5.dtsi+30−4

This diff is large: its 61 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-sld3-ref.dts+3−5

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-sld3.dtsi+17−4

This diff is large: its 48 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-sld8-ref.dts+3−5

This diff is large: its 25 lines aren’t shown here.

arch/arm/boot/dts/uniphier-ph1-sld8.dtsi+16−4

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/uniphier-proxstream2-gentil.dts+78−0

This diff is large: its 79 lines aren’t shown here.

arch/arm/boot/dts/uniphier-proxstream2-vodka.dts+78−0

This diff is large: its 79 lines aren’t shown here.

arch/arm/boot/dts/uniphier-proxstream2.dtsi+19−4

This diff is large: its 62 lines aren’t shown here.

arch/arm/boot/dts/vf-colibri.dtsi+39−0

This diff is large: its 53 lines aren’t shown here.

arch/arm/boot/dts/vf500-colibri-eval-v3.dts+5−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/vf500-colibri.dtsi+47−0

This diff is large: its 52 lines aren’t shown here.

arch/arm/boot/dts/vf610-twr.dts+47−0

This diff is large: its 61 lines aren’t shown here.

arch/arm/boot/dts/vfxxx.dtsi+11−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/wm8750.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/zynq-7000.dtsi+5−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/common/Kconfig+0−3

This diff is large: its 7 lines aren’t shown here.

arch/arm/common/Makefile+0−1

This diff is large: its 7 lines aren’t shown here.

arch/arm/common/edma.c+0−1876

This diff is large: its 1877 lines aren’t shown here.

arch/arm/configs/at91_dt_defconfig+0−15

This diff is large: its 68 lines aren’t shown here.

arch/arm/configs/bockw_defconfig+0−133

This diff is large: its 134 lines aren’t shown here.

arch/arm/configs/exynos_defconfig+16−4

This diff is large: its 62 lines aren’t shown here.

arch/arm/configs/hisi_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/configs/imx_v6_v7_defconfig+1−1

This diff is large: its 16 lines aren’t shown here.

arch/arm/configs/keystone_defconfig+27−27

This diff is large: its 145 lines aren’t shown here.

arch/arm/configs/lpc18xx_defconfig+22−5

This diff is large: its 85 lines aren’t shown here.

arch/arm/configs/multi_v7_defconfig+47−1

This diff is large: its 266 lines aren’t shown here.

arch/arm/configs/mvebu_v7_defconfig+8−1

This diff is large: its 35 lines aren’t shown here.

arch/arm/configs/omap2plus_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/configs/qcom_defconfig+5−3

This diff is large: its 29 lines aren’t shown here.

arch/arm/configs/sama5_defconfig+6−10

This diff is large: its 83 lines aren’t shown here.

arch/arm/configs/shmobile_defconfig+3−1

This diff is large: its 19 lines aren’t shown here.

arch/arm/configs/socfpga_defconfig+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/configs/sunxi_defconfig+4−0

This diff is large: its 25 lines aren’t shown here.

arch/arm/configs/tegra_defconfig+7−3

This diff is large: its 60 lines aren’t shown here.

arch/arm/include/asm/Kbuild+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/arch_gicv3.h+188−0

This diff is large: its 189 lines aren’t shown here.

arch/arm/include/asm/atomic.h+6−6

This diff is large: its 36 lines aren’t shown here.

arch/arm/include/asm/cmpxchg.h+12−0

This diff is large: its 26 lines aren’t shown here.

arch/arm/include/asm/hardware/cache-uniphier.h+46−0

This diff is large: its 47 lines aren’t shown here.

arch/arm/include/asm/highmem.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/irqflags.h+10−0

This diff is large: its 24 lines aren’t shown here.

arch/arm/include/asm/kvm_arm.h+20−0

This diff is large: its 25 lines aren’t shown here.

arch/arm/include/asm/kvm_host.h+4−1

This diff is large: its 12 lines aren’t shown here.

arch/arm/include/asm/mach/arch.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/asm/mach/pci.h+0−6

This diff is large: its 13 lines aren’t shown here.

arch/arm/include/asm/memory.h+2−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/include/asm/pgtable.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/asm/smp.h+2−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/include/asm/unistd.h+0−7

This diff is large: its 14 lines aren’t shown here.

arch/arm/include/asm/xen/hypervisor.h+10−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/include/asm/xen/page-coherent.h+17−9

This diff is large: its 40 lines aren’t shown here.

arch/arm/include/asm/xen/page.h+15−7

This diff is large: its 50 lines aren’t shown here.

arch/arm/include/debug/at91.S+4−14

This diff is large: its 37 lines aren’t shown here.

arch/arm/kernel/bios32.c+8−4

This diff is large: its 40 lines aren’t shown here.

arch/arm/kernel/devtree.c+9−3

This diff is large: its 42 lines aren’t shown here.

arch/arm/kernel/entry-armv.S+3−30

This diff is large: its 54 lines aren’t shown here.

arch/arm/kernel/hw_breakpoint.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/kernel/irq.c+3−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/kernel/kgdb.c+12−19

This diff is large: its 45 lines aren’t shown here.

arch/arm/kernel/psci_smp.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/kernel/smp.c+11−1

This diff is large: its 33 lines aren’t shown here.

arch/arm/kernel/smp_twd.c+5−6

This diff is large: its 46 lines aren’t shown here.

arch/arm/kernel/time.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/kernel/traps.c+0−52

This diff is large: its 59 lines aren’t shown here.

arch/arm/kvm/Kconfig+3−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/kvm/arm.c+61−17

This diff is large: its 164 lines aren’t shown here.

arch/arm/kvm/psci.c+5−5

This diff is large: its 45 lines aren’t shown here.

arch/arm/kvm/trace.h+7−3

This diff is large: its 29 lines aren’t shown here.

arch/arm/lib/clear_user.S+4−0

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-at91/Kconfig+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-at91/pm_suspend.S+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-bcm/Kconfig+16−1

This diff is large: its 38 lines aren’t shown here.

arch/arm/mach-bcm/Makefile+4−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-bcm/bcm_nsp.c+25−0

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-bcm/brcmstb.c+9−0

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-berlin/berlin.c+6−0

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-berlin/platsmp.c+35−3

This diff is large: its 65 lines aren’t shown here.

arch/arm/mach-cns3xxx/pcie.c+30−41

This diff is large: its 98 lines aren’t shown here.

arch/arm/mach-davinci/board-dm644x-evm.c+1−3

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-davinci/clock.c+11−5

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-davinci/devices-da8xx.c+45−77

This diff is large: its 196 lines aren’t shown here.

arch/arm/mach-davinci/dm355.c+21−19

This diff is large: its 97 lines aren’t shown here.

arch/arm/mach-davinci/dm365.c+10−15

This diff is large: its 81 lines aren’t shown here.

arch/arm/mach-davinci/dm644x.c+21−19

This diff is large: its 96 lines aren’t shown here.

arch/arm/mach-davinci/dm646x.c+22−22

This diff is large: its 107 lines aren’t shown here.

arch/arm/mach-digicolor/Kconfig+3−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-exynos/mcpm-exynos.c+26−1

This diff is large: its 41 lines aren’t shown here.

arch/arm/mach-exynos/pm_domains.c+3−5

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-exynos/regs-pmu.h+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-exynos/suspend.c+31−27

This diff is large: its 101 lines aren’t shown here.

arch/arm/mach-gemini/board-nas4220b.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-gemini/board-wbd111.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-gemini/board-wbd222.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-imx/common.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-imx/gpc.c+31−32

This diff is large: its 108 lines aren’t shown here.

arch/arm/mach-imx/mach-imx6q.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-imx/mach-imx6ul.c+9−0

This diff is large: its 29 lines aren’t shown here.

arch/arm/mach-imx/mach-imx7d.c+74−0

This diff is large: its 94 lines aren’t shown here.

arch/arm/mach-imx/pm-imx6.c+40−6

This diff is large: its 122 lines aren’t shown here.

arch/arm/mach-imx/suspend-imx6.S+3−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-keystone/keystone.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-mediatek/Makefile+3−0

This diff is large: its 5 lines aren’t shown here.

arch/arm/mach-mediatek/mediatek.c+27−0

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-mediatek/platsmp.c+141−0

This diff is large: its 142 lines aren’t shown here.

arch/arm/mach-meson/Kconfig+5−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-meson/meson.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-mvebu/Kconfig+0−7

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-mvebu/Makefile+0−1

This diff is large: its 5 lines aren’t shown here.

arch/arm/mach-mvebu/board-v7.c+0−35

This diff is large: its 63 lines aren’t shown here.

arch/arm/mach-mvebu/board.h+0−21

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-mvebu/coherency.c+60−0

This diff is large: its 98 lines aren’t shown here.

arch/arm/mach-mvebu/kirkwood.c+0−4

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-mvebu/netxbig.c+0−191

This diff is large: its 192 lines aren’t shown here.

arch/arm/mach-mvebu/pmsu.c+28−5

This diff is large: its 97 lines aren’t shown here.

arch/arm/mach-omap1/Kconfig+0−7

This diff is large: its 14 lines aren’t shown here.

arch/arm/mach-omap1/Makefile+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap1/board-voiceblue.c+0−296

This diff is large: its 297 lines aren’t shown here.

arch/arm/mach-omap1/include/mach/board-voiceblue.h+0−19

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/Kconfig+3−1

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-omap2/Makefile+0−3

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/board-generic.c+16−6

This diff is large: its 90 lines aren’t shown here.

arch/arm/mach-omap2/board-ldp.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-rx51.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/clkt34xx_dpll3m2.c+0−122

This diff is large: its 123 lines aren’t shown here.

arch/arm/mach-omap2/common.h+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-omap2/devices.c+0−53

This diff is large: its 67 lines aren’t shown here.

arch/arm/mach-omap2/id.c+15−15

This diff is large: its 89 lines aren’t shown here.

arch/arm/mach-omap2/omap-hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/omap-wakeupgen.c+32−33

This diff is large: its 114 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_33xx_43xx_interconnect_data.c+0−20

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_3xxx_data.c+0−29

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_44xx_data.c+0−10

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_54xx_data.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_7xx_data.c+0−30

This diff is large: its 66 lines aren’t shown here.

arch/arm/mach-omap2/pdata-quirks.c+8−1

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/pm44xx.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/powerdomains3xxx_data.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/soc.h+106−89

This diff is large: its 289 lines aren’t shown here.

arch/arm/mach-omap2/sram.c+0−25

This diff is large: its 36 lines aren’t shown here.

arch/arm/mach-omap2/sram.h+0−14

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-omap2/sram34xx.S+0−346

This diff is large: its 347 lines aren’t shown here.

arch/arm/mach-omap2/timer.c+73−91

This diff is large: its 222 lines aren’t shown here.

arch/arm/mach-omap2/vc.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-orion5x/Kconfig+3−0

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-orion5x/dns323-setup.c+3−50

This diff is large: its 70 lines aren’t shown here.

arch/arm/mach-orion5x/tsx09-common.c+4−45

This diff is large: its 71 lines aren’t shown here.

arch/arm/mach-prima2/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-pxa/cm-x300.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/colibri-pxa270-income.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/devices.c+20−0

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-pxa/ezx.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/hx4700.c+0−3

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-pxa/icontrol.c+0−2

This diff is large: its 14 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/magician.h+39−31

This diff is large: its 93 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/pxa27x.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-pxa/lpd270.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/magician.c+422−258

This diff is large: its 1062 lines aren’t shown here.

arch/arm/mach-pxa/mainstone.c+15−4

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-pxa/mioa701.c+9−2

This diff is large: its 50 lines aren’t shown here.

arch/arm/mach-pxa/palm27x.c+7−2

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-pxa/palmtc.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/palmte2.c+7−2

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-pxa/pcm990-baseboard.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/pxa27x.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-pxa/pxa3xx.c+5−4

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-pxa/raumfeld.c+13−8

This diff is large: its 81 lines aren’t shown here.

arch/arm/mach-pxa/tavorevb.c+9−4

This diff is large: its 45 lines aren’t shown here.

arch/arm/mach-pxa/viper.c+7−2

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-pxa/z2.c+9−6

This diff is large: its 59 lines aren’t shown here.

arch/arm/mach-pxa/zylonite.c+7−2

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-qcom/platsmp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-realview/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-rockchip/rockchip.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-h1940.c+7−3

This diff is large: its 40 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-rx1950.c+6−2

This diff is large: its 31 lines aren’t shown here.

arch/arm/mach-s3c64xx/dev-backlight.c+0−4

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-crag6410.c+9−4

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-hmt.c+7−2

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smartq.c+9−4

This diff is large: its 56 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smdk6410.c+9−3

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-shmobile/Kconfig+0−73

This diff is large: its 77 lines aren’t shown here.

arch/arm/mach-shmobile/Makefile+1−13

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-shmobile/Makefile.boot+0−12

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-shmobile/board-bockw-reference.c+0−86

This diff is large: its 87 lines aren’t shown here.

arch/arm/mach-shmobile/board-bockw.c+0−737

This diff is large: its 738 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7778.c+0−342

This diff is large: its 343 lines aren’t shown here.

arch/arm/mach-shmobile/clock.c+0−47

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-shmobile/clock.h+0−42

This diff is large: its 43 lines aren’t shown here.

arch/arm/mach-shmobile/common.h+0−5

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-shmobile/console.c+0−27

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-shmobile/intc.h+0−295

This diff is large: its 296 lines aren’t shown here.

arch/arm/mach-shmobile/platsmp-apmu.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-shmobile/pm-r8a7779.c+0−99

This diff is large: its 122 lines aren’t shown here.

arch/arm/mach-shmobile/pm-rmobile.c+6−33

This diff is large: its 68 lines aren’t shown here.

arch/arm/mach-shmobile/pm-rmobile.h+0−9

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7778.h+0−78

This diff is large: its 79 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7779.h+0−8

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7778.c+3−560

This diff is large: its 606 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7779.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-shmobile/setup-rcar-gen2.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-shmobile/sh-gpio.h+0−29

This diff is large: its 30 lines aren’t shown here.

arch/arm/mach-shmobile/timer.c+0−21

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-spear/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-spear/spear13xx.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-sunxi/sunxi.c+3−2

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-tegra/board-paz00.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-tegra/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-u300/core.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-u300/dummyspichip.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-uniphier/Makefile+1−1

This diff is large: its 4 lines aren’t shown here.

arch/arm/mach-uniphier/headsmp.S+43−0

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-uniphier/platsmp.c+155−30

This diff is large: its 229 lines aren’t shown here.

arch/arm/mach-ux500/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-ux500/timer.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-vexpress/hotplug.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-zynq/common.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/Kconfig+10−12

This diff is large: its 61 lines aren’t shown here.

arch/arm/mm/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/arm/mm/alignment.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/cache-uniphier.c+555−0

This diff is large: its 556 lines aren’t shown here.

arch/arm/mm/dma-mapping.c+10−3

This diff is large: its 44 lines aren’t shown here.

arch/arm/mm/fault.c+22−0

This diff is large: its 29 lines aren’t shown here.

arch/arm/mm/fault.h+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mm/highmem.c+0−10

This diff is large: its 14 lines aren’t shown here.

arch/arm/mm/mmu.c+4−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/net/bpf_jit_32.c+35−8

This diff is large: its 107 lines aren’t shown here.

arch/arm/net/bpf_jit_32.h+5−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/plat-orion/common.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/plat-samsung/devs.c+3−3

This diff is large: its 15 lines aren’t shown here.

arch/arm/vdso/vdsomunge.c+13−4

This diff is large: its 46 lines aren’t shown here.

arch/arm/xen/enlighten.c+16−4

This diff is large: its 56 lines aren’t shown here.

arch/arm/xen/mm.c+30−11

This diff is large: its 80 lines aren’t shown here.

arch/arm/xen/p2m.c+3−3

This diff is large: its 20 lines aren’t shown here.

arch/arm64/Kconfig+80−18

This diff is large: its 224 lines aren’t shown here.

arch/arm64/Kconfig.debug+1−5

This diff is large: its 20 lines aren’t shown here.

arch/arm64/Kconfig.platforms+9−3

This diff is large: its 34 lines aren’t shown here.

arch/arm64/Makefile+8−1

This diff is large: its 23 lines aren’t shown here.

arch/arm64/boot/dts/Makefile+7−0

This diff is large: its 15 lines aren’t shown here.

arch/arm64/boot/dts/altera/Makefile+5−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi+358−0

This diff is large: its 359 lines aren’t shown here.

arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts+39−0

This diff is large: its 40 lines aren’t shown here.

arch/arm64/boot/dts/amd/amd-overdrive.dts+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm64/boot/dts/apm/Makefile+1−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-merlin.dts+72−0

This diff is large: its 73 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-mustang.dts+12−0

This diff is large: its 19 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-shadowcat.dtsi+271−0

This diff is large: its 272 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-storm.dtsi+55−0

This diff is large: its 90 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno-base.dtsi+59−0

This diff is large: its 73 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno-motherboard.dtsi+21−6

This diff is large: its 70 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno-r1.dts+63−7

This diff is large: its 136 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno.dts+43−7

This diff is large: its 109 lines aren’t shown here.

arch/arm64/boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm64/boot/dts/arm/vexpress-v2m-rs1.dtsi+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi+103−0

This diff is large: its 107 lines aren’t shown here.

arch/arm64/boot/dts/exynos/exynos7.dtsi+7−0

This diff is large: its 21 lines aren’t shown here.

arch/arm64/boot/dts/freescale/Makefile+3−1

This diff is large: its 8 lines aren’t shown here.

arch/arm64/boot/dts/freescale/fsl-ls2080a-qds.dts+204−0

This diff is large: its 205 lines aren’t shown here.

arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts+166−0

This diff is large: its 167 lines aren’t shown here.

arch/arm64/boot/dts/freescale/fsl-ls2080a-simu.dtsrenamed from arch/arm64/boot/dts/freescale/fsl-ls2085a-simu.dts+15−10

This diff is large: its 51 lines aren’t shown here.

arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi+515−0

This diff is large: its 516 lines aren’t shown here.

arch/arm64/boot/dts/freescale/fsl-ls2085a.dtsi+0−163

This diff is large: its 164 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts+5−2

This diff is large: its 17 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/hi6220.dtsi+42−1

This diff is large: its 58 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/hip05-d02.dts+36−0

This diff is large: its 37 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/hip05.dtsi+271−0

This diff is large: its 272 lines aren’t shown here.

arch/arm64/boot/dts/hisilicon/hip05_hns.dtsi+191−0

This diff is large: its 192 lines aren’t shown here.

arch/arm64/boot/dts/marvell/Makefile+1−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/marvell/berlin4ct-stb.dts+66−0

This diff is large: its 67 lines aren’t shown here.

arch/arm64/boot/dts/marvell/berlin4ct.dtsi+120−0

This diff is large: its 134 lines aren’t shown here.

arch/arm64/boot/dts/mediatek/mt8173-evb.dts+18−0

This diff is large: its 25 lines aren’t shown here.

arch/arm64/boot/dts/mediatek/mt8173.dtsi+57−5

This diff is large: its 104 lines aren’t shown here.

arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi+30−0

This diff is large: its 48 lines aren’t shown here.

arch/arm64/boot/dts/qcom/msm8916-pins.dtsi+74−2

This diff is large: its 111 lines aren’t shown here.

arch/arm64/boot/dts/qcom/msm8916.dtsi+47−0

This diff is large: its 78 lines aren’t shown here.

arch/arm64/configs/defconfig+23−1

This diff is large: its 91 lines aren’t shown here.

arch/arm64/crypto/aes-ce-cipher.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/acpi.h+5−1

This diff is large: its 18 lines aren’t shown here.

arch/arm64/include/asm/arch_gicv3.h+170−0

This diff is large: its 171 lines aren’t shown here.

arch/arm64/include/asm/assembler.h+11−0

This diff is large: its 16 lines aren’t shown here.

arch/arm64/include/asm/atomic.h+60−5

This diff is large: its 89 lines aren’t shown here.

arch/arm64/include/asm/atomic_ll_sc.h+61−39

This diff is large: its 179 lines aren’t shown here.

arch/arm64/include/asm/atomic_lse.h+117−78

This diff is large: its 245 lines aren’t shown here.

arch/arm64/include/asm/barrier.h+10−6

This diff is large: its 38 lines aren’t shown here.

arch/arm64/include/asm/cache.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/cacheflush.h+7−0

This diff is large: its 14 lines aren’t shown here.

arch/arm64/include/asm/cachetype.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm64/include/asm/cmpxchg.h+136−143

This diff is large: its 308 lines aren’t shown here.

arch/arm64/include/asm/compat.h+1−2

This diff is large: its 17 lines aren’t shown here.

arch/arm64/include/asm/cpu.h+4−0

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/cpufeature.h+85−9

This diff is large: its 140 lines aren’t shown here.

arch/arm64/include/asm/cputype.h+9−21

This diff is large: its 47 lines aren’t shown here.

arch/arm64/include/asm/dcc.h+55−0

This diff is large: its 56 lines aren’t shown here.

arch/arm64/include/asm/dma-mapping.h+10−18

This diff is large: its 58 lines aren’t shown here.

arch/arm64/include/asm/fixmap.h+2−5

This diff is large: its 21 lines aren’t shown here.

arch/arm64/include/asm/hw_breakpoint.h+7−2

This diff is large: its 28 lines aren’t shown here.

arch/arm64/include/asm/hwcap.h+8−0

This diff is large: its 15 lines aren’t shown here.

arch/arm64/include/asm/irq.h+0−14

This diff is large: its 25 lines aren’t shown here.

arch/arm64/include/asm/kasan.h+38−0

This diff is large: its 39 lines aren’t shown here.

arch/arm64/include/asm/kernel-pgtable.h+83−0

This diff is large: its 84 lines aren’t shown here.

arch/arm64/include/asm/kvm_arm.h+16−0

This diff is large: its 21 lines aren’t shown here.

arch/arm64/include/asm/kvm_host.h+4−1

This diff is large: its 12 lines aren’t shown here.

arch/arm64/include/asm/memory.h+3−4

This diff is large: its 34 lines aren’t shown here.

arch/arm64/include/asm/mmu.h+8−7

This diff is large: its 24 lines aren’t shown here.

arch/arm64/include/asm/mmu_context.h+25−88

This diff is large: its 152 lines aren’t shown here.

arch/arm64/include/asm/page.h+9−18

This diff is large: its 41 lines aren’t shown here.

arch/arm64/include/asm/pgalloc.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm64/include/asm/pgtable-hwdef.h+45−3

This diff is large: its 96 lines aren’t shown here.

arch/arm64/include/asm/pgtable.h+32−6

This diff is large: its 102 lines aren’t shown here.

arch/arm64/include/asm/pmu.h+0−83

This diff is large: its 84 lines aren’t shown here.

arch/arm64/include/asm/processor.h+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm64/include/asm/ptrace.h+8−8

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/string.h+16−0

This diff is large: its 34 lines aren’t shown here.

arch/arm64/include/asm/sysreg.h+152−5

This diff is large: its 175 lines aren’t shown here.

arch/arm64/include/asm/thread_info.h+3−2

This diff is large: its 20 lines aren’t shown here.

arch/arm64/include/asm/tlb.h+15−11

This diff is large: its 33 lines aren’t shown here.

arch/arm64/include/asm/tlbflush.h+12−6

This diff is large: its 54 lines aren’t shown here.

arch/arm64/include/asm/unistd.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/unistd32.h+9−0

This diff is large: its 13 lines aren’t shown here.

arch/arm64/include/uapi/asm/kvm.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/uapi/asm/signal.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm64/kernel/Makefile+8−3

This diff is large: its 39 lines aren’t shown here.

arch/arm64/kernel/acpi.c+24−20

This diff is large: its 59 lines aren’t shown here.

arch/arm64/kernel/arm64ksyms.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm64/kernel/armv8_deprecated.c+9−7

This diff is large: its 31 lines aren’t shown here.

arch/arm64/kernel/asm-offsets.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/kernel/cpu_errata.c+10−1

This diff is large: its 30 lines aren’t shown here.

arch/arm64/kernel/cpufeature.c+842−24

This diff is large: its 922 lines aren’t shown here.

arch/arm64/kernel/cpuinfo.c+129−132

This diff is large: its 326 lines aren’t shown here.

arch/arm64/kernel/debug-monitors.c+18−15

This diff is large: its 90 lines aren’t shown here.

arch/arm64/kernel/efi-entry.S+5−5

This diff is large: its 28 lines aren’t shown here.

arch/arm64/kernel/efi.c+14−27

This diff is large: its 118 lines aren’t shown here.

arch/arm64/kernel/entry-ftrace.S+20−2

This diff is large: its 39 lines aren’t shown here.

arch/arm64/kernel/entry.S+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm64/kernel/fpsimd.c+5−11

This diff is large: its 27 lines aren’t shown here.

arch/arm64/kernel/head.S+39−39

This diff is large: its 181 lines aren’t shown here.

arch/arm64/kernel/hw_breakpoint.c+17−2

This diff is large: its 47 lines aren’t shown here.

arch/arm64/kernel/image.h+37−1

This diff is large: its 50 lines aren’t shown here.

arch/arm64/kernel/insn.c+3−3

This diff is large: its 25 lines aren’t shown here.

arch/arm64/kernel/irq.c+0−62

This diff is large: its 73 lines aren’t shown here.

arch/arm64/kernel/module.c+13−3

This diff is large: its 30 lines aren’t shown here.

arch/arm64/kernel/perf_event.c+208−858

This diff is large: its 1280 lines aren’t shown here.

arch/arm64/kernel/process.c+3−0

This diff is large: its 19 lines aren’t shown here.

arch/arm64/kernel/psci.c+0−14

This diff is large: its 21 lines aren’t shown here.

arch/arm64/kernel/setup.c+8−239

This diff is large: its 308 lines aren’t shown here.

arch/arm64/kernel/smp.c+14−10

This diff is large: its 78 lines aren’t shown here.

arch/arm64/kernel/stacktrace.c+1−5

This diff is large: its 13 lines aren’t shown here.

arch/arm64/kernel/suspend.c+24−10

This diff is large: its 68 lines aren’t shown here.

arch/arm64/kernel/time.c+1−7

This diff is large: its 18 lines aren’t shown here.

arch/arm64/kernel/traps.c+10−5

This diff is large: its 36 lines aren’t shown here.

arch/arm64/kernel/vdso/Makefile+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm64/kernel/vmlinux.lds.S+5−1

This diff is large: its 22 lines aren’t shown here.

arch/arm64/kvm/Kconfig+9−0

This diff is large: its 33 lines aren’t shown here.

arch/arm64/kvm/hyp.S+8−0

This diff is large: its 15 lines aren’t shown here.

arch/arm64/kvm/reset.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/kvm/sys_regs.c+6−6

This diff is large: its 20 lines aren’t shown here.

arch/arm64/lib/copy_from_user.S+44−34

This diff is large: its 101 lines aren’t shown here.

arch/arm64/lib/copy_in_user.S+38−29

This diff is large: its 90 lines aren’t shown here.

arch/arm64/lib/copy_template.S+193−0

This diff is large: its 194 lines aren’t shown here.

arch/arm64/lib/copy_to_user.S+38−29

This diff is large: its 90 lines aren’t shown here.

arch/arm64/lib/memchr.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/lib/memcmp.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/lib/memcpy.S+30−154

This diff is large: its 197 lines aren’t shown here.

arch/arm64/lib/memmove.S+6−3

This diff is large: its 24 lines aren’t shown here.

arch/arm64/lib/memset.S+4−1

This diff is large: its 16 lines aren’t shown here.

arch/arm64/lib/strcmp.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/lib/strlen.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/lib/strncmp.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm64/mm/Makefile+3−0

This diff is large: its 7 lines aren’t shown here.

arch/arm64/mm/cache.S+5−5

This diff is large: its 42 lines aren’t shown here.

arch/arm64/mm/context.c+143−93

This diff is large: its 279 lines aren’t shown here.

arch/arm64/mm/dma-mapping.c+468−12

This diff is large: its 519 lines aren’t shown here.

arch/arm64/mm/dump.c+17−1

This diff is large: its 39 lines aren’t shown here.

arch/arm64/mm/fault.c+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm64/mm/init.c+13−6

This diff is large: its 50 lines aren’t shown here.

arch/arm64/mm/kasan_init.c+165−0

This diff is large: its 166 lines aren’t shown here.

arch/arm64/mm/mmu.c+105−60

This diff is large: its 296 lines aren’t shown here.

arch/arm64/mm/pageattr.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/mm/pgd.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm64/mm/proc.S+9−5

This diff is large: its 47 lines aren’t shown here.

arch/arm64/net/bpf_jit.h+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm64/net/bpf_jit_comp.c+78−26

This diff is large: its 181 lines aren’t shown here.

arch/avr32/boards/atngw100/mrmt.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/avr32/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/avr32/include/asm/atomic.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/avr32/mach-at32ap/at32ap700x.c+1−8

This diff is large: its 20 lines aren’t shown here.

arch/blackfin/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/c6x/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/c6x/platforms/megamod-pic.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/cris/Kconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/cris/arch-v10/kernel/head.S+0−106

This diff is large: its 147 lines aren’t shown here.

arch/cris/arch-v10/kernel/kgdb.c+36−53

This diff is large: its 206 lines aren’t shown here.

arch/cris/arch-v10/mm/init.c+3−11

This diff is large: its 33 lines aren’t shown here.

arch/cris/arch-v32/Kconfig+0−89

This diff is large: its 96 lines aren’t shown here.

arch/cris/arch-v32/drivers/Kconfig+0−167

This diff is large: its 174 lines aren’t shown here.

arch/cris/arch-v32/drivers/Makefile+0−1

This diff is large: its 7 lines aren’t shown here.

arch/cris/arch-v32/drivers/axisflashmap.c+6−34

This diff is large: its 62 lines aren’t shown here.

arch/cris/arch-v32/drivers/i2c.c+0−751

This diff is large: its 752 lines aren’t shown here.

arch/cris/arch-v32/drivers/i2c.h+0−16

This diff is large: its 17 lines aren’t shown here.

arch/cris/arch-v32/drivers/mach-a3/Makefile+0−1

This diff is large: its 5 lines aren’t shown here.

arch/cris/arch-v32/drivers/mach-a3/gpio.c+0−999

This diff is large: its 1000 lines aren’t shown here.

arch/cris/arch-v32/drivers/mach-fs/Makefile+0−1

This diff is large: its 5 lines aren’t shown here.

arch/cris/arch-v32/drivers/mach-fs/gpio.c+0−978

This diff is large: its 979 lines aren’t shown here.

arch/cris/arch-v32/kernel/crisksyms.c+0−3

This diff is large: its 17 lines aren’t shown here.

arch/cris/arch-v32/kernel/debugport.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/cris/arch-v32/kernel/head.S+0−4

This diff is large: its 12 lines aren’t shown here.

arch/cris/arch-v32/kernel/irq.c+3−3

This diff is large: its 26 lines aren’t shown here.

arch/cris/arch-v32/kernel/kgdb.c+38−58

This diff is large: its 211 lines aren’t shown here.

arch/cris/arch-v32/kernel/setup.c+0−8

This diff is large: its 22 lines aren’t shown here.

arch/cris/arch-v32/mach-a3/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/cris/arch-v32/mach-a3/io.c+0−149

This diff is large: its 150 lines aren’t shown here.

arch/cris/arch-v32/mach-fs/Kconfig+0−19

This diff is large: its 26 lines aren’t shown here.

arch/cris/arch-v32/mach-fs/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/cris/arch-v32/mach-fs/io.c+0−191

This diff is large: its 192 lines aren’t shown here.

arch/cris/boot/dts/artpec3.dtsi+46−0

This diff is large: its 47 lines aren’t shown here.

arch/cris/boot/dts/dev88.dts+49−0

This diff is large: its 60 lines aren’t shown here.

arch/cris/boot/dts/etraxfs.dtsi+8−0

This diff is large: its 15 lines aren’t shown here.

arch/cris/boot/dts/include/dt-bindings+1−0

This diff is large: its 2 lines aren’t shown here.

arch/cris/boot/dts/p1343.dts+76−0

This diff is large: its 77 lines aren’t shown here.

arch/cris/boot/rescue/head_v10.S+0−3

This diff is large: its 10 lines aren’t shown here.

arch/cris/include/arch-v32/arch/io.h+0−140

This diff is large: its 141 lines aren’t shown here.

arch/cris/include/arch-v32/arch/irq.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/cris/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/cris/include/asm/eshlibld.h+1−2

This diff is large: its 10 lines aren’t shown here.

arch/cris/include/asm/io.h+2−0

This diff is large: its 10 lines aren’t shown here.

arch/cris/include/uapi/asm/etraxgpio.h+0−157

This diff is large: its 182 lines aren’t shown here.

arch/cris/kernel/crisksyms.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/cris/kernel/time.c+0−25

This diff is large: its 32 lines aren’t shown here.

arch/frv/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/frv/include/asm/atomic.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/frv/include/asm/highmem.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/frv/mm/highmem.c+0−5

This diff is large: its 12 lines aren’t shown here.

arch/h8300/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/h8300/Makefile+2−0

This diff is large: its 10 lines aren’t shown here.

arch/h8300/boot/compressed/Makefile+3−2

This diff is large: its 15 lines aren’t shown here.

arch/h8300/boot/compressed/head.S+2−2

This diff is large: its 19 lines aren’t shown here.

arch/h8300/boot/compressed/misc.c+1−6

This diff is large: its 25 lines aren’t shown here.

arch/h8300/boot/compressed/vmlinux.lds+1−1

This diff is large: its 8 lines aren’t shown here.

arch/h8300/boot/dts/Makefile+3−0

This diff is large: its 9 lines aren’t shown here.

arch/h8300/boot/dts/edosk2674.dts+3−3

This diff is large: its 25 lines aren’t shown here.

arch/h8300/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/h8300/include/asm/atomic.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/h8300/include/asm/io.h+6−6

This diff is large: its 27 lines aren’t shown here.

arch/h8300/include/asm/thread_info.h+6−8

This diff is large: its 28 lines aren’t shown here.

arch/h8300/kernel/setup.c+2−0

This diff is large: its 14 lines aren’t shown here.

arch/h8300/kernel/vmlinux.lds.S+2−2

This diff is large: its 20 lines aren’t shown here.

arch/hexagon/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/hexagon/include/asm/atomic.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/ia64/include/asm/atomic.h+4−4

This diff is large: its 16 lines aren’t shown here.

arch/ia64/include/asm/pci.h+0−5

This diff is large: its 12 lines aren’t shown here.

arch/ia64/include/asm/unistd.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/uapi/asm/unistd.h+1−0

This diff is large: its 7 lines aren’t shown here.

arch/ia64/kernel/entry.S+1−0

This diff is large: its 7 lines aren’t shown here.

arch/ia64/pci/pci.c+100−268

This diff is large: its 445 lines aren’t shown here.

arch/m32r/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/m32r/include/asm/atomic.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/m68k/configs/amiga_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/apollo_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/atari_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/bvme6000_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/hp300_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/mac_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/multi_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/mvme147_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/mvme16x_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/q40_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/sun3_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/configs/sun3x_defconfig+8−1

This diff is large: its 69 lines aren’t shown here.

arch/m68k/emu/nfblock.c+2−1

This diff is large: its 17 lines aren’t shown here.

arch/m68k/include/asm/atomic.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/m68k/include/asm/linkage.h+30−0

This diff is large: its 35 lines aren’t shown here.

arch/m68k/include/asm/unistd.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/include/uapi/asm/unistd.h+19−0

This diff is large: its 25 lines aren’t shown here.

arch/m68k/kernel/syscalltable.S+19−1

This diff is large: its 24 lines aren’t shown here.

arch/m68k/mac/psc.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/m68k/sun3/idprom.c+1−4

This diff is large: its 10 lines aren’t shown here.

arch/metag/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/metag/boot/dts/Makefile+3−4

This diff is large: its 15 lines aren’t shown here.

arch/metag/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/metag/include/asm/atomic_lnkget.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/metag/include/asm/atomic_lock1.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/metag/include/asm/highmem.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/metag/include/asm/irq.h+6−2

This diff is large: its 15 lines aren’t shown here.

arch/metag/kernel/smp.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/metag/mm/highmem.c+0−14

This diff is large: its 21 lines aren’t shown here.

arch/microblaze/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/microblaze/include/asm/highmem.h+0−13

This diff is large: its 20 lines aren’t shown here.

arch/microblaze/kernel/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/Kbuild+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/Kbuild.platforms+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/Kconfig+84−4

This diff is large: its 190 lines aren’t shown here.

arch/mips/Kconfig.debug+72−0

This diff is large: its 77 lines aren’t shown here.

arch/mips/Makefile+4−0

This diff is large: its 11 lines aren’t shown here.

arch/mips/ath79/irq.c+20−2

This diff is large: its 29 lines aren’t shown here.

arch/mips/ath79/setup.c+6−1

This diff is large: its 20 lines aren’t shown here.

arch/mips/bcm47xx/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/bcm47xx/setup.c+18−1

This diff is large: its 30 lines aren’t shown here.

arch/mips/bcm47xx/sprom.c+22−24

This diff is large: its 92 lines aren’t shown here.

arch/mips/bcm63xx/boards/board_bcm963xx.c+7−7

This diff is large: its 63 lines aren’t shown here.

arch/mips/bcm63xx/cpu.c+6−6

This diff is large: its 17 lines aren’t shown here.

arch/mips/bcm63xx/dev-pcmcia.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/bcm63xx/dev-spi.c+2−40

This diff is large: its 74 lines aren’t shown here.

arch/mips/bcm63xx/irq.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/bcm63xx/setup.c+4−4

This diff is large: its 36 lines aren’t shown here.

arch/mips/bcm63xx/timer.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/bmips/setup.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/boot/dts/Makefile+4−0

This diff is large: its 14 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm7346.dtsi+112−2

This diff is large: its 140 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm7358.dtsi+60−2

This diff is large: its 82 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm7360.dtsi+60−2

This diff is large: its 82 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm7362.dtsi+92−2

This diff is large: its 120 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm7425.dtsi+42−0

This diff is large: its 48 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm97346dbsmb.dts+28−0

This diff is large: its 39 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm97358svmb.dts+16−0

This diff is large: its 23 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm97360svmb.dts+16−0

This diff is large: its 23 lines aren’t shown here.

arch/mips/boot/dts/brcm/bcm97362svmb.dts+20−0

This diff is large: its 31 lines aren’t shown here.

arch/mips/boot/dts/mti/malta.dts+4−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/boot/dts/qca/ar9132.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/boot/dts/xilfpga/Makefile+9−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/boot/dts/xilfpga/microAptiv.dtsi+21−0

This diff is large: its 22 lines aren’t shown here.

arch/mips/boot/dts/xilfpga/nexys4ddr.dts+46−0

This diff is large: its 47 lines aren’t shown here.

arch/mips/cavium-octeon/octeon-irq.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/cavium-octeon/setup.c+10−3

This diff is large: its 46 lines aren’t shown here.

arch/mips/configs/bigsur_defconfig+6−6

This diff is large: its 27 lines aren’t shown here.

arch/mips/configs/bmips_be_defconfig+2−1

This diff is large: its 17 lines aren’t shown here.

arch/mips/configs/bmips_stb_defconfig+2−1

This diff is large: its 17 lines aren’t shown here.

arch/mips/configs/capcella_defconfig+3−3

This diff is large: its 13 lines aren’t shown here.

arch/mips/configs/e55_defconfig+3−3

This diff is large: its 13 lines aren’t shown here.

arch/mips/configs/fuloong2e_defconfig+5−9

This diff is large: its 34 lines aren’t shown here.

arch/mips/configs/lasat_defconfig+5−5

This diff is large: its 17 lines aren’t shown here.

arch/mips/configs/lemote2f_defconfig+3−8

This diff is large: its 20 lines aren’t shown here.

arch/mips/configs/malta_defconfig+2−4

This diff is large: its 24 lines aren’t shown here.

arch/mips/configs/malta_kvm_defconfig+9−7

This diff is large: its 34 lines aren’t shown here.

arch/mips/configs/malta_kvm_guest_defconfig+9−7

This diff is large: its 34 lines aren’t shown here.

arch/mips/configs/malta_qemu_32r6_defconfig+5−6

This diff is large: its 21 lines aren’t shown here.

arch/mips/configs/maltaaprp_defconfig+5−6

This diff is large: its 21 lines aren’t shown here.

arch/mips/configs/maltasmvp_eva_defconfig+5−6

This diff is large: its 21 lines aren’t shown here.

arch/mips/configs/maltaup_defconfig+5−6

This diff is large: its 21 lines aren’t shown here.

arch/mips/configs/maltaup_xpa_defconfig+9−7

This diff is large: its 34 lines aren’t shown here.

arch/mips/configs/mpc30x_defconfig+3−3

This diff is large: its 13 lines aren’t shown here.

arch/mips/configs/pistachio_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/configs/xilfpga_defconfig+40−0

This diff is large: its 41 lines aren’t shown here.

arch/mips/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/include/asm/abi.h+3−2

This diff is large: its 23 lines aren’t shown here.

arch/mips/include/asm/atomic.h+5−5

This diff is large: its 44 lines aren’t shown here.

arch/mips/include/asm/bcache.h+27−0

This diff is large: its 55 lines aren’t shown here.

arch/mips/include/asm/cdmm.h+11−0

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/asm/clocksource.h+29−0

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/compat.h+34−28

This diff is large: its 99 lines aren’t shown here.

arch/mips/include/asm/cpu-features.h+4−5

This diff is large: its 23 lines aren’t shown here.

arch/mips/include/asm/cpu.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/debug.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/mips/include/asm/elf.h+7−0

This diff is large: its 21 lines aren’t shown here.

arch/mips/include/asm/fw/fw.h+0−16

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/highmem.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/io.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/kvm_host.h+2−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/maar.h+9−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/include/asm/mach-bcm47xx/bcm47xx.h+0−5

This diff is large: its 12 lines aren’t shown here.

arch/mips/include/asm/mach-bcm63xx/bcm63xx_dev_spi.h+0−44

This diff is large: its 49 lines aren’t shown here.

arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h+14−0

This diff is large: its 28 lines aren’t shown here.

arch/mips/include/asm/mach-malta/malta-dtshim.h+29−0

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/mt7620.h+1−7

This diff is large: its 19 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/ralink_regs.h+17−0

This diff is large: its 24 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/rt305x.h+6−15

This diff is large: its 50 lines aren’t shown here.

arch/mips/include/asm/mach-xilfpga/irq.h+18−0

This diff is large: its 19 lines aren’t shown here.

arch/mips/include/asm/mips-cm.h+109−8

This diff is large: its 180 lines aren’t shown here.

arch/mips/include/asm/mips-cpc.h+2−1

This diff is large: its 10 lines aren’t shown here.

arch/mips/include/asm/mipsregs.h+11−9

This diff is large: its 50 lines aren’t shown here.

arch/mips/include/asm/page.h+3−2

This diff is large: its 20 lines aren’t shown here.

arch/mips/include/asm/processor.h+1−7

This diff is large: its 22 lines aren’t shown here.

arch/mips/include/asm/vdso.h+123−16

This diff is large: its 153 lines aren’t shown here.

arch/mips/include/uapi/asm/Kbuild+1−1

This diff is large: its 11 lines aren’t shown here.

arch/mips/include/uapi/asm/auxvec.h+17−0

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/uapi/asm/mman.h+6−0

This diff is large: its 13 lines aren’t shown here.

arch/mips/include/uapi/asm/swab.h+7−12

This diff is large: its 58 lines aren’t shown here.

arch/mips/include/uapi/asm/unistd.h+15−6

This diff is large: its 65 lines aren’t shown here.

arch/mips/jz4740/board-qi_lb60.c+9−5

This diff is large: its 47 lines aren’t shown here.

arch/mips/jz4740/gpio.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/kernel/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/kernel/cps-vec-ns16550.S+202−0

This diff is large: its 203 lines aren’t shown here.

arch/mips/kernel/cps-vec.S+43−13

This diff is large: its 170 lines aren’t shown here.

arch/mips/kernel/cpu-probe.c+14−10

This diff is large: its 56 lines aren’t shown here.

arch/mips/kernel/csrc-r4k.c+44−0

This diff is large: its 58 lines aren’t shown here.

arch/mips/kernel/idle.c+14−3

This diff is large: its 50 lines aren’t shown here.

arch/mips/kernel/mips-cm.c+83−31

This diff is large: its 175 lines aren’t shown here.

arch/mips/kernel/mips-cpc.c+6−0

This diff is large: its 13 lines aren’t shown here.

arch/mips/kernel/mips-r2-to-r6-emul.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/octeon_switch.S+1−25

This diff is large: its 40 lines aren’t shown here.

arch/mips/kernel/r2300_switch.S+1−27

This diff is large: its 44 lines aren’t shown here.

arch/mips/kernel/scall32-o32.S+19−23

This diff is large: its 83 lines aren’t shown here.

arch/mips/kernel/scall64-64.S+19−22

This diff is large: its 85 lines aren’t shown here.

arch/mips/kernel/scall64-n32.S+8−14

This diff is large: its 50 lines aren’t shown here.

arch/mips/kernel/scall64-o32.S+8−14

This diff is large: its 50 lines aren’t shown here.

arch/mips/kernel/segment.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/setup.c+31−8

This diff is large: its 84 lines aren’t shown here.

arch/mips/kernel/signal.c+5−7

This diff is large: its 42 lines aren’t shown here.

arch/mips/kernel/signal32.c+2−5

This diff is large: its 25 lines aren’t shown here.

arch/mips/kernel/signal_n32.c+2−3

This diff is large: its 22 lines aren’t shown here.

arch/mips/kernel/smp-cps.c+30−5

This diff is large: its 82 lines aren’t shown here.

arch/mips/kernel/smp-gic.c+2−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/kernel/smp.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/spinlock_test.c+1−3

This diff is large: its 18 lines aren’t shown here.

arch/mips/kernel/stacktrace.c+15−12

This diff is large: its 66 lines aren’t shown here.

arch/mips/kernel/traps.c+5−6

This diff is large: its 38 lines aren’t shown here.

arch/mips/kernel/unaligned.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/vdso.c+130−77

This diff is large: its 253 lines aren’t shown here.

arch/mips/kernel/vmlinux.lds.S+14−1

This diff is large: its 44 lines aren’t shown here.

arch/mips/kvm/locore.S+0−8

This diff is large: its 15 lines aren’t shown here.

arch/mips/lantiq/clk.c+17−0

This diff is large: its 24 lines aren’t shown here.

arch/mips/lantiq/clk.h+13−0

This diff is large: its 32 lines aren’t shown here.

arch/mips/lantiq/irq.c+4−4

This diff is large: its 22 lines aren’t shown here.

arch/mips/lantiq/prom.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/mips/lantiq/xway/clk.c+170−10

This diff is large: its 232 lines aren’t shown here.

arch/mips/lantiq/xway/prom.c+33−2

This diff is large: its 70 lines aren’t shown here.

arch/mips/lantiq/xway/reset.c+175−21

This diff is large: its 275 lines aren’t shown here.

arch/mips/lantiq/xway/sysctrl.c+262−39

This diff is large: its 474 lines aren’t shown here.

arch/mips/lib/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

arch/mips/lib/bswapdi.c+15−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/lib/bswapsi.c+11−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/loongson64/Kconfig+0−5

This diff is large: its 12 lines aren’t shown here.

arch/mips/loongson64/common/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/loongson64/common/env.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/loongson64/lemote-2f/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

arch/mips/math-emu/me-debugfs.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/mips/mm/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/mm/dma-default.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/mm/highmem.c+0−13

This diff is large: its 20 lines aren’t shown here.

arch/mips/mm/init.c+114−63

This diff is large: its 198 lines aren’t shown here.

arch/mips/mm/sc-debugfs.c+81−0

This diff is large: its 82 lines aren’t shown here.

arch/mips/mm/sc-mips.c+62−3

This diff is large: its 95 lines aren’t shown here.

arch/mips/mm/tlbex.c+62−35

This diff is large: its 163 lines aren’t shown here.

arch/mips/mti-malta/Makefile+12−3

This diff is large: its 22 lines aren’t shown here.

arch/mips/mti-malta/malta-dtshim.c+162−0

This diff is large: its 163 lines aren’t shown here.

arch/mips/mti-malta/malta-init.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/mti-malta/malta-memory.c+2−129

This diff is large: its 150 lines aren’t shown here.

arch/mips/mti-malta/malta-setup.c+4−1

This diff is large: its 20 lines aren’t shown here.

arch/mips/mti-sead3/Makefile+0−2

This diff is large: its 7 lines aren’t shown here.

arch/mips/net/bpf_jit.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/net/bpf_jit_asm.S+54−9

This diff is large: its 119 lines aren’t shown here.

arch/mips/netlogic/xlp/dt.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/pci/pci-rt3883.c+2−4

This diff is large: its 20 lines aren’t shown here.

arch/mips/pistachio/init.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/pistachio/time.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/ralink/cevt-rt3352.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/ralink/clk.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/mips/ralink/early_printk.c+26−0

This diff is large: its 47 lines aren’t shown here.

arch/mips/ralink/mt7620.c+50−13

This diff is large: its 121 lines aren’t shown here.

arch/mips/ralink/of.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/mips/ralink/prom.c+5−0

This diff is large: its 17 lines aren’t shown here.

arch/mips/ralink/reset.c+10−3

This diff is large: its 41 lines aren’t shown here.

arch/mips/ralink/rt288x.c+1−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/ralink/rt305x.c+6−7

This diff is large: its 47 lines aren’t shown here.

arch/mips/ralink/rt3883.c+2−0

This diff is large: its 7 lines aren’t shown here.

arch/mips/txx9/generic/spi_eeprom.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/vdso/.gitignore+4−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/vdso/Makefile+160−0

This diff is large: its 161 lines aren’t shown here.

arch/mips/vdso/elf.S+68−0

This diff is large: its 69 lines aren’t shown here.

arch/mips/vdso/genvdso.c+293−0

This diff is large: its 294 lines aren’t shown here.

arch/mips/vdso/genvdso.h+187−0

This diff is large: its 188 lines aren’t shown here.

arch/mips/vdso/gettimeofday.c+232−0

This diff is large: its 233 lines aren’t shown here.

arch/mips/vdso/sigreturn.S+49−0

This diff is large: its 50 lines aren’t shown here.

arch/mips/vdso/vdso.h+89−0

This diff is large: its 90 lines aren’t shown here.

arch/mips/vdso/vdso.lds.S+105−0

This diff is large: its 106 lines aren’t shown here.

arch/mips/xilfpga/Kconfig+9−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/xilfpga/Makefile+7−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/xilfpga/Platform+3−0

This diff is large: its 4 lines aren’t shown here.

arch/mips/xilfpga/init.c+57−0

This diff is large: its 58 lines aren’t shown here.

arch/mips/xilfpga/intc.c+25−0

This diff is large: its 26 lines aren’t shown here.

arch/mips/xilfpga/time.c+41−0

This diff is large: its 42 lines aren’t shown here.

arch/mn10300/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mn10300/include/asm/atomic.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/nios2/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/nios2/include/asm/cmpxchg.h+0−47

This diff is large: its 54 lines aren’t shown here.

arch/nios2/kernel/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/nios2/kernel/time.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/nios2/lib/memmove.c+0−2

This diff is large: its 13 lines aren’t shown here.

arch/nios2/lib/memset.c+0−2

This diff is large: its 13 lines aren’t shown here.

arch/parisc/Kconfig+3−0

This diff is large: its 10 lines aren’t shown here.

arch/parisc/include/asm/atomic.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/parisc/include/asm/cache.h+5−13

This diff is large: its 26 lines aren’t shown here.

arch/parisc/include/asm/cacheflush.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/parisc/include/asm/compat.h+2−2

This diff is large: its 13 lines aren’t shown here.

arch/parisc/include/asm/hugetlb.h+85−0

This diff is large: its 86 lines aren’t shown here.

arch/parisc/include/asm/page.h+12−1

This diff is large: its 24 lines aren’t shown here.

arch/parisc/include/asm/pgalloc.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/parisc/include/asm/pgtable.h+22−4

This diff is large: its 69 lines aren’t shown here.

arch/parisc/include/asm/processor.h+0−27

This diff is large: its 34 lines aren’t shown here.

arch/parisc/include/uapi/asm/ipcbuf.h+12−7

This diff is large: its 36 lines aren’t shown here.

arch/parisc/include/uapi/asm/mman.h+3−10

This diff is large: its 27 lines aren’t shown here.

arch/parisc/include/uapi/asm/msgbuf.h+5−5

This diff is large: its 19 lines aren’t shown here.

arch/parisc/include/uapi/asm/posix_types.h+2−0

This diff is large: its 11 lines aren’t shown here.

arch/parisc/include/uapi/asm/sembuf.h+3−3

This diff is large: its 13 lines aren’t shown here.

arch/parisc/include/uapi/asm/shmbuf.h+4−4

This diff is large: its 17 lines aren’t shown here.

arch/parisc/include/uapi/asm/stat.h+0−31

This diff is large: its 38 lines aren’t shown here.

arch/parisc/include/uapi/asm/unistd.h+3−1

This diff is large: its 12 lines aren’t shown here.

arch/parisc/kernel/asm-offsets.c+8−0

This diff is large: its 15 lines aren’t shown here.

arch/parisc/kernel/entry.S+34−22

This diff is large: its 162 lines aren’t shown here.

arch/parisc/kernel/head.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/parisc/kernel/setup.c+13−1

This diff is large: its 35 lines aren’t shown here.

arch/parisc/kernel/syscall.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/parisc/kernel/syscall_table.S+2−0

This diff is large: its 9 lines aren’t shown here.

arch/parisc/kernel/traps.c+15−20

This diff is large: its 61 lines aren’t shown here.

arch/parisc/kernel/vmlinux.lds.S+6−3

This diff is large: its 31 lines aren’t shown here.

arch/parisc/mm/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/parisc/mm/hugetlbpage.c+161−0

This diff is large: its 162 lines aren’t shown here.

arch/parisc/mm/init.c+33−23

This diff is large: its 120 lines aren’t shown here.

arch/powerpc/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/Makefile+4−2

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/boot/Makefile+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4420qds.dtsrenamed from arch/powerpc/boot/dts/b4420qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4420si-post.dtsi+3−1

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4420si-pre.dtsi+9−4

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4860qds.dtsrenamed from arch/powerpc/boot/dts/b4860qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4860si-post.dtsi+22−4

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4860si-pre.dtsi+15−5

This diff is large: its 59 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4qds.dtsirenamed from arch/powerpc/boot/dts/b4qds.dtsi+1−1

This diff is large: its 6 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4si-post.dtsi+28−5

This diff is large: its 46 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/bsc9131rdb.dtsrenamed from arch/powerpc/boot/dts/bsc9131rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/bsc9131rdb.dtsirenamed from arch/powerpc/boot/dts/bsc9131rdb.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/bsc9132qds.dtsrenamed from arch/powerpc/boot/dts/bsc9132qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/bsc9132qds.dtsirenamed from arch/powerpc/boot/dts/bsc9132qds.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/c293pcie.dtsrenamed from arch/powerpc/boot/dts/c293pcie.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/cyrus_p5020.dts+155−0

This diff is large: its 156 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/ge_imp3a.dtsrenamed from arch/powerpc/boot/dts/ge_imp3a.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/kmcoge4.dtsrenamed from arch/powerpc/boot/dts/kmcoge4.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8536ds.dtsrenamed from arch/powerpc/boot/dts/mpc8536ds.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8536ds.dtsirenamed from arch/powerpc/boot/dts/mpc8536ds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8536ds_36b.dtsrenamed from arch/powerpc/boot/dts/mpc8536ds_36b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8540ads.dtsrenamed from arch/powerpc/boot/dts/mpc8540ads.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8541cds.dtsrenamed from arch/powerpc/boot/dts/mpc8541cds.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8544ds.dtsrenamed from arch/powerpc/boot/dts/mpc8544ds.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8544ds.dtsirenamed from arch/powerpc/boot/dts/mpc8544ds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8548cds.dtsirenamed from arch/powerpc/boot/dts/mpc8548cds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8548cds_32b.dtsrenamed from arch/powerpc/boot/dts/mpc8548cds_32b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8548cds_36b.dtsrenamed from arch/powerpc/boot/dts/mpc8548cds_36b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8555cds.dtsrenamed from arch/powerpc/boot/dts/mpc8555cds.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8560ads.dtsrenamed from arch/powerpc/boot/dts/mpc8560ads.dts+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8568mds.dtsrenamed from arch/powerpc/boot/dts/mpc8568mds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8569mds.dtsrenamed from arch/powerpc/boot/dts/mpc8569mds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8572ds.dtsrenamed from arch/powerpc/boot/dts/mpc8572ds.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8572ds.dtsirenamed from arch/powerpc/boot/dts/mpc8572ds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8572ds_36b.dtsrenamed from arch/powerpc/boot/dts/mpc8572ds_36b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mpc8572ds_camp_core0.dtsrenamed from arch/powerpc/boot/dts/mpc8572ds_camp_core0.dts+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8572ds_camp_core1.dtsrenamed from arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/mpc8572si-post.dtsi+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/mvme2500.dtsrenamed from arch/powerpc/boot/dts/mvme2500.dts+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/oca4080.dtsrenamed from arch/powerpc/boot/dts/oca4080.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb-pa.dtsrenamed from arch/powerpc/boot/dts/p1010rdb-pa.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb-pa.dtsirenamed from arch/powerpc/boot/dts/p1010rdb-pa.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1010rdb-pa_36b.dtsrenamed from arch/powerpc/boot/dts/p1010rdb-pa_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb-pb.dtsrenamed from arch/powerpc/boot/dts/p1010rdb-pb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb-pb_36b.dtsrenamed from arch/powerpc/boot/dts/p1010rdb-pb_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb.dtsirenamed from arch/powerpc/boot/dts/p1010rdb.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1010rdb_32b.dtsirenamed from arch/powerpc/boot/dts/p1010rdb_32b.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1010rdb_36b.dtsirenamed from arch/powerpc/boot/dts/p1010rdb_36b.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020mbg-pc.dtsirenamed from arch/powerpc/boot/dts/p1020mbg-pc.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020mbg-pc_32b.dtsrenamed from arch/powerpc/boot/dts/p1020mbg-pc_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020mbg-pc_36b.dtsrenamed from arch/powerpc/boot/dts/p1020mbg-pc_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020rdb-pc.dtsirenamed from arch/powerpc/boot/dts/p1020rdb-pc.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020rdb-pc_32b.dtsrenamed from arch/powerpc/boot/dts/p1020rdb-pc_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020rdb-pc_36b.dtsrenamed from arch/powerpc/boot/dts/p1020rdb-pc_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020rdb-pc_camp_core0.dtsrenamed from arch/powerpc/boot/dts/p1020rdb-pc_camp_core0.dts+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020rdb-pc_camp_core1.dtsrenamed from arch/powerpc/boot/dts/p1020rdb-pc_camp_core1.dts+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020rdb-pd.dtsrenamed from arch/powerpc/boot/dts/p1020rdb-pd.dts+14−2

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020rdb.dtsrenamed from arch/powerpc/boot/dts/p1020rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020rdb.dtsirenamed from arch/powerpc/boot/dts/p1020rdb.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020rdb_36b.dtsrenamed from arch/powerpc/boot/dts/p1020rdb_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020utm-pc.dtsirenamed from arch/powerpc/boot/dts/p1020utm-pc.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1020utm-pc_32b.dtsrenamed from arch/powerpc/boot/dts/p1020utm-pc_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1020utm-pc_36b.dtsrenamed from arch/powerpc/boot/dts/p1020utm-pc_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1021mds.dtsrenamed from arch/powerpc/boot/dts/p1021mds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1021rdb-pc.dtsirenamed from arch/powerpc/boot/dts/p1021rdb-pc.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1021rdb-pc_32b.dtsrenamed from arch/powerpc/boot/dts/p1021rdb-pc_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1021rdb-pc_36b.dtsrenamed from arch/powerpc/boot/dts/p1021rdb-pc_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1022ds.dtsirenamed from arch/powerpc/boot/dts/p1022ds.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1022ds_32b.dtsrenamed from arch/powerpc/boot/dts/p1022ds_32b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1022ds_36b.dtsrenamed from arch/powerpc/boot/dts/p1022ds_36b.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1022rdk.dtsrenamed from arch/powerpc/boot/dts/p1022rdk.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1022si-post.dtsi+2−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1023rdb.dtsrenamed from arch/powerpc/boot/dts/p1023rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1024rdb.dtsirenamed from arch/powerpc/boot/dts/p1024rdb.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1024rdb_32b.dtsrenamed from arch/powerpc/boot/dts/p1024rdb_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1024rdb_36b.dtsrenamed from arch/powerpc/boot/dts/p1024rdb_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1025rdb.dtsirenamed from arch/powerpc/boot/dts/p1025rdb.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p1025rdb_32b.dtsrenamed from arch/powerpc/boot/dts/p1025rdb_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1025rdb_36b.dtsrenamed from arch/powerpc/boot/dts/p1025rdb_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1025twr.dtsrenamed from arch/powerpc/boot/dts/p1025twr.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p1025twr.dtsirenamed from arch/powerpc/boot/dts/p1025twr.dtsi+12−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2020ds.dtsrenamed from arch/powerpc/boot/dts/p2020ds.dts+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2020ds.dtsirenamed from arch/powerpc/boot/dts/p2020ds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/p2020rdb-pc.dtsirenamed from arch/powerpc/boot/dts/p2020rdb-pc.dtsi+6−6

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2020rdb-pc_32b.dtsrenamed from arch/powerpc/boot/dts/p2020rdb-pc_32b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2020rdb-pc_36b.dtsrenamed from arch/powerpc/boot/dts/p2020rdb-pc_36b.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2020rdb.dtsrenamed from arch/powerpc/boot/dts/p2020rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2041rdb.dtsrenamed from arch/powerpc/boot/dts/p2041rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2041si-post.dtsi+28−1

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2041si-pre.dtsi+9−1

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p3041ds.dtsrenamed from arch/powerpc/boot/dts/p3041ds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p3041si-post.dtsi+28−1

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p3041si-pre.dtsi+9−1

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p4080ds.dtsrenamed from arch/powerpc/boot/dts/p4080ds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p4080si-post.dtsi+47−1

This diff is large: its 60 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p4080si-pre.dtsi+14−1

This diff is large: its 29 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5020ds.dtsrenamed from arch/powerpc/boot/dts/p5020ds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5020si-post.dtsi+28−1

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5020si-pre.dtsi+9−1

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5040ds.dtsrenamed from arch/powerpc/boot/dts/p5040ds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5040si-post.dtsi+55−1

This diff is large: its 68 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5040si-pre.dtsi+16−1

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/ppa8548.dtsrenamed from arch/powerpc/boot/dts/ppa8548.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi+2−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-clockgen2.dtsi+2−1

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-10g-0.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-0.dtsi+69−0

This diff is large: its 70 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-1.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-2.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-3.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-4.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-0.dtsi+101−0

This diff is large: its 102 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-10g-0.dtsi+61−0

This diff is large: its 62 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-0.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-1.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-2.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-3.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1-1g-4.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman-1.dtsi+101−0

This diff is large: its 102 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-0-best-effort.dtsi+66−0

This diff is large: its 67 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-0.dtsi+63−0

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-1-best-effort.dtsi+66−0

This diff is large: its 67 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-10g-1.dtsi+63−0

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-0.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-1.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-2.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-3.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-4.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0-1g-5.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-0.dtsi+106−0

This diff is large: its 107 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-10g-0.dtsi+63−0

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-10g-1.dtsi+63−0

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-0.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-1.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-2.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-3.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-4.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1-1g-5.dtsi+62−0

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3-1.dtsi+106−0

This diff is large: its 107 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-fman3l-0.dtsi+94−0

This diff is large: its 95 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1023rdb.dtsrenamed from arch/powerpc/boot/dts/t1023rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1023si-post.dtsi+19−0

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1024qds.dtsrenamed from arch/powerpc/boot/dts/t1024qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1024rdb.dtsrenamed from arch/powerpc/boot/dts/t1024rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t102xsi-pre.dtsi+6−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1040d4rdb.dtsrenamed from arch/powerpc/boot/dts/t1040d4rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1040qds.dtsrenamed from arch/powerpc/boot/dts/t1040qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1040rdb.dtsrenamed from arch/powerpc/boot/dts/t1040rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1040si-post.dtsi+31−0

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1042d4rdb.dtsrenamed from arch/powerpc/boot/dts/t1042d4rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1042qds.dtsrenamed from arch/powerpc/boot/dts/t1042qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1042rdb.dtsrenamed from arch/powerpc/boot/dts/t1042rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1042rdb_pi.dtsrenamed from arch/powerpc/boot/dts/t1042rdb_pi.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t104xd4rdb.dtsirenamed from arch/powerpc/boot/dts/t104xd4rdb.dtsi+10−0

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t104xqds.dtsirenamed from arch/powerpc/boot/dts/t104xqds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/t104xrdb.dtsirenamed from arch/powerpc/boot/dts/t104xrdb.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/t104xsi-pre.dtsi+8−1

This diff is large: its 23 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t2080qds.dtsrenamed from arch/powerpc/boot/dts/t2080qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t2080rdb.dtsrenamed from arch/powerpc/boot/dts/t2080rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t2081qds.dtsrenamed from arch/powerpc/boot/dts/t2081qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t2081si-post.dtsi+43−0

This diff is large: its 50 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t208xqds.dtsirenamed from arch/powerpc/boot/dts/t208xqds.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/t208xrdb.dtsirenamed from arch/powerpc/boot/dts/t208xrdb.dtsi+0−0

File renamed without changes.

arch/powerpc/boot/dts/fsl/t208xsi-pre.dtsi+11−0

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t4240qds.dtsrenamed from arch/powerpc/boot/dts/t4240qds.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t4240rdb.dtsrenamed from arch/powerpc/boot/dts/t4240rdb.dts+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t4240si-post.dtsi+87−1

This diff is large: its 102 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t4240si-pre.dtsi+21−1

This diff is large: its 43 lines aren’t shown here.

arch/powerpc/boot/dts/mpc5121.dtsi+9−2

This diff is large: its 25 lines aren’t shown here.

arch/powerpc/boot/dts/mpc5125twr.dts+10−1

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/boot/dts/prpmc2800.dts+0−297

This diff is large: its 298 lines aren’t shown here.

arch/powerpc/boot/page.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/boot/prpmc2800.c+0−571

This diff is large: its 572 lines aren’t shown here.

arch/powerpc/boot/wrapper+21−4

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/configs/cell_defconfig+1−1

This diff is large: its 7 lines aren’t shown here.

arch/powerpc/configs/mpc512x_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/ppc64_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/configs/ps3_defconfig+1−6

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/configs/pseries_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/cache.h+0−7

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/include/asm/disassemble.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/asm/exception-64e.h+8−7

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/include/asm/highmem.h+0−13

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/include/asm/kvm_host.h+2−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/include/asm/machdep.h+7−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/include/asm/mmu-hash64.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/mpc5121.h+59−0

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/include/asm/mpc52xx_psc.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/msi_bitmap.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/page.h+25−7

This diff is large: its 86 lines aren’t shown here.

arch/powerpc/include/asm/pgtable-ppc64.h+9−1

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/include/asm/pgtable.h+3−3

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/include/asm/ppc-opcode.h+0−17

This diff is large: its 38 lines aren’t shown here.

arch/powerpc/include/asm/reg.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/reg_booke.h+6−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/include/asm/systbl.h+13−0

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/include/asm/unistd.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/word-at-a-time.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/uapi/asm/mman.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/uapi/asm/unistd.h+13−0

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/kernel/crash.c+3−3

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/kernel/dma.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/eeh.c+4−4

This diff is large: its 29 lines aren’t shown here.

arch/powerpc/kernel/eeh_driver.c+22−5

This diff is large: its 51 lines aren’t shown here.

arch/powerpc/kernel/exceptions-64e.S+11−6

This diff is large: its 54 lines aren’t shown here.

arch/powerpc/kernel/head_64.S+39−4

This diff is large: its 99 lines aren’t shown here.

arch/powerpc/kernel/io-workarounds.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/machine_kexec_64.c+18−0

This diff is large: its 43 lines aren’t shown here.

arch/powerpc/kernel/misc_64.S+59−1

This diff is large: its 119 lines aren’t shown here.

arch/powerpc/kernel/nvram_64.c+8−7

This diff is large: its 46 lines aren’t shown here.

arch/powerpc/kernel/paca.c+7−2

This diff is large: its 22 lines aren’t shown here.

arch/powerpc/kernel/pci-common.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kernel/prom.c+10−8

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/kernel/prom_init.c+30−10

This diff is large: its 75 lines aren’t shown here.

arch/powerpc/kernel/rtas.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/kernel/setup_64.c+24−1

This diff is large: its 51 lines aren’t shown here.

arch/powerpc/kernel/vdso32/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/vdso32/datapage.S+7−5

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/kernel/vdso64/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/vdso64/datapage.S+7−5

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/kernel/vmlinux.lds.S+6−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/kvm/book3s_64_mmu_hv.c+3−2

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv.c+2−55

This diff is large: its 109 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_rm_mmu.c+7−3

This diff is large: its 33 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_rmhandlers.S+34−15

This diff is large: its 128 lines aren’t shown here.

arch/powerpc/kvm/e500.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/kvm/e500_emulate.c+19−0

This diff is large: its 47 lines aren’t shown here.

arch/powerpc/kvm/e500_mmu_host.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/kvm/powerpc.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/mm/fsl_booke_mmu.c+17−9

This diff is large: its 80 lines aren’t shown here.

arch/powerpc/mm/hash_native_64.c+11−12

This diff is large: its 57 lines aren’t shown here.

arch/powerpc/mm/hash_utils_64.c+4−3

This diff is large: its 35 lines aren’t shown here.

arch/powerpc/mm/hugetlbpage.c+35−5

This diff is large: its 95 lines aren’t shown here.

arch/powerpc/mm/mmu_decl.h+3−1

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/mm/numa.c+2−5

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/mm/slb.c+27−22

This diff is large: its 129 lines aren’t shown here.

arch/powerpc/mm/tlb_hash64.c+5−4

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/mm/tlb_low_64e.S+17−8

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/mm/tlb_nohash.c+34−7

This diff is large: its 72 lines aren’t shown here.

arch/powerpc/mm/tlb_nohash_low.S+63−0

This diff is large: its 75 lines aren’t shown here.

arch/powerpc/net/bpf_jit_comp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/perf/callchain.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/perf/core-book3s.c+30−6

This diff is large: its 85 lines aren’t shown here.

arch/powerpc/perf/hv-24x7.c+164−2

This diff is large: its 195 lines aren’t shown here.

arch/powerpc/perf/power8-pmu.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/platforms/512x/Kconfig+6−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/platforms/512x/Makefile+1−0

This diff is large: its 6 lines aren’t shown here.

arch/powerpc/platforms/512x/mpc512x_lpbfifo.c+540−0

This diff is large: its 541 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_gpt.c+2−4

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/85xx/corenet_generic.c+11−0

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/platforms/85xx/mpc85xx_mds.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/85xx/mpc85xx_rdb.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/85xx/p1022_ds.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/85xx/p1022_rdk.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/85xx/smp.c+79−9

This diff is large: its 148 lines aren’t shown here.

arch/powerpc/platforms/85xx/twr_p102x.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/86xx/mpc8610_hpcd.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/Kconfig.cputype+0−11

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/cell/Kconfig+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/cell/axon_msi.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/cell/spider-pic.c+6−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/platforms/maple/Kconfig+1−1

This diff is large: its 7 lines aren’t shown here.

arch/powerpc/platforms/pasemi/Kconfig+1−1

This diff is large: its 7 lines aren’t shown here.

arch/powerpc/platforms/pasemi/msi.c+4−2

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/platforms/powermac/Kconfig+1−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/powernv/eeh-powernv.c+35−51

This diff is large: its 166 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-irqchip.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal.c+5−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/platforms/powernv/setup.c+13−8

This diff is large: its 42 lines aren’t shown here.

arch/powerpc/platforms/powernv/smp.c+24−5

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/platforms/ps3/Kconfig+1−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/ps3/os-area.c+0−5

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/platforms/pseries/Kconfig+1−6

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/platforms/pseries/Makefile+3−4

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/pseries/dlpar.c+5−26

This diff is large: its 49 lines aren’t shown here.

arch/powerpc/platforms/pseries/eeh_pseries.c+26−34

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/platforms/pseries/hvcserver.c+1−1

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/platforms/pseries/iommu.c+0−10

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/platforms/pseries/of_helpers.c+38−0

This diff is large: its 39 lines aren’t shown here.

arch/powerpc/platforms/pseries/of_helpers.h+8−0

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/pseries/reconfig.c+2−32

This diff is large: its 48 lines aren’t shown here.

arch/powerpc/platforms/pseries/setup.c+2−16

This diff is large: its 39 lines aren’t shown here.

arch/powerpc/sysdev/axonram.c+3−2

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/sysdev/cpm_common.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/sysdev/ehv_pic.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/sysdev/fsl_msi.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/fsl_pci.c+63−25

This diff is large: its 156 lines aren’t shown here.

arch/powerpc/sysdev/i8259.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/sysdev/ipic.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/sysdev/mpc5xxx_clocks.c+1−4

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/sysdev/mpc8xx_pic.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/mpic.c+6−20

This diff is large: its 62 lines aren’t shown here.

arch/powerpc/sysdev/mpic_msi.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/msi_bitmap.c+13−5

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/sysdev/qe_lib/qe_ic.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/xmon/nonstdio.c+62−2

This diff is large: its 80 lines aren’t shown here.

arch/powerpc/xmon/nonstdio.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/xmon/xmon.c+75−4

This diff is large: its 155 lines aren’t shown here.

arch/s390/Kconfig+3−0

This diff is large: its 24 lines aren’t shown here.

arch/s390/boot/compressed/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/configs/default_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/configs/gcov_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/configs/performance_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/crypto/sha.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/hypfs/hypfs_diag.c+9−1

This diff is large: its 38 lines aren’t shown here.

arch/s390/hypfs/hypfs_diag0c.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/s390/hypfs/hypfs_sprp.c+8−1

This diff is large: its 30 lines aren’t shown here.

arch/s390/hypfs/hypfs_vm.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/s390/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/s390/include/asm/appldata.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/s390/include/asm/atomic.h+0−2

This diff is large: its 16 lines aren’t shown here.

arch/s390/include/asm/barrier.h+4−4

This diff is large: its 15 lines aren’t shown here.

arch/s390/include/asm/bitops.h+34−21

This diff is large: its 94 lines aren’t shown here.

arch/s390/include/asm/cio.h+11−0

This diff is large: its 31 lines aren’t shown here.

arch/s390/include/asm/cmb.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/s390/include/asm/cmpxchg.h+3−27

This diff is large: its 58 lines aren’t shown here.

arch/s390/include/asm/cpu_mf.h+0−5

This diff is large: its 16 lines aren’t shown here.

arch/s390/include/asm/ctl_reg.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/s390/include/asm/diag.h+29−0

This diff is large: its 43 lines aren’t shown here.

arch/s390/include/asm/elf.h+10−3

This diff is large: its 20 lines aren’t shown here.

arch/s390/include/asm/etr.h+6−4

This diff is large: its 23 lines aren’t shown here.

arch/s390/include/asm/fpu/api.h+30−0

This diff is large: its 31 lines aren’t shown here.

arch/s390/include/asm/fpu/internal.hrenamed from arch/s390/include/asm/fpu-internal.h+4−47

This diff is large: its 83 lines aren’t shown here.

arch/s390/include/asm/fpu/types.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/s390/include/asm/idle.h+2−0

This diff is large: its 7 lines aren’t shown here.

arch/s390/include/asm/ipl.h+2−1

This diff is large: its 10 lines aren’t shown here.

arch/s390/include/asm/irq.h+13−1

This diff is large: its 28 lines aren’t shown here.

arch/s390/include/asm/kvm_host.h+3−1

This diff is large: its 17 lines aren’t shown here.

arch/s390/include/asm/kvm_para.h+58−9

This diff is large: its 125 lines aren’t shown here.

arch/s390/include/asm/lowcore.h+9−2

This diff is large: its 25 lines aren’t shown here.

arch/s390/include/asm/nmi.h+55−43

This diff is large: its 112 lines aren’t shown here.

arch/s390/include/asm/numa.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/include/asm/pci.h+4−0

This diff is large: its 18 lines aren’t shown here.

arch/s390/include/asm/pci_dma.h+5−0

This diff is large: its 11 lines aren’t shown here.

arch/s390/include/asm/pgtable.h+60−6

This diff is large: its 125 lines aren’t shown here.

arch/s390/include/asm/processor.h+32−67

This diff is large: its 168 lines aren’t shown here.

arch/s390/include/asm/ptrace.h+6−5

This diff is large: its 38 lines aren’t shown here.

arch/s390/include/asm/setup.h+27−23

This diff is large: its 69 lines aren’t shown here.

arch/s390/include/asm/spinlock.h+0−3

This diff is large: its 24 lines aren’t shown here.

arch/s390/include/asm/switch_to.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/include/asm/thread_info.h+12−10

This diff is large: its 36 lines aren’t shown here.

arch/s390/include/asm/topology.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/include/asm/trace/diag.h+43−0

This diff is large: its 44 lines aren’t shown here.

arch/s390/include/uapi/asm/unistd.h+10−9

This diff is large: its 33 lines aren’t shown here.

arch/s390/kernel/Makefile+2−0

This diff is large: its 9 lines aren’t shown here.

arch/s390/kernel/asm-offsets.c+149−140

This diff is large: its 311 lines aren’t shown here.

arch/s390/kernel/compat_signal.c+3−4

This diff is large: its 28 lines aren’t shown here.

arch/s390/kernel/compat_wrapper.c+1−0

This diff is large: its 5 lines aren’t shown here.

arch/s390/kernel/cpcmd.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/s390/kernel/crash_dump.c+4−12

This diff is large: its 37 lines aren’t shown here.

arch/s390/kernel/diag.c+133−1

This diff is large: its 160 lines aren’t shown here.

arch/s390/kernel/early.c+14−1

This diff is large: its 45 lines aren’t shown here.

arch/s390/kernel/entry.S+124−136

This diff is large: its 565 lines aren’t shown here.

arch/s390/kernel/entry.h+0−3

This diff is large: its 14 lines aren’t shown here.

arch/s390/kernel/head.S+12−83

This diff is large: its 144 lines aren’t shown here.

arch/s390/kernel/head64.S+6−1

This diff is large: its 14 lines aren’t shown here.

arch/s390/kernel/ipl.c+50−24

This diff is large: its 191 lines aren’t shown here.

arch/s390/kernel/irq.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/s390/kernel/nmi.c+61−59

This diff is large: its 299 lines aren’t shown here.

arch/s390/kernel/perf_cpum_cf.c+30−5

This diff is large: its 92 lines aren’t shown here.

arch/s390/kernel/perf_cpum_sf.c+6−4

This diff is large: its 18 lines aren’t shown here.

arch/s390/kernel/process.c+20−23

This diff is large: its 94 lines aren’t shown here.

arch/s390/kernel/processor.c+4−1

This diff is large: its 20 lines aren’t shown here.

arch/s390/kernel/ptrace.c+19−33

This diff is large: its 131 lines aren’t shown here.

arch/s390/kernel/runtime_instr.c+3−61

This diff is large: its 109 lines aren’t shown here.

arch/s390/kernel/s390_ksyms.c+1−2

This diff is large: its 16 lines aren’t shown here.

arch/s390/kernel/sclp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/kernel/setup.c+0−3

This diff is large: its 10 lines aren’t shown here.

arch/s390/kernel/signal.c+3−4

This diff is large: its 28 lines aren’t shown here.

arch/s390/kernel/smp.c+8−2

This diff is large: its 34 lines aren’t shown here.

arch/s390/kernel/syscalls.S+1−0

This diff is large: its 5 lines aren’t shown here.

arch/s390/kernel/time.c+21−10

This diff is large: its 79 lines aren’t shown here.

arch/s390/kernel/topology.c+16−12

This diff is large: its 57 lines aren’t shown here.

arch/s390/kernel/trace.c+29−0

This diff is large: its 30 lines aren’t shown here.

arch/s390/kernel/traps.c+1−40

This diff is large: its 69 lines aren’t shown here.

arch/s390/kernel/vdso.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/kernel/vtime.c+37−29

This diff is large: its 102 lines aren’t shown here.

arch/s390/kvm/intercept.c+21−21

This diff is large: its 50 lines aren’t shown here.

arch/s390/kvm/interrupt.c+43−73

This diff is large: its 222 lines aren’t shown here.

arch/s390/kvm/kvm-s390.c+27−37

This diff is large: its 145 lines aren’t shown here.

arch/s390/kvm/kvm-s390.h+31−4

This diff is large: its 70 lines aren’t shown here.

arch/s390/kvm/priv.c+3−16

This diff is large: its 35 lines aren’t shown here.

arch/s390/lib/delay.c+14−16

This diff is large: its 50 lines aren’t shown here.

arch/s390/lib/find.c+1−3

This diff is large: its 12 lines aren’t shown here.

arch/s390/lib/spinlock.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/s390/mm/extmem.c+3−0

This diff is large: its 24 lines aren’t shown here.

arch/s390/mm/fault.c+5−2

This diff is large: its 42 lines aren’t shown here.

arch/s390/mm/hugetlbpage.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/s390/mm/init.c+3−27

This diff is large: its 41 lines aren’t shown here.

arch/s390/mm/mmap.c+9−51

This diff is large: its 114 lines aren’t shown here.

arch/s390/net/bpf_jit_comp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/numa/mode_emu.c+10−4

This diff is large: its 36 lines aren’t shown here.

arch/s390/numa/numa.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/s390/pci/pci_dma.c+76−35

This diff is large: its 255 lines aren’t shown here.

arch/s390/pci/pci_insn.c+3−3

This diff is large: its 15 lines aren’t shown here.

arch/score/include/asm/Kbuild+1−0

This diff is large: its 5 lines aren’t shown here.

arch/sh/boards/mach-rsk/setup.c+0−3

This diff is large: its 17 lines aren’t shown here.

arch/sh/include/asm/atomic.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/sh/include/asm/page.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/sh/kernel/cpu/sh5/unwind.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/sh/kernel/traps_64.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/sparc/crypto/aes_glue.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/sparc/crypto/camellia_glue.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/sparc/crypto/des_glue.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/sparc/include/asm/atomic_64.h+4−4

This diff is large: its 16 lines aren’t shown here.

arch/sparc/include/asm/topology_64.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/sparc/include/uapi/asm/asi.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/sparc/include/uapi/asm/mman.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/sparc/include/uapi/asm/unistd.h+2−1

This diff is large: its 11 lines aren’t shown here.

arch/sparc/kernel/iommu.c+6−6

This diff is large: its 54 lines aren’t shown here.

arch/sparc/kernel/ldc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/sparc/kernel/pci.c+6−1

This diff is large: its 22 lines aren’t shown here.

arch/sparc/kernel/pci_common.c+15−2

This diff is large: its 46 lines aren’t shown here.

arch/sparc/kernel/pci_impl.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/sparc/kernel/pci_sun4v.c+9−9

This diff is large: its 81 lines aren’t shown here.

arch/sparc/kernel/perf_event.c+25−7

This diff is large: its 78 lines aren’t shown here.

arch/sparc/kernel/systbls_32.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/sparc/kernel/systbls_64.S+2−2

This diff is large: its 15 lines aren’t shown here.

arch/sparc/kernel/unaligned_64.c+15−7

This diff is large: its 47 lines aren’t shown here.

arch/sparc/lib/VISsave.S+5−5

This diff is large: its 34 lines aren’t shown here.

arch/sparc/mm/init_64.c+69−1

This diff is large: its 100 lines aren’t shown here.

arch/sparc/net/bpf_jit_comp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/tile/gxio/mpipe.c+4−29

This diff is large: its 68 lines aren’t shown here.

arch/tile/include/asm/atomic.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/tile/include/asm/atomic_64.h+3−3

This diff is large: its 20 lines aren’t shown here.

arch/tile/include/asm/highmem.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/tile/include/asm/word-at-a-time.h+7−1

This diff is large: its 20 lines aren’t shown here.

arch/tile/include/uapi/asm/mman.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/tile/kernel/usb.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/tile/mm/highmem.c+0−12

This diff is large: its 16 lines aren’t shown here.

arch/um/Makefile+3−3

This diff is large: its 20 lines aren’t shown here.

arch/um/drivers/net_kern.c+9−8

This diff is large: its 64 lines aren’t shown here.

arch/um/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/um/include/asm/ptrace-generic.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/um/include/shared/os.h+14−5

This diff is large: its 61 lines aren’t shown here.

arch/um/include/shared/skas/stub-data.h+4−3

This diff is large: its 22 lines aren’t shown here.

arch/um/include/shared/timer-internal.h+13−0

This diff is large: its 14 lines aren’t shown here.

arch/um/kernel/process.c+4−4

This diff is large: its 28 lines aren’t shown here.

arch/um/kernel/skas/clone.c+1−5

This diff is large: its 18 lines aren’t shown here.

arch/um/kernel/skas/mmu.c+3−0

This diff is large: its 19 lines aren’t shown here.

arch/um/kernel/skas/syscall.c+6−15

This diff is large: its 36 lines aren’t shown here.

arch/um/kernel/time.c+48−25

This diff is large: its 154 lines aren’t shown here.

arch/um/kernel/tlb.c+15−1

This diff is large: its 38 lines aren’t shown here.

arch/um/kernel/trap.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/um/os-Linux/helper.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/um/os-Linux/internal.h+0−1

This diff is large: its 2 lines aren’t shown here.

arch/um/os-Linux/main.c+4−3

This diff is large: its 23 lines aren’t shown here.

arch/um/os-Linux/process.c+6−0

This diff is large: its 18 lines aren’t shown here.

arch/um/os-Linux/signal.c+22−19

This diff is large: its 127 lines aren’t shown here.

arch/um/os-Linux/skas/process.c+17−38

This diff is large: its 135 lines aren’t shown here.

arch/um/os-Linux/time.c+126−123

This diff is large: its 309 lines aren’t shown here.

arch/unicore32/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/unicore32/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/unicore32/kernel/puv3-nb0916.c+8−2

This diff is large: its 34 lines aren’t shown here.

arch/x86/Kconfig+53−19

This diff is large: its 101 lines aren’t shown here.

arch/x86/Kconfig.cpu+17−7

This diff is large: its 56 lines aren’t shown here.

arch/x86/Kconfig.debug+34−1

This diff is large: its 60 lines aren’t shown here.

arch/x86/Makefile+10−2

This diff is large: its 26 lines aren’t shown here.

arch/x86/boot/Makefile+2−2

This diff is large: its 16 lines aren’t shown here.

arch/x86/boot/compressed/eboot.c+26−6

This diff is large: its 116 lines aren’t shown here.

arch/x86/boot/header.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/crypto/Makefile+8−0

This diff is large: its 25 lines aren’t shown here.

arch/x86/crypto/camellia_aesni_avx2_glue.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/x86/crypto/camellia_aesni_avx_glue.c+7−1

This diff is large: its 15 lines aren’t shown here.

arch/x86/crypto/cast5_avx_glue.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/x86/crypto/cast6_avx_glue.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/x86/crypto/chacha20_glue.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/crypto/crc32c-pcl-intel-asm_64.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/crypto/poly1305_glue.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/crypto/serpent_avx2_glue.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/x86/crypto/serpent_avx_glue.c+2−1

This diff is large: its 10 lines aren’t shown here.

arch/x86/crypto/sha1_ni_asm.S+302−0

This diff is large: its 303 lines aren’t shown here.

arch/x86/crypto/sha1_ssse3_glue.c+251−65

This diff is large: its 399 lines aren’t shown here.

arch/x86/crypto/sha256_ni_asm.S+353−0

This diff is large: its 354 lines aren’t shown here.

arch/x86/crypto/sha256_ssse3_glue.c+285−46

This diff is large: its 400 lines aren’t shown here.

arch/x86/crypto/sha512_ssse3_glue.c+205−46

This diff is large: its 320 lines aren’t shown here.

arch/x86/crypto/twofish_avx_glue.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/entry/common.c+216−48

This diff is large: its 343 lines aren’t shown here.

arch/x86/entry/entry_32.S+60−122

This diff is large: its 253 lines aren’t shown here.

arch/x86/entry/entry_64.S+2−7

This diff is large: its 39 lines aren’t shown here.

arch/x86/entry/entry_64_compat.S+134−413

This diff is large: its 652 lines aren’t shown here.

arch/x86/entry/syscall_32.c+3−6

This diff is large: its 28 lines aren’t shown here.

arch/x86/entry/syscall_64.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/x86/entry/syscalls/syscall_32.tbl+7−6

This diff is large: its 59 lines aren’t shown here.

arch/x86/entry/syscalls/syscall_64.tbl+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/entry/vdso/Makefile+13−26

This diff is large: its 81 lines aren’t shown here.

arch/x86/entry/vdso/vdso2c.c+1−1

This diff is large: its 12 lines aren’t shown here.

arch/x86/entry/vdso/vdso32-setup.c+1−27

This diff is large: its 37 lines aren’t shown here.

arch/x86/entry/vdso/vdso32/int80.S+0−56

This diff is large: its 57 lines aren’t shown here.

arch/x86/entry/vdso/vdso32/syscall.S+0−75

This diff is large: its 76 lines aren’t shown here.

arch/x86/entry/vdso/vdso32/sysenter.S+0−116

This diff is large: its 117 lines aren’t shown here.

arch/x86/entry/vdso/vdso32/system_call.S+57−0

This diff is large: its 58 lines aren’t shown here.

arch/x86/entry/vdso/vdso32/vclock_gettime.c+2−0

This diff is large: its 14 lines aren’t shown here.

arch/x86/entry/vdso/vma.c+1−12

This diff is large: its 23 lines aren’t shown here.

arch/x86/entry/vsyscall/vsyscall_64.c+8−1

This diff is large: its 16 lines aren’t shown here.

arch/x86/ia32/ia32_signal.c+6−6

This diff is large: its 54 lines aren’t shown here.

arch/x86/include/asm/acpi.h+23−0

This diff is large: its 35 lines aren’t shown here.

arch/x86/include/asm/amd_nb.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/asm/apic.h+55−55

This diff is large: its 130 lines aren’t shown here.

arch/x86/include/asm/atomic.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/x86/include/asm/atomic64_64.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/x86/include/asm/cpufeature.h+5−2

This diff is large: its 28 lines aren’t shown here.

arch/x86/include/asm/dwarf2.h+84−0

This diff is large: its 85 lines aren’t shown here.

arch/x86/include/asm/efi.h+3−0

This diff is large: its 24 lines aren’t shown here.

arch/x86/include/asm/elf.h+5−5

This diff is large: its 25 lines aren’t shown here.

arch/x86/include/asm/fpu/signal.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/asm/fpu/types.h+103−45

This diff is large: its 198 lines aren’t shown here.

arch/x86/include/asm/fpu/xstate.h+10−5

This diff is large: its 40 lines aren’t shown here.

arch/x86/include/asm/highmem.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/x86/include/asm/hpet.h+3−3

This diff is large: its 14 lines aren’t shown here.

arch/x86/include/asm/i8259.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/include/asm/ia32.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/x86/include/asm/irq_remapping.h+5−5

This diff is large: its 24 lines aren’t shown here.

arch/x86/include/asm/kdebug.h+0−6

This diff is large: its 12 lines aren’t shown here.

arch/x86/include/asm/kvm_emulate.h+10−0

This diff is large: its 17 lines aren’t shown here.

arch/x86/include/asm/kvm_host.h+48−23

This diff is large: its 191 lines aren’t shown here.

arch/x86/include/asm/mce.h+21−13

This diff is large: its 41 lines aren’t shown here.

arch/x86/include/asm/microcode.h+13−13

This diff is large: its 59 lines aren’t shown here.

arch/x86/include/asm/microcode_amd.h+2−1

This diff is large: its 15 lines aren’t shown here.

arch/x86/include/asm/microcode_intel.h+3−7

This diff is large: its 25 lines aren’t shown here.

arch/x86/include/asm/msr-index.h+10−2

This diff is large: its 40 lines aren’t shown here.

arch/x86/include/asm/numachip/numachip.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/include/asm/numachip/numachip_csr.h+42−111

This diff is large: its 195 lines aren’t shown here.

arch/x86/include/asm/page_64_types.h+0−3

This diff is large: its 10 lines aren’t shown here.

arch/x86/include/asm/page_types.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/x86/include/asm/pgtable.h+28−7

This diff is large: its 93 lines aren’t shown here.

arch/x86/include/asm/pgtable_types.h+36−4

This diff is large: its 62 lines aren’t shown here.

arch/x86/include/asm/preempt.h+1−4

This diff is large: its 14 lines aren’t shown here.

arch/x86/include/asm/processor.h+3−3

This diff is large: its 24 lines aren’t shown here.

arch/x86/include/asm/pvclock-abi.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/include/asm/sigcontext.h+2−73

This diff is large: its 82 lines aren’t shown here.

arch/x86/include/asm/sigframe.h+3−5

This diff is large: its 36 lines aren’t shown here.

arch/x86/include/asm/signal.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/asm/string_64.h+2−3

This diff is large: its 15 lines aren’t shown here.

arch/x86/include/asm/switch_to.h+8−4

This diff is large: its 29 lines aren’t shown here.

arch/x86/include/asm/syscall.h+13−1

This diff is large: its 23 lines aren’t shown here.

arch/x86/include/asm/thread_info.h+0−3

This diff is large: its 18 lines aren’t shown here.

arch/x86/include/asm/trace/mpx.h+4−3

This diff is large: its 28 lines aren’t shown here.

arch/x86/include/asm/uaccess.h+7−7

This diff is large: its 53 lines aren’t shown here.

arch/x86/include/asm/uv/uv_hub.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/asm/vdso.h+2−8

This diff is large: its 24 lines aren’t shown here.

arch/x86/include/asm/vmx.h+5−1

This diff is large: its 27 lines aren’t shown here.

arch/x86/include/asm/xen/hypercall.h+2−2

This diff is large: its 13 lines aren’t shown here.

arch/x86/include/asm/xen/hypervisor.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/x86/include/asm/xen/page.h+5−3

This diff is large: its 29 lines aren’t shown here.

arch/x86/include/uapi/asm/bitsperlong.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/uapi/asm/hyperv.h+18−0

This diff is large: its 30 lines aren’t shown here.

arch/x86/include/uapi/asm/mce.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/include/uapi/asm/sigcontext.h+307−168

This diff is large: its 529 lines aren’t shown here.

arch/x86/include/uapi/asm/sigcontext32.h+2−71

This diff is large: its 80 lines aren’t shown here.

arch/x86/include/uapi/asm/svm.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/include/uapi/asm/vmx.h+3−1

This diff is large: its 18 lines aren’t shown here.

arch/x86/kernel/acpi/boot.c+18−4

This diff is large: its 36 lines aren’t shown here.

arch/x86/kernel/apic/apic.c+4−4

This diff is large: its 36 lines aren’t shown here.

arch/x86/kernel/apic/apic_numachip.c+160−60

This diff is large: its 317 lines aren’t shown here.

arch/x86/kernel/apic/io_apic.c+8−2

This diff is large: its 43 lines aren’t shown here.

arch/x86/kernel/apic/vector.c+5−1

This diff is large: its 13 lines aren’t shown here.

arch/x86/kernel/asm-offsets.c+9−12

This diff is large: its 28 lines aren’t shown here.

arch/x86/kernel/cpu/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/kernel/cpu/amd.c+13−0

This diff is large: its 27 lines aren’t shown here.

arch/x86/kernel/cpu/common.c+2−2

This diff is large: its 20 lines aren’t shown here.

arch/x86/kernel/cpu/intel.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/kernel/cpu/intel_cacheinfo.c+4−4

This diff is large: its 29 lines aren’t shown here.

arch/x86/kernel/cpu/mcheck/mce.c+24−10

This diff is large: its 84 lines aren’t shown here.

arch/x86/kernel/cpu/mcheck/therm_throt.c+0−8

This diff is large: its 15 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/Makefile+0−3

This diff is large: its 7 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/amd.c+492−17

This diff is large: its 579 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/amd_early.c+0−440

This diff is large: its 441 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/core.c+169−63

This diff is large: its 295 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/core_early.c+0−170

This diff is large: its 171 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/intel.c+784−7

This diff is large: its 820 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/intel_early.c+0−808

This diff is large: its 809 lines aren’t shown here.

arch/x86/kernel/cpu/microcode/intel_lib.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/x86/kernel/cpu/mshyperv.c+7−5

This diff is large: its 45 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event.c+33−6

This diff is large: its 84 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event.h+2−1

This diff is large: its 17 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel.c+15−2

This diff is large: its 52 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_bts.c+13−0

This diff is large: its 20 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_cstate.c+694−0

This diff is large: its 695 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_ds.c+34−6

This diff is large: its 74 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_lbr.c+6−2

This diff is large: its 38 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_pt.c+4−3

This diff is large: its 21 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_rapl.c+0−6

This diff is large: its 13 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_uncore.c+58−3

This diff is large: its 91 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_uncore.h+11−1

This diff is large: its 26 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_uncore_snb.c+13−3

This diff is large: its 29 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_intel_uncore_snbep.c+25−9

This diff is large: its 72 lines aren’t shown here.

arch/x86/kernel/cpu/perf_event_msr.c+5−6

This diff is large: its 29 lines aren’t shown here.

arch/x86/kernel/cpu/scattered.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/kernel/crash.c+3−7

This diff is large: its 39 lines aren’t shown here.

arch/x86/kernel/e820.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/kernel/early-quirks.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/kernel/early_printk.c+3−3

This diff is large: its 26 lines aren’t shown here.

arch/x86/kernel/fpu/init.c+4−14

This diff is large: its 34 lines aren’t shown here.

arch/x86/kernel/fpu/regset.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/x86/kernel/fpu/signal.c+10−11

This diff is large: its 71 lines aren’t shown here.

arch/x86/kernel/fpu/xstate.c+345−54

This diff is large: its 534 lines aren’t shown here.

arch/x86/kernel/ftrace.c+4−0

This diff is large: its 30 lines aren’t shown here.

arch/x86/kernel/head_32.S+2−3

This diff is large: its 23 lines aren’t shown here.

arch/x86/kernel/head_64.S+8−0

This diff is large: its 29 lines aren’t shown here.

arch/x86/kernel/hpet.c+14−15

This diff is large: its 96 lines aren’t shown here.

arch/x86/kernel/i8259.c+21−8

This diff is large: its 76 lines aren’t shown here.

arch/x86/kernel/irq_64.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/kernel/kgdb.c+11−6

This diff is large: its 38 lines aren’t shown here.

arch/x86/kernel/kvmclock.c+35−11

This diff is large: its 74 lines aren’t shown here.

arch/x86/kernel/livepatch.c+5−4

This diff is large: its 24 lines aren’t shown here.

arch/x86/kernel/mcount_64.S+6−0

This diff is large: its 13 lines aren’t shown here.

arch/x86/kernel/pci-dma.c+4−3

This diff is large: its 24 lines aren’t shown here.

arch/x86/kernel/process.c+58−0

This diff is large: its 69 lines aren’t shown here.

arch/x86/kernel/process_32.c+0−36

This diff is large: its 47 lines aren’t shown here.

arch/x86/kernel/process_64.c+1−33

This diff is large: its 55 lines aren’t shown here.

arch/x86/kernel/quirks.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/kernel/setup.c+66−48

This diff is large: its 223 lines aren’t shown here.

arch/x86/kernel/signal.c+6−4

This diff is large: its 45 lines aren’t shown here.

arch/x86/kernel/smpboot.c+11−4

This diff is large: its 49 lines aren’t shown here.

arch/x86/kernel/traps.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/x86/kernel/tsc.c+22−13

This diff is large: its 72 lines aren’t shown here.

arch/x86/kernel/verify_cpu.S+7−5

This diff is large: its 36 lines aren’t shown here.

arch/x86/kvm/Kconfig+2−0

This diff is large: its 9 lines aren’t shown here.

arch/x86/kvm/assigned-dev.c+37−25

This diff is large: its 189 lines aren’t shown here.

arch/x86/kvm/cpuid.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/x86/kvm/cpuid.h+37−0

This diff is large: its 42 lines aren’t shown here.

arch/x86/kvm/emulate.c+34−11

This diff is large: its 91 lines aren’t shown here.

arch/x86/kvm/hyperv.c+29−2

This diff is large: its 80 lines aren’t shown here.

arch/x86/kvm/i8254.c+3−1

This diff is large: its 18 lines aren’t shown here.

arch/x86/kvm/ioapic.c+6−23

This diff is large: its 75 lines aren’t shown here.

arch/x86/kvm/ioapic.h+8−7

This diff is large: its 43 lines aren’t shown here.

arch/x86/kvm/irq.c+30−10

This diff is large: its 86 lines aren’t shown here.

arch/x86/kvm/irq.h+26−1

This diff is large: its 40 lines aren’t shown here.

arch/x86/kvm/irq_comm.c+88−41

This diff is large: its 179 lines aren’t shown here.

arch/x86/kvm/lapic.c+106−25

This diff is large: its 239 lines aren’t shown here.

arch/x86/kvm/lapic.h+4−3

This diff is large: its 27 lines aren’t shown here.

arch/x86/kvm/mmu.c+58−53

This diff is large: its 251 lines aren’t shown here.

arch/x86/kvm/mmu.h+3−3

This diff is large: its 25 lines aren’t shown here.

arch/x86/kvm/paging_tmpl.h+10−12

This diff is large: its 42 lines aren’t shown here.

arch/x86/kvm/svm.c+54−252

This diff is large: its 567 lines aren’t shown here.

arch/x86/kvm/trace.h+51−0

This diff is large: its 65 lines aren’t shown here.

arch/x86/kvm/vmx.c+656−200

This diff is large: its 1591 lines aren’t shown here.

arch/x86/kvm/x86.c+422−157

This diff is large: its 1148 lines aren’t shown here.

arch/x86/kvm/x86.h+3−3

This diff is large: its 13 lines aren’t shown here.

arch/x86/lib/x86-opcode-map.txt+19−5

This diff is large: its 66 lines aren’t shown here.

arch/x86/math-emu/fpu_aux.c+70−0

This diff is large: its 77 lines aren’t shown here.

arch/x86/math-emu/fpu_emu.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/math-emu/fpu_entry.c+31−65

This diff is large: its 118 lines aren’t shown here.

arch/x86/math-emu/fpu_proto.h+12−0

This diff is large: its 26 lines aren’t shown here.

arch/x86/math-emu/load_store.c+51−12

This diff is large: its 121 lines aren’t shown here.

arch/x86/math-emu/reg_compare.c+128−0

This diff is large: its 146 lines aren’t shown here.

arch/x86/mm/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/mm/dump_pagetables.c+78−20

This diff is large: its 224 lines aren’t shown here.

arch/x86/mm/gup.c+8−10

This diff is large: its 52 lines aren’t shown here.

arch/x86/mm/highmem_32.c+0−14

This diff is large: its 21 lines aren’t shown here.

arch/x86/mm/init.c+2−4

This diff is large: its 33 lines aren’t shown here.

arch/x86/mm/init_32.c+2−0

This diff is large: its 9 lines aren’t shown here.

arch/x86/mm/init_64.c+5−3

This diff is large: its 36 lines aren’t shown here.

arch/x86/mm/kasan_init_64.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/x86/mm/mpx.c+49−13

This diff is large: its 125 lines aren’t shown here.

arch/x86/mm/pageattr.c+56−32

This diff is large: its 185 lines aren’t shown here.

arch/x86/net/bpf_jit_comp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/pci/acpi.c+88−208

This diff is large: its 397 lines aren’t shown here.

arch/x86/pci/common.c+8−0

This diff is large: its 15 lines aren’t shown here.

arch/x86/pci/legacy.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/platform/efi/efi-bgrt.c+7−2

This diff is large: its 19 lines aren’t shown here.

arch/x86/platform/efi/efi.c+70−25

This diff is large: its 151 lines aren’t shown here.

arch/x86/platform/intel-mid/intel-mid.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/platform/intel-mid/sfi.c+1−2

This diff is large: its 12 lines aren’t shown here.

arch/x86/platform/uv/uv_nmi.c+30−23

This diff is large: its 132 lines aren’t shown here.

arch/x86/ras/Kconfig+1−3

This diff is large: its 13 lines aren’t shown here.

arch/x86/ras/mce_amd_inj.c+96−7

This diff is large: its 173 lines aren’t shown here.

arch/x86/um/asm/syscall.h+4−0

This diff is large: its 11 lines aren’t shown here.

arch/x86/um/ldt.c+4−1

This diff is large: its 12 lines aren’t shown here.

arch/x86/um/stub_32.S+0−1

This diff is large: its 7 lines aren’t shown here.

arch/x86/um/stub_64.S+1−17

This diff is large: its 27 lines aren’t shown here.

arch/x86/um/sys_call_table_32.c+3−4

This diff is large: its 26 lines aren’t shown here.

arch/x86/um/sys_call_table_64.c+3−4

This diff is large: its 26 lines aren’t shown here.

arch/x86/xen/enlighten.c+39−0

This diff is large: its 78 lines aren’t shown here.

arch/x86/xen/grant-table.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/x86/xen/mmu.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/x86/xen/p2m.c+31−7

This diff is large: its 109 lines aren’t shown here.

arch/x86/xen/setup.c+10−16

This diff is large: its 70 lines aren’t shown here.

arch/xtensa/Kconfig+16−1

This diff is large: its 38 lines aren’t shown here.

arch/xtensa/Makefile+4−0

This diff is large: its 11 lines aren’t shown here.

arch/xtensa/boot/boot-elf/boot.lds.S+0−13

This diff is large: its 18 lines aren’t shown here.

arch/xtensa/boot/boot-elf/bootstrap.S+0−28

This diff is large: its 39 lines aren’t shown here.

arch/xtensa/boot/dts/Makefile+6−1

This diff is large: its 11 lines aren’t shown here.

arch/xtensa/boot/dts/kc705_nommu.dts+17−0

This diff is large: its 18 lines aren’t shown here.

arch/xtensa/configs/iss_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/xtensa/configs/nommu_kc705_defconfig+131−0

This diff is large: its 132 lines aren’t shown here.

arch/xtensa/include/asm/Kbuild+1−0

This diff is large: its 6 lines aren’t shown here.

arch/xtensa/include/asm/asmmacro.h+4−3

This diff is large: its 22 lines aren’t shown here.

arch/xtensa/include/asm/atomic.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/xtensa/include/asm/cacheasm.h+26−0

This diff is large: its 122 lines aren’t shown here.

arch/xtensa/include/asm/cacheflush.h+8−98

This diff is large: its 118 lines aren’t shown here.

arch/xtensa/include/asm/dma-mapping.h+10−0

This diff is large: its 15 lines aren’t shown here.

arch/xtensa/include/asm/initialize_mmu.h+9−4

This diff is large: its 32 lines aren’t shown here.

arch/xtensa/include/asm/io.h+0−9

This diff is large: its 16 lines aren’t shown here.

arch/xtensa/include/asm/pgtable.h+4−0

This diff is large: its 12 lines aren’t shown here.

arch/xtensa/include/asm/vectors.h+19−9

This diff is large: its 62 lines aren’t shown here.

arch/xtensa/include/uapi/asm/mman.h+6−0

This diff is large: its 13 lines aren’t shown here.

arch/xtensa/kernel/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/xtensa/kernel/entry.S+6−2

This diff is large: its 41 lines aren’t shown here.

arch/xtensa/kernel/head.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/xtensa/kernel/mxhead.S+0−23

This diff is large: its 34 lines aren’t shown here.

arch/xtensa/kernel/pci-dma.c+31−14

This diff is large: its 86 lines aren’t shown here.

arch/xtensa/kernel/setup.c+9−2

This diff is large: its 32 lines aren’t shown here.

arch/xtensa/kernel/time.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/xtensa/kernel/vectors.S+3−1

This diff is large: its 18 lines aren’t shown here.

arch/xtensa/kernel/vmlinux.lds.S+2−35

This diff is large: its 61 lines aren’t shown here.

arch/xtensa/lib/usercopy.S+3−3

This diff is large: its 20 lines aren’t shown here.

arch/xtensa/platforms/iss/setup.c+2−0

This diff is large: its 10 lines aren’t shown here.

arch/xtensa/platforms/iss/simdisk.c+2−1

This diff is large: its 17 lines aren’t shown here.

arch/xtensa/platforms/xt2000/setup.c+2−0

This diff is large: its 10 lines aren’t shown here.

arch/xtensa/platforms/xtfpga/include/platform/hardware.h+4−2

This diff is large: its 18 lines aren’t shown here.

arch/xtensa/platforms/xtfpga/setup.c+2−0

This diff is large: its 10 lines aren’t shown here.

arch/xtensa/variants/de212/include/variant/core.h+594−0

This diff is large: its 595 lines aren’t shown here.

arch/xtensa/variants/de212/include/variant/tie-asm.h+170−0

This diff is large: its 171 lines aren’t shown here.

arch/xtensa/variants/de212/include/variant/tie.h+136−0

This diff is large: its 137 lines aren’t shown here.

block/bio-integrity.c+11−6

This diff is large: its 62 lines aren’t shown here.

block/bio.c+13−13

This diff is large: its 60 lines aren’t shown here.

block/blk-cgroup.c+1−0

This diff is large: its 8 lines aren’t shown here.

block/blk-core.c+161−29

This diff is large: its 350 lines aren’t shown here.

block/blk-integrity.c+86−106

This diff is large: its 304 lines aren’t shown here.

block/blk-ioc.c+1−1

This diff is large: its 9 lines aren’t shown here.

block/blk-lib.c+22−9

This diff is large: its 67 lines aren’t shown here.

block/blk-merge.c+25−7

This diff is large: its 81 lines aren’t shown here.

block/blk-mq-cpumap.c+5−4

This diff is large: its 37 lines aren’t shown here.

block/blk-mq-sysfs.c+32−18

This diff is large: its 156 lines aren’t shown here.

block/blk-mq-tag.c+26−8

This diff is large: its 66 lines aren’t shown here.

block/blk-mq-tag.h+2−0

This diff is large: its 9 lines aren’t shown here.

block/blk-mq.c+203−153

This diff is large: its 784 lines aren’t shown here.

block/blk-mq.h+2−4

This diff is large: its 23 lines aren’t shown here.

block/blk-sysfs.c+37−2

This diff is large: its 75 lines aren’t shown here.

block/blk-throttle.c+1−1

This diff is large: its 9 lines aren’t shown here.

block/blk.h+21−0

This diff is large: its 35 lines aren’t shown here.

block/cfq-iosched.c+2−2

This diff is large: its 18 lines aren’t shown here.

block/elevator.c+1−1

This diff is large: its 9 lines aren’t shown here.

block/genhd.c+2−0

This diff is large: its 16 lines aren’t shown here.

block/ioctl.c+230−100

This diff is large: its 401 lines aren’t shown here.

block/ioprio.c+4−2

This diff is large: its 20 lines aren’t shown here.

block/partition-generic.c+1−0

This diff is large: its 8 lines aren’t shown here.

block/scsi_ioctl.c+3−3

This diff is large: its 27 lines aren’t shown here.

block/t10-pi.c+4−12

This diff is large: its 43 lines aren’t shown here.

certs/.gitignore+4−0

This diff is large: its 5 lines aren’t shown here.

crypto/Kconfig+13−4

This diff is large: its 46 lines aren’t shown here.

crypto/Makefile+7−3

This diff is large: its 25 lines aren’t shown here.

crypto/ablkcipher.c+1−1

This diff is large: its 9 lines aren’t shown here.

crypto/ahash.c+2−1

This diff is large: its 10 lines aren’t shown here.

crypto/akcipher.c+0−1

This diff is large: its 8 lines aren’t shown here.

crypto/algapi.c+1−1

This diff is large: its 9 lines aren’t shown here.

crypto/algif_hash.c+10−2

This diff is large: its 28 lines aren’t shown here.

crypto/api.c+3−3

This diff is large: its 27 lines aren’t shown here.

crypto/asymmetric_keys/asymmetric_keys.h+0−5

This diff is large: its 9 lines aren’t shown here.

crypto/asymmetric_keys/asymmetric_type.c+26−18

This diff is large: its 74 lines aren’t shown here.

crypto/asymmetric_keys/pkcs7_verify.c+3−2

This diff is large: its 15 lines aren’t shown here.

crypto/asymmetric_keys/public_key.c+2−2

This diff is large: its 18 lines aren’t shown here.

crypto/asymmetric_keys/signature.c+1−1

This diff is large: its 9 lines aren’t shown here.

crypto/asymmetric_keys/x509_cert_parser.c+10−8

This diff is large: its 33 lines aren’t shown here.

crypto/asymmetric_keys/x509_parser.h+1−0

This diff is large: its 8 lines aren’t shown here.

crypto/asymmetric_keys/x509_public_key.c+8−10

This diff is large: its 52 lines aren’t shown here.

crypto/crypto_user.c+1−1

This diff is large: its 9 lines aren’t shown here.

crypto/jitterentropy-kcapi.c+0−4

This diff is large: its 11 lines aren’t shown here.

crypto/keywrap.c+419−0

This diff is large: its 420 lines aren’t shown here.

crypto/rsa.c+49−34

This diff is large: its 177 lines aren’t shown here.

crypto/rsa_helper.c+35−7

This diff is large: its 71 lines aren’t shown here.

crypto/rsakey.asn1+0−5

This diff is large: its 6 lines aren’t shown here.

crypto/rsaprivkey.asn1+11−0

This diff is large: its 12 lines aren’t shown here.

crypto/rsapubkey.asn1+4−0

This diff is large: its 5 lines aren’t shown here.

crypto/skcipher.c+2−2

This diff is large: its 18 lines aren’t shown here.

crypto/tcrypt.c+13−4

This diff is large: its 52 lines aren’t shown here.

crypto/testmgr.c+47−36

This diff is large: its 254 lines aren’t shown here.

crypto/testmgr.h+68−9

This diff is large: its 136 lines aren’t shown here.

drivers/Kconfig+10−0

This diff is large: its 29 lines aren’t shown here.

drivers/Makefile+5−0

This diff is large: its 18 lines aren’t shown here.

drivers/acpi/Kconfig+26−3

This diff is large: its 45 lines aren’t shown here.

drivers/acpi/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/acpi/acpi_lpss.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpi_pad.c+0−2

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpi_platform.c+6−1

This diff is large: its 14 lines aren’t shown here.

drivers/acpi/acpi_pnp.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/acpi/acpi_processor.c+18−0

This diff is large: its 25 lines aren’t shown here.

drivers/acpi/acpi_video.c+66−12

This diff is large: its 127 lines aren’t shown here.

drivers/acpi/acpica/Makefile+17−1

This diff is large: its 33 lines aren’t shown here.

drivers/acpi/acpica/acapps.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpica/acdebug.h+6−0

This diff is large: its 13 lines aren’t shown here.

drivers/acpi/acpica/acglobal.h+7−1

This diff is large: its 38 lines aren’t shown here.

drivers/acpi/acpica/acinterp.h+0−2

This diff is large: its 13 lines aren’t shown here.

drivers/acpi/acpica/aclocal.h+16−6

This diff is large: its 56 lines aren’t shown here.

drivers/acpi/acpica/acnamesp.h+0−4

This diff is large: its 26 lines aren’t shown here.

drivers/acpi/acpica/acopcode.h+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/acpi/acpica/acparser.h+0−4

This diff is large: its 21 lines aren’t shown here.

drivers/acpi/acpica/actables.h+1−3

This diff is large: its 18 lines aren’t shown here.

drivers/acpi/acpica/acutils.h+0−2

This diff is large: its 10 lines aren’t shown here.

drivers/acpi/acpica/amlcode.h+6−5

This diff is large: its 21 lines aren’t shown here.

drivers/acpi/acpica/dbcmds.c+1187−0

This diff is large: its 1188 lines aren’t shown here.

drivers/acpi/acpica/dbconvert.c+484−0

This diff is large: its 485 lines aren’t shown here.

drivers/acpi/acpica/dbdisply.c+1108−0

This diff is large: its 1109 lines aren’t shown here.

drivers/acpi/acpica/dbexec.c+764−0

This diff is large: its 765 lines aren’t shown here.

drivers/acpi/acpica/dbfileio.c+256−0

This diff is large: its 257 lines aren’t shown here.

drivers/acpi/acpica/dbhistry.c+239−0

This diff is large: its 240 lines aren’t shown here.

drivers/acpi/acpica/dbinput.c+1267−0

This diff is large: its 1268 lines aren’t shown here.

drivers/acpi/acpica/dbmethod.c+369−0

This diff is large: its 370 lines aren’t shown here.

drivers/acpi/acpica/dbnames.c+947−0

This diff is large: its 948 lines aren’t shown here.

drivers/acpi/acpica/dbobject.c+533−0

This diff is large: its 534 lines aren’t shown here.

drivers/acpi/acpica/dbstats.c+546−0

This diff is large: its 547 lines aren’t shown here.

drivers/acpi/acpica/dbtest.c+1057−0

This diff is large: its 1058 lines aren’t shown here.

drivers/acpi/acpica/dbutils.c+457−0

This diff is large: its 458 lines aren’t shown here.

drivers/acpi/acpica/dbxface.c+513−0

This diff is large: its 514 lines aren’t shown here.

drivers/acpi/acpica/evxface.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpica/evxfevnt.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpica/exconvrt.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/acpi/acpica/exresolv.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/acpi/acpica/exresop.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpica/exstore.c+91−29

This diff is large: its 195 lines aren’t shown here.

drivers/acpi/acpica/exstoren.c+3−2

This diff is large: its 21 lines aren’t shown here.

drivers/acpi/acpica/nsdump.c+0−6

This diff is large: its 42 lines aren’t shown here.

drivers/acpi/acpica/nspredef.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/acpica/pstree.c+0−2

This diff is large: its 13 lines aren’t shown here.

drivers/acpi/acpica/psutils.c+0−2

This diff is large: its 16 lines aren’t shown here.

drivers/acpi/acpica/rsdump.c+0−3

This diff is large: its 14 lines aren’t shown here.

drivers/acpi/acpica/rsutils.c+0−2

This diff is large: its 16 lines aren’t shown here.

drivers/acpi/acpica/rsxface.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/acpi/acpica/tbfadt.c+5−5

This diff is large: its 33 lines aren’t shown here.

drivers/acpi/acpica/tbutils.c+2−24

This diff is large: its 40 lines aren’t shown here.

drivers/acpi/acpica/utdecode.c+17−4

This diff is large: its 39 lines aren’t shown here.

drivers/acpi/acpica/utfileio.c+6−0

This diff is large: its 20 lines aren’t shown here.

drivers/acpi/acpica/utinit.c+13−2

This diff is large: its 29 lines aren’t shown here.

drivers/acpi/acpica/utmutex.c+21−0

This diff is large: its 35 lines aren’t shown here.

drivers/acpi/acpica/utxface.c+1−18

This diff is large: its 33 lines aren’t shown here.

drivers/acpi/apei/ghes.c+7−3

This diff is large: its 19 lines aren’t shown here.

drivers/acpi/cppc_acpi.c+733−0

This diff is large: its 734 lines aren’t shown here.

drivers/acpi/device_pm.c+1−18

This diff is large: its 33 lines aren’t shown here.

drivers/acpi/device_sysfs.c+108−12

This diff is large: its 150 lines aren’t shown here.

drivers/acpi/ec.c+75−40

This diff is large: its 204 lines aren’t shown here.

drivers/acpi/ec_sys.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/acpi/glue.c+7−6

This diff is large: its 38 lines aren’t shown here.

drivers/acpi/gsi.c+33−21

This diff is large: its 89 lines aren’t shown here.

drivers/acpi/internal.h+4−4

This diff is large: its 34 lines aren’t shown here.

drivers/acpi/nfit.c+246−60

This diff is large: its 522 lines aren’t shown here.

drivers/acpi/nfit.h+3−1

This diff is large: its 25 lines aren’t shown here.

drivers/acpi/osl.c+12−14

This diff is large: its 89 lines aren’t shown here.

drivers/acpi/pci_irq.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/acpi/pci_link.c+14−2

This diff is large: its 37 lines aren’t shown here.

drivers/acpi/pci_root.c+204−0

This diff is large: its 211 lines aren’t shown here.

drivers/acpi/proc.c+1−3

This diff is large: its 13 lines aren’t shown here.

drivers/acpi/processor_driver.c+6−0

This diff is large: its 20 lines aren’t shown here.

drivers/acpi/property.c+358−69

This diff is large: its 609 lines aren’t shown here.

drivers/acpi/resource.c+6−3

This diff is large: its 37 lines aren’t shown here.

drivers/acpi/sbshc.c+7−41

This diff is large: its 107 lines aren’t shown here.

drivers/acpi/scan.c+85−24

This diff is large: its 153 lines aren’t shown here.

drivers/acpi/sleep.c+7−2

This diff is large: its 36 lines aren’t shown here.

drivers/acpi/sysfs.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/acpi/tables.c+76−18

This diff is large: its 158 lines aren’t shown here.

drivers/acpi/thermal.c+6−6

This diff is large: its 48 lines aren’t shown here.

drivers/acpi/video_detect.c+18−0

This diff is large: its 32 lines aren’t shown here.

drivers/ata/Kconfig+9−0

This diff is large: its 16 lines aren’t shown here.

drivers/ata/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/ata/ahci.c+12−0

This diff is large: its 26 lines aren’t shown here.

drivers/ata/ahci.h+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/ata/ahci_platform.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/ata/ahci_qoriq.c+279−0

This diff is large: its 280 lines aren’t shown here.

drivers/ata/libahci.c+11−19

This diff is large: its 54 lines aren’t shown here.

drivers/ata/libata-scsi.c+33−29

This diff is large: its 142 lines aren’t shown here.

drivers/ata/pata_it821x.c+3−3

This diff is large: its 21 lines aren’t shown here.

drivers/ata/pata_macio.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/ata/pata_pxa.c+59−112

This diff is large: its 273 lines aren’t shown here.

drivers/ata/pata_samsung_cf.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/atm/iphase.c+3−2

This diff is large: its 19 lines aren’t shown here.

drivers/base/class.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/base/core.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/base/dd.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/base/devres.c+10−9

This diff is large: its 73 lines aren’t shown here.

drivers/base/dma-contiguous.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/base/pinctrl.c+13−2

This diff is large: its 23 lines aren’t shown here.

drivers/base/platform-msi.c+3−3

This diff is large: its 27 lines aren’t shown here.

drivers/base/platform.c+70−10

This diff is large: its 116 lines aren’t shown here.

drivers/base/power/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/base/power/clock_ops.c+7−5

This diff is large: its 47 lines aren’t shown here.

drivers/base/power/domain.c+85−306

This diff is large: its 696 lines aren’t shown here.

drivers/base/power/domain_governor.c+4−16

This diff is large: its 45 lines aren’t shown here.

drivers/base/power/generic_ops.c+20−3

This diff is large: its 39 lines aren’t shown here.

drivers/base/power/opp/Makefile+2−0

This diff is large: its 3 lines aren’t shown here.

drivers/base/power/opp/core.crenamed from drivers/base/power/opp.c+73−353

This diff is large: its 661 lines aren’t shown here.

drivers/base/power/opp/cpu.c+270−0

This diff is large: its 271 lines aren’t shown here.

drivers/base/power/opp/opp.h+146−0

This diff is large: its 147 lines aren’t shown here.

drivers/base/power/wakeirq.c+6−0

This diff is large: its 20 lines aren’t shown here.

drivers/base/power/wakeup.c+14−2

This diff is large: its 44 lines aren’t shown here.

drivers/base/property.c+100−20

This diff is large: its 179 lines aren’t shown here.

drivers/base/regmap/internal.h+6−3

This diff is large: its 38 lines aren’t shown here.

drivers/base/regmap/regcache-lzo.c+2−2

This diff is large: its 12 lines aren’t shown here.

drivers/base/regmap/regcache.c+12−12

This diff is large: its 93 lines aren’t shown here.

drivers/base/regmap/regmap-debugfs.c+12−16

This diff is large: its 74 lines aren’t shown here.

drivers/base/regmap/regmap-irq.c+38−5

This diff is large: its 89 lines aren’t shown here.

drivers/base/regmap/regmap.c+29−12

This diff is large: its 72 lines aren’t shown here.

drivers/base/soc.c+5−16

This diff is large: its 50 lines aren’t shown here.

drivers/bcma/main.c+2−7

This diff is large: its 16 lines aren’t shown here.

drivers/block/Kconfig+0−11

This diff is large: its 18 lines aren’t shown here.

drivers/block/Makefile+0−2

This diff is large: its 15 lines aren’t shown here.

drivers/block/brd.c+6−2

This diff is large: its 31 lines aren’t shown here.

drivers/block/drbd/drbd_bitmap.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/block/drbd/drbd_int.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/block/drbd/drbd_receiver.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/block/drbd/drbd_req.c+2−1

This diff is large: its 17 lines aren’t shown here.

drivers/block/loop.c+222−61

This diff is large: its 435 lines aren’t shown here.

drivers/block/loop.h+7−6

This diff is large: its 38 lines aren’t shown here.

drivers/block/mtip32xx/mtip32xx.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/block/nbd.c+30−13

This diff is large: its 126 lines aren’t shown here.

drivers/block/null_blk.c+3−2

This diff is large: its 26 lines aren’t shown here.

drivers/block/osdblk.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/block/paride/pd.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/block/pktcdvd.c+7−9

This diff is large: its 61 lines aren’t shown here.

drivers/block/ps3vram.c+4−2

This diff is large: its 24 lines aren’t shown here.

drivers/block/rbd.c+104−87

This diff is large: its 433 lines aren’t shown here.

drivers/block/rsxx/dev.c+3−2

This diff is large: its 26 lines aren’t shown here.

drivers/block/umem.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/block/virtio_blk.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/block/xen-blkback/blkback.c+7−6

This diff is large: its 49 lines aren’t shown here.

drivers/block/xen-blkback/common.h+13−4

This diff is large: its 33 lines aren’t shown here.

drivers/block/xen-blkback/xenbus.c+27−22

This diff is large: its 101 lines aren’t shown here.

drivers/block/xen-blkfront.c+372−210

This diff is large: its 898 lines aren’t shown here.

drivers/block/zram/zram_drv.c+17−16

This diff is large: its 122 lines aren’t shown here.

drivers/bluetooth/Kconfig+5−3

This diff is large: its 36 lines aren’t shown here.

drivers/bluetooth/ath3k.c+4−0

This diff is large: its 32 lines aren’t shown here.

drivers/bluetooth/bfusb.c+0−11

This diff is large: its 38 lines aren’t shown here.

drivers/bluetooth/bluecard_cs.c+1−7

This diff is large: its 29 lines aren’t shown here.

drivers/bluetooth/bpa10x.c+66−120

This diff is large: its 267 lines aren’t shown here.

drivers/bluetooth/bt3c_cs.c+9−11

This diff is large: its 67 lines aren’t shown here.

drivers/bluetooth/btbcm.c+65−6

This diff is large: its 126 lines aren’t shown here.

drivers/bluetooth/btintel.c+369−0

This diff is large: its 390 lines aren’t shown here.

drivers/bluetooth/btintel.h+42−1

This diff is large: its 71 lines aren’t shown here.

drivers/bluetooth/btmrvl_main.c+5−28

This diff is large: its 82 lines aren’t shown here.

drivers/bluetooth/btmrvl_sdio.c+48−6

This diff is large: its 100 lines aren’t shown here.

drivers/bluetooth/btsdio.c+1−13

This diff is large: its 43 lines aren’t shown here.

drivers/bluetooth/btuart_cs.c+2−8

This diff is large: its 44 lines aren’t shown here.

drivers/bluetooth/btusb.c+307−61

This diff is large: its 663 lines aren’t shown here.

drivers/bluetooth/btwilink.c+0−13

This diff is large: its 62 lines aren’t shown here.

drivers/bluetooth/dtl1_cs.c+0−5

This diff is large: its 19 lines aren’t shown here.

drivers/bluetooth/hci_ath.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/bluetooth/hci_bcm.c+359−87

This diff is large: its 737 lines aren’t shown here.

drivers/bluetooth/hci_h4.c+1−0

This diff is large: its 5 lines aren’t shown here.

drivers/bluetooth/hci_h5.c+5−5

This diff is large: its 45 lines aren’t shown here.

drivers/bluetooth/hci_intel.c+516−84

This diff is large: its 980 lines aren’t shown here.

drivers/bluetooth/hci_ldisc.c+10−14

This diff is large: its 71 lines aren’t shown here.

drivers/bluetooth/hci_qca.c+11−10

This diff is large: its 74 lines aren’t shown here.

drivers/bluetooth/hci_uart.h+1−1

This diff is large: its 16 lines aren’t shown here.

drivers/bluetooth/hci_vhci.c+0−8

This diff is large: its 29 lines aren’t shown here.

drivers/bus/Kconfig+11−1

This diff is large: its 26 lines aren’t shown here.

drivers/bus/Makefile+1−0

This diff is large: its 7 lines aren’t shown here.

drivers/bus/arm-ccn.c+3−2

This diff is large: its 15 lines aren’t shown here.

drivers/bus/sunxi-rsb.c+783−0

This diff is large: its 784 lines aren’t shown here.

drivers/cdrom/cdrom.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/char/agp/uninorth-agp.c+10−6

This diff is large: its 64 lines aren’t shown here.

drivers/char/efirtc.c+3−10

This diff is large: its 26 lines aren’t shown here.

drivers/char/hpet.c+3−22

This diff is large: its 56 lines aren’t shown here.

drivers/char/hw_random/Kconfig+23−1

This diff is large: its 45 lines aren’t shown here.

drivers/char/hw_random/Makefile+2−0

This diff is large: its 7 lines aren’t shown here.

drivers/char/hw_random/core.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/char/hw_random/exynos-rng.c+49−9

This diff is large: its 110 lines aren’t shown here.

drivers/char/hw_random/mxc-rnga.c+4−10

This diff is large: its 46 lines aren’t shown here.

drivers/char/hw_random/octeon-rng.c+1−11

This diff is large: its 31 lines aren’t shown here.

drivers/char/hw_random/pasemi-rng.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/char/hw_random/ppc4xx-rng.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/char/hw_random/st-rng.c+151−0

This diff is large: its 152 lines aren’t shown here.

drivers/char/hw_random/stm32-rng.c+202−0

This diff is large: its 203 lines aren’t shown here.

drivers/char/ipmi/ipmi_si_intf.c+52−30

This diff is large: its 202 lines aren’t shown here.

drivers/char/ipmi/ipmi_ssif.c+5−4

This diff is large: its 25 lines aren’t shown here.

drivers/char/ipmi/ipmi_watchdog.c+7−1

This diff is large: its 29 lines aren’t shown here.

drivers/char/pcmcia/synclink_cs.c+0−9

This diff is large: its 16 lines aren’t shown here.

drivers/char/snsc.c+2−3

This diff is large: its 16 lines aren’t shown here.

drivers/char/tpm/st33zp24/Kconfig+1−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/st33zp24/i2c.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/st33zp24/spi.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/tpm-chip.c+19−9

This diff is large: its 73 lines aren’t shown here.

drivers/char/tpm/tpm-interface.c+76−0

This diff is large: its 90 lines aren’t shown here.

drivers/char/tpm/tpm.h+123−11

This diff is large: its 211 lines aren’t shown here.

drivers/char/tpm/tpm2-cmd.c+254−1

This diff is large: its 274 lines aren’t shown here.

drivers/char/tpm/tpm_crb.c+15−24

This diff is large: its 84 lines aren’t shown here.

drivers/char/tpm/tpm_eventlog.c+56−22

This diff is large: its 185 lines aren’t shown here.

drivers/char/tpm/tpm_eventlog.h+6−0

This diff is large: its 13 lines aren’t shown here.

drivers/char/tpm/tpm_i2c_atmel.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/tpm_i2c_infineon.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/tpm_i2c_nuvoton.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/char/tpm/tpm_ibmvtpm.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/char/tpm/tpm_of.c+5−4

This diff is large: its 38 lines aren’t shown here.

drivers/char/tpm/tpm_ppi.c+11−23

This diff is large: its 102 lines aren’t shown here.

drivers/char/tpm/tpm_tis.c+170−30

This diff is large: its 336 lines aren’t shown here.

drivers/clk/Kconfig+25−4

This diff is large: its 76 lines aren’t shown here.

drivers/clk/Makefile+4−2

This diff is large: its 35 lines aren’t shown here.

drivers/clk/at91/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

drivers/clk/at91/clk-generated.c+306−0

This diff is large: its 307 lines aren’t shown here.

drivers/clk/at91/clk-peripheral.c+16−8

This diff is large: its 60 lines aren’t shown here.

drivers/clk/at91/clk-system.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/clk/at91/clk-utmi.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/clk/at91/pmc.c+21−0

This diff is large: its 42 lines aren’t shown here.

drivers/clk/at91/pmc.h+3−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/bcm/Kconfig+2−4

This diff is large: its 20 lines aren’t shown here.

drivers/clk/bcm/Makefile+4−0

This diff is large: its 9 lines aren’t shown here.

drivers/clk/bcm/clk-bcm2835.c+1575−0

This diff is large: its 1576 lines aren’t shown here.

drivers/clk/bcm/clk-cygnus.c+80−75

This diff is large: its 283 lines aren’t shown here.

drivers/clk/bcm/clk-iproc-pll.c+110−86

This diff is large: its 390 lines aren’t shown here.

drivers/clk/bcm/clk-iproc.h+21−1

This diff is large: its 48 lines aren’t shown here.

drivers/clk/bcm/clk-ns2.c+288−0

This diff is large: its 289 lines aren’t shown here.

drivers/clk/bcm/clk-nsp.c+139−0

This diff is large: its 140 lines aren’t shown here.

drivers/clk/berlin/bg2.c+2−2

This diff is large: its 11 lines aren’t shown here.

drivers/clk/berlin/bg2q.c+8−8

This diff is large: its 38 lines aren’t shown here.

drivers/clk/clk-bcm2835.c+0−55

This diff is large: its 56 lines aren’t shown here.

drivers/clk/clk-divider.c+10−10

This diff is large: its 83 lines aren’t shown here.

drivers/clk/clk-fractional-divider.c+33−20

This diff is large: its 103 lines aren’t shown here.

drivers/clk/clk-max77802.c+1−1

This diff is large: its 7 lines aren’t shown here.

drivers/clk/clk-multiplier.c+130−0

This diff is large: its 131 lines aren’t shown here.

drivers/clk/clk-qoriq.c+1135−219

This diff is large: its 1483 lines aren’t shown here.

drivers/clk/clk-scpi.c+325−0

This diff is large: its 326 lines aren’t shown here.

drivers/clk/clk-si514.c+379−0

This diff is large: its 380 lines aren’t shown here.

drivers/clk/clk-si5351.c+10−7

This diff is large: its 71 lines aren’t shown here.

drivers/clk/clk-xgene.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/clk/clk.c+32−6

This diff is large: its 100 lines aren’t shown here.

drivers/clk/clkdev.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/clk/h8300/clk-div.c+5−1

This diff is large: its 24 lines aren’t shown here.

drivers/clk/hisilicon/clk-hi6220-stub.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clk/imx/clk-imx25.c+12−0

This diff is large: its 26 lines aren’t shown here.

drivers/clk/imx/clk-imx27.c+16−1

This diff is large: its 39 lines aren’t shown here.

drivers/clk/imx/clk-imx31.c+31−8

This diff is large: its 76 lines aren’t shown here.

drivers/clk/imx/clk-imx35.c+37−22

This diff is large: its 89 lines aren’t shown here.

drivers/clk/imx/clk-imx51-imx53.c+16−0

This diff is large: its 30 lines aren’t shown here.

drivers/clk/imx/clk-imx6q.c+11−1

This diff is large: its 39 lines aren’t shown here.

drivers/clk/imx/clk-imx6sl.c+11−1

This diff is large: its 39 lines aren’t shown here.

drivers/clk/imx/clk-imx6sx.c+9−0

This diff is large: its 29 lines aren’t shown here.

drivers/clk/imx/clk-imx6ul.c+18−0

This diff is large: its 25 lines aren’t shown here.

drivers/clk/imx/clk-imx7d.c+14−0

This diff is large: its 34 lines aren’t shown here.

drivers/clk/imx/clk-pllv2.c+4−8

This diff is large: its 32 lines aren’t shown here.

drivers/clk/imx/clk-vf610.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/imx/clk.c+38−0

This diff is large: its 42 lines aren’t shown here.

drivers/clk/imx/clk.h+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/keystone/pll.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clk/mediatek/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

drivers/clk/mediatek/clk-apmixed.c+107−0

This diff is large: its 108 lines aren’t shown here.

drivers/clk/mediatek/clk-gate.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clk/mediatek/clk-mt8173.c+335−12

This diff is large: its 437 lines aren’t shown here.

drivers/clk/mediatek/clk-mtk.c+30−6

This diff is large: its 71 lines aren’t shown here.

drivers/clk/mediatek/clk-mtk.h+22−2

This diff is large: its 48 lines aren’t shown here.

drivers/clk/mediatek/clk-pll.c+1−6

This diff is large: its 19 lines aren’t shown here.

drivers/clk/mvebu/common.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clk/mxs/clk-frac.c+9−3

This diff is large: its 37 lines aren’t shown here.

drivers/clk/nxp/clk-lpc18xx-ccu.c+15−2

This diff is large: its 25 lines aren’t shown here.

drivers/clk/nxp/clk-lpc18xx-cgu.c+39−3

This diff is large: its 70 lines aren’t shown here.

drivers/clk/qcom/Kconfig+9−0

This diff is large: its 48 lines aren’t shown here.

drivers/clk/qcom/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/qcom/clk-rcg.c+230−0

This diff is large: its 244 lines aren’t shown here.

drivers/clk/qcom/clk-rcg.h+7−1

This diff is large: its 38 lines aren’t shown here.

drivers/clk/qcom/clk-rcg2.c+162−8

This diff is large: its 212 lines aren’t shown here.

drivers/clk/qcom/common.c+32−10

This diff is large: its 79 lines aren’t shown here.

drivers/clk/qcom/common.h+2−2

This diff is large: its 16 lines aren’t shown here.

drivers/clk/qcom/gcc-apq8084.c+42−7

This diff is large: its 86 lines aren’t shown here.

drivers/clk/qcom/gcc-ipq806x.c+0−7

This diff is large: its 16 lines aren’t shown here.

drivers/clk/qcom/gcc-msm8660.c+0−7

This diff is large: its 16 lines aren’t shown here.

drivers/clk/qcom/gcc-msm8916.c+549−20

This diff is large: its 675 lines aren’t shown here.

drivers/clk/qcom/gcc-msm8960.c+18−2

This diff is large: its 38 lines aren’t shown here.

drivers/clk/qcom/gcc-msm8974.c+15−7

This diff is large: its 59 lines aren’t shown here.

drivers/clk/qcom/gdsc.c+237−0

This diff is large: its 238 lines aren’t shown here.

drivers/clk/qcom/gdsc.h+68−0

This diff is large: its 69 lines aren’t shown here.

drivers/clk/qcom/lcc-ipq806x.c+0−7

This diff is large: its 16 lines aren’t shown here.

drivers/clk/qcom/lcc-msm8960.c+0−7

This diff is large: its 16 lines aren’t shown here.

drivers/clk/qcom/mmcc-apq8084.c+87−24

This diff is large: its 198 lines aren’t shown here.

drivers/clk/qcom/mmcc-msm8960.c+404−7

This diff is large: its 483 lines aren’t shown here.

drivers/clk/qcom/mmcc-msm8974.c+81−11

This diff is large: its 171 lines aren’t shown here.

drivers/clk/rockchip/clk-mmc-phase.c+46−19

This diff is large: its 100 lines aren’t shown here.

drivers/clk/rockchip/clk-pll.c+74−61

This diff is large: its 202 lines aren’t shown here.

drivers/clk/rockchip/clk.c+4−2

This diff is large: its 14 lines aren’t shown here.

drivers/clk/samsung/clk-cpu.c+5−5

This diff is large: its 45 lines aren’t shown here.

drivers/clk/samsung/clk-exynos5250.c+13−1

This diff is large: its 48 lines aren’t shown here.

drivers/clk/samsung/clk-exynos7.c+319−148

This diff is large: its 787 lines aren’t shown here.

drivers/clk/shmobile/clk-mstp.c+5−1

This diff is large: its 20 lines aren’t shown here.

drivers/clk/shmobile/clk-r8a7778.c+4−4

This diff is large: its 26 lines aren’t shown here.

drivers/clk/sirf/clk-atlas7.c+200−158

This diff is large: its 437 lines aren’t shown here.

drivers/clk/st/clk-flexgen.c+4−3

This diff is large: its 25 lines aren’t shown here.

drivers/clk/st/clkgen-mux.c+3−0

This diff is large: its 24 lines aren’t shown here.

drivers/clk/st/clkgen-pll.c+461−8

This diff is large: its 719 lines aren’t shown here.

drivers/clk/st/clkgen.h+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/clk/sunxi/Makefile+3−0

This diff is large: its 11 lines aren’t shown here.

drivers/clk/sunxi/clk-a10-codec.c+44−0

This diff is large: its 45 lines aren’t shown here.

drivers/clk/sunxi/clk-a10-mod1.c+81−0

This diff is large: its 82 lines aren’t shown here.

drivers/clk/sunxi/clk-a10-pll2.c+216−0

This diff is large: its 217 lines aren’t shown here.

drivers/clk/sunxi/clk-simple-gates.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/clk/sunxi/clk-sun6i-apb0-gates.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/sunxi/clk-sun6i-apb0.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/sunxi/clk-sun6i-ar100.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/sunxi/clk-sun8i-apb0.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/sunxi/clk-sun9i-mmc.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/sunxi/clk-sunxi.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/clk/tegra/clk-dfll.c+57−57

This diff is large: its 154 lines aren’t shown here.

drivers/clk/tegra/clk-emc.c+1−3

This diff is large: its 12 lines aren’t shown here.

drivers/clk/tegra/clk-tegra-audio.c+18−7

This diff is large: its 37 lines aren’t shown here.

drivers/clk/tegra/clk-tegra114.c+7−1

This diff is large: its 22 lines aren’t shown here.

drivers/clk/tegra/clk-tegra124.c+7−1

This diff is large: its 22 lines aren’t shown here.

drivers/clk/tegra/clk-tegra30.c+7−1

This diff is large: its 22 lines aren’t shown here.

drivers/clk/tegra/clk.h+67−39

This diff is large: its 150 lines aren’t shown here.

drivers/clk/tegra/cvb.c+0−7

This diff is large: its 14 lines aren’t shown here.

drivers/clk/ti/clk-3xxx.c+1−1

This diff is large: its 16 lines aren’t shown here.

drivers/clk/ti/clk-7xx.c+1−17

This diff is large: its 37 lines aren’t shown here.

drivers/clk/ti/clkt_dflt.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/clk/versatile/Kconfig+1−1

This diff is large: its 8 lines aren’t shown here.

drivers/clk/versatile/clk-icst.c+3−1

This diff is large: its 12 lines aren’t shown here.

drivers/clocksource/Kconfig+22−0

This diff is large: its 51 lines aren’t shown here.

drivers/clocksource/Makefile+4−1

This diff is large: its 26 lines aren’t shown here.

drivers/clocksource/arm_arch_timer.c+1−9

This diff is large: its 15 lines aren’t shown here.

drivers/clocksource/arm_global_timer.c+7−2

This diff is large: its 30 lines aren’t shown here.

drivers/clocksource/clksrc-probe.crenamed from drivers/clocksource/clksrc-of.c+5−1

This diff is large: its 27 lines aren’t shown here.

drivers/clocksource/em_sti.c+0−2

This diff is large: its 16 lines aren’t shown here.

drivers/clocksource/exynos_mct.c+8−4

This diff is large: its 33 lines aren’t shown here.

drivers/clocksource/fsl_ftm_timer.c+3−3

This diff is large: its 27 lines aren’t shown here.

drivers/clocksource/h8300_timer16.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/clocksource/h8300_timer8.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/clocksource/h8300_tpu.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/clocksource/mips-gic-timer.c+4−3

This diff is large: its 14 lines aren’t shown here.

drivers/clocksource/mtk_timer.c+16−10

This diff is large: its 68 lines aren’t shown here.

drivers/clocksource/numachip.c+95−0

This diff is large: its 96 lines aren’t shown here.

drivers/clocksource/rockchip_timer.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clocksource/samsung_pwm_timer.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clocksource/sh_cmt.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/clocksource/sh_mtu2.c+3−1

This diff is large: its 11 lines aren’t shown here.

drivers/clocksource/tango_xtal.c+66−0

This diff is large: its 67 lines aren’t shown here.

drivers/clocksource/tcb_clksrc.c+10−2

This diff is large: its 29 lines aren’t shown here.

drivers/clocksource/time-armada-370-xp.c+14−0

This diff is large: its 35 lines aren’t shown here.

drivers/clocksource/time-pistachio.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/clocksource/timer-atmel-st.c+22−9

This diff is large: its 83 lines aren’t shown here.

drivers/clocksource/timer-digicolor.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clocksource/timer-imx-gpt.c+2−1

This diff is large: its 16 lines aren’t shown here.

drivers/clocksource/timer-keystone.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clocksource/timer-prima2.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/clocksource/timer-ti-32k.c+126−0

This diff is large: its 127 lines aren’t shown here.

drivers/clocksource/vf_pit_timer.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/connector/connector.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/cpufreq/Kconfig.arm+28−0

This diff is large: its 46 lines aren’t shown here.

drivers/cpufreq/Makefile+3−1

This diff is large: its 21 lines aren’t shown here.

drivers/cpufreq/acpi-cpufreq.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/cpufreq/arm_big_little.c+13−9

This diff is large: its 36 lines aren’t shown here.

drivers/cpufreq/arm_big_little.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/cpufreq/arm_big_little_dt.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/cpufreq/cppc_cpufreq.c+175−0

This diff is large: its 176 lines aren’t shown here.

drivers/cpufreq/cpufreq-dt.c+5−5

This diff is large: its 45 lines aren’t shown here.

drivers/cpufreq/cpufreq.c+23−93

This diff is large: its 223 lines aren’t shown here.

drivers/cpufreq/cpufreq_conservative.c+18−13

This diff is large: its 55 lines aren’t shown here.

drivers/cpufreq/cpufreq_governor.c+29−36

This diff is large: its 146 lines aren’t shown here.

drivers/cpufreq/cpufreq_governor.h+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/cpufreq/cpufreq_ondemand.c+1−9

This diff is large: its 29 lines aren’t shown here.

drivers/cpufreq/cpufreq_opp.c+0−114

This diff is large: its 115 lines aren’t shown here.

drivers/cpufreq/exynos5440-cpufreq.c+3−3

This diff is large: its 27 lines aren’t shown here.

drivers/cpufreq/imx6q-cpufreq.c+48−8

This diff is large: its 117 lines aren’t shown here.

drivers/cpufreq/integrator-cpufreq.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/cpufreq/intel_pstate.c+202−83

This diff is large: its 597 lines aren’t shown here.

drivers/cpufreq/mt8173-cpufreq.c+3−3

This diff is large: its 27 lines aren’t shown here.

drivers/cpufreq/powernv-cpufreq.c+8−2

This diff is large: its 17 lines aren’t shown here.

drivers/cpufreq/s5pv210-cpufreq.c+2−2

This diff is large: its 14 lines aren’t shown here.

drivers/cpufreq/scpi-cpufreq.c+124−0

This diff is large: its 125 lines aren’t shown here.

drivers/cpufreq/tegra20-cpufreq.c+0−2

This diff is large: its 10 lines aren’t shown here.

drivers/cpuidle/cpuidle-mvebu-v7.c+21−25

This diff is large: its 66 lines aren’t shown here.

drivers/crypto/Kconfig+3−2

This diff is large: its 19 lines aren’t shown here.

drivers/crypto/amcc/crypto4xx_core.c+2−21

This diff is large: its 44 lines aren’t shown here.

drivers/crypto/atmel-aes.c+14−30

This diff is large: its 110 lines aren’t shown here.

drivers/crypto/atmel-sha.c+14−19

This diff is large: its 95 lines aren’t shown here.

drivers/crypto/atmel-tdes.c+12−23

This diff is large: its 90 lines aren’t shown here.

drivers/crypto/bfin_crc.c+3−22

This diff is large: its 46 lines aren’t shown here.

drivers/crypto/caam/caamalg.c+171−61

This diff is large: its 390 lines aren’t shown here.

drivers/crypto/caam/caamhash.c+72−59

This diff is large: its 391 lines aren’t shown here.

drivers/crypto/caam/desc.h+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/crypto/caam/sg_sw_sec4.h+2−70

This diff is large: its 84 lines aren’t shown here.

drivers/crypto/ccp/Kconfig+6−7

This diff is large: its 26 lines aren’t shown here.

drivers/crypto/ccp/ccp-crypto-aes-cmac.c+19−1

This diff is large: its 44 lines aren’t shown here.

drivers/crypto/ccp/ccp-crypto-main.c+4−2

This diff is large: its 19 lines aren’t shown here.

drivers/crypto/ccp/ccp-crypto-sha.c+13−0

This diff is large: its 28 lines aren’t shown here.

drivers/crypto/ccp/ccp-ops.c+69−39

This diff is large: its 185 lines aren’t shown here.

drivers/crypto/ccp/ccp-pci.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/crypto/ccp/ccp-platform.c+12−9

This diff is large: its 64 lines aren’t shown here.

drivers/crypto/hifn_795x.c+0−2

This diff is large: its 9 lines aren’t shown here.

drivers/crypto/marvell/cesa.h+31−24

This diff is large: its 120 lines aren’t shown here.

drivers/crypto/marvell/cipher.c+7−6

This diff is large: its 39 lines aren’t shown here.

drivers/crypto/marvell/hash.c+226−245

This diff is large: its 799 lines aren’t shown here.

drivers/crypto/marvell/tdma.c+22−20

This diff is large: its 110 lines aren’t shown here.

drivers/crypto/n2_core.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/crypto/nx/nx-842-powernv.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/crypto/nx/nx-842-pseries.c+6−2

This diff is large: its 29 lines aren’t shown here.

drivers/crypto/picoxcell_crypto.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/crypto/qat/qat_common/Makefile+9−3

This diff is large: its 23 lines aren’t shown here.

drivers/crypto/qat/qat_common/adf_common_drv.h+1−3

This diff is large: its 12 lines aren’t shown here.

drivers/crypto/qat/qat_common/adf_ctl_drv.c+1−7

This diff is large: its 36 lines aren’t shown here.

drivers/crypto/qat/qat_common/adf_init.c+3−5

This diff is large: its 16 lines aren’t shown here.

drivers/crypto/qat/qat_common/adf_sriov.c+2−5

This diff is large: its 14 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_algs.c+128−50

This diff is large: its 318 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_asym_algs.c+158−55

This diff is large: its 358 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_crypto.c+48−31

This diff is large: its 107 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_hal.c+2−3

This diff is large: its 19 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_rsakey.asn1+0−5

This diff is large: its 6 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_rsaprivkey.asn1+11−0

This diff is large: its 12 lines aren’t shown here.

drivers/crypto/qat/qat_common/qat_rsapubkey.asn1+4−0

This diff is large: its 5 lines aren’t shown here.

drivers/crypto/qce/ablkcipher.c+10−20

This diff is large: its 64 lines aren’t shown here.

drivers/crypto/qce/cipher.h+0−4

This diff is large: its 18 lines aren’t shown here.

drivers/crypto/qce/dma.c+0−52

This diff is large: its 59 lines aren’t shown here.

drivers/crypto/qce/dma.h+0−5

This diff is large: its 12 lines aren’t shown here.

drivers/crypto/qce/sha.c+7−11

This diff is large: its 45 lines aren’t shown here.

drivers/crypto/qce/sha.h+0−2

This diff is large: its 16 lines aren’t shown here.

drivers/crypto/sahara.c+22−86

This diff is large: its 218 lines aren’t shown here.

drivers/crypto/talitos.c+18−86

This diff is large: its 214 lines aren’t shown here.

drivers/crypto/ux500/cryp/cryp_core.c+10−61

This diff is large: its 164 lines aren’t shown here.

drivers/crypto/ux500/hash/hash_core.c+8−42

This diff is large: its 134 lines aren’t shown here.

drivers/devfreq/devfreq.c+4−3

This diff is large: its 29 lines aren’t shown here.

drivers/dma-buf/fence.c+98−0

This diff is large: its 105 lines aren’t shown here.

drivers/dma/Kconfig+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/dma/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/dma/acpi-dma.c+22−14

This diff is large: its 73 lines aren’t shown here.

drivers/dma/at_hdmac.c+140−44

This diff is large: its 278 lines aren’t shown here.

drivers/dma/at_hdmac_regs.h+4−4

This diff is large: its 22 lines aren’t shown here.

drivers/dma/at_xdmac.c+75−66

This diff is large: its 224 lines aren’t shown here.

drivers/dma/dmaengine.c+11−5

This diff is large: its 34 lines aren’t shown here.

drivers/dma/dw/core.c+39−38

This diff is large: its 198 lines aren’t shown here.

drivers/dma/dw/pci.c+7−13

This diff is large: its 40 lines aren’t shown here.

drivers/dma/dw/platform.c+16−1

This diff is large: its 39 lines aren’t shown here.

drivers/dma/edma.c+1606−252

This diff is large: its 2211 lines aren’t shown here.

drivers/dma/fsldma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/hsu/Kconfig+2−7

This diff is large: its 13 lines aren’t shown here.

drivers/dma/hsu/hsu.c+7−17

This diff is large: its 65 lines aren’t shown here.

drivers/dma/hsu/hsu.h+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/hsu/pci.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/dma/idma64.c+20−18

This diff is large: its 99 lines aren’t shown here.

drivers/dma/idma64.h+5−9

This diff is large: its 40 lines aren’t shown here.

drivers/dma/imx-sdma.c+2−5

This diff is large: its 35 lines aren’t shown here.

drivers/dma/ioat/dma.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/dma/ioat/dma.h+4−2

This diff is large: its 20 lines aren’t shown here.

drivers/dma/ioat/init.c+112−2

This diff is large: its 154 lines aren’t shown here.

drivers/dma/ioat/prep.c+34−0

This diff is large: its 90 lines aren’t shown here.

drivers/dma/mic_x100_dma.c+38−1

This diff is large: its 61 lines aren’t shown here.

drivers/dma/moxart-dma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/mpc512x_dma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/omap-dma.c+5−1

This diff is large: its 14 lines aren’t shown here.

drivers/dma/pxa_dma.c+25−6

This diff is large: its 72 lines aren’t shown here.

drivers/dma/sh/usb-dmac.c+8−3

This diff is large: its 40 lines aren’t shown here.

drivers/dma/sirf-dma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/ste_dma40.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/dma/sun4i-dma.c+3−3

This diff is large: its 17 lines aren’t shown here.

drivers/dma/sun6i-dma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/ti-dma-crossbar.c+221−30

This diff is large: its 353 lines aren’t shown here.

drivers/dma/virt-dma.h+9−9

This diff is large: its 60 lines aren’t shown here.

drivers/dma/xgene-dma.c+19−90

This diff is large: its 230 lines aren’t shown here.

drivers/dma/xilinx/xilinx_vdma.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/dma/zx296702_dma.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/edac/Makefile+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/edac/altera_edac.c+8−12

This diff is large: its 55 lines aren’t shown here.

drivers/edac/altera_edac.h+1−4

This diff is large: its 24 lines aren’t shown here.

drivers/edac/amd64_edac.c+28−13

This diff is large: its 92 lines aren’t shown here.

drivers/edac/amd64_edac.h+3−55

This diff is large: its 75 lines aren’t shown here.

drivers/edac/debugfs.c+163−0

This diff is large: its 164 lines aren’t shown here.

drivers/edac/edac_core.h+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/edac/edac_mc.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/edac/edac_mc_sysfs.c+28−122

This diff is large: its 212 lines aren’t shown here.

drivers/edac/edac_module.h+29−5

This diff is large: its 45 lines aren’t shown here.

drivers/edac/ghes_edac.c+2−22

This diff is large: its 45 lines aren’t shown here.

drivers/edac/i3200_edac.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/edac/i5100_edac.c+19−18

This diff is large: its 76 lines aren’t shown here.

drivers/edac/ie31200_edac.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/edac/ppc4xx_edac.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/edac/sb_edac.c+4−4

This diff is large: its 29 lines aren’t shown here.

drivers/edac/x38_edac.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/edac/xgene_edac.c+985−208

This diff is large: its 1326 lines aren’t shown here.

drivers/extcon/extcon-arizona.c+124−40

This diff is large: its 367 lines aren’t shown here.

drivers/extcon/extcon-axp288.c+11−24

This diff is large: its 100 lines aren’t shown here.

drivers/extcon/extcon-gpio.c+70−60

This diff is large: its 213 lines aren’t shown here.

drivers/extcon/extcon-max14577.c+9−8

This diff is large: its 39 lines aren’t shown here.

drivers/extcon/extcon-max77693.c+17−15

This diff is large: its 85 lines aren’t shown here.

drivers/extcon/extcon-max77843.c+15−12

This diff is large: its 77 lines aren’t shown here.

drivers/extcon/extcon-max8997.c+11−10

This diff is large: its 50 lines aren’t shown here.

drivers/extcon/extcon-rt8973a.c+4−3

This diff is large: its 35 lines aren’t shown here.

drivers/extcon/extcon-sm5502.c+4−3

This diff is large: its 35 lines aren’t shown here.

drivers/extcon/extcon.c+32−29

This diff is large: its 70 lines aren’t shown here.

drivers/firewire/core-cdev.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/firewire/ohci.c+5−0

This diff is large: its 12 lines aren’t shown here.

drivers/firmware/Kconfig+26−0

This diff is large: its 40 lines aren’t shown here.

drivers/firmware/Makefile+3−1

This diff is large: its 21 lines aren’t shown here.

drivers/firmware/arm_scpi.c+771−0

This diff is large: its 772 lines aren’t shown here.

drivers/firmware/efi/Kconfig+22−0

This diff is large: its 29 lines aren’t shown here.

drivers/firmware/efi/Makefile+9−0

This diff is large: its 20 lines aren’t shown here.

drivers/firmware/efi/efi-pstore.c+2−1

This diff is large: its 14 lines aren’t shown here.

drivers/firmware/efi/efi.c+82−25

This diff is large: its 194 lines aren’t shown here.

drivers/firmware/efi/esrt.c+3−16

This diff is large: its 34 lines aren’t shown here.

drivers/firmware/efi/fake_mem.c+238−0

This diff is large: its 239 lines aren’t shown here.

drivers/firmware/efi/libstub/Makefile+36−6

This diff is large: its 62 lines aren’t shown here.

drivers/firmware/efi/libstub/arm-stub.c+73−15

This diff is large: its 121 lines aren’t shown here.

drivers/firmware/efi/libstub/arm64-stub.crenamed from arch/arm64/kernel/efi-stub.c+12−2

This diff is large: its 31 lines aren’t shown here.

drivers/firmware/efi/libstub/fdt.c+0−9

This diff is large: its 16 lines aren’t shown here.

drivers/firmware/efi/libstub/string.c+57−0

This diff is large: its 58 lines aren’t shown here.

drivers/firmware/psci.c+98−10

This diff is large: its 190 lines aren’t shown here.

drivers/firmware/qcom_scm-32.c+3−3

This diff is large: its 19 lines aren’t shown here.

drivers/firmware/raspberrypi.c+260−0

This diff is large: its 261 lines aren’t shown here.

drivers/fpga/Kconfig+29−0

This diff is large: its 30 lines aren’t shown here.

drivers/fpga/Makefile+10−0

This diff is large: its 11 lines aren’t shown here.

drivers/fpga/fpga-mgr.c+380−0

This diff is large: its 381 lines aren’t shown here.

drivers/fpga/socfpga.c+616−0

This diff is large: its 617 lines aren’t shown here.

drivers/fpga/zynq-fpga.c+514−0

This diff is large: its 515 lines aren’t shown here.

drivers/gpio/Kconfig+103−93

This diff is large: its 323 lines aren’t shown here.

drivers/gpio/Makefile+3−2

This diff is large: its 33 lines aren’t shown here.

drivers/gpio/gpio-104-idio-16.c+216−0

This diff is large: its 217 lines aren’t shown here.

drivers/gpio/gpio-74x164.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpio/gpio-altera.c+10−5

This diff is large: its 57 lines aren’t shown here.

drivers/gpio/gpio-amdpt.c+261−0

This diff is large: its 262 lines aren’t shown here.

drivers/gpio/gpio-arizona.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/gpio/gpio-ath79.c+60−59

This diff is large: its 215 lines aren’t shown here.

drivers/gpio/gpio-etraxfs.c+17−6

This diff is large: its 72 lines aren’t shown here.

drivers/gpio/gpio-generic.c+19−39

This diff is large: its 86 lines aren’t shown here.

drivers/gpio/gpio-it87.c+411−0

This diff is large: its 412 lines aren’t shown here.

drivers/gpio/gpio-it8761e.c+0−230

This diff is large: its 231 lines aren’t shown here.

drivers/gpio/gpio-lpc18xx.c+2−12

This diff is large: its 28 lines aren’t shown here.

drivers/gpio/gpio-max7301.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpio/gpio-max730x.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpio/gpio-mc33880.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpio/gpio-mcp23s08.c+0−2

This diff is large: its 16 lines aren’t shown here.

drivers/gpio/gpio-moxart.c+2−12

This diff is large: its 28 lines aren’t shown here.

drivers/gpio/gpio-msm-v2.c+0−453

This diff is large: its 454 lines aren’t shown here.

drivers/gpio/gpio-mvebu.c+2−12

This diff is large: its 28 lines aren’t shown here.

drivers/gpio/gpio-mxc.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpio/gpio-omap.c+43−39

This diff is large: its 205 lines aren’t shown here.

drivers/gpio/gpio-pca953x.c+36−9

This diff is large: its 139 lines aren’t shown here.

drivers/gpio/gpio-pl061.c+74−38

This diff is large: its 179 lines aren’t shown here.

drivers/gpio/gpio-sodaville.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpio/gpio-sx150x.c+14−17

This diff is large: its 106 lines aren’t shown here.

drivers/gpio/gpio-tb10x.c+2−12

This diff is large: its 28 lines aren’t shown here.

drivers/gpio/gpio-tz1090-pdc.c+2−12

This diff is large: its 28 lines aren’t shown here.

drivers/gpio/gpio-vf610.c+21−22

This diff is large: its 114 lines aren’t shown here.

drivers/gpio/gpio-xlp.c+11−10

This diff is large: its 64 lines aren’t shown here.

drivers/gpio/gpio-zx.c+4−24

This diff is large: its 51 lines aren’t shown here.

drivers/gpio/gpio-zynq.c+22−10

This diff is large: its 109 lines aren’t shown here.

drivers/gpio/gpiolib-acpi.c+129−45

This diff is large: its 233 lines aren’t shown here.

drivers/gpio/gpiolib-legacy.c+4−4

This diff is large: its 22 lines aren’t shown here.

drivers/gpio/gpiolib-of.c+10−10

This diff is large: its 61 lines aren’t shown here.

drivers/gpio/gpiolib.c+153−25

This diff is large: its 329 lines aren’t shown here.

drivers/gpio/gpiolib.h+12−1

This diff is large: its 35 lines aren’t shown here.

drivers/gpu/drm/Kconfig+2−0

This diff is large: its 6 lines aren’t shown here.

drivers/gpu/drm/Makefile+5−1

This diff is large: its 27 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu.h+88−133

This diff is large: its 435 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v7.c+2−2

This diff is large: its 15 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c+2−2

This diff is large: its 15 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_atombios.c+6−2

This diff is large: its 15 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_bios.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_cgs.c+0−39

This diff is large: its 53 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c+106−124

This diff is large: its 370 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_device.c+34−13

This diff is large: its 114 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_display.c+6−16

This diff is large: its 78 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c+21−11

This diff is large: its 79 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c+17−0

This diff is large: its 28 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c+170−310

This diff is large: its 609 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c+32−21

This diff is large: its 167 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c+4−4

This diff is large: its 36 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c+40−37

This diff is large: its 169 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h+9−5

This diff is large: its 35 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_object.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_object.h+3−4

This diff is large: its 14 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c+11−2

This diff is large: its 36 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c+26−45

This diff is large: its 106 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c+16−30

This diff is large: its 86 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c+14−19

This diff is large: its 68 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_semaphore.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c+34−31

This diff is large: its 136 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h+62−44

This diff is large: its 134 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c+6−1

This diff is large: its 21 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c+5−0

This diff is large: its 26 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c+5−0

This diff is large: its 26 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c+101−99

This diff is large: its 508 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/atom.c+51−2

This diff is large: its 81 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/atom.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/atombios_encoders.c+1−2

This diff is large: its 10 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/ci_dpm.c+9−7

This diff is large: its 52 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/cik.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/cik_sdma.c+62−87

This diff is large: its 354 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/cz_dpm.c+23−8

This diff is large: its 78 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/cz_smc.c+48−12

This diff is large: its 118 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/dce_v10_0.c+130−137

This diff is large: its 441 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/dce_v11_0.c+149−139

This diff is large: its 498 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/dce_v8_0.c+132−137

This diff is large: its 441 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c+0−20

This diff is large: its 41 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c+948−284

This diff is large: its 1602 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/gmc_v7_0.c+44−15

This diff is large: its 124 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c+57−8

This diff is large: its 141 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/kv_dpm.c+9−3

This diff is large: its 26 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/sdma_v2_4.c+72−103

This diff is large: its 382 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c+110−103

This diff is large: its 471 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/uvd_v4_2.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/uvd_v5_0.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/vce_v2_0.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/vce_v3_0.c+3−3

This diff is large: its 20 lines aren’t shown here.

drivers/gpu/drm/amd/amdgpu/vi.c+42−11

This diff is large: its 141 lines aren’t shown here.

drivers/gpu/drm/amd/include/amd_shared.h+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/amd/include/asic_reg/gca/gfx_8_1_d.h+2791−0

This diff is large: its 2792 lines aren’t shown here.

drivers/gpu/drm/amd/include/asic_reg/gca/gfx_8_1_enum.h+6808−0

This diff is large: its 6809 lines aren’t shown here.

This diff is larger than a page shows: the files after these aren’t listed. Clone the repository to see all of it.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t