History

Merge tag 'v3.19-rc4' into next

Merge with mainline to bring in the latest thermal and other changes.

Dmitry Torokhov committed 11 years ago

Commit 0c49cd22 parents 0c3e994 eaa27f315497 files · +879003 −622018Browse files

Unified · Split

3291 files
  1. .gitignore +3 −0
  2. .mailmap +4 −1
  3. CREDITS +10 −3
  4. Documentation/.gitignore +0 −7
  5. Documentation/00-INDEX +2 −0
  6. Documentation/ABI/removed/net_dma +8 −0
  7. Documentation/ABI/stable/sysfs-bus-usb +6 −8
  8. Documentation/ABI/stable/sysfs-class-udc +93 −0
  9. Documentation/ABI/stable/sysfs-devices-node +0 −8
  10. Documentation/ABI/stable/sysfs-driver-ib_srp +19 −6
  11. Documentation/ABI/testing/configfs-usb-gadget-hid +11 −0
  12. Documentation/ABI/testing/configfs-usb-gadget-midi +12 −0
  13. Documentation/ABI/testing/configfs-usb-gadget-uac1 +12 −0
  14. Documentation/ABI/testing/configfs-usb-gadget-uac2 +12 −0
  15. Documentation/ABI/testing/sysfs-block +8 −0
  16. Documentation/ABI/testing/sysfs-block-zram +27 −5
  17. Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10 +24 −0
  18. Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x +253 −0
  19. Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel +12 −0
  20. Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc +8 −0
  21. Documentation/ABI/testing/sysfs-bus-event_source-devices-events +49 −562
  22. Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 +3 −3
  23. Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci +6 −6
  24. Documentation/ABI/testing/sysfs-bus-iio +23 −0
  25. Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 +7 −0
  26. Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 +7 −0
  27. Documentation/ABI/testing/sysfs-bus-pci +23 −0
  28. Documentation/ABI/testing/sysfs-bus-usb +9 −10
  29. Documentation/ABI/testing/sysfs-class-cxl +129 −0
  30. Documentation/ABI/testing/sysfs-class-net +9 −1
  31. Documentation/ABI/testing/sysfs-class-power +14 −0
  32. Documentation/ABI/testing/sysfs-class-uwb_rc +13 −0
  33. Documentation/ABI/testing/sysfs-devices-memory +8 −0
  34. Documentation/ABI/testing/sysfs-devices-system-cpu +47 −0
  35. Documentation/ABI/testing/sysfs-fs-f2fs +7 −0
  36. Documentation/ABI/testing/sysfs-ibft +1 −1
  37. Documentation/ABI/testing/sysfs-platform-dell-laptop +60 −0
  38. Documentation/Changes +6 −17
  39. Documentation/CodingStyle +66 −6
  40. Documentation/DMA-API-HOWTO.txt +3 −3
  41. Documentation/DocBook/Makefile +1 −1
  42. Documentation/DocBook/alsa-driver-api.tmpl +31 −0
  43. Documentation/DocBook/crypto-API.tmpl +1253 −0
  44. Documentation/DocBook/drm.tmpl +306 −144
  45. Documentation/DocBook/kernel-locking.tmpl +1 −1
  46. Documentation/DocBook/media/Makefile +1 −1
  47. Documentation/DocBook/media/dvb/dvbproperty.xml +2 −2
  48. Documentation/DocBook/media/v4l/biblio.xml +85 −0
  49. Documentation/DocBook/media/v4l/common.xml +1 −1
  50. Documentation/DocBook/media/v4l/compat.xml +22 −0
  51. Documentation/DocBook/media/v4l/controls.xml +55 −0
  52. Documentation/DocBook/media/v4l/dev-subdev.xml +63 −46
  53. Documentation/DocBook/media/v4l/io.xml +4 −1
  54. Documentation/DocBook/media/v4l/pixfmt-packed-rgb.xml +48 −4
  55. Documentation/DocBook/media/v4l/pixfmt.xml +1001 −309
  56. Documentation/DocBook/media/v4l/selections-common.xml +16 −0
  57. Documentation/DocBook/media/v4l/subdev-formats.xml +171 −155
  58. Documentation/DocBook/media/v4l/v4l2.xml +10 −1
  59. Documentation/DocBook/media/v4l/vidioc-dqevent.xml +4 −3
  60. Documentation/DocBook/media/v4l/vidioc-enuminput.xml +8 −0
  61. Documentation/DocBook/media/v4l/vidioc-enumoutput.xml +8 −0
  62. Documentation/DocBook/media/v4l/vidioc-g-edid.xml +7 −7
  63. Documentation/DocBook/media/v4l/vidioc-subscribe-event.xml +1 −1
  64. Documentation/DocBook/uio-howto.tmpl +1 −1
  65. Documentation/DocBook/usb.tmpl +1 −1
  66. Documentation/DocBook/writing-an-alsa-driver.tmpl +46 −5
  67. Documentation/HOWTO +0 −1
  68. Documentation/IPMI.txt +71 −3
  69. Documentation/IRQ-domain.txt +71 −0
  70. Documentation/Makefile +4 −3
  71. Documentation/RCU/rcu.txt +2 −2
  72. Documentation/RCU/stallwarn.txt +28 −19
  73. Documentation/RCU/trace.txt +2 −2
  74. Documentation/RCU/whatisRCU.txt +1 −1
  75. Documentation/SubmittingPatches +4 −6
  76. Documentation/accounting/Makefile +0 −3
  77. Documentation/acpi/enumeration.txt +27 −0
  78. Documentation/acpi/gpio-properties.txt +96 −0
  79. Documentation/applying-patches.txt +1 −1
  80. Documentation/arm/Makefile +1 −0
  81. Documentation/arm/Marvell/README +4 −0
  82. Documentation/arm/SH-Mobile/.gitignore +1 −0
  83. Documentation/arm/SH-Mobile/Makefile +5 −6
  84. Documentation/arm/SH-Mobile/vrl4.c +4 −3
  85. Documentation/arm/firmware.txt +5 −23
  86. Documentation/arm/memory.txt +1 −1
  87. Documentation/arm/sunxi/README +13 −3
  88. Documentation/arm64/legacy_instructions.txt +45 −0
  89. Documentation/arm64/memory.txt +1 −1
  90. Documentation/atomic_ops.txt +8 −4
  91. Documentation/auxdisplay/Makefile +0 −3
  92. Documentation/binfmt_misc.txt +29 −21
  93. Documentation/blackfin/Makefile +2 −5
  94. Documentation/block/biodoc.txt +5 −5
  95. Documentation/block/data-integrity.txt +5 −49
  96. Documentation/block/null_blk.txt +2 −2
  97. Documentation/block/queue-sysfs.txt +3 −3
  98. Documentation/blockdev/zram.txt +21 −4
  99. Documentation/cgroups/cgroups.txt +2 −2
  100. Documentation/cgroups/cpusets.txt +3 −3
  101. Documentation/cgroups/hugetlb.txt +1 −1
  102. Documentation/cgroups/memory.txt +19 −15
  103. Documentation/cgroups/resource_counter.txt +0 −197
  104. Documentation/clk.txt +1 −1
  105. Documentation/cpu-freq/intel-pstate.txt +25 −12
  106. Documentation/crypto/crypto-API-userspace.txt +205 −0
  107. Documentation/development-process/2.Process +0 −4
  108. Documentation/development-process/8.Conclusion +0 −4
  109. Documentation/device-mapper/cache-policies.txt +15 −9
  110. Documentation/devicetree/bindings/arm/altera/socfpga-sdram-edac.txt +15 −0
  111. Documentation/devicetree/bindings/arm/amlogic.txt +10 −0
  112. Documentation/devicetree/bindings/arm/arch_timer.txt +8 −0
  113. Documentation/devicetree/bindings/arm/arm-boards +65 −0
  114. Documentation/devicetree/bindings/arm/atmel-at91.txt +38 −7
  115. Documentation/devicetree/bindings/arm/bcm/bcm63138.txt +9 −0
  116. Documentation/devicetree/bindings/arm/bcm/cygnus.txt +31 −0
  117. Documentation/devicetree/bindings/arm/cavium-thunder.txt +10 −0
  118. Documentation/devicetree/bindings/arm/coresight.txt +204 −0
  119. Documentation/devicetree/bindings/arm/cpus.txt +18 −0
  120. Documentation/devicetree/bindings/arm/exynos/power_domain.txt +6 −7
  121. Documentation/devicetree/bindings/arm/fsl.txt +38 −0
  122. Documentation/devicetree/bindings/arm/geniatech.txt +5 −0
  123. Documentation/devicetree/bindings/arm/gic-v3.txt +39 −0
  124. Documentation/devicetree/bindings/arm/gic.txt +54 −0
  125. Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt +23 −0
  126. Documentation/devicetree/bindings/arm/idle-states.txt +699 −0
  127. Documentation/devicetree/bindings/arm/l2cc.txt +10 −0
  128. Documentation/devicetree/bindings/arm/marvell,berlin.txt +10 −0
  129. Documentation/devicetree/bindings/arm/mediatek.txt +22 −3
  130. Documentation/devicetree/bindings/arm/mediatek/mediatek,sysirq.txt +28 −0
  131. Documentation/devicetree/bindings/arm/omap/mpu.txt +3 −0
  132. Documentation/devicetree/bindings/arm/omap/omap.txt +15 −0
  133. Documentation/devicetree/bindings/arm/psci.txt +13 −1
  134. Documentation/devicetree/bindings/arm/rockchip.txt +4 −0
  135. Documentation/devicetree/bindings/arm/samsung-boards.txt +14 −5
  136. Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt +24 −5
  137. Documentation/devicetree/bindings/arm/shmobile.txt +71 −0
  138. Documentation/devicetree/bindings/arm/ste-nomadik.txt +6 −0
  139. Documentation/devicetree/bindings/arm/sunxi.txt +12 −0
  140. Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-flowctrl.txt +12 −0
  141. Documentation/devicetree/bindings/arm/ux500/power_domain.txt +35 −0
  142. Documentation/devicetree/bindings/ata/marvell.txt +6 −0
  143. Documentation/devicetree/bindings/ata/qcom-sata.txt +48 −0
  144. Documentation/devicetree/bindings/ata/sata_rcar.txt +11 −6
  145. Documentation/devicetree/bindings/btmrvl.txt +29 −0
  146. Documentation/devicetree/bindings/bus/bcma.txt +53 −0
  147. Documentation/devicetree/bindings/bus/brcm,gisb-arb.txt +5 −1
  148. Documentation/devicetree/bindings/bus/mvebu-mbus.txt +10 −7
  149. Documentation/devicetree/bindings/chosen.txt +46 −0
  150. Documentation/devicetree/bindings/clock/arm-integrator.txt +1 −1
  151. Documentation/devicetree/bindings/clock/at91-clock.txt +14 −0
  152. Documentation/devicetree/bindings/clock/bcm-cygnus-clock.txt +34 −0
  153. Documentation/devicetree/bindings/clock/exynos3250-clock.txt +9 −1
  154. Documentation/devicetree/bindings/clock/exynos4415-clock.txt +38 −0
  155. Documentation/devicetree/bindings/clock/exynos7-clock.txt +93 −0
  156. Documentation/devicetree/bindings/clock/gpio-gate-clock.txt +21 −0
  157. Documentation/devicetree/bindings/clock/marvell,mmp2.txt +21 −0
  158. Documentation/devicetree/bindings/clock/marvell,pxa168.txt +21 −0
  159. Documentation/devicetree/bindings/clock/marvell,pxa910.txt +21 −0
  160. Documentation/devicetree/bindings/clock/maxim,max77686.txt +12 −4
  161. Documentation/devicetree/bindings/clock/maxim,max77802.txt +44 −0
  162. Documentation/devicetree/bindings/clock/pxa-clock.txt +16 −0
  163. Documentation/devicetree/bindings/clock/qoriq-clock.txt +12 −2
  164. Documentation/devicetree/bindings/clock/renesas,cpg-div6-clocks.txt +12 −6
  165. Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt +7 −4
  166. Documentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt +1 −0
  167. Documentation/devicetree/bindings/clock/st/st,flexgen.txt +1 −1
  168. Documentation/devicetree/bindings/clock/sunxi.txt +31 −4
  169. Documentation/devicetree/bindings/clock/vf610-clock.txt +15 −0
  170. Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt +0 −64
  171. Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt +64 −0
  172. Documentation/devicetree/bindings/crypto/fsl-imx-sahara.txt +1 −1
  173. Documentation/devicetree/bindings/crypto/fsl-sec6.txt +1 −1
  174. Documentation/devicetree/bindings/dma/atmel-xdma.txt +54 −0
  175. Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt +1 −0
  176. Documentation/devicetree/bindings/dma/qcom_adm.txt +62 −0
  177. Documentation/devicetree/bindings/dma/qcom_bam_dma.txt +3 −1
  178. Documentation/devicetree/bindings/dma/sun6i-dma.txt +1 −1
  179. Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt +65 −0
  180. Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt +1 −1
  181. Documentation/devicetree/bindings/drm/imx/fsl-imx-drm.txt +0 −0
  182. Documentation/devicetree/bindings/drm/imx/hdmi.txt +0 −0
  183. Documentation/devicetree/bindings/drm/imx/ldb.txt +0 −0
  184. Documentation/devicetree/bindings/drm/tilcdc/panel.txt +7 −0
  185. Documentation/devicetree/bindings/extcon/extcon-rt8973a.txt +25 −0
  186. Documentation/devicetree/bindings/gpio/gpio-74xx-mmio.txt +30 −0
  187. Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt +39 −0
  188. Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt +2 −0
  189. Documentation/devicetree/bindings/gpio/gpio-pca953x.txt +39 −0
  190. Documentation/devicetree/bindings/gpio/gpio-restart.txt +54 −0
  191. Documentation/devicetree/bindings/gpio/gpio-vf610.txt +55 −0
  192. Documentation/devicetree/bindings/gpio/gpio-xgene.txt +22 −0
  193. Documentation/devicetree/bindings/gpio/gpio.txt +26 −14
  194. Documentation/devicetree/bindings/gpio/mrvl-gpio.txt +14 −1
  195. Documentation/devicetree/bindings/gpio/pl061-gpio.txt +1 −1
  196. Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt +3 −1
  197. Documentation/devicetree/bindings/gpu/nvidia,tegra20-host1x.txt +2 −0
  198. Documentation/devicetree/bindings/gpu/st,stih4xx.txt +27 −2
  199. Documentation/devicetree/bindings/hwmon/ltc2978.txt +39 −0
  200. Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt +3 −0
  201. Documentation/devicetree/bindings/hwrng/atmel-trng.txt +16 −0
  202. Documentation/devicetree/bindings/i2c/i2c-axxia.txt +30 −0
  203. Documentation/devicetree/bindings/i2c/i2c-designware.txt +2 −2
  204. Documentation/devicetree/bindings/i2c/i2c-exynos5.txt +2 −0
  205. Documentation/devicetree/bindings/i2c/i2c-hix5hd2.txt +24 −0
  206. Documentation/devicetree/bindings/i2c/i2c-img-scb.txt +26 −0
  207. Documentation/devicetree/bindings/i2c/i2c-imx.txt +11 −0
  208. Documentation/devicetree/bindings/i2c/i2c-meson.txt +24 −0
  209. Documentation/devicetree/bindings/i2c/i2c-opal.txt +37 −0
  210. Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt +1 −0
  211. Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt +14 −0
  212. Documentation/devicetree/bindings/i2c/ti,bq32k.txt +18 −0
  213. Documentation/devicetree/bindings/i2c/trivial-devices.txt +11 −2
  214. Documentation/devicetree/bindings/iio/adc/qcom,spmi-iadc.txt +46 −0
  215. Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt +24 −0
  216. Documentation/devicetree/bindings/iio/adc/vf610-adc.txt +1 −1
  217. Documentation/devicetree/bindings/iio/dac/max5821.txt +14 −0
  218. Documentation/devicetree/bindings/interrupt-controller/atmel,aic.txt +1 −1
  219. Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7120-l2-intc.txt +96 −0
  220. Documentation/devicetree/bindings/interrupt-controller/interrupts.txt +0 −4
  221. Documentation/devicetree/bindings/interrupt-controller/mips-gic.txt +55 −0
  222. Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt +7 −1
  223. Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt +32 −0
  224. Documentation/devicetree/bindings/interrupt-controller/ti,keystone-irq.txt +36 −0
  225. Documentation/devicetree/bindings/iommu/arm,smmu.txt +1 −0
  226. Documentation/devicetree/bindings/iommu/rockchip,iommu.txt +26 −0
  227. Documentation/devicetree/bindings/leds/leds-lp8860.txt +29 −0
  228. Documentation/devicetree/bindings/leds/register-bit-led.txt +99 −0
  229. Documentation/devicetree/bindings/mailbox/mailbox.txt +38 −0
  230. Documentation/devicetree/bindings/mailbox/omap-mailbox.txt +131 −0
  231. Documentation/devicetree/bindings/media/hix5hd2-ir.txt +25 −0
  232. Documentation/devicetree/bindings/media/meson-ir.txt +14 −0
  233. Documentation/devicetree/bindings/media/rcar_vin.txt +2 −0
  234. Documentation/devicetree/bindings/media/si4713.txt +30 −0
  235. Documentation/devicetree/bindings/memory-controllers/mvebu-sdram-controller.txt +21 −0
  236. Documentation/devicetree/bindings/memory-controllers/nvidia,tegra-mc.txt +36 −0
  237. Documentation/devicetree/bindings/memory-controllers/synopsys.txt +11 −0
  238. Documentation/devicetree/bindings/mfd/arizona.txt +7 −0
  239. Documentation/devicetree/bindings/mfd/atmel-gpbr.txt +15 −0
  240. Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt +51 −0
  241. Documentation/devicetree/bindings/mfd/hi6421.txt +38 −0
  242. Documentation/devicetree/bindings/mfd/max14577.txt +146 −0
  243. Documentation/devicetree/bindings/mfd/max77686.txt +6 −0
  244. Documentation/devicetree/bindings/mfd/max77693.txt +21 −0
  245. Documentation/devicetree/bindings/mfd/qcom,pm8xxx.txt +0 −96
  246. Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt +64 −0
  247. Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt +97 −0
  248. Documentation/devicetree/bindings/mfd/rk808.txt +177 −0
  249. Documentation/devicetree/bindings/mfd/rn5t618.txt +36 −0
  250. Documentation/devicetree/bindings/mfd/s2mps11.txt +13 −11
  251. Documentation/devicetree/bindings/mfd/stmpe.txt +1 −0
  252. Documentation/devicetree/bindings/mfd/twl4030-power.txt +7 −2
  253. Documentation/devicetree/bindings/mips/brcm/bcm3384-intc.txt +37 −0
  254. Documentation/devicetree/bindings/mips/brcm/bmips.txt +8 −0
  255. Documentation/devicetree/bindings/mips/brcm/cm-dsl.txt +11 −0
  256. Documentation/devicetree/bindings/mips/brcm/usb.txt +11 −0
  257. Documentation/devicetree/bindings/mips/cpu_irq.txt +2 −2
  258. Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt +4 −0
  259. Documentation/devicetree/bindings/mmc/img-dw-mshc.txt +29 −0
  260. Documentation/devicetree/bindings/mmc/mmc.txt +2 −0
  261. Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt +4 −2
  262. Documentation/devicetree/bindings/mmc/sdhci-pxa.txt +7 −0
  263. Documentation/devicetree/bindings/mmc/tmio_mmc.txt +3 −0
  264. Documentation/devicetree/bindings/mtd/atmel-nand.txt +6 −2
  265. Documentation/devicetree/bindings/mtd/diskonchip.txt +15 −0
  266. Documentation/devicetree/bindings/mtd/gpio-control-nand.txt +7 −7
  267. Documentation/devicetree/bindings/mtd/gpmc-nand.txt +3 −3
  268. Documentation/devicetree/bindings/mtd/mtd-physmap.txt +2 −2
  269. Documentation/devicetree/bindings/mtd/sunxi-nand.txt +45 −0
  270. Documentation/devicetree/bindings/net/amd-xgbe.txt +10 −2
  271. Documentation/devicetree/bindings/net/apm-xgene-enet.txt +3 −1
  272. Documentation/devicetree/bindings/net/broadcom-mdio-unimac.txt +39 −0
  273. Documentation/devicetree/bindings/net/broadcom-sf2.txt +78 −0
  274. Documentation/devicetree/bindings/net/can/c_can.txt +5 −0
  275. Documentation/devicetree/bindings/net/can/m_can.txt +67 −0
  276. Documentation/devicetree/bindings/net/can/rcar_can.txt +43 −0
  277. Documentation/devicetree/bindings/net/cpsw.txt +5 −1
  278. Documentation/devicetree/bindings/net/dsa/dsa.txt +25 −1
  279. Documentation/devicetree/bindings/net/emac_rockchip.txt +50 −0
  280. Documentation/devicetree/bindings/net/fsl-fec.txt +6 −0
  281. Documentation/devicetree/bindings/net/marvell-pxa168.txt +36 −0
  282. Documentation/devicetree/bindings/net/meson-dwmac.txt +25 −0
  283. Documentation/devicetree/bindings/net/micrel.txt +27 −8
  284. Documentation/devicetree/bindings/net/nfc/st21nfcb.txt +1 −1
  285. Documentation/devicetree/bindings/net/nfc/trf7970a.txt +8 −0
  286. Documentation/devicetree/bindings/net/phy.txt +2 −1
  287. Documentation/devicetree/bindings/net/qca-qca7000-spi.txt +47 −0
  288. Documentation/devicetree/bindings/net/samsung-sxgbe.txt +1 −1
  289. Documentation/devicetree/bindings/net/sh_eth.txt +1 −0
  290. Documentation/devicetree/bindings/net/smsc-lan91c111.txt +2 −0
  291. Documentation/devicetree/bindings/net/socfpga-dwmac.txt +4 −0
  292. Documentation/devicetree/bindings/net/sti-dwmac.txt +49 −42
  293. Documentation/devicetree/bindings/net/stmmac.txt +1 −1
  294. Documentation/devicetree/bindings/nios2/nios2.txt +62 −0
  295. Documentation/devicetree/bindings/nios2/timer.txt +19 −0
  296. Documentation/devicetree/bindings/panel/auo,b101xtn01.txt +7 −0
  297. Documentation/devicetree/bindings/panel/auo,b116xw03.txt +7 −0
  298. Documentation/devicetree/bindings/panel/hannstar,hsd070pww1.txt +7 −0
  299. Documentation/devicetree/bindings/panel/hit,tx23d38vm0caa.txt +7 −0
  300. Documentation/devicetree/bindings/panel/innolux,g121i1-l01.txt +7 −0
  301. Documentation/devicetree/bindings/panel/sharp,lq101r1sx01.txt +49 −0
  302. Documentation/devicetree/bindings/pci/designware-pcie.txt +3 −0
  303. Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt +3 −1
  304. Documentation/devicetree/bindings/pci/fsl,pci.txt +27 −0
  305. Documentation/devicetree/bindings/pci/host-generic-pci.txt +1 −1
  306. Documentation/devicetree/bindings/pci/layerscape-pci.txt +42 −0
  307. Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt +24 −1
  308. Documentation/devicetree/bindings/pci/pci-keystone.txt +63 −0
  309. Documentation/devicetree/bindings/pci/pci.txt +11 −0
  310. Documentation/devicetree/bindings/pci/xgene-pci.txt +57 −0
  311. Documentation/devicetree/bindings/pci/xilinx-pcie.txt +62 −0
  312. Documentation/devicetree/bindings/phy/berlin-sata-phy.txt +3 −1
  313. Documentation/devicetree/bindings/phy/berlin-usb-phy.txt +16 −0
  314. Documentation/devicetree/bindings/phy/phy-bindings.txt +1 −1
  315. Documentation/devicetree/bindings/phy/phy-miphy28lp.txt +128 −0
  316. Documentation/devicetree/bindings/phy/phy-mvebu.txt +43 −0
  317. Documentation/devicetree/bindings/phy/phy-stih407-usb.txt +30 −0
  318. Documentation/devicetree/bindings/phy/phy-stih41x-usb.txt +24 −0
  319. Documentation/devicetree/bindings/phy/qcom-dwc3-usb-phy.txt +39 −0
  320. Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt +51 −0
  321. Documentation/devicetree/bindings/phy/samsung-phy.txt +11 −2
  322. Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt +15 −7
  323. Documentation/devicetree/bindings/pinctrl/img,tz1090-pdc-pinctrl.txt +1 −1
  324. Documentation/devicetree/bindings/pinctrl/img,tz1090-pinctrl.txt +2 −2
  325. Documentation/devicetree/bindings/pinctrl/lantiq,falcon-pinumx.txt +1 −1
  326. Documentation/devicetree/bindings/pinctrl/lantiq,xway-pinumx.txt +1 −1
  327. Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt +96 −0
  328. Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-pinmux.txt +11 −3
  329. Documentation/devicetree/bindings/pinctrl/nvidia,tegra20-pinmux.txt +1 −1
  330. Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt +40 −12
  331. Documentation/devicetree/bindings/pinctrl/pinctrl-sirf.txt +1 −1
  332. Documentation/devicetree/bindings/pinctrl/pinctrl_spear.txt +1 −1
  333. Documentation/devicetree/bindings/pinctrl/qcom,apq8064-pinctrl.txt +2 −2
  334. Documentation/devicetree/bindings/pinctrl/qcom,apq8084-pinctrl.txt +179 −0
  335. Documentation/devicetree/bindings/pinctrl/qcom,ipq8064-pinctrl.txt +1 −1
  336. Documentation/devicetree/bindings/pinctrl/qcom,msm8960-pinctrl.txt +1 −1
  337. Documentation/devicetree/bindings/pinctrl/qcom,msm8974-pinctrl.txt +1 −1
  338. Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt +215 −0
  339. Documentation/devicetree/bindings/pinctrl/qcom,pmic-mpp.txt +162 −0
  340. Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt +3 −3
  341. Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt +3 −0
  342. Documentation/devicetree/bindings/pinctrl/ste,abx500.txt +75 −109
  343. Documentation/devicetree/bindings/pinctrl/ti,omap-pinctrl.txt +13 −0
  344. Documentation/devicetree/bindings/power/power-controller.txt +18 −0
  345. Documentation/devicetree/bindings/power/power_domain.txt +49 −0
  346. Documentation/devicetree/bindings/power/reset/ltc2952-poweroff.txt +26 −0
  347. Documentation/devicetree/bindings/power/reset/st-reset.txt +11 −0
  348. Documentation/devicetree/bindings/power/reset/syscon-reboot.txt +23 −0
  349. Documentation/devicetree/bindings/power/rockchip-io-domain.txt +83 −0
  350. Documentation/devicetree/bindings/power_supply/charger-manager.txt +1 −1
  351. Documentation/devicetree/bindings/power_supply/gpio-charger.txt +27 −0
  352. Documentation/devicetree/bindings/power_supply/imx-snvs-poweroff.txt +23 −0
  353. Documentation/devicetree/bindings/powerpc/fsl/fman.txt +534 −0
  354. Documentation/devicetree/bindings/pwm/atmel-hlcdc-pwm.txt +29 −0
  355. Documentation/devicetree/bindings/pwm/pwm-bcm2835.txt +30 −0
  356. Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt +18 −1
  357. Documentation/devicetree/bindings/pwm/pwm-rockchip.txt +2 −2
  358. Documentation/devicetree/bindings/regmap/regmap.txt +47 −0
  359. Documentation/devicetree/bindings/regulator/act8865-regulator.txt +4 −0
  360. Documentation/devicetree/bindings/regulator/da9210.txt +2 −2
  361. Documentation/devicetree/bindings/regulator/da9211.txt +63 −0
  362. Documentation/devicetree/bindings/regulator/fan53555.txt +23 −0
  363. Documentation/devicetree/bindings/regulator/isl9305.txt +36 −0
  364. Documentation/devicetree/bindings/regulator/max1586-regulator.txt +28 −0
  365. Documentation/devicetree/bindings/regulator/max77802.txt +88 −0
  366. Documentation/devicetree/bindings/regulator/pwm-regulator.txt +27 −0
  367. Documentation/devicetree/bindings/regulator/regulator.txt +22 −0
  368. Documentation/devicetree/bindings/regulator/sky81452-regulator.txt +18 −0
  369. Documentation/devicetree/bindings/reset/st,sti-picophyreset.txt +42 −0
  370. Documentation/devicetree/bindings/rng/apm,rng.txt +17 −0
  371. Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.txt +23 −0
  372. Documentation/devicetree/bindings/rtc/dallas,ds1339.txt +18 −0
  373. Documentation/devicetree/bindings/rtc/rtc-omap.txt +8 −1
  374. Documentation/devicetree/bindings/rtc/rtc-opal.txt +16 −0
  375. Documentation/devicetree/bindings/rtc/s3c-rtc.txt +3 −0
  376. Documentation/devicetree/bindings/rtc/sun6i-rtc.txt +17 −0
  377. Documentation/devicetree/bindings/serial/bcm63xx-uart.txt +30 −0
  378. Documentation/devicetree/bindings/serial/cirrus,clps711x-uart.txt +5 −2
  379. Documentation/devicetree/bindings/serial/fsl-mxs-auart.txt +9 −1
  380. Documentation/devicetree/bindings/serial/mtk-uart.txt +22 −0
  381. Documentation/devicetree/bindings/serial/of-serial.txt +2 −1
  382. Documentation/devicetree/bindings/serial/pl011.txt +38 −4
  383. Documentation/devicetree/bindings/serial/qcom,msm-uartdm.txt +47 −22
  384. Documentation/devicetree/bindings/serial/renesas,sci-serial.txt +7 −2
  385. Documentation/devicetree/bindings/serial/sirf-uart.txt +15 −1
  386. Documentation/devicetree/bindings/serial/via,vt8500-uart.txt +0 −17
  387. Documentation/devicetree/bindings/serial/vt8500-uart.txt +2 −1
  388. Documentation/devicetree/bindings/soc/fsl/bman-portals.txt +56 −0
  389. Documentation/devicetree/bindings/soc/fsl/bman.txt +125 −0
  390. Documentation/devicetree/bindings/soc/fsl/qman-portals.txt +154 −0
  391. Documentation/devicetree/bindings/soc/fsl/qman.txt +165 −0
  392. Documentation/devicetree/bindings/soc/ti/keystone-navigator-dma.txt +111 −0
  393. Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt +232 −0
  394. Documentation/devicetree/bindings/sound/adi,ssm2602.txt +19 −0
  395. Documentation/devicetree/bindings/sound/arndale.txt +24 −0
  396. Documentation/devicetree/bindings/sound/cs35l32.txt +62 −0
  397. Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt +1 −1
  398. Documentation/devicetree/bindings/sound/es8328.txt +38 −0
  399. Documentation/devicetree/bindings/sound/eukrea-tlv320.txt +10 −5
  400. Documentation/devicetree/bindings/sound/fsl,esai.txt +23 −20
  401. Documentation/devicetree/bindings/sound/fsl,spdif.txt +18 −19
  402. Documentation/devicetree/bindings/sound/fsl,ssi.txt +1 −7
  403. Documentation/devicetree/bindings/sound/fsl-asoc-card.txt +82 −0
  404. Documentation/devicetree/bindings/sound/fsl-sai.txt +50 −20
  405. Documentation/devicetree/bindings/sound/imx-audio-es8328.txt +60 −0
  406. Documentation/devicetree/bindings/sound/imx-audio-sgtl5000.txt +34 −27
  407. Documentation/devicetree/bindings/sound/imx-audio-spdif.txt +12 −10
  408. Documentation/devicetree/bindings/sound/imx-audio-wm8962.txt +26 −19
  409. Documentation/devicetree/bindings/sound/imx-audmux.txt +14 −8
  410. Documentation/devicetree/bindings/sound/max98090.txt +2 −0
  411. Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max98090.txt +1 −0
  412. Documentation/devicetree/bindings/sound/renesas,fsi.txt +7 −2
  413. Documentation/devicetree/bindings/sound/renesas,rsnd.txt +7 −3
  414. Documentation/devicetree/bindings/sound/rt5631.txt +48 −0
  415. Documentation/devicetree/bindings/sound/rt5677.txt +76 −0
  416. Documentation/devicetree/bindings/sound/samsung-i2s.txt +11 −4
  417. Documentation/devicetree/bindings/sound/sgtl5000.txt +23 −0
  418. Documentation/devicetree/bindings/sound/simple-card.txt +4 −0
  419. Documentation/devicetree/bindings/sound/ssm4567.txt +15 −0
  420. Documentation/devicetree/bindings/sound/st,sta350.txt +1 −1
  421. Documentation/devicetree/bindings/sound/ts3a227e.txt +26 −0
  422. Documentation/devicetree/bindings/sound/wm8960.txt +31 −0
  423. Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt +5 −0
  424. Documentation/devicetree/bindings/spi/sh-msiof.txt +19 −4
  425. Documentation/devicetree/bindings/spi/spi-davinci.txt +30 −0
  426. Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt +6 −1
  427. Documentation/devicetree/bindings/spi/spi-gpio.txt +4 −2
  428. Documentation/devicetree/bindings/spi/spi-img-spfi.txt +37 −0
  429. Documentation/devicetree/bindings/spi/spi-meson.txt +22 −0
  430. Documentation/devicetree/bindings/spi/spi-orion.txt +1 −1
  431. Documentation/devicetree/bindings/spi/spi-rspi.txt +9 −1
  432. Documentation/devicetree/bindings/spi/spi-samsung.txt +1 −1
  433. Documentation/devicetree/bindings/submitting-patches.txt +3 −0
  434. Documentation/devicetree/bindings/thermal/armada-thermal.txt +0 −8
  435. Documentation/devicetree/bindings/thermal/imx-thermal.txt +4 −1
  436. Documentation/devicetree/bindings/thermal/rcar-thermal.txt +4 −1
  437. Documentation/devicetree/bindings/thermal/rockchip-thermal.txt +68 −0
  438. Documentation/devicetree/bindings/thermal/tegra-soctherm.txt +53 −0
  439. Documentation/devicetree/bindings/timer/amlogic,meson6-timer.txt +15 −0
  440. Documentation/devicetree/bindings/timer/marvell,armada-370-xp-timer.txt +6 −3
  441. Documentation/devicetree/bindings/timer/renesas,cmt.txt +38 −6
  442. Documentation/devicetree/bindings/timer/renesas,mtu2.txt +6 −3
  443. Documentation/devicetree/bindings/timer/renesas,tmu.txt +8 −3
  444. Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt +41 −0
  445. Documentation/devicetree/bindings/unittest.txt +14 −0
  446. Documentation/devicetree/bindings/usb/ci-hdrc-imx.txt +2 −0
  447. Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt +24 −0
  448. Documentation/devicetree/bindings/usb/dwc2.txt +5 −0
  449. Documentation/devicetree/bindings/usb/dwc3-st.txt +68 −0
  450. Documentation/devicetree/bindings/usb/dwc3.txt +23 −0
  451. Documentation/devicetree/bindings/usb/ehci-st.txt +39 −0
  452. Documentation/devicetree/bindings/usb/exynos-usb.txt +4 −2
  453. Documentation/devicetree/bindings/usb/mxs-phy.txt +1 −0
  454. Documentation/devicetree/bindings/usb/ohci-st.txt +37 −0
  455. Documentation/devicetree/bindings/usb/pxa-usb.txt +22 −0
  456. Documentation/devicetree/bindings/usb/qcom,dwc3.txt +66 −0
  457. Documentation/devicetree/bindings/usb/renesas_usbhs.txt +24 −0
  458. Documentation/devicetree/bindings/usb/udc-xilinx.txt +18 −0
  459. Documentation/devicetree/bindings/usb/usb-ohci.txt +2 −0
  460. Documentation/devicetree/bindings/usb/usb3503.txt +2 −2
  461. Documentation/devicetree/bindings/usb/usbmisc-imx.txt +1 −0
  462. Documentation/devicetree/bindings/vendor-prefixes.txt +28 −2
  463. Documentation/devicetree/bindings/video/adi,adv7123.txt +50 −0
  464. Documentation/devicetree/bindings/video/adi,adv7511.txt +88 −0
  465. Documentation/devicetree/bindings/video/atmel,lcdc.txt +5 −2
  466. Documentation/devicetree/bindings/video/backlight/lp855x.txt +2 −0
  467. Documentation/devicetree/bindings/video/exynos_dsim.txt +2 −0
  468. Documentation/devicetree/bindings/video/fsl,imx-fb.txt +1 −1
  469. Documentation/devicetree/bindings/video/renesas,du.txt +84 −0
  470. Documentation/devicetree/bindings/video/rockchip-drm.txt +19 −0
  471. Documentation/devicetree/bindings/video/rockchip-vop.txt +58 −0
  472. Documentation/devicetree/bindings/video/samsung-fimd.txt +2 −0
  473. Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt +33 −0
  474. Documentation/devicetree/bindings/video/simple-framebuffer.txt +64 −4
  475. Documentation/devicetree/bindings/video/thine,thc63lvdm83d +50 −0
  476. Documentation/devicetree/bindings/video/vga-connector.txt +36 −0
  477. Documentation/devicetree/bindings/w1/omap-hdq.txt +17 −0
  478. Documentation/devicetree/bindings/watchdog/cadence-wdt.txt +24 −0
  479. Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.txt +2 −1
  480. Documentation/devicetree/bindings/watchdog/marvel.txt +13 −0
  481. Documentation/devicetree/bindings/watchdog/meson6-wdt.txt +13 −0
  482. Documentation/devicetree/bindings/watchdog/qcom-wdt.txt +24 −0
  483. Documentation/devicetree/bindings/watchdog/samsung-wdt.txt +1 −0
  484. Documentation/devicetree/bindings/xillybus/xillybus.txt +0 −0
  485. Documentation/devicetree/booting-without-of.txt +53 −0
  486. Documentation/devicetree/dynamic-resolution-notes.txt +25 −0
  487. Documentation/devicetree/of_selftest.txt +15 −29
  488. Documentation/devicetree/overlay-notes.txt +133 −0
  489. Documentation/devicetree/todo.txt +0 −1
  490. Documentation/dmaengine.txt +0 −199
  491. Documentation/dmaengine/client.txt +199 −0
  492. Documentation/dmaengine/dmatest.txt +0 −0
  493. Documentation/dmaengine/provider.txt +366 −0
  494. Documentation/driver-model/devres.txt +7 −0
  495. Documentation/dvb/get_dvb_firmware +13 −11
  496. Documentation/email-clients.txt +11 −0
  497. Documentation/filesystems/.gitignore +1 −0
  498. Documentation/filesystems/Locking +8 −5
  499. Documentation/filesystems/Makefile +1 −2
  500. Documentation/filesystems/autofs4.txt +520 −0
  501. Documentation/filesystems/debugfs.txt +1 −1
  502. Documentation/filesystems/f2fs.txt +17 −3
  503. Documentation/filesystems/nfs/Exporting +5 −18
  504. Documentation/filesystems/ntfs.txt +0 −268
  505. Documentation/filesystems/overlayfs.txt +198 −0
  506. Documentation/filesystems/porting +8 −0
  507. Documentation/filesystems/proc.txt +1 −1
  508. Documentation/filesystems/seq_file.txt +13 −9
  509. Documentation/filesystems/squashfs.txt +4 −4
  510. Documentation/filesystems/vfs.txt +13 −5
  511. Documentation/gpio/consumer.txt +45 −0
  512. Documentation/gpio/driver.txt +6 −4
  513. Documentation/hid/uhid.txt +92 −87
  514. Documentation/hwmon/k10temp +1 −1
  515. Documentation/hwmon/lm75 +5 −0
  516. Documentation/hwmon/lm95234 +10 −5
  517. Documentation/hwmon/lm95245 +9 −5
  518. Documentation/hwmon/menf21bmc +50 −0
  519. Documentation/hwmon/nct6775 +13 −1
  520. Documentation/hwmon/nct7802 +32 −0
  521. Documentation/hwmon/tmp401 +6 −2
  522. Documentation/i2c/busses/i2c-i801 +2 −0
  523. Documentation/i2c/upgrading-clients +2 −4
  524. Documentation/i2c/writing-clients +4 −4
  525. Documentation/ia64/Makefile +0 −3
  526. Documentation/ia64/kvm.txt +0 −83
  527. Documentation/input/elantech.txt +75 −6
  528. Documentation/input/xpad.txt +83 −40
  529. Documentation/ioctl/ioctl-number.txt +1 −0
  530. Documentation/kbuild/makefiles.txt +35 −59
  531. Documentation/kdump/kdump.txt +7 −0
  532. Documentation/kernel-parameters.txt +221 −25
  533. Documentation/kmemleak.txt +5 −1
  534. Documentation/kobject.txt +1 −1
  535. Documentation/kprobes.txt +1 −0
  536. Documentation/kselftest.txt +69 −0
  537. Documentation/laptops/.gitignore +2 −0
  538. Documentation/laptops/Makefile +1 −4
  539. Documentation/local_ops.txt +9 −4
  540. Documentation/locking/lglock.txt +166 −0
  541. Documentation/locking/lockdep-design.txt +0 −0
  542. Documentation/locking/lockstat.txt +1 −1
  543. Documentation/locking/locktorture.txt +147 −0
  544. Documentation/locking/mutex-design.txt +3 −3
  545. Documentation/locking/rt-mutex-design.txt +0 −0
  546. Documentation/locking/rt-mutex.txt +0 −0
  547. Documentation/locking/spinlocks.txt +7 −7
  548. Documentation/locking/ww-mutex-design.txt +0 −0
  549. Documentation/lockup-watchdogs.txt +1 −1
  550. Documentation/lzo.txt +164 −0
  551. Documentation/mailbox.txt +122 −0
  552. Documentation/memory-barriers.txt +145 −76
  553. Documentation/memory-hotplug.txt +10 −1
  554. Documentation/mic/Makefile +1 −0
  555. Documentation/mic/mpssd/Makefile +12 −12
  556. Documentation/mic/mpssd/mpssd.c +3 −2
  557. Documentation/mips/AU1xxx_IDE.README +1 −1
  558. Documentation/misc-devices/Makefile +1 −0
  559. Documentation/misc-devices/mei/Makefile +0 −3
  560. Documentation/networking/Makefile +1 −7
  561. Documentation/networking/bonding.txt +2 −5
  562. Documentation/networking/dctcp.txt +43 −0
  563. Documentation/networking/fib_trie.txt +2 −2
  564. Documentation/networking/filter.txt +275 −6
  565. Documentation/networking/ip-sysctl.txt +68 −15
  566. Documentation/networking/ipvlan.txt +107 −0
  567. Documentation/networking/ixgbe.txt +1 −1
  568. Documentation/networking/pktgen.txt +3 −0
  569. Documentation/networking/stmmac.txt +65 −67
  570. Documentation/networking/switchdev.txt +59 −0
  571. Documentation/networking/timestamping.txt +303 −82
  572. Documentation/networking/timestamping/.gitignore +1 −0
  573. Documentation/networking/timestamping/Makefile +6 −6
  574. Documentation/networking/timestamping/txtimestamp.c +535 −0
  575. Documentation/nios2/README +23 −0
  576. Documentation/pcmcia/Makefile +0 −3
  577. Documentation/phy.txt +16 −44
  578. Documentation/pinctrl.txt +2 −12
  579. Documentation/power/charger-manager.txt +1 −1
  580. Documentation/power/pm_qos_interface.txt +3 −1
  581. Documentation/power/power_supply_class.txt +6 −0
  582. Documentation/power/runtime_pm.txt +7 −3
  583. Documentation/power/suspend-and-interrupts.txt +123 −0
  584. Documentation/power/userland-swsusp.txt +1 −1
  585. Documentation/powerpc/00-INDEX +2 −0
  586. Documentation/powerpc/cxl.txt +379 −0
  587. Documentation/prctl/.gitignore +3 −0
  588. Documentation/prctl/Makefile +8 −0
  589. Documentation/prctl/disable-tsc-ctxt-sw-stress-test.c +6 −5
  590. Documentation/prctl/disable-tsc-on-off-stress-test.c +4 −3
  591. Documentation/prctl/disable-tsc-test.c +3 −2
  592. Documentation/printk-formats.txt +32 −0
  593. Documentation/ptp/.gitignore +1 −0
  594. Documentation/ptp/Makefile +8 −0
  595. Documentation/ptp/testptp.c +3 −3
  596. Documentation/ramoops.txt +11 −2
  597. Documentation/s390/Debugging390.txt +61 −401
  598. Documentation/scheduler/sched-deadline.txt +292 −48
  599. Documentation/scsi/ChangeLog.megaraid_sas +14 −0
  600. Documentation/scsi/libsas.txt +4 −78
  601. Documentation/scsi/osd.txt +1 −2
  602. Documentation/scsi/scsi_eh.txt +2 −2
  603. Documentation/scsi/scsi_mid_low_api.txt +13 −53
  604. Documentation/scsi/st.txt +5 −3
  605. Documentation/scsi/wd719x.txt +21 −0
  606. Documentation/security/IMA-templates.txt +14 −15
  607. Documentation/security/keys.txt +52 −13
  608. Documentation/serial/driver +6 −2
  609. Documentation/serial/serial-rs485.txt +1 −1
  610. Documentation/serial/tty.txt +2 −2
  611. Documentation/sound/alsa/ControlNames.txt +27 −5
  612. Documentation/sound/alsa/HD-Audio-Models.txt +2 −6
  613. Documentation/sound/alsa/Procfile.txt +4 −13
  614. Documentation/spi/Makefile +0 −3
  615. Documentation/spi/spi-summary +3 −3
  616. Documentation/sysctl/kernel.txt +34 −18
  617. Documentation/sysctl/net.txt +46 −4
  618. Documentation/sysfs-rules.txt +21 −0
  619. Documentation/target/tcmu-design.txt +378 −0
  620. Documentation/this_cpu_ops.txt +0 −2
  621. Documentation/timers/.gitignore +1 −0
  622. Documentation/timers/Makefile +0 −3
  623. Documentation/trace/coresight.txt +299 −0
  624. Documentation/trace/ftrace.txt +12 −3
  625. Documentation/usb/WUSB-Design-overview.txt +7 −16
  626. Documentation/usb/gadget_configfs.txt +1 −1
  627. Documentation/usb/gadget_hid.txt +7 −0
  628. Documentation/usb/hotplug.txt +1 −1
  629. Documentation/usb/power-management.txt +9 −8
  630. Documentation/usb/usb-serial.txt +1 −1
  631. Documentation/vDSO/.gitignore +2 −0
  632. Documentation/vDSO/Makefile +15 −0
  633. Documentation/vDSO/vdso_standalone_test_x86.c +1 −1
  634. Documentation/video4linux/.gitignore +0 −1
  635. Documentation/video4linux/CARDLIST.cx23885 +2 −0
  636. Documentation/video4linux/CARDLIST.em28xx +1 −0
  637. Documentation/video4linux/CARDLIST.saa7134 +1 −0
  638. Documentation/video4linux/Makefile +1 −0
  639. Documentation/video4linux/soc-camera.txt +1 −1
  640. Documentation/video4linux/vivid.txt +1124 −0
  641. Documentation/virtual/kvm/api.txt +190 −100
  642. Documentation/virtual/kvm/devices/arm-vgic.txt +10 −0
  643. Documentation/virtual/kvm/devices/vm.txt +5 −5
  644. Documentation/virtual/kvm/mmu.txt +14 −0
  645. Documentation/virtual/kvm/msr.txt +1 −1
  646. Documentation/vm/hugetlbpage.txt +3 −3
  647. Documentation/vm/page_owner.txt +81 −0
  648. Documentation/watchdog/Makefile +1 −0
  649. Documentation/watchdog/src/Makefile +0 −3
  650. Documentation/x86/entry_64.txt +5 −2
  651. Documentation/x86/intel_mpx.txt +244 −0
  652. Documentation/x86/x86_64/mm.txt +1 −1
  653. Documentation/xillybus.txt +0 −0
  654. MAINTAINERS +626 −202
  655. Makefile +69 −63
  656. arch/Kconfig +11 −0
  657. arch/alpha/include/asm/Kbuild +2 −1
  658. arch/alpha/include/asm/atomic.h +82 −135
  659. arch/alpha/include/asm/barrier.h +51 −0
  660. arch/alpha/include/asm/sections.h +0 −7
  661. arch/alpha/include/asm/syscall.h +11 −0
  662. arch/alpha/include/uapi/asm/ioctls.h +2 −0
  663. arch/alpha/include/uapi/asm/socket.h +5 −0
  664. arch/alpha/kernel/osf_sys.c +14 −16
  665. arch/alpha/kernel/perf_event.c +8 −8
  666. arch/alpha/kernel/ptrace.c +1 −1
  667. arch/alpha/kernel/time.c +3 −3
  668. arch/arc/Kconfig +3 −4
  669. arch/arc/Makefile +2 −17
  670. arch/arc/boot/dts/angel4.dts +0 −5
  671. arch/arc/boot/dts/nsimosci.dts +9 −14
  672. arch/arc/configs/fpga_defconfig +0 −68
  673. arch/arc/configs/fpga_noramfs_defconfig +0 −64
  674. arch/arc/configs/nsim_700_defconfig +67 −0
  675. arch/arc/configs/nsimosci_defconfig +0 −1
  676. arch/arc/include/asm/Kbuild +1 −1
  677. arch/arc/include/asm/arcregs.h +53 −36
  678. arch/arc/include/asm/atomic.h +63 −125
  679. arch/arc/include/asm/bitops.h +0 −4
  680. arch/arc/include/asm/bug.h +3 −4
  681. arch/arc/include/asm/cache.h +1 −1
  682. arch/arc/include/asm/current.h +0 −4
  683. arch/arc/include/asm/io.h +0 −2
  684. arch/arc/include/asm/irqflags.h +9 −4
  685. arch/arc/include/asm/kgdb.h +18 −14
  686. arch/arc/include/asm/processor.h +9 −4
  687. arch/arc/include/asm/setup.h +0 −1
  688. arch/arc/include/asm/smp.h +9 −1
  689. arch/arc/include/asm/string.h +0 −3
  690. arch/arc/include/asm/syscalls.h +0 −4
  691. arch/arc/include/asm/thread_info.h +0 −4
  692. arch/arc/include/asm/unaligned.h +1 −1
  693. arch/arc/kernel/Makefile +1 −1
  694. arch/arc/kernel/disasm.c +2 −2
  695. arch/arc/kernel/head.S +0 −10
  696. arch/arc/kernel/kgdb.c +0 −5
  697. arch/arc/kernel/perf_event.c +10 −12
  698. arch/arc/kernel/setup.c +133 −139
  699. arch/arc/kernel/smp.c +3 −1
  700. arch/arc/mm/cache_arc700.c +5 −9
  701. arch/arc/mm/tlb.c +3 −5
  702. arch/arc/plat-arcfpga/Kconfig +1 −12
  703. arch/arc/plat-arcfpga/include/plat/irq.h +0 −27
  704. arch/arc/plat-arcfpga/include/plat/memmap.h +0 −29
  705. arch/arc/plat-arcfpga/platform.c +9 −52
  706. arch/arc/plat-arcfpga/smp.c +2 −1
  707. arch/arc/plat-tb10x/Kconfig +0 −1
  708. arch/arc/plat-tb10x/tb10x.c +0 −13
  709. arch/arm/Kconfig +32 −24
  710. arch/arm/Kconfig.debug +279 −27
  711. arch/arm/Makefile +8 −5
  712. arch/arm/boot/bootp/Makefile +2 −0
  713. arch/arm/boot/compressed/Makefile +2 −0
  714. arch/arm/boot/compressed/head.S +16 −4
  715. arch/arm/boot/dts/Makefile +87 −31
  716. arch/arm/boot/dts/am335x-bone-common.dtsi +5 −3
  717. arch/arm/boot/dts/am335x-bone.dts +5 −0
  718. arch/arm/boot/dts/am335x-boneblack.dts +9 −0
  719. arch/arm/boot/dts/am335x-evm.dts +16 −3
  720. arch/arm/boot/dts/am335x-igep0033.dtsi +2 −2
  721. arch/arm/boot/dts/am335x-lxm.dts +362 −0
  722. arch/arm/boot/dts/am33xx.dtsi +38 −14
  723. arch/arm/boot/dts/am4372.dtsi +64 −1
  724. arch/arm/boot/dts/am437x-gp-evm.dts +36 −2
  725. arch/arm/boot/dts/am437x-sk-evm.dts +9 −10
  726. arch/arm/boot/dts/am43x-epos-evm.dts +12 −4
  727. arch/arm/boot/dts/am57xx-beagle-x15.dts +405 −0
  728. arch/arm/boot/dts/arm-realview-pb1176.dts +412 −0
  729. arch/arm/boot/dts/armada-370-db.dts +58 −30
  730. arch/arm/boot/dts/armada-370-mirabox.dts +19 −12
  731. arch/arm/boot/dts/armada-370-netgear-rn102.dts +60 −51
  732. arch/arm/boot/dts/armada-370-netgear-rn104.dts +43 −33
  733. arch/arm/boot/dts/armada-370-rd.dts +90 −6
  734. arch/arm/boot/dts/armada-370-synology-ds213j.dts +316 −0
  735. arch/arm/boot/dts/armada-370-xp.dtsi +12 −6
  736. arch/arm/boot/dts/armada-370.dtsi +128 −47
  737. arch/arm/boot/dts/armada-375.dtsi +27 −2
  738. arch/arm/boot/dts/armada-385-db.dts +1 −1
  739. arch/arm/boot/dts/armada-38x.dtsi +3 −3
  740. arch/arm/boot/dts/armada-xp-axpwifiap.dts +18 −39
  741. arch/arm/boot/dts/armada-xp-gp.dts +18 −1
  742. arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts +42 −33
  743. arch/arm/boot/dts/armada-xp-mv78230.dtsi +4 −11
  744. arch/arm/boot/dts/armada-xp-mv78260.dtsi +4 −11
  745. arch/arm/boot/dts/armada-xp-mv78460.dtsi +4 −11
  746. arch/arm/boot/dts/armada-xp-netgear-rn2120.dts +91 −81
  747. arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts +8 −6
  748. arch/arm/boot/dts/armada-xp-synology-ds414.dts +330 −0
  749. arch/arm/boot/dts/armada-xp.dtsi +69 −2
  750. arch/arm/boot/dts/at91-sama5d4ek.dts +260 −0
  751. arch/arm/boot/dts/at91sam9260.dtsi +14 −0
  752. arch/arm/boot/dts/at91sam9261.dtsi +14 −0
  753. arch/arm/boot/dts/at91sam9263.dtsi +52 −5
  754. arch/arm/boot/dts/at91sam9g20.dtsi +4 −0
  755. arch/arm/boot/dts/at91sam9g20ek_common.dtsi +14 −0
  756. arch/arm/boot/dts/at91sam9g45.dtsi +96 −4
  757. arch/arm/boot/dts/at91sam9m10g45ek.dts +13 −0
  758. arch/arm/boot/dts/at91sam9n12.dtsi +2 −0
  759. arch/arm/boot/dts/at91sam9n12ek.dts +2 −0
  760. arch/arm/boot/dts/at91sam9rl.dtsi +23 −2
  761. arch/arm/boot/dts/at91sam9x25.dtsi +1 −0
  762. arch/arm/boot/dts/at91sam9x35.dtsi +1 −0
  763. arch/arm/boot/dts/at91sam9x5.dtsi +15 −1
  764. arch/arm/boot/dts/at91sam9x5_can.dtsi +45 −5
  765. arch/arm/boot/dts/at91sam9x5_usart3.dtsi +3 −0
  766. arch/arm/boot/dts/atlas6.dtsi +15 −0
  767. arch/arm/boot/dts/bcm-cygnus-clock.dtsi +91 −0
  768. arch/arm/boot/dts/bcm-cygnus.dtsi +140 −0
  769. arch/arm/boot/dts/bcm2835-rpi-b-plus.dts +30 −0
  770. arch/arm/boot/dts/bcm2835-rpi-b.dts +6 −40
  771. arch/arm/boot/dts/bcm2835-rpi.dtsi +51 −0
  772. arch/arm/boot/dts/bcm2835.dtsi +1 −0
  773. arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts +64 −0
  774. arch/arm/boot/dts/bcm4708-netgear-r6250.dts +59 −0
  775. arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts +84 −0
  776. arch/arm/boot/dts/bcm47081-asus-rt-n18u.dts +78 −0
  777. arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dts +57 −0
  778. arch/arm/boot/dts/bcm47081.dtsi +26 −0
  779. arch/arm/boot/dts/bcm5301x.dtsi +51 −0
  780. arch/arm/boot/dts/bcm63138.dtsi +134 −0
  781. arch/arm/boot/dts/bcm911360_entphn.dts +53 −0
  782. arch/arm/boot/dts/bcm911360k.dts +53 −0
  783. arch/arm/boot/dts/bcm958300k.dts +53 −0
  784. arch/arm/boot/dts/bcm963138dvt.dts +30 −0
  785. arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts +16 −0
  786. arch/arm/boot/dts/berlin2.dtsi +110 −0
  787. arch/arm/boot/dts/berlin2cd-google-chromecast.dts +30 −0
  788. arch/arm/boot/dts/berlin2cd.dtsi +82 −0
  789. arch/arm/boot/dts/berlin2q-marvell-dmp.dts +65 −0
  790. arch/arm/boot/dts/berlin2q.dtsi +112 −1
  791. arch/arm/boot/dts/cros-adc-thermistors.dtsi +44 −0
  792. arch/arm/boot/dts/da850-evm.dts +72 −0
  793. arch/arm/boot/dts/da850.dtsi +19 −0
  794. arch/arm/boot/dts/dra7-evm.dts +137 −2
  795. arch/arm/boot/dts/dra7.dtsi +194 −35
  796. arch/arm/boot/dts/dra72-evm.dts +439 −0
  797. arch/arm/boot/dts/dra72x.dtsi +5 −0
  798. arch/arm/boot/dts/dra74x.dtsi +28 −0
  799. arch/arm/boot/dts/dra7xx-clocks.dtsi +3 −3
  800. arch/arm/boot/dts/emev2-kzm9d.dts +32 −31
  801. arch/arm/boot/dts/emev2.dtsi +6 −6
  802. arch/arm/boot/dts/exynos3250-monk.dts +579 −0
  803. arch/arm/boot/dts/exynos3250-pinctrl.dtsi +16 −0
  804. arch/arm/boot/dts/exynos3250-rinato.dts +682 −0
  805. arch/arm/boot/dts/exynos3250.dtsi +52 −2
  806. arch/arm/boot/dts/exynos4.dtsi +2 −2
  807. arch/arm/boot/dts/exynos4210-trats.dts +16 −0
  808. arch/arm/boot/dts/exynos4210-universal_c210.dts +16 −0
  809. arch/arm/boot/dts/exynos4210.dtsi +17 −0
  810. arch/arm/boot/dts/exynos4212.dtsi +17 −0
  811. arch/arm/boot/dts/exynos4412-odroid-common.dtsi +28 −6
  812. arch/arm/boot/dts/exynos4412-origen.dts +2 −6
  813. arch/arm/boot/dts/exynos4412-trats2.dts +406 −12
  814. arch/arm/boot/dts/exynos4412.dtsi +29 −0
  815. arch/arm/boot/dts/exynos4415-pinctrl.dtsi +573 −0
  816. arch/arm/boot/dts/exynos4415.dtsi +604 −0
  817. arch/arm/boot/dts/exynos4x12-pinctrl.dtsi +17 −1
  818. arch/arm/boot/dts/exynos4x12.dtsi +12 −1
  819. arch/arm/boot/dts/exynos5250-arndale.dts +450 −465
  820. arch/arm/boot/dts/exynos5250-cros-common.dtsi +0 −164
  821. arch/arm/boot/dts/exynos5250-smdk5250.dts +311 −315
  822. arch/arm/boot/dts/exynos5250-snow.dts +277 −154
  823. arch/arm/boot/dts/exynos5250-spring.dts +566 −0
  824. arch/arm/boot/dts/exynos5250.dtsi +15 −25
  825. arch/arm/boot/dts/exynos5260-xyref5260.dts +5 −13
  826. arch/arm/boot/dts/exynos5410-smdk5410.dts +5 −13
  827. arch/arm/boot/dts/exynos5420-arndale-octa.dts +10 −13
  828. arch/arm/boot/dts/exynos5420-peach-pit.dts +459 −36
  829. arch/arm/boot/dts/exynos5420-smdk5420.dts +4 −12
  830. arch/arm/boot/dts/exynos5420.dtsi +8 −3
  831. arch/arm/boot/dts/exynos5800-peach-pi.dts +449 −36
  832. arch/arm/boot/dts/hip04-d01.dts +32 −0
  833. arch/arm/boot/dts/hip04.dtsi +984 −0
  834. arch/arm/boot/dts/hisi-x5hd2-dkb.dts +33 −0
  835. arch/arm/boot/dts/hisi-x5hd2.dtsi +388 −2
  836. arch/arm/boot/dts/imx1-ads.dts +152 −0
  837. arch/arm/boot/dts/imx1-apf9328.dts +129 −0
  838. arch/arm/boot/dts/imx1-pinfunc.h +302 −0
  839. arch/arm/boot/dts/imx1.dtsi +266 −0
  840. arch/arm/boot/dts/imx23-evk.dts +2 −2
  841. arch/arm/boot/dts/imx25-pinfunc.h +31 −2
  842. arch/arm/boot/dts/imx25.dtsi +3 −1
  843. arch/arm/boot/dts/imx27-apf27dev.dts +17 −0
  844. arch/arm/boot/dts/imx28-apf28dev.dts +2 −2
  845. arch/arm/boot/dts/imx28-apx4devkit.dts +2 −2
  846. arch/arm/boot/dts/imx28-cfa10049.dts +2 −2
  847. arch/arm/boot/dts/imx28-cfa10055.dts +2 −2
  848. arch/arm/boot/dts/imx28-cfa10056.dts +2 −2
  849. arch/arm/boot/dts/imx28-cfa10057.dts +2 −2
  850. arch/arm/boot/dts/imx28-cfa10058.dts +2 −2
  851. arch/arm/boot/dts/imx28-evk.dts +2 −3
  852. arch/arm/boot/dts/imx28-m28cu3.dts +2 −2
  853. arch/arm/boot/dts/imx28-m28evk.dts +2 −2
  854. arch/arm/boot/dts/imx28-tx28.dts +84 −23
  855. arch/arm/boot/dts/imx28.dtsi +43 −0
  856. arch/arm/boot/dts/imx35.dtsi +1 −0
  857. arch/arm/boot/dts/imx50.dtsi +2 −0
  858. arch/arm/boot/dts/imx51.dtsi +12 −3
  859. arch/arm/boot/dts/imx53-smd.dts +1 −1
  860. arch/arm/boot/dts/imx53.dtsi +29 −4
  861. arch/arm/boot/dts/imx6dl-gw552x.dts +20 −0
  862. arch/arm/boot/dts/imx6dl-hummingboard.dts +5 −198
  863. arch/arm/boot/dts/imx6dl.dtsi +8 −0
  864. arch/arm/boot/dts/imx6q-gw5400-a.dts +90 −113
  865. arch/arm/boot/dts/imx6q-gw552x.dts +24 −0
  866. arch/arm/boot/dts/imx6q-hummingboard.dts +21 −0
  867. arch/arm/boot/dts/imx6q-tbs2910.dts +432 −0
  868. arch/arm/boot/dts/imx6q.dtsi +4 −0
  869. arch/arm/boot/dts/imx6qdl-gw51xx.dtsi +73 −119
  870. arch/arm/boot/dts/imx6qdl-gw52xx.dtsi +129 −184
  871. arch/arm/boot/dts/imx6qdl-gw53xx.dtsi +122 −215
  872. arch/arm/boot/dts/imx6qdl-gw54xx.dtsi +124 −152
  873. arch/arm/boot/dts/imx6qdl-gw552x.dtsi +267 −0
  874. arch/arm/boot/dts/imx6qdl-hummingboard.dtsi +200 −0
  875. arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi +38 −0
  876. arch/arm/boot/dts/imx6qdl-phytec-pbab01.dtsi +105 −26
  877. arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi +82 −17
  878. arch/arm/boot/dts/imx6qdl-rex.dtsi +0 −1
  879. arch/arm/boot/dts/imx6qdl-sabresd.dtsi +39 −18
  880. arch/arm/boot/dts/imx6qdl.dtsi +32 −6
  881. arch/arm/boot/dts/imx6sl-evk.dts +102 −6
  882. arch/arm/boot/dts/imx6sl.dtsi +33 −4
  883. arch/arm/boot/dts/imx6sx-sdb.dts +159 −0
  884. arch/arm/boot/dts/imx6sx.dtsi +15 −2
  885. arch/arm/boot/dts/integrator.dtsi +47 −1
  886. arch/arm/boot/dts/k2e-evm.dts +12 −0
  887. arch/arm/boot/dts/k2e.dtsi +58 −0
  888. arch/arm/boot/dts/k2hk.dtsi +56 −0
  889. arch/arm/boot/dts/k2l-evm.dts +12 −0
  890. arch/arm/boot/dts/k2l.dtsi +46 −0
  891. arch/arm/boot/dts/keystone.dtsi +54 −1
  892. arch/arm/boot/dts/kirkwood-dir665.dts +278 −0
  893. arch/arm/boot/dts/kirkwood-mv88f6281gtw-ge.dts +6 −10
  894. arch/arm/boot/dts/kirkwood-rd88f6281-a.dts +43 −0
  895. arch/arm/boot/dts/kirkwood-rd88f6281-a0.dts +0 −26
  896. arch/arm/boot/dts/kirkwood-rd88f6281-a1.dts +0 −31
  897. arch/arm/boot/dts/kirkwood-rd88f6281-z0.dts +35 −0
  898. arch/arm/boot/dts/kirkwood-rd88f6281.dtsi +5 −22
  899. arch/arm/boot/dts/kirkwood-synology.dtsi +1 −1
  900. arch/arm/boot/dts/kirkwood.dtsi +2 −2
  901. arch/arm/boot/dts/ls1021a-qds.dts +240 −0
  902. arch/arm/boot/dts/ls1021a-twr.dts +127 −0
  903. arch/arm/boot/dts/ls1021a.dtsi +408 −0
  904. arch/arm/boot/dts/meson.dtsi +154 −0
  905. arch/arm/boot/dts/meson6-atv1200.dts +66 −0
  906. arch/arm/boot/dts/meson6.dtsi +80 −0
  907. arch/arm/boot/dts/meson8.dtsi +92 −0
  908. arch/arm/boot/dts/mmp2-brownstone.dts +1 −1
  909. arch/arm/boot/dts/mmp2.dtsi +28 −1
  910. arch/arm/boot/dts/mt6589-aquaris5.dts +5 −0
  911. arch/arm/boot/dts/mt6589.dtsi +2 −2
  912. arch/arm/boot/dts/mt6592-evb.dts +26 −0
  913. arch/arm/boot/dts/mt6592.dtsi +98 −0
  914. arch/arm/boot/dts/mt8127-moose.dts +25 −0
  915. arch/arm/boot/dts/mt8127.dtsi +94 −0
  916. arch/arm/boot/dts/mt8135-evbp1.dts +25 −0
  917. arch/arm/boot/dts/mt8135.dtsi +116 −0
  918. arch/arm/boot/dts/omap-gpmc-smsc911x.dtsi +23 −18
  919. arch/arm/boot/dts/omap-zoom-common.dtsi +60 −2
  920. arch/arm/boot/dts/omap2.dtsi +0 −1
  921. arch/arm/boot/dts/omap2420-n810.dts +7 −0
  922. arch/arm/boot/dts/omap2420-n8x0-common.dtsi +8 −2
  923. arch/arm/boot/dts/omap2420.dtsi +9 −0
  924. arch/arm/boot/dts/omap2430-sdp.dts +26 −2
  925. arch/arm/boot/dts/omap2430.dtsi +5 −0
  926. arch/arm/boot/dts/omap3-beagle-xm.dts +30 −2
  927. arch/arm/boot/dts/omap3-beagle.dts +28 −0
  928. arch/arm/boot/dts/omap3-cm-t3517.dts +11 −0
  929. arch/arm/boot/dts/omap3-cm-t3530.dts +11 −0
  930. arch/arm/boot/dts/omap3-cm-t3730.dts +24 −0
  931. arch/arm/boot/dts/omap3-cm-t3x.dtsi +151 −0
  932. arch/arm/boot/dts/omap3-cm-t3x30.dtsi +35 −0
  933. arch/arm/boot/dts/omap3-devkit8000.dts +2 −2
  934. arch/arm/boot/dts/omap3-evm-37xx.dts +3 −2
  935. arch/arm/boot/dts/omap3-evm-common.dtsi +21 −0
  936. arch/arm/boot/dts/omap3-gta04.dts +0 −311
  937. arch/arm/boot/dts/omap3-gta04.dtsi +451 −0
  938. arch/arm/boot/dts/omap3-gta04a3.dts +48 −0
  939. arch/arm/boot/dts/omap3-gta04a4.dts +13 −0
  940. arch/arm/boot/dts/omap3-gta04a5.dts +17 −0
  941. arch/arm/boot/dts/omap3-ha-common.dtsi +88 −0
  942. arch/arm/boot/dts/omap3-ha-lcd.dts +165 −0
  943. arch/arm/boot/dts/omap3-ha.dts +28 −0
  944. arch/arm/boot/dts/omap3-igep.dtsi +49 −54
  945. arch/arm/boot/dts/omap3-igep0020-common.dtsi +246 −0
  946. arch/arm/boot/dts/omap3-igep0020-rev-f.dts +45 −0
  947. arch/arm/boot/dts/omap3-igep0020.dts +36 −249
  948. arch/arm/boot/dts/omap3-igep0030-common.dtsi +60 −0
  949. arch/arm/boot/dts/omap3-igep0030-rev-g.dts +67 −0
  950. arch/arm/boot/dts/omap3-igep0030.dts +44 −79
  951. arch/arm/boot/dts/omap3-ldp.dts +29 −2
  952. arch/arm/boot/dts/omap3-lilly-a83x.dtsi +1 −1
  953. arch/arm/boot/dts/omap3-n900.dts +100 −10
  954. arch/arm/boot/dts/omap3-n950-n9.dtsi +2 −2
  955. arch/arm/boot/dts/omap3-overo-common-peripherals.dtsi +3 −2
  956. arch/arm/boot/dts/omap3-sb-t35.dtsi +108 −18
  957. arch/arm/boot/dts/omap3-sbc-t3517.dts +15 −0
  958. arch/arm/boot/dts/omap3-sbc-t3530.dts +15 −0
  959. arch/arm/boot/dts/omap3-sbc-t3730.dts +15 −0
  960. arch/arm/boot/dts/omap3-tao3530.dtsi +337 −0
  961. arch/arm/boot/dts/omap3-thunder.dts +129 −0
  962. arch/arm/boot/dts/omap3.dtsi +8 −3
  963. arch/arm/boot/dts/omap3430-sdp.dts +4 −4
  964. arch/arm/boot/dts/omap4-duovero-parlor.dts +1 −0
  965. arch/arm/boot/dts/omap4-panda-common.dtsi +0 −3
  966. arch/arm/boot/dts/omap4-panda-es.dts +5 −0
  967. arch/arm/boot/dts/omap4-panda.dts +5 −0
  968. arch/arm/boot/dts/omap4.dtsi +17 −1
  969. arch/arm/boot/dts/omap44xx-clocks.dtsi +0 −8
  970. arch/arm/boot/dts/omap5-cm-t54.dts +270 −2
  971. arch/arm/boot/dts/omap5-sbc-t54.dts +4 −4
  972. arch/arm/boot/dts/omap5.dtsi +38 −9
  973. arch/arm/boot/dts/prima2.dtsi +33 −0
  974. arch/arm/boot/dts/pxa168-aspenite.dts +1 −1
  975. arch/arm/boot/dts/pxa168.dtsi +26 −1
  976. arch/arm/boot/dts/pxa27x.dtsi +19 −1
  977. arch/arm/boot/dts/pxa2xx.dtsi +2 −2
  978. arch/arm/boot/dts/pxa910-dkb.dts +1 −1
  979. arch/arm/boot/dts/pxa910.dtsi +27 −1
  980. arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts +59 −0
  981. arch/arm/boot/dts/qcom-apq8064-ifc6410.dts +43 −0
  982. arch/arm/boot/dts/qcom-apq8064.dtsi +183 −0
  983. arch/arm/boot/dts/qcom-apq8074-dragonboard.dts +21 −0
  984. arch/arm/boot/dts/qcom-apq8084-ifc6540.dts +23 −0
  985. arch/arm/boot/dts/qcom-apq8084-mtp.dts +6 −0
  986. arch/arm/boot/dts/qcom-apq8084.dtsi +51 −0
  987. arch/arm/boot/dts/qcom-ipq8064-ap148.dts +93 −0
  988. arch/arm/boot/dts/qcom-ipq8064-v1.0.dtsi +1 −0
  989. arch/arm/boot/dts/qcom-ipq8064.dtsi +283 −0
  990. arch/arm/boot/dts/qcom-msm8660-surf.dts +42 −0
  991. arch/arm/boot/dts/qcom-msm8660.dtsi +93 −0
  992. arch/arm/boot/dts/qcom-msm8960-cdp.dts +27 −0
  993. arch/arm/boot/dts/qcom-msm8960.dtsi +87 −0
  994. arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts +17 −0
  995. arch/arm/boot/dts/qcom-msm8974.dtsi +13 −2
  996. arch/arm/boot/dts/r7s72100-genmai.dts +6 −1
  997. arch/arm/boot/dts/r7s72100.dtsi +101 −91
  998. arch/arm/boot/dts/r8a73a4-ape6evm-reference.dts +6 −1
  999. arch/arm/boot/dts/r8a73a4.dtsi +140 −129
  1000. arch/arm/boot/dts/r8a7740-armadillo800eva-reference.dts +0 −283
  1001. arch/arm/boot/dts/r8a7740-armadillo800eva.dts +280 −1
  1002. arch/arm/boot/dts/r8a7740.dtsi +253 −1
  1003. arch/arm/boot/dts/r8a7778-bockw-reference.dts +6 −1
  1004. arch/arm/boot/dts/r8a7778.dtsi +42 −6
  1005. arch/arm/boot/dts/r8a7779-marzen.dts +88 −0
  1006. arch/arm/boot/dts/r8a7779.dtsi +72 −20
  1007. arch/arm/boot/dts/r8a7790-lager.dts +211 −18
  1008. arch/arm/boot/dts/r8a7790.dtsi +408 −28
  1009. arch/arm/boot/dts/r8a7791-henninger.dts +47 −0
  1010. arch/arm/boot/dts/r8a7791-koelsch.dts +152 −7
  1011. arch/arm/boot/dts/r8a7791.dtsi +371 −18
  1012. arch/arm/boot/dts/r8a7794-alt.dts +48 −0
  1013. arch/arm/boot/dts/r8a7794.dtsi +542 −0
  1014. arch/arm/boot/dts/r8a77xx-aa104xd12-panel.dtsi +41 −0
  1015. arch/arm/boot/dts/rk3066a-bqcurie2.dts +8 −11
  1016. arch/arm/boot/dts/rk3066a-marsboard.dts +206 −0
  1017. arch/arm/boot/dts/rk3066a.dtsi +181 −1
  1018. arch/arm/boot/dts/rk3188-radxarock.dts +105 −8
  1019. arch/arm/boot/dts/rk3188.dtsi +133 −3
  1020. arch/arm/boot/dts/rk3288-evb-act8846.dts +1 −9
  1021. arch/arm/boot/dts/rk3288-evb-rk808.dts +136 −0
  1022. arch/arm/boot/dts/rk3288-evb.dtsi +93 −0
  1023. arch/arm/boot/dts/rk3288-thermal.dtsi +74 −0
  1024. arch/arm/boot/dts/rk3288.dtsi +478 −1
  1025. arch/arm/boot/dts/rk3xxx.dtsi +129 −8
  1026. arch/arm/boot/dts/s3c6410-mini6410.dts +0 −4
  1027. arch/arm/boot/dts/s3c64xx.dtsi +0 −1
  1028. arch/arm/boot/dts/sama5d3.dtsi +35 −2
  1029. arch/arm/boot/dts/sama5d31.dtsi +1 −1
  1030. arch/arm/boot/dts/sama5d33.dtsi +1 −1
  1031. arch/arm/boot/dts/sama5d34.dtsi +1 −1
  1032. arch/arm/boot/dts/sama5d35.dtsi +1 −1
  1033. arch/arm/boot/dts/sama5d36.dtsi +1 −1
  1034. arch/arm/boot/dts/sama5d3_can.dtsi +1 −1
  1035. arch/arm/boot/dts/sama5d3xcm.dtsi +31 −1
  1036. arch/arm/boot/dts/sama5d3xmb.dtsi +4 −0
  1037. arch/arm/boot/dts/sama5d4.dtsi +1309 −0
  1038. arch/arm/boot/dts/sh7372.dtsi +1 −0
  1039. arch/arm/boot/dts/sh73a0-kzm9g-reference.dts +13 −4
  1040. arch/arm/boot/dts/sh73a0.dtsi +18 −28
  1041. arch/arm/boot/dts/socfpga.dtsi +44 −6
  1042. arch/arm/boot/dts/socfpga_arria10.dtsi +374 −0
  1043. arch/arm/boot/dts/socfpga_arria10_socdk.dts +48 −0
  1044. arch/arm/boot/dts/socfpga_arria5.dtsi +6 −7
  1045. arch/arm/boot/dts/socfpga_arria5_socdk.dts +10 −5
  1046. arch/arm/boot/dts/socfpga_cyclone5.dtsi +10 −7
  1047. arch/arm/boot/dts/socfpga_cyclone5_socdk.dts +17 −0
  1048. arch/arm/boot/dts/socfpga_cyclone5_sockit.dts +12 −0
  1049. arch/arm/boot/dts/socfpga_vt.dts +3 −6
  1050. arch/arm/boot/dts/spear1310.dtsi +9 −9
  1051. arch/arm/boot/dts/spear1340.dtsi +3 −3
  1052. arch/arm/boot/dts/ste-ccu8540-pinctrl.dtsi +32 −32
  1053. arch/arm/boot/dts/ste-dbx5x0.dtsi +22 −0
  1054. arch/arm/boot/dts/ste-href-ab8500.dtsi +81 −81
  1055. arch/arm/boot/dts/ste-href-ab8505.dtsi +45 −45
  1056. arch/arm/boot/dts/ste-href-family-pinctrl.dtsi +115 −115
  1057. arch/arm/boot/dts/ste-href-stuib.dtsi +2 −2
  1058. arch/arm/boot/dts/ste-href-tvk1281618.dtsi +6 −6
  1059. arch/arm/boot/dts/ste-hrefprev60.dtsi +10 −10
  1060. arch/arm/boot/dts/ste-hrefv60plus.dtsi +21 −21
  1061. arch/arm/boot/dts/ste-nomadik-nhk15.dts +151 −0
  1062. arch/arm/boot/dts/ste-nomadik-s8815.dts +52 −12
  1063. arch/arm/boot/dts/ste-nomadik-stn8815.dtsi +17 −56
  1064. arch/arm/boot/dts/ste-snowball.dts +18 −18
  1065. arch/arm/boot/dts/stih407-b2120.dts +4 −51
  1066. arch/arm/boot/dts/stih407-clock.dtsi +290 −3
  1067. arch/arm/boot/dts/stih407-family.dtsi +278 −0
  1068. arch/arm/boot/dts/stih407.dtsi +0 −263
  1069. arch/arm/boot/dts/stih410-b2120.dts +29 −0
  1070. arch/arm/boot/dts/stih410-clock.dtsi +338 −0
  1071. arch/arm/boot/dts/stih410-pinctrl.dtsi +34 −0
  1072. arch/arm/boot/dts/stih410.dtsi +14 −0
  1073. arch/arm/boot/dts/stih415-pinctrl.dtsi +191 −170
  1074. arch/arm/boot/dts/stih415.dtsi +12 −0
  1075. arch/arm/boot/dts/stih416-b2020.dts +22 −0
  1076. arch/arm/boot/dts/stih416-b2020e.dts +23 −3
  1077. arch/arm/boot/dts/stih416-pinctrl.dtsi +244 −171
  1078. arch/arm/boot/dts/stih416.dtsi +209 −0
  1079. arch/arm/boot/dts/stih41x-b2000.dtsi +3 −3
  1080. arch/arm/boot/dts/stih41x-b2020.dtsi +7 −3
  1081. arch/arm/boot/dts/stih41x-b2020x.dtsi +4 −0
  1082. arch/arm/boot/dts/stihxxx-b2120.dtsi +59 −0
  1083. arch/arm/boot/dts/sun4i-a10-a1000.dts +41 −5
  1084. arch/arm/boot/dts/sun4i-a10-ba10-tvbox.dts +41 −5
  1085. arch/arm/boot/dts/sun4i-a10-cubieboard.dts +41 −5
  1086. arch/arm/boot/dts/sun4i-a10-hackberry.dts +41 −5
  1087. arch/arm/boot/dts/sun4i-a10-inet97fv2.dts +41 −5
  1088. arch/arm/boot/dts/sun4i-a10-mini-xplus.dts +41 −5
  1089. arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts +41 −5
  1090. arch/arm/boot/dts/sun4i-a10-pcduino.dts +41 −5
  1091. arch/arm/boot/dts/sun4i-a10.dtsi +32 −13
  1092. arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts +41 −5
  1093. arch/arm/boot/dts/sun5i-a10s-r7-tv-dongle.dts +41 −5
  1094. arch/arm/boot/dts/sun5i-a10s.dtsi +31 −14
  1095. arch/arm/boot/dts/sun5i-a13-hsg-h702.dts +130 −0
  1096. arch/arm/boot/dts/sun5i-a13-olinuxino-micro.dts +41 −7
  1097. arch/arm/boot/dts/sun5i-a13-olinuxino.dts +41 −5
  1098. arch/arm/boot/dts/sun5i-a13.dtsi +17 −14
  1099. arch/arm/boot/dts/sun6i-a31-app4-evb1.dts +41 −5
  1100. arch/arm/boot/dts/sun6i-a31-colombus.dts +41 −5
  1101. arch/arm/boot/dts/sun6i-a31-hummingbird.dts +41 −5
  1102. arch/arm/boot/dts/sun6i-a31-m9.dts +98 −5
  1103. arch/arm/boot/dts/sun6i-a31.dtsi +78 −32
  1104. arch/arm/boot/dts/sun7i-a20-bananapi.dts +214 −0
  1105. arch/arm/boot/dts/sun7i-a20-cubietruck.dts +14 −0
  1106. arch/arm/boot/dts/sun7i-a20-hummingbird.dts +236 −0
  1107. arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts +41 −5
  1108. arch/arm/boot/dts/sun7i-a20-m3.dts +168 −0
  1109. arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts +173 −0
  1110. arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts +228 −0
  1111. arch/arm/boot/dts/sun7i-a20-pcduino3.dts +41 −5
  1112. arch/arm/boot/dts/sun7i-a20.dtsi +132 −23
  1113. arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts +82 −5
  1114. arch/arm/boot/dts/sun8i-a23.dtsi +234 −15
  1115. arch/arm/boot/dts/sun9i-a80-optimus.dts +119 −0
  1116. arch/arm/boot/dts/sun9i-a80.dtsi +514 −0
  1117. arch/arm/boot/dts/sunxi-common-regulators.dtsi +68 −5
  1118. arch/arm/boot/dts/tegra114-dalmore.dts +1 −0
  1119. arch/arm/boot/dts/tegra114-roth.dts +5 −4
  1120. arch/arm/boot/dts/tegra114-tn7.dts +4 −1
  1121. arch/arm/boot/dts/tegra114.dtsi +19 −16
  1122. arch/arm/boot/dts/tegra124-jetson-tk1.dts +139 −4
  1123. arch/arm/boot/dts/tegra124-nyan-big.dts +1137 −0
  1124. arch/arm/boot/dts/tegra124-venice2.dts +14 −5
  1125. arch/arm/boot/dts/tegra124.dtsi +167 −7
  1126. arch/arm/boot/dts/tegra20-harmony.dts +1 −0
  1127. arch/arm/boot/dts/tegra20-iris-512.dts +5 −0
  1128. arch/arm/boot/dts/tegra20-medcom-wide.dts +4 −0
  1129. arch/arm/boot/dts/tegra20-paz00.dts +2 −0
  1130. arch/arm/boot/dts/tegra20-seaboard.dts +1 −0
  1131. arch/arm/boot/dts/tegra20-tamonten.dtsi +1 −0
  1132. arch/arm/boot/dts/tegra20-trimslice.dts +1 −0
  1133. arch/arm/boot/dts/tegra20-ventana.dts +1 −0
  1134. arch/arm/boot/dts/tegra20-whistler.dts +1 −0
  1135. arch/arm/boot/dts/tegra20.dtsi +5 −8
  1136. arch/arm/boot/dts/tegra30-apalis-eval.dts +4 −0
  1137. arch/arm/boot/dts/tegra30-beaver.dts +1 −0
  1138. arch/arm/boot/dts/tegra30-cardhu.dtsi +3 −1
  1139. arch/arm/boot/dts/tegra30-colibri-eval-v3.dts +3 −0
  1140. arch/arm/boot/dts/tegra30.dtsi +16 −22
  1141. arch/arm/boot/dts/vexpress-v2m-rs1.dtsi +34 −2
  1142. arch/arm/boot/dts/vexpress-v2m.dtsi +34 −2
  1143. arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts +222 −0
  1144. arch/arm/boot/dts/vexpress-v2p-ca9.dts +31 −0
  1145. arch/arm/boot/dts/vf-colibri-eval-v3.dtsi +96 −0
  1146. arch/arm/boot/dts/vf-colibri.dtsi +186 −0
  1147. arch/arm/boot/dts/vf500-colibri-eval-v3.dts +17 −0
  1148. arch/arm/boot/dts/vf500-colibri.dtsi +20 −0
  1149. arch/arm/boot/dts/vf500.dtsi +171 −0
  1150. arch/arm/boot/dts/vf610-colibri-eval-v3.dts +17 −0
  1151. arch/arm/boot/dts/vf610-colibri.dts +0 −123
  1152. arch/arm/boot/dts/vf610-colibri.dtsi +25 −0
  1153. arch/arm/boot/dts/vf610-cosmic.dts +27 −6
  1154. arch/arm/boot/dts/vf610-twr.dts +58 −14
  1155. arch/arm/boot/dts/vf610.dtsi +12 −420
  1156. arch/arm/boot/dts/vfxxx.dtsi +437 −0
  1157. arch/arm/boot/dts/zynq-7000.dtsi +30 −10
  1158. arch/arm/boot/dts/zynq-parallella.dts +29 −3
  1159. arch/arm/boot/dts/zynq-zc702.dts +20 −2
  1160. arch/arm/boot/dts/zynq-zc706.dts +12 −4
  1161. arch/arm/boot/dts/zynq-zed.dts +13 −5
  1162. arch/arm/boot/dts/zynq-zybo.dts +52 −0
  1163. arch/arm/common/edma.c +61 −2
  1164. arch/arm/common/sa1111.c +6 −8
  1165. arch/arm/common/scoop.c +2 −8
  1166. arch/arm/configs/ape6evm_defconfig +9 −1
  1167. arch/arm/configs/armadillo800eva_defconfig +1 −1
  1168. arch/arm/configs/at91_dt_defconfig +26 −12
  1169. arch/arm/configs/at91rm9200_defconfig +0 −161
  1170. arch/arm/configs/at91sam9260_9g20_defconfig +0 −148
  1171. arch/arm/configs/at91sam9261_9g10_defconfig +0 −148
  1172. arch/arm/configs/at91sam9263_defconfig +0 −152
  1173. arch/arm/configs/at91sam9g45_defconfig +0 −172
  1174. arch/arm/configs/at91sam9rl_defconfig +0 −83
  1175. arch/arm/configs/at91x40_defconfig +0 −48
  1176. arch/arm/configs/bcm2835_defconfig +1 −0
  1177. arch/arm/configs/bcm_defconfig +3 −3
  1178. arch/arm/configs/bockw_defconfig +3 −2
  1179. arch/arm/configs/clps711x_defconfig +3 −1
  1180. arch/arm/configs/davinci_all_defconfig +1 −2
  1181. arch/arm/configs/ep93xx_defconfig +1 −0
  1182. arch/arm/configs/exynos_defconfig +14 −1
  1183. arch/arm/configs/ezx_defconfig +0 −2
  1184. arch/arm/configs/hi3xxx_defconfig +0 −58
  1185. arch/arm/configs/hisi_defconfig +90 −0
  1186. arch/arm/configs/imote2_defconfig +0 −2
  1187. arch/arm/configs/imx_v4_v5_defconfig +2 −13
  1188. arch/arm/configs/imx_v6_v7_defconfig +14 −7
  1189. arch/arm/configs/integrator_defconfig +3 −0
  1190. arch/arm/configs/keystone_defconfig +8 −1
  1191. arch/arm/configs/koelsch_defconfig +0 −96
  1192. arch/arm/configs/kzm9g_defconfig +2 −1
  1193. arch/arm/configs/lager_defconfig +8 −2
  1194. arch/arm/configs/lpc32xx_defconfig +2 −0
  1195. arch/arm/configs/mackerel_defconfig +0 −1
  1196. arch/arm/configs/marzen_defconfig +2 −1
  1197. arch/arm/configs/multi_v5_defconfig +2 −0
  1198. arch/arm/configs/multi_v7_defconfig +80 −2
  1199. arch/arm/configs/mvebu_v5_defconfig +2 −0
  1200. arch/arm/configs/mvebu_v7_defconfig +40 −35
  1201. arch/arm/configs/nhk8815_defconfig +4 −7
  1202. arch/arm/configs/omap1_defconfig +0 −1
  1203. arch/arm/configs/omap2plus_defconfig +87 −17
  1204. arch/arm/configs/prima2_defconfig +1 −1
  1205. arch/arm/configs/pxa3xx_defconfig +0 −1
  1206. arch/arm/configs/qcom_defconfig +10 −4
  1207. arch/arm/configs/sama5_defconfig +19 −9
  1208. arch/arm/configs/shmobile_defconfig +20 −3
  1209. arch/arm/configs/socfpga_defconfig +28 −43
  1210. arch/arm/configs/sunxi_defconfig +6 −2
  1211. arch/arm/configs/tegra_defconfig +5 −4
  1212. arch/arm/configs/u8500_defconfig +1 −1
  1213. arch/arm/configs/versatile_defconfig +1 −0
  1214. arch/arm/configs/vt8500_v6_v7_defconfig +1 −1
  1215. arch/arm/crypto/aes_glue.c +2 −2
  1216. arch/arm/crypto/sha1-armv7-neon.S +22 −17
  1217. arch/arm/crypto/sha1_glue.c +1 −1
  1218. arch/arm/crypto/sha1_neon_glue.c +1 −1
  1219. arch/arm/crypto/sha512_neon_glue.c +3 −3
  1220. arch/arm/include/asm/Kbuild +0 −1
  1221. arch/arm/include/asm/arch_timer.h +9 −25
  1222. arch/arm/include/asm/atomic.h +124 −183
  1223. arch/arm/include/asm/barrier.h +4 −0
  1224. arch/arm/include/asm/cacheflush.h +10 −0
  1225. arch/arm/include/asm/cpuidle.h +0 −1
  1226. arch/arm/include/asm/device.h +1 −0
  1227. arch/arm/include/asm/dma-mapping.h +10 −20
  1228. arch/arm/include/asm/firmware.h +9 −1
  1229. arch/arm/include/asm/fixmap.h +14 −17
  1230. arch/arm/include/asm/ftrace.h +1 −1
  1231. arch/arm/include/asm/hardware/coresight.h +0 −157
  1232. arch/arm/include/asm/hardware/cp14.h +542 −0
  1233. arch/arm/include/asm/hw_irq.h +1 −0
  1234. arch/arm/include/asm/io.h +37 −53
  1235. arch/arm/include/asm/irq_work.h +11 −0
  1236. arch/arm/include/asm/kvm_emulate.h +10 −0
  1237. arch/arm/include/asm/kvm_host.h +16 −9
  1238. arch/arm/include/asm/kvm_mmu.h +30 −16
  1239. arch/arm/include/asm/mach/pci.h +6 −4
  1240. arch/arm/include/asm/mcpm.h +22 −0
  1241. arch/arm/include/asm/memory.h +4 −0
  1242. arch/arm/include/asm/percpu.h +2 −2
  1243. arch/arm/include/asm/perf_event.h +1 −1
  1244. arch/arm/include/asm/pgalloc.h +9 −1
  1245. arch/arm/include/asm/pgtable-2level-hwdef.h +2 −0
  1246. arch/arm/include/asm/pgtable-2level.h +2 −0
  1247. arch/arm/include/asm/pgtable-3level-hwdef.h +1 −0
  1248. arch/arm/include/asm/pgtable-3level.h +15 −0
  1249. arch/arm/include/asm/pgtable.h +52 −14
  1250. arch/arm/include/asm/pmu.h +33 −3
  1251. arch/arm/include/asm/ptrace.h +2 −3
  1252. arch/arm/include/asm/smp.h +0 −6
  1253. arch/arm/include/asm/spinlock.h +2 −2
  1254. arch/arm/include/asm/syscall.h +4 −4
  1255. arch/arm/include/asm/thread_info.h +7 −13
  1256. arch/arm/include/asm/tlb.h +36 −2
  1257. arch/arm/include/asm/vfp.h +5 −0
  1258. arch/arm/include/asm/xen/page-coherent.h +57 −9
  1259. arch/arm/include/asm/xen/page.h +4 −0
  1260. arch/arm/include/debug/asm9260.S +29 −0
  1261. arch/arm/include/debug/bcm63xx.S +33 −0
  1262. arch/arm/include/debug/meson.S +35 −0
  1263. arch/arm/include/debug/renesas-scif.S +52 −0
  1264. arch/arm/include/debug/sa1100.S +68 −0
  1265. arch/arm/include/uapi/asm/kvm.h +2 −0
  1266. arch/arm/include/uapi/asm/unistd.h +2 −0
  1267. arch/arm/kernel/Makefile +4 −3
  1268. arch/arm/kernel/asm-offsets.c +11 −1
  1269. arch/arm/kernel/atags_compat.c +2 −4
  1270. arch/arm/kernel/atags_parse.c +3 −4
  1271. arch/arm/kernel/atags_proc.c +2 −2
  1272. arch/arm/kernel/bios32.c +13 −17
  1273. arch/arm/kernel/calls.S +2 −0
  1274. arch/arm/kernel/dma-isa.c +2 −2
  1275. arch/arm/kernel/dma.c +11 −15
  1276. arch/arm/kernel/entry-armv.S +94 −14
  1277. arch/arm/kernel/entry-common.S +1 −236
  1278. arch/arm/kernel/entry-ftrace.S +243 −0
  1279. arch/arm/kernel/entry-header.S +59 −4
  1280. arch/arm/kernel/etm.c +0 −654
  1281. arch/arm/kernel/fiq.c +14 −5
  1282. arch/arm/kernel/ftrace.c +19 −0
  1283. arch/arm/kernel/hibernate.c +1 −2
  1284. arch/arm/kernel/hw_breakpoint.c +11 −11
  1285. arch/arm/kernel/io.c +2 −3
  1286. arch/arm/kernel/irq.c +6 −23
  1287. arch/arm/kernel/iwmmxt.S +13 −0
  1288. arch/arm/kernel/jump_label.c +1 −1
  1289. arch/arm/kernel/kgdb.c +29 −0
  1290. arch/arm/kernel/machine_kexec.c +8 −7
  1291. arch/arm/kernel/module.c +1 −1
  1292. arch/arm/kernel/patch.c +73 −19
  1293. arch/arm/kernel/patch.h +11 −1
  1294. arch/arm/kernel/perf_callchain.c +136 −0
  1295. arch/arm/kernel/perf_event.c +20 −144
  1296. arch/arm/kernel/perf_event_cpu.c +90 −95
  1297. arch/arm/kernel/perf_event_v6.c +6 −6
  1298. arch/arm/kernel/perf_event_v7.c +34 −38
  1299. arch/arm/kernel/perf_event_xscale.c +10 −10
  1300. arch/arm/kernel/perf_regs.c +8 −0
  1301. arch/arm/kernel/process.c +59 −19
  1302. arch/arm/kernel/ptrace.c +8 −3
  1303. arch/arm/kernel/return_address.c +1 −11
  1304. arch/arm/kernel/setup.c +19 −1
  1305. arch/arm/kernel/signal.c +0 −1
  1306. arch/arm/kernel/smp.c +23 −18
  1307. arch/arm/kernel/smp_twd.c +8 −8
  1308. arch/arm/kernel/stacktrace.c +1 −3
  1309. arch/arm/kernel/swp_emulate.c +1 −1
  1310. arch/arm/kernel/sys_oabi-compat.c +2 −2
  1311. arch/arm/kernel/thumbee.c +1 −1
  1312. arch/arm/kernel/topology.c +4 −4
  1313. arch/arm/kernel/traps.c +46 −53
  1314. arch/arm/kernel/unwind.c +13 −14
  1315. arch/arm/kernel/vmlinux.lds.S +20 −1
  1316. arch/arm/kernel/xscale-cp0.c +3 −4
  1317. arch/arm/kvm/arm.c +84 −33
  1318. arch/arm/kvm/coproc.c +1 −1
  1319. arch/arm/kvm/guest.c +1 −27
  1320. arch/arm/kvm/interrupts_head.S +7 −0
  1321. arch/arm/kvm/mmio.c +9 −6
  1322. arch/arm/kvm/mmu.c +308 −59
  1323. arch/arm/kvm/psci.c +18 −0
  1324. arch/arm/lib/copy_from_user.S +5 −0
  1325. arch/arm/lib/copy_template.S +30 −0
  1326. arch/arm/lib/copy_to_user.S +5 −0
  1327. arch/arm/lib/memcpy.S +5 −0
  1328. arch/arm/lib/memmove.S +28 −0
  1329. arch/arm/lib/memset.S +12 −0
  1330. arch/arm/lib/memzero.S +12 −0
  1331. arch/arm/mach-asm9260/Kconfig +6 −0
  1332. arch/arm/mach-at91/Kconfig +32 −69
  1333. arch/arm/mach-at91/Kconfig.non_dt +0 −350
  1334. arch/arm/mach-at91/Makefile +3 −72
  1335. arch/arm/mach-at91/Makefile.boot +0 −6
  1336. arch/arm/mach-at91/at91_aic.h +0 −99
  1337. arch/arm/mach-at91/at91_rstc.h +0 −53
  1338. arch/arm/mach-at91/at91_shdwc.h +0 −50
  1339. arch/arm/mach-at91/at91_tc.h +0 −146
  1340. arch/arm/mach-at91/at91rm9200.c +0 −341
  1341. arch/arm/mach-at91/at91rm9200_devices.c +0 −1212
  1342. arch/arm/mach-at91/at91rm9200_time.c +0 −23
  1343. arch/arm/mach-at91/at91sam9260.c +0 −354
  1344. arch/arm/mach-at91/at91sam9260_devices.c +0 −1364
  1345. arch/arm/mach-at91/at91sam9261.c +0 −332
  1346. arch/arm/mach-at91/at91sam9261_devices.c +0 −1098
  1347. arch/arm/mach-at91/at91sam9263.c +0 −356
  1348. arch/arm/mach-at91/at91sam9263_devices.c +0 −1538
  1349. arch/arm/mach-at91/at91sam926x_time.c +0 −294
  1350. arch/arm/mach-at91/at91sam9_alt_reset.S +0 −40
  1351. arch/arm/mach-at91/at91sam9g45.c +1 −406
  1352. arch/arm/mach-at91/at91sam9g45_devices.c +0 −1915
  1353. arch/arm/mach-at91/at91sam9g45_reset.S +0 −45
  1354. arch/arm/mach-at91/at91sam9n12.c +2 −211
  1355. arch/arm/mach-at91/at91sam9rl.c +1 −334
  1356. arch/arm/mach-at91/at91sam9rl_devices.c +0 −1260
  1357. arch/arm/mach-at91/at91sam9x5.c +2 −309
  1358. arch/arm/mach-at91/at91x40.c +0 −93
  1359. arch/arm/mach-at91/at91x40_time.c +0 −85
  1360. arch/arm/mach-at91/board-1arm.c +0 −99
  1361. arch/arm/mach-at91/board-afeb-9260v1.c +0 −221
  1362. arch/arm/mach-at91/board-cam60.c +0 −197
  1363. arch/arm/mach-at91/board-carmeva.c +0 −167
  1364. arch/arm/mach-at91/board-cpu9krea.c +0 −384
  1365. arch/arm/mach-at91/board-cpuat91.c +0 −189
  1366. arch/arm/mach-at91/board-csb337.c +0 −260
  1367. arch/arm/mach-at91/board-csb637.c +0 −142
  1368. arch/arm/mach-at91/board-dt-rm9200.c +0 −16
  1369. arch/arm/mach-at91/board-dt-sam9.c +0 −25
  1370. arch/arm/mach-at91/board-dt-sama5.c +15 −46
  1371. arch/arm/mach-at91/board-eb01.c +0 −52
  1372. arch/arm/mach-at91/board-eb9200.c +0 −126
  1373. arch/arm/mach-at91/board-ecbat91.c +0 −191
  1374. arch/arm/mach-at91/board-eco920.c +0 −160
  1375. arch/arm/mach-at91/board-flexibity.c +0 −169
  1376. arch/arm/mach-at91/board-foxg20.c +0 −272
  1377. arch/arm/mach-at91/board-gsia18s.c +0 −585
  1378. arch/arm/mach-at91/board-kafa.c +0 −113
  1379. arch/arm/mach-at91/board-kb9202.c +0 −159
  1380. arch/arm/mach-at91/board-pcontrol-g20.c +0 −228
  1381. arch/arm/mach-at91/board-picotux200.c +0 −129
  1382. arch/arm/mach-at91/board-rm9200ek.c +0 −196
  1383. arch/arm/mach-at91/board-rsi-ews.c +0 −232
  1384. arch/arm/mach-at91/board-sam9-l9260.c +0 −228
  1385. arch/arm/mach-at91/board-sam9260ek.c +0 −353
  1386. arch/arm/mach-at91/board-sam9261ek.c +0 −622
  1387. arch/arm/mach-at91/board-sam9263ek.c +0 −492
  1388. arch/arm/mach-at91/board-sam9g20ek.c +0 −429
  1389. arch/arm/mach-at91/board-sam9m10g45ek.c +0 −526
  1390. arch/arm/mach-at91/board-sam9rlek.c +0 −332
  1391. arch/arm/mach-at91/board-snapper9260.c +0 −189
  1392. arch/arm/mach-at91/board-stamp9g20.c +0 −294
  1393. arch/arm/mach-at91/board-yl-9200.c +0 −597
  1394. arch/arm/mach-at91/board.h +0 −127
  1395. arch/arm/mach-at91/clock.c +0 −976
  1396. arch/arm/mach-at91/clock.h +0 −49
  1397. arch/arm/mach-at91/generic.h +5 −57
  1398. arch/arm/mach-at91/gpio.c +0 −982
  1399. arch/arm/mach-at91/gpio.h +0 −214
  1400. arch/arm/mach-at91/gsia18s.h +0 −33
  1401. arch/arm/mach-at91/include/mach/at91_dbgu.h +0 −3
  1402. arch/arm/mach-at91/include/mach/at91_pio.h +6 −0
  1403. arch/arm/mach-at91/include/mach/at91_ramc.h +3 −3
  1404. arch/arm/mach-at91/include/mach/at91x40.h +0 −60
  1405. arch/arm/mach-at91/include/mach/atmel-mci.h +0 −17
  1406. arch/arm/mach-at91/include/mach/cpu.h +21 −2
  1407. arch/arm/mach-at91/include/mach/debug-macro.S +4 −1
  1408. arch/arm/mach-at91/include/mach/hardware.h +21 −10
  1409. arch/arm/mach-at91/include/mach/sama5d4.h +33 −0
  1410. arch/arm/mach-at91/include/mach/uncompress.h +17 −11
  1411. arch/arm/mach-at91/irq.c +0 −554
  1412. arch/arm/mach-at91/leds.c +0 −56
  1413. arch/arm/mach-at91/pm.c +3 −96
  1414. arch/arm/mach-at91/pm.h +0 −1
  1415. arch/arm/mach-at91/sama5d4.c +64 −0
  1416. arch/arm/mach-at91/setup.c +112 −202
  1417. arch/arm/mach-at91/soc.h +5 −4
  1418. arch/arm/mach-at91/stamp9g20.h +0 −7
  1419. arch/arm/mach-bcm/Kconfig +70 −34
  1420. arch/arm/mach-bcm/Makefile +8 −0
  1421. arch/arm/mach-bcm/bcm63xx.c +27 −0
  1422. arch/arm/mach-bcm/bcm_cygnus.c +25 −0
  1423. arch/arm/mach-bcm/brcmstb.h +19 −0
  1424. arch/arm/mach-bcm/headsmp-brcmstb.S +33 −0
  1425. arch/arm/mach-bcm/platsmp-brcmstb.c +329 −0
  1426. arch/arm/mach-berlin/Kconfig +2 −1
  1427. arch/arm/mach-clps711x/board-edb7211.c +22 −15
  1428. arch/arm/mach-clps711x/common.c +4 −134
  1429. arch/arm/mach-clps711x/common.h +5 −0
  1430. arch/arm/mach-clps711x/devices.c +51 −1
  1431. arch/arm/mach-cns3xxx/cns3420vb.c +1 −0
  1432. arch/arm/mach-cns3xxx/core.c +1 −0
  1433. arch/arm/mach-cns3xxx/core.h +6 −0
  1434. arch/arm/mach-cns3xxx/pcie.c +24 −25
  1435. arch/arm/mach-davinci/board-da830-evm.c +37 −52
  1436. arch/arm/mach-davinci/board-da850-evm.c +18 −6
  1437. arch/arm/mach-davinci/board-dm355-evm.c +1 −1
  1438. arch/arm/mach-davinci/board-dm365-evm.c +2 −2
  1439. arch/arm/mach-davinci/board-dm644x-evm.c +4 −6
  1440. arch/arm/mach-davinci/board-mityomapl138.c +22 −23
  1441. arch/arm/mach-davinci/board-neuros-osd2.c +2 −3
  1442. arch/arm/mach-davinci/clock.c +1 −1
  1443. arch/arm/mach-davinci/cpuidle.c +0 −2
  1444. arch/arm/mach-davinci/da8xx-dt.c +1 −0
  1445. arch/arm/mach-davinci/dm355.c +3 −4
  1446. arch/arm/mach-davinci/dm365.c +3 −4
  1447. arch/arm/mach-davinci/mux.c +9 −6
  1448. arch/arm/mach-davinci/pm.c +0 −1
  1449. arch/arm/mach-davinci/pm_domain.c +1 −1
  1450. arch/arm/mach-davinci/time.c +6 −7
  1451. arch/arm/mach-ebsa110/Makefile +0 −3
  1452. arch/arm/mach-ebsa110/include/mach/io.h +18 −7
  1453. arch/arm/mach-ebsa110/io.c +7 −7
  1454. arch/arm/mach-ep93xx/Makefile +0 −3
  1455. arch/arm/mach-ep93xx/dma.c +10 −2
  1456. arch/arm/mach-exynos/Kconfig +13 −2
  1457. arch/arm/mach-exynos/Makefile +3 −9
  1458. arch/arm/mach-exynos/common.h +13 −20
  1459. arch/arm/mach-exynos/exynos-pmu.h +24 −0
  1460. arch/arm/mach-exynos/exynos.c +8 −75
  1461. arch/arm/mach-exynos/firmware.c +64 −3
  1462. arch/arm/mach-exynos/hotplug.c +0 −91
  1463. arch/arm/mach-exynos/include/mach/map.h +0 −23
  1464. arch/arm/mach-exynos/include/mach/memory.h +0 −26
  1465. arch/arm/mach-exynos/mcpm-exynos.c +22 −10
  1466. arch/arm/mach-exynos/platsmp.c +150 −2
  1467. arch/arm/mach-exynos/pm.c +40 −271
  1468. arch/arm/mach-exynos/pm_domains.c +1 −77
  1469. arch/arm/mach-exynos/pmu.c +629 −46
  1470. arch/arm/mach-exynos/regs-pmu.h +361 −0
  1471. arch/arm/mach-exynos/sleep.S +28 −0
  1472. arch/arm/mach-exynos/smc.h +4 −0
  1473. arch/arm/mach-exynos/suspend.c +566 −0
  1474. arch/arm/mach-footbridge/Makefile +0 −3
  1475. arch/arm/mach-highbank/highbank.c +1 −1
  1476. arch/arm/mach-hisi/Kconfig +10 −1
  1477. arch/arm/mach-hisi/Makefile +3 −0
  1478. arch/arm/mach-hisi/hisilicon.c +9 −0
  1479. arch/arm/mach-hisi/platmcpm.c +386 −0
  1480. arch/arm/mach-imx/Kconfig +38 −104
  1481. arch/arm/mach-imx/Makefile +7 −9
  1482. arch/arm/mach-imx/anatop.c +45 −2
  1483. arch/arm/mach-imx/avic.c +1 −1
  1484. arch/arm/mach-imx/board-pcm038.h +0 −36
  1485. arch/arm/mach-imx/clk-cpu.c +107 −0
  1486. arch/arm/mach-imx/clk-gate-exclusive.c +94 −0
  1487. arch/arm/mach-imx/clk-imx51-imx53.c +13 −1
  1488. arch/arm/mach-imx/clk-imx6q.c +90 −25
  1489. arch/arm/mach-imx/clk-imx6sl.c +86 −17
  1490. arch/arm/mach-imx/clk-imx6sx.c +54 −9
  1491. arch/arm/mach-imx/clk-pllv3.c +1 −43
  1492. arch/arm/mach-imx/clk-vf610.c +122 −44
  1493. arch/arm/mach-imx/clk.h +7 −0
  1494. arch/arm/mach-imx/common.h +4 −5
  1495. arch/arm/mach-imx/cpuidle-imx5.c +0 −1
  1496. arch/arm/mach-imx/cpuidle-imx6q.c +1 −6
  1497. arch/arm/mach-imx/cpuidle-imx6sl.c +1 −2
  1498. arch/arm/mach-imx/eukrea-baseboards.h +1 −9
  1499. arch/arm/mach-imx/eukrea_mbimx27-baseboard.c +0 −351
  1500. arch/arm/mach-imx/gpc.c +26 −16
  1501. arch/arm/mach-imx/imx1-dt.c +26 −0
  1502. arch/arm/mach-imx/imx25-dt.c +0 −9
  1503. arch/arm/mach-imx/imx27-dt.c +1 −4
  1504. arch/arm/mach-imx/imx31-dt.c +0 −9
  1505. arch/arm/mach-imx/imx35-dt.c +0 −10
  1506. arch/arm/mach-imx/iomux-imx31.c +4 −11
  1507. arch/arm/mach-imx/iomux-mx3.h +1 −1
  1508. arch/arm/mach-imx/iomux-v1.c +0 −2
  1509. arch/arm/mach-imx/iomux-v3.c +0 −2
  1510. arch/arm/mach-imx/mach-armadillo5x0.c +1 −1
  1511. arch/arm/mach-imx/mach-cpuimx27.c +0 −321
  1512. arch/arm/mach-imx/mach-imx50.c +0 −9
  1513. arch/arm/mach-imx/mach-imx51.c +1 −3
  1514. arch/arm/mach-imx/mach-imx53.c +2 −2
  1515. arch/arm/mach-imx/mach-imx6q.c +0 −3
  1516. arch/arm/mach-imx/mach-imx6sl.c +0 −4
  1517. arch/arm/mach-imx/mach-imx6sx.c +54 −4
  1518. arch/arm/mach-imx/mach-ls1021a.c +22 −0
  1519. arch/arm/mach-imx/mach-mx1ads.c +0 −154
  1520. arch/arm/mach-imx/mach-mx31_3ds.c +2 −2
  1521. arch/arm/mach-imx/mach-mx31lite.c +1 −1
  1522. arch/arm/mach-imx/mach-mxt_td60.c +0 −273
  1523. arch/arm/mach-imx/mach-pcm037.c +2 −2
  1524. arch/arm/mach-imx/mach-pcm038.c +0 −358
  1525. arch/arm/mach-imx/mach-vf610.c +0 −10
  1526. arch/arm/mach-imx/mmdc.c +17 −1
  1527. arch/arm/mach-imx/mxc.h +4 −0
  1528. arch/arm/mach-imx/pcm970-baseboard.c +0 −231
  1529. arch/arm/mach-imx/platsmp.c +33 −10
  1530. arch/arm/mach-imx/pm-imx6.c +5 −10
  1531. arch/arm/mach-imx/suspend-imx6.S +7 −7
  1532. arch/arm/mach-imx/system.c +0 −15
  1533. arch/arm/mach-imx/time.c +26 −5
  1534. arch/arm/mach-imx/tzic.c +1 −2
  1535. arch/arm/mach-integrator/Kconfig +23 −0
  1536. arch/arm/mach-integrator/Makefile +1 −1
  1537. arch/arm/mach-integrator/cm.h +0 −1
  1538. arch/arm/mach-integrator/common.h +0 −2
  1539. arch/arm/mach-integrator/core.c +0 −103
  1540. arch/arm/mach-integrator/impd1.c +48 −0
  1541. arch/arm/mach-integrator/include/mach/uncompress.h +0 −48
  1542. arch/arm/mach-integrator/integrator_ap.c +0 −218
  1543. arch/arm/mach-integrator/integrator_cp.c +0 −28
  1544. arch/arm/mach-integrator/leds.c +0 −124
  1545. arch/arm/mach-integrator/pci_v3.c +12 −11
  1546. arch/arm/mach-iop13xx/Makefile +0 −5
  1547. arch/arm/mach-iop13xx/msi.c +5 −5
  1548. arch/arm/mach-iop32x/Makefile +0 −3
  1549. arch/arm/mach-iop33x/Makefile +0 −3
  1550. arch/arm/mach-ixp4xx/common.c +1 −1
  1551. arch/arm/mach-ixp4xx/include/mach/io.h +24 −4
  1552. arch/arm/mach-keystone/Kconfig +2 −0
  1553. arch/arm/mach-keystone/pm_domain.c +1 −1
  1554. arch/arm/mach-ks8695/Makefile +0 −3
  1555. arch/arm/mach-lpc32xx/common.c +6 −23
  1556. arch/arm/mach-mediatek/Kconfig +2 −2
  1557. arch/arm/mach-mediatek/mediatek.c +3 −0
  1558. arch/arm/mach-meson/Kconfig +19 −0
  1559. arch/arm/mach-meson/Makefile +1 −0
  1560. arch/arm/mach-meson/meson.c +29 −0
  1561. arch/arm/mach-mmp/Kconfig +6 −6
  1562. arch/arm/mach-mmp/gplugd.c +1 −0
  1563. arch/arm/mach-mmp/mmp-dt.c +18 −39
  1564. arch/arm/mach-mmp/mmp2-dt.c +9 −17
  1565. arch/arm/mach-msm/board-mahimahi.c +0 −83
  1566. arch/arm/mach-msm/board-msm7x30.c +1 −1
  1567. arch/arm/mach-msm/board-trout-gpio.c +1 −1
  1568. arch/arm/mach-msm/board-trout.c +1 −1
  1569. arch/arm/mach-msm/clock-pcom.c +0 −1
  1570. arch/arm/mach-msm/io.c +2 −4
  1571. arch/arm/mach-msm/smd.c +0 −1
  1572. arch/arm/mach-mvebu/Makefile +1 −1
  1573. arch/arm/mach-mvebu/armada-370-xp.h +0 −6
  1574. arch/arm/mach-mvebu/board-v7.c +58 −66
  1575. arch/arm/mach-mvebu/coherency.c +38 −185
  1576. arch/arm/mach-mvebu/coherency_ll.S +19 −2
  1577. arch/arm/mach-mvebu/common.h +2 −0
  1578. arch/arm/mach-mvebu/cpu-reset.c +0 −1
  1579. arch/arm/mach-mvebu/headsmp-a9.S +1 −0
  1580. arch/arm/mach-mvebu/platsmp-a9.c +51 −2
  1581. arch/arm/mach-mvebu/platsmp.c +17 −16
  1582. arch/arm/mach-mvebu/pm-board.c +141 −0
  1583. arch/arm/mach-mvebu/pm.c +218 −0
  1584. arch/arm/mach-mvebu/pmsu.c +8 −3
  1585. arch/arm/mach-mvebu/pmsu.h +3 −0
  1586. arch/arm/mach-mvebu/pmsu_ll.S +21 −7
  1587. arch/arm/mach-nomadik/cpu-8815.c +1 −0
  1588. arch/arm/mach-omap1/pm_bus.c +2 −2
  1589. arch/arm/mach-omap2/Kconfig +6 −32
  1590. arch/arm/mach-omap2/Makefile +11 −15
  1591. arch/arm/mach-omap2/am33xx-restart.c +2 −10
  1592. arch/arm/mach-omap2/board-3430sdp.c +0 −633
  1593. arch/arm/mach-omap2/board-am3517crane.c +1 −1
  1594. arch/arm/mach-omap2/board-am3517evm.c +0 −1
  1595. arch/arm/mach-omap2/board-cm-t35.c +1 −4
  1596. arch/arm/mach-omap2/board-cm-t3517.c +1 −3
  1597. arch/arm/mach-omap2/board-devkit8000.c +0 −1
  1598. arch/arm/mach-omap2/board-flash.c +1 −2
  1599. arch/arm/mach-omap2/board-flash.h +0 −1
  1600. arch/arm/mach-omap2/board-generic.c +17 −27
  1601. arch/arm/mach-omap2/board-ldp.c +0 −1
  1602. arch/arm/mach-omap2/board-n8x0.c +5 −25
  1603. arch/arm/mach-omap2/board-omap3beagle.c +0 −1
  1604. arch/arm/mach-omap2/board-omap3logic.c +0 −2
  1605. arch/arm/mach-omap2/board-omap3pandora.c +1 −2
  1606. arch/arm/mach-omap2/board-omap3stalker.c +0 −1
  1607. arch/arm/mach-omap2/board-omap3touchbook.c +0 −1
  1608. arch/arm/mach-omap2/board-overo.c +0 −1
  1609. arch/arm/mach-omap2/board-rx51-peripherals.c +35 −72
  1610. arch/arm/mach-omap2/board-rx51.c +0 −1
  1611. arch/arm/mach-omap2/board-ti8168evm.c +0 −62
  1612. arch/arm/mach-omap2/cclock3xxx_data.c +20 −9
  1613. arch/arm/mach-omap2/clock.c +6 −1
  1614. arch/arm/mach-omap2/clock.h +1 −2
  1615. arch/arm/mach-omap2/clock3xxx.c +37 −1
  1616. arch/arm/mach-omap2/cm.h +15 −3
  1617. arch/arm/mach-omap2/cm1_44xx.h +0 −2
  1618. arch/arm/mach-omap2/cm1_54xx.h +0 −2
  1619. arch/arm/mach-omap2/cm1_7xx.h +0 −2
  1620. arch/arm/mach-omap2/cm2_44xx.h +0 −2
  1621. arch/arm/mach-omap2/cm2_54xx.h +0 −2
  1622. arch/arm/mach-omap2/cm2_7xx.h +0 −2
  1623. arch/arm/mach-omap2/cm2xxx.c +10 −7
  1624. arch/arm/mach-omap2/cm2xxx.h +2 −8
  1625. arch/arm/mach-omap2/cm33xx.c +41 −20
  1626. arch/arm/mach-omap2/cm33xx.h +1 −36
  1627. arch/arm/mach-omap2/cm3xxx.c +11 −8
  1628. arch/arm/mach-omap2/cm3xxx.h +0 −12
  1629. arch/arm/mach-omap2/cm44xx.c +0 −49
  1630. arch/arm/mach-omap2/cm44xx.h +3 −0
  1631. arch/arm/mach-omap2/cm_44xx_54xx.h +0 −36
  1632. arch/arm/mach-omap2/cm_common.c +78 −4
  1633. arch/arm/mach-omap2/cminst44xx.c +47 −33
  1634. arch/arm/mach-omap2/cminst44xx.h +0 −43
  1635. arch/arm/mach-omap2/common-board-devices.h +5 −0
  1636. arch/arm/mach-omap2/common.h +3 −24
  1637. arch/arm/mach-omap2/cpuidle34xx.c +0 −7
  1638. arch/arm/mach-omap2/cpuidle44xx.c +2 −3
  1639. arch/arm/mach-omap2/devices.c +27 −66
  1640. arch/arm/mach-omap2/display.c +1 −1
  1641. arch/arm/mach-omap2/dpll3xxx.c +119 −60
  1642. arch/arm/mach-omap2/dpll44xx.c +41 −0
  1643. arch/arm/mach-omap2/emu.c +0 −50
  1644. arch/arm/mach-omap2/gpmc-nand.c +1 −2
  1645. arch/arm/mach-omap2/gpmc-nand.h +0 −27
  1646. arch/arm/mach-omap2/gpmc-onenand.c +1 −2
  1647. arch/arm/mach-omap2/gpmc-onenand.h +0 −24
  1648. arch/arm/mach-omap2/gpmc-smc91x.c +0 −186
  1649. arch/arm/mach-omap2/gpmc-smc91x.h +0 −42
  1650. arch/arm/mach-omap2/gpmc.c +0 −1889
  1651. arch/arm/mach-omap2/gpmc.h +5 −222
  1652. arch/arm/mach-omap2/hdq1w.c +2 −2
  1653. arch/arm/mach-omap2/hsmmc.c +64 −94
  1654. arch/arm/mach-omap2/hsmmc.h +1 −8
  1655. arch/arm/mach-omap2/i2c.c +1 −1
  1656. arch/arm/mach-omap2/id.c +6 −2
  1657. arch/arm/mach-omap2/io.c +27 −21
  1658. arch/arm/mach-omap2/irq.c +0 −380
  1659. arch/arm/mach-omap2/mmc.h +0 −10
  1660. arch/arm/mach-omap2/msdi.c +2 −2
  1661. arch/arm/mach-omap2/mux.c +1 −1
  1662. arch/arm/mach-omap2/omap-mpuss-lowpower.c +78 −32
  1663. arch/arm/mach-omap2/omap-secure.h +1 −0
  1664. arch/arm/mach-omap2/omap-wakeupgen.c +19 −1
  1665. arch/arm/mach-omap2/omap-wakeupgen.h +1 −0
  1666. arch/arm/mach-omap2/omap2-restart.c +2 −3
  1667. arch/arm/mach-omap2/omap3-restart.c +2 −5
  1668. arch/arm/mach-omap2/omap4-common.c +21 −2
  1669. arch/arm/mach-omap2/omap4-restart.c +2 −4
  1670. arch/arm/mach-omap2/omap_device.c +5 −1
  1671. arch/arm/mach-omap2/omap_hwmod.c +91 −211
  1672. arch/arm/mach-omap2/omap_hwmod.h +12 −0
  1673. arch/arm/mach-omap2/omap_hwmod_2430_data.c +2 −2
  1674. arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c +4 −4
  1675. arch/arm/mach-omap2/omap_hwmod_33xx_data.c +0 −1
  1676. arch/arm/mach-omap2/omap_hwmod_3xxx_data.c +10 −10
  1677. arch/arm/mach-omap2/omap_hwmod_43xx_data.c +39 −0
  1678. arch/arm/mach-omap2/omap_hwmod_44xx_data.c +18 −11
  1679. arch/arm/mach-omap2/omap_hwmod_54xx_data.c +7 −2
  1680. arch/arm/mach-omap2/omap_hwmod_7xx_data.c +102 −2
  1681. arch/arm/mach-omap2/omap_phy_internal.c +5 −3
  1682. arch/arm/mach-omap2/pdata-quirks.c +55 −8
  1683. arch/arm/mach-omap2/pm.c +1 −1
  1684. arch/arm/mach-omap2/pm.h +1 −0
  1685. arch/arm/mach-omap2/pm34xx.c +2 −2
  1686. arch/arm/mach-omap2/pm44xx.c +92 −63
  1687. arch/arm/mach-omap2/powerdomain.c +78 −1
  1688. arch/arm/mach-omap2/powerdomain.h +4 −0
  1689. arch/arm/mach-omap2/powerdomains54xx_data.c +6 −6
  1690. arch/arm/mach-omap2/powerdomains7xx_data.c +7 −7
  1691. arch/arm/mach-omap2/prm.h +16 −0
  1692. arch/arm/mach-omap2/prm2xxx.c +5 −1
  1693. arch/arm/mach-omap2/prm2xxx.h +0 −1
  1694. arch/arm/mach-omap2/prm2xxx_3xxx.c +14 −5
  1695. arch/arm/mach-omap2/prm2xxx_3xxx.h +6 −3
  1696. arch/arm/mach-omap2/prm33xx.c +55 −9
  1697. arch/arm/mach-omap2/prm33xx.h +2 −9
  1698. arch/arm/mach-omap2/prm3xxx.c +34 −16
  1699. arch/arm/mach-omap2/prm3xxx.h +0 −16
  1700. arch/arm/mach-omap2/prm44xx.c +103 −23
  1701. arch/arm/mach-omap2/prm44xx_54xx.h +0 −19
  1702. arch/arm/mach-omap2/prm_common.c +100 −3
  1703. arch/arm/mach-omap2/prminst44xx.c +32 −18
  1704. arch/arm/mach-omap2/prminst44xx.h +6 −2
  1705. arch/arm/mach-omap2/serial.c +0 −3
  1706. arch/arm/mach-omap2/smartreflex-class3.c +2 −2
  1707. arch/arm/mach-omap2/soc.h +1 −0
  1708. arch/arm/mach-omap2/sr_device.c +1 −1
  1709. arch/arm/mach-omap2/sram.c +1 −38
  1710. arch/arm/mach-omap2/sram.h +0 −7
  1711. arch/arm/mach-omap2/timer.c +3 −3
  1712. arch/arm/mach-omap2/twl-common.c +1 −11
  1713. arch/arm/mach-omap2/vc.c +1 −1
  1714. arch/arm/mach-omap2/voltage.c +11 −11
  1715. arch/arm/mach-omap2/wd_timer.c +2 −2
  1716. arch/arm/mach-orion5x/dns323-setup.c +4 −4
  1717. arch/arm/mach-orion5x/terastation_pro2-setup.c +1 −1
  1718. arch/arm/mach-orion5x/ts209-setup.c +1 −1
  1719. arch/arm/mach-orion5x/ts409-setup.c +1 −1
  1720. arch/arm/mach-orion5x/ts78xx-setup.c +2 −2
  1721. arch/arm/mach-prima2/pm.c +0 −1
  1722. arch/arm/mach-prima2/rstc.c +0 −1
  1723. arch/arm/mach-prima2/rtciobrg.c +0 −1
  1724. arch/arm/mach-pxa/Kconfig +11 −0
  1725. arch/arm/mach-pxa/Makefile +1 −0
  1726. arch/arm/mach-pxa/devices.c +40 −2
  1727. arch/arm/mach-pxa/devices.h +3 −0
  1728. arch/arm/mach-pxa/em-x270.c +2 −2
  1729. arch/arm/mach-pxa/generic.h +42 −23
  1730. arch/arm/mach-pxa/gumstix.c +1 −2
  1731. arch/arm/mach-pxa/include/mach/addr-map.h +5 −0
  1732. arch/arm/mach-pxa/include/mach/pxa25x.h +0 −8
  1733. arch/arm/mach-pxa/include/mach/pxa27x.h +0 −4
  1734. arch/arm/mach-pxa/include/mach/pxa2xx-regs.h +10 −0
  1735. arch/arm/mach-pxa/include/mach/pxa3xx.h +0 −5
  1736. arch/arm/mach-pxa/lpd270.c +6 −6
  1737. arch/arm/mach-pxa/mfp-pxa2xx.c +5 −7
  1738. arch/arm/mach-pxa/poodle.c +1 −1
  1739. arch/arm/mach-pxa/pxa-dt.c +15 −3
  1740. arch/arm/mach-pxa/pxa27x.c +6 −0
  1741. arch/arm/mach-pxa/pxa3xx-ulpi.c +3 −4
  1742. arch/arm/mach-pxa/pxa3xx.c +7 −7
  1743. arch/arm/mach-pxa/raumfeld.c +13 −13
  1744. arch/arm/mach-pxa/spitz.c +9 −0
  1745. arch/arm/mach-pxa/tosa-bt.c +0 −1
  1746. arch/arm/mach-pxa/tosa.c +7 −34
  1747. arch/arm/mach-qcom/board.c +2 −0
  1748. arch/arm/mach-realview/Kconfig +13 −0
  1749. arch/arm/mach-realview/Makefile +1 −0
  1750. arch/arm/mach-realview/realview-dt.c +32 −0
  1751. arch/arm/mach-rockchip/Kconfig +1 −0
  1752. arch/arm/mach-rockchip/headsmp.S +4 −1
  1753. arch/arm/mach-rockchip/platsmp.c +180 −43
  1754. arch/arm/mach-rockchip/rockchip.c +7 −0
  1755. arch/arm/mach-rpc/Makefile +0 −4
  1756. arch/arm/mach-s3c24xx/Kconfig +0 −2
  1757. arch/arm/mach-s3c24xx/Makefile +0 −5
  1758. arch/arm/mach-s3c24xx/common.c +0 −4
  1759. arch/arm/mach-s3c24xx/common.h +0 −5
  1760. arch/arm/mach-s3c24xx/h1940-bluetooth.c +2 −2
  1761. arch/arm/mach-s3c24xx/h1940.h +3 −1
  1762. arch/arm/mach-s3c24xx/include/mach/regs-s3c2443-clock.h +0 −2
  1763. arch/arm/mach-s3c24xx/mach-amlm5900.c +0 −1
  1764. arch/arm/mach-s3c24xx/mach-anubis.c +0 −1
  1765. arch/arm/mach-s3c24xx/mach-at2440evb.c +0 −1
  1766. arch/arm/mach-s3c24xx/mach-bast.c +0 −1
  1767. arch/arm/mach-s3c24xx/mach-gta02.c +0 −1
  1768. arch/arm/mach-s3c24xx/mach-h1940.c +2 −2
  1769. arch/arm/mach-s3c24xx/mach-jive.c +0 −1
  1770. arch/arm/mach-s3c24xx/mach-mini2440.c +0 −1
  1771. arch/arm/mach-s3c24xx/mach-n30.c +0 −2
  1772. arch/arm/mach-s3c24xx/mach-nexcoder.c +0 −1
  1773. arch/arm/mach-s3c24xx/mach-osiris-dvs.c +0 −1
  1774. arch/arm/mach-s3c24xx/mach-osiris.c +0 −1
  1775. arch/arm/mach-s3c24xx/mach-otom.c +0 −1
  1776. arch/arm/mach-s3c24xx/mach-qt2410.c +0 −1
  1777. arch/arm/mach-s3c24xx/mach-rx1950.c +2 −2
  1778. arch/arm/mach-s3c24xx/mach-rx3715.c +0 −1
  1779. arch/arm/mach-s3c24xx/mach-s3c2416-dt.c +0 −1
  1780. arch/arm/mach-s3c24xx/mach-smdk2410.c +0 −1
  1781. arch/arm/mach-s3c24xx/mach-smdk2413.c +0 −3
  1782. arch/arm/mach-s3c24xx/mach-smdk2416.c +0 −1
  1783. arch/arm/mach-s3c24xx/mach-smdk2440.c +0 −1
  1784. arch/arm/mach-s3c24xx/mach-smdk2443.c +0 −1
  1785. arch/arm/mach-s3c24xx/mach-tct_hammer.c +0 −1
  1786. arch/arm/mach-s3c24xx/mach-vr1000.c +0 −1
  1787. arch/arm/mach-s3c24xx/mach-vstms.c +0 −1
  1788. arch/arm/mach-s3c24xx/s3c2410.c +0 −13
  1789. arch/arm/mach-s3c24xx/s3c2412.c +0 −23
  1790. arch/arm/mach-s3c24xx/s3c2416.c +0 −8
  1791. arch/arm/mach-s3c24xx/s3c2443.c +0 −8
  1792. arch/arm/mach-s3c24xx/s3c244x.c +0 −12
  1793. arch/arm/mach-s3c64xx/Makefile +0 −5
  1794. arch/arm/mach-s3c64xx/common.c +0 −5
  1795. arch/arm/mach-s3c64xx/common.h +0 −7
  1796. arch/arm/mach-s3c64xx/cpuidle.c +0 −1
  1797. arch/arm/mach-s3c64xx/mach-anw6410.c +0 −1
  1798. arch/arm/mach-s3c64xx/mach-crag6410.c +0 −1
  1799. arch/arm/mach-s3c64xx/mach-hmt.c +0 −1
  1800. arch/arm/mach-s3c64xx/mach-mini6410.c +0 −1
  1801. arch/arm/mach-s3c64xx/mach-ncp.c +0 −1
  1802. arch/arm/mach-s3c64xx/mach-real6410.c +0 −1
  1803. arch/arm/mach-s3c64xx/mach-smartq5.c +0 −1
  1804. arch/arm/mach-s3c64xx/mach-smartq7.c +0 −1
  1805. arch/arm/mach-s3c64xx/mach-smdk6400.c +0 −1
  1806. arch/arm/mach-s3c64xx/mach-smdk6410.c +0 −1
  1807. arch/arm/mach-s3c64xx/pm.c +0 −7
  1808. arch/arm/mach-s5pv210/Makefile +0 −5
  1809. arch/arm/mach-s5pv210/pm.c +1 −2
  1810. arch/arm/mach-s5pv210/regs-clock.h +1 −2
  1811. arch/arm/mach-s5pv210/s5pv210.c +1 −1
  1812. arch/arm/mach-sa1100/Kconfig +2 −0
  1813. arch/arm/mach-sa1100/Makefile +0 −3
  1814. arch/arm/mach-sa1100/clock.c +36 −7
  1815. arch/arm/mach-sa1100/collie.c +7 −48
  1816. arch/arm/mach-sa1100/h3xxx.c +15 −0
  1817. arch/arm/mach-sa1100/include/mach/debug-macro.S +0 −62
  1818. arch/arm/mach-sa1100/include/mach/entry-macro.S +0 −41
  1819. arch/arm/mach-sa1100/include/mach/irqs.h +51 −51
  1820. arch/arm/mach-sa1100/irq.c +130 −99
  1821. arch/arm/mach-sa1100/neponset.c +0 −1
  1822. arch/arm/mach-sa1100/pci-nanoengine.c +4 −4
  1823. arch/arm/mach-shmobile/Kconfig +46 −90
  1824. arch/arm/mach-shmobile/Makefile +16 −27
  1825. arch/arm/mach-shmobile/Makefile.boot +0 −3
  1826. arch/arm/mach-shmobile/board-ape6evm-reference.c +2 −7
  1827. arch/arm/mach-shmobile/board-ape6evm.c +2 −5
  1828. arch/arm/mach-shmobile/board-armadillo800eva-reference.c +0 −198
  1829. arch/arm/mach-shmobile/board-armadillo800eva.c +37 −28
  1830. arch/arm/mach-shmobile/board-bockw-reference.c +2 −5
  1831. arch/arm/mach-shmobile/board-bockw.c +1 −5
  1832. arch/arm/mach-shmobile/board-genmai-reference.c +0 −55
  1833. arch/arm/mach-shmobile/board-genmai.c +0 −161
  1834. arch/arm/mach-shmobile/board-koelsch-reference.c +0 −120
  1835. arch/arm/mach-shmobile/board-koelsch.c +0 −531
  1836. arch/arm/mach-shmobile/board-kzm9g-reference.c +10 −6
  1837. arch/arm/mach-shmobile/board-kzm9g.c +1 −5
  1838. arch/arm/mach-shmobile/board-lager-reference.c +0 −87
  1839. arch/arm/mach-shmobile/board-lager.c +0 −65
  1840. arch/arm/mach-shmobile/board-mackerel.c +3 −6
  1841. arch/arm/mach-shmobile/board-marzen-reference.c +1 −16
  1842. arch/arm/mach-shmobile/board-marzen.c +0 −63
  1843. arch/arm/mach-shmobile/clock-r7s72100.c +0 −231
  1844. arch/arm/mach-shmobile/clock-r8a73a4.c +0 −4
  1845. arch/arm/mach-shmobile/clock-r8a7740.c +7 −6
  1846. arch/arm/mach-shmobile/clock-r8a7778.c +0 −4
  1847. arch/arm/mach-shmobile/clock-r8a7779.c +0 −4
  1848. arch/arm/mach-shmobile/clock-r8a7790.c +1 −5
  1849. arch/arm/mach-shmobile/clock-r8a7791.c +0 −342
  1850. arch/arm/mach-shmobile/clock-sh7372.c +0 −4
  1851. arch/arm/mach-shmobile/clock-sh73a0.c +0 −4
  1852. arch/arm/mach-shmobile/clock.c +3 −33
  1853. arch/arm/mach-shmobile/clock.h +0 −14
  1854. arch/arm/mach-shmobile/common.h +0 −7
  1855. arch/arm/mach-shmobile/console.c +0 −4
  1856. arch/arm/mach-shmobile/cpufreq.c +1 −1
  1857. arch/arm/mach-shmobile/dma-register.h +2 −2
  1858. arch/arm/mach-shmobile/headsmp-scu.S +0 −5
  1859. arch/arm/mach-shmobile/intc-sh7372.c +0 −4
  1860. arch/arm/mach-shmobile/intc-sh73a0.c +0 −4
  1861. arch/arm/mach-shmobile/intc.h +5 −0
  1862. arch/arm/mach-shmobile/irqs.h +1 −7
  1863. arch/arm/mach-shmobile/platsmp-apmu.c +9 −18
  1864. arch/arm/mach-shmobile/platsmp-apmu.h +32 −0
  1865. arch/arm/mach-shmobile/pm-r8a7740.c +47 −14
  1866. arch/arm/mach-shmobile/pm-r8a7779.c +1 −3
  1867. arch/arm/mach-shmobile/pm-rcar.c +0 −4
  1868. arch/arm/mach-shmobile/pm-rmobile.c +1 −5
  1869. arch/arm/mach-shmobile/pm-rmobile.h +2 −2
  1870. arch/arm/mach-shmobile/pm-sh7372.c +0 −4
  1871. arch/arm/mach-shmobile/r7s72100.h +0 −7
  1872. arch/arm/mach-shmobile/r8a73a4.h +0 −2
  1873. arch/arm/mach-shmobile/r8a7740.h +2 −7
  1874. arch/arm/mach-shmobile/r8a7778.h +0 −5
  1875. arch/arm/mach-shmobile/r8a7779.h +0 −1
  1876. arch/arm/mach-shmobile/r8a7790.h +0 −1
  1877. arch/arm/mach-shmobile/r8a7791.h +0 −4
  1878. arch/arm/mach-shmobile/setup-emev2.c +0 −4
  1879. arch/arm/mach-shmobile/setup-r7s72100.c +1 −27
  1880. arch/arm/mach-shmobile/setup-r8a73a4.c +4 −19
  1881. arch/arm/mach-shmobile/setup-r8a7740.c +44 −32
  1882. arch/arm/mach-shmobile/setup-r8a7778.c +4 −13
  1883. arch/arm/mach-shmobile/setup-r8a7779.c +10 −21
  1884. arch/arm/mach-shmobile/setup-r8a7790.c +1 −10
  1885. arch/arm/mach-shmobile/setup-r8a7791.c +1 −189
  1886. arch/arm/mach-shmobile/setup-r8a7794.c +33 −0
  1887. arch/arm/mach-shmobile/setup-rcar-gen2.c +49 −27
  1888. arch/arm/mach-shmobile/setup-sh7372.c +6 −8
  1889. arch/arm/mach-shmobile/setup-sh73a0.c +34 −27
  1890. arch/arm/mach-shmobile/sh73a0.h +0 −1
  1891. arch/arm/mach-shmobile/sleep-sh7372.S +0 −5
  1892. arch/arm/mach-shmobile/smp-emev2.c +0 −4
  1893. arch/arm/mach-shmobile/smp-r8a7779.c +0 −4
  1894. arch/arm/mach-shmobile/smp-r8a7790.c +15 −1
  1895. arch/arm/mach-shmobile/smp-r8a7791.c +11 −1
  1896. arch/arm/mach-shmobile/smp-sh73a0.c +0 −4
  1897. arch/arm/mach-shmobile/timer.c +18 −32
  1898. arch/arm/mach-socfpga/core.h +4 −1
  1899. arch/arm/mach-socfpga/headsmp.S +15 −10
  1900. arch/arm/mach-socfpga/platsmp.c +12 −9
  1901. arch/arm/mach-socfpga/socfpga.c +2 −2
  1902. arch/arm/mach-spear/Kconfig +4 −5
  1903. arch/arm/mach-sti/Kconfig +10 −0
  1904. arch/arm/mach-sunxi/Kconfig +7 −0
  1905. arch/arm/mach-sunxi/platsmp.c +1 −1
  1906. arch/arm/mach-sunxi/sunxi.c +9 −76
  1907. arch/arm/mach-tegra/Kconfig +1 −8
  1908. arch/arm/mach-tegra/cpuidle-tegra114.c +1 −2
  1909. arch/arm/mach-tegra/cpuidle-tegra20.c +1 −2
  1910. arch/arm/mach-tegra/cpuidle-tegra30.c +0 −1
  1911. arch/arm/mach-tegra/flowctrl.c +37 −7
  1912. arch/arm/mach-tegra/flowctrl.h +2 −0
  1913. arch/arm/mach-tegra/irq.c +11 −11
  1914. arch/arm/mach-tegra/reset-handler.S +1 −0
  1915. arch/arm/mach-tegra/tegra.c +2 −0
  1916. arch/arm/mach-u300/Makefile +0 −3
  1917. arch/arm/mach-u300/dummyspichip.c +29 −36
  1918. arch/arm/mach-u300/regulator.c +0 −1
  1919. arch/arm/mach-ux500/Kconfig +1 −0
  1920. arch/arm/mach-ux500/Makefile +1 −0
  1921. arch/arm/mach-ux500/pm.c +4 −0
  1922. arch/arm/mach-ux500/pm_domains.c +79 −0
  1923. arch/arm/mach-ux500/pm_domains.h +17 −0
  1924. arch/arm/mach-vexpress/Kconfig +1 −3
  1925. arch/arm/mach-vexpress/Makefile +1 −2
  1926. arch/arm/mach-vexpress/core.h +0 −7
  1927. arch/arm/mach-vexpress/ct-ca9x4.c +0 −212
  1928. arch/arm/mach-vexpress/include/mach/ct-ca9x4.h +0 −47
  1929. arch/arm/mach-vexpress/include/mach/hardware.h +0 −1
  1930. arch/arm/mach-vexpress/include/mach/irqs.h +0 −6
  1931. arch/arm/mach-vexpress/include/mach/motherboard.h +0 −88
  1932. arch/arm/mach-vexpress/platsmp.c +0 −42
  1933. arch/arm/mach-vexpress/v2m.c +0 −374
  1934. arch/arm/mach-vt8500/vt8500.c +1 −1
  1935. arch/arm/mach-zynq/Makefile +1 −4
  1936. arch/arm/mach-zynq/common.c +10 −3
  1937. arch/arm/mach-zynq/common.h +14 −3
  1938. arch/arm/mach-zynq/hotplug.c +0 −59
  1939. arch/arm/mach-zynq/platsmp.c +40 −1
  1940. arch/arm/mach-zynq/pm.c +83 −0
  1941. arch/arm/mach-zynq/slcr.c +42 −1
  1942. arch/arm/mm/Kconfig +36 −14
  1943. arch/arm/mm/Makefile +1 −1
  1944. arch/arm/mm/alignment.c +5 −5
  1945. arch/arm/mm/cache-feroceon-l2.c +3 −3
  1946. arch/arm/mm/cache-l2x0.c +131 −0
  1947. arch/arm/mm/cache-tauros2.c +6 −6
  1948. arch/arm/mm/context.c +34 −24
  1949. arch/arm/mm/copypage-v6.c +1 −1
  1950. arch/arm/mm/dma-mapping.c +135 −160
  1951. arch/arm/mm/dump.c +2 −7
  1952. arch/arm/mm/fault-armv.c +3 −3
  1953. arch/arm/mm/fault.c +15 −16
  1954. arch/arm/mm/flush.c +16 −1
  1955. arch/arm/mm/highmem.c +11 −7
  1956. arch/arm/mm/idmap.c +1 −1
  1957. arch/arm/mm/init.c +159 −9
  1958. arch/arm/mm/mmu.c +68 −67
  1959. arch/arm/mm/pageattr.c +91 −0
  1960. arch/arm/mm/proc-macros.S +1 −1
  1961. arch/arm/mm/proc-v7.S +4 −5
  1962. arch/arm/mm/proc-xscale.S +2 −2
  1963. arch/arm/net/bpf_jit_32.c +29 −8
  1964. arch/arm/net/bpf_jit_32.h +14 −0
  1965. arch/arm/nwfpe/fpmodule.c +4 −4
  1966. arch/arm/plat-iop/Makefile +0 −6
  1967. arch/arm/plat-omap/Makefile +0 −3
  1968. arch/arm/plat-omap/dma.c +6 −731
  1969. arch/arm/plat-orion/common.c +1 −1
  1970. arch/arm/plat-orion/gpio.c +34 −5
  1971. arch/arm/plat-orion/include/plat/orion-gpio.h +4 −1
  1972. arch/arm/plat-pxa/ssp.c +1 −1
  1973. arch/arm/plat-samsung/Kconfig +3 −2
  1974. arch/arm/plat-samsung/Makefile +1 −5
  1975. arch/arm/plat-samsung/adc.c +0 −1
  1976. arch/arm/plat-samsung/include/plat/map-s5p.h +0 −21
  1977. arch/arm/plat-samsung/pm-debug.c +1 −0
  1978. arch/arm/plat-versatile/Kconfig +1 −1
  1979. arch/arm/vfp/vfphw.S +6 −0
  1980. arch/arm/vfp/vfpmodule.c +56 −46
  1981. arch/arm/vfp/vfpsingle.c +1 −1
  1982. arch/arm/xen/Makefile +1 −1
  1983. arch/arm/xen/enlighten.c +0 −5
  1984. arch/arm/xen/mm.c +121 −0
  1985. arch/arm/xen/mm32.c +0 −202
  1986. arch/arm64/Kconfig +234 −9
  1987. arch/arm64/Kconfig.debug +23 −0
  1988. arch/arm64/Makefile +9 −4
  1989. arch/arm64/boot/dts/Makefile +7 −8
  1990. arch/arm64/boot/dts/amd/Makefile +5 −0
  1991. arch/arm64/boot/dts/amd/amd-overdrive.dts +66 −0
  1992. arch/arm64/boot/dts/amd/amd-seattle-clks.dtsi +54 −0
  1993. arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi +172 −0
  1994. arch/arm64/boot/dts/apm-storm.dtsi +0 −425
  1995. arch/arm64/boot/dts/apm/Makefile +5 −0
  1996. arch/arm64/boot/dts/apm/apm-mustang.dts +16 −0
  1997. arch/arm64/boot/dts/apm/apm-storm.dtsi +660 −0
  1998. arch/arm64/boot/dts/arm/Makefile +7 −0
  1999. arch/arm64/boot/dts/arm/foundation-v8.dts +4 −4
  2000. arch/arm64/boot/dts/arm/juno-clocks.dtsi +44 −0
  2001. arch/arm64/boot/dts/arm/juno-motherboard.dtsi +129 −0
  2002. arch/arm64/boot/dts/arm/juno.dts +218 −0
  2003. arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts +4 −4
  2004. arch/arm64/boot/dts/arm/rtsm_ve-motherboard.dtsi +34 −1
  2005. arch/arm64/boot/dts/cavium/Makefile +5 −0
  2006. arch/arm64/boot/dts/cavium/thunder-88xx.dts +67 −0
  2007. arch/arm64/boot/dts/cavium/thunder-88xx.dtsi +401 −0
  2008. arch/arm64/boot/dts/include/dt-bindings +1 −0
  2009. arch/arm64/configs/defconfig +31 −5
  2010. arch/arm64/crypto/Kconfig +6 −3
  2011. arch/arm64/crypto/Makefile +4 −0
  2012. arch/arm64/crypto/aes-ce-ccm-glue.c +4 −2
  2013. arch/arm64/crypto/aes-ce-cipher.c +111 −1
  2014. arch/arm64/crypto/aes-ce-setkey.h +5 −0
  2015. arch/arm64/crypto/aes-glue.c +16 −10
  2016. arch/arm64/crypto/crc32-arm64.c +274 −0
  2017. arch/arm64/include/asm/Kbuild +4 −2
  2018. arch/arm64/include/asm/alternative-asm.h +29 −0
  2019. arch/arm64/include/asm/alternative.h +44 −0
  2020. arch/arm64/include/asm/arch_timer.h +7 −28
  2021. arch/arm64/include/asm/atomic.h +82 −119
  2022. arch/arm64/include/asm/barrier.h +3 −0
  2023. arch/arm64/include/asm/cache.h +2 −0
  2024. arch/arm64/include/asm/cacheflush.h +5 −1
  2025. arch/arm64/include/asm/cachetype.h +20 −0
  2026. arch/arm64/include/asm/cmpxchg.h +73 −0
  2027. arch/arm64/include/asm/compat.h +9 −2
  2028. arch/arm64/include/asm/cpu.h +7 −0
  2029. arch/arm64/include/asm/cpu_ops.h +5 −2
  2030. arch/arm64/include/asm/cpufeature.h +29 −0
  2031. arch/arm64/include/asm/cpuidle.h +13 −0
  2032. arch/arm64/include/asm/cputype.h +5 −0
  2033. arch/arm64/include/asm/debug-monitors.h +19 −11
  2034. arch/arm64/include/asm/device.h +1 −0
  2035. arch/arm64/include/asm/dma-contiguous.h +0 −28
  2036. arch/arm64/include/asm/dma-mapping.h +15 −0
  2037. arch/arm64/include/asm/dmi.h +31 −0
  2038. arch/arm64/include/asm/elf.h +2 −2
  2039. arch/arm64/include/asm/fixmap.h +5 −3
  2040. arch/arm64/include/asm/hardirq.h +0 −2
  2041. arch/arm64/include/asm/hwcap.h +1 −0
  2042. arch/arm64/include/asm/insn.h +259 −0
  2043. arch/arm64/include/asm/io.h +46 −102
  2044. arch/arm64/include/asm/irq.h +2 −1
  2045. arch/arm64/include/asm/irq_work.h +22 −0
  2046. arch/arm64/include/asm/kgdb.h +1 −1
  2047. arch/arm64/include/asm/kvm_arm.h +22 −10
  2048. arch/arm64/include/asm/kvm_emulate.h +10 −0
  2049. arch/arm64/include/asm/kvm_host.h +18 −9
  2050. arch/arm64/include/asm/kvm_mmu.h +123 −28
  2051. arch/arm64/include/asm/memory.h +3 −1
  2052. arch/arm64/include/asm/opcodes.h +1 −0
  2053. arch/arm64/include/asm/pci.h +37 −0
  2054. arch/arm64/include/asm/percpu.h +217 −2
  2055. arch/arm64/include/asm/pgalloc.h +4 −4
  2056. arch/arm64/include/asm/pgtable.h +46 −18
  2057. arch/arm64/include/asm/proc-fns.h +2 −0
  2058. arch/arm64/include/asm/processor.h +1 −3
  2059. arch/arm64/include/asm/seccomp.h +25 −0
  2060. arch/arm64/include/asm/smp.h +2 −0
  2061. arch/arm64/include/asm/spinlock.h +2 −2
  2062. arch/arm64/include/asm/suspend.h +1 −0
  2063. arch/arm64/include/asm/thread_info.h +7 −2
  2064. arch/arm64/include/asm/tlb.h +17 −64
  2065. arch/arm64/include/asm/traps.h +16 −0
  2066. arch/arm64/include/asm/unistd.h +4 −1
  2067. arch/arm64/include/asm/unistd32.h +4 −1
  2068. arch/arm64/include/asm/xen/page-coherent.h +1 −43
  2069. arch/arm64/include/uapi/asm/kvm.h +2 −0
  2070. arch/arm64/kernel/Makefile +7 −2
  2071. arch/arm64/kernel/alternative.c +85 −0
  2072. arch/arm64/kernel/armv8_deprecated.c +553 −0
  2073. arch/arm64/kernel/cpu_errata.c +111 −0
  2074. arch/arm64/kernel/cpuidle.c +31 −0
  2075. arch/arm64/kernel/cpuinfo.c +57 −4
  2076. arch/arm64/kernel/efi-entry.S +23 −7
  2077. arch/arm64/kernel/efi-stub.c +6 −10
  2078. arch/arm64/kernel/efi.c +43 −38
  2079. arch/arm64/kernel/entry-ftrace.S +11 −10
  2080. arch/arm64/kernel/entry.S +74 −65
  2081. arch/arm64/kernel/ftrace.c +6 −4
  2082. arch/arm64/kernel/head.S +231 −209
  2083. arch/arm64/kernel/insn.c +693 −9
  2084. arch/arm64/kernel/io.c +56 −10
  2085. arch/arm64/kernel/irq.c +1 −26
  2086. arch/arm64/kernel/jump_label.c +9 −14
  2087. arch/arm64/kernel/kgdb.c +2 −2
  2088. arch/arm64/kernel/module.c +19 −0
  2089. arch/arm64/kernel/pci.c +70 −0
  2090. arch/arm64/kernel/perf_event.c +9 −3
  2091. arch/arm64/kernel/perf_regs.c +8 −0
  2092. arch/arm64/kernel/process.c +4 −34
  2093. arch/arm64/kernel/psci.c +106 −0
  2094. arch/arm64/kernel/ptrace.c +42 −2
  2095. arch/arm64/kernel/return_address.c +1 −2
  2096. arch/arm64/kernel/setup.c +90 −30
  2097. arch/arm64/kernel/signal32.c +6 −0
  2098. arch/arm64/kernel/sleep.S +40 −43
  2099. arch/arm64/kernel/smp.c +3 −1
  2100. arch/arm64/kernel/smp_spin_table.c +18 −5
  2101. arch/arm64/kernel/stacktrace.c +1 −2
  2102. arch/arm64/kernel/suspend.c +44 −22
  2103. arch/arm64/kernel/sys_compat.c +29 −20
  2104. arch/arm64/kernel/topology.c +5 −2
  2105. arch/arm64/kernel/trace-events-emulation.h +35 −0
  2106. arch/arm64/kernel/traps.c +67 −2
  2107. arch/arm64/kernel/vmlinux.lds.S +31 −2
  2108. arch/arm64/kvm/guest.c +1 −27
  2109. arch/arm64/kvm/hyp.S +2 −2
  2110. arch/arm64/kvm/sys_regs.c +10 −1
  2111. arch/arm64/kvm/vgic-v2-switch.S +8 −4
  2112. arch/arm64/lib/clear_user.S +1 −1
  2113. arch/arm64/mm/Makefile +2 −1
  2114. arch/arm64/mm/cache.S +8 −2
  2115. arch/arm64/mm/dma-mapping.c +145 −50
  2116. arch/arm64/mm/dump.c +329 −0
  2117. arch/arm64/mm/fault.c +1 −1
  2118. arch/arm64/mm/flush.c +16 −0
  2119. arch/arm64/mm/init.c +10 −2
  2120. arch/arm64/mm/ioremap.c +3 −90
  2121. arch/arm64/mm/mm.h +0 −1
  2122. arch/arm64/mm/mmap.c +3 −11
  2123. arch/arm64/mm/mmu.c +104 −6
  2124. arch/arm64/mm/pageattr.c +97 −0
  2125. arch/arm64/mm/pgd.c +17 −3
  2126. arch/arm64/mm/proc.S +15 −0
  2127. arch/arm64/net/Makefile +4 −0
  2128. arch/arm64/net/bpf_jit.h +173 −0
  2129. arch/arm64/net/bpf_jit_comp.c +746 −0
  2130. arch/avr32/include/asm/Kbuild +1 −1
  2131. arch/avr32/include/asm/atomic.h +63 −62
  2132. arch/avr32/include/uapi/asm/socket.h +5 −0
  2133. arch/avr32/kernel/kprobes.c +1 −1
  2134. arch/avr32/mach-at32ap/at32ap700x.c +9 −12
  2135. arch/avr32/mach-at32ap/include/mach/atmel-mci.h +0 −17
  2136. arch/blackfin/Kconfig +1 −1
  2137. arch/blackfin/include/asm/Kbuild +1 −1
  2138. arch/blackfin/include/asm/barrier.h +51 −0
  2139. arch/blackfin/include/asm/bfin_serial.h +3 −4
  2140. arch/blackfin/include/asm/ipipe.h +1 −1
  2141. arch/blackfin/kernel/perf_event.c +5 −5
  2142. arch/blackfin/mach-bf533/boards/stamp.c +1 −0
  2143. arch/blackfin/mach-bf537/boards/cm_bf537e.c +1 −2
  2144. arch/blackfin/mach-bf537/boards/cm_bf537u.c +1 −2
  2145. arch/blackfin/mach-bf537/boards/stamp.c +1 −2
  2146. arch/blackfin/mach-bf537/boards/tcm_bf537.c +1 −2
  2147. arch/blackfin/mach-bf561/boards/cm_bf561.c +1 −2
  2148. arch/blackfin/mach-common/ints-priority.c +5 −5
  2149. arch/blackfin/mach-common/smp.c +1 −1
  2150. arch/c6x/include/asm/Kbuild +1 −1
  2151. arch/cris/arch-v10/drivers/sync_serial.c +0 −1
  2152. arch/cris/arch-v10/lib/usercopy.c +7 −7
  2153. arch/cris/arch-v32/drivers/Kconfig +1 −7
  2154. arch/cris/arch-v32/drivers/Makefile +0 −1
  2155. arch/cris/arch-v32/drivers/i2c.h +0 −1
  2156. arch/cris/arch-v32/drivers/sync_serial.c +791 −640
  2157. arch/cris/arch-v32/kernel/debugport.c +56 −26
  2158. arch/cris/arch-v32/kernel/time.c +18 −11
  2159. arch/cris/arch-v32/lib/usercopy.c +7 −8
  2160. arch/cris/arch-v32/mach-fs/pinmux.c +83 −69
  2161. arch/cris/include/arch-v32/mach-fs/mach/pinmux.h +0 −2
  2162. arch/cris/include/asm/Kbuild +2 −5
  2163. arch/cris/include/asm/atomic.h +26 −33
  2164. arch/cris/include/asm/io.h +3 −0
  2165. arch/cris/include/asm/sections.h +0 −7
  2166. arch/cris/include/uapi/asm/Kbuild +2 −2
  2167. arch/cris/include/uapi/asm/socket.h +5 −0
  2168. arch/cris/kernel/crisksyms.c +5 −4
  2169. arch/cris/kernel/traps.c +34 −27
  2170. arch/cris/mm/init.c +33 −5
  2171. arch/cris/mm/ioremap.c +2 −1
  2172. arch/frv/include/asm/Kbuild +1 −1
  2173. arch/frv/include/asm/atomic.h +1 −1
  2174. arch/frv/include/asm/io.h +3 −0
  2175. arch/frv/include/asm/processor.h +0 −16
  2176. arch/frv/include/uapi/asm/socket.h +5 −0
  2177. arch/frv/kernel/irq-mb93091.c +4 −4
  2178. arch/frv/kernel/irq-mb93093.c +0 −1
  2179. arch/frv/kernel/irq-mb93493.c +2 −2
  2180. arch/frv/kernel/setup.c +0 −2
  2181. arch/frv/kernel/time.c +0 −1
  2182. arch/frv/mm/extable.c +0 −2
  2183. arch/hexagon/include/asm/Kbuild +1 −1
  2184. arch/hexagon/include/asm/atomic.h +37 −31
  2185. arch/hexagon/include/asm/cache.h +3 −1
  2186. arch/hexagon/include/asm/cacheflush.h +19 −17
  2187. arch/hexagon/include/asm/io.h +0 −5
  2188. arch/hexagon/kernel/setup.c +1 −0
  2189. arch/hexagon/kernel/traps.c +2 −2
  2190. arch/hexagon/kernel/vmlinux.lds.S +2 −2
  2191. arch/hexagon/mm/cache.c +10 −0
  2192. arch/hexagon/mm/ioremap.c +1 −0
  2193. arch/ia64/Kconfig +1 −4
  2194. arch/ia64/Makefile +0 −1
  2195. arch/ia64/include/asm/Kbuild +1 −1
  2196. arch/ia64/include/asm/atomic.h +88 −104
  2197. arch/ia64/include/asm/barrier.h +12 −13
  2198. arch/ia64/include/asm/hw_irq.h +1 −1
  2199. arch/ia64/include/asm/io.h +4 −0
  2200. arch/ia64/include/asm/kvm_host.h +0 −600
  2201. arch/ia64/include/asm/percpu.h +2 −2
  2202. arch/ia64/include/asm/processor.h +0 −1
  2203. arch/ia64/include/asm/pvclock-abi.h +0 −48
  2204. arch/ia64/include/asm/sections.h +1 −1
  2205. arch/ia64/include/asm/sn/arch.h +2 −2
  2206. arch/ia64/include/asm/sn/nodepda.h +1 −1
  2207. arch/ia64/include/asm/switch_to.h +1 −1
  2208. arch/ia64/include/asm/syscall.h +6 −0
  2209. arch/ia64/include/asm/uaccess.h +8 −8
  2210. arch/ia64/include/asm/unistd.h +1 −1
  2211. arch/ia64/include/asm/uv/uv_hub.h +1 −1
  2212. arch/ia64/include/uapi/asm/kvm.h +0 −268
  2213. arch/ia64/include/uapi/asm/siginfo.h +6 −2
  2214. arch/ia64/include/uapi/asm/socket.h +5 −0
  2215. arch/ia64/include/uapi/asm/unistd.h +2 −0
  2216. arch/ia64/kernel/acpi.c +4 −5
  2217. arch/ia64/kernel/efi.c +4 −2
  2218. arch/ia64/kernel/entry.S +2 −0
  2219. arch/ia64/kernel/irq.c +1 −1
  2220. arch/ia64/kernel/irq_ia64.c +2 −2
  2221. arch/ia64/kernel/kprobes.c +3 −3
  2222. arch/ia64/kernel/mca.c +8 −8
  2223. arch/ia64/kernel/msi_ia64.c +5 −5
  2224. arch/ia64/kernel/perfmon.c +1 −11
  2225. arch/ia64/kernel/process.c +3 −3
  2226. arch/ia64/kernel/ptrace.c +1 −1
  2227. arch/ia64/kernel/traps.c +1 −1
  2228. arch/ia64/kvm/Kconfig +0 −66
  2229. arch/ia64/kvm/Makefile +0 −67
  2230. arch/ia64/kvm/asm-offsets.c +0 −241
  2231. arch/ia64/kvm/irq.h +0 −33
  2232. arch/ia64/kvm/kvm-ia64.c +0 −1972
  2233. arch/ia64/kvm/kvm_fw.c +0 −674
  2234. arch/ia64/kvm/kvm_lib.c +0 −21
  2235. arch/ia64/kvm/kvm_minstate.h +0 −266
  2236. arch/ia64/kvm/lapic.h +0 −30
  2237. arch/ia64/kvm/memcpy.S +0 −1
  2238. arch/ia64/kvm/memset.S +0 −1
  2239. arch/ia64/kvm/misc.h +0 −94
  2240. arch/ia64/kvm/mmio.c +0 −336
  2241. arch/ia64/kvm/optvfault.S +0 −1090
  2242. arch/ia64/kvm/process.c +0 −1024
  2243. arch/ia64/kvm/trampoline.S +0 −1038
  2244. arch/ia64/kvm/vcpu.c +0 −2209
  2245. arch/ia64/kvm/vcpu.h +0 −752
  2246. arch/ia64/kvm/vmm.c +0 −99
  2247. arch/ia64/kvm/vmm_ivt.S +0 −1392
  2248. arch/ia64/kvm/vti.h +0 −290
  2249. arch/ia64/kvm/vtlb.c +0 −640
  2250. arch/ia64/sn/kernel/msi_sn.c +6 −6
  2251. arch/ia64/sn/kernel/setup.c +1 −1
  2252. arch/ia64/sn/kernel/sn2/sn2_smp.c +14 −14
  2253. arch/m32r/include/asm/Kbuild +2 −1
  2254. arch/m32r/include/asm/atomic.h +58 −87
  2255. arch/m32r/include/asm/io.h +3 −0
  2256. arch/m32r/include/asm/sections.h +0 −7
  2257. arch/m32r/include/uapi/asm/socket.h +5 −0
  2258. arch/m32r/kernel/time.c +0 −1
  2259. arch/m68k/68000/Makefile +0 −0
  2260. arch/m68k/68000/bootlogo-vz.h +0 −0
  2261. arch/m68k/68000/bootlogo.h +0 −0
  2262. arch/m68k/68000/entry.S +244 −0
  2263. arch/m68k/68000/head.S +0 −0
  2264. arch/m68k/68000/ints.c +0 −0
  2265. arch/m68k/68000/m68328.c +0 −0
  2266. arch/m68k/68000/m68EZ328.c +0 −0
  2267. arch/m68k/68000/m68VZ328.c +0 −0
  2268. arch/m68k/68000/romvec.S +0 −0
  2269. arch/m68k/68000/timers.c +0 −0
  2270. arch/m68k/68360/Makefile +12 −0
  2271. arch/m68k/68360/commproc.c +0 −0
  2272. arch/m68k/68360/config.c +1 −1
  2273. arch/m68k/68360/entry.S +164 −0
  2274. arch/m68k/68360/head-ram.S +2 −3
  2275. arch/m68k/68360/head-rom.S +2 −3
  2276. arch/m68k/68360/ints.c +1 −1
  2277. arch/m68k/Kconfig.devices +2 −2
  2278. arch/m68k/Makefile +6 −6
  2279. arch/m68k/atari/config.c +27 −0
  2280. arch/m68k/atari/stdma.c +40 −21
  2281. arch/m68k/atari/stram.c +1 −0
  2282. arch/m68k/coldfire/Makefile +0 −0
  2283. arch/m68k/coldfire/cache.c +0 −0
  2284. arch/m68k/coldfire/clk.c +0 −0
  2285. arch/m68k/coldfire/device.c +0 −0
  2286. arch/m68k/coldfire/dma.c +0 −0
  2287. arch/m68k/coldfire/dma_timer.c +0 −0
  2288. arch/m68k/coldfire/entry.S +203 −0
  2289. arch/m68k/coldfire/firebee.c +0 −0
  2290. arch/m68k/coldfire/gpio.c +0 −0
  2291. arch/m68k/coldfire/head.S +0 −0
  2292. arch/m68k/coldfire/intc-2.c +0 −0
  2293. arch/m68k/coldfire/intc-5249.c +0 −0
  2294. arch/m68k/coldfire/intc-525x.c +0 −0
  2295. arch/m68k/coldfire/intc-5272.c +1 −1
  2296. arch/m68k/coldfire/intc-simr.c +0 −0
  2297. arch/m68k/coldfire/intc.c +0 −0
  2298. arch/m68k/coldfire/m5206.c +1 −1
  2299. arch/m68k/coldfire/m520x.c +1 −1
  2300. arch/m68k/coldfire/m523x.c +1 −1
  2301. arch/m68k/coldfire/m5249.c +1 −1
  2302. arch/m68k/coldfire/m525x.c +1 −1
  2303. arch/m68k/coldfire/m5272.c +1 −1
  2304. arch/m68k/coldfire/m527x.c +2 −2
  2305. arch/m68k/coldfire/m528x.c +1 −1
  2306. arch/m68k/coldfire/m5307.c +1 −1
  2307. arch/m68k/coldfire/m53xx.c +0 −0
  2308. arch/m68k/coldfire/m5407.c +1 −1
  2309. arch/m68k/coldfire/m5441x.c +0 −0
  2310. arch/m68k/coldfire/m54xx.c +1 −2
  2311. arch/m68k/coldfire/mcf8390.c +0 −0
  2312. arch/m68k/coldfire/nettel.c +0 −0
  2313. arch/m68k/coldfire/pci.c +0 −0
  2314. arch/m68k/coldfire/pit.c +0 −0
  2315. arch/m68k/coldfire/reset.c +0 −0
  2316. arch/m68k/coldfire/sltimers.c +0 −0
  2317. arch/m68k/coldfire/timers.c +0 −0
  2318. arch/m68k/coldfire/vectors.c +1 −1
  2319. arch/m68k/include/asm/Kbuild +1 −1
  2320. arch/m68k/include/asm/atari_stdma.h +2 −2
  2321. arch/m68k/include/asm/atomic.h +48 −63
  2322. arch/m68k/include/asm/io.h +8 −0
  2323. arch/m68k/include/asm/io_mm.h +8 −1
  2324. arch/m68k/include/asm/io_no.h +9 −4
  2325. arch/m68k/include/asm/m54xxpci.h +1 −1
  2326. arch/m68k/include/asm/macintosh.h +4 −0
  2327. arch/m68k/include/asm/unistd.h +1 −1
  2328. arch/m68k/include/uapi/asm/unistd.h +1 −0
  2329. arch/m68k/kernel/sys_m68k.c +13 −8
  2330. arch/m68k/kernel/syscalltable.S +1 −0
  2331. arch/m68k/mac/config.c +132 −14
  2332. arch/m68k/mm/hwtest.c +43 −35
  2333. arch/m68k/mm/init.c +0 −1
  2334. arch/m68k/platform/68000/entry.S +0 −244
  2335. arch/m68k/platform/68360/Makefile +0 −12
  2336. arch/m68k/platform/68360/entry.S +0 −164
  2337. arch/m68k/platform/Makefile +0 −3
  2338. arch/m68k/platform/coldfire/entry.S +0 −203
  2339. arch/m68k/sun3/config.c +60 −0
  2340. arch/metag/include/asm/Kbuild +1 −1
  2341. arch/metag/include/asm/atomic_lnkget.h +46 −75
  2342. arch/metag/include/asm/atomic_lock1.h +31 −45
  2343. arch/metag/include/asm/barrier.h +10 −9
  2344. arch/metag/kernel/perf/perf_event.c +7 −7
  2345. arch/microblaze/Kconfig +5 −0
  2346. arch/microblaze/include/asm/Kbuild +1 −1
  2347. arch/microblaze/include/asm/io.h +0 −8
  2348. arch/microblaze/include/asm/pgtable.h +1 −0
  2349. arch/microblaze/include/asm/syscall.h +5 −0
  2350. arch/microblaze/include/asm/tlb.h +2 −1
  2351. arch/microblaze/include/asm/unistd.h +1 −1
  2352. arch/microblaze/include/uapi/asm/unistd.h +1 −0
  2353. arch/microblaze/kernel/dma.c +27 −0
  2354. arch/microblaze/kernel/ptrace.c +1 −2
  2355. arch/microblaze/kernel/syscall_table.S +1 −0
  2356. arch/microblaze/mm/consistent.c +20 −5
  2357. arch/microblaze/pci/pci-common.c +7 −2
  2358. arch/mips/Kbuild.platforms +2 −0
  2359. arch/mips/Kconfig +81 −38
  2360. arch/mips/Kconfig.debug +13 −0
  2361. arch/mips/Makefile +21 −0
  2362. arch/mips/alchemy/common/clock.c +8 −9
  2363. arch/mips/alchemy/common/setup.c +3 −3
  2364. arch/mips/alchemy/devboards/db1300.c +46 −1
  2365. arch/mips/alchemy/devboards/db1550.c +4 −5
  2366. arch/mips/alchemy/devboards/platform.c +3 −0
  2367. arch/mips/ar7/platform.c +12 −12
  2368. arch/mips/ath25/Kconfig +16 −0
  2369. arch/mips/ath25/Makefile +16 −0
  2370. arch/mips/ath25/Platform +6 −0
  2371. arch/mips/ath25/ar2315.c +364 −0
  2372. arch/mips/ath25/ar2315.h +22 −0
  2373. arch/mips/ath25/ar2315_regs.h +410 −0
  2374. arch/mips/ath25/ar5312.c +393 −0
  2375. arch/mips/ath25/ar5312.h +22 −0
  2376. arch/mips/ath25/ar5312_regs.h +224 −0
  2377. arch/mips/ath25/board.c +234 −0
  2378. arch/mips/ath25/devices.c +125 −0
  2379. arch/mips/ath25/devices.h +43 −0
  2380. arch/mips/ath25/early_printk.c +44 −0
  2381. arch/mips/ath25/prom.c +26 −0
  2382. arch/mips/ath79/irq.c +0 −1
  2383. arch/mips/ath79/mach-db120.c +1 −1
  2384. arch/mips/ath79/prom.c +10 −28
  2385. arch/mips/ath79/setup.c +5 −0
  2386. arch/mips/bcm3384/Makefile +1 −0
  2387. arch/mips/bcm3384/Platform +7 −0
  2388. arch/mips/bcm3384/dma.c +81 −0
  2389. arch/mips/bcm3384/irq.c +193 −0
  2390. arch/mips/bcm3384/setup.c +97 −0
  2391. arch/mips/bcm47xx/bcm47xx_private.h +6 −0
  2392. arch/mips/bcm47xx/irq.c +8 −0
  2393. arch/mips/bcm47xx/nvram.c +86 −69
  2394. arch/mips/bcm47xx/setup.c +30 −59
  2395. arch/mips/bcm47xx/sprom.c +82 −0
  2396. arch/mips/bcm63xx/cpu.c +1 −1
  2397. arch/mips/boot/.gitignore +1 −0
  2398. arch/mips/boot/dts/Makefile +21 −0
  2399. arch/mips/boot/dts/bcm3384.dtsi +109 −0
  2400. arch/mips/boot/dts/bcm93384wvg.dts +32 −0
  2401. arch/mips/boot/dts/danube.dtsi +0 −0
  2402. arch/mips/boot/dts/easy50712.dts +0 −0
  2403. arch/mips/boot/dts/mt7620a.dtsi +0 −0
  2404. arch/mips/boot/dts/mt7620a_eval.dts +0 −0
  2405. arch/mips/boot/dts/octeon_3xxx.dts +0 −0
  2406. arch/mips/boot/dts/octeon_68xx.dts +0 −0
  2407. arch/mips/boot/dts/rt2880.dtsi +0 −0
  2408. arch/mips/boot/dts/rt2880_eval.dts +0 −0
  2409. arch/mips/boot/dts/rt3050.dtsi +0 −0
  2410. arch/mips/boot/dts/rt3052_eval.dts +0 −0
  2411. arch/mips/boot/dts/rt3883.dtsi +0 −0
  2412. arch/mips/boot/dts/rt3883_eval.dts +0 −0
  2413. arch/mips/boot/dts/sead3.dts +0 −0
  2414. arch/mips/boot/dts/xlp_evp.dts +0 −0
  2415. arch/mips/boot/dts/xlp_fvp.dts +0 −0
  2416. arch/mips/boot/dts/xlp_gvp.dts +0 −0
  2417. arch/mips/boot/dts/xlp_svp.dts +0 −0
  2418. arch/mips/cavium-octeon/.gitignore +0 −2
  2419. arch/mips/cavium-octeon/Kconfig +1 −1
  2420. arch/mips/cavium-octeon/Makefile +0 −10
  2421. arch/mips/cavium-octeon/dma-octeon.c +2 −2
  2422. arch/mips/cavium-octeon/executive/octeon-model.c +35 −14
  2423. arch/mips/cavium-octeon/octeon-irq.c +17 −15
  2424. arch/mips/cavium-octeon/octeon-platform.c +272 −2
  2425. arch/mips/cavium-octeon/setup.c +2 −11
  2426. arch/mips/configs/bcm3384_defconfig +78 −0
  2427. arch/mips/configs/cavium_octeon_defconfig +3 −0
  2428. arch/mips/configs/db1xxx_defconfig +1 −1
  2429. arch/mips/configs/lemote2f_defconfig +0 −1
  2430. arch/mips/configs/loongson3_defconfig +1 −1
  2431. arch/mips/configs/nlm_xlp_defconfig +1 −1
  2432. arch/mips/configs/nlm_xlr_defconfig +1 −1
  2433. arch/mips/configs/sead3_defconfig +1 −1
  2434. arch/mips/configs/sead3micro_defconfig +1 −1
  2435. arch/mips/fw/lib/cmdline.c +4 −4
  2436. arch/mips/include/asm/Kbuild +2 −1
  2437. arch/mips/include/asm/asmmacro-32.h +6 −0
  2438. arch/mips/include/asm/asmmacro.h +18 −0
  2439. arch/mips/include/asm/atomic.h +202 −375
  2440. arch/mips/include/asm/barrier.h +5 −56
  2441. arch/mips/include/asm/bitops.h +18 −17
  2442. arch/mips/include/asm/bmips.h +1 −0
  2443. arch/mips/include/asm/bootinfo.h +5 −8
  2444. arch/mips/include/asm/clock.h +0 −3
  2445. arch/mips/include/asm/cmpxchg.h +15 −12
  2446. arch/mips/include/asm/compiler.h +8 −0
  2447. arch/mips/include/asm/cop2.h +4 −4
  2448. arch/mips/include/asm/cpu-features.h +14 −0
  2449. arch/mips/include/asm/cpu-info.h +5 −0
  2450. arch/mips/include/asm/cpu.h +2 −0
  2451. arch/mips/include/asm/edac.h +4 −2
  2452. arch/mips/include/asm/elf.h +59 −15
  2453. arch/mips/include/asm/fpregdef.h +14 −0
  2454. arch/mips/include/asm/fpu.h +43 −10
  2455. arch/mips/include/asm/fpu_emulator.h +12 −12
  2456. arch/mips/include/asm/ftrace.h +2 −2
  2457. arch/mips/include/asm/futex.h +19 −8
  2458. arch/mips/include/asm/gic.h +0 −384
  2459. arch/mips/include/asm/hpet.h +73 −0
  2460. arch/mips/include/asm/idle.h +0 −8
  2461. arch/mips/include/asm/io.h +4 −4
  2462. arch/mips/include/asm/irq.h +3 −0
  2463. arch/mips/include/asm/irq_cpu.h +2 −2
  2464. arch/mips/include/asm/jump_label.h +7 −1
  2465. arch/mips/include/asm/kvm_host.h +11 −5
  2466. arch/mips/include/asm/mach-ath25/ath25_platform.h +73 −0
  2467. arch/mips/include/asm/mach-ath25/cpu-feature-overrides.h +64 −0
  2468. arch/mips/include/asm/mach-ath25/dma-coherence.h +82 −0
  2469. arch/mips/include/asm/mach-ath25/gpio.h +16 −0
  2470. arch/mips/include/asm/mach-ath25/war.h +25 −0
  2471. arch/mips/include/asm/mach-au1x00/cpu-feature-overrides.h +12 −0
  2472. arch/mips/include/asm/mach-au1x00/ioremap.h +5 −5
  2473. arch/mips/include/asm/mach-bcm3384/dma-coherence.h +48 −0
  2474. arch/mips/include/asm/mach-bcm3384/war.h +24 −0
  2475. arch/mips/include/asm/mach-bcm47xx/bcm47xx_nvram.h +2 −34
  2476. arch/mips/include/asm/mach-bcm63xx/ioremap.h +3 −3
  2477. arch/mips/include/asm/mach-cavium-octeon/cpu-feature-overrides.h +1 −0
  2478. arch/mips/include/asm/mach-generic/ioremap.h +2 −2
  2479. arch/mips/include/asm/mach-generic/irq.h +6 −0
  2480. arch/mips/include/asm/mach-lantiq/lantiq.h +2 −0
  2481. arch/mips/include/asm/mach-loongson/boot_param.h +46 −3
  2482. arch/mips/include/asm/mach-loongson/cpu-feature-overrides.h +2 −2
  2483. arch/mips/include/asm/mach-loongson/dma-coherence.h +3 −3
  2484. arch/mips/include/asm/mach-loongson/irq.h +1 −2
  2485. arch/mips/include/asm/mach-loongson/loongson.h +1 −1
  2486. arch/mips/include/asm/mach-loongson/loongson_hwmon.h +55 −0
  2487. arch/mips/include/asm/mach-loongson/machine.h +1 −1
  2488. arch/mips/include/asm/mach-loongson/topology.h +1 −1
  2489. arch/mips/include/asm/mach-loongson/workarounds.h +7 −0
  2490. arch/mips/include/asm/mach-loongson1/cpufreq.h +23 −0
  2491. arch/mips/include/asm/mach-loongson1/loongson1.h +7 −1
  2492. arch/mips/include/asm/mach-loongson1/platform.h +6 −4
  2493. arch/mips/include/asm/mach-loongson1/regs-clk.h +20 −3
  2494. arch/mips/include/asm/mach-loongson1/regs-mux.h +67 −0
  2495. arch/mips/include/asm/mach-loongson1/regs-pwm.h +29 −0
  2496. arch/mips/include/asm/mach-loongson1/regs-wdt.h +4 −7
  2497. arch/mips/include/asm/mach-malta/irq.h +0 −1
  2498. arch/mips/include/asm/mach-pmcs-msp71xx/msp_regops.h +13 −12
  2499. arch/mips/include/asm/mach-ralink/mt7620.h +48 −16
  2500. arch/mips/include/asm/mach-ralink/pinmux.h +55 −0
  2501. arch/mips/include/asm/mach-ralink/ralink_regs.h +7 −0
  2502. arch/mips/include/asm/mach-ralink/rt305x.h +20 −15
  2503. arch/mips/include/asm/mach-ralink/rt3883.h +9 −7
  2504. arch/mips/include/asm/mach-sead3/irq.h +0 −1
  2505. arch/mips/include/asm/mach-tx39xx/ioremap.h +2 −2
  2506. arch/mips/include/asm/mach-tx49xx/ioremap.h +2 −2
  2507. arch/mips/include/asm/mips-boards/maltaint.h +8 −16
  2508. arch/mips/include/asm/mips-boards/sead3int.h +14 −1
  2509. arch/mips/include/asm/mips-cm.h +1 −1
  2510. arch/mips/include/asm/mips-cpc.h +2 −2
  2511. arch/mips/include/asm/mipsregs.h +55 −1
  2512. arch/mips/include/asm/octeon/cvmx-cmd-queue.h +3 −1
  2513. arch/mips/include/asm/octeon/cvmx-pow.h +27 −42
  2514. arch/mips/include/asm/octeon/cvmx.h +0 −63
  2515. arch/mips/include/asm/octeon/octeon-feature.h +0 −52
  2516. arch/mips/include/asm/octeon/octeon-model.h +1 −2
  2517. arch/mips/include/asm/paccess.h +2 −0
  2518. arch/mips/include/asm/page.h +1 −1
  2519. arch/mips/include/asm/pci.h +1 −1
  2520. arch/mips/include/asm/pgtable-32.h +53 −51
  2521. arch/mips/include/asm/pgtable-bits.h +48 −32
  2522. arch/mips/include/asm/pgtable.h +19 −9
  2523. arch/mips/include/asm/processor.h +0 −6
  2524. arch/mips/include/asm/prom.h +1 −0
  2525. arch/mips/include/asm/r4kcache.h +4 −59
  2526. arch/mips/include/asm/spinlock.h +26 −24
  2527. arch/mips/include/asm/suspend.h +0 −7
  2528. arch/mips/include/asm/syscall.h +1 −1
  2529. arch/mips/include/asm/thread_info.h +2 −0
  2530. arch/mips/include/asm/time.h +2 −4
  2531. arch/mips/include/asm/types.h +1 −17
  2532. arch/mips/include/asm/uaccess.h +10 −35
  2533. arch/mips/include/asm/uasm.h +2 −0
  2534. arch/mips/include/uapi/asm/inst.h +4 −3
  2535. arch/mips/include/uapi/asm/ioctls.h +2 −0
  2536. arch/mips/include/uapi/asm/ptrace.h +2 −0
  2537. arch/mips/include/uapi/asm/siginfo.h +4 −0
  2538. arch/mips/include/uapi/asm/socket.h +5 −0
  2539. arch/mips/include/uapi/asm/swab.h +14 −4
  2540. arch/mips/include/uapi/asm/unistd.h +9 −6
  2541. arch/mips/jz4740/setup.c +1 −1
  2542. arch/mips/kernel/Makefile +4 −6
  2543. arch/mips/kernel/bmips_vec.S +0 −3
  2544. arch/mips/kernel/branch.c +2 −6
  2545. arch/mips/kernel/cevt-gic.c +0 −105
  2546. arch/mips/kernel/cevt-r4k.c +3 −3
  2547. arch/mips/kernel/cps-vec.S +2 −0
  2548. arch/mips/kernel/cpu-probe.c +124 −6
  2549. arch/mips/kernel/crash_dump.c +2 −2
  2550. arch/mips/kernel/csrc-gic.c +0 −40
  2551. arch/mips/kernel/elf.c +191 −0
  2552. arch/mips/kernel/genex.S +1 −0
  2553. arch/mips/kernel/i8259.c +19 −5
  2554. arch/mips/kernel/idle.c +0 −3
  2555. arch/mips/kernel/irq-gic.c +0 −402
  2556. arch/mips/kernel/irq_cpu.c +28 −20
  2557. arch/mips/kernel/jump_label.c +32 −10
  2558. arch/mips/kernel/kprobes.c +3 −3
  2559. arch/mips/kernel/mips-cm.c +6 −6
  2560. arch/mips/kernel/mips-cpc.c +2 −2
  2561. arch/mips/kernel/mips_ksyms.c +0 −4
  2562. arch/mips/kernel/perf_event_mipsxx.c +17 −27
  2563. arch/mips/kernel/process.c +36 −18
  2564. arch/mips/kernel/prom.c +18 −0
  2565. arch/mips/kernel/ptrace.c +2 −4
  2566. arch/mips/kernel/r2300_fpu.S +6 −0
  2567. arch/mips/kernel/r2300_switch.S +5 −0
  2568. arch/mips/kernel/r4k_fpu.S +25 −2
  2569. arch/mips/kernel/r4k_switch.S +14 −1
  2570. arch/mips/kernel/r6000_fpu.S +5 −0
  2571. arch/mips/kernel/rtlx.c +2 −2
  2572. arch/mips/kernel/scall32-o32.S +1 −0
  2573. arch/mips/kernel/scall64-64.S +1 −0
  2574. arch/mips/kernel/scall64-n32.S +1 −0
  2575. arch/mips/kernel/scall64-o32.S +1 −0
  2576. arch/mips/kernel/setup.c +18 −8
  2577. arch/mips/kernel/signal.c +5 −5
  2578. arch/mips/kernel/smp-bmips.c +74 −42
  2579. arch/mips/kernel/smp-cmp.c +1 −1
  2580. arch/mips/kernel/smp-cps.c +3 −3
  2581. arch/mips/kernel/smp-gic.c +1 −1
  2582. arch/mips/kernel/smp-mt.c +3 −3
  2583. arch/mips/kernel/syscall.c +2 −0
  2584. arch/mips/kernel/traps.c +60 −6
  2585. arch/mips/kernel/vdso.c +14 −1
  2586. arch/mips/kvm/mips.c +1 −39
  2587. arch/mips/lantiq/Kconfig +1 −0
  2588. arch/mips/lantiq/Makefile +0 −2
  2589. arch/mips/lantiq/dts/Makefile +0 −1
  2590. arch/mips/lantiq/falcon/sysctrl.c +7 −6
  2591. arch/mips/lantiq/irq.c +31 −25
  2592. arch/mips/lantiq/prom.c +8 −10
  2593. arch/mips/lantiq/xway/Makefile +2 −0
  2594. arch/mips/lantiq/xway/dcdc.c +0 −1
  2595. arch/mips/lantiq/xway/dma.c +0 −1
  2596. arch/mips/lantiq/xway/gptu.c +0 −1
  2597. arch/mips/lantiq/xway/reset.c +69 −1
  2598. arch/mips/lantiq/xway/sysctrl.c +1 −1
  2599. arch/mips/lantiq/xway/vmmc.c +69 −0
  2600. arch/mips/lantiq/xway/xrx200_phy_fw.c +22 −2
  2601. arch/mips/lasat/Kconfig +1 −1
  2602. arch/mips/lib/csum_partial.S +8 −2
  2603. arch/mips/lib/iomap.c +9 −9
  2604. arch/mips/lib/memcpy.S +1 −0
  2605. arch/mips/lib/memset.S +2 −4
  2606. arch/mips/lib/mips-atomic.c +0 −20
  2607. arch/mips/lib/r3k_dump_tlb.c +6 −5
  2608. arch/mips/lib/strlen_user.S +0 −3
  2609. arch/mips/lib/strnlen_user.S +4 −2
  2610. arch/mips/loongson/Kconfig +17 −0
  2611. arch/mips/loongson/common/Makefile +2 −1
  2612. arch/mips/loongson/common/cs5536/cs5536_pci.c +13 −12
  2613. arch/mips/loongson/common/dma-swiotlb.c +14 −0
  2614. arch/mips/loongson/common/early_printk.c +1 −1
  2615. arch/mips/loongson/common/env.c +26 −2
  2616. arch/mips/loongson/common/gpio.c +1 −1
  2617. arch/mips/loongson/common/init.c +1 −0
  2618. arch/mips/loongson/common/machtype.c +10 −13
  2619. arch/mips/loongson/common/rtc.c +1 −1
  2620. arch/mips/loongson/common/serial.c +49 −17
  2621. arch/mips/loongson/common/setup.c +1 −0
  2622. arch/mips/loongson/common/time.c +5 −0
  2623. arch/mips/loongson/common/uart_base.c +14 −16
  2624. arch/mips/loongson/lemote-2f/clock.c +3 −2
  2625. arch/mips/loongson/lemote-2f/irq.c +2 −2
  2626. arch/mips/loongson/lemote-2f/reset.c +1 −1
  2627. arch/mips/loongson/loongson-3/Makefile +3 −1
  2628. arch/mips/loongson/loongson-3/hpet.c +257 −0
  2629. arch/mips/loongson/loongson-3/irq.c +9 −7
  2630. arch/mips/loongson/loongson-3/numa.c +10 −3
  2631. arch/mips/loongson/loongson-3/platform.c +43 −0
  2632. arch/mips/loongson/loongson-3/smp.c +48 −28
  2633. arch/mips/loongson1/Kconfig +40 −2
  2634. arch/mips/loongson1/common/Makefile +1 −1
  2635. arch/mips/loongson1/common/clock.c +0 −28
  2636. arch/mips/loongson1/common/platform.c +123 −18
  2637. arch/mips/loongson1/common/prom.c +13 −17
  2638. arch/mips/loongson1/common/reset.c +14 −6
  2639. arch/mips/loongson1/common/time.c +226 −0
  2640. arch/mips/loongson1/ls1b/board.c +7 −5
  2641. arch/mips/math-emu/cp1emu.c +10 −9
  2642. arch/mips/math-emu/ieee754dp.c +1 −1
  2643. arch/mips/math-emu/ieee754sp.c +1 −1
  2644. arch/mips/mm/Makefile +7 −3
  2645. arch/mips/mm/c-r4k.c +43 −0
  2646. arch/mips/mm/dma-default.c +30 −12
  2647. arch/mips/mm/gup.c +2 −2
  2648. arch/mips/mm/init.c +1 −1
  2649. arch/mips/mm/ioremap.c +9 −9
  2650. arch/mips/mm/sc-r5k.c +1 −1
  2651. arch/mips/mm/tlb-r4k.c +5 −1
  2652. arch/mips/mm/tlbex.c +23 −11
  2653. arch/mips/mm/uasm-mips.c +2 −0
  2654. arch/mips/mm/uasm.c +8 −6
  2655. arch/mips/mti-malta/Makefile +2 −1
  2656. arch/mips/mti-malta/malta-init.c +1 −1
  2657. arch/mips/mti-malta/malta-int.c +40 −287
  2658. arch/mips/mti-malta/malta-time.c +19 −32
  2659. arch/mips/mti-sead3/Makefile +0 −5
  2660. arch/mips/mti-sead3/leds-sead3.c +0 −1
  2661. arch/mips/mti-sead3/sead3-ehci.c +7 −1
  2662. arch/mips/mti-sead3/sead3-i2c-drv.c +0 −1
  2663. arch/mips/mti-sead3/sead3-i2c.c +1 −7
  2664. arch/mips/mti-sead3/sead3-int.c +8 −123
  2665. arch/mips/mti-sead3/sead3-leds.c +2 −6
  2666. arch/mips/mti-sead3/sead3-net.c +10 −4
  2667. arch/mips/mti-sead3/sead3-pic32-bus.c +0 −102
  2668. arch/mips/mti-sead3/sead3-pic32-i2c-drv.c +0 −423
  2669. arch/mips/mti-sead3/sead3-platform.c +14 −4
  2670. arch/mips/mti-sead3/sead3-serial.c +0 −45
  2671. arch/mips/mti-sead3/sead3-time.c +10 −25
  2672. arch/mips/net/bpf_jit.c +26 −64
  2673. arch/mips/netlogic/Kconfig +4 −0
  2674. arch/mips/netlogic/Makefile +0 −1
  2675. arch/mips/netlogic/dts/Makefile +0 −4
  2676. arch/mips/netlogic/xlp/Makefile +8 −4
  2677. arch/mips/oprofile/Makefile +1 −0
  2678. arch/mips/oprofile/backtrace.c +4 −3
  2679. arch/mips/oprofile/common.c +10 −1
  2680. arch/mips/oprofile/op_model_loongson3.c +220 −0
  2681. arch/mips/oprofile/op_model_mipsxx.c +14 −4
  2682. arch/mips/pci/Makefile +2 −0
  2683. arch/mips/pci/msi-octeon.c +3 −5
  2684. arch/mips/pci/msi-xlp.c +7 −9
  2685. arch/mips/pci/ops-bcm63xx.c +1 −1
  2686. arch/mips/pci/ops-nile4.c +1 −11
  2687. arch/mips/pci/ops-pmcmsp.c +0 −12
  2688. arch/mips/pci/pci-alchemy.c +0 −1
  2689. arch/mips/pci/pci-ar2315.c +511 −0
  2690. arch/mips/pci/pci-ar71xx.c +0 −14
  2691. arch/mips/pci/pci-ar724x.c +0 −24
  2692. arch/mips/pci/pci-lantiq.c +1 −7
  2693. arch/mips/pci/pci-octeon.c +1 −1
  2694. arch/mips/pci/pci-rt2880.c +285 −0
  2695. arch/mips/pci/pci-rt3883.c +0 −10
  2696. arch/mips/pci/pci-tx4939.c +1 −1
  2697. arch/mips/pci/pci-xlr.c +1 −1
  2698. arch/mips/pmcs-msp71xx/msp_irq.c +1 −0
  2699. arch/mips/pmcs-msp71xx/msp_irq_cic.c +2 −2
  2700. arch/mips/pmcs-msp71xx/msp_prom.c +1 −1
  2701. arch/mips/power/cpu.c +1 −1
  2702. arch/mips/ralink/Kconfig +6 −1
  2703. arch/mips/ralink/Makefile +3 −1
  2704. arch/mips/ralink/bootrom.c +48 −0
  2705. arch/mips/ralink/clk.c +6 −0
  2706. arch/mips/ralink/common.h +0 −19
  2707. arch/mips/ralink/dts/Makefile +0 −4
  2708. arch/mips/ralink/early_printk.c +30 −15
  2709. arch/mips/ralink/ill_acc.c +87 −0
  2710. arch/mips/ralink/irq.c +33 −12
  2711. arch/mips/ralink/mt7620.c +312 −153
  2712. arch/mips/ralink/of.c +19 −13
  2713. arch/mips/ralink/prom.c +1 −0
  2714. arch/mips/ralink/rt288x.c +22 −43
  2715. arch/mips/ralink/rt305x.c +68 −85
  2716. arch/mips/ralink/rt3883.c +42 −132
  2717. arch/mips/ralink/timer.c +1 −2
  2718. arch/mips/rb532/gpio.c +1 −1
  2719. arch/mips/rb532/prom.c +4 −4
  2720. arch/mips/sgi-ip22/ip22-mc.c +2 −4
  2721. arch/mips/sgi-ip22/ip28-berr.c +3 −3
  2722. arch/mips/sgi-ip27/ip27-klnuma.c +2 −3
  2723. arch/mips/sgi-ip27/ip27-memory.c +3 −3
  2724. arch/mips/sibyte/Makefile +1 −0
  2725. arch/mips/sibyte/common/cfe.c +4 −4
  2726. arch/mips/sibyte/swarm/platform.c +1 −1
  2727. arch/mips/sibyte/swarm/rtc_m41t81.c +2 −2
  2728. arch/mips/sibyte/swarm/rtc_xicor1241.c +2 −2
  2729. arch/mips/sibyte/swarm/setup.c +1 −1
  2730. arch/mips/txx9/generic/setup.c +2 −2
  2731. arch/mips/txx9/generic/setup_tx4927.c +2 −2
  2732. arch/mips/txx9/generic/setup_tx4938.c +2 −2
  2733. arch/mips/txx9/generic/setup_tx4939.c +2 −2
  2734. arch/mips/txx9/rbtx4939/setup.c +0 −1
  2735. arch/mn10300/Kconfig +1 −1
  2736. arch/mn10300/include/asm/Kbuild +2 −1
  2737. arch/mn10300/include/asm/atomic.h +42 −83
  2738. arch/mn10300/include/asm/io.h +4 −0
  2739. arch/mn10300/include/asm/sections.h +0 −1
  2740. arch/mn10300/include/uapi/asm/socket.h +5 −0
  2741. arch/nios2/Kconfig +206 −0
  2742. arch/nios2/Kconfig.debug +17 −0
  2743. arch/nios2/Makefile +75 −0
  2744. arch/nios2/boot/Makefile +52 −0
  2745. arch/nios2/boot/dts/3c120_devboard.dts +164 −0
  2746. arch/nios2/boot/install.sh +52 −0
  2747. arch/nios2/boot/linked_dtb.S +19 −0
  2748. arch/nios2/configs/3c120_defconfig +77 −0
  2749. arch/nios2/include/asm/Kbuild +65 −0
  2750. arch/nios2/include/asm/asm-macros.h +309 −0
  2751. arch/nios2/include/asm/asm-offsets.h +20 −0
  2752. arch/nios2/include/asm/cache.h +36 −0
  2753. arch/nios2/include/asm/cacheflush.h +52 −0
  2754. arch/nios2/include/asm/checksum.h +78 −0
  2755. arch/nios2/include/asm/cmpxchg.h +61 −0
  2756. arch/nios2/include/asm/cpuinfo.h +57 −0
  2757. arch/nios2/include/asm/delay.h +21 −0
  2758. arch/nios2/include/asm/dma-mapping.h +140 −0
  2759. arch/nios2/include/asm/elf.h +101 −0
  2760. arch/nios2/include/asm/entry.h +120 −0
  2761. arch/nios2/include/asm/io.h +63 −0
  2762. arch/nios2/include/asm/irq.h +28 −0
  2763. arch/nios2/include/asm/irqflags.h +72 −0
  2764. arch/nios2/include/asm/linkage.h +25 −0
  2765. arch/nios2/include/asm/mmu.h +16 −0
  2766. arch/nios2/include/asm/mmu_context.h +66 −0
  2767. arch/nios2/include/asm/mutex.h +1 −0
  2768. arch/nios2/include/asm/page.h +109 −0
  2769. arch/nios2/include/asm/pgalloc.h +86 −0
  2770. arch/nios2/include/asm/pgtable-bits.h +35 −0
  2771. arch/nios2/include/asm/pgtable.h +310 −0
  2772. arch/nios2/include/asm/processor.h +103 −0
  2773. arch/nios2/include/asm/ptrace.h +33 −0
  2774. arch/nios2/include/asm/registers.h +71 −0
  2775. arch/nios2/include/asm/setup.h +38 −0
  2776. arch/nios2/include/asm/signal.h +22 −0
  2777. arch/nios2/include/asm/string.h +24 −0
  2778. arch/nios2/include/asm/switch_to.h +31 −0
  2779. arch/nios2/include/asm/syscall.h +138 −0
  2780. arch/nios2/include/asm/syscalls.h +25 −0
  2781. arch/nios2/include/asm/thread_info.h +120 −0
  2782. arch/nios2/include/asm/timex.h +24 −0
  2783. arch/nios2/include/asm/tlb.h +34 −0
  2784. arch/nios2/include/asm/tlbflush.h +46 −0
  2785. arch/nios2/include/asm/traps.h +19 −0
  2786. arch/nios2/include/asm/uaccess.h +231 −0
  2787. arch/nios2/include/asm/ucontext.h +32 −0
  2788. arch/nios2/include/uapi/asm/Kbuild +4 −0
  2789. arch/nios2/include/uapi/asm/byteorder.h +22 −0
  2790. arch/nios2/include/uapi/asm/elf.h +67 −0
  2791. arch/nios2/include/uapi/asm/ptrace.h +120 −0
  2792. arch/nios2/include/uapi/asm/sigcontext.h +28 −0
  2793. arch/nios2/include/uapi/asm/signal.h +23 −0
  2794. arch/nios2/include/uapi/asm/swab.h +37 −0
  2795. arch/nios2/include/uapi/asm/unistd.h +25 −0
  2796. arch/nios2/kernel/Makefile +24 −0
  2797. arch/nios2/kernel/asm-offsets.c +87 −0
  2798. arch/nios2/kernel/cpuinfo.c +198 −0
  2799. arch/nios2/kernel/entry.S +539 −0
  2800. arch/nios2/kernel/head.S +175 −0
  2801. arch/nios2/kernel/insnemu.S +592 −0
  2802. arch/nios2/kernel/irq.c +93 −0
  2803. arch/nios2/kernel/misaligned.c +256 −0
  2804. arch/nios2/kernel/module.c +138 −0
  2805. arch/nios2/kernel/nios2_ksyms.c +33 −0
  2806. arch/nios2/kernel/process.c +258 −0
  2807. arch/nios2/kernel/prom.c +65 −0
  2808. arch/nios2/kernel/ptrace.c +166 −0
  2809. arch/nios2/kernel/setup.c +218 −0
  2810. arch/nios2/kernel/signal.c +323 −0
  2811. arch/nios2/kernel/sys_nios2.c +53 −0
  2812. arch/nios2/kernel/syscall_table.c +29 −0
  2813. arch/nios2/kernel/time.c +308 −0
  2814. arch/nios2/kernel/traps.c +185 −0
  2815. arch/nios2/kernel/vmlinux.lds.S +75 −0
  2816. arch/nios2/lib/Makefile +8 −0
  2817. arch/nios2/lib/delay.c +52 −0
  2818. arch/nios2/lib/memcpy.c +202 −0
  2819. arch/nios2/lib/memmove.c +82 −0
  2820. arch/nios2/lib/memset.c +81 −0
  2821. arch/nios2/mm/Makefile +14 −0
  2822. arch/nios2/mm/cacheflush.c +271 −0
  2823. arch/nios2/mm/dma-mapping.c +186 −0
  2824. arch/nios2/mm/extable.c +25 −0
  2825. arch/nios2/mm/fault.c +251 −0
  2826. arch/nios2/mm/init.c +142 −0
  2827. arch/nios2/mm/ioremap.c +187 −0
  2828. arch/nios2/mm/mmu_context.c +116 −0
  2829. arch/nios2/mm/pgtable.c +74 −0
  2830. arch/nios2/mm/tlb.c +275 −0
  2831. arch/nios2/mm/uaccess.c +163 −0
  2832. arch/nios2/platform/Kconfig.platform +129 −0
  2833. arch/nios2/platform/Makefile +1 −0
  2834. arch/nios2/platform/platform.c +46 −0
  2835. arch/openrisc/Kconfig +1 −0
  2836. arch/openrisc/include/asm/Kbuild +1 −1
  2837. arch/openrisc/include/asm/irq.h +0 −1
  2838. arch/openrisc/include/asm/syscall.h +5 −0
  2839. arch/openrisc/include/uapi/asm/elf.h +1 −2
  2840. arch/openrisc/kernel/irq.c +0 −12
  2841. arch/openrisc/kernel/ptrace.c +1 −2
  2842. arch/parisc/hpux/fs.c +4 −3
  2843. arch/parisc/include/asm/Kbuild +1 −1
  2844. arch/parisc/include/asm/atomic.h +71 −46
  2845. arch/parisc/include/asm/io.h +8 −4
  2846. arch/parisc/include/asm/ldcw.h +10 −3
  2847. arch/parisc/include/asm/syscall.h +11 −0
  2848. arch/parisc/include/asm/uaccess.h +8 −11
  2849. arch/parisc/include/uapi/asm/bitsperlong.h +1 −7
  2850. arch/parisc/include/uapi/asm/ioctls.h +2 −0
  2851. arch/parisc/include/uapi/asm/msgbuf.h +5 −3
  2852. arch/parisc/include/uapi/asm/sembuf.h +4 −2
  2853. arch/parisc/include/uapi/asm/shmbuf.h +15 −20
  2854. arch/parisc/include/uapi/asm/signal.h +7 −11
  2855. arch/parisc/include/uapi/asm/socket.h +5 −0
  2856. arch/parisc/include/uapi/asm/unistd.h +2 −1
  2857. arch/parisc/kernel/ptrace.c +3 −6
  2858. arch/parisc/kernel/syscall_table.S +5 −4
  2859. arch/parisc/lib/fixup.S +2 −2
  2860. arch/powerpc/Kconfig +15 −2
  2861. arch/powerpc/Makefile +1 −0
  2862. arch/powerpc/boot/Makefile +5 −0
  2863. arch/powerpc/boot/dts/b4860emu.dts +2 −2
  2864. arch/powerpc/boot/dts/b4qds.dtsi +23 −0
  2865. arch/powerpc/boot/dts/bsc9131rdb.dtsi +0 −50
  2866. arch/powerpc/boot/dts/fsl/b4420si-post.dtsi +2 −26
  2867. arch/powerpc/boot/dts/fsl/b4860si-post.dtsi +2 −26
  2868. arch/powerpc/boot/dts/fsl/p2041si-post.dtsi +2 −46
  2869. arch/powerpc/boot/dts/fsl/p3041si-post.dtsi +2 −46
  2870. arch/powerpc/boot/dts/fsl/p4080si-post.dtsi +2 −46
  2871. arch/powerpc/boot/dts/fsl/p5020si-post.dtsi +2 −46
  2872. arch/powerpc/boot/dts/fsl/p5040si-post.dtsi +2 −46
  2873. arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi +85 −0
  2874. arch/powerpc/boot/dts/fsl/qoriq-clockgen2.dtsi +68 −0
  2875. arch/powerpc/boot/dts/fsl/t1040si-post.dtsi +2 −28
  2876. arch/powerpc/boot/dts/fsl/t2081si-post.dtsi +4 −29
  2877. arch/powerpc/boot/dts/fsl/t4240si-post.dtsi +4 −29
  2878. arch/powerpc/boot/dts/p3041ds.dts +20 −0
  2879. arch/powerpc/boot/dts/p5020ds.dts +20 −0
  2880. arch/powerpc/boot/dts/p5040ds.dts +20 −0
  2881. arch/powerpc/boot/dts/t1040rdb.dts +48 −0
  2882. arch/powerpc/boot/dts/t1042rdb.dts +48 −0
  2883. arch/powerpc/boot/dts/t1042rdb_pi.dts +57 −0
  2884. arch/powerpc/boot/dts/t104xrdb.dtsi +163 −0
  2885. arch/powerpc/boot/dts/t208xqds.dtsi +11 −0
  2886. arch/powerpc/boot/dts/t4240emu.dts +2 −2
  2887. arch/powerpc/boot/main.c +13 −2
  2888. arch/powerpc/boot/ops.h +1 −1
  2889. arch/powerpc/boot/serial.c +3 −3
  2890. arch/powerpc/boot/simpleboot.c +1 −1
  2891. arch/powerpc/configs/85xx/ge_imp3a_defconfig +0 −1
  2892. arch/powerpc/configs/86xx/gef_ppc9a_defconfig +0 −1
  2893. arch/powerpc/configs/86xx/gef_sbc310_defconfig +0 −1
  2894. arch/powerpc/configs/86xx/gef_sbc610_defconfig +0 −1
  2895. arch/powerpc/configs/86xx/sbc8641d_defconfig +0 −1
  2896. arch/powerpc/configs/c2k_defconfig +0 −1
  2897. arch/powerpc/configs/cell_defconfig +1 −0
  2898. arch/powerpc/configs/celleb_defconfig +1 −0
  2899. arch/powerpc/configs/corenet32_smp_defconfig +3 −0
  2900. arch/powerpc/configs/corenet64_smp_defconfig +11 −36
  2901. arch/powerpc/configs/g5_defconfig +1 −0
  2902. arch/powerpc/configs/maple_defconfig +1 −0
  2903. arch/powerpc/configs/mpc85xx_defconfig +4 −1
  2904. arch/powerpc/configs/mpc85xx_smp_defconfig +4 −1
  2905. arch/powerpc/configs/mpc86xx_defconfig +3 −0
  2906. arch/powerpc/configs/pasemi_defconfig +1 −0
  2907. arch/powerpc/configs/ppc64_defconfig +1 −1
  2908. arch/powerpc/configs/ppc64e_defconfig +0 −1
  2909. arch/powerpc/configs/ppc6xx_defconfig +0 −1
  2910. arch/powerpc/configs/ps3_defconfig +1 −1
  2911. arch/powerpc/configs/pseries_defconfig +0 −1
  2912. arch/powerpc/configs/pseries_le_defconfig +6 −2
  2913. arch/powerpc/crypto/sha1.c +2 −2
  2914. arch/powerpc/include/asm/Kbuild +1 −1
  2915. arch/powerpc/include/asm/atomic.h +77 −121
  2916. arch/powerpc/include/asm/barrier.h +11 −8
  2917. arch/powerpc/include/asm/bitops.h +3 −3
  2918. arch/powerpc/include/asm/bug.h +0 −1
  2919. arch/powerpc/include/asm/copro.h +29 −0
  2920. arch/powerpc/include/asm/cpuidle.h +20 −0
  2921. arch/powerpc/include/asm/cputable.h +3 −7
  2922. arch/powerpc/include/asm/cputime.h +5 −3
  2923. arch/powerpc/include/asm/dma-mapping.h +1 −0
  2924. arch/powerpc/include/asm/eeh.h +28 −16
  2925. arch/powerpc/include/asm/elf.h +1 −2
  2926. arch/powerpc/include/asm/fadump.h +26 −26
  2927. arch/powerpc/include/asm/fsl_guts.h +4 −1
  2928. arch/powerpc/include/asm/hardirq.h +6 −1
  2929. arch/powerpc/include/asm/hugetlb.h +5 −5
  2930. arch/powerpc/include/asm/hydra.h +0 −1
  2931. arch/powerpc/include/asm/io.h +8 −7
  2932. arch/powerpc/include/asm/iommu.h +10 −7
  2933. arch/powerpc/include/asm/irq.h +0 −5
  2934. arch/powerpc/include/asm/kexec.h +10 −1
  2935. arch/powerpc/include/asm/kvm_asm.h +10 −10
  2936. arch/powerpc/include/asm/kvm_book3s.h +0 −2
  2937. arch/powerpc/include/asm/kvm_book3s_64.h +1 −2
  2938. arch/powerpc/include/asm/kvm_booke.h +4 −3
  2939. arch/powerpc/include/asm/kvm_host.h +19 −23
  2940. arch/powerpc/include/asm/kvm_ppc.h +11 −4
  2941. arch/powerpc/include/asm/machdep.h +2 −21
  2942. arch/powerpc/include/asm/mmu-8xx.h +2 −0
  2943. arch/powerpc/include/asm/mmu-hash64.h +23 −7
  2944. arch/powerpc/include/asm/opal.h +103 −106
  2945. arch/powerpc/include/asm/paca.h +8 −5
  2946. arch/powerpc/include/asm/page.h +3 −1
  2947. arch/powerpc/include/asm/page_64.h +31 −12
  2948. arch/powerpc/include/asm/pci-bridge.h +0 −2
  2949. arch/powerpc/include/asm/perf_event.h +1 −1
  2950. arch/powerpc/include/asm/pgalloc.h +2 −1
  2951. arch/powerpc/include/asm/pgtable-ppc32.h +22 −4
  2952. arch/powerpc/include/asm/pgtable-ppc64-4k.h +16 −2
  2953. arch/powerpc/include/asm/pgtable-ppc64-64k.h +3 −0
  2954. arch/powerpc/include/asm/pgtable-ppc64.h +42 −17
  2955. arch/powerpc/include/asm/pgtable.h +17 −49
  2956. arch/powerpc/include/asm/plpar_wrappers.h +6 −6
  2957. arch/powerpc/include/asm/pnv-pci.h +31 −0
  2958. arch/powerpc/include/asm/ppc-opcode.h +3 −0
  2959. arch/powerpc/include/asm/processor.h +3 −2
  2960. arch/powerpc/include/asm/prom.h +0 −2
  2961. arch/powerpc/include/asm/pte-8xx.h +5 −2
  2962. arch/powerpc/include/asm/pte-common.h +5 −0
  2963. arch/powerpc/include/asm/reg.h +7 −3
  2964. arch/powerpc/include/asm/reg_booke.h +2 −0
  2965. arch/powerpc/include/asm/rio.h +0 −1
  2966. arch/powerpc/include/asm/setup.h +1 −2
  2967. arch/powerpc/include/asm/spu.h +2 −3
  2968. arch/powerpc/include/asm/sstep.h +62 −0
  2969. arch/powerpc/include/asm/syscall.h +11 −1
  2970. arch/powerpc/include/asm/systbl.h +2 −0
  2971. arch/powerpc/include/asm/thread_info.h +2 −3
  2972. arch/powerpc/include/asm/tlb.h +1 −0
  2973. arch/powerpc/include/asm/tlbflush.h +6 −4
  2974. arch/powerpc/include/asm/tsi108.h +0 −4
  2975. arch/powerpc/include/asm/uaccess.h +3 −3
  2976. arch/powerpc/include/asm/udbg.h +0 −1
  2977. arch/powerpc/include/asm/unistd.h +1 −1
  2978. arch/powerpc/include/asm/vga.h +1 −3
  2979. arch/powerpc/include/asm/word-at-a-time.h +98 −14
  2980. arch/powerpc/include/asm/xics.h +5 −4
  2981. arch/powerpc/include/uapi/asm/kvm.h +6 −0
  2982. arch/powerpc/include/uapi/asm/socket.h +5 −0
  2983. arch/powerpc/include/uapi/asm/unistd.h +2 −0
  2984. arch/powerpc/kernel/Makefile +3 −0
  2985. arch/powerpc/kernel/align.c +1 −1
  2986. arch/powerpc/kernel/asm-offsets.c +9 −5
  2987. arch/powerpc/kernel/cpu_setup_fsl_booke.S +11 −1
  2988. arch/powerpc/kernel/cputable.c +5 −0
  2989. arch/powerpc/kernel/crash_dump.c +1 −1
  2990. arch/powerpc/kernel/dbell.c +1 −1
  2991. arch/powerpc/kernel/dma-iommu.c +4 −4
  2992. arch/powerpc/kernel/dma-swiotlb.c +6 −2
  2993. arch/powerpc/kernel/dma.c +51 −4
  2994. arch/powerpc/kernel/eeh.c +243 −74
  2995. arch/powerpc/kernel/eeh_driver.c +90 −20
  2996. arch/powerpc/kernel/eeh_pe.c +28 −5
  2997. arch/powerpc/kernel/eeh_sysfs.c +40 −1
  2998. arch/powerpc/kernel/entry_32.S +9 −3
  2999. arch/powerpc/kernel/entry_64.S +16 −25
  3000. arch/powerpc/kernel/exceptions-64e.S +2 −2
  3001. arch/powerpc/kernel/exceptions-64s.S +40 −34
  3002. arch/powerpc/kernel/fadump.c +57 −57
  3003. arch/powerpc/kernel/ftrace.c +16 −59
  3004. arch/powerpc/kernel/head_8xx.S +171 −195
  3005. arch/powerpc/kernel/head_fsl_booke.S +17 −9
  3006. arch/powerpc/kernel/hw_breakpoint.c +4 −4
  3007. arch/powerpc/kernel/ibmebus.c +1 −1
  3008. arch/powerpc/kernel/idle_power7.S +311 −47
  3009. arch/powerpc/kernel/iommu.c +9 −9
  3010. arch/powerpc/kernel/irq.c +6 −7
  3011. arch/powerpc/kernel/kgdb.c +1 −1
  3012. arch/powerpc/kernel/kprobes.c +3 −3
  3013. arch/powerpc/kernel/legacy_serial.c +1 −1
  3014. arch/powerpc/kernel/machine_kexec_64.c +1 −1
  3015. arch/powerpc/kernel/mce.c +12 −12
  3016. arch/powerpc/kernel/mce_power.c +2 −2
  3017. arch/powerpc/kernel/misc.S +4 −0
  3018. arch/powerpc/kernel/module_32.c +14 −17
  3019. arch/powerpc/kernel/module_64.c +17 −19
  3020. arch/powerpc/kernel/msi.c +1 −11
  3021. arch/powerpc/kernel/nvram_64.c +1 −1
  3022. arch/powerpc/kernel/of_platform.c +1 −2
  3023. arch/powerpc/kernel/pci-common.c +7 −5
  3024. arch/powerpc/kernel/pci_32.c +1 −3
  3025. arch/powerpc/kernel/pci_64.c +0 −11
  3026. arch/powerpc/kernel/pci_of_scan.c +1 −1
  3027. arch/powerpc/kernel/ppc_ksyms.c +15 −179
  3028. arch/powerpc/kernel/ppc_ksyms_32.c +61 −0
  3029. arch/powerpc/kernel/process.c +11 −29
  3030. arch/powerpc/kernel/prom.c +15 −9
  3031. arch/powerpc/kernel/prom_init_check.sh +6 −16
  3032. arch/powerpc/kernel/ptrace.c +3 −6
  3033. arch/powerpc/kernel/rtas-proc.c +9 −11
  3034. arch/powerpc/kernel/rtas.c +2 −2
  3035. arch/powerpc/kernel/rtas_pci.c +11 −20
  3036. arch/powerpc/kernel/rtasd.c +1 −1
  3037. arch/powerpc/kernel/setup-common.c +7 −6
  3038. arch/powerpc/kernel/setup_32.c +3 −10
  3039. arch/powerpc/kernel/setup_64.c +26 −47
  3040. arch/powerpc/kernel/smp.c +12 −5
  3041. arch/powerpc/kernel/stacktrace.c +1 −1
  3042. arch/powerpc/kernel/suspend.c +1 −3
  3043. arch/powerpc/kernel/sysfs.c +2 −2
  3044. arch/powerpc/kernel/time.c +15 −13
  3045. arch/powerpc/kernel/traps.c +4 −4
  3046. arch/powerpc/kernel/udbg_16550.c +5 −1
  3047. arch/powerpc/kernel/vdso.c +0 −1
  3048. arch/powerpc/kernel/vdso32/getcpu.S +2 −2
  3049. arch/powerpc/kvm/Kconfig +1 −0
  3050. arch/powerpc/kvm/book3s.c +49 −121
  3051. arch/powerpc/kvm/book3s.h +2 −1
  3052. arch/powerpc/kvm/book3s_32_mmu.c +0 −5
  3053. arch/powerpc/kvm/book3s_64_mmu_hv.c +36 −192
  3054. arch/powerpc/kvm/book3s_hv.c +185 −300
  3055. arch/powerpc/kvm/book3s_hv_builtin.c +41 −104
  3056. arch/powerpc/kvm/book3s_hv_interrupts.S +1 −38
  3057. arch/powerpc/kvm/book3s_hv_ras.c +1 −4
  3058. arch/powerpc/kvm/book3s_hv_rm_mmu.c +32 −118
  3059. arch/powerpc/kvm/book3s_hv_rm_xics.c +28 −8
  3060. arch/powerpc/kvm/book3s_hv_rmhandlers.S +46 −260
  3061. arch/powerpc/kvm/book3s_paired_singles.c +0 −8
  3062. arch/powerpc/kvm/book3s_pr.c +5 −6
  3063. arch/powerpc/kvm/book3s_xics.c +23 −7
  3064. arch/powerpc/kvm/book3s_xics.h +1 −0
  3065. arch/powerpc/kvm/booke.c +214 −73
  3066. arch/powerpc/kvm/booke.h +6 −34
  3067. arch/powerpc/kvm/booke_emulate.c +163 −0
  3068. arch/powerpc/kvm/bookehv_interrupts.S +4 −9
  3069. arch/powerpc/kvm/e500.c +7 −15
  3070. arch/powerpc/kvm/e500.h +20 −0
  3071. arch/powerpc/kvm/e500_emulate.c +20 −0
  3072. arch/powerpc/kvm/e500_mmu_host.c +12 −14
  3073. arch/powerpc/kvm/e500mc.c +44 −16
  3074. arch/powerpc/kvm/emulate.c +16 −1
  3075. arch/powerpc/kvm/emulate_loadstore.c +1 −1
  3076. arch/powerpc/kvm/powerpc.c +102 −42
  3077. arch/powerpc/kvm/trace_book3s.h +32 −0
  3078. arch/powerpc/kvm/trace_booke.h +45 −2
  3079. arch/powerpc/kvm/trace_hv.h +477 −0
  3080. arch/powerpc/kvm/trace_pr.h +1 −24
  3081. arch/powerpc/lib/Makefile +1 −2
  3082. arch/powerpc/lib/alloc.c +1 −3
  3083. arch/powerpc/lib/copyuser_power7.S +1 −1
  3084. arch/powerpc/lib/devres.c +0 −43
  3085. arch/powerpc/lib/feature-fixups.c +1 −1
  3086. arch/powerpc/lib/memcpy_power7.S +1 −1
  3087. arch/powerpc/lib/ppc_ksyms.c +39 −0
  3088. arch/powerpc/lib/sstep.c +638 −360
  3089. arch/powerpc/mm/Makefile +2 −1
  3090. arch/powerpc/mm/copro_fault.c +148 −0
  3091. arch/powerpc/mm/fault.c +29 −26
  3092. arch/powerpc/mm/gup.c +0 −235
  3093. arch/powerpc/mm/hash_low_64.S +10 −9
  3094. arch/powerpc/mm/hash_native_64.c +32 −15
  3095. arch/powerpc/mm/hash_utils_64.c +180 −90
  3096. arch/powerpc/mm/hugepage-hash64.c +5 −55
  3097. arch/powerpc/mm/hugetlbpage-book3e.c +3 −3
  3098. arch/powerpc/mm/hugetlbpage-hash64.c +3 −3
  3099. arch/powerpc/mm/hugetlbpage.c +26 −27
  3100. arch/powerpc/mm/init_32.c +3 −13
  3101. arch/powerpc/mm/init_64.c +0 −4
  3102. arch/powerpc/mm/mem.c +77 −68
  3103. arch/powerpc/mm/mmu_context_nohash.c +4 −4
  3104. arch/powerpc/mm/mmu_decl.h +1 −1
  3105. arch/powerpc/mm/numa.c +90 −212
  3106. arch/powerpc/mm/pgtable.c +1 −1
  3107. arch/powerpc/mm/pgtable_32.c +2 −3
  3108. arch/powerpc/mm/pgtable_64.c +36 −68
  3109. arch/powerpc/mm/slb.c +0 −3
  3110. arch/powerpc/mm/slice.c +7 −8
  3111. arch/powerpc/net/bpf_jit.h +7 −0
  3112. arch/powerpc/net/bpf_jit_comp.c +29 −25
  3113. arch/powerpc/oprofile/backtrace.c +5 −2
  3114. arch/powerpc/oprofile/cell/spu_task_sync.c +4 −6
  3115. arch/powerpc/perf/core-book3s.c +20 −20
  3116. arch/powerpc/perf/core-fsl-emb.c +3 −3
  3117. arch/powerpc/perf/hv-24x7.c +48 −111
  3118. arch/powerpc/perf/hv-gpci.c +0 −6
  3119. arch/powerpc/platforms/40x/ep405.c +1 −1
  3120. arch/powerpc/platforms/40x/ppc40x_simple.c +1 −1
  3121. arch/powerpc/platforms/40x/virtex.c +1 −1
  3122. arch/powerpc/platforms/40x/walnut.c +1 −1
  3123. arch/powerpc/platforms/44x/Kconfig +3 −4
  3124. arch/powerpc/platforms/44x/canyonlands.c +1 −1
  3125. arch/powerpc/platforms/44x/ebony.c +1 −1
  3126. arch/powerpc/platforms/44x/iss4xx.c +1 −1
  3127. arch/powerpc/platforms/44x/ppc44x_simple.c +1 −1
  3128. arch/powerpc/platforms/44x/ppc476.c +2 −2
  3129. arch/powerpc/platforms/44x/sam440ep.c +1 −1
  3130. arch/powerpc/platforms/44x/virtex.c +1 −1
  3131. arch/powerpc/platforms/44x/warp.c +1 −1
  3132. arch/powerpc/platforms/512x/mpc512x_shared.c +5 −6
  3133. arch/powerpc/platforms/52xx/efika.c +2 −1
  3134. arch/powerpc/platforms/52xx/lite5200.c +2 −2
  3135. arch/powerpc/platforms/52xx/media5200.c +1 −1
  3136. arch/powerpc/platforms/52xx/mpc52xx_common.c +6 −6
  3137. arch/powerpc/platforms/52xx/mpc52xx_gpt.c +0 −1
  3138. arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c +1 −2
  3139. arch/powerpc/platforms/52xx/mpc52xx_pic.c +2 −2
  3140. arch/powerpc/platforms/82xx/ep8248e.c +1 −2
  3141. arch/powerpc/platforms/82xx/km82xx.c +1 −1
  3142. arch/powerpc/platforms/82xx/mpc8272_ads.c +1 −1
  3143. arch/powerpc/platforms/82xx/pq2fads.c +1 −1
  3144. arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c +7 −6
  3145. arch/powerpc/platforms/83xx/misc.c +1 −1
  3146. arch/powerpc/platforms/83xx/mpc834x_itx.c +1 −1
  3147. arch/powerpc/platforms/83xx/suspend.c +2 −3
  3148. arch/powerpc/platforms/85xx/Kconfig +1 −1
  3149. arch/powerpc/platforms/85xx/common.c +1 −1
  3150. arch/powerpc/platforms/85xx/corenet_generic.c +15 −1
  3151. arch/powerpc/platforms/85xx/ppa8548.c +1 −1
  3152. arch/powerpc/platforms/85xx/qemu_e500.c +10 −0
  3153. arch/powerpc/platforms/85xx/sgy_cts1000.c +4 −5
  3154. arch/powerpc/platforms/86xx/gef_ppc9a.c +1 −1
  3155. arch/powerpc/platforms/86xx/gef_sbc310.c +1 −1
  3156. arch/powerpc/platforms/86xx/gef_sbc610.c +1 −1
  3157. arch/powerpc/platforms/86xx/mpc8610_hpcd.c +1 −1
  3158. arch/powerpc/platforms/86xx/mpc86xx_hpcn.c +1 −1
  3159. arch/powerpc/platforms/86xx/sbc8641d.c +1 −1
  3160. arch/powerpc/platforms/8xx/Kconfig +0 −4
  3161. arch/powerpc/platforms/8xx/adder875.c +1 −1
  3162. arch/powerpc/platforms/8xx/ep88xc.c +1 −1
  3163. arch/powerpc/platforms/8xx/mpc86xads_setup.c +1 −1
  3164. arch/powerpc/platforms/8xx/mpc885ads_setup.c +1 −1
  3165. arch/powerpc/platforms/8xx/tqm8xx_setup.c +1 −1
  3166. arch/powerpc/platforms/Kconfig.cputype +11 −1
  3167. arch/powerpc/platforms/cell/Kconfig +1 −0
  3168. arch/powerpc/platforms/cell/Makefile +1 −1
  3169. arch/powerpc/platforms/cell/axon_msi.c +4 −14
  3170. arch/powerpc/platforms/cell/beat_htab.c +2 −2
  3171. arch/powerpc/platforms/cell/celleb_pci.c +4 −4
  3172. arch/powerpc/platforms/cell/celleb_scc_epci.c +0 −1
  3173. arch/powerpc/platforms/cell/celleb_scc_pciex.c +0 −1
  3174. arch/powerpc/platforms/cell/celleb_setup.c +3 −3
  3175. arch/powerpc/platforms/cell/interrupt.c +3 −3
  3176. arch/powerpc/platforms/cell/iommu.c +5 −4
  3177. arch/powerpc/platforms/cell/qpace_setup.c +1 −1
  3178. arch/powerpc/platforms/cell/setup.c +1 −1
  3179. arch/powerpc/platforms/cell/spu_base.c +12 −48
  3180. arch/powerpc/platforms/cell/spu_fault.c +0 −94
  3181. arch/powerpc/platforms/cell/spufs/fault.c +3 −3
  3182. arch/powerpc/platforms/cell/spufs/inode.c +3 −3
  3183. arch/powerpc/platforms/chrp/setup.c +3 −2
  3184. arch/powerpc/platforms/embedded6xx/gamecube.c +3 −2
  3185. arch/powerpc/platforms/embedded6xx/linkstation.c +4 −2
  3186. arch/powerpc/platforms/embedded6xx/mvme5100.c +1 −1
  3187. arch/powerpc/platforms/embedded6xx/storcenter.c +1 −1
  3188. arch/powerpc/platforms/embedded6xx/usbgecko_udbg.c +3 −3
  3189. arch/powerpc/platforms/embedded6xx/wii.c +3 −2
  3190. arch/powerpc/platforms/maple/pci.c +0 −1
  3191. arch/powerpc/platforms/maple/setup.c +2 −2
  3192. arch/powerpc/platforms/pasemi/gpio_mdio.c +1 −2
  3193. arch/powerpc/platforms/pasemi/setup.c +1 −1
  3194. arch/powerpc/platforms/powermac/nvram.c +1 −5
  3195. arch/powerpc/platforms/powermac/pci.c +0 −1
  3196. arch/powerpc/platforms/powermac/setup.c +6 −5
  3197. arch/powerpc/platforms/powernv/eeh-ioda.c +207 −33
  3198. arch/powerpc/platforms/powernv/eeh-powernv.c +81 −2
  3199. arch/powerpc/platforms/powernv/opal-async.c +3 −0
  3200. arch/powerpc/platforms/powernv/opal-dump.c +13 −5
  3201. arch/powerpc/platforms/powernv/opal-elog.c +4 −0
  3202. arch/powerpc/platforms/powernv/opal-hmi.c +1 −1
  3203. arch/powerpc/platforms/powernv/opal-lpc.c +59 −0
  3204. arch/powerpc/platforms/powernv/opal-nvram.c +1 −1
  3205. arch/powerpc/platforms/powernv/opal-rtc.c +22 −44
  3206. arch/powerpc/platforms/powernv/opal-sensor.c +20 −0
  3207. arch/powerpc/platforms/powernv/opal-tracepoints.c +3 −3
  3208. arch/powerpc/platforms/powernv/opal-wrappers.S +48 −2
  3209. arch/powerpc/platforms/powernv/opal.c +94 −6
  3210. arch/powerpc/platforms/powernv/pci-ioda.c +396 −116
  3211. arch/powerpc/platforms/powernv/pci-p5ioc2.c +20 −24
  3212. arch/powerpc/platforms/powernv/pci.c +17 −17
  3213. arch/powerpc/platforms/powernv/pci.h +5 −1
  3214. arch/powerpc/platforms/powernv/powernv.h +8 −0
  3215. arch/powerpc/platforms/powernv/setup.c +178 −5
  3216. arch/powerpc/platforms/powernv/smp.c +45 −7
  3217. arch/powerpc/platforms/powernv/subcore.c +35 −0
  3218. arch/powerpc/platforms/powernv/subcore.h +8 −1
  3219. arch/powerpc/platforms/ps3/htab.c +1 −1
  3220. arch/powerpc/platforms/ps3/interrupt.c +1 −1
  3221. arch/powerpc/platforms/ps3/setup.c +2 −7
  3222. arch/powerpc/platforms/pseries/cmm.c +0 −1
  3223. arch/powerpc/platforms/pseries/dlpar.c +30 −25
  3224. arch/powerpc/platforms/pseries/dtl.c +1 −1
  3225. arch/powerpc/platforms/pseries/eeh_pseries.c +14 −26
  3226. arch/powerpc/platforms/pseries/hotplug-cpu.c +12 −9
  3227. arch/powerpc/platforms/pseries/hotplug-memory.c +10 −31
  3228. arch/powerpc/platforms/pseries/hvCall.S +2 −2
  3229. arch/powerpc/platforms/pseries/hvCall_inst.c +2 −2
  3230. arch/powerpc/platforms/pseries/iommu.c +41 −37
  3231. arch/powerpc/platforms/pseries/lpar.c +25 −11
  3232. arch/powerpc/platforms/pseries/msi.c +18 −28
  3233. arch/powerpc/platforms/pseries/nvram.c +9 −5
  3234. arch/powerpc/platforms/pseries/pci.c +2 −1
  3235. arch/powerpc/platforms/pseries/pseries.h +2 −1
  3236. arch/powerpc/platforms/pseries/ras.c +3 −3
  3237. arch/powerpc/platforms/pseries/setup.c +39 −33
  3238. arch/powerpc/sysdev/axonram.c +1 −2
  3239. arch/powerpc/sysdev/dcr.c +1 −0
  3240. arch/powerpc/sysdev/fsl_85xx_l2ctlr.c +1 −2
  3241. arch/powerpc/sysdev/fsl_msi.c +56 −59
  3242. arch/powerpc/sysdev/fsl_msi.h +3 −1
  3243. arch/powerpc/sysdev/fsl_pci.c +3 −3
  3244. arch/powerpc/sysdev/fsl_pmc.c +0 −1
  3245. arch/powerpc/sysdev/fsl_rio.c +104 −1
  3246. arch/powerpc/sysdev/fsl_rio.h +13 −0
  3247. arch/powerpc/sysdev/fsl_soc.c +2 −3
  3248. arch/powerpc/sysdev/ipic.c +0 −1
  3249. arch/powerpc/sysdev/mpc5xxx_clocks.c +1 −2
  3250. arch/powerpc/sysdev/mpic.c +1 −2
  3251. arch/powerpc/sysdev/mpic_msgr.c +0 −1
  3252. arch/powerpc/sysdev/mpic_pasemi_msi.c +5 −13
  3253. arch/powerpc/sysdev/mpic_u3msi.c +14 −21
  3254. arch/powerpc/sysdev/msi_bitmap.c +56 −38
  3255. arch/powerpc/sysdev/mv64x60_dev.c +1 −1
  3256. arch/powerpc/sysdev/pmi.c +1 −2
  3257. arch/powerpc/sysdev/ppc4xx_cpm.c +4 −4
  3258. arch/powerpc/sysdev/ppc4xx_hsta_msi.c +7 −14
  3259. arch/powerpc/sysdev/ppc4xx_msi.c +7 −16
  3260. arch/powerpc/sysdev/ppc4xx_pci.c +0 −1
  3261. arch/powerpc/sysdev/qe_lib/qe.c +0 −2
  3262. arch/powerpc/sysdev/qe_lib/qe_ic.c +0 −1
  3263. arch/powerpc/sysdev/uic.c +0 −1
  3264. arch/powerpc/sysdev/xics/icp-native.c +25 −0
  3265. arch/powerpc/sysdev/xics/ics-opal.c +1 −1
  3266. arch/powerpc/sysdev/xics/ics-rtas.c +1 −1
  3267. arch/powerpc/sysdev/xics/xics-common.c +1 −1
  3268. arch/powerpc/sysdev/xilinx_intc.c +1 −1
  3269. arch/powerpc/sysdev/xilinx_pci.c +1 −1
  3270. arch/powerpc/xmon/xmon.c +66 −22
  3271. arch/s390/Kconfig +10 −7
  3272. arch/s390/Makefile +10 −7
  3273. arch/s390/appldata/appldata_base.c +0 −1
  3274. arch/s390/configs/default_defconfig +14 −22
  3275. arch/s390/configs/gcov_defconfig +5 −20
  3276. arch/s390/configs/performance_defconfig +9 −21
  3277. arch/s390/configs/zfcpdump_defconfig +2 −8
  3278. arch/s390/crypto/aes_s390.c +1 −1
  3279. arch/s390/crypto/des_s390.c +2 −2
  3280. arch/s390/crypto/ghash_s390.c +1 −1
  3281. arch/s390/crypto/sha1_s390.c +1 −1
  3282. arch/s390/crypto/sha256_s390.c +2 −2
  3283. arch/s390/crypto/sha512_s390.c +2 −2
  3284. arch/s390/defconfig +2 −3
  3285. arch/s390/hypfs/hypfs_dbfs.c +1 −2
  3286. arch/s390/include/asm/Kbuild +1 −1
  3287. arch/s390/include/asm/barrier.h +9 −4
  3288. arch/s390/include/asm/cmpxchg.h +16 −224
  3289. arch/s390/include/asm/cputime.h +28 −46
  3290. arch/s390/include/asm/debug.h +27 −2
  3291. arch/s390/include/asm/dis.h +7 −6
.gitignore+3−0
@@ -96,3 +96,6 @@ x509.genkey · 95 unmodified lines
9696
9797 # Kconfig presets
9898 all.config
99+
100+# Kdevelop4
101+*.kdev4
.mailmap+4−1
@@ -17,7 +17,7 @@ Aleksey Gorelov <aleksey_gorelov@phoenix.com> · 16 unmodified lines
1717 Al Viro <viro@ftp.linux.org.uk>
1818 Al Viro <viro@zenIV.linux.org.uk>
1919 Andreas Herrmann <aherrman@de.ibm.com>
20−Andrew Morton <akpm@osdl.org>
20+Andrew Morton <akpm@linux-foundation.org>
2121 Andrew Vasquez <andrew.vasquez@qlogic.com>
2222 Andy Adamson <andros@citi.umich.edu>
2323 Archit Taneja <archit@ti.com>
@@ -51,6 +51,7 @@ Greg Kroah-Hartman <gregkh@suse.de> · 27 unmodified lines
5151 Greg Kroah-Hartman <greg@kroah.com>
5252 Henk Vergonet <Henk.Vergonet@gmail.com>
5353 Henrik Kretzschmar <henne@nachtwindheim.de>
54+Henrik Rydberg <rydberg@bitmath.org>
5455 Herbert Xu <herbert@gondor.apana.org.au>
5556 Jacob Shin <Jacob.Shin@amd.com>
5657 James Bottomley <jejb@mulgrave.(none)>
@@ -102,6 +103,8 @@ Rudolf Marek <R.Marek@sh.cvut.cz> · 45 unmodified lines
102103 Rui Saraiva <rmps@joel.ist.utl.pt>
103104 Sachin P Sant <ssant@in.ibm.com>
104105 Sam Ravnborg <sam@mars.ravnborg.org>
106+Santosh Shilimkar <ssantosh@kernel.org>
107+Santosh Shilimkar <santosh.shilimkar@oracle.org>
105108 Sascha Hauer <s.hauer@pengutronix.de>
106109 S.Çağlar Onur <caglar@pardus.org.tr>
107110 Shiraz Hashim <shiraz.linux.kernel@gmail.com> <shiraz.hashim@st.com>
CREDITS+10−3
@@ -1197,6 +1197,13 @@ S: R. Tocantins, 89 - Cristo Rei · 1196 unmodified lines
11971197 S: 80050-430 - Curitiba - Paraná
11981198 S: Brazil
11991199
1200+N: Oded Gabbay
1201+E: oded.gabbay@gmail.com
1202+D: AMD KFD maintainer
1203+S: 12 Shraga Raphaeli
1204+S: Petah-Tikva, 4906418
1205+S: Israel
1206+
12001207 N: Kumar Gala
12011208 E: galak@kernel.crashing.org
12021209 D: Embedded PowerPC 6xx/7xx/74xx/82xx/83xx/85xx support
@@ -1727,14 +1734,14 @@ S: Chapel Hill, North Carolina 27514-4818 · 524 unmodified lines
17271734 S: USA
17281735
17291736 N: Dave Jones
1730−E: davej@redhat.com
1737+E: davej@codemonkey.org.uk
17311738 W: http://www.codemonkey.org.uk
17321739 D: Assorted VIA x86 support.
17331740 D: 2.5 AGPGART overhaul.
17341741 D: CPUFREQ maintenance.
1735−D: Fedora kernel maintenance.
1742+D: Fedora kernel maintenance (2003-2014).
1743+D: 'Trinity' and similar fuzz testing work.
17361744 D: Misc/Other.
1737−S: 314 Littleton Rd, Westford, MA 01886, USA
17381745
17391746 N: Martin Josfsson
17401747 E: gandalf@wlug.westbo.se
Documentation/.gitignore+0−7
@@ -1,7 +0,0 @@
1−filesystems/dnotify_test
2−laptops/dslm
3−timers/hpet_example
4−vm/hugepage-mmap
5−vm/hugepage-shm
6−vm/map_hugetlb
7−
Documentation/00-INDEX+2−0
@@ -287,6 +287,8 @@ local_ops.txt · 286 unmodified lines
287287 - semantics and behavior of local atomic operations.
288288 lockdep-design.txt
289289 - documentation on the runtime locking correctness validator.
290+locking/
291+ - directory with info about kernel locking primitives
290292 lockstat.txt
291293 - info on collecting statistics on locks (and contention).
292294 lockup-watchdogs.txt
Documentation/ABI/removed/net_dma+8−0
@@ -0,0 +1,8 @@
1+What: tcp_dma_copybreak sysctl
2+Date: Removed in kernel v3.13
3+Contact: Dan Williams <dan.j.williams@intel.com>
4+Description:
5+ Formerly the lower limit, in bytes, of the size of socket reads
6+ that will be offloaded to a DMA copy engine. Removed due to
7+ coherency issues of the cpu potentially touching the buffers
8+ while dma is in flight.
Documentation/ABI/stable/sysfs-bus-usb+6−8
@@ -32,10 +32,9 @@ Date: January 2008 · 31 unmodified lines
3232 KernelVersion: 2.6.25
3333 Contact: Sarah Sharp <sarah.a.sharp@intel.com>
3434 Description:
35− If CONFIG_PM_RUNTIME is enabled then this file
36− is present. When read, it returns the total time (in msec)
37− that the USB device has been connected to the machine. This
38− file is read-only.
35+ If CONFIG_PM is enabled, then this file is present. When read,
36+ it returns the total time (in msec) that the USB device has been
37+ connected to the machine. This file is read-only.
3938 Users:
4039 PowerTOP <powertop@lists.01.org>
4140 https://01.org/powertop/
@@ -45,10 +44,9 @@ Date: January 2008 · 3 unmodified lines
4544 KernelVersion: 2.6.25
4645 Contact: Sarah Sharp <sarah.a.sharp@intel.com>
4746 Description:
48− If CONFIG_PM_RUNTIME is enabled then this file
49− is present. When read, it returns the total time (in msec)
50− that the USB device has been active, i.e. not in a suspended
51− state. This file is read-only.
47+ If CONFIG_PM is enabled, then this file is present. When read,
48+ it returns the total time (in msec) that the USB device has been
49+ active, i.e. not in a suspended state. This file is read-only.
5250
5351 Tools can use this file and the connected_duration file to
5452 compute the percentage of time that a device has been active.
Documentation/ABI/stable/sysfs-class-udc+93−0
@@ -0,0 +1,93 @@
1+What: /sys/class/udc/<udc>/a_alt_hnp_support
2+Date: June 2011
3+KernelVersion: 3.1
4+Contact: Felipe Balbi <balbi@kernel.org>
5+Description:
6+ Indicates if an OTG A-Host supports HNP at an alternate port.
7+Users:
8+
9+What: /sys/class/udc/<udc>/a_hnp_support
10+Date: June 2011
11+KernelVersion: 3.1
12+Contact: Felipe Balbi <balbi@kernel.org>
13+Description:
14+ Indicates if an OTG A-Host supports HNP at this port.
15+Users:
16+
17+What: /sys/class/udc/<udc>/b_hnp_enable
18+Date: June 2011
19+KernelVersion: 3.1
20+Contact: Felipe Balbi <balbi@kernel.org>
21+Description:
22+ Indicates if an OTG A-Host enabled HNP support.
23+Users:
24+
25+What: /sys/class/udc/<udc>/current_speed
26+Date: June 2011
27+KernelVersion: 3.1
28+Contact: Felipe Balbi <balbi@kernel.org>
29+Description:
30+ Indicates the current negotiated speed at this port.
31+Users:
32+
33+What: /sys/class/udc/<udc>/is_a_peripheral
34+Date: June 2011
35+KernelVersion: 3.1
36+Contact: Felipe Balbi <balbi@kernel.org>
37+Description:
38+ Indicates that this port is the default Host on an OTG session
39+ but HNP was used to switch roles.
40+Users:
41+
42+What: /sys/class/udc/<udc>/is_otg
43+Date: June 2011
44+KernelVersion: 3.1
45+Contact: Felipe Balbi <balbi@kernel.org>
46+Description:
47+ Indicates that this port support OTG.
48+Users:
49+
50+What: /sys/class/udc/<udc>/maximum_speed
51+Date: June 2011
52+KernelVersion: 3.1
53+Contact: Felipe Balbi <balbi@kernel.org>
54+Description:
55+ Indicates the maximum USB speed supported by this port.
56+Users:
57+
58+What: /sys/class/udc/<udc>/maximum_speed
59+Date: June 2011
60+KernelVersion: 3.1
61+Contact: Felipe Balbi <balbi@kernel.org>
62+Description:
63+ Indicates the maximum USB speed supported by this port.
64+Users:
65+
66+What: /sys/class/udc/<udc>/soft_connect
67+Date: June 2011
68+KernelVersion: 3.1
69+Contact: Felipe Balbi <balbi@kernel.org>
70+Description:
71+ Allows users to disconnect data pullup resistors thus causing a
72+ logical disconnection from the USB Host.
73+Users:
74+
75+What: /sys/class/udc/<udc>/srp
76+Date: June 2011
77+KernelVersion: 3.1
78+Contact: Felipe Balbi <balbi@kernel.org>
79+Description:
80+ Allows users to manually start Session Request Protocol.
81+Users:
82+
83+What: /sys/class/udc/<udc>/state
84+Date: June 2011
85+KernelVersion: 3.1
86+Contact: Felipe Balbi <balbi@kernel.org>
87+Description:
88+ Indicates current state of the USB Device Controller. Valid
89+ states are: 'not-attached', 'attached', 'powered',
90+ 'reconnecting', 'unauthenticated', 'default', 'addressed',
91+ 'configured', and 'suspended'; however not all USB Device
92+ Controllers support reporting all states.
93+Users:
Documentation/ABI/stable/sysfs-devices-node+0−8
@@ -85,14 +85,6 @@ Description: · 84 unmodified lines
8585 will be compacted. When it completes, memory will be freed
8686 into blocks which have as many contiguous pages as possible
8787
88−What: /sys/devices/system/node/nodeX/scan_unevictable_pages
89−Date: October 2008
90−Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
91−Description:
92− When set, it triggers scanning the node's unevictable lists
93− and move any pages that have become evictable onto the respective
94− zone's inactive list. See mm/vmscan.c
95−
9688 What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
9789 Date: December 2009
9890 Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
Documentation/ABI/stable/sysfs-driver-ib_srp+19−6
@@ -55,12 +55,12 @@ Description: Interface for making ib_srp connect to a new target. · 54 unmodified lines
5555 only safe with partial memory descriptor list support enabled
5656 (allow_ext_sg=1).
5757 * comp_vector, a number in the range 0..n-1 specifying the
58− MSI-X completion vector. Some HCA's allocate multiple (n)
59− MSI-X vectors per HCA port. If the IRQ affinity masks of
60− these interrupts have been configured such that each MSI-X
61− interrupt is handled by a different CPU then the comp_vector
62− parameter can be used to spread the SRP completion workload
63− over multiple CPU's.
58+ MSI-X completion vector of the first RDMA channel. Some
59+ HCA's allocate multiple (n) MSI-X vectors per HCA port. If
60+ the IRQ affinity masks of these interrupts have been
61+ configured such that each MSI-X interrupt is handled by a
62+ different CPU then the comp_vector parameter can be used to
63+ spread the SRP completion workload over multiple CPU's.
6464 * tl_retry_count, a number in the range 2..7 specifying the
6565 IB RC retry count.
6666 * queue_size, the maximum number of commands that the
@@ -88,6 +88,13 @@ Description: Whether ib_srp is allowed to include a partial memory · 21 unmodified lines
8888 descriptor list in an SRP_CMD when communicating with an SRP
8989 target.
9090
91+What: /sys/class/scsi_host/host<n>/ch_count
92+Date: April 1, 2015
93+KernelVersion: 3.19
94+Contact: linux-rdma@vger.kernel.org
95+Description: Number of RDMA channels used for communication with the SRP
96+ target.
97+
9198 What: /sys/class/scsi_host/host<n>/cmd_sg_entries
9299 Date: May 19, 2011
93100 KernelVersion: 2.6.39
@@ -95,6 +102,12 @@ Contact: linux-rdma@vger.kernel.org · 1 unmodified line
95102 Description: Maximum number of data buffer descriptors that may be sent to
96103 the target in a single SRP_CMD request.
97104
105+What: /sys/class/scsi_host/host<n>/comp_vector
106+Date: September 2, 2013
107+KernelVersion: 3.11
108+Contact: linux-rdma@vger.kernel.org
109+Description: Completion vector used for the first RDMA channel.
110+
98111 What: /sys/class/scsi_host/host<n>/dgid
99112 Date: June 17, 2006
100113 KernelVersion: 2.6.17
Documentation/ABI/testing/configfs-usb-gadget-hid+11−0
@@ -0,0 +1,11 @@
1+What: /config/usb-gadget/gadget/functions/hid.name
2+Date: Nov 2014
3+KernelVersion: 3.19
4+Description:
5+ The attributes:
6+
7+ protocol - HID protocol to use
8+ report_desc - blob corresponding to HID report descriptors
9+ except the data passed through /dev/hidg<N>
10+ report_length - HID report length
11+ subclass - HID device subclass to use
Documentation/ABI/testing/configfs-usb-gadget-midi+12−0
@@ -0,0 +1,12 @@
1+What: /config/usb-gadget/gadget/functions/midi.name
2+Date: Nov 2014
3+KernelVersion: 3.19
4+Description:
5+ The attributes:
6+
7+ index - index value for the USB MIDI adapter
8+ id - ID string for the USB MIDI adapter
9+ buflen - MIDI buffer length
10+ qlen - USB read request queue length
11+ in_ports - number of MIDI input ports
12+ out_ports - number of MIDI output ports
Documentation/ABI/testing/configfs-usb-gadget-uac1+12−0
@@ -0,0 +1,12 @@
1+What: /config/usb-gadget/gadget/functions/uac1.name
2+Date: Sep 2014
3+KernelVersion: 3.18
4+Description:
5+ The attributes:
6+
7+ audio_buf_size - audio buffer size
8+ fn_cap - capture pcm device file name
9+ fn_cntl - control device file name
10+ fn_play - playback pcm device file name
11+ req_buf_size - ISO OUT endpoint request buffer size
12+ req_count - ISO OUT endpoint request count
Documentation/ABI/testing/configfs-usb-gadget-uac2+12−0
@@ -0,0 +1,12 @@
1+What: /config/usb-gadget/gadget/functions/uac2.name
2+Date: Sep 2014
3+KernelVersion: 3.18
4+Description:
5+ The attributes:
6+
7+ c_chmask - capture channel mask
8+ c_srate - capture sampling rate
9+ c_ssize - capture sample size (bytes)
10+ p_chmask - playback channel mask
11+ p_srate - playback sampling rate
12+ p_ssize - playback sample size (bytes)
Documentation/ABI/testing/sysfs-block+8−0
@@ -53,6 +53,14 @@ Description: · 52 unmodified lines
5353 512 bytes of data.
5454
5555
56+What: /sys/block/<disk>/integrity/device_is_integrity_capable
57+Date: July 2014
58+Contact: Martin K. Petersen <martin.petersen@oracle.com>
59+Description:
60+ Indicates whether a storage device is capable of storing
61+ integrity metadata. Set if the device is T10 PI-capable.
62+
63+
5664 What: /sys/block/<disk>/integrity/write_generate
5765 Date: June 2008
5866 Contact: Martin K. Petersen <martin.petersen@oracle.com>
Documentation/ABI/testing/sysfs-block-zram+27−5
@@ -77,11 +77,14 @@ What: /sys/block/zram<id>/notify_free · 76 unmodified lines
7777 Date: August 2010
7878 Contact: Nitin Gupta <ngupta@vflare.org>
7979 Description:
80− The notify_free file is read-only and specifies the number of
81− swap slot free notifications received by this device. These
82− notifications are sent to a swap block device when a swap slot
83− is freed. This statistic is applicable only when this disk is
84− being used as a swap disk.
80+ The notify_free file is read-only. Depending on device usage
81+ scenario it may account a) the number of pages freed because
82+ of swap slot free notifications or b) the number of pages freed
83+ because of REQ_DISCARD requests sent by bio. The former ones
84+ are sent to a swap block device when a swap slot is freed, which
85+ implies that this disk is being used as a swap disk. The latter
86+ ones are sent by filesystem mounted with discard option,
87+ whenever some data blocks are getting discarded.
8588
8689 What: /sys/block/zram<id>/zero_pages
8790 Date: August 2010
@@ -119,3 +122,22 @@ Description: · 31 unmodified lines
119122 efficiency can be calculated using compr_data_size and this
120123 statistic.
121124 Unit: bytes
125+
126+What: /sys/block/zram<id>/mem_used_max
127+Date: August 2014
128+Contact: Minchan Kim <minchan@kernel.org>
129+Description:
130+ The mem_used_max file is read/write and specifies the amount
131+ of maximum memory zram have consumed to store compressed data.
132+ For resetting the value, you should write "0". Otherwise,
133+ you could see -EINVAL.
134+ Unit: bytes
135+
136+What: /sys/block/zram<id>/mem_limit
137+Date: August 2014
138+Contact: Minchan Kim <minchan@kernel.org>
139+Description:
140+ The mem_limit file is read/write and specifies the maximum
141+ amount of memory ZRAM can use to store the compressed data. The
142+ limit could be changed in run time and "0" means disable the
143+ limit. No limit is the initial state. Unit: bytes
Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10+24−0
@@ -0,0 +1,24 @@
1+What: /sys/bus/coresight/devices/<memory_map>.etb/enable_sink
2+Date: November 2014
3+KernelVersion: 3.19
4+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
5+Description: (RW) Add/remove a sink from a trace path. There can be multiple
6+ source for a single sink.
7+ ex: echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink
8+
9+What: /sys/bus/coresight/devices/<memory_map>.etb/status
10+Date: November 2014
11+KernelVersion: 3.19
12+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
13+Description: (R) List various control and status registers. The specific
14+ layout and content is driver specific.
15+
16+What: /sys/bus/coresight/devices/<memory_map>.etb/trigger_cntr
17+Date: November 2014
18+KernelVersion: 3.19
19+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
20+Description: (RW) Disables write access to the Trace RAM by stopping the
21+ formatter after a defined number of words have been stored
22+ following the trigger event. The number of 32-bit words written
23+ into the Trace RAM following the trigger event is equal to the
24+ value stored in this register+1 (from ARM ETB-TRM).
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x+253−0
@@ -0,0 +1,253 @@
1+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/enable_source
2+Date: November 2014
3+KernelVersion: 3.19
4+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
5+Description: (RW) Enable/disable tracing on this specific trace entiry.
6+ Enabling a source implies the source has been configured
7+ properly and a sink has been identidifed for it. The path
8+ of coresight components linking the source to the sink is
9+ configured and managed automatically by the coresight framework.
10+
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+
18+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_idx
19+Date: November 2014
20+KernelVersion: 3.19
21+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
22+Description: Select which address comparator or pair (of comparators) to
23+ work with.
24+
25+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_acctype
26+Date: November 2014
27+KernelVersion: 3.19
28+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
29+Description: (RW) Used in conjunction with @addr_idx. Specifies
30+ characteristics about the address comparator being configure,
31+ for example the access type, the kind of instruction to trace,
32+ processor contect ID to trigger on, etc. Individual fields in
33+ the access type register may vary on the version of the trace
34+ entity.
35+
36+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_range
37+Date: November 2014
38+KernelVersion: 3.19
39+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
40+Description: (RW) Used in conjunction with @addr_idx. Specifies the range of
41+ addresses to trigger on. Inclusion or exclusion is specificed
42+ in the corresponding access type register.
43+
44+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_single
45+Date: November 2014
46+KernelVersion: 3.19
47+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
48+Description: (RW) Used in conjunction with @addr_idx. Specifies the single
49+ address to trigger on, highly influenced by the configuration
50+ options of the corresponding access type register.
51+
52+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_start
53+Date: November 2014
54+KernelVersion: 3.19
55+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
56+Description: (RW) Used in conjunction with @addr_idx. Specifies the single
57+ address to start tracing on, highly influenced by the
58+ configuration options of the corresponding access type register.
59+
60+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_stop
61+Date: November 2014
62+KernelVersion: 3.19
63+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
64+Description: (RW) Used in conjunction with @addr_idx. Specifies the single
65+ address to stop tracing on, highly influenced by the
66+ configuration options of the corresponding access type register.
67+
68+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cntr_idx
69+Date: November 2014
70+KernelVersion: 3.19
71+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
72+Description: (RW) Specifies the counter to work on.
73+
74+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cntr_event
75+Date: November 2014
76+KernelVersion: 3.19
77+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
78+Description: (RW) Used in conjunction with cntr_idx, give access to the
79+ counter event register.
80+
81+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cntr_val
82+Date: November 2014
83+KernelVersion: 3.19
84+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
85+Description: (RW) Used in conjunction with cntr_idx, give access to the
86+ counter value register.
87+
88+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cntr_rld_val
89+Date: November 2014
90+KernelVersion: 3.19
91+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
92+Description: (RW) Used in conjunction with cntr_idx, give access to the
93+ counter reload value register.
94+
95+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/cntr_rld_event
96+Date: November 2014
97+KernelVersion: 3.19
98+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
99+Description: (RW) Used in conjunction with cntr_idx, give access to the
100+ counter reload event register.
101+
102+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/ctxid_idx
103+Date: November 2014
104+KernelVersion: 3.19
105+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
106+Description: (RW) Specifies the index of the context ID register to be
107+ selected.
108+
109+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/ctxid_mask
110+Date: November 2014
111+KernelVersion: 3.19
112+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
113+Description: (RW) Mask to apply to all the context ID comparator.
114+
115+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/ctxid_val
116+Date: November 2014
117+KernelVersion: 3.19
118+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
119+Description: (RW) Used with the ctxid_idx, specify with context ID to trigger
120+ on.
121+
122+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/enable_event
123+Date: November 2014
124+KernelVersion: 3.19
125+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
126+Description: (RW) Defines which event triggers a trace.
127+
128+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/etmsr
129+Date: November 2014
130+KernelVersion: 3.19
131+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
132+Description: (RW) Gives access to the ETM status register, which holds
133+ programming information and status on certains events.
134+
135+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/fifofull_level
136+Date: November 2014
137+KernelVersion: 3.19
138+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
139+Description: (RW) Number of byte left in the fifo before considering it full.
140+ Depending on the tracer's version, can also hold threshold for
141+ data suppression.
142+
143+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mode
144+Date: November 2014
145+KernelVersion: 3.19
146+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
147+Description: (RW) Interface with the driver's 'mode' field, controlling
148+ various aspect of the trace entity such as time stamping,
149+ context ID size and cycle accurate tracing. Driver specific
150+ and bound to change depending on the driver.
151+
152+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_addr_cmp
153+Date: November 2014
154+KernelVersion: 3.19
155+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
156+Description: (R) Provides the number of address comparators pairs accessible
157+ on a trace unit, as specified by bit 3:0 of register ETMCCR.
158+
159+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_cntr
160+Date: November 2014
161+KernelVersion: 3.19
162+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
163+Description: (R) Provides the number of counters accessible on a trace unit,
164+ as specified by bit 15:13 of register ETMCCR.
165+
166+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_ctxid_cmp
167+Date: November 2014
168+KernelVersion: 3.19
169+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
170+Description: (R) Provides the number of context ID comparator available on a
171+ trace unit, as specified by bit 25:24 of register ETMCCR.
172+
173+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/reset
174+Date: November 2014
175+KernelVersion: 3.19
176+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
177+Description: (W) Cancels all configuration on a trace unit and set it back
178+ to its boot configuration.
179+
180+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_12_event
181+Date: November 2014
182+KernelVersion: 3.19
183+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
184+Description: (RW) Defines the event that causes the sequencer to transition
185+ from state 1 to state 2.
186+
187+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_13_event
188+Date: November 2014
189+KernelVersion: 3.19
190+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
191+Description: (RW) Defines the event that causes the sequencer to transition
192+ from state 1 to state 3.
193+
194+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_21_event
195+Date: November 2014
196+KernelVersion: 3.19
197+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
198+Description: (RW) Defines the event that causes the sequencer to transition
199+ from state 2 to state 1.
200+
201+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_23_event
202+Date: November 2014
203+KernelVersion: 3.19
204+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
205+Description: (RW) Defines the event that causes the sequencer to transition
206+ from state 2 to state 3.
207+
208+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_31_event
209+Date: November 2014
210+KernelVersion: 3.19
211+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
212+Description: (RW) Defines the event that causes the sequencer to transition
213+ from state 3 to state 1.
214+
215+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_32_event
216+Date: November 2014
217+KernelVersion: 3.19
218+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
219+Description: (RW) Defines the event that causes the sequencer to transition
220+ from state 3 to state 2.
221+
222+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/curr_seq_state
223+Date: November 2014
224+KernelVersion: 3.19
225+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
226+Description: (R) Holds the current state of the sequencer.
227+
228+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/sync_freq
229+Date: November 2014
230+KernelVersion: 3.19
231+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
232+Description: (RW) Holds the trace synchronization frequency value - must be
233+ programmed with the various implementation behavior in mind.
234+
235+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/timestamp_event
236+Date: November 2014
237+KernelVersion: 3.19
238+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
239+Description: (RW) Defines an event that requests the insertion of a timestamp
240+ into the trace stream.
241+
242+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/traceid
243+Date: November 2014
244+KernelVersion: 3.19
245+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
246+Description: (RW) Holds the trace ID that will appear in the trace stream
247+ coming from this trace entity.
248+
249+What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/trigger_event
250+Date: November 2014
251+KernelVersion: 3.19
252+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
253+Description: (RW) Define the event that controls the trigger.
Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel+12−0
@@ -0,0 +1,12 @@
1+What: /sys/bus/coresight/devices/<memory_map>.funnel/funnel_ctrl
2+Date: November 2014
3+KernelVersion: 3.19
4+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
5+Description: (RW) Enables the slave ports and defines the hold time of the
6+ slave ports.
7+
8+What: /sys/bus/coresight/devices/<memory_map>.funnel/priority
9+Date: November 2014
10+KernelVersion: 3.19
11+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
12+Description: (RW) Defines input port priority order.
Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc+8−0
@@ -0,0 +1,8 @@
1+What: /sys/bus/coresight/devices/<memory_map>.tmc/trigger_cntr
2+Date: November 2014
3+KernelVersion: 3.19
4+Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
5+Description: (RW) Disables write access to the Trace RAM by stopping the
6+ formatter after a defined number of words have been stored
7+ following the trigger event. Additional interface for this
8+ driver are expected to be added as it matures.
Documentation/ABI/testing/sysfs-bus-event_source-devices-events+49−562
@@ -27,575 +27,62 @@ Description: Generic performance monitoring events · 26 unmodified lines
2727 "basename".
2828
2929
30−What: /sys/devices/cpu/events/PM_1PLUS_PPC_CMPL
31− /sys/devices/cpu/events/PM_BRU_FIN
32− /sys/devices/cpu/events/PM_BR_MPRED
33− /sys/devices/cpu/events/PM_CMPLU_STALL
34− /sys/devices/cpu/events/PM_CMPLU_STALL_BRU
35− /sys/devices/cpu/events/PM_CMPLU_STALL_DCACHE_MISS
36− /sys/devices/cpu/events/PM_CMPLU_STALL_DFU
37− /sys/devices/cpu/events/PM_CMPLU_STALL_DIV
38− /sys/devices/cpu/events/PM_CMPLU_STALL_ERAT_MISS
39− /sys/devices/cpu/events/PM_CMPLU_STALL_FXU
40− /sys/devices/cpu/events/PM_CMPLU_STALL_IFU
41− /sys/devices/cpu/events/PM_CMPLU_STALL_LSU
42− /sys/devices/cpu/events/PM_CMPLU_STALL_REJECT
43− /sys/devices/cpu/events/PM_CMPLU_STALL_SCALAR
44− /sys/devices/cpu/events/PM_CMPLU_STALL_SCALAR_LONG
45− /sys/devices/cpu/events/PM_CMPLU_STALL_STORE
46− /sys/devices/cpu/events/PM_CMPLU_STALL_THRD
47− /sys/devices/cpu/events/PM_CMPLU_STALL_VECTOR
48− /sys/devices/cpu/events/PM_CMPLU_STALL_VECTOR_LONG
49− /sys/devices/cpu/events/PM_CYC
50− /sys/devices/cpu/events/PM_GCT_NOSLOT_BR_MPRED
51− /sys/devices/cpu/events/PM_GCT_NOSLOT_BR_MPRED_IC_MISS
52− /sys/devices/cpu/events/PM_GCT_NOSLOT_CYC
53− /sys/devices/cpu/events/PM_GCT_NOSLOT_IC_MISS
54− /sys/devices/cpu/events/PM_GRP_CMPL
55− /sys/devices/cpu/events/PM_INST_CMPL
56− /sys/devices/cpu/events/PM_LD_MISS_L1
57− /sys/devices/cpu/events/PM_LD_REF_L1
58− /sys/devices/cpu/events/PM_RUN_CYC
59− /sys/devices/cpu/events/PM_RUN_INST_CMPL
60− /sys/devices/cpu/events/PM_IC_DEMAND_L2_BR_ALL
61− /sys/devices/cpu/events/PM_GCT_UTIL_7_TO_10_SLOTS
62− /sys/devices/cpu/events/PM_PMC2_SAVED
63− /sys/devices/cpu/events/PM_VSU0_16FLOP
64− /sys/devices/cpu/events/PM_MRK_LSU_DERAT_MISS
65− /sys/devices/cpu/events/PM_MRK_ST_CMPL
66− /sys/devices/cpu/events/PM_NEST_PAIR3_ADD
67− /sys/devices/cpu/events/PM_L2_ST_DISP
68− /sys/devices/cpu/events/PM_L2_CASTOUT_MOD
69− /sys/devices/cpu/events/PM_ISEG
70− /sys/devices/cpu/events/PM_MRK_INST_TIMEO
71− /sys/devices/cpu/events/PM_L2_RCST_DISP_FAIL_ADDR
72− /sys/devices/cpu/events/PM_LSU1_DC_PREF_STREAM_CONFIRM
73− /sys/devices/cpu/events/PM_IERAT_WR_64K
74− /sys/devices/cpu/events/PM_MRK_DTLB_MISS_16M
75− /sys/devices/cpu/events/PM_IERAT_MISS
76− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_LMEM
77− /sys/devices/cpu/events/PM_FLOP
78− /sys/devices/cpu/events/PM_THRD_PRIO_4_5_CYC
79− /sys/devices/cpu/events/PM_BR_PRED_TA
80− /sys/devices/cpu/events/PM_EXT_INT
81− /sys/devices/cpu/events/PM_VSU_FSQRT_FDIV
82− /sys/devices/cpu/events/PM_MRK_LD_MISS_EXPOSED_CYC
83− /sys/devices/cpu/events/PM_LSU1_LDF
84− /sys/devices/cpu/events/PM_IC_WRITE_ALL
85− /sys/devices/cpu/events/PM_LSU0_SRQ_STFWD
86− /sys/devices/cpu/events/PM_PTEG_FROM_RL2L3_MOD
87− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L31_SHR
88− /sys/devices/cpu/events/PM_DATA_FROM_L21_MOD
89− /sys/devices/cpu/events/PM_VSU1_SCAL_DOUBLE_ISSUED
90− /sys/devices/cpu/events/PM_VSU0_8FLOP
91− /sys/devices/cpu/events/PM_POWER_EVENT1
92− /sys/devices/cpu/events/PM_DISP_CLB_HELD_BAL
93− /sys/devices/cpu/events/PM_VSU1_2FLOP
94− /sys/devices/cpu/events/PM_LWSYNC_HELD
95− /sys/devices/cpu/events/PM_PTEG_FROM_DL2L3_SHR
96− /sys/devices/cpu/events/PM_INST_FROM_L21_MOD
97− /sys/devices/cpu/events/PM_IERAT_XLATE_WR_16MPLUS
98− /sys/devices/cpu/events/PM_IC_REQ_ALL
99− /sys/devices/cpu/events/PM_DSLB_MISS
100− /sys/devices/cpu/events/PM_L3_MISS
101− /sys/devices/cpu/events/PM_LSU0_L1_PREF
102− /sys/devices/cpu/events/PM_VSU_SCALAR_SINGLE_ISSUED
103− /sys/devices/cpu/events/PM_LSU1_DC_PREF_STREAM_CONFIRM_STRIDE
104− /sys/devices/cpu/events/PM_L2_INST
105− /sys/devices/cpu/events/PM_VSU0_FRSP
106− /sys/devices/cpu/events/PM_FLUSH_DISP
107− /sys/devices/cpu/events/PM_PTEG_FROM_L2MISS
108− /sys/devices/cpu/events/PM_VSU1_DQ_ISSUED
109− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DMEM
110− /sys/devices/cpu/events/PM_LSU_FLUSH_ULD
111− /sys/devices/cpu/events/PM_PTEG_FROM_LMEM
112− /sys/devices/cpu/events/PM_MRK_DERAT_MISS_16M
113− /sys/devices/cpu/events/PM_THRD_ALL_RUN_CYC
114− /sys/devices/cpu/events/PM_MEM0_PREFETCH_DISP
115− /sys/devices/cpu/events/PM_MRK_STALL_CMPLU_CYC_COUNT
116− /sys/devices/cpu/events/PM_DATA_FROM_DL2L3_MOD
117− /sys/devices/cpu/events/PM_VSU_FRSP
118− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L21_MOD
119− /sys/devices/cpu/events/PM_PMC1_OVERFLOW
120− /sys/devices/cpu/events/PM_VSU0_SINGLE
121− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L3MISS
122− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L31_SHR
123− /sys/devices/cpu/events/PM_VSU0_VECTOR_SP_ISSUED
124− /sys/devices/cpu/events/PM_VSU1_FEST
125− /sys/devices/cpu/events/PM_MRK_INST_DISP
126− /sys/devices/cpu/events/PM_VSU0_COMPLEX_ISSUED
127− /sys/devices/cpu/events/PM_LSU1_FLUSH_UST
128− /sys/devices/cpu/events/PM_FXU_IDLE
129− /sys/devices/cpu/events/PM_LSU0_FLUSH_ULD
130− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DL2L3_MOD
131− /sys/devices/cpu/events/PM_LSU_LMQ_SRQ_EMPTY_ALL_CYC
132− /sys/devices/cpu/events/PM_LSU1_REJECT_LMQ_FULL
133− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L21_MOD
134− /sys/devices/cpu/events/PM_INST_FROM_RL2L3_MOD
135− /sys/devices/cpu/events/PM_SHL_CREATED
136− /sys/devices/cpu/events/PM_L2_ST_HIT
137− /sys/devices/cpu/events/PM_DATA_FROM_DMEM
138− /sys/devices/cpu/events/PM_L3_LD_MISS
139− /sys/devices/cpu/events/PM_FXU1_BUSY_FXU0_IDLE
140− /sys/devices/cpu/events/PM_DISP_CLB_HELD_RES
141− /sys/devices/cpu/events/PM_L2_SN_SX_I_DONE
142− /sys/devices/cpu/events/PM_STCX_CMPL
143− /sys/devices/cpu/events/PM_VSU0_2FLOP
144− /sys/devices/cpu/events/PM_L3_PREF_MISS
145− /sys/devices/cpu/events/PM_LSU_SRQ_SYNC_CYC
146− /sys/devices/cpu/events/PM_LSU_REJECT_ERAT_MISS
147− /sys/devices/cpu/events/PM_L1_ICACHE_MISS
148− /sys/devices/cpu/events/PM_LSU1_FLUSH_SRQ
149− /sys/devices/cpu/events/PM_LD_REF_L1_LSU0
150− /sys/devices/cpu/events/PM_VSU0_FEST
151− /sys/devices/cpu/events/PM_VSU_VECTOR_SINGLE_ISSUED
152− /sys/devices/cpu/events/PM_FREQ_UP
153− /sys/devices/cpu/events/PM_DATA_FROM_LMEM
154− /sys/devices/cpu/events/PM_LSU1_LDX
155− /sys/devices/cpu/events/PM_PMC3_OVERFLOW
156− /sys/devices/cpu/events/PM_MRK_BR_MPRED
157− /sys/devices/cpu/events/PM_SHL_MATCH
158− /sys/devices/cpu/events/PM_MRK_BR_TAKEN
159− /sys/devices/cpu/events/PM_ISLB_MISS
160− /sys/devices/cpu/events/PM_DISP_HELD_THERMAL
161− /sys/devices/cpu/events/PM_INST_PTEG_FROM_RL2L3_SHR
162− /sys/devices/cpu/events/PM_LSU1_SRQ_STFWD
163− /sys/devices/cpu/events/PM_PTEG_FROM_DMEM
164− /sys/devices/cpu/events/PM_VSU_2FLOP
165− /sys/devices/cpu/events/PM_GCT_FULL_CYC
166− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L3_CYC
167− /sys/devices/cpu/events/PM_LSU_SRQ_S0_ALLOC
168− /sys/devices/cpu/events/PM_MRK_DERAT_MISS_4K
169− /sys/devices/cpu/events/PM_BR_MPRED_TA
170− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L2MISS
171− /sys/devices/cpu/events/PM_DPU_HELD_POWER
172− /sys/devices/cpu/events/PM_MRK_VSU_FIN
173− /sys/devices/cpu/events/PM_LSU_SRQ_S0_VALID
174− /sys/devices/cpu/events/PM_GCT_EMPTY_CYC
175− /sys/devices/cpu/events/PM_IOPS_DISP
176− /sys/devices/cpu/events/PM_RUN_SPURR
177− /sys/devices/cpu/events/PM_PTEG_FROM_L21_MOD
178− /sys/devices/cpu/events/PM_VSU0_1FLOP
179− /sys/devices/cpu/events/PM_SNOOP_TLBIE
180− /sys/devices/cpu/events/PM_DATA_FROM_L3MISS
181− /sys/devices/cpu/events/PM_VSU_SINGLE
182− /sys/devices/cpu/events/PM_DTLB_MISS_16G
183− /sys/devices/cpu/events/PM_FLUSH
184− /sys/devices/cpu/events/PM_L2_LD_HIT
185− /sys/devices/cpu/events/PM_NEST_PAIR2_AND
186− /sys/devices/cpu/events/PM_VSU1_1FLOP
187− /sys/devices/cpu/events/PM_IC_PREF_REQ
188− /sys/devices/cpu/events/PM_L3_LD_HIT
189− /sys/devices/cpu/events/PM_DISP_HELD
190− /sys/devices/cpu/events/PM_L2_LD
191− /sys/devices/cpu/events/PM_LSU_FLUSH_SRQ
192− /sys/devices/cpu/events/PM_BC_PLUS_8_CONV
193− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L31_MOD_CYC
194− /sys/devices/cpu/events/PM_L2_RCST_BUSY_RC_FULL
195− /sys/devices/cpu/events/PM_TB_BIT_TRANS
196− /sys/devices/cpu/events/PM_THERMAL_MAX
197− /sys/devices/cpu/events/PM_LSU1_FLUSH_ULD
198− /sys/devices/cpu/events/PM_LSU1_REJECT_LHS
199− /sys/devices/cpu/events/PM_LSU_LRQ_S0_ALLOC
200− /sys/devices/cpu/events/PM_L3_CO_L31
201− /sys/devices/cpu/events/PM_POWER_EVENT4
202− /sys/devices/cpu/events/PM_DATA_FROM_L31_SHR
203− /sys/devices/cpu/events/PM_BR_UNCOND
204− /sys/devices/cpu/events/PM_LSU1_DC_PREF_STREAM_ALLOC
205− /sys/devices/cpu/events/PM_PMC4_REWIND
206− /sys/devices/cpu/events/PM_L2_RCLD_DISP
207− /sys/devices/cpu/events/PM_THRD_PRIO_2_3_CYC
208− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L2MISS
209− /sys/devices/cpu/events/PM_IC_DEMAND_L2_BHT_REDIRECT
210− /sys/devices/cpu/events/PM_DATA_FROM_L31_SHR
211− /sys/devices/cpu/events/PM_IC_PREF_CANCEL_L2
212− /sys/devices/cpu/events/PM_MRK_FIN_STALL_CYC_COUNT
213− /sys/devices/cpu/events/PM_BR_PRED_CCACHE
214− /sys/devices/cpu/events/PM_GCT_UTIL_1_TO_2_SLOTS
215− /sys/devices/cpu/events/PM_MRK_ST_CMPL_INT
216− /sys/devices/cpu/events/PM_LSU_TWO_TABLEWALK_CYC
217− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L3MISS
218− /sys/devices/cpu/events/PM_LSU_SET_MPRED
219− /sys/devices/cpu/events/PM_FLUSH_DISP_TLBIE
220− /sys/devices/cpu/events/PM_VSU1_FCONV
221− /sys/devices/cpu/events/PM_DERAT_MISS_16G
222− /sys/devices/cpu/events/PM_INST_FROM_LMEM
223− /sys/devices/cpu/events/PM_IC_DEMAND_L2_BR_REDIRECT
224− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L2
225− /sys/devices/cpu/events/PM_PTEG_FROM_L2
226− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L21_SHR_CYC
227− /sys/devices/cpu/events/PM_MRK_DTLB_MISS_4K
228− /sys/devices/cpu/events/PM_VSU0_FPSCR
229− /sys/devices/cpu/events/PM_VSU1_VECT_DOUBLE_ISSUED
230− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_RL2L3_MOD
231− /sys/devices/cpu/events/PM_MEM0_RQ_DISP
232− /sys/devices/cpu/events/PM_L2_LD_MISS
233− /sys/devices/cpu/events/PM_VMX_RESULT_SAT_1
234− /sys/devices/cpu/events/PM_L1_PREF
235− /sys/devices/cpu/events/PM_MRK_DATA_FROM_LMEM_CYC
236− /sys/devices/cpu/events/PM_GRP_IC_MISS_NONSPEC
237− /sys/devices/cpu/events/PM_PB_NODE_PUMP
238− /sys/devices/cpu/events/PM_SHL_MERGED
239− /sys/devices/cpu/events/PM_NEST_PAIR1_ADD
240− /sys/devices/cpu/events/PM_DATA_FROM_L3
241− /sys/devices/cpu/events/PM_LSU_FLUSH
242− /sys/devices/cpu/events/PM_LSU_SRQ_SYNC_COUNT
243− /sys/devices/cpu/events/PM_PMC2_OVERFLOW
244− /sys/devices/cpu/events/PM_LSU_LDF
245− /sys/devices/cpu/events/PM_POWER_EVENT3
246− /sys/devices/cpu/events/PM_DISP_WT
247− /sys/devices/cpu/events/PM_IC_BANK_CONFLICT
248− /sys/devices/cpu/events/PM_BR_MPRED_CR_TA
249− /sys/devices/cpu/events/PM_L2_INST_MISS
250− /sys/devices/cpu/events/PM_NEST_PAIR2_ADD
251− /sys/devices/cpu/events/PM_MRK_LSU_FLUSH
252− /sys/devices/cpu/events/PM_L2_LDST
253− /sys/devices/cpu/events/PM_INST_FROM_L31_SHR
254− /sys/devices/cpu/events/PM_VSU0_FIN
255− /sys/devices/cpu/events/PM_VSU1_FCONV
256− /sys/devices/cpu/events/PM_INST_FROM_RMEM
257− /sys/devices/cpu/events/PM_DISP_CLB_HELD_TLBIE
258− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DMEM_CYC
259− /sys/devices/cpu/events/PM_BR_PRED_CR
260− /sys/devices/cpu/events/PM_LSU_REJECT
261− /sys/devices/cpu/events/PM_GCT_UTIL_3_TO_6_SLOTS
262− /sys/devices/cpu/events/PM_CMPLU_STALL_END_GCT_NOSLOT
263− /sys/devices/cpu/events/PM_LSU0_REJECT_LMQ_FULL
264− /sys/devices/cpu/events/PM_VSU_FEST
265− /sys/devices/cpu/events/PM_NEST_PAIR0_AND
266− /sys/devices/cpu/events/PM_PTEG_FROM_L3
267− /sys/devices/cpu/events/PM_POWER_EVENT2
268− /sys/devices/cpu/events/PM_IC_PREF_CANCEL_PAGE
269− /sys/devices/cpu/events/PM_VSU0_FSQRT_FDIV
270− /sys/devices/cpu/events/PM_MRK_GRP_CMPL
271− /sys/devices/cpu/events/PM_VSU0_SCAL_DOUBLE_ISSUED
272− /sys/devices/cpu/events/PM_GRP_DISP
273− /sys/devices/cpu/events/PM_LSU0_LDX
274− /sys/devices/cpu/events/PM_DATA_FROM_L2
275− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RL2L3_MOD
276− /sys/devices/cpu/events/PM_VSU0_VECT_DOUBLE_ISSUED
277− /sys/devices/cpu/events/PM_VSU1_2FLOP_DOUBLE
278− /sys/devices/cpu/events/PM_THRD_PRIO_6_7_CYC
279− /sys/devices/cpu/events/PM_BC_PLUS_8_RSLV_TAKEN
280− /sys/devices/cpu/events/PM_BR_MPRED_CR
281− /sys/devices/cpu/events/PM_L3_CO_MEM
282− /sys/devices/cpu/events/PM_DATA_FROM_RL2L3_MOD
283− /sys/devices/cpu/events/PM_LSU_SRQ_FULL_CYC
284− /sys/devices/cpu/events/PM_TABLEWALK_CYC
285− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_RMEM
286− /sys/devices/cpu/events/PM_LSU_SRQ_STFWD
287− /sys/devices/cpu/events/PM_INST_PTEG_FROM_RMEM
288− /sys/devices/cpu/events/PM_FXU0_FIN
289− /sys/devices/cpu/events/PM_LSU1_L1_SW_PREF
290− /sys/devices/cpu/events/PM_PTEG_FROM_L31_MOD
291− /sys/devices/cpu/events/PM_PMC5_OVERFLOW
292− /sys/devices/cpu/events/PM_LD_REF_L1_LSU1
293− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L21_SHR
294− /sys/devices/cpu/events/PM_DATA_FROM_RMEM
295− /sys/devices/cpu/events/PM_VSU0_SCAL_SINGLE_ISSUED
296− /sys/devices/cpu/events/PM_BR_MPRED_LSTACK
297− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RL2L3_MOD_CYC
298− /sys/devices/cpu/events/PM_LSU0_FLUSH_UST
299− /sys/devices/cpu/events/PM_LSU_NCST
300− /sys/devices/cpu/events/PM_BR_TAKEN
301− /sys/devices/cpu/events/PM_INST_PTEG_FROM_LMEM
302− /sys/devices/cpu/events/PM_DTLB_MISS_4K
303− /sys/devices/cpu/events/PM_PMC4_SAVED
304− /sys/devices/cpu/events/PM_VSU1_PERMUTE_ISSUED
305− /sys/devices/cpu/events/PM_SLB_MISS
306− /sys/devices/cpu/events/PM_LSU1_FLUSH_LRQ
307− /sys/devices/cpu/events/PM_DTLB_MISS
308− /sys/devices/cpu/events/PM_VSU1_FRSP
309− /sys/devices/cpu/events/PM_VSU_VECTOR_DOUBLE_ISSUED
310− /sys/devices/cpu/events/PM_L2_CASTOUT_SHR
311− /sys/devices/cpu/events/PM_DATA_FROM_DL2L3_SHR
312− /sys/devices/cpu/events/PM_VSU1_STF
313− /sys/devices/cpu/events/PM_ST_FIN
314− /sys/devices/cpu/events/PM_PTEG_FROM_L21_SHR
315− /sys/devices/cpu/events/PM_L2_LOC_GUESS_WRONG
316− /sys/devices/cpu/events/PM_MRK_STCX_FAIL
317− /sys/devices/cpu/events/PM_LSU0_REJECT_LHS
318− /sys/devices/cpu/events/PM_IC_PREF_CANCEL_HIT
319− /sys/devices/cpu/events/PM_L3_PREF_BUSY
320− /sys/devices/cpu/events/PM_MRK_BRU_FIN
321− /sys/devices/cpu/events/PM_LSU1_NCLD
322− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L31_MOD
323− /sys/devices/cpu/events/PM_LSU_NCLD
324− /sys/devices/cpu/events/PM_LSU_LDX
325− /sys/devices/cpu/events/PM_L2_LOC_GUESS_CORRECT
326− /sys/devices/cpu/events/PM_THRESH_TIMEO
327− /sys/devices/cpu/events/PM_L3_PREF_ST
328− /sys/devices/cpu/events/PM_DISP_CLB_HELD_SYNC
329− /sys/devices/cpu/events/PM_VSU_SIMPLE_ISSUED
330− /sys/devices/cpu/events/PM_VSU1_SINGLE
331− /sys/devices/cpu/events/PM_DATA_TABLEWALK_CYC
332− /sys/devices/cpu/events/PM_L2_RC_ST_DONE
333− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L21_MOD
334− /sys/devices/cpu/events/PM_LARX_LSU1
335− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RMEM
336− /sys/devices/cpu/events/PM_DISP_CLB_HELD
337− /sys/devices/cpu/events/PM_DERAT_MISS_4K
338− /sys/devices/cpu/events/PM_L2_RCLD_DISP_FAIL_ADDR
339− /sys/devices/cpu/events/PM_SEG_EXCEPTION
340− /sys/devices/cpu/events/PM_FLUSH_DISP_SB
341− /sys/devices/cpu/events/PM_L2_DC_INV
342− /sys/devices/cpu/events/PM_PTEG_FROM_DL2L3_MOD
343− /sys/devices/cpu/events/PM_DSEG
344− /sys/devices/cpu/events/PM_BR_PRED_LSTACK
345− /sys/devices/cpu/events/PM_VSU0_STF
346− /sys/devices/cpu/events/PM_LSU_FX_FIN
347− /sys/devices/cpu/events/PM_DERAT_MISS_16M
348− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_DL2L3_MOD
349− /sys/devices/cpu/events/PM_GCT_UTIL_11_PLUS_SLOTS
350− /sys/devices/cpu/events/PM_INST_FROM_L3
351− /sys/devices/cpu/events/PM_MRK_IFU_FIN
352− /sys/devices/cpu/events/PM_ITLB_MISS
353− /sys/devices/cpu/events/PM_VSU_STF
354− /sys/devices/cpu/events/PM_LSU_FLUSH_UST
355− /sys/devices/cpu/events/PM_L2_LDST_MISS
356− /sys/devices/cpu/events/PM_FXU1_FIN
357− /sys/devices/cpu/events/PM_SHL_DEALLOCATED
358− /sys/devices/cpu/events/PM_L2_SN_M_WR_DONE
359− /sys/devices/cpu/events/PM_LSU_REJECT_SET_MPRED
360− /sys/devices/cpu/events/PM_L3_PREF_LD
361− /sys/devices/cpu/events/PM_L2_SN_M_RD_DONE
362− /sys/devices/cpu/events/PM_MRK_DERAT_MISS_16G
363− /sys/devices/cpu/events/PM_VSU_FCONV
364− /sys/devices/cpu/events/PM_ANY_THRD_RUN_CYC
365− /sys/devices/cpu/events/PM_LSU_LMQ_FULL_CYC
366− /sys/devices/cpu/events/PM_MRK_LSU_REJECT_LHS
367− /sys/devices/cpu/events/PM_MRK_LD_MISS_L1_CYC
368− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L2_CYC
369− /sys/devices/cpu/events/PM_INST_IMC_MATCH_DISP
370− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RMEM_CYC
371− /sys/devices/cpu/events/PM_VSU0_SIMPLE_ISSUED
372− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_RL2L3_SHR
373− /sys/devices/cpu/events/PM_VSU_FMA_DOUBLE
374− /sys/devices/cpu/events/PM_VSU_4FLOP
375− /sys/devices/cpu/events/PM_VSU1_FIN
376− /sys/devices/cpu/events/PM_NEST_PAIR1_AND
377− /sys/devices/cpu/events/PM_INST_PTEG_FROM_RL2L3_MOD
378− /sys/devices/cpu/events/PM_PTEG_FROM_RMEM
379− /sys/devices/cpu/events/PM_LSU_LRQ_S0_VALID
380− /sys/devices/cpu/events/PM_LSU0_LDF
381− /sys/devices/cpu/events/PM_FLUSH_COMPLETION
382− /sys/devices/cpu/events/PM_ST_MISS_L1
383− /sys/devices/cpu/events/PM_L2_NODE_PUMP
384− /sys/devices/cpu/events/PM_INST_FROM_DL2L3_SHR
385− /sys/devices/cpu/events/PM_MRK_STALL_CMPLU_CYC
386− /sys/devices/cpu/events/PM_VSU1_DENORM
387− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L31_SHR_CYC
388− /sys/devices/cpu/events/PM_NEST_PAIR0_ADD
389− /sys/devices/cpu/events/PM_INST_FROM_L3MISS
390− /sys/devices/cpu/events/PM_EE_OFF_EXT_INT
391− /sys/devices/cpu/events/PM_INST_PTEG_FROM_DMEM
392− /sys/devices/cpu/events/PM_INST_FROM_DL2L3_MOD
393− /sys/devices/cpu/events/PM_PMC6_OVERFLOW
394− /sys/devices/cpu/events/PM_VSU_2FLOP_DOUBLE
395− /sys/devices/cpu/events/PM_TLB_MISS
396− /sys/devices/cpu/events/PM_FXU_BUSY
397− /sys/devices/cpu/events/PM_L2_RCLD_DISP_FAIL_OTHER
398− /sys/devices/cpu/events/PM_LSU_REJECT_LMQ_FULL
399− /sys/devices/cpu/events/PM_IC_RELOAD_SHR
400− /sys/devices/cpu/events/PM_GRP_MRK
401− /sys/devices/cpu/events/PM_MRK_ST_NEST
402− /sys/devices/cpu/events/PM_VSU1_FSQRT_FDIV
403− /sys/devices/cpu/events/PM_LSU0_FLUSH_LRQ
404− /sys/devices/cpu/events/PM_LARX_LSU0
405− /sys/devices/cpu/events/PM_IBUF_FULL_CYC
406− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DL2L3_SHR_CYC
407− /sys/devices/cpu/events/PM_LSU_DC_PREF_STREAM_ALLOC
408− /sys/devices/cpu/events/PM_GRP_MRK_CYC
409− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RL2L3_SHR_CYC
410− /sys/devices/cpu/events/PM_L2_GLOB_GUESS_CORRECT
411− /sys/devices/cpu/events/PM_LSU_REJECT_LHS
412− /sys/devices/cpu/events/PM_MRK_DATA_FROM_LMEM
413− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L3
414− /sys/devices/cpu/events/PM_FREQ_DOWN
415− /sys/devices/cpu/events/PM_PB_RETRY_NODE_PUMP
416− /sys/devices/cpu/events/PM_INST_FROM_RL2L3_SHR
417− /sys/devices/cpu/events/PM_MRK_INST_ISSUED
418− /sys/devices/cpu/events/PM_PTEG_FROM_L3MISS
419− /sys/devices/cpu/events/PM_RUN_PURR
420− /sys/devices/cpu/events/PM_MRK_GRP_IC_MISS
421− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L3
422− /sys/devices/cpu/events/PM_PTEG_FROM_RL2L3_SHR
423− /sys/devices/cpu/events/PM_LSU_FLUSH_LRQ
424− /sys/devices/cpu/events/PM_MRK_DERAT_MISS_64K
425− /sys/devices/cpu/events/PM_INST_PTEG_FROM_DL2L3_MOD
426− /sys/devices/cpu/events/PM_L2_ST_MISS
427− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L21_SHR
428− /sys/devices/cpu/events/PM_LWSYNC
429− /sys/devices/cpu/events/PM_LSU0_DC_PREF_STREAM_CONFIRM_STRIDE
430− /sys/devices/cpu/events/PM_MRK_LSU_FLUSH_LRQ
431− /sys/devices/cpu/events/PM_INST_IMC_MATCH_CMPL
432− /sys/devices/cpu/events/PM_NEST_PAIR3_AND
433− /sys/devices/cpu/events/PM_PB_RETRY_SYS_PUMP
434− /sys/devices/cpu/events/PM_MRK_INST_FIN
435− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_DL2L3_SHR
436− /sys/devices/cpu/events/PM_INST_FROM_L31_MOD
437− /sys/devices/cpu/events/PM_MRK_DTLB_MISS_64K
438− /sys/devices/cpu/events/PM_LSU_FIN
439− /sys/devices/cpu/events/PM_MRK_LSU_REJECT
440− /sys/devices/cpu/events/PM_L2_CO_FAIL_BUSY
441− /sys/devices/cpu/events/PM_MEM0_WQ_DISP
442− /sys/devices/cpu/events/PM_DATA_FROM_L31_MOD
443− /sys/devices/cpu/events/PM_THERMAL_WARN
444− /sys/devices/cpu/events/PM_VSU0_4FLOP
445− /sys/devices/cpu/events/PM_BR_MPRED_CCACHE
446− /sys/devices/cpu/events/PM_L1_DEMAND_WRITE
447− /sys/devices/cpu/events/PM_FLUSH_BR_MPRED
448− /sys/devices/cpu/events/PM_MRK_DTLB_MISS_16G
449− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_DMEM
450− /sys/devices/cpu/events/PM_L2_RCST_DISP
451− /sys/devices/cpu/events/PM_LSU_PARTIAL_CDF
452− /sys/devices/cpu/events/PM_DISP_CLB_HELD_SB
453− /sys/devices/cpu/events/PM_VSU0_FMA_DOUBLE
454− /sys/devices/cpu/events/PM_FXU0_BUSY_FXU1_IDLE
455− /sys/devices/cpu/events/PM_IC_DEMAND_CYC
456− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L21_SHR
457− /sys/devices/cpu/events/PM_MRK_LSU_FLUSH_UST
458− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L3MISS
459− /sys/devices/cpu/events/PM_VSU_DENORM
460− /sys/devices/cpu/events/PM_MRK_LSU_PARTIAL_CDF
461− /sys/devices/cpu/events/PM_INST_FROM_L21_SHR
462− /sys/devices/cpu/events/PM_IC_PREF_WRITE
463− /sys/devices/cpu/events/PM_BR_PRED
464− /sys/devices/cpu/events/PM_INST_FROM_DMEM
465− /sys/devices/cpu/events/PM_IC_PREF_CANCEL_ALL
466− /sys/devices/cpu/events/PM_LSU_DC_PREF_STREAM_CONFIRM
467− /sys/devices/cpu/events/PM_MRK_LSU_FLUSH_SRQ
468− /sys/devices/cpu/events/PM_MRK_FIN_STALL_CYC
469− /sys/devices/cpu/events/PM_L2_RCST_DISP_FAIL_OTHER
470− /sys/devices/cpu/events/PM_VSU1_DD_ISSUED
471− /sys/devices/cpu/events/PM_PTEG_FROM_L31_SHR
472− /sys/devices/cpu/events/PM_DATA_FROM_L21_SHR
473− /sys/devices/cpu/events/PM_LSU0_NCLD
474− /sys/devices/cpu/events/PM_VSU1_4FLOP
475− /sys/devices/cpu/events/PM_VSU1_8FLOP
476− /sys/devices/cpu/events/PM_VSU_8FLOP
477− /sys/devices/cpu/events/PM_LSU_LMQ_SRQ_EMPTY_CYC
478− /sys/devices/cpu/events/PM_DTLB_MISS_64K
479− /sys/devices/cpu/events/PM_THRD_CONC_RUN_INST
480− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L2
481− /sys/devices/cpu/events/PM_PB_SYS_PUMP
482− /sys/devices/cpu/events/PM_VSU_FIN
483− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L31_MOD
484− /sys/devices/cpu/events/PM_THRD_PRIO_0_1_CYC
485− /sys/devices/cpu/events/PM_DERAT_MISS_64K
486− /sys/devices/cpu/events/PM_PMC2_REWIND
487− /sys/devices/cpu/events/PM_INST_FROM_L2
488− /sys/devices/cpu/events/PM_GRP_BR_MPRED_NONSPEC
489− /sys/devices/cpu/events/PM_INST_DISP
490− /sys/devices/cpu/events/PM_MEM0_RD_CANCEL_TOTAL
491− /sys/devices/cpu/events/PM_LSU0_DC_PREF_STREAM_CONFIRM
492− /sys/devices/cpu/events/PM_L1_DCACHE_RELOAD_VALID
493− /sys/devices/cpu/events/PM_VSU_SCALAR_DOUBLE_ISSUED
494− /sys/devices/cpu/events/PM_L3_PREF_HIT
495− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L31_MOD
496− /sys/devices/cpu/events/PM_MRK_FXU_FIN
497− /sys/devices/cpu/events/PM_PMC4_OVERFLOW
498− /sys/devices/cpu/events/PM_MRK_PTEG_FROM_L3
499− /sys/devices/cpu/events/PM_LSU0_LMQ_LHR_MERGE
500− /sys/devices/cpu/events/PM_BTAC_HIT
501− /sys/devices/cpu/events/PM_L3_RD_BUSY
502− /sys/devices/cpu/events/PM_LSU0_L1_SW_PREF
503− /sys/devices/cpu/events/PM_INST_FROM_L2MISS
504− /sys/devices/cpu/events/PM_LSU0_DC_PREF_STREAM_ALLOC
505− /sys/devices/cpu/events/PM_L2_ST
506− /sys/devices/cpu/events/PM_VSU0_DENORM
507− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DL2L3_SHR
508− /sys/devices/cpu/events/PM_BR_PRED_CR_TA
509− /sys/devices/cpu/events/PM_VSU0_FCONV
510− /sys/devices/cpu/events/PM_MRK_LSU_FLUSH_ULD
511− /sys/devices/cpu/events/PM_BTAC_MISS
512− /sys/devices/cpu/events/PM_MRK_LD_MISS_EXPOSED_CYC_COUNT
513− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L2
514− /sys/devices/cpu/events/PM_LSU_DCACHE_RELOAD_VALID
515− /sys/devices/cpu/events/PM_VSU_FMA
516− /sys/devices/cpu/events/PM_LSU0_FLUSH_SRQ
517− /sys/devices/cpu/events/PM_LSU1_L1_PREF
518− /sys/devices/cpu/events/PM_IOPS_CMPL
519− /sys/devices/cpu/events/PM_L2_SYS_PUMP
520− /sys/devices/cpu/events/PM_L2_RCLD_BUSY_RC_FULL
521− /sys/devices/cpu/events/PM_LSU_LMQ_S0_ALLOC
522− /sys/devices/cpu/events/PM_FLUSH_DISP_SYNC
523− /sys/devices/cpu/events/PM_MRK_DATA_FROM_DL2L3_MOD_CYC
524− /sys/devices/cpu/events/PM_L2_IC_INV
525− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L21_MOD_CYC
526− /sys/devices/cpu/events/PM_L3_PREF_LDST
527− /sys/devices/cpu/events/PM_LSU_SRQ_EMPTY_CYC
528− /sys/devices/cpu/events/PM_LSU_LMQ_S0_VALID
529− /sys/devices/cpu/events/PM_FLUSH_PARTIAL
530− /sys/devices/cpu/events/PM_VSU1_FMA_DOUBLE
531− /sys/devices/cpu/events/PM_1PLUS_PPC_DISP
532− /sys/devices/cpu/events/PM_DATA_FROM_L2MISS
533− /sys/devices/cpu/events/PM_SUSPENDED
534− /sys/devices/cpu/events/PM_VSU0_FMA
535− /sys/devices/cpu/events/PM_STCX_FAIL
536− /sys/devices/cpu/events/PM_VSU0_FSQRT_FDIV_DOUBLE
537− /sys/devices/cpu/events/PM_DC_PREF_DST
538− /sys/devices/cpu/events/PM_VSU1_SCAL_SINGLE_ISSUED
539− /sys/devices/cpu/events/PM_L3_HIT
540− /sys/devices/cpu/events/PM_L2_GLOB_GUESS_WRONG
541− /sys/devices/cpu/events/PM_MRK_DFU_FIN
542− /sys/devices/cpu/events/PM_INST_FROM_L1
543− /sys/devices/cpu/events/PM_IC_DEMAND_REQ
544− /sys/devices/cpu/events/PM_VSU1_FSQRT_FDIV_DOUBLE
545− /sys/devices/cpu/events/PM_VSU1_FMA
546− /sys/devices/cpu/events/PM_MRK_LD_MISS_L1
547− /sys/devices/cpu/events/PM_VSU0_2FLOP_DOUBLE
548− /sys/devices/cpu/events/PM_LSU_DC_PREF_STRIDED_STREAM_CONFIRM
549− /sys/devices/cpu/events/PM_INST_PTEG_FROM_L31_SHR
550− /sys/devices/cpu/events/PM_MRK_LSU_REJECT_ERAT_MISS
551− /sys/devices/cpu/events/PM_MRK_DATA_FROM_L2MISS
552− /sys/devices/cpu/events/PM_DATA_FROM_RL2L3_SHR
553− /sys/devices/cpu/events/PM_INST_FROM_PREF
554− /sys/devices/cpu/events/PM_VSU1_SQ
555− /sys/devices/cpu/events/PM_L2_LD_DISP
556− /sys/devices/cpu/events/PM_L2_DISP_ALL
557− /sys/devices/cpu/events/PM_THRD_GRP_CMPL_BOTH_CYC
558− /sys/devices/cpu/events/PM_VSU_FSQRT_FDIV_DOUBLE
559− /sys/devices/cpu/events/PM_INST_PTEG_FROM_DL2L3_SHR
560− /sys/devices/cpu/events/PM_VSU_1FLOP
561− /sys/devices/cpu/events/PM_HV_CYC
562− /sys/devices/cpu/events/PM_MRK_LSU_FIN
563− /sys/devices/cpu/events/PM_MRK_DATA_FROM_RL2L3_SHR
564− /sys/devices/cpu/events/PM_DTLB_MISS_16M
565− /sys/devices/cpu/events/PM_LSU1_LMQ_LHR_MERGE
566− /sys/devices/cpu/events/PM_IFU_FIN
567− /sys/devices/cpu/events/PM_1THRD_CON_RUN_INSTR
568− /sys/devices/cpu/events/PM_CMPLU_STALL_COUNT
569− /sys/devices/cpu/events/PM_MEM0_PB_RD_CL
570− /sys/devices/cpu/events/PM_THRD_1_RUN_CYC
571− /sys/devices/cpu/events/PM_THRD_2_CONC_RUN_INSTR
572− /sys/devices/cpu/events/PM_THRD_2_RUN_CYC
573− /sys/devices/cpu/events/PM_THRD_3_CONC_RUN_INST
574− /sys/devices/cpu/events/PM_THRD_3_RUN_CYC
575− /sys/devices/cpu/events/PM_THRD_4_CONC_RUN_INST
576− /sys/devices/cpu/events/PM_THRD_4_RUN_CYC
30+What: /sys/bus/event_source/devices/<pmu>/events/<event>
31+Date: 2014/02/24
32+Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
33+Description: Per-pmu performance monitoring events specific to the running system
57734
578−Date: 2013/01/08
35+ Each file (except for some of those with a '.' in them, '.unit'
36+ and '.scale') in the 'events' directory describes a single
37+ performance monitoring event supported by the <pmu>. The name
38+ of the file is the name of the event.
39+
40+ File contents:
41+
42+ <term>[=<value>][,<term>[=<value>]]...
43+
44+ Where <term> is one of the terms listed under
45+ /sys/bus/event_source/devices/<pmu>/format/ and <value> is
46+ a number is base-16 format with a '0x' prefix (lowercase only).
47+ If a <term> is specified alone (without an assigned value), it
48+ is implied that 0x1 is assigned to that <term>.
57949
50+ Examples (each of these lines would be in a seperate file):
51+
52+ event=0x2abc
53+ event=0x423,inv,cmask=0x3
54+ domain=0x1,offset=0x8,starting_index=0xffff
55+
56+ Each of the assignments indicates a value to be assigned to a
57+ particular set of bits (as defined by the format file
58+ corresponding to the <term>) in the perf_event structure passed
59+ to the perf_open syscall.
60+
61+What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
62+Date: 2014/02/24
58063 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
581− Linux Powerpc mailing list <linuxppc-dev@ozlabs.org>
64+Description: Perf event units
58265
583−Description: POWER-systems specific performance monitoring events
66+ A string specifying the English plural numerical unit that <event>
67+ (once multiplied by <event>.scale) represents.
58468
585− A collection of performance monitoring events that may be
586− supported by the POWER CPU. These events can be monitored
587− using the 'perf(1)' tool.
69+ Example:
58870
589− These events may not be supported by other CPUs.
71+ Joules
59072
591− The contents of each file would look like:
73+What: /sys/bus/event_source/devices/<pmu>/events/<event>.scale
74+Date: 2014/02/24
75+Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
76+Description: Perf event scaling factors
59277
593− event=0xNNNN
78+ A string representing a floating point value expressed in
79+ scientific notation to be multiplied by the event count
80+ recieved from the kernel to match the unit specified in the
81+ <event>.unit file.
59482
595− where 'N' is a hex digit and the number '0xNNNN' shows the
596− "raw code" for the perf event identified by the file's
597− "basename".
83+ Example:
84+
85+ 2.3283064365386962890625e-10
59886
599− Further, multiple terms like 'event=0xNNNN' can be specified
600− and separated with comma. All available terms are defined in
601− the /sys/bus/event_source/devices/<dev>/format file.
87+ This is provided to avoid performing floating point arithmetic
88+ in the kernel.
Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7+3−3
@@ -1,6 +1,6 @@
11 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog
22 Date: February 2014
3−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
3+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
44 Description:
55 Provides access to the binary "24x7 catalog" provided by the
66 hypervisor on POWER7 and 8 systems. This catalog lists events
@@ -10,14 +10,14 @@ Description: · 3 unmodified lines
1010
1111 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length
1212 Date: February 2014
13−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
13+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
1414 Description:
1515 A number equal to the length in bytes of the catalog. This is
1616 also extractable from the provided binary "catalog" sysfs entry.
1717
1818 What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version
1919 Date: February 2014
20−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
20+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
2121 Description:
2222 Exposes the "version" field of the 24x7 catalog. This is also
2323 extractable from the provided binary "catalog" sysfs entry.
Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci+6−6
@@ -1,6 +1,6 @@
11 What: /sys/bus/event_source/devices/hv_gpci/interface/collect_privileged
22 Date: February 2014
3−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
3+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
44 Description:
55 '0' if the hypervisor is configured to forbid access to event
66 counters being accumulated by other guests and to physical
@@ -9,35 +9,35 @@ Description: · 2 unmodified lines
99
1010 What: /sys/bus/event_source/devices/hv_gpci/interface/ga
1111 Date: February 2014
12−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
12+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
1313 Description:
1414 0 or 1. Indicates whether we have access to "GA" events (listed
1515 in arch/powerpc/perf/hv-gpci.h).
1616
1717 What: /sys/bus/event_source/devices/hv_gpci/interface/expanded
1818 Date: February 2014
19−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
19+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
2020 Description:
2121 0 or 1. Indicates whether we have access to "EXPANDED" events (listed
2222 in arch/powerpc/perf/hv-gpci.h).
2323
2424 What: /sys/bus/event_source/devices/hv_gpci/interface/lab
2525 Date: February 2014
26−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
26+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
2727 Description:
2828 0 or 1. Indicates whether we have access to "LAB" events (listed
2929 in arch/powerpc/perf/hv-gpci.h).
3030
3131 What: /sys/bus/event_source/devices/hv_gpci/interface/version
3232 Date: February 2014
33−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
33+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
3434 Description:
3535 A number indicating the version of the gpci interface that the
3636 hypervisor reports supporting.
3737
3838 What: /sys/bus/event_source/devices/hv_gpci/interface/kernel_version
3939 Date: February 2014
40−Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
40+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
4141 Description:
4242 A number indicating the latest version of the gpci interface
4343 that the kernel is aware of.
Documentation/ABI/testing/sysfs-bus-iio+23−0
@@ -200,6 +200,13 @@ Description: · 199 unmodified lines
200200 Raw pressure measurement from channel Y. Units after
201201 application of scale and offset are kilopascal.
202202
203+What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_input
204+What: /sys/bus/iio/devices/iio:deviceX/in_pressure_input
205+KernelVersion: 3.8
206+Contact: linux-iio@vger.kernel.org
207+Description:
208+ Scaled pressure measurement from channel Y, in kilopascal.
209+
203210 What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_raw
204211 KernelVersion: 3.14
205212 Contact: linux-iio@vger.kernel.org
@@ -231,6 +238,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset · 25 unmodified lines
231238 What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
232239 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
233240 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset
241+What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset
234242 KernelVersion: 2.6.35
235243 Contact: linux-iio@vger.kernel.org
236244 Description:
@@ -251,6 +259,7 @@ Description: · 14 unmodified lines
251259 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
252260 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
253261 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
262+What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
254263 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
255264 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
256265 What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
@@ -266,6 +275,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_sca · 9 unmodified lines
266275 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_scale
267276 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
268277 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
278+What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale
269279 KernelVersion: 2.6.35
270280 Contact: linux-iio@vger.kernel.org
271281 Description:
@@ -328,6 +338,10 @@ Description: · 56 unmodified lines
328338 are listed in this attribute.
329339
330340 What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
341+What: /sys/bus/iio/devices/iio:deviceX/in_intensity_red_hardwaregain
342+What: /sys/bus/iio/devices/iio:deviceX/in_intensity_green_hardwaregain
343+What: /sys/bus/iio/devices/iio:deviceX/in_intensity_blue_hardwaregain
344+What: /sys/bus/iio/devices/iio:deviceX/in_intensity_clear_hardwaregain
331345 KernelVersion: 2.6.35
332346 Contact: linux-iio@vger.kernel.org
333347 Description:
@@ -1028,3 +1042,12 @@ Contact: linux-iio@vger.kernel.org · 694 unmodified lines
10281042 Description:
10291043 Raw value of rotation from true/magnetic north measured with
10301044 or without compensation from tilt sensors.
1045+
1046+What: /sys/bus/iio/devices/iio:deviceX/in_currentX_raw
1047+KernelVersion: 3.18
1048+Contact: linux-iio@vger.kernel.org
1049+Description:
1050+ Raw current measurement from channel X. Units are in milliamps
1051+ after application of scale and offset. If no offset or scale is
1052+ present, output should be considered as processed with the
1053+ unit in milliamps.
Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150+7−0
@@ -0,0 +1,7 @@
1+What: /sys/bus/iio/devices/triggerX/name = "bmc150_accel-any-motion-devX"
2+KernelVersion: 3.17
3+Contact: linux-iio@vger.kernel.org
4+Description:
5+ The BMC150 accelerometer kernel module provides an additional trigger,
6+ which sets driver in a mode, where data is pushed to the buffer
7+ only when there is any motion.
Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160+7−0
@@ -0,0 +1,7 @@
1+What: /sys/bus/iio/devices/triggerX/name = "bmg160-any-motion-devX"
2+KernelVersion: 3.17
3+Contact: linux-iio@vger.kernel.org
4+Description:
5+ The BMG160 gyro kernel module provides an additional trigger,
6+ which sets driver in a mode, where data is pushed to the buffer
7+ only when there is any motion.
Documentation/ABI/testing/sysfs-bus-pci+23−0
@@ -65,6 +65,16 @@ Description: · 64 unmodified lines
6565 force a rescan of all PCI buses in the system, and
6666 re-discover previously removed devices.
6767
68+What: /sys/bus/pci/devices/.../msi_bus
69+Date: September 2014
70+Contact: Linux PCI developers <linux-pci@vger.kernel.org>
71+Description:
72+ Writing a zero value to this attribute disallows MSI and
73+ MSI-X for any future drivers of the device. If the device
74+ is a bridge, MSI and MSI-X will be disallowed for future
75+ drivers of all child devices under the bridge. Drivers
76+ must be reloaded for the new setting to take effect.
77+
6878 What: /sys/bus/pci/devices/.../msi_irqs/
6979 Date: September, 2011
7080 Contact: Neil Horman <nhorman@tuxdriver.com>
@@ -271,3 +281,16 @@ Description: · 200 unmodified lines
271281 opt-out of driver binding using a driver_override name such as
272282 "none". Only a single driver may be specified in the override,
273283 there is no support for parsing delimiters.
284+
285+What: /sys/bus/pci/devices/.../numa_node
286+Date: Oct 2014
287+Contact: Prarit Bhargava <prarit@redhat.com>
288+Description:
289+ This file contains the NUMA node to which the PCI device is
290+ attached, or -1 if the node is unknown. The initial value
291+ comes from an ACPI _PXM method or a similar firmware
292+ source. If that is missing or incorrect, this file can be
293+ written to override the node. In that case, please report
294+ a firmware bug to the system vendor. Writing to this file
295+ taints the kernel with TAINT_FIRMWARE_WORKAROUND, which
296+ reduces the supportability of your system.
Documentation/ABI/testing/sysfs-bus-usb+9−10
@@ -104,16 +104,15 @@ What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm · 103 unmodified lines
104104 Date: September 2011
105105 Contact: Andiry Xu <andiry.xu@amd.com>
106106 Description:
107− If CONFIG_PM_RUNTIME is set and a USB 2.0 lpm-capable device
108− is plugged in to a xHCI host which support link PM, it will
109− perform a LPM test; if the test is passed and host supports
110− USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will
111− be enabled for the device and the USB device directory will
112− contain a file named power/usb2_hardware_lpm. The file holds
113− a string value (enable or disable) indicating whether or not
114− USB2 hardware LPM is enabled for the device. Developer can
115− write y/Y/1 or n/N/0 to the file to enable/disable the
116− feature.
107+ If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
108+ in to a xHCI host which support link PM, it will perform a LPM
109+ test; if the test is passed and host supports USB2 hardware LPM
110+ (xHCI 1.0 feature), USB2 hardware LPM will be enabled for the
111+ device and the USB device directory will contain a file named
112+ power/usb2_hardware_lpm. The file holds a string value (enable
113+ or disable) indicating whether or not USB2 hardware LPM is
114+ enabled for the device. Developer can write y/Y/1 or n/N/0 to
115+ the file to enable/disable the feature.
117116
118117 What: /sys/bus/usb/devices/.../removable
119118 Date: February 2012
Documentation/ABI/testing/sysfs-class-cxl+129−0
@@ -0,0 +1,129 @@
1+Slave contexts (eg. /sys/class/cxl/afu0.0s):
2+
3+What: /sys/class/cxl/<afu>/irqs_max
4+Date: September 2014
5+Contact: linuxppc-dev@lists.ozlabs.org
6+Description: read/write
7+ Decimal value of maximum number of interrupts that can be
8+ requested by userspace. The default on probe is the maximum
9+ that hardware can support (eg. 2037). Write values will limit
10+ userspace applications to that many userspace interrupts. Must
11+ be >= irqs_min.
12+
13+What: /sys/class/cxl/<afu>/irqs_min
14+Date: September 2014
15+Contact: linuxppc-dev@lists.ozlabs.org
16+Description: read only
17+ Decimal value of the minimum number of interrupts that
18+ userspace must request on a CXL_START_WORK ioctl. Userspace may
19+ omit the num_interrupts field in the START_WORK IOCTL to get
20+ this minimum automatically.
21+
22+What: /sys/class/cxl/<afu>/mmio_size
23+Date: September 2014
24+Contact: linuxppc-dev@lists.ozlabs.org
25+Description: read only
26+ Decimal value of the size of the MMIO space that may be mmaped
27+ by userspace.
28+
29+What: /sys/class/cxl/<afu>/modes_supported
30+Date: September 2014
31+Contact: linuxppc-dev@lists.ozlabs.org
32+Description: read only
33+ List of the modes this AFU supports. One per line.
34+ Valid entries are: "dedicated_process" and "afu_directed"
35+
36+What: /sys/class/cxl/<afu>/mode
37+Date: September 2014
38+Contact: linuxppc-dev@lists.ozlabs.org
39+Description: read/write
40+ The current mode the AFU is using. Will be one of the modes
41+ given in modes_supported. Writing will change the mode
42+ provided that no user contexts are attached.
43+
44+
45+What: /sys/class/cxl/<afu>/prefault_mode
46+Date: September 2014
47+Contact: linuxppc-dev@lists.ozlabs.org
48+Description: read/write
49+ Set the mode for prefaulting in segments into the segment table
50+ when performing the START_WORK ioctl. Possible values:
51+ none: No prefaulting (default)
52+ work_element_descriptor: Treat the work element
53+ descriptor as an effective address and
54+ prefault what it points to.
55+ all: all segments process calling START_WORK maps.
56+
57+What: /sys/class/cxl/<afu>/reset
58+Date: September 2014
59+Contact: linuxppc-dev@lists.ozlabs.org
60+Description: write only
61+ Writing 1 here will reset the AFU provided there are not
62+ contexts active on the AFU.
63+
64+What: /sys/class/cxl/<afu>/api_version
65+Date: September 2014
66+Contact: linuxppc-dev@lists.ozlabs.org
67+Description: read only
68+ Decimal value of the current version of the kernel/user API.
69+
70+What: /sys/class/cxl/<afu>/api_version_com
71+Date: September 2014
72+Contact: linuxppc-dev@lists.ozlabs.org
73+Description: read only
74+ Decimal value of the the lowest version of the userspace API
75+ this this kernel supports.
76+
77+
78+
79+Master contexts (eg. /sys/class/cxl/afu0.0m)
80+
81+What: /sys/class/cxl/<afu>m/mmio_size
82+Date: September 2014
83+Contact: linuxppc-dev@lists.ozlabs.org
84+Description: read only
85+ Decimal value of the size of the MMIO space that may be mmaped
86+ by userspace. This includes all slave contexts space also.
87+
88+What: /sys/class/cxl/<afu>m/pp_mmio_len
89+Date: September 2014
90+Contact: linuxppc-dev@lists.ozlabs.org
91+Description: read only
92+ Decimal value of the Per Process MMIO space length.
93+
94+What: /sys/class/cxl/<afu>m/pp_mmio_off
95+Date: September 2014
96+Contact: linuxppc-dev@lists.ozlabs.org
97+Description: read only
98+ Decimal value of the Per Process MMIO space offset.
99+
100+
101+Card info (eg. /sys/class/cxl/card0)
102+
103+What: /sys/class/cxl/<card>/caia_version
104+Date: September 2014
105+Contact: linuxppc-dev@lists.ozlabs.org
106+Description: read only
107+ Identifies the CAIA Version the card implements.
108+
109+What: /sys/class/cxl/<card>/psl_version
110+Date: September 2014
111+Contact: linuxppc-dev@lists.ozlabs.org
112+Description: read only
113+ Identifies the revision level of the PSL.
114+
115+What: /sys/class/cxl/<card>/base_image
116+Date: September 2014
117+Contact: linuxppc-dev@lists.ozlabs.org
118+Description: read only
119+ Identifies the revision level of the base image for devices
120+ that support loadable PSLs. For FPGAs this field identifies
121+ the image contained in the on-adapter flash which is loaded
122+ during the initial program load.
123+
124+What: /sys/class/cxl/<card>/image_loaded
125+Date: September 2014
126+Contact: linuxppc-dev@lists.ozlabs.org
127+Description: read only
128+ Will return "user" or "factory" depending on the image loaded
129+ onto the card.
Documentation/ABI/testing/sysfs-class-net+9−1
@@ -159,7 +159,7 @@ Description: · 158 unmodified lines
159159 lower-level interface protocol used. Ethernet devices will show
160160 a 'mtu' attribute value of 1500 unless changed.
161161
162−What: /sys/calss/net/<iface>/netdev_group
162+What: /sys/class/net/<iface>/netdev_group
163163 Date: January 2011
164164 KernelVersion: 2.6.39
165165 Contact: netdev@vger.kernel.org
@@ -216,3 +216,11 @@ Contact: netdev@vger.kernel.org · 50 unmodified lines
216216 Description:
217217 Indicates the interface protocol type as a decimal value. See
218218 include/uapi/linux/if_arp.h for all possible values.
219+
220+What: /sys/class/net/<iface>/phys_switch_id
221+Date: November 2014
222+KernelVersion: 3.19
223+Contact: netdev@vger.kernel.org
224+Description:
225+ Indicates the unique physical switch identifier of a switch this
226+ port belongs to, as a string.
Documentation/ABI/testing/sysfs-class-power+14−0
@@ -18,3 +18,17 @@ Description: · 17 unmodified lines
1818 This file is writeable and can be used to set the assumed
1919 battery 'full level'. As batteries age, this value has to be
2020 amended over time.
21+
22+What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
23+Date: October 2014
24+KernelVersion: 3.18.0
25+Contact: Krzysztof Kozlowski <k.kozlowski@samsung.com>
26+Description:
27+ This entry shows and sets the maximum time the max14577
28+ charger operates in fast-charge mode. When the timer expires
29+ the device will terminate fast-charge mode (charging current
30+ will drop to 0 A) and will trigger interrupt.
31+
32+ Valid values:
33+ - 5, 6 or 7 (hours),
34+ - 0: disabled.
Documentation/ABI/testing/sysfs-class-uwb_rc+13−0
@@ -43,6 +43,19 @@ Description: · 42 unmodified lines
4343 Reading returns the currently active channel, or -1 if
4444 the radio controller is not beaconing.
4545
46+What: /sys/class/uwb_rc/uwbN/ASIE
47+Date: August 2014
48+KernelVersion: 3.18
49+Contact: linux-usb@vger.kernel.org
50+Description:
51+
52+ The application-specific information element (ASIE)
53+ included in this device's beacon, in space separated
54+ hex octets.
55+
56+ Reading returns the current ASIE. Writing replaces
57+ the current ASIE with the one written.
58+
4659 What: /sys/class/uwb_rc/uwbN/scan
4760 Date: July 2008
4861 KernelVersion: 2.6.27
Documentation/ABI/testing/sysfs-devices-memory+8−0
@@ -61,6 +61,14 @@ Users: hotplug memory remove tools · 60 unmodified lines
6161 http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
6262
6363
64+What: /sys/devices/system/memory/memoryX/valid_zones
65+Date: July 2014
66+Contact: Zhang Zhen <zhenzhang.zhang@huawei.com>
67+Description:
68+ The file /sys/devices/system/memory/memoryX/valid_zones is
69+ read-only and is designed to show which zone this memory
70+ block can be onlined to.
71+
6472 What: /sys/devices/system/memoryX/nodeY
6573 Date: October 2009
6674 Contact: Linux Memory Management list <linux-mm@kvack.org>
Documentation/ABI/testing/sysfs-devices-system-cpu+47−0
@@ -224,3 +224,50 @@ Description: Parameters for the Intel P-state driver · 223 unmodified lines
224224 frequency range.
225225
226226 More details can be found in Documentation/cpu-freq/intel-pstate.txt
227+
228+What: /sys/devices/system/cpu/cpu*/cache/index*/<set_of_attributes_mentioned_below>
229+Date: July 2014(documented, existed before August 2008)
230+Contact: Sudeep Holla <sudeep.holla@arm.com>
231+ Linux kernel mailing list <linux-kernel@vger.kernel.org>
232+Description: Parameters for the CPU cache attributes
233+
234+ allocation_policy:
235+ - WriteAllocate: allocate a memory location to a cache line
236+ on a cache miss because of a write
237+ - ReadAllocate: allocate a memory location to a cache line
238+ on a cache miss because of a read
239+ - ReadWriteAllocate: both writeallocate and readallocate
240+
241+ attributes: LEGACY used only on IA64 and is same as write_policy
242+
243+ coherency_line_size: the minimum amount of data in bytes that gets
244+ transferred from memory to cache
245+
246+ level: the cache hierarcy in the multi-level cache configuration
247+
248+ number_of_sets: total number of sets in the cache, a set is a
249+ collection of cache lines with the same cache index
250+
251+ physical_line_partition: number of physical cache line per cache tag
252+
253+ shared_cpu_list: the list of logical cpus sharing the cache
254+
255+ shared_cpu_map: logical cpu mask containing the list of cpus sharing
256+ the cache
257+
258+ size: the total cache size in kB
259+
260+ type:
261+ - Instruction: cache that only holds instructions
262+ - Data: cache that only caches data
263+ - Unified: cache that holds both data and instructions
264+
265+ ways_of_associativity: degree of freedom in placing a particular block
266+ of memory in the cache
267+
268+ write_policy:
269+ - WriteThrough: data is written to both the cache line
270+ and to the block in the lower-level memory
271+ - WriteBack: data is written only to the cache line and
272+ the modified cache line is written to main
273+ memory only when it is replaced
Documentation/ABI/testing/sysfs-fs-f2fs+7−0
@@ -44,6 +44,13 @@ Description: · 43 unmodified lines
4444 Controls the FS utilization condition for the in-place-update
4545 policies.
4646
47+What: /sys/fs/f2fs/<disk>/min_fsync_blocks
48+Date: September 2014
49+Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
50+Description:
51+ Controls the dirty page count condition for the in-place-update
52+ policies.
53+
4754 What: /sys/fs/f2fs/<disk>/max_small_discards
4855 Date: November 2013
4956 Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Documentation/ABI/testing/sysfs-ibft+1−1
@@ -20,4 +20,4 @@ Date: November 2007 · 19 unmodified lines
2020 Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
2121 Description: The /sys/firmware/ibft/ethernetX directory will contain
2222 files that expose the iSCSI Boot Firmware Table NIC data.
23− This can this can the IP address, MAC, and gateway of the NIC.
23+ Usually this contains the IP address, MAC, and gateway of the NIC.
Documentation/ABI/testing/sysfs-platform-dell-laptop+60−0
@@ -0,0 +1,60 @@
1+What: /sys/class/leds/dell::kbd_backlight/als_setting
2+Date: December 2014
3+KernelVersion: 3.19
4+Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
5+ Pali Rohár <pali.rohar@gmail.com>
6+Description:
7+ This file allows to control the automatic keyboard
8+ illumination mode on some systems that have an ambient
9+ light sensor. Write 1 to this file to enable the auto
10+ mode, 0 to disable it.
11+
12+What: /sys/class/leds/dell::kbd_backlight/start_triggers
13+Date: December 2014
14+KernelVersion: 3.19
15+Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
16+ Pali Rohár <pali.rohar@gmail.com>
17+Description:
18+ This file allows to control the input triggers that
19+ turn on the keyboard backlight illumination that is
20+ disabled because of inactivity.
21+ Read the file to see the triggers available. The ones
22+ enabled are preceded by '+', those disabled by '-'.
23+
24+ To enable a trigger, write its name preceded by '+' to
25+ this file. To disable a trigger, write its name preceded
26+ by '-' instead.
27+
28+ For example, to enable the keyboard as trigger run:
29+ echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
30+ To disable it:
31+ echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
32+
33+ Note that not all the available triggers can be configured.
34+
35+What: /sys/class/leds/dell::kbd_backlight/stop_timeout
36+Date: December 2014
37+KernelVersion: 3.19
38+Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
39+ Pali Rohár <pali.rohar@gmail.com>
40+Description:
41+ This file allows to specify the interval after which the
42+ keyboard illumination is disabled because of inactivity.
43+ The timeouts are expressed in seconds, minutes, hours and
44+ days, for which the symbols are 's', 'm', 'h' and 'd'
45+ respectively.
46+
47+ To configure the timeout, write to this file a value along
48+ with any the above units. If no unit is specified, the value
49+ is assumed to be expressed in seconds.
50+
51+ For example, to set the timeout to 10 minutes run:
52+ echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout
53+
54+ Note that when this file is read, the returned value might be
55+ expressed in a different unit than the one used when the timeout
56+ was set.
57+
58+ Also note that only some timeouts are supported and that
59+ some systems might fall back to a specific timeout in case
60+ an invalid timeout is written to this file.
Documentation/Changes+6−17
@@ -167,18 +167,11 @@ later is recommended, due to some significant improvements). · 166 unmodified lines
167167 PCMCIAutils
168168 -----------
169169
170−PCMCIAutils replaces pcmcia-cs (see below). It properly sets up
170+PCMCIAutils replaces pcmcia-cs. It properly sets up
171171 PCMCIA sockets at system startup and loads the appropriate modules
172172 for 16-bit PCMCIA devices if the kernel is modularized and the hotplug
173173 subsystem is used.
174174
175−Pcmcia-cs
176−---------
177−
178−PCMCIA (PC Card) support is now partially implemented in the main
179−kernel source. The "pcmciautils" package (see above) replaces pcmcia-cs
180−for newest kernels.
181−
182175 Quota-tools
183176 -----------
184177
@@ -341,17 +334,13 @@ Pcmciautils · 156 unmodified lines
341334 -----------
342335 o <ftp://ftp.kernel.org/pub/linux/utils/kernel/pcmcia/>
343336
344−Pcmcia-cs
345−---------
346−o <http://pcmcia-cs.sourceforge.net/>
347−
348337 Quota-tools
349338 ----------
350339 o <http://sourceforge.net/projects/linuxquota/>
351340
352341 DocBook Stylesheets
353342 -------------------
354−o <http://nwalsh.com/docbook/dsssl/>
343+o <http://sourceforge.net/projects/docbook/files/docbook-dsssl/>
355344
356345 XMLTO XSLT Frontend
357346 -------------------
@@ -359,11 +348,11 @@ o <http://cyberelk.net/tim/xmlto/> · 1 unmodified line
359348
360349 Intel P6 microcode
361350 ------------------
362−o <http://www.urbanmyth.org/microcode/>
351+o <https://downloadcenter.intel.com/>
363352
364353 udev
365354 ----
366−o <http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html>
355+o <http://www.freedesktop.org/software/systemd/man/udev.html>
367356
368357 FUSE
369358 ----
@@ -371,7 +360,7 @@ o <http://sourceforge.net/projects/fuse> · 1 unmodified line
371360
372361 mcelog
373362 ------
374−o <ftp://ftp.kernel.org/pub/linux/utils/cpu/mce/>
363+o <http://www.mcelog.org/>
375364
376365 Networking
377366 **********
@@ -394,7 +383,7 @@ o <http://www.iptables.org/downloads.html> · 16 unmodified lines
394383
395384 Ip-route2
396385 ---------
397−o <ftp://ftp.tux.org/pub/net/ip-routing/iproute2-2.2.4-now-ss991023.tar.gz>
386+o <https://www.kernel.org/pub/linux/utils/net/iproute2/>
398387
399388 OProfile
400389 --------
Documentation/CodingStyle+66−6
@@ -392,7 +392,12 @@ The goto statement comes in handy when a function exits from multiple · 391 unmodified lines
392392 locations and some common work such as cleanup has to be done. If there is no
393393 cleanup needed then just return directly.
394394
395−The rationale is:
395+Choose label names which say what the goto does or why the goto exists. An
396+example of a good name could be "out_buffer:" if the goto frees "buffer". Avoid
397+using GW-BASIC names like "err1:" and "err2:". Also don't name them after the
398+goto location like "err_kmalloc_failed:"
399+
400+The rationale for using gotos is:
396401
397402 - unconditional statements are easier to understand and follow
398403 - nesting is reduced
@@ -403,9 +408,10 @@ The rationale is: · 4 unmodified lines
403408 int fun(int a)
404409 {
405410 int result = 0;
406− char *buffer = kmalloc(SIZE);
411+ char *buffer;
407412
408− if (buffer == NULL)
413+ buffer = kmalloc(SIZE, GFP_KERNEL);
414+ if (!buffer)
409415 return -ENOMEM;
410416
411417 if (condition1) {
@@ -413,14 +419,25 @@ int fun(int a) · 1 unmodified line
413419 ...
414420 }
415421 result = 1;
416− goto out;
422+ goto out_buffer;
417423 }
418424 ...
419−out:
425+out_buffer:
420426 kfree(buffer);
421427 return result;
422428 }
423429
430+A common type of bug to be aware of it "one err bugs" which look like this:
431+
432+err:
433+ kfree(foo->bar);
434+ kfree(foo);
435+ return ret;
436+
437+The bug in this code is that on some exit paths "foo" is NULL. Normally the
438+fix for this is to split it up into two error labels "err_bar:" and "err_foo:".
439+
440+
424441 Chapter 8: Commenting
425442
426443 Comments are good, but there is also a danger of over-commenting. NEVER
@@ -675,7 +692,7 @@ the ones already enabled by DEBUG. · 248 unmodified lines
675692 Many subsystems have Kconfig debug options to turn on -DDEBUG in the
676693 corresponding Makefile; in other cases specific files #define DEBUG. And
677694 when a debug message should be unconditionally printed, such as if it is
678−already inside a debug-related #ifdef secton, printk(KERN_DEBUG ...) can be
695+already inside a debug-related #ifdef section, printk(KERN_DEBUG ...) can be
679696 used.
680697
681698
@@ -845,6 +862,49 @@ next instruction in the assembly output: · 163 unmodified lines
845862 : /* outputs */ : /* inputs */ : /* clobbers */);
846863
847864
865+ Chapter 20: Conditional Compilation
866+
867+Wherever possible, don't use preprocessor conditionals (#if, #ifdef) in .c
868+files; doing so makes code harder to read and logic harder to follow. Instead,
869+use such conditionals in a header file defining functions for use in those .c
870+files, providing no-op stub versions in the #else case, and then call those
871+functions unconditionally from .c files. The compiler will avoid generating
872+any code for the stub calls, producing identical results, but the logic will
873+remain easy to follow.
874+
875+Prefer to compile out entire functions, rather than portions of functions or
876+portions of expressions. Rather than putting an ifdef in an expression, factor
877+out part or all of the expression into a separate helper function and apply the
878+conditional to that function.
879+
880+If you have a function or variable which may potentially go unused in a
881+particular configuration, and the compiler would warn about its definition
882+going unused, mark the definition as __maybe_unused rather than wrapping it in
883+a preprocessor conditional. (However, if a function or variable *always* goes
884+unused, delete it.)
885+
886+Within code, where possible, use the IS_ENABLED macro to convert a Kconfig
887+symbol into a C boolean expression, and use it in a normal C conditional:
888+
889+ if (IS_ENABLED(CONFIG_SOMETHING)) {
890+ ...
891+ }
892+
893+The compiler will constant-fold the conditional away, and include or exclude
894+the block of code just as with an #ifdef, so this will not add any runtime
895+overhead. However, this approach still allows the C compiler to see the code
896+inside the block, and check it for correctness (syntax, types, symbol
897+references, etc). Thus, you still have to use an #ifdef if the code inside the
898+block references symbols that will not exist if the condition is not met.
899+
900+At the end of any non-trivial #if or #ifdef block (more than a few lines),
901+place a comment after the #endif on the same line, noting the conditional
902+expression used. For instance:
903+
904+#ifdef CONFIG_SOMETHING
905+...
906+#endif /* CONFIG_SOMETHING */
907+
848908
849909 Appendix I: References
850910
Documentation/DMA-API-HOWTO.txt+3−3
@@ -531,7 +531,7 @@ To map a single region, you do: · 530 unmodified lines
531531 size_t size = buffer->len;
532532
533533 dma_handle = dma_map_single(dev, addr, size, direction);
534− if (dma_mapping_error(dma_handle)) {
534+ if (dma_mapping_error(dev, dma_handle)) {
535535 /*
536536 * reduce current DMA mapping usage,
537537 * delay and try again later or
@@ -588,7 +588,7 @@ Specifically: · 50 unmodified lines
588588 size_t size = buffer->len;
589589
590590 dma_handle = dma_map_page(dev, page, offset, size, direction);
591− if (dma_mapping_error(dma_handle)) {
591+ if (dma_mapping_error(dev, dma_handle)) {
592592 /*
593593 * reduce current DMA mapping usage,
594594 * delay and try again later or
@@ -689,7 +689,7 @@ to use the dma_sync_*() interfaces. · 94 unmodified lines
689689 dma_addr_t mapping;
690690
691691 mapping = dma_map_single(cp->dev, buffer, len, DMA_FROM_DEVICE);
692− if (dma_mapping_error(dma_handle)) {
692+ if (dma_mapping_error(cp->dev, dma_handle)) {
693693 /*
694694 * reduce current DMA mapping usage,
695695 * delay and try again later or
Documentation/DocBook/Makefile+1−1
@@ -15,7 +15,7 @@ DOCBOOKS := z8530book.xml device-drivers.xml \ · 14 unmodified lines
1515 80211.xml debugobjects.xml sh.xml regulator.xml \
1616 alsa-driver-api.xml writing-an-alsa-driver.xml \
1717 tracepoint.xml drm.xml media_api.xml w1.xml \
18− writing_musb_glue_layer.xml
18+ writing_musb_glue_layer.xml crypto-API.xml
1919
2020 include Documentation/DocBook/media/Makefile
2121
Documentation/DocBook/alsa-driver-api.tmpl+31−0
@@ -57,6 +57,7 @@ · 56 unmodified lines
5757 !Esound/core/pcm.c
5858 !Esound/core/pcm_lib.c
5959 !Esound/core/pcm_native.c
60+!Iinclude/sound/pcm.h
6061 </sect1>
6162 <sect1><title>PCM Format Helpers</title>
6263 !Esound/core/pcm_misc.c
@@ -64,6 +65,10 @@ · 1 unmodified line
6465 <sect1><title>PCM Memory Management</title>
6566 !Esound/core/pcm_memory.c
6667 </sect1>
68+ <sect1><title>PCM DMA Engine API</title>
69+!Esound/core/pcm_dmaengine.c
70+!Iinclude/sound/dmaengine_pcm.h
71+ </sect1>
6772 </chapter>
6873 <chapter><title>Control/Mixer API</title>
6974 <sect1><title>General Control Interface</title>
@@ -91,12 +96,38 @@ · 21 unmodified lines
9196 !Esound/core/info.c
9297 </sect1>
9398 </chapter>
99+ <chapter><title>Compress Offload</title>
100+ <sect1><title>Compress Offload API</title>
101+!Esound/core/compress_offload.c
102+!Iinclude/uapi/sound/compress_offload.h
103+!Iinclude/uapi/sound/compress_params.h
104+!Iinclude/sound/compress_driver.h
105+ </sect1>
106+ </chapter>
107+ <chapter><title>ASoC</title>
108+ <sect1><title>ASoC Core API</title>
109+!Iinclude/sound/soc.h
110+!Esound/soc/soc-core.c
111+!Esound/soc/soc-cache.c
112+!Esound/soc/soc-devres.c
113+!Esound/soc/soc-io.c
114+!Esound/soc/soc-pcm.c
115+ </sect1>
116+ <sect1><title>ASoC DAPM API</title>
117+!Esound/soc/soc-dapm.c
118+ </sect1>
119+ <sect1><title>ASoC DMA Engine API</title>
120+!Esound/soc/soc-generic-dmaengine-pcm.c
121+ </sect1>
122+ </chapter>
94123 <chapter><title>Miscellaneous Functions</title>
95124 <sect1><title>Hardware-Dependent Devices API</title>
96125 !Esound/core/hwdep.c
97126 </sect1>
98127 <sect1><title>Jack Abstraction Layer API</title>
128+!Iinclude/sound/jack.h
99129 !Esound/core/jack.c
130+!Esound/soc/soc-jack.c
100131 </sect1>
101132 <sect1><title>ISA DMA Helpers</title>
102133 !Esound/core/isadma.c
Documentation/DocBook/crypto-API.tmpl+1253−0
@@ -0,0 +1,1253 @@
1+<?xml version="1.0" encoding="UTF-8"?>
2+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
3+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
4+
5+<book id="KernelCryptoAPI">
6+ <bookinfo>
7+ <title>Linux Kernel Crypto API</title>
8+
9+ <authorgroup>
10+ <author>
11+ <firstname>Stephan</firstname>
12+ <surname>Mueller</surname>
13+ <affiliation>
14+ <address>
15+ <email>smueller@chronox.de</email>
16+ </address>
17+ </affiliation>
18+ </author>
19+ <author>
20+ <firstname>Marek</firstname>
21+ <surname>Vasut</surname>
22+ <affiliation>
23+ <address>
24+ <email>marek@denx.de</email>
25+ </address>
26+ </affiliation>
27+ </author>
28+ </authorgroup>
29+
30+ <copyright>
31+ <year>2014</year>
32+ <holder>Stephan Mueller</holder>
33+ </copyright>
34+
35+
36+ <legalnotice>
37+ <para>
38+ This documentation is free software; you can redistribute
39+ it and/or modify it under the terms of the GNU General Public
40+ License as published by the Free Software Foundation; either
41+ version 2 of the License, or (at your option) any later
42+ version.
43+ </para>
44+
45+ <para>
46+ This program is distributed in the hope that it will be
47+ useful, but WITHOUT ANY WARRANTY; without even the implied
48+ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
49+ See the GNU General Public License for more details.
50+ </para>
51+
52+ <para>
53+ You should have received a copy of the GNU General Public
54+ License along with this program; if not, write to the Free
55+ Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
56+ MA 02111-1307 USA
57+ </para>
58+
59+ <para>
60+ For more details see the file COPYING in the source
61+ distribution of Linux.
62+ </para>
63+ </legalnotice>
64+ </bookinfo>
65+
66+ <toc></toc>
67+
68+ <chapter id="Intro">
69+ <title>Kernel Crypto API Interface Specification</title>
70+
71+ <sect1><title>Introduction</title>
72+
73+ <para>
74+ The kernel crypto API offers a rich set of cryptographic ciphers as
75+ well as other data transformation mechanisms and methods to invoke
76+ these. This document contains a description of the API and provides
77+ example code.
78+ </para>
79+
80+ <para>
81+ To understand and properly use the kernel crypto API a brief
82+ explanation of its structure is given. Based on the architecture,
83+ the API can be separated into different components. Following the
84+ architecture specification, hints to developers of ciphers are
85+ provided. Pointers to the API function call documentation are
86+ given at the end.
87+ </para>
88+
89+ <para>
90+ The kernel crypto API refers to all algorithms as "transformations".
91+ Therefore, a cipher handle variable usually has the name "tfm".
92+ Besides cryptographic operations, the kernel crypto API also knows
93+ compression transformations and handles them the same way as ciphers.
94+ </para>
95+
96+ <para>
97+ The kernel crypto API serves the following entity types:
98+
99+ <itemizedlist>
100+ <listitem>
101+ <para>consumers requesting cryptographic services</para>
102+ </listitem>
103+ <listitem>
104+ <para>data transformation implementations (typically ciphers)
105+ that can be called by consumers using the kernel crypto
106+ API</para>
107+ </listitem>
108+ </itemizedlist>
109+ </para>
110+
111+ <para>
112+ This specification is intended for consumers of the kernel crypto
113+ API as well as for developers implementing ciphers. This API
114+ specification, however, does not discusses all API calls available
115+ to data transformation implementations (i.e. implementations of
116+ ciphers and other transformations (such as CRC or even compression
117+ algorithms) that can register with the kernel crypto API).
118+ </para>
119+
120+ <para>
121+ Note: The terms "transformation" and cipher algorithm are used
122+ interchangably.
123+ </para>
124+ </sect1>
125+
126+ <sect1><title>Terminology</title>
127+ <para>
128+ The transformation implementation is an actual code or interface
129+ to hardware which implements a certain transformation with precisely
130+ defined behavior.
131+ </para>
132+
133+ <para>
134+ The transformation object (TFM) is an instance of a transformation
135+ implementation. There can be multiple transformation objects
136+ associated with a single transformation implementation. Each of
137+ those transformation objects is held by a crypto API consumer or
138+ another transformation. Transformation object is allocated when a
139+ crypto API consumer requests a transformation implementation.
140+ The consumer is then provided with a structure, which contains
141+ a transformation object (TFM).
142+ </para>
143+
144+ <para>
145+ The structure that contains transformation objects may also be
146+ referred to as a "cipher handle". Such a cipher handle is always
147+ subject to the following phases that are reflected in the API calls
148+ applicable to such a cipher handle:
149+ </para>
150+
151+ <orderedlist>
152+ <listitem>
153+ <para>Initialization of a cipher handle.</para>
154+ </listitem>
155+ <listitem>
156+ <para>Execution of all intended cipher operations applicable
157+ for the handle where the cipher handle must be furnished to
158+ every API call.</para>
159+ </listitem>
160+ <listitem>
161+ <para>Destruction of a cipher handle.</para>
162+ </listitem>
163+ </orderedlist>
164+
165+ <para>
166+ When using the initialization API calls, a cipher handle is
167+ created and returned to the consumer. Therefore, please refer
168+ to all initialization API calls that refer to the data
169+ structure type a consumer is expected to receive and subsequently
170+ to use. The initialization API calls have all the same naming
171+ conventions of crypto_alloc_*.
172+ </para>
173+
174+ <para>
175+ The transformation context is private data associated with
176+ the transformation object.
177+ </para>
178+ </sect1>
179+ </chapter>
180+
181+ <chapter id="Architecture"><title>Kernel Crypto API Architecture</title>
182+ <sect1><title>Cipher algorithm types</title>
183+ <para>
184+ The kernel crypto API provides different API calls for the
185+ following cipher types:
186+
187+ <itemizedlist>
188+ <listitem><para>Symmetric ciphers</para></listitem>
189+ <listitem><para>AEAD ciphers</para></listitem>
190+ <listitem><para>Message digest, including keyed message digest</para></listitem>
191+ <listitem><para>Random number generation</para></listitem>
192+ <listitem><para>User space interface</para></listitem>
193+ </itemizedlist>
194+ </para>
195+ </sect1>
196+
197+ <sect1><title>Ciphers And Templates</title>
198+ <para>
199+ The kernel crypto API provides implementations of single block
200+ ciphers and message digests. In addition, the kernel crypto API
201+ provides numerous "templates" that can be used in conjunction
202+ with the single block ciphers and message digests. Templates
203+ include all types of block chaining mode, the HMAC mechanism, etc.
204+ </para>
205+
206+ <para>
207+ Single block ciphers and message digests can either be directly
208+ used by a caller or invoked together with a template to form
209+ multi-block ciphers or keyed message digests.
210+ </para>
211+
212+ <para>
213+ A single block cipher may even be called with multiple templates.
214+ However, templates cannot be used without a single cipher.
215+ </para>
216+
217+ <para>
218+ See /proc/crypto and search for "name". For example:
219+
220+ <itemizedlist>
221+ <listitem><para>aes</para></listitem>
222+ <listitem><para>ecb(aes)</para></listitem>
223+ <listitem><para>cmac(aes)</para></listitem>
224+ <listitem><para>ccm(aes)</para></listitem>
225+ <listitem><para>rfc4106(gcm(aes))</para></listitem>
226+ <listitem><para>sha1</para></listitem>
227+ <listitem><para>hmac(sha1)</para></listitem>
228+ <listitem><para>authenc(hmac(sha1),cbc(aes))</para></listitem>
229+ </itemizedlist>
230+ </para>
231+
232+ <para>
233+ In these examples, "aes" and "sha1" are the ciphers and all
234+ others are the templates.
235+ </para>
236+ </sect1>
237+
238+ <sect1><title>Synchronous And Asynchronous Operation</title>
239+ <para>
240+ The kernel crypto API provides synchronous and asynchronous
241+ API operations.
242+ </para>
243+
244+ <para>
245+ When using the synchronous API operation, the caller invokes
246+ a cipher operation which is performed synchronously by the
247+ kernel crypto API. That means, the caller waits until the
248+ cipher operation completes. Therefore, the kernel crypto API
249+ calls work like regular function calls. For synchronous
250+ operation, the set of API calls is small and conceptually
251+ similar to any other crypto library.
252+ </para>
253+
254+ <para>
255+ Asynchronous operation is provided by the kernel crypto API
256+ which implies that the invocation of a cipher operation will
257+ complete almost instantly. That invocation triggers the
258+ cipher operation but it does not signal its completion. Before
259+ invoking a cipher operation, the caller must provide a callback
260+ function the kernel crypto API can invoke to signal the
261+ completion of the cipher operation. Furthermore, the caller
262+ must ensure it can handle such asynchronous events by applying
263+ appropriate locking around its data. The kernel crypto API
264+ does not perform any special serialization operation to protect
265+ the caller's data integrity.
266+ </para>
267+ </sect1>
268+
269+ <sect1><title>Crypto API Cipher References And Priority</title>
270+ <para>
271+ A cipher is referenced by the caller with a string. That string
272+ has the following semantics:
273+
274+ <programlisting>
275+ template(single block cipher)
276+ </programlisting>
277+
278+ where "template" and "single block cipher" is the aforementioned
279+ template and single block cipher, respectively. If applicable,
280+ additional templates may enclose other templates, such as
281+
282+ <programlisting>
283+ template1(template2(single block cipher)))
284+ </programlisting>
285+ </para>
286+
287+ <para>
288+ The kernel crypto API may provide multiple implementations of a
289+ template or a single block cipher. For example, AES on newer
290+ Intel hardware has the following implementations: AES-NI,
291+ assembler implementation, or straight C. Now, when using the
292+ string "aes" with the kernel crypto API, which cipher
293+ implementation is used? The answer to that question is the
294+ priority number assigned to each cipher implementation by the
295+ kernel crypto API. When a caller uses the string to refer to a
296+ cipher during initialization of a cipher handle, the kernel
297+ crypto API looks up all implementations providing an
298+ implementation with that name and selects the implementation
299+ with the highest priority.
300+ </para>
301+
302+ <para>
303+ Now, a caller may have the need to refer to a specific cipher
304+ implementation and thus does not want to rely on the
305+ priority-based selection. To accommodate this scenario, the
306+ kernel crypto API allows the cipher implementation to register
307+ a unique name in addition to common names. When using that
308+ unique name, a caller is therefore always sure to refer to
309+ the intended cipher implementation.
310+ </para>
311+
312+ <para>
313+ The list of available ciphers is given in /proc/crypto. However,
314+ that list does not specify all possible permutations of
315+ templates and ciphers. Each block listed in /proc/crypto may
316+ contain the following information -- if one of the components
317+ listed as follows are not applicable to a cipher, it is not
318+ displayed:
319+ </para>
320+
321+ <itemizedlist>
322+ <listitem>
323+ <para>name: the generic name of the cipher that is subject
324+ to the priority-based selection -- this name can be used by
325+ the cipher allocation API calls (all names listed above are
326+ examples for such generic names)</para>
327+ </listitem>
328+ <listitem>
329+ <para>driver: the unique name of the cipher -- this name can
330+ be used by the cipher allocation API calls</para>
331+ </listitem>
332+ <listitem>
333+ <para>module: the kernel module providing the cipher
334+ implementation (or "kernel" for statically linked ciphers)</para>
335+ </listitem>
336+ <listitem>
337+ <para>priority: the priority value of the cipher implementation</para>
338+ </listitem>
339+ <listitem>
340+ <para>refcnt: the reference count of the respective cipher
341+ (i.e. the number of current consumers of this cipher)</para>
342+ </listitem>
343+ <listitem>
344+ <para>selftest: specification whether the self test for the
345+ cipher passed</para>
346+ </listitem>
347+ <listitem>
348+ <para>type:
349+ <itemizedlist>
350+ <listitem>
351+ <para>blkcipher for synchronous block ciphers</para>
352+ </listitem>
353+ <listitem>
354+ <para>ablkcipher for asynchronous block ciphers</para>
355+ </listitem>
356+ <listitem>
357+ <para>cipher for single block ciphers that may be used with
358+ an additional template</para>
359+ </listitem>
360+ <listitem>
361+ <para>shash for synchronous message digest</para>
362+ </listitem>
363+ <listitem>
364+ <para>ahash for asynchronous message digest</para>
365+ </listitem>
366+ <listitem>
367+ <para>aead for AEAD cipher type</para>
368+ </listitem>
369+ <listitem>
370+ <para>compression for compression type transformations</para>
371+ </listitem>
372+ <listitem>
373+ <para>rng for random number generator</para>
374+ </listitem>
375+ <listitem>
376+ <para>givcipher for cipher with associated IV generator
377+ (see the geniv entry below for the specification of the
378+ IV generator type used by the cipher implementation)</para>
379+ </listitem>
380+ </itemizedlist>
381+ </para>
382+ </listitem>
383+ <listitem>
384+ <para>blocksize: blocksize of cipher in bytes</para>
385+ </listitem>
386+ <listitem>
387+ <para>keysize: key size in bytes</para>
388+ </listitem>
389+ <listitem>
390+ <para>ivsize: IV size in bytes</para>
391+ </listitem>
392+ <listitem>
393+ <para>seedsize: required size of seed data for random number
394+ generator</para>
395+ </listitem>
396+ <listitem>
397+ <para>digestsize: output size of the message digest</para>
398+ </listitem>
399+ <listitem>
400+ <para>geniv: IV generation type:
401+ <itemizedlist>
402+ <listitem>
403+ <para>eseqiv for encrypted sequence number based IV
404+ generation</para>
405+ </listitem>
406+ <listitem>
407+ <para>seqiv for sequence number based IV generation</para>
408+ </listitem>
409+ <listitem>
410+ <para>chainiv for chain iv generation</para>
411+ </listitem>
412+ <listitem>
413+ <para>&lt;builtin&gt; is a marker that the cipher implements
414+ IV generation and handling as it is specific to the given
415+ cipher</para>
416+ </listitem>
417+ </itemizedlist>
418+ </para>
419+ </listitem>
420+ </itemizedlist>
421+ </sect1>
422+
423+ <sect1><title>Key Sizes</title>
424+ <para>
425+ When allocating a cipher handle, the caller only specifies the
426+ cipher type. Symmetric ciphers, however, typically support
427+ multiple key sizes (e.g. AES-128 vs. AES-192 vs. AES-256).
428+ These key sizes are determined with the length of the provided
429+ key. Thus, the kernel crypto API does not provide a separate
430+ way to select the particular symmetric cipher key size.
431+ </para>
432+ </sect1>
433+
434+ <sect1><title>Cipher Allocation Type And Masks</title>
435+ <para>
436+ The different cipher handle allocation functions allow the
437+ specification of a type and mask flag. Both parameters have
438+ the following meaning (and are therefore not covered in the
439+ subsequent sections).
440+ </para>
441+
442+ <para>
443+ The type flag specifies the type of the cipher algorithm.
444+ The caller usually provides a 0 when the caller wants the
445+ default handling. Otherwise, the caller may provide the
446+ following selections which match the the aforementioned
447+ cipher types:
448+ </para>
449+
450+ <itemizedlist>
451+ <listitem>
452+ <para>CRYPTO_ALG_TYPE_CIPHER Single block cipher</para>
453+ </listitem>
454+ <listitem>
455+ <para>CRYPTO_ALG_TYPE_COMPRESS Compression</para>
456+ </listitem>
457+ <listitem>
458+ <para>CRYPTO_ALG_TYPE_AEAD Authenticated Encryption with
459+ Associated Data (MAC)</para>
460+ </listitem>
461+ <listitem>
462+ <para>CRYPTO_ALG_TYPE_BLKCIPHER Synchronous multi-block cipher</para>
463+ </listitem>
464+ <listitem>
465+ <para>CRYPTO_ALG_TYPE_ABLKCIPHER Asynchronous multi-block cipher</para>
466+ </listitem>
467+ <listitem>
468+ <para>CRYPTO_ALG_TYPE_GIVCIPHER Asynchronous multi-block
469+ cipher packed together with an IV generator (see geniv field
470+ in the /proc/crypto listing for the known IV generators)</para>
471+ </listitem>
472+ <listitem>
473+ <para>CRYPTO_ALG_TYPE_DIGEST Raw message digest</para>
474+ </listitem>
475+ <listitem>
476+ <para>CRYPTO_ALG_TYPE_HASH Alias for CRYPTO_ALG_TYPE_DIGEST</para>
477+ </listitem>
478+ <listitem>
479+ <para>CRYPTO_ALG_TYPE_SHASH Synchronous multi-block hash</para>
480+ </listitem>
481+ <listitem>
482+ <para>CRYPTO_ALG_TYPE_AHASH Asynchronous multi-block hash</para>
483+ </listitem>
484+ <listitem>
485+ <para>CRYPTO_ALG_TYPE_RNG Random Number Generation</para>
486+ </listitem>
487+ <listitem>
488+ <para>CRYPTO_ALG_TYPE_PCOMPRESS Enhanced version of
489+ CRYPTO_ALG_TYPE_COMPRESS allowing for segmented compression /
490+ decompression instead of performing the operation on one
491+ segment only. CRYPTO_ALG_TYPE_PCOMPRESS is intended to replace
492+ CRYPTO_ALG_TYPE_COMPRESS once existing consumers are converted.</para>
493+ </listitem>
494+ </itemizedlist>
495+
496+ <para>
497+ The mask flag restricts the type of cipher. The only allowed
498+ flag is CRYPTO_ALG_ASYNC to restrict the cipher lookup function
499+ to asynchronous ciphers. Usually, a caller provides a 0 for the
500+ mask flag.
501+ </para>
502+
503+ <para>
504+ When the caller provides a mask and type specification, the
505+ caller limits the search the kernel crypto API can perform for
506+ a suitable cipher implementation for the given cipher name.
507+ That means, even when a caller uses a cipher name that exists
508+ during its initialization call, the kernel crypto API may not
509+ select it due to the used type and mask field.
510+ </para>
511+ </sect1>
512+ </chapter>
513+
514+ <chapter id="Development"><title>Developing Cipher Algorithms</title>
515+ <sect1><title>Registering And Unregistering Transformation</title>
516+ <para>
517+ There are three distinct types of registration functions in
518+ the Crypto API. One is used to register a generic cryptographic
519+ transformation, while the other two are specific to HASH
520+ transformations and COMPRESSion. We will discuss the latter
521+ two in a separate chapter, here we will only look at the
522+ generic ones.
523+ </para>
524+
525+ <para>
526+ Before discussing the register functions, the data structure
527+ to be filled with each, struct crypto_alg, must be considered
528+ -- see below for a description of this data structure.
529+ </para>
530+
531+ <para>
532+ The generic registration functions can be found in
533+ include/linux/crypto.h and their definition can be seen below.
534+ The former function registers a single transformation, while
535+ the latter works on an array of transformation descriptions.
536+ The latter is useful when registering transformations in bulk.
537+ </para>
538+
539+ <programlisting>
540+ int crypto_register_alg(struct crypto_alg *alg);
541+ int crypto_register_algs(struct crypto_alg *algs, int count);
542+ </programlisting>
543+
544+ <para>
545+ The counterparts to those functions are listed below.
546+ </para>
547+
548+ <programlisting>
549+ int crypto_unregister_alg(struct crypto_alg *alg);
550+ int crypto_unregister_algs(struct crypto_alg *algs, int count);
551+ </programlisting>
552+
553+ <para>
554+ Notice that both registration and unregistration functions
555+ do return a value, so make sure to handle errors. A return
556+ code of zero implies success. Any return code &lt; 0 implies
557+ an error.
558+ </para>
559+
560+ <para>
561+ The bulk registration / unregistration functions require
562+ that struct crypto_alg is an array of count size. These
563+ functions simply loop over that array and register /
564+ unregister each individual algorithm. If an error occurs,
565+ the loop is terminated at the offending algorithm definition.
566+ That means, the algorithms prior to the offending algorithm
567+ are successfully registered. Note, the caller has no way of
568+ knowing which cipher implementations have successfully
569+ registered. If this is important to know, the caller should
570+ loop through the different implementations using the single
571+ instance *_alg functions for each individual implementation.
572+ </para>
573+ </sect1>
574+
575+ <sect1><title>Single-Block Symmetric Ciphers [CIPHER]</title>
576+ <para>
577+ Example of transformations: aes, arc4, ...
578+ </para>
579+
580+ <para>
581+ This section describes the simplest of all transformation
582+ implementations, that being the CIPHER type used for symmetric
583+ ciphers. The CIPHER type is used for transformations which
584+ operate on exactly one block at a time and there are no
585+ dependencies between blocks at all.
586+ </para>
587+
588+ <sect2><title>Registration specifics</title>
589+ <para>
590+ The registration of [CIPHER] algorithm is specific in that
591+ struct crypto_alg field .cra_type is empty. The .cra_u.cipher
592+ has to be filled in with proper callbacks to implement this
593+ transformation.
594+ </para>
595+
596+ <para>
597+ See struct cipher_alg below.
598+ </para>
599+ </sect2>
600+
601+ <sect2><title>Cipher Definition With struct cipher_alg</title>
602+ <para>
603+ Struct cipher_alg defines a single block cipher.
604+ </para>
605+
606+ <para>
607+ Here are schematics of how these functions are called when
608+ operated from other part of the kernel. Note that the
609+ .cia_setkey() call might happen before or after any of these
610+ schematics happen, but must not happen during any of these
611+ are in-flight.
612+ </para>
613+
614+ <para>
615+ <programlisting>
616+ KEY ---. PLAINTEXT ---.
617+ v v
618+ .cia_setkey() -&gt; .cia_encrypt()
619+ |
620+ '-----&gt; CIPHERTEXT
621+ </programlisting>
622+ </para>
623+
624+ <para>
625+ Please note that a pattern where .cia_setkey() is called
626+ multiple times is also valid:
627+ </para>
628+
629+ <para>
630+ <programlisting>
631+
632+ KEY1 --. PLAINTEXT1 --. KEY2 --. PLAINTEXT2 --.
633+ v v v v
634+ .cia_setkey() -&gt; .cia_encrypt() -&gt; .cia_setkey() -&gt; .cia_encrypt()
635+ | |
636+ '---&gt; CIPHERTEXT1 '---&gt; CIPHERTEXT2
637+ </programlisting>
638+ </para>
639+
640+ </sect2>
641+ </sect1>
642+
643+ <sect1><title>Multi-Block Ciphers [BLKCIPHER] [ABLKCIPHER]</title>
644+ <para>
645+ Example of transformations: cbc(aes), ecb(arc4), ...
646+ </para>
647+
648+ <para>
649+ This section describes the multi-block cipher transformation
650+ implementations for both synchronous [BLKCIPHER] and
651+ asynchronous [ABLKCIPHER] case. The multi-block ciphers are
652+ used for transformations which operate on scatterlists of
653+ data supplied to the transformation functions. They output
654+ the result into a scatterlist of data as well.
655+ </para>
656+
657+ <sect2><title>Registration Specifics</title>
658+
659+ <para>
660+ The registration of [BLKCIPHER] or [ABLKCIPHER] algorithms
661+ is one of the most standard procedures throughout the crypto API.
662+ </para>
663+
664+ <para>
665+ Note, if a cipher implementation requires a proper alignment
666+ of data, the caller should use the functions of
667+ crypto_blkcipher_alignmask() or crypto_ablkcipher_alignmask()
668+ respectively to identify a memory alignment mask. The kernel
669+ crypto API is able to process requests that are unaligned.
670+ This implies, however, additional overhead as the kernel
671+ crypto API needs to perform the realignment of the data which
672+ may imply moving of data.
673+ </para>
674+ </sect2>
675+
676+ <sect2><title>Cipher Definition With struct blkcipher_alg and ablkcipher_alg</title>
677+ <para>
678+ Struct blkcipher_alg defines a synchronous block cipher whereas
679+ struct ablkcipher_alg defines an asynchronous block cipher.
680+ </para>
681+
682+ <para>
683+ Please refer to the single block cipher description for schematics
684+ of the block cipher usage. The usage patterns are exactly the same
685+ for [ABLKCIPHER] and [BLKCIPHER] as they are for plain [CIPHER].
686+ </para>
687+ </sect2>
688+
689+ <sect2><title>Specifics Of Asynchronous Multi-Block Cipher</title>
690+ <para>
691+ There are a couple of specifics to the [ABLKCIPHER] interface.
692+ </para>
693+
694+ <para>
695+ First of all, some of the drivers will want to use the
696+ Generic ScatterWalk in case the hardware needs to be fed
697+ separate chunks of the scatterlist which contains the
698+ plaintext and will contain the ciphertext. Please refer
699+ to the ScatterWalk interface offered by the Linux kernel
700+ scatter / gather list implementation.
701+ </para>
702+ </sect2>
703+ </sect1>
704+
705+ <sect1><title>Hashing [HASH]</title>
706+
707+ <para>
708+ Example of transformations: crc32, md5, sha1, sha256,...
709+ </para>
710+
711+ <sect2><title>Registering And Unregistering The Transformation</title>
712+
713+ <para>
714+ There are multiple ways to register a HASH transformation,
715+ depending on whether the transformation is synchronous [SHASH]
716+ or asynchronous [AHASH] and the amount of HASH transformations
717+ we are registering. You can find the prototypes defined in
718+ include/crypto/internal/hash.h:
719+ </para>
720+
721+ <programlisting>
722+ int crypto_register_ahash(struct ahash_alg *alg);
723+
724+ int crypto_register_shash(struct shash_alg *alg);
725+ int crypto_register_shashes(struct shash_alg *algs, int count);
726+ </programlisting>
727+
728+ <para>
729+ The respective counterparts for unregistering the HASH
730+ transformation are as follows:
731+ </para>
732+
733+ <programlisting>
734+ int crypto_unregister_ahash(struct ahash_alg *alg);
735+
736+ int crypto_unregister_shash(struct shash_alg *alg);
737+ int crypto_unregister_shashes(struct shash_alg *algs, int count);
738+ </programlisting>
739+ </sect2>
740+
741+ <sect2><title>Cipher Definition With struct shash_alg and ahash_alg</title>
742+ <para>
743+ Here are schematics of how these functions are called when
744+ operated from other part of the kernel. Note that the .setkey()
745+ call might happen before or after any of these schematics happen,
746+ but must not happen during any of these are in-flight. Please note
747+ that calling .init() followed immediately by .finish() is also a
748+ perfectly valid transformation.
749+ </para>
750+
751+ <programlisting>
752+ I) DATA -----------.
753+ v
754+ .init() -&gt; .update() -&gt; .final() ! .update() might not be called
755+ ^ | | at all in this scenario.
756+ '----' '---&gt; HASH
757+
758+ II) DATA -----------.-----------.
759+ v v
760+ .init() -&gt; .update() -&gt; .finup() ! .update() may not be called
761+ ^ | | at all in this scenario.
762+ '----' '---&gt; HASH
763+
764+ III) DATA -----------.
765+ v
766+ .digest() ! The entire process is handled
767+ | by the .digest() call.
768+ '---------------&gt; HASH
769+ </programlisting>
770+
771+ <para>
772+ Here is a schematic of how the .export()/.import() functions are
773+ called when used from another part of the kernel.
774+ </para>
775+
776+ <programlisting>
777+ KEY--. DATA--.
778+ v v ! .update() may not be called
779+ .setkey() -&gt; .init() -&gt; .update() -&gt; .export() at all in this scenario.
780+ ^ | |
781+ '-----' '--&gt; PARTIAL_HASH
782+
783+ ----------- other transformations happen here -----------
784+
785+ PARTIAL_HASH--. DATA1--.
786+ v v
787+ .import -&gt; .update() -&gt; .final() ! .update() may not be called
788+ ^ | | at all in this scenario.
789+ '----' '--&gt; HASH1
790+
791+ PARTIAL_HASH--. DATA2-.
792+ v v
793+ .import -&gt; .finup()
794+ |
795+ '---------------&gt; HASH2
796+ </programlisting>
797+ </sect2>
798+
799+ <sect2><title>Specifics Of Asynchronous HASH Transformation</title>
800+ <para>
801+ Some of the drivers will want to use the Generic ScatterWalk
802+ in case the implementation needs to be fed separate chunks of the
803+ scatterlist which contains the input data. The buffer containing
804+ the resulting hash will always be properly aligned to
805+ .cra_alignmask so there is no need to worry about this.
806+ </para>
807+ </sect2>
808+ </sect1>
809+ </chapter>
810+
811+ <chapter id="API"><title>Programming Interface</title>
812+ <sect1><title>Block Cipher Context Data Structures</title>
813+!Pinclude/linux/crypto.h Block Cipher Context Data Structures
814+!Finclude/linux/crypto.h aead_request
815+ </sect1>
816+ <sect1><title>Block Cipher Algorithm Definitions</title>
817+!Pinclude/linux/crypto.h Block Cipher Algorithm Definitions
818+!Finclude/linux/crypto.h crypto_alg
819+!Finclude/linux/crypto.h ablkcipher_alg
820+!Finclude/linux/crypto.h aead_alg
821+!Finclude/linux/crypto.h blkcipher_alg
822+!Finclude/linux/crypto.h cipher_alg
823+!Finclude/linux/crypto.h rng_alg
824+ </sect1>
825+ <sect1><title>Asynchronous Block Cipher API</title>
826+!Pinclude/linux/crypto.h Asynchronous Block Cipher API
827+!Finclude/linux/crypto.h crypto_alloc_ablkcipher
828+!Finclude/linux/crypto.h crypto_free_ablkcipher
829+!Finclude/linux/crypto.h crypto_has_ablkcipher
830+!Finclude/linux/crypto.h crypto_ablkcipher_ivsize
831+!Finclude/linux/crypto.h crypto_ablkcipher_blocksize
832+!Finclude/linux/crypto.h crypto_ablkcipher_setkey
833+!Finclude/linux/crypto.h crypto_ablkcipher_reqtfm
834+!Finclude/linux/crypto.h crypto_ablkcipher_encrypt
835+!Finclude/linux/crypto.h crypto_ablkcipher_decrypt
836+ </sect1>
837+ <sect1><title>Asynchronous Cipher Request Handle</title>
838+!Pinclude/linux/crypto.h Asynchronous Cipher Request Handle
839+!Finclude/linux/crypto.h crypto_ablkcipher_reqsize
840+!Finclude/linux/crypto.h ablkcipher_request_set_tfm
841+!Finclude/linux/crypto.h ablkcipher_request_alloc
842+!Finclude/linux/crypto.h ablkcipher_request_free
843+!Finclude/linux/crypto.h ablkcipher_request_set_callback
844+!Finclude/linux/crypto.h ablkcipher_request_set_crypt
845+ </sect1>
846+ <sect1><title>Authenticated Encryption With Associated Data (AEAD) Cipher API</title>
847+!Pinclude/linux/crypto.h Authenticated Encryption With Associated Data (AEAD) Cipher API
848+!Finclude/linux/crypto.h crypto_alloc_aead
849+!Finclude/linux/crypto.h crypto_free_aead
850+!Finclude/linux/crypto.h crypto_aead_ivsize
851+!Finclude/linux/crypto.h crypto_aead_authsize
852+!Finclude/linux/crypto.h crypto_aead_blocksize
853+!Finclude/linux/crypto.h crypto_aead_setkey
854+!Finclude/linux/crypto.h crypto_aead_setauthsize
855+!Finclude/linux/crypto.h crypto_aead_encrypt
856+!Finclude/linux/crypto.h crypto_aead_decrypt
857+ </sect1>
858+ <sect1><title>Asynchronous AEAD Request Handle</title>
859+!Pinclude/linux/crypto.h Asynchronous AEAD Request Handle
860+!Finclude/linux/crypto.h crypto_aead_reqsize
861+!Finclude/linux/crypto.h aead_request_set_tfm
862+!Finclude/linux/crypto.h aead_request_alloc
863+!Finclude/linux/crypto.h aead_request_free
864+!Finclude/linux/crypto.h aead_request_set_callback
865+!Finclude/linux/crypto.h aead_request_set_crypt
866+!Finclude/linux/crypto.h aead_request_set_assoc
867+ </sect1>
868+ <sect1><title>Synchronous Block Cipher API</title>
869+!Pinclude/linux/crypto.h Synchronous Block Cipher API
870+!Finclude/linux/crypto.h crypto_alloc_blkcipher
871+!Finclude/linux/crypto.h crypto_free_blkcipher
872+!Finclude/linux/crypto.h crypto_has_blkcipher
873+!Finclude/linux/crypto.h crypto_blkcipher_name
874+!Finclude/linux/crypto.h crypto_blkcipher_ivsize
875+!Finclude/linux/crypto.h crypto_blkcipher_blocksize
876+!Finclude/linux/crypto.h crypto_blkcipher_setkey
877+!Finclude/linux/crypto.h crypto_blkcipher_encrypt
878+!Finclude/linux/crypto.h crypto_blkcipher_encrypt_iv
879+!Finclude/linux/crypto.h crypto_blkcipher_decrypt
880+!Finclude/linux/crypto.h crypto_blkcipher_decrypt_iv
881+!Finclude/linux/crypto.h crypto_blkcipher_set_iv
882+!Finclude/linux/crypto.h crypto_blkcipher_get_iv
883+ </sect1>
884+ <sect1><title>Single Block Cipher API</title>
885+!Pinclude/linux/crypto.h Single Block Cipher API
886+!Finclude/linux/crypto.h crypto_alloc_cipher
887+!Finclude/linux/crypto.h crypto_free_cipher
888+!Finclude/linux/crypto.h crypto_has_cipher
889+!Finclude/linux/crypto.h crypto_cipher_blocksize
890+!Finclude/linux/crypto.h crypto_cipher_setkey
891+!Finclude/linux/crypto.h crypto_cipher_encrypt_one
892+!Finclude/linux/crypto.h crypto_cipher_decrypt_one
893+ </sect1>
894+ <sect1><title>Synchronous Message Digest API</title>
895+!Pinclude/linux/crypto.h Synchronous Message Digest API
896+!Finclude/linux/crypto.h crypto_alloc_hash
897+!Finclude/linux/crypto.h crypto_free_hash
898+!Finclude/linux/crypto.h crypto_has_hash
899+!Finclude/linux/crypto.h crypto_hash_blocksize
900+!Finclude/linux/crypto.h crypto_hash_digestsize
901+!Finclude/linux/crypto.h crypto_hash_init
902+!Finclude/linux/crypto.h crypto_hash_update
903+!Finclude/linux/crypto.h crypto_hash_final
904+!Finclude/linux/crypto.h crypto_hash_digest
905+!Finclude/linux/crypto.h crypto_hash_setkey
906+ </sect1>
907+ <sect1><title>Message Digest Algorithm Definitions</title>
908+!Pinclude/crypto/hash.h Message Digest Algorithm Definitions
909+!Finclude/crypto/hash.h hash_alg_common
910+!Finclude/crypto/hash.h ahash_alg
911+!Finclude/crypto/hash.h shash_alg
912+ </sect1>
913+ <sect1><title>Asynchronous Message Digest API</title>
914+!Pinclude/crypto/hash.h Asynchronous Message Digest API
915+!Finclude/crypto/hash.h crypto_alloc_ahash
916+!Finclude/crypto/hash.h crypto_free_ahash
917+!Finclude/crypto/hash.h crypto_ahash_init
918+!Finclude/crypto/hash.h crypto_ahash_digestsize
919+!Finclude/crypto/hash.h crypto_ahash_reqtfm
920+!Finclude/crypto/hash.h crypto_ahash_reqsize
921+!Finclude/crypto/hash.h crypto_ahash_setkey
922+!Finclude/crypto/hash.h crypto_ahash_finup
923+!Finclude/crypto/hash.h crypto_ahash_final
924+!Finclude/crypto/hash.h crypto_ahash_digest
925+!Finclude/crypto/hash.h crypto_ahash_export
926+!Finclude/crypto/hash.h crypto_ahash_import
927+ </sect1>
928+ <sect1><title>Asynchronous Hash Request Handle</title>
929+!Pinclude/crypto/hash.h Asynchronous Hash Request Handle
930+!Finclude/crypto/hash.h ahash_request_set_tfm
931+!Finclude/crypto/hash.h ahash_request_alloc
932+!Finclude/crypto/hash.h ahash_request_free
933+!Finclude/crypto/hash.h ahash_request_set_callback
934+!Finclude/crypto/hash.h ahash_request_set_crypt
935+ </sect1>
936+ <sect1><title>Synchronous Message Digest API</title>
937+!Pinclude/crypto/hash.h Synchronous Message Digest API
938+!Finclude/crypto/hash.h crypto_alloc_shash
939+!Finclude/crypto/hash.h crypto_free_shash
940+!Finclude/crypto/hash.h crypto_shash_blocksize
941+!Finclude/crypto/hash.h crypto_shash_digestsize
942+!Finclude/crypto/hash.h crypto_shash_descsize
943+!Finclude/crypto/hash.h crypto_shash_setkey
944+!Finclude/crypto/hash.h crypto_shash_digest
945+!Finclude/crypto/hash.h crypto_shash_export
946+!Finclude/crypto/hash.h crypto_shash_import
947+!Finclude/crypto/hash.h crypto_shash_init
948+!Finclude/crypto/hash.h crypto_shash_update
949+!Finclude/crypto/hash.h crypto_shash_final
950+!Finclude/crypto/hash.h crypto_shash_finup
951+ </sect1>
952+ <sect1><title>Crypto API Random Number API</title>
953+!Pinclude/crypto/rng.h Random number generator API
954+!Finclude/crypto/rng.h crypto_alloc_rng
955+!Finclude/crypto/rng.h crypto_rng_alg
956+!Finclude/crypto/rng.h crypto_free_rng
957+!Finclude/crypto/rng.h crypto_rng_get_bytes
958+!Finclude/crypto/rng.h crypto_rng_reset
959+!Finclude/crypto/rng.h crypto_rng_seedsize
960+!Cinclude/crypto/rng.h
961+ </sect1>
962+ </chapter>
963+
964+ <chapter id="Code"><title>Code Examples</title>
965+ <sect1><title>Code Example For Asynchronous Block Cipher Operation</title>
966+ <programlisting>
967+
968+struct tcrypt_result {
969+ struct completion completion;
970+ int err;
971+};
972+
973+/* tie all data structures together */
974+struct ablkcipher_def {
975+ struct scatterlist sg;
976+ struct crypto_ablkcipher *tfm;
977+ struct ablkcipher_request *req;
978+ struct tcrypt_result result;
979+};
980+
981+/* Callback function */
982+static void test_ablkcipher_cb(struct crypto_async_request *req, int error)
983+{
984+ struct tcrypt_result *result = req-&gt;data;
985+
986+ if (error == -EINPROGRESS)
987+ return;
988+ result-&gt;err = error;
989+ complete(&amp;result-&gt;completion);
990+ pr_info("Encryption finished successfully\n");
991+}
992+
993+/* Perform cipher operation */
994+static unsigned int test_ablkcipher_encdec(struct ablkcipher_def *ablk,
995+ int enc)
996+{
997+ int rc = 0;
998+
999+ if (enc)
1000+ rc = crypto_ablkcipher_encrypt(ablk-&gt;req);
1001+ else
1002+ rc = crypto_ablkcipher_decrypt(ablk-&gt;req);
1003+
1004+ switch (rc) {
1005+ case 0:
1006+ break;
1007+ case -EINPROGRESS:
1008+ case -EBUSY:
1009+ rc = wait_for_completion_interruptible(
1010+ &amp;ablk-&gt;result.completion);
1011+ if (!rc &amp;&amp; !ablk-&gt;result.err) {
1012+ reinit_completion(&amp;ablk-&gt;result.completion);
1013+ break;
1014+ }
1015+ default:
1016+ pr_info("ablkcipher encrypt returned with %d result %d\n",
1017+ rc, ablk-&gt;result.err);
1018+ break;
1019+ }
1020+ init_completion(&amp;ablk-&gt;result.completion);
1021+
1022+ return rc;
1023+}
1024+
1025+/* Initialize and trigger cipher operation */
1026+static int test_ablkcipher(void)
1027+{
1028+ struct ablkcipher_def ablk;
1029+ struct crypto_ablkcipher *ablkcipher = NULL;
1030+ struct ablkcipher_request *req = NULL;
1031+ char *scratchpad = NULL;
1032+ char *ivdata = NULL;
1033+ unsigned char key[32];
1034+ int ret = -EFAULT;
1035+
1036+ ablkcipher = crypto_alloc_ablkcipher("cbc-aes-aesni", 0, 0);
1037+ if (IS_ERR(ablkcipher)) {
1038+ pr_info("could not allocate ablkcipher handle\n");
1039+ return PTR_ERR(ablkcipher);
1040+ }
1041+
1042+ req = ablkcipher_request_alloc(ablkcipher, GFP_KERNEL);
1043+ if (IS_ERR(req)) {
1044+ pr_info("could not allocate request queue\n");
1045+ ret = PTR_ERR(req);
1046+ goto out;
1047+ }
1048+
1049+ ablkcipher_request_set_callback(req, CRYPTO_TFM_REQ_MAY_BACKLOG,
1050+ test_ablkcipher_cb,
1051+ &amp;ablk.result);
1052+
1053+ /* AES 256 with random key */
1054+ get_random_bytes(&amp;key, 32);
1055+ if (crypto_ablkcipher_setkey(ablkcipher, key, 32)) {
1056+ pr_info("key could not be set\n");
1057+ ret = -EAGAIN;
1058+ goto out;
1059+ }
1060+
1061+ /* IV will be random */
1062+ ivdata = kmalloc(16, GFP_KERNEL);
1063+ if (!ivdata) {
1064+ pr_info("could not allocate ivdata\n");
1065+ goto out;
1066+ }
1067+ get_random_bytes(ivdata, 16);
1068+
1069+ /* Input data will be random */
1070+ scratchpad = kmalloc(16, GFP_KERNEL);
1071+ if (!scratchpad) {
1072+ pr_info("could not allocate scratchpad\n");
1073+ goto out;
1074+ }
1075+ get_random_bytes(scratchpad, 16);
1076+
1077+ ablk.tfm = ablkcipher;
1078+ ablk.req = req;
1079+
1080+ /* We encrypt one block */
1081+ sg_init_one(&amp;ablk.sg, scratchpad, 16);
1082+ ablkcipher_request_set_crypt(req, &amp;ablk.sg, &amp;ablk.sg, 16, ivdata);
1083+ init_completion(&amp;ablk.result.completion);
1084+
1085+ /* encrypt data */
1086+ ret = test_ablkcipher_encdec(&amp;ablk, 1);
1087+ if (ret)
1088+ goto out;
1089+
1090+ pr_info("Encryption triggered successfully\n");
1091+
1092+out:
1093+ if (ablkcipher)
1094+ crypto_free_ablkcipher(ablkcipher);
1095+ if (req)
1096+ ablkcipher_request_free(req);
1097+ if (ivdata)
1098+ kfree(ivdata);
1099+ if (scratchpad)
1100+ kfree(scratchpad);
1101+ return ret;
1102+}
1103+ </programlisting>
1104+ </sect1>
1105+
1106+ <sect1><title>Code Example For Synchronous Block Cipher Operation</title>
1107+ <programlisting>
1108+
1109+static int test_blkcipher(void)
1110+{
1111+ struct crypto_blkcipher *blkcipher = NULL;
1112+ char *cipher = "cbc(aes)";
1113+ // AES 128
1114+ charkey =
1115+"\x12\x34\x56\x78\x90\xab\xcd\xef\x12\x34\x56\x78\x90\xab\xcd\xef";
1116+ chariv =
1117+"\x12\x34\x56\x78\x90\xab\xcd\xef\x12\x34\x56\x78\x90\xab\xcd\xef";
1118+ unsigned int ivsize = 0;
1119+ char *scratchpad = NULL; // holds plaintext and ciphertext
1120+ struct scatterlist sg;
1121+ struct blkcipher_desc desc;
1122+ int ret = -EFAULT;
1123+
1124+ blkcipher = crypto_alloc_blkcipher(cipher, 0, 0);
1125+ if (IS_ERR(blkcipher)) {
1126+ printk("could not allocate blkcipher handle for %s\n", cipher);
1127+ return -PTR_ERR(blkcipher);
1128+ }
1129+
1130+ if (crypto_blkcipher_setkey(blkcipher, key, strlen(key))) {
1131+ printk("key could not be set\n");
1132+ ret = -EAGAIN;
1133+ goto out;
1134+ }
1135+
1136+ ivsize = crypto_blkcipher_ivsize(blkcipher);
1137+ if (ivsize) {
1138+ if (ivsize != strlen(iv))
1139+ printk("IV length differs from expected length\n");
1140+ crypto_blkcipher_set_iv(blkcipher, iv, ivsize);
1141+ }
1142+
1143+ scratchpad = kmalloc(crypto_blkcipher_blocksize(blkcipher), GFP_KERNEL);
1144+ if (!scratchpad) {
1145+ printk("could not allocate scratchpad for %s\n", cipher);
1146+ goto out;
1147+ }
1148+ /* get some random data that we want to encrypt */
1149+ get_random_bytes(scratchpad, crypto_blkcipher_blocksize(blkcipher));
1150+
1151+ desc.flags = 0;
1152+ desc.tfm = blkcipher;
1153+ sg_init_one(&amp;sg, scratchpad, crypto_blkcipher_blocksize(blkcipher));
1154+
1155+ /* encrypt data in place */
1156+ crypto_blkcipher_encrypt(&amp;desc, &amp;sg, &amp;sg,
1157+ crypto_blkcipher_blocksize(blkcipher));
1158+
1159+ /* decrypt data in place
1160+ * crypto_blkcipher_decrypt(&amp;desc, &amp;sg, &amp;sg,
1161+ */ crypto_blkcipher_blocksize(blkcipher));
1162+
1163+
1164+ printk("Cipher operation completed\n");
1165+ return 0;
1166+
1167+out:
1168+ if (blkcipher)
1169+ crypto_free_blkcipher(blkcipher);
1170+ if (scratchpad)
1171+ kzfree(scratchpad);
1172+ return ret;
1173+}
1174+ </programlisting>
1175+ </sect1>
1176+
1177+ <sect1><title>Code Example For Use of Operational State Memory With SHASH</title>
1178+ <programlisting>
1179+
1180+struct sdesc {
1181+ struct shash_desc shash;
1182+ char ctx[];
1183+};
1184+
1185+static struct sdescinit_sdesc(struct crypto_shash *alg)
1186+{
1187+ struct sdescsdesc;
1188+ int size;
1189+
1190+ size = sizeof(struct shash_desc) + crypto_shash_descsize(alg);
1191+ sdesc = kmalloc(size, GFP_KERNEL);
1192+ if (!sdesc)
1193+ return ERR_PTR(-ENOMEM);
1194+ sdesc-&gt;shash.tfm = alg;
1195+ sdesc-&gt;shash.flags = 0x0;
1196+ return sdesc;
1197+}
1198+
1199+static int calc_hash(struct crypto_shashalg,
1200+ const unsigned chardata, unsigned int datalen,
1201+ unsigned chardigest) {
1202+ struct sdescsdesc;
1203+ int ret;
1204+
1205+ sdesc = init_sdesc(alg);
1206+ if (IS_ERR(sdesc)) {
1207+ pr_info("trusted_key: can't alloc %s\n", hash_alg);
1208+ return PTR_ERR(sdesc);
1209+ }
1210+
1211+ ret = crypto_shash_digest(&amp;sdesc-&gt;shash, data, datalen, digest);
1212+ kfree(sdesc);
1213+ return ret;
1214+}
1215+ </programlisting>
1216+ </sect1>
1217+
1218+ <sect1><title>Code Example For Random Number Generator Usage</title>
1219+ <programlisting>
1220+
1221+static int get_random_numbers(u8 *buf, unsigned int len)
1222+{
1223+ struct crypto_rngrng = NULL;
1224+ chardrbg = "drbg_nopr_sha256"; /* Hash DRBG with SHA-256, no PR */
1225+ int ret;
1226+
1227+ if (!buf || !len) {
1228+ pr_debug("No output buffer provided\n");
1229+ return -EINVAL;
1230+ }
1231+
1232+ rng = crypto_alloc_rng(drbg, 0, 0);
1233+ if (IS_ERR(rng)) {
1234+ pr_debug("could not allocate RNG handle for %s\n", drbg);
1235+ return -PTR_ERR(rng);
1236+ }
1237+
1238+ ret = crypto_rng_get_bytes(rng, buf, len);
1239+ if (ret &lt; 0)
1240+ pr_debug("generation of random numbers failed\n");
1241+ else if (ret == 0)
1242+ pr_debug("RNG returned no data");
1243+ else
1244+ pr_debug("RNG returned %d bytes of data\n", ret);
1245+
1246+out:
1247+ crypto_free_rng(rng);
1248+ return ret;
1249+}
1250+ </programlisting>
1251+ </sect1>
1252+ </chapter>
1253+ </book>
Documentation/DocBook/drm.tmpl+306−144
@@ -291,10 +291,9 @@ char *date;</synopsis> · 290 unmodified lines
291291 <title>Device Registration</title>
292292 <para>
293293 A number of functions are provided to help with device registration.
294− The functions deal with PCI, USB and platform devices, respectively.
294+ The functions deal with PCI and platform devices, respectively.
295295 </para>
296296 !Edrivers/gpu/drm/drm_pci.c
297−!Edrivers/gpu/drm/drm_usb.c
298297 !Edrivers/gpu/drm/drm_platform.c
299298 <para>
300299 New drivers that no longer rely on the services provided by the
@@ -493,10 +492,10 @@ char *date;</synopsis> · 192 unmodified lines
493492 <sect2>
494493 <title>The Translation Table Manager (TTM)</title>
495494 <para>
496− TTM design background and information belongs here.
495+ TTM design background and information belongs here.
497496 </para>
498497 <sect3>
499− <title>TTM initialization</title>
498+ <title>TTM initialization</title>
500499 <warning><para>This section is outdated.</para></warning>
501500 <para>
502501 Drivers wishing to support TTM must fill out a drm_bo_driver
@@ -504,42 +503,42 @@ char *date;</synopsis> · 1 unmodified line
504503 pointers for initializing the TTM, allocating and freeing memory,
505504 waiting for command completion and fence synchronization, and memory
506505 migration. See the radeon_ttm.c file for an example of usage.
507− </para>
508− <para>
509− The ttm_global_reference structure is made up of several fields:
510− </para>
511− <programlisting>
512− struct ttm_global_reference {
513− enum ttm_global_types global_type;
514− size_t size;
515− void *object;
516− int (*init) (struct ttm_global_reference *);
517− void (*release) (struct ttm_global_reference *);
518− };
519− </programlisting>
520− <para>
521− There should be one global reference structure for your memory
522− manager as a whole, and there will be others for each object
523− created by the memory manager at runtime. Your global TTM should
524− have a type of TTM_GLOBAL_TTM_MEM. The size field for the global
525− object should be sizeof(struct ttm_mem_global), and the init and
526− release hooks should point at your driver-specific init and
527− release routines, which probably eventually call
528− ttm_mem_global_init and ttm_mem_global_release, respectively.
529− </para>
530− <para>
531− Once your global TTM accounting structure is set up and initialized
532− by calling ttm_global_item_ref() on it,
533− you need to create a buffer object TTM to
534− provide a pool for buffer object allocation by clients and the
535− kernel itself. The type of this object should be TTM_GLOBAL_TTM_BO,
536− and its size should be sizeof(struct ttm_bo_global). Again,
537− driver-specific init and release functions may be provided,
538− likely eventually calling ttm_bo_global_init() and
539− ttm_bo_global_release(), respectively. Also, like the previous
540− object, ttm_global_item_ref() is used to create an initial reference
541− count for the TTM, which will call your initialization function.
542− </para>
506+ </para>
507+ <para>
508+ The ttm_global_reference structure is made up of several fields:
509+ </para>
510+ <programlisting>
511+ struct ttm_global_reference {
512+ enum ttm_global_types global_type;
513+ size_t size;
514+ void *object;
515+ int (*init) (struct ttm_global_reference *);
516+ void (*release) (struct ttm_global_reference *);
517+ };
518+ </programlisting>
519+ <para>
520+ There should be one global reference structure for your memory
521+ manager as a whole, and there will be others for each object
522+ created by the memory manager at runtime. Your global TTM should
523+ have a type of TTM_GLOBAL_TTM_MEM. The size field for the global
524+ object should be sizeof(struct ttm_mem_global), and the init and
525+ release hooks should point at your driver-specific init and
526+ release routines, which probably eventually call
527+ ttm_mem_global_init and ttm_mem_global_release, respectively.
528+ </para>
529+ <para>
530+ Once your global TTM accounting structure is set up and initialized
531+ by calling ttm_global_item_ref() on it,
532+ you need to create a buffer object TTM to
533+ provide a pool for buffer object allocation by clients and the
534+ kernel itself. The type of this object should be TTM_GLOBAL_TTM_BO,
535+ and its size should be sizeof(struct ttm_bo_global). Again,
536+ driver-specific init and release functions may be provided,
537+ likely eventually calling ttm_bo_global_init() and
538+ ttm_bo_global_release(), respectively. Also, like the previous
539+ object, ttm_global_item_ref() is used to create an initial reference
540+ count for the TTM, which will call your initialization function.
541+ </para>
543542 </sect3>
544543 </sect2>
545544 <sect2 id="drm-gem">
@@ -567,19 +566,19 @@ char *date;</synopsis> · 21 unmodified lines
567566 using driver-specific ioctls.
568567 </para>
569568 <para>
570− On a fundamental level, GEM involves several operations:
571− <itemizedlist>
572− <listitem>Memory allocation and freeing</listitem>
573− <listitem>Command execution</listitem>
574− <listitem>Aperture management at command execution time</listitem>
575− </itemizedlist>
576− Buffer object allocation is relatively straightforward and largely
569+ On a fundamental level, GEM involves several operations:
570+ <itemizedlist>
571+ <listitem>Memory allocation and freeing</listitem>
572+ <listitem>Command execution</listitem>
573+ <listitem>Aperture management at command execution time</listitem>
574+ </itemizedlist>
575+ Buffer object allocation is relatively straightforward and largely
577576 provided by Linux's shmem layer, which provides memory to back each
578577 object.
579578 </para>
580579 <para>
581580 Device-specific operations, such as command execution, pinning, buffer
582− read &amp; write, mapping, and domain ownership transfers are left to
581+ read &amp; write, mapping, and domain ownership transfers are left to
583582 driver-specific ioctls.
584583 </para>
585584 <sect3>
@@ -739,16 +738,16 @@ char *date;</synopsis> · 153 unmodified lines
739738 respectively. The conversion is handled by the DRM core without any
740739 driver-specific support.
741740 </para>
742− <para>
743− GEM also supports buffer sharing with dma-buf file descriptors through
744− PRIME. GEM-based drivers must use the provided helpers functions to
745− implement the exporting and importing correctly. See <xref linkend="drm-prime-support" />.
746− Since sharing file descriptors is inherently more secure than the
747− easily guessable and global GEM names it is the preferred buffer
748− sharing mechanism. Sharing buffers through GEM names is only supported
749− for legacy userspace. Furthermore PRIME also allows cross-device
750− buffer sharing since it is based on dma-bufs.
751− </para>
741+ <para>
742+ GEM also supports buffer sharing with dma-buf file descriptors through
743+ PRIME. GEM-based drivers must use the provided helpers functions to
744+ implement the exporting and importing correctly. See <xref linkend="drm-prime-support" />.
745+ Since sharing file descriptors is inherently more secure than the
746+ easily guessable and global GEM names it is the preferred buffer
747+ sharing mechanism. Sharing buffers through GEM names is only supported
748+ for legacy userspace. Furthermore PRIME also allows cross-device
749+ buffer sharing since it is based on dma-bufs.
750+ </para>
752751 </sect3>
753752 <sect3 id="drm-gem-objects-mapping">
754753 <title>GEM Objects Mapping</title>
@@ -853,7 +852,7 @@ char *date;</synopsis> · 98 unmodified lines
853852 <sect3>
854853 <title>Command Execution</title>
855854 <para>
856− Perhaps the most important GEM function for GPU devices is providing a
855+ Perhaps the most important GEM function for GPU devices is providing a
857856 command execution interface to clients. Client programs construct
858857 command buffers containing references to previously allocated memory
859858 objects, and then submit them to GEM. At that point, GEM takes care to
@@ -875,95 +874,101 @@ char *date;</synopsis> · 15 unmodified lines
875874 <title>GEM Function Reference</title>
876875 !Edrivers/gpu/drm/drm_gem.c
877876 </sect3>
878− </sect2>
879− <sect2>
880− <title>VMA Offset Manager</title>
877+ </sect2>
878+ <sect2>
879+ <title>VMA Offset Manager</title>
881880 !Pdrivers/gpu/drm/drm_vma_manager.c vma offset manager
882881 !Edrivers/gpu/drm/drm_vma_manager.c
883882 !Iinclude/drm/drm_vma_manager.h
884− </sect2>
885− <sect2 id="drm-prime-support">
886− <title>PRIME Buffer Sharing</title>
887− <para>
888− PRIME is the cross device buffer sharing framework in drm, originally
889− created for the OPTIMUS range of multi-gpu platforms. To userspace
890− PRIME buffers are dma-buf based file descriptors.
891− </para>
892− <sect3>
893− <title>Overview and Driver Interface</title>
894− <para>
895− Similar to GEM global names, PRIME file descriptors are
896− also used to share buffer objects across processes. They offer
897− additional security: as file descriptors must be explicitly sent over
898− UNIX domain sockets to be shared between applications, they can't be
899− guessed like the globally unique GEM names.
900− </para>
901− <para>
902− Drivers that support the PRIME
903− API must set the DRIVER_PRIME bit in the struct
904− <structname>drm_driver</structname>
905− <structfield>driver_features</structfield> field, and implement the
906− <methodname>prime_handle_to_fd</methodname> and
907− <methodname>prime_fd_to_handle</methodname> operations.
908− </para>
909− <para>
910− <synopsis>int (*prime_handle_to_fd)(struct drm_device *dev,
911− struct drm_file *file_priv, uint32_t handle,
912− uint32_t flags, int *prime_fd);
883+ </sect2>
884+ <sect2 id="drm-prime-support">
885+ <title>PRIME Buffer Sharing</title>
886+ <para>
887+ PRIME is the cross device buffer sharing framework in drm, originally
888+ created for the OPTIMUS range of multi-gpu platforms. To userspace
889+ PRIME buffers are dma-buf based file descriptors.
890+ </para>
891+ <sect3>
892+ <title>Overview and Driver Interface</title>
893+ <para>
894+ Similar to GEM global names, PRIME file descriptors are
895+ also used to share buffer objects across processes. They offer
896+ additional security: as file descriptors must be explicitly sent over
897+ UNIX domain sockets to be shared between applications, they can't be
898+ guessed like the globally unique GEM names.
899+ </para>
900+ <para>
901+ Drivers that support the PRIME
902+ API must set the DRIVER_PRIME bit in the struct
903+ <structname>drm_driver</structname>
904+ <structfield>driver_features</structfield> field, and implement the
905+ <methodname>prime_handle_to_fd</methodname> and
906+ <methodname>prime_fd_to_handle</methodname> operations.
907+ </para>
908+ <para>
909+ <synopsis>int (*prime_handle_to_fd)(struct drm_device *dev,
910+ struct drm_file *file_priv, uint32_t handle,
911+ uint32_t flags, int *prime_fd);
913912 int (*prime_fd_to_handle)(struct drm_device *dev,
914− struct drm_file *file_priv, int prime_fd,
915− uint32_t *handle);</synopsis>
916− Those two operations convert a handle to a PRIME file descriptor and
917− vice versa. Drivers must use the kernel dma-buf buffer sharing framework
918− to manage the PRIME file descriptors. Similar to the mode setting
919− API PRIME is agnostic to the underlying buffer object manager, as
920− long as handles are 32bit unsigned integers.
921− </para>
922− <para>
923− While non-GEM drivers must implement the operations themselves, GEM
924− drivers must use the <function>drm_gem_prime_handle_to_fd</function>
925− and <function>drm_gem_prime_fd_to_handle</function> helper functions.
926− Those helpers rely on the driver
927− <methodname>gem_prime_export</methodname> and
928− <methodname>gem_prime_import</methodname> operations to create a dma-buf
929− instance from a GEM object (dma-buf exporter role) and to create a GEM
930− object from a dma-buf instance (dma-buf importer role).
931− </para>
932− <para>
933− <synopsis>struct dma_buf * (*gem_prime_export)(struct drm_device *dev,
934− struct drm_gem_object *obj,
935− int flags);
913+ struct drm_file *file_priv, int prime_fd,
914+ uint32_t *handle);</synopsis>
915+ Those two operations convert a handle to a PRIME file descriptor and
916+ vice versa. Drivers must use the kernel dma-buf buffer sharing framework
917+ to manage the PRIME file descriptors. Similar to the mode setting
918+ API PRIME is agnostic to the underlying buffer object manager, as
919+ long as handles are 32bit unsigned integers.
920+ </para>
921+ <para>
922+ While non-GEM drivers must implement the operations themselves, GEM
923+ drivers must use the <function>drm_gem_prime_handle_to_fd</function>
924+ and <function>drm_gem_prime_fd_to_handle</function> helper functions.
925+ Those helpers rely on the driver
926+ <methodname>gem_prime_export</methodname> and
927+ <methodname>gem_prime_import</methodname> operations to create a dma-buf
928+ instance from a GEM object (dma-buf exporter role) and to create a GEM
929+ object from a dma-buf instance (dma-buf importer role).
930+ </para>
931+ <para>
932+ <synopsis>struct dma_buf * (*gem_prime_export)(struct drm_device *dev,
933+ struct drm_gem_object *obj,
934+ int flags);
936935 struct drm_gem_object * (*gem_prime_import)(struct drm_device *dev,
937− struct dma_buf *dma_buf);</synopsis>
938− These two operations are mandatory for GEM drivers that support
939− PRIME.
940− </para>
941− </sect3>
942− <sect3>
943− <title>PRIME Helper Functions</title>
944−!Pdrivers/gpu/drm/drm_prime.c PRIME Helpers
936+ struct dma_buf *dma_buf);</synopsis>
937+ These two operations are mandatory for GEM drivers that support
938+ PRIME.
939+ </para>
945940 </sect3>
946− </sect2>
947− <sect2>
948− <title>PRIME Function References</title>
941+ <sect3>
942+ <title>PRIME Helper Functions</title>
943+!Pdrivers/gpu/drm/drm_prime.c PRIME Helpers
944+ </sect3>
945+ </sect2>
946+ <sect2>
947+ <title>PRIME Function References</title>
949948 !Edrivers/gpu/drm/drm_prime.c
950− </sect2>
951− <sect2>
952− <title>DRM MM Range Allocator</title>
953− <sect3>
954− <title>Overview</title>
949+ </sect2>
950+ <sect2>
951+ <title>DRM MM Range Allocator</title>
952+ <sect3>
953+ <title>Overview</title>
955954 !Pdrivers/gpu/drm/drm_mm.c Overview
956− </sect3>
957− <sect3>
958− <title>LRU Scan/Eviction Support</title>
955+ </sect3>
956+ <sect3>
957+ <title>LRU Scan/Eviction Support</title>
959958 !Pdrivers/gpu/drm/drm_mm.c lru scan roaster
960− </sect3>
959+ </sect3>
961960 </sect2>
962− <sect2>
963− <title>DRM MM Range Allocator Function References</title>
961+ <sect2>
962+ <title>DRM MM Range Allocator Function References</title>
964963 !Edrivers/gpu/drm/drm_mm.c
965964 !Iinclude/drm/drm_mm.h
966− </sect2>
965+ </sect2>
966+ <sect2>
967+ <title>CMA Helper Functions Reference</title>
968+!Pdrivers/gpu/drm/drm_gem_cma_helper.c cma helpers
969+!Edrivers/gpu/drm/drm_gem_cma_helper.c
970+!Iinclude/drm/drm_gem_cma_helper.h
971+ </sect2>
967972 </sect1>
968973
969974 <!-- Internals: mode setting -->
@@ -995,6 +1000,10 @@ int max_width, max_height;</synopsis> · 25 unmodified lines
9951000 <title>Display Modes Function Reference</title>
9961001 !Iinclude/drm/drm_modes.h
9971002 !Edrivers/gpu/drm/drm_modes.c
1003+ </sect2>
1004+ <sect2>
1005+ <title>Atomic Mode Setting Function Reference</title>
1006+!Edrivers/gpu/drm/drm_atomic.c
9981007 </sect2>
9991008 <sect2>
10001009 <title>Frame Buffer Creation</title>
@@ -1826,6 +1835,10 @@ void intel_crt_init(struct drm_device *dev) · 825 unmodified lines
18261835 <sect2>
18271836 <title>KMS API Functions</title>
18281837 !Edrivers/gpu/drm/drm_crtc.c
1838+ </sect2>
1839+ <sect2>
1840+ <title>KMS Data Structures</title>
1841+!Iinclude/drm/drm_crtc.h
18291842 </sect2>
18301843 <sect2>
18311844 <title>KMS Locking</title>
@@ -1934,10 +1947,16 @@ void intel_crt_init(struct drm_device *dev) · 102 unmodified lines
19341947 and then retrieves a list of modes by calling the connector
19351948 <methodname>get_modes</methodname> helper operation.
19361949 </para>
1950+ <para>
1951+ If the helper operation returns no mode, and if the connector status
1952+ is connector_status_connected, standard VESA DMT modes up to
1953+ 1024x768 are automatically added to the modes list by a call to
1954+ <function>drm_add_modes_noedid</function>.
1955+ </para>
19371956 <para>
1938− The function filters out modes larger than
1957+ The function then filters out modes larger than
19391958 <parameter>max_width</parameter> and <parameter>max_height</parameter>
1940− if specified. It then calls the optional connector
1959+ if specified. It finally calls the optional connector
19411960 <methodname>mode_valid</methodname> helper operation for each mode in
19421961 the probed list to check whether the mode is valid for the connector.
19431962 </para>
@@ -2077,11 +2096,19 @@ void intel_crt_init(struct drm_device *dev) · 133 unmodified lines
20772096 <synopsis>int (*get_modes)(struct drm_connector *connector);</synopsis>
20782097 <para>
20792098 Fill the connector's <structfield>probed_modes</structfield> list
2080− by parsing EDID data with <function>drm_add_edid_modes</function> or
2081− calling <function>drm_mode_probed_add</function> directly for every
2099+ by parsing EDID data with <function>drm_add_edid_modes</function>,
2100+ adding standard VESA DMT modes with <function>drm_add_modes_noedid</function>,
2101+ or calling <function>drm_mode_probed_add</function> directly for every
20822102 supported mode and return the number of modes it has detected. This
20832103 operation is mandatory.
20842104 </para>
2105+ <para>
2106+ Note that the caller function will automatically add standard VESA
2107+ DMT modes up to 1024x768 if the <methodname>get_modes</methodname>
2108+ helper operation returns no mode and if the connector status is
2109+ connector_status_connected. There is no need to call
2110+ <function>drm_add_edid_modes</function> manually in that case.
2111+ </para>
20852112 <para>
20862113 When adding modes manually the driver creates each mode with a call to
20872114 <function>drm_mode_create</function> and must fill the following fields.
@@ -2279,7 +2306,7 @@ void intel_crt_init(struct drm_device *dev) · 191 unmodified lines
22792306 <function>drm_helper_probe_single_connector_modes</function>.
22802307 </para>
22812308 <para>
2282− When parsing EDID data, <function>drm_add_edid_modes</function> fill the
2309+ When parsing EDID data, <function>drm_add_edid_modes</function> fills the
22832310 connector <structfield>display_info</structfield>
22842311 <structfield>width_mm</structfield> and
22852312 <structfield>height_mm</structfield> fields. When creating modes
@@ -2316,9 +2343,27 @@ void intel_crt_init(struct drm_device *dev) · 30 unmodified lines
23162343 </listitem>
23172344 </itemizedlist>
23182345 </sect2>
2346+ <sect2>
2347+ <title>Atomic Modeset Helper Functions Reference</title>
2348+ <sect3>
2349+ <title>Overview</title>
2350+!Pdrivers/gpu/drm/drm_atomic_helper.c overview
2351+ </sect3>
2352+ <sect3>
2353+ <title>Implementing Asynchronous Atomic Commit</title>
2354+!Pdrivers/gpu/drm/drm_atomic_helper.c implementing async commit
2355+ </sect3>
2356+ <sect3>
2357+ <title>Atomic State Reset and Initialization</title>
2358+!Pdrivers/gpu/drm/drm_atomic_helper.c atomic state reset and initialization
2359+ </sect3>
2360+!Iinclude/drm/drm_atomic_helper.h
2361+!Edrivers/gpu/drm/drm_atomic_helper.c
2362+ </sect2>
23192363 <sect2>
23202364 <title>Modeset Helper Functions Reference</title>
23212365 !Edrivers/gpu/drm/drm_crtc_helper.c
2366+!Pdrivers/gpu/drm/drm_crtc_helper.c overview
23222367 </sect2>
23232368 <sect2>
23242369 <title>Output Probing Helper Functions Reference</title>
@@ -2342,6 +2387,12 @@ void intel_crt_init(struct drm_device *dev) · 17 unmodified lines
23422387 !Pdrivers/gpu/drm/drm_dp_mst_topology.c dp mst helper
23432388 !Iinclude/drm/drm_dp_mst_helper.h
23442389 !Edrivers/gpu/drm/drm_dp_mst_topology.c
2390+ </sect2>
2391+ <sect2>
2392+ <title>MIPI DSI Helper Functions Reference</title>
2393+!Pdrivers/gpu/drm/drm_mipi_dsi.c dsi helpers
2394+!Iinclude/drm/drm_mipi_dsi.h
2395+!Edrivers/gpu/drm/drm_mipi_dsi.c
23452396 </sect2>
23462397 <sect2>
23472398 <title>EDID Helper Functions Reference</title>
@@ -2372,7 +2423,12 @@ void intel_crt_init(struct drm_device *dev) · 24 unmodified lines
23722423 </sect2>
23732424 <sect2>
23742425 <title id="drm-kms-planehelpers">Plane Helper Reference</title>
2375−!Edrivers/gpu/drm/drm_plane_helper.c Plane Helpers
2426+!Edrivers/gpu/drm/drm_plane_helper.c
2427+!Pdrivers/gpu/drm/drm_plane_helper.c overview
2428+ </sect2>
2429+ <sect2>
2430+ <title>Tile group</title>
2431+!Pdrivers/gpu/drm/drm_crtc.c Tile group
23762432 </sect2>
23772433 </sect1>
23782434
@@ -2508,8 +2564,8 @@ void intel_crt_init(struct drm_device *dev) · 129 unmodified lines
25082564 <td valign="top" >Description/Restrictions</td>
25092565 </tr>
25102566 <tr>
2511− <td rowspan="21" valign="top" >DRM</td>
2512− <td rowspan="2" valign="top" >Generic</td>
2567+ <td rowspan="25" valign="top" >DRM</td>
2568+ <td rowspan="4" valign="top" >Generic</td>
25132569 <td valign="top" >“EDID”</td>
25142570 <td valign="top" >BLOB | IMMUTABLE</td>
25152571 <td valign="top" >0</td>
@@ -2524,6 +2580,20 @@ void intel_crt_init(struct drm_device *dev) · 8 unmodified lines
25242580 <td valign="top" >Contains DPMS operation mode value.</td>
25252581 </tr>
25262582 <tr>
2583+ <td valign="top" >“PATH”</td>
2584+ <td valign="top" >BLOB | IMMUTABLE</td>
2585+ <td valign="top" >0</td>
2586+ <td valign="top" >Connector</td>
2587+ <td valign="top" >Contains topology path to a connector.</td>
2588+ </tr>
2589+ <tr>
2590+ <td valign="top" >“TILE”</td>
2591+ <td valign="top" >BLOB | IMMUTABLE</td>
2592+ <td valign="top" >0</td>
2593+ <td valign="top" >Connector</td>
2594+ <td valign="top" >Contains tiling information for a connector.</td>
2595+ </tr>
2596+ <tr>
25272597 <td rowspan="1" valign="top" >Plane</td>
25282598 <td valign="top" >“type”</td>
25292599 <td valign="top" >ENUM | IMMUTABLE</td>
@@ -2639,6 +2709,21 @@ void intel_crt_init(struct drm_device *dev) · 109 unmodified lines
26392709 <td valign="top" >TBD</td>
26402710 </tr>
26412711 <tr>
2712+ <td rowspan="2" valign="top" >Virtual GPU</td>
2713+ <td valign="top" >“suggested X”</td>
2714+ <td valign="top" >RANGE</td>
2715+ <td valign="top" >Min=0, Max=0xffffffff</td>
2716+ <td valign="top" >Connector</td>
2717+ <td valign="top" >property to suggest an X offset for a connector</td>
2718+ </tr>
2719+ <tr>
2720+ <td valign="top" >“suggested Y”</td>
2721+ <td valign="top" >RANGE</td>
2722+ <td valign="top" >Min=0, Max=0xffffffff</td>
2723+ <td valign="top" >Connector</td>
2724+ <td valign="top" >property to suggest an Y offset for a connector</td>
2725+ </tr>
2726+ <tr>
26422727 <td rowspan="3" valign="top" >Optional</td>
26432728 <td valign="top" >“scaling mode”</td>
26442729 <td valign="top" >ENUM</td>
@@ -3386,6 +3471,13 @@ void (*disable_vblank) (struct drm_device *dev, int crtc);</synopsis> · 741 unmodified lines
33863471 by scheduling a timer. The delay is accessible through the vblankoffdelay
33873472 module parameter or the <varname>drm_vblank_offdelay</varname> global
33883473 variable and expressed in milliseconds. Its default value is 5000 ms.
3474+ Zero means never disable, and a negative value means disable immediately.
3475+ Drivers may override the behaviour by setting the
3476+ <structname>drm_device</structname>
3477+ <structfield>vblank_disable_immediate</structfield> flag, which when set
3478+ causes vblank interrupts to be disabled immediately regardless of the
3479+ drm_vblank_offdelay value. The flag should only be set if there's a
3480+ properly working hardware vblank counter present.
33893481 </para>
33903482 <para>
33913483 When a vertical blanking interrupt occurs drivers only need to call the
@@ -3400,6 +3492,7 @@ void (*disable_vblank) (struct drm_device *dev, int crtc);</synopsis> · 8 unmodified lines
34003492 <sect2>
34013493 <title>Vertical Blanking and Interrupt Handling Functions Reference</title>
34023494 !Edrivers/gpu/drm/drm_irq.c
3495+!Finclude/drm/drmP.h drm_crtc_vblank_waitqueue
34033496 </sect2>
34043497 </sect1>
34053498
@@ -3780,6 +3873,26 @@ int num_ioctls;</synopsis> · 374 unmodified lines
37803873 blocks. This excludes a set of SoC platforms with an SGX rendering unit,
37813874 those have basic support through the gma500 drm driver.
37823875 </para>
3876+ <sect1>
3877+ <title>Core Driver Infrastructure</title>
3878+ <para>
3879+ This section covers core driver infrastructure used by both the display
3880+ and the GEM parts of the driver.
3881+ </para>
3882+ <sect2>
3883+ <title>Runtime Power Management</title>
3884+!Pdrivers/gpu/drm/i915/intel_runtime_pm.c runtime pm
3885+!Idrivers/gpu/drm/i915/intel_runtime_pm.c
3886+ </sect2>
3887+ <sect2>
3888+ <title>Interrupt Handling</title>
3889+!Pdrivers/gpu/drm/i915/i915_irq.c interrupt handling
3890+!Fdrivers/gpu/drm/i915/i915_irq.c intel_irq_init intel_irq_init_hw intel_hpd_init
3891+!Fdrivers/gpu/drm/i915/i915_irq.c intel_irq_fini
3892+!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_disable_interrupts
3893+!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_enable_interrupts
3894+ </sect2>
3895+ </sect1>
37833896 <sect1>
37843897 <title>Display Hardware Handling</title>
37853898 <para>
@@ -3796,6 +3909,18 @@ int num_ioctls;</synopsis> · 10 unmodified lines
37963909 configuration change.
37973910 </para>
37983911 </sect2>
3912+ <sect2>
3913+ <title>Frontbuffer Tracking</title>
3914+!Pdrivers/gpu/drm/i915/intel_frontbuffer.c frontbuffer tracking
3915+!Idrivers/gpu/drm/i915/intel_frontbuffer.c
3916+!Fdrivers/gpu/drm/i915/intel_drv.h intel_frontbuffer_flip
3917+!Fdrivers/gpu/drm/i915/i915_gem.c i915_gem_track_fb
3918+ </sect2>
3919+ <sect2>
3920+ <title>Display FIFO Underrun Reporting</title>
3921+!Pdrivers/gpu/drm/i915/intel_fifo_underrun.c fifo underrun handling
3922+!Idrivers/gpu/drm/i915/intel_fifo_underrun.c
3923+ </sect2>
37993924 <sect2>
38003925 <title>Plane Configuration</title>
38013926 <para>
@@ -3815,6 +3940,16 @@ int num_ioctls;</synopsis> · 13 unmodified lines
38153940 probing, so those sections fully apply.
38163941 </para>
38173942 </sect2>
3943+ <sect2>
3944+ <title>High Definition Audio</title>
3945+!Pdrivers/gpu/drm/i915/intel_audio.c High Definition Audio over HDMI and Display Port
3946+!Idrivers/gpu/drm/i915/intel_audio.c
3947+ </sect2>
3948+ <sect2>
3949+ <title>Panel Self Refresh PSR (PSR/SRD)</title>
3950+!Pdrivers/gpu/drm/i915/intel_psr.c Panel Self Refresh (PSR/SRD)
3951+!Idrivers/gpu/drm/i915/intel_psr.c
3952+ </sect2>
38183953 <sect2>
38193954 <title>DPIO</title>
38203955 !Pdrivers/gpu/drm/i915/i915_reg.h DPIO
@@ -3918,7 +4053,34 @@ int num_ioctls;</synopsis> · 97 unmodified lines
39184053 !Pdrivers/gpu/drm/i915/i915_cmd_parser.c batch buffer command parser
39194054 !Idrivers/gpu/drm/i915/i915_cmd_parser.c
39204055 </sect2>
4056+ <sect2>
4057+ <title>Logical Rings, Logical Ring Contexts and Execlists</title>
4058+!Pdrivers/gpu/drm/i915/intel_lrc.c Logical Rings, Logical Ring Contexts and Execlists
4059+!Idrivers/gpu/drm/i915/intel_lrc.c
4060+ </sect2>
39214061 </sect1>
4062+
4063+ <sect1>
4064+ <title> Tracing </title>
4065+ <para>
4066+ This sections covers all things related to the tracepoints implemented in
4067+ the i915 driver.
4068+ </para>
4069+ <sect2>
4070+ <title> i915_ppgtt_create and i915_ppgtt_release </title>
4071+!Pdrivers/gpu/drm/i915/i915_trace.h i915_ppgtt_create and i915_ppgtt_release tracepoints
4072+ </sect2>
4073+ <sect2>
4074+ <title> i915_context_create and i915_context_free </title>
4075+!Pdrivers/gpu/drm/i915/i915_trace.h i915_context_create and i915_context_free tracepoints
4076+ </sect2>
4077+ <sect2>
4078+ <title> switch_mm </title>
4079+!Pdrivers/gpu/drm/i915/i915_trace.h switch_mm tracepoint
4080+ </sect2>
4081+ </sect1>
4082+
39224083 </chapter>
4084+!Cdrivers/gpu/drm/i915/i915_irq.c
39234085 </part>
39244086 </book>
Documentation/DocBook/kernel-locking.tmpl+1−1
@@ -1972,7 +1972,7 @@ machines due to caching. · 1971 unmodified lines
19721972 <itemizedlist>
19731973 <listitem>
19741974 <para>
1975− <filename>Documentation/spinlocks.txt</filename>:
1975+ <filename>Documentation/locking/spinlocks.txt</filename>:
19761976 Linus Torvalds' spinlocking tutorial in the kernel sources.
19771977 </para>
19781978 </listitem>
Documentation/DocBook/media/Makefile+1−1
@@ -25,7 +25,7 @@ GENFILES := $(addprefix $(MEDIA_OBJ_DIR)/, $(MEDIA_TEMP)) · 24 unmodified lines
2525 PHONY += cleanmediadocs
2626
2727 cleanmediadocs:
28− -@rm `find $(MEDIA_OBJ_DIR) -type l` $(GENFILES) $(OBJIMGFILES) 2>/dev/null
28+ -@rm -f `find $(MEDIA_OBJ_DIR) -type l` $(GENFILES) $(OBJIMGFILES) 2>/dev/null
2929
3030 $(obj)/media_api.xml: $(GENFILES) FORCE
3131
Documentation/DocBook/media/dvb/dvbproperty.xml+2−2
@@ -120,8 +120,8 @@ struct dtv_properties { · 119 unmodified lines
120120 </para>
121121 <informaltable><tgroup cols="1"><tbody><row><entry
122122 align="char">
123−<para>This ioctl call sets one or more frontend properties. This call only
124− requires read-only access to the device.</para>
123+<para>This ioctl call sets one or more frontend properties. This call
124+ requires read/write access to the device.</para>
125125 </entry>
126126 </row></tbody></tgroup></informaltable>
127127 <para>SYNOPSIS
Documentation/DocBook/media/v4l/biblio.xml+85−0
@@ -178,6 +178,75 @@ Signal - NTSC for Studio Applications"</title> · 177 unmodified lines
178178 1125-Line High-Definition Production"</title>
179179 </biblioentry>
180180
181+ <biblioentry id="srgb">
182+ <abbrev>sRGB</abbrev>
183+ <authorgroup>
184+ <corpauthor>International Electrotechnical Commission
185+(<ulink url="http://www.iec.ch">http://www.iec.ch</ulink>)</corpauthor>
186+ </authorgroup>
187+ <title>IEC 61966-2-1 ed1.0 "Multimedia systems and equipment - Colour measurement
188+and management - Part 2-1: Colour management - Default RGB colour space - sRGB"</title>
189+ </biblioentry>
190+
191+ <biblioentry id="sycc">
192+ <abbrev>sYCC</abbrev>
193+ <authorgroup>
194+ <corpauthor>International Electrotechnical Commission
195+(<ulink url="http://www.iec.ch">http://www.iec.ch</ulink>)</corpauthor>
196+ </authorgroup>
197+ <title>IEC 61966-2-1-am1 ed1.0 "Amendment 1 - Multimedia systems and equipment - Colour measurement
198+and management - Part 2-1: Colour management - Default RGB colour space - sRGB"</title>
199+ </biblioentry>
200+
201+ <biblioentry id="xvycc">
202+ <abbrev>xvYCC</abbrev>
203+ <authorgroup>
204+ <corpauthor>International Electrotechnical Commission
205+(<ulink url="http://www.iec.ch">http://www.iec.ch</ulink>)</corpauthor>
206+ </authorgroup>
207+ <title>IEC 61966-2-4 ed1.0 "Multimedia systems and equipment - Colour measurement
208+and management - Part 2-4: Colour management - Extended-gamut YCC colour space for video
209+applications - xvYCC"</title>
210+ </biblioentry>
211+
212+ <biblioentry id="adobergb">
213+ <abbrev>AdobeRGB</abbrev>
214+ <authorgroup>
215+ <corpauthor>Adobe Systems Incorporated (<ulink url="http://www.adobe.com">http://www.adobe.com</ulink>)</corpauthor>
216+ </authorgroup>
217+ <title>Adobe&copy; RGB (1998) Color Image Encoding Version 2005-05</title>
218+ </biblioentry>
219+
220+ <biblioentry id="oprgb">
221+ <abbrev>opRGB</abbrev>
222+ <authorgroup>
223+ <corpauthor>International Electrotechnical Commission
224+(<ulink url="http://www.iec.ch">http://www.iec.ch</ulink>)</corpauthor>
225+ </authorgroup>
226+ <title>IEC 61966-2-5 "Multimedia systems and equipment - Colour measurement
227+and management - Part 2-5: Colour management - Optional RGB colour space - opRGB"</title>
228+ </biblioentry>
229+
230+ <biblioentry id="itu2020">
231+ <abbrev>ITU&nbsp;BT.2020</abbrev>
232+ <authorgroup>
233+ <corpauthor>International Telecommunication Union (<ulink
234+url="http://www.itu.ch">http://www.itu.ch</ulink>)</corpauthor>
235+ </authorgroup>
236+ <title>ITU-R Recommendation BT.2020 (08/2012) "Parameter values for ultra-high
237+definition television systems for production and international programme exchange"
238+</title>
239+ </biblioentry>
240+
241+ <biblioentry id="tech3213">
242+ <abbrev>EBU&nbsp;Tech&nbsp;3213</abbrev>
243+ <authorgroup>
244+ <corpauthor>European Broadcast Union (<ulink
245+url="http://www.ebu.ch">http://www.ebu.ch</ulink>)</corpauthor>
246+ </authorgroup>
247+ <title>E.B.U. Standard for Chromaticity Tolerances for Studio Monitors"</title>
248+ </biblioentry>
249+
181250 <biblioentry id="iec62106">
182251 <abbrev>IEC&nbsp;62106</abbrev>
183252 <authorgroup>
@@ -266,4 +335,20 @@ in the frequency range from 87,5 to 108,0 MHz</title> · 82 unmodified lines
266335 <subtitle>Version 1, Revision 2</subtitle>
267336 </biblioentry>
268337
338+ <biblioentry id="poynton">
339+ <abbrev>poynton</abbrev>
340+ <authorgroup>
341+ <corpauthor>Charles Poynton</corpauthor>
342+ </authorgroup>
343+ <title>Digital Video and HDTV, Algorithms and Interfaces</title>
344+ </biblioentry>
345+
346+ <biblioentry id="colimg">
347+ <abbrev>colimg</abbrev>
348+ <authorgroup>
349+ <corpauthor>Erik Reinhard et al.</corpauthor>
350+ </authorgroup>
351+ <title>Color Imaging: Fundamentals and Applications</title>
352+ </biblioentry>
353+
269354 </bibliography>
Documentation/DocBook/media/v4l/common.xml+1−1
@@ -110,7 +110,7 @@ makes no provisions to find these related devices. Some really · 109 unmodified lines
110110 complex devices use the Media Controller (see <xref linkend="media_controller" />)
111111 which can be used for this purpose. But most drivers do not use it,
112112 and while some code exists that uses sysfs to discover related devices
113−(see libmedia_dev in the <ulink url="http://git.linuxtv.org/v4l-utils/">v4l-utils</ulink>
113+(see libmedia_dev in the <ulink url="http://git.linuxtv.org/cgit.cgi/v4l-utils.git/">v4l-utils</ulink>
114114 git repository), there is no library yet that can provide a single API towards
115115 both Media Controller-based devices and devices that do not use the Media Controller.
116116 If you want to work on this please write to the linux-media mailing list: &v4l-ml;.</para>
Documentation/DocBook/media/v4l/compat.xml+22−0
@@ -2569,6 +2569,28 @@ fields changed from _s32 to _u32. · 2568 unmodified lines
25692569 </orderedlist>
25702570 </section>
25712571
2572+ <section>
2573+ <title>V4L2 in Linux 3.18</title>
2574+ <orderedlist>
2575+ <listitem>
2576+ <para>Added <constant>V4L2_CID_PAN_SPEED</constant> and
2577+ <constant>V4L2_CID_TILT_SPEED</constant> camera controls.</para>
2578+ </listitem>
2579+ </orderedlist>
2580+ </section>
2581+
2582+ <section>
2583+ <title>V4L2 in Linux 3.19</title>
2584+ <orderedlist>
2585+ <listitem>
2586+ <para>Rewrote Colorspace chapter, added new &v4l2-ycbcr-encoding;
2587+and &v4l2-quantization; fields to &v4l2-pix-format;, &v4l2-pix-format-mplane;
2588+and &v4l2-mbus-framefmt;.
2589+ </para>
2590+ </listitem>
2591+ </orderedlist>
2592+ </section>
2593+
25722594 <section id="other">
25732595 <title>Relation of V4L2 to other Linux multimedia APIs</title>
25742596
Documentation/DocBook/media/v4l/controls.xml+55−0
@@ -3965,6 +3965,27 @@ by exposure, white balance or focus controls.</entry> · 3964 unmodified lines
39653965 </row>
39663966 <row><entry></entry></row>
39673967
3968+ <row>
3969+ <entry spanname="id"><constant>V4L2_CID_PAN_SPEED</constant>&nbsp;</entry>
3970+ <entry>integer</entry>
3971+ </row><row><entry spanname="descr">This control turns the
3972+camera horizontally at the specific speed. The unit is undefined. A
3973+positive value moves the camera to the right (clockwise when viewed
3974+from above), a negative value to the left. A value of zero stops the motion
3975+if one is in progress and has no effect otherwise.</entry>
3976+ </row>
3977+ <row><entry></entry></row>
3978+
3979+ <row>
3980+ <entry spanname="id"><constant>V4L2_CID_TILT_SPEED</constant>&nbsp;</entry>
3981+ <entry>integer</entry>
3982+ </row><row><entry spanname="descr">This control turns the
3983+camera vertically at the specified speed. The unit is undefined. A
3984+positive value moves the camera up, a negative value down. A value of zero
3985+stops the motion if one is in progress and has no effect otherwise.</entry>
3986+ </row>
3987+ <row><entry></entry></row>
3988+
39683989 </tbody>
39693990 </tgroup>
39703991 </table>
@@ -4790,6 +4811,40 @@ interface and may change in the future.</para> · 819 unmodified lines
47904811 conversion.
47914812 </entry>
47924813 </row>
4814+ <row>
4815+ <entry spanname="id"><constant>V4L2_CID_TEST_PATTERN_RED</constant></entry>
4816+ <entry>integer</entry>
4817+ </row>
4818+ <row>
4819+ <entry spanname="descr">Test pattern red colour component.
4820+ </entry>
4821+ </row>
4822+ <row>
4823+ <entry spanname="id"><constant>V4L2_CID_TEST_PATTERN_GREENR</constant></entry>
4824+ <entry>integer</entry>
4825+ </row>
4826+ <row>
4827+ <entry spanname="descr">Test pattern green (next to red)
4828+ colour component.
4829+ </entry>
4830+ </row>
4831+ <row>
4832+ <entry spanname="id"><constant>V4L2_CID_TEST_PATTERN_BLUE</constant></entry>
4833+ <entry>integer</entry>
4834+ </row>
4835+ <row>
4836+ <entry spanname="descr">Test pattern blue colour component.
4837+ </entry>
4838+ </row>
4839+ <row>
4840+ <entry spanname="id"><constant>V4L2_CID_TEST_PATTERN_GREENB</constant></entry>
4841+ <entry>integer</entry>
4842+ </row>
4843+ <row>
4844+ <entry spanname="descr">Test pattern green (next to blue)
4845+ colour component.
4846+ </entry>
4847+ </row>
47934848 <row><entry></entry></row>
47944849 </tbody>
47954850 </tgroup>
Documentation/DocBook/media/v4l/dev-subdev.xml+63−46
@@ -195,53 +195,59 @@ · 194 unmodified lines
195195 <title>Sample Pipeline Configuration</title>
196196 <tgroup cols="3">
197197 <colspec colname="what"/>
198− <colspec colname="sensor-0" />
199− <colspec colname="frontend-0" />
200− <colspec colname="frontend-1" />
201− <colspec colname="scaler-0" />
202− <colspec colname="scaler-1" />
198+ <colspec colname="sensor-0 format" />
199+ <colspec colname="frontend-0 format" />
200+ <colspec colname="frontend-1 format" />
201+ <colspec colname="scaler-0 format" />
202+ <colspec colname="scaler-0 compose" />
203+ <colspec colname="scaler-1 format" />
203204 <thead>
204205 <row>
205206 <entry></entry>
206− <entry>Sensor/0</entry>
207− <entry>Frontend/0</entry>
208− <entry>Frontend/1</entry>
209− <entry>Scaler/0</entry>
210− <entry>Scaler/1</entry>
207+ <entry>Sensor/0 format</entry>
208+ <entry>Frontend/0 format</entry>
209+ <entry>Frontend/1 format</entry>
210+ <entry>Scaler/0 format</entry>
211+ <entry>Scaler/0 compose selection rectangle</entry>
212+ <entry>Scaler/1 format</entry>
211213 </row>
212214 </thead>
213215 <tbody valign="top">
214216 <row>
215217 <entry>Initial state</entry>
216− <entry>2048x1536</entry>
217− <entry>-</entry>
218− <entry>-</entry>
219− <entry>-</entry>
220− <entry>-</entry>
218+ <entry>2048x1536/SGRBG8_1X8</entry>
219+ <entry>(default)</entry>
220+ <entry>(default)</entry>
221+ <entry>(default)</entry>
222+ <entry>(default)</entry>
223+ <entry>(default)</entry>
221224 </row>
222225 <row>
223− <entry>Configure frontend input</entry>
224− <entry>2048x1536</entry>
225− <entry><emphasis>2048x1536</emphasis></entry>
226− <entry><emphasis>2046x1534</emphasis></entry>
227− <entry>-</entry>
228− <entry>-</entry>
226+ <entry>Configure frontend sink format</entry>
227+ <entry>2048x1536/SGRBG8_1X8</entry>
228+ <entry><emphasis>2048x1536/SGRBG8_1X8</emphasis></entry>
229+ <entry><emphasis>2046x1534/SGRBG8_1X8</emphasis></entry>
230+ <entry>(default)</entry>
231+ <entry>(default)</entry>
232+ <entry>(default)</entry>
229233 </row>
230234 <row>
231− <entry>Configure scaler input</entry>
232− <entry>2048x1536</entry>
233− <entry>2048x1536</entry>
234− <entry>2046x1534</entry>
235− <entry><emphasis>2046x1534</emphasis></entry>
236− <entry><emphasis>2046x1534</emphasis></entry>
235+ <entry>Configure scaler sink format</entry>
236+ <entry>2048x1536/SGRBG8_1X8</entry>
237+ <entry>2048x1536/SGRBG8_1X8</entry>
238+ <entry>2046x1534/SGRBG8_1X8</entry>
239+ <entry><emphasis>2046x1534/SGRBG8_1X8</emphasis></entry>
240+ <entry><emphasis>0,0/2046x1534</emphasis></entry>
241+ <entry><emphasis>2046x1534/SGRBG8_1X8</emphasis></entry>
237242 </row>
238243 <row>
239− <entry>Configure scaler output</entry>
240− <entry>2048x1536</entry>
241− <entry>2048x1536</entry>
242− <entry>2046x1534</entry>
243− <entry>2046x1534</entry>
244− <entry><emphasis>1280x960</emphasis></entry>
244+ <entry>Configure scaler sink compose selection</entry>
245+ <entry>2048x1536/SGRBG8_1X8</entry>
246+ <entry>2048x1536/SGRBG8_1X8</entry>
247+ <entry>2046x1534/SGRBG8_1X8</entry>
248+ <entry>2046x1534/SGRBG8_1X8</entry>
249+ <entry><emphasis>0,0/1280x960</emphasis></entry>
250+ <entry><emphasis>1280x960/SGRBG8_1X8</emphasis></entry>
245251 </row>
246252 </tbody>
247253 </tgroup>
@@ -249,19 +255,30 @@ · 1 unmodified line
249255
250256 <para>
251257 <orderedlist>
252− <listitem><para>Initial state. The sensor output is set to its native 3MP
253− resolution. Resolutions on the host frontend and scaler input and output
254− pads are undefined.</para></listitem>
255− <listitem><para>The application configures the frontend input pad resolution to
256− 2048x1536. The driver propagates the format to the frontend output pad.
257− Note that the propagated output format can be different, as in this case,
258− than the input format, as the hardware might need to crop pixels (for
259− instance when converting a Bayer filter pattern to RGB or YUV).</para></listitem>
260− <listitem><para>The application configures the scaler input pad resolution to
261− 2046x1534 to match the frontend output resolution. The driver propagates
262− the format to the scaler output pad.</para></listitem>
263− <listitem><para>The application configures the scaler output pad resolution to
264− 1280x960.</para></listitem>
258+ <listitem><para>Initial state. The sensor source pad format is
259+ set to its native 3MP size and V4L2_MBUS_FMT_SGRBG8_1X8
260+ media bus code. Formats on the host frontend and scaler sink
261+ and source pads have the default values, as well as the
262+ compose rectangle on the scaler's sink pad.</para></listitem>
263+
264+ <listitem><para>The application configures the frontend sink
265+ pad format's size to 2048x1536 and its media bus code to
266+ V4L2_MBUS_FMT_SGRBG_1X8. The driver propagates the format to
267+ the frontend source pad.</para></listitem>
268+
269+ <listitem><para>The application configures the scaler sink pad
270+ format's size to 2046x1534 and the media bus code to
271+ V4L2_MBUS_FMT_SGRBG_1X8 to match the frontend source size and
272+ media bus code. The media bus code on the sink pad is set to
273+ V4L2_MBUS_FMT_SGRBG_1X8. The driver propagates the size to the
274+ compose selection rectangle on the scaler's sink pad, and the
275+ format to the scaler source pad.</para></listitem>
276+
277+ <listitem><para>The application configures the size of the compose
278+ selection rectangle of the scaler's sink pad 1280x960. The driver
279+ propagates the size to the scaler's source pad
280+ format.</para></listitem>
281+
265282 </orderedlist>
266283 </para>
267284
Documentation/DocBook/media/v4l/io.xml+4−1
@@ -1422,7 +1422,10 @@ one of the <constant>V4L2_FIELD_NONE</constant>, · 1421 unmodified lines
14221422 <constant>V4L2_FIELD_BOTTOM</constant>, or
14231423 <constant>V4L2_FIELD_INTERLACED</constant> formats is acceptable.
14241424 Drivers choose depending on hardware capabilities or e.&nbsp;g. the
1425−requested image size, and return the actual field order. &v4l2-buffer;
1425+requested image size, and return the actual field order. Drivers must
1426+never return <constant>V4L2_FIELD_ANY</constant>. If multiple
1427+field orders are possible the driver must choose one of the possible
1428+field orders during &VIDIOC-S-FMT; or &VIDIOC-TRY-FMT;. &v4l2-buffer;
14261429 <structfield>field</structfield> can never be
14271430 <constant>V4L2_FIELD_ANY</constant>.</entry>
14281431 </row>
Documentation/DocBook/media/v4l/pixfmt-packed-rgb.xml+48−4
@@ -237,9 +237,9 @@ for a pixel lie next to each other in memory.</para> · 236 unmodified lines
237237 <entry>g<subscript>4</subscript></entry>
238238 <entry>g<subscript>3</subscript></entry>
239239 </row>
240− <row id="V4L2-PIX-FMT-RGB555X">
241− <entry><constant>V4L2_PIX_FMT_RGB555X</constant></entry>
242− <entry>'RGBQ'</entry>
240+ <row id="V4L2-PIX-FMT-ARGB555X">
241+ <entry><constant>V4L2_PIX_FMT_ARGB555X</constant></entry>
242+ <entry>'AR15' | (1 &lt;&lt; 31)</entry>
243243 <entry></entry>
244244 <entry>a</entry>
245245 <entry>r<subscript>4</subscript></entry>
@@ -259,6 +259,28 @@ for a pixel lie next to each other in memory.</para> · 13 unmodified lines
259259 <entry>b<subscript>1</subscript></entry>
260260 <entry>b<subscript>0</subscript></entry>
261261 </row>
262+ <row id="V4L2-PIX-FMT-XRGB555X">
263+ <entry><constant>V4L2_PIX_FMT_XRGB555X</constant></entry>
264+ <entry>'XR15' | (1 &lt;&lt; 31)</entry>
265+ <entry></entry>
266+ <entry>-</entry>
267+ <entry>r<subscript>4</subscript></entry>
268+ <entry>r<subscript>3</subscript></entry>
269+ <entry>r<subscript>2</subscript></entry>
270+ <entry>r<subscript>1</subscript></entry>
271+ <entry>r<subscript>0</subscript></entry>
272+ <entry>g<subscript>4</subscript></entry>
273+ <entry>g<subscript>3</subscript></entry>
274+ <entry></entry>
275+ <entry>g<subscript>2</subscript></entry>
276+ <entry>g<subscript>1</subscript></entry>
277+ <entry>g<subscript>0</subscript></entry>
278+ <entry>b<subscript>4</subscript></entry>
279+ <entry>b<subscript>3</subscript></entry>
280+ <entry>b<subscript>2</subscript></entry>
281+ <entry>b<subscript>1</subscript></entry>
282+ <entry>b<subscript>0</subscript></entry>
283+ </row>
262284 <row id="V4L2-PIX-FMT-RGB565X">
263285 <entry><constant>V4L2_PIX_FMT_RGB565X</constant></entry>
264286 <entry>'RGBR'</entry>
@@ -464,7 +486,7 @@ for a pixel lie next to each other in memory.</para> · 199 unmodified lines
464486 </row>
465487 <row id="V4L2-PIX-FMT-ARGB32">
466488 <entry><constant>V4L2_PIX_FMT_ARGB32</constant></entry>
467− <entry>'AX24'</entry>
489+ <entry>'BA24'</entry>
468490 <entry></entry>
469491 <entry>a<subscript>7</subscript></entry>
470492 <entry>a<subscript>6</subscript></entry>
@@ -800,6 +822,28 @@ image</title> · 329 unmodified lines
800822 <entry>g<subscript>4</subscript></entry>
801823 <entry>g<subscript>3</subscript></entry>
802824 </row>
825+ <row id="V4L2-PIX-FMT-RGB555X">
826+ <entry><constant>V4L2_PIX_FMT_RGB555X</constant></entry>
827+ <entry>'RGBQ'</entry>
828+ <entry></entry>
829+ <entry>a</entry>
830+ <entry>r<subscript>4</subscript></entry>
831+ <entry>r<subscript>3</subscript></entry>
832+ <entry>r<subscript>2</subscript></entry>
833+ <entry>r<subscript>1</subscript></entry>
834+ <entry>r<subscript>0</subscript></entry>
835+ <entry>g<subscript>4</subscript></entry>
836+ <entry>g<subscript>3</subscript></entry>
837+ <entry></entry>
838+ <entry>g<subscript>2</subscript></entry>
839+ <entry>g<subscript>1</subscript></entry>
840+ <entry>g<subscript>0</subscript></entry>
841+ <entry>b<subscript>4</subscript></entry>
842+ <entry>b<subscript>3</subscript></entry>
843+ <entry>b<subscript>2</subscript></entry>
844+ <entry>b<subscript>1</subscript></entry>
845+ <entry>b<subscript>0</subscript></entry>
846+ </row>
803847 <row id="V4L2-PIX-FMT-BGR32">
804848 <entry><constant>V4L2_PIX_FMT_BGR32</constant></entry>
805849 <entry>'BGR4'</entry>
Documentation/DocBook/media/v4l/pixfmt.xml+1001−309
@@ -138,9 +138,25 @@ applicable values.</para></entry> · 137 unmodified lines
138138 <row>
139139 <entry>__u32</entry>
140140 <entry><structfield>flags</structfield></entry>
141− <entry>Flags set by the application or driver, see <xref
141+ <entry>Flags set by the application or driver, see <xref
142142 linkend="format-flags" />.</entry>
143143 </row>
144+ <row>
145+ <entry>&v4l2-ycbcr-encoding;</entry>
146+ <entry><structfield>ycbcr_enc</structfield></entry>
147+ <entry>This information supplements the
148+<structfield>colorspace</structfield> and must be set by the driver for
149+capture streams and by the application for output streams,
150+see <xref linkend="colorspaces" />.</entry>
151+ </row>
152+ <row>
153+ <entry>&v4l2-quantization;</entry>
154+ <entry><structfield>quantization</structfield></entry>
155+ <entry>This information supplements the
156+<structfield>colorspace</structfield> and must be set by the driver for
157+capture streams and by the application for output streams,
158+see <xref linkend="colorspaces" />.</entry>
159+ </row>
144160 </tbody>
145161 </tgroup>
146162 </table>
@@ -231,10 +247,26 @@ codes can be used.</entry> · 84 unmodified lines
231247 <entry><structfield>flags</structfield></entry>
232248 <entry>Flags set by the application or driver, see <xref
233249 linkend="format-flags" />.</entry>
250+ </row>
251+ <row>
252+ <entry>&v4l2-ycbcr-encoding;</entry>
253+ <entry><structfield>ycbcr_enc</structfield></entry>
254+ <entry>This information supplements the
255+<structfield>colorspace</structfield> and must be set by the driver for
256+capture streams and by the application for output streams,
257+see <xref linkend="colorspaces" />.</entry>
258+ </row>
259+ <row>
260+ <entry>&v4l2-quantization;</entry>
261+ <entry><structfield>quantization</structfield></entry>
262+ <entry>This information supplements the
263+<structfield>colorspace</structfield> and must be set by the driver for
264+capture streams and by the application for output streams,
265+see <xref linkend="colorspaces" />.</entry>
234266 </row>
235267 <row>
236268 <entry>__u8</entry>
237− <entry><structfield>reserved[10]</structfield></entry>
269+ <entry><structfield>reserved[8]</structfield></entry>
238270 <entry>Reserved for future extensions. Should be zeroed by the
239271 application.</entry>
240272 </row>
@@ -296,345 +328,1005 @@ in the 2-planar version or with each component in its own buffer in the · 55 unmodified lines
296328 <section id="colorspaces">
297329 <title>Colorspaces</title>
298330
299− <para>[intro]</para>
331+ <para>'Color' is a very complex concept and depends on physics, chemistry and
332+biology. Just because you have three numbers that describe the 'red', 'green'
333+and 'blue' components of the color of a pixel does not mean that you can accurately
334+display that color. A colorspace defines what it actually <emphasis>means</emphasis>
335+to have an RGB value of e.g. (255,&nbsp;0,&nbsp;0). That is, which color should be
336+reproduced on the screen in a perfectly calibrated environment.</para>
300337
301− <!-- See proposal by Billy Biggs, video4linux-list@redhat.com
302−on 11 Oct 2002, subject: "Re: [V4L] Re: v4l2 api", and
303−http://vektor.theorem.ca/graphics/ycbcr/ and
304−http://www.poynton.com/notes/colour_and_gamma/ColorFAQ.html -->
338+ <para>In order to do that we first need to have a good definition of
339+color, i.e. some way to uniquely and unambiguously define a color so that someone
340+else can reproduce it. Human color vision is trichromatic since the human eye has
341+color receptors that are sensitive to three different wavelengths of light. Hence
342+the need to use three numbers to describe color. Be glad you are not a mantis shrimp
343+as those are sensitive to 12 different wavelengths, so instead of RGB we would be
344+using the ABCDEFGHIJKL colorspace...</para>
305345
306− <para>
307− <variablelist>
308− <varlistentry>
309− <term>Gamma Correction</term>
310− <listitem>
311− <para>[to do]</para>
312− <para>E'<subscript>R</subscript> = f(R)</para>
313− <para>E'<subscript>G</subscript> = f(G)</para>
314− <para>E'<subscript>B</subscript> = f(B)</para>
315− </listitem>
316− </varlistentry>
317− <varlistentry>
318− <term>Construction of luminance and color-difference
319−signals</term>
320− <listitem>
321− <para>[to do]</para>
322− <para>E'<subscript>Y</subscript> =
323−Coeff<subscript>R</subscript> E'<subscript>R</subscript>
324−+ Coeff<subscript>G</subscript> E'<subscript>G</subscript>
325−+ Coeff<subscript>B</subscript> E'<subscript>B</subscript></para>
326− <para>(E'<subscript>R</subscript> - E'<subscript>Y</subscript>) = E'<subscript>R</subscript>
327−- Coeff<subscript>R</subscript> E'<subscript>R</subscript>
328−- Coeff<subscript>G</subscript> E'<subscript>G</subscript>
329−- Coeff<subscript>B</subscript> E'<subscript>B</subscript></para>
330− <para>(E'<subscript>B</subscript> - E'<subscript>Y</subscript>) = E'<subscript>B</subscript>
331−- Coeff<subscript>R</subscript> E'<subscript>R</subscript>
332−- Coeff<subscript>G</subscript> E'<subscript>G</subscript>
333−- Coeff<subscript>B</subscript> E'<subscript>B</subscript></para>
334− </listitem>
335− </varlistentry>
336− <varlistentry>
337− <term>Re-normalized color-difference signals</term>
338− <listitem>
339− <para>The color-difference signals are scaled back to unity
340−range [-0.5;+0.5]:</para>
341− <para>K<subscript>B</subscript> = 0.5 / (1 - Coeff<subscript>B</subscript>)</para>
342− <para>K<subscript>R</subscript> = 0.5 / (1 - Coeff<subscript>R</subscript>)</para>
343− <para>P<subscript>B</subscript> =
344−K<subscript>B</subscript> (E'<subscript>B</subscript> - E'<subscript>Y</subscript>) =
345− 0.5 (Coeff<subscript>R</subscript> / Coeff<subscript>B</subscript>) E'<subscript>R</subscript>
346−+ 0.5 (Coeff<subscript>G</subscript> / Coeff<subscript>B</subscript>) E'<subscript>G</subscript>
347−+ 0.5 E'<subscript>B</subscript></para>
348− <para>P<subscript>R</subscript> =
349−K<subscript>R</subscript> (E'<subscript>R</subscript> - E'<subscript>Y</subscript>) =
350− 0.5 E'<subscript>R</subscript>
351−+ 0.5 (Coeff<subscript>G</subscript> / Coeff<subscript>R</subscript>) E'<subscript>G</subscript>
352−+ 0.5 (Coeff<subscript>B</subscript> / Coeff<subscript>R</subscript>) E'<subscript>B</subscript></para>
353− </listitem>
354− </varlistentry>
355− <varlistentry>
356− <term>Quantization</term>
357− <listitem>
358− <para>[to do]</para>
359− <para>Y' = (Lum. Levels - 1) &middot; E'<subscript>Y</subscript> + Lum. Offset</para>
360− <para>C<subscript>B</subscript> = (Chrom. Levels - 1)
361−&middot; P<subscript>B</subscript> + Chrom. Offset</para>
362− <para>C<subscript>R</subscript> = (Chrom. Levels - 1)
363−&middot; P<subscript>R</subscript> + Chrom. Offset</para>
364− <para>Rounding to the nearest integer and clamping to the range
365−[0;255] finally yields the digital color components Y'CbCr
366−stored in YUV images.</para>
367− </listitem>
368− </varlistentry>
369− </variablelist>
370− </para>
371−
372− <example>
373− <title>ITU-R Rec. BT.601 color conversion</title>
374−
375− <para>Forward Transformation</para>
376−
377− <programlisting>
378−int ER, EG, EB; /* gamma corrected RGB input [0;255] */
379−int Y1, Cb, Cr; /* output [0;255] */
380−
381−double r, g, b; /* temporaries */
382−double y1, pb, pr;
383−
384−int
385−clamp (double x)
386−{
387− int r = x; /* round to nearest */
388−
389− if (r &lt; 0) return 0;
390− else if (r &gt; 255) return 255;
391− else return r;
392−}
393−
394−r = ER / 255.0;
395−g = EG / 255.0;
396−b = EB / 255.0;
397−
398−y1 = 0.299 * r + 0.587 * g + 0.114 * b;
399−pb = -0.169 * r - 0.331 * g + 0.5 * b;
400−pr = 0.5 * r - 0.419 * g - 0.081 * b;
401−
402−Y1 = clamp (219 * y1 + 16);
403−Cb = clamp (224 * pb + 128);
404−Cr = clamp (224 * pr + 128);
405−
406−/* or shorter */
407−
408−y1 = 0.299 * ER + 0.587 * EG + 0.114 * EB;
409−
410−Y1 = clamp ( (219 / 255.0) * y1 + 16);
411−Cb = clamp (((224 / 255.0) / (2 - 2 * 0.114)) * (EB - y1) + 128);
412−Cr = clamp (((224 / 255.0) / (2 - 2 * 0.299)) * (ER - y1) + 128);
413− </programlisting>
414−
415− <para>Inverse Transformation</para>
416−
417− <programlisting>
418−int Y1, Cb, Cr; /* gamma pre-corrected input [0;255] */
419−int ER, EG, EB; /* output [0;255] */
420−
421−double r, g, b; /* temporaries */
422−double y1, pb, pr;
423−
424−int
425−clamp (double x)
426−{
427− int r = x; /* round to nearest */
428−
429− if (r &lt; 0) return 0;
430− else if (r &gt; 255) return 255;
431− else return r;
432−}
433−
434−y1 = (Y1 - 16) / 219.0;
435−pb = (Cb - 128) / 224.0;
436−pr = (Cr - 128) / 224.0;
437−
438−r = 1.0 * y1 + 0 * pb + 1.402 * pr;
439−g = 1.0 * y1 - 0.344 * pb - 0.714 * pr;
440−b = 1.0 * y1 + 1.772 * pb + 0 * pr;
441−
442−ER = clamp (r * 255); /* [ok? one should prob. limit y1,pb,pr] */
443−EG = clamp (g * 255);
444−EB = clamp (b * 255);
445− </programlisting>
446− </example>
447−
448− <table pgwide="1" id="v4l2-colorspace" orient="land">
449− <title>enum v4l2_colorspace</title>
450− <tgroup cols="11" align="center">
451− <colspec align="left" />
452− <colspec align="center" />
453− <colspec align="left" />
454− <colspec colname="cr" />
455− <colspec colname="cg" />
456− <colspec colname="cb" />
457− <colspec colname="wp" />
458− <colspec colname="gc" />
459− <colspec colname="lum" />
460− <colspec colname="qy" />
461− <colspec colname="qc" />
462− <spanspec namest="cr" nameend="cb" spanname="chrom" />
463− <spanspec namest="qy" nameend="qc" spanname="quant" />
464− <spanspec namest="lum" nameend="qc" spanname="spam" />
346+ <para>Color exists only in the eye and brain and is the result of how strongly
347+color receptors are stimulated. This is based on the Spectral
348+Power Distribution (SPD) which is a graph showing the intensity (radiant power)
349+of the light at wavelengths covering the visible spectrum as it enters the eye.
350+The science of colorimetry is about the relationship between the SPD and color as
351+perceived by the human brain.</para>
352+
353+ <para>Since the human eye has only three color receptors it is perfectly
354+possible that different SPDs will result in the same stimulation of those receptors
355+and are perceived as the same color, even though the SPD of the light is
356+different.</para>
357+
358+ <para>In the 1920s experiments were devised to determine the relationship
359+between SPDs and the perceived color and that resulted in the CIE 1931 standard
360+that defines spectral weighting functions that model the perception of color.
361+Specifically that standard defines functions that can take an SPD and calculate
362+the stimulus for each color receptor. After some further mathematical transforms
363+these stimuli are known as the <emphasis>CIE XYZ tristimulus</emphasis> values
364+and these X, Y and Z values describe a color as perceived by a human unambiguously.
365+These X, Y and Z values are all in the range [0&hellip;1].</para>
366+
367+ <para>The Y value in the CIE XYZ colorspace corresponds to luminance. Often
368+the CIE XYZ colorspace is transformed to the normalized CIE xyY colorspace:</para>
369+
370+ <para>x = X / (X + Y + Z)</para>
371+ <para>y = Y / (X + Y + Z)</para>
372+
373+ <para>The x and y values are the chromaticity coordinates and can be used to
374+define a color without the luminance component Y. It is very confusing to
375+have such similar names for these colorspaces. Just be aware that if colors
376+are specified with lower case 'x' and 'y', then the CIE xyY colorspace is
377+used. Upper case 'X' and 'Y' refer to the CIE XYZ colorspace. Also, y has nothing
378+to do with luminance. Together x and y specify a color, and Y the luminance.
379+That is really all you need to remember from a practical point of view. At
380+the end of this section you will find reading resources that go into much more
381+detail if you are interested.
382+</para>
383+
384+ <para>A monitor or TV will reproduce colors by emitting light at three
385+different wavelengths, the combination of which will stimulate the color receptors
386+in the eye and thus cause the perception of color. Historically these wavelengths
387+were defined by the red, green and blue phosphors used in the displays. These
388+<emphasis>color primaries</emphasis> are part of what defines a colorspace.</para>
389+
390+ <para>Different display devices will have different primaries and some
391+primaries are more suitable for some display technologies than others. This has
392+resulted in a variety of colorspaces that are used for different display
393+technologies or uses. To define a colorspace you need to define the three
394+color primaries (these are typically defined as x,&nbsp;y chromaticity coordinates
395+from the CIE xyY colorspace) but also the white reference: that is the color obtained
396+when all three primaries are at maximum power. This determines the relative power
397+or energy of the primaries. This is usually chosen to be close to daylight which has
398+been defined as the CIE D65 Illuminant.</para>
399+
400+ <para>To recapitulate: the CIE XYZ colorspace uniquely identifies colors.
401+Other colorspaces are defined by three chromaticity coordinates defined in the
402+CIE xyY colorspace. Based on those a 3x3 matrix can be constructed that
403+transforms CIE XYZ colors to colors in the new colorspace.
404+</para>
405+
406+ <para>Both the CIE XYZ and the RGB colorspace that are derived from the
407+specific chromaticity primaries are linear colorspaces. But neither the eye,
408+nor display technology is linear. Doubling the values of all components in
409+the linear colorspace will not be perceived as twice the intensity of the color.
410+So each colorspace also defines a transfer function that takes a linear color
411+component value and transforms it to the non-linear component value, which is a
412+closer match to the non-linear performance of both the eye and displays. Linear
413+component values are denoted RGB, non-linear are denoted as R'G'B'. In general
414+colors used in graphics are all R'G'B', except in openGL which uses linear RGB.
415+Special care should be taken when dealing with openGL to provide linear RGB colors
416+or to use the built-in openGL support to apply the inverse transfer function.</para>
417+
418+ <para>The final piece that defines a colorspace is a function that
419+transforms non-linear R'G'B' to non-linear Y'CbCr. This function is determined
420+by the so-called luma coefficients. There may be multiple possible Y'CbCr
421+encodings allowed for the same colorspace. Many encodings of color
422+prefer to use luma (Y') and chroma (CbCr) instead of R'G'B'. Since the human
423+eye is more sensitive to differences in luminance than in color this encoding
424+allows one to reduce the amount of color information compared to the luma
425+data. Note that the luma (Y') is unrelated to the Y in the CIE XYZ colorspace.
426+Also note that Y'CbCr is often called YCbCr or YUV even though these are
427+strictly speaking wrong.</para>
428+
429+ <para>Sometimes people confuse Y'CbCr as being a colorspace. This is not
430+correct, it is just an encoding of an R'G'B' color into luma and chroma
431+values. The underlying colorspace that is associated with the R'G'B' color
432+is also associated with the Y'CbCr color.</para>
433+
434+ <para>The final step is how the RGB, R'G'B' or Y'CbCr values are
435+quantized. The CIE XYZ colorspace where X, Y and Z are in the range
436+[0&hellip;1] describes all colors that humans can perceive, but the transform to
437+another colorspace will produce colors that are outside the [0&hellip;1] range.
438+Once clamped to the [0&hellip;1] range those colors can no longer be reproduced
439+in that colorspace. This clamping is what reduces the extent or gamut of the
440+colorspace. How the range of [0&hellip;1] is translated to integer values in the
441+range of [0&hellip;255] (or higher, depending on the color depth) is called the
442+quantization. This is <emphasis>not</emphasis> part of the colorspace
443+definition. In practice RGB or R'G'B' values are full range, i.e. they
444+use the full [0&hellip;255] range. Y'CbCr values on the other hand are limited
445+range with Y' using [16&hellip;235] and Cb and Cr using [16&hellip;240].</para>
446+
447+ <para>Unfortunately, in some cases limited range RGB is also used
448+where the components use the range [16&hellip;235]. And full range Y'CbCr also exists
449+using the [0&hellip;255] range.</para>
450+
451+ <para>In order to correctly interpret a color you need to know the
452+quantization range, whether it is R'G'B' or Y'CbCr, the used Y'CbCr encoding
453+and the colorspace.
454+From that information you can calculate the corresponding CIE XYZ color
455+and map that again to whatever colorspace your display device uses.</para>
456+
457+ <para>The colorspace definition itself consists of the three
458+chromaticity primaries, the white reference chromaticity, a transfer
459+function and the luma coefficients needed to transform R'G'B' to Y'CbCr. While
460+some colorspace standards correctly define all four, quite often the colorspace
461+standard only defines some, and you have to rely on other standards for
462+the missing pieces. The fact that colorspaces are often a mix of different
463+standards also led to very confusing naming conventions where the name of
464+a standard was used to name a colorspace when in fact that standard was
465+part of various other colorspaces as well.</para>
466+
467+ <para>If you want to read more about colors and colorspaces, then the
468+following resources are useful: <xref linkend="poynton" /> is a good practical
469+book for video engineers, <xref linkend="colimg" /> has a much broader scope and
470+describes many more aspects of color (physics, chemistry, biology, etc.).
471+The <ulink url="http://www.brucelindbloom.com">http://www.brucelindbloom.com</ulink>
472+website is an excellent resource, especially with respect to the mathematics behind
473+colorspace conversions. The wikipedia <ulink url="http://en.wikipedia.org/wiki/CIE_1931_color_space#CIE_xy_chromaticity_diagram_and_the_CIE_xyY_color_space">CIE 1931 colorspace</ulink> article
474+is also very useful.</para>
475+ </section>
476+
477+ <section>
478+ <title>Defining Colorspaces in V4L2</title>
479+ <para>In V4L2 colorspaces are defined by three values. The first is the colorspace
480+identifier (&v4l2-colorspace;) which defines the chromaticities, the transfer
481+function, the default Y'CbCr encoding and the default quantization method. The second
482+is the Y'CbCr encoding identifier (&v4l2-ycbcr-encoding;) to specify non-standard
483+Y'CbCr encodings and the third is the quantization identifier (&v4l2-quantization;)
484+to specify non-standard quantization methods. Most of the time only the colorspace
485+field of &v4l2-pix-format; or &v4l2-pix-format-mplane; needs to be filled in. Note
486+that the default R'G'B' quantization is always full range for all colorspaces,
487+so this won't be mentioned explicitly for each colorspace description.</para>
488+
489+ <table pgwide="1" frame="none" id="v4l2-colorspace">
490+ <title>V4L2 Colorspaces</title>
491+ <tgroup cols="2" align="left">
492+ &cs-def;
465493 <thead>
466494 <row>
467− <entry morerows="1">Identifier</entry>
468− <entry morerows="1">Value</entry>
469− <entry morerows="1">Description</entry>
470− <entry spanname="chrom">Chromaticities<footnote>
471− <para>The coordinates of the color primaries are
472−given in the CIE system (1931)</para>
473− </footnote></entry>
474− <entry morerows="1">White Point</entry>
475− <entry morerows="1">Gamma Correction</entry>
476− <entry morerows="1">Luminance E'<subscript>Y</subscript></entry>
477− <entry spanname="quant">Quantization</entry>
478− </row>
479− <row>
480− <entry>Red</entry>
481− <entry>Green</entry>
482− <entry>Blue</entry>
483− <entry>Y'</entry>
484− <entry>Cb, Cr</entry>
495+ <entry>Identifier</entry>
496+ <entry>Details</entry>
485497 </row>
486498 </thead>
487499 <tbody valign="top">
488500 <row>
489501 <entry><constant>V4L2_COLORSPACE_SMPTE170M</constant></entry>
490− <entry>1</entry>
491− <entry>NTSC/PAL according to <xref linkend="smpte170m" />,
492−<xref linkend="itu601" /></entry>
493− <entry>x&nbsp;=&nbsp;0.630, y&nbsp;=&nbsp;0.340</entry>
494− <entry>x&nbsp;=&nbsp;0.310, y&nbsp;=&nbsp;0.595</entry>
495− <entry>x&nbsp;=&nbsp;0.155, y&nbsp;=&nbsp;0.070</entry>
496− <entry>x&nbsp;=&nbsp;0.3127, y&nbsp;=&nbsp;0.3290,
497− Illuminant D<subscript>65</subscript></entry>
498− <entry>E' = 4.5&nbsp;I&nbsp;for&nbsp;I&nbsp;&le;0.018,
499−1.099&nbsp;I<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&lt;&nbsp;I</entry>
500− <entry>0.299&nbsp;E'<subscript>R</subscript>
501−+&nbsp;0.587&nbsp;E'<subscript>G</subscript>
502−+&nbsp;0.114&nbsp;E'<subscript>B</subscript></entry>
503− <entry>219&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
504− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
502+ <entry>See <xref linkend="col-smpte-170m" />.</entry>
505503 </row>
506504 <row>
507− <entry><constant>V4L2_COLORSPACE_SMPTE240M</constant></entry>
508− <entry>2</entry>
509− <entry>1125-Line (US) HDTV, see <xref
510−linkend="smpte240m" /></entry>
511− <entry>x&nbsp;=&nbsp;0.630, y&nbsp;=&nbsp;0.340</entry>
512− <entry>x&nbsp;=&nbsp;0.310, y&nbsp;=&nbsp;0.595</entry>
513− <entry>x&nbsp;=&nbsp;0.155, y&nbsp;=&nbsp;0.070</entry>
514− <entry>x&nbsp;=&nbsp;0.3127, y&nbsp;=&nbsp;0.3290,
515− Illuminant D<subscript>65</subscript></entry>
516− <entry>E' = 4&nbsp;I&nbsp;for&nbsp;I&nbsp;&le;0.0228,
517−1.1115&nbsp;I<superscript>0.45</superscript>&nbsp;-&nbsp;0.1115&nbsp;for&nbsp;0.0228&nbsp;&lt;&nbsp;I</entry>
518− <entry>0.212&nbsp;E'<subscript>R</subscript>
519−+&nbsp;0.701&nbsp;E'<subscript>G</subscript>
520−+&nbsp;0.087&nbsp;E'<subscript>B</subscript></entry>
521− <entry>219&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
522− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
505+ <entry><constant>V4L2_COLORSPACE_REC709</constant></entry>
506+ <entry>See <xref linkend="col-rec709" />.</entry>
523507 </row>
524508 <row>
525− <entry><constant>V4L2_COLORSPACE_REC709</constant></entry>
526− <entry>3</entry>
527− <entry>HDTV and modern devices, see <xref
528−linkend="itu709" /></entry>
529− <entry>x&nbsp;=&nbsp;0.640, y&nbsp;=&nbsp;0.330</entry>
530− <entry>x&nbsp;=&nbsp;0.300, y&nbsp;=&nbsp;0.600</entry>
531− <entry>x&nbsp;=&nbsp;0.150, y&nbsp;=&nbsp;0.060</entry>
532− <entry>x&nbsp;=&nbsp;0.3127, y&nbsp;=&nbsp;0.3290,
533− Illuminant D<subscript>65</subscript></entry>
534− <entry>E' = 4.5&nbsp;I&nbsp;for&nbsp;I&nbsp;&le;0.018,
535−1.099&nbsp;I<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&lt;&nbsp;I</entry>
536− <entry>0.2125&nbsp;E'<subscript>R</subscript>
537−+&nbsp;0.7154&nbsp;E'<subscript>G</subscript>
538−+&nbsp;0.0721&nbsp;E'<subscript>B</subscript></entry>
539− <entry>219&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
540− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
509+ <entry><constant>V4L2_COLORSPACE_SRGB</constant></entry>
510+ <entry>See <xref linkend="col-srgb" />.</entry>
541511 </row>
542512 <row>
543− <entry><constant>V4L2_COLORSPACE_BT878</constant></entry>
544− <entry>4</entry>
545− <entry>Broken Bt878 extents<footnote>
546− <para>The ubiquitous Bt878 video capture chip
547−quantizes E'<subscript>Y</subscript> to 238 levels, yielding a range
548−of Y' = 16 &hellip; 253, unlike Rec. 601 Y' = 16 &hellip;
549−235. This is not a typo in the Bt878 documentation, it has been
550−implemented in silicon. The chroma extents are unclear.</para>
551− </footnote>, <xref linkend="itu601" /></entry>
552− <entry>?</entry>
553− <entry>?</entry>
554− <entry>?</entry>
555− <entry>?</entry>
556− <entry>?</entry>
557− <entry>0.299&nbsp;E'<subscript>R</subscript>
558−+&nbsp;0.587&nbsp;E'<subscript>G</subscript>
559−+&nbsp;0.114&nbsp;E'<subscript>B</subscript></entry>
560− <entry><emphasis>237</emphasis>&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
561− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128 (probably)</entry>
513+ <entry><constant>V4L2_COLORSPACE_ADOBERGB</constant></entry>
514+ <entry>See <xref linkend="col-adobergb" />.</entry>
515+ </row>
516+ <row>
517+ <entry><constant>V4L2_COLORSPACE_BT2020</constant></entry>
518+ <entry>See <xref linkend="col-bt2020" />.</entry>
519+ </row>
520+ <row>
521+ <entry><constant>V4L2_COLORSPACE_SMPTE240M</constant></entry>
522+ <entry>See <xref linkend="col-smpte-240m" />.</entry>
562523 </row>
563524 <row>
564525 <entry><constant>V4L2_COLORSPACE_470_SYSTEM_M</constant></entry>
565− <entry>5</entry>
566− <entry>M/NTSC<footnote>
567− <para>No identifier exists for M/PAL which uses
568−the chromaticities of M/NTSC, the remaining parameters are equal to B and
569−G/PAL.</para>
570− </footnote> according to <xref linkend="itu470" />, <xref
571− linkend="itu601" /></entry>
572− <entry>x&nbsp;=&nbsp;0.67, y&nbsp;=&nbsp;0.33</entry>
573− <entry>x&nbsp;=&nbsp;0.21, y&nbsp;=&nbsp;0.71</entry>
574− <entry>x&nbsp;=&nbsp;0.14, y&nbsp;=&nbsp;0.08</entry>
575− <entry>x&nbsp;=&nbsp;0.310, y&nbsp;=&nbsp;0.316, Illuminant C</entry>
576− <entry>?</entry>
577− <entry>0.299&nbsp;E'<subscript>R</subscript>
578−+&nbsp;0.587&nbsp;E'<subscript>G</subscript>
579−+&nbsp;0.114&nbsp;E'<subscript>B</subscript></entry>
580− <entry>219&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
581− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
526+ <entry>See <xref linkend="col-sysm" />.</entry>
582527 </row>
583528 <row>
584529 <entry><constant>V4L2_COLORSPACE_470_SYSTEM_BG</constant></entry>
585− <entry>6</entry>
586− <entry>625-line PAL and SECAM systems according to <xref
587−linkend="itu470" />, <xref linkend="itu601" /></entry>
588− <entry>x&nbsp;=&nbsp;0.64, y&nbsp;=&nbsp;0.33</entry>
589− <entry>x&nbsp;=&nbsp;0.29, y&nbsp;=&nbsp;0.60</entry>
590− <entry>x&nbsp;=&nbsp;0.15, y&nbsp;=&nbsp;0.06</entry>
591− <entry>x&nbsp;=&nbsp;0.313, y&nbsp;=&nbsp;0.329,
592−Illuminant D<subscript>65</subscript></entry>
593− <entry>?</entry>
594− <entry>0.299&nbsp;E'<subscript>R</subscript>
595−+&nbsp;0.587&nbsp;E'<subscript>G</subscript>
596−+&nbsp;0.114&nbsp;E'<subscript>B</subscript></entry>
597− <entry>219&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16</entry>
598− <entry>224&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
530+ <entry>See <xref linkend="col-sysbg" />.</entry>
599531 </row>
600532 <row>
601533 <entry><constant>V4L2_COLORSPACE_JPEG</constant></entry>
602− <entry>7</entry>
603− <entry>JPEG Y'CbCr, see <xref linkend="jfif" />, <xref linkend="itu601" /></entry>
604− <entry>?</entry>
605− <entry>?</entry>
606− <entry>?</entry>
607− <entry>?</entry>
608− <entry>?</entry>
609− <entry>0.299&nbsp;E'<subscript>R</subscript>
610−+&nbsp;0.587&nbsp;E'<subscript>G</subscript>
611−+&nbsp;0.114&nbsp;E'<subscript>B</subscript></entry>
612− <entry>256&nbsp;E'<subscript>Y</subscript>&nbsp;+&nbsp;16<footnote>
613− <para>Note JFIF quantizes
614−Y'P<subscript>B</subscript>P<subscript>R</subscript> in range [0;+1] and
615−[-0.5;+0.5] to <emphasis>257</emphasis> levels, however Y'CbCr signals
616−are still clamped to [0;255].</para>
617− </footnote></entry>
618− <entry>256&nbsp;P<subscript>B,R</subscript>&nbsp;+&nbsp;128</entry>
534+ <entry>See <xref linkend="col-jpeg" />.</entry>
619535 </row>
536+ </tbody>
537+ </tgroup>
538+ </table>
539+
540+ <table pgwide="1" frame="none" id="v4l2-ycbcr-encoding">
541+ <title>V4L2 Y'CbCr Encodings</title>
542+ <tgroup cols="2" align="left">
543+ &cs-def;
544+ <thead>
620545 <row>
621− <entry><constant>V4L2_COLORSPACE_SRGB</constant></entry>
622− <entry>8</entry>
623− <entry>[?]</entry>
624− <entry>x&nbsp;=&nbsp;0.640, y&nbsp;=&nbsp;0.330</entry>
625− <entry>x&nbsp;=&nbsp;0.300, y&nbsp;=&nbsp;0.600</entry>
626− <entry>x&nbsp;=&nbsp;0.150, y&nbsp;=&nbsp;0.060</entry>
627− <entry>x&nbsp;=&nbsp;0.3127, y&nbsp;=&nbsp;0.3290,
628− Illuminant D<subscript>65</subscript></entry>
629− <entry>E' = 4.5&nbsp;I&nbsp;for&nbsp;I&nbsp;&le;0.018,
630−1.099&nbsp;I<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&lt;&nbsp;I</entry>
631− <entry spanname="spam">n/a</entry>
546+ <entry>Identifier</entry>
547+ <entry>Details</entry>
548+ </row>
549+ </thead>
550+ <tbody valign="top">
551+ <row>
552+ <entry><constant>V4L2_YCBCR_ENC_DEFAULT</constant></entry>
553+ <entry>Use the default Y'CbCr encoding as defined by the colorspace.</entry>
554+ </row>
555+ <row>
556+ <entry><constant>V4L2_YCBCR_ENC_601</constant></entry>
557+ <entry>Use the BT.601 Y'CbCr encoding.</entry>
558+ </row>
559+ <row>
560+ <entry><constant>V4L2_YCBCR_ENC_709</constant></entry>
561+ <entry>Use the Rec. 709 Y'CbCr encoding.</entry>
562+ </row>
563+ <row>
564+ <entry><constant>V4L2_YCBCR_ENC_XV601</constant></entry>
565+ <entry>Use the extended gamut xvYCC BT.601 encoding.</entry>
566+ </row>
567+ <row>
568+ <entry><constant>V4L2_YCBCR_ENC_XV709</constant></entry>
569+ <entry>Use the extended gamut xvYCC Rec. 709 encoding.</entry>
570+ </row>
571+ <row>
572+ <entry><constant>V4L2_YCBCR_ENC_SYCC</constant></entry>
573+ <entry>Use the extended gamut sYCC encoding.</entry>
574+ </row>
575+ <row>
576+ <entry><constant>V4L2_YCBCR_ENC_BT2020</constant></entry>
577+ <entry>Use the default non-constant luminance BT.2020 Y'CbCr encoding.</entry>
578+ </row>
579+ <row>
580+ <entry><constant>V4L2_YCBCR_ENC_BT2020_CONST_LUM</constant></entry>
581+ <entry>Use the constant luminance BT.2020 Yc'CbcCrc encoding.</entry>
582+ </row>
583+ </tbody>
584+ </tgroup>
585+ </table>
586+
587+ <table pgwide="1" frame="none" id="v4l2-quantization">
588+ <title>V4L2 Quantization Methods</title>
589+ <tgroup cols="2" align="left">
590+ &cs-def;
591+ <thead>
592+ <row>
593+ <entry>Identifier</entry>
594+ <entry>Details</entry>
595+ </row>
596+ </thead>
597+ <tbody valign="top">
598+ <row>
599+ <entry><constant>V4L2_QUANTIZATION_DEFAULT</constant></entry>
600+ <entry>Use the default quantization encoding as defined by the colorspace.
601+This is always full range for R'G'B' and usually limited range for Y'CbCr.</entry>
602+ </row>
603+ <row>
604+ <entry><constant>V4L2_QUANTIZATION_FULL_RANGE</constant></entry>
605+ <entry>Use the full range quantization encoding. I.e. the range [0&hellip;1]
606+is mapped to [0&hellip;255] (with possible clipping to [1&hellip;254] to avoid the
607+0x00 and 0xff values). Cb and Cr are mapped from [-0.5&hellip;0.5] to [0&hellip;255]
608+(with possible clipping to [1&hellip;254] to avoid the 0x00 and 0xff values).</entry>
609+ </row>
610+ <row>
611+ <entry><constant>V4L2_QUANTIZATION_LIM_RANGE</constant></entry>
612+ <entry>Use the limited range quantization encoding. I.e. the range [0&hellip;1]
613+is mapped to [16&hellip;235]. Cb and Cr are mapped from [-0.5&hellip;0.5] to [16&hellip;240].
614+</entry>
632615 </row>
633616 </tbody>
634617 </tgroup>
635618 </table>
636619 </section>
637620
621+ <section>
622+ <title>Detailed Colorspace Descriptions</title>
623+ <section>
624+ <title id="col-smpte-170m">Colorspace SMPTE 170M (<constant>V4L2_COLORSPACE_SMPTE170M</constant>)</title>
625+ <para>The <xref linkend="smpte170m" /> standard defines the colorspace used by NTSC and PAL and by SDTV
626+in general. The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_601</constant>.
627+The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and
628+the white reference are:</para>
629+ <table frame="none">
630+ <title>SMPTE 170M Chromaticities</title>
631+ <tgroup cols="3" align="left">
632+ &cs-str;
633+ <thead>
634+ <row>
635+ <entry>Color</entry>
636+ <entry>x</entry>
637+ <entry>y</entry>
638+ </row>
639+ </thead>
640+ <tbody valign="top">
641+ <row>
642+ <entry>Red</entry>
643+ <entry>0.630</entry>
644+ <entry>0.340</entry>
645+ </row>
646+ <row>
647+ <entry>Green</entry>
648+ <entry>0.310</entry>
649+ <entry>0.595</entry>
650+ </row>
651+ <row>
652+ <entry>Blue</entry>
653+ <entry>0.155</entry>
654+ <entry>0.070</entry>
655+ </row>
656+ <row>
657+ <entry>White Reference (D65)</entry>
658+ <entry>0.3127</entry>
659+ <entry>0.3290</entry>
660+ </row>
661+ </tbody>
662+ </tgroup>
663+ </table>
664+ <para>The red, green and blue chromaticities are also often referred to
665+as the SMPTE C set, so this colorspace is sometimes called SMPTE C as well.</para>
666+ <variablelist>
667+ <varlistentry>
668+ <term>The transfer function defined for SMPTE 170M is the same as the
669+one defined in Rec. 709. Normally L is in the range [0&hellip;1], but for the extended
670+gamut xvYCC encoding values outside that range are allowed.</term>
671+ <listitem>
672+ <para>L' = -1.099(-L)<superscript>0.45</superscript>&nbsp;+&nbsp;0.099&nbsp;for&nbsp;L&nbsp;&le;&nbsp;-0.018</para>
673+ <para>L' = 4.5L&nbsp;for&nbsp;-0.018&nbsp;&lt;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
674+ <para>L' = 1.099L<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;L&nbsp;&ge;&nbsp;0.018</para>
675+ </listitem>
676+ </varlistentry>
677+ </variablelist>
678+ <variablelist>
679+ <varlistentry>
680+ <term>Inverse Transfer function:</term>
681+ <listitem>
682+ <para>L = -((L'&nbsp;-&nbsp;0.099)&nbsp;/&nbsp;-1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&le;&nbsp;-0.081</para>
683+ <para>L = L'&nbsp;/&nbsp;4.5&nbsp;for&nbsp;-0.081&nbsp;&lt;&nbsp;L'&nbsp;&lt;&nbsp;0.081</para>
684+ <para>L = ((L'&nbsp;+&nbsp;0.099)&nbsp;/&nbsp;1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.081</para>
685+ </listitem>
686+ </varlistentry>
687+ </variablelist>
688+ <variablelist>
689+ <varlistentry>
690+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with
691+the following <constant>V4L2_YCBCR_ENC_601</constant> encoding:</term>
692+ <listitem>
693+ <para>Y'&nbsp;=&nbsp;0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B'</para>
694+ <para>Cb&nbsp;=&nbsp;-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B'</para>
695+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B'</para>
696+ </listitem>
697+ </varlistentry>
698+ </variablelist>
699+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
700+clamped to the range [-0.5&hellip;0.5]. This conversion to Y'CbCr is identical to the one
701+defined in the <xref linkend="itu601" /> standard and this colorspace is sometimes called BT.601 as well, even
702+though BT.601 does not mention any color primaries.</para>
703+ <para>The default quantization is limited range, but full range is possible although
704+rarely seen.</para>
705+ <para>The <constant>V4L2_YCBCR_ENC_601</constant> encoding as described above is the
706+default for this colorspace, but it can be overridden with <constant>V4L2_YCBCR_ENC_709</constant>,
707+in which case the Rec. 709 Y'CbCr encoding is used.</para>
708+ <variablelist>
709+ <varlistentry>
710+ <term>The xvYCC 601 encoding (<constant>V4L2_YCBCR_ENC_XV601</constant>, <xref linkend="xvycc" />) is similar
711+to the BT.601 encoding, but it allows for R', G' and B' values that are outside the range
712+[0&hellip;1]. The resulting Y', Cb and Cr values are scaled and offset:</term>
713+ <listitem>
714+ <para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;255)</para>
715+ <para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B')</para>
716+ <para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B')</para>
717+ </listitem>
718+ </varlistentry>
719+ </variablelist>
720+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are clamped
721+to the range [-0.5&hellip;0.5]. The non-standard xvYCC 709 encoding can also be used by selecting
722+<constant>V4L2_YCBCR_ENC_XV709</constant>. The xvYCC encodings always use full range
723+quantization.</para>
724+ </section>
725+
726+ <section>
727+ <title id="col-rec709">Colorspace Rec. 709 (<constant>V4L2_COLORSPACE_REC709</constant>)</title>
728+ <para>The <xref linkend="itu709" /> standard defines the colorspace used by HDTV in general. The default
729+Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_709</constant>. The default Y'CbCr quantization is
730+limited range. The chromaticities of the primary colors and the white reference are:</para>
731+ <table frame="none">
732+ <title>Rec. 709 Chromaticities</title>
733+ <tgroup cols="3" align="left">
734+ &cs-str;
735+ <thead>
736+ <row>
737+ <entry>Color</entry>
738+ <entry>x</entry>
739+ <entry>y</entry>
740+ </row>
741+ </thead>
742+ <tbody valign="top">
743+ <row>
744+ <entry>Red</entry>
745+ <entry>0.640</entry>
746+ <entry>0.330</entry>
747+ </row>
748+ <row>
749+ <entry>Green</entry>
750+ <entry>0.300</entry>
751+ <entry>0.600</entry>
752+ </row>
753+ <row>
754+ <entry>Blue</entry>
755+ <entry>0.150</entry>
756+ <entry>0.060</entry>
757+ </row>
758+ <row>
759+ <entry>White Reference (D65)</entry>
760+ <entry>0.3127</entry>
761+ <entry>0.3290</entry>
762+ </row>
763+ </tbody>
764+ </tgroup>
765+ </table>
766+ <para>The full name of this standard is Rec. ITU-R BT.709-5.</para>
767+ <variablelist>
768+ <varlistentry>
769+ <term>Transfer function. Normally L is in the range [0&hellip;1], but for the extended
770+gamut xvYCC encoding values outside that range are allowed.</term>
771+ <listitem>
772+ <para>L' = -1.099(-L)<superscript>0.45</superscript>&nbsp;+&nbsp;0.099&nbsp;for&nbsp;L&nbsp;&le;&nbsp;-0.018</para>
773+ <para>L' = 4.5L&nbsp;for&nbsp;-0.018&nbsp;&lt;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
774+ <para>L' = 1.099L<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;L&nbsp;&ge;&nbsp;0.018</para>
775+ </listitem>
776+ </varlistentry>
777+ </variablelist>
778+ <variablelist>
779+ <varlistentry>
780+ <term>Inverse Transfer function:</term>
781+ <listitem>
782+ <para>L = -((L'&nbsp;-&nbsp;0.099)&nbsp;/&nbsp;-1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&le;&nbsp;-0.081</para>
783+ <para>L = L'&nbsp;/&nbsp;4.5&nbsp;for&nbsp;-0.081&nbsp;&lt;&nbsp;L'&nbsp;&lt;&nbsp;0.081</para>
784+ <para>L = ((L'&nbsp;+&nbsp;0.099)&nbsp;/&nbsp;1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.081</para>
785+ </listitem>
786+ </varlistentry>
787+ </variablelist>
788+ <variablelist>
789+ <varlistentry>
790+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the following
791+<constant>V4L2_YCBCR_ENC_709</constant> encoding:</term>
792+ <listitem>
793+ <para>Y'&nbsp;=&nbsp;0.2126R'&nbsp;+&nbsp;0.7152G'&nbsp;+&nbsp;0.0722B'</para>
794+ <para>Cb&nbsp;=&nbsp;-0.1146R'&nbsp;-&nbsp;0.3854G'&nbsp;+&nbsp;0.5B'</para>
795+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.4542G'&nbsp;-&nbsp;0.0458B'</para>
796+ </listitem>
797+ </varlistentry>
798+ </variablelist>
799+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
800+clamped to the range [-0.5&hellip;0.5].</para>
801+ <para>The default quantization is limited range, but full range is possible although
802+rarely seen.</para>
803+ <para>The <constant>V4L2_YCBCR_ENC_709</constant> encoding described above is the default
804+for this colorspace, but it can be overridden with <constant>V4L2_YCBCR_ENC_601</constant>, in which
805+case the BT.601 Y'CbCr encoding is used.</para>
806+ <variablelist>
807+ <varlistentry>
808+ <term>The xvYCC 709 encoding (<constant>V4L2_YCBCR_ENC_XV709</constant>, <xref linkend="xvycc" />)
809+is similar to the Rec. 709 encoding, but it allows for R', G' and B' values that are outside the range
810+[0&hellip;1]. The resulting Y', Cb and Cr values are scaled and offset:</term>
811+ <listitem>
812+ <para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.2126R'&nbsp;+&nbsp;0.7152G'&nbsp;+&nbsp;0.0722B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;255)</para>
813+ <para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(-0.1146R'&nbsp;-&nbsp;0.3854G'&nbsp;+&nbsp;0.5B')</para>
814+ <para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.4542G'&nbsp;-&nbsp;0.0458B')</para>
815+ </listitem>
816+ </varlistentry>
817+ </variablelist>
818+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are clamped
819+to the range [-0.5&hellip;0.5]. The non-standard xvYCC 601 encoding can also be used by
820+selecting <constant>V4L2_YCBCR_ENC_XV601</constant>. The xvYCC encodings always use full
821+range quantization.</para>
822+ </section>
823+
824+ <section>
825+ <title id="col-srgb">Colorspace sRGB (<constant>V4L2_COLORSPACE_SRGB</constant>)</title>
826+ <para>The <xref linkend="srgb" /> standard defines the colorspace used by most webcams and computer graphics. The
827+default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_SYCC</constant>. The default Y'CbCr quantization
828+is full range. The chromaticities of the primary colors and the white reference are:</para>
829+ <table frame="none">
830+ <title>sRGB Chromaticities</title>
831+ <tgroup cols="3" align="left">
832+ &cs-str;
833+ <thead>
834+ <row>
835+ <entry>Color</entry>
836+ <entry>x</entry>
837+ <entry>y</entry>
838+ </row>
839+ </thead>
840+ <tbody valign="top">
841+ <row>
842+ <entry>Red</entry>
843+ <entry>0.640</entry>
844+ <entry>0.330</entry>
845+ </row>
846+ <row>
847+ <entry>Green</entry>
848+ <entry>0.300</entry>
849+ <entry>0.600</entry>
850+ </row>
851+ <row>
852+ <entry>Blue</entry>
853+ <entry>0.150</entry>
854+ <entry>0.060</entry>
855+ </row>
856+ <row>
857+ <entry>White Reference (D65)</entry>
858+ <entry>0.3127</entry>
859+ <entry>0.3290</entry>
860+ </row>
861+ </tbody>
862+ </tgroup>
863+ </table>
864+ <para>These chromaticities are identical to the Rec. 709 colorspace.</para>
865+ <variablelist>
866+ <varlistentry>
867+ <term>Transfer function. Note that negative values for L are only used by the Y'CbCr conversion.</term>
868+ <listitem>
869+ <para>L' = -1.055(-L)<superscript>1/2.4</superscript>&nbsp;+&nbsp;0.055&nbsp;for&nbsp;L&nbsp;&lt;&nbsp;-0.0031308</para>
870+ <para>L' = 12.92L&nbsp;for&nbsp;-0.0031308&nbsp;&le;&nbsp;L&nbsp;&le;&nbsp;0.0031308</para>
871+ <para>L' = 1.055L<superscript>1/2.4</superscript>&nbsp;-&nbsp;0.055&nbsp;for&nbsp;0.0031308&nbsp;&lt;&nbsp;L&nbsp;&le;&nbsp;1</para>
872+ </listitem>
873+ </varlistentry>
874+ <varlistentry>
875+ <term>Inverse Transfer function:</term>
876+ <listitem>
877+ <para>L = -((-L'&nbsp;+&nbsp;0.055)&nbsp;/&nbsp;1.055)<superscript>2.4</superscript>&nbsp;for&nbsp;L'&nbsp;&lt;&nbsp;-0.04045</para>
878+ <para>L = L'&nbsp;/&nbsp;12.92&nbsp;for&nbsp;-0.04045&nbsp;&le;&nbsp;L'&nbsp;&le;&nbsp;0.04045</para>
879+ <para>L = ((L'&nbsp;+&nbsp;0.055)&nbsp;/&nbsp;1.055)<superscript>2.4</superscript>&nbsp;for&nbsp;L'&nbsp;&gt;&nbsp;0.04045</para>
880+ </listitem>
881+ </varlistentry>
882+ </variablelist>
883+ <variablelist>
884+ <varlistentry>
885+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the following
886+<constant>V4L2_YCBCR_ENC_SYCC</constant> encoding as defined by <xref linkend="sycc" />:</term>
887+ <listitem>
888+ <para>Y'&nbsp;=&nbsp;0.2990R'&nbsp;+&nbsp;0.5870G'&nbsp;+&nbsp;0.1140B'</para>
889+ <para>Cb&nbsp;=&nbsp;-0.1687R'&nbsp;-&nbsp;0.3313G'&nbsp;+&nbsp;0.5B'</para>
890+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.4187G'&nbsp;-&nbsp;0.0813B'</para>
891+ </listitem>
892+ </varlistentry>
893+ </variablelist>
894+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are clamped
895+to the range [-0.5&hellip;0.5]. The <constant>V4L2_YCBCR_ENC_SYCC</constant> quantization is always
896+full range. Although this Y'CbCr encoding looks very similar to the <constant>V4L2_YCBCR_ENC_XV601</constant>
897+encoding, it is not. The <constant>V4L2_YCBCR_ENC_XV601</constant> scales and offsets the Y'CbCr
898+values before quantization, but this encoding does not do that.</para>
899+ </section>
900+
901+ <section>
902+ <title id="col-adobergb">Colorspace Adobe RGB (<constant>V4L2_COLORSPACE_ADOBERGB</constant>)</title>
903+ <para>The <xref linkend="adobergb" /> standard defines the colorspace used by computer graphics
904+that use the AdobeRGB colorspace. This is also known as the <xref linkend="oprgb" /> standard.
905+The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr
906+quantization is limited range. The chromaticities of the primary colors and the white reference
907+are:</para>
908+ <table frame="none">
909+ <title>Adobe RGB Chromaticities</title>
910+ <tgroup cols="3" align="left">
911+ &cs-str;
912+ <thead>
913+ <row>
914+ <entry>Color</entry>
915+ <entry>x</entry>
916+ <entry>y</entry>
917+ </row>
918+ </thead>
919+ <tbody valign="top">
920+ <row>
921+ <entry>Red</entry>
922+ <entry>0.6400</entry>
923+ <entry>0.3300</entry>
924+ </row>
925+ <row>
926+ <entry>Green</entry>
927+ <entry>0.2100</entry>
928+ <entry>0.7100</entry>
929+ </row>
930+ <row>
931+ <entry>Blue</entry>
932+ <entry>0.1500</entry>
933+ <entry>0.0600</entry>
934+ </row>
935+ <row>
936+ <entry>White Reference (D65)</entry>
937+ <entry>0.3127</entry>
938+ <entry>0.3290</entry>
939+ </row>
940+ </tbody>
941+ </tgroup>
942+ </table>
943+ <variablelist>
944+ <varlistentry>
945+ <term>Transfer function:</term>
946+ <listitem>
947+ <para>L' = L<superscript>1/2.19921875</superscript></para>
948+ </listitem>
949+ </varlistentry>
950+ <varlistentry>
951+ <term>Inverse Transfer function:</term>
952+ <listitem>
953+ <para>L = L'<superscript>2.19921875</superscript></para>
954+ </listitem>
955+ </varlistentry>
956+ </variablelist>
957+ <variablelist>
958+ <varlistentry>
959+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
960+following <constant>V4L2_YCBCR_ENC_601</constant> encoding:</term>
961+ <listitem>
962+ <para>Y'&nbsp;=&nbsp;0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B'</para>
963+ <para>Cb&nbsp;=&nbsp;-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B'</para>
964+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B'</para>
965+ </listitem>
966+ </varlistentry>
967+ </variablelist>
968+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
969+clamped to the range [-0.5&hellip;0.5]. This transform is identical to one defined in
970+SMPTE 170M/BT.601. The Y'CbCr quantization is limited range.</para>
971+ </section>
972+
973+ <section>
974+ <title id="col-bt2020">Colorspace BT.2020 (<constant>V4L2_COLORSPACE_BT2020</constant>)</title>
975+ <para>The <xref linkend="itu2020" /> standard defines the colorspace used by Ultra-high definition
976+television (UHDTV). The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_BT2020</constant>.
977+The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and
978+the white reference are:</para>
979+ <table frame="none">
980+ <title>BT.2020 Chromaticities</title>
981+ <tgroup cols="3" align="left">
982+ &cs-str;
983+ <thead>
984+ <row>
985+ <entry>Color</entry>
986+ <entry>x</entry>
987+ <entry>y</entry>
988+ </row>
989+ </thead>
990+ <tbody valign="top">
991+ <row>
992+ <entry>Red</entry>
993+ <entry>0.708</entry>
994+ <entry>0.292</entry>
995+ </row>
996+ <row>
997+ <entry>Green</entry>
998+ <entry>0.170</entry>
999+ <entry>0.797</entry>
1000+ </row>
1001+ <row>
1002+ <entry>Blue</entry>
1003+ <entry>0.131</entry>
1004+ <entry>0.046</entry>
1005+ </row>
1006+ <row>
1007+ <entry>White Reference (D65)</entry>
1008+ <entry>0.3127</entry>
1009+ <entry>0.3290</entry>
1010+ </row>
1011+ </tbody>
1012+ </tgroup>
1013+ </table>
1014+ <variablelist>
1015+ <varlistentry>
1016+ <term>Transfer function (same as Rec. 709):</term>
1017+ <listitem>
1018+ <para>L' = 4.5L&nbsp;for&nbsp;0&nbsp;&le;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
1019+ <para>L' = 1.099L<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&le;&nbsp;L&nbsp;&le;&nbsp;1</para>
1020+ </listitem>
1021+ </varlistentry>
1022+ <varlistentry>
1023+ <term>Inverse Transfer function:</term>
1024+ <listitem>
1025+ <para>L = L'&nbsp;/&nbsp;4.5&nbsp;for&nbsp;L'&nbsp;&lt;&nbsp;0.081</para>
1026+ <para>L = ((L'&nbsp;+&nbsp;0.099)&nbsp;/&nbsp;1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.081</para>
1027+ </listitem>
1028+ </varlistentry>
1029+ </variablelist>
1030+ <variablelist>
1031+ <varlistentry>
1032+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
1033+following <constant>V4L2_YCBCR_ENC_BT2020</constant> encoding:</term>
1034+ <listitem>
1035+ <para>Y'&nbsp;=&nbsp;0.2627R'&nbsp;+&nbsp;0.6789G'&nbsp;+&nbsp;0.0593B'</para>
1036+ <para>Cb&nbsp;=&nbsp;-0.1396R'&nbsp;-&nbsp;0.3604G'&nbsp;+&nbsp;0.5B'</para>
1037+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.4598G'&nbsp;-&nbsp;0.0402B'</para>
1038+ </listitem>
1039+ </varlistentry>
1040+ </variablelist>
1041+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
1042+clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range.</para>
1043+ <para>There is also an alternate constant luminance R'G'B' to Yc'CbcCrc
1044+(<constant>V4L2_YCBCR_ENC_BT2020_CONST_LUM</constant>) encoding:</para>
1045+ <variablelist>
1046+ <varlistentry>
1047+ <term>Luma:</term>
1048+ <listitem>
1049+ <para>Yc'&nbsp;=&nbsp;(0.2627R&nbsp;+&nbsp;0.6789G&nbsp;+&nbsp;0.0593B)'</para>
1050+ </listitem>
1051+ </varlistentry>
1052+ </variablelist>
1053+ <variablelist>
1054+ <varlistentry>
1055+ <term>B'&nbsp;-&nbsp;Yc'&nbsp;&le;&nbsp;0:</term>
1056+ <listitem>
1057+ <para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;1.9404</para>
1058+ </listitem>
1059+ </varlistentry>
1060+ </variablelist>
1061+ <variablelist>
1062+ <varlistentry>
1063+ <term>B'&nbsp;-&nbsp;Yc'&nbsp;&gt;&nbsp;0:</term>
1064+ <listitem>
1065+ <para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;1.5816</para>
1066+ </listitem>
1067+ </varlistentry>
1068+ </variablelist>
1069+ <variablelist>
1070+ <varlistentry>
1071+ <term>R'&nbsp;-&nbsp;Yc'&nbsp;&le;&nbsp;0:</term>
1072+ <listitem>
1073+ <para>Crc&nbsp;=&nbsp;(R'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;1.7184</para>
1074+ </listitem>
1075+ </varlistentry>
1076+ </variablelist>
1077+ <variablelist>
1078+ <varlistentry>
1079+ <term>R'&nbsp;-&nbsp;Yc'&nbsp;&gt;&nbsp;0:</term>
1080+ <listitem>
1081+ <para>Crc&nbsp;=&nbsp;(R'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;0.9936</para>
1082+ </listitem>
1083+ </varlistentry>
1084+ </variablelist>
1085+ <para>Yc' is clamped to the range [0&hellip;1] and Cbc and Crc are
1086+clamped to the range [-0.5&hellip;0.5]. The Yc'CbcCrc quantization is limited range.</para>
1087+ </section>
1088+
1089+ <section>
1090+ <title id="col-smpte-240m">Colorspace SMPTE 240M (<constant>V4L2_COLORSPACE_SMPTE240M</constant>)</title>
1091+ <para>The <xref linkend="smpte240m" /> standard was an interim standard used during the early days of HDTV (1988-1998).
1092+It has been superseded by Rec. 709. The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_SMPTE240M</constant>.
1093+The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and the
1094+white reference are:</para>
1095+ <table frame="none">
1096+ <title>SMPTE 240M Chromaticities</title>
1097+ <tgroup cols="3" align="left">
1098+ &cs-str;
1099+ <thead>
1100+ <row>
1101+ <entry>Color</entry>
1102+ <entry>x</entry>
1103+ <entry>y</entry>
1104+ </row>
1105+ </thead>
1106+ <tbody valign="top">
1107+ <row>
1108+ <entry>Red</entry>
1109+ <entry>0.630</entry>
1110+ <entry>0.340</entry>
1111+ </row>
1112+ <row>
1113+ <entry>Green</entry>
1114+ <entry>0.310</entry>
1115+ <entry>0.595</entry>
1116+ </row>
1117+ <row>
1118+ <entry>Blue</entry>
1119+ <entry>0.155</entry>
1120+ <entry>0.070</entry>
1121+ </row>
1122+ <row>
1123+ <entry>White Reference (D65)</entry>
1124+ <entry>0.3127</entry>
1125+ <entry>0.3290</entry>
1126+ </row>
1127+ </tbody>
1128+ </tgroup>
1129+ </table>
1130+ <para>These chromaticities are identical to the SMPTE 170M colorspace.</para>
1131+ <variablelist>
1132+ <varlistentry>
1133+ <term>Transfer function:</term>
1134+ <listitem>
1135+ <para>L' = 4L&nbsp;for&nbsp;0&nbsp;&le;&nbsp;L&nbsp;&lt;&nbsp;0.0228</para>
1136+ <para>L' = 1.1115L<superscript>0.45</superscript>&nbsp;-&nbsp;0.1115&nbsp;for&nbsp;0.0228&nbsp;&le;&nbsp;L&nbsp;&le;&nbsp;1</para>
1137+ </listitem>
1138+ </varlistentry>
1139+ <varlistentry>
1140+ <term>Inverse Transfer function:</term>
1141+ <listitem>
1142+ <para>L = L'&nbsp;/&nbsp;4&nbsp;for&nbsp;0&nbsp;&le;&nbsp;L'&nbsp;&lt;&nbsp;0.0913</para>
1143+ <para>L = ((L'&nbsp;+&nbsp;0.1115)&nbsp;/&nbsp;1.1115)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.0913</para>
1144+ </listitem>
1145+ </varlistentry>
1146+ </variablelist>
1147+ <variablelist>
1148+ <varlistentry>
1149+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
1150+following <constant>V4L2_YCBCR_ENC_SMPTE240M</constant> encoding:</term>
1151+ <listitem>
1152+ <para>Y'&nbsp;=&nbsp;0.2122R'&nbsp;+&nbsp;0.7013G'&nbsp;+&nbsp;0.0865B'</para>
1153+ <para>Cb&nbsp;=&nbsp;-0.1161R'&nbsp;-&nbsp;0.3839G'&nbsp;+&nbsp;0.5B'</para>
1154+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.4451G'&nbsp;-&nbsp;0.0549B'</para>
1155+ </listitem>
1156+ </varlistentry>
1157+ </variablelist>
1158+ <para>Yc' is clamped to the range [0&hellip;1] and Cbc and Crc are
1159+clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range.</para>
1160+ </section>
1161+
1162+ <section>
1163+ <title id="col-sysm">Colorspace NTSC 1953 (<constant>V4L2_COLORSPACE_470_SYSTEM_M</constant>)</title>
1164+ <para>This standard defines the colorspace used by NTSC in 1953. In practice this
1165+colorspace is obsolete and SMPTE 170M should be used instead. The default Y'CbCr encoding
1166+is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr quantization is limited range.
1167+The chromaticities of the primary colors and the white reference are:</para>
1168+ <table frame="none">
1169+ <title>NTSC 1953 Chromaticities</title>
1170+ <tgroup cols="3" align="left">
1171+ &cs-str;
1172+ <thead>
1173+ <row>
1174+ <entry>Color</entry>
1175+ <entry>x</entry>
1176+ <entry>y</entry>
1177+ </row>
1178+ </thead>
1179+ <tbody valign="top">
1180+ <row>
1181+ <entry>Red</entry>
1182+ <entry>0.67</entry>
1183+ <entry>0.33</entry>
1184+ </row>
1185+ <row>
1186+ <entry>Green</entry>
1187+ <entry>0.21</entry>
1188+ <entry>0.71</entry>
1189+ </row>
1190+ <row>
1191+ <entry>Blue</entry>
1192+ <entry>0.14</entry>
1193+ <entry>0.08</entry>
1194+ </row>
1195+ <row>
1196+ <entry>White Reference (C)</entry>
1197+ <entry>0.310</entry>
1198+ <entry>0.316</entry>
1199+ </row>
1200+ </tbody>
1201+ </tgroup>
1202+ </table>
1203+ <para>Note that this colorspace uses Illuminant C instead of D65 as the
1204+white reference. To correctly convert an image in this colorspace to another
1205+that uses D65 you need to apply a chromatic adaptation algorithm such as the
1206+Bradford method.</para>
1207+ <variablelist>
1208+ <varlistentry>
1209+ <term>The transfer function was never properly defined for NTSC 1953. The
1210+Rec. 709 transfer function is recommended in the literature:</term>
1211+ <listitem>
1212+ <para>L' = 4.5L&nbsp;for&nbsp;0&nbsp;&le;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
1213+ <para>L' = 1.099L<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&le;&nbsp;L&nbsp;&le;&nbsp;1</para>
1214+ </listitem>
1215+ </varlistentry>
1216+ <varlistentry>
1217+ <term>Inverse Transfer function:</term>
1218+ <listitem>
1219+ <para>L = L'&nbsp;/&nbsp;4.5&nbsp;for&nbsp;L'&nbsp;&lt;&nbsp;0.081</para>
1220+ <para>L = ((L'&nbsp;+&nbsp;0.099)&nbsp;/&nbsp;1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.081</para>
1221+ </listitem>
1222+ </varlistentry>
1223+ </variablelist>
1224+ <variablelist>
1225+ <varlistentry>
1226+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
1227+following <constant>V4L2_YCBCR_ENC_601</constant> encoding:</term>
1228+ <listitem>
1229+ <para>Y'&nbsp;=&nbsp;0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B'</para>
1230+ <para>Cb&nbsp;=&nbsp;-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B'</para>
1231+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B'</para>
1232+ </listitem>
1233+ </varlistentry>
1234+ </variablelist>
1235+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
1236+clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range.
1237+This transform is identical to one defined in SMPTE 170M/BT.601.</para>
1238+ </section>
1239+
1240+ <section>
1241+ <title id="col-sysbg">Colorspace EBU Tech. 3213 (<constant>V4L2_COLORSPACE_470_SYSTEM_BG</constant>)</title>
1242+ <para>The <xref linkend="tech3213" /> standard defines the colorspace used by PAL/SECAM in 1975. In practice this
1243+colorspace is obsolete and SMPTE 170M should be used instead. The default Y'CbCr encoding
1244+is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr quantization is limited range.
1245+The chromaticities of the primary colors and the white reference are:</para>
1246+ <table frame="none">
1247+ <title>EBU Tech. 3213 Chromaticities</title>
1248+ <tgroup cols="3" align="left">
1249+ &cs-str;
1250+ <thead>
1251+ <row>
1252+ <entry>Color</entry>
1253+ <entry>x</entry>
1254+ <entry>y</entry>
1255+ </row>
1256+ </thead>
1257+ <tbody valign="top">
1258+ <row>
1259+ <entry>Red</entry>
1260+ <entry>0.64</entry>
1261+ <entry>0.33</entry>
1262+ </row>
1263+ <row>
1264+ <entry>Green</entry>
1265+ <entry>0.29</entry>
1266+ <entry>0.60</entry>
1267+ </row>
1268+ <row>
1269+ <entry>Blue</entry>
1270+ <entry>0.15</entry>
1271+ <entry>0.06</entry>
1272+ </row>
1273+ <row>
1274+ <entry>White Reference (D65)</entry>
1275+ <entry>0.3127</entry>
1276+ <entry>0.3290</entry>
1277+ </row>
1278+ </tbody>
1279+ </tgroup>
1280+ </table>
1281+ <variablelist>
1282+ <varlistentry>
1283+ <term>The transfer function was never properly defined for this colorspace.
1284+The Rec. 709 transfer function is recommended in the literature:</term>
1285+ <listitem>
1286+ <para>L' = 4.5L&nbsp;for&nbsp;0&nbsp;&le;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
1287+ <para>L' = 1.099L<superscript>0.45</superscript>&nbsp;-&nbsp;0.099&nbsp;for&nbsp;0.018&nbsp;&le;&nbsp;L&nbsp;&le;&nbsp;1</para>
1288+ </listitem>
1289+ </varlistentry>
1290+ <varlistentry>
1291+ <term>Inverse Transfer function:</term>
1292+ <listitem>
1293+ <para>L = L'&nbsp;/&nbsp;4.5&nbsp;for&nbsp;L'&nbsp;&lt;&nbsp;0.081</para>
1294+ <para>L = ((L'&nbsp;+&nbsp;0.099)&nbsp;/&nbsp;1.099)<superscript>1/0.45</superscript>&nbsp;for&nbsp;L'&nbsp;&ge;&nbsp;0.081</para>
1295+ </listitem>
1296+ </varlistentry>
1297+ </variablelist>
1298+ <variablelist>
1299+ <varlistentry>
1300+ <term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
1301+following <constant>V4L2_YCBCR_ENC_601</constant> encoding:</term>
1302+ <listitem>
1303+ <para>Y'&nbsp;=&nbsp;0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B'</para>
1304+ <para>Cb&nbsp;=&nbsp;-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B'</para>
1305+ <para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B'</para>
1306+ </listitem>
1307+ </varlistentry>
1308+ </variablelist>
1309+ <para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are
1310+clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range.
1311+This transform is identical to one defined in SMPTE 170M/BT.601.</para>
1312+ </section>
1313+
1314+ <section>
1315+ <title id="col-jpeg">Colorspace JPEG (<constant>V4L2_COLORSPACE_JPEG</constant>)</title>
1316+ <para>This colorspace defines the colorspace used by most (Motion-)JPEG formats. The chromaticities
1317+of the primary colors and the white reference are identical to sRGB. The Y'CbCr encoding is
1318+<constant>V4L2_YCBCR_ENC_601</constant> with full range quantization where
1319+Y' is scaled to [0&hellip;255] and Cb/Cr are scaled to [-128&hellip;128] and
1320+then clipped to [-128&hellip;127].</para>
1321+ <para>Note that the JPEG standard does not actually store colorspace information.
1322+So if something other than sRGB is used, then the driver will have to set that information
1323+explicitly. Effectively <constant>V4L2_COLORSPACE_JPEG</constant> can be considered to be
1324+an abbreviation for <constant>V4L2_COLORSPACE_SRGB</constant>, <constant>V4L2_YCBCR_ENC_601</constant>
1325+and <constant>V4L2_QUANTIZATION_FULL_RANGE</constant>.</para>
1326+ </section>
1327+
1328+ </section>
1329+
6381330 <section id="pixfmt-indexed">
6391331 <title>Indexed Format</title>
6401332
Documentation/DocBook/media/v4l/selections-common.xml+16−0
@@ -62,6 +62,22 @@ · 61 unmodified lines
6262 <entry>Yes</entry>
6363 <entry>Yes</entry>
6464 </row>
65+ <row>
66+ <entry><constant>V4L2_SEL_TGT_NATIVE_SIZE</constant></entry>
67+ <entry>0x0003</entry>
68+ <entry>The native size of the device, e.g. a sensor's
69+ pixel array. <structfield>left</structfield> and
70+ <structfield>top</structfield> fields are zero for this
71+ target. Setting the native size will generally only make
72+ sense for memory to memory devices where the software can
73+ create a canvas of a given size in which for example a
74+ video frame can be composed. In that case
75+ V4L2_SEL_TGT_NATIVE_SIZE can be used to configure the size
76+ of that canvas.
77+ </entry>
78+ <entry>Yes</entry>
79+ <entry>Yes</entry>
80+ </row>
6581 <row>
6682 <entry><constant>V4L2_SEL_TGT_COMPOSE</constant></entry>
6783 <entry>0x0100</entry>
Documentation/DocBook/media/v4l/subdev-formats.xml+171−155
@@ -33,9 +33,25 @@ · 32 unmodified lines
3333 <entry>Image colorspace, from &v4l2-colorspace;. See
3434 <xref linkend="colorspaces" /> for details.</entry>
3535 </row>
36+ <row>
37+ <entry>&v4l2-ycbcr-encoding;</entry>
38+ <entry><structfield>ycbcr_enc</structfield></entry>
39+ <entry>This information supplements the
40+<structfield>colorspace</structfield> and must be set by the driver for
41+capture streams and by the application for output streams,
42+see <xref linkend="colorspaces" />.</entry>
43+ </row>
44+ <row>
45+ <entry>&v4l2-quantization;</entry>
46+ <entry><structfield>quantization</structfield></entry>
47+ <entry>This information supplements the
48+<structfield>colorspace</structfield> and must be set by the driver for
49+capture streams and by the application for output streams,
50+see <xref linkend="colorspaces" />.</entry>
51+ </row>
3652 <row>
3753 <entry>__u32</entry>
38− <entry><structfield>reserved</structfield>[7]</entry>
54+ <entry><structfield>reserved</structfield>[6]</entry>
3955 <entry>Reserved for future extensions. Applications and drivers must
4056 set the array to zero.</entry>
4157 </row>
@@ -86,7 +102,7 @@ · 44 unmodified lines
86102 green and 5-bit blue values padded on the high bit, transferred as 2 8-bit
87103 samples per pixel with the most significant bits (padding, red and half of
88104 the green value) transferred first will be named
89− <constant>V4L2_MBUS_FMT_RGB555_2X8_PADHI_BE</constant>.
105+ <constant>MEDIA_BUS_FMT_RGB555_2X8_PADHI_BE</constant>.
90106 </para>
91107
92108 <para>The following tables list existing packed RGB formats.</para>
@@ -176,8 +192,8 @@ · 83 unmodified lines
176192 </row>
177193 </thead>
178194 <tbody valign="top">
179− <row id="V4L2-MBUS-FMT-RGB444-2X8-PADHI-BE">
180− <entry>V4L2_MBUS_FMT_RGB444_2X8_PADHI_BE</entry>
195+ <row id="MEDIA-BUS-FMT-RGB444-2X8-PADHI-BE">
196+ <entry>MEDIA_BUS_FMT_RGB444_2X8_PADHI_BE</entry>
181197 <entry>0x1001</entry>
182198 <entry></entry>
183199 &dash-ent-24;
@@ -204,8 +220,8 @@ · 20 unmodified lines
204220 <entry>b<subscript>1</subscript></entry>
205221 <entry>b<subscript>0</subscript></entry>
206222 </row>
207− <row id="V4L2-MBUS-FMT-RGB444-2X8-PADHI-LE">
208− <entry>V4L2_MBUS_FMT_RGB444_2X8_PADHI_LE</entry>
223+ <row id="MEDIA-BUS-FMT-RGB444-2X8-PADHI-LE">
224+ <entry>MEDIA_BUS_FMT_RGB444_2X8_PADHI_LE</entry>
209225 <entry>0x1002</entry>
210226 <entry></entry>
211227 &dash-ent-24;
@@ -232,8 +248,8 @@ · 20 unmodified lines
232248 <entry>r<subscript>1</subscript></entry>
233249 <entry>r<subscript>0</subscript></entry>
234250 </row>
235− <row id="V4L2-MBUS-FMT-RGB555-2X8-PADHI-BE">
236− <entry>V4L2_MBUS_FMT_RGB555_2X8_PADHI_BE</entry>
251+ <row id="MEDIA-BUS-FMT-RGB555-2X8-PADHI-BE">
252+ <entry>MEDIA_BUS_FMT_RGB555_2X8_PADHI_BE</entry>
237253 <entry>0x1003</entry>
238254 <entry></entry>
239255 &dash-ent-24;
@@ -260,8 +276,8 @@ · 20 unmodified lines
260276 <entry>b<subscript>1</subscript></entry>
261277 <entry>b<subscript>0</subscript></entry>
262278 </row>
263− <row id="V4L2-MBUS-FMT-RGB555-2X8-PADHI-LE">
264− <entry>V4L2_MBUS_FMT_RGB555_2X8_PADHI_LE</entry>
279+ <row id="MEDIA-BUS-FMT-RGB555-2X8-PADHI-LE">
280+ <entry>MEDIA_BUS_FMT_RGB555_2X8_PADHI_LE</entry>
265281 <entry>0x1004</entry>
266282 <entry></entry>
267283 &dash-ent-24;
@@ -288,8 +304,8 @@ · 20 unmodified lines
288304 <entry>g<subscript>4</subscript></entry>
289305 <entry>g<subscript>3</subscript></entry>
290306 </row>
291− <row id="V4L2-MBUS-FMT-BGR565-2X8-BE">
292− <entry>V4L2_MBUS_FMT_BGR565_2X8_BE</entry>
307+ <row id="MEDIA-BUS-FMT-BGR565-2X8-BE">
308+ <entry>MEDIA_BUS_FMT_BGR565_2X8_BE</entry>
293309 <entry>0x1005</entry>
294310 <entry></entry>
295311 &dash-ent-24;
@@ -316,8 +332,8 @@ · 20 unmodified lines
316332 <entry>r<subscript>1</subscript></entry>
317333 <entry>r<subscript>0</subscript></entry>
318334 </row>
319− <row id="V4L2-MBUS-FMT-BGR565-2X8-LE">
320− <entry>V4L2_MBUS_FMT_BGR565_2X8_LE</entry>
335+ <row id="MEDIA-BUS-FMT-BGR565-2X8-LE">
336+ <entry>MEDIA_BUS_FMT_BGR565_2X8_LE</entry>
321337 <entry>0x1006</entry>
322338 <entry></entry>
323339 &dash-ent-24;
@@ -344,8 +360,8 @@ · 20 unmodified lines
344360 <entry>g<subscript>4</subscript></entry>
345361 <entry>g<subscript>3</subscript></entry>
346362 </row>
347− <row id="V4L2-MBUS-FMT-RGB565-2X8-BE">
348− <entry>V4L2_MBUS_FMT_RGB565_2X8_BE</entry>
363+ <row id="MEDIA-BUS-FMT-RGB565-2X8-BE">
364+ <entry>MEDIA_BUS_FMT_RGB565_2X8_BE</entry>
349365 <entry>0x1007</entry>
350366 <entry></entry>
351367 &dash-ent-24;
@@ -372,8 +388,8 @@ · 20 unmodified lines
372388 <entry>b<subscript>1</subscript></entry>
373389 <entry>b<subscript>0</subscript></entry>
374390 </row>
375− <row id="V4L2-MBUS-FMT-RGB565-2X8-LE">
376− <entry>V4L2_MBUS_FMT_RGB565_2X8_LE</entry>
391+ <row id="MEDIA-BUS-FMT-RGB565-2X8-LE">
392+ <entry>MEDIA_BUS_FMT_RGB565_2X8_LE</entry>
377393 <entry>0x1008</entry>
378394 <entry></entry>
379395 &dash-ent-24;
@@ -400,8 +416,8 @@ · 20 unmodified lines
400416 <entry>g<subscript>4</subscript></entry>
401417 <entry>g<subscript>3</subscript></entry>
402418 </row>
403− <row id="V4L2-MBUS-FMT-RGB666-1X18">
404− <entry>V4L2_MBUS_FMT_RGB666_1X18</entry>
419+ <row id="MEDIA-BUS-FMT-RGB666-1X18">
420+ <entry>MEDIA_BUS_FMT_RGB666_1X18</entry>
405421 <entry>0x1009</entry>
406422 <entry></entry>
407423 &dash-ent-14;
@@ -424,8 +440,8 @@ · 16 unmodified lines
424440 <entry>b<subscript>1</subscript></entry>
425441 <entry>b<subscript>0</subscript></entry>
426442 </row>
427− <row id="V4L2-MBUS-FMT-RGB888-1X24">
428− <entry>V4L2_MBUS_FMT_RGB888_1X24</entry>
443+ <row id="MEDIA-BUS-FMT-RGB888-1X24">
444+ <entry>MEDIA_BUS_FMT_RGB888_1X24</entry>
429445 <entry>0x100a</entry>
430446 <entry></entry>
431447 &dash-ent-8;
@@ -454,8 +470,8 @@ · 22 unmodified lines
454470 <entry>b<subscript>1</subscript></entry>
455471 <entry>b<subscript>0</subscript></entry>
456472 </row>
457− <row id="V4L2-MBUS-FMT-RGB888-2X12-BE">
458− <entry>V4L2_MBUS_FMT_RGB888_2X12_BE</entry>
473+ <row id="MEDIA-BUS-FMT-RGB888-2X12-BE">
474+ <entry>MEDIA_BUS_FMT_RGB888_2X12_BE</entry>
459475 <entry>0x100b</entry>
460476 <entry></entry>
461477 &dash-ent-20;
@@ -490,8 +506,8 @@ · 28 unmodified lines
490506 <entry>b<subscript>1</subscript></entry>
491507 <entry>b<subscript>0</subscript></entry>
492508 </row>
493− <row id="V4L2-MBUS-FMT-RGB888-2X12-LE">
494− <entry>V4L2_MBUS_FMT_RGB888_2X12_LE</entry>
509+ <row id="MEDIA-BUS-FMT-RGB888-2X12-LE">
510+ <entry>MEDIA_BUS_FMT_RGB888_2X12_LE</entry>
495511 <entry>0x100c</entry>
496512 <entry></entry>
497513 &dash-ent-20;
@@ -526,8 +542,8 @@ · 28 unmodified lines
526542 <entry>g<subscript>5</subscript></entry>
527543 <entry>g<subscript>4</subscript></entry>
528544 </row>
529− <row id="V4L2-MBUS-FMT-ARGB888-1X32">
530− <entry>V4L2_MBUS_FMT_ARGB888_1X32</entry>
545+ <row id="MEDIA-BUS-FMT-ARGB888-1X32">
546+ <entry>MEDIA_BUS_FMT_ARGB888_1X32</entry>
531547 <entry>0x100d</entry>
532548 <entry></entry>
533549 <entry>a<subscript>7</subscript></entry>
@@ -600,7 +616,7 @@ · 66 unmodified lines
600616 <para>For instance, a format with uncompressed 10-bit Bayer components
601617 arranged in a red, green, green, blue pattern transferred as 2 8-bit
602618 samples per pixel with the least significant bits transferred first will
603− be named <constant>V4L2_MBUS_FMT_SRGGB10_2X8_PADHI_LE</constant>.
619+ be named <constant>MEDIA_BUS_FMT_SRGGB10_2X8_PADHI_LE</constant>.
604620 </para>
605621
606622 <figure id="bayer-patterns">
@@ -663,8 +679,8 @@ · 56 unmodified lines
663679 </row>
664680 </thead>
665681 <tbody valign="top">
666− <row id="V4L2-MBUS-FMT-SBGGR8-1X8">
667− <entry>V4L2_MBUS_FMT_SBGGR8_1X8</entry>
682+ <row id="MEDIA-BUS-FMT-SBGGR8-1X8">
683+ <entry>MEDIA_BUS_FMT_SBGGR8_1X8</entry>
668684 <entry>0x3001</entry>
669685 <entry></entry>
670686 <entry>-</entry>
@@ -680,8 +696,8 @@ · 9 unmodified lines
680696 <entry>b<subscript>1</subscript></entry>
681697 <entry>b<subscript>0</subscript></entry>
682698 </row>
683− <row id="V4L2-MBUS-FMT-SGBRG8-1X8">
684− <entry>V4L2_MBUS_FMT_SGBRG8_1X8</entry>
699+ <row id="MEDIA-BUS-FMT-SGBRG8-1X8">
700+ <entry>MEDIA_BUS_FMT_SGBRG8_1X8</entry>
685701 <entry>0x3013</entry>
686702 <entry></entry>
687703 <entry>-</entry>
@@ -697,8 +713,8 @@ · 9 unmodified lines
697713 <entry>g<subscript>1</subscript></entry>
698714 <entry>g<subscript>0</subscript></entry>
699715 </row>
700− <row id="V4L2-MBUS-FMT-SGRBG8-1X8">
701− <entry>V4L2_MBUS_FMT_SGRBG8_1X8</entry>
716+ <row id="MEDIA-BUS-FMT-SGRBG8-1X8">
717+ <entry>MEDIA_BUS_FMT_SGRBG8_1X8</entry>
702718 <entry>0x3002</entry>
703719 <entry></entry>
704720 <entry>-</entry>
@@ -714,8 +730,8 @@ · 9 unmodified lines
714730 <entry>g<subscript>1</subscript></entry>
715731 <entry>g<subscript>0</subscript></entry>
716732 </row>
717− <row id="V4L2-MBUS-FMT-SRGGB8-1X8">
718− <entry>V4L2_MBUS_FMT_SRGGB8_1X8</entry>
733+ <row id="MEDIA-BUS-FMT-SRGGB8-1X8">
734+ <entry>MEDIA_BUS_FMT_SRGGB8_1X8</entry>
719735 <entry>0x3014</entry>
720736 <entry></entry>
721737 <entry>-</entry>
@@ -731,8 +747,8 @@ · 9 unmodified lines
731747 <entry>r<subscript>1</subscript></entry>
732748 <entry>r<subscript>0</subscript></entry>
733749 </row>
734− <row id="V4L2-MBUS-FMT-SBGGR10-ALAW8-1X8">
735− <entry>V4L2_MBUS_FMT_SBGGR10_ALAW8_1X8</entry>
750+ <row id="MEDIA-BUS-FMT-SBGGR10-ALAW8-1X8">
751+ <entry>MEDIA_BUS_FMT_SBGGR10_ALAW8_1X8</entry>
736752 <entry>0x3015</entry>
737753 <entry></entry>
738754 <entry>-</entry>
@@ -748,8 +764,8 @@ · 9 unmodified lines
748764 <entry>b<subscript>1</subscript></entry>
749765 <entry>b<subscript>0</subscript></entry>
750766 </row>
751− <row id="V4L2-MBUS-FMT-SGBRG10-ALAW8-1X8">
752− <entry>V4L2_MBUS_FMT_SGBRG10_ALAW8_1X8</entry>
767+ <row id="MEDIA-BUS-FMT-SGBRG10-ALAW8-1X8">
768+ <entry>MEDIA_BUS_FMT_SGBRG10_ALAW8_1X8</entry>
753769 <entry>0x3016</entry>
754770 <entry></entry>
755771 <entry>-</entry>
@@ -765,8 +781,8 @@ · 9 unmodified lines
765781 <entry>g<subscript>1</subscript></entry>
766782 <entry>g<subscript>0</subscript></entry>
767783 </row>
768− <row id="V4L2-MBUS-FMT-SGRBG10-ALAW8-1X8">
769− <entry>V4L2_MBUS_FMT_SGRBG10_ALAW8_1X8</entry>
784+ <row id="MEDIA-BUS-FMT-SGRBG10-ALAW8-1X8">
785+ <entry>MEDIA_BUS_FMT_SGRBG10_ALAW8_1X8</entry>
770786 <entry>0x3017</entry>
771787 <entry></entry>
772788 <entry>-</entry>
@@ -782,8 +798,8 @@ · 9 unmodified lines
782798 <entry>g<subscript>1</subscript></entry>
783799 <entry>g<subscript>0</subscript></entry>
784800 </row>
785− <row id="V4L2-MBUS-FMT-SRGGB10-ALAW8-1X8">
786− <entry>V4L2_MBUS_FMT_SRGGB10_ALAW8_1X8</entry>
801+ <row id="MEDIA-BUS-FMT-SRGGB10-ALAW8-1X8">
802+ <entry>MEDIA_BUS_FMT_SRGGB10_ALAW8_1X8</entry>
787803 <entry>0x3018</entry>
788804 <entry></entry>
789805 <entry>-</entry>
@@ -799,8 +815,8 @@ · 9 unmodified lines
799815 <entry>r<subscript>1</subscript></entry>
800816 <entry>r<subscript>0</subscript></entry>
801817 </row>
802− <row id="V4L2-MBUS-FMT-SBGGR10-DPCM8-1X8">
803− <entry>V4L2_MBUS_FMT_SBGGR10_DPCM8_1X8</entry>
818+ <row id="MEDIA-BUS-FMT-SBGGR10-DPCM8-1X8">
819+ <entry>MEDIA_BUS_FMT_SBGGR10_DPCM8_1X8</entry>
804820 <entry>0x300b</entry>
805821 <entry></entry>
806822 <entry>-</entry>
@@ -816,8 +832,8 @@ · 9 unmodified lines
816832 <entry>b<subscript>1</subscript></entry>
817833 <entry>b<subscript>0</subscript></entry>
818834 </row>
819− <row id="V4L2-MBUS-FMT-SGBRG10-DPCM8-1X8">
820− <entry>V4L2_MBUS_FMT_SGBRG10_DPCM8_1X8</entry>
835+ <row id="MEDIA-BUS-FMT-SGBRG10-DPCM8-1X8">
836+ <entry>MEDIA_BUS_FMT_SGBRG10_DPCM8_1X8</entry>
821837 <entry>0x300c</entry>
822838 <entry></entry>
823839 <entry>-</entry>
@@ -833,8 +849,8 @@ · 9 unmodified lines
833849 <entry>g<subscript>1</subscript></entry>
834850 <entry>g<subscript>0</subscript></entry>
835851 </row>
836− <row id="V4L2-MBUS-FMT-SGRBG10-DPCM8-1X8">
837− <entry>V4L2_MBUS_FMT_SGRBG10_DPCM8_1X8</entry>
852+ <row id="MEDIA-BUS-FMT-SGRBG10-DPCM8-1X8">
853+ <entry>MEDIA_BUS_FMT_SGRBG10_DPCM8_1X8</entry>
838854 <entry>0x3009</entry>
839855 <entry></entry>
840856 <entry>-</entry>
@@ -850,8 +866,8 @@ · 9 unmodified lines
850866 <entry>g<subscript>1</subscript></entry>
851867 <entry>g<subscript>0</subscript></entry>
852868 </row>
853− <row id="V4L2-MBUS-FMT-SRGGB10-DPCM8-1X8">
854− <entry>V4L2_MBUS_FMT_SRGGB10_DPCM8_1X8</entry>
869+ <row id="MEDIA-BUS-FMT-SRGGB10-DPCM8-1X8">
870+ <entry>MEDIA_BUS_FMT_SRGGB10_DPCM8_1X8</entry>
855871 <entry>0x300d</entry>
856872 <entry></entry>
857873 <entry>-</entry>
@@ -867,8 +883,8 @@ · 9 unmodified lines
867883 <entry>r<subscript>1</subscript></entry>
868884 <entry>r<subscript>0</subscript></entry>
869885 </row>
870− <row id="V4L2-MBUS-FMT-SBGGR10-2X8-PADHI-BE">
871− <entry>V4L2_MBUS_FMT_SBGGR10_2X8_PADHI_BE</entry>
886+ <row id="MEDIA-BUS-FMT-SBGGR10-2X8-PADHI-BE">
887+ <entry>MEDIA_BUS_FMT_SBGGR10_2X8_PADHI_BE</entry>
872888 <entry>0x3003</entry>
873889 <entry></entry>
874890 <entry>-</entry>
@@ -901,8 +917,8 @@ · 26 unmodified lines
901917 <entry>b<subscript>1</subscript></entry>
902918 <entry>b<subscript>0</subscript></entry>
903919 </row>
904− <row id="V4L2-MBUS-FMT-SBGGR10-2X8-PADHI-LE">
905− <entry>V4L2_MBUS_FMT_SBGGR10_2X8_PADHI_LE</entry>
920+ <row id="MEDIA-BUS-FMT-SBGGR10-2X8-PADHI-LE">
921+ <entry>MEDIA_BUS_FMT_SBGGR10_2X8_PADHI_LE</entry>
906922 <entry>0x3004</entry>
907923 <entry></entry>
908924 <entry>-</entry>
@@ -935,8 +951,8 @@ · 26 unmodified lines
935951 <entry>b<subscript>9</subscript></entry>
936952 <entry>b<subscript>8</subscript></entry>
937953 </row>
938− <row id="V4L2-MBUS-FMT-SBGGR10-2X8-PADLO-BE">
939− <entry>V4L2_MBUS_FMT_SBGGR10_2X8_PADLO_BE</entry>
954+ <row id="MEDIA-BUS-FMT-SBGGR10-2X8-PADLO-BE">
955+ <entry>MEDIA_BUS_FMT_SBGGR10_2X8_PADLO_BE</entry>
940956 <entry>0x3005</entry>
941957 <entry></entry>
942958 <entry>-</entry>
@@ -969,8 +985,8 @@ · 26 unmodified lines
969985 <entry>0</entry>
970986 <entry>0</entry>
971987 </row>
972− <row id="V4L2-MBUS-FMT-SBGGR10-2X8-PADLO-LE">
973− <entry>V4L2_MBUS_FMT_SBGGR10_2X8_PADLO_LE</entry>
988+ <row id="MEDIA-BUS-FMT-SBGGR10-2X8-PADLO-LE">
989+ <entry>MEDIA_BUS_FMT_SBGGR10_2X8_PADLO_LE</entry>
974990 <entry>0x3006</entry>
975991 <entry></entry>
976992 <entry>-</entry>
@@ -1003,8 +1019,8 @@ · 26 unmodified lines
10031019 <entry>b<subscript>3</subscript></entry>
10041020 <entry>b<subscript>2</subscript></entry>
10051021 </row>
1006− <row id="V4L2-MBUS-FMT-SBGGR10-1X10">
1007− <entry>V4L2_MBUS_FMT_SBGGR10_1X10</entry>
1022+ <row id="MEDIA-BUS-FMT-SBGGR10-1X10">
1023+ <entry>MEDIA_BUS_FMT_SBGGR10_1X10</entry>
10081024 <entry>0x3007</entry>
10091025 <entry></entry>
10101026 <entry>-</entry>
@@ -1020,8 +1036,8 @@ · 9 unmodified lines
10201036 <entry>b<subscript>1</subscript></entry>
10211037 <entry>b<subscript>0</subscript></entry>
10221038 </row>
1023− <row id="V4L2-MBUS-FMT-SGBRG10-1X10">
1024− <entry>V4L2_MBUS_FMT_SGBRG10_1X10</entry>
1039+ <row id="MEDIA-BUS-FMT-SGBRG10-1X10">
1040+ <entry>MEDIA_BUS_FMT_SGBRG10_1X10</entry>
10251041 <entry>0x300e</entry>
10261042 <entry></entry>
10271043 <entry>-</entry>
@@ -1037,8 +1053,8 @@ · 9 unmodified lines
10371053 <entry>g<subscript>1</subscript></entry>
10381054 <entry>g<subscript>0</subscript></entry>
10391055 </row>
1040− <row id="V4L2-MBUS-FMT-SGRBG10-1X10">
1041− <entry>V4L2_MBUS_FMT_SGRBG10_1X10</entry>
1056+ <row id="MEDIA-BUS-FMT-SGRBG10-1X10">
1057+ <entry>MEDIA_BUS_FMT_SGRBG10_1X10</entry>
10421058 <entry>0x300a</entry>
10431059 <entry></entry>
10441060 <entry>-</entry>
@@ -1054,8 +1070,8 @@ · 9 unmodified lines
10541070 <entry>g<subscript>1</subscript></entry>
10551071 <entry>g<subscript>0</subscript></entry>
10561072 </row>
1057− <row id="V4L2-MBUS-FMT-SRGGB10-1X10">
1058− <entry>V4L2_MBUS_FMT_SRGGB10_1X10</entry>
1073+ <row id="MEDIA-BUS-FMT-SRGGB10-1X10">
1074+ <entry>MEDIA_BUS_FMT_SRGGB10_1X10</entry>
10591075 <entry>0x300f</entry>
10601076 <entry></entry>
10611077 <entry>-</entry>
@@ -1071,8 +1087,8 @@ · 9 unmodified lines
10711087 <entry>r<subscript>1</subscript></entry>
10721088 <entry>r<subscript>0</subscript></entry>
10731089 </row>
1074− <row id="V4L2-MBUS-FMT-SBGGR12-1X12">
1075− <entry>V4L2_MBUS_FMT_SBGGR12_1X12</entry>
1090+ <row id="MEDIA-BUS-FMT-SBGGR12-1X12">
1091+ <entry>MEDIA_BUS_FMT_SBGGR12_1X12</entry>
10761092 <entry>0x3008</entry>
10771093 <entry></entry>
10781094 <entry>b<subscript>11</subscript></entry>
@@ -1088,8 +1104,8 @@ · 9 unmodified lines
10881104 <entry>b<subscript>1</subscript></entry>
10891105 <entry>b<subscript>0</subscript></entry>
10901106 </row>
1091− <row id="V4L2-MBUS-FMT-SGBRG12-1X12">
1092− <entry>V4L2_MBUS_FMT_SGBRG12_1X12</entry>
1107+ <row id="MEDIA-BUS-FMT-SGBRG12-1X12">
1108+ <entry>MEDIA_BUS_FMT_SGBRG12_1X12</entry>
10931109 <entry>0x3010</entry>
10941110 <entry></entry>
10951111 <entry>g<subscript>11</subscript></entry>
@@ -1105,8 +1121,8 @@ · 9 unmodified lines
11051121 <entry>g<subscript>1</subscript></entry>
11061122 <entry>g<subscript>0</subscript></entry>
11071123 </row>
1108− <row id="V4L2-MBUS-FMT-SGRBG12-1X12">
1109− <entry>V4L2_MBUS_FMT_SGRBG12_1X12</entry>
1124+ <row id="MEDIA-BUS-FMT-SGRBG12-1X12">
1125+ <entry>MEDIA_BUS_FMT_SGRBG12_1X12</entry>
11101126 <entry>0x3011</entry>
11111127 <entry></entry>
11121128 <entry>g<subscript>11</subscript></entry>
@@ -1122,8 +1138,8 @@ · 9 unmodified lines
11221138 <entry>g<subscript>1</subscript></entry>
11231139 <entry>g<subscript>0</subscript></entry>
11241140 </row>
1125− <row id="V4L2-MBUS-FMT-SRGGB12-1X12">
1126− <entry>V4L2_MBUS_FMT_SRGGB12_1X12</entry>
1141+ <row id="MEDIA-BUS-FMT-SRGGB12-1X12">
1142+ <entry>MEDIA_BUS_FMT_SRGGB12_1X12</entry>
11271143 <entry>0x3012</entry>
11281144 <entry></entry>
11291145 <entry>r<subscript>11</subscript></entry>
@@ -1175,7 +1191,7 @@ · 45 unmodified lines
11751191
11761192 <para>For instance, a format where pixels are encoded as 8-bit YUV values
11771193 downsampled to 4:2:2 and transferred as 2 8-bit bus samples per pixel in the
1178− U, Y, V, Y order will be named <constant>V4L2_MBUS_FMT_UYVY8_2X8</constant>.
1194+ U, Y, V, Y order will be named <constant>MEDIA_BUS_FMT_UYVY8_2X8</constant>.
11791195 </para>
11801196
11811197 <para><xref linkend="v4l2-mbus-pixelcode-yuv8"/> lists existing packed YUV
@@ -1280,8 +1296,8 @@ · 98 unmodified lines
12801296 </row>
12811297 </thead>
12821298 <tbody valign="top">
1283− <row id="V4L2-MBUS-FMT-Y8-1X8">
1284− <entry>V4L2_MBUS_FMT_Y8_1X8</entry>
1299+ <row id="MEDIA-BUS-FMT-Y8-1X8">
1300+ <entry>MEDIA_BUS_FMT_Y8_1X8</entry>
12851301 <entry>0x2001</entry>
12861302 <entry></entry>
12871303 &dash-ent-24;
@@ -1294,8 +1310,8 @@ · 6 unmodified lines
12941310 <entry>y<subscript>1</subscript></entry>
12951311 <entry>y<subscript>0</subscript></entry>
12961312 </row>
1297− <row id="V4L2-MBUS-FMT-UV8-1X8">
1298− <entry>V4L2_MBUS_FMT_UV8_1X8</entry>
1313+ <row id="MEDIA-BUS-FMT-UV8-1X8">
1314+ <entry>MEDIA_BUS_FMT_UV8_1X8</entry>
12991315 <entry>0x2015</entry>
13001316 <entry></entry>
13011317 &dash-ent-24;
@@ -1322,8 +1338,8 @@ · 20 unmodified lines
13221338 <entry>v<subscript>1</subscript></entry>
13231339 <entry>v<subscript>0</subscript></entry>
13241340 </row>
1325− <row id="V4L2-MBUS-FMT-UYVY8-1_5X8">
1326− <entry>V4L2_MBUS_FMT_UYVY8_1_5X8</entry>
1341+ <row id="MEDIA-BUS-FMT-UYVY8-1_5X8">
1342+ <entry>MEDIA_BUS_FMT_UYVY8_1_5X8</entry>
13271343 <entry>0x2002</entry>
13281344 <entry></entry>
13291345 &dash-ent-24;
@@ -1406,8 +1422,8 @@ · 76 unmodified lines
14061422 <entry>y<subscript>1</subscript></entry>
14071423 <entry>y<subscript>0</subscript></entry>
14081424 </row>
1409− <row id="V4L2-MBUS-FMT-VYUY8-1_5X8">
1410− <entry>V4L2_MBUS_FMT_VYUY8_1_5X8</entry>
1425+ <row id="MEDIA-BUS-FMT-VYUY8-1_5X8">
1426+ <entry>MEDIA_BUS_FMT_VYUY8_1_5X8</entry>
14111427 <entry>0x2003</entry>
14121428 <entry></entry>
14131429 &dash-ent-24;
@@ -1490,8 +1506,8 @@ · 76 unmodified lines
14901506 <entry>y<subscript>1</subscript></entry>
14911507 <entry>y<subscript>0</subscript></entry>
14921508 </row>
1493− <row id="V4L2-MBUS-FMT-YUYV8-1_5X8">
1494− <entry>V4L2_MBUS_FMT_YUYV8_1_5X8</entry>
1509+ <row id="MEDIA-BUS-FMT-YUYV8-1_5X8">
1510+ <entry>MEDIA_BUS_FMT_YUYV8_1_5X8</entry>
14951511 <entry>0x2004</entry>
14961512 <entry></entry>
14971513 &dash-ent-24;
@@ -1574,8 +1590,8 @@ · 76 unmodified lines
15741590 <entry>v<subscript>1</subscript></entry>
15751591 <entry>v<subscript>0</subscript></entry>
15761592 </row>
1577− <row id="V4L2-MBUS-FMT-YVYU8-1_5X8">
1578− <entry>V4L2_MBUS_FMT_YVYU8_1_5X8</entry>
1593+ <row id="MEDIA-BUS-FMT-YVYU8-1_5X8">
1594+ <entry>MEDIA_BUS_FMT_YVYU8_1_5X8</entry>
15791595 <entry>0x2005</entry>
15801596 <entry></entry>
15811597 &dash-ent-24;
@@ -1658,8 +1674,8 @@ · 76 unmodified lines
16581674 <entry>u<subscript>1</subscript></entry>
16591675 <entry>u<subscript>0</subscript></entry>
16601676 </row>
1661− <row id="V4L2-MBUS-FMT-UYVY8-2X8">
1662− <entry>V4L2_MBUS_FMT_UYVY8_2X8</entry>
1677+ <row id="MEDIA-BUS-FMT-UYVY8-2X8">
1678+ <entry>MEDIA_BUS_FMT_UYVY8_2X8</entry>
16631679 <entry>0x2006</entry>
16641680 <entry></entry>
16651681 &dash-ent-24;
@@ -1714,8 +1730,8 @@ · 48 unmodified lines
17141730 <entry>y<subscript>1</subscript></entry>
17151731 <entry>y<subscript>0</subscript></entry>
17161732 </row>
1717− <row id="V4L2-MBUS-FMT-VYUY8-2X8">
1718− <entry>V4L2_MBUS_FMT_VYUY8_2X8</entry>
1733+ <row id="MEDIA-BUS-FMT-VYUY8-2X8">
1734+ <entry>MEDIA_BUS_FMT_VYUY8_2X8</entry>
17191735 <entry>0x2007</entry>
17201736 <entry></entry>
17211737 &dash-ent-24;
@@ -1770,8 +1786,8 @@ · 48 unmodified lines
17701786 <entry>y<subscript>1</subscript></entry>
17711787 <entry>y<subscript>0</subscript></entry>
17721788 </row>
1773− <row id="V4L2-MBUS-FMT-YUYV8-2X8">
1774− <entry>V4L2_MBUS_FMT_YUYV8_2X8</entry>
1789+ <row id="MEDIA-BUS-FMT-YUYV8-2X8">
1790+ <entry>MEDIA_BUS_FMT_YUYV8_2X8</entry>
17751791 <entry>0x2008</entry>
17761792 <entry></entry>
17771793 &dash-ent-24;
@@ -1826,8 +1842,8 @@ · 48 unmodified lines
18261842 <entry>v<subscript>1</subscript></entry>
18271843 <entry>v<subscript>0</subscript></entry>
18281844 </row>
1829− <row id="V4L2-MBUS-FMT-YVYU8-2X8">
1830− <entry>V4L2_MBUS_FMT_YVYU8_2X8</entry>
1845+ <row id="MEDIA-BUS-FMT-YVYU8-2X8">
1846+ <entry>MEDIA_BUS_FMT_YVYU8_2X8</entry>
18311847 <entry>0x2009</entry>
18321848 <entry></entry>
18331849 &dash-ent-24;
@@ -1882,8 +1898,8 @@ · 48 unmodified lines
18821898 <entry>u<subscript>1</subscript></entry>
18831899 <entry>u<subscript>0</subscript></entry>
18841900 </row>
1885− <row id="V4L2-MBUS-FMT-Y10-1X10">
1886− <entry>V4L2_MBUS_FMT_Y10_1X10</entry>
1901+ <row id="MEDIA-BUS-FMT-Y10-1X10">
1902+ <entry>MEDIA_BUS_FMT_Y10_1X10</entry>
18871903 <entry>0x200a</entry>
18881904 <entry></entry>
18891905 &dash-ent-22;
@@ -1898,8 +1914,8 @@ · 8 unmodified lines
18981914 <entry>y<subscript>1</subscript></entry>
18991915 <entry>y<subscript>0</subscript></entry>
19001916 </row>
1901− <row id="V4L2-MBUS-FMT-UYVY10-2X10">
1902− <entry>V4L2_MBUS_FMT_UYVY10_2X10</entry>
1917+ <row id="MEDIA-BUS-FMT-UYVY10-2X10">
1918+ <entry>MEDIA_BUS_FMT_UYVY10_2X10</entry>
19031919 <entry>0x2018</entry>
19041920 <entry></entry>
19051921 &dash-ent-22;
@@ -1962,8 +1978,8 @@ · 56 unmodified lines
19621978 <entry>y<subscript>1</subscript></entry>
19631979 <entry>y<subscript>0</subscript></entry>
19641980 </row>
1965− <row id="V4L2-MBUS-FMT-VYUY10-2X10">
1966− <entry>V4L2_MBUS_FMT_VYUY10_2X10</entry>
1981+ <row id="MEDIA-BUS-FMT-VYUY10-2X10">
1982+ <entry>MEDIA_BUS_FMT_VYUY10_2X10</entry>
19671983 <entry>0x2019</entry>
19681984 <entry></entry>
19691985 &dash-ent-22;
@@ -2026,8 +2042,8 @@ · 56 unmodified lines
20262042 <entry>y<subscript>1</subscript></entry>
20272043 <entry>y<subscript>0</subscript></entry>
20282044 </row>
2029− <row id="V4L2-MBUS-FMT-YUYV10-2X10">
2030− <entry>V4L2_MBUS_FMT_YUYV10_2X10</entry>
2045+ <row id="MEDIA-BUS-FMT-YUYV10-2X10">
2046+ <entry>MEDIA_BUS_FMT_YUYV10_2X10</entry>
20312047 <entry>0x200b</entry>
20322048 <entry></entry>
20332049 &dash-ent-22;
@@ -2090,8 +2106,8 @@ · 56 unmodified lines
20902106 <entry>v<subscript>1</subscript></entry>
20912107 <entry>v<subscript>0</subscript></entry>
20922108 </row>
2093− <row id="V4L2-MBUS-FMT-YVYU10-2X10">
2094− <entry>V4L2_MBUS_FMT_YVYU10_2X10</entry>
2109+ <row id="MEDIA-BUS-FMT-YVYU10-2X10">
2110+ <entry>MEDIA_BUS_FMT_YVYU10_2X10</entry>
20952111 <entry>0x200c</entry>
20962112 <entry></entry>
20972113 &dash-ent-22;
@@ -2154,8 +2170,8 @@ · 56 unmodified lines
21542170 <entry>u<subscript>1</subscript></entry>
21552171 <entry>u<subscript>0</subscript></entry>
21562172 </row>
2157− <row id="V4L2-MBUS-FMT-Y12-1X12">
2158− <entry>V4L2_MBUS_FMT_Y12_1X12</entry>
2173+ <row id="MEDIA-BUS-FMT-Y12-1X12">
2174+ <entry>MEDIA_BUS_FMT_Y12_1X12</entry>
21592175 <entry>0x2013</entry>
21602176 <entry></entry>
21612177 &dash-ent-20;
@@ -2172,8 +2188,8 @@ · 10 unmodified lines
21722188 <entry>y<subscript>1</subscript></entry>
21732189 <entry>y<subscript>0</subscript></entry>
21742190 </row>
2175− <row id="V4L2-MBUS-FMT-UYVY8-1X16">
2176− <entry>V4L2_MBUS_FMT_UYVY8_1X16</entry>
2191+ <row id="MEDIA-BUS-FMT-UYVY8-1X16">
2192+ <entry>MEDIA_BUS_FMT_UYVY8_1X16</entry>
21772193 <entry>0x200f</entry>
21782194 <entry></entry>
21792195 &dash-ent-16;
@@ -2216,8 +2232,8 @@ · 36 unmodified lines
22162232 <entry>y<subscript>1</subscript></entry>
22172233 <entry>y<subscript>0</subscript></entry>
22182234 </row>
2219− <row id="V4L2-MBUS-FMT-VYUY8-1X16">
2220− <entry>V4L2_MBUS_FMT_VYUY8_1X16</entry>
2235+ <row id="MEDIA-BUS-FMT-VYUY8-1X16">
2236+ <entry>MEDIA_BUS_FMT_VYUY8_1X16</entry>
22212237 <entry>0x2010</entry>
22222238 <entry></entry>
22232239 &dash-ent-16;
@@ -2260,8 +2276,8 @@ · 36 unmodified lines
22602276 <entry>y<subscript>1</subscript></entry>
22612277 <entry>y<subscript>0</subscript></entry>
22622278 </row>
2263− <row id="V4L2-MBUS-FMT-YUYV8-1X16">
2264− <entry>V4L2_MBUS_FMT_YUYV8_1X16</entry>
2279+ <row id="MEDIA-BUS-FMT-YUYV8-1X16">
2280+ <entry>MEDIA_BUS_FMT_YUYV8_1X16</entry>
22652281 <entry>0x2011</entry>
22662282 <entry></entry>
22672283 &dash-ent-16;
@@ -2304,8 +2320,8 @@ · 36 unmodified lines
23042320 <entry>v<subscript>1</subscript></entry>
23052321 <entry>v<subscript>0</subscript></entry>
23062322 </row>
2307− <row id="V4L2-MBUS-FMT-YVYU8-1X16">
2308− <entry>V4L2_MBUS_FMT_YVYU8_1X16</entry>
2323+ <row id="MEDIA-BUS-FMT-YVYU8-1X16">
2324+ <entry>MEDIA_BUS_FMT_YVYU8_1X16</entry>
23092325 <entry>0x2012</entry>
23102326 <entry></entry>
23112327 &dash-ent-16;
@@ -2348,8 +2364,8 @@ · 36 unmodified lines
23482364 <entry>u<subscript>1</subscript></entry>
23492365 <entry>u<subscript>0</subscript></entry>
23502366 </row>
2351− <row id="V4L2-MBUS-FMT-YDYUYDYV8-1X16">
2352− <entry>V4L2_MBUS_FMT_YDYUYDYV8_1X16</entry>
2367+ <row id="MEDIA-BUS-FMT-YDYUYDYV8-1X16">
2368+ <entry>MEDIA_BUS_FMT_YDYUYDYV8_1X16</entry>
23532369 <entry>0x2014</entry>
23542370 <entry></entry>
23552371 &dash-ent-16;
@@ -2436,8 +2452,8 @@ · 80 unmodified lines
24362452 <entry>v<subscript>1</subscript></entry>
24372453 <entry>v<subscript>0</subscript></entry>
24382454 </row>
2439− <row id="V4L2-MBUS-FMT-UYVY10-1X20">
2440− <entry>V4L2_MBUS_FMT_UYVY10_1X20</entry>
2455+ <row id="MEDIA-BUS-FMT-UYVY10-1X20">
2456+ <entry>MEDIA_BUS_FMT_UYVY10_1X20</entry>
24412457 <entry>0x201a</entry>
24422458 <entry></entry>
24432459 &dash-ent-12;
@@ -2488,8 +2504,8 @@ · 44 unmodified lines
24882504 <entry>y<subscript>1</subscript></entry>
24892505 <entry>y<subscript>0</subscript></entry>
24902506 </row>
2491− <row id="V4L2-MBUS-FMT-VYUY10-1X20">
2492− <entry>V4L2_MBUS_FMT_VYUY10_1X20</entry>
2507+ <row id="MEDIA-BUS-FMT-VYUY10-1X20">
2508+ <entry>MEDIA_BUS_FMT_VYUY10_1X20</entry>
24932509 <entry>0x201b</entry>
24942510 <entry></entry>
24952511 &dash-ent-12;
@@ -2540,8 +2556,8 @@ · 44 unmodified lines
25402556 <entry>y<subscript>1</subscript></entry>
25412557 <entry>y<subscript>0</subscript></entry>
25422558 </row>
2543− <row id="V4L2-MBUS-FMT-YUYV10-1X20">
2544− <entry>V4L2_MBUS_FMT_YUYV10_1X20</entry>
2559+ <row id="MEDIA-BUS-FMT-YUYV10-1X20">
2560+ <entry>MEDIA_BUS_FMT_YUYV10_1X20</entry>
25452561 <entry>0x200d</entry>
25462562 <entry></entry>
25472563 &dash-ent-12;
@@ -2592,8 +2608,8 @@ · 44 unmodified lines
25922608 <entry>v<subscript>1</subscript></entry>
25932609 <entry>v<subscript>0</subscript></entry>
25942610 </row>
2595− <row id="V4L2-MBUS-FMT-YVYU10-1X20">
2596− <entry>V4L2_MBUS_FMT_YVYU10_1X20</entry>
2611+ <row id="MEDIA-BUS-FMT-YVYU10-1X20">
2612+ <entry>MEDIA_BUS_FMT_YVYU10_1X20</entry>
25972613 <entry>0x200e</entry>
25982614 <entry></entry>
25992615 &dash-ent-12;
@@ -2644,8 +2660,8 @@ · 44 unmodified lines
26442660 <entry>u<subscript>1</subscript></entry>
26452661 <entry>u<subscript>0</subscript></entry>
26462662 </row>
2647− <row id="V4L2-MBUS-FMT-YUV10-1X30">
2648− <entry>V4L2_MBUS_FMT_YUV10_1X30</entry>
2663+ <row id="MEDIA-BUS-FMT-YUV10-1X30">
2664+ <entry>MEDIA_BUS_FMT_YUV10_1X30</entry>
26492665 <entry>0x2016</entry>
26502666 <entry></entry>
26512667 <entry>-</entry>
@@ -2681,8 +2697,8 @@ · 29 unmodified lines
26812697 <entry>v<subscript>1</subscript></entry>
26822698 <entry>v<subscript>0</subscript></entry>
26832699 </row>
2684− <row id="V4L2-MBUS-FMT-AYUV8-1X32">
2685− <entry>V4L2_MBUS_FMT_AYUV8_1X32</entry>
2700+ <row id="MEDIA-BUS-FMT-AYUV8-1X32">
2701+ <entry>MEDIA_BUS_FMT_AYUV8_1X32</entry>
26862702 <entry>0x2017</entry>
26872703 <entry></entry>
26882704 <entry>a<subscript>7</subscript></entry>
@@ -2718,8 +2734,8 @@ · 29 unmodified lines
27182734 <entry>v<subscript>1</subscript></entry>
27192735 <entry>v<subscript>0</subscript></entry>
27202736 </row>
2721− <row id="V4L2-MBUS-FMT-UYVY12-2X12">
2722− <entry>V4L2_MBUS_FMT_UYVY12_2X12</entry>
2737+ <row id="MEDIA-BUS-FMT-UYVY12-2X12">
2738+ <entry>MEDIA_BUS_FMT_UYVY12_2X12</entry>
27232739 <entry>0x201c</entry>
27242740 <entry></entry>
27252741 &dash-ent-20;
@@ -2790,8 +2806,8 @@ · 64 unmodified lines
27902806 <entry>y<subscript>1</subscript></entry>
27912807 <entry>y<subscript>0</subscript></entry>
27922808 </row>
2793− <row id="V4L2-MBUS-FMT-VYUY12-2X12">
2794− <entry>V4L2_MBUS_FMT_VYUY12_2X12</entry>
2809+ <row id="MEDIA-BUS-FMT-VYUY12-2X12">
2810+ <entry>MEDIA_BUS_FMT_VYUY12_2X12</entry>
27952811 <entry>0x201d</entry>
27962812 <entry></entry>
27972813 &dash-ent-20;
@@ -2862,8 +2878,8 @@ · 64 unmodified lines
28622878 <entry>y<subscript>1</subscript></entry>
28632879 <entry>y<subscript>0</subscript></entry>
28642880 </row>
2865− <row id="V4L2-MBUS-FMT-YUYV12-2X12">
2866− <entry>V4L2_MBUS_FMT_YUYV12_2X12</entry>
2881+ <row id="MEDIA-BUS-FMT-YUYV12-2X12">
2882+ <entry>MEDIA_BUS_FMT_YUYV12_2X12</entry>
28672883 <entry>0x201e</entry>
28682884 <entry></entry>
28692885 &dash-ent-20;
@@ -2934,8 +2950,8 @@ · 64 unmodified lines
29342950 <entry>v<subscript>1</subscript></entry>
29352951 <entry>v<subscript>0</subscript></entry>
29362952 </row>
2937− <row id="V4L2-MBUS-FMT-YVYU12-2X12">
2938− <entry>V4L2_MBUS_FMT_YVYU12_2X12</entry>
2953+ <row id="MEDIA-BUS-FMT-YVYU12-2X12">
2954+ <entry>MEDIA_BUS_FMT_YVYU12_2X12</entry>
29392955 <entry>0x201f</entry>
29402956 <entry></entry>
29412957 &dash-ent-20;
@@ -3006,8 +3022,8 @@ · 64 unmodified lines
30063022 <entry>u<subscript>1</subscript></entry>
30073023 <entry>u<subscript>0</subscript></entry>
30083024 </row>
3009− <row id="V4L2-MBUS-FMT-UYVY12-1X24">
3010− <entry>V4L2_MBUS_FMT_UYVY12_1X24</entry>
3025+ <row id="MEDIA-BUS-FMT-UYVY12-1X24">
3026+ <entry>MEDIA_BUS_FMT_UYVY12_1X24</entry>
30113027 <entry>0x2020</entry>
30123028 <entry></entry>
30133029 &dash-ent-8;
@@ -3066,8 +3082,8 @@ · 52 unmodified lines
30663082 <entry>y<subscript>1</subscript></entry>
30673083 <entry>y<subscript>0</subscript></entry>
30683084 </row>
3069− <row id="V4L2-MBUS-FMT-VYUY12-1X24">
3070− <entry>V4L2_MBUS_FMT_VYUY12_1X24</entry>
3085+ <row id="MEDIA-BUS-FMT-VYUY12-1X24">
3086+ <entry>MEDIA_BUS_FMT_VYUY12_1X24</entry>
30713087 <entry>0x2021</entry>
30723088 <entry></entry>
30733089 &dash-ent-8;
@@ -3126,8 +3142,8 @@ · 52 unmodified lines
31263142 <entry>y<subscript>1</subscript></entry>
31273143 <entry>y<subscript>0</subscript></entry>
31283144 </row>
3129− <row id="V4L2-MBUS-FMT-YUYV12-1X24">
3130− <entry>V4L2_MBUS_FMT_YUYV12_1X24</entry>
3145+ <row id="MEDIA-BUS-FMT-YUYV12-1X24">
3146+ <entry>MEDIA_BUS_FMT_YUYV12_1X24</entry>
31313147 <entry>0x2022</entry>
31323148 <entry></entry>
31333149 &dash-ent-8;
@@ -3186,8 +3202,8 @@ · 52 unmodified lines
31863202 <entry>v<subscript>1</subscript></entry>
31873203 <entry>v<subscript>0</subscript></entry>
31883204 </row>
3189− <row id="V4L2-MBUS-FMT-YVYU12-1X24">
3190− <entry>V4L2_MBUS_FMT_YVYU12_1X24</entry>
3205+ <row id="MEDIA-BUS-FMT-YVYU12-1X24">
3206+ <entry>MEDIA_BUS_FMT_YVYU12_1X24</entry>
31913207 <entry>0x2023</entry>
31923208 <entry></entry>
31933209 &dash-ent-8;
@@ -3366,8 +3382,8 @@ · 172 unmodified lines
33663382 </row>
33673383 </thead>
33683384 <tbody valign="top">
3369− <row id="V4L2-MBUS-FMT-AHSV8888-1X32">
3370− <entry>V4L2_MBUS_FMT_AHSV8888_1X32</entry>
3385+ <row id="MEDIA-BUS-FMT-AHSV8888-1X32">
3386+ <entry>MEDIA_BUS_FMT_AHSV8888_1X32</entry>
33713387 <entry>0x6001</entry>
33723388 <entry></entry>
33733389 <entry>a<subscript>7</subscript></entry>
@@ -3422,7 +3438,7 @@ · 48 unmodified lines
34223438 </para>
34233439
34243440 <para>For instance, for a JPEG baseline process and an 8-bit bus width
3425− the format will be named <constant>V4L2_MBUS_FMT_JPEG_1X8</constant>.
3441+ the format will be named <constant>MEDIA_BUS_FMT_JPEG_1X8</constant>.
34263442 </para>
34273443
34283444 <para>The following table lists existing JPEG compressed formats.</para>
@@ -3441,8 +3457,8 @@ · 12 unmodified lines
34413457 </row>
34423458 </thead>
34433459 <tbody valign="top">
3444− <row id="V4L2-MBUS-FMT-JPEG-1X8">
3445− <entry>V4L2_MBUS_FMT_JPEG_1X8</entry>
3460+ <row id="MEDIA-BUS-FMT-JPEG-1X8">
3461+ <entry>MEDIA_BUS_FMT_JPEG_1X8</entry>
34463462 <entry>0x4001</entry>
34473463 <entry>Besides of its usage for the parallel bus this format is
34483464 recommended for transmission of JPEG data over MIPI CSI bus
@@ -3484,8 +3500,8 @@ interface and may change in the future.</para> · 35 unmodified lines
34843500 </row>
34853501 </thead>
34863502 <tbody valign="top">
3487− <row id="V4L2-MBUS-FMT-S5C-UYVY-JPEG-1X8">
3488− <entry>V4L2_MBUS_FMT_S5C_UYVY_JPEG_1X8</entry>
3503+ <row id="MEDIA-BUS-FMT-S5C-UYVY-JPEG-1X8">
3504+ <entry>MEDIA_BUS_FMT_S5C_UYVY_JPEG_1X8</entry>
34893505 <entry>0x5001</entry>
34903506 <entry>
34913507 Interleaved raw UYVY and JPEG image format with embedded
Documentation/DocBook/media/v4l/v4l2.xml+10−1
@@ -151,6 +151,15 @@ structs, ioctls) must be noted in more detail in the history chapter · 150 unmodified lines
151151 (compat.xml), along with the possible impact on existing drivers and
152152 applications. -->
153153
154+ <revision>
155+ <revnumber>3.19</revnumber>
156+ <date>2014-12-05</date>
157+ <authorinitials>hv</authorinitials>
158+ <revremark>Rewrote Colorspace chapter, added new &v4l2-ycbcr-encoding; and &v4l2-quantization; fields
159+to &v4l2-pix-format;, &v4l2-pix-format-mplane; and &v4l2-mbus-framefmt;.
160+ </revremark>
161+ </revision>
162+
154163 <revision>
155164 <revnumber>3.17</revnumber>
156165 <date>2014-08-04</date>
@@ -539,7 +548,7 @@ and discussions on the V4L mailing list.</revremark> · 382 unmodified lines
539548 </partinfo>
540549
541550 <title>Video for Linux Two API Specification</title>
542− <subtitle>Revision 3.17</subtitle>
551+ <subtitle>Revision 3.19</subtitle>
543552
544553 <chapter id="common">
545554 &sub-common;
Documentation/DocBook/media/v4l/vidioc-dqevent.xml+4−3
@@ -76,21 +76,22 @@ · 75 unmodified lines
7676 <entry></entry>
7777 <entry>&v4l2-event-vsync;</entry>
7878 <entry><structfield>vsync</structfield></entry>
79− <entry>Event data for event V4L2_EVENT_VSYNC.
79+ <entry>Event data for event <constant>V4L2_EVENT_VSYNC</constant>.
8080 </entry>
8181 </row>
8282 <row>
8383 <entry></entry>
8484 <entry>&v4l2-event-ctrl;</entry>
8585 <entry><structfield>ctrl</structfield></entry>
86− <entry>Event data for event V4L2_EVENT_CTRL.
86+ <entry>Event data for event <constant>V4L2_EVENT_CTRL</constant>.
8787 </entry>
8888 </row>
8989 <row>
9090 <entry></entry>
9191 <entry>&v4l2-event-frame-sync;</entry>
9292 <entry><structfield>frame_sync</structfield></entry>
93− <entry>Event data for event V4L2_EVENT_FRAME_SYNC.</entry>
93+ <entry>Event data for event
94+ <constant>V4L2_EVENT_FRAME_SYNC</constant>.</entry>
9495 </row>
9596 <row>
9697 <entry></entry>
Documentation/DocBook/media/v4l/vidioc-enuminput.xml+8−0
@@ -287,6 +287,14 @@ input/output interface to linux-media@vger.kernel.org on 19 Oct 2009. · 286 unmodified lines
287287 <entry>0x00000004</entry>
288288 <entry>This input supports setting the TV standard by using VIDIOC_S_STD.</entry>
289289 </row>
290+ <row>
291+ <entry><constant>V4L2_IN_CAP_NATIVE_SIZE</constant></entry>
292+ <entry>0x00000008</entry>
293+ <entry>This input supports setting the native size using
294+ the <constant>V4L2_SEL_TGT_NATIVE_SIZE</constant>
295+ selection target, see <xref
296+ linkend="v4l2-selections-common"/>.</entry>
297+ </row>
290298 </tbody>
291299 </tgroup>
292300 </table>
Documentation/DocBook/media/v4l/vidioc-enumoutput.xml+8−0
@@ -172,6 +172,14 @@ input/output interface to linux-media@vger.kernel.org on 19 Oct 2009. · 171 unmodified lines
172172 <entry>0x00000004</entry>
173173 <entry>This output supports setting the TV standard by using VIDIOC_S_STD.</entry>
174174 </row>
175+ <row>
176+ <entry><constant>V4L2_OUT_CAP_NATIVE_SIZE</constant></entry>
177+ <entry>0x00000008</entry>
178+ <entry>This output supports setting the native size using
179+ the <constant>V4L2_SEL_TGT_NATIVE_SIZE</constant>
180+ selection target, see <xref
181+ linkend="v4l2-selections-common"/>.</entry>
182+ </row>
175183 </tbody>
176184 </tgroup>
177185 </table>
Documentation/DocBook/media/v4l/vidioc-g-edid.xml+7−7
@@ -24,7 +24,7 @@ · 23 unmodified lines
2424 <funcdef>int <function>ioctl</function></funcdef>
2525 <paramdef>int <parameter>fd</parameter></paramdef>
2626 <paramdef>int <parameter>request</parameter></paramdef>
27− <paramdef>const struct v4l2_edid *<parameter>argp</parameter></paramdef>
27+ <paramdef>struct v4l2_edid *<parameter>argp</parameter></paramdef>
2828 </funcprototype>
2929 </funcsynopsis>
3030 </refsynopsisdiv>
@@ -124,18 +124,18 @@ · 93 unmodified lines
124124 maximum number of blocks as defined by the standard). When you set the EDID and
125125 <structfield>blocks</structfield> is 0, then the EDID is disabled or erased.</entry>
126126 </row>
127− <row>
128− <entry>__u8&nbsp;*</entry>
129− <entry><structfield>edid</structfield></entry>
130− <entry>Pointer to memory that contains the EDID. The minimum size is
131− <structfield>blocks</structfield>&nbsp;*&nbsp;128.</entry>
132− </row>
133127 <row>
134128 <entry>__u32</entry>
135129 <entry><structfield>reserved</structfield>[5]</entry>
136130 <entry>Reserved for future extensions. Applications and drivers must
137131 set the array to zero.</entry>
138132 </row>
133+ <row>
134+ <entry>__u8&nbsp;*</entry>
135+ <entry><structfield>edid</structfield></entry>
136+ <entry>Pointer to memory that contains the EDID. The minimum size is
137+ <structfield>blocks</structfield>&nbsp;*&nbsp;128.</entry>
138+ </row>
139139 </tbody>
140140 </tgroup>
141141 </table>
Documentation/DocBook/media/v4l/vidioc-subscribe-event.xml+1−1
@@ -176,7 +176,7 @@ · 175 unmodified lines
176176 </row>
177177 <row>
178178 <entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
179− <entry>5</entry>
179+ <entry>6</entry>
180180 <entry>
181181 <para>Triggered whenever the motion detection state for one or more of the regions
182182 changes. This event has a &v4l2-event-motion-det; associated with it.</para>
Documentation/DocBook/uio-howto.tmpl+1−1
@@ -540,7 +540,7 @@ appears in sysfs. · 539 unmodified lines
540540 </para></listitem>
541541
542542 <listitem><para>
543−<varname>unsigned long size</varname>: Fill in the size of the
543+<varname>resource_size_t size</varname>: Fill in the size of the
544544 memory block that <varname>addr</varname> points to. If <varname>size</varname>
545545 is zero, the mapping is considered unused. Note that you
546546 <emphasis>must</emphasis> initialize <varname>size</varname> with zero for
Documentation/DocBook/usb.tmpl+1−1
@@ -593,7 +593,7 @@ for (;;) { · 592 unmodified lines
593593 Each device has one control endpoint (endpoint zero)
594594 which supports a limited RPC style RPC access.
595595 Devices are configured
596− by khubd (in the kernel) setting a device-wide
596+ by hub_wq (in the kernel) setting a device-wide
597597 <emphasis>configuration</emphasis> that affects things
598598 like power consumption and basic functionality.
599599 The endpoints are part of USB <emphasis>interfaces</emphasis>,
Documentation/DocBook/writing-an-alsa-driver.tmpl+46−5
@@ -2742,7 +2742,9 @@ struct _snd_pcm_runtime { · 2741 unmodified lines
27422742
27432743 <para>
27442744 Another note is that this callback is non-atomic
2745− (schedulable). This is important, because the
2745+ (schedulable) as default, i.e. when no
2746+ <structfield>nonatomic</structfield> flag set.
2747+ This is important, because the
27462748 <structfield>trigger</structfield> callback
27472749 is atomic (non-schedulable). That is, mutexes or any
27482750 schedule-related functions are not available in
@@ -2900,8 +2902,9 @@ struct _snd_pcm_runtime { · 151 unmodified lines
29002902 </para>
29012903
29022904 <para>
2903− As mentioned, this callback is atomic. You cannot call
2904− functions which may sleep.
2905+ As mentioned, this callback is atomic as default unless
2906+ <structfield>nonatomic</structfield> flag set, and
2907+ you cannot call functions which may sleep.
29052908 The trigger callback should be as minimal as possible,
29062909 just really triggering the DMA. The other stuff should be
29072910 initialized hw_params and prepare callbacks properly
@@ -2936,7 +2939,7 @@ struct _snd_pcm_runtime { · 28 unmodified lines
29362939 </para>
29372940
29382941 <para>
2939− This callback is also atomic.
2942+ This callback is also atomic as default.
29402943 </para>
29412944 </section>
29422945
@@ -2972,7 +2975,7 @@ struct _snd_pcm_runtime { · 29 unmodified lines
29722975 is useful only for such a purpose.
29732976 </para>
29742977 <para>
2975− This callback is atomic.
2978+ This callback is atomic as default.
29762979 </para>
29772980 </section>
29782981
@@ -3175,6 +3178,21 @@ struct _snd_pcm_runtime { · 196 unmodified lines
31753178 called with local interrupts disabled.
31763179 </para>
31773180
3181+ <para>
3182+ The recent changes in PCM core code, however, allow all PCM
3183+ operations to be non-atomic. This assumes that the all caller
3184+ sides are in non-atomic contexts. For example, the function
3185+ <function>snd_pcm_period_elapsed()</function> is called
3186+ typically from the interrupt handler. But, if you set up the
3187+ driver to use a threaded interrupt handler, this call can be in
3188+ non-atomic context, too. In such a case, you can set
3189+ <structfield>nonatomic</structfield> filed of
3190+ <structname>snd_pcm</structname> object after creating it.
3191+ When this flag is set, mutex and rwsem are used internally in
3192+ the PCM core instead of spin and rwlocks, so that you can call
3193+ all PCM functions safely in a non-atomic context.
3194+ </para>
3195+
31783196 </section>
31793197 <section id="pcm-interface-constraints">
31803198 <title>Constraints</title>
@@ -3639,6 +3657,29 @@ struct _snd_pcm_runtime { · 458 unmodified lines
36393657 </informalexample>
36403658 </para>
36413659
3660+ <para>
3661+ The above callback can be simplified with a helper function,
3662+ <function>snd_ctl_enum_info</function>. The final code
3663+ looks like below.
3664+ (You can pass ARRAY_SIZE(texts) instead of 4 in the third
3665+ argument; it's a matter of taste.)
3666+
3667+ <informalexample>
3668+ <programlisting>
3669+<![CDATA[
3670+ static int snd_myctl_enum_info(struct snd_kcontrol *kcontrol,
3671+ struct snd_ctl_elem_info *uinfo)
3672+ {
3673+ static char *texts[4] = {
3674+ "First", "Second", "Third", "Fourth"
3675+ };
3676+ return snd_ctl_enum_info(uinfo, 1, 4, texts);
3677+ }
3678+]]>
3679+ </programlisting>
3680+ </informalexample>
3681+ </para>
3682+
36423683 <para>
36433684 Some common info callbacks are available for your convenience:
36443685 <function>snd_ctl_boolean_mono_info()</function> and
Documentation/HOWTO+0−1
@@ -324,7 +324,6 @@ tree, they need to be integration-tested. For this purpose, a special · 323 unmodified lines
324324 testing repository exists into which virtually all subsystem trees are
325325 pulled on an almost daily basis:
326326 http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git
327− http://linux.f-seidel.de/linux-next/pmwiki/
328327
329328 This way, the -next kernel gives a summary outlook onto what will be
330329 expected to go into the mainline kernel at the next merge period.
Documentation/IPMI.txt+71−3
@@ -42,7 +42,13 @@ The driver interface depends on your hardware. If your system · 41 unmodified lines
4242 properly provides the SMBIOS info for IPMI, the driver will detect it
4343 and just work. If you have a board with a standard interface (These
4444 will generally be either "KCS", "SMIC", or "BT", consult your hardware
45−manual), choose the 'IPMI SI handler' option.
45+manual), choose the 'IPMI SI handler' option. A driver also exists
46+for direct I2C access to the IPMI management controller. Some boards
47+support this, but it is unknown if it will work on every board. For
48+this, choose 'IPMI SMBus handler', but be ready to try to do some
49+figuring to see if it will work on your system if the SMBIOS/APCI
50+information is wrong or not present. It is fairly safe to have both
51+these enabled and let the drivers auto-detect what is present.
4652
4753 You should generally enable ACPI on your system, as systems with IPMI
4854 can have ACPI tables describing them.
@@ -52,7 +58,8 @@ their job correctly, the IPMI controller should be automatically · 3 unmodified lines
5258 detected (via ACPI or SMBIOS tables) and should just work. Sadly,
5359 many boards do not have this information. The driver attempts
5460 standard defaults, but they may not work. If you fall into this
55−situation, you need to read the section below named 'The SI Driver'.
61+situation, you need to read the section below named 'The SI Driver' or
62+"The SMBus Driver" on how to hand-configure your system.
5663
5764 IPMI defines a standard watchdog timer. You can enable this with the
5865 'IPMI Watchdog Timer' config option. If you compile the driver into
@@ -97,7 +104,12 @@ driver, each open file for this device ties in to the message handler · 38 unmodified lines
97104 as an IPMI user.
98105
99106 ipmi_si - A driver for various system interfaces. This supports KCS,
100−SMIC, and BT interfaces.
107+SMIC, and BT interfaces. Unless you have an SMBus interface or your
108+own custom interface, you probably need to use this.
109+
110+ipmi_ssif - A driver for accessing BMCs on the SMBus. It uses the
111+I2C kernel driver's SMBus interfaces to send and receive IPMI messages
112+over the SMBus.
101113
102114 ipmi_watchdog - IPMI requires systems to have a very capable watchdog
103115 timer. This driver implements the standard Linux watchdog timer
@@ -476,6 +488,62 @@ for specifying an interface. Note that when removing an interface, · 372 unmodified lines
476488 only the first three parameters (si type, address type, and address)
477489 are used for the comparison. Any options are ignored for removing.
478490
491+The SMBus Driver (SSIF)
492+-----------------------
493+
494+The SMBus driver allows up to 4 SMBus devices to be configured in the
495+system. By default, the driver will only register with something it
496+finds in DMI or ACPI tables. You can change this
497+at module load time (for a module) with:
498+
499+ modprobe ipmi_ssif.o
500+ addr=<i2caddr1>[,<i2caddr2>[,...]]
501+ adapter=<adapter1>[,<adapter2>[...]]
502+ dbg=<flags1>,<flags2>...
503+ slave_addrs=<addr1>,<addr2>,...
504+ [dbg_probe=1]
505+
506+The addresses are normal I2C addresses. The adapter is the string
507+name of the adapter, as shown in /sys/class/i2c-adapter/i2c-<n>/name.
508+It is *NOT* i2c-<n> itself.
509+
510+The debug flags are bit flags for each BMC found, they are:
511+IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8
512+
513+Setting dbg_probe to 1 will enable debugging of the probing and
514+detection process for BMCs on the SMBusses.
515+
516+The slave_addrs specifies the IPMI address of the local BMC. This is
517+usually 0x20 and the driver defaults to that, but in case it's not, it
518+can be specified when the driver starts up.
519+
520+Discovering the IPMI compliant BMC on the SMBus can cause devices on
521+the I2C bus to fail. The SMBus driver writes a "Get Device ID" IPMI
522+message as a block write to the I2C bus and waits for a response.
523+This action can be detrimental to some I2C devices. It is highly
524+recommended that the known I2C address be given to the SMBus driver in
525+the smb_addr parameter unless you have DMI or ACPI data to tell the
526+driver what to use.
527+
528+When compiled into the kernel, the addresses can be specified on the
529+kernel command line as:
530+
531+ ipmb_ssif.addr=<i2caddr1>[,<i2caddr2>[...]]
532+ ipmi_ssif.adapter=<adapter1>[,<adapter2>[...]]
533+ ipmi_ssif.dbg=<flags1>[,<flags2>[...]]
534+ ipmi_ssif.dbg_probe=1
535+ ipmi_ssif.slave_addrs=<addr1>[,<addr2>[...]]
536+
537+These are the same options as on the module command line.
538+
539+The I2C driver does not support non-blocking access or polling, so
540+this driver cannod to IPMI panic events, extend the watchdog at panic
541+time, or other panic-related IPMI functions without special kernel
542+patches and driver modifications. You can get those at the openipmi
543+web page.
544+
545+The driver supports a hot add and remove of interfaces through the I2C
546+sysfs interface.
479547
480548 Other Pieces
481549 ------------
Documentation/IRQ-domain.txt+71−0
@@ -151,3 +151,74 @@ used and no descriptor gets allocated it is very important to make sure · 150 unmodified lines
151151 that the driver using the simple domain call irq_create_mapping()
152152 before any irq_find_mapping() since the latter will actually work
153153 for the static IRQ assignment case.
154+
155+==== Hierarchy IRQ domain ====
156+On some architectures, there may be multiple interrupt controllers
157+involved in delivering an interrupt from the device to the target CPU.
158+Let's look at a typical interrupt delivering path on x86 platforms:
159+
160+Device --> IOAPIC -> Interrupt remapping Controller -> Local APIC -> CPU
161+
162+There are three interrupt controllers involved:
163+1) IOAPIC controller
164+2) Interrupt remapping controller
165+3) Local APIC controller
166+
167+To support such a hardware topology and make software architecture match
168+hardware architecture, an irq_domain data structure is built for each
169+interrupt controller and those irq_domains are organized into hierarchy.
170+When building irq_domain hierarchy, the irq_domain near to the device is
171+child and the irq_domain near to CPU is parent. So a hierarchy structure
172+as below will be built for the example above.
173+ CPU Vector irq_domain (root irq_domain to manage CPU vectors)
174+ ^
175+ |
176+ Interrupt Remapping irq_domain (manage irq_remapping entries)
177+ ^
178+ |
179+ IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
180+
181+There are four major interfaces to use hierarchy irq_domain:
182+1) irq_domain_alloc_irqs(): allocate IRQ descriptors and interrupt
183+ controller related resources to deliver these interrupts.
184+2) irq_domain_free_irqs(): free IRQ descriptors and interrupt controller
185+ related resources associated with these interrupts.
186+3) irq_domain_activate_irq(): activate interrupt controller hardware to
187+ deliver the interrupt.
188+3) irq_domain_deactivate_irq(): deactivate interrupt controller hardware
189+ to stop delivering the interrupt.
190+
191+Following changes are needed to support hierarchy irq_domain.
192+1) a new field 'parent' is added to struct irq_domain; it's used to
193+ maintain irq_domain hierarchy information.
194+2) a new field 'parent_data' is added to struct irq_data; it's used to
195+ build hierarchy irq_data to match hierarchy irq_domains. The irq_data
196+ is used to store irq_domain pointer and hardware irq number.
197+3) new callbacks are added to struct irq_domain_ops to support hierarchy
198+ irq_domain operations.
199+
200+With support of hierarchy irq_domain and hierarchy irq_data ready, an
201+irq_domain structure is built for each interrupt controller, and an
202+irq_data structure is allocated for each irq_domain associated with an
203+IRQ. Now we could go one step further to support stacked(hierarchy)
204+irq_chip. That is, an irq_chip is associated with each irq_data along
205+the hierarchy. A child irq_chip may implement a required action by
206+itself or by cooperating with its parent irq_chip.
207+
208+With stacked irq_chip, interrupt controller driver only needs to deal
209+with the hardware managed by itself and may ask for services from its
210+parent irq_chip when needed. So we could achieve a much cleaner
211+software architecture.
212+
213+For an interrupt controller driver to support hierarchy irq_domain, it
214+needs to:
215+1) Implement irq_domain_ops.alloc and irq_domain_ops.free
216+2) Optionally implement irq_domain_ops.activate and
217+ irq_domain_ops.deactivate.
218+3) Optionally implement an irq_chip to manage the interrupt controller
219+ hardware.
220+4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
221+ they are unused with hierarchy irq_domain.
222+
223+Hierarchy irq_domain may also be used to support other architectures,
224+such as ARM, ARM64 etc.
Documentation/Makefile+4−3
@@ -1,3 +1,4 @@
1−obj-m := DocBook/ accounting/ auxdisplay/ connector/ \
2− filesystems/ filesystems/configfs/ ia64/ laptops/ networking/ \
3− pcmcia/ spi/ timers/ watchdog/src/ misc-devices/mei/
1+subdir-y := accounting arm auxdisplay blackfin connector \
2+ filesystems filesystems ia64 laptops mic misc-devices \
3+ networking pcmcia prctl ptp spi timers vDSO video4linux \
4+ watchdog
Documentation/RCU/rcu.txt+2−2
@@ -36,7 +36,7 @@ o How can the updater tell when a grace period has completed · 35 unmodified lines
3636 executed in user mode, or executed in the idle loop, we can
3737 safely free up that item.
3838
39− Preemptible variants of RCU (CONFIG_TREE_PREEMPT_RCU) get the
39+ Preemptible variants of RCU (CONFIG_PREEMPT_RCU) get the
4040 same effect, but require that the readers manipulate CPU-local
4141 counters. These counters allow limited types of blocking within
4242 RCU read-side critical sections. SRCU also uses CPU-local
@@ -81,7 +81,7 @@ o I hear that RCU is patented? What is with that? · 38 unmodified lines
8181 o I hear that RCU needs work in order to support realtime kernels?
8282
8383 This work is largely completed. Realtime-friendly RCU can be
84− enabled via the CONFIG_TREE_PREEMPT_RCU kernel configuration
84+ enabled via the CONFIG_PREEMPT_RCU kernel configuration
8585 parameter. However, work is in progress for enabling priority
8686 boosting of preempted RCU read-side critical sections. This is
8787 needed if you have CPU-bound realtime threads.
Documentation/RCU/stallwarn.txt+28−19
@@ -26,12 +26,6 @@ CONFIG_RCU_CPU_STALL_TIMEOUT · 25 unmodified lines
2626 Stall-warning messages may be enabled and disabled completely via
2727 /sys/module/rcupdate/parameters/rcu_cpu_stall_suppress.
2828
29−CONFIG_RCU_CPU_STALL_VERBOSE
30−
31− This kernel configuration parameter causes the stall warning to
32− also dump the stacks of any tasks that are blocking the current
33− RCU-preempt grace period.
34−
3529 CONFIG_RCU_CPU_STALL_INFO
3630
3731 This kernel configuration parameter causes the stall warning to
@@ -56,8 +50,20 @@ RCU_STALL_RAT_DELAY · 18 unmodified lines
5650 two jiffies. (This is a cpp macro, not a kernel configuration
5751 parameter.)
5852
59−When a CPU detects that it is stalling, it will print a message similar
60−to the following:
53+rcupdate.rcu_task_stall_timeout
54+
55+ This boot/sysfs parameter controls the RCU-tasks stall warning
56+ interval. A value of zero or less suppresses RCU-tasks stall
57+ warnings. A positive value sets the stall-warning interval
58+ in jiffies. An RCU-tasks stall warning starts wtih the line:
59+
60+ INFO: rcu_tasks detected stalls on tasks:
61+
62+ And continues with the output of sched_show_task() for each
63+ task stalling the current RCU-tasks grace period.
64+
65+For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
66+it will print a message similar to the following:
6167
6268 INFO: rcu_sched_state detected stall on CPU 5 (t=2500 jiffies)
6369
@@ -65,7 +71,7 @@ This message indicates that CPU 5 detected that it was causing a stall, · 1 unmodified line
6571 and that the stall was affecting RCU-sched. This message will normally be
6672 followed by a stack dump of the offending CPU. On TREE_RCU kernel builds,
6773 RCU and RCU-sched are implemented by the same underlying mechanism,
68−while on TREE_PREEMPT_RCU kernel builds, RCU is instead implemented
74+while on PREEMPT_RCU kernel builds, RCU is instead implemented
6975 by rcu_preempt_state.
7076
7177 On the other hand, if the offending CPU fails to print out a stall-warning
@@ -77,7 +83,7 @@ INFO: rcu_bh_state detected stalls on CPUs/tasks: { 3 5 } (detected by 2, 2502 j · 5 unmodified lines
7783 This message indicates that CPU 2 detected that CPUs 3 and 5 were both
7884 causing stalls, and that the stall was affecting RCU-bh. This message
7985 will normally be followed by stack dumps for each CPU. Please note that
80−TREE_PREEMPT_RCU builds can be stalled by tasks as well as by CPUs,
86+PREEMPT_RCU builds can be stalled by tasks as well as by CPUs,
8187 and that the tasks will be indicated by PID, for example, "P3421".
8288 It is even possible for a rcu_preempt_state stall to be caused by both
8389 CPUs -and- tasks, in which case the offending CPUs and tasks will all
@@ -174,8 +180,12 @@ o A CPU looping with preemption disabled. This condition can · 90 unmodified lines
174180 o A CPU looping with bottom halves disabled. This condition can
175181 result in RCU-sched and RCU-bh stalls.
176182
177−o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the kernel
178− without invoking schedule().
183+o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the
184+ kernel without invoking schedule(). Note that cond_resched()
185+ does not necessarily prevent RCU CPU stall warnings. Therefore,
186+ if the looping in the kernel is really expected and desirable
187+ behavior, you might need to replace some of the cond_resched()
188+ calls with calls to cond_resched_rcu_qs().
179189
180190 o A CPU-bound real-time task in a CONFIG_PREEMPT kernel, which might
181191 happen to preempt a low-priority task in the middle of an RCU
@@ -189,10 +199,10 @@ o A CPU-bound real-time task in a CONFIG_PREEMPT kernel, which might · 7 unmodified lines
189199 o A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that
190200 is running at a higher priority than the RCU softirq threads.
191201 This will prevent RCU callbacks from ever being invoked,
192− and in a CONFIG_TREE_PREEMPT_RCU kernel will further prevent
202+ and in a CONFIG_PREEMPT_RCU kernel will further prevent
193203 RCU grace periods from ever completing. Either way, the
194204 system will eventually run out of memory and hang. In the
195− CONFIG_TREE_PREEMPT_RCU case, you might see stall-warning
205+ CONFIG_PREEMPT_RCU case, you might see stall-warning
196206 messages.
197207
198208 o A hardware or software issue shuts off the scheduler-clock
@@ -208,11 +218,10 @@ o A hardware failure. This is quite unlikely, but has occurred · 9 unmodified lines
208218 This resulted in a series of RCU CPU stall warnings, eventually
209219 leading the realization that the CPU had failed.
210220
211−The RCU, RCU-sched, and RCU-bh implementations have CPU stall warning.
212−SRCU does not have its own CPU stall warnings, but its calls to
213−synchronize_sched() will result in RCU-sched detecting RCU-sched-related
214−CPU stalls. Please note that RCU only detects CPU stalls when there is
215−a grace period in progress. No grace period, no CPU stall warnings.
221+The RCU, RCU-sched, RCU-bh, and RCU-tasks implementations have CPU stall
222+warning. Note that SRCU does -not- have CPU stall warnings. Please note
223+that RCU only detects CPU stalls when there is a grace period in progress.
224+No grace period, no CPU stall warnings.
216225
217226 To diagnose the cause of the stall, inspect the stack traces.
218227 The offending function will usually be near the top of the stack.
Documentation/RCU/trace.txt+2−2
@@ -8,7 +8,7 @@ The following sections describe the debugfs files and formats, first · 7 unmodified lines
88 for rcutree and next for rcutiny.
99
1010
11−CONFIG_TREE_RCU and CONFIG_TREE_PREEMPT_RCU debugfs Files and Formats
11+CONFIG_TREE_RCU and CONFIG_PREEMPT_RCU debugfs Files and Formats
1212
1313 These implementations of RCU provide several debugfs directories under the
1414 top-level directory "rcu":
@@ -18,7 +18,7 @@ rcu/rcu_preempt · 3 unmodified lines
1818 rcu/rcu_sched
1919
2020 Each directory contains files for the corresponding flavor of RCU.
21−Note that rcu/rcu_preempt is only present for CONFIG_TREE_PREEMPT_RCU.
21+Note that rcu/rcu_preempt is only present for CONFIG_PREEMPT_RCU.
2222 For CONFIG_TREE_RCU, the RCU flavor maps onto the RCU-sched flavor,
2323 so that activity for both appears in rcu/rcu_sched.
2424
Documentation/RCU/whatisRCU.txt+1−1
@@ -137,7 +137,7 @@ rcu_read_lock() · 136 unmodified lines
137137 Used by a reader to inform the reclaimer that the reader is
138138 entering an RCU read-side critical section. It is illegal
139139 to block while in an RCU read-side critical section, though
140− kernels built with CONFIG_TREE_PREEMPT_RCU can preempt RCU
140+ kernels built with CONFIG_PREEMPT_RCU can preempt RCU
141141 read-side critical sections. Any RCU-protected data structure
142142 accessed during an RCU read-side critical section is guaranteed to
143143 remain unreclaimed for the full duration of that critical section.
Documentation/SubmittingPatches+4−6
@@ -483,12 +483,10 @@ have been included in the discussion · 482 unmodified lines
483483
484484 14) Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
485485
486−If this patch fixes a problem reported by somebody else, consider adding a
487−Reported-by: tag to credit the reporter for their contribution. Please
488−note that this tag should not be added without the reporter's permission,
489−especially if the problem was not reported in a public forum. That said,
490−if we diligently credit our bug reporters, they will, hopefully, be
491−inspired to help us again in the future.
486+The Reported-by tag gives credit to people who find bugs and report them and it
487+hopefully inspires them to help us again in the future. Please note that if
488+the bug was reported in private, then ask for permission first before using the
489+Reported-by tag.
492490
493491 A Tested-by: tag indicates that the patch has been successfully tested (in
494492 some environment) by the person named. This tag informs maintainers that
Documentation/accounting/Makefile+0−3
@@ -1,6 +1,3 @@
1−# kbuild trick to avoid linker error. Can be omitted if a module is built.
2−obj- := dummy.o
3−
41 # List of programs to build
52 hostprogs-y := getdelays
63
Documentation/acpi/enumeration.txt+27−0
@@ -312,3 +312,30 @@ a code like this: · 311 unmodified lines
312312
313313 There are also devm_* versions of these functions which release the
314314 descriptors once the device is released.
315+
316+MFD devices
317+~~~~~~~~~~~
318+The MFD devices register their children as platform devices. For the child
319+devices there needs to be an ACPI handle that they can use to reference
320+parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
321+we provide two ways:
322+
323+ o The children share the parent ACPI handle.
324+ o The MFD cell can specify the ACPI id of the device.
325+
326+For the first case, the MFD drivers do not need to do anything. The
327+resulting child platform device will have its ACPI_COMPANION() set to point
328+to the parent device.
329+
330+If the ACPI namespace has a device that we can match using an ACPI id,
331+the id should be set like:
332+
333+ static struct mfd_cell my_subdevice_cell = {
334+ .name = "my_subdevice",
335+ /* set the resources relative to the parent */
336+ .acpi_pnpid = "XYZ0001",
337+ };
338+
339+The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
340+the MFD device and if found, that ACPI companion device is bound to the
341+resulting child platform device.
Documentation/acpi/gpio-properties.txt+96−0
@@ -0,0 +1,96 @@
1+_DSD Device Properties Related to GPIO
2+--------------------------------------
3+
4+With the release of ACPI 5.1 and the _DSD configuration objecte names
5+can finally be given to GPIOs (and other things as well) returned by
6+_CRS. Previously, we were only able to use an integer index to find
7+the corresponding GPIO, which is pretty error prone (it depends on
8+the _CRS output ordering, for example).
9+
10+With _DSD we can now query GPIOs using a name instead of an integer
11+index, like the ASL example below shows:
12+
13+ // Bluetooth device with reset and shutdown GPIOs
14+ Device (BTH)
15+ {
16+ Name (_HID, ...)
17+
18+ Name (_CRS, ResourceTemplate ()
19+ {
20+ GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
21+ "\\_SB.GPO0", 0, ResourceConsumer) {15}
22+ GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
23+ "\\_SB.GPO0", 0, ResourceConsumer) {27, 31}
24+ })
25+
26+ Name (_DSD, Package ()
27+ {
28+ ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
29+ Package ()
30+ {
31+ Package () {"reset-gpio", Package() {^BTH, 1, 1, 0 }},
32+ Package () {"shutdown-gpio", Package() {^BTH, 0, 0, 0 }},
33+ }
34+ })
35+ }
36+
37+The format of the supported GPIO property is:
38+
39+ Package () { "name", Package () { ref, index, pin, active_low }}
40+
41+ ref - The device that has _CRS containing GpioIo()/GpioInt() resources,
42+ typically this is the device itself (BTH in our case).
43+ index - Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
44+ pin - Pin in the GpioIo()/GpioInt() resource. Typically this is zero.
45+ active_low - If 1 the GPIO is marked as active_low.
46+
47+Since ACPI GpioIo() resource does not have a field saying whether it is
48+active low or high, the "active_low" argument can be used here. Setting
49+it to 1 marks the GPIO as active low.
50+
51+In our Bluetooth example the "reset-gpio" refers to the second GpioIo()
52+resource, second pin in that resource with the GPIO number of 31.
53+
54+ACPI GPIO Mappings Provided by Drivers
55+--------------------------------------
56+
57+There are systems in which the ACPI tables do not contain _DSD but provide _CRS
58+with GpioIo()/GpioInt() resources and device drivers still need to work with
59+them.
60+
61+In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
62+available to the driver can be used to identify the device and that is supposed
63+to be sufficient to determine the meaning and purpose of all of the GPIO lines
64+listed by the GpioIo()/GpioInt() resources returned by _CRS. In other words,
65+the driver is supposed to know what to use the GpioIo()/GpioInt() resources for
66+once it has identified the device. Having done that, it can simply assign names
67+to the GPIO lines it is going to use and provide the GPIO subsystem with a
68+mapping between those names and the ACPI GPIO resources corresponding to them.
69+
70+To do that, the driver needs to define a mapping table as a NULL-terminated
71+array of struct acpi_gpio_mapping objects that each contain a name, a pointer
72+to an array of line data (struct acpi_gpio_params) objects and the size of that
73+array. Each struct acpi_gpio_params object consists of three fields,
74+crs_entry_index, line_index, active_low, representing the index of the target
75+GpioIo()/GpioInt() resource in _CRS starting from zero, the index of the target
76+line in that resource starting from zero, and the active-low flag for that line,
77+respectively, in analogy with the _DSD GPIO property format specified above.
78+
79+For the example Bluetooth device discussed previously the data structures in
80+question would look like this:
81+
82+static const struct acpi_gpio_params reset_gpio = { 1, 1, false };
83+static const struct acpi_gpio_params shutdown_gpio = { 0, 0, false };
84+
85+static const struct acpi_gpio_mapping bluetooth_acpi_gpios[] = {
86+ { "reset-gpio", &reset_gpio, 1 },
87+ { "shutdown-gpio", &shutdown_gpio, 1 },
88+ { },
89+};
90+
91+Next, the mapping table needs to be passed as the second argument to
92+acpi_dev_add_driver_gpios() that will register it with the ACPI device object
93+pointed to by its first argument. That should be done in the driver's .probe()
94+routine. On removal, the driver should unregister its GPIO mapping table by
95+calling acpi_dev_remove_driver_gpios() on the ACPI device object where that
96+table was previously registered.
Documentation/applying-patches.txt+1−1
@@ -94,7 +94,7 @@ Common errors when patching · 93 unmodified lines
9494 ---
9595 When patch applies a patch file it attempts to verify the sanity of the
9696 file in different ways.
97−Checking that the file looks like a valid patch file & checking the code
97+Checking that the file looks like a valid patch file and checking the code
9898 around the bits being modified matches the context provided in the patch are
9999 just two of the basic sanity checks patch does.
100100
Documentation/arm/Makefile+1−0
@@ -0,0 +1 @@
1+subdir-y := SH-Mobile
Documentation/arm/Marvell/README+4−0
@@ -103,6 +103,10 @@ EBU Armada family · 102 unmodified lines
103103 NOTE: not to be confused with the non-SMP 78xx0 SoCs
104104 Product Brief: http://www.marvell.com/embedded-processors/armada-xp/assets/Marvell-ArmadaXP-SoC-product%20brief.pdf
105105 Functional Spec: http://www.marvell.com/embedded-processors/armada-xp/assets/ARMADA-XP-Functional-SpecDatasheet.pdf
106+ Hardware Specs:
107+ http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78230_OS.PDF
108+ http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78260_OS.PDF
109+ http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78460_OS.PDF
106110
107111 Core: Sheeva ARMv7 compatible
108112
Documentation/arm/SH-Mobile/.gitignore+1−0
@@ -0,0 +1 @@
1+vrl4
Documentation/arm/SH-Mobile/Makefile+5−6
@@ -1,8 +1,7 @@
1−BIN := vrl4
1+# List of programs to build
2+hostprogs-y := vrl4
23
3−.PHONY: all
4−all: $(BIN)
4+# Tell kbuild to always build the programs
5+always := $(hostprogs-y)
56
6−.PHONY: clean
7−clean:
8− rm -f *.o $(BIN)
7+HOSTCFLAGS_vrl4.o += -I$(objtree)/usr/include -I$(srctree)/tools/include
Documentation/arm/SH-Mobile/vrl4.c+4−3
@@ -34,6 +34,7 @@ · 33 unmodified lines
3434 #include <stdint.h>
3535 #include <stdio.h>
3636 #include <errno.h>
37+#include <tools/endian.h>
3738
3839 struct hdr {
3940 uint32_t magic1;
@@ -77,7 +78,7 @@ struct hdr { · 37 unmodified lines
7778
7879 #define ROUND_UP(x) ((x + ALIGN - 1) & ~(ALIGN - 1))
7980
80−ssize_t do_read(int fd, void *buf, size_t count)
81+static ssize_t do_read(int fd, void *buf, size_t count)
8182 {
8283 size_t offset = 0;
8384 ssize_t l;
@@ -98,7 +99,7 @@ ssize_t do_read(int fd, void *buf, size_t count) · 14 unmodified lines
9899 return offset;
99100 }
100101
101−ssize_t do_write(int fd, const void *buf, size_t count)
102+static ssize_t do_write(int fd, const void *buf, size_t count)
102103 {
103104 size_t offset = 0;
104105 ssize_t l;
@@ -117,7 +118,7 @@ ssize_t do_write(int fd, const void *buf, size_t count) · 12 unmodified lines
117118 return offset;
118119 }
119120
120−ssize_t write_zero(int fd, size_t len)
121+static ssize_t write_zero(int fd, size_t len)
121122 {
122123 size_t i = len;
123124
Documentation/arm/firmware.txt+5−23
@@ -7,32 +7,14 @@ world, which changes the way some things have to be initialized. This makes · 6 unmodified lines
77 a need to provide an interface for such platforms to specify available firmware
88 operations and call them when needed.
99
10−Firmware operations can be specified using struct firmware_ops
11−
12− struct firmware_ops {
13− /*
14− * Enters CPU idle mode
15− */
16− int (*do_idle)(void);
17− /*
18− * Sets boot address of specified physical CPU
19− */
20− int (*set_cpu_boot_addr)(int cpu, unsigned long boot_addr);
21− /*
22− * Boots specified physical CPU
23− */
24− int (*cpu_boot)(int cpu);
25− /*
26− * Initializes L2 cache
27− */
28− int (*l2x0_init)(void);
29− };
30−
31−and then registered with register_firmware_ops function
10+Firmware operations can be specified by filling in a struct firmware_ops
11+with appropriate callbacks and then registering it with register_firmware_ops()
12+function.
3213
3314 void register_firmware_ops(const struct firmware_ops *ops)
3415
35−the ops pointer must be non-NULL.
16+The ops pointer must be non-NULL. More information about struct firmware_ops
17+and its members can be found in arch/arm/include/asm/firmware.h header.
3618
3719 There is a default, empty set of operations provided, so there is no need to
3820 set anything if platform does not require firmware operations.
Documentation/arm/memory.txt+1−1
@@ -41,7 +41,7 @@ fffe8000 fffeffff DTCM mapping area for platforms with · 40 unmodified lines
4141 fffe0000 fffe7fff ITCM mapping area for platforms with
4242 ITCM mounted inside the CPU.
4343
44−ffc00000 ffdfffff Fixmap mapping region. Addresses provided
44+ffc00000 ffefffff Fixmap mapping region. Addresses provided
4545 by fix_to_virt() will be located here.
4646
4747 fee00000 feffffff Mapping of PCI I/O space. This is a static
Documentation/arm/sunxi/README+13−3
@@ -37,16 +37,26 @@ SunXi family · 36 unmodified lines
3737 http://dl.linux-sunxi.org/A20/A20%20User%20Manual%202013-03-22.pdf
3838
3939 - Allwinner A23
40− + Not Supported
40+ + Datasheet
41+ http://dl.linux-sunxi.org/A23/A23%20Datasheet%20V1.0%2020130830.pdf
42+ + User Manual
43+ http://dl.linux-sunxi.org/A23/A23%20User%20Manual%20V1.0%2020130830.pdf
4144
4245 * Quad ARM Cortex-A7 based SoCs
4346 - Allwinner A31 (sun6i)
4447 + Datasheet
45− http://dl.linux-sunxi.org/A31/A31%20Datasheet%20-%20v1.00%20(2012-12-24).pdf
48+ http://dl.linux-sunxi.org/A31/A3x_release_document/A31/IC/A31%20datasheet%20V1.3%2020131106.pdf
49+ + User Manual
50+ http://dl.linux-sunxi.org/A31/A3x_release_document/A31/IC/A31%20user%20manual%20V1.1%2020130630.pdf
4651
4752 - Allwinner A31s (sun6i)
4853 + Not Supported
54+ + Datasheet
55+ http://dl.linux-sunxi.org/A31/A3x_release_document/A31s/IC/A31s%20datasheet%20V1.3%2020131106.pdf
56+ + User Manual
57+ http://dl.linux-sunxi.org/A31/A3x_release_document/A31s/IC/A31s%20User%20Manual%20%20V1.0%2020130322.pdf
4958
5059 * Quad ARM Cortex-A15, Quad ARM Cortex-A7 based SoCs
5160 - Allwinner A80
52− + Not Supported
61+ + Datasheet
62+ http://dl.linux-sunxi.org/A80/A80_Datasheet_Revision_1.0_0404.pdf
Documentation/arm64/legacy_instructions.txt+45−0
@@ -0,0 +1,45 @@
1+The arm64 port of the Linux kernel provides infrastructure to support
2+emulation of instructions which have been deprecated, or obsoleted in
3+the architecture. The infrastructure code uses undefined instruction
4+hooks to support emulation. Where available it also allows turning on
5+the instruction execution in hardware.
6+
7+The emulation mode can be controlled by writing to sysctl nodes
8+(/proc/sys/abi). The following explains the different execution
9+behaviours and the corresponding values of the sysctl nodes -
10+
11+* Undef
12+ Value: 0
13+ Generates undefined instruction abort. Default for instructions that
14+ have been obsoleted in the architecture, e.g., SWP
15+
16+* Emulate
17+ Value: 1
18+ Uses software emulation. To aid migration of software, in this mode
19+ usage of emulated instruction is traced as well as rate limited
20+ warnings are issued. This is the default for deprecated
21+ instructions, .e.g., CP15 barriers
22+
23+* Hardware Execution
24+ Value: 2
25+ Although marked as deprecated, some implementations may support the
26+ enabling/disabling of hardware support for the execution of these
27+ instructions. Using hardware execution generally provides better
28+ performance, but at the loss of ability to gather runtime statistics
29+ about the use of the deprecated instructions.
30+
31+The default mode depends on the status of the instruction in the
32+architecture. Deprecated instructions should default to emulation
33+while obsolete instructions must be undefined by default.
34+
35+Supported legacy instructions
36+-----------------------------
37+* SWP{B}
38+Node: /proc/sys/abi/swp
39+Status: Obsolete
40+Default: Undef (0)
41+
42+* CP15 Barriers
43+Node: /proc/sys/abi/cp15_barrier
44+Status: Deprecated
45+Default: Emulate (1)
Documentation/arm64/memory.txt+1−1
@@ -17,7 +17,7 @@ User addresses have bits 63:48 set to 0 while the kernel addresses have · 16 unmodified lines
1717 the same bits set to 1. TTBRx selection is given by bit 63 of the
1818 virtual address. The swapper_pg_dir contains only kernel (global)
1919 mappings while the user pgd contains only user (non-global) mappings.
20−The swapper_pgd_dir address is written to TTBR1 and never written to
20+The swapper_pg_dir address is written to TTBR1 and never written to
2121 TTBR0.
2222
2323
Documentation/atomic_ops.txt+8−4
@@ -7,12 +7,13 @@ · 6 unmodified lines
77 maintainers on how to implement atomic counter, bitops, and spinlock
88 interfaces properly.
99
10− The atomic_t type should be defined as a signed integer.
11−Also, it should be made opaque such that any kind of cast to a normal
12−C integer type will fail. Something like the following should
13−suffice:
10+ The atomic_t type should be defined as a signed integer and
11+the atomic_long_t type as a signed long integer. Also, they should
12+be made opaque such that any kind of cast to a normal C integer type
13+will fail. Something like the following should suffice:
1414
1515 typedef struct { int counter; } atomic_t;
16+ typedef struct { long counter; } atomic_long_t;
1617
1718 Historically, counter has been declared volatile. This is now discouraged.
1819 See Documentation/volatile-considered-harmful.txt for the complete rationale.
@@ -37,6 +38,9 @@ initializer is used before runtime. If the initializer is used at runtime, a · 18 unmodified lines
3738 proper implicit or explicit read memory barrier is needed before reading the
3839 value with atomic_read from another thread.
3940
41+As with all of the atomic_ interfaces, replace the leading "atomic_"
42+with "atomic_long_" to operate on atomic_long_t.
43+
4044 The second interface can be used at runtime, as in:
4145
4246 struct foo { atomic_t counter; };
Documentation/auxdisplay/Makefile+0−3
@@ -1,6 +1,3 @@
1−# kbuild trick to avoid linker error. Can be omitted if a module is built.
2−obj- := dummy.o
3−
41 # List of programs to build
52 hostprogs-y := cfag12864b-example
63
Documentation/binfmt_misc.txt+29−21
@@ -15,39 +15,50 @@ First you must mount binfmt_misc: · 14 unmodified lines
1515 mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
1616
1717 To actually register a new binary type, you have to set up a string looking like
18−:name:type:offset:magic:mask:interpreter:flags (where you can choose the ':' upon
19−your needs) and echo it to /proc/sys/fs/binfmt_misc/register.
18+:name:type:offset:magic:mask:interpreter:flags (where you can choose the ':'
19+upon your needs) and echo it to /proc/sys/fs/binfmt_misc/register.
20+
2021 Here is what the fields mean:
2122 - 'name' is an identifier string. A new /proc file will be created with this
22− name below /proc/sys/fs/binfmt_misc
23+ name below /proc/sys/fs/binfmt_misc; cannot contain slashes '/' for obvious
24+ reasons.
2325 - 'type' is the type of recognition. Give 'M' for magic and 'E' for extension.
2426 - 'offset' is the offset of the magic/mask in the file, counted in bytes. This
25− defaults to 0 if you omit it (i.e. you write ':name:type::magic...')
27+ defaults to 0 if you omit it (i.e. you write ':name:type::magic...'). Ignored
28+ when using filename extension matching.
2629 - 'magic' is the byte sequence binfmt_misc is matching for. The magic string
27− may contain hex-encoded characters like \x0a or \xA4. In a shell environment
28− you will have to write \\x0a to prevent the shell from eating your \.
30+ may contain hex-encoded characters like \x0a or \xA4. Note that you must
31+ escape any NUL bytes; parsing halts at the first one. In a shell environment
32+ you might have to write \\x0a to prevent the shell from eating your \.
2933 If you chose filename extension matching, this is the extension to be
3034 recognised (without the '.', the \x0a specials are not allowed). Extension
31− matching is case sensitive!
35+ matching is case sensitive, and slashes '/' are not allowed!
3236 - 'mask' is an (optional, defaults to all 0xff) mask. You can mask out some
3337 bits from matching by supplying a string like magic and as long as magic.
34− The mask is anded with the byte sequence of the file.
38+ The mask is anded with the byte sequence of the file. Note that you must
39+ escape any NUL bytes; parsing halts at the first one. Ignored when using
40+ filename extension matching.
3541 - 'interpreter' is the program that should be invoked with the binary as first
3642 argument (specify the full path)
3743 - 'flags' is an optional field that controls several aspects of the invocation
38− of the interpreter. It is a string of capital letters, each controls a certain
39− aspect. The following flags are supported -
40− 'P' - preserve-argv[0]. Legacy behavior of binfmt_misc is to overwrite the
41− original argv[0] with the full path to the binary. When this flag is
42− included, binfmt_misc will add an argument to the argument vector for
43− this purpose, thus preserving the original argv[0].
44+ of the interpreter. It is a string of capital letters, each controls a
45+ certain aspect. The following flags are supported -
46+ 'P' - preserve-argv[0]. Legacy behavior of binfmt_misc is to overwrite
47+ the original argv[0] with the full path to the binary. When this
48+ flag is included, binfmt_misc will add an argument to the argument
49+ vector for this purpose, thus preserving the original argv[0].
50+ e.g. If your interp is set to /bin/foo and you run `blah` (which is
51+ in /usr/local/bin), then the kernel will execute /bin/foo with
52+ argv[] set to ["/bin/foo", "/usr/local/bin/blah", "blah"]. The
53+ interp has to be aware of this so it can execute /usr/local/bin/blah
54+ with argv[] set to ["blah"].
4455 'O' - open-binary. Legacy behavior of binfmt_misc is to pass the full path
4556 of the binary to the interpreter as an argument. When this flag is
4657 included, binfmt_misc will open the file for reading and pass its
4758 descriptor as an argument, instead of the full path, thus allowing
48− the interpreter to execute non-readable binaries. This feature should
49− be used with care - the interpreter has to be trusted not to emit
50− the contents of the non-readable binary.
59+ the interpreter to execute non-readable binaries. This feature
60+ should be used with care - the interpreter has to be trusted not to
61+ emit the contents of the non-readable binary.
5162 'C' - credentials. Currently, the behavior of binfmt_misc is to calculate
5263 the credentials and security token of the new process according to
5364 the interpreter. When this flag is included, these attributes are
@@ -58,7 +69,7 @@ Here is what the fields mean: · 4 unmodified lines
5869
5970
6071 There are some restrictions:
61− - the whole register string may not exceed 255 characters
72+ - the whole register string may not exceed 1920 characters
6273 - the magic must reside in the first 128 bytes of the file, i.e.
6374 offset+size(magic) has to be less than 128
6475 - the interpreter string may not exceed 127 characters
@@ -110,7 +121,4 @@ passes it the full filename (or the file descriptor) to use. Using $PATH can · 45 unmodified lines
110121 cause unexpected behaviour and can be a security hazard.
111122
112123
113−There is a web page about binfmt_misc at
114−http://www.tat.physik.uni-tuebingen.de
115−
116124 Richard Günther <rguenth@tat.physik.uni-tuebingen.de>
Documentation/blackfin/Makefile+2−5
@@ -1,6 +1,3 @@
1+ifneq ($(CONFIG_BLACKFIN),)
12 obj-m := gptimers-example.o
2−
3−all: modules
4−
5−modules clean:
6− $(MAKE) -C ../.. SUBDIRS=$(PWD) $@
3+endif
Documentation/block/biodoc.txt+5−5
@@ -827,10 +827,6 @@ but in the event of any barrier requests in the tag queue we need to ensure · 826 unmodified lines
827827 that requests are restarted in the order they were queue. This may happen
828828 if the driver needs to use blk_queue_invalidate_tags().
829829
830−Tagging also defines a new request flag, REQ_QUEUED. This is set whenever
831−a request is currently tagged. You should not use this flag directly,
832−blk_rq_tagged(rq) is the portable way to do so.
833−
834830 3.3 I/O Submission
835831
836832 The routine submit_bio() is used to submit a single io. Higher level i/o
@@ -946,7 +942,11 @@ elevator_allow_merge_fn called whenever the block layer determines · 109 unmodified lines
946942 request safely. The io scheduler may still
947943 want to stop a merge at this point if it
948944 results in some sort of conflict internally,
949− this hook allows it to do that.
945+ this hook allows it to do that. Note however
946+ that two *requests* can still be merged at later
947+ time. Currently the io scheduler has no way to
948+ prevent that. It can only learn about the fact
949+ from elevator_merge_req_fn callback.
950950
951951 elevator_dispatch_fn* fills the dispatch queue with ready requests.
952952 I/O schedulers are free to postpone requests by
Documentation/block/data-integrity.txt+5−49
@@ -129,11 +129,11 @@ interface for this is being worked on. · 128 unmodified lines
129129 4.1 BIO
130130
131131 The data integrity patches add a new field to struct bio when
132−CONFIG_BLK_DEV_INTEGRITY is enabled. bio->bi_integrity is a pointer
133−to a struct bip which contains the bio integrity payload. Essentially
134−a bip is a trimmed down struct bio which holds a bio_vec containing
135−the integrity metadata and the required housekeeping information (bvec
136−pool, vector count, etc.)
132+CONFIG_BLK_DEV_INTEGRITY is enabled. bio_integrity(bio) returns a
133+pointer to a struct bip which contains the bio integrity payload.
134+Essentially a bip is a trimmed down struct bio which holds a bio_vec
135+containing the integrity metadata and the required housekeeping
136+information (bvec pool, vector count, etc.)
137137
138138 A kernel subsystem can enable data integrity protection on a bio by
139139 calling bio_integrity_alloc(bio). This will allocate and attach the
@@ -192,16 +192,6 @@ will require extra work due to the application tag. · 52 unmodified lines
192192 supported by the block device.
193193
194194
195− int bdev_integrity_enabled(block_device, int rw);
196−
197− bdev_integrity_enabled() will return 1 if the block device
198− supports integrity metadata transfer for the data direction
199− specified in 'rw'.
200−
201− bdev_integrity_enabled() honors the write_generate and
202− read_verify flags in sysfs and will respond accordingly.
203−
204−
205195 int bio_integrity_prep(bio);
206196
207197 To generate IMD for WRITE and to set up buffers for READ, the
@@ -216,36 +206,6 @@ will require extra work due to the application tag. · 8 unmodified lines
216206 bio_integrity_enabled() returned 1.
217207
218208
219− int bio_integrity_tag_size(bio);
220−
221− If the filesystem wants to use the application tag space it will
222− first have to find out how much storage space is available.
223− Because tag space is generally limited (usually 2 bytes per
224− sector regardless of sector size), the integrity framework
225− supports interleaving the information between the sectors in an
226− I/O.
227−
228− Filesystems can call bio_integrity_tag_size(bio) to find out how
229− many bytes of storage are available for that particular bio.
230−
231− Another option is bdev_get_tag_size(block_device) which will
232− return the number of available bytes per hardware sector.
233−
234−
235− int bio_integrity_set_tag(bio, void *tag_buf, len);
236−
237− After a successful return from bio_integrity_prep(),
238− bio_integrity_set_tag() can be used to attach an opaque tag
239− buffer to a bio. Obviously this only makes sense if the I/O is
240− a WRITE.
241−
242−
243− int bio_integrity_get_tag(bio, void *tag_buf, len);
244−
245− Similarly, at READ I/O completion time the filesystem can
246− retrieve the tag buffer using bio_integrity_get_tag().
247−
248−
249209 5.3 PASSING EXISTING INTEGRITY METADATA
250210
251211 Filesystems that either generate their own integrity metadata or
@@ -298,8 +258,6 @@ will require extra work due to the application tag. · 46 unmodified lines
298258 .name = "STANDARDSBODY-TYPE-VARIANT-CSUM",
299259 .generate_fn = my_generate_fn,
300260 .verify_fn = my_verify_fn,
301− .get_tag_fn = my_get_tag_fn,
302− .set_tag_fn = my_set_tag_fn,
303261 .tuple_size = sizeof(struct my_tuple_size),
304262 .tag_size = <tag bytes per hw sector>,
305263 };
@@ -321,7 +279,5 @@ will require extra work due to the application tag. · 15 unmodified lines
321279 are available per hardware sector. For DIF this is either 2 or
322280 0 depending on the value of the Control Mode Page ATO bit.
323281
324− See 6.2 for a description of get_tag_fn and set_tag_fn.
325−
326282 ----------------------------------------------------------------------
327283 2007-12-24 Martin K. Petersen <martin.petersen@oracle.com>
Documentation/block/null_blk.txt+2−2
@@ -42,7 +42,7 @@ nr_devices=[Number of devices]: Default: 2 · 41 unmodified lines
4242 Number of block devices instantiated. They are instantiated as /dev/nullb0,
4343 etc.
4444
45−irq_mode=[0-2]: Default: 1-Soft-irq
45+irqmode=[0-2]: Default: 1-Soft-irq
4646 The completion mode used for completing IOs to the block-layer.
4747
4848 0: None.
@@ -53,7 +53,7 @@ irq_mode=[0-2]: Default: 1-Soft-irq · 4 unmodified lines
5353 completion.
5454
5555 completion_nsec=[ns]: Default: 10.000ns
56− Combined with irq_mode=2 (timer). The time each completion event must wait.
56+ Combined with irqmode=2 (timer). The time each completion event must wait.
5757
5858 submit_queues=[0..nr_cpus]:
5959 The number of submission queues attached to the device driver. If unset, it
Documentation/block/queue-sysfs.txt+3−3
@@ -11,7 +11,7 @@ read-write. · 10 unmodified lines
1111
1212 add_random (RW)
1313 ----------------
14−This file allows to trun off the disk entropy contribution. Default
14+This file allows to turn off the disk entropy contribution. Default
1515 value of this file is '1'(on).
1616
1717 discard_granularity (RO)
@@ -72,7 +72,7 @@ Maximum segment size of the device. · 54 unmodified lines
7272
7373 minimum_io_size (RO)
7474 --------------------
75−This is the smallest preferred io size reported by the device.
75+This is the smallest preferred IO size reported by the device.
7676
7777 nomerges (RW)
7878 -------------
@@ -98,7 +98,7 @@ regulated by nr_requests. · 19 unmodified lines
9898
9999 optimal_io_size (RO)
100100 --------------------
101−This is the optimal io size reported by the device.
101+This is the optimal IO size reported by the device.
102102
103103 physical_block_size (RO)
104104 ------------------------
Documentation/blockdev/zram.txt+21−4
@@ -74,14 +74,30 @@ There is little point creating a zram of greater than twice the size of memory · 73 unmodified lines
7474 since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the
7575 size of the disk when not in use so a huge zram is wasteful.
7676
77−5) Activate:
77+5) Set memory limit: Optional
78+ Set memory limit by writing the value to sysfs node 'mem_limit'.
79+ The value can be either in bytes or you can use mem suffixes.
80+ In addition, you could change the value in runtime.
81+ Examples:
82+ # limit /dev/zram0 with 50MB memory
83+ echo $((50*1024*1024)) > /sys/block/zram0/mem_limit
84+
85+ # Using mem suffixes
86+ echo 256K > /sys/block/zram0/mem_limit
87+ echo 512M > /sys/block/zram0/mem_limit
88+ echo 1G > /sys/block/zram0/mem_limit
89+
90+ # To disable memory limit
91+ echo 0 > /sys/block/zram0/mem_limit
92+
93+6) Activate:
7894 mkswap /dev/zram0
7995 swapon /dev/zram0
8096
8197 mkfs.ext4 /dev/zram1
8298 mount /dev/zram1 /tmp
8399
84−6) Stats:
100+7) Stats:
85101 Per-device statistics are exported as various nodes under
86102 /sys/block/zram<id>/
87103 disksize
@@ -95,12 +111,13 @@ size of the disk when not in use so a huge zram is wasteful. · 7 unmodified lines
95111 orig_data_size
96112 compr_data_size
97113 mem_used_total
114+ mem_used_max
98115
99−7) Deactivate:
116+8) Deactivate:
100117 swapoff /dev/zram0
101118 umount /dev/zram1
102119
103−8) Reset:
120+9) Reset:
104121 Write any positive value to 'reset' sysfs node
105122 echo 1 > /sys/block/zram0/reset
106123 echo 1 > /sys/block/zram1/reset
Documentation/cgroups/cgroups.txt+2−2
@@ -312,10 +312,10 @@ the "cpuset" cgroup subsystem, the steps are something like: · 311 unmodified lines
312312 2) mkdir /sys/fs/cgroup/cpuset
313313 3) mount -t cgroup -ocpuset cpuset /sys/fs/cgroup/cpuset
314314 4) Create the new cgroup by doing mkdir's and write's (or echo's) in
315− the /sys/fs/cgroup virtual file system.
315+ the /sys/fs/cgroup/cpuset virtual file system.
316316 5) Start a task that will be the "founding father" of the new job.
317317 6) Attach that task to the new cgroup by writing its PID to the
318− /sys/fs/cgroup/cpuset/tasks file for that cgroup.
318+ /sys/fs/cgroup/cpuset tasks file for that cgroup.
319319 7) fork, exec or clone the job tasks from this founding father task.
320320
321321 For example, the following sequence of commands will setup a cgroup
Documentation/cgroups/cpusets.txt+3−3
@@ -445,7 +445,7 @@ across partially overlapping sets of CPUs would risk unstable dynamics · 444 unmodified lines
445445 that would be beyond our understanding. So if each of two partially
446446 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
447447 form a single sched domain that is a superset of both. We won't move
448−a task to a CPU outside it cpuset, but the scheduler load balancing
448+a task to a CPU outside its cpuset, but the scheduler load balancing
449449 code might waste some compute cycles considering that possibility.
450450
451451 This mismatch is why there is not a simple one-to-one relation
@@ -552,8 +552,8 @@ otherwise initial value -1 that indicates the cpuset has no request. · 100 unmodified lines
552552 1 : search siblings (hyperthreads in a core).
553553 2 : search cores in a package.
554554 3 : search cpus in a node [= system wide on non-NUMA system]
555− ( 4 : search nodes in a chunk of node [on NUMA system] )
556− ( 5 : search system wide [on NUMA system] )
555+ 4 : search nodes in a chunk of node [on NUMA system]
556+ 5 : search system wide [on NUMA system]
557557
558558 The system default is architecture dependent. The system default
559559 can be changed using the relax_domain_level= boot parameter.
Documentation/cgroups/hugetlb.txt+1−1
@@ -29,7 +29,7 @@ Brief summary of control files · 28 unmodified lines
2929
3030 hugetlb.<hugepagesize>.limit_in_bytes # set/show limit of "hugepagesize" hugetlb usage
3131 hugetlb.<hugepagesize>.max_usage_in_bytes # show max "hugepagesize" hugetlb usage recorded
32− hugetlb.<hugepagesize>.usage_in_bytes # show current res_counter usage for "hugepagesize" hugetlb
32+ hugetlb.<hugepagesize>.usage_in_bytes # show current usage for "hugepagesize" hugetlb
3333 hugetlb.<hugepagesize>.failcnt # show the number of allocation failure due to HugeTLB limit
3434
3535 For a system supporting two hugepage size (16M and 16G) the control
Documentation/cgroups/memory.txt+19−15
@@ -1,5 +1,10 @@
11 Memory Resource Controller
22
3+NOTE: This document is hopelessly outdated and it asks for a complete
4+ rewrite. It still contains a useful information so we are keeping it
5+ here but make sure to check the current code if you need a deeper
6+ understanding.
7+
38 NOTE: The Memory Resource Controller has generically been referred to as the
49 memory controller in this document. Do not confuse memory controller
510 used here with the memory controller that is used in hardware.
@@ -52,9 +57,9 @@ Brief summary of control files. · 46 unmodified lines
5257 tasks # attach a task(thread) and show list of threads
5358 cgroup.procs # show list of processes
5459 cgroup.event_control # an interface for event_fd()
55− memory.usage_in_bytes # show current res_counter usage for memory
60+ memory.usage_in_bytes # show current usage for memory
5661 (See 5.5 for details)
57− memory.memsw.usage_in_bytes # show current res_counter usage for memory+Swap
62+ memory.memsw.usage_in_bytes # show current usage for memory+Swap
5863 (See 5.5 for details)
5964 memory.limit_in_bytes # set/show limit of memory usage
6065 memory.memsw.limit_in_bytes # set/show limit of memory+Swap usage
@@ -116,16 +121,16 @@ The memory controller is the first controller developed. · 55 unmodified lines
116121
117122 2.1. Design
118123
119−The core of the design is a counter called the res_counter. The res_counter
120−tracks the current memory usage and limit of the group of processes associated
121−with the controller. Each cgroup has a memory controller specific data
122−structure (mem_cgroup) associated with it.
124+The core of the design is a counter called the page_counter. The
125+page_counter tracks the current memory usage and limit of the group of
126+processes associated with the controller. Each cgroup has a memory controller
127+specific data structure (mem_cgroup) associated with it.
123128
124129 2.2. Accounting
125130
126131 +--------------------+
127− | mem_cgroup |
128− | (res_counter) |
132+ | mem_cgroup |
133+ | (page_counter) |
129134 +--------------------+
130135 / ^ \
131136 / | \
@@ -321,7 +326,7 @@ per cgroup, instead of globally. · 189 unmodified lines
321326
322327 * tcp memory pressure: sockets memory pressure for the tcp protocol.
323328
324−2.7.3 Common use cases
329+2.7.2 Common use cases
325330
326331 Because the "kmem" counter is fed to the main user counter, kernel memory can
327332 never be limited completely independently of user memory. Say "U" is the user
@@ -349,20 +354,19 @@ set: · 21 unmodified lines
349354
350355 3. User Interface
351356
352−0. Configuration
357+3.0. Configuration
353358
354359 a. Enable CONFIG_CGROUPS
355−b. Enable CONFIG_RESOURCE_COUNTERS
356−c. Enable CONFIG_MEMCG
357−d. Enable CONFIG_MEMCG_SWAP (to use swap extension)
360+b. Enable CONFIG_MEMCG
361+c. Enable CONFIG_MEMCG_SWAP (to use swap extension)
358362 d. Enable CONFIG_MEMCG_KMEM (to use kmem extension)
359363
360−1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?)
364+3.1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?)
361365 # mount -t tmpfs none /sys/fs/cgroup
362366 # mkdir /sys/fs/cgroup/memory
363367 # mount -t cgroup none /sys/fs/cgroup/memory -o memory
364368
365−2. Make the new group and move bash into it
369+3.2. Make the new group and move bash into it
366370 # mkdir /sys/fs/cgroup/memory/0
367371 # echo $$ > /sys/fs/cgroup/memory/0/tasks
368372
Documentation/cgroups/resource_counter.txt+0−197
@@ -1,197 +0,0 @@
1−
2− The Resource Counter
3−
4−The resource counter, declared at include/linux/res_counter.h,
5−is supposed to facilitate the resource management by controllers
6−by providing common stuff for accounting.
7−
8−This "stuff" includes the res_counter structure and routines
9−to work with it.
10−
11−
12−
13−1. Crucial parts of the res_counter structure
14−
15− a. unsigned long long usage
16−
17− The usage value shows the amount of a resource that is consumed
18− by a group at a given time. The units of measurement should be
19− determined by the controller that uses this counter. E.g. it can
20− be bytes, items or any other unit the controller operates on.
21−
22− b. unsigned long long max_usage
23−
24− The maximal value of the usage over time.
25−
26− This value is useful when gathering statistical information about
27− the particular group, as it shows the actual resource requirements
28− for a particular group, not just some usage snapshot.
29−
30− c. unsigned long long limit
31−
32− The maximal allowed amount of resource to consume by the group. In
33− case the group requests for more resources, so that the usage value
34− would exceed the limit, the resource allocation is rejected (see
35− the next section).
36−
37− d. unsigned long long failcnt
38−
39− The failcnt stands for "failures counter". This is the number of
40− resource allocation attempts that failed.
41−
42− c. spinlock_t lock
43−
44− Protects changes of the above values.
45−
46−
47−
48−2. Basic accounting routines
49−
50− a. void res_counter_init(struct res_counter *rc,
51− struct res_counter *rc_parent)
52−
53− Initializes the resource counter. As usual, should be the first
54− routine called for a new counter.
55−
56− The struct res_counter *parent can be used to define a hierarchical
57− child -> parent relationship directly in the res_counter structure,
58− NULL can be used to define no relationship.
59−
60− c. int res_counter_charge(struct res_counter *rc, unsigned long val,
61− struct res_counter **limit_fail_at)
62−
63− When a resource is about to be allocated it has to be accounted
64− with the appropriate resource counter (controller should determine
65− which one to use on its own). This operation is called "charging".
66−
67− This is not very important which operation - resource allocation
68− or charging - is performed first, but
69− * if the allocation is performed first, this may create a
70− temporary resource over-usage by the time resource counter is
71− charged;
72− * if the charging is performed first, then it should be uncharged
73− on error path (if the one is called).
74−
75− If the charging fails and a hierarchical dependency exists, the
76− limit_fail_at parameter is set to the particular res_counter element
77− where the charging failed.
78−
79− d. u64 res_counter_uncharge(struct res_counter *rc, unsigned long val)
80−
81− When a resource is released (freed) it should be de-accounted
82− from the resource counter it was accounted to. This is called
83− "uncharging". The return value of this function indicate the amount
84− of charges still present in the counter.
85−
86− The _locked routines imply that the res_counter->lock is taken.
87−
88− e. u64 res_counter_uncharge_until
89− (struct res_counter *rc, struct res_counter *top,
90− unsigned long val)
91−
92− Almost same as res_counter_uncharge() but propagation of uncharge
93− stops when rc == top. This is useful when kill a res_counter in
94− child cgroup.
95−
96− 2.1 Other accounting routines
97−
98− There are more routines that may help you with common needs, like
99− checking whether the limit is reached or resetting the max_usage
100− value. They are all declared in include/linux/res_counter.h.
101−
102−
103−
104−3. Analyzing the resource counter registrations
105−
106− a. If the failcnt value constantly grows, this means that the counter's
107− limit is too tight. Either the group is misbehaving and consumes too
108− many resources, or the configuration is not suitable for the group
109− and the limit should be increased.
110−
111− b. The max_usage value can be used to quickly tune the group. One may
112− set the limits to maximal values and either load the container with
113− a common pattern or leave one for a while. After this the max_usage
114− value shows the amount of memory the container would require during
115− its common activity.
116−
117− Setting the limit a bit above this value gives a pretty good
118− configuration that works in most of the cases.
119−
120− c. If the max_usage is much less than the limit, but the failcnt value
121− is growing, then the group tries to allocate a big chunk of resource
122− at once.
123−
124− d. If the max_usage is much less than the limit, but the failcnt value
125− is 0, then this group is given too high limit, that it does not
126− require. It is better to lower the limit a bit leaving more resource
127− for other groups.
128−
129−
130−
131−4. Communication with the control groups subsystem (cgroups)
132−
133−All the resource controllers that are using cgroups and resource counters
134−should provide files (in the cgroup filesystem) to work with the resource
135−counter fields. They are recommended to adhere to the following rules:
136−
137− a. File names
138−
139− Field name File name
140− ---------------------------------------------------
141− usage usage_in_<unit_of_measurement>
142− max_usage max_usage_in_<unit_of_measurement>
143− limit limit_in_<unit_of_measurement>
144− failcnt failcnt
145− lock no file :)
146−
147− b. Reading from file should show the corresponding field value in the
148− appropriate format.
149−
150− c. Writing to file
151−
152− Field Expected behavior
153− ----------------------------------
154− usage prohibited
155− max_usage reset to usage
156− limit set the limit
157− failcnt reset to zero
158−
159−
160−
161−5. Usage example
162−
163− a. Declare a task group (take a look at cgroups subsystem for this) and
164− fold a res_counter into it
165−
166− struct my_group {
167− struct res_counter res;
168−
169− <other fields>
170− }
171−
172− b. Put hooks in resource allocation/release paths
173−
174− int alloc_something(...)
175− {
176− if (res_counter_charge(res_counter_ptr, amount) < 0)
177− return -ENOMEM;
178−
179− <allocate the resource and return to the caller>
180− }
181−
182− void release_something(...)
183− {
184− res_counter_uncharge(res_counter_ptr, amount);
185−
186− <release the resource>
187− }
188−
189− In order to keep the usage value self-consistent, both the
190− "res_counter_ptr" and the "amount" in release_something() should be
191− the same as they were in the alloc_something() when the releasing
192− resource was allocated.
193−
194− c. Provide the way to read res_counter values and set them (the cgroups
195− still can help with it).
196−
197− c. Compile and run :)
Documentation/clk.txt+1−1
@@ -74,7 +74,7 @@ the operations defined in clk.h: · 73 unmodified lines
7474 long (*determine_rate)(struct clk_hw *hw,
7575 unsigned long rate,
7676 unsigned long *best_parent_rate,
77− struct clk **best_parent_clk);
77+ struct clk_hw **best_parent_clk);
7878 int (*set_parent)(struct clk_hw *hw, u8 index);
7979 u8 (*get_parent)(struct clk_hw *hw);
8080 int (*set_rate)(struct clk_hw *hw,
Documentation/cpu-freq/intel-pstate.txt+25−12
@@ -1,17 +1,28 @@
11 Intel P-state driver
22 --------------------
33
4−This driver implements a scaling driver with an internal governor for
5−Intel Core processors. The driver follows the same model as the
6−Transmeta scaling driver (longrun.c) and implements the setpolicy()
7−instead of target(). Scaling drivers that implement setpolicy() are
8−assumed to implement internal governors by the cpufreq core. All the
9−logic for selecting the current P state is contained within the
10−driver; no external governor is used by the cpufreq core.
11−
12−Intel SandyBridge+ processors are supported.
13−
14−New sysfs files for controlling P state selection have been added to
4+This driver provides an interface to control the P state selection for
5+SandyBridge+ Intel processors. The driver can operate two different
6+modes based on the processor model legacy and Hardware P state (HWP)
7+mode.
8+
9+In legacy mode the driver implements a scaling driver with an internal
10+governor for Intel Core processors. The driver follows the same model
11+as the Transmeta scaling driver (longrun.c) and implements the
12+setpolicy() instead of target(). Scaling drivers that implement
13+setpolicy() are assumed to implement internal governors by the cpufreq
14+core. All the logic for selecting the current P state is contained
15+within the driver; no external governor is used by the cpufreq core.
16+
17+In HWP mode P state selection is implemented in the processor
18+itself. The driver provides the interfaces between the cpufreq core and
19+the processor to control P state selection based on user preferences
20+and reporting frequency to the cpufreq core. In this mode the
21+internal governor code is disabled.
22+
23+In addtion to the interfaces provided by the cpufreq core for
24+controlling frequency the driver provides sysfs files for
25+controlling P state selection. These files have been added to
1526 /sys/devices/system/cpu/intel_pstate/
1627
1728 max_perf_pct: limits the maximum P state that will be requested by
@@ -33,7 +44,9 @@ frequency is fiction for Intel Core processors. Even if the scaling · 15 unmodified lines
3344 driver selects a single P state the actual frequency the processor
3445 will run at is selected by the processor itself.
3546
36−New debugfs files have also been added to /sys/kernel/debug/pstate_snb/
47+For legacy mode debugfs files have also been added to allow tuning of
48+the internal governor algorythm. These files are located at
49+/sys/kernel/debug/pstate_snb/ These files are NOT present in HWP mode.
3750
3851 deadband
3952 d_gain_pct
Documentation/crypto/crypto-API-userspace.txt+205−0
@@ -0,0 +1,205 @@
1+Introduction
2+============
3+
4+The concepts of the kernel crypto API visible to kernel space is fully
5+applicable to the user space interface as well. Therefore, the kernel crypto API
6+high level discussion for the in-kernel use cases applies here as well.
7+
8+The major difference, however, is that user space can only act as a consumer
9+and never as a provider of a transformation or cipher algorithm.
10+
11+The following covers the user space interface exported by the kernel crypto
12+API. A working example of this description is libkcapi that can be obtained from
13+[1]. That library can be used by user space applications that require
14+cryptographic services from the kernel.
15+
16+Some details of the in-kernel kernel crypto API aspects do not
17+apply to user space, however. This includes the difference between synchronous
18+and asynchronous invocations. The user space API call is fully synchronous.
19+In addition, only a subset of all cipher types are available as documented
20+below.
21+
22+
23+User space API general remarks
24+==============================
25+
26+The kernel crypto API is accessible from user space. Currently, the following
27+ciphers are accessible:
28+
29+ * Message digest including keyed message digest (HMAC, CMAC)
30+
31+ * Symmetric ciphers
32+
33+Note, AEAD ciphers are currently not supported via the symmetric cipher
34+interface.
35+
36+The interface is provided via Netlink using the type AF_ALG. In addition, the
37+setsockopt option type is SOL_ALG. In case the user space header files do not
38+export these flags yet, use the following macros:
39+
40+#ifndef AF_ALG
41+#define AF_ALG 38
42+#endif
43+#ifndef SOL_ALG
44+#define SOL_ALG 279
45+#endif
46+
47+A cipher is accessed with the same name as done for the in-kernel API calls.
48+This includes the generic vs. unique naming schema for ciphers as well as the
49+enforcement of priorities for generic names.
50+
51+To interact with the kernel crypto API, a Netlink socket must be created by
52+the user space application. User space invokes the cipher operation with the
53+send/write system call family. The result of the cipher operation is obtained
54+with the read/recv system call family.
55+
56+The following API calls assume that the Netlink socket descriptor is already
57+opened by the user space application and discusses only the kernel crypto API
58+specific invocations.
59+
60+To initialize a Netlink interface, the following sequence has to be performed
61+by the consumer:
62+
63+ 1. Create a socket of type AF_ALG with the struct sockaddr_alg parameter
64+ specified below for the different cipher types.
65+
66+ 2. Invoke bind with the socket descriptor
67+
68+ 3. Invoke accept with the socket descriptor. The accept system call
69+ returns a new file descriptor that is to be used to interact with
70+ the particular cipher instance. When invoking send/write or recv/read
71+ system calls to send data to the kernel or obtain data from the
72+ kernel, the file descriptor returned by accept must be used.
73+
74+In-place cipher operation
75+=========================
76+
77+Just like the in-kernel operation of the kernel crypto API, the user space
78+interface allows the cipher operation in-place. That means that the input buffer
79+used for the send/write system call and the output buffer used by the read/recv
80+system call may be one and the same. This is of particular interest for
81+symmetric cipher operations where a copying of the output data to its final
82+destination can be avoided.
83+
84+If a consumer on the other hand wants to maintain the plaintext and the
85+ciphertext in different memory locations, all a consumer needs to do is to
86+provide different memory pointers for the encryption and decryption operation.
87+
88+Message digest API
89+==================
90+
91+The message digest type to be used for the cipher operation is selected when
92+invoking the bind syscall. bind requires the caller to provide a filled
93+struct sockaddr data structure. This data structure must be filled as follows:
94+
95+struct sockaddr_alg sa = {
96+ .salg_family = AF_ALG,
97+ .salg_type = "hash", /* this selects the hash logic in the kernel */
98+ .salg_name = "sha1" /* this is the cipher name */
99+};
100+
101+The salg_type value "hash" applies to message digests and keyed message digests.
102+Though, a keyed message digest is referenced by the appropriate salg_name.
103+Please see below for the setsockopt interface that explains how the key can be
104+set for a keyed message digest.
105+
106+Using the send() system call, the application provides the data that should be
107+processed with the message digest. The send system call allows the following
108+flags to be specified:
109+
110+ * MSG_MORE: If this flag is set, the send system call acts like a
111+ message digest update function where the final hash is not
112+ yet calculated. If the flag is not set, the send system call
113+ calculates the final message digest immediately.
114+
115+With the recv() system call, the application can read the message digest from
116+the kernel crypto API. If the buffer is too small for the message digest, the
117+flag MSG_TRUNC is set by the kernel.
118+
119+In order to set a message digest key, the calling application must use the
120+setsockopt() option of ALG_SET_KEY. If the key is not set the HMAC operation is
121+performed without the initial HMAC state change caused by the key.
122+
123+
124+Symmetric cipher API
125+====================
126+
127+The operation is very similar to the message digest discussion. During
128+initialization, the struct sockaddr data structure must be filled as follows:
129+
130+struct sockaddr_alg sa = {
131+ .salg_family = AF_ALG,
132+ .salg_type = "skcipher", /* this selects the symmetric cipher */
133+ .salg_name = "cbc(aes)" /* this is the cipher name */
134+};
135+
136+Before data can be sent to the kernel using the write/send system call family,
137+the consumer must set the key. The key setting is described with the setsockopt
138+invocation below.
139+
140+Using the sendmsg() system call, the application provides the data that should
141+be processed for encryption or decryption. In addition, the IV is specified
142+with the data structure provided by the sendmsg() system call.
143+
144+The sendmsg system call parameter of struct msghdr is embedded into the
145+struct cmsghdr data structure. See recv(2) and cmsg(3) for more information
146+on how the cmsghdr data structure is used together with the send/recv system
147+call family. That cmsghdr data structure holds the following information
148+specified with a separate header instances:
149+
150+ * specification of the cipher operation type with one of these flags:
151+ ALG_OP_ENCRYPT - encryption of data
152+ ALG_OP_DECRYPT - decryption of data
153+
154+ * specification of the IV information marked with the flag ALG_SET_IV
155+
156+The send system call family allows the following flag to be specified:
157+
158+ * MSG_MORE: If this flag is set, the send system call acts like a
159+ cipher update function where more input data is expected
160+ with a subsequent invocation of the send system call.
161+
162+Note: The kernel reports -EINVAL for any unexpected data. The caller must
163+make sure that all data matches the constraints given in /proc/crypto for the
164+selected cipher.
165+
166+With the recv() system call, the application can read the result of the
167+cipher operation from the kernel crypto API. The output buffer must be at least
168+as large as to hold all blocks of the encrypted or decrypted data. If the output
169+data size is smaller, only as many blocks are returned that fit into that
170+output buffer size.
171+
172+Setsockopt interface
173+====================
174+
175+In addition to the read/recv and send/write system call handling to send and
176+retrieve data subject to the cipher operation, a consumer also needs to set
177+the additional information for the cipher operation. This additional information
178+is set using the setsockopt system call that must be invoked with the file
179+descriptor of the open cipher (i.e. the file descriptor returned by the
180+accept system call).
181+
182+Each setsockopt invocation must use the level SOL_ALG.
183+
184+The setsockopt interface allows setting the following data using the mentioned
185+optname:
186+
187+ * ALG_SET_KEY -- Setting the key. Key setting is applicable to:
188+
189+ - the skcipher cipher type (symmetric ciphers)
190+
191+ - the hash cipher type (keyed message digests)
192+
193+User space API example
194+======================
195+
196+Please see [1] for libkcapi which provides an easy-to-use wrapper around the
197+aforementioned Netlink kernel interface. [1] also contains a test application
198+that invokes all libkcapi API calls.
199+
200+[1] http://www.chronox.de/libkcapi.html
201+
202+Author
203+======
204+
205+Stephan Mueller <smueller@chronox.de>
Documentation/development-process/2.Process+0−4
@@ -289,10 +289,6 @@ lists when they are assembled; they can be downloaded from: · 288 unmodified lines
289289
290290 http://www.kernel.org/pub/linux/kernel/next/
291291
292−Some information about linux-next has been gathered at:
293−
294− http://linux.f-seidel.de/linux-next/pmwiki/
295−
296292 Linux-next has become an integral part of the kernel development process;
297293 all patches merged during a given merge window should really have found
298294 their way into linux-next some time before the merge window opens.
Documentation/development-process/8.Conclusion+0−4
@@ -22,10 +22,6 @@ Beyond that, a valuable resource for kernel developers is: · 21 unmodified lines
2222
2323 http://kernelnewbies.org/
2424
25−Information about the linux-next tree gathers at:
26−
27− http://linux.f-seidel.de/linux-next/pmwiki/
28−
2925 And, of course, one should not forget http://kernel.org/, the definitive
3026 location for kernel release information.
3127
Documentation/device-mapper/cache-policies.txt+15−9
@@ -47,20 +47,26 @@ Message and constructor argument pairs are: · 46 unmodified lines
4747 'discard_promote_adjustment <value>'
4848
4949 The sequential threshold indicates the number of contiguous I/Os
50−required before a stream is treated as sequential. The random threshold
50+required before a stream is treated as sequential. Once a stream is
51+considered sequential it will bypass the cache. The random threshold
5152 is the number of intervening non-contiguous I/Os that must be seen
5253 before the stream is treated as random again.
5354
5455 The sequential and random thresholds default to 512 and 4 respectively.
5556
56−Large, sequential ios are probably better left on the origin device
57−since spindles tend to have good bandwidth. The io_tracker counts
58−contiguous I/Os to try to spot when the io is in one of these sequential
59−modes.
60−
61−Internally the mq policy maintains a promotion threshold variable. If
62−the hit count of a block not in the cache goes above this threshold it
63−gets promoted to the cache. The read, write and discard promote adjustment
57+Large, sequential I/Os are probably better left on the origin device
58+since spindles tend to have good sequential I/O bandwidth. The
59+io_tracker counts contiguous I/Os to try to spot when the I/O is in one
60+of these sequential modes. But there are use-cases for wanting to
61+promote sequential blocks to the cache (e.g. fast application startup).
62+If sequential threshold is set to 0 the sequential I/O detection is
63+disabled and sequential I/O will no longer implicitly bypass the cache.
64+Setting the random threshold to 0 does _not_ disable the random I/O
65+stream detection.
66+
67+Internally the mq policy determines a promotion threshold. If the hit
68+count of a block not in the cache goes above this threshold it gets
69+promoted to the cache. The read, write and discard promote adjustment
6470 tunables allow you to tweak the promotion threshold by adding a small
6571 value based on the io type. They default to 4, 8 and 1 respectively.
6672 If you're trying to quickly warm a new cache device you may wish to
Documentation/devicetree/bindings/arm/altera/socfpga-sdram-edac.txt+15−0
@@ -0,0 +1,15 @@
1+Altera SOCFPGA SDRAM Error Detection & Correction [EDAC]
2+The EDAC accesses a range of registers in the SDRAM controller.
3+
4+Required properties:
5+- compatible : should contain "altr,sdram-edac";
6+- altr,sdr-syscon : phandle of the sdr module
7+- interrupts : Should contain the SDRAM ECC IRQ in the
8+ appropriate format for the IRQ controller.
9+
10+Example:
11+ sdramedac {
12+ compatible = "altr,sdram-edac";
13+ altr,sdr-syscon = <&sdr>;
14+ interrupts = <0 39 4>;
15+ };
Documentation/devicetree/bindings/arm/amlogic.txt+10−0
@@ -0,0 +1,10 @@
1+Amlogic MesonX device tree bindings
2+-------------------------------------------
3+
4+Boards with the Amlogic Meson6 SoC shall have the following properties:
5+ Required root node property:
6+ compatible: "amlogic,meson6"
7+
8+Boards with the Amlogic Meson8 SoC shall have the following properties:
9+ Required root node property:
10+ compatible: "amlogic,meson8";
Documentation/devicetree/bindings/arm/arch_timer.txt+8−0
@@ -22,6 +22,14 @@ to deliver its interrupts via SPIs. · 21 unmodified lines
2222 - always-on : a boolean property. If present, the timer is powered through an
2323 always-on power domain, therefore it never loses context.
2424
25+** Optional properties:
26+
27+- arm,cpu-registers-not-fw-configured : Firmware does not initialize
28+ any of the generic timer CPU registers, which contain their
29+ architecturally-defined reset values. Only supported for 32-bit
30+ systems which follow the ARMv7 architected reset values.
31+
32+
2533 Example:
2634
2735 timer {
Documentation/devicetree/bindings/arm/arm-boards+65−0
@@ -92,3 +92,68 @@ Required nodes: · 91 unmodified lines
9292 - core-module: the root node to the Versatile platforms must have
9393 a core-module with regs and the compatible strings
9494 "arm,core-module-versatile", "syscon"
95+
96+ARM RealView Boards
97+-------------------
98+The RealView boards cover tailored evaluation boards that are used to explore
99+the ARM11 and Cortex A-8 and Cortex A-9 processors.
100+
101+Required properties (in root node):
102+ /* RealView Emulation Baseboard */
103+ compatible = "arm,realview-eb";
104+ /* RealView Platform Baseboard for ARM1176JZF-S */
105+ compatible = "arm,realview-pb1176";
106+ /* RealView Platform Baseboard for ARM11 MPCore */
107+ compatible = "arm,realview-pb11mp";
108+ /* RealView Platform Baseboard for Cortex A-8 */
109+ compatible = "arm,realview-pba8";
110+ /* RealView Platform Baseboard Explore for Cortex A-9 */
111+ compatible = "arm,realview-pbx";
112+
113+Required nodes:
114+
115+- soc: some node of the RealView platforms must be the SoC
116+ node that contain the SoC-specific devices, withe the compatible
117+ string set to one of these tuples:
118+ "arm,realview-eb-soc", "simple-bus"
119+ "arm,realview-pb1176-soc", "simple-bus"
120+ "arm,realview-pb11mp-soc", "simple-bus"
121+ "arm,realview-pba8-soc", "simple-bus"
122+ "arm,realview-pbx-soc", "simple-bus"
123+
124+- syscon: some subnode of the RealView SoC node must be a
125+ system controller node pointing to the control registers,
126+ with the compatible string set to one of these tuples:
127+ "arm,realview-eb-syscon", "syscon"
128+ "arm,realview-pb1176-syscon", "syscon"
129+ "arm,realview-pb11mp-syscon", "syscon"
130+ "arm,realview-pba8-syscon", "syscon"
131+ "arm,realview-pbx-syscon", "syscon"
132+
133+ Required properties for the system controller:
134+ - regs: the location and size of the system controller registers,
135+ one range of 0x1000 bytes.
136+
137+Example:
138+
139+/dts-v1/;
140+#include <dt-bindings/interrupt-controller/irq.h>
141+#include "skeleton.dtsi"
142+
143+/ {
144+ model = "ARM RealView PB1176 with device tree";
145+ compatible = "arm,realview-pb1176";
146+
147+ soc {
148+ #address-cells = <1>;
149+ #size-cells = <1>;
150+ compatible = "arm,realview-pb1176-soc", "simple-bus";
151+ ranges;
152+
153+ syscon: syscon@10000000 {
154+ compatible = "arm,realview-syscon", "syscon";
155+ reg = <0x10000000 0x1000>;
156+ };
157+
158+ };
159+};
Documentation/devicetree/bindings/arm/atmel-at91.txt+38−7
@@ -1,6 +1,43 @@
11 Atmel AT91 device tree bindings.
22 ================================
33
4+Boards with a SoC of the Atmel AT91 or SMART family shall have the following
5+properties:
6+
7+Required root node properties:
8+compatible: must be one of:
9+ * "atmel,at91rm9200"
10+
11+ * "atmel,at91sam9" for SoCs using an ARM926EJ-S core, shall be extended with
12+ the specific SoC family or compatible:
13+ o "atmel,at91sam9260"
14+ o "atmel,at91sam9261"
15+ o "atmel,at91sam9263"
16+ o "atmel,at91sam9x5" for the 5 series, shall be extended with the specific
17+ SoC compatible:
18+ - "atmel,at91sam9g15"
19+ - "atmel,at91sam9g25"
20+ - "atmel,at91sam9g35"
21+ - "atmel,at91sam9x25"
22+ - "atmel,at91sam9x35"
23+ o "atmel,at91sam9g20"
24+ o "atmel,at91sam9g45"
25+ o "atmel,at91sam9n12"
26+ o "atmel,at91sam9rl"
27+ * "atmel,sama5" for SoCs using a Cortex-A5, shall be extended with the specific
28+ SoC family:
29+ o "atmel,sama5d3" shall be extended with the specific SoC compatible:
30+ - "atmel,sama5d31"
31+ - "atmel,sama5d33"
32+ - "atmel,sama5d34"
33+ - "atmel,sama5d35"
34+ - "atmel,sama5d36"
35+ o "atmel,sama5d4" shall be extended with the specific SoC compatible:
36+ - "atmel,sama5d41"
37+ - "atmel,sama5d42"
38+ - "atmel,sama5d43"
39+ - "atmel,sama5d44"
40+
441 PIT Timer required properties:
542 - compatible: Should be "atmel,at91sam9260-pit"
643 - reg: Should contain registers location and length
@@ -61,8 +98,8 @@ RAMC SDRAM/DDR Controller required properties: · 54 unmodified lines
6198 - compatible: Should be "atmel,at91rm9200-sdramc",
6299 "atmel,at91sam9260-sdramc",
63100 "atmel,at91sam9g45-ddramc",
101+ "atmel,sama5d3-ddramc",
64102 - reg: Should contain registers location and length
65− For at91sam9263 and at91sam9g45 you must specify 2 entries.
66103
67104 Examples:
68105
@@ -71,12 +108,6 @@ Examples: · 2 unmodified lines
71108 reg = <0xffffe800 0x200>;
72109 };
73110
74− ramc0: ramc@ffffe400 {
75− compatible = "atmel,at91sam9g45-ddramc";
76− reg = <0xffffe400 0x200
77− 0xffffe600 0x200>;
78− };
79−
80111 SHDWC Shutdown Controller
81112
82113 required properties:
Documentation/devicetree/bindings/arm/bcm/bcm63138.txt+9−0
@@ -0,0 +1,9 @@
1+Broadcom BCM63138 DSL System-on-a-Chip device tree bindings
2+-----------------------------------------------------------
3+
4+Boards compatible with the BCM63138 DSL System-on-a-Chip should have the
5+following properties:
6+
7+Required root node property:
8+
9+compatible: should be "brcm,bcm63138"
Documentation/devicetree/bindings/arm/bcm/cygnus.txt+31−0
@@ -0,0 +1,31 @@
1+Broadcom Cygnus device tree bindings
2+------------------------------------
3+
4+
5+Boards with Cygnus SoCs shall have the following properties:
6+
7+Required root node property:
8+
9+BCM11300
10+compatible = "brcm,bcm11300", "brcm,cygnus";
11+
12+BCM11320
13+compatible = "brcm,bcm11320", "brcm,cygnus";
14+
15+BCM11350
16+compatible = "brcm,bcm11350", "brcm,cygnus";
17+
18+BCM11360
19+compatible = "brcm,bcm11360", "brcm,cygnus";
20+
21+BCM58300
22+compatible = "brcm,bcm58300", "brcm,cygnus";
23+
24+BCM58302
25+compatible = "brcm,bcm58302", "brcm,cygnus";
26+
27+BCM58303
28+compatible = "brcm,bcm58303", "brcm,cygnus";
29+
30+BCM58305
31+compatible = "brcm,bcm58305", "brcm,cygnus";
Documentation/devicetree/bindings/arm/cavium-thunder.txt+10−0
@@ -0,0 +1,10 @@
1+Cavium Thunder platform device tree bindings
2+--------------------------------------------
3+
4+Boards with Cavium's Thunder SoC shall have following properties.
5+
6+Root Node
7+---------
8+Required root node properties:
9+
10+ - compatible = "cavium,thunder-88xx";
Documentation/devicetree/bindings/arm/coresight.txt+204−0
@@ -0,0 +1,204 @@
1+* CoreSight Components:
2+
3+CoreSight components are compliant with the ARM CoreSight architecture
4+specification and can be connected in various topologies to suit a particular
5+SoCs tracing needs. These trace components can generally be classified as
6+sinks, links and sources. Trace data produced by one or more sources flows
7+through the intermediate links connecting the source to the currently selected
8+sink. Each CoreSight component device should use these properties to describe
9+its hardware characteristcs.
10+
11+* Required properties for all components *except* non-configurable replicators:
12+
13+ * compatible: These have to be supplemented with "arm,primecell" as
14+ drivers are using the AMBA bus interface. Possible values include:
15+ - "arm,coresight-etb10", "arm,primecell";
16+ - "arm,coresight-tpiu", "arm,primecell";
17+ - "arm,coresight-tmc", "arm,primecell";
18+ - "arm,coresight-funnel", "arm,primecell";
19+ - "arm,coresight-etm3x", "arm,primecell";
20+
21+ * reg: physical base address and length of the register
22+ set(s) of the component.
23+
24+ * clocks: the clock associated to this component.
25+
26+ * clock-names: the name of the clock as referenced by the code.
27+ Since we are using the AMBA framework, the name should be
28+ "apb_pclk".
29+
30+ * port or ports: The representation of the component's port
31+ layout using the generic DT graph presentation found in
32+ "bindings/graph.txt".
33+
34+* Required properties for devices that don't show up on the AMBA bus, such as
35+ non-configurable replicators:
36+
37+ * compatible: Currently supported value is (note the absence of the
38+ AMBA markee):
39+ - "arm,coresight-replicator"
40+
41+ * id: a unique number that will identify this replicator.
42+
43+ * port or ports: same as above.
44+
45+* Optional properties for ETM/PTMs:
46+
47+ * arm,cp14: must be present if the system accesses ETM/PTM management
48+ registers via co-processor 14.
49+
50+ * cpu: the cpu phandle this ETM/PTM is affined to. When omitted the
51+ source is considered to belong to CPU0.
52+
53+* Optional property for TMC:
54+
55+ * arm,buffer-size: size of contiguous buffer space for TMC ETR
56+ (embedded trace router)
57+
58+
59+Example:
60+
61+1. Sinks
62+ etb@20010000 {
63+ compatible = "arm,coresight-etb10", "arm,primecell";
64+ reg = <0 0x20010000 0 0x1000>;
65+
66+ coresight-default-sink;
67+ clocks = <&oscclk6a>;
68+ clock-names = "apb_pclk";
69+ port {
70+ etb_in_port: endpoint@0 {
71+ slave-mode;
72+ remote-endpoint = <&replicator_out_port0>;
73+ };
74+ };
75+ };
76+
77+ tpiu@20030000 {
78+ compatible = "arm,coresight-tpiu", "arm,primecell";
79+ reg = <0 0x20030000 0 0x1000>;
80+
81+ clocks = <&oscclk6a>;
82+ clock-names = "apb_pclk";
83+ port {
84+ tpiu_in_port: endpoint@0 {
85+ slave-mode;
86+ remote-endpoint = <&replicator_out_port1>;
87+ };
88+ };
89+ };
90+
91+2. Links
92+ replicator {
93+ /* non-configurable replicators don't show up on the
94+ * AMBA bus. As such no need to add "arm,primecell".
95+ */
96+ compatible = "arm,coresight-replicator";
97+ /* this will show up in debugfs as "0.replicator" */
98+ id = <0>;
99+
100+ ports {
101+ #address-cells = <1>;
102+ #size-cells = <0>;
103+
104+ /* replicator output ports */
105+ port@0 {
106+ reg = <0>;
107+ replicator_out_port0: endpoint {
108+ remote-endpoint = <&etb_in_port>;
109+ };
110+ };
111+
112+ port@1 {
113+ reg = <1>;
114+ replicator_out_port1: endpoint {
115+ remote-endpoint = <&tpiu_in_port>;
116+ };
117+ };
118+
119+ /* replicator input port */
120+ port@2 {
121+ reg = <0>;
122+ replicator_in_port0: endpoint {
123+ slave-mode;
124+ remote-endpoint = <&funnel_out_port0>;
125+ };
126+ };
127+ };
128+ };
129+
130+ funnel@20040000 {
131+ compatible = "arm,coresight-funnel", "arm,primecell";
132+ reg = <0 0x20040000 0 0x1000>;
133+
134+ clocks = <&oscclk6a>;
135+ clock-names = "apb_pclk";
136+ ports {
137+ #address-cells = <1>;
138+ #size-cells = <0>;
139+
140+ /* funnel output port */
141+ port@0 {
142+ reg = <0>;
143+ funnel_out_port0: endpoint {
144+ remote-endpoint =
145+ <&replicator_in_port0>;
146+ };
147+ };
148+
149+ /* funnel input ports */
150+ port@1 {
151+ reg = <0>;
152+ funnel_in_port0: endpoint {
153+ slave-mode;
154+ remote-endpoint = <&ptm0_out_port>;
155+ };
156+ };
157+
158+ port@2 {
159+ reg = <1>;
160+ funnel_in_port1: endpoint {
161+ slave-mode;
162+ remote-endpoint = <&ptm1_out_port>;
163+ };
164+ };
165+
166+ port@3 {
167+ reg = <2>;
168+ funnel_in_port2: endpoint {
169+ slave-mode;
170+ remote-endpoint = <&etm0_out_port>;
171+ };
172+ };
173+
174+ };
175+ };
176+
177+3. Sources
178+ ptm@2201c000 {
179+ compatible = "arm,coresight-etm3x", "arm,primecell";
180+ reg = <0 0x2201c000 0 0x1000>;
181+
182+ cpu = <&cpu0>;
183+ clocks = <&oscclk6a>;
184+ clock-names = "apb_pclk";
185+ port {
186+ ptm0_out_port: endpoint {
187+ remote-endpoint = <&funnel_in_port0>;
188+ };
189+ };
190+ };
191+
192+ ptm@2201d000 {
193+ compatible = "arm,coresight-etm3x", "arm,primecell";
194+ reg = <0 0x2201d000 0 0x1000>;
195+
196+ cpu = <&cpu1>;
197+ clocks = <&oscclk6a>;
198+ clock-names = "apb_pclk";
199+ port {
200+ ptm1_out_port: endpoint {
201+ remote-endpoint = <&funnel_in_port1>;
202+ };
203+ };
204+ };
Documentation/devicetree/bindings/arm/cpus.txt+18−0
@@ -166,6 +166,7 @@ nodes to be present and contain the properties described below. · 165 unmodified lines
166166 "arm,cortex-r5"
167167 "arm,cortex-r7"
168168 "brcm,brahma-b15"
169+ "cavium,thunder"
169170 "faraday,fa526"
170171 "intel,sa110"
171172 "intel,sa1100"
@@ -219,6 +220,21 @@ nodes to be present and contain the properties described below. · 47 unmodified lines
219220 Value type: <phandle>
220221 Definition: Specifies the ACC[2] node associated with this CPU.
221222
223+ - cpu-idle-states
224+ Usage: Optional
225+ Value type: <prop-encoded-array>
226+ Definition:
227+ # List of phandles to idle state nodes supported
228+ by this cpu [3].
229+
230+ - rockchip,pmu
231+ Usage: optional for systems that have an "enable-method"
232+ property value of "rockchip,rk3066-smp"
233+ While optional, it is the preferred way to get access to
234+ the cpu-core power-domains.
235+ Value type: <phandle>
236+ Definition: Specifies the syscon node controlling the cpu core
237+ power domains.
222238
223239 Example 1 (dual-cluster big.LITTLE system 32-bit):
224240
@@ -415,3 +431,5 @@ cpus { · 190 unmodified lines
415431 --
416432 [1] arm/msm/qcom,saw2.txt
417433 [2] arm/msm/qcom,kpss-acc.txt
434+[3] ARM Linux kernel documentation - idle states bindings
435+ Documentation/devicetree/bindings/arm/idle-states.txt
Documentation/devicetree/bindings/arm/exynos/power_domain.txt+6−7
@@ -8,6 +8,8 @@ Required Properties: · 7 unmodified lines
88 * samsung,exynos4210-pd - for exynos4210 type power domain.
99 - reg: physical base address of the controller and length of memory mapped
1010 region.
11+- #power-domain-cells: number of cells in power domain specifier;
12+ must be 0.
1113
1214 Optional Properties:
1315 - clocks: List of clock handles. The parent clocks of the input clocks to the
@@ -29,6 +31,7 @@ Example: · 15 unmodified lines
2931 lcd0: power-domain-lcd0 {
3032 compatible = "samsung,exynos4210-pd";
3133 reg = <0x10023C00 0x10>;
34+ #power-domain-cells = <0>;
3235 };
3336
3437 mfc_pd: power-domain@10044060 {
@@ -37,12 +40,8 @@ Example: · 2 unmodified lines
3740 clocks = <&clock CLK_FIN_PLL>, <&clock CLK_MOUT_SW_ACLK333>,
3841 <&clock CLK_MOUT_USER_ACLK333>;
3942 clock-names = "oscclk", "pclk0", "clk0";
43+ #power-domain-cells = <0>;
4044 };
4145
42−Example of the node using power domain:
43−
44− node {
45− /* ... */
46− samsung,power-domain = <&lcd0>;
47− /* ... */
48− };
46+See Documentation/devicetree/bindings/power/power_domain.txt for description
47+of consumer-side bindings.
Documentation/devicetree/bindings/arm/fsl.txt+38−0
@@ -74,3 +74,41 @@ Required root node properties: · 73 unmodified lines
7474 i.MX6q generic board
7575 Required root node properties:
7676 - compatible = "fsl,imx6q";
77+
78+
79+Freescale LS1021A Platform Device Tree Bindings
80+------------------------------------------------
81+
82+Required root node compatible properties:
83+ - compatible = "fsl,ls1021a";
84+
85+Freescale LS1021A SoC-specific Device Tree Bindings
86+-------------------------------------------
87+
88+Freescale SCFG
89+ SCFG is the supplemental configuration unit, that provides SoC specific
90+configuration and status registers for the chip. Such as getting PEX port
91+status.
92+ Required properties:
93+ - compatible: should be "fsl,ls1021a-scfg"
94+ - reg: should contain base address and length of SCFG memory-mapped registers
95+
96+Example:
97+ scfg: scfg@1570000 {
98+ compatible = "fsl,ls1021a-scfg";
99+ reg = <0x0 0x1570000 0x0 0x10000>;
100+ };
101+
102+Freescale DCFG
103+ DCFG is the device configuration unit, that provides general purpose
104+configuration and status for the device. Such as setting the secondary
105+core start address and release the secondary core from holdoff and startup.
106+ Required properties:
107+ - compatible: should be "fsl,ls1021a-dcfg"
108+ - reg : should contain base address and length of DCFG memory-mapped registers
109+
110+Example:
111+ dcfg: dcfg@1ee0000 {
112+ compatible = "fsl,ls1021a-dcfg";
113+ reg = <0x0 0x1ee0000 0x0 0x10000>;
114+ };
Documentation/devicetree/bindings/arm/geniatech.txt+5−0
@@ -0,0 +1,5 @@
1+Geniatech platforms device tree bindings
2+-------------------------------------------
3+
4+Geniatech ATV1200
5+ - compatible = "geniatech,atv1200"
Documentation/devicetree/bindings/arm/gic-v3.txt+39−0
@@ -49,11 +49,29 @@ Optional · 48 unmodified lines
4949 occupied by the redistributors. Required if more than one such
5050 region is present.
5151
52+Sub-nodes:
53+
54+GICv3 has one or more Interrupt Translation Services (ITS) that are
55+used to route Message Signalled Interrupts (MSI) to the CPUs.
56+
57+These nodes must have the following properties:
58+- compatible : Should at least contain "arm,gic-v3-its".
59+- msi-controller : Boolean property. Identifies the node as an MSI controller
60+- reg: Specifies the base physical address and size of the ITS
61+ registers.
62+
63+The main GIC node must contain the appropriate #address-cells,
64+#size-cells and ranges properties for the reg property of all ITS
65+nodes.
66+
5267 Examples:
5368
5469 gic: interrupt-controller@2cf00000 {
5570 compatible = "arm,gic-v3";
5671 #interrupt-cells = <3>;
72+ #address-cells = <2>;
73+ #size-cells = <2>;
74+ ranges;
5775 interrupt-controller;
5876 reg = <0x0 0x2f000000 0 0x10000>, // GICD
5977 <0x0 0x2f100000 0 0x200000>, // GICR
@@ -61,11 +79,20 @@ Examples: · 1 unmodified line
6179 <0x0 0x2c010000 0 0x2000>, // GICH
6280 <0x0 0x2c020000 0 0x2000>; // GICV
6381 interrupts = <1 9 4>;
82+
83+ gic-its@2c200000 {
84+ compatible = "arm,gic-v3-its";
85+ msi-controller;
86+ reg = <0x0 0x2c200000 0 0x200000>;
87+ };
6488 };
6589
6690 gic: interrupt-controller@2c010000 {
6791 compatible = "arm,gic-v3";
6892 #interrupt-cells = <3>;
93+ #address-cells = <2>;
94+ #size-cells = <2>;
95+ ranges;
6996 interrupt-controller;
7097 redistributor-stride = <0x0 0x40000>; // 256kB stride
7198 #redistributor-regions = <2>;
@@ -76,4 +103,16 @@ Examples: · 4 unmodified lines
76103 <0x0 0x2c060000 0 0x2000>, // GICH
77104 <0x0 0x2c080000 0 0x2000>; // GICV
78105 interrupts = <1 9 4>;
106+
107+ gic-its@2c200000 {
108+ compatible = "arm,gic-v3-its";
109+ msi-controller;
110+ reg = <0x0 0x2c200000 0 0x200000>;
111+ };
112+
113+ gic-its@2c400000 {
114+ compatible = "arm,gic-v3-its";
115+ msi-controller;
116+ reg = <0x0 0x2c400000 0 0x200000>;
117+ };
79118 };
Documentation/devicetree/bindings/arm/gic.txt+54−0
@@ -17,6 +17,7 @@ Main node required properties: · 16 unmodified lines
1717 "arm,cortex-a7-gic"
1818 "arm,arm11mp-gic"
1919 "brcm,brahma-b15-gic"
20+ "arm,arm1176jzf-devchip-gic"
2021 - interrupt-controller : Identifies the node as an interrupt controller
2122 - #interrupt-cells : Specifies the number of cells needed to encode an
2223 interrupt source. The type shall be a <u32> and the value shall be 3.
@@ -96,3 +97,56 @@ Example: · 73 unmodified lines
9697 <0x2c006000 0x2000>;
9798 interrupts = <1 9 0xf04>;
9899 };
100+
101+
102+* GICv2m extension for MSI/MSI-x support (Optional)
103+
104+Certain revisions of GIC-400 supports MSI/MSI-x via V2M register frame(s).
105+This is enabled by specifying v2m sub-node(s).
106+
107+Required properties:
108+
109+- compatible : The value here should contain "arm,gic-v2m-frame".
110+
111+- msi-controller : Identifies the node as an MSI controller.
112+
113+- reg : GICv2m MSI interface register base and size
114+
115+Optional properties:
116+
117+- arm,msi-base-spi : When the MSI_TYPER register contains an incorrect
118+ value, this property should contain the SPI base of
119+ the MSI frame, overriding the HW value.
120+
121+- arm,msi-num-spis : When the MSI_TYPER register contains an incorrect
122+ value, this property should contain the number of
123+ SPIs assigned to the frame, overriding the HW value.
124+
125+Example:
126+
127+ interrupt-controller@e1101000 {
128+ compatible = "arm,gic-400";
129+ #interrupt-cells = <3>;
130+ #address-cells = <2>;
131+ #size-cells = <2>;
132+ interrupt-controller;
133+ interrupts = <1 8 0xf04>;
134+ ranges = <0 0 0 0xe1100000 0 0x100000>;
135+ reg = <0x0 0xe1110000 0 0x01000>,
136+ <0x0 0xe112f000 0 0x02000>,
137+ <0x0 0xe1140000 0 0x10000>,
138+ <0x0 0xe1160000 0 0x10000>;
139+ v2m0: v2m@0x8000 {
140+ compatible = "arm,gic-v2m-frame";
141+ msi-controller;
142+ reg = <0x0 0x80000 0 0x1000>;
143+ };
144+
145+ ....
146+
147+ v2mN: v2m@0x9000 {
148+ compatible = "arm,gic-v2m-frame";
149+ msi-controller;
150+ reg = <0x0 0x90000 0 0x1000>;
151+ };
152+ };
Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt+23−0
@@ -5,6 +5,11 @@ Hi4511 Board · 4 unmodified lines
55 Required root node properties:
66 - compatible = "hisilicon,hi3620-hi4511";
77
8+HiP04 D01 Board
9+Required root node properties:
10+ - compatible = "hisilicon,hip04-d01";
11+
12+
813 Hisilicon system controller
914
1015 Required properties:
@@ -55,3 +60,21 @@ Example: · 44 unmodified lines
5560 compatible = "hisilicon,pctrl";
5661 reg = <0xfca09000 0x1000>;
5762 };
63+
64+-----------------------------------------------------------------------
65+Fabric:
66+
67+Required Properties:
68+- compatible: "hisilicon,hip04-fabric";
69+- reg: Address and size of Fabric
70+
71+-----------------------------------------------------------------------
72+Bootwrapper boot method (software protocol on SMP):
73+
74+Required Properties:
75+- compatible: "hisilicon,hip04-bootwrapper";
76+- boot-method: Address and size of boot method.
77+ [0]: bootwrapper physical address
78+ [1]: bootwrapper size
79+ [2]: relocation physical address
80+ [3]: relocation size
Documentation/devicetree/bindings/arm/idle-states.txt+699−0
@@ -0,0 +1,699 @@
1+==========================================
2+ARM idle states binding description
3+==========================================
4+
5+==========================================
6+1 - Introduction
7+==========================================
8+
9+ARM systems contain HW capable of managing power consumption dynamically,
10+where cores can be put in different low-power states (ranging from simple
11+wfi to power gating) according to OS PM policies. The CPU states representing
12+the range of dynamic idle states that a processor can enter at run-time, can be
13+specified through device tree bindings representing the parameters required
14+to enter/exit specific idle states on a given processor.
15+
16+According to the Server Base System Architecture document (SBSA, [3]), the
17+power states an ARM CPU can be put into are identified by the following list:
18+
19+- Running
20+- Idle_standby
21+- Idle_retention
22+- Sleep
23+- Off
24+
25+The power states described in the SBSA document define the basic CPU states on
26+top of which ARM platforms implement power management schemes that allow an OS
27+PM implementation to put the processor in different idle states (which include
28+states listed above; "off" state is not an idle state since it does not have
29+wake-up capabilities, hence it is not considered in this document).
30+
31+Idle state parameters (eg entry latency) are platform specific and need to be
32+characterized with bindings that provide the required information to OS PM
33+code so that it can build the required tables and use them at runtime.
34+
35+The device tree binding definition for ARM idle states is the subject of this
36+document.
37+
38+===========================================
39+2 - idle-states definitions
40+===========================================
41+
42+Idle states are characterized for a specific system through a set of
43+timing and energy related properties, that underline the HW behaviour
44+triggered upon idle states entry and exit.
45+
46+The following diagram depicts the CPU execution phases and related timing
47+properties required to enter and exit an idle state:
48+
49+..__[EXEC]__|__[PREP]__|__[ENTRY]__|__[IDLE]__|__[EXIT]__|__[EXEC]__..
50+ | | | | |
51+
52+ |<------ entry ------->|
53+ | latency |
54+ |<- exit ->|
55+ | latency |
56+ |<-------- min-residency -------->|
57+ |<------- wakeup-latency ------->|
58+
59+ Diagram 1: CPU idle state execution phases
60+
61+EXEC: Normal CPU execution.
62+
63+PREP: Preparation phase before committing the hardware to idle mode
64+ like cache flushing. This is abortable on pending wake-up
65+ event conditions. The abort latency is assumed to be negligible
66+ (i.e. less than the ENTRY + EXIT duration). If aborted, CPU
67+ goes back to EXEC. This phase is optional. If not abortable,
68+ this should be included in the ENTRY phase instead.
69+
70+ENTRY: The hardware is committed to idle mode. This period must run
71+ to completion up to IDLE before anything else can happen.
72+
73+IDLE: This is the actual energy-saving idle period. This may last
74+ between 0 and infinite time, until a wake-up event occurs.
75+
76+EXIT: Period during which the CPU is brought back to operational
77+ mode (EXEC).
78+
79+entry-latency: Worst case latency required to enter the idle state. The
80+exit-latency may be guaranteed only after entry-latency has passed.
81+
82+min-residency: Minimum period, including preparation and entry, for a given
83+idle state to be worthwhile energywise.
84+
85+wakeup-latency: Maximum delay between the signaling of a wake-up event and the
86+CPU being able to execute normal code again. If not specified, this is assumed
87+to be entry-latency + exit-latency.
88+
89+These timing parameters can be used by an OS in different circumstances.
90+
91+An idle CPU requires the expected min-residency time to select the most
92+appropriate idle state based on the expected expiry time of the next IRQ
93+(ie wake-up) that causes the CPU to return to the EXEC phase.
94+
95+An operating system scheduler may need to compute the shortest wake-up delay
96+for CPUs in the system by detecting how long will it take to get a CPU out
97+of an idle state, eg:
98+
99+wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0)
100+
101+In other words, the scheduler can make its scheduling decision by selecting
102+(eg waking-up) the CPU with the shortest wake-up latency.
103+The wake-up latency must take into account the entry latency if that period
104+has not expired. The abortable nature of the PREP period can be ignored
105+if it cannot be relied upon (e.g. the PREP deadline may occur much sooner than
106+the worst case since it depends on the CPU operating conditions, ie caches
107+state).
108+
109+An OS has to reliably probe the wakeup-latency since some devices can enforce
110+latency constraints guarantees to work properly, so the OS has to detect the
111+worst case wake-up latency it can incur if a CPU is allowed to enter an
112+idle state, and possibly to prevent that to guarantee reliable device
113+functioning.
114+
115+The min-residency time parameter deserves further explanation since it is
116+expressed in time units but must factor in energy consumption coefficients.
117+
118+The energy consumption of a cpu when it enters a power state can be roughly
119+characterised by the following graph:
120+
121+ |
122+ |
123+ |
124+ e |
125+ n | /---
126+ e | /------
127+ r | /------
128+ g | /-----
129+ y | /------
130+ | ----
131+ | /|
132+ | / |
133+ | / |
134+ | / |
135+ | / |
136+ | / |
137+ |/ |
138+ -----|-------+----------------------------------
139+ 0| 1 time(ms)
140+
141+ Graph 1: Energy vs time example
142+
143+The graph is split in two parts delimited by time 1ms on the X-axis.
144+The graph curve with X-axis values = { x | 0 < x < 1ms } has a steep slope
145+and denotes the energy costs incurred whilst entering and leaving the idle
146+state.
147+The graph curve in the area delimited by X-axis values = {x | x > 1ms } has
148+shallower slope and essentially represents the energy consumption of the idle
149+state.
150+
151+min-residency is defined for a given idle state as the minimum expected
152+residency time for a state (inclusive of preparation and entry) after
153+which choosing that state become the most energy efficient option. A good
154+way to visualise this, is by taking the same graph above and comparing some
155+states energy consumptions plots.
156+
157+For sake of simplicity, let's consider a system with two idle states IDLE1,
158+and IDLE2:
159+
160+ |
161+ |
162+ |
163+ | /-- IDLE1
164+ e | /---
165+ n | /----
166+ e | /---
167+ r | /-----/--------- IDLE2
168+ g | /-------/---------
169+ y | ------------ /---|
170+ | / /---- |
171+ | / /--- |
172+ | / /---- |
173+ | / /--- |
174+ | --- |
175+ | / |
176+ | / |
177+ |/ | time
178+ ---/----------------------------+------------------------
179+ |IDLE1-energy < IDLE2-energy | IDLE2-energy < IDLE1-energy
180+ |
181+ IDLE2-min-residency
182+
183+ Graph 2: idle states min-residency example
184+
185+In graph 2 above, that takes into account idle states entry/exit energy
186+costs, it is clear that if the idle state residency time (ie time till next
187+wake-up IRQ) is less than IDLE2-min-residency, IDLE1 is the better idle state
188+choice energywise.
189+
190+This is mainly down to the fact that IDLE1 entry/exit energy costs are lower
191+than IDLE2.
192+
193+However, the lower power consumption (ie shallower energy curve slope) of idle
194+state IDLE2 implies that after a suitable time, IDLE2 becomes more energy
195+efficient.
196+
197+The time at which IDLE2 becomes more energy efficient than IDLE1 (and other
198+shallower states in a system with multiple idle states) is defined
199+IDLE2-min-residency and corresponds to the time when energy consumption of
200+IDLE1 and IDLE2 states breaks even.
201+
202+The definitions provided in this section underpin the idle states
203+properties specification that is the subject of the following sections.
204+
205+===========================================
206+3 - idle-states node
207+===========================================
208+
209+ARM processor idle states are defined within the idle-states node, which is
210+a direct child of the cpus node [1] and provides a container where the
211+processor idle states, defined as device tree nodes, are listed.
212+
213+- idle-states node
214+
215+ Usage: Optional - On ARM systems, it is a container of processor idle
216+ states nodes. If the system does not provide CPU
217+ power management capabilities or the processor just
218+ supports idle_standby an idle-states node is not
219+ required.
220+
221+ Description: idle-states node is a container node, where its
222+ subnodes describe the CPU idle states.
223+
224+ Node name must be "idle-states".
225+
226+ The idle-states node's parent node must be the cpus node.
227+
228+ The idle-states node's child nodes can be:
229+
230+ - one or more state nodes
231+
232+ Any other configuration is considered invalid.
233+
234+ An idle-states node defines the following properties:
235+
236+ - entry-method
237+ Value type: <stringlist>
238+ Usage and definition depend on ARM architecture version.
239+ # On ARM v8 64-bit this property is required and must
240+ be one of:
241+ - "psci" (see bindings in [2])
242+ # On ARM 32-bit systems this property is optional
243+
244+The nodes describing the idle states (state) can only be defined within the
245+idle-states node, any other configuration is considered invalid and therefore
246+must be ignored.
247+
248+===========================================
249+4 - state node
250+===========================================
251+
252+A state node represents an idle state description and must be defined as
253+follows:
254+
255+- state node
256+
257+ Description: must be child of the idle-states node
258+
259+ The state node name shall follow standard device tree naming
260+ rules ([5], 2.2.1 "Node names"), in particular state nodes which
261+ are siblings within a single common parent must be given a unique name.
262+
263+ The idle state entered by executing the wfi instruction (idle_standby
264+ SBSA,[3][4]) is considered standard on all ARM platforms and therefore
265+ must not be listed.
266+
267+ With the definitions provided above, the following list represents
268+ the valid properties for a state node:
269+
270+ - compatible
271+ Usage: Required
272+ Value type: <stringlist>
273+ Definition: Must be "arm,idle-state".
274+
275+ - local-timer-stop
276+ Usage: See definition
277+ Value type: <none>
278+ Definition: if present the CPU local timer control logic is
279+ lost on state entry, otherwise it is retained.
280+
281+ - entry-latency-us
282+ Usage: Required
283+ Value type: <prop-encoded-array>
284+ Definition: u32 value representing worst case latency in
285+ microseconds required to enter the idle state.
286+ The exit-latency-us duration may be guaranteed
287+ only after entry-latency-us has passed.
288+
289+ - exit-latency-us
290+ Usage: Required
291+ Value type: <prop-encoded-array>
292+ Definition: u32 value representing worst case latency
293+ in microseconds required to exit the idle state.
294+
295+ - min-residency-us
296+ Usage: Required
297+ Value type: <prop-encoded-array>
298+ Definition: u32 value representing minimum residency duration
299+ in microseconds, inclusive of preparation and
300+ entry, for this idle state to be considered
301+ worthwhile energy wise (refer to section 2 of
302+ this document for a complete description).
303+
304+ - wakeup-latency-us:
305+ Usage: Optional
306+ Value type: <prop-encoded-array>
307+ Definition: u32 value representing maximum delay between the
308+ signaling of a wake-up event and the CPU being
309+ able to execute normal code again. If omitted,
310+ this is assumed to be equal to:
311+
312+ entry-latency-us + exit-latency-us
313+
314+ It is important to supply this value on systems
315+ where the duration of PREP phase (see diagram 1,
316+ section 2) is non-neglibigle.
317+ In such systems entry-latency-us + exit-latency-us
318+ will exceed wakeup-latency-us by this duration.
319+
320+ - status:
321+ Usage: Optional
322+ Value type: <string>
323+ Definition: A standard device tree property [5] that indicates
324+ the operational status of an idle-state.
325+ If present, it shall be:
326+ "okay": to indicate that the idle state is
327+ operational.
328+ "disabled": to indicate that the idle state has
329+ been disabled in firmware so it is not
330+ operational.
331+ If the property is not present the idle-state must
332+ be considered operational.
333+
334+ - idle-state-name:
335+ Usage: Optional
336+ Value type: <string>
337+ Definition: A string used as a descriptive name for the idle
338+ state.
339+
340+ In addition to the properties listed above, a state node may require
341+ additional properties specifics to the entry-method defined in the
342+ idle-states node, please refer to the entry-method bindings
343+ documentation for properties definitions.
344+
345+===========================================
346+4 - Examples
347+===========================================
348+
349+Example 1 (ARM 64-bit, 16-cpu system, PSCI enable-method):
350+
351+cpus {
352+ #size-cells = <0>;
353+ #address-cells = <2>;
354+
355+ CPU0: cpu@0 {
356+ device_type = "cpu";
357+ compatible = "arm,cortex-a57";
358+ reg = <0x0 0x0>;
359+ enable-method = "psci";
360+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
361+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
362+ };
363+
364+ CPU1: cpu@1 {
365+ device_type = "cpu";
366+ compatible = "arm,cortex-a57";
367+ reg = <0x0 0x1>;
368+ enable-method = "psci";
369+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
370+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
371+ };
372+
373+ CPU2: cpu@100 {
374+ device_type = "cpu";
375+ compatible = "arm,cortex-a57";
376+ reg = <0x0 0x100>;
377+ enable-method = "psci";
378+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
379+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
380+ };
381+
382+ CPU3: cpu@101 {
383+ device_type = "cpu";
384+ compatible = "arm,cortex-a57";
385+ reg = <0x0 0x101>;
386+ enable-method = "psci";
387+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
388+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
389+ };
390+
391+ CPU4: cpu@10000 {
392+ device_type = "cpu";
393+ compatible = "arm,cortex-a57";
394+ reg = <0x0 0x10000>;
395+ enable-method = "psci";
396+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
397+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
398+ };
399+
400+ CPU5: cpu@10001 {
401+ device_type = "cpu";
402+ compatible = "arm,cortex-a57";
403+ reg = <0x0 0x10001>;
404+ enable-method = "psci";
405+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
406+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
407+ };
408+
409+ CPU6: cpu@10100 {
410+ device_type = "cpu";
411+ compatible = "arm,cortex-a57";
412+ reg = <0x0 0x10100>;
413+ enable-method = "psci";
414+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
415+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
416+ };
417+
418+ CPU7: cpu@10101 {
419+ device_type = "cpu";
420+ compatible = "arm,cortex-a57";
421+ reg = <0x0 0x10101>;
422+ enable-method = "psci";
423+ cpu-idle-states = <&CPU_RETENTION_0_0 &CPU_SLEEP_0_0
424+ &CLUSTER_RETENTION_0 &CLUSTER_SLEEP_0>;
425+ };
426+
427+ CPU8: cpu@100000000 {
428+ device_type = "cpu";
429+ compatible = "arm,cortex-a53";
430+ reg = <0x1 0x0>;
431+ enable-method = "psci";
432+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
433+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
434+ };
435+
436+ CPU9: cpu@100000001 {
437+ device_type = "cpu";
438+ compatible = "arm,cortex-a53";
439+ reg = <0x1 0x1>;
440+ enable-method = "psci";
441+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
442+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
443+ };
444+
445+ CPU10: cpu@100000100 {
446+ device_type = "cpu";
447+ compatible = "arm,cortex-a53";
448+ reg = <0x1 0x100>;
449+ enable-method = "psci";
450+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
451+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
452+ };
453+
454+ CPU11: cpu@100000101 {
455+ device_type = "cpu";
456+ compatible = "arm,cortex-a53";
457+ reg = <0x1 0x101>;
458+ enable-method = "psci";
459+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
460+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
461+ };
462+
463+ CPU12: cpu@100010000 {
464+ device_type = "cpu";
465+ compatible = "arm,cortex-a53";
466+ reg = <0x1 0x10000>;
467+ enable-method = "psci";
468+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
469+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
470+ };
471+
472+ CPU13: cpu@100010001 {
473+ device_type = "cpu";
474+ compatible = "arm,cortex-a53";
475+ reg = <0x1 0x10001>;
476+ enable-method = "psci";
477+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
478+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
479+ };
480+
481+ CPU14: cpu@100010100 {
482+ device_type = "cpu";
483+ compatible = "arm,cortex-a53";
484+ reg = <0x1 0x10100>;
485+ enable-method = "psci";
486+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
487+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
488+ };
489+
490+ CPU15: cpu@100010101 {
491+ device_type = "cpu";
492+ compatible = "arm,cortex-a53";
493+ reg = <0x1 0x10101>;
494+ enable-method = "psci";
495+ cpu-idle-states = <&CPU_RETENTION_1_0 &CPU_SLEEP_1_0
496+ &CLUSTER_RETENTION_1 &CLUSTER_SLEEP_1>;
497+ };
498+
499+ idle-states {
500+ entry-method = "arm,psci";
501+
502+ CPU_RETENTION_0_0: cpu-retention-0-0 {
503+ compatible = "arm,idle-state";
504+ arm,psci-suspend-param = <0x0010000>;
505+ entry-latency-us = <20>;
506+ exit-latency-us = <40>;
507+ min-residency-us = <80>;
508+ };
509+
510+ CLUSTER_RETENTION_0: cluster-retention-0 {
511+ compatible = "arm,idle-state";
512+ local-timer-stop;
513+ arm,psci-suspend-param = <0x1010000>;
514+ entry-latency-us = <50>;
515+ exit-latency-us = <100>;
516+ min-residency-us = <250>;
517+ wakeup-latency-us = <130>;
518+ };
519+
520+ CPU_SLEEP_0_0: cpu-sleep-0-0 {
521+ compatible = "arm,idle-state";
522+ local-timer-stop;
523+ arm,psci-suspend-param = <0x0010000>;
524+ entry-latency-us = <250>;
525+ exit-latency-us = <500>;
526+ min-residency-us = <950>;
527+ };
528+
529+ CLUSTER_SLEEP_0: cluster-sleep-0 {
530+ compatible = "arm,idle-state";
531+ local-timer-stop;
532+ arm,psci-suspend-param = <0x1010000>;
533+ entry-latency-us = <600>;
534+ exit-latency-us = <1100>;
535+ min-residency-us = <2700>;
536+ wakeup-latency-us = <1500>;
537+ };
538+
539+ CPU_RETENTION_1_0: cpu-retention-1-0 {
540+ compatible = "arm,idle-state";
541+ arm,psci-suspend-param = <0x0010000>;
542+ entry-latency-us = <20>;
543+ exit-latency-us = <40>;
544+ min-residency-us = <90>;
545+ };
546+
547+ CLUSTER_RETENTION_1: cluster-retention-1 {
548+ compatible = "arm,idle-state";
549+ local-timer-stop;
550+ arm,psci-suspend-param = <0x1010000>;
551+ entry-latency-us = <50>;
552+ exit-latency-us = <100>;
553+ min-residency-us = <270>;
554+ wakeup-latency-us = <100>;
555+ };
556+
557+ CPU_SLEEP_1_0: cpu-sleep-1-0 {
558+ compatible = "arm,idle-state";
559+ local-timer-stop;
560+ arm,psci-suspend-param = <0x0010000>;
561+ entry-latency-us = <70>;
562+ exit-latency-us = <100>;
563+ min-residency-us = <300>;
564+ wakeup-latency-us = <150>;
565+ };
566+
567+ CLUSTER_SLEEP_1: cluster-sleep-1 {
568+ compatible = "arm,idle-state";
569+ local-timer-stop;
570+ arm,psci-suspend-param = <0x1010000>;
571+ entry-latency-us = <500>;
572+ exit-latency-us = <1200>;
573+ min-residency-us = <3500>;
574+ wakeup-latency-us = <1300>;
575+ };
576+ };
577+
578+};
579+
580+Example 2 (ARM 32-bit, 8-cpu system, two clusters):
581+
582+cpus {
583+ #size-cells = <0>;
584+ #address-cells = <1>;
585+
586+ CPU0: cpu@0 {
587+ device_type = "cpu";
588+ compatible = "arm,cortex-a15";
589+ reg = <0x0>;
590+ cpu-idle-states = <&CPU_SLEEP_0_0 &CLUSTER_SLEEP_0>;
591+ };
592+
593+ CPU1: cpu@1 {
594+ device_type = "cpu";
595+ compatible = "arm,cortex-a15";
596+ reg = <0x1>;
597+ cpu-idle-states = <&CPU_SLEEP_0_0 &CLUSTER_SLEEP_0>;
598+ };
599+
600+ CPU2: cpu@2 {
601+ device_type = "cpu";
602+ compatible = "arm,cortex-a15";
603+ reg = <0x2>;
604+ cpu-idle-states = <&CPU_SLEEP_0_0 &CLUSTER_SLEEP_0>;
605+ };
606+
607+ CPU3: cpu@3 {
608+ device_type = "cpu";
609+ compatible = "arm,cortex-a15";
610+ reg = <0x3>;
611+ cpu-idle-states = <&CPU_SLEEP_0_0 &CLUSTER_SLEEP_0>;
612+ };
613+
614+ CPU4: cpu@100 {
615+ device_type = "cpu";
616+ compatible = "arm,cortex-a7";
617+ reg = <0x100>;
618+ cpu-idle-states = <&CPU_SLEEP_1_0 &CLUSTER_SLEEP_1>;
619+ };
620+
621+ CPU5: cpu@101 {
622+ device_type = "cpu";
623+ compatible = "arm,cortex-a7";
624+ reg = <0x101>;
625+ cpu-idle-states = <&CPU_SLEEP_1_0 &CLUSTER_SLEEP_1>;
626+ };
627+
628+ CPU6: cpu@102 {
629+ device_type = "cpu";
630+ compatible = "arm,cortex-a7";
631+ reg = <0x102>;
632+ cpu-idle-states = <&CPU_SLEEP_1_0 &CLUSTER_SLEEP_1>;
633+ };
634+
635+ CPU7: cpu@103 {
636+ device_type = "cpu";
637+ compatible = "arm,cortex-a7";
638+ reg = <0x103>;
639+ cpu-idle-states = <&CPU_SLEEP_1_0 &CLUSTER_SLEEP_1>;
640+ };
641+
642+ idle-states {
643+ CPU_SLEEP_0_0: cpu-sleep-0-0 {
644+ compatible = "arm,idle-state";
645+ local-timer-stop;
646+ entry-latency-us = <200>;
647+ exit-latency-us = <100>;
648+ min-residency-us = <400>;
649+ wakeup-latency-us = <250>;
650+ };
651+
652+ CLUSTER_SLEEP_0: cluster-sleep-0 {
653+ compatible = "arm,idle-state";
654+ local-timer-stop;
655+ entry-latency-us = <500>;
656+ exit-latency-us = <1500>;
657+ min-residency-us = <2500>;
658+ wakeup-latency-us = <1700>;
659+ };
660+
661+ CPU_SLEEP_1_0: cpu-sleep-1-0 {
662+ compatible = "arm,idle-state";
663+ local-timer-stop;
664+ entry-latency-us = <300>;
665+ exit-latency-us = <500>;
666+ min-residency-us = <900>;
667+ wakeup-latency-us = <600>;
668+ };
669+
670+ CLUSTER_SLEEP_1: cluster-sleep-1 {
671+ compatible = "arm,idle-state";
672+ local-timer-stop;
673+ entry-latency-us = <800>;
674+ exit-latency-us = <2000>;
675+ min-residency-us = <6500>;
676+ wakeup-latency-us = <2300>;
677+ };
678+ };
679+
680+};
681+
682+===========================================
683+5 - References
684+===========================================
685+
686+[1] ARM Linux Kernel documentation - CPUs bindings
687+ Documentation/devicetree/bindings/arm/cpus.txt
688+
689+[2] ARM Linux Kernel documentation - PSCI bindings
690+ Documentation/devicetree/bindings/arm/psci.txt
691+
692+[3] ARM Server Base System Architecture (SBSA)
693+ http://infocenter.arm.com/help/index.jsp
694+
695+[4] ARM Architecture Reference Manuals
696+ http://infocenter.arm.com/help/index.jsp
697+
698+[5] ePAPR standard
699+ https://www.power.org/documentation/epapr-version-1-1/
Documentation/devicetree/bindings/arm/l2cc.txt+10−0
@@ -2,6 +2,10 @@ · 1 unmodified line
22
33 ARM cores often have a separate level 2 cache controller. There are various
44 implementations of the L2 cache controller with compatible programming models.
5+Some of the properties that are just prefixed "cache-*" are taken from section
6+3.7.3 of the ePAPR v1.1 specification which can be found at:
7+https://www.power.org/wp-content/uploads/2012/06/Power_ePAPR_APPROVED_v1.1.pdf
8+
59 The ARM L2 cache representation in the device tree should be done as follows:
610
711 Required properties:
@@ -44,6 +48,12 @@ Optional properties: · 36 unmodified lines
4448 I/O coherent mode. Valid only when the arm,pl310-cache compatible
4549 string is used.
4650 - interrupts : 1 combined interrupt.
51+- cache-size : specifies the size in bytes of the cache
52+- cache-sets : specifies the number of associativity sets of the cache
53+- cache-block-size : specifies the size in bytes of a cache block
54+- cache-line-size : specifies the size in bytes of a line in the cache,
55+ if this is not specified, the line size is assumed to be equal to the
56+ cache block size
4757 - cache-id-part: cache id part number to be used if it is not present
4858 on hardware
4959 - wt-override: If present then L2 is forced to Write through mode
Documentation/devicetree/bindings/arm/marvell,berlin.txt+10−0
@@ -106,11 +106,21 @@ Required subnode-properties: · 105 unmodified lines
106106 - groups: a list of strings describing the group names.
107107 - function: a string describing the function used to mux the groups.
108108
109+* Reset controller binding
110+
111+A reset controller is part of the chip control registers set. The chip control
112+node also provides the reset. The register set is not at the same offset between
113+Berlin SoCs.
114+
115+Required property:
116+- #reset-cells: must be set to 2
117+
109118 Example:
110119
111120 chip: chip-control@ea0000 {
112121 compatible = "marvell,berlin2-chip-ctrl";
113122 #clock-cells = <1>;
123+ #reset-cells = <2>;
114124 reg = <0xea0000 0x400>;
115125 clocks = <&refclk>, <&externaldev 0>;
116126 clock-names = "refclk", "video_ext0";
Documentation/devicetree/bindings/arm/mediatek.txt+22−3
@@ -1,8 +1,27 @@
1−Mediatek MT6589 Platforms Device Tree Bindings
1+MediaTek mt65xx & mt81xx Platforms Device Tree Bindings
22
3−Boards with a SoC of the Mediatek MT6589 shall have the following property:
3+Boards with a MediaTek mt65xx/mt81xx SoC shall have the following property:
44
55 Required root node property:
66
7−compatible: must contain "mediatek,mt6589"
7+compatible: Must contain one of
8+ "mediatek,mt6589"
9+ "mediatek,mt6592"
10+ "mediatek,mt8127"
11+ "mediatek,mt8135"
812
13+
14+Supported boards:
15+
16+- bq Aquaris5 smart phone:
17+ Required root node properties:
18+ - compatible = "mundoreader,bq-aquaris5", "mediatek,mt6589";
19+- Evaluation board for MT6592:
20+ Required root node properties:
21+ - compatible = "mediatek,mt6592-evb", "mediatek,mt6592";
22+- MTK mt8127 tablet moose EVB:
23+ Required root node properties:
24+ - compatible = "mediatek,mt8127-moose", "mediatek,mt8127";
25+- MTK mt8135 tablet EVB:
26+ Required root node properties:
27+ - compatible = "mediatek,mt8135-evbp1", "mediatek,mt8135";
Documentation/devicetree/bindings/arm/mediatek/mediatek,sysirq.txt+28−0
@@ -0,0 +1,28 @@
1+Mediatek 65xx/81xx sysirq
2+
3+Mediatek SOCs sysirq support controllable irq inverter for each GIC SPI
4+interrupt.
5+
6+Required properties:
7+- compatible: should be one of:
8+ "mediatek,mt8135-sysirq"
9+ "mediatek,mt8127-sysirq"
10+ "mediatek,mt6589-sysirq"
11+ "mediatek,mt6582-sysirq"
12+ "mediatek,mt6577-sysirq"
13+- interrupt-controller : Identifies the node as an interrupt controller
14+- #interrupt-cells : Use the same format as specified by GIC in
15+ Documentation/devicetree/bindings/arm/gic.txt
16+- interrupt-parent: phandle of irq parent for sysirq. The parent must
17+ use the same interrupt-cells format as GIC.
18+- reg: Physical base address of the intpol registers and length of memory
19+ mapped region.
20+
21+Example:
22+ sysirq: interrupt-controller@10200100 {
23+ compatible = "mediatek,mt6589-sysirq", "mediatek,mt6577-sysirq";
24+ interrupt-controller;
25+ #interrupt-cells = <3>;
26+ interrupt-parent = <&gic>;
27+ reg = <0 0x10200100 0 0x1c>;
28+ };
Documentation/devicetree/bindings/arm/omap/mpu.txt+3−0
@@ -10,6 +10,9 @@ Required properties: · 9 unmodified lines
1010 Should be "ti,omap5-mpu" for OMAP5
1111 - ti,hwmods: "mpu"
1212
13+Optional properties:
14+- sram: Phandle to the ocmcram node
15+
1316 Examples:
1417
1518 - For an OMAP5 SMP system:
Documentation/devicetree/bindings/arm/omap/omap.txt+15−0
@@ -85,6 +85,18 @@ SoCs: · 84 unmodified lines
8585 - DRA722
8686 compatible = "ti,dra722", "ti,dra72", "ti,dra7"
8787
88+- AM5728
89+ compatible = "ti,am5728", "ti,dra742", "ti,dra74", "ti,dra7"
90+
91+- AM5726
92+ compatible = "ti,am5726", "ti,dra742", "ti,dra74", "ti,dra7"
93+
94+- AM5718
95+ compatible = "ti,am5718", "ti,dra722", "ti,dra72", "ti,dra7"
96+
97+- AM5716
98+ compatible = "ti,am5716", "ti,dra722", "ti,dra72", "ti,dra7"
99+
88100 - AM4372
89101 compatible = "ti,am4372", "ti,am43"
90102
@@ -120,6 +132,9 @@ Boards: · 29 unmodified lines
120132 - AM335X Bone : Low cost community board
121133 compatible = "ti,am335x-bone", "ti,am33xx", "ti,omap3"
122134
135+- AM335X OrionLXm : Substation Automation Platform
136+ compatible = "novatech,am335x-lxm", "ti,am33xx"
137+
123138 - OMAP5 EVM : Evaluation Module
124139 compatible = "ti,omap5-evm", "ti,omap5"
125140
Documentation/devicetree/bindings/arm/psci.txt+13−1
@@ -50,6 +50,16 @@ Main node optional properties: · 49 unmodified lines
5050
5151 - migrate : Function ID for MIGRATE operation
5252
53+Device tree nodes that require usage of PSCI CPU_SUSPEND function (ie idle
54+state nodes, as per bindings in [1]) must specify the following properties:
55+
56+- arm,psci-suspend-param
57+ Usage: Required for state nodes[1] if the corresponding
58+ idle-states node entry-method property is set
59+ to "psci".
60+ Value type: <u32>
61+ Definition: power_state parameter to pass to the PSCI
62+ suspend call.
5363
5464 Example:
5565
@@ -64,7 +74,6 @@ Case 1: PSCI v0.1 only. · 8 unmodified lines
6474 migrate = <0x95c10003>;
6575 };
6676
67−
6877 Case 2: PSCI v0.2 only
6978
7079 psci {
@@ -88,3 +97,6 @@ Case 3: PSCI v0.2 and PSCI v0.1. · 17 unmodified lines
8897
8998 ...
9099 };
100+
101+[1] Kernel documentation - ARM idle states bindings
102+ Documentation/devicetree/bindings/arm/idle-states.txt
Documentation/devicetree/bindings/arm/rockchip.txt+4−0
@@ -1,6 +1,10 @@
11 Rockchip platforms device tree bindings
22 ---------------------------------------
33
4+- MarsBoard RK3066 board:
5+ Required root node properties:
6+ - compatible = "haoyu,marsboard-rk3066", "rockchip,rk3066a";
7+
48 - bq Curie 2 tablet:
59 Required root node properties:
610 - compatible = "mundoreader,bq-curie2", "rockchip,rk3066a";
Documentation/devicetree/bindings/arm/samsung-boards.txt+14−5
@@ -1,11 +1,20 @@
1−* Samsung's Exynos4210 based SMDKV310 evaluation board
2−
3−SMDKV310 evaluation board is based on Samsung's Exynos4210 SoC.
1+* Samsung's Exynos SoC based boards
42
53 Required root node properties:
64 - compatible = should be one or more of the following.
7− (a) "samsung,smdkv310" - for Samsung's SMDKV310 eval board.
8− (b) "samsung,exynos4210" - for boards based on Exynos4210 SoC.
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.
918
1019 Optional:
1120 - firmware node, specifying presence and type of secure firmware:
Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt+24−5
@@ -11,13 +11,27 @@ New driver handles the following · 10 unmodified lines
1111
1212 Required properties:
1313 - compatible: Must be "samsung,exynos-adc-v1"
14− for exynos4412/5250 controllers.
14+ for exynos4412/5250 and s5pv210 controllers.
1515 Must be "samsung,exynos-adc-v2" for
1616 future controllers.
1717 Must be "samsung,exynos3250-adc" for
1818 controllers compatible with ADC of Exynos3250.
19−- reg: Contains ADC register address range (base address and
20− length) and the address of the phy enable register.
19+ Must be "samsung,exynos7-adc" for
20+ the ADC in Exynos7 and compatibles
21+ Must be "samsung,s3c2410-adc" for
22+ the ADC in s3c2410 and compatibles
23+ Must be "samsung,s3c2416-adc" for
24+ the ADC in s3c2416 and compatibles
25+ Must be "samsung,s3c2440-adc" for
26+ the ADC in s3c2440 and compatibles
27+ Must be "samsung,s3c2443-adc" for
28+ the ADC in s3c2443 and compatibles
29+ Must be "samsung,s3c6410-adc" for
30+ the ADC in s3c6410 and compatibles
31+- reg: List of ADC register address range
32+ - The base address and range of ADC register
33+ - The base address and range of ADC_PHY register (every
34+ SoC except for s3c24xx/s3c64xx ADC)
2135 - interrupts: Contains the interrupt information for the timer. The
2236 format is being dependent on which interrupt controller
2337 the Samsung device uses.
@@ -31,13 +45,16 @@ Required properties: · 7 unmodified lines
3145 compatible ADC block)
3246 - vdd-supply VDD input supply.
3347
48+- samsung,syscon-phandle Contains the PMU system controller node
49+ (To access the ADC_PHY register on Exynos5250/5420/5800/3250)
50+
3451 Note: child nodes can be added for auto probing from device tree.
3552
3653 Example: adding device info in dtsi file
3754
3855 adc: adc@12D10000 {
3956 compatible = "samsung,exynos-adc-v1";
40− reg = <0x12D10000 0x100>, <0x10040718 0x4>;
57+ reg = <0x12D10000 0x100>;
4158 interrupts = <0 106 0>;
4259 #io-channel-cells = <1>;
4360 io-channel-ranges;
@@ -46,13 +63,14 @@ adc: adc@12D10000 { · 2 unmodified lines
4663 clock-names = "adc";
4764
4865 vdd-supply = <&buck5_reg>;
66+ samsung,syscon-phandle = <&pmu_system_controller>;
4967 };
5068
5169 Example: adding device info in dtsi file for Exynos3250 with additional sclk
5270
5371 adc: adc@126C0000 {
5472 compatible = "samsung,exynos3250-adc", "samsung,exynos-adc-v2;
55− reg = <0x126C0000 0x100>, <0x10020718 0x4>;
73+ reg = <0x126C0000 0x100>;
5674 interrupts = <0 137 0>;
5775 #io-channel-cells = <1>;
5876 io-channel-ranges;
@@ -61,6 +79,7 @@ adc: adc@126C0000 { · 2 unmodified lines
6179 clock-names = "adc", "sclk";
6280
6381 vdd-supply = <&buck5_reg>;
82+ samsung,syscon-phandle = <&pmu_system_controller>;
6483 };
6584
6685 Example: Adding child nodes in dts file
Documentation/devicetree/bindings/arm/shmobile.txt+71−0
@@ -0,0 +1,71 @@
1+Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
2+--------------------------------------------------------------------
3+
4+SoCs:
5+
6+ - Emma Mobile EV2
7+ compatible = "renesas,emev2"
8+ - RZ/A1H (R7S72100)
9+ compatible = "renesas,r7s72100"
10+ - SH-Mobile AP4 (R8A73720/SH7372)
11+ compatible = "renesas,sh7372"
12+ - SH-Mobile AG5 (R8A73A00/SH73A0)
13+ compatible = "renesas,sh73a0"
14+ - R-Mobile APE6 (R8A73A40)
15+ compatible = "renesas,r8a73a4"
16+ - R-Mobile A1 (R8A77400)
17+ compatible = "renesas,r8a7740"
18+ - R-Car M1A (R8A77781)
19+ compatible = "renesas,r8a7778"
20+ - R-Car H1 (R8A77790)
21+ compatible = "renesas,r8a7779"
22+ - R-Car H2 (R8A77900)
23+ compatible = "renesas,r8a7790"
24+ - R-Car M2-W (R8A77910)
25+ compatible = "renesas,r8a7791"
26+ - R-Car V2H (R8A77920)
27+ compatible = "renesas,r8a7792"
28+ - R-Car M2-N (R8A77930)
29+ compatible = "renesas,r8a7793"
30+ - R-Car E2 (R8A77940)
31+ compatible = "renesas,r8a7794"
32+
33+
34+Boards:
35+
36+ - Alt
37+ compatible = "renesas,alt", "renesas,r8a7794"
38+ - APE6-EVM
39+ compatible = "renesas,ape6evm", "renesas,r8a73a4"
40+ - APE6-EVM - Reference Device Tree Implementation
41+ compatible = "renesas,ape6evm-reference", "renesas,r8a73a4"
42+ - Atmark Techno Armadillo-800 EVA
43+ compatible = "renesas,armadillo800eva"
44+ - BOCK-W
45+ compatible = "renesas,bockw", "renesas,r8a7778"
46+ - BOCK-W - Reference Device Tree Implementation
47+ compatible = "renesas,bockw-reference", "renesas,r8a7778"
48+ - Genmai (RTK772100BC00000BR)
49+ compatible = "renesas,genmai", "renesas,r7s72100"
50+ - Gose
51+ compatible = "renesas,gose", "renesas,r8a7793"
52+ - Henninger
53+ compatible = "renesas,henninger", "renesas,r8a7791"
54+ - Koelsch (RTP0RC7791SEB00010S)
55+ compatible = "renesas,koelsch", "renesas,r8a7791"
56+ - Kyoto Microcomputer Co. KZM-A9-Dual
57+ compatible = "renesas,kzm9d", "renesas,emev2"
58+ - Kyoto Microcomputer Co. KZM-A9-GT
59+ compatible = "renesas,kzm9g", "renesas,sh73a0"
60+ - Kyoto Microcomputer Co. KZM-A9-GT - Reference Device Tree Implementation
61+ compatible = "renesas,kzm9g-reference", "renesas,sh73a0"
62+ - Lager (RTP0RC7790SEB00010S)
63+ compatible = "renesas,lager", "renesas,r8a7790"
64+ - Mackerel (R0P7372LC0016RL, AP4 EVM 2nd)
65+ compatible = "renesas,mackerel"
66+ - Marzen
67+ compatible = "renesas,marzen", "renesas,r8a7779"
68+
69+Note: Reference Device Tree Implementations are temporary implementations
70+ to ease the migration from platform devices to Device Tree, and are
71+ intended to be removed in the future.
Documentation/devicetree/bindings/arm/ste-nomadik.txt+6−0
@@ -10,6 +10,12 @@ Required root node property: src · 9 unmodified lines
1010
1111 Boards with the Nomadik SoC include:
1212
13+Nomadik NHK-15 board manufactured by ST Microelectronics:
14+
15+Required root node property:
16+
17+compatible="st,nomadik-nhk-15";
18+
1319 S8815 "MiniKit" manufactured by Calao Systems:
1420
1521 Required root node property:
Documentation/devicetree/bindings/arm/sunxi.txt+12−0
@@ -0,0 +1,12 @@
1+Allwinner sunXi Platforms Device Tree Bindings
2+
3+Each device tree must specify which Allwinner SoC it uses,
4+using one of the following compatible strings:
5+
6+ allwinner,sun4i-a10
7+ allwinner,sun5i-a10s
8+ allwinner,sun5i-a13
9+ allwinner,sun6i-a31
10+ allwinner,sun7i-a20
11+ allwinner,sun8i-a23
12+ allwinner,sun9i-a80
Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-flowctrl.txt+12−0
@@ -0,0 +1,12 @@
1+NVIDIA Tegra Flow Controller
2+
3+Required properties:
4+- compatible: Should be "nvidia,tegra<chip>-flowctrl"
5+- reg: Should contain one register range (address and length)
6+
7+Example:
8+
9+ flow-controller@60007000 {
10+ compatible = "nvidia,tegra20-flowctrl";
11+ reg = <0x60007000 0x1000>;
12+ };
Documentation/devicetree/bindings/arm/ux500/power_domain.txt+35−0
@@ -0,0 +1,35 @@
1+* ST-Ericsson UX500 PM Domains
2+
3+UX500 supports multiple PM domains which are used to gate power to one or
4+more peripherals on the SOC.
5+
6+The implementation of PM domains for UX500 are based upon the generic PM domain
7+and use the corresponding DT bindings.
8+
9+==PM domain providers==
10+
11+Required properties:
12+ - compatible: Must be "stericsson,ux500-pm-domains".
13+ - #power-domain-cells : Number of cells in a power domain specifier, must be 1.
14+
15+Example:
16+ pm_domains: pm_domains0 {
17+ compatible = "stericsson,ux500-pm-domains";
18+ #power-domain-cells = <1>;
19+ };
20+
21+==PM domain consumers==
22+
23+Required properties:
24+ - power-domains: A phandle and PM domain specifier. Below are the list of
25+ valid specifiers:
26+
27+ Index Specifier
28+ ----- ---------
29+ 0 DOMAIN_VAPE
30+
31+Example:
32+ sdi0_per1@80126000 {
33+ compatible = "arm,pl18x", "arm,primecell";
34+ power-domains = <&pm_domains DOMAIN_VAPE>
35+ };
Documentation/devicetree/bindings/ata/marvell.txt+6−0
@@ -6,11 +6,17 @@ Required Properties: · 5 unmodified lines
66 - interrupts : Interrupt controller is using
77 - nr-ports : Number of SATA ports in use.
88
9+Optional Properties:
10+- phys : List of phandles to sata phys
11+- phy-names : Should be "0", "1", etc, one number per phandle
12+
913 Example:
1014
1115 sata@80000 {
1216 compatible = "marvell,orion-sata";
1317 reg = <0x80000 0x5000>;
1418 interrupts = <21>;
19+ phys = <&sata_phy0>, <&sata_phy1>;
20+ phy-names = "0", "1";
1521 nr-ports = <2>;
1622 }
Documentation/devicetree/bindings/ata/qcom-sata.txt+48−0
@@ -0,0 +1,48 @@
1+* Qualcomm AHCI SATA Controller
2+
3+SATA nodes are defined to describe on-chip Serial ATA controllers.
4+Each SATA controller should have its own node.
5+
6+Required properties:
7+- compatible : compatible list, must contain "generic-ahci"
8+- interrupts : <interrupt mapping for SATA IRQ>
9+- reg : <registers mapping>
10+- phys : Must contain exactly one entry as specified
11+ in phy-bindings.txt
12+- phy-names : Must be "sata-phy"
13+
14+Required properties for "qcom,ipq806x-ahci" compatible:
15+- clocks : Must contain an entry for each entry in clock-names.
16+- clock-names : Shall be:
17+ "slave_iface" - Fabric port AHB clock for SATA
18+ "iface" - AHB clock
19+ "core" - core clock
20+ "rxoob" - RX out-of-band clock
21+ "pmalive" - Power Module Alive clock
22+- assigned-clocks : Shall be:
23+ SATA_RXOOB_CLK
24+ SATA_PMALIVE_CLK
25+- assigned-clock-rates : Shall be:
26+ 100Mhz (100000000) for SATA_RXOOB_CLK
27+ 100Mhz (100000000) for SATA_PMALIVE_CLK
28+
29+Example:
30+ sata@29000000 {
31+ compatible = "qcom,ipq806x-ahci", "generic-ahci";
32+ reg = <0x29000000 0x180>;
33+
34+ interrupts = <0 209 0x0>;
35+
36+ clocks = <&gcc SFAB_SATA_S_H_CLK>,
37+ <&gcc SATA_H_CLK>,
38+ <&gcc SATA_A_CLK>,
39+ <&gcc SATA_RXOOB_CLK>,
40+ <&gcc SATA_PMALIVE_CLK>;
41+ clock-names = "slave_iface", "iface", "core",
42+ "rxoob", "pmalive";
43+ assigned-clocks = <&gcc SATA_RXOOB_CLK>, <&gcc SATA_PMALIVE_CLK>;
44+ assigned-clock-rates = <100000000>, <100000000>;
45+
46+ phys = <&sata_phy>;
47+ phy-names = "sata-phy";
48+ };
Documentation/devicetree/bindings/ata/sata_rcar.txt+11−6
@@ -3,16 +3,21 @@ · 2 unmodified lines
33 Required properties:
44 - compatible : should contain one of the following:
55 - "renesas,sata-r8a7779" for R-Car H1
6− - "renesas,sata-r8a7790" for R-Car H2
7− - "renesas,sata-r8a7791" for R-Car M2
6+ ("renesas,rcar-sata" is deprecated)
7+ - "renesas,sata-r8a7790-es1" for R-Car H2 ES1
8+ - "renesas,sata-r8a7790" for R-Car H2 other than ES1
9+ - "renesas,sata-r8a7791" for R-Car M2-W
10+ - "renesas,sata-r8a7793" for R-Car M2-N
811 - reg : address and length of the SATA registers;
912 - interrupts : must consist of one interrupt specifier.
13+- clocks : must contain a reference to the functional clock.
1014
1115 Example:
1216
13−sata: sata@fc600000 {
14− compatible = "renesas,sata-r8a7779";
15− reg = <0xfc600000 0x2000>;
17+sata0: sata@ee300000 {
18+ compatible = "renesas,sata-r8a7791";
19+ reg = <0 0xee300000 0 0x2000>;
1620 interrupt-parent = <&gic>;
17− interrupts = <0 100 IRQ_TYPE_LEVEL_HIGH>;
21+ interrupts = <0 105 IRQ_TYPE_LEVEL_HIGH>;
22+ clocks = <&mstp8_clks R8A7791_CLK_SATA0>;
1823 };
Documentation/devicetree/bindings/btmrvl.txt+29−0
@@ -0,0 +1,29 @@
1+btmrvl
2+------
3+
4+Required properties:
5+
6+ - compatible : must be "btmrvl,cfgdata"
7+
8+Optional properties:
9+
10+ - btmrvl,cal-data : Calibration data downloaded to the device during
11+ initialization. This is an array of 28 values(u8).
12+
13+ - btmrvl,gpio-gap : gpio and gap (in msecs) combination to be
14+ configured.
15+
16+Example:
17+
18+GPIO pin 13 is configured as a wakeup source and GAP is set to 100 msecs
19+in below example.
20+
21+btmrvl {
22+ compatible = "btmrvl,cfgdata";
23+
24+ btmrvl,cal-data = /bits/ 8 <
25+ 0x37 0x01 0x1c 0x00 0xff 0xff 0xff 0xff 0x01 0x7f 0x04 0x02
26+ 0x00 0x00 0xba 0xce 0xc0 0xc6 0x2d 0x00 0x00 0x00 0x00 0x00
27+ 0x00 0x00 0xf0 0x00>;
28+ btmrvl,gpio-gap = <0x0d64>;
29+};
Documentation/devicetree/bindings/bus/bcma.txt+53−0
@@ -0,0 +1,53 @@
1+Driver for ARM AXI Bus with Broadcom Plugins (bcma)
2+
3+Required properties:
4+
5+- compatible : brcm,bus-axi
6+
7+- reg : iomem address range of chipcommon core
8+
9+The cores on the AXI bus are automatically detected by bcma with the
10+memory ranges they are using and they get registered afterwards.
11+Automatic detection of the IRQ number is not working on
12+BCM47xx/BCM53xx ARM SoCs. To assign IRQ numbers to the cores, provide
13+them manually through device tree. Use an interrupt-map to specify the
14+IRQ used by the devices on the bus. The first address is just an index,
15+because we do not have any special register.
16+
17+The top-level axi bus may contain children representing attached cores
18+(devices). This is needed since some hardware details can't be auto
19+detected (e.g. IRQ numbers). Also some of the cores may be responsible
20+for extra things, e.g. ChipCommon providing access to the GPIO chip.
21+
22+Example:
23+
24+ axi@18000000 {
25+ compatible = "brcm,bus-axi";
26+ reg = <0x18000000 0x1000>;
27+ ranges = <0x00000000 0x18000000 0x00100000>;
28+ #address-cells = <1>;
29+ #size-cells = <1>;
30+ #interrupt-cells = <1>;
31+ interrupt-map-mask = <0x000fffff 0xffff>;
32+ interrupt-map =
33+ /* Ethernet Controller 0 */
34+ <0x00024000 0 &gic GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>,
35+
36+ /* Ethernet Controller 1 */
37+ <0x00025000 0 &gic GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>;
38+
39+ /* PCIe Controller 0 */
40+ <0x00012000 0 &gic GIC_SPI 126 IRQ_TYPE_LEVEL_HIGH>,
41+ <0x00012000 1 &gic GIC_SPI 127 IRQ_TYPE_LEVEL_HIGH>,
42+ <0x00012000 2 &gic GIC_SPI 128 IRQ_TYPE_LEVEL_HIGH>,
43+ <0x00012000 3 &gic GIC_SPI 129 IRQ_TYPE_LEVEL_HIGH>,
44+ <0x00012000 4 &gic GIC_SPI 130 IRQ_TYPE_LEVEL_HIGH>,
45+ <0x00012000 5 &gic GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>;
46+
47+ chipcommon {
48+ reg = <0x00000000 0x1000>;
49+
50+ gpio-controller;
51+ #gpio-cells = <2>;
52+ };
53+ };
Documentation/devicetree/bindings/bus/brcm,gisb-arb.txt+5−1
@@ -2,7 +2,11 @@ Broadcom GISB bus Arbiter controller · 1 unmodified line
22
33 Required properties:
44
5−- compatible: should be "brcm,gisb-arb"
5+- compatible:
6+ "brcm,gisb-arb" or "brcm,bcm7445-gisb-arb" for 28nm chips
7+ "brcm,bcm7435-gisb-arb" for newer 40nm chips
8+ "brcm,bcm7400-gisb-arb" for older 40nm chips and all 65nm chips
9+ "brcm,bcm7038-gisb-arb" for 130nm chips
610 - reg: specifies the base physical address and size of the registers
711 - interrupt-parent: specifies the phandle to the parent interrupt controller
812 this arbiter gets interrupt line from
Documentation/devicetree/bindings/bus/mvebu-mbus.txt+10−7
@@ -48,9 +48,12 @@ Required properties: · 47 unmodified lines
4848 - compatible: Should be set to "marvell,mbus-controller".
4949
5050 - reg: Device's register space.
51− Two entries are expected (see the examples below):
52− the first one controls the devices decoding window and
53− the second one controls the SDRAM decoding window.
51+ Two or three entries are expected (see the examples below):
52+ the first one controls the devices decoding window,
53+ the second one controls the SDRAM decoding window and
54+ the third controls the MBus bridge (only with the
55+ marvell,armada370-mbus and marvell,armadaxp-mbus
56+ compatible strings)
5457
5558 Example:
5659
@@ -67,7 +70,7 @@ Example: · 10 unmodified lines
6770
6871 mbusc: mbus-controller@20000 {
6972 compatible = "marvell,mbus-controller";
70− reg = <0x20000 0x100>, <0x20180 0x20>;
73+ reg = <0x20000 0x100>, <0x20180 0x20>, <0x20250 0x8>;
7174 };
7275
7376 /* more children ...*/
@@ -126,7 +129,7 @@ are skipped. · 52 unmodified lines
126129
127130 mbusc: mbus-controller@20000 {
128131 compatible = "marvell,mbus-controller";
129− reg = <0x20000 0x100>, <0x20180 0x20>;
132+ reg = <0x20000 0x100>, <0x20180 0x20>, <0x20250 0x8>;
130133 };
131134
132135 /* more children ...*/
@@ -170,7 +173,7 @@ Using this macro, the above example would be: · 37 unmodified lines
170173
171174 mbusc: mbus-controller@20000 {
172175 compatible = "marvell,mbus-controller";
173− reg = <0x20000 0x100>, <0x20180 0x20>;
176+ reg = <0x20000 0x100>, <0x20180 0x20>, <0x20250 0x8>;
174177 };
175178
176179 /* other children */
@@ -266,7 +269,7 @@ See the example below, where a more complete device tree is shown: · 89 unmodified lines
266269 ranges = <0 MBUS_ID(0xf0, 0x01) 0 0x100000>;
267270
268271 mbusc: mbus-controller@20000 {
269− reg = <0x20000 0x100>, <0x20180 0x20>;
272+ reg = <0x20000 0x100>, <0x20180 0x20>, <0x20250 0x8>;
270273 };
271274
272275 interrupt-controller@20000 {
Documentation/devicetree/bindings/chosen.txt+46−0
@@ -0,0 +1,46 @@
1+The chosen node
2+---------------
3+
4+The chosen node does not represent a real device, but serves as a place
5+for passing data between firmware and the operating system, like boot
6+arguments. Data in the chosen node does not represent the hardware.
7+
8+
9+stdout-path property
10+--------------------
11+
12+Device trees may specify the device to be used for boot console output
13+with a stdout-path property under /chosen, as described in ePAPR, e.g.
14+
15+/ {
16+ chosen {
17+ stdout-path = "/serial@f00:115200";
18+ };
19+
20+ serial@f00 {
21+ compatible = "vendor,some-uart";
22+ reg = <0xf00 0x10>;
23+ };
24+};
25+
26+If the character ":" is present in the value, this terminates the path.
27+The meaning of any characters following the ":" is device-specific, and
28+must be specified in the relevant binding documentation.
29+
30+For UART devices, the preferred binding is a string in the form:
31+
32+ <baud>{<parity>{<bits>{<flow>}}}
33+
34+where
35+
36+ baud - baud rate in decimal
37+ parity - 'n' (none), 'o', (odd) or 'e' (even)
38+ bits - number of data bits
39+ flow - 'r' (rts)
40+
41+For example: 115200n8r
42+
43+Implementation note: Linux will look for the property "linux,stdout-path" or
44+on PowerPC "stdout" if "stdout-path" is not found. However, the
45+"linux,stdout-path" and "stdout" properties are deprecated. New platforms
46+should only use the "stdout-path" property.
Documentation/devicetree/bindings/clock/arm-integrator.txt+1−1
@@ -1,6 +1,6 @@
11 Clock bindings for ARM Integrator and Versatile Core Module clocks
22
3−Auxilary Oscillator Clock
3+Auxiliary Oscillator Clock
44
55 This is a configurable clock fed from a 24 MHz chrystal,
66 used for generating e.g. video clocks. It is located on the
Documentation/devicetree/bindings/clock/at91-clock.txt+14−0
@@ -74,6 +74,9 @@ Required properties: · 73 unmodified lines
7474 "atmel,at91sam9x5-clk-utmi":
7575 at91 utmi clock
7676
77+ "atmel,sama5d4-clk-h32mx":
78+ at91 h32mx clock
79+
7780 Required properties for SCKC node:
7881 - reg : defines the IO memory reserved for the SCKC.
7982 - #size-cells : shall be 0 (reg is used to encode clk id).
@@ -447,3 +450,14 @@ For example: · 367 unmodified lines
447450 #clock-cells = <0>;
448451 clocks = <&main>;
449452 };
453+
454+Required properties for 32 bits bus Matrix clock (h32mx clock):
455+- #clock-cells : from common clock binding; shall be set to 0.
456+- clocks : shall be the master clock source phandle.
457+
458+For example:
459+ h32ck: h32mxck {
460+ #clock-cells = <0>;
461+ compatible = "atmel,sama5d4-clk-h32mx";
462+ clocks = <&mck>;
463+ };
Documentation/devicetree/bindings/clock/bcm-cygnus-clock.txt+34−0
@@ -0,0 +1,34 @@
1+Broadcom Cygnus Clocks
2+
3+This binding uses the common clock binding:
4+Documentation/devicetree/bindings/clock/clock-bindings.txt
5+
6+Currently various "fixed" clocks are declared for peripheral drivers that use
7+the common clock framework to reference their core clocks. Proper support of
8+these clocks will be added later
9+
10+Device tree example:
11+
12+ clocks {
13+ #address-cells = <1>;
14+ #size-cells = <1>;
15+ ranges;
16+
17+ osc: oscillator {
18+ compatible = "fixed-clock";
19+ #clock-cells = <1>;
20+ clock-frequency = <25000000>;
21+ };
22+
23+ apb_clk: apb_clk {
24+ compatible = "fixed-clock";
25+ #clock-cells = <0>;
26+ clock-frequency = <1000000000>;
27+ };
28+
29+ periph_clk: periph_clk {
30+ compatible = "fixed-clock";
31+ #clock-cells = <0>;
32+ clock-frequency = <500000000>;
33+ };
34+ };
Documentation/devicetree/bindings/clock/exynos3250-clock.txt+9−1
@@ -7,6 +7,8 @@ Required Properties: · 6 unmodified lines
77
88 - compatible: should be one of the following.
99 - "samsung,exynos3250-cmu" - controller compatible with Exynos3250 SoC.
10+ - "samsung,exynos3250-cmu-dmc" - controller compatible with
11+ Exynos3250 SoC for Dynamic Memory Controller domain.
1012
1113 - reg: physical base address of the controller and length of memory mapped
1214 region.
@@ -20,7 +22,7 @@ All available clocks are defined as preprocessor macros in · 7 unmodified lines
2022 dt-bindings/clock/exynos3250.h header and can be used in device
2123 tree sources.
2224
23−Example 1: An example of a clock controller node is listed below.
25+Example 1: Examples of clock controller nodes are listed below.
2426
2527 cmu: clock-controller@10030000 {
2628 compatible = "samsung,exynos3250-cmu";
@@ -28,6 +30,12 @@ Example 1: An example of a clock controller node is listed below. · 1 unmodified line
2830 #clock-cells = <1>;
2931 };
3032
33+ cmu_dmc: clock-controller@105C0000 {
34+ compatible = "samsung,exynos3250-cmu-dmc";
35+ reg = <0x105C0000 0x2000>;
36+ #clock-cells = <1>;
37+ };
38+
3139 Example 2: UART controller node that consumes the clock generated by the clock
3240 controller. Refer to the standard clock bindings for information
3341 about 'clocks' and 'clock-names' property.
Documentation/devicetree/bindings/clock/exynos4415-clock.txt+38−0
@@ -0,0 +1,38 @@
1+* Samsung Exynos4415 Clock Controller
2+
3+The Exynos4415 clock controller generates and supplies clock to various
4+consumer devices within the Exynos4415 SoC.
5+
6+Required properties:
7+
8+- compatible: should be one of the following:
9+ - "samsung,exynos4415-cmu" - for the main system clocks controller
10+ (CMU_LEFTBUS, CMU_RIGHTBUS, CMU_TOP, CMU_CPU clock domains).
11+ - "samsung,exynos4415-cmu-dmc" - for the Exynos4415 SoC DRAM Memory
12+ Controller (DMC) domain clock controller.
13+
14+- reg: physical base address of the controller and length of memory mapped
15+ region.
16+
17+- #clock-cells: should be 1.
18+
19+Each clock is assigned an identifier and client nodes can use this identifier
20+to specify the clock which they consume.
21+
22+All available clocks are defined as preprocessor macros in
23+dt-bindings/clock/exynos4415.h header and can be used in device
24+tree sources.
25+
26+Example 1: An example of a clock controller node is listed below.
27+
28+ cmu: clock-controller@10030000 {
29+ compatible = "samsung,exynos4415-cmu";
30+ reg = <0x10030000 0x18000>;
31+ #clock-cells = <1>;
32+ };
33+
34+ cmu-dmc: clock-controller@105C0000 {
35+ compatible = "samsung,exynos4415-cmu-dmc";
36+ reg = <0x105C0000 0x3000>;
37+ #clock-cells = <1>;
38+ };
Documentation/devicetree/bindings/clock/exynos7-clock.txt+93−0
@@ -0,0 +1,93 @@
1+* Samsung Exynos7 Clock Controller
2+
3+Exynos7 clock controller has various blocks which are instantiated
4+independently from the device-tree. These clock controllers
5+generate and supply clocks to various hardware blocks within
6+the SoC.
7+
8+Each clock is assigned an identifier and client nodes can use
9+this identifier to specify the clock which they consume. All
10+available clocks are defined as preprocessor macros in
11+dt-bindings/clock/exynos7-clk.h header and can be used in
12+device tree sources.
13+
14+External clocks:
15+
16+There are several clocks that are generated outside the SoC. It
17+is expected that they are defined using standard clock bindings
18+with following clock-output-names:
19+
20+ - "fin_pll" - PLL input clock from XXTI
21+
22+Required Properties for Clock Controller:
23+
24+ - compatible: clock controllers will use one of the following
25+ compatible strings to indicate the clock controller
26+ functionality.
27+
28+ - "samsung,exynos7-clock-topc"
29+ - "samsung,exynos7-clock-top0"
30+ - "samsung,exynos7-clock-top1"
31+ - "samsung,exynos7-clock-ccore"
32+ - "samsung,exynos7-clock-peric0"
33+ - "samsung,exynos7-clock-peric1"
34+ - "samsung,exynos7-clock-peris"
35+ - "samsung,exynos7-clock-fsys0"
36+ - "samsung,exynos7-clock-fsys1"
37+
38+ - reg: physical base address of the controller and the length of
39+ memory mapped region.
40+
41+ - #clock-cells: should be 1.
42+
43+ - clocks: list of clock identifiers which are fed as the input to
44+ the given clock controller. Please refer the next section to
45+ find the input clocks for a given controller.
46+
47+- clock-names: list of names of clocks which are fed as the input
48+ to the given clock controller.
49+
50+Input clocks for top0 clock controller:
51+ - fin_pll
52+ - dout_sclk_bus0_pll
53+ - dout_sclk_bus1_pll
54+ - dout_sclk_cc_pll
55+ - dout_sclk_mfc_pll
56+
57+Input clocks for top1 clock controller:
58+ - fin_pll
59+ - dout_sclk_bus0_pll
60+ - dout_sclk_bus1_pll
61+ - dout_sclk_cc_pll
62+ - dout_sclk_mfc_pll
63+
64+Input clocks for ccore clock controller:
65+ - fin_pll
66+ - dout_aclk_ccore_133
67+
68+Input clocks for peric0 clock controller:
69+ - fin_pll
70+ - dout_aclk_peric0_66
71+ - sclk_uart0
72+
73+Input clocks for peric1 clock controller:
74+ - fin_pll
75+ - dout_aclk_peric1_66
76+ - sclk_uart1
77+ - sclk_uart2
78+ - sclk_uart3
79+
80+Input clocks for peris clock controller:
81+ - fin_pll
82+ - dout_aclk_peris_66
83+
84+Input clocks for fsys0 clock controller:
85+ - fin_pll
86+ - dout_aclk_fsys0_200
87+ - dout_sclk_mmc2
88+
89+Input clocks for fsys1 clock controller:
90+ - fin_pll
91+ - dout_aclk_fsys1_200
92+ - dout_sclk_mmc0
93+ - dout_sclk_mmc1
Documentation/devicetree/bindings/clock/gpio-gate-clock.txt+21−0
@@ -0,0 +1,21 @@
1+Binding for simple gpio gated clock.
2+
3+This binding uses the common clock binding[1].
4+
5+[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
6+
7+Required properties:
8+- compatible : shall be "gpio-gate-clock".
9+- #clock-cells : from common clock binding; shall be set to 0.
10+- enable-gpios : GPIO reference for enabling and disabling the clock.
11+
12+Optional properties:
13+- clocks: Maximum of one parent clock is supported.
14+
15+Example:
16+ clock {
17+ compatible = "gpio-gate-clock";
18+ clocks = <&parentclk>;
19+ #clock-cells = <0>;
20+ enable-gpios = <&gpio 1 GPIO_ACTIVE_HIGH>;
21+ };
Documentation/devicetree/bindings/clock/marvell,mmp2.txt+21−0
@@ -0,0 +1,21 @@
1+* Marvell MMP2 Clock Controller
2+
3+The MMP2 clock subsystem generates and supplies clock to various
4+controllers within the MMP2 SoC.
5+
6+Required Properties:
7+
8+- compatible: should be one of the following.
9+ - "marvell,mmp2-clock" - controller compatible with MMP2 SoC.
10+
11+- reg: physical base address of the clock subsystem and length of memory mapped
12+ region. There are 3 places in SOC has clock control logic:
13+ "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
14+
15+- #clock-cells: should be 1.
16+- #reset-cells: should be 1.
17+
18+Each clock is assigned an identifier and client nodes use this identifier
19+to specify the clock which they consume.
20+
21+All these identifier could be found in <dt-bindings/clock/marvell-mmp2.h>.
Documentation/devicetree/bindings/clock/marvell,pxa168.txt+21−0
@@ -0,0 +1,21 @@
1+* Marvell PXA168 Clock Controller
2+
3+The PXA168 clock subsystem generates and supplies clock to various
4+controllers within the PXA168 SoC.
5+
6+Required Properties:
7+
8+- compatible: should be one of the following.
9+ - "marvell,pxa168-clock" - controller compatible with PXA168 SoC.
10+
11+- reg: physical base address of the clock subsystem and length of memory mapped
12+ region. There are 3 places in SOC has clock control logic:
13+ "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
14+
15+- #clock-cells: should be 1.
16+- #reset-cells: should be 1.
17+
18+Each clock is assigned an identifier and client nodes use this identifier
19+to specify the clock which they consume.
20+
21+All these identifier could be found in <dt-bindings/clock/marvell,pxa168.h>.
Documentation/devicetree/bindings/clock/marvell,pxa910.txt+21−0
@@ -0,0 +1,21 @@
1+* Marvell PXA910 Clock Controller
2+
3+The PXA910 clock subsystem generates and supplies clock to various
4+controllers within the PXA910 SoC.
5+
6+Required Properties:
7+
8+- compatible: should be one of the following.
9+ - "marvell,pxa910-clock" - controller compatible with PXA910 SoC.
10+
11+- reg: physical base address of the clock subsystem and length of memory mapped
12+ region. There are 4 places in SOC has clock control logic:
13+ "mpmu", "apmu", "apbc", "apbcp". So four reg spaces need to be defined.
14+
15+- #clock-cells: should be 1.
16+- #reset-cells: should be 1.
17+
18+Each clock is assigned an identifier and client nodes use this identifier
19+to specify the clock which they consume.
20+
21+All these identifier could be found in <dt-bindings/clock/marvell-pxa910.h>.
Documentation/devicetree/bindings/clock/maxim,max77686.txt+12−4
@@ -9,13 +9,21 @@ The MAX77686 contains three 32.768khz clock outputs that can be controlled · 8 unmodified lines
99 Following properties should be presend in main device node of the MFD chip.
1010
1111 Required properties:
12−- #clock-cells: simple one-cell clock specifier format is used, where the
13− only cell is used as an index of the clock inside the provider. Following
14− indices are allowed:
12+
13+- #clock-cells: from common clock binding; shall be set to 1.
14+
15+Optional properties:
16+- clock-output-names: From common clock binding.
17+
18+Each clock is assigned an identifier and client nodes can use this identifier
19+to specify the clock which they consume. Following indices are allowed:
1520 - 0: 32khz_ap clock,
1621 - 1: 32khz_cp clock,
1722 - 2: 32khz_pmic clock.
1823
24+Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77686.h
25+header and can be used in device tree sources.
26+
1927 Example: Node of the MFD chip
2028
2129 max77686: max77686@09 {
@@ -34,5 +42,5 @@ Example: Clock consumer node · 12 unmodified lines
3442 compatible = "bar,foo";
3543 /* ... */
3644 clock-names = "my-clock";
37− clocks = <&max77686 2>;
45+ clocks = <&max77686 MAX77686_CLK_PMIC>;
3846 };
Documentation/devicetree/bindings/clock/maxim,max77802.txt+44−0
@@ -0,0 +1,44 @@
1+Binding for Maxim MAX77802 32k clock generator block
2+
3+This is a part of device tree bindings of MAX77802 multi-function device.
4+More information can be found in bindings/mfd/max77802.txt file.
5+
6+The MAX77802 contains two 32.768khz clock outputs that can be controlled
7+(gated/ungated) over I2C.
8+
9+Following properties should be present in main device node of the MFD chip.
10+
11+Required properties:
12+- #clock-cells: From common clock binding; shall be set to 1.
13+
14+Optional properties:
15+- clock-output-names: From common clock binding.
16+
17+Each clock is assigned an identifier and client nodes can use this identifier
18+to specify the clock which they consume. Following indices are allowed:
19+ - 0: 32khz_ap clock,
20+ - 1: 32khz_cp clock.
21+
22+Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77802.h
23+header and can be used in device tree sources.
24+
25+Example: Node of the MFD chip
26+
27+ max77802: max77802@09 {
28+ compatible = "maxim,max77802";
29+ interrupt-parent = <&wakeup_eint>;
30+ interrupts = <26 0>;
31+ reg = <0x09>;
32+ #clock-cells = <1>;
33+
34+ /* ... */
35+ };
36+
37+Example: Clock consumer node
38+
39+ foo@0 {
40+ compatible = "bar,foo";
41+ /* ... */
42+ clock-names = "my-clock";
43+ clocks = <&max77802 MAX77802_CLK_32K_AP>;
44+ };
Documentation/devicetree/bindings/clock/pxa-clock.txt+16−0
@@ -0,0 +1,16 @@
1+* Clock bindings for Marvell PXA chips
2+
3+Required properties:
4+- compatible: Should be "marvell,pxa-clocks"
5+- #clock-cells: Should be <1>
6+
7+The clock consumer should specify the desired clock by having the clock
8+ID in its "clocks" phandle cell (see include/.../pxa-clock.h).
9+
10+Examples:
11+
12+pxa2xx_clks: pxa2xx_clks@41300004 {
13+ compatible = "marvell,pxa-clocks";
14+ #clock-cells = <1>;
15+ status = "okay";
16+};
Documentation/devicetree/bindings/clock/qoriq-clock.txt+12−2
@@ -62,6 +62,8 @@ Required properties: · 61 unmodified lines
6262 It takes parent's clock-frequency as its clock.
6363 * "fsl,qoriq-sysclk-2.0": for input system clock (v2.0).
6464 It takes parent's clock-frequency as its clock.
65+ * "fsl,qoriq-platform-pll-1.0" for the platform PLL clock (v1.0)
66+ * "fsl,qoriq-platform-pll-2.0" for the platform PLL clock (v2.0)
6567 - #clock-cells: From common clock binding. The number of cells in a
6668 clock-specifier. Should be <0> for "fsl,qoriq-sysclk-[1,2].0"
6769 clocks, or <1> for "fsl,qoriq-core-pll-[1,2].0" clocks.
@@ -128,8 +130,16 @@ Example for clock block and clock provider: · 60 unmodified lines
128130 clock-names = "pll0", "pll0-div2", "pll1", "pll1-div2";
129131 clock-output-names = "cmux1";
130132 };
133+
134+ platform-pll: platform-pll@c00 {
135+ #clock-cells = <1>;
136+ reg = <0xc00 0x4>;
137+ compatible = "fsl,qoriq-platform-pll-1.0";
138+ clocks = <&sysclk>;
139+ clock-output-names = "platform-pll", "platform-pll-div2";
140+ };
131141 };
132− }
142+};
133143
134144 Example for clock consumer:
135145
@@ -139,4 +149,4 @@ Example for clock consumer: · 3 unmodified lines
139149 clocks = <&mux0>;
140150 ...
141151 };
142− }
152+};
Documentation/devicetree/bindings/clock/renesas,cpg-div6-clocks.txt+12−6
@@ -7,11 +7,16 @@ to 64. · 6 unmodified lines
77 Required Properties:
88
99 - compatible: Must be one of the following
10+ - "renesas,r8a73a4-div6-clock" for R8A73A4 (R-Mobile APE6) DIV6 clocks
11+ - "renesas,r8a7740-div6-clock" for R8A7740 (R-Mobile A1) DIV6 clocks
1012 - "renesas,r8a7790-div6-clock" for R8A7790 (R-Car H2) DIV6 clocks
1113 - "renesas,r8a7791-div6-clock" for R8A7791 (R-Car M2) DIV6 clocks
14+ - "renesas,sh73a0-div6-clock" for SH73A0 (SH-Mobile AG5) DIV6 clocks
1215 - "renesas,cpg-div6-clock" for generic DIV6 clocks
1316 - reg: Base address and length of the memory resource used by the DIV6 clock
14− - clocks: Reference to the parent clock
17+ - clocks: Reference to the parent clock(s); either one, four, or eight
18+ clocks must be specified. For clocks with multiple parents, invalid
19+ settings must be specified as "<0>".
1520 - #clock-cells: Must be 0
1621 - clock-output-names: The name of the clock as a free-form string
1722
@@ -19,10 +24,11 @@ Required Properties: · 1 unmodified line
1924 Example
2025 -------
2126
22− sd2_clk: sd2_clk@e6150078 {
23− compatible = "renesas,r8a7790-div6-clock", "renesas,cpg-div6-clock";
24− reg = <0 0xe6150078 0 4>;
25− clocks = <&pll1_div2_clk>;
27+ sdhi2_clk: sdhi2_clk@e615007c {
28+ compatible = "renesas,r8a73a4-div6-clock", "renesas,cpg-div6-clock";
29+ reg = <0 0xe615007c 0 4>;
30+ clocks = <&pll1_div2_clk>, <&cpg_clocks R8A73A4_CLK_PLL2S>,
31+ <0>, <&extal2_clk>;
2632 #clock-cells = <0>;
27− clock-output-names = "sd2";
33+ clock-output-names = "sdhi2ck";
2834 };
Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt+7−4
@@ -11,9 +11,12 @@ Required Properties: · 10 unmodified lines
1111
1212 - compatible: Must be one of the following
1313 - "renesas,r7s72100-mstp-clocks" for R7S72100 (RZ) MSTP gate clocks
14+ - "renesas,r8a7740-mstp-clocks" for R8A7740 (R-Mobile A1) MSTP gate clocks
1415 - "renesas,r8a7779-mstp-clocks" for R8A7779 (R-Car H1) MSTP gate clocks
1516 - "renesas,r8a7790-mstp-clocks" for R8A7790 (R-Car H2) MSTP gate clocks
1617 - "renesas,r8a7791-mstp-clocks" for R8A7791 (R-Car M2) MSTP gate clocks
18+ - "renesas,r8a7794-mstp-clocks" for R8A7794 (R-Car E2) MSTP gate clocks
19+ - "renesas,sh73a0-mstp-clocks" for SH73A0 (SH-MobileAG5) MSTP gate clocks
1720 - "renesas,cpg-mstp-clock" for generic MSTP gate clocks
1821 - reg: Base address and length of the I/O mapped registers used by the MSTP
1922 clocks. The first register is the clock control register and is mandatory.
@@ -23,11 +26,11 @@ Required Properties: · 3 unmodified lines
2326 must appear in the same order as the output clocks.
2427 - #clock-cells: Must be 1
2528 - clock-output-names: The name of the clocks as free-form strings
26− - renesas,clock-indices: Indices of the gate clocks into the group (0 to 31)
29+ - clock-indices: Indices of the gate clocks into the group (0 to 31)
2730
28−The clocks, clock-output-names and renesas,clock-indices properties contain one
29−entry per gate clock. The MSTP groups are sparsely populated. Unimplemented
30−gate clocks must not be declared.
31+The clocks, clock-output-names and clock-indices properties contain one entry
32+per gate clock. The MSTP groups are sparsely populated. Unimplemented gate
33+clocks must not be declared.
3134
3235
3336 Example
Documentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt+1−0
@@ -8,6 +8,7 @@ Required Properties: · 7 unmodified lines
88 - compatible: Must be one of
99 - "renesas,r8a7790-cpg-clocks" for the r8a7790 CPG
1010 - "renesas,r8a7791-cpg-clocks" for the r8a7791 CPG
11+ - "renesas,r8a7794-cpg-clocks" for the r8a7794 CPG
1112 - "renesas,rcar-gen2-cpg-clocks" for the generic R-Car Gen2 CPG
1213
1314 - reg: Base address and length of the memory resource used by the CPG
Documentation/devicetree/bindings/clock/st/st,flexgen.txt+1−1
@@ -11,7 +11,7 @@ Please find an example below: · 10 unmodified lines
1111
1212 Clockgen block diagram
1313 -------------------------------------------------------------------
14− | Flexgen stucture |
14+ | Flexgen structure |
1515 | --------------------------------------------- |
1616 | | ------- -------- -------- | |
1717 clk_sysin | | | | | | | | |
Documentation/devicetree/bindings/clock/sunxi.txt+31−4
@@ -10,14 +10,17 @@ Required properties: · 9 unmodified lines
1010 "allwinner,sun4i-a10-pll1-clk" - for the main PLL clock and PLL4
1111 "allwinner,sun6i-a31-pll1-clk" - for the main PLL clock on A31
1212 "allwinner,sun8i-a23-pll1-clk" - for the main PLL clock on A23
13+ "allwinner,sun9i-a80-pll4-clk" - for the peripheral PLLs on A80
1314 "allwinner,sun4i-a10-pll5-clk" - for the PLL5 clock
1415 "allwinner,sun4i-a10-pll6-clk" - for the PLL6 clock
1516 "allwinner,sun6i-a31-pll6-clk" - for the PLL6 clock on A31
17+ "allwinner,sun9i-a80-gt-clk" - for the GT bus clock on A80
1618 "allwinner,sun4i-a10-cpu-clk" - for the CPU multiplexer clock
1719 "allwinner,sun4i-a10-axi-clk" - for the AXI clock
1820 "allwinner,sun8i-a23-axi-clk" - for the AXI clock on A23
1921 "allwinner,sun4i-a10-axi-gates-clk" - for the AXI gates
2022 "allwinner,sun4i-a10-ahb-clk" - for the AHB clock
23+ "allwinner,sun9i-a80-ahb-clk" - for the AHB bus clocks on A80
2124 "allwinner,sun4i-a10-ahb-gates-clk" - for the AHB gates on A10
2225 "allwinner,sun5i-a13-ahb-gates-clk" - for the AHB gates on A13
2326 "allwinner,sun5i-a10s-ahb-gates-clk" - for the AHB gates on A10s
@@ -26,27 +29,36 @@ Required properties: · 2 unmodified lines
2629 "allwinner,sun6i-a31-ahb1-mux-clk" - for the AHB1 multiplexer on A31
2730 "allwinner,sun6i-a31-ahb1-gates-clk" - for the AHB1 gates on A31
2831 "allwinner,sun8i-a23-ahb1-gates-clk" - for the AHB1 gates on A23
32+ "allwinner,sun9i-a80-ahb0-gates-clk" - for the AHB0 gates on A80
33+ "allwinner,sun9i-a80-ahb1-gates-clk" - for the AHB1 gates on A80
34+ "allwinner,sun9i-a80-ahb2-gates-clk" - for the AHB2 gates on A80
2935 "allwinner,sun4i-a10-apb0-clk" - for the APB0 clock
3036 "allwinner,sun6i-a31-apb0-clk" - for the APB0 clock on A31
3137 "allwinner,sun8i-a23-apb0-clk" - for the APB0 clock on A23
38+ "allwinner,sun9i-a80-apb0-clk" - for the APB0 bus clock on A80
3239 "allwinner,sun4i-a10-apb0-gates-clk" - for the APB0 gates on A10
3340 "allwinner,sun5i-a13-apb0-gates-clk" - for the APB0 gates on A13
3441 "allwinner,sun5i-a10s-apb0-gates-clk" - for the APB0 gates on A10s
3542 "allwinner,sun6i-a31-apb0-gates-clk" - for the APB0 gates on A31
3643 "allwinner,sun7i-a20-apb0-gates-clk" - for the APB0 gates on A20
3744 "allwinner,sun8i-a23-apb0-gates-clk" - for the APB0 gates on A23
45+ "allwinner,sun9i-a80-apb0-gates-clk" - for the APB0 gates on A80
3846 "allwinner,sun4i-a10-apb1-clk" - for the APB1 clock
39− "allwinner,sun4i-a10-apb1-mux-clk" - for the APB1 clock muxing
47+ "allwinner,sun9i-a80-apb1-clk" - for the APB1 bus clock on A80
4048 "allwinner,sun4i-a10-apb1-gates-clk" - for the APB1 gates on A10
4149 "allwinner,sun5i-a13-apb1-gates-clk" - for the APB1 gates on A13
4250 "allwinner,sun5i-a10s-apb1-gates-clk" - for the APB1 gates on A10s
4351 "allwinner,sun6i-a31-apb1-gates-clk" - for the APB1 gates on A31
4452 "allwinner,sun7i-a20-apb1-gates-clk" - for the APB1 gates on A20
4553 "allwinner,sun8i-a23-apb1-gates-clk" - for the APB1 gates on A23
46− "allwinner,sun6i-a31-apb2-div-clk" - for the APB2 gates on A31
54+ "allwinner,sun9i-a80-apb1-gates-clk" - for the APB1 gates on A80
4755 "allwinner,sun6i-a31-apb2-gates-clk" - for the APB2 gates on A31
4856 "allwinner,sun8i-a23-apb2-gates-clk" - for the APB2 gates on A23
57+ "allwinner,sun5i-a13-mbus-clk" - for the MBUS clock on A13
58+ "allwinner,sun4i-a10-mmc-output-clk" - for the MMC output clock on A10
59+ "allwinner,sun4i-a10-mmc-sample-clk" - for the MMC sample clock on A10
4960 "allwinner,sun4i-a10-mod0-clk" - for the module 0 family of clocks
61+ "allwinner,sun8i-a23-mbus-clk" - for the MBUS clock on A23
5062 "allwinner,sun7i-a20-out-clk" - for the external output clocks
5163 "allwinner,sun7i-a20-gmac-clk" - for the GMAC clock module on A20/A31
5264 "allwinner,sun4i-a10-usb-clk" - for usb gates + resets on A10 / A20
@@ -59,8 +71,9 @@ Required properties for all clocks: · 6 unmodified lines
5971 multiplexed clocks, the list order must match the hardware
6072 programming order.
6173 - #clock-cells : from common clock binding; shall be set to 0 except for
62− "allwinner,*-gates-clk", "allwinner,sun4i-pll5-clk" and
63− "allwinner,sun4i-pll6-clk" where it shall be set to 1
74+ the following compatibles where it shall be set to 1:
75+ "allwinner,*-gates-clk", "allwinner,sun4i-pll5-clk",
76+ "allwinner,sun4i-pll6-clk", "allwinner,sun6i-a31-pll6-clk"
6477 - clock-output-names : shall be the corresponding names of the outputs.
6578 If the clock module only has one output, the name shall be the
6679 module name.
@@ -75,6 +88,12 @@ Clock consumers should specify the desired clocks they use with a · 8 unmodified lines
7588 "clocks" phandle cell. Consumers that are using a gated clock should
7689 provide an additional ID in their clock property. This ID is the
7790 offset of the bit controlling this particular gate in the register.
91+For the other clocks with "#clock-cells" = 1, the additional ID shall
92+refer to the index of the output.
93+
94+For "allwinner,sun6i-a31-pll6-clk", there are 2 outputs. The first output
95+is the normal PLL6 output, or "pll6". The second output is rate doubled
96+PLL6, or "pll6x2".
7897
7998 For example:
8099
@@ -102,6 +121,14 @@ pll5: clk@01c20020 { · 21 unmodified lines
102121 clock-output-names = "pll5_ddr", "pll5_other";
103122 };
104123
124+pll6: clk@01c20028 {
125+ #clock-cells = <1>;
126+ compatible = "allwinner,sun6i-a31-pll6-clk";
127+ reg = <0x01c20028 0x4>;
128+ clocks = <&osc24M>;
129+ clock-output-names = "pll6", "pll6x2";
130+};
131+
105132 cpu: cpu@01c20054 {
106133 #clock-cells = <0>;
107134 compatible = "allwinner,sun4i-a10-cpu-clk";
Documentation/devicetree/bindings/clock/vf610-clock.txt+15−0
@@ -5,6 +5,19 @@ Required properties: · 4 unmodified lines
55 - reg: Address and length of the register set
66 - #clock-cells: Should be <1>
77
8+Optional properties:
9+- clocks: list of clock identifiers which are external input clocks to the
10+ given clock controller. Please refer the next section to find
11+ the input clocks for a given controller.
12+- clock-names: list of names of clocks which are exteral input clocks to the
13+ given clock controller.
14+
15+Input clocks for top clock controller:
16+ - sxosc (external crystal oscillator 32KHz, recommended)
17+ - fxosc (external crystal oscillator 24MHz, recommended)
18+ - audio_ext
19+ - enet_ext
20+
821 The clock consumer should specify the desired clock by having the clock
922 ID in its "clocks" phandle cell. See include/dt-bindings/clock/vf610-clock.h
1023 for the full list of VF610 clock IDs.
@@ -15,6 +28,8 @@ clks: ccm@4006b000 { · 4 unmodified lines
1528 compatible = "fsl,vf610-ccm";
1629 reg = <0x4006b000 0x1000>;
1730 #clock-cells = <1>;
31+ clocks = <&sxosc>, <&fxosc>;
32+ clock-names = "sxosc", "fxosc";
1833 };
1934
2035 uart1: serial@40028000 {
Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt+0−64
@@ -1,64 +0,0 @@
1−Generic CPU0 cpufreq driver
2−
3−It is a generic cpufreq driver for CPU0 frequency management. It
4−supports both uniprocessor (UP) and symmetric multiprocessor (SMP)
5−systems which share clock and voltage across all CPUs.
6−
7−Both required and optional properties listed below must be defined
8−under node /cpus/cpu@0.
9−
10−Required properties:
11−- None
12−
13−Optional properties:
14−- operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
15− details. OPPs *must* be supplied either via DT, i.e. this property, or
16− populated at runtime.
17−- clock-latency: Specify the possible maximum transition latency for clock,
18− in unit of nanoseconds.
19−- voltage-tolerance: Specify the CPU voltage tolerance in percentage.
20−- #cooling-cells:
21−- cooling-min-level:
22−- cooling-max-level:
23− Please refer to Documentation/devicetree/bindings/thermal/thermal.txt.
24−
25−Examples:
26−
27−cpus {
28− #address-cells = <1>;
29− #size-cells = <0>;
30−
31− cpu@0 {
32− compatible = "arm,cortex-a9";
33− reg = <0>;
34− next-level-cache = <&L2>;
35− operating-points = <
36− /* kHz uV */
37− 792000 1100000
38− 396000 950000
39− 198000 850000
40− >;
41− clock-latency = <61036>; /* two CLK32 periods */
42− #cooling-cells = <2>;
43− cooling-min-level = <0>;
44− cooling-max-level = <2>;
45− };
46−
47− cpu@1 {
48− compatible = "arm,cortex-a9";
49− reg = <1>;
50− next-level-cache = <&L2>;
51− };
52−
53− cpu@2 {
54− compatible = "arm,cortex-a9";
55− reg = <2>;
56− next-level-cache = <&L2>;
57− };
58−
59− cpu@3 {
60− compatible = "arm,cortex-a9";
61− reg = <3>;
62− next-level-cache = <&L2>;
63− };
64−};
Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt+64−0
@@ -0,0 +1,64 @@
1+Generic cpufreq driver
2+
3+It is a generic DT based cpufreq driver for frequency management. It supports
4+both uniprocessor (UP) and symmetric multiprocessor (SMP) systems which share
5+clock and voltage across all CPUs.
6+
7+Both required and optional properties listed below must be defined
8+under node /cpus/cpu@0.
9+
10+Required properties:
11+- None
12+
13+Optional properties:
14+- operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
15+ details. OPPs *must* be supplied either via DT, i.e. this property, or
16+ populated at runtime.
17+- clock-latency: Specify the possible maximum transition latency for clock,
18+ in unit of nanoseconds.
19+- voltage-tolerance: Specify the CPU voltage tolerance in percentage.
20+- #cooling-cells:
21+- cooling-min-level:
22+- cooling-max-level:
23+ Please refer to Documentation/devicetree/bindings/thermal/thermal.txt.
24+
25+Examples:
26+
27+cpus {
28+ #address-cells = <1>;
29+ #size-cells = <0>;
30+
31+ cpu@0 {
32+ compatible = "arm,cortex-a9";
33+ reg = <0>;
34+ next-level-cache = <&L2>;
35+ operating-points = <
36+ /* kHz uV */
37+ 792000 1100000
38+ 396000 950000
39+ 198000 850000
40+ >;
41+ clock-latency = <61036>; /* two CLK32 periods */
42+ #cooling-cells = <2>;
43+ cooling-min-level = <0>;
44+ cooling-max-level = <2>;
45+ };
46+
47+ cpu@1 {
48+ compatible = "arm,cortex-a9";
49+ reg = <1>;
50+ next-level-cache = <&L2>;
51+ };
52+
53+ cpu@2 {
54+ compatible = "arm,cortex-a9";
55+ reg = <2>;
56+ next-level-cache = <&L2>;
57+ };
58+
59+ cpu@3 {
60+ compatible = "arm,cortex-a9";
61+ reg = <3>;
62+ next-level-cache = <&L2>;
63+ };
64+};
Documentation/devicetree/bindings/crypto/fsl-imx-sahara.txt+1−1
@@ -1,5 +1,5 @@
11 Freescale SAHARA Cryptographic Accelerator included in some i.MX chips.
2−Currently only i.MX27 is supported.
2+Currently only i.MX27 and i.MX53 are supported.
33
44 Required properties:
55 - compatible : Should be "fsl,<soc>-sahara"
Documentation/devicetree/bindings/crypto/fsl-sec6.txt+1−1
@@ -1,5 +1,5 @@
11 SEC 6 is as Freescale's Cryptographic Accelerator and Assurance Module (CAAM).
2−Currently Freescale powerpc chip C29X is embeded with SEC 6.
2+Currently Freescale powerpc chip C29X is embedded with SEC 6.
33 SEC 6 device tree binding include:
44 -SEC 6 Node
55 -Job Ring Node
Documentation/devicetree/bindings/dma/atmel-xdma.txt+54−0
@@ -0,0 +1,54 @@
1+* Atmel Extensible Direct Memory Access Controller (XDMAC)
2+
3+* XDMA Controller
4+Required properties:
5+- compatible: Should be "atmel,<chip>-dma".
6+ <chip> compatible description:
7+ - sama5d4: first SoC adding the XDMAC
8+- reg: Should contain DMA registers location and length.
9+- interrupts: Should contain DMA interrupt.
10+- #dma-cells: Must be <1>, used to represent the number of integer cells in
11+the dmas property of client devices.
12+ - The 1st cell specifies the channel configuration register:
13+ - bit 13: SIF, source interface identifier, used to get the memory
14+ interface identifier,
15+ - bit 14: DIF, destination interface identifier, used to get the peripheral
16+ interface identifier,
17+ - bit 30-24: PERID, peripheral identifier.
18+
19+Example:
20+
21+dma1: dma-controller@f0004000 {
22+ compatible = "atmel,sama5d4-dma";
23+ reg = <0xf0004000 0x200>;
24+ interrupts = <50 4 0>;
25+ #dma-cells = <1>;
26+};
27+
28+
29+* DMA clients
30+DMA clients connected to the Atmel XDMA controller must use the format
31+described in the dma.txt file, using a one-cell specifier for each channel.
32+The two cells in order are:
33+1. A phandle pointing to the DMA controller.
34+2. Channel configuration register. Configurable fields are:
35+ - bit 13: SIF, source interface identifier, used to get the memory
36+ interface identifier,
37+ - bit 14: DIF, destination interface identifier, used to get the peripheral
38+ interface identifier,
39+ - bit 30-24: PERID, peripheral identifier.
40+
41+Example:
42+
43+i2c2: i2c@f8024000 {
44+ compatible = "atmel,at91sam9x5-i2c";
45+ reg = <0xf8024000 0x4000>;
46+ interrupts = <34 4 6>;
47+ dmas = <&dma1
48+ (AT91_XDMAC_DT_MEM_IF(0) | AT91_XDMAC_DT_PER_IF(1)
49+ | AT91_XDMAC_DT_PERID(6))>,
50+ <&dma1
51+ (AT91_XDMAC_DT_MEM_IF(0) | AT91_XDMAC_DT_PER_IF(1)
52+ | AT91_XDMAC_DT_PERID(7))>;
53+ dma-names = "tx", "rx";
54+};
Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt+1−0
@@ -48,6 +48,7 @@ The full ID of peripheral types can be found below. · 47 unmodified lines
4848 21 ESAI
4949 22 SSI Dual FIFO (needs firmware ver >= 2)
5050 23 Shared ASRC
51+ 24 SAI
5152
5253 The third cell specifies the transfer priority as below.
5354
Documentation/devicetree/bindings/dma/qcom_adm.txt+62−0
@@ -0,0 +1,62 @@
1+QCOM ADM DMA Controller
2+
3+Required properties:
4+- compatible: must contain "qcom,adm" for IPQ/APQ8064 and MSM8960
5+- reg: Address range for DMA registers
6+- interrupts: Should contain one interrupt shared by all channels
7+- #dma-cells: must be <2>. First cell denotes the channel number. Second cell
8+ denotes CRCI (client rate control interface) flow control assignment.
9+- clocks: Should contain the core clock and interface clock.
10+- clock-names: Must contain "core" for the core clock and "iface" for the
11+ interface clock.
12+- resets: Must contain an entry for each entry in reset names.
13+- reset-names: Must include the following entries:
14+ - clk
15+ - c0
16+ - c1
17+ - c2
18+- qcom,ee: indicates the security domain identifier used in the secure world.
19+
20+Example:
21+ adm_dma: dma@18300000 {
22+ compatible = "qcom,adm";
23+ reg = <0x18300000 0x100000>;
24+ interrupts = <0 170 0>;
25+ #dma-cells = <2>;
26+
27+ clocks = <&gcc ADM0_CLK>, <&gcc ADM0_PBUS_CLK>;
28+ clock-names = "core", "iface";
29+
30+ resets = <&gcc ADM0_RESET>,
31+ <&gcc ADM0_C0_RESET>,
32+ <&gcc ADM0_C1_RESET>,
33+ <&gcc ADM0_C2_RESET>;
34+ reset-names = "clk", "c0", "c1", "c2";
35+ qcom,ee = <0>;
36+ };
37+
38+DMA clients must use the format descripted in the dma.txt file, using a three
39+cell specifier for each channel.
40+
41+Each dmas request consists of 3 cells:
42+ 1. phandle pointing to the DMA controller
43+ 2. channel number
44+ 3. CRCI assignment, if applicable. If no CRCI flow control is required, use 0.
45+ The CRCI is used for flow control. It identifies the peripheral device that
46+ is the source/destination for the transferred data.
47+
48+Example:
49+
50+ spi4: spi@1a280000 {
51+ status = "ok";
52+ spi-max-frequency = <50000000>;
53+
54+ pinctrl-0 = <&spi_pins>;
55+ pinctrl-names = "default";
56+
57+ cs-gpios = <&qcom_pinmux 20 0>;
58+
59+ dmas = <&adm_dma 6 9>,
60+ <&adm_dma 5 10>;
61+ dma-names = "rx", "tx";
62+ };
Documentation/devicetree/bindings/dma/qcom_bam_dma.txt+3−1
@@ -1,7 +1,9 @@
11 QCOM BAM DMA controller
22
33 Required properties:
4−- compatible: must contain "qcom,bam-v1.4.0" for MSM8974
4+- compatible: must be one of the following:
5+ * "qcom,bam-v1.4.0" for MSM8974, APQ8074 and APQ8084
6+ * "qcom,bam-v1.3.0" for APQ8064, IPQ8064 and MSM8960
57 - reg: Address range for DMA registers
68 - interrupts: Should contain the one interrupt shared by all channels
79 - #dma-cells: must be <1>, the cell in the dmas property of the client device
Documentation/devicetree/bindings/dma/sun6i-dma.txt+1−1
@@ -4,7 +4,7 @@ This driver follows the generic DMA bindings defined in dma.txt. · 3 unmodified lines
44
55 Required properties:
66
7−- compatible: Must be "allwinner,sun6i-a31-dma"
7+- compatible: Must be "allwinner,sun6i-a31-dma" or "allwinner,sun8i-a23-dma"
88 - reg: Should contain the registers base address and length
99 - interrupts: Should contain a reference to the interrupt used by this device
1010 - clocks: Should contain a reference to the parent AHB clock
Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt+65−0
@@ -0,0 +1,65 @@
1+Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream
2+target devices. It can be configured to have one channel or two channels.
3+If configured as two channels, one is to transmit to the device and another
4+is to receive from the device.
5+
6+Required properties:
7+- compatible: Should be "xlnx,axi-dma-1.00.a"
8+- #dma-cells: Should be <1>, see "dmas" property below
9+- reg: Should contain DMA registers location and length.
10+- dma-channel child node: Should have atleast one channel and can have upto
11+ two channels per device. This node specifies the properties of each
12+ DMA channel (see child node properties below).
13+
14+Optional properties:
15+- xlnx,include-sg: Tells whether configured for Scatter-mode in
16+ the hardware.
17+
18+Required child node properties:
19+- compatible: It should be either "xlnx,axi-dma-mm2s-channel" or
20+ "xlnx,axi-dma-s2mm-channel".
21+- interrupts: Should contain per channel DMA interrupts.
22+- xlnx,datawidth: Should contain the stream data width, take values
23+ {32,64...1024}.
24+
25+Option child node properties:
26+- xlnx,include-dre: Tells whether hardware is configured for Data
27+ Realignment Engine.
28+
29+Example:
30+++++++++
31+
32+axi_dma_0: axidma@40400000 {
33+ compatible = "xlnx,axi-dma-1.00.a";
34+ #dma_cells = <1>;
35+ reg = < 0x40400000 0x10000 >;
36+ dma-channel@40400000 {
37+ compatible = "xlnx,axi-dma-mm2s-channel";
38+ interrupts = < 0 59 4 >;
39+ xlnx,datawidth = <0x40>;
40+ } ;
41+ dma-channel@40400030 {
42+ compatible = "xlnx,axi-dma-s2mm-channel";
43+ interrupts = < 0 58 4 >;
44+ xlnx,datawidth = <0x40>;
45+ } ;
46+} ;
47+
48+
49+* DMA client
50+
51+Required properties:
52+- dmas: a list of <[DMA device phandle] [Channel ID]> pairs,
53+ where Channel ID is '0' for write/tx and '1' for read/rx
54+ channel.
55+- dma-names: a list of DMA channel names, one per "dmas" entry
56+
57+Example:
58+++++++++
59+
60+dmatest_0: dmatest@0 {
61+ compatible ="xlnx,axi-dma-test-1.00.a";
62+ dmas = <&axi_dma_0 0
63+ &axi_dma_0 1>;
64+ dma-names = "dma0", "dma1";
65+} ;
Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt+1−1
@@ -25,7 +25,7 @@ Required child node properties: · 24 unmodified lines
2525 - compatible: It should be either "xlnx,axi-vdma-mm2s-channel" or
2626 "xlnx,axi-vdma-s2mm-channel".
2727 - interrupts: Should contain per channel VDMA interrupts.
28−- xlnx,data-width: Should contain the stream data width, take values
28+- xlnx,datawidth: Should contain the stream data width, take values
2929 {32,64...1024}.
3030
3131 Optional child node properties:
Documentation/devicetree/bindings/drm/imx/fsl-imx-drm.txtrenamed from Documentation/devicetree/bindings/staging/imx-drm/fsl-imx-drm.txt+0−0

File renamed without changes.

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

File renamed without changes.

Documentation/devicetree/bindings/drm/imx/ldb.txtrenamed from Documentation/devicetree/bindings/staging/imx-drm/ldb.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/drm/tilcdc/panel.txt+7−0
@@ -18,6 +18,10 @@ Required properties: · 17 unmodified lines
1818 Documentation/devicetree/bindings/video/display-timing.txt for display
1919 timing binding details.
2020
21+Optional properties:
22+- backlight: phandle of the backlight device attached to the panel
23+- enable-gpios: GPIO pin to enable or disable the panel
24+
2125 Recommended properties:
2226 - pinctrl-names, pinctrl-0: the pincontrol settings to configure
2327 muxing properly for pins that connect to TFP410 device
@@ -29,6 +33,9 @@ Example: · 5 unmodified lines
2933 compatible = "ti,tilcdc,panel";
3034 pinctrl-names = "default";
3135 pinctrl-0 = <&bone_lcd3_cape_lcd_pins>;
36+ backlight = <&backlight>;
37+ enable-gpios = <&gpio3 19 0>;
38+
3239 panel-info {
3340 ac-bias = <255>;
3441 ac-bias-intrpt = <0>;
Documentation/devicetree/bindings/extcon/extcon-rt8973a.txt+25−0
@@ -0,0 +1,25 @@
1+
2+* Richtek RT8973A - Micro USB Switch device
3+
4+The Richtek RT8973A is Micro USB Switch with OVP and I2C interface. The RT8973A
5+is a USB port accessory detector and switch that is optimized to protect low
6+voltage system from abnormal high input voltage (up to 28V) and supports high
7+speed USB operation. Also, RT8973A support 'auto-configuration' mode.
8+If auto-configuration mode is enabled, RT8973A would control internal h/w patch
9+for USB D-/D+ switching.
10+
11+Required properties:
12+- compatible: Should be "richtek,rt8973a-muic"
13+- reg: Specifies the I2C slave address of the MUIC block. It should be 0x14
14+- interrupt-parent: Specifies the phandle of the interrupt controller to which
15+ the interrupts from rt8973a are delivered to.
16+- interrupts: Interrupt specifiers for detection interrupt sources.
17+
18+Example:
19+
20+ rt8973a@14 {
21+ compatible = "richtek,rt8973a-muic";
22+ interrupt-parent = <&gpx1>;
23+ interrupts = <5 0>;
24+ reg = <0x14>;
25+ };
Documentation/devicetree/bindings/gpio/gpio-74xx-mmio.txt+30−0
@@ -0,0 +1,30 @@
1+* 74XX MMIO GPIO driver
2+
3+Required properties:
4+- compatible: Should contain one of the following:
5+ "ti,741g125": for 741G125 (1-bit Input),
6+ "ti,741g174": for 741G74 (1-bit Output),
7+ "ti,742g125": for 742G125 (2-bit Input),
8+ "ti,7474" : for 7474 (2-bit Output),
9+ "ti,74125" : for 74125 (4-bit Input),
10+ "ti,74175" : for 74175 (4-bit Output),
11+ "ti,74365" : for 74365 (6-bit Input),
12+ "ti,74174" : for 74174 (6-bit Output),
13+ "ti,74244" : for 74244 (8-bit Input),
14+ "ti,74273" : for 74273 (8-bit Output),
15+ "ti,741624" : for 741624 (16-bit Input),
16+ "ti,7416374": for 7416374 (16-bit Output).
17+- reg: Physical base address and length where IC resides.
18+- gpio-controller: Marks the device node as a gpio controller.
19+- #gpio-cells: Should be two. The first cell is the pin number and
20+ the second cell is used to specify the GPIO polarity:
21+ 0 = Active High,
22+ 1 = Active Low.
23+
24+Example:
25+ ctrl: gpio@30008004 {
26+ compatible = "ti,74174";
27+ reg = <0x30008004 0x1>;
28+ gpio-controller;
29+ #gpio-cells = <2>;
30+ };
Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt+39−0
@@ -0,0 +1,39 @@
1+Keystone 2 DSP GPIO controller bindings
2+
3+HOST OS userland running on ARM can send interrupts to DSP cores using
4+the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
5+This is one of the component used by the IPC mechanism used on Keystone SOCs.
6+
7+For example TCI6638K2K SoC has 8 DSP GPIO controllers:
8+ - 8 for C66x CorePacx CPUs 0-7
9+
10+Keystone 2 DSP GPIO controller has specific features:
11+- each GPIO can be configured only as output pin;
12+- setting GPIO value to 1 causes IRQ generation on target DSP core;
13+- reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
14+ pending.
15+
16+Required Properties:
17+- compatible: should be "ti,keystone-dsp-gpio"
18+- ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
19+ access device state control registers and the offset of device's specific
20+ registers within device state control registers range.
21+- gpio-controller: Marks the device node as a gpio controller.
22+- #gpio-cells: Should be 2.
23+
24+Please refer to gpio.txt in this directory for details of the common GPIO
25+bindings used by client devices.
26+
27+Example:
28+ dspgpio0: keystone_dsp_gpio@02620240 {
29+ compatible = "ti,keystone-dsp-gpio";
30+ ti,syscon-dev = <&devctrl 0x240>;
31+ gpio-controller;
32+ #gpio-cells = <2>;
33+ };
34+
35+ dsp0: dsp0 {
36+ compatible = "linux,rproc-user";
37+ ...
38+ kick-gpio = <&dspgpio0 27>;
39+ };
Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt+2−0
@@ -57,6 +57,8 @@ Optional device specific properties: · 56 unmodified lines
5757 occurred on. If it is not set, the interrupt are only generated for the
5858 bank they belong to.
5959 On devices with only one interrupt output this property is useless.
60+- microchip,irq-active-high: Sets the INTPOL flag in the IOCON register. This
61+ configures the IRQ output polarity as active high.
6062
6163 Example I2C (with interrupt):
6264 gpiom1: gpio@20 {
Documentation/devicetree/bindings/gpio/gpio-pca953x.txt+39−0
@@ -0,0 +1,39 @@
1+* NXP PCA953x I2C GPIO multiplexer
2+
3+Required properties:
4+ - compatible: Has to contain one of the following:
5+ nxp,pca9505
6+ nxp,pca9534
7+ nxp,pca9535
8+ nxp,pca9536
9+ nxp,pca9537
10+ nxp,pca9538
11+ nxp,pca9539
12+ nxp,pca9554
13+ nxp,pca9555
14+ nxp,pca9556
15+ nxp,pca9557
16+ nxp,pca9574
17+ nxp,pca9575
18+ nxp,pca9698
19+ maxim,max7310
20+ maxim,max7312
21+ maxim,max7313
22+ maxim,max7315
23+ ti,pca6107
24+ ti,tca6408
25+ ti,tca6416
26+ ti,tca6424
27+ exar,xra1202
28+
29+Example:
30+
31+
32+ gpio@20 {
33+ compatible = "nxp,pca9505";
34+ reg = <0x20>;
35+ pinctrl-names = "default";
36+ pinctrl-0 = <&pinctrl_pca9505>;
37+ interrupt-parent = <&gpio3>;
38+ interrupts = <23 IRQ_TYPE_LEVEL_LOW>;
39+ };
Documentation/devicetree/bindings/gpio/gpio-restart.txt+54−0
@@ -0,0 +1,54 @@
1+Drive a GPIO line that can be used to restart the system from a restart
2+handler.
3+
4+This binding supports level and edge triggered reset. At driver load
5+time, the driver will request the given gpio line and install a restart
6+handler. If the optional properties 'open-source' is not found, the GPIO line
7+will be driven in the inactive state. Otherwise its not driven until
8+the restart is initiated.
9+
10+When the system is restarted, the restart handler will be invoked in
11+priority order. The gpio is configured as an output, and driven active,
12+triggering a level triggered reset condition. This will also cause an
13+inactive->active edge condition, triggering positive edge triggered
14+reset. After a delay specified by active-delay, the GPIO is set to
15+inactive, thus causing an active->inactive edge, triggering negative edge
16+triggered reset. After a delay specified by inactive-delay, the GPIO
17+is driven active again. After a delay specified by wait-delay, the
18+restart handler completes allowing other restart handlers to be attempted.
19+
20+Required properties:
21+- compatible : should be "gpio-restart".
22+- gpios : The GPIO to set high/low, see "gpios property" in
23+ Documentation/devicetree/bindings/gpio/gpio.txt. If the pin should be
24+ low to reset the board set it to "Active Low", otherwise set
25+ gpio to "Active High".
26+
27+Optional properties:
28+- open-source : Treat the GPIO as being open source and defer driving
29+ it to when the restart is initiated. If this optional property is not
30+ specified, the GPIO is initialized as an output in its inactive state.
31+- priority : A priority ranging from 0 to 255 (default 128) according to
32+ the following guidelines:
33+ 0: Restart handler of last resort, with limited restart
34+ capabilities
35+ 128: Default restart handler; use if no other restart handler is
36+ expected to be available, and/or if restart functionality is
37+ sufficient to restart the entire system
38+ 255: Highest priority restart handler, will preempt all other
39+ restart handlers
40+- active-delay: Delay (default 100) to wait after driving gpio active [ms]
41+- inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
42+- wait-delay: Delay (default 3000) to wait after completing restart
43+ sequence [ms]
44+
45+Examples:
46+
47+gpio-restart {
48+ compatible = "gpio-restart";
49+ gpios = <&gpio 4 0>;
50+ priority = <128>;
51+ active-delay = <100>;
52+ inactive-delay = <100>;
53+ wait-delay = <3000>;
54+};
Documentation/devicetree/bindings/gpio/gpio-vf610.txt+55−0
@@ -0,0 +1,55 @@
1+* Freescale VF610 PORT/GPIO module
2+
3+The Freescale PORT/GPIO modules are two adjacent modules providing GPIO
4+functionality. Each pair serves 32 GPIOs. The VF610 has 5 instances of
5+each, and each PORT module has its own interrupt.
6+
7+Required properties for GPIO node:
8+- compatible : Should be "fsl,<soc>-gpio", currently "fsl,vf610-gpio"
9+- reg : The first reg tuple represents the PORT module, the second tuple
10+ the GPIO module.
11+- interrupts : Should be the port interrupt shared by all 32 pins.
12+- gpio-controller : Marks the device node as a gpio controller.
13+- #gpio-cells : Should be two. The first cell is the pin number and
14+ the second cell is used to specify the gpio polarity:
15+ 0 = active high
16+ 1 = active low
17+- interrupt-controller: Marks the device node as an interrupt controller.
18+- #interrupt-cells : Should be 2. The first cell is the GPIO number.
19+ The second cell bits[3:0] is used to specify trigger type and level flags:
20+ 1 = low-to-high edge triggered.
21+ 2 = high-to-low edge triggered.
22+ 4 = active high level-sensitive.
23+ 8 = active low level-sensitive.
24+
25+Note: Each GPIO port should have an alias correctly numbered in "aliases"
26+node.
27+
28+Examples:
29+
30+aliases {
31+ gpio0 = &gpio1;
32+ gpio1 = &gpio2;
33+};
34+
35+gpio1: gpio@40049000 {
36+ compatible = "fsl,vf610-gpio";
37+ reg = <0x40049000 0x1000 0x400ff000 0x40>;
38+ interrupts = <0 107 IRQ_TYPE_LEVEL_HIGH>;
39+ gpio-controller;
40+ #gpio-cells = <2>;
41+ interrupt-controller;
42+ #interrupt-cells = <2>;
43+ gpio-ranges = <&iomuxc 0 0 32>;
44+};
45+
46+gpio2: gpio@4004a000 {
47+ compatible = "fsl,vf610-gpio";
48+ reg = <0x4004a000 0x1000 0x400ff040 0x40>;
49+ interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>;
50+ gpio-controller;
51+ #gpio-cells = <2>;
52+ interrupt-controller;
53+ #interrupt-cells = <2>;
54+ gpio-ranges = <&iomuxc 0 32 32>;
55+};
Documentation/devicetree/bindings/gpio/gpio-xgene.txt+22−0
@@ -0,0 +1,22 @@
1+APM X-Gene SoC GPIO controller bindings
2+
3+This is a gpio controller that is part of the flash controller.
4+This gpio controller controls a total of 48 gpios.
5+
6+Required properties:
7+- compatible: "apm,xgene-gpio" for X-Gene GPIO controller
8+- reg: Physical base address and size of the controller's registers
9+- #gpio-cells: Should be two.
10+ - first cell is the pin number
11+ - second cell is used to specify the gpio polarity:
12+ 0 = active high
13+ 1 = active low
14+- gpio-controller: Marks the device node as a GPIO controller.
15+
16+Example:
17+ gpio0: gpio0@1701c000 {
18+ compatible = "apm,xgene-gpio";
19+ reg = <0x0 0x1701c000 0x0 0x40>;
20+ gpio-controller;
21+ #gpio-cells = <2>;
22+ };
Documentation/devicetree/bindings/gpio/gpio.txt+26−14
@@ -13,13 +13,22 @@ properties, each containing a 'gpio-list': · 12 unmodified lines
1313 gpio-specifier : Array of #gpio-cells specifying specific gpio
1414 (controller specific)
1515
16−GPIO properties should be named "[<name>-]gpios". The exact
17−meaning of each gpios property must be documented in the device tree
18−binding for each device.
16+GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
17+of this GPIO for the device. While a non-existent <name> is considered valid
18+for compatibility reasons (resolving to the "gpios" property), it is not allowed
19+for new bindings.
1920
20−For example, the following could be used to describe GPIO pins used
21−as chip select lines; with chip selects 0, 1 and 3 populated, and chip
22−select 2 left empty:
21+GPIO properties can contain one or more GPIO phandles, but only in exceptional
22+cases should they contain more than one. If your device uses several GPIOs with
23+distinct functions, reference each of them under its own property, giving it a
24+meaningful name. The only case where an array of GPIOs is accepted is when
25+several GPIOs serve the same function (e.g. a parallel data line).
26+
27+The exact purpose of each gpios property must be documented in the device tree
28+binding of the device.
29+
30+The following example could be used to describe GPIO pins used as device enable
31+and bit-banged data signals:
2332
2433 gpio1: gpio1 {
2534 gpio-controller
@@ -30,10 +39,12 @@ select 2 left empty: · 4 unmodified lines
3039 #gpio-cells = <1>;
3140 };
3241 [...]
33− chipsel-gpios = <&gpio1 12 0>,
34− <&gpio1 13 0>,
35− <0>, /* holes are permitted, means no GPIO 2 */
36− <&gpio2 2>;
42+
43+ enable-gpios = <&gpio2 2>;
44+ data-gpios = <&gpio1 12 0>,
45+ <&gpio1 13 0>,
46+ <&gpio1 14 0>,
47+ <&gpio1 15 0>;
3748
3849 Note that gpio-specifier length is controller dependent. In the
3950 above example, &gpio1 uses 2 cells to specify a gpio, while &gpio2
@@ -42,16 +53,17 @@ only uses one. · 2 unmodified lines
4253 gpio-specifier may encode: bank, pin position inside the bank,
4354 whether pin is open-drain and whether pin is logically inverted.
4455 Exact meaning of each specifier cell is controller specific, and must
45−be documented in the device tree binding for the device.
56+be documented in the device tree binding for the device. Use the macros
57+defined in include/dt-bindings/gpio/gpio.h whenever possible:
4658
4759 Example of a node using GPIOs:
4860
4961 node {
50− gpios = <&qe_pio_e 18 0>;
62+ enable-gpios = <&qe_pio_e 18 GPIO_ACTIVE_HIGH>;
5163 };
5264
53−In this example gpio-specifier is "18 0" and encodes GPIO pin number,
54−and GPIO flags as accepted by the "qe_pio_e" gpio-controller.
65+GPIO_ACTIVE_HIGH is 0, so in this example gpio-specifier is "18 0" and encodes
66+GPIO pin number, and GPIO flags as accepted by the "qe_pio_e" gpio-controller.
5567
5668 1.1) GPIO specifier best practices
5769 ----------------------------------
Documentation/devicetree/bindings/gpio/mrvl-gpio.txt+14−1
@@ -19,7 +19,7 @@ Required properties: · 18 unmodified lines
1919 - gpio-controller : Marks the device node as a gpio controller.
2020 - #gpio-cells : Should be one. It is the pin number.
2121
22−Example:
22+Example for a MMP platform:
2323
2424 gpio: gpio@d4019000 {
2525 compatible = "marvell,mmp-gpio";
@@ -32,6 +32,19 @@ Example: · 6 unmodified lines
3232 #interrupt-cells = <1>;
3333 };
3434
35+Example for a PXA3xx platform:
36+
37+ gpio: gpio@40e00000 {
38+ compatible = "intel,pxa3xx-gpio";
39+ reg = <0x40e00000 0x10000>;
40+ interrupt-names = "gpio0", "gpio1", "gpio_mux";
41+ interrupts = <8 9 10>;
42+ gpio-controller;
43+ #gpio-cells = <0x2>;
44+ interrupt-controller;
45+ #interrupt-cells = <0x2>;
46+ };
47+
3548 * Marvell Orion GPIO Controller
3649
3750 Required properties:
Documentation/devicetree/bindings/gpio/pl061-gpio.txt+1−1
@@ -7,4 +7,4 @@ Required properties: · 6 unmodified lines
77 - bit 0 specifies polarity (0 for normal, 1 for inverted)
88 - gpio-controller : Marks the device node as a GPIO controller.
99 - interrupts : Interrupt mapping for GPIO IRQ.
10−
10+- gpio-ranges : Interaction with the PINCTRL subsystem.
Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt+3−1
@@ -6,7 +6,9 @@ Required Properties: · 5 unmodified lines
66 - "renesas,gpio-r8a7778": for R8A7778 (R-Mobile M1) compatible GPIO controller.
77 - "renesas,gpio-r8a7779": for R8A7779 (R-Car H1) compatible GPIO controller.
88 - "renesas,gpio-r8a7790": for R8A7790 (R-Car H2) compatible GPIO controller.
9− - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2) compatible GPIO controller.
9+ - "renesas,gpio-r8a7791": for R8A7791 (R-Car M2-W) compatible GPIO controller.
10+ - "renesas,gpio-r8a7793": for R8A7793 (R-Car M2-N) compatible GPIO controller.
11+ - "renesas,gpio-r8a7794": for R8A7794 (R-Car E2) compatible GPIO controller.
1012 - "renesas,gpio-rcar": for generic R-Car GPIO controller.
1113
1214 - reg: Base address and length of each memory resource used by the GPIO
Documentation/devicetree/bindings/gpu/nvidia,tegra20-host1x.txt+2−0
@@ -191,6 +191,8 @@ of the following host1x client modules: · 190 unmodified lines
191191 - nvidia,hpd-gpio: specifies a GPIO used for hotplug detection
192192 - nvidia,edid: supplies a binary EDID blob
193193 - nvidia,panel: phandle of a display panel
194+ - nvidia,ganged-mode: contains a phandle to a second DSI controller to gang
195+ up with in order to support up to 8 data lanes
194196
195197 - sor: serial output resource
196198
Documentation/devicetree/bindings/gpu/st,stih4xx.txt+27−2
@@ -68,7 +68,7 @@ STMicroelectronics stih4xx platforms · 67 unmodified lines
6868 number of clocks may depend of the SoC type.
6969 - clock-names: names of the clocks listed in clocks property in the same
7070 order.
71− - hdmi,hpd-gpio: gpio id to detect if an hdmi cable is plugged or not.
71+ - ddc: phandle of an I2C controller used for DDC EDID probing
7272
7373 sti-hda:
7474 Required properties:
@@ -83,6 +83,22 @@ sti-hda: · 8 unmodified lines
8383 - clock-names: names of the clocks listed in clocks property in the same
8484 order.
8585
86+sti-hqvdp:
87+ must be a child of sti-display-subsystem
88+ Required properties:
89+ - compatible: "st,stih<chip>-hqvdp"
90+ - reg: Physical base address of the IP registers and length of memory mapped region.
91+ - clocks: from common clock binding: handle hardware IP needed clocks, the
92+ number of clocks may depend of the SoC type.
93+ See ../clocks/clock-bindings.txt for details.
94+ - clock-names: names of the clocks listed in clocks property in the same
95+ order.
96+ - resets: resets to be used by the device
97+ See ../reset/reset.txt for details.
98+ - reset-names: names of the resets listed in resets property in the same
99+ order.
100+ - st,vtg: phandle on vtg main device node.
101+
86102 Example:
87103
88104 / {
@@ -173,7 +189,6 @@ Example: · 84 unmodified lines
173189 interrupt-names = "irq";
174190 clock-names = "pix", "tmds", "phy", "audio";
175191 clocks = <&clockgen_c_vcc CLK_S_PIX_HDMI>, <&clockgen_c_vcc CLK_S_TMDS_HDMI>, <&clockgen_c_vcc CLK_S_HDMI_REJECT_PLL>, <&clockgen_b1 CLK_S_PCM_0>;
176− hdmi,hpd-gpio = <&PIO2 5>;
177192 };
178193
179194 sti-hda@fe85a000 {
@@ -184,6 +199,16 @@ Example: · 4 unmodified lines
184199 clocks = <&clockgen_c_vcc CLK_S_PIX_HD>, <&clockgen_c_vcc CLK_S_HDDAC>;
185200 };
186201 };
202+
203+ sti-hqvdp@9c000000 {
204+ compatible = "st,stih407-hqvdp";
205+ reg = <0x9C00000 0x100000>;
206+ clock-names = "hqvdp", "pix_main";
207+ clocks = <&clk_s_c0_flexgen CLK_MAIN_DISP>, <&clk_s_d2_flexgen CLK_PIX_MAIN_DISP>;
208+ reset-names = "hqvdp";
209+ resets = <&softreset STIH407_HDQVDP_SOFTRESET>;
210+ st,vtg = <&vtg_main>;
211+ };
187212 };
188213 ...
189214 };
Documentation/devicetree/bindings/hwmon/ltc2978.txt+39−0
@@ -0,0 +1,39 @@
1+ltc2978
2+
3+Required properties:
4+- compatible: should contain one of:
5+ * "lltc,ltc2974"
6+ * "lltc,ltc2977"
7+ * "lltc,ltc2978"
8+ * "lltc,ltc3880"
9+ * "lltc,ltc3883"
10+ * "lltc,ltm4676"
11+- reg: I2C slave address
12+
13+Optional properties:
14+- regulators: A node that houses a sub-node for each regulator controlled by
15+ the device. Each sub-node is identified using the node's name, with valid
16+ values listed below. The content of each sub-node is defined by the
17+ standard binding for regulators; see regulator.txt.
18+
19+Valid names of regulators depend on number of supplies supported per device:
20+ * ltc2974 : vout0 - vout3
21+ * ltc2977 : vout0 - vout7
22+ * ltc2978 : vout0 - vout7
23+ * ltc3880 : vout0 - vout1
24+ * ltc3883 : vout0
25+ * ltm4676 : vout0 - vout1
26+
27+Example:
28+ltc2978@5e {
29+ compatible = "lltc,ltc2978";
30+ reg = <0x5e>;
31+ regulators {
32+ vout0 {
33+ regulator-name = "FPGA-2.5V";
34+ };
35+ vout2 {
36+ regulator-name = "FPGA-1.5V";
37+ };
38+ };
39+};
Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt+3−0
@@ -25,6 +25,9 @@ Requires node properties: · 24 unmodified lines
2525 - "io-channels" Channel node of ADC to be used for
2626 conversion.
2727
28+Optional node properties:
29+- "#thermal-sensor-cells" Used to expose itself to thermal fw.
30+
2831 Read more about iio bindings at
2932 Documentation/devicetree/bindings/iio/iio-bindings.txt
3033
Documentation/devicetree/bindings/hwrng/atmel-trng.txt+16−0
@@ -0,0 +1,16 @@
1+Atmel TRNG (True Random Number Generator) block
2+
3+Required properties:
4+- compatible : Should be "atmel,at91sam9g45-trng"
5+- reg : Offset and length of the register set of this block
6+- interrupts : the interrupt number for the TRNG block
7+- clocks: should contain the TRNG clk source
8+
9+Example:
10+
11+trng@fffcc000 {
12+ compatible = "atmel,at91sam9g45-trng";
13+ reg = <0xfffcc000 0x4000>;
14+ interrupts = <6 IRQ_TYPE_LEVEL_HIGH 0>;
15+ clocks = <&trng_clk>;
16+};
Documentation/devicetree/bindings/i2c/i2c-axxia.txt+30−0
@@ -0,0 +1,30 @@
1+LSI Axxia I2C
2+
3+Required properties :
4+- compatible : Must be "lsi,api2c"
5+- reg : Offset and length of the register set for the device
6+- interrupts : the interrupt specifier
7+- #address-cells : Must be <1>;
8+- #size-cells : Must be <0>;
9+- clock-names : Must contain "i2c".
10+- clocks: Must contain an entry for each name in clock-names. See the common
11+ clock bindings.
12+
13+Optional properties :
14+- clock-frequency : Desired I2C bus clock frequency in Hz. If not specified,
15+ the default 100 kHz frequency will be used. As only Normal and Fast modes
16+ are supported, possible values are 100000 and 400000.
17+
18+Example :
19+
20+i2c@02010084000 {
21+ compatible = "lsi,api2c";
22+ device_type = "i2c";
23+ #address-cells = <1>;
24+ #size-cells = <0>;
25+ reg = <0x20 0x10084000 0x00 0x1000>;
26+ interrupts = <0 19 4>;
27+ clocks = <&clk_per>;
28+ clock-names = "i2c";
29+ clock-frequency = <400000>;
30+};
Documentation/devicetree/bindings/i2c/i2c-designware.txt+2−2
@@ -14,10 +14,10 @@ Optional properties : · 13 unmodified lines
1414 - i2c-sda-hold-time-ns : should contain the SDA hold time in nanoseconds.
1515 This option is only supported in hardware blocks version 1.11a or newer.
1616
17− - i2c-scl-falling-time : should contain the SCL falling time in nanoseconds.
17+ - i2c-scl-falling-time-ns : should contain the SCL falling time in nanoseconds.
1818 This value which is by default 300ns is used to compute the tLOW period.
1919
20− - i2c-sda-falling-time : should contain the SDA falling time in nanoseconds.
20+ - i2c-sda-falling-time-ns : should contain the SDA falling time in nanoseconds.
2121 This value which is by default 300ns is used to compute the tHIGH period.
2222
2323 Example :
Documentation/devicetree/bindings/i2c/i2c-exynos5.txt+2−0
@@ -12,6 +12,8 @@ Required properties: · 11 unmodified lines
1212 on Exynos5250 and Exynos5420 SoCs.
1313 -> "samsung,exynos5260-hsi2c", for i2c compatible with HSI2C available
1414 on Exynos5260 SoCs.
15+ -> "samsung,exynos7-hsi2c", for i2c compatible with HSI2C available
16+ on Exynos7 SoCs.
1517
1618 - reg: physical base address of the controller and length of memory mapped
1719 region.
Documentation/devicetree/bindings/i2c/i2c-hix5hd2.txt+24−0
@@ -0,0 +1,24 @@
1+I2C for Hisilicon hix5hd2 chipset platform
2+
3+Required properties:
4+- compatible: Must be "hisilicon,hix5hd2-i2c"
5+- reg: physical base address of the controller and length of memory mapped
6+ region.
7+- interrupts: interrupt number to the cpu.
8+- #address-cells = <1>;
9+- #size-cells = <0>;
10+- clocks: phandles to input clocks.
11+
12+Optional properties:
13+- clock-frequency: Desired I2C bus frequency in Hz, otherwise defaults to 100000
14+- Child nodes conforming to i2c bus binding
15+
16+Examples:
17+I2C0@f8b10000 {
18+ compatible = "hisilicon,hix5hd2-i2c";
19+ reg = <0xf8b10000 0x1000>;
20+ interrupts = <0 38 4>;
21+ clocks = <&clock HIX5HD2_I2C0_RST>;
22+ #address-cells = <1>;
23+ #size-cells = <0>;
24+}
Documentation/devicetree/bindings/i2c/i2c-img-scb.txt+26−0
@@ -0,0 +1,26 @@
1+IMG Serial Control Bus (SCB) I2C Controller
2+
3+Required Properties:
4+- compatible: "img,scb-i2c"
5+- reg: Physical base address and length of controller registers
6+- interrupts: Interrupt number used by the controller
7+- clocks : Should contain a clock specifier for each entry in clock-names
8+- clock-names : Should contain the following entries:
9+ "scb", for the SCB core clock.
10+ "sys", for the system clock.
11+- clock-frequency: The I2C bus frequency in Hz
12+- #address-cells: Should be <1>
13+- #size-cells: Should be <0>
14+
15+Example:
16+
17+i2c@18100000 {
18+ compatible = "img,scb-i2c";
19+ reg = <0x18100000 0x200>;
20+ interrupts = <GIC_SHARED 2 IRQ_TYPE_LEVEL_HIGH>;
21+ clocks = <&i2c0_clk>, <&system_clk>;
22+ clock-names = "scb", "sys";
23+ clock-frequency = <400000>;
24+ #address-cells = <1>;
25+ #size-cells = <0>;
26+};
Documentation/devicetree/bindings/i2c/i2c-imx.txt+11−0
@@ -11,6 +11,8 @@ Required properties: · 10 unmodified lines
1111 Optional properties:
1212 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
1313 The absence of the propoerty indicates the default frequency 100 kHz.
14+- dmas: A list of two dma specifiers, one for each entry in dma-names.
15+- dma-names: should contain "tx" and "rx".
1416
1517 Examples:
1618
@@ -26,3 +28,12 @@ i2c@70038000 { /* HS-I2C on i.MX51 */ · 9 unmodified lines
2628 interrupts = <64>;
2729 clock-frequency = <400000>;
2830 };
31+
32+i2c0: i2c@40066000 { /* i2c0 on vf610 */
33+ compatible = "fsl,vf610-i2c";
34+ reg = <0x40066000 0x1000>;
35+ interrupts =<0 71 0x04>;
36+ dmas = <&edma0 0 50>,
37+ <&edma0 0 51>;
38+ dma-names = "rx","tx";
39+};
Documentation/devicetree/bindings/i2c/i2c-meson.txt+24−0
@@ -0,0 +1,24 @@
1+Amlogic Meson I2C controller
2+
3+Required properties:
4+ - compatible: must be "amlogic,meson6-i2c"
5+ - reg: physical address and length of the device registers
6+ - interrupts: a single interrupt specifier
7+ - clocks: clock for the device
8+ - #address-cells: should be <1>
9+ - #size-cells: should be <0>
10+
11+Optional properties:
12+- clock-frequency: the desired I2C bus clock frequency in Hz; in
13+ absence of this property the default value is used (100 kHz).
14+
15+Examples:
16+
17+ i2c@c8100500 {
18+ compatible = "amlogic,meson6-i2c";
19+ reg = <0xc8100500 0x20>;
20+ interrupts = <0 92 1>;
21+ clocks = <&clk81>;
22+ #address-cells = <1>;
23+ #size-cells = <0>;
24+ };
Documentation/devicetree/bindings/i2c/i2c-opal.txt+37−0
@@ -0,0 +1,37 @@
1+Device-tree bindings for I2C OPAL driver
2+----------------------------------------
3+
4+Most of the device node and properties layout is specific to the firmware and
5+used by the firmware itself for configuring the port. From the linux
6+perspective, the properties of use are "ibm,port-name" and "ibm,opal-id".
7+
8+Required properties:
9+
10+- reg: Port-id within a given master
11+- compatible: must be "ibm,opal-i2c"
12+- ibm,opal-id: Refers to a specific bus and used to identify it when calling
13+ the relevant OPAL functions.
14+- bus-frequency: Operating frequency of the i2c bus (in HZ). Informational for
15+ linux, used by the FW though.
16+
17+Optional properties:
18+- ibm,port-name: Firmware provides this name that uniquely identifies the i2c
19+ port.
20+
21+The node contains a number of other properties that are used by the FW itself
22+and depend on the specific hardware implementation. The example below depicts
23+a P8 on-chip bus.
24+
25+Example:
26+
27+i2c-bus@0 {
28+ reg = <0x0>;
29+ bus-frequency = <0x61a80>;
30+ compatible = "ibm,power8-i2c-port", "ibm,opal-i2c";
31+ ibm,opal-id = <0x1>;
32+ ibm,port-name = "p8_00000000_e1p0";
33+ #address-cells = <0x1>;
34+ phandle = <0x10000006>;
35+ #size-cells = <0x0>;
36+ linux,phandle = <0x10000006>;
37+};
Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt+1−0
@@ -32,6 +32,7 @@ Optional properties: · 31 unmodified lines
3232 specified, default value is 0.
3333 - samsung,i2c-max-bus-freq: Desired frequency in Hz of the bus. If not
3434 specified, the default value in Hz is 100000.
35+ - samsung,sysreg-phandle - handle to syscon used to control the system registers
3536
3637 Example:
3738
Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt+14−0
@@ -2,6 +2,15 @@ Device tree configuration for Renesas IIC (sh_mobile) driver · 1 unmodified line
22
33 Required properties:
44 - compatible : "renesas,iic-<soctype>". "renesas,rmobile-iic" as fallback
5+ Examples with soctypes are:
6+ - "renesas,iic-r8a73a4" (R-Mobile APE6)
7+ - "renesas,iic-r8a7740" (R-Mobile A1)
8+ - "renesas,iic-r8a7790" (R-Car H2)
9+ - "renesas,iic-r8a7791" (R-Car M2-W)
10+ - "renesas,iic-r8a7792" (R-Car V2H)
11+ - "renesas,iic-r8a7793" (R-Car M2-N)
12+ - "renesas,iic-r8a7794" (R-Car E2)
13+ - "renesas,iic-sh73a0" (SH-Mobile AG5)
514 - reg : address start and address range size of device
615 - interrupts : interrupt of device
716 - clocks : clock for device
@@ -10,6 +19,11 @@ Required properties: · 2 unmodified lines
1019
1120 Optional properties:
1221 - clock-frequency : frequency of bus clock in Hz. Default 100kHz if unset.
22+- dmas : Must contain a list of two references to DMA
23+ specifiers, one for transmission, and one for
24+ reception.
25+- dma-names : Must contain a list of two DMA names, "tx" and "rx".
26+
1327
1428 Pinctrl properties might be needed, too. See there.
1529
Documentation/devicetree/bindings/i2c/ti,bq32k.txt+18−0
@@ -0,0 +1,18 @@
1+* TI BQ32000 I2C Serial Real-Time Clock
2+
3+Required properties:
4+- compatible: Should contain "ti,bq32000".
5+- reg: I2C address for chip
6+
7+Optional properties:
8+- trickle-resistor-ohms : Selected resistor for trickle charger
9+ Values usable are 1120 and 20180
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+ bq32000: rtc@68 {
15+ compatible = "ti,bq32000";
16+ trickle-resistor-ohms = <1120>;
17+ reg = <0x68>;
18+ };
Documentation/devicetree/bindings/i2c/trivial-devices.txt+11−2
@@ -17,6 +17,9 @@ adi,adt7473 +/-1C TDM Extended Temp Range I.C · 16 unmodified lines
1717 adi,adt7475 +/-1C TDM Extended Temp Range I.C
1818 adi,adt7476 +/-1C TDM Extended Temp Range I.C
1919 adi,adt7490 +/-1C TDM Extended Temp Range I.C
20+adi,adxl345 Three-Axis Digital Accelerometer
21+adi,adxl346 Three-Axis Digital Accelerometer
22+adi,adxl34x Three-Axis Digital Accelerometer
2023 at,24c08 i2c serial eeprom (24cxx)
2124 atmel,24c00 i2c serial eeprom (24cxx)
2225 atmel,24c01 i2c serial eeprom (24cxx)
@@ -35,7 +38,6 @@ catalyst,24c32 i2c serial eeprom · 12 unmodified lines
3538 cirrus,cs42l51 Cirrus Logic CS42L51 audio codec
3639 dallas,ds1307 64 x 8, Serial, I2C Real-Time Clock
3740 dallas,ds1338 I2C RTC with 56-Byte NV RAM
38−dallas,ds1339 I2C Serial Real-Time Clock
3941 dallas,ds1340 I2C RTC with Trickle Charger
4042 dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
4143 dallas,ds1631 High-Precision Digital Thermometer
@@ -44,7 +46,7 @@ dallas,ds1775 Tiny Digital Thermometer and Thermostat · 2 unmodified lines
4446 dallas,ds3232 Extremely Accurate I²C RTC with Integrated Crystal and SRAM
4547 dallas,ds4510 CPU Supervisor with Nonvolatile Memory and Programmable I/O
4648 dallas,ds75 Digital Thermometer and Thermostat
47−dialog,da9053 DA9053: flexible system level PMIC with multicore support
49+dlg,da9053 DA9053: flexible system level PMIC with multicore support
4850 epson,rx8025 High-Stability. I2C-Bus INTERFACE REAL TIME CLOCK MODULE
4951 epson,rx8581 I2C-BUS INTERFACE REAL TIME CLOCK MODULE
5052 fsl,mag3110 MAG3110: Xtrinsic High Accuracy, 3D Magnetometer
@@ -57,6 +59,8 @@ gmt,g751 G751: Digital Temperature Sensor and Thermal Watchdog with Two-Wire In · 6 unmodified lines
5759 infineon,slb9635tt Infineon SLB9635 (Soft-) I2C TPM (old protocol, max 100khz)
5860 infineon,slb9645tt Infineon SLB9645 I2C TPM (new protocol, max 400khz)
5961 isl,isl12057 Intersil ISL12057 I2C RTC Chip
62+isil,isl29028 (deprecated, use isl)
63+isl,isl29028 Intersil ISL29028 Ambient Light and Proximity Sensor
6064 maxim,ds1050 5 Bit Programmable, Pulse-Width Modulator
6165 maxim,max1237 Low-Power, 4-/12-Channel, 2-Wire Serial, 12-Bit ADCs
6266 maxim,max6625 9-Bit/12-Bit Temperature Sensors with I²C-Compatible Serial Interface
@@ -75,7 +79,12 @@ ovti,ov5642 OV5642: Color CMOS QSXGA (5-megapixel) Image Sensor with OmniBSI an · 12 unmodified lines
7579 pericom,pt7c4338 Real-time Clock Module
7680 plx,pex8648 48-Lane, 12-Port PCI Express Gen 2 (5.0 GT/s) Switch
7781 ramtron,24c64 i2c serial eeprom (24cxx)
82+ricoh,r2025sd I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
83+ricoh,r2221tl I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
7884 ricoh,rs5c372a I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
85+ricoh,rs5c372b I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
86+ricoh,rv5c386 I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
87+ricoh,rv5c387a I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
7988 samsung,24ad0xd1 S524AD0XF1 (128K/256K-bit Serial EEPROM for Low Power)
8089 sii,s35390a 2-wire CMOS real-time clock
8190 st-micro,24c256 i2c serial eeprom (24cxx)
Documentation/devicetree/bindings/iio/adc/qcom,spmi-iadc.txt+46−0
@@ -0,0 +1,46 @@
1+Qualcomm's SPMI PMIC current ADC
2+
3+QPNP PMIC current ADC (IADC) provides interface to clients to read current.
4+A 16 bit ADC is used for current measurements. IADC can measure the current
5+through an external resistor (channel 1) or internal (built-in) resistor
6+(channel 0). When using an external resistor it is to be described by
7+qcom,external-resistor-micro-ohms property.
8+
9+IADC node:
10+
11+- compatible:
12+ Usage: required
13+ Value type: <string>
14+ Definition: Should contain "qcom,spmi-iadc".
15+
16+- reg:
17+ Usage: required
18+ Value type: <prop-encoded-array>
19+ Definition: IADC base address and length in the SPMI PMIC register map
20+
21+- interrupts:
22+ Usage: optional
23+ Value type: <prop-encoded-array>
24+ Definition: End of ADC conversion.
25+
26+- qcom,external-resistor-micro-ohms:
27+ Usage: optional
28+ Value type: <u32>
29+ Definition: Sense resister value in micro Ohm.
30+ If not defined value of 10000 micro Ohms will be used.
31+
32+Example:
33+ /* IADC node */
34+ pmic_iadc: iadc@3600 {
35+ compatible = "qcom,spmi-iadc";
36+ reg = <0x3600 0x100>;
37+ interrupts = <0x0 0x36 0x0 IRQ_TYPE_EDGE_RISING>;
38+ qcom,external-resistor-micro-ohms = <10000>;
39+ #io-channel-cells = <1>;
40+ };
41+
42+ /* IIO client node */
43+ bat {
44+ io-channels = <&pmic_iadc 0>;
45+ io-channel-names = "iadc";
46+ };
Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt+24−0
@@ -0,0 +1,24 @@
1+Rockchip Successive Approximation Register (SAR) A/D Converter bindings
2+
3+Required properties:
4+- compatible: Should be "rockchip,saradc" or "rockchip,rk3066-tsadc"
5+- reg: physical base address of the controller and length of memory mapped
6+ region.
7+- interrupts: The interrupt number to the cpu. The interrupt specifier format
8+ depends on the interrupt controller.
9+- clocks: Must contain an entry for each entry in clock-names.
10+- clock-names: Shall be "saradc" for the converter-clock, and "apb_pclk" for
11+ the peripheral clock.
12+- vref-supply: The regulator supply ADC reference voltage.
13+- #io-channel-cells: Should be 1, see ../iio-bindings.txt
14+
15+Example:
16+ saradc: saradc@2006c000 {
17+ compatible = "rockchip,saradc";
18+ reg = <0x2006c000 0x100>;
19+ interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
20+ clocks = <&cru SCLK_SARADC>, <&cru PCLK_SARADC>;
21+ clock-names = "saradc", "apb_pclk";
22+ #io-channel-cells = <1>;
23+ vref-supply = <&vcc18>;
24+ };
Documentation/devicetree/bindings/iio/adc/vf610-adc.txt+1−1
@@ -9,7 +9,7 @@ Required properties: · 8 unmodified lines
99 - interrupts: Should contain the interrupt for the device
1010 - clocks: The clock is needed by the ADC controller, ADC clock source is ipg clock.
1111 - clock-names: Must contain "adc", matching entry in the clocks property.
12−- vref-supply: The regulator supply ADC refrence voltage.
12+- vref-supply: The regulator supply ADC reference voltage.
1313
1414 Example:
1515 adc0: adc@4003b000 {
Documentation/devicetree/bindings/iio/dac/max5821.txt+14−0
@@ -0,0 +1,14 @@
1+Maxim max5821 DAC device driver
2+
3+Required properties:
4+ - compatible: Must be "maxim,max5821"
5+ - reg: Should contain the DAC I2C address
6+ - vref-supply: Phandle to the vref power supply
7+
8+Example:
9+
10+ max5821@38 {
11+ compatible = "maxim,max5821";
12+ reg = <0x38>;
13+ vref-supply = <&reg_max5821>;
14+ };
Documentation/devicetree/bindings/interrupt-controller/atmel,aic.txt+1−1
@@ -2,7 +2,7 @@ · 1 unmodified line
22
33 Required properties:
44 - compatible: Should be "atmel,<chip>-aic"
5− <chip> can be "at91rm9200" or "sama5d3"
5+ <chip> can be "at91rm9200", "sama5d3" or "sama5d4"
66 - interrupt-controller: Identifies the node as an interrupt controller.
77 - interrupt-parent: For single AIC system, it is an empty property.
88 - #interrupt-cells: The number of cells to define the interrupts. It should be 3.
Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7120-l2-intc.txt+96−0
@@ -0,0 +1,96 @@
1+Broadcom BCM7120-style Level 2 interrupt controller
2+
3+This interrupt controller hardware is a second level interrupt controller that
4+is hooked to a parent interrupt controller: e.g: ARM GIC for ARM-based
5+platforms. It can be found on BCM7xxx products starting with BCM7120.
6+
7+Such an interrupt controller has the following hardware design:
8+
9+- outputs multiple interrupts signals towards its interrupt controller parent
10+
11+- controls how some of the interrupts will be flowing, whether they will
12+ directly output an interrupt signal towards the interrupt controller parent,
13+ or if they will output an interrupt signal at this 2nd level interrupt
14+ controller, in particular for UARTs
15+
16+- typically has one 32-bit enable word and one 32-bit status word, but on
17+ some hardware may have more than one enable/status pair
18+
19+- no atomic set/clear operations
20+
21+- not all bits within the interrupt controller actually map to an interrupt
22+
23+The typical hardware layout for this controller is represented below:
24+
25+2nd level interrupt line Outputs for the parent controller (e.g: ARM GIC)
26+
27+0 -----[ MUX ] ------------|==========> GIC interrupt 75
28+ \-----------\
29+ |
30+1 -----[ MUX ] --------)---|==========> GIC interrupt 76
31+ \------------|
32+ |
33+2 -----[ MUX ] --------)---|==========> GIC interrupt 77
34+ \------------|
35+ |
36+3 ---------------------|
37+4 ---------------------|
38+5 ---------------------|
39+7 ---------------------|---|===========> GIC interrupt 66
40+9 ---------------------|
41+10 --------------------|
42+11 --------------------/
43+
44+6 ------------------------\
45+ |===========> GIC interrupt 64
46+8 ------------------------/
47+
48+12 ........................ X
49+13 ........................ X (not connected)
50+..
51+31 ........................ X
52+
53+Required properties:
54+
55+- compatible: should be "brcm,bcm7120-l2-intc"
56+- reg: specifies the base physical address and size of the registers;
57+ multiple pairs may be specified, with the first pair handling IRQ offsets
58+ 0..31 and the second pair handling 32..63
59+- interrupt-controller: identifies the node as an interrupt controller
60+- #interrupt-cells: specifies the number of cells needed to encode an interrupt
61+ source, should be 1.
62+- interrupt-parent: specifies the phandle to the parent interrupt controller
63+ this one is cascaded from
64+- interrupts: specifies the interrupt line(s) in the interrupt-parent controller
65+ node, valid values depend on the type of parent interrupt controller
66+- brcm,int-map-mask: 32-bits bit mask describing how many and which interrupts
67+ are wired to this 2nd level interrupt controller, and how they match their
68+ respective interrupt parents. Should match exactly the number of interrupts
69+ specified in the 'interrupts' property, multiplied by the number of
70+ enable/status register pairs implemented by this controller. For
71+ multiple parent IRQs with multiple enable/status words, this looks like:
72+ <irq0_w0 irq0_w1 irq1_w0 irq1_w1 ...>
73+
74+Optional properties:
75+
76+- brcm,irq-can-wake: if present, this means the L2 controller can be used as a
77+ wakeup source for system suspend/resume.
78+
79+- brcm,int-fwd-mask: if present, a bit mask to configure the interrupts which
80+ have a mux gate, typically UARTs. Setting these bits will make their
81+ respective interrupt outputs bypass this 2nd level interrupt controller
82+ completely; it is completely transparent for the interrupt controller
83+ parent. This should have one 32-bit word per enable/status pair.
84+
85+Example:
86+
87+irq0_intc: interrupt-controller@f0406800 {
88+ compatible = "brcm,bcm7120-l2-intc";
89+ interrupt-parent = <&intc>;
90+ #interrupt-cells = <1>;
91+ reg = <0xf0406800 0x8>;
92+ interrupt-controller;
93+ interrupts = <0x0 0x42 0x0>, <0x0 0x40 0x0>;
94+ brcm,int-map-mask = <0xeb8>, <0x140>;
95+ brcm,int-fwd-mask = <0x7>;
96+};
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt+0−4
@@ -30,10 +30,6 @@ should only be used when a device has multiple interrupt parents. · 29 unmodified lines
3030 Example:
3131 interrupts-extended = <&intc1 5 1>, <&intc2 1 0>;
3232
33−A device node may contain either "interrupts" or "interrupts-extended", but not
34−both. If both properties are present, then the operating system should log an
35−error and use only the data in "interrupts".
36−
3733 2) Interrupt controller nodes
3834 -----------------------------
3935
Documentation/devicetree/bindings/interrupt-controller/mips-gic.txt+55−0
@@ -0,0 +1,55 @@
1+MIPS Global Interrupt Controller (GIC)
2+
3+The MIPS GIC routes external interrupts to individual VPEs and IRQ pins.
4+It also supports local (per-processor) interrupts and software-generated
5+interrupts which can be used as IPIs. The GIC also includes a free-running
6+global timer, per-CPU count/compare timers, and a watchdog.
7+
8+Required properties:
9+- compatible : Should be "mti,gic".
10+- interrupt-controller : Identifies the node as an interrupt controller
11+- #interrupt-cells : Specifies the number of cells needed to encode an
12+ interrupt specifier. Should be 3.
13+ - The first cell is the type of interrupt, local or shared.
14+ See <include/dt-bindings/interrupt-controller/mips-gic.h>.
15+ - The second cell is the GIC interrupt number.
16+ - The third cell encodes the interrupt flags.
17+ See <include/dt-bindings/interrupt-controller/irq.h> for a list of valid
18+ flags.
19+
20+Optional properties:
21+- reg : Base address and length of the GIC registers. If not present,
22+ the base address reported by the hardware GCR_GIC_BASE will be used.
23+- mti,reserved-cpu-vectors : Specifies the list of CPU interrupt vectors
24+ to which the GIC may not route interrupts. Valid values are 2 - 7.
25+ This property is ignored if the CPU is started in EIC mode.
26+
27+Required properties for timer sub-node:
28+- compatible : Should be "mti,gic-timer".
29+- interrupts : Interrupt for the GIC local timer.
30+- clock-frequency : Clock frequency at which the GIC timers operate.
31+
32+Example:
33+
34+ gic: interrupt-controller@1bdc0000 {
35+ compatible = "mti,gic";
36+ reg = <0x1bdc0000 0x20000>;
37+
38+ interrupt-controller;
39+ #interrupt-cells = <3>;
40+
41+ mti,reserved-cpu-vectors = <7>;
42+
43+ timer {
44+ compatible = "mti,gic-timer";
45+ interrupts = <GIC_LOCAL 1 IRQ_TYPE_NONE>;
46+ clock-frequency = <50000000>;
47+ };
48+ };
49+
50+ uart@18101400 {
51+ ...
52+ interrupt-parent = <&gic>;
53+ interrupts = <GIC_SHARED 24 IRQ_TYPE_LEVEL_HIGH>;
54+ ...
55+ };
Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt+7−1
@@ -2,7 +2,13 @@ DT bindings for the R-/SH-Mobile irqpin controller · 1 unmodified line
22
33 Required properties:
44
5−- compatible: has to be "renesas,intc-irqpin"
5+- compatible: has to be "renesas,intc-irqpin-<soctype>", "renesas,intc-irqpin"
6+ as fallback.
7+ Examples with soctypes are:
8+ - "renesas,intc-irqpin-r8a7740" (R-Mobile A1)
9+ - "renesas,intc-irqpin-r8a7778" (R-Car M1A)
10+ - "renesas,intc-irqpin-r8a7779" (R-Car H1)
11+ - "renesas,intc-irqpin-sh73a0" (SH-Mobile AG5)
612 - #interrupt-cells: has to be <2>: an interrupt index and flags, as defined in
713 interrupts.txt in this directory
814
Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt+32−0
@@ -0,0 +1,32 @@
1+DT bindings for the R-Mobile/R-Car interrupt controller
2+
3+Required properties:
4+
5+- compatible: has to be "renesas,irqc-<soctype>", "renesas,irqc" as fallback.
6+ Examples with soctypes are:
7+ - "renesas,irqc-r8a73a4" (R-Mobile AP6)
8+ - "renesas,irqc-r8a7790" (R-Car H2)
9+ - "renesas,irqc-r8a7791" (R-Car M2-W)
10+ - "renesas,irqc-r8a7792" (R-Car V2H)
11+ - "renesas,irqc-r8a7793" (R-Car M2-N)
12+ - "renesas,irqc-r8a7794" (R-Car E2)
13+- #interrupt-cells: has to be <2>: an interrupt index and flags, as defined in
14+ interrupts.txt in this directory
15+
16+Optional properties:
17+
18+- any properties, listed in interrupts.txt, and any standard resource allocation
19+ properties
20+
21+Example:
22+
23+ irqc0: interrupt-controller@e61c0000 {
24+ compatible = "renesas,irqc-r8a7790", "renesas,irqc";
25+ #interrupt-cells = <2>;
26+ interrupt-controller;
27+ reg = <0 0xe61c0000 0 0x200>;
28+ interrupts = <0 0 IRQ_TYPE_LEVEL_HIGH>,
29+ <0 1 IRQ_TYPE_LEVEL_HIGH>,
30+ <0 2 IRQ_TYPE_LEVEL_HIGH>,
31+ <0 3 IRQ_TYPE_LEVEL_HIGH>;
32+ };
Documentation/devicetree/bindings/interrupt-controller/ti,keystone-irq.txt+36−0
@@ -0,0 +1,36 @@
1+Keystone 2 IRQ controller IP
2+
3+On Keystone SOCs, DSP cores can send interrupts to ARM
4+host using the IRQ controller IP. It provides 28 IRQ signals to ARM.
5+The IRQ handler running on HOST OS can identify DSP signal source by
6+analyzing SRCCx bits in IPCARx registers. This is one of the component
7+used by the IPC mechanism used on Keystone SOCs.
8+
9+Required Properties:
10+- compatible: should be "ti,keystone-irq"
11+- ti,syscon-dev : phandle and offset pair. The phandle to syscon used to
12+ access device control registers and the offset inside
13+ device control registers range.
14+- interrupt-controller : Identifies the node as an interrupt controller
15+- #interrupt-cells : Specifies the number of cells needed to encode interrupt
16+ source should be 1.
17+- interrupts: interrupt reference to primary interrupt controller
18+
19+Please refer to interrupts.txt in this directory for details of the common
20+Interrupt Controllers bindings used by client devices.
21+
22+Example:
23+ kirq0: keystone_irq0@026202a0 {
24+ compatible = "ti,keystone-irq";
25+ ti,syscon-dev = <&devctrl 0x2a0>;
26+ interrupts = <GIC_SPI 4 IRQ_TYPE_EDGE_RISING>;
27+ interrupt-controller;
28+ #interrupt-cells = <1>;
29+ };
30+
31+ dsp0: dsp0 {
32+ compatible = "linux,rproc-user";
33+ ...
34+ interrupt-parent = <&kirq0>;
35+ interrupts = <10 2>;
36+ };
Documentation/devicetree/bindings/iommu/arm,smmu.txt+1−0
@@ -14,6 +14,7 @@ conditions. · 13 unmodified lines
1414 "arm,smmu-v1"
1515 "arm,smmu-v2"
1616 "arm,mmu-400"
17+ "arm,mmu-401"
1718 "arm,mmu-500"
1819
1920 depending on the particular implementation and/or the
Documentation/devicetree/bindings/iommu/rockchip,iommu.txt+26−0
@@ -0,0 +1,26 @@
1+Rockchip IOMMU
2+==============
3+
4+A Rockchip DRM iommu translates io virtual addresses to physical addresses for
5+its master device. Each slave device is bound to a single master device, and
6+shares its clocks, power domain and irq.
7+
8+Required properties:
9+- compatible : Should be "rockchip,iommu"
10+- reg : Address space for the configuration registers
11+- interrupts : Interrupt specifier for the IOMMU instance
12+- interrupt-names : Interrupt name for the IOMMU instance
13+- #iommu-cells : Should be <0>. This indicates the iommu is a
14+ "single-master" device, and needs no additional information
15+ to associate with its master device. See:
16+ Documentation/devicetree/bindings/iommu/iommu.txt
17+
18+Example:
19+
20+ vopl_mmu: iommu@ff940300 {
21+ compatible = "rockchip,iommu";
22+ reg = <0xff940300 0x100>;
23+ interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
24+ interrupt-names = "vopl_mmu";
25+ #iommu-cells = <0>;
26+ };
Documentation/devicetree/bindings/leds/leds-lp8860.txt+29−0
@@ -0,0 +1,29 @@
1+* Texas Instruments - lp8860 4-Channel LED Driver
2+
3+The LP8860-Q1 is an high-efficiency LED
4+driver with boost controller. It has 4 high-precision
5+current sinks that can be controlled by a PWM input
6+signal, a SPI/I2C master, or both.
7+
8+Required properties:
9+ - compatible:
10+ "ti,lp8860"
11+ - reg - I2C slave address
12+ - label - Used for naming LEDs
13+
14+Optional properties:
15+ - enable-gpio - gpio pin to enable/disable the device.
16+ - supply - "vled" - LED supply
17+
18+Example:
19+
20+leds: leds@6 {
21+ compatible = "ti,lp8860";
22+ reg = <0x2d>;
23+ label = "display_cluster";
24+ enable-gpio = <&gpio1 28 GPIO_ACTIVE_HIGH>;
25+ vled-supply = <&vbatt>;
26+}
27+
28+For more product information please see the link below:
29+http://www.ti.com/product/lp8860-q1
Documentation/devicetree/bindings/leds/register-bit-led.txt+99−0
@@ -0,0 +1,99 @@
1+Device Tree Bindings for Register Bit LEDs
2+
3+Register bit leds are used with syscon multifunctional devices
4+where single bits in a certain register can turn on/off a
5+single LED. The register bit LEDs appear as children to the
6+syscon device, with the proper compatible string. For the
7+syscon bindings see:
8+Documentation/devicetree/bindings/mfd/syscon.txt
9+
10+Each LED is represented as a sub-node of the syscon device. Each
11+node's name represents the name of the corresponding LED.
12+
13+LED sub-node properties:
14+
15+Required properties:
16+- compatible : must be "register-bit-led"
17+- offset : register offset to the register controlling this LED
18+- mask : bit mask for the bit controlling this LED in the register
19+ typically 0x01, 0x02, 0x04 ...
20+
21+Optional properties:
22+- label : (optional)
23+ see Documentation/devicetree/bindings/leds/common.txt
24+- linux,default-trigger : (optional)
25+ see Documentation/devicetree/bindings/leds/common.txt
26+- default-state: (optional) The initial state of the LED. Valid
27+ values are "on", "off", and "keep". If the LED is already on or off
28+ and the default-state property is set the to same value, then no
29+ glitch should be produced where the LED momentarily turns off (or
30+ on). The "keep" setting will keep the LED at whatever its current
31+ state is, without producing a glitch. The default is off if this
32+ property is not present.
33+
34+Example:
35+
36+syscon: syscon@10000000 {
37+ compatible = "arm,realview-pb1176-syscon", "syscon";
38+ reg = <0x10000000 0x1000>;
39+
40+ led@08.0 {
41+ compatible = "register-bit-led";
42+ offset = <0x08>;
43+ mask = <0x01>;
44+ label = "versatile:0";
45+ linux,default-trigger = "heartbeat";
46+ default-state = "on";
47+ };
48+ led@08.1 {
49+ compatible = "register-bit-led";
50+ offset = <0x08>;
51+ mask = <0x02>;
52+ label = "versatile:1";
53+ linux,default-trigger = "mmc0";
54+ default-state = "off";
55+ };
56+ led@08.2 {
57+ compatible = "register-bit-led";
58+ offset = <0x08>;
59+ mask = <0x04>;
60+ label = "versatile:2";
61+ linux,default-trigger = "cpu0";
62+ default-state = "off";
63+ };
64+ led@08.3 {
65+ compatible = "register-bit-led";
66+ offset = <0x08>;
67+ mask = <0x08>;
68+ label = "versatile:3";
69+ default-state = "off";
70+ };
71+ led@08.4 {
72+ compatible = "register-bit-led";
73+ offset = <0x08>;
74+ mask = <0x10>;
75+ label = "versatile:4";
76+ default-state = "off";
77+ };
78+ led@08.5 {
79+ compatible = "register-bit-led";
80+ offset = <0x08>;
81+ mask = <0x20>;
82+ label = "versatile:5";
83+ default-state = "off";
84+ };
85+ led@08.6 {
86+ compatible = "register-bit-led";
87+ offset = <0x08>;
88+ mask = <0x40>;
89+ label = "versatile:6";
90+ default-state = "off";
91+ };
92+ led@08.7 {
93+ compatible = "register-bit-led";
94+ offset = <0x08>;
95+ mask = <0x80>;
96+ label = "versatile:7";
97+ default-state = "off";
98+ };
99+};
Documentation/devicetree/bindings/mailbox/mailbox.txt+38−0
@@ -0,0 +1,38 @@
1+* Generic Mailbox Controller and client driver bindings
2+
3+Generic binding to provide a way for Mailbox controller drivers to
4+assign appropriate mailbox channel to client drivers.
5+
6+* Mailbox Controller
7+
8+Required property:
9+- #mbox-cells: Must be at least 1. Number of cells in a mailbox
10+ specifier.
11+
12+Example:
13+ mailbox: mailbox {
14+ ...
15+ #mbox-cells = <1>;
16+ };
17+
18+
19+* Mailbox Client
20+
21+Required property:
22+- mboxes: List of phandle and mailbox channel specifiers.
23+
24+Optional property:
25+- mbox-names: List of identifier strings for each mailbox channel
26+ required by the client. The use of this property
27+ is discouraged in favor of using index in list of
28+ 'mboxes' while requesting a mailbox. Instead the
29+ platforms may define channel indices, in DT headers,
30+ to something legible.
31+
32+Example:
33+ pwr_cntrl: power {
34+ ...
35+ mbox-names = "pwr-ctrl", "rpc";
36+ mboxes = <&mailbox 0
37+ &mailbox 1>;
38+ };
Documentation/devicetree/bindings/mailbox/omap-mailbox.txt+131−0
@@ -0,0 +1,131 @@
1+OMAP2+ Mailbox Driver
2+=====================
3+
4+The OMAP mailbox hardware facilitates communication between different processors
5+using a queued mailbox interrupt mechanism. The IP block is external to the
6+various processor subsystems and is connected on an interconnect bus. The
7+communication is achieved through a set of registers for message storage and
8+interrupt configuration registers.
9+
10+Each mailbox IP block has a certain number of h/w fifo queues and output
11+interrupt lines. An output interrupt line is routed to an interrupt controller
12+within a processor subsystem, and there can be more than one line going to a
13+specific processor's interrupt controller. The interrupt line connections are
14+fixed for an instance and are dictated by the IP integration into the SoC
15+(excluding the SoCs that have a Interrupt Crossbar IP). Each interrupt line is
16+programmable through a set of interrupt configuration registers, and have a rx
17+and tx interrupt source per h/w fifo. Communication between different processors
18+is achieved through the appropriate programming of the rx and tx interrupt
19+sources on the appropriate interrupt lines.
20+
21+The number of h/w fifo queues and interrupt lines dictate the usable registers.
22+All the current OMAP SoCs except for the newest DRA7xx SoC has a single IP
23+instance. DRA7xx has multiple instances with different number of h/w fifo queues
24+and interrupt lines between different instances. The interrupt lines can also be
25+routed to different processor sub-systems on DRA7xx as they are routed through
26+the Crossbar, a kind of interrupt router/multiplexer.
27+
28+Mailbox Device Node:
29+====================
30+A Mailbox device node is used to represent a Mailbox IP instance within a SoC.
31+The sub-mailboxes are represented as child nodes of this parent node.
32+
33+Required properties:
34+--------------------
35+- compatible: Should be one of the following,
36+ "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
37+ "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
38+ "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
39+ AM43xx and DRA7xx SoCs
40+- reg: Contains the mailbox register address range (base
41+ address and length)
42+- interrupts: Contains the interrupt information for the mailbox
43+ device. The format is dependent on which interrupt
44+ controller the OMAP device uses
45+- ti,hwmods: Name of the hwmod associated with the mailbox
46+- #mbox-cells: Common mailbox binding property to identify the number
47+ of cells required for the mailbox specifier. Should be
48+ 1
49+- ti,mbox-num-users: Number of targets (processor devices) that the mailbox
50+ device can interrupt
51+- ti,mbox-num-fifos: Number of h/w fifo queues within the mailbox IP block
52+
53+Child Nodes:
54+============
55+A child node is used for representing the actual sub-mailbox device that is
56+used for the communication between the host processor and a remote processor.
57+Each child node should have a unique node name across all the different
58+mailbox device nodes.
59+
60+Required properties:
61+--------------------
62+- ti,mbox-tx: sub-mailbox descriptor property defining a Tx fifo
63+- ti,mbox-rx: sub-mailbox descriptor property defining a Rx fifo
64+
65+Sub-mailbox Descriptor Data
66+---------------------------
67+Each of the above ti,mbox-tx and ti,mbox-rx properties should have 3 cells of
68+data that represent the following:
69+ Cell #1 (fifo_id) - mailbox fifo id used either for transmitting
70+ (ti,mbox-tx) or for receiving (ti,mbox-rx)
71+ Cell #2 (irq_id) - irq identifier index number to use from the parent's
72+ interrupts data. Should be 0 for most of the cases, a
73+ positive index value is seen only on mailboxes that have
74+ multiple interrupt lines connected to the MPU processor.
75+ Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
76+ associated with generating a tx/rx fifo interrupt.
77+
78+Mailbox Users:
79+==============
80+A device needing to communicate with a target processor device should specify
81+them using the common mailbox binding properties, "mboxes" and the optional
82+"mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
83+for details). Each value of the mboxes property should contain a phandle to the
84+mailbox controller device node and an args specifier that will be the phandle to
85+the intended sub-mailbox child node to be used for communication. The equivalent
86+"mbox-names" property value can be used to give a name to the communication channel
87+to be used by the client user.
88+
89+
90+Example:
91+--------
92+
93+/* OMAP4 */
94+mailbox: mailbox@4a0f4000 {
95+ compatible = "ti,omap4-mailbox";
96+ reg = <0x4a0f4000 0x200>;
97+ interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
98+ ti,hwmods = "mailbox";
99+ #mbox-cells = <1>;
100+ ti,mbox-num-users = <3>;
101+ ti,mbox-num-fifos = <8>;
102+ mbox_ipu: mbox_ipu {
103+ ti,mbox-tx = <0 0 0>;
104+ ti,mbox-rx = <1 0 0>;
105+ };
106+ mbox_dsp: mbox_dsp {
107+ ti,mbox-tx = <3 0 0>;
108+ ti,mbox-rx = <2 0 0>;
109+ };
110+};
111+
112+dsp {
113+ ...
114+ mboxes = <&mailbox &mbox_dsp>;
115+ ...
116+};
117+
118+/* AM33xx */
119+mailbox: mailbox@480C8000 {
120+ compatible = "ti,omap4-mailbox";
121+ reg = <0x480C8000 0x200>;
122+ interrupts = <77>;
123+ ti,hwmods = "mailbox";
124+ #mbox-cells = <1>;
125+ ti,mbox-num-users = <4>;
126+ ti,mbox-num-fifos = <8>;
127+ mbox_wkupm3: wkup_m3 {
128+ ti,mbox-tx = <0 0 0>;
129+ ti,mbox-rx = <0 0 3>;
130+ };
131+};
Documentation/devicetree/bindings/media/hix5hd2-ir.txt+25−0
@@ -0,0 +1,25 @@
1+Device-Tree bindings for hix5hd2 ir IP
2+
3+Required properties:
4+ - compatible: Should contain "hisilicon,hix5hd2-ir".
5+ - reg: Base physical address of the controller and length of memory
6+ mapped region.
7+ - interrupts: interrupt-specifier for the sole interrupt generated by
8+ the device. The interrupt specifier format depends on the interrupt
9+ controller parent.
10+ - clocks: clock phandle and specifier pair.
11+ - hisilicon,power-syscon: phandle of syscon used to control power.
12+
13+Optional properties:
14+ - linux,rc-map-name : Remote control map name.
15+
16+Example node:
17+
18+ ir: ir@f8001000 {
19+ compatible = "hisilicon,hix5hd2-ir";
20+ reg = <0xf8001000 0x1000>;
21+ interrupts = <0 47 4>;
22+ clocks = <&clock HIX5HD2_FIXED_24M>;
23+ hisilicon,power-syscon = <&sysctrl>;
24+ linux,rc-map-name = "rc-tivo";
25+ };
Documentation/devicetree/bindings/media/meson-ir.txt+14−0
@@ -0,0 +1,14 @@
1+* Amlogic Meson IR remote control receiver
2+
3+Required properties:
4+ - compatible : should be "amlogic,meson6-ir"
5+ - reg : physical base address and length of the device registers
6+ - interrupts : a single specifier for the interrupt from the device
7+
8+Example:
9+
10+ ir-receiver@c8100480 {
11+ compatible= "amlogic,meson6-ir";
12+ reg = <0xc8100480 0x20>;
13+ interrupts = <0 15 1>;
14+ };
Documentation/devicetree/bindings/media/rcar_vin.txt+2−0
@@ -6,6 +6,8 @@ family of devices. The current blocks are always slaves and suppot one input · 5 unmodified lines
66 channel which can be either RGB, YUYV or BT656.
77
88 - compatible: Must be one of the following
9+ - "renesas,vin-r8a7794" for the R8A7794 device
10+ - "renesas,vin-r8a7793" for the R8A7793 device
911 - "renesas,vin-r8a7791" for the R8A7791 device
1012 - "renesas,vin-r8a7790" for the R8A7790 device
1113 - "renesas,vin-r8a7779" for the R8A7779 device
Documentation/devicetree/bindings/media/si4713.txt+30−0
@@ -0,0 +1,30 @@
1+* Silicon Labs FM Radio transmitter
2+
3+The Silicon Labs Si4713 is an FM radio transmitter with receive power scan
4+supporting 76-108 MHz. It includes an RDS encoder and has both, a stereo-analog
5+and a digital interface, which supports I2S, left-justified and a custom
6+DSP-mode format. It is programmable through an I2C interface.
7+
8+Required Properties:
9+- compatible: Should contain "silabs,si4713"
10+- reg: the I2C address of the device
11+
12+Optional Properties:
13+- interrupts-extended: Interrupt specifier for the chips interrupt
14+- reset-gpios: GPIO specifier for the chips reset line
15+- vdd-supply: phandle for Vdd regulator
16+- vio-supply: phandle for Vio regulator
17+
18+Example:
19+
20+&i2c2 {
21+ fmtx: si4713@63 {
22+ compatible = "silabs,si4713";
23+ reg = <0x63>;
24+
25+ interrupts-extended = <&gpio2 21 IRQ_TYPE_EDGE_FALLING>; /* 53 */
26+ reset-gpios = <&gpio6 3 GPIO_ACTIVE_HIGH>; /* 163 */
27+ vio-supply = <&vio>;
28+ vdd-supply = <&vaux1>;
29+ };
30+};
Documentation/devicetree/bindings/memory-controllers/mvebu-sdram-controller.txt+21−0
@@ -0,0 +1,21 @@
1+Device Tree bindings for MVEBU SDRAM controllers
2+
3+The Marvell EBU SoCs all have a SDRAM controller. The SDRAM controller
4+differs from one SoC variant to another, but they also share a number
5+of commonalities.
6+
7+For now, this Device Tree binding documentation only documents the
8+Armada XP SDRAM controller.
9+
10+Required properties:
11+
12+ - compatible: for Armada XP, "marvell,armada-xp-sdram-controller"
13+ - reg: a resource specifier for the register space, which should
14+ include all SDRAM controller registers as per the datasheet.
15+
16+Example:
17+
18+sdramc@1400 {
19+ compatible = "marvell,armada-xp-sdram-controller";
20+ reg = <0x1400 0x500>;
21+};
Documentation/devicetree/bindings/memory-controllers/nvidia,tegra-mc.txt+36−0
@@ -0,0 +1,36 @@
1+NVIDIA Tegra Memory Controller device tree bindings
2+===================================================
3+
4+Required properties:
5+- compatible: Should be "nvidia,tegra<chip>-mc"
6+- reg: Physical base address and length of the controller's registers.
7+- clocks: Must contain an entry for each entry in clock-names.
8+ See ../clocks/clock-bindings.txt for details.
9+- clock-names: Must include the following entries:
10+ - mc: the module's clock input
11+- interrupts: The interrupt outputs from the controller.
12+- #iommu-cells: Should be 1. The single cell of the IOMMU specifier defines
13+ the SWGROUP of the master.
14+
15+This device implements an IOMMU that complies with the generic IOMMU binding.
16+See ../iommu/iommu.txt for details.
17+
18+Example:
19+--------
20+
21+ mc: memory-controller@0,70019000 {
22+ compatible = "nvidia,tegra124-mc";
23+ reg = <0x0 0x70019000 0x0 0x1000>;
24+ clocks = <&tegra_car TEGRA124_CLK_MC>;
25+ clock-names = "mc";
26+
27+ interrupts = <GIC_SPI 77 IRQ_TYPE_LEVEL_HIGH>;
28+
29+ #iommu-cells = <1>;
30+ };
31+
32+ sdhci@0,700b0000 {
33+ compatible = "nvidia,tegra124-sdhci";
34+ ...
35+ iommus = <&mc TEGRA_SWGROUP_SDMMC1A>;
36+ };
Documentation/devicetree/bindings/memory-controllers/synopsys.txt+11−0
@@ -0,0 +1,11 @@
1+Binding for Synopsys IntelliDDR Multi Protocol Memory Controller
2+
3+Required properties:
4+ - compatible: Should be 'xlnx,zynq-ddrc-a05'
5+ - reg: Base address and size of the controllers memory area
6+
7+Example:
8+ memory-controller@f8006000 {
9+ compatible = "xlnx,zynq-ddrc-a05";
10+ reg = <0xf8006000 0x1000>;
11+ };
Documentation/devicetree/bindings/mfd/arizona.txt+7−0
@@ -42,6 +42,13 @@ Optional properties: · 41 unmodified lines
4242 the chip default will be used. If present exactly five values must
4343 be specified.
4444
45+ - wlf,inmode : A list of INn_MODE register values, where n is the number
46+ of input signals. Valid values are 0 (Differential), 1 (Single-ended) and
47+ 2 (Digital Microphone). If absent, INn_MODE registers set to 0 by default.
48+ If present, values must be specified less than or equal to the number of
49+ input singals. If values less than the number of input signals, elements
50+ that has not been specifed are set to 0 by default.
51+
4552 - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if
4653 they are being externally supplied. As covered in
4754 Documentation/devicetree/bindings/regulator/regulator.txt
Documentation/devicetree/bindings/mfd/atmel-gpbr.txt+15−0
@@ -0,0 +1,15 @@
1+* Device tree bindings for Atmel GPBR (General Purpose Backup Registers)
2+
3+The GPBR are a set of battery-backed registers.
4+
5+Required properties:
6+- compatible: "atmel,at91sam9260-gpbr", "syscon"
7+- reg: contains offset/length value of the GPBR memory
8+ region.
9+
10+Example:
11+
12+gpbr: gpbr@fffffd50 {
13+ compatible = "atmel,at91sam9260-gpbr", "syscon";
14+ reg = <0xfffffd50 0x10>;
15+};
Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt+51−0
@@ -0,0 +1,51 @@
1+Device-Tree bindings for Atmel's HLCDC (High LCD Controller) MFD driver
2+
3+Required properties:
4+ - compatible: value should be one of the following:
5+ "atmel,sama5d3-hlcdc"
6+ - reg: base address and size of the HLCDC device registers.
7+ - clock-names: the name of the 3 clocks requested by the HLCDC device.
8+ Should contain "periph_clk", "sys_clk" and "slow_clk".
9+ - clocks: should contain the 3 clocks requested by the HLCDC device.
10+ - interrupts: should contain the description of the HLCDC interrupt line
11+
12+The HLCDC IP exposes two subdevices:
13+ - a PWM chip: see ../pwm/atmel-hlcdc-pwm.txt
14+ - a Display Controller: see ../drm/atmel-hlcdc-dc.txt
15+
16+Example:
17+
18+ hlcdc: hlcdc@f0030000 {
19+ compatible = "atmel,sama5d3-hlcdc";
20+ reg = <0xf0030000 0x2000>;
21+ clocks = <&lcdc_clk>, <&lcdck>, <&clk32k>;
22+ clock-names = "periph_clk","sys_clk", "slow_clk";
23+ interrupts = <36 IRQ_TYPE_LEVEL_HIGH 0>;
24+ status = "disabled";
25+
26+ hlcdc-display-controller {
27+ compatible = "atmel,hlcdc-display-controller";
28+ pinctrl-names = "default";
29+ pinctrl-0 = <&pinctrl_lcd_base &pinctrl_lcd_rgb888>;
30+ #address-cells = <1>;
31+ #size-cells = <0>;
32+
33+ port@0 {
34+ #address-cells = <1>;
35+ #size-cells = <0>;
36+ reg = <0>;
37+
38+ hlcdc_panel_output: endpoint@0 {
39+ reg = <0>;
40+ remote-endpoint = <&panel_input>;
41+ };
42+ };
43+ };
44+
45+ hlcdc_pwm: hlcdc-pwm {
46+ compatible = "atmel,hlcdc-pwm";
47+ pinctrl-names = "default";
48+ pinctrl-0 = <&pinctrl_lcd_pwm>;
49+ #pwm-cells = <3>;
50+ };
51+ };
Documentation/devicetree/bindings/mfd/hi6421.txt+38−0
@@ -0,0 +1,38 @@
1+* HI6421 Multi-Functional Device (MFD), by HiSilicon Ltd.
2+
3+Required parent device properties:
4+- compatible : contains "hisilicon,hi6421-pmic";
5+- reg : register range space of hi6421;
6+
7+Supported Hi6421 sub-devices include:
8+
9+Device IRQ Names Supply Names Description
10+------ --------- ------------ -----------
11+regulators : None : None : Regulators
12+
13+Required child device properties:
14+None.
15+
16+Example:
17+ hi6421 {
18+ compatible = "hisilicon,hi6421-pmic";
19+ reg = <0xfcc00000 0x0180>; /* 0x60 << 2 */
20+
21+ regulators {
22+ // supply for MLC NAND/ eMMC
23+ hi6421_vout0_reg: hi6421_vout0 {
24+ regulator-name = "VOUT0";
25+ regulator-min-microvolt = <2850000>;
26+ regulator-max-microvolt = <2850000>;
27+ };
28+
29+ // supply for 26M Oscillator
30+ hi6421_vout1_reg: hi6421_vout1 {
31+ regulator-name = "VOUT1";
32+ regulator-min-microvolt = <1700000>;
33+ regulator-max-microvolt = <2000000>;
34+ regulator-boot-on;
35+ regulator-always-on;
36+ };
37+ };
38+ };
Documentation/devicetree/bindings/mfd/max14577.txt+146−0
@@ -0,0 +1,146 @@
1+Maxim MAX14577/77836 Multi-Function Device
2+
3+MAX14577 is a Multi-Function Device with Micro-USB Interface Circuit, Li+
4+Battery Charger and SFOUT LDO output for powering USB devices. It is
5+interfaced to host controller using I2C.
6+
7+MAX77836 additionally contains PMIC (with two LDO regulators) and Fuel Gauge.
8+
9+
10+Required properties:
11+- compatible : Must be "maxim,max14577" or "maxim,max77836".
12+- reg : I2C slave address for the max14577 chip (0x25 for max14577/max77836)
13+- interrupts : IRQ line for the chip.
14+- interrupt-parent : The parent interrupt controller.
15+
16+
17+Required nodes:
18+ - charger :
19+ Node for configuring the charger driver.
20+ Required properties:
21+ - compatible : "maxim,max14577-charger"
22+ or "maxim,max77836-charger"
23+ - maxim,fast-charge-uamp : Current in uA for Fast Charge;
24+ Valid values:
25+ - for max14577: 90000 - 950000;
26+ - for max77836: 45000 - 475000;
27+ - maxim,eoc-uamp : Current in uA for End-Of-Charge mode;
28+ Valid values:
29+ - for max14577: 50000 - 200000;
30+ - for max77836: 5000 - 100000;
31+ - maxim,ovp-uvolt : OverVoltage Protection Threshold in uV;
32+ In an overvoltage condition, INT asserts and charging
33+ stops. Valid values:
34+ - 6000000, 6500000, 7000000, 7500000;
35+ - maxim,constant-uvolt : Battery Constant Voltage in uV;
36+ Valid values:
37+ - 4000000 - 4280000 (step by 20000);
38+ - 4350000;
39+
40+
41+Optional nodes:
42+- max14577-muic/max77836-muic :
43+ Node used only by extcon consumers.
44+ Required properties:
45+ - compatible : "maxim,max14577-muic" or "maxim,max77836-muic"
46+
47+- regulators :
48+ Required properties:
49+ - compatible : "maxim,max14577-regulator"
50+ or "maxim,max77836-regulator"
51+
52+ May contain a sub-node per regulator from the list below. Each
53+ sub-node should contain the constraints and initialization information
54+ for that regulator. See regulator.txt for a description of standard
55+ properties for these sub-nodes.
56+
57+ List of valid regulator names:
58+ - for max14577: CHARGER, SAFEOUT.
59+ - for max77836: CHARGER, SAFEOUT, LDO1, LDO2.
60+
61+ The SAFEOUT is a fixed voltage regulator so there is no need to specify
62+ voltages for it.
63+
64+
65+Example:
66+
67+#include <dt-bindings/interrupt-controller/irq.h>
68+
69+max14577@25 {
70+ compatible = "maxim,max14577";
71+ reg = <0x25>;
72+ interrupt-parent = <&gpx1>;
73+ interrupts = <5 IRQ_TYPE_NONE>;
74+
75+ muic: max14577-muic {
76+ compatible = "maxim,max14577-muic";
77+ };
78+
79+ regulators {
80+ compatible = "maxim,max14577-regulator";
81+
82+ SAFEOUT {
83+ regulator-name = "SAFEOUT";
84+ };
85+ CHARGER {
86+ regulator-name = "CHARGER";
87+ regulator-min-microamp = <90000>;
88+ regulator-max-microamp = <950000>;
89+ regulator-boot-on;
90+ };
91+ };
92+
93+ charger {
94+ compatible = "maxim,max14577-charger";
95+
96+ maxim,constant-uvolt = <4350000>;
97+ maxim,fast-charge-uamp = <450000>;
98+ maxim,eoc-uamp = <50000>;
99+ maxim,ovp-uvolt = <6500000>;
100+ };
101+};
102+
103+
104+max77836@25 {
105+ compatible = "maxim,max77836";
106+ reg = <0x25>;
107+ interrupt-parent = <&gpx1>;
108+ interrupts = <5 IRQ_TYPE_NONE>;
109+
110+ muic: max77836-muic {
111+ compatible = "maxim,max77836-muic";
112+ };
113+
114+ regulators {
115+ compatible = "maxim,max77836-regulator";
116+
117+ SAFEOUT {
118+ regulator-name = "SAFEOUT";
119+ };
120+ CHARGER {
121+ regulator-name = "CHARGER";
122+ regulator-min-microamp = <90000>;
123+ regulator-max-microamp = <950000>;
124+ regulator-boot-on;
125+ };
126+ LDO1 {
127+ regulator-name = "LDO1";
128+ regulator-min-microvolt = <2700000>;
129+ regulator-max-microvolt = <2700000>;
130+ };
131+ LDO2 {
132+ regulator-name = "LDO2";
133+ regulator-min-microvolt = <800000>;
134+ regulator-max-microvolt = <3950000>;
135+ };
136+ };
137+
138+ charger {
139+ compatible = "maxim,max77836-charger";
140+
141+ maxim,constant-uvolt = <4350000>;
142+ maxim,fast-charge-uamp = <225000>;
143+ maxim,eoc-uamp = <7500>;
144+ maxim,ovp-uvolt = <6500000>;
145+ };
146+};
Documentation/devicetree/bindings/mfd/max77686.txt+6−0
@@ -34,6 +34,12 @@ to get matched with their hardware counterparts as follow: · 33 unmodified lines
3434 -BUCKn : for BUCKs, where n can lie in range 1 to 9.
3535 example: BUCK1, BUCK5, BUCK9.
3636
37+ Regulators which can be turned off during system suspend:
38+ -LDOn : 2, 6-8, 10-12, 14-16,
39+ -BUCKn : 1-4.
40+ Use standard regulator bindings for it ('regulator-off-in-suspend').
41+
42+
3743 Example:
3844
3945 max77686@09 {
Documentation/devicetree/bindings/mfd/max77693.txt+21−0
@@ -27,6 +27,20 @@ Optional properties: · 26 unmodified lines
2727
2828 [*] refer Documentation/devicetree/bindings/regulator/regulator.txt
2929
30+- haptic : The MAX77693 haptic device utilises a PWM controlled motor to provide
31+ users with tactile feedback. PWM period and duty-cycle are varied in
32+ order to provide the approprite level of feedback.
33+
34+ Required properties:
35+ - compatible : Must be "maxim,max77693-hpatic"
36+ - haptic-supply : power supply for the haptic motor
37+ [*] refer Documentation/devicetree/bindings/regulator/regulator.txt
38+ - pwms : phandle to the physical PWM(Pulse Width Modulation) device.
39+ PWM properties should be named "pwms". And number of cell is different
40+ for each pwm device.
41+ To get more informations, please refer to documentaion.
42+ [*] refer Documentation/devicetree/bindings/pwm/pwm.txt
43+
3044 Example:
3145 max77693@66 {
3246 compatible = "maxim,max77693";
@@ -52,4 +66,11 @@ Example: · 19 unmodified lines
5266 regulator-boot-on;
5367 };
5468 };
69+
70+ haptic {
71+ compatible = "maxim,max77693-haptic";
72+ haptic-supply = <&haptic_supply>;
73+ pwms = <&pwm 0 40000 0>;
74+ pwm-names = "haptic";
75+ };
5576 };
Documentation/devicetree/bindings/mfd/qcom,pm8xxx.txt+0−96
@@ -1,96 +0,0 @@
1−Qualcomm PM8xxx PMIC multi-function devices
2−
3−The PM8xxx family of Power Management ICs are used to provide regulated
4−voltages and other various functionality to Qualcomm SoCs.
5−
6−= PROPERTIES
7−
8−- compatible:
9− Usage: required
10− Value type: <string>
11− Definition: must be one of:
12− "qcom,pm8058"
13− "qcom,pm8921"
14−
15−- #address-cells:
16− Usage: required
17− Value type: <u32>
18− Definition: must be 1
19−
20−- #size-cells:
21− Usage: required
22− Value type: <u32>
23− Definition: must be 0
24−
25−- interrupts:
26− Usage: required
27− Value type: <prop-encoded-array>
28− Definition: specifies the interrupt that indicates a subdevice
29− has generated an interrupt (summary interrupt). The
30− format of the specifier is defined by the binding document
31− describing the node's interrupt parent.
32−
33−- #interrupt-cells:
34− Usage: required
35− Value type : <u32>
36− Definition: must be 2. Specifies the number of cells needed to encode
37− an interrupt source. The 1st cell contains the interrupt
38− number. The 2nd cell is the trigger type and level flags
39− encoded as follows:
40−
41− 1 = low-to-high edge triggered
42− 2 = high-to-low edge triggered
43− 4 = active high level-sensitive
44− 8 = active low level-sensitive
45−
46−- interrupt-controller:
47− Usage: required
48− Value type: <empty>
49− Definition: identifies this node as an interrupt controller
50−
51−= SUBCOMPONENTS
52−
53−The PMIC contains multiple independent functions, each described in a subnode.
54−The below bindings specify the set of valid subnodes.
55−
56−== Real-Time Clock
57−
58−- compatible:
59− Usage: required
60− Value type: <string>
61− Definition: must be one of:
62− "qcom,pm8058-rtc"
63− "qcom,pm8921-rtc"
64−
65−- reg:
66− Usage: required
67− Value type: <prop-encoded-array>
68− Definition: single entry specifying the base address of the RTC registers
69−
70−- interrupts:
71− Usage: required
72− Value type: <prop-encoded-array>
73− Definition: single entry specifying the RTC's alarm interrupt
74−
75−- allow-set-time:
76− Usage: optional
77− Value type: <empty>
78− Definition: indicates that the setting of RTC time is allowed by
79− the host CPU
80−
81−= EXAMPLE
82−
83− pmicintc: pmic@0 {
84− compatible = "qcom,pm8921";
85− interrupts = <104 8>;
86− #interrupt-cells = <2>;
87− interrupt-controller;
88− #address-cells = <1>;
89− #size-cells = <0>;
90−
91− rtc@11d {
92− compatible = "qcom,pm8921-rtc";
93− reg = <0x11d>;
94− interrupts = <0x27 0>;
95− };
96− };
Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt+64−0
@@ -0,0 +1,64 @@
1+ Qualcomm SPMI PMICs multi-function device bindings
2+
3+The Qualcomm SPMI series presently includes PM8941, PM8841 and PMA8084
4+PMICs. These PMICs use a QPNP scheme through SPMI interface.
5+QPNP is effectively a partitioning scheme for dividing the SPMI extended
6+register space up into logical pieces, and set of fixed register
7+locations/definitions within these regions, with some of these regions
8+specifically used for interrupt handling.
9+
10+The QPNP PMICs are used with the Qualcomm Snapdragon series SoCs, and are
11+interfaced to the chip via the SPMI (System Power Management Interface) bus.
12+Support for multiple independent functions are implemented by splitting the
13+16-bit SPMI slave address space into 256 smaller fixed-size regions, 256 bytes
14+each. A function can consume one or more of these fixed-size register regions.
15+
16+Required properties:
17+- compatible: Should contain one of:
18+ "qcom,pm8941"
19+ "qcom,pm8841"
20+ "qcom,pma8084"
21+ or generalized "qcom,spmi-pmic".
22+- reg: Specifies the SPMI USID slave address for this device.
23+ For more information see:
24+ Documentation/devicetree/bindings/spmi/spmi.txt
25+
26+Required properties for peripheral child nodes:
27+- compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name.
28+
29+Optional properties for peripheral child nodes:
30+- interrupts: Interrupts are specified as a 4-tuple. For more information
31+ see:
32+ Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt
33+- interrupt-names: Corresponding interrupt name to the interrupts property
34+
35+Each child node of SPMI slave id represents a function of the PMIC. In the
36+example below the rtc device node represents a peripheral of pm8941
37+SID = 0. The regulator device node represents a peripheral of pm8941 SID = 1.
38+
39+Example:
40+
41+ spmi {
42+ compatible = "qcom,spmi-pmic-arb";
43+
44+ pm8941@0 {
45+ compatible = "qcom,pm8941", "qcom,spmi-pmic";
46+ reg = <0x0 SPMI_USID>;
47+
48+ rtc {
49+ compatible = "qcom,rtc";
50+ interrupts = <0x0 0x61 0x1 IRQ_TYPE_EDGE_RISING>;
51+ interrupt-names = "alarm";
52+ };
53+ };
54+
55+ pm8941@1 {
56+ compatible = "qcom,pm8941", "qcom,spmi-pmic";
57+ reg = <0x1 SPMI_USID>;
58+
59+ regulator {
60+ compatible = "qcom,regulator";
61+ regulator-name = "8941_boost";
62+ };
63+ };
64+ };
Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt+97−0
@@ -0,0 +1,97 @@
1+Qualcomm PM8xxx PMIC multi-function devices
2+
3+The PM8xxx family of Power Management ICs are used to provide regulated
4+voltages and other various functionality to Qualcomm SoCs.
5+
6+= PROPERTIES
7+
8+- compatible:
9+ Usage: required
10+ Value type: <string>
11+ Definition: must be one of:
12+ "qcom,pm8058"
13+ "qcom,pm8921"
14+
15+- #address-cells:
16+ Usage: required
17+ Value type: <u32>
18+ Definition: must be 1
19+
20+- #size-cells:
21+ Usage: required
22+ Value type: <u32>
23+ Definition: must be 0
24+
25+- interrupts:
26+ Usage: required
27+ Value type: <prop-encoded-array>
28+ Definition: specifies the interrupt that indicates a subdevice
29+ has generated an interrupt (summary interrupt). The
30+ format of the specifier is defined by the binding document
31+ describing the node's interrupt parent.
32+
33+- #interrupt-cells:
34+ Usage: required
35+ Value type : <u32>
36+ Definition: must be 2. Specifies the number of cells needed to encode
37+ an interrupt source. The 1st cell contains the interrupt
38+ number. The 2nd cell is the trigger type and level flags
39+ encoded as follows:
40+
41+ 1 = low-to-high edge triggered
42+ 2 = high-to-low edge triggered
43+ 4 = active high level-sensitive
44+ 8 = active low level-sensitive
45+
46+- interrupt-controller:
47+ Usage: required
48+ Value type: <empty>
49+ Definition: identifies this node as an interrupt controller
50+
51+= SUBCOMPONENTS
52+
53+The PMIC contains multiple independent functions, each described in a subnode.
54+The below bindings specify the set of valid subnodes.
55+
56+== Real-Time Clock
57+
58+- compatible:
59+ Usage: required
60+ Value type: <string>
61+ Definition: must be one of:
62+ "qcom,pm8058-rtc"
63+ "qcom,pm8921-rtc"
64+ "qcom,pm8941-rtc"
65+
66+- reg:
67+ Usage: required
68+ Value type: <prop-encoded-array>
69+ Definition: single entry specifying the base address of the RTC registers
70+
71+- interrupts:
72+ Usage: required
73+ Value type: <prop-encoded-array>
74+ Definition: single entry specifying the RTC's alarm interrupt
75+
76+- allow-set-time:
77+ Usage: optional
78+ Value type: <empty>
79+ Definition: indicates that the setting of RTC time is allowed by
80+ the host CPU
81+
82+= EXAMPLE
83+
84+ pmicintc: pmic@0 {
85+ compatible = "qcom,pm8921";
86+ interrupts = <104 8>;
87+ #interrupt-cells = <2>;
88+ interrupt-controller;
89+ #address-cells = <1>;
90+ #size-cells = <0>;
91+
92+ rtc@11d {
93+ compatible = "qcom,pm8921-rtc";
94+ reg = <0x11d>;
95+ interrupts = <0x27 0>;
96+ };
97+ };
Documentation/devicetree/bindings/mfd/rk808.txt+177−0
@@ -0,0 +1,177 @@
1+RK808 Power Management Integrated Circuit
2+
3+Required properties:
4+- compatible: "rockchip,rk808"
5+- reg: I2C slave address
6+- interrupt-parent: The parent interrupt controller.
7+- interrupts: the interrupt outputs of the controller.
8+- #clock-cells: from common clock binding; shall be set to 1 (multiple clock
9+ outputs). See <dt-bindings/clock/rockchip,rk808.h> for clock IDs.
10+
11+Optional properties:
12+- clock-output-names: From common clock binding to override the
13+ default output clock name
14+- rockchip,system-power-controller: Telling whether or not this pmic is controlling
15+ the system power.
16+- vcc1-supply: The input supply for DCDC_REG1
17+- vcc2-supply: The input supply for DCDC_REG2
18+- vcc3-supply: The input supply for DCDC_REG3
19+- vcc4-supply: The input supply for DCDC_REG4
20+- vcc6-supply: The input supply for LDO_REG1 and LDO_REG2
21+- vcc7-supply: The input supply for LDO_REG3 and LDO_REG7
22+- vcc8-supply: The input supply for SWITCH_REG1
23+- vcc9-supply: The input supply for LDO_REG4 and LDO_REG5
24+- vcc10-supply: The input supply for LDO_REG6
25+- vcc11-supply: The input supply for LDO_REG8
26+- vcc12-supply: The input supply for SWITCH_REG2
27+
28+Regulators: All the regulators of RK808 to be instantiated shall be
29+listed in a child node named 'regulators'. Each regulator is represented
30+by a child node of the 'regulators' node.
31+
32+ regulator-name {
33+ /* standard regulator bindings here */
34+ };
35+
36+Following regulators of the RK808 PMIC block are supported. Note that
37+the 'n' in regulator name, as in DCDC_REGn or LDOn, represents the DCDC or LDO
38+number as described in RK808 datasheet.
39+
40+ - DCDC_REGn
41+ - valid values for n are 1 to 4.
42+ - LDO_REGn
43+ - valid values for n are 1 to 8.
44+ - SWITCH_REGn
45+ - valid values for n are 1 to 2
46+
47+Standard regulator bindings are used inside regulator subnodes. Check
48+ Documentation/devicetree/bindings/regulator/regulator.txt
49+for more details
50+
51+Example:
52+ rk808: pmic@1b {
53+ compatible = "rockchip,rk808";
54+ clock-output-names = "xin32k", "rk808-clkout2";
55+ interrupt-parent = <&gpio0>;
56+ interrupts = <4 IRQ_TYPE_LEVEL_LOW>;
57+ pinctrl-names = "default";
58+ pinctrl-0 = <&pmic_int>;
59+ reg = <0x1b>;
60+ rockchip,system-power-controller;
61+ wakeup-source;
62+ #clock-cells = <1>;
63+
64+ vcc8-supply = <&vcc_18>;
65+ vcc9-supply = <&vcc_io>;
66+ vcc10-supply = <&vcc_io>;
67+ vcc12-supply = <&vcc_io>;
68+ vddio-supply = <&vccio_pmu>;
69+
70+ regulators {
71+ vdd_cpu: DCDC_REG1 {
72+ regulator-always-on;
73+ regulator-boot-on;
74+ regulator-min-microvolt = <750000>;
75+ regulator-max-microvolt = <1300000>;
76+ regulator-name = "vdd_arm";
77+ };
78+
79+ vdd_gpu: DCDC_REG2 {
80+ regulator-always-on;
81+ regulator-boot-on;
82+ regulator-min-microvolt = <850000>;
83+ regulator-max-microvolt = <1250000>;
84+ regulator-name = "vdd_gpu";
85+ };
86+
87+ vcc_ddr: DCDC_REG3 {
88+ regulator-always-on;
89+ regulator-boot-on;
90+ regulator-name = "vcc_ddr";
91+ };
92+
93+ vcc_io: DCDC_REG4 {
94+ regulator-always-on;
95+ regulator-boot-on;
96+ regulator-min-microvolt = <3300000>;
97+ regulator-max-microvolt = <3300000>;
98+ regulator-name = "vcc_io";
99+ };
100+
101+ vccio_pmu: LDO_REG1 {
102+ regulator-always-on;
103+ regulator-boot-on;
104+ regulator-min-microvolt = <3300000>;
105+ regulator-max-microvolt = <3300000>;
106+ regulator-name = "vccio_pmu";
107+ };
108+
109+ vcc_tp: LDO_REG2 {
110+ regulator-always-on;
111+ regulator-boot-on;
112+ regulator-min-microvolt = <3300000>;
113+ regulator-max-microvolt = <3300000>;
114+ regulator-name = "vcc_tp";
115+ };
116+
117+ vdd_10: LDO_REG3 {
118+ regulator-always-on;
119+ regulator-boot-on;
120+ regulator-min-microvolt = <1000000>;
121+ regulator-max-microvolt = <1000000>;
122+ regulator-name = "vdd_10";
123+ };
124+
125+ vcc18_lcd: LDO_REG4 {
126+ regulator-always-on;
127+ regulator-boot-on;
128+ regulator-min-microvolt = <1800000>;
129+ regulator-max-microvolt = <1800000>;
130+ regulator-name = "vcc18_lcd";
131+ };
132+
133+ vccio_sd: LDO_REG5 {
134+ regulator-always-on;
135+ regulator-boot-on;
136+ regulator-min-microvolt = <1800000>;
137+ regulator-max-microvolt = <3300000>;
138+ regulator-name = "vccio_sd";
139+ };
140+
141+ vdd10_lcd: LDO_REG6 {
142+ regulator-always-on;
143+ regulator-boot-on;
144+ regulator-min-microvolt = <1000000>;
145+ regulator-max-microvolt = <1000000>;
146+ regulator-name = "vdd10_lcd";
147+ };
148+
149+ vcc_18: LDO_REG7 {
150+ regulator-always-on;
151+ regulator-boot-on;
152+ regulator-min-microvolt = <1800000>;
153+ regulator-max-microvolt = <1800000>;
154+ regulator-name = "vcc_18";
155+ };
156+
157+ vcca_codec: LDO_REG8 {
158+ regulator-always-on;
159+ regulator-boot-on;
160+ regulator-min-microvolt = <3300000>;
161+ regulator-max-microvolt = <3300000>;
162+ regulator-name = "vcca_codec";
163+ };
164+
165+ vcc_wl: SWITCH_REG1 {
166+ regulator-always-on;
167+ regulator-boot-on;
168+ regulator-name = "vcc_wl";
169+ };
170+
171+ vcc_lcd: SWITCH_REG2 {
172+ regulator-always-on;
173+ regulator-boot-on;
174+ regulator-name = "vcc_lcd";
175+ };
176+ };
177+ };
Documentation/devicetree/bindings/mfd/rn5t618.txt+36−0
@@ -0,0 +1,36 @@
1+* Ricoh RN5T618 PMIC
2+
3+Ricoh RN5T618 is a power management IC which integrates 3 step-down
4+DCDC converters, 7 low-dropout regulators, a Li-ion battery charger,
5+fuel gauge, ADC, GPIOs and a watchdog timer. It can be controlled
6+through a I2C interface.
7+
8+Required properties:
9+ - compatible: should be "ricoh,rn5t618"
10+ - reg: the I2C slave address of the device
11+
12+Sub-nodes:
13+ - regulators: the node is required if the regulator functionality is
14+ needed. The valid regulator names are: DCDC1, DCDC2, DCDC3, LDO1,
15+ LDO2, LDO3, LDO4, LDO5, LDORTC1 and LDORTC2.
16+ The common bindings for each individual regulator can be found in:
17+ Documentation/devicetree/bindings/regulator/regulator.txt
18+
19+Example:
20+
21+ pmic@32 {
22+ compatible = "ricoh,rn5t618";
23+ reg = <0x32>;
24+
25+ regulators {
26+ DCDC1 {
27+ regulator-min-microvolt = <1050000>;
28+ regulator-max-microvolt = <1050000>;
29+ };
30+
31+ DCDC2 {
32+ regulator-min-microvolt = <1175000>;
33+ regulator-max-microvolt = <1175000>;
34+ };
35+ };
36+ };
Documentation/devicetree/bindings/mfd/s2mps11.txt+13−11
@@ -1,5 +1,5 @@
11
2−* Samsung S2MPS11, S2MPS14 and S2MPU02 Voltage and Current Regulator
2+* Samsung S2MPS11, S2MPS13, S2MPS14 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,8 +7,8 @@ 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,s2mps14-pmic"
11− or "samsung,s2mpu02-pmic".
10+- compatible: Should be "samsung,s2mps11-pmic" or "samsung,s2mps13-pmic"
11+ or "samsung,s2mps14-pmic" or "samsung,s2mpu02-pmic".
1212 - reg: Specifies the I2C slave address of the pmic block. It should be 0x66.
1313
1414 Optional properties:
@@ -17,8 +17,8 @@ Optional properties: · 2 unmodified lines
1717 - interrupts: Interrupt specifiers for interrupt sources.
1818
1919 Optional nodes:
20−- clocks: s2mps11 and s5m8767 provide three(AP/CP/BT) buffered 32.768 KHz
21− outputs, so to register these as clocks with common clock framework
20+- clocks: s2mps11, s2mps13 and s5m8767 provide three(AP/CP/BT) buffered 32.768
21+ KHz outputs, so to register these as clocks with common clock framework
2222 instantiate a sub-node named "clocks". It uses the common clock binding
2323 documented in :
2424 [Documentation/devicetree/bindings/clock/clock-bindings.txt]
@@ -30,12 +30,12 @@ Optional nodes: · 5 unmodified lines
3030 the clock which they consume.
3131 Clock ID Devices
3232 ----------------------------------------------------------
33− 32KhzAP 0 S2MPS11, S2MPS14, S5M8767
34− 32KhzCP 1 S2MPS11, S5M8767
35− 32KhzBT 2 S2MPS11, S2MPS14, S5M8767
33+ 32KhzAP 0 S2MPS11, S2MPS13, S2MPS14, S5M8767
34+ 32KhzCP 1 S2MPS11, S2MPS13, S5M8767
35+ 32KhzBT 2 S2MPS11, S2MPS13, S2MPS14, S5M8767
3636
37− - compatible: Should be one of: "samsung,s2mps11-clk", "samsung,s2mps14-clk",
38− "samsung,s5m8767-clk"
37+ - compatible: Should be one of: "samsung,s2mps11-clk", "samsung,s2mps13-clk",
38+ "samsung,s2mps14-clk", "samsung,s5m8767-clk"
3939
4040 - regulators: The regulators of s2mps11 that have to be instantiated should be
4141 included in a sub-node named 'regulators'. Regulator nodes included in this
@@ -47,7 +47,7 @@ sub-node should be of the format as listed below. · 5 unmodified lines
4747
4848 regulator-ramp-delay for BUCKs = [6250/12500/25000(default)/50000] uV/us
4949
50− BUCK[2/3/4/6] supports disabling ramp delay on hardware, so explictly
50+ BUCK[2/3/4/6] supports disabling ramp delay on hardware, so explicitly
5151 regulator-ramp-delay = <0> can be used for them to disable ramp delay.
5252 In the absence of the regulator-ramp-delay property, the default ramp
5353 delay will be used.
@@ -81,12 +81,14 @@ as per the datasheet of s2mps11. · 27 unmodified lines
8181 - LDOn
8282 - valid values for n are:
8383 - S2MPS11: 1 to 38
84+ - S2MPS13: 1 to 40
8485 - S2MPS14: 1 to 25
8586 - S2MPU02: 1 to 28
8687 - Example: LDO1, LDO2, LDO28
8788 - BUCKn
8889 - valid values for n are:
8990 - S2MPS11: 1 to 10
91+ - S2MPS13: 1 to 10
9092 - S2MPS14: 1 to 5
9193 - S2MPU02: 1 to 7
9294 - Example: BUCK1, BUCK2, BUCK9
Documentation/devicetree/bindings/mfd/stmpe.txt+1−0
@@ -13,6 +13,7 @@ Optional properties: · 12 unmodified lines
1313 - interrupt-parent : Specifies which IRQ controller we're connected to
1414 - wakeup-source : Marks the input device as wakable
1515 - st,autosleep-timeout : Valid entries (ms); 4, 16, 32, 64, 128, 256, 512 and 1024
16+ - irq-gpio : If present, which GPIO to use for event IRQ
1617
1718 Example:
1819
Documentation/devicetree/bindings/mfd/twl4030-power.txt+7−2
@@ -23,8 +23,13 @@ down during off-idle. Note that this does not work on all boards · 22 unmodified lines
2323 depending on how the external oscillator is wired.
2424
2525 Optional properties:
26−- ti,use_poweroff: With this flag, the chip will initiates an ACTIVE-to-OFF or
27− SLEEP-to-OFF transition when the system poweroffs.
26+
27+- ti,system-power-controller: This indicates that TWL4030 is the
28+ power supply master of the system. With this flag, the chip will
29+ initiate an ACTIVE-to-OFF or SLEEP-to-OFF transition when the
30+ system poweroffs.
31+
32+- ti,use_poweroff: Deprecated name for ti,system-power-controller
2833
2934 Example:
3035 &i2c1 {
Documentation/devicetree/bindings/mips/brcm/bcm3384-intc.txt+37−0
@@ -0,0 +1,37 @@
1+* Interrupt Controller
2+
3+Properties:
4+- compatible: "brcm,bcm3384-intc"
5+
6+ Compatibility with BCM3384 and possibly other BCM33xx/BCM63xx SoCs.
7+
8+- reg: Address/length pairs for each mask/status register set. Length must
9+ be 8. If multiple register sets are specified, the first set will
10+ handle IRQ offsets 0..31, the second set 32..63, and so on.
11+
12+- interrupt-controller: This is an interrupt controller.
13+
14+- #interrupt-cells: Must be <1>. Just a simple IRQ offset; no level/edge
15+ or polarity configuration is possible with this controller.
16+
17+- interrupt-parent: This controller is cascaded from a MIPS CPU HW IRQ, or
18+ from another INTC.
19+
20+- interrupts: The IRQ on the parent controller.
21+
22+Example:
23+ periph_intc: periph_intc@14e00038 {
24+ compatible = "brcm,bcm3384-intc";
25+
26+ /*
27+ * IRQs 0..31: mask reg 0x14e00038, status reg 0x14e0003c
28+ * IRQs 32..63: mask reg 0x14e00340, status reg 0x14e00344
29+ */
30+ reg = <0x14e00038 0x8 0x14e00340 0x8>;
31+
32+ interrupt-controller;
33+ #interrupt-cells = <1>;
34+
35+ interrupt-parent = <&cpu_intc>;
36+ interrupts = <4>;
37+ };
Documentation/devicetree/bindings/mips/brcm/bmips.txt+8−0
@@ -0,0 +1,8 @@
1+* Broadcom MIPS (BMIPS) CPUs
2+
3+Required properties:
4+- compatible: "brcm,bmips3300", "brcm,bmips4350", "brcm,bmips4380",
5+ "brcm,bmips5000"
6+
7+- mips-hpt-frequency: This is common to all CPUs in the system so it lives
8+ under the "cpus" node.
Documentation/devicetree/bindings/mips/brcm/cm-dsl.txt+11−0
@@ -0,0 +1,11 @@
1+* Broadcom cable/DSL platforms
2+
3+SoCs:
4+
5+Required properties:
6+- compatible: "brcm,bcm3384", "brcm,bcm33843"
7+
8+Boards:
9+
10+Required properties:
11+- compatible: "brcm,bcm93384wvg"
Documentation/devicetree/bindings/mips/brcm/usb.txt+11−0
@@ -0,0 +1,11 @@
1+* Broadcom USB controllers
2+
3+Required properties:
4+- compatible: "brcm,bcm3384-ohci", "brcm,bcm3384-ehci"
5+
6+ These currently use the generic-ohci and generic-ehci drivers. On some
7+ systems, special handling may be needed in the following cases:
8+
9+ - Restoring state after systemwide power save modes
10+ - Sharing PHYs with the USBD (UDC) hardware
11+ - Figuring out which controllers are disabled on ASIC bondout variants
Documentation/devicetree/bindings/mips/cpu_irq.txt+2−2
@@ -1,6 +1,6 @@
11 MIPS CPU interrupt controller
22
3−On MIPS the mips_cpu_intc_init() helper can be used to initialize the 8 CPU
3+On MIPS the mips_cpu_irq_of_init() helper can be used to initialize the 8 CPU
44 IRQs from a devicetree file and create a irq_domain for IRQ controller.
55
66 With the irq_domain in place we can describe how the 8 IRQs are wired to the
@@ -36,7 +36,7 @@ Example devicetree: · 29 unmodified lines
3636
3737 Example platform irq.c:
3838 static struct of_device_id __initdata of_irq_ids[] = {
39− { .compatible = "mti,cpu-interrupt-controller", .data = mips_cpu_intc_init },
39+ { .compatible = "mti,cpu-interrupt-controller", .data = mips_cpu_irq_of_init },
4040 { .compatible = "ralink,rt2880-intc", .data = intc_of_init },
4141 {},
4242 };
Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt+4−0
@@ -18,6 +18,10 @@ Required Properties: · 17 unmodified lines
1818 specific extensions.
1919 - "samsung,exynos5420-dw-mshc": for controllers with Samsung Exynos5420
2020 specific extensions.
21+ - "samsung,exynos7-dw-mshc": for controllers with Samsung Exynos7
22+ specific extensions.
23+ - "samsung,exynos7-dw-mshc-smu": for controllers with Samsung Exynos7
24+ specific extensions having an SMU.
2125
2226 * samsung,dw-mshc-ciu-div: Specifies the divider value for the card interface
2327 unit (ciu) clock. This property is applicable only for Exynos5 SoC's and
Documentation/devicetree/bindings/mmc/img-dw-mshc.txt+29−0
@@ -0,0 +1,29 @@
1+* Imagination specific extensions to the Synopsys Designware Mobile Storage
2+ Host Controller
3+
4+The Synopsys designware mobile storage host controller is used to interface
5+a SoC with storage medium such as eMMC or SD/MMC cards. This file documents
6+differences between the core Synopsys dw mshc controller properties described
7+by synopsys-dw-mshc.txt and the properties used by the Imagination specific
8+extensions to the Synopsys Designware Mobile Storage Host Controller.
9+
10+Required Properties:
11+
12+* compatible: should be
13+ - "img,pistachio-dw-mshc": for Pistachio SoCs
14+
15+Example:
16+
17+ mmc@18142000 {
18+ compatible = "img,pistachio-dw-mshc";
19+ reg = <0x18142000 0x400>;
20+ interrupts = <GIC_SHARED 39 IRQ_TYPE_LEVEL_HIGH>;
21+
22+ clocks = <&system_clk>, <&sdhost_clk>;
23+ clock-names = "biu", "ciu";
24+
25+ fifo-depth = <0x20>;
26+ bus-width = <4>;
27+ num-slots = <1>;
28+ disable-wp;
29+ };
Documentation/devicetree/bindings/mmc/mmc.txt+2−0
@@ -40,6 +40,8 @@ Optional properties: · 39 unmodified lines
4040 - mmc-hs200-1_2v: eMMC HS200 mode(1.2V I/O) is supported
4141 - mmc-hs400-1_8v: eMMC HS400 mode(1.8V I/O) is supported
4242 - mmc-hs400-1_2v: eMMC HS400 mode(1.2V I/O) is supported
43+- dsr: Value the card's (optional) Driver Stage Register (DSR) should be
44+ programmed with. Valid range: [0 .. 0xffff].
4345
4446 *NOTE* on CD and WP polarity. To use common for all SD/MMC host controllers line
4547 polarity properties, we have to fix the meaning of the "normal" and "inverted"
Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt+4−2
@@ -10,12 +10,14 @@ extensions to the Synopsys Designware Mobile Storage Host Controller. · 9 unmodified lines
1010 Required Properties:
1111
1212 * compatible: should be
13− - "rockchip,rk2928-dw-mshc": for Rockchip RK2928 and following
13+ - "rockchip,rk2928-dw-mshc": for Rockchip RK2928 and following,
14+ before RK3288
15+ - "rockchip,rk3288-dw-mshc": for Rockchip RK3288
1416
1517 Example:
1618
1719 rkdwmmc0@12200000 {
18− compatible = "rockchip,rk2928-dw-mshc";
20+ compatible = "rockchip,rk3288-dw-mshc";
1921 reg = <0x12200000 0x1000>;
2022 interrupts = <0 75 0>;
2123 #address-cells = <1>;
Documentation/devicetree/bindings/mmc/sdhci-pxa.txt+7−0
@@ -12,6 +12,10 @@ Required properties: · 11 unmodified lines
1212 * for "marvell,armada-380-sdhci", two register areas. The first one
1313 for the SDHCI registers themselves, and the second one for the
1414 AXI/Mbus bridge registers of the SDHCI unit.
15+- clocks: Array of clocks required for SDHCI; requires at least one for
16+ I/O clock.
17+- clock-names: Array of names corresponding to clocks property; shall be
18+ "io" for I/O clock and "core" for optional core clock.
1519
1620 Optional properties:
1721 - mrvl,clk-delay-cycles: Specify a number of cycles to delay for tuning.
@@ -23,6 +27,8 @@ sdhci@d4280800 { · 5 unmodified lines
2327 reg = <0xd4280800 0x800>;
2428 bus-width = <8>;
2529 interrupts = <27>;
30+ clocks = <&chip CLKID_SDIO1XIN>, <&chip CLKID_SDIO1>;
31+ clock-names = "io", "core";
2632 non-removable;
2733 mrvl,clk-delay-cycles = <31>;
2834 };
@@ -32,5 +38,6 @@ sdhci@d8000 { · 3 unmodified lines
3238 reg = <0xd8000 0x1000>, <0xdc000 0x100>;
3339 interrupts = <0 25 0x4>;
3440 clocks = <&gateclk 17>;
41+ clock-names = "io";
3542 mrvl,clk-delay-cycles = <0x1F>;
3643 };
Documentation/devicetree/bindings/mmc/tmio_mmc.txt+3−0
@@ -19,6 +19,9 @@ Required properties: · 18 unmodified lines
1919 "renesas,sdhi-r8a7779" - SDHI IP on R8A7779 SoC
2020 "renesas,sdhi-r8a7790" - SDHI IP on R8A7790 SoC
2121 "renesas,sdhi-r8a7791" - SDHI IP on R8A7791 SoC
22+ "renesas,sdhi-r8a7792" - SDHI IP on R8A7792 SoC
23+ "renesas,sdhi-r8a7793" - SDHI IP on R8A7793 SoC
24+ "renesas,sdhi-r8a7794" - SDHI IP on R8A7794 SoC
2225
2326 Optional properties:
2427 - toshiba,mmc-wrprotect-disable: write-protect detection is unavailable
Documentation/devicetree/bindings/mtd/atmel-nand.txt+6−2
@@ -5,7 +5,9 @@ Required properties: · 4 unmodified lines
55 - reg : should specify localbus address and size used for the chip,
66 and hardware ECC controller if available.
77 If the hardware ECC is PMECC, it should contain address and size for
8− PMECC, PMECC Error Location controller and ROM which has lookup tables.
8+ PMECC and PMECC Error Location controller.
9+ The PMECC lookup table address and size in ROM is optional. If not
10+ specified, driver will build it in runtime.
911 - atmel,nand-addr-offset : offset for the address latch.
1012 - atmel,nand-cmd-offset : offset for the command latch.
1113 - #address-cells, #size-cells : Must be present if the device has sub-nodes
@@ -27,7 +29,7 @@ Optional properties: · 15 unmodified lines
2729 are: 512, 1024.
2830 - atmel,pmecc-lookup-table-offset : includes two offsets of lookup table in ROM
2931 for different sector size. First one is for sector size 512, the next is for
30− sector size 1024.
32+ sector size 1024. If not specified, driver will build the table in runtime.
3133 - nand-bus-width : 8 or 16 bus width if not present 8
3234 - nand-on-flash-bbt: boolean to enable on flash bbt option if not present false
3335 - Nand Flash Controller(NFC) is a slave driver under Atmel nand flash
@@ -36,6 +38,7 @@ Optional properties: · 2 unmodified lines
3638 - reg : should specify the address and size used for NFC command registers,
3739 NFC registers and NFC Sram. NFC Sram address and size can be absent
3840 if don't want to use it.
41+ - clocks: phandle to the peripheral clock
3942 - Optional properties:
4043 - atmel,write-by-sram: boolean to enable NFC write by sram.
4144
@@ -98,6 +101,7 @@ nand0: nand@40000000 { · 56 unmodified lines
98101 compatible = "atmel,sama5d3-nfc";
99102 #address-cells = <1>;
100103 #size-cells = <1>;
104+ clocks = <&hsmc_clk>
101105 reg = <
102106 0x70000000 0x10000000 /* NFC Command Registers */
103107 0xffffc000 0x00000070 /* NFC HSMC regs */
Documentation/devicetree/bindings/mtd/diskonchip.txt+15−0
@@ -0,0 +1,15 @@
1+M-Systems and Sandisk DiskOnChip devices
2+
3+M-System DiskOnChip G3
4+======================
5+The Sandisk (formerly M-Systems) docg3 is a nand device of 64M to 256MB.
6+
7+Required properties:
8+ - compatible: should be "m-systems,diskonchip-g3"
9+ - reg: register base and size
10+
11+Example:
12+ docg3: flash@0 {
13+ compatible = "m-systems,diskonchip-g3";
14+ reg = <0x0 0x2000>;
15+ };
Documentation/devicetree/bindings/mtd/gpio-control-nand.txt+7−7
@@ -11,8 +11,8 @@ Required properties: · 10 unmodified lines
1111 are made in native endianness.
1212 - #address-cells, #size-cells : Must be present if the device has sub-nodes
1313 representing partitions.
14−- gpios : specifies the gpio pins to control the NAND device. nwp is an
15− optional gpio and may be set to 0 if not present.
14+- gpios : Specifies the GPIO pins to control the NAND device. The order of
15+ GPIO references is: RDY, nCE, ALE, CLE, and an optional nWP.
1616
1717 Optional properties:
1818 - bank-width : Width (in bytes) of the device. If not present, the width
@@ -35,11 +35,11 @@ gpio-nand@1,0 { · 16 unmodified lines
3535 reg = <1 0x0000 0x2>;
3636 #address-cells = <1>;
3737 #size-cells = <1>;
38− gpios = <&banka 1 0 /* rdy */
39− &banka 2 0 /* nce */
40− &banka 3 0 /* ale */
41− &banka 4 0 /* cle */
42− 0 /* nwp */>;
38+ gpios = <&banka 1 0>, /* RDY */
39+ <&banka 2 0>, /* nCE */
40+ <&banka 3 0>, /* ALE */
41+ <&banka 4 0>, /* CLE */
42+ <0>; /* nWP */
4343
4444 partition@0 {
4545 ...
Documentation/devicetree/bindings/mtd/gpmc-nand.txt+3−3
@@ -110,8 +110,8 @@ on various other factors also like; · 109 unmodified lines
110110 Other factor which governs the selection of ecc-scheme is oob-size.
111111 Higher ECC schemes require more OOB/Spare area to store ECC syndrome,
112112 so the device should have enough free bytes available its OOB/Spare
113− area to accomodate ECC for entire page. In general following expression
114− helps in determining if given device can accomodate ECC syndrome:
113+ area to accommodate ECC for entire page. In general following expression
114+ helps in determining if given device can accommodate ECC syndrome:
115115 "2 + (PAGESIZE / 512) * ECC_BYTES" >= OOBSIZE"
116116 where
117117 OOBSIZE number of bytes in OOB/spare area
@@ -133,5 +133,5 @@ on various other factors also like; · 15 unmodified lines
133133 Example(b): For a device with PAGESIZE = 2048 and OOBSIZE = 128 and
134134 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
135135 Number of ECC bytes per page = (2 + (2048 / 512) * 26) = 106 B
136− which can be accomodate in the OOB/Spare area of this device
136+ which can be accommodated in the OOB/Spare area of this device
137137 (OOBSIZE=128). So this device can use BCH16 ecc-scheme.
Documentation/devicetree/bindings/mtd/mtd-physmap.txt+2−2
@@ -4,8 +4,8 @@ Flash chips (Memory Technology Devices) are often used for solid state · 3 unmodified lines
44 file systems on embedded devices.
55
66 - compatible : should contain the specific model of mtd chip(s)
7− used, if known, followed by either "cfi-flash", "jedec-flash"
8− or "mtd-ram".
7+ used, if known, followed by either "cfi-flash", "jedec-flash",
8+ "mtd-ram" or "mtd-rom".
99 - reg : Address range(s) of the mtd chip(s)
1010 It's possible to (optionally) define multiple "reg" tuples so that
1111 non-identical chips can be described in one node.
Documentation/devicetree/bindings/mtd/sunxi-nand.txt+45−0
@@ -0,0 +1,45 @@
1+Allwinner NAND Flash Controller (NFC)
2+
3+Required properties:
4+- compatible : "allwinner,sun4i-a10-nand".
5+- reg : shall contain registers location and length for data and reg.
6+- interrupts : shall define the nand controller interrupt.
7+- #address-cells: shall be set to 1. Encode the nand CS.
8+- #size-cells : shall be set to 0.
9+- clocks : shall reference nand controller clocks.
10+- clock-names : nand controller internal clock names. Shall contain :
11+ * "ahb" : AHB gating clock
12+ * "mod" : nand controller clock
13+
14+Optional children nodes:
15+Children nodes represent the available nand chips.
16+
17+Optional properties:
18+- allwinner,rb : shall contain the native Ready/Busy ids.
19+ or
20+- rb-gpios : shall contain the gpios used as R/B pins.
21+- nand-ecc-mode : one of the supported ECC modes ("hw", "hw_syndrome", "soft",
22+ "soft_bch" or "none")
23+
24+see Documentation/devicetree/mtd/nand.txt for generic bindings.
25+
26+
27+Examples:
28+nfc: nand@01c03000 {
29+ compatible = "allwinner,sun4i-a10-nand";
30+ reg = <0x01c03000 0x1000>;
31+ interrupts = <0 37 1>;
32+ clocks = <&ahb_gates 13>, <&nand_clk>;
33+ clock-names = "ahb", "mod";
34+ #address-cells = <1>;
35+ #size-cells = <0>;
36+ pinctrl-names = "default";
37+ pinctrl-0 = <&nand_pins_a &nand_cs0_pins_a &nand_rb0_pins_a>;
38+ status = "okay";
39+
40+ nand@0 {
41+ reg = <0>;
42+ allwinner,rb = <0>;
43+ nand-ecc-mode = "soft_bch";
44+ };
45+};
Documentation/devicetree/bindings/net/amd-xgbe.txt+10−2
@@ -7,7 +7,10 @@ Required properties: · 6 unmodified lines
77 - PCS registers
88 - interrupt-parent: Should be the phandle for the interrupt controller
99 that services interrupts for this device
10−- interrupts: Should contain the amd-xgbe interrupt
10+- interrupts: Should contain the amd-xgbe interrupt(s). The first interrupt
11+ listed is required and is the general device interrupt. If the optional
12+ amd,per-channel-interrupt property is specified, then one additional
13+ interrupt for each DMA channel supported by the device should be specified
1114 - clocks:
1215 - DMA clock for the amd-xgbe device (used for calculating the
1316 correct Rx interrupt watchdog timer value on a DMA channel
@@ -23,6 +26,9 @@ Optional properties: · 9 unmodified lines
2326 - mac-address: mac address to be assigned to the device. Can be overridden
2427 by UEFI.
2528 - dma-coherent: Present if dma operations are coherent
29+- amd,per-channel-interrupt: Indicates that Rx and Tx complete will generate
30+ a unique interrupt for each DMA channel - this requires an additional
31+ interrupt be configured for each DMA channel
2632
2733 Example:
2834 xgbe@e0700000 {
@@ -30,7 +36,9 @@ Example: · 1 unmodified line
3036 reg = <0 0xe0700000 0 0x80000>,
3137 <0 0xe0780000 0 0x80000>;
3238 interrupt-parent = <&gic>;
33− interrupts = <0 325 4>;
39+ interrupts = <0 325 4>,
40+ <0 326 1>, <0 327 1>, <0 328 1>, <0 329 1>;
41+ amd,per-channel-interrupt;
3442 clocks = <&xgbe_dma_clk>, <&xgbe_ptp_clk>;
3543 clock-names = "dma_clk", "ptp_clk";
3644 phy-handle = <&phy>;
Documentation/devicetree/bindings/net/apm-xgene-enet.txt+3−1
@@ -3,7 +3,7 @@ APM X-Gene SoC Ethernet nodes · 2 unmodified lines
33 Ethernet nodes are defined to describe on-chip ethernet interfaces in
44 APM X-Gene SoC.
55
6−Required properties:
6+Required properties for all the ethernet interfaces:
77 - compatible: Should be "apm,xgene-enet"
88 - reg: Address and length of the register set for the device. It contains the
99 information of registers in the same order as described by reg-names
@@ -15,6 +15,8 @@ Required properties: · 5 unmodified lines
1515 - clocks: Reference to the clock entry.
1616 - local-mac-address: MAC address assigned to this device
1717 - phy-connection-type: Interface type between ethernet device and PHY device
18+
19+Required properties for ethernet interfaces that have external PHY:
1820 - phy-handle: Reference to a PHY node connected to this device
1921
2022 - mdio: Device tree subnode with the following required properties:
Documentation/devicetree/bindings/net/broadcom-mdio-unimac.txt+39−0
@@ -0,0 +1,39 @@
1+* Broadcom UniMAC MDIO bus controller
2+
3+Required properties:
4+- compatible: should one from "brcm,genet-mdio-v1", "brcm,genet-mdio-v2",
5+ "brcm,genet-mdio-v3", "brcm,genet-mdio-v4" or "brcm,unimac-mdio"
6+- reg: address and length of the regsiter set for the device, first one is the
7+ base register, and the second one is optional and for indirect accesses to
8+ larger than 16-bits MDIO transactions
9+- reg-names: name(s) of the register must be "mdio" and optional "mdio_indir_rw"
10+- #size-cells: must be 1
11+- #address-cells: must be 0
12+
13+Optional properties:
14+- interrupts: must be one if the interrupt is shared with the Ethernet MAC or
15+ Ethernet switch this MDIO block is integrated from, or must be two, if there
16+ are two separate interrupts, first one must be "mdio done" and second must be
17+ for "mdio error"
18+- interrupt-names: must be "mdio_done_error" when there is a share interrupt fed
19+ to this hardware block, or must be "mdio_done" for the first interrupt and
20+ "mdio_error" for the second when there are separate interrupts
21+
22+Child nodes of this MDIO bus controller node are standard Ethernet PHY device
23+nodes as described in Documentation/devicetree/bindings/net/phy.txt
24+
25+Example:
26+
27+mdio@403c0 {
28+ compatible = "brcm,unimac-mdio";
29+ reg = <0x403c0 0x8 0x40300 0x18>;
30+ reg-names = "mdio", "mdio_indir_rw";
31+ #size-cells = <1>;
32+ #address-cells = <0>;
33+
34+ ...
35+ phy@0 {
36+ compatible = "ethernet-phy-ieee802.3-c22";
37+ reg = <0>;
38+ };
39+};
Documentation/devicetree/bindings/net/broadcom-sf2.txt+78−0
@@ -0,0 +1,78 @@
1+* Broadcom Starfighter 2 integrated swich
2+
3+Required properties:
4+
5+- compatible: should be "brcm,bcm7445-switch-v4.0"
6+- reg: addresses and length of the register sets for the device, must be 6
7+ pairs of register addresses and lengths
8+- interrupts: interrupts for the devices, must be two interrupts
9+- dsa,mii-bus: phandle to the MDIO bus controller, see dsa/dsa.txt
10+- dsa,ethernet: phandle to the CPU network interface controller, see dsa/dsa.txt
11+- #size-cells: must be 0
12+- #address-cells: must be 2, see dsa/dsa.txt
13+
14+Subnodes:
15+
16+The integrated switch subnode should be specified according to the binding
17+described in dsa/dsa.txt.
18+
19+Optional properties:
20+
21+- reg-names: litteral names for the device base register addresses, when present
22+ must be: "core", "reg", "intrl2_0", "intrl2_1", "fcb", "acb"
23+
24+- interrupt-names: litternal names for the device interrupt lines, when present
25+ must be: "switch_0" and "switch_1"
26+
27+- brcm,num-gphy: specify the maximum number of integrated gigabit PHYs in the
28+ switch
29+
30+- brcm,num-rgmii-ports: specify the maximum number of RGMII interfaces supported
31+ by the switch
32+
33+- brcm,fcb-pause-override: boolean property, if present indicates that the switch
34+ supports Failover Control Block pause override capability
35+
36+- brcm,acb-packets-inflight: boolean property, if present indicates that the switch
37+ Admission Control Block supports reporting the number of packets in-flight in a
38+ switch queue
39+
40+Example:
41+
42+switch_top@f0b00000 {
43+ compatible = "simple-bus";
44+ #size-cells = <1>;
45+ #address-cells = <1>;
46+ ranges = <0 0xf0b00000 0x40804>;
47+
48+ ethernet_switch@0 {
49+ compatible = "brcm,bcm7445-switch-v4.0";
50+ #size-cells = <0>;
51+ #address-cells = <2>;
52+ reg = <0x0 0x40000
53+ 0x40000 0x110
54+ 0x40340 0x30
55+ 0x40380 0x30
56+ 0x40400 0x34
57+ 0x40600 0x208>;
58+ interrupts = <0 0x18 0
59+ 0 0x19 0>;
60+ brcm,num-gphy = <1>;
61+ brcm,num-rgmii-ports = <2>;
62+ brcm,fcb-pause-override;
63+ brcm,acb-packets-inflight;
64+
65+ ...
66+ switch@0 {
67+ reg = <0 0>;
68+ #size-cells = <0>;
69+ #address-cells <1>;
70+
71+ port@0 {
72+ label = "gphy";
73+ reg = <0>;
74+ };
75+ ...
76+ };
77+ };
78+};
Documentation/devicetree/bindings/net/can/c_can.txt+5−0
@@ -4,6 +4,8 @@ Bosch C_CAN/D_CAN controller Device Tree Bindings · 3 unmodified lines
44 Required properties:
55 - compatible : Should be "bosch,c_can" for C_CAN controllers and
66 "bosch,d_can" for D_CAN controllers.
7+ Can be "ti,dra7-d_can", "ti,am3352-d_can" or
8+ "ti,am4372-d_can".
79 - reg : physical base address and size of the C_CAN/D_CAN
810 registers map
911 - interrupts : property with a value describing the interrupt
@@ -12,6 +14,9 @@ Required properties: · 2 unmodified lines
1214 Optional properties:
1315 - ti,hwmods : Must be "d_can<n>" or "c_can<n>", n being the
1416 instance number
17+- syscon-raminit : Handle to system control region that contains the
18+ RAMINIT register, register offset to the RAMINIT
19+ register and the CAN instance number (0 offset).
1520
1621 Note: "ti,hwmods" field is used to fetch the base address and irq
1722 resources from TI, omap hwmod data base during device registration.
Documentation/devicetree/bindings/net/can/m_can.txt+67−0
@@ -0,0 +1,67 @@
1+Bosch MCAN controller Device Tree Bindings
2+-------------------------------------------------
3+
4+Required properties:
5+- compatible : Should be "bosch,m_can" for M_CAN controllers
6+- reg : physical base address and size of the M_CAN
7+ registers map and Message RAM
8+- reg-names : Should be "m_can" and "message_ram"
9+- interrupts : Should be the interrupt number of M_CAN interrupt
10+ line 0 and line 1, could be same if sharing
11+ the same interrupt.
12+- interrupt-names : Should contain "int0" and "int1"
13+- clocks : Clocks used by controller, should be host clock
14+ and CAN clock.
15+- clock-names : Should contain "hclk" and "cclk"
16+- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt
17+- pinctrl-names : Names corresponding to the numbered pinctrl states
18+- bosch,mram-cfg : Message RAM configuration data.
19+ Multiple M_CAN instances can share the same Message
20+ RAM and each element(e.g Rx FIFO or Tx Buffer and etc)
21+ number in Message RAM is also configurable,
22+ so this property is telling driver how the shared or
23+ private Message RAM are used by this M_CAN controller.
24+
25+ The format should be as follows:
26+ <offset sidf_elems xidf_elems rxf0_elems rxf1_elems
27+ rxb_elems txe_elems txb_elems>
28+ The 'offset' is an address offset of the Message RAM
29+ where the following elements start from. This is
30+ usually set to 0x0 if you're using a private Message
31+ RAM. The remain cells are used to specify how many
32+ elements are used for each FIFO/Buffer.
33+
34+ M_CAN includes the following elements according to user manual:
35+ 11-bit Filter 0-128 elements / 0-128 words
36+ 29-bit Filter 0-64 elements / 0-128 words
37+ Rx FIFO 0 0-64 elements / 0-1152 words
38+ Rx FIFO 1 0-64 elements / 0-1152 words
39+ Rx Buffers 0-64 elements / 0-1152 words
40+ Tx Event FIFO 0-32 elements / 0-64 words
41+ Tx Buffers 0-32 elements / 0-576 words
42+
43+ Please refer to 2.4.1 Message RAM Configuration in
44+ Bosch M_CAN user manual for details.
45+
46+Example:
47+SoC dtsi:
48+m_can1: can@020e8000 {
49+ compatible = "bosch,m_can";
50+ reg = <0x020e8000 0x4000>, <0x02298000 0x4000>;
51+ reg-names = "m_can", "message_ram";
52+ interrupts = <0 114 0x04>,
53+ <0 114 0x04>;
54+ interrupt-names = "int0", "int1";
55+ clocks = <&clks IMX6SX_CLK_CANFD>,
56+ <&clks IMX6SX_CLK_CANFD>;
57+ clock-names = "hclk", "cclk";
58+ bosch,mram-cfg = <0x0 0 0 32 0 0 0 1>;
59+ status = "disabled";
60+};
61+
62+Board dts:
63+&m_can1 {
64+ pinctrl-names = "default";
65+ pinctrl-0 = <&pinctrl_m_can1>;
66+ status = "enabled";
67+};
Documentation/devicetree/bindings/net/can/rcar_can.txt+43−0
@@ -0,0 +1,43 @@
1+Renesas R-Car CAN controller Device Tree Bindings
2+-------------------------------------------------
3+
4+Required properties:
5+- compatible: "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
6+ "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
7+ "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
8+ "renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC.
9+- reg: physical base address and size of the R-Car CAN register map.
10+- interrupts: interrupt specifier for the sole interrupt.
11+- clocks: phandles and clock specifiers for 3 CAN clock inputs.
12+- clock-names: 3 clock input name strings: "clkp1", "clkp2", "can_clk".
13+- pinctrl-0: pin control group to be used for this controller.
14+- pinctrl-names: must be "default".
15+
16+Optional properties:
17+- renesas,can-clock-select: R-Car CAN Clock Source Select. Valid values are:
18+ <0x0> (default) : Peripheral clock (clkp1)
19+ <0x1> : Peripheral clock (clkp2)
20+ <0x3> : Externally input clock
21+
22+Example
23+-------
24+
25+SoC common .dtsi file:
26+
27+ can0: can@e6e80000 {
28+ compatible = "renesas,can-r8a7791";
29+ reg = <0 0xe6e80000 0 0x1000>;
30+ interrupts = <0 186 IRQ_TYPE_LEVEL_HIGH>;
31+ clocks = <&mstp9_clks R8A7791_CLK_RCAN0>,
32+ <&cpg_clocks R8A7791_CLK_RCAN>, <&can_clk>;
33+ clock-names = "clkp1", "clkp2", "can_clk";
34+ status = "disabled";
35+ };
36+
37+Board specific .dts file:
38+
39+&can0 {
40+ pinctrl-0 = <&can0_pins>;
41+ pinctrl-names = "default";
42+ status = "okay";
43+};
Documentation/devicetree/bindings/net/cpsw.txt+5−1
@@ -24,15 +24,17 @@ Optional properties: · 23 unmodified lines
2424 - ti,hwmods : Must be "cpgmac0"
2525 - no_bd_ram : Must be 0 or 1
2626 - dual_emac : Specifies Switch to act as Dual EMAC
27+- syscon : Phandle to the system control device node, which is
28+ the control module device of the am33x
2729
2830 Slave Properties:
2931 Required properties:
3032 - phy_id : Specifies slave phy id
3133 - phy-mode : See ethernet.txt file in the same directory
32−- mac-address : See ethernet.txt file in the same directory
3334
3435 Optional properties:
3536 - dual_emac_res_vlan : Specifies VID to be used to segregate the ports
37+- mac-address : See ethernet.txt file in the same directory
3638
3739 Note: "ti,hwmods" field is used to fetch the base address and irq
3840 resources from TI, omap hwmod data base during device registration.
@@ -57,6 +59,7 @@ Examples: · 18 unmodified lines
5759 active_slave = <0>;
5860 cpts_clock_mult = <0x80000000>;
5961 cpts_clock_shift = <29>;
62+ syscon = <&cm>;
6063 cpsw_emac0: slave@0 {
6164 phy_id = <&davinci_mdio>, <0>;
6265 phy-mode = "rgmii-txid";
@@ -85,6 +88,7 @@ Examples: · 22 unmodified lines
8588 active_slave = <0>;
8689 cpts_clock_mult = <0x80000000>;
8790 cpts_clock_shift = <29>;
91+ syscon = <&cm>;
8892 cpsw_emac0: slave@0 {
8993 phy_id = <&davinci_mdio>, <0>;
9094 phy-mode = "rgmii-txid";
Documentation/devicetree/bindings/net/dsa/dsa.txt+25−1
@@ -10,7 +10,7 @@ Required properties: · 9 unmodified lines
1010 - dsa,ethernet : Should be a phandle to a valid Ethernet device node
1111 - dsa,mii-bus : Should be a phandle to a valid MDIO bus device node
1212
13−Optionnal properties:
13+Optional properties:
1414 - interrupts : property with a value describing the switch
1515 interrupt number (not supported by the driver)
1616
@@ -23,6 +23,13 @@ Each of these switch child nodes should have the following required properties: · 6 unmodified lines
2323 - #address-cells : Must be 1
2424 - #size-cells : Must be 0
2525
26+A switch child node has the following optional property:
27+
28+- eeprom-length : Set to the length of an EEPROM connected to the
29+ switch. Must be set if the switch can not detect
30+ the presence and/or size of a connected EEPROM,
31+ otherwise optional.
32+
2633 A switch may have multiple "port" children nodes
2734
2835 Each port children node must have the following mandatory properties:
@@ -39,6 +46,22 @@ Optionnal property: · 10 unmodified lines
3946 This property is only used when switches are being
4047 chained/cascaded together.
4148
49+- phy-handle : Phandle to a PHY on an external MDIO bus, not the
50+ switch internal one. See
51+ Documentation/devicetree/bindings/net/ethernet.txt
52+ for details.
53+
54+- phy-mode : String representing the connection to the designated
55+ PHY node specified by the 'phy-handle' property. See
56+ Documentation/devicetree/bindings/net/ethernet.txt
57+ for details.
58+
59+Optional subnodes:
60+- fixed-link : Fixed-link subnode describing a link to a non-MDIO
61+ managed entity. See
62+ Documentation/devicetree/bindings/net/fixed-link.txt
63+ for details.
64+
4265 Example:
4366
4467 dsa@0 {
@@ -58,6 +81,7 @@ Example: · 13 unmodified lines
5881 port@0 {
5982 reg = <0>;
6083 label = "lan1";
84+ phy-handle = <&phy0>;
6185 };
6286
6387 port@1 {
Documentation/devicetree/bindings/net/emac_rockchip.txt+50−0
@@ -0,0 +1,50 @@
1+* ARC EMAC 10/100 Ethernet platform driver for Rockchip Rk3066/RK3188 SoCs
2+
3+Required properties:
4+- compatible: Should be "rockchip,rk3066-emac" or "rockchip,rk3188-emac"
5+ according to the target SoC.
6+- reg: Address and length of the register set for the device
7+- interrupts: Should contain the EMAC interrupts
8+- rockchip,grf: phandle to the syscon grf used to control speed and mode
9+ for emac.
10+- phy: see ethernet.txt file in the same directory.
11+- phy-mode: see ethernet.txt file in the same directory.
12+
13+Optional properties:
14+- phy-supply: phandle to a regulator if the PHY needs one
15+
16+Clock handling:
17+- clocks: Must contain an entry for each entry in clock-names.
18+- clock-names: Shall be "hclk" for the host clock needed to calculate and set
19+ polling period of EMAC and "macref" for the reference clock needed to transfer
20+ data to and from the phy.
21+
22+Child nodes of the driver are the individual PHY devices connected to the
23+MDIO bus. They must have a "reg" property given the PHY address on the MDIO bus.
24+
25+Examples:
26+
27+ethernet@10204000 {
28+ compatible = "rockchip,rk3188-emac";
29+ reg = <0xc0fc2000 0x3c>;
30+ interrupts = <6>;
31+ mac-address = [ 00 11 22 33 44 55 ];
32+
33+ clocks = <&cru HCLK_EMAC>, <&cru SCLK_MAC>;
34+ clock-names = "hclk", "macref";
35+
36+ pinctrl-names = "default";
37+ pinctrl-0 = <&emac_xfer>, <&emac_mdio>, <&phy_int>;
38+
39+ rockchip,grf = <&grf>;
40+
41+ phy = <&phy0>;
42+ phy-mode = "rmii";
43+ phy-supply = <&vcc_rmii>;
44+
45+ #address-cells = <1>;
46+ #size-cells = <0>;
47+ phy0: ethernet-phy@0 {
48+ reg = <1>;
49+ };
50+};
Documentation/devicetree/bindings/net/fsl-fec.txt+6−0
@@ -16,6 +16,12 @@ Optional properties: · 15 unmodified lines
1616 - phy-handle : phandle to the PHY device connected to this device.
1717 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
1818 Use instead of phy-handle.
19+- fsl,num-tx-queues : The property is valid for enet-avb IP, which supports
20+ hw multi queues. Should specify the tx queue number, otherwise set tx queue
21+ number to 1.
22+- fsl,num-rx-queues : The property is valid for enet-avb IP, which supports
23+ hw multi queues. Should specify the rx queue number, otherwise set rx queue
24+ number to 1.
1925
2026 Optional subnodes:
2127 - mdio : specifies the mdio bus in the FEC, used as a container for phy nodes
Documentation/devicetree/bindings/net/marvell-pxa168.txt+36−0
@@ -0,0 +1,36 @@
1+* Marvell PXA168 Ethernet Controller
2+
3+Required properties:
4+- compatible: should be "marvell,pxa168-eth".
5+- reg: address and length of the register set for the device.
6+- interrupts: interrupt for the device.
7+- clocks: pointer to the clock for the device.
8+
9+Optional properties:
10+- port-id: Ethernet port number. Should be '0','1' or '2'.
11+- #address-cells: must be 1 when using sub-nodes.
12+- #size-cells: must be 0 when using sub-nodes.
13+- phy-handle: see ethernet.txt file in the same directory.
14+- local-mac-address: see ethernet.txt file in the same directory.
15+
16+Sub-nodes:
17+Each PHY can be represented as a sub-node. This is not mandatory.
18+
19+Sub-nodes required properties:
20+- reg: the MDIO address of the PHY.
21+
22+Example:
23+
24+ eth0: ethernet@f7b90000 {
25+ compatible = "marvell,pxa168-eth";
26+ reg = <0xf7b90000 0x10000>;
27+ clocks = <&chip CLKID_GETH0>;
28+ interrupts = <GIC_SPI 24 IRQ_TYPE_LEVEL_HIGH>;
29+ #address-cells = <1>;
30+ #size-cells = <0>;
31+ phy-handle = <&ethphy0>;
32+
33+ ethphy0: ethernet-phy@0 {
34+ reg = <0>;
35+ };
36+ };
Documentation/devicetree/bindings/net/meson-dwmac.txt+25−0
@@ -0,0 +1,25 @@
1+* Amlogic Meson DWMAC Ethernet controller
2+
3+The device inherits all the properties of the dwmac/stmmac devices
4+described in the file net/stmmac.txt with the following changes.
5+
6+Required properties:
7+
8+- compatible: should be "amlogic,meson6-dwmac" along with "snps,dwmac"
9+ and any applicable more detailed version number
10+ described in net/stmmac.txt
11+
12+- reg: should contain a register range for the dwmac controller and
13+ another one for the Amlogic specific configuration
14+
15+Example:
16+
17+ ethmac: ethernet@c9410000 {
18+ compatible = "amlogic,meson6-dwmac", "snps,dwmac";
19+ reg = <0xc9410000 0x10000
20+ 0xc1108108 0x4>;
21+ interrupts = <0 8 1>;
22+ interrupt-names = "macirq";
23+ clocks = <&clk81>;
24+ clock-names = "stmmaceth";
25+ }
Documentation/devicetree/bindings/net/micrel.txt+27−8
@@ -6,13 +6,32 @@ Optional properties: · 5 unmodified lines
66
77 - micrel,led-mode : LED mode value to set for PHYs with configurable LEDs.
88
9− Configure the LED mode with single value. The list of PHYs and
10− the bits that are currently supported:
9+ Configure the LED mode with single value. The list of PHYs and the
10+ bits that are currently supported:
1111
12− KSZ8001: register 0x1e, bits 15..14
13− KSZ8041: register 0x1e, bits 15..14
14− KSZ8021: register 0x1f, bits 5..4
15− KSZ8031: register 0x1f, bits 5..4
16− KSZ8051: register 0x1f, bits 5..4
12+ KSZ8001: register 0x1e, bits 15..14
13+ KSZ8041: register 0x1e, bits 15..14
14+ KSZ8021: register 0x1f, bits 5..4
15+ KSZ8031: register 0x1f, bits 5..4
16+ KSZ8051: register 0x1f, bits 5..4
17+ KSZ8081: register 0x1f, bits 5..4
18+ KSZ8091: register 0x1f, bits 5..4
1719
18− See the respective PHY datasheet for the mode values.
20+ See the respective PHY datasheet for the mode values.
21+
22+ - micrel,rmii-reference-clock-select-25-mhz: RMII Reference Clock Select
23+ bit selects 25 MHz mode
24+
25+ Setting the RMII Reference Clock Select bit enables 25 MHz rather
26+ than 50 MHz clock mode.
27+
28+ Note that this option in only needed for certain PHY revisions with a
29+ non-standard, inverted function of this configuration bit.
30+ Specifically, a clock reference ("rmii-ref" below) is always needed to
31+ actually select a mode.
32+
33+ - clocks, clock-names: contains clocks according to the common clock bindings.
34+
35+ supported clocks:
36+ - KSZ8021, KSZ8031, KSZ8081, KSZ8091: "rmii-ref": The RMII reference
37+ input clock. Used to determine the XI input clock.
Documentation/devicetree/bindings/net/nfc/st21nfcb.txt+1−1
@@ -26,7 +26,7 @@ Example (for ARM-based BeagleBoard xM with ST21NFCB on I2C2): · 25 unmodified lines
2626 clock-frequency = <400000>;
2727
2828 interrupt-parent = <&gpio5>;
29− interrupts = <2 IRQ_TYPE_LEVEL_LOW>;
29+ interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
3030
3131 reset-gpios = <&gpio5 29 GPIO_ACTIVE_HIGH>;
3232 };
Documentation/devicetree/bindings/net/nfc/trf7970a.txt+8−0
@@ -13,6 +13,11 @@ Optional SoC Specific Properties: · 12 unmodified lines
1313 - pinctrl-names: Contains only one value - "default".
1414 - pintctrl-0: Specifies the pin control groups used for this controller.
1515 - autosuspend-delay: Specify autosuspend delay in milliseconds.
16+- vin-voltage-override: Specify voltage of VIN pin in microvolts.
17+- irq-status-read-quirk: Specify that the trf7970a being used has the
18+ "IRQ Status Read" erratum.
19+- en2-rf-quirk: Specify that the trf7970a being used has the "EN2 RF"
20+ erratum.
1621
1722 Example (for ARM-based BeagleBone with TRF7970A on SPI1):
1823
@@ -30,7 +35,10 @@ Example (for ARM-based BeagleBone with TRF7970A on SPI1): · 11 unmodified lines
3035 ti,enable-gpios = <&gpio2 2 GPIO_ACTIVE_LOW>,
3136 <&gpio2 5 GPIO_ACTIVE_LOW>;
3237 vin-supply = <&ldo3_reg>;
38+ vin-voltage-override = <5000000>;
3339 autosuspend-delay = <30000>;
40+ irq-status-read-quirk;
41+ en2-rf-quirk;
3442 status = "okay";
3543 };
3644 };
Documentation/devicetree/bindings/net/phy.txt+2−1
@@ -19,7 +19,6 @@ Optional Properties: · 18 unmodified lines
1919 specifications. If neither of these are specified, the default is to
2020 assume clause 22. The compatible list may also contain other
2121 elements.
22−- max-speed: Maximum PHY supported speed (10, 100, 1000...)
2322
2423 If the phy's identifier is known then the list may contain an entry
2524 of the form: "ethernet-phy-idAAAA.BBBB" where
@@ -29,6 +28,8 @@ Optional Properties: · 3 unmodified lines
2928 4 hex digits. This is the chip vendor OUI bits 19:24,
3029 followed by 10 bits of a vendor specific ID.
3130
31+- max-speed: Maximum PHY supported speed (10, 100, 1000...)
32+
3233 Example:
3334
3435 ethernet-phy@0 {
Documentation/devicetree/bindings/net/qca-qca7000-spi.txt+47−0
@@ -0,0 +1,47 @@
1+* Qualcomm QCA7000 (Ethernet over SPI protocol)
2+
3+Note: The QCA7000 is useable as a SPI device. In this case it must be defined
4+as a child of a SPI master in the device tree.
5+
6+Required properties:
7+- compatible : Should be "qca,qca7000"
8+- reg : Should specify the SPI chip select
9+- interrupts : The first cell should specify the index of the source interrupt
10+ and the second cell should specify the trigger type as rising edge
11+- spi-cpha : Must be set
12+- spi-cpol: Must be set
13+
14+Optional properties:
15+- interrupt-parent : Specify the pHandle of the source interrupt
16+- spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at.
17+ Numbers smaller than 1000000 or greater than 16000000 are invalid. Missing
18+ the property will set the SPI frequency to 8000000 Hertz.
19+- local-mac-address: 6 bytes, MAC address
20+- qca,legacy-mode : Set the SPI data transfer of the QCA7000 to legacy mode.
21+ In this mode the SPI master must toggle the chip select between each data
22+ word. In burst mode these gaps aren't necessary, which is faster.
23+ This setting depends on how the QCA7000 is setup via GPIO pin strapping.
24+ If the property is missing the driver defaults to burst mode.
25+
26+Example:
27+
28+/* Freescale i.MX28 SPI master*/
29+ssp2: spi@80014000 {
30+ #address-cells = <1>;
31+ #size-cells = <0>;
32+ compatible = "fsl,imx28-spi";
33+ pinctrl-names = "default";
34+ pinctrl-0 = <&spi2_pins_a>;
35+ status = "okay";
36+
37+ qca7000: ethernet@0 {
38+ compatible = "qca,qca7000";
39+ reg = <0x0>;
40+ interrupt-parent = <&gpio3>; /* GPIO Bank 3 */
41+ interrupts = <25 0x1>; /* Index: 25, rising edge */
42+ spi-cpha; /* SPI mode: CPHA=1 */
43+ spi-cpol; /* SPI mode: CPOL=1 */
44+ spi-max-frequency = <8000000>; /* freq: 8 MHz */
45+ local-mac-address = [ A0 B0 C0 D0 E0 F0 ];
46+ };
47+};
Documentation/devicetree/bindings/net/samsung-sxgbe.txt+1−1
@@ -17,7 +17,7 @@ Required properties: · 16 unmodified lines
1717 - samsung,pbl: Integer, Programmable Burst Length.
1818 Supported values are 1, 2, 4, 8, 16, or 32.
1919 - samsung,burst-map: Integer, Program the possible bursts supported by sxgbe
20− This is an interger and represents allowable DMA bursts when fixed burst.
20+ This is an integer and represents allowable DMA bursts when fixed burst.
2121 Allowable range is 0x01-0x3F. When this field is set fixed burst is enabled.
2222 When fixed length is needed for burst mode, it can be set within allowable
2323 range.
Documentation/devicetree/bindings/net/sh_eth.txt+1−0
@@ -9,6 +9,7 @@ Required properties: · 8 unmodified lines
99 "renesas,ether-r8a7779" if the device is a part of R8A7779 SoC.
1010 "renesas,ether-r8a7790" if the device is a part of R8A7790 SoC.
1111 "renesas,ether-r8a7791" if the device is a part of R8A7791 SoC.
12+ "renesas,ether-r8a7793" if the device is a part of R8A7793 SoC.
1213 "renesas,ether-r8a7794" if the device is a part of R8A7794 SoC.
1314 "renesas,ether-r7s72100" if the device is a part of R7S72100 SoC.
1415 - reg: offset and length of (1) the E-DMAC/feLic register block (required),
Documentation/devicetree/bindings/net/smsc-lan91c111.txt+2−0
@@ -11,3 +11,5 @@ Optional properties: · 10 unmodified lines
1111 are supported on the device. Valid value for SMSC LAN91c111 are
1212 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning
1313 16-bit access only.
14+- power-gpios: GPIO to control the PWRDWN pin
15+- reset-gpios: GPIO to control the RESET pin
Documentation/devicetree/bindings/net/socfpga-dwmac.txt+4−0
@@ -12,6 +12,10 @@ Required properties: · 11 unmodified lines
1212 - altr,sysmgr-syscon : Should be the phandle to the system manager node that
1313 encompasses the glue register, the register offset, and the register shift.
1414
15+Optional properties:
16+altr,emac-splitter: Should be the phandle to the emac splitter soft IP node if
17+ DWMAC controller is connected emac splitter.
18+
1519 Example:
1620
1721 gmac0: ethernet@ff700000 {
Documentation/devicetree/bindings/net/sti-dwmac.txt+49−42
@@ -1,58 +1,65 @@
11 STMicroelectronics SoC DWMAC glue layer controller
22
3+This file documents differences between the core properties in
4+Documentation/devicetree/bindings/net/stmmac.txt
5+and what is needed on STi platforms to program the stmmac glue logic.
6+
37 The device node has following properties.
48
59 Required properties:
6− - compatible : Can be "st,stih415-dwmac", "st,stih416-dwmac" or
7− "st,stid127-dwmac".
8− - reg : Offset of the glue configuration register map in system
10+ - compatible : Can be "st,stih415-dwmac", "st,stih416-dwmac",
11+ "st,stih407-dwmac", "st,stid127-dwmac".
12+ - reg : Offset of the glue configuration register map in system
913 configuration regmap pointed by st,syscon property and size.
10−
11− - reg-names : Should be "sti-ethconf".
12−
13− - st,syscon : Should be phandle to system configuration node which
14+ - st,syscon : Should be phandle to system configuration node which
1415 encompases this glue registers.
16+ - st,gmac_en: this is to enable the gmac into a dedicated sysctl control
17+ register available on STiH407 SoC.
18+ - sti-ethconf: this is the gmac glue logic register to enable the GMAC,
19+ select among the different modes and program the clk retiming.
20+ - pinctrl-0: pin-control for all the MII mode supported.
1521
16− - st,tx-retime-src: On STi Parts for Giga bit speeds, 125Mhz clocks can be
17− wired up in from different sources. One via TXCLK pin and other via CLK_125
18− pin. This wiring is totally board dependent. However the retiming glue
19− logic should be configured accordingly. Possible values for this property
20−
21− "txclk" - if 125Mhz clock is wired up via txclk line.
22− "clk_125" - if 125Mhz clock is wired up via clk_125 line.
23−
24− This property is only valid for Giga bit setup( GMII, RGMII), and it is
25− un-used for non-giga bit (MII and RMII) setups. Also note that internal
26− clockgen can not generate stable 125Mhz clock.
27−
28− - st,ext-phyclk: This boolean property indicates who is generating the clock
29− for tx and rx. This property is only valid for RMII case where the clock can
30− be generated from the MAC or PHY.
31−
32− - clock-names: should be "sti-ethclk".
33− - clocks: Should point to ethernet clockgen which can generate phyclk.
34−
22+Optional properties:
23+ - resets : phandle pointing to the system reset controller with correct
24+ reset line index for ethernet reset.
25+ - st,ext-phyclk: valid only for RMII where PHY can generate 50MHz clock or
26+ MAC can generate it.
27+ - st,tx-retime-src: This specifies which clk is wired up to the mac for
28+ retimeing tx lines. This is totally board dependent and can take one of the
29+ posssible values from "txclk", "clk_125" or "clkgen".
30+ If not passed, the internal clock will be used by default.
31+ - sti-ethclk: this is the phy clock.
32+ - sti-clkconf: this is an extra sysconfig register, available in new SoCs,
33+ to program the clk retiming.
34+ - st,gmac_en: to enable the GMAC, this only is present in some SoCs; e.g.
35+ STiH407.
3536
3637 Example:
3738
38−ethernet0: dwmac@fe810000 {
39− device_type = "network";
40− compatible = "st,stih416-dwmac", "snps,dwmac", "snps,dwmac-3.710";
41− reg = <0xfe810000 0x8000>, <0x8bc 0x4>;
42− reg-names = "stmmaceth", "sti-ethconf";
43− interrupts = <0 133 0>, <0 134 0>, <0 135 0>;
44− interrupt-names = "macirq", "eth_wake_irq", "eth_lpi";
45− phy-mode = "mii";
39+ethernet0: dwmac@9630000 {
40+ device_type = "network";
41+ status = "disabled";
42+ compatible = "st,stih407-dwmac", "snps,dwmac", "snps,dwmac-3.710";
43+ reg = <0x9630000 0x8000>, <0x80 0x4>;
44+ reg-names = "stmmaceth", "sti-ethconf";
4645
47− st,syscon = <&syscfg_rear>;
46+ st,syscon = <&syscfg_sbc_reg>;
47+ st,gmac_en;
48+ resets = <&softreset STIH407_ETH1_SOFTRESET>;
49+ reset-names = "stmmaceth";
4850
49− snps,pbl = <32>;
51+ interrupts = <GIC_SPI 98 IRQ_TYPE_NONE>,
52+ <GIC_SPI 99 IRQ_TYPE_NONE>,
53+ <GIC_SPI 100 IRQ_TYPE_NONE>;
54+ interrupt-names = "macirq", "eth_wake_irq", "eth_lpi";
55+
56+ snps,pbl = <32>;
5057 snps,mixed-burst;
5158
52− resets = <&softreset STIH416_ETH0_SOFTRESET>;
53− reset-names = "stmmaceth";
54− pinctrl-0 = <&pinctrl_mii0>;
55− pinctrl-names = "default";
56− clocks = <&CLK_S_GMAC0_PHY>;
57− clock-names = "stmmaceth";
59+ pinctrl-names = "default";
60+ pinctrl-0 = <&pinctrl_rgmii1>;
61+
62+ clock-names = "stmmaceth", "sti-ethclk";
63+ clocks = <&CLK_S_C0_FLEXGEN CLK_EXT2F_A9>,
64+ <&CLK_S_C0_FLEXGEN CLK_ETH_PHY>;
5865 };
Documentation/devicetree/bindings/net/stmmac.txt+1−1
@@ -58,5 +58,5 @@ Examples: · 57 unmodified lines
5858 snps,multicast-filter-bins = <256>;
5959 snps,perfect-filter-entries = <128>;
6060 clocks = <&clock>;
61− clock-names = "stmmaceth">;
61+ clock-names = "stmmaceth";
6262 };
Documentation/devicetree/bindings/nios2/nios2.txt+62−0
@@ -0,0 +1,62 @@
1+* Nios II Processor Binding
2+
3+This binding specifies what properties available in the device tree
4+representation of a Nios II Processor Core.
5+
6+Users can use sopc2dts tool for generating device tree sources (dts) from a
7+Qsys system. See more detail in: http://www.alterawiki.com/wiki/Sopc2dts
8+
9+Required properties:
10+
11+- compatible: Compatible property value should be "altr,nios2-1.0".
12+- reg: Contains CPU index.
13+- interrupt-controller: Specifies that the node is an interrupt controller
14+- #interrupt-cells: Specifies the number of cells needed to encode an
15+ interrupt source, should be 1.
16+- clock-frequency: Contains the clock frequency for CPU, in Hz.
17+- dcache-line-size: Contains data cache line size.
18+- icache-line-size: Contains instruction line size.
19+- dcache-size: Contains data cache size.
20+- icache-size: Contains instruction cache size.
21+- altr,pid-num-bits: Specifies the number of bits to use to represent the process
22+ identifier (PID).
23+- altr,tlb-num-ways: Specifies the number of set-associativity ways in the TLB.
24+- altr,tlb-num-entries: Specifies the number of entries in the TLB.
25+- altr,tlb-ptr-sz: Specifies size of TLB pointer.
26+- altr,has-mul: Specifies CPU hardware multipy support, should be 1.
27+- altr,has-mmu: Specifies CPU support MMU support, should be 1.
28+- altr,has-initda: Specifies CPU support initda instruction, should be 1.
29+- altr,reset-addr: Specifies CPU reset address
30+- altr,fast-tlb-miss-addr: Specifies CPU fast TLB miss exception address
31+- altr,exception-addr: Specifies CPU exception address
32+
33+Optional properties:
34+- altr,has-div: Specifies CPU hardware divide support
35+- altr,implementation: Nios II core implementation, this should be "fast";
36+
37+Example:
38+
39+cpu@0x0 {
40+ device_type = "cpu";
41+ compatible = "altr,nios2-1.0";
42+ reg = <0>;
43+ interrupt-controller;
44+ #interrupt-cells = <1>;
45+ clock-frequency = <125000000>;
46+ dcache-line-size = <32>;
47+ icache-line-size = <32>;
48+ dcache-size = <32768>;
49+ icache-size = <32768>;
50+ altr,implementation = "fast";
51+ altr,pid-num-bits = <8>;
52+ altr,tlb-num-ways = <16>;
53+ altr,tlb-num-entries = <128>;
54+ altr,tlb-ptr-sz = <7>;
55+ altr,has-div = <1>;
56+ altr,has-mul = <1>;
57+ altr,reset-addr = <0xc2800000>;
58+ altr,fast-tlb-miss-addr = <0xc7fff400>;
59+ altr,exception-addr = <0xd0000020>;
60+ altr,has-initda = <1>;
61+ altr,has-mmu = <1>;
62+};
Documentation/devicetree/bindings/nios2/timer.txt+19−0
@@ -0,0 +1,19 @@
1+Altera Timer
2+
3+Required properties:
4+
5+- compatible : should be "altr,timer-1.0"
6+- reg : Specifies base physical address and size of the registers.
7+- interrupt-parent: phandle of the interrupt controller
8+- interrupts : Should contain the timer interrupt number
9+- clock-frequency : The frequency of the clock that drives the counter, in Hz.
10+
11+Example:
12+
13+timer {
14+ compatible = "altr,timer-1.0";
15+ reg = <0x00400000 0x00000020>;
16+ interrupt-parent = <&cpu>;
17+ interrupts = <11>;
18+ clock-frequency = <125000000>;
19+};
Documentation/devicetree/bindings/panel/auo,b101xtn01.txt+7−0
@@ -0,0 +1,7 @@
1+AU Optronics Corporation 10.1" WXGA TFT LCD panel
2+
3+Required properties:
4+- compatible: should be "auo,b101xtn01"
5+
6+This binding is compatible with the simple-panel binding, which is specified
7+in simple-panel.txt in this directory.
Documentation/devicetree/bindings/panel/auo,b116xw03.txt+7−0
@@ -0,0 +1,7 @@
1+AU Optronics Corporation 11.6" HD (1366x768) color TFT-LCD panel
2+
3+Required properties:
4+- compatible: should be "auo,b116xw03"
5+
6+This binding is compatible with the simple-panel binding, which is specified
7+in simple-panel.txt in this directory.
Documentation/devicetree/bindings/panel/hannstar,hsd070pww1.txt+7−0
@@ -0,0 +1,7 @@
1+HannStar Display Corp. HSD070PWW1 7.0" WXGA TFT LCD panel
2+
3+Required properties:
4+- compatible: should be "hannstar,hsd070pww1"
5+
6+This binding is compatible with the simple-panel binding, which is specified
7+in simple-panel.txt in this directory.
Documentation/devicetree/bindings/panel/hit,tx23d38vm0caa.txt+7−0
@@ -0,0 +1,7 @@
1+Hitachi Ltd. Corporation 9" WVGA (800x480) TFT LCD panel
2+
3+Required properties:
4+- compatible: should be "hit,tx23d38vm0caa"
5+
6+This binding is compatible with the simple-panel binding, which is specified
7+in simple-panel.txt in this directory.
Documentation/devicetree/bindings/panel/innolux,g121i1-l01.txt+7−0
@@ -0,0 +1,7 @@
1+Innolux Corporation 12.1" WXGA (1280x800) TFT LCD panel
2+
3+Required properties:
4+- compatible: should be "innolux,g121i1-l01"
5+
6+This binding is compatible with the simple-panel binding, which is specified
7+in simple-panel.txt in this directory.
Documentation/devicetree/bindings/panel/sharp,lq101r1sx01.txt+49−0
@@ -0,0 +1,49 @@
1+Sharp Microelectronics 10.1" WQXGA TFT LCD panel
2+
3+This panel requires a dual-channel DSI host to operate. It supports two modes:
4+- left-right: each channel drives the left or right half of the screen
5+- even-odd: each channel drives the even or odd lines of the screen
6+
7+Each of the DSI channels controls a separate DSI peripheral. The peripheral
8+driven by the first link (DSI-LINK1), left or even, is considered the primary
9+peripheral and controls the device. The 'link2' property contains a phandle
10+to the peripheral driven by the second link (DSI-LINK2, right or odd).
11+
12+Note that in video mode the DSI-LINK1 interface always provides the left/even
13+pixels and DSI-LINK2 always provides the right/odd pixels. In command mode it
14+is possible to program either link to drive the left/even or right/odd pixels
15+but for the sake of consistency this binding assumes that the same assignment
16+is chosen as for video mode.
17+
18+Required properties:
19+- compatible: should be "sharp,lq101r1sx01"
20+- reg: DSI virtual channel of the peripheral
21+
22+Required properties (for DSI-LINK1 only):
23+- link2: phandle to the DSI peripheral on the secondary link. Note that the
24+ presence of this property marks the containing node as DSI-LINK1.
25+- power-supply: phandle of the regulator that provides the supply voltage
26+
27+Optional properties (for DSI-LINK1 only):
28+- backlight: phandle of the backlight device attached to the panel
29+
30+Example:
31+
32+ dsi@54300000 {
33+ panel: panel@0 {
34+ compatible = "sharp,lq101r1sx01";
35+ reg = <0>;
36+
37+ link2 = <&secondary>;
38+
39+ power-supply = <...>;
40+ backlight = <...>;
41+ };
42+ };
43+
44+ dsi@54400000 {
45+ secondary: panel@0 {
46+ compatible = "sharp,lq101r1sx01";
47+ reg = <0>;
48+ };
49+ };
Documentation/devicetree/bindings/pci/designware-pcie.txt+3−0
@@ -23,3 +23,6 @@ Required properties: · 22 unmodified lines
2323
2424 Optional properties:
2525 - reset-gpio: gpio pin number of power good signal
26+- bus-range: PCI bus numbers covered (it is recommended for new devicetrees to
27+ specify this property, to keep backwards compatibility a range of 0x00-0xff
28+ is assumed if not present)
Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt+3−1
@@ -17,7 +17,9 @@ Example: · 16 unmodified lines
1717
1818 pcie@0x01000000 {
1919 compatible = "fsl,imx6q-pcie", "snps,dw-pcie";
20− reg = <0x01ffc000 0x4000>;
20+ reg = <0x01ffc000 0x04000>,
21+ <0x01f00000 0x80000>;
22+ reg-names = "dbi", "config";
2123 #address-cells = <3>;
2224 #size-cells = <2>;
2325 device_type = "pci";
Documentation/devicetree/bindings/pci/fsl,pci.txt+27−0
@@ -0,0 +1,27 @@
1+* Bus Enumeration by Freescale PCI-X Agent
2+
3+Typically any Freescale PCI-X bridge hardware strapped into Agent mode
4+is prevented from enumerating the bus. The PrPMC form-factor requires
5+all mezzanines to be PCI-X Agents, but one per system may still
6+enumerate the bus.
7+
8+The property defined below will allow a PCI-X bridge to be used for bus
9+enumeration despite being strapped into Agent mode.
10+
11+Required properties:
12+- fsl,pci-agent-force-enum : There is no value associated with this
13+ property. The property itself is treated as a boolean.
14+
15+Example:
16+
17+ /* PCI-X bridge known to be PrPMC Monarch */
18+ pci0: pci@ef008000 {
19+ fsl,pci-agent-force-enum;
20+ #interrupt-cells = <1>;
21+ #size-cells = <2>;
22+ #address-cells = <3>;
23+ compatible = "fsl,mpc8540-pcix", "fsl,mpc8540-pci";
24+ device_type = "pci";
25+ ...
26+ ...
27+ };
Documentation/devicetree/bindings/pci/host-generic-pci.txt+1−1
@@ -55,7 +55,7 @@ For CAM, this 24-bit offset is: · 54 unmodified lines
5555 cfg_offset(bus, device, function, register) =
5656 bus << 16 | device << 11 | function << 8 | register
5757
58−Whilst ECAM extends this by 4 bits to accomodate 4k of function space:
58+Whilst ECAM extends this by 4 bits to accommodate 4k of function space:
5959
6060 cfg_offset(bus, device, function, register) =
6161 bus << 20 | device << 15 | function << 12 | register
Documentation/devicetree/bindings/pci/layerscape-pci.txt+42−0
@@ -0,0 +1,42 @@
1+Freescale Layerscape PCIe controller
2+
3+This PCIe host controller is based on the Synopsis Designware PCIe IP
4+and thus inherits all the common properties defined in designware-pcie.txt.
5+
6+Required properties:
7+- compatible: should contain the platform identifier such as "fsl,ls1021a-pcie"
8+- reg: base addresses and lengths of the PCIe controller
9+- interrupts: A list of interrupt outputs of the controller. Must contain an
10+ entry for each entry in the interrupt-names property.
11+- interrupt-names: Must include the following entries:
12+ "intr": The interrupt that is asserted for controller interrupts
13+- fsl,pcie-scfg: Must include two entries.
14+ The first entry must be a link to the SCFG device node
15+ The second entry must be '0' or '1' based on physical PCIe controller index.
16+ This is used to get SCFG PEXN registers
17+
18+Example:
19+
20+ pcie@3400000 {
21+ compatible = "fsl,ls1021a-pcie", "snps,dw-pcie";
22+ reg = <0x00 0x03400000 0x0 0x00010000 /* controller registers */
23+ 0x40 0x00000000 0x0 0x00002000>; /* configuration space */
24+ reg-names = "regs", "config";
25+ interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH>; /* controller interrupt */
26+ interrupt-names = "intr";
27+ fsl,pcie-scfg = <&scfg 0>;
28+ #address-cells = <3>;
29+ #size-cells = <2>;
30+ device_type = "pci";
31+ num-lanes = <4>;
32+ bus-range = <0x0 0xff>;
33+ ranges = <0x81000000 0x0 0x00000000 0x40 0x00010000 0x0 0x00010000 /* downstream I/O */
34+ 0xc2000000 0x0 0x20000000 0x40 0x20000000 0x0 0x20000000 /* prefetchable memory */
35+ 0x82000000 0x0 0x40000000 0x40 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
36+ #interrupt-cells = <1>;
37+ interrupt-map-mask = <0 0 0 7>;
38+ interrupt-map = <0000 0 0 1 &gic GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>,
39+ <0000 0 0 2 &gic GIC_SPI 188 IRQ_TYPE_LEVEL_HIGH>,
40+ <0000 0 0 3 &gic GIC_SPI 190 IRQ_TYPE_LEVEL_HIGH>,
41+ <0000 0 0 4 &gic GIC_SPI 192 IRQ_TYPE_LEVEL_HIGH>;
42+ };
Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt+24−1
@@ -1,7 +1,10 @@
11 NVIDIA Tegra PCIe controller
22
33 Required properties:
4−- compatible: "nvidia,tegra20-pcie" or "nvidia,tegra30-pcie"
4+- compatible: Must be one of:
5+ - "nvidia,tegra20-pcie"
6+ - "nvidia,tegra30-pcie"
7+ - "nvidia,tegra124-pcie"
58 - device_type: Must be "pci"
69 - reg: A list of physical base address and length for each set of controller
710 registers. Must contain an entry for each entry in the reg-names property.
@@ -57,6 +60,11 @@ Required properties: · 49 unmodified lines
5760 - afi
5861 - pcie_x
5962
63+Required properties on Tegra124 and later:
64+- phys: Must contain an entry for each entry in phy-names.
65+- phy-names: Must include the following entries:
66+ - pcie
67+
6068 Power supplies for Tegra20:
6169 - avdd-pex-supply: Power supply for analog PCIe logic. Must supply 1.05 V.
6270 - vdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
@@ -84,6 +92,21 @@ Power supplies for Tegra30: · 21 unmodified lines
8492 - avdd-pexb-supply: Power supply for analog PCIe logic. Must supply 1.05 V.
8593 - vdd-pexb-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
8694
95+Power supplies for Tegra124:
96+- Required:
97+ - avddio-pex-supply: Power supply for analog PCIe logic. Must supply 1.05 V.
98+ - dvddio-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
99+ - avdd-pex-pll-supply: Power supply for dedicated (internal) PCIe PLL. Must
100+ supply 1.05 V.
101+ - hvdd-pex-supply: High-voltage supply for PCIe I/O and PCIe output clocks.
102+ Must supply 3.3 V.
103+ - hvdd-pex-pll-e-supply: High-voltage supply for PLLE (shared with USB3).
104+ Must supply 3.3 V.
105+ - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must
106+ supply 2.8-3.3 V.
107+ - avdd-pll-erefe-supply: Power supply for PLLE (shared with USB3). Must
108+ supply 1.05 V.
109+
87110 Root ports are defined as subnodes of the PCIe controller node.
88111
89112 Required properties:
Documentation/devicetree/bindings/pci/pci-keystone.txt+63−0
@@ -0,0 +1,63 @@
1+TI Keystone PCIe interface
2+
3+Keystone PCI host Controller is based on Designware PCI h/w version 3.65.
4+It shares common functions with PCIe Designware core driver and inherit
5+common properties defined in
6+Documentation/devicetree/bindings/pci/designware-pci.txt
7+
8+Please refer to Documentation/devicetree/bindings/pci/designware-pci.txt
9+for the details of Designware DT bindings. Additional properties are
10+described here as well as properties that are not applicable.
11+
12+Required Properties:-
13+
14+compatibility: "ti,keystone-pcie"
15+reg: index 1 is the base address and length of DW application registers.
16+ index 2 is the base address and length of PCI device ID register.
17+
18+pcie_msi_intc : Interrupt controller device node for MSI IRQ chip
19+ interrupt-cells: should be set to 1
20+ interrupt-parent: Parent interrupt controller phandle
21+ interrupts: GIC interrupt lines connected to PCI MSI interrupt lines
22+
23+ Example:
24+ pcie_msi_intc: msi-interrupt-controller {
25+ interrupt-controller;
26+ #interrupt-cells = <1>;
27+ interrupt-parent = <&gic>;
28+ interrupts = <GIC_SPI 30 IRQ_TYPE_EDGE_RISING>,
29+ <GIC_SPI 31 IRQ_TYPE_EDGE_RISING>,
30+ <GIC_SPI 32 IRQ_TYPE_EDGE_RISING>,
31+ <GIC_SPI 33 IRQ_TYPE_EDGE_RISING>,
32+ <GIC_SPI 34 IRQ_TYPE_EDGE_RISING>,
33+ <GIC_SPI 35 IRQ_TYPE_EDGE_RISING>,
34+ <GIC_SPI 36 IRQ_TYPE_EDGE_RISING>,
35+ <GIC_SPI 37 IRQ_TYPE_EDGE_RISING>;
36+ };
37+
38+pcie_intc: Interrupt controller device node for Legacy IRQ chip
39+ interrupt-cells: should be set to 1
40+ interrupt-parent: Parent interrupt controller phandle
41+ interrupts: GIC interrupt lines connected to PCI Legacy interrupt lines
42+
43+ Example:
44+ pcie_intc: legacy-interrupt-controller {
45+ interrupt-controller;
46+ #interrupt-cells = <1>;
47+ interrupt-parent = <&gic>;
48+ interrupts = <GIC_SPI 26 IRQ_TYPE_EDGE_RISING>,
49+ <GIC_SPI 27 IRQ_TYPE_EDGE_RISING>,
50+ <GIC_SPI 28 IRQ_TYPE_EDGE_RISING>,
51+ <GIC_SPI 29 IRQ_TYPE_EDGE_RISING>;
52+ };
53+
54+Optional properties:-
55+ phys: phandle to Generic Keystone SerDes phy for PCI
56+ phy-names: name of the Generic Keystine SerDes phy for PCI
57+ - If boot loader already does PCI link establishment, then phys and
58+ phy-names shouldn't be present.
59+
60+Designware DT Properties not applicable for Keystone PCI
61+
62+1. pcie_bus clock-names not used. Instead, a phandle to phys is used.
63+
Documentation/devicetree/bindings/pci/pci.txt+11−0
@@ -7,3 +7,14 @@ And for the interrupt mapping part: · 6 unmodified lines
77
88 Open Firmware Recommended Practice: Interrupt Mapping
99 http://www.openfirmware.org/1275/practice/imap/imap0_9d.pdf
10+
11+Additionally to the properties specified in the above standards a host bridge
12+driver implementation may support the following properties:
13+
14+- linux,pci-domain:
15+ If present this property assigns a fixed PCI domain number to a host bridge,
16+ otherwise an unstable (across boots) unique number will be assigned.
17+ It is required to either not set this property at all or set it for all
18+ host bridges in the system, otherwise potentially conflicting domain numbers
19+ may be assigned to root buses behind different host bridges. The domain
20+ number for each host bridge in the system must be unique.
Documentation/devicetree/bindings/pci/xgene-pci.txt+57−0
@@ -0,0 +1,57 @@
1+* AppliedMicro X-Gene PCIe interface
2+
3+Required properties:
4+- device_type: set to "pci"
5+- compatible: should contain "apm,xgene-pcie" to identify the core.
6+- reg: A list of physical base address and length for each set of controller
7+ registers. Must contain an entry for each entry in the reg-names
8+ property.
9+- reg-names: Must include the following entries:
10+ "csr": controller configuration registers.
11+ "cfg": pcie configuration space registers.
12+- #address-cells: set to <3>
13+- #size-cells: set to <2>
14+- ranges: ranges for the outbound memory, I/O regions.
15+- dma-ranges: ranges for the inbound memory regions.
16+- #interrupt-cells: set to <1>
17+- interrupt-map-mask and interrupt-map: standard PCI properties
18+ to define the mapping of the PCIe interface to interrupt
19+ numbers.
20+- clocks: from common clock binding: handle to pci clock.
21+
22+Optional properties:
23+- status: Either "ok" or "disabled".
24+- dma-coherent: Present if dma operations are coherent
25+
26+Example:
27+
28+SoC specific DT Entry:
29+
30+ pcie0: pcie@1f2b0000 {
31+ status = "disabled";
32+ device_type = "pci";
33+ compatible = "apm,xgene-storm-pcie", "apm,xgene-pcie";
34+ #interrupt-cells = <1>;
35+ #size-cells = <2>;
36+ #address-cells = <3>;
37+ reg = < 0x00 0x1f2b0000 0x0 0x00010000 /* Controller registers */
38+ 0xe0 0xd0000000 0x0 0x00040000>; /* PCI config space */
39+ reg-names = "csr", "cfg";
40+ ranges = <0x01000000 0x00 0x00000000 0xe0 0x10000000 0x00 0x00010000 /* io */
41+ 0x02000000 0x00 0x80000000 0xe1 0x80000000 0x00 0x80000000>; /* mem */
42+ dma-ranges = <0x42000000 0x80 0x00000000 0x80 0x00000000 0x00 0x80000000
43+ 0x42000000 0x00 0x00000000 0x00 0x00000000 0x80 0x00000000>;
44+ interrupt-map-mask = <0x0 0x0 0x0 0x7>;
45+ interrupt-map = <0x0 0x0 0x0 0x1 &gic 0x0 0xc2 0x1
46+ 0x0 0x0 0x0 0x2 &gic 0x0 0xc3 0x1
47+ 0x0 0x0 0x0 0x3 &gic 0x0 0xc4 0x1
48+ 0x0 0x0 0x0 0x4 &gic 0x0 0xc5 0x1>;
49+ dma-coherent;
50+ clocks = <&pcie0clk 0>;
51+ };
52+
53+
54+Board specific DT Entry:
55+ &pcie0 {
56+ status = "ok";
57+ };
Documentation/devicetree/bindings/pci/xilinx-pcie.txt+62−0
@@ -0,0 +1,62 @@
1+* Xilinx AXI PCIe Root Port Bridge DT description
2+
3+Required properties:
4+- #address-cells: Address representation for root ports, set to <3>
5+- #size-cells: Size representation for root ports, set to <2>
6+- #interrupt-cells: specifies the number of cells needed to encode an
7+ interrupt source. The value must be 1.
8+- compatible: Should contain "xlnx,axi-pcie-host-1.00.a"
9+- reg: Should contain AXI PCIe registers location and length
10+- device_type: must be "pci"
11+- interrupts: Should contain AXI PCIe interrupt
12+- interrupt-map-mask,
13+ interrupt-map: standard PCI properties to define the mapping of the
14+ PCI interface to interrupt numbers.
15+- ranges: ranges for the PCI memory regions (I/O space region is not
16+ supported by hardware)
17+ Please refer to the standard PCI bus binding document for a more
18+ detailed explanation
19+
20+Optional properties:
21+- bus-range: PCI bus numbers covered
22+
23+Interrupt controller child node
24++++++++++++++++++++++++++++++++
25+Required properties:
26+- interrupt-controller: identifies the node as an interrupt controller
27+- #address-cells: specifies the number of cells needed to encode an
28+ address. The value must be 0.
29+- #interrupt-cells: specifies the number of cells needed to encode an
30+ interrupt source. The value must be 1.
31+
32+NOTE:
33+The core provides a single interrupt for both INTx/MSI messages. So,
34+created a interrupt controller node to support 'interrupt-map' DT
35+functionality. The driver will create an IRQ domain for this map, decode
36+the four INTx interrupts in ISR and route them to this domain.
37+
38+
39+Example:
40+++++++++
41+
42+ pci_express: axi-pcie@50000000 {
43+ #address-cells = <3>;
44+ #size-cells = <2>;
45+ #interrupt-cells = <1>;
46+ compatible = "xlnx,axi-pcie-host-1.00.a";
47+ reg = < 0x50000000 0x10000000 >;
48+ device_type = "pci";
49+ interrupts = < 0 52 4 >;
50+ interrupt-map-mask = <0 0 0 7>;
51+ interrupt-map = <0 0 0 1 &pcie_intc 1>,
52+ <0 0 0 2 &pcie_intc 2>,
53+ <0 0 0 3 &pcie_intc 3>,
54+ <0 0 0 4 &pcie_intc 4>;
55+ ranges = < 0x02000000 0 0x60000000 0x60000000 0 0x10000000 >;
56+
57+ pcie_intc: interrupt-controller {
58+ interrupt-controller;
59+ #address-cells = <0>;
60+ #interrupt-cells = <1>;
61+ }
62+ };
Documentation/devicetree/bindings/phy/berlin-sata-phy.txt+3−1
@@ -2,7 +2,9 @@ Berlin SATA PHY · 1 unmodified line
22 ---------------
33
44 Required properties:
5−- compatible: should be "marvell,berlin2q-sata-phy"
5+- compatible: should be one of
6+ "marvell,berlin2-sata-phy"
7+ "marvell,berlin2q-sata-phy"
68 - address-cells: should be 1
79 - size-cells: should be 0
810 - phy-cells: from the generic PHY bindings, must be 1
Documentation/devicetree/bindings/phy/berlin-usb-phy.txt+16−0
@@ -0,0 +1,16 @@
1+* Marvell Berlin USB PHY
2+
3+Required properties:
4+- compatible: "marvell,berlin2-usb-phy" or "marvell,berlin2cd-usb-phy"
5+- reg: base address and length of the registers
6+- #phys-cells: should be 0
7+- resets: reference to the reset controller
8+
9+Example:
10+
11+ usb-phy@f774000 {
12+ compatible = "marvell,berlin2-usb-phy";
13+ reg = <0xf774000 0x128>;
14+ #phy-cells = <0>;
15+ resets = <&chip 0x104 14>;
16+ };
Documentation/devicetree/bindings/phy/phy-bindings.txt+1−1
@@ -27,7 +27,7 @@ phys: phy { · 26 unmodified lines
2727 };
2828
2929 That node describes an IP block (PHY provider) that implements 2 different PHYs.
30−In order to differentiate between these 2 PHYs, an additonal specifier should be
30+In order to differentiate between these 2 PHYs, an additional specifier should be
3131 given while trying to get a reference to it.
3232
3333 PHY user node
Documentation/devicetree/bindings/phy/phy-miphy28lp.txt+128−0
@@ -0,0 +1,128 @@
1+STMicroelectronics STi MIPHY28LP PHY binding
2+============================================
3+
4+This binding describes a miphy device that is used to control PHY hardware
5+for SATA, PCIe or USB3.
6+
7+Required properties (controller (parent) node):
8+- compatible : Should be "st,miphy28lp-phy".
9+- st,syscfg : Should be a phandle of the system configuration register group
10+ which contain the SATA, PCIe or USB3 mode setting bits.
11+
12+Required nodes : A sub-node is required for each channel the controller
13+ provides. Address range information including the usual
14+ 'reg' and 'reg-names' properties are used inside these
15+ nodes to describe the controller's topology. These nodes
16+ are translated by the driver's .xlate() function.
17+
18+Required properties (port (child) node):
19+- #phy-cells : Should be 1 (See second example)
20+ Cell after port phandle is device type from:
21+ - PHY_TYPE_SATA
22+ - PHY_TYPE_PCI
23+ - PHY_TYPE_USB3
24+- reg : Address and length of the register set for the device.
25+- reg-names : The names of the register addresses corresponding to the registers
26+ filled in "reg". It can also contain the offset of the system configuration
27+ registers used as glue-logic to setup the device for SATA/PCIe or USB3
28+ devices.
29+- resets : phandle to the parent reset controller.
30+- reset-names : Associated name must be "miphy-sw-rst".
31+
32+Optional properties (port (child) node):
33+- st,osc-rdy : to check the MIPHY0_OSC_RDY status in the glue-logic. This
34+ is not available in all the MiPHY. For example, for STiH407, only the
35+ MiPHY0 has this bit.
36+- st,osc-force-ext : to select the external oscillator. This can change from
37+ different MiPHY inside the same SoC.
38+- st,sata_gen : to select which SATA_SPDMODE has to be set in the SATA system config
39+ register.
40+- st,px_rx_pol_inv : to invert polarity of RXn/RXp (respectively negative line and positive
41+ line).
42+- st,scc-on : enable ssc to reduce effects of EMI (only for sata or PCIe).
43+- st,tx-impedance-comp : to compensate tx impedance avoiding out of range values.
44+
45+example:
46+
47+ miphy28lp_phy: miphy28lp@9b22000 {
48+ compatible = "st,miphy28lp-phy";
49+ st,syscfg = <&syscfg_core>;
50+ #address-cells = <1>;
51+ #size-cells = <1>;
52+ ranges;
53+
54+ phy_port0: port@9b22000 {
55+ reg = <0x9b22000 0xff>,
56+ <0x9b09000 0xff>,
57+ <0x9b04000 0xff>,
58+ <0x114 0x4>, /* sysctrl MiPHY cntrl */
59+ <0x818 0x4>, /* sysctrl MiPHY status*/
60+ <0xe0 0x4>, /* sysctrl PCIe */
61+ <0xec 0x4>; /* sysctrl SATA */
62+ reg-names = "sata-up",
63+ "pcie-up",
64+ "pipew",
65+ "miphy-ctrl-glue",
66+ "miphy-status-glue",
67+ "pcie-glue",
68+ "sata-glue";
69+ #phy-cells = <1>;
70+ st,osc-rdy;
71+ reset-names = "miphy-sw-rst";
72+ resets = <&softreset STIH407_MIPHY0_SOFTRESET>;
73+ };
74+
75+ phy_port1: port@9b2a000 {
76+ reg = <0x9b2a000 0xff>,
77+ <0x9b19000 0xff>,
78+ <0x9b14000 0xff>,
79+ <0x118 0x4>,
80+ <0x81c 0x4>,
81+ <0xe4 0x4>,
82+ <0xf0 0x4>;
83+ reg-names = "sata-up",
84+ "pcie-up",
85+ "pipew",
86+ "miphy-ctrl-glue",
87+ "miphy-status-glue",
88+ "pcie-glue",
89+ "sata-glue";
90+ #phy-cells = <1>;
91+ st,osc-force-ext;
92+ reset-names = "miphy-sw-rst";
93+ resets = <&softreset STIH407_MIPHY1_SOFTRESET>;
94+ };
95+
96+ phy_port2: port@8f95000 {
97+ reg = <0x8f95000 0xff>,
98+ <0x8f90000 0xff>,
99+ <0x11c 0x4>,
100+ <0x820 0x4>;
101+ reg-names = "pipew",
102+ "usb3-up",
103+ "miphy-ctrl-glue",
104+ "miphy-status-glue";
105+ #phy-cells = <1>;
106+ reset-names = "miphy-sw-rst";
107+ resets = <&softreset STIH407_MIPHY2_SOFTRESET>;
108+ };
109+ };
110+
111+
112+Specifying phy control of devices
113+=================================
114+
115+Device nodes should specify the configuration required in their "phys"
116+property, containing a phandle to the miphy device node and an index
117+specifying which configuration to use, as described in phy-bindings.txt.
118+
119+example:
120+ sata0: sata@9b20000 {
121+ ...
122+ phys = <&phy_port0 PHY_TYPE_SATA>;
123+ ...
124+ };
125+
126+Macro definitions for the supported miphy configuration can be found in:
127+
128+include/dt-bindings/phy/phy-miphy28lp.h
Documentation/devicetree/bindings/phy/phy-mvebu.txt+43−0
@@ -0,0 +1,43 @@
1+* Marvell MVEBU SATA PHY
2+
3+Power control for the SATA phy found on Marvell MVEBU SoCs.
4+
5+This document extends the binding described in phy-bindings.txt
6+
7+Required properties :
8+
9+ - reg : Offset and length of the register set for the SATA device
10+ - compatible : Should be "marvell,mvebu-sata-phy"
11+ - clocks : phandle of clock and specifier that supplies the device
12+ - clock-names : Should be "sata"
13+
14+Example:
15+ sata-phy@84000 {
16+ compatible = "marvell,mvebu-sata-phy";
17+ reg = <0x84000 0x0334>;
18+ clocks = <&gate_clk 15>;
19+ clock-names = "sata";
20+ #phy-cells = <0>;
21+ status = "ok";
22+ };
23+
24+Armada 375 USB cluster
25+----------------------
26+
27+Armada 375 comes with an USB2 host and device controller and an USB3
28+controller. The USB cluster control register allows to manage common
29+features of both USB controllers.
30+
31+Required properties:
32+
33+- compatible: "marvell,armada-375-usb-cluster"
34+- reg: Should contain usb cluster register location and length.
35+- #phy-cells : from the generic phy bindings, must be 1. Possible
36+values are 1 (USB2), 2 (USB3).
37+
38+Example:
39+ usbcluster: usb-cluster@18400 {
40+ compatible = "marvell,armada-375-usb-cluster";
41+ reg = <0x18400 0x4>;
42+ #phy-cells = <1>
43+ };
Documentation/devicetree/bindings/phy/phy-stih407-usb.txt+30−0
@@ -0,0 +1,30 @@
1+ST STiH407 USB PHY controller
2+
3+This file documents the dt bindings for the usb picoPHY driver which is the PHY for both USB2 and USB3
4+host controllers (when controlling usb2/1.1 devices) available on STiH407 SoC family from STMicroelectronics.
5+
6+Required properties:
7+- compatible : should be "st,stih407-usb2-phy"
8+- reg : contain the offset and length of the system configuration registers
9+ used as glue logic to control & parameter phy
10+- reg-names : the names of the system configuration registers in "reg", should be "param" and "reg"
11+- st,syscfg : sysconfig register to manage phy parameter at driver level
12+- resets : list of phandle and reset specifier pairs. There should be two entries, one
13+ for the whole phy and one for the port
14+- reset-names : list of reset signal names. Should be "global" and "port"
15+See: Documentation/devicetree/bindings/reset/st,sti-powerdown.txt
16+See: Documentation/devicetree/bindings/reset/reset.txt
17+
18+Example:
19+
20+usb2_picophy0: usbpicophy@f8 {
21+ compatible = "st,stih407-usb2-phy";
22+ reg = <0xf8 0x04>, /* syscfg 5062 */
23+ <0xf4 0x04>; /* syscfg 5061 */
24+ reg-names = "param", "ctrl";
25+ #phy-cells = <0>;
26+ st,syscfg = <&syscfg_core>;
27+ resets = <&softreset STIH407_PICOPHY_SOFTRESET>,
28+ <&picophyreset STIH407_PICOPHY0_RESET>;
29+ reset-names = "global", "port";
30+};
Documentation/devicetree/bindings/phy/phy-stih41x-usb.txt+24−0
@@ -0,0 +1,24 @@
1+STMicroelectronics STiH41x USB PHY binding
2+------------------------------------------
3+
4+This file contains documentation for the usb phy found in STiH415/6 SoCs from
5+STMicroelectronics.
6+
7+Required properties:
8+- compatible : should be "st,stih416-usb-phy" or "st,stih415-usb-phy"
9+- st,syscfg : should be a phandle of the syscfg node
10+- clock-names : must contain "osc_phy"
11+- clocks : must contain an entry for each name in clock-names.
12+See: Documentation/devicetree/bindings/clock/clock-bindings.txt
13+- #phy-cells : must be 0 for this phy
14+See: Documentation/devicetree/bindings/phy/phy-bindings.txt
15+
16+Example:
17+
18+usb2_phy: usb2phy@0 {
19+ compatible = "st,stih416-usb-phy";
20+ #phy-cell = <0>;
21+ st,syscfg = <&syscfg_rear>;
22+ clocks = <&clk_sysin>;
23+ clock-names = "osc_phy";
24+};
Documentation/devicetree/bindings/phy/qcom-dwc3-usb-phy.txt+39−0
@@ -0,0 +1,39 @@
1+Qualcomm DWC3 HS AND SS PHY CONTROLLER
2+--------------------------------------
3+
4+DWC3 PHY nodes are defined to describe on-chip Synopsis Physical layer
5+controllers. Each DWC3 PHY controller should have its own node.
6+
7+Required properties:
8+- compatible: should contain one of the following:
9+ - "qcom,dwc3-hs-usb-phy" for High Speed Synopsis PHY controller
10+ - "qcom,dwc3-ss-usb-phy" for Super Speed Synopsis PHY controller
11+- reg: offset and length of the DWC3 PHY controller register set
12+- #phy-cells: must be zero
13+- clocks: a list of phandles and clock-specifier pairs, one for each entry in
14+ clock-names.
15+- clock-names: Should contain "ref" for the PHY reference clock
16+
17+Optional clocks:
18+ "xo" External reference clock
19+
20+Example:
21+ phy@100f8800 {
22+ compatible = "qcom,dwc3-hs-usb-phy";
23+ reg = <0x100f8800 0x30>;
24+ clocks = <&gcc USB30_0_UTMI_CLK>;
25+ clock-names = "ref";
26+ #phy-cells = <0>;
27+
28+ status = "ok";
29+ };
30+
31+ phy@100f8830 {
32+ compatible = "qcom,dwc3-ss-usb-phy";
33+ reg = <0x100f8830 0x30>;
34+ clocks = <&gcc USB30_0_MASTER_CLK>;
35+ clock-names = "ref";
36+ #phy-cells = <0>;
37+
38+ status = "ok";
39+ };
Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt+51−0
@@ -0,0 +1,51 @@
1+* Renesas R-Car generation 2 USB PHY
2+
3+This file provides information on what the device node for the R-Car generation
4+2 USB PHY contains.
5+
6+Required properties:
7+- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
8+ "renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
9+- reg: offset and length of the register block.
10+- #address-cells: number of address cells for the USB channel subnodes, must
11+ be <1>.
12+- #size-cells: number of size cells for the USB channel subnodes, must be <0>.
13+- clocks: clock phandle and specifier pair.
14+- clock-names: string, clock input name, must be "usbhs".
15+
16+The USB PHY device tree node should have the subnodes corresponding to the USB
17+channels. These subnodes must contain the following properties:
18+- reg: the USB controller selector; see the table below for the values.
19+- #phy-cells: see phy-bindings.txt in the same directory, must be <1>.
20+
21+The phandle's argument in the PHY specifier is the USB controller selector for
22+the USB channel; see the selector meanings below:
23+
24++-----------+---------------+---------------+
25+|\ Selector | | |
26++ --------- + 0 | 1 |
27+| Channel \| | |
28++-----------+---------------+---------------+
29+| 0 | PCI EHCI/OHCI | HS-USB |
30+| 2 | PCI EHCI/OHCI | xHCI |
31++-----------+---------------+---------------+
32+
33+Example (Lager board):
34+
35+ usb-phy@e6590100 {
36+ compatible = "renesas,usb-phy-r8a7790";
37+ reg = <0 0xe6590100 0 0x100>;
38+ #address-cells = <1>;
39+ #size-cells = <0>;
40+ clocks = <&mstp7_clks R8A7790_CLK_HSUSB>;
41+ clock-names = "usbhs";
42+
43+ usb-channel@0 {
44+ reg = <0>;
45+ #phy-cells = <1>;
46+ };
47+ usb-channel@2 {
48+ reg = <2>;
49+ #phy-cells = <1>;
50+ };
51+ };
Documentation/devicetree/bindings/phy/samsung-phy.txt+11−2
@@ -17,8 +17,11 @@ Samsung EXYNOS SoC series Display Port PHY · 16 unmodified lines
1717 -------------------------------------------------
1818
1919 Required properties:
20−- compatible : should be "samsung,exynos5250-dp-video-phy";
21−- reg : offset and length of the Display Port PHY register set;
20+- compatible : should be one of the following supported values:
21+ - "samsung,exynos5250-dp-video-phy"
22+ - "samsung,exynos5420-dp-video-phy"
23+- samsung,pmu-syscon: phandle for PMU system controller interface, used to
24+ control pmu registers for power isolation.
2225 - #phy-cells : from the generic PHY bindings, must be 0;
2326
2427 Samsung S5P/EXYNOS SoC series USB PHY
@@ -125,6 +128,7 @@ Required properties: · 100 unmodified lines
125128 - compatible : Should be set to one of the following supported values:
126129 - "samsung,exynos5250-usbdrd-phy" - for exynos5250 SoC,
127130 - "samsung,exynos5420-usbdrd-phy" - for exynos5420 SoC.
131+ - "samsung,exynos7-usbdrd-phy" - for exynos7 SoC.
128132 - reg : Register offset and length of USB DRD PHY register set;
129133 - clocks: Clock IDs array as required by the controller
130134 - clock-names: names of clocks correseponding to IDs in the clock property;
@@ -135,6 +139,11 @@ Required properties: · 4 unmodified lines
135139 PHY operations, associated by phy name. It is used to
136140 determine bit values for clock settings register.
137141 For Exynos5420 this is given as 'sclk_usbphy30' in CMU.
142+ - optional clocks: Exynos7 SoC has now following additional
143+ gate clocks available:
144+ - phy_pipe: for PIPE3 phy
145+ - phy_utmi: for UTMI+ phy
146+ - itp: for ITP generation
138147 - samsung,pmu-syscon: phandle for PMU system controller interface, used to
139148 control pmu registers for power isolation.
140149 - #phy-cells : from the generic PHY bindings, must be 1;
Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt+15−7
@@ -19,6 +19,7 @@ such as pull-up, multi drive, etc. · 18 unmodified lines
1919
2020 Required properties for iomux controller:
2121 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22+ or "atmel,sama5d3-pinctrl"
2223 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
2324 configured in this periph mode. All the periph and bank need to be describe.
2425
@@ -85,13 +86,20 @@ Required properties for pin configuration node: · 60 unmodified lines
8586 PIN_BANK 0 is pioA, PIN_BANK 1 is pioB...
8687
8788 Bits used for CONFIG:
88−PULL_UP (1 << 0): indicate this pin need a pull up.
89−MULTIDRIVE (1 << 1): indicate this pin need to be configured as multidrive.
90−DEGLITCH (1 << 2): indicate this pin need deglitch.
91−PULL_DOWN (1 << 3): indicate this pin need a pull down.
92−DIS_SCHMIT (1 << 4): indicate this pin need to disable schmit trigger.
93−DEBOUNCE (1 << 16): indicate this pin need debounce.
94−DEBOUNCE_VAL (0x3fff << 17): debounce val.
89+PULL_UP (1 << 0): indicate this pin needs a pull up.
90+MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
91+ Multi-drive is equivalent to open-drain type output.
92+DEGLITCH (1 << 2): indicate this pin needs deglitch.
93+PULL_DOWN (1 << 3): indicate this pin needs a pull down.
94+DIS_SCHMIT (1 << 4): indicate this pin needs to the disable schmitt trigger.
95+DRIVE_STRENGTH (3 << 5): indicate the drive strength of the pin using the
96+ following values:
97+ 00 - No change (reset state value kept)
98+ 01 - Low
99+ 10 - Medium
100+ 11 - High
101+DEBOUNCE (1 << 16): indicate this pin needs debounce.
102+DEBOUNCE_VAL (0x3fff << 17): debounce value.
95103
96104 NOTE:
97105 Some requirements for using atmel,at91rm9200-pinctrl binding:
Documentation/devicetree/bindings/pinctrl/img,tz1090-pdc-pinctrl.txt+1−1
@@ -9,7 +9,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 8 unmodified lines
99 common pinctrl bindings used by client devices, including the meaning of the
1010 phrase "pin configuration node".
1111
12−TZ1090-PDC's pin configuration nodes act as a container for an abitrary number
12+TZ1090-PDC's pin configuration nodes act as a container for an arbitrary number
1313 of subnodes. Each of these subnodes represents some desired configuration for a
1414 pin, a group, or a list of pins or groups. This configuration can include the
1515 mux function to select on those pin(s)/group(s), and various pin configuration
Documentation/devicetree/bindings/pinctrl/img,tz1090-pinctrl.txt+2−2
@@ -9,7 +9,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 8 unmodified lines
99 common pinctrl bindings used by client devices, including the meaning of the
1010 phrase "pin configuration node".
1111
12−TZ1090's pin configuration nodes act as a container for an abitrary number of
12+TZ1090's pin configuration nodes act as a container for an arbitrary number of
1313 subnodes. Each of these subnodes represents some desired configuration for a
1414 pin, a group, or a list of pins or groups. This configuration can include the
1515 mux function to select on those pin(s)/group(s), and various pin configuration
@@ -67,7 +67,7 @@ Valid values for pin and group names are: · 51 unmodified lines
6767 They also all support the some form of muxing. Any pins which are contained
6868 in one of the mux groups (see below) can be muxed only to the functions
6969 supported by the mux group. All other pins can be muxed to the "perip"
70− function which which enables them with their intended peripheral.
70+ function which enables them with their intended peripheral.
7171
7272 Different pins in the same mux group cannot be muxed to different functions,
7373 however it is possible to mux only a subset of the pins in a mux group to a
Documentation/devicetree/bindings/pinctrl/lantiq,falcon-pinumx.txt+1−1
@@ -9,7 +9,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 8 unmodified lines
99 common pinctrl bindings used by client devices, including the meaning of the
1010 phrase "pin configuration node".
1111
12−Lantiq's pin configuration nodes act as a container for an abitrary number of
12+Lantiq's pin configuration nodes act as a container for an arbitrary number of
1313 subnodes. Each of these subnodes represents some desired configuration for a
1414 pin, a group, or a list of pins or groups. This configuration can include the
1515 mux function to select on those group(s), and two pin configuration parameters:
Documentation/devicetree/bindings/pinctrl/lantiq,xway-pinumx.txt+1−1
@@ -9,7 +9,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 8 unmodified lines
99 common pinctrl bindings used by client devices, including the meaning of the
1010 phrase "pin configuration node".
1111
12−Lantiq's pin configuration nodes act as a container for an abitrary number of
12+Lantiq's pin configuration nodes act as a container for an arbitrary number of
1313 subnodes. Each of these subnodes represents some desired configuration for a
1414 pin, a group, or a list of pins or groups. This configuration can include the
1515 mux function to select on those group(s), and two pin configuration parameters:
Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt+96−0
@@ -0,0 +1,96 @@
1+== Amlogic Meson pinmux controller ==
2+
3+Required properties for the root node:
4+ - compatible: "amlogic,meson8-pinctrl"
5+ - reg: address and size of registers controlling irq functionality
6+
7+=== GPIO sub-nodes ===
8+
9+The 2 power domains of the controller (regular and always-on) are
10+represented as sub-nodes and each of them acts as a GPIO controller.
11+
12+Required properties for sub-nodes are:
13+ - reg: should contain address and size for mux, pull-enable, pull and
14+ gpio register sets
15+ - reg-names: an array of strings describing the "reg" entries. Must
16+ contain "mux", "pull" and "gpio". "pull-enable" is optional and
17+ when it is missing the "pull" registers are used instead
18+ - gpio-controller: identifies the node as a gpio controller
19+ - #gpio-cells: must be 2
20+
21+Valid sub-node names are:
22+ - "banks" for the regular domain
23+ - "ao-bank" for the always-on domain
24+
25+=== Other sub-nodes ===
26+
27+Child nodes without the "gpio-controller" represent some desired
28+configuration for a pin or a group. Those nodes can be pinmux nodes or
29+configuration nodes.
30+
31+Required properties for pinmux nodes are:
32+ - groups: a list of pinmux groups. The list of all available groups
33+ depends on the SoC and can be found in driver sources.
34+ - function: the name of a function to activate for the specified set
35+ of groups. The list of all available functions depends on the SoC
36+ and can be found in driver sources.
37+
38+Required properties for configuration nodes:
39+ - pins: a list of pin names
40+
41+Configuration nodes support the generic properties "bias-disable",
42+"bias-pull-up" and "bias-pull-down", described in file
43+pinctrl-bindings.txt
44+
45+=== Example ===
46+
47+ pinctrl: pinctrl@c1109880 {
48+ compatible = "amlogic,meson8-pinctrl";
49+ reg = <0xc1109880 0x10>;
50+ #address-cells = <1>;
51+ #size-cells = <1>;
52+ ranges;
53+
54+ gpio: banks@c11080b0 {
55+ reg = <0xc11080b0 0x28>,
56+ <0xc11080e8 0x18>,
57+ <0xc1108120 0x18>,
58+ <0xc1108030 0x30>;
59+ reg-names = "mux", "pull", "pull-enable", "gpio";
60+ gpio-controller;
61+ #gpio-cells = <2>;
62+ };
63+
64+ gpio_ao: ao-bank@c1108030 {
65+ reg = <0xc8100014 0x4>,
66+ <0xc810002c 0x4>,
67+ <0xc8100024 0x8>;
68+ reg-names = "mux", "pull", "gpio";
69+ gpio-controller;
70+ #gpio-cells = <2>;
71+ };
72+
73+ nand {
74+ mux {
75+ groups = "nand_io", "nand_io_ce0", "nand_io_ce1",
76+ "nand_io_rb0", "nand_ale", "nand_cle",
77+ "nand_wen_clk", "nand_ren_clk", "nand_dqs",
78+ "nand_ce2", "nand_ce3";
79+ function = "nand";
80+ };
81+ };
82+
83+ uart_ao_a {
84+ mux {
85+ groups = "uart_tx_ao_a", "uart_rx_ao_a",
86+ "uart_cts_ao_a", "uart_rts_ao_a";
87+ function = "uart_ao";
88+ };
89+
90+ conf {
91+ pins = "GPIOAO_0", "GPIOAO_1",
92+ "GPIOAO_2", "GPIOAO_3";
93+ bias-disable;
94+ };
95+ };
96+ };
Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-pinmux.txt+11−3
@@ -10,6 +10,7 @@ Required properties: · 9 unmodified lines
1010 - reg: Should contain a list of base address and size pairs for:
1111 -- first entry - the drive strength and pad control registers.
1212 -- second entry - the pinmux registers
13+ -- third entry - the MIPI_PAD_CTRL register
1314
1415 Tegra124 adds the following optional properties for pin configuration subnodes.
1516 The macros for options are defined in the
@@ -91,6 +92,12 @@ Valid values for pin and group names are: · 75 unmodified lines
9192 dbg, sdio3, spi, uaa, uab, uart2, uart3, sdio1, ddc, gma, gme, gmf, gmg,
9293 gmh, owr, uda, gpv, dev3, cec, usb_vbus_en, ao3, ao0, hv0, sdio4, ao4.
9394
95+ MIPI pad control groups:
96+
97+ These support only the nvidia,function property.
98+
99+ dsi_b
100+
94101 Valid values for nvidia,functions are:
95102
96103 blink, cec, cldvfs, clk12, cpu, dap, dap1, dap2, dev3, displaya,
@@ -101,14 +108,15 @@ Valid values for nvidia,functions are: · 4 unmodified lines
101108 sdmmc4, soc, spdif, spi1, spi2, spi3, spi4, spi5, spi6, trace, uarta,
102109 uartb, uartc, uartd, ulpi, usb, vgp1, vgp2, vgp3, vgp4, vgp5, vgp6,
103110 vi, vi_alt1, vi_alt3, vimclk2, vimclk2_alt, sata, ccla, pe0, pe, pe1,
104− dp, rtck, sys, clk tmds.
111+ dp, rtck, sys, clk tmds, csi, dsi_b
105112
106113 Example:
107114
108115 pinmux: pinmux {
109116 compatible = "nvidia,tegra124-pinmux";
110− reg = <0x70000868 0x164 /* Pad control registers */
111− 0x70003000 0x434>; /* PinMux registers */
117+ reg = <0x0 0x70000868 0x0 0x164>, /* Pad control registers */
118+ <0x0 0x70003000 0x0 0x434>, /* Mux registers */
119+ <0x0 0x70000820 0x0 0x8>; /* MIPI pad control */
112120 };
113121
114122 Example pinmux entries:
Documentation/devicetree/bindings/pinctrl/nvidia,tegra20-pinmux.txt+1−1
@@ -9,7 +9,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 8 unmodified lines
99 common pinctrl bindings used by client devices, including the meaning of the
1010 phrase "pin configuration node".
1111
12−Tegra's pin configuration nodes act as a container for an abitrary number of
12+Tegra's pin configuration nodes act as a container for an arbitrary number of
1313 subnodes. Each of these subnodes represents some desired configuration for a
1414 pin, a group, or a list of pins or groups. This configuration can include the
1515 mux function to select on those pin(s)/group(s), and various pin configuration
Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt+40−12
@@ -127,6 +127,24 @@ whether there is any interaction between the child and intermediate parent · 126 unmodified lines
127127 nodes, is again defined entirely by the binding for the individual pin
128128 controller device.
129129
130+== Generic pin multiplexing node content ==
131+
132+pin multiplexing nodes:
133+
134+function - the mux function to select
135+groups - the list of groups to select with this function
136+
137+Example:
138+
139+state_0_node_a {
140+ function = "uart0";
141+ groups = "u0rxtx", "u0rtscts";
142+};
143+state_1_node_a {
144+ function = "spi0";
145+ groups = "spi0pins";
146+};
147+
130148 == Generic pin configuration node content ==
131149
132150 Many data items that are represented in a pin configuration node are common
@@ -139,8 +157,12 @@ structure of the DT nodes that contain these properties. · 6 unmodified lines
139157 Supported generic properties are:
140158
141159 pins - the list of pins that properties in the node
142− apply to
143−function - the mux function to select
160+ apply to (either this or "group" has to be
161+ specified)
162+group - the group to apply the properties to, if the driver
163+ supports configuration of whole groups rather than
164+ individual pins (either this or "pins" has to be
165+ specified)
144166 bias-disable - disable any pin bias
145167 bias-high-impedance - high impedance mode ("third-state", "floating")
146168 bias-bus-hold - latch weakly
@@ -163,6 +185,21 @@ output-low - set the pin to output mode with low level · 16 unmodified lines
163185 output-high - set the pin to output mode with high level
164186 slew-rate - set the slew rate
165187
188+For example:
189+
190+state_0_node_a {
191+ pins = "GPIO0_AJ5", "GPIO2_AH4"; /* CTS+RXD */
192+ bias-pull-up;
193+};
194+state_1_node_a {
195+ pins = "GPIO1_AJ3", "GPIO3_AH3"; /* RTS+TXD */
196+ output-high;
197+};
198+state_2_node_a {
199+ group = "foo-group";
200+ bias-pull-up;
201+};
202+
166203 Some of the generic properties take arguments. For those that do, the
167204 arguments are described below.
168205
@@ -170,15 +207,6 @@ arguments are described below. · 1 unmodified line
170207 binding for the hardware defines:
171208 - Whether the entries are integers or strings, and their meaning.
172209
173−- function takes a list of function names/IDs as a required argument. The
174− specific binding for the hardware defines:
175− - Whether the entries are integers or strings, and their meaning.
176− - Whether only a single entry is allowed (which is applied to all entries
177− in the pins property), or whether there may alternatively be one entry per
178− entry in the pins property, in which case the list lengths must match, and
179− for each list index i, the function at list index i is applied to the pin
180− at list index i.
181−
182210 - bias-pull-up, -down and -pin-default take as optional argument on hardware
183211 supporting it the pull strength in Ohm. bias-disable will disable the pull.
184212
@@ -188,4 +216,4 @@ arguments are described below. · 3 unmodified lines
188216 or 0 to disable debouncing
189217
190218 More in-depth documentation on these parameters can be found in
191−<include/linux/pinctrl/pinconfig-generic.h>
219+<include/linux/pinctrl/pinconf-generic.h>
Documentation/devicetree/bindings/pinctrl/pinctrl-sirf.txt+1−1
@@ -13,7 +13,7 @@ Optional properties: · 12 unmodified lines
1313 Please refer to pinctrl-bindings.txt in this directory for details of the common
1414 pinctrl bindings used by client devices.
1515
16−SiRFprimaII's pinmux nodes act as a container for an abitrary number of subnodes.
16+SiRFprimaII's pinmux nodes act as a container for an arbitrary number of subnodes.
1717 Each of these subnodes represents some desired configuration for a group of pins.
1818
1919 Required subnode-properties:
Documentation/devicetree/bindings/pinctrl/pinctrl_spear.txt+1−1
@@ -32,7 +32,7 @@ Required properties: · 31 unmodified lines
3232 Please refer to pinctrl-bindings.txt in this directory for details of the common
3333 pinctrl bindings used by client devices.
3434
35−SPEAr's pinmux nodes act as a container for an abitrary number of subnodes. Each
35+SPEAr's pinmux nodes act as a container for an arbitrary number of subnodes. Each
3636 of these subnodes represents muxing for a pin, a group, or a list of pins or
3737 groups.
3838
Documentation/devicetree/bindings/pinctrl/qcom,apq8064-pinctrl.txt+2−2
@@ -18,7 +18,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 17 unmodified lines
1818 common pinctrl bindings used by client devices, including the meaning of the
1919 phrase "pin configuration node".
2020
21−Qualcomm's pin configuration nodes act as a container for an abitrary number of
21+Qualcomm's pin configuration nodes act as a container for an arbitrary number of
2222 subnodes. Each of these subnodes represents some desired configuration for a
2323 pin, a group, or a list of pins or groups. This configuration can include the
2424 mux function to select on those pin(s)/group(s), and various pin configuration
@@ -50,7 +50,7 @@ Valid values for function are: · 25 unmodified lines
5050 gsbi4_cam_i2c, gsbi5, gsbi5_spi_cs1, gsbi5_spi_cs2, gsbi5_spi_cs3, gsbi6,
5151 gsbi6_spi_cs1, gsbi6_spi_cs2, gsbi6_spi_cs3, gsbi7, gsbi7_spi_cs1,
5252 gsbi7_spi_cs2, gsbi7_spi_cs3, gsbi_cam_i2c, hdmi, mi2s, riva_bt, riva_fm,
53− riva_wlan, sdc2, sdc4, slimbus, spkr_i2s, tsif1, tsif2, usb2_hsic,
53+ riva_wlan, sdc2, sdc4, slimbus, spkr_i2s, tsif1, tsif2, usb2_hsic, ps_hold
5454
5555 Example:
5656
Documentation/devicetree/bindings/pinctrl/qcom,apq8084-pinctrl.txt+179−0
@@ -0,0 +1,179 @@
1+Qualcomm APQ8084 TLMM block
2+
3+This binding describes the Top Level Mode Multiplexer block found in the
4+MSM8960 platform.
5+
6+- compatible:
7+ Usage: required
8+ Value type: <string>
9+ Definition: must be "qcom,apq8084-pinctrl"
10+
11+- reg:
12+ Usage: required
13+ Value type: <prop-encoded-array>
14+ Definition: the base address and size of the TLMM register space.
15+
16+- interrupts:
17+ Usage: required
18+ Value type: <prop-encoded-array>
19+ Definition: should specify the TLMM summary IRQ.
20+
21+- interrupt-controller:
22+ Usage: required
23+ Value type: <none>
24+ Definition: identifies this node as an interrupt controller
25+
26+- #interrupt-cells:
27+ Usage: required
28+ Value type: <u32>
29+ Definition: must be 2. Specifying the pin number and flags, as defined
30+ in <dt-bindings/interrupt-controller/irq.h>
31+
32+- gpio-controller:
33+ Usage: required
34+ Value type: <none>
35+ Definition: identifies this node as a gpio controller
36+
37+- #gpio-cells:
38+ Usage: required
39+ Value type: <u32>
40+ Definition: must be 2. Specifying the pin number and flags, as defined
41+ in <dt-bindings/gpio/gpio.h>
42+
43+Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
44+a general description of GPIO and interrupt bindings.
45+
46+Please refer to pinctrl-bindings.txt in this directory for details of the
47+common pinctrl bindings used by client devices, including the meaning of the
48+phrase "pin configuration node".
49+
50+The pin configuration nodes act as a container for an arbitrary number of
51+subnodes. Each of these subnodes represents some desired configuration for a
52+pin, a group, or a list of pins or groups. This configuration can include the
53+mux function to select on those pin(s)/group(s), and various pin configuration
54+parameters, such as pull-up, drive strength, etc.
55+
56+
57+PIN CONFIGURATION NODES:
58+
59+The name of each subnode is not important; all subnodes should be enumerated
60+and processed purely based on their content.
61+
62+Each subnode only affects those parameters that are explicitly listed. In
63+other words, a subnode that lists a mux function but no pin configuration
64+parameters implies no information about any pin configuration parameters.
65+Similarly, a pin subnode that describes a pullup parameter implies no
66+information about e.g. the mux function.
67+
68+
69+The following generic properties as defined in pinctrl-bindings.txt are valid
70+to specify in a pin configuration subnode:
71+
72+- pins:
73+ Usage: required
74+ Value type: <string-array>
75+ Definition: List of gpio pins affected by the properties specified in
76+ this subnode. Valid pins are:
77+ gpio0-gpio146,
78+ sdc1_clk,
79+ sdc1_cmd,
80+ sdc1_data
81+ sdc2_clk,
82+ sdc2_cmd,
83+ sdc2_data
84+
85+- function:
86+ Usage: required
87+ Value type: <string>
88+ Definition: Specify the alternative function to be configured for the
89+ specified pins. Functions are only valid for gpio pins.
90+ Valid values are:
91+ adsp_ext, audio_ref, blsp_i2c1, blsp_i2c2, blsp_i2c3,
92+ blsp_i2c4, blsp_i2c5, blsp_i2c6, blsp_i2c7, blsp_i2c8,
93+ blsp_i2c9, blsp_i2c10, blsp_i2c11, blsp_i2c12,
94+ blsp_spi1, blsp_spi2, blsp_spi3, blsp_spi4, blsp_spi5,
95+ blsp_spi6, blsp_spi7, blsp_spi8, blsp_spi9, blsp_spi10,
96+ blsp_spi11, blsp_spi12, blsp_uart1, blsp_uart2, blsp_uart3,
97+ blsp_uart4, blsp_uart5, blsp_uart6, blsp_uart7, blsp_uart8,
98+ blsp_uart9, blsp_uart10, blsp_uart11, blsp_uart12,
99+ blsp_uim1, blsp_uim2, blsp_uim3, blsp_uim4, blsp_uim5,
100+ blsp_uim6, blsp_uim7, blsp_uim8, blsp_uim9, blsp_uim10,
101+ blsp_uim11, blsp_uim12, cam_mclk0, cam_mclk1, cam_mclk2,
102+ cam_mclk3, cci_async, cci_async_in0, cci_i2c0, cci_i2c1,
103+ cci_timer0, cci_timer1, cci_timer2, cci_timer3, cci_timer4,
104+ edp_hpd, gcc_gp1, gcc_gp2, gcc_gp3, gcc_obt, gcc_vtt,i
105+ gp_mn, gp_pdm0, gp_pdm1, gp_pdm2, gp0_clk, gp1_clk, gpio,
106+ hdmi_cec, hdmi_ddc, hdmi_dtest, hdmi_hpd, hdmi_rcv, hsic,
107+ ldo_en, ldo_update, mdp_vsync, pci_e0, pci_e0_n, pci_e0_rst,
108+ pci_e1, pci_e1_rst, pci_e1_rst_n, pci_e1_clkreq_n, pri_mi2s,
109+ qua_mi2s, sata_act, sata_devsleep, sata_devsleep_n,
110+ sd_write, sdc_emmc_mode, sdc3, sdc4, sec_mi2s, slimbus,
111+ spdif_tx, spkr_i2s, spkr_i2s_ws, spss_geni, ter_mi2s, tsif1,
112+ tsif2, uim, uim_batt_alarm
113+
114+- bias-disable:
115+ Usage: optional
116+ Value type: <none>
117+ Definition: The specified pins should be configued as no pull.
118+
119+- bias-pull-down:
120+ Usage: optional
121+ Value type: <none>
122+ Definition: The specified pins should be configued as pull down.
123+
124+- bias-pull-up:
125+ Usage: optional
126+ Value type: <none>
127+ Definition: The specified pins should be configued as pull up.
128+
129+- output-high:
130+ Usage: optional
131+ Value type: <none>
132+ Definition: The specified pins are configured in output mode, driven
133+ high.
134+ Not valid for sdc pins.
135+
136+- output-low:
137+ Usage: optional
138+ Value type: <none>
139+ Definition: The specified pins are configured in output mode, driven
140+ low.
141+ Not valid for sdc pins.
142+
143+- drive-strength:
144+ Usage: optional
145+ Value type: <u32>
146+ Definition: Selects the drive strength for the specified pins, in mA.
147+ Valid values are: 2, 4, 6, 8, 10, 12, 14 and 16
148+
149+Example:
150+
151+ tlmm: pinctrl@fd510000 {
152+ compatible = "qcom,apq8084-pinctrl";
153+ reg = <0xfd510000 0x4000>;
154+
155+ gpio-controller;
156+ #gpio-cells = <2>;
157+ interrupt-controller;
158+ #interrupt-cells = <2>;
159+ interrupts = <0 208 0>;
160+
161+ uart2: uart2-default {
162+ mux {
163+ pins = "gpio4", "gpio5";
164+ function = "blsp_uart2";
165+ };
166+
167+ tx {
168+ pins = "gpio4";
169+ drive-strength = <4>;
170+ bias-disable;
171+ };
172+
173+ rx {
174+ pins = "gpio5";
175+ drive-strength = <2>;
176+ bias-pull-up;
177+ };
178+ };
179+ };
Documentation/devicetree/bindings/pinctrl/qcom,ipq8064-pinctrl.txt+1−1
@@ -18,7 +18,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 17 unmodified lines
1818 common pinctrl bindings used by client devices, including the meaning of the
1919 phrase "pin configuration node".
2020
21−Qualcomm's pin configuration nodes act as a container for an abitrary number of
21+Qualcomm's pin configuration nodes act as a container for an arbitrary number of
2222 subnodes. Each of these subnodes represents some desired configuration for a
2323 pin, a group, or a list of pins or groups. This configuration can include the
2424 mux function to select on those pin(s)/group(s), and various pin configuration
Documentation/devicetree/bindings/pinctrl/qcom,msm8960-pinctrl.txt+1−1
@@ -47,7 +47,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 46 unmodified lines
4747 common pinctrl bindings used by client devices, including the meaning of the
4848 phrase "pin configuration node".
4949
50−The pin configuration nodes act as a container for an abitrary number of
50+The pin configuration nodes act as a container for an arbitrary number of
5151 subnodes. Each of these subnodes represents some desired configuration for a
5252 pin, a group, or a list of pins or groups. This configuration can include the
5353 mux function to select on those pin(s)/group(s), and various pin configuration
Documentation/devicetree/bindings/pinctrl/qcom,msm8974-pinctrl.txt+1−1
@@ -18,7 +18,7 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 17 unmodified lines
1818 common pinctrl bindings used by client devices, including the meaning of the
1919 phrase "pin configuration node".
2020
21−Qualcomm's pin configuration nodes act as a container for an abitrary number of
21+Qualcomm's pin configuration nodes act as a container for an arbitrary number of
2222 subnodes. Each of these subnodes represents some desired configuration for a
2323 pin, a group, or a list of pins or groups. This configuration can include the
2424 mux function to select on those pin(s)/group(s), and various pin configuration
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt+215−0
@@ -0,0 +1,215 @@
1+Qualcomm PMIC GPIO block
2+
3+This binding describes the GPIO block(s) found in the 8xxx series of
4+PMIC's from Qualcomm.
5+
6+- compatible:
7+ Usage: required
8+ Value type: <string>
9+ Definition: must be one of:
10+ "qcom,pm8018-gpio"
11+ "qcom,pm8038-gpio"
12+ "qcom,pm8058-gpio"
13+ "qcom,pm8917-gpio"
14+ "qcom,pm8921-gpio"
15+ "qcom,pm8941-gpio"
16+ "qcom,pma8084-gpio"
17+
18+- reg:
19+ Usage: required
20+ Value type: <prop-encoded-array>
21+ Definition: Register base of the GPIO block and length.
22+
23+- interrupts:
24+ Usage: required
25+ Value type: <prop-encoded-array>
26+ Definition: Must contain an array of encoded interrupt specifiers for
27+ each available GPIO
28+
29+- gpio-controller:
30+ Usage: required
31+ Value type: <none>
32+ Definition: Mark the device node as a GPIO controller
33+
34+- #gpio-cells:
35+ Usage: required
36+ Value type: <u32>
37+ Definition: Must be 2;
38+ the first cell will be used to define gpio number and the
39+ second denotes the flags for this gpio
40+
41+Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
42+a general description of GPIO and interrupt bindings.
43+
44+Please refer to pinctrl-bindings.txt in this directory for details of the
45+common pinctrl bindings used by client devices, including the meaning of the
46+phrase "pin configuration node".
47+
48+The pin configuration nodes act as a container for an arbitrary number of
49+subnodes. Each of these subnodes represents some desired configuration for a
50+pin or a list of pins. This configuration can include the
51+mux function to select on those pin(s), and various pin configuration
52+parameters, as listed below.
53+
54+
55+SUBNODES:
56+
57+The name of each subnode is not important; all subnodes should be enumerated
58+and processed purely based on their content.
59+
60+Each subnode only affects those parameters that are explicitly listed. In
61+other words, a subnode that lists a mux function but no pin configuration
62+parameters implies no information about any pin configuration parameters.
63+Similarly, a pin subnode that describes a pullup parameter implies no
64+information about e.g. the mux function.
65+
66+The following generic properties as defined in pinctrl-bindings.txt are valid
67+to specify in a pin configuration subnode:
68+
69+- pins:
70+ Usage: required
71+ Value type: <string-array>
72+ Definition: List of gpio pins affected by the properties specified in
73+ this subnode. Valid pins are:
74+ gpio1-gpio6 for pm8018
75+ gpio1-gpio12 for pm8038
76+ gpio1-gpio40 for pm8058
77+ gpio1-gpio38 for pm8917
78+ gpio1-gpio44 for pm8921
79+ gpio1-gpio36 for pm8941
80+ gpio1-gpio22 for pma8084
81+
82+- function:
83+ Usage: required
84+ Value type: <string>
85+ Definition: Specify the alternative function to be configured for the
86+ specified pins. Valid values are:
87+ "normal",
88+ "paired",
89+ "func1",
90+ "func2",
91+ "dtest1",
92+ "dtest2",
93+ "dtest3",
94+ "dtest4"
95+
96+- bias-disable:
97+ Usage: optional
98+ Value type: <none>
99+ Definition: The specified pins should be configured as no pull.
100+
101+- bias-pull-down:
102+ Usage: optional
103+ Value type: <none>
104+ Definition: The specified pins should be configured as pull down.
105+
106+- bias-pull-up:
107+ Usage: optional
108+ Value type: <empty>
109+ Definition: The specified pins should be configured as pull up.
110+
111+- qcom,pull-up-strength:
112+ Usage: optional
113+ Value type: <u32>
114+ Definition: Specifies the strength to use for pull up, if selected.
115+ Valid values are; as defined in
116+ <dt-bindings/pinctrl/qcom,pmic-gpio.h>:
117+ 1: 30uA (PMIC_GPIO_PULL_UP_30)
118+ 2: 1.5uA (PMIC_GPIO_PULL_UP_1P5)
119+ 3: 31.5uA (PMIC_GPIO_PULL_UP_31P5)
120+ 4: 1.5uA + 30uA boost (PMIC_GPIO_PULL_UP_1P5_30)
121+ If this property is ommited 30uA strength will be used if
122+ pull up is selected
123+
124+- bias-high-impedance:
125+ Usage: optional
126+ Value type: <none>
127+ Definition: The specified pins will put in high-Z mode and disabled.
128+
129+- input-enable:
130+ Usage: optional
131+ Value type: <none>
132+ Definition: The specified pins are put in input mode.
133+
134+- output-high:
135+ Usage: optional
136+ Value type: <none>
137+ Definition: The specified pins are configured in output mode, driven
138+ high.
139+
140+- output-low:
141+ Usage: optional
142+ Value type: <none>
143+ Definition: The specified pins are configured in output mode, driven
144+ low.
145+
146+- power-source:
147+ Usage: optional
148+ Value type: <u32>
149+ Definition: Selects the power source for the specified pins. Valid
150+ power sources are defined per chip in
151+ <dt-bindings/pinctrl/qcom,pmic-gpio.h>
152+
153+- qcom,drive-strength:
154+ Usage: optional
155+ Value type: <u32>
156+ Definition: Selects the drive strength for the specified pins. Value
157+ drive strengths are:
158+ 0: no (PMIC_GPIO_STRENGTH_NO)
159+ 1: high (PMIC_GPIO_STRENGTH_HIGH) 0.9mA @ 1.8V - 1.9mA @ 2.6V
160+ 2: medium (PMIC_GPIO_STRENGTH_MED) 0.6mA @ 1.8V - 1.25mA @ 2.6V
161+ 3: low (PMIC_GPIO_STRENGTH_LOW) 0.15mA @ 1.8V - 0.3mA @ 2.6V
162+ as defined in <dt-bindings/pinctrl/qcom,pmic-gpio.h>
163+
164+- drive-push-pull:
165+ Usage: optional
166+ Value type: <none>
167+ Definition: The specified pins are configured in push-pull mode.
168+
169+- drive-open-drain:
170+ Usage: optional
171+ Value type: <none>
172+ Definition: The specified pins are configured in open-drain mode.
173+
174+- drive-open-source:
175+ Usage: optional
176+ Value type: <none>
177+ Definition: The specified pins are configured in open-source mode.
178+
179+Example:
180+
181+ pm8921_gpio: gpio@150 {
182+ compatible = "qcom,pm8921-gpio";
183+ reg = <0x150 0x160>;
184+ interrupts = <192 1>, <193 1>, <194 1>,
185+ <195 1>, <196 1>, <197 1>,
186+ <198 1>, <199 1>, <200 1>,
187+ <201 1>, <202 1>, <203 1>,
188+ <204 1>, <205 1>, <206 1>,
189+ <207 1>, <208 1>, <209 1>,
190+ <210 1>, <211 1>, <212 1>,
191+ <213 1>, <214 1>, <215 1>,
192+ <216 1>, <217 1>, <218 1>,
193+ <219 1>, <220 1>, <221 1>,
194+ <222 1>, <223 1>, <224 1>,
195+ <225 1>, <226 1>, <227 1>,
196+ <228 1>, <229 1>, <230 1>,
197+ <231 1>, <232 1>, <233 1>,
198+ <234 1>, <235 1>;
199+
200+ gpio-controller;
201+ #gpio-cells = <2>;
202+
203+ pm8921_gpio_keys: gpio-keys {
204+ volume-keys {
205+ pins = "gpio20", "gpio21";
206+ function = "normal";
207+
208+ input-enable;
209+ bias-pull-up;
210+ drive-push-pull;
211+ qcom,drive-strength = <PMIC_GPIO_STRENGTH_NO>;
212+ power-source = <PM8921_GPIO_S4>;
213+ };
214+ };
215+ };
Documentation/devicetree/bindings/pinctrl/qcom,pmic-mpp.txt+162−0
@@ -0,0 +1,162 @@
1+Qualcomm PMIC Multi-Purpose Pin (MPP) block
2+
3+This binding describes the MPP block(s) found in the 8xxx series
4+of PMIC's from Qualcomm.
5+
6+- compatible:
7+ Usage: required
8+ Value type: <string>
9+ Definition: Should contain one of:
10+ "qcom,pm8841-mpp",
11+ "qcom,pm8941-mpp",
12+ "qcom,pma8084-mpp",
13+
14+- reg:
15+ Usage: required
16+ Value type: <prop-encoded-array>
17+ Definition: Register base of the MPP block and length.
18+
19+- interrupts:
20+ Usage: required
21+ Value type: <prop-encoded-array>
22+ Definition: Must contain an array of encoded interrupt specifiers for
23+ each available MPP
24+
25+- gpio-controller:
26+ Usage: required
27+ Value type: <none>
28+ Definition: Mark the device node as a GPIO controller
29+
30+- #gpio-cells:
31+ Usage: required
32+ Value type: <u32>
33+ Definition: Must be 2;
34+ the first cell will be used to define MPP number and the
35+ second denotes the flags for this MPP
36+
37+Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
38+a general description of GPIO and interrupt bindings.
39+
40+Please refer to pinctrl-bindings.txt in this directory for details of the
41+common pinctrl bindings used by client devices, including the meaning of the
42+phrase "pin configuration node".
43+
44+The pin configuration nodes act as a container for an arbitrary number of
45+subnodes. Each of these subnodes represents some desired configuration for a
46+pin or a list of pins. This configuration can include the
47+mux function to select on those pin(s), and various pin configuration
48+parameters, as listed below.
49+
50+SUBNODES:
51+
52+The name of each subnode is not important; all subnodes should be enumerated
53+and processed purely based on their content.
54+
55+Each subnode only affects those parameters that are explicitly listed. In
56+other words, a subnode that lists a mux function but no pin configuration
57+parameters implies no information about any pin configuration parameters.
58+Similarly, a pin subnode that describes a pullup parameter implies no
59+information about e.g. the mux function.
60+
61+The following generic properties as defined in pinctrl-bindings.txt are valid
62+to specify in a pin configuration subnode:
63+
64+- pins:
65+ Usage: required
66+ Value type: <string-array>
67+ Definition: List of MPP pins affected by the properties specified in
68+ this subnode. Valid pins are:
69+ mpp1-mpp4 for pm8841
70+ mpp1-mpp8 for pm8941
71+ mpp1-mpp4 for pma8084
72+
73+- function:
74+ Usage: required
75+ Value type: <string>
76+ Definition: Specify the alternative function to be configured for the
77+ specified pins. Valid values are:
78+ "normal",
79+ "paired",
80+ "dtest1",
81+ "dtest2",
82+ "dtest3",
83+ "dtest4"
84+
85+- bias-disable:
86+ Usage: optional
87+ Value type: <none>
88+ Definition: The specified pins should be configured as no pull.
89+
90+- bias-pull-up:
91+ Usage: optional
92+ Value type: <u32>
93+ Definition: The specified pins should be configured as pull up.
94+ Valid values are 600, 10000 and 30000 in bidirectional mode
95+ only, i.e. when operating in qcom,analog-mode and input and
96+ outputs are enabled. The hardware ignores the configuration
97+ when operating in other modes.
98+
99+- bias-high-impedance:
100+ Usage: optional
101+ Value type: <none>
102+ Definition: The specified pins will put in high-Z mode and disabled.
103+
104+- input-enable:
105+ Usage: optional
106+ Value type: <none>
107+ Definition: The specified pins are put in input mode, i.e. their input
108+ buffer is enabled
109+
110+- output-high:
111+ Usage: optional
112+ Value type: <none>
113+ Definition: The specified pins are configured in output mode, driven
114+ high.
115+
116+- output-low:
117+ Usage: optional
118+ Value type: <none>
119+ Definition: The specified pins are configured in output mode, driven
120+ low.
121+
122+- power-source:
123+ Usage: optional
124+ Value type: <u32>
125+ Definition: Selects the power source for the specified pins. Valid power
126+ sources are defined in <dt-bindings/pinctrl/qcom,pmic-mpp.h>
127+
128+- qcom,analog-mode:
129+ Usage: optional
130+ Value type: <none>
131+ Definition: Selects Analog mode of operation: combined with input-enable
132+ and/or output-high, output-low MPP could operate as
133+ Bidirectional Logic, Analog Input, Analog Output.
134+
135+- qcom,amux-route:
136+ Usage: optional
137+ Value type: <u32>
138+ Definition: Selects the source for analog input. Valid values are
139+ defined in <dt-bindings/pinctrl/qcom,pmic-mpp.h>
140+ PMIC_MPP_AMUX_ROUTE_CH5, PMIC_MPP_AMUX_ROUTE_CH6...
141+
142+Example:
143+
144+ mpps@a000 {
145+ compatible = "qcom,pm8841-mpp";
146+ reg = <0xa000>;
147+ gpio-controller;
148+ #gpio-cells = <2>;
149+ interrupts = <4 0xa0 0 0>, <4 0xa1 0 0>, <4 0xa2 0 0>, <4 0xa3 0 0>;
150+
151+ pinctrl-names = "default";
152+ pinctrl-0 = <&pm8841_default>;
153+
154+ pm8841_default: default {
155+ gpio {
156+ pins = "mpp1", "mpp2", "mpp3", "mpp4";
157+ function = "normal";
158+ input-enable;
159+ power-source = <PM8841_MPP_S3>;
160+ };
161+ };
162+ };
Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt+3−3
@@ -2,8 +2,8 @@ · 1 unmodified line
22
33 The Rockchip Pinmux Controller, enables the IC
44 to share one PAD to several functional blocks. The sharing is done by
5−multiplexing the PAD input/output signals. For each PAD there are up to
6−4 muxing options with option 0 being the use as a GPIO.
5+multiplexing the PAD input/output signals. For each PAD there are several
6+muxing options with option 0 being the use as a GPIO.
77
88 Please refer to pinctrl-bindings.txt in this directory for details of the
99 common pinctrl bindings used by client devices, including the meaning of the
@@ -58,7 +58,7 @@ Deprecated properties for gpio sub nodes: · 48 unmodified lines
5858 Required properties for pin configuration node:
5959 - rockchip,pins: 3 integers array, represents a group of pins mux and config
6060 setting. The format is rockchip,pins = <PIN_BANK PIN_BANK_IDX MUX &phandle>.
61− The MUX 0 means gpio and MUX 1 to 3 mean the specific device function.
61+ The MUX 0 means gpio and MUX 1 to N mean the specific device function.
6262 The phandle of a node containing the generic pinconfig options
6363 to use, as described in pinctrl-bindings.txt in this directory.
6464
Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt+3−0
@@ -18,6 +18,7 @@ Required Properties: · 17 unmodified lines
1818 - "samsung,exynos5250-pinctrl": for Exynos5250 compatible pin-controller.
1919 - "samsung,exynos5260-pinctrl": for Exynos5260 compatible pin-controller.
2020 - "samsung,exynos5420-pinctrl": for Exynos5420 compatible pin-controller.
21+ - "samsung,exynos7-pinctrl": for Exynos7 compatible pin-controller.
2122
2223 - reg: Base address of the pin controller hardware module and length of
2324 the address space it occupies.
@@ -136,6 +137,8 @@ B. External Wakeup Interrupts: For supporting external wakeup interrupts, a · 112 unmodified lines
136137 found on Samsung S3C64xx SoCs,
137138 - samsung,exynos4210-wakeup-eint: represents wakeup interrupt controller
138139 found on Samsung Exynos4210 and S5PC110/S5PV210 SoCs.
140+ - samsung,exynos7-wakeup-eint: represents wakeup interrupt controller
141+ found on Samsung Exynos7 SoC.
139142 - interrupt-parent: phandle of the interrupt parent to which the external
140143 wakeup interrupts are forwarded to.
141144 - interrupts: interrupt used by multiplexed wakeup interrupts.
Documentation/devicetree/bindings/pinctrl/ste,abx500.txt+75−109
@@ -8,42 +8,8 @@ Please refer to pinctrl-bindings.txt in this directory for details of the · 7 unmodified lines
88 common pinctrl bindings used by client devices, including the meaning of the
99 phrase "pin configuration node".
1010
11−ST Ericsson's pin configuration nodes act as a container for an arbitrary number of
12−subnodes. Each of these subnodes represents some desired configuration for a
13−pin, a group, or a list of pins or groups. This configuration can include the
14−mux function to select on those pin(s)/group(s), and various pin configuration
15−parameters, such as input, output, pull up, pull down...
16−
17−The name of each subnode is not important; all subnodes should be enumerated
18−and processed purely based on their content.
19−
20−Required subnode-properties:
21−- ste,pins : An array of strings. Each string contains the name of a pin or
22− group.
23−
24−Optional subnode-properties:
25−- ste,function: A string containing the name of the function to mux to the
26− pin or group.
27−
28−- generic pin configuration option to use. Example :
29−
30− default_cfg {
31− ste,pins = "GPIO1";
32− bias-disable;
33− };
34−
35−- ste,config: Handle of pin configuration node containing the generic
36− pinconfig options to use, as described in pinctrl-bindings.txt in
37− this directory. Example :
38−
39− pcfg_bias_disable: pcfg_bias_disable {
40− bias-disable;
41− };
42−
43− default_cfg {
44− ste,pins = "GPIO1";
45− ste.config = <&pcfg_bias_disable>;
46− };
11+ST Ericsson's pin configuration nodes use the generic pin multiplexing
12+and pin configuration bindings, see pinctrl-bindings.txt
4713
4814 Example board file extract:
4915
@@ -54,11 +20,11 @@ Example board file extract: · 4 unmodified lines
5420 sysclkreq2 {
5521 sysclkreq2_default_mode: sysclkreq2_default {
5622 default_mux {
57− ste,function = "sysclkreq";
58− ste,pins = "sysclkreq2_d_1";
23+ function = "sysclkreq";
24+ groups = "sysclkreq2_d_1";
5925 };
6026 default_cfg {
61− ste,pins = "GPIO1";
27+ pins = "GPIO1";
6228 bias-disable;
6329 };
6430 };
@@ -66,11 +32,11 @@ Example board file extract: · 1 unmodified line
6632 sysclkreq3 {
6733 sysclkreq3_default_mode: sysclkreq3_default {
6834 default_mux {
69− ste,function = "sysclkreq";
70− ste,pins = "sysclkreq3_d_1";
35+ function = "sysclkreq";
36+ groups = "sysclkreq3_d_1";
7137 };
7238 default_cfg {
73− ste,pins = "GPIO2";
39+ pins = "GPIO2";
7440 output-low;
7541 };
7642 };
@@ -78,11 +44,11 @@ Example board file extract: · 1 unmodified line
7844 gpio3 {
7945 gpio3_default_mode: gpio3_default {
8046 default_mux {
81− ste,function = "gpio";
82− ste,pins = "gpio3_a_1";
47+ function = "gpio";
48+ groups = "gpio3_a_1";
8349 };
8450 default_cfg {
85− ste,pins = "GPIO3";
51+ pins = "GPIO3";
8652 output-low;
8753 };
8854 };
@@ -90,11 +56,11 @@ Example board file extract: · 1 unmodified line
9056 sysclkreq6 {
9157 sysclkreq6_default_mode: sysclkreq6_default {
9258 default_mux {
93− ste,function = "sysclkreq";
94− ste,pins = "sysclkreq6_d_1";
59+ function = "sysclkreq";
60+ groups = "sysclkreq6_d_1";
9561 };
9662 default_cfg {
97− ste,pins = "GPIO4";
63+ pins = "GPIO4";
9864 bias-disable;
9965 };
10066 };
@@ -102,11 +68,11 @@ Example board file extract: · 1 unmodified line
10268 pwmout1 {
10369 pwmout1_default_mode: pwmout1_default {
10470 default_mux {
105− ste,function = "pwmout";
106− ste,pins = "pwmout1_d_1";
71+ function = "pwmout";
72+ groups = "pwmout1_d_1";
10773 };
10874 default_cfg {
109− ste,pins = "GPIO14";
75+ pins = "GPIO14";
11076 output-low;
11177 };
11278 };
@@ -114,11 +80,11 @@ Example board file extract: · 1 unmodified line
11480 pwmout2 {
11581 pwmout2_default_mode: pwmout2_default {
11682 pwmout2_default_mux {
117− ste,function = "pwmout";
118− ste,pins = "pwmout2_d_1";
83+ function = "pwmout";
84+ groups = "pwmout2_d_1";
11985 };
12086 pwmout2_default_cfg {
121− ste,pins = "GPIO15";
87+ pins = "GPIO15";
12288 output-low;
12389 };
12490 };
@@ -126,11 +92,11 @@ Example board file extract: · 1 unmodified line
12692 pwmout3 {
12793 pwmout3_default_mode: pwmout3_default {
12894 pwmout3_default_mux {
129− ste,function = "pwmout";
130− ste,pins = "pwmout3_d_1";
95+ function = "pwmout";
96+ groups = "pwmout3_d_1";
13197 };
13298 pwmout3_default_cfg {
133− ste,pins = "GPIO16";
99+ pins = "GPIO16";
134100 output-low;
135101 };
136102 };
@@ -139,15 +105,15 @@ Example board file extract: · 2 unmodified lines
139105
140106 adi1_default_mode: adi1_default {
141107 adi1_default_mux {
142− ste,function = "adi1";
143− ste,pins = "adi1_d_1";
108+ function = "adi1";
109+ groups = "adi1_d_1";
144110 };
145111 adi1_default_cfg1 {
146− ste,pins = "GPIO17","GPIO19","GPIO20";
112+ pins = "GPIO17","GPIO19","GPIO20";
147113 bias-disable;
148114 };
149115 adi1_default_cfg2 {
150− ste,pins = "GPIO18";
116+ pins = "GPIO18";
151117 output-low;
152118 };
153119 };
@@ -155,15 +121,15 @@ Example board file extract: · 1 unmodified line
155121 dmic12 {
156122 dmic12_default_mode: dmic12_default {
157123 dmic12_default_mux {
158− ste,function = "dmic";
159− ste,pins = "dmic12_d_1";
124+ function = "dmic";
125+ groups = "dmic12_d_1";
160126 };
161127 dmic12_default_cfg1 {
162− ste,pins = "GPIO27";
128+ pins = "GPIO27";
163129 output-low;
164130 };
165131 dmic12_default_cfg2 {
166− ste,pins = "GPIO28";
132+ pins = "GPIO28";
167133 bias-disable;
168134 };
169135 };
@@ -171,15 +137,15 @@ Example board file extract: · 1 unmodified line
171137 dmic34 {
172138 dmic34_default_mode: dmic34_default {
173139 dmic34_default_mux {
174− ste,function = "dmic";
175− ste,pins = "dmic34_d_1";
140+ function = "dmic";
141+ groups = "dmic34_d_1";
176142 };
177143 dmic34_default_cfg1 {
178− ste,pins = "GPIO29";
144+ pins = "GPIO29";
179145 output-low;
180146 };
181147 dmic34_default_cfg2 {
182− ste,pins = "GPIO30";
148+ pins = "GPIO30";
183149 bias-disable;{
184150
185151 };
@@ -188,15 +154,15 @@ Example board file extract: · 2 unmodified lines
188154 dmic56 {
189155 dmic56_default_mode: dmic56_default {
190156 dmic56_default_mux {
191− ste,function = "dmic";
192− ste,pins = "dmic56_d_1";
157+ function = "dmic";
158+ groups = "dmic56_d_1";
193159 };
194160 dmic56_default_cfg1 {
195− ste,pins = "GPIO31";
161+ pins = "GPIO31";
196162 output-low;
197163 };
198164 dmic56_default_cfg2 {
199− ste,pins = "GPIO32";
165+ pins = "GPIO32";
200166 bias-disable;
201167 };
202168 };
@@ -204,11 +170,11 @@ Example board file extract: · 1 unmodified line
204170 sysclkreq5 {
205171 sysclkreq5_default_mode: sysclkreq5_default {
206172 sysclkreq5_default_mux {
207− ste,function = "sysclkreq";
208− ste,pins = "sysclkreq5_d_1";
173+ function = "sysclkreq";
174+ groups = "sysclkreq5_d_1";
209175 };
210176 sysclkreq5_default_cfg {
211− ste,pins = "GPIO42";
177+ pins = "GPIO42";
212178 output-low;
213179 };
214180 };
@@ -216,11 +182,11 @@ Example board file extract: · 1 unmodified line
216182 batremn {
217183 batremn_default_mode: batremn_default {
218184 batremn_default_mux {
219− ste,function = "batremn";
220− ste,pins = "batremn_d_1";
185+ function = "batremn";
186+ groups = "batremn_d_1";
221187 };
222188 batremn_default_cfg {
223− ste,pins = "GPIO43";
189+ pins = "GPIO43";
224190 bias-disable;
225191 };
226192 };
@@ -228,11 +194,11 @@ Example board file extract: · 1 unmodified line
228194 service {
229195 service_default_mode: service_default {
230196 service_default_mux {
231− ste,function = "service";
232− ste,pins = "service_d_1";
197+ function = "service";
198+ groups = "service_d_1";
233199 };
234200 service_default_cfg {
235− ste,pins = "GPIO44";
201+ pins = "GPIO44";
236202 bias-disable;
237203 };
238204 };
@@ -240,13 +206,13 @@ Example board file extract: · 1 unmodified line
240206 pwrctrl0 {
241207 pwrctrl0_default_mux: pwrctrl0_mux {
242208 pwrctrl0_default_mux {
243− ste,function = "pwrctrl";
244− ste,pins = "pwrctrl0_d_1";
209+ function = "pwrctrl";
210+ groups = "pwrctrl0_d_1";
245211 };
246212 };
247213 pwrctrl0_default_mode: pwrctrl0_default {
248214 pwrctrl0_default_cfg {
249− ste,pins = "GPIO45";
215+ pins = "GPIO45";
250216 bias-disable;
251217 };
252218 };
@@ -254,13 +220,13 @@ Example board file extract: · 1 unmodified line
254220 pwrctrl1 {
255221 pwrctrl1_default_mux: pwrctrl1_mux {
256222 pwrctrl1_default_mux {
257− ste,function = "pwrctrl";
258− ste,pins = "pwrctrl1_d_1";
223+ function = "pwrctrl";
224+ groups = "pwrctrl1_d_1";
259225 };
260226 };
261227 pwrctrl1_default_mode: pwrctrl1_default {
262228 pwrctrl1_default_cfg {
263− ste,pins = "GPIO46";
229+ pins = "GPIO46";
264230 bias-disable;
265231 };
266232 };
@@ -268,11 +234,11 @@ Example board file extract: · 1 unmodified line
268234 pwmextvibra1 {
269235 pwmextvibra1_default_mode: pwmextvibra1_default {
270236 pwmextvibra1_default_mux {
271− ste,function = "pwmextvibra";
272− ste,pins = "pwmextvibra1_d_1";
237+ function = "pwmextvibra";
238+ groups = "pwmextvibra1_d_1";
273239 };
274240 pwmextvibra1_default_cfg {
275− ste,pins = "GPIO47";
241+ pins = "GPIO47";
276242 bias-disable;
277243 };
278244 };
@@ -280,11 +246,11 @@ Example board file extract: · 1 unmodified line
280246 pwmextvibra2 {
281247 pwmextvibra2_default_mode: pwmextvibra2_default {
282248 pwmextvibra2_default_mux {
283− ste,function = "pwmextvibra";
284− ste,pins = "pwmextvibra2_d_1";
249+ function = "pwmextvibra";
250+ groups = "pwmextvibra2_d_1";
285251 };
286252 pwmextvibra1_default_cfg {
287− ste,pins = "GPIO48";
253+ pins = "GPIO48";
288254 bias-disable;
289255 };
290256 };
@@ -292,11 +258,11 @@ Example board file extract: · 1 unmodified line
292258 gpio51 {
293259 gpio51_default_mode: gpio51_default {
294260 gpio51_default_mux {
295− ste,function = "gpio";
296− ste,pins = "gpio51_a_1";
261+ function = "gpio";
262+ groups = "gpio51_a_1";
297263 };
298264 gpio51_default_cfg {
299− ste,pins = "GPIO51";
265+ pins = "GPIO51";
300266 output-low;
301267 };
302268 };
@@ -304,11 +270,11 @@ Example board file extract: · 1 unmodified line
304270 gpio52 {
305271 gpio52_default_mode: gpio52_default {
306272 gpio52_default_mux {
307− ste,function = "gpio";
308− ste,pins = "gpio52_a_1";
273+ function = "gpio";
274+ groups = "gpio52_a_1";
309275 };
310276 gpio52_default_cfg {
311− ste,pins = "GPIO52";
277+ pins = "GPIO52";
312278 bias-pull-down;
313279 };
314280 };
@@ -316,11 +282,11 @@ Example board file extract: · 1 unmodified line
316282 gpio53 {
317283 gpio53_default_mode: gpio53_default {
318284 gpio53_default_mux {
319− ste,function = "gpio";
320− ste,pins = "gpio53_a_1";
285+ function = "gpio";
286+ groups = "gpio53_a_1";
321287 };
322288 gpio53_default_cfg {
323− ste,pins = "GPIO53";
289+ pins = "GPIO53";
324290 bias-pull-down;
325291 };
326292 };
@@ -328,11 +294,11 @@ Example board file extract: · 1 unmodified line
328294 gpio54 {
329295 gpio54_default_mode: gpio54_default {
330296 gpio54_default_mux {
331− ste,function = "gpio";
332− ste,pins = "gpio54_a_1";
297+ function = "gpio";
298+ groups = "gpio54_a_1";
333299 };
334300 gpio54_default_cfg {
335− ste,pins = "GPIO54";
301+ pins = "GPIO54";
336302 output-low;
337303 };
338304 };
@@ -340,11 +306,11 @@ Example board file extract: · 1 unmodified line
340306 pdmclkdat {
341307 pdmclkdat_default_mode: pdmclkdat_default {
342308 pdmclkdat_default_mux {
343− ste,function = "pdm";
344− ste,pins = "pdmclkdat_d_1";
309+ function = "pdm";
310+ groups = "pdmclkdat_d_1";
345311 };
346312 pdmclkdat_default_cfg {
347− ste,pins = "GPIO55", "GPIO56";
313+ pins = "GPIO55", "GPIO56";
348314 bias-disable;
349315 };
350316 };
Documentation/devicetree/bindings/pinctrl/ti,omap-pinctrl.txt+13−0
@@ -0,0 +1,13 @@
1+OMAP Pinctrl definitions
2+
3+Required properties:
4+- compatible : Should be one of:
5+ "ti,omap2420-padconf" - OMAP2420 compatible pinctrl
6+ "ti,omap2430-padconf" - OMAP2430 compatible pinctrl
7+ "ti,omap3-padconf" - OMAP3 compatible pinctrl
8+ "ti,omap4-padconf" - OMAP4 compatible pinctrl
9+ "ti,omap5-padconf" - OMAP5 compatible pinctrl
10+ "ti,dra7-padconf" - DRA7 compatible pinctrl
11+ "ti,am437-padconf" - AM437x compatible pinctrl
12+
13+See Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt for further details.
Documentation/devicetree/bindings/power/power-controller.txt+18−0
@@ -0,0 +1,18 @@
1+* Generic system power control capability
2+
3+Power-management integrated circuits or miscellaneous hardware components are
4+sometimes able to control the system power. The device driver associated with these
5+components might need to define this capability, which tells the kernel that
6+it can be used to switch off the system. The corresponding device must have the
7+standard property "system-power-controller" in its device node. This property
8+marks the device as able to control the system power. In order to test if this
9+property is found programmatically, use the helper function
10+"of_device_is_system_power_controller" from of.h .
11+
12+Example:
13+
14+act8846: act8846@5 {
15+ compatible = "active-semi,act8846";
16+ status = "okay";
17+ system-power-controller;
18+}
Documentation/devicetree/bindings/power/power_domain.txt+49−0
@@ -0,0 +1,49 @@
1+* Generic PM domains
2+
3+System on chip designs are often divided into multiple PM domains that can be
4+used for power gating of selected IP blocks for power saving by reduced leakage
5+current.
6+
7+This device tree binding can be used to bind PM domain consumer devices with
8+their PM domains provided by PM domain providers. A PM domain provider can be
9+represented by any node in the device tree and can provide one or more PM
10+domains. A consumer node can refer to the provider by a phandle and a set of
11+phandle arguments (so called PM domain specifiers) of length specified by the
12+#power-domain-cells property in the PM domain provider node.
13+
14+==PM domain providers==
15+
16+Required properties:
17+ - #power-domain-cells : Number of cells in a PM domain specifier;
18+ Typically 0 for nodes representing a single PM domain and 1 for nodes
19+ providing multiple PM domains (e.g. power controllers), but can be any value
20+ as specified by device tree binding documentation of particular provider.
21+
22+Example:
23+
24+ power: power-controller@12340000 {
25+ compatible = "foo,power-controller";
26+ reg = <0x12340000 0x1000>;
27+ #power-domain-cells = <1>;
28+ };
29+
30+The node above defines a power controller that is a PM domain provider and
31+expects one cell as its phandle argument.
32+
33+==PM domain consumers==
34+
35+Required properties:
36+ - power-domains : A phandle and PM domain specifier as defined by bindings of
37+ the power controller specified by phandle.
38+
39+Example:
40+
41+ leaky-device@12350000 {
42+ compatible = "foo,i-leak-current";
43+ reg = <0x12350000 0x1000>;
44+ power-domains = <&power 0>;
45+ };
46+
47+The node above defines a typical PM domain consumer device, which is located
48+inside a PM domain with index 0 of a power controller represented by a node
49+with the label "power".
Documentation/devicetree/bindings/power/reset/ltc2952-poweroff.txt+26−0
@@ -0,0 +1,26 @@
1+Binding for the LTC2952 PowerPath controller
2+
3+This chip is used to externally trigger a system shut down. Once the trigger has
4+been sent, the chips' watchdog has to be reset to gracefully shut down.
5+If the Linux systems decides to shut down it powers off the platform via the
6+kill signal.
7+
8+Required properties:
9+
10+- compatible: Must contain: "lltc,ltc2952"
11+- trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
12+ chip's trigger line
13+- watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
14+ chip's watchdog line
15+- kill-gpios: phandle + gpio-specifier for the GPIO connected to the
16+ chip's kill line
17+
18+Example:
19+
20+ltc2952 {
21+ compatible = "lltc,ltc2952";
22+
23+ trigger-gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
24+ watchdog-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
25+ kill-gpios = <&gpio0 2 GPIO_ACTIVE_LOW>;
26+};
Documentation/devicetree/bindings/power/reset/st-reset.txt+11−0
@@ -0,0 +1,11 @@
1+*Device-Tree bindings for ST SW reset functionality
2+
3+Required properties:
4+- compatible: should be "st,<chip>-restart".
5+- st,syscfg: should be a phandle of the syscfg node.
6+
7+Example node:
8+ restart {
9+ compatible = "st,stih416-restart";
10+ st,syscfg = <&syscfg_sbc>;
11+ };
Documentation/devicetree/bindings/power/reset/syscon-reboot.txt+23−0
@@ -0,0 +1,23 @@
1+Generic SYSCON mapped register reset driver
2+
3+This is a generic reset driver using syscon to map the reset register.
4+The reset is generally performed with a write to the reset register
5+defined by the register map pointed by syscon reference plus the offset
6+with the mask defined in the reboot node.
7+
8+Required properties:
9+- compatible: should contain "syscon-reboot"
10+- regmap: this is phandle to the register map node
11+- offset: offset in the register map for the reboot register (in bytes)
12+- mask: the reset value written to the reboot register (32 bit access)
13+
14+Default will be little endian mode, 32 bit access only.
15+
16+Examples:
17+
18+ reboot {
19+ compatible = "syscon-reboot";
20+ regmap = <&regmapnode>;
21+ offset = <0x0>;
22+ mask = <0x1>;
23+ };
Documentation/devicetree/bindings/power/rockchip-io-domain.txt+83−0
@@ -0,0 +1,83 @@
1+Rockchip SRAM for IO Voltage Domains:
2+-------------------------------------
3+
4+IO domain voltages on some Rockchip SoCs are variable but need to be
5+kept in sync between the regulators and the SoC using a special
6+register.
7+
8+A specific example using rk3288:
9+- If the regulator hooked up to a pin like SDMMC0_VDD is 3.3V then
10+ bit 7 of GRF_IO_VSEL needs to be 0. If the regulator hooked up to
11+ that same pin is 1.8V then bit 7 of GRF_IO_VSEL needs to be 1.
12+
13+Said another way, this driver simply handles keeping bits in the SoC's
14+general register file (GRF) in sync with the actual value of a voltage
15+hooked up to the pins.
16+
17+Note that this driver specifically doesn't include:
18+- any logic for deciding what voltage we should set regulators to
19+- any logic for deciding whether regulators (or internal SoC blocks)
20+ should have power or not have power
21+
22+If there were some other software that had the smarts of making
23+decisions about regulators, it would work in conjunction with this
24+driver. When that other software adjusted a regulator's voltage then
25+this driver would handle telling the SoC about it. A good example is
26+vqmmc for SD. In that case the dw_mmc driver simply is told about a
27+regulator. It changes the regulator between 3.3V and 1.8V at the
28+right time. This driver notices the change and makes sure that the
29+SoC is on the same page.
30+
31+
32+Required properties:
33+- compatible: should be one of:
34+ - "rockchip,rk3188-io-voltage-domain" for rk3188
35+ - "rockchip,rk3288-io-voltage-domain" for rk3288
36+- rockchip,grf: phandle to the syscon managing the "general register files"
37+
38+
39+You specify supplies using the standard regulator bindings by including
40+a phandle the the relevant regulator. All specified supplies must be able
41+to report their voltage. The IO Voltage Domain for any non-specified
42+supplies will be not be touched.
43+
44+Possible supplies for rk3188:
45+- ap0-supply: The supply connected to AP0_VCC.
46+- ap1-supply: The supply connected to AP1_VCC.
47+- cif-supply: The supply connected to CIF_VCC.
48+- flash-supply: The supply connected to FLASH_VCC.
49+- lcdc0-supply: The supply connected to LCD0_VCC.
50+- lcdc1-supply: The supply connected to LCD1_VCC.
51+- vccio0-supply: The supply connected to VCCIO0.
52+- vccio1-supply: The supply connected to VCCIO1.
53+ Sometimes also labeled VCCIO1 and VCCIO2.
54+
55+Possible supplies for rk3288:
56+- audio-supply: The supply connected to APIO4_VDD.
57+- bb-supply: The supply connected to APIO5_VDD.
58+- dvp-supply: The supply connected to DVPIO_VDD.
59+- flash0-supply: The supply connected to FLASH0_VDD. Typically for eMMC
60+- flash1-supply: The supply connected to FLASH1_VDD. Also known as SDIO1.
61+- gpio30-supply: The supply connected to APIO1_VDD.
62+- gpio1830 The supply connected to APIO2_VDD.
63+- lcdc-supply: The supply connected to LCDC_VDD.
64+- sdcard-supply: The supply connected to SDMMC0_VDD.
65+- wifi-supply: The supply connected to APIO3_VDD. Also known as SDIO0.
66+
67+
68+Example:
69+
70+ io-domains {
71+ compatible = "rockchip,rk3288-io-voltage-domain";
72+ rockchip,grf = <&grf>;
73+
74+ audio-supply = <&vcc18_codec>;
75+ bb-supply = <&vcc33_io>;
76+ dvp-supply = <&vcc_18>;
77+ flash0-supply = <&vcc18_flashio>;
78+ gpio1830-supply = <&vcc33_io>;
79+ gpio30-supply = <&vcc33_pmuio>;
80+ lcdc-supply = <&vcc33_lcd>;
81+ sdcard-supply = <&vccio_sd>;
82+ wifi-supply = <&vcc18_wl>;
83+ };
Documentation/devicetree/bindings/power_supply/charger-manager.txt+1−1
@@ -24,7 +24,7 @@ Optional properties : · 23 unmodified lines
2424 - cm-thermal-zone : name of external thermometer's thermal zone
2525 - cm-battery-* : threshold battery temperature for charging
2626 -cold : critical cold temperature of battery for charging
27− -cold-in-minus : flag that cold temerature is in minus degree
27+ -cold-in-minus : flag that cold temperature is in minus degrees
2828 -hot : critical hot temperature of battery for charging
2929 -temp-diff : temperature difference to allow recharging
3030 - cm-dis/charging-max = limits of charging duration
Documentation/devicetree/bindings/power_supply/gpio-charger.txt+27−0
@@ -0,0 +1,27 @@
1+gpio-charger
2+
3+Required properties :
4+ - compatible : "gpio-charger"
5+ - gpios : GPIO indicating the charger presence.
6+ See GPIO binding in bindings/gpio/gpio.txt .
7+ - charger-type : power supply type, one of
8+ unknown
9+ battery
10+ ups
11+ mains
12+ usb-sdp (USB standard downstream port)
13+ usb-dcp (USB dedicated charging port)
14+ usb-cdp (USB charging downstream port)
15+ usb-aca (USB accessory charger adapter)
16+
17+Example:
18+
19+ usb_charger: charger {
20+ compatible = "gpio-charger";
21+ charger-type = "usb-sdp";
22+ gpios = <&gpf0 2 0 0 0>;
23+ }
24+
25+ battery {
26+ power-supplies = <&usb_charger>;
27+ };
Documentation/devicetree/bindings/power_supply/imx-snvs-poweroff.txt+23−0
@@ -0,0 +1,23 @@
1+i.mx6 Poweroff Driver
2+
3+SNVS_LPCR in SNVS module can power off the whole system by pull
4+PMIC_ON_REQ low if PMIC_ON_REQ is connected with external PMIC.
5+If you don't want to use PMIC_ON_REQ as power on/off control,
6+please set status='disabled' to disable this driver.
7+
8+Required Properties:
9+-compatible: "fsl,sec-v4.0-poweroff"
10+-reg: Specifies the physical address of the SNVS_LPCR register
11+
12+Example:
13+ snvs@020cc000 {
14+ compatible = "fsl,sec-v4.0-mon", "simple-bus";
15+ #address-cells = <1>;
16+ #size-cells = <1>;
17+ ranges = <0 0x020cc000 0x4000>;
18+ .....
19+ snvs_poweroff: snvs-poweroff@38 {
20+ compatible = "fsl,sec-v4.0-poweroff";
21+ reg = <0x38 0x4>;
22+ };
23+ }
Documentation/devicetree/bindings/powerpc/fsl/fman.txt+534−0
@@ -0,0 +1,534 @@
1+=============================================================================
2+Freescale Frame Manager Device Bindings
3+
4+CONTENTS
5+ - FMan Node
6+ - FMan Port Node
7+ - FMan MURAM Node
8+ - FMan dTSEC/XGEC/mEMAC Node
9+ - FMan IEEE 1588 Node
10+ - Example
11+
12+=============================================================================
13+FMan Node
14+
15+DESCRIPTION
16+
17+Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
18+etc.) the FMan node will have child nodes for each of them.
19+
20+PROPERTIES
21+
22+- compatible
23+ Usage: required
24+ Value type: <stringlist>
25+ Definition: Must include "fsl,fman"
26+ FMan version can be determined via FM_IP_REV_1 register in the
27+ FMan block. The offset is 0xc4 from the beginning of the
28+ Frame Processing Manager memory map (0xc3000 from the
29+ beginning of the FMan node).
30+
31+- cell-index
32+ Usage: required
33+ Value type: <u32>
34+ Definition: Specifies the index of the FMan unit.
35+
36+ The cell-index value may be used by the SoC, to identify the
37+ FMan unit in the SoC memory map. In the table bellow,
38+ there's a description of the cell-index use in each SoC:
39+
40+ - P1023:
41+ register[bit] FMan unit cell-index
42+ ============================================================
43+ DEVDISR[1] 1 0
44+
45+ - P2041, P3041, P4080 P5020, P5040:
46+ register[bit] FMan unit cell-index
47+ ============================================================
48+ DCFG_DEVDISR2[6] 1 0
49+ DCFG_DEVDISR2[14] 2 1
50+ (Second FM available only in P4080 and P5040)
51+
52+ - B4860, T1040, T2080, T4240:
53+ register[bit] FMan unit cell-index
54+ ============================================================
55+ DCFG_CCSR_DEVDISR2[24] 1 0
56+ DCFG_CCSR_DEVDISR2[25] 2 1
57+ (Second FM available only in T4240)
58+
59+ DEVDISR, DCFG_DEVDISR2 and DCFG_CCSR_DEVDISR2 are located in
60+ the specific SoC "Device Configuration/Pin Control" Memory
61+ Map.
62+
63+- reg
64+ Usage: required
65+ Value type: <prop-encoded-array>
66+ Definition: A standard property. Specifies the offset of the
67+ following configuration registers:
68+ - BMI configuration registers.
69+ - QMI configuration registers.
70+ - DMA configuration registers.
71+ - FPM configuration registers.
72+ - FMan controller configuration registers.
73+
74+- ranges
75+ Usage: required
76+ Value type: <prop-encoded-array>
77+ Definition: A standard property.
78+
79+- clocks
80+ Usage: required
81+ Value type: <prop-encoded-array>
82+ Definition: phandle for the fman input clock.
83+
84+- clock-names
85+ usage: required
86+ Value type: <stringlist>
87+ Definition: "fmanclk" for the fman input clock.
88+
89+- interrupts
90+ Usage: required
91+ Value type: <prop-encoded-array>
92+ Definition: A pair of IRQs are specified in this property.
93+ The first element is associated with the event interrupts and
94+ the second element is associated with the error interrupts.
95+
96+- fsl,qman-channel-range
97+ Usage: required
98+ Value type: <prop-encoded-array>
99+ Definition: Specifies the range of the available dedicated
100+ channels in the FMan. The first cell specifies the beginning
101+ of the range and the second cell specifies the number of
102+ channels.
103+ Further information available at:
104+ "Work Queue (WQ) Channel Assignments in the QMan" section
105+ in DPAA Reference Manual.
106+
107+- fsl,qman
108+- fsl,bman
109+ Usage: required
110+ Definition: See soc/fsl/qman.txt and soc/fsl/bman.txt
111+
112+=============================================================================
113+FMan MURAM Node
114+
115+DESCRIPTION
116+
117+FMan Internal memory - shared between all the FMan modules.
118+It contains data structures that are common and written to or read by
119+the modules.
120+FMan internal memory is split into the following parts:
121+ Packet buffering (Tx/Rx FIFOs)
122+ Frames internal context
123+
124+PROPERTIES
125+
126+- compatible
127+ Usage: required
128+ Value type: <stringlist>
129+ Definition: Must include "fsl,fman-muram"
130+
131+- ranges
132+ Usage: required
133+ Value type: <prop-encoded-array>
134+ Definition: A standard property.
135+ Specifies the multi-user memory offset and the size within
136+ the FMan.
137+
138+EXAMPLE
139+
140+muram@0 {
141+ compatible = "fsl,fman-muram";
142+ ranges = <0 0x000000 0x28000>;
143+};
144+
145+=============================================================================
146+FMan Port Node
147+
148+DESCRIPTION
149+
150+The Frame Manager (FMan) supports several types of hardware ports:
151+ Ethernet receiver (RX)
152+ Ethernet transmitter (TX)
153+ Offline/Host command (O/H)
154+
155+PROPERTIES
156+
157+- compatible
158+ Usage: required
159+ Value type: <stringlist>
160+ Definition: A standard property.
161+ Must include one of the following:
162+ - "fsl,fman-v2-port-oh" for FManV2 OH ports
163+ - "fsl,fman-v2-port-rx" for FManV2 RX ports
164+ - "fsl,fman-v2-port-tx" for FManV2 TX ports
165+ - "fsl,fman-v3-port-oh" for FManV3 OH ports
166+ - "fsl,fman-v3-port-rx" for FManV3 RX ports
167+ - "fsl,fman-v3-port-tx" for FManV3 TX ports
168+
169+- cell-index
170+ Usage: required
171+ Value type: <u32>
172+ Definition: Specifies the hardware port id.
173+ Each hardware port on the FMan has its own hardware PortID.
174+ Super set of all hardware Port IDs available at FMan Reference
175+ Manual under "FMan Hardware Ports in Freescale Devices" table.
176+
177+ Each hardware port is assigned a 4KB, port-specific page in
178+ the FMan hardware port memory region (which is part of the
179+ FMan memory map). The first 4 KB in the FMan hardware ports
180+ memory region is used for what are called common registers.
181+ The subsequent 63 4KB pages are allocated to the hardware
182+ ports.
183+ The page of a specific port is determined by the cell-index.
184+
185+- reg
186+ Usage: required
187+ Value type: <prop-encoded-array>
188+ Definition: There is one reg region describing the port
189+ configuration registers.
190+
191+EXAMPLE
192+
193+port@a8000 {
194+ cell-index = <0x28>;
195+ compatible = "fsl,fman-v2-port-tx";
196+ reg = <0xa8000 0x1000>;
197+};
198+
199+port@88000 {
200+ cell-index = <0x8>;
201+ compatible = "fsl,fman-v2-port-rx";
202+ reg = <0x88000 0x1000>;
203+};
204+
205+port@81000 {
206+ cell-index = <0x1>;
207+ compatible = "fsl,fman-v2-port-oh";
208+ reg = <0x81000 0x1000>;
209+};
210+
211+=============================================================================
212+FMan dTSEC/XGEC/mEMAC Node
213+
214+DESCRIPTION
215+
216+mEMAC/dTSEC/XGEC are the Ethernet network interfaces
217+
218+PROPERTIES
219+
220+- compatible
221+ Usage: required
222+ Value type: <stringlist>
223+ Definition: A standard property.
224+ Must include one of the following:
225+ - "fsl,fman-dtsec" for dTSEC MAC
226+ - "fsl,fman-xgec" for XGEC MAC
227+ - "fsl,fman-memac for mEMAC MAC
228+
229+- cell-index
230+ Usage: required
231+ Value type: <u32>
232+ Definition: Specifies the MAC id.
233+
234+ The cell-index value may be used by the FMan or the SoC, to
235+ identify the MAC unit in the FMan (or SoC) memory map.
236+ In the tables bellow there's a description of the cell-index
237+ use, there are two tables, one describes the use of cell-index
238+ by the FMan, the second describes the use by the SoC:
239+
240+ 1. FMan Registers
241+
242+ FManV2:
243+ register[bit] MAC cell-index
244+ ============================================================
245+ FM_EPI[16] XGEC 8
246+ FM_EPI[16+n] dTSECn n-1
247+ FM_NPI[11+n] dTSECn n-1
248+ n = 1,..,5
249+
250+ FManV3:
251+ register[bit] MAC cell-index
252+ ============================================================
253+ FM_EPI[16+n] mEMACn n-1
254+ FM_EPI[25] mEMAC10 9
255+
256+ FM_NPI[11+n] mEMACn n-1
257+ FM_NPI[10] mEMAC10 9
258+ FM_NPI[11] mEMAC9 8
259+ n = 1,..8
260+
261+ FM_EPI and FM_NPI are located in the FMan memory map.
262+
263+ 2. SoC registers:
264+
265+ - P2041, P3041, P4080 P5020, P5040:
266+ register[bit] FMan MAC cell
267+ Unit index
268+ ============================================================
269+ DCFG_DEVDISR2[7] 1 XGEC 8
270+ DCFG_DEVDISR2[7+n] 1 dTSECn n-1
271+ DCFG_DEVDISR2[15] 2 XGEC 8
272+ DCFG_DEVDISR2[15+n] 2 dTSECn n-1
273+ n = 1,..5
274+
275+ - T1040, T2080, T4240, B4860:
276+ register[bit] FMan MAC cell
277+ Unit index
278+ ============================================================
279+ DCFG_CCSR_DEVDISR2[n-1] 1 mEMACn n-1
280+ DCFG_CCSR_DEVDISR2[11+n] 2 mEMACn n-1
281+ n = 1,..6,9,10
282+
283+ EVDISR, DCFG_DEVDISR2 and DCFG_CCSR_DEVDISR2 are located in
284+ the specific SoC "Device Configuration/Pin Control" Memory
285+ Map.
286+
287+- reg
288+ Usage: required
289+ Value type: <prop-encoded-array>
290+ Definition: A standard property.
291+
292+- fsl,fman-ports
293+ Usage: required
294+ Value type: <prop-encoded-array>
295+ Definition: An array of two phandles - the first references is
296+ the FMan RX port and the second is the TX port used by this
297+ MAC.
298+
299+- ptp-timer
300+ Usage required
301+ Value type: <phandle>
302+ Definition: A phandle for 1EEE1588 timer.
303+
304+EXAMPLE
305+
306+fman1_tx28: port@a8000 {
307+ cell-index = <0x28>;
308+ compatible = "fsl,fman-v2-port-tx";
309+ reg = <0xa8000 0x1000>;
310+};
311+
312+fman1_rx8: port@88000 {
313+ cell-index = <0x8>;
314+ compatible = "fsl,fman-v2-port-rx";
315+ reg = <0x88000 0x1000>;
316+};
317+
318+ptp-timer: ptp_timer@fe000 {
319+ compatible = "fsl,fman-ptp-timer";
320+ reg = <0xfe000 0x1000>;
321+};
322+
323+ethernet@e0000 {
324+ compatible = "fsl,fman-dtsec";
325+ cell-index = <0>;
326+ reg = <0xe0000 0x1000>;
327+ fsl,fman-ports = <&fman1_rx8 &fman1_tx28>;
328+ ptp-timer = <&ptp-timer>;
329+};
330+
331+============================================================================
332+FMan IEEE 1588 Node
333+
334+DESCRIPTION
335+
336+The FMan interface to support IEEE 1588
337+
338+
339+PROPERTIES
340+
341+- compatible
342+ Usage: required
343+ Value type: <stringlist>
344+ Definition: A standard property.
345+ Must include "fsl,fman-ptp-timer".
346+
347+- reg
348+ Usage: required
349+ Value type: <prop-encoded-array>
350+ Definition: A standard property.
351+
352+EXAMPLE
353+
354+ptp-timer@fe000 {
355+ compatible = "fsl,fman-ptp-timer";
356+ reg = <0xfe000 0x1000>;
357+};
358+
359+=============================================================================
360+Example
361+
362+fman@400000 {
363+ #address-cells = <1>;
364+ #size-cells = <1>;
365+ cell-index = <1>;
366+ compatible = "fsl,fman"
367+ ranges = <0 0x400000 0x100000>;
368+ reg = <0x400000 0x100000>;
369+ clocks = <&fman_clk>;
370+ clock-names = "fmanclk";
371+ interrupts = <
372+ 96 2 0 0
373+ 16 2 1 1>;
374+ fsl,qman-channel-range = <0x40 0xc>;
375+
376+ muram@0 {
377+ compatible = "fsl,fman-muram";
378+ reg = <0x0 0x28000>;
379+ };
380+
381+ port@81000 {
382+ cell-index = <1>;
383+ compatible = "fsl,fman-v2-port-oh";
384+ reg = <0x81000 0x1000>;
385+ };
386+
387+ port@82000 {
388+ cell-index = <2>;
389+ compatible = "fsl,fman-v2-port-oh";
390+ reg = <0x82000 0x1000>;
391+ };
392+
393+ port@83000 {
394+ cell-index = <3>;
395+ compatible = "fsl,fman-v2-port-oh";
396+ reg = <0x83000 0x1000>;
397+ };
398+
399+ port@84000 {
400+ cell-index = <4>;
401+ compatible = "fsl,fman-v2-port-oh";
402+ reg = <0x84000 0x1000>;
403+ };
404+
405+ port@85000 {
406+ cell-index = <5>;
407+ compatible = "fsl,fman-v2-port-oh";
408+ reg = <0x85000 0x1000>;
409+ };
410+
411+ port@86000 {
412+ cell-index = <6>;
413+ compatible = "fsl,fman-v2-port-oh";
414+ reg = <0x86000 0x1000>;
415+ };
416+
417+ fman1_rx_0x8: port@88000 {
418+ cell-index = <0x8>;
419+ compatible = "fsl,fman-v2-port-rx";
420+ reg = <0x88000 0x1000>;
421+ };
422+
423+ fman1_rx_0x9: port@89000 {
424+ cell-index = <0x9>;
425+ compatible = "fsl,fman-v2-port-rx";
426+ reg = <0x89000 0x1000>;
427+ };
428+
429+ fman1_rx_0xa: port@8a000 {
430+ cell-index = <0xa>;
431+ compatible = "fsl,fman-v2-port-rx";
432+ reg = <0x8a000 0x1000>;
433+ };
434+
435+ fman1_rx_0xb: port@8b000 {
436+ cell-index = <0xb>;
437+ compatible = "fsl,fman-v2-port-rx";
438+ reg = <0x8b000 0x1000>;
439+ };
440+
441+ fman1_rx_0xc: port@8c000 {
442+ cell-index = <0xc>;
443+ compatible = "fsl,fman-v2-port-rx";
444+ reg = <0x8c000 0x1000>;
445+ };
446+
447+ fman1_rx_0x10: port@90000 {
448+ cell-index = <0x10>;
449+ compatible = "fsl,fman-v2-port-rx";
450+ reg = <0x90000 0x1000>;
451+ };
452+
453+ fman1_tx_0x28: port@a8000 {
454+ cell-index = <0x28>;
455+ compatible = "fsl,fman-v2-port-tx";
456+ reg = <0xa8000 0x1000>;
457+ };
458+
459+ fman1_tx_0x29: port@a9000 {
460+ cell-index = <0x29>;
461+ compatible = "fsl,fman-v2-port-tx";
462+ reg = <0xa9000 0x1000>;
463+ };
464+
465+ fman1_tx_0x2a: port@aa000 {
466+ cell-index = <0x2a>;
467+ compatible = "fsl,fman-v2-port-tx";
468+ reg = <0xaa000 0x1000>;
469+ };
470+
471+ fman1_tx_0x2b: port@ab000 {
472+ cell-index = <0x2b>;
473+ compatible = "fsl,fman-v2-port-tx";
474+ reg = <0xab000 0x1000>;
475+ };
476+
477+ fman1_tx_0x2c: port@ac0000 {
478+ cell-index = <0x2c>;
479+ compatible = "fsl,fman-v2-port-tx";
480+ reg = <0xac000 0x1000>;
481+ };
482+
483+ fman1_tx_0x30: port@b0000 {
484+ cell-index = <0x30>;
485+ compatible = "fsl,fman-v2-port-tx";
486+ reg = <0xb0000 0x1000>;
487+ };
488+
489+ ethernet@e0000 {
490+ compatible = "fsl,fman-dtsec";
491+ cell-index = <0>;
492+ reg = <0xe0000 0x1000>;
493+ fsl,fman-ports = <&fman1_rx_0x8 &fman1_tx_0x28>;
494+ };
495+
496+ ethernet@e2000 {
497+ compatible = "fsl,fman-dtsec";
498+ cell-index = <1>;
499+ reg = <0xe2000 0x1000>;
500+ fsl,fman-ports = <&fman1_rx_0x9 &fman1_tx_0x29>;
501+ };
502+
503+ ethernet@e4000 {
504+ compatible = "fsl,fman-dtsec";
505+ cell-index = <2>;
506+ reg = <0xe4000 0x1000>;
507+ fsl,fman-ports = <&fman1_rx_0xa &fman1_tx_0x2a>;
508+ };
509+
510+ ethernet@e6000 {
511+ compatible = "fsl,fman-dtsec";
512+ cell-index = <3>;
513+ reg = <0xe6000 0x1000>;
514+ fsl,fman-ports = <&fman1_rx_0xb &fman1_tx_0x2b>;
515+ };
516+
517+ ethernet@e8000 {
518+ compatible = "fsl,fman-dtsec";
519+ cell-index = <4>;
520+ reg = <0xf0000 0x1000>;
521+ fsl,fman-ports = <&fman1_rx_0xc &fman1_tx_0x2c>;
522+
523+ ethernet@f0000 {
524+ cell-index = <8>;
525+ compatible = "fsl,fman-xgec";
526+ reg = <0xf0000 0x1000>;
527+ fsl,fman-ports = <&fman1_rx_0x10 &fman1_tx_0x30>;
528+ };
529+
530+ ptp-timer@fe000 {
531+ compatible = "fsl,fman-ptp-timer";
532+ reg = <0xfe000 0x1000>;
533+ };
534+};
Documentation/devicetree/bindings/pwm/atmel-hlcdc-pwm.txt+29−0
@@ -0,0 +1,29 @@
1+Device-Tree bindings for Atmel's HLCDC (High-end LCD Controller) PWM driver
2+
3+The Atmel HLCDC PWM is subdevice of the HLCDC MFD device.
4+See ../mfd/atmel-hlcdc.txt for more details.
5+
6+Required properties:
7+ - compatible: value should be one of the following:
8+ "atmel,hlcdc-pwm"
9+ - pinctr-names: the pin control state names. Should contain "default".
10+ - pinctrl-0: should contain the pinctrl states described by pinctrl
11+ default.
12+ - #pwm-cells: should be set to 3. This PWM chip use the default 3 cells
13+ bindings defined in pwm.txt in this directory.
14+
15+Example:
16+
17+ hlcdc: hlcdc@f0030000 {
18+ compatible = "atmel,sama5d3-hlcdc";
19+ reg = <0xf0030000 0x2000>;
20+ clocks = <&lcdc_clk>, <&lcdck>, <&clk32k>;
21+ clock-names = "periph_clk","sys_clk", "slow_clk";
22+
23+ hlcdc_pwm: hlcdc-pwm {
24+ compatible = "atmel,hlcdc-pwm";
25+ pinctrl-names = "default";
26+ pinctrl-0 = <&pinctrl_lcd_pwm>;
27+ #pwm-cells = <3>;
28+ };
29+ };
Documentation/devicetree/bindings/pwm/pwm-bcm2835.txt+30−0
@@ -0,0 +1,30 @@
1+BCM2835 PWM controller (Raspberry Pi controller)
2+
3+Required properties:
4+- compatible: should be "brcm,bcm2835-pwm"
5+- reg: physical base address and length of the controller's registers
6+- clock: This clock defines the base clock frequency of the PWM hardware
7+ system, the period and the duty_cycle of the PWM signal is a multiple of
8+ the base period.
9+- #pwm-cells: Should be 2. See pwm.txt in this directory for a description of
10+ the cells format.
11+
12+Examples:
13+
14+pwm@2020c000 {
15+ compatible = "brcm,bcm2835-pwm";
16+ reg = <0x2020c000 0x28>;
17+ clocks = <&clk_pwm>;
18+ #pwm-cells = <2>;
19+};
20+
21+clocks {
22+ ....
23+ clk_pwm: pwm {
24+ compatible = "fixed-clock";
25+ reg = <3>;
26+ #clock-cells = <0>;
27+ clock-frequency = <9200000>;
28+ };
29+ ....
30+};
Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt+18−1
@@ -1,5 +1,20 @@
11 Freescale FlexTimer Module (FTM) PWM controller
22
3+The same FTM PWM device can have a different endianness on different SoCs. The
4+device tree provides a property to describing this so that an operating system
5+device driver can handle all variants of the device. Refer to the table below
6+for the endianness of the FTM PWM block as integrated into the existing SoCs:
7+
8+ SoC | FTM-PWM endianness
9+ --------+-------------------
10+ Vybrid | LE
11+ LS1 | BE
12+ LS2 | LE
13+
14+Please see ../regmap/regmap.txt for more detail about how to specify endian
15+modes in device tree.
16+
17+
318 Required properties:
419 - compatible: Should be "fsl,vf610-ftm-pwm".
520 - reg: Physical base address and length of the controller's registers
@@ -16,7 +31,8 @@ Required properties: · 10 unmodified lines
1631 - pinctrl-names: Must contain a "default" entry.
1732 - pinctrl-NNN: One property must exist for each entry in pinctrl-names.
1833 See pinctrl/pinctrl-bindings.txt for details of the property values.
19−
34+- big-endian: Boolean property, required if the FTM PWM registers use a big-
35+ endian rather than little-endian layout.
2036
2137 Example:
2238
@@ -32,4 +48,5 @@ pwm0: pwm@40038000 { · 9 unmodified lines
3248 <&clks VF610_CLK_FTM0_EXT_FIX_EN>;
3349 pinctrl-names = "default";
3450 pinctrl-0 = <&pinctrl_pwm0_1>;
51+ big-endian;
3552 };
Documentation/devicetree/bindings/pwm/pwm-rockchip.txt+2−2
@@ -7,8 +7,8 @@ Required properties: · 6 unmodified lines
77 "rockchip,vop-pwm": found integrated in VOP on RK3288 SoC
88 - reg: physical base address and length of the controller's registers
99 - clocks: phandle and clock specifier of the PWM reference clock
10− - #pwm-cells: should be 2. See pwm.txt in this directory for a
11− description of the cell format.
10+ - #pwm-cells: must be 2 (rk2928) or 3 (rk3288). See pwm.txt in this directory
11+ for a description of the cell format.
1212
1313 Example:
1414
Documentation/devicetree/bindings/regmap/regmap.txt+47−0
@@ -0,0 +1,47 @@
1+Device-Tree binding for regmap
2+
3+The endianness mode of CPU & Device scenarios:
4+Index Device Endianness properties
5+---------------------------------------------------
6+1 BE 'big-endian'
7+2 LE 'little-endian'
8+
9+For one device driver, which will run in different scenarios above
10+on different SoCs using the devicetree, we need one way to simplify
11+this.
12+
13+Required properties:
14+- {big,little}-endian: these are boolean properties, if absent
15+ meaning that the CPU and the Device are in the same endianness mode,
16+ these properties are for register values and all the buffers only.
17+
18+Examples:
19+Scenario 1 : CPU in LE mode & device in LE mode.
20+dev: dev@40031000 {
21+ compatible = "name";
22+ reg = <0x40031000 0x1000>;
23+ ...
24+};
25+
26+Scenario 2 : CPU in LE mode & device in BE mode.
27+dev: dev@40031000 {
28+ compatible = "name";
29+ reg = <0x40031000 0x1000>;
30+ ...
31+ big-endian;
32+};
33+
34+Scenario 3 : CPU in BE mode & device in BE mode.
35+dev: dev@40031000 {
36+ compatible = "name";
37+ reg = <0x40031000 0x1000>;
38+ ...
39+};
40+
41+Scenario 4 : CPU in BE mode & device in LE mode.
42+dev: dev@40031000 {
43+ compatible = "name";
44+ reg = <0x40031000 0x1000>;
45+ ...
46+ little-endian;
47+};
Documentation/devicetree/bindings/regulator/act8865-regulator.txt+4−0
@@ -5,6 +5,10 @@ Required properties: · 4 unmodified lines
55 - compatible: "active-semi,act8846" or "active-semi,act8865"
66 - reg: I2C slave address
77
8+Optional properties:
9+- system-power-controller: Telling whether or not this pmic is controlling
10+ the system power. See Documentation/devicetree/bindings/power/power-controller.txt .
11+
812 Any standard regulator properties can be used to configure the single regulator.
913
1014 The valid names for regulators are:
Documentation/devicetree/bindings/regulator/da9210.txt+2−2
@@ -2,7 +2,7 @@ · 1 unmodified line
22
33 Required properties:
44
5−- compatible: must be "diasemi,da9210"
5+- compatible: must be "dlg,da9210"
66 - reg: the i2c slave address of the regulator. It should be 0x68.
77
88 Any standard regulator properties can be used to configure the single da9210
@@ -11,7 +11,7 @@ DCDC. · 2 unmodified lines
1111 Example:
1212
1313 da9210@68 {
14− compatible = "diasemi,da9210";
14+ compatible = "dlg,da9210";
1515 reg = <0x68>;
1616
1717 regulator-min-microvolt = <900000>;
Documentation/devicetree/bindings/regulator/da9211.txt+63−0
@@ -0,0 +1,63 @@
1+* Dialog Semiconductor DA9211/DA9213 Voltage Regulator
2+
3+Required properties:
4+- compatible: "dlg,da9211" or "dlg,da9213".
5+- reg: I2C slave address, usually 0x68.
6+- interrupts: the interrupt outputs of the controller
7+- regulators: A node that houses a sub-node for each regulator within the
8+ device. Each sub-node is identified using the node's name, with valid
9+ values listed below. The content of each sub-node is defined by the
10+ standard binding for regulators; see regulator.txt.
11+ BUCKA and BUCKB.
12+
13+Optional properties:
14+- Any optional property defined in regulator.txt
15+
16+Example 1) DA9211
17+
18+ pmic: da9211@68 {
19+ compatible = "dlg,da9211";
20+ reg = <0x68>;
21+ interrupts = <3 27>;
22+
23+ regulators {
24+ BUCKA {
25+ regulator-name = "VBUCKA";
26+ regulator-min-microvolt = < 300000>;
27+ regulator-max-microvolt = <1570000>;
28+ regulator-min-microamp = <2000000>;
29+ regulator-max-microamp = <5000000>;
30+ };
31+ BUCKB {
32+ regulator-name = "VBUCKB";
33+ regulator-min-microvolt = < 300000>;
34+ regulator-max-microvolt = <1570000>;
35+ regulator-min-microamp = <2000000>;
36+ regulator-max-microamp = <5000000>;
37+ };
38+ };
39+ };
40+
41+Example 2) DA92113
42+ pmic: da9213@68 {
43+ compatible = "dlg,da9213";
44+ reg = <0x68>;
45+ interrupts = <3 27>;
46+
47+ regulators {
48+ BUCKA {
49+ regulator-name = "VBUCKA";
50+ regulator-min-microvolt = < 300000>;
51+ regulator-max-microvolt = <1570000>;
52+ regulator-min-microamp = <3000000>;
53+ regulator-max-microamp = <6000000>;
54+ };
55+ BUCKB {
56+ regulator-name = "VBUCKB";
57+ regulator-min-microvolt = < 300000>;
58+ regulator-max-microvolt = <1570000>;
59+ regulator-min-microamp = <3000000>;
60+ regulator-max-microamp = <6000000>;
61+ };
62+ };
63+ };
Documentation/devicetree/bindings/regulator/fan53555.txt+23−0
@@ -0,0 +1,23 @@
1+Binding for Fairchild FAN53555 regulators
2+
3+Required properties:
4+ - compatible: one of "fcs,fan53555", "silergy,syr827", "silergy,syr828"
5+ - reg: I2C address
6+
7+Optional properties:
8+ - fcs,suspend-voltage-selector: declare which of the two available
9+ voltage selector registers should be used for the suspend
10+ voltage. The other one is used for the runtime voltage setting
11+ Possible values are either <0> or <1>
12+ - vin-supply: regulator supplying the vin pin
13+
14+Example:
15+
16+ regulator@40 {
17+ compatible = "fcs,fan53555";
18+ regulator-name = "fan53555";
19+ regulator-min-microvolt = <1000000>;
20+ regulator-max-microvolt = <1800000>;
21+ vin-supply = <&parent_reg>;
22+ fcs,suspend-voltage-selector = <1>;
23+ };
Documentation/devicetree/bindings/regulator/isl9305.txt+36−0
@@ -0,0 +1,36 @@
1+Intersil ISL9305/ISL9305H voltage regulator
2+
3+Required properties:
4+
5+- compatible: "isl,isl9305" or "isl,isl9305h"
6+- reg: I2C slave address, usually 0x68.
7+- regulators: A node that houses a sub-node for each regulator within the
8+ device. Each sub-node is identified using the node's name, with valid
9+ values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
10+ is defined by the standard binding for regulators; see regulator.txt.
11+- VINDCD1-supply: A phandle to a regulator node supplying VINDCD1.
12+ VINDCD2-supply: A phandle to a regulator node supplying VINDCD2.
13+ VINLDO1-supply: A phandle to a regulator node supplying VINLDO1.
14+ VINLDO2-supply: A phandle to a regulator node supplying VINLDO2.
15+
16+Optional properties:
17+- Per-regulator optional properties are defined in regulator.txt
18+
19+Example
20+
21+ pmic: isl9305@68 {
22+ compatible = "isl,isl9305";
23+ reg = <0x68>;
24+
25+ VINDCD1-supply = <&system_power>;
26+ VINDCD2-supply = <&system_power>;
27+ VINLDO1-supply = <&system_power>;
28+ VINLDO2-supply = <&system_power>;
29+
30+ regulators {
31+ dcd1 {
32+ regulator-name = "VDD_DSP";
33+ regulator-always-on;
34+ };
35+ };
36+ };
Documentation/devicetree/bindings/regulator/max1586-regulator.txt+28−0
@@ -0,0 +1,28 @@
1+Maxim MAX1586 voltage regulator
2+
3+Required properties:
4+- compatible: must be "maxim,max1586"
5+- reg: I2C slave address, usually 0x14
6+- v3-gain: integer specifying the V3 gain as per datasheet
7+ (1 + R24/R25 + R24/185.5kOhm)
8+- any required generic properties defined in regulator.txt
9+
10+Example:
11+
12+ i2c_master {
13+ max1586@14 {
14+ compatible = "maxim,max1586";
15+ reg = <0x14>;
16+ v3-gain = <1000000>;
17+
18+ regulators {
19+ vcc_core: v3 {
20+ regulator-name = "vcc_core";
21+ regulator-compatible = "Output_V3";
22+ regulator-min-microvolt = <1000000>;
23+ regulator-max-microvolt = <1705000>;
24+ regulator-always-on;
25+ };
26+ };
27+ };
28+ };
Documentation/devicetree/bindings/regulator/max77802.txt+88−0
@@ -0,0 +1,88 @@
1+Binding for Maxim MAX77802 regulators
2+
3+This is a part of device tree bindings of MAX77802 multi-function device.
4+More information can be found in bindings/mfd/max77802.txt file.
5+
6+The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO)
7+regulators that can be controlled over I2C.
8+
9+Following properties should be present in main device node of the MFD chip.
10+
11+Optional node:
12+- regulators : The regulators of max77802 have to be instantiated
13+ under subnode named "regulators" using the following format.
14+
15+ regulator-name {
16+ standard regulator constraints....
17+ };
18+ refer Documentation/devicetree/bindings/regulator/regulator.txt
19+
20+The regulator node name should be initialized with a string to get matched
21+with their hardware counterparts as follow. The valid names are:
22+
23+ -LDOn : for LDOs, where n can lie in ranges 1-15, 17-21, 23-30
24+ and 32-35.
25+ example: LDO1, LDO2, LDO35.
26+ -BUCKn : for BUCKs, where n can lie in range 1 to 10.
27+ example: BUCK1, BUCK5, BUCK10.
28+
29+The max77802 regulator supports two different operating modes: Normal and Low
30+Power Mode. Some regulators support the modes to be changed at startup or by
31+the consumers during normal operation while others only support to change the
32+mode during system suspend. The standard regulator suspend states binding can
33+be used to configure the regulator operating mode.
34+
35+The regulators that support the standard "regulator-initial-mode" property,
36+changing their mode during normal operation are: LDOs 1, 3, 20 and 21.
37+
38+The possible values for "regulator-initial-mode" and "regulator-mode" are:
39+ 1: Normal regulator voltage output mode.
40+ 3: Low Power which reduces the quiescent current down to only 1uA
41+
42+The list of valid modes are defined in the dt-bindings/clock/maxim,max77802.h
43+header and can be included by device tree source files.
44+
45+The standard "regulator-mode" property can only be used for regulators that
46+support changing their mode to Low Power Mode during suspend. These regulators
47+are: BUCKs 2-4 and LDOs 1-35. Also, it only takes effect if the regulator has
48+been enabled for the given suspend state using "regulator-on-in-suspend" and
49+has not been disabled for that state using "regulator-off-in-suspend".
50+
51+Example:
52+
53+ max77802@09 {
54+ compatible = "maxim,max77802";
55+ interrupt-parent = <&wakeup_eint>;
56+ interrupts = <26 0>;
57+ reg = <0x09>;
58+ #address-cells = <1>;
59+ #size-cells = <0>;
60+
61+ regulators {
62+ ldo1_reg: LDO1 {
63+ regulator-name = "vdd_1v0";
64+ regulator-min-microvolt = <1000000>;
65+ regulator-max-microvolt = <1000000>;
66+ regulator-always-on;
67+ regulator-initial-mode = <MAX77802_OPMODE_LP>;
68+ };
69+
70+ ldo11_reg: LDO11 {
71+ regulator-name = "vdd_ldo11";
72+ regulator-min-microvolt = <1900000>;
73+ regulator-max-microvolt = <1900000>;
74+ regulator-always-on;
75+ regulator-state-mem {
76+ regulator-on-in-suspend;
77+ regulator-mode = <MAX77802_OPMODE_LP>;
78+ };
79+ };
80+
81+ buck1_reg: BUCK1 {
82+ regulator-name = "vdd_mif";
83+ regulator-min-microvolt = <950000>;
84+ regulator-max-microvolt = <1300000>;
85+ regulator-always-on;
86+ regulator-boot-on;
87+ };
88+ };
Documentation/devicetree/bindings/regulator/pwm-regulator.txt+27−0
@@ -0,0 +1,27 @@
1+pwm regulator bindings
2+
3+Required properties:
4+- compatible: Should be "pwm-regulator"
5+- pwms: OF device-tree PWM specification (see PWM binding pwm.txt)
6+- voltage-table: voltage and duty table, include 2 members in each set of
7+ brackets, first one is voltage(unit: uv), the next is duty(unit: percent)
8+
9+Any property defined as part of the core regulator binding defined in
10+regulator.txt can also be used.
11+
12+Example:
13+ pwm_regulator {
14+ compatible = "pwm-regulator;
15+ pwms = <&pwm1 0 8448 0>;
16+
17+ voltage-table = <1114000 0>,
18+ <1095000 10>,
19+ <1076000 20>,
20+ <1056000 30>,
21+ <1036000 40>,
22+ <1016000 50>;
23+
24+ regulator-min-microvolt = <1016000>;
25+ regulator-max-microvolt = <1114000>;
26+ regulator-name = "vdd_logic";
27+ };
Documentation/devicetree/bindings/regulator/regulator.txt+22−0
@@ -19,6 +19,24 @@ Optional properties: · 18 unmodified lines
1919 design requires. This property describes the total system ramp time
2020 required due to the combination of internal ramping of the regulator itself,
2121 and board design issues such as trace capacitance and load on the supply.
22+- regulator-state-mem sub-root node for Suspend-to-RAM mode
23+ : suspend to memory, the device goes to sleep, but all data stored in memory,
24+ only some external interrupt can wake the device.
25+- regulator-state-disk sub-root node for Suspend-to-DISK mode
26+ : suspend to disk, this state operates similarly to Suspend-to-RAM,
27+ but includes a final step of writing memory contents to disk.
28+- regulator-state-[mem/disk] node has following common properties:
29+ - regulator-on-in-suspend: regulator should be on in suspend state.
30+ - regulator-off-in-suspend: regulator should be off in suspend state.
31+ - regulator-suspend-microvolt: regulator should be set to this voltage
32+ in suspend.
33+ - regulator-mode: operating mode in the given suspend state.
34+ The set of possible operating modes depends on the capabilities of
35+ every hardware so the valid modes are documented on each regulator
36+ device tree binding document.
37+- regulator-initial-mode: initial operating mode. The set of possible operating
38+ modes depends on the capabilities of every hardware so each device binding
39+ documentation explains which values the regulator supports.
2240
2341 Deprecated properties:
2442 - regulator-compatible: If a regulator chip contains multiple
@@ -34,6 +52,10 @@ Example: · 9 unmodified lines
3452 regulator-max-microvolt = <2500000>;
3553 regulator-always-on;
3654 vin-supply = <&vin>;
55+
56+ regulator-state-mem {
57+ regulator-on-in-suspend;
58+ };
3759 };
3860
3961 Regulator Consumers:
Documentation/devicetree/bindings/regulator/sky81452-regulator.txt+18−0
@@ -0,0 +1,18 @@
1+SKY81452 voltage regulator
2+
3+Required properties:
4+- regulator node named lout.
5+- any required generic properties defined in regulator.txt
6+
7+Optional properties:
8+- any available generic properties defined in regulator.txt
9+
10+Example:
11+
12+ regulator {
13+ lout {
14+ regulator-name = "sky81452-lout";
15+ regulator-min-microvolt = <4500000>;
16+ regulator-max-microvolt = <8000000>;
17+ };
18+ };
Documentation/devicetree/bindings/reset/st,sti-picophyreset.txt+42−0
@@ -0,0 +1,42 @@
1+STMicroelectronics STi family Sysconfig Picophy SoftReset Controller
2+=============================================================================
3+
4+This binding describes a reset controller device that is used to enable and
5+disable on-chip PicoPHY USB2 phy(s) using "softreset" control bits found in
6+the STi family SoC system configuration registers.
7+
8+The actual action taken when softreset is asserted is hardware dependent.
9+However, when asserted it may not be possible to access the hardware's
10+registers and after an assert/deassert sequence the hardware's previous state
11+may no longer be valid.
12+
13+Please refer to Documentation/devicetree/bindings/reset/reset.txt
14+for common reset controller binding usage.
15+
16+Required properties:
17+- compatible: Should be "st,stih407-picophyreset"
18+- #reset-cells: 1, see below
19+
20+Example:
21+
22+ picophyreset: picophyreset-controller {
23+ compatible = "st,stih407-picophyreset";
24+ #reset-cells = <1>;
25+ };
26+
27+Specifying picophyreset control of devices
28+=======================================
29+
30+Device nodes should specify the reset channel required in their "resets"
31+property, containing a phandle to the picophyreset device node and an
32+index specifying which channel to use, as described in
33+Documentation/devicetree/bindings/reset/reset.txt.
34+
35+Example:
36+
37+ usb2_picophy0: usbpicophy@0 {
38+ resets = <&picophyreset STIH407_PICOPHY0_RESET>;
39+ };
40+
41+Macro definitions for the supported reset channels can be found in:
42+include/dt-bindings/reset-controller/stih407-resets.h
Documentation/devicetree/bindings/rng/apm,rng.txt+17−0
@@ -0,0 +1,17 @@
1+APM X-Gene SoC random number generator.
2+
3+Required properties:
4+
5+- compatible : should be "apm,xgene-rng"
6+- reg : specifies base physical address and size of the registers map
7+- clocks : phandle to clock-controller plus clock-specifier pair
8+- interrupts : specify the fault interrupt for the RNG device
9+
10+Example:
11+
12+ rng: rng@10520000 {
13+ compatible = "apm,xgene-rng";
14+ reg = <0x0 0x10520000 0x0 0x100>;
15+ interrupts = <0x0 0x41 0x4>;
16+ clocks = <&rngpkaclk 0>;
17+ };
Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.txt+23−0
@@ -0,0 +1,23 @@
1+Atmel AT91SAM9260 Real Time Timer
2+
3+Required properties:
4+- compatible: should be: "atmel,at91sam9260-rtt"
5+- reg: should encode the memory region of the RTT controller
6+- interrupts: rtt alarm/event interrupt
7+- clocks: should contain the 32 KHz slow clk that will drive the RTT block.
8+- atmel,rtt-rtc-time-reg: should encode the GPBR register used to store
9+ the time base when the RTT is used as an RTC.
10+ The first cell should point to the GPBR node and the second one
11+ encode the offset within the GPBR block (or in other words, the
12+ GPBR register used to store the time base).
13+
14+
15+Example:
16+
17+rtt@fffffd20 {
18+ compatible = "atmel,at91sam9260-rtt";
19+ reg = <0xfffffd20 0x10>;
20+ interrupts = <1 4 7>;
21+ clocks = <&clk32k>;
22+ atmel,rtt-rtc-time-reg = <&gpbr 0x0>;
23+};
Documentation/devicetree/bindings/rtc/dallas,ds1339.txt+18−0
@@ -0,0 +1,18 @@
1+* Dallas DS1339 I2C Serial Real-Time Clock
2+
3+Required properties:
4+- compatible: Should contain "dallas,ds1339".
5+- reg: I2C address for chip
6+
7+Optional properties:
8+- trickle-resistor-ohms : Selected resistor for trickle charger
9+ Values usable for ds1339 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+ ds1339: rtc@68 {
15+ compatible = "dallas,ds1339";
16+ trickle-resistor-ohms = <250>;
17+ reg = <0x68>;
18+ };
Documentation/devicetree/bindings/rtc/rtc-omap.txt+8−1
@@ -5,11 +5,17 @@ Required properties: · 4 unmodified lines
55 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family.
66 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family.
77 This RTC IP has special WAKE-EN Register to enable
8− Wakeup generation for event Alarm.
8+ Wakeup generation for event Alarm. It can also be
9+ used to control an external PMIC via the
10+ pmic_power_en pin.
911 - reg: Address range of rtc register set
1012 - interrupts: rtc timer, alarm interrupts in order
1113 - interrupt-parent: phandle for the interrupt controller
1214
15+Optional properties:
16+- system-power-controller: whether the rtc is controlling the system power
17+ through pmic_power_en
18+
1319 Example:
1420
1521 rtc@1c23000 {
@@ -18,4 +24,5 @@ rtc@1c23000 { · 2 unmodified lines
1824 interrupts = <19
1925 19>;
2026 interrupt-parent = <&intc>;
27+ system-power-controller;
2128 };
Documentation/devicetree/bindings/rtc/rtc-opal.txt+16−0
@@ -0,0 +1,16 @@
1+IBM OPAL real-time clock
2+------------------------
3+
4+Required properties:
5+- comapatible: Should be "ibm,opal-rtc"
6+
7+Optional properties:
8+- has-tpo: Decides if the wakeup is supported or not.
9+
10+Example:
11+ rtc {
12+ compatible = "ibm,opal-rtc";
13+ has-tpo;
14+ phandle = <0x10000029>;
15+ linux,phandle = <0x10000029>;
16+ };
Documentation/devicetree/bindings/rtc/s3c-rtc.txt+3−0
@@ -3,7 +3,10 @@ · 2 unmodified lines
33 Required properties:
44 - compatible: should be one of the following.
55 * "samsung,s3c2410-rtc" - for controllers compatible with s3c2410 rtc.
6+ * "samsung,s3c2416-rtc" - for controllers compatible with s3c2416 rtc.
7+ * "samsung,s3c2443-rtc" - for controllers compatible with s3c2443 rtc.
68 * "samsung,s3c6410-rtc" - for controllers compatible with s3c6410 rtc.
9+ * "samsung,exynos3250-rtc" - for controllers compatible with exynos3250 rtc.
710 - reg: physical base address of the controller and length of memory mapped
811 region.
912 - interrupts: Two interrupt numbers to the cpu should be specified. First
Documentation/devicetree/bindings/rtc/sun6i-rtc.txt+17−0
@@ -0,0 +1,17 @@
1+* sun6i Real Time Clock
2+
3+RTC controller for the Allwinner A31
4+
5+Required properties:
6+- compatible : Should be "allwinner,sun6i-a31-rtc"
7+- reg : physical base address of the controller and length of
8+ memory mapped region.
9+- interrupts : IRQ lines for the RTC alarm 0 and alarm 1, in that order.
10+
11+Example:
12+
13+rtc: rtc@01f00000 {
14+ compatible = "allwinner,sun6i-a31-rtc";
15+ reg = <0x01f00000 0x54>;
16+ interrupts = <0 40 4>, <0 41 4>;
17+};
Documentation/devicetree/bindings/serial/bcm63xx-uart.txt+30−0
@@ -0,0 +1,30 @@
1+* BCM63xx UART
2+
3+Required properties:
4+
5+- compatible: "brcm,bcm6345-uart"
6+
7+- reg: The base address of the UART register bank.
8+
9+- interrupts: A single interrupt specifier.
10+
11+- clocks: Clock driving the hardware; used to figure out the baud rate
12+ divisor.
13+
14+Example:
15+
16+ uart0: serial@14e00520 {
17+ compatible = "brcm,bcm6345-uart";
18+ reg = <0x14e00520 0x18>;
19+ interrupt-parent = <&periph_intc>;
20+ interrupts = <2>;
21+ clocks = <&periph_clk>;
22+ };
23+
24+ clocks {
25+ periph_clk: periph_clk@0 {
26+ compatible = "fixed-clock";
27+ #clock-cells = <0>;
28+ clock-frequency = <54000000>;
29+ };
30+ };
Documentation/devicetree/bindings/serial/cirrus,clps711x-uart.txt+5−2
@@ -8,7 +8,8 @@ Required properties: · 7 unmodified lines
88 - syscon: Phandle to SYSCON node, which contain UART control bits.
99
1010 Optional properties:
11−- uart-use-ms: Indicate the UART has modem signal (DCD, DSR, CTS).
11+- {rts,cts,dtr,dsr,rng,dcd}-gpios: specify a GPIO for RTS/CTS/DTR/DSR/RI/DCD
12+ line respectively.
1213
1314 Note: Each UART port should have an alias correctly numbered
1415 in "aliases" node.
@@ -24,5 +25,7 @@ Example: · 9 unmodified lines
2425 interrupts = <12 13>;
2526 clocks = <&clks 11>;
2627 syscon = <&syscon1>;
27− uart-use-ms;
28+ cts-gpios = <&sysgpio 0 GPIO_ACTIVE_LOW>;
29+ dsr-gpios = <&sysgpio 1 GPIO_ACTIVE_LOW>;
30+ dcd-gpios = <&sysgpio 2 GPIO_ACTIVE_LOW>;
2831 };
Documentation/devicetree/bindings/serial/fsl-mxs-auart.txt+9−1
@@ -11,8 +11,13 @@ Required properties: · 10 unmodified lines
1111 - dma-names: "rx" for RX channel, "tx" for TX channel.
1212
1313 Optional properties:
14−- fsl,uart-has-rtscts : Indicate the UART has RTS and CTS lines,
14+- fsl,uart-has-rtscts : Indicate the UART has RTS and CTS lines
15+ for hardware flow control,
1516 it also means you enable the DMA support for this UART.
17+- {rts,cts,dtr,dsr,rng,dcd}-gpios: specify a GPIO for RTS/CTS/DTR/DSR/RI/DCD
18+ line respectively. It will use specified PIO instead of the peripheral
19+ function pin for the USART feature.
20+ If unsure, don't specify this property.
1621
1722 Example:
1823 auart0: serial@8006a000 {
@@ -21,6 +26,9 @@ auart0: serial@8006a000 { · 2 unmodified lines
2126 interrupts = <112>;
2227 dmas = <&dma_apbx 8>, <&dma_apbx 9>;
2328 dma-names = "rx", "tx";
29+ cts-gpios = <&gpio1 15 GPIO_ACTIVE_LOW>;
30+ dsr-gpios = <&gpio1 16 GPIO_ACTIVE_LOW>;
31+ dcd-gpios = <&gpio1 17 GPIO_ACTIVE_LOW>;
2432 };
2533
2634 Note: Each auart port should have an alias correctly numbered in "aliases"
Documentation/devicetree/bindings/serial/mtk-uart.txt+22−0
@@ -0,0 +1,22 @@
1+* Mediatek Universal Asynchronous Receiver/Transmitter (UART)
2+
3+Required properties:
4+- compatible should contain:
5+ * "mediatek,mt6589-uart" for MT6589 compatible UARTS
6+ * "mediatek,mt6582-uart" for MT6582 compatible UARTS
7+ * "mediatek,mt6577-uart" for all compatible UARTS (MT6589, MT6582, MT6577)
8+
9+- reg: The base address of the UART register bank.
10+
11+- interrupts: A single interrupt specifier.
12+
13+- clocks: Clock driving the hardware.
14+
15+Example:
16+
17+ uart0: serial@11006000 {
18+ compatible = "mediatek,mt6589-uart", "mediatek,mt6577-uart";
19+ reg = <0x11006000 0x400>;
20+ interrupts = <GIC_SPI 51 IRQ_TYPE_LEVEL_LOW>;
21+ clocks = <&uart_clk>;
22+ };
Documentation/devicetree/bindings/serial/of-serial.txt+2−1
@@ -10,10 +10,12 @@ Required properties: · 9 unmodified lines
1010 - "ns16850"
1111 - "nvidia,tegra20-uart"
1212 - "nxp,lpc3220-uart"
13+ - "ralink,rt2880-uart"
1314 - "ibm,qpace-nwp-serial"
1415 - "altr,16550-FIFO32"
1516 - "altr,16550-FIFO64"
1617 - "altr,16550-FIFO128"
18+ - "fsl,16550-FIFO64"
1719 - "serial" if the port type is unknown.
1820 - reg : offset and length of the register set for the device.
1921 - interrupts : should contain uart interrupt.
@@ -37,7 +39,6 @@ Optional properties: · 17 unmodified lines
3739 - auto-flow-control: one way to enable automatic flow control support. The
3840 driver is allowed to detect support for the capability even without this
3941 property.
40−- has-hw-flow-control: the hardware has flow control capability.
4142
4243 Example:
4344
Documentation/devicetree/bindings/serial/pl011.txt+38−4
@@ -6,12 +6,46 @@ Required properties: · 5 unmodified lines
66 - interrupts: exactly one interrupt specifier
77
88 Optional properties:
9−- pinctrl: When present, must have one state named "sleep"
10− and one state named "default"
11−- clocks: When present, must refer to exactly one clock named
9+- pinctrl:
10+ When present, must have one state named "default",
11+ and may contain a second name named "sleep". The former
12+ state sets up pins for ordinary operation whereas
13+ the latter state will put the associated pins to sleep
14+ when the UART is unused
15+- clocks:
16+ When present, the first clock listed must correspond to
17+ the clock named UARTCLK on the IP block, i.e. the clock
18+ to the external serial line, whereas the second clock
19+ must correspond to the PCLK clocking the internal logic
20+ of the block. Just listing one clock (the first one) is
21+ deprecated.
22+- clocks-names:
23+ When present, the first clock listed must be named
24+ "uartclk" and the second clock listed must be named
1225 "apb_pclk"
13−- dmas: When present, may have one or two dma channels.
26+- dmas:
27+ When present, may have one or two dma channels.
1428 The first one must be named "rx", the second one
1529 must be named "tx".
30+- auto-poll:
31+ Enables polling when using RX DMA.
32+- poll-rate-ms:
33+ Rate at which poll occurs when auto-poll is set,
34+ default 100ms.
35+- poll-timeout-ms:
36+ Poll timeout when auto-poll is set, default
37+ 3000ms.
1638
1739 See also bindings/arm/primecell.txt
40+
41+Example:
42+
43+uart@80120000 {
44+ compatible = "arm,pl011", "arm,primecell";
45+ reg = <0x80120000 0x1000>;
46+ interrupts = <0 11 IRQ_TYPE_LEVEL_HIGH>;
47+ dmas = <&dma 13 0 0x2>, <&dma 13 0 0x0>;
48+ dma-names = "rx", "tx";
49+ clocks = <&foo_clk>, <&bar_clk>;
50+ clock-names = "uartclk", "apb_pclk";
51+};
Documentation/devicetree/bindings/serial/qcom,msm-uartdm.txt+47−22
@@ -27,27 +27,52 @@ Optional properties: · 26 unmodified lines
2727 - dmas: Should contain dma specifiers for transmit and receive channels
2828 - dma-names: Should contain "tx" for transmit and "rx" for receive channels
2929
30+Note: Aliases may be defined to ensure the correct ordering of the UARTs.
31+The alias serialN will result in the UART being assigned port N. If any
32+serialN alias exists, then an alias must exist for each enabled UART. The
33+serialN aliases should be in a .dts file instead of in a .dtsi file.
34+
3035 Examples:
3136
32−A uartdm v1.4 device with dma capabilities.
33−
34−serial@f991e000 {
35− compatible = "qcom,msm-uartdm-v1.4", "qcom,msm-uartdm";
36− reg = <0xf991e000 0x1000>;
37− interrupts = <0 108 0x0>;
38− clocks = <&blsp1_uart2_apps_cxc>, <&blsp1_ahb_cxc>;
39− clock-names = "core", "iface";
40− dmas = <&dma0 0>, <&dma0 1>;
41− dma-names = "tx", "rx";
42−};
43−
44−A uartdm v1.3 device without dma capabilities and part of a GSBI complex.
45−
46−serial@19c40000 {
47− compatible = "qcom,msm-uartdm-v1.3", "qcom,msm-uartdm";
48− reg = <0x19c40000 0x1000>,
49− <0x19c00000 0x1000>;
50− interrupts = <0 195 0x0>;
51− clocks = <&gsbi5_uart_cxc>, <&gsbi5_ahb_cxc>;
52− clock-names = "core", "iface";
53−};
37+- A uartdm v1.4 device with dma capabilities.
38+
39+ serial@f991e000 {
40+ compatible = "qcom,msm-uartdm-v1.4", "qcom,msm-uartdm";
41+ reg = <0xf991e000 0x1000>;
42+ interrupts = <0 108 0x0>;
43+ clocks = <&blsp1_uart2_apps_cxc>, <&blsp1_ahb_cxc>;
44+ clock-names = "core", "iface";
45+ dmas = <&dma0 0>, <&dma0 1>;
46+ dma-names = "tx", "rx";
47+ };
48+
49+- A uartdm v1.3 device without dma capabilities and part of a GSBI complex.
50+
51+ serial@19c40000 {
52+ compatible = "qcom,msm-uartdm-v1.3", "qcom,msm-uartdm";
53+ reg = <0x19c40000 0x1000>,
54+ <0x19c00000 0x1000>;
55+ interrupts = <0 195 0x0>;
56+ clocks = <&gsbi5_uart_cxc>, <&gsbi5_ahb_cxc>;
57+ clock-names = "core", "iface";
58+ };
59+
60+- serialN alias.
61+
62+ aliases {
63+ serial0 = &uarta;
64+ serial1 = &uartc;
65+ serial2 = &uartb;
66+ };
67+
68+ uarta: serial@12490000 {
69+ status = "ok";
70+ };
71+
72+ uartb: serial@16340000 {
73+ status = "ok";
74+ };
75+
76+ uartc: serial@1a240000 {
77+ status = "ok";
78+ };
Documentation/devicetree/bindings/serial/renesas,sci-serial.txt+7−2
@@ -4,8 +4,7 @@ Required properties: · 3 unmodified lines
44
55 - compatible: Must contain one of the following:
66
7− - "renesas,scifa-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFA compatible UART.
8− - "renesas,scifb-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFB compatible UART.
7+ - "renesas,scif-r7s72100" for R7S72100 (RZ/A1H) SCIF compatible UART.
98 - "renesas,scifa-r8a73a4" for R8A73A4 (R-Mobile APE6) SCIFA compatible UART.
109 - "renesas,scifb-r8a73a4" for R8A73A4 (R-Mobile APE6) SCIFB compatible UART.
1110 - "renesas,scifa-r8a7740" for R8A7740 (R-Mobile A1) SCIFA compatible UART.
@@ -20,6 +19,12 @@ Required properties: · 8 unmodified lines
2019 - "renesas,scifa-r8a7791" for R8A7791 (R-Car M2) SCIFA compatible UART.
2120 - "renesas,scifb-r8a7791" for R8A7791 (R-Car M2) SCIFB compatible UART.
2221 - "renesas,hscif-r8a7791" for R8A7791 (R-Car M2) HSCIF compatible UART.
22+ - "renesas,scif-r8a7794" for R8A7794 (R-Car E2) SCIF compatible UART.
23+ - "renesas,scifa-r8a7794" for R8A7794 (R-Car E2) SCIFA compatible UART.
24+ - "renesas,scifb-r8a7794" for R8A7794 (R-Car E2) SCIFB compatible UART.
25+ - "renesas,hscif-r8a7794" for R8A7794 (R-Car E2) HSCIF compatible UART.
26+ - "renesas,scifa-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFA compatible UART.
27+ - "renesas,scifb-sh73a0" for SH73A0 (SH-Mobile AG5) SCIFB compatible UART.
2328 - "renesas,scif" for generic SCIF compatible UART.
2429 - "renesas,scifa" for generic SCIFA compatible UART.
2530 - "renesas,scifb" for generic SCIFB compatible UART.
Documentation/devicetree/bindings/serial/sirf-uart.txt+15−1
@@ -1,7 +1,9 @@
11 * CSR SiRFprimaII/atlasVI Universal Synchronous Asynchronous Receiver/Transmitter *
22
33 Required properties:
4−- compatible : Should be "sirf,prima2-uart" or "sirf, prima2-usp-uart"
4+- compatible : Should be "sirf,prima2-uart", "sirf, prima2-usp-uart",
5+ "sirf,marco-uart" or "sirf,marco-bt-uart" which means
6+ uart located in BT module and used for BT.
57 - reg : Offset and length of the register set for the device
68 - interrupts : Should contain uart interrupt
79 - fifosize : Should define hardware rx/tx fifo size
@@ -31,3 +33,15 @@ usp@b0090000 { · 23 unmodified lines
3133 rts-gpios = <&gpio 15 0>;
3234 cts-gpios = <&gpio 46 0>;
3335 };
36+
37+for uart use in BT module,
38+uart6: uart@11000000 {
39+ cell-index = <6>;
40+ compatible = "sirf,marco-bt-uart", "sirf,marco-uart";
41+ reg = <0x11000000 0x1000>;
42+ interrupts = <0 100 0>;
43+ clocks = <&clks 138>, <&clks 140>, <&clks 141>;
44+ clock-names = "uart", "general", "noc";
45+ fifosize = <128>;
46+ status = "disabled";
47+}
Documentation/devicetree/bindings/serial/via,vt8500-uart.txt+0−17
@@ -1,17 +0,0 @@
1−VIA/Wondermedia VT8500 UART Controller
2−-----------------------------------------------------
3−
4−Required properties:
5−- compatible : "via,vt8500-uart"
6−- reg : Should contain 1 register ranges(address and length)
7−- interrupts : UART interrupt
8−- clocks : phandle to the uart source clock (usually a 24Mhz fixed clock)
9−
10−Example:
11−
12− uart@d8210000 {
13− compatible = "via,vt8500-uart";
14− reg = <0xd8210000 0x1040>;
15− interrupts = <47>;
16− clocks = <&ref24>;
17− };
Documentation/devicetree/bindings/serial/vt8500-uart.txt+2−1
@@ -1,7 +1,8 @@
11 * VIA VT8500 and WonderMedia WM8xxx UART Controller
22
33 Required properties:
4−- compatible: should be "via,vt8500-uart"
4+- compatible: should be "via,vt8500-uart" (for VIA/WonderMedia chips up to and
5+ including WM8850/WM8950), or "wm,wm8880-uart" (for WM8880 and later)
56
67 - reg: base physical address of the controller and length of memory mapped
78 region.
Documentation/devicetree/bindings/soc/fsl/bman-portals.txt+56−0
@@ -0,0 +1,56 @@
1+QorIQ DPAA Buffer Manager Portals Device Tree Binding
2+
3+Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
4+
5+CONTENTS
6+
7+ - BMan Portal
8+ - Example
9+
10+BMan Portal Node
11+
12+Portals are memory mapped interfaces to BMan that allow low-latency, lock-less
13+interaction by software running on processor cores, accelerators and network
14+interfaces with the BMan
15+
16+PROPERTIES
17+
18+- compatible
19+ Usage: Required
20+ Value type: <stringlist>
21+ Definition: Must include "fsl,bman-portal-<hardware revision>"
22+ May include "fsl,<SoC>-bman-portal" or "fsl,bman-portal"
23+
24+- reg
25+ Usage: Required
26+ Value type: <prop-encoded-array>
27+ Definition: Two regions. The first is the cache-enabled region of
28+ the portal. The second is the cache-inhibited region of
29+ the portal
30+
31+- interrupts
32+ Usage: Required
33+ Value type: <prop-encoded-array>
34+ Definition: Standard property
35+
36+EXAMPLE
37+
38+The example below shows a (P4080) BMan portals container/bus node with two portals
39+
40+ bman-portals@ff4000000 {
41+ #address-cells = <1>;
42+ #size-cells = <1>;
43+ compatible = "simple-bus";
44+ ranges = <0 0xf 0xf4000000 0x200000>;
45+
46+ bman-portal@0 {
47+ compatible = "fsl,bman-portal-1.0.0", "fsl,bman-portal";
48+ reg = <0x0 0x4000>, <0x100000 0x1000>;
49+ interrupts = <105 2 0 0>;
50+ };
51+ bman-portal@4000 {
52+ compatible = "fsl,bman-portal-1.0.0", "fsl,bman-portal";
53+ reg = <0x4000 0x4000>, <0x101000 0x1000>;
54+ interrupts = <107 2 0 0>;
55+ };
56+ };
Documentation/devicetree/bindings/soc/fsl/bman.txt+125−0
@@ -0,0 +1,125 @@
1+QorIQ DPAA Buffer Manager Device Tree Bindings
2+
3+Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
4+
5+CONTENTS
6+
7+ - BMan Node
8+ - BMan Private Memory Node
9+ - Example
10+
11+BMan Node
12+
13+The Buffer Manager is part of the Data-Path Acceleration Architecture (DPAA).
14+BMan supports hardware allocation and deallocation of buffers belonging to pools
15+originally created by software with configurable depletion thresholds. This
16+binding covers the CCSR space programming model
17+
18+PROPERTIES
19+
20+- compatible
21+ Usage: Required
22+ Value type: <stringlist>
23+ Definition: Must include "fsl,bman"
24+ May include "fsl,<SoC>-bman"
25+
26+- reg
27+ Usage: Required
28+ Value type: <prop-encoded-array>
29+ Definition: Registers region within the CCSR address space
30+
31+The BMan revision information is located in the BMAN_IP_REV_1/2 registers which
32+are located at offsets 0xbf8 and 0xbfc
33+
34+- interrupts
35+ Usage: Required
36+ Value type: <prop-encoded-array>
37+ Definition: Standard property. The error interrupt
38+
39+- fsl,liodn
40+ Usage: See pamu.txt
41+ Value type: <prop-encoded-array>
42+ Definition: PAMU property used for static LIODN assignment
43+
44+- fsl,iommu-parent
45+ Usage: See pamu.txt
46+ Value type: <phandle>
47+ Definition: PAMU property used for dynamic LIODN assignment
48+
49+ For additional details about the PAMU/LIODN binding(s) see pamu.txt
50+
51+Devices connected to a BMan instance via Direct Connect Portals (DCP) must link
52+to the respective BMan instance
53+
54+- fsl,bman
55+ Usage: Required
56+ Value type: <prop-encoded-array>
57+ Description: List of phandle and DCP index pairs, to the BMan instance
58+ to which this device is connected via the DCP
59+
60+BMan Private Memory Node
61+
62+BMan requires a contiguous range of physical memory used for the backing store
63+for BMan Free Buffer Proxy Records (FBPR). This memory is reserved/allocated as a
64+node under the /reserved-memory node
65+
66+The BMan FBPR memory node must be named "bman-fbpr"
67+
68+PROPERTIES
69+
70+- compatible
71+ Usage: required
72+ Value type: <stringlist>
73+ Definition: Must inclide "fsl,bman-fbpr"
74+
75+The following constraints are relevant to the FBPR private memory:
76+ - The size must be 2^(size + 1), with size = 11..33. That is 4 KiB to
77+ 16 GiB
78+ - The alignment must be a muliptle of the memory size
79+
80+The size of the FBPR must be chosen by observing the hardware features configured
81+via the Reset Configuration Word (RCW) and that are relevant to a specific board
82+(e.g. number of MAC(s) pinned-out, number of offline/host command FMan ports,
83+etc.). The size configured in the DT must reflect the hardware capabilities and
84+not the specific needs of an application
85+
86+For additional details about reserved memory regions see reserved-memory.txt
87+
88+EXAMPLE
89+
90+The example below shows a BMan FBPR dynamic allocation memory node
91+
92+ reserved-memory {
93+ #address-cells = <2>;
94+ #size-cells = <2>;
95+ ranges;
96+
97+ bman_fbpr: bman-fbpr {
98+ compatible = "fsl,bman-fbpr";
99+ alloc-ranges = <0 0 0xf 0xffffffff>;
100+ size = <0 0x1000000>;
101+ alignment = <0 0x1000000>;
102+ };
103+ };
104+
105+The example below shows a (P4080) BMan CCSR-space node
106+
107+ crypto@300000 {
108+ ...
109+ fsl,bman = <&bman, 2>;
110+ ...
111+ };
112+
113+ bman: bman@31a000 {
114+ compatible = "fsl,bman";
115+ reg = <0x31a000 0x1000>;
116+ interrupts = <16 2 1 2>;
117+ fsl,liodn = <0x17>;
118+ memory-region = <&bman_fbpr>;
119+ };
120+
121+ fman@400000 {
122+ ...
123+ fsl,bman = <&bman, 0>;
124+ ...
125+ };
Documentation/devicetree/bindings/soc/fsl/qman-portals.txt+154−0
@@ -0,0 +1,154 @@
1+QorIQ DPAA Queue Manager Portals Device Tree Binding
2+
3+Copyright (C) 2008 - 2014 Freescale Semiconductor Inc.
4+
5+CONTENTS
6+
7+ - QMan Portal
8+ - QMan Pool Channel
9+ - Example
10+
11+QMan Portal Node
12+
13+Portals are memory mapped interfaces to QMan that allow low-latency, lock-less
14+interaction by software running on processor cores, accelerators and network
15+interfaces with the QMan
16+
17+PROPERTIES
18+
19+- compatible
20+ Usage: Required
21+ Value type: <stringlist>
22+ Definition: Must include "fsl,qman-portal-<hardware revision>"
23+ May include "fsl,<SoC>-qman-portal" or "fsl,qman-portal"
24+
25+- reg
26+ Usage: Required
27+ Value type: <prop-encoded-array>
28+ Definition: Two regions. The first is the cache-enabled region of
29+ the portal. The second is the cache-inhibited region of
30+ the portal
31+
32+- interrupts
33+ Usage: Required
34+ Value type: <prop-encoded-array>
35+ Definition: Standard property
36+
37+- fsl,liodn
38+ Usage: See pamu.txt
39+ Value type: <prop-encoded-array>
40+ Definition: Two LIODN(s). DQRR LIODN (DLIODN) and Frame LIODN
41+ (FLIODN)
42+
43+- fsl,iommu-parent
44+ Usage: See pamu.txt
45+ Value type: <phandle>
46+ Definition: PAMU property used for dynamic LIODN assignment
47+
48+ For additional details about the PAMU/LIODN binding(s) see pamu.txt
49+
50+- fsl,qman-channel-id
51+ Usage: Required
52+ Value type: <u32>
53+ Definition: The hardware index of the channel. This can also be
54+ determined by dividing any of the channel's 8 work queue
55+ IDs by 8
56+
57+In addition to these properties the qman-portals should have sub-nodes to
58+represent the HW devices/portals that are connected to the software portal
59+described here
60+
61+The currently supported sub-nodes are:
62+ * fman0
63+ * fman1
64+ * pme
65+ * crypto
66+
67+These subnodes should have the following properties:
68+
69+- fsl,liodn
70+ Usage: See pamu.txt
71+ Value type: <prop-encoded-array>
72+ Definition: PAMU property used for static LIODN assignment
73+
74+- fsl,iommu-parent
75+ Usage: See pamu.txt
76+ Value type: <phandle>
77+ Definition: PAMU property used for dynamic LIODN assignment
78+
79+- dev-handle
80+ Usage: Required
81+ Value type: <phandle>
82+ Definition: The phandle to the particular hardware device that this
83+ portal is connected to.
84+
85+DPAA QMan Pool Channel Nodes
86+
87+Pool Channels are defined with the following properties.
88+
89+PROPERTIES
90+
91+- compatible
92+ Usage: Required
93+ Value type: <stringlist>
94+ Definition: Must include "fsl,qman-pool-channel"
95+ May include "fsl,<SoC>-qman-pool-channel"
96+
97+- fsl,qman-channel-id
98+ Usage: Required
99+ Value type: <u32>
100+ Definition: The hardware index of the channel. This can also be
101+ determined by dividing any of the channel's 8 work queue
102+ IDs by 8
103+
104+EXAMPLE
105+
106+The example below shows a (P4080) QMan portals container/bus node with two portals
107+
108+ qman-portals@ff4200000 {
109+ #address-cells = <1>;
110+ #size-cells = <1>;
111+ compatible = "simple-bus";
112+ ranges = <0 0xf 0xf4200000 0x200000>;
113+
114+ qman-portal@0 {
115+ compatible = "fsl,qman-portal-1.2.0", "fsl,qman-portal";
116+ reg = <0 0x4000>, <0x100000 0x1000>;
117+ interrupts = <104 2 0 0>;

37 more lines aren’t shown here.

Documentation/devicetree/bindings/soc/fsl/qman.txt+165−0

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

Documentation/devicetree/bindings/soc/ti/keystone-navigator-dma.txt+111−0

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

Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt+232−0

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

Documentation/devicetree/bindings/sound/adi,ssm2602.txt+19−0

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

Documentation/devicetree/bindings/sound/arndale.txt+24−0

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

Documentation/devicetree/bindings/sound/cs35l32.txt+62−0

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

Documentation/devicetree/bindings/sound/davinci-mcasp-audio.txt+1−1

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

Documentation/devicetree/bindings/sound/es8328.txt+38−0

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

Documentation/devicetree/bindings/sound/eukrea-tlv320.txt+10−5

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

Documentation/devicetree/bindings/sound/fsl,esai.txt+23−20

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

Documentation/devicetree/bindings/sound/fsl,spdif.txt+18−19

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

Documentation/devicetree/bindings/sound/fsl,ssi.txt+1−7

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

Documentation/devicetree/bindings/sound/fsl-asoc-card.txt+82−0

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

Documentation/devicetree/bindings/sound/fsl-sai.txt+50−20

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

Documentation/devicetree/bindings/sound/imx-audio-es8328.txt+60−0

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

Documentation/devicetree/bindings/sound/imx-audio-sgtl5000.txt+34−27

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

Documentation/devicetree/bindings/sound/imx-audio-spdif.txt+12−10

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

Documentation/devicetree/bindings/sound/imx-audio-wm8962.txt+26−19

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

Documentation/devicetree/bindings/sound/imx-audmux.txt+14−8

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

Documentation/devicetree/bindings/sound/max98090.txt+2−0

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

Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max98090.txt+1−0

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

Documentation/devicetree/bindings/sound/renesas,fsi.txt+7−2

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

Documentation/devicetree/bindings/sound/renesas,rsnd.txt+7−3

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

Documentation/devicetree/bindings/sound/rt5631.txt+48−0

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

Documentation/devicetree/bindings/sound/rt5677.txt+76−0

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

Documentation/devicetree/bindings/sound/samsung-i2s.txt+11−4

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

Documentation/devicetree/bindings/sound/sgtl5000.txt+23−0

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

Documentation/devicetree/bindings/sound/simple-card.txt+4−0

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

Documentation/devicetree/bindings/sound/ssm4567.txt+15−0

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

Documentation/devicetree/bindings/sound/st,sta350.txt+1−1

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

Documentation/devicetree/bindings/sound/ts3a227e.txt+26−0

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

Documentation/devicetree/bindings/sound/wm8960.txt+31−0

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

Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt+5−0

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

Documentation/devicetree/bindings/spi/sh-msiof.txt+19−4

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

Documentation/devicetree/bindings/spi/spi-davinci.txt+30−0

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

Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt+6−1

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

Documentation/devicetree/bindings/spi/spi-gpio.txt+4−2

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

Documentation/devicetree/bindings/spi/spi-img-spfi.txt+37−0

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

Documentation/devicetree/bindings/spi/spi-meson.txt+22−0

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

Documentation/devicetree/bindings/spi/spi-orion.txt+1−1

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

Documentation/devicetree/bindings/spi/spi-rspi.txt+9−1

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

Documentation/devicetree/bindings/spi/spi-samsung.txt+1−1

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

Documentation/devicetree/bindings/submitting-patches.txt+3−0

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

Documentation/devicetree/bindings/thermal/armada-thermal.txt+0−8

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

Documentation/devicetree/bindings/thermal/imx-thermal.txt+4−1

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

Documentation/devicetree/bindings/thermal/rcar-thermal.txt+4−1

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

Documentation/devicetree/bindings/thermal/rockchip-thermal.txt+68−0

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

Documentation/devicetree/bindings/thermal/tegra-soctherm.txt+53−0

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

Documentation/devicetree/bindings/timer/amlogic,meson6-timer.txt+15−0

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

Documentation/devicetree/bindings/timer/marvell,armada-370-xp-timer.txt+6−3

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

Documentation/devicetree/bindings/timer/renesas,cmt.txt+38−6

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

Documentation/devicetree/bindings/timer/renesas,mtu2.txt+6−3

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

Documentation/devicetree/bindings/timer/renesas,tmu.txt+8−3

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

Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt+41−0

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

Documentation/devicetree/bindings/unittest.txt+14−0

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

Documentation/devicetree/bindings/usb/ci-hdrc-imx.txt+2−0

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

Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt+24−0

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

Documentation/devicetree/bindings/usb/dwc2.txt+5−0

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

Documentation/devicetree/bindings/usb/dwc3-st.txt+68−0

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

Documentation/devicetree/bindings/usb/dwc3.txt+23−0

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

Documentation/devicetree/bindings/usb/ehci-st.txt+39−0

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

Documentation/devicetree/bindings/usb/exynos-usb.txt+4−2

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

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

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

Documentation/devicetree/bindings/usb/ohci-st.txt+37−0

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

Documentation/devicetree/bindings/usb/pxa-usb.txt+22−0

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

Documentation/devicetree/bindings/usb/qcom,dwc3.txt+66−0

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

Documentation/devicetree/bindings/usb/renesas_usbhs.txt+24−0

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

Documentation/devicetree/bindings/usb/udc-xilinx.txt+18−0

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

Documentation/devicetree/bindings/usb/usb-ohci.txt+2−0

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

Documentation/devicetree/bindings/usb/usb3503.txt+2−2

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

Documentation/devicetree/bindings/usb/usbmisc-imx.txt+1−0

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

Documentation/devicetree/bindings/vendor-prefixes.txt+28−2

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

Documentation/devicetree/bindings/video/adi,adv7123.txt+50−0

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

Documentation/devicetree/bindings/video/adi,adv7511.txt+88−0

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

Documentation/devicetree/bindings/video/atmel,lcdc.txt+5−2

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

Documentation/devicetree/bindings/video/backlight/lp855x.txt+2−0

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

Documentation/devicetree/bindings/video/exynos_dsim.txt+2−0

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

Documentation/devicetree/bindings/video/fsl,imx-fb.txt+1−1

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

Documentation/devicetree/bindings/video/renesas,du.txt+84−0

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

Documentation/devicetree/bindings/video/rockchip-drm.txt+19−0

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

Documentation/devicetree/bindings/video/rockchip-vop.txt+58−0

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

Documentation/devicetree/bindings/video/samsung-fimd.txt+2−0

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

Documentation/devicetree/bindings/video/simple-framebuffer-sunxi.txt+33−0

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

Documentation/devicetree/bindings/video/simple-framebuffer.txt+64−4

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

Documentation/devicetree/bindings/video/thine,thc63lvdm83d+50−0

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

Documentation/devicetree/bindings/video/vga-connector.txt+36−0

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

Documentation/devicetree/bindings/w1/omap-hdq.txt+17−0

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

Documentation/devicetree/bindings/watchdog/cadence-wdt.txt+24−0

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

Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.txt+2−1

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

Documentation/devicetree/bindings/watchdog/marvel.txt+13−0

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

Documentation/devicetree/bindings/watchdog/meson6-wdt.txt+13−0

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

Documentation/devicetree/bindings/watchdog/qcom-wdt.txt+24−0

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

Documentation/devicetree/bindings/watchdog/samsung-wdt.txt+1−0

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

Documentation/devicetree/bindings/xillybus/xillybus.txtrenamed from Documentation/devicetree/bindings/staging/xillybus.txt+0−0

File renamed without changes.

Documentation/devicetree/booting-without-of.txt+53−0

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

Documentation/devicetree/dynamic-resolution-notes.txt+25−0

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

Documentation/devicetree/of_selftest.txt+15−29

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

Documentation/devicetree/overlay-notes.txt+133−0

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

Documentation/devicetree/todo.txt+0−1

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

Documentation/dmaengine.txt+0−199

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

Documentation/dmaengine/client.txt+199−0

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

Documentation/dmaengine/dmatest.txtrenamed from Documentation/dmatest.txt+0−0

File renamed without changes.

Documentation/dmaengine/provider.txt+366−0

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

Documentation/driver-model/devres.txt+7−0

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

Documentation/dvb/get_dvb_firmware+13−11

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

Documentation/email-clients.txt+11−0

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

Documentation/filesystems/.gitignore+1−0

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

Documentation/filesystems/Locking+8−5

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

Documentation/filesystems/Makefile+1−2

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

Documentation/filesystems/autofs4.txt+520−0

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

Documentation/filesystems/debugfs.txt+1−1

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

Documentation/filesystems/f2fs.txt+17−3

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

Documentation/filesystems/nfs/Exporting+5−18

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

Documentation/filesystems/ntfs.txt+0−268

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

Documentation/filesystems/overlayfs.txt+198−0

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

Documentation/filesystems/porting+8−0

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

Documentation/filesystems/proc.txt+1−1

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

Documentation/filesystems/seq_file.txt+13−9

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

Documentation/filesystems/squashfs.txt+4−4

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

Documentation/filesystems/vfs.txt+13−5

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

Documentation/gpio/consumer.txt+45−0

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

Documentation/gpio/driver.txt+6−4

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

Documentation/hid/uhid.txt+92−87

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

Documentation/hwmon/k10temp+1−1

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

Documentation/hwmon/lm75+5−0

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

Documentation/hwmon/lm95234+10−5

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

Documentation/hwmon/lm95245+9−5

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

Documentation/hwmon/menf21bmc+50−0

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

Documentation/hwmon/nct6775+13−1

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

Documentation/hwmon/nct7802+32−0

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

Documentation/hwmon/tmp401+6−2

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

Documentation/i2c/busses/i2c-i801+2−0

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

Documentation/i2c/upgrading-clients+2−4

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

Documentation/i2c/writing-clients+4−4

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

Documentation/ia64/Makefile+0−3

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

Documentation/ia64/kvm.txt+0−83

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

Documentation/input/elantech.txt+75−6

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

Documentation/input/xpad.txt+83−40

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

Documentation/ioctl/ioctl-number.txt+1−0

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

Documentation/kbuild/makefiles.txt+35−59

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

Documentation/kdump/kdump.txt+7−0

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

Documentation/kernel-parameters.txt+221−25

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

Documentation/kmemleak.txt+5−1

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

Documentation/kobject.txt+1−1

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

Documentation/kprobes.txt+1−0

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

Documentation/kselftest.txt+69−0

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

Documentation/laptops/.gitignore+2−0

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

Documentation/laptops/Makefile+1−4

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

Documentation/local_ops.txt+9−4

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

Documentation/locking/lglock.txt+166−0

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

Documentation/locking/lockdep-design.txtrenamed from Documentation/lockdep-design.txt+0−0

File renamed without changes.

Documentation/locking/lockstat.txtrenamed from Documentation/lockstat.txt+1−1

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

Documentation/locking/locktorture.txt+147−0

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

Documentation/locking/mutex-design.txtrenamed from Documentation/mutex-design.txt+3−3

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

Documentation/locking/rt-mutex-design.txtrenamed from Documentation/rt-mutex-design.txt+0−0

File renamed without changes.

Documentation/locking/rt-mutex.txtrenamed from Documentation/rt-mutex.txt+0−0

File renamed without changes.

Documentation/locking/spinlocks.txtrenamed from Documentation/spinlocks.txt+7−7

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

Documentation/locking/ww-mutex-design.txtrenamed from Documentation/ww-mutex-design.txt+0−0

File renamed without changes.

Documentation/lockup-watchdogs.txt+1−1

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

Documentation/lzo.txt+164−0

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

Documentation/mailbox.txt+122−0

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

Documentation/memory-barriers.txt+145−76

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

Documentation/memory-hotplug.txt+10−1

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

Documentation/mic/Makefile+1−0

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

Documentation/mic/mpssd/Makefile+12−12

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

Documentation/mic/mpssd/mpssd.c+3−2

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

Documentation/mips/AU1xxx_IDE.README+1−1

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

Documentation/misc-devices/Makefile+1−0

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

Documentation/misc-devices/mei/Makefile+0−3

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

Documentation/networking/Makefile+1−7

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

Documentation/networking/bonding.txt+2−5

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

Documentation/networking/dctcp.txt+43−0

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

Documentation/networking/fib_trie.txt+2−2

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

Documentation/networking/filter.txt+275−6

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

Documentation/networking/ip-sysctl.txt+68−15

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

Documentation/networking/ipvlan.txt+107−0

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

Documentation/networking/ixgbe.txt+1−1

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

Documentation/networking/pktgen.txt+3−0

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

Documentation/networking/stmmac.txt+65−67

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

Documentation/networking/switchdev.txt+59−0

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

Documentation/networking/timestamping.txt+303−82

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

Documentation/networking/timestamping/.gitignore+1−0

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

Documentation/networking/timestamping/Makefile+6−6

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

Documentation/networking/timestamping/txtimestamp.c+535−0

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

Documentation/nios2/README+23−0

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

Documentation/pcmcia/Makefile+0−3

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

Documentation/phy.txt+16−44

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

Documentation/pinctrl.txt+2−12

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

Documentation/power/charger-manager.txt+1−1

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

Documentation/power/pm_qos_interface.txt+3−1

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

Documentation/power/power_supply_class.txt+6−0

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

Documentation/power/runtime_pm.txt+7−3

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

Documentation/power/suspend-and-interrupts.txt+123−0

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

Documentation/power/userland-swsusp.txt+1−1

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

Documentation/powerpc/00-INDEX+2−0

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

Documentation/powerpc/cxl.txt+379−0

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

Documentation/prctl/.gitignore+3−0

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

Documentation/prctl/Makefile+8−0

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

Documentation/prctl/disable-tsc-ctxt-sw-stress-test.c+6−5

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

Documentation/prctl/disable-tsc-on-off-stress-test.c+4−3

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

Documentation/prctl/disable-tsc-test.c+3−2

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

Documentation/printk-formats.txt+32−0

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

Documentation/ptp/.gitignore+1−0

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

Documentation/ptp/Makefile+8−0

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

Documentation/ptp/testptp.c+3−3

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

Documentation/ramoops.txt+11−2

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

Documentation/s390/Debugging390.txt+61−401

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

Documentation/scheduler/sched-deadline.txt+292−48

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

Documentation/scsi/ChangeLog.megaraid_sas+14−0

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

Documentation/scsi/libsas.txt+4−78

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

Documentation/scsi/osd.txt+1−2

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

Documentation/scsi/scsi_eh.txt+2−2

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

Documentation/scsi/scsi_mid_low_api.txt+13−53

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

Documentation/scsi/st.txt+5−3

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

Documentation/scsi/wd719x.txt+21−0

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

Documentation/security/IMA-templates.txt+14−15

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

Documentation/security/keys.txt+52−13

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

Documentation/serial/driver+6−2

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

Documentation/serial/serial-rs485.txt+1−1

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

Documentation/serial/tty.txt+2−2

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

Documentation/sound/alsa/ControlNames.txt+27−5

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

Documentation/sound/alsa/HD-Audio-Models.txt+2−6

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

Documentation/sound/alsa/Procfile.txt+4−13

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

Documentation/spi/Makefile+0−3

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

Documentation/spi/spi-summary+3−3

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

Documentation/sysctl/kernel.txt+34−18

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

Documentation/sysctl/net.txt+46−4

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

Documentation/sysfs-rules.txt+21−0

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

Documentation/target/tcmu-design.txt+378−0

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

Documentation/this_cpu_ops.txt+0−2

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

Documentation/timers/.gitignore+1−0

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

Documentation/timers/Makefile+0−3

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

Documentation/trace/coresight.txt+299−0

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

Documentation/trace/ftrace.txt+12−3

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

Documentation/usb/WUSB-Design-overview.txt+7−16

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

Documentation/usb/gadget_configfs.txt+1−1

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

Documentation/usb/gadget_hid.txt+7−0

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

Documentation/usb/hotplug.txt+1−1

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

Documentation/usb/power-management.txt+9−8

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

Documentation/usb/usb-serial.txt+1−1

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

Documentation/vDSO/.gitignore+2−0

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

Documentation/vDSO/Makefile+15−0

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

Documentation/vDSO/vdso_standalone_test_x86.c+1−1

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

Documentation/video4linux/.gitignore+0−1

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

Documentation/video4linux/CARDLIST.cx23885+2−0

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

Documentation/video4linux/CARDLIST.em28xx+1−0

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

Documentation/video4linux/CARDLIST.saa7134+1−0

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

Documentation/video4linux/Makefile+1−0

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

Documentation/video4linux/soc-camera.txt+1−1

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

Documentation/video4linux/vivid.txt+1124−0

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

Documentation/virtual/kvm/api.txt+190−100

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

Documentation/virtual/kvm/devices/arm-vgic.txt+10−0

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

Documentation/virtual/kvm/devices/vm.txt+5−5

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

Documentation/virtual/kvm/mmu.txt+14−0

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

Documentation/virtual/kvm/msr.txt+1−1

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

Documentation/vm/hugetlbpage.txt+3−3

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

Documentation/vm/page_owner.txt+81−0

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

Documentation/watchdog/Makefile+1−0

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

Documentation/watchdog/src/Makefile+0−3

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

Documentation/x86/entry_64.txt+5−2

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

Documentation/x86/intel_mpx.txt+244−0

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

Documentation/x86/x86_64/mm.txt+1−1

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

Documentation/xillybus.txtrenamed from drivers/staging/xillybus/README+0−0

File renamed without changes.

MAINTAINERS+626−202

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

Makefile+69−63

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

arch/Kconfig+11−0

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

arch/alpha/include/asm/Kbuild+2−1

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

arch/alpha/include/asm/atomic.h+82−135

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

arch/alpha/include/asm/barrier.h+51−0

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

arch/alpha/include/asm/sections.h+0−7

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

arch/alpha/include/asm/syscall.h+11−0

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

arch/alpha/include/uapi/asm/ioctls.h+2−0

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

arch/alpha/include/uapi/asm/socket.h+5−0

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

arch/alpha/kernel/osf_sys.c+14−16

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

arch/alpha/kernel/perf_event.c+8−8

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

arch/alpha/kernel/ptrace.c+1−1

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

arch/alpha/kernel/time.c+3−3

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

arch/arc/Kconfig+3−4

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

arch/arc/Makefile+2−17

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

arch/arc/boot/dts/angel4.dts+0−5

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

arch/arc/boot/dts/nsimosci.dts+9−14

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

arch/arc/configs/fpga_defconfig+0−68

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

arch/arc/configs/fpga_noramfs_defconfig+0−64

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

arch/arc/configs/nsim_700_defconfig+67−0

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

arch/arc/configs/nsimosci_defconfig+0−1

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

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

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

arch/arc/include/asm/arcregs.h+53−36

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

arch/arc/include/asm/atomic.h+63−125

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

arch/arc/include/asm/bitops.h+0−4

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

arch/arc/include/asm/bug.h+3−4

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

arch/arc/include/asm/cache.h+1−1

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

arch/arc/include/asm/current.h+0−4

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

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

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

arch/arc/include/asm/irqflags.h+9−4

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

arch/arc/include/asm/kgdb.h+18−14

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

arch/arc/include/asm/processor.h+9−4

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

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

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

arch/arc/include/asm/smp.h+9−1

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

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

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

arch/arc/include/asm/syscalls.h+0−4

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

arch/arc/include/asm/thread_info.h+0−4

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

arch/arc/include/asm/unaligned.h+1−1

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

arch/arc/kernel/Makefile+1−1

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

arch/arc/kernel/disasm.c+2−2

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

arch/arc/kernel/head.S+0−10

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

arch/arc/kernel/kgdb.c+0−5

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

arch/arc/kernel/perf_event.c+10−12

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

arch/arc/kernel/setup.c+133−139

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

arch/arc/kernel/smp.c+3−1

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

arch/arc/mm/cache_arc700.c+5−9

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

arch/arc/mm/tlb.c+3−5

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

arch/arc/plat-arcfpga/Kconfig+1−12

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

arch/arc/plat-arcfpga/include/plat/irq.h+0−27

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

arch/arc/plat-arcfpga/include/plat/memmap.h+0−29

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

arch/arc/plat-arcfpga/platform.c+9−52

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

arch/arc/plat-arcfpga/smp.c+2−1

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

arch/arc/plat-tb10x/Kconfig+0−1

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

arch/arc/plat-tb10x/tb10x.c+0−13

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

arch/arm/Kconfig+32−24

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

arch/arm/Kconfig.debug+279−27

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

arch/arm/Makefile+8−5

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

arch/arm/boot/bootp/Makefile+2−0

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

arch/arm/boot/compressed/Makefile+2−0

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

arch/arm/boot/compressed/head.S+16−4

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

arch/arm/boot/dts/Makefile+87−31

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

arch/arm/boot/dts/am335x-bone-common.dtsi+5−3

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

arch/arm/boot/dts/am335x-bone.dts+5−0

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

arch/arm/boot/dts/am335x-boneblack.dts+9−0

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

arch/arm/boot/dts/am335x-evm.dts+16−3

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

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

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

arch/arm/boot/dts/am335x-lxm.dts+362−0

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

arch/arm/boot/dts/am33xx.dtsi+38−14

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

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

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

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

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

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

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

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

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

arch/arm/boot/dts/am57xx-beagle-x15.dts+405−0

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

arch/arm/boot/dts/arm-realview-pb1176.dts+412−0

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

arch/arm/boot/dts/armada-370-db.dts+58−30

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

arch/arm/boot/dts/armada-370-mirabox.dts+19−12

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

arch/arm/boot/dts/armada-370-netgear-rn102.dts+60−51

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

arch/arm/boot/dts/armada-370-netgear-rn104.dts+43−33

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

arch/arm/boot/dts/armada-370-rd.dts+90−6

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

arch/arm/boot/dts/armada-370-synology-ds213j.dts+316−0

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

arch/arm/boot/dts/armada-370-xp.dtsi+12−6

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

arch/arm/boot/dts/armada-370.dtsi+128−47

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

arch/arm/boot/dts/armada-375.dtsi+27−2

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

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

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

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

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

arch/arm/boot/dts/armada-xp-axpwifiap.dts+18−39

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

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

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

arch/arm/boot/dts/armada-xp-lenovo-ix4-300d.dts+42−33

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

arch/arm/boot/dts/armada-xp-mv78230.dtsi+4−11

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

arch/arm/boot/dts/armada-xp-mv78260.dtsi+4−11

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

arch/arm/boot/dts/armada-xp-mv78460.dtsi+4−11

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

arch/arm/boot/dts/armada-xp-netgear-rn2120.dts+91−81

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

arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts+8−6

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

arch/arm/boot/dts/armada-xp-synology-ds414.dts+330−0

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

arch/arm/boot/dts/armada-xp.dtsi+69−2

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

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

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

arch/arm/boot/dts/at91sam9260.dtsi+14−0

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

arch/arm/boot/dts/at91sam9261.dtsi+14−0

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

arch/arm/boot/dts/at91sam9263.dtsi+52−5

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

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

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

arch/arm/boot/dts/at91sam9g20ek_common.dtsi+14−0

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

arch/arm/boot/dts/at91sam9g45.dtsi+96−4

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

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

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

arch/arm/boot/dts/at91sam9n12.dtsi+2−0

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

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

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

arch/arm/boot/dts/at91sam9rl.dtsi+23−2

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

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

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

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

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

arch/arm/boot/dts/at91sam9x5.dtsi+15−1

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

arch/arm/boot/dts/at91sam9x5_can.dtsi+45−5

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

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

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

arch/arm/boot/dts/atlas6.dtsi+15−0

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

arch/arm/boot/dts/bcm-cygnus-clock.dtsi+91−0

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

arch/arm/boot/dts/bcm-cygnus.dtsi+140−0

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

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

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

arch/arm/boot/dts/bcm2835-rpi-b.dts+6−40

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

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

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

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

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

arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts+64−0

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

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

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

arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts+84−0

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

arch/arm/boot/dts/bcm47081-asus-rt-n18u.dts+78−0

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

arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dts+57−0

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

arch/arm/boot/dts/bcm47081.dtsi+26−0

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

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

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

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

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

arch/arm/boot/dts/bcm911360_entphn.dts+53−0

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

arch/arm/boot/dts/bcm911360k.dts+53−0

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

arch/arm/boot/dts/bcm958300k.dts+53−0

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

arch/arm/boot/dts/bcm963138dvt.dts+30−0

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

arch/arm/boot/dts/berlin2-sony-nsz-gs7.dts+16−0

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

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

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

arch/arm/boot/dts/berlin2cd-google-chromecast.dts+30−0

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

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

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

arch/arm/boot/dts/berlin2q-marvell-dmp.dts+65−0

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

arch/arm/boot/dts/berlin2q.dtsi+112−1

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

arch/arm/boot/dts/cros-adc-thermistors.dtsi+44−0

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

arch/arm/boot/dts/da850-evm.dts+72−0

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

arch/arm/boot/dts/da850.dtsi+19−0

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

arch/arm/boot/dts/dra7-evm.dts+137−2

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

arch/arm/boot/dts/dra7.dtsi+194−35

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

arch/arm/boot/dts/dra72-evm.dts+439−0

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

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

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

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

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

arch/arm/boot/dts/dra7xx-clocks.dtsi+3−3

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

arch/arm/boot/dts/emev2-kzm9d.dts+32−31

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

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

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

arch/arm/boot/dts/exynos3250-monk.dts+579−0

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

arch/arm/boot/dts/exynos3250-pinctrl.dtsi+16−0

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

arch/arm/boot/dts/exynos3250-rinato.dts+682−0

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

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

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

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

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

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

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

arch/arm/boot/dts/exynos4210-universal_c210.dts+16−0

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

arch/arm/boot/dts/exynos4210.dtsi+17−0

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

arch/arm/boot/dts/exynos4212.dtsi+17−0

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

arch/arm/boot/dts/exynos4412-odroid-common.dtsi+28−6

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

arch/arm/boot/dts/exynos4412-origen.dts+2−6

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

arch/arm/boot/dts/exynos4412-trats2.dts+406−12

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

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

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

arch/arm/boot/dts/exynos4415-pinctrl.dtsi+573−0

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

arch/arm/boot/dts/exynos4415.dtsi+604−0

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

arch/arm/boot/dts/exynos4x12-pinctrl.dtsi+17−1

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

arch/arm/boot/dts/exynos4x12.dtsi+12−1

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

arch/arm/boot/dts/exynos5250-arndale.dts+450−465

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

arch/arm/boot/dts/exynos5250-cros-common.dtsi+0−164

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

arch/arm/boot/dts/exynos5250-smdk5250.dts+311−315

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

arch/arm/boot/dts/exynos5250-snow.dts+277−154

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

arch/arm/boot/dts/exynos5250-spring.dts+566−0

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

arch/arm/boot/dts/exynos5250.dtsi+15−25

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

arch/arm/boot/dts/exynos5260-xyref5260.dts+5−13

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

arch/arm/boot/dts/exynos5410-smdk5410.dts+5−13

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

arch/arm/boot/dts/exynos5420-arndale-octa.dts+10−13

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

arch/arm/boot/dts/exynos5420-peach-pit.dts+459−36

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

arch/arm/boot/dts/exynos5420-smdk5420.dts+4−12

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

arch/arm/boot/dts/exynos5420.dtsi+8−3

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

arch/arm/boot/dts/exynos5800-peach-pi.dts+449−36

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

arch/arm/boot/dts/hip04-d01.dts+32−0

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

arch/arm/boot/dts/hip04.dtsi+984−0

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

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

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

arch/arm/boot/dts/hisi-x5hd2.dtsi+388−2

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

arch/arm/boot/dts/imx1-ads.dts+152−0

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

arch/arm/boot/dts/imx1-apf9328.dts+129−0

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

arch/arm/boot/dts/imx1-pinfunc.h+302−0

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

arch/arm/boot/dts/imx1.dtsi+266−0

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

arch/arm/boot/dts/imx23-evk.dts+2−2

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

arch/arm/boot/dts/imx25-pinfunc.h+31−2

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

arch/arm/boot/dts/imx25.dtsi+3−1

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

arch/arm/boot/dts/imx27-apf27dev.dts+17−0

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

arch/arm/boot/dts/imx28-apf28dev.dts+2−2

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

arch/arm/boot/dts/imx28-apx4devkit.dts+2−2

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

arch/arm/boot/dts/imx28-cfa10049.dts+2−2

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

arch/arm/boot/dts/imx28-cfa10055.dts+2−2

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

arch/arm/boot/dts/imx28-cfa10056.dts+2−2

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

arch/arm/boot/dts/imx28-cfa10057.dts+2−2

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

arch/arm/boot/dts/imx28-cfa10058.dts+2−2

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

arch/arm/boot/dts/imx28-evk.dts+2−3

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

arch/arm/boot/dts/imx28-m28cu3.dts+2−2

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

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

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

arch/arm/boot/dts/imx28-tx28.dts+84−23

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

arch/arm/boot/dts/imx28.dtsi+43−0

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

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

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

arch/arm/boot/dts/imx50.dtsi+2−0

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

arch/arm/boot/dts/imx51.dtsi+12−3

This diff is large: its 45 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.dtsi+29−4

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

arch/arm/boot/dts/imx6dl-gw552x.dts+20−0

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

arch/arm/boot/dts/imx6dl-hummingboard.dts+5−198

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

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

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

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

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

arch/arm/boot/dts/imx6q-gw552x.dts+24−0

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

arch/arm/boot/dts/imx6q-hummingboard.dts+21−0

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

arch/arm/boot/dts/imx6q-tbs2910.dts+432−0

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

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

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

arch/arm/boot/dts/imx6qdl-gw51xx.dtsi+73−119

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

arch/arm/boot/dts/imx6qdl-gw52xx.dtsi+129−184

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

arch/arm/boot/dts/imx6qdl-gw53xx.dtsi+122−215

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

arch/arm/boot/dts/imx6qdl-gw54xx.dtsi+124−152

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

arch/arm/boot/dts/imx6qdl-gw552x.dtsi+267−0

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

arch/arm/boot/dts/imx6qdl-hummingboard.dtsi+200−0

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

arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi+38−0

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

arch/arm/boot/dts/imx6qdl-phytec-pbab01.dtsi+105−26

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

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

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

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

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

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

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

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

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

arch/arm/boot/dts/imx6sl-evk.dts+102−6

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

arch/arm/boot/dts/imx6sl.dtsi+33−4

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

arch/arm/boot/dts/imx6sx-sdb.dts+159−0

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

arch/arm/boot/dts/imx6sx.dtsi+15−2

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

arch/arm/boot/dts/integrator.dtsi+47−1

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

arch/arm/boot/dts/k2e-evm.dts+12−0

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

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

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

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

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

arch/arm/boot/dts/k2l-evm.dts+12−0

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

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

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

arch/arm/boot/dts/keystone.dtsi+54−1

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

arch/arm/boot/dts/kirkwood-dir665.dts+278−0

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

arch/arm/boot/dts/kirkwood-mv88f6281gtw-ge.dts+6−10

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

arch/arm/boot/dts/kirkwood-rd88f6281-a.dts+43−0

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

arch/arm/boot/dts/kirkwood-rd88f6281-a0.dts+0−26

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

arch/arm/boot/dts/kirkwood-rd88f6281-a1.dts+0−31

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

arch/arm/boot/dts/kirkwood-rd88f6281-z0.dts+35−0

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

arch/arm/boot/dts/kirkwood-rd88f6281.dtsi+5−22

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

arch/arm/boot/dts/kirkwood-synology.dtsi+1−1

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

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

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

arch/arm/boot/dts/ls1021a-qds.dts+240−0

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

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

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

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

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

arch/arm/boot/dts/meson.dtsi+154−0

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

arch/arm/boot/dts/meson6-atv1200.dts+66−0

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

arch/arm/boot/dts/meson6.dtsi+80−0

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

arch/arm/boot/dts/meson8.dtsi+92−0

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

arch/arm/boot/dts/mmp2-brownstone.dts+1−1

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

arch/arm/boot/dts/mmp2.dtsi+28−1

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

arch/arm/boot/dts/mt6589-aquaris5.dts+5−0

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

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

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

arch/arm/boot/dts/mt6592-evb.dts+26−0

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

arch/arm/boot/dts/mt6592.dtsi+98−0

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

arch/arm/boot/dts/mt8127-moose.dts+25−0

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

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

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

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

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

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

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

arch/arm/boot/dts/omap-gpmc-smsc911x.dtsi+23−18

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

arch/arm/boot/dts/omap-zoom-common.dtsi+60−2

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

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

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

arch/arm/boot/dts/omap2420-n810.dts+7−0

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

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

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

arch/arm/boot/dts/omap2420.dtsi+9−0

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

arch/arm/boot/dts/omap2430-sdp.dts+26−2

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

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

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

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

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

arch/arm/boot/dts/omap3-beagle.dts+28−0

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

arch/arm/boot/dts/omap3-cm-t3517.dts+11−0

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

arch/arm/boot/dts/omap3-cm-t3530.dts+11−0

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

arch/arm/boot/dts/omap3-cm-t3730.dts+24−0

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

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

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

arch/arm/boot/dts/omap3-cm-t3x30.dtsi+35−0

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

arch/arm/boot/dts/omap3-devkit8000.dts+2−2

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

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

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

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

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

arch/arm/boot/dts/omap3-gta04.dts+0−311

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

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

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

arch/arm/boot/dts/omap3-gta04a3.dts+48−0

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

arch/arm/boot/dts/omap3-gta04a4.dts+13−0

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

arch/arm/boot/dts/omap3-gta04a5.dts+17−0

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

arch/arm/boot/dts/omap3-ha-common.dtsi+88−0

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

arch/arm/boot/dts/omap3-ha-lcd.dts+165−0

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

arch/arm/boot/dts/omap3-ha.dts+28−0

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

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

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

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

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

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

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

arch/arm/boot/dts/omap3-igep0020.dts+36−249

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

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

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

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

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

arch/arm/boot/dts/omap3-igep0030.dts+44−79

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

arch/arm/boot/dts/omap3-ldp.dts+29−2

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

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

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

arch/arm/boot/dts/omap3-n900.dts+100−10

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

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

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

arch/arm/boot/dts/omap3-overo-common-peripherals.dtsi+3−2

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

arch/arm/boot/dts/omap3-sb-t35.dtsi+108−18

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

arch/arm/boot/dts/omap3-sbc-t3517.dts+15−0

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

arch/arm/boot/dts/omap3-sbc-t3530.dts+15−0

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

arch/arm/boot/dts/omap3-sbc-t3730.dts+15−0

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

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

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

arch/arm/boot/dts/omap3-thunder.dts+129−0

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

arch/arm/boot/dts/omap3.dtsi+8−3

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

arch/arm/boot/dts/omap3430-sdp.dts+4−4

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

arch/arm/boot/dts/omap4-duovero-parlor.dts+1−0

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

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

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

arch/arm/boot/dts/omap4-panda-es.dts+5−0

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

arch/arm/boot/dts/omap4-panda.dts+5−0

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

arch/arm/boot/dts/omap4.dtsi+17−1

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

arch/arm/boot/dts/omap44xx-clocks.dtsi+0−8

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

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

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

arch/arm/boot/dts/omap5-sbc-t54.dts+4−4

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

arch/arm/boot/dts/omap5.dtsi+38−9

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

arch/arm/boot/dts/prima2.dtsi+33−0

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

arch/arm/boot/dts/pxa168-aspenite.dts+1−1

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

arch/arm/boot/dts/pxa168.dtsi+26−1

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

arch/arm/boot/dts/pxa27x.dtsi+19−1

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

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

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

arch/arm/boot/dts/pxa910-dkb.dts+1−1

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

arch/arm/boot/dts/pxa910.dtsi+27−1

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

arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts+59−0

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

arch/arm/boot/dts/qcom-apq8064-ifc6410.dts+43−0

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

arch/arm/boot/dts/qcom-apq8064.dtsi+183−0

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

arch/arm/boot/dts/qcom-apq8074-dragonboard.dts+21−0

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

arch/arm/boot/dts/qcom-apq8084-ifc6540.dts+23−0

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

arch/arm/boot/dts/qcom-apq8084-mtp.dts+6−0

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

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

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

arch/arm/boot/dts/qcom-ipq8064-ap148.dts+93−0

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

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

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

arch/arm/boot/dts/qcom-ipq8064.dtsi+283−0

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

arch/arm/boot/dts/qcom-msm8660-surf.dts+42−0

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

arch/arm/boot/dts/qcom-msm8660.dtsi+93−0

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

arch/arm/boot/dts/qcom-msm8960-cdp.dts+27−0

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

arch/arm/boot/dts/qcom-msm8960.dtsi+87−0

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

arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts+17−0

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

arch/arm/boot/dts/qcom-msm8974.dtsi+13−2

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

arch/arm/boot/dts/r7s72100-genmai.dts+6−1

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

arch/arm/boot/dts/r7s72100.dtsi+101−91

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

arch/arm/boot/dts/r8a73a4-ape6evm-reference.dts+6−1

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

arch/arm/boot/dts/r8a73a4.dtsi+140−129

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

arch/arm/boot/dts/r8a7740-armadillo800eva-reference.dts+0−283

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

arch/arm/boot/dts/r8a7740-armadillo800eva.dts+280−1

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

arch/arm/boot/dts/r8a7740.dtsi+253−1

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

arch/arm/boot/dts/r8a7778-bockw-reference.dts+6−1

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

arch/arm/boot/dts/r8a7778.dtsi+42−6

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

arch/arm/boot/dts/r8a7779-marzen.dts+88−0

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

arch/arm/boot/dts/r8a7779.dtsi+72−20

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

arch/arm/boot/dts/r8a7790-lager.dts+211−18

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

arch/arm/boot/dts/r8a7790.dtsi+408−28

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

arch/arm/boot/dts/r8a7791-henninger.dts+47−0

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

arch/arm/boot/dts/r8a7791-koelsch.dts+152−7

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

arch/arm/boot/dts/r8a7791.dtsi+371−18

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

arch/arm/boot/dts/r8a7794-alt.dts+48−0

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

arch/arm/boot/dts/r8a7794.dtsi+542−0

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

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

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

arch/arm/boot/dts/rk3066a-bqcurie2.dts+8−11

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

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

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

arch/arm/boot/dts/rk3066a.dtsi+181−1

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

arch/arm/boot/dts/rk3188-radxarock.dts+105−8

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

arch/arm/boot/dts/rk3188.dtsi+133−3

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

arch/arm/boot/dts/rk3288-evb-act8846.dts+1−9

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

arch/arm/boot/dts/rk3288-evb-rk808.dts+136−0

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

arch/arm/boot/dts/rk3288-evb.dtsi+93−0

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

arch/arm/boot/dts/rk3288-thermal.dtsi+74−0

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

arch/arm/boot/dts/rk3288.dtsi+478−1

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

arch/arm/boot/dts/rk3xxx.dtsi+129−8

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

arch/arm/boot/dts/s3c6410-mini6410.dts+0−4

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

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

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

arch/arm/boot/dts/sama5d3.dtsi+35−2

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

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

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

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

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

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

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

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

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

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

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

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

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

arch/arm/boot/dts/sama5d3xcm.dtsi+31−1

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

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

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

arch/arm/boot/dts/sama5d4.dtsi+1309−0

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

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

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

arch/arm/boot/dts/sh73a0-kzm9g-reference.dts+13−4

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

arch/arm/boot/dts/sh73a0.dtsi+18−28

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

arch/arm/boot/dts/socfpga.dtsi+44−6

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

arch/arm/boot/dts/socfpga_arria10.dtsi+374−0

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

arch/arm/boot/dts/socfpga_arria10_socdk.dts+48−0

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

arch/arm/boot/dts/socfpga_arria5.dtsi+6−7

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

arch/arm/boot/dts/socfpga_arria5_socdk.dts+10−5

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

arch/arm/boot/dts/socfpga_cyclone5.dtsi+10−7

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

arch/arm/boot/dts/socfpga_cyclone5_socdk.dts+17−0

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

arch/arm/boot/dts/socfpga_cyclone5_sockit.dts+12−0

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

arch/arm/boot/dts/socfpga_vt.dts+3−6

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

arch/arm/boot/dts/spear1310.dtsi+9−9

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

arch/arm/boot/dts/spear1340.dtsi+3−3

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

arch/arm/boot/dts/ste-ccu8540-pinctrl.dtsi+32−32

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

arch/arm/boot/dts/ste-dbx5x0.dtsi+22−0

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

arch/arm/boot/dts/ste-href-ab8500.dtsi+81−81

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

arch/arm/boot/dts/ste-href-ab8505.dtsi+45−45

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

arch/arm/boot/dts/ste-href-family-pinctrl.dtsi+115−115

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

arch/arm/boot/dts/ste-href-stuib.dtsi+2−2

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

arch/arm/boot/dts/ste-href-tvk1281618.dtsi+6−6

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

arch/arm/boot/dts/ste-hrefprev60.dtsi+10−10

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

arch/arm/boot/dts/ste-hrefv60plus.dtsi+21−21

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

arch/arm/boot/dts/ste-nomadik-nhk15.dts+151−0

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

arch/arm/boot/dts/ste-nomadik-s8815.dts+52−12

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

arch/arm/boot/dts/ste-nomadik-stn8815.dtsi+17−56

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

arch/arm/boot/dts/ste-snowball.dts+18−18

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

arch/arm/boot/dts/stih407-b2120.dts+4−51

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

arch/arm/boot/dts/stih407-clock.dtsi+290−3

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

arch/arm/boot/dts/stih407-family.dtsi+278−0

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

arch/arm/boot/dts/stih407.dtsi+0−263

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

arch/arm/boot/dts/stih410-b2120.dts+29−0

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

arch/arm/boot/dts/stih410-clock.dtsi+338−0

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

arch/arm/boot/dts/stih410-pinctrl.dtsi+34−0

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

arch/arm/boot/dts/stih410.dtsi+14−0

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

arch/arm/boot/dts/stih415-pinctrl.dtsi+191−170

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

arch/arm/boot/dts/stih415.dtsi+12−0

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

arch/arm/boot/dts/stih416-b2020.dts+22−0

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

arch/arm/boot/dts/stih416-b2020e.dts+23−3

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

arch/arm/boot/dts/stih416-pinctrl.dtsi+244−171

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

arch/arm/boot/dts/stih416.dtsi+209−0

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

arch/arm/boot/dts/stih41x-b2000.dtsi+3−3

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

arch/arm/boot/dts/stih41x-b2020.dtsi+7−3

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

arch/arm/boot/dts/stih41x-b2020x.dtsi+4−0

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

arch/arm/boot/dts/stihxxx-b2120.dtsi+59−0

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

arch/arm/boot/dts/sun4i-a10-a1000.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-ba10-tvbox.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-cubieboard.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-hackberry.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-inet97fv2.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-mini-xplus.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts+41−5

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

arch/arm/boot/dts/sun4i-a10-pcduino.dts+41−5

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

arch/arm/boot/dts/sun4i-a10.dtsi+32−13

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

arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts+41−5

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

arch/arm/boot/dts/sun5i-a10s-r7-tv-dongle.dts+41−5

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

arch/arm/boot/dts/sun5i-a10s.dtsi+31−14

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

arch/arm/boot/dts/sun5i-a13-hsg-h702.dts+130−0

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

arch/arm/boot/dts/sun5i-a13-olinuxino-micro.dts+41−7

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

arch/arm/boot/dts/sun5i-a13-olinuxino.dts+41−5

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

arch/arm/boot/dts/sun5i-a13.dtsi+17−14

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

arch/arm/boot/dts/sun6i-a31-app4-evb1.dts+41−5

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

arch/arm/boot/dts/sun6i-a31-colombus.dts+41−5

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

arch/arm/boot/dts/sun6i-a31-hummingbird.dts+41−5

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

arch/arm/boot/dts/sun6i-a31-m9.dts+98−5

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

arch/arm/boot/dts/sun6i-a31.dtsi+78−32

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

arch/arm/boot/dts/sun7i-a20-bananapi.dts+214−0

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

arch/arm/boot/dts/sun7i-a20-cubietruck.dts+14−0

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

arch/arm/boot/dts/sun7i-a20-hummingbird.dts+236−0

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

arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts+41−5

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

arch/arm/boot/dts/sun7i-a20-m3.dts+168−0

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

arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts+173−0

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

arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts+228−0

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

arch/arm/boot/dts/sun7i-a20-pcduino3.dts+41−5

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

arch/arm/boot/dts/sun7i-a20.dtsi+132−23

This diff is large: its 298 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts+82−5

This diff is large: its 107 lines aren’t shown here.

arch/arm/boot/dts/sun8i-a23.dtsi+234−15

This diff is large: its 332 lines aren’t shown here.

arch/arm/boot/dts/sun9i-a80-optimus.dts+119−0

This diff is large: its 120 lines aren’t shown here.

arch/arm/boot/dts/sun9i-a80.dtsi+514−0

This diff is large: its 515 lines aren’t shown here.

arch/arm/boot/dts/sunxi-common-regulators.dtsi+68−5

This diff is large: its 105 lines aren’t shown here.

arch/arm/boot/dts/tegra114-dalmore.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra114-roth.dts+5−4

This diff is large: its 37 lines aren’t shown here.

arch/arm/boot/dts/tegra114-tn7.dts+4−1

This diff is large: its 19 lines aren’t shown here.

arch/arm/boot/dts/tegra114.dtsi+19−16

This diff is large: its 76 lines aren’t shown here.

arch/arm/boot/dts/tegra124-jetson-tk1.dts+139−4

This diff is large: its 197 lines aren’t shown here.

arch/arm/boot/dts/tegra124-nyan-big.dts+1137−0

This diff is large: its 1138 lines aren’t shown here.

arch/arm/boot/dts/tegra124-venice2.dts+14−5

This diff is large: its 54 lines aren’t shown here.

arch/arm/boot/dts/tegra124.dtsi+167−7

This diff is large: its 281 lines aren’t shown here.

arch/arm/boot/dts/tegra20-harmony.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20-iris-512.dts+5−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/boot/dts/tegra20-medcom-wide.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/tegra20-paz00.dts+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/boot/dts/tegra20-seaboard.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20-tamonten.dtsi+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20-trimslice.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20-ventana.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20-whistler.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra20.dtsi+5−8

This diff is large: its 27 lines aren’t shown here.

arch/arm/boot/dts/tegra30-apalis-eval.dts+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/boot/dts/tegra30-beaver.dts+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/boot/dts/tegra30-cardhu.dtsi+3−1

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/tegra30-colibri-eval-v3.dts+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/boot/dts/tegra30.dtsi+16−22

This diff is large: its 82 lines aren’t shown here.

arch/arm/boot/dts/vexpress-v2m-rs1.dtsi+34−2

This diff is large: its 60 lines aren’t shown here.

arch/arm/boot/dts/vexpress-v2m.dtsi+34−2

This diff is large: its 60 lines aren’t shown here.

arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts+222−0

This diff is large: its 264 lines aren’t shown here.

arch/arm/boot/dts/vexpress-v2p-ca9.dts+31−0

This diff is large: its 41 lines aren’t shown here.

arch/arm/boot/dts/vf-colibri-eval-v3.dtsi+96−0

This diff is large: its 97 lines aren’t shown here.

arch/arm/boot/dts/vf-colibri.dtsi+186−0

This diff is large: its 187 lines aren’t shown here.

arch/arm/boot/dts/vf500-colibri-eval-v3.dts+17−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/vf500-colibri.dtsi+20−0

This diff is large: its 21 lines aren’t shown here.

arch/arm/boot/dts/vf500.dtsi+171−0

This diff is large: its 172 lines aren’t shown here.

arch/arm/boot/dts/vf610-colibri-eval-v3.dts+17−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/boot/dts/vf610-colibri.dts+0−123

This diff is large: its 124 lines aren’t shown here.

arch/arm/boot/dts/vf610-colibri.dtsi+25−0

This diff is large: its 26 lines aren’t shown here.

arch/arm/boot/dts/vf610-cosmic.dts+27−6

This diff is large: its 49 lines aren’t shown here.

arch/arm/boot/dts/vf610-twr.dts+58−14

This diff is large: its 123 lines aren’t shown here.

arch/arm/boot/dts/vf610.dtsi+12−420

This diff is large: its 440 lines aren’t shown here.

arch/arm/boot/dts/vfxxx.dtsi+437−0

This diff is large: its 438 lines aren’t shown here.

arch/arm/boot/dts/zynq-7000.dtsi+30−10

This diff is large: its 128 lines aren’t shown here.

arch/arm/boot/dts/zynq-parallella.dts+29−3

This diff is large: its 57 lines aren’t shown here.

arch/arm/boot/dts/zynq-zc702.dts+20−2

This diff is large: its 42 lines aren’t shown here.

arch/arm/boot/dts/zynq-zc706.dts+12−4

This diff is large: its 38 lines aren’t shown here.

arch/arm/boot/dts/zynq-zed.dts+13−5

This diff is large: its 43 lines aren’t shown here.

arch/arm/boot/dts/zynq-zybo.dts+52−0

This diff is large: its 53 lines aren’t shown here.

arch/arm/common/edma.c+61−2

This diff is large: its 114 lines aren’t shown here.

arch/arm/common/sa1111.c+6−8

This diff is large: its 42 lines aren’t shown here.

arch/arm/common/scoop.c+2−8

This diff is large: its 21 lines aren’t shown here.

arch/arm/configs/ape6evm_defconfig+9−1

This diff is large: its 43 lines aren’t shown here.

arch/arm/configs/armadillo800eva_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/configs/at91_dt_defconfig+26−12

This diff is large: its 128 lines aren’t shown here.

arch/arm/configs/at91rm9200_defconfig+0−161

This diff is large: its 162 lines aren’t shown here.

arch/arm/configs/at91sam9260_9g20_defconfig+0−148

This diff is large: its 149 lines aren’t shown here.

arch/arm/configs/at91sam9261_9g10_defconfig+0−148

This diff is large: its 149 lines aren’t shown here.

arch/arm/configs/at91sam9263_defconfig+0−152

This diff is large: its 153 lines aren’t shown here.

arch/arm/configs/at91sam9g45_defconfig+0−172

This diff is large: its 173 lines aren’t shown here.

arch/arm/configs/at91sam9rl_defconfig+0−83

This diff is large: its 84 lines aren’t shown here.

arch/arm/configs/at91x40_defconfig+0−48

This diff is large: its 49 lines aren’t shown here.

arch/arm/configs/bcm2835_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/configs/bcm_defconfig+3−3

This diff is large: its 27 lines aren’t shown here.

arch/arm/configs/bockw_defconfig+3−2

This diff is large: its 26 lines aren’t shown here.

arch/arm/configs/clps711x_defconfig+3−1

This diff is large: its 19 lines aren’t shown here.

arch/arm/configs/davinci_all_defconfig+1−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/configs/ep93xx_defconfig+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/configs/exynos_defconfig+14−1

This diff is large: its 98 lines aren’t shown here.

arch/arm/configs/ezx_defconfig+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/configs/hi3xxx_defconfig+0−58

This diff is large: its 59 lines aren’t shown here.

arch/arm/configs/hisi_defconfig+90−0

This diff is large: its 91 lines aren’t shown here.

arch/arm/configs/imote2_defconfig+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/configs/imx_v4_v5_defconfig+2−13

This diff is large: its 66 lines aren’t shown here.

arch/arm/configs/imx_v6_v7_defconfig+14−7

This diff is large: its 92 lines aren’t shown here.

arch/arm/configs/integrator_defconfig+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/configs/keystone_defconfig+8−1

This diff is large: its 27 lines aren’t shown here.

arch/arm/configs/koelsch_defconfig+0−96

This diff is large: its 97 lines aren’t shown here.

arch/arm/configs/kzm9g_defconfig+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/configs/lager_defconfig+8−2

This diff is large: its 49 lines aren’t shown here.

arch/arm/configs/lpc32xx_defconfig+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/configs/mackerel_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/configs/marzen_defconfig+2−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/configs/multi_v5_defconfig+2−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/configs/multi_v7_defconfig+80−2

This diff is large: its 325 lines aren’t shown here.

arch/arm/configs/mvebu_v5_defconfig+2−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/configs/mvebu_v7_defconfig+40−35

This diff is large: its 154 lines aren’t shown here.

arch/arm/configs/nhk8815_defconfig+4−7

This diff is large: its 62 lines aren’t shown here.

arch/arm/configs/omap1_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/configs/omap2plus_defconfig+87−17

This diff is large: its 259 lines aren’t shown here.

arch/arm/configs/prima2_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/configs/pxa3xx_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/configs/qcom_defconfig+10−4

This diff is large: its 74 lines aren’t shown here.

arch/arm/configs/sama5_defconfig+19−9

This diff is large: its 111 lines aren’t shown here.

arch/arm/configs/shmobile_defconfig+20−3

This diff is large: its 94 lines aren’t shown here.

arch/arm/configs/socfpga_defconfig+28−43

This diff is large: its 143 lines aren’t shown here.

arch/arm/configs/sunxi_defconfig+6−2

This diff is large: its 35 lines aren’t shown here.

arch/arm/configs/tegra_defconfig+5−4

This diff is large: its 40 lines aren’t shown here.

arch/arm/configs/u8500_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/configs/versatile_defconfig+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/configs/vt8500_v6_v7_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/crypto/aes_glue.c+2−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/crypto/sha1-armv7-neon.S+22−17

This diff is large: its 97 lines aren’t shown here.

arch/arm/crypto/sha1_glue.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/arm/crypto/sha1_neon_glue.c+1−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/crypto/sha512_neon_glue.c+3−3

This diff is large: its 17 lines aren’t shown here.

arch/arm/include/asm/Kbuild+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/arch_timer.h+9−25

This diff is large: its 48 lines aren’t shown here.

arch/arm/include/asm/atomic.h+124−183

This diff is large: its 348 lines aren’t shown here.

arch/arm/include/asm/barrier.h+4−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/include/asm/cacheflush.h+10−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/include/asm/cpuidle.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/device.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/dma-mapping.h+10−20

This diff is large: its 46 lines aren’t shown here.

arch/arm/include/asm/firmware.h+9−1

This diff is large: its 24 lines aren’t shown here.

arch/arm/include/asm/fixmap.h+14−17

This diff is large: its 42 lines aren’t shown here.

arch/arm/include/asm/ftrace.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/asm/hardware/coresight.h+0−157

This diff is large: its 158 lines aren’t shown here.

arch/arm/include/asm/hardware/cp14.h+542−0

This diff is large: its 543 lines aren’t shown here.

arch/arm/include/asm/hw_irq.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/io.h+37−53

This diff is large: its 179 lines aren’t shown here.

arch/arm/include/asm/irq_work.h+11−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/include/asm/kvm_emulate.h+10−0

This diff is large: its 24 lines aren’t shown here.

arch/arm/include/asm/kvm_host.h+16−9

This diff is large: its 80 lines aren’t shown here.

arch/arm/include/asm/kvm_mmu.h+30−16

This diff is large: its 90 lines aren’t shown here.

arch/arm/include/asm/mach/pci.h+6−4

This diff is large: its 38 lines aren’t shown here.

arch/arm/include/asm/mcpm.h+22−0

This diff is large: its 37 lines aren’t shown here.

arch/arm/include/asm/memory.h+4−0

This diff is large: its 28 lines aren’t shown here.

arch/arm/include/asm/percpu.h+2−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/include/asm/perf_event.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/asm/pgalloc.h+9−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/include/asm/pgtable-2level-hwdef.h+2−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/include/asm/pgtable-2level.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/asm/pgtable-3level-hwdef.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/include/asm/pgtable-3level.h+15−0

This diff is large: its 33 lines aren’t shown here.

arch/arm/include/asm/pgtable.h+52−14

This diff is large: its 95 lines aren’t shown here.

arch/arm/include/asm/pmu.h+33−3

This diff is large: its 75 lines aren’t shown here.

arch/arm/include/asm/ptrace.h+2−3

This diff is large: its 12 lines aren’t shown here.

arch/arm/include/asm/smp.h+0−6

This diff is large: its 13 lines aren’t shown here.

arch/arm/include/asm/spinlock.h+2−2

This diff is large: its 15 lines aren’t shown here.

arch/arm/include/asm/syscall.h+4−4

This diff is large: its 22 lines aren’t shown here.

arch/arm/include/asm/thread_info.h+7−13

This diff is large: its 48 lines aren’t shown here.

arch/arm/include/asm/tlb.h+36−2

This diff is large: its 79 lines aren’t shown here.

arch/arm/include/asm/vfp.h+5−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/include/asm/xen/page-coherent.h+57−9

This diff is large: its 85 lines aren’t shown here.

arch/arm/include/asm/xen/page.h+4−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/include/debug/asm9260.S+29−0

This diff is large: its 30 lines aren’t shown here.

arch/arm/include/debug/bcm63xx.S+33−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/include/debug/meson.S+35−0

This diff is large: its 36 lines aren’t shown here.

arch/arm/include/debug/renesas-scif.S+52−0

This diff is large: its 53 lines aren’t shown here.

arch/arm/include/debug/sa1100.S+68−0

This diff is large: its 69 lines aren’t shown here.

arch/arm/include/uapi/asm/kvm.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/include/uapi/asm/unistd.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/Makefile+4−3

This diff is large: its 36 lines aren’t shown here.

arch/arm/kernel/asm-offsets.c+11−1

This diff is large: its 29 lines aren’t shown here.

arch/arm/kernel/atags_compat.c+2−4

This diff is large: its 20 lines aren’t shown here.

arch/arm/kernel/atags_parse.c+3−4

This diff is large: its 28 lines aren’t shown here.

arch/arm/kernel/atags_proc.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/kernel/bios32.c+13−17

This diff is large: its 60 lines aren’t shown here.

arch/arm/kernel/calls.S+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/dma-isa.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/kernel/dma.c+11−15

This diff is large: its 99 lines aren’t shown here.

arch/arm/kernel/entry-armv.S+94−14

This diff is large: its 193 lines aren’t shown here.

arch/arm/kernel/entry-common.S+1−236

This diff is large: its 251 lines aren’t shown here.

arch/arm/kernel/entry-ftrace.S+243−0

This diff is large: its 244 lines aren’t shown here.

arch/arm/kernel/entry-header.S+59−4

This diff is large: its 85 lines aren’t shown here.

arch/arm/kernel/etm.c+0−654

This diff is large: its 655 lines aren’t shown here.

arch/arm/kernel/fiq.c+14−5

This diff is large: its 46 lines aren’t shown here.

arch/arm/kernel/ftrace.c+19−0

This diff is large: its 40 lines aren’t shown here.

arch/arm/kernel/hibernate.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/kernel/hw_breakpoint.c+11−11

This diff is large: its 85 lines aren’t shown here.

arch/arm/kernel/io.c+2−3

This diff is large: its 24 lines aren’t shown here.

arch/arm/kernel/irq.c+6−23

This diff is large: its 64 lines aren’t shown here.

arch/arm/kernel/iwmmxt.S+13−0

This diff is large: its 62 lines aren’t shown here.

arch/arm/kernel/jump_label.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/kgdb.c+29−0

This diff is large: its 45 lines aren’t shown here.

arch/arm/kernel/machine_kexec.c+8−7

This diff is large: its 57 lines aren’t shown here.

arch/arm/kernel/module.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/patch.c+73−19

This diff is large: its 132 lines aren’t shown here.

arch/arm/kernel/patch.h+11−1

This diff is large: its 18 lines aren’t shown here.

arch/arm/kernel/perf_callchain.c+136−0

This diff is large: its 137 lines aren’t shown here.

arch/arm/kernel/perf_event.c+20−144

This diff is large: its 247 lines aren’t shown here.

arch/arm/kernel/perf_event_cpu.c+90−95

This diff is large: its 320 lines aren’t shown here.

arch/arm/kernel/perf_event_v6.c+6−6

This diff is large: its 54 lines aren’t shown here.

arch/arm/kernel/perf_event_v7.c+34−38

This diff is large: its 208 lines aren’t shown here.

arch/arm/kernel/perf_event_xscale.c+10−10

This diff is large: its 90 lines aren’t shown here.

arch/arm/kernel/perf_regs.c+8−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/kernel/process.c+59−19

This diff is large: its 142 lines aren’t shown here.

arch/arm/kernel/ptrace.c+8−3

This diff is large: its 26 lines aren’t shown here.

arch/arm/kernel/return_address.c+1−11

This diff is large: its 31 lines aren’t shown here.

arch/arm/kernel/setup.c+19−1

This diff is large: its 69 lines aren’t shown here.

arch/arm/kernel/signal.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/kernel/smp.c+23−18

This diff is large: its 118 lines aren’t shown here.

arch/arm/kernel/smp_twd.c+8−8

This diff is large: its 72 lines aren’t shown here.

arch/arm/kernel/stacktrace.c+1−3

This diff is large: its 14 lines aren’t shown here.

arch/arm/kernel/swp_emulate.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/sys_oabi-compat.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/kernel/thumbee.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/kernel/topology.c+4−4

This diff is large: its 29 lines aren’t shown here.

arch/arm/kernel/traps.c+46−53

This diff is large: its 227 lines aren’t shown here.

arch/arm/kernel/unwind.c+13−14

This diff is large: its 97 lines aren’t shown here.

arch/arm/kernel/vmlinux.lds.S+20−1

This diff is large: its 58 lines aren’t shown here.

arch/arm/kernel/xscale-cp0.c+3−4

This diff is large: its 19 lines aren’t shown here.

arch/arm/kvm/arm.c+84−33

This diff is large: its 240 lines aren’t shown here.

arch/arm/kvm/coproc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/kvm/guest.c+1−27

This diff is large: its 49 lines aren’t shown here.

arch/arm/kvm/interrupts_head.S+7−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/kvm/mmio.c+9−6

This diff is large: its 25 lines aren’t shown here.

arch/arm/kvm/mmu.c+308−59

This diff is large: its 639 lines aren’t shown here.

arch/arm/kvm/psci.c+18−0

This diff is large: its 32 lines aren’t shown here.

arch/arm/lib/copy_from_user.S+5−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/lib/copy_template.S+30−0

This diff is large: its 94 lines aren’t shown here.

arch/arm/lib/copy_to_user.S+5−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/lib/memcpy.S+5−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/lib/memmove.S+28−0

This diff is large: its 94 lines aren’t shown here.

arch/arm/lib/memset.S+12−0

This diff is large: its 60 lines aren’t shown here.

arch/arm/lib/memzero.S+12−0

This diff is large: its 62 lines aren’t shown here.

arch/arm/mach-asm9260/Kconfig+6−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-at91/Kconfig+32−69

This diff is large: its 166 lines aren’t shown here.

arch/arm/mach-at91/Kconfig.non_dt+0−350

This diff is large: its 351 lines aren’t shown here.

arch/arm/mach-at91/Makefile+3−72

This diff is large: its 96 lines aren’t shown here.

arch/arm/mach-at91/Makefile.boot+0−6

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-at91/at91_aic.h+0−99

This diff is large: its 100 lines aren’t shown here.

arch/arm/mach-at91/at91_rstc.h+0−53

This diff is large: its 54 lines aren’t shown here.

arch/arm/mach-at91/at91_shdwc.h+0−50

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-at91/at91_tc.h+0−146

This diff is large: its 147 lines aren’t shown here.

arch/arm/mach-at91/at91rm9200.c+0−341

This diff is large: its 372 lines aren’t shown here.

arch/arm/mach-at91/at91rm9200_devices.c+0−1212

This diff is large: its 1213 lines aren’t shown here.

arch/arm/mach-at91/at91rm9200_time.c+0−23

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-at91/at91sam9260.c+0−354

This diff is large: its 383 lines aren’t shown here.

arch/arm/mach-at91/at91sam9260_devices.c+0−1364

This diff is large: its 1365 lines aren’t shown here.

arch/arm/mach-at91/at91sam9261.c+0−332

This diff is large: its 360 lines aren’t shown here.

arch/arm/mach-at91/at91sam9261_devices.c+0−1098

This diff is large: its 1099 lines aren’t shown here.

arch/arm/mach-at91/at91sam9263.c+0−356

This diff is large: its 384 lines aren’t shown here.

arch/arm/mach-at91/at91sam9263_devices.c+0−1538

This diff is large: its 1539 lines aren’t shown here.

arch/arm/mach-at91/at91sam926x_time.c+0−294

This diff is large: its 295 lines aren’t shown here.

arch/arm/mach-at91/at91sam9_alt_reset.S+0−40

This diff is large: its 41 lines aren’t shown here.

arch/arm/mach-at91/at91sam9g45.c+1−406

This diff is large: its 435 lines aren’t shown here.

arch/arm/mach-at91/at91sam9g45_devices.c+0−1915

This diff is large: its 1916 lines aren’t shown here.

arch/arm/mach-at91/at91sam9g45_reset.S+0−45

This diff is large: its 46 lines aren’t shown here.

arch/arm/mach-at91/at91sam9n12.c+2−211

This diff is large: its 229 lines aren’t shown here.

arch/arm/mach-at91/at91sam9rl.c+1−334

This diff is large: its 365 lines aren’t shown here.

arch/arm/mach-at91/at91sam9rl_devices.c+0−1260

This diff is large: its 1261 lines aren’t shown here.

arch/arm/mach-at91/at91sam9x5.c+2−309

This diff is large: its 327 lines aren’t shown here.

arch/arm/mach-at91/at91x40.c+0−93

This diff is large: its 94 lines aren’t shown here.

arch/arm/mach-at91/at91x40_time.c+0−85

This diff is large: its 86 lines aren’t shown here.

arch/arm/mach-at91/board-1arm.c+0−99

This diff is large: its 100 lines aren’t shown here.

arch/arm/mach-at91/board-afeb-9260v1.c+0−221

This diff is large: its 222 lines aren’t shown here.

arch/arm/mach-at91/board-cam60.c+0−197

This diff is large: its 198 lines aren’t shown here.

arch/arm/mach-at91/board-carmeva.c+0−167

This diff is large: its 168 lines aren’t shown here.

arch/arm/mach-at91/board-cpu9krea.c+0−384

This diff is large: its 385 lines aren’t shown here.

arch/arm/mach-at91/board-cpuat91.c+0−189

This diff is large: its 190 lines aren’t shown here.

arch/arm/mach-at91/board-csb337.c+0−260

This diff is large: its 261 lines aren’t shown here.

arch/arm/mach-at91/board-csb637.c+0−142

This diff is large: its 143 lines aren’t shown here.

arch/arm/mach-at91/board-dt-rm9200.c+0−16

This diff is large: its 35 lines aren’t shown here.

arch/arm/mach-at91/board-dt-sam9.c+0−25

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-at91/board-dt-sama5.c+15−46

This diff is large: its 83 lines aren’t shown here.

arch/arm/mach-at91/board-eb01.c+0−52

This diff is large: its 53 lines aren’t shown here.

arch/arm/mach-at91/board-eb9200.c+0−126

This diff is large: its 127 lines aren’t shown here.

arch/arm/mach-at91/board-ecbat91.c+0−191

This diff is large: its 192 lines aren’t shown here.

arch/arm/mach-at91/board-eco920.c+0−160

This diff is large: its 161 lines aren’t shown here.

arch/arm/mach-at91/board-flexibity.c+0−169

This diff is large: its 170 lines aren’t shown here.

arch/arm/mach-at91/board-foxg20.c+0−272

This diff is large: its 273 lines aren’t shown here.

arch/arm/mach-at91/board-gsia18s.c+0−585

This diff is large: its 586 lines aren’t shown here.

arch/arm/mach-at91/board-kafa.c+0−113

This diff is large: its 114 lines aren’t shown here.

arch/arm/mach-at91/board-kb9202.c+0−159

This diff is large: its 160 lines aren’t shown here.

arch/arm/mach-at91/board-pcontrol-g20.c+0−228

This diff is large: its 229 lines aren’t shown here.

arch/arm/mach-at91/board-picotux200.c+0−129

This diff is large: its 130 lines aren’t shown here.

arch/arm/mach-at91/board-rm9200ek.c+0−196

This diff is large: its 197 lines aren’t shown here.

arch/arm/mach-at91/board-rsi-ews.c+0−232

This diff is large: its 233 lines aren’t shown here.

arch/arm/mach-at91/board-sam9-l9260.c+0−228

This diff is large: its 229 lines aren’t shown here.

arch/arm/mach-at91/board-sam9260ek.c+0−353

This diff is large: its 354 lines aren’t shown here.

arch/arm/mach-at91/board-sam9261ek.c+0−622

This diff is large: its 623 lines aren’t shown here.

arch/arm/mach-at91/board-sam9263ek.c+0−492

This diff is large: its 493 lines aren’t shown here.

arch/arm/mach-at91/board-sam9g20ek.c+0−429

This diff is large: its 430 lines aren’t shown here.

arch/arm/mach-at91/board-sam9m10g45ek.c+0−526

This diff is large: its 527 lines aren’t shown here.

arch/arm/mach-at91/board-sam9rlek.c+0−332

This diff is large: its 333 lines aren’t shown here.

arch/arm/mach-at91/board-snapper9260.c+0−189

This diff is large: its 190 lines aren’t shown here.

arch/arm/mach-at91/board-stamp9g20.c+0−294

This diff is large: its 295 lines aren’t shown here.

arch/arm/mach-at91/board-yl-9200.c+0−597

This diff is large: its 598 lines aren’t shown here.

arch/arm/mach-at91/board.h+0−127

This diff is large: its 128 lines aren’t shown here.

arch/arm/mach-at91/clock.c+0−976

This diff is large: its 977 lines aren’t shown here.

arch/arm/mach-at91/clock.h+0−49

This diff is large: its 50 lines aren’t shown here.

arch/arm/mach-at91/generic.h+5−57

This diff is large: its 91 lines aren’t shown here.

arch/arm/mach-at91/gpio.c+0−982

This diff is large: its 983 lines aren’t shown here.

arch/arm/mach-at91/gpio.h+0−214

This diff is large: its 215 lines aren’t shown here.

arch/arm/mach-at91/gsia18s.h+0−33

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-at91/include/mach/at91_dbgu.h+0−3

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-at91/include/mach/at91_pio.h+6−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-at91/include/mach/at91_ramc.h+3−3

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-at91/include/mach/at91x40.h+0−60

This diff is large: its 61 lines aren’t shown here.

arch/arm/mach-at91/include/mach/atmel-mci.h+0−17

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-at91/include/mach/cpu.h+21−2

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-at91/include/mach/debug-macro.S+4−1

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-at91/include/mach/hardware.h+21−10

This diff is large: its 87 lines aren’t shown here.

arch/arm/mach-at91/include/mach/sama5d4.h+33−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-at91/include/mach/uncompress.h+17−11

This diff is large: its 72 lines aren’t shown here.

arch/arm/mach-at91/irq.c+0−554

This diff is large: its 555 lines aren’t shown here.

arch/arm/mach-at91/leds.c+0−56

This diff is large: its 57 lines aren’t shown here.

arch/arm/mach-at91/pm.c+3−96

This diff is large: its 134 lines aren’t shown here.

arch/arm/mach-at91/pm.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-at91/sama5d4.c+64−0

This diff is large: its 65 lines aren’t shown here.

arch/arm/mach-at91/setup.c+112−202

This diff is large: its 453 lines aren’t shown here.

arch/arm/mach-at91/soc.h+5−4

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-at91/stamp9g20.h+0−7

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-bcm/Kconfig+70−34

This diff is large: its 171 lines aren’t shown here.

arch/arm/mach-bcm/Makefile+8−0

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-bcm/bcm63xx.c+27−0

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-bcm/bcm_cygnus.c+25−0

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-bcm/brcmstb.h+19−0

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-bcm/headsmp-brcmstb.S+33−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-bcm/platsmp-brcmstb.c+329−0

This diff is large: its 330 lines aren’t shown here.

arch/arm/mach-berlin/Kconfig+2−1

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-clps711x/board-edb7211.c+22−15

This diff is large: its 68 lines aren’t shown here.

arch/arm/mach-clps711x/common.c+4−134

This diff is large: its 164 lines aren’t shown here.

arch/arm/mach-clps711x/common.h+5−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-clps711x/devices.c+51−1

This diff is large: its 79 lines aren’t shown here.

arch/arm/mach-cns3xxx/cns3420vb.c+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-cns3xxx/core.c+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-cns3xxx/core.h+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-cns3xxx/pcie.c+24−25

This diff is large: its 99 lines aren’t shown here.

arch/arm/mach-davinci/board-da830-evm.c+37−52

This diff is large: its 232 lines aren’t shown here.

arch/arm/mach-davinci/board-da850-evm.c+18−6

This diff is large: its 78 lines aren’t shown here.

arch/arm/mach-davinci/board-dm355-evm.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-davinci/board-dm365-evm.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-davinci/board-dm644x-evm.c+4−6

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-davinci/board-mityomapl138.c+22−23

This diff is large: its 140 lines aren’t shown here.

arch/arm/mach-davinci/board-neuros-osd2.c+2−3

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-davinci/clock.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-davinci/cpuidle.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-davinci/da8xx-dt.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-davinci/dm355.c+3−4

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-davinci/dm365.c+3−4

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-davinci/mux.c+9−6

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-davinci/pm.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-davinci/pm_domain.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-davinci/time.c+6−7

This diff is large: its 36 lines aren’t shown here.

arch/arm/mach-ebsa110/Makefile+0−3

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-ebsa110/include/mach/io.h+18−7

This diff is large: its 49 lines aren’t shown here.

arch/arm/mach-ebsa110/io.c+7−7

This diff is large: its 63 lines aren’t shown here.

arch/arm/mach-ep93xx/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-ep93xx/dma.c+10−2

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-exynos/Kconfig+13−2

This diff is large: its 43 lines aren’t shown here.

arch/arm/mach-exynos/Makefile+3−9

This diff is large: its 29 lines aren’t shown here.

arch/arm/mach-exynos/common.h+13−20

This diff is large: its 68 lines aren’t shown here.

arch/arm/mach-exynos/exynos-pmu.h+24−0

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-exynos/exynos.c+8−75

This diff is large: its 161 lines aren’t shown here.

arch/arm/mach-exynos/firmware.c+64−3

This diff is large: its 92 lines aren’t shown here.

arch/arm/mach-exynos/hotplug.c+0−91

This diff is large: its 92 lines aren’t shown here.

arch/arm/mach-exynos/include/mach/map.h+0−23

This diff is large: its 41 lines aren’t shown here.

arch/arm/mach-exynos/include/mach/memory.h+0−26

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-exynos/mcpm-exynos.c+22−10

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-exynos/platsmp.c+150−2

This diff is large: its 212 lines aren’t shown here.

arch/arm/mach-exynos/pm.c+40−271

This diff is large: its 397 lines aren’t shown here.

arch/arm/mach-exynos/pm_domains.c+1−77

This diff is large: its 104 lines aren’t shown here.

arch/arm/mach-exynos/pmu.c+629−46

This diff is large: its 748 lines aren’t shown here.

arch/arm/mach-exynos/regs-pmu.h+361−0

This diff is large: its 416 lines aren’t shown here.

arch/arm/mach-exynos/sleep.S+28−0

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-exynos/smc.h+4−0

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-exynos/suspend.c+566−0

This diff is large: its 567 lines aren’t shown here.

arch/arm/mach-footbridge/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-highbank/highbank.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-hisi/Kconfig+10−1

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-hisi/Makefile+3−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-hisi/hisilicon.c+9−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-hisi/platmcpm.c+386−0

This diff is large: its 387 lines aren’t shown here.

arch/arm/mach-imx/Kconfig+38−104

This diff is large: its 189 lines aren’t shown here.

arch/arm/mach-imx/Makefile+7−9

This diff is large: its 57 lines aren’t shown here.

arch/arm/mach-imx/anatop.c+45−2

This diff is large: its 78 lines aren’t shown here.

arch/arm/mach-imx/avic.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-imx/board-pcm038.h+0−36

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-imx/clk-cpu.c+107−0

This diff is large: its 108 lines aren’t shown here.

arch/arm/mach-imx/clk-gate-exclusive.c+94−0

This diff is large: its 95 lines aren’t shown here.

arch/arm/mach-imx/clk-imx51-imx53.c+13−1

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-imx/clk-imx6q.c+90−25

This diff is large: its 219 lines aren’t shown here.

arch/arm/mach-imx/clk-imx6sl.c+86−17

This diff is large: its 168 lines aren’t shown here.

arch/arm/mach-imx/clk-imx6sx.c+54−9

This diff is large: its 88 lines aren’t shown here.

arch/arm/mach-imx/clk-pllv3.c+1−43

This diff is large: its 107 lines aren’t shown here.

arch/arm/mach-imx/clk-vf610.c+122−44

This diff is large: its 234 lines aren’t shown here.

arch/arm/mach-imx/clk.h+7−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-imx/common.h+4−5

This diff is large: its 45 lines aren’t shown here.

arch/arm/mach-imx/cpuidle-imx5.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-imx/cpuidle-imx6q.c+1−6

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-imx/cpuidle-imx6sl.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-imx/eukrea-baseboards.h+1−9

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-imx/eukrea_mbimx27-baseboard.c+0−351

This diff is large: its 352 lines aren’t shown here.

arch/arm/mach-imx/gpc.c+26−16

This diff is large: its 76 lines aren’t shown here.

arch/arm/mach-imx/imx1-dt.c+26−0

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-imx/imx25-dt.c+0−9

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-imx/imx27-dt.c+1−4

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-imx/imx31-dt.c+0−9

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-imx/imx35-dt.c+0−10

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-imx/iomux-imx31.c+4−11

This diff is large: its 70 lines aren’t shown here.

arch/arm/mach-imx/iomux-mx3.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-imx/iomux-v1.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-imx/iomux-v3.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-imx/mach-armadillo5x0.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-imx/mach-cpuimx27.c+0−321

This diff is large: its 322 lines aren’t shown here.

arch/arm/mach-imx/mach-imx50.c+0−9

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-imx/mach-imx51.c+1−3

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-imx/mach-imx53.c+2−2

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-imx/mach-imx6q.c+0−3

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-imx/mach-imx6sl.c+0−4

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-imx/mach-imx6sx.c+54−4

This diff is large: its 97 lines aren’t shown here.

arch/arm/mach-imx/mach-ls1021a.c+22−0

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-imx/mach-mx1ads.c+0−154

This diff is large: its 155 lines aren’t shown here.

arch/arm/mach-imx/mach-mx31_3ds.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-imx/mach-mx31lite.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-imx/mach-mxt_td60.c+0−273

This diff is large: its 274 lines aren’t shown here.

arch/arm/mach-imx/mach-pcm037.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-imx/mach-pcm038.c+0−358

This diff is large: its 359 lines aren’t shown here.

arch/arm/mach-imx/mach-vf610.c+0−10

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-imx/mmdc.c+17−1

This diff is large: its 46 lines aren’t shown here.

arch/arm/mach-imx/mxc.h+4−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-imx/pcm970-baseboard.c+0−231

This diff is large: its 232 lines aren’t shown here.

arch/arm/mach-imx/platsmp.c+33−10

This diff is large: its 69 lines aren’t shown here.

arch/arm/mach-imx/pm-imx6.c+5−10

This diff is large: its 79 lines aren’t shown here.

arch/arm/mach-imx/suspend-imx6.S+7−7

This diff is large: its 56 lines aren’t shown here.

arch/arm/mach-imx/system.c+0−15

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-imx/time.c+26−5

This diff is large: its 65 lines aren’t shown here.

arch/arm/mach-imx/tzic.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-integrator/Kconfig+23−0

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-integrator/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-integrator/cm.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-integrator/common.h+0−2

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-integrator/core.c+0−103

This diff is large: its 128 lines aren’t shown here.

arch/arm/mach-integrator/impd1.c+48−0

This diff is large: its 80 lines aren’t shown here.

arch/arm/mach-integrator/include/mach/uncompress.h+0−48

This diff is large: its 49 lines aren’t shown here.

arch/arm/mach-integrator/integrator_ap.c+0−218

This diff is large: its 273 lines aren’t shown here.

arch/arm/mach-integrator/integrator_cp.c+0−28

This diff is large: its 55 lines aren’t shown here.

arch/arm/mach-integrator/leds.c+0−124

This diff is large: its 125 lines aren’t shown here.

arch/arm/mach-integrator/pci_v3.c+12−11

This diff is large: its 76 lines aren’t shown here.

arch/arm/mach-iop13xx/Makefile+0−5

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-iop13xx/msi.c+5−5

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-iop32x/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-iop33x/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-ixp4xx/common.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-ixp4xx/include/mach/io.h+24−4

This diff is large: its 147 lines aren’t shown here.

arch/arm/mach-keystone/Kconfig+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-keystone/pm_domain.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-ks8695/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-lpc32xx/common.c+6−23

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-mediatek/Kconfig+2−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-mediatek/mediatek.c+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-meson/Kconfig+19−0

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-meson/Makefile+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm/mach-meson/meson.c+29−0

This diff is large: its 30 lines aren’t shown here.

arch/arm/mach-mmp/Kconfig+6−6

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-mmp/gplugd.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-mmp/mmp-dt.c+18−39

This diff is large: its 82 lines aren’t shown here.

arch/arm/mach-mmp/mmp2-dt.c+9−17

This diff is large: its 47 lines aren’t shown here.

arch/arm/mach-msm/board-mahimahi.c+0−83

This diff is large: its 84 lines aren’t shown here.

arch/arm/mach-msm/board-msm7x30.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-msm/board-trout-gpio.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-msm/board-trout.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-msm/clock-pcom.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-msm/io.c+2−4

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-msm/smd.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-mvebu/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-mvebu/armada-370-xp.h+0−6

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-mvebu/board-v7.c+58−66

This diff is large: its 164 lines aren’t shown here.

arch/arm/mach-mvebu/coherency.c+38−185

This diff is large: its 286 lines aren’t shown here.

arch/arm/mach-mvebu/coherency_ll.S+19−2

This diff is large: its 57 lines aren’t shown here.

arch/arm/mach-mvebu/common.h+2−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-mvebu/cpu-reset.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-mvebu/headsmp-a9.S+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-mvebu/platsmp-a9.c+51−2

This diff is large: its 73 lines aren’t shown here.

arch/arm/mach-mvebu/platsmp.c+17−16

This diff is large: its 73 lines aren’t shown here.

arch/arm/mach-mvebu/pm-board.c+141−0

This diff is large: its 142 lines aren’t shown here.

arch/arm/mach-mvebu/pm.c+218−0

This diff is large: its 219 lines aren’t shown here.

arch/arm/mach-mvebu/pmsu.c+8−3

This diff is large: its 46 lines aren’t shown here.

arch/arm/mach-mvebu/pmsu.h+3−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-mvebu/pmsu_ll.S+21−7

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-nomadik/cpu-8815.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap1/pm_bus.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-omap2/Kconfig+6−32

This diff is large: its 117 lines aren’t shown here.

arch/arm/mach-omap2/Makefile+11−15

This diff is large: its 92 lines aren’t shown here.

arch/arm/mach-omap2/am33xx-restart.c+2−10

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-omap2/board-3430sdp.c+0−633

This diff is large: its 634 lines aren’t shown here.

arch/arm/mach-omap2/board-am3517crane.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/board-am3517evm.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-cm-t35.c+1−4

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-omap2/board-cm-t3517.c+1−3

This diff is large: its 32 lines aren’t shown here.

arch/arm/mach-omap2/board-devkit8000.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-flash.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-omap2/board-flash.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-generic.c+17−27

This diff is large: its 184 lines aren’t shown here.

arch/arm/mach-omap2/board-ldp.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-n8x0.c+5−25

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-omap2/board-omap3beagle.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-omap3logic.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/board-omap3pandora.c+1−2

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-omap2/board-omap3stalker.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-omap3touchbook.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-overo.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-rx51-peripherals.c+35−72

This diff is large: its 207 lines aren’t shown here.

arch/arm/mach-omap2/board-rx51.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/board-ti8168evm.c+0−62

This diff is large: its 63 lines aren’t shown here.

arch/arm/mach-omap2/cclock3xxx_data.c+20−9

This diff is large: its 120 lines aren’t shown here.

arch/arm/mach-omap2/clock.c+6−1

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-omap2/clock.h+1−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-omap2/clock3xxx.c+37−1

This diff is large: its 59 lines aren’t shown here.

arch/arm/mach-omap2/cm.h+15−3

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-omap2/cm1_44xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm1_54xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm1_7xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm2_44xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm2_54xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm2_7xx.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/cm2xxx.c+10−7

This diff is large: its 63 lines aren’t shown here.

arch/arm/mach-omap2/cm2xxx.h+2−8

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-omap2/cm33xx.c+41−20

This diff is large: its 189 lines aren’t shown here.

arch/arm/mach-omap2/cm33xx.h+1−36

This diff is large: its 43 lines aren’t shown here.

arch/arm/mach-omap2/cm3xxx.c+11−8

This diff is large: its 66 lines aren’t shown here.

arch/arm/mach-omap2/cm3xxx.h+0−12

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-omap2/cm44xx.c+0−49

This diff is large: its 50 lines aren’t shown here.

arch/arm/mach-omap2/cm44xx.h+3−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/cm_44xx_54xx.h+0−36

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-omap2/cm_common.c+78−4

This diff is large: its 104 lines aren’t shown here.

arch/arm/mach-omap2/cminst44xx.c+47−33

This diff is large: its 253 lines aren’t shown here.

arch/arm/mach-omap2/cminst44xx.h+0−43

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-omap2/common-board-devices.h+5−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-omap2/common.h+3−24

This diff is large: its 62 lines aren’t shown here.

arch/arm/mach-omap2/cpuidle34xx.c+0−7

This diff is large: its 56 lines aren’t shown here.

arch/arm/mach-omap2/cpuidle44xx.c+2−3

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-omap2/devices.c+27−66

This diff is large: its 125 lines aren’t shown here.

arch/arm/mach-omap2/display.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/dpll3xxx.c+119−60

This diff is large: its 207 lines aren’t shown here.

arch/arm/mach-omap2/dpll44xx.c+41−0

This diff is large: its 45 lines aren’t shown here.

arch/arm/mach-omap2/emu.c+0−50

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-nand.c+1−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-nand.h+0−27

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-onenand.c+1−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-onenand.h+0−24

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-smc91x.c+0−186

This diff is large: its 187 lines aren’t shown here.

arch/arm/mach-omap2/gpmc-smc91x.h+0−42

This diff is large: its 43 lines aren’t shown here.

arch/arm/mach-omap2/gpmc.c+0−1889

This diff is large: its 1890 lines aren’t shown here.

arch/arm/mach-omap2/gpmc.h+5−222

This diff is large: its 232 lines aren’t shown here.

arch/arm/mach-omap2/hdq1w.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-omap2/hsmmc.c+64−94

This diff is large: its 367 lines aren’t shown here.

arch/arm/mach-omap2/hsmmc.h+1−8

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-omap2/i2c.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/id.c+6−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-omap2/io.c+27−21

This diff is large: its 146 lines aren’t shown here.

arch/arm/mach-omap2/irq.c+0−380

This diff is large: its 381 lines aren’t shown here.

arch/arm/mach-omap2/mmc.h+0−10

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-omap2/msdi.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-omap2/mux.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/omap-mpuss-lowpower.c+78−32

This diff is large: its 263 lines aren’t shown here.

arch/arm/mach-omap2/omap-secure.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/omap-wakeupgen.c+19−1

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-omap2/omap-wakeupgen.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/omap2-restart.c+2−3

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-omap2/omap3-restart.c+2−5

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/omap4-common.c+21−2

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-omap2/omap4-restart.c+2−4

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-omap2/omap_device.c+5−1

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod.c+91−211

This diff is large: its 548 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod.h+12−0

This diff is large: its 47 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_2430_data.c+2−2

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c+4−4

This diff is large: its 39 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_33xx_data.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_3xxx_data.c+10−10

This diff is large: its 87 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_43xx_data.c+39−0

This diff is large: its 60 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_44xx_data.c+18−11

This diff is large: its 155 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_54xx_data.c+7−2

This diff is large: its 65 lines aren’t shown here.

arch/arm/mach-omap2/omap_hwmod_7xx_data.c+102−2

This diff is large: its 146 lines aren’t shown here.

arch/arm/mach-omap2/omap_phy_internal.c+5−3

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-omap2/pdata-quirks.c+55−8

This diff is large: its 137 lines aren’t shown here.

arch/arm/mach-omap2/pm.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/pm.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/pm34xx.c+2−2

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-omap2/pm44xx.c+92−63

This diff is large: its 231 lines aren’t shown here.

arch/arm/mach-omap2/powerdomain.c+78−1

This diff is large: its 93 lines aren’t shown here.

arch/arm/mach-omap2/powerdomain.h+4−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-omap2/powerdomains54xx_data.c+6−6

This diff is large: its 40 lines aren’t shown here.

arch/arm/mach-omap2/powerdomains7xx_data.c+7−7

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-omap2/prm.h+16−0

This diff is large: its 45 lines aren’t shown here.

arch/arm/mach-omap2/prm2xxx.c+5−1

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/prm2xxx.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/prm2xxx_3xxx.c+14−5

This diff is large: its 61 lines aren’t shown here.

arch/arm/mach-omap2/prm2xxx_3xxx.h+6−3

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-omap2/prm33xx.c+55−9

This diff is large: its 147 lines aren’t shown here.

arch/arm/mach-omap2/prm33xx.h+2−9

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-omap2/prm3xxx.c+34−16

This diff is large: its 141 lines aren’t shown here.

arch/arm/mach-omap2/prm3xxx.h+0−16

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-omap2/prm44xx.c+103−23

This diff is large: its 275 lines aren’t shown here.

arch/arm/mach-omap2/prm44xx_54xx.h+0−19

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-omap2/prm_common.c+100−3

This diff is large: its 124 lines aren’t shown here.

arch/arm/mach-omap2/prminst44xx.c+32−18

This diff is large: its 93 lines aren’t shown here.

arch/arm/mach-omap2/prminst44xx.h+6−2

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-omap2/serial.c+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-omap2/smartreflex-class3.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-omap2/soc.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-omap2/sr_device.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/sram.c+1−38

This diff is large: its 81 lines aren’t shown here.

arch/arm/mach-omap2/sram.h+0−7

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-omap2/timer.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-omap2/twl-common.c+1−11

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-omap2/vc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-omap2/voltage.c+11−11

This diff is large: its 89 lines aren’t shown here.

arch/arm/mach-omap2/wd_timer.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-orion5x/dns323-setup.c+4−4

This diff is large: its 29 lines aren’t shown here.

arch/arm/mach-orion5x/terastation_pro2-setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-orion5x/ts209-setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-orion5x/ts409-setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-orion5x/ts78xx-setup.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-prima2/pm.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-prima2/rstc.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-prima2/rtciobrg.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-pxa/Kconfig+11−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-pxa/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-pxa/devices.c+40−2

This diff is large: its 50 lines aren’t shown here.

arch/arm/mach-pxa/devices.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-pxa/em-x270.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-pxa/generic.h+42−23

This diff is large: its 92 lines aren’t shown here.

arch/arm/mach-pxa/gumstix.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/addr-map.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/pxa25x.h+0−8

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/pxa27x.h+0−4

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/pxa2xx-regs.h+10−0

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-pxa/include/mach/pxa3xx.h+0−5

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-pxa/lpd270.c+6−6

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-pxa/mfp-pxa2xx.c+5−7

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-pxa/poodle.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-pxa/pxa-dt.c+15−3

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-pxa/pxa27x.c+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-pxa/pxa3xx-ulpi.c+3−4

This diff is large: its 35 lines aren’t shown here.

arch/arm/mach-pxa/pxa3xx.c+7−7

This diff is large: its 28 lines aren’t shown here.

arch/arm/mach-pxa/raumfeld.c+13−13

This diff is large: its 104 lines aren’t shown here.

arch/arm/mach-pxa/spitz.c+9−0

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-pxa/tosa-bt.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-pxa/tosa.c+7−34

This diff is large: its 68 lines aren’t shown here.

arch/arm/mach-qcom/board.c+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-realview/Kconfig+13−0

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-realview/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-realview/realview-dt.c+32−0

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-rockchip/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-rockchip/headsmp.S+4−1

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-rockchip/platsmp.c+180−43

This diff is large: its 292 lines aren’t shown here.

arch/arm/mach-rockchip/rockchip.c+7−0

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-rpc/Makefile+0−4

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c24xx/Kconfig+0−2

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-s3c24xx/Makefile+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-s3c24xx/common.c+0−4

This diff is large: its 32 lines aren’t shown here.

arch/arm/mach-s3c24xx/common.h+0−5

This diff is large: its 40 lines aren’t shown here.

arch/arm/mach-s3c24xx/h1940-bluetooth.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-s3c24xx/h1940.h+3−1

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-s3c24xx/include/mach/regs-s3c2443-clock.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-amlm5900.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-anubis.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-at2440evb.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-bast.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-gta02.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-h1940.c+2−2

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-jive.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-mini2440.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-n30.c+0−2

This diff is large: its 14 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-nexcoder.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-osiris-dvs.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-osiris.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-otom.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-qt2410.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-rx1950.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-rx3715.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-s3c2416-dt.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-smdk2410.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-smdk2413.c+0−3

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-smdk2416.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-smdk2440.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-smdk2443.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-tct_hammer.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-vr1000.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/mach-vstms.c+0−1

This diff is large: its 6 lines aren’t shown here.

arch/arm/mach-s3c24xx/s3c2410.c+0−13

This diff is large: its 24 lines aren’t shown here.

arch/arm/mach-s3c24xx/s3c2412.c+0−23

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-s3c24xx/s3c2416.c+0−8

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-s3c24xx/s3c2443.c+0−8

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-s3c24xx/s3c244x.c+0−12

This diff is large: its 23 lines aren’t shown here.

arch/arm/mach-s3c64xx/Makefile+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-s3c64xx/common.c+0−5

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-s3c64xx/common.h+0−7

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-s3c64xx/cpuidle.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-anw6410.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-crag6410.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-hmt.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-mini6410.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-ncp.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-real6410.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smartq5.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smartq7.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smdk6400.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/mach-smdk6410.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-s3c64xx/pm.c+0−7

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-s5pv210/Makefile+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-s5pv210/pm.c+1−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-s5pv210/regs-clock.hrenamed from arch/arm/mach-s5pv210/include/mach/regs-clock.h+1−2

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-s5pv210/s5pv210.c+1−1

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-sa1100/Kconfig+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-sa1100/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-sa1100/clock.c+36−7

This diff is large: its 85 lines aren’t shown here.

arch/arm/mach-sa1100/collie.c+7−48

This diff is large: its 88 lines aren’t shown here.

arch/arm/mach-sa1100/h3xxx.c+15−0

This diff is large: its 32 lines aren’t shown here.

arch/arm/mach-sa1100/include/mach/debug-macro.S+0−62

This diff is large: its 63 lines aren’t shown here.

arch/arm/mach-sa1100/include/mach/entry-macro.S+0−41

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-sa1100/include/mach/irqs.h+51−51

This diff is large: its 117 lines aren’t shown here.

arch/arm/mach-sa1100/irq.c+130−99

This diff is large: its 338 lines aren’t shown here.

arch/arm/mach-sa1100/neponset.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-sa1100/pci-nanoengine.c+4−4

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-shmobile/Kconfig+46−90

This diff is large: its 234 lines aren’t shown here.

arch/arm/mach-shmobile/Makefile+16−27

This diff is large: its 93 lines aren’t shown here.

arch/arm/mach-shmobile/Makefile.boot+0−3

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-shmobile/board-ape6evm-reference.c+2−7

This diff is large: its 31 lines aren’t shown here.

arch/arm/mach-shmobile/board-ape6evm.c+2−5

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-shmobile/board-armadillo800eva-reference.c+0−198

This diff is large: its 199 lines aren’t shown here.

arch/arm/mach-shmobile/board-armadillo800eva.c+37−28

This diff is large: its 117 lines aren’t shown here.

arch/arm/mach-shmobile/board-bockw-reference.c+2−5

This diff is large: its 22 lines aren’t shown here.

arch/arm/mach-shmobile/board-bockw.c+1−5

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-shmobile/board-genmai-reference.c+0−55

This diff is large: its 56 lines aren’t shown here.

arch/arm/mach-shmobile/board-genmai.c+0−161

This diff is large: its 162 lines aren’t shown here.

arch/arm/mach-shmobile/board-koelsch-reference.c+0−120

This diff is large: its 121 lines aren’t shown here.

arch/arm/mach-shmobile/board-koelsch.c+0−531

This diff is large: its 532 lines aren’t shown here.

arch/arm/mach-shmobile/board-kzm9g-reference.c+10−6

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-shmobile/board-kzm9g.c+1−5

This diff is large: its 27 lines aren’t shown here.

arch/arm/mach-shmobile/board-lager-reference.c+0−87

This diff is large: its 112 lines aren’t shown here.

arch/arm/mach-shmobile/board-lager.c+0−65

This diff is large: its 107 lines aren’t shown here.

arch/arm/mach-shmobile/board-mackerel.c+3−6

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-shmobile/board-marzen-reference.c+1−16

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-shmobile/board-marzen.c+0−63

This diff is large: its 91 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r7s72100.c+0−231

This diff is large: its 232 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a73a4.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7740.c+7−6

This diff is large: its 45 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7778.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7779.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7790.c+1−5

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-shmobile/clock-r8a7791.c+0−342

This diff is large: its 343 lines aren’t shown here.

arch/arm/mach-shmobile/clock-sh7372.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/clock-sh73a0.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/clock.c+3−33

This diff is large: its 51 lines aren’t shown here.

arch/arm/mach-shmobile/clock.h+0−14

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-shmobile/common.h+0−7

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-shmobile/console.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/cpufreq.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-shmobile/dma-register.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/headsmp-scu.S+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-shmobile/intc-sh7372.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/intc-sh73a0.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/intc.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-shmobile/irqs.h+1−7

This diff is large: its 20 lines aren’t shown here.

arch/arm/mach-shmobile/platsmp-apmu.c+9−18

This diff is large: its 67 lines aren’t shown here.

arch/arm/mach-shmobile/platsmp-apmu.h+32−0

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-shmobile/pm-r8a7740.c+47−14

This diff is large: its 95 lines aren’t shown here.

arch/arm/mach-shmobile/pm-r8a7779.c+1−3

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-shmobile/pm-rcar.c+0−4

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-shmobile/pm-rmobile.c+1−5

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-shmobile/pm-rmobile.h+2−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-shmobile/pm-sh7372.c+0−4

This diff is large: its 32 lines aren’t shown here.

arch/arm/mach-shmobile/r7s72100.h+0−7

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-shmobile/r8a73a4.h+0−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7740.h+2−7

This diff is large: its 29 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7778.h+0−5

This diff is large: its 19 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7779.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7790.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-shmobile/r8a7791.h+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/setup-emev2.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r7s72100.c+1−27

This diff is large: its 49 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a73a4.c+4−19

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7740.c+44−32

This diff is large: its 156 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7778.c+4−13

This diff is large: its 61 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7779.c+10−21

This diff is large: its 97 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7790.c+1−10

This diff is large: its 32 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7791.c+1−189

This diff is large: its 210 lines aren’t shown here.

arch/arm/mach-shmobile/setup-r8a7794.c+33−0

This diff is large: its 34 lines aren’t shown here.

arch/arm/mach-shmobile/setup-rcar-gen2.c+49−27

This diff is large: its 112 lines aren’t shown here.

arch/arm/mach-shmobile/setup-sh7372.c+6−8

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-shmobile/setup-sh73a0.c+34−27

This diff is large: its 192 lines aren’t shown here.

arch/arm/mach-shmobile/sh73a0.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-shmobile/sleep-sh7372.S+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-shmobile/smp-emev2.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/smp-r8a7779.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/smp-r8a7790.c+15−1

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-shmobile/smp-r8a7791.c+11−1

This diff is large: its 25 lines aren’t shown here.

arch/arm/mach-shmobile/smp-sh73a0.c+0−4

This diff is large: its 11 lines aren’t shown here.

arch/arm/mach-shmobile/timer.c+18−32

This diff is large: its 89 lines aren’t shown here.

arch/arm/mach-socfpga/core.h+4−1

This diff is large: its 26 lines aren’t shown here.

arch/arm/mach-socfpga/headsmp.S+15−10

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-socfpga/platsmp.c+12−9

This diff is large: its 42 lines aren’t shown here.

arch/arm/mach-socfpga/socfpga.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-spear/Kconfig+4−5

This diff is large: its 44 lines aren’t shown here.

arch/arm/mach-sti/Kconfig+10−0

This diff is large: its 15 lines aren’t shown here.

arch/arm/mach-sunxi/Kconfig+7−0

This diff is large: its 12 lines aren’t shown here.

arch/arm/mach-sunxi/platsmp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-sunxi/sunxi.c+9−76

This diff is large: its 115 lines aren’t shown here.

arch/arm/mach-tegra/Kconfig+1−8

This diff is large: its 21 lines aren’t shown here.

arch/arm/mach-tegra/cpuidle-tegra114.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/arm/mach-tegra/cpuidle-tegra20.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-tegra/cpuidle-tegra30.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-tegra/flowctrl.c+37−7

This diff is large: its 77 lines aren’t shown here.

arch/arm/mach-tegra/flowctrl.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-tegra/irq.c+11−11

This diff is large: its 62 lines aren’t shown here.

arch/arm/mach-tegra/reset-handler.S+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-tegra/tegra.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-u300/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-u300/dummyspichip.c+29−36

This diff is large: its 151 lines aren’t shown here.

arch/arm/mach-u300/regulator.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-ux500/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/mach-ux500/Makefile+1−0

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-ux500/pm.c+4−0

This diff is large: its 16 lines aren’t shown here.

arch/arm/mach-ux500/pm_domains.c+79−0

This diff is large: its 80 lines aren’t shown here.

arch/arm/mach-ux500/pm_domains.h+17−0

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-vexpress/Kconfig+1−3

This diff is large: its 18 lines aren’t shown here.

arch/arm/mach-vexpress/Makefile+1−2

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-vexpress/core.h+0−7

This diff is large: its 13 lines aren’t shown here.

arch/arm/mach-vexpress/ct-ca9x4.c+0−212

This diff is large: its 213 lines aren’t shown here.

arch/arm/mach-vexpress/include/mach/ct-ca9x4.h+0−47

This diff is large: its 48 lines aren’t shown here.

arch/arm/mach-vexpress/include/mach/hardware.h+0−1

This diff is large: its 2 lines aren’t shown here.

arch/arm/mach-vexpress/include/mach/irqs.h+0−6

This diff is large: its 7 lines aren’t shown here.

arch/arm/mach-vexpress/include/mach/motherboard.h+0−88

This diff is large: its 89 lines aren’t shown here.

arch/arm/mach-vexpress/platsmp.c+0−42

This diff is large: its 64 lines aren’t shown here.

arch/arm/mach-vexpress/v2m.c+0−374

This diff is large: its 387 lines aren’t shown here.

arch/arm/mach-vt8500/vt8500.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mach-zynq/Makefile+1−4

This diff is large: its 10 lines aren’t shown here.

arch/arm/mach-zynq/common.c+10−3

This diff is large: its 37 lines aren’t shown here.

arch/arm/mach-zynq/common.h+14−3

This diff is large: its 33 lines aren’t shown here.

arch/arm/mach-zynq/hotplug.c+0−59

This diff is large: its 60 lines aren’t shown here.

arch/arm/mach-zynq/platsmp.c+40−1

This diff is large: its 61 lines aren’t shown here.

arch/arm/mach-zynq/pm.c+83−0

This diff is large: its 84 lines aren’t shown here.

arch/arm/mach-zynq/slcr.c+42−1

This diff is large: its 58 lines aren’t shown here.

arch/arm/mm/Kconfig+36−14

This diff is large: its 159 lines aren’t shown here.

arch/arm/mm/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/alignment.c+5−5

This diff is large: its 43 lines aren’t shown here.

arch/arm/mm/cache-feroceon-l2.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/arm/mm/cache-l2x0.c+131−0

This diff is large: its 173 lines aren’t shown here.

arch/arm/mm/cache-tauros2.c+6−6

This diff is large: its 50 lines aren’t shown here.

arch/arm/mm/context.c+34−24

This diff is large: its 71 lines aren’t shown here.

arch/arm/mm/copypage-v6.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/dma-mapping.c+135−160

This diff is large: its 434 lines aren’t shown here.

arch/arm/mm/dump.c+2−7

This diff is large: its 28 lines aren’t shown here.

arch/arm/mm/fault-armv.c+3−3

This diff is large: its 21 lines aren’t shown here.

arch/arm/mm/fault.c+15−16

This diff is large: its 100 lines aren’t shown here.

arch/arm/mm/flush.c+16−1

This diff is large: its 28 lines aren’t shown here.

arch/arm/mm/highmem.c+11−7

This diff is large: its 54 lines aren’t shown here.

arch/arm/mm/idmap.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/init.c+159−9

This diff is large: its 231 lines aren’t shown here.

arch/arm/mm/mmu.c+68−67

This diff is large: its 295 lines aren’t shown here.

arch/arm/mm/pageattr.c+91−0

This diff is large: its 92 lines aren’t shown here.

arch/arm/mm/proc-macros.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/mm/proc-v7.S+4−5

This diff is large: its 38 lines aren’t shown here.

arch/arm/mm/proc-xscale.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm/net/bpf_jit_32.c+29−8

This diff is large: its 89 lines aren’t shown here.

arch/arm/net/bpf_jit_32.h+14−0

This diff is large: its 21 lines aren’t shown here.

arch/arm/nwfpe/fpmodule.c+4−4

This diff is large: its 25 lines aren’t shown here.

arch/arm/plat-iop/Makefile+0−6

This diff is large: its 17 lines aren’t shown here.

arch/arm/plat-omap/Makefile+0−3

This diff is large: its 10 lines aren’t shown here.

arch/arm/plat-omap/dma.c+6−731

This diff is large: its 798 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-orion/gpio.c+34−5

This diff is large: its 69 lines aren’t shown here.

arch/arm/plat-orion/include/plat/orion-gpio.h+4−1

This diff is large: its 17 lines aren’t shown here.

arch/arm/plat-pxa/ssp.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/arm/plat-samsung/Kconfig+3−2

This diff is large: its 12 lines aren’t shown here.

arch/arm/plat-samsung/Makefile+1−5

This diff is large: its 20 lines aren’t shown here.

arch/arm/plat-samsung/adc.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/plat-samsung/include/plat/map-s5p.h+0−21

This diff is large: its 44 lines aren’t shown here.

arch/arm/plat-samsung/pm-debug.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm/plat-versatile/Kconfig+1−1

This diff is large: its 8 lines aren’t shown here.

arch/arm/vfp/vfphw.S+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm/vfp/vfpmodule.c+56−46

This diff is large: its 120 lines aren’t shown here.

arch/arm/vfp/vfpsingle.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm/xen/Makefile+1−1

This diff is large: its 3 lines aren’t shown here.

arch/arm/xen/enlighten.c+0−5

This diff is large: its 12 lines aren’t shown here.

arch/arm/xen/mm.c+121−0

This diff is large: its 153 lines aren’t shown here.

arch/arm/xen/mm32.c+0−202

This diff is large: its 203 lines aren’t shown here.

arch/arm64/Kconfig+234−9

This diff is large: its 363 lines aren’t shown here.

arch/arm64/Kconfig.debug+23−0

This diff is large: its 35 lines aren’t shown here.

arch/arm64/Makefile+9−4

This diff is large: its 41 lines aren’t shown here.

arch/arm64/boot/dts/Makefile+7−8

This diff is large: its 17 lines aren’t shown here.

arch/arm64/boot/dts/amd/Makefile+5−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/amd/amd-overdrive.dts+66−0

This diff is large: its 67 lines aren’t shown here.

arch/arm64/boot/dts/amd/amd-seattle-clks.dtsi+54−0

This diff is large: its 55 lines aren’t shown here.

arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi+172−0

This diff is large: its 173 lines aren’t shown here.

arch/arm64/boot/dts/apm-storm.dtsi+0−425

This diff is large: its 426 lines aren’t shown here.

arch/arm64/boot/dts/apm/Makefile+5−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-mustang.dtsrenamed from arch/arm64/boot/dts/apm-mustang.dts+16−0

This diff is large: its 27 lines aren’t shown here.

arch/arm64/boot/dts/apm/apm-storm.dtsi+660−0

This diff is large: its 661 lines aren’t shown here.

arch/arm64/boot/dts/arm/Makefile+7−0

This diff is large: its 8 lines aren’t shown here.

arch/arm64/boot/dts/arm/foundation-v8.dtsrenamed from arch/arm64/boot/dts/foundation-v8.dts+4−4

This diff is large: its 15 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno-clocks.dtsi+44−0

This diff is large: its 45 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno-motherboard.dtsi+129−0

This diff is large: its 130 lines aren’t shown here.

arch/arm64/boot/dts/arm/juno.dts+218−0

This diff is large: its 219 lines aren’t shown here.

arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dtsrenamed from arch/arm64/boot/dts/rtsm_ve-aemv8a.dts+4−4

This diff is large: its 15 lines aren’t shown here.

arch/arm64/boot/dts/arm/rtsm_ve-motherboard.dtsirenamed from arch/arm64/boot/dts/rtsm_ve-motherboard.dtsi+34−1

This diff is large: its 52 lines aren’t shown here.

arch/arm64/boot/dts/cavium/Makefile+5−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/boot/dts/cavium/thunder-88xx.dts+67−0

This diff is large: its 68 lines aren’t shown here.

arch/arm64/boot/dts/cavium/thunder-88xx.dtsi+401−0

This diff is large: its 402 lines aren’t shown here.

arch/arm64/boot/dts/include/dt-bindings+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm64/configs/defconfig+31−5

This diff is large: its 134 lines aren’t shown here.

arch/arm64/crypto/Kconfig+6−3

This diff is large: its 32 lines aren’t shown here.

arch/arm64/crypto/Makefile+4−0

This diff is large: its 10 lines aren’t shown here.

arch/arm64/crypto/aes-ce-ccm-glue.c+4−2

This diff is large: its 24 lines aren’t shown here.

arch/arm64/crypto/aes-ce-cipher.c+111−1

This diff is large: its 133 lines aren’t shown here.

arch/arm64/crypto/aes-ce-setkey.h+5−0

This diff is large: its 6 lines aren’t shown here.

arch/arm64/crypto/aes-glue.c+16−10

This diff is large: its 79 lines aren’t shown here.

arch/arm64/crypto/crc32-arm64.c+274−0

This diff is large: its 275 lines aren’t shown here.

arch/arm64/include/asm/Kbuild+4−2

This diff is large: its 25 lines aren’t shown here.

arch/arm64/include/asm/alternative-asm.h+29−0

This diff is large: its 30 lines aren’t shown here.

arch/arm64/include/asm/alternative.h+44−0

This diff is large: its 45 lines aren’t shown here.

arch/arm64/include/asm/arch_timer.h+7−28

This diff is large: its 50 lines aren’t shown here.

arch/arm64/include/asm/atomic.h+82−119

This diff is large: its 233 lines aren’t shown here.

arch/arm64/include/asm/barrier.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/arm64/include/asm/cache.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/cacheflush.h+5−1

This diff is large: its 18 lines aren’t shown here.

arch/arm64/include/asm/cachetype.h+20−0

This diff is large: its 27 lines aren’t shown here.

arch/arm64/include/asm/cmpxchg.h+73−0

This diff is large: its 94 lines aren’t shown here.

arch/arm64/include/asm/compat.h+9−2

This diff is large: its 25 lines aren’t shown here.

arch/arm64/include/asm/cpu.h+7−0

This diff is large: its 28 lines aren’t shown here.

arch/arm64/include/asm/cpu_ops.h+5−2

This diff is large: its 27 lines aren’t shown here.

arch/arm64/include/asm/cpufeature.h+29−0

This diff is large: its 39 lines aren’t shown here.

arch/arm64/include/asm/cpuidle.h+13−0

This diff is large: its 14 lines aren’t shown here.

arch/arm64/include/asm/cputype.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/arm64/include/asm/debug-monitors.h+19−11

This diff is large: its 57 lines aren’t shown here.

arch/arm64/include/asm/device.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm64/include/asm/dma-contiguous.h+0−28

This diff is large: its 29 lines aren’t shown here.

arch/arm64/include/asm/dma-mapping.h+15−0

This diff is large: its 22 lines aren’t shown here.

arch/arm64/include/asm/dmi.h+31−0

This diff is large: its 32 lines aren’t shown here.

arch/arm64/include/asm/elf.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/arm64/include/asm/fixmap.h+5−3

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/hardirq.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/hwcap.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm64/include/asm/insn.h+259−0

This diff is large: its 308 lines aren’t shown here.

arch/arm64/include/asm/io.h+46−102

This diff is large: its 228 lines aren’t shown here.

arch/arm64/include/asm/irq.h+2−1

This diff is large: its 10 lines aren’t shown here.

arch/arm64/include/asm/irq_work.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/kgdb.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/kvm_arm.h+22−10

This diff is large: its 77 lines aren’t shown here.

arch/arm64/include/asm/kvm_emulate.h+10−0

This diff is large: its 24 lines aren’t shown here.

arch/arm64/include/asm/kvm_host.h+18−9

This diff is large: its 76 lines aren’t shown here.

arch/arm64/include/asm/kvm_mmu.h+123−28

This diff is large: its 214 lines aren’t shown here.

arch/arm64/include/asm/memory.h+3−1

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/opcodes.h+1−0

This diff is large: its 2 lines aren’t shown here.

arch/arm64/include/asm/pci.h+37−0

This diff is large: its 38 lines aren’t shown here.

arch/arm64/include/asm/percpu.h+217−2

This diff is large: its 238 lines aren’t shown here.

arch/arm64/include/asm/pgalloc.h+4−4

This diff is large: its 33 lines aren’t shown here.

arch/arm64/include/asm/pgtable.h+46−18

This diff is large: its 146 lines aren’t shown here.

arch/arm64/include/asm/proc-fns.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/processor.h+1−3

This diff is large: its 18 lines aren’t shown here.

arch/arm64/include/asm/seccomp.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/arm64/include/asm/smp.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/arm64/include/asm/spinlock.h+2−2

This diff is large: its 15 lines aren’t shown here.

arch/arm64/include/asm/suspend.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/arm64/include/asm/thread_info.h+7−2

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/tlb.h+17−64

This diff is large: its 118 lines aren’t shown here.

arch/arm64/include/asm/traps.h+16−0

This diff is large: its 23 lines aren’t shown here.

arch/arm64/include/asm/unistd.h+4−1

This diff is large: its 19 lines aren’t shown here.

arch/arm64/include/asm/unistd32.h+4−1

This diff is large: its 13 lines aren’t shown here.

arch/arm64/include/asm/xen/page-coherent.h+1−43

This diff is large: its 45 lines aren’t shown here.

arch/arm64/include/uapi/asm/kvm.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/arm64/kernel/Makefile+7−2

This diff is large: its 35 lines aren’t shown here.

arch/arm64/kernel/alternative.c+85−0

This diff is large: its 86 lines aren’t shown here.

arch/arm64/kernel/armv8_deprecated.c+553−0

This diff is large: its 554 lines aren’t shown here.

arch/arm64/kernel/cpu_errata.c+111−0

This diff is large: its 112 lines aren’t shown here.

arch/arm64/kernel/cpuidle.c+31−0

This diff is large: its 32 lines aren’t shown here.

arch/arm64/kernel/cpuinfo.c+57−4

This diff is large: its 136 lines aren’t shown here.

arch/arm64/kernel/efi-entry.S+23−7

This diff is large: its 57 lines aren’t shown here.

arch/arm64/kernel/efi-stub.c+6−10

This diff is large: its 27 lines aren’t shown here.

arch/arm64/kernel/efi.c+43−38

This diff is large: its 148 lines aren’t shown here.

arch/arm64/kernel/entry-ftrace.S+11−10

This diff is large: its 35 lines aren’t shown here.

arch/arm64/kernel/entry.S+74−65

This diff is large: its 262 lines aren’t shown here.

arch/arm64/kernel/ftrace.c+6−4

This diff is large: its 38 lines aren’t shown here.

arch/arm64/kernel/head.S+231−209

This diff is large: its 520 lines aren’t shown here.

arch/arm64/kernel/insn.c+693−9

This diff is large: its 766 lines aren’t shown here.

arch/arm64/kernel/io.c+56−10

This diff is large: its 93 lines aren’t shown here.

arch/arm64/kernel/irq.c+1−26

This diff is large: its 34 lines aren’t shown here.

arch/arm64/kernel/jump_label.c+9−14

This diff is large: its 42 lines aren’t shown here.

arch/arm64/kernel/kgdb.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/arm64/kernel/module.c+19−0

This diff is large: its 31 lines aren’t shown here.

arch/arm64/kernel/pci.c+70−0

This diff is large: its 71 lines aren’t shown here.

arch/arm64/kernel/perf_event.c+9−3

This diff is large: its 26 lines aren’t shown here.

arch/arm64/kernel/perf_regs.c+8−0

This diff is large: its 12 lines aren’t shown here.

arch/arm64/kernel/process.c+4−34

This diff is large: its 65 lines aren’t shown here.

arch/arm64/kernel/psci.c+106−0

This diff is large: its 150 lines aren’t shown here.

arch/arm64/kernel/ptrace.c+42−2

This diff is large: its 85 lines aren’t shown here.

arch/arm64/kernel/return_address.c+1−2

This diff is large: its 15 lines aren’t shown here.

arch/arm64/kernel/setup.c+90−30

This diff is large: its 214 lines aren’t shown here.

arch/arm64/kernel/signal32.c+6−0

This diff is large: its 13 lines aren’t shown here.

arch/arm64/kernel/sleep.S+40−43

This diff is large: its 146 lines aren’t shown here.

arch/arm64/kernel/smp.c+3−1

This diff is large: its 25 lines aren’t shown here.

arch/arm64/kernel/smp_spin_table.c+18−5

This diff is large: its 58 lines aren’t shown here.

arch/arm64/kernel/stacktrace.c+1−2

This diff is large: its 12 lines aren’t shown here.

arch/arm64/kernel/suspend.c+44−22

This diff is large: its 129 lines aren’t shown here.

arch/arm64/kernel/sys_compat.c+29−20

This diff is large: its 68 lines aren’t shown here.

arch/arm64/kernel/topology.c+5−2

This diff is large: its 18 lines aren’t shown here.

arch/arm64/kernel/trace-events-emulation.h+35−0

This diff is large: its 36 lines aren’t shown here.

arch/arm64/kernel/traps.c+67−2

This diff is large: its 97 lines aren’t shown here.

arch/arm64/kernel/vmlinux.lds.S+31−2

This diff is large: its 60 lines aren’t shown here.

arch/arm64/kvm/guest.c+1−27

This diff is large: its 49 lines aren’t shown here.

arch/arm64/kvm/hyp.S+2−2

This diff is large: its 13 lines aren’t shown here.

arch/arm64/kvm/sys_regs.c+10−1

This diff is large: its 32 lines aren’t shown here.

arch/arm64/kvm/vgic-v2-switch.S+8−4

This diff is large: its 19 lines aren’t shown here.

arch/arm64/lib/clear_user.S+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/mm/Makefile+2−1

This diff is large: its 8 lines aren’t shown here.

arch/arm64/mm/cache.S+8−2

This diff is large: its 36 lines aren’t shown here.

arch/arm64/mm/dma-mapping.c+145−50

This diff is large: its 286 lines aren’t shown here.

arch/arm64/mm/dump.c+329−0

This diff is large: its 330 lines aren’t shown here.

arch/arm64/mm/fault.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/arm64/mm/flush.c+16−0

This diff is large: its 20 lines aren’t shown here.

arch/arm64/mm/init.c+10−2

This diff is large: its 41 lines aren’t shown here.

arch/arm64/mm/ioremap.c+3−90

This diff is large: its 101 lines aren’t shown here.

arch/arm64/mm/mm.h+0−1

This diff is large: its 3 lines aren’t shown here.

arch/arm64/mm/mmap.c+3−11

This diff is large: its 34 lines aren’t shown here.

arch/arm64/mm/mmu.c+104−6

This diff is large: its 143 lines aren’t shown here.

arch/arm64/mm/pageattr.c+97−0

This diff is large: its 98 lines aren’t shown here.

arch/arm64/mm/pgd.c+17−3

This diff is large: its 36 lines aren’t shown here.

arch/arm64/mm/proc.S+15−0

This diff is large: its 22 lines aren’t shown here.

arch/arm64/net/Makefile+4−0

This diff is large: its 5 lines aren’t shown here.

arch/arm64/net/bpf_jit.h+173−0

This diff is large: its 174 lines aren’t shown here.

arch/arm64/net/bpf_jit_comp.c+746−0

This diff is large: its 747 lines aren’t shown here.

arch/avr32/include/asm/Kbuild+1−1

This diff is large: its 10 lines aren’t shown here.

arch/avr32/include/asm/atomic.h+63−62

This diff is large: its 166 lines aren’t shown here.

arch/avr32/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/avr32/kernel/kprobes.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/avr32/mach-at32ap/at32ap700x.c+9−12

This diff is large: its 63 lines aren’t shown here.

arch/avr32/mach-at32ap/include/mach/atmel-mci.h+0−17

This diff is large: its 18 lines aren’t shown here.

arch/blackfin/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/blackfin/include/asm/Kbuild+1−1

This diff is large: its 13 lines aren’t shown here.

arch/blackfin/include/asm/barrier.h+51−0

This diff is large: its 58 lines aren’t shown here.

arch/blackfin/include/asm/bfin_serial.h+3−4

This diff is large: its 23 lines aren’t shown here.

arch/blackfin/include/asm/ipipe.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/blackfin/kernel/perf_event.c+5−5

This diff is large: its 45 lines aren’t shown here.

arch/blackfin/mach-bf533/boards/stamp.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/blackfin/mach-bf537/boards/cm_bf537e.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/blackfin/mach-bf537/boards/cm_bf537u.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/blackfin/mach-bf537/boards/stamp.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/blackfin/mach-bf537/boards/tcm_bf537.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/blackfin/mach-bf561/boards/cm_bf561.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/blackfin/mach-common/ints-priority.c+5−5

This diff is large: its 26 lines aren’t shown here.

arch/blackfin/mach-common/smp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/c6x/include/asm/Kbuild+1−1

This diff is large: its 15 lines aren’t shown here.

arch/cris/arch-v10/drivers/sync_serial.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/cris/arch-v10/lib/usercopy.c+7−7

This diff is large: its 46 lines aren’t shown here.

arch/cris/arch-v32/drivers/Kconfig+1−7

This diff is large: its 22 lines aren’t shown here.

arch/cris/arch-v32/drivers/Makefile+0−1

This diff is large: its 5 lines aren’t shown here.

arch/cris/arch-v32/drivers/i2c.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/cris/arch-v32/drivers/sync_serial.c+791−640

This diff is large: its 1961 lines aren’t shown here.

arch/cris/arch-v32/kernel/debugport.c+56−26

This diff is large: its 154 lines aren’t shown here.

arch/cris/arch-v32/kernel/time.c+18−11

This diff is large: its 109 lines aren’t shown here.

arch/cris/arch-v32/lib/usercopy.c+7−8

This diff is large: its 46 lines aren’t shown here.

arch/cris/arch-v32/mach-fs/pinmux.c+83−69

This diff is large: its 293 lines aren’t shown here.

arch/cris/include/arch-v32/mach-fs/mach/pinmux.h+0−2

This diff is large: its 12 lines aren’t shown here.

arch/cris/include/asm/Kbuild+2−5

This diff is large: its 22 lines aren’t shown here.

arch/cris/include/asm/atomic.h+26−33

This diff is large: its 75 lines aren’t shown here.

arch/cris/include/asm/io.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/cris/include/asm/sections.h+0−7

This diff is large: its 8 lines aren’t shown here.

arch/cris/include/uapi/asm/Kbuild+2−2

This diff is large: its 11 lines aren’t shown here.

arch/cris/include/uapi/asm/socket.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/cris/kernel/crisksyms.c+5−4

This diff is large: its 26 lines aren’t shown here.

arch/cris/kernel/traps.c+34−27

This diff is large: its 175 lines aren’t shown here.

arch/cris/mm/init.c+33−5

This diff is large: its 58 lines aren’t shown here.

arch/cris/mm/ioremap.c+2−1

This diff is large: its 13 lines aren’t shown here.

arch/frv/include/asm/Kbuild+1−1

This diff is large: its 9 lines aren’t shown here.

arch/frv/include/asm/atomic.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/frv/include/asm/io.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/frv/include/asm/processor.h+0−16

This diff is large: its 23 lines aren’t shown here.

arch/frv/include/uapi/asm/socket.h+5−0

This diff is large: its 11 lines aren’t shown here.

arch/frv/kernel/irq-mb93091.c+4−4

This diff is large: its 30 lines aren’t shown here.

arch/frv/kernel/irq-mb93093.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/frv/kernel/irq-mb93493.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/frv/kernel/setup.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/frv/kernel/time.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/frv/mm/extable.c+0−2

This diff is large: its 9 lines aren’t shown here.

arch/hexagon/include/asm/Kbuild+1−1

This diff is large: its 15 lines aren’t shown here.

arch/hexagon/include/asm/atomic.h+37−31

This diff is large: its 79 lines aren’t shown here.

arch/hexagon/include/asm/cache.h+3−1

This diff is large: its 18 lines aren’t shown here.

arch/hexagon/include/asm/cacheflush.h+19−17

This diff is large: its 65 lines aren’t shown here.

arch/hexagon/include/asm/io.h+0−5

This diff is large: its 15 lines aren’t shown here.

arch/hexagon/kernel/setup.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/hexagon/kernel/traps.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/hexagon/kernel/vmlinux.lds.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/hexagon/mm/cache.c+10−0

This diff is large: its 14 lines aren’t shown here.

arch/hexagon/mm/ioremap.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/ia64/Kconfig+1−4

This diff is large: its 33 lines aren’t shown here.

arch/ia64/Makefile+0−1

This diff is large: its 8 lines aren’t shown here.

arch/ia64/include/asm/Kbuild+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/atomic.h+88−104

This diff is large: its 233 lines aren’t shown here.

arch/ia64/include/asm/barrier.h+12−13

This diff is large: its 39 lines aren’t shown here.

arch/ia64/include/asm/hw_irq.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/io.h+4−0

This diff is large: its 11 lines aren’t shown here.

arch/ia64/include/asm/kvm_host.h+0−600

This diff is large: its 601 lines aren’t shown here.

arch/ia64/include/asm/percpu.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/ia64/include/asm/processor.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/ia64/include/asm/pvclock-abi.h+0−48

This diff is large: its 49 lines aren’t shown here.

arch/ia64/include/asm/sections.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/sn/arch.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/ia64/include/asm/sn/nodepda.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/switch_to.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/asm/syscall.h+6−0

This diff is large: its 18 lines aren’t shown here.

arch/ia64/include/asm/uaccess.h+8−8

This diff is large: its 40 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/asm/uv/uv_hub.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/include/uapi/asm/kvm.h+0−268

This diff is large: its 269 lines aren’t shown here.

arch/ia64/include/uapi/asm/siginfo.h+6−2

This diff is large: its 23 lines aren’t shown here.

arch/ia64/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/ia64/include/uapi/asm/unistd.h+2−0

This diff is large: its 8 lines aren’t shown here.

arch/ia64/kernel/acpi.c+4−5

This diff is large: its 27 lines aren’t shown here.

arch/ia64/kernel/efi.c+4−2

This diff is large: its 21 lines aren’t shown here.

arch/ia64/kernel/entry.S+2−0

This diff is large: its 9 lines aren’t shown here.

arch/ia64/kernel/irq.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/kernel/irq_ia64.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/ia64/kernel/kprobes.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/ia64/kernel/mca.c+8−8

This diff is large: its 42 lines aren’t shown here.

arch/ia64/kernel/msi_ia64.c+5−5

This diff is large: its 38 lines aren’t shown here.

arch/ia64/kernel/perfmon.c+1−11

This diff is large: its 32 lines aren’t shown here.

arch/ia64/kernel/process.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/ia64/kernel/ptrace.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/kernel/traps.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/kvm/Kconfig+0−66

This diff is large: its 67 lines aren’t shown here.

arch/ia64/kvm/Makefile+0−67

This diff is large: its 68 lines aren’t shown here.

arch/ia64/kvm/asm-offsets.c+0−241

This diff is large: its 242 lines aren’t shown here.

arch/ia64/kvm/irq.h+0−33

This diff is large: its 34 lines aren’t shown here.

arch/ia64/kvm/kvm-ia64.c+0−1972

This diff is large: its 1973 lines aren’t shown here.

arch/ia64/kvm/kvm_fw.c+0−674

This diff is large: its 675 lines aren’t shown here.

arch/ia64/kvm/kvm_lib.c+0−21

This diff is large: its 22 lines aren’t shown here.

arch/ia64/kvm/kvm_minstate.h+0−266

This diff is large: its 267 lines aren’t shown here.

arch/ia64/kvm/lapic.h+0−30

This diff is large: its 31 lines aren’t shown here.

arch/ia64/kvm/memcpy.S+0−1

This diff is large: its 2 lines aren’t shown here.

arch/ia64/kvm/memset.S+0−1

This diff is large: its 2 lines aren’t shown here.

arch/ia64/kvm/misc.h+0−94

This diff is large: its 95 lines aren’t shown here.

arch/ia64/kvm/mmio.c+0−336

This diff is large: its 337 lines aren’t shown here.

arch/ia64/kvm/optvfault.S+0−1090

This diff is large: its 1091 lines aren’t shown here.

arch/ia64/kvm/process.c+0−1024

This diff is large: its 1025 lines aren’t shown here.

arch/ia64/kvm/trampoline.S+0−1038

This diff is large: its 1039 lines aren’t shown here.

arch/ia64/kvm/vcpu.c+0−2209

This diff is large: its 2210 lines aren’t shown here.

arch/ia64/kvm/vcpu.h+0−752

This diff is large: its 753 lines aren’t shown here.

arch/ia64/kvm/vmm.c+0−99

This diff is large: its 100 lines aren’t shown here.

arch/ia64/kvm/vmm_ivt.S+0−1392

This diff is large: its 1393 lines aren’t shown here.

arch/ia64/kvm/vti.h+0−290

This diff is large: its 291 lines aren’t shown here.

arch/ia64/kvm/vtlb.c+0−640

This diff is large: its 641 lines aren’t shown here.

arch/ia64/sn/kernel/msi_sn.c+6−6

This diff is large: its 40 lines aren’t shown here.

arch/ia64/sn/kernel/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/ia64/sn/kernel/sn2/sn2_smp.c+14−14

This diff is large: its 84 lines aren’t shown here.

arch/m32r/include/asm/Kbuild+2−1

This diff is large: its 12 lines aren’t shown here.

arch/m32r/include/asm/atomic.h+58−87

This diff is large: its 192 lines aren’t shown here.

arch/m32r/include/asm/io.h+3−0

This diff is large: its 10 lines aren’t shown here.

arch/m32r/include/asm/sections.h+0−7

This diff is large: its 8 lines aren’t shown here.

arch/m32r/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/m32r/kernel/time.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/m68k/68000/Makefilerenamed from arch/m68k/platform/68000/Makefile+0−0

File renamed without changes.

arch/m68k/68000/bootlogo-vz.hrenamed from arch/m68k/platform/68000/bootlogo-vz.h+0−0

File renamed without changes.

arch/m68k/68000/bootlogo.hrenamed from arch/m68k/platform/68000/bootlogo.h+0−0

File renamed without changes.

arch/m68k/68000/entry.S+244−0

This diff is large: its 245 lines aren’t shown here.

arch/m68k/68000/head.Srenamed from arch/m68k/platform/68000/head.S+0−0

File renamed without changes.

arch/m68k/68000/ints.crenamed from arch/m68k/platform/68000/ints.c+0−0

File renamed without changes.

arch/m68k/68000/m68328.crenamed from arch/m68k/platform/68000/m68328.c+0−0

File renamed without changes.

arch/m68k/68000/m68EZ328.crenamed from arch/m68k/platform/68000/m68EZ328.c+0−0

File renamed without changes.

arch/m68k/68000/m68VZ328.crenamed from arch/m68k/platform/68000/m68VZ328.c+0−0

File renamed without changes.

arch/m68k/68000/romvec.Srenamed from arch/m68k/platform/68000/romvec.S+0−0

File renamed without changes.

arch/m68k/68000/timers.crenamed from arch/m68k/platform/68000/timers.c+0−0

File renamed without changes.

arch/m68k/68360/Makefile+12−0

This diff is large: its 13 lines aren’t shown here.

arch/m68k/68360/commproc.crenamed from arch/m68k/platform/68360/commproc.c+0−0

File renamed without changes.

arch/m68k/68360/config.crenamed from arch/m68k/platform/68360/config.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/m68k/68360/entry.S+164−0

This diff is large: its 165 lines aren’t shown here.

arch/m68k/68360/head-ram.Srenamed from arch/m68k/platform/68360/head-ram.S+2−3

This diff is large: its 9 lines aren’t shown here.

arch/m68k/68360/head-rom.Srenamed from arch/m68k/platform/68360/head-rom.S+2−3

This diff is large: its 9 lines aren’t shown here.

arch/m68k/68360/ints.crenamed from arch/m68k/platform/68360/ints.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/m68k/Kconfig.devices+2−2

This diff is large: its 18 lines aren’t shown here.

arch/m68k/Makefile+6−6

This diff is large: its 26 lines aren’t shown here.

arch/m68k/atari/config.c+27−0

This diff is large: its 41 lines aren’t shown here.

arch/m68k/atari/stdma.c+40−21

This diff is large: its 90 lines aren’t shown here.

arch/m68k/atari/stram.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/m68k/coldfire/Makefilerenamed from arch/m68k/platform/coldfire/Makefile+0−0

File renamed without changes.

arch/m68k/coldfire/cache.crenamed from arch/m68k/platform/coldfire/cache.c+0−0

File renamed without changes.

arch/m68k/coldfire/clk.crenamed from arch/m68k/platform/coldfire/clk.c+0−0

File renamed without changes.

arch/m68k/coldfire/device.crenamed from arch/m68k/platform/coldfire/device.c+0−0

File renamed without changes.

arch/m68k/coldfire/dma.crenamed from arch/m68k/platform/coldfire/dma.c+0−0

File renamed without changes.

arch/m68k/coldfire/dma_timer.crenamed from arch/m68k/platform/coldfire/dma_timer.c+0−0

File renamed without changes.

arch/m68k/coldfire/entry.S+203−0

This diff is large: its 204 lines aren’t shown here.

arch/m68k/coldfire/firebee.crenamed from arch/m68k/platform/coldfire/firebee.c+0−0

File renamed without changes.

arch/m68k/coldfire/gpio.crenamed from arch/m68k/platform/coldfire/gpio.c+0−0

File renamed without changes.

arch/m68k/coldfire/head.Srenamed from arch/m68k/platform/coldfire/head.S+0−0

File renamed without changes.

arch/m68k/coldfire/intc-2.crenamed from arch/m68k/platform/coldfire/intc-2.c+0−0

File renamed without changes.

arch/m68k/coldfire/intc-5249.crenamed from arch/m68k/platform/coldfire/intc-5249.c+0−0

File renamed without changes.

arch/m68k/coldfire/intc-525x.crenamed from arch/m68k/platform/coldfire/intc-525x.c+0−0

File renamed without changes.

arch/m68k/coldfire/intc-5272.crenamed from arch/m68k/platform/coldfire/intc-5272.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/intc-simr.crenamed from arch/m68k/platform/coldfire/intc-simr.c+0−0

File renamed without changes.

arch/m68k/coldfire/intc.crenamed from arch/m68k/platform/coldfire/intc.c+0−0

File renamed without changes.

arch/m68k/coldfire/m5206.crenamed from arch/m68k/platform/coldfire/m5206.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m520x.crenamed from arch/m68k/platform/coldfire/m520x.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m523x.crenamed from arch/m68k/platform/coldfire/m523x.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m5249.crenamed from arch/m68k/platform/coldfire/m5249.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m525x.crenamed from arch/m68k/platform/coldfire/m525x.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m5272.crenamed from arch/m68k/platform/coldfire/m5272.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m527x.crenamed from arch/m68k/platform/coldfire/m527x.c+2−2

This diff is large: its 13 lines aren’t shown here.

arch/m68k/coldfire/m528x.crenamed from arch/m68k/platform/coldfire/m528x.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m5307.crenamed from arch/m68k/platform/coldfire/m5307.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m53xx.crenamed from arch/m68k/platform/coldfire/m53xx.c+0−0

File renamed without changes.

arch/m68k/coldfire/m5407.crenamed from arch/m68k/platform/coldfire/m5407.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/coldfire/m5441x.crenamed from arch/m68k/platform/coldfire/m5441x.c+0−0

File renamed without changes.

arch/m68k/coldfire/m54xx.crenamed from arch/m68k/platform/coldfire/m54xx.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/m68k/coldfire/mcf8390.crenamed from arch/m68k/platform/coldfire/mcf8390.c+0−0

File renamed without changes.

arch/m68k/coldfire/nettel.crenamed from arch/m68k/platform/coldfire/nettel.c+0−0

File renamed without changes.

arch/m68k/coldfire/pci.crenamed from arch/m68k/platform/coldfire/pci.c+0−0

File renamed without changes.

arch/m68k/coldfire/pit.crenamed from arch/m68k/platform/coldfire/pit.c+0−0

File renamed without changes.

arch/m68k/coldfire/reset.crenamed from arch/m68k/platform/coldfire/reset.c+0−0

File renamed without changes.

arch/m68k/coldfire/sltimers.crenamed from arch/m68k/platform/coldfire/sltimers.c+0−0

File renamed without changes.

arch/m68k/coldfire/timers.crenamed from arch/m68k/platform/coldfire/timers.c+0−0

File renamed without changes.

arch/m68k/coldfire/vectors.crenamed from arch/m68k/platform/coldfire/vectors.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/include/asm/Kbuild+1−1

This diff is large: its 13 lines aren’t shown here.

arch/m68k/include/asm/atari_stdma.h+2−2

This diff is large: its 14 lines aren’t shown here.

arch/m68k/include/asm/atomic.h+48−63

This diff is large: its 141 lines aren’t shown here.

arch/m68k/include/asm/io.h+8−0

This diff is large: its 12 lines aren’t shown here.

arch/m68k/include/asm/io_mm.h+8−1

This diff is large: its 15 lines aren’t shown here.

arch/m68k/include/asm/io_no.h+9−4

This diff is large: its 27 lines aren’t shown here.

arch/m68k/include/asm/m54xxpci.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/m68k/include/asm/macintosh.h+4−0

This diff is large: its 11 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+1−0

This diff is large: its 7 lines aren’t shown here.

arch/m68k/kernel/sys_m68k.c+13−8

This diff is large: its 54 lines aren’t shown here.

arch/m68k/kernel/syscalltable.S+1−0

This diff is large: its 6 lines aren’t shown here.

arch/m68k/mac/config.c+132−14

This diff is large: its 258 lines aren’t shown here.

arch/m68k/mm/hwtest.c+43−35

This diff is large: its 105 lines aren’t shown here.

arch/m68k/mm/init.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/m68k/platform/68000/entry.S+0−244

This diff is large: its 245 lines aren’t shown here.

arch/m68k/platform/68360/Makefile+0−12

This diff is large: its 13 lines aren’t shown here.

arch/m68k/platform/68360/entry.S+0−164

This diff is large: its 165 lines aren’t shown here.

arch/m68k/platform/Makefile+0−3

This diff is large: its 4 lines aren’t shown here.

arch/m68k/platform/coldfire/entry.S+0−203

This diff is large: its 204 lines aren’t shown here.

arch/m68k/sun3/config.c+60−0

This diff is large: its 78 lines aren’t shown here.

arch/metag/include/asm/Kbuild+1−1

This diff is large: its 14 lines aren’t shown here.

arch/metag/include/asm/atomic_lnkget.h+46−75

This diff is large: its 132 lines aren’t shown here.

arch/metag/include/asm/atomic_lock1.h+31−45

This diff is large: its 87 lines aren’t shown here.

arch/metag/include/asm/barrier.h+10−9

This diff is large: its 41 lines aren’t shown here.

arch/metag/kernel/perf/perf_event.c+7−7

This diff is large: its 63 lines aren’t shown here.

arch/microblaze/Kconfig+5−0

This diff is large: its 18 lines aren’t shown here.

arch/microblaze/include/asm/Kbuild+1−1

This diff is large: its 9 lines aren’t shown here.

arch/microblaze/include/asm/io.h+0−8

This diff is large: its 13 lines aren’t shown here.

arch/microblaze/include/asm/pgtable.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/microblaze/include/asm/syscall.h+5−0

This diff is large: its 17 lines aren’t shown here.

arch/microblaze/include/asm/tlb.h+2−1

This diff is large: its 15 lines aren’t shown here.

arch/microblaze/include/asm/unistd.h+1−1

This diff is large: its 8 lines aren’t shown here.

arch/microblaze/include/uapi/asm/unistd.h+1−0

This diff is large: its 7 lines aren’t shown here.

arch/microblaze/kernel/dma.c+27−0

This diff is large: its 37 lines aren’t shown here.

arch/microblaze/kernel/ptrace.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/microblaze/kernel/syscall_table.S+1−0

This diff is large: its 5 lines aren’t shown here.

arch/microblaze/mm/consistent.c+20−5

This diff is large: its 41 lines aren’t shown here.

arch/microblaze/pci/pci-common.c+7−2

This diff is large: its 16 lines aren’t shown here.

arch/mips/Kbuild.platforms+2−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/Kconfig+81−38

This diff is large: its 344 lines aren’t shown here.

arch/mips/Kconfig.debug+13−0

This diff is large: its 18 lines aren’t shown here.

arch/mips/Makefile+21−0

This diff is large: its 48 lines aren’t shown here.

arch/mips/alchemy/common/clock.c+8−9

This diff is large: its 67 lines aren’t shown here.

arch/mips/alchemy/common/setup.c+3−3

This diff is large: its 21 lines aren’t shown here.

arch/mips/alchemy/devboards/db1300.c+46−1

This diff is large: its 77 lines aren’t shown here.

arch/mips/alchemy/devboards/db1550.c+4−5

This diff is large: its 29 lines aren’t shown here.

arch/mips/alchemy/devboards/platform.c+3−0

This diff is large: its 17 lines aren’t shown here.

arch/mips/ar7/platform.c+12−12

This diff is large: its 80 lines aren’t shown here.

arch/mips/ath25/Kconfig+16−0

This diff is large: its 17 lines aren’t shown here.

arch/mips/ath25/Makefile+16−0

This diff is large: its 17 lines aren’t shown here.

arch/mips/ath25/Platform+6−0

This diff is large: its 7 lines aren’t shown here.

arch/mips/ath25/ar2315.c+364−0

This diff is large: its 365 lines aren’t shown here.

arch/mips/ath25/ar2315.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/mips/ath25/ar2315_regs.h+410−0

This diff is large: its 411 lines aren’t shown here.

arch/mips/ath25/ar5312.c+393−0

This diff is large: its 394 lines aren’t shown here.

arch/mips/ath25/ar5312.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/mips/ath25/ar5312_regs.h+224−0

This diff is large: its 225 lines aren’t shown here.

arch/mips/ath25/board.c+234−0

This diff is large: its 235 lines aren’t shown here.

arch/mips/ath25/devices.c+125−0

This diff is large: its 126 lines aren’t shown here.

arch/mips/ath25/devices.h+43−0

This diff is large: its 44 lines aren’t shown here.

arch/mips/ath25/early_printk.c+44−0

This diff is large: its 45 lines aren’t shown here.

arch/mips/ath25/prom.c+26−0

This diff is large: its 27 lines aren’t shown here.

arch/mips/ath79/irq.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/ath79/mach-db120.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/ath79/prom.c+10−28

This diff is large: its 53 lines aren’t shown here.

arch/mips/ath79/setup.c+5−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/bcm3384/Makefile+1−0

This diff is large: its 2 lines aren’t shown here.

arch/mips/bcm3384/Platform+7−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/bcm3384/dma.c+81−0

This diff is large: its 82 lines aren’t shown here.

arch/mips/bcm3384/irq.c+193−0

This diff is large: its 194 lines aren’t shown here.

arch/mips/bcm3384/setup.c+97−0

This diff is large: its 98 lines aren’t shown here.

arch/mips/bcm47xx/bcm47xx_private.h+6−0

This diff is large: its 19 lines aren’t shown here.

arch/mips/bcm47xx/irq.c+8−0

This diff is large: its 22 lines aren’t shown here.

arch/mips/bcm47xx/nvram.c+86−69

This diff is large: its 220 lines aren’t shown here.

arch/mips/bcm47xx/setup.c+30−59

This diff is large: its 140 lines aren’t shown here.

arch/mips/bcm47xx/sprom.c+82−0

This diff is large: its 93 lines aren’t shown here.

arch/mips/bcm63xx/cpu.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/boot/.gitignore+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/boot/dts/Makefile+21−0

This diff is large: its 22 lines aren’t shown here.

arch/mips/boot/dts/bcm3384.dtsi+109−0

This diff is large: its 110 lines aren’t shown here.

arch/mips/boot/dts/bcm93384wvg.dts+32−0

This diff is large: its 33 lines aren’t shown here.

arch/mips/boot/dts/danube.dtsirenamed from arch/mips/lantiq/dts/danube.dtsi+0−0

File renamed without changes.

arch/mips/boot/dts/easy50712.dtsrenamed from arch/mips/lantiq/dts/easy50712.dts+0−0

File renamed without changes.

arch/mips/boot/dts/mt7620a.dtsirenamed from arch/mips/ralink/dts/mt7620a.dtsi+0−0

File renamed without changes.

arch/mips/boot/dts/mt7620a_eval.dtsrenamed from arch/mips/ralink/dts/mt7620a_eval.dts+0−0

File renamed without changes.

arch/mips/boot/dts/octeon_3xxx.dtsrenamed from arch/mips/cavium-octeon/octeon_3xxx.dts+0−0

File renamed without changes.

arch/mips/boot/dts/octeon_68xx.dtsrenamed from arch/mips/cavium-octeon/octeon_68xx.dts+0−0

File renamed without changes.

arch/mips/boot/dts/rt2880.dtsirenamed from arch/mips/ralink/dts/rt2880.dtsi+0−0

File renamed without changes.

arch/mips/boot/dts/rt2880_eval.dtsrenamed from arch/mips/ralink/dts/rt2880_eval.dts+0−0

File renamed without changes.

arch/mips/boot/dts/rt3050.dtsirenamed from arch/mips/ralink/dts/rt3050.dtsi+0−0

File renamed without changes.

arch/mips/boot/dts/rt3052_eval.dtsrenamed from arch/mips/ralink/dts/rt3052_eval.dts+0−0

File renamed without changes.

arch/mips/boot/dts/rt3883.dtsirenamed from arch/mips/ralink/dts/rt3883.dtsi+0−0

File renamed without changes.

arch/mips/boot/dts/rt3883_eval.dtsrenamed from arch/mips/ralink/dts/rt3883_eval.dts+0−0

File renamed without changes.

arch/mips/boot/dts/sead3.dtsrenamed from arch/mips/mti-sead3/sead3.dts+0−0

File renamed without changes.

arch/mips/boot/dts/xlp_evp.dtsrenamed from arch/mips/netlogic/dts/xlp_evp.dts+0−0

File renamed without changes.

arch/mips/boot/dts/xlp_fvp.dtsrenamed from arch/mips/netlogic/dts/xlp_fvp.dts+0−0

File renamed without changes.

arch/mips/boot/dts/xlp_gvp.dtsrenamed from arch/mips/netlogic/dts/xlp_gvp.dts+0−0

File renamed without changes.

arch/mips/boot/dts/xlp_svp.dtsrenamed from arch/mips/netlogic/dts/xlp_svp.dts+0−0

File renamed without changes.

arch/mips/cavium-octeon/.gitignore+0−2

This diff is large: its 3 lines aren’t shown here.

arch/mips/cavium-octeon/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/cavium-octeon/Makefile+0−10

This diff is large: its 14 lines aren’t shown here.

arch/mips/cavium-octeon/dma-octeon.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/mips/cavium-octeon/executive/octeon-model.c+35−14

This diff is large: its 70 lines aren’t shown here.

arch/mips/cavium-octeon/octeon-irq.c+17−15

This diff is large: its 126 lines aren’t shown here.

arch/mips/cavium-octeon/octeon-platform.c+272−2

This diff is large: its 339 lines aren’t shown here.

arch/mips/cavium-octeon/setup.c+2−11

This diff is large: its 34 lines aren’t shown here.

arch/mips/configs/bcm3384_defconfig+78−0

This diff is large: its 79 lines aren’t shown here.

arch/mips/configs/cavium_octeon_defconfig+3−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/configs/db1xxx_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/configs/lemote2f_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/configs/loongson3_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/configs/nlm_xlp_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/configs/nlm_xlr_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/configs/sead3_defconfig+1−1

This diff is large: its 10 lines aren’t shown here.

arch/mips/configs/sead3micro_defconfig+1−1

This diff is large: its 10 lines aren’t shown here.

arch/mips/fw/lib/cmdline.c+4−4

This diff is large: its 26 lines aren’t shown here.

arch/mips/include/asm/Kbuild+2−1

This diff is large: its 11 lines aren’t shown here.

arch/mips/include/asm/asmmacro-32.h+6−0

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/asmmacro.h+18−0

This diff is large: its 128 lines aren’t shown here.

arch/mips/include/asm/atomic.h+202−375

This diff is large: its 654 lines aren’t shown here.

arch/mips/include/asm/barrier.h+5−56

This diff is large: its 85 lines aren’t shown here.

arch/mips/include/asm/bitops.h+18−17

This diff is large: its 154 lines aren’t shown here.

arch/mips/include/asm/bmips.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/bootinfo.h+5−8

This diff is large: its 33 lines aren’t shown here.

arch/mips/include/asm/clock.h+0−3

This diff is large: its 10 lines aren’t shown here.

arch/mips/include/asm/cmpxchg.h+15−12

This diff is large: its 76 lines aren’t shown here.

arch/mips/include/asm/compiler.h+8−0

This diff is large: its 13 lines aren’t shown here.

arch/mips/include/asm/cop2.h+4−4

This diff is large: its 20 lines aren’t shown here.

arch/mips/include/asm/cpu-features.h+14−0

This diff is large: its 26 lines aren’t shown here.

arch/mips/include/asm/cpu-info.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/include/asm/cpu.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/include/asm/edac.h+4−2

This diff is large: its 20 lines aren’t shown here.

arch/mips/include/asm/elf.h+59−15

This diff is large: its 147 lines aren’t shown here.

arch/mips/include/asm/fpregdef.h+14−0

This diff is large: its 21 lines aren’t shown here.

arch/mips/include/asm/fpu.h+43−10

This diff is large: its 106 lines aren’t shown here.

arch/mips/include/asm/fpu_emulator.h+12−12

This diff is large: its 38 lines aren’t shown here.

arch/mips/include/asm/ftrace.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/asm/futex.h+19−8

This diff is large: its 90 lines aren’t shown here.

arch/mips/include/asm/gic.h+0−384

This diff is large: its 385 lines aren’t shown here.

arch/mips/include/asm/hpet.h+73−0

This diff is large: its 74 lines aren’t shown here.

arch/mips/include/asm/idle.h+0−8

This diff is large: its 28 lines aren’t shown here.

arch/mips/include/asm/io.h+4−4

This diff is large: its 36 lines aren’t shown here.

arch/mips/include/asm/irq.h+3−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/irq_cpu.h+2−2

This diff is large: its 11 lines aren’t shown here.

arch/mips/include/asm/jump_label.h+7−1

This diff is large: its 17 lines aren’t shown here.

arch/mips/include/asm/kvm_host.h+11−5

This diff is large: its 29 lines aren’t shown here.

arch/mips/include/asm/mach-ath25/ath25_platform.h+73−0

This diff is large: its 74 lines aren’t shown here.

arch/mips/include/asm/mach-ath25/cpu-feature-overrides.h+64−0

This diff is large: its 65 lines aren’t shown here.

arch/mips/include/asm/mach-ath25/dma-coherence.h+82−0

This diff is large: its 83 lines aren’t shown here.

arch/mips/include/asm/mach-ath25/gpio.h+16−0

This diff is large: its 17 lines aren’t shown here.

arch/mips/include/asm/mach-ath25/war.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/mips/include/asm/mach-au1x00/cpu-feature-overrides.h+12−0

This diff is large: its 31 lines aren’t shown here.

arch/mips/include/asm/mach-au1x00/ioremap.h+5−5

This diff is large: its 29 lines aren’t shown here.

arch/mips/include/asm/mach-bcm3384/dma-coherence.h+48−0

This diff is large: its 49 lines aren’t shown here.

arch/mips/include/asm/mach-bcm3384/war.h+24−0

This diff is large: its 25 lines aren’t shown here.

arch/mips/include/asm/mach-bcm47xx/bcm47xx_nvram.h+2−34

This diff is large: its 43 lines aren’t shown here.

arch/mips/include/asm/mach-bcm63xx/ioremap.h+3−3

This diff is large: its 24 lines aren’t shown here.

arch/mips/include/asm/mach-cavium-octeon/cpu-feature-overrides.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/mach-generic/ioremap.h+2−2

This diff is large: its 15 lines aren’t shown here.

arch/mips/include/asm/mach-generic/irq.h+6−0

This diff is large: its 11 lines aren’t shown here.

arch/mips/include/asm/mach-lantiq/lantiq.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/boot_param.h+46−3

This diff is large: its 87 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/cpu-feature-overrides.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/dma-coherence.h+3−3

This diff is large: its 27 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/irq.h+1−2

This diff is large: its 10 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/loongson.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/loongson_hwmon.h+55−0

This diff is large: its 56 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/machine.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/topology.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/mach-loongson/workarounds.h+7−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/cpufreq.h+23−0

This diff is large: its 24 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/loongson1.h+7−1

This diff is large: its 29 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/platform.h+6−4

This diff is large: its 17 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/regs-clk.h+20−3

This diff is large: its 36 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/regs-mux.h+67−0

This diff is large: its 68 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/regs-pwm.h+29−0

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/mach-loongson1/regs-wdt.h+4−7

This diff is large: its 24 lines aren’t shown here.

arch/mips/include/asm/mach-malta/irq.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/mach-pmcs-msp71xx/msp_regops.h+13−12

This diff is large: its 73 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/mt7620.h+48−16

This diff is large: its 98 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/pinmux.h+55−0

This diff is large: its 56 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/ralink_regs.h+7−0

This diff is large: its 14 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/rt305x.h+20−15

This diff is large: its 45 lines aren’t shown here.

arch/mips/include/asm/mach-ralink/rt3883.h+9−7

This diff is large: its 30 lines aren’t shown here.

arch/mips/include/asm/mach-sead3/irq.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/mach-tx39xx/ioremap.h+2−2

This diff is large: its 15 lines aren’t shown here.

arch/mips/include/asm/mach-tx49xx/ioremap.h+2−2

This diff is large: its 15 lines aren’t shown here.

arch/mips/include/asm/mips-boards/maltaint.h+8−16

This diff is large: its 61 lines aren’t shown here.

arch/mips/include/asm/mips-boards/sead3int.h+14−1

This diff is large: its 25 lines aren’t shown here.

arch/mips/include/asm/mips-cm.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/mips-cpc.h+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/asm/mipsregs.h+55−1

This diff is large: its 114 lines aren’t shown here.

arch/mips/include/asm/octeon/cvmx-cmd-queue.h+3−1

This diff is large: its 18 lines aren’t shown here.

arch/mips/include/asm/octeon/cvmx-pow.h+27−42

This diff is large: its 132 lines aren’t shown here.

arch/mips/include/asm/octeon/cvmx.h+0−63

This diff is large: its 68 lines aren’t shown here.

arch/mips/include/asm/octeon/octeon-feature.h+0−52

This diff is large: its 73 lines aren’t shown here.

arch/mips/include/asm/octeon/octeon-model.h+1−2

This diff is large: its 10 lines aren’t shown here.

arch/mips/include/asm/paccess.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/include/asm/page.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/pci.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/pgtable-32.h+53−51

This diff is large: its 151 lines aren’t shown here.

arch/mips/include/asm/pgtable-bits.h+48−32

This diff is large: its 135 lines aren’t shown here.

arch/mips/include/asm/pgtable.h+19−9

This diff is large: its 85 lines aren’t shown here.

arch/mips/include/asm/processor.h+0−6

This diff is large: its 13 lines aren’t shown here.

arch/mips/include/asm/prom.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/r4kcache.h+4−59

This diff is large: its 92 lines aren’t shown here.

arch/mips/include/asm/spinlock.h+26−24

This diff is large: its 155 lines aren’t shown here.

arch/mips/include/asm/suspend.h+0−7

This diff is large: its 8 lines aren’t shown here.

arch/mips/include/asm/syscall.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/asm/thread_info.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/include/asm/time.h+2−4

This diff is large: its 22 lines aren’t shown here.

arch/mips/include/asm/types.h+1−17

This diff is large: its 25 lines aren’t shown here.

arch/mips/include/asm/uaccess.h+10−35

This diff is large: its 95 lines aren’t shown here.

arch/mips/include/asm/uasm.h+2−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/include/uapi/asm/inst.h+4−3

This diff is large: its 14 lines aren’t shown here.

arch/mips/include/uapi/asm/ioctls.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/uapi/asm/ptrace.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/mips/include/uapi/asm/siginfo.h+4−0

This diff is large: its 11 lines aren’t shown here.

arch/mips/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/mips/include/uapi/asm/swab.h+14−4

This diff is large: its 51 lines aren’t shown here.

arch/mips/include/uapi/asm/unistd.h+9−6

This diff is large: its 59 lines aren’t shown here.

arch/mips/jz4740/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/kernel/Makefile+4−6

This diff is large: its 35 lines aren’t shown here.

arch/mips/kernel/bmips_vec.S+0−3

This diff is large: its 14 lines aren’t shown here.

arch/mips/kernel/branch.c+2−6

This diff is large: its 22 lines aren’t shown here.

arch/mips/kernel/cevt-gic.c+0−105

This diff is large: its 106 lines aren’t shown here.

arch/mips/kernel/cevt-r4k.c+3−3

This diff is large: its 23 lines aren’t shown here.

arch/mips/kernel/cps-vec.S+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/cpu-probe.c+124−6

This diff is large: its 328 lines aren’t shown here.

arch/mips/kernel/crash_dump.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/kernel/csrc-gic.c+0−40

This diff is large: its 41 lines aren’t shown here.

arch/mips/kernel/elf.c+191−0

This diff is large: its 192 lines aren’t shown here.

arch/mips/kernel/genex.S+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/kernel/i8259.c+19−5

This diff is large: its 51 lines aren’t shown here.

arch/mips/kernel/idle.c+0−3

This diff is large: its 10 lines aren’t shown here.

arch/mips/kernel/irq-gic.c+0−402

This diff is large: its 403 lines aren’t shown here.

arch/mips/kernel/irq_cpu.c+28−20

This diff is large: its 88 lines aren’t shown here.

arch/mips/kernel/jump_label.c+32−10

This diff is large: its 64 lines aren’t shown here.

arch/mips/kernel/kprobes.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/mips/kernel/mips-cm.c+6−6

This diff is large: its 47 lines aren’t shown here.

arch/mips/kernel/mips-cpc.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/kernel/mips_ksyms.c+0−4

This diff is large: its 20 lines aren’t shown here.

arch/mips/kernel/perf_event_mipsxx.c+17−27

This diff is large: its 114 lines aren’t shown here.

arch/mips/kernel/process.c+36−18

This diff is large: its 91 lines aren’t shown here.

arch/mips/kernel/prom.c+18−0

This diff is large: its 30 lines aren’t shown here.

arch/mips/kernel/ptrace.c+2−4

This diff is large: its 20 lines aren’t shown here.

arch/mips/kernel/r2300_fpu.S+6−0

This diff is large: its 34 lines aren’t shown here.

arch/mips/kernel/r2300_switch.S+5−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/r4k_fpu.S+25−2

This diff is large: its 110 lines aren’t shown here.

arch/mips/kernel/r4k_switch.S+14−1

This diff is large: its 49 lines aren’t shown here.

arch/mips/kernel/r6000_fpu.S+5−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/rtlx.c+2−2

This diff is large: its 15 lines aren’t shown here.

arch/mips/kernel/scall32-o32.S+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/kernel/scall64-64.S+1−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/kernel/scall64-n32.S+1−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/kernel/scall64-o32.S+1−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/kernel/setup.c+18−8

This diff is large: its 97 lines aren’t shown here.

arch/mips/kernel/signal.c+5−5

This diff is large: its 27 lines aren’t shown here.

arch/mips/kernel/smp-bmips.c+74−42

This diff is large: its 223 lines aren’t shown here.

arch/mips/kernel/smp-cmp.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/smp-cps.c+3−3

This diff is large: its 26 lines aren’t shown here.

arch/mips/kernel/smp-gic.c+1−1

This diff is large: its 11 lines aren’t shown here.

arch/mips/kernel/smp-mt.c+3−3

This diff is large: its 34 lines aren’t shown here.

arch/mips/kernel/syscall.c+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/kernel/traps.c+60−6

This diff is large: its 87 lines aren’t shown here.

arch/mips/kernel/vdso.c+14−1

This diff is large: its 32 lines aren’t shown here.

arch/mips/kvm/mips.c+1−39

This diff is large: its 90 lines aren’t shown here.

arch/mips/lantiq/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/lantiq/Makefile+0−2

This diff is large: its 9 lines aren’t shown here.

arch/mips/lantiq/dts/Makefile+0−1

This diff is large: its 2 lines aren’t shown here.

arch/mips/lantiq/falcon/sysctrl.c+7−6

This diff is large: its 41 lines aren’t shown here.

arch/mips/lantiq/irq.c+31−25

This diff is large: its 87 lines aren’t shown here.

arch/mips/lantiq/prom.c+8−10

This diff is large: its 39 lines aren’t shown here.

arch/mips/lantiq/xway/Makefile+2−0

This diff is large: its 6 lines aren’t shown here.

arch/mips/lantiq/xway/dcdc.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/lantiq/xway/dma.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/lantiq/xway/gptu.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/lantiq/xway/reset.c+69−1

This diff is large: its 87 lines aren’t shown here.

arch/mips/lantiq/xway/sysctrl.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/lantiq/xway/vmmc.c+69−0

This diff is large: its 70 lines aren’t shown here.

arch/mips/lantiq/xway/xrx200_phy_fw.c+22−2

This diff is large: its 38 lines aren’t shown here.

arch/mips/lasat/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/lib/csum_partial.S+8−2

This diff is large: its 28 lines aren’t shown here.

arch/mips/lib/iomap.c+9−9

This diff is large: its 64 lines aren’t shown here.

arch/mips/lib/memcpy.S+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/lib/memset.S+2−4

This diff is large: its 20 lines aren’t shown here.

arch/mips/lib/mips-atomic.c+0−20

This diff is large: its 70 lines aren’t shown here.

arch/mips/lib/r3k_dump_tlb.c+6−5

This diff is large: its 39 lines aren’t shown here.

arch/mips/lib/strlen_user.S+0−3

This diff is large: its 18 lines aren’t shown here.

arch/mips/lib/strnlen_user.S+4−2

This diff is large: its 14 lines aren’t shown here.

arch/mips/loongson/Kconfig+17−0

This diff is large: its 38 lines aren’t shown here.

arch/mips/loongson/common/Makefile+2−1

This diff is large: its 10 lines aren’t shown here.

arch/mips/loongson/common/cs5536/cs5536_pci.c+13−12

This diff is large: its 42 lines aren’t shown here.

arch/mips/loongson/common/dma-swiotlb.c+14−0

This diff is large: its 26 lines aren’t shown here.

arch/mips/loongson/common/early_printk.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/loongson/common/env.c+26−2

This diff is large: its 84 lines aren’t shown here.

arch/mips/loongson/common/gpio.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/loongson/common/init.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/loongson/common/machtype.c+10−13

This diff is large: its 30 lines aren’t shown here.

arch/mips/loongson/common/rtc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/loongson/common/serial.c+49−17

This diff is large: its 88 lines aren’t shown here.

arch/mips/loongson/common/setup.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/loongson/common/time.c+5−0

This diff is large: its 20 lines aren’t shown here.

arch/mips/loongson/common/uart_base.c+14−16

This diff is large: its 55 lines aren’t shown here.

arch/mips/loongson/lemote-2f/clock.c+3−2

This diff is large: its 20 lines aren’t shown here.

arch/mips/loongson/lemote-2f/irq.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/mips/loongson/lemote-2f/reset.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/loongson/loongson-3/Makefile+3−1

This diff is large: its 12 lines aren’t shown here.

arch/mips/loongson/loongson-3/hpet.c+257−0

This diff is large: its 258 lines aren’t shown here.

arch/mips/loongson/loongson-3/irq.c+9−7

This diff is large: its 46 lines aren’t shown here.

arch/mips/loongson/loongson-3/numa.c+10−3

This diff is large: its 34 lines aren’t shown here.

arch/mips/loongson/loongson-3/platform.c+43−0

This diff is large: its 44 lines aren’t shown here.

arch/mips/loongson/loongson-3/smp.c+48−28

This diff is large: its 170 lines aren’t shown here.

arch/mips/loongson1/Kconfig+40−2

This diff is large: its 58 lines aren’t shown here.

arch/mips/loongson1/common/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

arch/mips/loongson1/common/clock.c+0−28

This diff is large: its 29 lines aren’t shown here.

arch/mips/loongson1/common/platform.c+123−18

This diff is large: its 211 lines aren’t shown here.

arch/mips/loongson1/common/prom.c+13−17

This diff is large: its 60 lines aren’t shown here.

arch/mips/loongson1/common/reset.c+14−6

This diff is large: its 41 lines aren’t shown here.

arch/mips/loongson1/common/time.c+226−0

This diff is large: its 227 lines aren’t shown here.

arch/mips/loongson1/ls1b/board.c+7−5

This diff is large: its 25 lines aren’t shown here.

arch/mips/math-emu/cp1emu.c+10−9

This diff is large: its 56 lines aren’t shown here.

arch/mips/math-emu/ieee754dp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/math-emu/ieee754sp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/mm/Makefile+7−3

This diff is large: its 21 lines aren’t shown here.

arch/mips/mm/c-r4k.c+43−0

This diff is large: its 57 lines aren’t shown here.

arch/mips/mm/dma-default.c+30−12

This diff is large: its 83 lines aren’t shown here.

arch/mips/mm/gup.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/mips/mm/init.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/mm/ioremap.c+9−9

This diff is large: its 52 lines aren’t shown here.

arch/mips/mm/sc-r5k.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/mm/tlb-r4k.c+5−1

This diff is large: its 41 lines aren’t shown here.

arch/mips/mm/tlbex.c+23−11

This diff is large: its 129 lines aren’t shown here.

arch/mips/mm/uasm-mips.c+2−0

This diff is large: its 12 lines aren’t shown here.

arch/mips/mm/uasm.c+8−6

This diff is large: its 31 lines aren’t shown here.

arch/mips/mti-malta/Makefile+2−1

This diff is large: its 11 lines aren’t shown here.

arch/mips/mti-malta/malta-init.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/mti-malta/malta-int.c+40−287

This diff is large: its 438 lines aren’t shown here.

arch/mips/mti-malta/malta-time.c+19−32

This diff is large: its 137 lines aren’t shown here.

arch/mips/mti-sead3/Makefile+0−5

This diff is large: its 15 lines aren’t shown here.

arch/mips/mti-sead3/leds-sead3.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/mti-sead3/sead3-ehci.c+7−1

This diff is large: its 29 lines aren’t shown here.

arch/mips/mti-sead3/sead3-i2c-drv.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/mti-sead3/sead3-i2c.c+1−7

This diff is large: its 21 lines aren’t shown here.

arch/mips/mti-sead3/sead3-int.c+8−123

This diff is large: its 157 lines aren’t shown here.

arch/mips/mti-sead3/sead3-leds.c+2−6

This diff is large: its 19 lines aren’t shown here.

arch/mips/mti-sead3/sead3-net.c+10−4

This diff is large: its 48 lines aren’t shown here.

arch/mips/mti-sead3/sead3-pic32-bus.c+0−102

This diff is large: its 103 lines aren’t shown here.

arch/mips/mti-sead3/sead3-pic32-i2c-drv.c+0−423

This diff is large: its 424 lines aren’t shown here.

arch/mips/mti-sead3/sead3-platform.c+14−4

This diff is large: its 43 lines aren’t shown here.

arch/mips/mti-sead3/sead3-serial.c+0−45

This diff is large: its 46 lines aren’t shown here.

arch/mips/mti-sead3/sead3-time.c+10−25

This diff is large: its 66 lines aren’t shown here.

arch/mips/net/bpf_jit.c+26−64

This diff is large: its 200 lines aren’t shown here.

arch/mips/netlogic/Kconfig+4−0

This diff is large: its 32 lines aren’t shown here.

arch/mips/netlogic/Makefile+0−1

This diff is large: its 5 lines aren’t shown here.

arch/mips/netlogic/dts/Makefile+0−4

This diff is large: its 5 lines aren’t shown here.

arch/mips/netlogic/xlp/Makefile+8−4

This diff is large: its 15 lines aren’t shown here.

arch/mips/oprofile/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/oprofile/backtrace.c+4−3

This diff is large: its 35 lines aren’t shown here.

arch/mips/oprofile/common.c+10−1

This diff is large: its 34 lines aren’t shown here.

arch/mips/oprofile/op_model_loongson3.c+220−0

This diff is large: its 221 lines aren’t shown here.

arch/mips/oprofile/op_model_mipsxx.c+14−4

This diff is large: its 46 lines aren’t shown here.

arch/mips/pci/Makefile+2−0

This diff is large: its 16 lines aren’t shown here.

arch/mips/pci/msi-octeon.c+3−5

This diff is large: its 24 lines aren’t shown here.

arch/mips/pci/msi-xlp.c+7−9

This diff is large: its 47 lines aren’t shown here.

arch/mips/pci/ops-bcm63xx.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/pci/ops-nile4.c+1−11

This diff is large: its 50 lines aren’t shown here.

arch/mips/pci/ops-pmcmsp.c+0−12

This diff is large: its 48 lines aren’t shown here.

arch/mips/pci/pci-alchemy.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mips/pci/pci-ar2315.c+511−0

This diff is large: its 512 lines aren’t shown here.

arch/mips/pci/pci-ar71xx.c+0−14

This diff is large: its 76 lines aren’t shown here.

arch/mips/pci/pci-ar724x.c+0−24

This diff is large: its 130 lines aren’t shown here.

arch/mips/pci/pci-lantiq.c+1−7

This diff is large: its 27 lines aren’t shown here.

arch/mips/pci/pci-octeon.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/pci/pci-rt2880.c+285−0

This diff is large: its 286 lines aren’t shown here.

arch/mips/pci/pci-rt3883.c+0−10

This diff is large: its 65 lines aren’t shown here.

arch/mips/pci/pci-tx4939.c+1−1

This diff is large: its 7 lines aren’t shown here.

arch/mips/pci/pci-xlr.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/pmcs-msp71xx/msp_irq.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/pmcs-msp71xx/msp_irq_cic.c+2−2

This diff is large: its 14 lines aren’t shown here.

arch/mips/pmcs-msp71xx/msp_prom.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/power/cpu.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/ralink/Kconfig+6−1

This diff is large: its 40 lines aren’t shown here.

arch/mips/ralink/Makefile+3−1

This diff is large: its 15 lines aren’t shown here.

arch/mips/ralink/bootrom.c+48−0

This diff is large: its 49 lines aren’t shown here.

arch/mips/ralink/clk.c+6−0

This diff is large: its 13 lines aren’t shown here.

arch/mips/ralink/common.h+0−19

This diff is large: its 26 lines aren’t shown here.

arch/mips/ralink/dts/Makefile+0−4

This diff is large: its 5 lines aren’t shown here.

arch/mips/ralink/early_printk.c+30−15

This diff is large: its 64 lines aren’t shown here.

arch/mips/ralink/ill_acc.c+87−0

This diff is large: its 88 lines aren’t shown here.

arch/mips/ralink/irq.c+33−12

This diff is large: its 93 lines aren’t shown here.

arch/mips/ralink/mt7620.c+312−153

This diff is large: its 534 lines aren’t shown here.

arch/mips/ralink/of.c+19−13

This diff is large: its 54 lines aren’t shown here.

arch/mips/ralink/prom.c+1−0

This diff is large: its 8 lines aren’t shown here.

arch/mips/ralink/rt288x.c+22−43

This diff is large: its 96 lines aren’t shown here.

arch/mips/ralink/rt305x.c+68−85

This diff is large: its 186 lines aren’t shown here.

arch/mips/ralink/rt3883.c+42−132

This diff is large: its 205 lines aren’t shown here.

arch/mips/ralink/timer.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/mips/rb532/gpio.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/rb532/prom.c+4−4

This diff is large: its 22 lines aren’t shown here.

arch/mips/sgi-ip22/ip22-mc.c+2−4

This diff is large: its 17 lines aren’t shown here.

arch/mips/sgi-ip22/ip28-berr.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/mips/sgi-ip27/ip27-klnuma.c+2−3

This diff is large: its 11 lines aren’t shown here.

arch/mips/sgi-ip27/ip27-memory.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/mips/sibyte/Makefile+1−0

This diff is large: its 5 lines aren’t shown here.

arch/mips/sibyte/common/cfe.c+4−4

This diff is large: its 29 lines aren’t shown here.

arch/mips/sibyte/swarm/platform.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/sibyte/swarm/rtc_m41t81.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/mips/sibyte/swarm/rtc_xicor1241.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/mips/sibyte/swarm/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mips/txx9/generic/setup.c+2−2

This diff is large: its 14 lines aren’t shown here.

arch/mips/txx9/generic/setup_tx4927.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/mips/txx9/generic/setup_tx4938.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/mips/txx9/generic/setup_tx4939.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/mips/txx9/rbtx4939/setup.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/mn10300/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/mn10300/include/asm/Kbuild+2−1

This diff is large: its 11 lines aren’t shown here.

arch/mn10300/include/asm/atomic.h+42−83

This diff is large: its 153 lines aren’t shown here.

arch/mn10300/include/asm/io.h+4−0

This diff is large: its 11 lines aren’t shown here.

arch/mn10300/include/asm/sections.h+0−1

This diff is large: its 2 lines aren’t shown here.

arch/mn10300/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/nios2/Kconfig+206−0

This diff is large: its 207 lines aren’t shown here.

arch/nios2/Kconfig.debug+17−0

This diff is large: its 18 lines aren’t shown here.

arch/nios2/Makefile+75−0

This diff is large: its 76 lines aren’t shown here.

arch/nios2/boot/Makefile+52−0

This diff is large: its 53 lines aren’t shown here.

arch/nios2/boot/dts/3c120_devboard.dts+164−0

This diff is large: its 165 lines aren’t shown here.

arch/nios2/boot/install.sh+52−0

This diff is large: its 53 lines aren’t shown here.

arch/nios2/boot/linked_dtb.S+19−0

This diff is large: its 20 lines aren’t shown here.

arch/nios2/configs/3c120_defconfig+77−0

This diff is large: its 78 lines aren’t shown here.

arch/nios2/include/asm/Kbuild+65−0

This diff is large: its 66 lines aren’t shown here.

arch/nios2/include/asm/asm-macros.h+309−0

This diff is large: its 310 lines aren’t shown here.

arch/nios2/include/asm/asm-offsets.h+20−0

This diff is large: its 21 lines aren’t shown here.

arch/nios2/include/asm/cache.h+36−0

This diff is large: its 37 lines aren’t shown here.

arch/nios2/include/asm/cacheflush.h+52−0

This diff is large: its 53 lines aren’t shown here.

arch/nios2/include/asm/checksum.h+78−0

This diff is large: its 79 lines aren’t shown here.

arch/nios2/include/asm/cmpxchg.h+61−0

This diff is large: its 62 lines aren’t shown here.

arch/nios2/include/asm/cpuinfo.h+57−0

This diff is large: its 58 lines aren’t shown here.

arch/nios2/include/asm/delay.h+21−0

This diff is large: its 22 lines aren’t shown here.

arch/nios2/include/asm/dma-mapping.h+140−0

This diff is large: its 141 lines aren’t shown here.

arch/nios2/include/asm/elf.h+101−0

This diff is large: its 102 lines aren’t shown here.

arch/nios2/include/asm/entry.h+120−0

This diff is large: its 121 lines aren’t shown here.

arch/nios2/include/asm/io.h+63−0

This diff is large: its 64 lines aren’t shown here.

arch/nios2/include/asm/irq.h+28−0

This diff is large: its 29 lines aren’t shown here.

arch/nios2/include/asm/irqflags.h+72−0

This diff is large: its 73 lines aren’t shown here.

arch/nios2/include/asm/linkage.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/nios2/include/asm/mmu.h+16−0

This diff is large: its 17 lines aren’t shown here.

arch/nios2/include/asm/mmu_context.h+66−0

This diff is large: its 67 lines aren’t shown here.

arch/nios2/include/asm/mutex.h+1−0

This diff is large: its 2 lines aren’t shown here.

arch/nios2/include/asm/page.h+109−0

This diff is large: its 110 lines aren’t shown here.

arch/nios2/include/asm/pgalloc.h+86−0

This diff is large: its 87 lines aren’t shown here.

arch/nios2/include/asm/pgtable-bits.h+35−0

This diff is large: its 36 lines aren’t shown here.

arch/nios2/include/asm/pgtable.h+310−0

This diff is large: its 311 lines aren’t shown here.

arch/nios2/include/asm/processor.h+103−0

This diff is large: its 104 lines aren’t shown here.

arch/nios2/include/asm/ptrace.h+33−0

This diff is large: its 34 lines aren’t shown here.

arch/nios2/include/asm/registers.h+71−0

This diff is large: its 72 lines aren’t shown here.

arch/nios2/include/asm/setup.h+38−0

This diff is large: its 39 lines aren’t shown here.

arch/nios2/include/asm/signal.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/nios2/include/asm/string.h+24−0

This diff is large: its 25 lines aren’t shown here.

arch/nios2/include/asm/switch_to.h+31−0

This diff is large: its 32 lines aren’t shown here.

arch/nios2/include/asm/syscall.h+138−0

This diff is large: its 139 lines aren’t shown here.

arch/nios2/include/asm/syscalls.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/nios2/include/asm/thread_info.h+120−0

This diff is large: its 121 lines aren’t shown here.

arch/nios2/include/asm/timex.h+24−0

This diff is large: its 25 lines aren’t shown here.

arch/nios2/include/asm/tlb.h+34−0

This diff is large: its 35 lines aren’t shown here.

arch/nios2/include/asm/tlbflush.h+46−0

This diff is large: its 47 lines aren’t shown here.

arch/nios2/include/asm/traps.h+19−0

This diff is large: its 20 lines aren’t shown here.

arch/nios2/include/asm/uaccess.h+231−0

This diff is large: its 232 lines aren’t shown here.

arch/nios2/include/asm/ucontext.h+32−0

This diff is large: its 33 lines aren’t shown here.

arch/nios2/include/uapi/asm/Kbuild+4−0

This diff is large: its 5 lines aren’t shown here.

arch/nios2/include/uapi/asm/byteorder.h+22−0

This diff is large: its 23 lines aren’t shown here.

arch/nios2/include/uapi/asm/elf.h+67−0

This diff is large: its 68 lines aren’t shown here.

arch/nios2/include/uapi/asm/ptrace.h+120−0

This diff is large: its 121 lines aren’t shown here.

arch/nios2/include/uapi/asm/sigcontext.h+28−0

This diff is large: its 29 lines aren’t shown here.

arch/nios2/include/uapi/asm/signal.h+23−0

This diff is large: its 24 lines aren’t shown here.

arch/nios2/include/uapi/asm/swab.h+37−0

This diff is large: its 38 lines aren’t shown here.

arch/nios2/include/uapi/asm/unistd.h+25−0

This diff is large: its 26 lines aren’t shown here.

arch/nios2/kernel/Makefile+24−0

This diff is large: its 25 lines aren’t shown here.

arch/nios2/kernel/asm-offsets.c+87−0

This diff is large: its 88 lines aren’t shown here.

arch/nios2/kernel/cpuinfo.c+198−0

This diff is large: its 199 lines aren’t shown here.

arch/nios2/kernel/entry.S+539−0

This diff is large: its 540 lines aren’t shown here.

arch/nios2/kernel/head.S+175−0

This diff is large: its 176 lines aren’t shown here.

arch/nios2/kernel/insnemu.S+592−0

This diff is large: its 593 lines aren’t shown here.

arch/nios2/kernel/irq.c+93−0

This diff is large: its 94 lines aren’t shown here.

arch/nios2/kernel/misaligned.c+256−0

This diff is large: its 257 lines aren’t shown here.

arch/nios2/kernel/module.c+138−0

This diff is large: its 139 lines aren’t shown here.

arch/nios2/kernel/nios2_ksyms.c+33−0

This diff is large: its 34 lines aren’t shown here.

arch/nios2/kernel/process.c+258−0

This diff is large: its 259 lines aren’t shown here.

arch/nios2/kernel/prom.c+65−0

This diff is large: its 66 lines aren’t shown here.

arch/nios2/kernel/ptrace.c+166−0

This diff is large: its 167 lines aren’t shown here.

arch/nios2/kernel/setup.c+218−0

This diff is large: its 219 lines aren’t shown here.

arch/nios2/kernel/signal.c+323−0

This diff is large: its 324 lines aren’t shown here.

arch/nios2/kernel/sys_nios2.c+53−0

This diff is large: its 54 lines aren’t shown here.

arch/nios2/kernel/syscall_table.c+29−0

This diff is large: its 30 lines aren’t shown here.

arch/nios2/kernel/time.c+308−0

This diff is large: its 309 lines aren’t shown here.

arch/nios2/kernel/traps.c+185−0

This diff is large: its 186 lines aren’t shown here.

arch/nios2/kernel/vmlinux.lds.S+75−0

This diff is large: its 76 lines aren’t shown here.

arch/nios2/lib/Makefile+8−0

This diff is large: its 9 lines aren’t shown here.

arch/nios2/lib/delay.c+52−0

This diff is large: its 53 lines aren’t shown here.

arch/nios2/lib/memcpy.c+202−0

This diff is large: its 203 lines aren’t shown here.

arch/nios2/lib/memmove.c+82−0

This diff is large: its 83 lines aren’t shown here.

arch/nios2/lib/memset.c+81−0

This diff is large: its 82 lines aren’t shown here.

arch/nios2/mm/Makefile+14−0

This diff is large: its 15 lines aren’t shown here.

arch/nios2/mm/cacheflush.c+271−0

This diff is large: its 272 lines aren’t shown here.

arch/nios2/mm/dma-mapping.c+186−0

This diff is large: its 187 lines aren’t shown here.

arch/nios2/mm/extable.c+25−0

This diff is large: its 26 lines aren’t shown here.

arch/nios2/mm/fault.c+251−0

This diff is large: its 252 lines aren’t shown here.

arch/nios2/mm/init.c+142−0

This diff is large: its 143 lines aren’t shown here.

arch/nios2/mm/ioremap.c+187−0

This diff is large: its 188 lines aren’t shown here.

arch/nios2/mm/mmu_context.c+116−0

This diff is large: its 117 lines aren’t shown here.

arch/nios2/mm/pgtable.c+74−0

This diff is large: its 75 lines aren’t shown here.

arch/nios2/mm/tlb.c+275−0

This diff is large: its 276 lines aren’t shown here.

arch/nios2/mm/uaccess.c+163−0

This diff is large: its 164 lines aren’t shown here.

arch/nios2/platform/Kconfig.platform+129−0

This diff is large: its 130 lines aren’t shown here.

arch/nios2/platform/Makefile+1−0

This diff is large: its 2 lines aren’t shown here.

arch/nios2/platform/platform.c+46−0

This diff is large: its 47 lines aren’t shown here.

arch/openrisc/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/openrisc/include/asm/Kbuild+1−1

This diff is large: its 14 lines aren’t shown here.

arch/openrisc/include/asm/irq.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/openrisc/include/asm/syscall.h+5−0

This diff is large: its 17 lines aren’t shown here.

arch/openrisc/include/uapi/asm/elf.h+1−2

This diff is large: its 11 lines aren’t shown here.

arch/openrisc/kernel/irq.c+0−12

This diff is large: its 19 lines aren’t shown here.

arch/openrisc/kernel/ptrace.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/parisc/hpux/fs.c+4−3

This diff is large: its 16 lines aren’t shown here.

arch/parisc/include/asm/Kbuild+1−1

This diff is large: its 11 lines aren’t shown here.

arch/parisc/include/asm/atomic.h+71−46

This diff is large: its 159 lines aren’t shown here.

arch/parisc/include/asm/io.h+8−4

This diff is large: its 19 lines aren’t shown here.

arch/parisc/include/asm/ldcw.h+10−3

This diff is large: its 22 lines aren’t shown here.

arch/parisc/include/asm/syscall.h+11−0

This diff is large: its 23 lines aren’t shown here.

arch/parisc/include/asm/uaccess.h+8−11

This diff is large: its 68 lines aren’t shown here.

arch/parisc/include/uapi/asm/bitsperlong.h+1−7

This diff is large: its 15 lines aren’t shown here.

arch/parisc/include/uapi/asm/ioctls.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/parisc/include/uapi/asm/msgbuf.h+5−3

This diff is large: its 28 lines aren’t shown here.

arch/parisc/include/uapi/asm/sembuf.h+4−2

This diff is large: its 23 lines aren’t shown here.

arch/parisc/include/uapi/asm/shmbuf.h+15−20

This diff is large: its 66 lines aren’t shown here.

arch/parisc/include/uapi/asm/signal.h+7−11

This diff is large: its 45 lines aren’t shown here.

arch/parisc/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/parisc/include/uapi/asm/unistd.h+2−1

This diff is large: its 11 lines aren’t shown here.

arch/parisc/kernel/ptrace.c+3−6

This diff is large: its 18 lines aren’t shown here.

arch/parisc/kernel/syscall_table.S+5−4

This diff is large: its 32 lines aren’t shown here.

arch/parisc/lib/fixup.S+2−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/Kconfig+15−2

This diff is large: its 66 lines aren’t shown here.

arch/powerpc/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/boot/Makefile+5−0

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/boot/dts/b4860emu.dts+2−2

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/boot/dts/b4qds.dtsi+23−0

This diff is large: its 30 lines aren’t shown here.

arch/powerpc/boot/dts/bsc9131rdb.dtsi+0−50

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4420si-post.dtsi+2−26

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/b4860si-post.dtsi+2−26

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p2041si-post.dtsi+2−46

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p3041si-post.dtsi+2−46

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p4080si-post.dtsi+2−46

This diff is large: its 63 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5020si-post.dtsi+2−46

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/p5040si-post.dtsi+2−46

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi+85−0

This diff is large: its 86 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/qoriq-clockgen2.dtsi+68−0

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t1040si-post.dtsi+2−28

This diff is large: its 38 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t2081si-post.dtsi+4−29

This diff is large: its 55 lines aren’t shown here.

arch/powerpc/boot/dts/fsl/t4240si-post.dtsi+4−29

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/boot/dts/p3041ds.dts+20−0

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/boot/dts/p5020ds.dts+20−0

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/boot/dts/p5040ds.dts+20−0

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/boot/dts/t1040rdb.dts+48−0

This diff is large: its 49 lines aren’t shown here.

arch/powerpc/boot/dts/t1042rdb.dts+48−0

This diff is large: its 49 lines aren’t shown here.

arch/powerpc/boot/dts/t1042rdb_pi.dts+57−0

This diff is large: its 58 lines aren’t shown here.

arch/powerpc/boot/dts/t104xrdb.dtsi+163−0

This diff is large: its 164 lines aren’t shown here.

arch/powerpc/boot/dts/t208xqds.dtsi+11−0

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/boot/dts/t4240emu.dts+2−2

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/boot/main.c+13−2

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/boot/ops.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/boot/serial.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/boot/simpleboot.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/configs/85xx/ge_imp3a_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/86xx/gef_ppc9a_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/86xx/gef_sbc310_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/86xx/gef_sbc610_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/86xx/sbc8641d_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/c2k_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/cell_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/celleb_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/corenet32_smp_defconfig+3−0

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/configs/corenet64_smp_defconfig+11−36

This diff is large: its 124 lines aren’t shown here.

arch/powerpc/configs/g5_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/maple_defconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/mpc85xx_defconfig+4−1

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/configs/mpc85xx_smp_defconfig+4−1

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/configs/mpc86xx_defconfig+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/configs/pasemi_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 16 lines aren’t shown here.

arch/powerpc/configs/ppc64e_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/ppc6xx_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/ps3_defconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/configs/pseries_defconfig+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/configs/pseries_le_defconfig+6−2

This diff is large: its 29 lines aren’t shown here.

arch/powerpc/crypto/sha1.c+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/include/asm/Kbuild+1−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/atomic.h+77−121

This diff is large: its 226 lines aren’t shown here.

arch/powerpc/include/asm/barrier.h+11−8

This diff is large: its 61 lines aren’t shown here.

arch/powerpc/include/asm/bitops.h+3−3

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/include/asm/bug.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/copro.h+29−0

This diff is large: its 30 lines aren’t shown here.

arch/powerpc/include/asm/cpuidle.h+20−0

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/include/asm/cputable.h+3−7

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/include/asm/cputime.h+5−3

This diff is large: its 23 lines aren’t shown here.

arch/powerpc/include/asm/dma-mapping.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/eeh.h+28−16

This diff is large: its 180 lines aren’t shown here.

arch/powerpc/include/asm/elf.h+1−2

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/include/asm/fadump.h+26−26

This diff is large: its 82 lines aren’t shown here.

arch/powerpc/include/asm/fsl_guts.h+4−1

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/asm/hardirq.h+6−1

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/include/asm/hugetlb.h+5−5

This diff is large: its 39 lines aren’t shown here.

arch/powerpc/include/asm/hydra.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/io.h+8−7

This diff is large: its 29 lines aren’t shown here.

arch/powerpc/include/asm/iommu.h+10−7

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/include/asm/irq.h+0−5

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/asm/kexec.h+10−1

This diff is large: its 30 lines aren’t shown here.

arch/powerpc/include/asm/kvm_asm.h+10−10

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/include/asm/kvm_book3s.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/kvm_book3s_64.h+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/include/asm/kvm_booke.h+4−3

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/include/asm/kvm_host.h+19−23

This diff is large: its 139 lines aren’t shown here.

arch/powerpc/include/asm/kvm_ppc.h+11−4

This diff is large: its 50 lines aren’t shown here.

arch/powerpc/include/asm/machdep.h+2−21

This diff is large: its 71 lines aren’t shown here.

arch/powerpc/include/asm/mmu-8xx.h+2−0

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/include/asm/mmu-hash64.h+23−7

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/include/asm/opal.h+103−106

This diff is large: its 306 lines aren’t shown here.

arch/powerpc/include/asm/paca.h+8−5

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/include/asm/page.h+3−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/include/asm/page_64.h+31−12

This diff is large: its 60 lines aren’t shown here.

arch/powerpc/include/asm/pci-bridge.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/perf_event.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/pgalloc.h+2−1

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/include/asm/pgtable-ppc32.h+22−4

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/include/asm/pgtable-ppc64-4k.h+16−2

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/include/asm/pgtable-ppc64-64k.h+3−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/pgtable-ppc64.h+42−17

This diff is large: its 118 lines aren’t shown here.

arch/powerpc/include/asm/pgtable.h+17−49

This diff is large: its 122 lines aren’t shown here.

arch/powerpc/include/asm/plpar_wrappers.h+6−6

This diff is large: its 48 lines aren’t shown here.

arch/powerpc/include/asm/pnv-pci.h+31−0

This diff is large: its 32 lines aren’t shown here.

arch/powerpc/include/asm/ppc-opcode.h+3−0

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/include/asm/processor.h+3−2

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/asm/prom.h+0−2

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/pte-8xx.h+5−2

This diff is large: its 25 lines aren’t shown here.

arch/powerpc/include/asm/pte-common.h+5−0

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/include/asm/reg.h+7−3

This diff is large: its 54 lines aren’t shown here.

arch/powerpc/include/asm/reg_booke.h+2−0

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/include/asm/rio.h+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/setup.h+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/include/asm/spu.h+2−3

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/include/asm/sstep.h+62−0

This diff is large: its 66 lines aren’t shown here.

arch/powerpc/include/asm/syscall.h+11−1

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/include/asm/systbl.h+2−0

This diff is large: its 6 lines aren’t shown here.

arch/powerpc/include/asm/thread_info.h+2−3

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/include/asm/tlb.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/include/asm/tlbflush.h+6−4

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/include/asm/tsi108.h+0−4

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/include/asm/uaccess.h+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/include/asm/udbg.h+0−1

This diff is large: its 8 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/vga.h+1−3

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/include/asm/word-at-a-time.h+98−14

This diff is large: its 147 lines aren’t shown here.

arch/powerpc/include/asm/xics.h+5−4

This diff is large: its 44 lines aren’t shown here.

arch/powerpc/include/uapi/asm/kvm.h+6−0

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/include/uapi/asm/socket.h+5−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/include/uapi/asm/unistd.h+2−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kernel/Makefile+3−0

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/kernel/align.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/asm-offsets.c+9−5

This diff is large: its 35 lines aren’t shown here.

arch/powerpc/kernel/cpu_setup_fsl_booke.S+11−1

This diff is large: its 48 lines aren’t shown here.

arch/powerpc/kernel/cputable.c+5−0

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/kernel/crash_dump.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/dbell.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/dma-iommu.c+4−4

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/kernel/dma-swiotlb.c+6−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/kernel/dma.c+51−4

This diff is large: its 100 lines aren’t shown here.

arch/powerpc/kernel/eeh.c+243−74

This diff is large: its 543 lines aren’t shown here.

arch/powerpc/kernel/eeh_driver.c+90−20

This diff is large: its 166 lines aren’t shown here.

arch/powerpc/kernel/eeh_pe.c+28−5

This diff is large: its 68 lines aren’t shown here.

arch/powerpc/kernel/eeh_sysfs.c+40−1

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/kernel/entry_32.S+9−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/kernel/entry_64.S+16−25

This diff is large: its 74 lines aren’t shown here.

arch/powerpc/kernel/exceptions-64e.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/kernel/exceptions-64s.S+40−34

This diff is large: its 148 lines aren’t shown here.

arch/powerpc/kernel/fadump.c+57−57

This diff is large: its 266 lines aren’t shown here.

arch/powerpc/kernel/ftrace.c+16−59

This diff is large: its 104 lines aren’t shown here.

arch/powerpc/kernel/head_8xx.S+171−195

This diff is large: its 640 lines aren’t shown here.

arch/powerpc/kernel/head_fsl_booke.S+17−9

This diff is large: its 82 lines aren’t shown here.

arch/powerpc/kernel/hw_breakpoint.c+4−4

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/kernel/ibmebus.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/idle_power7.S+311−47

This diff is large: its 454 lines aren’t shown here.

arch/powerpc/kernel/iommu.c+9−9

This diff is large: its 46 lines aren’t shown here.

arch/powerpc/kernel/irq.c+6−7

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/kernel/kgdb.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/kprobes.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/kernel/legacy_serial.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/machine_kexec_64.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/mce.c+12−12

This diff is large: its 71 lines aren’t shown here.

arch/powerpc/kernel/mce_power.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/kernel/misc.S+4−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kernel/module_32.c+14−17

This diff is large: its 101 lines aren’t shown here.

arch/powerpc/kernel/module_64.c+17−19

This diff is large: its 137 lines aren’t shown here.

arch/powerpc/kernel/msi.c+1−11

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/kernel/nvram_64.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/of_platform.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/kernel/pci-common.c+7−5

This diff is large: its 47 lines aren’t shown here.

arch/powerpc/kernel/pci_32.c+1−3

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/kernel/pci_64.c+0−11

This diff is large: its 22 lines aren’t shown here.

arch/powerpc/kernel/pci_of_scan.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/ppc_ksyms.c+15−179

This diff is large: its 225 lines aren’t shown here.

arch/powerpc/kernel/ppc_ksyms_32.c+61−0

This diff is large: its 62 lines aren’t shown here.

arch/powerpc/kernel/process.c+11−29

This diff is large: its 131 lines aren’t shown here.

arch/powerpc/kernel/prom.c+15−9

This diff is large: its 64 lines aren’t shown here.

arch/powerpc/kernel/prom_init_check.sh+6−16

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/kernel/ptrace.c+3−6

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/kernel/rtas-proc.c+9−11

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/kernel/rtas.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/kernel/rtas_pci.c+11−20

This diff is large: its 81 lines aren’t shown here.

arch/powerpc/kernel/rtasd.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/setup-common.c+7−6

This diff is large: its 48 lines aren’t shown here.

arch/powerpc/kernel/setup_32.c+3−10

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/kernel/setup_64.c+26−47

This diff is large: its 112 lines aren’t shown here.

arch/powerpc/kernel/smp.c+12−5

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/kernel/stacktrace.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kernel/suspend.c+1−3

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/kernel/sysfs.c+2−2

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/kernel/time.c+15−13

This diff is large: its 105 lines aren’t shown here.

arch/powerpc/kernel/traps.c+4−4

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/kernel/udbg_16550.c+5−1

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/kernel/vdso.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kernel/vdso32/getcpu.S+2−2

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/kvm/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kvm/book3s.c+49−121

This diff is large: its 293 lines aren’t shown here.

arch/powerpc/kvm/book3s.h+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/kvm/book3s_32_mmu.c+0−5

This diff is large: its 12 lines aren’t shown here.

arch/powerpc/kvm/book3s_64_mmu_hv.c+36−192

This diff is large: its 398 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv.c+185−300

This diff is large: its 788 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_builtin.c+41−104

This diff is large: its 201 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_interrupts.S+1−38

This diff is large: its 77 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_ras.c+1−4

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_rm_mmu.c+32−118

This diff is large: its 217 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_rm_xics.c+28−8

This diff is large: its 71 lines aren’t shown here.

arch/powerpc/kvm/book3s_hv_rmhandlers.S+46−260

This diff is large: its 607 lines aren’t shown here.

arch/powerpc/kvm/book3s_paired_singles.c+0−8

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/kvm/book3s_pr.c+5−6

This diff is large: its 32 lines aren’t shown here.

arch/powerpc/kvm/book3s_xics.c+23−7

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/kvm/book3s_xics.h+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/kvm/booke.c+214−73

This diff is large: its 517 lines aren’t shown here.

arch/powerpc/kvm/booke.h+6−34

This diff is large: its 57 lines aren’t shown here.

arch/powerpc/kvm/booke_emulate.c+163−0

This diff is large: its 226 lines aren’t shown here.

arch/powerpc/kvm/bookehv_interrupts.S+4−9

This diff is large: its 42 lines aren’t shown here.

arch/powerpc/kvm/e500.c+7−15

This diff is large: its 52 lines aren’t shown here.

arch/powerpc/kvm/e500.h+20−0

This diff is large: its 34 lines aren’t shown here.

arch/powerpc/kvm/e500_emulate.c+20−0

This diff is large: its 48 lines aren’t shown here.

arch/powerpc/kvm/e500_mmu_host.c+12−14

This diff is large: its 99 lines aren’t shown here.

arch/powerpc/kvm/e500mc.c+44−16

This diff is large: its 154 lines aren’t shown here.

arch/powerpc/kvm/emulate.c+16−1

This diff is large: its 31 lines aren’t shown here.

arch/powerpc/kvm/emulate_loadstore.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/kvm/powerpc.c+102−42

This diff is large: its 237 lines aren’t shown here.

arch/powerpc/kvm/trace_book3s.h+32−0

This diff is large: its 33 lines aren’t shown here.

arch/powerpc/kvm/trace_booke.h+45−2

This diff is large: its 61 lines aren’t shown here.

arch/powerpc/kvm/trace_hv.h+477−0

This diff is large: its 478 lines aren’t shown here.

arch/powerpc/kvm/trace_pr.h+1−24

This diff is large: its 38 lines aren’t shown here.

arch/powerpc/lib/Makefile+1−2

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/lib/alloc.c+1−3

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/lib/copyuser_power7.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/powerpc/lib/devres.c+0−43

This diff is large: its 44 lines aren’t shown here.

arch/powerpc/lib/feature-fixups.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/lib/memcpy_power7.S+1−1

This diff is large: its 6 lines aren’t shown here.

arch/powerpc/lib/ppc_ksyms.c+39−0

This diff is large: its 40 lines aren’t shown here.

arch/powerpc/lib/sstep.c+638−360

This diff is large: its 1336 lines aren’t shown here.

arch/powerpc/mm/Makefile+2−1

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/mm/copro_fault.c+148−0

This diff is large: its 149 lines aren’t shown here.

arch/powerpc/mm/fault.c+29−26

This diff is large: its 112 lines aren’t shown here.

arch/powerpc/mm/gup.c+0−235

This diff is large: its 236 lines aren’t shown here.

arch/powerpc/mm/hash_low_64.S+10−9

This diff is large: its 75 lines aren’t shown here.

arch/powerpc/mm/hash_native_64.c+32−15

This diff is large: its 109 lines aren’t shown here.

arch/powerpc/mm/hash_utils_64.c+180−90

This diff is large: its 451 lines aren’t shown here.

arch/powerpc/mm/hugepage-hash64.c+5−55

This diff is large: its 82 lines aren’t shown here.

arch/powerpc/mm/hugetlbpage-book3e.c+3−3

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/mm/hugetlbpage-hash64.c+3−3

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/mm/hugetlbpage.c+26−27

This diff is large: its 179 lines aren’t shown here.

arch/powerpc/mm/init_32.c+3−13

This diff is large: its 42 lines aren’t shown here.

arch/powerpc/mm/init_64.c+0−4

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/mm/mem.c+77−68

This diff is large: its 222 lines aren’t shown here.

arch/powerpc/mm/mmu_context_nohash.c+4−4

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/mm/mmu_decl.h+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/mm/numa.c+90−212

This diff is large: its 439 lines aren’t shown here.

arch/powerpc/mm/pgtable.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/mm/pgtable_32.c+2−3

This diff is large: its 23 lines aren’t shown here.

arch/powerpc/mm/pgtable_64.c+36−68

This diff is large: its 170 lines aren’t shown here.

arch/powerpc/mm/slb.c+0−3

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/mm/slice.c+7−8

This diff is large: its 49 lines aren’t shown here.

arch/powerpc/net/bpf_jit.h+7−0

This diff is large: its 21 lines aren’t shown here.

arch/powerpc/net/bpf_jit_comp.c+29−25

This diff is large: its 112 lines aren’t shown here.

arch/powerpc/oprofile/backtrace.c+5−2

This diff is large: its 35 lines aren’t shown here.

arch/powerpc/oprofile/cell/spu_task_sync.c+4−6

This diff is large: its 29 lines aren’t shown here.

arch/powerpc/perf/core-book3s.c+20−20

This diff is large: its 161 lines aren’t shown here.

arch/powerpc/perf/core-fsl-emb.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/perf/hv-24x7.c+48−111

This diff is large: its 243 lines aren’t shown here.

arch/powerpc/perf/hv-gpci.c+0−6

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/platforms/40x/ep405.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/40x/ppc40x_simple.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/40x/virtex.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/40x/walnut.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/Kconfig+3−4

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/44x/canyonlands.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/ebony.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/iss4xx.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/ppc44x_simple.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/ppc476.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/44x/sam440ep.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/virtex.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/44x/warp.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/512x/mpc512x_shared.c+5−6

This diff is large: its 36 lines aren’t shown here.

arch/powerpc/platforms/52xx/efika.c+2−1

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/platforms/52xx/lite5200.c+2−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/52xx/media5200.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_common.c+6−6

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_gpt.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/platforms/52xx/mpc52xx_pic.c+2−2

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/platforms/82xx/ep8248e.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/platforms/82xx/km82xx.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/82xx/mpc8272_ads.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/82xx/pq2fads.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c+7−6

This diff is large: its 42 lines aren’t shown here.

arch/powerpc/platforms/83xx/misc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/83xx/mpc834x_itx.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/83xx/suspend.c+2−3

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/platforms/85xx/Kconfig+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/85xx/common.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/85xx/corenet_generic.c+15−1

This diff is large: its 44 lines aren’t shown here.

arch/powerpc/platforms/85xx/ppa8548.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/85xx/qemu_e500.c+10−0

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/platforms/85xx/sgy_cts1000.c+4−5

This diff is large: its 44 lines aren’t shown here.

arch/powerpc/platforms/86xx/gef_ppc9a.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/86xx/gef_sbc310.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/86xx/gef_sbc610.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/86xx/mpc8610_hpcd.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/86xx/mpc86xx_hpcn.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/86xx/sbc8641d.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/8xx/Kconfig+0−4

This diff is large: its 15 lines aren’t shown here.

arch/powerpc/platforms/8xx/adder875.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/8xx/ep88xc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/8xx/mpc86xads_setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/8xx/mpc885ads_setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/8xx/tqm8xx_setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/Kconfig.cputype+11−1

This diff is large: its 28 lines aren’t shown here.

arch/powerpc/platforms/cell/Kconfig+1−0

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/cell/Makefile+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/cell/axon_msi.c+4−14

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/platforms/cell/beat_htab.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/cell/celleb_pci.c+4−4

This diff is large: its 32 lines aren’t shown here.

arch/powerpc/platforms/cell/celleb_scc_epci.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/cell/celleb_scc_pciex.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/cell/celleb_setup.c+3−3

This diff is large: its 41 lines aren’t shown here.

arch/powerpc/platforms/cell/interrupt.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/platforms/cell/iommu.c+5−4

This diff is large: its 23 lines aren’t shown here.

arch/powerpc/platforms/cell/qpace_setup.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/cell/setup.c+1−1

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/platforms/cell/spu_base.c+12−48

This diff is large: its 117 lines aren’t shown here.

arch/powerpc/platforms/cell/spu_fault.c+0−94

This diff is large: its 95 lines aren’t shown here.

arch/powerpc/platforms/cell/spufs/fault.c+3−3

This diff is large: its 22 lines aren’t shown here.

arch/powerpc/platforms/cell/spufs/inode.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/platforms/chrp/setup.c+3−2

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/gamecube.c+3−2

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/linkstation.c+4−2

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/mvme5100.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/storcenter.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/usbgecko_udbg.c+3−3

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/platforms/embedded6xx/wii.c+3−2

This diff is large: its 26 lines aren’t shown here.

arch/powerpc/platforms/maple/pci.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/maple/setup.c+2−2

This diff is large: its 25 lines aren’t shown here.

arch/powerpc/platforms/pasemi/gpio_mdio.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/platforms/pasemi/setup.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/powermac/nvram.c+1−5

This diff is large: its 13 lines aren’t shown here.

arch/powerpc/platforms/powermac/pci.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/powermac/setup.c+6−5

This diff is large: its 46 lines aren’t shown here.

arch/powerpc/platforms/powernv/eeh-ioda.c+207−33

This diff is large: its 372 lines aren’t shown here.

arch/powerpc/platforms/powernv/eeh-powernv.c+81−2

This diff is large: its 104 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-async.c+3−0

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-dump.c+13−5

This diff is large: its 53 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-elog.c+4−0

This diff is large: its 11 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-hmi.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-lpc.c+59−0

This diff is large: its 87 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-nvram.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-rtc.c+22−44

This diff is large: its 98 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-sensor.c+20−0

This diff is large: its 32 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-tracepoints.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal-wrappers.S+48−2

This diff is large: its 91 lines aren’t shown here.

arch/powerpc/platforms/powernv/opal.c+94−6

This diff is large: its 185 lines aren’t shown here.

arch/powerpc/platforms/powernv/pci-ioda.c+396−116

This diff is large: its 710 lines aren’t shown here.

arch/powerpc/platforms/powernv/pci-p5ioc2.c+20−24

This diff is large: its 69 lines aren’t shown here.

arch/powerpc/platforms/powernv/pci.c+17−17

This diff is large: its 83 lines aren’t shown here.

arch/powerpc/platforms/powernv/pci.h+5−1

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/platforms/powernv/powernv.h+8−0

This diff is large: its 24 lines aren’t shown here.

arch/powerpc/platforms/powernv/setup.c+178−5

This diff is large: its 232 lines aren’t shown here.

arch/powerpc/platforms/powernv/smp.c+45−7

This diff is large: its 94 lines aren’t shown here.

arch/powerpc/platforms/powernv/subcore.c+35−0

This diff is large: its 77 lines aren’t shown here.

arch/powerpc/platforms/powernv/subcore.h+8−1

This diff is large: its 14 lines aren’t shown here.

arch/powerpc/platforms/ps3/htab.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/ps3/interrupt.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/ps3/setup.c+2−7

This diff is large: its 30 lines aren’t shown here.

arch/powerpc/platforms/pseries/cmm.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/platforms/pseries/dlpar.c+30−25

This diff is large: its 187 lines aren’t shown here.

arch/powerpc/platforms/pseries/dtl.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/platforms/pseries/eeh_pseries.c+14−26

This diff is large: its 71 lines aren’t shown here.

arch/powerpc/platforms/pseries/hotplug-cpu.c+12−9

This diff is large: its 76 lines aren’t shown here.

arch/powerpc/platforms/pseries/hotplug-memory.c+10−31

This diff is large: its 106 lines aren’t shown here.

arch/powerpc/platforms/pseries/hvCall.S+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/pseries/hvCall_inst.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/platforms/pseries/iommu.c+41−37

This diff is large: its 238 lines aren’t shown here.

arch/powerpc/platforms/pseries/lpar.c+25−11

This diff is large: its 107 lines aren’t shown here.

arch/powerpc/platforms/pseries/msi.c+18−28

This diff is large: its 98 lines aren’t shown here.

arch/powerpc/platforms/pseries/nvram.c+9−5

This diff is large: its 35 lines aren’t shown here.

arch/powerpc/platforms/pseries/pci.c+2−1

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/platforms/pseries/pseries.h+2−1

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/platforms/pseries/ras.c+3−3

This diff is large: its 20 lines aren’t shown here.

arch/powerpc/platforms/pseries/setup.c+39−33

This diff is large: its 122 lines aren’t shown here.

arch/powerpc/sysdev/axonram.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/sysdev/dcr.c+1−0

This diff is large: its 7 lines aren’t shown here.

arch/powerpc/sysdev/fsl_85xx_l2ctlr.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/sysdev/fsl_msi.c+56−59

This diff is large: its 258 lines aren’t shown here.

arch/powerpc/sysdev/fsl_msi.h+3−1

This diff is large: its 18 lines aren’t shown here.

arch/powerpc/sysdev/fsl_pci.c+3−3

This diff is large: its 27 lines aren’t shown here.

arch/powerpc/sysdev/fsl_pmc.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/fsl_rio.c+104−1

This diff is large: its 147 lines aren’t shown here.

arch/powerpc/sysdev/fsl_rio.h+13−0

This diff is large: its 37 lines aren’t shown here.

arch/powerpc/sysdev/fsl_soc.c+2−3

This diff is large: its 19 lines aren’t shown here.

arch/powerpc/sysdev/ipic.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/mpc5xxx_clocks.c+1−2

This diff is large: its 10 lines aren’t shown here.

arch/powerpc/sysdev/mpic.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/sysdev/mpic_msgr.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/mpic_pasemi_msi.c+5−13

This diff is large: its 67 lines aren’t shown here.

arch/powerpc/sysdev/mpic_u3msi.c+14−21

This diff is large: its 83 lines aren’t shown here.

arch/powerpc/sysdev/msi_bitmap.c+56−38

This diff is large: its 178 lines aren’t shown here.

arch/powerpc/sysdev/mv64x60_dev.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/pmi.c+1−2

This diff is large: its 17 lines aren’t shown here.

arch/powerpc/sysdev/ppc4xx_cpm.c+4−4

This diff is large: its 30 lines aren’t shown here.

arch/powerpc/sysdev/ppc4xx_hsta_msi.c+7−14

This diff is large: its 56 lines aren’t shown here.

arch/powerpc/sysdev/ppc4xx_msi.c+7−16

This diff is large: its 65 lines aren’t shown here.

arch/powerpc/sysdev/ppc4xx_pci.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/qe_lib/qe.c+0−2

This diff is large: its 16 lines aren’t shown here.

arch/powerpc/sysdev/qe_lib/qe_ic.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/uic.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/powerpc/sysdev/xics/icp-native.c+25−0

This diff is large: its 32 lines aren’t shown here.

arch/powerpc/sysdev/xics/ics-opal.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/xics/ics-rtas.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/xics/xics-common.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/xilinx_intc.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/sysdev/xilinx_pci.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/powerpc/xmon/xmon.c+66−22

This diff is large: its 199 lines aren’t shown here.

arch/s390/Kconfig+10−7

This diff is large: its 58 lines aren’t shown here.

arch/s390/Makefile+10−7

This diff is large: its 24 lines aren’t shown here.

arch/s390/appldata/appldata_base.c+0−1

This diff is large: its 8 lines aren’t shown here.

arch/s390/configs/default_defconfig+14−22

This diff is large: its 134 lines aren’t shown here.

arch/s390/configs/gcov_defconfig+5−20

This diff is large: its 99 lines aren’t shown here.

arch/s390/configs/performance_defconfig+9−21

This diff is large: its 112 lines aren’t shown here.

arch/s390/configs/zfcpdump_defconfig+2−8

This diff is large: its 34 lines aren’t shown here.

arch/s390/crypto/aes_s390.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/crypto/des_s390.c+2−2

This diff is large: its 11 lines aren’t shown here.

arch/s390/crypto/ghash_s390.c+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/crypto/sha1_s390.c+1−1

This diff is large: its 8 lines aren’t shown here.

arch/s390/crypto/sha256_s390.c+2−2

This diff is large: its 10 lines aren’t shown here.

arch/s390/crypto/sha512_s390.c+2−2

This diff is large: its 18 lines aren’t shown here.

arch/s390/defconfig+2−3

This diff is large: its 28 lines aren’t shown here.

arch/s390/hypfs/hypfs_dbfs.c+1−2

This diff is large: its 12 lines aren’t shown here.

arch/s390/include/asm/Kbuild+1−1

This diff is large: its 9 lines aren’t shown here.

arch/s390/include/asm/barrier.h+9−4

This diff is large: its 28 lines aren’t shown here.

arch/s390/include/asm/cmpxchg.h+16−224

This diff is large: its 258 lines aren’t shown here.

arch/s390/include/asm/cputime.h+28−46

This diff is large: its 182 lines aren’t shown here.

arch/s390/include/asm/debug.h+27−2

This diff is large: its 47 lines aren’t shown here.

arch/s390/include/asm/dis.h+7−6

This diff is large: its 20 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