From 2c3c1048746a4622d8c89a29670120dc8fab93c4 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 20:49:45 +0200 Subject: Adding upstream version 6.1.76. Signed-off-by: Daniel Baumann --- Documentation/.gitignore | 3 + Documentation/ABI/README | 95 + Documentation/ABI/obsolete/o2cb | 11 + Documentation/ABI/obsolete/procfs-i8k | 10 + Documentation/ABI/obsolete/sysfs-bus-iio | 186 + Documentation/ABI/obsolete/sysfs-bus-usb | 31 + Documentation/ABI/obsolete/sysfs-class-typec | 48 + Documentation/ABI/obsolete/sysfs-cpuidle | 9 + .../ABI/obsolete/sysfs-driver-hid-roccat-arvo | 53 + .../ABI/obsolete/sysfs-driver-hid-roccat-isku | 153 + .../ABI/obsolete/sysfs-driver-hid-roccat-koneplus | 145 + .../ABI/obsolete/sysfs-driver-hid-roccat-konepure | 105 + .../ABI/obsolete/sysfs-driver-hid-roccat-kovaplus | 116 + .../ABI/obsolete/sysfs-driver-hid-roccat-lua | 7 + .../ABI/obsolete/sysfs-driver-hid-roccat-pyra | 126 + .../ABI/obsolete/sysfs-driver-hid-roccat-ryos | 178 + .../ABI/obsolete/sysfs-driver-hid-roccat-savu | 77 + .../ABI/obsolete/sysfs-driver-intel_pmc_bxt | 22 + Documentation/ABI/obsolete/sysfs-firmware-acpi | 8 + Documentation/ABI/obsolete/sysfs-gpio | 32 + .../ABI/obsolete/sysfs-kernel-fadump_enabled | 9 + .../ABI/obsolete/sysfs-kernel-fadump_registered | 10 + .../ABI/obsolete/sysfs-kernel-fadump_release_mem | 10 + .../ABI/obsolete/sysfs-selinux-checkreqprot | 23 + Documentation/ABI/obsolete/sysfs-selinux-disable | 26 + Documentation/ABI/removed/devfs | 13 + Documentation/ABI/removed/dv1394 | 14 + Documentation/ABI/removed/ip_queue | 9 + Documentation/ABI/removed/net_dma | 8 + Documentation/ABI/removed/o2cb | 10 + Documentation/ABI/removed/raw1394 | 16 + Documentation/ABI/removed/sysfs-bus-nfit | 17 + Documentation/ABI/removed/sysfs-class-rfkill | 13 + .../removed/sysfs-kernel-fadump_release_opalcore | 9 + Documentation/ABI/removed/sysfs-kernel-uids | 14 + Documentation/ABI/removed/sysfs-mce | 37 + Documentation/ABI/removed/video1394 | 17 + Documentation/ABI/stable/firewire-cdev | 111 + Documentation/ABI/stable/o2cb | 10 + Documentation/ABI/stable/procfs-audit_loginuid | 27 + Documentation/ABI/stable/syscalls | 10 + Documentation/ABI/stable/sysfs-acpi-pmprofile | 26 + Documentation/ABI/stable/sysfs-block | 734 ++ Documentation/ABI/stable/sysfs-bus-firewire | 136 + Documentation/ABI/stable/sysfs-bus-fsl-mc | 19 + Documentation/ABI/stable/sysfs-bus-mhi | 31 + Documentation/ABI/stable/sysfs-bus-nvmem | 22 + Documentation/ABI/stable/sysfs-bus-usb | 142 + Documentation/ABI/stable/sysfs-bus-vmbus | 187 + Documentation/ABI/stable/sysfs-bus-w1 | 12 + Documentation/ABI/stable/sysfs-bus-xen-backend | 84 + Documentation/ABI/stable/sysfs-class-backlight | 57 + Documentation/ABI/stable/sysfs-class-infiniband | 784 ++ Documentation/ABI/stable/sysfs-class-rfkill | 93 + Documentation/ABI/stable/sysfs-class-tpm | 210 + Documentation/ABI/stable/sysfs-class-ubi | 221 + Documentation/ABI/stable/sysfs-class-udc | 93 + Documentation/ABI/stable/sysfs-devices | 32 + Documentation/ABI/stable/sysfs-devices-node | 184 + Documentation/ABI/stable/sysfs-devices-system-cpu | 127 + .../ABI/stable/sysfs-devices-system-xen_memory | 86 + Documentation/ABI/stable/sysfs-driver-aspeed-vuart | 24 + Documentation/ABI/stable/sysfs-driver-dma-idxd | 304 + Documentation/ABI/stable/sysfs-driver-dma-ioatdma | 30 + .../ABI/stable/sysfs-driver-firmware-zynqmp | 256 + Documentation/ABI/stable/sysfs-driver-ib_srp | 192 + Documentation/ABI/stable/sysfs-driver-mlxreg-io | 544 ++ Documentation/ABI/stable/sysfs-driver-qla2xxx | 8 + Documentation/ABI/stable/sysfs-driver-speakup | 386 + Documentation/ABI/stable/sysfs-driver-usb-usbtmc | 27 + Documentation/ABI/stable/sysfs-driver-w1_ds2438 | 13 + Documentation/ABI/stable/sysfs-driver-w1_ds28e04 | 15 + Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 | 6 + Documentation/ABI/stable/sysfs-firmware-efi-vars | 79 + Documentation/ABI/stable/sysfs-firmware-opal-dump | 46 + Documentation/ABI/stable/sysfs-firmware-opal-elog | 62 + Documentation/ABI/stable/sysfs-fs-orangefs | 87 + Documentation/ABI/stable/sysfs-hypervisor-xen | 122 + Documentation/ABI/stable/sysfs-kernel-notes | 5 + Documentation/ABI/stable/sysfs-module | 47 + Documentation/ABI/stable/sysfs-transport-srp | 58 + Documentation/ABI/stable/thermal-notification | 4 + Documentation/ABI/stable/vdso | 35 + Documentation/ABI/testing/configfs-acpi | 52 + Documentation/ABI/testing/configfs-iio | 34 + Documentation/ABI/testing/configfs-most | 241 + Documentation/ABI/testing/configfs-rdma_cm | 30 + .../ABI/testing/configfs-spear-pcie-gadget | 33 + Documentation/ABI/testing/configfs-stp-policy | 48 + .../ABI/testing/configfs-stp-policy-p_sys-t | 41 + Documentation/ABI/testing/configfs-usb-gadget | 145 + Documentation/ABI/testing/configfs-usb-gadget-acm | 8 + Documentation/ABI/testing/configfs-usb-gadget-ecm | 20 + Documentation/ABI/testing/configfs-usb-gadget-eem | 16 + Documentation/ABI/testing/configfs-usb-gadget-ffs | 9 + Documentation/ABI/testing/configfs-usb-gadget-hid | 13 + .../ABI/testing/configfs-usb-gadget-loopback | 10 + .../ABI/testing/configfs-usb-gadget-mass-storage | 41 + Documentation/ABI/testing/configfs-usb-gadget-midi | 14 + Documentation/ABI/testing/configfs-usb-gadget-ncm | 15 + Documentation/ABI/testing/configfs-usb-gadget-obex | 9 + .../ABI/testing/configfs-usb-gadget-phonet | 8 + .../ABI/testing/configfs-usb-gadget-printer | 11 + .../ABI/testing/configfs-usb-gadget-rndis | 19 + .../ABI/testing/configfs-usb-gadget-serial | 9 + .../ABI/testing/configfs-usb-gadget-sourcesink | 16 + .../ABI/testing/configfs-usb-gadget-subset | 16 + Documentation/ABI/testing/configfs-usb-gadget-tcm | 6 + Documentation/ABI/testing/configfs-usb-gadget-uac1 | 33 + .../ABI/testing/configfs-usb-gadget-uac1_legacy | 12 + Documentation/ABI/testing/configfs-usb-gadget-uac2 | 38 + Documentation/ABI/testing/configfs-usb-gadget-uvc | 327 + Documentation/ABI/testing/debugfs-cec-error-inj | 40 + Documentation/ABI/testing/debugfs-cros-ec | 78 + Documentation/ABI/testing/debugfs-driver-genwqe | 91 + .../ABI/testing/debugfs-driver-habanalabs | 310 + Documentation/ABI/testing/debugfs-ec | 21 + Documentation/ABI/testing/debugfs-hisi-hpre | 164 + Documentation/ABI/testing/debugfs-hisi-sec | 137 + Documentation/ABI/testing/debugfs-hisi-zip | 138 + Documentation/ABI/testing/debugfs-hyperv | 23 + Documentation/ABI/testing/debugfs-ideapad | 19 + Documentation/ABI/testing/debugfs-moxtet | 35 + Documentation/ABI/testing/debugfs-olpc | 16 + Documentation/ABI/testing/debugfs-pfo-nx-crypto | 45 + Documentation/ABI/testing/debugfs-pktcdvd | 18 + Documentation/ABI/testing/debugfs-turris-mox-rwtm | 14 + Documentation/ABI/testing/debugfs-wilco-ec | 45 + Documentation/ABI/testing/dell-smbios-wmi | 41 + Documentation/ABI/testing/dev-kmsg | 127 + Documentation/ABI/testing/devlink-resource-mlxsw | 33 + Documentation/ABI/testing/evm | 108 + Documentation/ABI/testing/gpio-cdev | 27 + Documentation/ABI/testing/ima_policy | 190 + Documentation/ABI/testing/ppc-memtrace | 46 + Documentation/ABI/testing/procfs-attr-current | 20 + Documentation/ABI/testing/procfs-attr-exec | 20 + Documentation/ABI/testing/procfs-attr-prev | 19 + Documentation/ABI/testing/procfs-diskstats | 43 + Documentation/ABI/testing/procfs-smaps_rollup | 42 + Documentation/ABI/testing/pstore | 47 + Documentation/ABI/testing/rtc-cdev | 50 + Documentation/ABI/testing/securityfs-secrets-coco | 51 + Documentation/ABI/testing/sysfs-amd-pmc | 13 + Documentation/ABI/testing/sysfs-amd-pmf | 13 + Documentation/ABI/testing/sysfs-ata | 140 + Documentation/ABI/testing/sysfs-block-aoe | 45 + Documentation/ABI/testing/sysfs-block-bcache | 156 + Documentation/ABI/testing/sysfs-block-device | 97 + Documentation/ABI/testing/sysfs-block-dm | 47 + Documentation/ABI/testing/sysfs-block-loop | 50 + Documentation/ABI/testing/sysfs-block-rnbd | 64 + Documentation/ABI/testing/sysfs-block-rssd | 5 + Documentation/ABI/testing/sysfs-block-zram | 139 + Documentation/ABI/testing/sysfs-bus-acpi | 98 + Documentation/ABI/testing/sysfs-bus-amba | 20 + Documentation/ABI/testing/sysfs-bus-bcma | 31 + .../ABI/testing/sysfs-bus-coresight-devices-cti | 241 + .../ABI/testing/sysfs-bus-coresight-devices-etb10 | 82 + .../ABI/testing/sysfs-bus-coresight-devices-etm3x | 322 + .../ABI/testing/sysfs-bus-coresight-devices-etm4x | 526 ++ .../ABI/testing/sysfs-bus-coresight-devices-funnel | 12 + .../ABI/testing/sysfs-bus-coresight-devices-stm | 53 + .../ABI/testing/sysfs-bus-coresight-devices-tmc | 93 + .../ABI/testing/sysfs-bus-coresight-devices-trbe | 14 + Documentation/ABI/testing/sysfs-bus-counter | 382 + Documentation/ABI/testing/sysfs-bus-css | 61 + Documentation/ABI/testing/sysfs-bus-cxl | 390 + Documentation/ABI/testing/sysfs-bus-dfl | 17 + .../ABI/testing/sysfs-bus-dfl-devices-emif | 25 + .../ABI/testing/sysfs-bus-dfl-devices-n3000-nios | 47 + .../testing/sysfs-bus-event_source-devices-caps | 18 + .../testing/sysfs-bus-event_source-devices-dfl_fme | 104 + .../ABI/testing/sysfs-bus-event_source-devices-dsa | 30 + .../testing/sysfs-bus-event_source-devices-events | 94 + .../testing/sysfs-bus-event_source-devices-format | 21 + .../testing/sysfs-bus-event_source-devices-hv_24x7 | 98 + .../testing/sysfs-bus-event_source-devices-hv_gpci | 82 + .../testing/sysfs-bus-event_source-devices-uncore | 13 + Documentation/ABI/testing/sysfs-bus-fcoe | 138 + Documentation/ABI/testing/sysfs-bus-fsi | 46 + .../ABI/testing/sysfs-bus-fsi-devices-sbefifo | 10 + Documentation/ABI/testing/sysfs-bus-fsl-mc | 25 + Documentation/ABI/testing/sysfs-bus-hsi | 19 + .../ABI/testing/sysfs-bus-i2c-devices-bq32k | 7 + .../ABI/testing/sysfs-bus-i2c-devices-fsa9480 | 27 + .../ABI/testing/sysfs-bus-i2c-devices-hm6352 | 21 + .../ABI/testing/sysfs-bus-i2c-devices-lm3533 | 15 + .../ABI/testing/sysfs-bus-i2c-devices-pca954x | 23 + Documentation/ABI/testing/sysfs-bus-i3c | 148 + Documentation/ABI/testing/sysfs-bus-iio | 2164 +++++ .../ABI/testing/sysfs-bus-iio-accel-adxl372 | 7 + .../ABI/testing/sysfs-bus-iio-accel-bmc150 | 7 + Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192 | 51 + .../ABI/testing/sysfs-bus-iio-adc-ad7280a | 13 + .../testing/sysfs-bus-iio-adc-envelope-detector | 39 + Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 | 48 + .../ABI/testing/sysfs-bus-iio-adc-max9611 | 17 + Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 | 78 + Documentation/ABI/testing/sysfs-bus-iio-adc-stm32 | 21 + Documentation/ABI/testing/sysfs-bus-iio-bno055 | 81 + Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746 | 11 + .../ABI/testing/sysfs-bus-iio-chemical-sgp40 | 31 + .../ABI/testing/sysfs-bus-iio-chemical-sunrise-co2 | 38 + .../ABI/testing/sysfs-bus-iio-chemical-vz89x | 7 + Documentation/ABI/testing/sysfs-bus-iio-cros-ec | 28 + Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 | 31 + .../ABI/testing/sysfs-bus-iio-dac-dpot-dac | 8 + .../ABI/testing/sysfs-bus-iio-dac-ltc2688 | 86 + .../ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 | 22 + .../ABI/testing/sysfs-bus-iio-distance-srf08 | 17 + Documentation/ABI/testing/sysfs-bus-iio-dma-buffer | 19 + .../ABI/testing/sysfs-bus-iio-filter-admv8818 | 16 + .../ABI/testing/sysfs-bus-iio-frequency-ad9523 | 31 + .../ABI/testing/sysfs-bus-iio-frequency-adf4350 | 21 + .../ABI/testing/sysfs-bus-iio-frequency-adf4371 | 11 + .../ABI/testing/sysfs-bus-iio-frequency-admv1013 | 38 + .../ABI/testing/sysfs-bus-iio-frequency-admv1014 | 23 + .../ABI/testing/sysfs-bus-iio-gyro-bmg160 | 7 + .../ABI/testing/sysfs-bus-iio-health-afe440x | 39 + Documentation/ABI/testing/sysfs-bus-iio-humidity | 10 + .../sysfs-bus-iio-impedance-analyzer-ad5933 | 35 + Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc | 24 + Documentation/ABI/testing/sysfs-bus-iio-isl29501 | 47 + .../ABI/testing/sysfs-bus-iio-light-isl29018 | 21 + .../ABI/testing/sysfs-bus-iio-light-lm3533-als | 56 + .../ABI/testing/sysfs-bus-iio-light-si1133 | 22 + .../ABI/testing/sysfs-bus-iio-light-tsl2583 | 20 + .../ABI/testing/sysfs-bus-iio-light-tsl2772 | 13 + .../ABI/testing/sysfs-bus-iio-magnetometer-hmc5843 | 20 + Documentation/ABI/testing/sysfs-bus-iio-meas-spec | 7 + Documentation/ABI/testing/sysfs-bus-iio-mpu6050 | 13 + .../testing/sysfs-bus-iio-potentiometer-mcp4531 | 8 + Documentation/ABI/testing/sysfs-bus-iio-proximity | 24 + .../ABI/testing/sysfs-bus-iio-proximity-as3935 | 15 + Documentation/ABI/testing/sysfs-bus-iio-sps30 | 28 + Documentation/ABI/testing/sysfs-bus-iio-sx9310 | 10 + Documentation/ABI/testing/sysfs-bus-iio-sx9324 | 29 + .../ABI/testing/sysfs-bus-iio-thermocouple | 18 + .../ABI/testing/sysfs-bus-iio-timer-stm32 | 143 + .../ABI/testing/sysfs-bus-iio-trigger-sysfs | 42 + Documentation/ABI/testing/sysfs-bus-iio-vf610 | 16 + .../ABI/testing/sysfs-bus-intel_th-devices-gth | 52 + .../ABI/testing/sysfs-bus-intel_th-devices-msc | 54 + .../ABI/testing/sysfs-bus-intel_th-devices-pti | 24 + .../ABI/testing/sysfs-bus-intel_th-output-devices | 15 + Documentation/ABI/testing/sysfs-bus-mcb | 29 + Documentation/ABI/testing/sysfs-bus-mdio | 72 + Documentation/ABI/testing/sysfs-bus-media | 6 + Documentation/ABI/testing/sysfs-bus-mei | 56 + Documentation/ABI/testing/sysfs-bus-mmc | 4 + Documentation/ABI/testing/sysfs-bus-most | 299 + Documentation/ABI/testing/sysfs-bus-moxtet-devices | 17 + Documentation/ABI/testing/sysfs-bus-nfit | 233 + Documentation/ABI/testing/sysfs-bus-nvdimm | 43 + Documentation/ABI/testing/sysfs-bus-optee-devices | 17 + Documentation/ABI/testing/sysfs-bus-papr-pmem | 75 + Documentation/ABI/testing/sysfs-bus-pci | 492 ++ .../ABI/testing/sysfs-bus-pci-devices-aer_stats | 119 + .../ABI/testing/sysfs-bus-pci-devices-catpt | 17 + .../ABI/testing/sysfs-bus-pci-devices-cciss | 80 + .../ABI/testing/sysfs-bus-pci-devices-pvpanic | 26 + .../ABI/testing/sysfs-bus-pci-drivers-ehci_hcd | 46 + .../ABI/testing/sysfs-bus-pci-drivers-janz-cmodio | 8 + .../ABI/testing/sysfs-bus-pci-drivers-xhci_hcd | 25 + Documentation/ABI/testing/sysfs-bus-peci | 16 + Documentation/ABI/testing/sysfs-bus-platform | 56 + .../testing/sysfs-bus-platform-devices-occ-hwmon | 13 + .../ABI/testing/sysfs-bus-platform-onboard-usb-hub | 8 + Documentation/ABI/testing/sysfs-bus-rapidio | 201 + Documentation/ABI/testing/sysfs-bus-rbd | 173 + Documentation/ABI/testing/sysfs-bus-rpmsg | 95 + Documentation/ABI/testing/sysfs-bus-siox | 90 + .../ABI/testing/sysfs-bus-soundwire-master | 23 + .../ABI/testing/sysfs-bus-soundwire-slave | 109 + .../ABI/testing/sysfs-bus-spi-devices-spi-nor | 34 + .../testing/sysfs-bus-surface_aggregator-tabletsw | 57 + Documentation/ABI/testing/sysfs-bus-thunderbolt | 370 + Documentation/ABI/testing/sysfs-bus-typec | 51 + Documentation/ABI/testing/sysfs-bus-umc | 28 + Documentation/ABI/testing/sysfs-bus-usb | 584 ++ .../ABI/testing/sysfs-bus-usb-devices-usbsevseg | 46 + Documentation/ABI/testing/sysfs-bus-usb-lvstest | 60 + Documentation/ABI/testing/sysfs-bus-vdpa | 57 + Documentation/ABI/testing/sysfs-bus-vfio-mdev | 113 + Documentation/ABI/testing/sysfs-bus-vmbus | 21 + Documentation/ABI/testing/sysfs-c2port | 81 + Documentation/ABI/testing/sysfs-cfq-target-latency | 8 + Documentation/ABI/testing/sysfs-class | 16 + Documentation/ABI/testing/sysfs-class-backlight | 186 + .../testing/sysfs-class-backlight-driver-lm3533 | 54 + .../ABI/testing/sysfs-class-backlight-lm3639 | 11 + Documentation/ABI/testing/sysfs-class-bdi | 66 + Documentation/ABI/testing/sysfs-class-bsr | 25 + Documentation/ABI/testing/sysfs-class-chromeos | 33 + .../sysfs-class-chromeos-driver-cros-ec-lightbar | 74 + .../sysfs-class-chromeos-driver-cros-ec-vbc | 6 + Documentation/ABI/testing/sysfs-class-cxl | 270 + Documentation/ABI/testing/sysfs-class-devfreq | 134 + .../ABI/testing/sysfs-class-devfreq-event | 25 + Documentation/ABI/testing/sysfs-class-devlink | 130 + Documentation/ABI/testing/sysfs-class-extcon | 101 + Documentation/ABI/testing/sysfs-class-fc | 27 + Documentation/ABI/testing/sysfs-class-fc_host | 23 + .../ABI/testing/sysfs-class-fc_remote_ports | 23 + Documentation/ABI/testing/sysfs-class-firmware | 77 + .../ABI/testing/sysfs-class-firmware-attributes | 366 + Documentation/ABI/testing/sysfs-class-fpga-bridge | 11 + Documentation/ABI/testing/sysfs-class-fpga-manager | 60 + Documentation/ABI/testing/sysfs-class-fpga-region | 9 + Documentation/ABI/testing/sysfs-class-gnss | 17 + Documentation/ABI/testing/sysfs-class-hwmon | 949 +++ Documentation/ABI/testing/sysfs-class-intel_pmt | 119 + Documentation/ABI/testing/sysfs-class-iommu | 17 + .../ABI/testing/sysfs-class-iommu-amd-iommu | 14 + .../ABI/testing/sysfs-class-iommu-intel-iommu | 32 + Documentation/ABI/testing/sysfs-class-lcd | 23 + Documentation/ABI/testing/sysfs-class-led | 83 + .../ABI/testing/sysfs-class-led-driver-lm3533 | 73 + .../testing/sysfs-class-led-driver-turris-omnia | 14 + Documentation/ABI/testing/sysfs-class-led-flash | 89 + .../ABI/testing/sysfs-class-led-multicolor | 24 + .../ABI/testing/sysfs-class-led-trigger-netdev | 52 + .../ABI/testing/sysfs-class-led-trigger-oneshot | 36 + .../ABI/testing/sysfs-class-led-trigger-pattern | 40 + .../ABI/testing/sysfs-class-led-trigger-tty | 6 + .../ABI/testing/sysfs-class-led-trigger-usbport | 13 + Documentation/ABI/testing/sysfs-class-leds-gt683r | 18 + Documentation/ABI/testing/sysfs-class-mei | 105 + Documentation/ABI/testing/sysfs-class-mic | 178 + Documentation/ABI/testing/sysfs-class-mtd | 242 + Documentation/ABI/testing/sysfs-class-mux | 16 + Documentation/ABI/testing/sysfs-class-net | 354 + Documentation/ABI/testing/sysfs-class-net-cdc_ncm | 168 + Documentation/ABI/testing/sysfs-class-net-dsa | 14 + Documentation/ABI/testing/sysfs-class-net-grcan | 35 + .../ABI/testing/sysfs-class-net-janz-ican3 | 19 + Documentation/ABI/testing/sysfs-class-net-phydev | 65 + Documentation/ABI/testing/sysfs-class-net-qmi | 76 + Documentation/ABI/testing/sysfs-class-net-queues | 98 + .../ABI/testing/sysfs-class-net-statistics | 217 + Documentation/ABI/testing/sysfs-class-ocxl | 51 + Documentation/ABI/testing/sysfs-class-pktcdvd | 97 + Documentation/ABI/testing/sysfs-class-power | 773 ++ .../ABI/testing/sysfs-class-power-ltc4162l | 82 + Documentation/ABI/testing/sysfs-class-power-mp2629 | 9 + .../ABI/testing/sysfs-class-power-surface | 15 + .../ABI/testing/sysfs-class-power-twl4030 | 33 + Documentation/ABI/testing/sysfs-class-power-wilco | 40 + Documentation/ABI/testing/sysfs-class-powercap | 152 + Documentation/ABI/testing/sysfs-class-pwm | 88 + Documentation/ABI/testing/sysfs-class-rapidio | 59 + Documentation/ABI/testing/sysfs-class-rc | 137 + Documentation/ABI/testing/sysfs-class-rc-nuvoton | 15 + Documentation/ABI/testing/sysfs-class-regulator | 453 ++ Documentation/ABI/testing/sysfs-class-remoteproc | 104 + Documentation/ABI/testing/sysfs-class-rnbd-client | 133 + Documentation/ABI/testing/sysfs-class-rnbd-server | 58 + Documentation/ABI/testing/sysfs-class-rtc | 91 + .../sysfs-class-rtc-rtc0-device-rtc_calibration | 14 + Documentation/ABI/testing/sysfs-class-rtrs-client | 146 + Documentation/ABI/testing/sysfs-class-rtrs-server | 53 + Documentation/ABI/testing/sysfs-class-scsi_host | 119 + Documentation/ABI/testing/sysfs-class-scsi_tape | 109 + Documentation/ABI/testing/sysfs-class-spi-eeprom | 19 + Documentation/ABI/testing/sysfs-class-stm | 24 + Documentation/ABI/testing/sysfs-class-stm_source | 11 + Documentation/ABI/testing/sysfs-class-switchtec | 96 + Documentation/ABI/testing/sysfs-class-thermal | 259 + Documentation/ABI/testing/sysfs-class-typec | 348 + .../ABI/testing/sysfs-class-usb_power_delivery | 240 + Documentation/ABI/testing/sysfs-class-usb_role | 21 + Documentation/ABI/testing/sysfs-class-uwb_rc | 156 + .../ABI/testing/sysfs-class-uwb_rc-wusbhc | 57 + Documentation/ABI/testing/sysfs-class-vduse | 33 + Documentation/ABI/testing/sysfs-class-wakeup | 76 + Documentation/ABI/testing/sysfs-class-watchdog | 116 + Documentation/ABI/testing/sysfs-class-zram | 24 + Documentation/ABI/testing/sysfs-dev | 21 + Documentation/ABI/testing/sysfs-devices | 25 + Documentation/ABI/testing/sysfs-devices-consumer | 9 + Documentation/ABI/testing/sysfs-devices-coredump | 10 + Documentation/ABI/testing/sysfs-devices-edac | 157 + .../ABI/testing/sysfs-devices-firmware_node | 17 + Documentation/ABI/testing/sysfs-devices-hisi_ptt | 61 + Documentation/ABI/testing/sysfs-devices-lpss_ltr | 44 + Documentation/ABI/testing/sysfs-devices-mapping | 34 + Documentation/ABI/testing/sysfs-devices-memory | 112 + Documentation/ABI/testing/sysfs-devices-mmc | 21 + Documentation/ABI/testing/sysfs-devices-online | 20 + .../ABI/testing/sysfs-devices-physical_location | 42 + .../ABI/testing/sysfs-devices-platform-ACPI-TAD | 117 + .../testing/sysfs-devices-platform-_UDC_-gadget | 23 + .../ABI/testing/sysfs-devices-platform-docg3 | 40 + .../ABI/testing/sysfs-devices-platform-dock | 39 + .../ABI/testing/sysfs-devices-platform-ipmi | 242 + .../sysfs-devices-platform-sh_mobile_lcdc_fb | 44 + .../ABI/testing/sysfs-devices-platform-soc-ipa | 114 + .../testing/sysfs-devices-platform-stratix10-rsu | 174 + .../ABI/testing/sysfs-devices-platform-trackpoint | 115 + Documentation/ABI/testing/sysfs-devices-power | 307 + .../ABI/testing/sysfs-devices-power_resources_D0 | 13 + .../ABI/testing/sysfs-devices-power_resources_D1 | 14 + .../ABI/testing/sysfs-devices-power_resources_D2 | 14 + .../testing/sysfs-devices-power_resources_D3hot | 14 + .../testing/sysfs-devices-power_resources_wakeup | 13 + .../ABI/testing/sysfs-devices-power_state | 20 + .../ABI/testing/sysfs-devices-real_power_state | 23 + Documentation/ABI/testing/sysfs-devices-removable | 20 + .../ABI/testing/sysfs-devices-resource_in_use | 12 + Documentation/ABI/testing/sysfs-devices-soc | 95 + .../ABI/testing/sysfs-devices-software_node | 10 + .../ABI/testing/sysfs-devices-state_synced | 24 + Documentation/ABI/testing/sysfs-devices-sun | 14 + Documentation/ABI/testing/sysfs-devices-supplier | 9 + Documentation/ABI/testing/sysfs-devices-system-cpu | 689 ++ .../ABI/testing/sysfs-devices-system-ibm-rtl | 24 + .../ABI/testing/sysfs-devices-system-xen_cpu | 20 + Documentation/ABI/testing/sysfs-devices-vfio-dev | 8 + .../ABI/testing/sysfs-devices-waiting_for_supplier | 17 + Documentation/ABI/testing/sysfs-devices-xenbus | 41 + Documentation/ABI/testing/sysfs-driver-altera-cvp | 8 + .../ABI/testing/sysfs-driver-aspeed-uart-routing | 27 + .../ABI/testing/sysfs-driver-bd9571mwv-regulator | 31 + Documentation/ABI/testing/sysfs-driver-ccp | 87 + .../ABI/testing/sysfs-driver-chromeos-acpi | 137 + Documentation/ABI/testing/sysfs-driver-eud | 9 + .../ABI/testing/sysfs-driver-fsi-master-gpio | 10 + Documentation/ABI/testing/sysfs-driver-ge-achc | 15 + Documentation/ABI/testing/sysfs-driver-genwqe | 78 + Documentation/ABI/testing/sysfs-driver-habanalabs | 241 + Documentation/ABI/testing/sysfs-driver-hid | 20 + Documentation/ABI/testing/sysfs-driver-hid-corsair | 15 + Documentation/ABI/testing/sysfs-driver-hid-lenovo | 60 + .../ABI/testing/sysfs-driver-hid-logitech-hidpp | 19 + .../ABI/testing/sysfs-driver-hid-logitech-lg4ff | 75 + .../ABI/testing/sysfs-driver-hid-multitouch | 9 + Documentation/ABI/testing/sysfs-driver-hid-ntrig | 73 + Documentation/ABI/testing/sysfs-driver-hid-picolcd | 43 + .../ABI/testing/sysfs-driver-hid-prodikeys | 29 + .../ABI/testing/sysfs-driver-hid-roccat-kone | 125 + Documentation/ABI/testing/sysfs-driver-hid-srws1 | 21 + Documentation/ABI/testing/sysfs-driver-hid-wiimote | 85 + .../ABI/testing/sysfs-driver-input-axp-pek | 11 + .../ABI/testing/sysfs-driver-input-cros-ec-keyb | 6 + .../ABI/testing/sysfs-driver-input-exc3000 | 26 + Documentation/ABI/testing/sysfs-driver-intc_sar | 54 + .../ABI/testing/sysfs-driver-intel-m10-bmc | 36 + .../testing/sysfs-driver-intel-m10-bmc-sec-update | 61 + .../ABI/testing/sysfs-driver-intel-rapid-start | 21 + Documentation/ABI/testing/sysfs-driver-intel_sdsi | 79 + .../ABI/testing/sysfs-driver-jz4780-efuse | 20 + Documentation/ABI/testing/sysfs-driver-pciback | 28 + Documentation/ABI/testing/sysfs-driver-ppi | 75 + Documentation/ABI/testing/sysfs-driver-qat | 49 + .../ABI/testing/sysfs-driver-samsung-laptop | 48 + Documentation/ABI/testing/sysfs-driver-st | 12 + Documentation/ABI/testing/sysfs-driver-tegra-fuse | 11 + .../ABI/testing/sysfs-driver-toshiba_acpi | 223 + .../ABI/testing/sysfs-driver-toshiba_haps | 22 + .../ABI/testing/sysfs-driver-typec-displayport | 49 + Documentation/ABI/testing/sysfs-driver-uacce | 39 + Documentation/ABI/testing/sysfs-driver-ucsi-ccg | 6 + Documentation/ABI/testing/sysfs-driver-ufs | 1712 ++++ Documentation/ABI/testing/sysfs-driver-w1_ds28e17 | 24 + Documentation/ABI/testing/sysfs-driver-w1_therm | 190 + Documentation/ABI/testing/sysfs-driver-wacom | 105 + Documentation/ABI/testing/sysfs-driver-xdata | 49 + Documentation/ABI/testing/sysfs-driver-xen-blkback | 46 + .../ABI/testing/sysfs-driver-xen-blkfront | 19 + Documentation/ABI/testing/sysfs-firmware-acpi | 250 + .../ABI/testing/sysfs-firmware-dmi-entries | 114 + .../ABI/testing/sysfs-firmware-dmi-tables | 22 + Documentation/ABI/testing/sysfs-firmware-efi | 38 + Documentation/ABI/testing/sysfs-firmware-efi-esrt | 87 + .../ABI/testing/sysfs-firmware-efi-runtime-map | 36 + Documentation/ABI/testing/sysfs-firmware-gsmi | 58 + .../ABI/testing/sysfs-firmware-lefi-boardinfo | 35 + Documentation/ABI/testing/sysfs-firmware-log | 7 + Documentation/ABI/testing/sysfs-firmware-memmap | 75 + Documentation/ABI/testing/sysfs-firmware-ofw | 52 + .../ABI/testing/sysfs-firmware-opal-powercap | 31 + Documentation/ABI/testing/sysfs-firmware-opal-psr | 18 + .../ABI/testing/sysfs-firmware-opal-sensor-groups | 21 + .../testing/sysfs-firmware-papr-energy-scale-info | 29 + .../ABI/testing/sysfs-firmware-qemu_fw_cfg | 103 + Documentation/ABI/testing/sysfs-firmware-sgi_uv | 159 + .../ABI/testing/sysfs-firmware-turris-mox-rwtm | 37 + Documentation/ABI/testing/sysfs-fs-erofs | 17 + Documentation/ABI/testing/sysfs-fs-ext4 | 118 + Documentation/ABI/testing/sysfs-fs-f2fs | 636 ++ Documentation/ABI/testing/sysfs-fs-nilfs2 | 269 + Documentation/ABI/testing/sysfs-fs-ubifs | 35 + Documentation/ABI/testing/sysfs-fs-xfs | 39 + Documentation/ABI/testing/sysfs-hypervisor-xen | 46 + Documentation/ABI/testing/sysfs-ibft | 33 + Documentation/ABI/testing/sysfs-kernel-boot_params | 39 + Documentation/ABI/testing/sysfs-kernel-btf | 25 + .../ABI/testing/sysfs-kernel-dmabuf-buffers | 24 + Documentation/ABI/testing/sysfs-kernel-fadump | 40 + Documentation/ABI/testing/sysfs-kernel-fscaps | 8 + .../ABI/testing/sysfs-kernel-iommu_groups | 65 + Documentation/ABI/testing/sysfs-kernel-irq | 60 + Documentation/ABI/testing/sysfs-kernel-livepatch | 78 + Documentation/ABI/testing/sysfs-kernel-mm | 6 + Documentation/ABI/testing/sysfs-kernel-mm-cma | 25 + Documentation/ABI/testing/sysfs-kernel-mm-damon | 285 + .../ABI/testing/sysfs-kernel-mm-hugepages | 17 + Documentation/ABI/testing/sysfs-kernel-mm-ksm | 53 + .../ABI/testing/sysfs-kernel-mm-memory-tiers | 25 + Documentation/ABI/testing/sysfs-kernel-mm-numa | 24 + Documentation/ABI/testing/sysfs-kernel-mm-swap | 16 + Documentation/ABI/testing/sysfs-kernel-oops_count | 6 + Documentation/ABI/testing/sysfs-kernel-reboot | 32 + Documentation/ABI/testing/sysfs-kernel-slab | 519 ++ Documentation/ABI/testing/sysfs-kernel-vmcoreinfo | 14 + Documentation/ABI/testing/sysfs-kernel-warn_count | 6 + Documentation/ABI/testing/sysfs-mce | 97 + .../ABI/testing/sysfs-memory-page-offline | 44 + Documentation/ABI/testing/sysfs-module | 73 + Documentation/ABI/testing/sysfs-ocfs2 | 89 + .../ABI/testing/sysfs-platform-asus-laptop | 71 + Documentation/ABI/testing/sysfs-platform-asus-wmi | 100 + Documentation/ABI/testing/sysfs-platform-at91 | 27 + .../ABI/testing/sysfs-platform-brcmstb-gisb-arb | 8 + .../ABI/testing/sysfs-platform-brcmstb-memc | 15 + .../ABI/testing/sysfs-platform-chipidea-usb-otg | 56 + .../ABI/testing/sysfs-platform-chipidea-usb2 | 9 + .../ABI/testing/sysfs-platform-dell-laptop | 73 + .../ABI/testing/sysfs-platform-dell-privacy-wmi | 71 + .../ABI/testing/sysfs-platform-dell-smbios | 21 + Documentation/ABI/testing/sysfs-platform-dfl-fme | 246 + Documentation/ABI/testing/sysfs-platform-dfl-port | 101 + Documentation/ABI/testing/sysfs-platform-dptf | 157 + .../ABI/testing/sysfs-platform-eeepc-laptop | 56 + Documentation/ABI/testing/sysfs-platform-hidma | 9 + .../ABI/testing/sysfs-platform-hidma-mgmt | 97 + .../ABI/testing/sysfs-platform-i2c-demux-pinctrl | 18 + .../ABI/testing/sysfs-platform-ideapad-laptop | 61 + Documentation/ABI/testing/sysfs-platform-intel-ifs | 39 + Documentation/ABI/testing/sysfs-platform-intel-pmc | 22 + .../testing/sysfs-platform-intel-wmi-sbl-fw-update | 13 + .../testing/sysfs-platform-intel-wmi-thunderbolt | 12 + Documentation/ABI/testing/sysfs-platform-kim | 49 + Documentation/ABI/testing/sysfs-platform-lg-laptop | 36 + .../ABI/testing/sysfs-platform-mellanox-bootctl | 70 + .../ABI/testing/sysfs-platform-msi-laptop | 83 + .../ABI/testing/sysfs-platform-phy-rcar-gen3-usb2 | 17 + .../ABI/testing/sysfs-platform-renesas_usb3 | 17 + Documentation/ABI/testing/sysfs-platform-sst-atom | 26 + Documentation/ABI/testing/sysfs-platform-tahvo-usb | 16 + Documentation/ABI/testing/sysfs-platform-ts5500 | 54 + .../ABI/testing/sysfs-platform-twl4030-usb | 8 + .../ABI/testing/sysfs-platform-usbip-vudc | 38 + Documentation/ABI/testing/sysfs-platform-wilco-ec | 58 + Documentation/ABI/testing/sysfs-platform_profile | 35 + Documentation/ABI/testing/sysfs-power | 427 + Documentation/ABI/testing/sysfs-pps | 73 + Documentation/ABI/testing/sysfs-profiling | 13 + Documentation/ABI/testing/sysfs-ptp | 142 + Documentation/ABI/testing/sysfs-secvar | 46 + Documentation/ABI/testing/sysfs-timecard | 288 + Documentation/ABI/testing/sysfs-tty | 163 + Documentation/ABI/testing/sysfs-uevent | 51 + Documentation/ABI/testing/sysfs-wusb_cbaf | 101 + Documentation/ABI/testing/usb-charger-uevent | 54 + Documentation/ABI/testing/usb-uevent | 27 + Documentation/Changes | 1 + Documentation/CodingStyle | 1 + Documentation/Kconfig | 22 + Documentation/Makefile | 166 + Documentation/PCI/acpi-info.rst | 192 + Documentation/PCI/boot-interrupts.rst | 159 + .../PCI/endpoint/function/binding/pci-ntb.rst | 38 + .../PCI/endpoint/function/binding/pci-test.rst | 26 + Documentation/PCI/endpoint/index.rst | 20 + Documentation/PCI/endpoint/pci-endpoint-cfs.rst | 138 + Documentation/PCI/endpoint/pci-endpoint.rst | 231 + Documentation/PCI/endpoint/pci-ntb-function.rst | 348 + Documentation/PCI/endpoint/pci-ntb-howto.rst | 161 + Documentation/PCI/endpoint/pci-test-function.rst | 103 + Documentation/PCI/endpoint/pci-test-howto.rst | 235 + Documentation/PCI/endpoint/pci-vntb-function.rst | 129 + Documentation/PCI/endpoint/pci-vntb-howto.rst | 167 + Documentation/PCI/index.rst | 20 + Documentation/PCI/msi-howto.rst | 287 + Documentation/PCI/pci-error-recovery.rst | 426 + Documentation/PCI/pci-iov-howto.rst | 171 + Documentation/PCI/pci.rst | 578 ++ Documentation/PCI/pcieaer-howto.rst | 300 + Documentation/PCI/pciebus-howto.rst | 220 + Documentation/PCI/sysfs-pci.rst | 138 + .../Design/Data-Structures/BigTreeClassicRCU.svg | 474 ++ .../BigTreePreemptRCUBHdyntickCB.svg | 662 ++ .../RCU/Design/Data-Structures/Data-Structures.rst | 1163 +++ .../Design/Data-Structures/HugeTreeClassicRCU.svg | 939 +++ .../RCU/Design/Data-Structures/TreeLevel.svg | 828 ++ .../RCU/Design/Data-Structures/TreeMapping.svg | 305 + .../Design/Data-Structures/TreeMappingLevel.svg | 380 + .../RCU/Design/Data-Structures/blkd_task.svg | 631 ++ .../RCU/Design/Data-Structures/nxtlist.svg | 386 + .../Design/Expedited-Grace-Periods/ExpRCUFlow.svg | 830 ++ .../Expedited-Grace-Periods/ExpSchedFlow.svg | 830 ++ .../Expedited-Grace-Periods.rst | 521 ++ .../RCU/Design/Expedited-Grace-Periods/Funnel0.svg | 275 + .../RCU/Design/Expedited-Grace-Periods/Funnel1.svg | 275 + .../RCU/Design/Expedited-Grace-Periods/Funnel2.svg | 287 + .../RCU/Design/Expedited-Grace-Periods/Funnel3.svg | 323 + .../RCU/Design/Expedited-Grace-Periods/Funnel4.svg | 323 + .../RCU/Design/Expedited-Grace-Periods/Funnel5.svg | 335 + .../RCU/Design/Expedited-Grace-Periods/Funnel6.svg | 335 + .../RCU/Design/Expedited-Grace-Periods/Funnel7.svg | 347 + .../RCU/Design/Expedited-Grace-Periods/Funnel8.svg | 311 + .../Memory-Ordering/Tree-RCU-Memory-Ordering.rst | 648 ++ .../TreeRCU-callback-invocation.svg | 486 ++ .../Memory-Ordering/TreeRCU-callback-registry.svg | 655 ++ .../RCU/Design/Memory-Ordering/TreeRCU-dyntick.svg | 700 ++ .../Design/Memory-Ordering/TreeRCU-gp-cleanup.svg | 1133 +++ .../RCU/Design/Memory-Ordering/TreeRCU-gp-fqs.svg | 1309 ++++ .../Design/Memory-Ordering/TreeRCU-gp-init-1.svg | 658 ++ .../Design/Memory-Ordering/TreeRCU-gp-init-2.svg | 656 ++ .../Design/Memory-Ordering/TreeRCU-gp-init-3.svg | 636 ++ .../RCU/Design/Memory-Ordering/TreeRCU-gp.svg | 5144 ++++++++++++ .../RCU/Design/Memory-Ordering/TreeRCU-hotplug.svg | 775 ++ .../RCU/Design/Memory-Ordering/TreeRCU-qs.svg | 1095 +++ .../RCU/Design/Memory-Ordering/rcu_node-lock.svg | 229 + .../Design/Requirements/GPpartitionReaders1.svg | 374 + .../Design/Requirements/ReadersPartitionGP1.svg | 639 ++ .../RCU/Design/Requirements/Requirements.rst | 2760 +++++++ Documentation/RCU/NMI-RCU.rst | 123 + Documentation/RCU/RTFP.txt | 2812 +++++++ Documentation/RCU/UP.rst | 143 + Documentation/RCU/arrayRCU.rst | 165 + Documentation/RCU/checklist.rst | 491 ++ Documentation/RCU/index.rst | 38 + Documentation/RCU/listRCU.rst | 468 ++ Documentation/RCU/lockdep-splat.rst | 115 + Documentation/RCU/lockdep.rst | 116 + Documentation/RCU/rcu.rst | 91 + Documentation/RCU/rcu_dereference.rst | 475 ++ Documentation/RCU/rcubarrier.rst | 353 + Documentation/RCU/rculist_nulls.rst | 200 + Documentation/RCU/rcuref.rst | 158 + Documentation/RCU/stallwarn.rst | 385 + Documentation/RCU/torture.rst | 293 + Documentation/RCU/whatisRCU.rst | 1238 +++ Documentation/SubmittingPatches | 1 + Documentation/accounting/cgroupstats.rst | 31 + Documentation/accounting/delay-accounting.rst | 130 + Documentation/accounting/index.rst | 14 + Documentation/accounting/psi.rst | 188 + Documentation/accounting/taskstats-struct.rst | 199 + Documentation/accounting/taskstats.rst | 180 + Documentation/admin-guide/LSM/LoadPin.rst | 31 + Documentation/admin-guide/LSM/SELinux.rst | 33 + Documentation/admin-guide/LSM/SafeSetID.rst | 118 + Documentation/admin-guide/LSM/Smack.rst | 861 ++ Documentation/admin-guide/LSM/Yama.rst | 75 + Documentation/admin-guide/LSM/apparmor.rst | 51 + Documentation/admin-guide/LSM/index.rst | 49 + Documentation/admin-guide/LSM/tomoyo.rst | 65 + Documentation/admin-guide/README.rst | 339 + Documentation/admin-guide/abi-obsolete.rst | 11 + Documentation/admin-guide/abi-removed.rst | 5 + Documentation/admin-guide/abi-stable.rst | 14 + Documentation/admin-guide/abi-testing.rst | 20 + Documentation/admin-guide/abi.rst | 11 + Documentation/admin-guide/acpi/cppc_sysfs.rst | 78 + .../admin-guide/acpi/fan_performance_states.rst | 90 + Documentation/admin-guide/acpi/index.rst | 14 + .../admin-guide/acpi/initrd_table_override.rst | 115 + Documentation/admin-guide/acpi/ssdt-overlays.rst | 181 + Documentation/admin-guide/aoe/aoe.rst | 150 + Documentation/admin-guide/aoe/autoload.sh | 17 + Documentation/admin-guide/aoe/examples.rst | 23 + Documentation/admin-guide/aoe/index.rst | 17 + Documentation/admin-guide/aoe/status.sh | 30 + Documentation/admin-guide/aoe/todo.rst | 17 + Documentation/admin-guide/aoe/udev-install.sh | 33 + Documentation/admin-guide/aoe/udev.txt | 26 + .../admin-guide/auxdisplay/cfag12864b.rst | 98 + Documentation/admin-guide/auxdisplay/index.rst | 16 + Documentation/admin-guide/auxdisplay/ks0108.rst | 50 + Documentation/admin-guide/bcache.rst | 656 ++ Documentation/admin-guide/binderfs.rst | 87 + Documentation/admin-guide/binfmt-misc.rst | 151 + .../blockdev/drbd/DRBD-8.3-data-packets.svg | 588 ++ .../blockdev/drbd/DRBD-data-packets.svg | 459 ++ .../admin-guide/blockdev/drbd/conn-states-8.dot | 18 + .../blockdev/drbd/data-structure-v9.rst | 42 + .../admin-guide/blockdev/drbd/disk-states-8.dot | 16 + .../drbd/drbd-connection-state-overview.dot | 85 + .../admin-guide/blockdev/drbd/figures.rst | 30 + Documentation/admin-guide/blockdev/drbd/index.rst | 19 + .../admin-guide/blockdev/drbd/peer-states-8.dot | 8 + Documentation/admin-guide/blockdev/floppy.rst | 255 + Documentation/admin-guide/blockdev/index.rst | 16 + Documentation/admin-guide/blockdev/nbd.rst | 31 + Documentation/admin-guide/blockdev/paride.rst | 439 ++ Documentation/admin-guide/blockdev/ramdisk.rst | 153 + Documentation/admin-guide/blockdev/zram.rst | 440 ++ Documentation/admin-guide/bootconfig.rst | 323 + Documentation/admin-guide/braille-console.rst | 38 + Documentation/admin-guide/btmrvl.rst | 124 + Documentation/admin-guide/bug-bisect.rst | 76 + Documentation/admin-guide/bug-hunting.rst | 378 + .../admin-guide/cgroup-v1/blkio-controller.rst | 301 + Documentation/admin-guide/cgroup-v1/cgroups.rst | 695 ++ Documentation/admin-guide/cgroup-v1/cpuacct.rst | 50 + Documentation/admin-guide/cgroup-v1/cpusets.rst | 879 +++ Documentation/admin-guide/cgroup-v1/devices.rst | 132 + .../admin-guide/cgroup-v1/freezer-subsystem.rst | 127 + Documentation/admin-guide/cgroup-v1/hugetlb.rst | 135 + Documentation/admin-guide/cgroup-v1/index.rst | 31 + Documentation/admin-guide/cgroup-v1/memcg_test.rst | 344 + Documentation/admin-guide/cgroup-v1/memory.rst | 993 +++ Documentation/admin-guide/cgroup-v1/misc.rst | 4 + Documentation/admin-guide/cgroup-v1/net_cls.rst | 44 + Documentation/admin-guide/cgroup-v1/net_prio.rst | 57 + Documentation/admin-guide/cgroup-v1/pids.rst | 92 + Documentation/admin-guide/cgroup-v1/rdma.rst | 117 + Documentation/admin-guide/cgroup-v2.rst | 2968 +++++++ Documentation/admin-guide/cifs/authors.rst | 69 + Documentation/admin-guide/cifs/changes.rst | 9 + Documentation/admin-guide/cifs/index.rst | 21 + Documentation/admin-guide/cifs/introduction.rst | 53 + Documentation/admin-guide/cifs/todo.rst | 135 + Documentation/admin-guide/cifs/usage.rst | 870 ++ Documentation/admin-guide/cifs/winucase_convert.pl | 62 + Documentation/admin-guide/clearing-warn-once.rst | 9 + Documentation/admin-guide/cpu-load.rst | 117 + Documentation/admin-guide/cputopology.rst | 101 + Documentation/admin-guide/dell_rbu.rst | 128 + .../admin-guide/device-mapper/cache-policies.rst | 131 + Documentation/admin-guide/device-mapper/cache.rst | 337 + Documentation/admin-guide/device-mapper/delay.rst | 31 + .../admin-guide/device-mapper/dm-clone.rst | 333 + .../admin-guide/device-mapper/dm-crypt.rst | 181 + .../admin-guide/device-mapper/dm-dust.rst | 305 + Documentation/admin-guide/device-mapper/dm-ebs.rst | 51 + .../admin-guide/device-mapper/dm-flakey.rst | 74 + Documentation/admin-guide/device-mapper/dm-ima.rst | 715 ++ .../admin-guide/device-mapper/dm-init.rst | 133 + .../admin-guide/device-mapper/dm-integrity.rst | 292 + Documentation/admin-guide/device-mapper/dm-io.rst | 75 + Documentation/admin-guide/device-mapper/dm-log.rst | 57 + .../admin-guide/device-mapper/dm-queue-length.rst | 48 + .../admin-guide/device-mapper/dm-raid.rst | 423 + .../admin-guide/device-mapper/dm-service-time.rst | 101 + .../admin-guide/device-mapper/dm-uevent.rst | 110 + .../admin-guide/device-mapper/dm-zoned.rst | 194 + Documentation/admin-guide/device-mapper/era.rst | 116 + Documentation/admin-guide/device-mapper/index.rst | 46 + Documentation/admin-guide/device-mapper/kcopyd.rst | 47 + Documentation/admin-guide/device-mapper/linear.rst | 63 + .../admin-guide/device-mapper/log-writes.rst | 145 + .../admin-guide/device-mapper/persistent-data.rst | 88 + .../admin-guide/device-mapper/snapshot.rst | 196 + .../admin-guide/device-mapper/statistics.rst | 225 + .../admin-guide/device-mapper/striped.rst | 61 + Documentation/admin-guide/device-mapper/switch.rst | 141 + .../device-mapper/thin-provisioning.rst | 427 + .../admin-guide/device-mapper/unstriped.rst | 135 + Documentation/admin-guide/device-mapper/verity.rst | 249 + .../admin-guide/device-mapper/writecache.rst | 114 + Documentation/admin-guide/device-mapper/zero.rst | 37 + Documentation/admin-guide/devices.rst | 268 + Documentation/admin-guide/devices.txt | 3086 ++++++++ Documentation/admin-guide/dynamic-debug-howto.rst | 376 + Documentation/admin-guide/edid.rst | 60 + Documentation/admin-guide/efi-stub.rst | 100 + Documentation/admin-guide/ext4.rst | 627 ++ Documentation/admin-guide/features.rst | 3 + .../admin-guide/filesystem-monitoring.rst | 78 + Documentation/admin-guide/gpio/gpio-aggregator.rst | 111 + Documentation/admin-guide/gpio/gpio-mockup.rst | 51 + Documentation/admin-guide/gpio/gpio-sim.rst | 134 + Documentation/admin-guide/gpio/index.rst | 20 + Documentation/admin-guide/gpio/sysfs.rst | 167 + Documentation/admin-guide/highuid.rst | 80 + .../admin-guide/hw-vuln/core-scheduling.rst | 226 + .../admin-guide/hw-vuln/cross-thread-rsb.rst | 92 + .../admin-guide/hw-vuln/gather_data_sampling.rst | 109 + Documentation/admin-guide/hw-vuln/index.rst | 23 + Documentation/admin-guide/hw-vuln/l1d_flush.rst | 69 + Documentation/admin-guide/hw-vuln/l1tf.rst | 615 ++ Documentation/admin-guide/hw-vuln/mds.rst | 311 + Documentation/admin-guide/hw-vuln/multihit.rst | 167 + .../hw-vuln/processor_mmio_stale_data.rst | 260 + .../special-register-buffer-data-sampling.rst | 150 + Documentation/admin-guide/hw-vuln/spectre.rst | 756 ++ Documentation/admin-guide/hw-vuln/srso.rst | 133 + .../admin-guide/hw-vuln/tsx_async_abort.rst | 277 + Documentation/admin-guide/hw_random.rst | 105 + Documentation/admin-guide/index.rst | 131 + Documentation/admin-guide/init.rst | 48 + Documentation/admin-guide/initrd.rst | 383 + Documentation/admin-guide/iostats.rst | 210 + Documentation/admin-guide/java.rst | 423 + Documentation/admin-guide/jfs.rst | 66 + Documentation/admin-guide/kdump/gdbmacros.txt | 323 + Documentation/admin-guide/kdump/index.rst | 20 + Documentation/admin-guide/kdump/kdump.rst | 597 ++ Documentation/admin-guide/kdump/vmcoreinfo.rst | 597 ++ Documentation/admin-guide/kernel-parameters.rst | 224 + Documentation/admin-guide/kernel-parameters.txt | 7025 +++++++++++++++++ .../admin-guide/kernel-per-CPU-kthreads.rst | 334 + Documentation/admin-guide/laptops/asus-laptop.rst | 271 + .../admin-guide/laptops/disk-shock-protection.rst | 151 + Documentation/admin-guide/laptops/index.rst | 17 + Documentation/admin-guide/laptops/laptop-mode.rst | 770 ++ Documentation/admin-guide/laptops/lg-laptop.rst | 82 + Documentation/admin-guide/laptops/sony-laptop.rst | 174 + Documentation/admin-guide/laptops/sonypi.rst | 158 + .../admin-guide/laptops/thinkpad-acpi.rst | 1662 ++++ Documentation/admin-guide/laptops/toshiba_haps.rst | 87 + Documentation/admin-guide/lcd-panel-cgram.rst | 27 + Documentation/admin-guide/ldm.rst | 121 + Documentation/admin-guide/lockup-watchdogs.rst | 83 + Documentation/admin-guide/md.rst | 765 ++ .../admin-guide/media/au0828-cardlist.rst | 39 + Documentation/admin-guide/media/avermedia.rst | 94 + Documentation/admin-guide/media/bt8xx.rst | 157 + Documentation/admin-guide/media/bttv-cardlist.rst | 683 ++ Documentation/admin-guide/media/bttv.rst | 1762 +++++ Documentation/admin-guide/media/building.rst | 357 + Documentation/admin-guide/media/cafe_ccic.rst | 62 + Documentation/admin-guide/media/cardlist.rst | 29 + Documentation/admin-guide/media/cec-drivers.rst | 10 + Documentation/admin-guide/media/ci.rst | 77 + Documentation/admin-guide/media/cpia2.rst | 145 + Documentation/admin-guide/media/cx18-cardlist.rst | 17 + .../admin-guide/media/cx231xx-cardlist.rst | 99 + .../admin-guide/media/cx23885-cardlist.rst | 267 + Documentation/admin-guide/media/cx88-cardlist.rst | 383 + Documentation/admin-guide/media/cx88.rst | 58 + Documentation/admin-guide/media/davinci-vpbe.rst | 65 + Documentation/admin-guide/media/dvb-drivers.rst | 16 + .../admin-guide/media/dvb-usb-a800-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-af9005-cardlist.rst | 20 + .../admin-guide/media/dvb-usb-af9015-cardlist.rst | 80 + .../admin-guide/media/dvb-usb-af9035-cardlist.rst | 74 + .../admin-guide/media/dvb-usb-anysee-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-au6610-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-az6007-cardlist.rst | 20 + .../admin-guide/media/dvb-usb-az6027-cardlist.rst | 24 + .../admin-guide/media/dvb-usb-ce6230-cardlist.rst | 18 + .../media/dvb-usb-cinergyT2-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-cxusb-cardlist.rst | 40 + .../admin-guide/media/dvb-usb-dib0700-cardlist.rst | 162 + .../media/dvb-usb-dibusb-mb-cardlist.rst | 42 + .../media/dvb-usb-dibusb-mc-cardlist.rst | 30 + .../admin-guide/media/dvb-usb-digitv-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-dtt200u-cardlist.rst | 22 + .../admin-guide/media/dvb-usb-dtv5100-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-dvbsky-cardlist.rst | 42 + .../admin-guide/media/dvb-usb-dw2102-cardlist.rst | 56 + .../admin-guide/media/dvb-usb-ec168-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-gl861-cardlist.rst | 20 + .../admin-guide/media/dvb-usb-gp8psk-cardlist.rst | 22 + .../admin-guide/media/dvb-usb-lmedm04-cardlist.rst | 20 + .../admin-guide/media/dvb-usb-m920x-cardlist.rst | 26 + .../media/dvb-usb-mxl111sf-cardlist.rst | 36 + .../media/dvb-usb-nova-t-usb2-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-opera1-cardlist.rst | 16 + .../media/dvb-usb-pctv452e-cardlist.rst | 20 + .../media/dvb-usb-rtl28xxu-cardlist.rst | 80 + .../media/dvb-usb-technisat-usb2-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-ttusb2-cardlist.rst | 24 + .../admin-guide/media/dvb-usb-umt-010-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-vp702x-cardlist.rst | 16 + .../admin-guide/media/dvb-usb-vp7045-cardlist.rst | 18 + .../admin-guide/media/dvb-usb-zd1301-cardlist.rst | 16 + Documentation/admin-guide/media/dvb.rst | 12 + Documentation/admin-guide/media/dvb_intro.rst | 616 ++ Documentation/admin-guide/media/dvb_references.rst | 29 + .../admin-guide/media/em28xx-cardlist.rst | 440 ++ Documentation/admin-guide/media/faq.rst | 216 + Documentation/admin-guide/media/fimc.rst | 153 + .../admin-guide/media/frontend-cardlist.rst | 226 + Documentation/admin-guide/media/gspca-cardlist.rst | 451 ++ Documentation/admin-guide/media/i2c-cardlist.rst | 296 + Documentation/admin-guide/media/imx.rst | 714 ++ .../admin-guide/media/imx6q-sabreauto.dot | 51 + Documentation/admin-guide/media/imx6q-sabresd.dot | 56 + Documentation/admin-guide/media/imx7.rst | 221 + Documentation/admin-guide/media/index.rst | 63 + Documentation/admin-guide/media/intro.rst | 27 + Documentation/admin-guide/media/ipu3.rst | 600 ++ Documentation/admin-guide/media/ipu3_rcb.svg | 331 + Documentation/admin-guide/media/ivtv-cardlist.rst | 139 + Documentation/admin-guide/media/ivtv.rst | 218 + Documentation/admin-guide/media/lmedm04.rst | 107 + Documentation/admin-guide/media/meye.rst | 93 + Documentation/admin-guide/media/misc-cardlist.rst | 28 + Documentation/admin-guide/media/omap3isp.rst | 92 + Documentation/admin-guide/media/omap4_camera.rst | 62 + Documentation/admin-guide/media/opera-firmware.rst | 33 + .../admin-guide/media/other-usb-cardlist.rst | 92 + Documentation/admin-guide/media/pci-cardlist.rst | 109 + Documentation/admin-guide/media/philips.rst | 247 + .../admin-guide/media/platform-cardlist.rst | 91 + Documentation/admin-guide/media/pulse8-cec.rst | 13 + Documentation/admin-guide/media/qcom_camss.rst | 185 + .../admin-guide/media/qcom_camss_8x96_graph.dot | 106 + .../admin-guide/media/qcom_camss_graph.dot | 43 + Documentation/admin-guide/media/radio-cardlist.rst | 44 + Documentation/admin-guide/media/rcar-fdp1.rst | 39 + .../admin-guide/media/remote-controller.rst | 76 + Documentation/admin-guide/media/rkisp1.dot | 18 + Documentation/admin-guide/media/rkisp1.rst | 197 + .../admin-guide/media/saa7134-cardlist.rst | 803 ++ Documentation/admin-guide/media/saa7134.rst | 89 + .../admin-guide/media/saa7164-cardlist.rst | 71 + Documentation/admin-guide/media/si470x.rst | 167 + Documentation/admin-guide/media/si4713.rst | 192 + Documentation/admin-guide/media/si476x.rst | 160 + Documentation/admin-guide/media/siano-cardlist.rst | 56 + Documentation/admin-guide/media/technisat.rst | 100 + .../admin-guide/media/tm6000-cardlist.rst | 83 + Documentation/admin-guide/media/ttusb-dec.rst | 45 + Documentation/admin-guide/media/tuner-cardlist.rst | 100 + Documentation/admin-guide/media/usb-cardlist.rst | 156 + Documentation/admin-guide/media/v4l-drivers.rst | 34 + Documentation/admin-guide/media/vimc.dot | 26 + Documentation/admin-guide/media/vimc.rst | 110 + Documentation/admin-guide/media/vivid.rst | 1416 ++++ Documentation/admin-guide/media/zoran-cardlist.rst | 51 + Documentation/admin-guide/media/zr364xx.rst | 102 + Documentation/admin-guide/mm/cma_debugfs.rst | 25 + Documentation/admin-guide/mm/concepts.rst | 223 + Documentation/admin-guide/mm/damon/index.rst | 17 + Documentation/admin-guide/mm/damon/lru_sort.rst | 294 + Documentation/admin-guide/mm/damon/reclaim.rst | 265 + Documentation/admin-guide/mm/damon/start.rst | 127 + Documentation/admin-guide/mm/damon/usage.rst | 702 ++ Documentation/admin-guide/mm/hugetlbpage.rst | 475 ++ .../admin-guide/mm/idle_page_tracking.rst | 121 + Documentation/admin-guide/mm/index.rst | 45 + Documentation/admin-guide/mm/ksm.rst | 243 + Documentation/admin-guide/mm/memory-hotplug.rst | 677 ++ Documentation/admin-guide/mm/multigen_lru.rst | 162 + Documentation/admin-guide/mm/nommu-mmap.rst | 283 + .../admin-guide/mm/numa_memory_policy.rst | 516 ++ Documentation/admin-guide/mm/numaperf.rst | 178 + Documentation/admin-guide/mm/pagemap.rst | 232 + Documentation/admin-guide/mm/shrinker_debugfs.rst | 135 + Documentation/admin-guide/mm/soft-dirty.rst | 47 + Documentation/admin-guide/mm/swap_numa.rst | 80 + Documentation/admin-guide/mm/transhuge.rst | 429 + Documentation/admin-guide/mm/userfaultfd.rst | 354 + Documentation/admin-guide/mm/zswap.rst | 168 + Documentation/admin-guide/module-signing.rst | 285 + Documentation/admin-guide/mono.rst | 70 + .../admin-guide/namespaces/compatibility-list.rst | 43 + Documentation/admin-guide/namespaces/index.rst | 11 + .../admin-guide/namespaces/resource-control.rst | 18 + Documentation/admin-guide/nfs/index.rst | 14 + Documentation/admin-guide/nfs/nfs-client.rst | 144 + Documentation/admin-guide/nfs/nfs-idmapper.rst | 78 + Documentation/admin-guide/nfs/nfs-rdma.rst | 292 + .../admin-guide/nfs/nfsd-admin-interfaces.rst | 40 + Documentation/admin-guide/nfs/nfsroot.rst | 364 + .../admin-guide/nfs/pnfs-block-server.rst | 42 + Documentation/admin-guide/nfs/pnfs-scsi-server.rst | 24 + Documentation/admin-guide/numastat.rst | 55 + Documentation/admin-guide/parport.rst | 286 + Documentation/admin-guide/perf-security.rst | 325 + Documentation/admin-guide/perf/alibaba_pmu.rst | 100 + Documentation/admin-guide/perf/arm-ccn.rst | 61 + Documentation/admin-guide/perf/arm-cmn.rst | 65 + Documentation/admin-guide/perf/arm_dsu_pmu.rst | 29 + Documentation/admin-guide/perf/hisi-pcie-pmu.rst | 106 + Documentation/admin-guide/perf/hisi-pmu.rst | 114 + Documentation/admin-guide/perf/hns3-pmu.rst | 136 + Documentation/admin-guide/perf/imx-ddr.rst | 71 + Documentation/admin-guide/perf/index.rst | 21 + Documentation/admin-guide/perf/qcom_l2_pmu.rst | 39 + Documentation/admin-guide/perf/qcom_l3_pmu.rst | 26 + Documentation/admin-guide/perf/thunderx2-pmu.rst | 44 + Documentation/admin-guide/perf/xgene-pmu.rst | 49 + Documentation/admin-guide/pm/amd-pstate.rst | 479 ++ Documentation/admin-guide/pm/cpufreq.rst | 708 ++ Documentation/admin-guide/pm/cpufreq_drivers.rst | 274 + Documentation/admin-guide/pm/cpuidle.rst | 662 ++ Documentation/admin-guide/pm/index.rst | 12 + .../admin-guide/pm/intel-speed-select.rst | 939 +++ Documentation/admin-guide/pm/intel_epb.rst | 41 + Documentation/admin-guide/pm/intel_idle.rst | 272 + Documentation/admin-guide/pm/intel_pstate.rst | 770 ++ .../pm/intel_uncore_frequency_scaling.rst | 60 + Documentation/admin-guide/pm/sleep-states.rst | 291 + Documentation/admin-guide/pm/strategies.rst | 56 + Documentation/admin-guide/pm/suspend-flows.rst | 270 + Documentation/admin-guide/pm/system-wide.rst | 11 + Documentation/admin-guide/pm/working-state.rst | 18 + Documentation/admin-guide/pnp.rst | 288 + Documentation/admin-guide/pstore-blk.rst | 234 + Documentation/admin-guide/ramoops.rst | 164 + Documentation/admin-guide/rapidio.rst | 107 + Documentation/admin-guide/ras.rst | 1219 +++ Documentation/admin-guide/reporting-issues.rst | 1764 +++++ .../admin-guide/reporting-regressions.rst | 451 ++ Documentation/admin-guide/rtc.rst | 140 + Documentation/admin-guide/security-bugs.rst | 93 + Documentation/admin-guide/serial-console.rst | 115 + Documentation/admin-guide/spkguide.txt | 1620 ++++ Documentation/admin-guide/svga.rst | 250 + .../admin-guide/syscall-user-dispatch.rst | 90 + Documentation/admin-guide/sysctl/abi.rst | 34 + Documentation/admin-guide/sysctl/fs.rst | 384 + Documentation/admin-guide/sysctl/index.rst | 98 + Documentation/admin-guide/sysctl/kernel.rst | 1596 ++++ Documentation/admin-guide/sysctl/net.rst | 499 ++ Documentation/admin-guide/sysctl/sunrpc.rst | 25 + Documentation/admin-guide/sysctl/user.rst | 84 + Documentation/admin-guide/sysctl/vm.rst | 1046 +++ Documentation/admin-guide/sysfs-rules.rst | 192 + Documentation/admin-guide/sysrq.rst | 294 + Documentation/admin-guide/tainted-kernels.rst | 184 + Documentation/admin-guide/thunderbolt.rst | 336 + Documentation/admin-guide/ufs.rst | 68 + Documentation/admin-guide/unicode.rst | 189 + Documentation/admin-guide/vga-softcursor.rst | 62 + Documentation/admin-guide/video-output.rst | 34 + Documentation/admin-guide/xfs.rst | 543 ++ Documentation/arc/arc.rst | 85 + Documentation/arc/features.rst | 3 + Documentation/arc/index.rst | 17 + Documentation/arch.rst | 28 + Documentation/arm/arm.rst | 212 + Documentation/arm/booting.rst | 237 + Documentation/arm/cluster-pm-race-avoidance.rst | 533 ++ Documentation/arm/features.rst | 3 + Documentation/arm/firmware.rst | 72 + Documentation/arm/google/chromebook-boot-flow.rst | 69 + Documentation/arm/index.rst | 87 + Documentation/arm/interrupts.rst | 169 + Documentation/arm/ixp4xx.rst | 173 + Documentation/arm/kernel_mode_neon.rst | 124 + Documentation/arm/kernel_user_helpers.rst | 268 + Documentation/arm/keystone/knav-qmss.rst | 60 + Documentation/arm/keystone/overview.rst | 74 + Documentation/arm/marvell.rst | 525 ++ Documentation/arm/mem_alignment.rst | 63 + Documentation/arm/memory.rst | 103 + Documentation/arm/microchip.rst | 230 + Documentation/arm/netwinder.rst | 85 + Documentation/arm/nwfpe/index.rst | 13 + Documentation/arm/nwfpe/netwinder-fpe.rst | 162 + Documentation/arm/nwfpe/notes.rst | 32 + Documentation/arm/nwfpe/nwfpe.rst | 74 + Documentation/arm/nwfpe/todo.rst | 72 + Documentation/arm/omap/dss.rst | 372 + Documentation/arm/omap/index.rst | 12 + Documentation/arm/omap/omap.rst | 18 + Documentation/arm/omap/omap_pm.rst | 165 + Documentation/arm/porting.rst | 137 + Documentation/arm/pxa/mfp.rst | 288 + Documentation/arm/sa1100/assabet.rst | 301 + Documentation/arm/sa1100/cerf.rst | 35 + Documentation/arm/sa1100/index.rst | 13 + Documentation/arm/sa1100/lart.rst | 15 + Documentation/arm/sa1100/serial_uart.rst | 51 + Documentation/arm/samsung-s3c24xx/cpufreq.rst | 77 + Documentation/arm/samsung-s3c24xx/eb2410itx.rst | 59 + Documentation/arm/samsung-s3c24xx/gpio.rst | 172 + Documentation/arm/samsung-s3c24xx/h1940.rst | 41 + Documentation/arm/samsung-s3c24xx/index.rst | 20 + Documentation/arm/samsung-s3c24xx/nand.rst | 30 + Documentation/arm/samsung-s3c24xx/overview.rst | 311 + Documentation/arm/samsung-s3c24xx/s3c2412.rst | 121 + Documentation/arm/samsung-s3c24xx/s3c2413.rst | 22 + Documentation/arm/samsung-s3c24xx/smdk2440.rst | 57 + Documentation/arm/samsung-s3c24xx/suspend.rst | 137 + Documentation/arm/samsung-s3c24xx/usb-host.rst | 91 + Documentation/arm/samsung/bootloader-interface.rst | 81 + .../arm/samsung/clksrc-change-registers.awk | 166 + Documentation/arm/samsung/gpio.rst | 40 + Documentation/arm/samsung/index.rst | 12 + Documentation/arm/samsung/overview.rst | 89 + Documentation/arm/setup.rst | 108 + Documentation/arm/spear/overview.rst | 66 + Documentation/arm/sti/overview.rst | 36 + Documentation/arm/sti/stih407-overview.rst | 19 + Documentation/arm/sti/stih415-overview.rst | 14 + Documentation/arm/sti/stih416-overview.rst | 13 + Documentation/arm/sti/stih418-overview.rst | 21 + Documentation/arm/stm32/overview.rst | 34 + .../arm/stm32/stm32-dma-mdma-chaining.rst | 415 + Documentation/arm/stm32/stm32f429-overview.rst | 25 + Documentation/arm/stm32/stm32f746-overview.rst | 32 + Documentation/arm/stm32/stm32f769-overview.rst | 34 + Documentation/arm/stm32/stm32h743-overview.rst | 33 + Documentation/arm/stm32/stm32h750-overview.rst | 34 + Documentation/arm/stm32/stm32mp13-overview.rst | 37 + Documentation/arm/stm32/stm32mp157-overview.rst | 20 + Documentation/arm/sunxi.rst | 170 + Documentation/arm/sunxi/clocks.rst | 57 + Documentation/arm/swp_emulation.rst | 27 + Documentation/arm/tcm.rst | 161 + Documentation/arm/uefi.rst | 70 + Documentation/arm/vfp/release-notes.rst | 57 + Documentation/arm/vlocks.rst | 212 + Documentation/arm64/acpi_object_usage.rst | 738 ++ Documentation/arm64/amu.rst | 119 + Documentation/arm64/arm-acpi.rst | 528 ++ Documentation/arm64/asymmetric-32bit.rst | 155 + Documentation/arm64/booting.rst | 420 + Documentation/arm64/cpu-feature-registers.rst | 400 + Documentation/arm64/elf_hwcaps.rst | 282 + Documentation/arm64/features.rst | 3 + Documentation/arm64/hugetlbpage.rst | 43 + Documentation/arm64/index.rst | 36 + Documentation/arm64/kasan-offsets.sh | 26 + Documentation/arm64/legacy_instructions.rst | 68 + Documentation/arm64/memory-tagging-extension.rst | 375 + Documentation/arm64/memory.rst | 167 + Documentation/arm64/perf.rst | 166 + Documentation/arm64/pointer-authentication.rst | 142 + Documentation/arm64/silicon-errata.rst | 223 + Documentation/arm64/sme.rst | 431 + Documentation/arm64/sve.rst | 615 ++ Documentation/arm64/tagged-address-abi.rst | 179 + Documentation/arm64/tagged-pointers.rst | 88 + Documentation/atomic_bitops.txt | 69 + Documentation/atomic_t.txt | 367 + Documentation/block/bfq-iosched.rst | 606 ++ Documentation/block/biovecs.rst | 150 + Documentation/block/blk-mq.rst | 153 + Documentation/block/capability.rst | 10 + Documentation/block/cmdline-partition.rst | 53 + Documentation/block/data-integrity.rst | 291 + Documentation/block/deadline-iosched.rst | 72 + Documentation/block/index.rst | 26 + Documentation/block/inline-encryption.rst | 304 + Documentation/block/ioprio.rst | 182 + Documentation/block/kyber-iosched.rst | 15 + Documentation/block/null_blk.rst | 151 + Documentation/block/pr.rst | 119 + Documentation/block/request.rst | 99 + Documentation/block/stat.rst | 103 + Documentation/block/switching-sched.rst | 35 + Documentation/block/ublk.rst | 289 + Documentation/block/writeback_cache_control.rst | 86 + Documentation/bpf/bpf_design_QA.rst | 300 + Documentation/bpf/bpf_devel_QA.rst | 668 ++ Documentation/bpf/bpf_licensing.rst | 92 + Documentation/bpf/bpf_prog_run.rst | 117 + Documentation/bpf/btf.rst | 1065 +++ Documentation/bpf/clang-notes.rst | 30 + Documentation/bpf/classic_vs_extended.rst | 376 + Documentation/bpf/drgn.rst | 213 + Documentation/bpf/faq.rst | 11 + Documentation/bpf/helpers.rst | 7 + Documentation/bpf/index.rst | 41 + Documentation/bpf/instruction-set.rst | 340 + Documentation/bpf/kfuncs.rst | 193 + Documentation/bpf/libbpf/index.rst | 21 + Documentation/bpf/libbpf/libbpf_build.rst | 37 + .../bpf/libbpf/libbpf_naming_convention.rst | 193 + Documentation/bpf/linux-notes.rst | 53 + Documentation/bpf/llvm_reloc.rst | 240 + Documentation/bpf/map_cgroup_storage.rst | 169 + Documentation/bpf/map_hash.rst | 185 + Documentation/bpf/maps.rst | 52 + Documentation/bpf/other.rst | 9 + Documentation/bpf/prog_cgroup_sockopt.rst | 107 + Documentation/bpf/prog_cgroup_sysctl.rst | 125 + Documentation/bpf/prog_flow_dissector.rst | 147 + Documentation/bpf/prog_lsm.rst | 143 + Documentation/bpf/prog_sk_lookup.rst | 98 + Documentation/bpf/programs.rst | 9 + Documentation/bpf/ringbuf.rst | 206 + Documentation/bpf/s390.rst | 205 + Documentation/bpf/syscall_api.rst | 11 + Documentation/bpf/test_debug.rst | 9 + Documentation/bpf/verifier.rst | 529 ++ Documentation/cdrom/cdrom-standard.rst | 1048 +++ Documentation/cdrom/index.rst | 18 + Documentation/cdrom/packet-writing.rst | 139 + Documentation/conf.py | 668 ++ Documentation/core-api/asm-annotations.rst | 222 + Documentation/core-api/assoc_array.rst | 554 ++ Documentation/core-api/boot-time-mm.rst | 41 + Documentation/core-api/cachetlb.rst | 399 + Documentation/core-api/circular-buffers.rst | 237 + Documentation/core-api/cpu_hotplug.rst | 756 ++ Documentation/core-api/debug-objects.rst | 310 + Documentation/core-api/debugging-via-ohci1394.rst | 185 + Documentation/core-api/dma-api-howto.rst | 915 +++ Documentation/core-api/dma-api.rst | 846 ++ Documentation/core-api/dma-attributes.rst | 132 + Documentation/core-api/dma-isa-lpc.rst | 152 + Documentation/core-api/entry.rst | 279 + Documentation/core-api/errseq.rst | 159 + Documentation/core-api/genalloc.rst | 144 + Documentation/core-api/generic-radix-tree.rst | 12 + Documentation/core-api/genericirq.rst | 444 ++ Documentation/core-api/gfp_mask-from-fs-io.rst | 68 + Documentation/core-api/idr.rst | 84 + Documentation/core-api/index.rst | 136 + Documentation/core-api/irq/concepts.rst | 24 + Documentation/core-api/irq/index.rst | 11 + Documentation/core-api/irq/irq-affinity.rst | 70 + Documentation/core-api/irq/irq-domain.rst | 297 + Documentation/core-api/irq/irqflags-tracing.rst | 52 + Documentation/core-api/kernel-api.rst | 396 + Documentation/core-api/kobject.rst | 434 + Documentation/core-api/kref.rst | 323 + Documentation/core-api/librs.rst | 212 + Documentation/core-api/local_ops.rst | 202 + Documentation/core-api/maple_tree.rst | 217 + Documentation/core-api/memory-allocation.rst | 176 + Documentation/core-api/memory-hotplug.rst | 122 + Documentation/core-api/mm-api.rst | 117 + Documentation/core-api/packing.rst | 166 + Documentation/core-api/padata.rst | 178 + Documentation/core-api/pin_user_pages.rst | 279 + Documentation/core-api/printk-basics.rst | 112 + Documentation/core-api/printk-formats.rst | 644 ++ Documentation/core-api/printk-index.rst | 137 + Documentation/core-api/protection-keys.rst | 98 + Documentation/core-api/rbtree.rst | 429 + Documentation/core-api/refcount-vs-atomic.rst | 168 + Documentation/core-api/symbol-namespaces.rst | 157 + Documentation/core-api/this_cpu_ops.rst | 339 + Documentation/core-api/timekeeping.rst | 190 + Documentation/core-api/tracepoint.rst | 55 + Documentation/core-api/unaligned-memory-access.rst | 265 + Documentation/core-api/watch_queue.rst | 343 + Documentation/core-api/workqueue.rst | 413 + Documentation/core-api/wrappers/atomic_bitops.rst | 18 + Documentation/core-api/wrappers/atomic_t.rst | 19 + .../core-api/wrappers/memory-barriers.rst | 18 + Documentation/core-api/xarray.rst | 496 ++ Documentation/cpu-freq/core.rst | 113 + Documentation/cpu-freq/cpu-drivers.rst | 286 + Documentation/cpu-freq/cpufreq-stats.rst | 136 + Documentation/cpu-freq/index.rst | 39 + Documentation/crypto/api-aead.rst | 23 + Documentation/crypto/api-akcipher.rst | 20 + Documentation/crypto/api-digest.rst | 35 + Documentation/crypto/api-intro.rst | 262 + Documentation/crypto/api-kpp.rst | 38 + Documentation/crypto/api-rng.rst | 14 + Documentation/crypto/api-samples.rst | 187 + Documentation/crypto/api-skcipher.rst | 35 + Documentation/crypto/api.rst | 16 + Documentation/crypto/architecture.rst | 414 + Documentation/crypto/asymmetric-keys.rst | 424 + Documentation/crypto/async-tx-api.rst | 270 + Documentation/crypto/crypto_engine.rst | 86 + Documentation/crypto/descore-readme.rst | 414 + Documentation/crypto/devel-algos.rst | 240 + Documentation/crypto/index.rst | 30 + Documentation/crypto/intro.rst | 74 + Documentation/crypto/userspace-if.rst | 401 + Documentation/dev-tools/checkpatch.rst | 1256 +++ Documentation/dev-tools/coccinelle.rst | 519 ++ Documentation/dev-tools/gcov.rst | 274 + Documentation/dev-tools/gdb-kernel-debugging.rst | 179 + Documentation/dev-tools/index.rst | 44 + Documentation/dev-tools/kasan.rst | 529 ++ Documentation/dev-tools/kcov.rst | 339 + Documentation/dev-tools/kcsan.rst | 366 + Documentation/dev-tools/kfence.rst | 333 + Documentation/dev-tools/kgdb.rst | 939 +++ Documentation/dev-tools/kmemleak.rst | 258 + Documentation/dev-tools/kmsan.rst | 428 + Documentation/dev-tools/kselftest.rst | 392 + Documentation/dev-tools/ktap.rst | 311 + Documentation/dev-tools/kunit/api/index.rst | 20 + Documentation/dev-tools/kunit/api/resource.rst | 13 + Documentation/dev-tools/kunit/api/test.rst | 10 + Documentation/dev-tools/kunit/architecture.rst | 195 + Documentation/dev-tools/kunit/faq.rst | 104 + Documentation/dev-tools/kunit/index.rst | 113 + .../dev-tools/kunit/kunit_suitememorydiagram.svg | 81 + Documentation/dev-tools/kunit/run_manual.rst | 57 + Documentation/dev-tools/kunit/run_wrapper.rst | 323 + Documentation/dev-tools/kunit/running_tips.rst | 264 + Documentation/dev-tools/kunit/start.rst | 306 + Documentation/dev-tools/kunit/style.rst | 202 + Documentation/dev-tools/kunit/tips.rst | 190 + Documentation/dev-tools/kunit/usage.rst | 705 ++ Documentation/dev-tools/sparse.rst | 104 + Documentation/dev-tools/testing-overview.rst | 180 + Documentation/dev-tools/ubsan.rst | 89 + Documentation/devicetree/bindings/.gitignore | 4 + Documentation/devicetree/bindings/.yamllint | 39 + Documentation/devicetree/bindings/ABI.rst | 42 + Documentation/devicetree/bindings/Makefile | 80 + .../devicetree/bindings/arc/archs-pct.txt | 17 + Documentation/devicetree/bindings/arc/axs101.txt | 7 + Documentation/devicetree/bindings/arc/axs103.txt | 8 + Documentation/devicetree/bindings/arc/eznps.txt | 7 + Documentation/devicetree/bindings/arc/hsdk.txt | 7 + Documentation/devicetree/bindings/arc/pct.txt | 20 + Documentation/devicetree/bindings/arm/actions.yaml | 53 + Documentation/devicetree/bindings/arm/airoha.yaml | 28 + Documentation/devicetree/bindings/arm/altera.yaml | 67 + .../bindings/arm/altera/socfpga-clk-manager.yaml | 33 + .../arm/altera/socfpga-sdram-controller.txt | 12 + .../bindings/arm/altera/socfpga-sdram-edac.txt | 15 + .../bindings/arm/altera/socfpga-system.txt | 25 + .../devicetree/bindings/arm/amazon,al.yaml | 35 + Documentation/devicetree/bindings/arm/amlogic.yaml | 202 + .../arm/amlogic/amlogic,meson-gx-ao-secure.yaml | 54 + .../arm/amlogic/amlogic,meson-mx-secbus2.yaml | 42 + .../devicetree/bindings/arm/amlogic/analog-top.txt | 20 + .../devicetree/bindings/arm/amlogic/assist.txt | 17 + .../devicetree/bindings/arm/amlogic/bootrom.txt | 17 + .../devicetree/bindings/arm/amlogic/pmu.txt | 18 + Documentation/devicetree/bindings/arm/apm/scu.txt | 17 + Documentation/devicetree/bindings/arm/apple.yaml | 87 + .../devicetree/bindings/arm/apple/apple,pmgr.yaml | 134 + .../devicetree/bindings/arm/arm,cci-400.yaml | 211 + .../bindings/arm/arm,coresight-catu.yaml | 104 + .../bindings/arm/arm,coresight-cpu-debug.yaml | 81 + .../devicetree/bindings/arm/arm,coresight-cti.yaml | 334 + .../bindings/arm/arm,coresight-dynamic-funnel.yaml | 129 + .../arm/arm,coresight-dynamic-replicator.yaml | 129 + .../bindings/arm/arm,coresight-etb10.yaml | 95 + .../devicetree/bindings/arm/arm,coresight-etm.yaml | 159 + .../bindings/arm/arm,coresight-static-funnel.yaml | 93 + .../arm/arm,coresight-static-replicator.yaml | 94 + .../devicetree/bindings/arm/arm,coresight-stm.yaml | 104 + .../devicetree/bindings/arm/arm,coresight-tmc.yaml | 137 + .../bindings/arm/arm,coresight-tpiu.yaml | 94 + .../devicetree/bindings/arm/arm,corstone1000.yaml | 45 + .../bindings/arm/arm,embedded-trace-extension.yaml | 77 + .../devicetree/bindings/arm/arm,integrator.yaml | 88 + .../devicetree/bindings/arm/arm,realview.yaml | 125 + Documentation/devicetree/bindings/arm/arm,scu.yaml | 46 + .../bindings/arm/arm,trace-buffer-extension.yaml | 49 + .../bindings/arm/arm,versatile-sysreg.yaml | 35 + .../devicetree/bindings/arm/arm,versatile.yaml | 73 + .../devicetree/bindings/arm/arm,vexpress-juno.yaml | 229 + .../devicetree/bindings/arm/aspeed/aspeed,sbc.yaml | 37 + .../devicetree/bindings/arm/aspeed/aspeed.yaml | 89 + .../devicetree/bindings/arm/atmel-at91.yaml | 237 + .../devicetree/bindings/arm/atmel-sysregs.txt | 191 + Documentation/devicetree/bindings/arm/axis.txt | 29 + Documentation/devicetree/bindings/arm/axxia.yaml | 23 + .../devicetree/bindings/arm/bcm/bcm2835.yaml | 59 + .../devicetree/bindings/arm/bcm/brcm,bcm11351.yaml | 23 + .../devicetree/bindings/arm/bcm/brcm,bcm21664.yaml | 23 + .../devicetree/bindings/arm/bcm/brcm,bcm23550.yaml | 23 + .../devicetree/bindings/arm/bcm/brcm,bcm4708.yaml | 106 + .../devicetree/bindings/arm/bcm/brcm,bcm63138.txt | 85 + .../devicetree/bindings/arm/bcm/brcm,bcmbca.yaml | 151 + .../devicetree/bindings/arm/bcm/brcm,brcmstb.txt | 258 + .../devicetree/bindings/arm/bcm/brcm,cygnus.yaml | 31 + .../devicetree/bindings/arm/bcm/brcm,hr2.yaml | 30 + .../devicetree/bindings/arm/bcm/brcm,ns2.yaml | 25 + .../devicetree/bindings/arm/bcm/brcm,nsp.yaml | 83 + .../devicetree/bindings/arm/bcm/brcm,stingray.yaml | 26 + .../bindings/arm/bcm/brcm,vulcan-soc.yaml | 24 + .../arm/bcm/raspberrypi,bcm2835-firmware.yaml | 108 + Documentation/devicetree/bindings/arm/bitmain.yaml | 23 + Documentation/devicetree/bindings/arm/calxeda.yaml | 24 + .../devicetree/bindings/arm/calxeda/hb-sregs.yaml | 49 + .../devicetree/bindings/arm/calxeda/l2ecc.yaml | 42 + .../devicetree/bindings/arm/cavium-thunder.txt | 10 + .../devicetree/bindings/arm/cavium-thunder2.txt | 8 + .../devicetree/bindings/arm/cci-control-port.yaml | 38 + .../devicetree/bindings/arm/cpu-capacity.txt | 238 + .../bindings/arm/cpu-enable-method/al,alpine-smp | 80 + .../arm/cpu-enable-method/marvell,berlin-smp | 41 + .../arm/cpu-enable-method/nuvoton,npcm750-smp | 42 + Documentation/devicetree/bindings/arm/cpus.yaml | 566 ++ .../devicetree/bindings/arm/digicolor.yaml | 20 + .../bindings/arm/firmware/linaro,optee-tz.yaml | 66 + .../devicetree/bindings/arm/firmware/sdei.txt | 42 + .../arm/firmware/tlm,trusted-foundations.yaml | 46 + .../bindings/arm/freescale/fsl,imx7ulp-pm.yaml | 42 + .../bindings/arm/freescale/fsl,imx7ulp-sim.yaml | 38 + .../arm/freescale/fsl,vf610-mscm-cpucfg.txt | 14 + .../bindings/arm/freescale/fsl,vf610-mscm-ir.txt | 30 + .../devicetree/bindings/arm/freescale/m4if.txt | 12 + .../devicetree/bindings/arm/freescale/tigerp.txt | 12 + Documentation/devicetree/bindings/arm/fsl.yaml | 1264 +++ Documentation/devicetree/bindings/arm/gemini.yaml | 95 + .../bindings/arm/hisilicon/controller/cpuctrl.yaml | 54 + .../hisilicon/controller/hi3798cv200-perictrl.yaml | 64 + .../hisilicon/controller/hi6220-domain-ctrl.yaml | 68 + .../hisilicon/controller/hip04-bootwrapper.yaml | 35 + .../arm/hisilicon/controller/hip04-fabric.yaml | 27 + .../bindings/arm/hisilicon/controller/pctrl.yaml | 34 + .../bindings/arm/hisilicon/controller/sysctrl.yaml | 132 + .../bindings/arm/hisilicon/hisilicon.yaml | 70 + .../bindings/arm/hisilicon/low-pin-count.yaml | 61 + Documentation/devicetree/bindings/arm/hpe,gxp.yaml | 27 + .../devicetree/bindings/arm/intel,keembay.yaml | 24 + .../devicetree/bindings/arm/intel,socfpga.yaml | 27 + .../devicetree/bindings/arm/intel-ixp4xx.yaml | 27 + .../devicetree/bindings/arm/keystone/keystone.txt | 42 + .../bindings/arm/keystone/ti,k3-sci-common.yaml | 46 + .../devicetree/bindings/arm/keystone/ti,sci.yaml | 129 + Documentation/devicetree/bindings/arm/l2c2x0.yaml | 242 + .../devicetree/bindings/arm/linux,dummy-virt.yaml | 20 + .../bindings/arm/marvell/98dx3236-resume-ctrl.txt | 16 + .../devicetree/bindings/arm/marvell/98dx3236.txt | 23 + .../arm/marvell/ap80x-system-controller.txt | 185 + .../bindings/arm/marvell/armada-370-xp-pmsu.txt | 21 + .../bindings/arm/marvell/armada-370-xp.txt | 24 + .../devicetree/bindings/arm/marvell/armada-375.txt | 9 + .../bindings/arm/marvell/armada-37xx.txt | 32 + .../bindings/arm/marvell/armada-37xx.yaml | 47 + .../arm/marvell/armada-380-mpcore-soc-ctrl.txt | 14 + .../devicetree/bindings/arm/marvell/armada-38x.txt | 27 + .../devicetree/bindings/arm/marvell/armada-39x.txt | 31 + .../bindings/arm/marvell/armada-7k-8k.yaml | 63 + .../devicetree/bindings/arm/marvell/armada-8kp.txt | 15 + .../bindings/arm/marvell/armada-cpu-reset.txt | 14 + .../bindings/arm/marvell/coherency-fabric.txt | 48 + .../arm/marvell/cp110-system-controller.txt | 234 + .../devicetree/bindings/arm/marvell/kirkwood.txt | 27 + .../bindings/arm/marvell/marvell,ac5.yaml | 32 + .../bindings/arm/marvell/marvell,dove.txt | 22 + .../bindings/arm/marvell/marvell,kirkwood.txt | 105 + .../bindings/arm/marvell/marvell,orion5x.txt | 25 + .../bindings/arm/marvell/mvebu-cpu-config.txt | 20 + .../arm/marvell/mvebu-system-controller.txt | 18 + .../devicetree/bindings/arm/mediatek.yaml | 252 + .../bindings/arm/mediatek/mediatek,audsys.txt | 39 + .../bindings/arm/mediatek/mediatek,bdpsys.txt | 24 + .../bindings/arm/mediatek/mediatek,camsys.txt | 24 + .../bindings/arm/mediatek/mediatek,ethsys.txt | 28 + .../bindings/arm/mediatek/mediatek,g3dsys.txt | 30 + .../bindings/arm/mediatek/mediatek,hifsys.txt | 26 + .../bindings/arm/mediatek/mediatek,imgsys.txt | 30 + .../bindings/arm/mediatek/mediatek,infracfg.yaml | 83 + .../bindings/arm/mediatek/mediatek,ipesys.txt | 22 + .../bindings/arm/mediatek/mediatek,ipu.txt | 43 + .../bindings/arm/mediatek/mediatek,jpgdecsys.txt | 22 + .../bindings/arm/mediatek/mediatek,mcucfg.txt | 23 + .../bindings/arm/mediatek/mediatek,mfgcfg.txt | 25 + .../bindings/arm/mediatek/mediatek,mipi0a.txt | 28 + .../bindings/arm/mediatek/mediatek,mmsys.yaml | 98 + .../arm/mediatek/mediatek,mt7622-pcie-mirror.yaml | 42 + .../bindings/arm/mediatek/mediatek,mt7622-wed.yaml | 51 + .../arm/mediatek/mediatek,mt7986-wed-pcie.yaml | 43 + .../arm/mediatek/mediatek,mt8186-clock.yaml | 56 + .../arm/mediatek/mediatek,mt8186-sys-clock.yaml | 57 + .../arm/mediatek/mediatek,mt8192-clock.yaml | 191 + .../arm/mediatek/mediatek,mt8192-sys-clock.yaml | 68 + .../arm/mediatek/mediatek,mt8195-clock.yaml | 254 + .../arm/mediatek/mediatek,mt8195-sys-clock.yaml | 76 + .../bindings/arm/mediatek/mediatek,pciesys.txt | 25 + .../bindings/arm/mediatek/mediatek,pericfg.yaml | 70 + .../bindings/arm/mediatek/mediatek,sgmiisys.txt | 25 + .../bindings/arm/mediatek/mediatek,ssusbsys.txt | 25 + .../bindings/arm/mediatek/mediatek,vcodecsys.txt | 27 + .../bindings/arm/mediatek/mediatek,vdecsys.txt | 29 + .../bindings/arm/mediatek/mediatek,vencltsys.txt | 22 + .../bindings/arm/mediatek/mediatek,vencsys.txt | 26 + .../devicetree/bindings/arm/microchip,sparx5.yaml | 67 + Documentation/devicetree/bindings/arm/moxart.yaml | 20 + .../devicetree/bindings/arm/mrvl/feroceon.txt | 16 + .../devicetree/bindings/arm/mrvl/mrvl.yaml | 41 + .../devicetree/bindings/arm/mrvl/tauros2.txt | 17 + .../bindings/arm/msm/qcom,idle-state.txt | 84 + .../devicetree/bindings/arm/msm/qcom,kpss-acc.txt | 49 + .../devicetree/bindings/arm/msm/qcom,kpss-gcc.txt | 44 + .../devicetree/bindings/arm/msm/qcom,llcc.yaml | 64 + .../devicetree/bindings/arm/msm/qcom,saw2.txt | 58 + Documentation/devicetree/bindings/arm/msm/ssbi.txt | 18 + .../bindings/arm/mstar/mstar,l3bridge.yaml | 44 + .../bindings/arm/mstar/mstar,smpctrl.yaml | 40 + .../devicetree/bindings/arm/mstar/mstar.yaml | 46 + .../devicetree/bindings/arm/npcm/npcm.yaml | 36 + .../devicetree/bindings/arm/npcm/nuvoton,gcr.yaml | 50 + .../bindings/arm/nvidia,tegra194-ccplex.yaml | 71 + .../devicetree/bindings/arm/nxp/lpc32xx.yaml | 26 + .../devicetree/bindings/arm/omap/counter.txt | 15 + .../devicetree/bindings/arm/omap/crossbar.txt | 55 + .../devicetree/bindings/arm/omap/ctrl.txt | 82 + Documentation/devicetree/bindings/arm/omap/dmm.txt | 22 + Documentation/devicetree/bindings/arm/omap/dsp.txt | 14 + Documentation/devicetree/bindings/arm/omap/iva.txt | 19 + .../devicetree/bindings/arm/omap/l3-noc.txt | 23 + Documentation/devicetree/bindings/arm/omap/l4.txt | 37 + Documentation/devicetree/bindings/arm/omap/mpu.txt | 54 + .../devicetree/bindings/arm/omap/omap.txt | 225 + .../devicetree/bindings/arm/omap/prcm.txt | 68 + .../devicetree/bindings/arm/omap/prm-inst.txt | 31 + Documentation/devicetree/bindings/arm/oxnas.txt | 14 + Documentation/devicetree/bindings/arm/pmu.yaml | 111 + .../devicetree/bindings/arm/primecell.yaml | 39 + Documentation/devicetree/bindings/arm/psci.yaml | 263 + Documentation/devicetree/bindings/arm/qcom.yaml | 744 ++ Documentation/devicetree/bindings/arm/rda.yaml | 24 + Documentation/devicetree/bindings/arm/realtek.yaml | 60 + Documentation/devicetree/bindings/arm/renesas.yaml | 471 ++ .../devicetree/bindings/arm/rockchip.yaml | 744 ++ .../devicetree/bindings/arm/rockchip/pmu.yaml | 63 + .../devicetree/bindings/arm/rtsm-dcscb.txt | 19 + .../bindings/arm/samsung/samsung-boards.yaml | 225 + .../arm/samsung/samsung-secure-firmware.yaml | 33 + .../bindings/arm/samsung/samsung-soc.yaml | 40 + Documentation/devicetree/bindings/arm/secure.txt | 70 + .../bindings/arm/socionext/milbeaut.yaml | 25 + .../socionext/socionext,uniphier-system-cache.yaml | 101 + .../bindings/arm/socionext/uniphier.yaml | 64 + Documentation/devicetree/bindings/arm/sp810.yaml | 80 + .../devicetree/bindings/arm/spear-misc.txt | 9 + Documentation/devicetree/bindings/arm/spear.yaml | 28 + .../devicetree/bindings/arm/sprd/sprd.yaml | 40 + .../devicetree/bindings/arm/ste-nomadik.txt | 38 + Documentation/devicetree/bindings/arm/sti.yaml | 26 + .../devicetree/bindings/arm/stm32/st,mlahb.yaml | 72 + .../bindings/arm/stm32/st,stm32-syscon.yaml | 60 + .../devicetree/bindings/arm/stm32/stm32.yaml | 154 + .../devicetree/bindings/arm/sunplus,sp7021.yaml | 29 + Documentation/devicetree/bindings/arm/sunxi.yaml | 976 +++ .../arm/sunxi/allwinner,sun4i-a10-mbus.yaml | 168 + .../arm/sunxi/allwinner,sun6i-a31-cpuconfig.yaml | 38 + .../arm/sunxi/allwinner,sun9i-a80-prcm.yaml | 33 + Documentation/devicetree/bindings/arm/swir.txt | 12 + Documentation/devicetree/bindings/arm/syna.txt | 101 + Documentation/devicetree/bindings/arm/tegra.yaml | 171 + .../devicetree/bindings/arm/tegra/nvidia,nvec.txt | 21 + .../arm/tegra/nvidia,tegra-ccplex-cluster.yaml | 51 + .../bindings/arm/tegra/nvidia,tegra186-pmc.yaml | 198 + .../arm/tegra/nvidia,tegra194-axi2apb.yaml | 40 + .../bindings/arm/tegra/nvidia,tegra194-cbb.yaml | 97 + .../bindings/arm/tegra/nvidia,tegra20-ahb.txt | 17 + .../bindings/arm/tegra/nvidia,tegra20-flowctrl.txt | 18 + .../bindings/arm/tegra/nvidia,tegra20-pmc.yaml | 389 + .../bindings/arm/tegra/nvidia,tegra234-cbb.yaml | 74 + Documentation/devicetree/bindings/arm/tesla.yaml | 27 + Documentation/devicetree/bindings/arm/ti/k3.yaml | 76 + .../devicetree/bindings/arm/ti/nspire.yaml | 27 + .../devicetree/bindings/arm/ti/ti,davinci.yaml | 29 + Documentation/devicetree/bindings/arm/toshiba.yaml | 26 + Documentation/devicetree/bindings/arm/ux500.yaml | 73 + .../devicetree/bindings/arm/ux500/boards.txt | 83 + .../devicetree/bindings/arm/ux500/power_domain.txt | 35 + .../devicetree/bindings/arm/vexpress-config.yaml | 285 + .../devicetree/bindings/arm/vexpress-scc.txt | 33 + .../devicetree/bindings/arm/vexpress-sysreg.yaml | 96 + Documentation/devicetree/bindings/arm/vt8500.yaml | 25 + .../bindings/arm/vt8500/via,vt8500-pmc.txt | 13 + Documentation/devicetree/bindings/arm/xen.txt | 62 + Documentation/devicetree/bindings/arm/xilinx.yaml | 137 + .../devicetree/bindings/ata/ahci-common.yaml | 123 + .../devicetree/bindings/ata/ahci-da850.txt | 18 + .../devicetree/bindings/ata/ahci-dm816.txt | 21 + .../devicetree/bindings/ata/ahci-fsl-qoriq.txt | 21 + Documentation/devicetree/bindings/ata/ahci-mtk.txt | 51 + .../devicetree/bindings/ata/ahci-platform.yaml | 135 + Documentation/devicetree/bindings/ata/ahci-st.txt | 35 + .../bindings/ata/allwinner,sun4i-a10-ahci.yaml | 47 + .../bindings/ata/allwinner,sun8i-r40-ahci.yaml | 67 + .../devicetree/bindings/ata/apm-xgene.txt | 77 + .../devicetree/bindings/ata/atmel-at91_cf.txt | 19 + .../devicetree/bindings/ata/baikal,bt1-ahci.yaml | 115 + .../devicetree/bindings/ata/brcm,sata-brcm.yaml | 87 + .../bindings/ata/cavium-compact-flash.txt | 30 + .../devicetree/bindings/ata/ceva,ahci-1v84.yaml | 189 + .../bindings/ata/cortina,gemini-sata-bridge.yaml | 107 + .../devicetree/bindings/ata/faraday,ftide010.yaml | 91 + Documentation/devicetree/bindings/ata/fsl-sata.txt | 28 + Documentation/devicetree/bindings/ata/imx-pata.txt | 16 + .../devicetree/bindings/ata/imx-sata.yaml | 83 + .../bindings/ata/intel,ixp4xx-compact-flash.yaml | 61 + Documentation/devicetree/bindings/ata/marvell.txt | 22 + .../devicetree/bindings/ata/nvidia,tegra-ahci.yaml | 175 + .../devicetree/bindings/ata/pata-arasan.txt | 37 + .../devicetree/bindings/ata/pata-common.yaml | 52 + .../devicetree/bindings/ata/qcom-sata.txt | 48 + .../devicetree/bindings/ata/renesas,rcar-sata.yaml | 84 + .../devicetree/bindings/ata/sata-common.yaml | 57 + .../devicetree/bindings/ata/sata_highbank.yaml | 95 + .../bindings/ata/snps,dwc-ahci-common.yaml | 102 + .../devicetree/bindings/ata/snps,dwc-ahci.yaml | 75 + .../bindings/auxdisplay/arm,versatile-lcd.yaml | 44 + .../bindings/auxdisplay/hit,hd44780.yaml | 125 + .../bindings/auxdisplay/holtek,ht16k33.yaml | 103 + .../bindings/auxdisplay/img,ascii-lcd.yaml | 55 + .../bindings/auxdisplay/modtronix,lcd2s.yaml | 58 + .../devicetree/bindings/board/fsl-board.txt | 81 + .../bindings/bus/allwinner,sun50i-a64-de2.yaml | 87 + .../bindings/bus/allwinner,sun8i-a23-rsb.yaml | 81 + .../bindings/bus/arm,integrator-ap-lm.yaml | 83 + .../devicetree/bindings/bus/baikal,bt1-apb.yaml | 90 + .../devicetree/bindings/bus/baikal,bt1-axi.yaml | 107 + .../devicetree/bindings/bus/brcm,bus-axi.txt | 53 + .../devicetree/bindings/bus/brcm,gisb-arb.yaml | 66 + .../devicetree/bindings/bus/fsl,spba-bus.yaml | 68 + Documentation/devicetree/bindings/bus/imx-weim.txt | 117 + .../bus/intel,ixp4xx-expansion-bus-controller.yaml | 168 + Documentation/devicetree/bindings/bus/moxtet.txt | 46 + .../devicetree/bindings/bus/mti,mips-cdmm.yaml | 37 + .../devicetree/bindings/bus/mvebu-mbus.txt | 276 + .../devicetree/bindings/bus/nvidia,tegra20-gmi.txt | 128 + .../bindings/bus/nvidia,tegra210-aconnect.yaml | 83 + .../devicetree/bindings/bus/omap-ocp2scp.txt | 29 + Documentation/devicetree/bindings/bus/palmbus.yaml | 79 + .../devicetree/bindings/bus/qcom,ebi2.txt | 138 + .../bindings/bus/qcom,ssc-block-bus.yaml | 144 + .../devicetree/bindings/bus/renesas,bsc.yaml | 62 + .../devicetree/bindings/bus/simple-pm-bus.yaml | 77 + .../bus/socionext,uniphier-system-bus.yaml | 103 + .../devicetree/bindings/bus/ti,da850-mstpri.txt | 20 + Documentation/devicetree/bindings/bus/ti-sysc.yaml | 215 + Documentation/devicetree/bindings/bus/ts-nbus.txt | 50 + .../bindings/chrome/google,cros-ec-typec.yaml | 67 + .../chrome/google,cros-kbd-led-backlight.yaml | 35 + .../devicetree/bindings/clock/actions,owl-cmu.txt | 52 + .../devicetree/bindings/clock/adi,axi-clkgen.yaml | 54 + .../bindings/clock/airoha,en7523-scu.yaml | 58 + .../clock/allwinner,sun4i-a10-ahb-clk.yaml | 108 + .../clock/allwinner,sun4i-a10-apb0-clk.yaml | 50 + .../clock/allwinner,sun4i-a10-apb1-clk.yaml | 52 + .../clock/allwinner,sun4i-a10-axi-clk.yaml | 61 + .../bindings/clock/allwinner,sun4i-a10-ccu.yaml | 153 + .../clock/allwinner,sun4i-a10-cpu-clk.yaml | 52 + .../clock/allwinner,sun4i-a10-display-clk.yaml | 57 + .../clock/allwinner,sun4i-a10-gates-clk.yaml | 152 + .../clock/allwinner,sun4i-a10-mbus-clk.yaml | 63 + .../clock/allwinner,sun4i-a10-mmc-clk.yaml | 87 + .../clock/allwinner,sun4i-a10-mod0-clk.yaml | 80 + .../clock/allwinner,sun4i-a10-mod1-clk.yaml | 57 + .../clock/allwinner,sun4i-a10-osc-clk.yaml | 51 + .../clock/allwinner,sun4i-a10-pll1-clk.yaml | 71 + .../clock/allwinner,sun4i-a10-pll3-clk.yaml | 50 + .../clock/allwinner,sun4i-a10-pll5-clk.yaml | 53 + .../clock/allwinner,sun4i-a10-pll6-clk.yaml | 53 + .../clock/allwinner,sun4i-a10-tcon-ch0-clk.yaml | 77 + .../clock/allwinner,sun4i-a10-usb-clk.yaml | 166 + .../bindings/clock/allwinner,sun4i-a10-ve-clk.yaml | 55 + .../clock/allwinner,sun5i-a13-ahb-clk.yaml | 52 + .../clock/allwinner,sun6i-a31-pll6-clk.yaml | 53 + .../clock/allwinner,sun7i-a20-gmac-clk.yaml | 51 + .../clock/allwinner,sun7i-a20-out-clk.yaml | 52 + .../clock/allwinner,sun8i-a83t-de2-clk.yaml | 79 + .../clock/allwinner,sun8i-h3-bus-gates-clk.yaml | 103 + .../clock/allwinner,sun9i-a80-ahb-clk.yaml | 52 + .../clock/allwinner,sun9i-a80-apb0-clk.yaml | 63 + .../clock/allwinner,sun9i-a80-cpus-clk.yaml | 52 + .../clock/allwinner,sun9i-a80-de-clks.yaml | 67 + .../bindings/clock/allwinner,sun9i-a80-gt-clk.yaml | 52 + .../clock/allwinner,sun9i-a80-mmc-config-clk.yaml | 68 + .../clock/allwinner,sun9i-a80-pll4-clk.yaml | 50 + .../clock/allwinner,sun9i-a80-usb-clks.yaml | 59 + .../clock/allwinner,sun9i-a80-usb-mod-clk.yaml | 60 + .../clock/allwinner,sun9i-a80-usb-phy-clk.yaml | 60 + .../devicetree/bindings/clock/alphascale,acc.txt | 114 + .../devicetree/bindings/clock/altr_socfpga.txt | 30 + .../bindings/clock/amlogic,axg-audio-clkc.txt | 59 + .../bindings/clock/amlogic,gxbb-aoclkc.txt | 64 + .../bindings/clock/amlogic,gxbb-clkc.txt | 53 + .../bindings/clock/amlogic,meson8-ddr-clkc.yaml | 50 + .../bindings/clock/amlogic,meson8b-clkc.txt | 51 + .../devicetree/bindings/clock/apple,nco.yaml | 62 + .../devicetree/bindings/clock/arm,syscon-icst.yaml | 110 + .../bindings/clock/armada3700-periph-clock.txt | 71 + .../bindings/clock/armada3700-tbg-clock.txt | 27 + .../bindings/clock/armada3700-xtal-clock.txt | 29 + .../devicetree/bindings/clock/artpec6.txt | 41 + .../devicetree/bindings/clock/at91-clock.txt | 58 + .../bindings/clock/axs10x-i2s-pll-clock.txt | 25 + .../bindings/clock/baikal,bt1-ccu-div.yaml | 192 + .../bindings/clock/baikal,bt1-ccu-pll.yaml | 131 + .../bindings/clock/bitmain,bm1880-clk.yaml | 64 + .../bindings/clock/brcm,bcm2711-dvp.yaml | 47 + .../bindings/clock/brcm,bcm2835-aux-clock.txt | 31 + .../bindings/clock/brcm,bcm2835-cprman.txt | 60 + .../bindings/clock/brcm,bcm53573-ilp.txt | 36 + .../bindings/clock/brcm,bcm63xx-clocks.txt | 24 + .../bindings/clock/brcm,iproc-clocks.yaml | 417 + .../devicetree/bindings/clock/brcm,kona-ccu.txt | 138 + .../devicetree/bindings/clock/calxeda.yaml | 82 + .../devicetree/bindings/clock/canaan,k210-clk.yaml | 55 + .../bindings/clock/cirrus,cs2000-cp.yaml | 90 + .../bindings/clock/cirrus,lochnagar.yaml | 78 + .../bindings/clock/clk-palmas-clk32kg-clocks.txt | 35 + .../devicetree/bindings/clock/clock-bindings.txt | 2 + .../devicetree/bindings/clock/clps711x-clock.txt | 19 + .../bindings/clock/dove-divider-clock.txt | 28 + .../devicetree/bindings/clock/fixed-clock.yaml | 44 + .../bindings/clock/fixed-factor-clock.yaml | 54 + .../bindings/clock/fixed-mmio-clock.yaml | 47 + .../bindings/clock/fsl,flexspi-clock.yaml | 55 + .../devicetree/bindings/clock/fsl,plldig.yaml | 58 + .../devicetree/bindings/clock/fsl,sai-clock.yaml | 55 + .../devicetree/bindings/clock/fsl,scu-clk.yaml | 43 + .../bindings/clock/fujitsu,mb86s70-crg11.txt | 26 + .../devicetree/bindings/clock/gpio-gate-clock.yaml | 42 + .../devicetree/bindings/clock/gpio-mux-clock.yaml | 45 + .../devicetree/bindings/clock/hi3620-clock.txt | 20 + .../devicetree/bindings/clock/hi3660-clock.txt | 47 + .../devicetree/bindings/clock/hi3670-clock.txt | 43 + .../devicetree/bindings/clock/hi6220-clock.txt | 52 + .../devicetree/bindings/clock/hisi-crg.txt | 50 + .../clock/hisilicon,hi3559av100-clock.yaml | 59 + .../devicetree/bindings/clock/hix5hd2-clock.txt | 30 + .../devicetree/bindings/clock/idt,versaclock5.yaml | 196 + .../devicetree/bindings/clock/img,boston-clock.txt | 31 + .../devicetree/bindings/clock/imx1-clock.yaml | 42 + .../devicetree/bindings/clock/imx21-clock.yaml | 42 + .../devicetree/bindings/clock/imx23-clock.yaml | 85 + .../devicetree/bindings/clock/imx25-clock.yaml | 178 + .../devicetree/bindings/clock/imx27-clock.yaml | 46 + .../devicetree/bindings/clock/imx28-clock.yaml | 108 + .../devicetree/bindings/clock/imx31-clock.yaml | 112 + .../devicetree/bindings/clock/imx35-clock.yaml | 131 + .../devicetree/bindings/clock/imx5-clock.yaml | 58 + .../devicetree/bindings/clock/imx6q-clock.yaml | 73 + .../devicetree/bindings/clock/imx6sl-clock.yaml | 49 + .../devicetree/bindings/clock/imx6sll-clock.yaml | 67 + .../devicetree/bindings/clock/imx6sx-clock.yaml | 71 + .../devicetree/bindings/clock/imx6ul-clock.yaml | 67 + .../devicetree/bindings/clock/imx7d-clock.yaml | 65 + .../bindings/clock/imx7ulp-pcc-clock.yaml | 110 + .../bindings/clock/imx7ulp-scg-clock.yaml | 88 + .../devicetree/bindings/clock/imx8m-clock.yaml | 121 + .../devicetree/bindings/clock/imx8qxp-lpcg.yaml | 103 + .../bindings/clock/imx8ulp-cgc-clock.yaml | 43 + .../bindings/clock/imx8ulp-pcc-clock.yaml | 50 + .../devicetree/bindings/clock/imx93-clock.yaml | 62 + .../devicetree/bindings/clock/imxrt1050-clock.yaml | 59 + .../devicetree/bindings/clock/ingenic,cgu.yaml | 130 + .../devicetree/bindings/clock/intel,agilex.yaml | 46 + .../devicetree/bindings/clock/intel,cgu-lgm.yaml | 46 + .../devicetree/bindings/clock/intel,easic-n5x.yaml | 46 + .../devicetree/bindings/clock/intel,stratix10.yaml | 35 + .../devicetree/bindings/clock/keystone-gate.txt | 29 + .../devicetree/bindings/clock/keystone-pll.txt | 84 + .../devicetree/bindings/clock/lpc1850-ccu.txt | 77 + .../devicetree/bindings/clock/lpc1850-cgu.txt | 131 + .../devicetree/bindings/clock/lpc1850-creg-clk.txt | 52 + .../devicetree/bindings/clock/lsi,axm5516-clks.txt | 29 + .../clock/marvell,armada-3700-uart-clock.yaml | 59 + .../devicetree/bindings/clock/marvell,berlin.txt | 31 + .../bindings/clock/marvell,mmp2-audio-clock.yaml | 75 + .../bindings/clock/marvell,mmp2-clock.yaml | 69 + .../devicetree/bindings/clock/marvell,pxa168.txt | 21 + .../devicetree/bindings/clock/marvell,pxa1928.txt | 21 + .../devicetree/bindings/clock/marvell,pxa910.txt | 21 + .../devicetree/bindings/clock/maxim,max77686.txt | 114 + .../devicetree/bindings/clock/maxim,max9485.txt | 59 + .../bindings/clock/mediatek,apmixedsys.yaml | 62 + .../bindings/clock/mediatek,mt6795-clock.yaml | 66 + .../bindings/clock/mediatek,mt6795-sys-clock.yaml | 54 + .../bindings/clock/mediatek,mt7621-sysc.yaml | 80 + .../bindings/clock/mediatek,mt8365-clock.yaml | 42 + .../bindings/clock/mediatek,mt8365-sys-clock.yaml | 47 + .../bindings/clock/mediatek,topckgen.yaml | 62 + .../bindings/clock/microchip,lan966x-gck.yaml | 60 + .../bindings/clock/microchip,mpfs-ccc.yaml | 80 + .../bindings/clock/microchip,mpfs-clkcfg.yaml | 80 + .../devicetree/bindings/clock/microchip,pic32.txt | 39 + .../bindings/clock/microchip,sparx5-dpll.yaml | 52 + .../devicetree/bindings/clock/milbeaut-clock.yaml | 77 + .../bindings/clock/moxa,moxart-clock.txt | 48 + .../bindings/clock/mstar,msc313-cpupll.yaml | 45 + .../bindings/clock/mstar,msc313-mpll.yaml | 46 + .../devicetree/bindings/clock/mvebu-core-clock.txt | 87 + .../bindings/clock/mvebu-corediv-clock.txt | 23 + .../devicetree/bindings/clock/mvebu-cpu-clock.txt | 23 + .../bindings/clock/mvebu-gated-clock.txt | 205 + .../devicetree/bindings/clock/nspire-clock.txt | 24 + .../bindings/clock/nuvoton,npcm750-clk.txt | 100 + .../bindings/clock/nuvoton,npcm845-clk.yaml | 49 + .../bindings/clock/nvidia,tegra124-car.yaml | 108 + .../bindings/clock/nvidia,tegra124-dfll.txt | 155 + .../bindings/clock/nvidia,tegra20-car.yaml | 99 + .../devicetree/bindings/clock/nxp,lpc3220-clk.txt | 30 + .../bindings/clock/nxp,lpc3220-usb-clk.txt | 22 + .../devicetree/bindings/clock/oxnas,stdclk.txt | 28 + .../devicetree/bindings/clock/pistachio-clock.txt | 123 + .../devicetree/bindings/clock/pwm-clock.txt | 26 + .../devicetree/bindings/clock/pxa-clock.txt | 15 + .../devicetree/bindings/clock/qca,ath79-pll.txt | 33 + .../devicetree/bindings/clock/qcom,a53pll.yaml | 63 + .../devicetree/bindings/clock/qcom,a7pll.yaml | 51 + .../bindings/clock/qcom,aoncc-sm8250.yaml | 58 + .../bindings/clock/qcom,audiocc-sm8250.yaml | 58 + .../bindings/clock/qcom,camcc-sm8250.yaml | 68 + .../bindings/clock/qcom,dispcc-sm6125.yaml | 87 + .../bindings/clock/qcom,dispcc-sm6350.yaml | 86 + .../bindings/clock/qcom,dispcc-sm8x50.yaml | 109 + .../bindings/clock/qcom,gcc-apq8064.yaml | 98 + .../bindings/clock/qcom,gcc-apq8084.yaml | 42 + .../bindings/clock/qcom,gcc-ipq8064.yaml | 76 + .../bindings/clock/qcom,gcc-ipq8074.yaml | 58 + .../bindings/clock/qcom,gcc-msm8660.yaml | 54 + .../bindings/clock/qcom,gcc-msm8909.yaml | 58 + .../bindings/clock/qcom,gcc-msm8916.yaml | 66 + .../bindings/clock/qcom,gcc-msm8976.yaml | 84 + .../bindings/clock/qcom,gcc-msm8994.yaml | 57 + .../bindings/clock/qcom,gcc-msm8996.yaml | 69 + .../bindings/clock/qcom,gcc-msm8998.yaml | 68 + .../devicetree/bindings/clock/qcom,gcc-other.yaml | 62 + .../bindings/clock/qcom,gcc-qcm2290.yaml | 55 + .../devicetree/bindings/clock/qcom,gcc-qcs404.yaml | 53 + .../devicetree/bindings/clock/qcom,gcc-sc7180.yaml | 60 + .../devicetree/bindings/clock/qcom,gcc-sc7280.yaml | 79 + .../bindings/clock/qcom,gcc-sc8180x.yaml | 59 + .../bindings/clock/qcom,gcc-sc8280xp.yaml | 115 + .../devicetree/bindings/clock/qcom,gcc-sdm845.yaml | 101 + .../devicetree/bindings/clock/qcom,gcc-sdx55.yaml | 62 + .../devicetree/bindings/clock/qcom,gcc-sdx65.yaml | 67 + .../devicetree/bindings/clock/qcom,gcc-sm6115.yaml | 55 + .../devicetree/bindings/clock/qcom,gcc-sm6125.yaml | 55 + .../devicetree/bindings/clock/qcom,gcc-sm6350.yaml | 59 + .../devicetree/bindings/clock/qcom,gcc-sm8150.yaml | 57 + .../devicetree/bindings/clock/qcom,gcc-sm8250.yaml | 57 + .../devicetree/bindings/clock/qcom,gcc-sm8350.yaml | 81 + .../devicetree/bindings/clock/qcom,gcc-sm8450.yaml | 72 + .../devicetree/bindings/clock/qcom,gcc.yaml | 42 + .../bindings/clock/qcom,gpucc-sdm660.yaml | 76 + .../bindings/clock/qcom,gpucc-sm8350.yaml | 72 + .../devicetree/bindings/clock/qcom,gpucc.yaml | 89 + .../devicetree/bindings/clock/qcom,hfpll.txt | 60 + .../devicetree/bindings/clock/qcom,krait-cc.txt | 34 + .../devicetree/bindings/clock/qcom,lcc.txt | 22 + .../devicetree/bindings/clock/qcom,lpasscc.txt | 26 + .../devicetree/bindings/clock/qcom,mmcc.yaml | 254 + .../bindings/clock/qcom,msm8996-apcc.yaml | 53 + .../bindings/clock/qcom,msm8998-gpucc.yaml | 68 + .../devicetree/bindings/clock/qcom,q6sstopcc.yaml | 43 + .../bindings/clock/qcom,qcm2290-dispcc.yaml | 87 + .../devicetree/bindings/clock/qcom,rpmcc.yaml | 158 + .../devicetree/bindings/clock/qcom,rpmhcc.yaml | 61 + .../bindings/clock/qcom,sc7180-camcc.yaml | 73 + .../bindings/clock/qcom,sc7180-dispcc.yaml | 86 + .../bindings/clock/qcom,sc7180-lpasscorecc.yaml | 108 + .../devicetree/bindings/clock/qcom,sc7180-mss.yaml | 62 + .../bindings/clock/qcom,sc7280-camcc.yaml | 71 + .../bindings/clock/qcom,sc7280-dispcc.yaml | 94 + .../bindings/clock/qcom,sc7280-lpasscc.yaml | 66 + .../bindings/clock/qcom,sc7280-lpasscorecc.yaml | 192 + .../bindings/clock/qcom,sdm845-camcc.yaml | 65 + .../bindings/clock/qcom,sdm845-dispcc.yaml | 101 + .../bindings/clock/qcom,sm6115-dispcc.yaml | 70 + .../devicetree/bindings/clock/qcom,sm6375-gcc.yaml | 52 + .../bindings/clock/qcom,sm8450-camcc.yaml | 80 + .../bindings/clock/qcom,sm8450-dispcc.yaml | 98 + .../devicetree/bindings/clock/qcom,spmi-clkdiv.txt | 59 + .../devicetree/bindings/clock/qcom,turingcc.txt | 19 + .../devicetree/bindings/clock/qcom,videocc.yaml | 88 + .../devicetree/bindings/clock/qoriq-clock.txt | 212 + .../devicetree/bindings/clock/renesas,9series.yaml | 97 + .../bindings/clock/renesas,cpg-clocks.yaml | 241 + .../bindings/clock/renesas,cpg-div6-clock.yaml | 72 + .../bindings/clock/renesas,cpg-mssr.yaml | 124 + .../bindings/clock/renesas,cpg-mstp-clocks.yaml | 82 + .../bindings/clock/renesas,emev2-smu.yaml | 140 + .../bindings/clock/renesas,r9a06g032-sysctrl.yaml | 73 + .../clock/renesas,rcar-usb2-clock-sel.yaml | 101 + .../bindings/clock/renesas,rzg2l-cpg.yaml | 88 + .../bindings/clock/renesas,versaclock7.yaml | 64 + .../bindings/clock/rockchip,px30-cru.yaml | 119 + .../bindings/clock/rockchip,rk3036-cru.yaml | 72 + .../bindings/clock/rockchip,rk3128-cru.yaml | 76 + .../bindings/clock/rockchip,rk3188-cru.yaml | 78 + .../bindings/clock/rockchip,rk3228-cru.yaml | 74 + .../bindings/clock/rockchip,rk3288-cru.yaml | 85 + .../bindings/clock/rockchip,rk3308-cru.yaml | 76 + .../bindings/clock/rockchip,rk3328-cru.txt | 58 + .../bindings/clock/rockchip,rk3368-cru.yaml | 78 + .../bindings/clock/rockchip,rk3399-cru.yaml | 83 + .../bindings/clock/rockchip,rk3568-cru.yaml | 73 + .../bindings/clock/rockchip,rv1108-cru.yaml | 75 + .../bindings/clock/rockchip,rv1126-cru.yaml | 62 + .../bindings/clock/samsung,exynos-audss-clock.yaml | 80 + .../bindings/clock/samsung,exynos-clock.yaml | 59 + .../bindings/clock/samsung,exynos-ext-clock.yaml | 46 + .../clock/samsung,exynos4412-isp-clock.yaml | 63 + .../bindings/clock/samsung,exynos5260-clock.yaml | 382 + .../bindings/clock/samsung,exynos5410-clock.yaml | 66 + .../bindings/clock/samsung,exynos5433-clock.yaml | 524 ++ .../bindings/clock/samsung,exynos7-clock.yaml | 272 + .../bindings/clock/samsung,exynos7885-clock.yaml | 193 + .../bindings/clock/samsung,exynos850-clock.yaml | 292 + .../bindings/clock/samsung,exynosautov9-clock.yaml | 263 + .../devicetree/bindings/clock/samsung,s2mps11.yaml | 44 + .../bindings/clock/samsung,s3c2410-clock.txt | 49 + .../bindings/clock/samsung,s3c2412-clock.txt | 49 + .../bindings/clock/samsung,s3c2443-clock.txt | 55 + .../bindings/clock/samsung,s3c64xx-clock.txt | 76 + .../clock/samsung,s5pv210-audss-clock.yaml | 78 + .../bindings/clock/samsung,s5pv210-clock.yaml | 79 + .../bindings/clock/sifive/fu540-prci.yaml | 60 + .../bindings/clock/sifive/fu740-prci.yaml | 64 + .../devicetree/bindings/clock/silabs,si514.txt | 24 + .../devicetree/bindings/clock/silabs,si5341.txt | 175 + .../devicetree/bindings/clock/silabs,si5351.txt | 126 + .../devicetree/bindings/clock/silabs,si544.txt | 25 + .../devicetree/bindings/clock/silabs,si570.txt | 41 + .../bindings/clock/snps,hsdk-pll-clock.txt | 28 + .../devicetree/bindings/clock/snps,pll-clock.txt | 28 + .../bindings/clock/socionext,uniphier-clock.yaml | 100 + .../devicetree/bindings/clock/sprd,sc9860-clk.txt | 63 + .../bindings/clock/sprd,sc9863a-clk.yaml | 102 + .../devicetree/bindings/clock/sprd,ums512-clk.yaml | 71 + .../devicetree/bindings/clock/st,nomadik.txt | 104 + .../devicetree/bindings/clock/st,stm32-rcc.txt | 138 + .../devicetree/bindings/clock/st,stm32h7-rcc.txt | 71 + .../devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 125 + .../devicetree/bindings/clock/st/st,clkgen-mux.txt | 32 + .../devicetree/bindings/clock/st/st,clkgen-pll.txt | 40 + .../devicetree/bindings/clock/st/st,clkgen.txt | 68 + .../devicetree/bindings/clock/st/st,flexgen.txt | 133 + .../devicetree/bindings/clock/st/st,quadfs.txt | 48 + .../bindings/clock/starfive,jh7100-audclk.yaml | 57 + .../bindings/clock/starfive,jh7100-clkgen.yaml | 56 + .../bindings/clock/stericsson,abx500.txt | 20 + .../bindings/clock/stericsson,u8500-clks.yaml | 178 + .../bindings/clock/sunplus,sp7021-clkc.yaml | 52 + .../devicetree/bindings/clock/tesla,fsd-clock.yaml | 198 + .../bindings/clock/ti,am654-ehrpwm-tbclk.yaml | 40 + .../devicetree/bindings/clock/ti,cdce706.txt | 42 + .../devicetree/bindings/clock/ti,cdce925.txt | 53 + .../devicetree/bindings/clock/ti,lmk04832.yaml | 209 + .../devicetree/bindings/clock/ti,sci-clk.yaml | 49 + .../devicetree/bindings/clock/ti-clkctrl.txt | 63 + .../bindings/clock/ti-keystone-pllctrl.txt | 20 + .../devicetree/bindings/clock/ti/adpll.txt | 41 + .../devicetree/bindings/clock/ti/apll.txt | 45 + .../devicetree/bindings/clock/ti/autoidle.txt | 39 + .../devicetree/bindings/clock/ti/clockdomain.txt | 27 + .../devicetree/bindings/clock/ti/composite.txt | 57 + .../bindings/clock/ti/davinci/da8xx-cfgchip.txt | 93 + .../devicetree/bindings/clock/ti/davinci/pll.txt | 96 + .../devicetree/bindings/clock/ti/davinci/psc.txt | 71 + .../devicetree/bindings/clock/ti/divider.txt | 117 + .../devicetree/bindings/clock/ti/dpll.txt | 105 + .../devicetree/bindings/clock/ti/dra7-atl.txt | 94 + .../devicetree/bindings/clock/ti/fapll.txt | 33 + .../bindings/clock/ti/fixed-factor-clock.txt | 44 + .../devicetree/bindings/clock/ti/gate.txt | 107 + .../devicetree/bindings/clock/ti/interface.txt | 57 + Documentation/devicetree/bindings/clock/ti/mux.txt | 80 + .../devicetree/bindings/clock/ti/ti,clksel.yaml | 51 + .../bindings/clock/toshiba,tmpv770x-pipllct.yaml | 57 + .../bindings/clock/toshiba,tmpv770x-pismu.yaml | 52 + .../devicetree/bindings/clock/vf610-clock.txt | 41 + Documentation/devicetree/bindings/clock/vt8500.txt | 74 + Documentation/devicetree/bindings/clock/xgene.txt | 131 + .../bindings/clock/xlnx,clocking-wizard.yaml | 77 + .../devicetree/bindings/clock/xlnx,versal-clk.yaml | 62 + .../devicetree/bindings/clock/xlnx,zynqmp-clk.txt | 63 + .../devicetree/bindings/clock/zynq-7000.txt | 110 + .../devicetree/bindings/common-properties.txt | 85 + .../bindings/connector/usb-connector.yaml | 393 + .../devicetree/bindings/counter/ftm-quaddec.txt | 18 + .../bindings/counter/interrupt-counter.yaml | 62 + .../bindings/counter/ti,am62-ecap-capture.yaml | 61 + .../devicetree/bindings/counter/ti-eqep.yaml | 50 + .../devicetree/bindings/cpu/cpu-topology.txt | 553 ++ .../devicetree/bindings/cpu/idle-states.yaml | 855 ++ .../bindings/cpufreq/brcm,stb-avs-cpu-freq.txt | 76 + .../devicetree/bindings/cpufreq/cpufreq-dt.txt | 61 + .../bindings/cpufreq/cpufreq-mediatek-hw.yaml | 70 + .../bindings/cpufreq/cpufreq-mediatek.txt | 250 + .../bindings/cpufreq/cpufreq-qcom-hw.yaml | 202 + .../devicetree/bindings/cpufreq/cpufreq-spear.txt | 42 + .../devicetree/bindings/cpufreq/cpufreq-st.txt | 89 + .../devicetree/bindings/cpufreq/imx-cpufreq-dt.txt | 37 + .../bindings/cpufreq/nvidia,tegra124-cpufreq.txt | 40 + .../bindings/cpufreq/nvidia,tegra20-cpufreq.txt | 56 + .../bindings/cpufreq/qcom-cpufreq-nvmem.yaml | 173 + .../devicetree/bindings/cpufreq/ti-cpufreq.txt | 132 + .../crypto/allwinner,sun4i-a10-crypto.yaml | 95 + .../bindings/crypto/allwinner,sun8i-ce.yaml | 84 + .../bindings/crypto/allwinner,sun8i-ss.yaml | 60 + .../devicetree/bindings/crypto/amd-ccp.txt | 17 + .../bindings/crypto/amlogic,gxl-crypto.yaml | 52 + .../devicetree/bindings/crypto/arm,cryptocell.yaml | 53 + .../devicetree/bindings/crypto/artpec6-crypto.txt | 16 + .../bindings/crypto/aspeed,ast2500-hace.yaml | 53 + .../bindings/crypto/atmel,at91sam9g46-aes.yaml | 66 + .../bindings/crypto/atmel,at91sam9g46-sha.yaml | 60 + .../bindings/crypto/atmel,at91sam9g46-tdes.yaml | 64 + .../devicetree/bindings/crypto/brcm,spu-crypto.txt | 22 + .../bindings/crypto/cortina,sl3516-crypto.yaml | 50 + .../devicetree/bindings/crypto/fsl-dcp.yaml | 50 + .../devicetree/bindings/crypto/fsl-imx-sahara.yaml | 37 + .../devicetree/bindings/crypto/fsl-imx-scc.yaml | 54 + .../devicetree/bindings/crypto/fsl-sec2.txt | 65 + .../devicetree/bindings/crypto/fsl-sec4.txt | 553 ++ .../devicetree/bindings/crypto/fsl-sec6.txt | 157 + .../bindings/crypto/hisilicon,hip07-sec.txt | 67 + .../devicetree/bindings/crypto/img-hash.txt | 27 + .../bindings/crypto/inside-secure-safexcel.txt | 40 + .../bindings/crypto/intel,ixp4xx-crypto.yaml | 56 + .../bindings/crypto/intel,keembay-ocs-aes.yaml | 45 + .../bindings/crypto/intel,keembay-ocs-ecc.yaml | 47 + .../bindings/crypto/intel,keembay-ocs-hcu.yaml | 46 + .../devicetree/bindings/crypto/marvell-cesa.txt | 44 + .../devicetree/bindings/crypto/mediatek-crypto.txt | 25 + .../devicetree/bindings/crypto/mv_cesa.txt | 32 + .../devicetree/bindings/crypto/omap-aes.txt | 31 + .../devicetree/bindings/crypto/omap-des.txt | 30 + .../devicetree/bindings/crypto/omap-sham.txt | 28 + .../devicetree/bindings/crypto/qcom,prng.yaml | 43 + .../devicetree/bindings/crypto/qcom-qce.txt | 25 + .../devicetree/bindings/crypto/rockchip-crypto.txt | 28 + .../bindings/crypto/samsung-slimsss.yaml | 45 + .../devicetree/bindings/crypto/samsung-sss.yaml | 57 + .../devicetree/bindings/crypto/st,stm32-crc.yaml | 38 + .../devicetree/bindings/crypto/st,stm32-cryp.yaml | 51 + .../devicetree/bindings/crypto/st,stm32-hash.yaml | 68 + .../devicetree/bindings/crypto/ti,sa2ul.yaml | 86 + .../bindings/crypto/xlnx,zynqmp-aes.yaml | 37 + Documentation/devicetree/bindings/csky/cpus.txt | 73 + Documentation/devicetree/bindings/csky/pmu.txt | 38 + .../bindings/devfreq/event/rockchip-dfi.txt | 18 + .../devfreq/event/samsung,exynos-nocp.yaml | 48 + .../devfreq/event/samsung,exynos-ppmu.yaml | 169 + .../bindings/devfreq/nvidia,tegra30-actmon.yaml | 126 + .../allwinner,sun4i-a10-display-backend.yaml | 272 + .../allwinner,sun4i-a10-display-engine.yaml | 117 + .../allwinner,sun4i-a10-display-frontend.yaml | 125 + .../bindings/display/allwinner,sun4i-a10-hdmi.yaml | 170 + .../bindings/display/allwinner,sun4i-a10-tcon.yaml | 677 ++ .../display/allwinner,sun4i-a10-tv-encoder.yaml | 56 + .../bindings/display/allwinner,sun6i-a31-drc.yaml | 125 + .../display/allwinner,sun6i-a31-mipi-dsi.yaml | 124 + .../display/allwinner,sun8i-a83t-de2-mixer.yaml | 110 + .../display/allwinner,sun8i-a83t-dw-hdmi.yaml | 254 + .../display/allwinner,sun8i-a83t-hdmi-phy.yaml | 115 + .../display/allwinner,sun8i-r40-tcon-top.yaml | 329 + .../bindings/display/allwinner,sun9i-a80-deu.yaml | 120 + .../bindings/display/amlogic,meson-dw-hdmi.yaml | 152 + .../bindings/display/amlogic,meson-vpu.yaml | 145 + .../devicetree/bindings/display/arm,hdlcd.yaml | 89 + .../devicetree/bindings/display/arm,komeda.yaml | 131 + .../devicetree/bindings/display/arm,malidp.yaml | 119 + .../devicetree/bindings/display/arm,pl11x.yaml | 170 + .../bindings/display/armada/marvell,dove-lcd.txt | 30 + .../devicetree/bindings/display/atmel,lcdc.txt | 87 + .../devicetree/bindings/display/atmel/hlcdc-dc.txt | 75 + .../bindings/display/brcm,bcm2711-hdmi.yaml | 141 + .../bindings/display/brcm,bcm2835-dpi.yaml | 61 + .../bindings/display/brcm,bcm2835-dsi0.yaml | 85 + .../bindings/display/brcm,bcm2835-hdmi.yaml | 83 + .../bindings/display/brcm,bcm2835-hvs.yaml | 53 + .../bindings/display/brcm,bcm2835-pixelvalve0.yaml | 45 + .../bindings/display/brcm,bcm2835-txp.yaml | 37 + .../bindings/display/brcm,bcm2835-v3d.yaml | 45 + .../bindings/display/brcm,bcm2835-vc4.yaml | 35 + .../bindings/display/brcm,bcm2835-vec.yaml | 49 + .../bindings/display/bridge/adi,adv7511.yaml | 237 + .../bindings/display/bridge/adi,adv7533.yaml | 182 + .../bindings/display/bridge/analogix,anx7625.yaml | 188 + .../bindings/display/bridge/analogix,anx7814.yaml | 108 + .../bindings/display/bridge/analogix_dp.txt | 51 + .../bindings/display/bridge/anx6345.yaml | 94 + .../bindings/display/bridge/cdns,dsi.txt | 112 + .../bindings/display/bridge/cdns,mhdp8546.yaml | 164 + .../bindings/display/bridge/chipone,icn6211.yaml | 123 + .../bindings/display/bridge/chrontel,ch7033.yaml | 77 + .../bindings/display/bridge/fsl,imx8qxp-ldb.yaml | 173 + .../display/bridge/fsl,imx8qxp-pixel-combiner.yaml | 144 + .../display/bridge/fsl,imx8qxp-pixel-link.yaml | 144 + .../display/bridge/fsl,imx8qxp-pxl2dpi.yaml | 108 + .../bindings/display/bridge/fsl,ldb.yaml | 105 + .../display/bridge/google,cros-ec-anx7688.yaml | 80 + .../display/bridge/ingenic,jz4780-hdmi.yaml | 81 + .../bindings/display/bridge/intel,keembay-dsi.yaml | 93 + .../bindings/display/bridge/ite,it6505.yaml | 94 + .../bindings/display/bridge/ite,it66121.yaml | 127 + .../bindings/display/bridge/lontium,lt8912b.yaml | 103 + .../bindings/display/bridge/lontium,lt9211.yaml | 117 + .../bindings/display/bridge/lontium,lt9611.yaml | 121 + .../bindings/display/bridge/lvds-codec.yaml | 186 + .../bridge/megachips-stdpxxxx-ge-b850v3-fw.txt | 91 + .../bindings/display/bridge/nwl-dsi.yaml | 202 + .../bindings/display/bridge/nxp,ptn3460.yaml | 106 + .../bindings/display/bridge/nxp,tda998x.yaml | 109 + .../devicetree/bindings/display/bridge/ps8622.txt | 31 + .../devicetree/bindings/display/bridge/ps8640.yaml | 121 + .../display/bridge/renesas,dsi-csi2-tx.yaml | 118 + .../bindings/display/bridge/renesas,dw-hdmi.yaml | 130 + .../bindings/display/bridge/renesas,lvds.yaml | 235 + .../bindings/display/bridge/sil,sii9022.yaml | 131 + .../bindings/display/bridge/sil,sii9234.yaml | 110 + .../bindings/display/bridge/sil-sii8620.txt | 33 + .../bindings/display/bridge/simple-bridge.yaml | 91 + .../bindings/display/bridge/snps,dw-mipi-dsi.yaml | 71 + .../bindings/display/bridge/synopsys,dw-hdmi.yaml | 53 + .../display/bridge/thine,thc63lvd1024.yaml | 115 + .../bindings/display/bridge/ti,dlpc3433.yaml | 117 + .../bindings/display/bridge/ti,sn65dsi83.yaml | 162 + .../bindings/display/bridge/ti,sn65dsi86.yaml | 277 + .../bindings/display/bridge/ti,tfp410.yaml | 119 + .../bindings/display/bridge/toshiba,tc358762.yaml | 84 + .../bindings/display/bridge/toshiba,tc358764.txt | 35 + .../bindings/display/bridge/toshiba,tc358767.yaml | 174 + .../bindings/display/bridge/toshiba,tc358768.yaml | 127 + .../bindings/display/bridge/toshiba,tc358775.yaml | 206 + .../bindings/display/cirrus,clps711x-fb.txt | 47 + .../display/connector/analog-tv-connector.yaml | 53 + .../bindings/display/connector/dp-connector.yaml | 55 + .../bindings/display/connector/dvi-connector.yaml | 71 + .../bindings/display/connector/hdmi-connector.yaml | 65 + .../bindings/display/connector/vga-connector.yaml | 47 + .../devicetree/bindings/display/dp-aux-bus.yaml | 37 + .../bindings/display/dsi-controller.yaml | 93 + .../bindings/display/exynos/exynos_dp.txt | 112 + .../bindings/display/exynos/exynos_dsim.txt | 90 + .../bindings/display/faraday,tve200.yaml | 68 + .../devicetree/bindings/display/fsl,dcu.txt | 34 + .../devicetree/bindings/display/fsl,lcdif.yaml | 112 + .../devicetree/bindings/display/fsl,tcon.txt | 17 + .../bindings/display/google,goldfish-fb.txt | 17 + .../devicetree/bindings/display/himax,hx8357d.txt | 26 + .../bindings/display/hisilicon/dw-dsi.txt | 72 + .../bindings/display/hisilicon/hisi-ade.txt | 64 + .../devicetree/bindings/display/ilitek,ili9225.txt | 25 + .../bindings/display/ilitek,ili9486.yaml | 73 + .../devicetree/bindings/display/imx/fsl,imx-fb.txt | 57 + .../bindings/display/imx/fsl,imx6-hdmi.yaml | 126 + .../bindings/display/imx/fsl-imx-drm.txt | 162 + .../devicetree/bindings/display/imx/ldb.txt | 147 + .../bindings/display/imx/nxp,imx8mq-dcss.yaml | 107 + .../devicetree/bindings/display/ingenic,ipu.yaml | 64 + .../devicetree/bindings/display/ingenic,lcd.yaml | 128 + .../bindings/display/intel,keembay-display.yaml | 72 + .../bindings/display/intel,keembay-msscam.yaml | 43 + .../devicetree/bindings/display/lvds.yaml | 90 + .../bindings/display/marvell,pxa2xx-lcdc.txt | 36 + .../bindings/display/marvell,pxa300-gcu.txt | 17 + .../bindings/display/mediatek/mediatek,aal.yaml | 89 + .../bindings/display/mediatek/mediatek,ccorr.yaml | 88 + .../bindings/display/mediatek/mediatek,cec.yaml | 52 + .../bindings/display/mediatek/mediatek,color.yaml | 94 + .../bindings/display/mediatek/mediatek,dither.yaml | 85 + .../bindings/display/mediatek/mediatek,dp.yaml | 116 + .../bindings/display/mediatek/mediatek,dpi.yaml | 95 + .../bindings/display/mediatek/mediatek,dsc.yaml | 80 + .../bindings/display/mediatek/mediatek,dsi.yaml | 116 + .../bindings/display/mediatek/mediatek,gamma.yaml | 86 + .../display/mediatek/mediatek,hdmi-ddc.yaml | 58 + .../bindings/display/mediatek/mediatek,hdmi.yaml | 136 + .../display/mediatek/mediatek,mdp-rdma.yaml | 88 + .../bindings/display/mediatek/mediatek,merge.yaml | 104 + .../bindings/display/mediatek/mediatek,od.yaml | 59 + .../bindings/display/mediatek/mediatek,ovl-2l.yaml | 92 + .../bindings/display/mediatek/mediatek,ovl.yaml | 105 + .../display/mediatek/mediatek,postmask.yaml | 82 + .../bindings/display/mediatek/mediatek,rdma.yaml | 116 + .../bindings/display/mediatek/mediatek,split.yaml | 65 + .../bindings/display/mediatek/mediatek,ufoe.yaml | 68 + .../bindings/display/mediatek/mediatek,wdma.yaml | 86 + .../devicetree/bindings/display/mipi-dsi-bus.txt | 235 + .../bindings/display/msm/dp-controller.yaml | 200 + .../bindings/display/msm/dpu-msm8998.yaml | 223 + .../bindings/display/msm/dpu-qcm2290.yaml | 222 + .../bindings/display/msm/dpu-sc7180.yaml | 235 + .../bindings/display/msm/dpu-sc7280.yaml | 239 + .../bindings/display/msm/dpu-sdm845.yaml | 217 + .../bindings/display/msm/dsi-controller-main.yaml | 213 + .../bindings/display/msm/dsi-phy-10nm.yaml | 101 + .../bindings/display/msm/dsi-phy-14nm.yaml | 66 + .../bindings/display/msm/dsi-phy-20nm.yaml | 70 + .../bindings/display/msm/dsi-phy-28nm.yaml | 72 + .../bindings/display/msm/dsi-phy-7nm.yaml | 72 + .../bindings/display/msm/dsi-phy-common.yaml | 40 + .../devicetree/bindings/display/msm/gmu.yaml | 251 + .../devicetree/bindings/display/msm/gpu.yaml | 292 + .../devicetree/bindings/display/msm/hdmi.yaml | 232 + .../devicetree/bindings/display/msm/mdp4.yaml | 124 + .../devicetree/bindings/display/msm/mdp5.txt | 160 + .../bindings/display/multi-inno,mi0283qt.txt | 27 + .../bindings/display/panel/abt,y030xx067a.yaml | 59 + .../display/panel/advantech,idk-1110wr.yaml | 84 + .../display/panel/advantech,idk-2121wr.yaml | 121 + .../bindings/display/panel/arm,rtsm-display.yaml | 27 + .../display/panel/arm,versatile-tft-panel.yaml | 51 + .../display/panel/armadeus,st0700-adapt.yaml | 33 + .../display/panel/asus,z00t-tm5p5-nt35596.yaml | 56 + .../display/panel/bananapi,s070wv20-ct16.yaml | 31 + .../bindings/display/panel/boe,bf060y8m-aj0.yaml | 81 + .../bindings/display/panel/boe,himax8279d.yaml | 59 + .../bindings/display/panel/boe,tv101wum-nl6.yaml | 88 + .../bindings/display/panel/display-timing.txt | 1 + .../bindings/display/panel/display-timings.yaml | 76 + .../bindings/display/panel/dlc,dlc0700yzg-1.yaml | 31 + .../bindings/display/panel/ebbg,ft8719.yaml | 74 + .../bindings/display/panel/elida,kd35t133.yaml | 49 + .../display/panel/feixin,k101-im2ba02.yaml | 55 + .../display/panel/feiyang,fy07024di26a30d.yaml | 57 + .../bindings/display/panel/ilitek,ili9163.yaml | 69 + .../bindings/display/panel/ilitek,ili9322.yaml | 68 + .../bindings/display/panel/ilitek,ili9341.yaml | 98 + .../bindings/display/panel/ilitek,ili9881c.yaml | 54 + .../display/panel/innolux,ee101ia-01d.yaml | 50 + .../bindings/display/panel/innolux,ej030na.yaml | 59 + .../bindings/display/panel/innolux,p097pfg.yaml | 56 + .../display/panel/innolux,p120zdg-bf1.yaml | 43 + .../bindings/display/panel/jdi,lt070me05000.yaml | 72 + .../display/panel/kingdisplay,kd035g6-54nt.yaml | 63 + .../display/panel/leadtek,ltk035c5444t.yaml | 61 + .../display/panel/leadtek,ltk050h3146w.yaml | 51 + .../display/panel/leadtek,ltk500hd1829.yaml | 50 + .../bindings/display/panel/lg,lg4573.yaml | 45 + .../bindings/display/panel/lgphilips,lb035q02.yaml | 59 + .../bindings/display/panel/logicpd,type28.yaml | 42 + .../display/panel/mantix,mlaf057we51-x.yaml | 76 + .../display/panel/mitsubishi,aa104xd12.yaml | 90 + .../display/panel/mitsubishi,aa121td01.yaml | 89 + .../bindings/display/panel/nec,nl8048hl11.yaml | 62 + .../bindings/display/panel/novatek,nt35510.yaml | 56 + .../bindings/display/panel/novatek,nt35950.yaml | 106 + .../bindings/display/panel/novatek,nt36672a.yaml | 88 + .../display/panel/olimex,lcd-olinuxino.yaml | 70 + .../bindings/display/panel/orisetech,otm8009a.yaml | 52 + .../bindings/display/panel/panel-common.yaml | 159 + .../bindings/display/panel/panel-dpi.yaml | 71 + .../bindings/display/panel/panel-dsi-cm.yaml | 86 + .../bindings/display/panel/panel-edp.yaml | 188 + .../bindings/display/panel/panel-lvds.yaml | 57 + .../bindings/display/panel/panel-mipi-dbi-spi.yaml | 128 + .../bindings/display/panel/panel-simple-dsi.yaml | 94 + .../bindings/display/panel/panel-simple.yaml | 370 + .../bindings/display/panel/panel-timing.yaml | 214 + .../bindings/display/panel/pda,91-00156-a0.yaml | 31 + .../panel/raspberrypi,7inch-touchscreen.yaml | 71 + .../bindings/display/panel/raydium,rm67191.yaml | 77 + .../bindings/display/panel/raydium,rm68200.yaml | 56 + .../display/panel/rocktech,jh057n00900.yaml | 69 + .../bindings/display/panel/ronbo,rb070d30.yaml | 51 + .../display/panel/samsung,amoled-mipi-dsi.yaml | 75 + .../bindings/display/panel/samsung,ld9040.yaml | 105 + .../bindings/display/panel/samsung,lms380kf01.yaml | 99 + .../bindings/display/panel/samsung,lms397kf04.yaml | 88 + .../bindings/display/panel/samsung,s6d16d0.yaml | 56 + .../bindings/display/panel/samsung,s6d27a1.yaml | 98 + .../bindings/display/panel/samsung,s6e63m0.yaml | 67 + .../display/panel/samsung,s6e88a0-ams452ef01.yaml | 50 + .../bindings/display/panel/samsung,s6e8aa0.yaml | 101 + .../bindings/display/panel/seiko,43wvf1g.yaml | 50 + .../bindings/display/panel/sgd,gktw70sdae4se.yaml | 83 + .../bindings/display/panel/sharp,ld-d5116z01b.yaml | 30 + .../bindings/display/panel/sharp,lq101r1sx01.yaml | 92 + .../bindings/display/panel/sharp,lq150x1lg11.yaml | 58 + .../bindings/display/panel/sharp,ls037v7dw01.yaml | 68 + .../bindings/display/panel/sharp,ls043t1le01.yaml | 51 + .../bindings/display/panel/sharp,ls060t1sx01.yaml | 56 + .../bindings/display/panel/sitronix,st7701.yaml | 73 + .../bindings/display/panel/sitronix,st7789v.yaml | 63 + .../bindings/display/panel/sony,acx424akp.yaml | 56 + .../bindings/display/panel/sony,acx565akm.yaml | 54 + .../display/panel/sony,tulip-truly-nt35521.yaml | 72 + .../display/panel/startek,startek-kd050c.yaml | 33 + .../display/panel/tfc,s9700rtwv43tr-01b.yaml | 33 + .../bindings/display/panel/ti,nspire.yaml | 36 + .../devicetree/bindings/display/panel/tpo,td.yaml | 65 + .../bindings/display/panel/tpo,tpg110.yaml | 103 + .../bindings/display/panel/visionox,rm69299.yaml | 57 + .../bindings/display/panel/xinpeng,xpp055c272.yaml | 50 + .../devicetree/bindings/display/renesas,cmm.yaml | 67 + .../devicetree/bindings/display/renesas,du.yaml | 865 ++ .../devicetree/bindings/display/repaper.txt | 52 + .../display/rockchip/analogix_dp-rockchip.txt | 98 + .../bindings/display/rockchip/cdn-dp-rockchip.txt | 74 + .../display/rockchip/dw_mipi_dsi_rockchip.txt | 94 + .../display/rockchip/inno_hdmi-rockchip.txt | 49 + .../display/rockchip/rockchip,dw-hdmi.yaml | 166 + .../display/rockchip/rockchip,rk3066-hdmi.yaml | 122 + .../bindings/display/rockchip/rockchip-drm.yaml | 42 + .../bindings/display/rockchip/rockchip-lvds.txt | 92 + .../bindings/display/rockchip/rockchip-vop.yaml | 131 + .../bindings/display/rockchip/rockchip-vop2.yaml | 146 + .../display/samsung/samsung,exynos-hdmi-ddc.yaml | 41 + .../display/samsung/samsung,exynos-hdmi.yaml | 226 + .../display/samsung/samsung,exynos-mixer.yaml | 142 + .../display/samsung/samsung,exynos5433-decon.yaml | 145 + .../display/samsung/samsung,exynos5433-mic.yaml | 93 + .../display/samsung/samsung,exynos7-decon.yaml | 119 + .../bindings/display/samsung/samsung,fimd.yaml | 197 + .../bindings/display/simple-framebuffer.yaml | 197 + .../bindings/display/sitronix,st7586.txt | 22 + .../bindings/display/sitronix,st7735r.yaml | 77 + .../devicetree/bindings/display/sm501fb.txt | 32 + .../devicetree/bindings/display/snps,arcpgu.txt | 35 + .../bindings/display/solomon,ssd1307fb.yaml | 277 + .../display/sprd/sprd,display-subsystem.yaml | 65 + .../bindings/display/sprd/sprd,sharkl3-dpu.yaml | 77 + .../display/sprd/sprd,sharkl3-dsi-host.yaml | 88 + .../devicetree/bindings/display/ssd1289fb.txt | 13 + .../devicetree/bindings/display/st,stih4xx.txt | 241 + .../devicetree/bindings/display/st,stm32-dsi.yaml | 138 + .../devicetree/bindings/display/st,stm32-ltdc.yaml | 77 + .../devicetree/bindings/display/ste,mcde.yaml | 168 + .../display/tegra/nvidia,tegra114-mipi.yaml | 74 + .../display/tegra/nvidia,tegra124-dpaux.yaml | 152 + .../display/tegra/nvidia,tegra124-sor.yaml | 197 + .../display/tegra/nvidia,tegra124-vic.yaml | 72 + .../bindings/display/tegra/nvidia,tegra186-dc.yaml | 85 + .../display/tegra/nvidia,tegra186-display.yaml | 310 + .../display/tegra/nvidia,tegra186-dsi-padctl.yaml | 45 + .../bindings/display/tegra/nvidia,tegra20-dc.yaml | 183 + .../bindings/display/tegra/nvidia,tegra20-dsi.yaml | 159 + .../bindings/display/tegra/nvidia,tegra20-epp.yaml | 70 + .../display/tegra/nvidia,tegra20-gr2d.yaml | 74 + .../display/tegra/nvidia,tegra20-gr3d.yaml | 214 + .../display/tegra/nvidia,tegra20-hdmi.yaml | 126 + .../display/tegra/nvidia,tegra20-host1x.yaml | 431 + .../bindings/display/tegra/nvidia,tegra20-isp.yaml | 67 + .../bindings/display/tegra/nvidia,tegra20-mpe.yaml | 71 + .../bindings/display/tegra/nvidia,tegra20-tvo.yaml | 58 + .../bindings/display/tegra/nvidia,tegra20-vi.yaml | 163 + .../display/tegra/nvidia,tegra210-csi.yaml | 52 + .../bindings/display/ti/ti,am65x-dss.yaml | 150 + .../devicetree/bindings/display/ti/ti,dra7-dss.txt | 74 + .../bindings/display/ti/ti,j721e-dss.yaml | 208 + .../devicetree/bindings/display/ti/ti,k2g-dss.yaml | 105 + .../devicetree/bindings/display/ti/ti,omap-dss.txt | 211 + .../bindings/display/ti/ti,omap2-dss.txt | 58 + .../bindings/display/ti/ti,omap3-dss.txt | 87 + .../bindings/display/ti/ti,omap4-dss.txt | 119 + .../bindings/display/ti/ti,omap5-dss.txt | 100 + .../devicetree/bindings/display/ti/ti,opa362.txt | 38 + .../bindings/display/ti/ti,tpd12s015.txt | 44 + .../devicetree/bindings/display/tilcdc/panel.txt | 66 + .../devicetree/bindings/display/tilcdc/tilcdc.txt | 82 + .../devicetree/bindings/display/truly,nt35597.txt | 59 + .../devicetree/bindings/display/via,vt8500-fb.txt | 36 + .../bindings/display/wm,prizm-ge-rops.txt | 13 + .../devicetree/bindings/display/wm,wm8505-fb.txt | 33 + .../bindings/display/xlnx/xlnx,zynqmp-dpsub.yaml | 169 + .../bindings/display/xylon,logicvc-display.yaml | 301 + .../devicetree/bindings/dma/adi,axi-dmac.txt | 61 + .../bindings/dma/allwinner,sun4i-a10-dma.yaml | 55 + .../bindings/dma/allwinner,sun50i-a64-dma.yaml | 95 + .../bindings/dma/allwinner,sun6i-a31-dma.yaml | 62 + .../devicetree/bindings/dma/altr,msgdma.yaml | 63 + .../devicetree/bindings/dma/apm-xgene-dma.txt | 47 + .../devicetree/bindings/dma/apple,admac.yaml | 87 + .../devicetree/bindings/dma/arm,pl330.yaml | 92 + .../devicetree/bindings/dma/arm-pl08x.yaml | 140 + .../devicetree/bindings/dma/atmel-dma.txt | 42 + .../devicetree/bindings/dma/atmel-xdma.txt | 53 + .../devicetree/bindings/dma/brcm,bcm2835-dma.txt | 83 + .../devicetree/bindings/dma/brcm,iproc-sba.txt | 29 + .../devicetree/bindings/dma/dma-common.yaml | 53 + .../devicetree/bindings/dma/dma-controller.yaml | 37 + .../devicetree/bindings/dma/dma-router.yaml | 54 + Documentation/devicetree/bindings/dma/dma.txt | 1 + .../devicetree/bindings/dma/fsl,edma.yaml | 155 + .../devicetree/bindings/dma/fsl-imx-dma.txt | 50 + .../devicetree/bindings/dma/fsl-imx-sdma.txt | 118 + .../devicetree/bindings/dma/fsl-mxs-dma.txt | 60 + Documentation/devicetree/bindings/dma/fsl-qdma.txt | 58 + .../devicetree/bindings/dma/img-mdc-dma.txt | 57 + .../devicetree/bindings/dma/ingenic,dma.yaml | 98 + .../devicetree/bindings/dma/intel,ldma.yaml | 116 + Documentation/devicetree/bindings/dma/k3dma.txt | 47 + .../devicetree/bindings/dma/lpc1850-dmamux.txt | 54 + .../devicetree/bindings/dma/mediatek,uart-dma.yaml | 124 + .../bindings/dma/milbeaut-m10v-hdmac.txt | 32 + .../bindings/dma/milbeaut-m10v-xdmac.txt | 24 + Documentation/devicetree/bindings/dma/mmp-dma.txt | 81 + .../devicetree/bindings/dma/moxa,moxart-dma.txt | 45 + .../devicetree/bindings/dma/mpc512x-dma.txt | 29 + .../devicetree/bindings/dma/mtk-hsdma.txt | 33 + .../devicetree/bindings/dma/mv-xor-v2.txt | 28 + Documentation/devicetree/bindings/dma/mv-xor.txt | 40 + .../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 112 + .../bindings/dma/nvidia,tegra20-apbdma.txt | 44 + .../bindings/dma/nvidia,tegra210-adma.yaml | 101 + Documentation/devicetree/bindings/dma/owl-dma.yaml | 80 + .../devicetree/bindings/dma/qcom,adm.yaml | 99 + .../devicetree/bindings/dma/qcom,bam-dma.yaml | 100 + .../devicetree/bindings/dma/qcom,gpi.yaml | 95 + .../devicetree/bindings/dma/qcom_hidma_mgmt.txt | 95 + .../devicetree/bindings/dma/renesas,nbpfaxi.txt | 69 + .../devicetree/bindings/dma/renesas,rcar-dmac.yaml | 174 + .../devicetree/bindings/dma/renesas,rz-dmac.yaml | 132 + .../bindings/dma/renesas,rzn1-dmamux.yaml | 51 + .../devicetree/bindings/dma/renesas,usb-dmac.yaml | 104 + .../bindings/dma/sifive,fu540-c000-pdma.yaml | 74 + .../bindings/dma/snps,dma-spear1340.yaml | 185 + .../devicetree/bindings/dma/snps,dw-axi-dmac.yaml | 134 + .../bindings/dma/socionext,uniphier-mio-dmac.yaml | 63 + .../bindings/dma/socionext,uniphier-xdmac.yaml | 62 + Documentation/devicetree/bindings/dma/sprd-dma.txt | 44 + .../devicetree/bindings/dma/st,stm32-dma.yaml | 116 + .../devicetree/bindings/dma/st,stm32-dmamux.yaml | 53 + .../devicetree/bindings/dma/st,stm32-mdma.yaml | 106 + Documentation/devicetree/bindings/dma/st_fdma.txt | 86 + .../devicetree/bindings/dma/stericsson,dma40.yaml | 159 + .../devicetree/bindings/dma/ti-dma-crossbar.txt | 68 + Documentation/devicetree/bindings/dma/ti-edma.txt | 238 + .../devicetree/bindings/dma/ti/k3-bcdma.yaml | 167 + .../devicetree/bindings/dma/ti/k3-pktdma.yaml | 175 + .../devicetree/bindings/dma/ti/k3-udma.yaml | 186 + .../devicetree/bindings/dma/xilinx/xilinx_dma.txt | 128 + .../bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml | 85 + .../bindings/dma/xilinx/xlnx,zynqmp-dpdma.yaml | 68 + Documentation/devicetree/bindings/dsp/fsl,dsp.yaml | 205 + .../bindings/dsp/mediatek,mt8186-dsp.yaml | 91 + .../bindings/dsp/mediatek,mt8195-dsp.yaml | 105 + .../bindings/dvfs/performance-domain.yaml | 79 + .../bindings/edac/amazon,al-mc-edac.yaml | 66 + .../devicetree/bindings/edac/apm-xgene-edac.txt | 112 + .../devicetree/bindings/edac/aspeed-sdram-edac.txt | 28 + .../devicetree/bindings/edac/dmc-520.yaml | 61 + .../devicetree/bindings/edac/socfpga-eccmgr.txt | 383 + Documentation/devicetree/bindings/eeprom/at24.yaml | 202 + Documentation/devicetree/bindings/eeprom/at25.yaml | 146 + .../bindings/eeprom/microchip,93lc46b.yaml | 69 + .../devicetree/bindings/example-schema.yaml | 261 + .../devicetree/bindings/extcon/extcon-max3355.txt | 21 + .../devicetree/bindings/extcon/extcon-palmas.txt | 22 + .../devicetree/bindings/extcon/extcon-ptn5150.yaml | 62 + .../devicetree/bindings/extcon/extcon-rt8973a.txt | 23 + .../devicetree/bindings/extcon/extcon-usb-gpio.txt | 21 + .../bindings/extcon/extcon-usbc-cros-ec.yaml | 54 + .../bindings/extcon/extcon-usbc-tusb320.yaml | 43 + .../devicetree/bindings/extcon/fcs,fsa880.yaml | 52 + .../devicetree/bindings/extcon/maxim,max77843.yaml | 41 + .../bindings/extcon/qcom,pm8941-misc.yaml | 62 + .../bindings/extcon/siliconmitus,sm5502-muic.yaml | 53 + .../devicetree/bindings/extcon/wlf,arizona.yaml | 126 + .../devicetree/bindings/firmware/arm,scmi.yaml | 432 + .../devicetree/bindings/firmware/arm,scpi.yaml | 249 + .../devicetree/bindings/firmware/coreboot.txt | 33 + .../bindings/firmware/cznic,turris-mox-rwtm.txt | 19 + .../devicetree/bindings/firmware/fsl,scu.yaml | 215 + .../intel,ixp4xx-network-processing-engine.yaml | 94 + .../bindings/firmware/intel,stratix10-svc.txt | 57 + .../bindings/firmware/meson/meson_sm.txt | 15 + .../bindings/firmware/nvidia,tegra186-bpmp.yaml | 186 + .../bindings/firmware/nvidia,tegra210-bpmp.txt | 35 + .../devicetree/bindings/firmware/qcom,scm.yaml | 148 + .../bindings/firmware/qemu,fw-cfg-mmio.yaml | 54 + .../firmware/xilinx/xlnx,zynqmp-firmware.yaml | 89 + .../bindings/fpga/altera-fpga2sdram-bridge.txt | 13 + .../bindings/fpga/altera-freeze-bridge.txt | 20 + .../bindings/fpga/altera-hps2fpga-bridge.txt | 36 + .../bindings/fpga/altera-passive-serial.txt | 29 + .../devicetree/bindings/fpga/altera-pr-ip.txt | 12 + .../bindings/fpga/altera-socfpga-a10-fpga-mgr.txt | 19 + .../bindings/fpga/altera-socfpga-fpga-mgr.txt | 17 + .../devicetree/bindings/fpga/fpga-bridge.txt | 13 + .../devicetree/bindings/fpga/fpga-region.txt | 479 ++ .../bindings/fpga/intel-stratix10-soc-fpga-mgr.txt | 18 + .../bindings/fpga/lattice-ice40-fpga-mgr.txt | 21 + .../bindings/fpga/lattice-machxo2-spi.txt | 29 + .../bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml | 45 + .../bindings/fpga/xilinx-pr-decoupler.txt | 54 + .../bindings/fpga/xilinx-slave-serial.txt | 51 + .../bindings/fpga/xilinx-zynq-fpga-mgr.yaml | 52 + .../devicetree/bindings/fpga/xlnx,versal-fpga.yaml | 33 + .../bindings/fpga/xlnx,zynqmp-pcap-fpga.yaml | 36 + .../devicetree/bindings/fsi/fsi-master-aspeed.txt | 36 + .../devicetree/bindings/fsi/fsi-master-ast-cf.txt | 36 + .../devicetree/bindings/fsi/fsi-master-gpio.txt | 28 + Documentation/devicetree/bindings/fsi/fsi.txt | 156 + .../devicetree/bindings/fsi/ibm,fsi2spi.yaml | 38 + .../devicetree/bindings/fsi/ibm,p9-occ.txt | 16 + .../bindings/fuse/nvidia,tegra20-fuse.yaml | 89 + .../devicetree/bindings/gnss/brcm,bcm4751.yaml | 69 + .../devicetree/bindings/gnss/gnss-common.yaml | 55 + .../devicetree/bindings/gnss/mediatek.yaml | 59 + .../devicetree/bindings/gnss/sirfstar.yaml | 76 + .../devicetree/bindings/gnss/u-blox,neo-6m.yaml | 58 + .../devicetree/bindings/goldfish/audio.txt | 17 + .../devicetree/bindings/goldfish/battery.txt | 17 + .../devicetree/bindings/goldfish/events.txt | 17 + .../devicetree/bindings/goldfish/pipe.txt | 17 + Documentation/devicetree/bindings/goldfish/tty.txt | 17 + .../devicetree/bindings/gpio/8xxx_gpio.txt | 72 + .../devicetree/bindings/gpio/abilis,tb10x-gpio.txt | 35 + .../bindings/gpio/airoha,en7523-gpio.yaml | 66 + .../devicetree/bindings/gpio/aspeed,sgpio.yaml | 77 + .../bindings/gpio/brcm,bcm6345-gpio.yaml | 86 + .../bindings/gpio/brcm,brcmstb-gpio.yaml | 104 + .../devicetree/bindings/gpio/brcm,kona-gpio.txt | 52 + .../bindings/gpio/brcm,xgs-iproc-gpio.yaml | 70 + .../bindings/gpio/cavium-octeon-gpio.txt | 49 + .../devicetree/bindings/gpio/cdns,gpio.txt | 43 + .../bindings/gpio/cirrus,clps711x-mctrl-gpio.txt | 17 + .../devicetree/bindings/gpio/delta,tn48m-gpio.yaml | 39 + .../bindings/gpio/fairchild,74hc595.yaml | 79 + .../bindings/gpio/faraday,ftgpio010.yaml | 65 + .../bindings/gpio/fsl,imx8qxp-sc-gpio.yaml | 39 + .../devicetree/bindings/gpio/fsl-imx-gpio.yaml | 113 + .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 20 + .../bindings/gpio/gateworks,pld-gpio.txt | 20 + .../devicetree/bindings/gpio/gpio-74xx-mmio.txt | 30 + .../devicetree/bindings/gpio/gpio-adnp.txt | 33 + .../devicetree/bindings/gpio/gpio-altera.txt | 44 + .../devicetree/bindings/gpio/gpio-aspeed.txt | 39 + .../devicetree/bindings/gpio/gpio-ath79.txt | 37 + .../devicetree/bindings/gpio/gpio-clps711x.txt | 28 + .../bindings/gpio/gpio-consumer-common.yaml | 64 + .../devicetree/bindings/gpio/gpio-davinci.yaml | 185 + .../devicetree/bindings/gpio/gpio-dsp-keystone.txt | 39 + .../devicetree/bindings/gpio/gpio-eic-sprd.txt | 97 + .../devicetree/bindings/gpio/gpio-exar.txt | 5 + .../devicetree/bindings/gpio/gpio-grgpio.txt | 26 + .../devicetree/bindings/gpio/gpio-lp3943.txt | 37 + .../devicetree/bindings/gpio/gpio-max3191x.txt | 59 + .../devicetree/bindings/gpio/gpio-max77620.txt | 25 + .../devicetree/bindings/gpio/gpio-mm-lantiq.txt | 38 + .../devicetree/bindings/gpio/gpio-moxtet.txt | 18 + .../devicetree/bindings/gpio/gpio-mpc8xxx.txt | 53 + .../devicetree/bindings/gpio/gpio-mvebu.yaml | 146 + .../devicetree/bindings/gpio/gpio-mxs.yaml | 136 + .../devicetree/bindings/gpio/gpio-nmk.txt | 31 + .../devicetree/bindings/gpio/gpio-palmas.txt | 27 + .../devicetree/bindings/gpio/gpio-pca9570.yaml | 48 + .../devicetree/bindings/gpio/gpio-pca95xx.yaml | 235 + .../devicetree/bindings/gpio/gpio-pisosr.txt | 34 + .../devicetree/bindings/gpio/gpio-rda.yaml | 50 + .../devicetree/bindings/gpio/gpio-sprd.txt | 28 + .../devicetree/bindings/gpio/gpio-stmpe.txt | 17 + .../devicetree/bindings/gpio/gpio-stp-xway.yaml | 99 + .../devicetree/bindings/gpio/gpio-thunderx.txt | 27 + .../devicetree/bindings/gpio/gpio-tpic2810.yaml | 51 + .../devicetree/bindings/gpio/gpio-ts4800.txt | 20 + .../devicetree/bindings/gpio/gpio-ts4900.txt | 30 + .../devicetree/bindings/gpio/gpio-twl4030.txt | 29 + .../devicetree/bindings/gpio/gpio-vf610.yaml | 88 + .../devicetree/bindings/gpio/gpio-virtio.yaml | 59 + .../devicetree/bindings/gpio/gpio-xgene-sb.txt | 64 + .../devicetree/bindings/gpio/gpio-xgene.txt | 22 + .../devicetree/bindings/gpio/gpio-xra1403.txt | 46 + .../devicetree/bindings/gpio/gpio-zevio.txt | 16 + .../devicetree/bindings/gpio/gpio-zynq.yaml | 116 + Documentation/devicetree/bindings/gpio/gpio.txt | 331 + .../devicetree/bindings/gpio/gpio_atmel.txt | 31 + .../devicetree/bindings/gpio/gpio_lpc32xx.txt | 43 + .../devicetree/bindings/gpio/gpio_oxnas.txt | 47 + .../devicetree/bindings/gpio/ibm,ppc4xx-gpio.txt | 24 + .../devicetree/bindings/gpio/idt,32434-gpio.yaml | 67 + .../devicetree/bindings/gpio/intel,ixp4xx-gpio.txt | 38 + .../bindings/gpio/kontron,sl28cpld-gpio.yaml | 54 + .../bindings/gpio/mediatek,mt7621-gpio.yaml | 72 + .../bindings/gpio/microchip,mpfs-gpio.yaml | 97 + .../bindings/gpio/microchip,pic32-gpio.txt | 49 + .../devicetree/bindings/gpio/mrvl-gpio.yaml | 172 + .../bindings/gpio/mstar,msc313-gpio.yaml | 61 + .../devicetree/bindings/gpio/netxbig-gpio-ext.txt | 22 + .../bindings/gpio/ni,169445-nand-gpio.txt | 38 + .../bindings/gpio/nintendo,hollywood-gpio.txt | 26 + .../bindings/gpio/nvidia,tegra186-gpio.yaml | 214 + .../bindings/gpio/nvidia,tegra20-gpio.yaml | 110 + .../devicetree/bindings/gpio/nxp,lpc1850-gpio.txt | 59 + .../devicetree/bindings/gpio/nxp,pcf8575.yaml | 103 + .../devicetree/bindings/gpio/pl061-gpio.yaml | 72 + .../bindings/gpio/qcom,wcd934x-gpio.yaml | 47 + .../bindings/gpio/raspberrypi,firmware-gpio.txt | 30 + .../bindings/gpio/realtek,otto-gpio.yaml | 108 + .../devicetree/bindings/gpio/renesas,em-gio.yaml | 70 + .../bindings/gpio/renesas,rcar-gpio.yaml | 152 + .../bindings/gpio/rockchip,gpio-bank.yaml | 89 + .../bindings/gpio/rockchip,rk3328-grf-gpio.yaml | 50 + .../devicetree/bindings/gpio/sifive,gpio.yaml | 93 + .../devicetree/bindings/gpio/snps,creg-gpio.txt | 21 + .../devicetree/bindings/gpio/snps,dw-apb-gpio.yaml | 139 + .../bindings/gpio/socionext,uniphier-gpio.yaml | 112 + .../devicetree/bindings/gpio/sodaville.txt | 48 + .../devicetree/bindings/gpio/spear_spics.txt | 49 + .../devicetree/bindings/gpio/ti,omap-gpio.yaml | 108 + .../bindings/gpio/toshiba,gpio-visconti.yaml | 69 + .../devicetree/bindings/gpio/wd,mbl-gpio.txt | 38 + .../bindings/gpio/x-powers,axp209-gpio.yaml | 61 + .../devicetree/bindings/gpio/xlnx,gpio-xilinx.yaml | 154 + .../bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml | 43 + .../bindings/gpio/xylon,logicvc-gpio.yaml | 71 + .../devicetree/bindings/gpu/arm,mali-bifrost.yaml | 237 + .../devicetree/bindings/gpu/arm,mali-midgard.yaml | 197 + .../devicetree/bindings/gpu/arm,mali-utgard.yaml | 180 + .../devicetree/bindings/gpu/aspeed-gfx.txt | 41 + .../devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 75 + .../bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml | 106 + .../bindings/gpu/host1x/nvidia,tegra210-nvenc.yaml | 135 + .../bindings/gpu/host1x/nvidia,tegra210-nvjpg.yaml | 94 + .../devicetree/bindings/gpu/nvidia,gk20a.txt | 115 + .../devicetree/bindings/gpu/samsung-g2d.yaml | 75 + .../devicetree/bindings/gpu/samsung-rotator.yaml | 55 + .../devicetree/bindings/gpu/samsung-scaler.yaml | 81 + .../devicetree/bindings/gpu/vivante,gc.yaml | 76 + Documentation/devicetree/bindings/graph.txt | 1 + .../devicetree/bindings/hsi/client-devices.txt | 44 + .../devicetree/bindings/hsi/nokia-modem.txt | 59 + Documentation/devicetree/bindings/hsi/omap-ssi.txt | 102 + .../devicetree/bindings/hwinfo/renesas,prr.yaml | 37 + .../bindings/hwinfo/samsung,exynos-chipid.yaml | 41 + .../bindings/hwinfo/samsung,s5pv210-chipid.yaml | 30 + .../devicetree/bindings/hwinfo/ti,k3-socinfo.yaml | 40 + .../hwlock/allwinner,sun6i-a31-hwspinlock.yaml | 48 + .../devicetree/bindings/hwlock/hwlock.txt | 59 + .../bindings/hwlock/qcom-hwspinlock.yaml | 55 + .../devicetree/bindings/hwlock/sprd-hwspinlock.txt | 23 + .../bindings/hwlock/st,stm32-hwspinlock.yaml | 49 + .../bindings/hwlock/ti,omap-hwspinlock.yaml | 46 + .../devicetree/bindings/hwmon/adc128d818.txt | 38 + .../devicetree/bindings/hwmon/adi,ad741x.yaml | 39 + .../devicetree/bindings/hwmon/adi,adm1177.yaml | 67 + .../devicetree/bindings/hwmon/adi,adm1266.yaml | 51 + .../devicetree/bindings/hwmon/adi,adm1275.yaml | 125 + .../bindings/hwmon/adi,axi-fan-control.yaml | 63 + .../devicetree/bindings/hwmon/adi,ltc2947.yaml | 101 + .../devicetree/bindings/hwmon/adi,ltc2992.yaml | 80 + .../devicetree/bindings/hwmon/adi,max31760.yaml | 42 + .../devicetree/bindings/hwmon/adt7475.yaml | 105 + .../devicetree/bindings/hwmon/amd,sbrmi.yaml | 53 + .../devicetree/bindings/hwmon/amd,sbtsi.yaml | 54 + .../devicetree/bindings/hwmon/apm-xgene-hwmon.txt | 14 + Documentation/devicetree/bindings/hwmon/as370.txt | 11 + .../devicetree/bindings/hwmon/aspeed-pwm-tacho.txt | 73 + .../devicetree/bindings/hwmon/baikal,bt1-pvt.yaml | 105 + .../bindings/hwmon/cirrus,lochnagar.yaml | 35 + Documentation/devicetree/bindings/hwmon/g762.txt | 47 + .../devicetree/bindings/hwmon/gpio-fan.txt | 41 + .../devicetree/bindings/hwmon/ibm,occ-hwmon.yaml | 39 + .../devicetree/bindings/hwmon/ibm,p8-occ-hwmon.txt | 25 + .../devicetree/bindings/hwmon/ibmpowernv.txt | 23 + .../devicetree/bindings/hwmon/iio-hwmon.yaml | 37 + .../devicetree/bindings/hwmon/ina3221.txt | 54 + .../devicetree/bindings/hwmon/jedec,jc42.yaml | 78 + .../bindings/hwmon/kontron,sl28cpld-hwmon.yaml | 27 + .../devicetree/bindings/hwmon/lltc,ltc4151.yaml | 41 + Documentation/devicetree/bindings/hwmon/lm75.yaml | 68 + Documentation/devicetree/bindings/hwmon/lm87.txt | 30 + .../devicetree/bindings/hwmon/ltc2978.txt | 62 + .../devicetree/bindings/hwmon/ltc2990.txt | 36 + .../devicetree/bindings/hwmon/ltq-cputemp.txt | 10 + .../devicetree/bindings/hwmon/max31785.txt | 22 + .../devicetree/bindings/hwmon/max6650.txt | 28 + .../devicetree/bindings/hwmon/max6697.txt | 64 + .../devicetree/bindings/hwmon/maxim,max20730.yaml | 65 + .../bindings/hwmon/microchip,lan966x.yaml | 53 + .../bindings/hwmon/microchip,mcp3021.yaml | 43 + .../bindings/hwmon/microchip,sparx5-temp.yaml | 44 + .../devicetree/bindings/hwmon/moortec,mr75203.yaml | 164 + .../devicetree/bindings/hwmon/national,lm90.yaml | 227 + .../devicetree/bindings/hwmon/npcm750-pwm-fan.txt | 84 + .../devicetree/bindings/hwmon/nsa320-mcu.txt | 20 + .../devicetree/bindings/hwmon/ntc-thermistor.yaml | 142 + .../devicetree/bindings/hwmon/nuvoton,nct6775.yaml | 57 + .../devicetree/bindings/hwmon/nuvoton,nct7802.yaml | 145 + .../bindings/hwmon/pmbus/ti,lm25066.yaml | 54 + .../bindings/hwmon/pmbus/ti,ucd90320.yaml | 47 + .../devicetree/bindings/hwmon/pwm-fan.txt | 67 + .../devicetree/bindings/hwmon/sensirion,sht15.yaml | 43 + .../devicetree/bindings/hwmon/sensirion,shtc1.yaml | 61 + .../devicetree/bindings/hwmon/stts751.txt | 15 + .../devicetree/bindings/hwmon/ti,ads7828.yaml | 57 + .../devicetree/bindings/hwmon/ti,ina2xx.yaml | 77 + .../devicetree/bindings/hwmon/ti,tmp102.yaml | 47 + .../devicetree/bindings/hwmon/ti,tmp108.yaml | 50 + .../devicetree/bindings/hwmon/ti,tmp401.yaml | 104 + .../devicetree/bindings/hwmon/ti,tmp421.yaml | 109 + .../devicetree/bindings/hwmon/ti,tmp464.yaml | 113 + .../devicetree/bindings/hwmon/ti,tmp513.yaml | 91 + .../devicetree/bindings/hwmon/ti,tps23861.yaml | 51 + .../devicetree/bindings/hwmon/vexpress.txt | 23 + .../devicetree/bindings/hwmon/winbond,w83781d.yaml | 41 + .../bindings/i2c/allwinner,sun6i-a31-p2wi.yaml | 63 + .../bindings/i2c/amlogic,meson6-i2c.yaml | 55 + .../devicetree/bindings/i2c/apple,i2c.yaml | 66 + .../devicetree/bindings/i2c/arm,i2c-versatile.yaml | 29 + .../devicetree/bindings/i2c/aspeed,i2c.yaml | 73 + .../devicetree/bindings/i2c/atmel,at91sam-i2c.yaml | 146 + .../devicetree/bindings/i2c/brcm,bcm2835-i2c.yaml | 54 + .../devicetree/bindings/i2c/brcm,brcmstb-i2c.yaml | 96 + .../devicetree/bindings/i2c/brcm,iproc-i2c.yaml | 71 + .../devicetree/bindings/i2c/brcm,kona-i2c.txt | 35 + .../devicetree/bindings/i2c/cdns,i2c-r1p10.yaml | 60 + .../bindings/i2c/google,cros-ec-i2c-tunnel.yaml | 65 + .../devicetree/bindings/i2c/i2c-altera.txt | 39 + .../bindings/i2c/i2c-arb-gpio-challenge.txt | 82 + Documentation/devicetree/bindings/i2c/i2c-arb.txt | 35 + .../devicetree/bindings/i2c/i2c-axxia.txt | 30 + .../devicetree/bindings/i2c/i2c-cbus-gpio.txt | 27 + .../devicetree/bindings/i2c/i2c-davinci.txt | 43 + .../devicetree/bindings/i2c/i2c-demux-pinctrl.txt | 135 + .../devicetree/bindings/i2c/i2c-digicolor.txt | 25 + .../devicetree/bindings/i2c/i2c-exynos5.yaml | 133 + Documentation/devicetree/bindings/i2c/i2c-fsi.txt | 40 + .../devicetree/bindings/i2c/i2c-gate.yaml | 38 + .../devicetree/bindings/i2c/i2c-gpio.yaml | 73 + .../devicetree/bindings/i2c/i2c-hix5hd2.txt | 24 + .../devicetree/bindings/i2c/i2c-img-scb.txt | 26 + .../devicetree/bindings/i2c/i2c-imx-lpi2c.yaml | 81 + Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 123 + .../devicetree/bindings/i2c/i2c-iop3xx.txt | 20 + .../devicetree/bindings/i2c/i2c-lpc2k.txt | 33 + Documentation/devicetree/bindings/i2c/i2c-mpc.yaml | 100 + .../devicetree/bindings/i2c/i2c-mt65xx.yaml | 119 + .../devicetree/bindings/i2c/i2c-mux-gpio.yaml | 104 + .../devicetree/bindings/i2c/i2c-mux-gpmux.yaml | 123 + .../devicetree/bindings/i2c/i2c-mux-ltc4306.txt | 61 + .../devicetree/bindings/i2c/i2c-mux-pca954x.yaml | 110 + .../devicetree/bindings/i2c/i2c-mux-pinctrl.yaml | 103 + .../devicetree/bindings/i2c/i2c-mux-reg.txt | 74 + Documentation/devicetree/bindings/i2c/i2c-mux.yaml | 87 + Documentation/devicetree/bindings/i2c/i2c-mxs.yaml | 51 + .../devicetree/bindings/i2c/i2c-octeon.txt | 40 + Documentation/devicetree/bindings/i2c/i2c-opal.txt | 37 + Documentation/devicetree/bindings/i2c/i2c-owl.yaml | 62 + .../devicetree/bindings/i2c/i2c-pca-platform.txt | 27 + Documentation/devicetree/bindings/i2c/i2c-pnx.txt | 34 + .../devicetree/bindings/i2c/i2c-pxa-pci-ce4100.txt | 93 + Documentation/devicetree/bindings/i2c/i2c-pxa.yaml | 74 + .../devicetree/bindings/i2c/i2c-rk3x.yaml | 142 + Documentation/devicetree/bindings/i2c/i2c-sprd.txt | 31 + Documentation/devicetree/bindings/i2c/i2c-st.txt | 41 + .../devicetree/bindings/i2c/i2c-synquacer.txt | 29 + .../devicetree/bindings/i2c/i2c-virtio.yaml | 51 + Documentation/devicetree/bindings/i2c/i2c-wmt.txt | 24 + .../devicetree/bindings/i2c/i2c-xgene-slimpro.txt | 15 + Documentation/devicetree/bindings/i2c/i2c.txt | 151 + .../devicetree/bindings/i2c/ingenic,i2c.yaml | 90 + .../bindings/i2c/marvell,mv64xxx-i2c.yaml | 140 + .../bindings/i2c/mediatek,mt7621-i2c.yaml | 61 + .../devicetree/bindings/i2c/microchip,corei2c.yaml | 56 + .../bindings/i2c/nuvoton,npcm7xx-i2c.yaml | 77 + .../bindings/i2c/nvidia,tegra186-bpmp-i2c.yaml | 45 + .../bindings/i2c/nvidia,tegra20-i2c.yaml | 192 + .../devicetree/bindings/i2c/nxp,pca9541.txt | 29 + .../bindings/i2c/opencores,i2c-ocores.yaml | 113 + .../devicetree/bindings/i2c/qcom,i2c-cci.yaml | 262 + .../bindings/i2c/qcom,i2c-geni-qcom.yaml | 100 + .../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 89 + .../devicetree/bindings/i2c/renesas,iic-emev2.yaml | 54 + .../devicetree/bindings/i2c/renesas,rcar-i2c.yaml | 165 + .../devicetree/bindings/i2c/renesas,riic.yaml | 114 + .../bindings/i2c/renesas,rmobile-iic.yaml | 149 + .../devicetree/bindings/i2c/renesas,rzv2m.yaml | 80 + .../bindings/i2c/samsung,s3c2410-i2c.yaml | 164 + .../bindings/i2c/snps,designware-i2c.yaml | 145 + .../bindings/i2c/socionext,uniphier-fi2c.yaml | 52 + .../bindings/i2c/socionext,uniphier-i2c.yaml | 52 + .../devicetree/bindings/i2c/st,nomadik-i2c.yaml | 115 + .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 161 + .../devicetree/bindings/i2c/ti,omap4-i2c.yaml | 102 + .../bindings/i2c/xlnx,xps-iic-2.00.a.yaml | 51 + .../devicetree/bindings/i3c/cdns,i3c-master.yaml | 60 + Documentation/devicetree/bindings/i3c/i3c.yaml | 180 + .../devicetree/bindings/i3c/mipi-i3c-hci.yaml | 52 + .../bindings/i3c/silvaco,i3c-master.yaml | 60 + .../bindings/i3c/snps,dw-i3c-master.yaml | 52 + .../bindings/iio/accel/adi,adis16201.yaml | 56 + .../bindings/iio/accel/adi,adis16240.yaml | 54 + .../devicetree/bindings/iio/accel/adi,adxl313.yaml | 91 + .../devicetree/bindings/iio/accel/adi,adxl345.yaml | 81 + .../devicetree/bindings/iio/accel/adi,adxl355.yaml | 89 + .../devicetree/bindings/iio/accel/adi,adxl367.yaml | 80 + .../devicetree/bindings/iio/accel/adi,adxl372.yaml | 68 + .../bindings/iio/accel/bosch,bma220.yaml | 51 + .../bindings/iio/accel/bosch,bma255.yaml | 120 + .../bindings/iio/accel/bosch,bma400.yaml | 56 + .../bindings/iio/accel/bosch,bmi088.yaml | 71 + .../devicetree/bindings/iio/accel/fsl,mma7455.yaml | 82 + .../devicetree/bindings/iio/accel/fsl,mma8452.yaml | 65 + .../bindings/iio/accel/kionix,kxcjk1013.yaml | 53 + .../bindings/iio/accel/kionix,kxsd9.yaml | 70 + .../devicetree/bindings/iio/accel/lis302.txt | 119 + .../bindings/iio/accel/memsensing,msa311.yaml | 53 + .../bindings/iio/accel/murata,sca3300.yaml | 48 + .../bindings/iio/accel/nxp,fxls8962af.yaml | 81 + Documentation/devicetree/bindings/iio/adc/adc.yaml | 54 + .../devicetree/bindings/iio/adc/adi,ad7091r5.yaml | 54 + .../devicetree/bindings/iio/adc/adi,ad7124.yaml | 157 + .../devicetree/bindings/iio/adc/adi,ad7192.yaml | 124 + .../devicetree/bindings/iio/adc/adi,ad7280a.yaml | 78 + .../devicetree/bindings/iio/adc/adi,ad7291.yaml | 46 + .../devicetree/bindings/iio/adc/adi,ad7292.yaml | 110 + .../devicetree/bindings/iio/adc/adi,ad7298.yaml | 50 + .../devicetree/bindings/iio/adc/adi,ad7476.yaml | 175 + .../devicetree/bindings/iio/adc/adi,ad7606.yaml | 141 + .../devicetree/bindings/iio/adc/adi,ad7768-1.yaml | 125 + .../devicetree/bindings/iio/adc/adi,ad7780.yaml | 88 + .../devicetree/bindings/iio/adc/adi,ad7923.yaml | 73 + .../devicetree/bindings/iio/adc/adi,ad7949.yaml | 103 + .../devicetree/bindings/iio/adc/adi,ad799x.yaml | 73 + .../devicetree/bindings/iio/adc/adi,ad9467.yaml | 73 + .../devicetree/bindings/iio/adc/adi,axi-adc.yaml | 61 + .../bindings/iio/adc/allwinner,sun8i-a33-ths.yaml | 43 + .../bindings/iio/adc/amlogic,meson-saradc.yaml | 148 + .../bindings/iio/adc/aspeed,ast2400-adc.yaml | 56 + .../bindings/iio/adc/aspeed,ast2600-adc.yaml | 93 + .../bindings/iio/adc/atmel,sama5d2-adc.yaml | 100 + .../bindings/iio/adc/atmel,sama9260-adc.yaml | 121 + .../devicetree/bindings/iio/adc/avia-hx711.yaml | 67 + .../bindings/iio/adc/brcm,iproc-static-adc.yaml | 65 + .../bindings/iio/adc/cosmic,10001-adc.yaml | 59 + .../bindings/iio/adc/dlg,da9150-gpadc.yaml | 35 + .../bindings/iio/adc/envelope-detector.yaml | 86 + .../devicetree/bindings/iio/adc/fsl,imx25-gcq.yaml | 131 + .../devicetree/bindings/iio/adc/fsl,imx7d-adc.yaml | 62 + .../devicetree/bindings/iio/adc/fsl,vf610-adc.yaml | 88 + .../devicetree/bindings/iio/adc/holt,hi8435.yaml | 51 + .../devicetree/bindings/iio/adc/ingenic,adc.yaml | 91 + .../devicetree/bindings/iio/adc/lltc,ltc2496.yaml | 47 + .../devicetree/bindings/iio/adc/lltc,ltc2497.yaml | 50 + .../bindings/iio/adc/marvell,berlin2-adc.yaml | 50 + .../devicetree/bindings/iio/adc/maxim,max1027.yaml | 68 + .../bindings/iio/adc/maxim,max11100.yaml | 52 + .../devicetree/bindings/iio/adc/maxim,max1118.yaml | 64 + .../bindings/iio/adc/maxim,max11205.yaml | 69 + .../devicetree/bindings/iio/adc/maxim,max1238.yaml | 78 + .../devicetree/bindings/iio/adc/maxim,max1241.yaml | 68 + .../devicetree/bindings/iio/adc/maxim,max1363.yaml | 52 + .../devicetree/bindings/iio/adc/maxim,max9611.yaml | 50 + .../bindings/iio/adc/mediatek,mt2701-auxadc.yaml | 80 + .../bindings/iio/adc/mediatek,mt6360-adc.yaml | 31 + .../bindings/iio/adc/microchip,mcp3201.yaml | 79 + .../bindings/iio/adc/microchip,mcp3911.yaml | 82 + .../bindings/iio/adc/motorola,cpcap-adc.yaml | 53 + .../bindings/iio/adc/nuvoton,nau7802.yaml | 50 + .../bindings/iio/adc/nuvoton,npcm750-adc.yaml | 67 + .../bindings/iio/adc/nxp,imx8qxp-adc.yaml | 78 + .../bindings/iio/adc/nxp,lpc1850-adc.yaml | 61 + .../bindings/iio/adc/nxp,lpc3220-adc.yaml | 50 + .../bindings/iio/adc/qcom,pm8018-adc.yaml | 166 + .../bindings/iio/adc/qcom,spmi-iadc.yaml | 60 + .../bindings/iio/adc/qcom,spmi-rradc.yaml | 51 + .../bindings/iio/adc/qcom,spmi-vadc.yaml | 279 + .../bindings/iio/adc/renesas,rcar-gyroadc.yaml | 143 + .../bindings/iio/adc/renesas,rzg2l-adc.yaml | 155 + .../bindings/iio/adc/richtek,rtq6056.yaml | 56 + .../bindings/iio/adc/rockchip-saradc.yaml | 81 + .../bindings/iio/adc/samsung,exynos-adc.yaml | 163 + .../bindings/iio/adc/sigma-delta-modulator.yaml | 37 + .../bindings/iio/adc/sprd,sc2720-adc.yaml | 120 + .../devicetree/bindings/iio/adc/st,stm32-adc.yaml | 546 ++ .../bindings/iio/adc/st,stm32-dfsdm-adc.yaml | 329 + .../devicetree/bindings/iio/adc/st,stmpe-adc.yaml | 44 + .../devicetree/bindings/iio/adc/ti,adc0832.yaml | 57 + .../devicetree/bindings/iio/adc/ti,adc084s021.yaml | 59 + .../devicetree/bindings/iio/adc/ti,adc108s102.yaml | 49 + .../devicetree/bindings/iio/adc/ti,adc12138.yaml | 87 + .../devicetree/bindings/iio/adc/ti,adc128s052.yaml | 60 + .../devicetree/bindings/iio/adc/ti,adc161s626.yaml | 52 + .../devicetree/bindings/iio/adc/ti,ads1015.yaml | 116 + .../devicetree/bindings/iio/adc/ti,ads124s08.yaml | 53 + .../devicetree/bindings/iio/adc/ti,ads131e08.yaml | 182 + .../devicetree/bindings/iio/adc/ti,ads7950.yaml | 65 + .../devicetree/bindings/iio/adc/ti,ads8344.yaml | 52 + .../devicetree/bindings/iio/adc/ti,ads8688.yaml | 50 + .../devicetree/bindings/iio/adc/ti,am3359-adc.yaml | 75 + .../bindings/iio/adc/ti,palmas-gpadc.yaml | 85 + .../devicetree/bindings/iio/adc/ti,tlc4541.yaml | 53 + .../devicetree/bindings/iio/adc/ti,tsc2046.yaml | 119 + .../bindings/iio/adc/ti,twl4030-madc.yaml | 48 + .../bindings/iio/adc/x-powers,axp209-adc.yaml | 74 + .../devicetree/bindings/iio/adc/xilinx-xadc.txt | 141 + .../bindings/iio/adc/xlnx,zynqmp-ams.yaml | 236 + .../bindings/iio/addac/adi,ad74413r.yaml | 159 + .../bindings/iio/afe/current-sense-amplifier.yaml | 54 + .../bindings/iio/afe/current-sense-shunt.yaml | 68 + .../bindings/iio/afe/temperature-sense-rtd.yaml | 101 + .../bindings/iio/afe/temperature-transducer.yaml | 114 + .../bindings/iio/afe/voltage-divider.yaml | 86 + .../bindings/iio/amplifiers/adi,ada4250.yaml | 51 + .../bindings/iio/amplifiers/adi,hmc425a.yaml | 50 + .../devicetree/bindings/iio/cdc/adi,ad7150.yaml | 69 + .../devicetree/bindings/iio/cdc/adi,ad7746.yaml | 77 + .../bindings/iio/chemical/ams,ccs811.yaml | 53 + .../bindings/iio/chemical/atlas,sensor.yaml | 61 + .../bindings/iio/chemical/plantower,pms7003.yaml | 52 + .../bindings/iio/chemical/senseair,sunrise.yaml | 55 + .../bindings/iio/chemical/sensirion,scd30.yaml | 68 + .../bindings/iio/chemical/sensirion,scd4x.yaml | 46 + .../bindings/iio/chemical/sensirion,sps30.yaml | 46 + Documentation/devicetree/bindings/iio/common.yaml | 37 + .../devicetree/bindings/iio/dac/adi,ad3552r.yaml | 218 + .../devicetree/bindings/iio/dac/adi,ad5064.yaml | 267 + .../devicetree/bindings/iio/dac/adi,ad5360.yaml | 78 + .../devicetree/bindings/iio/dac/adi,ad5380.yaml | 71 + .../devicetree/bindings/iio/dac/adi,ad5421.yaml | 52 + .../devicetree/bindings/iio/dac/adi,ad5449.yaml | 96 + .../devicetree/bindings/iio/dac/adi,ad5504.yaml | 50 + .../devicetree/bindings/iio/dac/adi,ad5592r.yaml | 204 + .../devicetree/bindings/iio/dac/adi,ad5624r.yaml | 48 + .../devicetree/bindings/iio/dac/adi,ad5686.yaml | 76 + .../devicetree/bindings/iio/dac/adi,ad5696.yaml | 57 + .../devicetree/bindings/iio/dac/adi,ad5755.yaml | 169 + .../devicetree/bindings/iio/dac/adi,ad5758.yaml | 140 + .../devicetree/bindings/iio/dac/adi,ad5761.yaml | 59 + .../devicetree/bindings/iio/dac/adi,ad5764.yaml | 61 + .../devicetree/bindings/iio/dac/adi,ad5766.yaml | 65 + .../devicetree/bindings/iio/dac/adi,ad5770r.yaml | 195 + .../devicetree/bindings/iio/dac/adi,ad5791.yaml | 53 + .../devicetree/bindings/iio/dac/adi,ad7293.yaml | 61 + .../devicetree/bindings/iio/dac/adi,ad7303.yaml | 50 + .../devicetree/bindings/iio/dac/adi,ad8801.yaml | 59 + .../devicetree/bindings/iio/dac/adi,ltc2688.yaml | 147 + .../devicetree/bindings/iio/dac/dpot-dac.yaml | 64 + .../devicetree/bindings/iio/dac/fsl,vf610-dac.yaml | 55 + .../devicetree/bindings/iio/dac/lltc,ltc1660.yaml | 51 + .../devicetree/bindings/iio/dac/lltc,ltc2632.yaml | 77 + .../devicetree/bindings/iio/dac/maxim,ds4424.yaml | 45 + .../devicetree/bindings/iio/dac/maxim,max5821.yaml | 44 + .../bindings/iio/dac/microchip,mcp4725.yaml | 90 + .../bindings/iio/dac/microchip,mcp4922.yaml | 48 + .../bindings/iio/dac/nxp,lpc1850-dac.yaml | 58 + .../devicetree/bindings/iio/dac/st,stm32-dac.yaml | 110 + .../devicetree/bindings/iio/dac/ti,dac082s085.yaml | 73 + .../devicetree/bindings/iio/dac/ti,dac5571.yaml | 53 + .../devicetree/bindings/iio/dac/ti,dac7311.yaml | 50 + .../devicetree/bindings/iio/dac/ti,dac7512.yaml | 42 + .../devicetree/bindings/iio/dac/ti,dac7612.yaml | 54 + .../bindings/iio/filter/adi,admv8818.yaml | 66 + .../devicetree/bindings/iio/frequency/adf4371.yaml | 68 + .../bindings/iio/frequency/adi,adf4350.yaml | 190 + .../bindings/iio/frequency/adi,admv1013.yaml | 91 + .../bindings/iio/frequency/adi,admv1014.yaml | 134 + .../bindings/iio/frequency/adi,admv4420.yaml | 55 + .../bindings/iio/frequency/adi,adrf6780.yaml | 131 + .../bindings/iio/gyroscope/adi,adxrs290.yaml | 59 + .../bindings/iio/gyroscope/bosch,bmg160.yaml | 51 + .../bindings/iio/gyroscope/invensense,mpu3050.yaml | 70 + .../bindings/iio/gyroscope/nxp,fxas21002c.yaml | 95 + .../bindings/iio/health/maxim,max30100.yaml | 51 + .../bindings/iio/health/maxim,max30102.yaml | 72 + .../devicetree/bindings/iio/health/ti,afe4403.yaml | 55 + .../devicetree/bindings/iio/health/ti,afe4404.yaml | 51 + .../devicetree/bindings/iio/humidity/dht11.yaml | 41 + .../bindings/iio/humidity/st,hts221.yaml | 54 + .../bindings/iio/humidity/ti,hdc2010.yaml | 46 + .../iio/impedance-analyzer/adi,ad5933.yaml | 59 + .../devicetree/bindings/iio/imu/adi,adis16460.yaml | 58 + .../devicetree/bindings/iio/imu/adi,adis16475.yaml | 129 + .../devicetree/bindings/iio/imu/adi,adis16480.yaml | 131 + .../devicetree/bindings/iio/imu/bosch,bmi160.yaml | 94 + .../devicetree/bindings/iio/imu/bosch,bno055.yaml | 59 + .../bindings/iio/imu/invensense,icm42600.yaml | 98 + .../bindings/iio/imu/invensense,mpu6050.yaml | 107 + .../devicetree/bindings/iio/imu/nxp,fxos8700.yaml | 81 + .../devicetree/bindings/iio/imu/st,lsm6dsx.yaml | 108 + .../devicetree/bindings/iio/light/adux1020.yaml | 49 + .../devicetree/bindings/iio/light/ams,as73211.yaml | 54 + .../bindings/iio/light/amstaos,tsl2563.yaml | 50 + .../bindings/iio/light/amstaos,tsl2591.yaml | 50 + .../bindings/iio/light/avago,apds9300.yaml | 44 + .../bindings/iio/light/avago,apds9960.yaml | 44 + .../devicetree/bindings/iio/light/bh1750.yaml | 45 + .../bindings/iio/light/capella,cm3605.yaml | 78 + .../bindings/iio/light/capella,cm36651.yaml | 48 + .../bindings/iio/light/dynaimage,al3010.yaml | 45 + .../bindings/iio/light/dynaimage,al3320a.yaml | 45 + .../devicetree/bindings/iio/light/isl29018.yaml | 58 + .../bindings/iio/light/liteon,ltr501.yaml | 58 + .../bindings/iio/light/liteon,ltrf216a.yaml | 49 + .../bindings/iio/light/maxim,max44009.yaml | 45 + .../devicetree/bindings/iio/light/noa1305.yaml | 46 + .../bindings/iio/light/sharp,gp2ap002.yaml | 87 + .../bindings/iio/light/sharp,gp2ap020a00f.yaml | 48 + .../devicetree/bindings/iio/light/st,uvis25.yaml | 42 + .../devicetree/bindings/iio/light/st,vl6180.yaml | 45 + .../devicetree/bindings/iio/light/stk33xx.yaml | 57 + .../devicetree/bindings/iio/light/ti,opt3001.yaml | 47 + .../devicetree/bindings/iio/light/tsl2583.yaml | 48 + .../devicetree/bindings/iio/light/tsl2772.yaml | 84 + .../bindings/iio/light/upisemi,us5182.yaml | 78 + .../devicetree/bindings/iio/light/veml6030.yaml | 64 + .../bindings/iio/light/vishay,vcnl4000.yaml | 54 + .../bindings/iio/light/vishay,vcnl4035.yaml | 45 + .../iio/magnetometer/asahi-kasei,ak8974.yaml | 57 + .../iio/magnetometer/asahi-kasei,ak8975.yaml | 93 + .../iio/magnetometer/bosch,bmc150_magn.yaml | 58 + .../bindings/iio/magnetometer/fsl,mag3110.yaml | 48 + .../iio/magnetometer/honeywell,hmc5843.yaml | 43 + .../bindings/iio/magnetometer/pni,rm3100.yaml | 42 + .../bindings/iio/magnetometer/yamaha,yas530.yaml | 112 + .../devicetree/bindings/iio/mount-matrix.txt | 203 + .../bindings/iio/multiplexer/io-channel-mux.yaml | 79 + .../bindings/iio/potentiometer/adi,ad5272.yaml | 51 + .../bindings/iio/potentiometer/max5432.yaml | 44 + .../iio/potentiometer/microchip,mcp41010.yaml | 49 + .../iio/potentiometer/microchip,mcp4131.yaml | 104 + .../iio/potentiometer/microchip,mcp4531.yaml | 116 + .../bindings/iio/potentiostat/ti,lmp91000.yaml | 68 + .../bindings/iio/pressure/asc,dlhl60d.yaml | 53 + .../devicetree/bindings/iio/pressure/bmp085.yaml | 75 + .../bindings/iio/pressure/hoperf,hp03.yaml | 47 + .../bindings/iio/pressure/meas,ms5611.yaml | 57 + .../bindings/iio/pressure/murata,zpa2326.yaml | 62 + .../bindings/iio/proximity/ams,as3935.yaml | 71 + .../bindings/iio/proximity/devantech-srf04.yaml | 86 + .../proximity/google,cros-ec-mkbp-proximity.yaml | 36 + .../bindings/iio/proximity/maxbotix,mb1232.yaml | 60 + .../bindings/iio/proximity/parallax-ping.yaml | 53 + .../bindings/iio/proximity/semtech,sx9310.yaml | 128 + .../bindings/iio/proximity/semtech,sx9324.yaml | 200 + .../bindings/iio/proximity/semtech,sx9360.yaml | 98 + .../bindings/iio/proximity/semtech,sx9500.yaml | 50 + .../bindings/iio/proximity/st,vl53l0x.yaml | 47 + .../bindings/iio/proximity/vishay,vcnl3020.yaml | 64 + .../bindings/iio/resolver/adi,ad2s90.yaml | 60 + .../bindings/iio/samsung,sensorhub-rinato.yaml | 73 + .../devicetree/bindings/iio/st,st-sensors.yaml | 197 + .../bindings/iio/temperature/adi,ltc2983.yaml | 466 ++ .../bindings/iio/temperature/maxim,max31855k.yaml | 76 + .../bindings/iio/temperature/maxim,max31856.yaml | 56 + .../bindings/iio/temperature/maxim,max31865.yaml | 54 + .../bindings/iio/temperature/melexis,mlx90614.yaml | 50 + .../bindings/iio/temperature/melexis,mlx90632.yaml | 59 + .../bindings/iio/temperature/ti,tmp007.yaml | 57 + .../bindings/iio/temperature/ti,tmp117.yaml | 41 + Documentation/devicetree/bindings/index.rst | 9 + .../bindings/infiniband/hisilicon-hns-roce.txt | 108 + .../devicetree/bindings/input/adc-joystick.yaml | 127 + .../devicetree/bindings/input/adc-keys.yaml | 103 + .../devicetree/bindings/input/adi,adp5588.yaml | 111 + .../input/allwinner,sun4i-a10-lradc-keys.yaml | 117 + .../devicetree/bindings/input/ariel-pwrbutton.yaml | 58 + .../devicetree/bindings/input/atmel,captouch.txt | 36 + .../devicetree/bindings/input/atmel,maxtouch.yaml | 113 + .../devicetree/bindings/input/azoteq,iqs7222.yaml | 950 +++ .../devicetree/bindings/input/brcm,bcm-keypad.txt | 107 + .../devicetree/bindings/input/clps711x-keypad.txt | 27 + .../devicetree/bindings/input/cpcap-pwrbutton.txt | 20 + .../devicetree/bindings/input/cypress,cyapa.txt | 42 + .../bindings/input/cypress,tm2-touchkey.yaml | 73 + .../devicetree/bindings/input/cypress-sf.yaml | 61 + .../devicetree/bindings/input/da9062-onkey.txt | 47 + .../devicetree/bindings/input/dlg,da7280.txt | 108 + .../bindings/input/dlink,dir685-touchkeys.txt | 21 + .../devicetree/bindings/input/e3x0-button.txt | 23 + .../devicetree/bindings/input/elan,ekth3000.yaml | 81 + .../devicetree/bindings/input/elan,ekth6915.yaml | 65 + .../bindings/input/fsl,mpr121-touchkey.yaml | 90 + .../devicetree/bindings/input/fsl,scu-key.yaml | 40 + .../devicetree/bindings/input/goodix,gt7375p.yaml | 68 + .../bindings/input/google,cros-ec-keyb.yaml | 140 + .../devicetree/bindings/input/gpio-beeper.txt | 13 + .../devicetree/bindings/input/gpio-decoder.txt | 23 + .../devicetree/bindings/input/gpio-keys.yaml | 142 + .../bindings/input/gpio-matrix-keypad.txt | 49 + .../devicetree/bindings/input/gpio-mouse.txt | 32 + .../devicetree/bindings/input/gpio-vibrator.yaml | 39 + .../devicetree/bindings/input/hid-over-i2c.yaml | 83 + .../devicetree/bindings/input/ibm,op-panel.yaml | 50 + .../devicetree/bindings/input/imx-keypad.yaml | 85 + .../devicetree/bindings/input/input-reset.txt | 33 + Documentation/devicetree/bindings/input/input.yaml | 64 + .../devicetree/bindings/input/iqs269a.yaml | 552 ++ .../devicetree/bindings/input/iqs626a.yaml | 838 ++ .../devicetree/bindings/input/iqs62x-keys.yaml | 132 + .../devicetree/bindings/input/lpc32xx-key.txt | 34 + .../devicetree/bindings/input/matrix-keymap.txt | 1 + .../devicetree/bindings/input/matrix-keymap.yaml | 48 + .../devicetree/bindings/input/max77650-onkey.yaml | 38 + .../bindings/input/mediatek,mt6779-keypad.yaml | 83 + .../bindings/input/mediatek,pmic-keys.yaml | 114 + .../bindings/input/microchip,cap11xx.yaml | 149 + .../devicetree/bindings/input/microchip,qt1050.txt | 78 + .../bindings/input/nvidia,tegra20-kbc.txt | 55 + .../devicetree/bindings/input/omap-keypad.txt | 28 + .../bindings/input/pine64,pinephone-keyboard.yaml | 66 + .../bindings/input/ps2keyb-mouse-apbps2.txt | 16 + .../devicetree/bindings/input/pwm-beeper.txt | 24 + .../devicetree/bindings/input/pwm-vibrator.yaml | 57 + .../devicetree/bindings/input/pxa27x-keypad.txt | 60 + .../bindings/input/qcom,pm8941-pwrkey.yaml | 51 + .../bindings/input/qcom,pm8xxx-keypad.txt | 90 + .../bindings/input/qcom,pm8xxx-pwrkey.txt | 46 + .../devicetree/bindings/input/qcom,pm8xxx-vib.yaml | 38 + .../devicetree/bindings/input/raydium_i2c_ts.txt | 19 + .../bindings/input/regulator-haptic.yaml | 43 + .../bindings/input/rmi4/rmi_2d_sensor.txt | 56 + .../devicetree/bindings/input/rmi4/rmi_f01.txt | 39 + .../devicetree/bindings/input/rmi4/rmi_i2c.txt | 61 + .../devicetree/bindings/input/rmi4/rmi_spi.txt | 56 + .../devicetree/bindings/input/rotary-encoder.txt | 50 + .../devicetree/bindings/input/samsung-keypad.txt | 77 + .../devicetree/bindings/input/snvs-pwrkey.txt | 1 + .../devicetree/bindings/input/spear-keyboard.txt | 20 + .../bindings/input/sprd,sc27xx-vibrator.yaml | 48 + .../devicetree/bindings/input/st-keyscan.txt | 60 + .../devicetree/bindings/input/stmpe-keypad.txt | 41 + .../devicetree/bindings/input/tca8418_keypad.txt | 10 + .../devicetree/bindings/input/ti,drv260x.txt | 50 + .../devicetree/bindings/input/ti,drv2665.txt | 17 + .../devicetree/bindings/input/ti,drv2667.txt | 17 + .../devicetree/bindings/input/ti,nspire-keypad.txt | 60 + .../bindings/input/ti,palmas-pwrbutton.txt | 35 + .../bindings/input/touchscreen/ad7879.txt | 71 + .../bindings/input/touchscreen/ads7846.txt | 106 + .../bindings/input/touchscreen/ar1021.txt | 15 + .../bindings/input/touchscreen/auo_pixcir_ts.txt | 30 + .../bindings/input/touchscreen/azoteq,iqs5xx.yaml | 75 + .../input/touchscreen/brcm,iproc-touchscreen.txt | 87 + .../bindings/input/touchscreen/bu21013.txt | 43 + .../bindings/input/touchscreen/bu21029.txt | 35 + .../input/touchscreen/chipone,icn8318.yaml | 62 + .../bindings/input/touchscreen/colibri-vf50-ts.txt | 34 + .../input/touchscreen/cypress,cy8ctma140.yaml | 72 + .../input/touchscreen/cypress,cy8ctma340.yaml | 148 + .../bindings/input/touchscreen/edt-ft5x06.yaml | 129 + .../bindings/input/touchscreen/eeti,exc3000.yaml | 58 + .../devicetree/bindings/input/touchscreen/eeti.txt | 30 + .../bindings/input/touchscreen/egalax-ts.txt | 18 + .../bindings/input/touchscreen/ektf2127.txt | 25 + .../input/touchscreen/elan,elants_i2c.yaml | 74 + .../bindings/input/touchscreen/fsl-mx25-tcq.txt | 34 + .../bindings/input/touchscreen/goodix.yaml | 81 + .../bindings/input/touchscreen/hideep.txt | 41 + .../bindings/input/touchscreen/hycon,hy46xx.yaml | 119 + .../bindings/input/touchscreen/ilitek_ts_i2c.yaml | 76 + .../input/touchscreen/imagis,ist3038c.yaml | 74 + .../bindings/input/touchscreen/imx6ul_tsc.txt | 38 + .../bindings/input/touchscreen/lpc32xx-tsc.txt | 16 + .../bindings/input/touchscreen/max11801-ts.txt | 17 + .../bindings/input/touchscreen/melfas,mms114.yaml | 87 + .../bindings/input/touchscreen/melfas_mip4.txt | 20 + .../bindings/input/touchscreen/mstar,msg2638.yaml | 69 + .../input/touchscreen/pixcir,pixcir_ts.yaml | 68 + .../input/touchscreen/raspberrypi,firmware-ts.txt | 26 + .../input/touchscreen/resistive-adc-touch.yaml | 86 + .../bindings/input/touchscreen/samsung,s6sy761.txt | 32 + .../bindings/input/touchscreen/silead,gsl1680.yaml | 91 + .../bindings/input/touchscreen/sis_i2c.txt | 31 + .../input/touchscreen/sitronix,st1232.yaml | 50 + .../bindings/input/touchscreen/st,stmfts.txt | 41 + .../bindings/input/touchscreen/stmpe.txt | 108 + .../bindings/input/touchscreen/sx8654.txt | 23 + .../bindings/input/touchscreen/ti,am3359-tsc.yaml | 76 + .../bindings/input/touchscreen/ti,tsc2005.yaml | 128 + .../bindings/input/touchscreen/touchscreen.txt | 1 + .../bindings/input/touchscreen/touchscreen.yaml | 89 + .../bindings/input/touchscreen/ts4800-ts.txt | 11 + .../bindings/input/touchscreen/tsc2007.txt | 39 + .../bindings/input/touchscreen/zet6223.txt | 30 + .../bindings/input/touchscreen/zforce_ts.txt | 34 + .../bindings/input/touchscreen/zinitix,bt400.yaml | 115 + .../bindings/input/tps65218-pwrbutton.txt | 30 + .../devicetree/bindings/input/twl4030-keypad.txt | 27 + .../bindings/input/twl4030-pwrbutton.txt | 21 + .../bindings/input/zii,rave-sp-pwrbutton.txt | 22 + .../bindings/interconnect/fsl,imx8m-noc.yaml | 104 + .../bindings/interconnect/interconnect.txt | 86 + .../bindings/interconnect/mediatek,cci.yaml | 142 + .../bindings/interconnect/qcom,bcm-voter.yaml | 65 + .../bindings/interconnect/qcom,msm8974.yaml | 62 + .../bindings/interconnect/qcom,msm8998-bwmon.yaml | 90 + .../bindings/interconnect/qcom,osm-l3.yaml | 66 + .../bindings/interconnect/qcom,qcm2290.yaml | 137 + .../devicetree/bindings/interconnect/qcom,rpm.yaml | 247 + .../bindings/interconnect/qcom,rpmh-common.yaml | 43 + .../bindings/interconnect/qcom,rpmh.yaml | 161 + .../bindings/interconnect/qcom,sm6350-rpmh.yaml | 82 + .../bindings/interconnect/samsung,exynos-bus.yaml | 290 + .../interrupt-controller/abilis,tb10x-ictl.txt | 37 + .../interrupt-controller/actions,owl-sirq.yaml | 65 + .../interrupt-controller/al,alpine-msix.txt | 25 + .../allwinner,sun4i-a10-ic.yaml | 47 + .../allwinner,sun6i-a31-r-intc.yaml | 67 + .../allwinner,sun7i-a20-sc-nmi.yaml | 64 + .../interrupt-controller/amazon,al-fic.txt | 27 + .../amlogic,meson-gpio-intc.txt | 38 + .../bindings/interrupt-controller/apple,aic.yaml | 122 + .../bindings/interrupt-controller/apple,aic2.yaml | 98 + .../bindings/interrupt-controller/arm,gic-v3.yaml | 296 + .../bindings/interrupt-controller/arm,gic.yaml | 243 + .../bindings/interrupt-controller/arm,nvic.txt | 36 + .../arm,versatile-fpga-irq.txt | 36 + .../bindings/interrupt-controller/arm,vic.yaml | 81 + .../interrupt-controller/aspeed,ast2400-i2c-ic.txt | 25 + .../interrupt-controller/aspeed,ast2400-vic.txt | 23 + .../interrupt-controller/aspeed,ast2xxx-scu-ic.txt | 23 + .../bindings/interrupt-controller/atmel,aic.txt | 43 + .../brcm,bcm2835-armctrl-ic.txt | 131 + .../interrupt-controller/brcm,bcm2836-l1-intc.txt | 37 + .../interrupt-controller/brcm,bcm6345-l1-intc.txt | 55 + .../interrupt-controller/brcm,bcm7038-l1-intc.yaml | 91 + .../interrupt-controller/brcm,bcm7120-l2-intc.yaml | 151 + .../interrupt-controller/brcm,l2-intc.yaml | 72 + .../interrupt-controller/cdns,xtensa-mx.txt | 18 + .../interrupt-controller/cdns,xtensa-pic.txt | 25 + .../interrupt-controller/cirrus,clps711x-intc.txt | 41 + .../interrupt-controller/csky,apb-intc.txt | 62 + .../bindings/interrupt-controller/csky,mpintc.txt | 52 + .../bindings/interrupt-controller/digicolor-ic.txt | 21 + .../interrupt-controller/ezchip,nps400-ic.txt | 17 + .../interrupt-controller/faraday,ftintc010.txt | 25 + .../bindings/interrupt-controller/fsl,intmux.yaml | 68 + .../interrupt-controller/fsl,irqsteer.yaml | 90 + .../interrupt-controller/fsl,ls-extirq.yaml | 118 + .../interrupt-controller/fsl,ls-scfg-msi.txt | 30 + .../bindings/interrupt-controller/fsl,mu-msi.yaml | 99 + .../interrupt-controller/google,goldfish-pic.txt | 30 + .../interrupt-controller/hisilicon,mbigen-v2.txt | 84 + .../interrupt-controller/idt,32434-pic.yaml | 52 + .../bindings/interrupt-controller/img,pdc-intc.txt | 105 + .../interrupt-controller/ingenic,intc.yaml | 66 + .../interrupt-controller/intel,ce4100-ioapic.txt | 26 + .../intel,ixp4xx-interrupt.yaml | 56 + .../bindings/interrupt-controller/interrupts.txt | 122 + .../bindings/interrupt-controller/jcore,aic.txt | 26 + .../kontron,sl28cpld-intc.yaml | 54 + .../interrupt-controller/loongson,htpic.yaml | 61 + .../interrupt-controller/loongson,htvec.yaml | 57 + .../interrupt-controller/loongson,liointc.yaml | 119 + .../interrupt-controller/loongson,ls1x-intc.txt | 24 + .../interrupt-controller/loongson,pch-msi.yaml | 62 + .../interrupt-controller/loongson,pch-pic.yaml | 57 + .../interrupt-controller/lsi,zevio-intc.txt | 18 + .../marvell,armada-370-xp-mpic.txt | 38 + .../interrupt-controller/marvell,armada-8k-pic.txt | 25 + .../bindings/interrupt-controller/marvell,gicp.txt | 27 + .../bindings/interrupt-controller/marvell,icu.txt | 112 + .../marvell,odmi-controller.txt | 42 + .../interrupt-controller/marvell,orion-intc.txt | 48 + .../bindings/interrupt-controller/marvell,sei.txt | 36 + .../interrupt-controller/mediatek,cirq.txt | 33 + .../interrupt-controller/mediatek,sysirq.txt | 43 + .../interrupt-controller/microchip,eic.yaml | 73 + .../interrupt-controller/microchip,pic32-evic.txt | 67 + .../bindings/interrupt-controller/mrvl,intc.yaml | 132 + .../mscc,ocelot-icpu-intr.yaml | 64 + .../interrupt-controller/msi-controller.yaml | 46 + .../bindings/interrupt-controller/msi.txt | 135 + .../interrupt-controller/mstar,mst-intc.yaml | 64 + .../mti,cpu-interrupt-controller.yaml | 46 + .../bindings/interrupt-controller/mti,gic.yaml | 146 + .../interrupt-controller/nuvoton,wpcm450-aic.yaml | 39 + .../interrupt-controller/nvidia,tegra20-ictlr.txt | 41 + .../interrupt-controller/nxp,lpc3220-mic.txt | 58 + .../bindings/interrupt-controller/open-pic.txt | 97 + .../interrupt-controller/opencores,or1k-pic.txt | 23 + .../interrupt-controller/openrisc,ompic.txt | 22 + .../interrupt-controller/qca,ath79-cpu-intc.txt | 44 + .../interrupt-controller/qca,ath79-misc-intc.txt | 45 + .../bindings/interrupt-controller/qcom,mpm.yaml | 100 + .../bindings/interrupt-controller/qcom,pdc.yaml | 87 + .../interrupt-controller/rda,8810pl-intc.yaml | 43 + .../interrupt-controller/realtek,rtl-intc.yaml | 87 + .../interrupt-controller/renesas,intc-irqpin.yaml | 107 + .../interrupt-controller/renesas,irqc.yaml | 92 + .../interrupt-controller/renesas,rza1-irqc.yaml | 80 + .../interrupt-controller/renesas,rzg2l-irqc.yaml | 135 + .../interrupt-controller/riscv,cpu-intc.txt | 52 + .../samsung,exynos4210-combiner.yaml | 96 + .../interrupt-controller/samsung,s3c24xx-irq.txt | 53 + .../interrupt-controller/sifive,plic-1.0.0.yaml | 170 + .../interrupt-controller/snps,arc700-intc.txt | 24 + .../interrupt-controller/snps,archs-idu-intc.txt | 46 + .../interrupt-controller/snps,archs-intc.txt | 22 + .../interrupt-controller/snps,dw-apb-ictl.txt | 43 + .../socionext,synquacer-exiu.txt | 31 + .../socionext,uniphier-aidet.yaml | 62 + .../interrupt-controller/st,spear3xx-shirq.txt | 44 + .../interrupt-controller/st,sti-irq-syscfg.txt | 35 + .../interrupt-controller/st,stm32-exti.yaml | 101 + .../interrupt-controller/sunplus,sp7021-intc.yaml | 62 + .../interrupt-controller/technologic,ts4800.txt | 14 + .../bindings/interrupt-controller/ti,cp-intc.txt | 27 + .../interrupt-controller/ti,keystone-irq.txt | 36 + .../interrupt-controller/ti,omap-intc-irq.txt | 28 + .../interrupt-controller/ti,omap2-intc.txt | 27 + .../interrupt-controller/ti,omap4-wugen-mpu | 31 + .../interrupt-controller/ti,pruss-intc.yaml | 163 + .../bindings/interrupt-controller/ti,sci-inta.yaml | 115 + .../bindings/interrupt-controller/ti,sci-intr.yaml | 107 + .../interrupt-controller/via,vt8500-intc.txt | 16 + .../bindings/iommu/allwinner,sun50i-h6-iommu.yaml | 61 + .../devicetree/bindings/iommu/apple,dart.yaml | 84 + .../devicetree/bindings/iommu/apple,sart.yaml | 52 + .../devicetree/bindings/iommu/arm,smmu-v3.yaml | 95 + .../devicetree/bindings/iommu/arm,smmu.yaml | 300 + Documentation/devicetree/bindings/iommu/iommu.txt | 206 + .../devicetree/bindings/iommu/mediatek,iommu.yaml | 218 + .../devicetree/bindings/iommu/msm,iommu-v0.txt | 64 + .../bindings/iommu/nvidia,tegra30-smmu.txt | 21 + .../devicetree/bindings/iommu/qcom,iommu.txt | 121 + .../bindings/iommu/renesas,ipmmu-vmsa.yaml | 121 + .../devicetree/bindings/iommu/rockchip,iommu.yaml | 83 + .../devicetree/bindings/iommu/samsung,sysmmu.yaml | 99 + .../devicetree/bindings/iommu/sprd,iommu.yaml | 57 + .../devicetree/bindings/iommu/ti,omap-iommu.txt | 59 + .../devicetree/bindings/iommu/xen,grant-dma.yaml | 39 + .../bindings/ipmi/aspeed,ast2400-ibt-bmc.txt | 28 + .../bindings/ipmi/aspeed,ast2400-kcs-bmc.yaml | 106 + .../devicetree/bindings/ipmi/ipmi-ipmb.yaml | 67 + .../devicetree/bindings/ipmi/ipmi-smic.yaml | 63 + .../devicetree/bindings/ipmi/npcm7xx-kcs-bmc.txt | 40 + Documentation/devicetree/bindings/jailhouse.txt | 8 + .../devicetree/bindings/leds/ams,as3645a.txt | 85 + .../bindings/leds/backlight/88pm860x.txt | 15 + .../bindings/leds/backlight/arcxcnn_bl.txt | 33 + .../devicetree/bindings/leds/backlight/common.yaml | 36 + .../bindings/leds/backlight/gpio-backlight.yaml | 41 + .../bindings/leds/backlight/kinetic,ktd253.yaml | 49 + .../bindings/leds/backlight/led-backlight.yaml | 59 + .../bindings/leds/backlight/lm3630a-backlight.yaml | 142 + .../devicetree/bindings/leds/backlight/lp855x.txt | 72 + .../bindings/leds/backlight/max8925-backlight.txt | 10 + .../leds/backlight/mediatek,mt6370-backlight.yaml | 121 + .../bindings/leds/backlight/pwm-backlight.yaml | 104 + .../bindings/leds/backlight/qcom-wled.yaml | 262 + .../leds/backlight/richtek,rt4831-backlight.yaml | 67 + .../bindings/leds/backlight/sky81452-backlight.txt | 29 + .../bindings/leds/backlight/tps65217-backlight.txt | 27 + .../leds/backlight/zii,rave-sp-backlight.txt | 23 + Documentation/devicetree/bindings/leds/common.txt | 1 + Documentation/devicetree/bindings/leds/common.yaml | 241 + .../bindings/leds/cznic,turris-omnia-leds.yaml | 91 + .../devicetree/bindings/leds/irled/gpio-ir-tx.txt | 14 + .../devicetree/bindings/leds/irled/pwm-ir-tx.txt | 13 + .../devicetree/bindings/leds/irled/spi-ir-led.txt | 29 + .../devicetree/bindings/leds/issi,is31fl319x.yaml | 193 + .../devicetree/bindings/leds/kinetic,ktd2692.yaml | 87 + .../devicetree/bindings/leds/leds-an30259a.txt | 55 + .../devicetree/bindings/leds/leds-aw2013.yaml | 90 + .../devicetree/bindings/leds/leds-bcm63138.yaml | 95 + .../devicetree/bindings/leds/leds-bcm6328.yaml | 404 + .../devicetree/bindings/leds/leds-bcm6358.txt | 145 + .../bindings/leds/leds-class-multicolor.yaml | 41 + .../devicetree/bindings/leds/leds-cpcap.txt | 29 + .../devicetree/bindings/leds/leds-cr0014114.txt | 66 + .../devicetree/bindings/leds/leds-el15203000.txt | 69 + .../devicetree/bindings/leds/leds-gpio.yaml | 85 + .../devicetree/bindings/leds/leds-is31fl32xx.txt | 52 + .../devicetree/bindings/leds/leds-lgm.yaml | 131 + .../devicetree/bindings/leds/leds-lm3532.txt | 105 + .../devicetree/bindings/leds/leds-lm3601x.txt | 51 + .../devicetree/bindings/leds/leds-lm36274.txt | 85 + .../devicetree/bindings/leds/leds-lm3692x.txt | 65 + .../devicetree/bindings/leds/leds-lm3697.txt | 73 + .../devicetree/bindings/leds/leds-lp50xx.yaml | 151 + .../devicetree/bindings/leds/leds-lp55xx.yaml | 228 + .../devicetree/bindings/leds/leds-lp8860.txt | 50 + .../devicetree/bindings/leds/leds-lt3593.txt | 37 + .../devicetree/bindings/leds/leds-max77650.yaml | 54 + .../devicetree/bindings/leds/leds-mt6323.txt | 60 + .../devicetree/bindings/leds/leds-mt6360.yaml | 157 + .../devicetree/bindings/leds/leds-netxbig.txt | 92 + .../devicetree/bindings/leds/leds-ns2.txt | 35 + .../devicetree/bindings/leds/leds-pca9532.txt | 49 + .../devicetree/bindings/leds/leds-pca955x.txt | 89 + .../devicetree/bindings/leds/leds-pm8058.txt | 67 + .../devicetree/bindings/leds/leds-powernv.txt | 26 + .../bindings/leds/leds-pwm-multicolor.yaml | 88 + .../devicetree/bindings/leds/leds-pwm.yaml | 70 + .../devicetree/bindings/leds/leds-qcom-lpg.yaml | 177 + .../devicetree/bindings/leds/leds-rt4505.yaml | 57 + .../devicetree/bindings/leds/leds-sc27xx-bltc.txt | 43 + .../devicetree/bindings/leds/leds-sgm3140.yaml | 61 + .../devicetree/bindings/leds/leds-spi-byte.txt | 44 + .../devicetree/bindings/leds/leds-tlc591xx.txt | 40 + .../bindings/leds/leds-trigger-pattern.txt | 49 + .../devicetree/bindings/leds/maxim,max77693.yaml | 105 + .../bindings/leds/mediatek,mt6370-flashlight.yaml | 41 + .../bindings/leds/mediatek,mt6370-indicator.yaml | 80 + Documentation/devicetree/bindings/leds/pca963x.txt | 52 + .../devicetree/bindings/leds/register-bit-led.yaml | 95 + .../devicetree/bindings/leds/regulator-led.yaml | 55 + .../devicetree/bindings/leds/richtek,rt8515.yaml | 111 + .../bindings/leds/rohm,bd71828-leds.yaml | 54 + .../devicetree/bindings/leds/skyworks,aat1290.yaml | 95 + .../devicetree/bindings/leds/ti,tca6507.yaml | 135 + .../devicetree/bindings/leds/trigger-source.yaml | 26 + .../mailbox/allwinner,sun6i-a31-msgbox.yaml | 80 + .../devicetree/bindings/mailbox/altera-mailbox.txt | 48 + .../bindings/mailbox/amlogic,meson-gxbb-mhu.yaml | 53 + .../devicetree/bindings/mailbox/apple,mailbox.yaml | 86 + .../devicetree/bindings/mailbox/arm,mhu.yaml | 169 + .../devicetree/bindings/mailbox/arm,mhuv2.yaml | 208 + .../bindings/mailbox/brcm,bcm2835-mbox.txt | 26 + .../bindings/mailbox/brcm,iproc-flexrm-mbox.txt | 59 + .../bindings/mailbox/brcm,iproc-pdc-mbox.txt | 25 + .../devicetree/bindings/mailbox/fsl,mu.yaml | 135 + .../bindings/mailbox/hisilicon,hi3660-mailbox.txt | 51 + .../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 74 + .../devicetree/bindings/mailbox/mailbox.txt | 60 + .../mailbox/marvell,armada-3700-rwtm-mailbox.txt | 16 + .../bindings/mailbox/mediatek,gce-mailbox.yaml | 85 + .../bindings/mailbox/microchip,mpfs-mailbox.yaml | 54 + .../devicetree/bindings/mailbox/mtk,adsp-mbox.yaml | 51 + .../bindings/mailbox/nvidia,tegra186-hsp.yaml | 123 + .../bindings/mailbox/qcom,apcs-kpss-global.yaml | 171 + .../devicetree/bindings/mailbox/qcom-ipcc.yaml | 76 + .../bindings/mailbox/rockchip-mailbox.txt | 32 + .../devicetree/bindings/mailbox/sprd-mailbox.yaml | 69 + .../devicetree/bindings/mailbox/st,stm32-ipcc.yaml | 76 + .../devicetree/bindings/mailbox/sti-mailbox.txt | 51 + .../bindings/mailbox/ti,message-manager.txt | 50 + .../bindings/mailbox/ti,omap-mailbox.yaml | 299 + .../bindings/mailbox/ti,secure-proxy.yaml | 79 + .../bindings/mailbox/xgene-slimpro-mailbox.txt | 35 + .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.yaml | 140 + .../devicetree/bindings/media/allegro,al5e.yaml | 105 + .../bindings/media/allwinner,sun4i-a10-csi.yaml | 129 + .../bindings/media/allwinner,sun4i-a10-ir.yaml | 77 + .../media/allwinner,sun4i-a10-video-engine.yaml | 94 + .../bindings/media/allwinner,sun50i-h6-vpu-g2.yaml | 69 + .../bindings/media/allwinner,sun6i-a31-csi.yaml | 139 + .../media/allwinner,sun6i-a31-mipi-csi2.yaml | 137 + .../media/allwinner,sun8i-a83t-de2-rotate.yaml | 70 + .../media/allwinner,sun8i-a83t-mipi-csi2.yaml | 125 + .../media/allwinner,sun8i-h3-deinterlace.yaml | 83 + .../bindings/media/amlogic,axg-ge2d.yaml | 47 + .../devicetree/bindings/media/amlogic,gx-vdec.yaml | 140 + .../bindings/media/amlogic,meson-gx-ao-cec.yaml | 95 + .../bindings/media/amlogic,meson-ir-tx.yaml | 60 + .../devicetree/bindings/media/amphion,vpu.yaml | 180 + .../devicetree/bindings/media/aspeed-video.txt | 33 + .../devicetree/bindings/media/atmel,isc.yaml | 115 + .../devicetree/bindings/media/atmel-isi.txt | 66 + .../devicetree/bindings/media/cdns,csi2rx.txt | 100 + .../devicetree/bindings/media/cdns,csi2tx.txt | 99 + .../devicetree/bindings/media/cec-gpio.txt | 42 + Documentation/devicetree/bindings/media/cec.txt | 8 + Documentation/devicetree/bindings/media/coda.yaml | 107 + .../devicetree/bindings/media/exynos-fimc-lite.txt | 16 + .../devicetree/bindings/media/exynos4-fimc-is.txt | 50 + .../devicetree/bindings/media/fsl-pxp.txt | 26 + .../devicetree/bindings/media/fsl-vdoa.txt | 21 + .../bindings/media/gpio-ir-receiver.yaml | 40 + .../devicetree/bindings/media/hix5hd2-ir.txt | 26 + .../devicetree/bindings/media/i2c/ad5820.txt | 28 + .../devicetree/bindings/media/i2c/adp1653.txt | 38 + .../devicetree/bindings/media/i2c/adv7180.yaml | 179 + .../devicetree/bindings/media/i2c/adv7343.txt | 48 + .../devicetree/bindings/media/i2c/adv748x.yaml | 212 + .../devicetree/bindings/media/i2c/adv7604.yaml | 160 + .../devicetree/bindings/media/i2c/ak7375.txt | 8 + .../bindings/media/i2c/aptina,mt9p031.yaml | 109 + .../bindings/media/i2c/aptina,mt9v111.yaml | 75 + .../bindings/media/i2c/chrontel,ch7322.yaml | 69 + .../bindings/media/i2c/dongwoon,dw9714.yaml | 47 + .../bindings/media/i2c/dongwoon,dw9768.yaml | 97 + .../bindings/media/i2c/dongwoon,dw9807-vcm.yaml | 41 + .../devicetree/bindings/media/i2c/hynix,hi846.yaml | 124 + .../bindings/media/i2c/imi,rdacm2x-gmsl.yaml | 137 + .../devicetree/bindings/media/i2c/imx219.yaml | 109 + .../devicetree/bindings/media/i2c/imx258.yaml | 134 + .../devicetree/bindings/media/i2c/imx290.txt | 57 + .../bindings/media/i2c/isil,isl79987.yaml | 113 + .../devicetree/bindings/media/i2c/max2175.txt | 59 + .../bindings/media/i2c/maxim,max9286.yaml | 378 + .../bindings/media/i2c/maxim,max96712.yaml | 111 + .../bindings/media/i2c/melexis,mlx90640.txt | 20 + .../devicetree/bindings/media/i2c/mipi-ccs.yaml | 132 + .../devicetree/bindings/media/i2c/mt9m001.txt | 38 + .../devicetree/bindings/media/i2c/mt9m111.txt | 37 + .../devicetree/bindings/media/i2c/mt9v032.txt | 41 + .../devicetree/bindings/media/i2c/onnn,ar0521.yaml | 112 + .../devicetree/bindings/media/i2c/ov2640.txt | 41 + .../devicetree/bindings/media/i2c/ov2659.txt | 47 + .../devicetree/bindings/media/i2c/ov2685.txt | 41 + .../devicetree/bindings/media/i2c/ov5645.txt | 54 + .../devicetree/bindings/media/i2c/ov5695.txt | 41 + .../devicetree/bindings/media/i2c/ov7251.txt | 52 + .../devicetree/bindings/media/i2c/ov7670.txt | 55 + .../devicetree/bindings/media/i2c/ov7740.txt | 47 + .../devicetree/bindings/media/i2c/ov8856.yaml | 134 + .../devicetree/bindings/media/i2c/ov9650.txt | 36 + .../bindings/media/i2c/ovti,ov02a10.yaml | 154 + .../devicetree/bindings/media/i2c/ovti,ov2680.yaml | 97 + .../devicetree/bindings/media/i2c/ovti,ov5640.yaml | 154 + .../devicetree/bindings/media/i2c/ovti,ov5647.yaml | 75 + .../devicetree/bindings/media/i2c/ovti,ov5648.yaml | 109 + .../devicetree/bindings/media/i2c/ovti,ov5693.yaml | 124 + .../devicetree/bindings/media/i2c/ovti,ov772x.yaml | 133 + .../devicetree/bindings/media/i2c/ovti,ov8865.yaml | 118 + .../devicetree/bindings/media/i2c/ovti,ov9282.yaml | 91 + .../bindings/media/i2c/panasonic,amg88xx.txt | 19 + .../devicetree/bindings/media/i2c/rda,rda5807.yaml | 67 + .../devicetree/bindings/media/i2c/sony,imx214.yaml | 125 + .../devicetree/bindings/media/i2c/sony,imx274.yaml | 72 + .../devicetree/bindings/media/i2c/sony,imx334.yaml | 90 + .../devicetree/bindings/media/i2c/sony,imx335.yaml | 91 + .../devicetree/bindings/media/i2c/sony,imx412.yaml | 100 + .../bindings/media/i2c/st,st-mipid02.txt | 82 + .../devicetree/bindings/media/i2c/tc358743.txt | 48 + .../devicetree/bindings/media/i2c/tda1997x.txt | 178 + .../devicetree/bindings/media/i2c/ths8200.txt | 19 + .../bindings/media/i2c/toshiba,et8ek8.txt | 55 + .../devicetree/bindings/media/i2c/tvp514x.txt | 44 + .../devicetree/bindings/media/i2c/tvp5150.txt | 157 + .../devicetree/bindings/media/i2c/tvp7002.txt | 53 + .../devicetree/bindings/media/img-ir-rev1.txt | 34 + Documentation/devicetree/bindings/media/imx.txt | 53 + .../bindings/media/marvell,mmp2-ccic.yaml | 94 + .../bindings/media/mediatek,mdp3-rdma.yaml | 100 + .../bindings/media/mediatek,mdp3-rsz.yaml | 77 + .../bindings/media/mediatek,mdp3-wrot.yaml | 85 + .../bindings/media/mediatek,vcodec-decoder.yaml | 167 + .../bindings/media/mediatek,vcodec-encoder.yaml | 180 + .../media/mediatek,vcodec-subdev-decoder.yaml | 293 + .../bindings/media/mediatek-jpeg-decoder.yaml | 80 + .../bindings/media/mediatek-jpeg-encoder.yaml | 78 + .../devicetree/bindings/media/mediatek-mdp.txt | 95 + .../devicetree/bindings/media/mediatek-vpu.txt | 31 + .../devicetree/bindings/media/meson-ir.txt | 20 + .../bindings/media/microchip,csi2dc.yaml | 199 + .../bindings/media/microchip,sama5d4-vdec.yaml | 47 + .../devicetree/bindings/media/microchip,xisc.yaml | 128 + .../devicetree/bindings/media/mtk-cir.txt | 28 + .../devicetree/bindings/media/nokia,n900-ir | 20 + .../bindings/media/nvidia,tegra-vde.yaml | 119 + .../devicetree/bindings/media/nxp,dw100.yaml | 69 + .../bindings/media/nxp,imx-mipi-csi2.yaml | 219 + .../devicetree/bindings/media/nxp,imx7-csi.yaml | 73 + .../devicetree/bindings/media/nxp,imx8-jpeg.yaml | 89 + .../bindings/media/nxp,imx8mq-mipi-csi2.yaml | 172 + .../devicetree/bindings/media/nxp,imx8mq-vpu.yaml | 69 + .../devicetree/bindings/media/pxa-camera.txt | 42 + .../bindings/media/qcom,msm8916-camss.yaml | 246 + .../bindings/media/qcom,msm8916-venus.yaml | 122 + .../bindings/media/qcom,msm8996-camss.yaml | 367 + .../bindings/media/qcom,msm8996-venus.yaml | 175 + .../bindings/media/qcom,sc7180-venus.yaml | 146 + .../bindings/media/qcom,sc7280-venus.yaml | 162 + .../bindings/media/qcom,sdm660-camss.yaml | 385 + .../bindings/media/qcom,sdm660-venus.yaml | 187 + .../bindings/media/qcom,sdm845-camss.yaml | 360 + .../bindings/media/qcom,sdm845-venus-v2.yaml | 146 + .../bindings/media/qcom,sdm845-venus.yaml | 159 + .../bindings/media/qcom,sm8250-camss.yaml | 463 ++ .../bindings/media/qcom,sm8250-venus.yaml | 167 + Documentation/devicetree/bindings/media/rc.txt | 1 + Documentation/devicetree/bindings/media/rc.yaml | 161 + .../devicetree/bindings/media/renesas,ceu.yaml | 82 + .../devicetree/bindings/media/renesas,csi2.yaml | 168 + .../devicetree/bindings/media/renesas,drif.yaml | 269 + .../devicetree/bindings/media/renesas,fcp.yaml | 66 + .../devicetree/bindings/media/renesas,fdp1.yaml | 69 + .../devicetree/bindings/media/renesas,imr.yaml | 67 + .../devicetree/bindings/media/renesas,isp.yaml | 196 + .../devicetree/bindings/media/renesas,jpu.yaml | 65 + .../devicetree/bindings/media/renesas,vin.yaml | 356 + .../devicetree/bindings/media/renesas,vsp1.yaml | 124 + .../bindings/media/rockchip,rk3568-vepu.yaml | 69 + .../devicetree/bindings/media/rockchip,vdec.yaml | 83 + .../devicetree/bindings/media/rockchip-isp1.yaml | 287 + .../devicetree/bindings/media/rockchip-rga.yaml | 83 + .../devicetree/bindings/media/rockchip-vpu.yaml | 96 + .../devicetree/bindings/media/s5p-cec.txt | 36 + .../devicetree/bindings/media/s5p-mfc.txt | 76 + .../bindings/media/samsung,exynos5250-gsc.yaml | 109 + .../bindings/media/samsung,s5pv210-jpeg.yaml | 123 + .../devicetree/bindings/media/samsung-fimc.txt | 209 + .../bindings/media/samsung-mipi-csis.txt | 81 + .../devicetree/bindings/media/samsung-s5c73m3.txt | 97 + .../devicetree/bindings/media/samsung-s5k5baf.txt | 58 + .../devicetree/bindings/media/samsung-s5k6a3.txt | 33 + Documentation/devicetree/bindings/media/si470x.txt | 26 + Documentation/devicetree/bindings/media/si4713.txt | 30 + .../devicetree/bindings/media/spi/sony-cxd2880.txt | 18 + .../devicetree/bindings/media/st,st-delta.txt | 17 + .../devicetree/bindings/media/st,st-hva.txt | 24 + .../devicetree/bindings/media/st,stih4xx.txt | 32 + .../devicetree/bindings/media/st,stm32-cec.yaml | 53 + .../devicetree/bindings/media/st,stm32-dcmi.yaml | 116 + .../devicetree/bindings/media/st,stm32-dma2d.yaml | 71 + Documentation/devicetree/bindings/media/st-rc.txt | 29 + .../devicetree/bindings/media/stih-cec.txt | 27 + .../bindings/media/stih407-c8sectpfe.txt | 88 + .../devicetree/bindings/media/tegra-cec.txt | 27 + .../devicetree/bindings/media/ti,cal.yaml | 177 + .../devicetree/bindings/media/ti,da850-vpif.txt | 106 + .../devicetree/bindings/media/ti,omap3isp.txt | 71 + .../devicetree/bindings/media/ti,vpe.yaml | 64 + .../devicetree/bindings/media/ti-am437x-vpfe.txt | 61 + .../bindings/media/video-interface-devices.yaml | 406 + .../devicetree/bindings/media/video-interfaces.txt | 1 + .../bindings/media/video-interfaces.yaml | 218 + .../devicetree/bindings/media/video-mux.yaml | 106 + .../devicetree/bindings/media/xilinx/video.txt | 35 + .../bindings/media/xilinx/xlnx,csi2rxss.yaml | 209 + .../devicetree/bindings/media/xilinx/xlnx,v-tc.txt | 33 + .../bindings/media/xilinx/xlnx,v-tpg.txt | 71 + .../bindings/media/xilinx/xlnx,video.txt | 55 + .../bindings/memory-controllers/arm,pl172.txt | 127 + .../bindings/memory-controllers/arm,pl353-smc.yaml | 130 + .../bindings/memory-controllers/atmel,ebi.txt | 137 + .../memory-controllers/baikal,bt1-l2-ctl.yaml | 63 + .../memory-controllers/brcm,brcmstb-memc-ddr.yaml | 52 + .../bindings/memory-controllers/brcm,dpfe-cpu.yaml | 48 + .../memory-controllers/calxeda-ddr-ctrlr.yaml | 42 + .../memory-controllers/canaan,k210-sram.yaml | 52 + .../ddr/jedec,lpddr2-timings.yaml | 135 + .../memory-controllers/ddr/jedec,lpddr2.yaml | 234 + .../ddr/jedec,lpddr3-timings.yaml | 157 + .../memory-controllers/ddr/jedec,lpddr3.yaml | 263 + .../bindings/memory-controllers/exynos-srom.yaml | 127 + .../bindings/memory-controllers/fsl/fsl,ddr.yaml | 77 + .../bindings/memory-controllers/fsl/fsl,ifc.yaml | 113 + .../memory-controllers/fsl/imx8m-ddrc.yaml | 73 + .../bindings/memory-controllers/fsl/mmdc.yaml | 51 + .../ingenic,nemc-peripherals.yaml | 46 + .../bindings/memory-controllers/ingenic,nemc.yaml | 93 + .../marvell,mvebu-sdram-controller.yaml | 31 + .../memory-controllers/mediatek,mt7621-memc.yaml | 32 + .../memory-controllers/mediatek,smi-common.yaml | 182 + .../memory-controllers/mediatek,smi-larb.yaml | 139 + .../bindings/memory-controllers/mvebu-devbus.txt | 177 + .../memory-controllers/nvidia,tegra124-emc.yaml | 549 ++ .../memory-controllers/nvidia,tegra124-mc.yaml | 157 + .../memory-controllers/nvidia,tegra186-mc.yaml | 276 + .../memory-controllers/nvidia,tegra20-emc.yaml | 249 + .../memory-controllers/nvidia,tegra20-mc.yaml | 79 + .../memory-controllers/nvidia,tegra210-emc.yaml | 82 + .../memory-controllers/nvidia,tegra30-emc.yaml | 355 + .../memory-controllers/nvidia,tegra30-mc.yaml | 172 + .../qca,ath79-ddr-controller.yaml | 61 + .../bindings/memory-controllers/renesas,dbsc.yaml | 56 + .../memory-controllers/renesas,rpc-if.yaml | 139 + .../memory-controllers/rockchip,rk3399-dmc.yaml | 384 + .../memory-controllers/samsung,exynos5422-dmc.yaml | 139 + .../memory-controllers/snps,dw-umctl2-ddrc.yaml | 118 + .../memory-controllers/st,stm32-fmc2-ebi.yaml | 254 + .../memory-controllers/ti,da8xx-ddrctl.yaml | 35 + .../bindings/memory-controllers/ti,gpmc-child.yaml | 245 + .../bindings/memory-controllers/ti,gpmc.yaml | 190 + .../bindings/memory-controllers/ti-aemif.txt | 210 + .../bindings/memory-controllers/ti/emif.txt | 84 + .../memory-controllers/xlnx,zynq-ddrc-a05.yaml | 38 + Documentation/devicetree/bindings/mfd/88pm860x.txt | 85 + Documentation/devicetree/bindings/mfd/act8945a.txt | 82 + .../devicetree/bindings/mfd/actions,atc260x.yaml | 183 + .../bindings/mfd/allwinner,sun4i-a10-ts.yaml | 76 + .../bindings/mfd/allwinner,sun6i-a31-prcm.yaml | 259 + .../bindings/mfd/allwinner,sun8i-a23-prcm.yaml | 210 + .../devicetree/bindings/mfd/altera-a10sr.txt | 56 + Documentation/devicetree/bindings/mfd/as3711.txt | 73 + Documentation/devicetree/bindings/mfd/as3722.txt | 214 + .../bindings/mfd/aspeed,ast2x00-scu.yaml | 110 + .../devicetree/bindings/mfd/aspeed-gfx.txt | 17 + .../devicetree/bindings/mfd/aspeed-lpc.yaml | 199 + .../devicetree/bindings/mfd/atmel-flexcom.txt | 63 + .../devicetree/bindings/mfd/atmel-gpbr.txt | 17 + .../devicetree/bindings/mfd/atmel-hlcdc.txt | 55 + .../devicetree/bindings/mfd/atmel-matrix.txt | 25 + .../devicetree/bindings/mfd/atmel-smc.txt | 21 + Documentation/devicetree/bindings/mfd/bfticu.txt | 24 + .../devicetree/bindings/mfd/brcm,bcm59056.txt | 39 + .../bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml | 177 + .../bindings/mfd/brcm,bcm63268-gpio-sysctl.yaml | 194 + .../bindings/mfd/brcm,bcm6328-gpio-sysctl.yaml | 162 + .../bindings/mfd/brcm,bcm6358-gpio-sysctl.yaml | 130 + .../bindings/mfd/brcm,bcm6362-gpio-sysctl.yaml | 236 + .../bindings/mfd/brcm,bcm6368-gpio-sysctl.yaml | 246 + .../devicetree/bindings/mfd/brcm,cru.yaml | 108 + .../devicetree/bindings/mfd/brcm,iproc-cdru.txt | 16 + .../devicetree/bindings/mfd/brcm,iproc-mhb.txt | 18 + .../devicetree/bindings/mfd/brcm,misc.yaml | 60 + .../devicetree/bindings/mfd/brcm,twd.yaml | 61 + .../bindings/mfd/canaan,k210-sysctl.yaml | 109 + .../devicetree/bindings/mfd/cirrus,lochnagar.yaml | 365 + .../devicetree/bindings/mfd/cirrus,madera.yaml | 297 + .../devicetree/bindings/mfd/da9052-i2c.txt | 67 + Documentation/devicetree/bindings/mfd/da9055.txt | 70 + Documentation/devicetree/bindings/mfd/da9062.txt | 123 + Documentation/devicetree/bindings/mfd/da9150.txt | 60 + .../devicetree/bindings/mfd/delta,tn48m-cpld.yaml | 90 + .../devicetree/bindings/mfd/dlg,da9063.yaml | 133 + .../devicetree/bindings/mfd/ene-kb3930.yaml | 55 + .../devicetree/bindings/mfd/ene-kb930.yaml | 65 + .../devicetree/bindings/mfd/fsl,imx8qxp-csr.yaml | 192 + .../devicetree/bindings/mfd/fsl-imx25-tsadc.txt | 47 + .../devicetree/bindings/mfd/gateworks-gsc.yaml | 203 + .../devicetree/bindings/mfd/google,cros-ec.yaml | 225 + Documentation/devicetree/bindings/mfd/hi6421.txt | 40 + .../bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml | 137 + .../devicetree/bindings/mfd/hisilicon,hi655x.txt | 33 + Documentation/devicetree/bindings/mfd/iqs62x.yaml | 179 + .../devicetree/bindings/mfd/khadas,mcu.yaml | 44 + .../devicetree/bindings/mfd/kontron,sl28cpld.yaml | 153 + Documentation/devicetree/bindings/mfd/lp3943.txt | 33 + Documentation/devicetree/bindings/mfd/lp873x.txt | 67 + Documentation/devicetree/bindings/mfd/max77620.txt | 162 + .../devicetree/bindings/mfd/max77650.yaml | 151 + Documentation/devicetree/bindings/mfd/max8925.txt | 64 + Documentation/devicetree/bindings/mfd/max8998.txt | 125 + .../devicetree/bindings/mfd/maxim,max14577.yaml | 196 + .../devicetree/bindings/mfd/maxim,max77686.yaml | 132 + .../devicetree/bindings/mfd/maxim,max77693.yaml | 143 + .../devicetree/bindings/mfd/maxim,max77714.yaml | 68 + .../devicetree/bindings/mfd/maxim,max77802.yaml | 194 + .../devicetree/bindings/mfd/maxim,max77843.yaml | 145 + Documentation/devicetree/bindings/mfd/mc13xxx.txt | 156 + .../devicetree/bindings/mfd/mediatek,mt6360.yaml | 256 + .../devicetree/bindings/mfd/mediatek,mt6370.yaml | 280 + .../bindings/mfd/mediatek,mt8195-scpsys.yaml | 68 + Documentation/devicetree/bindings/mfd/mfd.txt | 51 + .../devicetree/bindings/mfd/motorola-cpcap.txt | 72 + .../devicetree/bindings/mfd/mps,mp2629.yaml | 64 + .../devicetree/bindings/mfd/mscc,ocelot.yaml | 160 + Documentation/devicetree/bindings/mfd/mt6397.txt | 110 + .../devicetree/bindings/mfd/mxs-lradc.txt | 45 + .../devicetree/bindings/mfd/netronix,ntxec.yaml | 76 + .../devicetree/bindings/mfd/omap-usb-host.txt | 103 + .../devicetree/bindings/mfd/omap-usb-tll.txt | 27 + Documentation/devicetree/bindings/mfd/palmas.txt | 52 + .../devicetree/bindings/mfd/qcom,pm8008.yaml | 128 + .../devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 296 + .../devicetree/bindings/mfd/qcom,tcsr.yaml | 54 + .../devicetree/bindings/mfd/qcom-pm8xxx.yaml | 55 + Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 283 + Documentation/devicetree/bindings/mfd/qriox.txt | 17 + Documentation/devicetree/bindings/mfd/retu.txt | 24 + .../devicetree/bindings/mfd/richtek,rt4831.yaml | 90 + .../devicetree/bindings/mfd/richtek,rt5120.yaml | 178 + .../devicetree/bindings/mfd/ricoh,rn5t618.yaml | 111 + .../devicetree/bindings/mfd/rockchip,rk805.yaml | 219 + .../devicetree/bindings/mfd/rockchip,rk808.yaml | 257 + .../devicetree/bindings/mfd/rockchip,rk809.yaml | 284 + .../devicetree/bindings/mfd/rockchip,rk817.yaml | 382 + .../devicetree/bindings/mfd/rockchip,rk818.yaml | 282 + .../devicetree/bindings/mfd/rohm,bd71815-pmic.yaml | 201 + .../devicetree/bindings/mfd/rohm,bd71828-pmic.yaml | 204 + .../devicetree/bindings/mfd/rohm,bd71837-pmic.yaml | 244 + .../devicetree/bindings/mfd/rohm,bd71847-pmic.yaml | 229 + .../devicetree/bindings/mfd/rohm,bd9571mwv.yaml | 127 + .../devicetree/bindings/mfd/rohm,bd9576-pmic.yaml | 123 + .../bindings/mfd/samsung,exynos5433-lpass.yaml | 117 + .../devicetree/bindings/mfd/samsung,s2mpa01.yaml | 91 + .../devicetree/bindings/mfd/samsung,s2mps11.yaml | 267 + .../devicetree/bindings/mfd/samsung,s5m8767.yaml | 307 + .../devicetree/bindings/mfd/silergy,sy7636a.yaml | 83 + Documentation/devicetree/bindings/mfd/sky81452.txt | 35 + .../devicetree/bindings/mfd/sprd,sc27xx-pmic.txt | 40 + .../bindings/mfd/sprd,ums512-glbreg.yaml | 71 + .../devicetree/bindings/mfd/st,stm32-lptimer.yaml | 145 + .../devicetree/bindings/mfd/st,stm32-timers.yaml | 176 + .../devicetree/bindings/mfd/st,stmfx.yaml | 122 + .../devicetree/bindings/mfd/st,stpmic1.yaml | 334 + .../devicetree/bindings/mfd/stericsson,ab8500.yaml | 522 ++ .../bindings/mfd/stericsson,db8500-prcmu.yaml | 279 + Documentation/devicetree/bindings/mfd/stmpe.txt | 42 + Documentation/devicetree/bindings/mfd/syscon.yaml | 118 + Documentation/devicetree/bindings/mfd/tc3589x.txt | 107 + .../devicetree/bindings/mfd/ti,am3359-tscadc.yaml | 84 + .../bindings/mfd/ti,j721e-system-controller.yaml | 101 + .../devicetree/bindings/mfd/ti,lp87524-q1.yaml | 116 + .../devicetree/bindings/mfd/ti,lp87561-q1.yaml | 87 + .../devicetree/bindings/mfd/ti,lp87565-q1.yaml | 105 + .../devicetree/bindings/mfd/ti,tps65086.yaml | 125 + .../bindings/mfd/ti-keystone-devctrl.txt | 19 + Documentation/devicetree/bindings/mfd/ti-lmu.txt | 269 + Documentation/devicetree/bindings/mfd/tps6105x.txt | 62 + Documentation/devicetree/bindings/mfd/tps6507x.txt | 91 + Documentation/devicetree/bindings/mfd/tps65910.txt | 205 + Documentation/devicetree/bindings/mfd/tps65912.txt | 49 + .../devicetree/bindings/mfd/twl-family.txt | 46 + .../devicetree/bindings/mfd/twl4030-audio.txt | 46 + .../devicetree/bindings/mfd/twl4030-power.txt | 48 + Documentation/devicetree/bindings/mfd/twl6040.txt | 67 + .../devicetree/bindings/mfd/wlf,arizona.yaml | 281 + Documentation/devicetree/bindings/mfd/wm831x.txt | 81 + .../devicetree/bindings/mfd/x-powers,ac100.yaml | 116 + .../devicetree/bindings/mfd/x-powers,axp152.yaml | 404 + .../devicetree/bindings/mfd/xylon,logicvc.yaml | 63 + .../devicetree/bindings/mfd/zii,rave-sp.txt | 39 + .../devicetree/bindings/mips/ath79-soc.txt | 21 + .../devicetree/bindings/mips/brcm/brcm,bmips.txt | 8 + .../devicetree/bindings/mips/brcm/soc.txt | 166 + .../devicetree/bindings/mips/cavium/bootbus.txt | 126 + .../devicetree/bindings/mips/cavium/cib.txt | 41 + .../devicetree/bindings/mips/cavium/ciu.txt | 26 + .../devicetree/bindings/mips/cavium/ciu2.txt | 27 + .../devicetree/bindings/mips/cavium/ciu3.txt | 27 + .../devicetree/bindings/mips/cavium/dma-engine.txt | 21 + .../devicetree/bindings/mips/cavium/sata-uctl.txt | 42 + .../devicetree/bindings/mips/cavium/uctl.txt | 46 + .../bindings/mips/img/pistachio-marduk.txt | 10 + .../devicetree/bindings/mips/img/pistachio.txt | 42 + .../devicetree/bindings/mips/img/xilfpga.txt | 83 + .../devicetree/bindings/mips/ingenic/devices.yaml | 58 + .../bindings/mips/ingenic/ingenic,cpu.yaml | 69 + .../devicetree/bindings/mips/lantiq/fpi-bus.txt | 31 + .../bindings/mips/lantiq/lantiq,cgu.yaml | 32 + .../bindings/mips/lantiq/lantiq,dma-xway.yaml | 32 + .../bindings/mips/lantiq/lantiq,ebu.yaml | 32 + .../bindings/mips/lantiq/lantiq,pmu.yaml | 32 + .../devicetree/bindings/mips/lantiq/rcu.txt | 69 + .../devicetree/bindings/mips/loongson/devices.yaml | 42 + .../bindings/mips/loongson/ls2k-reset.yaml | 38 + .../bindings/mips/loongson/rs780e-acpi.yaml | 42 + Documentation/devicetree/bindings/mips/mscc.txt | 59 + Documentation/devicetree/bindings/mips/ni.txt | 7 + .../bindings/mips/pic32/microchip,pic32mzda.txt | 31 + Documentation/devicetree/bindings/mips/ralink.yaml | 87 + .../devicetree/bindings/mips/realtek-rtl.yaml | 24 + .../devicetree/bindings/misc/aspeed,cvic.txt | 35 + .../devicetree/bindings/misc/aspeed-p2a-ctrl.txt | 46 + .../devicetree/bindings/misc/atmel-ssc.txt | 50 + .../devicetree/bindings/misc/brcm,kona-smc.txt | 15 + .../bindings/misc/fsl,dpaa2-console.yaml | 26 + .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 196 + .../devicetree/bindings/misc/ge-achc.yaml | 65 + .../devicetree/bindings/misc/idt_89hpesx.txt | 44 + Documentation/devicetree/bindings/misc/ifm-csi.txt | 41 + .../misc/intel,ixp4xx-ahb-queue-manager.yaml | 51 + Documentation/devicetree/bindings/misc/lwn-bk4.txt | 26 + .../bindings/misc/nvidia,tegra186-misc.yaml | 43 + .../bindings/misc/nvidia,tegra20-apbmisc.yaml | 51 + .../devicetree/bindings/misc/olpc,xo1.75-ec.yaml | 56 + .../devicetree/bindings/misc/pvpanic-mmio.txt | 29 + .../devicetree/bindings/misc/qcom,fastrpc.yaml | 144 + .../bindings/misc/qemu,vcpu-stall-detector.yaml | 51 + .../devicetree/bindings/misc/xlnx,sd-fec.txt | 58 + .../bindings/mmc/allwinner,sun4i-a10-mmc.yaml | 115 + .../devicetree/bindings/mmc/amlogic,meson-gx.txt | 39 + .../bindings/mmc/amlogic,meson-mx-sdhc.yaml | 70 + .../bindings/mmc/amlogic,meson-mx-sdio.txt | 54 + .../devicetree/bindings/mmc/arasan,sdhci.yaml | 330 + .../devicetree/bindings/mmc/arm,pl18x.yaml | 244 + .../devicetree/bindings/mmc/aspeed,sdhci.yaml | 106 + .../devicetree/bindings/mmc/atmel-hsmci.txt | 73 + .../devicetree/bindings/mmc/bluefield-dw-mshc.txt | 29 + .../bindings/mmc/brcm,bcm2835-sdhost.txt | 23 + .../devicetree/bindings/mmc/brcm,iproc-sdhci.yaml | 64 + .../devicetree/bindings/mmc/brcm,kona-sdhci.txt | 21 + .../bindings/mmc/brcm,sdhci-brcmstb.yaml | 118 + .../devicetree/bindings/mmc/cavium-mmc.txt | 57 + .../devicetree/bindings/mmc/cdns,sdhci.yaml | 134 + .../devicetree/bindings/mmc/davinci_mmc.txt | 32 + .../devicetree/bindings/mmc/fsl-esdhc.txt | 52 + .../devicetree/bindings/mmc/fsl-imx-esdhc.yaml | 188 + .../devicetree/bindings/mmc/fsl-imx-mmc.yaml | 53 + .../bindings/mmc/hi3798cv200-dw-mshc.txt | 40 + .../devicetree/bindings/mmc/ingenic,mmc.yaml | 107 + .../devicetree/bindings/mmc/k3-dw-mshc.txt | 73 + .../devicetree/bindings/mmc/litex,mmc.yaml | 78 + .../bindings/mmc/marvell,dove-sdhci.yaml | 44 + .../bindings/mmc/marvell,orion-sdio.yaml | 44 + .../bindings/mmc/marvell,xenon-sdhci.yaml | 277 + .../bindings/mmc/microchip,dw-sparx5-sdhci.yaml | 67 + .../bindings/mmc/microchip,sdhci-pic32.txt | 29 + .../devicetree/bindings/mmc/mmc-card.yaml | 48 + .../devicetree/bindings/mmc/mmc-controller.yaml | 388 + .../devicetree/bindings/mmc/mmc-pwrseq-emmc.yaml | 48 + .../devicetree/bindings/mmc/mmc-pwrseq-sd8787.yaml | 43 + .../devicetree/bindings/mmc/mmc-pwrseq-simple.yaml | 64 + .../devicetree/bindings/mmc/mmc-spi-slot.yaml | 75 + Documentation/devicetree/bindings/mmc/mmc.txt | 1 + .../devicetree/bindings/mmc/moxa,moxart-mmc.txt | 30 + Documentation/devicetree/bindings/mmc/mtk-sd.yaml | 258 + Documentation/devicetree/bindings/mmc/mxs-mmc.yaml | 58 + .../bindings/mmc/nvidia,tegra20-sdhci.yaml | 314 + Documentation/devicetree/bindings/mmc/owl-mmc.yaml | 67 + Documentation/devicetree/bindings/mmc/pxa-mmc.txt | 25 + .../devicetree/bindings/mmc/renesas,mmcif.yaml | 135 + .../devicetree/bindings/mmc/renesas,sdhi.yaml | 269 + .../devicetree/bindings/mmc/rockchip-dw-mshc.yaml | 121 + .../bindings/mmc/samsung,exynos-dw-mshc.yaml | 160 + .../bindings/mmc/samsung,s3c6410-sdhci.yaml | 81 + .../devicetree/bindings/mmc/samsung,s3cmci.txt | 42 + .../devicetree/bindings/mmc/sdhci-am654.yaml | 237 + .../devicetree/bindings/mmc/sdhci-atmel.txt | 33 + .../devicetree/bindings/mmc/sdhci-fujitsu.txt | 32 + .../devicetree/bindings/mmc/sdhci-milbeaut.txt | 30 + .../devicetree/bindings/mmc/sdhci-msm.yaml | 258 + .../devicetree/bindings/mmc/sdhci-omap.txt | 43 + .../devicetree/bindings/mmc/sdhci-pxa.yaml | 103 + .../devicetree/bindings/mmc/sdhci-spear.txt | 18 + .../devicetree/bindings/mmc/sdhci-sprd.txt | 67 + Documentation/devicetree/bindings/mmc/sdhci-st.txt | 110 + Documentation/devicetree/bindings/mmc/sdhci.txt | 13 + .../bindings/mmc/snps,dwcmshc-sdhci.yaml | 86 + .../bindings/mmc/socionext,uniphier-sd.yaml | 107 + .../bindings/mmc/synopsys-dw-mshc-common.yaml | 66 + .../devicetree/bindings/mmc/synopsys-dw-mshc.yaml | 75 + .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 134 + Documentation/devicetree/bindings/mmc/ti-omap.txt | 26 + .../devicetree/bindings/mmc/usdhi6rol0.txt | 39 + .../devicetree/bindings/mmc/vt8500-sdmmc.txt | 23 + .../bindings/mtd/allwinner,sun4i-a10-nand.yaml | 96 + .../bindings/mtd/amlogic,meson-nand.yaml | 93 + .../bindings/mtd/arasan,nand-controller.yaml | 61 + .../bindings/mtd/arm,pl353-nand-r2p1.yaml | 53 + .../devicetree/bindings/mtd/atmel-dataflash.txt | 17 + .../devicetree/bindings/mtd/atmel-nand.txt | 237 + .../devicetree/bindings/mtd/brcm,brcmnand.yaml | 234 + .../bindings/mtd/cadence-nand-controller.txt | 53 + .../devicetree/bindings/mtd/davinci-nand.txt | 94 + .../devicetree/bindings/mtd/denali,nand.yaml | 150 + .../devicetree/bindings/mtd/diskonchip.txt | 15 + .../devicetree/bindings/mtd/flctl-nand.txt | 49 + .../devicetree/bindings/mtd/fsl-upm-nand.txt | 67 + .../devicetree/bindings/mtd/fsmc-nand.txt | 60 + .../devicetree/bindings/mtd/gpio-control-nand.txt | 47 + .../devicetree/bindings/mtd/gpmi-nand.yaml | 168 + .../devicetree/bindings/mtd/hisi504-nand.txt | 47 + .../bindings/mtd/hisilicon,fmc-spi-nor.txt | 24 + Documentation/devicetree/bindings/mtd/ibm,ndfc.txt | 39 + .../devicetree/bindings/mtd/ingenic,nand.yaml | 135 + .../devicetree/bindings/mtd/intel,lgm-ebunand.yaml | 99 + .../devicetree/bindings/mtd/jedec,spi-nor.yaml | 109 + .../devicetree/bindings/mtd/lpc32xx-mlc.txt | 50 + .../devicetree/bindings/mtd/lpc32xx-slc.txt | 52 + .../devicetree/bindings/mtd/marvell-nand.txt | 126 + .../bindings/mtd/microchip,mchp23k256.txt | 18 + .../bindings/mtd/microchip,mchp48l640.yaml | 46 + .../devicetree/bindings/mtd/mtd-physmap.yaml | 225 + Documentation/devicetree/bindings/mtd/mtd.yaml | 89 + Documentation/devicetree/bindings/mtd/mtk-nand.txt | 176 + .../devicetree/bindings/mtd/mxc-nand.yaml | 40 + .../devicetree/bindings/mtd/mxic-nand.txt | 36 + .../bindings/mtd/mxicy,nand-ecc-engine.yaml | 77 + .../devicetree/bindings/mtd/nand-chip.yaml | 70 + .../devicetree/bindings/mtd/nand-controller.yaml | 152 + .../devicetree/bindings/mtd/nand-macronix.txt | 27 + .../bindings/mtd/nvidia-tegra20-nand.txt | 64 + .../devicetree/bindings/mtd/nxp-spifi.txt | 58 + .../devicetree/bindings/mtd/orion-nand.txt | 50 + .../devicetree/bindings/mtd/oxnas-nand.txt | 41 + .../devicetree/bindings/mtd/partition.txt | 33 + .../mtd/partitions/arm,arm-firmware-suite.yaml | 28 + .../mtd/partitions/brcm,bcm4908-partitions.yaml | 70 + .../partitions/brcm,bcm947xx-cfe-partitions.yaml | 48 + .../brcm,bcm963xx-cfe-nor-partitions.txt | 24 + .../mtd/partitions/brcm,bcm963xx-imagetag.txt | 45 + .../bindings/mtd/partitions/brcm,trx.txt | 42 + .../bindings/mtd/partitions/fixed-partitions.yaml | 172 + .../mtd/partitions/linksys,ns-partitions.yaml | 74 + .../bindings/mtd/partitions/nvmem-cells.yaml | 99 + .../bindings/mtd/partitions/partition.yaml | 63 + .../bindings/mtd/partitions/qcom,smem-part.yaml | 60 + .../bindings/mtd/partitions/redboot-fis.yaml | 42 + .../devicetree/bindings/mtd/partitions/u-boot.yaml | 49 + .../devicetree/bindings/mtd/qcom,nandc.yaml | 223 + .../devicetree/bindings/mtd/renesas-nandc.yaml | 66 + .../bindings/mtd/rockchip,nand-controller.yaml | 160 + .../devicetree/bindings/mtd/samsung-s3c2410.txt | 56 + .../devicetree/bindings/mtd/spear_smi.txt | 29 + .../devicetree/bindings/mtd/spi-nand.yaml | 28 + .../bindings/mtd/st,stm32-fmc2-nand.yaml | 131 + Documentation/devicetree/bindings/mtd/st-fsm.txt | 25 + .../devicetree/bindings/mtd/ti,am654-hbmc.yaml | 69 + Documentation/devicetree/bindings/mtd/ti,elm.yaml | 72 + .../devicetree/bindings/mtd/ti,gpmc-nand.yaml | 129 + .../devicetree/bindings/mtd/ti,gpmc-onenand.yaml | 81 + .../devicetree/bindings/mtd/vf610-nfc.txt | 59 + .../devicetree/bindings/mux/adi,adg792a.txt | 75 + .../devicetree/bindings/mux/adi,adgs1408.txt | 48 + .../devicetree/bindings/mux/gpio-mux.yaml | 99 + .../devicetree/bindings/mux/mux-consumer.yaml | 67 + .../devicetree/bindings/mux/mux-controller.yaml | 206 + Documentation/devicetree/bindings/mux/reg-mux.yaml | 146 + .../devicetree/bindings/net/actions,owl-emac.yaml | 96 + .../devicetree/bindings/net/adi,adin.yaml | 84 + .../devicetree/bindings/net/adi,adin1110.yaml | 77 + .../bindings/net/allwinner,sun4i-a10-emac.yaml | 58 + .../bindings/net/allwinner,sun4i-a10-mdio.yaml | 68 + .../bindings/net/allwinner,sun7i-a20-gmac.yaml | 66 + .../bindings/net/allwinner,sun8i-a83t-emac.yaml | 319 + .../devicetree/bindings/net/altr,tse.yaml | 168 + Documentation/devicetree/bindings/net/amd-xgbe.txt | 76 + .../bindings/net/amlogic,meson-dwmac.yaml | 176 + .../devicetree/bindings/net/anarion-gmac.txt | 25 + .../devicetree/bindings/net/apm-xgene-enet.txt | 91 + .../devicetree/bindings/net/apm-xgene-mdio.txt | 37 + Documentation/devicetree/bindings/net/arc_emac.txt | 46 + .../devicetree/bindings/net/asix,ax88178.yaml | 68 + .../devicetree/bindings/net/asix,ax88796c.yaml | 73 + .../bindings/net/aspeed,ast2600-mdio.yaml | 53 + .../devicetree/bindings/net/bluetooth.txt | 5 + .../devicetree/bindings/net/brcm,amac.yaml | 88 + .../devicetree/bindings/net/brcm,bcm4908-enet.yaml | 55 + .../bindings/net/brcm,bcm6368-mdio-mux.yaml | 52 + .../bindings/net/brcm,bcm7445-switch-v4.0.txt | 50 + .../devicetree/bindings/net/brcm,bcmgenet.yaml | 145 + .../devicetree/bindings/net/brcm,iproc-mdio.yaml | 38 + .../bindings/net/brcm,mdio-mux-iproc.yaml | 80 + .../devicetree/bindings/net/brcm,systemport.yaml | 86 + .../devicetree/bindings/net/brcm,unimac-mdio.yaml | 85 + .../devicetree/bindings/net/broadcom-bcm87xx.txt | 29 + .../bindings/net/broadcom-bluetooth.yaml | 156 + Documentation/devicetree/bindings/net/btusb.txt | 44 + .../devicetree/bindings/net/calxeda-xgmac.yaml | 49 + .../bindings/net/can/allwinner,sun4i-a10-can.yaml | 78 + .../devicetree/bindings/net/can/atmel-can.txt | 15 + .../devicetree/bindings/net/can/bosch,c_can.yaml | 116 + .../devicetree/bindings/net/can/bosch,m_can.yaml | 152 + .../bindings/net/can/can-controller.yaml | 27 + .../bindings/net/can/can-transceiver.yaml | 20 + .../devicetree/bindings/net/can/cc770.txt | 53 + .../devicetree/bindings/net/can/ctu,ctucanfd.yaml | 66 + .../devicetree/bindings/net/can/fsl,flexcan.yaml | 167 + .../devicetree/bindings/net/can/grcan.txt | 28 + .../devicetree/bindings/net/can/holt_hi311x.txt | 23 + .../devicetree/bindings/net/can/ifi_canfd.txt | 15 + .../bindings/net/can/microchip,mcp251x.txt | 30 + .../bindings/net/can/microchip,mcp251xfd.yaml | 83 + .../bindings/net/can/microchip,mpfs-can.yaml | 45 + .../devicetree/bindings/net/can/mpc5xxx-mscan.txt | 53 + .../devicetree/bindings/net/can/nxp,sja1000.yaml | 136 + .../bindings/net/can/renesas,rcar-can.yaml | 139 + .../bindings/net/can/renesas,rcar-canfd.yaml | 185 + .../devicetree/bindings/net/can/tcan4x5x.txt | 40 + .../devicetree/bindings/net/can/ti_hecc.txt | 32 + .../devicetree/bindings/net/can/xilinx,can.yaml | 161 + .../devicetree/bindings/net/cavium-mdio.txt | 84 + .../devicetree/bindings/net/cavium-mix.txt | 34 + .../devicetree/bindings/net/cavium-pip.txt | 99 + .../devicetree/bindings/net/cdns,macb.yaml | 215 + .../devicetree/bindings/net/cirrus,cs89x0.txt | 13 + .../bindings/net/cortina,gemini-ethernet.yaml | 138 + Documentation/devicetree/bindings/net/cortina.txt | 21 + .../devicetree/bindings/net/cpsw-phy-sel.txt | 30 + Documentation/devicetree/bindings/net/cpsw.txt | 132 + .../devicetree/bindings/net/davicom,dm9051.yaml | 62 + .../devicetree/bindings/net/davicom-dm9000.txt | 27 + .../devicetree/bindings/net/davinci_emac.txt | 44 + .../devicetree/bindings/net/dsa/ar9331.txt | 147 + .../devicetree/bindings/net/dsa/arrow,xrs700x.yaml | 74 + .../devicetree/bindings/net/dsa/brcm,b53.yaml | 264 + .../devicetree/bindings/net/dsa/brcm,sf2.yaml | 171 + .../devicetree/bindings/net/dsa/dsa-port.yaml | 98 + Documentation/devicetree/bindings/net/dsa/dsa.txt | 4 + Documentation/devicetree/bindings/net/dsa/dsa.yaml | 61 + .../bindings/net/dsa/hirschmann,hellcreek.yaml | 132 + .../devicetree/bindings/net/dsa/lan9303.txt | 100 + .../devicetree/bindings/net/dsa/lantiq-gswip.txt | 146 + .../devicetree/bindings/net/dsa/marvell.txt | 109 + .../bindings/net/dsa/mediatek,mt7530.yaml | 804 ++ .../devicetree/bindings/net/dsa/microchip,ksz.yaml | 159 + .../bindings/net/dsa/microchip,lan937x.yaml | 192 + .../devicetree/bindings/net/dsa/mscc,ocelot.yaml | 260 + .../devicetree/bindings/net/dsa/nxp,sja1105.yaml | 174 + .../devicetree/bindings/net/dsa/qca8k.yaml | 306 + .../devicetree/bindings/net/dsa/realtek.yaml | 386 + .../bindings/net/dsa/renesas,rzn1-a5psw.yaml | 158 + .../bindings/net/dsa/vitesse,vsc73xx.txt | 129 + .../devicetree/bindings/net/engleder,tsnep.yaml | 118 + .../bindings/net/ethernet-controller.yaml | 244 + .../devicetree/bindings/net/ethernet-phy.yaml | 223 + Documentation/devicetree/bindings/net/ethernet.txt | 1 + .../devicetree/bindings/net/ezchip_enet.txt | 15 + .../devicetree/bindings/net/faraday,ftmac.txt | 24 + .../devicetree/bindings/net/fixed-link.txt | 1 + Documentation/devicetree/bindings/net/fsl,fec.yaml | 260 + .../devicetree/bindings/net/fsl,fman-dtsec.yaml | 145 + .../bindings/net/fsl,qoriq-mc-dpmac.yaml | 60 + .../devicetree/bindings/net/fsl-enetc.txt | 119 + Documentation/devicetree/bindings/net/fsl-fman.txt | 547 ++ .../devicetree/bindings/net/fsl-tsec-phy.txt | 89 + .../devicetree/bindings/net/ftgmac100.txt | 67 + .../bindings/net/hisilicon-femac-mdio.txt | 22 + .../devicetree/bindings/net/hisilicon-femac.txt | 41 + .../bindings/net/hisilicon-hip04-net.txt | 89 + .../bindings/net/hisilicon-hix5hd2-gmac.txt | 60 + .../devicetree/bindings/net/hisilicon-hns-dsaf.txt | 90 + .../devicetree/bindings/net/hisilicon-hns-mdio.txt | 27 + .../devicetree/bindings/net/hisilicon-hns-nic.txt | 76 + Documentation/devicetree/bindings/net/ibm,emac.txt | 205 + .../devicetree/bindings/net/icplus-ip101ag.txt | 19 + .../devicetree/bindings/net/idt,3243x-emac.yaml | 73 + .../devicetree/bindings/net/ieee802154/adf7242.txt | 18 + .../bindings/net/ieee802154/at86rf230.txt | 27 + .../devicetree/bindings/net/ieee802154/ca8210.txt | 28 + .../devicetree/bindings/net/ieee802154/cc2520.txt | 33 + .../devicetree/bindings/net/ieee802154/mcr20a.txt | 23 + .../bindings/net/ieee802154/mrf24j40.txt | 20 + .../devicetree/bindings/net/ingenic,mac.yaml | 77 + .../devicetree/bindings/net/intel,dwmac-plat.yaml | 131 + .../bindings/net/intel,ixp46x-ptp-timer.yaml | 54 + .../bindings/net/intel,ixp4xx-ethernet.yaml | 109 + .../devicetree/bindings/net/intel,ixp4xx-hss.yaml | 123 + .../devicetree/bindings/net/ipq806x-dwmac.txt | 35 + .../devicetree/bindings/net/keystone-netcp.txt | 265 + .../devicetree/bindings/net/lantiq,etop-xway.yaml | 68 + .../devicetree/bindings/net/lantiq,xrx200-net.yaml | 58 + .../devicetree/bindings/net/litex,liteeth.yaml | 99 + Documentation/devicetree/bindings/net/lpc-eth.txt | 28 + .../devicetree/bindings/net/marvell,mvusb.yaml | 66 + .../bindings/net/marvell,orion-mdio.yaml | 60 + .../devicetree/bindings/net/marvell,prestera.txt | 81 + .../bindings/net/marvell-armada-370-neta.txt | 50 + .../devicetree/bindings/net/marvell-bluetooth.yaml | 31 + .../devicetree/bindings/net/marvell-bt-8xxx.txt | 83 + .../devicetree/bindings/net/marvell-neta-bm.txt | 47 + .../devicetree/bindings/net/marvell-orion-net.txt | 83 + .../devicetree/bindings/net/marvell-pp2.txt | 141 + .../devicetree/bindings/net/marvell-pxa168.txt | 38 + .../devicetree/bindings/net/maxim,ds26522.txt | 13 + .../bindings/net/mctp-i2c-controller.yaml | 92 + .../devicetree/bindings/net/mdio-gpio.yaml | 57 + .../devicetree/bindings/net/mdio-mux-gpio.yaml | 135 + .../bindings/net/mdio-mux-meson-g12a.txt | 48 + .../devicetree/bindings/net/mdio-mux-mmioreg.yaml | 78 + .../bindings/net/mdio-mux-multiplexer.yaml | 82 + .../devicetree/bindings/net/mdio-mux.yaml | 41 + Documentation/devicetree/bindings/net/mdio.txt | 1 + Documentation/devicetree/bindings/net/mdio.yaml | 116 + .../devicetree/bindings/net/mediatek,net.yaml | 446 ++ .../bindings/net/mediatek,star-emac.yaml | 107 + .../devicetree/bindings/net/mediatek-bluetooth.txt | 116 + .../devicetree/bindings/net/mediatek-dwmac.yaml | 184 + .../devicetree/bindings/net/micrel,ks8851.yaml | 96 + .../devicetree/bindings/net/micrel-ks8995.txt | 20 + .../devicetree/bindings/net/micrel-ksz90x1.txt | 227 + Documentation/devicetree/bindings/net/micrel.txt | 57 + .../devicetree/bindings/net/microchip,enc28j60.txt | 56 + .../devicetree/bindings/net/microchip,lan78xx.txt | 53 + .../devicetree/bindings/net/microchip,lan95xx.yaml | 63 + .../bindings/net/microchip,lan966x-switch.yaml | 171 + .../bindings/net/microchip,sparx5-switch.yaml | 212 + .../devicetree/bindings/net/mscc,miim.yaml | 61 + .../bindings/net/mscc,vsc7514-switch.yaml | 191 + .../devicetree/bindings/net/mscc-phy-vsc8531.txt | 73 + .../devicetree/bindings/net/nfc/marvell,nci.yaml | 170 + .../devicetree/bindings/net/nfc/nxp,nci.yaml | 60 + .../devicetree/bindings/net/nfc/nxp,pn532.yaml | 65 + .../devicetree/bindings/net/nfc/nxp,pn544.yaml | 58 + .../bindings/net/nfc/samsung,s3fwrn5.yaml | 99 + .../devicetree/bindings/net/nfc/st,st-nci.yaml | 105 + .../devicetree/bindings/net/nfc/st,st21nfca.yaml | 64 + .../devicetree/bindings/net/nfc/st,st95hf.yaml | 58 + .../devicetree/bindings/net/nfc/ti,trf7970a.yaml | 99 + Documentation/devicetree/bindings/net/nixge.txt | 92 + .../devicetree/bindings/net/nokia-bluetooth.txt | 51 + .../bindings/net/nvidia,tegra234-mgbe.yaml | 162 + .../devicetree/bindings/net/nxp,dwmac-imx.yaml | 96 + .../devicetree/bindings/net/nxp,lpc1850-dwmac.txt | 20 + .../devicetree/bindings/net/nxp,tja11xx.yaml | 80 + .../devicetree/bindings/net/opencores-ethoc.txt | 22 + .../devicetree/bindings/net/oxnas-dwmac.txt | 41 + .../bindings/net/pcs/renesas,rzn1-miic.yaml | 171 + Documentation/devicetree/bindings/net/phy.txt | 1 + .../bindings/net/pse-pd/podl-pse-regulator.yaml | 40 + .../bindings/net/pse-pd/pse-controller.yaml | 33 + .../devicetree/bindings/net/qca,ar71xx.yaml | 195 + .../devicetree/bindings/net/qca,ar803x.yaml | 132 + .../devicetree/bindings/net/qca,qca7000.txt | 87 + .../devicetree/bindings/net/qcom,bam-dmux.yaml | 92 + .../devicetree/bindings/net/qcom,ethqos.txt | 66 + .../devicetree/bindings/net/qcom,ipa.yaml | 242 + .../devicetree/bindings/net/qcom,ipq4019-mdio.yaml | 76 + .../devicetree/bindings/net/qcom,ipq8064-mdio.yaml | 59 + .../devicetree/bindings/net/qcom-emac.txt | 111 + .../bindings/net/qualcomm-bluetooth.yaml | 183 + .../devicetree/bindings/net/realtek,rtl82xx.yaml | 45 + .../devicetree/bindings/net/realtek-bluetooth.yaml | 58 + .../devicetree/bindings/net/renesas,ether.yaml | 130 + .../devicetree/bindings/net/renesas,etheravb.yaml | 357 + .../devicetree/bindings/net/rockchip,emac.yaml | 115 + .../devicetree/bindings/net/rockchip-dwmac.yaml | 137 + .../devicetree/bindings/net/samsung-sxgbe.txt | 52 + Documentation/devicetree/bindings/net/sff,sfp.yaml | 142 + .../devicetree/bindings/net/smsc,lan9115.yaml | 110 + .../devicetree/bindings/net/smsc,lan91c111.yaml | 61 + .../devicetree/bindings/net/smsc-lan87xx.txt | 27 + .../bindings/net/snps,dwc-qos-ethernet.txt | 168 + .../devicetree/bindings/net/snps,dwmac.yaml | 533 ++ .../devicetree/bindings/net/socfpga-dwmac.txt | 57 + .../bindings/net/socionext,uniphier-ave4.yaml | 138 + .../devicetree/bindings/net/socionext-netsec.txt | 56 + .../devicetree/bindings/net/sti-dwmac.txt | 60 + .../devicetree/bindings/net/stm32-dwmac.yaml | 163 + Documentation/devicetree/bindings/net/stmmac.txt | 1 + .../bindings/net/sunplus,sp7021-emac.yaml | 143 + .../devicetree/bindings/net/ti,bluetooth.yaml | 92 + .../devicetree/bindings/net/ti,cpsw-switch.yaml | 242 + .../devicetree/bindings/net/ti,davinci-mdio.yaml | 80 + .../devicetree/bindings/net/ti,dp83822.yaml | 82 + .../devicetree/bindings/net/ti,dp83867.yaml | 141 + .../devicetree/bindings/net/ti,dp83869.yaml | 100 + .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 279 + .../devicetree/bindings/net/ti,k3-am654-cpts.yaml | 145 + .../bindings/net/toshiba,visconti-dwmac.yaml | 86 + .../devicetree/bindings/net/vertexcom-mse102x.yaml | 71 + .../devicetree/bindings/net/via-rhine.txt | 17 + .../devicetree/bindings/net/via-velocity.txt | 20 + .../bindings/net/wireless/brcm,bcm4329-fmac.yaml | 150 + .../bindings/net/wireless/esp,esp8089.yaml | 43 + .../bindings/net/wireless/ieee80211.yaml | 45 + .../bindings/net/wireless/marvell-8xxx.txt | 68 + .../bindings/net/wireless/mediatek,mt76.yaml | 286 + .../bindings/net/wireless/microchip,wilc1000.yaml | 95 + .../bindings/net/wireless/qca,ath9k.yaml | 90 + .../bindings/net/wireless/qcom,ath10k.txt | 215 + .../bindings/net/wireless/qcom,ath11k.yaml | 468 ++ .../bindings/net/wireless/silabs,wfx.yaml | 133 + .../devicetree/bindings/net/wireless/ti,wl1251.txt | 64 + .../bindings/net/wireless/ti,wlcore.yaml | 136 + .../devicetree/bindings/net/wiznet,w5x00.txt | 50 + .../devicetree/bindings/net/xilinx_axienet.txt | 99 + .../devicetree/bindings/net/xilinx_gmii2rgmii.txt | 35 + .../devicetree/bindings/net/xlnx,emaclite.yaml | 63 + Documentation/devicetree/bindings/nios2/nios2.txt | 62 + Documentation/devicetree/bindings/numa.txt | 319 + .../devicetree/bindings/nvme/apple,nvme-ans.yaml | 110 + .../bindings/nvmem/allwinner,sun4i-a10-sid.yaml | 53 + .../devicetree/bindings/nvmem/amlogic-efuse.txt | 48 + .../bindings/nvmem/amlogic-meson-mx-efuse.txt | 22 + .../devicetree/bindings/nvmem/apple,efuses.yaml | 50 + .../devicetree/bindings/nvmem/brcm,nvram.yaml | 58 + .../devicetree/bindings/nvmem/brcm,ocotp.txt | 17 + .../bindings/nvmem/fsl,layerscape-sfp.yaml | 62 + .../devicetree/bindings/nvmem/fsl,scu-ocotp.yaml | 56 + .../devicetree/bindings/nvmem/imx-iim.yaml | 57 + .../devicetree/bindings/nvmem/imx-ocotp.yaml | 105 + .../bindings/nvmem/ingenic,jz4780-efuse.yaml | 45 + .../devicetree/bindings/nvmem/lpc1850-otp.txt | 20 + .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 + .../devicetree/bindings/nvmem/mediatek,efuse.yaml | 90 + .../bindings/nvmem/microchip,lan9662-otpc.yaml | 45 + .../bindings/nvmem/microchip,sama7g5-otpc.yaml | 50 + .../devicetree/bindings/nvmem/mxs-ocotp.yaml | 52 + .../devicetree/bindings/nvmem/nintendo-otp.yaml | 44 + .../devicetree/bindings/nvmem/nvmem-consumer.yaml | 45 + Documentation/devicetree/bindings/nvmem/nvmem.txt | 1 + Documentation/devicetree/bindings/nvmem/nvmem.yaml | 99 + .../devicetree/bindings/nvmem/qcom,qfprom.yaml | 116 + .../devicetree/bindings/nvmem/qcom,spmi-sdam.yaml | 58 + Documentation/devicetree/bindings/nvmem/rmem.yaml | 52 + .../devicetree/bindings/nvmem/rockchip-efuse.yaml | 72 + .../devicetree/bindings/nvmem/rockchip-otp.txt | 25 + .../devicetree/bindings/nvmem/sc27xx-efuse.txt | 52 + .../devicetree/bindings/nvmem/snvs-lpgpr.yaml | 37 + .../bindings/nvmem/socionext,uniphier-efuse.yaml | 95 + .../devicetree/bindings/nvmem/sprd-efuse.txt | 39 + .../devicetree/bindings/nvmem/st,stm32-romem.yaml | 68 + .../bindings/nvmem/sunplus,sp7021-ocotp.yaml | 84 + .../devicetree/bindings/nvmem/u-boot,env.yaml | 75 + .../devicetree/bindings/nvmem/vf610-ocotp.txt | 19 + .../bindings/nvmem/xlnx,zynqmp-nvmem.txt | 46 + .../bindings/nvmem/zii,rave-sp-eeprom.txt | 40 + .../bindings/openrisc/opencores/or1ksim.txt | 39 + .../opp/allwinner,sun50i-h6-operating-points.yaml | 135 + Documentation/devicetree/bindings/opp/opp-v1.yaml | 51 + .../devicetree/bindings/opp/opp-v2-base.yaml | 249 + .../devicetree/bindings/opp/opp-v2-kryo-cpu.yaml | 269 + .../devicetree/bindings/opp/opp-v2-qcom-level.yaml | 61 + Documentation/devicetree/bindings/opp/opp-v2.yaml | 475 ++ .../bindings/opp/ti-omap5-opp-supply.txt | 63 + .../devicetree/bindings/pci/83xx-512x-pci.txt | 39 + .../devicetree/bindings/pci/aardvark-pci.txt | 59 + .../devicetree/bindings/pci/altera-pcie-msi.txt | 27 + .../devicetree/bindings/pci/altera-pcie.txt | 50 + .../devicetree/bindings/pci/amlogic,meson-pcie.txt | 70 + .../devicetree/bindings/pci/apple,pcie.yaml | 174 + .../devicetree/bindings/pci/axis,artpec6-pcie.txt | 50 + .../devicetree/bindings/pci/brcm,iproc-pcie.yaml | 184 + .../devicetree/bindings/pci/brcm,stb-pcie.yaml | 185 + .../devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml | 50 + .../bindings/pci/cdns,cdns-pcie-host.yaml | 75 + .../devicetree/bindings/pci/cdns-pcie-ep.yaml | 24 + .../devicetree/bindings/pci/cdns-pcie-host.yaml | 37 + .../devicetree/bindings/pci/cdns-pcie.yaml | 25 + .../devicetree/bindings/pci/faraday,ftpci100.yaml | 174 + .../devicetree/bindings/pci/fsl,imx6q-pcie.yaml | 248 + Documentation/devicetree/bindings/pci/fsl,pci.txt | 27 + .../bindings/pci/hisilicon,kirin-pcie.yaml | 180 + .../bindings/pci/hisilicon-histb-pcie.txt | 69 + .../devicetree/bindings/pci/host-generic-pci.yaml | 177 + .../devicetree/bindings/pci/intel,ixp4xx-pci.yaml | 100 + .../bindings/pci/intel,keembay-pcie-ep.yaml | 69 + .../bindings/pci/intel,keembay-pcie.yaml | 97 + .../devicetree/bindings/pci/intel-gw-pcie.yaml | 117 + .../devicetree/bindings/pci/layerscape-pci.txt | 79 + .../bindings/pci/layerscape-pcie-gen4.txt | 52 + .../devicetree/bindings/pci/loongson.yaml | 63 + .../bindings/pci/mediatek,mt7621-pcie.yaml | 145 + .../devicetree/bindings/pci/mediatek-pcie-cfg.yaml | 39 + .../bindings/pci/mediatek-pcie-gen3.yaml | 193 + .../devicetree/bindings/pci/mediatek-pcie.txt | 289 + .../bindings/pci/microchip,pcie-host.yaml | 140 + .../devicetree/bindings/pci/mobiveil-pcie.txt | 72 + .../devicetree/bindings/pci/mvebu-pci.txt | 310 + .../bindings/pci/nvidia,tegra194-pcie-ep.yaml | 319 + .../bindings/pci/nvidia,tegra194-pcie.yaml | 350 + .../bindings/pci/nvidia,tegra20-pcie.txt | 670 ++ .../devicetree/bindings/pci/pci-armada8k.txt | 48 + Documentation/devicetree/bindings/pci/pci-ep.yaml | 47 + .../devicetree/bindings/pci/pci-iommu.txt | 171 + Documentation/devicetree/bindings/pci/pci-msi.txt | 220 + Documentation/devicetree/bindings/pci/pci.txt | 84 + Documentation/devicetree/bindings/pci/pcie-al.txt | 46 + .../devicetree/bindings/pci/qcom,pcie-ep.yaml | 202 + .../devicetree/bindings/pci/qcom,pcie.yaml | 825 ++ .../devicetree/bindings/pci/ralink,rt3883-pci.txt | 187 + .../devicetree/bindings/pci/rcar-pci-ep.yaml | 93 + .../devicetree/bindings/pci/rcar-pci-host.yaml | 125 + .../bindings/pci/renesas,pci-rcar-gen2.yaml | 186 + .../devicetree/bindings/pci/rockchip-dw-pcie.yaml | 131 + .../devicetree/bindings/pci/rockchip-pcie-ep.txt | 62 + .../devicetree/bindings/pci/rockchip-pcie-host.txt | 135 + .../bindings/pci/samsung,exynos-pcie.yaml | 119 + .../devicetree/bindings/pci/sifive,fu740-pcie.yaml | 120 + .../devicetree/bindings/pci/snps,dw-pcie-ep.yaml | 88 + .../devicetree/bindings/pci/snps,dw-pcie.yaml | 104 + .../bindings/pci/socionext,uniphier-pcie-ep.yaml | 108 + .../bindings/pci/socionext,uniphier-pcie.yaml | 117 + .../devicetree/bindings/pci/spear13xx-pcie.txt | 14 + .../devicetree/bindings/pci/ti,am65-pci-ep.yaml | 76 + .../devicetree/bindings/pci/ti,am65-pci-host.yaml | 106 + .../devicetree/bindings/pci/ti,j721e-pci-ep.yaml | 103 + .../devicetree/bindings/pci/ti,j721e-pci-host.yaml | 137 + Documentation/devicetree/bindings/pci/ti-pci.txt | 102 + .../bindings/pci/toshiba,visconti-pcie.yaml | 111 + .../devicetree/bindings/pci/v3-v360epc-pci.txt | 76 + .../devicetree/bindings/pci/versatile.yaml | 94 + .../devicetree/bindings/pci/xgene-pci-msi.txt | 68 + .../devicetree/bindings/pci/xgene-pci.txt | 50 + .../devicetree/bindings/pci/xilinx-nwl-pcie.txt | 73 + .../devicetree/bindings/pci/xilinx-pcie.txt | 88 + .../devicetree/bindings/pci/xilinx-versal-cpm.yaml | 134 + .../devicetree/bindings/peci/peci-aspeed.yaml | 72 + .../devicetree/bindings/peci/peci-controller.yaml | 33 + .../devicetree/bindings/perf/apm-xgene-pmu.txt | 112 + .../devicetree/bindings/perf/arm,ccn.yaml | 40 + .../devicetree/bindings/perf/arm,cmn.yaml | 69 + .../devicetree/bindings/perf/arm,dsu-pmu.yaml | 47 + .../devicetree/bindings/perf/arm,smmu-v3-pmcg.yaml | 70 + .../devicetree/bindings/perf/fsl-imx-ddr.yaml | 52 + .../bindings/perf/marvell-cn10k-ddr.yaml | 37 + .../bindings/perf/marvell-cn10k-tad.yaml | 63 + .../devicetree/bindings/perf/spe-pmu.yaml | 40 + .../bindings/phy/allwinner,sun4i-a10-usb-phy.yaml | 107 + .../bindings/phy/allwinner,sun50i-a64-usb-phy.yaml | 110 + .../bindings/phy/allwinner,sun50i-h6-usb-phy.yaml | 107 + .../bindings/phy/allwinner,sun50i-h6-usb3-phy.yaml | 49 + .../bindings/phy/allwinner,sun5i-a13-usb-phy.yaml | 95 + .../phy/allwinner,sun6i-a31-mipi-dphy.yaml | 73 + .../bindings/phy/allwinner,sun6i-a31-usb-phy.yaml | 121 + .../bindings/phy/allwinner,sun8i-a23-usb-phy.yaml | 104 + .../bindings/phy/allwinner,sun8i-a83t-usb-phy.yaml | 124 + .../bindings/phy/allwinner,sun8i-h3-usb-phy.yaml | 141 + .../bindings/phy/allwinner,sun8i-r40-usb-phy.yaml | 121 + .../bindings/phy/allwinner,sun8i-v3s-usb-phy.yaml | 88 + .../bindings/phy/allwinner,sun9i-a80-usb-phy.yaml | 132 + .../bindings/phy/amlogic,axg-mipi-dphy.yaml | 70 + .../phy/amlogic,g12a-mipi-dphy-analog.yaml | 35 + .../bindings/phy/amlogic,g12a-usb2-phy.yaml | 78 + .../bindings/phy/amlogic,g12a-usb3-pcie-phy.yaml | 59 + .../phy/amlogic,meson-axg-mipi-pcie-analog.yaml | 40 + .../bindings/phy/amlogic,meson-axg-pcie.yaml | 52 + .../bindings/phy/amlogic,meson8-hdmi-tx-phy.yaml | 65 + .../bindings/phy/amlogic,meson8b-usb2-phy.yaml | 64 + .../devicetree/bindings/phy/apm-xgene-phy.txt | 76 + .../devicetree/bindings/phy/bcm-ns-usb2-phy.yaml | 72 + .../devicetree/bindings/phy/bcm-ns-usb3-phy.yaml | 62 + .../devicetree/bindings/phy/berlin-sata-phy.txt | 36 + .../devicetree/bindings/phy/berlin-usb-phy.txt | 16 + .../bindings/phy/brcm,bcm63xx-usbh-phy.yaml | 78 + .../bindings/phy/brcm,brcmstb-usb-phy.yaml | 196 + .../bindings/phy/brcm,cygnus-pcie-phy.yaml | 77 + .../devicetree/bindings/phy/brcm,kona-usb2-phy.txt | 15 + .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt | 30 + .../devicetree/bindings/phy/brcm,ns2-pcie-phy.yaml | 41 + .../devicetree/bindings/phy/brcm,sata-phy.yaml | 144 + .../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41 + .../bindings/phy/brcm,stingray-usb-phy.txt | 32 + .../devicetree/bindings/phy/calxeda-combophy.yaml | 50 + .../devicetree/bindings/phy/cdns,dphy-rx.yaml | 42 + .../devicetree/bindings/phy/cdns,dphy.yaml | 57 + .../devicetree/bindings/phy/cdns,salvo-phy.yaml | 52 + .../devicetree/bindings/phy/dm816x-phy.txt | 24 + .../devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml | 92 + .../bindings/phy/fsl,imx8mq-usb-phy.yaml | 53 + .../bindings/phy/fsl,imx8qm-lvds-phy.yaml | 61 + .../devicetree/bindings/phy/fsl,lynx-28g.yaml | 40 + .../bindings/phy/hisilicon,hi3660-usb3.yaml | 50 + .../bindings/phy/hisilicon,hi3670-usb3.yaml | 63 + .../bindings/phy/hisilicon,phy-hi3670-pcie.yaml | 82 + .../devicetree/bindings/phy/hix5hd2-phy.txt | 22 + .../devicetree/bindings/phy/ingenic,phy-usb.yaml | 58 + .../devicetree/bindings/phy/intel,combo-phy.yaml | 109 + .../bindings/phy/intel,keembay-phy-usb.yaml | 44 + .../bindings/phy/intel,lgm-emmc-phy.yaml | 75 + .../devicetree/bindings/phy/intel,lgm-usb-phy.yaml | 58 + .../bindings/phy/intel,phy-thunderbay-emmc.yaml | 46 + .../devicetree/bindings/phy/keystone-usb-phy.txt | 19 + .../bindings/phy/lantiq,vrx200-pcie-phy.yaml | 95 + .../bindings/phy/marvell,armada-3700-utmi-phy.yaml | 57 + .../phy/marvell,armada-cp110-utmi-phy.yaml | 109 + .../bindings/phy/marvell,mmp3-hsic-phy.yaml | 37 + .../bindings/phy/marvell,mmp3-usb-phy.yaml | 42 + .../devicetree/bindings/phy/mediatek,dsi-phy.yaml | 92 + .../devicetree/bindings/phy/mediatek,hdmi-phy.yaml | 95 + .../bindings/phy/mediatek,mt7621-pci-phy.yaml | 41 + .../devicetree/bindings/phy/mediatek,pcie-phy.yaml | 75 + .../devicetree/bindings/phy/mediatek,tphy.yaml | 312 + .../devicetree/bindings/phy/mediatek,ufs-phy.yaml | 69 + .../devicetree/bindings/phy/mediatek,xsphy.yaml | 199 + .../devicetree/bindings/phy/meson-gxl-usb2-phy.txt | 21 + .../bindings/phy/microchip,lan966x-serdes.yaml | 59 + .../bindings/phy/microchip,sparx5-serdes.yaml | 100 + .../bindings/phy/mixel,mipi-dsi-phy.yaml | 107 + .../bindings/phy/mscc,vsc7514-serdes.yaml | 56 + .../devicetree/bindings/phy/mxs-usb-phy.txt | 33 + .../bindings/phy/nvidia,tegra124-xusb-padctl.txt | 779 ++ .../bindings/phy/nvidia,tegra20-usb-phy.yaml | 373 + .../bindings/phy/phy-armada38x-comphy.txt | 48 + .../devicetree/bindings/phy/phy-ath79-usb.txt | 18 + .../devicetree/bindings/phy/phy-bindings.txt | 72 + .../bindings/phy/phy-cadence-sierra.yaml | 174 + .../bindings/phy/phy-cadence-torrent.yaml | 218 + .../devicetree/bindings/phy/phy-cpcap-usb.txt | 40 + .../devicetree/bindings/phy/phy-da8xx-usb.txt | 40 + .../bindings/phy/phy-hi3798cv200-combphy.txt | 59 + .../devicetree/bindings/phy/phy-hi6220-usb.txt | 16 + .../devicetree/bindings/phy/phy-hisi-inno-usb2.txt | 71 + .../bindings/phy/phy-lantiq-rcu-usb2.txt | 40 + .../bindings/phy/phy-lpc18xx-usb-otg.txt | 26 + .../bindings/phy/phy-mapphone-mdm6600.txt | 29 + .../devicetree/bindings/phy/phy-miphy28lp.txt | 117 + .../devicetree/bindings/phy/phy-miphy365x.txt | 77 + .../devicetree/bindings/phy/phy-mvebu-comphy.txt | 94 + .../devicetree/bindings/phy/phy-mvebu.txt | 42 + .../devicetree/bindings/phy/phy-pxa-usb.txt | 18 + .../bindings/phy/phy-rockchip-inno-hdmi.txt | 43 + .../bindings/phy/phy-rockchip-inno-usb2.yaml | 188 + .../bindings/phy/phy-rockchip-naneng-combphy.yaml | 109 + .../devicetree/bindings/phy/phy-rockchip-typec.txt | 84 + .../devicetree/bindings/phy/phy-stih407-usb.txt | 24 + .../devicetree/bindings/phy/phy-stm32-usbphyc.yaml | 282 + .../devicetree/bindings/phy/phy-tegra194-p2u.yaml | 53 + .../devicetree/bindings/phy/pistachio-usb-phy.txt | 29 + .../devicetree/bindings/phy/pxa1928-usb-phy.txt | 18 + .../devicetree/bindings/phy/qcom,edp-phy.yaml | 77 + .../bindings/phy/qcom,hdmi-phy-other.yaml | 104 + .../devicetree/bindings/phy/qcom,hdmi-phy-qmp.yaml | 94 + .../bindings/phy/qcom,ipq806x-usb-phy-hs.yaml | 56 + .../bindings/phy/qcom,ipq806x-usb-phy-ss.yaml | 74 + .../bindings/phy/qcom,msm8996-qmp-pcie-phy.yaml | 189 + .../devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml | 296 + .../devicetree/bindings/phy/qcom,qmp-ufs-phy.yaml | 240 + .../devicetree/bindings/phy/qcom,qmp-usb-phy.yaml | 401 + .../bindings/phy/qcom,qmp-usb3-dp-phy.yaml | 224 + .../devicetree/bindings/phy/qcom,qusb2-phy.yaml | 192 + .../devicetree/bindings/phy/qcom,usb-8x16-phy.txt | 76 + .../devicetree/bindings/phy/qcom,usb-hs-28nm.yaml | 91 + .../devicetree/bindings/phy/qcom,usb-hs-phy.yaml | 111 + .../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 65 + .../bindings/phy/qcom,usb-snps-femto-v2.yaml | 176 + .../devicetree/bindings/phy/qcom,usb-ss.yaml | 83 + .../bindings/phy/qcom-apq8064-sata-phy.txt | 24 + .../bindings/phy/qcom-ipq806x-sata-phy.txt | 23 + .../devicetree/bindings/phy/qcom-pcie2-phy.txt | 42 + .../bindings/phy/qcom-usb-ipq4019-phy.yaml | 52 + .../devicetree/bindings/phy/ralink-usb-phy.txt | 23 + .../bindings/phy/renesas,rcar-gen2-usb-phy.yaml | 123 + .../bindings/phy/renesas,rcar-gen3-pcie-phy.yaml | 53 + .../devicetree/bindings/phy/renesas,usb2-phy.yaml | 132 + .../devicetree/bindings/phy/renesas,usb3-phy.yaml | 78 + .../bindings/phy/rockchip,pcie3-phy.yaml | 80 + .../bindings/phy/rockchip,px30-dsi-dphy.yaml | 71 + .../devicetree/bindings/phy/rockchip-dp-phy.txt | 26 + .../devicetree/bindings/phy/rockchip-emmc-phy.txt | 43 + .../bindings/phy/rockchip-inno-csi-dphy.yaml | 80 + .../bindings/phy/rockchip-mipi-dphy-rx0.yaml | 73 + .../devicetree/bindings/phy/rockchip-pcie-phy.txt | 36 + .../devicetree/bindings/phy/rockchip-usb-phy.yaml | 78 + .../bindings/phy/samsung,dp-video-phy.yaml | 41 + .../bindings/phy/samsung,exynos-hdmi-phy.yaml | 43 + .../bindings/phy/samsung,exynos-pcie-phy.yaml | 51 + .../bindings/phy/samsung,exynos5250-sata-phy.yaml | 64 + .../bindings/phy/samsung,mipi-video-phy.yaml | 113 + .../devicetree/bindings/phy/samsung,ufs-phy.yaml | 112 + .../devicetree/bindings/phy/samsung,usb2-phy.yaml | 102 + .../bindings/phy/samsung,usb3-drd-phy.yaml | 126 + .../bindings/phy/socionext,uniphier-ahci-phy.yaml | 136 + .../bindings/phy/socionext,uniphier-pcie-phy.yaml | 101 + .../bindings/phy/socionext,uniphier-usb2-phy.yaml | 88 + .../phy/socionext,uniphier-usb3hs-phy.yaml | 167 + .../phy/socionext,uniphier-usb3ss-phy.yaml | 151 + .../devicetree/bindings/phy/st-spear-miphy.txt | 15 + .../bindings/phy/sunplus,sp7021-usb2-phy.yaml | 73 + .../devicetree/bindings/phy/ti,omap-usb2.yaml | 80 + .../bindings/phy/ti,phy-am654-serdes.yaml | 103 + .../devicetree/bindings/phy/ti,phy-gmii-sel.yaml | 129 + .../devicetree/bindings/phy/ti,phy-j721e-wiz.yaml | 260 + .../devicetree/bindings/phy/ti,tcan104x-can.yaml | 63 + Documentation/devicetree/bindings/phy/ti-phy.txt | 98 + .../bindings/phy/transmit-amplitude.yaml | 103 + .../devicetree/bindings/phy/xlnx,zynqmp-psgtr.yaml | 105 + .../bindings/pinctrl/abilis,tb10x-iomux.txt | 80 + .../bindings/pinctrl/actions,s500-pinctrl.yaml | 242 + .../bindings/pinctrl/actions,s700-pinctrl.txt | 170 + .../bindings/pinctrl/actions,s900-pinctrl.txt | 204 + .../pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 302 + .../devicetree/bindings/pinctrl/apple,pinctrl.yaml | 124 + .../bindings/pinctrl/aspeed,ast2400-pinctrl.yaml | 86 + .../bindings/pinctrl/aspeed,ast2500-pinctrl.yaml | 103 + .../bindings/pinctrl/aspeed,ast2600-pinctrl.yaml | 119 + .../bindings/pinctrl/atmel,at91-pinctrl.txt | 176 + .../bindings/pinctrl/atmel,at91-pio4-pinctrl.txt | 97 + .../bindings/pinctrl/axis,artpec6-pinctrl.txt | 87 + .../devicetree/bindings/pinctrl/berlin,pinctrl.txt | 47 + .../bindings/pinctrl/bitmain,bm1880-pinctrl.txt | 126 + .../bindings/pinctrl/brcm,bcm11351-pinctrl.txt | 461 ++ .../bindings/pinctrl/brcm,bcm2835-gpio.txt | 99 + .../bindings/pinctrl/brcm,bcm4908-pinctrl.yaml | 73 + .../bindings/pinctrl/brcm,bcm6318-pinctrl.yaml | 146 + .../bindings/pinctrl/brcm,bcm63268-pinctrl.yaml | 167 + .../bindings/pinctrl/brcm,bcm6328-pinctrl.yaml | 130 + .../bindings/pinctrl/brcm,bcm6358-pinctrl.yaml | 96 + .../bindings/pinctrl/brcm,bcm6362-pinctrl.yaml | 209 + .../bindings/pinctrl/brcm,bcm6368-pinctrl.yaml | 220 + .../bindings/pinctrl/brcm,cygnus-pinmux.txt | 132 + .../bindings/pinctrl/brcm,iproc-gpio.txt | 123 + .../bindings/pinctrl/brcm,ns-pinmux.yaml | 90 + .../bindings/pinctrl/brcm,ns2-pinmux.txt | 102 + .../devicetree/bindings/pinctrl/brcm,nsp-gpio.txt | 80 + .../bindings/pinctrl/brcm,nsp-pinmux.txt | 79 + .../bindings/pinctrl/canaan,k210-fpioa.yaml | 180 + .../bindings/pinctrl/cirrus,lochnagar.yaml | 186 + .../devicetree/bindings/pinctrl/cirrus,madera.yaml | 113 + .../bindings/pinctrl/cnxt,cx92755-pinctrl.txt | 86 + .../bindings/pinctrl/cortina,gemini-pinctrl.txt | 68 + .../bindings/pinctrl/cypress,cy8c95x0.yaml | 134 + .../bindings/pinctrl/fsl,imx-pinctrl.txt | 93 + .../bindings/pinctrl/fsl,imx25-pinctrl.txt | 23 + .../bindings/pinctrl/fsl,imx27-pinctrl.txt | 121 + .../bindings/pinctrl/fsl,imx35-pinctrl.txt | 33 + .../bindings/pinctrl/fsl,imx50-pinctrl.txt | 32 + .../bindings/pinctrl/fsl,imx51-pinctrl.txt | 32 + .../bindings/pinctrl/fsl,imx53-pinctrl.txt | 32 + .../bindings/pinctrl/fsl,imx6dl-pinctrl.txt | 38 + .../bindings/pinctrl/fsl,imx6q-pinctrl.txt | 38 + .../bindings/pinctrl/fsl,imx6sl-pinctrl.txt | 39 + .../bindings/pinctrl/fsl,imx6sll-pinctrl.txt | 40 + .../bindings/pinctrl/fsl,imx6sx-pinctrl.txt | 36 + .../bindings/pinctrl/fsl,imx6ul-pinctrl.txt | 37 + .../bindings/pinctrl/fsl,imx7d-pinctrl.yaml | 113 + .../bindings/pinctrl/fsl,imx7ulp-pinctrl.txt | 53 + .../bindings/pinctrl/fsl,imx8mm-pinctrl.yaml | 84 + .../bindings/pinctrl/fsl,imx8mn-pinctrl.yaml | 84 + .../bindings/pinctrl/fsl,imx8mp-pinctrl.yaml | 84 + .../bindings/pinctrl/fsl,imx8mq-pinctrl.yaml | 84 + .../bindings/pinctrl/fsl,imx8ulp-pinctrl.yaml | 82 + .../bindings/pinctrl/fsl,imx93-pinctrl.yaml | 85 + .../devicetree/bindings/pinctrl/fsl,imxrt1050.yaml | 79 + .../devicetree/bindings/pinctrl/fsl,imxrt1170.yaml | 77 + .../bindings/pinctrl/fsl,mxs-pinctrl.txt | 127 + .../bindings/pinctrl/fsl,scu-pinctrl.yaml | 74 + .../bindings/pinctrl/fsl,vf610-pinctrl.txt | 41 + .../bindings/pinctrl/img,pistachio-pinctrl.txt | 217 + .../bindings/pinctrl/ingenic,pinctrl.yaml | 193 + .../devicetree/bindings/pinctrl/intel,lgm-io.yaml | 76 + .../bindings/pinctrl/intel,pinctrl-keembay.yaml | 136 + .../bindings/pinctrl/intel,pinctrl-thunderbay.yaml | 120 + .../bindings/pinctrl/lantiq,pinctrl-falcon.txt | 83 + .../bindings/pinctrl/lantiq,pinctrl-xway.txt | 191 + .../bindings/pinctrl/marvell,ac5-pinctrl.yaml | 73 + .../pinctrl/marvell,armada-370-pinctrl.txt | 99 + .../pinctrl/marvell,armada-375-pinctrl.txt | 82 + .../pinctrl/marvell,armada-37xx-pinctrl.txt | 195 + .../pinctrl/marvell,armada-38x-pinctrl.txt | 80 + .../pinctrl/marvell,armada-39x-pinctrl.txt | 84 + .../pinctrl/marvell,armada-98dx3236-pinctrl.txt | 46 + .../bindings/pinctrl/marvell,armada-xp-pinctrl.txt | 99 + .../bindings/pinctrl/marvell,dove-pinctrl.txt | 90 + .../bindings/pinctrl/marvell,kirkwood-pinctrl.txt | 359 + .../bindings/pinctrl/marvell,mvebu-pinctrl.txt | 46 + .../bindings/pinctrl/marvell,orion-pinctrl.txt | 93 + .../bindings/pinctrl/mediatek,mt65xx-pinctrl.yaml | 211 + .../bindings/pinctrl/mediatek,mt6779-pinctrl.yaml | 207 + .../bindings/pinctrl/mediatek,mt6797-pinctrl.yaml | 176 + .../bindings/pinctrl/mediatek,mt7622-pinctrl.yaml | 376 + .../bindings/pinctrl/mediatek,mt7986-pinctrl.yaml | 410 + .../bindings/pinctrl/mediatek,mt8183-pinctrl.yaml | 231 + .../bindings/pinctrl/mediatek,mt8188-pinctrl.yaml | 226 + .../bindings/pinctrl/mediatek,pinctrl-mt6795.yaml | 224 + .../devicetree/bindings/pinctrl/meson,pinctrl.txt | 94 + .../bindings/pinctrl/microchip,pic32-pinctrl.txt | 60 + .../bindings/pinctrl/microchip,sparx5-sgpio.yaml | 168 + .../bindings/pinctrl/mscc,ocelot-pinctrl.yaml | 116 + .../bindings/pinctrl/nuvoton,npcm7xx-pinctrl.txt | 216 + .../bindings/pinctrl/nuvoton,wpcm450-pinctrl.yaml | 161 + .../bindings/pinctrl/nvidia,tegra114-pinmux.txt | 131 + .../bindings/pinctrl/nvidia,tegra124-pinmux.txt | 153 + .../pinctrl/nvidia,tegra124-xusb-padctl.txt | 135 + .../bindings/pinctrl/nvidia,tegra194-pinmux.txt | 107 + .../bindings/pinctrl/nvidia,tegra20-pinmux.txt | 143 + .../bindings/pinctrl/nvidia,tegra210-pinmux.txt | 166 + .../bindings/pinctrl/nvidia,tegra30-pinmux.txt | 144 + .../bindings/pinctrl/nxp,lpc1850-scu.txt | 71 + .../devicetree/bindings/pinctrl/oxnas,pinctrl.txt | 56 + .../devicetree/bindings/pinctrl/pincfg-node.yaml | 153 + .../bindings/pinctrl/pinctrl-bindings.txt | 109 + .../bindings/pinctrl/pinctrl-max77620.txt | 127 + .../bindings/pinctrl/pinctrl-mcp23s08.txt | 148 + .../bindings/pinctrl/pinctrl-mt8186.yaml | 276 + .../bindings/pinctrl/pinctrl-mt8192.yaml | 183 + .../bindings/pinctrl/pinctrl-mt8195.yaml | 287 + .../devicetree/bindings/pinctrl/pinctrl-palmas.txt | 105 + .../devicetree/bindings/pinctrl/pinctrl-rk805.txt | 63 + .../devicetree/bindings/pinctrl/pinctrl-single.txt | 262 + .../devicetree/bindings/pinctrl/pinctrl-sirf.txt | 47 + .../devicetree/bindings/pinctrl/pinctrl-st.txt | 174 + .../devicetree/bindings/pinctrl/pinctrl-sx150x.txt | 72 + .../devicetree/bindings/pinctrl/pinctrl-vt8500.txt | 57 + .../devicetree/bindings/pinctrl/pinctrl.yaml | 45 + .../devicetree/bindings/pinctrl/pinctrl_spear.txt | 155 + .../devicetree/bindings/pinctrl/pinmux-node.yaml | 133 + .../bindings/pinctrl/qcom,apq8064-pinctrl.txt | 95 + .../bindings/pinctrl/qcom,apq8084-pinctrl.txt | 188 + .../bindings/pinctrl/qcom,ipq4019-pinctrl.txt | 85 + .../bindings/pinctrl/qcom,ipq6018-pinctrl.yaml | 155 + .../bindings/pinctrl/qcom,ipq8064-pinctrl.txt | 101 + .../bindings/pinctrl/qcom,ipq8074-pinctrl.txt | 181 + .../bindings/pinctrl/qcom,mdm9607-pinctrl.yaml | 134 + .../bindings/pinctrl/qcom,mdm9615-pinctrl.txt | 161 + .../bindings/pinctrl/qcom,msm8226-pinctrl.yaml | 135 + .../bindings/pinctrl/qcom,msm8660-pinctrl.txt | 96 + .../bindings/pinctrl/qcom,msm8909-tlmm.yaml | 152 + .../bindings/pinctrl/qcom,msm8916-pinctrl.txt | 195 + .../bindings/pinctrl/qcom,msm8953-pinctrl.yaml | 172 + .../bindings/pinctrl/qcom,msm8960-pinctrl.txt | 190 + .../bindings/pinctrl/qcom,msm8974-pinctrl.txt | 121 + .../bindings/pinctrl/qcom,msm8976-pinctrl.txt | 183 + .../bindings/pinctrl/qcom,msm8994-pinctrl.txt | 186 + .../bindings/pinctrl/qcom,msm8996-pinctrl.txt | 208 + .../bindings/pinctrl/qcom,msm8998-pinctrl.txt | 202 + .../bindings/pinctrl/qcom,pmic-gpio.yaml | 538 ++ .../devicetree/bindings/pinctrl/qcom,pmic-mpp.yaml | 189 + .../bindings/pinctrl/qcom,qcm2290-pinctrl.yaml | 167 + .../bindings/pinctrl/qcom,qcs404-pinctrl.txt | 199 + .../bindings/pinctrl/qcom,sc7180-pinctrl.txt | 187 + .../pinctrl/qcom,sc7280-lpass-lpi-pinctrl.yaml | 119 + .../bindings/pinctrl/qcom,sc7280-pinctrl.yaml | 171 + .../bindings/pinctrl/qcom,sc8180x-pinctrl.yaml | 162 + .../pinctrl/qcom,sc8280xp-lpass-lpi-pinctrl.yaml | 133 + .../bindings/pinctrl/qcom,sc8280xp-pinctrl.yaml | 160 + .../bindings/pinctrl/qcom,sdm660-pinctrl.txt | 191 + .../bindings/pinctrl/qcom,sdm845-pinctrl.txt | 176 + .../bindings/pinctrl/qcom,sdx55-pinctrl.yaml | 157 + .../bindings/pinctrl/qcom,sdx65-pinctrl.yaml | 191 + .../bindings/pinctrl/qcom,sm6115-pinctrl.yaml | 193 + .../bindings/pinctrl/qcom,sm6125-pinctrl.yaml | 162 + .../bindings/pinctrl/qcom,sm6350-pinctrl.yaml | 158 + .../bindings/pinctrl/qcom,sm6375-tlmm.yaml | 167 + .../bindings/pinctrl/qcom,sm8150-pinctrl.txt | 190 + .../pinctrl/qcom,sm8250-lpass-lpi-pinctrl.yaml | 133 + .../bindings/pinctrl/qcom,sm8250-pinctrl.yaml | 158 + .../bindings/pinctrl/qcom,sm8350-pinctrl.yaml | 155 + .../pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml | 135 + .../bindings/pinctrl/qcom,sm8450-pinctrl.yaml | 159 + .../bindings/pinctrl/qcom,tlmm-common.yaml | 86 + .../bindings/pinctrl/ralink,mt7620-pinctrl.yaml | 97 + .../bindings/pinctrl/ralink,mt7621-pinctrl.yaml | 71 + .../bindings/pinctrl/ralink,rt2880-pinctrl.yaml | 68 + .../bindings/pinctrl/ralink,rt305x-pinctrl.yaml | 89 + .../bindings/pinctrl/ralink,rt3883-pinctrl.yaml | 71 + .../devicetree/bindings/pinctrl/renesas,pfc.yaml | 198 + .../bindings/pinctrl/renesas,rza1-ports.yaml | 194 + .../bindings/pinctrl/renesas,rza2-pinctrl.yaml | 103 + .../bindings/pinctrl/renesas,rzg2l-pinctrl.yaml | 184 + .../bindings/pinctrl/renesas,rzn1-pinctrl.yaml | 132 + .../bindings/pinctrl/renesas,rzv2m-pinctrl.yaml | 170 + .../bindings/pinctrl/rockchip,pinctrl.yaml | 190 + .../pinctrl/samsung,pinctrl-gpio-bank.yaml | 52 + .../bindings/pinctrl/samsung,pinctrl-pins-cfg.yaml | 80 + .../pinctrl/samsung,pinctrl-wakeup-interrupt.yaml | 106 + .../bindings/pinctrl/samsung,pinctrl.yaml | 387 + .../pinctrl/socionext,uniphier-pinctrl.yaml | 79 + .../devicetree/bindings/pinctrl/sprd,pinctrl.txt | 83 + .../bindings/pinctrl/sprd,sc9860-pinctrl.txt | 70 + .../bindings/pinctrl/st,stm32-pinctrl.yaml | 287 + .../bindings/pinctrl/starfive,jh7100-pinctrl.yaml | 307 + .../devicetree/bindings/pinctrl/ste,abx500.txt | 318 + .../devicetree/bindings/pinctrl/ste,nomadik.txt | 148 + .../bindings/pinctrl/sunplus,sp7021-pinctrl.yaml | 377 + .../devicetree/bindings/pinctrl/ti,da850-pupd.txt | 55 + .../devicetree/bindings/pinctrl/ti,iodelay.txt | 47 + .../bindings/pinctrl/ti,omap-pinctrl.txt | 13 + .../bindings/pinctrl/toshiba,visconti-pinctrl.yaml | 96 + .../bindings/pinctrl/xlnx,zynq-pinctrl.yaml | 217 + .../bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 339 + .../devicetree/bindings/pmem/pmem-region.txt | 65 + .../devicetree/bindings/power/actions,owl-sps.txt | 21 + .../bindings/power/amlogic,meson-ee-pwrc.yaml | 184 + .../bindings/power/amlogic,meson-gx-pwrc.txt | 63 + .../bindings/power/amlogic,meson-sec-pwrc.yaml | 42 + .../bindings/power/apple,pmgr-pwrstate.yaml | 79 + .../devicetree/bindings/power/avs/qcom,cpr.yaml | 161 + .../devicetree/bindings/power/brcm,bcm-pmb.yaml | 51 + .../bindings/power/brcm,bcm63xx-power.yaml | 44 + .../bindings/power/domain-idle-state.yaml | 76 + .../devicetree/bindings/power/fsl,imx-gpc.yaml | 138 + .../devicetree/bindings/power/fsl,imx-gpcv2.yaml | 144 + .../devicetree/bindings/power/fsl,scu-pd.yaml | 41 + .../bindings/power/mediatek,power-controller.yaml | 212 + .../devicetree/bindings/power/mti,mips-cpc.yaml | 37 + .../devicetree/bindings/power/pd-samsung.yaml | 68 + .../devicetree/bindings/power/power-controller.txt | 17 + .../devicetree/bindings/power/power-domain.yaml | 137 + .../devicetree/bindings/power/power_domain.txt | 112 + .../devicetree/bindings/power/qcom,rpmpd.yaml | 192 + .../devicetree/bindings/power/renesas,apmu.yaml | 59 + .../bindings/power/renesas,rcar-sysc.yaml | 69 + .../bindings/power/renesas,sysc-rmobile.yaml | 121 + .../bindings/power/reset/axxia-reset.txt | 20 + .../power/reset/brcm,bcm21664-resetmgr.txt | 14 + .../bindings/power/reset/gemini-poweroff.txt | 17 + .../bindings/power/reset/gpio-poweroff.yaml | 59 + .../bindings/power/reset/gpio-restart.yaml | 86 + .../bindings/power/reset/keystone-reset.txt | 67 + .../bindings/power/reset/ltc2952-poweroff.txt | 33 + .../bindings/power/reset/mt6323-poweroff.txt | 20 + .../bindings/power/reset/nvmem-reboot-mode.txt | 26 + .../bindings/power/reset/ocelot-reset.txt | 19 + .../devicetree/bindings/power/reset/qcom,pon.yaml | 128 + .../bindings/power/reset/qcom,pshold.yaml | 35 + .../bindings/power/reset/qnap-poweroff.txt | 15 + .../bindings/power/reset/reboot-mode.yaml | 49 + .../bindings/power/reset/regulator-poweroff.yaml | 37 + .../bindings/power/reset/restart-poweroff.txt | 8 + .../devicetree/bindings/power/reset/st-reset.txt | 11 + .../bindings/power/reset/syscon-poweroff.yaml | 62 + .../bindings/power/reset/syscon-reboot-mode.yaml | 55 + .../bindings/power/reset/syscon-reboot.yaml | 67 + .../bindings/power/reset/xlnx,zynqmp-power.yaml | 83 + .../bindings/power/rockchip,power-controller.yaml | 254 + .../bindings/power/rockchip-io-domain.yaml | 390 + .../power/supply/active-semi,act8945a-charger.yaml | 76 + .../devicetree/bindings/power/supply/battery.yaml | 184 + .../devicetree/bindings/power/supply/bq2415x.yaml | 97 + .../devicetree/bindings/power/supply/bq24190.yaml | 92 + .../devicetree/bindings/power/supply/bq24257.yaml | 124 + .../devicetree/bindings/power/supply/bq24735.yaml | 89 + .../devicetree/bindings/power/supply/bq2515x.yaml | 91 + .../devicetree/bindings/power/supply/bq256xx.yaml | 109 + .../devicetree/bindings/power/supply/bq25890.yaml | 123 + .../devicetree/bindings/power/supply/bq25980.yaml | 114 + .../devicetree/bindings/power/supply/bq27xxx.yaml | 95 + .../bindings/power/supply/charger-manager.yaml | 217 + .../bindings/power/supply/cpcap-battery.yaml | 87 + .../bindings/power/supply/cpcap-charger.yaml | 106 + .../bindings/power/supply/cw2015_battery.yaml | 80 + .../bindings/power/supply/dlg,da9150-charger.yaml | 52 + .../power/supply/dlg,da9150-fuel-gauge.yaml | 51 + .../bindings/power/supply/gpio-charger.yaml | 94 + .../bindings/power/supply/ingenic,battery.yaml | 61 + .../devicetree/bindings/power/supply/isp1704.yaml | 42 + .../bindings/power/supply/lego,ev3-battery.yaml | 55 + .../bindings/power/supply/lltc,lt3651-charger.yaml | 44 + .../bindings/power/supply/lltc,ltc294x.yaml | 66 + .../bindings/power/supply/ltc4162-l.yaml | 67 + .../bindings/power/supply/max77650-charger.yaml | 37 + .../bindings/power/supply/max8925_battery.txt | 18 + .../bindings/power/supply/maxim,ds2760.yaml | 43 + .../bindings/power/supply/maxim,max14577.yaml | 84 + .../bindings/power/supply/maxim,max14656.yaml | 45 + .../bindings/power/supply/maxim,max17040.yaml | 97 + .../bindings/power/supply/maxim,max17042.yaml | 81 + .../bindings/power/supply/maxim,max77693.yaml | 70 + .../bindings/power/supply/maxim,max77976.yaml | 44 + .../bindings/power/supply/maxim,max8903.yaml | 67 + .../power/supply/mediatek,mt6370-charger.yaml | 96 + .../bindings/power/supply/microchip,ucs1002.yaml | 51 + .../bindings/power/supply/mt6360_charger.yaml | 48 + .../bindings/power/supply/nokia,n900-battery.yaml | 49 + .../bindings/power/supply/olpc-battery.yaml | 27 + .../bindings/power/supply/power-supply.yaml | 21 + .../bindings/power/supply/qcom,pm8941-charger.yaml | 178 + .../power/supply/qcom,pm8941-coincell.yaml | 57 + .../power/supply/richtek,rt5033-battery.yaml | 54 + .../bindings/power/supply/richtek,rt9455.yaml | 90 + .../bindings/power/supply/rohm,bd99954.yaml | 163 + .../bindings/power/supply/samsung,battery.yaml | 56 + .../bindings/power/supply/sbs,sbs-battery.yaml | 84 + .../bindings/power/supply/sbs,sbs-charger.yaml | 55 + .../bindings/power/supply/sbs,sbs-manager.yaml | 105 + .../bindings/power/supply/sc2731-charger.yaml | 53 + .../bindings/power/supply/sc27xx-fg.yaml | 98 + .../power/supply/stericsson,ab8500-battery.txt | 34 + .../power/supply/stericsson,ab8500-btemp.yaml | 77 + .../power/supply/stericsson,ab8500-chargalg.yaml | 41 + .../power/supply/stericsson,ab8500-charger.yaml | 127 + .../power/supply/stericsson,ab8500-fg.yaml | 81 + .../power/supply/summit,smb347-charger.yaml | 182 + .../bindings/power/supply/ti,lp8727.yaml | 89 + .../bindings/power/supply/tps65090-charger.yaml | 36 + .../bindings/power/supply/tps65217-charger.yaml | 43 + .../bindings/power/supply/twl4030-charger.yaml | 68 + .../supply/x-powers,axp20x-ac-power-supply.yaml | 35 + .../x-powers,axp20x-battery-power-supply.yaml | 34 + .../supply/x-powers,axp20x-usb-power-supply.yaml | 37 + .../devicetree/bindings/power/ti-smartreflex.txt | 47 + .../devicetree/bindings/power/wakeup-source.txt | 70 + .../bindings/power/xlnx,zynqmp-genpd.txt | 34 + .../devicetree/bindings/powerpc/4xx/akebono.txt | 52 + .../devicetree/bindings/powerpc/4xx/cpm.txt | 52 + .../devicetree/bindings/powerpc/4xx/hsta.txt | 18 + .../bindings/powerpc/4xx/ppc440spe-adma.txt | 91 + .../devicetree/bindings/powerpc/4xx/reboot.txt | 18 + .../devicetree/bindings/powerpc/fsl/ccf.txt | 46 + .../devicetree/bindings/powerpc/fsl/cpus.txt | 33 + .../devicetree/bindings/powerpc/fsl/dcsr.txt | 388 + .../devicetree/bindings/powerpc/fsl/diu.txt | 32 + .../devicetree/bindings/powerpc/fsl/dma.txt | 204 + .../devicetree/bindings/powerpc/fsl/ecm.txt | 60 + .../bindings/powerpc/fsl/interlaken-lac.txt | 309 + .../devicetree/bindings/powerpc/fsl/l2cache.txt | 55 + .../devicetree/bindings/powerpc/fsl/lbc.txt | 43 + .../devicetree/bindings/powerpc/fsl/mcm.txt | 60 + .../bindings/powerpc/fsl/mcu-mpc8349emitx.txt | 17 + .../bindings/powerpc/fsl/mpc5121-psc.txt | 78 + .../bindings/powerpc/fsl/mpc512x_lpbfifo.txt | 21 + .../devicetree/bindings/powerpc/fsl/mpc5200.txt | 198 + .../devicetree/bindings/powerpc/fsl/mpic-msgr.txt | 63 + .../devicetree/bindings/powerpc/fsl/mpic-timer.txt | 38 + .../devicetree/bindings/powerpc/fsl/mpic.txt | 231 + .../devicetree/bindings/powerpc/fsl/msi-pic.txt | 111 + .../devicetree/bindings/powerpc/fsl/pamu.txt | 148 + .../devicetree/bindings/powerpc/fsl/pmc.txt | 63 + .../devicetree/bindings/powerpc/fsl/raideng.txt | 81 + .../devicetree/bindings/powerpc/fsl/scfg.txt | 18 + .../devicetree/bindings/powerpc/fsl/srio-rmu.txt | 163 + .../devicetree/bindings/powerpc/fsl/srio.txt | 104 + .../bindings/powerpc/ibm,powerpc-cpu-features.txt | 248 + .../devicetree/bindings/powerpc/ibm,vas.txt | 22 + .../bindings/powerpc/nintendo/gamecube.txt | 109 + .../devicetree/bindings/powerpc/nintendo/wii.txt | 176 + .../bindings/powerpc/opal/oppanel-opal.txt | 14 + .../devicetree/bindings/powerpc/opal/power-mgt.txt | 118 + .../bindings/powerpc/opal/sensor-groups.txt | 27 + .../devicetree/bindings/powerpc/sleep.yaml | 47 + Documentation/devicetree/bindings/pps/pps-gpio.txt | 30 + .../devicetree/bindings/ptp/brcm,ptp-dte.txt | 19 + .../devicetree/bindings/ptp/ptp-idt82p33.yaml | 45 + .../devicetree/bindings/ptp/ptp-idtcm.yaml | 69 + Documentation/devicetree/bindings/ptp/ptp-ines.txt | 35 + .../devicetree/bindings/ptp/ptp-qoriq.txt | 87 + .../devicetree/bindings/ptp/timestamper.txt | 42 + .../bindings/pwm/allwinner,sun4i-a10-pwm.yaml | 113 + .../devicetree/bindings/pwm/atmel,at91sam-pwm.yaml | 47 + .../devicetree/bindings/pwm/atmel-hlcdc-pwm.txt | 29 + .../devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml | 42 + .../devicetree/bindings/pwm/brcm,iproc-pwm.yaml | 45 + .../devicetree/bindings/pwm/brcm,kona-pwm.txt | 21 + .../bindings/pwm/cirrus,clps711x-pwm.txt | 15 + Documentation/devicetree/bindings/pwm/clk-pwm.yaml | 46 + .../bindings/pwm/google,cros-ec-pwm.yaml | 57 + Documentation/devicetree/bindings/pwm/img-pwm.txt | 24 + Documentation/devicetree/bindings/pwm/imx-pwm.yaml | 85 + .../devicetree/bindings/pwm/imx-tpm-pwm.yaml | 57 + .../devicetree/bindings/pwm/intel,keembay-pwm.yaml | 46 + .../devicetree/bindings/pwm/intel,lgm-pwm.yaml | 47 + .../devicetree/bindings/pwm/iqs620a-pwm.yaml | 34 + .../bindings/pwm/kontron,sl28cpld-pwm.yaml | 35 + .../devicetree/bindings/pwm/lpc1850-sct-pwm.txt | 20 + .../devicetree/bindings/pwm/lpc32xx-pwm.txt | 17 + .../devicetree/bindings/pwm/mediatek,pwm-disp.yaml | 76 + .../devicetree/bindings/pwm/microchip,corepwm.yaml | 83 + Documentation/devicetree/bindings/pwm/mxs-pwm.yaml | 45 + .../devicetree/bindings/pwm/nvidia,tegra20-pwm.txt | 77 + .../devicetree/bindings/pwm/nxp,pca9685-pwm.txt | 27 + .../devicetree/bindings/pwm/pwm-bcm2835.txt | 30 + .../devicetree/bindings/pwm/pwm-berlin.txt | 17 + .../devicetree/bindings/pwm/pwm-fsl-ftm.txt | 55 + .../devicetree/bindings/pwm/pwm-hibvt.txt | 23 + .../devicetree/bindings/pwm/pwm-lp3943.txt | 58 + .../devicetree/bindings/pwm/pwm-mediatek.txt | 52 + .../devicetree/bindings/pwm/pwm-meson.txt | 29 + .../devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 22 + .../devicetree/bindings/pwm/pwm-rockchip.yaml | 105 + .../devicetree/bindings/pwm/pwm-samsung.yaml | 120 + .../devicetree/bindings/pwm/pwm-sifive.yaml | 73 + Documentation/devicetree/bindings/pwm/pwm-sprd.txt | 40 + Documentation/devicetree/bindings/pwm/pwm-st.txt | 43 + .../devicetree/bindings/pwm/pwm-tiecap.yaml | 63 + .../devicetree/bindings/pwm/pwm-tiehrpwm.yaml | 64 + .../devicetree/bindings/pwm/pwm-tipwmss.txt | 58 + Documentation/devicetree/bindings/pwm/pwm.txt | 60 + Documentation/devicetree/bindings/pwm/pwm.yaml | 34 + Documentation/devicetree/bindings/pwm/pxa-pwm.txt | 30 + .../devicetree/bindings/pwm/renesas,pwm-rcar.yaml | 96 + .../devicetree/bindings/pwm/renesas,tpu-pwm.yaml | 101 + .../devicetree/bindings/pwm/spear-pwm.txt | 17 + .../devicetree/bindings/pwm/st,stmpe-pwm.txt | 18 + .../bindings/pwm/sunplus,sp7021-pwm.yaml | 42 + .../devicetree/bindings/pwm/ti,twl-pwm.txt | 17 + .../devicetree/bindings/pwm/ti,twl-pwmled.txt | 17 + .../bindings/pwm/toshiba,pwm-visconti.yaml | 45 + .../devicetree/bindings/pwm/vt8500-pwm.txt | 18 + .../devicetree/bindings/regmap/regmap.txt | 29 + .../devicetree/bindings/regulator/88pg86x.txt | 22 + .../devicetree/bindings/regulator/88pm800.txt | 38 + .../devicetree/bindings/regulator/88pm860x.txt | 30 + .../bindings/regulator/act8865-regulator.txt | 117 + .../bindings/regulator/act8945a-regulator.txt | 113 + .../bindings/regulator/anatop-regulator.yaml | 93 + .../bindings/regulator/as3722-regulator.txt | 91 + .../bindings/regulator/cpcap-regulator.txt | 35 + .../devicetree/bindings/regulator/da9210.txt | 29 + .../devicetree/bindings/regulator/da9211.txt | 205 + .../devicetree/bindings/regulator/dlg,da9121.yaml | 201 + .../devicetree/bindings/regulator/fan53555.txt | 24 + .../bindings/regulator/fixed-regulator.yaml | 139 + .../regulator/google,cros-ec-regulator.yaml | 53 + .../bindings/regulator/gpio-regulator.yaml | 120 + .../regulator/hisilicon,hi655x-regulator.txt | 29 + .../devicetree/bindings/regulator/isl9305.txt | 36 + .../bindings/regulator/lm363x-regulator.txt | 108 + .../devicetree/bindings/regulator/lp872x.txt | 161 + .../devicetree/bindings/regulator/ltc3589.txt | 99 + .../devicetree/bindings/regulator/ltc3676.txt | 94 + .../bindings/regulator/max1586-regulator.txt | 28 + .../bindings/regulator/max77650-regulator.yaml | 34 + .../devicetree/bindings/regulator/max8660.yaml | 77 + .../devicetree/bindings/regulator/max8893.yaml | 88 + .../devicetree/bindings/regulator/max8907.txt | 69 + .../bindings/regulator/max8925-regulator.txt | 40 + .../bindings/regulator/maxim,max14577.yaml | 78 + .../bindings/regulator/maxim,max20086.yaml | 106 + .../bindings/regulator/maxim,max77686.yaml | 83 + .../bindings/regulator/maxim,max77693.yaml | 60 + .../bindings/regulator/maxim,max77802.yaml | 86 + .../bindings/regulator/maxim,max77826.yaml | 65 + .../bindings/regulator/maxim,max77843.yaml | 65 + .../bindings/regulator/maxim,max8952.yaml | 109 + .../bindings/regulator/maxim,max8973.yaml | 141 + .../bindings/regulator/maxim,max8997.yaml | 446 ++ .../bindings/regulator/mcp16502-regulator.txt | 144 + .../regulator/mediatek,mt6331-regulator.yaml | 273 + .../regulator/mediatek,mt6332-regulator.yaml | 112 + .../devicetree/bindings/regulator/mp8859.txt | 22 + .../devicetree/bindings/regulator/mps,mp5416.yaml | 76 + .../devicetree/bindings/regulator/mps,mp886x.yaml | 63 + .../devicetree/bindings/regulator/mps,mpq7920.yaml | 116 + .../bindings/regulator/mt6311-regulator.txt | 35 + .../bindings/regulator/mt6315-regulator.yaml | 70 + .../bindings/regulator/mt6323-regulator.txt | 237 + .../bindings/regulator/mt6358-regulator.txt | 370 + .../bindings/regulator/mt6359-regulator.yaml | 385 + .../bindings/regulator/mt6360-regulator.yaml | 113 + .../bindings/regulator/mt6380-regulator.txt | 89 + .../bindings/regulator/mt6397-regulator.txt | 220 + .../regulator/nvidia,tegra-regulators-coupling.txt | 65 + .../bindings/regulator/nxp,pca9450-regulator.yaml | 195 + .../bindings/regulator/nxp,pf8x00-regulator.yaml | 207 + .../bindings/regulator/onnn,fan53880.yaml | 85 + .../devicetree/bindings/regulator/palmas-pmic.txt | 89 + .../bindings/regulator/pbias-regulator.txt | 32 + .../devicetree/bindings/regulator/pfuze100.yaml | 192 + .../devicetree/bindings/regulator/pv88060.txt | 124 + .../devicetree/bindings/regulator/pv88080.txt | 62 + .../devicetree/bindings/regulator/pv88090.txt | 65 + .../bindings/regulator/pwm-regulator.yaml | 126 + .../bindings/regulator/qcom,rpmh-regulator.yaml | 440 ++ .../bindings/regulator/qcom,smd-rpm-regulator.yaml | 137 + .../bindings/regulator/qcom,spmi-regulator.yaml | 354 + .../regulator/qcom,usb-vbus-regulator.yaml | 41 + .../bindings/regulator/qcom-labibb-regulator.yaml | 99 + ...pberrypi,7inch-touchscreen-panel-regulator.yaml | 44 + .../bindings/regulator/regulator-max77620.txt | 222 + .../devicetree/bindings/regulator/regulator.txt | 1 + .../devicetree/bindings/regulator/regulator.yaml | 291 + .../regulator/richtek,rt4801-regulator.yaml | 89 + .../regulator/richtek,rt4831-regulator.yaml | 35 + .../regulator/richtek,rt5190a-regulator.yaml | 141 + .../regulator/richtek,rt5759-regulator.yaml | 90 + .../regulator/richtek,rt6160-regulator.yaml | 61 + .../regulator/richtek,rt6245-regulator.yaml | 88 + .../regulator/richtek,rtmv20-regulator.yaml | 159 + .../regulator/richtek,rtq2134-regulator.yaml | 106 + .../regulator/richtek,rtq6752-regulator.yaml | 76 + .../bindings/regulator/rohm,bd71815-regulator.yaml | 117 + .../bindings/regulator/rohm,bd71828-regulator.yaml | 105 + .../bindings/regulator/rohm,bd71837-regulator.yaml | 161 + .../bindings/regulator/rohm,bd71847-regulator.yaml | 156 + .../bindings/regulator/rohm,bd9576-regulator.yaml | 40 + .../bindings/regulator/samsung,s2mpa01.yaml | 62 + .../bindings/regulator/samsung,s2mps11.yaml | 44 + .../bindings/regulator/samsung,s2mps13.yaml | 44 + .../bindings/regulator/samsung,s2mps14.yaml | 61 + .../bindings/regulator/samsung,s2mps15.yaml | 44 + .../bindings/regulator/samsung,s2mpu02.yaml | 44 + .../bindings/regulator/samsung,s5m8767.yaml | 100 + .../bindings/regulator/silergy,sy8106a.yaml | 52 + .../bindings/regulator/silergy,sy8824x.yaml | 45 + .../bindings/regulator/silergy,sy8827n.yaml | 47 + .../regulator/siliconmitus,sm5703-regulator.yaml | 49 + .../bindings/regulator/sky81452-regulator.txt | 18 + .../devicetree/bindings/regulator/slg51000.txt | 88 + .../regulator/socionext,uniphier-regulator.yaml | 106 + .../bindings/regulator/sprd,sc2731-regulator.txt | 43 + .../bindings/regulator/st,stm32-booster.yaml | 47 + .../bindings/regulator/st,stm32-vrefbuf.yaml | 53 + .../bindings/regulator/st,stm32mp1-pwr-reg.yaml | 63 + .../devicetree/bindings/regulator/ti,tps62360.yaml | 98 + .../devicetree/bindings/regulator/ti,tps62864.yaml | 63 + .../devicetree/bindings/regulator/ti,tps65219.yaml | 173 + .../bindings/regulator/ti-abb-regulator.txt | 132 + .../bindings/regulator/tps51632-regulator.txt | 27 + .../devicetree/bindings/regulator/tps65023.txt | 60 + .../devicetree/bindings/regulator/tps65090.txt | 126 + .../bindings/regulator/tps65132-regulator.txt | 46 + .../devicetree/bindings/regulator/tps65217.txt | 78 + .../devicetree/bindings/regulator/tps65218.txt | 83 + .../devicetree/bindings/regulator/tps6586x.txt | 135 + .../bindings/regulator/twl-regulator.txt | 80 + .../devicetree/bindings/regulator/vctrl.txt | 49 + .../devicetree/bindings/regulator/vexpress.txt | 32 + .../regulator/vqmmc-ipq4019-regulator.yaml | 43 + .../devicetree/bindings/regulator/wlf,arizona.yaml | 39 + .../remoteproc/amlogic,meson-mx-ao-arc.yaml | 87 + .../bindings/remoteproc/fsl,imx-rproc.yaml | 99 + .../bindings/remoteproc/ingenic,vpu.yaml | 77 + .../devicetree/bindings/remoteproc/mtk,scp.yaml | 124 + .../devicetree/bindings/remoteproc/qcom,adsp.yaml | 611 ++ .../bindings/remoteproc/qcom,glink-edge.yaml | 76 + .../bindings/remoteproc/qcom,pil-info.yaml | 46 + .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 264 + .../bindings/remoteproc/qcom,qcs404-cdsp-pil.yaml | 160 + .../bindings/remoteproc/qcom,sc7180-mss-pil.yaml | 246 + .../bindings/remoteproc/qcom,sc7280-mss-pil.yaml | 267 + .../bindings/remoteproc/qcom,sc7280-wpss-pil.yaml | 207 + .../bindings/remoteproc/qcom,sdm845-adsp-pil.yaml | 159 + .../bindings/remoteproc/qcom,smd-edge.yaml | 117 + .../bindings/remoteproc/qcom,wcnss-pil.txt | 177 + .../bindings/remoteproc/renesas,rcar-rproc.yaml | 65 + .../bindings/remoteproc/st,stm32-rproc.yaml | 158 + .../devicetree/bindings/remoteproc/st-rproc.txt | 41 + .../bindings/remoteproc/ti,davinci-rproc.txt | 80 + .../bindings/remoteproc/ti,k3-dsp-rproc.yaml | 195 + .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 313 + .../bindings/remoteproc/ti,keystone-rproc.txt | 182 + .../bindings/remoteproc/ti,omap-remoteproc.yaml | 331 + .../bindings/remoteproc/ti,pru-rproc.yaml | 220 + .../bindings/remoteproc/wkup_m3_rproc.txt | 52 + .../bindings/reserved-memory/google,open-dice.yaml | 46 + .../bindings/reserved-memory/memory-region.yaml | 40 + .../reserved-memory/nvidia,tegra210-emc-table.yaml | 31 + .../devicetree/bindings/reserved-memory/phram.yaml | 47 + .../bindings/reserved-memory/qcom,cmd-db.yaml | 46 + .../bindings/reserved-memory/qcom,rmtfs-mem.yaml | 53 + .../bindings/reserved-memory/ramoops.yaml | 144 + .../bindings/reserved-memory/reserved-memory.txt | 1 + .../bindings/reserved-memory/reserved-memory.yaml | 100 + .../bindings/reserved-memory/shared-dma-pool.yaml | 97 + .../bindings/reserved-memory/xen,shared-memory.txt | 24 + .../reset/allwinner,sun6i-a31-clock-reset.yaml | 68 + .../devicetree/bindings/reset/altr,rst-mgr.yaml | 47 + .../reset/amlogic,meson-axg-audio-arb.yaml | 56 + .../bindings/reset/amlogic,meson-reset.yaml | 41 + .../bindings/reset/atmel,at91sam9260-reset.yaml | 68 + .../bindings/reset/bitmain,bm1880-reset.yaml | 36 + .../reset/brcm,bcm4908-misc-pcie-reset.yaml | 39 + .../bindings/reset/brcm,bcm63138-pmb.txt | 19 + .../bindings/reset/brcm,bcm6345-reset.yaml | 37 + .../reset/brcm,bcm7216-pcie-sata-rescal.yaml | 41 + .../bindings/reset/brcm,brcmstb-reset.yaml | 48 + .../devicetree/bindings/reset/canaan,k210-rst.yaml | 40 + .../bindings/reset/delta,tn48m-reset.yaml | 35 + .../devicetree/bindings/reset/fsl,imx-src.yaml | 81 + .../devicetree/bindings/reset/fsl,imx7-src.yaml | 65 + .../bindings/reset/hisilicon,hi3660-reset.yaml | 81 + .../bindings/reset/img,pistachio-reset.txt | 55 + .../devicetree/bindings/reset/intel,rcu-gw.yaml | 65 + .../devicetree/bindings/reset/lantiq,reset.yaml | 49 + .../bindings/reset/marvell,berlin2-reset.yaml | 38 + .../devicetree/bindings/reset/microchip,rst.yaml | 59 + .../bindings/reset/nuvoton,npcm750-reset.yaml | 58 + .../devicetree/bindings/reset/nxp,lpc1850-rgu.txt | 83 + .../devicetree/bindings/reset/oxnas,reset.txt | 32 + .../bindings/reset/qca,ar7100-reset.yaml | 40 + .../devicetree/bindings/reset/qcom,aoss-reset.yaml | 52 + .../devicetree/bindings/reset/qcom,pdc-global.yaml | 51 + .../devicetree/bindings/reset/renesas,rst.yaml | 68 + .../bindings/reset/renesas,rzg2l-usbphy-ctrl.yaml | 67 + Documentation/devicetree/bindings/reset/reset.txt | 75 + .../bindings/reset/snps,axs10x-reset.yaml | 48 + .../devicetree/bindings/reset/snps,dw-reset.txt | 30 + .../devicetree/bindings/reset/snps,hsdk-reset.txt | 28 + .../reset/socionext,uniphier-glue-reset.yaml | 113 + .../bindings/reset/socionext,uniphier-reset.yaml | 118 + .../devicetree/bindings/reset/st,sti-softreset.txt | 44 + .../bindings/reset/st,stih407-picophyreset.yaml | 47 + .../bindings/reset/st,stih407-powerdown.yaml | 49 + .../devicetree/bindings/reset/st,stm32-rcc.txt | 6 + .../devicetree/bindings/reset/st,stm32mp1-rcc.txt | 6 + .../bindings/reset/starfive,jh7100-reset.yaml | 38 + .../devicetree/bindings/reset/sunplus,reset.yaml | 38 + .../devicetree/bindings/reset/ti,sci-reset.yaml | 51 + .../bindings/reset/ti,tps380x-reset.yaml | 49 + .../devicetree/bindings/reset/ti-syscon-reset.txt | 91 + .../bindings/reset/xlnx,zynqmp-reset.txt | 55 + .../devicetree/bindings/reset/zynq-reset.txt | 68 + .../devicetree/bindings/resource-names.txt | 54 + .../devicetree/bindings/riscv/canaan.yaml | 47 + Documentation/devicetree/bindings/riscv/cpus.yaml | 186 + .../devicetree/bindings/riscv/microchip.yaml | 37 + .../devicetree/bindings/riscv/sifive,ccache0.yaml | 164 + .../devicetree/bindings/riscv/sifive.yaml | 35 + .../devicetree/bindings/riscv/starfive.yaml | 27 + .../devicetree/bindings/rng/amlogic,meson-rng.yaml | 39 + .../devicetree/bindings/rng/apm,x-gene-rng.yaml | 47 + .../devicetree/bindings/rng/arm-cctrng.yaml | 52 + .../devicetree/bindings/rng/atmel,at91-trng.yaml | 51 + .../devicetree/bindings/rng/brcm,bcm2835.yaml | 82 + .../devicetree/bindings/rng/brcm,iproc-rng200.yaml | 30 + Documentation/devicetree/bindings/rng/hisi-rng.txt | 12 + Documentation/devicetree/bindings/rng/imx-rng.yaml | 52 + .../devicetree/bindings/rng/ingenic,rng.yaml | 36 + .../devicetree/bindings/rng/ingenic,trng.yaml | 43 + .../devicetree/bindings/rng/intel,ixp46x-rng.yaml | 35 + .../bindings/rng/microchip,pic32-rng.txt | 17 + Documentation/devicetree/bindings/rng/mtk-rng.yaml | 55 + .../devicetree/bindings/rng/nuvoton,npcm-rng.yaml | 35 + .../devicetree/bindings/rng/omap_rng.yaml | 81 + .../bindings/rng/samsung,exynos4-rng.yaml | 45 + .../bindings/rng/samsung,exynos5250-trng.yaml | 44 + .../bindings/rng/silex-insight,ba431-rng.yaml | 36 + .../bindings/rng/sparc_sun_oracle_rng.txt | 30 + Documentation/devicetree/bindings/rng/st,rng.yaml | 35 + .../devicetree/bindings/rng/st,stm32-rng.yaml | 49 + .../devicetree/bindings/rng/ti,keystone-rng.yaml | 50 + .../devicetree/bindings/rng/ti,omap-rom-rng.yaml | 41 + .../devicetree/bindings/rng/timeriomem_rng.yaml | 48 + .../bindings/rng/xiphera,xip8001b-trng.yaml | 33 + .../devicetree/bindings/rtc/abracon,abx80x.txt | 31 + .../bindings/rtc/allwinner,sun4i-a10-rtc.yaml | 43 + .../bindings/rtc/allwinner,sun6i-a31-rtc.yaml | 195 + .../bindings/rtc/alphascale,asm9260-rtc.txt | 19 + .../devicetree/bindings/rtc/arm,pl031.yaml | 58 + .../devicetree/bindings/rtc/armada-380-rtc.txt | 24 + .../bindings/rtc/atmel,at91rm9200-rtc.yaml | 50 + .../bindings/rtc/atmel,at91sam9260-rtt.yaml | 69 + .../bindings/rtc/brcm,brcmstb-waketimer.yaml | 44 + Documentation/devicetree/bindings/rtc/cdns,rtc.txt | 25 + .../devicetree/bindings/rtc/cpcap-rtc.txt | 18 + .../devicetree/bindings/rtc/dallas,ds1390.txt | 18 + .../devicetree/bindings/rtc/digicolor-rtc.txt | 17 + .../devicetree/bindings/rtc/epson,rtc7301.txt | 16 + .../devicetree/bindings/rtc/epson,rx6110.txt | 39 + .../devicetree/bindings/rtc/epson,rx8900.yaml | 50 + .../devicetree/bindings/rtc/faraday,ftrtc010.yaml | 58 + .../devicetree/bindings/rtc/fsl,scu-rtc.yaml | 31 + .../bindings/rtc/google,goldfish-rtc.txt | 17 + .../devicetree/bindings/rtc/haoyu,hym8563.txt | 30 + .../devicetree/bindings/rtc/imxdi-rtc.yaml | 43 + .../devicetree/bindings/rtc/ingenic,rtc.yaml | 85 + .../devicetree/bindings/rtc/isil,isl12026.txt | 28 + .../devicetree/bindings/rtc/isil,isl12057.txt | 74 + .../devicetree/bindings/rtc/isil,isl1208.txt | 38 + .../devicetree/bindings/rtc/lpc32xx-rtc.txt | 15 + .../devicetree/bindings/rtc/maxim,ds1742.txt | 12 + .../devicetree/bindings/rtc/maxim,ds3231.txt | 38 + .../devicetree/bindings/rtc/maxim,mcp795.txt | 11 + .../devicetree/bindings/rtc/maxim-ds1302.txt | 46 + .../bindings/rtc/microchip,mfps-rtc.yaml | 67 + .../bindings/rtc/microchip,pic32-rtc.txt | 21 + .../bindings/rtc/microcrystal,rv3032.yaml | 64 + .../devicetree/bindings/rtc/moxa,moxart-rtc.txt | 17 + .../devicetree/bindings/rtc/mstar,msc313-rtc.yaml | 49 + .../devicetree/bindings/rtc/nuvoton,nct3018y.yaml | 45 + .../bindings/rtc/nvidia,tegra20-rtc.yaml | 61 + .../devicetree/bindings/rtc/nxp,lpc1788-rtc.txt | 21 + .../devicetree/bindings/rtc/nxp,pcf2127.yaml | 51 + .../devicetree/bindings/rtc/nxp,pcf85063.yaml | 92 + .../devicetree/bindings/rtc/nxp,pcf8523.txt | 18 + .../devicetree/bindings/rtc/nxp,pcf8563.yaml | 58 + .../devicetree/bindings/rtc/nxp,rtc-2123.txt | 17 + .../devicetree/bindings/rtc/olpc-xo1-rtc.txt | 5 + .../devicetree/bindings/rtc/orion-rtc.txt | 18 + Documentation/devicetree/bindings/rtc/pxa-rtc.txt | 14 + .../devicetree/bindings/rtc/qcom-pm8xxx-rtc.yaml | 69 + .../devicetree/bindings/rtc/realtek,rtd119x.txt | 16 + .../devicetree/bindings/rtc/renesas,rzn1-rtc.yaml | 70 + .../devicetree/bindings/rtc/renesas,sh-rtc.yaml | 77 + .../devicetree/bindings/rtc/rtc-aspeed.txt | 22 + Documentation/devicetree/bindings/rtc/rtc-cmos.txt | 27 + .../devicetree/bindings/rtc/rtc-ds1307.yaml | 102 + .../devicetree/bindings/rtc/rtc-fsl-ftm-alarm.txt | 36 + .../devicetree/bindings/rtc/rtc-m41t80.txt | 39 + .../devicetree/bindings/rtc/rtc-meson-vrtc.txt | 22 + .../devicetree/bindings/rtc/rtc-meson.txt | 35 + .../devicetree/bindings/rtc/rtc-mt2712.txt | 14 + .../devicetree/bindings/rtc/rtc-mt6397.txt | 31 + .../devicetree/bindings/rtc/rtc-mt7622.txt | 21 + Documentation/devicetree/bindings/rtc/rtc-mxc.yaml | 57 + .../devicetree/bindings/rtc/rtc-mxc_v2.yaml | 46 + Documentation/devicetree/bindings/rtc/rtc-omap.txt | 53 + Documentation/devicetree/bindings/rtc/rtc-opal.txt | 17 + .../devicetree/bindings/rtc/rtc-palmas.txt | 32 + .../devicetree/bindings/rtc/rtc-st-lpc.txt | 28 + Documentation/devicetree/bindings/rtc/rtc.yaml | 71 + Documentation/devicetree/bindings/rtc/s3c-rtc.yaml | 91 + .../devicetree/bindings/rtc/sa1100-rtc.yaml | 57 + Documentation/devicetree/bindings/rtc/snvs-rtc.txt | 1 + .../devicetree/bindings/rtc/spear-rtc.txt | 15 + .../devicetree/bindings/rtc/sprd,sc27xx-rtc.txt | 26 + .../devicetree/bindings/rtc/st,stm32-rtc.yaml | 141 + .../devicetree/bindings/rtc/stmp3xxx-rtc.txt | 21 + .../bindings/rtc/sunplus,sp7021-rtc.yaml | 56 + .../devicetree/bindings/rtc/ti,bq32000.yaml | 49 + .../devicetree/bindings/rtc/ti,k3-rtc.yaml | 62 + .../devicetree/bindings/rtc/trivial-rtc.yaml | 93 + Documentation/devicetree/bindings/rtc/twl-rtc.txt | 11 + .../devicetree/bindings/rtc/via,vt8500-rtc.txt | 15 + .../devicetree/bindings/rtc/xgene-rtc.txt | 28 + .../devicetree/bindings/rtc/xlnx,zynqmp-rtc.yaml | 75 + .../devicetree/bindings/scsi/hisilicon-sas.txt | 98 + .../bindings/security/tpm/google,cr50.txt | 19 + .../devicetree/bindings/security/tpm/ibmvtpm.txt | 41 + .../bindings/security/tpm/st33zp24-i2c.txt | 34 + .../bindings/security/tpm/st33zp24-spi.txt | 32 + .../devicetree/bindings/security/tpm/tpm-i2c.txt | 26 + .../bindings/security/tpm/tpm_tis_mmio.txt | 25 + .../bindings/security/tpm/tpm_tis_spi.txt | 23 + Documentation/devicetree/bindings/serial/8250.yaml | 259 + .../devicetree/bindings/serial/8250_omap.yaml | 120 + .../bindings/serial/actions,owl-uart.txt | 16 + .../devicetree/bindings/serial/altera_jtaguart.txt | 5 + .../devicetree/bindings/serial/altera_uart.txt | 8 + .../bindings/serial/amlogic,meson-uart.yaml | 82 + .../devicetree/bindings/serial/arc-uart.txt | 25 + .../devicetree/bindings/serial/arm,mps2-uart.txt | 19 + .../devicetree/bindings/serial/arm_sbsa_uart.txt | 10 + .../bindings/serial/atmel,at91-usart.yaml | 190 + .../bindings/serial/brcm,bcm2835-aux-uart.txt | 18 + .../bindings/serial/brcm,bcm6345-uart.yaml | 47 + .../bindings/serial/brcm,bcm7271-uart.yaml | 95 + .../devicetree/bindings/serial/cavium-uart.txt | 19 + .../devicetree/bindings/serial/cdns,uart.yaml | 66 + .../bindings/serial/cirrus,clps711x-uart.txt | 31 + .../devicetree/bindings/serial/digicolor-usart.txt | 27 + .../bindings/serial/fsl,s32-linflexuart.yaml | 48 + .../devicetree/bindings/serial/fsl-imx-uart.yaml | 112 + .../devicetree/bindings/serial/fsl-lpuart.yaml | 88 + .../devicetree/bindings/serial/fsl-mxs-auart.yaml | 91 + .../devicetree/bindings/serial/ingenic,uart.yaml | 99 + .../devicetree/bindings/serial/lantiq_asc.txt | 31 + .../devicetree/bindings/serial/litex,liteuart.yaml | 40 + .../devicetree/bindings/serial/maxim,max310x.txt | 48 + .../devicetree/bindings/serial/mediatek,uart.yaml | 121 + .../bindings/serial/microchip,pic32-uart.txt | 29 + .../devicetree/bindings/serial/milbeaut-uart.txt | 21 + .../devicetree/bindings/serial/mrvl,pxa-ssp.txt | 64 + .../devicetree/bindings/serial/mvebu-uart.txt | 56 + .../bindings/serial/nvidia,tegra194-tcu.yaml | 61 + .../bindings/serial/nvidia,tegra20-hsuart.txt | 73 + .../bindings/serial/nxp,lpc1850-uart.txt | 28 + .../devicetree/bindings/serial/nxp,sc16is7xx.txt | 118 + .../bindings/serial/nxp-lpc32xx-hsuart.txt | 14 + .../devicetree/bindings/serial/pl011.yaml | 126 + .../bindings/serial/qca,ar9330-uart.yaml | 50 + .../devicetree/bindings/serial/qcom,msm-uart.txt | 25 + .../bindings/serial/qcom,msm-uartdm.yaml | 112 + .../bindings/serial/qcom,serial-geni-qcom.yaml | 86 + .../bindings/serial/rda,8810pl-uart.yaml | 46 + .../bindings/serial/renesas,em-uart.yaml | 74 + .../devicetree/bindings/serial/renesas,hscif.yaml | 150 + .../devicetree/bindings/serial/renesas,sci.yaml | 109 + .../devicetree/bindings/serial/renesas,scif.yaml | 197 + .../devicetree/bindings/serial/renesas,scifa.yaml | 112 + .../devicetree/bindings/serial/renesas,scifb.yaml | 103 + Documentation/devicetree/bindings/serial/rs485.txt | 1 + .../devicetree/bindings/serial/rs485.yaml | 56 + .../devicetree/bindings/serial/samsung_uart.yaml | 145 + .../devicetree/bindings/serial/serial.yaml | 153 + .../devicetree/bindings/serial/sifive-serial.yaml | 65 + .../bindings/serial/snps-dw-apb-uart.yaml | 153 + .../bindings/serial/socionext,uniphier-uart.yaml | 51 + .../devicetree/bindings/serial/sprd-uart.yaml | 75 + .../devicetree/bindings/serial/st,stm32-uart.yaml | 133 + .../devicetree/bindings/serial/st-asc.txt | 18 + .../bindings/serial/sunplus,sp7021-uart.yaml | 56 + .../devicetree/bindings/serial/vt8500-uart.txt | 27 + .../bindings/serial/xlnx,opb-uartlite.yaml | 89 + .../bindings/serio/allwinner,sun4i-a10-ps2.yaml | 51 + .../devicetree/bindings/serio/altera_ps2.txt | 5 + .../devicetree/bindings/serio/arm,pl050.yaml | 67 + .../devicetree/bindings/serio/olpc,ap-sp.txt | 13 + .../devicetree/bindings/serio/ps2-gpio.yaml | 64 + .../devicetree/bindings/serio/snps-arc_ps2.txt | 16 + .../sifive/sifive-blocks-ip-versioning.txt | 38 + .../bindings/siox/eckelmann,siox-gpio.txt | 19 + Documentation/devicetree/bindings/slimbus/bus.txt | 60 + .../bindings/slimbus/slim-ngd-qcom-ctrl.txt | 84 + .../devicetree/bindings/slimbus/slim-qcom-ctrl.txt | 39 + .../bindings/soc/amlogic/amlogic,canvas.yaml | 50 + .../bindings/soc/amlogic/clk-measure.txt | 21 + .../bindings/soc/aspeed/uart-routing.yaml | 56 + .../bindings/soc/bcm/brcm,bcm2835-pm.yaml | 86 + .../bindings/soc/bcm/brcm,bcm2835-vchiq.yaml | 53 + .../bindings/soc/bcm/raspberrypi,bcm2835-power.txt | 47 + Documentation/devicetree/bindings/soc/dove/pmu.txt | 56 + .../devicetree/bindings/soc/fsl/bman-portals.txt | 56 + Documentation/devicetree/bindings/soc/fsl/bman.txt | 137 + .../devicetree/bindings/soc/fsl/cpm_qe/cpm.txt | 67 + .../devicetree/bindings/soc/fsl/cpm_qe/cpm/brg.txt | 21 + .../devicetree/bindings/soc/fsl/cpm_qe/cpm/i2c.txt | 41 + .../devicetree/bindings/soc/fsl/cpm_qe/cpm/pic.txt | 18 + .../devicetree/bindings/soc/fsl/cpm_qe/cpm/usb.txt | 15 + .../devicetree/bindings/soc/fsl/cpm_qe/gpio.txt | 56 + .../devicetree/bindings/soc/fsl/cpm_qe/network.txt | 130 + .../devicetree/bindings/soc/fsl/cpm_qe/qe.txt | 178 + .../bindings/soc/fsl/cpm_qe/qe/firmware.txt | 24 + .../bindings/soc/fsl/cpm_qe/qe/par_io.txt | 51 + .../bindings/soc/fsl/cpm_qe/qe/pincfg.txt | 57 + .../devicetree/bindings/soc/fsl/cpm_qe/qe/ucc.txt | 68 + .../devicetree/bindings/soc/fsl/cpm_qe/qe/usb.txt | 36 + .../devicetree/bindings/soc/fsl/cpm_qe/serial.txt | 32 + .../bindings/soc/fsl/cpm_qe/uqe_serial.txt | 17 + .../bindings/soc/fsl/fsl,layerscape-dcfg.yaml | 68 + .../bindings/soc/fsl/fsl,layerscape-scfg.yaml | 58 + Documentation/devicetree/bindings/soc/fsl/guts.txt | 44 + .../devicetree/bindings/soc/fsl/qman-portals.txt | 134 + Documentation/devicetree/bindings/soc/fsl/qman.txt | 187 + Documentation/devicetree/bindings/soc/fsl/rcpm.txt | 69 + .../devicetree/bindings/soc/imx/fsl,aips-bus.yaml | 49 + .../bindings/soc/imx/fsl,imx8mm-disp-blk-ctrl.yaml | 94 + .../bindings/soc/imx/fsl,imx8mm-vpu-blk-ctrl.yaml | 164 + .../bindings/soc/imx/fsl,imx8mn-disp-blk-ctrl.yaml | 97 + .../bindings/soc/imx/fsl,imx8mp-hdmi-blk-ctrl.yaml | 93 + .../bindings/soc/imx/fsl,imx8mp-hsio-blk-ctrl.yaml | 88 + .../soc/imx/fsl,imx8mp-media-blk-ctrl.yaml | 118 + .../bindings/soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml | 71 + .../bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml | 80 + .../devicetree/bindings/soc/imx/fsl,imx93-src.yaml | 96 + .../devicetree/bindings/soc/imx/imx8m-soc.yaml | 86 + .../bindings/soc/intel/intel,hps-copy-engine.yaml | 51 + .../bindings/soc/litex/litex,soc-controller.yaml | 40 + .../devicetree/bindings/soc/mediatek/devapc.yaml | 61 + .../bindings/soc/mediatek/mediatek,ccorr.yaml | 68 + .../bindings/soc/mediatek/mediatek,mutex.yaml | 101 + .../bindings/soc/mediatek/mediatek,wdma.yaml | 81 + .../devicetree/bindings/soc/mediatek/mtk-svs.yaml | 91 + .../devicetree/bindings/soc/mediatek/pwrap.txt | 72 + .../devicetree/bindings/soc/mediatek/scpsys.txt | 78 + .../soc/microchip/atmel,at91rm9200-tcb.yaml | 213 + .../microchip/microchip,mpfs-sys-controller.yaml | 40 + .../bindings/soc/qcom/qcom,aoss-qmp.yaml | 107 + .../devicetree/bindings/soc/qcom/qcom,apr.yaml | 271 + .../devicetree/bindings/soc/qcom/qcom,eud.yaml | 77 + .../devicetree/bindings/soc/qcom/qcom,geni-se.yaml | 131 + .../devicetree/bindings/soc/qcom/qcom,glink.txt | 94 + .../devicetree/bindings/soc/qcom/qcom,gsbi.yaml | 132 + .../bindings/soc/qcom/qcom,rpmh-rsc.yaml | 261 + .../devicetree/bindings/soc/qcom/qcom,smd-rpm.yaml | 124 + .../devicetree/bindings/soc/qcom/qcom,smd.yaml | 62 + .../devicetree/bindings/soc/qcom/qcom,smem.yaml | 98 + .../devicetree/bindings/soc/qcom/qcom,smp2p.yaml | 145 + .../devicetree/bindings/soc/qcom/qcom,smsm.yaml | 138 + .../devicetree/bindings/soc/qcom/qcom,spm.yaml | 82 + .../devicetree/bindings/soc/qcom/qcom,wcnss.yaml | 136 + .../devicetree/bindings/soc/qcom/qcom-stats.yaml | 53 + .../bindings/soc/renesas/renesas,rzg2l-sysc.yaml | 63 + .../devicetree/bindings/soc/rockchip/grf.yaml | 279 + .../bindings/soc/samsung/exynos-pmu.yaml | 133 + .../bindings/soc/samsung/exynos-usi.yaml | 167 + .../devicetree/bindings/soc/ti/k3-ringacc.yaml | 96 + .../bindings/soc/ti/keystone-navigator-dma.txt | 111 + .../bindings/soc/ti/keystone-navigator-qmss.txt | 238 + .../devicetree/bindings/soc/ti/sci-pm-domain.yaml | 59 + .../devicetree/bindings/soc/ti/ti,pruss.yaml | 520 ++ .../devicetree/bindings/soc/ti/wkup-m3-ipc.yaml | 175 + .../bindings/soc/xilinx/xlnx,vcu-settings.yaml | 43 + .../devicetree/bindings/soc/xilinx/xlnx,vcu.txt | 26 + .../devicetree/bindings/sound/ac97-bus.txt | 32 + .../devicetree/bindings/sound/adi,adau1372.yaml | 66 + .../devicetree/bindings/sound/adi,adau1701.txt | 39 + .../devicetree/bindings/sound/adi,adau17x1.txt | 32 + .../devicetree/bindings/sound/adi,adau1977.yaml | 93 + .../devicetree/bindings/sound/adi,adau7002.txt | 19 + .../devicetree/bindings/sound/adi,adau7118.yaml | 85 + .../devicetree/bindings/sound/adi,axi-i2s.txt | 34 + .../devicetree/bindings/sound/adi,axi-spdif-tx.txt | 30 + .../devicetree/bindings/sound/adi,max98396.yaml | 141 + .../devicetree/bindings/sound/adi,ssm2305.txt | 14 + .../devicetree/bindings/sound/adi,ssm2602.txt | 19 + Documentation/devicetree/bindings/sound/ak4104.txt | 25 + Documentation/devicetree/bindings/sound/ak4118.txt | 22 + .../devicetree/bindings/sound/ak4375.yaml | 57 + Documentation/devicetree/bindings/sound/ak4458.txt | 28 + Documentation/devicetree/bindings/sound/ak4554.txt | 11 + .../devicetree/bindings/sound/ak4613.yaml | 49 + .../devicetree/bindings/sound/ak4642.yaml | 56 + Documentation/devicetree/bindings/sound/ak5386.txt | 23 + Documentation/devicetree/bindings/sound/ak5558.txt | 24 + .../devicetree/bindings/sound/alc5623.txt | 25 + .../devicetree/bindings/sound/alc5632.txt | 43 + .../bindings/sound/allwinner,sun4i-a10-codec.yaml | 267 + .../bindings/sound/allwinner,sun4i-a10-i2s.yaml | 146 + .../bindings/sound/allwinner,sun4i-a10-spdif.yaml | 122 + .../sound/allwinner,sun50i-a64-codec-analog.yaml | 44 + .../bindings/sound/allwinner,sun50i-h6-dmic.yaml | 79 + .../sound/allwinner,sun8i-a23-codec-analog.yaml | 41 + .../bindings/sound/allwinner,sun8i-a33-codec.yaml | 65 + .../devicetree/bindings/sound/amlogic,aiu.yaml | 118 + .../devicetree/bindings/sound/amlogic,axg-fifo.txt | 34 + .../devicetree/bindings/sound/amlogic,axg-pdm.txt | 29 + .../bindings/sound/amlogic,axg-sound-card.txt | 124 + .../bindings/sound/amlogic,axg-spdifin.txt | 27 + .../bindings/sound/amlogic,axg-spdifout.txt | 25 + .../bindings/sound/amlogic,axg-tdm-formatters.txt | 36 + .../bindings/sound/amlogic,axg-tdm-iface.txt | 22 + .../bindings/sound/amlogic,g12a-toacodec.yaml | 56 + .../bindings/sound/amlogic,g12a-tohdmitx.txt | 58 + .../bindings/sound/amlogic,gx-sound-card.yaml | 116 + .../devicetree/bindings/sound/amlogic,t9015.yaml | 70 + .../devicetree/bindings/sound/apple,mca.yaml | 131 + .../devicetree/bindings/sound/arm,pl041.yaml | 62 + .../bindings/sound/armada-370db-audio.txt | 26 + .../bindings/sound/atmel,sama5d2-classd.yaml | 100 + .../bindings/sound/atmel,sama5d2-i2s.yaml | 85 + .../bindings/sound/atmel,sama5d2-pdmic.yaml | 98 + .../sound/atmel-at91sam9g20ek-wm8731-audio.txt | 26 + .../bindings/sound/atmel-sam9x5-wm8731-audio.txt | 35 + .../devicetree/bindings/sound/atmel-wm8904.txt | 55 + .../devicetree/bindings/sound/atmel_ac97c.txt | 20 + .../bindings/sound/audio-graph-card.yaml | 57 + .../bindings/sound/audio-graph-card2.yaml | 60 + .../bindings/sound/audio-graph-port.yaml | 103 + .../devicetree/bindings/sound/audio-graph.yaml | 46 + .../devicetree/bindings/sound/awinic,aw8738.yaml | 54 + .../bindings/sound/axentia,tse850-pcm5142.txt | 92 + .../devicetree/bindings/sound/brcm,bcm2835-i2s.txt | 24 + .../bindings/sound/brcm,bcm63xx-audio.txt | 29 + .../bindings/sound/brcm,cygnus-audio.txt | 63 + .../devicetree/bindings/sound/cdns,xtfpga-i2s.txt | 18 + .../devicetree/bindings/sound/cirrus,cs35l41.yaml | 195 + .../devicetree/bindings/sound/cirrus,cs35l45.yaml | 75 + .../devicetree/bindings/sound/cirrus,cs4234.yaml | 74 + .../devicetree/bindings/sound/cirrus,cs42l42.yaml | 226 + .../devicetree/bindings/sound/cirrus,cs42l51.yaml | 71 + .../bindings/sound/cirrus,lochnagar.yaml | 52 + .../devicetree/bindings/sound/cirrus,madera.yaml | 115 + .../devicetree/bindings/sound/cs35l32.txt | 62 + .../devicetree/bindings/sound/cs35l33.txt | 124 + .../devicetree/bindings/sound/cs35l34.txt | 62 + .../devicetree/bindings/sound/cs35l35.txt | 181 + .../devicetree/bindings/sound/cs35l36.txt | 168 + Documentation/devicetree/bindings/sound/cs4265.txt | 29 + Documentation/devicetree/bindings/sound/cs4270.txt | 21 + Documentation/devicetree/bindings/sound/cs4271.txt | 57 + .../devicetree/bindings/sound/cs42l52.txt | 46 + .../devicetree/bindings/sound/cs42l56.txt | 63 + .../devicetree/bindings/sound/cs42l73.txt | 22 + .../devicetree/bindings/sound/cs42xx8.txt | 34 + .../devicetree/bindings/sound/cs43130.txt | 67 + Documentation/devicetree/bindings/sound/cs4341.txt | 22 + Documentation/devicetree/bindings/sound/cs4349.txt | 19 + .../devicetree/bindings/sound/cs53l30.txt | 44 + Documentation/devicetree/bindings/sound/da7213.txt | 45 + Documentation/devicetree/bindings/sound/da7218.txt | 102 + Documentation/devicetree/bindings/sound/da7219.txt | 112 + Documentation/devicetree/bindings/sound/da9055.txt | 22 + .../devicetree/bindings/sound/dai-params.yaml | 40 + .../bindings/sound/davinci-evm-audio.txt | 49 + .../bindings/sound/davinci-mcasp-audio.yaml | 201 + .../devicetree/bindings/sound/davinci-mcbsp.txt | 50 + Documentation/devicetree/bindings/sound/dmic.txt | 22 + Documentation/devicetree/bindings/sound/es8328.txt | 38 + .../devicetree/bindings/sound/eukrea-tlv320.txt | 26 + .../devicetree/bindings/sound/everest,es7134.txt | 15 + .../devicetree/bindings/sound/everest,es7241.txt | 28 + .../devicetree/bindings/sound/everest,es8316.yaml | 50 + .../devicetree/bindings/sound/everest,es8326.yaml | 116 + .../devicetree/bindings/sound/fsl,asrc.txt | 80 + .../devicetree/bindings/sound/fsl,aud2htx.yaml | 66 + .../devicetree/bindings/sound/fsl,audmix.txt | 50 + .../devicetree/bindings/sound/fsl,easrc.yaml | 100 + .../devicetree/bindings/sound/fsl,esai.txt | 68 + .../devicetree/bindings/sound/fsl,micfil.yaml | 85 + .../devicetree/bindings/sound/fsl,mqs.txt | 36 + .../devicetree/bindings/sound/fsl,rpmsg.yaml | 109 + .../devicetree/bindings/sound/fsl,sai.yaml | 216 + .../devicetree/bindings/sound/fsl,spdif.yaml | 120 + .../devicetree/bindings/sound/fsl,ssi.txt | 87 + .../devicetree/bindings/sound/fsl,xcvr.yaml | 104 + .../devicetree/bindings/sound/fsl-asoc-card.txt | 115 + .../bindings/sound/google,cros-ec-codec.yaml | 74 + .../bindings/sound/google,sc7180-trogdor.yaml | 145 + .../bindings/sound/google,sc7280-herobrine.yaml | 180 + Documentation/devicetree/bindings/sound/gtm601.txt | 19 + .../bindings/sound/hisilicon,hi6210-i2s.txt | 42 + .../devicetree/bindings/sound/ics43432.txt | 19 + .../devicetree/bindings/sound/img,i2s-in.txt | 47 + .../devicetree/bindings/sound/img,i2s-out.txt | 51 + .../devicetree/bindings/sound/img,parallel-out.txt | 44 + .../bindings/sound/img,pistachio-internal-dac.txt | 18 + .../devicetree/bindings/sound/img,spdif-in.txt | 41 + .../devicetree/bindings/sound/img,spdif-out.txt | 44 + .../devicetree/bindings/sound/imx-audio-card.yaml | 127 + .../devicetree/bindings/sound/imx-audio-es8328.txt | 60 + .../devicetree/bindings/sound/imx-audio-hdmi.yaml | 55 + .../bindings/sound/imx-audio-sgtl5000.txt | 56 + .../devicetree/bindings/sound/imx-audio-spdif.txt | 36 + .../devicetree/bindings/sound/imx-audmux.yaml | 119 + .../devicetree/bindings/sound/ingenic,aic.yaml | 92 + .../devicetree/bindings/sound/ingenic,codec.yaml | 60 + .../devicetree/bindings/sound/inno-rk3036.txt | 20 + .../bindings/sound/intel,keembay-i2s.yaml | 86 + .../devicetree/bindings/sound/linux,bt-sco.yaml | 38 + .../devicetree/bindings/sound/linux,spdif-dit.yaml | 37 + .../bindings/sound/marvell,mmp-sspa.yaml | 101 + .../bindings/sound/marvell,pxa2xx-ac97.txt | 27 + .../devicetree/bindings/sound/max98090.txt | 59 + .../devicetree/bindings/sound/max98095.txt | 22 + .../devicetree/bindings/sound/max98357a.txt | 28 + .../devicetree/bindings/sound/max98371.txt | 17 + .../devicetree/bindings/sound/max98373.txt | 40 + .../devicetree/bindings/sound/max98504.txt | 44 + .../devicetree/bindings/sound/max9860.txt | 28 + .../devicetree/bindings/sound/max9867.txt | 17 + .../devicetree/bindings/sound/max9892x.txt | 44 + .../devicetree/bindings/sound/maxim,max9759.txt | 18 + .../devicetree/bindings/sound/maxim,max98088.txt | 23 + .../devicetree/bindings/sound/maxim,max98390.yaml | 54 + .../devicetree/bindings/sound/maxim,max98520.yaml | 35 + .../devicetree/bindings/sound/mchp,i2s-mcc.yaml | 108 + .../devicetree/bindings/sound/mchp,spdifrx.yaml | 73 + .../devicetree/bindings/sound/mchp,spdiftx.yaml | 75 + .../devicetree/bindings/sound/microchip,pdmc.yaml | 100 + .../bindings/sound/mikroe,mikroe-proto.txt | 23 + .../devicetree/bindings/sound/mrvl,pxa-ssp.txt | 34 + .../devicetree/bindings/sound/mt2701-afe-pcm.txt | 146 + .../devicetree/bindings/sound/mt2701-cs42448.txt | 43 + .../devicetree/bindings/sound/mt2701-wm8960.txt | 24 + Documentation/devicetree/bindings/sound/mt6351.txt | 16 + Documentation/devicetree/bindings/sound/mt6358.txt | 26 + .../devicetree/bindings/sound/mt6359.yaml | 61 + .../devicetree/bindings/sound/mt6797-afe-pcm.txt | 42 + .../devicetree/bindings/sound/mt6797-mt6351.txt | 14 + .../devicetree/bindings/sound/mt8173-max98090.txt | 15 + .../bindings/sound/mt8173-rt5650-rt5514.txt | 15 + .../bindings/sound/mt8173-rt5650-rt5676.txt | 16 + .../devicetree/bindings/sound/mt8173-rt5650.txt | 31 + .../devicetree/bindings/sound/mt8183-afe-pcm.txt | 42 + .../bindings/sound/mt8183-da7219-max98357.txt | 21 + .../sound/mt8183-mt6358-ts3a227-max98357.txt | 25 + .../devicetree/bindings/sound/mt8186-afe-pcm.yaml | 175 + .../sound/mt8186-mt6366-da7219-max98357.yaml | 85 + .../sound/mt8186-mt6366-rt1019-rt5682s.yaml | 85 + .../devicetree/bindings/sound/mt8192-afe-pcm.yaml | 100 + .../sound/mt8192-mt6359-rt1015-rt5682.yaml | 85 + .../devicetree/bindings/sound/mt8195-afe-pcm.yaml | 200 + .../devicetree/bindings/sound/mt8195-mt6359.yaml | 64 + .../devicetree/bindings/sound/mtk-afe-pcm.txt | 45 + .../devicetree/bindings/sound/mtk-btcvsd-snd.txt | 24 + .../devicetree/bindings/sound/mvebu-audio.txt | 34 + .../bindings/sound/mxs-audio-sgtl5000.txt | 42 + .../devicetree/bindings/sound/mxs-saif.txt | 41 + .../devicetree/bindings/sound/name-prefix.yaml | 21 + .../devicetree/bindings/sound/nau8315.txt | 18 + .../devicetree/bindings/sound/nau8540.txt | 16 + .../devicetree/bindings/sound/nau8810.txt | 17 + .../devicetree/bindings/sound/nau8821.txt | 55 + .../devicetree/bindings/sound/nau8822.txt | 16 + .../devicetree/bindings/sound/nau8824.txt | 88 + .../devicetree/bindings/sound/nau8825.txt | 108 + .../devicetree/bindings/sound/nokia,rx51.txt | 27 + .../bindings/sound/nvidia,tegra-audio-alc5632.yaml | 74 + .../bindings/sound/nvidia,tegra-audio-common.yaml | 83 + .../sound/nvidia,tegra-audio-graph-card.yaml | 199 + .../sound/nvidia,tegra-audio-max98090.yaml | 97 + .../bindings/sound/nvidia,tegra-audio-rt5640.yaml | 84 + .../bindings/sound/nvidia,tegra-audio-rt5677.yaml | 100 + .../sound/nvidia,tegra-audio-sgtl5000.yaml | 67 + .../sound/nvidia,tegra-audio-trimslice.yaml | 33 + .../bindings/sound/nvidia,tegra-audio-wm8753.yaml | 79 + .../bindings/sound/nvidia,tegra-audio-wm8903.yaml | 93 + .../bindings/sound/nvidia,tegra-audio-wm9712.yaml | 76 + .../bindings/sound/nvidia,tegra186-asrc.yaml | 81 + .../bindings/sound/nvidia,tegra186-dspk.yaml | 100 + .../bindings/sound/nvidia,tegra20-ac97.txt | 36 + .../bindings/sound/nvidia,tegra20-das.txt | 12 + .../bindings/sound/nvidia,tegra20-i2s.yaml | 77 + .../bindings/sound/nvidia,tegra20-spdif.yaml | 85 + .../bindings/sound/nvidia,tegra210-admaif.yaml | 129 + .../bindings/sound/nvidia,tegra210-adx.yaml | 77 + .../bindings/sound/nvidia,tegra210-ahub.yaml | 196 + .../bindings/sound/nvidia,tegra210-amx.yaml | 79 + .../bindings/sound/nvidia,tegra210-dmic.yaml | 99 + .../bindings/sound/nvidia,tegra210-i2s.yaml | 115 + .../bindings/sound/nvidia,tegra210-mbdrc.yaml | 47 + .../bindings/sound/nvidia,tegra210-mixer.yaml | 75 + .../bindings/sound/nvidia,tegra210-mvc.yaml | 77 + .../bindings/sound/nvidia,tegra210-ope.yaml | 87 + .../bindings/sound/nvidia,tegra210-peq.yaml | 48 + .../bindings/sound/nvidia,tegra210-sfc.yaml | 74 + .../bindings/sound/nvidia,tegra30-ahub.txt | 88 + .../bindings/sound/nvidia,tegra30-hda.yaml | 115 + .../bindings/sound/nvidia,tegra30-i2s.txt | 27 + .../devicetree/bindings/sound/nxp,tfa989x.yaml | 99 + .../devicetree/bindings/sound/omap-abe-twl6040.txt | 91 + .../devicetree/bindings/sound/omap-dmic.txt | 20 + .../devicetree/bindings/sound/omap-mcbsp.txt | 36 + .../devicetree/bindings/sound/omap-mcpdm.txt | 30 + .../devicetree/bindings/sound/omap-twl4030.txt | 62 + .../devicetree/bindings/sound/pcm1789.txt | 22 + .../devicetree/bindings/sound/pcm179x.txt | 27 + .../devicetree/bindings/sound/pcm186x.txt | 42 + .../devicetree/bindings/sound/pcm3060.txt | 23 + .../devicetree/bindings/sound/pcm5102a.txt | 13 + .../devicetree/bindings/sound/pcm512x.txt | 52 + .../devicetree/bindings/sound/qcom,apq8096.txt | 128 + .../devicetree/bindings/sound/qcom,lpass-cpu.yaml | 293 + .../bindings/sound/qcom,lpass-rx-macro.yaml | 80 + .../bindings/sound/qcom,lpass-tx-macro.yaml | 84 + .../bindings/sound/qcom,lpass-va-macro.yaml | 82 + .../bindings/sound/qcom,lpass-wsa-macro.yaml | 73 + .../bindings/sound/qcom,msm8916-wcd-analog.txt | 101 + .../bindings/sound/qcom,msm8916-wcd-digital.txt | 20 + .../bindings/sound/qcom,q6adm-routing.yaml | 52 + .../devicetree/bindings/sound/qcom,q6apm-dai.yaml | 46 + .../devicetree/bindings/sound/qcom,q6asm-dais.yaml | 112 + .../bindings/sound/qcom,q6dsp-lpass-clocks.yaml | 75 + .../bindings/sound/qcom,q6dsp-lpass-ports.yaml | 203 + .../devicetree/bindings/sound/qcom,sm8250.yaml | 314 + .../devicetree/bindings/sound/qcom,wcd9335.txt | 123 + .../devicetree/bindings/sound/qcom,wcd934x.yaml | 206 + .../bindings/sound/qcom,wcd938x-sdw.yaml | 70 + .../devicetree/bindings/sound/qcom,wcd938x.yaml | 153 + .../devicetree/bindings/sound/qcom,wsa881x.yaml | 68 + .../devicetree/bindings/sound/qcom,wsa883x.yaml | 74 + .../devicetree/bindings/sound/realtek,rt1015p.yaml | 43 + .../devicetree/bindings/sound/realtek,rt5682s.yaml | 121 + .../devicetree/bindings/sound/renesas,fsi.yaml | 84 + .../devicetree/bindings/sound/renesas,rsnd.txt | 255 + .../devicetree/bindings/sound/renesas,rsnd.yaml | 463 ++ .../devicetree/bindings/sound/renesas,rz-ssi.yaml | 120 + .../devicetree/bindings/sound/richtek,rt9120.yaml | 59 + .../bindings/sound/rockchip,i2s-tdm.yaml | 182 + .../devicetree/bindings/sound/rockchip,pdm.yaml | 120 + .../bindings/sound/rockchip,rk3288-hdmi-analog.txt | 36 + .../bindings/sound/rockchip,rk3328-codec.yaml | 71 + .../bindings/sound/rockchip,rk3399-gru-sound.txt | 22 + .../devicetree/bindings/sound/rockchip-i2s.yaml | 132 + .../bindings/sound/rockchip-max98090.txt | 42 + .../devicetree/bindings/sound/rockchip-rt5645.txt | 17 + .../devicetree/bindings/sound/rockchip-spdif.yaml | 103 + .../devicetree/bindings/sound/rohm,bd28623.yaml | 67 + Documentation/devicetree/bindings/sound/rt1011.txt | 42 + Documentation/devicetree/bindings/sound/rt1015.txt | 23 + Documentation/devicetree/bindings/sound/rt1016.txt | 17 + .../devicetree/bindings/sound/rt1019.yaml | 35 + Documentation/devicetree/bindings/sound/rt1308.txt | 17 + Documentation/devicetree/bindings/sound/rt274.txt | 33 + Documentation/devicetree/bindings/sound/rt5514.txt | 37 + Documentation/devicetree/bindings/sound/rt5616.txt | 32 + Documentation/devicetree/bindings/sound/rt5631.txt | 48 + Documentation/devicetree/bindings/sound/rt5640.txt | 94 + Documentation/devicetree/bindings/sound/rt5645.txt | 76 + Documentation/devicetree/bindings/sound/rt5651.txt | 63 + Documentation/devicetree/bindings/sound/rt5659.txt | 89 + Documentation/devicetree/bindings/sound/rt5660.txt | 47 + Documentation/devicetree/bindings/sound/rt5663.txt | 60 + Documentation/devicetree/bindings/sound/rt5665.txt | 68 + Documentation/devicetree/bindings/sound/rt5668.txt | 50 + Documentation/devicetree/bindings/sound/rt5677.txt | 78 + Documentation/devicetree/bindings/sound/rt5682.txt | 78 + .../bindings/sound/samsung,aries-wm8994.yaml | 153 + .../devicetree/bindings/sound/samsung,arndale.yaml | 45 + .../bindings/sound/samsung,midas-audio.yaml | 112 + .../devicetree/bindings/sound/samsung,odroid.yaml | 94 + .../bindings/sound/samsung,smdk5250.yaml | 38 + .../devicetree/bindings/sound/samsung,snow.yaml | 76 + .../devicetree/bindings/sound/samsung,tm2.yaml | 80 + .../devicetree/bindings/sound/samsung-i2s.yaml | 149 + .../devicetree/bindings/sound/serial-midi.yaml | 51 + .../devicetree/bindings/sound/sgtl5000.yaml | 110 + .../bindings/sound/simple-audio-amplifier.yaml | 45 + .../bindings/sound/simple-audio-mux.yaml | 40 + .../devicetree/bindings/sound/simple-card.yaml | 500 ++ .../devicetree/bindings/sound/sirf-audio-port.txt | 20 + .../devicetree/bindings/sound/sirf-audio.txt | 41 + .../bindings/sound/snps,designware-i2s.yaml | 94 + .../devicetree/bindings/sound/soc-ac97link.txt | 28 + .../bindings/sound/socionext,uniphier-aio.yaml | 99 + .../bindings/sound/socionext,uniphier-evea.yaml | 72 + .../devicetree/bindings/sound/sound-dai.yaml | 20 + .../devicetree/bindings/sound/spdif-receiver.txt | 10 + .../devicetree/bindings/sound/sprd-mcdt.txt | 19 + .../devicetree/bindings/sound/sprd-pcm.txt | 23 + .../devicetree/bindings/sound/ssm2518.txt | 20 + .../devicetree/bindings/sound/ssm4567.txt | 15 + .../devicetree/bindings/sound/st,sta32x.txt | 101 + .../devicetree/bindings/sound/st,sta350.txt | 131 + .../devicetree/bindings/sound/st,sti-asoc-card.txt | 164 + .../devicetree/bindings/sound/st,stm32-i2s.yaml | 91 + .../devicetree/bindings/sound/st,stm32-sai.yaml | 199 + .../bindings/sound/st,stm32-spdifrx.yaml | 80 + Documentation/devicetree/bindings/sound/storm.txt | 23 + .../devicetree/bindings/sound/tas2552.txt | 36 + .../devicetree/bindings/sound/tas2562.yaml | 80 + .../devicetree/bindings/sound/tas2770.yaml | 84 + .../devicetree/bindings/sound/tas27xx.yaml | 79 + .../devicetree/bindings/sound/tas571x.txt | 48 + .../devicetree/bindings/sound/tas5720.txt | 26 + .../devicetree/bindings/sound/tas5805m.yaml | 56 + .../devicetree/bindings/sound/tda7419.txt | 38 + .../devicetree/bindings/sound/tdm-slot.txt | 29 + .../devicetree/bindings/sound/test-component.yaml | 33 + .../devicetree/bindings/sound/tfa9879.txt | 23 + .../devicetree/bindings/sound/ti,ads117x.txt | 11 + .../bindings/sound/ti,j721e-cpb-audio.yaml | 139 + .../bindings/sound/ti,j721e-cpb-ivi-audio.yaml | 145 + .../devicetree/bindings/sound/ti,pcm1681.txt | 15 + .../devicetree/bindings/sound/ti,pcm3168a.txt | 56 + .../devicetree/bindings/sound/ti,src4xxx.yaml | 48 + .../devicetree/bindings/sound/ti,tas5086.txt | 48 + .../devicetree/bindings/sound/ti,tas6424.txt | 22 + .../bindings/sound/ti,tlv320adc3xxx.yaml | 137 + .../devicetree/bindings/sound/ti,ts3a227e.yaml | 94 + .../devicetree/bindings/sound/tlv320adcx140.yaml | 209 + .../devicetree/bindings/sound/tlv320aic31xx.txt | 77 + .../devicetree/bindings/sound/tlv320aic32x4.txt | 42 + .../devicetree/bindings/sound/tlv320aic3x.txt | 97 + .../devicetree/bindings/sound/tpa6130a2.txt | 27 + .../devicetree/bindings/sound/tscs42xx.txt | 22 + .../devicetree/bindings/sound/tscs454.txt | 23 + .../devicetree/bindings/sound/uda1334.txt | 17 + .../devicetree/bindings/sound/ux500-mop500.txt | 39 + .../devicetree/bindings/sound/ux500-msp.txt | 42 + .../devicetree/bindings/sound/widgets.txt | 20 + .../devicetree/bindings/sound/wlf,arizona.yaml | 116 + .../devicetree/bindings/sound/wlf,wm8731.yaml | 98 + .../devicetree/bindings/sound/wlf,wm8903.yaml | 116 + .../devicetree/bindings/sound/wlf,wm8940.yaml | 57 + .../devicetree/bindings/sound/wlf,wm8962.yaml | 121 + .../devicetree/bindings/sound/wlf,wm8974.txt | 15 + .../devicetree/bindings/sound/wlf,wm8978.yaml | 58 + Documentation/devicetree/bindings/sound/wm8510.txt | 18 + Documentation/devicetree/bindings/sound/wm8523.txt | 16 + Documentation/devicetree/bindings/sound/wm8524.txt | 16 + Documentation/devicetree/bindings/sound/wm8580.txt | 16 + Documentation/devicetree/bindings/sound/wm8711.txt | 18 + Documentation/devicetree/bindings/sound/wm8728.txt | 18 + Documentation/devicetree/bindings/sound/wm8737.txt | 18 + Documentation/devicetree/bindings/sound/wm8741.txt | 29 + .../devicetree/bindings/sound/wm8750.yaml | 42 + Documentation/devicetree/bindings/sound/wm8753.txt | 40 + Documentation/devicetree/bindings/sound/wm8770.txt | 16 + Documentation/devicetree/bindings/sound/wm8776.txt | 18 + Documentation/devicetree/bindings/sound/wm8782.txt | 17 + Documentation/devicetree/bindings/sound/wm8804.txt | 25 + Documentation/devicetree/bindings/sound/wm8904.txt | 33 + Documentation/devicetree/bindings/sound/wm8960.txt | 42 + Documentation/devicetree/bindings/sound/wm8994.txt | 112 + .../bindings/sound/xlnx,audio-formatter.txt | 29 + .../devicetree/bindings/sound/xlnx,i2s.txt | 28 + .../devicetree/bindings/sound/xlnx,spdif.txt | 28 + .../devicetree/bindings/sound/zl38060.yaml | 69 + .../devicetree/bindings/soundwire/qcom,sdw.txt | 214 + .../bindings/soundwire/soundwire-controller.yaml | 86 + .../devicetree/bindings/spi/adi,axi-spi-engine.txt | 31 + .../bindings/spi/allwinner,sun4i-a10-spi.yaml | 87 + .../bindings/spi/allwinner,sun6i-a31-spi.yaml | 114 + .../bindings/spi/amlogic,meson-gx-spicc.yaml | 97 + .../bindings/spi/amlogic,meson6-spifc.yaml | 54 + .../bindings/spi/aspeed,ast2600-fmc.yaml | 82 + .../bindings/spi/atmel,at91rm9200-spi.yaml | 85 + .../devicetree/bindings/spi/atmel,quadspi.yaml | 99 + .../bindings/spi/brcm,bcm2835-aux-spi.txt | 38 + .../devicetree/bindings/spi/brcm,bcm2835-spi.txt | 23 + .../devicetree/bindings/spi/brcm,spi-bcm-qspi.yaml | 196 + .../spi/cdns,qspi-nor-peripheral-props.yaml | 42 + .../devicetree/bindings/spi/cdns,qspi-nor.yaml | 123 + .../devicetree/bindings/spi/cdns,xspi.yaml | 77 + .../devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml | 96 + .../devicetree/bindings/spi/fsl-imx-cspi.yaml | 97 + Documentation/devicetree/bindings/spi/fsl-spi.txt | 62 + .../devicetree/bindings/spi/hpe,gxp-spifi.yaml | 56 + .../bindings/spi/icpdas-lp8841-spi-rtc.txt | 54 + .../devicetree/bindings/spi/ingenic,spi.yaml | 75 + .../devicetree/bindings/spi/jcore,spi.txt | 34 + .../devicetree/bindings/spi/marvell,mmp2-ssp.yaml | 58 + .../bindings/spi/mediatek,spi-mt65xx.yaml | 113 + .../bindings/spi/mediatek,spi-mtk-nor.yaml | 99 + .../bindings/spi/mediatek,spi-mtk-snfi.yaml | 88 + .../bindings/spi/mediatek,spi-slave-mt27xx.yaml | 58 + .../bindings/spi/microchip,mpfs-spi.yaml | 58 + .../bindings/spi/microchip,spi-pic32.txt | 34 + .../bindings/spi/mikrotik,rb4xx-spi.yaml | 38 + .../devicetree/bindings/spi/mxicy,mx25f0a-spi.yaml | 65 + Documentation/devicetree/bindings/spi/mxs-spi.yaml | 56 + .../devicetree/bindings/spi/nuvoton,npcm-fiu.txt | 58 + .../devicetree/bindings/spi/nuvoton,npcm-pspi.txt | 36 + .../bindings/spi/nvidia,tegra114-spi.txt | 61 + .../bindings/spi/nvidia,tegra20-sflash.txt | 37 + .../bindings/spi/nvidia,tegra20-slink.txt | 37 + .../spi/nvidia,tegra210-quad-peripheral-props.yaml | 32 + .../bindings/spi/nvidia,tegra210-quad.yaml | 98 + .../devicetree/bindings/spi/omap-spi.yaml | 117 + .../devicetree/bindings/spi/qca,ar934x-spi.yaml | 43 + .../bindings/spi/qcom,spi-geni-qcom.yaml | 118 + .../bindings/spi/qcom,spi-qcom-qspi.yaml | 94 + .../devicetree/bindings/spi/qcom,spi-qup.yaml | 81 + .../devicetree/bindings/spi/ralink,mt7621-spi.yaml | 61 + .../devicetree/bindings/spi/realtek,rtl-spi.yaml | 41 + .../devicetree/bindings/spi/renesas,hspi.yaml | 58 + .../devicetree/bindings/spi/renesas,rspi.yaml | 155 + .../devicetree/bindings/spi/renesas,sh-msiof.yaml | 171 + .../devicetree/bindings/spi/rockchip-sfc.yaml | 91 + .../bindings/spi/samsung,spi-peripheral-props.yaml | 33 + .../devicetree/bindings/spi/samsung,spi.yaml | 192 + .../devicetree/bindings/spi/snps,dw-apb-ssi.yaml | 186 + .../bindings/spi/socionext,uniphier-spi.yaml | 59 + .../devicetree/bindings/spi/spi-armada-3700.txt | 25 + .../devicetree/bindings/spi/spi-ath79.txt | 24 + .../devicetree/bindings/spi/spi-bcm63xx-hsspi.txt | 33 + .../devicetree/bindings/spi/spi-bcm63xx.txt | 33 + Documentation/devicetree/bindings/spi/spi-bus.txt | 1 + .../devicetree/bindings/spi/spi-cadence.yaml | 73 + .../devicetree/bindings/spi/spi-clps711x.txt | 32 + .../devicetree/bindings/spi/spi-controller.yaml | 163 + .../devicetree/bindings/spi/spi-davinci.txt | 100 + .../devicetree/bindings/spi/spi-fsl-dspi.txt | 65 + .../devicetree/bindings/spi/spi-fsl-lpspi.yaml | 83 + .../devicetree/bindings/spi/spi-gpio.yaml | 74 + .../devicetree/bindings/spi/spi-img-spfi.txt | 39 + .../devicetree/bindings/spi/spi-lantiq-ssc.txt | 46 + Documentation/devicetree/bindings/spi/spi-mux.yaml | 88 + .../devicetree/bindings/spi/spi-nxp-fspi.yaml | 87 + .../devicetree/bindings/spi/spi-octeon.txt | 33 + .../devicetree/bindings/spi/spi-orion.txt | 79 + .../bindings/spi/spi-peripheral-props.yaml | 107 + .../devicetree/bindings/spi/spi-pl022.yaml | 161 + .../devicetree/bindings/spi/spi-rockchip.yaml | 116 + .../devicetree/bindings/spi/spi-sc18is602.txt | 23 + .../devicetree/bindings/spi/spi-sifive.yaml | 87 + Documentation/devicetree/bindings/spi/spi-sprd.txt | 33 + .../devicetree/bindings/spi/spi-st-ssc.txt | 40 + .../bindings/spi/spi-sunplus-sp7021.yaml | 78 + .../devicetree/bindings/spi/spi-synquacer.txt | 27 + .../devicetree/bindings/spi/spi-xilinx.yaml | 55 + .../devicetree/bindings/spi/spi-xtensa-xtfpga.txt | 9 + .../devicetree/bindings/spi/spi-zynqmp-qspi.yaml | 58 + .../devicetree/bindings/spi/spi_altera.txt | 5 + .../devicetree/bindings/spi/spi_oc_tiny.txt | 12 + .../devicetree/bindings/spi/sprd,spi-adi.yaml | 104 + .../devicetree/bindings/spi/sqi-pic32.txt | 18 + .../devicetree/bindings/spi/st,stm32-qspi.yaml | 85 + .../devicetree/bindings/spi/st,stm32-spi.yaml | 101 + Documentation/devicetree/bindings/spi/ti_qspi.txt | 53 + .../devicetree/bindings/spi/xlnx,zynq-qspi.yaml | 59 + .../spmi/hisilicon,hisi-spmi-controller.yaml | 73 + .../bindings/spmi/mtk,spmi-mtk-pmif.yaml | 76 + .../bindings/spmi/qcom,spmi-pmic-arb.yaml | 117 + Documentation/devicetree/bindings/spmi/spmi.yaml | 75 + .../sram/allwinner,sun4i-a10-system-control.yaml | 132 + .../devicetree/bindings/sram/qcom,imem.yaml | 75 + .../devicetree/bindings/sram/qcom,ocmem.yaml | 98 + Documentation/devicetree/bindings/sram/sram.yaml | 299 + .../bindings/staging/iio/adc/spear-adc.txt | 24 + .../devicetree/bindings/submitting-patches.rst | 96 + .../bindings/thermal/allwinner,sun8i-a83t-ths.yaml | 162 + .../bindings/thermal/amazon,al-thermal.txt | 33 + .../bindings/thermal/amlogic,thermal.yaml | 58 + .../devicetree/bindings/thermal/armada-thermal.txt | 41 + .../bindings/thermal/brcm,avs-ro-thermal.yaml | 48 + .../devicetree/bindings/thermal/brcm,avs-tmon.yaml | 56 + .../bindings/thermal/brcm,bcm2835-thermal.txt | 41 + .../bindings/thermal/brcm,ns-thermal.yaml | 60 + .../bindings/thermal/brcm,sr-thermal.txt | 105 + .../devicetree/bindings/thermal/da9062-thermal.txt | 36 + .../devicetree/bindings/thermal/db8500-thermal.txt | 44 + .../devicetree/bindings/thermal/dove-thermal.txt | 18 + .../bindings/thermal/fsl,scu-thermal.yaml | 38 + .../bindings/thermal/hisilicon-thermal.txt | 32 + .../devicetree/bindings/thermal/imx-thermal.yaml | 102 + .../bindings/thermal/imx8mm-thermal.yaml | 62 + .../bindings/thermal/kirkwood-thermal.txt | 15 + .../bindings/thermal/max77620_thermal.txt | 70 + .../bindings/thermal/mediatek-thermal.txt | 49 + .../bindings/thermal/nvidia,tegra124-soctherm.txt | 238 + .../thermal/nvidia,tegra186-bpmp-thermal.yaml | 42 + .../bindings/thermal/nvidia,tegra30-tsensor.yaml | 73 + .../bindings/thermal/qcom,spmi-temp-alarm.yaml | 85 + .../devicetree/bindings/thermal/qcom-lmh.yaml | 84 + .../bindings/thermal/qcom-spmi-adc-tm-hc.yaml | 149 + .../bindings/thermal/qcom-spmi-adc-tm5.yaml | 257 + .../devicetree/bindings/thermal/qcom-tsens.yaml | 229 + .../devicetree/bindings/thermal/qoriq-thermal.yaml | 114 + .../bindings/thermal/rcar-gen3-thermal.yaml | 147 + .../devicetree/bindings/thermal/rcar-thermal.yaml | 155 + .../bindings/thermal/rockchip-thermal.yaml | 99 + .../devicetree/bindings/thermal/rzg2l-thermal.yaml | 78 + .../bindings/thermal/samsung,exynos-thermal.yaml | 184 + .../thermal/socionext,uniphier-thermal.yaml | 59 + .../devicetree/bindings/thermal/spear-thermal.txt | 14 + .../devicetree/bindings/thermal/sprd-thermal.yaml | 111 + .../bindings/thermal/st,stm32-thermal.yaml | 79 + .../devicetree/bindings/thermal/st-thermal.txt | 32 + .../bindings/thermal/thermal-cooling-devices.yaml | 118 + .../bindings/thermal/thermal-generic-adc.txt | 95 + .../devicetree/bindings/thermal/thermal-idle.yaml | 146 + .../bindings/thermal/thermal-sensor.yaml | 77 + .../devicetree/bindings/thermal/thermal-zones.yaml | 343 + .../bindings/thermal/ti,am654-thermal.yaml | 56 + .../bindings/thermal/ti,j72xx-thermal.yaml | 63 + .../devicetree/bindings/thermal/ti_soc_thermal.txt | 88 + .../bindings/timer/actions,owl-timer.txt | 21 + .../bindings/timer/allwinner,sun4i-a10-timer.yaml | 101 + .../timer/allwinner,sun5i-a13-hstimer.yaml | 77 + .../devicetree/bindings/timer/altr,timer-1.0.txt | 18 + .../bindings/timer/amlogic,meson6-timer.txt | 22 + .../devicetree/bindings/timer/arm,arch_timer.yaml | 128 + .../bindings/timer/arm,arch_timer_mmio.yaml | 123 + .../bindings/timer/arm,armv7m-systick.yaml | 54 + .../bindings/timer/arm,global_timer.yaml | 48 + .../devicetree/bindings/timer/arm,mps2-timer.txt | 28 + .../devicetree/bindings/timer/arm,sp804.yaml | 97 + .../devicetree/bindings/timer/arm,twd-timer.yaml | 56 + .../bindings/timer/brcm,bcm2835-system-timer.txt | 22 + .../devicetree/bindings/timer/brcm,kona-timer.txt | 25 + .../devicetree/bindings/timer/cdns,ttc.yaml | 52 + .../bindings/timer/cirrus,clps711x-timer.txt | 29 + .../bindings/timer/csky,gx6605s-timer.txt | 42 + .../devicetree/bindings/timer/csky,mptimer.txt | 42 + .../devicetree/bindings/timer/digicolor-timer.txt | 18 + .../bindings/timer/ezchip,nps400-timer0.txt | 17 + .../bindings/timer/ezchip,nps400-timer1.txt | 15 + .../devicetree/bindings/timer/faraday,fttmr010.txt | 38 + .../devicetree/bindings/timer/fsl,ftm-timer.txt | 31 + .../devicetree/bindings/timer/fsl,gtm.txt | 30 + .../devicetree/bindings/timer/fsl,imxgpt.yaml | 72 + .../devicetree/bindings/timer/hpe,gxp-timer.yaml | 47 + .../bindings/timer/img,pistachio-gptimer.txt | 28 + .../devicetree/bindings/timer/ingenic,sysost.yaml | 63 + .../devicetree/bindings/timer/ingenic,tcu.yaml | 302 + .../bindings/timer/intel,ixp4xx-timer.yaml | 43 + .../devicetree/bindings/timer/jcore,pit.txt | 24 + .../devicetree/bindings/timer/lsi,zevio-timer.txt | 33 + .../bindings/timer/marvell,armada-370-xp-timer.txt | 44 + .../bindings/timer/marvell,orion-timer.txt | 16 + .../bindings/timer/mediatek,mtk-timer.txt | 47 + .../devicetree/bindings/timer/mrvl,mmp-timer.yaml | 46 + .../bindings/timer/mstar,msc313e-timer.yaml | 46 + .../bindings/timer/nuvoton,npcm7xx-timer.yaml | 48 + .../bindings/timer/nvidia,tegra-timer.yaml | 150 + .../bindings/timer/nvidia,tegra186-timer.yaml | 109 + .../bindings/timer/nxp,lpc3220-timer.txt | 26 + .../bindings/timer/nxp,sysctr-timer.yaml | 58 + .../devicetree/bindings/timer/nxp,tpm-timer.yaml | 65 + .../devicetree/bindings/timer/oxsemi,rps-timer.txt | 17 + .../devicetree/bindings/timer/qcom,msm-timer.txt | 47 + .../bindings/timer/rda,8810pl-timer.yaml | 47 + .../devicetree/bindings/timer/renesas,cmt.yaml | 202 + .../devicetree/bindings/timer/renesas,em-sti.yaml | 46 + .../devicetree/bindings/timer/renesas,mtu2.yaml | 76 + .../devicetree/bindings/timer/renesas,ostm.yaml | 77 + .../devicetree/bindings/timer/renesas,tmu.yaml | 107 + .../devicetree/bindings/timer/renesas,tpu.yaml | 56 + .../bindings/timer/rockchip,rk-timer.yaml | 63 + .../bindings/timer/samsung,exynos4210-mct.yaml | 237 + .../devicetree/bindings/timer/sifive,clint.yaml | 72 + .../devicetree/bindings/timer/snps,arc-timer.txt | 27 + .../devicetree/bindings/timer/snps,archs-gfrc.txt | 14 + .../devicetree/bindings/timer/snps,archs-rtc.txt | 14 + .../bindings/timer/snps,dw-apb-timer.yaml | 84 + .../bindings/timer/socionext,milbeaut-timer.txt | 17 + .../bindings/timer/spreadtrum,sprd-timer.txt | 20 + .../devicetree/bindings/timer/st,nomadik-mtu.yaml | 58 + .../devicetree/bindings/timer/st,spear-timer.txt | 16 + .../devicetree/bindings/timer/st,stih407-lpc | 28 + .../devicetree/bindings/timer/st,stm32-timer.yaml | 48 + .../devicetree/bindings/timer/ti,davinci-timer.txt | 37 + .../bindings/timer/ti,keystone-timer.txt | 29 + .../devicetree/bindings/timer/ti,timer-dm.yaml | 159 + .../devicetree/bindings/timer/via,vt8500-timer.txt | 15 + .../devicetree/bindings/timer/xlnx,xps-timer.yaml | 92 + .../timestamp/hardware-timestamps-common.yaml | 29 + .../bindings/timestamp/hte-consumer.yaml | 39 + .../bindings/timestamp/nvidia,tegra194-hte.yaml | 88 + .../devicetree/bindings/trivial-devices.yaml | 395 + .../devicetree/bindings/ufs/cdns,ufshc.yaml | 71 + .../devicetree/bindings/ufs/hisilicon,ufs.yaml | 90 + .../devicetree/bindings/ufs/mediatek,ufs.yaml | 67 + .../devicetree/bindings/ufs/qcom,ufs.yaml | 246 + .../devicetree/bindings/ufs/renesas,ufs.yaml | 61 + .../bindings/ufs/samsung,exynos-ufs.yaml | 95 + .../devicetree/bindings/ufs/snps,tc-dwc-g210.yaml | 51 + .../devicetree/bindings/ufs/ti,j721e-ufs.yaml | 90 + .../devicetree/bindings/ufs/ufs-common.yaml | 82 + Documentation/devicetree/bindings/unittest.txt | 66 + .../bindings/usb/allwinner,sun4i-a10-musb.yaml | 104 + .../devicetree/bindings/usb/am33xx-usb.txt | 200 + .../bindings/usb/amlogic,meson-g12a-usb-ctrl.yaml | 236 + .../devicetree/bindings/usb/analogix,anx7411.yaml | 83 + .../bindings/usb/aspeed,ast2600-udc.yaml | 52 + .../devicetree/bindings/usb/aspeed,usb-vhub.yaml | 139 + .../devicetree/bindings/usb/atmel-usb.txt | 125 + .../devicetree/bindings/usb/brcm,bcm3384-usb.txt | 11 + .../devicetree/bindings/usb/brcm,bcm7445-ehci.yaml | 59 + .../devicetree/bindings/usb/brcm,bdc.yaml | 50 + .../devicetree/bindings/usb/brcm,usb-pinmap.yaml | 73 + .../devicetree/bindings/usb/cdns,usb3.yaml | 102 + .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 158 + .../devicetree/bindings/usb/da8xx-usb.txt | 81 + Documentation/devicetree/bindings/usb/dwc2.yaml | 193 + .../devicetree/bindings/usb/dwc3-cavium.txt | 28 + Documentation/devicetree/bindings/usb/dwc3-st.txt | 66 + .../devicetree/bindings/usb/dwc3-xilinx.yaml | 135 + .../devicetree/bindings/usb/ehci-omap.txt | 31 + .../devicetree/bindings/usb/ehci-orion.txt | 22 + Documentation/devicetree/bindings/usb/ehci-st.txt | 38 + .../devicetree/bindings/usb/faraday,fotg210.yaml | 77 + .../devicetree/bindings/usb/fcs,fsa4480.yaml | 72 + .../devicetree/bindings/usb/fcs,fusb302.txt | 34 + .../devicetree/bindings/usb/fsl,imx8mp-dwc3.yaml | 125 + Documentation/devicetree/bindings/usb/fsl-usb.txt | 81 + .../devicetree/bindings/usb/generic-ehci.yaml | 176 + .../devicetree/bindings/usb/generic-ohci.yaml | 139 + .../devicetree/bindings/usb/generic-xhci.yaml | 65 + Documentation/devicetree/bindings/usb/gr-udc.txt | 34 + .../bindings/usb/hisilicon,histb-xhci.txt | 45 + .../devicetree/bindings/usb/ingenic,musb.yaml | 79 + .../bindings/usb/intel,keembay-dwc3.yaml | 77 + .../devicetree/bindings/usb/iproc-udc.txt | 21 + Documentation/devicetree/bindings/usb/isp1301.txt | 24 + .../devicetree/bindings/usb/lpc32xx-udc.txt | 28 + .../bindings/usb/marvell,pxau2o-ehci.yaml | 62 + .../devicetree/bindings/usb/maxim,max33359.yaml | 75 + .../devicetree/bindings/usb/maxim,max3420-udc.yaml | 67 + .../devicetree/bindings/usb/maxim,max3421.txt | 23 + .../bindings/usb/mediatek,mt6360-tcpc.yaml | 100 + .../bindings/usb/mediatek,mt6370-tcpc.yaml | 36 + .../devicetree/bindings/usb/mediatek,mtk-xhci.yaml | 219 + .../devicetree/bindings/usb/mediatek,mtu3.yaml | 333 + .../devicetree/bindings/usb/mediatek,musb.yaml | 115 + .../bindings/usb/microchip,mpfs-musb.yaml | 59 + .../devicetree/bindings/usb/msm-hsusb.txt | 110 + .../devicetree/bindings/usb/npcm7xx-usb.txt | 20 + .../devicetree/bindings/usb/nvidia,tegra-xudc.yaml | 201 + .../bindings/usb/nvidia,tegra124-xusb.txt | 132 + .../bindings/usb/nvidia,tegra20-ehci.txt | 23 + .../devicetree/bindings/usb/nxp,isp1760.yaml | 67 + .../devicetree/bindings/usb/octeon-usb.txt | 62 + .../devicetree/bindings/usb/ohci-da8xx.txt | 23 + Documentation/devicetree/bindings/usb/ohci-nxp.txt | 24 + .../devicetree/bindings/usb/ohci-omap3.txt | 15 + Documentation/devicetree/bindings/usb/ohci-st.txt | 36 + Documentation/devicetree/bindings/usb/omap-usb.txt | 80 + Documentation/devicetree/bindings/usb/pxa-usb.txt | 53 + .../devicetree/bindings/usb/qcom,dwc3.yaml | 504 ++ .../devicetree/bindings/usb/realtek,rts5411.yaml | 62 + .../devicetree/bindings/usb/renesas,usb-xhci.yaml | 86 + .../devicetree/bindings/usb/renesas,usb3-peri.yaml | 182 + .../devicetree/bindings/usb/renesas,usbhs.yaml | 153 + .../devicetree/bindings/usb/richtek,rt1711h.txt | 44 + .../devicetree/bindings/usb/richtek,rt1711h.yaml | 100 + .../devicetree/bindings/usb/richtek,rt1719.yaml | 85 + .../devicetree/bindings/usb/rockchip,dwc3.yaml | 110 + .../devicetree/bindings/usb/s3c2410-usb.txt | 22 + .../bindings/usb/samsung,exynos-dwc3.yaml | 129 + .../bindings/usb/samsung,exynos-usb2.yaml | 107 + .../devicetree/bindings/usb/samsung-hsotg.txt | 38 + .../devicetree/bindings/usb/smsc,usb3503.yaml | 109 + .../devicetree/bindings/usb/snps,dwc3.yaml | 391 + .../devicetree/bindings/usb/spear-usb.txt | 35 + .../devicetree/bindings/usb/st,stusb160x.yaml | 91 + .../devicetree/bindings/usb/st,typec-stm32g0.yaml | 91 + .../devicetree/bindings/usb/ti,am62-usb.yaml | 103 + .../devicetree/bindings/usb/ti,hd3ss3220.yaml | 82 + .../devicetree/bindings/usb/ti,j721e-usb.yaml | 119 + .../devicetree/bindings/usb/ti,keystone-dwc3.yaml | 100 + .../devicetree/bindings/usb/ti,tps6598x.yaml | 70 + .../devicetree/bindings/usb/ti,usb8041.yaml | 67 + .../devicetree/bindings/usb/twlxxxx-usb.txt | 43 + .../devicetree/bindings/usb/typec-tcpci.txt | 49 + Documentation/devicetree/bindings/usb/ulpi.txt | 20 + .../devicetree/bindings/usb/usb-device.yaml | 124 + Documentation/devicetree/bindings/usb/usb-drd.yaml | 78 + Documentation/devicetree/bindings/usb/usb-hcd.yaml | 52 + .../devicetree/bindings/usb/usb-nop-xceiv.yaml | 64 + Documentation/devicetree/bindings/usb/usb-uhci.txt | 18 + .../devicetree/bindings/usb/usb-xhci.yaml | 42 + Documentation/devicetree/bindings/usb/usb.yaml | 62 + Documentation/devicetree/bindings/usb/usb251xb.txt | 89 + Documentation/devicetree/bindings/usb/usb4604.txt | 19 + .../devicetree/bindings/usb/usbmisc-imx.txt | 18 + .../devicetree/bindings/usb/ux500-usb.txt | 50 + .../devicetree/bindings/usb/willsemi,wusb3801.yaml | 76 + .../devicetree/bindings/usb/xlnx,usb2.yaml | 47 + .../devicetree/bindings/vendor-prefixes.yaml | 1520 ++++ Documentation/devicetree/bindings/virtio/mmio.yaml | 67 + .../devicetree/bindings/virtio/pci-iommu.yaml | 101 + .../devicetree/bindings/virtio/virtio-device.yaml | 41 + .../devicetree/bindings/w1/fsl-imx-owire.yaml | 44 + Documentation/devicetree/bindings/w1/omap-hdq.txt | 22 + Documentation/devicetree/bindings/w1/w1-gpio.yaml | 43 + Documentation/devicetree/bindings/w1/w1.txt | 25 + .../bindings/watchdog/allwinner,sun4i-a10-wdt.yaml | 96 + .../bindings/watchdog/alphascale-asm9260.txt | 35 + .../bindings/watchdog/amlogic,meson-gxbb-wdt.yaml | 42 + .../devicetree/bindings/watchdog/apple,wdt.yaml | 52 + .../bindings/watchdog/arm,sbsa-gwdt.yaml | 51 + .../devicetree/bindings/watchdog/arm,sp805.yaml | 71 + .../devicetree/bindings/watchdog/arm,twd-wdt.yaml | 50 + .../devicetree/bindings/watchdog/arm-smc-wdt.yaml | 38 + .../bindings/watchdog/armada-37xx-wdt.txt | 23 + .../devicetree/bindings/watchdog/aspeed-wdt.txt | 57 + .../bindings/watchdog/atmel,at91sam9-wdt.yaml | 127 + .../bindings/watchdog/atmel,sama5d4-wdt.yaml | 77 + .../bindings/watchdog/atmel-at91rm9200-wdt.txt | 9 + .../bindings/watchdog/brcm,bcm2835-pm-wdog.txt | 18 + .../bindings/watchdog/brcm,bcm7038-wdt.yaml | 43 + .../devicetree/bindings/watchdog/brcm,kona-wdt.txt | 15 + .../devicetree/bindings/watchdog/cadence-wdt.txt | 23 + .../devicetree/bindings/watchdog/da9062-wdt.txt | 34 + .../devicetree/bindings/watchdog/davinci-wdt.txt | 24 + .../devicetree/bindings/watchdog/digicolor-wdt.txt | 25 + .../bindings/watchdog/faraday,ftwdt010.yaml | 67 + .../devicetree/bindings/watchdog/fsl,scu-wdt.yaml | 34 + .../devicetree/bindings/watchdog/fsl-imx-wdt.yaml | 77 + .../bindings/watchdog/fsl-imx7ulp-wdt.yaml | 58 + .../devicetree/bindings/watchdog/gpio-wdt.txt | 28 + .../devicetree/bindings/watchdog/imgpdc-wdt.txt | 19 + .../bindings/watchdog/intel,keembay-wdt.yaml | 57 + .../bindings/watchdog/kontron,sl28cpld-wdt.yaml | 35 + .../devicetree/bindings/watchdog/lantiq-wdt.txt | 24 + .../devicetree/bindings/watchdog/lpc18xx-wdt.txt | 19 + .../devicetree/bindings/watchdog/marvel.txt | 45 + .../bindings/watchdog/maxim,max63xx.yaml | 44 + .../bindings/watchdog/mediatek,mt7621-wdt.yaml | 33 + .../devicetree/bindings/watchdog/men-a021-wdt.txt | 25 + .../devicetree/bindings/watchdog/meson-wdt.txt | 21 + .../bindings/watchdog/microchip,pic32-dmt.txt | 19 + .../bindings/watchdog/microchip,pic32-wdt.txt | 18 + .../bindings/watchdog/moxa,moxart-watchdog.txt | 15 + .../devicetree/bindings/watchdog/mpc8xxx-wdt.txt | 25 + .../bindings/watchdog/mstar,msc313e-wdt.yaml | 40 + .../devicetree/bindings/watchdog/mtk-wdt.txt | 42 + .../bindings/watchdog/nuvoton,npcm-wdt.txt | 30 + .../devicetree/bindings/watchdog/omap-wdt.txt | 15 + .../devicetree/bindings/watchdog/pnx4008-wdt.txt | 17 + .../bindings/watchdog/qca-ar7130-wdt.txt | 13 + .../bindings/watchdog/qcom,pm8916-wdt.yaml | 51 + .../devicetree/bindings/watchdog/qcom-wdt.yaml | 62 + .../bindings/watchdog/realtek,otto-wdt.yaml | 92 + .../bindings/watchdog/realtek,rtd119x.txt | 17 + .../devicetree/bindings/watchdog/renesas,wdt.yaml | 187 + .../devicetree/bindings/watchdog/rt2880-wdt.txt | 18 + .../devicetree/bindings/watchdog/samsung-wdt.yaml | 117 + .../devicetree/bindings/watchdog/snps,dw-wdt.yaml | 106 + .../bindings/watchdog/socionext,uniphier-wdt.yaml | 36 + .../devicetree/bindings/watchdog/sprd-wdt.txt | 19 + .../bindings/watchdog/st,stm32-iwdg.yaml | 58 + .../devicetree/bindings/watchdog/st_lpc_wdt.txt | 41 + .../bindings/watchdog/sunplus,sp7021-wdt.yaml | 47 + .../devicetree/bindings/watchdog/ti,rti-wdt.yaml | 61 + .../bindings/watchdog/toshiba,visconti-wdt.yaml | 50 + .../devicetree/bindings/watchdog/ts4800-wdt.txt | 25 + .../devicetree/bindings/watchdog/twl4030-wdt.txt | 10 + .../devicetree/bindings/watchdog/watchdog.yaml | 27 + .../bindings/watchdog/xlnx,xps-timebase-wdt.yaml | 68 + .../bindings/watchdog/zii,rave-sp-wdt.txt | 39 + .../devicetree/bindings/watchdog/ziirave-wdt.txt | 19 + .../devicetree/bindings/writing-bindings.rst | 93 + .../devicetree/bindings/writing-schema.rst | 186 + Documentation/devicetree/bindings/x86/ce4100.txt | 57 + Documentation/devicetree/bindings/x86/timer.txt | 6 + Documentation/devicetree/bindings/xilinx.txt | 165 + .../devicetree/bindings/xillybus/xillybus.txt | 18 + Documentation/devicetree/changesets.rst | 37 + .../devicetree/dynamic-resolution-notes.rst | 27 + Documentation/devicetree/index.rst | 30 + Documentation/devicetree/kernel-api.rst | 57 + Documentation/devicetree/of_unittest.rst | 226 + Documentation/devicetree/overlay-notes.rst | 150 + Documentation/devicetree/usage-model.rst | 420 + Documentation/doc-guide/contributing.rst | 296 + Documentation/doc-guide/hello.dot | 3 + Documentation/doc-guide/index.rst | 21 + Documentation/doc-guide/kernel-doc.rst | 552 ++ Documentation/doc-guide/maintainer-profile.rst | 45 + Documentation/doc-guide/parse-headers.rst | 192 + Documentation/doc-guide/sphinx.rst | 527 ++ Documentation/doc-guide/svg_image.svg | 10 + Documentation/docutils.conf | 7 + Documentation/dontdiff | 271 + Documentation/driver-api/80211/cfg80211.rst | 178 + Documentation/driver-api/80211/index.rst | 17 + Documentation/driver-api/80211/introduction.rst | 17 + .../driver-api/80211/mac80211-advanced.rst | 239 + Documentation/driver-api/80211/mac80211.rst | 155 + Documentation/driver-api/acpi/index.rst | 9 + Documentation/driver-api/acpi/linuxized-acpica.rst | 279 + Documentation/driver-api/acpi/scan_handlers.rst | 83 + Documentation/driver-api/aperture.rst | 13 + Documentation/driver-api/auxiliary_bus.rst | 50 + .../driver-api/backlight/lp855x-driver.rst | 81 + Documentation/driver-api/basics.rst | 115 + Documentation/driver-api/clk.rst | 307 + Documentation/driver-api/component.rst | 19 + Documentation/driver-api/connector.rst | 157 + Documentation/driver-api/console.rst | 152 + Documentation/driver-api/cxl/index.rst | 12 + Documentation/driver-api/cxl/memory-devices.rst | 383 + Documentation/driver-api/dcdbas.rst | 99 + Documentation/driver-api/devfreq.rst | 30 + Documentation/driver-api/device-io.rst | 521 ++ Documentation/driver-api/device_link.rst | 320 + Documentation/driver-api/dma-buf.rst | 348 + Documentation/driver-api/dmaengine/client.rst | 379 + Documentation/driver-api/dmaengine/dmatest.rst | 232 + Documentation/driver-api/dmaengine/index.rst | 55 + Documentation/driver-api/dmaengine/provider.rst | 647 ++ Documentation/driver-api/dmaengine/pxa_dma.rst | 190 + Documentation/driver-api/driver-model/binding.rst | 98 + Documentation/driver-api/driver-model/bus.rst | 146 + .../driver-api/driver-model/design-patterns.rst | 116 + Documentation/driver-api/driver-model/device.rst | 120 + Documentation/driver-api/driver-model/devres.rst | 448 ++ Documentation/driver-api/driver-model/driver.rst | 286 + Documentation/driver-api/driver-model/index.rst | 23 + Documentation/driver-api/driver-model/overview.rst | 124 + Documentation/driver-api/driver-model/platform.rst | 246 + Documentation/driver-api/driver-model/porting.rst | 448 ++ .../driver-api/early-userspace/buffer-format.rst | 119 + .../early-userspace/early_userspace_support.rst | 154 + Documentation/driver-api/early-userspace/index.rst | 18 + Documentation/driver-api/edac.rst | 178 + Documentation/driver-api/eisa.rst | 230 + Documentation/driver-api/firewire.rst | 48 + Documentation/driver-api/firmware/built-in-fw.rst | 33 + Documentation/driver-api/firmware/core.rst | 17 + .../driver-api/firmware/direct-fs-lookup.rst | 30 + Documentation/driver-api/firmware/efi/index.rst | 11 + .../driver-api/firmware/fallback-mechanisms.rst | 308 + .../firmware/firmware-usage-guidelines.rst | 44 + .../driver-api/firmware/firmware_cache.rst | 51 + .../driver-api/firmware/fw_search_path.rst | 26 + Documentation/driver-api/firmware/fw_upload.rst | 126 + Documentation/driver-api/firmware/index.rst | 19 + Documentation/driver-api/firmware/introduction.rst | 27 + Documentation/driver-api/firmware/lookup-order.rst | 20 + .../driver-api/firmware/other_interfaces.rst | 51 + .../driver-api/firmware/request_firmware.rst | 80 + Documentation/driver-api/fpga/fpga-bridge.rst | 22 + Documentation/driver-api/fpga/fpga-mgr.rst | 162 + Documentation/driver-api/fpga/fpga-programming.rst | 107 + Documentation/driver-api/fpga/fpga-region.rst | 109 + Documentation/driver-api/fpga/index.rst | 15 + Documentation/driver-api/fpga/intro.rst | 54 + Documentation/driver-api/frame-buffer.rst | 62 + Documentation/driver-api/generic-counter.rst | 573 ++ Documentation/driver-api/gpio/board.rst | 222 + Documentation/driver-api/gpio/bt8xxgpio.rst | 62 + Documentation/driver-api/gpio/consumer.rst | 468 ++ Documentation/driver-api/gpio/driver.rst | 778 ++ Documentation/driver-api/gpio/drivers-on-gpio.rst | 114 + Documentation/driver-api/gpio/index.rst | 50 + Documentation/driver-api/gpio/intro.rst | 124 + Documentation/driver-api/gpio/legacy.rst | 769 ++ Documentation/driver-api/gpio/using-gpio.rst | 50 + Documentation/driver-api/hsi.rst | 88 + Documentation/driver-api/hte/hte.rst | 79 + Documentation/driver-api/hte/index.rst | 22 + Documentation/driver-api/hte/tegra194-hte.rst | 48 + Documentation/driver-api/i2c.rst | 48 + Documentation/driver-api/i3c/device-driver-api.rst | 9 + Documentation/driver-api/i3c/index.rst | 11 + Documentation/driver-api/i3c/master-driver-api.rst | 9 + Documentation/driver-api/i3c/protocol.rst | 203 + Documentation/driver-api/iio/buffers.rst | 126 + Documentation/driver-api/iio/core.rst | 182 + Documentation/driver-api/iio/hw-consumer.rst | 50 + Documentation/driver-api/iio/index.rst | 18 + Documentation/driver-api/iio/intro.rst | 33 + Documentation/driver-api/iio/triggered-buffers.rst | 69 + Documentation/driver-api/iio/triggers.rst | 78 + Documentation/driver-api/index.rst | 119 + Documentation/driver-api/infiniband.rst | 124 + Documentation/driver-api/infrastructure.rst | 79 + Documentation/driver-api/input.rst | 42 + Documentation/driver-api/interconnect.rst | 115 + Documentation/driver-api/io-mapping.rst | 91 + Documentation/driver-api/io_ordering.rst | 51 + Documentation/driver-api/ioctl.rst | 253 + Documentation/driver-api/ipmb.rst | 109 + Documentation/driver-api/ipmi.rst | 810 ++ Documentation/driver-api/isa.rst | 122 + Documentation/driver-api/isapnp.rst | 15 + Documentation/driver-api/libata.rst | 1019 +++ Documentation/driver-api/mailbox.rst | 129 + Documentation/driver-api/md/index.rst | 12 + Documentation/driver-api/md/md-cluster.rst | 385 + Documentation/driver-api/md/raid5-cache.rst | 111 + Documentation/driver-api/md/raid5-ppl.rst | 47 + Documentation/driver-api/media/camera-sensor.rst | 153 + Documentation/driver-api/media/cec-core.rst | 478 ++ .../driver-api/media/drivers/bttv-devel.rst | 116 + .../driver-api/media/drivers/ccs/ccs-regs.asc | 1041 +++ Documentation/driver-api/media/drivers/ccs/ccs.rst | 95 + .../driver-api/media/drivers/ccs/mk-ccs-regs | 434 + .../driver-api/media/drivers/contributors.rst | 131 + .../driver-api/media/drivers/cpia2_devel.rst | 56 + .../driver-api/media/drivers/cx2341x-devel.rst | 3685 +++++++++ .../driver-api/media/drivers/cx88-devel.rst | 113 + .../media/drivers/davinci-vpbe-devel.rst | 39 + Documentation/driver-api/media/drivers/dvb-usb.rst | 357 + .../driver-api/media/drivers/fimc-devel.rst | 33 + .../driver-api/media/drivers/frontends.rst | 32 + Documentation/driver-api/media/drivers/index.rst | 42 + Documentation/driver-api/media/drivers/pvrusb2.rst | 202 + .../driver-api/media/drivers/pxa_camera.rst | 194 + .../driver-api/media/drivers/radiotrack.rst | 168 + Documentation/driver-api/media/drivers/rkisp1.rst | 43 + .../driver-api/media/drivers/saa7134-devel.rst | 67 + .../media/drivers/sh_mobile_ceu_camera.rst | 142 + Documentation/driver-api/media/drivers/tuners.rst | 133 + Documentation/driver-api/media/drivers/vidtv.rst | 513 ++ .../driver-api/media/drivers/vimc-devel.rst | 15 + Documentation/driver-api/media/drivers/zoran.rst | 575 ++ Documentation/driver-api/media/dtv-ca.rst | 6 + Documentation/driver-api/media/dtv-common.rst | 62 + Documentation/driver-api/media/dtv-core.rst | 39 + Documentation/driver-api/media/dtv-demux.rst | 84 + Documentation/driver-api/media/dtv-frontend.rst | 445 ++ Documentation/driver-api/media/dtv-net.rst | 6 + Documentation/driver-api/media/index.rst | 59 + .../driver-api/media/maintainer-entry-profile.rst | 206 + Documentation/driver-api/media/mc-core.rst | 328 + Documentation/driver-api/media/rc-core.rst | 88 + Documentation/driver-api/media/tx-rx.rst | 133 + Documentation/driver-api/media/v4l2-async.rst | 5 + Documentation/driver-api/media/v4l2-common.rst | 8 + Documentation/driver-api/media/v4l2-controls.rst | 823 ++ Documentation/driver-api/media/v4l2-core.rst | 28 + Documentation/driver-api/media/v4l2-dev.rst | 375 + Documentation/driver-api/media/v4l2-device.rst | 146 + Documentation/driver-api/media/v4l2-dv-timings.rst | 6 + Documentation/driver-api/media/v4l2-event.rst | 181 + Documentation/driver-api/media/v4l2-fh.rst | 141 + .../driver-api/media/v4l2-flash-led-class.rst | 6 + Documentation/driver-api/media/v4l2-fwnode.rst | 5 + Documentation/driver-api/media/v4l2-intro.rst | 76 + Documentation/driver-api/media/v4l2-mc.rst | 6 + Documentation/driver-api/media/v4l2-mediabus.rst | 6 + Documentation/driver-api/media/v4l2-mem2mem.rst | 6 + Documentation/driver-api/media/v4l2-rect.rst | 6 + Documentation/driver-api/media/v4l2-subdev.rst | 599 ++ Documentation/driver-api/media/v4l2-tuner.rst | 8 + Documentation/driver-api/media/v4l2-tveeprom.rst | 6 + Documentation/driver-api/media/v4l2-videobuf.rst | 403 + Documentation/driver-api/media/v4l2-videobuf2.rst | 12 + Documentation/driver-api/mei/hdcp.rst | 32 + Documentation/driver-api/mei/iamt.rst | 101 + Documentation/driver-api/mei/index.rst | 23 + Documentation/driver-api/mei/mei-client-bus.rst | 168 + Documentation/driver-api/mei/mei.rst | 213 + Documentation/driver-api/mei/nfc.rst | 28 + Documentation/driver-api/memory-devices/index.rst | 18 + .../driver-api/memory-devices/ti-emif.rst | 64 + .../driver-api/memory-devices/ti-gpmc.rst | 179 + Documentation/driver-api/men-chameleon-bus.rst | 187 + Documentation/driver-api/message-based.rst | 12 + Documentation/driver-api/misc_devices.rst | 5 + Documentation/driver-api/miscellaneous.rst | 48 + Documentation/driver-api/mmc/index.rst | 13 + Documentation/driver-api/mmc/mmc-async-req.rst | 98 + Documentation/driver-api/mmc/mmc-dev-attrs.rst | 91 + Documentation/driver-api/mmc/mmc-dev-parts.rst | 41 + Documentation/driver-api/mmc/mmc-tools.rst | 37 + Documentation/driver-api/mtd/index.rst | 12 + Documentation/driver-api/mtd/nand_ecc.rst | 763 ++ Documentation/driver-api/mtd/spi-intel.rst | 90 + Documentation/driver-api/mtd/spi-nor.rst | 68 + Documentation/driver-api/mtdnand.rst | 1006 +++ Documentation/driver-api/nfc/index.rst | 11 + Documentation/driver-api/nfc/nfc-hci.rst | 311 + Documentation/driver-api/nfc/nfc-pn544.rst | 34 + Documentation/driver-api/ntb.rst | 263 + Documentation/driver-api/nvdimm/btt.rst | 285 + .../driver-api/nvdimm/firmware-activate.rst | 86 + Documentation/driver-api/nvdimm/index.rst | 13 + Documentation/driver-api/nvdimm/nvdimm.rst | 657 ++ Documentation/driver-api/nvdimm/security.rst | 143 + Documentation/driver-api/nvmem.rst | 187 + Documentation/driver-api/parport-lowlevel.rst | 1832 +++++ Documentation/driver-api/pci/index.rst | 22 + Documentation/driver-api/pci/p2pdma.rst | 131 + Documentation/driver-api/pci/pci.rst | 47 + Documentation/driver-api/phy/index.rst | 18 + Documentation/driver-api/phy/phy.rst | 197 + Documentation/driver-api/phy/samsung-usb2.rst | 137 + Documentation/driver-api/pin-control.rst | 1467 ++++ Documentation/driver-api/pldmfw/driver-ops.rst | 56 + Documentation/driver-api/pldmfw/file-format.rst | 203 + Documentation/driver-api/pldmfw/index.rst | 72 + Documentation/driver-api/pm/cpuidle.rst | 279 + Documentation/driver-api/pm/devices.rst | 880 +++ Documentation/driver-api/pm/index.rst | 19 + Documentation/driver-api/pm/notifiers.rst | 74 + Documentation/driver-api/pm/types.rst | 7 + Documentation/driver-api/pps.rst | 242 + Documentation/driver-api/ptp.rst | 108 + Documentation/driver-api/pwm.rst | 179 + Documentation/driver-api/rapidio/index.rst | 15 + Documentation/driver-api/rapidio/mport_cdev.rst | 110 + Documentation/driver-api/rapidio/rapidio.rst | 362 + Documentation/driver-api/rapidio/rio_cm.rst | 135 + Documentation/driver-api/rapidio/sysfs.rst | 7 + Documentation/driver-api/rapidio/tsi721.rst | 112 + Documentation/driver-api/regulator.rst | 170 + Documentation/driver-api/reset.rst | 221 + Documentation/driver-api/rfkill.rst | 132 + Documentation/driver-api/s390-drivers.rst | 135 + Documentation/driver-api/scsi.rst | 338 + Documentation/driver-api/serial/driver.rst | 103 + Documentation/driver-api/serial/index.rst | 27 + Documentation/driver-api/serial/serial-iso7816.rst | 90 + Documentation/driver-api/serial/serial-rs485.rst | 131 + Documentation/driver-api/slimbus.rst | 132 + Documentation/driver-api/sm501.rst | 74 + .../driver-api/soundwire/error_handling.rst | 65 + Documentation/driver-api/soundwire/index.rst | 18 + Documentation/driver-api/soundwire/locking.rst | 108 + Documentation/driver-api/soundwire/stream.rst | 527 ++ Documentation/driver-api/soundwire/summary.rst | 208 + Documentation/driver-api/spi.rst | 53 + .../driver-api/surface_aggregator/client-api.rst | 38 + .../driver-api/surface_aggregator/client.rst | 397 + .../driver-api/surface_aggregator/clients/cdev.rst | 204 + .../driver-api/surface_aggregator/clients/dtx.rst | 718 ++ .../surface_aggregator/clients/index.rst | 23 + .../driver-api/surface_aggregator/clients/san.rst | 44 + .../driver-api/surface_aggregator/index.rst | 21 + .../driver-api/surface_aggregator/internal-api.rst | 67 + .../driver-api/surface_aggregator/internal.rst | 578 ++ .../driver-api/surface_aggregator/overview.rst | 79 + .../driver-api/surface_aggregator/ssh.rst | 344 + Documentation/driver-api/switchtec.rst | 102 + Documentation/driver-api/sync_file.rst | 86 + Documentation/driver-api/target.rst | 52 + .../driver-api/thermal/cpu-cooling-api.rst | 107 + .../driver-api/thermal/cpu-idle-cooling.rst | 199 + .../driver-api/thermal/exynos_thermal.rst | 90 + .../thermal/exynos_thermal_emulation.rst | 61 + Documentation/driver-api/thermal/index.rst | 20 + Documentation/driver-api/thermal/intel_dptf.rst | 272 + .../driver-api/thermal/intel_powerclamp.rst | 320 + .../driver-api/thermal/nouveau_thermal.rst | 96 + .../driver-api/thermal/power_allocator.rst | 281 + Documentation/driver-api/thermal/sysfs-api.rst | 535 ++ .../thermal/x86_pkg_temperature_thermal.rst | 55 + Documentation/driver-api/tty/index.rst | 73 + Documentation/driver-api/tty/moxa-smartio.rst | 197 + Documentation/driver-api/tty/n_gsm.rst | 153 + Documentation/driver-api/tty/n_tty.rst | 22 + Documentation/driver-api/tty/tty_buffer.rst | 46 + Documentation/driver-api/tty/tty_driver.rst | 128 + Documentation/driver-api/tty/tty_internals.rst | 31 + Documentation/driver-api/tty/tty_ldisc.rst | 85 + Documentation/driver-api/tty/tty_port.rst | 70 + Documentation/driver-api/tty/tty_struct.rst | 81 + Documentation/driver-api/uio-howto.rst | 730 ++ Documentation/driver-api/usb/URB.rst | 290 + Documentation/driver-api/usb/anchors.rst | 83 + Documentation/driver-api/usb/bulk-streams.rst | 83 + Documentation/driver-api/usb/callbacks.rst | 157 + Documentation/driver-api/usb/dma.rst | 136 + Documentation/driver-api/usb/dwc3.rst | 711 ++ Documentation/driver-api/usb/error-codes.rst | 210 + Documentation/driver-api/usb/gadget.rst | 510 ++ Documentation/driver-api/usb/hotplug.rst | 154 + Documentation/driver-api/usb/index.rst | 30 + Documentation/driver-api/usb/persist.rst | 171 + Documentation/driver-api/usb/power-management.rst | 798 ++ Documentation/driver-api/usb/typec.rst | 234 + Documentation/driver-api/usb/typec_bus.rst | 122 + Documentation/driver-api/usb/usb.rst | 1051 +++ Documentation/driver-api/usb/usb3-debug-port.rst | 152 + .../driver-api/usb/writing_musb_glue_layer.rst | 720 ++ .../driver-api/usb/writing_usb_driver.rst | 328 + Documentation/driver-api/vfio-mediated-device.rst | 379 + .../vfio-pci-device-specific-driver-acceptance.rst | 35 + Documentation/driver-api/vfio.rst | 528 ++ Documentation/driver-api/vme.rst | 297 + Documentation/driver-api/w1.rst | 67 + Documentation/driver-api/xilinx/eemi.rst | 40 + Documentation/driver-api/xilinx/index.rst | 16 + Documentation/driver-api/xillybus.rst | 379 + Documentation/driver-api/zorro.rst | 104 + Documentation/fault-injection/fault-injection.rst | 478 ++ Documentation/fault-injection/index.rst | 20 + .../fault-injection/notifier-error-inject.rst | 98 + .../fault-injection/nvme-fault-injection.rst | 178 + Documentation/fault-injection/provoke-crashes.rst | 57 + Documentation/fb/api.rst | 307 + Documentation/fb/arkfb.rst | 68 + Documentation/fb/aty128fb.rst | 75 + Documentation/fb/cirrusfb.rst | 94 + Documentation/fb/cmap_xfbdev.rst | 56 + Documentation/fb/deferred_io.rst | 79 + Documentation/fb/efifb.rst | 71 + Documentation/fb/ep93xx-fb.rst | 140 + Documentation/fb/fbcon.rst | 348 + Documentation/fb/framebuffer.rst | 353 + Documentation/fb/gxfb.rst | 54 + Documentation/fb/index.rst | 50 + Documentation/fb/intel810.rst | 287 + Documentation/fb/intelfb.rst | 155 + Documentation/fb/internals.rst | 86 + Documentation/fb/lxfb.rst | 55 + Documentation/fb/matroxfb.rst | 441 ++ Documentation/fb/metronomefb.rst | 38 + Documentation/fb/modedb.rst | 172 + Documentation/fb/pvr2fb.rst | 66 + Documentation/fb/pxafb.rst | 173 + Documentation/fb/s3fb.rst | 82 + Documentation/fb/sa1100fb.rst | 40 + Documentation/fb/sh7760fb.rst | 130 + Documentation/fb/sisfb.rst | 160 + Documentation/fb/sm501.rst | 15 + Documentation/fb/sm712fb.rst | 35 + Documentation/fb/sstfb.rst | 204 + Documentation/fb/tgafb.rst | 71 + Documentation/fb/tridentfb.rst | 78 + Documentation/fb/udlfb.rst | 169 + Documentation/fb/uvesafb.rst | 188 + Documentation/fb/vesafb.rst | 190 + Documentation/fb/viafb.modes | 870 ++ Documentation/fb/viafb.rst | 297 + Documentation/fb/vt8623fb.rst | 64 + Documentation/features/arch-support.txt | 12 + .../features/core/cBPF-JIT/arch-support.txt | 31 + .../features/core/eBPF-JIT/arch-support.txt | 31 + .../core/generic-idle-thread/arch-support.txt | 31 + .../features/core/jump-labels/arch-support.txt | 31 + .../core/thread-info-in-task/arch-support.txt | 31 + .../features/core/tracehook/arch-support.txt | 31 + .../features/debug/KASAN/arch-support.txt | 31 + .../debug/debug-vm-pgtable/arch-support.txt | 31 + .../debug/gcov-profile-all/arch-support.txt | 31 + Documentation/features/debug/kcov/arch-support.txt | 31 + Documentation/features/debug/kgdb/arch-support.txt | 31 + .../features/debug/kmemleak/arch-support.txt | 31 + .../debug/kprobes-on-ftrace/arch-support.txt | 31 + .../features/debug/kprobes/arch-support.txt | 31 + .../features/debug/kretprobes/arch-support.txt | 31 + .../features/debug/optprobes/arch-support.txt | 31 + .../features/debug/stackprotector/arch-support.txt | 31 + .../features/debug/uprobes/arch-support.txt | 31 + .../debug/user-ret-profiler/arch-support.txt | 31 + .../features/io/dma-contiguous/arch-support.txt | 31 + Documentation/features/list-arch.sh | 11 + .../locking/cmpxchg-local/arch-support.txt | 31 + .../features/locking/lockdep/arch-support.txt | 31 + .../locking/queued-rwlocks/arch-support.txt | 31 + .../locking/queued-spinlocks/arch-support.txt | 31 + .../features/perf/kprobes-event/arch-support.txt | 31 + .../features/perf/perf-regs/arch-support.txt | 31 + .../features/perf/perf-stackdump/arch-support.txt | 31 + .../sched/membarrier-sync-core/arch-support.txt | 54 + .../features/sched/numa-balancing/arch-support.txt | 31 + Documentation/features/scripts/features-refresh.sh | 98 + .../seccomp/seccomp-filter/arch-support.txt | 31 + .../time/arch-tick-broadcast/arch-support.txt | 31 + .../features/time/clockevents/arch-support.txt | 31 + .../time/context-tracking/arch-support.txt | 31 + .../features/time/irq-time-acct/arch-support.txt | 31 + .../features/time/virt-cpuacct/arch-support.txt | 31 + .../features/vm/ELF-ASLR/arch-support.txt | 31 + .../features/vm/PG_uncached/arch-support.txt | 31 + Documentation/features/vm/THP/arch-support.txt | 31 + Documentation/features/vm/TLB/arch-support.txt | 31 + .../features/vm/huge-vmap/arch-support.txt | 31 + .../features/vm/ioremap_prot/arch-support.txt | 31 + .../features/vm/pte_special/arch-support.txt | 31 + Documentation/filesystems/9p.rst | 195 + Documentation/filesystems/adfs.rst | 108 + Documentation/filesystems/affs.rst | 250 + Documentation/filesystems/afs.rst | 251 + Documentation/filesystems/api-summary.rst | 150 + Documentation/filesystems/autofs-mount-control.rst | 410 + Documentation/filesystems/autofs.rst | 580 ++ Documentation/filesystems/automount-support.rst | 98 + Documentation/filesystems/befs.rst | 128 + Documentation/filesystems/bfs.rst | 60 + Documentation/filesystems/btrfs.rst | 44 + Documentation/filesystems/caching/backend-api.rst | 479 ++ Documentation/filesystems/caching/cachefiles.rst | 662 ++ Documentation/filesystems/caching/fscache.rst | 348 + Documentation/filesystems/caching/index.rst | 12 + Documentation/filesystems/caching/netfs-api.rst | 452 ++ Documentation/filesystems/ceph.rst | 208 + Documentation/filesystems/cifs/cifsroot.rst | 105 + Documentation/filesystems/cifs/index.rst | 10 + Documentation/filesystems/cifs/ksmbd.rst | 183 + Documentation/filesystems/coda.rst | 1670 ++++ Documentation/filesystems/configfs.rst | 535 ++ Documentation/filesystems/cramfs.rst | 123 + Documentation/filesystems/dax.rst | 307 + Documentation/filesystems/debugfs.rst | 252 + Documentation/filesystems/devpts.rst | 36 + Documentation/filesystems/directory-locking.rst | 148 + Documentation/filesystems/dlmfs.rst | 140 + Documentation/filesystems/dnotify.rst | 75 + Documentation/filesystems/ecryptfs.rst | 86 + Documentation/filesystems/efivarfs.rst | 43 + Documentation/filesystems/erofs.rst | 316 + Documentation/filesystems/ext2.rst | 398 + Documentation/filesystems/ext3.rst | 14 + Documentation/filesystems/ext4/about.rst | 44 + Documentation/filesystems/ext4/allocators.rst | 56 + Documentation/filesystems/ext4/attributes.rst | 191 + Documentation/filesystems/ext4/bigalloc.rst | 34 + Documentation/filesystems/ext4/bitmaps.rst | 28 + Documentation/filesystems/ext4/blockgroup.rst | 135 + Documentation/filesystems/ext4/blockmap.rst | 49 + Documentation/filesystems/ext4/blocks.rst | 144 + Documentation/filesystems/ext4/checksums.rst | 73 + Documentation/filesystems/ext4/directory.rst | 453 ++ Documentation/filesystems/ext4/dynamic.rst | 12 + Documentation/filesystems/ext4/eainode.rst | 18 + Documentation/filesystems/ext4/globals.rst | 14 + Documentation/filesystems/ext4/group_descr.rst | 173 + Documentation/filesystems/ext4/ifork.rst | 194 + Documentation/filesystems/ext4/index.rst | 14 + Documentation/filesystems/ext4/inlinedata.rst | 37 + Documentation/filesystems/ext4/inodes.rst | 578 ++ Documentation/filesystems/ext4/journal.rst | 756 ++ Documentation/filesystems/ext4/mmp.rst | 77 + Documentation/filesystems/ext4/orphan.rst | 42 + Documentation/filesystems/ext4/overview.rst | 27 + Documentation/filesystems/ext4/special_inodes.rst | 55 + Documentation/filesystems/ext4/super.rst | 831 ++ Documentation/filesystems/ext4/verity.rst | 44 + Documentation/filesystems/f2fs.rst | 891 +++ Documentation/filesystems/fiemap.rst | 236 + Documentation/filesystems/files.rst | 128 + Documentation/filesystems/fscrypt.rst | 1367 ++++ Documentation/filesystems/fsverity.rst | 824 ++ Documentation/filesystems/fuse-io.rst | 44 + Documentation/filesystems/fuse.rst | 426 + Documentation/filesystems/gfs2-glocks.rst | 253 + Documentation/filesystems/gfs2-uevents.rst | 112 + Documentation/filesystems/gfs2.rst | 52 + Documentation/filesystems/hfs.rst | 87 + Documentation/filesystems/hfsplus.rst | 61 + Documentation/filesystems/hpfs.rst | 353 + Documentation/filesystems/idmappings.rst | 959 +++ Documentation/filesystems/index.rst | 126 + Documentation/filesystems/inotify.rst | 90 + Documentation/filesystems/isofs.rst | 64 + Documentation/filesystems/journalling.rst | 215 + Documentation/filesystems/locking.rst | 697 ++ Documentation/filesystems/locks.rst | 65 + Documentation/filesystems/mount_api.rst | 825 ++ Documentation/filesystems/netfs_library.rst | 610 ++ .../filesystems/nfs/client-identifier.rst | 216 + Documentation/filesystems/nfs/exporting.rst | 217 + Documentation/filesystems/nfs/index.rst | 16 + Documentation/filesystems/nfs/knfsd-stats.rst | 122 + Documentation/filesystems/nfs/nfs41-server.rst | 256 + Documentation/filesystems/nfs/pnfs.rst | 78 + Documentation/filesystems/nfs/reexport.rst | 113 + Documentation/filesystems/nfs/rpc-cache.rst | 220 + Documentation/filesystems/nfs/rpc-server-gss.rst | 93 + Documentation/filesystems/nilfs2.rst | 286 + Documentation/filesystems/ntfs.rst | 466 ++ Documentation/filesystems/ntfs3.rst | 115 + .../filesystems/ocfs2-online-filecheck.rst | 99 + Documentation/filesystems/ocfs2.rst | 117 + Documentation/filesystems/omfs.rst | 112 + Documentation/filesystems/orangefs.rst | 556 ++ Documentation/filesystems/overlayfs.rst | 626 ++ Documentation/filesystems/path-lookup.rst | 1390 ++++ Documentation/filesystems/path-lookup.txt | 382 + Documentation/filesystems/porting.rst | 963 +++ Documentation/filesystems/proc.rst | 2237 ++++++ Documentation/filesystems/qnx6.rst | 196 + Documentation/filesystems/quota.rst | 85 + .../filesystems/ramfs-rootfs-initramfs.rst | 369 + Documentation/filesystems/relay.rst | 501 ++ Documentation/filesystems/romfs.rst | 194 + Documentation/filesystems/seq_file.rst | 396 + Documentation/filesystems/sharedsubtree.rst | 995 +++ Documentation/filesystems/splice.rst | 22 + Documentation/filesystems/spufs/index.rst | 13 + Documentation/filesystems/spufs/spu_create.rst | 131 + Documentation/filesystems/spufs/spu_run.rst | 138 + Documentation/filesystems/spufs/spufs.rst | 273 + Documentation/filesystems/squashfs.rst | 265 + Documentation/filesystems/sysfs.rst | 415 + Documentation/filesystems/sysv-fs.rst | 264 + Documentation/filesystems/tmpfs.rst | 181 + Documentation/filesystems/ubifs-authentication.rst | 448 ++ Documentation/filesystems/ubifs.rst | 137 + Documentation/filesystems/udf.rst | 75 + Documentation/filesystems/vfat.rst | 387 + Documentation/filesystems/vfs.rst | 1476 ++++ Documentation/filesystems/virtiofs.rst | 76 + .../filesystems/xfs-delayed-logging-design.rst | 1087 +++ .../filesystems/xfs-self-describing-metadata.rst | 352 + Documentation/filesystems/zonefs.rst | 485 ++ .../firmware-guide/acpi/DSD-properties-rules.rst | 103 + Documentation/firmware-guide/acpi/acpi-lid.rst | 114 + Documentation/firmware-guide/acpi/aml-debugger.rst | 75 + Documentation/firmware-guide/acpi/apei/einj.rst | 204 + .../firmware-guide/acpi/apei/output_format.rst | 150 + .../firmware-guide/acpi/chromeos-acpi-device.rst | 363 + Documentation/firmware-guide/acpi/debug.rst | 132 + .../acpi/dsd/data-node-references.rst | 96 + Documentation/firmware-guide/acpi/dsd/graph.rst | 173 + Documentation/firmware-guide/acpi/dsd/leds.rst | 107 + Documentation/firmware-guide/acpi/dsd/phy.rst | 201 + Documentation/firmware-guide/acpi/enumeration.rst | 690 ++ .../firmware-guide/acpi/extcon-intel-int3496.rst | 33 + .../firmware-guide/acpi/gpio-properties.rst | 323 + Documentation/firmware-guide/acpi/i2c-muxes.rst | 61 + Documentation/firmware-guide/acpi/index.rst | 32 + .../firmware-guide/acpi/intel-pmc-mux.rst | 153 + Documentation/firmware-guide/acpi/lpit.rst | 33 + .../firmware-guide/acpi/method-customizing.rst | 89 + .../firmware-guide/acpi/method-tracing.rst | 238 + Documentation/firmware-guide/acpi/namespace.rst | 400 + Documentation/firmware-guide/acpi/non-d0-probe.rst | 78 + Documentation/firmware-guide/acpi/osi.rst | 187 + .../firmware-guide/acpi/video_extension.rst | 121 + Documentation/firmware-guide/index.rst | 13 + Documentation/firmware_class/hotplug-script | 17 + Documentation/fpga/dfl.rst | 568 ++ Documentation/fpga/index.rst | 17 + Documentation/gpu/afbc.rst | 235 + Documentation/gpu/amdgpu/amdgpu-glossary.rst | 100 + Documentation/gpu/amdgpu/apu-asic-info-table.csv | 8 + Documentation/gpu/amdgpu/dgpu-asic-info-table.csv | 24 + .../gpu/amdgpu/display/config_example.svg | 414 + Documentation/gpu/amdgpu/display/dc-debug.rst | 77 + Documentation/gpu/amdgpu/display/dc-glossary.rst | 237 + .../gpu/amdgpu/display/dc_pipeline_overview.svg | 1125 +++ Documentation/gpu/amdgpu/display/dcn-overview.rst | 230 + .../gpu/amdgpu/display/dcn2_cm_drm_current.svg | 1370 ++++ .../gpu/amdgpu/display/dcn3_cm_drm_current.svg | 1529 ++++ .../gpu/amdgpu/display/display-manager.rst | 183 + .../gpu/amdgpu/display/global_sync_vblank.svg | 485 ++ Documentation/gpu/amdgpu/display/index.rst | 32 + Documentation/gpu/amdgpu/display/mpo-cursor.svg | 435 + Documentation/gpu/amdgpu/display/mpo-overview.rst | 242 + .../multi-display-hdcp-mpo-less-pipe-ex.svg | 220 + .../gpu/amdgpu/display/multi-display-hdcp-mpo.svg | 171 + .../gpu/amdgpu/display/pipeline_4k_no_split.svg | 958 +++ .../gpu/amdgpu/display/pipeline_4k_split.svg | 1062 +++ .../display/single-display-mpo-multi-video.svg | 339 + .../gpu/amdgpu/display/single-display-mpo.svg | 266 + Documentation/gpu/amdgpu/driver-core.rst | 182 + Documentation/gpu/amdgpu/driver-misc.rst | 129 + Documentation/gpu/amdgpu/index.rst | 17 + Documentation/gpu/amdgpu/module-parameters.rst | 7 + Documentation/gpu/amdgpu/ras.rst | 62 + Documentation/gpu/amdgpu/thermal.rst | 122 + Documentation/gpu/amdgpu/xgmi.rst | 5 + Documentation/gpu/backlight.rst | 12 + Documentation/gpu/bridge/dw-hdmi.rst | 15 + Documentation/gpu/dp-mst/topology-figure-1.dot | 52 + Documentation/gpu/dp-mst/topology-figure-2.dot | 56 + Documentation/gpu/dp-mst/topology-figure-3.dot | 59 + Documentation/gpu/driver-uapi.rst | 8 + Documentation/gpu/drivers.rst | 27 + Documentation/gpu/drm-client.rst | 15 + Documentation/gpu/drm-internals.rst | 273 + Documentation/gpu/drm-kms-helpers.rst | 455 ++ Documentation/gpu/drm-kms.rst | 613 ++ Documentation/gpu/drm-mm.rst | 515 ++ Documentation/gpu/drm-uapi.rst | 488 ++ Documentation/gpu/drm-usage-stats.rst | 133 + Documentation/gpu/i915.rst | 739 ++ Documentation/gpu/index.rst | 28 + Documentation/gpu/introduction.rst | 174 + Documentation/gpu/kms-properties.csv | 101 + Documentation/gpu/komeda-kms.rst | 488 ++ Documentation/gpu/mcde.rst | 8 + Documentation/gpu/meson.rst | 55 + Documentation/gpu/msm-crash-dump.rst | 98 + Documentation/gpu/pl111.rst | 6 + Documentation/gpu/rfc/i915_gem_lmem.rst | 22 + Documentation/gpu/rfc/i915_scheduler.rst | 148 + Documentation/gpu/rfc/i915_small_bar.h | 189 + Documentation/gpu/rfc/i915_small_bar.rst | 47 + Documentation/gpu/rfc/i915_vm_bind.h | 291 + Documentation/gpu/rfc/i915_vm_bind.rst | 245 + Documentation/gpu/rfc/index.rst | 33 + Documentation/gpu/tegra.rst | 178 + Documentation/gpu/todo.rst | 769 ++ Documentation/gpu/tve200.rst | 6 + Documentation/gpu/v3d.rst | 28 + Documentation/gpu/vc4.rst | 89 + Documentation/gpu/vga-switcheroo.rst | 98 + Documentation/gpu/vgaarbiter.rst | 191 + Documentation/gpu/vkms.rst | 200 + Documentation/gpu/xen-front.rst | 31 + Documentation/hid/amd-sfh-hid.rst | 145 + Documentation/hid/hid-alps.rst | 180 + Documentation/hid/hid-sensor.rst | 242 + Documentation/hid/hid-transport.rst | 359 + Documentation/hid/hiddev.rst | 251 + Documentation/hid/hidraw.rst | 180 + Documentation/hid/index.rst | 19 + Documentation/hid/intel-ish-hid.rst | 487 ++ Documentation/hid/uhid.rst | 193 + Documentation/hwmon/abituguru-datasheet.rst | 336 + Documentation/hwmon/abituguru.rst | 113 + Documentation/hwmon/abituguru3.rst | 75 + Documentation/hwmon/acpi_power_meter.rst | 54 + Documentation/hwmon/ad7314.rst | 34 + Documentation/hwmon/adc128d818.rst | 50 + Documentation/hwmon/adm1021.rst | 153 + Documentation/hwmon/adm1025.rst | 60 + Documentation/hwmon/adm1026.rst | 101 + Documentation/hwmon/adm1031.rst | 43 + Documentation/hwmon/adm1177.rst | 36 + Documentation/hwmon/adm1266.rst | 37 + Documentation/hwmon/adm1275.rst | 148 + Documentation/hwmon/adm9240.rst | 201 + Documentation/hwmon/ads7828.rst | 65 + Documentation/hwmon/adt7410.rst | 94 + Documentation/hwmon/adt7411.rst | 50 + Documentation/hwmon/adt7462.rst | 70 + Documentation/hwmon/adt7470.rst | 94 + Documentation/hwmon/adt7475.rst | 156 + Documentation/hwmon/aht10.rst | 46 + Documentation/hwmon/amc6821.rst | 108 + Documentation/hwmon/aquacomputer_d5next.rst | 79 + Documentation/hwmon/asb100.rst | 73 + Documentation/hwmon/asc7621.rst | 326 + Documentation/hwmon/aspeed-pwm-tacho.rst | 24 + Documentation/hwmon/asus_ec_sensors.rst | 63 + Documentation/hwmon/asus_wmi_sensors.rst | 78 + Documentation/hwmon/bcm54140.rst | 45 + Documentation/hwmon/bel-pfe.rst | 112 + Documentation/hwmon/bpa-rs600.rst | 74 + Documentation/hwmon/bt1-pvt.rst | 117 + Documentation/hwmon/coretemp.rst | 195 + Documentation/hwmon/corsair-cpro.rst | 41 + Documentation/hwmon/corsair-psu.rst | 96 + Documentation/hwmon/da9052.rst | 78 + Documentation/hwmon/da9055.rst | 57 + Documentation/hwmon/dell-smm-hwmon.rst | 359 + Documentation/hwmon/dme1737.rst | 364 + Documentation/hwmon/dps920ab.rst | 73 + Documentation/hwmon/drivetemp.rst | 70 + Documentation/hwmon/ds1621.rst | 217 + Documentation/hwmon/ds620.rst | 38 + Documentation/hwmon/emc1403.rst | 80 + Documentation/hwmon/emc2103.rst | 37 + Documentation/hwmon/emc2305.rst | 37 + Documentation/hwmon/emc6w201.rst | 47 + Documentation/hwmon/f71805f.rst | 181 + Documentation/hwmon/f71882fg.rst | 192 + Documentation/hwmon/fam15h_power.rst | 131 + Documentation/hwmon/fsp-3y.rst | 28 + Documentation/hwmon/ftsteutates.rst | 37 + Documentation/hwmon/g760a.rst | 40 + Documentation/hwmon/g762.rst | 74 + Documentation/hwmon/gl518sm.rst | 80 + Documentation/hwmon/gsc-hwmon.rst | 53 + Documentation/hwmon/hih6130.rst | 45 + Documentation/hwmon/hwmon-kernel-api.rst | 402 + Documentation/hwmon/ibm-cffps.rst | 57 + Documentation/hwmon/ibmaem.rst | 44 + Documentation/hwmon/ibmpowernv.rst | 87 + Documentation/hwmon/ina209.rst | 99 + Documentation/hwmon/ina238.rst | 56 + Documentation/hwmon/ina2xx.rst | 123 + Documentation/hwmon/ina3221.rst | 74 + Documentation/hwmon/index.rst | 238 + Documentation/hwmon/inspur-ipsps1.rst | 79 + Documentation/hwmon/intel-m10-bmc-hwmon.rst | 78 + Documentation/hwmon/ir35221.rst | 92 + Documentation/hwmon/ir36021.rst | 63 + Documentation/hwmon/ir38064.rst | 90 + Documentation/hwmon/isl68137.rst | 605 ++ Documentation/hwmon/it87.rst | 348 + Documentation/hwmon/jc42.rst | 152 + Documentation/hwmon/k10temp.rst | 134 + Documentation/hwmon/k8temp.rst | 62 + Documentation/hwmon/lan966x.rst | 40 + Documentation/hwmon/lineage-pem.rst | 85 + Documentation/hwmon/lm25066.rst | 139 + Documentation/hwmon/lm63.rst | 95 + Documentation/hwmon/lm70.rst | 69 + Documentation/hwmon/lm73.rst | 98 + Documentation/hwmon/lm75.rst | 166 + Documentation/hwmon/lm77.rst | 45 + Documentation/hwmon/lm78.rst | 80 + Documentation/hwmon/lm80.rst | 74 + Documentation/hwmon/lm83.rst | 97 + Documentation/hwmon/lm85.rst | 286 + Documentation/hwmon/lm87.rst | 86 + Documentation/hwmon/lm90.rst | 641 ++ Documentation/hwmon/lm92.rst | 48 + Documentation/hwmon/lm93.rst | 312 + Documentation/hwmon/lm95234.rst | 48 + Documentation/hwmon/lm95245.rst | 48 + Documentation/hwmon/lochnagar.rst | 83 + Documentation/hwmon/lt7182s.rst | 92 + Documentation/hwmon/ltc2945.rst | 92 + Documentation/hwmon/ltc2947.rst | 100 + Documentation/hwmon/ltc2978.rst | 449 ++ Documentation/hwmon/ltc2990.rst | 62 + Documentation/hwmon/ltc2992.rst | 56 + Documentation/hwmon/ltc3815.rst | 67 + Documentation/hwmon/ltc4151.rst | 55 + Documentation/hwmon/ltc4215.rst | 59 + Documentation/hwmon/ltc4245.rst | 111 + Documentation/hwmon/ltc4260.rst | 64 + Documentation/hwmon/ltc4261.rst | 71 + Documentation/hwmon/max127.rst | 45 + Documentation/hwmon/max15301.rst | 87 + Documentation/hwmon/max16064.rst | 75 + Documentation/hwmon/max16065.rst | 127 + Documentation/hwmon/max1619.rst | 33 + Documentation/hwmon/max16601.rst | 136 + Documentation/hwmon/max1668.rst | 70 + Documentation/hwmon/max197.rst | 70 + Documentation/hwmon/max20730.rst | 82 + Documentation/hwmon/max20751.rst | 84 + Documentation/hwmon/max31722.rst | 46 + Documentation/hwmon/max31730.rst | 44 + Documentation/hwmon/max31760.rst | 77 + Documentation/hwmon/max31785.rst | 66 + Documentation/hwmon/max31790.rst | 45 + Documentation/hwmon/max34440.rst | 195 + Documentation/hwmon/max6620.rst | 46 + Documentation/hwmon/max6639.rst | 55 + Documentation/hwmon/max6642.rst | 27 + Documentation/hwmon/max6650.rst | 74 + Documentation/hwmon/max6697.rst | 91 + Documentation/hwmon/max8688.rst | 85 + Documentation/hwmon/mc13783-adc.rst | 89 + Documentation/hwmon/mcp3021.rst | 38 + Documentation/hwmon/menf21bmc.rst | 55 + Documentation/hwmon/mlxreg-fan.rst | 70 + Documentation/hwmon/mp2888.rst | 113 + Documentation/hwmon/mp2975.rst | 128 + Documentation/hwmon/mp5023.rst | 84 + Documentation/hwmon/nct6683.rst | 66 + Documentation/hwmon/nct6775.rst | 280 + Documentation/hwmon/nct7802.rst | 38 + Documentation/hwmon/nct7904.rst | 67 + Documentation/hwmon/npcm750-pwm-fan.rst | 26 + Documentation/hwmon/nsa320.rst | 64 + Documentation/hwmon/ntc_thermistor.rst | 111 + Documentation/hwmon/nzxt-kraken2.rst | 42 + Documentation/hwmon/nzxt-smart2.rst | 62 + Documentation/hwmon/occ.rst | 153 + Documentation/hwmon/pc87360.rst | 198 + Documentation/hwmon/pc87427.rst | 63 + Documentation/hwmon/pcf8591.rst | 98 + Documentation/hwmon/peci-cputemp.rst | 90 + Documentation/hwmon/peci-dimmtemp.rst | 57 + Documentation/hwmon/pim4328.rst | 105 + Documentation/hwmon/pli1209bc.rst | 75 + Documentation/hwmon/pm6764tr.rst | 32 + Documentation/hwmon/pmbus-core.rst | 360 + Documentation/hwmon/pmbus.rst | 277 + Documentation/hwmon/powr1220.rst | 53 + Documentation/hwmon/pwm-fan.rst | 32 + Documentation/hwmon/pxe1610.rst | 107 + Documentation/hwmon/q54sj108a2.rst | 54 + Documentation/hwmon/raspberrypi-hwmon.rst | 25 + Documentation/hwmon/sbrmi.rst | 79 + Documentation/hwmon/sbtsi_temp.rst | 42 + Documentation/hwmon/sch5627.rst | 35 + Documentation/hwmon/sch5636.rst | 37 + Documentation/hwmon/scpi-hwmon.rst | 36 + Documentation/hwmon/sht15.rst | 83 + Documentation/hwmon/sht21.rst | 68 + Documentation/hwmon/sht3x.rst | 88 + Documentation/hwmon/sht4x.rst | 45 + Documentation/hwmon/shtc1.rst | 67 + Documentation/hwmon/sis5595.rst | 123 + Documentation/hwmon/sl28cpld.rst | 36 + Documentation/hwmon/smm665.rst | 187 + Documentation/hwmon/smsc47b397.rst | 197 + Documentation/hwmon/smsc47m1.rst | 86 + Documentation/hwmon/smsc47m192.rst | 116 + Documentation/hwmon/sparx5-temp.rst | 33 + Documentation/hwmon/stpddc60.rst | 90 + Documentation/hwmon/submitting-patches.rst | 149 + Documentation/hwmon/sy7636a-hwmon.rst | 26 + Documentation/hwmon/sysfs-interface.rst | 656 ++ Documentation/hwmon/tc654.rst | 34 + Documentation/hwmon/tc74.rst | 23 + Documentation/hwmon/thmc50.rst | 89 + Documentation/hwmon/tmp102.rst | 31 + Documentation/hwmon/tmp103.rst | 33 + Documentation/hwmon/tmp108.rst | 41 + Documentation/hwmon/tmp401.rst | 80 + Documentation/hwmon/tmp421.rst | 76 + Documentation/hwmon/tmp464.rst | 73 + Documentation/hwmon/tmp513.rst | 103 + Documentation/hwmon/tps23861.rst | 41 + Documentation/hwmon/tps40422.rst | 73 + Documentation/hwmon/tps53679.rst | 187 + Documentation/hwmon/tps546d24.rst | 35 + Documentation/hwmon/twl4030-madc-hwmon.rst | 49 + Documentation/hwmon/ucd9000.rst | 137 + Documentation/hwmon/ucd9200.rst | 124 + Documentation/hwmon/userspace-tools.rst | 43 + Documentation/hwmon/vexpress.rst | 41 + Documentation/hwmon/via686a.rst | 84 + Documentation/hwmon/vt1211.rst | 226 + Documentation/hwmon/w83627ehf.rst | 248 + Documentation/hwmon/w83627hf.rst | 124 + Documentation/hwmon/w83773g.rst | 35 + Documentation/hwmon/w83781d.rst | 513 ++ Documentation/hwmon/w83791d.rst | 180 + Documentation/hwmon/w83792d.rst | 199 + Documentation/hwmon/w83793.rst | 113 + Documentation/hwmon/w83795.rst | 142 + Documentation/hwmon/w83l785ts.rst | 45 + Documentation/hwmon/w83l786ng.rst | 66 + Documentation/hwmon/wm831x.rst | 40 + Documentation/hwmon/wm8350.rst | 30 + Documentation/hwmon/xdpe12284.rst | 106 + Documentation/hwmon/xdpe152c4.rst | 118 + Documentation/hwmon/xgene-hwmon.rst | 36 + Documentation/hwmon/zl6100.rst | 259 + Documentation/i2c/busses/i2c-ali1535.rst | 45 + Documentation/i2c/busses/i2c-ali1563.rst | 30 + Documentation/i2c/busses/i2c-ali15x3.rst | 122 + Documentation/i2c/busses/i2c-amd-mp2.rst | 25 + Documentation/i2c/busses/i2c-amd756.rst | 29 + Documentation/i2c/busses/i2c-amd8111.rst | 43 + Documentation/i2c/busses/i2c-diolan-u2c.rst | 29 + Documentation/i2c/busses/i2c-i801.rst | 187 + Documentation/i2c/busses/i2c-ismt.rst | 44 + Documentation/i2c/busses/i2c-mlxcpld.rst | 57 + Documentation/i2c/busses/i2c-nforce2.rst | 53 + Documentation/i2c/busses/i2c-nvidia-gpu.rst | 20 + Documentation/i2c/busses/i2c-ocores.rst | 70 + Documentation/i2c/busses/i2c-parport.rst | 190 + Documentation/i2c/busses/i2c-pca-isa.rst | 26 + Documentation/i2c/busses/i2c-piix4.rst | 111 + Documentation/i2c/busses/i2c-sis5595.rst | 68 + Documentation/i2c/busses/i2c-sis630.rst | 63 + Documentation/i2c/busses/i2c-sis96x.rst | 82 + Documentation/i2c/busses/i2c-taos-evm.rst | 48 + Documentation/i2c/busses/i2c-via.rst | 40 + Documentation/i2c/busses/i2c-viapro.rst | 77 + Documentation/i2c/busses/index.rst | 32 + Documentation/i2c/busses/scx200_acb.rst | 37 + Documentation/i2c/dev-interface.rst | 221 + Documentation/i2c/dma-considerations.rst | 71 + Documentation/i2c/fault-codes.rst | 131 + Documentation/i2c/functionality.rst | 156 + Documentation/i2c/gpio-fault-injection.rst | 136 + Documentation/i2c/i2c-protocol.rst | 96 + Documentation/i2c/i2c-stub.rst | 66 + Documentation/i2c/i2c-sysfs.rst | 387 + Documentation/i2c/i2c-topology.rst | 412 + Documentation/i2c/i2c_bus.svg | 1341 ++++ Documentation/i2c/index.rst | 74 + Documentation/i2c/instantiating-devices.rst | 272 + Documentation/i2c/muxes/i2c-mux-gpio.rst | 85 + Documentation/i2c/old-module-parameters.rst | 55 + Documentation/i2c/slave-eeprom-backend.rst | 26 + Documentation/i2c/slave-interface.rst | 201 + Documentation/i2c/slave-testunit-backend.rst | 88 + Documentation/i2c/smbus-protocol.rst | 324 + Documentation/i2c/summary.rst | 61 + Documentation/i2c/ten-bit-addresses.rst | 33 + Documentation/i2c/writing-clients.rst | 428 + Documentation/ia64/aliasing.rst | 246 + Documentation/ia64/efirtc.rst | 144 + Documentation/ia64/err_inject.rst | 1067 +++ Documentation/ia64/features.rst | 3 + Documentation/ia64/fsys.rst | 303 + Documentation/ia64/ia64.rst | 49 + Documentation/ia64/index.rst | 19 + Documentation/ia64/irq-redir.rst | 80 + Documentation/ia64/mca.rst | 198 + Documentation/ia64/serial.rst | 165 + Documentation/iio/bno055.rst | 51 + Documentation/iio/ep93xx_adc.rst | 40 + Documentation/iio/iio_configfs.rst | 102 + Documentation/iio/index.rst | 14 + Documentation/images/COPYING-logo | 21 + Documentation/images/logo.gif | Bin 0 -> 16335 bytes Documentation/images/logo.svg | 2040 +++++ Documentation/index.rst | 128 + Documentation/infiniband/core_locking.rst | 116 + Documentation/infiniband/index.rst | 23 + Documentation/infiniband/ipoib.rst | 115 + Documentation/infiniband/opa_vnic.rst | 159 + Documentation/infiniband/sysfs.rst | 6 + Documentation/infiniband/tag_matching.rst | 69 + Documentation/infiniband/user_mad.rst | 166 + Documentation/infiniband/user_verbs.rst | 75 + Documentation/input/devices/alps.rst | 390 + Documentation/input/devices/amijoy.rst | 263 + Documentation/input/devices/appletouch.rst | 94 + Documentation/input/devices/atarikbd.rst | 820 ++ Documentation/input/devices/bcm5974.rst | 70 + Documentation/input/devices/cma3000_d0x.rst | 139 + Documentation/input/devices/cs461x.rst | 43 + Documentation/input/devices/edt-ft5x06.rst | 54 + Documentation/input/devices/elantech.rst | 841 ++ Documentation/input/devices/iforce-protocol.rst | 381 + Documentation/input/devices/index.rst | 19 + Documentation/input/devices/joystick-parport.rst | 611 ++ Documentation/input/devices/ntrig.rst | 137 + Documentation/input/devices/pxrc.rst | 57 + Documentation/input/devices/rotary-encoder.rst | 135 + Documentation/input/devices/sentelic.rst | 901 +++ Documentation/input/devices/walkera0701.rst | 128 + Documentation/input/devices/xpad.rst | 234 + Documentation/input/devices/yealink.rst | 225 + Documentation/input/event-codes.rst | 453 ++ Documentation/input/ff.rst | 265 + Documentation/input/gamepad.rst | 197 + Documentation/input/gameport-programming.rst | 233 + Documentation/input/index.rst | 19 + Documentation/input/input-programming.rst | 348 + Documentation/input/input.rst | 281 + Documentation/input/input_kapi.rst | 17 + Documentation/input/input_uapi.rst | 22 + Documentation/input/interactive.svg | 24 + Documentation/input/joydev/index.rst | 17 + Documentation/input/joydev/joystick-api.rst | 348 + Documentation/input/joydev/joystick.rst | 586 ++ Documentation/input/multi-touch-protocol.rst | 415 + Documentation/input/notifier.rst | 55 + Documentation/input/shape.svg | 39 + Documentation/input/uinput.rst | 245 + Documentation/input/userio.rst | 85 + Documentation/isdn/credits.rst | 73 + Documentation/isdn/index.rst | 21 + Documentation/isdn/interface_capi.rst | 336 + Documentation/isdn/m_isdn.rst | 9 + Documentation/kbuild/Kconfig.recursion-issue-01 | 57 + Documentation/kbuild/Kconfig.recursion-issue-02 | 63 + Documentation/kbuild/Kconfig.select-break | 33 + Documentation/kbuild/gcc-plugins.rst | 133 + Documentation/kbuild/headers_install.rst | 44 + Documentation/kbuild/index.rst | 30 + Documentation/kbuild/issues.rst | 15 + Documentation/kbuild/kbuild.rst | 297 + Documentation/kbuild/kconfig-language.rst | 746 ++ Documentation/kbuild/kconfig-macro-language.rst | 247 + Documentation/kbuild/kconfig.rst | 307 + Documentation/kbuild/llvm.rst | 179 + Documentation/kbuild/makefiles.rst | 1693 ++++ Documentation/kbuild/modules.rst | 561 ++ Documentation/kbuild/reproducible-builds.rst | 137 + Documentation/kernel-hacking/hacking.rst | 830 ++ Documentation/kernel-hacking/index.rst | 11 + Documentation/kernel-hacking/locking.rst | 1451 ++++ Documentation/leds/index.rst | 28 + Documentation/leds/leds-blinkm.rst | 84 + Documentation/leds/leds-class-flash.rst | 90 + Documentation/leds/leds-class-multicolor.rst | 86 + Documentation/leds/leds-class.rst | 179 + Documentation/leds/leds-el15203000.rst | 140 + Documentation/leds/leds-lm3556.rst | 137 + Documentation/leds/leds-lp3944.rst | 59 + Documentation/leds/leds-lp5521.rst | 115 + Documentation/leds/leds-lp5523.rst | 147 + Documentation/leds/leds-lp5562.rst | 137 + Documentation/leds/leds-lp55xx.rst | 224 + Documentation/leds/leds-mlxcpld.rst | 118 + Documentation/leds/leds-qcom-lpg.rst | 78 + Documentation/leds/leds-sc27xx.rst | 27 + Documentation/leds/ledtrig-oneshot.rst | 44 + Documentation/leds/ledtrig-transient.rst | 160 + Documentation/leds/ledtrig-usbport.rst | 46 + Documentation/leds/uleds.rst | 37 + Documentation/leds/well-known-leds.txt | 72 + Documentation/litmus-tests/README | 35 + ...b__after_atomic-is-stronger-than-acquire.litmus | 32 + ...Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 25 + .../litmus-tests/rcu/RCU+sync+free.litmus | 42 + .../litmus-tests/rcu/RCU+sync+read.litmus | 37 + Documentation/livepatch/api.rst | 30 + Documentation/livepatch/callbacks.rst | 133 + Documentation/livepatch/cumulative-patches.rst | 102 + Documentation/livepatch/index.rst | 24 + Documentation/livepatch/livepatch.rst | 448 ++ Documentation/livepatch/module-elf-format.rst | 309 + Documentation/livepatch/reliable-stacktrace.rst | 309 + Documentation/livepatch/shadow-vars.rst | 226 + Documentation/livepatch/system-state.rst | 167 + Documentation/locking/futex-requeue-pi.rst | 132 + Documentation/locking/hwspinlock.rst | 485 ++ Documentation/locking/index.rst | 33 + Documentation/locking/lockdep-design.rst | 663 ++ Documentation/locking/lockstat.rst | 204 + Documentation/locking/locktorture.rst | 169 + Documentation/locking/locktypes.rst | 534 ++ Documentation/locking/mutex-design.rst | 152 + Documentation/locking/percpu-rw-semaphore.rst | 28 + Documentation/locking/pi-futex.rst | 122 + Documentation/locking/preempt-locking.rst | 144 + Documentation/locking/robust-futex-ABI.rst | 184 + Documentation/locking/robust-futexes.rst | 221 + Documentation/locking/rt-mutex-design.rst | 574 ++ Documentation/locking/rt-mutex.rst | 77 + Documentation/locking/seqlock.rst | 239 + Documentation/locking/spinlocks.rst | 165 + Documentation/locking/ww-mutex-design.rst | 393 + Documentation/loongarch/booting.rst | 42 + Documentation/loongarch/features.rst | 3 + Documentation/loongarch/index.rst | 22 + Documentation/loongarch/introduction.rst | 390 + Documentation/loongarch/irq-chip-model.rst | 160 + Documentation/m68k/buddha-driver.rst | 209 + Documentation/m68k/features.rst | 3 + Documentation/m68k/index.rst | 20 + Documentation/m68k/kernel-options.rst | 911 +++ Documentation/maintainer/configure-git.rst | 64 + Documentation/maintainer/index.rst | 18 + .../maintainer/maintainer-entry-profile.rst | 106 + Documentation/maintainer/messy-diffstat.rst | 96 + Documentation/maintainer/modifying-patches.rst | 50 + Documentation/maintainer/pull-requests.rst | 178 + Documentation/maintainer/rebasing-and-merging.rst | 226 + Documentation/memory-barriers.txt | 3007 +++++++ Documentation/mhi/index.rst | 18 + Documentation/mhi/mhi.rst | 218 + Documentation/mhi/topology.rst | 60 + Documentation/mips/booting.rst | 28 + Documentation/mips/features.rst | 3 + Documentation/mips/index.rst | 21 + Documentation/mips/ingenic-tcu.rst | 71 + Documentation/misc-devices/ad525x_dpot.rst | 57 + Documentation/misc-devices/apds990x.rst | 128 + Documentation/misc-devices/bh1770glc.rst | 135 + Documentation/misc-devices/c2port.rst | 94 + Documentation/misc-devices/dw-xdata-pcie.rst | 64 + Documentation/misc-devices/eeprom.rst | 107 + Documentation/misc-devices/ibmvmc.rst | 227 + Documentation/misc-devices/ics932s401.rst | 36 + Documentation/misc-devices/index.rst | 32 + Documentation/misc-devices/isl29003.rst | 75 + Documentation/misc-devices/lis3lv02d.rst | 99 + Documentation/misc-devices/max6875.rst | 136 + Documentation/misc-devices/oxsemi-tornado.rst | 131 + Documentation/misc-devices/pci-endpoint-test.rst | 56 + Documentation/misc-devices/spear-pcie-gadget.rst | 170 + Documentation/misc-devices/uacce.rst | 176 + Documentation/misc-devices/xilinx_sdfec.rst | 292 + Documentation/mm/active_mm.rst | 91 + Documentation/mm/arch_pgtable_helpers.rst | 260 + Documentation/mm/balance.rst | 102 + Documentation/mm/bootmem.rst | 5 + Documentation/mm/damon/api.rst | 20 + Documentation/mm/damon/design.rst | 176 + Documentation/mm/damon/faq.rst | 50 + Documentation/mm/damon/index.rst | 29 + Documentation/mm/free_page_reporting.rst | 40 + Documentation/mm/frontswap.rst | 266 + Documentation/mm/highmem.rst | 190 + Documentation/mm/hmm.rst | 452 ++ Documentation/mm/hugetlbfs_reserv.rst | 596 ++ Documentation/mm/hwpoison.rst | 184 + Documentation/mm/index.rst | 69 + Documentation/mm/ksm.rst | 87 + Documentation/mm/memory-model.rst | 177 + Documentation/mm/mmu_notifier.rst | 99 + Documentation/mm/multigen_lru.rst | 159 + Documentation/mm/numa.rst | 150 + Documentation/mm/oom.rst | 5 + Documentation/mm/overcommit-accounting.rst | 86 + Documentation/mm/page_allocation.rst | 5 + Documentation/mm/page_cache.rst | 5 + Documentation/mm/page_frags.rst | 45 + Documentation/mm/page_migration.rst | 195 + Documentation/mm/page_owner.rst | 189 + Documentation/mm/page_reclaim.rst | 5 + Documentation/mm/page_table_check.rst | 75 + Documentation/mm/page_tables.rst | 5 + Documentation/mm/physical_memory.rst | 5 + Documentation/mm/process_addrs.rst | 5 + Documentation/mm/remap_file_pages.rst | 33 + Documentation/mm/shmfs.rst | 5 + Documentation/mm/slab.rst | 5 + Documentation/mm/slub.rst | 461 ++ Documentation/mm/split_page_table_lock.rst | 100 + Documentation/mm/swap.rst | 5 + Documentation/mm/transhuge.rst | 187 + Documentation/mm/unevictable-lru.rst | 554 ++ Documentation/mm/vmalloc.rst | 5 + Documentation/mm/vmalloced-kernel-stacks.rst | 153 + Documentation/mm/vmemmap_dedup.rst | 249 + Documentation/mm/z3fold.rst | 30 + Documentation/mm/zsmalloc.rst | 84 + Documentation/netlabel/cipso_ipv4.rst | 56 + Documentation/netlabel/draft_ietf.rst | 5 + Documentation/netlabel/index.rst | 21 + Documentation/netlabel/introduction.rst | 52 + Documentation/netlabel/lsm_interface.rst | 53 + Documentation/networking/6lowpan.rst | 53 + Documentation/networking/6pack.rst | 191 + Documentation/networking/af_xdp.rst | 640 ++ Documentation/networking/alias.rst | 49 + Documentation/networking/arcnet-hardware.rst | 3234 ++++++++ Documentation/networking/arcnet.rst | 594 ++ Documentation/networking/atm.rst | 14 + Documentation/networking/ax25.rst | 16 + Documentation/networking/bareudp.rst | 58 + Documentation/networking/batman-adv.rst | 168 + Documentation/networking/bonding.rst | 2922 +++++++ Documentation/networking/bridge.rst | 21 + Documentation/networking/caif/caif.rst | 138 + Documentation/networking/caif/index.rst | 12 + Documentation/networking/caif/linux_caif.rst | 195 + Documentation/networking/can.rst | 1475 ++++ Documentation/networking/can_ucan_protocol.rst | 332 + Documentation/networking/cdc_mbim.rst | 355 + Documentation/networking/checksum-offloads.rst | 143 + Documentation/networking/dccp.rst | 219 + Documentation/networking/dctcp.rst | 52 + .../networking/device_drivers/appletalk/cops.rst | 80 + .../networking/device_drivers/appletalk/index.rst | 18 + .../networking/device_drivers/atm/cxacru-cf.py | 48 + .../networking/device_drivers/atm/cxacru.rst | 120 + .../networking/device_drivers/atm/fore200e.rst | 66 + .../networking/device_drivers/atm/index.rst | 20 + .../networking/device_drivers/atm/iphase.rst | 193 + .../networking/device_drivers/cable/index.rst | 18 + .../networking/device_drivers/cable/sb1000.rst | 222 + .../networking/device_drivers/can/can327.rst | 331 + .../device_drivers/can/ctu/ctucanfd-driver.rst | 639 ++ .../device_drivers/can/ctu/fsm_txt_buffer_user.svg | 151 + .../device_drivers/can/freescale/flexcan.rst | 54 + .../networking/device_drivers/can/index.rst | 22 + .../networking/device_drivers/cellular/index.rst | 18 + .../device_drivers/cellular/qualcomm/rmnet.rst | 197 + .../device_drivers/ethernet/3com/3c509.rst | 249 + .../device_drivers/ethernet/3com/vortex.rst | 459 ++ .../device_drivers/ethernet/altera/altera_tse.rst | 286 + .../device_drivers/ethernet/amazon/ena.rst | 317 + .../device_drivers/ethernet/aquantia/atlantic.rst | 556 ++ .../device_drivers/ethernet/chelsio/cxgb.rst | 393 + .../device_drivers/ethernet/cirrus/cs89x0.rst | 647 ++ .../device_drivers/ethernet/davicom/dm9000.rst | 171 + .../device_drivers/ethernet/dec/dmfe.rst | 71 + .../device_drivers/ethernet/dlink/dl2k.rst | 314 + .../device_drivers/ethernet/freescale/dpaa.rst | 269 + .../ethernet/freescale/dpaa2/dpio-driver.rst | 161 + .../ethernet/freescale/dpaa2/ethernet-driver.rst | 186 + .../ethernet/freescale/dpaa2/index.rst | 12 + .../ethernet/freescale/dpaa2/mac-phy-support.rst | 191 + .../ethernet/freescale/dpaa2/overview.rst | 406 + .../ethernet/freescale/dpaa2/switch-driver.rst | 217 + .../device_drivers/ethernet/freescale/gianfar.rst | 51 + .../device_drivers/ethernet/google/gve.rst | 166 + .../device_drivers/ethernet/huawei/hinic.rst | 128 + .../networking/device_drivers/ethernet/index.rst | 62 + .../device_drivers/ethernet/intel/e100.rst | 188 + .../device_drivers/ethernet/intel/e1000.rst | 463 ++ .../device_drivers/ethernet/intel/e1000e.rst | 383 + .../device_drivers/ethernet/intel/fm10k.rst | 142 + .../device_drivers/ethernet/intel/i40e.rst | 771 ++ .../device_drivers/ethernet/intel/iavf.rst | 331 + .../device_drivers/ethernet/intel/ice.rst | 1040 +++ .../device_drivers/ethernet/intel/igb.rst | 213 + .../device_drivers/ethernet/intel/igbvf.rst | 65 + .../device_drivers/ethernet/intel/ixgb.rst | 468 ++ .../device_drivers/ethernet/intel/ixgbe.rst | 557 ++ .../device_drivers/ethernet/intel/ixgbevf.rst | 67 + .../device_drivers/ethernet/marvell/octeon_ep.rst | 35 + .../device_drivers/ethernet/marvell/octeontx2.rst | 289 + .../device_drivers/ethernet/mellanox/mlx5.rst | 762 ++ .../device_drivers/ethernet/microsoft/netvsc.rst | 120 + .../device_drivers/ethernet/neterion/s2io.rst | 196 + .../device_drivers/ethernet/netronome/nfp.rst | 249 + .../device_drivers/ethernet/pensando/ionic.rst | 274 + .../device_drivers/ethernet/smsc/smc9.rst | 48 + .../device_drivers/ethernet/stmicro/stmmac.rst | 700 ++ .../ethernet/ti/am65_nuss_cpsw_switchdev.rst | 143 + .../networking/device_drivers/ethernet/ti/cpsw.rst | 587 ++ .../device_drivers/ethernet/ti/cpsw_switchdev.rst | 242 + .../networking/device_drivers/ethernet/ti/tlan.rst | 140 + .../device_drivers/ethernet/toshiba/spider_net.rst | 202 + .../device_drivers/ethernet/wangxun/ngbe.rst | 14 + .../device_drivers/ethernet/wangxun/txgbe.rst | 20 + .../networking/device_drivers/fddi/defza.rst | 63 + .../networking/device_drivers/fddi/index.rst | 19 + .../networking/device_drivers/fddi/skfp.rst | 253 + .../networking/device_drivers/hamradio/baycom.rst | 174 + .../networking/device_drivers/hamradio/index.rst | 19 + .../device_drivers/hamradio/z8530drv.rst | 686 ++ Documentation/networking/device_drivers/index.rst | 28 + .../networking/device_drivers/qlogic/index.rst | 18 + .../networking/device_drivers/qlogic/qlge.rst | 118 + .../networking/device_drivers/wifi/index.rst | 20 + .../device_drivers/wifi/intel/ipw2100.rst | 323 + .../device_drivers/wifi/intel/ipw2200.rst | 526 ++ .../networking/device_drivers/wifi/ray_cs.rst | 165 + .../networking/device_drivers/wwan/index.rst | 19 + .../networking/device_drivers/wwan/iosm.rst | 96 + .../networking/device_drivers/wwan/t7xx.rst | 120 + .../networking/devlink/am65-nuss-cpsw-switch.rst | 26 + Documentation/networking/devlink/bnxt.rst | 82 + Documentation/networking/devlink/devlink-dpipe.rst | 252 + Documentation/networking/devlink/devlink-flash.rst | 121 + .../networking/devlink/devlink-health.rst | 119 + Documentation/networking/devlink/devlink-info.rst | 210 + .../networking/devlink/devlink-linecard.rst | 122 + .../networking/devlink/devlink-params.rst | 139 + Documentation/networking/devlink/devlink-port.rst | 234 + .../networking/devlink/devlink-region.rst | 70 + .../networking/devlink/devlink-reload.rst | 81 + .../networking/devlink/devlink-resource.rst | 76 + .../networking/devlink/devlink-selftests.rst | 38 + Documentation/networking/devlink/devlink-trap.rst | 627 ++ Documentation/networking/devlink/hns3.rst | 25 + Documentation/networking/devlink/ice.rst | 256 + Documentation/networking/devlink/index.rst | 67 + Documentation/networking/devlink/ionic.rst | 29 + Documentation/networking/devlink/iosm.rst | 162 + Documentation/networking/devlink/mlx4.rst | 56 + Documentation/networking/devlink/mlx5.rst | 76 + Documentation/networking/devlink/mlxsw.rst | 105 + Documentation/networking/devlink/mv88e6xxx.rst | 28 + Documentation/networking/devlink/netdevsim.rst | 99 + Documentation/networking/devlink/nfp.rst | 65 + Documentation/networking/devlink/octeontx2.rst | 42 + Documentation/networking/devlink/prestera.rst | 141 + Documentation/networking/devlink/qed.rst | 26 + .../networking/devlink/ti-cpsw-switch.rst | 31 + Documentation/networking/dns_resolver.rst | 155 + Documentation/networking/driver.rst | 97 + Documentation/networking/dsa/b53.rst | 183 + Documentation/networking/dsa/bcm_sf2.rst | 115 + Documentation/networking/dsa/configuration.rst | 458 ++ Documentation/networking/dsa/dsa.rst | 1129 +++ Documentation/networking/dsa/index.rst | 13 + Documentation/networking/dsa/lan9303.rst | 37 + Documentation/networking/dsa/sja1105.rst | 445 ++ Documentation/networking/eql.rst | 373 + Documentation/networking/ethtool-netlink.rst | 1790 +++++ Documentation/networking/failover.rst | 18 + Documentation/networking/fib_trie.rst | 149 + Documentation/networking/filter.rst | 685 ++ Documentation/networking/gen_stats.rst | 129 + Documentation/networking/generic-hdlc.rst | 170 + Documentation/networking/generic_netlink.rst | 9 + Documentation/networking/gtp.rst | 251 + Documentation/networking/ieee802154.rst | 182 + Documentation/networking/ila.rst | 296 + Documentation/networking/index.rst | 128 + Documentation/networking/ioam6-sysctl.rst | 26 + Documentation/networking/ip-sysctl.rst | 3067 ++++++++ Documentation/networking/ip_dynaddr.rst | 40 + Documentation/networking/ipddp.rst | 78 + Documentation/networking/ipsec.rst | 46 + Documentation/networking/ipv6.rst | 78 + Documentation/networking/ipvlan.rst | 189 + Documentation/networking/ipvs-sysctl.rst | 312 + Documentation/networking/j1939.rst | 460 ++ Documentation/networking/kapi.rst | 159 + Documentation/networking/kcm.rst | 290 + Documentation/networking/l2tp.rst | 677 ++ Documentation/networking/lapb-module.rst | 305 + .../networking/mac80211-auth-assoc-deauth.txt | 95 + Documentation/networking/mac80211-injection.rst | 106 + .../networking/mac80211_hwsim/hostapd.conf | 11 + .../networking/mac80211_hwsim/mac80211_hwsim.rst | 80 + .../networking/mac80211_hwsim/wpa_supplicant.conf | 10 + Documentation/networking/mctp.rst | 320 + Documentation/networking/mpls-sysctl.rst | 57 + Documentation/networking/mptcp-sysctl.rst | 76 + Documentation/networking/msg_zerocopy.rst | 256 + Documentation/networking/multiqueue.rst | 78 + Documentation/networking/net_dim.rst | 176 + Documentation/networking/net_failover.rst | 184 + Documentation/networking/netconsole.rst | 239 + Documentation/networking/netdev-features.rst | 205 + Documentation/networking/netdevices.rst | 299 + Documentation/networking/netfilter-sysctl.rst | 17 + Documentation/networking/netif-msg.rst | 95 + .../networking/nexthop-group-resilient.rst | 293 + Documentation/networking/nf_conntrack-sysctl.rst | 203 + Documentation/networking/nf_flowtable.rst | 235 + Documentation/networking/nfc.rst | 130 + Documentation/networking/openvswitch.rst | 251 + Documentation/networking/operstates.rst | 187 + Documentation/networking/packet_mmap.rst | 1083 +++ Documentation/networking/page_pool.rst | 223 + Documentation/networking/phonet.rst | 230 + Documentation/networking/phy.rst | 547 ++ Documentation/networking/pktgen.rst | 410 + Documentation/networking/plip.rst | 222 + Documentation/networking/ppp_generic.rst | 456 ++ Documentation/networking/proc_net_tcp.rst | 57 + Documentation/networking/radiotap-headers.rst | 159 + Documentation/networking/rds.rst | 448 ++ Documentation/networking/regulatory.rst | 209 + Documentation/networking/representors.rst | 259 + Documentation/networking/rxrpc.rst | 1167 +++ Documentation/networking/scaling.rst | 523 ++ Documentation/networking/sctp.rst | 42 + Documentation/networking/secid.rst | 20 + Documentation/networking/seg6-sysctl.rst | 39 + Documentation/networking/segmentation-offloads.rst | 184 + Documentation/networking/sfp-phylink.rst | 284 + Documentation/networking/skbuff.rst | 37 + Documentation/networking/smc-sysctl.rst | 61 + Documentation/networking/snmp_counter.rst | 1793 +++++ Documentation/networking/statistics.rst | 220 + Documentation/networking/strparser.rst | 240 + Documentation/networking/switchdev.rst | 564 ++ Documentation/networking/sysfs-tagging.rst | 48 + Documentation/networking/tc-actions-env-rules.rst | 29 + Documentation/networking/tcp-thin.rst | 52 + Documentation/networking/team.rst | 8 + Documentation/networking/timestamping.rst | 772 ++ Documentation/networking/tipc.rst | 215 + Documentation/networking/tls-offload-layers.svg | 1 + .../networking/tls-offload-reorder-bad.svg | 1 + .../networking/tls-offload-reorder-good.svg | 1 + Documentation/networking/tls-offload.rst | 539 ++ Documentation/networking/tls.rst | 288 + Documentation/networking/tproxy.rst | 109 + Documentation/networking/tuntap.rst | 259 + Documentation/networking/udplite.rst | 291 + Documentation/networking/vrf.rst | 464 ++ Documentation/networking/vxlan.rst | 88 + Documentation/networking/x25-iface.rst | 82 + Documentation/networking/x25.rst | 46 + Documentation/networking/xfrm_device.rst | 151 + Documentation/networking/xfrm_proc.rst | 113 + Documentation/networking/xfrm_sync.rst | 189 + Documentation/networking/xfrm_sysctl.rst | 11 + Documentation/nios2/features.rst | 3 + Documentation/nios2/index.rst | 12 + Documentation/nios2/nios2.rst | 24 + Documentation/nvdimm/maintainer-entry-profile.rst | 60 + Documentation/openrisc/features.rst | 3 + Documentation/openrisc/index.rst | 20 + Documentation/openrisc/openrisc_port.rst | 121 + Documentation/openrisc/todo.rst | 15 + Documentation/parisc/debugging.rst | 46 + Documentation/parisc/features.rst | 3 + Documentation/parisc/index.rst | 20 + Documentation/parisc/registers.rst | 154 + Documentation/pcmcia/devicetable.rst | 37 + Documentation/pcmcia/driver-changes.rst | 160 + Documentation/pcmcia/driver.rst | 30 + Documentation/pcmcia/index.rst | 20 + Documentation/pcmcia/locking.rst | 133 + Documentation/peci/index.rst | 16 + Documentation/peci/peci.rst | 51 + Documentation/power/apm-acpi.rst | 36 + Documentation/power/basic-pm-debugging.rst | 269 + Documentation/power/charger-manager.rst | 205 + Documentation/power/drivers-testing.rst | 52 + Documentation/power/energy-model.rst | 244 + Documentation/power/freezing-of-tasks.rst | 245 + Documentation/power/index.rst | 46 + Documentation/power/opp.rst | 381 + Documentation/power/pci.rst | 1133 +++ Documentation/power/pm_qos_interface.rst | 218 + Documentation/power/power_supply_class.rst | 288 + Documentation/power/powercap/dtpm.rst | 212 + Documentation/power/powercap/powercap.rst | 262 + Documentation/power/regulator/consumer.rst | 229 + Documentation/power/regulator/design.rst | 38 + Documentation/power/regulator/machine.rst | 97 + Documentation/power/regulator/overview.rst | 178 + Documentation/power/regulator/regulator.rst | 32 + Documentation/power/runtime_pm.rst | 969 +++ Documentation/power/s2ram.rst | 87 + Documentation/power/suspend-and-cpuhotplug.rst | 287 + Documentation/power/suspend-and-interrupts.rst | 137 + Documentation/power/swsusp-and-swap-files.rst | 63 + Documentation/power/swsusp-dmcrypt.rst | 140 + Documentation/power/swsusp.rst | 503 ++ Documentation/power/tricks.rst | 29 + Documentation/power/userland-swsusp.rst | 193 + Documentation/power/video.rst | 213 + Documentation/powerpc/associativity.rst | 105 + Documentation/powerpc/booting.rst | 110 + Documentation/powerpc/bootwrapper.rst | 131 + Documentation/powerpc/cpu_families.rst | 224 + Documentation/powerpc/cpu_features.rst | 60 + Documentation/powerpc/cxl.rst | 469 ++ Documentation/powerpc/cxlflash.rst | 433 + Documentation/powerpc/dawr-power9.rst | 101 + Documentation/powerpc/dscr.rst | 87 + Documentation/powerpc/eeh-pci-error-recovery.rst | 336 + Documentation/powerpc/elf_hwcaps.rst | 231 + Documentation/powerpc/elfnote.rst | 41 + Documentation/powerpc/features.rst | 3 + Documentation/powerpc/firmware-assisted-dump.rst | 381 + Documentation/powerpc/hvcs.rst | 581 ++ Documentation/powerpc/imc.rst | 199 + Documentation/powerpc/index.rst | 46 + Documentation/powerpc/isa-versions.rst | 101 + Documentation/powerpc/kasan.txt | 58 + Documentation/powerpc/kaslr-booke32.rst | 42 + Documentation/powerpc/mpc52xx.rst | 43 + Documentation/powerpc/papr_hcalls.rst | 302 + .../powerpc/pci_iov_resource_on_powernv.rst | 312 + Documentation/powerpc/pmu-ebb.rst | 138 + Documentation/powerpc/ptrace.rst | 157 + Documentation/powerpc/qe_firmware.rst | 296 + Documentation/powerpc/syscall64-abi.rst | 153 + Documentation/powerpc/transactional_memory.rst | 274 + Documentation/powerpc/ultravisor.rst | 1117 +++ Documentation/powerpc/vas-api.rst | 305 + Documentation/powerpc/vcpudispatch_stats.rst | 75 + Documentation/process/1.Intro.rst | 268 + Documentation/process/2.Process.rst | 496 ++ Documentation/process/3.Early-stage.rst | 223 + Documentation/process/4.Coding.rst | 421 + Documentation/process/5.Posting.rst | 347 + Documentation/process/6.Followthrough.rst | 212 + Documentation/process/7.AdvancedTopics.rst | 178 + Documentation/process/8.Conclusion.rst | 73 + Documentation/process/adding-syscalls.rst | 577 ++ Documentation/process/applying-patches.rst | 444 ++ Documentation/process/botching-up-ioctls.rst | 225 + Documentation/process/changes.rst | 568 ++ Documentation/process/clang-format.rst | 184 + .../process/code-of-conduct-interpretation.rst | 158 + Documentation/process/code-of-conduct.rst | 86 + Documentation/process/coding-style.rst | 1271 +++ Documentation/process/deprecated.rst | 348 + Documentation/process/development-process.rst | 28 + Documentation/process/email-clients.rst | 352 + .../process/embargoed-hardware-issues.rst | 315 + Documentation/process/handling-regressions.rst | 746 ++ Documentation/process/howto.rst | 626 ++ Documentation/process/index.rst | 74 + Documentation/process/kernel-docs.rst | 620 ++ Documentation/process/kernel-driver-statement.rst | 202 + .../process/kernel-enforcement-statement.rst | 163 + Documentation/process/license-rules.rst | 485 ++ Documentation/process/magic-number.rst | 85 + Documentation/process/maintainer-handbooks.rst | 19 + Documentation/process/maintainer-netdev.rst | 331 + Documentation/process/maintainer-pgp-guide.rst | 961 +++ Documentation/process/maintainer-tip.rst | 799 ++ Documentation/process/maintainers.rst | 1 + Documentation/process/management-style.rst | 290 + Documentation/process/programming-language.rst | 46 + Documentation/process/researcher-guidelines.rst | 143 + Documentation/process/stable-api-nonsense.rst | 204 + Documentation/process/stable-kernel-rules.rst | 204 + Documentation/process/submit-checklist.rst | 120 + Documentation/process/submitting-patches.rst | 838 ++ .../process/volatile-considered-harmful.rst | 125 + Documentation/riscv/boot-image-header.rst | 62 + Documentation/riscv/features.rst | 3 + Documentation/riscv/index.rst | 20 + Documentation/riscv/patch-acceptance.rst | 35 + Documentation/riscv/uabi.rst | 6 + Documentation/riscv/vm-layout.rst | 99 + Documentation/rust/arch-support.rst | 19 + Documentation/rust/coding-guidelines.rst | 216 + Documentation/rust/general-information.rst | 79 + Documentation/rust/index.rst | 22 + Documentation/rust/quick-start.rst | 232 + Documentation/s390/3270.ChangeLog | 44 + Documentation/s390/3270.rst | 298 + Documentation/s390/cds.rst | 530 ++ Documentation/s390/common_io.rst | 140 + Documentation/s390/config3270.sh | 76 + Documentation/s390/driver-model.rst | 328 + Documentation/s390/features.rst | 3 + Documentation/s390/index.rst | 30 + Documentation/s390/monreader.rst | 212 + Documentation/s390/pci.rst | 133 + Documentation/s390/qeth.rst | 64 + Documentation/s390/s390dbf.rst | 478 ++ Documentation/s390/text_files.rst | 11 + Documentation/s390/vfio-ap-locking.rst | 115 + Documentation/s390/vfio-ap.rst | 1071 +++ Documentation/s390/vfio-ccw.rst | 445 ++ Documentation/s390/zfcpdump.rst | 50 + Documentation/scheduler/completion.rst | 293 + Documentation/scheduler/index.rst | 30 + Documentation/scheduler/sched-arch.rst | 76 + Documentation/scheduler/sched-bwc.rst | 246 + Documentation/scheduler/sched-capacity.rst | 441 ++ Documentation/scheduler/sched-deadline.rst | 888 +++ Documentation/scheduler/sched-debug.rst | 54 + Documentation/scheduler/sched-design-CFS.rst | 249 + Documentation/scheduler/sched-domains.rst | 81 + Documentation/scheduler/sched-energy.rst | 427 + Documentation/scheduler/sched-nice-design.rst | 112 + Documentation/scheduler/sched-pelt.c | 109 + Documentation/scheduler/sched-rt-group.rst | 185 + Documentation/scheduler/sched-stats.rst | 167 + Documentation/scheduler/schedutil.rst | 173 + Documentation/scheduler/text_files.rst | 5 + Documentation/scsi/53c700.rst | 134 + Documentation/scsi/BusLogic.rst | 581 ++ Documentation/scsi/ChangeLog.arcmsr | 118 + Documentation/scsi/ChangeLog.ips | 122 + Documentation/scsi/ChangeLog.lpfc | 1865 +++++ Documentation/scsi/ChangeLog.megaraid | 614 ++ Documentation/scsi/ChangeLog.megaraid_sas | 641 ++ Documentation/scsi/ChangeLog.ncr53c8xx | 495 ++ Documentation/scsi/ChangeLog.sym53c8xx | 593 ++ Documentation/scsi/ChangeLog.sym53c8xx_2 | 144 + Documentation/scsi/FlashPoint.rst | 176 + Documentation/scsi/LICENSE.FlashPoint | 60 + Documentation/scsi/NinjaSCSI.rst | 164 + Documentation/scsi/aacraid.rst | 177 + Documentation/scsi/advansys.rst | 272 + Documentation/scsi/aha152x.rst | 204 + Documentation/scsi/aic79xx.rst | 593 ++ Documentation/scsi/aic7xxx.rst | 458 ++ Documentation/scsi/arcmsr_spec.rst | 907 +++ Documentation/scsi/bfa.rst | 92 + Documentation/scsi/bnx2fc.rst | 81 + Documentation/scsi/cxgb3i.rst | 90 + Documentation/scsi/dc395x.rst | 117 + Documentation/scsi/dpti.rst | 92 + Documentation/scsi/g_NCR5380.rst | 93 + Documentation/scsi/hpsa.rst | 129 + Documentation/scsi/hptiop.rst | 215 + Documentation/scsi/index.rst | 51 + Documentation/scsi/libsas.rst | 458 ++ .../scsi/link_power_management_policy.rst | 25 + Documentation/scsi/lpfc.rst | 81 + Documentation/scsi/megaraid.rst | 77 + Documentation/scsi/ncr53c8xx.rst | 2169 +++++ Documentation/scsi/ppa.rst | 18 + Documentation/scsi/qlogicfas.rst | 87 + Documentation/scsi/scsi-changer.rst | 184 + Documentation/scsi/scsi-generic.rst | 118 + Documentation/scsi/scsi-parameters.rst | 108 + Documentation/scsi/scsi.rst | 47 + Documentation/scsi/scsi_eh.rst | 510 ++ Documentation/scsi/scsi_fc_transport.rst | 560 ++ Documentation/scsi/scsi_mid_low_api.rst | 1302 +++ Documentation/scsi/scsi_transport_srp/figures.rst | 6 + .../scsi_transport_srp/rport_state_diagram.dot | 26 + Documentation/scsi/sd-parameters.rst | 27 + Documentation/scsi/smartpqi.rst | 78 + Documentation/scsi/st.rst | 673 ++ Documentation/scsi/sym53c500_cs.rst | 29 + Documentation/scsi/sym53c8xx_2.rst | 1209 +++ Documentation/scsi/tcm_qla2xxx.rst | 36 + Documentation/scsi/ufs.rst | 210 + Documentation/scsi/wd719x.rst | 24 + Documentation/security/IMA-templates.rst | 111 + Documentation/security/SCTP.rst | 344 + Documentation/security/credentials.rst | 564 ++ Documentation/security/digsig.rst | 101 + Documentation/security/index.rst | 20 + Documentation/security/keys/core.rst | 1849 +++++ Documentation/security/keys/ecryptfs.rst | 73 + Documentation/security/keys/index.rst | 11 + Documentation/security/keys/request-key.rst | 207 + Documentation/security/keys/trusted-encrypted.rst | 428 + Documentation/security/landlock.rst | 101 + Documentation/security/lsm-development.rst | 17 + Documentation/security/lsm.rst | 131 + Documentation/security/sak.rst | 91 + Documentation/security/secrets/coco.rst | 103 + Documentation/security/secrets/index.rst | 9 + Documentation/security/self-protection.rst | 316 + Documentation/security/siphash.rst | 199 + Documentation/security/tpm/index.rst | 10 + Documentation/security/tpm/tpm_event_log.rst | 55 + Documentation/security/tpm/tpm_ftpm_tee.rst | 27 + Documentation/security/tpm/tpm_vtpm_proxy.rst | 50 + Documentation/security/tpm/xen-tpmfront.rst | 124 + Documentation/sh/booting.rst | 12 + Documentation/sh/features.rst | 3 + Documentation/sh/index.rst | 56 + Documentation/sh/new-machine.rst | 277 + Documentation/sh/register-banks.rst | 40 + Documentation/sound/alsa-configuration.rst | 2752 +++++++ Documentation/sound/cards/audigy-mixer.rst | 368 + Documentation/sound/cards/audiophile-usb.rst | 550 ++ Documentation/sound/cards/bt87x.rst | 83 + Documentation/sound/cards/cmipci.rst | 272 + Documentation/sound/cards/emu10k1-jack.rst | 78 + Documentation/sound/cards/hdspm.rst | 379 + Documentation/sound/cards/img-spdif-in.rst | 53 + Documentation/sound/cards/index.rst | 19 + Documentation/sound/cards/joystick.rst | 91 + Documentation/sound/cards/maya44.rst | 186 + Documentation/sound/cards/mixart.rst | 110 + Documentation/sound/cards/multisound.sh | 1139 +++ Documentation/sound/cards/sb-live-mixer.rst | 373 + Documentation/sound/cards/serial-u16550.rst | 93 + Documentation/sound/cards/via82xx-mixer.rst | 8 + .../sound/designs/channel-mapping-api.rst | 164 + Documentation/sound/designs/compress-offload.rst | 328 + Documentation/sound/designs/control-names.rst | 142 + Documentation/sound/designs/index.rst | 17 + Documentation/sound/designs/jack-controls.rst | 48 + Documentation/sound/designs/jack-injection.rst | 166 + Documentation/sound/designs/oss-emulation.rst | 336 + Documentation/sound/designs/powersave.rst | 43 + Documentation/sound/designs/procfile.rst | 238 + Documentation/sound/designs/seq-oss.rst | 371 + Documentation/sound/designs/timestamping.rst | 215 + Documentation/sound/designs/tracepoints.rst | 172 + Documentation/sound/hd-audio/controls.rst | 121 + Documentation/sound/hd-audio/dp-mst.rst | 101 + Documentation/sound/hd-audio/index.rst | 11 + Documentation/sound/hd-audio/models.rst | 809 ++ Documentation/sound/hd-audio/notes.rst | 898 +++ Documentation/sound/hd-audio/realtek-pc-beep.rst | 129 + Documentation/sound/index.rst | 20 + Documentation/sound/kernel-api/alsa-driver-api.rst | 135 + Documentation/sound/kernel-api/index.rst | 8 + .../sound/kernel-api/writing-an-alsa-driver.rst | 4339 ++++++++++ Documentation/sound/soc/clocking.rst | 46 + Documentation/sound/soc/codec-to-codec.rst | 113 + Documentation/sound/soc/codec.rst | 190 + Documentation/sound/soc/dai.rst | 64 + Documentation/sound/soc/dapm.rst | 360 + Documentation/sound/soc/dpcm.rst | 388 + Documentation/sound/soc/index.rst | 20 + Documentation/sound/soc/jack.rst | 72 + Documentation/sound/soc/machine.rst | 97 + Documentation/sound/soc/overview.rst | 69 + Documentation/sound/soc/platform.rst | 78 + Documentation/sound/soc/pops-clicks.rst | 55 + Documentation/sparc/adi.rst | 286 + Documentation/sparc/console.rst | 9 + Documentation/sparc/features.rst | 3 + Documentation/sparc/index.rst | 13 + Documentation/sparc/oradax/dax-hv-api.txt | 1433 ++++ Documentation/sparc/oradax/oracle-dax.rst | 445 ++ Documentation/sphinx-static/theme_overrides.css | 125 + Documentation/sphinx-static/theme_rtd_colors.css | 37 + Documentation/sphinx/automarkup.py | 312 + Documentation/sphinx/cdomain.py | 253 + Documentation/sphinx/kernel_abi.py | 141 + Documentation/sphinx/kernel_feat.py | 166 + Documentation/sphinx/kernel_include.py | 193 + Documentation/sphinx/kerneldoc-preamble.sty | 236 + Documentation/sphinx/kerneldoc.py | 170 + Documentation/sphinx/kernellog.py | 22 + Documentation/sphinx/kfigure.py | 655 ++ Documentation/sphinx/load_config.py | 59 + Documentation/sphinx/maintainers_include.py | 195 + Documentation/sphinx/parallel-wrapper.sh | 33 + Documentation/sphinx/parse-headers.pl | 401 + Documentation/sphinx/requirements.txt | 4 + Documentation/sphinx/rstFlatTable.py | 364 + Documentation/spi/butterfly.rst | 74 + Documentation/spi/index.rst | 22 + Documentation/spi/pxa2xx.rst | 214 + Documentation/spi/spi-lm70llp.rst | 84 + Documentation/spi/spi-sc18is602.rst | 39 + Documentation/spi/spi-summary.rst | 639 ++ Documentation/spi/spidev.rst | 191 + Documentation/staging/crc32.rst | 189 + Documentation/staging/index.rst | 16 + Documentation/staging/lzo.rst | 202 + Documentation/staging/remoteproc.rst | 360 + Documentation/staging/rpmsg.rst | 341 + Documentation/staging/speculation.rst | 92 + Documentation/staging/static-keys.rst | 328 + Documentation/staging/tee.rst | 311 + Documentation/staging/xz.rst | 127 + Documentation/subsystem-apis.rst | 58 + Documentation/target/index.rst | 19 + Documentation/target/scripts.rst | 11 + Documentation/target/target-export-device | 80 + Documentation/target/tcm_mod_builder.py | 656 ++ Documentation/target/tcm_mod_builder.rst | 149 + Documentation/target/tcmu-design.rst | 405 + Documentation/timers/highres.rst | 250 + Documentation/timers/hpet.rst | 30 + Documentation/timers/hrtimers.rst | 178 + Documentation/timers/index.rst | 22 + Documentation/timers/no_hz.rst | 320 + Documentation/timers/timekeeping.rst | 180 + Documentation/timers/timers-howto.rst | 115 + Documentation/tools/index.rst | 20 + Documentation/tools/rtla/Makefile | 53 + Documentation/tools/rtla/common_appendix.rst | 13 + Documentation/tools/rtla/common_hist_options.rst | 23 + Documentation/tools/rtla/common_options.rst | 47 + .../tools/rtla/common_osnoise_description.rst | 8 + .../tools/rtla/common_osnoise_options.rst | 27 + .../tools/rtla/common_timerlat_description.rst | 10 + .../tools/rtla/common_timerlat_options.rst | 28 + Documentation/tools/rtla/common_top_options.rst | 3 + Documentation/tools/rtla/index.rst | 26 + Documentation/tools/rtla/rtla-osnoise-hist.rst | 66 + Documentation/tools/rtla/rtla-osnoise-top.rst | 61 + Documentation/tools/rtla/rtla-osnoise.rst | 59 + Documentation/tools/rtla/rtla-timerlat-hist.rst | 106 + Documentation/tools/rtla/rtla-timerlat-top.rst | 145 + Documentation/tools/rtla/rtla-timerlat.rst | 57 + Documentation/tools/rtla/rtla.rst | 48 + Documentation/trace/boottime-trace.rst | 301 + Documentation/trace/coresight/coresight-config.rst | 294 + .../trace/coresight/coresight-cpu-debug.rst | 193 + Documentation/trace/coresight/coresight-ect.rst | 226 + .../trace/coresight/coresight-etm4x-reference.rst | 827 ++ Documentation/trace/coresight/coresight-perf.rst | 158 + Documentation/trace/coresight/coresight-trbe.rst | 38 + Documentation/trace/coresight/coresight.rst | 691 ++ Documentation/trace/coresight/index.rst | 9 + Documentation/trace/events-kmem.rst | 119 + Documentation/trace/events-msr.rst | 40 + Documentation/trace/events-nmi.rst | 45 + Documentation/trace/events-power.rst | 104 + Documentation/trace/events.rst | 1073 +++ Documentation/trace/fprobe.rst | 174 + Documentation/trace/ftrace-design.rst | 411 + Documentation/trace/ftrace-uses.rst | 348 + Documentation/trace/ftrace.rst | 3570 +++++++++ Documentation/trace/function-graph-fold.vim | 42 + Documentation/trace/hisi-ptt.rst | 298 + Documentation/trace/histogram-design.rst | 2115 +++++ Documentation/trace/histogram.rst | 2909 +++++++ Documentation/trace/hwlat_detector.rst | 88 + Documentation/trace/index.rst | 36 + Documentation/trace/intel_th.rst | 150 + Documentation/trace/kprobes.rst | 788 ++ Documentation/trace/kprobetrace.rst | 261 + Documentation/trace/mmiotrace.rst | 184 + Documentation/trace/osnoise-tracer.rst | 152 + Documentation/trace/postprocess/decode_msr.py | 37 + .../postprocess/trace-pagealloc-postprocess.pl | 418 + .../trace/postprocess/trace-vmscan-postprocess.pl | 758 ++ Documentation/trace/ring-buffer-design.rst | 983 +++ .../trace/rv/da_monitor_instrumentation.rst | 171 + Documentation/trace/rv/da_monitor_synthesis.rst | 147 + Documentation/trace/rv/deterministic_automata.rst | 184 + Documentation/trace/rv/index.rst | 14 + Documentation/trace/rv/monitor_wip.rst | 55 + Documentation/trace/rv/monitor_wwnr.rst | 45 + Documentation/trace/rv/runtime-verification.rst | 231 + Documentation/trace/stm.rst | 143 + Documentation/trace/sys-t.rst | 62 + Documentation/trace/timerlat-tracer.rst | 182 + Documentation/trace/tracepoint-analysis.rst | 338 + Documentation/trace/tracepoints.rst | 175 + Documentation/trace/uprobetracer.rst | 186 + Documentation/trace/user_events.rst | 238 + Documentation/translations/index.rst | 58 + .../translations/it_IT/admin-guide/README.rst | 12 + .../it_IT/admin-guide/kernel-parameters.rst | 12 + .../it_IT/admin-guide/security-bugs.rst | 12 + .../translations/it_IT/core-api/index.rst | 18 + .../it_IT/core-api/memory-allocation.rst | 13 + .../it_IT/core-api/symbol-namespaces.rst | 166 + .../devicetree/bindings/submitting-patches.rst | 11 + .../translations/it_IT/disclaimer-ita.rst | 6 + .../translations/it_IT/doc-guide/index.rst | 24 + .../translations/it_IT/doc-guide/kernel-doc.rst | 561 ++ .../translations/it_IT/doc-guide/parse-headers.rst | 196 + .../translations/it_IT/doc-guide/sphinx.rst | 489 ++ Documentation/translations/it_IT/index.rst | 141 + .../translations/it_IT/kernel-hacking/hacking.rst | 870 ++ .../translations/it_IT/kernel-hacking/index.rst | 16 + .../translations/it_IT/kernel-hacking/locking.rst | 1495 ++++ .../it_IT/maintainer/configure-git.rst | 10 + .../translations/it_IT/networking/netdev-FAQ.rst | 13 + .../translations/it_IT/process/1.Intro.rst | 297 + .../translations/it_IT/process/2.Process.rst | 534 ++ .../translations/it_IT/process/3.Early-stage.rst | 242 + .../translations/it_IT/process/4.Coding.rst | 446 ++ .../translations/it_IT/process/5.Posting.rst | 364 + .../translations/it_IT/process/6.Followthrough.rst | 240 + .../it_IT/process/7.AdvancedTopics.rst | 191 + .../translations/it_IT/process/8.Conclusion.rst | 84 + .../translations/it_IT/process/adding-syscalls.rst | 643 ++ .../it_IT/process/applying-patches.rst | 15 + .../translations/it_IT/process/changes.rst | 517 ++ .../translations/it_IT/process/clang-format.rst | 197 + .../translations/it_IT/process/code-of-conduct.rst | 12 + .../translations/it_IT/process/coding-style.rst | 1213 +++ .../translations/it_IT/process/deprecated.rst | 384 + .../it_IT/process/development-process.rst | 33 + .../translations/it_IT/process/email-clients.rst | 341 + Documentation/translations/it_IT/process/howto.rst | 642 ++ Documentation/translations/it_IT/process/index.rst | 69 + .../translations/it_IT/process/kernel-docs.rst | 18 + .../it_IT/process/kernel-driver-statement.rst | 211 + .../it_IT/process/kernel-enforcement-statement.rst | 175 + .../translations/it_IT/process/license-rules.rst | 500 ++ .../translations/it_IT/process/magic-number.rst | 91 + .../it_IT/process/maintainer-handbooks.rst | 24 + .../it_IT/process/maintainer-pgp-guide.rst | 949 +++ .../translations/it_IT/process/maintainer-tip.rst | 10 + .../translations/it_IT/process/maintainers.rst | 13 + .../it_IT/process/management-style.rst | 295 + .../it_IT/process/programming-language.rst | 53 + .../it_IT/process/stable-api-nonsense.rst | 209 + .../it_IT/process/stable-kernel-rules.rst | 216 + .../it_IT/process/submit-checklist.rst | 132 + .../it_IT/process/submitting-patches.rst | 817 ++ .../it_IT/process/volatile-considered-harmful.rst | 134 + .../translations/it_IT/riscv/patch-acceptance.rst | 40 + Documentation/translations/ja_JP/SubmitChecklist | 105 + Documentation/translations/ja_JP/SubmittingPatches | 721 ++ Documentation/translations/ja_JP/howto.rst | 650 ++ Documentation/translations/ja_JP/index.rst | 18 + .../translations/ja_JP/stable_api_nonsense.txt | 263 + .../translations/ja_JP/stable_kernel_rules.txt | 84 + Documentation/translations/ko_KR/howto.rst | 619 ++ Documentation/translations/ko_KR/index.rst | 29 + .../translations/ko_KR/memory-barriers.txt | 2931 +++++++ .../translations/ko_KR/stable_api_nonsense.txt | 195 + Documentation/translations/zh_CN/PCI/acpi-info.rst | 139 + Documentation/translations/zh_CN/PCI/index.rst | 34 + Documentation/translations/zh_CN/PCI/msi-howto.rst | 233 + .../translations/zh_CN/PCI/pci-iov-howto.rst | 169 + Documentation/translations/zh_CN/PCI/pci.rst | 514 ++ .../translations/zh_CN/PCI/pciebus-howto.rst | 192 + Documentation/translations/zh_CN/PCI/sysfs-pci.rst | 126 + .../zh_CN/accounting/delay-accounting.rst | 109 + .../translations/zh_CN/accounting/index.rst | 25 + .../translations/zh_CN/accounting/psi.rst | 155 + .../translations/zh_CN/accounting/taskstats.rst | 145 + .../translations/zh_CN/admin-guide/README.rst | 291 + .../translations/zh_CN/admin-guide/bootconfig.rst | 293 + .../translations/zh_CN/admin-guide/bug-bisect.rst | 81 + .../translations/zh_CN/admin-guide/bug-hunting.rst | 340 + .../zh_CN/admin-guide/clearing-warn-once.rst | 9 + .../translations/zh_CN/admin-guide/cpu-load.rst | 105 + .../translations/zh_CN/admin-guide/cputopology.rst | 96 + .../translations/zh_CN/admin-guide/index.rst | 133 + .../translations/zh_CN/admin-guide/init.rst | 54 + .../zh_CN/admin-guide/lockup-watchdogs.rst | 66 + .../zh_CN/admin-guide/mm/damon/index.rst | 28 + .../zh_CN/admin-guide/mm/damon/reclaim.rst | 232 + .../zh_CN/admin-guide/mm/damon/start.rst | 132 + .../zh_CN/admin-guide/mm/damon/usage.rst | 559 ++ .../translations/zh_CN/admin-guide/mm/index.rst | 49 + .../translations/zh_CN/admin-guide/mm/ksm.rst | 148 + .../zh_CN/admin-guide/reporting-issues.rst | 1368 ++++ .../zh_CN/admin-guide/reporting-regressions.rst | 370 + .../zh_CN/admin-guide/security-bugs.rst | 74 + .../translations/zh_CN/admin-guide/sysrq.rst | 280 + .../zh_CN/admin-guide/tainted-kernels.rst | 157 + .../translations/zh_CN/admin-guide/unicode.rst | 170 + Documentation/translations/zh_CN/arch.rst | 29 + Documentation/translations/zh_CN/arm/Booting | 175 + .../translations/zh_CN/arm/kernel_user_helpers.txt | 284 + Documentation/translations/zh_CN/arm64/amu.rst | 100 + Documentation/translations/zh_CN/arm64/booting.txt | 246 + .../translations/zh_CN/arm64/elf_hwcaps.rst | 240 + .../translations/zh_CN/arm64/hugetlbpage.rst | 45 + Documentation/translations/zh_CN/arm64/index.rst | 19 + .../zh_CN/arm64/legacy_instructions.txt | 72 + Documentation/translations/zh_CN/arm64/memory.txt | 114 + Documentation/translations/zh_CN/arm64/perf.rst | 86 + .../translations/zh_CN/arm64/silicon-errata.txt | 74 + .../translations/zh_CN/arm64/tagged-pointers.txt | 52 + .../translations/zh_CN/core-api/assoc_array.rst | 473 ++ .../translations/zh_CN/core-api/boot-time-mm.rst | 49 + .../translations/zh_CN/core-api/cachetlb.rst | 333 + .../zh_CN/core-api/circular-buffers.rst | 210 + .../translations/zh_CN/core-api/cpu_hotplug.rst | 667 ++ .../translations/zh_CN/core-api/genalloc.rst | 109 + .../zh_CN/core-api/generic-radix-tree.rst | 23 + .../translations/zh_CN/core-api/genericirq.rst | 409 + .../zh_CN/core-api/gfp_mask-from-fs-io.rst | 66 + Documentation/translations/zh_CN/core-api/idr.rst | 80 + .../translations/zh_CN/core-api/index.rst | 147 + .../translations/zh_CN/core-api/irq/concepts.rst | 26 + .../translations/zh_CN/core-api/irq/index.rst | 22 + .../zh_CN/core-api/irq/irq-affinity.rst | 78 + .../translations/zh_CN/core-api/irq/irq-domain.rst | 243 + .../zh_CN/core-api/irq/irqflags-tracing.rst | 47 + .../translations/zh_CN/core-api/kernel-api.rst | 372 + .../translations/zh_CN/core-api/kobject.rst | 379 + Documentation/translations/zh_CN/core-api/kref.rst | 311 + .../translations/zh_CN/core-api/local_ops.rst | 196 + .../zh_CN/core-api/memory-allocation.rst | 138 + .../translations/zh_CN/core-api/memory-hotplug.rst | 122 + .../translations/zh_CN/core-api/mm-api.rst | 131 + .../translations/zh_CN/core-api/packing.rst | 160 + .../translations/zh_CN/core-api/padata.rst | 161 + .../translations/zh_CN/core-api/printk-basics.rst | 111 + .../translations/zh_CN/core-api/printk-formats.rst | 598 ++ .../zh_CN/core-api/protection-keys.rst | 99 + .../translations/zh_CN/core-api/rbtree.rst | 391 + .../zh_CN/core-api/refcount-vs-atomic.rst | 156 + .../zh_CN/core-api/symbol-namespaces.rst | 144 + .../zh_CN/core-api/unaligned-memory-access.rst | 229 + .../translations/zh_CN/core-api/watch_queue.rst | 313 + .../translations/zh_CN/core-api/workqueue.rst | 352 + .../translations/zh_CN/core-api/xarray.rst | 373 + Documentation/translations/zh_CN/cpu-freq/core.rst | 109 + .../translations/zh_CN/cpu-freq/cpu-drivers.rst | 257 + .../translations/zh_CN/cpu-freq/cpufreq-stats.rst | 133 + .../translations/zh_CN/cpu-freq/index.rst | 47 + .../translations/zh_CN/dev-tools/gcov.rst | 264 + .../zh_CN/dev-tools/gdb-kernel-debugging.rst | 167 + .../translations/zh_CN/dev-tools/index.rst | 40 + .../translations/zh_CN/dev-tools/kasan.rst | 454 ++ .../translations/zh_CN/dev-tools/sparse.rst | 110 + .../zh_CN/dev-tools/testing-overview.rst | 134 + .../translations/zh_CN/devicetree/changesets.rst | 37 + .../zh_CN/devicetree/dynamic-resolution-notes.rst | 31 + .../translations/zh_CN/devicetree/index.rst | 45 + .../translations/zh_CN/devicetree/kernel-api.rst | 58 + .../translations/zh_CN/devicetree/of_unittest.rst | 189 + .../zh_CN/devicetree/overlay-notes.rst | 140 + .../translations/zh_CN/devicetree/usage-model.rst | 330 + .../translations/zh_CN/disclaimer-zh_CN.rst | 9 + .../translations/zh_CN/doc-guide/contributing.rst | 238 + .../translations/zh_CN/doc-guide/index.rst | 27 + .../translations/zh_CN/doc-guide/kernel-doc.rst | 499 ++ .../zh_CN/doc-guide/maintainer-profile.rst | 43 + .../translations/zh_CN/doc-guide/parse-headers.rst | 187 + .../translations/zh_CN/doc-guide/sphinx.rst | 412 + .../translations/zh_CN/driver-api/gpio/index.rst | 69 + .../translations/zh_CN/driver-api/gpio/legacy.rst | 694 ++ .../translations/zh_CN/driver-api/index.rst | 132 + .../translations/zh_CN/driver-api/io_ordering.rst | 60 + .../translations/zh_CN/filesystems/debugfs.rst | 221 + .../translations/zh_CN/filesystems/index.rst | 29 + .../translations/zh_CN/filesystems/sysfs.txt | 373 + .../translations/zh_CN/filesystems/tmpfs.rst | 146 + .../translations/zh_CN/filesystems/virtiofs.rst | 58 + .../translations/zh_CN/iio/ep93xx_adc.rst | 48 + .../translations/zh_CN/iio/iio_configfs.rst | 106 + Documentation/translations/zh_CN/iio/index.rst | 22 + Documentation/translations/zh_CN/index.rst | 142 + .../translations/zh_CN/infiniband/core_locking.rst | 115 + .../translations/zh_CN/infiniband/index.rst | 40 + .../translations/zh_CN/infiniband/ipoib.rst | 111 + .../translations/zh_CN/infiniband/opa_vnic.rst | 156 + .../translations/zh_CN/infiniband/sysfs.rst | 21 + .../translations/zh_CN/infiniband/tag_matching.rst | 63 + .../translations/zh_CN/infiniband/user_mad.rst | 164 + .../translations/zh_CN/infiniband/user_verbs.rst | 72 + .../translations/zh_CN/kernel-hacking/hacking.rst | 707 ++ .../translations/zh_CN/kernel-hacking/index.rst | 22 + Documentation/translations/zh_CN/locking/index.rst | 43 + .../translations/zh_CN/locking/mutex-design.rst | 145 + .../translations/zh_CN/locking/spinlocks.rst | 149 + .../translations/zh_CN/loongarch/booting.rst | 48 + .../translations/zh_CN/loongarch/features.rst | 8 + .../translations/zh_CN/loongarch/index.rst | 27 + .../translations/zh_CN/loongarch/introduction.rst | 353 + .../zh_CN/loongarch/irq-chip-model.rst | 157 + .../zh_CN/maintainer/configure-git.rst | 62 + .../translations/zh_CN/maintainer/index.rst | 21 + .../zh_CN/maintainer/maintainer-entry-profile.rst | 92 + .../zh_CN/maintainer/modifying-patches.rst | 51 + .../zh_CN/maintainer/pull-requests.rst | 148 + .../zh_CN/maintainer/rebasing-and-merging.rst | 165 + Documentation/translations/zh_CN/mips/booting.rst | 34 + Documentation/translations/zh_CN/mips/features.rst | 13 + Documentation/translations/zh_CN/mips/index.rst | 29 + .../translations/zh_CN/mips/ingenic-tcu.rst | 72 + Documentation/translations/zh_CN/mm/active_mm.rst | 85 + Documentation/translations/zh_CN/mm/balance.rst | 81 + Documentation/translations/zh_CN/mm/damon/api.rst | 32 + .../translations/zh_CN/mm/damon/design.rst | 140 + Documentation/translations/zh_CN/mm/damon/faq.rst | 48 + .../translations/zh_CN/mm/damon/index.rst | 32 + .../translations/zh_CN/mm/free_page_reporting.rst | 38 + Documentation/translations/zh_CN/mm/frontswap.rst | 196 + Documentation/translations/zh_CN/mm/highmem.rst | 137 + Documentation/translations/zh_CN/mm/hmm.rst | 361 + .../translations/zh_CN/mm/hugetlbfs_reserv.rst | 436 ++ Documentation/translations/zh_CN/mm/hwpoison.rst | 166 + Documentation/translations/zh_CN/mm/index.rst | 69 + Documentation/translations/zh_CN/mm/ksm.rst | 70 + .../translations/zh_CN/mm/memory-model.rst | 135 + .../translations/zh_CN/mm/mmu_notifier.rst | 97 + Documentation/translations/zh_CN/mm/numa.rst | 101 + .../zh_CN/mm/overcommit-accounting.rst | 86 + Documentation/translations/zh_CN/mm/page_frags.rst | 38 + .../translations/zh_CN/mm/page_migration.rst | 228 + Documentation/translations/zh_CN/mm/page_owner.rst | 181 + .../translations/zh_CN/mm/page_table_check.rst | 56 + .../translations/zh_CN/mm/remap_file_pages.rst | 32 + .../zh_CN/mm/split_page_table_lock.rst | 96 + .../zh_CN/mm/vmalloced-kernel-stacks.rst | 133 + Documentation/translations/zh_CN/mm/z3fold.rst | 31 + Documentation/translations/zh_CN/mm/zsmalloc.rst | 78 + .../translations/zh_CN/openrisc/index.rst | 32 + .../translations/zh_CN/openrisc/openrisc_port.rst | 127 + Documentation/translations/zh_CN/openrisc/todo.rst | 23 + .../translations/zh_CN/parisc/debugging.rst | 45 + Documentation/translations/zh_CN/parisc/index.rst | 31 + .../translations/zh_CN/parisc/registers.rst | 156 + Documentation/translations/zh_CN/peci/index.rst | 26 + Documentation/translations/zh_CN/peci/peci.rst | 54 + .../translations/zh_CN/power/energy-model.rst | 190 + Documentation/translations/zh_CN/power/index.rst | 56 + Documentation/translations/zh_CN/power/opp.rst | 341 + .../translations/zh_CN/process/1.Intro.rst | 195 + .../translations/zh_CN/process/2.Process.rst | 365 + .../translations/zh_CN/process/3.Early-stage.rst | 168 + .../translations/zh_CN/process/4.Coding.rst | 293 + .../translations/zh_CN/process/5.Posting.rst | 246 + .../translations/zh_CN/process/6.Followthrough.rst | 152 + .../zh_CN/process/7.AdvancedTopics.rst | 133 + .../translations/zh_CN/process/8.Conclusion.rst | 69 + .../process/code-of-conduct-interpretation.rst | 108 + .../translations/zh_CN/process/code-of-conduct.rst | 72 + .../translations/zh_CN/process/coding-style.rst | 1083 +++ .../zh_CN/process/development-process.rst | 26 + .../translations/zh_CN/process/email-clients.rst | 327 + .../zh_CN/process/embargoed-hardware-issues.rst | 228 + Documentation/translations/zh_CN/process/howto.rst | 495 ++ Documentation/translations/zh_CN/process/index.rst | 63 + .../zh_CN/process/kernel-driver-statement.rst | 199 + .../zh_CN/process/kernel-enforcement-statement.rst | 151 + .../translations/zh_CN/process/license-rules.rst | 370 + .../translations/zh_CN/process/magic-number.rst | 74 + .../zh_CN/process/management-style.rst | 207 + .../zh_CN/process/programming-language.rst | 71 + .../zh_CN/process/stable-api-nonsense.rst | 155 + .../zh_CN/process/stable-kernel-rules.rst | 64 + .../zh_CN/process/submit-checklist.rst | 111 + .../zh_CN/process/submitting-patches.rst | 657 ++ .../zh_CN/process/volatile-considered-harmful.rst | 106 + .../translations/zh_CN/riscv/boot-image-header.rst | 69 + Documentation/translations/zh_CN/riscv/index.rst | 30 + .../translations/zh_CN/riscv/patch-acceptance.rst | 33 + .../translations/zh_CN/riscv/vm-layout.rst | 104 + .../translations/zh_CN/scheduler/completion.rst | 256 + .../translations/zh_CN/scheduler/index.rst | 45 + .../translations/zh_CN/scheduler/sched-arch.rst | 76 + .../translations/zh_CN/scheduler/sched-bwc.rst | 204 + .../zh_CN/scheduler/sched-capacity.rst | 390 + .../translations/zh_CN/scheduler/sched-debug.rst | 51 + .../zh_CN/scheduler/sched-design-CFS.rst | 205 + .../translations/zh_CN/scheduler/sched-domains.rst | 72 + .../translations/zh_CN/scheduler/sched-energy.rst | 351 + .../zh_CN/scheduler/sched-nice-design.rst | 99 + .../translations/zh_CN/scheduler/sched-stats.rst | 156 + .../translations/zh_CN/scheduler/schedutil.rst | 165 + .../translations/zh_CN/sound/hd-audio/controls.rst | 102 + .../translations/zh_CN/sound/hd-audio/index.rst | 14 + Documentation/translations/zh_CN/sound/index.rst | 22 + .../translations/zh_CN/video4linux/omap3isp.txt | 277 + .../zh_CN/video4linux/v4l2-framework.txt | 976 +++ .../translations/zh_CN/virt/acrn/cpuid.rst | 56 + .../translations/zh_CN/virt/acrn/index.rst | 25 + .../translations/zh_CN/virt/acrn/introduction.rst | 52 + .../translations/zh_CN/virt/acrn/io-request.rst | 99 + .../translations/zh_CN/virt/guest-halt-polling.rst | 87 + Documentation/translations/zh_CN/virt/index.rst | 38 + .../translations/zh_CN/virt/ne_overview.rst | 88 + .../translations/zh_CN/virt/paravirt_ops.rst | 41 + Documentation/translations/zh_TW/IRQ.txt | 41 + .../translations/zh_TW/admin-guide/README.rst | 351 + .../translations/zh_TW/admin-guide/bug-bisect.rst | 85 + .../translations/zh_TW/admin-guide/bug-hunting.rst | 344 + .../zh_TW/admin-guide/clearing-warn-once.rst | 16 + .../translations/zh_TW/admin-guide/cpu-load.rst | 112 + .../translations/zh_TW/admin-guide/index.rst | 135 + .../translations/zh_TW/admin-guide/init.rst | 58 + .../zh_TW/admin-guide/reporting-issues.rst | 1337 ++++ .../zh_TW/admin-guide/security-bugs.rst | 78 + .../zh_TW/admin-guide/tainted-kernels.rst | 161 + .../translations/zh_TW/admin-guide/unicode.rst | 174 + Documentation/translations/zh_TW/arm64/amu.rst | 104 + Documentation/translations/zh_TW/arm64/booting.txt | 251 + .../translations/zh_TW/arm64/elf_hwcaps.rst | 244 + .../translations/zh_TW/arm64/hugetlbpage.rst | 49 + Documentation/translations/zh_TW/arm64/index.rst | 23 + .../zh_TW/arm64/legacy_instructions.txt | 77 + Documentation/translations/zh_TW/arm64/memory.txt | 119 + Documentation/translations/zh_TW/arm64/perf.rst | 88 + .../translations/zh_TW/arm64/silicon-errata.txt | 79 + .../translations/zh_TW/arm64/tagged-pointers.txt | 57 + Documentation/translations/zh_TW/cpu-freq/core.rst | 108 + .../translations/zh_TW/cpu-freq/cpu-drivers.rst | 256 + .../translations/zh_TW/cpu-freq/cpufreq-stats.rst | 132 + .../translations/zh_TW/cpu-freq/index.rst | 47 + .../translations/zh_TW/disclaimer-zh_TW.rst | 11 + .../translations/zh_TW/filesystems/debugfs.rst | 224 + .../translations/zh_TW/filesystems/index.rst | 31 + .../translations/zh_TW/filesystems/sysfs.txt | 377 + .../translations/zh_TW/filesystems/tmpfs.rst | 148 + .../translations/zh_TW/filesystems/virtiofs.rst | 61 + Documentation/translations/zh_TW/gpio.txt | 651 ++ Documentation/translations/zh_TW/index.rst | 177 + Documentation/translations/zh_TW/io_ordering.txt | 68 + .../translations/zh_TW/process/1.Intro.rst | 199 + .../translations/zh_TW/process/2.Process.rst | 369 + .../translations/zh_TW/process/3.Early-stage.rst | 172 + .../translations/zh_TW/process/4.Coding.rst | 297 + .../translations/zh_TW/process/5.Posting.rst | 250 + .../translations/zh_TW/process/6.Followthrough.rst | 156 + .../zh_TW/process/7.AdvancedTopics.rst | 137 + .../translations/zh_TW/process/8.Conclusion.rst | 73 + .../process/code-of-conduct-interpretation.rst | 112 + .../translations/zh_TW/process/code-of-conduct.rst | 76 + .../translations/zh_TW/process/coding-style.rst | 958 +++ .../zh_TW/process/development-process.rst | 30 + .../translations/zh_TW/process/email-clients.rst | 252 + .../zh_TW/process/embargoed-hardware-issues.rst | 232 + Documentation/translations/zh_TW/process/howto.rst | 499 ++ Documentation/translations/zh_TW/process/index.rst | 66 + .../zh_TW/process/kernel-driver-statement.rst | 203 + .../zh_TW/process/kernel-enforcement-statement.rst | 155 + .../translations/zh_TW/process/license-rules.rst | 374 + .../translations/zh_TW/process/magic-number.rst | 77 + .../zh_TW/process/management-style.rst | 211 + .../zh_TW/process/programming-language.rst | 75 + .../zh_TW/process/stable-api-nonsense.rst | 159 + .../zh_TW/process/stable-kernel-rules.rst | 68 + .../zh_TW/process/submit-checklist.rst | 109 + .../zh_TW/process/submitting-patches.rst | 660 ++ .../zh_TW/process/volatile-considered-harmful.rst | 110 + Documentation/translations/zh_TW/sparse.txt | 91 + Documentation/usb/CREDITS | 175 + Documentation/usb/acm.rst | 132 + Documentation/usb/authorization.rst | 132 + Documentation/usb/chipidea.rst | 133 + Documentation/usb/dwc3.rst | 53 + Documentation/usb/ehci.rst | 230 + Documentation/usb/functionfs.rst | 68 + Documentation/usb/gadget-testing.rst | 967 +++ Documentation/usb/gadget_configfs.rst | 390 + Documentation/usb/gadget_hid.rst | 457 ++ Documentation/usb/gadget_multi.rst | 165 + Documentation/usb/gadget_printer.rst | 523 ++ Documentation/usb/gadget_serial.rst | 289 + Documentation/usb/index.rst | 38 + Documentation/usb/iuu_phoenix.rst | 94 + Documentation/usb/linux-cdc-acm.inf | 107 + Documentation/usb/linux.inf | 66 + Documentation/usb/mass-storage.rst | 243 + Documentation/usb/misc_usbsevseg.rst | 51 + Documentation/usb/mtouchusb.rst | 84 + Documentation/usb/ohci.rst | 35 + Documentation/usb/raw-gadget.rst | 94 + Documentation/usb/text_files.rst | 23 + Documentation/usb/usb-help.rst | 17 + Documentation/usb/usb-serial.rst | 537 ++ Documentation/usb/usbdevfs-drop-permissions.c | 120 + Documentation/usb/usbip_protocol.rst | 452 ++ Documentation/usb/usbmon.rst | 375 + Documentation/userspace-api/accelerators/ocxl.rst | 176 + Documentation/userspace-api/ebpf/index.rst | 17 + Documentation/userspace-api/ebpf/syscall.rst | 24 + Documentation/userspace-api/futex2.rst | 86 + Documentation/userspace-api/index.rst | 39 + Documentation/userspace-api/ioctl/cdrom.rst | 1242 +++ Documentation/userspace-api/ioctl/hdio.rst | 547 ++ Documentation/userspace-api/ioctl/index.rst | 15 + .../userspace-api/ioctl/ioctl-decoding.rst | 31 + Documentation/userspace-api/ioctl/ioctl-number.rst | 381 + Documentation/userspace-api/iommu.rst | 209 + Documentation/userspace-api/landlock.rst | 447 ++ Documentation/userspace-api/media/Makefile | 63 + .../userspace-api/media/ca.h.rst.exceptions | 25 + .../userspace-api/media/cec.h.rst.exceptions | 577 ++ Documentation/userspace-api/media/cec/cec-api.rst | 46 + .../userspace-api/media/cec/cec-func-close.rst | 43 + .../userspace-api/media/cec/cec-func-ioctl.rst | 63 + .../userspace-api/media/cec/cec-func-open.rst | 74 + .../userspace-api/media/cec/cec-func-poll.rst | 74 + .../userspace-api/media/cec/cec-funcs.rst | 23 + .../userspace-api/media/cec/cec-header.rst | 10 + .../userspace-api/media/cec/cec-intro.rst | 42 + .../media/cec/cec-ioc-adap-g-caps.rst | 146 + .../media/cec/cec-ioc-adap-g-conn-info.rst | 106 + .../media/cec/cec-ioc-adap-g-log-addrs.rst | 367 + .../media/cec/cec-ioc-adap-g-phys-addr.rst | 94 + .../userspace-api/media/cec/cec-ioc-dqevent.rst | 245 + .../userspace-api/media/cec/cec-ioc-g-mode.rst | 294 + .../userspace-api/media/cec/cec-ioc-receive.rst | 385 + .../userspace-api/media/cec/cec-pin-error-inj.rst | 327 + Documentation/userspace-api/media/conf_nitpick.py | 111 + .../userspace-api/media/dmx.h.rst.exceptions | 66 + Documentation/userspace-api/media/drivers/ccs.rst | 110 + .../userspace-api/media/drivers/cx2341x-uapi.rst | 177 + .../userspace-api/media/drivers/dw100.rst | 84 + .../userspace-api/media/drivers/imx-uapi.rst | 125 + .../userspace-api/media/drivers/index.rst | 41 + .../userspace-api/media/drivers/max2175.rst | 64 + .../userspace-api/media/drivers/meye-uapi.rst | 53 + .../userspace-api/media/drivers/omap3isp-uapi.rst | 208 + .../userspace-api/media/drivers/uvcvideo.rst | 257 + .../userspace-api/media/dvb/ca-fclose.rst | 40 + Documentation/userspace-api/media/dvb/ca-fopen.rst | 72 + .../userspace-api/media/dvb/ca-get-cap.rst | 46 + .../userspace-api/media/dvb/ca-get-descr-info.rst | 43 + .../userspace-api/media/dvb/ca-get-msg.rst | 50 + .../userspace-api/media/dvb/ca-get-slot-info.rst | 56 + Documentation/userspace-api/media/dvb/ca-reset.rst | 43 + .../userspace-api/media/dvb/ca-send-msg.rst | 50 + .../userspace-api/media/dvb/ca-set-descr.rst | 46 + Documentation/userspace-api/media/dvb/ca.rst | 25 + .../userspace-api/media/dvb/ca_data_types.rst | 9 + .../userspace-api/media/dvb/ca_function_calls.rst | 20 + .../userspace-api/media/dvb/ca_high_level.rst | 157 + Documentation/userspace-api/media/dvb/demux.rst | 23 + .../userspace-api/media/dvb/dmx-add-pid.rst | 47 + .../userspace-api/media/dvb/dmx-expbuf.rst | 87 + .../userspace-api/media/dvb/dmx-fclose.rst | 42 + .../userspace-api/media/dvb/dmx-fopen.rst | 88 + .../userspace-api/media/dvb/dmx-fread.rst | 77 + .../userspace-api/media/dvb/dmx-fwrite.rst | 70 + .../userspace-api/media/dvb/dmx-get-pes-pids.rst | 62 + .../userspace-api/media/dvb/dmx-get-stc.rst | 64 + Documentation/userspace-api/media/dvb/dmx-mmap.rst | 115 + .../userspace-api/media/dvb/dmx-munmap.rst | 52 + Documentation/userspace-api/media/dvb/dmx-qbuf.rst | 85 + .../userspace-api/media/dvb/dmx-querybuf.rst | 64 + .../userspace-api/media/dvb/dmx-remove-pid.rst | 48 + .../userspace-api/media/dvb/dmx-reqbufs.rst | 75 + .../media/dvb/dmx-set-buffer-size.rst | 48 + .../userspace-api/media/dvb/dmx-set-filter.rst | 55 + .../userspace-api/media/dvb/dmx-set-pes-filter.rst | 64 + .../userspace-api/media/dvb/dmx-start.rst | 65 + Documentation/userspace-api/media/dvb/dmx-stop.rst | 44 + .../userspace-api/media/dvb/dmx_fcalls.rst | 30 + .../userspace-api/media/dvb/dmx_types.rst | 9 + .../userspace-api/media/dvb/dvb-fe-read-status.rst | 25 + .../userspace-api/media/dvb/dvb-frontend-event.rst | 15 + .../media/dvb/dvb-frontend-parameters.rst | 119 + Documentation/userspace-api/media/dvb/dvbapi.rst | 118 + .../userspace-api/media/dvb/dvbproperty.rst | 126 + Documentation/userspace-api/media/dvb/dvbstb.svg | 17 + Documentation/userspace-api/media/dvb/examples.rst | 16 + .../userspace-api/media/dvb/fe-bandwidth-t.rst | 74 + .../media/dvb/fe-diseqc-recv-slave-reply.rst | 47 + .../media/dvb/fe-diseqc-reset-overload.rst | 45 + .../media/dvb/fe-diseqc-send-burst.rst | 50 + .../media/dvb/fe-diseqc-send-master-cmd.rst | 48 + .../media/dvb/fe-dishnetwork-send-legacy-cmd.rst | 53 + .../media/dvb/fe-enable-high-lnb-voltage.rst | 52 + .../userspace-api/media/dvb/fe-get-event.rst | 67 + .../userspace-api/media/dvb/fe-get-frontend.rst | 58 + .../userspace-api/media/dvb/fe-get-info.rst | 59 + .../userspace-api/media/dvb/fe-get-property.rst | 75 + .../userspace-api/media/dvb/fe-read-ber.rst | 49 + .../media/dvb/fe-read-signal-strength.rst | 49 + .../userspace-api/media/dvb/fe-read-snr.rst | 49 + .../userspace-api/media/dvb/fe-read-status.rst | 62 + .../media/dvb/fe-read-uncorrected-blocks.rst | 51 + .../media/dvb/fe-set-frontend-tune-mode.rst | 55 + .../userspace-api/media/dvb/fe-set-frontend.rst | 68 + .../userspace-api/media/dvb/fe-set-tone.rst | 56 + .../userspace-api/media/dvb/fe-set-voltage.rst | 60 + .../userspace-api/media/dvb/fe-type-t.rst | 91 + .../media/dvb/fe_property_parameters.rst | 1007 +++ .../userspace-api/media/dvb/frontend-header.rst | 6 + .../media/dvb/frontend-property-cable-systems.rst | 75 + .../dvb/frontend-property-satellite-systems.rst | 105 + .../dvb/frontend-property-terrestrial-systems.rst | 294 + .../media/dvb/frontend-stat-properties.rst | 245 + Documentation/userspace-api/media/dvb/frontend.rst | 56 + .../userspace-api/media/dvb/frontend_f_close.rst | 46 + .../userspace-api/media/dvb/frontend_f_open.rst | 104 + .../userspace-api/media/dvb/frontend_fcalls.rst | 24 + .../media/dvb/frontend_legacy_api.rst | 38 + .../media/dvb/frontend_legacy_dvbv3_api.rst | 18 + Documentation/userspace-api/media/dvb/headers.rst | 16 + Documentation/userspace-api/media/dvb/intro.rst | 183 + .../userspace-api/media/dvb/legacy_dvb_apis.rst | 25 + .../userspace-api/media/dvb/net-add-if.rst | 52 + .../userspace-api/media/dvb/net-get-if.rst | 50 + .../userspace-api/media/dvb/net-remove-if.rst | 46 + .../userspace-api/media/dvb/net-types.rst | 9 + Documentation/userspace-api/media/dvb/net.rst | 41 + .../media/dvb/query-dvb-frontend-info.rst | 13 + Documentation/userspace-api/media/fdl-appendix.rst | 471 ++ .../userspace-api/media/frontend.h.rst.exceptions | 214 + Documentation/userspace-api/media/gen-errors.rst | 96 + Documentation/userspace-api/media/glossary.rst | 205 + Documentation/userspace-api/media/index.rst | 72 + Documentation/userspace-api/media/intro.rst | 46 + .../userspace-api/media/lirc.h.rst.exceptions | 87 + .../userspace-api/media/media.h.rst.exceptions | 32 + .../media/mediactl/media-controller-intro.rst | 33 + .../media/mediactl/media-controller-model.rst | 41 + .../media/mediactl/media-controller.rst | 54 + .../media/mediactl/media-func-close.rst | 43 + .../media/mediactl/media-func-ioctl.rst | 63 + .../media/mediactl/media-func-open.rst | 65 + .../userspace-api/media/mediactl/media-funcs.rst | 26 + .../userspace-api/media/mediactl/media-header.rst | 10 + .../media/mediactl/media-ioc-device-info.rst | 106 + .../media/mediactl/media-ioc-enum-entities.rst | 146 + .../media/mediactl/media-ioc-enum-links.rst | 145 + .../media/mediactl/media-ioc-g-topology.rst | 294 + .../media/mediactl/media-ioc-request-alloc.rst | 65 + .../media/mediactl/media-ioc-setup-link.rst | 65 + .../media/mediactl/media-request-ioc-queue.rst | 77 + .../media/mediactl/media-request-ioc-reinit.rst | 51 + .../userspace-api/media/mediactl/media-types.rst | 432 + .../userspace-api/media/mediactl/request-api.rst | 253 + .../media/mediactl/request-func-close.rst | 45 + .../media/mediactl/request-func-ioctl.rst | 63 + .../media/mediactl/request-func-poll.rst | 73 + .../userspace-api/media/net.h.rst.exceptions | 13 + .../userspace-api/media/rc/keytable.c.rst | 176 + .../userspace-api/media/rc/lirc-dev-intro.rst | 176 + Documentation/userspace-api/media/rc/lirc-dev.rst | 14 + Documentation/userspace-api/media/rc/lirc-func.rst | 26 + .../userspace-api/media/rc/lirc-get-features.rst | 174 + .../userspace-api/media/rc/lirc-get-rec-mode.rst | 69 + .../media/rc/lirc-get-rec-resolution.rst | 47 + .../userspace-api/media/rc/lirc-get-send-mode.rst | 71 + .../userspace-api/media/rc/lirc-get-timeout.rst | 57 + .../userspace-api/media/rc/lirc-header.rst | 10 + Documentation/userspace-api/media/rc/lirc-read.rst | 65 + .../media/rc/lirc-set-measure-carrier-mode.rst | 46 + .../media/rc/lirc-set-rec-carrier-range.rst | 49 + .../media/rc/lirc-set-rec-carrier.rst | 46 + .../media/rc/lirc-set-rec-timeout.rst | 55 + .../media/rc/lirc-set-send-carrier.rst | 41 + .../media/rc/lirc-set-send-duty-cycle.rst | 47 + .../media/rc/lirc-set-transmitter-mask.rst | 51 + .../media/rc/lirc-set-wideband-receiver.rst | 56 + .../userspace-api/media/rc/lirc-write.rst | 72 + Documentation/userspace-api/media/rc/rc-intro.rst | 24 + Documentation/userspace-api/media/rc/rc-protos.rst | 454 ++ .../userspace-api/media/rc/rc-sysfs-nodes.rst | 144 + .../userspace-api/media/rc/rc-table-change.rst | 18 + Documentation/userspace-api/media/rc/rc-tables.rst | 759 ++ .../userspace-api/media/rc/remote_controllers.rst | 51 + .../userspace-api/media/typical_media_device.svg | 107 + Documentation/userspace-api/media/v4l/app-pri.rst | 30 + Documentation/userspace-api/media/v4l/audio.rst | 97 + Documentation/userspace-api/media/v4l/bayer.svg | 30 + Documentation/userspace-api/media/v4l/biblio.rst | 429 + Documentation/userspace-api/media/v4l/buffer.rst | 841 ++ .../userspace-api/media/v4l/capture-example.rst | 13 + .../userspace-api/media/v4l/capture.c.rst | 664 ++ .../userspace-api/media/v4l/colorspaces-defs.rst | 175 + .../media/v4l/colorspaces-details.rst | 775 ++ .../userspace-api/media/v4l/colorspaces.rst | 163 + .../userspace-api/media/v4l/common-defs.rst | 13 + Documentation/userspace-api/media/v4l/common.rst | 60 + Documentation/userspace-api/media/v4l/compat.rst | 18 + .../userspace-api/media/v4l/constraints.svg | 11 + Documentation/userspace-api/media/v4l/control.rst | 517 ++ Documentation/userspace-api/media/v4l/crop.rst | 317 + Documentation/userspace-api/media/v4l/crop.svg | 281 + .../userspace-api/media/v4l/depth-formats.rst | 17 + .../userspace-api/media/v4l/dev-capture.rst | 101 + .../userspace-api/media/v4l/dev-decoder.rst | 1127 +++ .../userspace-api/media/v4l/dev-encoder.rst | 729 ++ .../userspace-api/media/v4l/dev-event.rst | 47 + .../userspace-api/media/v4l/dev-mem2mem.rst | 43 + Documentation/userspace-api/media/v4l/dev-meta.rst | 67 + Documentation/userspace-api/media/v4l/dev-osd.rst | 150 + .../userspace-api/media/v4l/dev-output.rst | 98 + .../userspace-api/media/v4l/dev-overlay.rst | 320 + .../userspace-api/media/v4l/dev-radio.rst | 52 + .../userspace-api/media/v4l/dev-raw-vbi.rst | 292 + Documentation/userspace-api/media/v4l/dev-rds.rst | 176 + Documentation/userspace-api/media/v4l/dev-sdr.rst | 107 + .../userspace-api/media/v4l/dev-sliced-vbi.rst | 661 ++ .../media/v4l/dev-stateless-decoder.rst | 424 + .../userspace-api/media/v4l/dev-subdev.rst | 503 ++ .../userspace-api/media/v4l/dev-touch.rst | 56 + Documentation/userspace-api/media/v4l/devices.rst | 26 + Documentation/userspace-api/media/v4l/diff-v4l.rst | 667 ++ Documentation/userspace-api/media/v4l/dmabuf.rst | 162 + .../userspace-api/media/v4l/dv-timings.rst | 38 + .../userspace-api/media/v4l/ext-ctrls-camera.rst | 663 ++ .../media/v4l/ext-ctrls-codec-stateless.rst | 2959 +++++++ .../userspace-api/media/v4l/ext-ctrls-codec.rst | 2660 +++++++ .../media/v4l/ext-ctrls-colorimetry.rst | 93 + .../userspace-api/media/v4l/ext-ctrls-detect.rst | 64 + .../userspace-api/media/v4l/ext-ctrls-dv.rst | 159 + .../userspace-api/media/v4l/ext-ctrls-flash.rst | 188 + .../userspace-api/media/v4l/ext-ctrls-fm-rx.rst | 88 + .../userspace-api/media/v4l/ext-ctrls-fm-tx.rst | 181 + .../media/v4l/ext-ctrls-image-process.rst | 57 + .../media/v4l/ext-ctrls-image-source.rst | 94 + .../userspace-api/media/v4l/ext-ctrls-jpeg.rst | 105 + .../userspace-api/media/v4l/ext-ctrls-rf-tuner.rst | 89 + .../userspace-api/media/v4l/extended-controls.rst | 173 + .../userspace-api/media/v4l/field-order.rst | 165 + .../userspace-api/media/v4l/fieldseq_bt.svg | 2612 ++++++ .../userspace-api/media/v4l/fieldseq_tb.svg | 2609 ++++++ Documentation/userspace-api/media/v4l/format.rst | 91 + Documentation/userspace-api/media/v4l/fourcc.rst | 32 + .../userspace-api/media/v4l/func-close.rst | 45 + .../userspace-api/media/v4l/func-ioctl.rst | 58 + .../userspace-api/media/v4l/func-mmap.rst | 137 + .../userspace-api/media/v4l/func-munmap.rst | 54 + .../userspace-api/media/v4l/func-open.rst | 79 + .../userspace-api/media/v4l/func-poll.rst | 113 + .../userspace-api/media/v4l/func-read.rst | 130 + .../userspace-api/media/v4l/func-select.rst | 116 + .../userspace-api/media/v4l/func-write.rst | 81 + .../userspace-api/media/v4l/hist-v4l2.rst | 1276 +++ .../userspace-api/media/v4l/hsv-formats.rst | 19 + Documentation/userspace-api/media/v4l/io.rst | 49 + .../media/v4l/libv4l-introduction.rst | 180 + Documentation/userspace-api/media/v4l/libv4l.rst | 13 + .../userspace-api/media/v4l/meta-formats.rst | 21 + Documentation/userspace-api/media/v4l/mmap.rst | 285 + Documentation/userspace-api/media/v4l/nv12mt.svg | 451 ++ .../userspace-api/media/v4l/nv12mt_example.svg | 1590 ++++ Documentation/userspace-api/media/v4l/open.rst | 238 + Documentation/userspace-api/media/v4l/pipeline.dot | 14 + .../userspace-api/media/v4l/pixfmt-bayer.rst | 32 + .../userspace-api/media/v4l/pixfmt-cnf4.rst | 31 + .../userspace-api/media/v4l/pixfmt-compressed.rst | 238 + .../userspace-api/media/v4l/pixfmt-indexed.rst | 47 + .../userspace-api/media/v4l/pixfmt-intro.rst | 51 + .../userspace-api/media/v4l/pixfmt-inzi.rst | 82 + .../userspace-api/media/v4l/pixfmt-m420.rst | 71 + .../userspace-api/media/v4l/pixfmt-meta-d4xx.rst | 213 + .../media/v4l/pixfmt-meta-intel-ipu3.rst | 81 + .../userspace-api/media/v4l/pixfmt-meta-rkisp1.rst | 50 + .../userspace-api/media/v4l/pixfmt-meta-uvc.rst | 51 + .../userspace-api/media/v4l/pixfmt-meta-vivid.rst | 36 + .../media/v4l/pixfmt-meta-vsp1-hgo.rst | 168 + .../media/v4l/pixfmt-meta-vsp1-hgt.rst | 129 + .../userspace-api/media/v4l/pixfmt-packed-hsv.rst | 157 + .../userspace-api/media/v4l/pixfmt-packed-yuv.rst | 409 + .../userspace-api/media/v4l/pixfmt-reserved.rst | 263 + .../userspace-api/media/v4l/pixfmt-rgb.rst | 991 +++ .../userspace-api/media/v4l/pixfmt-sdr-cs08.rst | 30 + .../userspace-api/media/v4l/pixfmt-sdr-cs14le.rst | 34 + .../userspace-api/media/v4l/pixfmt-sdr-cu08.rst | 30 + .../userspace-api/media/v4l/pixfmt-sdr-cu16le.rst | 34 + .../userspace-api/media/v4l/pixfmt-sdr-pcu16be.rst | 55 + .../userspace-api/media/v4l/pixfmt-sdr-pcu18be.rst | 55 + .../userspace-api/media/v4l/pixfmt-sdr-pcu20be.rst | 55 + .../userspace-api/media/v4l/pixfmt-sdr-ru12le.rst | 32 + .../media/v4l/pixfmt-srggb10-ipu3.rst | 345 + .../userspace-api/media/v4l/pixfmt-srggb10.rst | 76 + .../media/v4l/pixfmt-srggb10alaw8.rst | 24 + .../media/v4l/pixfmt-srggb10dpcm8.rst | 28 + .../userspace-api/media/v4l/pixfmt-srggb10p.rst | 74 + .../userspace-api/media/v4l/pixfmt-srggb12.rst | 77 + .../userspace-api/media/v4l/pixfmt-srggb12p.rst | 87 + .../userspace-api/media/v4l/pixfmt-srggb14.rst | 77 + .../userspace-api/media/v4l/pixfmt-srggb14p.rst | 147 + .../userspace-api/media/v4l/pixfmt-srggb16.rst | 71 + .../userspace-api/media/v4l/pixfmt-srggb8.rst | 55 + .../userspace-api/media/v4l/pixfmt-tch-td08.rst | 52 + .../userspace-api/media/v4l/pixfmt-tch-td16.rst | 67 + .../userspace-api/media/v4l/pixfmt-tch-tu08.rst | 50 + .../userspace-api/media/v4l/pixfmt-tch-tu16.rst | 66 + .../userspace-api/media/v4l/pixfmt-uv8.rst | 47 + .../userspace-api/media/v4l/pixfmt-v4l2-mplane.rst | 123 + .../userspace-api/media/v4l/pixfmt-v4l2.rst | 240 + .../userspace-api/media/v4l/pixfmt-y12i.rst | 36 + .../userspace-api/media/v4l/pixfmt-y8i.rst | 66 + .../userspace-api/media/v4l/pixfmt-yuv-luma.rst | 148 + .../userspace-api/media/v4l/pixfmt-yuv-planar.rst | 1078 +++ .../userspace-api/media/v4l/pixfmt-z16.rst | 66 + Documentation/userspace-api/media/v4l/pixfmt.rst | 38 + .../userspace-api/media/v4l/planar-apis.rst | 61 + Documentation/userspace-api/media/v4l/querycap.rst | 34 + Documentation/userspace-api/media/v4l/rw.rst | 47 + .../userspace-api/media/v4l/sdr-formats.rst | 22 + .../media/v4l/selection-api-configuration.rst | 137 + .../media/v4l/selection-api-examples.rst | 84 + .../media/v4l/selection-api-intro.rst | 28 + .../media/v4l/selection-api-targets.rst | 20 + .../media/v4l/selection-api-vs-crop-api.rst | 39 + .../userspace-api/media/v4l/selection-api.rst | 16 + .../userspace-api/media/v4l/selection.svg | 1152 +++ .../userspace-api/media/v4l/selections-common.rst | 23 + Documentation/userspace-api/media/v4l/standard.rst | 185 + .../userspace-api/media/v4l/streaming-par.rst | 34 + .../userspace-api/media/v4l/subdev-formats.rst | 8088 +++++++++++++++++++ .../media/v4l/subdev-image-processing-crop.svg | 303 + .../media/v4l/subdev-image-processing-full.svg | 743 ++ ...ubdev-image-processing-scaling-multi-source.svg | 541 ++ .../userspace-api/media/v4l/tch-formats.rst | 18 + Documentation/userspace-api/media/v4l/tuner.rst | 85 + .../userspace-api/media/v4l/user-func.rst | 82 + Documentation/userspace-api/media/v4l/userp.rst | 122 + .../media/v4l/v4l2-selection-flags.rst | 54 + .../media/v4l/v4l2-selection-targets.rst | 81 + Documentation/userspace-api/media/v4l/v4l2.rst | 418 + .../userspace-api/media/v4l/v4l2grab-example.rst | 17 + .../userspace-api/media/v4l/v4l2grab.c.rst | 169 + Documentation/userspace-api/media/v4l/vbi_525.svg | 812 ++ Documentation/userspace-api/media/v4l/vbi_625.svg | 861 ++ .../userspace-api/media/v4l/vbi_hsync.svg | 312 + Documentation/userspace-api/media/v4l/video.rst | 68 + Documentation/userspace-api/media/v4l/videodev.rst | 9 + .../userspace-api/media/v4l/vidioc-create-bufs.rst | 137 + .../userspace-api/media/v4l/vidioc-cropcap.rst | 133 + .../media/v4l/vidioc-dbg-g-chip-info.rst | 155 + .../media/v4l/vidioc-dbg-g-register.rst | 160 + .../userspace-api/media/v4l/vidioc-decoder-cmd.rst | 218 + .../userspace-api/media/v4l/vidioc-dqevent.rst | 377 + .../media/v4l/vidioc-dv-timings-cap.rst | 159 + .../userspace-api/media/v4l/vidioc-encoder-cmd.rst | 169 + .../media/v4l/vidioc-enum-dv-timings.rst | 105 + .../userspace-api/media/v4l/vidioc-enum-fmt.rst | 243 + .../media/v4l/vidioc-enum-frameintervals.rst | 186 + .../media/v4l/vidioc-enum-framesizes.rst | 194 + .../media/v4l/vidioc-enum-freq-bands.rst | 139 + .../userspace-api/media/v4l/vidioc-enumaudio.rst | 53 + .../media/v4l/vidioc-enumaudioout.rst | 58 + .../userspace-api/media/v4l/vidioc-enuminput.rst | 229 + .../userspace-api/media/v4l/vidioc-enumoutput.rst | 153 + .../userspace-api/media/v4l/vidioc-enumstd.rst | 351 + .../userspace-api/media/v4l/vidioc-expbuf.rst | 162 + .../userspace-api/media/v4l/vidioc-g-audio.rst | 124 + .../userspace-api/media/v4l/vidioc-g-audioout.rst | 99 + .../userspace-api/media/v4l/vidioc-g-crop.rst | 110 + .../userspace-api/media/v4l/vidioc-g-ctrl.rst | 100 + .../media/v4l/vidioc-g-dv-timings.rst | 317 + .../userspace-api/media/v4l/vidioc-g-edid.rst | 146 + .../userspace-api/media/v4l/vidioc-g-enc-index.rst | 144 + .../userspace-api/media/v4l/vidioc-g-ext-ctrls.rst | 503 ++ .../userspace-api/media/v4l/vidioc-g-fbuf.rst | 351 + .../userspace-api/media/v4l/vidioc-g-fmt.rst | 154 + .../userspace-api/media/v4l/vidioc-g-frequency.rst | 103 + .../userspace-api/media/v4l/vidioc-g-input.rst | 63 + .../userspace-api/media/v4l/vidioc-g-jpegcomp.rst | 124 + .../userspace-api/media/v4l/vidioc-g-modulator.rst | 193 + .../userspace-api/media/v4l/vidioc-g-output.rst | 65 + .../userspace-api/media/v4l/vidioc-g-parm.rst | 269 + .../userspace-api/media/v4l/vidioc-g-priority.rst | 91 + .../userspace-api/media/v4l/vidioc-g-selection.rst | 190 + .../media/v4l/vidioc-g-sliced-vbi-cap.rst | 202 + .../userspace-api/media/v4l/vidioc-g-std.rst | 82 + .../userspace-api/media/v4l/vidioc-g-tuner.rst | 464 ++ .../userspace-api/media/v4l/vidioc-log-status.rst | 47 + .../userspace-api/media/v4l/vidioc-overlay.rst | 52 + .../userspace-api/media/v4l/vidioc-prepare-buf.rst | 56 + .../userspace-api/media/v4l/vidioc-qbuf.rst | 197 + .../media/v4l/vidioc-query-dv-timings.rst | 86 + .../userspace-api/media/v4l/vidioc-querybuf.rst | 78 + .../userspace-api/media/v4l/vidioc-querycap.rst | 278 + .../userspace-api/media/v4l/vidioc-queryctrl.rst | 660 ++ .../userspace-api/media/v4l/vidioc-querystd.rst | 69 + .../userspace-api/media/v4l/vidioc-reqbufs.rst | 181 + .../media/v4l/vidioc-s-hw-freq-seek.rst | 137 + .../userspace-api/media/v4l/vidioc-streamon.rst | 105 + .../v4l/vidioc-subdev-enum-frame-interval.rst | 111 + .../media/v4l/vidioc-subdev-enum-frame-size.rst | 115 + .../media/v4l/vidioc-subdev-enum-mbus-code.rst | 146 + .../media/v4l/vidioc-subdev-g-crop.rst | 125 + .../media/v4l/vidioc-subdev-g-fmt.rst | 152 + .../media/v4l/vidioc-subdev-g-frame-interval.rst | 119 + .../media/v4l/vidioc-subdev-g-selection.rst | 123 + .../media/v4l/vidioc-subdev-querycap.rst | 104 + .../media/v4l/vidioc-subscribe-event.rst | 113 + .../userspace-api/media/v4l/yuv-formats.rst | 273 + .../userspace-api/media/videodev2.h.rst.exceptions | 599 ++ Documentation/userspace-api/netlink/index.rst | 12 + Documentation/userspace-api/netlink/intro.rst | 681 ++ Documentation/userspace-api/no_new_privs.rst | 63 + Documentation/userspace-api/seccomp_filter.rst | 376 + Documentation/userspace-api/spec_ctrl.rst | 116 + .../userspace-api/sysfs-platform_profile.rst | 42 + Documentation/userspace-api/unshare.rst | 332 + Documentation/userspace-api/vduse.rst | 233 + Documentation/virt/acrn/cpuid.rst | 46 + Documentation/virt/acrn/index.rst | 12 + Documentation/virt/acrn/introduction.rst | 43 + Documentation/virt/acrn/io-request.rst | 97 + Documentation/virt/coco/sev-guest.rst | 161 + Documentation/virt/guest-halt-polling.rst | 84 + Documentation/virt/hyperv/clocks.rst | 73 + Documentation/virt/hyperv/index.rst | 12 + Documentation/virt/hyperv/overview.rst | 207 + Documentation/virt/hyperv/vmbus.rst | 303 + Documentation/virt/index.rst | 24 + Documentation/virt/kvm/api.rst | 8281 ++++++++++++++++++++ Documentation/virt/kvm/arm/hyp-abi.rst | 78 + Documentation/virt/kvm/arm/hypercalls.rst | 138 + Documentation/virt/kvm/arm/index.rst | 13 + Documentation/virt/kvm/arm/ptp_kvm.rst | 25 + Documentation/virt/kvm/arm/pvtime.rst | 80 + Documentation/virt/kvm/devices/README | 1 + Documentation/virt/kvm/devices/arm-vgic-its.rst | 209 + Documentation/virt/kvm/devices/arm-vgic-v3.rst | 291 + Documentation/virt/kvm/devices/arm-vgic.rst | 156 + Documentation/virt/kvm/devices/index.rst | 19 + Documentation/virt/kvm/devices/mpic.rst | 58 + Documentation/virt/kvm/devices/s390_flic.rst | 166 + Documentation/virt/kvm/devices/vcpu.rst | 265 + Documentation/virt/kvm/devices/vfio.rst | 41 + Documentation/virt/kvm/devices/vm.rst | 323 + Documentation/virt/kvm/devices/xics.rst | 92 + Documentation/virt/kvm/devices/xive.rst | 247 + Documentation/virt/kvm/halt-polling.rst | 153 + Documentation/virt/kvm/index.rst | 21 + Documentation/virt/kvm/locking.rst | 284 + Documentation/virt/kvm/ppc-pv.rst | 222 + Documentation/virt/kvm/review-checklist.rst | 41 + Documentation/virt/kvm/s390/index.rst | 13 + Documentation/virt/kvm/s390/s390-diag.rst | 119 + Documentation/virt/kvm/s390/s390-pv-boot.rst | 84 + Documentation/virt/kvm/s390/s390-pv-dump.rst | 64 + Documentation/virt/kvm/s390/s390-pv.rst | 116 + Documentation/virt/kvm/vcpu-requests.rst | 294 + .../virt/kvm/x86/amd-memory-encryption.rst | 446 ++ Documentation/virt/kvm/x86/cpuid.rst | 124 + Documentation/virt/kvm/x86/errata.rst | 39 + Documentation/virt/kvm/x86/hypercalls.rst | 192 + Documentation/virt/kvm/x86/index.rst | 18 + Documentation/virt/kvm/x86/mmu.rst | 484 ++ Documentation/virt/kvm/x86/msr.rst | 391 + Documentation/virt/kvm/x86/nested-vmx.rst | 244 + .../virt/kvm/x86/running-nested-guests.rst | 278 + Documentation/virt/kvm/x86/timekeeping.rst | 645 ++ Documentation/virt/ne_overview.rst | 100 + Documentation/virt/paravirt_ops.rst | 35 + .../virt/uml/user_mode_linux_howto_v2.rst | 1238 +++ Documentation/w1/index.rst | 21 + Documentation/w1/masters/ds2482.rst | 39 + Documentation/w1/masters/ds2490.rst | 72 + Documentation/w1/masters/index.rst | 14 + Documentation/w1/masters/mxc-w1.rst | 17 + Documentation/w1/masters/omap-hdq.rst | 54 + Documentation/w1/masters/w1-gpio.rst | 47 + Documentation/w1/slaves/index.rst | 16 + Documentation/w1/slaves/w1_ds2406.rst | 27 + Documentation/w1/slaves/w1_ds2413.rst | 59 + Documentation/w1/slaves/w1_ds2423.rst | 54 + Documentation/w1/slaves/w1_ds2438.rst | 86 + Documentation/w1/slaves/w1_ds28e04.rst | 41 + Documentation/w1/slaves/w1_ds28e17.rst | 72 + Documentation/w1/slaves/w1_therm.rst | 144 + Documentation/w1/w1-generic.rst | 133 + Documentation/w1/w1-netlink.rst | 202 + .../watchdog/convert_drivers_to_kernel_api.rst | 219 + Documentation/watchdog/hpwdt.rst | 77 + Documentation/watchdog/index.rst | 25 + Documentation/watchdog/mlx-wdt.rst | 66 + Documentation/watchdog/pcwd-watchdog.rst | 71 + Documentation/watchdog/watchdog-api.rst | 271 + Documentation/watchdog/watchdog-kernel-api.rst | 350 + Documentation/watchdog/watchdog-parameters.rst | 740 ++ Documentation/watchdog/watchdog-pm.rst | 22 + Documentation/watchdog/wdt.rst | 63 + Documentation/x86/amd-memory-encryption.rst | 133 + Documentation/x86/amd_hsmp.rst | 86 + Documentation/x86/boot.rst | 1442 ++++ Documentation/x86/booting-dt.rst | 21 + Documentation/x86/buslock.rst | 126 + Documentation/x86/cpuinfo.rst | 154 + Documentation/x86/earlyprintk.rst | 151 + Documentation/x86/elf_auxvec.rst | 53 + Documentation/x86/entry_64.rst | 110 + Documentation/x86/exception-tables.rst | 357 + Documentation/x86/features.rst | 3 + Documentation/x86/i386/IO-APIC.rst | 123 + Documentation/x86/i386/index.rst | 10 + Documentation/x86/ifs.rst | 2 + Documentation/x86/index.rst | 44 + Documentation/x86/intel-hfi.rst | 72 + Documentation/x86/intel_txt.rst | 227 + Documentation/x86/iommu.rst | 151 + Documentation/x86/kernel-stacks.rst | 152 + Documentation/x86/mds.rst | 193 + Documentation/x86/microcode.rst | 240 + Documentation/x86/mtrr.rst | 354 + Documentation/x86/orc-unwinder.rst | 182 + Documentation/x86/pat.rst | 240 + Documentation/x86/pti.rst | 195 + Documentation/x86/resctrl.rst | 1304 +++ Documentation/x86/sgx.rst | 302 + Documentation/x86/sva.rst | 286 + Documentation/x86/tdx.rst | 218 + Documentation/x86/tlb.rst | 83 + Documentation/x86/topology.rst | 234 + Documentation/x86/tsx_async_abort.rst | 117 + Documentation/x86/usb-legacy-support.rst | 50 + Documentation/x86/x86_64/5level-paging.rst | 67 + Documentation/x86/x86_64/boot-options.rst | 319 + Documentation/x86/x86_64/cpu-hotplug-spec.rst | 24 + Documentation/x86/x86_64/fake-numa-for-cpusets.rst | 78 + Documentation/x86/x86_64/fsgs.rst | 199 + Documentation/x86/x86_64/index.rst | 17 + Documentation/x86/x86_64/machinecheck.rst | 33 + Documentation/x86/x86_64/mm.rst | 157 + Documentation/x86/x86_64/uefi.rst | 58 + Documentation/x86/xstate.rst | 74 + Documentation/x86/zero-page.rst | 47 + Documentation/xtensa/atomctl.rst | 51 + Documentation/xtensa/booting.rst | 22 + Documentation/xtensa/features.rst | 3 + Documentation/xtensa/index.rst | 14 + Documentation/xtensa/mmu.rst | 198 + 8865 files changed, 1213555 insertions(+) create mode 100644 Documentation/.gitignore create mode 100644 Documentation/ABI/README create mode 100644 Documentation/ABI/obsolete/o2cb create mode 100644 Documentation/ABI/obsolete/procfs-i8k create mode 100644 Documentation/ABI/obsolete/sysfs-bus-iio create mode 100644 Documentation/ABI/obsolete/sysfs-bus-usb create mode 100644 Documentation/ABI/obsolete/sysfs-class-typec create mode 100644 Documentation/ABI/obsolete/sysfs-cpuidle create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos create mode 100644 Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu create mode 100644 Documentation/ABI/obsolete/sysfs-driver-intel_pmc_bxt create mode 100644 Documentation/ABI/obsolete/sysfs-firmware-acpi create mode 100644 Documentation/ABI/obsolete/sysfs-gpio create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_registered create mode 100644 Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem create mode 100644 Documentation/ABI/obsolete/sysfs-selinux-checkreqprot create mode 100644 Documentation/ABI/obsolete/sysfs-selinux-disable create mode 100644 Documentation/ABI/removed/devfs create mode 100644 Documentation/ABI/removed/dv1394 create mode 100644 Documentation/ABI/removed/ip_queue create mode 100644 Documentation/ABI/removed/net_dma create mode 100644 Documentation/ABI/removed/o2cb create mode 100644 Documentation/ABI/removed/raw1394 create mode 100644 Documentation/ABI/removed/sysfs-bus-nfit create mode 100644 Documentation/ABI/removed/sysfs-class-rfkill create mode 100644 Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore create mode 100644 Documentation/ABI/removed/sysfs-kernel-uids create mode 100644 Documentation/ABI/removed/sysfs-mce create mode 100644 Documentation/ABI/removed/video1394 create mode 100644 Documentation/ABI/stable/firewire-cdev create mode 100644 Documentation/ABI/stable/o2cb create mode 100644 Documentation/ABI/stable/procfs-audit_loginuid create mode 100644 Documentation/ABI/stable/syscalls create mode 100644 Documentation/ABI/stable/sysfs-acpi-pmprofile create mode 100644 Documentation/ABI/stable/sysfs-block create mode 100644 Documentation/ABI/stable/sysfs-bus-firewire create mode 100644 Documentation/ABI/stable/sysfs-bus-fsl-mc create mode 100644 Documentation/ABI/stable/sysfs-bus-mhi create mode 100644 Documentation/ABI/stable/sysfs-bus-nvmem create mode 100644 Documentation/ABI/stable/sysfs-bus-usb create mode 100644 Documentation/ABI/stable/sysfs-bus-vmbus create mode 100644 Documentation/ABI/stable/sysfs-bus-w1 create mode 100644 Documentation/ABI/stable/sysfs-bus-xen-backend create mode 100644 Documentation/ABI/stable/sysfs-class-backlight create mode 100644 Documentation/ABI/stable/sysfs-class-infiniband create mode 100644 Documentation/ABI/stable/sysfs-class-rfkill create mode 100644 Documentation/ABI/stable/sysfs-class-tpm create mode 100644 Documentation/ABI/stable/sysfs-class-ubi create mode 100644 Documentation/ABI/stable/sysfs-class-udc create mode 100644 Documentation/ABI/stable/sysfs-devices create mode 100644 Documentation/ABI/stable/sysfs-devices-node create mode 100644 Documentation/ABI/stable/sysfs-devices-system-cpu create mode 100644 Documentation/ABI/stable/sysfs-devices-system-xen_memory create mode 100644 Documentation/ABI/stable/sysfs-driver-aspeed-vuart create mode 100644 Documentation/ABI/stable/sysfs-driver-dma-idxd create mode 100644 Documentation/ABI/stable/sysfs-driver-dma-ioatdma create mode 100644 Documentation/ABI/stable/sysfs-driver-firmware-zynqmp create mode 100644 Documentation/ABI/stable/sysfs-driver-ib_srp create mode 100644 Documentation/ABI/stable/sysfs-driver-mlxreg-io create mode 100644 Documentation/ABI/stable/sysfs-driver-qla2xxx create mode 100644 Documentation/ABI/stable/sysfs-driver-speakup create mode 100644 Documentation/ABI/stable/sysfs-driver-usb-usbtmc create mode 100644 Documentation/ABI/stable/sysfs-driver-w1_ds2438 create mode 100644 Documentation/ABI/stable/sysfs-driver-w1_ds28e04 create mode 100644 Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 create mode 100644 Documentation/ABI/stable/sysfs-firmware-efi-vars create mode 100644 Documentation/ABI/stable/sysfs-firmware-opal-dump create mode 100644 Documentation/ABI/stable/sysfs-firmware-opal-elog create mode 100644 Documentation/ABI/stable/sysfs-fs-orangefs create mode 100644 Documentation/ABI/stable/sysfs-hypervisor-xen create mode 100644 Documentation/ABI/stable/sysfs-kernel-notes create mode 100644 Documentation/ABI/stable/sysfs-module create mode 100644 Documentation/ABI/stable/sysfs-transport-srp create mode 100644 Documentation/ABI/stable/thermal-notification create mode 100644 Documentation/ABI/stable/vdso create mode 100644 Documentation/ABI/testing/configfs-acpi create mode 100644 Documentation/ABI/testing/configfs-iio create mode 100644 Documentation/ABI/testing/configfs-most create mode 100644 Documentation/ABI/testing/configfs-rdma_cm create mode 100644 Documentation/ABI/testing/configfs-spear-pcie-gadget create mode 100644 Documentation/ABI/testing/configfs-stp-policy create mode 100644 Documentation/ABI/testing/configfs-stp-policy-p_sys-t create mode 100644 Documentation/ABI/testing/configfs-usb-gadget create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-acm create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-ecm create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-eem create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-ffs create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-hid create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-loopback create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-mass-storage create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-midi create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-ncm create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-obex create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-phonet create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-printer create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-rndis create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-serial create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-sourcesink create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-subset create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-tcm create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-uac1 create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-uac1_legacy create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-uac2 create mode 100644 Documentation/ABI/testing/configfs-usb-gadget-uvc create mode 100644 Documentation/ABI/testing/debugfs-cec-error-inj create mode 100644 Documentation/ABI/testing/debugfs-cros-ec create mode 100644 Documentation/ABI/testing/debugfs-driver-genwqe create mode 100644 Documentation/ABI/testing/debugfs-driver-habanalabs create mode 100644 Documentation/ABI/testing/debugfs-ec create mode 100644 Documentation/ABI/testing/debugfs-hisi-hpre create mode 100644 Documentation/ABI/testing/debugfs-hisi-sec create mode 100644 Documentation/ABI/testing/debugfs-hisi-zip create mode 100644 Documentation/ABI/testing/debugfs-hyperv create mode 100644 Documentation/ABI/testing/debugfs-ideapad create mode 100644 Documentation/ABI/testing/debugfs-moxtet create mode 100644 Documentation/ABI/testing/debugfs-olpc create mode 100644 Documentation/ABI/testing/debugfs-pfo-nx-crypto create mode 100644 Documentation/ABI/testing/debugfs-pktcdvd create mode 100644 Documentation/ABI/testing/debugfs-turris-mox-rwtm create mode 100644 Documentation/ABI/testing/debugfs-wilco-ec create mode 100644 Documentation/ABI/testing/dell-smbios-wmi create mode 100644 Documentation/ABI/testing/dev-kmsg create mode 100644 Documentation/ABI/testing/devlink-resource-mlxsw create mode 100644 Documentation/ABI/testing/evm create mode 100644 Documentation/ABI/testing/gpio-cdev create mode 100644 Documentation/ABI/testing/ima_policy create mode 100644 Documentation/ABI/testing/ppc-memtrace create mode 100644 Documentation/ABI/testing/procfs-attr-current create mode 100644 Documentation/ABI/testing/procfs-attr-exec create mode 100644 Documentation/ABI/testing/procfs-attr-prev create mode 100644 Documentation/ABI/testing/procfs-diskstats create mode 100644 Documentation/ABI/testing/procfs-smaps_rollup create mode 100644 Documentation/ABI/testing/pstore create mode 100644 Documentation/ABI/testing/rtc-cdev create mode 100644 Documentation/ABI/testing/securityfs-secrets-coco create mode 100644 Documentation/ABI/testing/sysfs-amd-pmc create mode 100644 Documentation/ABI/testing/sysfs-amd-pmf create mode 100644 Documentation/ABI/testing/sysfs-ata create mode 100644 Documentation/ABI/testing/sysfs-block-aoe create mode 100644 Documentation/ABI/testing/sysfs-block-bcache create mode 100644 Documentation/ABI/testing/sysfs-block-device create mode 100644 Documentation/ABI/testing/sysfs-block-dm create mode 100644 Documentation/ABI/testing/sysfs-block-loop create mode 100644 Documentation/ABI/testing/sysfs-block-rnbd create mode 100644 Documentation/ABI/testing/sysfs-block-rssd create mode 100644 Documentation/ABI/testing/sysfs-block-zram create mode 100644 Documentation/ABI/testing/sysfs-bus-acpi create mode 100644 Documentation/ABI/testing/sysfs-bus-amba create mode 100644 Documentation/ABI/testing/sysfs-bus-bcma create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-cti create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10 create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-stm create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc create mode 100644 Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe create mode 100644 Documentation/ABI/testing/sysfs-bus-counter create mode 100644 Documentation/ABI/testing/sysfs-bus-css create mode 100644 Documentation/ABI/testing/sysfs-bus-cxl create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-emif create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-n3000-nios create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-caps create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-dsa create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-events create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-format create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-uncore create mode 100644 Documentation/ABI/testing/sysfs-bus-fcoe create mode 100644 Documentation/ABI/testing/sysfs-bus-fsi create mode 100644 Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo create mode 100644 Documentation/ABI/testing/sysfs-bus-fsl-mc create mode 100644 Documentation/ABI/testing/sysfs-bus-hsi create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-bq32k create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x create mode 100644 Documentation/ABI/testing/sysfs-bus-i3c create mode 100644 Documentation/ABI/testing/sysfs-bus-iio create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-max9611 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-adc-stm32 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-bno055 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-cros-ec create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-distance-srf08 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dma-buffer create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-health-afe440x create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-humidity create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-impedance-analyzer-ad5933 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-isl29501 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-isl29018 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-si1133 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-tsl2583 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-tsl2772 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-magnetometer-hmc5843 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-meas-spec create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-mpu6050 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-potentiometer-mcp4531 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-proximity create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-sps30 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-sx9310 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-sx9324 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-thermocouple create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-vf610 create mode 100644 Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth create mode 100644 Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc create mode 100644 Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti create mode 100644 Documentation/ABI/testing/sysfs-bus-intel_th-output-devices create mode 100644 Documentation/ABI/testing/sysfs-bus-mcb create mode 100644 Documentation/ABI/testing/sysfs-bus-mdio create mode 100644 Documentation/ABI/testing/sysfs-bus-media create mode 100644 Documentation/ABI/testing/sysfs-bus-mei create mode 100644 Documentation/ABI/testing/sysfs-bus-mmc create mode 100644 Documentation/ABI/testing/sysfs-bus-most create mode 100644 Documentation/ABI/testing/sysfs-bus-moxtet-devices create mode 100644 Documentation/ABI/testing/sysfs-bus-nfit create mode 100644 Documentation/ABI/testing/sysfs-bus-nvdimm create mode 100644 Documentation/ABI/testing/sysfs-bus-optee-devices create mode 100644 Documentation/ABI/testing/sysfs-bus-papr-pmem create mode 100644 Documentation/ABI/testing/sysfs-bus-pci create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-devices-aer_stats create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-devices-catpt create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-devices-cciss create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-devices-pvpanic create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd create mode 100644 Documentation/ABI/testing/sysfs-bus-peci create mode 100644 Documentation/ABI/testing/sysfs-bus-platform create mode 100644 Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon create mode 100644 Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub create mode 100644 Documentation/ABI/testing/sysfs-bus-rapidio create mode 100644 Documentation/ABI/testing/sysfs-bus-rbd create mode 100644 Documentation/ABI/testing/sysfs-bus-rpmsg create mode 100644 Documentation/ABI/testing/sysfs-bus-siox create mode 100644 Documentation/ABI/testing/sysfs-bus-soundwire-master create mode 100644 Documentation/ABI/testing/sysfs-bus-soundwire-slave create mode 100644 Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor create mode 100644 Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw create mode 100644 Documentation/ABI/testing/sysfs-bus-thunderbolt create mode 100644 Documentation/ABI/testing/sysfs-bus-typec create mode 100644 Documentation/ABI/testing/sysfs-bus-umc create mode 100644 Documentation/ABI/testing/sysfs-bus-usb create mode 100644 Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg create mode 100644 Documentation/ABI/testing/sysfs-bus-usb-lvstest create mode 100644 Documentation/ABI/testing/sysfs-bus-vdpa create mode 100644 Documentation/ABI/testing/sysfs-bus-vfio-mdev create mode 100644 Documentation/ABI/testing/sysfs-bus-vmbus create mode 100644 Documentation/ABI/testing/sysfs-c2port create mode 100644 Documentation/ABI/testing/sysfs-cfq-target-latency create mode 100644 Documentation/ABI/testing/sysfs-class create mode 100644 Documentation/ABI/testing/sysfs-class-backlight create mode 100644 Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 create mode 100644 Documentation/ABI/testing/sysfs-class-backlight-lm3639 create mode 100644 Documentation/ABI/testing/sysfs-class-bdi create mode 100644 Documentation/ABI/testing/sysfs-class-bsr create mode 100644 Documentation/ABI/testing/sysfs-class-chromeos create mode 100644 Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-lightbar create mode 100644 Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-vbc create mode 100644 Documentation/ABI/testing/sysfs-class-cxl create mode 100644 Documentation/ABI/testing/sysfs-class-devfreq create mode 100644 Documentation/ABI/testing/sysfs-class-devfreq-event create mode 100644 Documentation/ABI/testing/sysfs-class-devlink create mode 100644 Documentation/ABI/testing/sysfs-class-extcon create mode 100644 Documentation/ABI/testing/sysfs-class-fc create mode 100644 Documentation/ABI/testing/sysfs-class-fc_host create mode 100644 Documentation/ABI/testing/sysfs-class-fc_remote_ports create mode 100644 Documentation/ABI/testing/sysfs-class-firmware create mode 100644 Documentation/ABI/testing/sysfs-class-firmware-attributes create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-bridge create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-manager create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-region create mode 100644 Documentation/ABI/testing/sysfs-class-gnss create mode 100644 Documentation/ABI/testing/sysfs-class-hwmon create mode 100644 Documentation/ABI/testing/sysfs-class-intel_pmt create mode 100644 Documentation/ABI/testing/sysfs-class-iommu create mode 100644 Documentation/ABI/testing/sysfs-class-iommu-amd-iommu create mode 100644 Documentation/ABI/testing/sysfs-class-iommu-intel-iommu create mode 100644 Documentation/ABI/testing/sysfs-class-lcd create mode 100644 Documentation/ABI/testing/sysfs-class-led create mode 100644 Documentation/ABI/testing/sysfs-class-led-driver-lm3533 create mode 100644 Documentation/ABI/testing/sysfs-class-led-driver-turris-omnia create mode 100644 Documentation/ABI/testing/sysfs-class-led-flash create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-netdev create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-oneshot create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-pattern create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-tty create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-usbport create mode 100644 Documentation/ABI/testing/sysfs-class-leds-gt683r create mode 100644 Documentation/ABI/testing/sysfs-class-mei create mode 100644 Documentation/ABI/testing/sysfs-class-mic create mode 100644 Documentation/ABI/testing/sysfs-class-mtd create mode 100644 Documentation/ABI/testing/sysfs-class-mux create mode 100644 Documentation/ABI/testing/sysfs-class-net create mode 100644 Documentation/ABI/testing/sysfs-class-net-cdc_ncm create mode 100644 Documentation/ABI/testing/sysfs-class-net-dsa create mode 100644 Documentation/ABI/testing/sysfs-class-net-grcan create mode 100644 Documentation/ABI/testing/sysfs-class-net-janz-ican3 create mode 100644 Documentation/ABI/testing/sysfs-class-net-phydev create mode 100644 Documentation/ABI/testing/sysfs-class-net-qmi create mode 100644 Documentation/ABI/testing/sysfs-class-net-queues create mode 100644 Documentation/ABI/testing/sysfs-class-net-statistics create mode 100644 Documentation/ABI/testing/sysfs-class-ocxl create mode 100644 Documentation/ABI/testing/sysfs-class-pktcdvd create mode 100644 Documentation/ABI/testing/sysfs-class-power create mode 100644 Documentation/ABI/testing/sysfs-class-power-ltc4162l create mode 100644 Documentation/ABI/testing/sysfs-class-power-mp2629 create mode 100644 Documentation/ABI/testing/sysfs-class-power-surface create mode 100644 Documentation/ABI/testing/sysfs-class-power-twl4030 create mode 100644 Documentation/ABI/testing/sysfs-class-power-wilco create mode 100644 Documentation/ABI/testing/sysfs-class-powercap create mode 100644 Documentation/ABI/testing/sysfs-class-pwm create mode 100644 Documentation/ABI/testing/sysfs-class-rapidio create mode 100644 Documentation/ABI/testing/sysfs-class-rc create mode 100644 Documentation/ABI/testing/sysfs-class-rc-nuvoton create mode 100644 Documentation/ABI/testing/sysfs-class-regulator create mode 100644 Documentation/ABI/testing/sysfs-class-remoteproc create mode 100644 Documentation/ABI/testing/sysfs-class-rnbd-client create mode 100644 Documentation/ABI/testing/sysfs-class-rnbd-server create mode 100644 Documentation/ABI/testing/sysfs-class-rtc create mode 100644 Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration create mode 100644 Documentation/ABI/testing/sysfs-class-rtrs-client create mode 100644 Documentation/ABI/testing/sysfs-class-rtrs-server create mode 100644 Documentation/ABI/testing/sysfs-class-scsi_host create mode 100644 Documentation/ABI/testing/sysfs-class-scsi_tape create mode 100644 Documentation/ABI/testing/sysfs-class-spi-eeprom create mode 100644 Documentation/ABI/testing/sysfs-class-stm create mode 100644 Documentation/ABI/testing/sysfs-class-stm_source create mode 100644 Documentation/ABI/testing/sysfs-class-switchtec create mode 100644 Documentation/ABI/testing/sysfs-class-thermal create mode 100644 Documentation/ABI/testing/sysfs-class-typec create mode 100644 Documentation/ABI/testing/sysfs-class-usb_power_delivery create mode 100644 Documentation/ABI/testing/sysfs-class-usb_role create mode 100644 Documentation/ABI/testing/sysfs-class-uwb_rc create mode 100644 Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc create mode 100644 Documentation/ABI/testing/sysfs-class-vduse create mode 100644 Documentation/ABI/testing/sysfs-class-wakeup create mode 100644 Documentation/ABI/testing/sysfs-class-watchdog create mode 100644 Documentation/ABI/testing/sysfs-class-zram create mode 100644 Documentation/ABI/testing/sysfs-dev create mode 100644 Documentation/ABI/testing/sysfs-devices create mode 100644 Documentation/ABI/testing/sysfs-devices-consumer create mode 100644 Documentation/ABI/testing/sysfs-devices-coredump create mode 100644 Documentation/ABI/testing/sysfs-devices-edac create mode 100644 Documentation/ABI/testing/sysfs-devices-firmware_node create mode 100644 Documentation/ABI/testing/sysfs-devices-hisi_ptt create mode 100644 Documentation/ABI/testing/sysfs-devices-lpss_ltr create mode 100644 Documentation/ABI/testing/sysfs-devices-mapping create mode 100644 Documentation/ABI/testing/sysfs-devices-memory create mode 100644 Documentation/ABI/testing/sysfs-devices-mmc create mode 100644 Documentation/ABI/testing/sysfs-devices-online create mode 100644 Documentation/ABI/testing/sysfs-devices-physical_location create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-ACPI-TAD create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-docg3 create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-dock create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-ipmi create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-soc-ipa create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-trackpoint create mode 100644 Documentation/ABI/testing/sysfs-devices-power create mode 100644 Documentation/ABI/testing/sysfs-devices-power_resources_D0 create mode 100644 Documentation/ABI/testing/sysfs-devices-power_resources_D1 create mode 100644 Documentation/ABI/testing/sysfs-devices-power_resources_D2 create mode 100644 Documentation/ABI/testing/sysfs-devices-power_resources_D3hot create mode 100644 Documentation/ABI/testing/sysfs-devices-power_resources_wakeup create mode 100644 Documentation/ABI/testing/sysfs-devices-power_state create mode 100644 Documentation/ABI/testing/sysfs-devices-real_power_state create mode 100644 Documentation/ABI/testing/sysfs-devices-removable create mode 100644 Documentation/ABI/testing/sysfs-devices-resource_in_use create mode 100644 Documentation/ABI/testing/sysfs-devices-soc create mode 100644 Documentation/ABI/testing/sysfs-devices-software_node create mode 100644 Documentation/ABI/testing/sysfs-devices-state_synced create mode 100644 Documentation/ABI/testing/sysfs-devices-sun create mode 100644 Documentation/ABI/testing/sysfs-devices-supplier create mode 100644 Documentation/ABI/testing/sysfs-devices-system-cpu create mode 100644 Documentation/ABI/testing/sysfs-devices-system-ibm-rtl create mode 100644 Documentation/ABI/testing/sysfs-devices-system-xen_cpu create mode 100644 Documentation/ABI/testing/sysfs-devices-vfio-dev create mode 100644 Documentation/ABI/testing/sysfs-devices-waiting_for_supplier create mode 100644 Documentation/ABI/testing/sysfs-devices-xenbus create mode 100644 Documentation/ABI/testing/sysfs-driver-altera-cvp create mode 100644 Documentation/ABI/testing/sysfs-driver-aspeed-uart-routing create mode 100644 Documentation/ABI/testing/sysfs-driver-bd9571mwv-regulator create mode 100644 Documentation/ABI/testing/sysfs-driver-ccp create mode 100644 Documentation/ABI/testing/sysfs-driver-chromeos-acpi create mode 100644 Documentation/ABI/testing/sysfs-driver-eud create mode 100644 Documentation/ABI/testing/sysfs-driver-fsi-master-gpio create mode 100644 Documentation/ABI/testing/sysfs-driver-ge-achc create mode 100644 Documentation/ABI/testing/sysfs-driver-genwqe create mode 100644 Documentation/ABI/testing/sysfs-driver-habanalabs create mode 100644 Documentation/ABI/testing/sysfs-driver-hid create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-corsair create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-lenovo create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-logitech-hidpp create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-multitouch create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-ntrig create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-picolcd create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-prodikeys create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-roccat-kone create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-srws1 create mode 100644 Documentation/ABI/testing/sysfs-driver-hid-wiimote create mode 100644 Documentation/ABI/testing/sysfs-driver-input-axp-pek create mode 100644 Documentation/ABI/testing/sysfs-driver-input-cros-ec-keyb create mode 100644 Documentation/ABI/testing/sysfs-driver-input-exc3000 create mode 100644 Documentation/ABI/testing/sysfs-driver-intc_sar create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-rapid-start create mode 100644 Documentation/ABI/testing/sysfs-driver-intel_sdsi create mode 100644 Documentation/ABI/testing/sysfs-driver-jz4780-efuse create mode 100644 Documentation/ABI/testing/sysfs-driver-pciback create mode 100644 Documentation/ABI/testing/sysfs-driver-ppi create mode 100644 Documentation/ABI/testing/sysfs-driver-qat create mode 100644 Documentation/ABI/testing/sysfs-driver-samsung-laptop create mode 100644 Documentation/ABI/testing/sysfs-driver-st create mode 100644 Documentation/ABI/testing/sysfs-driver-tegra-fuse create mode 100644 Documentation/ABI/testing/sysfs-driver-toshiba_acpi create mode 100644 Documentation/ABI/testing/sysfs-driver-toshiba_haps create mode 100644 Documentation/ABI/testing/sysfs-driver-typec-displayport create mode 100644 Documentation/ABI/testing/sysfs-driver-uacce create mode 100644 Documentation/ABI/testing/sysfs-driver-ucsi-ccg create mode 100644 Documentation/ABI/testing/sysfs-driver-ufs create mode 100644 Documentation/ABI/testing/sysfs-driver-w1_ds28e17 create mode 100644 Documentation/ABI/testing/sysfs-driver-w1_therm create mode 100644 Documentation/ABI/testing/sysfs-driver-wacom create mode 100644 Documentation/ABI/testing/sysfs-driver-xdata create mode 100644 Documentation/ABI/testing/sysfs-driver-xen-blkback create mode 100644 Documentation/ABI/testing/sysfs-driver-xen-blkfront create mode 100644 Documentation/ABI/testing/sysfs-firmware-acpi create mode 100644 Documentation/ABI/testing/sysfs-firmware-dmi-entries create mode 100644 Documentation/ABI/testing/sysfs-firmware-dmi-tables create mode 100644 Documentation/ABI/testing/sysfs-firmware-efi create mode 100644 Documentation/ABI/testing/sysfs-firmware-efi-esrt create mode 100644 Documentation/ABI/testing/sysfs-firmware-efi-runtime-map create mode 100644 Documentation/ABI/testing/sysfs-firmware-gsmi create mode 100644 Documentation/ABI/testing/sysfs-firmware-lefi-boardinfo create mode 100644 Documentation/ABI/testing/sysfs-firmware-log create mode 100644 Documentation/ABI/testing/sysfs-firmware-memmap create mode 100644 Documentation/ABI/testing/sysfs-firmware-ofw create mode 100644 Documentation/ABI/testing/sysfs-firmware-opal-powercap create mode 100644 Documentation/ABI/testing/sysfs-firmware-opal-psr create mode 100644 Documentation/ABI/testing/sysfs-firmware-opal-sensor-groups create mode 100644 Documentation/ABI/testing/sysfs-firmware-papr-energy-scale-info create mode 100644 Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg create mode 100644 Documentation/ABI/testing/sysfs-firmware-sgi_uv create mode 100644 Documentation/ABI/testing/sysfs-firmware-turris-mox-rwtm create mode 100644 Documentation/ABI/testing/sysfs-fs-erofs create mode 100644 Documentation/ABI/testing/sysfs-fs-ext4 create mode 100644 Documentation/ABI/testing/sysfs-fs-f2fs create mode 100644 Documentation/ABI/testing/sysfs-fs-nilfs2 create mode 100644 Documentation/ABI/testing/sysfs-fs-ubifs create mode 100644 Documentation/ABI/testing/sysfs-fs-xfs create mode 100644 Documentation/ABI/testing/sysfs-hypervisor-xen create mode 100644 Documentation/ABI/testing/sysfs-ibft create mode 100644 Documentation/ABI/testing/sysfs-kernel-boot_params create mode 100644 Documentation/ABI/testing/sysfs-kernel-btf create mode 100644 Documentation/ABI/testing/sysfs-kernel-dmabuf-buffers create mode 100644 Documentation/ABI/testing/sysfs-kernel-fadump create mode 100644 Documentation/ABI/testing/sysfs-kernel-fscaps create mode 100644 Documentation/ABI/testing/sysfs-kernel-iommu_groups create mode 100644 Documentation/ABI/testing/sysfs-kernel-irq create mode 100644 Documentation/ABI/testing/sysfs-kernel-livepatch create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-cma create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-damon create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-hugepages create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-ksm create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-memory-tiers create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-numa create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-swap create mode 100644 Documentation/ABI/testing/sysfs-kernel-oops_count create mode 100644 Documentation/ABI/testing/sysfs-kernel-reboot create mode 100644 Documentation/ABI/testing/sysfs-kernel-slab create mode 100644 Documentation/ABI/testing/sysfs-kernel-vmcoreinfo create mode 100644 Documentation/ABI/testing/sysfs-kernel-warn_count create mode 100644 Documentation/ABI/testing/sysfs-mce create mode 100644 Documentation/ABI/testing/sysfs-memory-page-offline create mode 100644 Documentation/ABI/testing/sysfs-module create mode 100644 Documentation/ABI/testing/sysfs-ocfs2 create mode 100644 Documentation/ABI/testing/sysfs-platform-asus-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-asus-wmi create mode 100644 Documentation/ABI/testing/sysfs-platform-at91 create mode 100644 Documentation/ABI/testing/sysfs-platform-brcmstb-gisb-arb create mode 100644 Documentation/ABI/testing/sysfs-platform-brcmstb-memc create mode 100644 Documentation/ABI/testing/sysfs-platform-chipidea-usb-otg create mode 100644 Documentation/ABI/testing/sysfs-platform-chipidea-usb2 create mode 100644 Documentation/ABI/testing/sysfs-platform-dell-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi create mode 100644 Documentation/ABI/testing/sysfs-platform-dell-smbios create mode 100644 Documentation/ABI/testing/sysfs-platform-dfl-fme create mode 100644 Documentation/ABI/testing/sysfs-platform-dfl-port create mode 100644 Documentation/ABI/testing/sysfs-platform-dptf create mode 100644 Documentation/ABI/testing/sysfs-platform-eeepc-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma-mgmt create mode 100644 Documentation/ABI/testing/sysfs-platform-i2c-demux-pinctrl create mode 100644 Documentation/ABI/testing/sysfs-platform-ideapad-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-intel-ifs create mode 100644 Documentation/ABI/testing/sysfs-platform-intel-pmc create mode 100644 Documentation/ABI/testing/sysfs-platform-intel-wmi-sbl-fw-update create mode 100644 Documentation/ABI/testing/sysfs-platform-intel-wmi-thunderbolt create mode 100644 Documentation/ABI/testing/sysfs-platform-kim create mode 100644 Documentation/ABI/testing/sysfs-platform-lg-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-mellanox-bootctl create mode 100644 Documentation/ABI/testing/sysfs-platform-msi-laptop create mode 100644 Documentation/ABI/testing/sysfs-platform-phy-rcar-gen3-usb2 create mode 100644 Documentation/ABI/testing/sysfs-platform-renesas_usb3 create mode 100644 Documentation/ABI/testing/sysfs-platform-sst-atom create mode 100644 Documentation/ABI/testing/sysfs-platform-tahvo-usb create mode 100644 Documentation/ABI/testing/sysfs-platform-ts5500 create mode 100644 Documentation/ABI/testing/sysfs-platform-twl4030-usb create mode 100644 Documentation/ABI/testing/sysfs-platform-usbip-vudc create mode 100644 Documentation/ABI/testing/sysfs-platform-wilco-ec create mode 100644 Documentation/ABI/testing/sysfs-platform_profile create mode 100644 Documentation/ABI/testing/sysfs-power create mode 100644 Documentation/ABI/testing/sysfs-pps create mode 100644 Documentation/ABI/testing/sysfs-profiling create mode 100644 Documentation/ABI/testing/sysfs-ptp create mode 100644 Documentation/ABI/testing/sysfs-secvar create mode 100644 Documentation/ABI/testing/sysfs-timecard create mode 100644 Documentation/ABI/testing/sysfs-tty create mode 100644 Documentation/ABI/testing/sysfs-uevent create mode 100644 Documentation/ABI/testing/sysfs-wusb_cbaf create mode 100644 Documentation/ABI/testing/usb-charger-uevent create mode 100644 Documentation/ABI/testing/usb-uevent create mode 120000 Documentation/Changes create mode 100644 Documentation/CodingStyle create mode 100644 Documentation/Kconfig create mode 100644 Documentation/Makefile create mode 100644 Documentation/PCI/acpi-info.rst create mode 100644 Documentation/PCI/boot-interrupts.rst create mode 100644 Documentation/PCI/endpoint/function/binding/pci-ntb.rst create mode 100644 Documentation/PCI/endpoint/function/binding/pci-test.rst create mode 100644 Documentation/PCI/endpoint/index.rst create mode 100644 Documentation/PCI/endpoint/pci-endpoint-cfs.rst create mode 100644 Documentation/PCI/endpoint/pci-endpoint.rst create mode 100644 Documentation/PCI/endpoint/pci-ntb-function.rst create mode 100644 Documentation/PCI/endpoint/pci-ntb-howto.rst create mode 100644 Documentation/PCI/endpoint/pci-test-function.rst create mode 100644 Documentation/PCI/endpoint/pci-test-howto.rst create mode 100644 Documentation/PCI/endpoint/pci-vntb-function.rst create mode 100644 Documentation/PCI/endpoint/pci-vntb-howto.rst create mode 100644 Documentation/PCI/index.rst create mode 100644 Documentation/PCI/msi-howto.rst create mode 100644 Documentation/PCI/pci-error-recovery.rst create mode 100644 Documentation/PCI/pci-iov-howto.rst create mode 100644 Documentation/PCI/pci.rst create mode 100644 Documentation/PCI/pcieaer-howto.rst create mode 100644 Documentation/PCI/pciebus-howto.rst create mode 100644 Documentation/PCI/sysfs-pci.rst create mode 100644 Documentation/RCU/Design/Data-Structures/BigTreeClassicRCU.svg create mode 100644 Documentation/RCU/Design/Data-Structures/BigTreePreemptRCUBHdyntickCB.svg create mode 100644 Documentation/RCU/Design/Data-Structures/Data-Structures.rst create mode 100644 Documentation/RCU/Design/Data-Structures/HugeTreeClassicRCU.svg create mode 100644 Documentation/RCU/Design/Data-Structures/TreeLevel.svg create mode 100644 Documentation/RCU/Design/Data-Structures/TreeMapping.svg create mode 100644 Documentation/RCU/Design/Data-Structures/TreeMappingLevel.svg create mode 100644 Documentation/RCU/Design/Data-Structures/blkd_task.svg create mode 100644 Documentation/RCU/Design/Data-Structures/nxtlist.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/ExpRCUFlow.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/ExpSchedFlow.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel0.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel1.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel2.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel3.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel4.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel5.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel6.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel7.svg create mode 100644 Documentation/RCU/Design/Expedited-Grace-Periods/Funnel8.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-invocation.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-registry.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-dyntick.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-cleanup.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-fqs.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-1.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-2.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-3.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-hotplug.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg create mode 100644 Documentation/RCU/Design/Memory-Ordering/rcu_node-lock.svg create mode 100644 Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg create mode 100644 Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg create mode 100644 Documentation/RCU/Design/Requirements/Requirements.rst create mode 100644 Documentation/RCU/NMI-RCU.rst create mode 100644 Documentation/RCU/RTFP.txt create mode 100644 Documentation/RCU/UP.rst create mode 100644 Documentation/RCU/arrayRCU.rst create mode 100644 Documentation/RCU/checklist.rst create mode 100644 Documentation/RCU/index.rst create mode 100644 Documentation/RCU/listRCU.rst create mode 100644 Documentation/RCU/lockdep-splat.rst create mode 100644 Documentation/RCU/lockdep.rst create mode 100644 Documentation/RCU/rcu.rst create mode 100644 Documentation/RCU/rcu_dereference.rst create mode 100644 Documentation/RCU/rcubarrier.rst create mode 100644 Documentation/RCU/rculist_nulls.rst create mode 100644 Documentation/RCU/rcuref.rst create mode 100644 Documentation/RCU/stallwarn.rst create mode 100644 Documentation/RCU/torture.rst create mode 100644 Documentation/RCU/whatisRCU.rst create mode 100644 Documentation/SubmittingPatches create mode 100644 Documentation/accounting/cgroupstats.rst create mode 100644 Documentation/accounting/delay-accounting.rst create mode 100644 Documentation/accounting/index.rst create mode 100644 Documentation/accounting/psi.rst create mode 100644 Documentation/accounting/taskstats-struct.rst create mode 100644 Documentation/accounting/taskstats.rst create mode 100644 Documentation/admin-guide/LSM/LoadPin.rst create mode 100644 Documentation/admin-guide/LSM/SELinux.rst create mode 100644 Documentation/admin-guide/LSM/SafeSetID.rst create mode 100644 Documentation/admin-guide/LSM/Smack.rst create mode 100644 Documentation/admin-guide/LSM/Yama.rst create mode 100644 Documentation/admin-guide/LSM/apparmor.rst create mode 100644 Documentation/admin-guide/LSM/index.rst create mode 100644 Documentation/admin-guide/LSM/tomoyo.rst create mode 100644 Documentation/admin-guide/README.rst create mode 100644 Documentation/admin-guide/abi-obsolete.rst create mode 100644 Documentation/admin-guide/abi-removed.rst create mode 100644 Documentation/admin-guide/abi-stable.rst create mode 100644 Documentation/admin-guide/abi-testing.rst create mode 100644 Documentation/admin-guide/abi.rst create mode 100644 Documentation/admin-guide/acpi/cppc_sysfs.rst create mode 100644 Documentation/admin-guide/acpi/fan_performance_states.rst create mode 100644 Documentation/admin-guide/acpi/index.rst create mode 100644 Documentation/admin-guide/acpi/initrd_table_override.rst create mode 100644 Documentation/admin-guide/acpi/ssdt-overlays.rst create mode 100644 Documentation/admin-guide/aoe/aoe.rst create mode 100644 Documentation/admin-guide/aoe/autoload.sh create mode 100644 Documentation/admin-guide/aoe/examples.rst create mode 100644 Documentation/admin-guide/aoe/index.rst create mode 100644 Documentation/admin-guide/aoe/status.sh create mode 100644 Documentation/admin-guide/aoe/todo.rst create mode 100644 Documentation/admin-guide/aoe/udev-install.sh create mode 100644 Documentation/admin-guide/aoe/udev.txt create mode 100644 Documentation/admin-guide/auxdisplay/cfag12864b.rst create mode 100644 Documentation/admin-guide/auxdisplay/index.rst create mode 100644 Documentation/admin-guide/auxdisplay/ks0108.rst create mode 100644 Documentation/admin-guide/bcache.rst create mode 100644 Documentation/admin-guide/binderfs.rst create mode 100644 Documentation/admin-guide/binfmt-misc.rst create mode 100644 Documentation/admin-guide/blockdev/drbd/DRBD-8.3-data-packets.svg create mode 100644 Documentation/admin-guide/blockdev/drbd/DRBD-data-packets.svg create mode 100644 Documentation/admin-guide/blockdev/drbd/conn-states-8.dot create mode 100644 Documentation/admin-guide/blockdev/drbd/data-structure-v9.rst create mode 100644 Documentation/admin-guide/blockdev/drbd/disk-states-8.dot create mode 100644 Documentation/admin-guide/blockdev/drbd/drbd-connection-state-overview.dot create mode 100644 Documentation/admin-guide/blockdev/drbd/figures.rst create mode 100644 Documentation/admin-guide/blockdev/drbd/index.rst create mode 100644 Documentation/admin-guide/blockdev/drbd/peer-states-8.dot create mode 100644 Documentation/admin-guide/blockdev/floppy.rst create mode 100644 Documentation/admin-guide/blockdev/index.rst create mode 100644 Documentation/admin-guide/blockdev/nbd.rst create mode 100644 Documentation/admin-guide/blockdev/paride.rst create mode 100644 Documentation/admin-guide/blockdev/ramdisk.rst create mode 100644 Documentation/admin-guide/blockdev/zram.rst create mode 100644 Documentation/admin-guide/bootconfig.rst create mode 100644 Documentation/admin-guide/braille-console.rst create mode 100644 Documentation/admin-guide/btmrvl.rst create mode 100644 Documentation/admin-guide/bug-bisect.rst create mode 100644 Documentation/admin-guide/bug-hunting.rst create mode 100644 Documentation/admin-guide/cgroup-v1/blkio-controller.rst create mode 100644 Documentation/admin-guide/cgroup-v1/cgroups.rst create mode 100644 Documentation/admin-guide/cgroup-v1/cpuacct.rst create mode 100644 Documentation/admin-guide/cgroup-v1/cpusets.rst create mode 100644 Documentation/admin-guide/cgroup-v1/devices.rst create mode 100644 Documentation/admin-guide/cgroup-v1/freezer-subsystem.rst create mode 100644 Documentation/admin-guide/cgroup-v1/hugetlb.rst create mode 100644 Documentation/admin-guide/cgroup-v1/index.rst create mode 100644 Documentation/admin-guide/cgroup-v1/memcg_test.rst create mode 100644 Documentation/admin-guide/cgroup-v1/memory.rst create mode 100644 Documentation/admin-guide/cgroup-v1/misc.rst create mode 100644 Documentation/admin-guide/cgroup-v1/net_cls.rst create mode 100644 Documentation/admin-guide/cgroup-v1/net_prio.rst create mode 100644 Documentation/admin-guide/cgroup-v1/pids.rst create mode 100644 Documentation/admin-guide/cgroup-v1/rdma.rst create mode 100644 Documentation/admin-guide/cgroup-v2.rst create mode 100644 Documentation/admin-guide/cifs/authors.rst create mode 100644 Documentation/admin-guide/cifs/changes.rst create mode 100644 Documentation/admin-guide/cifs/index.rst create mode 100644 Documentation/admin-guide/cifs/introduction.rst create mode 100644 Documentation/admin-guide/cifs/todo.rst create mode 100644 Documentation/admin-guide/cifs/usage.rst create mode 100755 Documentation/admin-guide/cifs/winucase_convert.pl create mode 100644 Documentation/admin-guide/clearing-warn-once.rst create mode 100644 Documentation/admin-guide/cpu-load.rst create mode 100644 Documentation/admin-guide/cputopology.rst create mode 100644 Documentation/admin-guide/dell_rbu.rst create mode 100644 Documentation/admin-guide/device-mapper/cache-policies.rst create mode 100644 Documentation/admin-guide/device-mapper/cache.rst create mode 100644 Documentation/admin-guide/device-mapper/delay.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-clone.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-crypt.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-dust.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-ebs.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-flakey.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-ima.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-init.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-integrity.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-io.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-log.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-queue-length.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-raid.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-service-time.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-uevent.rst create mode 100644 Documentation/admin-guide/device-mapper/dm-zoned.rst create mode 100644 Documentation/admin-guide/device-mapper/era.rst create mode 100644 Documentation/admin-guide/device-mapper/index.rst create mode 100644 Documentation/admin-guide/device-mapper/kcopyd.rst create mode 100644 Documentation/admin-guide/device-mapper/linear.rst create mode 100644 Documentation/admin-guide/device-mapper/log-writes.rst create mode 100644 Documentation/admin-guide/device-mapper/persistent-data.rst create mode 100644 Documentation/admin-guide/device-mapper/snapshot.rst create mode 100644 Documentation/admin-guide/device-mapper/statistics.rst create mode 100644 Documentation/admin-guide/device-mapper/striped.rst create mode 100644 Documentation/admin-guide/device-mapper/switch.rst create mode 100644 Documentation/admin-guide/device-mapper/thin-provisioning.rst create mode 100644 Documentation/admin-guide/device-mapper/unstriped.rst create mode 100644 Documentation/admin-guide/device-mapper/verity.rst create mode 100644 Documentation/admin-guide/device-mapper/writecache.rst create mode 100644 Documentation/admin-guide/device-mapper/zero.rst create mode 100644 Documentation/admin-guide/devices.rst create mode 100644 Documentation/admin-guide/devices.txt create mode 100644 Documentation/admin-guide/dynamic-debug-howto.rst create mode 100644 Documentation/admin-guide/edid.rst create mode 100644 Documentation/admin-guide/efi-stub.rst create mode 100644 Documentation/admin-guide/ext4.rst create mode 100644 Documentation/admin-guide/features.rst create mode 100644 Documentation/admin-guide/filesystem-monitoring.rst create mode 100644 Documentation/admin-guide/gpio/gpio-aggregator.rst create mode 100644 Documentation/admin-guide/gpio/gpio-mockup.rst create mode 100644 Documentation/admin-guide/gpio/gpio-sim.rst create mode 100644 Documentation/admin-guide/gpio/index.rst create mode 100644 Documentation/admin-guide/gpio/sysfs.rst create mode 100644 Documentation/admin-guide/highuid.rst create mode 100644 Documentation/admin-guide/hw-vuln/core-scheduling.rst create mode 100644 Documentation/admin-guide/hw-vuln/cross-thread-rsb.rst create mode 100644 Documentation/admin-guide/hw-vuln/gather_data_sampling.rst create mode 100644 Documentation/admin-guide/hw-vuln/index.rst create mode 100644 Documentation/admin-guide/hw-vuln/l1d_flush.rst create mode 100644 Documentation/admin-guide/hw-vuln/l1tf.rst create mode 100644 Documentation/admin-guide/hw-vuln/mds.rst create mode 100644 Documentation/admin-guide/hw-vuln/multihit.rst create mode 100644 Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst create mode 100644 Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst create mode 100644 Documentation/admin-guide/hw-vuln/spectre.rst create mode 100644 Documentation/admin-guide/hw-vuln/srso.rst create mode 100644 Documentation/admin-guide/hw-vuln/tsx_async_abort.rst create mode 100644 Documentation/admin-guide/hw_random.rst create mode 100644 Documentation/admin-guide/index.rst create mode 100644 Documentation/admin-guide/init.rst create mode 100644 Documentation/admin-guide/initrd.rst create mode 100644 Documentation/admin-guide/iostats.rst create mode 100644 Documentation/admin-guide/java.rst create mode 100644 Documentation/admin-guide/jfs.rst create mode 100644 Documentation/admin-guide/kdump/gdbmacros.txt create mode 100644 Documentation/admin-guide/kdump/index.rst create mode 100644 Documentation/admin-guide/kdump/kdump.rst create mode 100644 Documentation/admin-guide/kdump/vmcoreinfo.rst create mode 100644 Documentation/admin-guide/kernel-parameters.rst create mode 100644 Documentation/admin-guide/kernel-parameters.txt create mode 100644 Documentation/admin-guide/kernel-per-CPU-kthreads.rst create mode 100644 Documentation/admin-guide/laptops/asus-laptop.rst create mode 100644 Documentation/admin-guide/laptops/disk-shock-protection.rst create mode 100644 Documentation/admin-guide/laptops/index.rst create mode 100644 Documentation/admin-guide/laptops/laptop-mode.rst create mode 100644 Documentation/admin-guide/laptops/lg-laptop.rst create mode 100644 Documentation/admin-guide/laptops/sony-laptop.rst create mode 100644 Documentation/admin-guide/laptops/sonypi.rst create mode 100644 Documentation/admin-guide/laptops/thinkpad-acpi.rst create mode 100644 Documentation/admin-guide/laptops/toshiba_haps.rst create mode 100644 Documentation/admin-guide/lcd-panel-cgram.rst create mode 100644 Documentation/admin-guide/ldm.rst create mode 100644 Documentation/admin-guide/lockup-watchdogs.rst create mode 100644 Documentation/admin-guide/md.rst create mode 100644 Documentation/admin-guide/media/au0828-cardlist.rst create mode 100644 Documentation/admin-guide/media/avermedia.rst create mode 100644 Documentation/admin-guide/media/bt8xx.rst create mode 100644 Documentation/admin-guide/media/bttv-cardlist.rst create mode 100644 Documentation/admin-guide/media/bttv.rst create mode 100644 Documentation/admin-guide/media/building.rst create mode 100644 Documentation/admin-guide/media/cafe_ccic.rst create mode 100644 Documentation/admin-guide/media/cardlist.rst create mode 100644 Documentation/admin-guide/media/cec-drivers.rst create mode 100644 Documentation/admin-guide/media/ci.rst create mode 100644 Documentation/admin-guide/media/cpia2.rst create mode 100644 Documentation/admin-guide/media/cx18-cardlist.rst create mode 100644 Documentation/admin-guide/media/cx231xx-cardlist.rst create mode 100644 Documentation/admin-guide/media/cx23885-cardlist.rst create mode 100644 Documentation/admin-guide/media/cx88-cardlist.rst create mode 100644 Documentation/admin-guide/media/cx88.rst create mode 100644 Documentation/admin-guide/media/davinci-vpbe.rst create mode 100644 Documentation/admin-guide/media/dvb-drivers.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-a800-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-af9005-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-af9015-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-af9035-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-anysee-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-au6610-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-az6007-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-az6027-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-ce6230-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-cinergyT2-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-cxusb-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dib0700-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dibusb-mb-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dibusb-mc-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-digitv-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dtt200u-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dtv5100-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dvbsky-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-dw2102-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-ec168-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-gl861-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-gp8psk-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-lmedm04-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-m920x-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-mxl111sf-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-nova-t-usb2-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-opera1-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-pctv452e-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-rtl28xxu-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-technisat-usb2-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-ttusb2-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-umt-010-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-vp702x-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-vp7045-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb-usb-zd1301-cardlist.rst create mode 100644 Documentation/admin-guide/media/dvb.rst create mode 100644 Documentation/admin-guide/media/dvb_intro.rst create mode 100644 Documentation/admin-guide/media/dvb_references.rst create mode 100644 Documentation/admin-guide/media/em28xx-cardlist.rst create mode 100644 Documentation/admin-guide/media/faq.rst create mode 100644 Documentation/admin-guide/media/fimc.rst create mode 100644 Documentation/admin-guide/media/frontend-cardlist.rst create mode 100644 Documentation/admin-guide/media/gspca-cardlist.rst create mode 100644 Documentation/admin-guide/media/i2c-cardlist.rst create mode 100644 Documentation/admin-guide/media/imx.rst create mode 100644 Documentation/admin-guide/media/imx6q-sabreauto.dot create mode 100644 Documentation/admin-guide/media/imx6q-sabresd.dot create mode 100644 Documentation/admin-guide/media/imx7.rst create mode 100644 Documentation/admin-guide/media/index.rst create mode 100644 Documentation/admin-guide/media/intro.rst create mode 100644 Documentation/admin-guide/media/ipu3.rst create mode 100644 Documentation/admin-guide/media/ipu3_rcb.svg create mode 100644 Documentation/admin-guide/media/ivtv-cardlist.rst create mode 100644 Documentation/admin-guide/media/ivtv.rst create mode 100644 Documentation/admin-guide/media/lmedm04.rst create mode 100644 Documentation/admin-guide/media/meye.rst create mode 100644 Documentation/admin-guide/media/misc-cardlist.rst create mode 100644 Documentation/admin-guide/media/omap3isp.rst create mode 100644 Documentation/admin-guide/media/omap4_camera.rst create mode 100644 Documentation/admin-guide/media/opera-firmware.rst create mode 100644 Documentation/admin-guide/media/other-usb-cardlist.rst create mode 100644 Documentation/admin-guide/media/pci-cardlist.rst create mode 100644 Documentation/admin-guide/media/philips.rst create mode 100644 Documentation/admin-guide/media/platform-cardlist.rst create mode 100644 Documentation/admin-guide/media/pulse8-cec.rst create mode 100644 Documentation/admin-guide/media/qcom_camss.rst create mode 100644 Documentation/admin-guide/media/qcom_camss_8x96_graph.dot create mode 100644 Documentation/admin-guide/media/qcom_camss_graph.dot create mode 100644 Documentation/admin-guide/media/radio-cardlist.rst create mode 100644 Documentation/admin-guide/media/rcar-fdp1.rst create mode 100644 Documentation/admin-guide/media/remote-controller.rst create mode 100644 Documentation/admin-guide/media/rkisp1.dot create mode 100644 Documentation/admin-guide/media/rkisp1.rst create mode 100644 Documentation/admin-guide/media/saa7134-cardlist.rst create mode 100644 Documentation/admin-guide/media/saa7134.rst create mode 100644 Documentation/admin-guide/media/saa7164-cardlist.rst create mode 100644 Documentation/admin-guide/media/si470x.rst create mode 100644 Documentation/admin-guide/media/si4713.rst create mode 100644 Documentation/admin-guide/media/si476x.rst create mode 100644 Documentation/admin-guide/media/siano-cardlist.rst create mode 100644 Documentation/admin-guide/media/technisat.rst create mode 100644 Documentation/admin-guide/media/tm6000-cardlist.rst create mode 100644 Documentation/admin-guide/media/ttusb-dec.rst create mode 100644 Documentation/admin-guide/media/tuner-cardlist.rst create mode 100644 Documentation/admin-guide/media/usb-cardlist.rst create mode 100644 Documentation/admin-guide/media/v4l-drivers.rst create mode 100644 Documentation/admin-guide/media/vimc.dot create mode 100644 Documentation/admin-guide/media/vimc.rst create mode 100644 Documentation/admin-guide/media/vivid.rst create mode 100644 Documentation/admin-guide/media/zoran-cardlist.rst create mode 100644 Documentation/admin-guide/media/zr364xx.rst create mode 100644 Documentation/admin-guide/mm/cma_debugfs.rst create mode 100644 Documentation/admin-guide/mm/concepts.rst create mode 100644 Documentation/admin-guide/mm/damon/index.rst create mode 100644 Documentation/admin-guide/mm/damon/lru_sort.rst create mode 100644 Documentation/admin-guide/mm/damon/reclaim.rst create mode 100644 Documentation/admin-guide/mm/damon/start.rst create mode 100644 Documentation/admin-guide/mm/damon/usage.rst create mode 100644 Documentation/admin-guide/mm/hugetlbpage.rst create mode 100644 Documentation/admin-guide/mm/idle_page_tracking.rst create mode 100644 Documentation/admin-guide/mm/index.rst create mode 100644 Documentation/admin-guide/mm/ksm.rst create mode 100644 Documentation/admin-guide/mm/memory-hotplug.rst create mode 100644 Documentation/admin-guide/mm/multigen_lru.rst create mode 100644 Documentation/admin-guide/mm/nommu-mmap.rst create mode 100644 Documentation/admin-guide/mm/numa_memory_policy.rst create mode 100644 Documentation/admin-guide/mm/numaperf.rst create mode 100644 Documentation/admin-guide/mm/pagemap.rst create mode 100644 Documentation/admin-guide/mm/shrinker_debugfs.rst create mode 100644 Documentation/admin-guide/mm/soft-dirty.rst create mode 100644 Documentation/admin-guide/mm/swap_numa.rst create mode 100644 Documentation/admin-guide/mm/transhuge.rst create mode 100644 Documentation/admin-guide/mm/userfaultfd.rst create mode 100644 Documentation/admin-guide/mm/zswap.rst create mode 100644 Documentation/admin-guide/module-signing.rst create mode 100644 Documentation/admin-guide/mono.rst create mode 100644 Documentation/admin-guide/namespaces/compatibility-list.rst create mode 100644 Documentation/admin-guide/namespaces/index.rst create mode 100644 Documentation/admin-guide/namespaces/resource-control.rst create mode 100644 Documentation/admin-guide/nfs/index.rst create mode 100644 Documentation/admin-guide/nfs/nfs-client.rst create mode 100644 Documentation/admin-guide/nfs/nfs-idmapper.rst create mode 100644 Documentation/admin-guide/nfs/nfs-rdma.rst create mode 100644 Documentation/admin-guide/nfs/nfsd-admin-interfaces.rst create mode 100644 Documentation/admin-guide/nfs/nfsroot.rst create mode 100644 Documentation/admin-guide/nfs/pnfs-block-server.rst create mode 100644 Documentation/admin-guide/nfs/pnfs-scsi-server.rst create mode 100644 Documentation/admin-guide/numastat.rst create mode 100644 Documentation/admin-guide/parport.rst create mode 100644 Documentation/admin-guide/perf-security.rst create mode 100644 Documentation/admin-guide/perf/alibaba_pmu.rst create mode 100644 Documentation/admin-guide/perf/arm-ccn.rst create mode 100644 Documentation/admin-guide/perf/arm-cmn.rst create mode 100644 Documentation/admin-guide/perf/arm_dsu_pmu.rst create mode 100644 Documentation/admin-guide/perf/hisi-pcie-pmu.rst create mode 100644 Documentation/admin-guide/perf/hisi-pmu.rst create mode 100644 Documentation/admin-guide/perf/hns3-pmu.rst create mode 100644 Documentation/admin-guide/perf/imx-ddr.rst create mode 100644 Documentation/admin-guide/perf/index.rst create mode 100644 Documentation/admin-guide/perf/qcom_l2_pmu.rst create mode 100644 Documentation/admin-guide/perf/qcom_l3_pmu.rst create mode 100644 Documentation/admin-guide/perf/thunderx2-pmu.rst create mode 100644 Documentation/admin-guide/perf/xgene-pmu.rst create mode 100644 Documentation/admin-guide/pm/amd-pstate.rst create mode 100644 Documentation/admin-guide/pm/cpufreq.rst create mode 100644 Documentation/admin-guide/pm/cpufreq_drivers.rst create mode 100644 Documentation/admin-guide/pm/cpuidle.rst create mode 100644 Documentation/admin-guide/pm/index.rst create mode 100644 Documentation/admin-guide/pm/intel-speed-select.rst create mode 100644 Documentation/admin-guide/pm/intel_epb.rst create mode 100644 Documentation/admin-guide/pm/intel_idle.rst create mode 100644 Documentation/admin-guide/pm/intel_pstate.rst create mode 100644 Documentation/admin-guide/pm/intel_uncore_frequency_scaling.rst create mode 100644 Documentation/admin-guide/pm/sleep-states.rst create mode 100644 Documentation/admin-guide/pm/strategies.rst create mode 100644 Documentation/admin-guide/pm/suspend-flows.rst create mode 100644 Documentation/admin-guide/pm/system-wide.rst create mode 100644 Documentation/admin-guide/pm/working-state.rst create mode 100644 Documentation/admin-guide/pnp.rst create mode 100644 Documentation/admin-guide/pstore-blk.rst create mode 100644 Documentation/admin-guide/ramoops.rst create mode 100644 Documentation/admin-guide/rapidio.rst create mode 100644 Documentation/admin-guide/ras.rst create mode 100644 Documentation/admin-guide/reporting-issues.rst create mode 100644 Documentation/admin-guide/reporting-regressions.rst create mode 100644 Documentation/admin-guide/rtc.rst create mode 100644 Documentation/admin-guide/security-bugs.rst create mode 100644 Documentation/admin-guide/serial-console.rst create mode 100644 Documentation/admin-guide/spkguide.txt create mode 100644 Documentation/admin-guide/svga.rst create mode 100644 Documentation/admin-guide/syscall-user-dispatch.rst create mode 100644 Documentation/admin-guide/sysctl/abi.rst create mode 100644 Documentation/admin-guide/sysctl/fs.rst create mode 100644 Documentation/admin-guide/sysctl/index.rst create mode 100644 Documentation/admin-guide/sysctl/kernel.rst create mode 100644 Documentation/admin-guide/sysctl/net.rst create mode 100644 Documentation/admin-guide/sysctl/sunrpc.rst create mode 100644 Documentation/admin-guide/sysctl/user.rst create mode 100644 Documentation/admin-guide/sysctl/vm.rst create mode 100644 Documentation/admin-guide/sysfs-rules.rst create mode 100644 Documentation/admin-guide/sysrq.rst create mode 100644 Documentation/admin-guide/tainted-kernels.rst create mode 100644 Documentation/admin-guide/thunderbolt.rst create mode 100644 Documentation/admin-guide/ufs.rst create mode 100644 Documentation/admin-guide/unicode.rst create mode 100644 Documentation/admin-guide/vga-softcursor.rst create mode 100644 Documentation/admin-guide/video-output.rst create mode 100644 Documentation/admin-guide/xfs.rst create mode 100644 Documentation/arc/arc.rst create mode 100644 Documentation/arc/features.rst create mode 100644 Documentation/arc/index.rst create mode 100644 Documentation/arch.rst create mode 100644 Documentation/arm/arm.rst create mode 100644 Documentation/arm/booting.rst create mode 100644 Documentation/arm/cluster-pm-race-avoidance.rst create mode 100644 Documentation/arm/features.rst create mode 100644 Documentation/arm/firmware.rst create mode 100644 Documentation/arm/google/chromebook-boot-flow.rst create mode 100644 Documentation/arm/index.rst create mode 100644 Documentation/arm/interrupts.rst create mode 100644 Documentation/arm/ixp4xx.rst create mode 100644 Documentation/arm/kernel_mode_neon.rst create mode 100644 Documentation/arm/kernel_user_helpers.rst create mode 100644 Documentation/arm/keystone/knav-qmss.rst create mode 100644 Documentation/arm/keystone/overview.rst create mode 100644 Documentation/arm/marvell.rst create mode 100644 Documentation/arm/mem_alignment.rst create mode 100644 Documentation/arm/memory.rst create mode 100644 Documentation/arm/microchip.rst create mode 100644 Documentation/arm/netwinder.rst create mode 100644 Documentation/arm/nwfpe/index.rst create mode 100644 Documentation/arm/nwfpe/netwinder-fpe.rst create mode 100644 Documentation/arm/nwfpe/notes.rst create mode 100644 Documentation/arm/nwfpe/nwfpe.rst create mode 100644 Documentation/arm/nwfpe/todo.rst create mode 100644 Documentation/arm/omap/dss.rst create mode 100644 Documentation/arm/omap/index.rst create mode 100644 Documentation/arm/omap/omap.rst create mode 100644 Documentation/arm/omap/omap_pm.rst create mode 100644 Documentation/arm/porting.rst create mode 100644 Documentation/arm/pxa/mfp.rst create mode 100644 Documentation/arm/sa1100/assabet.rst create mode 100644 Documentation/arm/sa1100/cerf.rst create mode 100644 Documentation/arm/sa1100/index.rst create mode 100644 Documentation/arm/sa1100/lart.rst create mode 100644 Documentation/arm/sa1100/serial_uart.rst create mode 100644 Documentation/arm/samsung-s3c24xx/cpufreq.rst create mode 100644 Documentation/arm/samsung-s3c24xx/eb2410itx.rst create mode 100644 Documentation/arm/samsung-s3c24xx/gpio.rst create mode 100644 Documentation/arm/samsung-s3c24xx/h1940.rst create mode 100644 Documentation/arm/samsung-s3c24xx/index.rst create mode 100644 Documentation/arm/samsung-s3c24xx/nand.rst create mode 100644 Documentation/arm/samsung-s3c24xx/overview.rst create mode 100644 Documentation/arm/samsung-s3c24xx/s3c2412.rst create mode 100644 Documentation/arm/samsung-s3c24xx/s3c2413.rst create mode 100644 Documentation/arm/samsung-s3c24xx/smdk2440.rst create mode 100644 Documentation/arm/samsung-s3c24xx/suspend.rst create mode 100644 Documentation/arm/samsung-s3c24xx/usb-host.rst create mode 100644 Documentation/arm/samsung/bootloader-interface.rst create mode 100755 Documentation/arm/samsung/clksrc-change-registers.awk create mode 100644 Documentation/arm/samsung/gpio.rst create mode 100644 Documentation/arm/samsung/index.rst create mode 100644 Documentation/arm/samsung/overview.rst create mode 100644 Documentation/arm/setup.rst create mode 100644 Documentation/arm/spear/overview.rst create mode 100644 Documentation/arm/sti/overview.rst create mode 100644 Documentation/arm/sti/stih407-overview.rst create mode 100644 Documentation/arm/sti/stih415-overview.rst create mode 100644 Documentation/arm/sti/stih416-overview.rst create mode 100644 Documentation/arm/sti/stih418-overview.rst create mode 100644 Documentation/arm/stm32/overview.rst create mode 100644 Documentation/arm/stm32/stm32-dma-mdma-chaining.rst create mode 100644 Documentation/arm/stm32/stm32f429-overview.rst create mode 100644 Documentation/arm/stm32/stm32f746-overview.rst create mode 100644 Documentation/arm/stm32/stm32f769-overview.rst create mode 100644 Documentation/arm/stm32/stm32h743-overview.rst create mode 100644 Documentation/arm/stm32/stm32h750-overview.rst create mode 100644 Documentation/arm/stm32/stm32mp13-overview.rst create mode 100644 Documentation/arm/stm32/stm32mp157-overview.rst create mode 100644 Documentation/arm/sunxi.rst create mode 100644 Documentation/arm/sunxi/clocks.rst create mode 100644 Documentation/arm/swp_emulation.rst create mode 100644 Documentation/arm/tcm.rst create mode 100644 Documentation/arm/uefi.rst create mode 100644 Documentation/arm/vfp/release-notes.rst create mode 100644 Documentation/arm/vlocks.rst create mode 100644 Documentation/arm64/acpi_object_usage.rst create mode 100644 Documentation/arm64/amu.rst create mode 100644 Documentation/arm64/arm-acpi.rst create mode 100644 Documentation/arm64/asymmetric-32bit.rst create mode 100644 Documentation/arm64/booting.rst create mode 100644 Documentation/arm64/cpu-feature-registers.rst create mode 100644 Documentation/arm64/elf_hwcaps.rst create mode 100644 Documentation/arm64/features.rst create mode 100644 Documentation/arm64/hugetlbpage.rst create mode 100644 Documentation/arm64/index.rst create mode 100644 Documentation/arm64/kasan-offsets.sh create mode 100644 Documentation/arm64/legacy_instructions.rst create mode 100644 Documentation/arm64/memory-tagging-extension.rst create mode 100644 Documentation/arm64/memory.rst create mode 100644 Documentation/arm64/perf.rst create mode 100644 Documentation/arm64/pointer-authentication.rst create mode 100644 Documentation/arm64/silicon-errata.rst create mode 100644 Documentation/arm64/sme.rst create mode 100644 Documentation/arm64/sve.rst create mode 100644 Documentation/arm64/tagged-address-abi.rst create mode 100644 Documentation/arm64/tagged-pointers.rst create mode 100644 Documentation/atomic_bitops.txt create mode 100644 Documentation/atomic_t.txt create mode 100644 Documentation/block/bfq-iosched.rst create mode 100644 Documentation/block/biovecs.rst create mode 100644 Documentation/block/blk-mq.rst create mode 100644 Documentation/block/capability.rst create mode 100644 Documentation/block/cmdline-partition.rst create mode 100644 Documentation/block/data-integrity.rst create mode 100644 Documentation/block/deadline-iosched.rst create mode 100644 Documentation/block/index.rst create mode 100644 Documentation/block/inline-encryption.rst create mode 100644 Documentation/block/ioprio.rst create mode 100644 Documentation/block/kyber-iosched.rst create mode 100644 Documentation/block/null_blk.rst create mode 100644 Documentation/block/pr.rst create mode 100644 Documentation/block/request.rst create mode 100644 Documentation/block/stat.rst create mode 100644 Documentation/block/switching-sched.rst create mode 100644 Documentation/block/ublk.rst create mode 100644 Documentation/block/writeback_cache_control.rst create mode 100644 Documentation/bpf/bpf_design_QA.rst create mode 100644 Documentation/bpf/bpf_devel_QA.rst create mode 100644 Documentation/bpf/bpf_licensing.rst create mode 100644 Documentation/bpf/bpf_prog_run.rst create mode 100644 Documentation/bpf/btf.rst create mode 100644 Documentation/bpf/clang-notes.rst create mode 100644 Documentation/bpf/classic_vs_extended.rst create mode 100644 Documentation/bpf/drgn.rst create mode 100644 Documentation/bpf/faq.rst create mode 100644 Documentation/bpf/helpers.rst create mode 100644 Documentation/bpf/index.rst create mode 100644 Documentation/bpf/instruction-set.rst create mode 100644 Documentation/bpf/kfuncs.rst create mode 100644 Documentation/bpf/libbpf/index.rst create mode 100644 Documentation/bpf/libbpf/libbpf_build.rst create mode 100644 Documentation/bpf/libbpf/libbpf_naming_convention.rst create mode 100644 Documentation/bpf/linux-notes.rst create mode 100644 Documentation/bpf/llvm_reloc.rst create mode 100644 Documentation/bpf/map_cgroup_storage.rst create mode 100644 Documentation/bpf/map_hash.rst create mode 100644 Documentation/bpf/maps.rst create mode 100644 Documentation/bpf/other.rst create mode 100644 Documentation/bpf/prog_cgroup_sockopt.rst create mode 100644 Documentation/bpf/prog_cgroup_sysctl.rst create mode 100644 Documentation/bpf/prog_flow_dissector.rst create mode 100644 Documentation/bpf/prog_lsm.rst create mode 100644 Documentation/bpf/prog_sk_lookup.rst create mode 100644 Documentation/bpf/programs.rst create mode 100644 Documentation/bpf/ringbuf.rst create mode 100644 Documentation/bpf/s390.rst create mode 100644 Documentation/bpf/syscall_api.rst create mode 100644 Documentation/bpf/test_debug.rst create mode 100644 Documentation/bpf/verifier.rst create mode 100644 Documentation/cdrom/cdrom-standard.rst create mode 100644 Documentation/cdrom/index.rst create mode 100644 Documentation/cdrom/packet-writing.rst create mode 100644 Documentation/conf.py create mode 100644 Documentation/core-api/asm-annotations.rst create mode 100644 Documentation/core-api/assoc_array.rst create mode 100644 Documentation/core-api/boot-time-mm.rst create mode 100644 Documentation/core-api/cachetlb.rst create mode 100644 Documentation/core-api/circular-buffers.rst create mode 100644 Documentation/core-api/cpu_hotplug.rst create mode 100644 Documentation/core-api/debug-objects.rst create mode 100644 Documentation/core-api/debugging-via-ohci1394.rst create mode 100644 Documentation/core-api/dma-api-howto.rst create mode 100644 Documentation/core-api/dma-api.rst create mode 100644 Documentation/core-api/dma-attributes.rst create mode 100644 Documentation/core-api/dma-isa-lpc.rst create mode 100644 Documentation/core-api/entry.rst create mode 100644 Documentation/core-api/errseq.rst create mode 100644 Documentation/core-api/genalloc.rst create mode 100644 Documentation/core-api/generic-radix-tree.rst create mode 100644 Documentation/core-api/genericirq.rst create mode 100644 Documentation/core-api/gfp_mask-from-fs-io.rst create mode 100644 Documentation/core-api/idr.rst create mode 100644 Documentation/core-api/index.rst create mode 100644 Documentation/core-api/irq/concepts.rst create mode 100644 Documentation/core-api/irq/index.rst create mode 100644 Documentation/core-api/irq/irq-affinity.rst create mode 100644 Documentation/core-api/irq/irq-domain.rst create mode 100644 Documentation/core-api/irq/irqflags-tracing.rst create mode 100644 Documentation/core-api/kernel-api.rst create mode 100644 Documentation/core-api/kobject.rst create mode 100644 Documentation/core-api/kref.rst create mode 100644 Documentation/core-api/librs.rst create mode 100644 Documentation/core-api/local_ops.rst create mode 100644 Documentation/core-api/maple_tree.rst create mode 100644 Documentation/core-api/memory-allocation.rst create mode 100644 Documentation/core-api/memory-hotplug.rst create mode 100644 Documentation/core-api/mm-api.rst create mode 100644 Documentation/core-api/packing.rst create mode 100644 Documentation/core-api/padata.rst create mode 100644 Documentation/core-api/pin_user_pages.rst create mode 100644 Documentation/core-api/printk-basics.rst create mode 100644 Documentation/core-api/printk-formats.rst create mode 100644 Documentation/core-api/printk-index.rst create mode 100644 Documentation/core-api/protection-keys.rst create mode 100644 Documentation/core-api/rbtree.rst create mode 100644 Documentation/core-api/refcount-vs-atomic.rst create mode 100644 Documentation/core-api/symbol-namespaces.rst create mode 100644 Documentation/core-api/this_cpu_ops.rst create mode 100644 Documentation/core-api/timekeeping.rst create mode 100644 Documentation/core-api/tracepoint.rst create mode 100644 Documentation/core-api/unaligned-memory-access.rst create mode 100644 Documentation/core-api/watch_queue.rst create mode 100644 Documentation/core-api/workqueue.rst create mode 100644 Documentation/core-api/wrappers/atomic_bitops.rst create mode 100644 Documentation/core-api/wrappers/atomic_t.rst create mode 100644 Documentation/core-api/wrappers/memory-barriers.rst create mode 100644 Documentation/core-api/xarray.rst create mode 100644 Documentation/cpu-freq/core.rst create mode 100644 Documentation/cpu-freq/cpu-drivers.rst create mode 100644 Documentation/cpu-freq/cpufreq-stats.rst create mode 100644 Documentation/cpu-freq/index.rst create mode 100644 Documentation/crypto/api-aead.rst create mode 100644 Documentation/crypto/api-akcipher.rst create mode 100644 Documentation/crypto/api-digest.rst create mode 100644 Documentation/crypto/api-intro.rst create mode 100644 Documentation/crypto/api-kpp.rst create mode 100644 Documentation/crypto/api-rng.rst create mode 100644 Documentation/crypto/api-samples.rst create mode 100644 Documentation/crypto/api-skcipher.rst create mode 100644 Documentation/crypto/api.rst create mode 100644 Documentation/crypto/architecture.rst create mode 100644 Documentation/crypto/asymmetric-keys.rst create mode 100644 Documentation/crypto/async-tx-api.rst create mode 100644 Documentation/crypto/crypto_engine.rst create mode 100644 Documentation/crypto/descore-readme.rst create mode 100644 Documentation/crypto/devel-algos.rst create mode 100644 Documentation/crypto/index.rst create mode 100644 Documentation/crypto/intro.rst create mode 100644 Documentation/crypto/userspace-if.rst create mode 100644 Documentation/dev-tools/checkpatch.rst create mode 100644 Documentation/dev-tools/coccinelle.rst create mode 100644 Documentation/dev-tools/gcov.rst create mode 100644 Documentation/dev-tools/gdb-kernel-debugging.rst create mode 100644 Documentation/dev-tools/index.rst create mode 100644 Documentation/dev-tools/kasan.rst create mode 100644 Documentation/dev-tools/kcov.rst create mode 100644 Documentation/dev-tools/kcsan.rst create mode 100644 Documentation/dev-tools/kfence.rst create mode 100644 Documentation/dev-tools/kgdb.rst create mode 100644 Documentation/dev-tools/kmemleak.rst create mode 100644 Documentation/dev-tools/kmsan.rst create mode 100644 Documentation/dev-tools/kselftest.rst create mode 100644 Documentation/dev-tools/ktap.rst create mode 100644 Documentation/dev-tools/kunit/api/index.rst create mode 100644 Documentation/dev-tools/kunit/api/resource.rst create mode 100644 Documentation/dev-tools/kunit/api/test.rst create mode 100644 Documentation/dev-tools/kunit/architecture.rst create mode 100644 Documentation/dev-tools/kunit/faq.rst create mode 100644 Documentation/dev-tools/kunit/index.rst create mode 100644 Documentation/dev-tools/kunit/kunit_suitememorydiagram.svg create mode 100644 Documentation/dev-tools/kunit/run_manual.rst create mode 100644 Documentation/dev-tools/kunit/run_wrapper.rst create mode 100644 Documentation/dev-tools/kunit/running_tips.rst create mode 100644 Documentation/dev-tools/kunit/start.rst create mode 100644 Documentation/dev-tools/kunit/style.rst create mode 100644 Documentation/dev-tools/kunit/tips.rst create mode 100644 Documentation/dev-tools/kunit/usage.rst create mode 100644 Documentation/dev-tools/sparse.rst create mode 100644 Documentation/dev-tools/testing-overview.rst create mode 100644 Documentation/dev-tools/ubsan.rst create mode 100644 Documentation/devicetree/bindings/.gitignore create mode 100644 Documentation/devicetree/bindings/.yamllint create mode 100644 Documentation/devicetree/bindings/ABI.rst create mode 100644 Documentation/devicetree/bindings/Makefile create mode 100644 Documentation/devicetree/bindings/arc/archs-pct.txt create mode 100644 Documentation/devicetree/bindings/arc/axs101.txt create mode 100644 Documentation/devicetree/bindings/arc/axs103.txt create mode 100644 Documentation/devicetree/bindings/arc/eznps.txt create mode 100644 Documentation/devicetree/bindings/arc/hsdk.txt create mode 100644 Documentation/devicetree/bindings/arc/pct.txt create mode 100644 Documentation/devicetree/bindings/arm/actions.yaml create mode 100644 Documentation/devicetree/bindings/arm/airoha.yaml create mode 100644 Documentation/devicetree/bindings/arm/altera.yaml create mode 100644 Documentation/devicetree/bindings/arm/altera/socfpga-clk-manager.yaml create mode 100644 Documentation/devicetree/bindings/arm/altera/socfpga-sdram-controller.txt create mode 100644 Documentation/devicetree/bindings/arm/altera/socfpga-sdram-edac.txt create mode 100644 Documentation/devicetree/bindings/arm/altera/socfpga-system.txt create mode 100644 Documentation/devicetree/bindings/arm/amazon,al.yaml create mode 100644 Documentation/devicetree/bindings/arm/amlogic.yaml create mode 100644 Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml create mode 100644 Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-mx-secbus2.yaml create mode 100644 Documentation/devicetree/bindings/arm/amlogic/analog-top.txt create mode 100644 Documentation/devicetree/bindings/arm/amlogic/assist.txt create mode 100644 Documentation/devicetree/bindings/arm/amlogic/bootrom.txt create mode 100644 Documentation/devicetree/bindings/arm/amlogic/pmu.txt create mode 100644 Documentation/devicetree/bindings/arm/apm/scu.txt create mode 100644 Documentation/devicetree/bindings/arm/apple.yaml create mode 100644 Documentation/devicetree/bindings/arm/apple/apple,pmgr.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,cci-400.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-catu.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-cpu-debug.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-dynamic-funnel.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-dynamic-replicator.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-etb10.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-etm.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-static-funnel.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-static-replicator.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-stm.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-tmc.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-tpiu.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,embedded-trace-extension.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,integrator.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,realview.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,scu.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,trace-buffer-extension.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,versatile-sysreg.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,versatile.yaml create mode 100644 Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml create mode 100644 Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml create mode 100644 Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml create mode 100644 Documentation/devicetree/bindings/arm/atmel-at91.yaml create mode 100644 Documentation/devicetree/bindings/arm/atmel-sysregs.txt create mode 100644 Documentation/devicetree/bindings/arm/axis.txt create mode 100644 Documentation/devicetree/bindings/arm/axxia.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/bcm2835.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm11351.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm21664.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,cygnus.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,hr2.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,ns2.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,nsp.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,stingray.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,vulcan-soc.yaml create mode 100644 Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml create mode 100644 Documentation/devicetree/bindings/arm/bitmain.yaml create mode 100644 Documentation/devicetree/bindings/arm/calxeda.yaml create mode 100644 Documentation/devicetree/bindings/arm/calxeda/hb-sregs.yaml create mode 100644 Documentation/devicetree/bindings/arm/calxeda/l2ecc.yaml create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder.txt create mode 100644 Documentation/devicetree/bindings/arm/cavium-thunder2.txt create mode 100644 Documentation/devicetree/bindings/arm/cci-control-port.yaml create mode 100644 Documentation/devicetree/bindings/arm/cpu-capacity.txt create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/al,alpine-smp create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/marvell,berlin-smp create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/nuvoton,npcm750-smp create mode 100644 Documentation/devicetree/bindings/arm/cpus.yaml create mode 100644 Documentation/devicetree/bindings/arm/digicolor.yaml create mode 100644 Documentation/devicetree/bindings/arm/firmware/linaro,optee-tz.yaml create mode 100644 Documentation/devicetree/bindings/arm/firmware/sdei.txt create mode 100644 Documentation/devicetree/bindings/arm/firmware/tlm,trusted-foundations.yaml create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx7ulp-pm.yaml create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx7ulp-sim.yaml create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-cpucfg.txt create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-ir.txt create mode 100644 Documentation/devicetree/bindings/arm/freescale/m4if.txt create mode 100644 Documentation/devicetree/bindings/arm/freescale/tigerp.txt create mode 100644 Documentation/devicetree/bindings/arm/fsl.yaml create mode 100644 Documentation/devicetree/bindings/arm/gemini.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/cpuctrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/hi3798cv200-perictrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/hi6220-domain-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/hip04-bootwrapper.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/hip04-fabric.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/pctrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/controller/sysctrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/hisilicon.yaml create mode 100644 Documentation/devicetree/bindings/arm/hisilicon/low-pin-count.yaml create mode 100644 Documentation/devicetree/bindings/arm/hpe,gxp.yaml create mode 100644 Documentation/devicetree/bindings/arm/intel,keembay.yaml create mode 100644 Documentation/devicetree/bindings/arm/intel,socfpga.yaml create mode 100644 Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml create mode 100644 Documentation/devicetree/bindings/arm/keystone/keystone.txt create mode 100644 Documentation/devicetree/bindings/arm/keystone/ti,k3-sci-common.yaml create mode 100644 Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml create mode 100644 Documentation/devicetree/bindings/arm/l2c2x0.yaml create mode 100644 Documentation/devicetree/bindings/arm/linux,dummy-virt.yaml create mode 100644 Documentation/devicetree/bindings/arm/marvell/98dx3236-resume-ctrl.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/98dx3236.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-370-xp-pmsu.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-370-xp.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-375.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-37xx.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-37xx.yaml create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-380-mpcore-soc-ctrl.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-38x.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-39x.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-8kp.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-cpu-reset.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/coherency-fabric.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/cp110-system-controller.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/kirkwood.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/marvell,ac5.yaml create mode 100644 Documentation/devicetree/bindings/arm/marvell/marvell,dove.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/marvell,kirkwood.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/mvebu-cpu-config.txt create mode 100644 Documentation/devicetree/bindings/arm/marvell/mvebu-system-controller.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,bdpsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,camsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,ethsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,imgsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,infracfg.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,ipesys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,ipu.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,jpgdecsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mcucfg.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mfgcfg.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mipi0a.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-pcie-mirror.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7622-wed.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt7986-wed-pcie.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8186-sys-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8192-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8192-sys-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-sys-clock.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,pciesys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,sgmiisys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,ssusbsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vcodecsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vdecsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencltsys.txt create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,vencsys.txt create mode 100644 Documentation/devicetree/bindings/arm/microchip,sparx5.yaml create mode 100644 Documentation/devicetree/bindings/arm/moxart.yaml create mode 100644 Documentation/devicetree/bindings/arm/mrvl/feroceon.txt create mode 100644 Documentation/devicetree/bindings/arm/mrvl/mrvl.yaml create mode 100644 Documentation/devicetree/bindings/arm/mrvl/tauros2.txt create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,idle-state.txt create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,kpss-acc.txt create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,kpss-gcc.txt create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt create mode 100644 Documentation/devicetree/bindings/arm/msm/ssbi.txt create mode 100644 Documentation/devicetree/bindings/arm/mstar/mstar,l3bridge.yaml create mode 100644 Documentation/devicetree/bindings/arm/mstar/mstar,smpctrl.yaml create mode 100644 Documentation/devicetree/bindings/arm/mstar/mstar.yaml create mode 100644 Documentation/devicetree/bindings/arm/npcm/npcm.yaml create mode 100644 Documentation/devicetree/bindings/arm/npcm/nuvoton,gcr.yaml create mode 100644 Documentation/devicetree/bindings/arm/nvidia,tegra194-ccplex.yaml create mode 100644 Documentation/devicetree/bindings/arm/nxp/lpc32xx.yaml create mode 100644 Documentation/devicetree/bindings/arm/omap/counter.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/crossbar.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/ctrl.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/dmm.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/dsp.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/iva.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/l3-noc.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/l4.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/mpu.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/omap.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/prcm.txt create mode 100644 Documentation/devicetree/bindings/arm/omap/prm-inst.txt create mode 100644 Documentation/devicetree/bindings/arm/oxnas.txt create mode 100644 Documentation/devicetree/bindings/arm/pmu.yaml create mode 100644 Documentation/devicetree/bindings/arm/primecell.yaml create mode 100644 Documentation/devicetree/bindings/arm/psci.yaml create mode 100644 Documentation/devicetree/bindings/arm/qcom.yaml create mode 100644 Documentation/devicetree/bindings/arm/rda.yaml create mode 100644 Documentation/devicetree/bindings/arm/realtek.yaml create mode 100644 Documentation/devicetree/bindings/arm/renesas.yaml create mode 100644 Documentation/devicetree/bindings/arm/rockchip.yaml create mode 100644 Documentation/devicetree/bindings/arm/rockchip/pmu.yaml create mode 100644 Documentation/devicetree/bindings/arm/rtsm-dcscb.txt create mode 100644 Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml create mode 100644 Documentation/devicetree/bindings/arm/samsung/samsung-secure-firmware.yaml create mode 100644 Documentation/devicetree/bindings/arm/samsung/samsung-soc.yaml create mode 100644 Documentation/devicetree/bindings/arm/secure.txt create mode 100644 Documentation/devicetree/bindings/arm/socionext/milbeaut.yaml create mode 100644 Documentation/devicetree/bindings/arm/socionext/socionext,uniphier-system-cache.yaml create mode 100644 Documentation/devicetree/bindings/arm/socionext/uniphier.yaml create mode 100644 Documentation/devicetree/bindings/arm/sp810.yaml create mode 100644 Documentation/devicetree/bindings/arm/spear-misc.txt create mode 100644 Documentation/devicetree/bindings/arm/spear.yaml create mode 100644 Documentation/devicetree/bindings/arm/sprd/sprd.yaml create mode 100644 Documentation/devicetree/bindings/arm/ste-nomadik.txt create mode 100644 Documentation/devicetree/bindings/arm/sti.yaml create mode 100644 Documentation/devicetree/bindings/arm/stm32/st,mlahb.yaml create mode 100644 Documentation/devicetree/bindings/arm/stm32/st,stm32-syscon.yaml create mode 100644 Documentation/devicetree/bindings/arm/stm32/stm32.yaml create mode 100644 Documentation/devicetree/bindings/arm/sunplus,sp7021.yaml create mode 100644 Documentation/devicetree/bindings/arm/sunxi.yaml create mode 100644 Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml create mode 100644 Documentation/devicetree/bindings/arm/sunxi/allwinner,sun6i-a31-cpuconfig.yaml create mode 100644 Documentation/devicetree/bindings/arm/sunxi/allwinner,sun9i-a80-prcm.yaml create mode 100644 Documentation/devicetree/bindings/arm/swir.txt create mode 100644 Documentation/devicetree/bindings/arm/syna.txt create mode 100644 Documentation/devicetree/bindings/arm/tegra.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,nvec.txt create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra-ccplex-cluster.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-cbb.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-ahb.txt create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-flowctrl.txt create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-pmc.yaml create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra234-cbb.yaml create mode 100644 Documentation/devicetree/bindings/arm/tesla.yaml create mode 100644 Documentation/devicetree/bindings/arm/ti/k3.yaml create mode 100644 Documentation/devicetree/bindings/arm/ti/nspire.yaml create mode 100644 Documentation/devicetree/bindings/arm/ti/ti,davinci.yaml create mode 100644 Documentation/devicetree/bindings/arm/toshiba.yaml create mode 100644 Documentation/devicetree/bindings/arm/ux500.yaml create mode 100644 Documentation/devicetree/bindings/arm/ux500/boards.txt create mode 100644 Documentation/devicetree/bindings/arm/ux500/power_domain.txt create mode 100644 Documentation/devicetree/bindings/arm/vexpress-config.yaml create mode 100644 Documentation/devicetree/bindings/arm/vexpress-scc.txt create mode 100644 Documentation/devicetree/bindings/arm/vexpress-sysreg.yaml create mode 100644 Documentation/devicetree/bindings/arm/vt8500.yaml create mode 100644 Documentation/devicetree/bindings/arm/vt8500/via,vt8500-pmc.txt create mode 100644 Documentation/devicetree/bindings/arm/xen.txt create mode 100644 Documentation/devicetree/bindings/arm/xilinx.yaml create mode 100644 Documentation/devicetree/bindings/ata/ahci-common.yaml create mode 100644 Documentation/devicetree/bindings/ata/ahci-da850.txt create mode 100644 Documentation/devicetree/bindings/ata/ahci-dm816.txt create mode 100644 Documentation/devicetree/bindings/ata/ahci-fsl-qoriq.txt create mode 100644 Documentation/devicetree/bindings/ata/ahci-mtk.txt create mode 100644 Documentation/devicetree/bindings/ata/ahci-platform.yaml create mode 100644 Documentation/devicetree/bindings/ata/ahci-st.txt create mode 100644 Documentation/devicetree/bindings/ata/allwinner,sun4i-a10-ahci.yaml create mode 100644 Documentation/devicetree/bindings/ata/allwinner,sun8i-r40-ahci.yaml create mode 100644 Documentation/devicetree/bindings/ata/apm-xgene.txt create mode 100644 Documentation/devicetree/bindings/ata/atmel-at91_cf.txt create mode 100644 Documentation/devicetree/bindings/ata/baikal,bt1-ahci.yaml create mode 100644 Documentation/devicetree/bindings/ata/brcm,sata-brcm.yaml create mode 100644 Documentation/devicetree/bindings/ata/cavium-compact-flash.txt create mode 100644 Documentation/devicetree/bindings/ata/ceva,ahci-1v84.yaml create mode 100644 Documentation/devicetree/bindings/ata/cortina,gemini-sata-bridge.yaml create mode 100644 Documentation/devicetree/bindings/ata/faraday,ftide010.yaml create mode 100644 Documentation/devicetree/bindings/ata/fsl-sata.txt create mode 100644 Documentation/devicetree/bindings/ata/imx-pata.txt create mode 100644 Documentation/devicetree/bindings/ata/imx-sata.yaml create mode 100644 Documentation/devicetree/bindings/ata/intel,ixp4xx-compact-flash.yaml create mode 100644 Documentation/devicetree/bindings/ata/marvell.txt create mode 100644 Documentation/devicetree/bindings/ata/nvidia,tegra-ahci.yaml create mode 100644 Documentation/devicetree/bindings/ata/pata-arasan.txt create mode 100644 Documentation/devicetree/bindings/ata/pata-common.yaml create mode 100644 Documentation/devicetree/bindings/ata/qcom-sata.txt create mode 100644 Documentation/devicetree/bindings/ata/renesas,rcar-sata.yaml create mode 100644 Documentation/devicetree/bindings/ata/sata-common.yaml create mode 100644 Documentation/devicetree/bindings/ata/sata_highbank.yaml create mode 100644 Documentation/devicetree/bindings/ata/snps,dwc-ahci-common.yaml create mode 100644 Documentation/devicetree/bindings/ata/snps,dwc-ahci.yaml create mode 100644 Documentation/devicetree/bindings/auxdisplay/arm,versatile-lcd.yaml create mode 100644 Documentation/devicetree/bindings/auxdisplay/hit,hd44780.yaml create mode 100644 Documentation/devicetree/bindings/auxdisplay/holtek,ht16k33.yaml create mode 100644 Documentation/devicetree/bindings/auxdisplay/img,ascii-lcd.yaml create mode 100644 Documentation/devicetree/bindings/auxdisplay/modtronix,lcd2s.yaml create mode 100644 Documentation/devicetree/bindings/board/fsl-board.txt create mode 100644 Documentation/devicetree/bindings/bus/allwinner,sun50i-a64-de2.yaml create mode 100644 Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml create mode 100644 Documentation/devicetree/bindings/bus/arm,integrator-ap-lm.yaml create mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-apb.yaml create mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-axi.yaml create mode 100644 Documentation/devicetree/bindings/bus/brcm,bus-axi.txt create mode 100644 Documentation/devicetree/bindings/bus/brcm,gisb-arb.yaml create mode 100644 Documentation/devicetree/bindings/bus/fsl,spba-bus.yaml create mode 100644 Documentation/devicetree/bindings/bus/imx-weim.txt create mode 100644 Documentation/devicetree/bindings/bus/intel,ixp4xx-expansion-bus-controller.yaml create mode 100644 Documentation/devicetree/bindings/bus/moxtet.txt create mode 100644 Documentation/devicetree/bindings/bus/mti,mips-cdmm.yaml create mode 100644 Documentation/devicetree/bindings/bus/mvebu-mbus.txt create mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra20-gmi.txt create mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.yaml create mode 100644 Documentation/devicetree/bindings/bus/omap-ocp2scp.txt create mode 100644 Documentation/devicetree/bindings/bus/palmbus.yaml create mode 100644 Documentation/devicetree/bindings/bus/qcom,ebi2.txt create mode 100644 Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml create mode 100644 Documentation/devicetree/bindings/bus/renesas,bsc.yaml create mode 100644 Documentation/devicetree/bindings/bus/simple-pm-bus.yaml create mode 100644 Documentation/devicetree/bindings/bus/socionext,uniphier-system-bus.yaml create mode 100644 Documentation/devicetree/bindings/bus/ti,da850-mstpri.txt create mode 100644 Documentation/devicetree/bindings/bus/ti-sysc.yaml create mode 100644 Documentation/devicetree/bindings/bus/ts-nbus.txt create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-ec-typec.yaml create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-kbd-led-backlight.yaml create mode 100644 Documentation/devicetree/bindings/clock/actions,owl-cmu.txt create mode 100644 Documentation/devicetree/bindings/clock/adi,axi-clkgen.yaml create mode 100644 Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-apb0-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-apb1-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-axi-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ccu.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-cpu-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-display-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-gates-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-mbus-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-mmc-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-mod0-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-mod1-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-osc-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-pll1-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-pll3-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-pll5-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-pll6-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-tcon-ch0-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-usb-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ve-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun5i-a13-ahb-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun6i-a31-pll6-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun7i-a20-gmac-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun7i-a20-out-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun8i-a83t-de2-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun8i-h3-bus-gates-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-ahb-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-apb0-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-cpus-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-de-clks.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-gt-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-mmc-config-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-pll4-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-usb-clks.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-usb-mod-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-usb-phy-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/alphascale,acc.txt create mode 100644 Documentation/devicetree/bindings/clock/altr_socfpga.txt create mode 100644 Documentation/devicetree/bindings/clock/amlogic,axg-audio-clkc.txt create mode 100644 Documentation/devicetree/bindings/clock/amlogic,gxbb-aoclkc.txt create mode 100644 Documentation/devicetree/bindings/clock/amlogic,gxbb-clkc.txt create mode 100644 Documentation/devicetree/bindings/clock/amlogic,meson8-ddr-clkc.yaml create mode 100644 Documentation/devicetree/bindings/clock/amlogic,meson8b-clkc.txt create mode 100644 Documentation/devicetree/bindings/clock/apple,nco.yaml create mode 100644 Documentation/devicetree/bindings/clock/arm,syscon-icst.yaml create mode 100644 Documentation/devicetree/bindings/clock/armada3700-periph-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/armada3700-tbg-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/armada3700-xtal-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/artpec6.txt create mode 100644 Documentation/devicetree/bindings/clock/at91-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/axs10x-i2s-pll-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/baikal,bt1-ccu-div.yaml create mode 100644 Documentation/devicetree/bindings/clock/baikal,bt1-ccu-pll.yaml create mode 100644 Documentation/devicetree/bindings/clock/bitmain,bm1880-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm2711-dvp.yaml create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm2835-aux-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm2835-cprman.txt create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm53573-ilp.txt create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm63xx-clocks.txt create mode 100644 Documentation/devicetree/bindings/clock/brcm,iproc-clocks.yaml create mode 100644 Documentation/devicetree/bindings/clock/brcm,kona-ccu.txt create mode 100644 Documentation/devicetree/bindings/clock/calxeda.yaml create mode 100644 Documentation/devicetree/bindings/clock/canaan,k210-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/cirrus,cs2000-cp.yaml create mode 100644 Documentation/devicetree/bindings/clock/cirrus,lochnagar.yaml create mode 100644 Documentation/devicetree/bindings/clock/clk-palmas-clk32kg-clocks.txt create mode 100644 Documentation/devicetree/bindings/clock/clock-bindings.txt create mode 100644 Documentation/devicetree/bindings/clock/clps711x-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/dove-divider-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/fixed-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/fixed-mmio-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/fsl,flexspi-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/fsl,plldig.yaml create mode 100644 Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/fsl,scu-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/fujitsu,mb86s70-crg11.txt create mode 100644 Documentation/devicetree/bindings/clock/gpio-gate-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/gpio-mux-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/hi3620-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/hi3660-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/hi3670-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/hi6220-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/hisi-crg.txt create mode 100644 Documentation/devicetree/bindings/clock/hisilicon,hi3559av100-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/hix5hd2-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/idt,versaclock5.yaml create mode 100644 Documentation/devicetree/bindings/clock/img,boston-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/imx1-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx21-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx23-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx25-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx27-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx28-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx31-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx35-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx5-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx6q-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx6sl-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx6sll-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx6sx-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx6ul-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx7d-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx7ulp-pcc-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx7ulp-scg-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx8m-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx8qxp-lpcg.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx8ulp-cgc-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx8ulp-pcc-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imx93-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/imxrt1050-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/ingenic,cgu.yaml create mode 100644 Documentation/devicetree/bindings/clock/intel,agilex.yaml create mode 100644 Documentation/devicetree/bindings/clock/intel,cgu-lgm.yaml create mode 100644 Documentation/devicetree/bindings/clock/intel,easic-n5x.yaml create mode 100644 Documentation/devicetree/bindings/clock/intel,stratix10.yaml create mode 100644 Documentation/devicetree/bindings/clock/keystone-gate.txt create mode 100644 Documentation/devicetree/bindings/clock/keystone-pll.txt create mode 100644 Documentation/devicetree/bindings/clock/lpc1850-ccu.txt create mode 100644 Documentation/devicetree/bindings/clock/lpc1850-cgu.txt create mode 100644 Documentation/devicetree/bindings/clock/lpc1850-creg-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/lsi,axm5516-clks.txt create mode 100644 Documentation/devicetree/bindings/clock/marvell,armada-3700-uart-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/marvell,berlin.txt create mode 100644 Documentation/devicetree/bindings/clock/marvell,mmp2-audio-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/marvell,mmp2-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/marvell,pxa168.txt create mode 100644 Documentation/devicetree/bindings/clock/marvell,pxa1928.txt create mode 100644 Documentation/devicetree/bindings/clock/marvell,pxa910.txt create mode 100644 Documentation/devicetree/bindings/clock/maxim,max77686.txt create mode 100644 Documentation/devicetree/bindings/clock/maxim,max9485.txt create mode 100644 Documentation/devicetree/bindings/clock/mediatek,apmixedsys.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt7621-sysc.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt8365-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt8365-sys-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/mediatek,topckgen.yaml create mode 100644 Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml create mode 100644 Documentation/devicetree/bindings/clock/microchip,mpfs-ccc.yaml create mode 100644 Documentation/devicetree/bindings/clock/microchip,mpfs-clkcfg.yaml create mode 100644 Documentation/devicetree/bindings/clock/microchip,pic32.txt create mode 100644 Documentation/devicetree/bindings/clock/microchip,sparx5-dpll.yaml create mode 100644 Documentation/devicetree/bindings/clock/milbeaut-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/moxa,moxart-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/mstar,msc313-cpupll.yaml create mode 100644 Documentation/devicetree/bindings/clock/mstar,msc313-mpll.yaml create mode 100644 Documentation/devicetree/bindings/clock/mvebu-core-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/mvebu-corediv-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/mvebu-cpu-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/mvebu-gated-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/nspire-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/nuvoton,npcm750-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-car.yaml create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra20-car.yaml create mode 100644 Documentation/devicetree/bindings/clock/nxp,lpc3220-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/nxp,lpc3220-usb-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/oxnas,stdclk.txt create mode 100644 Documentation/devicetree/bindings/clock/pistachio-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/pwm-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/pxa-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/qca,ath79-pll.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,a53pll.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,a7pll.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,aoncc-sm8250.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,audiocc-sm8250.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,camcc-sm8250.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,dispcc-sm6125.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,dispcc-sm6350.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-apq8084.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-ipq8064.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-ipq8074.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8660.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8909.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8976.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8996.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-msm8998.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-other.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-qcm2290.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-qcs404.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sc7180.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sc7280.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sc8180x.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sc8280xp.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sdm845.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sdx55.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sdx65.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm6115.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm6125.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm6350.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm8150.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm8250.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm8350.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm8450.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gpucc-sdm660.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gpucc-sm8350.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,gpucc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,hfpll.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,krait-cc.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,lcc.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,lpasscc.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,mmcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,msm8996-apcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,msm8998-gpucc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,q6sstopcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,qcm2290-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmhcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-camcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-lpasscorecc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-mss.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7280-camcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7280-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7280-lpasscc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7280-lpasscorecc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sdm845-camcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sdm845-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sm6115-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,sm8450-dispcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qcom,spmi-clkdiv.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,turingcc.txt create mode 100644 Documentation/devicetree/bindings/clock/qcom,videocc.yaml create mode 100644 Documentation/devicetree/bindings/clock/qoriq-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/renesas,9series.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-clocks.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-div6-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-mssr.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,emev2-smu.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,r9a06g032-sysctrl.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,rcar-usb2-clock-sel.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,rzg2l-cpg.yaml create mode 100644 Documentation/devicetree/bindings/clock/renesas,versaclock7.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,px30-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3036-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3128-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3228-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3308-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3328-cru.txt create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3368-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3568-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rv1108-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rv1126-cru.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-audss-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-ext-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos4412-isp-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos5260-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos5410-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos5433-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos7-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos7885-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos850-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynosautov9-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,s2mps11.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,s3c2410-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/samsung,s3c2412-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/samsung,s3c2443-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/samsung,s3c64xx-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/samsung,s5pv210-audss-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/samsung,s5pv210-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/sifive/fu540-prci.yaml create mode 100644 Documentation/devicetree/bindings/clock/sifive/fu740-prci.yaml create mode 100644 Documentation/devicetree/bindings/clock/silabs,si514.txt create mode 100644 Documentation/devicetree/bindings/clock/silabs,si5341.txt create mode 100644 Documentation/devicetree/bindings/clock/silabs,si5351.txt create mode 100644 Documentation/devicetree/bindings/clock/silabs,si544.txt create mode 100644 Documentation/devicetree/bindings/clock/silabs,si570.txt create mode 100644 Documentation/devicetree/bindings/clock/snps,hsdk-pll-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/snps,pll-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/sprd,sc9860-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/sprd,sc9863a-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/sprd,ums512-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/st,nomadik.txt create mode 100644 Documentation/devicetree/bindings/clock/st,stm32-rcc.txt create mode 100644 Documentation/devicetree/bindings/clock/st,stm32h7-rcc.txt create mode 100644 Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml create mode 100644 Documentation/devicetree/bindings/clock/st/st,clkgen-mux.txt create mode 100644 Documentation/devicetree/bindings/clock/st/st,clkgen-pll.txt create mode 100644 Documentation/devicetree/bindings/clock/st/st,clkgen.txt create mode 100644 Documentation/devicetree/bindings/clock/st/st,flexgen.txt create mode 100644 Documentation/devicetree/bindings/clock/st/st,quadfs.txt create mode 100644 Documentation/devicetree/bindings/clock/starfive,jh7100-audclk.yaml create mode 100644 Documentation/devicetree/bindings/clock/starfive,jh7100-clkgen.yaml create mode 100644 Documentation/devicetree/bindings/clock/stericsson,abx500.txt create mode 100644 Documentation/devicetree/bindings/clock/stericsson,u8500-clks.yaml create mode 100644 Documentation/devicetree/bindings/clock/sunplus,sp7021-clkc.yaml create mode 100644 Documentation/devicetree/bindings/clock/tesla,fsd-clock.yaml create mode 100644 Documentation/devicetree/bindings/clock/ti,am654-ehrpwm-tbclk.yaml create mode 100644 Documentation/devicetree/bindings/clock/ti,cdce706.txt create mode 100644 Documentation/devicetree/bindings/clock/ti,cdce925.txt create mode 100644 Documentation/devicetree/bindings/clock/ti,lmk04832.yaml create mode 100644 Documentation/devicetree/bindings/clock/ti,sci-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/ti-clkctrl.txt create mode 100644 Documentation/devicetree/bindings/clock/ti-keystone-pllctrl.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/adpll.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/apll.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/autoidle.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/clockdomain.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/composite.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/davinci/da8xx-cfgchip.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/davinci/pll.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/davinci/psc.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/divider.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/dpll.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/dra7-atl.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/fapll.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/fixed-factor-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/gate.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/interface.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/mux.txt create mode 100644 Documentation/devicetree/bindings/clock/ti/ti,clksel.yaml create mode 100644 Documentation/devicetree/bindings/clock/toshiba,tmpv770x-pipllct.yaml create mode 100644 Documentation/devicetree/bindings/clock/toshiba,tmpv770x-pismu.yaml create mode 100644 Documentation/devicetree/bindings/clock/vf610-clock.txt create mode 100644 Documentation/devicetree/bindings/clock/vt8500.txt create mode 100644 Documentation/devicetree/bindings/clock/xgene.txt create mode 100644 Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml create mode 100644 Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml create mode 100644 Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt create mode 100644 Documentation/devicetree/bindings/clock/zynq-7000.txt create mode 100644 Documentation/devicetree/bindings/common-properties.txt create mode 100644 Documentation/devicetree/bindings/connector/usb-connector.yaml create mode 100644 Documentation/devicetree/bindings/counter/ftm-quaddec.txt create mode 100644 Documentation/devicetree/bindings/counter/interrupt-counter.yaml create mode 100644 Documentation/devicetree/bindings/counter/ti,am62-ecap-capture.yaml create mode 100644 Documentation/devicetree/bindings/counter/ti-eqep.yaml create mode 100644 Documentation/devicetree/bindings/cpu/cpu-topology.txt create mode 100644 Documentation/devicetree/bindings/cpu/idle-states.yaml create mode 100644 Documentation/devicetree/bindings/cpufreq/brcm,stb-avs-cpu-freq.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek-hw.yaml create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-spear.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/imx-cpufreq-dt.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/nvidia,tegra124-cpufreq.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/nvidia,tegra20-cpufreq.txt create mode 100644 Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml create mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt create mode 100644 Documentation/devicetree/bindings/crypto/allwinner,sun4i-a10-crypto.yaml create mode 100644 Documentation/devicetree/bindings/crypto/allwinner,sun8i-ce.yaml create mode 100644 Documentation/devicetree/bindings/crypto/allwinner,sun8i-ss.yaml create mode 100644 Documentation/devicetree/bindings/crypto/amd-ccp.txt create mode 100644 Documentation/devicetree/bindings/crypto/amlogic,gxl-crypto.yaml create mode 100644 Documentation/devicetree/bindings/crypto/arm,cryptocell.yaml create mode 100644 Documentation/devicetree/bindings/crypto/artpec6-crypto.txt create mode 100644 Documentation/devicetree/bindings/crypto/aspeed,ast2500-hace.yaml create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-sha.yaml create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-tdes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/brcm,spu-crypto.txt create mode 100644 Documentation/devicetree/bindings/crypto/cortina,sl3516-crypto.yaml create mode 100644 Documentation/devicetree/bindings/crypto/fsl-dcp.yaml create mode 100644 Documentation/devicetree/bindings/crypto/fsl-imx-sahara.yaml create mode 100644 Documentation/devicetree/bindings/crypto/fsl-imx-scc.yaml create mode 100644 Documentation/devicetree/bindings/crypto/fsl-sec2.txt create mode 100644 Documentation/devicetree/bindings/crypto/fsl-sec4.txt create mode 100644 Documentation/devicetree/bindings/crypto/fsl-sec6.txt create mode 100644 Documentation/devicetree/bindings/crypto/hisilicon,hip07-sec.txt create mode 100644 Documentation/devicetree/bindings/crypto/img-hash.txt create mode 100644 Documentation/devicetree/bindings/crypto/inside-secure-safexcel.txt create mode 100644 Documentation/devicetree/bindings/crypto/intel,ixp4xx-crypto.yaml create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-ecc.yaml create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-hcu.yaml create mode 100644 Documentation/devicetree/bindings/crypto/marvell-cesa.txt create mode 100644 Documentation/devicetree/bindings/crypto/mediatek-crypto.txt create mode 100644 Documentation/devicetree/bindings/crypto/mv_cesa.txt create mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt create mode 100644 Documentation/devicetree/bindings/crypto/omap-des.txt create mode 100644 Documentation/devicetree/bindings/crypto/omap-sham.txt create mode 100644 Documentation/devicetree/bindings/crypto/qcom,prng.yaml create mode 100644 Documentation/devicetree/bindings/crypto/qcom-qce.txt create mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.txt create mode 100644 Documentation/devicetree/bindings/crypto/samsung-slimsss.yaml create mode 100644 Documentation/devicetree/bindings/crypto/samsung-sss.yaml create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-crc.yaml create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml create mode 100644 Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml create mode 100644 Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.yaml create mode 100644 Documentation/devicetree/bindings/csky/cpus.txt create mode 100644 Documentation/devicetree/bindings/csky/pmu.txt create mode 100644 Documentation/devicetree/bindings/devfreq/event/rockchip-dfi.txt create mode 100644 Documentation/devicetree/bindings/devfreq/event/samsung,exynos-nocp.yaml create mode 100644 Documentation/devicetree/bindings/devfreq/event/samsung,exynos-ppmu.yaml create mode 100644 Documentation/devicetree/bindings/devfreq/nvidia,tegra30-actmon.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-display-backend.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-display-engine.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-display-frontend.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tv-encoder.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun6i-a31-drc.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun6i-a31-mipi-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun8i-a83t-de2-mixer.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun8i-a83t-dw-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun8i-a83t-hdmi-phy.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun8i-r40-tcon-top.yaml create mode 100644 Documentation/devicetree/bindings/display/allwinner,sun9i-a80-deu.yaml create mode 100644 Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/amlogic,meson-vpu.yaml create mode 100644 Documentation/devicetree/bindings/display/arm,hdlcd.yaml create mode 100644 Documentation/devicetree/bindings/display/arm,komeda.yaml create mode 100644 Documentation/devicetree/bindings/display/arm,malidp.yaml create mode 100644 Documentation/devicetree/bindings/display/arm,pl11x.yaml create mode 100644 Documentation/devicetree/bindings/display/armada/marvell,dove-lcd.txt create mode 100644 Documentation/devicetree/bindings/display/atmel,lcdc.txt create mode 100644 Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-dpi.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-pixelvalve0.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-v3d.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml create mode 100644 Documentation/devicetree/bindings/display/brcm,bcm2835-vec.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix_dp.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/anx6345.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,dsi.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,mhdp8546.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/fsl,imx8qxp-ldb.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/fsl,imx8qxp-pixel-combiner.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/fsl,imx8qxp-pixel-link.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/fsl,imx8qxp-pxl2dpi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/google,cros-ec-anx7688.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ingenic,jz4780-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/intel,keembay-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ite,it66121.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/lontium,lt8912b.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/megachips-stdpxxxx-ge-b850v3-fw.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/nxp,ptn3460.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/nxp,tda998x.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ps8622.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/ps8640.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/renesas,dw-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/renesas,lvds.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/sil,sii9022.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/sil,sii9234.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/sil-sii8620.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/snps,dw-mipi-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/synopsys,dw-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,dlpc3433.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358762.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358764.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/toshiba,tc358775.yaml create mode 100644 Documentation/devicetree/bindings/display/cirrus,clps711x-fb.txt create mode 100644 Documentation/devicetree/bindings/display/connector/analog-tv-connector.yaml create mode 100644 Documentation/devicetree/bindings/display/connector/dp-connector.yaml create mode 100644 Documentation/devicetree/bindings/display/connector/dvi-connector.yaml create mode 100644 Documentation/devicetree/bindings/display/connector/hdmi-connector.yaml create mode 100644 Documentation/devicetree/bindings/display/connector/vga-connector.yaml create mode 100644 Documentation/devicetree/bindings/display/dp-aux-bus.yaml create mode 100644 Documentation/devicetree/bindings/display/dsi-controller.yaml create mode 100644 Documentation/devicetree/bindings/display/exynos/exynos_dp.txt create mode 100644 Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt create mode 100644 Documentation/devicetree/bindings/display/faraday,tve200.yaml create mode 100644 Documentation/devicetree/bindings/display/fsl,dcu.txt create mode 100644 Documentation/devicetree/bindings/display/fsl,lcdif.yaml create mode 100644 Documentation/devicetree/bindings/display/fsl,tcon.txt create mode 100644 Documentation/devicetree/bindings/display/google,goldfish-fb.txt create mode 100644 Documentation/devicetree/bindings/display/himax,hx8357d.txt create mode 100644 Documentation/devicetree/bindings/display/hisilicon/dw-dsi.txt create mode 100644 Documentation/devicetree/bindings/display/hisilicon/hisi-ade.txt create mode 100644 Documentation/devicetree/bindings/display/ilitek,ili9225.txt create mode 100644 Documentation/devicetree/bindings/display/ilitek,ili9486.yaml create mode 100644 Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt create mode 100644 Documentation/devicetree/bindings/display/imx/fsl,imx6-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt create mode 100644 Documentation/devicetree/bindings/display/imx/ldb.txt create mode 100644 Documentation/devicetree/bindings/display/imx/nxp,imx8mq-dcss.yaml create mode 100644 Documentation/devicetree/bindings/display/ingenic,ipu.yaml create mode 100644 Documentation/devicetree/bindings/display/ingenic,lcd.yaml create mode 100644 Documentation/devicetree/bindings/display/intel,keembay-display.yaml create mode 100644 Documentation/devicetree/bindings/display/intel,keembay-msscam.yaml create mode 100644 Documentation/devicetree/bindings/display/lvds.yaml create mode 100644 Documentation/devicetree/bindings/display/marvell,pxa2xx-lcdc.txt create mode 100644 Documentation/devicetree/bindings/display/marvell,pxa300-gcu.txt create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,ccorr.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,cec.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,color.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dither.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dsc.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,gamma.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi-ddc.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,mdp-rdma.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,merge.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,od.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,ovl.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,postmask.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,rdma.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,split.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,ufoe.yaml create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.yaml create mode 100644 Documentation/devicetree/bindings/display/mipi-dsi-bus.txt create mode 100644 Documentation/devicetree/bindings/display/msm/dp-controller.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-msm8998.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-qcm2290.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-sc7180.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-sc7280.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-sdm845.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-10nm.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-20nm.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-common.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/gmu.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/gpu.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/mdp4.yaml create mode 100644 Documentation/devicetree/bindings/display/msm/mdp5.txt create mode 100644 Documentation/devicetree/bindings/display/multi-inno,mi0283qt.txt create mode 100644 Documentation/devicetree/bindings/display/panel/abt,y030xx067a.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/advantech,idk-1110wr.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/advantech,idk-2121wr.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/arm,rtsm-display.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/arm,versatile-tft-panel.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/armadeus,st0700-adapt.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/asus,z00t-tm5p5-nt35596.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/boe,bf060y8m-aj0.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/boe,himax8279d.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/display-timing.txt create mode 100644 Documentation/devicetree/bindings/display/panel/display-timings.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/dlc,dlc0700yzg-1.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/elida,kd35t133.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/feixin,k101-im2ba02.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/feiyang,fy07024di26a30d.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ilitek,ili9163.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ilitek,ili9322.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ilitek,ili9341.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/innolux,ee101ia-01d.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/innolux,ej030na.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/innolux,p097pfg.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/innolux,p120zdg-bf1.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/jdi,lt070me05000.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/kingdisplay,kd035g6-54nt.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/leadtek,ltk035c5444t.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/leadtek,ltk500hd1829.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/lg,lg4573.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/lgphilips,lb035q02.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/logicpd,type28.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/mantix,mlaf057we51-x.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/mitsubishi,aa121td01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/nec,nl8048hl11.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/novatek,nt35510.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/novatek,nt35950.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/olimex,lcd-olinuxino.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/orisetech,otm8009a.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-common.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-dpi.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-dsi-cm.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-edp.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-lvds.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-simple.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/panel-timing.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/pda,91-00156-a0.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/raydium,rm68200.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/rocktech,jh057n00900.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ronbo,rb070d30.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,amoled-mipi-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,ld9040.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,lms380kf01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,lms397kf04.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6d16d0.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6d27a1.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6e88a0-ams452ef01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6e8aa0.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/seiko,43wvf1g.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sgd,gktw70sdae4se.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,ld-d5116z01b.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,lq101r1sx01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,lq150x1lg11.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,ls037v7dw01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,ls043t1le01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sharp,ls060t1sx01.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sitronix,st7701.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sitronix,st7789v.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sony,acx424akp.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sony,acx565akm.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/sony,tulip-truly-nt35521.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/startek,startek-kd050c.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/tfc,s9700rtwv43tr-01b.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/ti,nspire.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/tpo,td.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/tpo,tpg110.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/visionox,rm69299.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml create mode 100644 Documentation/devicetree/bindings/display/renesas,cmm.yaml create mode 100644 Documentation/devicetree/bindings/display/renesas,du.yaml create mode 100644 Documentation/devicetree/bindings/display/repaper.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/analogix_dp-rockchip.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/cdn-dp-rockchip.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/inno_hdmi-rockchip.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip,rk3066-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-drm.yaml create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-lvds.txt create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-vop.yaml create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-vop2.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos-hdmi-ddc.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos-mixer.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos5433-decon.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos5433-mic.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,exynos7-decon.yaml create mode 100644 Documentation/devicetree/bindings/display/samsung/samsung,fimd.yaml create mode 100644 Documentation/devicetree/bindings/display/simple-framebuffer.yaml create mode 100644 Documentation/devicetree/bindings/display/sitronix,st7586.txt create mode 100644 Documentation/devicetree/bindings/display/sitronix,st7735r.yaml create mode 100644 Documentation/devicetree/bindings/display/sm501fb.txt create mode 100644 Documentation/devicetree/bindings/display/snps,arcpgu.txt create mode 100644 Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml create mode 100644 Documentation/devicetree/bindings/display/sprd/sprd,display-subsystem.yaml create mode 100644 Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml create mode 100644 Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml create mode 100644 Documentation/devicetree/bindings/display/ssd1289fb.txt create mode 100644 Documentation/devicetree/bindings/display/st,stih4xx.txt create mode 100644 Documentation/devicetree/bindings/display/st,stm32-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/st,stm32-ltdc.yaml create mode 100644 Documentation/devicetree/bindings/display/ste,mcde.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-dpaux.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-sor.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-vic.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-dc.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-display.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-dsi-padctl.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-epp.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-gr2d.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-gr3d.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-isp.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-mpe.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-tvo.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vi.yaml create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra210-csi.yaml create mode 100644 Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml create mode 100644 Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml create mode 100644 Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml create mode 100644 Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,opa362.txt create mode 100644 Documentation/devicetree/bindings/display/ti/ti,tpd12s015.txt create mode 100644 Documentation/devicetree/bindings/display/tilcdc/panel.txt create mode 100644 Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt create mode 100644 Documentation/devicetree/bindings/display/truly,nt35597.txt create mode 100644 Documentation/devicetree/bindings/display/via,vt8500-fb.txt create mode 100644 Documentation/devicetree/bindings/display/wm,prizm-ge-rops.txt create mode 100644 Documentation/devicetree/bindings/display/wm,wm8505-fb.txt create mode 100644 Documentation/devicetree/bindings/display/xlnx/xlnx,zynqmp-dpsub.yaml create mode 100644 Documentation/devicetree/bindings/display/xylon,logicvc-display.yaml create mode 100644 Documentation/devicetree/bindings/dma/adi,axi-dmac.txt create mode 100644 Documentation/devicetree/bindings/dma/allwinner,sun4i-a10-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/allwinner,sun50i-a64-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/allwinner,sun6i-a31-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/altr,msgdma.yaml create mode 100644 Documentation/devicetree/bindings/dma/apm-xgene-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/apple,admac.yaml create mode 100644 Documentation/devicetree/bindings/dma/arm,pl330.yaml create mode 100644 Documentation/devicetree/bindings/dma/arm-pl08x.yaml create mode 100644 Documentation/devicetree/bindings/dma/atmel-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/atmel-xdma.txt create mode 100644 Documentation/devicetree/bindings/dma/brcm,bcm2835-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/brcm,iproc-sba.txt create mode 100644 Documentation/devicetree/bindings/dma/dma-common.yaml create mode 100644 Documentation/devicetree/bindings/dma/dma-controller.yaml create mode 100644 Documentation/devicetree/bindings/dma/dma-router.yaml create mode 100644 Documentation/devicetree/bindings/dma/dma.txt create mode 100644 Documentation/devicetree/bindings/dma/fsl,edma.yaml create mode 100644 Documentation/devicetree/bindings/dma/fsl-imx-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt create mode 100644 Documentation/devicetree/bindings/dma/fsl-mxs-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/fsl-qdma.txt create mode 100644 Documentation/devicetree/bindings/dma/img-mdc-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/ingenic,dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/intel,ldma.yaml create mode 100644 Documentation/devicetree/bindings/dma/k3dma.txt create mode 100644 Documentation/devicetree/bindings/dma/lpc1850-dmamux.txt create mode 100644 Documentation/devicetree/bindings/dma/mediatek,uart-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/milbeaut-m10v-hdmac.txt create mode 100644 Documentation/devicetree/bindings/dma/milbeaut-m10v-xdmac.txt create mode 100644 Documentation/devicetree/bindings/dma/mmp-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/mpc512x-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/mtk-hsdma.txt create mode 100644 Documentation/devicetree/bindings/dma/mv-xor-v2.txt create mode 100644 Documentation/devicetree/bindings/dma/mv-xor.txt create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra20-apbdma.txt create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml create mode 100644 Documentation/devicetree/bindings/dma/owl-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/qcom,adm.yaml create mode 100644 Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/qcom,gpi.yaml create mode 100644 Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt create mode 100644 Documentation/devicetree/bindings/dma/renesas,nbpfaxi.txt create mode 100644 Documentation/devicetree/bindings/dma/renesas,rcar-dmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/renesas,rzn1-dmamux.yaml create mode 100644 Documentation/devicetree/bindings/dma/renesas,usb-dmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/sifive,fu540-c000-pdma.yaml create mode 100644 Documentation/devicetree/bindings/dma/snps,dma-spear1340.yaml create mode 100644 Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/socionext,uniphier-mio-dmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/socionext,uniphier-xdmac.yaml create mode 100644 Documentation/devicetree/bindings/dma/sprd-dma.txt create mode 100644 Documentation/devicetree/bindings/dma/st,stm32-dma.yaml create mode 100644 Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml create mode 100644 Documentation/devicetree/bindings/dma/st,stm32-mdma.yaml create mode 100644 Documentation/devicetree/bindings/dma/st_fdma.txt create mode 100644 Documentation/devicetree/bindings/dma/stericsson,dma40.yaml create mode 100644 Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt create mode 100644 Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml create mode 100644 Documentation/devicetree/bindings/dma/ti/k3-pktdma.yaml create mode 100644 Documentation/devicetree/bindings/dma/ti/k3-udma.yaml create mode 100644 Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt create mode 100644 Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml create mode 100644 Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dpdma.yaml create mode 100644 Documentation/devicetree/bindings/dsp/fsl,dsp.yaml create mode 100644 Documentation/devicetree/bindings/dsp/mediatek,mt8186-dsp.yaml create mode 100644 Documentation/devicetree/bindings/dsp/mediatek,mt8195-dsp.yaml create mode 100644 Documentation/devicetree/bindings/dvfs/performance-domain.yaml create mode 100644 Documentation/devicetree/bindings/edac/amazon,al-mc-edac.yaml create mode 100644 Documentation/devicetree/bindings/edac/apm-xgene-edac.txt create mode 100644 Documentation/devicetree/bindings/edac/aspeed-sdram-edac.txt create mode 100644 Documentation/devicetree/bindings/edac/dmc-520.yaml create mode 100644 Documentation/devicetree/bindings/edac/socfpga-eccmgr.txt create mode 100644 Documentation/devicetree/bindings/eeprom/at24.yaml create mode 100644 Documentation/devicetree/bindings/eeprom/at25.yaml create mode 100644 Documentation/devicetree/bindings/eeprom/microchip,93lc46b.yaml create mode 100644 Documentation/devicetree/bindings/example-schema.yaml create mode 100644 Documentation/devicetree/bindings/extcon/extcon-max3355.txt create mode 100644 Documentation/devicetree/bindings/extcon/extcon-palmas.txt create mode 100644 Documentation/devicetree/bindings/extcon/extcon-ptn5150.yaml create mode 100644 Documentation/devicetree/bindings/extcon/extcon-rt8973a.txt create mode 100644 Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt create mode 100644 Documentation/devicetree/bindings/extcon/extcon-usbc-cros-ec.yaml create mode 100644 Documentation/devicetree/bindings/extcon/extcon-usbc-tusb320.yaml create mode 100644 Documentation/devicetree/bindings/extcon/fcs,fsa880.yaml create mode 100644 Documentation/devicetree/bindings/extcon/maxim,max77843.yaml create mode 100644 Documentation/devicetree/bindings/extcon/qcom,pm8941-misc.yaml create mode 100644 Documentation/devicetree/bindings/extcon/siliconmitus,sm5502-muic.yaml create mode 100644 Documentation/devicetree/bindings/extcon/wlf,arizona.yaml create mode 100644 Documentation/devicetree/bindings/firmware/arm,scmi.yaml create mode 100644 Documentation/devicetree/bindings/firmware/arm,scpi.yaml create mode 100644 Documentation/devicetree/bindings/firmware/coreboot.txt create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-mox-rwtm.txt create mode 100644 Documentation/devicetree/bindings/firmware/fsl,scu.yaml create mode 100644 Documentation/devicetree/bindings/firmware/intel,ixp4xx-network-processing-engine.yaml create mode 100644 Documentation/devicetree/bindings/firmware/intel,stratix10-svc.txt create mode 100644 Documentation/devicetree/bindings/firmware/meson/meson_sm.txt create mode 100644 Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.yaml create mode 100644 Documentation/devicetree/bindings/firmware/nvidia,tegra210-bpmp.txt create mode 100644 Documentation/devicetree/bindings/firmware/qcom,scm.yaml create mode 100644 Documentation/devicetree/bindings/firmware/qemu,fw-cfg-mmio.yaml create mode 100644 Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.yaml create mode 100644 Documentation/devicetree/bindings/fpga/altera-fpga2sdram-bridge.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-freeze-bridge.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-hps2fpga-bridge.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-passive-serial.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-pr-ip.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-socfpga-a10-fpga-mgr.txt create mode 100644 Documentation/devicetree/bindings/fpga/altera-socfpga-fpga-mgr.txt create mode 100644 Documentation/devicetree/bindings/fpga/fpga-bridge.txt create mode 100644 Documentation/devicetree/bindings/fpga/fpga-region.txt create mode 100644 Documentation/devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt create mode 100644 Documentation/devicetree/bindings/fpga/lattice-ice40-fpga-mgr.txt create mode 100644 Documentation/devicetree/bindings/fpga/lattice-machxo2-spi.txt create mode 100644 Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml create mode 100644 Documentation/devicetree/bindings/fpga/xilinx-pr-decoupler.txt create mode 100644 Documentation/devicetree/bindings/fpga/xilinx-slave-serial.txt create mode 100644 Documentation/devicetree/bindings/fpga/xilinx-zynq-fpga-mgr.yaml create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,versal-fpga.yaml create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,zynqmp-pcap-fpga.yaml create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-aspeed.txt create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-ast-cf.txt create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-gpio.txt create mode 100644 Documentation/devicetree/bindings/fsi/fsi.txt create mode 100644 Documentation/devicetree/bindings/fsi/ibm,fsi2spi.yaml create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt create mode 100644 Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml create mode 100644 Documentation/devicetree/bindings/gnss/brcm,bcm4751.yaml create mode 100644 Documentation/devicetree/bindings/gnss/gnss-common.yaml create mode 100644 Documentation/devicetree/bindings/gnss/mediatek.yaml create mode 100644 Documentation/devicetree/bindings/gnss/sirfstar.yaml create mode 100644 Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml create mode 100644 Documentation/devicetree/bindings/goldfish/audio.txt create mode 100644 Documentation/devicetree/bindings/goldfish/battery.txt create mode 100644 Documentation/devicetree/bindings/goldfish/events.txt create mode 100644 Documentation/devicetree/bindings/goldfish/pipe.txt create mode 100644 Documentation/devicetree/bindings/goldfish/tty.txt create mode 100644 Documentation/devicetree/bindings/gpio/8xxx_gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/abilis,tb10x-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/airoha,en7523-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/aspeed,sgpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/brcm,bcm6345-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/brcm,brcmstb-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/brcm,kona-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/brcm,xgs-iproc-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/cavium-octeon-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/cdns,gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/cirrus,clps711x-mctrl-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/delta,tn48m-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml create mode 100644 Documentation/devicetree/bindings/gpio/faraday,ftgpio010.yaml create mode 100644 Documentation/devicetree/bindings/gpio/fsl,imx8qxp-sc-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/fsl-imx-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gateworks,pld-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-74xx-mmio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-adnp.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-altera.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-aspeed.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-ath79.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-clps711x.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-consumer-common.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-davinci.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-eic-sprd.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-exar.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-grgpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-lp3943.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-max3191x.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-max77620.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-mm-lantiq.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-moxtet.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-mpc8xxx.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-mxs.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-nmk.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-palmas.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-pisosr.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-rda.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-sprd.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-stmpe.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-thunderx.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-ts4800.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-ts4900.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-twl4030.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-vf610.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-virtio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xgene-sb.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xgene.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xra1403.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-zevio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio-zynq.yaml create mode 100644 Documentation/devicetree/bindings/gpio/gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio_atmel.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio_lpc32xx.txt create mode 100644 Documentation/devicetree/bindings/gpio/gpio_oxnas.txt create mode 100644 Documentation/devicetree/bindings/gpio/ibm,ppc4xx-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/idt,32434-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/intel,ixp4xx-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/kontron,sl28cpld-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/microchip,mpfs-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/microchip,pic32-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/mrvl-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/mstar,msc313-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/netxbig-gpio-ext.txt create mode 100644 Documentation/devicetree/bindings/gpio/ni,169445-nand-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/nintendo,hollywood-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/nvidia,tegra186-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/nvidia,tegra20-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/nxp,lpc1850-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml create mode 100644 Documentation/devicetree/bindings/gpio/pl061-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/qcom,wcd934x-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/raspberrypi,firmware-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/realtek,otto-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/renesas,em-gio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/renesas,rcar-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/rockchip,gpio-bank.yaml create mode 100644 Documentation/devicetree/bindings/gpio/rockchip,rk3328-grf-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/sifive,gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/snps,creg-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/snps,dw-apb-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/socionext,uniphier-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/sodaville.txt create mode 100644 Documentation/devicetree/bindings/gpio/spear_spics.txt create mode 100644 Documentation/devicetree/bindings/gpio/ti,omap-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/toshiba,gpio-visconti.yaml create mode 100644 Documentation/devicetree/bindings/gpio/wd,mbl-gpio.txt create mode 100644 Documentation/devicetree/bindings/gpio/x-powers,axp209-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpio/xlnx,gpio-xilinx.yaml create mode 100644 Documentation/devicetree/bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml create mode 100644 Documentation/devicetree/bindings/gpio/xylon,logicvc-gpio.yaml create mode 100644 Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml create mode 100644 Documentation/devicetree/bindings/gpu/arm,mali-midgard.yaml create mode 100644 Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml create mode 100644 Documentation/devicetree/bindings/gpu/aspeed-gfx.txt create mode 100644 Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml create mode 100644 Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml create mode 100644 Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvenc.yaml create mode 100644 Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvjpg.yaml create mode 100644 Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt create mode 100644 Documentation/devicetree/bindings/gpu/samsung-g2d.yaml create mode 100644 Documentation/devicetree/bindings/gpu/samsung-rotator.yaml create mode 100644 Documentation/devicetree/bindings/gpu/samsung-scaler.yaml create mode 100644 Documentation/devicetree/bindings/gpu/vivante,gc.yaml create mode 100644 Documentation/devicetree/bindings/graph.txt create mode 100644 Documentation/devicetree/bindings/hsi/client-devices.txt create mode 100644 Documentation/devicetree/bindings/hsi/nokia-modem.txt create mode 100644 Documentation/devicetree/bindings/hsi/omap-ssi.txt create mode 100644 Documentation/devicetree/bindings/hwinfo/renesas,prr.yaml create mode 100644 Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml create mode 100644 Documentation/devicetree/bindings/hwinfo/samsung,s5pv210-chipid.yaml create mode 100644 Documentation/devicetree/bindings/hwinfo/ti,k3-socinfo.yaml create mode 100644 Documentation/devicetree/bindings/hwlock/allwinner,sun6i-a31-hwspinlock.yaml create mode 100644 Documentation/devicetree/bindings/hwlock/hwlock.txt create mode 100644 Documentation/devicetree/bindings/hwlock/qcom-hwspinlock.yaml create mode 100644 Documentation/devicetree/bindings/hwlock/sprd-hwspinlock.txt create mode 100644 Documentation/devicetree/bindings/hwlock/st,stm32-hwspinlock.yaml create mode 100644 Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adc128d818.txt create mode 100644 Documentation/devicetree/bindings/hwmon/adi,ad741x.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,adm1177.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,adm1266.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,adm1275.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,ltc2947.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adi,max31760.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/adt7475.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/amd,sbrmi.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/amd,sbtsi.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/apm-xgene-hwmon.txt create mode 100644 Documentation/devicetree/bindings/hwmon/as370.txt create mode 100644 Documentation/devicetree/bindings/hwmon/aspeed-pwm-tacho.txt create mode 100644 Documentation/devicetree/bindings/hwmon/baikal,bt1-pvt.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/cirrus,lochnagar.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/g762.txt create mode 100644 Documentation/devicetree/bindings/hwmon/gpio-fan.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ibm,occ-hwmon.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ibm,p8-occ-hwmon.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ibmpowernv.txt create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ina3221.txt create mode 100644 Documentation/devicetree/bindings/hwmon/jedec,jc42.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/kontron,sl28cpld-hwmon.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/lltc,ltc4151.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/lm75.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/lm87.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ltc2978.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ltc2990.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt create mode 100644 Documentation/devicetree/bindings/hwmon/max31785.txt create mode 100644 Documentation/devicetree/bindings/hwmon/max6650.txt create mode 100644 Documentation/devicetree/bindings/hwmon/max6697.txt create mode 100644 Documentation/devicetree/bindings/hwmon/maxim,max20730.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/microchip,lan966x.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/microchip,mcp3021.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/microchip,sparx5-temp.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/moortec,mr75203.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/national,lm90.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/npcm750-pwm-fan.txt create mode 100644 Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ntc-thermistor.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/nuvoton,nct6775.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/nuvoton,nct7802.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/ti,lm25066.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/ti,ucd90320.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/pwm-fan.txt create mode 100644 Documentation/devicetree/bindings/hwmon/sensirion,sht15.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/stts751.txt create mode 100644 Documentation/devicetree/bindings/hwmon/ti,ads7828.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp102.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp108.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp421.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp464.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp513.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tps23861.yaml create mode 100644 Documentation/devicetree/bindings/hwmon/vexpress.txt create mode 100644 Documentation/devicetree/bindings/hwmon/winbond,w83781d.yaml create mode 100644 Documentation/devicetree/bindings/i2c/allwinner,sun6i-a31-p2wi.yaml create mode 100644 Documentation/devicetree/bindings/i2c/amlogic,meson6-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/apple,i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/arm,i2c-versatile.yaml create mode 100644 Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/brcm,bcm2835-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/brcm,brcmstb-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/brcm,iproc-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/brcm,kona-i2c.txt create mode 100644 Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml create mode 100644 Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-altera.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-arb-gpio-challenge.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-arb.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-axxia.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-cbus-gpio.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-davinci.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-demux-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-digicolor.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-exynos5.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-fsi.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-gate.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-gpio.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-hix5hd2.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-img-scb.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-imx-lpi2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-imx.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-iop3xx.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-lpc2k.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mpc.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mt65xx.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-gpio.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-ltc4306.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-reg.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mxs.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-octeon.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-opal.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-owl.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-pca-platform.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-pnx.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-pxa-pci-ce4100.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-pxa.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-rk3x.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-sprd.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-st.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-virtio.yaml create mode 100644 Documentation/devicetree/bindings/i2c/i2c-wmt.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c-xgene-slimpro.txt create mode 100644 Documentation/devicetree/bindings/i2c/i2c.txt create mode 100644 Documentation/devicetree/bindings/i2c/ingenic,i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/mediatek,mt7621-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/microchip,corei2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/nuvoton,npcm7xx-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra186-bpmp-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/nxp,pca9541.txt create mode 100644 Documentation/devicetree/bindings/i2c/opencores,i2c-ocores.yaml create mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml create mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml create mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-qup.yaml create mode 100644 Documentation/devicetree/bindings/i2c/renesas,iic-emev2.yaml create mode 100644 Documentation/devicetree/bindings/i2c/renesas,rcar-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/renesas,riic.yaml create mode 100644 Documentation/devicetree/bindings/i2c/renesas,rmobile-iic.yaml create mode 100644 Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml create mode 100644 Documentation/devicetree/bindings/i2c/samsung,s3c2410-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/socionext,uniphier-fi2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/socionext,uniphier-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/st,nomadik-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/ti,omap4-i2c.yaml create mode 100644 Documentation/devicetree/bindings/i2c/xlnx,xps-iic-2.00.a.yaml create mode 100644 Documentation/devicetree/bindings/i3c/cdns,i3c-master.yaml create mode 100644 Documentation/devicetree/bindings/i3c/i3c.yaml create mode 100644 Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml create mode 100644 Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml create mode 100644 Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adis16201.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adis16240.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adxl313.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adxl345.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adxl355.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adxl367.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adxl372.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/bosch,bma220.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/bosch,bma400.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/bosch,bmi088.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/fsl,mma7455.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/fsl,mma8452.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/kionix,kxcjk1013.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/kionix,kxsd9.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/lis302.txt create mode 100644 Documentation/devicetree/bindings/iio/accel/memsensing,msa311.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/murata,sca3300.yaml create mode 100644 Documentation/devicetree/bindings/iio/accel/nxp,fxls8962af.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7091r5.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7280a.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7291.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7292.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7298.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7476.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7768-1.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7780.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7923.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7949.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad799x.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad9467.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,axi-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/allwinner,sun8i-a33-ths.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/amlogic,meson-saradc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/aspeed,ast2400-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/aspeed,ast2600-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/atmel,sama5d2-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/atmel,sama9260-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/brcm,iproc-static-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/cosmic,10001-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/dlg,da9150-gpadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/envelope-detector.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/fsl,imx25-gcq.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/fsl,imx7d-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/fsl,vf610-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/holt,hi8435.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ingenic,adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/marvell,berlin2-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max1027.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max11100.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max1118.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max11205.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max1241.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max1363.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/maxim,max9611.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/mediatek,mt2701-auxadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/mediatek,mt6360-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/microchip,mcp3201.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/microchip,mcp3911.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/nuvoton,nau7802.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/nuvoton,npcm750-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/nxp,lpc1850-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/nxp,lpc3220-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/qcom,spmi-iadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/qcom,spmi-rradc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/renesas,rcar-gyroadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/renesas,rzg2l-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/richtek,rtq6056.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/sigma-delta-modulator.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/sprd,sc2720-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/st,stmpe-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc0832.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc084s021.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc108s102.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc12138.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc128s052.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,adc161s626.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads1015.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads124s08.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads131e08.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads7950.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads8344.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,ads8688.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,am3359-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,palmas-gpadc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,tlc4541.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,tsc2046.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/ti,twl4030-madc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/x-powers,axp209-adc.yaml create mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt create mode 100644 Documentation/devicetree/bindings/iio/adc/xlnx,zynqmp-ams.yaml create mode 100644 Documentation/devicetree/bindings/iio/addac/adi,ad74413r.yaml create mode 100644 Documentation/devicetree/bindings/iio/afe/current-sense-amplifier.yaml create mode 100644 Documentation/devicetree/bindings/iio/afe/current-sense-shunt.yaml create mode 100644 Documentation/devicetree/bindings/iio/afe/temperature-sense-rtd.yaml create mode 100644 Documentation/devicetree/bindings/iio/afe/temperature-transducer.yaml create mode 100644 Documentation/devicetree/bindings/iio/afe/voltage-divider.yaml create mode 100644 Documentation/devicetree/bindings/iio/amplifiers/adi,ada4250.yaml create mode 100644 Documentation/devicetree/bindings/iio/amplifiers/adi,hmc425a.yaml create mode 100644 Documentation/devicetree/bindings/iio/cdc/adi,ad7150.yaml create mode 100644 Documentation/devicetree/bindings/iio/cdc/adi,ad7746.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/ams,ccs811.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/plantower,pms7003.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/senseair,sunrise.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/sensirion,scd30.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/sensirion,scd4x.yaml create mode 100644 Documentation/devicetree/bindings/iio/chemical/sensirion,sps30.yaml create mode 100644 Documentation/devicetree/bindings/iio/common.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad3552r.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5064.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5360.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5380.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5421.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5449.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5504.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5592r.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5624r.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5686.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5696.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5755.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5758.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5761.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5764.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5766.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5770r.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad7293.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ad8801.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ltc2688.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/dpot-dac.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/fsl,vf610-dac.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/lltc,ltc1660.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/maxim,ds4424.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/maxim,max5821.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/microchip,mcp4922.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/nxp,lpc1850-dac.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac082s085.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7311.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7512.yaml create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7612.yaml create mode 100644 Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adf4371.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,adf4350.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,admv1013.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,admv4420.yaml create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,adrf6780.yaml create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/adi,adxrs290.yaml create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/bosch,bmg160.yaml create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/invensense,mpu3050.yaml create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.yaml create mode 100644 Documentation/devicetree/bindings/iio/health/maxim,max30100.yaml create mode 100644 Documentation/devicetree/bindings/iio/health/maxim,max30102.yaml create mode 100644 Documentation/devicetree/bindings/iio/health/ti,afe4403.yaml create mode 100644 Documentation/devicetree/bindings/iio/health/ti,afe4404.yaml create mode 100644 Documentation/devicetree/bindings/iio/humidity/dht11.yaml create mode 100644 Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml create mode 100644 Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml create mode 100644 Documentation/devicetree/bindings/iio/impedance-analyzer/adi,ad5933.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/adi,adis16460.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/adi,adis16475.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/adi,adis16480.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/bosch,bmi160.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/bosch,bno055.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/invensense,icm42600.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/nxp,fxos8700.yaml create mode 100644 Documentation/devicetree/bindings/iio/imu/st,lsm6dsx.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/adux1020.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/ams,as73211.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/amstaos,tsl2563.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/amstaos,tsl2591.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/avago,apds9300.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/avago,apds9960.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/bh1750.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/capella,cm3605.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/capella,cm36651.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/dynaimage,al3010.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/dynaimage,al3320a.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/isl29018.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/maxim,max44009.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/noa1305.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/sharp,gp2ap002.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/sharp,gp2ap020a00f.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/st,uvis25.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/st,vl6180.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/stk33xx.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/ti,opt3001.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/tsl2583.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/tsl2772.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/upisemi,us5182.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/veml6030.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/vishay,vcnl4000.yaml create mode 100644 Documentation/devicetree/bindings/iio/light/vishay,vcnl4035.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/asahi-kasei,ak8974.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/asahi-kasei,ak8975.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/bosch,bmc150_magn.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/fsl,mag3110.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/honeywell,hmc5843.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/pni,rm3100.yaml create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/yamaha,yas530.yaml create mode 100644 Documentation/devicetree/bindings/iio/mount-matrix.txt create mode 100644 Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/adi,ad5272.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/max5432.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/microchip,mcp41010.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/microchip,mcp4131.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiometer/microchip,mcp4531.yaml create mode 100644 Documentation/devicetree/bindings/iio/potentiostat/ti,lmp91000.yaml create mode 100644 Documentation/devicetree/bindings/iio/pressure/asc,dlhl60d.yaml create mode 100644 Documentation/devicetree/bindings/iio/pressure/bmp085.yaml create mode 100644 Documentation/devicetree/bindings/iio/pressure/hoperf,hp03.yaml create mode 100644 Documentation/devicetree/bindings/iio/pressure/meas,ms5611.yaml create mode 100644 Documentation/devicetree/bindings/iio/pressure/murata,zpa2326.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/devantech-srf04.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/google,cros-ec-mkbp-proximity.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/maxbotix,mb1232.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/parallax-ping.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9310.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9324.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9360.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/st,vl53l0x.yaml create mode 100644 Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml create mode 100644 Documentation/devicetree/bindings/iio/resolver/adi,ad2s90.yaml create mode 100644 Documentation/devicetree/bindings/iio/samsung,sensorhub-rinato.yaml create mode 100644 Documentation/devicetree/bindings/iio/st,st-sensors.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim,max31855k.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim,max31856.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/maxim,max31865.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/melexis,mlx90614.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/melexis,mlx90632.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/ti,tmp007.yaml create mode 100644 Documentation/devicetree/bindings/iio/temperature/ti,tmp117.yaml create mode 100644 Documentation/devicetree/bindings/index.rst create mode 100644 Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt create mode 100644 Documentation/devicetree/bindings/input/adc-joystick.yaml create mode 100644 Documentation/devicetree/bindings/input/adc-keys.yaml create mode 100644 Documentation/devicetree/bindings/input/adi,adp5588.yaml create mode 100644 Documentation/devicetree/bindings/input/allwinner,sun4i-a10-lradc-keys.yaml create mode 100644 Documentation/devicetree/bindings/input/ariel-pwrbutton.yaml create mode 100644 Documentation/devicetree/bindings/input/atmel,captouch.txt create mode 100644 Documentation/devicetree/bindings/input/atmel,maxtouch.yaml create mode 100644 Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml create mode 100644 Documentation/devicetree/bindings/input/brcm,bcm-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/clps711x-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt create mode 100644 Documentation/devicetree/bindings/input/cypress,cyapa.txt create mode 100644 Documentation/devicetree/bindings/input/cypress,tm2-touchkey.yaml create mode 100644 Documentation/devicetree/bindings/input/cypress-sf.yaml create mode 100644 Documentation/devicetree/bindings/input/da9062-onkey.txt create mode 100644 Documentation/devicetree/bindings/input/dlg,da7280.txt create mode 100644 Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt create mode 100644 Documentation/devicetree/bindings/input/e3x0-button.txt create mode 100644 Documentation/devicetree/bindings/input/elan,ekth3000.yaml create mode 100644 Documentation/devicetree/bindings/input/elan,ekth6915.yaml create mode 100644 Documentation/devicetree/bindings/input/fsl,mpr121-touchkey.yaml create mode 100644 Documentation/devicetree/bindings/input/fsl,scu-key.yaml create mode 100644 Documentation/devicetree/bindings/input/goodix,gt7375p.yaml create mode 100644 Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml create mode 100644 Documentation/devicetree/bindings/input/gpio-beeper.txt create mode 100644 Documentation/devicetree/bindings/input/gpio-decoder.txt create mode 100644 Documentation/devicetree/bindings/input/gpio-keys.yaml create mode 100644 Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/gpio-mouse.txt create mode 100644 Documentation/devicetree/bindings/input/gpio-vibrator.yaml create mode 100644 Documentation/devicetree/bindings/input/hid-over-i2c.yaml create mode 100644 Documentation/devicetree/bindings/input/ibm,op-panel.yaml create mode 100644 Documentation/devicetree/bindings/input/imx-keypad.yaml create mode 100644 Documentation/devicetree/bindings/input/input-reset.txt create mode 100644 Documentation/devicetree/bindings/input/input.yaml create mode 100644 Documentation/devicetree/bindings/input/iqs269a.yaml create mode 100644 Documentation/devicetree/bindings/input/iqs626a.yaml create mode 100644 Documentation/devicetree/bindings/input/iqs62x-keys.yaml create mode 100644 Documentation/devicetree/bindings/input/lpc32xx-key.txt create mode 100644 Documentation/devicetree/bindings/input/matrix-keymap.txt create mode 100644 Documentation/devicetree/bindings/input/matrix-keymap.yaml create mode 100644 Documentation/devicetree/bindings/input/max77650-onkey.yaml create mode 100644 Documentation/devicetree/bindings/input/mediatek,mt6779-keypad.yaml create mode 100644 Documentation/devicetree/bindings/input/mediatek,pmic-keys.yaml create mode 100644 Documentation/devicetree/bindings/input/microchip,cap11xx.yaml create mode 100644 Documentation/devicetree/bindings/input/microchip,qt1050.txt create mode 100644 Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt create mode 100644 Documentation/devicetree/bindings/input/omap-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/pine64,pinephone-keyboard.yaml create mode 100644 Documentation/devicetree/bindings/input/ps2keyb-mouse-apbps2.txt create mode 100644 Documentation/devicetree/bindings/input/pwm-beeper.txt create mode 100644 Documentation/devicetree/bindings/input/pwm-vibrator.yaml create mode 100644 Documentation/devicetree/bindings/input/pxa27x-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/qcom,pm8941-pwrkey.yaml create mode 100644 Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/qcom,pm8xxx-pwrkey.txt create mode 100644 Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml create mode 100644 Documentation/devicetree/bindings/input/raydium_i2c_ts.txt create mode 100644 Documentation/devicetree/bindings/input/regulator-haptic.yaml create mode 100644 Documentation/devicetree/bindings/input/rmi4/rmi_2d_sensor.txt create mode 100644 Documentation/devicetree/bindings/input/rmi4/rmi_f01.txt create mode 100644 Documentation/devicetree/bindings/input/rmi4/rmi_i2c.txt create mode 100644 Documentation/devicetree/bindings/input/rmi4/rmi_spi.txt create mode 100644 Documentation/devicetree/bindings/input/rotary-encoder.txt create mode 100644 Documentation/devicetree/bindings/input/samsung-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/snvs-pwrkey.txt create mode 100644 Documentation/devicetree/bindings/input/spear-keyboard.txt create mode 100644 Documentation/devicetree/bindings/input/sprd,sc27xx-vibrator.yaml create mode 100644 Documentation/devicetree/bindings/input/st-keyscan.txt create mode 100644 Documentation/devicetree/bindings/input/stmpe-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/tca8418_keypad.txt create mode 100644 Documentation/devicetree/bindings/input/ti,drv260x.txt create mode 100644 Documentation/devicetree/bindings/input/ti,drv2665.txt create mode 100644 Documentation/devicetree/bindings/input/ti,drv2667.txt create mode 100644 Documentation/devicetree/bindings/input/ti,nspire-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/ti,palmas-pwrbutton.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ad7879.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ads7846.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ar1021.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/auo_pixcir_ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/azoteq,iqs5xx.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/bu21013.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/bu21029.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/chipone,icn8318.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/colibri-vf50-ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/cypress,cy8ctma140.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/cypress,cy8ctma340.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/eeti,exc3000.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/eeti.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ektf2127.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/elan,elants_i2c.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/fsl-mx25-tcq.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/goodix.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/hideep.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/hycon,hy46xx.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ilitek_ts_i2c.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/imagis,ist3038c.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/imx6ul_tsc.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/lpc32xx-tsc.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/max11801-ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/melfas,mms114.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/mstar,msg2638.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/pixcir,pixcir_ts.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/raspberrypi,firmware-ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/resistive-adc-touch.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/samsung,s6sy761.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/silead,gsl1680.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/sis_i2c.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/sitronix,st1232.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/st,stmfts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/stmpe.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/sx8654.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ti,am3359-tsc.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ti,tsc2005.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/touchscreen.yaml create mode 100644 Documentation/devicetree/bindings/input/touchscreen/ts4800-ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/zet6223.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/zforce_ts.txt create mode 100644 Documentation/devicetree/bindings/input/touchscreen/zinitix,bt400.yaml create mode 100644 Documentation/devicetree/bindings/input/tps65218-pwrbutton.txt create mode 100644 Documentation/devicetree/bindings/input/twl4030-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/twl4030-pwrbutton.txt create mode 100644 Documentation/devicetree/bindings/input/zii,rave-sp-pwrbutton.txt create mode 100644 Documentation/devicetree/bindings/interconnect/fsl,imx8m-noc.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/interconnect.txt create mode 100644 Documentation/devicetree/bindings/interconnect/mediatek,cci.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,bcm-voter.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,msm8974.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,qcm2290.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,rpm.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,rpmh-common.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,rpmh.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sm6350-rpmh.yaml create mode 100644 Documentation/devicetree/bindings/interconnect/samsung,exynos-bus.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/abilis,tb10x-ictl.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/actions,owl-sirq.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/al,alpine-msix.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/allwinner,sun4i-a10-ic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/allwinner,sun6i-a31-r-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,nvic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,versatile-fpga-irq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,vic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/aspeed,ast2400-i2c-ic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/aspeed,ast2400-vic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/aspeed,ast2xxx-scu-ic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/atmel,aic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-l1-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7120-l2-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,l2-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/cdns,xtensa-mx.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/cdns,xtensa-pic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/cirrus,clps711x-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/csky,apb-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/digicolor-ic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ezchip,nps400-ic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/faraday,ftintc010.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,irqsteer.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-scfg-msi.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/google,goldfish-pic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/hisilicon,mbigen-v2.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/idt,32434-pic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/img,pdc-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ingenic,intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/intel,ce4100-ioapic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/intel,ixp4xx-interrupt.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/interrupts.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/kontron,sl28cpld-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,htpic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,htvec.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,liointc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,ls1x-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,pch-msi.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson,pch-pic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/lsi,zevio-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-8k-pic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,gicp.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,icu.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,odmi-controller.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,orion-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,sei.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mediatek,cirq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/microchip,eic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/microchip,pic32-evic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mrvl,intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mscc,ocelot-icpu-intr.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/msi.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mstar,mst-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mti,cpu-interrupt-controller.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mti,gic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nuvoton,wpcm450-aic.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nxp,lpc3220-mic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/open-pic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/opencores,or1k-pic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/openrisc,ompic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qca,ath79-cpu-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qca,ath79-misc-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/rda,8810pl-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtl-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,rza1-irqc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,rzg2l-irqc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/riscv,cpu-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/samsung,exynos4210-combiner.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/samsung,s3c24xx-irq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/snps,arc700-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/snps,archs-idu-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/snps,archs-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/snps,dw-apb-ictl.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/socionext,synquacer-exiu.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/socionext,uniphier-aidet.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/st,spear3xx-shirq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/st,sti-irq-syscfg.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/sunplus,sp7021-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/technologic,ts4800.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,cp-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,keystone-irq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,omap-intc-irq.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,omap2-intc.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml create mode 100644 Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.txt create mode 100644 Documentation/devicetree/bindings/iommu/allwinner,sun50i-h6-iommu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/apple,dart.yaml create mode 100644 Documentation/devicetree/bindings/iommu/apple,sart.yaml create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/iommu.txt create mode 100644 Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/msm,iommu-v0.txt create mode 100644 Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt create mode 100644 Documentation/devicetree/bindings/iommu/qcom,iommu.txt create mode 100644 Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.yaml create mode 100644 Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/samsung,sysmmu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/sprd,iommu.yaml create mode 100644 Documentation/devicetree/bindings/iommu/ti,omap-iommu.txt create mode 100644 Documentation/devicetree/bindings/iommu/xen,grant-dma.yaml create mode 100644 Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.txt create mode 100644 Documentation/devicetree/bindings/ipmi/aspeed,ast2400-kcs-bmc.yaml create mode 100644 Documentation/devicetree/bindings/ipmi/ipmi-ipmb.yaml create mode 100644 Documentation/devicetree/bindings/ipmi/ipmi-smic.yaml create mode 100644 Documentation/devicetree/bindings/ipmi/npcm7xx-kcs-bmc.txt create mode 100644 Documentation/devicetree/bindings/jailhouse.txt create mode 100644 Documentation/devicetree/bindings/leds/ams,as3645a.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/88pm860x.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/common.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/gpio-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/kinetic,ktd253.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/led-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/lp855x.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/max8925-backlight.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/mediatek,mt6370-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/pwm-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/richtek,rt4831-backlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/backlight/sky81452-backlight.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/tps65217-backlight.txt create mode 100644 Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.txt create mode 100644 Documentation/devicetree/bindings/leds/common.txt create mode 100644 Documentation/devicetree/bindings/leds/common.yaml create mode 100644 Documentation/devicetree/bindings/leds/cznic,turris-omnia-leds.yaml create mode 100644 Documentation/devicetree/bindings/leds/irled/gpio-ir-tx.txt create mode 100644 Documentation/devicetree/bindings/leds/irled/pwm-ir-tx.txt create mode 100644 Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt create mode 100644 Documentation/devicetree/bindings/leds/issi,is31fl319x.yaml create mode 100644 Documentation/devicetree/bindings/leds/kinetic,ktd2692.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-an30259a.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-aw2013.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm63138.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm6328.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm6358.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-cpcap.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-cr0014114.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-el15203000.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-gpio.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lgm.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3532.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3601x.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3692x.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3697.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-lp55xx.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-lp8860.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lt3593.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-max77650.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-mt6323.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-mt6360.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-netxbig.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-ns2.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-pca9532.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-pca955x.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-pm8058.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-powernv.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-pwm.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-rt4505.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-sc27xx-bltc.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-sgm3140.yaml create mode 100644 Documentation/devicetree/bindings/leds/leds-spi-byte.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-tlc591xx.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt create mode 100644 Documentation/devicetree/bindings/leds/maxim,max77693.yaml create mode 100644 Documentation/devicetree/bindings/leds/mediatek,mt6370-flashlight.yaml create mode 100644 Documentation/devicetree/bindings/leds/mediatek,mt6370-indicator.yaml create mode 100644 Documentation/devicetree/bindings/leds/pca963x.txt create mode 100644 Documentation/devicetree/bindings/leds/register-bit-led.yaml create mode 100644 Documentation/devicetree/bindings/leds/regulator-led.yaml create mode 100644 Documentation/devicetree/bindings/leds/richtek,rt8515.yaml create mode 100644 Documentation/devicetree/bindings/leds/rohm,bd71828-leds.yaml create mode 100644 Documentation/devicetree/bindings/leds/skyworks,aat1290.yaml create mode 100644 Documentation/devicetree/bindings/leds/ti,tca6507.yaml create mode 100644 Documentation/devicetree/bindings/leds/trigger-source.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/allwinner,sun6i-a31-msgbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/altera-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/amlogic,meson-gxbb-mhu.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/apple,mailbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/arm,mhu.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/brcm,bcm2835-mbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/brcm,iproc-flexrm-mbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/brcm,iproc-pdc-mbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/fsl,mu.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi3660-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/marvell,armada-3700-rwtm-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/mediatek,gce-mailbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/microchip,mpfs-mailbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/mtk,adsp-mbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/rockchip-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/sprd-mailbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/st,stm32-ipcc.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/sti-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/ti,message-manager.txt create mode 100644 Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/ti,secure-proxy.yaml create mode 100644 Documentation/devicetree/bindings/mailbox/xgene-slimpro-mailbox.txt create mode 100644 Documentation/devicetree/bindings/mailbox/xlnx,zynqmp-ipi-mailbox.yaml create mode 100644 Documentation/devicetree/bindings/media/allegro,al5e.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun4i-a10-csi.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun4i-a10-ir.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun50i-h6-vpu-g2.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun6i-a31-csi.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun6i-a31-mipi-csi2.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun8i-a83t-de2-rotate.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun8i-a83t-mipi-csi2.yaml create mode 100644 Documentation/devicetree/bindings/media/allwinner,sun8i-h3-deinterlace.yaml create mode 100644 Documentation/devicetree/bindings/media/amlogic,axg-ge2d.yaml create mode 100644 Documentation/devicetree/bindings/media/amlogic,gx-vdec.yaml create mode 100644 Documentation/devicetree/bindings/media/amlogic,meson-gx-ao-cec.yaml create mode 100644 Documentation/devicetree/bindings/media/amlogic,meson-ir-tx.yaml create mode 100644 Documentation/devicetree/bindings/media/amphion,vpu.yaml create mode 100644 Documentation/devicetree/bindings/media/aspeed-video.txt create mode 100644 Documentation/devicetree/bindings/media/atmel,isc.yaml create mode 100644 Documentation/devicetree/bindings/media/atmel-isi.txt create mode 100644 Documentation/devicetree/bindings/media/cdns,csi2rx.txt create mode 100644 Documentation/devicetree/bindings/media/cdns,csi2tx.txt create mode 100644 Documentation/devicetree/bindings/media/cec-gpio.txt create mode 100644 Documentation/devicetree/bindings/media/cec.txt create mode 100644 Documentation/devicetree/bindings/media/coda.yaml create mode 100644 Documentation/devicetree/bindings/media/exynos-fimc-lite.txt create mode 100644 Documentation/devicetree/bindings/media/exynos4-fimc-is.txt create mode 100644 Documentation/devicetree/bindings/media/fsl-pxp.txt create mode 100644 Documentation/devicetree/bindings/media/fsl-vdoa.txt create mode 100644 Documentation/devicetree/bindings/media/gpio-ir-receiver.yaml create mode 100644 Documentation/devicetree/bindings/media/hix5hd2-ir.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ad5820.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/adp1653.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/adv7180.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/adv7343.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/adv748x.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/adv7604.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ak7375.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/aptina,mt9p031.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/aptina,mt9v111.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/chrontel,ch7322.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/dongwoon,dw9714.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/dongwoon,dw9807-vcm.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/hynix,hi846.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/imi,rdacm2x-gmsl.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/imx219.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/imx258.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/imx290.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/isil,isl79987.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/max2175.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/melexis,mlx90640.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/mipi-ccs.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/mt9m001.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/mt9m111.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/mt9v032.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/onnn,ar0521.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2640.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2659.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2685.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5645.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov7251.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov7670.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov7740.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ov8856.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ov9650.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov02a10.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5647.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5648.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5693.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov8865.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov9282.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/panasonic,amg88xx.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/rda,rda5807.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx214.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx274.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx334.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx335.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx412.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/st,st-mipid02.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/tc358743.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/tda1997x.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ths8200.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/tvp514x.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/tvp5150.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/tvp7002.txt create mode 100644 Documentation/devicetree/bindings/media/img-ir-rev1.txt create mode 100644 Documentation/devicetree/bindings/media/imx.txt create mode 100644 Documentation/devicetree/bindings/media/marvell,mmp2-ccic.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,mdp3-rdma.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,mdp3-rsz.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,mdp3-wrot.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,vcodec-decoder.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek,vcodec-subdev-decoder.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml create mode 100644 Documentation/devicetree/bindings/media/mediatek-mdp.txt create mode 100644 Documentation/devicetree/bindings/media/mediatek-vpu.txt create mode 100644 Documentation/devicetree/bindings/media/meson-ir.txt create mode 100644 Documentation/devicetree/bindings/media/microchip,csi2dc.yaml create mode 100644 Documentation/devicetree/bindings/media/microchip,sama5d4-vdec.yaml create mode 100644 Documentation/devicetree/bindings/media/microchip,xisc.yaml create mode 100644 Documentation/devicetree/bindings/media/mtk-cir.txt create mode 100644 Documentation/devicetree/bindings/media/nokia,n900-ir create mode 100644 Documentation/devicetree/bindings/media/nvidia,tegra-vde.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,dw100.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,imx7-csi.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,imx8mq-mipi-csi2.yaml create mode 100644 Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml create mode 100644 Documentation/devicetree/bindings/media/pxa-camera.txt create mode 100644 Documentation/devicetree/bindings/media/qcom,msm8916-camss.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,msm8916-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,msm8996-camss.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sc7180-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sc7280-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm660-camss.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm845-camss.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm845-venus-v2.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm845-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sm8250-camss.yaml create mode 100644 Documentation/devicetree/bindings/media/qcom,sm8250-venus.yaml create mode 100644 Documentation/devicetree/bindings/media/rc.txt create mode 100644 Documentation/devicetree/bindings/media/rc.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,ceu.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,csi2.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,drif.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,fdp1.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,imr.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,isp.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,jpu.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,vin.yaml create mode 100644 Documentation/devicetree/bindings/media/renesas,vsp1.yaml create mode 100644 Documentation/devicetree/bindings/media/rockchip,rk3568-vepu.yaml create mode 100644 Documentation/devicetree/bindings/media/rockchip,vdec.yaml create mode 100644 Documentation/devicetree/bindings/media/rockchip-isp1.yaml create mode 100644 Documentation/devicetree/bindings/media/rockchip-rga.yaml create mode 100644 Documentation/devicetree/bindings/media/rockchip-vpu.yaml create mode 100644 Documentation/devicetree/bindings/media/s5p-cec.txt create mode 100644 Documentation/devicetree/bindings/media/s5p-mfc.txt create mode 100644 Documentation/devicetree/bindings/media/samsung,exynos5250-gsc.yaml create mode 100644 Documentation/devicetree/bindings/media/samsung,s5pv210-jpeg.yaml create mode 100644 Documentation/devicetree/bindings/media/samsung-fimc.txt create mode 100644 Documentation/devicetree/bindings/media/samsung-mipi-csis.txt create mode 100644 Documentation/devicetree/bindings/media/samsung-s5c73m3.txt create mode 100644 Documentation/devicetree/bindings/media/samsung-s5k5baf.txt create mode 100644 Documentation/devicetree/bindings/media/samsung-s5k6a3.txt create mode 100644 Documentation/devicetree/bindings/media/si470x.txt create mode 100644 Documentation/devicetree/bindings/media/si4713.txt create mode 100644 Documentation/devicetree/bindings/media/spi/sony-cxd2880.txt create mode 100644 Documentation/devicetree/bindings/media/st,st-delta.txt create mode 100644 Documentation/devicetree/bindings/media/st,st-hva.txt create mode 100644 Documentation/devicetree/bindings/media/st,stih4xx.txt create mode 100644 Documentation/devicetree/bindings/media/st,stm32-cec.yaml create mode 100644 Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml create mode 100644 Documentation/devicetree/bindings/media/st,stm32-dma2d.yaml create mode 100644 Documentation/devicetree/bindings/media/st-rc.txt create mode 100644 Documentation/devicetree/bindings/media/stih-cec.txt create mode 100644 Documentation/devicetree/bindings/media/stih407-c8sectpfe.txt create mode 100644 Documentation/devicetree/bindings/media/tegra-cec.txt create mode 100644 Documentation/devicetree/bindings/media/ti,cal.yaml create mode 100644 Documentation/devicetree/bindings/media/ti,da850-vpif.txt create mode 100644 Documentation/devicetree/bindings/media/ti,omap3isp.txt create mode 100644 Documentation/devicetree/bindings/media/ti,vpe.yaml create mode 100644 Documentation/devicetree/bindings/media/ti-am437x-vpfe.txt create mode 100644 Documentation/devicetree/bindings/media/video-interface-devices.yaml create mode 100644 Documentation/devicetree/bindings/media/video-interfaces.txt create mode 100644 Documentation/devicetree/bindings/media/video-interfaces.yaml create mode 100644 Documentation/devicetree/bindings/media/video-mux.yaml create mode 100644 Documentation/devicetree/bindings/media/xilinx/video.txt create mode 100644 Documentation/devicetree/bindings/media/xilinx/xlnx,csi2rxss.yaml create mode 100644 Documentation/devicetree/bindings/media/xilinx/xlnx,v-tc.txt create mode 100644 Documentation/devicetree/bindings/media/xilinx/xlnx,v-tpg.txt create mode 100644 Documentation/devicetree/bindings/media/xilinx/xlnx,video.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/arm,pl172.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/arm,pl353-smc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/atmel,ebi.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/baikal,bt1-l2-ctl.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/calxeda-ddr-ctrlr.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/canaan,k210-sram.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr2-timings.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr2.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr3-timings.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr3.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/exynos-srom.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ddr.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/imx8m-ddrc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/mmdc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ingenic,nemc-peripherals.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ingenic,nemc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/marvell,mvebu-sdram-controller.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/mediatek,mt7621-memc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/mediatek,smi-common.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/mvebu-devbus.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra186-mc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-mc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-emc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-emc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/qca,ath79-ddr-controller.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/renesas,dbsc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/renesas,rpc-if.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/rockchip,rk3399-dmc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/samsung,exynos5422-dmc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti,da8xx-ddrctl.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti,gpmc.yaml create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti-aemif.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti/emif.txt create mode 100644 Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml create mode 100644 Documentation/devicetree/bindings/mfd/88pm860x.txt create mode 100644 Documentation/devicetree/bindings/mfd/act8945a.txt create mode 100644 Documentation/devicetree/bindings/mfd/actions,atc260x.yaml create mode 100644 Documentation/devicetree/bindings/mfd/allwinner,sun4i-a10-ts.yaml create mode 100644 Documentation/devicetree/bindings/mfd/allwinner,sun6i-a31-prcm.yaml create mode 100644 Documentation/devicetree/bindings/mfd/allwinner,sun8i-a23-prcm.yaml create mode 100644 Documentation/devicetree/bindings/mfd/altera-a10sr.txt create mode 100644 Documentation/devicetree/bindings/mfd/as3711.txt create mode 100644 Documentation/devicetree/bindings/mfd/as3722.txt create mode 100644 Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml create mode 100644 Documentation/devicetree/bindings/mfd/aspeed-gfx.txt create mode 100644 Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml create mode 100644 Documentation/devicetree/bindings/mfd/atmel-flexcom.txt create mode 100644 Documentation/devicetree/bindings/mfd/atmel-gpbr.txt create mode 100644 Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt create mode 100644 Documentation/devicetree/bindings/mfd/atmel-matrix.txt create mode 100644 Documentation/devicetree/bindings/mfd/atmel-smc.txt create mode 100644 Documentation/devicetree/bindings/mfd/bfticu.txt create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm59056.txt create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6318-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm63268-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6328-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6358-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6362-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,bcm6368-gpio-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,cru.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt create mode 100644 Documentation/devicetree/bindings/mfd/brcm,iproc-mhb.txt create mode 100644 Documentation/devicetree/bindings/mfd/brcm,misc.yaml create mode 100644 Documentation/devicetree/bindings/mfd/brcm,twd.yaml create mode 100644 Documentation/devicetree/bindings/mfd/canaan,k210-sysctl.yaml create mode 100644 Documentation/devicetree/bindings/mfd/cirrus,lochnagar.yaml create mode 100644 Documentation/devicetree/bindings/mfd/cirrus,madera.yaml create mode 100644 Documentation/devicetree/bindings/mfd/da9052-i2c.txt create mode 100644 Documentation/devicetree/bindings/mfd/da9055.txt create mode 100644 Documentation/devicetree/bindings/mfd/da9062.txt create mode 100644 Documentation/devicetree/bindings/mfd/da9150.txt create mode 100644 Documentation/devicetree/bindings/mfd/delta,tn48m-cpld.yaml create mode 100644 Documentation/devicetree/bindings/mfd/dlg,da9063.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ene-kb3930.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ene-kb930.yaml create mode 100644 Documentation/devicetree/bindings/mfd/fsl,imx8qxp-csr.yaml create mode 100644 Documentation/devicetree/bindings/mfd/fsl-imx25-tsadc.txt create mode 100644 Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml create mode 100644 Documentation/devicetree/bindings/mfd/google,cros-ec.yaml create mode 100644 Documentation/devicetree/bindings/mfd/hi6421.txt create mode 100644 Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt create mode 100644 Documentation/devicetree/bindings/mfd/iqs62x.yaml create mode 100644 Documentation/devicetree/bindings/mfd/khadas,mcu.yaml create mode 100644 Documentation/devicetree/bindings/mfd/kontron,sl28cpld.yaml create mode 100644 Documentation/devicetree/bindings/mfd/lp3943.txt create mode 100644 Documentation/devicetree/bindings/mfd/lp873x.txt create mode 100644 Documentation/devicetree/bindings/mfd/max77620.txt create mode 100644 Documentation/devicetree/bindings/mfd/max77650.yaml create mode 100644 Documentation/devicetree/bindings/mfd/max8925.txt create mode 100644 Documentation/devicetree/bindings/mfd/max8998.txt create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max14577.yaml create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77686.yaml create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77693.yaml create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77714.yaml create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77802.yaml create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77843.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mc13xxx.txt create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mt6360.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mt6370.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mt8195-scpsys.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mfd.txt create mode 100644 Documentation/devicetree/bindings/mfd/motorola-cpcap.txt create mode 100644 Documentation/devicetree/bindings/mfd/mps,mp2629.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mscc,ocelot.yaml create mode 100644 Documentation/devicetree/bindings/mfd/mt6397.txt create mode 100644 Documentation/devicetree/bindings/mfd/mxs-lradc.txt create mode 100644 Documentation/devicetree/bindings/mfd/netronix,ntxec.yaml create mode 100644 Documentation/devicetree/bindings/mfd/omap-usb-host.txt create mode 100644 Documentation/devicetree/bindings/mfd/omap-usb-tll.txt create mode 100644 Documentation/devicetree/bindings/mfd/palmas.txt create mode 100644 Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml create mode 100644 Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/qcom,tcsr.yaml create mode 100644 Documentation/devicetree/bindings/mfd/qcom-pm8xxx.yaml create mode 100644 Documentation/devicetree/bindings/mfd/qcom-rpm.txt create mode 100644 Documentation/devicetree/bindings/mfd/qriox.txt create mode 100644 Documentation/devicetree/bindings/mfd/retu.txt create mode 100644 Documentation/devicetree/bindings/mfd/richtek,rt4831.yaml create mode 100644 Documentation/devicetree/bindings/mfd/richtek,rt5120.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ricoh,rn5t618.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk805.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk808.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk817.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rockchip,rk818.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71815-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71847-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd9571mwv.yaml create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd9576-pmic.yaml create mode 100644 Documentation/devicetree/bindings/mfd/samsung,exynos5433-lpass.yaml create mode 100644 Documentation/devicetree/bindings/mfd/samsung,s2mpa01.yaml create mode 100644 Documentation/devicetree/bindings/mfd/samsung,s2mps11.yaml create mode 100644 Documentation/devicetree/bindings/mfd/samsung,s5m8767.yaml create mode 100644 Documentation/devicetree/bindings/mfd/silergy,sy7636a.yaml create mode 100644 Documentation/devicetree/bindings/mfd/sky81452.txt create mode 100644 Documentation/devicetree/bindings/mfd/sprd,sc27xx-pmic.txt create mode 100644 Documentation/devicetree/bindings/mfd/sprd,ums512-glbreg.yaml create mode 100644 Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml create mode 100644 Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml create mode 100644 Documentation/devicetree/bindings/mfd/st,stmfx.yaml create mode 100644 Documentation/devicetree/bindings/mfd/st,stpmic1.yaml create mode 100644 Documentation/devicetree/bindings/mfd/stericsson,ab8500.yaml create mode 100644 Documentation/devicetree/bindings/mfd/stericsson,db8500-prcmu.yaml create mode 100644 Documentation/devicetree/bindings/mfd/stmpe.txt create mode 100644 Documentation/devicetree/bindings/mfd/syscon.yaml create mode 100644 Documentation/devicetree/bindings/mfd/tc3589x.txt create mode 100644 Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti,lp87561-q1.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti,lp87565-q1.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti,tps65086.yaml create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt create mode 100644 Documentation/devicetree/bindings/mfd/ti-lmu.txt create mode 100644 Documentation/devicetree/bindings/mfd/tps6105x.txt create mode 100644 Documentation/devicetree/bindings/mfd/tps6507x.txt create mode 100644 Documentation/devicetree/bindings/mfd/tps65910.txt create mode 100644 Documentation/devicetree/bindings/mfd/tps65912.txt create mode 100644 Documentation/devicetree/bindings/mfd/twl-family.txt create mode 100644 Documentation/devicetree/bindings/mfd/twl4030-audio.txt create mode 100644 Documentation/devicetree/bindings/mfd/twl4030-power.txt create mode 100644 Documentation/devicetree/bindings/mfd/twl6040.txt create mode 100644 Documentation/devicetree/bindings/mfd/wlf,arizona.yaml create mode 100644 Documentation/devicetree/bindings/mfd/wm831x.txt create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,ac100.yaml create mode 100644 Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml create mode 100644 Documentation/devicetree/bindings/mfd/xylon,logicvc.yaml create mode 100644 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt create mode 100644 Documentation/devicetree/bindings/mips/ath79-soc.txt create mode 100644 Documentation/devicetree/bindings/mips/brcm/brcm,bmips.txt create mode 100644 Documentation/devicetree/bindings/mips/brcm/soc.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/bootbus.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/cib.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/ciu.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/ciu2.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/ciu3.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/dma-engine.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/sata-uctl.txt create mode 100644 Documentation/devicetree/bindings/mips/cavium/uctl.txt create mode 100644 Documentation/devicetree/bindings/mips/img/pistachio-marduk.txt create mode 100644 Documentation/devicetree/bindings/mips/img/pistachio.txt create mode 100644 Documentation/devicetree/bindings/mips/img/xilfpga.txt create mode 100644 Documentation/devicetree/bindings/mips/ingenic/devices.yaml create mode 100644 Documentation/devicetree/bindings/mips/ingenic/ingenic,cpu.yaml create mode 100644 Documentation/devicetree/bindings/mips/lantiq/fpi-bus.txt create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,cgu.yaml create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,dma-xway.yaml create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,ebu.yaml create mode 100644 Documentation/devicetree/bindings/mips/lantiq/lantiq,pmu.yaml create mode 100644 Documentation/devicetree/bindings/mips/lantiq/rcu.txt create mode 100644 Documentation/devicetree/bindings/mips/loongson/devices.yaml create mode 100644 Documentation/devicetree/bindings/mips/loongson/ls2k-reset.yaml create mode 100644 Documentation/devicetree/bindings/mips/loongson/rs780e-acpi.yaml create mode 100644 Documentation/devicetree/bindings/mips/mscc.txt create mode 100644 Documentation/devicetree/bindings/mips/ni.txt create mode 100644 Documentation/devicetree/bindings/mips/pic32/microchip,pic32mzda.txt create mode 100644 Documentation/devicetree/bindings/mips/ralink.yaml create mode 100644 Documentation/devicetree/bindings/mips/realtek-rtl.yaml create mode 100644 Documentation/devicetree/bindings/misc/aspeed,cvic.txt create mode 100644 Documentation/devicetree/bindings/misc/aspeed-p2a-ctrl.txt create mode 100644 Documentation/devicetree/bindings/misc/atmel-ssc.txt create mode 100644 Documentation/devicetree/bindings/misc/brcm,kona-smc.txt create mode 100644 Documentation/devicetree/bindings/misc/fsl,dpaa2-console.yaml create mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt create mode 100644 Documentation/devicetree/bindings/misc/ge-achc.yaml create mode 100644 Documentation/devicetree/bindings/misc/idt_89hpesx.txt create mode 100644 Documentation/devicetree/bindings/misc/ifm-csi.txt create mode 100644 Documentation/devicetree/bindings/misc/intel,ixp4xx-ahb-queue-manager.yaml create mode 100644 Documentation/devicetree/bindings/misc/lwn-bk4.txt create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra186-misc.yaml create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.yaml create mode 100644 Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml create mode 100644 Documentation/devicetree/bindings/misc/pvpanic-mmio.txt create mode 100644 Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml create mode 100644 Documentation/devicetree/bindings/misc/qemu,vcpu-stall-detector.yaml create mode 100644 Documentation/devicetree/bindings/misc/xlnx,sd-fec.txt create mode 100644 Documentation/devicetree/bindings/mmc/allwinner,sun4i-a10-mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/amlogic,meson-gx.txt create mode 100644 Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdhc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.txt create mode 100644 Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/arm,pl18x.yaml create mode 100644 Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/atmel-hsmci.txt create mode 100644 Documentation/devicetree/bindings/mmc/bluefield-dw-mshc.txt create mode 100644 Documentation/devicetree/bindings/mmc/brcm,bcm2835-sdhost.txt create mode 100644 Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/brcm,kona-sdhci.txt create mode 100644 Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml create mode 100644 Documentation/devicetree/bindings/mmc/cavium-mmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/davinci_mmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/fsl-esdhc.txt create mode 100644 Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/fsl-imx-mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/hi3798cv200-dw-mshc.txt create mode 100644 Documentation/devicetree/bindings/mmc/ingenic,mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt create mode 100644 Documentation/devicetree/bindings/mmc/litex,mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/marvell,dove-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml create mode 100644 Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/microchip,dw-sparx5-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/microchip,sdhci-pic32.txt create mode 100644 Documentation/devicetree/bindings/mmc/mmc-card.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc-controller.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc-pwrseq-emmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc-pwrseq-sd8787.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc-pwrseq-simple.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/moxa,moxart-mmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/mtk-sd.yaml create mode 100644 Documentation/devicetree/bindings/mmc/mxs-mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/owl-mmc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/pxa-mmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/renesas,mmcif.yaml create mode 100644 Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml create mode 100644 Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/samsung,exynos-dw-mshc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/samsung,s3c6410-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/samsung,s3cmci.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-am654.yaml create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-atmel.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-msm.yaml create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-omap.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-pxa.yaml create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-spear.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-sprd.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-st.txt create mode 100644 Documentation/devicetree/bindings/mmc/sdhci.txt create mode 100644 Documentation/devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml create mode 100644 Documentation/devicetree/bindings/mmc/socionext,uniphier-sd.yaml create mode 100644 Documentation/devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml create mode 100644 Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml create mode 100644 Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt create mode 100644 Documentation/devicetree/bindings/mmc/ti-omap.txt create mode 100644 Documentation/devicetree/bindings/mmc/usdhi6rol0.txt create mode 100644 Documentation/devicetree/bindings/mmc/vt8500-sdmmc.txt create mode 100644 Documentation/devicetree/bindings/mtd/allwinner,sun4i-a10-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/arasan,nand-controller.yaml create mode 100644 Documentation/devicetree/bindings/mtd/arm,pl353-nand-r2p1.yaml create mode 100644 Documentation/devicetree/bindings/mtd/atmel-dataflash.txt create mode 100644 Documentation/devicetree/bindings/mtd/atmel-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt create mode 100644 Documentation/devicetree/bindings/mtd/davinci-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/denali,nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/diskonchip.txt create mode 100644 Documentation/devicetree/bindings/mtd/flctl-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/fsl-upm-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/fsmc-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/gpio-control-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/gpmi-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/hisi504-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/hisilicon,fmc-spi-nor.txt create mode 100644 Documentation/devicetree/bindings/mtd/ibm,ndfc.txt create mode 100644 Documentation/devicetree/bindings/mtd/ingenic,nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/intel,lgm-ebunand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml create mode 100644 Documentation/devicetree/bindings/mtd/lpc32xx-mlc.txt create mode 100644 Documentation/devicetree/bindings/mtd/lpc32xx-slc.txt create mode 100644 Documentation/devicetree/bindings/mtd/marvell-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/microchip,mchp23k256.txt create mode 100644 Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml create mode 100644 Documentation/devicetree/bindings/mtd/mtd-physmap.yaml create mode 100644 Documentation/devicetree/bindings/mtd/mtd.yaml create mode 100644 Documentation/devicetree/bindings/mtd/mtk-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/mxc-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/mxic-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/mxicy,nand-ecc-engine.yaml create mode 100644 Documentation/devicetree/bindings/mtd/nand-chip.yaml create mode 100644 Documentation/devicetree/bindings/mtd/nand-controller.yaml create mode 100644 Documentation/devicetree/bindings/mtd/nand-macronix.txt create mode 100644 Documentation/devicetree/bindings/mtd/nvidia-tegra20-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/nxp-spifi.txt create mode 100644 Documentation/devicetree/bindings/mtd/orion-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/oxnas-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/partition.txt create mode 100644 Documentation/devicetree/bindings/mtd/partitions/arm,arm-firmware-suite.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm4908-partitions.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm963xx-imagetag.txt create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt create mode 100644 Documentation/devicetree/bindings/mtd/partitions/fixed-partitions.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/linksys,ns-partitions.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/nvmem-cells.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/partition.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/qcom,smem-part.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/redboot-fis.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/u-boot.yaml create mode 100644 Documentation/devicetree/bindings/mtd/qcom,nandc.yaml create mode 100644 Documentation/devicetree/bindings/mtd/renesas-nandc.yaml create mode 100644 Documentation/devicetree/bindings/mtd/rockchip,nand-controller.yaml create mode 100644 Documentation/devicetree/bindings/mtd/samsung-s3c2410.txt create mode 100644 Documentation/devicetree/bindings/mtd/spear_smi.txt create mode 100644 Documentation/devicetree/bindings/mtd/spi-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/st,stm32-fmc2-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/st-fsm.txt create mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.yaml create mode 100644 Documentation/devicetree/bindings/mtd/ti,elm.yaml create mode 100644 Documentation/devicetree/bindings/mtd/ti,gpmc-nand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/ti,gpmc-onenand.yaml create mode 100644 Documentation/devicetree/bindings/mtd/vf610-nfc.txt create mode 100644 Documentation/devicetree/bindings/mux/adi,adg792a.txt create mode 100644 Documentation/devicetree/bindings/mux/adi,adgs1408.txt create mode 100644 Documentation/devicetree/bindings/mux/gpio-mux.yaml create mode 100644 Documentation/devicetree/bindings/mux/mux-consumer.yaml create mode 100644 Documentation/devicetree/bindings/mux/mux-controller.yaml create mode 100644 Documentation/devicetree/bindings/mux/reg-mux.yaml create mode 100644 Documentation/devicetree/bindings/net/actions,owl-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/adi,adin.yaml create mode 100644 Documentation/devicetree/bindings/net/adi,adin1110.yaml create mode 100644 Documentation/devicetree/bindings/net/allwinner,sun4i-a10-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/allwinner,sun4i-a10-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/allwinner,sun7i-a20-gmac.yaml create mode 100644 Documentation/devicetree/bindings/net/allwinner,sun8i-a83t-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/altr,tse.yaml create mode 100644 Documentation/devicetree/bindings/net/amd-xgbe.txt create mode 100644 Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/anarion-gmac.txt create mode 100644 Documentation/devicetree/bindings/net/apm-xgene-enet.txt create mode 100644 Documentation/devicetree/bindings/net/apm-xgene-mdio.txt create mode 100644 Documentation/devicetree/bindings/net/arc_emac.txt create mode 100644 Documentation/devicetree/bindings/net/asix,ax88178.yaml create mode 100644 Documentation/devicetree/bindings/net/asix,ax88796c.yaml create mode 100644 Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/bluetooth.txt create mode 100644 Documentation/devicetree/bindings/net/brcm,amac.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm4908-enet.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm6368-mdio-mux.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm7445-switch-v4.0.txt create mode 100644 Documentation/devicetree/bindings/net/brcm,bcmgenet.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,iproc-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,systemport.yaml create mode 100644 Documentation/devicetree/bindings/net/brcm,unimac-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/broadcom-bcm87xx.txt create mode 100644 Documentation/devicetree/bindings/net/broadcom-bluetooth.yaml create mode 100644 Documentation/devicetree/bindings/net/btusb.txt create mode 100644 Documentation/devicetree/bindings/net/calxeda-xgmac.yaml create mode 100644 Documentation/devicetree/bindings/net/can/allwinner,sun4i-a10-can.yaml create mode 100644 Documentation/devicetree/bindings/net/can/atmel-can.txt create mode 100644 Documentation/devicetree/bindings/net/can/bosch,c_can.yaml create mode 100644 Documentation/devicetree/bindings/net/can/bosch,m_can.yaml create mode 100644 Documentation/devicetree/bindings/net/can/can-controller.yaml create mode 100644 Documentation/devicetree/bindings/net/can/can-transceiver.yaml create mode 100644 Documentation/devicetree/bindings/net/can/cc770.txt create mode 100644 Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml create mode 100644 Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml create mode 100644 Documentation/devicetree/bindings/net/can/grcan.txt create mode 100644 Documentation/devicetree/bindings/net/can/holt_hi311x.txt create mode 100644 Documentation/devicetree/bindings/net/can/ifi_canfd.txt create mode 100644 Documentation/devicetree/bindings/net/can/microchip,mcp251x.txt create mode 100644 Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml create mode 100644 Documentation/devicetree/bindings/net/can/microchip,mpfs-can.yaml create mode 100644 Documentation/devicetree/bindings/net/can/mpc5xxx-mscan.txt create mode 100644 Documentation/devicetree/bindings/net/can/nxp,sja1000.yaml create mode 100644 Documentation/devicetree/bindings/net/can/renesas,rcar-can.yaml create mode 100644 Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml create mode 100644 Documentation/devicetree/bindings/net/can/tcan4x5x.txt create mode 100644 Documentation/devicetree/bindings/net/can/ti_hecc.txt create mode 100644 Documentation/devicetree/bindings/net/can/xilinx,can.yaml create mode 100644 Documentation/devicetree/bindings/net/cavium-mdio.txt create mode 100644 Documentation/devicetree/bindings/net/cavium-mix.txt create mode 100644 Documentation/devicetree/bindings/net/cavium-pip.txt create mode 100644 Documentation/devicetree/bindings/net/cdns,macb.yaml create mode 100644 Documentation/devicetree/bindings/net/cirrus,cs89x0.txt create mode 100644 Documentation/devicetree/bindings/net/cortina,gemini-ethernet.yaml create mode 100644 Documentation/devicetree/bindings/net/cortina.txt create mode 100644 Documentation/devicetree/bindings/net/cpsw-phy-sel.txt create mode 100644 Documentation/devicetree/bindings/net/cpsw.txt create mode 100644 Documentation/devicetree/bindings/net/davicom,dm9051.yaml create mode 100644 Documentation/devicetree/bindings/net/davicom-dm9000.txt create mode 100644 Documentation/devicetree/bindings/net/davinci_emac.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/ar9331.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/arrow,xrs700x.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/brcm,b53.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/brcm,sf2.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/dsa-port.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/dsa.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/dsa.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/hirschmann,hellcreek.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/lan9303.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/lantiq-gswip.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/marvell.txt create mode 100644 Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/microchip,lan937x.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/mscc,ocelot.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/qca8k.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/realtek.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/renesas,rzn1-a5psw.yaml create mode 100644 Documentation/devicetree/bindings/net/dsa/vitesse,vsc73xx.txt create mode 100644 Documentation/devicetree/bindings/net/engleder,tsnep.yaml create mode 100644 Documentation/devicetree/bindings/net/ethernet-controller.yaml create mode 100644 Documentation/devicetree/bindings/net/ethernet-phy.yaml create mode 100644 Documentation/devicetree/bindings/net/ethernet.txt create mode 100644 Documentation/devicetree/bindings/net/ezchip_enet.txt create mode 100644 Documentation/devicetree/bindings/net/faraday,ftmac.txt create mode 100644 Documentation/devicetree/bindings/net/fixed-link.txt create mode 100644 Documentation/devicetree/bindings/net/fsl,fec.yaml create mode 100644 Documentation/devicetree/bindings/net/fsl,fman-dtsec.yaml create mode 100644 Documentation/devicetree/bindings/net/fsl,qoriq-mc-dpmac.yaml create mode 100644 Documentation/devicetree/bindings/net/fsl-enetc.txt create mode 100644 Documentation/devicetree/bindings/net/fsl-fman.txt create mode 100644 Documentation/devicetree/bindings/net/fsl-tsec-phy.txt create mode 100644 Documentation/devicetree/bindings/net/ftgmac100.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-femac-mdio.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-femac.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-hip04-net.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-hix5hd2-gmac.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-hns-mdio.txt create mode 100644 Documentation/devicetree/bindings/net/hisilicon-hns-nic.txt create mode 100644 Documentation/devicetree/bindings/net/ibm,emac.txt create mode 100644 Documentation/devicetree/bindings/net/icplus-ip101ag.txt create mode 100644 Documentation/devicetree/bindings/net/idt,3243x-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/ieee802154/adf7242.txt create mode 100644 Documentation/devicetree/bindings/net/ieee802154/at86rf230.txt create mode 100644 Documentation/devicetree/bindings/net/ieee802154/ca8210.txt create mode 100644 Documentation/devicetree/bindings/net/ieee802154/cc2520.txt create mode 100644 Documentation/devicetree/bindings/net/ieee802154/mcr20a.txt create mode 100644 Documentation/devicetree/bindings/net/ieee802154/mrf24j40.txt create mode 100644 Documentation/devicetree/bindings/net/ingenic,mac.yaml create mode 100644 Documentation/devicetree/bindings/net/intel,dwmac-plat.yaml create mode 100644 Documentation/devicetree/bindings/net/intel,ixp46x-ptp-timer.yaml create mode 100644 Documentation/devicetree/bindings/net/intel,ixp4xx-ethernet.yaml create mode 100644 Documentation/devicetree/bindings/net/intel,ixp4xx-hss.yaml create mode 100644 Documentation/devicetree/bindings/net/ipq806x-dwmac.txt create mode 100644 Documentation/devicetree/bindings/net/keystone-netcp.txt create mode 100644 Documentation/devicetree/bindings/net/lantiq,etop-xway.yaml create mode 100644 Documentation/devicetree/bindings/net/lantiq,xrx200-net.yaml create mode 100644 Documentation/devicetree/bindings/net/litex,liteeth.yaml create mode 100644 Documentation/devicetree/bindings/net/lpc-eth.txt create mode 100644 Documentation/devicetree/bindings/net/marvell,mvusb.yaml create mode 100644 Documentation/devicetree/bindings/net/marvell,orion-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/marvell,prestera.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-armada-370-neta.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-bluetooth.yaml create mode 100644 Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-neta-bm.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-orion-net.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-pp2.txt create mode 100644 Documentation/devicetree/bindings/net/marvell-pxa168.txt create mode 100644 Documentation/devicetree/bindings/net/maxim,ds26522.txt create mode 100644 Documentation/devicetree/bindings/net/mctp-i2c-controller.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio-gpio.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-gpio.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-meson-g12a.txt create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-mmioreg.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-multiplexer.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio-mux.yaml create mode 100644 Documentation/devicetree/bindings/net/mdio.txt create mode 100644 Documentation/devicetree/bindings/net/mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/mediatek,net.yaml create mode 100644 Documentation/devicetree/bindings/net/mediatek,star-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/mediatek-bluetooth.txt create mode 100644 Documentation/devicetree/bindings/net/mediatek-dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/micrel,ks8851.yaml create mode 100644 Documentation/devicetree/bindings/net/micrel-ks8995.txt create mode 100644 Documentation/devicetree/bindings/net/micrel-ksz90x1.txt create mode 100644 Documentation/devicetree/bindings/net/micrel.txt create mode 100644 Documentation/devicetree/bindings/net/microchip,enc28j60.txt create mode 100644 Documentation/devicetree/bindings/net/microchip,lan78xx.txt create mode 100644 Documentation/devicetree/bindings/net/microchip,lan95xx.yaml create mode 100644 Documentation/devicetree/bindings/net/microchip,lan966x-switch.yaml create mode 100644 Documentation/devicetree/bindings/net/microchip,sparx5-switch.yaml create mode 100644 Documentation/devicetree/bindings/net/mscc,miim.yaml create mode 100644 Documentation/devicetree/bindings/net/mscc,vsc7514-switch.yaml create mode 100644 Documentation/devicetree/bindings/net/mscc-phy-vsc8531.txt create mode 100644 Documentation/devicetree/bindings/net/nfc/marvell,nci.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/nxp,nci.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/nxp,pn532.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/nxp,pn544.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/samsung,s3fwrn5.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/st,st-nci.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/st,st21nfca.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/st,st95hf.yaml create mode 100644 Documentation/devicetree/bindings/net/nfc/ti,trf7970a.yaml create mode 100644 Documentation/devicetree/bindings/net/nixge.txt create mode 100644 Documentation/devicetree/bindings/net/nokia-bluetooth.txt create mode 100644 Documentation/devicetree/bindings/net/nvidia,tegra234-mgbe.yaml create mode 100644 Documentation/devicetree/bindings/net/nxp,dwmac-imx.yaml create mode 100644 Documentation/devicetree/bindings/net/nxp,lpc1850-dwmac.txt create mode 100644 Documentation/devicetree/bindings/net/nxp,tja11xx.yaml create mode 100644 Documentation/devicetree/bindings/net/opencores-ethoc.txt create mode 100644 Documentation/devicetree/bindings/net/oxnas-dwmac.txt create mode 100644 Documentation/devicetree/bindings/net/pcs/renesas,rzn1-miic.yaml create mode 100644 Documentation/devicetree/bindings/net/phy.txt create mode 100644 Documentation/devicetree/bindings/net/pse-pd/podl-pse-regulator.yaml create mode 100644 Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml create mode 100644 Documentation/devicetree/bindings/net/qca,ar71xx.yaml create mode 100644 Documentation/devicetree/bindings/net/qca,ar803x.yaml create mode 100644 Documentation/devicetree/bindings/net/qca,qca7000.txt create mode 100644 Documentation/devicetree/bindings/net/qcom,bam-dmux.yaml create mode 100644 Documentation/devicetree/bindings/net/qcom,ethqos.txt create mode 100644 Documentation/devicetree/bindings/net/qcom,ipa.yaml create mode 100644 Documentation/devicetree/bindings/net/qcom,ipq4019-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/qcom,ipq8064-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/qcom-emac.txt create mode 100644 Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml create mode 100644 Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml create mode 100644 Documentation/devicetree/bindings/net/realtek-bluetooth.yaml create mode 100644 Documentation/devicetree/bindings/net/renesas,ether.yaml create mode 100644 Documentation/devicetree/bindings/net/renesas,etheravb.yaml create mode 100644 Documentation/devicetree/bindings/net/rockchip,emac.yaml create mode 100644 Documentation/devicetree/bindings/net/rockchip-dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/samsung-sxgbe.txt create mode 100644 Documentation/devicetree/bindings/net/sff,sfp.yaml create mode 100644 Documentation/devicetree/bindings/net/smsc,lan9115.yaml create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml create mode 100644 Documentation/devicetree/bindings/net/smsc-lan87xx.txt create mode 100644 Documentation/devicetree/bindings/net/snps,dwc-qos-ethernet.txt create mode 100644 Documentation/devicetree/bindings/net/snps,dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/socfpga-dwmac.txt create mode 100644 Documentation/devicetree/bindings/net/socionext,uniphier-ave4.yaml create mode 100644 Documentation/devicetree/bindings/net/socionext-netsec.txt create mode 100644 Documentation/devicetree/bindings/net/sti-dwmac.txt create mode 100644 Documentation/devicetree/bindings/net/stm32-dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/stmmac.txt create mode 100644 Documentation/devicetree/bindings/net/sunplus,sp7021-emac.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,bluetooth.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,cpsw-switch.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,davinci-mdio.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,dp83822.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,dp83867.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,dp83869.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.yaml create mode 100644 Documentation/devicetree/bindings/net/ti,k3-am654-cpts.yaml create mode 100644 Documentation/devicetree/bindings/net/toshiba,visconti-dwmac.yaml create mode 100644 Documentation/devicetree/bindings/net/vertexcom-mse102x.yaml create mode 100644 Documentation/devicetree/bindings/net/via-rhine.txt create mode 100644 Documentation/devicetree/bindings/net/via-velocity.txt create mode 100644 Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/esp,esp8089.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/ieee80211.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt create mode 100644 Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/microchip,wilc1000.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt create mode 100644 Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/silabs,wfx.yaml create mode 100644 Documentation/devicetree/bindings/net/wireless/ti,wl1251.txt create mode 100644 Documentation/devicetree/bindings/net/wireless/ti,wlcore.yaml create mode 100644 Documentation/devicetree/bindings/net/wiznet,w5x00.txt create mode 100644 Documentation/devicetree/bindings/net/xilinx_axienet.txt create mode 100644 Documentation/devicetree/bindings/net/xilinx_gmii2rgmii.txt create mode 100644 Documentation/devicetree/bindings/net/xlnx,emaclite.yaml create mode 100644 Documentation/devicetree/bindings/nios2/nios2.txt create mode 100644 Documentation/devicetree/bindings/numa.txt create mode 100644 Documentation/devicetree/bindings/nvme/apple,nvme-ans.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/allwinner,sun4i-a10-sid.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt create mode 100644 Documentation/devicetree/bindings/nvmem/amlogic-meson-mx-efuse.txt create mode 100644 Documentation/devicetree/bindings/nvmem/apple,efuses.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,ocotp.txt create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,scu-ocotp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/imx-iim.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/ingenic,jz4780-efuse.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1850-otp.txt create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt create mode 100644 Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/mxs-ocotp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/nintendo-otp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/nvmem.txt create mode 100644 Documentation/devicetree/bindings/nvmem/nvmem.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,spmi-sdam.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/rmem.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/rockchip-efuse.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/rockchip-otp.txt create mode 100644 Documentation/devicetree/bindings/nvmem/sc27xx-efuse.txt create mode 100644 Documentation/devicetree/bindings/nvmem/snvs-lpgpr.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/socionext,uniphier-efuse.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/sprd-efuse.txt create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/sunplus,sp7021-ocotp.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/u-boot,env.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt create mode 100644 Documentation/devicetree/bindings/nvmem/xlnx,zynqmp-nvmem.txt create mode 100644 Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt create mode 100644 Documentation/devicetree/bindings/openrisc/opencores/or1ksim.txt create mode 100644 Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml create mode 100644 Documentation/devicetree/bindings/opp/opp-v1.yaml create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-base.yaml create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml create mode 100644 Documentation/devicetree/bindings/opp/opp-v2.yaml create mode 100644 Documentation/devicetree/bindings/opp/ti-omap5-opp-supply.txt create mode 100644 Documentation/devicetree/bindings/pci/83xx-512x-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/aardvark-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie-msi.txt create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/apple,pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/brcm,iproc-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/cdns,cdns-pcie-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/cdns-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/cdns-pcie-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/cdns-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/faraday,ftpci100.yaml create mode 100644 Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/fsl,pci.txt create mode 100644 Documentation/devicetree/bindings/pci/hisilicon,kirin-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/hisilicon-histb-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/host-generic-pci.yaml create mode 100644 Documentation/devicetree/bindings/pci/intel,ixp4xx-pci.yaml create mode 100644 Documentation/devicetree/bindings/pci/intel,keembay-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/intel,keembay-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/intel-gw-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/layerscape-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/layerscape-pcie-gen4.txt create mode 100644 Documentation/devicetree/bindings/pci/loongson.yaml create mode 100644 Documentation/devicetree/bindings/pci/mediatek,mt7621-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/mediatek-pcie-cfg.yaml create mode 100644 Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml create mode 100644 Documentation/devicetree/bindings/pci/mediatek-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/microchip,pcie-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/mobiveil-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/mvebu-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/pci-armada8k.txt create mode 100644 Documentation/devicetree/bindings/pci/pci-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/pci-iommu.txt create mode 100644 Documentation/devicetree/bindings/pci/pci-msi.txt create mode 100644 Documentation/devicetree/bindings/pci/pci.txt create mode 100644 Documentation/devicetree/bindings/pci/pcie-al.txt create mode 100644 Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/qcom,pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/ralink,rt3883-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/rcar-pci-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/rcar-pci-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/renesas,pci-rcar-gen2.yaml create mode 100644 Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/rockchip-pcie-ep.txt create mode 100644 Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt create mode 100644 Documentation/devicetree/bindings/pci/samsung,exynos-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/socionext,uniphier-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/socionext,uniphier-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/spear13xx-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/ti,am65-pci-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/ti,am65-pci-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/ti,j721e-pci-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml create mode 100644 Documentation/devicetree/bindings/pci/ti-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/toshiba,visconti-pcie.yaml create mode 100644 Documentation/devicetree/bindings/pci/v3-v360epc-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/versatile.yaml create mode 100644 Documentation/devicetree/bindings/pci/xgene-pci-msi.txt create mode 100644 Documentation/devicetree/bindings/pci/xgene-pci.txt create mode 100644 Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/xilinx-pcie.txt create mode 100644 Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml create mode 100644 Documentation/devicetree/bindings/peci/peci-aspeed.yaml create mode 100644 Documentation/devicetree/bindings/peci/peci-controller.yaml create mode 100644 Documentation/devicetree/bindings/perf/apm-xgene-pmu.txt create mode 100644 Documentation/devicetree/bindings/perf/arm,ccn.yaml create mode 100644 Documentation/devicetree/bindings/perf/arm,cmn.yaml create mode 100644 Documentation/devicetree/bindings/perf/arm,dsu-pmu.yaml create mode 100644 Documentation/devicetree/bindings/perf/arm,smmu-v3-pmcg.yaml create mode 100644 Documentation/devicetree/bindings/perf/fsl-imx-ddr.yaml create mode 100644 Documentation/devicetree/bindings/perf/marvell-cn10k-ddr.yaml create mode 100644 Documentation/devicetree/bindings/perf/marvell-cn10k-tad.yaml create mode 100644 Documentation/devicetree/bindings/perf/spe-pmu.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun4i-a10-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun50i-a64-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun50i-h6-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun50i-h6-usb3-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun5i-a13-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun6i-a31-mipi-dphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun6i-a31-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-a23-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-a83t-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-h3-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-r40-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun8i-v3s-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/allwinner,sun9i-a80-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,axg-mipi-dphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,g12a-mipi-dphy-analog.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,g12a-usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,g12a-usb3-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,meson-axg-mipi-pcie-analog.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,meson-axg-pcie.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,meson8-hdmi-tx-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/amlogic,meson8b-usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/apm-xgene-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/bcm-ns-usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/berlin-sata-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/berlin-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/brcm,brcmstb-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/brcm,kona-usb2-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-drd-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/brcm,ns2-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/brcm,sata-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/calxeda-combophy.yaml create mode 100644 Documentation/devicetree/bindings/phy/cdns,dphy-rx.yaml create mode 100644 Documentation/devicetree/bindings/phy/cdns,dphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/cdns,salvo-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/dm816x-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/fsl,imx8qm-lvds-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/fsl,lynx-28g.yaml create mode 100644 Documentation/devicetree/bindings/phy/hisilicon,hi3660-usb3.yaml create mode 100644 Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml create mode 100644 Documentation/devicetree/bindings/phy/hisilicon,phy-hi3670-pcie.yaml create mode 100644 Documentation/devicetree/bindings/phy/hix5hd2-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/ingenic,phy-usb.yaml create mode 100644 Documentation/devicetree/bindings/phy/intel,combo-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/intel,keembay-phy-usb.yaml create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/intel,phy-thunderbay-emmc.yaml create mode 100644 Documentation/devicetree/bindings/phy/keystone-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/lantiq,vrx200-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/marvell,armada-cp110-utmi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/marvell,mmp3-hsic-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/marvell,mmp3-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,hdmi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,tphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,ufs-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mediatek,xsphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/meson-gxl-usb2-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/microchip,lan966x-serdes.yaml create mode 100644 Documentation/devicetree/bindings/phy/microchip,sparx5-serdes.yaml create mode 100644 Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/mscc,vsc7514-serdes.yaml create mode 100644 Documentation/devicetree/bindings/phy/mxs-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt create mode 100644 Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-armada38x-comphy.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-ath79-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-bindings.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-sierra.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-cpcap-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-da8xx-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-hi3798cv200-combphy.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-hi6220-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-lantiq-rcu-usb2.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-lpc18xx-usb-otg.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-mapphone-mdm6600.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-miphy28lp.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-miphy365x.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-mvebu.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-pxa-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-inno-hdmi.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-naneng-combphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-stih407-usb.txt create mode 100644 Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml create mode 100644 Documentation/devicetree/bindings/phy/phy-tegra194-p2u.yaml create mode 100644 Documentation/devicetree/bindings/phy/pistachio-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/pxa1928-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom,edp-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,hdmi-phy-other.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,hdmi-phy-qmp.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,ipq806x-usb-phy-hs.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,ipq806x-usb-phy-ss.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,msm8996-qmp-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,qmp-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,qmp-ufs-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,qmp-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hs-28nm.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hs-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-snps-femto-v2.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-ss.yaml create mode 100644 Documentation/devicetree/bindings/phy/qcom-apq8064-sata-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom-ipq806x-sata-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom-pcie2-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/qcom-usb-ipq4019-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/ralink-usb-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/renesas,rcar-gen2-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/renesas,rcar-gen3-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/renesas,usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/renesas,usb3-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/rockchip-dp-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/rockchip-emmc-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml create mode 100644 Documentation/devicetree/bindings/phy/rockchip-mipi-dphy-rx0.yaml create mode 100644 Documentation/devicetree/bindings/phy/rockchip-pcie-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/rockchip-usb-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,dp-video-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,exynos-hdmi-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,exynos-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,exynos5250-sata-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,mipi-video-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,ufs-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/samsung,usb3-drd-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/socionext,uniphier-pcie-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/socionext,uniphier-usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/socionext,uniphier-usb3hs-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/socionext,uniphier-usb3ss-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/st-spear-miphy.txt create mode 100644 Documentation/devicetree/bindings/phy/sunplus,sp7021-usb2-phy.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti,omap-usb2.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti,phy-gmii-sel.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml create mode 100644 Documentation/devicetree/bindings/phy/ti-phy.txt create mode 100644 Documentation/devicetree/bindings/phy/transmit-amplitude.yaml create mode 100644 Documentation/devicetree/bindings/phy/xlnx,zynqmp-psgtr.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/abilis,tb10x-iomux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/actions,s500-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/actions,s700-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/actions,s900-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/apple,pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/aspeed,ast2400-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/aspeed,ast2500-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/atmel,at91-pio4-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/bitmain,bm1880-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm11351-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm2835-gpio.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm4908-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm6318-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm63268-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm6328-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm6358-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm6362-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm6368-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,cygnus-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,ns2-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,nsp-gpio.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,nsp-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/canaan,k210-fpioa.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/cirrus,lochnagar.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/cirrus,madera.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/cnxt,cx92755-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/cortina,gemini-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx25-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx27-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx35-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx50-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx51-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx53-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6dl-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6q-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6sl-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6sll-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6sx-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx6ul-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx7d-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx7ulp-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx8mm-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx8mn-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx8mp-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx8mq-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx8ulp-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx93-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imxrt1170.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,mxs-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,scu-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,vf610-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/img,pistachio-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/ingenic,pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/intel,lgm-io.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/intel,pinctrl-keembay.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/intel,pinctrl-thunderbay.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/lantiq,pinctrl-falcon.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/lantiq,pinctrl-xway.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,ac5-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-370-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-375-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-37xx-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-38x-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-39x-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-98dx3236-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-xp-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,dove-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,kirkwood-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,mvebu-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,orion-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt65xx-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt6797-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt7622-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt7986-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt8183-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt8188-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,pinctrl-mt6795.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/microchip,pic32-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/microchip,sparx5-sgpio.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/mscc,ocelot-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/nuvoton,npcm7xx-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nuvoton,wpcm450-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra114-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra194-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra20-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra210-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra30-pinmux.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/nxp,lpc1850-scu.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/oxnas,pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mcp23s08.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8186.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8192.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-palmas.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-sirf.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-st.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-sx150x.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-vt8500.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl_spear.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/pinmux-node.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,apq8064-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,apq8084-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,ipq4019-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,ipq8064-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,ipq8074-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,mdm9607-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,mdm9615-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8226-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8660-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8909-tlmm.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8916-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8953-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8960-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8974-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8976-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8994-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8996-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,msm8998-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,pmic-mpp.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,qcm2290-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,qcs404-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc7180-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc7280-lpass-lpi-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc7280-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc8180x-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-lpass-lpi-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sc8280xp-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sdm845-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sdx55-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sdx65-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm6115-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm6125-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm6350-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm6375-tlmm.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8150-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8250-lpass-lpi-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8250-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8350-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8450-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,tlmm-common.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,mt7621-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,rt2880-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ralink,rt3883-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,pfc.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rza1-ports.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rza2-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rzn1-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rzv2m-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-gpio-bank.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-pins-cfg.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/sprd,pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/sprd,sc9860-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/starfive,jh7100-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ste,abx500.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/ste,nomadik.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/sunplus,sp7021-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/ti,da850-pupd.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/ti,iodelay.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/ti,omap-pinctrl.txt create mode 100644 Documentation/devicetree/bindings/pinctrl/toshiba,visconti-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/xlnx,zynq-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml create mode 100644 Documentation/devicetree/bindings/pmem/pmem-region.txt create mode 100644 Documentation/devicetree/bindings/power/actions,owl-sps.txt create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-gx-pwrc.txt create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml create mode 100644 Documentation/devicetree/bindings/power/apple,pmgr-pwrstate.yaml create mode 100644 Documentation/devicetree/bindings/power/avs/qcom,cpr.yaml create mode 100644 Documentation/devicetree/bindings/power/brcm,bcm-pmb.yaml create mode 100644 Documentation/devicetree/bindings/power/brcm,bcm63xx-power.yaml create mode 100644 Documentation/devicetree/bindings/power/domain-idle-state.yaml create mode 100644 Documentation/devicetree/bindings/power/fsl,imx-gpc.yaml create mode 100644 Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml create mode 100644 Documentation/devicetree/bindings/power/fsl,scu-pd.yaml create mode 100644 Documentation/devicetree/bindings/power/mediatek,power-controller.yaml create mode 100644 Documentation/devicetree/bindings/power/mti,mips-cpc.yaml create mode 100644 Documentation/devicetree/bindings/power/pd-samsung.yaml create mode 100644 Documentation/devicetree/bindings/power/power-controller.txt create mode 100644 Documentation/devicetree/bindings/power/power-domain.yaml create mode 100644 Documentation/devicetree/bindings/power/power_domain.txt create mode 100644 Documentation/devicetree/bindings/power/qcom,rpmpd.yaml create mode 100644 Documentation/devicetree/bindings/power/renesas,apmu.yaml create mode 100644 Documentation/devicetree/bindings/power/renesas,rcar-sysc.yaml create mode 100644 Documentation/devicetree/bindings/power/renesas,sysc-rmobile.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/axxia-reset.txt create mode 100644 Documentation/devicetree/bindings/power/reset/brcm,bcm21664-resetmgr.txt create mode 100644 Documentation/devicetree/bindings/power/reset/gemini-poweroff.txt create mode 100644 Documentation/devicetree/bindings/power/reset/gpio-poweroff.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/gpio-restart.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/keystone-reset.txt create mode 100644 Documentation/devicetree/bindings/power/reset/ltc2952-poweroff.txt create mode 100644 Documentation/devicetree/bindings/power/reset/mt6323-poweroff.txt create mode 100644 Documentation/devicetree/bindings/power/reset/nvmem-reboot-mode.txt create mode 100644 Documentation/devicetree/bindings/power/reset/ocelot-reset.txt create mode 100644 Documentation/devicetree/bindings/power/reset/qcom,pon.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/qcom,pshold.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/qnap-poweroff.txt create mode 100644 Documentation/devicetree/bindings/power/reset/reboot-mode.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/regulator-poweroff.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/restart-poweroff.txt create mode 100644 Documentation/devicetree/bindings/power/reset/st-reset.txt create mode 100644 Documentation/devicetree/bindings/power/reset/syscon-poweroff.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml create mode 100644 Documentation/devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml create mode 100644 Documentation/devicetree/bindings/power/rockchip,power-controller.yaml create mode 100644 Documentation/devicetree/bindings/power/rockchip-io-domain.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/active-semi,act8945a-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq2415x.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq24190.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq24257.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq24735.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq2515x.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq256xx.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq25890.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq25980.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/bq27xxx.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/charger-manager.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/cpcap-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/cpcap-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/dlg,da9150-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/dlg,da9150-fuel-gauge.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/gpio-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/ingenic,battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/isp1704.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/lego,ev3-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/lltc,lt3651-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/lltc,ltc294x.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/ltc4162-l.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/max77650-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/max8925_battery.txt create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,ds2760.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max14577.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max14656.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max17040.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max17042.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max77693.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max77976.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/maxim,max8903.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/mediatek,mt6370-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/microchip,ucs1002.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/mt6360_charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/nokia,n900-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/olpc-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/power-supply.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/qcom,pm8941-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/qcom,pm8941-coincell.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/richtek,rt5033-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/richtek,rt9455.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/rohm,bd99954.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/samsung,battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/sbs,sbs-battery.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/sbs,sbs-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/sbs,sbs-manager.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/sc2731-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/sc27xx-fg.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/stericsson,ab8500-battery.txt create mode 100644 Documentation/devicetree/bindings/power/supply/stericsson,ab8500-btemp.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/stericsson,ab8500-chargalg.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/stericsson,ab8500-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/stericsson,ab8500-fg.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/summit,smb347-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/ti,lp8727.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/tps65090-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/tps65217-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/twl4030-charger.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/x-powers,axp20x-ac-power-supply.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/x-powers,axp20x-battery-power-supply.yaml create mode 100644 Documentation/devicetree/bindings/power/supply/x-powers,axp20x-usb-power-supply.yaml create mode 100644 Documentation/devicetree/bindings/power/ti-smartreflex.txt create mode 100644 Documentation/devicetree/bindings/power/wakeup-source.txt create mode 100644 Documentation/devicetree/bindings/power/xlnx,zynqmp-genpd.txt create mode 100644 Documentation/devicetree/bindings/powerpc/4xx/akebono.txt create mode 100644 Documentation/devicetree/bindings/powerpc/4xx/cpm.txt create mode 100644 Documentation/devicetree/bindings/powerpc/4xx/hsta.txt create mode 100644 Documentation/devicetree/bindings/powerpc/4xx/ppc440spe-adma.txt create mode 100644 Documentation/devicetree/bindings/powerpc/4xx/reboot.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/ccf.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/cpus.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/dcsr.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/diu.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/dma.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/ecm.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/interlaken-lac.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/l2cache.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/lbc.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mcm.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mcu-mpc8349emitx.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpc5121-psc.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpc512x_lpbfifo.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpc5200.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpic-msgr.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpic-timer.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/mpic.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/msi-pic.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/pamu.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/pmc.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/raideng.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/scfg.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/srio-rmu.txt create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/srio.txt create mode 100644 Documentation/devicetree/bindings/powerpc/ibm,powerpc-cpu-features.txt create mode 100644 Documentation/devicetree/bindings/powerpc/ibm,vas.txt create mode 100644 Documentation/devicetree/bindings/powerpc/nintendo/gamecube.txt create mode 100644 Documentation/devicetree/bindings/powerpc/nintendo/wii.txt create mode 100644 Documentation/devicetree/bindings/powerpc/opal/oppanel-opal.txt create mode 100644 Documentation/devicetree/bindings/powerpc/opal/power-mgt.txt create mode 100644 Documentation/devicetree/bindings/powerpc/opal/sensor-groups.txt create mode 100644 Documentation/devicetree/bindings/powerpc/sleep.yaml create mode 100644 Documentation/devicetree/bindings/pps/pps-gpio.txt create mode 100644 Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt create mode 100644 Documentation/devicetree/bindings/ptp/ptp-idt82p33.yaml create mode 100644 Documentation/devicetree/bindings/ptp/ptp-idtcm.yaml create mode 100644 Documentation/devicetree/bindings/ptp/ptp-ines.txt create mode 100644 Documentation/devicetree/bindings/ptp/ptp-qoriq.txt create mode 100644 Documentation/devicetree/bindings/ptp/timestamper.txt create mode 100644 Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/atmel,at91sam-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/atmel-hlcdc-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/brcm,iproc-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/brcm,kona-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/cirrus,clps711x-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/clk-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/img-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/imx-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/imx-tpm-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/intel,keembay-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/intel,lgm-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/iqs620a-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/kontron,sl28cpld-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/lpc1850-sct-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/lpc32xx-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/mediatek,pwm-disp.yaml create mode 100644 Documentation/devicetree/bindings/pwm/microchip,corepwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/mxs-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/nxp,pca9685-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-bcm2835.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-berlin.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-hibvt.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-lp3943.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-mediatek.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-meson.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pwm-samsung.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pwm-sifive.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pwm-sprd.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-st.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-tiecap.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pwm-tiehrpwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pwm-tipwmss.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/pxa-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/renesas,pwm-rcar.yaml create mode 100644 Documentation/devicetree/bindings/pwm/renesas,tpu-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/spear-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/st,stmpe-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/sunplus,sp7021-pwm.yaml create mode 100644 Documentation/devicetree/bindings/pwm/ti,twl-pwm.txt create mode 100644 Documentation/devicetree/bindings/pwm/ti,twl-pwmled.txt create mode 100644 Documentation/devicetree/bindings/pwm/toshiba,pwm-visconti.yaml create mode 100644 Documentation/devicetree/bindings/pwm/vt8500-pwm.txt create mode 100644 Documentation/devicetree/bindings/regmap/regmap.txt create mode 100644 Documentation/devicetree/bindings/regulator/88pg86x.txt create mode 100644 Documentation/devicetree/bindings/regulator/88pm800.txt create mode 100644 Documentation/devicetree/bindings/regulator/88pm860x.txt create mode 100644 Documentation/devicetree/bindings/regulator/act8865-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/act8945a-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/as3722-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/cpcap-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/da9210.txt create mode 100644 Documentation/devicetree/bindings/regulator/da9211.txt create mode 100644 Documentation/devicetree/bindings/regulator/dlg,da9121.yaml create mode 100644 Documentation/devicetree/bindings/regulator/fan53555.txt create mode 100644 Documentation/devicetree/bindings/regulator/fixed-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/google,cros-ec-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/gpio-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/isl9305.txt create mode 100644 Documentation/devicetree/bindings/regulator/lm363x-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/lp872x.txt create mode 100644 Documentation/devicetree/bindings/regulator/ltc3589.txt create mode 100644 Documentation/devicetree/bindings/regulator/ltc3676.txt create mode 100644 Documentation/devicetree/bindings/regulator/max1586-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/max77650-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/max8660.yaml create mode 100644 Documentation/devicetree/bindings/regulator/max8893.yaml create mode 100644 Documentation/devicetree/bindings/regulator/max8907.txt create mode 100644 Documentation/devicetree/bindings/regulator/max8925-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max14577.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max20086.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77686.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77693.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77802.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77826.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77843.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max8952.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max8973.yaml create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max8997.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mcp16502-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6331-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6332-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mp8859.txt create mode 100644 Documentation/devicetree/bindings/regulator/mps,mp5416.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mps,mp886x.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mt6311-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mt6323-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/mt6358-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/mt6359-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mt6360-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mt6380-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/mt6397-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt create mode 100644 Documentation/devicetree/bindings/regulator/nxp,pca9450-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/onnn,fan53880.yaml create mode 100644 Documentation/devicetree/bindings/regulator/palmas-pmic.txt create mode 100644 Documentation/devicetree/bindings/regulator/pbias-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/pfuze100.yaml create mode 100644 Documentation/devicetree/bindings/regulator/pv88060.txt create mode 100644 Documentation/devicetree/bindings/regulator/pv88080.txt create mode 100644 Documentation/devicetree/bindings/regulator/pv88090.txt create mode 100644 Documentation/devicetree/bindings/regulator/pwm-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/qcom,usb-vbus-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/raspberrypi,7inch-touchscreen-panel-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/regulator-max77620.txt create mode 100644 Documentation/devicetree/bindings/regulator/regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt4801-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt4831-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt5190a-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt5759-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt6160-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt6245-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rtmv20-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rtq2134-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rtq6752-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71815-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71828-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd71847-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd9576-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mpa01.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mps11.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mps13.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mps14.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mps15.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s2mpu02.yaml create mode 100644 Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8106a.yaml create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8824x.yaml create mode 100644 Documentation/devicetree/bindings/regulator/silergy,sy8827n.yaml create mode 100644 Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/sky81452-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/slg51000.txt create mode 100644 Documentation/devicetree/bindings/regulator/socionext,uniphier-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/sprd,sc2731-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/st,stm32-booster.yaml create mode 100644 Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml create mode 100644 Documentation/devicetree/bindings/regulator/st,stm32mp1-pwr-reg.yaml create mode 100644 Documentation/devicetree/bindings/regulator/ti,tps62360.yaml create mode 100644 Documentation/devicetree/bindings/regulator/ti,tps62864.yaml create mode 100644 Documentation/devicetree/bindings/regulator/ti,tps65219.yaml create mode 100644 Documentation/devicetree/bindings/regulator/ti-abb-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps51632-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps65023.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps65090.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps65132-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps65217.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps65218.txt create mode 100644 Documentation/devicetree/bindings/regulator/tps6586x.txt create mode 100644 Documentation/devicetree/bindings/regulator/twl-regulator.txt create mode 100644 Documentation/devicetree/bindings/regulator/vctrl.txt create mode 100644 Documentation/devicetree/bindings/regulator/vexpress.txt create mode 100644 Documentation/devicetree/bindings/regulator/vqmmc-ipq4019-regulator.yaml create mode 100644 Documentation/devicetree/bindings/regulator/wlf,arizona.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/amlogic,meson-mx-ao-arc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/ingenic,vpu.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,glink-edge.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,pil-info.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,qcs404-cdsp-pil.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,sc7180-mss-pil.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,sc7280-mss-pil.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,sc7280-wpss-pil.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,sdm845-adsp-pil.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,smd-edge.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.txt create mode 100644 Documentation/devicetree/bindings/remoteproc/renesas,rcar-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/st,stm32-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/st-rproc.txt create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,davinci-rproc.txt create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,omap-remoteproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml create mode 100644 Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt create mode 100644 Documentation/devicetree/bindings/reserved-memory/google,open-dice.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/memory-region.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/nvidia,tegra210-emc-table.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/phram.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/qcom,cmd-db.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/ramoops.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt create mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml create mode 100644 Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt create mode 100644 Documentation/devicetree/bindings/reset/allwinner,sun6i-a31-clock-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/altr,rst-mgr.yaml create mode 100644 Documentation/devicetree/bindings/reset/amlogic,meson-axg-audio-arb.yaml create mode 100644 Documentation/devicetree/bindings/reset/amlogic,meson-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/atmel,at91sam9260-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/bitmain,bm1880-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/brcm,bcm4908-misc-pcie-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/brcm,bcm63138-pmb.txt create mode 100644 Documentation/devicetree/bindings/reset/brcm,bcm6345-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/brcm,bcm7216-pcie-sata-rescal.yaml create mode 100644 Documentation/devicetree/bindings/reset/brcm,brcmstb-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/canaan,k210-rst.yaml create mode 100644 Documentation/devicetree/bindings/reset/delta,tn48m-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/fsl,imx-src.yaml create mode 100644 Documentation/devicetree/bindings/reset/fsl,imx7-src.yaml create mode 100644 Documentation/devicetree/bindings/reset/hisilicon,hi3660-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/img,pistachio-reset.txt create mode 100644 Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml create mode 100644 Documentation/devicetree/bindings/reset/lantiq,reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/marvell,berlin2-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/microchip,rst.yaml create mode 100644 Documentation/devicetree/bindings/reset/nuvoton,npcm750-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/nxp,lpc1850-rgu.txt create mode 100644 Documentation/devicetree/bindings/reset/oxnas,reset.txt create mode 100644 Documentation/devicetree/bindings/reset/qca,ar7100-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/qcom,aoss-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/qcom,pdc-global.yaml create mode 100644 Documentation/devicetree/bindings/reset/renesas,rst.yaml create mode 100644 Documentation/devicetree/bindings/reset/renesas,rzg2l-usbphy-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/reset/reset.txt create mode 100644 Documentation/devicetree/bindings/reset/snps,axs10x-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/snps,dw-reset.txt create mode 100644 Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt create mode 100644 Documentation/devicetree/bindings/reset/socionext,uniphier-glue-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/socionext,uniphier-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/st,sti-softreset.txt create mode 100644 Documentation/devicetree/bindings/reset/st,stih407-picophyreset.yaml create mode 100644 Documentation/devicetree/bindings/reset/st,stih407-powerdown.yaml create mode 100644 Documentation/devicetree/bindings/reset/st,stm32-rcc.txt create mode 100644 Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt create mode 100644 Documentation/devicetree/bindings/reset/starfive,jh7100-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/sunplus,reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/ti,sci-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/ti,tps380x-reset.yaml create mode 100644 Documentation/devicetree/bindings/reset/ti-syscon-reset.txt create mode 100644 Documentation/devicetree/bindings/reset/xlnx,zynqmp-reset.txt create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset.txt create mode 100644 Documentation/devicetree/bindings/resource-names.txt create mode 100644 Documentation/devicetree/bindings/riscv/canaan.yaml create mode 100644 Documentation/devicetree/bindings/riscv/cpus.yaml create mode 100644 Documentation/devicetree/bindings/riscv/microchip.yaml create mode 100644 Documentation/devicetree/bindings/riscv/sifive,ccache0.yaml create mode 100644 Documentation/devicetree/bindings/riscv/sifive.yaml create mode 100644 Documentation/devicetree/bindings/riscv/starfive.yaml create mode 100644 Documentation/devicetree/bindings/rng/amlogic,meson-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/apm,x-gene-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/arm-cctrng.yaml create mode 100644 Documentation/devicetree/bindings/rng/atmel,at91-trng.yaml create mode 100644 Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml create mode 100644 Documentation/devicetree/bindings/rng/brcm,iproc-rng200.yaml create mode 100644 Documentation/devicetree/bindings/rng/hisi-rng.txt create mode 100644 Documentation/devicetree/bindings/rng/imx-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/ingenic,rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/ingenic,trng.yaml create mode 100644 Documentation/devicetree/bindings/rng/intel,ixp46x-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/microchip,pic32-rng.txt create mode 100644 Documentation/devicetree/bindings/rng/mtk-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/nuvoton,npcm-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/omap_rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/samsung,exynos4-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.yaml create mode 100644 Documentation/devicetree/bindings/rng/silex-insight,ba431-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/sparc_sun_oracle_rng.txt create mode 100644 Documentation/devicetree/bindings/rng/st,rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/st,stm32-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/ti,keystone-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/ti,omap-rom-rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/timeriomem_rng.yaml create mode 100644 Documentation/devicetree/bindings/rng/xiphera,xip8001b-trng.yaml create mode 100644 Documentation/devicetree/bindings/rtc/abracon,abx80x.txt create mode 100644 Documentation/devicetree/bindings/rtc/allwinner,sun4i-a10-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/allwinner,sun6i-a31-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/alphascale,asm9260-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/arm,pl031.yaml create mode 100644 Documentation/devicetree/bindings/rtc/armada-380-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/atmel,at91rm9200-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/atmel,at91sam9260-rtt.yaml create mode 100644 Documentation/devicetree/bindings/rtc/brcm,brcmstb-waketimer.yaml create mode 100644 Documentation/devicetree/bindings/rtc/cdns,rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/cpcap-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/dallas,ds1390.txt create mode 100644 Documentation/devicetree/bindings/rtc/digicolor-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/epson,rtc7301.txt create mode 100644 Documentation/devicetree/bindings/rtc/epson,rx6110.txt create mode 100644 Documentation/devicetree/bindings/rtc/epson,rx8900.yaml create mode 100644 Documentation/devicetree/bindings/rtc/faraday,ftrtc010.yaml create mode 100644 Documentation/devicetree/bindings/rtc/fsl,scu-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/google,goldfish-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt create mode 100644 Documentation/devicetree/bindings/rtc/imxdi-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/ingenic,rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/isil,isl12026.txt create mode 100644 Documentation/devicetree/bindings/rtc/isil,isl12057.txt create mode 100644 Documentation/devicetree/bindings/rtc/isil,isl1208.txt create mode 100644 Documentation/devicetree/bindings/rtc/lpc32xx-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/maxim,ds1742.txt create mode 100644 Documentation/devicetree/bindings/rtc/maxim,ds3231.txt create mode 100644 Documentation/devicetree/bindings/rtc/maxim,mcp795.txt create mode 100644 Documentation/devicetree/bindings/rtc/maxim-ds1302.txt create mode 100644 Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/microchip,pic32-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/microcrystal,rv3032.yaml create mode 100644 Documentation/devicetree/bindings/rtc/moxa,moxart-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/mstar,msc313-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nuvoton,nct3018y.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nvidia,tegra20-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nxp,lpc1788-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nxp,pcf85063.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nxp,pcf8523.txt create mode 100644 Documentation/devicetree/bindings/rtc/nxp,pcf8563.yaml create mode 100644 Documentation/devicetree/bindings/rtc/nxp,rtc-2123.txt create mode 100644 Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/orion-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/pxa-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/qcom-pm8xxx-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/realtek,rtd119x.txt create mode 100644 Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/renesas,sh-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/rtc-aspeed.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-cmos.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-ds1307.yaml create mode 100644 Documentation/devicetree/bindings/rtc/rtc-fsl-ftm-alarm.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-m41t80.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-meson-vrtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-meson.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt2712.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt6397.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt7622.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mxc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mxc_v2.yaml create mode 100644 Documentation/devicetree/bindings/rtc/rtc-omap.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-opal.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-palmas.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc-st-lpc.txt create mode 100644 Documentation/devicetree/bindings/rtc/rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/s3c-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/sa1100-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/snvs-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/spear-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/sprd,sc27xx-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/st,stm32-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/stmp3xxx-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/sunplus,sp7021-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/ti,bq32000.yaml create mode 100644 Documentation/devicetree/bindings/rtc/ti,k3-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/trivial-rtc.yaml create mode 100644 Documentation/devicetree/bindings/rtc/twl-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/via,vt8500-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/xgene-rtc.txt create mode 100644 Documentation/devicetree/bindings/rtc/xlnx,zynqmp-rtc.yaml create mode 100644 Documentation/devicetree/bindings/scsi/hisilicon-sas.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/google,cr50.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/ibmvtpm.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/st33zp24-i2c.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/st33zp24-spi.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm-i2c.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm_tis_mmio.txt create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm_tis_spi.txt create mode 100644 Documentation/devicetree/bindings/serial/8250.yaml create mode 100644 Documentation/devicetree/bindings/serial/8250_omap.yaml create mode 100644 Documentation/devicetree/bindings/serial/actions,owl-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/altera_jtaguart.txt create mode 100644 Documentation/devicetree/bindings/serial/altera_uart.txt create mode 100644 Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/arc-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/arm,mps2-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/arm_sbsa_uart.txt create mode 100644 Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml create mode 100644 Documentation/devicetree/bindings/serial/brcm,bcm2835-aux-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/brcm,bcm6345-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/brcm,bcm7271-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/cavium-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/cdns,uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/cirrus,clps711x-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/digicolor-usart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml create mode 100644 Documentation/devicetree/bindings/serial/fsl-imx-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/fsl-lpuart.yaml create mode 100644 Documentation/devicetree/bindings/serial/fsl-mxs-auart.yaml create mode 100644 Documentation/devicetree/bindings/serial/ingenic,uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/lantiq_asc.txt create mode 100644 Documentation/devicetree/bindings/serial/litex,liteuart.yaml create mode 100644 Documentation/devicetree/bindings/serial/maxim,max310x.txt create mode 100644 Documentation/devicetree/bindings/serial/mediatek,uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/microchip,pic32-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/milbeaut-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/mrvl,pxa-ssp.txt create mode 100644 Documentation/devicetree/bindings/serial/mvebu-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/nvidia,tegra194-tcu.yaml create mode 100644 Documentation/devicetree/bindings/serial/nvidia,tegra20-hsuart.txt create mode 100644 Documentation/devicetree/bindings/serial/nxp,lpc1850-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt create mode 100644 Documentation/devicetree/bindings/serial/nxp-lpc32xx-hsuart.txt create mode 100644 Documentation/devicetree/bindings/serial/pl011.yaml create mode 100644 Documentation/devicetree/bindings/serial/qca,ar9330-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/qcom,msm-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/qcom,msm-uartdm.yaml create mode 100644 Documentation/devicetree/bindings/serial/qcom,serial-geni-qcom.yaml create mode 100644 Documentation/devicetree/bindings/serial/rda,8810pl-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,em-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,hscif.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,sci.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,scif.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,scifa.yaml create mode 100644 Documentation/devicetree/bindings/serial/renesas,scifb.yaml create mode 100644 Documentation/devicetree/bindings/serial/rs485.txt create mode 100644 Documentation/devicetree/bindings/serial/rs485.yaml create mode 100644 Documentation/devicetree/bindings/serial/samsung_uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/serial.yaml create mode 100644 Documentation/devicetree/bindings/serial/sifive-serial.yaml create mode 100644 Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/socionext,uniphier-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/sprd-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/st,stm32-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/st-asc.txt create mode 100644 Documentation/devicetree/bindings/serial/sunplus,sp7021-uart.yaml create mode 100644 Documentation/devicetree/bindings/serial/vt8500-uart.txt create mode 100644 Documentation/devicetree/bindings/serial/xlnx,opb-uartlite.yaml create mode 100644 Documentation/devicetree/bindings/serio/allwinner,sun4i-a10-ps2.yaml create mode 100644 Documentation/devicetree/bindings/serio/altera_ps2.txt create mode 100644 Documentation/devicetree/bindings/serio/arm,pl050.yaml create mode 100644 Documentation/devicetree/bindings/serio/olpc,ap-sp.txt create mode 100644 Documentation/devicetree/bindings/serio/ps2-gpio.yaml create mode 100644 Documentation/devicetree/bindings/serio/snps-arc_ps2.txt create mode 100644 Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt create mode 100644 Documentation/devicetree/bindings/siox/eckelmann,siox-gpio.txt create mode 100644 Documentation/devicetree/bindings/slimbus/bus.txt create mode 100644 Documentation/devicetree/bindings/slimbus/slim-ngd-qcom-ctrl.txt create mode 100644 Documentation/devicetree/bindings/slimbus/slim-qcom-ctrl.txt create mode 100644 Documentation/devicetree/bindings/soc/amlogic/amlogic,canvas.yaml create mode 100644 Documentation/devicetree/bindings/soc/amlogic/clk-measure.txt create mode 100644 Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.yaml create mode 100644 Documentation/devicetree/bindings/soc/bcm/raspberrypi,bcm2835-power.txt create mode 100644 Documentation/devicetree/bindings/soc/dove/pmu.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/bman-portals.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/bman.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/brg.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/i2c.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/pic.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/usb.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/gpio.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/network.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/firmware.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/par_io.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/pincfg.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ucc.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/usb.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/serial.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/cpm_qe/uqe_serial.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/fsl,layerscape-dcfg.yaml create mode 100644 Documentation/devicetree/bindings/soc/fsl/fsl,layerscape-scfg.yaml create mode 100644 Documentation/devicetree/bindings/soc/fsl/guts.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/qman-portals.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/qman.txt create mode 100644 Documentation/devicetree/bindings/soc/fsl/rcpm.txt create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,aips-bus.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mm-disp-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mm-vpu-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mn-disp-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mp-hdmi-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mp-hsio-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mp-media-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx93-src.yaml create mode 100644 Documentation/devicetree/bindings/soc/imx/imx8m-soc.yaml create mode 100644 Documentation/devicetree/bindings/soc/intel/intel,hps-copy-engine.yaml create mode 100644 Documentation/devicetree/bindings/soc/litex/litex,soc-controller.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/devapc.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,ccorr.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,wdma.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml create mode 100644 Documentation/devicetree/bindings/soc/mediatek/pwrap.txt create mode 100644 Documentation/devicetree/bindings/soc/mediatek/scpsys.txt create mode 100644 Documentation/devicetree/bindings/soc/microchip/atmel,at91rm9200-tcb.yaml create mode 100644 Documentation/devicetree/bindings/soc/microchip/microchip,mpfs-sys-controller.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,apr.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,glink.txt create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,gsbi.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smd-rpm.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smd.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smem.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smp2p.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smsm.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,spm.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,wcnss.yaml create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom-stats.yaml create mode 100644 Documentation/devicetree/bindings/soc/renesas/renesas,rzg2l-sysc.yaml create mode 100644 Documentation/devicetree/bindings/soc/rockchip/grf.yaml create mode 100644 Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml create mode 100644 Documentation/devicetree/bindings/soc/samsung/exynos-usi.yaml create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml create mode 100644 Documentation/devicetree/bindings/soc/ti/keystone-navigator-dma.txt create mode 100644 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt create mode 100644 Documentation/devicetree/bindings/soc/ti/sci-pm-domain.yaml create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml create mode 100644 Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml create mode 100644 Documentation/devicetree/bindings/soc/xilinx/xlnx,vcu-settings.yaml create mode 100644 Documentation/devicetree/bindings/soc/xilinx/xlnx,vcu.txt create mode 100644 Documentation/devicetree/bindings/sound/ac97-bus.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,adau1372.yaml create mode 100644 Documentation/devicetree/bindings/sound/adi,adau1701.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,adau17x1.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,adau1977.yaml create mode 100644 Documentation/devicetree/bindings/sound/adi,adau7002.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,adau7118.yaml create mode 100644 Documentation/devicetree/bindings/sound/adi,axi-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,axi-spdif-tx.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,max98396.yaml create mode 100644 Documentation/devicetree/bindings/sound/adi,ssm2305.txt create mode 100644 Documentation/devicetree/bindings/sound/adi,ssm2602.txt create mode 100644 Documentation/devicetree/bindings/sound/ak4104.txt create mode 100644 Documentation/devicetree/bindings/sound/ak4118.txt create mode 100644 Documentation/devicetree/bindings/sound/ak4375.yaml create mode 100644 Documentation/devicetree/bindings/sound/ak4458.txt create mode 100644 Documentation/devicetree/bindings/sound/ak4554.txt create mode 100644 Documentation/devicetree/bindings/sound/ak4613.yaml create mode 100644 Documentation/devicetree/bindings/sound/ak4642.yaml create mode 100644 Documentation/devicetree/bindings/sound/ak5386.txt create mode 100644 Documentation/devicetree/bindings/sound/ak5558.txt create mode 100644 Documentation/devicetree/bindings/sound/alc5623.txt create mode 100644 Documentation/devicetree/bindings/sound/alc5632.txt create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun4i-a10-codec.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun4i-a10-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun4i-a10-spdif.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun50i-a64-codec-analog.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun8i-a23-codec-analog.yaml create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun8i-a33-codec.yaml create mode 100644 Documentation/devicetree/bindings/sound/amlogic,aiu.yaml create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-fifo.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-pdm.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-sound-card.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-spdifin.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-spdifout.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-tdm-formatters.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,axg-tdm-iface.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,g12a-toacodec.yaml create mode 100644 Documentation/devicetree/bindings/sound/amlogic,g12a-tohdmitx.txt create mode 100644 Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml create mode 100644 Documentation/devicetree/bindings/sound/amlogic,t9015.yaml create mode 100644 Documentation/devicetree/bindings/sound/apple,mca.yaml create mode 100644 Documentation/devicetree/bindings/sound/arm,pl041.yaml create mode 100644 Documentation/devicetree/bindings/sound/armada-370db-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/atmel,sama5d2-classd.yaml create mode 100644 Documentation/devicetree/bindings/sound/atmel,sama5d2-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/atmel,sama5d2-pdmic.yaml create mode 100644 Documentation/devicetree/bindings/sound/atmel-at91sam9g20ek-wm8731-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/atmel-sam9x5-wm8731-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/atmel-wm8904.txt create mode 100644 Documentation/devicetree/bindings/sound/atmel_ac97c.txt create mode 100644 Documentation/devicetree/bindings/sound/audio-graph-card.yaml create mode 100644 Documentation/devicetree/bindings/sound/audio-graph-card2.yaml create mode 100644 Documentation/devicetree/bindings/sound/audio-graph-port.yaml create mode 100644 Documentation/devicetree/bindings/sound/audio-graph.yaml create mode 100644 Documentation/devicetree/bindings/sound/awinic,aw8738.yaml create mode 100644 Documentation/devicetree/bindings/sound/axentia,tse850-pcm5142.txt create mode 100644 Documentation/devicetree/bindings/sound/brcm,bcm2835-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/brcm,bcm63xx-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/brcm,cygnus-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/cdns,xtfpga-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs35l41.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs4234.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs42l42.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs42l51.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,lochnagar.yaml create mode 100644 Documentation/devicetree/bindings/sound/cirrus,madera.yaml create mode 100644 Documentation/devicetree/bindings/sound/cs35l32.txt create mode 100644 Documentation/devicetree/bindings/sound/cs35l33.txt create mode 100644 Documentation/devicetree/bindings/sound/cs35l34.txt create mode 100644 Documentation/devicetree/bindings/sound/cs35l35.txt create mode 100644 Documentation/devicetree/bindings/sound/cs35l36.txt create mode 100644 Documentation/devicetree/bindings/sound/cs4265.txt create mode 100644 Documentation/devicetree/bindings/sound/cs4270.txt create mode 100644 Documentation/devicetree/bindings/sound/cs4271.txt create mode 100644 Documentation/devicetree/bindings/sound/cs42l52.txt create mode 100644 Documentation/devicetree/bindings/sound/cs42l56.txt create mode 100644 Documentation/devicetree/bindings/sound/cs42l73.txt create mode 100644 Documentation/devicetree/bindings/sound/cs42xx8.txt create mode 100644 Documentation/devicetree/bindings/sound/cs43130.txt create mode 100644 Documentation/devicetree/bindings/sound/cs4341.txt create mode 100644 Documentation/devicetree/bindings/sound/cs4349.txt create mode 100644 Documentation/devicetree/bindings/sound/cs53l30.txt create mode 100644 Documentation/devicetree/bindings/sound/da7213.txt create mode 100644 Documentation/devicetree/bindings/sound/da7218.txt create mode 100644 Documentation/devicetree/bindings/sound/da7219.txt create mode 100644 Documentation/devicetree/bindings/sound/da9055.txt create mode 100644 Documentation/devicetree/bindings/sound/dai-params.yaml create mode 100644 Documentation/devicetree/bindings/sound/davinci-evm-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/davinci-mcasp-audio.yaml create mode 100644 Documentation/devicetree/bindings/sound/davinci-mcbsp.txt create mode 100644 Documentation/devicetree/bindings/sound/dmic.txt create mode 100644 Documentation/devicetree/bindings/sound/es8328.txt create mode 100644 Documentation/devicetree/bindings/sound/eukrea-tlv320.txt create mode 100644 Documentation/devicetree/bindings/sound/everest,es7134.txt create mode 100644 Documentation/devicetree/bindings/sound/everest,es7241.txt create mode 100644 Documentation/devicetree/bindings/sound/everest,es8316.yaml create mode 100644 Documentation/devicetree/bindings/sound/everest,es8326.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,asrc.txt create mode 100644 Documentation/devicetree/bindings/sound/fsl,aud2htx.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,audmix.txt create mode 100644 Documentation/devicetree/bindings/sound/fsl,easrc.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,esai.txt create mode 100644 Documentation/devicetree/bindings/sound/fsl,micfil.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,mqs.txt create mode 100644 Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,sai.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,spdif.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl,ssi.txt create mode 100644 Documentation/devicetree/bindings/sound/fsl,xcvr.yaml create mode 100644 Documentation/devicetree/bindings/sound/fsl-asoc-card.txt create mode 100644 Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml create mode 100644 Documentation/devicetree/bindings/sound/google,sc7180-trogdor.yaml create mode 100644 Documentation/devicetree/bindings/sound/google,sc7280-herobrine.yaml create mode 100644 Documentation/devicetree/bindings/sound/gtm601.txt create mode 100644 Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/ics43432.txt create mode 100644 Documentation/devicetree/bindings/sound/img,i2s-in.txt create mode 100644 Documentation/devicetree/bindings/sound/img,i2s-out.txt create mode 100644 Documentation/devicetree/bindings/sound/img,parallel-out.txt create mode 100644 Documentation/devicetree/bindings/sound/img,pistachio-internal-dac.txt create mode 100644 Documentation/devicetree/bindings/sound/img,spdif-in.txt create mode 100644 Documentation/devicetree/bindings/sound/img,spdif-out.txt create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-card.yaml create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-es8328.txt create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-hdmi.yaml create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-sgtl5000.txt create mode 100644 Documentation/devicetree/bindings/sound/imx-audio-spdif.txt create mode 100644 Documentation/devicetree/bindings/sound/imx-audmux.yaml create mode 100644 Documentation/devicetree/bindings/sound/ingenic,aic.yaml create mode 100644 Documentation/devicetree/bindings/sound/ingenic,codec.yaml create mode 100644 Documentation/devicetree/bindings/sound/inno-rk3036.txt create mode 100644 Documentation/devicetree/bindings/sound/intel,keembay-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/linux,bt-sco.yaml create mode 100644 Documentation/devicetree/bindings/sound/linux,spdif-dit.yaml create mode 100644 Documentation/devicetree/bindings/sound/marvell,mmp-sspa.yaml create mode 100644 Documentation/devicetree/bindings/sound/marvell,pxa2xx-ac97.txt create mode 100644 Documentation/devicetree/bindings/sound/max98090.txt create mode 100644 Documentation/devicetree/bindings/sound/max98095.txt create mode 100644 Documentation/devicetree/bindings/sound/max98357a.txt create mode 100644 Documentation/devicetree/bindings/sound/max98371.txt create mode 100644 Documentation/devicetree/bindings/sound/max98373.txt create mode 100644 Documentation/devicetree/bindings/sound/max98504.txt create mode 100644 Documentation/devicetree/bindings/sound/max9860.txt create mode 100644 Documentation/devicetree/bindings/sound/max9867.txt create mode 100644 Documentation/devicetree/bindings/sound/max9892x.txt create mode 100644 Documentation/devicetree/bindings/sound/maxim,max9759.txt create mode 100644 Documentation/devicetree/bindings/sound/maxim,max98088.txt create mode 100644 Documentation/devicetree/bindings/sound/maxim,max98390.yaml create mode 100644 Documentation/devicetree/bindings/sound/maxim,max98520.yaml create mode 100644 Documentation/devicetree/bindings/sound/mchp,i2s-mcc.yaml create mode 100644 Documentation/devicetree/bindings/sound/mchp,spdifrx.yaml create mode 100644 Documentation/devicetree/bindings/sound/mchp,spdiftx.yaml create mode 100644 Documentation/devicetree/bindings/sound/microchip,pdmc.yaml create mode 100644 Documentation/devicetree/bindings/sound/mikroe,mikroe-proto.txt create mode 100644 Documentation/devicetree/bindings/sound/mrvl,pxa-ssp.txt create mode 100644 Documentation/devicetree/bindings/sound/mt2701-afe-pcm.txt create mode 100644 Documentation/devicetree/bindings/sound/mt2701-cs42448.txt create mode 100644 Documentation/devicetree/bindings/sound/mt2701-wm8960.txt create mode 100644 Documentation/devicetree/bindings/sound/mt6351.txt create mode 100644 Documentation/devicetree/bindings/sound/mt6358.txt create mode 100644 Documentation/devicetree/bindings/sound/mt6359.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt6797-afe-pcm.txt create mode 100644 Documentation/devicetree/bindings/sound/mt6797-mt6351.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8173-max98090.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8173-rt5650-rt5514.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8173-rt5650-rt5676.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8173-rt5650.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8183-afe-pcm.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8183-da7219-max98357.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8183-mt6358-ts3a227-max98357.txt create mode 100644 Documentation/devicetree/bindings/sound/mt8186-afe-pcm.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8186-mt6366-da7219-max98357.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8186-mt6366-rt1019-rt5682s.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8192-afe-pcm.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8192-mt6359-rt1015-rt5682.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8195-afe-pcm.yaml create mode 100644 Documentation/devicetree/bindings/sound/mt8195-mt6359.yaml create mode 100644 Documentation/devicetree/bindings/sound/mtk-afe-pcm.txt create mode 100644 Documentation/devicetree/bindings/sound/mtk-btcvsd-snd.txt create mode 100644 Documentation/devicetree/bindings/sound/mvebu-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/mxs-audio-sgtl5000.txt create mode 100644 Documentation/devicetree/bindings/sound/mxs-saif.txt create mode 100644 Documentation/devicetree/bindings/sound/name-prefix.yaml create mode 100644 Documentation/devicetree/bindings/sound/nau8315.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8540.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8810.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8821.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8822.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8824.txt create mode 100644 Documentation/devicetree/bindings/sound/nau8825.txt create mode 100644 Documentation/devicetree/bindings/sound/nokia,rx51.txt create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-alc5632.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-common.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-graph-card.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-max98090.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-rt5640.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-rt5677.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-sgtl5000.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-trimslice.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-wm8753.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-wm8903.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra-audio-wm9712.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra186-asrc.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra186-dspk.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra20-ac97.txt create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra20-das.txt create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra20-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra20-spdif.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-admaif.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-adx.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-ahub.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-amx.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-dmic.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mbdrc.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mixer.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-mvc.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-ope.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-peq.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra210-sfc.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra30-ahub.txt create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml create mode 100644 Documentation/devicetree/bindings/sound/nvidia,tegra30-i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml create mode 100644 Documentation/devicetree/bindings/sound/omap-abe-twl6040.txt create mode 100644 Documentation/devicetree/bindings/sound/omap-dmic.txt create mode 100644 Documentation/devicetree/bindings/sound/omap-mcbsp.txt create mode 100644 Documentation/devicetree/bindings/sound/omap-mcpdm.txt create mode 100644 Documentation/devicetree/bindings/sound/omap-twl4030.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm1789.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm179x.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm186x.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm3060.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm5102a.txt create mode 100644 Documentation/devicetree/bindings/sound/pcm512x.txt create mode 100644 Documentation/devicetree/bindings/sound/qcom,apq8096.txt create mode 100644 Documentation/devicetree/bindings/sound/qcom,lpass-cpu.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,lpass-rx-macro.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,lpass-tx-macro.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,lpass-va-macro.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,lpass-wsa-macro.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-analog.txt create mode 100644 Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-digital.txt create mode 100644 Documentation/devicetree/bindings/sound/qcom,q6adm-routing.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,q6asm-dais.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,q6dsp-lpass-clocks.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,q6dsp-lpass-ports.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,sm8250.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,wcd9335.txt create mode 100644 Documentation/devicetree/bindings/sound/qcom,wcd934x.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,wcd938x-sdw.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,wcd938x.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,wsa881x.yaml create mode 100644 Documentation/devicetree/bindings/sound/qcom,wsa883x.yaml create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt5682s.yaml create mode 100644 Documentation/devicetree/bindings/sound/renesas,fsi.yaml create mode 100644 Documentation/devicetree/bindings/sound/renesas,rsnd.txt create mode 100644 Documentation/devicetree/bindings/sound/renesas,rsnd.yaml create mode 100644 Documentation/devicetree/bindings/sound/renesas,rz-ssi.yaml create mode 100644 Documentation/devicetree/bindings/sound/richtek,rt9120.yaml create mode 100644 Documentation/devicetree/bindings/sound/rockchip,i2s-tdm.yaml create mode 100644 Documentation/devicetree/bindings/sound/rockchip,pdm.yaml create mode 100644 Documentation/devicetree/bindings/sound/rockchip,rk3288-hdmi-analog.txt create mode 100644 Documentation/devicetree/bindings/sound/rockchip,rk3328-codec.yaml create mode 100644 Documentation/devicetree/bindings/sound/rockchip,rk3399-gru-sound.txt create mode 100644 Documentation/devicetree/bindings/sound/rockchip-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/rockchip-max98090.txt create mode 100644 Documentation/devicetree/bindings/sound/rockchip-rt5645.txt create mode 100644 Documentation/devicetree/bindings/sound/rockchip-spdif.yaml create mode 100644 Documentation/devicetree/bindings/sound/rohm,bd28623.yaml create mode 100644 Documentation/devicetree/bindings/sound/rt1011.txt create mode 100644 Documentation/devicetree/bindings/sound/rt1015.txt create mode 100644 Documentation/devicetree/bindings/sound/rt1016.txt create mode 100644 Documentation/devicetree/bindings/sound/rt1019.yaml create mode 100644 Documentation/devicetree/bindings/sound/rt1308.txt create mode 100644 Documentation/devicetree/bindings/sound/rt274.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5514.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5616.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5631.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5640.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5645.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5651.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5659.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5660.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5663.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5665.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5668.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5677.txt create mode 100644 Documentation/devicetree/bindings/sound/rt5682.txt create mode 100644 Documentation/devicetree/bindings/sound/samsung,aries-wm8994.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,arndale.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,midas-audio.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,odroid.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,smdk5250.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,snow.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung,tm2.yaml create mode 100644 Documentation/devicetree/bindings/sound/samsung-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/serial-midi.yaml create mode 100644 Documentation/devicetree/bindings/sound/sgtl5000.yaml create mode 100644 Documentation/devicetree/bindings/sound/simple-audio-amplifier.yaml create mode 100644 Documentation/devicetree/bindings/sound/simple-audio-mux.yaml create mode 100644 Documentation/devicetree/bindings/sound/simple-card.yaml create mode 100644 Documentation/devicetree/bindings/sound/sirf-audio-port.txt create mode 100644 Documentation/devicetree/bindings/sound/sirf-audio.txt create mode 100644 Documentation/devicetree/bindings/sound/snps,designware-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/soc-ac97link.txt create mode 100644 Documentation/devicetree/bindings/sound/socionext,uniphier-aio.yaml create mode 100644 Documentation/devicetree/bindings/sound/socionext,uniphier-evea.yaml create mode 100644 Documentation/devicetree/bindings/sound/sound-dai.yaml create mode 100644 Documentation/devicetree/bindings/sound/spdif-receiver.txt create mode 100644 Documentation/devicetree/bindings/sound/sprd-mcdt.txt create mode 100644 Documentation/devicetree/bindings/sound/sprd-pcm.txt create mode 100644 Documentation/devicetree/bindings/sound/ssm2518.txt create mode 100644 Documentation/devicetree/bindings/sound/ssm4567.txt create mode 100644 Documentation/devicetree/bindings/sound/st,sta32x.txt create mode 100644 Documentation/devicetree/bindings/sound/st,sta350.txt create mode 100644 Documentation/devicetree/bindings/sound/st,sti-asoc-card.txt create mode 100644 Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml create mode 100644 Documentation/devicetree/bindings/sound/st,stm32-sai.yaml create mode 100644 Documentation/devicetree/bindings/sound/st,stm32-spdifrx.yaml create mode 100644 Documentation/devicetree/bindings/sound/storm.txt create mode 100644 Documentation/devicetree/bindings/sound/tas2552.txt create mode 100644 Documentation/devicetree/bindings/sound/tas2562.yaml create mode 100644 Documentation/devicetree/bindings/sound/tas2770.yaml create mode 100644 Documentation/devicetree/bindings/sound/tas27xx.yaml create mode 100644 Documentation/devicetree/bindings/sound/tas571x.txt create mode 100644 Documentation/devicetree/bindings/sound/tas5720.txt create mode 100644 Documentation/devicetree/bindings/sound/tas5805m.yaml create mode 100644 Documentation/devicetree/bindings/sound/tda7419.txt create mode 100644 Documentation/devicetree/bindings/sound/tdm-slot.txt create mode 100644 Documentation/devicetree/bindings/sound/test-component.yaml create mode 100644 Documentation/devicetree/bindings/sound/tfa9879.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,ads117x.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,j721e-cpb-audio.yaml create mode 100644 Documentation/devicetree/bindings/sound/ti,j721e-cpb-ivi-audio.yaml create mode 100644 Documentation/devicetree/bindings/sound/ti,pcm1681.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,pcm3168a.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,src4xxx.yaml create mode 100644 Documentation/devicetree/bindings/sound/ti,tas5086.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,tas6424.txt create mode 100644 Documentation/devicetree/bindings/sound/ti,tlv320adc3xxx.yaml create mode 100644 Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml create mode 100644 Documentation/devicetree/bindings/sound/tlv320adcx140.yaml create mode 100644 Documentation/devicetree/bindings/sound/tlv320aic31xx.txt create mode 100644 Documentation/devicetree/bindings/sound/tlv320aic32x4.txt create mode 100644 Documentation/devicetree/bindings/sound/tlv320aic3x.txt create mode 100644 Documentation/devicetree/bindings/sound/tpa6130a2.txt create mode 100644 Documentation/devicetree/bindings/sound/tscs42xx.txt create mode 100644 Documentation/devicetree/bindings/sound/tscs454.txt create mode 100644 Documentation/devicetree/bindings/sound/uda1334.txt create mode 100644 Documentation/devicetree/bindings/sound/ux500-mop500.txt create mode 100644 Documentation/devicetree/bindings/sound/ux500-msp.txt create mode 100644 Documentation/devicetree/bindings/sound/widgets.txt create mode 100644 Documentation/devicetree/bindings/sound/wlf,arizona.yaml create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8731.yaml create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8903.yaml create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8940.yaml create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8962.yaml create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8974.txt create mode 100644 Documentation/devicetree/bindings/sound/wlf,wm8978.yaml create mode 100644 Documentation/devicetree/bindings/sound/wm8510.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8523.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8524.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8580.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8711.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8728.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8737.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8741.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8750.yaml create mode 100644 Documentation/devicetree/bindings/sound/wm8753.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8770.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8776.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8782.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8804.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8904.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8960.txt create mode 100644 Documentation/devicetree/bindings/sound/wm8994.txt create mode 100644 Documentation/devicetree/bindings/sound/xlnx,audio-formatter.txt create mode 100644 Documentation/devicetree/bindings/sound/xlnx,i2s.txt create mode 100644 Documentation/devicetree/bindings/sound/xlnx,spdif.txt create mode 100644 Documentation/devicetree/bindings/sound/zl38060.yaml create mode 100644 Documentation/devicetree/bindings/soundwire/qcom,sdw.txt create mode 100644 Documentation/devicetree/bindings/soundwire/soundwire-controller.yaml create mode 100644 Documentation/devicetree/bindings/spi/adi,axi-spi-engine.txt create mode 100644 Documentation/devicetree/bindings/spi/allwinner,sun4i-a10-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/allwinner,sun6i-a31-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/amlogic,meson-gx-spicc.yaml create mode 100644 Documentation/devicetree/bindings/spi/amlogic,meson6-spifc.yaml create mode 100644 Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml create mode 100644 Documentation/devicetree/bindings/spi/atmel,at91rm9200-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/atmel,quadspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt create mode 100644 Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.txt create mode 100644 Documentation/devicetree/bindings/spi/brcm,spi-bcm-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/cdns,qspi-nor-peripheral-props.yaml create mode 100644 Documentation/devicetree/bindings/spi/cdns,qspi-nor.yaml create mode 100644 Documentation/devicetree/bindings/spi/cdns,xspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/fsl-imx-cspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/fsl-spi.txt create mode 100644 Documentation/devicetree/bindings/spi/hpe,gxp-spifi.yaml create mode 100644 Documentation/devicetree/bindings/spi/icpdas-lp8841-spi-rtc.txt create mode 100644 Documentation/devicetree/bindings/spi/ingenic,spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt create mode 100644 Documentation/devicetree/bindings/spi/marvell,mmp2-ssp.yaml create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-mtk-snfi.yaml create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-slave-mt27xx.yaml create mode 100644 Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/microchip,spi-pic32.txt create mode 100644 Documentation/devicetree/bindings/spi/mikrotik,rb4xx-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/mxicy,mx25f0a-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/mxs-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/nuvoton,npcm-fiu.txt create mode 100644 Documentation/devicetree/bindings/spi/nuvoton,npcm-pspi.txt create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad-peripheral-props.yaml create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml create mode 100644 Documentation/devicetree/bindings/spi/omap-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/qca,ar934x-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-qup.yaml create mode 100644 Documentation/devicetree/bindings/spi/ralink,mt7621-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/realtek,rtl-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/renesas,hspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/renesas,rspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml create mode 100644 Documentation/devicetree/bindings/spi/rockchip-sfc.yaml create mode 100644 Documentation/devicetree/bindings/spi/samsung,spi-peripheral-props.yaml create mode 100644 Documentation/devicetree/bindings/spi/samsung,spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/snps,dw-apb-ssi.yaml create mode 100644 Documentation/devicetree/bindings/spi/socionext,uniphier-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-armada-3700.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-ath79.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-bcm63xx-hsspi.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-bcm63xx.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-bus.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-cadence.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-clps711x.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-controller.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-davinci.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-fsl-lpspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-gpio.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-img-spfi.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-lantiq-ssc.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-mux.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-nxp-fspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-octeon.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-orion.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-peripheral-props.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-pl022.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-rockchip.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-sc18is602.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-sifive.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-sprd.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-st-ssc.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-sunplus-sp7021.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-synquacer.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-xilinx.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi-xtensa-xtfpga.txt create mode 100644 Documentation/devicetree/bindings/spi/spi-zynqmp-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/spi_altera.txt create mode 100644 Documentation/devicetree/bindings/spi/spi_oc_tiny.txt create mode 100644 Documentation/devicetree/bindings/spi/sprd,spi-adi.yaml create mode 100644 Documentation/devicetree/bindings/spi/sqi-pic32.txt create mode 100644 Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spi/st,stm32-spi.yaml create mode 100644 Documentation/devicetree/bindings/spi/ti_qspi.txt create mode 100644 Documentation/devicetree/bindings/spi/xlnx,zynq-qspi.yaml create mode 100644 Documentation/devicetree/bindings/spmi/hisilicon,hisi-spmi-controller.yaml create mode 100644 Documentation/devicetree/bindings/spmi/mtk,spmi-mtk-pmif.yaml create mode 100644 Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml create mode 100644 Documentation/devicetree/bindings/spmi/spmi.yaml create mode 100644 Documentation/devicetree/bindings/sram/allwinner,sun4i-a10-system-control.yaml create mode 100644 Documentation/devicetree/bindings/sram/qcom,imem.yaml create mode 100644 Documentation/devicetree/bindings/sram/qcom,ocmem.yaml create mode 100644 Documentation/devicetree/bindings/sram/sram.yaml create mode 100644 Documentation/devicetree/bindings/staging/iio/adc/spear-adc.txt create mode 100644 Documentation/devicetree/bindings/submitting-patches.rst create mode 100644 Documentation/devicetree/bindings/thermal/allwinner,sun8i-a83t-ths.yaml create mode 100644 Documentation/devicetree/bindings/thermal/amazon,al-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/amlogic,thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/armada-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/brcm,avs-tmon.yaml create mode 100644 Documentation/devicetree/bindings/thermal/brcm,bcm2835-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/brcm,ns-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/brcm,sr-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/da9062-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/db8500-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/dove-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/fsl,scu-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/imx-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/imx8mm-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/kirkwood-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/max77620_thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/mediatek-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt create mode 100644 Documentation/devicetree/bindings/thermal/nvidia,tegra186-bpmp-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/nvidia,tegra30-tsensor.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qcom,spmi-temp-alarm.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qcom-lmh.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qcom-spmi-adc-tm-hc.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qcom-spmi-adc-tm5.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qcom-tsens.yaml create mode 100644 Documentation/devicetree/bindings/thermal/qoriq-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/rcar-gen3-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/rcar-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/rockchip-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/rzg2l-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/samsung,exynos-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/socionext,uniphier-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/spear-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/sprd-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/st,stm32-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/st-thermal.txt create mode 100644 Documentation/devicetree/bindings/thermal/thermal-cooling-devices.yaml create mode 100644 Documentation/devicetree/bindings/thermal/thermal-generic-adc.txt create mode 100644 Documentation/devicetree/bindings/thermal/thermal-idle.yaml create mode 100644 Documentation/devicetree/bindings/thermal/thermal-sensor.yaml create mode 100644 Documentation/devicetree/bindings/thermal/thermal-zones.yaml create mode 100644 Documentation/devicetree/bindings/thermal/ti,am654-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/ti,j72xx-thermal.yaml create mode 100644 Documentation/devicetree/bindings/thermal/ti_soc_thermal.txt create mode 100644 Documentation/devicetree/bindings/timer/actions,owl-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/allwinner,sun4i-a10-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.yaml create mode 100644 Documentation/devicetree/bindings/timer/altr,timer-1.0.txt create mode 100644 Documentation/devicetree/bindings/timer/amlogic,meson6-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/arm,arch_timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/arm,arch_timer_mmio.yaml create mode 100644 Documentation/devicetree/bindings/timer/arm,armv7m-systick.yaml create mode 100644 Documentation/devicetree/bindings/timer/arm,global_timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/arm,mps2-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/arm,sp804.yaml create mode 100644 Documentation/devicetree/bindings/timer/arm,twd-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/brcm,bcm2835-system-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/brcm,kona-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/cdns,ttc.yaml create mode 100644 Documentation/devicetree/bindings/timer/cirrus,clps711x-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/csky,gx6605s-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/csky,mptimer.txt create mode 100644 Documentation/devicetree/bindings/timer/digicolor-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/ezchip,nps400-timer0.txt create mode 100644 Documentation/devicetree/bindings/timer/ezchip,nps400-timer1.txt create mode 100644 Documentation/devicetree/bindings/timer/faraday,fttmr010.txt create mode 100644 Documentation/devicetree/bindings/timer/fsl,ftm-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/fsl,gtm.txt create mode 100644 Documentation/devicetree/bindings/timer/fsl,imxgpt.yaml create mode 100644 Documentation/devicetree/bindings/timer/hpe,gxp-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/img,pistachio-gptimer.txt create mode 100644 Documentation/devicetree/bindings/timer/ingenic,sysost.yaml create mode 100644 Documentation/devicetree/bindings/timer/ingenic,tcu.yaml create mode 100644 Documentation/devicetree/bindings/timer/intel,ixp4xx-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt create mode 100644 Documentation/devicetree/bindings/timer/lsi,zevio-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/marvell,armada-370-xp-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/marvell,orion-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/mrvl,mmp-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/mstar,msc313e-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/nxp,lpc3220-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/nxp,sysctr-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/nxp,tpm-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/oxsemi,rps-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/qcom,msm-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/rda,8810pl-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,cmt.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,em-sti.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,mtu2.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,ostm.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,tmu.yaml create mode 100644 Documentation/devicetree/bindings/timer/renesas,tpu.yaml create mode 100644 Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.yaml create mode 100644 Documentation/devicetree/bindings/timer/sifive,clint.yaml create mode 100644 Documentation/devicetree/bindings/timer/snps,arc-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-gfrc.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,archs-rtc.txt create mode 100644 Documentation/devicetree/bindings/timer/snps,dw-apb-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/socionext,milbeaut-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/spreadtrum,sprd-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/st,nomadik-mtu.yaml create mode 100644 Documentation/devicetree/bindings/timer/st,spear-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/st,stih407-lpc create mode 100644 Documentation/devicetree/bindings/timer/st,stm32-timer.yaml create mode 100644 Documentation/devicetree/bindings/timer/ti,davinci-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/ti,keystone-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/ti,timer-dm.yaml create mode 100644 Documentation/devicetree/bindings/timer/via,vt8500-timer.txt create mode 100644 Documentation/devicetree/bindings/timer/xlnx,xps-timer.yaml create mode 100644 Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml create mode 100644 Documentation/devicetree/bindings/timestamp/hte-consumer.yaml create mode 100644 Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml create mode 100644 Documentation/devicetree/bindings/trivial-devices.yaml create mode 100644 Documentation/devicetree/bindings/ufs/cdns,ufshc.yaml create mode 100644 Documentation/devicetree/bindings/ufs/hisilicon,ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/mediatek,ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/qcom,ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/renesas,ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/samsung,exynos-ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/snps,tc-dwc-g210.yaml create mode 100644 Documentation/devicetree/bindings/ufs/ti,j721e-ufs.yaml create mode 100644 Documentation/devicetree/bindings/ufs/ufs-common.yaml create mode 100644 Documentation/devicetree/bindings/unittest.txt create mode 100644 Documentation/devicetree/bindings/usb/allwinner,sun4i-a10-musb.yaml create mode 100644 Documentation/devicetree/bindings/usb/am33xx-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/amlogic,meson-g12a-usb-ctrl.yaml create mode 100644 Documentation/devicetree/bindings/usb/analogix,anx7411.yaml create mode 100644 Documentation/devicetree/bindings/usb/aspeed,ast2600-udc.yaml create mode 100644 Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml create mode 100644 Documentation/devicetree/bindings/usb/atmel-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/brcm,bcm3384-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/brcm,bcm7445-ehci.yaml create mode 100644 Documentation/devicetree/bindings/usb/brcm,bdc.yaml create mode 100644 Documentation/devicetree/bindings/usb/brcm,usb-pinmap.yaml create mode 100644 Documentation/devicetree/bindings/usb/cdns,usb3.yaml create mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt create mode 100644 Documentation/devicetree/bindings/usb/da8xx-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/dwc2.yaml create mode 100644 Documentation/devicetree/bindings/usb/dwc3-cavium.txt create mode 100644 Documentation/devicetree/bindings/usb/dwc3-st.txt create mode 100644 Documentation/devicetree/bindings/usb/dwc3-xilinx.yaml create mode 100644 Documentation/devicetree/bindings/usb/ehci-omap.txt create mode 100644 Documentation/devicetree/bindings/usb/ehci-orion.txt create mode 100644 Documentation/devicetree/bindings/usb/ehci-st.txt create mode 100644 Documentation/devicetree/bindings/usb/faraday,fotg210.yaml create mode 100644 Documentation/devicetree/bindings/usb/fcs,fsa4480.yaml create mode 100644 Documentation/devicetree/bindings/usb/fcs,fusb302.txt create mode 100644 Documentation/devicetree/bindings/usb/fsl,imx8mp-dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/fsl-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/generic-ehci.yaml create mode 100644 Documentation/devicetree/bindings/usb/generic-ohci.yaml create mode 100644 Documentation/devicetree/bindings/usb/generic-xhci.yaml create mode 100644 Documentation/devicetree/bindings/usb/gr-udc.txt create mode 100644 Documentation/devicetree/bindings/usb/hisilicon,histb-xhci.txt create mode 100644 Documentation/devicetree/bindings/usb/ingenic,musb.yaml create mode 100644 Documentation/devicetree/bindings/usb/intel,keembay-dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/iproc-udc.txt create mode 100644 Documentation/devicetree/bindings/usb/isp1301.txt create mode 100644 Documentation/devicetree/bindings/usb/lpc32xx-udc.txt create mode 100644 Documentation/devicetree/bindings/usb/marvell,pxau2o-ehci.yaml create mode 100644 Documentation/devicetree/bindings/usb/maxim,max33359.yaml create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3421.txt create mode 100644 Documentation/devicetree/bindings/usb/mediatek,mt6360-tcpc.yaml create mode 100644 Documentation/devicetree/bindings/usb/mediatek,mt6370-tcpc.yaml create mode 100644 Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml create mode 100644 Documentation/devicetree/bindings/usb/mediatek,mtu3.yaml create mode 100644 Documentation/devicetree/bindings/usb/mediatek,musb.yaml create mode 100644 Documentation/devicetree/bindings/usb/microchip,mpfs-musb.yaml create mode 100644 Documentation/devicetree/bindings/usb/msm-hsusb.txt create mode 100644 Documentation/devicetree/bindings/usb/npcm7xx-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/nvidia,tegra-xudc.yaml create mode 100644 Documentation/devicetree/bindings/usb/nvidia,tegra124-xusb.txt create mode 100644 Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt create mode 100644 Documentation/devicetree/bindings/usb/nxp,isp1760.yaml create mode 100644 Documentation/devicetree/bindings/usb/octeon-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/ohci-da8xx.txt create mode 100644 Documentation/devicetree/bindings/usb/ohci-nxp.txt create mode 100644 Documentation/devicetree/bindings/usb/ohci-omap3.txt create mode 100644 Documentation/devicetree/bindings/usb/ohci-st.txt create mode 100644 Documentation/devicetree/bindings/usb/omap-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/pxa-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/qcom,dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/realtek,rts5411.yaml create mode 100644 Documentation/devicetree/bindings/usb/renesas,usb-xhci.yaml create mode 100644 Documentation/devicetree/bindings/usb/renesas,usb3-peri.yaml create mode 100644 Documentation/devicetree/bindings/usb/renesas,usbhs.yaml create mode 100644 Documentation/devicetree/bindings/usb/richtek,rt1711h.txt create mode 100644 Documentation/devicetree/bindings/usb/richtek,rt1711h.yaml create mode 100644 Documentation/devicetree/bindings/usb/richtek,rt1719.yaml create mode 100644 Documentation/devicetree/bindings/usb/rockchip,dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/s3c2410-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/samsung,exynos-dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/samsung,exynos-usb2.yaml create mode 100644 Documentation/devicetree/bindings/usb/samsung-hsotg.txt create mode 100644 Documentation/devicetree/bindings/usb/smsc,usb3503.yaml create mode 100644 Documentation/devicetree/bindings/usb/snps,dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/spear-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/st,stusb160x.yaml create mode 100644 Documentation/devicetree/bindings/usb/st,typec-stm32g0.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,am62-usb.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,keystone-dwc3.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,tps6598x.yaml create mode 100644 Documentation/devicetree/bindings/usb/ti,usb8041.yaml create mode 100644 Documentation/devicetree/bindings/usb/twlxxxx-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/typec-tcpci.txt create mode 100644 Documentation/devicetree/bindings/usb/ulpi.txt create mode 100644 Documentation/devicetree/bindings/usb/usb-device.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb-drd.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb-hcd.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb-nop-xceiv.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb-uhci.txt create mode 100644 Documentation/devicetree/bindings/usb/usb-xhci.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb.yaml create mode 100644 Documentation/devicetree/bindings/usb/usb251xb.txt create mode 100644 Documentation/devicetree/bindings/usb/usb4604.txt create mode 100644 Documentation/devicetree/bindings/usb/usbmisc-imx.txt create mode 100644 Documentation/devicetree/bindings/usb/ux500-usb.txt create mode 100644 Documentation/devicetree/bindings/usb/willsemi,wusb3801.yaml create mode 100644 Documentation/devicetree/bindings/usb/xlnx,usb2.yaml create mode 100644 Documentation/devicetree/bindings/vendor-prefixes.yaml create mode 100644 Documentation/devicetree/bindings/virtio/mmio.yaml create mode 100644 Documentation/devicetree/bindings/virtio/pci-iommu.yaml create mode 100644 Documentation/devicetree/bindings/virtio/virtio-device.yaml create mode 100644 Documentation/devicetree/bindings/w1/fsl-imx-owire.yaml create mode 100644 Documentation/devicetree/bindings/w1/omap-hdq.txt create mode 100644 Documentation/devicetree/bindings/w1/w1-gpio.yaml create mode 100644 Documentation/devicetree/bindings/w1/w1.txt create mode 100644 Documentation/devicetree/bindings/watchdog/allwinner,sun4i-a10-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/alphascale-asm9260.txt create mode 100644 Documentation/devicetree/bindings/watchdog/amlogic,meson-gxbb-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/apple,wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/arm,sbsa-gwdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/arm,sp805.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/arm,twd-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/arm-smc-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/armada-37xx-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/atmel,at91sam9-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/atmel,sama5d4-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/atmel-at91rm9200-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/brcm,bcm2835-pm-wdog.txt create mode 100644 Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/brcm,kona-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/cadence-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/da9062-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/davinci-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/digicolor-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/faraday,ftwdt010.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/fsl,scu-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/fsl-imx7ulp-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/gpio-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/imgpdc-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/intel,keembay-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/kontron,sl28cpld-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/lantiq-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/lpc18xx-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/marvel.txt create mode 100644 Documentation/devicetree/bindings/watchdog/maxim,max63xx.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/mediatek,mt7621-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/men-a021-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/meson-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/microchip,pic32-dmt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/microchip,pic32-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/moxa,moxart-watchdog.txt create mode 100644 Documentation/devicetree/bindings/watchdog/mpc8xxx-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/mstar,msc313e-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/mtk-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/nuvoton,npcm-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/omap-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/pnx4008-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/qca-ar7130-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/qcom,pm8916-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/qcom-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/realtek,otto-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/realtek,rtd119x.txt create mode 100644 Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/rt2880-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/samsung-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/snps,dw-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/sprd-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/st_lpc_wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/sunplus,sp7021-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/toshiba,visconti-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/ts4800-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/twl4030-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/watchdog.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/xlnx,xps-timebase-wdt.yaml create mode 100644 Documentation/devicetree/bindings/watchdog/zii,rave-sp-wdt.txt create mode 100644 Documentation/devicetree/bindings/watchdog/ziirave-wdt.txt create mode 100644 Documentation/devicetree/bindings/writing-bindings.rst create mode 100644 Documentation/devicetree/bindings/writing-schema.rst create mode 100644 Documentation/devicetree/bindings/x86/ce4100.txt create mode 100644 Documentation/devicetree/bindings/x86/timer.txt create mode 100644 Documentation/devicetree/bindings/xilinx.txt create mode 100644 Documentation/devicetree/bindings/xillybus/xillybus.txt create mode 100644 Documentation/devicetree/changesets.rst create mode 100644 Documentation/devicetree/dynamic-resolution-notes.rst create mode 100644 Documentation/devicetree/index.rst create mode 100644 Documentation/devicetree/kernel-api.rst create mode 100644 Documentation/devicetree/of_unittest.rst create mode 100644 Documentation/devicetree/overlay-notes.rst create mode 100644 Documentation/devicetree/usage-model.rst create mode 100644 Documentation/doc-guide/contributing.rst create mode 100644 Documentation/doc-guide/hello.dot create mode 100644 Documentation/doc-guide/index.rst create mode 100644 Documentation/doc-guide/kernel-doc.rst create mode 100644 Documentation/doc-guide/maintainer-profile.rst create mode 100644 Documentation/doc-guide/parse-headers.rst create mode 100644 Documentation/doc-guide/sphinx.rst create mode 100644 Documentation/doc-guide/svg_image.svg create mode 100644 Documentation/docutils.conf create mode 100644 Documentation/dontdiff create mode 100644 Documentation/driver-api/80211/cfg80211.rst create mode 100644 Documentation/driver-api/80211/index.rst create mode 100644 Documentation/driver-api/80211/introduction.rst create mode 100644 Documentation/driver-api/80211/mac80211-advanced.rst create mode 100644 Documentation/driver-api/80211/mac80211.rst create mode 100644 Documentation/driver-api/acpi/index.rst create mode 100644 Documentation/driver-api/acpi/linuxized-acpica.rst create mode 100644 Documentation/driver-api/acpi/scan_handlers.rst create mode 100644 Documentation/driver-api/aperture.rst create mode 100644 Documentation/driver-api/auxiliary_bus.rst create mode 100644 Documentation/driver-api/backlight/lp855x-driver.rst create mode 100644 Documentation/driver-api/basics.rst create mode 100644 Documentation/driver-api/clk.rst create mode 100644 Documentation/driver-api/component.rst create mode 100644 Documentation/driver-api/connector.rst create mode 100644 Documentation/driver-api/console.rst create mode 100644 Documentation/driver-api/cxl/index.rst create mode 100644 Documentation/driver-api/cxl/memory-devices.rst create mode 100644 Documentation/driver-api/dcdbas.rst create mode 100644 Documentation/driver-api/devfreq.rst create mode 100644 Documentation/driver-api/device-io.rst create mode 100644 Documentation/driver-api/device_link.rst create mode 100644 Documentation/driver-api/dma-buf.rst create mode 100644 Documentation/driver-api/dmaengine/client.rst create mode 100644 Documentation/driver-api/dmaengine/dmatest.rst create mode 100644 Documentation/driver-api/dmaengine/index.rst create mode 100644 Documentation/driver-api/dmaengine/provider.rst create mode 100644 Documentation/driver-api/dmaengine/pxa_dma.rst create mode 100644 Documentation/driver-api/driver-model/binding.rst create mode 100644 Documentation/driver-api/driver-model/bus.rst create mode 100644 Documentation/driver-api/driver-model/design-patterns.rst create mode 100644 Documentation/driver-api/driver-model/device.rst create mode 100644 Documentation/driver-api/driver-model/devres.rst create mode 100644 Documentation/driver-api/driver-model/driver.rst create mode 100644 Documentation/driver-api/driver-model/index.rst create mode 100644 Documentation/driver-api/driver-model/overview.rst create mode 100644 Documentation/driver-api/driver-model/platform.rst create mode 100644 Documentation/driver-api/driver-model/porting.rst create mode 100644 Documentation/driver-api/early-userspace/buffer-format.rst create mode 100644 Documentation/driver-api/early-userspace/early_userspace_support.rst create mode 100644 Documentation/driver-api/early-userspace/index.rst create mode 100644 Documentation/driver-api/edac.rst create mode 100644 Documentation/driver-api/eisa.rst create mode 100644 Documentation/driver-api/firewire.rst create mode 100644 Documentation/driver-api/firmware/built-in-fw.rst create mode 100644 Documentation/driver-api/firmware/core.rst create mode 100644 Documentation/driver-api/firmware/direct-fs-lookup.rst create mode 100644 Documentation/driver-api/firmware/efi/index.rst create mode 100644 Documentation/driver-api/firmware/fallback-mechanisms.rst create mode 100644 Documentation/driver-api/firmware/firmware-usage-guidelines.rst create mode 100644 Documentation/driver-api/firmware/firmware_cache.rst create mode 100644 Documentation/driver-api/firmware/fw_search_path.rst create mode 100644 Documentation/driver-api/firmware/fw_upload.rst create mode 100644 Documentation/driver-api/firmware/index.rst create mode 100644 Documentation/driver-api/firmware/introduction.rst create mode 100644 Documentation/driver-api/firmware/lookup-order.rst create mode 100644 Documentation/driver-api/firmware/other_interfaces.rst create mode 100644 Documentation/driver-api/firmware/request_firmware.rst create mode 100644 Documentation/driver-api/fpga/fpga-bridge.rst create mode 100644 Documentation/driver-api/fpga/fpga-mgr.rst create mode 100644 Documentation/driver-api/fpga/fpga-programming.rst create mode 100644 Documentation/driver-api/fpga/fpga-region.rst create mode 100644 Documentation/driver-api/fpga/index.rst create mode 100644 Documentation/driver-api/fpga/intro.rst create mode 100644 Documentation/driver-api/frame-buffer.rst create mode 100644 Documentation/driver-api/generic-counter.rst create mode 100644 Documentation/driver-api/gpio/board.rst create mode 100644 Documentation/driver-api/gpio/bt8xxgpio.rst create mode 100644 Documentation/driver-api/gpio/consumer.rst create mode 100644 Documentation/driver-api/gpio/driver.rst create mode 100644 Documentation/driver-api/gpio/drivers-on-gpio.rst create mode 100644 Documentation/driver-api/gpio/index.rst create mode 100644 Documentation/driver-api/gpio/intro.rst create mode 100644 Documentation/driver-api/gpio/legacy.rst create mode 100644 Documentation/driver-api/gpio/using-gpio.rst create mode 100644 Documentation/driver-api/hsi.rst create mode 100644 Documentation/driver-api/hte/hte.rst create mode 100644 Documentation/driver-api/hte/index.rst create mode 100644 Documentation/driver-api/hte/tegra194-hte.rst create mode 100644 Documentation/driver-api/i2c.rst create mode 100644 Documentation/driver-api/i3c/device-driver-api.rst create mode 100644 Documentation/driver-api/i3c/index.rst create mode 100644 Documentation/driver-api/i3c/master-driver-api.rst create mode 100644 Documentation/driver-api/i3c/protocol.rst create mode 100644 Documentation/driver-api/iio/buffers.rst create mode 100644 Documentation/driver-api/iio/core.rst create mode 100644 Documentation/driver-api/iio/hw-consumer.rst create mode 100644 Documentation/driver-api/iio/index.rst create mode 100644 Documentation/driver-api/iio/intro.rst create mode 100644 Documentation/driver-api/iio/triggered-buffers.rst create mode 100644 Documentation/driver-api/iio/triggers.rst create mode 100644 Documentation/driver-api/index.rst create mode 100644 Documentation/driver-api/infiniband.rst create mode 100644 Documentation/driver-api/infrastructure.rst create mode 100644 Documentation/driver-api/input.rst create mode 100644 Documentation/driver-api/interconnect.rst create mode 100644 Documentation/driver-api/io-mapping.rst create mode 100644 Documentation/driver-api/io_ordering.rst create mode 100644 Documentation/driver-api/ioctl.rst create mode 100644 Documentation/driver-api/ipmb.rst create mode 100644 Documentation/driver-api/ipmi.rst create mode 100644 Documentation/driver-api/isa.rst create mode 100644 Documentation/driver-api/isapnp.rst create mode 100644 Documentation/driver-api/libata.rst create mode 100644 Documentation/driver-api/mailbox.rst create mode 100644 Documentation/driver-api/md/index.rst create mode 100644 Documentation/driver-api/md/md-cluster.rst create mode 100644 Documentation/driver-api/md/raid5-cache.rst create mode 100644 Documentation/driver-api/md/raid5-ppl.rst create mode 100644 Documentation/driver-api/media/camera-sensor.rst create mode 100644 Documentation/driver-api/media/cec-core.rst create mode 100644 Documentation/driver-api/media/drivers/bttv-devel.rst create mode 100644 Documentation/driver-api/media/drivers/ccs/ccs-regs.asc create mode 100644 Documentation/driver-api/media/drivers/ccs/ccs.rst create mode 100755 Documentation/driver-api/media/drivers/ccs/mk-ccs-regs create mode 100644 Documentation/driver-api/media/drivers/contributors.rst create mode 100644 Documentation/driver-api/media/drivers/cpia2_devel.rst create mode 100644 Documentation/driver-api/media/drivers/cx2341x-devel.rst create mode 100644 Documentation/driver-api/media/drivers/cx88-devel.rst create mode 100644 Documentation/driver-api/media/drivers/davinci-vpbe-devel.rst create mode 100644 Documentation/driver-api/media/drivers/dvb-usb.rst create mode 100644 Documentation/driver-api/media/drivers/fimc-devel.rst create mode 100644 Documentation/driver-api/media/drivers/frontends.rst create mode 100644 Documentation/driver-api/media/drivers/index.rst create mode 100644 Documentation/driver-api/media/drivers/pvrusb2.rst create mode 100644 Documentation/driver-api/media/drivers/pxa_camera.rst create mode 100644 Documentation/driver-api/media/drivers/radiotrack.rst create mode 100644 Documentation/driver-api/media/drivers/rkisp1.rst create mode 100644 Documentation/driver-api/media/drivers/saa7134-devel.rst create mode 100644 Documentation/driver-api/media/drivers/sh_mobile_ceu_camera.rst create mode 100644 Documentation/driver-api/media/drivers/tuners.rst create mode 100644 Documentation/driver-api/media/drivers/vidtv.rst create mode 100644 Documentation/driver-api/media/drivers/vimc-devel.rst create mode 100644 Documentation/driver-api/media/drivers/zoran.rst create mode 100644 Documentation/driver-api/media/dtv-ca.rst create mode 100644 Documentation/driver-api/media/dtv-common.rst create mode 100644 Documentation/driver-api/media/dtv-core.rst create mode 100644 Documentation/driver-api/media/dtv-demux.rst create mode 100644 Documentation/driver-api/media/dtv-frontend.rst create mode 100644 Documentation/driver-api/media/dtv-net.rst create mode 100644 Documentation/driver-api/media/index.rst create mode 100644 Documentation/driver-api/media/maintainer-entry-profile.rst create mode 100644 Documentation/driver-api/media/mc-core.rst create mode 100644 Documentation/driver-api/media/rc-core.rst create mode 100644 Documentation/driver-api/media/tx-rx.rst create mode 100644 Documentation/driver-api/media/v4l2-async.rst create mode 100644 Documentation/driver-api/media/v4l2-common.rst create mode 100644 Documentation/driver-api/media/v4l2-controls.rst create mode 100644 Documentation/driver-api/media/v4l2-core.rst create mode 100644 Documentation/driver-api/media/v4l2-dev.rst create mode 100644 Documentation/driver-api/media/v4l2-device.rst create mode 100644 Documentation/driver-api/media/v4l2-dv-timings.rst create mode 100644 Documentation/driver-api/media/v4l2-event.rst create mode 100644 Documentation/driver-api/media/v4l2-fh.rst create mode 100644 Documentation/driver-api/media/v4l2-flash-led-class.rst create mode 100644 Documentation/driver-api/media/v4l2-fwnode.rst create mode 100644 Documentation/driver-api/media/v4l2-intro.rst create mode 100644 Documentation/driver-api/media/v4l2-mc.rst create mode 100644 Documentation/driver-api/media/v4l2-mediabus.rst create mode 100644 Documentation/driver-api/media/v4l2-mem2mem.rst create mode 100644 Documentation/driver-api/media/v4l2-rect.rst create mode 100644 Documentation/driver-api/media/v4l2-subdev.rst create mode 100644 Documentation/driver-api/media/v4l2-tuner.rst create mode 100644 Documentation/driver-api/media/v4l2-tveeprom.rst create mode 100644 Documentation/driver-api/media/v4l2-videobuf.rst create mode 100644 Documentation/driver-api/media/v4l2-videobuf2.rst create mode 100644 Documentation/driver-api/mei/hdcp.rst create mode 100644 Documentation/driver-api/mei/iamt.rst create mode 100644 Documentation/driver-api/mei/index.rst create mode 100644 Documentation/driver-api/mei/mei-client-bus.rst create mode 100644 Documentation/driver-api/mei/mei.rst create mode 100644 Documentation/driver-api/mei/nfc.rst create mode 100644 Documentation/driver-api/memory-devices/index.rst create mode 100644 Documentation/driver-api/memory-devices/ti-emif.rst create mode 100644 Documentation/driver-api/memory-devices/ti-gpmc.rst create mode 100644 Documentation/driver-api/men-chameleon-bus.rst create mode 100644 Documentation/driver-api/message-based.rst create mode 100644 Documentation/driver-api/misc_devices.rst create mode 100644 Documentation/driver-api/miscellaneous.rst create mode 100644 Documentation/driver-api/mmc/index.rst create mode 100644 Documentation/driver-api/mmc/mmc-async-req.rst create mode 100644 Documentation/driver-api/mmc/mmc-dev-attrs.rst create mode 100644 Documentation/driver-api/mmc/mmc-dev-parts.rst create mode 100644 Documentation/driver-api/mmc/mmc-tools.rst create mode 100644 Documentation/driver-api/mtd/index.rst create mode 100644 Documentation/driver-api/mtd/nand_ecc.rst create mode 100644 Documentation/driver-api/mtd/spi-intel.rst create mode 100644 Documentation/driver-api/mtd/spi-nor.rst create mode 100644 Documentation/driver-api/mtdnand.rst create mode 100644 Documentation/driver-api/nfc/index.rst create mode 100644 Documentation/driver-api/nfc/nfc-hci.rst create mode 100644 Documentation/driver-api/nfc/nfc-pn544.rst create mode 100644 Documentation/driver-api/ntb.rst create mode 100644 Documentation/driver-api/nvdimm/btt.rst create mode 100644 Documentation/driver-api/nvdimm/firmware-activate.rst create mode 100644 Documentation/driver-api/nvdimm/index.rst create mode 100644 Documentation/driver-api/nvdimm/nvdimm.rst create mode 100644 Documentation/driver-api/nvdimm/security.rst create mode 100644 Documentation/driver-api/nvmem.rst create mode 100644 Documentation/driver-api/parport-lowlevel.rst create mode 100644 Documentation/driver-api/pci/index.rst create mode 100644 Documentation/driver-api/pci/p2pdma.rst create mode 100644 Documentation/driver-api/pci/pci.rst create mode 100644 Documentation/driver-api/phy/index.rst create mode 100644 Documentation/driver-api/phy/phy.rst create mode 100644 Documentation/driver-api/phy/samsung-usb2.rst create mode 100644 Documentation/driver-api/pin-control.rst create mode 100644 Documentation/driver-api/pldmfw/driver-ops.rst create mode 100644 Documentation/driver-api/pldmfw/file-format.rst create mode 100644 Documentation/driver-api/pldmfw/index.rst create mode 100644 Documentation/driver-api/pm/cpuidle.rst create mode 100644 Documentation/driver-api/pm/devices.rst create mode 100644 Documentation/driver-api/pm/index.rst create mode 100644 Documentation/driver-api/pm/notifiers.rst create mode 100644 Documentation/driver-api/pm/types.rst create mode 100644 Documentation/driver-api/pps.rst create mode 100644 Documentation/driver-api/ptp.rst create mode 100644 Documentation/driver-api/pwm.rst create mode 100644 Documentation/driver-api/rapidio/index.rst create mode 100644 Documentation/driver-api/rapidio/mport_cdev.rst create mode 100644 Documentation/driver-api/rapidio/rapidio.rst create mode 100644 Documentation/driver-api/rapidio/rio_cm.rst create mode 100644 Documentation/driver-api/rapidio/sysfs.rst create mode 100644 Documentation/driver-api/rapidio/tsi721.rst create mode 100644 Documentation/driver-api/regulator.rst create mode 100644 Documentation/driver-api/reset.rst create mode 100644 Documentation/driver-api/rfkill.rst create mode 100644 Documentation/driver-api/s390-drivers.rst create mode 100644 Documentation/driver-api/scsi.rst create mode 100644 Documentation/driver-api/serial/driver.rst create mode 100644 Documentation/driver-api/serial/index.rst create mode 100644 Documentation/driver-api/serial/serial-iso7816.rst create mode 100644 Documentation/driver-api/serial/serial-rs485.rst create mode 100644 Documentation/driver-api/slimbus.rst create mode 100644 Documentation/driver-api/sm501.rst create mode 100644 Documentation/driver-api/soundwire/error_handling.rst create mode 100644 Documentation/driver-api/soundwire/index.rst create mode 100644 Documentation/driver-api/soundwire/locking.rst create mode 100644 Documentation/driver-api/soundwire/stream.rst create mode 100644 Documentation/driver-api/soundwire/summary.rst create mode 100644 Documentation/driver-api/spi.rst create mode 100644 Documentation/driver-api/surface_aggregator/client-api.rst create mode 100644 Documentation/driver-api/surface_aggregator/client.rst create mode 100644 Documentation/driver-api/surface_aggregator/clients/cdev.rst create mode 100644 Documentation/driver-api/surface_aggregator/clients/dtx.rst create mode 100644 Documentation/driver-api/surface_aggregator/clients/index.rst create mode 100644 Documentation/driver-api/surface_aggregator/clients/san.rst create mode 100644 Documentation/driver-api/surface_aggregator/index.rst create mode 100644 Documentation/driver-api/surface_aggregator/internal-api.rst create mode 100644 Documentation/driver-api/surface_aggregator/internal.rst create mode 100644 Documentation/driver-api/surface_aggregator/overview.rst create mode 100644 Documentation/driver-api/surface_aggregator/ssh.rst create mode 100644 Documentation/driver-api/switchtec.rst create mode 100644 Documentation/driver-api/sync_file.rst create mode 100644 Documentation/driver-api/target.rst create mode 100644 Documentation/driver-api/thermal/cpu-cooling-api.rst create mode 100644 Documentation/driver-api/thermal/cpu-idle-cooling.rst create mode 100644 Documentation/driver-api/thermal/exynos_thermal.rst create mode 100644 Documentation/driver-api/thermal/exynos_thermal_emulation.rst create mode 100644 Documentation/driver-api/thermal/index.rst create mode 100644 Documentation/driver-api/thermal/intel_dptf.rst create mode 100644 Documentation/driver-api/thermal/intel_powerclamp.rst create mode 100644 Documentation/driver-api/thermal/nouveau_thermal.rst create mode 100644 Documentation/driver-api/thermal/power_allocator.rst create mode 100644 Documentation/driver-api/thermal/sysfs-api.rst create mode 100644 Documentation/driver-api/thermal/x86_pkg_temperature_thermal.rst create mode 100644 Documentation/driver-api/tty/index.rst create mode 100644 Documentation/driver-api/tty/moxa-smartio.rst create mode 100644 Documentation/driver-api/tty/n_gsm.rst create mode 100644 Documentation/driver-api/tty/n_tty.rst create mode 100644 Documentation/driver-api/tty/tty_buffer.rst create mode 100644 Documentation/driver-api/tty/tty_driver.rst create mode 100644 Documentation/driver-api/tty/tty_internals.rst create mode 100644 Documentation/driver-api/tty/tty_ldisc.rst create mode 100644 Documentation/driver-api/tty/tty_port.rst create mode 100644 Documentation/driver-api/tty/tty_struct.rst create mode 100644 Documentation/driver-api/uio-howto.rst create mode 100644 Documentation/driver-api/usb/URB.rst create mode 100644 Documentation/driver-api/usb/anchors.rst create mode 100644 Documentation/driver-api/usb/bulk-streams.rst create mode 100644 Documentation/driver-api/usb/callbacks.rst create mode 100644 Documentation/driver-api/usb/dma.rst create mode 100644 Documentation/driver-api/usb/dwc3.rst create mode 100644 Documentation/driver-api/usb/error-codes.rst create mode 100644 Documentation/driver-api/usb/gadget.rst create mode 100644 Documentation/driver-api/usb/hotplug.rst create mode 100644 Documentation/driver-api/usb/index.rst create mode 100644 Documentation/driver-api/usb/persist.rst create mode 100644 Documentation/driver-api/usb/power-management.rst create mode 100644 Documentation/driver-api/usb/typec.rst create mode 100644 Documentation/driver-api/usb/typec_bus.rst create mode 100644 Documentation/driver-api/usb/usb.rst create mode 100644 Documentation/driver-api/usb/usb3-debug-port.rst create mode 100644 Documentation/driver-api/usb/writing_musb_glue_layer.rst create mode 100644 Documentation/driver-api/usb/writing_usb_driver.rst create mode 100644 Documentation/driver-api/vfio-mediated-device.rst create mode 100644 Documentation/driver-api/vfio-pci-device-specific-driver-acceptance.rst create mode 100644 Documentation/driver-api/vfio.rst create mode 100644 Documentation/driver-api/vme.rst create mode 100644 Documentation/driver-api/w1.rst create mode 100644 Documentation/driver-api/xilinx/eemi.rst create mode 100644 Documentation/driver-api/xilinx/index.rst create mode 100644 Documentation/driver-api/xillybus.rst create mode 100644 Documentation/driver-api/zorro.rst create mode 100644 Documentation/fault-injection/fault-injection.rst create mode 100644 Documentation/fault-injection/index.rst create mode 100644 Documentation/fault-injection/notifier-error-inject.rst create mode 100644 Documentation/fault-injection/nvme-fault-injection.rst create mode 100644 Documentation/fault-injection/provoke-crashes.rst create mode 100644 Documentation/fb/api.rst create mode 100644 Documentation/fb/arkfb.rst create mode 100644 Documentation/fb/aty128fb.rst create mode 100644 Documentation/fb/cirrusfb.rst create mode 100644 Documentation/fb/cmap_xfbdev.rst create mode 100644 Documentation/fb/deferred_io.rst create mode 100644 Documentation/fb/efifb.rst create mode 100644 Documentation/fb/ep93xx-fb.rst create mode 100644 Documentation/fb/fbcon.rst create mode 100644 Documentation/fb/framebuffer.rst create mode 100644 Documentation/fb/gxfb.rst create mode 100644 Documentation/fb/index.rst create mode 100644 Documentation/fb/intel810.rst create mode 100644 Documentation/fb/intelfb.rst create mode 100644 Documentation/fb/internals.rst create mode 100644 Documentation/fb/lxfb.rst create mode 100644 Documentation/fb/matroxfb.rst create mode 100644 Documentation/fb/metronomefb.rst create mode 100644 Documentation/fb/modedb.rst create mode 100644 Documentation/fb/pvr2fb.rst create mode 100644 Documentation/fb/pxafb.rst create mode 100644 Documentation/fb/s3fb.rst create mode 100644 Documentation/fb/sa1100fb.rst create mode 100644 Documentation/fb/sh7760fb.rst create mode 100644 Documentation/fb/sisfb.rst create mode 100644 Documentation/fb/sm501.rst create mode 100644 Documentation/fb/sm712fb.rst create mode 100644 Documentation/fb/sstfb.rst create mode 100644 Documentation/fb/tgafb.rst create mode 100644 Documentation/fb/tridentfb.rst create mode 100644 Documentation/fb/udlfb.rst create mode 100644 Documentation/fb/uvesafb.rst create mode 100644 Documentation/fb/vesafb.rst create mode 100644 Documentation/fb/viafb.modes create mode 100644 Documentation/fb/viafb.rst create mode 100644 Documentation/fb/vt8623fb.rst create mode 100644 Documentation/features/arch-support.txt create mode 100644 Documentation/features/core/cBPF-JIT/arch-support.txt create mode 100644 Documentation/features/core/eBPF-JIT/arch-support.txt create mode 100644 Documentation/features/core/generic-idle-thread/arch-support.txt create mode 100644 Documentation/features/core/jump-labels/arch-support.txt create mode 100644 Documentation/features/core/thread-info-in-task/arch-support.txt create mode 100644 Documentation/features/core/tracehook/arch-support.txt create mode 100644 Documentation/features/debug/KASAN/arch-support.txt create mode 100644 Documentation/features/debug/debug-vm-pgtable/arch-support.txt create mode 100644 Documentation/features/debug/gcov-profile-all/arch-support.txt create mode 100644 Documentation/features/debug/kcov/arch-support.txt create mode 100644 Documentation/features/debug/kgdb/arch-support.txt create mode 100644 Documentation/features/debug/kmemleak/arch-support.txt create mode 100644 Documentation/features/debug/kprobes-on-ftrace/arch-support.txt create mode 100644 Documentation/features/debug/kprobes/arch-support.txt create mode 100644 Documentation/features/debug/kretprobes/arch-support.txt create mode 100644 Documentation/features/debug/optprobes/arch-support.txt create mode 100644 Documentation/features/debug/stackprotector/arch-support.txt create mode 100644 Documentation/features/debug/uprobes/arch-support.txt create mode 100644 Documentation/features/debug/user-ret-profiler/arch-support.txt create mode 100644 Documentation/features/io/dma-contiguous/arch-support.txt create mode 100755 Documentation/features/list-arch.sh create mode 100644 Documentation/features/locking/cmpxchg-local/arch-support.txt create mode 100644 Documentation/features/locking/lockdep/arch-support.txt create mode 100644 Documentation/features/locking/queued-rwlocks/arch-support.txt create mode 100644 Documentation/features/locking/queued-spinlocks/arch-support.txt create mode 100644 Documentation/features/perf/kprobes-event/arch-support.txt create mode 100644 Documentation/features/perf/perf-regs/arch-support.txt create mode 100644 Documentation/features/perf/perf-stackdump/arch-support.txt create mode 100644 Documentation/features/sched/membarrier-sync-core/arch-support.txt create mode 100644 Documentation/features/sched/numa-balancing/arch-support.txt create mode 100755 Documentation/features/scripts/features-refresh.sh create mode 100644 Documentation/features/seccomp/seccomp-filter/arch-support.txt create mode 100644 Documentation/features/time/arch-tick-broadcast/arch-support.txt create mode 100644 Documentation/features/time/clockevents/arch-support.txt create mode 100644 Documentation/features/time/context-tracking/arch-support.txt create mode 100644 Documentation/features/time/irq-time-acct/arch-support.txt create mode 100644 Documentation/features/time/virt-cpuacct/arch-support.txt create mode 100644 Documentation/features/vm/ELF-ASLR/arch-support.txt create mode 100644 Documentation/features/vm/PG_uncached/arch-support.txt create mode 100644 Documentation/features/vm/THP/arch-support.txt create mode 100644 Documentation/features/vm/TLB/arch-support.txt create mode 100644 Documentation/features/vm/huge-vmap/arch-support.txt create mode 100644 Documentation/features/vm/ioremap_prot/arch-support.txt create mode 100644 Documentation/features/vm/pte_special/arch-support.txt create mode 100644 Documentation/filesystems/9p.rst create mode 100644 Documentation/filesystems/adfs.rst create mode 100644 Documentation/filesystems/affs.rst create mode 100644 Documentation/filesystems/afs.rst create mode 100644 Documentation/filesystems/api-summary.rst create mode 100644 Documentation/filesystems/autofs-mount-control.rst create mode 100644 Documentation/filesystems/autofs.rst create mode 100644 Documentation/filesystems/automount-support.rst create mode 100644 Documentation/filesystems/befs.rst create mode 100644 Documentation/filesystems/bfs.rst create mode 100644 Documentation/filesystems/btrfs.rst create mode 100644 Documentation/filesystems/caching/backend-api.rst create mode 100644 Documentation/filesystems/caching/cachefiles.rst create mode 100644 Documentation/filesystems/caching/fscache.rst create mode 100644 Documentation/filesystems/caching/index.rst create mode 100644 Documentation/filesystems/caching/netfs-api.rst create mode 100644 Documentation/filesystems/ceph.rst create mode 100644 Documentation/filesystems/cifs/cifsroot.rst create mode 100644 Documentation/filesystems/cifs/index.rst create mode 100644 Documentation/filesystems/cifs/ksmbd.rst create mode 100644 Documentation/filesystems/coda.rst create mode 100644 Documentation/filesystems/configfs.rst create mode 100644 Documentation/filesystems/cramfs.rst create mode 100644 Documentation/filesystems/dax.rst create mode 100644 Documentation/filesystems/debugfs.rst create mode 100644 Documentation/filesystems/devpts.rst create mode 100644 Documentation/filesystems/directory-locking.rst create mode 100644 Documentation/filesystems/dlmfs.rst create mode 100644 Documentation/filesystems/dnotify.rst create mode 100644 Documentation/filesystems/ecryptfs.rst create mode 100644 Documentation/filesystems/efivarfs.rst create mode 100644 Documentation/filesystems/erofs.rst create mode 100644 Documentation/filesystems/ext2.rst create mode 100644 Documentation/filesystems/ext3.rst create mode 100644 Documentation/filesystems/ext4/about.rst create mode 100644 Documentation/filesystems/ext4/allocators.rst create mode 100644 Documentation/filesystems/ext4/attributes.rst create mode 100644 Documentation/filesystems/ext4/bigalloc.rst create mode 100644 Documentation/filesystems/ext4/bitmaps.rst create mode 100644 Documentation/filesystems/ext4/blockgroup.rst create mode 100644 Documentation/filesystems/ext4/blockmap.rst create mode 100644 Documentation/filesystems/ext4/blocks.rst create mode 100644 Documentation/filesystems/ext4/checksums.rst create mode 100644 Documentation/filesystems/ext4/directory.rst create mode 100644 Documentation/filesystems/ext4/dynamic.rst create mode 100644 Documentation/filesystems/ext4/eainode.rst create mode 100644 Documentation/filesystems/ext4/globals.rst create mode 100644 Documentation/filesystems/ext4/group_descr.rst create mode 100644 Documentation/filesystems/ext4/ifork.rst create mode 100644 Documentation/filesystems/ext4/index.rst create mode 100644 Documentation/filesystems/ext4/inlinedata.rst create mode 100644 Documentation/filesystems/ext4/inodes.rst create mode 100644 Documentation/filesystems/ext4/journal.rst create mode 100644 Documentation/filesystems/ext4/mmp.rst create mode 100644 Documentation/filesystems/ext4/orphan.rst create mode 100644 Documentation/filesystems/ext4/overview.rst create mode 100644 Documentation/filesystems/ext4/special_inodes.rst create mode 100644 Documentation/filesystems/ext4/super.rst create mode 100644 Documentation/filesystems/ext4/verity.rst create mode 100644 Documentation/filesystems/f2fs.rst create mode 100644 Documentation/filesystems/fiemap.rst create mode 100644 Documentation/filesystems/files.rst create mode 100644 Documentation/filesystems/fscrypt.rst create mode 100644 Documentation/filesystems/fsverity.rst create mode 100644 Documentation/filesystems/fuse-io.rst create mode 100644 Documentation/filesystems/fuse.rst create mode 100644 Documentation/filesystems/gfs2-glocks.rst create mode 100644 Documentation/filesystems/gfs2-uevents.rst create mode 100644 Documentation/filesystems/gfs2.rst create mode 100644 Documentation/filesystems/hfs.rst create mode 100644 Documentation/filesystems/hfsplus.rst create mode 100644 Documentation/filesystems/hpfs.rst create mode 100644 Documentation/filesystems/idmappings.rst create mode 100644 Documentation/filesystems/index.rst create mode 100644 Documentation/filesystems/inotify.rst create mode 100644 Documentation/filesystems/isofs.rst create mode 100644 Documentation/filesystems/journalling.rst create mode 100644 Documentation/filesystems/locking.rst create mode 100644 Documentation/filesystems/locks.rst create mode 100644 Documentation/filesystems/mount_api.rst create mode 100644 Documentation/filesystems/netfs_library.rst create mode 100644 Documentation/filesystems/nfs/client-identifier.rst create mode 100644 Documentation/filesystems/nfs/exporting.rst create mode 100644 Documentation/filesystems/nfs/index.rst create mode 100644 Documentation/filesystems/nfs/knfsd-stats.rst create mode 100644 Documentation/filesystems/nfs/nfs41-server.rst create mode 100644 Documentation/filesystems/nfs/pnfs.rst create mode 100644 Documentation/filesystems/nfs/reexport.rst create mode 100644 Documentation/filesystems/nfs/rpc-cache.rst create mode 100644 Documentation/filesystems/nfs/rpc-server-gss.rst create mode 100644 Documentation/filesystems/nilfs2.rst create mode 100644 Documentation/filesystems/ntfs.rst create mode 100644 Documentation/filesystems/ntfs3.rst create mode 100644 Documentation/filesystems/ocfs2-online-filecheck.rst create mode 100644 Documentation/filesystems/ocfs2.rst create mode 100644 Documentation/filesystems/omfs.rst create mode 100644 Documentation/filesystems/orangefs.rst create mode 100644 Documentation/filesystems/overlayfs.rst create mode 100644 Documentation/filesystems/path-lookup.rst create mode 100644 Documentation/filesystems/path-lookup.txt create mode 100644 Documentation/filesystems/porting.rst create mode 100644 Documentation/filesystems/proc.rst create mode 100644 Documentation/filesystems/qnx6.rst create mode 100644 Documentation/filesystems/quota.rst create mode 100644 Documentation/filesystems/ramfs-rootfs-initramfs.rst create mode 100644 Documentation/filesystems/relay.rst create mode 100644 Documentation/filesystems/romfs.rst create mode 100644 Documentation/filesystems/seq_file.rst create mode 100644 Documentation/filesystems/sharedsubtree.rst create mode 100644 Documentation/filesystems/splice.rst create mode 100644 Documentation/filesystems/spufs/index.rst create mode 100644 Documentation/filesystems/spufs/spu_create.rst create mode 100644 Documentation/filesystems/spufs/spu_run.rst create mode 100644 Documentation/filesystems/spufs/spufs.rst create mode 100644 Documentation/filesystems/squashfs.rst create mode 100644 Documentation/filesystems/sysfs.rst create mode 100644 Documentation/filesystems/sysv-fs.rst create mode 100644 Documentation/filesystems/tmpfs.rst create mode 100644 Documentation/filesystems/ubifs-authentication.rst create mode 100644 Documentation/filesystems/ubifs.rst create mode 100644 Documentation/filesystems/udf.rst create mode 100644 Documentation/filesystems/vfat.rst create mode 100644 Documentation/filesystems/vfs.rst create mode 100644 Documentation/filesystems/virtiofs.rst create mode 100644 Documentation/filesystems/xfs-delayed-logging-design.rst create mode 100644 Documentation/filesystems/xfs-self-describing-metadata.rst create mode 100644 Documentation/filesystems/zonefs.rst create mode 100644 Documentation/firmware-guide/acpi/DSD-properties-rules.rst create mode 100644 Documentation/firmware-guide/acpi/acpi-lid.rst create mode 100644 Documentation/firmware-guide/acpi/aml-debugger.rst create mode 100644 Documentation/firmware-guide/acpi/apei/einj.rst create mode 100644 Documentation/firmware-guide/acpi/apei/output_format.rst create mode 100644 Documentation/firmware-guide/acpi/chromeos-acpi-device.rst create mode 100644 Documentation/firmware-guide/acpi/debug.rst create mode 100644 Documentation/firmware-guide/acpi/dsd/data-node-references.rst create mode 100644 Documentation/firmware-guide/acpi/dsd/graph.rst create mode 100644 Documentation/firmware-guide/acpi/dsd/leds.rst create mode 100644 Documentation/firmware-guide/acpi/dsd/phy.rst create mode 100644 Documentation/firmware-guide/acpi/enumeration.rst create mode 100644 Documentation/firmware-guide/acpi/extcon-intel-int3496.rst create mode 100644 Documentation/firmware-guide/acpi/gpio-properties.rst create mode 100644 Documentation/firmware-guide/acpi/i2c-muxes.rst create mode 100644 Documentation/firmware-guide/acpi/index.rst create mode 100644 Documentation/firmware-guide/acpi/intel-pmc-mux.rst create mode 100644 Documentation/firmware-guide/acpi/lpit.rst create mode 100644 Documentation/firmware-guide/acpi/method-customizing.rst create mode 100644 Documentation/firmware-guide/acpi/method-tracing.rst create mode 100644 Documentation/firmware-guide/acpi/namespace.rst create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst create mode 100644 Documentation/firmware-guide/acpi/osi.rst create mode 100644 Documentation/firmware-guide/acpi/video_extension.rst create mode 100644 Documentation/firmware-guide/index.rst create mode 100644 Documentation/firmware_class/hotplug-script create mode 100644 Documentation/fpga/dfl.rst create mode 100644 Documentation/fpga/index.rst create mode 100644 Documentation/gpu/afbc.rst create mode 100644 Documentation/gpu/amdgpu/amdgpu-glossary.rst create mode 100644 Documentation/gpu/amdgpu/apu-asic-info-table.csv create mode 100644 Documentation/gpu/amdgpu/dgpu-asic-info-table.csv create mode 100644 Documentation/gpu/amdgpu/display/config_example.svg create mode 100644 Documentation/gpu/amdgpu/display/dc-debug.rst create mode 100644 Documentation/gpu/amdgpu/display/dc-glossary.rst create mode 100644 Documentation/gpu/amdgpu/display/dc_pipeline_overview.svg create mode 100644 Documentation/gpu/amdgpu/display/dcn-overview.rst create mode 100644 Documentation/gpu/amdgpu/display/dcn2_cm_drm_current.svg create mode 100644 Documentation/gpu/amdgpu/display/dcn3_cm_drm_current.svg create mode 100644 Documentation/gpu/amdgpu/display/display-manager.rst create mode 100644 Documentation/gpu/amdgpu/display/global_sync_vblank.svg create mode 100644 Documentation/gpu/amdgpu/display/index.rst create mode 100644 Documentation/gpu/amdgpu/display/mpo-cursor.svg create mode 100644 Documentation/gpu/amdgpu/display/mpo-overview.rst create mode 100644 Documentation/gpu/amdgpu/display/multi-display-hdcp-mpo-less-pipe-ex.svg create mode 100644 Documentation/gpu/amdgpu/display/multi-display-hdcp-mpo.svg create mode 100644 Documentation/gpu/amdgpu/display/pipeline_4k_no_split.svg create mode 100644 Documentation/gpu/amdgpu/display/pipeline_4k_split.svg create mode 100644 Documentation/gpu/amdgpu/display/single-display-mpo-multi-video.svg create mode 100644 Documentation/gpu/amdgpu/display/single-display-mpo.svg create mode 100644 Documentation/gpu/amdgpu/driver-core.rst create mode 100644 Documentation/gpu/amdgpu/driver-misc.rst create mode 100644 Documentation/gpu/amdgpu/index.rst create mode 100644 Documentation/gpu/amdgpu/module-parameters.rst create mode 100644 Documentation/gpu/amdgpu/ras.rst create mode 100644 Documentation/gpu/amdgpu/thermal.rst create mode 100644 Documentation/gpu/amdgpu/xgmi.rst create mode 100644 Documentation/gpu/backlight.rst create mode 100644 Documentation/gpu/bridge/dw-hdmi.rst create mode 100644 Documentation/gpu/dp-mst/topology-figure-1.dot create mode 100644 Documentation/gpu/dp-mst/topology-figure-2.dot create mode 100644 Documentation/gpu/dp-mst/topology-figure-3.dot create mode 100644 Documentation/gpu/driver-uapi.rst create mode 100644 Documentation/gpu/drivers.rst create mode 100644 Documentation/gpu/drm-client.rst create mode 100644 Documentation/gpu/drm-internals.rst create mode 100644 Documentation/gpu/drm-kms-helpers.rst create mode 100644 Documentation/gpu/drm-kms.rst create mode 100644 Documentation/gpu/drm-mm.rst create mode 100644 Documentation/gpu/drm-uapi.rst create mode 100644 Documentation/gpu/drm-usage-stats.rst create mode 100644 Documentation/gpu/i915.rst create mode 100644 Documentation/gpu/index.rst create mode 100644 Documentation/gpu/introduction.rst create mode 100644 Documentation/gpu/kms-properties.csv create mode 100644 Documentation/gpu/komeda-kms.rst create mode 100644 Documentation/gpu/mcde.rst create mode 100644 Documentation/gpu/meson.rst create mode 100644 Documentation/gpu/msm-crash-dump.rst create mode 100644 Documentation/gpu/pl111.rst create mode 100644 Documentation/gpu/rfc/i915_gem_lmem.rst create mode 100644 Documentation/gpu/rfc/i915_scheduler.rst create mode 100644 Documentation/gpu/rfc/i915_small_bar.h create mode 100644 Documentation/gpu/rfc/i915_small_bar.rst create mode 100644 Documentation/gpu/rfc/i915_vm_bind.h create mode 100644 Documentation/gpu/rfc/i915_vm_bind.rst create mode 100644 Documentation/gpu/rfc/index.rst create mode 100644 Documentation/gpu/tegra.rst create mode 100644 Documentation/gpu/todo.rst create mode 100644 Documentation/gpu/tve200.rst create mode 100644 Documentation/gpu/v3d.rst create mode 100644 Documentation/gpu/vc4.rst create mode 100644 Documentation/gpu/vga-switcheroo.rst create mode 100644 Documentation/gpu/vgaarbiter.rst create mode 100644 Documentation/gpu/vkms.rst create mode 100644 Documentation/gpu/xen-front.rst create mode 100644 Documentation/hid/amd-sfh-hid.rst create mode 100644 Documentation/hid/hid-alps.rst create mode 100644 Documentation/hid/hid-sensor.rst create mode 100644 Documentation/hid/hid-transport.rst create mode 100644 Documentation/hid/hiddev.rst create mode 100644 Documentation/hid/hidraw.rst create mode 100644 Documentation/hid/index.rst create mode 100644 Documentation/hid/intel-ish-hid.rst create mode 100644 Documentation/hid/uhid.rst create mode 100644 Documentation/hwmon/abituguru-datasheet.rst create mode 100644 Documentation/hwmon/abituguru.rst create mode 100644 Documentation/hwmon/abituguru3.rst create mode 100644 Documentation/hwmon/acpi_power_meter.rst create mode 100644 Documentation/hwmon/ad7314.rst create mode 100644 Documentation/hwmon/adc128d818.rst create mode 100644 Documentation/hwmon/adm1021.rst create mode 100644 Documentation/hwmon/adm1025.rst create mode 100644 Documentation/hwmon/adm1026.rst create mode 100644 Documentation/hwmon/adm1031.rst create mode 100644 Documentation/hwmon/adm1177.rst create mode 100644 Documentation/hwmon/adm1266.rst create mode 100644 Documentation/hwmon/adm1275.rst create mode 100644 Documentation/hwmon/adm9240.rst create mode 100644 Documentation/hwmon/ads7828.rst create mode 100644 Documentation/hwmon/adt7410.rst create mode 100644 Documentation/hwmon/adt7411.rst create mode 100644 Documentation/hwmon/adt7462.rst create mode 100644 Documentation/hwmon/adt7470.rst create mode 100644 Documentation/hwmon/adt7475.rst create mode 100644 Documentation/hwmon/aht10.rst create mode 100644 Documentation/hwmon/amc6821.rst create mode 100644 Documentation/hwmon/aquacomputer_d5next.rst create mode 100644 Documentation/hwmon/asb100.rst create mode 100644 Documentation/hwmon/asc7621.rst create mode 100644 Documentation/hwmon/aspeed-pwm-tacho.rst create mode 100644 Documentation/hwmon/asus_ec_sensors.rst create mode 100644 Documentation/hwmon/asus_wmi_sensors.rst create mode 100644 Documentation/hwmon/bcm54140.rst create mode 100644 Documentation/hwmon/bel-pfe.rst create mode 100644 Documentation/hwmon/bpa-rs600.rst create mode 100644 Documentation/hwmon/bt1-pvt.rst create mode 100644 Documentation/hwmon/coretemp.rst create mode 100644 Documentation/hwmon/corsair-cpro.rst create mode 100644 Documentation/hwmon/corsair-psu.rst create mode 100644 Documentation/hwmon/da9052.rst create mode 100644 Documentation/hwmon/da9055.rst create mode 100644 Documentation/hwmon/dell-smm-hwmon.rst create mode 100644 Documentation/hwmon/dme1737.rst create mode 100644 Documentation/hwmon/dps920ab.rst create mode 100644 Documentation/hwmon/drivetemp.rst create mode 100644 Documentation/hwmon/ds1621.rst create mode 100644 Documentation/hwmon/ds620.rst create mode 100644 Documentation/hwmon/emc1403.rst create mode 100644 Documentation/hwmon/emc2103.rst create mode 100644 Documentation/hwmon/emc2305.rst create mode 100644 Documentation/hwmon/emc6w201.rst create mode 100644 Documentation/hwmon/f71805f.rst create mode 100644 Documentation/hwmon/f71882fg.rst create mode 100644 Documentation/hwmon/fam15h_power.rst create mode 100644 Documentation/hwmon/fsp-3y.rst create mode 100644 Documentation/hwmon/ftsteutates.rst create mode 100644 Documentation/hwmon/g760a.rst create mode 100644 Documentation/hwmon/g762.rst create mode 100644 Documentation/hwmon/gl518sm.rst create mode 100644 Documentation/hwmon/gsc-hwmon.rst create mode 100644 Documentation/hwmon/hih6130.rst create mode 100644 Documentation/hwmon/hwmon-kernel-api.rst create mode 100644 Documentation/hwmon/ibm-cffps.rst create mode 100644 Documentation/hwmon/ibmaem.rst create mode 100644 Documentation/hwmon/ibmpowernv.rst create mode 100644 Documentation/hwmon/ina209.rst create mode 100644 Documentation/hwmon/ina238.rst create mode 100644 Documentation/hwmon/ina2xx.rst create mode 100644 Documentation/hwmon/ina3221.rst create mode 100644 Documentation/hwmon/index.rst create mode 100644 Documentation/hwmon/inspur-ipsps1.rst create mode 100644 Documentation/hwmon/intel-m10-bmc-hwmon.rst create mode 100644 Documentation/hwmon/ir35221.rst create mode 100644 Documentation/hwmon/ir36021.rst create mode 100644 Documentation/hwmon/ir38064.rst create mode 100644 Documentation/hwmon/isl68137.rst create mode 100644 Documentation/hwmon/it87.rst create mode 100644 Documentation/hwmon/jc42.rst create mode 100644 Documentation/hwmon/k10temp.rst create mode 100644 Documentation/hwmon/k8temp.rst create mode 100644 Documentation/hwmon/lan966x.rst create mode 100644 Documentation/hwmon/lineage-pem.rst create mode 100644 Documentation/hwmon/lm25066.rst create mode 100644 Documentation/hwmon/lm63.rst create mode 100644 Documentation/hwmon/lm70.rst create mode 100644 Documentation/hwmon/lm73.rst create mode 100644 Documentation/hwmon/lm75.rst create mode 100644 Documentation/hwmon/lm77.rst create mode 100644 Documentation/hwmon/lm78.rst create mode 100644 Documentation/hwmon/lm80.rst create mode 100644 Documentation/hwmon/lm83.rst create mode 100644 Documentation/hwmon/lm85.rst create mode 100644 Documentation/hwmon/lm87.rst create mode 100644 Documentation/hwmon/lm90.rst create mode 100644 Documentation/hwmon/lm92.rst create mode 100644 Documentation/hwmon/lm93.rst create mode 100644 Documentation/hwmon/lm95234.rst create mode 100644 Documentation/hwmon/lm95245.rst create mode 100644 Documentation/hwmon/lochnagar.rst create mode 100644 Documentation/hwmon/lt7182s.rst create mode 100644 Documentation/hwmon/ltc2945.rst create mode 100644 Documentation/hwmon/ltc2947.rst create mode 100644 Documentation/hwmon/ltc2978.rst create mode 100644 Documentation/hwmon/ltc2990.rst create mode 100644 Documentation/hwmon/ltc2992.rst create mode 100644 Documentation/hwmon/ltc3815.rst create mode 100644 Documentation/hwmon/ltc4151.rst create mode 100644 Documentation/hwmon/ltc4215.rst create mode 100644 Documentation/hwmon/ltc4245.rst create mode 100644 Documentation/hwmon/ltc4260.rst create mode 100644 Documentation/hwmon/ltc4261.rst create mode 100644 Documentation/hwmon/max127.rst create mode 100644 Documentation/hwmon/max15301.rst create mode 100644 Documentation/hwmon/max16064.rst create mode 100644 Documentation/hwmon/max16065.rst create mode 100644 Documentation/hwmon/max1619.rst create mode 100644 Documentation/hwmon/max16601.rst create mode 100644 Documentation/hwmon/max1668.rst create mode 100644 Documentation/hwmon/max197.rst create mode 100644 Documentation/hwmon/max20730.rst create mode 100644 Documentation/hwmon/max20751.rst create mode 100644 Documentation/hwmon/max31722.rst create mode 100644 Documentation/hwmon/max31730.rst create mode 100644 Documentation/hwmon/max31760.rst create mode 100644 Documentation/hwmon/max31785.rst create mode 100644 Documentation/hwmon/max31790.rst create mode 100644 Documentation/hwmon/max34440.rst create mode 100644 Documentation/hwmon/max6620.rst create mode 100644 Documentation/hwmon/max6639.rst create mode 100644 Documentation/hwmon/max6642.rst create mode 100644 Documentation/hwmon/max6650.rst create mode 100644 Documentation/hwmon/max6697.rst create mode 100644 Documentation/hwmon/max8688.rst create mode 100644 Documentation/hwmon/mc13783-adc.rst create mode 100644 Documentation/hwmon/mcp3021.rst create mode 100644 Documentation/hwmon/menf21bmc.rst create mode 100644 Documentation/hwmon/mlxreg-fan.rst create mode 100644 Documentation/hwmon/mp2888.rst create mode 100644 Documentation/hwmon/mp2975.rst create mode 100644 Documentation/hwmon/mp5023.rst create mode 100644 Documentation/hwmon/nct6683.rst create mode 100644 Documentation/hwmon/nct6775.rst create mode 100644 Documentation/hwmon/nct7802.rst create mode 100644 Documentation/hwmon/nct7904.rst create mode 100644 Documentation/hwmon/npcm750-pwm-fan.rst create mode 100644 Documentation/hwmon/nsa320.rst create mode 100644 Documentation/hwmon/ntc_thermistor.rst create mode 100644 Documentation/hwmon/nzxt-kraken2.rst create mode 100644 Documentation/hwmon/nzxt-smart2.rst create mode 100644 Documentation/hwmon/occ.rst create mode 100644 Documentation/hwmon/pc87360.rst create mode 100644 Documentation/hwmon/pc87427.rst create mode 100644 Documentation/hwmon/pcf8591.rst create mode 100644 Documentation/hwmon/peci-cputemp.rst create mode 100644 Documentation/hwmon/peci-dimmtemp.rst create mode 100644 Documentation/hwmon/pim4328.rst create mode 100644 Documentation/hwmon/pli1209bc.rst create mode 100644 Documentation/hwmon/pm6764tr.rst create mode 100644 Documentation/hwmon/pmbus-core.rst create mode 100644 Documentation/hwmon/pmbus.rst create mode 100644 Documentation/hwmon/powr1220.rst create mode 100644 Documentation/hwmon/pwm-fan.rst create mode 100644 Documentation/hwmon/pxe1610.rst create mode 100644 Documentation/hwmon/q54sj108a2.rst create mode 100644 Documentation/hwmon/raspberrypi-hwmon.rst create mode 100644 Documentation/hwmon/sbrmi.rst create mode 100644 Documentation/hwmon/sbtsi_temp.rst create mode 100644 Documentation/hwmon/sch5627.rst create mode 100644 Documentation/hwmon/sch5636.rst create mode 100644 Documentation/hwmon/scpi-hwmon.rst create mode 100644 Documentation/hwmon/sht15.rst create mode 100644 Documentation/hwmon/sht21.rst create mode 100644 Documentation/hwmon/sht3x.rst create mode 100644 Documentation/hwmon/sht4x.rst create mode 100644 Documentation/hwmon/shtc1.rst create mode 100644 Documentation/hwmon/sis5595.rst create mode 100644 Documentation/hwmon/sl28cpld.rst create mode 100644 Documentation/hwmon/smm665.rst create mode 100644 Documentation/hwmon/smsc47b397.rst create mode 100644 Documentation/hwmon/smsc47m1.rst create mode 100644 Documentation/hwmon/smsc47m192.rst create mode 100644 Documentation/hwmon/sparx5-temp.rst create mode 100644 Documentation/hwmon/stpddc60.rst create mode 100644 Documentation/hwmon/submitting-patches.rst create mode 100644 Documentation/hwmon/sy7636a-hwmon.rst create mode 100644 Documentation/hwmon/sysfs-interface.rst create mode 100644 Documentation/hwmon/tc654.rst create mode 100644 Documentation/hwmon/tc74.rst create mode 100644 Documentation/hwmon/thmc50.rst create mode 100644 Documentation/hwmon/tmp102.rst create mode 100644 Documentation/hwmon/tmp103.rst create mode 100644 Documentation/hwmon/tmp108.rst create mode 100644 Documentation/hwmon/tmp401.rst create mode 100644 Documentation/hwmon/tmp421.rst create mode 100644 Documentation/hwmon/tmp464.rst create mode 100644 Documentation/hwmon/tmp513.rst create mode 100644 Documentation/hwmon/tps23861.rst create mode 100644 Documentation/hwmon/tps40422.rst create mode 100644 Documentation/hwmon/tps53679.rst create mode 100644 Documentation/hwmon/tps546d24.rst create mode 100644 Documentation/hwmon/twl4030-madc-hwmon.rst create mode 100644 Documentation/hwmon/ucd9000.rst create mode 100644 Documentation/hwmon/ucd9200.rst create mode 100644 Documentation/hwmon/userspace-tools.rst create mode 100644 Documentation/hwmon/vexpress.rst create mode 100644 Documentation/hwmon/via686a.rst create mode 100644 Documentation/hwmon/vt1211.rst create mode 100644 Documentation/hwmon/w83627ehf.rst create mode 100644 Documentation/hwmon/w83627hf.rst create mode 100644 Documentation/hwmon/w83773g.rst create mode 100644 Documentation/hwmon/w83781d.rst create mode 100644 Documentation/hwmon/w83791d.rst create mode 100644 Documentation/hwmon/w83792d.rst create mode 100644 Documentation/hwmon/w83793.rst create mode 100644 Documentation/hwmon/w83795.rst create mode 100644 Documentation/hwmon/w83l785ts.rst create mode 100644 Documentation/hwmon/w83l786ng.rst create mode 100644 Documentation/hwmon/wm831x.rst create mode 100644 Documentation/hwmon/wm8350.rst create mode 100644 Documentation/hwmon/xdpe12284.rst create mode 100644 Documentation/hwmon/xdpe152c4.rst create mode 100644 Documentation/hwmon/xgene-hwmon.rst create mode 100644 Documentation/hwmon/zl6100.rst create mode 100644 Documentation/i2c/busses/i2c-ali1535.rst create mode 100644 Documentation/i2c/busses/i2c-ali1563.rst create mode 100644 Documentation/i2c/busses/i2c-ali15x3.rst create mode 100644 Documentation/i2c/busses/i2c-amd-mp2.rst create mode 100644 Documentation/i2c/busses/i2c-amd756.rst create mode 100644 Documentation/i2c/busses/i2c-amd8111.rst create mode 100644 Documentation/i2c/busses/i2c-diolan-u2c.rst create mode 100644 Documentation/i2c/busses/i2c-i801.rst create mode 100644 Documentation/i2c/busses/i2c-ismt.rst create mode 100644 Documentation/i2c/busses/i2c-mlxcpld.rst create mode 100644 Documentation/i2c/busses/i2c-nforce2.rst create mode 100644 Documentation/i2c/busses/i2c-nvidia-gpu.rst create mode 100644 Documentation/i2c/busses/i2c-ocores.rst create mode 100644 Documentation/i2c/busses/i2c-parport.rst create mode 100644 Documentation/i2c/busses/i2c-pca-isa.rst create mode 100644 Documentation/i2c/busses/i2c-piix4.rst create mode 100644 Documentation/i2c/busses/i2c-sis5595.rst create mode 100644 Documentation/i2c/busses/i2c-sis630.rst create mode 100644 Documentation/i2c/busses/i2c-sis96x.rst create mode 100644 Documentation/i2c/busses/i2c-taos-evm.rst create mode 100644 Documentation/i2c/busses/i2c-via.rst create mode 100644 Documentation/i2c/busses/i2c-viapro.rst create mode 100644 Documentation/i2c/busses/index.rst create mode 100644 Documentation/i2c/busses/scx200_acb.rst create mode 100644 Documentation/i2c/dev-interface.rst create mode 100644 Documentation/i2c/dma-considerations.rst create mode 100644 Documentation/i2c/fault-codes.rst create mode 100644 Documentation/i2c/functionality.rst create mode 100644 Documentation/i2c/gpio-fault-injection.rst create mode 100644 Documentation/i2c/i2c-protocol.rst create mode 100644 Documentation/i2c/i2c-stub.rst create mode 100644 Documentation/i2c/i2c-sysfs.rst create mode 100644 Documentation/i2c/i2c-topology.rst create mode 100644 Documentation/i2c/i2c_bus.svg create mode 100644 Documentation/i2c/index.rst create mode 100644 Documentation/i2c/instantiating-devices.rst create mode 100644 Documentation/i2c/muxes/i2c-mux-gpio.rst create mode 100644 Documentation/i2c/old-module-parameters.rst create mode 100644 Documentation/i2c/slave-eeprom-backend.rst create mode 100644 Documentation/i2c/slave-interface.rst create mode 100644 Documentation/i2c/slave-testunit-backend.rst create mode 100644 Documentation/i2c/smbus-protocol.rst create mode 100644 Documentation/i2c/summary.rst create mode 100644 Documentation/i2c/ten-bit-addresses.rst create mode 100644 Documentation/i2c/writing-clients.rst create mode 100644 Documentation/ia64/aliasing.rst create mode 100644 Documentation/ia64/efirtc.rst create mode 100644 Documentation/ia64/err_inject.rst create mode 100644 Documentation/ia64/features.rst create mode 100644 Documentation/ia64/fsys.rst create mode 100644 Documentation/ia64/ia64.rst create mode 100644 Documentation/ia64/index.rst create mode 100644 Documentation/ia64/irq-redir.rst create mode 100644 Documentation/ia64/mca.rst create mode 100644 Documentation/ia64/serial.rst create mode 100644 Documentation/iio/bno055.rst create mode 100644 Documentation/iio/ep93xx_adc.rst create mode 100644 Documentation/iio/iio_configfs.rst create mode 100644 Documentation/iio/index.rst create mode 100644 Documentation/images/COPYING-logo create mode 100644 Documentation/images/logo.gif create mode 100644 Documentation/images/logo.svg create mode 100644 Documentation/index.rst create mode 100644 Documentation/infiniband/core_locking.rst create mode 100644 Documentation/infiniband/index.rst create mode 100644 Documentation/infiniband/ipoib.rst create mode 100644 Documentation/infiniband/opa_vnic.rst create mode 100644 Documentation/infiniband/sysfs.rst create mode 100644 Documentation/infiniband/tag_matching.rst create mode 100644 Documentation/infiniband/user_mad.rst create mode 100644 Documentation/infiniband/user_verbs.rst create mode 100644 Documentation/input/devices/alps.rst create mode 100644 Documentation/input/devices/amijoy.rst create mode 100644 Documentation/input/devices/appletouch.rst create mode 100644 Documentation/input/devices/atarikbd.rst create mode 100644 Documentation/input/devices/bcm5974.rst create mode 100644 Documentation/input/devices/cma3000_d0x.rst create mode 100644 Documentation/input/devices/cs461x.rst create mode 100644 Documentation/input/devices/edt-ft5x06.rst create mode 100644 Documentation/input/devices/elantech.rst create mode 100644 Documentation/input/devices/iforce-protocol.rst create mode 100644 Documentation/input/devices/index.rst create mode 100644 Documentation/input/devices/joystick-parport.rst create mode 100644 Documentation/input/devices/ntrig.rst create mode 100644 Documentation/input/devices/pxrc.rst create mode 100644 Documentation/input/devices/rotary-encoder.rst create mode 100644 Documentation/input/devices/sentelic.rst create mode 100644 Documentation/input/devices/walkera0701.rst create mode 100644 Documentation/input/devices/xpad.rst create mode 100644 Documentation/input/devices/yealink.rst create mode 100644 Documentation/input/event-codes.rst create mode 100644 Documentation/input/ff.rst create mode 100644 Documentation/input/gamepad.rst create mode 100644 Documentation/input/gameport-programming.rst create mode 100644 Documentation/input/index.rst create mode 100644 Documentation/input/input-programming.rst create mode 100644 Documentation/input/input.rst create mode 100644 Documentation/input/input_kapi.rst create mode 100644 Documentation/input/input_uapi.rst create mode 100644 Documentation/input/interactive.svg create mode 100644 Documentation/input/joydev/index.rst create mode 100644 Documentation/input/joydev/joystick-api.rst create mode 100644 Documentation/input/joydev/joystick.rst create mode 100644 Documentation/input/multi-touch-protocol.rst create mode 100644 Documentation/input/notifier.rst create mode 100644 Documentation/input/shape.svg create mode 100644 Documentation/input/uinput.rst create mode 100644 Documentation/input/userio.rst create mode 100644 Documentation/isdn/credits.rst create mode 100644 Documentation/isdn/index.rst create mode 100644 Documentation/isdn/interface_capi.rst create mode 100644 Documentation/isdn/m_isdn.rst create mode 100644 Documentation/kbuild/Kconfig.recursion-issue-01 create mode 100644 Documentation/kbuild/Kconfig.recursion-issue-02 create mode 100644 Documentation/kbuild/Kconfig.select-break create mode 100644 Documentation/kbuild/gcc-plugins.rst create mode 100644 Documentation/kbuild/headers_install.rst create mode 100644 Documentation/kbuild/index.rst create mode 100644 Documentation/kbuild/issues.rst create mode 100644 Documentation/kbuild/kbuild.rst create mode 100644 Documentation/kbuild/kconfig-language.rst create mode 100644 Documentation/kbuild/kconfig-macro-language.rst create mode 100644 Documentation/kbuild/kconfig.rst create mode 100644 Documentation/kbuild/llvm.rst create mode 100644 Documentation/kbuild/makefiles.rst create mode 100644 Documentation/kbuild/modules.rst create mode 100644 Documentation/kbuild/reproducible-builds.rst create mode 100644 Documentation/kernel-hacking/hacking.rst create mode 100644 Documentation/kernel-hacking/index.rst create mode 100644 Documentation/kernel-hacking/locking.rst create mode 100644 Documentation/leds/index.rst create mode 100644 Documentation/leds/leds-blinkm.rst create mode 100644 Documentation/leds/leds-class-flash.rst create mode 100644 Documentation/leds/leds-class-multicolor.rst create mode 100644 Documentation/leds/leds-class.rst create mode 100644 Documentation/leds/leds-el15203000.rst create mode 100644 Documentation/leds/leds-lm3556.rst create mode 100644 Documentation/leds/leds-lp3944.rst create mode 100644 Documentation/leds/leds-lp5521.rst create mode 100644 Documentation/leds/leds-lp5523.rst create mode 100644 Documentation/leds/leds-lp5562.rst create mode 100644 Documentation/leds/leds-lp55xx.rst create mode 100644 Documentation/leds/leds-mlxcpld.rst create mode 100644 Documentation/leds/leds-qcom-lpg.rst create mode 100644 Documentation/leds/leds-sc27xx.rst create mode 100644 Documentation/leds/ledtrig-oneshot.rst create mode 100644 Documentation/leds/ledtrig-transient.rst create mode 100644 Documentation/leds/ledtrig-usbport.rst create mode 100644 Documentation/leds/uleds.rst create mode 100644 Documentation/leds/well-known-leds.txt create mode 100644 Documentation/litmus-tests/README create mode 100644 Documentation/litmus-tests/atomic/Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus create mode 100644 Documentation/litmus-tests/atomic/Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus create mode 100644 Documentation/litmus-tests/rcu/RCU+sync+free.litmus create mode 100644 Documentation/litmus-tests/rcu/RCU+sync+read.litmus create mode 100644 Documentation/livepatch/api.rst create mode 100644 Documentation/livepatch/callbacks.rst create mode 100644 Documentation/livepatch/cumulative-patches.rst create mode 100644 Documentation/livepatch/index.rst create mode 100644 Documentation/livepatch/livepatch.rst create mode 100644 Documentation/livepatch/module-elf-format.rst create mode 100644 Documentation/livepatch/reliable-stacktrace.rst create mode 100644 Documentation/livepatch/shadow-vars.rst create mode 100644 Documentation/livepatch/system-state.rst create mode 100644 Documentation/locking/futex-requeue-pi.rst create mode 100644 Documentation/locking/hwspinlock.rst create mode 100644 Documentation/locking/index.rst create mode 100644 Documentation/locking/lockdep-design.rst create mode 100644 Documentation/locking/lockstat.rst create mode 100644 Documentation/locking/locktorture.rst create mode 100644 Documentation/locking/locktypes.rst create mode 100644 Documentation/locking/mutex-design.rst create mode 100644 Documentation/locking/percpu-rw-semaphore.rst create mode 100644 Documentation/locking/pi-futex.rst create mode 100644 Documentation/locking/preempt-locking.rst create mode 100644 Documentation/locking/robust-futex-ABI.rst create mode 100644 Documentation/locking/robust-futexes.rst create mode 100644 Documentation/locking/rt-mutex-design.rst create mode 100644 Documentation/locking/rt-mutex.rst create mode 100644 Documentation/locking/seqlock.rst create mode 100644 Documentation/locking/spinlocks.rst create mode 100644 Documentation/locking/ww-mutex-design.rst create mode 100644 Documentation/loongarch/booting.rst create mode 100644 Documentation/loongarch/features.rst create mode 100644 Documentation/loongarch/index.rst create mode 100644 Documentation/loongarch/introduction.rst create mode 100644 Documentation/loongarch/irq-chip-model.rst create mode 100644 Documentation/m68k/buddha-driver.rst create mode 100644 Documentation/m68k/features.rst create mode 100644 Documentation/m68k/index.rst create mode 100644 Documentation/m68k/kernel-options.rst create mode 100644 Documentation/maintainer/configure-git.rst create mode 100644 Documentation/maintainer/index.rst create mode 100644 Documentation/maintainer/maintainer-entry-profile.rst create mode 100644 Documentation/maintainer/messy-diffstat.rst create mode 100644 Documentation/maintainer/modifying-patches.rst create mode 100644 Documentation/maintainer/pull-requests.rst create mode 100644 Documentation/maintainer/rebasing-and-merging.rst create mode 100644 Documentation/memory-barriers.txt create mode 100644 Documentation/mhi/index.rst create mode 100644 Documentation/mhi/mhi.rst create mode 100644 Documentation/mhi/topology.rst create mode 100644 Documentation/mips/booting.rst create mode 100644 Documentation/mips/features.rst create mode 100644 Documentation/mips/index.rst create mode 100644 Documentation/mips/ingenic-tcu.rst create mode 100644 Documentation/misc-devices/ad525x_dpot.rst create mode 100644 Documentation/misc-devices/apds990x.rst create mode 100644 Documentation/misc-devices/bh1770glc.rst create mode 100644 Documentation/misc-devices/c2port.rst create mode 100644 Documentation/misc-devices/dw-xdata-pcie.rst create mode 100644 Documentation/misc-devices/eeprom.rst create mode 100644 Documentation/misc-devices/ibmvmc.rst create mode 100644 Documentation/misc-devices/ics932s401.rst create mode 100644 Documentation/misc-devices/index.rst create mode 100644 Documentation/misc-devices/isl29003.rst create mode 100644 Documentation/misc-devices/lis3lv02d.rst create mode 100644 Documentation/misc-devices/max6875.rst create mode 100644 Documentation/misc-devices/oxsemi-tornado.rst create mode 100644 Documentation/misc-devices/pci-endpoint-test.rst create mode 100644 Documentation/misc-devices/spear-pcie-gadget.rst create mode 100644 Documentation/misc-devices/uacce.rst create mode 100644 Documentation/misc-devices/xilinx_sdfec.rst create mode 100644 Documentation/mm/active_mm.rst create mode 100644 Documentation/mm/arch_pgtable_helpers.rst create mode 100644 Documentation/mm/balance.rst create mode 100644 Documentation/mm/bootmem.rst create mode 100644 Documentation/mm/damon/api.rst create mode 100644 Documentation/mm/damon/design.rst create mode 100644 Documentation/mm/damon/faq.rst create mode 100644 Documentation/mm/damon/index.rst create mode 100644 Documentation/mm/free_page_reporting.rst create mode 100644 Documentation/mm/frontswap.rst create mode 100644 Documentation/mm/highmem.rst create mode 100644 Documentation/mm/hmm.rst create mode 100644 Documentation/mm/hugetlbfs_reserv.rst create mode 100644 Documentation/mm/hwpoison.rst create mode 100644 Documentation/mm/index.rst create mode 100644 Documentation/mm/ksm.rst create mode 100644 Documentation/mm/memory-model.rst create mode 100644 Documentation/mm/mmu_notifier.rst create mode 100644 Documentation/mm/multigen_lru.rst create mode 100644 Documentation/mm/numa.rst create mode 100644 Documentation/mm/oom.rst create mode 100644 Documentation/mm/overcommit-accounting.rst create mode 100644 Documentation/mm/page_allocation.rst create mode 100644 Documentation/mm/page_cache.rst create mode 100644 Documentation/mm/page_frags.rst create mode 100644 Documentation/mm/page_migration.rst create mode 100644 Documentation/mm/page_owner.rst create mode 100644 Documentation/mm/page_reclaim.rst create mode 100644 Documentation/mm/page_table_check.rst create mode 100644 Documentation/mm/page_tables.rst create mode 100644 Documentation/mm/physical_memory.rst create mode 100644 Documentation/mm/process_addrs.rst create mode 100644 Documentation/mm/remap_file_pages.rst create mode 100644 Documentation/mm/shmfs.rst create mode 100644 Documentation/mm/slab.rst create mode 100644 Documentation/mm/slub.rst create mode 100644 Documentation/mm/split_page_table_lock.rst create mode 100644 Documentation/mm/swap.rst create mode 100644 Documentation/mm/transhuge.rst create mode 100644 Documentation/mm/unevictable-lru.rst create mode 100644 Documentation/mm/vmalloc.rst create mode 100644 Documentation/mm/vmalloced-kernel-stacks.rst create mode 100644 Documentation/mm/vmemmap_dedup.rst create mode 100644 Documentation/mm/z3fold.rst create mode 100644 Documentation/mm/zsmalloc.rst create mode 100644 Documentation/netlabel/cipso_ipv4.rst create mode 100644 Documentation/netlabel/draft_ietf.rst create mode 100644 Documentation/netlabel/index.rst create mode 100644 Documentation/netlabel/introduction.rst create mode 100644 Documentation/netlabel/lsm_interface.rst create mode 100644 Documentation/networking/6lowpan.rst create mode 100644 Documentation/networking/6pack.rst create mode 100644 Documentation/networking/af_xdp.rst create mode 100644 Documentation/networking/alias.rst create mode 100644 Documentation/networking/arcnet-hardware.rst create mode 100644 Documentation/networking/arcnet.rst create mode 100644 Documentation/networking/atm.rst create mode 100644 Documentation/networking/ax25.rst create mode 100644 Documentation/networking/bareudp.rst create mode 100644 Documentation/networking/batman-adv.rst create mode 100644 Documentation/networking/bonding.rst create mode 100644 Documentation/networking/bridge.rst create mode 100644 Documentation/networking/caif/caif.rst create mode 100644 Documentation/networking/caif/index.rst create mode 100644 Documentation/networking/caif/linux_caif.rst create mode 100644 Documentation/networking/can.rst create mode 100644 Documentation/networking/can_ucan_protocol.rst create mode 100644 Documentation/networking/cdc_mbim.rst create mode 100644 Documentation/networking/checksum-offloads.rst create mode 100644 Documentation/networking/dccp.rst create mode 100644 Documentation/networking/dctcp.rst create mode 100644 Documentation/networking/device_drivers/appletalk/cops.rst create mode 100644 Documentation/networking/device_drivers/appletalk/index.rst create mode 100644 Documentation/networking/device_drivers/atm/cxacru-cf.py create mode 100644 Documentation/networking/device_drivers/atm/cxacru.rst create mode 100644 Documentation/networking/device_drivers/atm/fore200e.rst create mode 100644 Documentation/networking/device_drivers/atm/index.rst create mode 100644 Documentation/networking/device_drivers/atm/iphase.rst create mode 100644 Documentation/networking/device_drivers/cable/index.rst create mode 100644 Documentation/networking/device_drivers/cable/sb1000.rst create mode 100644 Documentation/networking/device_drivers/can/can327.rst create mode 100644 Documentation/networking/device_drivers/can/ctu/ctucanfd-driver.rst create mode 100644 Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg create mode 100644 Documentation/networking/device_drivers/can/freescale/flexcan.rst create mode 100644 Documentation/networking/device_drivers/can/index.rst create mode 100644 Documentation/networking/device_drivers/cellular/index.rst create mode 100644 Documentation/networking/device_drivers/cellular/qualcomm/rmnet.rst create mode 100644 Documentation/networking/device_drivers/ethernet/3com/3c509.rst create mode 100644 Documentation/networking/device_drivers/ethernet/3com/vortex.rst create mode 100644 Documentation/networking/device_drivers/ethernet/altera/altera_tse.rst create mode 100644 Documentation/networking/device_drivers/ethernet/amazon/ena.rst create mode 100644 Documentation/networking/device_drivers/ethernet/aquantia/atlantic.rst create mode 100644 Documentation/networking/device_drivers/ethernet/chelsio/cxgb.rst create mode 100644 Documentation/networking/device_drivers/ethernet/cirrus/cs89x0.rst create mode 100644 Documentation/networking/device_drivers/ethernet/davicom/dm9000.rst create mode 100644 Documentation/networking/device_drivers/ethernet/dec/dmfe.rst create mode 100644 Documentation/networking/device_drivers/ethernet/dlink/dl2k.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/dpio-driver.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ethernet-driver.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/index.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/mac-phy-support.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/overview.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/dpaa2/switch-driver.rst create mode 100644 Documentation/networking/device_drivers/ethernet/freescale/gianfar.rst create mode 100644 Documentation/networking/device_drivers/ethernet/google/gve.rst create mode 100644 Documentation/networking/device_drivers/ethernet/huawei/hinic.rst create mode 100644 Documentation/networking/device_drivers/ethernet/index.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/e100.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/e1000.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/e1000e.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/fm10k.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/i40e.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/iavf.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/ice.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/igb.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/igbvf.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/ixgb.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst create mode 100644 Documentation/networking/device_drivers/ethernet/intel/ixgbevf.rst create mode 100644 Documentation/networking/device_drivers/ethernet/marvell/octeon_ep.rst create mode 100644 Documentation/networking/device_drivers/ethernet/marvell/octeontx2.rst create mode 100644 Documentation/networking/device_drivers/ethernet/mellanox/mlx5.rst create mode 100644 Documentation/networking/device_drivers/ethernet/microsoft/netvsc.rst create mode 100644 Documentation/networking/device_drivers/ethernet/neterion/s2io.rst create mode 100644 Documentation/networking/device_drivers/ethernet/netronome/nfp.rst create mode 100644 Documentation/networking/device_drivers/ethernet/pensando/ionic.rst create mode 100644 Documentation/networking/device_drivers/ethernet/smsc/smc9.rst create mode 100644 Documentation/networking/device_drivers/ethernet/stmicro/stmmac.rst create mode 100644 Documentation/networking/device_drivers/ethernet/ti/am65_nuss_cpsw_switchdev.rst create mode 100644 Documentation/networking/device_drivers/ethernet/ti/cpsw.rst create mode 100644 Documentation/networking/device_drivers/ethernet/ti/cpsw_switchdev.rst create mode 100644 Documentation/networking/device_drivers/ethernet/ti/tlan.rst create mode 100644 Documentation/networking/device_drivers/ethernet/toshiba/spider_net.rst create mode 100644 Documentation/networking/device_drivers/ethernet/wangxun/ngbe.rst create mode 100644 Documentation/networking/device_drivers/ethernet/wangxun/txgbe.rst create mode 100644 Documentation/networking/device_drivers/fddi/defza.rst create mode 100644 Documentation/networking/device_drivers/fddi/index.rst create mode 100644 Documentation/networking/device_drivers/fddi/skfp.rst create mode 100644 Documentation/networking/device_drivers/hamradio/baycom.rst create mode 100644 Documentation/networking/device_drivers/hamradio/index.rst create mode 100644 Documentation/networking/device_drivers/hamradio/z8530drv.rst create mode 100644 Documentation/networking/device_drivers/index.rst create mode 100644 Documentation/networking/device_drivers/qlogic/index.rst create mode 100644 Documentation/networking/device_drivers/qlogic/qlge.rst create mode 100644 Documentation/networking/device_drivers/wifi/index.rst create mode 100644 Documentation/networking/device_drivers/wifi/intel/ipw2100.rst create mode 100644 Documentation/networking/device_drivers/wifi/intel/ipw2200.rst create mode 100644 Documentation/networking/device_drivers/wifi/ray_cs.rst create mode 100644 Documentation/networking/device_drivers/wwan/index.rst create mode 100644 Documentation/networking/device_drivers/wwan/iosm.rst create mode 100644 Documentation/networking/device_drivers/wwan/t7xx.rst create mode 100644 Documentation/networking/devlink/am65-nuss-cpsw-switch.rst create mode 100644 Documentation/networking/devlink/bnxt.rst create mode 100644 Documentation/networking/devlink/devlink-dpipe.rst create mode 100644 Documentation/networking/devlink/devlink-flash.rst create mode 100644 Documentation/networking/devlink/devlink-health.rst create mode 100644 Documentation/networking/devlink/devlink-info.rst create mode 100644 Documentation/networking/devlink/devlink-linecard.rst create mode 100644 Documentation/networking/devlink/devlink-params.rst create mode 100644 Documentation/networking/devlink/devlink-port.rst create mode 100644 Documentation/networking/devlink/devlink-region.rst create mode 100644 Documentation/networking/devlink/devlink-reload.rst create mode 100644 Documentation/networking/devlink/devlink-resource.rst create mode 100644 Documentation/networking/devlink/devlink-selftests.rst create mode 100644 Documentation/networking/devlink/devlink-trap.rst create mode 100644 Documentation/networking/devlink/hns3.rst create mode 100644 Documentation/networking/devlink/ice.rst create mode 100644 Documentation/networking/devlink/index.rst create mode 100644 Documentation/networking/devlink/ionic.rst create mode 100644 Documentation/networking/devlink/iosm.rst create mode 100644 Documentation/networking/devlink/mlx4.rst create mode 100644 Documentation/networking/devlink/mlx5.rst create mode 100644 Documentation/networking/devlink/mlxsw.rst create mode 100644 Documentation/networking/devlink/mv88e6xxx.rst create mode 100644 Documentation/networking/devlink/netdevsim.rst create mode 100644 Documentation/networking/devlink/nfp.rst create mode 100644 Documentation/networking/devlink/octeontx2.rst create mode 100644 Documentation/networking/devlink/prestera.rst create mode 100644 Documentation/networking/devlink/qed.rst create mode 100644 Documentation/networking/devlink/ti-cpsw-switch.rst create mode 100644 Documentation/networking/dns_resolver.rst create mode 100644 Documentation/networking/driver.rst create mode 100644 Documentation/networking/dsa/b53.rst create mode 100644 Documentation/networking/dsa/bcm_sf2.rst create mode 100644 Documentation/networking/dsa/configuration.rst create mode 100644 Documentation/networking/dsa/dsa.rst create mode 100644 Documentation/networking/dsa/index.rst create mode 100644 Documentation/networking/dsa/lan9303.rst create mode 100644 Documentation/networking/dsa/sja1105.rst create mode 100644 Documentation/networking/eql.rst create mode 100644 Documentation/networking/ethtool-netlink.rst create mode 100644 Documentation/networking/failover.rst create mode 100644 Documentation/networking/fib_trie.rst create mode 100644 Documentation/networking/filter.rst create mode 100644 Documentation/networking/gen_stats.rst create mode 100644 Documentation/networking/generic-hdlc.rst create mode 100644 Documentation/networking/generic_netlink.rst create mode 100644 Documentation/networking/gtp.rst create mode 100644 Documentation/networking/ieee802154.rst create mode 100644 Documentation/networking/ila.rst create mode 100644 Documentation/networking/index.rst create mode 100644 Documentation/networking/ioam6-sysctl.rst create mode 100644 Documentation/networking/ip-sysctl.rst create mode 100644 Documentation/networking/ip_dynaddr.rst create mode 100644 Documentation/networking/ipddp.rst create mode 100644 Documentation/networking/ipsec.rst create mode 100644 Documentation/networking/ipv6.rst create mode 100644 Documentation/networking/ipvlan.rst create mode 100644 Documentation/networking/ipvs-sysctl.rst create mode 100644 Documentation/networking/j1939.rst create mode 100644 Documentation/networking/kapi.rst create mode 100644 Documentation/networking/kcm.rst create mode 100644 Documentation/networking/l2tp.rst create mode 100644 Documentation/networking/lapb-module.rst create mode 100644 Documentation/networking/mac80211-auth-assoc-deauth.txt create mode 100644 Documentation/networking/mac80211-injection.rst create mode 100644 Documentation/networking/mac80211_hwsim/hostapd.conf create mode 100644 Documentation/networking/mac80211_hwsim/mac80211_hwsim.rst create mode 100644 Documentation/networking/mac80211_hwsim/wpa_supplicant.conf create mode 100644 Documentation/networking/mctp.rst create mode 100644 Documentation/networking/mpls-sysctl.rst create mode 100644 Documentation/networking/mptcp-sysctl.rst create mode 100644 Documentation/networking/msg_zerocopy.rst create mode 100644 Documentation/networking/multiqueue.rst create mode 100644 Documentation/networking/net_dim.rst create mode 100644 Documentation/networking/net_failover.rst create mode 100644 Documentation/networking/netconsole.rst create mode 100644 Documentation/networking/netdev-features.rst create mode 100644 Documentation/networking/netdevices.rst create mode 100644 Documentation/networking/netfilter-sysctl.rst create mode 100644 Documentation/networking/netif-msg.rst create mode 100644 Documentation/networking/nexthop-group-resilient.rst create mode 100644 Documentation/networking/nf_conntrack-sysctl.rst create mode 100644 Documentation/networking/nf_flowtable.rst create mode 100644 Documentation/networking/nfc.rst create mode 100644 Documentation/networking/openvswitch.rst create mode 100644 Documentation/networking/operstates.rst create mode 100644 Documentation/networking/packet_mmap.rst create mode 100644 Documentation/networking/page_pool.rst create mode 100644 Documentation/networking/phonet.rst create mode 100644 Documentation/networking/phy.rst create mode 100644 Documentation/networking/pktgen.rst create mode 100644 Documentation/networking/plip.rst create mode 100644 Documentation/networking/ppp_generic.rst create mode 100644 Documentation/networking/proc_net_tcp.rst create mode 100644 Documentation/networking/radiotap-headers.rst create mode 100644 Documentation/networking/rds.rst create mode 100644 Documentation/networking/regulatory.rst create mode 100644 Documentation/networking/representors.rst create mode 100644 Documentation/networking/rxrpc.rst create mode 100644 Documentation/networking/scaling.rst create mode 100644 Documentation/networking/sctp.rst create mode 100644 Documentation/networking/secid.rst create mode 100644 Documentation/networking/seg6-sysctl.rst create mode 100644 Documentation/networking/segmentation-offloads.rst create mode 100644 Documentation/networking/sfp-phylink.rst create mode 100644 Documentation/networking/skbuff.rst create mode 100644 Documentation/networking/smc-sysctl.rst create mode 100644 Documentation/networking/snmp_counter.rst create mode 100644 Documentation/networking/statistics.rst create mode 100644 Documentation/networking/strparser.rst create mode 100644 Documentation/networking/switchdev.rst create mode 100644 Documentation/networking/sysfs-tagging.rst create mode 100644 Documentation/networking/tc-actions-env-rules.rst create mode 100644 Documentation/networking/tcp-thin.rst create mode 100644 Documentation/networking/team.rst create mode 100644 Documentation/networking/timestamping.rst create mode 100644 Documentation/networking/tipc.rst create mode 100644 Documentation/networking/tls-offload-layers.svg create mode 100644 Documentation/networking/tls-offload-reorder-bad.svg create mode 100644 Documentation/networking/tls-offload-reorder-good.svg create mode 100644 Documentation/networking/tls-offload.rst create mode 100644 Documentation/networking/tls.rst create mode 100644 Documentation/networking/tproxy.rst create mode 100644 Documentation/networking/tuntap.rst create mode 100644 Documentation/networking/udplite.rst create mode 100644 Documentation/networking/vrf.rst create mode 100644 Documentation/networking/vxlan.rst create mode 100644 Documentation/networking/x25-iface.rst create mode 100644 Documentation/networking/x25.rst create mode 100644 Documentation/networking/xfrm_device.rst create mode 100644 Documentation/networking/xfrm_proc.rst create mode 100644 Documentation/networking/xfrm_sync.rst create mode 100644 Documentation/networking/xfrm_sysctl.rst create mode 100644 Documentation/nios2/features.rst create mode 100644 Documentation/nios2/index.rst create mode 100644 Documentation/nios2/nios2.rst create mode 100644 Documentation/nvdimm/maintainer-entry-profile.rst create mode 100644 Documentation/openrisc/features.rst create mode 100644 Documentation/openrisc/index.rst create mode 100644 Documentation/openrisc/openrisc_port.rst create mode 100644 Documentation/openrisc/todo.rst create mode 100644 Documentation/parisc/debugging.rst create mode 100644 Documentation/parisc/features.rst create mode 100644 Documentation/parisc/index.rst create mode 100644 Documentation/parisc/registers.rst create mode 100644 Documentation/pcmcia/devicetable.rst create mode 100644 Documentation/pcmcia/driver-changes.rst create mode 100644 Documentation/pcmcia/driver.rst create mode 100644 Documentation/pcmcia/index.rst create mode 100644 Documentation/pcmcia/locking.rst create mode 100644 Documentation/peci/index.rst create mode 100644 Documentation/peci/peci.rst create mode 100644 Documentation/power/apm-acpi.rst create mode 100644 Documentation/power/basic-pm-debugging.rst create mode 100644 Documentation/power/charger-manager.rst create mode 100644 Documentation/power/drivers-testing.rst create mode 100644 Documentation/power/energy-model.rst create mode 100644 Documentation/power/freezing-of-tasks.rst create mode 100644 Documentation/power/index.rst create mode 100644 Documentation/power/opp.rst create mode 100644 Documentation/power/pci.rst create mode 100644 Documentation/power/pm_qos_interface.rst create mode 100644 Documentation/power/power_supply_class.rst create mode 100644 Documentation/power/powercap/dtpm.rst create mode 100644 Documentation/power/powercap/powercap.rst create mode 100644 Documentation/power/regulator/consumer.rst create mode 100644 Documentation/power/regulator/design.rst create mode 100644 Documentation/power/regulator/machine.rst create mode 100644 Documentation/power/regulator/overview.rst create mode 100644 Documentation/power/regulator/regulator.rst create mode 100644 Documentation/power/runtime_pm.rst create mode 100644 Documentation/power/s2ram.rst create mode 100644 Documentation/power/suspend-and-cpuhotplug.rst create mode 100644 Documentation/power/suspend-and-interrupts.rst create mode 100644 Documentation/power/swsusp-and-swap-files.rst create mode 100644 Documentation/power/swsusp-dmcrypt.rst create mode 100644 Documentation/power/swsusp.rst create mode 100644 Documentation/power/tricks.rst create mode 100644 Documentation/power/userland-swsusp.rst create mode 100644 Documentation/power/video.rst create mode 100644 Documentation/powerpc/associativity.rst create mode 100644 Documentation/powerpc/booting.rst create mode 100644 Documentation/powerpc/bootwrapper.rst create mode 100644 Documentation/powerpc/cpu_families.rst create mode 100644 Documentation/powerpc/cpu_features.rst create mode 100644 Documentation/powerpc/cxl.rst create mode 100644 Documentation/powerpc/cxlflash.rst create mode 100644 Documentation/powerpc/dawr-power9.rst create mode 100644 Documentation/powerpc/dscr.rst create mode 100644 Documentation/powerpc/eeh-pci-error-recovery.rst create mode 100644 Documentation/powerpc/elf_hwcaps.rst create mode 100644 Documentation/powerpc/elfnote.rst create mode 100644 Documentation/powerpc/features.rst create mode 100644 Documentation/powerpc/firmware-assisted-dump.rst create mode 100644 Documentation/powerpc/hvcs.rst create mode 100644 Documentation/powerpc/imc.rst create mode 100644 Documentation/powerpc/index.rst create mode 100644 Documentation/powerpc/isa-versions.rst create mode 100644 Documentation/powerpc/kasan.txt create mode 100644 Documentation/powerpc/kaslr-booke32.rst create mode 100644 Documentation/powerpc/mpc52xx.rst create mode 100644 Documentation/powerpc/papr_hcalls.rst create mode 100644 Documentation/powerpc/pci_iov_resource_on_powernv.rst create mode 100644 Documentation/powerpc/pmu-ebb.rst create mode 100644 Documentation/powerpc/ptrace.rst create mode 100644 Documentation/powerpc/qe_firmware.rst create mode 100644 Documentation/powerpc/syscall64-abi.rst create mode 100644 Documentation/powerpc/transactional_memory.rst create mode 100644 Documentation/powerpc/ultravisor.rst create mode 100644 Documentation/powerpc/vas-api.rst create mode 100644 Documentation/powerpc/vcpudispatch_stats.rst create mode 100644 Documentation/process/1.Intro.rst create mode 100644 Documentation/process/2.Process.rst create mode 100644 Documentation/process/3.Early-stage.rst create mode 100644 Documentation/process/4.Coding.rst create mode 100644 Documentation/process/5.Posting.rst create mode 100644 Documentation/process/6.Followthrough.rst create mode 100644 Documentation/process/7.AdvancedTopics.rst create mode 100644 Documentation/process/8.Conclusion.rst create mode 100644 Documentation/process/adding-syscalls.rst create mode 100644 Documentation/process/applying-patches.rst create mode 100644 Documentation/process/botching-up-ioctls.rst create mode 100644 Documentation/process/changes.rst create mode 100644 Documentation/process/clang-format.rst create mode 100644 Documentation/process/code-of-conduct-interpretation.rst create mode 100644 Documentation/process/code-of-conduct.rst create mode 100644 Documentation/process/coding-style.rst create mode 100644 Documentation/process/deprecated.rst create mode 100644 Documentation/process/development-process.rst create mode 100644 Documentation/process/email-clients.rst create mode 100644 Documentation/process/embargoed-hardware-issues.rst create mode 100644 Documentation/process/handling-regressions.rst create mode 100644 Documentation/process/howto.rst create mode 100644 Documentation/process/index.rst create mode 100644 Documentation/process/kernel-docs.rst create mode 100644 Documentation/process/kernel-driver-statement.rst create mode 100644 Documentation/process/kernel-enforcement-statement.rst create mode 100644 Documentation/process/license-rules.rst create mode 100644 Documentation/process/magic-number.rst create mode 100644 Documentation/process/maintainer-handbooks.rst create mode 100644 Documentation/process/maintainer-netdev.rst create mode 100644 Documentation/process/maintainer-pgp-guide.rst create mode 100644 Documentation/process/maintainer-tip.rst create mode 100644 Documentation/process/maintainers.rst create mode 100644 Documentation/process/management-style.rst create mode 100644 Documentation/process/programming-language.rst create mode 100644 Documentation/process/researcher-guidelines.rst create mode 100644 Documentation/process/stable-api-nonsense.rst create mode 100644 Documentation/process/stable-kernel-rules.rst create mode 100644 Documentation/process/submit-checklist.rst create mode 100644 Documentation/process/submitting-patches.rst create mode 100644 Documentation/process/volatile-considered-harmful.rst create mode 100644 Documentation/riscv/boot-image-header.rst create mode 100644 Documentation/riscv/features.rst create mode 100644 Documentation/riscv/index.rst create mode 100644 Documentation/riscv/patch-acceptance.rst create mode 100644 Documentation/riscv/uabi.rst create mode 100644 Documentation/riscv/vm-layout.rst create mode 100644 Documentation/rust/arch-support.rst create mode 100644 Documentation/rust/coding-guidelines.rst create mode 100644 Documentation/rust/general-information.rst create mode 100644 Documentation/rust/index.rst create mode 100644 Documentation/rust/quick-start.rst create mode 100644 Documentation/s390/3270.ChangeLog create mode 100644 Documentation/s390/3270.rst create mode 100644 Documentation/s390/cds.rst create mode 100644 Documentation/s390/common_io.rst create mode 100644 Documentation/s390/config3270.sh create mode 100644 Documentation/s390/driver-model.rst create mode 100644 Documentation/s390/features.rst create mode 100644 Documentation/s390/index.rst create mode 100644 Documentation/s390/monreader.rst create mode 100644 Documentation/s390/pci.rst create mode 100644 Documentation/s390/qeth.rst create mode 100644 Documentation/s390/s390dbf.rst create mode 100644 Documentation/s390/text_files.rst create mode 100644 Documentation/s390/vfio-ap-locking.rst create mode 100644 Documentation/s390/vfio-ap.rst create mode 100644 Documentation/s390/vfio-ccw.rst create mode 100644 Documentation/s390/zfcpdump.rst create mode 100644 Documentation/scheduler/completion.rst create mode 100644 Documentation/scheduler/index.rst create mode 100644 Documentation/scheduler/sched-arch.rst create mode 100644 Documentation/scheduler/sched-bwc.rst create mode 100644 Documentation/scheduler/sched-capacity.rst create mode 100644 Documentation/scheduler/sched-deadline.rst create mode 100644 Documentation/scheduler/sched-debug.rst create mode 100644 Documentation/scheduler/sched-design-CFS.rst create mode 100644 Documentation/scheduler/sched-domains.rst create mode 100644 Documentation/scheduler/sched-energy.rst create mode 100644 Documentation/scheduler/sched-nice-design.rst create mode 100644 Documentation/scheduler/sched-pelt.c create mode 100644 Documentation/scheduler/sched-rt-group.rst create mode 100644 Documentation/scheduler/sched-stats.rst create mode 100644 Documentation/scheduler/schedutil.rst create mode 100644 Documentation/scheduler/text_files.rst create mode 100644 Documentation/scsi/53c700.rst create mode 100644 Documentation/scsi/BusLogic.rst create mode 100644 Documentation/scsi/ChangeLog.arcmsr create mode 100644 Documentation/scsi/ChangeLog.ips create mode 100644 Documentation/scsi/ChangeLog.lpfc create mode 100644 Documentation/scsi/ChangeLog.megaraid create mode 100644 Documentation/scsi/ChangeLog.megaraid_sas create mode 100644 Documentation/scsi/ChangeLog.ncr53c8xx create mode 100644 Documentation/scsi/ChangeLog.sym53c8xx create mode 100644 Documentation/scsi/ChangeLog.sym53c8xx_2 create mode 100644 Documentation/scsi/FlashPoint.rst create mode 100644 Documentation/scsi/LICENSE.FlashPoint create mode 100644 Documentation/scsi/NinjaSCSI.rst create mode 100644 Documentation/scsi/aacraid.rst create mode 100644 Documentation/scsi/advansys.rst create mode 100644 Documentation/scsi/aha152x.rst create mode 100644 Documentation/scsi/aic79xx.rst create mode 100644 Documentation/scsi/aic7xxx.rst create mode 100644 Documentation/scsi/arcmsr_spec.rst create mode 100644 Documentation/scsi/bfa.rst create mode 100644 Documentation/scsi/bnx2fc.rst create mode 100644 Documentation/scsi/cxgb3i.rst create mode 100644 Documentation/scsi/dc395x.rst create mode 100644 Documentation/scsi/dpti.rst create mode 100644 Documentation/scsi/g_NCR5380.rst create mode 100644 Documentation/scsi/hpsa.rst create mode 100644 Documentation/scsi/hptiop.rst create mode 100644 Documentation/scsi/index.rst create mode 100644 Documentation/scsi/libsas.rst create mode 100644 Documentation/scsi/link_power_management_policy.rst create mode 100644 Documentation/scsi/lpfc.rst create mode 100644 Documentation/scsi/megaraid.rst create mode 100644 Documentation/scsi/ncr53c8xx.rst create mode 100644 Documentation/scsi/ppa.rst create mode 100644 Documentation/scsi/qlogicfas.rst create mode 100644 Documentation/scsi/scsi-changer.rst create mode 100644 Documentation/scsi/scsi-generic.rst create mode 100644 Documentation/scsi/scsi-parameters.rst create mode 100644 Documentation/scsi/scsi.rst create mode 100644 Documentation/scsi/scsi_eh.rst create mode 100644 Documentation/scsi/scsi_fc_transport.rst create mode 100644 Documentation/scsi/scsi_mid_low_api.rst create mode 100644 Documentation/scsi/scsi_transport_srp/figures.rst create mode 100644 Documentation/scsi/scsi_transport_srp/rport_state_diagram.dot create mode 100644 Documentation/scsi/sd-parameters.rst create mode 100644 Documentation/scsi/smartpqi.rst create mode 100644 Documentation/scsi/st.rst create mode 100644 Documentation/scsi/sym53c500_cs.rst create mode 100644 Documentation/scsi/sym53c8xx_2.rst create mode 100644 Documentation/scsi/tcm_qla2xxx.rst create mode 100644 Documentation/scsi/ufs.rst create mode 100644 Documentation/scsi/wd719x.rst create mode 100644 Documentation/security/IMA-templates.rst create mode 100644 Documentation/security/SCTP.rst create mode 100644 Documentation/security/credentials.rst create mode 100644 Documentation/security/digsig.rst create mode 100644 Documentation/security/index.rst create mode 100644 Documentation/security/keys/core.rst create mode 100644 Documentation/security/keys/ecryptfs.rst create mode 100644 Documentation/security/keys/index.rst create mode 100644 Documentation/security/keys/request-key.rst create mode 100644 Documentation/security/keys/trusted-encrypted.rst create mode 100644 Documentation/security/landlock.rst create mode 100644 Documentation/security/lsm-development.rst create mode 100644 Documentation/security/lsm.rst create mode 100644 Documentation/security/sak.rst create mode 100644 Documentation/security/secrets/coco.rst create mode 100644 Documentation/security/secrets/index.rst create mode 100644 Documentation/security/self-protection.rst create mode 100644 Documentation/security/siphash.rst create mode 100644 Documentation/security/tpm/index.rst create mode 100644 Documentation/security/tpm/tpm_event_log.rst create mode 100644 Documentation/security/tpm/tpm_ftpm_tee.rst create mode 100644 Documentation/security/tpm/tpm_vtpm_proxy.rst create mode 100644 Documentation/security/tpm/xen-tpmfront.rst create mode 100644 Documentation/sh/booting.rst create mode 100644 Documentation/sh/features.rst create mode 100644 Documentation/sh/index.rst create mode 100644 Documentation/sh/new-machine.rst create mode 100644 Documentation/sh/register-banks.rst create mode 100644 Documentation/sound/alsa-configuration.rst create mode 100644 Documentation/sound/cards/audigy-mixer.rst create mode 100644 Documentation/sound/cards/audiophile-usb.rst create mode 100644 Documentation/sound/cards/bt87x.rst create mode 100644 Documentation/sound/cards/cmipci.rst create mode 100644 Documentation/sound/cards/emu10k1-jack.rst create mode 100644 Documentation/sound/cards/hdspm.rst create mode 100644 Documentation/sound/cards/img-spdif-in.rst create mode 100644 Documentation/sound/cards/index.rst create mode 100644 Documentation/sound/cards/joystick.rst create mode 100644 Documentation/sound/cards/maya44.rst create mode 100644 Documentation/sound/cards/mixart.rst create mode 100755 Documentation/sound/cards/multisound.sh create mode 100644 Documentation/sound/cards/sb-live-mixer.rst create mode 100644 Documentation/sound/cards/serial-u16550.rst create mode 100644 Documentation/sound/cards/via82xx-mixer.rst create mode 100644 Documentation/sound/designs/channel-mapping-api.rst create mode 100644 Documentation/sound/designs/compress-offload.rst create mode 100644 Documentation/sound/designs/control-names.rst create mode 100644 Documentation/sound/designs/index.rst create mode 100644 Documentation/sound/designs/jack-controls.rst create mode 100644 Documentation/sound/designs/jack-injection.rst create mode 100644 Documentation/sound/designs/oss-emulation.rst create mode 100644 Documentation/sound/designs/powersave.rst create mode 100644 Documentation/sound/designs/procfile.rst create mode 100644 Documentation/sound/designs/seq-oss.rst create mode 100644 Documentation/sound/designs/timestamping.rst create mode 100644 Documentation/sound/designs/tracepoints.rst create mode 100644 Documentation/sound/hd-audio/controls.rst create mode 100644 Documentation/sound/hd-audio/dp-mst.rst create mode 100644 Documentation/sound/hd-audio/index.rst create mode 100644 Documentation/sound/hd-audio/models.rst create mode 100644 Documentation/sound/hd-audio/notes.rst create mode 100644 Documentation/sound/hd-audio/realtek-pc-beep.rst create mode 100644 Documentation/sound/index.rst create mode 100644 Documentation/sound/kernel-api/alsa-driver-api.rst create mode 100644 Documentation/sound/kernel-api/index.rst create mode 100644 Documentation/sound/kernel-api/writing-an-alsa-driver.rst create mode 100644 Documentation/sound/soc/clocking.rst create mode 100644 Documentation/sound/soc/codec-to-codec.rst create mode 100644 Documentation/sound/soc/codec.rst create mode 100644 Documentation/sound/soc/dai.rst create mode 100644 Documentation/sound/soc/dapm.rst create mode 100644 Documentation/sound/soc/dpcm.rst create mode 100644 Documentation/sound/soc/index.rst create mode 100644 Documentation/sound/soc/jack.rst create mode 100644 Documentation/sound/soc/machine.rst create mode 100644 Documentation/sound/soc/overview.rst create mode 100644 Documentation/sound/soc/platform.rst create mode 100644 Documentation/sound/soc/pops-clicks.rst create mode 100644 Documentation/sparc/adi.rst create mode 100644 Documentation/sparc/console.rst create mode 100644 Documentation/sparc/features.rst create mode 100644 Documentation/sparc/index.rst create mode 100644 Documentation/sparc/oradax/dax-hv-api.txt create mode 100644 Documentation/sparc/oradax/oracle-dax.rst create mode 100644 Documentation/sphinx-static/theme_overrides.css create mode 100644 Documentation/sphinx-static/theme_rtd_colors.css create mode 100644 Documentation/sphinx/automarkup.py create mode 100644 Documentation/sphinx/cdomain.py create mode 100644 Documentation/sphinx/kernel_abi.py create mode 100644 Documentation/sphinx/kernel_feat.py create mode 100755 Documentation/sphinx/kernel_include.py create mode 100644 Documentation/sphinx/kerneldoc-preamble.sty create mode 100644 Documentation/sphinx/kerneldoc.py create mode 100644 Documentation/sphinx/kernellog.py create mode 100644 Documentation/sphinx/kfigure.py create mode 100644 Documentation/sphinx/load_config.py create mode 100755 Documentation/sphinx/maintainers_include.py create mode 100644 Documentation/sphinx/parallel-wrapper.sh create mode 100755 Documentation/sphinx/parse-headers.pl create mode 100644 Documentation/sphinx/requirements.txt create mode 100755 Documentation/sphinx/rstFlatTable.py create mode 100644 Documentation/spi/butterfly.rst create mode 100644 Documentation/spi/index.rst create mode 100644 Documentation/spi/pxa2xx.rst create mode 100644 Documentation/spi/spi-lm70llp.rst create mode 100644 Documentation/spi/spi-sc18is602.rst create mode 100644 Documentation/spi/spi-summary.rst create mode 100644 Documentation/spi/spidev.rst create mode 100644 Documentation/staging/crc32.rst create mode 100644 Documentation/staging/index.rst create mode 100644 Documentation/staging/lzo.rst create mode 100644 Documentation/staging/remoteproc.rst create mode 100644 Documentation/staging/rpmsg.rst create mode 100644 Documentation/staging/speculation.rst create mode 100644 Documentation/staging/static-keys.rst create mode 100644 Documentation/staging/tee.rst create mode 100644 Documentation/staging/xz.rst create mode 100644 Documentation/subsystem-apis.rst create mode 100644 Documentation/target/index.rst create mode 100644 Documentation/target/scripts.rst create mode 100755 Documentation/target/target-export-device create mode 100755 Documentation/target/tcm_mod_builder.py create mode 100644 Documentation/target/tcm_mod_builder.rst create mode 100644 Documentation/target/tcmu-design.rst create mode 100644 Documentation/timers/highres.rst create mode 100644 Documentation/timers/hpet.rst create mode 100644 Documentation/timers/hrtimers.rst create mode 100644 Documentation/timers/index.rst create mode 100644 Documentation/timers/no_hz.rst create mode 100644 Documentation/timers/timekeeping.rst create mode 100644 Documentation/timers/timers-howto.rst create mode 100644 Documentation/tools/index.rst create mode 100644 Documentation/tools/rtla/Makefile create mode 100644 Documentation/tools/rtla/common_appendix.rst create mode 100644 Documentation/tools/rtla/common_hist_options.rst create mode 100644 Documentation/tools/rtla/common_options.rst create mode 100644 Documentation/tools/rtla/common_osnoise_description.rst create mode 100644 Documentation/tools/rtla/common_osnoise_options.rst create mode 100644 Documentation/tools/rtla/common_timerlat_description.rst create mode 100644 Documentation/tools/rtla/common_timerlat_options.rst create mode 100644 Documentation/tools/rtla/common_top_options.rst create mode 100644 Documentation/tools/rtla/index.rst create mode 100644 Documentation/tools/rtla/rtla-osnoise-hist.rst create mode 100644 Documentation/tools/rtla/rtla-osnoise-top.rst create mode 100644 Documentation/tools/rtla/rtla-osnoise.rst create mode 100644 Documentation/tools/rtla/rtla-timerlat-hist.rst create mode 100644 Documentation/tools/rtla/rtla-timerlat-top.rst create mode 100644 Documentation/tools/rtla/rtla-timerlat.rst create mode 100644 Documentation/tools/rtla/rtla.rst create mode 100644 Documentation/trace/boottime-trace.rst create mode 100644 Documentation/trace/coresight/coresight-config.rst create mode 100644 Documentation/trace/coresight/coresight-cpu-debug.rst create mode 100644 Documentation/trace/coresight/coresight-ect.rst create mode 100644 Documentation/trace/coresight/coresight-etm4x-reference.rst create mode 100644 Documentation/trace/coresight/coresight-perf.rst create mode 100644 Documentation/trace/coresight/coresight-trbe.rst create mode 100644 Documentation/trace/coresight/coresight.rst create mode 100644 Documentation/trace/coresight/index.rst create mode 100644 Documentation/trace/events-kmem.rst create mode 100644 Documentation/trace/events-msr.rst create mode 100644 Documentation/trace/events-nmi.rst create mode 100644 Documentation/trace/events-power.rst create mode 100644 Documentation/trace/events.rst create mode 100644 Documentation/trace/fprobe.rst create mode 100644 Documentation/trace/ftrace-design.rst create mode 100644 Documentation/trace/ftrace-uses.rst create mode 100644 Documentation/trace/ftrace.rst create mode 100644 Documentation/trace/function-graph-fold.vim create mode 100644 Documentation/trace/hisi-ptt.rst create mode 100644 Documentation/trace/histogram-design.rst create mode 100644 Documentation/trace/histogram.rst create mode 100644 Documentation/trace/hwlat_detector.rst create mode 100644 Documentation/trace/index.rst create mode 100644 Documentation/trace/intel_th.rst create mode 100644 Documentation/trace/kprobes.rst create mode 100644 Documentation/trace/kprobetrace.rst create mode 100644 Documentation/trace/mmiotrace.rst create mode 100644 Documentation/trace/osnoise-tracer.rst create mode 100644 Documentation/trace/postprocess/decode_msr.py create mode 100644 Documentation/trace/postprocess/trace-pagealloc-postprocess.pl create mode 100644 Documentation/trace/postprocess/trace-vmscan-postprocess.pl create mode 100644 Documentation/trace/ring-buffer-design.rst create mode 100644 Documentation/trace/rv/da_monitor_instrumentation.rst create mode 100644 Documentation/trace/rv/da_monitor_synthesis.rst create mode 100644 Documentation/trace/rv/deterministic_automata.rst create mode 100644 Documentation/trace/rv/index.rst create mode 100644 Documentation/trace/rv/monitor_wip.rst create mode 100644 Documentation/trace/rv/monitor_wwnr.rst create mode 100644 Documentation/trace/rv/runtime-verification.rst create mode 100644 Documentation/trace/stm.rst create mode 100644 Documentation/trace/sys-t.rst create mode 100644 Documentation/trace/timerlat-tracer.rst create mode 100644 Documentation/trace/tracepoint-analysis.rst create mode 100644 Documentation/trace/tracepoints.rst create mode 100644 Documentation/trace/uprobetracer.rst create mode 100644 Documentation/trace/user_events.rst create mode 100644 Documentation/translations/index.rst create mode 100644 Documentation/translations/it_IT/admin-guide/README.rst create mode 100644 Documentation/translations/it_IT/admin-guide/kernel-parameters.rst create mode 100644 Documentation/translations/it_IT/admin-guide/security-bugs.rst create mode 100644 Documentation/translations/it_IT/core-api/index.rst create mode 100644 Documentation/translations/it_IT/core-api/memory-allocation.rst create mode 100644 Documentation/translations/it_IT/core-api/symbol-namespaces.rst create mode 100644 Documentation/translations/it_IT/devicetree/bindings/submitting-patches.rst create mode 100644 Documentation/translations/it_IT/disclaimer-ita.rst create mode 100644 Documentation/translations/it_IT/doc-guide/index.rst create mode 100644 Documentation/translations/it_IT/doc-guide/kernel-doc.rst create mode 100644 Documentation/translations/it_IT/doc-guide/parse-headers.rst create mode 100644 Documentation/translations/it_IT/doc-guide/sphinx.rst create mode 100644 Documentation/translations/it_IT/index.rst create mode 100644 Documentation/translations/it_IT/kernel-hacking/hacking.rst create mode 100644 Documentation/translations/it_IT/kernel-hacking/index.rst create mode 100644 Documentation/translations/it_IT/kernel-hacking/locking.rst create mode 100644 Documentation/translations/it_IT/maintainer/configure-git.rst create mode 100644 Documentation/translations/it_IT/networking/netdev-FAQ.rst create mode 100644 Documentation/translations/it_IT/process/1.Intro.rst create mode 100644 Documentation/translations/it_IT/process/2.Process.rst create mode 100644 Documentation/translations/it_IT/process/3.Early-stage.rst create mode 100644 Documentation/translations/it_IT/process/4.Coding.rst create mode 100644 Documentation/translations/it_IT/process/5.Posting.rst create mode 100644 Documentation/translations/it_IT/process/6.Followthrough.rst create mode 100644 Documentation/translations/it_IT/process/7.AdvancedTopics.rst create mode 100644 Documentation/translations/it_IT/process/8.Conclusion.rst create mode 100644 Documentation/translations/it_IT/process/adding-syscalls.rst create mode 100644 Documentation/translations/it_IT/process/applying-patches.rst create mode 100644 Documentation/translations/it_IT/process/changes.rst create mode 100644 Documentation/translations/it_IT/process/clang-format.rst create mode 100644 Documentation/translations/it_IT/process/code-of-conduct.rst create mode 100644 Documentation/translations/it_IT/process/coding-style.rst create mode 100644 Documentation/translations/it_IT/process/deprecated.rst create mode 100644 Documentation/translations/it_IT/process/development-process.rst create mode 100644 Documentation/translations/it_IT/process/email-clients.rst create mode 100644 Documentation/translations/it_IT/process/howto.rst create mode 100644 Documentation/translations/it_IT/process/index.rst create mode 100644 Documentation/translations/it_IT/process/kernel-docs.rst create mode 100644 Documentation/translations/it_IT/process/kernel-driver-statement.rst create mode 100644 Documentation/translations/it_IT/process/kernel-enforcement-statement.rst create mode 100644 Documentation/translations/it_IT/process/license-rules.rst create mode 100644 Documentation/translations/it_IT/process/magic-number.rst create mode 100644 Documentation/translations/it_IT/process/maintainer-handbooks.rst create mode 100644 Documentation/translations/it_IT/process/maintainer-pgp-guide.rst create mode 100644 Documentation/translations/it_IT/process/maintainer-tip.rst create mode 100644 Documentation/translations/it_IT/process/maintainers.rst create mode 100644 Documentation/translations/it_IT/process/management-style.rst create mode 100644 Documentation/translations/it_IT/process/programming-language.rst create mode 100644 Documentation/translations/it_IT/process/stable-api-nonsense.rst create mode 100644 Documentation/translations/it_IT/process/stable-kernel-rules.rst create mode 100644 Documentation/translations/it_IT/process/submit-checklist.rst create mode 100644 Documentation/translations/it_IT/process/submitting-patches.rst create mode 100644 Documentation/translations/it_IT/process/volatile-considered-harmful.rst create mode 100644 Documentation/translations/it_IT/riscv/patch-acceptance.rst create mode 100644 Documentation/translations/ja_JP/SubmitChecklist create mode 100644 Documentation/translations/ja_JP/SubmittingPatches create mode 100644 Documentation/translations/ja_JP/howto.rst create mode 100644 Documentation/translations/ja_JP/index.rst create mode 100644 Documentation/translations/ja_JP/stable_api_nonsense.txt create mode 100644 Documentation/translations/ja_JP/stable_kernel_rules.txt create mode 100644 Documentation/translations/ko_KR/howto.rst create mode 100644 Documentation/translations/ko_KR/index.rst create mode 100644 Documentation/translations/ko_KR/memory-barriers.txt create mode 100644 Documentation/translations/ko_KR/stable_api_nonsense.txt create mode 100644 Documentation/translations/zh_CN/PCI/acpi-info.rst create mode 100644 Documentation/translations/zh_CN/PCI/index.rst create mode 100644 Documentation/translations/zh_CN/PCI/msi-howto.rst create mode 100644 Documentation/translations/zh_CN/PCI/pci-iov-howto.rst create mode 100644 Documentation/translations/zh_CN/PCI/pci.rst create mode 100644 Documentation/translations/zh_CN/PCI/pciebus-howto.rst create mode 100644 Documentation/translations/zh_CN/PCI/sysfs-pci.rst create mode 100644 Documentation/translations/zh_CN/accounting/delay-accounting.rst create mode 100644 Documentation/translations/zh_CN/accounting/index.rst create mode 100644 Documentation/translations/zh_CN/accounting/psi.rst create mode 100644 Documentation/translations/zh_CN/accounting/taskstats.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/README.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/bootconfig.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/bug-bisect.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/bug-hunting.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/clearing-warn-once.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/cpu-load.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/cputopology.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/index.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/init.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/lockup-watchdogs.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/damon/index.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/damon/reclaim.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/damon/start.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/damon/usage.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/index.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/ksm.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/reporting-regressions.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/security-bugs.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/sysrq.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/tainted-kernels.rst create mode 100644 Documentation/translations/zh_CN/admin-guide/unicode.rst create mode 100644 Documentation/translations/zh_CN/arch.rst create mode 100644 Documentation/translations/zh_CN/arm/Booting create mode 100644 Documentation/translations/zh_CN/arm/kernel_user_helpers.txt create mode 100644 Documentation/translations/zh_CN/arm64/amu.rst create mode 100644 Documentation/translations/zh_CN/arm64/booting.txt create mode 100644 Documentation/translations/zh_CN/arm64/elf_hwcaps.rst create mode 100644 Documentation/translations/zh_CN/arm64/hugetlbpage.rst create mode 100644 Documentation/translations/zh_CN/arm64/index.rst create mode 100644 Documentation/translations/zh_CN/arm64/legacy_instructions.txt create mode 100644 Documentation/translations/zh_CN/arm64/memory.txt create mode 100644 Documentation/translations/zh_CN/arm64/perf.rst create mode 100644 Documentation/translations/zh_CN/arm64/silicon-errata.txt create mode 100644 Documentation/translations/zh_CN/arm64/tagged-pointers.txt create mode 100644 Documentation/translations/zh_CN/core-api/assoc_array.rst create mode 100644 Documentation/translations/zh_CN/core-api/boot-time-mm.rst create mode 100644 Documentation/translations/zh_CN/core-api/cachetlb.rst create mode 100644 Documentation/translations/zh_CN/core-api/circular-buffers.rst create mode 100644 Documentation/translations/zh_CN/core-api/cpu_hotplug.rst create mode 100644 Documentation/translations/zh_CN/core-api/genalloc.rst create mode 100644 Documentation/translations/zh_CN/core-api/generic-radix-tree.rst create mode 100644 Documentation/translations/zh_CN/core-api/genericirq.rst create mode 100644 Documentation/translations/zh_CN/core-api/gfp_mask-from-fs-io.rst create mode 100644 Documentation/translations/zh_CN/core-api/idr.rst create mode 100644 Documentation/translations/zh_CN/core-api/index.rst create mode 100644 Documentation/translations/zh_CN/core-api/irq/concepts.rst create mode 100644 Documentation/translations/zh_CN/core-api/irq/index.rst create mode 100644 Documentation/translations/zh_CN/core-api/irq/irq-affinity.rst create mode 100644 Documentation/translations/zh_CN/core-api/irq/irq-domain.rst create mode 100644 Documentation/translations/zh_CN/core-api/irq/irqflags-tracing.rst create mode 100644 Documentation/translations/zh_CN/core-api/kernel-api.rst create mode 100644 Documentation/translations/zh_CN/core-api/kobject.rst create mode 100644 Documentation/translations/zh_CN/core-api/kref.rst create mode 100644 Documentation/translations/zh_CN/core-api/local_ops.rst create mode 100644 Documentation/translations/zh_CN/core-api/memory-allocation.rst create mode 100644 Documentation/translations/zh_CN/core-api/memory-hotplug.rst create mode 100644 Documentation/translations/zh_CN/core-api/mm-api.rst create mode 100644 Documentation/translations/zh_CN/core-api/packing.rst create mode 100644 Documentation/translations/zh_CN/core-api/padata.rst create mode 100644 Documentation/translations/zh_CN/core-api/printk-basics.rst create mode 100644 Documentation/translations/zh_CN/core-api/printk-formats.rst create mode 100644 Documentation/translations/zh_CN/core-api/protection-keys.rst create mode 100644 Documentation/translations/zh_CN/core-api/rbtree.rst create mode 100644 Documentation/translations/zh_CN/core-api/refcount-vs-atomic.rst create mode 100644 Documentation/translations/zh_CN/core-api/symbol-namespaces.rst create mode 100644 Documentation/translations/zh_CN/core-api/unaligned-memory-access.rst create mode 100644 Documentation/translations/zh_CN/core-api/watch_queue.rst create mode 100644 Documentation/translations/zh_CN/core-api/workqueue.rst create mode 100644 Documentation/translations/zh_CN/core-api/xarray.rst create mode 100644 Documentation/translations/zh_CN/cpu-freq/core.rst create mode 100644 Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst create mode 100644 Documentation/translations/zh_CN/cpu-freq/cpufreq-stats.rst create mode 100644 Documentation/translations/zh_CN/cpu-freq/index.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/gcov.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/gdb-kernel-debugging.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/index.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/kasan.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/sparse.rst create mode 100644 Documentation/translations/zh_CN/dev-tools/testing-overview.rst create mode 100644 Documentation/translations/zh_CN/devicetree/changesets.rst create mode 100644 Documentation/translations/zh_CN/devicetree/dynamic-resolution-notes.rst create mode 100644 Documentation/translations/zh_CN/devicetree/index.rst create mode 100644 Documentation/translations/zh_CN/devicetree/kernel-api.rst create mode 100644 Documentation/translations/zh_CN/devicetree/of_unittest.rst create mode 100644 Documentation/translations/zh_CN/devicetree/overlay-notes.rst create mode 100644 Documentation/translations/zh_CN/devicetree/usage-model.rst create mode 100644 Documentation/translations/zh_CN/disclaimer-zh_CN.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/contributing.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/index.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/kernel-doc.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/maintainer-profile.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/parse-headers.rst create mode 100644 Documentation/translations/zh_CN/doc-guide/sphinx.rst create mode 100644 Documentation/translations/zh_CN/driver-api/gpio/index.rst create mode 100644 Documentation/translations/zh_CN/driver-api/gpio/legacy.rst create mode 100644 Documentation/translations/zh_CN/driver-api/index.rst create mode 100644 Documentation/translations/zh_CN/driver-api/io_ordering.rst create mode 100644 Documentation/translations/zh_CN/filesystems/debugfs.rst create mode 100644 Documentation/translations/zh_CN/filesystems/index.rst create mode 100644 Documentation/translations/zh_CN/filesystems/sysfs.txt create mode 100644 Documentation/translations/zh_CN/filesystems/tmpfs.rst create mode 100644 Documentation/translations/zh_CN/filesystems/virtiofs.rst create mode 100644 Documentation/translations/zh_CN/iio/ep93xx_adc.rst create mode 100644 Documentation/translations/zh_CN/iio/iio_configfs.rst create mode 100644 Documentation/translations/zh_CN/iio/index.rst create mode 100644 Documentation/translations/zh_CN/index.rst create mode 100644 Documentation/translations/zh_CN/infiniband/core_locking.rst create mode 100644 Documentation/translations/zh_CN/infiniband/index.rst create mode 100644 Documentation/translations/zh_CN/infiniband/ipoib.rst create mode 100644 Documentation/translations/zh_CN/infiniband/opa_vnic.rst create mode 100644 Documentation/translations/zh_CN/infiniband/sysfs.rst create mode 100644 Documentation/translations/zh_CN/infiniband/tag_matching.rst create mode 100644 Documentation/translations/zh_CN/infiniband/user_mad.rst create mode 100644 Documentation/translations/zh_CN/infiniband/user_verbs.rst create mode 100644 Documentation/translations/zh_CN/kernel-hacking/hacking.rst create mode 100644 Documentation/translations/zh_CN/kernel-hacking/index.rst create mode 100644 Documentation/translations/zh_CN/locking/index.rst create mode 100644 Documentation/translations/zh_CN/locking/mutex-design.rst create mode 100644 Documentation/translations/zh_CN/locking/spinlocks.rst create mode 100644 Documentation/translations/zh_CN/loongarch/booting.rst create mode 100644 Documentation/translations/zh_CN/loongarch/features.rst create mode 100644 Documentation/translations/zh_CN/loongarch/index.rst create mode 100644 Documentation/translations/zh_CN/loongarch/introduction.rst create mode 100644 Documentation/translations/zh_CN/loongarch/irq-chip-model.rst create mode 100644 Documentation/translations/zh_CN/maintainer/configure-git.rst create mode 100644 Documentation/translations/zh_CN/maintainer/index.rst create mode 100644 Documentation/translations/zh_CN/maintainer/maintainer-entry-profile.rst create mode 100644 Documentation/translations/zh_CN/maintainer/modifying-patches.rst create mode 100644 Documentation/translations/zh_CN/maintainer/pull-requests.rst create mode 100644 Documentation/translations/zh_CN/maintainer/rebasing-and-merging.rst create mode 100644 Documentation/translations/zh_CN/mips/booting.rst create mode 100644 Documentation/translations/zh_CN/mips/features.rst create mode 100644 Documentation/translations/zh_CN/mips/index.rst create mode 100644 Documentation/translations/zh_CN/mips/ingenic-tcu.rst create mode 100644 Documentation/translations/zh_CN/mm/active_mm.rst create mode 100644 Documentation/translations/zh_CN/mm/balance.rst create mode 100644 Documentation/translations/zh_CN/mm/damon/api.rst create mode 100644 Documentation/translations/zh_CN/mm/damon/design.rst create mode 100644 Documentation/translations/zh_CN/mm/damon/faq.rst create mode 100644 Documentation/translations/zh_CN/mm/damon/index.rst create mode 100644 Documentation/translations/zh_CN/mm/free_page_reporting.rst create mode 100644 Documentation/translations/zh_CN/mm/frontswap.rst create mode 100644 Documentation/translations/zh_CN/mm/highmem.rst create mode 100644 Documentation/translations/zh_CN/mm/hmm.rst create mode 100644 Documentation/translations/zh_CN/mm/hugetlbfs_reserv.rst create mode 100644 Documentation/translations/zh_CN/mm/hwpoison.rst create mode 100644 Documentation/translations/zh_CN/mm/index.rst create mode 100644 Documentation/translations/zh_CN/mm/ksm.rst create mode 100644 Documentation/translations/zh_CN/mm/memory-model.rst create mode 100644 Documentation/translations/zh_CN/mm/mmu_notifier.rst create mode 100644 Documentation/translations/zh_CN/mm/numa.rst create mode 100644 Documentation/translations/zh_CN/mm/overcommit-accounting.rst create mode 100644 Documentation/translations/zh_CN/mm/page_frags.rst create mode 100644 Documentation/translations/zh_CN/mm/page_migration.rst create mode 100644 Documentation/translations/zh_CN/mm/page_owner.rst create mode 100644 Documentation/translations/zh_CN/mm/page_table_check.rst create mode 100644 Documentation/translations/zh_CN/mm/remap_file_pages.rst create mode 100644 Documentation/translations/zh_CN/mm/split_page_table_lock.rst create mode 100644 Documentation/translations/zh_CN/mm/vmalloced-kernel-stacks.rst create mode 100644 Documentation/translations/zh_CN/mm/z3fold.rst create mode 100644 Documentation/translations/zh_CN/mm/zsmalloc.rst create mode 100644 Documentation/translations/zh_CN/openrisc/index.rst create mode 100644 Documentation/translations/zh_CN/openrisc/openrisc_port.rst create mode 100644 Documentation/translations/zh_CN/openrisc/todo.rst create mode 100644 Documentation/translations/zh_CN/parisc/debugging.rst create mode 100644 Documentation/translations/zh_CN/parisc/index.rst create mode 100644 Documentation/translations/zh_CN/parisc/registers.rst create mode 100644 Documentation/translations/zh_CN/peci/index.rst create mode 100644 Documentation/translations/zh_CN/peci/peci.rst create mode 100644 Documentation/translations/zh_CN/power/energy-model.rst create mode 100644 Documentation/translations/zh_CN/power/index.rst create mode 100644 Documentation/translations/zh_CN/power/opp.rst create mode 100644 Documentation/translations/zh_CN/process/1.Intro.rst create mode 100644 Documentation/translations/zh_CN/process/2.Process.rst create mode 100644 Documentation/translations/zh_CN/process/3.Early-stage.rst create mode 100644 Documentation/translations/zh_CN/process/4.Coding.rst create mode 100644 Documentation/translations/zh_CN/process/5.Posting.rst create mode 100644 Documentation/translations/zh_CN/process/6.Followthrough.rst create mode 100644 Documentation/translations/zh_CN/process/7.AdvancedTopics.rst create mode 100644 Documentation/translations/zh_CN/process/8.Conclusion.rst create mode 100644 Documentation/translations/zh_CN/process/code-of-conduct-interpretation.rst create mode 100644 Documentation/translations/zh_CN/process/code-of-conduct.rst create mode 100644 Documentation/translations/zh_CN/process/coding-style.rst create mode 100644 Documentation/translations/zh_CN/process/development-process.rst create mode 100644 Documentation/translations/zh_CN/process/email-clients.rst create mode 100644 Documentation/translations/zh_CN/process/embargoed-hardware-issues.rst create mode 100644 Documentation/translations/zh_CN/process/howto.rst create mode 100644 Documentation/translations/zh_CN/process/index.rst create mode 100644 Documentation/translations/zh_CN/process/kernel-driver-statement.rst create mode 100644 Documentation/translations/zh_CN/process/kernel-enforcement-statement.rst create mode 100644 Documentation/translations/zh_CN/process/license-rules.rst create mode 100644 Documentation/translations/zh_CN/process/magic-number.rst create mode 100644 Documentation/translations/zh_CN/process/management-style.rst create mode 100644 Documentation/translations/zh_CN/process/programming-language.rst create mode 100644 Documentation/translations/zh_CN/process/stable-api-nonsense.rst create mode 100644 Documentation/translations/zh_CN/process/stable-kernel-rules.rst create mode 100644 Documentation/translations/zh_CN/process/submit-checklist.rst create mode 100644 Documentation/translations/zh_CN/process/submitting-patches.rst create mode 100644 Documentation/translations/zh_CN/process/volatile-considered-harmful.rst create mode 100644 Documentation/translations/zh_CN/riscv/boot-image-header.rst create mode 100644 Documentation/translations/zh_CN/riscv/index.rst create mode 100644 Documentation/translations/zh_CN/riscv/patch-acceptance.rst create mode 100644 Documentation/translations/zh_CN/riscv/vm-layout.rst create mode 100644 Documentation/translations/zh_CN/scheduler/completion.rst create mode 100644 Documentation/translations/zh_CN/scheduler/index.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-arch.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-bwc.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-capacity.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-debug.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-design-CFS.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-domains.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-energy.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-nice-design.rst create mode 100644 Documentation/translations/zh_CN/scheduler/sched-stats.rst create mode 100644 Documentation/translations/zh_CN/scheduler/schedutil.rst create mode 100644 Documentation/translations/zh_CN/sound/hd-audio/controls.rst create mode 100644 Documentation/translations/zh_CN/sound/hd-audio/index.rst create mode 100644 Documentation/translations/zh_CN/sound/index.rst create mode 100644 Documentation/translations/zh_CN/video4linux/omap3isp.txt create mode 100644 Documentation/translations/zh_CN/video4linux/v4l2-framework.txt create mode 100644 Documentation/translations/zh_CN/virt/acrn/cpuid.rst create mode 100644 Documentation/translations/zh_CN/virt/acrn/index.rst create mode 100644 Documentation/translations/zh_CN/virt/acrn/introduction.rst create mode 100644 Documentation/translations/zh_CN/virt/acrn/io-request.rst create mode 100644 Documentation/translations/zh_CN/virt/guest-halt-polling.rst create mode 100644 Documentation/translations/zh_CN/virt/index.rst create mode 100644 Documentation/translations/zh_CN/virt/ne_overview.rst create mode 100644 Documentation/translations/zh_CN/virt/paravirt_ops.rst create mode 100644 Documentation/translations/zh_TW/IRQ.txt create mode 100644 Documentation/translations/zh_TW/admin-guide/README.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/bug-bisect.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/bug-hunting.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/clearing-warn-once.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/cpu-load.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/index.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/init.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/reporting-issues.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/security-bugs.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/tainted-kernels.rst create mode 100644 Documentation/translations/zh_TW/admin-guide/unicode.rst create mode 100644 Documentation/translations/zh_TW/arm64/amu.rst create mode 100644 Documentation/translations/zh_TW/arm64/booting.txt create mode 100644 Documentation/translations/zh_TW/arm64/elf_hwcaps.rst create mode 100644 Documentation/translations/zh_TW/arm64/hugetlbpage.rst create mode 100644 Documentation/translations/zh_TW/arm64/index.rst create mode 100644 Documentation/translations/zh_TW/arm64/legacy_instructions.txt create mode 100644 Documentation/translations/zh_TW/arm64/memory.txt create mode 100644 Documentation/translations/zh_TW/arm64/perf.rst create mode 100644 Documentation/translations/zh_TW/arm64/silicon-errata.txt create mode 100644 Documentation/translations/zh_TW/arm64/tagged-pointers.txt create mode 100644 Documentation/translations/zh_TW/cpu-freq/core.rst create mode 100644 Documentation/translations/zh_TW/cpu-freq/cpu-drivers.rst create mode 100644 Documentation/translations/zh_TW/cpu-freq/cpufreq-stats.rst create mode 100644 Documentation/translations/zh_TW/cpu-freq/index.rst create mode 100644 Documentation/translations/zh_TW/disclaimer-zh_TW.rst create mode 100644 Documentation/translations/zh_TW/filesystems/debugfs.rst create mode 100644 Documentation/translations/zh_TW/filesystems/index.rst create mode 100644 Documentation/translations/zh_TW/filesystems/sysfs.txt create mode 100644 Documentation/translations/zh_TW/filesystems/tmpfs.rst create mode 100644 Documentation/translations/zh_TW/filesystems/virtiofs.rst create mode 100644 Documentation/translations/zh_TW/gpio.txt create mode 100644 Documentation/translations/zh_TW/index.rst create mode 100644 Documentation/translations/zh_TW/io_ordering.txt create mode 100644 Documentation/translations/zh_TW/process/1.Intro.rst create mode 100644 Documentation/translations/zh_TW/process/2.Process.rst create mode 100644 Documentation/translations/zh_TW/process/3.Early-stage.rst create mode 100644 Documentation/translations/zh_TW/process/4.Coding.rst create mode 100644 Documentation/translations/zh_TW/process/5.Posting.rst create mode 100644 Documentation/translations/zh_TW/process/6.Followthrough.rst create mode 100644 Documentation/translations/zh_TW/process/7.AdvancedTopics.rst create mode 100644 Documentation/translations/zh_TW/process/8.Conclusion.rst create mode 100644 Documentation/translations/zh_TW/process/code-of-conduct-interpretation.rst create mode 100644 Documentation/translations/zh_TW/process/code-of-conduct.rst create mode 100644 Documentation/translations/zh_TW/process/coding-style.rst create mode 100644 Documentation/translations/zh_TW/process/development-process.rst create mode 100644 Documentation/translations/zh_TW/process/email-clients.rst create mode 100644 Documentation/translations/zh_TW/process/embargoed-hardware-issues.rst create mode 100644 Documentation/translations/zh_TW/process/howto.rst create mode 100644 Documentation/translations/zh_TW/process/index.rst create mode 100644 Documentation/translations/zh_TW/process/kernel-driver-statement.rst create mode 100644 Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst create mode 100644 Documentation/translations/zh_TW/process/license-rules.rst create mode 100644 Documentation/translations/zh_TW/process/magic-number.rst create mode 100644 Documentation/translations/zh_TW/process/management-style.rst create mode 100644 Documentation/translations/zh_TW/process/programming-language.rst create mode 100644 Documentation/translations/zh_TW/process/stable-api-nonsense.rst create mode 100644 Documentation/translations/zh_TW/process/stable-kernel-rules.rst create mode 100644 Documentation/translations/zh_TW/process/submit-checklist.rst create mode 100644 Documentation/translations/zh_TW/process/submitting-patches.rst create mode 100644 Documentation/translations/zh_TW/process/volatile-considered-harmful.rst create mode 100644 Documentation/translations/zh_TW/sparse.txt create mode 100644 Documentation/usb/CREDITS create mode 100644 Documentation/usb/acm.rst create mode 100644 Documentation/usb/authorization.rst create mode 100644 Documentation/usb/chipidea.rst create mode 100644 Documentation/usb/dwc3.rst create mode 100644 Documentation/usb/ehci.rst create mode 100644 Documentation/usb/functionfs.rst create mode 100644 Documentation/usb/gadget-testing.rst create mode 100644 Documentation/usb/gadget_configfs.rst create mode 100644 Documentation/usb/gadget_hid.rst create mode 100644 Documentation/usb/gadget_multi.rst create mode 100644 Documentation/usb/gadget_printer.rst create mode 100644 Documentation/usb/gadget_serial.rst create mode 100644 Documentation/usb/index.rst create mode 100644 Documentation/usb/iuu_phoenix.rst create mode 100644 Documentation/usb/linux-cdc-acm.inf create mode 100644 Documentation/usb/linux.inf create mode 100644 Documentation/usb/mass-storage.rst create mode 100644 Documentation/usb/misc_usbsevseg.rst create mode 100644 Documentation/usb/mtouchusb.rst create mode 100644 Documentation/usb/ohci.rst create mode 100644 Documentation/usb/raw-gadget.rst create mode 100644 Documentation/usb/text_files.rst create mode 100644 Documentation/usb/usb-help.rst create mode 100644 Documentation/usb/usb-serial.rst create mode 100644 Documentation/usb/usbdevfs-drop-permissions.c create mode 100644 Documentation/usb/usbip_protocol.rst create mode 100644 Documentation/usb/usbmon.rst create mode 100644 Documentation/userspace-api/accelerators/ocxl.rst create mode 100644 Documentation/userspace-api/ebpf/index.rst create mode 100644 Documentation/userspace-api/ebpf/syscall.rst create mode 100644 Documentation/userspace-api/futex2.rst create mode 100644 Documentation/userspace-api/index.rst create mode 100644 Documentation/userspace-api/ioctl/cdrom.rst create mode 100644 Documentation/userspace-api/ioctl/hdio.rst create mode 100644 Documentation/userspace-api/ioctl/index.rst create mode 100644 Documentation/userspace-api/ioctl/ioctl-decoding.rst create mode 100644 Documentation/userspace-api/ioctl/ioctl-number.rst create mode 100644 Documentation/userspace-api/iommu.rst create mode 100644 Documentation/userspace-api/landlock.rst create mode 100644 Documentation/userspace-api/media/Makefile create mode 100644 Documentation/userspace-api/media/ca.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/cec.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/cec/cec-api.rst create mode 100644 Documentation/userspace-api/media/cec/cec-func-close.rst create mode 100644 Documentation/userspace-api/media/cec/cec-func-ioctl.rst create mode 100644 Documentation/userspace-api/media/cec/cec-func-open.rst create mode 100644 Documentation/userspace-api/media/cec/cec-func-poll.rst create mode 100644 Documentation/userspace-api/media/cec/cec-funcs.rst create mode 100644 Documentation/userspace-api/media/cec/cec-header.rst create mode 100644 Documentation/userspace-api/media/cec/cec-intro.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-adap-g-caps.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-adap-g-conn-info.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-adap-g-log-addrs.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-adap-g-phys-addr.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-dqevent.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-g-mode.rst create mode 100644 Documentation/userspace-api/media/cec/cec-ioc-receive.rst create mode 100644 Documentation/userspace-api/media/cec/cec-pin-error-inj.rst create mode 100644 Documentation/userspace-api/media/conf_nitpick.py create mode 100644 Documentation/userspace-api/media/dmx.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/drivers/ccs.rst create mode 100644 Documentation/userspace-api/media/drivers/cx2341x-uapi.rst create mode 100644 Documentation/userspace-api/media/drivers/dw100.rst create mode 100644 Documentation/userspace-api/media/drivers/imx-uapi.rst create mode 100644 Documentation/userspace-api/media/drivers/index.rst create mode 100644 Documentation/userspace-api/media/drivers/max2175.rst create mode 100644 Documentation/userspace-api/media/drivers/meye-uapi.rst create mode 100644 Documentation/userspace-api/media/drivers/omap3isp-uapi.rst create mode 100644 Documentation/userspace-api/media/drivers/uvcvideo.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-fclose.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-fopen.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-get-cap.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-get-descr-info.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-get-msg.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-get-slot-info.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-reset.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-send-msg.rst create mode 100644 Documentation/userspace-api/media/dvb/ca-set-descr.rst create mode 100644 Documentation/userspace-api/media/dvb/ca.rst create mode 100644 Documentation/userspace-api/media/dvb/ca_data_types.rst create mode 100644 Documentation/userspace-api/media/dvb/ca_function_calls.rst create mode 100644 Documentation/userspace-api/media/dvb/ca_high_level.rst create mode 100644 Documentation/userspace-api/media/dvb/demux.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-add-pid.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-expbuf.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-fclose.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-fopen.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-fread.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-fwrite.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-get-pes-pids.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-get-stc.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-mmap.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-munmap.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-qbuf.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-querybuf.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-remove-pid.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-reqbufs.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-set-buffer-size.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-set-filter.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-set-pes-filter.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-start.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx-stop.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx_fcalls.rst create mode 100644 Documentation/userspace-api/media/dvb/dmx_types.rst create mode 100644 Documentation/userspace-api/media/dvb/dvb-fe-read-status.rst create mode 100644 Documentation/userspace-api/media/dvb/dvb-frontend-event.rst create mode 100644 Documentation/userspace-api/media/dvb/dvb-frontend-parameters.rst create mode 100644 Documentation/userspace-api/media/dvb/dvbapi.rst create mode 100644 Documentation/userspace-api/media/dvb/dvbproperty.rst create mode 100644 Documentation/userspace-api/media/dvb/dvbstb.svg create mode 100644 Documentation/userspace-api/media/dvb/examples.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-bandwidth-t.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-diseqc-recv-slave-reply.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-diseqc-reset-overload.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-diseqc-send-burst.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-diseqc-send-master-cmd.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-dishnetwork-send-legacy-cmd.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-enable-high-lnb-voltage.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-get-event.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-get-frontend.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-get-info.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-get-property.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-read-ber.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-read-signal-strength.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-read-snr.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-read-status.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-read-uncorrected-blocks.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-set-frontend-tune-mode.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-set-frontend.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-set-tone.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-set-voltage.rst create mode 100644 Documentation/userspace-api/media/dvb/fe-type-t.rst create mode 100644 Documentation/userspace-api/media/dvb/fe_property_parameters.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend-header.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend-property-cable-systems.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend-property-satellite-systems.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend-property-terrestrial-systems.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend-stat-properties.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend_f_close.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend_f_open.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend_fcalls.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend_legacy_api.rst create mode 100644 Documentation/userspace-api/media/dvb/frontend_legacy_dvbv3_api.rst create mode 100644 Documentation/userspace-api/media/dvb/headers.rst create mode 100644 Documentation/userspace-api/media/dvb/intro.rst create mode 100644 Documentation/userspace-api/media/dvb/legacy_dvb_apis.rst create mode 100644 Documentation/userspace-api/media/dvb/net-add-if.rst create mode 100644 Documentation/userspace-api/media/dvb/net-get-if.rst create mode 100644 Documentation/userspace-api/media/dvb/net-remove-if.rst create mode 100644 Documentation/userspace-api/media/dvb/net-types.rst create mode 100644 Documentation/userspace-api/media/dvb/net.rst create mode 100644 Documentation/userspace-api/media/dvb/query-dvb-frontend-info.rst create mode 100644 Documentation/userspace-api/media/fdl-appendix.rst create mode 100644 Documentation/userspace-api/media/frontend.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/gen-errors.rst create mode 100644 Documentation/userspace-api/media/glossary.rst create mode 100644 Documentation/userspace-api/media/index.rst create mode 100644 Documentation/userspace-api/media/intro.rst create mode 100644 Documentation/userspace-api/media/lirc.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/media.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/mediactl/media-controller-intro.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-controller-model.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-controller.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-func-close.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-func-ioctl.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-func-open.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-funcs.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-header.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-device-info.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-enum-entities.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-enum-links.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-g-topology.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-request-alloc.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-ioc-setup-link.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-request-ioc-queue.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-request-ioc-reinit.rst create mode 100644 Documentation/userspace-api/media/mediactl/media-types.rst create mode 100644 Documentation/userspace-api/media/mediactl/request-api.rst create mode 100644 Documentation/userspace-api/media/mediactl/request-func-close.rst create mode 100644 Documentation/userspace-api/media/mediactl/request-func-ioctl.rst create mode 100644 Documentation/userspace-api/media/mediactl/request-func-poll.rst create mode 100644 Documentation/userspace-api/media/net.h.rst.exceptions create mode 100644 Documentation/userspace-api/media/rc/keytable.c.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-dev-intro.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-dev.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-func.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-get-features.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-get-rec-mode.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-get-rec-resolution.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-get-send-mode.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-get-timeout.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-header.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-read.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-measure-carrier-mode.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-rec-carrier-range.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-rec-carrier.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-rec-timeout.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-send-carrier.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-send-duty-cycle.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-transmitter-mask.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst create mode 100644 Documentation/userspace-api/media/rc/lirc-write.rst create mode 100644 Documentation/userspace-api/media/rc/rc-intro.rst create mode 100644 Documentation/userspace-api/media/rc/rc-protos.rst create mode 100644 Documentation/userspace-api/media/rc/rc-sysfs-nodes.rst create mode 100644 Documentation/userspace-api/media/rc/rc-table-change.rst create mode 100644 Documentation/userspace-api/media/rc/rc-tables.rst create mode 100644 Documentation/userspace-api/media/rc/remote_controllers.rst create mode 100644 Documentation/userspace-api/media/typical_media_device.svg create mode 100644 Documentation/userspace-api/media/v4l/app-pri.rst create mode 100644 Documentation/userspace-api/media/v4l/audio.rst create mode 100644 Documentation/userspace-api/media/v4l/bayer.svg create mode 100644 Documentation/userspace-api/media/v4l/biblio.rst create mode 100644 Documentation/userspace-api/media/v4l/buffer.rst create mode 100644 Documentation/userspace-api/media/v4l/capture-example.rst create mode 100644 Documentation/userspace-api/media/v4l/capture.c.rst create mode 100644 Documentation/userspace-api/media/v4l/colorspaces-defs.rst create mode 100644 Documentation/userspace-api/media/v4l/colorspaces-details.rst create mode 100644 Documentation/userspace-api/media/v4l/colorspaces.rst create mode 100644 Documentation/userspace-api/media/v4l/common-defs.rst create mode 100644 Documentation/userspace-api/media/v4l/common.rst create mode 100644 Documentation/userspace-api/media/v4l/compat.rst create mode 100644 Documentation/userspace-api/media/v4l/constraints.svg create mode 100644 Documentation/userspace-api/media/v4l/control.rst create mode 100644 Documentation/userspace-api/media/v4l/crop.rst create mode 100644 Documentation/userspace-api/media/v4l/crop.svg create mode 100644 Documentation/userspace-api/media/v4l/depth-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-capture.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-decoder.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-encoder.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-event.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-mem2mem.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-meta.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-osd.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-output.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-overlay.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-radio.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-raw-vbi.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-rds.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-sdr.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-stateless-decoder.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-subdev.rst create mode 100644 Documentation/userspace-api/media/v4l/dev-touch.rst create mode 100644 Documentation/userspace-api/media/v4l/devices.rst create mode 100644 Documentation/userspace-api/media/v4l/diff-v4l.rst create mode 100644 Documentation/userspace-api/media/v4l/dmabuf.rst create mode 100644 Documentation/userspace-api/media/v4l/dv-timings.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-camera.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-codec.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-colorimetry.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-detect.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-dv.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-flash.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-fm-rx.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-fm-tx.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst create mode 100644 Documentation/userspace-api/media/v4l/ext-ctrls-rf-tuner.rst create mode 100644 Documentation/userspace-api/media/v4l/extended-controls.rst create mode 100644 Documentation/userspace-api/media/v4l/field-order.rst create mode 100644 Documentation/userspace-api/media/v4l/fieldseq_bt.svg create mode 100644 Documentation/userspace-api/media/v4l/fieldseq_tb.svg create mode 100644 Documentation/userspace-api/media/v4l/format.rst create mode 100644 Documentation/userspace-api/media/v4l/fourcc.rst create mode 100644 Documentation/userspace-api/media/v4l/func-close.rst create mode 100644 Documentation/userspace-api/media/v4l/func-ioctl.rst create mode 100644 Documentation/userspace-api/media/v4l/func-mmap.rst create mode 100644 Documentation/userspace-api/media/v4l/func-munmap.rst create mode 100644 Documentation/userspace-api/media/v4l/func-open.rst create mode 100644 Documentation/userspace-api/media/v4l/func-poll.rst create mode 100644 Documentation/userspace-api/media/v4l/func-read.rst create mode 100644 Documentation/userspace-api/media/v4l/func-select.rst create mode 100644 Documentation/userspace-api/media/v4l/func-write.rst create mode 100644 Documentation/userspace-api/media/v4l/hist-v4l2.rst create mode 100644 Documentation/userspace-api/media/v4l/hsv-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/io.rst create mode 100644 Documentation/userspace-api/media/v4l/libv4l-introduction.rst create mode 100644 Documentation/userspace-api/media/v4l/libv4l.rst create mode 100644 Documentation/userspace-api/media/v4l/meta-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/mmap.rst create mode 100644 Documentation/userspace-api/media/v4l/nv12mt.svg create mode 100644 Documentation/userspace-api/media/v4l/nv12mt_example.svg create mode 100644 Documentation/userspace-api/media/v4l/open.rst create mode 100644 Documentation/userspace-api/media/v4l/pipeline.dot create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-bayer.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-cnf4.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-compressed.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-indexed.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-intro.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-inzi.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-m420.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-d4xx.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-intel-ipu3.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-rkisp1.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-uvc.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-vivid.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-vsp1-hgo.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-meta-vsp1-hgt.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-packed-hsv.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-packed-yuv.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-reserved.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-rgb.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-cs08.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-cs14le.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-cu08.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-cu16le.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-pcu16be.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-pcu18be.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-pcu20be.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-sdr-ru12le.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb10-ipu3.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb10.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb10alaw8.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb10dpcm8.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb10p.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb12.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb12p.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb14.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb14p.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb16.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-srggb8.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-tch-td08.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-tch-td16.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-tch-tu08.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-tch-tu16.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-uv8.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-v4l2-mplane.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-v4l2.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-y12i.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-y8i.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-z16.rst create mode 100644 Documentation/userspace-api/media/v4l/pixfmt.rst create mode 100644 Documentation/userspace-api/media/v4l/planar-apis.rst create mode 100644 Documentation/userspace-api/media/v4l/querycap.rst create mode 100644 Documentation/userspace-api/media/v4l/rw.rst create mode 100644 Documentation/userspace-api/media/v4l/sdr-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api-configuration.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api-examples.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api-intro.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api-targets.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api-vs-crop-api.rst create mode 100644 Documentation/userspace-api/media/v4l/selection-api.rst create mode 100644 Documentation/userspace-api/media/v4l/selection.svg create mode 100644 Documentation/userspace-api/media/v4l/selections-common.rst create mode 100644 Documentation/userspace-api/media/v4l/standard.rst create mode 100644 Documentation/userspace-api/media/v4l/streaming-par.rst create mode 100644 Documentation/userspace-api/media/v4l/subdev-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/subdev-image-processing-crop.svg create mode 100644 Documentation/userspace-api/media/v4l/subdev-image-processing-full.svg create mode 100644 Documentation/userspace-api/media/v4l/subdev-image-processing-scaling-multi-source.svg create mode 100644 Documentation/userspace-api/media/v4l/tch-formats.rst create mode 100644 Documentation/userspace-api/media/v4l/tuner.rst create mode 100644 Documentation/userspace-api/media/v4l/user-func.rst create mode 100644 Documentation/userspace-api/media/v4l/userp.rst create mode 100644 Documentation/userspace-api/media/v4l/v4l2-selection-flags.rst create mode 100644 Documentation/userspace-api/media/v4l/v4l2-selection-targets.rst create mode 100644 Documentation/userspace-api/media/v4l/v4l2.rst create mode 100644 Documentation/userspace-api/media/v4l/v4l2grab-example.rst create mode 100644 Documentation/userspace-api/media/v4l/v4l2grab.c.rst create mode 100644 Documentation/userspace-api/media/v4l/vbi_525.svg create mode 100644 Documentation/userspace-api/media/v4l/vbi_625.svg create mode 100644 Documentation/userspace-api/media/v4l/vbi_hsync.svg create mode 100644 Documentation/userspace-api/media/v4l/video.rst create mode 100644 Documentation/userspace-api/media/v4l/videodev.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-create-bufs.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-cropcap.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-dbg-g-chip-info.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-dbg-g-register.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-decoder-cmd.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-dqevent.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-dv-timings-cap.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-encoder-cmd.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enum-dv-timings.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enum-fmt.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enum-frameintervals.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enum-framesizes.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enum-freq-bands.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enumaudio.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enumaudioout.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enuminput.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enumoutput.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-enumstd.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-expbuf.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-audio.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-audioout.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-crop.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-ctrl.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-dv-timings.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-edid.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-enc-index.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-ext-ctrls.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-fbuf.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-fmt.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-frequency.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-input.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-jpegcomp.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-modulator.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-output.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-parm.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-priority.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-selection.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-sliced-vbi-cap.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-std.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-g-tuner.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-log-status.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-overlay.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-prepare-buf.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-qbuf.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-query-dv-timings.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-querybuf.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-querycap.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-queryctrl.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-querystd.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-s-hw-freq-seek.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-streamon.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-enum-frame-interval.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-enum-frame-size.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-enum-mbus-code.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-g-crop.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-g-fmt.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-g-frame-interval.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-g-selection.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subdev-querycap.rst create mode 100644 Documentation/userspace-api/media/v4l/vidioc-subscribe-event.rst create mode 100644 Documentation/userspace-api/media/v4l/yuv-formats.rst create mode 100644 Documentation/userspace-api/media/videodev2.h.rst.exceptions create mode 100644 Documentation/userspace-api/netlink/index.rst create mode 100644 Documentation/userspace-api/netlink/intro.rst create mode 100644 Documentation/userspace-api/no_new_privs.rst create mode 100644 Documentation/userspace-api/seccomp_filter.rst create mode 100644 Documentation/userspace-api/spec_ctrl.rst create mode 100644 Documentation/userspace-api/sysfs-platform_profile.rst create mode 100644 Documentation/userspace-api/unshare.rst create mode 100644 Documentation/userspace-api/vduse.rst create mode 100644 Documentation/virt/acrn/cpuid.rst create mode 100644 Documentation/virt/acrn/index.rst create mode 100644 Documentation/virt/acrn/introduction.rst create mode 100644 Documentation/virt/acrn/io-request.rst create mode 100644 Documentation/virt/coco/sev-guest.rst create mode 100644 Documentation/virt/guest-halt-polling.rst create mode 100644 Documentation/virt/hyperv/clocks.rst create mode 100644 Documentation/virt/hyperv/index.rst create mode 100644 Documentation/virt/hyperv/overview.rst create mode 100644 Documentation/virt/hyperv/vmbus.rst create mode 100644 Documentation/virt/index.rst create mode 100644 Documentation/virt/kvm/api.rst create mode 100644 Documentation/virt/kvm/arm/hyp-abi.rst create mode 100644 Documentation/virt/kvm/arm/hypercalls.rst create mode 100644 Documentation/virt/kvm/arm/index.rst create mode 100644 Documentation/virt/kvm/arm/ptp_kvm.rst create mode 100644 Documentation/virt/kvm/arm/pvtime.rst create mode 100644 Documentation/virt/kvm/devices/README create mode 100644 Documentation/virt/kvm/devices/arm-vgic-its.rst create mode 100644 Documentation/virt/kvm/devices/arm-vgic-v3.rst create mode 100644 Documentation/virt/kvm/devices/arm-vgic.rst create mode 100644 Documentation/virt/kvm/devices/index.rst create mode 100644 Documentation/virt/kvm/devices/mpic.rst create mode 100644 Documentation/virt/kvm/devices/s390_flic.rst create mode 100644 Documentation/virt/kvm/devices/vcpu.rst create mode 100644 Documentation/virt/kvm/devices/vfio.rst create mode 100644 Documentation/virt/kvm/devices/vm.rst create mode 100644 Documentation/virt/kvm/devices/xics.rst create mode 100644 Documentation/virt/kvm/devices/xive.rst create mode 100644 Documentation/virt/kvm/halt-polling.rst create mode 100644 Documentation/virt/kvm/index.rst create mode 100644 Documentation/virt/kvm/locking.rst create mode 100644 Documentation/virt/kvm/ppc-pv.rst create mode 100644 Documentation/virt/kvm/review-checklist.rst create mode 100644 Documentation/virt/kvm/s390/index.rst create mode 100644 Documentation/virt/kvm/s390/s390-diag.rst create mode 100644 Documentation/virt/kvm/s390/s390-pv-boot.rst create mode 100644 Documentation/virt/kvm/s390/s390-pv-dump.rst create mode 100644 Documentation/virt/kvm/s390/s390-pv.rst create mode 100644 Documentation/virt/kvm/vcpu-requests.rst create mode 100644 Documentation/virt/kvm/x86/amd-memory-encryption.rst create mode 100644 Documentation/virt/kvm/x86/cpuid.rst create mode 100644 Documentation/virt/kvm/x86/errata.rst create mode 100644 Documentation/virt/kvm/x86/hypercalls.rst create mode 100644 Documentation/virt/kvm/x86/index.rst create mode 100644 Documentation/virt/kvm/x86/mmu.rst create mode 100644 Documentation/virt/kvm/x86/msr.rst create mode 100644 Documentation/virt/kvm/x86/nested-vmx.rst create mode 100644 Documentation/virt/kvm/x86/running-nested-guests.rst create mode 100644 Documentation/virt/kvm/x86/timekeeping.rst create mode 100644 Documentation/virt/ne_overview.rst create mode 100644 Documentation/virt/paravirt_ops.rst create mode 100644 Documentation/virt/uml/user_mode_linux_howto_v2.rst create mode 100644 Documentation/w1/index.rst create mode 100644 Documentation/w1/masters/ds2482.rst create mode 100644 Documentation/w1/masters/ds2490.rst create mode 100644 Documentation/w1/masters/index.rst create mode 100644 Documentation/w1/masters/mxc-w1.rst create mode 100644 Documentation/w1/masters/omap-hdq.rst create mode 100644 Documentation/w1/masters/w1-gpio.rst create mode 100644 Documentation/w1/slaves/index.rst create mode 100644 Documentation/w1/slaves/w1_ds2406.rst create mode 100644 Documentation/w1/slaves/w1_ds2413.rst create mode 100644 Documentation/w1/slaves/w1_ds2423.rst create mode 100644 Documentation/w1/slaves/w1_ds2438.rst create mode 100644 Documentation/w1/slaves/w1_ds28e04.rst create mode 100644 Documentation/w1/slaves/w1_ds28e17.rst create mode 100644 Documentation/w1/slaves/w1_therm.rst create mode 100644 Documentation/w1/w1-generic.rst create mode 100644 Documentation/w1/w1-netlink.rst create mode 100644 Documentation/watchdog/convert_drivers_to_kernel_api.rst create mode 100644 Documentation/watchdog/hpwdt.rst create mode 100644 Documentation/watchdog/index.rst create mode 100644 Documentation/watchdog/mlx-wdt.rst create mode 100644 Documentation/watchdog/pcwd-watchdog.rst create mode 100644 Documentation/watchdog/watchdog-api.rst create mode 100644 Documentation/watchdog/watchdog-kernel-api.rst create mode 100644 Documentation/watchdog/watchdog-parameters.rst create mode 100644 Documentation/watchdog/watchdog-pm.rst create mode 100644 Documentation/watchdog/wdt.rst create mode 100644 Documentation/x86/amd-memory-encryption.rst create mode 100644 Documentation/x86/amd_hsmp.rst create mode 100644 Documentation/x86/boot.rst create mode 100644 Documentation/x86/booting-dt.rst create mode 100644 Documentation/x86/buslock.rst create mode 100644 Documentation/x86/cpuinfo.rst create mode 100644 Documentation/x86/earlyprintk.rst create mode 100644 Documentation/x86/elf_auxvec.rst create mode 100644 Documentation/x86/entry_64.rst create mode 100644 Documentation/x86/exception-tables.rst create mode 100644 Documentation/x86/features.rst create mode 100644 Documentation/x86/i386/IO-APIC.rst create mode 100644 Documentation/x86/i386/index.rst create mode 100644 Documentation/x86/ifs.rst create mode 100644 Documentation/x86/index.rst create mode 100644 Documentation/x86/intel-hfi.rst create mode 100644 Documentation/x86/intel_txt.rst create mode 100644 Documentation/x86/iommu.rst create mode 100644 Documentation/x86/kernel-stacks.rst create mode 100644 Documentation/x86/mds.rst create mode 100644 Documentation/x86/microcode.rst create mode 100644 Documentation/x86/mtrr.rst create mode 100644 Documentation/x86/orc-unwinder.rst create mode 100644 Documentation/x86/pat.rst create mode 100644 Documentation/x86/pti.rst create mode 100644 Documentation/x86/resctrl.rst create mode 100644 Documentation/x86/sgx.rst create mode 100644 Documentation/x86/sva.rst create mode 100644 Documentation/x86/tdx.rst create mode 100644 Documentation/x86/tlb.rst create mode 100644 Documentation/x86/topology.rst create mode 100644 Documentation/x86/tsx_async_abort.rst create mode 100644 Documentation/x86/usb-legacy-support.rst create mode 100644 Documentation/x86/x86_64/5level-paging.rst create mode 100644 Documentation/x86/x86_64/boot-options.rst create mode 100644 Documentation/x86/x86_64/cpu-hotplug-spec.rst create mode 100644 Documentation/x86/x86_64/fake-numa-for-cpusets.rst create mode 100644 Documentation/x86/x86_64/fsgs.rst create mode 100644 Documentation/x86/x86_64/index.rst create mode 100644 Documentation/x86/x86_64/machinecheck.rst create mode 100644 Documentation/x86/x86_64/mm.rst create mode 100644 Documentation/x86/x86_64/uefi.rst create mode 100644 Documentation/x86/xstate.rst create mode 100644 Documentation/x86/zero-page.rst create mode 100644 Documentation/xtensa/atomctl.rst create mode 100644 Documentation/xtensa/booting.rst create mode 100644 Documentation/xtensa/features.rst create mode 100644 Documentation/xtensa/index.rst create mode 100644 Documentation/xtensa/mmu.rst (limited to 'Documentation') diff --git a/Documentation/.gitignore b/Documentation/.gitignore new file mode 100644 index 000000000..d6dc7c9b8 --- /dev/null +++ b/Documentation/.gitignore @@ -0,0 +1,3 @@ +# SPDX-License-Identifier: GPL-2.0-only +output +*.pyc diff --git a/Documentation/ABI/README b/Documentation/ABI/README new file mode 100644 index 000000000..8bac9cb09 --- /dev/null +++ b/Documentation/ABI/README @@ -0,0 +1,95 @@ +This directory attempts to document the ABI between the Linux kernel and +userspace, and the relative stability of these interfaces. Due to the +everchanging nature of Linux, and the differing maturity levels, these +interfaces should be used by userspace programs in different ways. + +We have four different levels of ABI stability, as shown by the four +different subdirectories in this location. Interfaces may change levels +of stability according to the rules described below. + +The different levels of stability are: + + stable/ + This directory documents the interfaces that the developer has + defined to be stable. Userspace programs are free to use these + interfaces with no restrictions, and backward compatibility for + them will be guaranteed for at least 2 years. Most interfaces + (like syscalls) are expected to never change and always be + available. + + testing/ + This directory documents interfaces that are felt to be stable, + as the main development of this interface has been completed. + The interface can be changed to add new features, but the + current interface will not break by doing this, unless grave + errors or security problems are found in them. Userspace + programs can start to rely on these interfaces, but they must be + aware of changes that can occur before these interfaces move to + be marked stable. Programs that use these interfaces are + strongly encouraged to add their name to the description of + these interfaces, so that the kernel developers can easily + notify them if any changes occur (see the description of the + layout of the files below for details on how to do this.) + + obsolete/ + This directory documents interfaces that are still remaining in + the kernel, but are marked to be removed at some later point in + time. The description of the interface will document the reason + why it is obsolete and when it can be expected to be removed. + + removed/ + This directory contains a list of the old interfaces that have + been removed from the kernel. + +Every file in these directories will contain the following information: + +What: Short description of the interface +Date: Date created +KernelVersion: Kernel version this feature first showed up in. +Contact: Primary contact for this interface (may be a mailing list) +Description: Long description of the interface and how to use it. +Users: All users of this interface who wish to be notified when + it changes. This is very important for interfaces in + the "testing" stage, so that kernel developers can work + with userspace developers to ensure that things do not + break in ways that are unacceptable. It is also + important to get feedback for these interfaces to make + sure they are working in a proper way and do not need to + be changed further. + + +Note: + The fields should be use a simple notation, compatible with ReST markup. + Also, the file **should not** have a top-level index, like:: + + === + foo + === + +How things move between levels: + +Interfaces in stable may move to obsolete, as long as the proper +notification is given. + +Interfaces may be removed from obsolete and the kernel as long as the +documented amount of time has gone by. + +Interfaces in the testing state can move to the stable state when the +developers feel they are finished. They cannot be removed from the +kernel tree without going through the obsolete state first. + +It's up to the developer to place their interfaces in the category they +wish for it to start out in. + + +Notable bits of non-ABI, which should not under any circumstances be considered +stable: + +- Kconfig. Userspace should not rely on the presence or absence of any + particular Kconfig symbol, in /proc/config.gz, in the copy of .config + commonly installed to /boot, or in any invocation of the kernel build + process. + +- Kernel-internal symbols. Do not rely on the presence, absence, location, or + type of any kernel symbol, either in System.map files or the kernel binary + itself. See Documentation/process/stable-api-nonsense.rst. diff --git a/Documentation/ABI/obsolete/o2cb b/Documentation/ABI/obsolete/o2cb new file mode 100644 index 000000000..fe7e45e17 --- /dev/null +++ b/Documentation/ABI/obsolete/o2cb @@ -0,0 +1,11 @@ +What: /sys/o2cb +Date: Dec 2005 +KernelVersion: 2.6.16 +Contact: ocfs2-devel@oss.oracle.com +Description: Ocfs2-tools looks at 'interface-revision' for versioning + information. Each logmask/ file controls a set of debug prints + and can be written into with the strings "allow", "deny", or + "off". Reading the file returns the current state. + Was renamed to /sys/fs/u2cb/ +Users: ocfs2-tools. It's sufficient to mail proposed changes to + ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/obsolete/procfs-i8k b/Documentation/ABI/obsolete/procfs-i8k new file mode 100644 index 000000000..32df4d5bd --- /dev/null +++ b/Documentation/ABI/obsolete/procfs-i8k @@ -0,0 +1,10 @@ +What: /proc/i8k +Date: November 2001 +KernelVersion: 2.4.14 +Contact: Pali Rohár +Description: Legacy interface for getting/setting sensor information like + fan speed, temperature, serial number, hotkey status etc + on Dell Laptops. + Since the driver is now using the standard hwmon sysfs interface, + the procfs interface is deprecated. +Users: https://github.com/vitorafsr/i8kutils diff --git a/Documentation/ABI/obsolete/sysfs-bus-iio b/Documentation/ABI/obsolete/sysfs-bus-iio new file mode 100644 index 000000000..b64394b0b --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-bus-iio @@ -0,0 +1,186 @@ +What: /sys/bus/iio/devices/iio:deviceX/buffer/length +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Number of scans contained by the buffer. + + Since Kernel 5.11, multiple buffers are supported. + so, it is better to use, instead: + + /sys/bus/iio/devices/iio:deviceX/bufferY/length + +What: /sys/bus/iio/devices/iio:deviceX/buffer/enable +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Actually start the buffer capture up. Will start trigger + if first device and appropriate. + + Since Kernel 5.11, multiple buffers are supported. + so, it is better to use, instead: + + /sys/bus/iio/devices/iio:deviceX/bufferY/enable + +What: /sys/bus/iio/devices/iio:deviceX/scan_elements +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Directory containing interfaces for elements that will be + captured for a single triggered sample set in the buffer. + + Since kernel 5.11 the scan_elements attributes are merged into + the bufferY directory, to be configurable per buffer. + +What: /sys/.../iio:deviceX/scan_elements/in_accel_x_en +What: /sys/.../iio:deviceX/scan_elements/in_accel_y_en +What: /sys/.../iio:deviceX/scan_elements/in_accel_z_en +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_x_en +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_y_en +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_z_en +What: /sys/.../iio:deviceX/scan_elements/in_magn_x_en +What: /sys/.../iio:deviceX/scan_elements/in_magn_y_en +What: /sys/.../iio:deviceX/scan_elements/in_magn_z_en +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_en +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_en +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_tilt_comp_en +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_tilt_comp_en +What: /sys/.../iio:deviceX/scan_elements/in_timestamp_en +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_en +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_en +What: /sys/.../iio:deviceX/scan_elements/in_voltageY-voltageZ_en +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_en +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_en +What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_en +What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_en +What: /sys/.../iio:deviceX/scan_elements/in_incli_x_en +What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en +What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en +What: /sys/.../iio:deviceX/scan_elements/in_pressure_en +What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en +What: /sys/.../iio:deviceX/scan_elements/in_proximity_en +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Scan element control for triggered data capture. + + Since kernel 5.11 the scan_elements attributes are merged into + the bufferY directory, to be configurable per buffer. + +What: /sys/.../iio:deviceX/scan_elements/in_accel_type +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_type +What: /sys/.../iio:deviceX/scan_elements/in_magn_type +What: /sys/.../iio:deviceX/scan_elements/in_incli_type +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_type +What: /sys/.../iio:deviceX/scan_elements/in_voltage_type +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_type +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_type +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_type +What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_type +What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_type +What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type +What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type +What: /sys/.../iio:deviceX/scan_elements/in_pressure_type +What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type +What: /sys/.../iio:deviceX/scan_elements/in_proximity_type +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Description of the scan element data storage within the buffer + and hence the form in which it is read from user-space. + Form is [be|le]:[s|u]bits/storagebits[>>shift]. + be or le specifies big or little endian. s or u specifies if + signed (2's complement) or unsigned. bits is the number of bits + of data and storagebits is the space (after padding) that it + occupies in the buffer. shift if specified, is the shift that + needs to be applied prior to masking out unused bits. Some + devices put their data in the middle of the transferred elements + with additional information on both sides. Note that some + devices will have additional information in the unused bits + so to get a clean value, the bits value must be used to mask + the buffer output value appropriately. The storagebits value + also specifies the data alignment. So s48/64>>2 will be a + signed 48 bit integer stored in a 64 bit location aligned to + a 64 bit boundary. To obtain the clean value, shift right 2 + and apply a mask to zero the top 16 bits of the result. + For other storage combinations this attribute will be extended + appropriately. + + Since kernel 5.11 the scan_elements attributes are merged into + the bufferY directory, to be configurable per buffer. + +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_index +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_index +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_index +What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_index +What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_index +What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_index +What: /sys/.../iio:deviceX/scan_elements/in_accel_x_index +What: /sys/.../iio:deviceX/scan_elements/in_accel_y_index +What: /sys/.../iio:deviceX/scan_elements/in_accel_z_index +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_x_index +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_y_index +What: /sys/.../iio:deviceX/scan_elements/in_anglvel_z_index +What: /sys/.../iio:deviceX/scan_elements/in_magn_x_index +What: /sys/.../iio:deviceX/scan_elements/in_magn_y_index +What: /sys/.../iio:deviceX/scan_elements/in_magn_z_index +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_index +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_index +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_tilt_comp_index +What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_tilt_comp_index +What: /sys/.../iio:deviceX/scan_elements/in_incli_x_index +What: /sys/.../iio:deviceX/scan_elements/in_incli_y_index +What: /sys/.../iio:deviceX/scan_elements/in_timestamp_index +What: /sys/.../iio:deviceX/scan_elements/in_pressureY_index +What: /sys/.../iio:deviceX/scan_elements/in_pressure_index +What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_index +What: /sys/.../iio:deviceX/scan_elements/in_proximity_index +KernelVersion: 2.6.37 +Description: + A single positive integer specifying the position of this + scan element in the buffer. Note these are not dependent on + what is enabled and may not be contiguous. Thus for user-space + to establish the full layout these must be used in conjunction + with all _en attributes to establish which channels are present, + and the relevant _type attributes to establish the data storage + format. + + Since kernel 5.11 the scan_elements attributes are merged into + the bufferY directory, to be configurable per buffer. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/watermark +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + A single positive integer specifying the maximum number of scan + elements to wait for. + + Poll will block until the watermark is reached. + + Blocking read will wait until the minimum between the requested + read amount or the low water mark is available. + + Non-blocking read will retrieve the available samples from the + buffer even if there are less samples then watermark level. This + allows the application to block on poll with a timeout and read + the available samples after the timeout expires and thus have a + maximum delay guarantee. + + Since Kernel 5.11, multiple buffers are supported. + so, it is better to use, instead: + + /sys/bus/iio/devices/iio:deviceX/bufferY/watermark + +What: /sys/bus/iio/devices/iio:deviceX/buffer/data_available +KernelVersion: 4.16 +Contact: linux-iio@vger.kernel.org +Description: + A read-only value indicating the bytes of data available in the + buffer. In the case of an output buffer, this indicates the + amount of empty space available to write data to. In the case of + an input buffer, this indicates the amount of data available for + reading. + + Since Kernel 5.11, multiple buffers are supported. + so, it is better to use, instead: + + /sys/bus/iio/devices/iio:deviceX/bufferY/data_available diff --git a/Documentation/ABI/obsolete/sysfs-bus-usb b/Documentation/ABI/obsolete/sysfs-bus-usb new file mode 100644 index 000000000..bd096d33f --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-bus-usb @@ -0,0 +1,31 @@ +What: /sys/bus/usb/devices/.../power/level +Date: March 2007 +KernelVersion: 2.6.21 +Contact: Alan Stern +Description: + Each USB device directory will contain a file named + power/level. This file holds a power-level setting for + the device, either "on" or "auto". + + "on" means that the device is not allowed to autosuspend, + although normal suspends for system sleep will still + be honored. "auto" means the device will autosuspend + and autoresume in the usual manner, according to the + capabilities of its driver. + + During normal use, devices should be left in the "auto" + level. The "on" level is meant for administrative uses. + If you want to suspend a device immediately but leave it + free to wake up in response to I/O requests, you should + write "0" to power/autosuspend. + + Device not capable of proper suspend and resume should be + left in the "on" level. Although the USB spec requires + devices to support suspend/resume, many of them do not. + In fact so many don't that by default, the USB core + initializes all non-hub devices in the "on" level. Some + drivers may change this setting when they are bound. + + This file is deprecated and will be removed after 2010. + Use the power/control file instead; it does exactly the + same thing. diff --git a/Documentation/ABI/obsolete/sysfs-class-typec b/Documentation/ABI/obsolete/sysfs-class-typec new file mode 100644 index 000000000..32623514e --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-class-typec @@ -0,0 +1,48 @@ +These files are deprecated and will be removed. The same files are available +under /sys/bus/typec (see Documentation/ABI/testing/sysfs-bus-typec). + +What: /sys/class/typec///svid +Date: April 2017 +Contact: Heikki Krogerus +Description: + The SVID (Standard or Vendor ID) assigned by USB-IF for this + alternate mode. + +What: /sys/class/typec///mode/ +Date: April 2017 +Contact: Heikki Krogerus +Description: + Every supported mode will have its own directory. The name of + a mode will be "mode" (for example mode1), where + is the actual index to the mode VDO returned by Discover Modes + USB power delivery command. + +What: /sys/class/typec///mode/description +Date: April 2017 +Contact: Heikki Krogerus +Description: + Shows description of the mode. The description is optional for + the drivers, just like with the Billboard Devices. + +What: /sys/class/typec///mode/vdo +Date: April 2017 +Contact: Heikki Krogerus +Description: + Shows the VDO in hexadecimal returned by Discover Modes command + for this mode. + +What: /sys/class/typec///mode/active +Date: April 2017 +Contact: Heikki Krogerus +Description: + Shows if the mode is active or not. The attribute can be used + for entering/exiting the mode with partners and cable plugs, and + with the port alternate modes it can be used for disabling + support for specific alternate modes. Entering/exiting modes is + supported as synchronous operation so write(2) to the attribute + does not return until the enter/exit mode operation has + finished. The attribute is notified when the mode is + entered/exited so poll(2) on the attribute wakes up. + Entering/exiting a mode will also generate uevent KOBJ_CHANGE. + + Valid values: yes, no diff --git a/Documentation/ABI/obsolete/sysfs-cpuidle b/Documentation/ABI/obsolete/sysfs-cpuidle new file mode 100644 index 000000000..972cc11d3 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-cpuidle @@ -0,0 +1,9 @@ +What: /sys/devices/system/cpu/cpuidle/current_governor_ro +Date: April, 2020 +Contact: linux-pm@vger.kernel.org +Description: + current_governor_ro shows current using cpuidle governor, but read only. + with the update that cpuidle governor can be changed at runtime in default, + both current_governor and current_governor_ro co-exist under + /sys/devices/system/cpu/cpuidle/ file, it's duplicate so make + current_governor_ro obsolete. diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo new file mode 100644 index 000000000..55e281b00 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo @@ -0,0 +1,53 @@ +What: /sys/bus/usb/devices/-:./::./arvo/roccatarvo/actual_profile +Date: Januar 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 1-5. + When read, this attribute returns the number of the actual + profile which is also the profile that's active on device startup. + When written this attribute activates the selected profile + immediately. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./arvo/roccatarvo/button +Date: Januar 2011 +Contact: Stefan Achatz +Description: The keyboard can store short macros with consist of 1 button with + several modifier keys internally. + When written, this file lets one set the sequence for a specific + button for a specific profile. Button and profile numbers are + included in written data. The data has to be 24 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./arvo/roccatarvo/info +Date: Januar 2011 +Contact: Stefan Achatz +Description: When read, this file returns some info about the device like the + installed firmware version. + The size of the data is 8 bytes in size. + This file is readonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./arvo/roccatarvo/key_mask +Date: Januar 2011 +Contact: Stefan Achatz +Description: The keyboard lets the user deactivate 5 certain keys like the + windows and application keys, to protect the user from the outcome + of accidentally pressing them. + The integer value of this attribute has bits 0-4 set depending + on the state of the corresponding key. + When read, this file returns the current state of the buttons. + When written, the given buttons are activated/deactivated + immediately. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./arvo/roccatarvo/mode_key +Date: Januar 2011 +Contact: Stefan Achatz +Description: The keyboard has a condensed layout without num-lock key. + Instead it uses a mode-key which activates a gaming mode where + the assignment of the number block changes. + The integer value of this attribute ranges from 0 (OFF) to 1 (ON). + When read, this file returns the actual state of the key. + When written, the key is activated/deactivated immediately. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku new file mode 100644 index 000000000..c601d0f2a --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku @@ -0,0 +1,153 @@ +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/actual_profile +Date: June 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 0-4. + When read, this attribute returns the number of the actual + profile. This value is persistent, so its equivalent to the + profile that's active when the device is powered on next time. + When written, this file sets the number of the startup profile + and the device activates this profile immediately. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/info +Date: June 2011 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + The data is 6 bytes long. + This file is readonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/key_mask +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one deactivate certain keys like + windows and application keys, to prevent accidental presses. + Profile number for which this settings occur is included in + written data. The data has to be 6 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_capslock +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + capslock key for a specific profile. Profile number is included + in written data. The data has to be 6 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_easyzone +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + easyzone keys for a specific profile. Profile number is included + in written data. The data has to be 65 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_function +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + function keys for a specific profile. Profile number is included + in written data. The data has to be 41 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_macro +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the macro + keys for a specific profile. Profile number is included in + written data. The data has to be 35 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_media +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the media + keys for a specific profile. Profile number is included in + written data. The data has to be 29 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/keys_thumbster +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + thumbster keys for a specific profile. Profile number is included + in written data. The data has to be 23 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/last_set +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the time in secs since + epoch in which the last configuration took place. + The data has to be 20 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/light +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one set the backlight intensity for + a specific profile. Profile number is included in written data. + The data has to be 10 bytes long for Isku, IskuFX needs 16 bytes + of data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/macro +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one store macros with max 500 + keystrokes for a specific button for a specific profile. + Button and profile numbers are included in written data. + The data has to be 2083 bytes long. + Before reading this file, control has to be written to select + which profile and key to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/reset +Date: November 2012 +Contact: Stefan Achatz +Description: When written, this file lets one reset the device. + The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/control +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one select which data from which + profile will be read next. The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/talk +Date: June 2011 +Contact: Stefan Achatz +Description: When written, this file lets one trigger easyshift functionality + from the host. + The data has to be 16 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./isku/roccatisku/talkfx +Date: February 2013 +Contact: Stefan Achatz +Description: When written, this file lets one trigger temporary color schemes + from the host. + The data has to be 16 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus new file mode 100644 index 000000000..545e69f43 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus @@ -0,0 +1,145 @@ +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/actual_profile +Date: October 2010 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 0-4. + When read, this attribute returns the number of the actual + profile. This value is persistent, so its equivalent to the + profile that's active when the mouse is powered on next time. + When written, this file sets the number of the startup profile + and the mouse activates this profile immediately. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/startup_profile +Date: October 2010 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 0-4. + When read, this attribute returns the number of the actual + profile. This value is persistent, so its equivalent to the + profile that's active when the mouse is powered on next time. + When written, this file sets the number of the startup profile + and the mouse activates this profile immediately. + Please use actual_profile, it does the same thing. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/firmware_version +Date: October 2010 +Contact: Stefan Achatz +Description: When read, this file returns the raw integer version number of the + firmware reported by the mouse. Using the integer value eases + further usage in other programs. To receive the real version + number the decimal point has to be shifted 2 positions to the + left. E.g. a returned value of 121 means 1.21 + This file is readonly. + Please read binary attribute info which contains firmware version. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/info +Date: November 2012 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + When written, the device can be reset. + The data is 8 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/macro +Date: October 2010 +Contact: Stefan Achatz +Description: The mouse can store a macro with max 500 key/button strokes + internally. + When written, this file lets one set the sequence for a specific + button for a specific profile. Button and profile numbers are + included in written data. The data has to be 2082 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/profile_buttons +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When written, this file lets one write the respective profile + buttons back to the mouse. The data has to be 77 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/profile[1-5]_buttons +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When read, these files return the respective profile buttons. + The returned data is 77 bytes in size. + This file is readonly. + Write control to select profile and read profile_buttons instead. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/profile_settings +Date: October 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When written, this file lets one write the respective profile + settings back to the mouse. The data has to be 43 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/profile[1-5]_settings +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When read, these files return the respective profile settings. + The returned data is 43 bytes in size. + This file is readonly. + Write control to select profile and read profile_settings instead. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/sensor +Date: October 2010 +Contact: Stefan Achatz +Description: The mouse has a tracking- and a distance-control-unit. These + can be activated/deactivated and the lift-off distance can be + set. The data has to be 6 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/talk +Date: May 2011 +Contact: Stefan Achatz +Description: Used to active some easy* functions of the mouse from outside. + The data has to be 16 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/tcu +Date: October 2010 +Contact: Stefan Achatz +Description: When written a calibration process for the tracking control unit + can be initiated/cancelled. Also lets one read/write sensor + registers. + The data has to be 4 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./koneplus/roccatkoneplus/tcu_image +Date: October 2010 +Contact: Stefan Achatz +Description: When read the mouse returns a 30x30 pixel image of the + sampled underground. This works only in the course of a + calibration process initiated with tcu. + The returned data is 1028 bytes in size. + This file is readonly. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure new file mode 100644 index 000000000..41a9b7fbf --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure @@ -0,0 +1,105 @@ +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/actual_profile +Date: December 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. actual_profile holds number of actual profile. + This value is persistent, so its value determines the profile + that's active when the mouse is powered on next time. + When written, the mouse activates the set profile immediately. + The data has to be 3 bytes long. + The mouse will reject invalid data. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/control +Date: December 2012 +Contact: Stefan Achatz +Description: When written, this file lets one select which data from which + profile will be read next. The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/info +Date: December 2012 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + When written, the device can be reset. + The data is 6 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/macro +Date: December 2012 +Contact: Stefan Achatz +Description: The mouse can store a macro with max 500 key/button strokes + internally. + When written, this file lets one set the sequence for a specific + button for a specific profile. Button and profile numbers are + included in written data. The data has to be 2082 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/profile_buttons +Date: December 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When written, this file lets one write the respective profile + buttons back to the mouse. The data has to be 59 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/profile_settings +Date: December 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When written, this file lets one write the respective profile + settings back to the mouse. The data has to be 31 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/sensor +Date: December 2012 +Contact: Stefan Achatz +Description: The mouse has a tracking- and a distance-control-unit. These + can be activated/deactivated and the lift-off distance can be + set. The data has to be 6 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/talk +Date: December 2012 +Contact: Stefan Achatz +Description: Used to active some easy* functions of the mouse from outside. + The data has to be 16 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/tcu +Date: December 2012 +Contact: Stefan Achatz +Description: When written a calibration process for the tracking control unit + can be initiated/cancelled. Also lets one read/write sensor + registers. + The data has to be 4 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./konepure/roccatkonepure/tcu_image +Date: December 2012 +Contact: Stefan Achatz +Description: When read the mouse returns a 30x30 pixel image of the + sampled underground. This works only in the course of a + calibration process initiated with tcu. + The returned data is 1028 bytes in size. + This file is readonly. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus new file mode 100644 index 000000000..ab01631e1 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus @@ -0,0 +1,116 @@ +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/actual_cpi +Date: January 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 1-4. + When read, this attribute returns the number of the active + cpi level. + This file is readonly. + Has never been used. If bookkeeping is done, it's done in userland tools. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/actual_profile +Date: January 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 0-4. + When read, this attribute returns the number of the active + profile. + When written, the mouse activates this profile immediately. + The profile that's active when powered down is the same that's + active when the mouse is powered on. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/actual_sensitivity_x +Date: January 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 1-10. + When read, this attribute returns the number of the actual + sensitivity in x direction. + This file is readonly. + Has never been used. If bookkeeping is done, it's done in userland tools. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/actual_sensitivity_y +Date: January 2011 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 1-10. + When read, this attribute returns the number of the actual + sensitivity in y direction. + This file is readonly. + Has never been used. If bookkeeping is done, it's done in userland tools. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/firmware_version +Date: January 2011 +Contact: Stefan Achatz +Description: When read, this file returns the raw integer version number of the + firmware reported by the mouse. Using the integer value eases + further usage in other programs. To receive the real version + number the decimal point has to be shifted 2 positions to the + left. E.g. a returned value of 121 means 1.21 + This file is readonly. + Obsoleted by binary sysfs attribute "info". +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/info +Date: November 2012 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + When written, the device can be reset. + The data is 6 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/profile_buttons +Date: January 2011 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When written, this file lets one write the respective profile + buttons back to the mouse. The data has to be 23 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/profile[1-5]_buttons +Date: January 2011 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When read, these files return the respective profile buttons. + The returned data is 23 bytes in size. + This file is readonly. + Write control to select profile and read profile_buttons instead. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/profile_settings +Date: January 2011 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When written, this file lets one write the respective profile + settings back to the mouse. The data has to be 16 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./kovaplus/roccatkovaplus/profile[1-5]_settings +Date: January 2011 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When read, these files return the respective profile settings. + The returned data is 16 bytes in size. + This file is readonly. + Write control to select profile and read profile_settings instead. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua new file mode 100644 index 000000000..31c6c4c8b --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua @@ -0,0 +1,7 @@ +What: /sys/bus/usb/devices/-:./control +Date: October 2012 +Contact: Stefan Achatz +Description: When written, cpi, button and light settings can be configured. + When read, actual cpi setting and sensor data are returned. + The data has to be 8 bytes long. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra new file mode 100644 index 000000000..66545c587 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra @@ -0,0 +1,126 @@ +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/actual_cpi +Date: August 2010 +Contact: Stefan Achatz +Description: It is possible to switch the cpi setting of the mouse with the + press of a button. + When read, this file returns the raw number of the actual cpi + setting reported by the mouse. This number has to be further + processed to receive the real dpi value: + + ===== ==== + VALUE DPI + ===== ==== + 1 400 + 2 800 + 4 1600 + ===== ==== + + This file is readonly. + Has never been used. If bookkeeping is done, it's done in userland tools. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/actual_profile +Date: August 2010 +Contact: Stefan Achatz +Description: When read, this file returns the number of the actual profile in + range 0-4. + This file is readonly. + Please use binary attribute "settings" which provides this information. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/firmware_version +Date: August 2010 +Contact: Stefan Achatz +Description: When read, this file returns the raw integer version number of the + firmware reported by the mouse. Using the integer value eases + further usage in other programs. To receive the real version + number the decimal point has to be shifted 2 positions to the + left. E.g. a returned value of 138 means 1.38 + This file is readonly. + Please use binary attribute "info" which provides this information. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/info +Date: November 2012 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + When written, the device can be reset. + The data is 6 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/profile_buttons +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When written, this file lets one write the respective profile + buttons back to the mouse. The data has to be 19 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/profile[1-5]_buttons +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_buttons holds information about button layout. + When read, these files return the respective profile buttons. + The returned data is 19 bytes in size. + This file is readonly. + Write control to select profile and read profile_buttons instead. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/profile_settings +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When written, this file lets one write the respective profile + settings back to the mouse. The data has to be 13 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/profile[1-5]_settings +Date: August 2010 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split in settings and buttons. + profile_settings holds information like resolution, sensitivity + and light effects. + When read, these files return the respective profile settings. + The returned data is 13 bytes in size. + This file is readonly. + Write control to select profile and read profile_settings instead. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/settings +Date: August 2010 +Contact: Stefan Achatz +Description: When read, this file returns the settings stored in the mouse. + The size of the data is 3 bytes and holds information on the + startup_profile. + When written, this file lets write settings back to the mouse. + The data has to be 3 bytes long. The mouse will reject invalid + data. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./pyra/roccatpyra/startup_profile +Date: August 2010 +Contact: Stefan Achatz +Description: The integer value of this attribute ranges from 0-4. + When read, this attribute returns the number of the profile + that's active when the mouse is powered on. + This file is readonly. + Please use binary attribute "settings" which provides this information. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos new file mode 100644 index 000000000..1d6a8cf9d --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos @@ -0,0 +1,178 @@ +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/control +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one select which data from which + profile will be read next. The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/profile +Date: October 2013 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. profile holds index of actual profile. + This value is persistent, so its value determines the profile + that's active when the device is powered on next time. + When written, the device activates the set profile immediately. + The data has to be 3 bytes long. + The device will reject invalid data. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_primary +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the default of all keys for + a specific profile. Profile index is included in written data. + The data has to be 125 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_function +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + function keys for a specific profile. Profile index is included + in written data. The data has to be 95 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_macro +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the macro + keys for a specific profile. Profile index is included in + written data. The data has to be 35 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_thumbster +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + thumbster keys for a specific profile. Profile index is included + in written data. The data has to be 23 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_extra +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + capslock and function keys for a specific profile. Profile index + is included in written data. The data has to be 8 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/keys_easyzone +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the function of the + easyzone keys for a specific profile. Profile index is included + in written data. The data has to be 294 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/key_mask +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one deactivate certain keys like + windows and application keys, to prevent accidental presses. + Profile index for which this settings occur is included in + written data. The data has to be 6 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/light +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the backlight intensity for + a specific profile. Profile index is included in written data. + This attribute is only valid for the glow and pro variant. + The data has to be 16 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/macro +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one store macros with max 480 + keystrokes for a specific button for a specific profile. + Button and profile indexes are included in written data. + The data has to be 2002 bytes long. + Before reading this file, control has to be written to select + which profile and key to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/info +Date: October 2013 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + The data is 8 bytes long. + This file is readonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/reset +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one reset the device. + The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/talk +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one trigger easyshift functionality + from the host. + The data has to be 16 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/light_control +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one switch between stored and custom + light settings. + This attribute is only valid for the pro variant. + The data has to be 8 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/stored_lights +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set per-key lighting for different + layers. + This attribute is only valid for the pro variant. + The data has to be 1382 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/custom_lights +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set the actual per-key lighting. + This attribute is only valid for the pro variant. + The data has to be 20 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./ryos/roccatryos/light_macro +Date: October 2013 +Contact: Stefan Achatz +Description: When written, this file lets one set a light macro that is looped + whenever the device gets in dimness mode. + This attribute is only valid for the pro variant. + The data has to be 2002 bytes long. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu new file mode 100644 index 000000000..99fda67fc --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu @@ -0,0 +1,77 @@ +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/buttons +Date: Mai 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split into general settings and + button settings. The buttons variable holds information about + button layout. When written, this file lets one write the + respective profile buttons to the mouse. The data has to be + 47 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + Before reading this file, control has to be written to select + which profile to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/control +Date: Mai 2012 +Contact: Stefan Achatz +Description: When written, this file lets one select which data from which + profile will be read next. The data has to be 3 bytes long. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/general +Date: Mai 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. A profile is split into general settings and + button settings. A profile holds information like resolution, + sensitivity and light effects. + When written, this file lets one write the respective profile + settings back to the mouse. The data has to be 43 bytes long. + The mouse will reject invalid data. + Which profile to write is determined by the profile number + contained in the data. + This file is writeonly. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/info +Date: Mai 2012 +Contact: Stefan Achatz +Description: When read, this file returns general data like firmware version. + When written, the device can be reset. + The data is 8 bytes long. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/macro +Date: Mai 2012 +Contact: Stefan Achatz +Description: When written, this file lets one store macros with max 500 + keystrokes for a specific button for a specific profile. + Button and profile numbers are included in written data. + The data has to be 2083 bytes long. + Before reading this file, control has to be written to select + which profile and key to read. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/profile +Date: Mai 2012 +Contact: Stefan Achatz +Description: The mouse can store 5 profiles which can be switched by the + press of a button. profile holds number of actual profile. + This value is persistent, so its value determines the profile + that's active when the mouse is powered on next time. + When written, the mouse activates the set profile immediately. + The data has to be 3 bytes long. + The mouse will reject invalid data. +Users: http://roccat.sourceforge.net + +What: /sys/bus/usb/devices/-:./::./savu/roccatsavu/sensor +Date: July 2012 +Contact: Stefan Achatz +Description: The mouse has a Avago ADNS-3090 sensor. + This file allows reading and writing of the mouse sensors registers. + The data has to be 4 bytes long. +Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/obsolete/sysfs-driver-intel_pmc_bxt b/Documentation/ABI/obsolete/sysfs-driver-intel_pmc_bxt new file mode 100644 index 000000000..39d5659f3 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-driver-intel_pmc_bxt @@ -0,0 +1,22 @@ +These files allow sending arbitrary IPC commands to the PMC/SCU which +may be dangerous. These will be removed eventually and should not be +used in any new applications. + +What: /sys/bus/platform/devices/INT34D2:00/simplecmd +Date: Jun 2015 +KernelVersion: 4.1 +Contact: Mika Westerberg +Description: This interface allows userspace to send an arbitrary + IPC command to the PMC/SCU. + + Format: %d %d where first number is command and + second number is subcommand. + +What: /sys/bus/platform/devices/INT34D2:00/northpeak +Date: Jun 2015 +KernelVersion: 4.1 +Contact: Mika Westerberg +Description: This interface allows userspace to enable and disable + Northpeak through the PMC/SCU. + + Format: %u. diff --git a/Documentation/ABI/obsolete/sysfs-firmware-acpi b/Documentation/ABI/obsolete/sysfs-firmware-acpi new file mode 100644 index 000000000..6715a71be --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-firmware-acpi @@ -0,0 +1,8 @@ +What: /sys/firmware/acpi/hotplug/force_remove +Date: Mar 2017 +Contact: Rafael J. Wysocki +Description: + Since the force_remove is inherently broken and dangerous to + use for some hotplugable resources like memory (because ignoring + the offline failure might lead to memory corruption and crashes) + enabling this knob is not safe and thus unsupported. diff --git a/Documentation/ABI/obsolete/sysfs-gpio b/Documentation/ABI/obsolete/sysfs-gpio new file mode 100644 index 000000000..b8b0fd341 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-gpio @@ -0,0 +1,32 @@ +What: /sys/class/gpio/ +Date: July 2008 +KernelVersion: 2.6.27 +Contact: Linus Walleij +Description: + + As a Kconfig option, individual GPIO signals may be accessed from + userspace. GPIOs are only made available to userspace by an explicit + "export" operation. If a given GPIO is not claimed for use by + kernel code, it may be exported by userspace (and unexported later). + Kernel code may export it for complete or partial access. + + GPIOs are identified as they are inside the kernel, using integers in + the range 0..INT_MAX. See Documentation/admin-guide/gpio for more information. + + :: + + /sys/class/gpio + /export ... asks the kernel to export a GPIO to userspace + /unexport ... to return a GPIO to the kernel + /gpioN ... for each exported GPIO #N OR + / ... for a properly named GPIO line + /value ... always readable, writes fail for input GPIOs + /direction ... r/w as: in, out (default low); write: high, low + /edge ... r/w as: none, falling, rising, both + /gpiochipN ... for each gpiochip; #N is its first GPIO + /base ... (r/o) same as N + /label ... (r/o) descriptive, not necessarily unique + /ngpio ... (r/o) number of GPIOs; numbered N to N + (ngpio - 1) + + This ABI is deprecated and will be removed after 2020. It is + replaced with the GPIO character device. diff --git a/Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled b/Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled new file mode 100644 index 000000000..e9c2de8b3 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled @@ -0,0 +1,9 @@ +This ABI is renamed and moved to a new location /sys/kernel/fadump/enabled. + +What: /sys/kernel/fadump_enabled +Date: Feb 2012 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Primarily used to identify whether the FADump is enabled in + the kernel or not. +User: Kdump service diff --git a/Documentation/ABI/obsolete/sysfs-kernel-fadump_registered b/Documentation/ABI/obsolete/sysfs-kernel-fadump_registered new file mode 100644 index 000000000..dae880b1a --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-kernel-fadump_registered @@ -0,0 +1,10 @@ +This ABI is renamed and moved to a new location /sys/kernel/fadump/registered. + +What: /sys/kernel/fadump_registered +Date: Feb 2012 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + Helps to control the dump collect feature from userspace. + Setting 1 to this file enables the system to collect the + dump and 0 to disable it. +User: Kdump service diff --git a/Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem b/Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem new file mode 100644 index 000000000..ca2396edb --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem @@ -0,0 +1,10 @@ +This ABI is renamed and moved to a new location /sys/kernel/fadump/release_mem. + +What: /sys/kernel/fadump_release_mem +Date: Feb 2012 +Contact: linuxppc-dev@lists.ozlabs.org +Description: write only + This is a special sysfs file and only available when + the system is booted to capture the vmcore using FADump. + It is used to release the memory reserved by FADump to + save the crash dump. diff --git a/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot b/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot new file mode 100644 index 000000000..ed6b52ca2 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-selinux-checkreqprot @@ -0,0 +1,23 @@ +What: /sys/fs/selinux/checkreqprot +Date: April 2005 (predates git) +KernelVersion: 2.6.12-rc2 (predates git) +Contact: selinux@vger.kernel.org +Description: + + The selinuxfs "checkreqprot" node allows SELinux to be configured + to check the protection requested by userspace for mmap/mprotect + calls instead of the actual protection applied by the kernel. + This was a compatibility mechanism for legacy userspace and + for the READ_IMPLIES_EXEC personality flag. However, if set to + 1, it weakens security by allowing mappings to be made executable + without authorization by policy. The default value of checkreqprot + at boot was changed starting in Linux v4.4 to 0 (i.e. check the + actual protection), and Android and Linux distributions have been + explicitly writing a "0" to /sys/fs/selinux/checkreqprot during + initialization for some time. Support for setting checkreqprot to 1 + will be removed no sooner than June 2021, at which point the kernel + will always cease using checkreqprot internally and will always + check the actual protections being applied upon mmap/mprotect calls. + The checkreqprot selinuxfs node will remain for backward compatibility + but will discard writes of the "0" value and will reject writes of the + "1" value when this mechanism is removed. diff --git a/Documentation/ABI/obsolete/sysfs-selinux-disable b/Documentation/ABI/obsolete/sysfs-selinux-disable new file mode 100644 index 000000000..c340278e3 --- /dev/null +++ b/Documentation/ABI/obsolete/sysfs-selinux-disable @@ -0,0 +1,26 @@ +What: /sys/fs/selinux/disable +Date: April 2005 (predates git) +KernelVersion: 2.6.12-rc2 (predates git) +Contact: selinux@vger.kernel.org +Description: + + The selinuxfs "disable" node allows SELinux to be disabled at runtime + prior to a policy being loaded into the kernel. If disabled via this + mechanism, SELinux will remain disabled until the system is rebooted. + + The preferred method of disabling SELinux is via the "selinux=0" boot + parameter, but the selinuxfs "disable" node was created to make it + easier for systems with primitive bootloaders that did not allow for + easy modification of the kernel command line. Unfortunately, allowing + for SELinux to be disabled at runtime makes it difficult to secure the + kernel's LSM hooks using the "__ro_after_init" feature. + + Thankfully, the need for the SELinux runtime disable appears to be + gone, the default Kconfig configuration disables this selinuxfs node, + and only one of the major distributions, Fedora, supports disabling + SELinux at runtime. Fedora is in the process of removing the + selinuxfs "disable" node and once that is complete we will start the + slow process of removing this code from the kernel. + + More information on /sys/fs/selinux/disable can be found under the + CONFIG_SECURITY_SELINUX_DISABLE Kconfig option. diff --git a/Documentation/ABI/removed/devfs b/Documentation/ABI/removed/devfs new file mode 100644 index 000000000..24fb35adf --- /dev/null +++ b/Documentation/ABI/removed/devfs @@ -0,0 +1,13 @@ +What: devfs +Date: July 2005 (scheduled), finally removed in kernel v2.6.18 +Contact: Greg Kroah-Hartman +Description: + devfs has been unmaintained for a number of years, has unfixable + races, contains a naming policy within the kernel that is + against the LSB, and can be replaced by using udev. + + The files fs/devfs/*, include/linux/devfs_fs*.h were removed, + along with the assorted devfs function calls throughout the + kernel tree. + +Users: diff --git a/Documentation/ABI/removed/dv1394 b/Documentation/ABI/removed/dv1394 new file mode 100644 index 000000000..c2310b667 --- /dev/null +++ b/Documentation/ABI/removed/dv1394 @@ -0,0 +1,14 @@ +What: dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire) +Date: May 2010 (scheduled), finally removed in kernel v2.6.37 +Contact: linux1394-devel@lists.sourceforge.net +Description: + /dev/dv1394/* were character device files, one for each FireWire + controller and for NTSC and PAL respectively, from which DV data + could be received by read() or transmitted by write(). A few + ioctl()s allowed limited control. + This special-purpose interface has been superseded by libraw1394 + + libiec61883 which are functionally equivalent, support HDV, and + transparently work on top of the newer firewire kernel drivers. + +Users: + ffmpeg/libavformat (if configured for DV1394) diff --git a/Documentation/ABI/removed/ip_queue b/Documentation/ABI/removed/ip_queue new file mode 100644 index 000000000..3243613bc --- /dev/null +++ b/Documentation/ABI/removed/ip_queue @@ -0,0 +1,9 @@ +What: ip_queue +Date: finally removed in kernel v3.5.0 +Contact: Pablo Neira Ayuso +Description: + ip_queue has been replaced by nfnetlink_queue which provides + more advanced queueing mechanism to user-space. The ip_queue + module was already announced to become obsolete years ago. + +Users: diff --git a/Documentation/ABI/removed/net_dma b/Documentation/ABI/removed/net_dma new file mode 100644 index 000000000..a173aecc2 --- /dev/null +++ b/Documentation/ABI/removed/net_dma @@ -0,0 +1,8 @@ +What: tcp_dma_copybreak sysctl +Date: Removed in kernel v3.13 +Contact: Dan Williams +Description: + Formerly the lower limit, in bytes, of the size of socket reads + that will be offloaded to a DMA copy engine. Removed due to + coherency issues of the cpu potentially touching the buffers + while dma is in flight. diff --git a/Documentation/ABI/removed/o2cb b/Documentation/ABI/removed/o2cb new file mode 100644 index 000000000..20c91adca --- /dev/null +++ b/Documentation/ABI/removed/o2cb @@ -0,0 +1,10 @@ +What: /sys/o2cb symlink +Date: May 2011 +KernelVersion: 3.0 +Contact: ocfs2-devel@oss.oracle.com +Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is + removed when new versions of ocfs2-tools which know to look + in /sys/fs/o2cb are sufficiently prevalent. Don't code new + software to look here, it should try /sys/fs/o2cb instead. +Users: ocfs2-tools. It's sufficient to mail proposed changes to + ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/removed/raw1394 b/Documentation/ABI/removed/raw1394 new file mode 100644 index 000000000..9ec7ec493 --- /dev/null +++ b/Documentation/ABI/removed/raw1394 @@ -0,0 +1,16 @@ +What: raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire) +Date: May 2010 (scheduled), finally removed in kernel v2.6.37 +Contact: linux1394-devel@lists.sourceforge.net +Description: + /dev/raw1394 was a character device file that allowed low-level + access to FireWire buses. Its major drawbacks were its inability + to implement sensible device security policies, and its low level + of abstraction that required userspace clients to duplicate much + of the kernel's ieee1394 core functionality. + + Replaced by /dev/fw*, i.e. the ABI of + firewire-core. + +Users: + libraw1394 (works with firewire-cdev too, transparent to library ABI + users) diff --git a/Documentation/ABI/removed/sysfs-bus-nfit b/Documentation/ABI/removed/sysfs-bus-nfit new file mode 100644 index 000000000..277437005 --- /dev/null +++ b/Documentation/ABI/removed/sysfs-bus-nfit @@ -0,0 +1,17 @@ +What: /sys/bus/nd/devices/regionX/nfit/ecc_unit_size +Date: Aug, 2017 +KernelVersion: v4.14 (Removed v4.18) +Contact: nvdimm@lists.linux.dev +Description: + (RO) Size of a write request to a DIMM that will not incur a + read-modify-write cycle at the memory controller. + + When the nfit driver initializes it runs an ARS (Address Range + Scrub) operation across every pmem range. Part of that process + involves determining the ARS capabilities of a given address + range. One of the capabilities that is reported is the 'Clear + Uncorrectable Error Range Length Unit Size' (see: ACPI 6.2 + section 9.20.7.4 Function Index 1 - Query ARS Capabilities). + This property indicates the boundary at which the NVDIMM may + need to perform read-modify-write cycles to maintain ECC (Error + Correcting Code) blocks. diff --git a/Documentation/ABI/removed/sysfs-class-rfkill b/Documentation/ABI/removed/sysfs-class-rfkill new file mode 100644 index 000000000..f25174eaf --- /dev/null +++ b/Documentation/ABI/removed/sysfs-class-rfkill @@ -0,0 +1,13 @@ +rfkill - radio frequency (RF) connector kill switch support + +For details to this subsystem look at Documentation/driver-api/rfkill.rst. + +What: /sys/class/rfkill/rfkill[0-9]+/claim +Date: 09-Jul-2007 +KernelVersion v2.6.22 +Contact: linux-wireless@vger.kernel.org +Description: This file was deprecated because there no longer was a way to + claim just control over a single rfkill instance. + This file was scheduled to be removed in 2012, and was removed + in 2016. +Values: 0: Kernel handles events diff --git a/Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore b/Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore new file mode 100644 index 000000000..a8d46cd0f --- /dev/null +++ b/Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore @@ -0,0 +1,9 @@ +This ABI is moved to /sys/firmware/opal/mpipl/release_core. + +What: /sys/kernel/fadump_release_opalcore +Date: Sep 2019 +Contact: linuxppc-dev@lists.ozlabs.org +Description: write only + The sysfs file is available when the system is booted to + collect the dump on OPAL based machine. It used to release + the memory used to collect the opalcore. diff --git a/Documentation/ABI/removed/sysfs-kernel-uids b/Documentation/ABI/removed/sysfs-kernel-uids new file mode 100644 index 000000000..85a90b86c --- /dev/null +++ b/Documentation/ABI/removed/sysfs-kernel-uids @@ -0,0 +1,14 @@ +What: /sys/kernel/uids//cpu_shares +Date: December 2007, finally removed in kernel v2.6.34-rc1 +Contact: Dhaval Giani + Srivatsa Vaddagiri +Description: + The /sys/kernel/uids//cpu_shares tunable is used + to set the cpu bandwidth a user is allowed. This is a + proportional value. What that means is that if there + are two users logged in, each with an equal number of + shares, then they will get equal CPU bandwidth. Another + example would be, if User A has shares = 1024 and user + B has shares = 2048, User B will get twice the CPU + bandwidth user A will. For more details refer + Documentation/scheduler/sched-design-CFS.rst diff --git a/Documentation/ABI/removed/sysfs-mce b/Documentation/ABI/removed/sysfs-mce new file mode 100644 index 000000000..ef5dd2a80 --- /dev/null +++ b/Documentation/ABI/removed/sysfs-mce @@ -0,0 +1,37 @@ +What: /sys/devices/system/machinecheck/machinecheckX/tolerant +Contact: Borislav Petkov +Date: Dec, 2021 +Description: + Unused and obsolete after the advent of recoverable machine + checks (see last sentence below) and those are present since + 2010 (Nehalem). + + Original description: + + The entries appear for each CPU, but they are truly shared + between all CPUs. + + Tolerance level. When a machine check exception occurs for a + non corrected machine check the kernel can take different + actions. + + Since machine check exceptions can happen any time it is + sometimes risky for the kernel to kill a process because it + defies normal kernel locking rules. The tolerance level + configures how hard the kernel tries to recover even at some + risk of deadlock. Higher tolerant values trade potentially + better uptime with the risk of a crash or even corruption + (for tolerant >= 3). + + == =========================================================== + 0 always panic on uncorrected errors, log corrected errors + 1 panic or SIGBUS on uncorrected errors, log corrected errors + 2 SIGBUS or log uncorrected errors, log corrected errors + 3 never panic or SIGBUS, log all errors (for testing only) + == =========================================================== + + Default: 1 + + Note this only makes a difference if the CPU allows recovery + from a machine check exception. Current x86 CPUs generally + do not. diff --git a/Documentation/ABI/removed/video1394 b/Documentation/ABI/removed/video1394 new file mode 100644 index 000000000..1905d35a6 --- /dev/null +++ b/Documentation/ABI/removed/video1394 @@ -0,0 +1,17 @@ +What: video1394 (a.k.a. "OHCI-1394 Video support" for FireWire) +Date: May 2010 (scheduled), finally removed in kernel v2.6.37 +Contact: linux1394-devel@lists.sourceforge.net +Description: + /dev/video1394/* were character device files, one for each FireWire + controller, which were used for isochronous I/O. It was added as an + alternative to raw1394's isochronous I/O functionality which had + performance issues in its first generation. Any video1394 user had + to use raw1394 + libraw1394 too because video1394 did not provide + asynchronous I/O for device discovery and configuration. + + Replaced by /dev/fw*, i.e. the ABI of + firewire-core. + +Users: + libdc1394 (works with firewire-cdev too, transparent to library ABI + users) diff --git a/Documentation/ABI/stable/firewire-cdev b/Documentation/ABI/stable/firewire-cdev new file mode 100644 index 000000000..261f85b13 --- /dev/null +++ b/Documentation/ABI/stable/firewire-cdev @@ -0,0 +1,111 @@ +What: /dev/fw[0-9]+ +Date: May 2007 +KernelVersion: 2.6.22 +Contact: linux1394-devel@lists.sourceforge.net +Description: + The character device files /dev/fw* are the interface between + firewire-core and IEEE 1394 device drivers implemented in + userspace. The ioctl(2)- and read(2)-based ABI is defined and + documented in . + + This ABI offers most of the features which firewire-core also + exposes to kernelspace IEEE 1394 drivers. + + Each /dev/fw* is associated with one IEEE 1394 node, which can + be remote or local nodes. Operations on a /dev/fw* file have + different scope: + + - The 1394 node which is associated with the file: + + - Asynchronous request transmission + - Get the Configuration ROM + - Query node ID + - Query maximum speed of the path between this node + and local node + + - The 1394 bus (i.e. "card") to which the node is attached to: + + - Isochronous stream transmission and reception + - Asynchronous stream transmission and reception + - Asynchronous broadcast request transmission + - PHY packet transmission and reception + - Allocate, reallocate, deallocate isochronous + resources (channels, bandwidth) at the bus's IRM + - Query node IDs of local node, root node, IRM, bus + manager + - Query cycle time + - Bus reset initiation, bus reset event reception + + - All 1394 buses: + + - Allocation of IEEE 1212 address ranges on the local + link layers, reception of inbound requests to such + an address range, asynchronous response transmission + to inbound requests + - Addition of descriptors or directories to the local + nodes' Configuration ROM + + Due to the different scope of operations and in order to let + userland implement different access permission models, some + operations are restricted to /dev/fw* files that are associated + with a local node: + + - Addition of descriptors or directories to the local + nodes' Configuration ROM + - PHY packet transmission and reception + + A /dev/fw* file remains associated with one particular node + during its entire life time. Bus topology changes, and hence + node ID changes, are tracked by firewire-core. ABI users do not + need to be aware of topology. + + The following file operations are supported: + + open(2) + Currently the only useful flags are O_RDWR. + + ioctl(2) + Initiate various actions. Some take immediate effect, others + are performed asynchronously while or after the ioctl returns. + See the inline documentation in for + descriptions of all ioctls. + + poll(2), select(2), epoll_wait(2) etc. + Watch for events to become available to be read. + + read(2) + Receive various events. There are solicited events like + outbound asynchronous transaction completion or isochronous + buffer completion, and unsolicited events such as bus resets, + request reception, or PHY packet reception. Always use a read + buffer which is large enough to receive the largest event that + could ever arrive. See for descriptions + of all event types and for which ioctls affect reception of + events. + + mmap(2) + Allocate a DMA buffer for isochronous reception or transmission + and map it into the process address space. The arguments should + be used as follows: addr = NULL, length = the desired buffer + size, i.e. number of packets times size of largest packet, + prot = at least PROT_READ for reception and at least PROT_WRITE + for transmission, flags = MAP_SHARED, fd = the handle to the + /dev/fw*, offset = 0. + + Isochronous reception works in packet-per-buffer fashion except + for multichannel reception which works in buffer-fill mode. + + munmap(2) + Unmap the isochronous I/O buffer from the process address space. + + close(2) + Besides stopping and freeing I/O contexts that were associated + with the file descriptor, back out any changes to the local + nodes' Configuration ROM. Deallocate isochronous channels and + bandwidth at the IRM that were marked for kernel-assisted + re- and deallocation. + +Users: libraw1394; + libdc1394; + libhinawa; + tools like linux-firewire-utils, fwhack, ... diff --git a/Documentation/ABI/stable/o2cb b/Documentation/ABI/stable/o2cb new file mode 100644 index 000000000..b62a967f0 --- /dev/null +++ b/Documentation/ABI/stable/o2cb @@ -0,0 +1,10 @@ +What: /sys/fs/o2cb/ +Date: Dec 2005 +KernelVersion: 2.6.16 +Contact: ocfs2-devel@oss.oracle.com +Description: Ocfs2-tools looks at 'interface-revision' for versioning + information. Each logmask/ file controls a set of debug prints + and can be written into with the strings "allow", "deny", or + "off". Reading the file returns the current state. +Users: ocfs2-tools. It's sufficient to mail proposed changes to + ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/stable/procfs-audit_loginuid b/Documentation/ABI/stable/procfs-audit_loginuid new file mode 100644 index 000000000..cda405178 --- /dev/null +++ b/Documentation/ABI/stable/procfs-audit_loginuid @@ -0,0 +1,27 @@ +What: Audit Login UID +Date: 2005-02-01 +KernelVersion: 2.6.11-rc2 1e2d1492e178 ("[PATCH] audit: handle loginuid through proc") +Contact: linux-audit@redhat.com +Users: audit and login applications +Description: + The /proc/$pid/loginuid pseudofile is written to set and + read to get the audit login UID of process $pid as a + decimal unsigned int (%u, u32). If it is unset, + permissions are not needed to set it. The accessor must + have CAP_AUDIT_CONTROL in the initial user namespace to + write it if it has been set. It cannot be written again + if AUDIT_FEATURE_LOGINUID_IMMUTABLE is enabled. It + cannot be unset if AUDIT_FEATURE_ONLY_UNSET_LOGINUID is + enabled. + +What: Audit Login Session ID +Date: 2008-03-13 +KernelVersion: 2.6.25-rc7 1e0bd7550ea9 ("[PATCH] export sessionid alongside the loginuid in procfs") +Contact: linux-audit@redhat.com +Users: audit and login applications +Description: + The /proc/$pid/sessionid pseudofile is read to get the + audit login session ID of process $pid as a decimal + unsigned int (%u, u32). It is set automatically, + serially assigned with each new login. + diff --git a/Documentation/ABI/stable/syscalls b/Documentation/ABI/stable/syscalls new file mode 100644 index 000000000..c3ae3e7d6 --- /dev/null +++ b/Documentation/ABI/stable/syscalls @@ -0,0 +1,10 @@ +What: The kernel syscall interface +Description: + This interface matches much of the POSIX interface and is based + on it and other Unix based interfaces. It will only be added to + over time, and not have things removed from it. + + Note that this interface is different for every architecture + that Linux supports. Please see the architecture-specific + documentation for details on the syscall numbers that are to be + mapped to each syscall. diff --git a/Documentation/ABI/stable/sysfs-acpi-pmprofile b/Documentation/ABI/stable/sysfs-acpi-pmprofile new file mode 100644 index 000000000..2d6314f0e --- /dev/null +++ b/Documentation/ABI/stable/sysfs-acpi-pmprofile @@ -0,0 +1,26 @@ +What: /sys/firmware/acpi/pm_profile +Date: 03-Nov-2011 +KernelVersion: v3.2 +Contact: linux-acpi@vger.kernel.org +Description: The ACPI pm_profile sysfs interface exports the platform + power management (and performance) requirement expectations + as provided by BIOS. The integer value is directly passed as + retrieved from the FADT ACPI table. + +Values: For possible values see ACPI specification: + 5.2.9 Fixed ACPI Description Table (FADT) + Field: Preferred_PM_Profile + + Currently these values are defined by spec: + + == ================= + 0 Unspecified + 1 Desktop + 2 Mobile + 3 Workstation + 4 Enterprise Server + 5 SOHO Server + 6 Appliance PC + 7 Performance Server + >7 Reserved + == ================= diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block new file mode 100644 index 000000000..cd14ecb3c --- /dev/null +++ b/Documentation/ABI/stable/sysfs-block @@ -0,0 +1,734 @@ +What: /sys/block//alignment_offset +Date: April 2009 +Contact: Martin K. Petersen +Description: + Storage devices may report a physical block size that is + bigger than the logical block size (for instance a drive + with 4KB physical sectors exposing 512-byte logical + blocks to the operating system). This parameter + indicates how many bytes the beginning of the device is + offset from the disk's natural alignment. + + +What: /sys/block//discard_alignment +Date: May 2011 +Contact: Martin K. Petersen +Description: + Devices that support discard functionality may + internally allocate space in units that are bigger than + the exported logical block size. The discard_alignment + parameter indicates how many bytes the beginning of the + device is offset from the internal allocation unit's + natural alignment. + + +What: /sys/block//diskseq +Date: February 2021 +Contact: Matteo Croce +Description: + The /sys/block//diskseq files reports the disk + sequence number, which is a monotonically increasing + number assigned to every drive. + Some devices, like the loop device, refresh such number + every time the backing file is changed. + The value type is 64 bit unsigned. + + +What: /sys/block//inflight +Date: October 2009 +Contact: Jens Axboe , Nikanth Karthikesan +Description: + Reports the number of I/O requests currently in progress + (pending / in flight) in a device driver. This can be less + than the number of requests queued in the block device queue. + The report contains 2 fields: one for read requests + and one for write requests. + The value type is unsigned int. + Cf. Documentation/block/stat.rst which contains a single value for + requests in flight. + This is related to /sys/block//queue/nr_requests + and for SCSI device also its queue_depth. + + +What: /sys/block//integrity/device_is_integrity_capable +Date: July 2014 +Contact: Martin K. Petersen +Description: + Indicates whether a storage device is capable of storing + integrity metadata. Set if the device is T10 PI-capable. + + +What: /sys/block//integrity/format +Date: June 2008 +Contact: Martin K. Petersen +Description: + Metadata format for integrity capable block device. + E.g. T10-DIF-TYPE1-CRC. + + +What: /sys/block//integrity/protection_interval_bytes +Date: July 2015 +Contact: Martin K. Petersen +Description: + Describes the number of data bytes which are protected + by one integrity tuple. Typically the device's logical + block size. + + +What: /sys/block//integrity/read_verify +Date: June 2008 +Contact: Martin K. Petersen +Description: + Indicates whether the block layer should verify the + integrity of read requests serviced by devices that + support sending integrity metadata. + + +What: /sys/block//integrity/tag_size +Date: June 2008 +Contact: Martin K. Petersen +Description: + Number of bytes of integrity tag space available per + 512 bytes of data. + + +What: /sys/block//integrity/write_generate +Date: June 2008 +Contact: Martin K. Petersen +Description: + Indicates whether the block layer should automatically + generate checksums for write requests bound for + devices that support receiving integrity metadata. + + +What: /sys/block///alignment_offset +Date: April 2009 +Contact: Martin K. Petersen +Description: + Storage devices may report a physical block size that is + bigger than the logical block size (for instance a drive + with 4KB physical sectors exposing 512-byte logical + blocks to the operating system). This parameter + indicates how many bytes the beginning of the partition + is offset from the disk's natural alignment. + + +What: /sys/block///discard_alignment +Date: May 2011 +Contact: Martin K. Petersen +Description: + Devices that support discard functionality may + internally allocate space in units that are bigger than + the exported logical block size. The discard_alignment + parameter indicates how many bytes the beginning of the + partition is offset from the internal allocation unit's + natural alignment. + + +What: /sys/block///stat +Date: February 2008 +Contact: Jerome Marchand +Description: + The /sys/block///stat files display the + I/O statistics of partition . The format is the + same as the format of /sys/block//stat. + + +What: /sys/block//queue/add_random +Date: June 2010 +Contact: linux-block@vger.kernel.org +Description: + [RW] This file allows to turn off the disk entropy contribution. + Default value of this file is '1'(on). + + +What: /sys/block//queue/chunk_sectors +Date: September 2016 +Contact: Hannes Reinecke +Description: + [RO] chunk_sectors has different meaning depending on the type + of the disk. For a RAID device (dm-raid), chunk_sectors + indicates the size in 512B sectors of the RAID volume stripe + segment. For a zoned block device, either host-aware or + host-managed, chunk_sectors indicates the size in 512B sectors + of the zones of the device, with the eventual exception of the + last zone of the device which may be smaller. + + +What: /sys/block//queue/crypto/ +Date: February 2022 +Contact: linux-block@vger.kernel.org +Description: + The presence of this subdirectory of /sys/block//queue/ + indicates that the device supports inline encryption. This + subdirectory contains files which describe the inline encryption + capabilities of the device. For more information about inline + encryption, refer to Documentation/block/inline-encryption.rst. + + +What: /sys/block//queue/crypto/max_dun_bits +Date: February 2022 +Contact: linux-block@vger.kernel.org +Description: + [RO] This file shows the maximum length, in bits, of data unit + numbers accepted by the device in inline encryption requests. + + +What: /sys/block//queue/crypto/modes/ +Date: February 2022 +Contact: linux-block@vger.kernel.org +Description: + [RO] For each crypto mode (i.e., encryption/decryption + algorithm) the device supports with inline encryption, a file + will exist at this location. It will contain a hexadecimal + number that is a bitmask of the supported data unit sizes, in + bytes, for that crypto mode. + + Currently, the crypto modes that may be supported are: + + * AES-256-XTS + * AES-128-CBC-ESSIV + * Adiantum + + For example, if a device supports AES-256-XTS inline encryption + with data unit sizes of 512 and 4096 bytes, the file + /sys/block//queue/crypto/modes/AES-256-XTS will exist and + will contain "0x1200". + + +What: /sys/block//queue/crypto/num_keyslots +Date: February 2022 +Contact: linux-block@vger.kernel.org +Description: + [RO] This file shows the number of keyslots the device has for + use with inline encryption. + + +What: /sys/block//queue/dax +Date: June 2016 +Contact: linux-block@vger.kernel.org +Description: + [RO] This file indicates whether the device supports Direct + Access (DAX), used by CPU-addressable storage to bypass the + pagecache. It shows '1' if true, '0' if not. + + +What: /sys/block//queue/discard_granularity +Date: May 2011 +Contact: Martin K. Petersen +Description: + [RO] Devices that support discard functionality may internally + allocate space using units that are bigger than the logical + block size. The discard_granularity parameter indicates the size + of the internal allocation unit in bytes if reported by the + device. Otherwise the discard_granularity will be set to match + the device's physical block size. A discard_granularity of 0 + means that the device does not support discard functionality. + + +What: /sys/block//queue/discard_max_bytes +Date: May 2011 +Contact: Martin K. Petersen +Description: + [RW] While discard_max_hw_bytes is the hardware limit for the + device, this setting is the software limit. Some devices exhibit + large latencies when large discards are issued, setting this + value lower will make Linux issue smaller discards and + potentially help reduce latencies induced by large discard + operations. + + +What: /sys/block//queue/discard_max_hw_bytes +Date: July 2015 +Contact: linux-block@vger.kernel.org +Description: + [RO] Devices that support discard functionality may have + internal limits on the number of bytes that can be trimmed or + unmapped in a single operation. The `discard_max_hw_bytes` + parameter is set by the device driver to the maximum number of + bytes that can be discarded in a single operation. Discard + requests issued to the device must not exceed this limit. A + `discard_max_hw_bytes` value of 0 means that the device does not + support discard functionality. + + +What: /sys/block//queue/discard_zeroes_data +Date: May 2011 +Contact: Martin K. Petersen +Description: + [RO] Will always return 0. Don't rely on any specific behavior + for discards, and don't read this file. + + +What: /sys/block//queue/dma_alignment +Date: May 2022 +Contact: linux-block@vger.kernel.org +Description: + Reports the alignment that user space addresses must have to be + used for raw block device access with O_DIRECT and other driver + specific passthrough mechanisms. + + +What: /sys/block//queue/fua +Date: May 2018 +Contact: linux-block@vger.kernel.org +Description: + [RO] Whether or not the block driver supports the FUA flag for + write requests. FUA stands for Force Unit Access. If the FUA + flag is set that means that write requests must bypass the + volatile cache of the storage device. + + +What: /sys/block//queue/hw_sector_size +Date: January 2008 +Contact: linux-block@vger.kernel.org +Description: + [RO] This is the hardware sector size of the device, in bytes. + + +What: /sys/block//queue/independent_access_ranges/ +Date: October 2021 +Contact: linux-block@vger.kernel.org +Description: + [RO] The presence of this sub-directory of the + /sys/block/xxx/queue/ directory indicates that the device is + capable of executing requests targeting different sector ranges + in parallel. For instance, single LUN multi-actuator hard-disks + will have an independent_access_ranges directory if the device + correctly advertizes the sector ranges of its actuators. + + The independent_access_ranges directory contains one directory + per access range, with each range described using the sector + (RO) attribute file to indicate the first sector of the range + and the nr_sectors (RO) attribute file to indicate the total + number of sectors in the range starting from the first sector of + the range. For example, a dual-actuator hard-disk will have the + following independent_access_ranges entries.:: + + $ tree /sys/block//queue/independent_access_ranges/ + /sys/block//queue/independent_access_ranges/ + |-- 0 + | |-- nr_sectors + | `-- sector + `-- 1 + |-- nr_sectors + `-- sector + + The sector and nr_sectors attributes use 512B sector unit, + regardless of the actual block size of the device. Independent + access ranges do not overlap and include all sectors within the + device capacity. The access ranges are numbered in increasing + order of the range start sector, that is, the sector attribute + of range 0 always has the value 0. + + +What: /sys/block//queue/io_poll +Date: November 2015 +Contact: linux-block@vger.kernel.org +Description: + [RW] When read, this file shows whether polling is enabled (1) + or disabled (0). Writing '0' to this file will disable polling + for this device. Writing any non-zero value will enable this + feature. + + +What: /sys/block//queue/io_poll_delay +Date: November 2016 +Contact: linux-block@vger.kernel.org +Description: + [RW] If polling is enabled, this controls what kind of polling + will be performed. It defaults to -1, which is classic polling. + In this mode, the CPU will repeatedly ask for completions + without giving up any time. If set to 0, a hybrid polling mode + is used, where the kernel will attempt to make an educated guess + at when the IO will complete. Based on this guess, the kernel + will put the process issuing IO to sleep for an amount of time, + before entering a classic poll loop. This mode might be a little + slower than pure classic polling, but it will be more efficient. + If set to a value larger than 0, the kernel will put the process + issuing IO to sleep for this amount of microseconds before + entering classic polling. + + +What: /sys/block//queue/io_timeout +Date: November 2018 +Contact: Weiping Zhang +Description: + [RW] io_timeout is the request timeout in milliseconds. If a + request does not complete in this time then the block driver + timeout handler is invoked. That timeout handler can decide to + retry the request, to fail it or to start a device recovery + strategy. + + +What: /sys/block//queue/iostats +Date: January 2009 +Contact: linux-block@vger.kernel.org +Description: + [RW] This file is used to control (on/off) the iostats + accounting of the disk. + + +What: /sys/block//queue/logical_block_size +Date: May 2009 +Contact: Martin K. Petersen +Description: + [RO] This is the smallest unit the storage device can address. + It is typically 512 bytes. + + +What: /sys/block//queue/max_active_zones +Date: July 2020 +Contact: Niklas Cassel +Description: + [RO] For zoned block devices (zoned attribute indicating + "host-managed" or "host-aware"), the sum of zones belonging to + any of the zone states: EXPLICIT OPEN, IMPLICIT OPEN or CLOSED, + is limited by this value. If this value is 0, there is no limit. + + If the host attempts to exceed this limit, the driver should + report this error with BLK_STS_ZONE_ACTIVE_RESOURCE, which user + space may see as the EOVERFLOW errno. + + +What: /sys/block//queue/max_discard_segments +Date: February 2017 +Contact: linux-block@vger.kernel.org +Description: + [RO] The maximum number of DMA scatter/gather entries in a + discard request. + + +What: /sys/block//queue/max_hw_sectors_kb +Date: September 2004 +Contact: linux-block@vger.kernel.org +Description: + [RO] This is the maximum number of kilobytes supported in a + single data transfer. + + +What: /sys/block//queue/max_integrity_segments +Date: September 2010 +Contact: linux-block@vger.kernel.org +Description: + [RO] Maximum number of elements in a DMA scatter/gather list + with integrity data that will be submitted by the block layer + core to the associated block driver. + + +What: /sys/block//queue/max_open_zones +Date: July 2020 +Contact: Niklas Cassel +Description: + [RO] For zoned block devices (zoned attribute indicating + "host-managed" or "host-aware"), the sum of zones belonging to + any of the zone states: EXPLICIT OPEN or IMPLICIT OPEN, is + limited by this value. If this value is 0, there is no limit. + + +What: /sys/block//queue/max_sectors_kb +Date: September 2004 +Contact: linux-block@vger.kernel.org +Description: + [RW] This is the maximum number of kilobytes that the block + layer will allow for a filesystem request. Must be smaller than + or equal to the maximum size allowed by the hardware. + + +What: /sys/block//queue/max_segment_size +Date: March 2010 +Contact: linux-block@vger.kernel.org +Description: + [RO] Maximum size in bytes of a single element in a DMA + scatter/gather list. + + +What: /sys/block//queue/max_segments +Date: March 2010 +Contact: linux-block@vger.kernel.org +Description: + [RO] Maximum number of elements in a DMA scatter/gather list + that is submitted to the associated block driver. + + +What: /sys/block//queue/minimum_io_size +Date: April 2009 +Contact: Martin K. Petersen +Description: + [RO] Storage devices may report a granularity or preferred + minimum I/O size which is the smallest request the device can + perform without incurring a performance penalty. For disk + drives this is often the physical block size. For RAID arrays + it is often the stripe chunk size. A properly aligned multiple + of minimum_io_size is the preferred request size for workloads + where a high number of I/O operations is desired. + + +What: /sys/block//queue/nomerges +Date: January 2010 +Contact: linux-block@vger.kernel.org +Description: + [RW] Standard I/O elevator operations include attempts to merge + contiguous I/Os. For known random I/O loads these attempts will + always fail and result in extra cycles being spent in the + kernel. This allows one to turn off this behavior on one of two + ways: When set to 1, complex merge checks are disabled, but the + simple one-shot merges with the previous I/O request are + enabled. When set to 2, all merge tries are disabled. The + default value is 0 - which enables all types of merge tries. + + +What: /sys/block//queue/nr_requests +Date: July 2003 +Contact: linux-block@vger.kernel.org +Description: + [RW] This controls how many requests may be allocated in the + block layer for read or write requests. Note that the total + allocated number may be twice this amount, since it applies only + to reads or writes (not the accumulated sum). + + To avoid priority inversion through request starvation, a + request queue maintains a separate request pool per each cgroup + when CONFIG_BLK_CGROUP is enabled, and this parameter applies to + each such per-block-cgroup request pool. IOW, if there are N + block cgroups, each request queue may have up to N request + pools, each independently regulated by nr_requests. + + +What: /sys/block//queue/nr_zones +Date: November 2018 +Contact: Damien Le Moal +Description: + [RO] nr_zones indicates the total number of zones of a zoned + block device ("host-aware" or "host-managed" zone model). For + regular block devices, the value is always 0. + + +What: /sys/block//queue/optimal_io_size +Date: April 2009 +Contact: Martin K. Petersen +Description: + [RO] Storage devices may report an optimal I/O size, which is + the device's preferred unit for sustained I/O. This is rarely + reported for disk drives. For RAID arrays it is usually the + stripe width or the internal track size. A properly aligned + multiple of optimal_io_size is the preferred request size for + workloads where sustained throughput is desired. If no optimal + I/O size is reported this file contains 0. + + +What: /sys/block//queue/physical_block_size +Date: May 2009 +Contact: Martin K. Petersen +Description: + [RO] This is the smallest unit a physical storage device can + write atomically. It is usually the same as the logical block + size but may be bigger. One example is SATA drives with 4KB + sectors that expose a 512-byte logical block size to the + operating system. For stacked block devices the + physical_block_size variable contains the maximum + physical_block_size of the component devices. + + +What: /sys/block//queue/read_ahead_kb +Date: May 2004 +Contact: linux-block@vger.kernel.org +Description: + [RW] Maximum number of kilobytes to read-ahead for filesystems + on this block device. + + +What: /sys/block//queue/rotational +Date: January 2009 +Contact: linux-block@vger.kernel.org +Description: + [RW] This file is used to stat if the device is of rotational + type or non-rotational type. + + +What: /sys/block//queue/rq_affinity +Date: September 2008 +Contact: linux-block@vger.kernel.org +Description: + [RW] If this option is '1', the block layer will migrate request + completions to the cpu "group" that originally submitted the + request. For some workloads this provides a significant + reduction in CPU cycles due to caching effects. + + For storage configurations that need to maximize distribution of + completion processing setting this option to '2' forces the + completion to run on the requesting cpu (bypassing the "group" + aggregation logic). + + +What: /sys/block//queue/scheduler +Date: October 2004 +Contact: linux-block@vger.kernel.org +Description: + [RW] When read, this file will display the current and available + IO schedulers for this block device. The currently active IO + scheduler will be enclosed in [] brackets. Writing an IO + scheduler name to this file will switch control of this block + device to that new IO scheduler. Note that writing an IO + scheduler name to this file will attempt to load that IO + scheduler module, if it isn't already present in the system. + + +What: /sys/block//queue/stable_writes +Date: September 2020 +Contact: linux-block@vger.kernel.org +Description: + [RW] This file will contain '1' if memory must not be modified + while it is being used in a write request to this device. When + this is the case and the kernel is performing writeback of a + page, the kernel will wait for writeback to complete before + allowing the page to be modified again, rather than allowing + immediate modification as is normally the case. This + restriction arises when the device accesses the memory multiple + times where the same data must be seen every time -- for + example, once to calculate a checksum and once to actually write + the data. If no such restriction exists, this file will contain + '0'. This file is writable for testing purposes. + + +What: /sys/block//queue/throttle_sample_time +Date: March 2017 +Contact: linux-block@vger.kernel.org +Description: + [RW] This is the time window that blk-throttle samples data, in + millisecond. blk-throttle makes decision based on the + samplings. Lower time means cgroups have more smooth throughput, + but higher CPU overhead. This exists only when + CONFIG_BLK_DEV_THROTTLING_LOW is enabled. + + +What: /sys/block//queue/virt_boundary_mask +Date: April 2021 +Contact: linux-block@vger.kernel.org +Description: + [RO] This file shows the I/O segment memory alignment mask for + the block device. I/O requests to this device will be split + between segments wherever either the memory address of the end + of the previous segment or the memory address of the beginning + of the current segment is not aligned to virt_boundary_mask + 1 + bytes. + + +What: /sys/block//queue/wbt_lat_usec +Date: November 2016 +Contact: linux-block@vger.kernel.org +Description: + [RW] If the device is registered for writeback throttling, then + this file shows the target minimum read latency. If this latency + is exceeded in a given window of time (see wb_window_usec), then + the writeback throttling will start scaling back writes. Writing + a value of '0' to this file disables the feature. Writing a + value of '-1' to this file resets the value to the default + setting. + + +What: /sys/block//queue/write_cache +Date: April 2016 +Contact: linux-block@vger.kernel.org +Description: + [RW] When read, this file will display whether the device has + write back caching enabled or not. It will return "write back" + for the former case, and "write through" for the latter. Writing + to this file can change the kernels view of the device, but it + doesn't alter the device state. This means that it might not be + safe to toggle the setting from "write back" to "write through", + since that will also eliminate cache flushes issued by the + kernel. + + +What: /sys/block//queue/write_same_max_bytes +Date: January 2012 +Contact: Martin K. Petersen +Description: + [RO] Some devices support a write same operation in which a + single data block can be written to a range of several + contiguous blocks on storage. This can be used to wipe areas on + disk or to initialize drives in a RAID configuration. + write_same_max_bytes indicates how many bytes can be written in + a single write same command. If write_same_max_bytes is 0, write + same is not supported by the device. + + +What: /sys/block//queue/write_zeroes_max_bytes +Date: November 2016 +Contact: Chaitanya Kulkarni +Description: + [RO] Devices that support write zeroes operation in which a + single request can be issued to zero out the range of contiguous + blocks on storage without having any payload in the request. + This can be used to optimize writing zeroes to the devices. + write_zeroes_max_bytes indicates how many bytes can be written + in a single write zeroes command. If write_zeroes_max_bytes is + 0, write zeroes is not supported by the device. + + +What: /sys/block//queue/zone_append_max_bytes +Date: May 2020 +Contact: linux-block@vger.kernel.org +Description: + [RO] This is the maximum number of bytes that can be written to + a sequential zone of a zoned block device using a zone append + write operation (REQ_OP_ZONE_APPEND). This value is always 0 for + regular block devices. + + +What: /sys/block//queue/zone_write_granularity +Date: January 2021 +Contact: linux-block@vger.kernel.org +Description: + [RO] This indicates the alignment constraint, in bytes, for + write operations in sequential zones of zoned block devices + (devices with a zoned attributed that reports "host-managed" or + "host-aware"). This value is always 0 for regular block devices. + + +What: /sys/block//queue/zoned +Date: September 2016 +Contact: Damien Le Moal +Description: + [RO] zoned indicates if the device is a zoned block device and + the zone model of the device if it is indeed zoned. The + possible values indicated by zoned are "none" for regular block + devices and "host-aware" or "host-managed" for zoned block + devices. The characteristics of host-aware and host-managed + zoned block devices are described in the ZBC (Zoned Block + Commands) and ZAC (Zoned Device ATA Command Set) standards. + These standards also define the "drive-managed" zone model. + However, since drive-managed zoned block devices do not support + zone commands, they will be treated as regular block devices and + zoned will report "none". + + +What: /sys/block//stat +Date: February 2008 +Contact: Jerome Marchand +Description: + The /sys/block//stat files displays the I/O + statistics of disk . They contain 11 fields: + + == ============================================== + 1 reads completed successfully + 2 reads merged + 3 sectors read + 4 time spent reading (ms) + 5 writes completed + 6 writes merged + 7 sectors written + 8 time spent writing (ms) + 9 I/Os currently in progress + 10 time spent doing I/Os (ms) + 11 weighted time spent doing I/Os (ms) + 12 discards completed + 13 discards merged + 14 sectors discarded + 15 time spent discarding (ms) + 16 flush requests completed + 17 time spent flushing (ms) + == ============================================== + + For more details refer Documentation/admin-guide/iostats.rst diff --git a/Documentation/ABI/stable/sysfs-bus-firewire b/Documentation/ABI/stable/sysfs-bus-firewire new file mode 100644 index 000000000..9ac9eddb8 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-firewire @@ -0,0 +1,136 @@ +What: /sys/bus/firewire/devices/fw[0-9]+/ +Date: May 2007 +KernelVersion: 2.6.22 +Contact: linux1394-devel@lists.sourceforge.net +Description: + IEEE 1394 node device attributes. + Read-only. Mutable during the node device's lifetime. + See IEEE 1212 for semantic definitions. + + config_rom + Contents of the Configuration ROM register. + Binary attribute; an array of host-endian u32. + + guid + The node's EUI-64 in the bus information block of + Configuration ROM. + Hexadecimal string representation of an u64. + + +What: /sys/bus/firewire/devices/fw[0-9]+/units +Date: June 2009 +KernelVersion: 2.6.31 +Contact: linux1394-devel@lists.sourceforge.net +Description: + IEEE 1394 node device attribute. + Read-only. Mutable during the node device's lifetime. + See IEEE 1212 for semantic definitions. + + units + Summary of all units present in an IEEE 1394 node. + Contains space-separated tuples of specifier_id and + version of each unit present in the node. Specifier_id + and version are hexadecimal string representations of + u24 of the respective unit directory entries. + Specifier_id and version within each tuple are separated + by a colon. + +Users: udev rules to set ownership and access permissions or ACLs of + /dev/fw[0-9]+ character device files + + +What: /sys/bus/firewire/devices/fw[0-9]+/is_local +Date: July 2012 +KernelVersion: 3.6 +Contact: linux1394-devel@lists.sourceforge.net +Description: + IEEE 1394 node device attribute. + Read-only and immutable. +Values: 1: The sysfs entry represents a local node (a controller card). + + 0: The sysfs entry represents a remote node. + + +What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ +Date: May 2007 +KernelVersion: 2.6.22 +Contact: linux1394-devel@lists.sourceforge.net +Description: + IEEE 1394 unit device attributes. + Read-only. Immutable during the unit device's lifetime. + See IEEE 1212 for semantic definitions. + + modalias + Same as MODALIAS in the uevent at device creation. + + rom_index + Offset of the unit directory within the parent device's + (node device's) Configuration ROM, in quadlets. + Decimal string representation. + + +What: /sys/bus/firewire/devices/*/ +Date: May 2007 +KernelVersion: 2.6.22 +Contact: linux1394-devel@lists.sourceforge.net +Description: + Attributes common to IEEE 1394 node devices and unit devices. + Read-only. Mutable during the node device's lifetime. + Immutable during the unit device's lifetime. + See IEEE 1212 for semantic definitions. + + These attributes are only created if the root directory of an + IEEE 1394 node or the unit directory of an IEEE 1394 unit + actually contains according entries. + + hardware_version + Hexadecimal string representation of an u24. + + hardware_version_name + Contents of a respective textual descriptor leaf. + + model + Hexadecimal string representation of an u24. + + model_name + Contents of a respective textual descriptor leaf. + + specifier_id + Hexadecimal string representation of an u24. + Mandatory in unit directories according to IEEE 1212. + + vendor + Hexadecimal string representation of an u24. + Mandatory in the root directory according to IEEE 1212. + + vendor_name + Contents of a respective textual descriptor leaf. + + version + Hexadecimal string representation of an u24. + Mandatory in unit directories according to IEEE 1212. + + +What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id + formerly + /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id +Date: Feb 2004 +KernelVersion: 2.6.4 +Contact: linux1394-devel@lists.sourceforge.net +Description: + SCSI target port identifier and logical unit identifier of a + logical unit of an SBP-2 target. The identifiers are specified + in SAM-2...SAM-4 annex A. They are persistent and world-wide + unique properties the SBP-2 attached target. + + Read-only attribute, immutable during the target's lifetime. + Format, as exposed by firewire-sbp2 since 2.6.22, May 2007: + Colon-separated hexadecimal string representations of + + u64 EUI-64 : u24 directory_ID : u16 LUN + + without 0x prefixes, without whitespace. The former sbp2 driver + (removed in 2.6.37 after being superseded by firewire-sbp2) used + a somewhat shorter format which was not as close to SAM. + +Users: udev rules to create /dev/disk/by-id/ symlinks diff --git a/Documentation/ABI/stable/sysfs-bus-fsl-mc b/Documentation/ABI/stable/sysfs-bus-fsl-mc new file mode 100644 index 000000000..58f06c7ee --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-fsl-mc @@ -0,0 +1,19 @@ +What: /sys/bus/fsl-mc/rescan +Date: January 2021 +KernelVersion: 5.12 +Contact: Ioana Ciornei +Description: Writing a non-zero value to this attribute will + force a rescan of fsl-mc bus in the system and + synchronize the objects under fsl-mc bus and the + Management Complex firmware. +Users: Userspace drivers and management tools + +What: /sys/bus/fsl-mc/autorescan +Date: January 2021 +KernelVersion: 5.12 +Contact: Ioana Ciornei +Description: Writing a zero value to this attribute will + disable the DPRC IRQs on which automatic rescan + of the fsl-mc bus is performed. A non-zero value + will enable the DPRC IRQs. +Users: Userspace drivers and management tools diff --git a/Documentation/ABI/stable/sysfs-bus-mhi b/Documentation/ABI/stable/sysfs-bus-mhi new file mode 100644 index 000000000..96ccc3385 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-mhi @@ -0,0 +1,31 @@ +What: /sys/bus/mhi/devices/.../serialnumber +Date: Sept 2020 +KernelVersion: 5.10 +Contact: Bhaumik Bhatt +Description: The file holds the serial number of the client device obtained + using a BHI (Boot Host Interface) register read after at least + one attempt to power up the device has been done. If read + without having the device power on at least once, the file will + read all 0's. +Users: Any userspace application or clients interested in device info. + +What: /sys/bus/mhi/devices/.../oem_pk_hash +Date: Sept 2020 +KernelVersion: 5.10 +Contact: Bhaumik Bhatt +Description: The file holds the OEM PK Hash value of the endpoint device + obtained using a BHI (Boot Host Interface) register read after + at least one attempt to power up the device has been done. If + read without having the device power on at least once, the file + will read all 0's. +Users: Any userspace application or clients interested in device info. + +What: /sys/bus/mhi/devices/.../soc_reset +Date: April 2022 +KernelVersion: 5.19 +Contact: mhi@lists.linux.dev +Description: Initiates a SoC reset on the MHI controller. A SoC reset is + a reset of last resort, and will require a complete re-init. + This can be useful as a method of recovery if the device is + non-responsive, or as a means of loading new firmware as a + system administration task. diff --git a/Documentation/ABI/stable/sysfs-bus-nvmem b/Documentation/ABI/stable/sysfs-bus-nvmem new file mode 100644 index 000000000..c399323f3 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-nvmem @@ -0,0 +1,22 @@ +What: /sys/bus/nvmem/devices/.../nvmem +Date: July 2015 +KernelVersion: 4.2 +Contact: Srinivas Kandagatla +Description: + This file allows user to read/write the raw NVMEM contents. + Permissions for write to this file depends on the nvmem + provider configuration. + Note: This file is only present if CONFIG_NVMEM_SYSFS + is enabled + + ex:: + + hexdump /sys/bus/nvmem/devices/qfprom0/nvmem + + 0000000 0000 0000 0000 0000 0000 0000 0000 0000 + * + 00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00 + 0000000 0000 0000 0000 0000 0000 0000 0000 0000 + ... + * + 0001000 diff --git a/Documentation/ABI/stable/sysfs-bus-usb b/Documentation/ABI/stable/sysfs-bus-usb new file mode 100644 index 000000000..cad4bc232 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-usb @@ -0,0 +1,142 @@ +What: /sys/bus/usb/devices/.../power/persist +Date: May 2007 +KernelVersion: 2.6.23 +Contact: Alan Stern +Description: + USB device directories can contain a file named power/persist. + The file holds a boolean value (0 or 1) indicating whether or + not the "USB-Persist" facility is enabled for the device. For + hubs this facility is always enabled and their device + directories will not contain this file. + + For more information, see Documentation/driver-api/usb/persist.rst. + +What: /sys/bus/usb/devices/.../power/autosuspend +Date: March 2007 +KernelVersion: 2.6.21 +Contact: Alan Stern +Description: + Each USB device directory will contain a file named + power/autosuspend. This file holds the time (in seconds) + the device must be idle before it will be autosuspended. + 0 means the device will be autosuspended as soon as + possible. Negative values will prevent the device from + being autosuspended at all, and writing a negative value + will resume the device if it is already suspended. + + The autosuspend delay for newly-created devices is set to + the value of the usbcore.autosuspend module parameter. + +What: /sys/bus/usb/device/.../power/connected_duration +Date: January 2008 +KernelVersion: 2.6.25 +Contact: Sarah Sharp +Description: + If CONFIG_PM is enabled, then this file is present. When read, + it returns the total time (in msec) that the USB device has been + connected to the machine. This file is read-only. +Users: + PowerTOP + https://01.org/powertop/ + +What: /sys/bus/usb/device/.../power/active_duration +Date: January 2008 +KernelVersion: 2.6.25 +Contact: Sarah Sharp +Description: + If CONFIG_PM is enabled, then this file is present. When read, + it returns the total time (in msec) that the USB device has been + active, i.e. not in a suspended state. This file is read-only. + + Tools can use this file and the connected_duration file to + compute the percentage of time that a device has been active. + For example:: + + echo $((100 * `cat active_duration` / `cat connected_duration`)) + + will give an integer percentage. Note that this does not + account for counter wrap. +Users: + PowerTOP + https://01.org/powertop/ + +What: /sys/bus/usb/devices/-...:-/supports_autosuspend +Date: January 2008 +KernelVersion: 2.6.27 +Contact: Sarah Sharp +Description: + When read, this file returns 1 if the interface driver + for this interface supports autosuspend. It also + returns 1 if no driver has claimed this interface, as an + unclaimed interface will not stop the device from being + autosuspended if all other interface drivers are idle. + The file returns 0 if autosuspend support has not been + added to the driver. +Users: + USB PM tool + git://git.moblin.org/users/sarah/usb-pm-tool/ + +What: /sys/bus/usb/device/.../avoid_reset_quirk +Date: December 2009 +Contact: Oliver Neukum +Description: + Writing 1 to this file tells the kernel that this + device will morph into another mode when it is reset. + Drivers will not use reset for error handling for + such devices. +Users: + usb_modeswitch + +What: /sys/bus/usb/devices/.../devnum +KernelVersion: since at least 2.6.18 +Description: + Device address on the USB bus. +Users: + libusb + +What: /sys/bus/usb/devices/.../bConfigurationValue +KernelVersion: since at least 2.6.18 +Description: + bConfigurationValue of the *active* configuration for the + device. Writing 0 or -1 to bConfigurationValue will reset the + active configuration (unconfigure the device). Writing + another value will change the active configuration. + + Note that some devices, in violation of the USB spec, have a + configuration with a value equal to 0. Writing 0 to + bConfigurationValue for these devices will install that + configuration, rather then unconfigure the device. + + Writing -1 will always unconfigure the device. +Users: + libusb + +What: /sys/bus/usb/devices/.../busnum +KernelVersion: 2.6.22 +Description: + Bus-number of the USB-bus the device is connected to. +Users: + libusb + +What: /sys/bus/usb/devices/.../descriptors +KernelVersion: 2.6.26 +Description: + Binary file containing cached descriptors of the device. The + binary data consists of the device descriptor followed by the + descriptors for each configuration of the device. + Note that the wTotalLength of the config descriptors can not + be trusted, as the device may have a smaller config descriptor + than it advertises. The bLength field of each (sub) descriptor + can be trusted, and can be used to seek forward one (sub) + descriptor at a time until the next config descriptor is found. + All descriptors read from this file are in bus-endian format +Users: + libusb + +What: /sys/bus/usb/devices/.../speed +KernelVersion: since at least 2.6.18 +Description: + Speed the device is connected with to the usb-host in + Mbit / second. IE one of 1.5 / 12 / 480 / 5000. +Users: + libusb diff --git a/Documentation/ABI/stable/sysfs-bus-vmbus b/Documentation/ABI/stable/sysfs-bus-vmbus new file mode 100644 index 000000000..3066feae1 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-vmbus @@ -0,0 +1,187 @@ +What: /sys/bus/vmbus/hibernation +Date: Jan 2021 +KernelVersion: 5.12 +Contact: Dexuan Cui +Description: Whether the host supports hibernation for the VM. +Users: Daemon that sets up swap partition/file for hibernation. + +What: /sys/bus/vmbus/devices//id +Date: Jul 2009 +KernelVersion: 2.6.31 +Contact: K. Y. Srinivasan +Description: The VMBus child_relid of the device's primary channel +Users: tools/hv/lsvmbus + +What: /sys/bus/vmbus/devices//class_id +Date: Jul 2009 +KernelVersion: 2.6.31 +Contact: K. Y. Srinivasan +Description: The VMBus interface type GUID of the device +Users: tools/hv/lsvmbus + +What: /sys/bus/vmbus/devices//device_id +Date: Jul 2009 +KernelVersion: 2.6.31 +Contact: K. Y. Srinivasan +Description: The VMBus interface instance GUID of the device +Users: tools/hv/lsvmbus + +What: /sys/bus/vmbus/devices//channel_vp_mapping +Date: Jul 2015 +KernelVersion: 4.2.0 +Contact: K. Y. Srinivasan +Description: The mapping of which primary/sub channels are bound to which + Virtual Processors. + Format: +Users: tools/hv/lsvmbus + +What: /sys/bus/vmbus/devices//device +Date: Dec. 2015 +KernelVersion: 4.5 +Contact: K. Y. Srinivasan +Description: The 16 bit device ID of the device +Users: tools/hv/lsvmbus and user level RDMA libraries + +What: /sys/bus/vmbus/devices//vendor +Date: Dec. 2015 +KernelVersion: 4.5 +Contact: K. Y. Srinivasan +Description: The 16 bit vendor ID of the device +Users: tools/hv/lsvmbus and user level RDMA libraries + +What: /sys/bus/vmbus/devices//numa_node +Date: Jul 2018 +KernelVersion: 4.19 +Contact: Stephen Hemminger +Description: This NUMA node to which the VMBUS device is + attached, or -1 if the node is unknown. + +What: /sys/bus/vmbus/devices//channels/ +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Directory for per-channel information + NN is the VMBUS relid associated with the channel. + +What: /sys/bus/vmbus/devices//channels//cpu +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: VCPU (sub)channel is affinitized to +Users: tools/hv/lsvmbus and other debugging tools + +What: /sys/bus/vmbus/devices//channels//in_mask +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Host to guest channel interrupt mask +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//latency +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Channel signaling latency. This file is available only for + performance critical channels (storage, network, etc.) that use + the monitor page mechanism. +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//out_mask +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Guest to host channel interrupt mask +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//pending +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Channel interrupt pending state. This file is available only for + performance critical channels (storage, network, etc.) that use + the monitor page mechanism. +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//read_avail +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Bytes available to read +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//write_avail +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Bytes available to write +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//events +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Number of times we have signaled the host +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//interrupts +Date: September. 2017 +KernelVersion: 4.14 +Contact: Stephen Hemminger +Description: Number of times we have taken an interrupt (incoming) +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//subchannel_id +Date: January. 2018 +KernelVersion: 4.16 +Contact: Stephen Hemminger +Description: Subchannel ID associated with VMBUS channel +Users: Debugging tools and userspace drivers + +What: /sys/bus/vmbus/devices//channels//monitor_id +Date: January. 2018 +KernelVersion: 4.16 +Contact: Stephen Hemminger +Description: Monitor bit associated with channel. This file is available only + for performance critical channels (storage, network, etc.) that + use the monitor page mechanism. +Users: Debugging tools and userspace drivers + +What: /sys/bus/vmbus/devices//channels//ring +Date: January. 2018 +KernelVersion: 4.16 +Contact: Stephen Hemminger +Description: Binary file created by uio_hv_generic for ring buffer +Users: Userspace drivers + +What: /sys/bus/vmbus/devices//channels//intr_in_full +Date: February 2019 +KernelVersion: 5.0 +Contact: Michael Kelley +Description: Number of guest to host interrupts caused by the inbound ring + buffer transitioning from full to not full while a packet is + waiting for buffer space to become available +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//intr_out_empty +Date: February 2019 +KernelVersion: 5.0 +Contact: Michael Kelley +Description: Number of guest to host interrupts caused by the outbound ring + buffer transitioning from empty to not empty +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//out_full_first +Date: February 2019 +KernelVersion: 5.0 +Contact: Michael Kelley +Description: Number of write operations that were the first to encounter an + outbound ring buffer full condition +Users: Debugging tools + +What: /sys/bus/vmbus/devices//channels//out_full_total +Date: February 2019 +KernelVersion: 5.0 +Contact: Michael Kelley +Description: Total number of write operations that encountered an outbound + ring buffer full condition +Users: Debugging tools diff --git a/Documentation/ABI/stable/sysfs-bus-w1 b/Documentation/ABI/stable/sysfs-bus-w1 new file mode 100644 index 000000000..5cd5e872b --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-w1 @@ -0,0 +1,12 @@ +What: /sys/bus/w1/devices/.../w1_master_timeout_us +Date: April 2015 +Contact: Dmitry Khromov +Description: Bus scanning interval, microseconds component. + Some of 1-Wire devices commonly associated with physical access + control systems are attached/generate presence for as short as + 100 ms - hence the tens-to-hundreds milliseconds scan intervals + are required. + + see Documentation/w1/w1-generic.rst for detailed information. +Users: any user space application which wants to know bus scanning + interval diff --git a/Documentation/ABI/stable/sysfs-bus-xen-backend b/Documentation/ABI/stable/sysfs-bus-xen-backend new file mode 100644 index 000000000..480a89edf --- /dev/null +++ b/Documentation/ABI/stable/sysfs-bus-xen-backend @@ -0,0 +1,84 @@ +What: /sys/bus/xen-backend/devices/*/devtype +Date: Feb 2009 +KernelVersion: 2.6.38 +Contact: Konrad Rzeszutek Wilk +Description: + The type of the device. e.g., one of: 'vbd' (block), + 'vif' (network), or 'vfb' (framebuffer). + +What: /sys/bus/xen-backend/devices/*/nodename +Date: Feb 2009 +KernelVersion: 2.6.38 +Contact: Konrad Rzeszutek Wilk +Description: + XenStore node (under /local/domain/NNN/) for this + backend device. + +What: /sys/bus/xen-backend/devices/vbd-*/physical_device +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + The major:minor number (in hexadecimal) of the + physical device providing the storage for this backend + block device. + +What: /sys/bus/xen-backend/devices/vbd-*/mode +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Whether the block device is read-only ('r') or + read-write ('w'). + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/f_req +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of flush requests from the frontend. + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/oo_req +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of requests delayed because the backend was too + busy processing previous requests. + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_req +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of read requests from the frontend. + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_sect +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of sectors read by the frontend. + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_req +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of write requests from the frontend. + +What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_sect +Date: April 2011 +KernelVersion: 3.0 +Contact: Konrad Rzeszutek Wilk +Description: + Number of sectors written by the frontend. + +What: /sys/bus/xen-backend/devices/*/state +Date: August 2018 +KernelVersion: 4.19 +Contact: Joe Jin +Description: + The state of the device. One of: 'Unknown', + 'Initialising', 'Initialised', 'Connected', 'Closing', + 'Closed', 'Reconfiguring', 'Reconfigured'. diff --git a/Documentation/ABI/stable/sysfs-class-backlight b/Documentation/ABI/stable/sysfs-class-backlight new file mode 100644 index 000000000..023fb5264 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-backlight @@ -0,0 +1,57 @@ +What: /sys/class/backlight//bl_power +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Control BACKLIGHT power, values are FB_BLANK_* from fb.h + + - FB_BLANK_UNBLANK (0) : power on. + - FB_BLANK_POWERDOWN (4) : power off +Users: HAL + +What: /sys/class/backlight//brightness +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Control the brightness for this . Values + are between 0 and max_brightness. This file will also + show the brightness level stored in the driver, which + may not be the actual brightness (see actual_brightness). +Users: HAL + +What: /sys/class/backlight//actual_brightness +Date: March 2006 +KernelVersion: 2.6.17 +Contact: Richard Purdie +Description: + Show the actual brightness by querying the hardware. +Users: HAL + +What: /sys/class/backlight//max_brightness +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Maximum brightness for . +Users: HAL + +What: /sys/class/backlight//type +Date: September 2010 +KernelVersion: 2.6.37 +Contact: Matthew Garrett +Description: + The type of interface controlled by . + "firmware": The driver uses a standard firmware interface + "platform": The driver uses a platform-specific interface + "raw": The driver controls hardware registers directly + + In the general case, when multiple backlight + interfaces are available for a single device, firmware + control should be preferred to platform control should + be preferred to raw control. Using a firmware + interface reduces the probability of confusion with + the hardware and the OS independently updating the + backlight state. Platform interfaces are mostly a + holdover from pre-standardisation of firmware + interfaces. diff --git a/Documentation/ABI/stable/sysfs-class-infiniband b/Documentation/ABI/stable/sysfs-class-infiniband new file mode 100644 index 000000000..ebf08c604 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-infiniband @@ -0,0 +1,784 @@ +sysfs interface common for all infiniband devices +------------------------------------------------- + +What: /sys/class/infiniband//node_type +What: /sys/class/infiniband//node_guid +What: /sys/class/infiniband//sys_image_guid +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + =============== =========================================== + node_type: (RO) Node type (CA, RNIC, usNIC, usNIC UDP, + switch or router) + + node_guid: (RO) Node GUID + + sys_image_guid: (RO) System image GUID + =============== =========================================== + + +What: /sys/class/infiniband//node_desc +Date: Feb, 2006 +KernelVersion: v2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: + (RW) Update the node description with information such as the + node's hostname, so that IB network management software can tie + its view to the real world. + + +What: /sys/class/infiniband//fw_ver +Date: Jun, 2016 +KernelVersion: v4.10 +Contact: linux-rdma@vger.kernel.org +Description: + (RO) Display firmware version + + +What: /sys/class/infiniband//ports//lid +What: /sys/class/infiniband//ports//rate +What: /sys/class/infiniband//ports//lid_mask_count +What: /sys/class/infiniband//ports//sm_sl +What: /sys/class/infiniband//ports//sm_lid +What: /sys/class/infiniband//ports//state +What: /sys/class/infiniband//ports//phys_state +What: /sys/class/infiniband//ports//cap_mask +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + + =============== =============================================== + lid: (RO) Port LID + + rate: (RO) Port data rate (active width * active + speed) + + lid_mask_count: (RO) Port LID mask count + + sm_sl: (RO) Subnet manager SL for port's subnet + + sm_lid: (RO) Subnet manager LID for port's subnet + + state: (RO) Port state (DOWN, INIT, ARMED, ACTIVE or + ACTIVE_DEFER) + + phys_state: (RO) Port physical state (Sleep, Polling, + LinkUp, etc) + + cap_mask: (RO) Port capability mask. 2 bits here are + settable- IsCommunicationManagementSupported + (set when CM module is loaded) and IsSM (set + via open of issmN file). + =============== =============================================== + + +What: /sys/class/infiniband//ports//link_layer +Date: Oct, 2010 +KernelVersion: v2.6.37 +Contact: linux-rdma@vger.kernel.org +Description: + (RO) Link layer type information (Infiniband or Ethernet type) + + +What: /sys/class/infiniband//ports//counters/symbol_error +What: /sys/class/infiniband//ports//counters/port_rcv_errors +What: /sys/class/infiniband//ports//counters/port_rcv_remote_physical_errors +What: /sys/class/infiniband//ports//counters/port_rcv_switch_relay_errors +What: /sys/class/infiniband//ports//counters/link_error_recovery +What: /sys/class/infiniband//ports//counters/port_xmit_constraint_errors +What: /sys/class/infiniband//ports//counters/port_rcv_contraint_errors +What: /sys/class/infiniband//ports//counters/local_link_integrity_errors +What: /sys/class/infiniband//ports//counters/excessive_buffer_overrun_errors +What: /sys/class/infiniband//ports//counters/port_xmit_data +What: /sys/class/infiniband//ports//counters/port_rcv_data +What: /sys/class/infiniband//ports//counters/port_xmit_packets +What: /sys/class/infiniband//ports//counters/port_rcv_packets +What: /sys/class/infiniband//ports//counters/unicast_rcv_packets +What: /sys/class/infiniband//ports//counters/unicast_xmit_packets +What: /sys/class/infiniband//ports//counters/multicast_rcv_packets +What: /sys/class/infiniband//ports//counters/multicast_xmit_packets +What: /sys/class/infiniband//ports//counters/link_downed +What: /sys/class/infiniband//ports//counters/port_xmit_discards +What: /sys/class/infiniband//ports//counters/VL15_dropped +What: /sys/class/infiniband//ports//counters/port_xmit_wait +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + **Errors info**: + + symbol_error: (RO) Total number of minor link errors detected on + one or more physical lanes. + + port_rcv_errors : (RO) Total number of packets containing an + error that were received on the port. + + port_rcv_remote_physical_errors : (RO) Total number of packets + marked with the EBP delimiter received on the port. + + port_rcv_switch_relay_errors : (RO) Total number of packets + received on the port that were discarded because they could not + be forwarded by the switch relay. + + link_error_recovery: (RO) Total number of times the Port + Training state machine has successfully completed the link error + recovery process. + + port_xmit_constraint_errors: (RO) Total number of packets not + transmitted from the switch physical port due to outbound raw + filtering or failing outbound partition or IP version check. + + port_rcv_constraint_errors: (RO) Total number of packets + received on the switch physical port that are discarded due to + inbound raw filtering or failing inbound partition or IP version + check. + + local_link_integrity_errors: (RO) The number of times that the + count of local physical errors exceeded the threshold specified + by LocalPhyErrors + + excessive_buffer_overrun_errors: (RO) This counter, indicates an + input buffer overrun. It indicates possible misconfiguration of + a port, either by the Subnet Manager (SM) or by user + intervention. It can also indicate hardware issues or extremely + poor link signal integrity + + **Data info**: + + port_xmit_data: (RO) Total number of data octets, divided by 4 + (lanes), transmitted on all VLs. This is 64 bit counter + + port_rcv_data: (RO) Total number of data octets, divided by 4 + (lanes), received on all VLs. This is 64 bit counter. + + port_xmit_packets: (RO) Total number of packets transmitted on + all VLs from this port. This may include packets with errors. + This is 64 bit counter. + + port_rcv_packets: (RO) Total number of packets (this may include + packets containing Errors. This is 64 bit counter. + + link_downed: (RO) Total number of times the Port Training state + machine has failed the link error recovery process and downed + the link. + + unicast_rcv_packets: (RO) Total number of unicast packets, + including unicast packets containing errors. + + unicast_xmit_packets: (RO) Total number of unicast packets + transmitted on all VLs from the port. This may include unicast + packets with errors. + + multicast_rcv_packets: (RO) Total number of multicast packets, + including multicast packets containing errors. + + multicast_xmit_packets: (RO) Total number of multicast packets + transmitted on all VLs from the port. This may include multicast + packets with errors. + + **Misc info**: + + port_xmit_discards: (RO) Total number of outbound packets + discarded by the port because the port is down or congested. + + VL15_dropped: (RO) Number of incoming VL15 packets dropped due + to resource limitations (e.g., lack of buffers) of the port. + + port_xmit_wait: (RO) The number of ticks during which the port + had data to transmit but no data was sent during the entire tick + (either because of insufficient credits or because of lack of + arbitration). + + Each of these files contains the corresponding value from the + port's Performance Management PortCounters attribute, as + described in the InfiniBand Architecture Specification. + + +What: /sys/class/infiniband//hw_counters/lifespan +What: /sys/class/infiniband//ports//hw_counters/lifespan +Date: May, 2016 +KernelVersion: 4.6 +Contact: linux-rdma@vger.kernel.org +Description: + The optional "hw_counters" subdirectory can be under either the + parent device or the port subdirectories or both. If present, + there are a list of counters provided by the hardware. They may + match some of the counters in the counters directory, but they + often include many other counters. In addition to the various + counters, there will be a file named "lifespan" that configures + how frequently the core should update the counters when they are + being accessed (counters are not updated if they are not being + accessed). The lifespan is in milliseconds and defaults to 10 + unless set to something else by the driver. Users may echo a + value between 0-10000 to the lifespan file to set the length + of time between updates in milliseconds. + + +What: /sys/class/infiniband//ports//gid_attrs/ndevs/ +Date: November 29, 2015 +KernelVersion: 4.4.0 +Contact: linux-rdma@vger.kernel.org +Description: The net-device's name associated with the GID resides + at index . + +What: /sys/class/infiniband//ports//gid_attrs/types/ +Date: November 29, 2015 +KernelVersion: 4.4.0 +Contact: linux-rdma@vger.kernel.org +Description: The RoCE type of the associated GID resides at index . + This could either be "IB/RoCE v1" for IB and RoCE v1 based GIDs + or "RoCE v2" for RoCE v2 based GIDs. + + +What: /sys/class/infiniband_mad/umad/ibdev +What: /sys/class/infiniband_mad/umad/port +What: /sys/class/infiniband_mad/issm/ibdev +What: /sys/class/infiniband_mad/issm/port +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + Each port of each InfiniBand device has a "umad" device and an + "issm" device attached. For example, a two-port HCA will have + two umad devices and two issm devices, while a switch will have + one device of each type (for switch port 0). + + ======= ===================================== + ibdev: (RO) Show Infiniband (IB) device name + + port: (RO) Display port number + ======= ===================================== + + +What: /sys/class/infiniband_mad/abi_version +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + (RO) Value is incremented if any changes are made that break + userspace ABI compatibility of umad & issm devices. + + +What: /sys/class/infiniband_verbs/uverbs/ibdev +What: /sys/class/infiniband_verbs/uverbs/abi_version +Date: Sept, 2005 +KernelVersion: v2.6.14 +Contact: linux-rdma@vger.kernel.org +Description: + =============== =========================================== + ibdev: (RO) Display Infiniband (IB) device name + + abi_version: (RO) Show ABI version of IB device specific + interfaces. + =============== =========================================== + + +What: /sys/class/infiniband_verbs/abi_version +Date: Sep, 2005 +KernelVersion: v2.6.14 +Contact: linux-rdma@vger.kernel.org +Description: + (RO) Value is incremented if any changes are made that break + userspace ABI compatibility of uverbs devices. + + +sysfs interface for Mellanox IB HCA low-level driver (mthca) +------------------------------------------------------------ + +What: /sys/class/infiniband/mthcaX/hw_rev +What: /sys/class/infiniband/mthcaX/hca_type +What: /sys/class/infiniband/mthcaX/board_id +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: linux-rdma@vger.kernel.org +Description: + =============== ================================================ + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Host Channel Adapter type: MT23108, MT25208 + (MT23108 compat mode), MT25208 or MT25204 + + board_id: (RO) Manufacturing board ID + =============== ================================================ + + +sysfs interface for Mellanox ConnectX HCA IB driver (mlx4) +---------------------------------------------------------- + +What: /sys/class/infiniband/mlx4_X/hw_rev +What: /sys/class/infiniband/mlx4_X/hca_type +What: /sys/class/infiniband/mlx4_X/board_id +Date: Sep, 2007 +KernelVersion: v2.6.24 +Contact: linux-rdma@vger.kernel.org +Description: + =============== =============================== + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Host channel adapter type + + board_id: (RO) Manufacturing board ID + =============== =============================== + + +What: /sys/class/infiniband/mlx4_X/iov/ports//gids/ +What: /sys/class/infiniband/mlx4_X/iov/ports//admin_guids/ +What: /sys/class/infiniband/mlx4_X/iov/ports//pkeys/ +What: /sys/class/infiniband/mlx4_X/iov/ports//mcgs/ +What: /sys/class/infiniband/mlx4_X/iov/ports//ports//gid_idx/0 +What: /sys/class/infiniband/mlx4_X/iov/ports//ports//pkey_idx/ +Date: Aug, 2012 +KernelVersion: v3.6.15 +Contact: linux-rdma@vger.kernel.org +Description: + The sysfs iov directory is used to manage and examine the port + P_Key and guid paravirtualization. This directory is added only + for the master -- slaves do not have it. + + Under iov/ports, the administrator may examine the gid and P_Key + tables as they are present in the device (and as are seen in the + "network view" presented to the SM). + + The "pkeys" and "gids" subdirectories contain one file for each + entry in the port's P_Key or GID table respectively. For + example, ports/1/pkeys/10 contains the value at index 10 in port + 1's P_Key table. + + ======================= ========================================== + gids/: (RO) The physical port gids n = 0..127 + + admin_guids/: (RW) Allows examining or changing the + administrative state of a given GUID + n = 0..127 + + pkeys/: (RO) Displays the contents of the physical + key table n = 0..126 + + mcgs/: (RO) Muticast group table + + /gid_idx/0: (RO) Display the GID mapping m = 1..2 + + /pkey_idx/: (RW) Writable except for RoCE pkeys. + m = 1..2, n = 0..126 + + Under the iov/ + directories, the admin may map the index + numbers in the physical tables (as under + iov/ports) to the paravirtualized index + numbers that guests see. + + For example, if the administrator, for + port 1 on guest 2 maps physical pkey + index 10 to virtual index 1, then that + guest, whenever it uses its pkey index + 1, will actually be using the real pkey + index 10. + ======================= ========================================== + + +What: /sys/class/infiniband/mlx4_X/iov//ports//smi_enabled +What: /sys/class/infiniband/mlx4_X/iov//ports//enable_smi_admin +Date: May, 2014 +KernelVersion: v3.15.7 +Contact: linux-rdma@vger.kernel.org +Description: + Enabling QP0 on VFs for selected VF/port. By default, no VFs are + enabled for QP0 operation. + + ================= ==== =========================================== + smi_enabled: (RO) Indicates whether smi is currently enabled + for the indicated VF/port + + enable_smi_admin: (RW) Used by the admin to request that smi + capability be enabled or disabled for the + indicated VF/port. 0 = disable, 1 = enable. + ================= ==== =========================================== + + The requested enablement will occur at the next reset of the VF + (e.g. driver restart on the VM which owns the VF). + + +sysfs interface for Chelsio T4/T5 RDMA driver (cxgb4) +----------------------------------------------------- + +What: /sys/class/infiniband/cxgb4_X/hw_rev +What: /sys/class/infiniband/cxgb4_X/hca_type +What: /sys/class/infiniband/cxgb4_X/board_id +Date: Apr, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + + =============== ============================================= + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Driver short name. Should normally match + the name in its bus driver structure (e.g. + pci_driver::name) + + board_id: (RO) Manufacturing board id. (Vendor + device + information) + =============== ============================================= + + +sysfs interface for Intel IB driver qib +--------------------------------------- + +What: /sys/class/infiniband/qibX/version +What: /sys/class/infiniband/qibX/hw_rev +What: /sys/class/infiniband/qibX/hca_type +What: /sys/class/infiniband/qibX/board_id +What: /sys/class/infiniband/qibX/boardversion +What: /sys/class/infiniband/qibX/nctxts +What: /sys/class/infiniband/qibX/localbus_info +What: /sys/class/infiniband/qibX/tempsense +What: /sys/class/infiniband/qibX/serial +What: /sys/class/infiniband/qibX/nfreectxts +What: /sys/class/infiniband/qibX/chip_reset +Date: May, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + =============== ====================================================== + version: (RO) Display version information of installed software + and drivers. + + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Host channel adapter type + + board_id: (RO) Manufacturing board id + + boardversion: (RO) Current version of the chip architecture + + nctxts: (RO) Return the number of user ports (contexts) + available + + localbus_info: (RO) Human readable localbus info + + tempsense: (RO) Display temp sense registers in decimal + + serial: (RO) Serial number of the HCA + + nfreectxts: (RO) The number of free user ports (contexts) + available. + + chip_reset: (WO) Reset the chip if possible by writing + "reset" to this file. Only allowed if no user + contexts are open that use chip resources. + =============== ====================================================== + + +What: /sys/class/infiniband/qibX/ports//sl2vl/[0-15] +Date: May, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + (RO) The directory contains 16 files numbered 0-15 that specify + the Service Level (SL). Listing the SL files returns the Virtual + Lane (VL) as programmed by the SL. + +What: /sys/class/infiniband/qibX/ports//CCMgtA/cc_settings_bin +What: /sys/class/infiniband/qibX/ports//CCMgtA/cc_table_bin +Date: May, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + Per-port congestion control. Both are binary attributes. + + =============== ================================================ + cc_table_bin (RO) Congestion control table size followed by + table entries. + + cc_settings_bin (RO) Congestion settings: port control, control + map and an array of 16 entries for the + congestion entries - increase, timer, event log + trigger threshold and the minimum injection rate + delay. + =============== ================================================ + +What: /sys/class/infiniband/qibX/ports//linkstate/loopback +What: /sys/class/infiniband/qibX/ports//linkstate/led_override +What: /sys/class/infiniband/qibX/ports//linkstate/hrtbt_enable +What: /sys/class/infiniband/qibX/ports//linkstate/status +What: /sys/class/infiniband/qibX/ports//linkstate/status_str +Date: May, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + [to be documented] + + =============== =============================================== + loopback: (WO) + led_override: (WO) + hrtbt_enable: (RW) + status: (RO) + + status_str: (RO) Displays information about the link state, + possible cable/switch problems, and hardware + errors. Possible states are- "Initted", + "Present", "IB_link_up", "IB_configured" or + "Fatal_Hardware_Error". + =============== =============================================== + +What: /sys/class/infiniband/qibX/ports//diag_counters/rc_resends +What: /sys/class/infiniband/qibX/ports//diag_counters/seq_naks +What: /sys/class/infiniband/qibX/ports//diag_counters/rdma_seq +What: /sys/class/infiniband/qibX/ports//diag_counters/rnr_naks +What: /sys/class/infiniband/qibX/ports//diag_counters/other_naks +What: /sys/class/infiniband/qibX/ports//diag_counters/rc_timeouts +What: /sys/class/infiniband/qibX/ports//diag_counters/look_pkts +What: /sys/class/infiniband/qibX/ports//diag_counters/pkt_drops +What: /sys/class/infiniband/qibX/ports//diag_counters/dma_wait +What: /sys/class/infiniband/qibX/ports//diag_counters/unaligned +Date: May, 2010 +KernelVersion: v2.6.35 +Contact: linux-rdma@vger.kernel.org +Description: + [to be documented] + + +sysfs interface for Mellanox Connect-IB HCA driver mlx5 +------------------------------------------------------- + +What: /sys/class/infiniband/mlx5_X/hw_rev +What: /sys/class/infiniband/mlx5_X/hca_type +What: /sys/class/infiniband/mlx5_X/reg_pages +What: /sys/class/infiniband/mlx5_X/fw_pages +Date: Jul, 2013 +KernelVersion: v3.11 +Contact: linux-rdma@vger.kernel.org +Description: + [to be documented] + + +sysfs interface for Cisco VIC (usNIC) Verbs Driver +-------------------------------------------------- + +What: /sys/class/infiniband/usnic_X/board_id +What: /sys/class/infiniband/usnic_X/config +What: /sys/class/infiniband/usnic_X/qp_per_vf +What: /sys/class/infiniband/usnic_X/max_vf +What: /sys/class/infiniband/usnic_X/cq_per_vf +What: /sys/class/infiniband/usnic_X/iface +Date: Sep, 2013 +KernelVersion: v3.14 +Contact: Christian Benvenuti , + Dave Goodell , + linux-rdma@vger.kernel.org +Description: + + =============== =============================================== + board_id: (RO) Manufacturing board id + + config: (RO) Report the configuration for this PF + + qp_per_vf: (RO) Queue pairs per virtual function. + + max_vf: (RO) Max virtual functions + + cq_per_vf: (RO) Completion queue per virtual function + + iface: (RO) Shows which network interface this usNIC + entry is associated to (visible with ifconfig). + =============== =============================================== + +What: /sys/class/infiniband/usnic_X/qpn/summary +What: /sys/class/infiniband/usnic_X/qpn/context +Date: Sep, 2013 +KernelVersion: v3.14 +Contact: Christian Benvenuti , + Dave Goodell , + linux-rdma@vger.kernel.org +Description: + [to be documented] + + +sysfs interface for Emulex RoCE HCA Driver +------------------------------------------ + +What: /sys/class/infiniband/ocrdmaX/hw_rev +Date: Feb, 2014 +KernelVersion: v3.14 +Description: + hw_rev: (RO) Hardware revision number + +What: /sys/class/infiniband/ocrdmaX/hca_type +Date: Jun, 2014 +KernelVersion: v3.16 +Contact: linux-rdma@vger.kernel.org +Description: + hca_type: (RO) Display FW version + + +sysfs interface for Intel Omni-Path driver (HFI1) +------------------------------------------------- + +What: /sys/class/infiniband/hfi1_X/hw_rev +What: /sys/class/infiniband/hfi1_X/board_id +What: /sys/class/infiniband/hfi1_X/nctxts +What: /sys/class/infiniband/hfi1_X/serial +What: /sys/class/infiniband/hfi1_X/chip_reset +What: /sys/class/infiniband/hfi1_X/boardversion +What: /sys/class/infiniband/hfi1_X/nfreectxts +What: /sys/class/infiniband/hfi1_X/tempsense +Date: May, 2016 +KernelVersion: v4.6 +Contact: linux-rdma@vger.kernel.org +Description: + =============== ============================================= + hw_rev: (RO) Hardware revision number + + board_id: (RO) Manufacturing board id + + nctxts: (RO) Total contexts available. + + serial: (RO) Board serial number + + chip_reset: (WO) Write "reset" to this file to reset the + chip if possible. Only allowed if no user + contexts are open that use chip resources. + + boardversion: (RO) Human readable board info + + nfreectxts: (RO) The number of free user ports (contexts) + available. + + tempsense: (RO) Thermal sense information + =============== ============================================= + + +What: /sys/class/infiniband/hfi1_X/ports//CCMgtA/cc_settings_bin +What: /sys/class/infiniband/hfi1_X/ports//CCMgtA/cc_table_bin +What: /sys/class/infiniband/hfi1_X/ports//CCMgtA/cc_prescan +Date: May, 2016 +KernelVersion: v4.6 +Contact: linux-rdma@vger.kernel.org +Description: + Per-port congestion control. + + =============== ================================================ + cc_table_bin (RO) CCA tables used by PSM2 Congestion control + table size followed by table entries. Binary + attribute. + + cc_settings_bin (RO) Congestion settings: port control, control + map and an array of 16 entries for the + congestion entries - increase, timer, event log + trigger threshold and the minimum injection rate + delay. Binary attribute. + + cc_prescan (RW) enable prescanning for faster BECN + response. Write "on" to enable and "off" to + disable. + =============== ================================================ + +What: /sys/class/infiniband/hfi1_X/ports//sc2vl/[0-31] +What: /sys/class/infiniband/hfi1_X/ports//sl2sc/[0-31] +What: /sys/class/infiniband/hfi1_X/ports//vl2mtu/[0-15] +Date: May, 2016 +KernelVersion: v4.6 +Contact: linux-rdma@vger.kernel.org +Description: + =============== =================================================== + sc2vl/: (RO) 32 files (0 - 31) used to translate sl->vl + + sl2sc/: (RO) 32 files (0 - 31) used to translate sl->sc + + vl2mtu/: (RO) 16 files (0 - 15) used to determine MTU for vl + =============== =================================================== + + +What: /sys/class/infiniband/hfi1_X/sdma_/cpu_list +What: /sys/class/infiniband/hfi1_X/sdma_/vl +Date: Sept, 2016 +KernelVersion: v4.8 +Contact: linux-rdma@vger.kernel.org +Description: + sdma/ contains one directory per sdma engine (0 - 15) + + =============== ============================================== + cpu_list: (RW) List of cpus for user-process to sdma + engine assignment. + + vl: (RO) Displays the virtual lane (vl) the sdma + engine maps to. + =============== ============================================== + + This interface gives the user control on the affinity settings + for the device. As an example, to set an sdma engine irq + affinity and thread affinity of a user processes to use the + sdma engine, which is "near" in terms of NUMA configuration, or + physical cpu location, the user will do:: + + echo "3" > /proc/irq//smp_affinity_list + echo "4-7" > /sys/devices/.../sdma3/cpu_list + cat /sys/devices/.../sdma3/vl + 0 + echo "8" > /proc/irq//smp_affinity_list + echo "9-12" > /sys/devices/.../sdma4/cpu_list + cat /sys/devices/.../sdma4/vl + 1 + + to make sure that when a process runs on cpus 4,5,6, or 7, and + uses vl=0, then sdma engine 3 is selected by the driver, and + also the interrupt of the sdma engine 3 is steered to cpu 3. + Similarly, when a process runs on cpus 9,10,11, or 12 and sets + vl=1, then engine 4 will be selected and the irq of the sdma + engine 4 is steered to cpu 8. This assumes that in the above N + is the irq number of "sdma3", and M is irq number of "sdma4" in + the /proc/interrupts file. + +sysfs interface for QLogic qedr NIC Driver +------------------------------------------ + +What: /sys/class/infiniband/qedrX/hw_rev +What: /sys/class/infiniband/qedrX/hca_type +Date: Oct, 2016 +KernelVersion: v4.10 +Contact: linux-rdma@vger.kernel.org +Description: + + =============== ==== ======================== + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Display HCA type + =============== ==== ======================== + + +sysfs interface for VMware Paravirtual RDMA driver +-------------------------------------------------- + +What: /sys/class/infiniband/vmw_pvrdmaX/hw_rev +What: /sys/class/infiniband/vmw_pvrdmaX/hca_type +What: /sys/class/infiniband/vmw_pvrdmaX/board_id +Date: Oct, 2016 +KernelVersion: v4.10 +Contact: linux-rdma@vger.kernel.org +Description: + + =============== ==== ===================================== + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Host channel adapter type + + board_id: (RO) Display PVRDMA manufacturing board ID + =============== ==== ===================================== + + +sysfs interface for Broadcom NetXtreme-E RoCE driver +---------------------------------------------------- + +What: /sys/class/infiniband/bnxt_reX/hw_rev +What: /sys/class/infiniband/bnxt_reX/hca_type +Date: Feb, 2017 +KernelVersion: v4.11 +Contact: linux-rdma@vger.kernel.org +Description: + =============== ==== ========================= + hw_rev: (RO) Hardware revision number + + hca_type: (RO) Host channel adapter type + =============== ==== ========================= diff --git a/Documentation/ABI/stable/sysfs-class-rfkill b/Documentation/ABI/stable/sysfs-class-rfkill new file mode 100644 index 000000000..037979f7d --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-rfkill @@ -0,0 +1,93 @@ +rfkill - radio frequency (RF) connector kill switch support + +For details to this subsystem look at Documentation/driver-api/rfkill.rst. + +For the deprecated ``/sys/class/rfkill/*/claim`` knobs of this interface look in +Documentation/ABI/removed/sysfs-class-rfkill. + +What: /sys/class/rfkill +Date: 09-Jul-2007 +KernelVersion: v2.6.22 +Contact: linux-wireless@vger.kernel.org, +Description: The rfkill class subsystem folder. + Each registered rfkill driver is represented by an rfkillX + subfolder (X being an integer >= 0). + + +What: /sys/class/rfkill/rfkill[0-9]+/name +Date: 09-Jul-2007 +KernelVersion v2.6.22 +Contact: linux-wireless@vger.kernel.org +Description: Name assigned by driver to this key (interface or driver name). +Values: arbitrary string. + + +What: /sys/class/rfkill/rfkill[0-9]+/type +Date: 09-Jul-2007 +KernelVersion v2.6.22 +Contact: linux-wireless@vger.kernel.org +Description: Driver type string ("wlan", "bluetooth", etc). +Values: See include/linux/rfkill.h. + + +What: /sys/class/rfkill/rfkill[0-9]+/persistent +Date: 09-Jul-2007 +KernelVersion v2.6.22 +Contact: linux-wireless@vger.kernel.org +Description: Whether the soft blocked state is initialised from non-volatile + storage at startup. +Values: A numeric value: + + - 0: false + - 1: true + + +What: /sys/class/rfkill/rfkill[0-9]+/state +Date: 09-Jul-2007 +KernelVersion v2.6.22 +Contact: linux-wireless@vger.kernel.org +Description: Current state of the transmitter. + This file was scheduled to be removed in 2014, but due to its + large number of users it will be sticking around for a bit + longer. Despite it being marked as stable, the newer "hard" and + "soft" interfaces should be preferred, since it is not possible + to express the 'soft and hard block' state of the rfkill driver + through this interface. There will likely be another attempt to + remove it in the future. +Values: A numeric value. + + 0: RFKILL_STATE_SOFT_BLOCKED + transmitter is turned off by software + 1: RFKILL_STATE_UNBLOCKED + transmitter is (potentially) active + 2: RFKILL_STATE_HARD_BLOCKED + transmitter is forced off by something outside of + the driver's control. + + +What: /sys/class/rfkill/rfkill[0-9]+/hard +Date: 12-March-2010 +KernelVersion v2.6.34 +Contact: linux-wireless@vger.kernel.org +Description: Current hardblock state. This file is read only. +Values: A numeric value. + + 0: inactive + The transmitter is (potentially) active. + 1: active + The transmitter is forced off by something outside of + the driver's control. + + +What: /sys/class/rfkill/rfkill[0-9]+/soft +Date: 12-March-2010 +KernelVersion v2.6.34 +Contact: linux-wireless@vger.kernel.org +Description: Current softblock state. This file is read and write. +Values: A numeric value. + + 0: inactive + The transmitter is (potentially) active. + + 1: active + The transmitter is turned off by software. diff --git a/Documentation/ABI/stable/sysfs-class-tpm b/Documentation/ABI/stable/sysfs-class-tpm new file mode 100644 index 000000000..411d5895b --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-tpm @@ -0,0 +1,210 @@ +What: /sys/class/tpm/tpmX/device/ +Date: April 2005 +KernelVersion: 2.6.12 +Contact: linux-integrity@vger.kernel.org +Description: The device/ directory under a specific TPM instance exposes + the properties of that TPM chip + + +What: /sys/class/tpm/tpmX/device/active +Date: April 2006 +KernelVersion: 2.6.17 +Contact: linux-integrity@vger.kernel.org +Description: The "active" property prints a '1' if the TPM chip is accepting + commands. An inactive TPM chip still contains all the state of + an active chip (Storage Root Key, NVRAM, etc), and can be + visible to the OS, but will only accept a restricted set of + commands. See the TPM Main Specification part 2, Structures, + section 17 for more information on which commands are + available. + +What: /sys/class/tpm/tpmX/device/cancel +Date: June 2005 +KernelVersion: 2.6.13 +Contact: linux-integrity@vger.kernel.org +Description: The "cancel" property allows you to cancel the currently + pending TPM command. Writing any value to cancel will call the + TPM vendor specific cancel operation. + +What: /sys/class/tpm/tpmX/device/caps +Date: April 2005 +KernelVersion: 2.6.12 +Contact: linux-integrity@vger.kernel.org +Description: The "caps" property contains TPM manufacturer and version info. + + Example output:: + + Manufacturer: 0x53544d20 + TCG version: 1.2 + Firmware version: 8.16 + + Manufacturer is a hex dump of the 4 byte manufacturer info + space in a TPM. TCG version shows the TCG TPM spec level that + the chip supports. Firmware version is that of the chip and + is manufacturer specific. + +What: /sys/class/tpm/tpmX/device/durations +Date: March 2011 +KernelVersion: 3.1 +Contact: linux-integrity@vger.kernel.org +Description: The "durations" property shows the 3 vendor-specific values + used to wait for a short, medium and long TPM command. All + TPM commands are categorized as short, medium or long in + execution time, so that the driver doesn't have to wait + any longer than necessary before starting to poll for a + result. + + Example output:: + + 3015000 4508000 180995000 [original] + + Here the short, medium and long durations are displayed in + usecs. "[original]" indicates that the values are displayed + unmodified from when they were queried from the chip. + Durations can be modified in the case where a buggy chip + reports them in msec instead of usec and they need to be + scaled to be displayed in usecs. In this case "[adjusted]" + will be displayed in place of "[original]". + +What: /sys/class/tpm/tpmX/device/enabled +Date: April 2006 +KernelVersion: 2.6.17 +Contact: linux-integrity@vger.kernel.org +Description: The "enabled" property prints a '1' if the TPM chip is enabled, + meaning that it should be visible to the OS. This property + may be visible but produce a '0' after some operation that + disables the TPM. + +What: /sys/class/tpm/tpmX/device/owned +Date: April 2006 +KernelVersion: 2.6.17 +Contact: linux-integrity@vger.kernel.org +Description: The "owned" property produces a '1' if the TPM_TakeOwnership + ordinal has been executed successfully in the chip. A '0' + indicates that ownership hasn't been taken. + +What: /sys/class/tpm/tpmX/device/pcrs +Date: April 2005 +KernelVersion: 2.6.12 +Contact: linux-integrity@vger.kernel.org +Description: The "pcrs" property will dump the current value of all Platform + Configuration Registers in the TPM. Note that since these + values may be constantly changing, the output is only valid + for a snapshot in time. + + Example output:: + + PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75 + PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75 + PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75 + PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75 + PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75 + ... + + The number of PCRs and hex bytes needed to represent a PCR + value will vary depending on TPM chip version. For TPM 1.1 and + 1.2 chips, PCRs represent SHA-1 hashes, which are 20 bytes + long. Use the "caps" property to determine TPM version. + +What: /sys/class/tpm/tpmX/device/pubek +Date: April 2005 +KernelVersion: 2.6.12 +Contact: linux-integrity@vger.kernel.org +Description: The "pubek" property will return the TPM's public endorsement + key if possible. If the TPM has had ownership established and + is version 1.2, the pubek will not be available without the + owner's authorization. Since the TPM driver doesn't store any + secrets, it can't authorize its own request for the pubek, + making it unaccessible. The public endorsement key is gener- + ated at TPM manufacture time and exists for the life of the + chip. + + Example output:: + + Algorithm: 00 00 00 01 + Encscheme: 00 03 + Sigscheme: 00 01 + Parameters: 00 00 08 00 00 00 00 02 00 00 00 00 + Modulus length: 256 + Modulus: + B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C + 3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6 + 1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB + 86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3 + D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B + 82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26 + 0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E + 1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D + 6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0 + A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6 + 47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6 + 10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70 + E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A + F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6 + F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B + C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B + + Possible values:: + + Algorithm: TPM_ALG_RSA (1) + Encscheme: TPM_ES_RSAESPKCSv15 (2) + TPM_ES_RSAESOAEP_SHA1_MGF1 (3) + Sigscheme: TPM_SS_NONE (1) + Parameters, a byte string of 3 u32 values: + Key Length (bits): 00 00 08 00 (2048) + Num primes: 00 00 00 02 (2) + Exponent Size: 00 00 00 00 (0 means the + default exp) + Modulus Length: 256 (bytes) + Modulus: The 256 byte Endorsement Key modulus + +What: /sys/class/tpm/tpmX/device/temp_deactivated +Date: April 2006 +KernelVersion: 2.6.17 +Contact: linux-integrity@vger.kernel.org +Description: The "temp_deactivated" property returns a '1' if the chip has + been temporarily deactivated, usually until the next power + cycle. Whether a warm boot (reboot) will clear a TPM chip + from a temp_deactivated state is platform specific. + +What: /sys/class/tpm/tpmX/device/timeouts +Date: March 2011 +KernelVersion: 3.1 +Contact: linux-integrity@vger.kernel.org +Description: The "timeouts" property shows the 4 vendor-specific values + for the TPM's interface spec timeouts. The use of these + timeouts is defined by the TPM interface spec that the chip + conforms to. + + Example output:: + + 750000 750000 750000 750000 [original] + + The four timeout values are shown in usecs, with a trailing + "[original]" or "[adjusted]" depending on whether the values + were scaled by the driver to be reported in usec from msecs. + +What: /sys/class/tpm/tpmX/tpm_version_major +Date: October 2019 +KernelVersion: 5.5 +Contact: linux-integrity@vger.kernel.org +Description: The "tpm_version_major" property shows the TCG spec major version + implemented by the TPM device. + + Example output:: + + 2 + +What: /sys/class/tpm/tpmX/pcr-/ +Date: March 2021 +KernelVersion: 5.12 +Contact: linux-integrity@vger.kernel.org +Description: produces output in compact hex representation for PCR + number N from hash bank H. N is the numeric value of + the PCR number and H is the crypto string + representation of the hash + + Example output:: + + cat /sys/class/tpm/tpm0/pcr-sha256/7 + 2ED93F199692DC6788EFA6A1FE74514AB9760B2A6CEEAEF6C808C13E4ABB0D42 diff --git a/Documentation/ABI/stable/sysfs-class-ubi b/Documentation/ABI/stable/sysfs-class-ubi new file mode 100644 index 000000000..a6b324014 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-ubi @@ -0,0 +1,221 @@ +What: /sys/class/ubi/ +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + The ubi/ class sub-directory belongs to the UBI subsystem and + provides general UBI information, per-UBI device information + and per-UBI volume information. + +What: /sys/class/ubi/version +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + This file contains version of the latest supported UBI on-media + format. Currently it is 1, and there is no plan to change this. + However, if in the future UBI needs on-flash format changes + which cannot be done in a compatible manner, a new format + version will be added. So this is a mechanism for possible + future backward-compatible (but forward-incompatible) + improvements. + +What: /sys/class/ubiX/ +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + The /sys/class/ubi0, /sys/class/ubi1, etc directories describe + UBI devices (UBI device 0, 1, etc). They contain general UBI + device information and per UBI volume information (each UBI + device may have many UBI volumes) + +What: /sys/class/ubi/ubiX/avail_eraseblocks +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Amount of available logical eraseblock. For example, one may + create a new UBI volume which has this amount of logical + eraseblocks. + +What: /sys/class/ubi/ubiX/bad_peb_count +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Count of bad physical eraseblocks on the underlying MTD device. + +What: /sys/class/ubi/ubiX/bgt_enabled +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Contains ASCII "0\n" if the UBI background thread is disabled, + and ASCII "1\n" if it is enabled. + +What: /sys/class/ubi/ubiX/dev +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Major and minor numbers of the character device corresponding + to this UBI device (in : format). + +What: /sys/class/ubi/ubiX/eraseblock_size +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Maximum logical eraseblock size this UBI device may provide. UBI + volumes may have smaller logical eraseblock size because of their + alignment. + +What: /sys/class/ubi/ubiX/max_ec +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Maximum physical eraseblock erase counter value. + +What: /sys/class/ubi/ubiX/max_vol_count +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Maximum number of volumes which this UBI device may have. + +What: /sys/class/ubi/ubiX/min_io_size +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Minimum input/output unit size. All the I/O may only be done + in fractions of the contained number. + +What: /sys/class/ubi/ubiX/mtd_num +Date: January 2008 +KernelVersion: 2.6.25 +Contact: Artem Bityutskiy +Description: + Number of the underlying MTD device. + +What: /sys/class/ubi/ubiX/reserved_for_bad +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Number of physical eraseblocks reserved for bad block handling. + +What: /sys/class/ubi/ubiX/ro_mode +Date: April 2016 +KernelVersion: 4.7 +Contact: linux-mtd@lists.infradead.org +Description: + Contains ASCII "1\n" if the read-only flag is set on this + device, and "0\n" if it is cleared. UBI devices mark themselves + as read-only when they detect an unrecoverable error. + +What: /sys/class/ubi/ubiX/total_eraseblocks +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Total number of good (not marked as bad) physical eraseblocks on + the underlying MTD device. + +What: /sys/class/ubi/ubiX/volumes_count +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Count of volumes on this UBI device. + +What: /sys/class/ubi/ubiX/ubiX_Y/ +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + The /sys/class/ubi/ubiX/ubiX_0/, /sys/class/ubi/ubiX/ubiX_1/, + etc directories describe UBI volumes on UBI device X (volumes + 0, 1, etc). + +What: /sys/class/ubi/ubiX/ubiX_Y/alignment +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Volume alignment - the value the logical eraseblock size of + this volume has to be aligned on. For example, 2048 means that + logical eraseblock size is multiple of 2048. In other words, + volume logical eraseblock size is UBI device logical eraseblock + size aligned to the alignment value. + +What: /sys/class/ubi/ubiX/ubiX_Y/corrupted +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n" + if it is corrupted (e.g., due to an interrupted volume update). + +What: /sys/class/ubi/ubiX/ubiX_Y/data_bytes +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + The amount of data this volume contains. This value makes sense + only for static volumes, and for dynamic volume it equivalent + to the total volume size in bytes. + +What: /sys/class/ubi/ubiX/ubiX_Y/dev +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Major and minor numbers of the character device corresponding + to this UBI volume (in : format). + +What: /sys/class/ubi/ubiX/ubiX_Y/name +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Volume name. + +What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Count of physical eraseblock reserved for this volume. + Equivalent to the volume size in logical eraseblocks. + +What: /sys/class/ubi/ubiX/ubiX_Y/type +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Volume type. Contains ASCII "dynamic\n" for dynamic volumes and + "static\n" for static volumes. + +What: /sys/class/ubi/ubiX/ubiX_Y/upd_marker +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Contains ASCII "0\n" if the update marker is not set for this + volume, and "1\n" if it is set. The update marker is set when + volume update starts, and cleaned when it ends. So the presence + of the update marker indicates that the volume is being updated + at the moment of the update was interrupted. The later may be + checked using the "corrupted" sysfs file. + +What: /sys/class/ubi/ubiX/ubiX_Y/usable_eb_size +Date: July 2006 +KernelVersion: 2.6.22 +Contact: Artem Bityutskiy +Description: + Logical eraseblock size of this volume. Equivalent to logical + eraseblock size of the device aligned on the volume alignment + value. diff --git a/Documentation/ABI/stable/sysfs-class-udc b/Documentation/ABI/stable/sysfs-class-udc new file mode 100644 index 000000000..d1e2f3ec1 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-class-udc @@ -0,0 +1,93 @@ +What: /sys/class/udc//a_alt_hnp_support +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates if an OTG A-Host supports HNP at an alternate port. +Users: + +What: /sys/class/udc//a_hnp_support +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates if an OTG A-Host supports HNP at this port. +Users: + +What: /sys/class/udc//b_hnp_enable +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates if an OTG A-Host enabled HNP support. +Users: + +What: /sys/class/udc//current_speed +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates the current negotiated speed at this port. +Users: + +What: /sys/class/udc//is_a_peripheral +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates that this port is the default Host on an OTG session + but HNP was used to switch roles. +Users: + +What: /sys/class/udc//is_otg +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates that this port support OTG. +Users: + +What: /sys/class/udc//maximum_speed +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates the maximum USB speed supported by this port. +Users: + +What: /sys/class/udc//soft_connect +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Allows users to disconnect data pullup resistors thus causing a + logical disconnection from the USB Host. +Users: + +What: /sys/class/udc//srp +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Allows users to manually start Session Request Protocol. +Users: + +What: /sys/class/udc//state +Date: June 2011 +KernelVersion: 3.1 +Contact: Felipe Balbi +Description: + Indicates current state of the USB Device Controller. Valid + states are: 'not-attached', 'attached', 'powered', + 'reconnecting', 'unauthenticated', 'default', 'addressed', + 'configured', and 'suspended'; however not all USB Device + Controllers support reporting all states. +Users: + +What: /sys/class/udc//function +Date: June 2017 +KernelVersion: 4.13 +Contact: Felipe Balbi +Description: + Prints out name of currently running USB Gadget Driver. +Users: diff --git a/Documentation/ABI/stable/sysfs-devices b/Documentation/ABI/stable/sysfs-devices new file mode 100644 index 000000000..98a8ef99a --- /dev/null +++ b/Documentation/ABI/stable/sysfs-devices @@ -0,0 +1,32 @@ +Note: + This documents additional properties of any device beyond what + is documented in Documentation/admin-guide/sysfs-rules.rst + +What: /sys/devices/*/of_node +Date: February 2015 +Contact: Device Tree mailing list +Description: + Any device associated with a device-tree node will have + an of_path symlink pointing to the corresponding device + node in /sys/firmware/devicetree/ + +What: /sys/devices/*/devspec +Date: October 2016 +Contact: Device Tree mailing list +Description: + If CONFIG_OF is enabled, then this file is present. When + read, it returns full name of the device node. + +What: /sys/devices/*/obppath +Date: October 2016 +Contact: Device Tree mailing list +Description: + If CONFIG_OF is enabled, then this file is present. When + read, it returns full name of the device node. + +What: /sys/devices/*/dev +Date: Jun 2006 +Contact: Greg Kroah-Hartman +Description: + Major and minor numbers of the character device corresponding + to the device (in : format). diff --git a/Documentation/ABI/stable/sysfs-devices-node b/Documentation/ABI/stable/sysfs-devices-node new file mode 100644 index 000000000..8db67aa47 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-devices-node @@ -0,0 +1,184 @@ +What: /sys/devices/system/node/possible +Date: October 2002 +Contact: Linux Memory Management list +Description: + Nodes that could be possibly become online at some point. + +What: /sys/devices/system/node/online +Date: October 2002 +Contact: Linux Memory Management list +Description: + Nodes that are online. + +What: /sys/devices/system/node/has_normal_memory +Date: October 2002 +Contact: Linux Memory Management list +Description: + Nodes that have regular memory. + +What: /sys/devices/system/node/has_cpu +Date: October 2002 +Contact: Linux Memory Management list +Description: + Nodes that have one or more CPUs. + +What: /sys/devices/system/node/has_high_memory +Date: October 2002 +Contact: Linux Memory Management list +Description: + Nodes that have regular or high memory. + Depends on CONFIG_HIGHMEM. + +What: /sys/devices/system/node/nodeX +Date: October 2002 +Contact: Linux Memory Management list +Description: + When CONFIG_NUMA is enabled, this is a directory containing + information on node X such as what CPUs are local to the + node. Each file is detailed next. + +What: /sys/devices/system/node/nodeX/cpumap +Date: October 2002 +Contact: Linux Memory Management list +Description: + The node's cpumap. + +What: /sys/devices/system/node/nodeX/cpulist +Date: October 2002 +Contact: Linux Memory Management list +Description: + The CPUs associated to the node. + +What: /sys/devices/system/node/nodeX/meminfo +Date: October 2002 +Contact: Linux Memory Management list +Description: + Provides information about the node's distribution and memory + utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst + +What: /sys/devices/system/node/nodeX/numastat +Date: October 2002 +Contact: Linux Memory Management list +Description: + The node's hit/miss statistics, in units of pages. + See Documentation/admin-guide/numastat.rst + +What: /sys/devices/system/node/nodeX/distance +Date: October 2002 +Contact: Linux Memory Management list +Description: + Distance between the node and all the other nodes + in the system. + +What: /sys/devices/system/node/nodeX/vmstat +Date: October 2002 +Contact: Linux Memory Management list +Description: + The node's zoned virtual memory statistics. + This is a superset of numastat. + +What: /sys/devices/system/node/nodeX/compact +Date: February 2010 +Contact: Mel Gorman +Description: + When this file is written to, all memory within that node + will be compacted. When it completes, memory will be freed + into blocks which have as many contiguous pages as possible + +What: /sys/devices/system/node/nodeX/hugepages/hugepages-/ +Date: December 2009 +Contact: Lee Schermerhorn +Description: + The node's huge page size control/query attributes. + See Documentation/admin-guide/mm/hugetlbpage.rst + +What: /sys/devices/system/node/nodeX/accessY/ +Date: December 2018 +Contact: Keith Busch +Description: + The node's relationship to other nodes for access class "Y". + +What: /sys/devices/system/node/nodeX/accessY/initiators/ +Date: December 2018 +Contact: Keith Busch +Description: + The directory containing symlinks to memory initiator + nodes that have class "Y" access to this target node's + memory. CPUs and other memory initiators in nodes not in + the list accessing this node's memory may have different + performance. + +What: /sys/devices/system/node/nodeX/accessY/targets/ +Date: December 2018 +Contact: Keith Busch +Description: + The directory containing symlinks to memory targets that + this initiator node has class "Y" access. + +What: /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth +Date: December 2018 +Contact: Keith Busch +Description: + This node's read bandwidth in MB/s when accessed from + nodes found in this access class's linked initiators. + +What: /sys/devices/system/node/nodeX/accessY/initiators/read_latency +Date: December 2018 +Contact: Keith Busch +Description: + This node's read latency in nanoseconds when accessed + from nodes found in this access class's linked initiators. + +What: /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth +Date: December 2018 +Contact: Keith Busch +Description: + This node's write bandwidth in MB/s when accessed from + found in this access class's linked initiators. + +What: /sys/devices/system/node/nodeX/accessY/initiators/write_latency +Date: December 2018 +Contact: Keith Busch +Description: + This node's write latency in nanoseconds when access + from nodes found in this class's linked initiators. + +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/ +Date: December 2018 +Contact: Keith Busch +Description: + The directory containing attributes for the memory-side cache + level 'Y'. + +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing +Date: December 2018 +Contact: Keith Busch +Description: + The caches associativity indexing: 0 for direct mapped, + non-zero if indexed. + +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size +Date: December 2018 +Contact: Keith Busch +Description: + The number of bytes accessed from the next cache level on a + cache miss. + +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/size +Date: December 2018 +Contact: Keith Busch +Description: + The size of this memory side cache in bytes. + +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy +Date: December 2018 +Contact: Keith Busch +Description: + The cache write policy: 0 for write-back, 1 for write-through, + other or unknown. + +What: /sys/devices/system/node/nodeX/x86/sgx_total_bytes +Date: November 2021 +Contact: Jarkko Sakkinen +Description: + The total amount of SGX physical memory in bytes. diff --git a/Documentation/ABI/stable/sysfs-devices-system-cpu b/Documentation/ABI/stable/sysfs-devices-system-cpu new file mode 100644 index 000000000..902392d7e --- /dev/null +++ b/Documentation/ABI/stable/sysfs-devices-system-cpu @@ -0,0 +1,127 @@ +What: /sys/devices/system/cpu/dscr_default +Date: 13-May-2014 +KernelVersion: v3.15.0 +Contact: +Description: Writes are equivalent to writing to + /sys/devices/system/cpu/cpuN/dscr on all CPUs. + Reads return the last written value or 0. + This value is not a global default: it is a way to set + all per-CPU defaults at the same time. +Values: 64 bit unsigned integer (bit field) + +What: /sys/devices/system/cpu/cpu[0-9]+/dscr +Date: 13-May-2014 +KernelVersion: v3.15.0 +Contact: +Description: Default value for the Data Stream Control Register (DSCR) on + a CPU. + This default value is used when the kernel is executing and + for any process that has not set the DSCR itself. + If a process ever sets the DSCR (via direct access to the + SPR) that value will be persisted for that process and used + on any CPU where it executes (overriding the value described + here). + If set by a process it will be inherited by child processes. +Values: 64 bit unsigned integer (bit field) + +What: /sys/devices/system/cpu/cpuX/topology/physical_package_id +Description: physical package id of cpuX. Typically corresponds to a physical + socket number, but the actual value is architecture and platform + dependent. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/die_id +Description: the CPU die ID of cpuX. Typically it is the hardware platform's + identifier (rather than the kernel's). The actual value is + architecture and platform dependent. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/core_id +Description: the CPU core ID of cpuX. Typically it is the hardware platform's + identifier (rather than the kernel's). The actual value is + architecture and platform dependent. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/cluster_id +Description: the cluster ID of cpuX. Typically it is the hardware platform's + identifier (rather than the kernel's). The actual value is + architecture and platform dependent. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/book_id +Description: the book ID of cpuX. Typically it is the hardware platform's + identifier (rather than the kernel's). The actual value is + architecture and platform dependent. it's only used on s390. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/drawer_id +Description: the drawer ID of cpuX. Typically it is the hardware platform's + identifier (rather than the kernel's). The actual value is + architecture and platform dependent. it's only used on s390. +Values: integer + +What: /sys/devices/system/cpu/cpuX/topology/core_cpus +Description: internal kernel map of CPUs within the same core. + (deprecated name: "thread_siblings") +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/core_cpus_list +Description: human-readable list of CPUs within the same core. + The format is like 0-3, 8-11, 14,17. + (deprecated name: "thread_siblings_list"). +Values: decimal list. + +What: /sys/devices/system/cpu/cpuX/topology/package_cpus +Description: internal kernel map of the CPUs sharing the same physical_package_id. + (deprecated name: "core_siblings"). +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/package_cpus_list +Description: human-readable list of CPUs sharing the same physical_package_id. + The format is like 0-3, 8-11, 14,17. + (deprecated name: "core_siblings_list") +Values: decimal list. + +What: /sys/devices/system/cpu/cpuX/topology/die_cpus +Description: internal kernel map of CPUs within the same die. +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/ppin +Description: per-socket protected processor inventory number +Values: hexadecimal. + +What: /sys/devices/system/cpu/cpuX/topology/die_cpus_list +Description: human-readable list of CPUs within the same die. + The format is like 0-3, 8-11, 14,17. +Values: decimal list. + +What: /sys/devices/system/cpu/cpuX/topology/cluster_cpus +Description: internal kernel map of CPUs within the same cluster. +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/cluster_cpus_list +Description: human-readable list of CPUs within the same cluster. + The format is like 0-3, 8-11, 14,17. +Values: decimal list. + +What: /sys/devices/system/cpu/cpuX/topology/book_siblings +Description: internal kernel map of cpuX's hardware threads within the same + book_id. it's only used on s390. +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/book_siblings_list +Description: human-readable list of cpuX's hardware threads within the same + book_id. + The format is like 0-3, 8-11, 14,17. it's only used on s390. +Values: decimal list. + +What: /sys/devices/system/cpu/cpuX/topology/drawer_siblings +Description: internal kernel map of cpuX's hardware threads within the same + drawer_id. it's only used on s390. +Values: hexadecimal bitmask. + +What: /sys/devices/system/cpu/cpuX/topology/drawer_siblings_list +Description: human-readable list of cpuX's hardware threads within the same + drawer_id. + The format is like 0-3, 8-11, 14,17. it's only used on s390. +Values: decimal list. diff --git a/Documentation/ABI/stable/sysfs-devices-system-xen_memory b/Documentation/ABI/stable/sysfs-devices-system-xen_memory new file mode 100644 index 000000000..6d83f95a8 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-devices-system-xen_memory @@ -0,0 +1,86 @@ +What: /sys/devices/system/xen_memory/xen_memory0/max_retry_count +Date: May 2011 +KernelVersion: 2.6.39 +Contact: Konrad Rzeszutek Wilk +Description: + The maximum number of times the balloon driver will + attempt to increase the balloon before giving up. See + also 'retry_count' below. + A value of zero means retry forever and is the default one. + +What: /sys/devices/system/xen_memory/xen_memory0/max_schedule_delay +Date: May 2011 +KernelVersion: 2.6.39 +Contact: Konrad Rzeszutek Wilk +Description: + The limit that 'schedule_delay' (see below) will be + increased to. The default value is 32 seconds. + +What: /sys/devices/system/xen_memory/xen_memory0/retry_count +Date: May 2011 +KernelVersion: 2.6.39 +Contact: Konrad Rzeszutek Wilk +Description: + The current number of times that the balloon driver + has attempted to increase the size of the balloon. + The default value is one. With max_retry_count being + zero (unlimited), this means that the driver will attempt + to retry with a 'schedule_delay' delay. + +What: /sys/devices/system/xen_memory/xen_memory0/schedule_delay +Date: May 2011 +KernelVersion: 2.6.39 +Contact: Konrad Rzeszutek Wilk +Description: + The time (in seconds) to wait between attempts to + increase the balloon. Each time the balloon cannot be + increased, 'schedule_delay' is increased (until + 'max_schedule_delay' is reached at which point it + will use the max value). + +What: /sys/devices/system/xen_memory/xen_memory0/target +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Konrad Rzeszutek Wilk +Description: + The target number of pages to adjust this domain's + memory reservation to. + +What: /sys/devices/system/xen_memory/xen_memory0/target_kb +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Konrad Rzeszutek Wilk +Description: + As target above, except the value is in KiB. + +What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Konrad Rzeszutek Wilk +Description: + Current size (in KiB) of this domain's memory + reservation. + +What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Konrad Rzeszutek Wilk +Description: + Amount (in KiB) of high memory in the balloon. + +What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Konrad Rzeszutek Wilk +Description: + Amount (in KiB) of low (or normal) memory in the + balloon. + +What: /sys/devices/system/xen_memory/xen_memory0/scrub_pages +Date: September 2018 +KernelVersion: 4.20 +Contact: xen-devel@lists.xenproject.org +Description: + Control scrubbing pages before returning them to Xen for others domains + use. Can be set with xen_scrub_pages cmdline + parameter. Default value controlled with CONFIG_XEN_SCRUB_PAGES_DEFAULT. diff --git a/Documentation/ABI/stable/sysfs-driver-aspeed-vuart b/Documentation/ABI/stable/sysfs-driver-aspeed-vuart new file mode 100644 index 000000000..950cafc94 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-aspeed-vuart @@ -0,0 +1,24 @@ +What: /sys/bus/platform/drivers/aspeed-vuart/*/lpc_address +Date: April 2017 +Contact: Jeremy Kerr +Description: Configures which IO port the host side of the UART + will appear on the host <-> BMC LPC bus. +Users: OpenBMC. Proposed changes should be mailed to + openbmc@lists.ozlabs.org + +What: /sys/bus/platform/drivers/aspeed-vuart/*/sirq +Date: April 2017 +Contact: Jeremy Kerr +Description: Configures which interrupt number the host side of + the UART will appear on the host <-> BMC LPC bus. +Users: OpenBMC. Proposed changes should be mailed to + openbmc@lists.ozlabs.org + +What: /sys/bus/platform/drivers/aspeed-vuart/*/sirq_polarity +Date: July 2019 +Contact: Oskar Senft +Description: Configures the polarity of the serial interrupt to the + host via the BMC LPC bus. + Set to 0 for active-low or 1 for active-high. +Users: OpenBMC. Proposed changes should be mailed to + openbmc@lists.ozlabs.org diff --git a/Documentation/ABI/stable/sysfs-driver-dma-idxd b/Documentation/ABI/stable/sysfs-driver-dma-idxd new file mode 100644 index 000000000..3becc9a82 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-dma-idxd @@ -0,0 +1,304 @@ +What: /sys/bus/dsa/devices/dsa/version +Date: Apr 15, 2020 +KernelVersion: 5.8.0 +Contact: dmaengine@vger.kernel.org +Description: The hardware version number. + +What: /sys/bus/dsa/devices/dsa/cdev_major +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The major number that the character device driver assigned to + this device. + +What: /sys/bus/dsa/devices/dsa/errors +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The error information for this device. + +What: /sys/bus/dsa/devices/dsa/max_batch_size +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The largest number of work descriptors in a batch. + It's not visible when the device does not support batch. + +What: /sys/bus/dsa/devices/dsa/max_work_queues_size +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The maximum work queue size supported by this device. + +What: /sys/bus/dsa/devices/dsa/max_engines +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The maximum number of engines supported by this device. + +What: /sys/bus/dsa/devices/dsa/max_groups +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The maximum number of groups can be created under this device. + +What: /sys/bus/dsa/devices/dsa/max_read_buffers +Date: Dec 10, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: The total number of read buffers supported by this device. + The read buffers represent resources within the DSA + implementation, and these resources are allocated by engines to + support operations. See DSA spec v1.2 9.2.4 Total Read Buffers. + It's not visible when the device does not support Read Buffer + allocation control. + +What: /sys/bus/dsa/devices/dsa/max_transfer_size +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The number of bytes to be read from the source address to + perform the operation. The maximum transfer size is dependent on + the workqueue the descriptor was submitted to. + +What: /sys/bus/dsa/devices/dsa/max_work_queues +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The maximum work queue number that this device supports. + +What: /sys/bus/dsa/devices/dsa/numa_node +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The numa node number for this device. + +What: /sys/bus/dsa/devices/dsa/op_cap +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The operation capability bit mask specify the operation types + supported by the this device. + +What: /sys/bus/dsa/devices/dsa/pasid_enabled +Date: Oct 27, 2020 +KernelVersion: 5.11.0 +Contact: dmaengine@vger.kernel.org +Description: To indicate if PASID (process address space identifier) is + enabled or not for this device. + +What: /sys/bus/dsa/devices/dsa/state +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The state information of this device. It can be either enabled + or disabled. + +What: /sys/bus/dsa/devices/dsa/group. +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The assigned group under this device. + +What: /sys/bus/dsa/devices/dsa/engine. +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The assigned engine under this device. + +What: /sys/bus/dsa/devices/dsa/wq. +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The assigned work queue under this device. + +What: /sys/bus/dsa/devices/dsa/configurable +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: To indicate if this device is configurable or not. + +What: /sys/bus/dsa/devices/dsa/read_buffer_limit +Date: Dec 10, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: The maximum number of read buffers that may be in use at + one time by operations that access low bandwidth memory in the + device. See DSA spec v1.2 9.2.8 GENCFG on Global Read Buffer Limit. + It's not visible when the device does not support Read Buffer + allocation control. + +What: /sys/bus/dsa/devices/dsa/cmd_status +Date: Aug 28, 2020 +KernelVersion: 5.10.0 +Contact: dmaengine@vger.kernel.org +Description: The last executed device administrative command's status/error. + Also last configuration error overloaded. + Writing to it will clear the status. + +What: /sys/bus/dsa/devices/wq./block_on_fault +Date: Oct 27, 2020 +KernelVersion: 5.11.0 +Contact: dmaengine@vger.kernel.org +Description: To indicate block on fault is allowed or not for the work queue + to support on demand paging. + +What: /sys/bus/dsa/devices/wq./group_id +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The group id that this work queue belongs to. + +What: /sys/bus/dsa/devices/wq./size +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The work queue size for this work queue. + +What: /sys/bus/dsa/devices/wq./type +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The type of this work queue, it can be "kernel" type for work + queue usages in the kernel space or "user" type for work queue + usages by applications in user space. + +What: /sys/bus/dsa/devices/wq./cdev_minor +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The minor number assigned to this work queue by the character + device driver. + +What: /sys/bus/dsa/devices/wq./mode +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The work queue mode type for this work queue. + +What: /sys/bus/dsa/devices/wq./priority +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The priority value of this work queue, it is a value relative to + other work queue in the same group to control quality of service + for dispatching work from multiple workqueues in the same group. + +What: /sys/bus/dsa/devices/wq./state +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The current state of the work queue. + +What: /sys/bus/dsa/devices/wq./threshold +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The number of entries in this work queue that may be filled + via a limited portal. + +What: /sys/bus/dsa/devices/wq./max_transfer_size +Date: Aug 28, 2020 +KernelVersion: 5.10.0 +Contact: dmaengine@vger.kernel.org +Description: The max transfer sized for this workqueue. Cannot exceed device + max transfer size. Configurable parameter. + +What: /sys/bus/dsa/devices/wq./max_batch_size +Date: Aug 28, 2020 +KernelVersion: 5.10.0 +Contact: dmaengine@vger.kernel.org +Description: The max batch size for this workqueue. Cannot exceed device + max batch size. Configurable parameter. + It's not visible when the device does not support batch. + +What: /sys/bus/dsa/devices/wq./ats_disable +Date: Nov 13, 2020 +KernelVersion: 5.11.0 +Contact: dmaengine@vger.kernel.org +Description: Indicate whether ATS disable is turned on for the workqueue. + 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue. + +What: /sys/bus/dsa/devices/wq./occupancy +Date May 25, 2021 +KernelVersion: 5.14.0 +Contact: dmaengine@vger.kernel.org +Description: Show the current number of entries in this WQ if WQ Occupancy + Support bit WQ capabilities is 1. + +What: /sys/bus/dsa/devices/wq./enqcmds_retries +Date Oct 29, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: Indicate the number of retires for an enqcmds submission on a sharedwq. + A max value to set attribute is capped at 64. + +What: /sys/bus/dsa/devices/wq./op_config +Date: Sept 14, 2022 +KernelVersion: 6.0.0 +Contact: dmaengine@vger.kernel.org +Description: Shows the operation capability bits displayed in bitmap format + presented by %*pb printk() output format specifier. + The attribute can be configured when the WQ is disabled in + order to configure the WQ to accept specific bits that + correlates to the operations allowed. It's visible only + on platforms that support the capability. + +What: /sys/bus/dsa/devices/engine./group_id +Date: Oct 25, 2019 +KernelVersion: 5.6.0 +Contact: dmaengine@vger.kernel.org +Description: The group that this engine belongs to. + +What: /sys/bus/dsa/devices/group./use_read_buffer_limit +Date: Dec 10, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: Enable the use of global read buffer limit for the group. See DSA + spec v1.2 9.2.18 GRPCFG Use Global Read Buffer Limit. + It's not visible when the device does not support Read Buffer + allocation control. + +What: /sys/bus/dsa/devices/group./read_buffers_allowed +Date: Dec 10, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: Indicates max number of read buffers that may be in use at one time + by all engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read + Buffers Allowed. + It's not visible when the device does not support Read Buffer + allocation control. + +What: /sys/bus/dsa/devices/group./read_buffers_reserved +Date: Dec 10, 2021 +KernelVersion: 5.17.0 +Contact: dmaengine@vger.kernel.org +Description: Indicates the number of Read Buffers reserved for the use of + engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read Buffers + Reserved. + It's not visible when the device does not support Read Buffer + allocation control. + +What: /sys/bus/dsa/devices/group./desc_progress_limit +Date: Sept 14, 2022 +KernelVersion: 6.0.0 +Contact: dmaengine@vger.kernel.org +Description: Allows control of the number of work descriptors that can be + concurrently processed by an engine in the group as a fraction + of the Maximum Work Descriptors in Progress value specified in + the ENGCAP register. The acceptable values are 0 (default), + 1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of + the max value). It's visible only on platforms that support + the capability. + +What: /sys/bus/dsa/devices/group./batch_progress_limit +Date: Sept 14, 2022 +KernelVersion: 6.0.0 +Contact: dmaengine@vger.kernel.org +Description: Allows control of the number of batch descriptors that can be + concurrently processed by an engine in the group as a fraction + of the Maximum Batch Descriptors in Progress value specified in + the ENGCAP register. The acceptable values are 0 (default), + 1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of + the max value). It's visible only on platforms that support + the capability. diff --git a/Documentation/ABI/stable/sysfs-driver-dma-ioatdma b/Documentation/ABI/stable/sysfs-driver-dma-ioatdma new file mode 100644 index 000000000..3a4e2cd0d --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-dma-ioatdma @@ -0,0 +1,30 @@ +What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dmachan/quickdata/cap +Date: December 3, 2009 +KernelVersion: 2.6.32 +Contact: dmaengine@vger.kernel.org +Description: Capabilities the DMA supports.Currently there are DMA_PQ, DMA_PQ_VAL, + DMA_XOR,DMA_XOR_VAL,DMA_INTERRUPT. + +What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dmachan/quickdata/ring_active +Date: December 3, 2009 +KernelVersion: 2.6.32 +Contact: dmaengine@vger.kernel.org +Description: The number of descriptors active in the ring. + +What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dmachan/quickdata/ring_size +Date: December 3, 2009 +KernelVersion: 2.6.32 +Contact: dmaengine@vger.kernel.org +Description: Descriptor ring size, total number of descriptors available. + +What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dmachan/quickdata/version +Date: December 3, 2009 +KernelVersion: 2.6.32 +Contact: dmaengine@vger.kernel.org +Description: Version of ioatdma device. + +What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dmachan/quickdata/intr_coalesce +Date: August 8, 2017 +KernelVersion: 4.14 +Contact: dmaengine@vger.kernel.org +Description: Tune-able interrupt delay value per channel basis. diff --git a/Documentation/ABI/stable/sysfs-driver-firmware-zynqmp b/Documentation/ABI/stable/sysfs-driver-firmware-zynqmp new file mode 100644 index 000000000..c3fec3c83 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-firmware-zynqmp @@ -0,0 +1,256 @@ +What: /sys/devices/platform/firmware\:zynqmp-firmware/ggs* +Date: March 2020 +KernelVersion: 5.6 +Contact: "Jolly Shah" +Description: + Read/Write PMU global general storage register value, + GLOBAL_GEN_STORAGE{0:3}. + Global general storage register that can be used + by system to pass information between masters. + + The register is reset during system or power-on + resets. Three registers are used by the FSBL and + other Xilinx software products: GLOBAL_GEN_STORAGE{4:6}. + + Usage:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0 + # echo > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0 + + Example:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0 + # echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0 + +Users: Xilinx + +What: /sys/devices/platform/firmware\:zynqmp-firmware/pggs* +Date: March 2020 +KernelVersion: 5.6 +Contact: "Jolly Shah" +Description: + Read/Write PMU persistent global general storage register + value, PERS_GLOB_GEN_STORAGE{0:3}. + Persistent global general storage register that + can be used by system to pass information between + masters. + + This register is only reset by the power-on reset + and maintains its value through a system reset. + Four registers are used by the FSBL and other Xilinx + software products: PERS_GLOB_GEN_STORAGE{4:7}. + Register is reset only by a POR reset. + + Usage:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0 + # echo > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0 + + Example:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0 + # echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0 + +Users: Xilinx + +What: /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope +Date: March 2020 +KernelVersion: 5.6 +Contact: "Jolly Shah" +Description: + This sysfs interface allows to set the shutdown scope for the + next shutdown request. When the next shutdown is performed, the + platform specific portion of PSCI-system_off can use the chosen + shutdown scope. + + Following are available shutdown scopes(subtypes): + + subsystem: + Only the APU along with all of its peripherals + not used by other processing units will be + shut down. This may result in the FPD power + domain being shut down provided that no other + processing unit uses FPD peripherals or DRAM. + ps_only: + The complete PS will be shut down, including the + RPU, PMU, etc. Only the PL domain (FPGA) + remains untouched. + system: + The complete system/device is shut down. + + Usage:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope + # echo > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope + + Example:: + + # cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope + # echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope + +Users: Xilinx + +What: /sys/devices/platform/firmware\:zynqmp-firmware/health_status +Date: March 2020 +KernelVersion: 5.6 +Contact: "Jolly Shah" +Description: + This sysfs interface allows to set the health status. If PMUFW + is compiled with CHECK_HEALTHY_BOOT, it will check the healthy + bit on FPD WDT expiration. If healthy bit is set by a user + application running in Linux, PMUFW will do APU only restart. If + healthy bit is not set during FPD WDT expiration, PMUFW will do + system restart. + + Usage: + + Set healthy bit:: + + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status + + Unset healthy bit:: + + # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status + +Users: Xilinx + +What: /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id +Date: Feb 2022 +KernelVersion: 5.18 +Contact: "Ronak Jain" +Description: + This sysfs interface allows user to configure features at + runtime. The user can enable or disable features running at + firmware as well as the user can configure the parameters of + the features at runtime. The supported features are over + temperature and external watchdog. Here, the external watchdog + is completely different than the /dev/watchdog as the external + watchdog is running on the firmware and it is used to monitor + the health of firmware not APU(Linux). Also, the external + watchdog is interfaced outside of the zynqmp soc. + + The supported config ids are for the feature configuration is, + 1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or + disable the over temperature feature. + 2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the + over temperature limit in Degree Celsius. + 3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable + the external watchdog feature. + 4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the + external watchdog feature. + + Usage: + + Select over temperature config ID to enable/disable feature + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + + Check over temperature config ID is selected or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + The expected result is 1. + + Select over temperature config ID to configure OT limit + # echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + + Check over temperature config ID is selected or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + The expected result is 2. + + Select external watchdog config ID to enable/disable feature + # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + + Check external watchdog config ID is selected or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + The expected result is 3. + + Select external watchdog config ID to configure time interval + # echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + + Check external watchdog config ID is selected or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + The expected result is 4. + +Users: Xilinx + +What: /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value +Date: Feb 2022 +KernelVersion: 5.18 +Contact: "Ronak Jain" +Description: + This sysfs interface allows to configure features at runtime. + The user can enable or disable features running at firmware. + Also, the user can configure the parameters of the features + at runtime. The supported features are over temperature and + external watchdog. Here, the external watchdog is completely + different than the /dev/watchdog as the external watchdog is + running on the firmware and it is used to monitor the health + of firmware not APU(Linux). Also, the external watchdog is + interfaced outside of the zynqmp soc. + + By default the features are disabled in the firmware. The user + can enable features by querying appropriate config id of the + features. + + The default limit for the over temperature is 90 Degree Celsius. + The default timer interval for the external watchdog is 570ms. + + The supported config ids are for the feature configuration is, + 1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or + disable the over temperature feature. + 2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the + over temperature limit in Degree Celsius. + 3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable + the external watchdog feature. + 4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the + external watchdog feature. + + Usage: + + Enable over temperature feature + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the over temperature feature is enabled or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 1. + + Disable over temperature feature + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the over temperature feature is disabled or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 0. + + Configure over temperature limit to 50 Degree Celsius + # echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 50 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the over temperature limit is configured or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 50. + + Enable external watchdog feature + # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the external watchdog feature is enabled or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 1. + + Disable external watchdog feature + # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the external watchdog feature is disabled or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 0. + + Configure external watchdog timer interval to 500ms + # echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id + # echo 500 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + + Check whether the external watchdog timer interval is configured or not + # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value + The expected result is 500. + +Users: Xilinx diff --git a/Documentation/ABI/stable/sysfs-driver-ib_srp b/Documentation/ABI/stable/sysfs-driver-ib_srp new file mode 100644 index 000000000..bada15a32 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-ib_srp @@ -0,0 +1,192 @@ +What: /sys/class/infiniband_srp/srp--/add_target +Date: January 2, 2006 +KernelVersion: 2.6.15 +Contact: linux-rdma@vger.kernel.org +Description: Interface for making ib_srp connect to a new target. + One can request ib_srp to connect to a new target by writing + a comma-separated list of login parameters to this sysfs + attribute. The supported parameters are: + + * id_ext, a 16-digit hexadecimal number specifying the eight + byte identifier extension in the 16-byte SRP target port + identifier. The target port identifier is sent by ib_srp + to the target in the SRP_LOGIN_REQ request. + * ioc_guid, a 16-digit hexadecimal number specifying the eight + byte I/O controller GUID portion of the 16-byte target port + identifier. + * dgid, a 32-digit hexadecimal number specifying the + destination GID. + * pkey, a four-digit hexadecimal number specifying the + InfiniBand partition key. + * service_id, a 16-digit hexadecimal number specifying the + InfiniBand service ID used to establish communication with + the SRP target. How to find out the value of the service ID + is specified in the documentation of the SRP target. + * max_sect, a decimal number specifying the maximum number of + 512-byte sectors to be transferred via a single SCSI command. + * max_cmd_per_lun, a decimal number specifying the maximum + number of outstanding commands for a single LUN. + * io_class, a hexadecimal number specifying the SRP I/O class. + Must be either 0xff00 (rev 10) or 0x0100 (rev 16a). The I/O + class defines the format of the SRP initiator and target + port identifiers. + * initiator_ext, a 16-digit hexadecimal number specifying the + identifier extension portion of the SRP initiator port + identifier. This data is sent by the initiator to the target + in the SRP_LOGIN_REQ request. + * cmd_sg_entries, a number in the range 1..255 that specifies + the maximum number of data buffer descriptors stored in the + SRP_CMD information unit itself. With allow_ext_sg=0 the + parameter cmd_sg_entries defines the maximum S/G list length + for a single SRP_CMD, and commands whose S/G list length + exceeds this limit after S/G list collapsing will fail. + * allow_ext_sg, whether ib_srp is allowed to include a partial + memory descriptor list in an SRP_CMD instead of the entire + list. If a partial memory descriptor list has been included + in an SRP_CMD the remaining memory descriptors are + communicated from initiator to target via an additional RDMA + transfer. Setting allow_ext_sg to 1 increases the maximum + amount of data that can be transferred between initiator and + target via a single SCSI command. Since not all SRP target + implementations support partial memory descriptor lists the + default value for this option is 0. + * sg_tablesize, a number in the range 1..2048 specifying the + maximum S/G list length the SCSI layer is allowed to pass to + ib_srp. Specifying a value that exceeds cmd_sg_entries is + only safe with partial memory descriptor list support enabled + (allow_ext_sg=1). + * comp_vector, a number in the range 0..n-1 specifying the + MSI-X completion vector of the first RDMA channel. Some + HCA's allocate multiple (n) MSI-X vectors per HCA port. If + the IRQ affinity masks of these interrupts have been + configured such that each MSI-X interrupt is handled by a + different CPU then the comp_vector parameter can be used to + spread the SRP completion workload over multiple CPU's. + * tl_retry_count, a number in the range 2..7 specifying the + IB RC retry count. + * queue_size, the maximum number of commands that the + initiator is allowed to queue per SCSI host. The default + value for this parameter is 62. The lowest supported value + is 2. + * max_it_iu_size, a decimal number specifying the maximum + initiator to target information unit length. + +What: /sys/class/infiniband_srp/srp--/ibdev +Date: January 2, 2006 +KernelVersion: 2.6.15 +Contact: linux-rdma@vger.kernel.org +Description: HCA name (). + +What: /sys/class/infiniband_srp/srp--/port +Date: January 2, 2006 +KernelVersion: 2.6.15 +Contact: linux-rdma@vger.kernel.org +Description: HCA port number (). + +What: /sys/class/scsi_host/host/allow_ext_sg +Date: May 19, 2011 +KernelVersion: 2.6.39 +Contact: linux-rdma@vger.kernel.org +Description: Whether ib_srp is allowed to include a partial memory + descriptor list in an SRP_CMD when communicating with an SRP + target. + +What: /sys/class/scsi_host/host/ch_count +Date: April 1, 2015 +KernelVersion: 3.19 +Contact: linux-rdma@vger.kernel.org +Description: Number of RDMA channels used for communication with the SRP + target. + +What: /sys/class/scsi_host/host/cmd_sg_entries +Date: May 19, 2011 +KernelVersion: 2.6.39 +Contact: linux-rdma@vger.kernel.org +Description: Maximum number of data buffer descriptors that may be sent to + the target in a single SRP_CMD request. + +What: /sys/class/scsi_host/host/comp_vector +Date: September 2, 2013 +KernelVersion: 3.11 +Contact: linux-rdma@vger.kernel.org +Description: Completion vector used for the first RDMA channel. + +What: /sys/class/scsi_host/host/dgid +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: InfiniBand destination GID used for communication with the SRP + target. Differs from orig_dgid if port redirection has happened. + +What: /sys/class/scsi_host/host/id_ext +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: Eight-byte identifier extension portion of the 16-byte target + port identifier. + +What: /sys/class/scsi_host/host/ioc_guid +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: Eight-byte I/O controller GUID portion of the 16-byte target + port identifier. + +What: /sys/class/scsi_host/host/local_ib_device +Date: November 29, 2006 +KernelVersion: 2.6.19 +Contact: linux-rdma@vger.kernel.org +Description: Name of the InfiniBand HCA used for communicating with the + SRP target. + +What: /sys/class/scsi_host/host/local_ib_port +Date: November 29, 2006 +KernelVersion: 2.6.19 +Contact: linux-rdma@vger.kernel.org +Description: Number of the HCA port used for communicating with the + SRP target. + +What: /sys/class/scsi_host/host/orig_dgid +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: InfiniBand destination GID specified in the parameters + written to the add_target sysfs attribute. + +What: /sys/class/scsi_host/host/pkey +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: A 16-bit number representing the InfiniBand partition key used + for communication with the SRP target. + +What: /sys/class/scsi_host/host/req_lim +Date: October 20, 2010 +KernelVersion: 2.6.36 +Contact: linux-rdma@vger.kernel.org +Description: Number of requests ib_srp can send to the target before it has + to wait for more credits. For more information see also the + SRP credit algorithm in the SRP specification. + +What: /sys/class/scsi_host/host/service_id +Date: June 17, 2006 +KernelVersion: 2.6.17 +Contact: linux-rdma@vger.kernel.org +Description: InfiniBand service ID used for establishing communication with + the SRP target. + +What: /sys/class/scsi_host/host/sgid +Date: February 1, 2014 +KernelVersion: 3.13 +Contact: linux-rdma@vger.kernel.org +Description: InfiniBand GID of the source port used for communication with + the SRP target. + +What: /sys/class/scsi_host/host/zero_req_lim +Date: September 20, 2006 +KernelVersion: 2.6.18 +Contact: linux-rdma@vger.kernel.org +Description: Number of times the initiator had to wait before sending a + request to the target because it ran out of credits. For more + information see also the SRP credit algorithm in the SRP + specification. diff --git a/Documentation/ABI/stable/sysfs-driver-mlxreg-io b/Documentation/ABI/stable/sysfs-driver-mlxreg-io new file mode 100644 index 000000000..af0cbf143 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-mlxreg-io @@ -0,0 +1,544 @@ +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_health +Date: June 2018 +KernelVersion: 4.19 +Contact: Vadim Pasternak +Description: This file shows ASIC health status. The possible values are: + 0 - health failed, 2 - health OK, 3 - ASIC in booting state. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version +Date: June 2018 +KernelVersion: 4.19 +Contact: Vadim Pasternak +Description: These files show with which CPLD versions have been burned + on carrier and switch boards. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/fan_dir +Date: December 2018 +KernelVersion: 5.0 +Contact: Vadim Pasternak +Description: This file shows the system fans direction: + forward direction - relevant bit is set 0; + reversed direction - relevant bit is set 1. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version +Date: November 2018 +KernelVersion: 5.0 +Contact: Vadim Pasternak +Description: These files show with which CPLD versions have been burned + on LED or Gearbox board. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_enable +Date: November 2018 +KernelVersion: 5.0 +Contact: Vadim Pasternak +Description: These files enable and disable the access to the JTAG domain. + By default access to the JTAG domain is disabled. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/select_iio +Date: June 2018 +KernelVersion: 4.19 +Contact: Vadim Pasternak +Description: This file allows iio devices selection. + + Attribute select_iio can be written with 0 or with 1. It + selects which one of iio devices can be accessed. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu1_on + /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu2_on + /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_cycle + /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_down +Date: June 2018 +KernelVersion: 4.19 +Contact: Vadim Pasternak +Description: These files allow asserting system power cycling, switching + power supply units on and off and system's main power domain + shutdown. + Expected behavior: + When pwr_cycle is written 1: auxiliary power domain will go + down and after short period (about 1 second) up. + When psu1_on or psu2_on is written 1, related unit will be + disconnected from the power source, when written 0 - connected. + If both are written 1 - power supplies main power domain will + go down. + When pwr_down is written 1, system's main power domain will go + down. + + The files are write only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_aux_pwr_or_ref +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_asic_thermal +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_hotswap_or_halt +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_hotswap_or_wd +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_fw_reset +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_long_pb +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_main_pwr_fail +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_short_pb +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_reset +Date: June 2018 +KernelVersion: 4.19 +Contact: Vadim Pasternak +Description: These files show the system reset cause, as following: power + auxiliary outage or power refresh, ASIC thermal shutdown, halt, + hotswap, watchdog, firmware reset, long press power button, + short press power button, software reset. Value 1 in file means + this is reset cause, 0 - otherwise. Only one of the above + causes could be 1 at the same time, representing only last + reset cause. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_pwr_fail +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_from_comex +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_system +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_voltmon_upgrade_fail +Date: November 2018 +KernelVersion: 5.0 +Contact: Vadim Pasternak +Description: These files show the system reset cause, as following: ComEx + power fail, reset from ComEx, system platform reset, reset + due to voltage monitor devices upgrade failure, + Value 1 in file means this is reset cause, 0 - otherwise. + Only one bit could be 1 at the same time, representing only + the last reset cause. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version +Date: November 2018 +KernelVersion: 5.0 +Contact: Vadim Pasternak +Description: These files show with which CPLD versions have been burned + on LED board. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_thermal +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_wd +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_from_asic +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_reload_bios +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sff_wd +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_swb_wd +Date: June 2019 +KernelVersion: 5.3 +Contact: Vadim Pasternak +Description: These files show the system reset cause, as following: + COMEX thermal shutdown; wathchdog power off or reset was derived + by one of the next components: COMEX, switch board or by Small Form + Factor mezzanine, reset requested from ASIC, reset caused by BIOS + reload. Value 1 in file means this is reset cause, 0 - otherwise. + Only one of the above causes could be 1 at the same time, representing + only last reset cause. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config1 +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config2 +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: These files show system static topology identification + like system's static I2C topology, number and type of FPGA + devices within the system and so on. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_ac_pwr_fail +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_platform +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_soc +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_pwr_off +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: These files show the system reset causes, as following: reset + due to AC power failure, reset invoked from software by + assertion reset signal through CPLD. reset caused by signal + asserted by SOC through ACPI register, reset invoked from + software by assertion power off signal through CPLD. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pcie_asic_reset_dis +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: This file allows to retain ASIC up during PCIe root complex + reset, when attribute is set 1. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/vpd_wp +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: This file allows to overwrite system VPD hardware write + protection when attribute is set 1. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/voltreg_update_status +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: This file exposes the configuration update status of burnable + voltage regulator devices. The status values are as following: + 0 - OK; 1 - CRC failure; 2 = I2C failure; 3 - in progress. + + The file is read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/ufm_version +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: This file exposes the firmware version of burnable voltage + regulator devices. + + The file is read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_pn +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_pn +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_pn +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_pn +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version_min +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version_min +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version_min +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version_min +Date: July 2020 +KernelVersion: 5.9 +Contact: Vadim Pasternak +Description: These files show with which CPLD part numbers and minor + versions have been burned CPLD devices equipped on a + system. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_active_image +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_auth_fail +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_upgrade_fail +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: The files represent BIOS statuses: + + bios_active_image: location of current active BIOS image: + 0: Top, 1: Bottom. + The reported value should correspond to value expected by OS + in case of BIOS safe mode is 0. This bit is related to Intel + top-swap feature of DualBios on the same flash. + + bios_auth_fail: BIOS upgrade is failed because provided BIOS + image is not signed correctly. + + bios_upgrade_fail: BIOS upgrade is failed by some other + reason not because authentication. For example due to + physical SPI flash problem. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_enable +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_enable +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files allow line cards enable state control. + Expected behavior: + When lc{n}_enable is written 1, related line card is released + from the reset state, when 0 - is hold in reset state. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_pwr +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_pwr +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files switching line cards power on and off. + Expected behavior: + When lc{n}_pwr is written 1, related line card is powered + on, when written 0 - powered off. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_rst_mask +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_rst_mask +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files clear line card reset bit enforced by ASIC, when it + sets it due to some abnormal ASIC behavior. + Expected behavior: + When lc{n}_rst_mask is written 1, related line card reset bit + is cleared, when written 0 - no effect. + + The files are write only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/os_started +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: This file, when written 1, indicates to programmable devices + that OS is taking control over it. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pm_mgmt_en +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: This file assigns power management control ownership. + When power management control is provided by hardware, hardware + will automatically power off one or more line previously + powered line cards in case system power budget is getting + insufficient. It could be in case when some of power units lost + power good state. + When pm_mgmt_en is written 1, power management control by + software is enabled, 0 - power management control by hardware. + Note that for any setting of pm_mgmt_en attribute hardware will + not allow to power on any new line card in case system power + budget is insufficient. + Same in case software will try to power on several line cards + at once - hardware will power line cards while system has + enough power budget. + Default is 0. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu3_on +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu4_on +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files switching power supply units on and off. + Expected behavior: + When psu3_on or psu4_on is written 1, related unit will be + disconnected from the power source, when written 0 - connected. + + The files are write only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/shutdown_unlock +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: This file allows to unlock ASIC after thermal shutdown event. + When system thermal shutdown is enforced by ASIC, ASIC is + getting locked and after system boot it will not be available. + Software can decide to unlock it by setting this attribute to + 1 and then perform system power cycle by setting pwr_cycle + attribute to 1 (power cycle of main power domain). + Before setting shutdown_unlock to 1 it is recommended to + validate that system reboot cause is reset_asic_thermal or + reset_thermal_spc_or_pciesw. + In case shutdown_unlock is not set 1, the only way to release + ASIC from locking - is full system power cycle through the + external power distribution unit. + Default is 1. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_pn +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version_min +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files show with which CPLD major and minor versions + and part number has been burned CPLD device on line card. + + The files are read only. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_pn +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version_min +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files show with which FPGA major and minor versions + and part number has been burned FPGA device on line card. + + The files are read only. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/vpd_wp +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: This file allow to overwrite line card VPD hardware write + protection mode. When attribute is set 1 - write protection is + disabled, when 0 - enabled. + Default is 0. + If the system is in locked-down mode writing this file will not + be allowed. + The purpose if this file is to allow line card VPD burning + during production flow. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_aux_pwr_or_ref +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_dc_dc_pwr_fail +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_fpga_not_done +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_from_chassis +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_line_card +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_pwr_off_from_chassis +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files show the line reset cause, as following: power + auxiliary outage or power refresh, DC-to-DC power failure, FPGA reset + failed, line card reset failed, power off from chassis. + Value 1 in file means this is reset cause, 0 - otherwise. Only one of + the above causes could be 1 at the same time, representing only last + reset cause. + + The files are read only. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld_upgrade_en +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_upgrade_en +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files allow CPLD and FPGA burning. Value 1 in file means burning + is enabled, 0 - otherwise. + If the system is in locked-down mode writing these files will + not be allowed. + The purpose of these files to allow line card CPLD and FPGA + upgrade through the JTAG daisy-chain. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/qsfp_pwr_en +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/pwr_en +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files allow to power on/off all QSFP ports and whole line card. + The attributes are set 1 for power on, 0 - for power off. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/agb_spi_burn_en +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_spi_burn_en +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files allow gearboxes and FPGA SPI flash burning. + The attributes are set 1 to enable burning, 0 - to disable. + If the system is in locked-down mode writing these files will + not be allowed. + The purpose of these files to allow line card Gearboxes and FPGA + burning during production flow. + + The file is read/write. + +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/max_power +What: /sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/config +Date: October 2021 +KernelVersion: 5.16 +Contact: Vadim Pasternak +Description: These files provide the maximum powered required for line card + feeding and line card configuration Id. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/phy_reset +Date: May 2022 +KernelVersion: 5.19 +Contact: Vadim Pasternak +Description: This file allows to reset PHY 88E1548 when attribute is set 0 + due to some abnormal PHY behavior. + Expected behavior: + When phy_reset is written 1, all PHY 88E1548 are released + from the reset state, when 0 - are hold in reset state. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/mac_reset +Date: May 2022 +KernelVersion: 5.19 +Contact: Vadim Pasternak +Description: This file allows to reset ASIC MT52132 when attribute is set 0 + due to some abnormal ASIC behavior. + Expected behavior: + When mac_reset is written 1, the ASIC MT52132 is released + from the reset state, when 0 - is hold in reset state. + + The files are read/write. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/qsfp_pwr_good +Date: May 2022 +KernelVersion: 5.19 +Contact: Vadim Pasternak +Description: This file shows QSFP ports power status. The value is set to 0 + when one of any QSFP ports is plugged. The value is set to 1 when + there are no any QSFP ports are plugged. + The possible values are: + 0 - Power good, 1 - Not power good. + + The files are read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_health +Date: July 2022 +KernelVersion: 5.20 +Contact: Vadim Pasternak +Description: This file shows 2-nd ASIC health status. The possible values are: + 0 - health failed, 2 - health OK, 3 - ASIC in booting state. + + The file is read only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_reset +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_reset +Date: July 2022 +KernelVersion: 5.20 +Contact: Vadim Pasternak +Description: These files allow to each of ASICs by writing 1. + + The files are write only. + + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/comm_chnl_ready +Date: July 2022 +KernelVersion: 5.20 +Contact: Vadim Pasternak +Description: This file is used to indicate remote end (for example BMC) that system + host CPU is ready for sending telemetry data to remote end. + For indication the file should be written 1. + + The file is write only. + +What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config3 +Date: January 2020 +KernelVersion: 5.6 +Contact: Vadim Pasternak +Description: The file indicates COME module hardware configuration. + The value is pushed by hardware through GPIO pins. + The purpose is to expose some minor BOM changes for the same system SKU. + + The file is read only. diff --git a/Documentation/ABI/stable/sysfs-driver-qla2xxx b/Documentation/ABI/stable/sysfs-driver-qla2xxx new file mode 100644 index 000000000..9a59d8449 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-qla2xxx @@ -0,0 +1,8 @@ +What: /sys/bus/pci/drivers/qla2xxx/.../devices/* +Date: September 2009 +Contact: QLogic Linux Driver +Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to + signal a firmware-dump has been generated by the driver and is + ready for retrieval. +Users: qla2xxx-udev.sh. Proposed changes should be mailed to + linux-driver@qlogic.com diff --git a/Documentation/ABI/stable/sysfs-driver-speakup b/Documentation/ABI/stable/sysfs-driver-speakup new file mode 100644 index 000000000..dc2a6ba16 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-speakup @@ -0,0 +1,386 @@ +What: /sys/accessibility/speakup/attrib_bleep +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Beeps the PC speaker when there is an attribute change such as + foreground or background color when using speakup review + commands. One = on, zero = off. + +What: /sys/accessibility/speakup/bell_pos +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This works much like a typewriter bell. If for example 72 is + echoed to bell_pos, it will beep the PC speaker when typing on + a line past character 72. + +What: /sys/accessibility/speakup/bleeps +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This controls whether one hears beeps through the PC speaker + when using speakup's review commands. + TODO: what values does it accept? + +What: /sys/accessibility/speakup/bleep_time +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This controls the duration of the PC speaker beeps speakup + produces. + TODO: What are the units? Jiffies? + +What: /sys/accessibility/speakup/cursor_time +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This controls cursor delay when using arrow keys. When a + connection is very slow, with the default setting, when moving + with the arrows, or backspacing etc. speakup says the incorrect + characters. Set this to a higher value to adjust for the delay + and better synchronisation between cursor position and speech. + +What: /sys/accessibility/speakup/delimiters +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Delimit a word from speakup. + TODO: add more info + +What: /sys/accessibility/speakup/ex_num +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup/key_echo +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Controls if speakup speaks keys when they are typed. One = on, + zero = off or don't echo keys. + +What: /sys/accessibility/speakup/keymap +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Speakup keymap remaps keys to Speakup functions. + It uses a binary + format. A special program called genmap is needed to compile a + textual keymap into the binary format which is then loaded into + /sys/accessibility/speakup/keymap. + +What: /sys/accessibility/speakup/no_interrupt +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Controls if typing interrupts output from speakup. With + no_interrupt set to zero, typing on the keyboard will interrupt + speakup if for example + the say screen command is used before the + entire screen is read. + + With no_interrupt set to one, if the say + screen command is used, and one then types on the keyboard, + speakup will continue to say the whole screen regardless until + it finishes. + +What: /sys/accessibility/speakup/punc_all +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This is a list of all the punctuation speakup should speak when + punc_level is set to four. + +What: /sys/accessibility/speakup/punc_level +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Controls the level of punctuation spoken as the screen is + displayed, not reviewed. Levels range from zero no punctuation, + to four, all punctuation. One corresponds to punc_some, two + corresponds to punc_most, and three as well as four both + correspond to punc_all. Some hardware synthesizers may have + different levels each corresponding to three and four for + punc_level. Also note that if punc_level is set to zero, and + key_echo is set to one, typed punctuation is still spoken as it + is typed. + +What: /sys/accessibility/speakup/punc_most +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This is a list of all the punctuation speakup should speak when + punc_level is set to two. + +What: /sys/accessibility/speakup/punc_some +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This is a list of all the punctuation speakup should speak when + punc_level is set to one. + +What: /sys/accessibility/speakup/reading_punc +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Almost the same as punc_level, the differences being that + reading_punc controls the level of punctuation when reviewing + the screen with speakup's screen review commands. The other + difference is that reading_punc set to three speaks punc_all, + and reading_punc set to four speaks all punctuation, including + spaces. + +What: /sys/accessibility/speakup/repeats +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: A list of characters speakup repeats. Normally, when there are + more than three characters in a row, speakup + just reads three of + those characters. For example, "......" would be read as dot, + dot, dot. If a . is added to the list of characters in repeats, + "......" would be read as dot, dot, dot, times six. + +What: /sys/accessibility/speakup/say_control +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: If set to one, speakup speaks shift, alt and control when those + keys are pressed. If say_control is set to zero, shift, ctrl, + and alt are not spoken when they are pressed. + +What: /sys/accessibility/speakup/say_word_ctl +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup/silent +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup/spell_delay +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This controls how fast a word is spelled + when speakup's say word + review command is pressed twice quickly to speak the current + word being reviewed. Zero just speaks the letters one after + another, while values one through four + seem to introduce more of + a pause between the spelling of each letter by speakup. + +What: /sys/accessibility/speakup/synth +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the synthesizer driver currently in use. Reading + synth returns the synthesizer driver currently in use. Writing + synth switches to the given synthesizer driver, provided it is + either built into the kernel, or already loaded as a module. + +What: /sys/accessibility/speakup/synth_direct +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Sends whatever is written to synth_direct + directly to the speech synthesizer in use, bypassing speakup. + This could be used to make the synthesizer speak + a string, or to + send control sequences to the synthesizer to change how the + synthesizer behaves. + +What: /sys/accessibility/speakup/version +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Reading version returns the version of speakup, and the version + of the synthesizer driver currently in use. + +What: /sys/accessibility/speakup/i18n/announcements +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This file contains various general announcements, most of which + cannot be categorized. You will find messages such as "You + killed Speakup", "I'm alive", "leaving help", "parked", + "unparked", and others. You will also find the names of the + screen edges and cursor tracking modes here. + +What: /sys/accessibility/speakup/i18n/chartab +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO + +What: /sys/accessibility/speakup/i18n/ctl_keys +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Here, you will find names of control keys. These are used with + Speakup's say_control feature. + +What: /sys/accessibility/speakup/i18n/function_names +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Here, you will find a list of names for Speakup functions. + These are used by the help system. For example, suppose that + you have activated help mode, and you pressed + keypad 3. Speakup + says: "keypad 3 is character, say next." + The message "character, say next" names a Speakup function, and + it comes from this function_names file. + +What: /sys/accessibility/speakup/i18n/states +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This file contains names for key states. + Again, these are part of the help system. For instance, if you + had pressed speakup + keypad 3, you would hear: + "speakup keypad 3 is go to bottom edge." + + The speakup key is depressed, so the name of the key state is + speakup. + + This part of the message comes from the states collection. + +What: /sys/accessibility/speakup/i18n/characters +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Through this sys entry, Speakup gives you the ability to change + how Speakup pronounces a given character. You could, for + example, change how some punctuation characters are spoken. You + can even change how Speakup will pronounce certain letters. For + further details see '12. Changing the Pronunciation of + Characters' in Speakup User's Guide (file spkguide.txt in + source). + +What: /sys/accessibility/speakup/i18n/colors +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: When you use the "say attributes" function, Speakup says the + name of the foreground and background colors. These names come + from the i18n/colors file. + +What: /sys/accessibility/speakup/i18n/formatted +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This group of messages contains embedded formatting codes, to + specify the type and width of displayed data. If you change + these, you must preserve all of the formatting codes, and they + must appear in the order used by the default messages. + +What: /sys/accessibility/speakup/i18n/key_names +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Again, key_names is used by Speakup's help system. In the + previous example, Speakup said that you pressed "keypad 3." + This name came from the key_names file. + +What: /sys/accessibility/speakup// +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: In `/sys/accessibility/speakup` is a directory corresponding to + the synthesizer driver currently in use (E.G) `soft` for the + soft driver. This directory contains files which control the + speech synthesizer itself, + as opposed to controlling the speakup + screen reader. The parameters in this directory have the same + names and functions across all + supported synthesizers. The range + of values for freq, pitch, rate, and vol is the same for all + supported synthesizers, with the given range being internally + mapped by the driver to more or less fit the range of values + supported for a given parameter by the individual synthesizer. + Below is a description of values and parameters for soft + synthesizer, which is currently the most commonly used. + +What: /sys/accessibility/speakup//caps_start +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This is the string that is sent to the synthesizer to cause it + to start speaking uppercase letters. For the soft synthesizer + and most others, this causes the pitch of the voice to rise + above the currently set pitch. + +What: /sys/accessibility/speakup//caps_stop +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This is the string sent to the synthesizer to cause it to stop + speaking uppercase letters. In the case of the soft synthesizer + and most others, this returns the pitch of the voice + down to the + currently set pitch. + +What: /sys/accessibility/speakup//delay_time +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup//direct +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Controls if punctuation is spoken by speakup, or by the + synthesizer. + + For example, speakup speaks ">" as "greater", while + the espeak synthesizer used by the soft driver speaks "greater + than". Zero lets speakup speak the punctuation. One lets the + synthesizer itself speak punctuation. + +What: /sys/accessibility/speakup//freq +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the frequency of the speech synthesizer. Range is + 0-9. + +What: /sys/accessibility/speakup//flush_time +KernelVersion: 5.12 +Contact: speakup@linux-speakup.org +Description: Gets or sets the timeout to wait for the synthesizer flush to + complete. This can be used when the cable gets faulty and flush + notifications are getting lost. + +What: /sys/accessibility/speakup//full_time +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup//jiffy_delta +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: This controls how many jiffys the kernel gives to the + synthesizer. Setting this too high can make a system unstable, + or even crash it. + +What: /sys/accessibility/speakup//pitch +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the pitch of the synthesizer. The range is 0-9. + +What: /sys/accessibility/speakup//inflection +KernelVersion: 5.8 +Contact: speakup@linux-speakup.org +Description: Gets or sets the inflection of the synthesizer, i.e. the pitch + range. The range is 0-9. + +What: /sys/accessibility/speakup//punct +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the amount of punctuation spoken by the + synthesizer. The range for the soft driver seems to be 0-2. + TODO: How is this related to speakup's punc_level, or + reading_punc. + +What: /sys/accessibility/speakup//rate +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the rate of the synthesizer. Range is from zero + slowest, to nine fastest. + +What: /sys/accessibility/speakup//tone +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the tone of the speech synthesizer. The range for + the soft driver seems to be 0-2. This seems to make no + difference if using espeak and the espeakup connector. + TODO: does espeakup support different tonalities? + +What: /sys/accessibility/speakup//trigger_time +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: TODO: + +What: /sys/accessibility/speakup//voice +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the voice used by the synthesizer if the + synthesizer can speak in more than one voice. The range for the + soft driver is 0-7. Note that while espeak supports multiple + voices, this parameter will not set the voice when the espeakup + connector is used between speakup and espeak. + +What: /sys/accessibility/speakup//vol +KernelVersion: 2.6 +Contact: speakup@linux-speakup.org +Description: Gets or sets the volume of the speech synthesizer. Range is 0-9, + with zero being the softest, and nine being the loudest. + diff --git a/Documentation/ABI/stable/sysfs-driver-usb-usbtmc b/Documentation/ABI/stable/sysfs-driver-usb-usbtmc new file mode 100644 index 000000000..a9e123ba3 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-usb-usbtmc @@ -0,0 +1,27 @@ +What: /sys/bus/usb/drivers/usbtmc/*/interface_capabilities +What: /sys/bus/usb/drivers/usbtmc/*/device_capabilities +Date: August 2008 +Contact: Greg Kroah-Hartman +Description: + These files show the various USB TMC capabilities as described + by the device itself. The full description of the bitfields + can be found in the USB TMC documents from the USB-IF entitled + "Universal Serial Bus Test and Measurement Class Specification + (USBTMC) Revision 1.0" section 4.2.1.8. + + The files are read only. + + +What: /sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities +What: /sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities +Date: August 2008 +Contact: Greg Kroah-Hartman +Description: + These files show the various USB TMC capabilities as described + by the device itself. The full description of the bitfields + can be found in the USB TMC documents from the USB-IF entitled + "Universal Serial Bus Test and Measurement Class, Subclass + USB488 Specification (USBTMC-USB488) Revision 1.0" section + 4.2.2. + + The files are read only. diff --git a/Documentation/ABI/stable/sysfs-driver-w1_ds2438 b/Documentation/ABI/stable/sysfs-driver-w1_ds2438 new file mode 100644 index 000000000..d2e7681cc --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-w1_ds2438 @@ -0,0 +1,13 @@ +What: /sys/bus/w1/devices/.../page1 +Date: April 2021 +Contact: Luiz Sampaio +Description: read the contents of the page1 of the DS2438 + see Documentation/w1/slaves/w1_ds2438.rst for detailed information +Users: any user space application which wants to communicate with DS2438 + +What: /sys/bus/w1/devices/.../offset +Date: April 2021 +Contact: Luiz Sampaio +Description: write the contents to the offset register of the DS2438 + see Documentation/w1/slaves/w1_ds2438.rst for detailed information +Users: any user space application which wants to communicate with DS2438 diff --git a/Documentation/ABI/stable/sysfs-driver-w1_ds28e04 b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04 new file mode 100644 index 000000000..3e1c1fa8d --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04 @@ -0,0 +1,15 @@ +What: /sys/bus/w1/devices/.../pio +Date: May 2012 +Contact: Markus Franke +Description: read/write the contents of the two PIO's of the DS28E04-100 + see Documentation/w1/slaves/w1_ds28e04.rst for detailed information +Users: any user space application which wants to communicate with DS28E04-100 + + + +What: /sys/bus/w1/devices/.../eeprom +Date: May 2012 +Contact: Markus Franke +Description: read/write the contents of the EEPROM memory of the DS28E04-100 + see Documentation/w1/slaves/w1_ds28e04.rst for detailed information +Users: any user space application which wants to communicate with DS28E04-100 diff --git a/Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 b/Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 new file mode 100644 index 000000000..534e63731 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 @@ -0,0 +1,6 @@ +What: /sys/bus/w1/devices/.../w1_seq +Date: Apr 2015 +Contact: Matt Campbell +Description: Support for the DS28EA00 chain sequence function + see Documentation/w1/slaves/w1_therm.rst for detailed information +Users: any user space application which wants to communicate with DS28EA00 diff --git a/Documentation/ABI/stable/sysfs-firmware-efi-vars b/Documentation/ABI/stable/sysfs-firmware-efi-vars new file mode 100644 index 000000000..46ccd233e --- /dev/null +++ b/Documentation/ABI/stable/sysfs-firmware-efi-vars @@ -0,0 +1,79 @@ +What: /sys/firmware/efi/vars +Date: April 2004 +Contact: Matt Domsch +Description: + This directory exposes interfaces for interactive with + EFI variables. For more information on EFI variables, + see 'Variable Services' in the UEFI specification + (section 7.2 in specification version 2.3 Errata D). + + In summary, EFI variables are named, and are classified + into separate namespaces through the use of a vendor + GUID. They also have an arbitrary binary value + associated with them. + + The efivars module enumerates these variables and + creates a separate directory for each one found. Each + directory has a name of the form "-" + and contains the following files: + + =============== ======================================== + attributes: A read-only text file enumerating the + EFI variable flags. Potential values + include: + + EFI_VARIABLE_NON_VOLATILE + EFI_VARIABLE_BOOTSERVICE_ACCESS + EFI_VARIABLE_RUNTIME_ACCESS + EFI_VARIABLE_HARDWARE_ERROR_RECORD + EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS + + See the EFI documentation for an + explanation of each of these variables. + + data: A read-only binary file that can be read + to attain the value of the EFI variable + + guid: The vendor GUID of the variable. This + should always match the GUID in the + variable's name. + + raw_var: A binary file that can be read to obtain + a structure that contains everything + there is to know about the variable. + For structure definition see "struct + efi_variable" in the kernel sources. + + This file can also be written to in + order to update the value of a variable. + For this to work however, all fields of + the "struct efi_variable" passed must + match byte for byte with the structure + read out of the file, save for the value + portion. + + **Note** the efi_variable structure + read/written with this file contains a + 'long' type that may change widths + depending on your underlying + architecture. + + size: As ASCII representation of the size of + the variable's value. + =============== ======================================== + + + In addition, two other magic binary files are provided + in the top-level directory and are used for adding and + removing variables: + + =============== ======================================== + new_var: Takes a "struct efi_variable" and + instructs the EFI firmware to create a + new variable. + + del_var: Takes a "struct efi_variable" and + instructs the EFI firmware to remove any + variable that has a matching vendor GUID + and variable key name. + =============== ======================================== diff --git a/Documentation/ABI/stable/sysfs-firmware-opal-dump b/Documentation/ABI/stable/sysfs-firmware-opal-dump new file mode 100644 index 000000000..1f74f4532 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-firmware-opal-dump @@ -0,0 +1,46 @@ +What: /sys/firmware/opal/dump +Date: Feb 2014 +Contact: Stewart Smith +Description: + This directory exposes interfaces for interacting with + the FSP and platform dumps through OPAL firmware interface. + + This is only for the powerpc/powernv platform. + + =============== =============================================== + initiate_dump: When '1' is written to it, + we will initiate a dump. + Read this file for supported commands. + + 0xXX-0xYYYY: A directory for dump of type 0xXX and + id 0xYYYY (in hex). The name of this + directory should not be relied upon to + be in this format, only that it's unique + among all dumps. For determining the type + and ID of the dump, use the id and type files. + Do not rely on any particular size of dump + type or dump id. + =============== =============================================== + + Each dump has the following files: + + =============== =============================================== + id: An ASCII representation of the dump ID + in hex (e.g. '0x01') + type: An ASCII representation of the type of + dump in the format "0x%x %s" with the ID + in hex and a description of the dump type + (or 'unknown'). + Type '0xffffffff unknown' is used when + we could not get the type from firmware. + e.g. '0x02 System/Platform Dump' + dump: A binary file containing the dump. + The size of the dump is the size of this file. + acknowledge: When 'ack' is written to this, we will + acknowledge that we've retrieved the + dump to the service processor. It will + then remove it, making the dump + inaccessible. + Reading this file will get a list of + supported actions. + =============== =============================================== diff --git a/Documentation/ABI/stable/sysfs-firmware-opal-elog b/Documentation/ABI/stable/sysfs-firmware-opal-elog new file mode 100644 index 000000000..7c8a61a2d --- /dev/null +++ b/Documentation/ABI/stable/sysfs-firmware-opal-elog @@ -0,0 +1,62 @@ +What: /sys/firmware/opal/elog +Date: Feb 2014 +Contact: Stewart Smith +Description: + This directory exposes error log entries retrieved + through the OPAL firmware interface. + + Each error log is identified by a unique ID and will + exist until explicitly acknowledged to firmware. + + Each log entry has a directory in /sys/firmware/opal/elog. + + Log entries may be purged by the service processor + before retrieved by firmware or retrieved/acknowledged by + Linux if there is no room for more log entries. + + In the event that Linux has retrieved the log entries + but not explicitly acknowledged them to firmware and + the service processor needs more room for log entries, + the only remaining copy of a log message may be in + Linux. + + Typically, a user space daemon will monitor for new + entries, read them out and acknowledge them. + + The service processor may be able to store more log + entries than firmware can, so after you acknowledge + an event from Linux you may instantly get another one + from the queue that was generated some time in the past. + + The raw log format is a binary format. We currently + do not parse this at all in kernel, leaving it up to + user space to solve the problem. In future, we may + do more parsing in kernel and add more files to make + it easier for simple user space processes to extract + more information. + + For each log entry (directory), there are the following + files: + + ============== ================================================ + id: An ASCII representation of the ID of the + error log, in hex - e.g. "0x01". + + type: An ASCII representation of the type id and + description of the type of error log. + Currently just "0x00 PEL" - platform error log. + In the future there may be additional types. + + raw: A read-only binary file that can be read + to get the raw log entry. These are + <16kb, often just hundreds of bytes and + "average" 2kb. + + acknowledge: Writing 'ack' to this file will acknowledge + the error log to firmware (and in turn + the service processor, if applicable). + Shortly after acknowledging it, the log + entry will be removed from sysfs. + Reading this file will list the supported + operations (currently just acknowledge). + ============== ================================================ diff --git a/Documentation/ABI/stable/sysfs-fs-orangefs b/Documentation/ABI/stable/sysfs-fs-orangefs new file mode 100644 index 000000000..affdb114b --- /dev/null +++ b/Documentation/ABI/stable/sysfs-fs-orangefs @@ -0,0 +1,87 @@ +What: /sys/fs/orangefs/perf_counters/* +Date: Jun 2015 +Contact: Mike Marshall +Description: + Counters and settings for various caches. + Read only. + + +What: /sys/fs/orangefs/perf_counter_reset +Date: June 2015 +Contact: Mike Marshall +Description: + echo a 0 or a 1 into perf_counter_reset to + reset all the counters in + /sys/fs/orangefs/perf_counters + except ones with PINT_PERF_PRESERVE set. + + +What: /sys/fs/orangefs/perf_time_interval_secs +Date: Jun 2015 +Contact: Mike Marshall +Description: + Length of perf counter intervals in + seconds. + + +What: /sys/fs/orangefs/perf_history_size +Date: Jun 2015 +Contact: Mike Marshall +Description: + The perf_counters cache statistics have N, or + perf_history_size, samples. The default is + one. + + Every perf_time_interval_secs the (first) + samples are reset. + + If N is greater than one, the "current" set + of samples is reset, and the samples from the + other N-1 intervals remain available. + + +What: /sys/fs/orangefs/op_timeout_secs +Date: Jun 2015 +Contact: Mike Marshall +Description: + Service operation timeout in seconds. + + +What: /sys/fs/orangefs/slot_timeout_secs +Date: Jun 2015 +Contact: Mike Marshall +Description: + "Slot" timeout in seconds. A "slot" + is an indexed buffer in the shared + memory segment used for communication + between the kernel module and userspace. + Slots are requested and waited for, + the wait times out after slot_timeout_secs. + + +What: /sys/fs/orangefs/acache/* +Date: Jun 2015 +Contact: Mike Marshall +Description: + Attribute cache configurable settings. + + +What: /sys/fs/orangefs/ncache/* +Date: Jun 2015 +Contact: Mike Marshall +Description: + Name cache configurable settings. + + +What: /sys/fs/orangefs/capcache/* +Date: Jun 2015 +Contact: Mike Marshall +Description: + Capability cache configurable settings. + + +What: /sys/fs/orangefs/ccache/* +Date: Jun 2015 +Contact: Mike Marshall +Description: + Credential cache configurable settings. diff --git a/Documentation/ABI/stable/sysfs-hypervisor-xen b/Documentation/ABI/stable/sysfs-hypervisor-xen new file mode 100644 index 000000000..748593c64 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-hypervisor-xen @@ -0,0 +1,122 @@ +What: /sys/hypervisor/compilation/compile_date +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Contains the build time stamp of the Xen hypervisor + Might return "" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/compilation/compiled_by +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Contains information who built the Xen hypervisor + Might return "" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/compilation/compiler +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Compiler which was used to build the Xen hypervisor + Might return "" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/properties/capabilities +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Space separated list of supported guest system types. Each type + is in the format: -.- + With: + + ======== ============================================ + : "xen" -- x86: paravirtualized, arm: standard + "hvm" -- x86 only: fully virtualized + : major guest interface version + : minor guest interface version + : architecture, e.g.: + "x86_32": 32 bit x86 guest without PAE + "x86_32p": 32 bit x86 guest with PAE + "x86_64": 64 bit x86 guest + "armv7l": 32 bit arm guest + "aarch64": 64 bit arm guest + ======== ============================================ + +What: /sys/hypervisor/properties/changeset +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Changeset of the hypervisor (git commit) + Might return "" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/properties/features +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Features the Xen hypervisor supports for the guest as defined + in include/xen/interface/features.h printed as a hex value. + +What: /sys/hypervisor/properties/pagesize +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Default page size of the hypervisor printed as a hex value. + Might return "0" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/properties/virtual_start +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Virtual address of the hypervisor as a hex value. + +What: /sys/hypervisor/type +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + Type of hypervisor: + "xen": Xen hypervisor + +What: /sys/hypervisor/uuid +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + UUID of the guest as known to the Xen hypervisor. + +What: /sys/hypervisor/version/extra +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + The Xen version is in the format . + This is the part of it. + Might return "" in case of special security settings + in the hypervisor. + +What: /sys/hypervisor/version/major +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + The Xen version is in the format . + This is the part of it. + +What: /sys/hypervisor/version/minor +Date: March 2009 +KernelVersion: 2.6.30 +Contact: xen-devel@lists.xenproject.org +Description: If running under Xen: + The Xen version is in the format . + This is the part of it. diff --git a/Documentation/ABI/stable/sysfs-kernel-notes b/Documentation/ABI/stable/sysfs-kernel-notes new file mode 100644 index 000000000..2c76ee9e6 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-kernel-notes @@ -0,0 +1,5 @@ +What: /sys/kernel/notes +Date: July 2009 +Contact: +Description: The /sys/kernel/notes file contains the binary representation + of the running vmlinux's .notes section. diff --git a/Documentation/ABI/stable/sysfs-module b/Documentation/ABI/stable/sysfs-module new file mode 100644 index 000000000..41b1f16e8 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-module @@ -0,0 +1,47 @@ +The /sys/module tree consists of the following structure: + +What: /sys/module/ +Description: + The name of the module that is in the kernel. This + module name will always show up if the module is loaded as a + dynamic module. If it is built directly into the kernel, it + will only show up if it has a version or at least one + parameter. + + Note: The conditions of creation in the built-in case are not + by design and may be removed in the future. + +What: /sys/module//parameters +Description: + This directory contains individual files that are each + individual parameters of the module that are able to be + changed at runtime. See the individual module + documentation as to the contents of these parameters and + what they accomplish. + + Note: The individual parameter names and values are not + considered stable, only the fact that they will be + placed in this location within sysfs. See the + individual driver documentation for details as to the + stability of the different parameters. + +What: /sys/module//refcnt +Description: + If the module is able to be unloaded from the kernel, this file + will contain the current reference count of the module. + + Note: If the module is built into the kernel, or if the + CONFIG_MODULE_UNLOAD kernel configuration value is not enabled, + this file will not be present. + +What: /sys/module//srcversion +Date: Jun 2005 +Description: + If the module source has MODULE_VERSION, this file will contain + the checksum of the source code. + +What: /sys/module//version +Date: Jun 2005 +Description: + If the module source has MODULE_VERSION, this file will contain + the version of the source code. diff --git a/Documentation/ABI/stable/sysfs-transport-srp b/Documentation/ABI/stable/sysfs-transport-srp new file mode 100644 index 000000000..ec7af69fe --- /dev/null +++ b/Documentation/ABI/stable/sysfs-transport-srp @@ -0,0 +1,58 @@ +What: /sys/class/srp_remote_ports/port-:/delete +Date: June 1, 2012 +KernelVersion: 3.7 +Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org +Description: Instructs an SRP initiator to disconnect from a target and to + remove all LUNs imported from that target. + +What: /sys/class/srp_remote_ports/port-:/dev_loss_tmo +Date: February 1, 2014 +KernelVersion: 3.13 +Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org +Description: Number of seconds the SCSI layer will wait after a transport + layer error has been observed before removing a target port. + Zero means immediate removal. Setting this attribute to "off" + will disable the dev_loss timer. + +What: /sys/class/srp_remote_ports/port-:/fast_io_fail_tmo +Date: February 1, 2014 +KernelVersion: 3.13 +Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org +Description: Number of seconds the SCSI layer will wait after a transport + layer error has been observed before failing I/O. Zero means + failing I/O immediately. Setting this attribute to "off" will + disable the fast_io_fail timer. + +What: /sys/class/srp_remote_ports/port-:/port_id +Date: June 27, 2007 +KernelVersion: 2.6.24 +Contact: linux-scsi@vger.kernel.org +Description: 16-byte local SRP port identifier in hexadecimal format. An + example: 4c:49:4e:55:58:20:56:49:4f:00:00:00:00:00:00:00. + +What: /sys/class/srp_remote_ports/port-:/reconnect_delay +Date: February 1, 2014 +KernelVersion: 3.13 +Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org +Description: Number of seconds the SCSI layer will wait after a reconnect + attempt failed before retrying. Setting this attribute to + "off" will disable time-based reconnecting. + +What: /sys/class/srp_remote_ports/port-:/roles +Date: June 27, 2007 +KernelVersion: 2.6.24 +Contact: linux-scsi@vger.kernel.org +Description: Role of the remote port. Either "SRP Initiator" or "SRP Target". + +What: /sys/class/srp_remote_ports/port-:/state +Date: February 1, 2014 +KernelVersion: 3.13 +Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org +Description: State of the transport layer used for communication with the + remote port. "running" if the transport layer is operational; + "blocked" if a transport layer error has been encountered but + the fast_io_fail_tmo timer has not yet fired; "fail-fast" + after the fast_io_fail_tmo timer has fired and before the + "dev_loss_tmo" timer has fired; "lost" after the + "dev_loss_tmo" timer has fired and before the port is finally + removed. diff --git a/Documentation/ABI/stable/thermal-notification b/Documentation/ABI/stable/thermal-notification new file mode 100644 index 000000000..9723e8b7a --- /dev/null +++ b/Documentation/ABI/stable/thermal-notification @@ -0,0 +1,4 @@ +What: A notification mechanism for thermal related events +Description: + This interface enables notification for thermal related events. + The notification is in the form of a netlink event. diff --git a/Documentation/ABI/stable/vdso b/Documentation/ABI/stable/vdso new file mode 100644 index 000000000..951838d42 --- /dev/null +++ b/Documentation/ABI/stable/vdso @@ -0,0 +1,35 @@ +What: vDSO +Date: July 2011 +KernelVersion: 3.0 +Contact: Andy Lutomirski +Description: + +On some architectures, when the kernel loads any userspace program it +maps an ELF DSO into that program's address space. This DSO is called +the vDSO and it often contains useful and highly-optimized alternatives +to real syscalls. + +These functions are called just like ordinary C function according to +your platform's ABI. Call them from a sensible context. (For example, +if you set CS on x86 to something strange, the vDSO functions are +within their rights to crash.) In addition, if you pass a bad +pointer to a vDSO function, you might get SIGSEGV instead of -EFAULT. + +To find the DSO, parse the auxiliary vector passed to the program's +entry point. The AT_SYSINFO_EHDR entry will point to the vDSO. + +The vDSO uses symbol versioning; whenever you request a symbol from the +vDSO, specify the version you are expecting. + +Programs that dynamically link to glibc will use the vDSO automatically. +Otherwise, you can use the reference parser in +tools/testing/selftests/vDSO/parse_vdso.c. + +Unless otherwise noted, the set of symbols with any given version and the +ABI of those symbols is considered stable. It may vary across architectures, +though. + +Note: + As of this writing, this ABI documentation as been confirmed for x86_64. + The maintainers of the other vDSO-using architectures should confirm + that it is correct for their architecture. diff --git a/Documentation/ABI/testing/configfs-acpi b/Documentation/ABI/testing/configfs-acpi new file mode 100644 index 000000000..c09b640c3 --- /dev/null +++ b/Documentation/ABI/testing/configfs-acpi @@ -0,0 +1,52 @@ +What: /config/acpi +Date: July 2016 +KernelVersion: 4.8 +Contact: linux-acpi@vger.kernel.org +Description: + This represents the ACPI subsystem entry point directory. It + contains sub-groups corresponding to ACPI configurable options. + +What: /config/acpi/table +Date: July 2016 +KernelVersion: 4.8 +Description: + + This group contains the configuration for user defined ACPI + tables. The attributes of a user define table are: + + aml + - a binary attribute that the user can use to + fill in the ACPI aml definitions. Once the aml + data is written to this file and the file is + closed the table will be loaded and ACPI devices + will be enumerated. To check if the operation is + successful the user must check the error code + for close(). If the operation is successful, + subsequent writes to this attribute will fail. + + The rest of the attributes are read-only and are valid only + after the table has been loaded by filling the aml entry: + + signature + - ASCII table signature + + length + - length of table in bytes, including the header + + revision + - ACPI Specification minor version number + + oem_id + - ASCII OEM identification + + oem_table_id + - ASCII OEM table identification + + oem_revision + - OEM revision number + + asl_compiler_id + - ASCII ASL compiler vendor ID + + asl_compiler_revision + - ASL compiler version diff --git a/Documentation/ABI/testing/configfs-iio b/Documentation/ABI/testing/configfs-iio new file mode 100644 index 000000000..1637fcb50 --- /dev/null +++ b/Documentation/ABI/testing/configfs-iio @@ -0,0 +1,34 @@ +What: /config/iio +Date: October 2015 +KernelVersion: 4.4 +Contact: linux-iio@vger.kernel.org +Description: + This represents Industrial IO configuration entry point + directory. It contains sub-groups corresponding to IIO + objects. + +What: /config/iio/triggers +Date: October 2015 +KernelVersion: 4.4 +Description: + Industrial IO software triggers directory. + +What: /config/iio/triggers/hrtimers +Date: October 2015 +KernelVersion: 4.4 +Description: + High resolution timers directory. Creating a directory here + will result in creating a hrtimer trigger in the IIO subsystem. + +What: /config/iio/devices +Date: April 2016 +KernelVersion: 4.7 +Description: + Industrial IO software devices directory. + +What: /config/iio/devices/dummy +Date: April 2016 +KernelVersion: 4.7 +Description: + Dummy IIO devices directory. Creating a directory here will result + in creating a dummy IIO device in the IIO subsystem. diff --git a/Documentation/ABI/testing/configfs-most b/Documentation/ABI/testing/configfs-most new file mode 100644 index 000000000..0a4b8649a --- /dev/null +++ b/Documentation/ABI/testing/configfs-most @@ -0,0 +1,241 @@ +What: /sys/kernel/config/most_ +Date: March 8, 2019 +KernelVersion: 5.2 +Description: Interface is used to configure and connect device channels + to component drivers. + + Attributes are visible only when configfs is mounted. To mount + configfs in /sys/kernel/config directory use: + # mount -t configfs none /sys/kernel/config/ + + +What: /sys/kernel/config/most_cdev/ +Date: March 8, 2019 +KernelVersion: 5.2 +Description: + The attributes: + + buffer_size + configure the buffer size for this channel + + subbuffer_size + configure the sub-buffer size for this channel + (needed for synchronous and isochronous data) + + + num_buffers + configure number of buffers used for this + channel + + datatype + configure type of data that will travel over + this channel + + direction + configure whether this link will be an input + or output + + dbr_size + configure DBR data buffer size (this is used + for MediaLB communication only) + + packets_per_xact + configure the number of packets that will be + collected from the network before being + transmitted via USB (this is used for USB + communication only) + + device + name of the device the link is to be attached to + + channel + name of the channel the link is to be attached to + + comp_params + pass parameters needed by some components + + create_link + write '1' to this attribute to trigger the + creation of the link. In case of speculative + configuration, the creation is post-poned until + a physical device is being attached to the bus. + + destroy_link + write '1' to this attribute to destroy an + active link + +What: /sys/kernel/config/most_video/ +Date: March 8, 2019 +KernelVersion: 5.2 +Description: + The attributes: + + buffer_size + configure the buffer size for this channel + + subbuffer_size + configure the sub-buffer size for this channel + (needed for synchronous and isochronous data) + + + num_buffers + configure number of buffers used for this + channel + + datatype + configure type of data that will travel over + this channel + + direction + configure whether this link will be an input + or output + + dbr_size + configure DBR data buffer size (this is used + for MediaLB communication only) + + packets_per_xact + configure the number of packets that will be + collected from the network before being + transmitted via USB (this is used for USB + communication only) + + device + name of the device the link is to be attached to + + channel + name of the channel the link is to be attached to + + comp_params + pass parameters needed by some components + + create_link + write '1' to this attribute to trigger the + creation of the link. In case of speculative + configuration, the creation is post-poned until + a physical device is being attached to the bus. + + destroy_link + write '1' to this attribute to destroy an + active link + +What: /sys/kernel/config/most_net/ +Date: March 8, 2019 +KernelVersion: 5.2 +Description: + The attributes: + + buffer_size + configure the buffer size for this channel + + subbuffer_size + configure the sub-buffer size for this channel + (needed for synchronous and isochronous data) + + + num_buffers + configure number of buffers used for this + channel + + datatype + configure type of data that will travel over + this channel + + direction + configure whether this link will be an input + or output + + dbr_size + configure DBR data buffer size (this is used + for MediaLB communication only) + + packets_per_xact + configure the number of packets that will be + collected from the network before being + transmitted via USB (this is used for USB + communication only) + + device + name of the device the link is to be attached to + + channel + name of the channel the link is to be attached to + + comp_params + pass parameters needed by some components + + create_link + write '1' to this attribute to trigger the + creation of the link. In case of speculative + configuration, the creation is post-poned until + a physical device is being attached to the bus. + + destroy_link + write '1' to this attribute to destroy an + active link + +What: /sys/kernel/config/most_sound/ +Date: March 8, 2019 +KernelVersion: 5.2 +Description: + The attributes: + + create_card + write '1' to this attribute to trigger the + registration of the sound card with the ALSA + subsystem. + +What: /sys/kernel/config/most_sound// +Date: March 8, 2019 +KernelVersion: 5.2 +Description: + The attributes: + + buffer_size + configure the buffer size for this channel + + subbuffer_size + configure the sub-buffer size for this channel + (needed for synchronous and isochronous data) + + + num_buffers + configure number of buffers used for this + channel + + datatype + configure type of data that will travel over + this channel + + direction + configure whether this link will be an input + or output + + dbr_size + configure DBR data buffer size (this is used + for MediaLB communication only) + + packets_per_xact + configure the number of packets that will be + collected from the network before being + transmitted via USB (this is used for USB + communication only) + + device + name of the device the link is to be attached to + + channel + name of the channel the link is to be attached to + + comp_params + pass parameters needed by some components + + create_link + write '1' to this attribute to trigger the + creation of the link. In case of speculative + configuration, the creation is post-poned until + a physical device is being attached to the bus. + + destroy_link + write '1' to this attribute to destroy an + active link diff --git a/Documentation/ABI/testing/configfs-rdma_cm b/Documentation/ABI/testing/configfs-rdma_cm new file mode 100644 index 000000000..74f9506f4 --- /dev/null +++ b/Documentation/ABI/testing/configfs-rdma_cm @@ -0,0 +1,30 @@ +What: /config/rdma_cm +Date: November 29, 2015 +KernelVersion: 4.4.0 +Description: Interface is used to configure RDMA-cable HCAs in respect to + RDMA-CM attributes. + + Attributes are visible only when configfs is mounted. To mount + configfs in /config directory use: + # mount -t configfs none /config/ + + In order to set parameters related to a specific HCA, a directory + for this HCA has to be created: + mkdir -p /config/rdma_cm/ + + +What: /config/rdma_cm//ports//default_roce_mode +Date: November 29, 2015 +KernelVersion: 4.4.0 +Description: RDMA-CM based connections from HCA at port + will be initiated with this RoCE type as default. + The possible RoCE types are either "IB/RoCE v1" or "RoCE v2". + This parameter has RW access. + +What: /config/rdma_cm//ports//default_roce_tos +Date: February 7, 2017 +KernelVersion: 4.11.0 +Description: RDMA-CM QPs from HCA at port + will be created with this TOS as default. + This can be overridden by using the rdma_set_option API. + The possible RoCE TOS values are 0-255. diff --git a/Documentation/ABI/testing/configfs-spear-pcie-gadget b/Documentation/ABI/testing/configfs-spear-pcie-gadget new file mode 100644 index 000000000..cf877bd34 --- /dev/null +++ b/Documentation/ABI/testing/configfs-spear-pcie-gadget @@ -0,0 +1,33 @@ +What: /config/pcie-gadget +Date: Feb 2011 +KernelVersion: 2.6.37 +Contact: Pratyush Anand +Description: + + Interface is used to configure selected dual mode PCIe controller + as device and then program its various registers to configure it + as a particular device type. + This interfaces can be used to show spear's PCIe device capability. + + Nodes are only visible when configfs is mounted. To mount configfs + in /config directory use:: + + # mount -t configfs none /config/ + + For nth PCIe Device Controller /config/pcie-gadget.n/: + + =============== ====================================================== + link used to enable ltssm and read its status. + int_type used to configure and read type of supported interrupt + no_of_msi used to configure number of MSI vector needed and + to read no of MSI granted. + inta write 1 to assert INTA and 0 to de-assert. + send_msi write MSI vector to be sent. + vendor_id used to write and read vendor id (hex) + device_id used to write and read device id (hex) + bar0_size used to write and read bar0_size + bar0_address used to write and read bar0 mapped area in hex. + bar0_rw_offset used to write and read offset of bar0 where bar0_data + will be written or read. + bar0_data used to write and read data at bar0_rw_offset. + =============== ====================================================== diff --git a/Documentation/ABI/testing/configfs-stp-policy b/Documentation/ABI/testing/configfs-stp-policy new file mode 100644 index 000000000..421ce6825 --- /dev/null +++ b/Documentation/ABI/testing/configfs-stp-policy @@ -0,0 +1,48 @@ +What: /config/stp-policy +Date: June 2015 +KernelVersion: 4.3 +Description: + This group contains policies mandating Master/Channel allocation + for software sources wishing to send trace data over an STM + device. + +What: /config/stp-policy/. +Date: June 2015 +KernelVersion: 4.3 +Description: + This group is the root of a policy; its name is a concatenation + of an stm device name to which this policy applies and an + arbitrary string. If part doesn't match an existing + stm device, mkdir will fail with ENODEV; if that device already + has a policy assigned to it, mkdir will fail with EBUSY. + +What: /config/stp-policy/./device +Date: June 2015 +KernelVersion: 4.3 +Description: + STM device to which this policy applies, read only. Same as the + component of its parent directory. + +What: /config/stp-policy/./ +Date: June 2015 +KernelVersion: 4.3 +Description: + Policy node is a string identifier that software clients will + use to request a master/channel to be allocated and assigned to + them. + +What: /config/stp-policy/.//masters +Date: June 2015 +KernelVersion: 4.3 +Description: + Range of masters from which to allocate for users of this node. + Write two numbers: the first master and the last master number. + +What: /config/stp-policy/.//channels +Date: June 2015 +KernelVersion: 4.3 +Description: + Range of channels from which to allocate for users of this node. + Write two numbers: the first channel and the last channel + number. + diff --git a/Documentation/ABI/testing/configfs-stp-policy-p_sys-t b/Documentation/ABI/testing/configfs-stp-policy-p_sys-t new file mode 100644 index 000000000..b290d1c00 --- /dev/null +++ b/Documentation/ABI/testing/configfs-stp-policy-p_sys-t @@ -0,0 +1,41 @@ +What: /config/stp-policy/:p_sys-t.//uuid +Date: June 2018 +KernelVersion: 4.19 +Description: + UUID source identifier string, RW. + Default value is randomly generated at the mkdir time. + Data coming from trace sources that use this will be + tagged with this UUID in the MIPI SyS-T packet stream, to + allow the decoder to discern between different sources + within the same master/channel range, and identify the + higher level decoders that may be needed for each source. + +What: /config/stp-policy/:p_sys-t.//do_len +Date: June 2018 +KernelVersion: 4.19 +Description: + Include payload length in the MIPI SyS-T header, boolean. + If enabled, the SyS-T protocol encoder will include payload + length in each packet's metadata. This is normally redundant + if the underlying transport protocol supports marking message + boundaries (which STP does), so this is off by default. + +What: /config/stp-policy/:p_sys-t.//ts_interval +Date: June 2018 +KernelVersion: 4.19 +Description: + Time interval in milliseconds. Include a timestamp in the + MIPI SyS-T packet metadata, if this many milliseconds have + passed since the previous packet from this source. Zero is + the default and stands for "never send the timestamp". + +What: /config/stp-policy/:p_sys-t.//clocksync_interval +Date: June 2018 +KernelVersion: 4.19 +Description: + Time interval in milliseconds. Send a CLOCKSYNC packet if + this many milliseconds have passed since the previous + CLOCKSYNC packet from this source. Zero is the default and + stands for "never send the CLOCKSYNC". It makes sense to + use this option with sources that generate constant and/or + periodic data, like stm_heartbeat. diff --git a/Documentation/ABI/testing/configfs-usb-gadget b/Documentation/ABI/testing/configfs-usb-gadget new file mode 100644 index 000000000..b7943aa7e --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget @@ -0,0 +1,145 @@ +What: /config/usb-gadget +Date: Jun 2013 +KernelVersion: 3.11 +Description: + This group contains sub-groups corresponding to created + USB gadgets. + +What: /config/usb-gadget/gadget +Date: Jun 2013 +KernelVersion: 3.11 +Description: + + The attributes of a gadget: + + ================ ============================================ + UDC bind a gadget to UDC/unbind a gadget; + write UDC's name found in /sys/class/udc/* + to bind a gadget, empty string "" to unbind. + + max_speed maximum speed the driver supports. Valid + names are super-speed-plus, super-speed, + high-speed, full-speed, and low-speed. + + bDeviceClass USB device class code + bDeviceSubClass USB device subclass code + bDeviceProtocol USB device protocol code + bMaxPacketSize0 maximum endpoint 0 packet size + bcdDevice bcd device release number + bcdUSB bcd USB specification version number + idProduct product ID + idVendor vendor ID + ================ ============================================ + +What: /config/usb-gadget/gadget/configs +Date: Jun 2013 +KernelVersion: 3.11 +Description: + This group contains a USB gadget's configurations + +What: /config/usb-gadget/gadget/configs/config +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes of a configuration: + + ================ ====================================== + bmAttributes configuration characteristics + MaxPower maximum power consumption from the bus + ================ ====================================== + +What: /config/usb-gadget/gadget/configs/config/strings +Date: Jun 2013 +KernelVersion: 3.11 +Description: + This group contains subdirectories for language-specific + strings for this configuration. + +What: /config/usb-gadget/gadget/configs/config/strings/language +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ================ ========================= + configuration configuration description + ================ ========================= + + +What: /config/usb-gadget/gadget/functions +Date: Jun 2013 +KernelVersion: 3.11 +Description: + This group contains functions available to this USB gadget. + +What: /config/usb-gadget/gadget/functions/./interface. +Date: May 2014 +KernelVersion: 3.16 +Description: + This group contains "Feature Descriptors" specific for one + gadget's USB interface or one interface group described + by an IAD. + + The attributes: + + ================= ===================================== + compatible_id 8-byte string for "Compatible ID" + sub_compatible_id 8-byte string for "Sub Compatible ID" + ================= ===================================== + +What: /config/usb-gadget/gadget/functions/./interface./ +Date: May 2014 +KernelVersion: 3.16 +Description: + This group contains "Extended Property Descriptors" specific for one + gadget's USB interface or one interface group described + by an IAD. + + The attributes: + + ===== =============================================== + type value 1..7 for interpreting the data + + - 1: unicode string + - 2: unicode string with environment variable + - 3: binary + - 4: little-endian 32-bit + - 5: big-endian 32-bit + - 6: unicode string with a symbolic link + - 7: multiple unicode strings + data blob of data to be interpreted depending on + type + ===== =============================================== + +What: /config/usb-gadget/gadget/strings +Date: Jun 2013 +KernelVersion: 3.11 +Description: + This group contains subdirectories for language-specific + strings for this gadget. + +What: /config/usb-gadget/gadget/strings/language +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ============ ================================= + serialnumber gadget's serial number (string) + product gadget's product description + manufacturer gadget's manufacturer description + ============ ================================= + +What: /config/usb-gadget/gadget/os_desc +Date: May 2014 +KernelVersion: 3.16 +Description: + This group contains "OS String" extension handling attributes. + + ============= =============================================== + use flag turning "OS Descriptors" support on/off + b_vendor_code one-byte value used for custom per-device and + per-interface requests + qw_sign an identifier to be reported as "OS String" + proper + ============= =============================================== diff --git a/Documentation/ABI/testing/configfs-usb-gadget-acm b/Documentation/ABI/testing/configfs-usb-gadget-acm new file mode 100644 index 000000000..d21092d75 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-acm @@ -0,0 +1,8 @@ +What: /config/usb-gadget/gadget/functions/acm.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + + This item contains just one readonly attribute: port_num. + It contains the port number of the /dev/ttyGS device + associated with acm function's instance "name". diff --git a/Documentation/ABI/testing/configfs-usb-gadget-ecm b/Documentation/ABI/testing/configfs-usb-gadget-ecm new file mode 100644 index 000000000..732101ca9 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-ecm @@ -0,0 +1,20 @@ +What: /config/usb-gadget/gadget/functions/ecm.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ifname + - network device interface name associated with + this function instance + qmult + - queue length multiplier for high and + super speed + host_addr + - MAC address of host's end of this + Ethernet over USB link + dev_addr + - MAC address of device's end of this + Ethernet over USB link + + diff --git a/Documentation/ABI/testing/configfs-usb-gadget-eem b/Documentation/ABI/testing/configfs-usb-gadget-eem new file mode 100644 index 000000000..178c3d5fb --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-eem @@ -0,0 +1,16 @@ +What: /config/usb-gadget/gadget/functions/eem.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ========== ============================================= + ifname network device interface name associated with + this function instance + qmult queue length multiplier for high and + super speed + host_addr MAC address of host's end of this + Ethernet over USB link + dev_addr MAC address of device's end of this + Ethernet over USB link + ========== ============================================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-ffs b/Documentation/ABI/testing/configfs-usb-gadget-ffs new file mode 100644 index 000000000..e39b27653 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-ffs @@ -0,0 +1,9 @@ +What: /config/usb-gadget/gadget/functions/ffs.name +Date: Nov 2013 +KernelVersion: 3.13 +Description: The purpose of this directory is to create and remove it. + + A corresponding USB function instance is created/removed. + There are no attributes here. + + All parameters are set through FunctionFS. diff --git a/Documentation/ABI/testing/configfs-usb-gadget-hid b/Documentation/ABI/testing/configfs-usb-gadget-hid new file mode 100644 index 000000000..748705c4c --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-hid @@ -0,0 +1,13 @@ +What: /config/usb-gadget/gadget/functions/hid.name +Date: Nov 2014 +KernelVersion: 3.19 +Description: + The attributes: + + ============= ============================================ + protocol HID protocol to use + report_desc blob corresponding to HID report descriptors + except the data passed through /dev/hidg + report_length HID report length + subclass HID device subclass to use + ============= ============================================ diff --git a/Documentation/ABI/testing/configfs-usb-gadget-loopback b/Documentation/ABI/testing/configfs-usb-gadget-loopback new file mode 100644 index 000000000..e6c6ba5ac --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-loopback @@ -0,0 +1,10 @@ +What: /config/usb-gadget/gadget/functions/Loopback.name +Date: Nov 2013 +KernelVersion: 3.13 +Description: + The attributes: + + ======= ======================= + qlen depth of loopback queue + buflen buffer length + ======= ======================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-mass-storage b/Documentation/ABI/testing/configfs-usb-gadget-mass-storage new file mode 100644 index 000000000..fc0328069 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-mass-storage @@ -0,0 +1,41 @@ +What: /config/usb-gadget/gadget/functions/mass_storage.name +Date: Oct 2013 +KernelVersion: 3.13 +Description: + The attributes: + + =========== ============================================== + stall Set to permit function to halt bulk endpoints. + Disabled on some USB devices known not to work + correctly. You should set it to true. + num_buffers Number of pipeline buffers. Valid numbers + are 2..4. Available only if + CONFIG_USB_GADGET_DEBUG_FILES is set. + =========== ============================================== + +What: /config/usb-gadget/gadget/functions/mass_storage.name/lun.name +Date: Oct 2013 +KernelVersion: 3.13 +Description: + The attributes: + + ============ ============================================== + file The path to the backing file for the LUN. + Required if LUN is not marked as removable. + ro Flag specifying access to the LUN shall be + read-only. This is implied if CD-ROM emulation + is enabled as well as when it was impossible + to open "filename" in R/W mode. + removable Flag specifying that LUN shall be indicated as + being removable. + cdrom Flag specifying that LUN shall be reported as + being a CD-ROM. + nofua Flag specifying that FUA flag + in SCSI WRITE(10,12) + forced_eject This write-only file is useful only when + the function is active. It causes the backing + file to be forcibly detached from the LUN, + regardless of whether the host has allowed it. + Any non-zero number of bytes written will + result in ejection. + ============ ============================================== diff --git a/Documentation/ABI/testing/configfs-usb-gadget-midi b/Documentation/ABI/testing/configfs-usb-gadget-midi new file mode 100644 index 000000000..07389cddd --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-midi @@ -0,0 +1,14 @@ +What: /config/usb-gadget/gadget/functions/midi.name +Date: Nov 2014 +KernelVersion: 3.19 +Description: + The attributes: + + ========== ==================================== + index index value for the USB MIDI adapter + id ID string for the USB MIDI adapter + buflen MIDI buffer length + qlen USB read request queue length + in_ports number of MIDI input ports + out_ports number of MIDI output ports + ========== ==================================== diff --git a/Documentation/ABI/testing/configfs-usb-gadget-ncm b/Documentation/ABI/testing/configfs-usb-gadget-ncm new file mode 100644 index 000000000..6fe723eff --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-ncm @@ -0,0 +1,15 @@ +What: /config/usb-gadget/gadget/functions/ncm.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ifname - network device interface name associated with + this function instance + qmult - queue length multiplier for high and + super speed + host_addr - MAC address of host's end of this + Ethernet over USB link + dev_addr - MAC address of device's end of this + Ethernet over USB link + diff --git a/Documentation/ABI/testing/configfs-usb-gadget-obex b/Documentation/ABI/testing/configfs-usb-gadget-obex new file mode 100644 index 000000000..a6a9327ed --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-obex @@ -0,0 +1,9 @@ +What: /config/usb-gadget/gadget/functions/obex.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + + This item contains just one readonly attribute: port_num. + It contains the port number of the /dev/ttyGS device + associated with obex function's instance "name". + diff --git a/Documentation/ABI/testing/configfs-usb-gadget-phonet b/Documentation/ABI/testing/configfs-usb-gadget-phonet new file mode 100644 index 000000000..7037a358e --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-phonet @@ -0,0 +1,8 @@ +What: /config/usb-gadget/gadget/functions/phonet.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + + This item contains just one readonly attribute: ifname. + It contains the network interface name assigned during + network device registration. diff --git a/Documentation/ABI/testing/configfs-usb-gadget-printer b/Documentation/ABI/testing/configfs-usb-gadget-printer new file mode 100644 index 000000000..7aa731bac --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-printer @@ -0,0 +1,11 @@ +What: /config/usb-gadget/gadget/functions/printer.name +Date: Apr 2015 +KernelVersion: 4.1 +Description: + The attributes: + + ========== =========================================== + pnp_string Data to be passed to the host in pnp string + q_len Number of requests per endpoint + ========== =========================================== + diff --git a/Documentation/ABI/testing/configfs-usb-gadget-rndis b/Documentation/ABI/testing/configfs-usb-gadget-rndis new file mode 100644 index 000000000..9416eda7f --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-rndis @@ -0,0 +1,19 @@ +What: /config/usb-gadget/gadget/functions/rndis.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ========= ============================================= + ifname network device interface name associated with + this function instance + qmult queue length multiplier for high and + super speed + host_addr MAC address of host's end of this + Ethernet over USB link + dev_addr MAC address of device's end of this + Ethernet over USB link + class USB interface class, default is 02 (hex) + subclass USB interface subclass, default is 06 (hex) + protocol USB interface protocol, default is 00 (hex) + ========= ============================================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-serial b/Documentation/ABI/testing/configfs-usb-gadget-serial new file mode 100644 index 000000000..474d249f7 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-serial @@ -0,0 +1,9 @@ +What: /config/usb-gadget/gadget/functions/gser.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + + This item contains just one readonly attribute: port_num. + It contains the port number of the /dev/ttyGS device + associated with gser function's instance "name". + diff --git a/Documentation/ABI/testing/configfs-usb-gadget-sourcesink b/Documentation/ABI/testing/configfs-usb-gadget-sourcesink new file mode 100644 index 000000000..1f3d31b60 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-sourcesink @@ -0,0 +1,16 @@ +What: /config/usb-gadget/gadget/functions/SourceSink.name +Date: Nov 2013 +KernelVersion: 3.13 +Description: + The attributes: + + ============== ================================== + pattern 0 (all zeros), 1 (mod63), 2 (none) + isoc_interval 1..16 + isoc_maxpacket 0 - 1023 (fs), 0 - 1024 (hs/ss) + isoc_mult 0..2 (hs/ss only) + isoc_maxburst 0..15 (ss only) + buflen buffer length + bulk_qlen depth of queue for bulk + iso_qlen depth of queue for iso + ============== ================================== diff --git a/Documentation/ABI/testing/configfs-usb-gadget-subset b/Documentation/ABI/testing/configfs-usb-gadget-subset new file mode 100644 index 000000000..0061b8643 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-subset @@ -0,0 +1,16 @@ +What: /config/usb-gadget/gadget/functions/geth.name +Date: Jun 2013 +KernelVersion: 3.11 +Description: + The attributes: + + ========== ============================================= + ifname network device interface name associated with + this function instance + qmult queue length multiplier for high and + super speed + host_addr MAC address of host's end of this + Ethernet over USB link + dev_addr MAC address of device's end of this + Ethernet over USB link + ========== ============================================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-tcm b/Documentation/ABI/testing/configfs-usb-gadget-tcm new file mode 100644 index 000000000..a29ed2dd6 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-tcm @@ -0,0 +1,6 @@ +What: /config/usb-gadget/gadget/functions/tcm.name +Date: Dec 2015 +KernelVersion: 4.5 +Description: + There are no attributes because all the configuration + is performed in the "target" subsystem of configfs. diff --git a/Documentation/ABI/testing/configfs-usb-gadget-uac1 b/Documentation/ABI/testing/configfs-usb-gadget-uac1 new file mode 100644 index 000000000..c4ba92f00 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-uac1 @@ -0,0 +1,33 @@ +What: /config/usb-gadget/gadget/functions/uac1.name +Date: June 2017 +KernelVersion: 4.14 +Description: + The attributes: + + ===================== ======================================= + c_chmask capture channel mask + c_srate list of capture sampling rates (comma-separated) + c_ssize capture sample size (bytes) + c_mute_present capture mute control enable + c_volume_present capture volume control enable + c_volume_min capture volume control min value + (in 1/256 dB) + c_volume_max capture volume control max value + (in 1/256 dB) + c_volume_res capture volume control resolution + (in 1/256 dB) + p_chmask playback channel mask + p_srate list of playback sampling rates (comma-separated) + p_ssize playback sample size (bytes) + p_mute_present playback mute control enable + p_volume_present playback volume control enable + p_volume_min playback volume control min value + (in 1/256 dB) + p_volume_max playback volume control max value + (in 1/256 dB) + p_volume_res playback volume control resolution + (in 1/256 dB) + req_number the number of pre-allocated requests + for both capture and playback + function_name name of the interface + ===================== ======================================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-uac1_legacy b/Documentation/ABI/testing/configfs-usb-gadget-uac1_legacy new file mode 100644 index 000000000..b2eaefd9b --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-uac1_legacy @@ -0,0 +1,12 @@ +What: /config/usb-gadget/gadget/functions/uac1_legacy.name +Date: Sep 2014 +KernelVersion: 3.18 +Description: + The attributes: + + audio_buf_size - audio buffer size + fn_cap - capture pcm device file name + fn_cntl - control device file name + fn_play - playback pcm device file name + req_buf_size - ISO OUT endpoint request buffer size + req_count - ISO OUT endpoint request count diff --git a/Documentation/ABI/testing/configfs-usb-gadget-uac2 b/Documentation/ABI/testing/configfs-usb-gadget-uac2 new file mode 100644 index 000000000..3371c39f6 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-uac2 @@ -0,0 +1,38 @@ +What: /config/usb-gadget/gadget/functions/uac2.name +Date: Sep 2014 +KernelVersion: 3.18 +Description: + The attributes: + + ===================== ======================================= + c_chmask capture channel mask + c_srate list of capture sampling rates (comma-separated) + c_ssize capture sample size (bytes) + c_hs_bint capture bInterval for HS/SS (1-4: fixed, 0: auto) + c_sync capture synchronization type + (async/adaptive) + c_mute_present capture mute control enable + c_volume_present capture volume control enable + c_volume_min capture volume control min value + (in 1/256 dB) + c_volume_max capture volume control max value + (in 1/256 dB) + c_volume_res capture volume control resolution + (in 1/256 dB) + fb_max maximum extra bandwidth in async mode + p_chmask playback channel mask + p_srate list of playback sampling rates (comma-separated) + p_ssize playback sample size (bytes) + p_hs_bint playback bInterval for HS/SS (1-4: fixed, 0: auto) + p_mute_present playback mute control enable + p_volume_present playback volume control enable + p_volume_min playback volume control min value + (in 1/256 dB) + p_volume_max playback volume control max value + (in 1/256 dB) + p_volume_res playback volume control resolution + (in 1/256 dB) + req_number the number of pre-allocated requests + for both capture and playback + function_name name of the interface + ===================== ======================================= diff --git a/Documentation/ABI/testing/configfs-usb-gadget-uvc b/Documentation/ABI/testing/configfs-usb-gadget-uvc new file mode 100644 index 000000000..feb3f2cc0 --- /dev/null +++ b/Documentation/ABI/testing/configfs-usb-gadget-uvc @@ -0,0 +1,327 @@ +What: /config/usb-gadget/gadget/functions/uvc.name +Date: Dec 2014 +KernelVersion: 4.0 +Description: UVC function directory + + =================== ============================= + streaming_maxburst 0..15 (ss only) + streaming_maxpacket 1..1023 (fs), 1..3072 (hs/ss) + streaming_interval 1..16 + function_name string [32] + =================== ============================= + +What: /config/usb-gadget/gadget/functions/uvc.name/control +Date: Dec 2014 +KernelVersion: 4.0 +Description: Control descriptors + + All attributes read only: + + ================ ============================= + bInterfaceNumber USB interface number for this + streaming interface + ================ ============================= + +What: /config/usb-gadget/gadget/functions/uvc.name/control/class +Date: Dec 2014 +KernelVersion: 4.0 +Description: Class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss +Date: Dec 2014 +KernelVersion: 4.0 +Description: Super speed control class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs +Date: Dec 2014 +KernelVersion: 4.0 +Description: Full speed control class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal +Date: Dec 2014 +KernelVersion: 4.0 +Description: Terminal descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output +Date: Dec 2014 +KernelVersion: 4.0 +Description: Output terminal descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default +Date: Dec 2014 +KernelVersion: 4.0 +Description: Default output terminal descriptors + + All attributes read only except bSourceID: + + ============== ============================================= + iTerminal index of string descriptor + bSourceID id of the terminal to which this terminal + is connected + bAssocTerminal id of the input terminal to which this output + terminal is associated + wTerminalType terminal type + bTerminalID a non-zero id of this terminal + ============== ============================================= + +What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera +Date: Dec 2014 +KernelVersion: 4.0 +Description: Camera terminal descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera/default +Date: Dec 2014 +KernelVersion: 4.0 +Description: Default camera terminal descriptors + + All attributes read only: + + ======================== ==================================== + bmControls bitmap specifying which controls are + supported for the video stream + wOcularFocalLength the value of Locular + wObjectiveFocalLengthMax the value of Lmin + wObjectiveFocalLengthMin the value of Lmax + iTerminal index of string descriptor + bAssocTerminal id of the output terminal to which + this terminal is connected + wTerminalType terminal type + bTerminalID a non-zero id of this terminal + ======================== ==================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/control/processing +Date: Dec 2014 +KernelVersion: 4.0 +Description: Processing unit descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/processing/default +Date: Dec 2014 +KernelVersion: 4.0 +Description: Default processing unit descriptors + + All attributes read only: + + =============== ======================================== + iProcessing index of string descriptor + bmControls bitmap specifying which controls are + supported for the video stream + wMaxMultiplier maximum digital magnification x100 + bSourceID id of the terminal to which this unit is + connected + bUnitID a non-zero id of this unit + =============== ======================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/control/header +Date: Dec 2014 +KernelVersion: 4.0 +Description: Control header descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/control/header/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific control header descriptors + +dwClockFrequency +bcdUVC +What: /config/usb-gadget/gadget/functions/uvc.name/streaming +Date: Dec 2014 +KernelVersion: 4.0 +Description: Streaming descriptors + + All attributes read only: + + ================ ============================= + bInterfaceNumber USB interface number for this + streaming interface + ================ ============================= + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class +Date: Dec 2014 +KernelVersion: 4.0 +Description: Streaming class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/ss +Date: Dec 2014 +KernelVersion: 4.0 +Description: Super speed streaming class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/hs +Date: Dec 2014 +KernelVersion: 4.0 +Description: High speed streaming class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/fs +Date: Dec 2014 +KernelVersion: 4.0 +Description: Full speed streaming class descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/color_matching +Date: Dec 2014 +KernelVersion: 4.0 +Description: Color matching descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/color_matching/default +Date: Dec 2014 +KernelVersion: 4.0 +Description: Default color matching descriptors + + All attributes read only: + + ======================== ====================================== + bMatrixCoefficients matrix used to compute luma and + chroma values from the color primaries + bTransferCharacteristics optoelectronic transfer + characteristic of the source picture, + also called the gamma function + bColorPrimaries color primaries and the reference + white + ======================== ====================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg +Date: Dec 2014 +KernelVersion: 4.0 +Description: MJPEG format descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific MJPEG format descriptors + + All attributes read only, + except bmaControls and bDefaultFrameIndex: + + =================== ===================================== + bFormatIndex unique id for this format descriptor; + only defined after parent header is + linked into the streaming class; + read-only + bmaControls this format's data for bmaControls in + the streaming header + bmInterfaceFlags specifies interlace information, + read-only + bAspectRatioY the X dimension of the picture aspect + ratio, read-only + bAspectRatioX the Y dimension of the picture aspect + ratio, read-only + bmFlags characteristics of this format, + read-only + bDefaultFrameIndex optimum frame index for this stream + =================== ===================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific MJPEG frame descriptors + + ========================= ===================================== + bFrameIndex unique id for this framedescriptor; + only defined after parent format is + linked into the streaming header; + read-only + dwFrameInterval indicates how frame interval can be + programmed; a number of values + separated by newline can be specified + dwDefaultFrameInterval the frame interval the device would + like to use as default + dwMaxVideoFrameBufferSize the maximum number of bytes the + compressor will produce for a video + frame or still image + dwMaxBitRate the maximum bit rate at the shortest + frame interval in bps + dwMinBitRate the minimum bit rate at the longest + frame interval in bps + wHeight height of decoded bitmap frame in px + wWidth width of decoded bitmam frame in px + bmCapabilities still image support, fixed frame-rate + support + ========================= ===================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed +Date: Dec 2014 +KernelVersion: 4.0 +Description: Uncompressed format descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific uncompressed format descriptors + + ================== ======================================= + bFormatIndex unique id for this format descriptor; + only defined after parent header is + linked into the streaming class; + read-only + bmaControls this format's data for bmaControls in + the streaming header + bmInterfaceFlags specifies interlace information, + read-only + bAspectRatioY the X dimension of the picture aspect + ratio, read-only + bAspectRatioX the Y dimension of the picture aspect + ratio, read-only + bDefaultFrameIndex optimum frame index for this stream + bBitsPerPixel number of bits per pixel used to + specify color in the decoded video + frame + guidFormat globally unique id used to identify + stream-encoding format + ================== ======================================= + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific uncompressed frame descriptors + + ========================= ===================================== + bFrameIndex unique id for this framedescriptor; + only defined after parent format is + linked into the streaming header; + read-only + dwFrameInterval indicates how frame interval can be + programmed; a number of values + separated by newline can be specified + dwDefaultFrameInterval the frame interval the device would + like to use as default + dwMaxVideoFrameBufferSize the maximum number of bytes the + compressor will produce for a video + frame or still image + dwMaxBitRate the maximum bit rate at the shortest + frame interval in bps + dwMinBitRate the minimum bit rate at the longest + frame interval in bps + wHeight height of decoded bitmap frame in px + wWidth width of decoded bitmam frame in px + bmCapabilities still image support, fixed frame-rate + support + ========================= ===================================== + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header +Date: Dec 2014 +KernelVersion: 4.0 +Description: Streaming header descriptors + +What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header/name +Date: Dec 2014 +KernelVersion: 4.0 +Description: Specific streaming header descriptors + + All attributes read only: + + ==================== ===================================== + bTriggerUsage how the host software will respond to + a hardware trigger interrupt event + bTriggerSupport flag specifying if hardware + triggering is supported + bStillCaptureMethod method of still image capture + supported + bTerminalLink id of the output terminal to which + the video endpoint of this interface + is connected + bmInfo capabilities of this video streaming + interface + ==================== ===================================== + +What: /sys/class/udc/udc.name/device/gadget/video4linux/video.name/function_name +Date: May 2018 +KernelVersion: 4.19 +Description: UVC configfs function instance name diff --git a/Documentation/ABI/testing/debugfs-cec-error-inj b/Documentation/ABI/testing/debugfs-cec-error-inj new file mode 100644 index 000000000..8debcb08a --- /dev/null +++ b/Documentation/ABI/testing/debugfs-cec-error-inj @@ -0,0 +1,40 @@ +What: /sys/kernel/debug/cec/*/error-inj +Date: March 2018 +Contact: Hans Verkuil +Description: + +The CEC Framework allows for CEC error injection commands through +debugfs. Drivers that support this will create an error-inj file +through which the error injection commands can be given. + +The basic syntax is as follows: + +Leading spaces/tabs are ignored. If the next character is a '#' or the +end of the line was reached, then the whole line is ignored. Otherwise +a command is expected. + +It is up to the driver to decide what commands to implement. The only +exception is that the command 'clear' without any arguments must be +implemented and that it will remove all current error injection +commands. + +This ensures that you can always do 'echo clear >error-inj' to clear any +error injections without having to know the details of the driver-specific +commands. + +Note that the output of 'error-inj' shall be valid as input to 'error-inj'. +So this must work:: + + $ cat error-inj >einj.txt + $ cat einj.txt >error-inj + +Other than these basic rules described above this ABI is not considered +stable and may change in the future. + +Drivers that implement this functionality must document the commands as +part of the CEC documentation and must keep that documentation up to date +when changes are made. + +The following CEC error injection implementations exist: + +- Documentation/userspace-api/media/cec/cec-pin-error-inj.rst diff --git a/Documentation/ABI/testing/debugfs-cros-ec b/Documentation/ABI/testing/debugfs-cros-ec new file mode 100644 index 000000000..9a040c6f5 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-cros-ec @@ -0,0 +1,78 @@ +What: /sys/kernel/debug//console_log +Date: September 2017 +KernelVersion: 4.13 +Description: + If the EC supports the CONSOLE_READ command type, this file + can be used to grab the EC logs. The kernel polls for the log + and keeps its own buffer but userspace should grab this and + write it out to some logs. + +What: /sys/kernel/debug//panicinfo +Date: September 2017 +KernelVersion: 4.13 +Description: + This file dumps the EC panic information from the previous + reboot. This file will only exist if the PANIC_INFO command + type is supported by the EC. + +What: /sys/kernel/debug//pdinfo +Date: June 2018 +KernelVersion: 4.17 +Description: + This file provides the port role, muxes and power debug + information for all the USB PD/type-C ports available. If + the are no ports available, this file will be just an empty + file. + +What: /sys/kernel/debug//uptime +Date: June 2019 +KernelVersion: 5.3 +Description: + A u32 providing the time since EC booted in ms. This is + is used for synchronizing the AP host time with the EC + log. An error is returned if the command is not supported + by the EC or there is a communication problem. + +What: /sys/kernel/debug//last_resume_result +Date: June 2019 +KernelVersion: 5.3 +Description: + Some ECs have a feature where they will track transitions to + the (Intel) processor's SLP_S0 line, in order to detect cases + where a system failed to go into S0ix. When the system resumes, + an EC with this feature will return a summary of SLP_S0 + transitions that occurred. The last_resume_result file returns + the most recent response from the AP's resume message to the EC. + + The bottom 31 bits contain a count of the number of SLP_S0 + transitions that occurred since the suspend message was + received. Bit 31 is set if the EC attempted to wake the + system due to a timeout when watching for SLP_S0 transitions. + Callers can use this to detect a wake from the EC due to + S0ix timeouts. The result will be zero if no suspend + transitions have been attempted, or the EC does not support + this feature. + + Output will be in the format: "0x%08x\n". + +What: /sys/kernel/debug//suspend_timeout_ms +Date: August 2022 +KernelVersion: 6.1 +Description: + Some ECs have a feature where they will track transitions of + a hardware-controlled sleep line, such as Intel's SLP_S0 line, + in order to detect cases where a system failed to go into deep + sleep states. The suspend_timeout_ms file controls the amount of + time in milliseconds the EC will wait before declaring a sleep + timeout event and attempting to wake the system. + + Supply 0 to use the default value coded into EC firmware. Supply + 65535 (EC_HOST_SLEEP_TIMEOUT_INFINITE) to disable the EC sleep + failure detection mechanism. Values in between 0 and 65535 + indicate the number of milliseconds the EC should wait after a + sleep transition before declaring a timeout. This includes both + the duration after a sleep command was received but before the + hardware line changed, as well as the duration between when the + hardware line changed and the kernel sent an EC resume command. + + Output will be in the format: "%u\n". diff --git a/Documentation/ABI/testing/debugfs-driver-genwqe b/Documentation/ABI/testing/debugfs-driver-genwqe new file mode 100644 index 000000000..b45b01654 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-driver-genwqe @@ -0,0 +1,91 @@ +What: /sys/kernel/debug/genwqe/genwqe_card/ddcb_info +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: DDCB queue dump used for debugging queueing problems. + +What: /sys/kernel/debug/genwqe/genwqe_card/curr_regs +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Dump of the current error registers. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/curr_dbg_uid0 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID0 (unit id 0). + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/curr_dbg_uid1 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID1. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/curr_dbg_uid2 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID2. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/prev_regs +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Dump of the error registers before the last reset of + the card occurred. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/prev_dbg_uid0 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID0 before card was reset. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/prev_dbg_uid1 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID1 before card was reset. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/prev_dbg_uid2 +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Internal chip state of UID2 before card was reset. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/info +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Comprehensive summary of bitstream version and software + version. Used bitstream and bitstream clocking information. + +What: /sys/kernel/debug/genwqe/genwqe_card/err_inject +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Possibility to inject error cases to ensure that the drivers + error handling code works well. + +What: /sys/kernel/debug/genwqe/genwqe_card/vf<0..14>_jobtimeout_msec +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Default VF timeout 250ms. Testing might require 1000ms. + Using 0 will use the cards default value (whatever that is). + + The timeout depends on the max number of available cards + in the system and the maximum allowed queue size. + + The driver ensures that the settings are done just before + the VFs get enabled. Changing the timeouts in flight is not + possible. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/jobtimer +Date: Oct 2013 +Contact: haver@linux.vnet.ibm.com +Description: Dump job timeout register values for PF and VFs. + Only available for PF. + +What: /sys/kernel/debug/genwqe/genwqe_card/queue_working_time +Date: Dec 2013 +Contact: haver@linux.vnet.ibm.com +Description: Dump queue working time register values for PF and VFs. + Only available for PF. diff --git a/Documentation/ABI/testing/debugfs-driver-habanalabs b/Documentation/ABI/testing/debugfs-driver-habanalabs new file mode 100644 index 000000000..c915bf17b --- /dev/null +++ b/Documentation/ABI/testing/debugfs-driver-habanalabs @@ -0,0 +1,310 @@ +What: /sys/kernel/debug/habanalabs/hl/addr +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets the device address to be used for read or write through + PCI bar, or the device VA of a host mapped memory to be read or + written directly from the host. The latter option is allowed + only when the IOMMU is disabled. + The acceptable value is a string that starts with "0x" + +What: /sys/kernel/debug/habanalabs/hl/clk_gate +Date: May 2020 +KernelVersion: 5.8 +Contact: ogabbay@kernel.org +Description: This setting is now deprecated as clock gating is handled solely by the f/w + +What: /sys/kernel/debug/habanalabs/hl/command_buffers +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays a list with information about the currently allocated + command buffers + +What: /sys/kernel/debug/habanalabs/hl/command_submission +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays a list with information about the currently active + command submissions + +What: /sys/kernel/debug/habanalabs/hl/command_submission_jobs +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays a list with detailed information about each JOB (CB) of + each active command submission + +What: /sys/kernel/debug/habanalabs/hl/data32 +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Allows the root user to read or write directly through the + device's PCI bar. Writing to this file generates a write + transaction while reading from the file generates a read + transaction. This custom interface is needed (instead of using + the generic Linux user-space PCI mapping) because the DDR bar + is very small compared to the DDR memory and only the driver can + move the bar before and after the transaction. + + If the IOMMU is disabled, it also allows the root user to read + or write from the host a device VA of a host mapped memory + +What: /sys/kernel/debug/habanalabs/hl/data64 +Date: Jan 2020 +KernelVersion: 5.6 +Contact: ogabbay@kernel.org +Description: Allows the root user to read or write 64 bit data directly + through the device's PCI bar. Writing to this file generates a + write transaction while reading from the file generates a read + transaction. This custom interface is needed (instead of using + the generic Linux user-space PCI mapping) because the DDR bar + is very small compared to the DDR memory and only the driver can + move the bar before and after the transaction. + + If the IOMMU is disabled, it also allows the root user to read + or write from the host a device VA of a host mapped memory + +What: /sys/kernel/debug/habanalabs/hl/data_dma +Date: Apr 2021 +KernelVersion: 5.13 +Contact: ogabbay@kernel.org +Description: Allows the root user to read from the device's internal + memory (DRAM/SRAM) through a DMA engine. + This property is a binary blob that contains the result of the + DMA transfer. + This custom interface is needed (instead of using the generic + Linux user-space PCI mapping) because the amount of internal + memory is huge (>32GB) and reading it via the PCI bar will take + a very long time. + This interface doesn't support concurrency in the same device. + In GAUDI and GOYA, this action can cause undefined behavior + in case the it is done while the device is executing user + workloads. + Only supported on GAUDI at this stage. + +What: /sys/kernel/debug/habanalabs/hl/device +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Enables the root user to set the device to specific state. + Valid values are "disable", "enable", "suspend", "resume". + User can read this property to see the valid values + +What: /sys/kernel/debug/habanalabs/hl/dma_size +Date: Apr 2021 +KernelVersion: 5.13 +Contact: ogabbay@kernel.org +Description: Specify the size of the DMA transaction when using DMA to read + from the device's internal memory. The value can not be larger + than 128MB. Writing to this value initiates the DMA transfer. + When the write is finished, the user can read the "data_dma" + blob + +What: /sys/kernel/debug/habanalabs/hl/dump_razwi_events +Date: Aug 2022 +KernelVersion: 5.20 +Contact: fkassabri@habana.ai +Description: Dumps all razwi events to dmesg if exist. + After reading the status register of an existing event + the routine will clear the status register. + Usage: cat dump_razwi_events + +What: /sys/kernel/debug/habanalabs/hl/dump_security_violations +Date: Jan 2021 +KernelVersion: 5.12 +Contact: ogabbay@kernel.org +Description: Dumps all security violations to dmesg. This will also ack + all security violations meanings those violations will not be + dumped next time user calls this API + +What: /sys/kernel/debug/habanalabs/hl/engines +Date: Jul 2019 +KernelVersion: 5.3 +Contact: ogabbay@kernel.org +Description: Displays the status registers values of the device engines and + their derived idle status + +What: /sys/kernel/debug/habanalabs/hl/i2c_addr +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets I2C device address for I2C transaction that is generated + by the device's CPU, Not available when device is loaded with secured + firmware + +What: /sys/kernel/debug/habanalabs/hl/i2c_bus +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets I2C bus address for I2C transaction that is generated by + the device's CPU, Not available when device is loaded with secured + firmware + +What: /sys/kernel/debug/habanalabs/hl/i2c_data +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Triggers an I2C transaction that is generated by the device's + CPU. Writing to this file generates a write transaction while + reading from the file generates a read transaction, Not available + when device is loaded with secured firmware + +What: /sys/kernel/debug/habanalabs/hl/i2c_len +Date: Dec 2021 +KernelVersion: 5.17 +Contact: obitton@habana.ai +Description: Sets I2C length in bytes for I2C transaction that is generated by + the device's CPU, Not available when device is loaded with secured + firmware + +What: /sys/kernel/debug/habanalabs/hl/i2c_reg +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets I2C register id for I2C transaction that is generated by + the device's CPU, Not available when device is loaded with secured + firmware + +What: /sys/kernel/debug/habanalabs/hl/led0 +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets the state of the first S/W led on the device, Not available + when device is loaded with secured firmware + +What: /sys/kernel/debug/habanalabs/hl/led1 +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets the state of the second S/W led on the device, Not available + when device is loaded with secured firmware + +What: /sys/kernel/debug/habanalabs/hl/led2 +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets the state of the third S/W led on the device, Not available + when device is loaded with secured firmware + +What: /sys/kernel/debug/habanalabs/hl/memory_scrub +Date: May 2022 +KernelVersion: 5.19 +Contact: dhirschfeld@habana.ai +Description: Allows the root user to scrub the dram memory. The scrubbing + value can be set using the debugfs file memory_scrub_val. + +What: /sys/kernel/debug/habanalabs/hl/memory_scrub_val +Date: May 2022 +KernelVersion: 5.19 +Contact: dhirschfeld@habana.ai +Description: The value to which the dram will be set to when the user + scrubs the dram using 'memory_scrub' debugfs file and + the scrubbing value when using module param 'memory_scrub' + +What: /sys/kernel/debug/habanalabs/hl/mmu +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays the hop values and physical address for a given ASID + and virtual address. The user should write the ASID and VA into + the file and then read the file to get the result. + e.g. to display info about VA 0x1000 for ASID 1 you need to do: + echo "1 0x1000" > /sys/kernel/debug/habanalabs/hl0/mmu + +What: /sys/kernel/debug/habanalabs/hl/mmu_error +Date: Mar 2021 +KernelVersion: 5.12 +Contact: fkassabri@habana.ai +Description: Check and display page fault or access violation mmu errors for + all MMUs specified in mmu_cap_mask. + e.g. to display error info for MMU hw cap bit 9, you need to do: + echo "0x200" > /sys/kernel/debug/habanalabs/hl0/mmu_error + cat /sys/kernel/debug/habanalabs/hl0/mmu_error + +What: /sys/kernel/debug/habanalabs/hl/monitor_dump +Date: Mar 2022 +KernelVersion: 5.19 +Contact: osharabi@habana.ai +Description: Allows the root user to dump monitors status from the device's + protected config space. + This property is a binary blob that contains the result of the + monitors registers dump. + This custom interface is needed (instead of using the generic + Linux user-space PCI mapping) because this space is protected + and cannot be accessed using PCI read. + This interface doesn't support concurrency in the same device. + Only supported on GAUDI. + +What: /sys/kernel/debug/habanalabs/hl/monitor_dump_trig +Date: Mar 2022 +KernelVersion: 5.19 +Contact: osharabi@habana.ai +Description: Triggers dump of monitor data. The value to trigger the operation + must be 1. Triggering the monitor dump operation initiates dump of + current registers values of all monitors. + When the write is finished, the user can read the "monitor_dump" + blob + +What: /sys/kernel/debug/habanalabs/hl/set_power_state +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Sets the PCI power state. Valid values are "1" for D0 and "2" + for D3Hot + +What: /sys/kernel/debug/habanalabs/hl/skip_reset_on_timeout +Date: Jun 2021 +KernelVersion: 5.13 +Contact: ynudelman@habana.ai +Description: Sets the skip reset on timeout option for the device. Value of + "0" means device will be reset in case some CS has timed out, + otherwise it will not be reset. + +What: /sys/kernel/debug/habanalabs/hl/state_dump +Date: Oct 2021 +KernelVersion: 5.15 +Contact: ynudelman@habana.ai +Description: Gets the state dump occurring on a CS timeout or failure. + State dump is used for debug and is created each time in case of + a problem in a CS execution, before reset. + Reading from the node returns the newest state dump available. + Writing an integer X discards X state dumps, so that the + next read would return X+1-st newest state dump. + +What: /sys/kernel/debug/habanalabs/hl/stop_on_err +Date: Mar 2020 +KernelVersion: 5.6 +Contact: ogabbay@kernel.org +Description: Sets the stop-on_error option for the device engines. Value of + "0" is for disable, otherwise enable. + Relevant only for GOYA and GAUDI. + +What: /sys/kernel/debug/habanalabs/hl/timeout_locked +Date: Sep 2021 +KernelVersion: 5.16 +Contact: obitton@habana.ai +Description: Sets the command submission timeout value in seconds. + +What: /sys/kernel/debug/habanalabs/hl/userptr +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays a list with information about the currently user + pointers (user virtual addresses) that are pinned and mapped + to DMA addresses + +What: /sys/kernel/debug/habanalabs/hl/userptr_lookup +Date: Oct 2021 +KernelVersion: 5.15 +Contact: ogabbay@kernel.org +Description: Allows to search for specific user pointers (user virtual + addresses) that are pinned and mapped to DMA addresses, and see + their resolution to the specific dma address. + +What: /sys/kernel/debug/habanalabs/hl/vm +Date: Jan 2019 +KernelVersion: 5.1 +Contact: ogabbay@kernel.org +Description: Displays a list with information about all the active virtual + address mappings per ASID and all user mappings of HW blocks diff --git a/Documentation/ABI/testing/debugfs-ec b/Documentation/ABI/testing/debugfs-ec new file mode 100644 index 000000000..ab6099daa --- /dev/null +++ b/Documentation/ABI/testing/debugfs-ec @@ -0,0 +1,21 @@ +What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io} +Date: July 2010 +Contact: Thomas Renninger +Description: + +General information like which GPE is assigned to the EC and whether +the global lock should get used. +Knowing the EC GPE one can watch the amount of HW events related to +the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`): +/sys/firmware/acpi/interrupts/gpeXY + +The io file is binary and a userspace tool located here: +ftp://ftp.suse.com/pub/people/trenn/sources/ec/ +should get used to read out the 256 Embedded Controller registers +or writing to them. + +CAUTION: + Do not write to the Embedded Controller if you don't know + what you are doing! Rebooting afterwards also is a good idea. + This can influence the way your machine is cooled and fans may + not get switched on again after you did a wrong write. diff --git a/Documentation/ABI/testing/debugfs-hisi-hpre b/Documentation/ABI/testing/debugfs-hisi-hpre new file mode 100644 index 000000000..82abf92df --- /dev/null +++ b/Documentation/ABI/testing/debugfs-hisi-hpre @@ -0,0 +1,164 @@ +What: /sys/kernel/debug/hisi_hpre//cluster[0-3]/regs +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: Dump debug registers from the HPRE cluster. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//cluster[0-3]/cluster_ctrl +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: Write the HPRE core selection in the cluster into this file, + and then we can read the debug information of the core. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//rdclr_en +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: HPRE cores debug registers read clear control. 1 means enable + register read clear, otherwise 0. Writing to this file has no + functional effect, only enable or disable counters clear after + reading of these registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//current_qm +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: One HPRE controller has one PF and multiple VFs, each function + has a QM. Select the QM which below qm refers to. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//alg_qos +Date: Jun 2021 +Contact: linux-crypto@vger.kernel.org +Description: The is related the function for PF and VF. + HPRE driver supports to configure each function's QoS, the driver + supports to write value to alg_qos in the host. Such as + "echo value > alg_qos". The qos value is 1~1000, means + 1/1000~1000/1000 of total QoS. The driver reading alg_qos to + get related QoS in the host and VM, Such as "cat alg_qos". + +What: /sys/kernel/debug/hisi_hpre//regs +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: Dump debug registers from the HPRE. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//qm/regs +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: Dump debug registers from the QM. + Available for PF and VF in host. VF in guest currently only + has one debug register. + +What: /sys/kernel/debug/hisi_hpre//qm/current_q +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: One QM may contain multiple queues. Select specific queue to + show its debug registers in above regs. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//qm/clear_enable +Date: Sep 2019 +Contact: linux-crypto@vger.kernel.org +Description: QM debug registers(regs) read clear control. 1 means enable + register read clear, otherwise 0. + Writing to this file has no functional effect, only enable or + disable counters clear after reading of these registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_hpre//qm/err_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of invalid interrupts for + QM task completion. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/aeq_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of QM async event queue interrupts. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/abnormal_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of interrupts for QM abnormal event. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/create_qp_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of queue allocation errors. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/mb_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of failed QM mailbox commands. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/status +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the status of the QM. + Four states: initiated, started, stopped and closed. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//qm/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: QM debug registers(regs) read hardware register value. This + node is used to show the change of the qm register values. This + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: HPRE debug registers(regs) read hardware register value. This + node is used to show the change of the register values. This + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/send_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of sent requests. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/recv_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of received requests. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/send_busy_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of requests sent + with returning busy. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/send_fail_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of completed but error requests. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/invalid_req_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of invalid requests being received. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/overtime_thrhld +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Set the threshold time for counting the request which is + processed longer than the threshold. + 0: disable(default), 1: 1 microsecond. + Available for both PF and VF, and take no other effect on HPRE. + +What: /sys/kernel/debug/hisi_hpre//hpre_dfx/over_thrhld_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of time out requests. + Available for both PF and VF, and take no other effect on HPRE. diff --git a/Documentation/ABI/testing/debugfs-hisi-sec b/Documentation/ABI/testing/debugfs-hisi-sec new file mode 100644 index 000000000..93c530d1b --- /dev/null +++ b/Documentation/ABI/testing/debugfs-hisi-sec @@ -0,0 +1,137 @@ +What: /sys/kernel/debug/hisi_sec2//clear_enable +Date: Oct 2019 +Contact: linux-crypto@vger.kernel.org +Description: Enabling/disabling of clear action after reading + the SEC debug registers. + 0: disable, 1: enable. + Only available for PF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//current_qm +Date: Oct 2019 +Contact: linux-crypto@vger.kernel.org +Description: One SEC controller has one PF and multiple VFs, each function + has a QM. This file can be used to select the QM which below + qm refers to. + Only available for PF. + +What: /sys/kernel/debug/hisi_sec2//alg_qos +Date: Jun 2021 +Contact: linux-crypto@vger.kernel.org +Description: The is related the function for PF and VF. + SEC driver supports to configure each function's QoS, the driver + supports to write value to alg_qos in the host. Such as + "echo value > alg_qos". The qos value is 1~1000, means + 1/1000~1000/1000 of total QoS. The driver reading alg_qos to + get related QoS in the host and VM, Such as "cat alg_qos". + +What: /sys/kernel/debug/hisi_sec2//qm/qm_regs +Date: Oct 2019 +Contact: linux-crypto@vger.kernel.org +Description: Dump of QM related debug registers. + Available for PF and VF in host. VF in guest currently only + has one debug register. + +What: /sys/kernel/debug/hisi_sec2//qm/current_q +Date: Oct 2019 +Contact: linux-crypto@vger.kernel.org +Description: One QM of SEC may contain multiple queues. Select specific + queue to show its debug registers in above 'regs'. + Only available for PF. + +What: /sys/kernel/debug/hisi_sec2//qm/clear_enable +Date: Oct 2019 +Contact: linux-crypto@vger.kernel.org +Description: Enabling/disabling of clear action after reading + the SEC's QM debug registers. + 0: disable, 1: enable. + Only available for PF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/err_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of invalid interrupts for + QM task completion. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/aeq_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of QM async event queue interrupts. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/abnormal_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of interrupts for QM abnormal event. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/create_qp_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of queue allocation errors. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/mb_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of failed QM mailbox commands. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/status +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the status of the QM. + Four states: initiated, started, stopped and closed. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//qm/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: QM debug registers(regs) read hardware register value. This + node is used to show the change of the qm register values. This + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: SEC debug registers(regs) read hardware register value. This + node is used to show the change of the register values. This + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/send_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of sent requests. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/recv_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of received requests. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/send_busy_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of requests sent with returning busy. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/err_bd_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of BD type error requests + to be received. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/invalid_req_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of invalid requests being received. + Available for both PF and VF, and take no other effect on SEC. + +What: /sys/kernel/debug/hisi_sec2//sec_dfx/done_flag_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of completed but marked error requests + to be received. + Available for both PF and VF, and take no other effect on SEC. diff --git a/Documentation/ABI/testing/debugfs-hisi-zip b/Documentation/ABI/testing/debugfs-hisi-zip new file mode 100644 index 000000000..fd3f314cf --- /dev/null +++ b/Documentation/ABI/testing/debugfs-hisi-zip @@ -0,0 +1,138 @@ +What: /sys/kernel/debug/hisi_zip//comp_core[01]/regs +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: Dump of compression cores related debug registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//decomp_core[0-5]/regs +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: Dump of decompression cores related debug registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//clear_enable +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: Compression/decompression core debug registers read clear + control. 1 means enable register read clear, otherwise 0. + Writing to this file has no functional effect, only enable or + disable counters clear after reading of these registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//current_qm +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: One ZIP controller has one PF and multiple VFs, each function + has a QM. Select the QM which below qm refers to. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//alg_qos +Date: Jun 2021 +Contact: linux-crypto@vger.kernel.org +Description: The is related the function for PF and VF. + ZIP driver supports to configure each function's QoS, the driver + supports to write value to alg_qos in the host. Such as + "echo value > alg_qos". The qos value is 1~1000, means + 1/1000~1000/1000 of total QoS. The driver reading alg_qos to + get related QoS in the host and VM, Such as "cat alg_qos". + +What: /sys/kernel/debug/hisi_zip//qm/regs +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: Dump of QM related debug registers. + Available for PF and VF in host. VF in guest currently only + has one debug register. + +What: /sys/kernel/debug/hisi_zip//qm/current_q +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: One QM may contain multiple queues. Select specific queue to + show its debug registers in above regs. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//qm/clear_enable +Date: Nov 2018 +Contact: linux-crypto@vger.kernel.org +Description: QM debug registers(regs) read clear control. 1 means enable + register read clear, otherwise 0. + Writing to this file has no functional effect, only enable or + disable counters clear after reading of these registers. + Only available for PF. + +What: /sys/kernel/debug/hisi_zip//qm/err_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of invalid interrupts for + QM task completion. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/aeq_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of QM async event queue interrupts. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/abnormal_irq +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of interrupts for QM abnormal event. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/create_qp_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of queue allocation errors. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/mb_err +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the number of failed QM mailbox commands. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/status +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the status of the QM. + Four states: initiated, started, stopped and closed. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//qm/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: QM debug registers(regs) read hardware register value. This + node is used to show the change of the qm registers value. This + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_zip//zip_dfx/diff_regs +Date: Mar 2022 +Contact: linux-crypto@vger.kernel.org +Description: ZIP debug registers(regs) read hardware register value. This + node is used to show the change of the registers value. this + node can be help users to check the change of register values. + +What: /sys/kernel/debug/hisi_zip//zip_dfx/send_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of sent requests. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//zip_dfx/recv_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of received requests. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//zip_dfx/send_busy_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of requests received + with returning busy. + Available for both PF and VF, and take no other effect on ZIP. + +What: /sys/kernel/debug/hisi_zip//zip_dfx/err_bd_cnt +Date: Apr 2020 +Contact: linux-crypto@vger.kernel.org +Description: Dump the total number of BD type error requests + to be received. + Available for both PF and VF, and take no other effect on ZIP. diff --git a/Documentation/ABI/testing/debugfs-hyperv b/Documentation/ABI/testing/debugfs-hyperv new file mode 100644 index 000000000..9185e1b06 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-hyperv @@ -0,0 +1,23 @@ +What: /sys/kernel/debug/hyperv//fuzz_test_state +Date: October 2019 +KernelVersion: 5.5 +Contact: Branden Bonaby +Description: Fuzz testing status of a vmbus device, whether its in an ON + state or a OFF state +Users: Debugging tools + +What: /sys/kernel/debug/hyperv//delay/fuzz_test_buffer_interrupt_delay +Date: October 2019 +KernelVersion: 5.5 +Contact: Branden Bonaby +Description: Fuzz testing buffer interrupt delay value between 0 - 1000 + microseconds (inclusive). +Users: Debugging tools + +What: /sys/kernel/debug/hyperv//delay/fuzz_test_message_delay +Date: October 2019 +KernelVersion: 5.5 +Contact: Branden Bonaby +Description: Fuzz testing message delay value between 0 - 1000 microseconds + (inclusive). +Users: Debugging tools diff --git a/Documentation/ABI/testing/debugfs-ideapad b/Documentation/ABI/testing/debugfs-ideapad new file mode 100644 index 000000000..7079c0b21 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-ideapad @@ -0,0 +1,19 @@ +What: /sys/kernel/debug/ideapad/cfg +Date: Sep 2011 +KernelVersion: 3.2 +Contact: Ike Panhc +Description: + +cfg shows the return value of _CFG method in VPC2004 device. It tells machine +capability and what graphic component within the machine. + + +What: /sys/kernel/debug/ideapad/status +Date: Sep 2011 +KernelVersion: 3.2 +Contact: Ike Panhc +Description: + +status shows infos we can read and tells its meaning and value. + + diff --git a/Documentation/ABI/testing/debugfs-moxtet b/Documentation/ABI/testing/debugfs-moxtet new file mode 100644 index 000000000..637d8587d --- /dev/null +++ b/Documentation/ABI/testing/debugfs-moxtet @@ -0,0 +1,35 @@ +What: /sys/kernel/debug/moxtet/input +Date: March 2019 +KernelVersion: 5.3 +Contact: Marek Behún +Description: (Read) Read input from the shift registers, in hexadecimal. + Returns N+1 bytes, where N is the number of Moxtet connected + modules. The first byte is from the CPU board itself. + + Example:: + + 101214 + + == ======================================= + 10 CPU board with SD card + 12 2 = PCIe module, 1 = IRQ not active + 14 4 = Peridot module, 1 = IRQ not active + == ======================================= + +What: /sys/kernel/debug/moxtet/output +Date: March 2019 +KernelVersion: 5.3 +Contact: Marek Behún +Description: (RW) Read last written value to the shift registers, in + hexadecimal, or write values to the shift registers, also + in hexadecimal. + + Example:: + + 0102 + + == ================================================ + 01 01 was last written, or is to be written, to the + first module's shift register + 02 the same for second module + == ================================================ diff --git a/Documentation/ABI/testing/debugfs-olpc b/Documentation/ABI/testing/debugfs-olpc new file mode 100644 index 000000000..bd76cc6d5 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-olpc @@ -0,0 +1,16 @@ +What: /sys/kernel/debug/olpc-ec/cmd +Date: Dec 2011 +KernelVersion: 3.4 +Contact: devel@lists.laptop.org +Description: + +A generic interface for executing OLPC Embedded Controller commands and +reading their responses. + +To execute a command, write data with the format: CC:N A A A A +CC is the (hex) command, N is the count of expected reply bytes, and A A A A +are optional (hex) arguments. + +To read the response (if any), read from the generic node after executing +a command. Hex reply bytes will be returned, *whether or not* they came from +the immediately previous command. diff --git a/Documentation/ABI/testing/debugfs-pfo-nx-crypto b/Documentation/ABI/testing/debugfs-pfo-nx-crypto new file mode 100644 index 000000000..f75a655c1 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-pfo-nx-crypto @@ -0,0 +1,45 @@ +What: /sys/kernel/debug/nx-crypto/* +Date: March 2012 +KernelVersion: 3.4 +Contact: Kent Yoder +Description: + +These debugfs interfaces are built by the nx-crypto driver, built in +arch/powerpc/crypto/nx. + +Error Detection +=============== + +errors: + A u32 providing a total count of errors since the driver was loaded. The + only errors counted here are those returned from the hcall, H_COP_OP. + +last_error: + The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not + recorded here (the hcall will retry until -EBUSY goes away). + +last_error_pid: + The process ID of the process who received the most recent error from the + hcall. + +Device Use +========== + +aes_bytes: + The total number of bytes encrypted using AES in any of the driver's + supported modes. + +aes_ops: + The total number of AES operations submitted to the hardware. + +sha256_bytes: + The total number of bytes hashed by the hardware using SHA-256. + +sha256_ops: + The total number of SHA-256 operations submitted to the hardware. + +sha512_bytes: + The total number of bytes hashed by the hardware using SHA-512. + +sha512_ops: + The total number of SHA-512 operations submitted to the hardware. diff --git a/Documentation/ABI/testing/debugfs-pktcdvd b/Documentation/ABI/testing/debugfs-pktcdvd new file mode 100644 index 000000000..f6f65a4fa --- /dev/null +++ b/Documentation/ABI/testing/debugfs-pktcdvd @@ -0,0 +1,18 @@ +What: /sys/kernel/debug/pktcdvd/pktcdvd[0-7] +Date: Oct. 2006 +KernelVersion: 2.6.20 +Contact: Thomas Maier +Description: + +The pktcdvd module (packet writing driver) creates +these files in debugfs: + +/sys/kernel/debug/pktcdvd/pktcdvd[0-7]/ + + ==== ====== ==================================== + info 0444 Lots of driver statistics and infos. + ==== ====== ==================================== + +Example:: + + cat /sys/kernel/debug/pktcdvd/pktcdvd0/info diff --git a/Documentation/ABI/testing/debugfs-turris-mox-rwtm b/Documentation/ABI/testing/debugfs-turris-mox-rwtm new file mode 100644 index 000000000..813987d5d --- /dev/null +++ b/Documentation/ABI/testing/debugfs-turris-mox-rwtm @@ -0,0 +1,14 @@ +What: /sys/kernel/debug/turris-mox-rwtm/do_sign +Date: Jun 2020 +KernelVersion: 5.8 +Contact: Marek Behún +Description: + + ======= =========================================================== + (Write) Message to sign with the ECDSA private key stored in + device's OTP. The message must be exactly 64 bytes + (since this is intended for SHA-512 hashes). + (Read) The resulting signature, 136 bytes. This contains the + R and S values of the ECDSA signature, both in + big-endian format. + ======= =========================================================== diff --git a/Documentation/ABI/testing/debugfs-wilco-ec b/Documentation/ABI/testing/debugfs-wilco-ec new file mode 100644 index 000000000..682e3c09e --- /dev/null +++ b/Documentation/ABI/testing/debugfs-wilco-ec @@ -0,0 +1,45 @@ +What: /sys/kernel/debug/wilco_ec/h1_gpio +Date: April 2019 +KernelVersion: 5.2 +Description: + As part of Chrome OS's FAFT (Fully Automated Firmware Testing) + tests, we need to ensure that the H1 chip is properly setting + some GPIO lines. The h1_gpio attribute exposes the state + of the lines: + - ENTRY_TO_FACT_MODE in BIT(0) + - SPI_CHROME_SEL in BIT(1) + + Output will formatted with "0x%02x\n". + +What: /sys/kernel/debug/wilco_ec/raw +Date: January 2019 +KernelVersion: 5.1 +Description: + Write and read raw mailbox commands to the EC. + + You can write a hexadecimal sentence to raw, and that series of + bytes will be sent to the EC. Then, you can read the bytes of + response by reading from raw. + + For writing, bytes 0-1 indicate the message type, one of enum + wilco_ec_msg_type. Byte 2+ consist of the data passed in the + request, starting at MBOX[0]. At least three bytes are required + for writing, two for the type and at least a single byte of + data. + + Example:: + + // Request EC info type 3 (EC firmware build date) + // Corresponds with sending type 0x00f0 with + // MBOX = [38, 00, 03, 00] + $ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw + // View the result. The decoded ASCII result "12/21/18" is + // included after the raw hex. + // Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...] + $ cat /sys/kernel/debug/wilco_ec/raw + 00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8... + + Note that the first 16 bytes of the received MBOX[] will be + printed, even if some of the data is junk, and skipping bytes + 17 to 32. It is up to you to know how many of the first bytes of + data are the actual response. diff --git a/Documentation/ABI/testing/dell-smbios-wmi b/Documentation/ABI/testing/dell-smbios-wmi new file mode 100644 index 000000000..f58229084 --- /dev/null +++ b/Documentation/ABI/testing/dell-smbios-wmi @@ -0,0 +1,41 @@ +What: /dev/wmi/dell-smbios +Date: November 2017 +KernelVersion: 4.15 +Contact: Dell.Client.Kernel@dell.com +Description: + Perform SMBIOS calls on supported Dell machines. + through the Dell ACPI-WMI interface. + + IOCTL's and buffer formats are defined in: + + + 1) To perform an SMBIOS call from userspace, you'll need to + first determine the minimum size of the calling interface + buffer for your machine. + Platforms that contain larger buffers can return larger + objects from the system firmware. + Commonly this size is either 4k or 32k. + + To determine the size of the buffer read() a u64 dword from + the WMI character device /dev/wmi/dell-smbios. + + 2) After you've determined the minimum size of the calling + interface buffer, you can allocate a structure that represents + the structure documented above. + + 3) In the 'length' object store the size of the buffer you + determined above and allocated. + + 4) In this buffer object, prepare as necessary for the SMBIOS + call you're interested in. Typically SMBIOS buffers have + "class", "select", and "input" defined to values that coincide + with the data you are interested in. + Documenting class/select/input values is outside of the scope + of this documentation. Check with the libsmbios project for + further documentation on these values. + + 6) Run the call by using ioctl() as described in the header. + + 7) The output will be returned in the buffer object. + + 8) Be sure to free up your allocated object. diff --git a/Documentation/ABI/testing/dev-kmsg b/Documentation/ABI/testing/dev-kmsg new file mode 100644 index 000000000..a377b6c09 --- /dev/null +++ b/Documentation/ABI/testing/dev-kmsg @@ -0,0 +1,127 @@ +What: /dev/kmsg +Date: Mai 2012 +KernelVersion: 3.5 +Contact: Kay Sievers +Description: The /dev/kmsg character device node provides userspace access + to the kernel's printk buffer. + + Injecting messages: + + Every write() to the opened device node places a log entry in + the kernel's printk buffer. + + The logged line can be prefixed with a syslog prefix, which + carries the syslog priority and facility. The single decimal + prefix number is composed of the 3 lowest bits being the syslog + priority and the next 8 bits the syslog facility number. + + If no prefix is given, the priority number is the default kernel + log priority and the facility number is set to LOG_USER (1). It + is not possible to inject messages from userspace with the + facility number LOG_KERN (0), to make sure that the origin of + the messages can always be reliably determined. + + Accessing the buffer: + + Every read() from the opened device node receives one record + of the kernel's printk buffer. + + The first read() directly following an open() always returns + first message in the buffer; there is no kernel-internal + persistent state; many readers can concurrently open the device + and read from it, without affecting other readers. + + Every read() will receive the next available record. If no more + records are available read() will block, or if O_NONBLOCK is + used -EAGAIN returned. + + Messages in the record ring buffer get overwritten as whole, + there are never partial messages received by read(). + + In case messages get overwritten in the circular buffer while + the device is kept open, the next read() will return -EPIPE, + and the seek position be updated to the next available record. + Subsequent reads() will return available records again. + + Unlike the classic syslog() interface, the 64 bit record + sequence numbers allow to calculate the amount of lost + messages, in case the buffer gets overwritten. And they allow + to reconnect to the buffer and reconstruct the read position + if needed, without limiting the interface to a single reader. + + The device supports seek with the following parameters: + + SEEK_SET, 0 + seek to the first entry in the buffer + SEEK_END, 0 + seek after the last entry in the buffer + SEEK_DATA, 0 + seek after the last record available at the time + the last SYSLOG_ACTION_CLEAR was issued. + + Other seek operations or offsets are not supported because of + the special behavior this device has. The device allows to read + or write only whole variable length messages (records) that are + stored in a ring buffer. + + Because of the non-standard behavior also the error values are + non-standard. -ESPIPE is returned for non-zero offset. -EINVAL + is returned for other operations, e.g. SEEK_CUR. This behavior + and values are historical and could not be modified without the + risk of breaking userspace. + + The output format consists of a prefix carrying the syslog + prefix including priority and facility, the 64 bit message + sequence number and the monotonic timestamp in microseconds, + and a flag field. All fields are separated by a ','. + + Future extensions might add more comma separated values before + the terminating ';'. Unknown fields and values should be + gracefully ignored. + + The human readable text string starts directly after the ';' + and is terminated by a '\n'. Untrusted values derived from + hardware or other facilities are printed, therefore + all non-printable characters and '\' itself in the log message + are escaped by "\x00" C-style hex encoding. + + A line starting with ' ', is a continuation line, adding + key/value pairs to the log message, which provide the machine + readable context of the message, for reliable processing in + userspace. + + Example:: + + 7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored) + SUBSYSTEM=acpi + DEVICE=+acpi:PNP0A03:00 + 6,339,5140900,-;NET: Registered protocol family 10 + 30,340,5690716,-;udevd[80]: starting version 181 + + The DEVICE= key uniquely identifies devices the following way: + + ============ ================= + b12:8 block dev_t + c127:3 char dev_t + n8 netdev ifindex + +sound:card0 subsystem:devname + ============ ================= + + The flags field carries '-' by default. A 'c' indicates a + fragment of a line. Note, that these hints about continuation + lines are not necessarily correct, and the stream could be + interleaved with unrelated messages, but merging the lines in + the output usually produces better human readable results. A + similar logic is used internally when messages are printed to + the console, /proc/kmsg or the syslog() syscall. + + By default, kernel tries to avoid fragments by concatenating + when it can and fragments are rare; however, when extended + console support is enabled, the in-kernel concatenation is + disabled and /dev/kmsg output will contain more fragments. If + the log consumer performs concatenation, the end result + should be the same. In the future, the in-kernel concatenation + may be removed entirely and /dev/kmsg users are recommended to + implement fragment handling. + +Users: dmesg(1), userspace kernel log consumers diff --git a/Documentation/ABI/testing/devlink-resource-mlxsw b/Documentation/ABI/testing/devlink-resource-mlxsw new file mode 100644 index 000000000..259ed2948 --- /dev/null +++ b/Documentation/ABI/testing/devlink-resource-mlxsw @@ -0,0 +1,33 @@ +What: /kvd/ +Date: 08-Jan-2018 +KernelVersion: v4.16 +Contact: mlxsw@mellanox.com +Description: The main database in the Spectrum device is a centralized + KVD database used for many of the tables used to configure + the chip including L2 FDB, L3 LPM, ECMP and more. The KVD + is divided into two sections, the first is hash-based table + and the second is a linear access table. The division + between the linear and hash-based sections is static and + require reload before the changes take effect. + +What: /kvd/linear +Date: 08-Jan-2018 +KernelVersion: v4.16 +Contact: mlxsw@mellanox.com +Description: The linear section of the KVD is managed by software as a + flat memory accessed using an index. + +What: /kvd/hash_single +Date: 08-Jan-2018 +KernelVersion: v4.16 +Contact: mlxsw@mellanox.com +Description: The hash based section of the KVD is managed by the switch + device. Used in case the key size is smaller or equal to + 64bit. + +What: /kvd/hash_double +Date: 08-Jan-2018 +KernelVersion: v4.16 +Contact: mlxsw@mellanox.com +Description: The hash based section of the KVD is managed by the switch + device. Used in case the key is larger than 64 bit. diff --git a/Documentation/ABI/testing/evm b/Documentation/ABI/testing/evm new file mode 100644 index 000000000..44750a933 --- /dev/null +++ b/Documentation/ABI/testing/evm @@ -0,0 +1,108 @@ +What: /sys/kernel/security/evm +What: /sys/kernel/security/*/evm +Date: March 2011 +Contact: Mimi Zohar +Description: + EVM protects a file's security extended attributes(xattrs) + against integrity attacks. The initial method maintains an + HMAC-sha1 value across the extended attributes, storing the + value as the extended attribute 'security.evm'. + + EVM supports two classes of security.evm. The first is + an HMAC-sha1 generated locally with a + trusted/encrypted key stored in the Kernel Key + Retention System. The second is a digital signature + generated either locally or remotely using an + asymmetric key. These keys are loaded onto root's + keyring using keyctl, and EVM is then enabled by + echoing a value to /evm made up of the + following bits: + + === ================================================== + Bit Effect + === ================================================== + 0 Enable HMAC validation and creation + 1 Enable digital signature validation + 2 Permit modification of EVM-protected metadata at + runtime. Not supported if HMAC validation and + creation is enabled (deprecated). + 31 Disable further runtime modification of EVM policy + === ================================================== + + For example:: + + echo 1 >/evm + + will enable HMAC validation and creation + + :: + + echo 0x80000003 >/evm + + will enable HMAC and digital signature validation and + HMAC creation and disable all further modification of policy. + + :: + + echo 0x80000006 >/evm + + will enable digital signature validation, permit + modification of EVM-protected metadata and + disable all further modification of policy. This option is now + deprecated in favor of:: + + echo 0x80000002 >/evm + + as the outstanding issues that prevent the usage of EVM portable + signatures have been solved. + + Echoing a value is additive, the new value is added to the + existing initialization flags. + + For example, after:: + + echo 2 >/evm + + another echo can be performed:: + + echo 1 >/evm + + and the resulting value will be 3. + + Note that once an HMAC key has been loaded, it will no longer + be possible to enable metadata modification. Signaling that an + HMAC key has been loaded will clear the corresponding flag. + For example, if the current value is 6 (2 and 4 set):: + + echo 1 >/evm + + will set the new value to 3 (4 cleared). + + Loading an HMAC key is the only way to disable metadata + modification. + + Until key loading has been signaled EVM can not create + or validate the 'security.evm' xattr, but returns + INTEGRITY_UNKNOWN. Loading keys and signaling EVM + should be done as early as possible. Normally this is + done in the initramfs, which has already been measured + as part of the trusted boot. For more information on + creating and loading existing trusted/encrypted keys, + refer to: + Documentation/security/keys/trusted-encrypted.rst. Both + dracut (via 97masterkey and 98integrity) and systemd (via + core/ima-setup) have support for loading keys at boot + time. + +What: /sys/kernel/security/*/evm/evm_xattrs +Date: April 2018 +Contact: Matthew Garrett +Description: + Shows the set of extended attributes used to calculate or + validate the EVM signature, and allows additional attributes + to be added at runtime. Any signatures generated after + additional attributes are added (and on files possessing those + additional attributes) will only be valid if the same + additional attributes are configured on system boot. Writing + a single period (.) will lock the xattr list from any further + modification. diff --git a/Documentation/ABI/testing/gpio-cdev b/Documentation/ABI/testing/gpio-cdev new file mode 100644 index 000000000..66bdcd188 --- /dev/null +++ b/Documentation/ABI/testing/gpio-cdev @@ -0,0 +1,27 @@ +What: /dev/gpiochip[0-9]+ +Date: November 2015 +KernelVersion: 4.4 +Contact: linux-gpio@vger.kernel.org +Description: + The character device files /dev/gpiochip* are the interface + between GPIO chips and userspace. + + The ioctl(2)-based ABI is defined and documented in + [include/uapi]. + + The following file operations are supported: + + open(2) + Currently the only useful flags are O_RDWR. + + ioctl(2) + Initiate various actions. + + See the inline documentation in [include/uapi] + for descriptions of all ioctls. + + close(2) + Stops and free up the I/O contexts that was associated + with the file descriptor. + +Users: TBD diff --git a/Documentation/ABI/testing/ima_policy b/Documentation/ABI/testing/ima_policy new file mode 100644 index 000000000..db17fc8a0 --- /dev/null +++ b/Documentation/ABI/testing/ima_policy @@ -0,0 +1,190 @@ +What: /sys/kernel/security/*/ima/policy +Date: May 2008 +Contact: Mimi Zohar +Description: + The Trusted Computing Group(TCG) runtime Integrity + Measurement Architecture(IMA) maintains a list of hash + values of executables and other sensitive system files + loaded into the run-time of this system. At runtime, + the policy can be constrained based on LSM specific data. + Policies are loaded into the securityfs file ima/policy + by opening the file, writing the rules one at a time and + then closing the file. The new policy takes effect after + the file ima/policy is closed. + + IMA appraisal, if configured, uses these file measurements + for local measurement appraisal. + + :: + + rule format: action [condition ...] + + action: measure | dont_measure | appraise | dont_appraise | + audit | hash | dont_hash + condition:= base | lsm [option] + base: [[func=] [mask=] [fsmagic=] [fsuuid=] [fsname=] + [uid=] [euid=] [gid=] [egid=] + [fowner=] [fgroup=]] + lsm: [[subj_user=] [subj_role=] [subj_type=] + [obj_user=] [obj_role=] [obj_type=]] + option: [digest_type=] [template=] [permit_directio] + [appraise_type=] [appraise_flag=] + [appraise_algos=] [keyrings=] + base: + func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK][MODULE_CHECK] + [FIRMWARE_CHECK] + [KEXEC_KERNEL_CHECK] [KEXEC_INITRAMFS_CHECK] + [KEXEC_CMDLINE] [KEY_CHECK] [CRITICAL_DATA] + [SETXATTR_CHECK] + mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND] + [[^]MAY_EXEC] + fsmagic:= hex value + fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6) + uid:= decimal value + euid:= decimal value + gid:= decimal value + egid:= decimal value + fowner:= decimal value + fgroup:= decimal value + lsm: are LSM specific + option: + appraise_type:= [imasig] | [imasig|modsig] | [sigv3] + where 'imasig' is the original or the signature + format v2. + where 'modsig' is an appended signature, + where 'sigv3' is the signature format v3. (Currently + limited to fsverity digest based signatures + stored in security.ima xattr. Requires + specifying "digest_type=verity" first.) + + appraise_flag:= [check_blacklist] + Currently, blacklist check is only for files signed with appended + signature. + digest_type:= verity + Require fs-verity's file digest instead of the + regular IMA file hash. + keyrings:= list of keyrings + (eg, .builtin_trusted_keys|.ima). Only valid + when action is "measure" and func is KEY_CHECK. + template:= name of a defined IMA template type + (eg, ima-ng). Only valid when action is "measure". + pcr:= decimal value + label:= [selinux]|[kernel_info]|[data_label] + data_label:= a unique string used for grouping and limiting critical data. + For example, "selinux" to measure critical data for SELinux. + appraise_algos:= comma-separated list of hash algorithms + For example, "sha256,sha512" to only accept to appraise + files where the security.ima xattr was hashed with one + of these two algorithms. + + default policy: + # PROC_SUPER_MAGIC + dont_measure fsmagic=0x9fa0 + dont_appraise fsmagic=0x9fa0 + # SYSFS_MAGIC + dont_measure fsmagic=0x62656572 + dont_appraise fsmagic=0x62656572 + # DEBUGFS_MAGIC + dont_measure fsmagic=0x64626720 + dont_appraise fsmagic=0x64626720 + # TMPFS_MAGIC + dont_measure fsmagic=0x01021994 + dont_appraise fsmagic=0x01021994 + # RAMFS_MAGIC + dont_appraise fsmagic=0x858458f6 + # DEVPTS_SUPER_MAGIC + dont_measure fsmagic=0x1cd1 + dont_appraise fsmagic=0x1cd1 + # BINFMTFS_MAGIC + dont_measure fsmagic=0x42494e4d + dont_appraise fsmagic=0x42494e4d + # SECURITYFS_MAGIC + dont_measure fsmagic=0x73636673 + dont_appraise fsmagic=0x73636673 + # SELINUX_MAGIC + dont_measure fsmagic=0xf97cff8c + dont_appraise fsmagic=0xf97cff8c + # CGROUP_SUPER_MAGIC + dont_measure fsmagic=0x27e0eb + dont_appraise fsmagic=0x27e0eb + # NSFS_MAGIC + dont_measure fsmagic=0x6e736673 + dont_appraise fsmagic=0x6e736673 + + measure func=BPRM_CHECK + measure func=FILE_MMAP mask=MAY_EXEC + measure func=FILE_CHECK mask=MAY_READ uid=0 + measure func=MODULE_CHECK + measure func=FIRMWARE_CHECK + appraise fowner=0 + + The default policy measures all executables in bprm_check, + all files mmapped executable in file_mmap, and all files + open for read by root in do_filp_open. The default appraisal + policy appraises all files owned by root. + + Examples of LSM specific definitions: + + SELinux:: + + dont_measure obj_type=var_log_t + dont_appraise obj_type=var_log_t + dont_measure obj_type=auditd_log_t + dont_appraise obj_type=auditd_log_t + measure subj_user=system_u func=FILE_CHECK mask=MAY_READ + measure subj_role=system_r func=FILE_CHECK mask=MAY_READ + + Smack:: + + measure subj_user=_ func=FILE_CHECK mask=MAY_READ + + Example of measure rules using alternate PCRs:: + + measure func=KEXEC_KERNEL_CHECK pcr=4 + measure func=KEXEC_INITRAMFS_CHECK pcr=5 + + Example of appraise rule allowing modsig appended signatures: + + appraise func=KEXEC_KERNEL_CHECK appraise_type=imasig|modsig + + Example of measure rule using KEY_CHECK to measure all keys: + + measure func=KEY_CHECK + + Example of measure rule using KEY_CHECK to only measure + keys added to .builtin_trusted_keys or .ima keyring: + + measure func=KEY_CHECK keyrings=.builtin_trusted_keys|.ima + + Example of the special SETXATTR_CHECK appraise rule, that + restricts the hash algorithms allowed when writing to the + security.ima xattr of a file: + + appraise func=SETXATTR_CHECK appraise_algos=sha256,sha384,sha512 + + Example of a 'measure' rule requiring fs-verity's digests + with indication of type of digest in the measurement list. + + measure func=FILE_CHECK digest_type=verity \ + template=ima-ngv2 + + Example of 'measure' and 'appraise' rules requiring fs-verity + signatures (format version 3) stored in security.ima xattr. + + The 'measure' rule specifies the 'ima-sigv3' template option, + which includes the indication of type of digest and the file + signature in the measurement list. + + measure func=BPRM_CHECK digest_type=verity \ + template=ima-sigv3 + + + The 'appraise' rule specifies the type and signature format + version (sigv3) required. + + appraise func=BPRM_CHECK digest_type=verity \ + appraise_type=sigv3 + + All of these policy rules could, for example, be constrained + either based on a filesystem's UUID (fsuuid) or based on LSM + labels. diff --git a/Documentation/ABI/testing/ppc-memtrace b/Documentation/ABI/testing/ppc-memtrace new file mode 100644 index 000000000..9606aed33 --- /dev/null +++ b/Documentation/ABI/testing/ppc-memtrace @@ -0,0 +1,46 @@ +What: /sys/kernel/debug/powerpc/memtrace +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: This folder contains the relevant debugfs files for the + hardware trace macro to use. CONFIG_PPC64_HARDWARE_TRACING + must be set. + +What: /sys/kernel/debug/powerpc/memtrace/enable +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: Write an integer containing the size in bytes of the memory + you want removed from each NUMA node to this file - it must be + aligned to the memblock size. This amount of RAM will be removed + from each NUMA node in the kernel mappings and the following + debugfs files will be created. Once memory is successfully + removed from each node, the following files are created. To + re-add memory to the kernel, echo 0 into this file (it will be + automatically onlined). + +What: /sys/kernel/debug/powerpc/memtrace/ +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: This directory contains information about the removed memory + from the specific NUMA node. + +What: /sys/kernel/debug/powerpc/memtrace//size +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: This contains the size of the memory removed from the node. + +What: /sys/kernel/debug/powerpc/memtrace//start +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: This contains the start address of the removed memory. + +What: /sys/kernel/debug/powerpc/memtrace//trace +Date: Aug 2017 +KernelVersion: 4.14 +Contact: linuxppc-dev@lists.ozlabs.org +Description: This is where the hardware trace macro will output the trace + it generates. diff --git a/Documentation/ABI/testing/procfs-attr-current b/Documentation/ABI/testing/procfs-attr-current new file mode 100644 index 000000000..198b9fe1c --- /dev/null +++ b/Documentation/ABI/testing/procfs-attr-current @@ -0,0 +1,20 @@ +What: /proc/*/attr/current +Contact: linux-security-module@vger.kernel.org, + selinux@vger.kernel.org, + apparmor@lists.ubuntu.com +Description: The current security information used by a Linux + security module (LSM) that is active on the system. + The details of permissions required to read from + this interface and hence obtain the security state + of the task identified is LSM dependent. + A process cannot write to this interface unless it + refers to itself. + The other details of permissions required to write to + this interface and hence change the security state of + the task identified are LSM dependent. + The format of the data used by this interface is LSM + dependent. + SELinux, Smack and AppArmor provide this interface. +Users: SELinux user-space + Smack user-space + AppArmor user-space diff --git a/Documentation/ABI/testing/procfs-attr-exec b/Documentation/ABI/testing/procfs-attr-exec new file mode 100644 index 000000000..34593866a --- /dev/null +++ b/Documentation/ABI/testing/procfs-attr-exec @@ -0,0 +1,20 @@ +What: /proc/*/attr/exec +Contact: linux-security-module@vger.kernel.org, + selinux@vger.kernel.org, + apparmor@lists.ubuntu.com +Description: The security information to be used on the process + by a Linux security module (LSM) active on the system + after a subsequent exec() call. + The details of permissions required to read from + this interface and hence obtain the security state + of the task identified is LSM dependent. + A process cannot write to this interface unless it + refers to itself. + The other details of permissions required to write to + this interface and hence change the security state of + the task identified are LSM dependent. + The format of the data used by this interface is LSM + dependent. + SELinux and AppArmor provide this interface. +Users: SELinux user-space + AppArmor user-space diff --git a/Documentation/ABI/testing/procfs-attr-prev b/Documentation/ABI/testing/procfs-attr-prev new file mode 100644 index 000000000..f990b3595 --- /dev/null +++ b/Documentation/ABI/testing/procfs-attr-prev @@ -0,0 +1,19 @@ +What: /proc/*/attr/prev +Contact: linux-security-module@vger.kernel.org, + selinux@vger.kernel.org, + apparmor@lists.ubuntu.com +Description: The security information used on the process by + a Linux security module (LSM) active on the system + prior to the most recent exec() call. + The details of permissions required to read from + this interface is LSM dependent. + A process cannot write to this interface unless it + refers to itself. + The other details of permissions required to write to + this interface are LSM dependent. + The format of the data used by this interface is LSM + dependent. + SELinux and AppArmor provide this interface. +Users: SELinux user-space + AppArmor user-space + diff --git a/Documentation/ABI/testing/procfs-diskstats b/Documentation/ABI/testing/procfs-diskstats new file mode 100644 index 000000000..e58d64144 --- /dev/null +++ b/Documentation/ABI/testing/procfs-diskstats @@ -0,0 +1,43 @@ +What: /proc/diskstats +Date: February 2008 +Contact: Jerome Marchand +Description: + The /proc/diskstats file displays the I/O statistics + of block devices. Each line contains the following 14 + fields: + + == =================================== + 1 major number + 2 minor mumber + 3 device name + 4 reads completed successfully + 5 reads merged + 6 sectors read + 7 time spent reading (ms) + 8 writes completed + 9 writes merged + 10 sectors written + 11 time spent writing (ms) + 12 I/Os currently in progress + 13 time spent doing I/Os (ms) + 14 weighted time spent doing I/Os (ms) + == =================================== + + Kernel 4.18+ appends four more fields for discard + tracking putting the total at 18: + + == =================================== + 15 discards completed successfully + 16 discards merged + 17 sectors discarded + 18 time spent discarding + == =================================== + + Kernel 5.5+ appends two more fields for flush requests: + + == ===================================== + 19 flush requests completed successfully + 20 time spent flushing + == ===================================== + + For more details refer to Documentation/admin-guide/iostats.rst diff --git a/Documentation/ABI/testing/procfs-smaps_rollup b/Documentation/ABI/testing/procfs-smaps_rollup new file mode 100644 index 000000000..b446a7154 --- /dev/null +++ b/Documentation/ABI/testing/procfs-smaps_rollup @@ -0,0 +1,42 @@ +What: /proc/pid/smaps_rollup +Date: August 2017 +Contact: Daniel Colascione +Description: + This file provides pre-summed memory information for a + process. The format is almost identical to /proc/pid/smaps, + except instead of an entry for each VMA in a process, + smaps_rollup has a single entry (tagged "[rollup]") + for which each field is the sum of the corresponding + fields from all the maps in /proc/pid/smaps. + Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem + are not present in /proc/pid/smaps. These fields represent + the sum of the Pss field of each type (anon, file, shmem). + For more details, see Documentation/filesystems/proc.rst + and the procfs man page. + + Typical output looks like this:: + + 00100000-ff709000 ---p 00000000 00:00 0 [rollup] + Size: 1192 kB + KernelPageSize: 4 kB + MMUPageSize: 4 kB + Rss: 884 kB + Pss: 385 kB + Pss_Dirty: 68 kB + Pss_Anon: 301 kB + Pss_File: 80 kB + Pss_Shmem: 4 kB + Shared_Clean: 696 kB + Shared_Dirty: 0 kB + Private_Clean: 120 kB + Private_Dirty: 68 kB + Referenced: 884 kB + Anonymous: 68 kB + LazyFree: 0 kB + AnonHugePages: 0 kB + ShmemPmdMapped: 0 kB + Shared_Hugetlb: 0 kB + Private_Hugetlb: 0 kB + Swap: 0 kB + SwapPss: 0 kB + Locked: 385 kB diff --git a/Documentation/ABI/testing/pstore b/Documentation/ABI/testing/pstore new file mode 100644 index 000000000..d3cff4a7e --- /dev/null +++ b/Documentation/ABI/testing/pstore @@ -0,0 +1,47 @@ +What: /sys/fs/pstore/... +What: /dev/pstore/... +Date: March 2011 +KernelVersion: 2.6.39 +Contact: tony.luck@intel.com +Description: Generic interface to platform dependent persistent storage. + + Platforms that provide a mechanism to preserve some data + across system reboots can register with this driver to + provide a generic interface to show records captured in + the dying moments. In the case of a panic the last part + of the console log is captured, but other interesting + data can also be saved:: + + # mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore + + $ ls -l /sys/fs/pstore/ + total 0 + -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1 + + Different users of this interface will result in different + filename prefixes. Currently two are defined: + + - "dmesg" - saved console log + - "mce" - architecture dependent data from fatal h/w error + + Once the information in a file has been read, removing + the file will signal to the underlying persistent storage + device that it can reclaim the space for later re-use:: + + $ rm /sys/fs/pstore/dmesg-erst-1 + + The expectation is that all files in /sys/fs/pstore/ + will be saved elsewhere and erased from persistent store + soon after boot to free up space ready for the next + catastrophe. + + The 'kmsg_bytes' mount option changes the target amount of + data saved on each oops/panic. Pstore saves (possibly + multiple) files based on the record size of the underlying + persistent storage until at least this amount is reached. + Default is 10 Kbytes. + + Pstore only supports one backend at a time. If multiple + backends are available, the preferred backend may be + set by passing the pstore.backend= argument to the kernel at + boot time. diff --git a/Documentation/ABI/testing/rtc-cdev b/Documentation/ABI/testing/rtc-cdev new file mode 100644 index 000000000..25910c3c3 --- /dev/null +++ b/Documentation/ABI/testing/rtc-cdev @@ -0,0 +1,50 @@ +What: /dev/rtcX +Date: April 2005 +KernelVersion: 2.6.12 +Contact: linux-rtc@vger.kernel.org +Description: + The ioctl interface to drivers for real-time clocks (RTCs). + Following actions are supported: + + * RTC_RD_TIME, RTC_SET_TIME: Read or set the RTC time. Time + format is a Gregorian calendar date and 24 hour wall clock + time. + + * RTC_AIE_ON, RTC_AIE_OFF: Enable or disable the alarm interrupt + for RTCs that support alarms + + * RTC_ALM_READ, RTC_ALM_SET: Read or set the alarm time for + RTCs that support alarms. Can be set upto 24 hours in the + future. Requires a separate RTC_AIE_ON call to enable the + alarm interrupt. (Prefer to use RTC_WKALM_*) + + * RTC_WKALM_RD, RTC_WKALM_SET: For RTCs that support a more + powerful interface, which can issue alarms beyond 24 hours and + enable IRQs in the same request. + + * RTC_PIE_ON, RTC_PIE_OFF: Enable or disable the periodic + interrupt for RTCs that support periodic interrupts. + + * RTC_UIE_ON, RTC_UIE_OFF: Enable or disable the update + interrupt for RTCs that support it. + + * RTC_IRQP_READ, RTC_IRQP_SET: Read or set the frequency for + periodic interrupts for RTCs that support periodic interrupts. + Requires a separate RTC_PIE_ON call to enable the periodic + interrupts. + + * RTC_VL_READ: Read the voltage inputs status of the RTC when + supported. The value is a bit field of RTC_VL_*, giving the + status of the main and backup voltages. + + * RTC_VL_CLEAR: Clear the voltage status of the RTC. Some RTCs + need user interaction when the backup power provider is + replaced or charged to be able to clear the status. + + The ioctl() calls supported by the older /dev/rtc interface are + also supported by the newer RTC class framework. However, + because the chips and systems are not standardized, some PC/AT + functionality might not be provided. And in the same way, some + newer features -- including those enabled by ACPI -- are exposed + by the RTC class framework, but can't be supported by the older + driver. diff --git a/Documentation/ABI/testing/securityfs-secrets-coco b/Documentation/ABI/testing/securityfs-secrets-coco new file mode 100644 index 000000000..f2b690915 --- /dev/null +++ b/Documentation/ABI/testing/securityfs-secrets-coco @@ -0,0 +1,51 @@ +What: security/secrets/coco +Date: February 2022 +Contact: Dov Murik +Description: + Exposes confidential computing (coco) EFI secrets to + userspace via securityfs. + + EFI can declare memory area used by confidential computing + platforms (such as AMD SEV and SEV-ES) for secret injection by + the Guest Owner during VM's launch. The secrets are encrypted + by the Guest Owner and decrypted inside the trusted enclave, + and therefore are not readable by the untrusted host. + + The efi_secret module exposes the secrets to userspace. Each + secret appears as a file under /secrets/coco, + where the filename is the GUID of the entry in the secrets + table. This module is loaded automatically by the EFI driver + if the EFI secret area is populated. + + Two operations are supported for the files: read and unlink. + Reading the file returns the content of secret entry. + Unlinking the file overwrites the secret data with zeroes and + removes the entry from the filesystem. A secret cannot be read + after it has been unlinked. + + For example, listing the available secrets:: + + # modprobe efi_secret + # ls -l /sys/kernel/security/secrets/coco + -r--r----- 1 root root 0 Jun 28 11:54 736870e5-84f0-4973-92ec-06879ce3da0b + -r--r----- 1 root root 0 Jun 28 11:54 83c83f7f-1356-4975-8b7e-d3a0b54312c6 + -r--r----- 1 root root 0 Jun 28 11:54 9553f55d-3da2-43ee-ab5d-ff17f78864d2 + -r--r----- 1 root root 0 Jun 28 11:54 e6f5a162-d67f-4750-a67c-5d065f2a9910 + + Reading the secret data by reading a file:: + + # cat /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910 + the-content-of-the-secret-data + + Wiping a secret by unlinking a file:: + + # rm /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910 + # ls -l /sys/kernel/security/secrets/coco + -r--r----- 1 root root 0 Jun 28 11:54 736870e5-84f0-4973-92ec-06879ce3da0b + -r--r----- 1 root root 0 Jun 28 11:54 83c83f7f-1356-4975-8b7e-d3a0b54312c6 + -r--r----- 1 root root 0 Jun 28 11:54 9553f55d-3da2-43ee-ab5d-ff17f78864d2 + + Note: The binary format of the secrets table injected by the + Guest Owner is described in + drivers/virt/coco/efi_secret/efi_secret.c under "Structure of + the EFI secret area". diff --git a/Documentation/ABI/testing/sysfs-amd-pmc b/Documentation/ABI/testing/sysfs-amd-pmc new file mode 100644 index 000000000..c421b7284 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-amd-pmc @@ -0,0 +1,13 @@ +What: /sys/bus/platform/drivers/amd_pmc/*/smu_fw_version +Date: October 2022 +Contact: Mario Limonciello +Description: Reading this file reports the version of the firmware loaded to + System Management Unit (SMU) contained in AMD CPUs and + APUs. + +What: /sys/bus/platform/drivers/amd_pmc/*/smu_program +Date: October 2022 +Contact: Mario Limonciello +Description: Reading this file reports the program corresponding to the SMU + firmware version. The program field is used to disambiguate two + APU/CPU models that can share the same firmware binary. diff --git a/Documentation/ABI/testing/sysfs-amd-pmf b/Documentation/ABI/testing/sysfs-amd-pmf new file mode 100644 index 000000000..7fc0e1c2b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-amd-pmf @@ -0,0 +1,13 @@ +What: /sys/devices/platform/*/cnqf_enable +Date: September 2022 +Contact: Shyam Sundar S K +Description: Reading this file tells if the AMD Platform Management(PMF) + Cool n Quiet Framework(CnQF) feature is enabled or not. + + This feature is not enabled by default and gets only turned on + if OEM BIOS passes a "flag" to PMF ACPI function (index 11 or 12) + or in case the user writes "on". + + To turn off CnQF user can write "off" to the sysfs node. + Note: Systems that support auto mode will not have this sysfs file + available. diff --git a/Documentation/ABI/testing/sysfs-ata b/Documentation/ABI/testing/sysfs-ata new file mode 100644 index 000000000..3daecac48 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-ata @@ -0,0 +1,140 @@ +What: /sys/class/ata_* +Description: + Provide a place in sysfs for storing the ATA topology of the + system. This allows retrieving various information about ATA + objects. + +Files under /sys/class/ata_port +------------------------------- + +For each port, a directory ataX is created where X is the ata_port_id of the +port. The device parent is the ata host device. + + +What: /sys/class/ata_port/ataX/nr_pmp_links +What: /sys/class/ata_port/ataX/idle_irq +Date: May, 2010 +KernelVersion: v2.6.37 +Contact: Gwendal Grignou +Description: + nr_pmp_links: (RO) If a SATA Port Multiplier (PM) is + connected, the number of links behind it. + + idle_irq: (RO) Number of IRQ received by the port while + idle [some ata HBA only]. + + +What: /sys/class/ata_port/ataX/port_no +Date: May, 2013 +KernelVersion: v3.11 +Contact: Gwendal Grignou +Description: + (RO) Host local port number. While registering host controller, + port numbers are tracked based upon number of ports available on + the controller. This attribute is needed by udev for composing + persistent links in /dev/disk/by-path. + +Files under /sys/class/ata_link +------------------------------- + +Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15 +ata_link objects are created. + +If a link is behind a port, the directory name is linkX, where X is ata_port_id +of the port. If a link is behind a PM, its name is linkX.Y where X is +ata_port_id of the parent port and Y the PM port. + + +What: /sys/class/ata_link/linkX[.Y]/hw_sata_spd_limit +What: /sys/class/ata_link/linkX[.Y]/sata_spd_limit +What: /sys/class/ata_link/linkX[.Y]/sata_spd +Date: May, 2010 +KernelVersion: v2.6.37 +Contact: Gwendal Grignou +Description: + hw_sata_spd_limit: (RO) Maximum speed supported by the + connected SATA device. + + sata_spd_limit: (RO) Maximum speed imposed by libata. + + sata_spd: (RO) Current speed of the link + eg. 1.5, 3 Gbps etc. + + +Files under /sys/class/ata_device +--------------------------------- + +Behind each link, up to two ata devices are created. +The name of the directory is devX[.Y].Z where: +- X is ata_port_id of the port where the device is connected, +- Y the port of the PM if any, and +- Z the device id: for PATA, there is usually 2 devices [0,1], only 1 for SATA. + + +What: /sys/class/ata_device/devX[.Y].Z/spdn_cnt +What: /sys/class/ata_device/devX[.Y].Z/gscr +What: /sys/class/ata_device/devX[.Y].Z/ering +What: /sys/class/ata_device/devX[.Y].Z/id +What: /sys/class/ata_device/devX[.Y].Z/pio_mode +What: /sys/class/ata_device/devX[.Y].Z/xfer_mode +What: /sys/class/ata_device/devX[.Y].Z/dma_mode +What: /sys/class/ata_device/devX[.Y].Z/class +Date: May, 2010 +KernelVersion: v2.6.37 +Contact: Gwendal Grignou +Description: + spdn_cnt: (RO) Number of times libata decided to lower the + speed of link due to errors. + + gscr: (RO) Cached result of the dump of PM GSCR + register. Valid registers are: + + 0: SATA_PMP_GSCR_PROD_ID, + 1: SATA_PMP_GSCR_REV, + 2: SATA_PMP_GSCR_PORT_INFO, + 32: SATA_PMP_GSCR_ERROR, + 33: SATA_PMP_GSCR_ERROR_EN, + 64: SATA_PMP_GSCR_FEAT, + 96: SATA_PMP_GSCR_FEAT_EN, + 130: SATA_PMP_GSCR_SII_GPIO + + Only valid if the device is a PM. + + ering: (RO) Formatted output of the error ring of the + device. + + id: (RO) Cached result of IDENTIFY command, as + described in ATA8 7.16 and 7.17. Only valid if + the device is not a PM. + + pio_mode: (RO) PIO transfer mode used by the device. + Mostly used by PATA devices. + + xfer_mode: (RO) Current transfer mode. Mostly used by + PATA devices. + + dma_mode: (RO) DMA transfer mode used by the device. + Mostly used by PATA devices. + + class: (RO) Device class. Can be "ata" for disk, + "atapi" for packet device, "pmp" for PM, or + "none" if no device was found behind the link. + + +What: /sys/class/ata_device/devX[.Y].Z/trim +Date: May, 2015 +KernelVersion: v4.10 +Contact: Gwendal Grignou +Description: + (RO) Shows the DSM TRIM mode currently used by the device. Valid + values are: + + unsupported: Drive does not support DSM TRIM + + unqueued: Drive supports unqueued DSM TRIM only + + queued: Drive supports queued DSM TRIM + + forced_unqueued: Drive's queued DSM support is known to + be buggy and only unqueued TRIM commands + are sent diff --git a/Documentation/ABI/testing/sysfs-block-aoe b/Documentation/ABI/testing/sysfs-block-aoe new file mode 100644 index 000000000..b5837765b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-aoe @@ -0,0 +1,45 @@ +What: /sys/block/etherd*/mac +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: Ed L. Cashin +Description: + (RO) The ethernet address of the remote Ata over Ethernet (AoE) + device. + +What: /sys/block/etherd*/netif +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: Ed L. Cashin +Description: + (RO) The names of the network interfaces on the localhost (comma + separated) through which we are communicating with the remote + AoE device. + +What: /sys/block/etherd*/state +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: Ed L. Cashin +Description: + (RO) Device status. The state attribute is "up" when the device + is ready for I/O and "down" if detected but unusable. The + "down,closewait" state shows that the device is still open and + cannot come up again until it has been closed. The "up,kickme" + state means that the driver wants to send more commands to the + target but found out there were already the max number of + commands waiting for a response. It will retry again after being + kicked by the periodic timer handler routine. + +What: /sys/block/etherd*/firmware-version +Date: Apr, 2005 +KernelVersion: v2.6.12 +Contact: Ed L. Cashin +Description: + (RO) Version of the firmware in the target. + +What: /sys/block/etherd*/payload +Date: Dec, 2012 +KernelVersion: v3.10 +Contact: Ed L. Cashin +Description: + (RO) The amount of user data transferred (in bytes) inside each AoE + command on the network, network headers excluded. diff --git a/Documentation/ABI/testing/sysfs-block-bcache b/Documentation/ABI/testing/sysfs-block-bcache new file mode 100644 index 000000000..9e4bbc5d5 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-bcache @@ -0,0 +1,156 @@ +What: /sys/block//bcache/unregister +Date: November 2010 +Contact: Kent Overstreet +Description: + A write to this file causes the backing device or cache to be + unregistered. If a backing device had dirty data in the cache, + writeback mode is automatically disabled and all dirty data is + flushed before the device is unregistered. Caches unregister + all associated backing devices before unregistering themselves. + +What: /sys/block//bcache/clear_stats +Date: November 2010 +Contact: Kent Overstreet +Description: + Writing to this file resets all the statistics for the device. + +What: /sys/block//bcache/cache +Date: November 2010 +Contact: Kent Overstreet +Description: + For a backing device that has cache, a symlink to + the bcache/ dir of that cache. + +What: /sys/block//bcache/cache_hits +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: integer number of full cache hits, + counted per bio. A partial cache hit counts as a miss. + +What: /sys/block//bcache/cache_misses +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: integer number of cache misses. + +What: /sys/block//bcache/cache_hit_ratio +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: cache hits as a percentage. + +What: /sys/block//bcache/sequential_cutoff +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: Threshold past which sequential IO will + skip the cache. Read and written as bytes in human readable + units (i.e. echo 10M > sequntial_cutoff). + +What: /sys/block//bcache/bypassed +Date: November 2010 +Contact: Kent Overstreet +Description: + Sum of all reads and writes that have bypassed the cache (due + to the sequential cutoff). Expressed as bytes in human + readable units. + +What: /sys/block//bcache/writeback +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: When on, writeback caching is enabled and + writes will be buffered in the cache. When off, caching is in + writethrough mode; reads and writes will be added to the + cache but no write buffering will take place. + +What: /sys/block//bcache/writeback_running +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: when off, dirty data will not be written + from the cache to the backing device. The cache will still be + used to buffer writes until it is mostly full, at which point + writes transparently revert to writethrough mode. Intended only + for benchmarking/testing. + +What: /sys/block//bcache/writeback_delay +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: In writeback mode, when dirty data is + written to the cache and the cache held no dirty data for that + backing device, writeback from cache to backing device starts + after this delay, expressed as an integer number of seconds. + +What: /sys/block//bcache/writeback_percent +Date: November 2010 +Contact: Kent Overstreet +Description: + For backing devices: If nonzero, writeback from cache to + backing device only takes place when more than this percentage + of the cache is used, allowing more write coalescing to take + place and reducing total number of writes sent to the backing + device. Integer between 0 and 40. + +What: /sys/block//bcache/synchronous +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, a boolean that allows synchronous mode to be + switched on and off. In synchronous mode all writes are ordered + such that the cache can reliably recover from unclean shutdown; + if disabled bcache will not generally wait for writes to + complete but if the cache is not shut down cleanly all data + will be discarded from the cache. Should not be turned off with + writeback caching enabled. + +What: /sys/block//bcache/discard +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, a boolean allowing discard/TRIM to be turned off + or back on if the device supports it. + +What: /sys/block//bcache/bucket_size +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, bucket size in human readable units, as set at + cache creation time; should match the erase block size of the + SSD for optimal performance. + +What: /sys/block//bcache/nbuckets +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, the number of usable buckets. + +What: /sys/block//bcache/tree_depth +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, height of the btree excluding leaf nodes (i.e. a + one node tree will have a depth of 0). + +What: /sys/block//bcache/btree_cache_size +Date: November 2010 +Contact: Kent Overstreet +Description: + Number of btree buckets/nodes that are currently cached in + memory; cache dynamically grows and shrinks in response to + memory pressure from the rest of the system. + +What: /sys/block//bcache/written +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, total amount of data in human readable units + written to the cache, excluding all metadata. + +What: /sys/block//bcache/btree_written +Date: November 2010 +Contact: Kent Overstreet +Description: + For a cache, sum of all btree writes in human readable units. diff --git a/Documentation/ABI/testing/sysfs-block-device b/Documentation/ABI/testing/sysfs-block-device new file mode 100644 index 000000000..7ac7b19b2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-device @@ -0,0 +1,97 @@ +What: /sys/block/*/device/sw_activity +Date: Jun, 2008 +KernelVersion: v2.6.27 +Contact: linux-ide@vger.kernel.org +Description: + (RW) Used by drivers which support software controlled activity + LEDs. + + It has the following valid values: + + == ======================================================== + 0 OFF - the LED is not activated on activity + 1 BLINK_ON - the LED blinks on every 10ms when activity is + detected. + 2 BLINK_OFF - the LED is on when idle, and blinks off + every 10ms when activity is detected. + == ======================================================== + + Note that the user must turn sw_activity OFF it they wish to + control the activity LED via the em_message file. + + +What: /sys/block/*/device/unload_heads +Date: Sep, 2008 +KernelVersion: v2.6.28 +Contact: linux-ide@vger.kernel.org +Description: + (RW) Hard disk shock protection + + Writing an integer value to this file will take the heads of the + respective drive off the platter and block all I/O operations + for the specified number of milliseconds. + + - If the device does not support the unload heads feature, + access is denied with -EOPNOTSUPP. + - The maximal value accepted for a timeout is 30000 + milliseconds. + - A previously set timeout can be cancelled and disk can resume + normal operation immediately by specifying a timeout of 0. + - Some hard drives only comply with an earlier version of the + ATA standard, but support the unload feature nonetheless. + There is no safe way Linux can detect these devices, so this + is not enabled by default. If it is known that your device + does support the unload feature, then you can tell the kernel + to enable it by writing -1. It can be disabled again by + writing -2. + - Values below -2 are rejected with -EINVAL + + For more information, see + Documentation/admin-guide/laptops/disk-shock-protection.rst + + +What: /sys/block/*/device/ncq_prio_enable +Date: Oct, 2016 +KernelVersion: v4.10 +Contact: linux-ide@vger.kernel.org +Description: + (RW) Write to the file to turn on or off the SATA NCQ (native + command queueing) priority support. By default this feature is + turned off. If the device does not support the SATA NCQ + priority feature, writing "1" to this file results in an error + (see ncq_prio_supported). + + +What: /sys/block/*/device/sas_ncq_prio_enable +Date: Oct, 2016 +KernelVersion: v4.10 +Contact: linux-ide@vger.kernel.org +Description: + (RW) This is the equivalent of the ncq_prio_enable attribute + file for SATA devices connected to a SAS host-bus-adapter + (HBA) implementing support for the SATA NCQ priority feature. + This file does not exist if the HBA driver does not implement + support for the SATA NCQ priority feature, regardless of the + device support for this feature (see sas_ncq_prio_supported). + + +What: /sys/block/*/device/ncq_prio_supported +Date: Aug, 2021 +KernelVersion: v5.15 +Contact: linux-ide@vger.kernel.org +Description: + (RO) Indicates if the device supports the SATA NCQ (native + command queueing) priority feature. + + +What: /sys/block/*/device/sas_ncq_prio_supported +Date: Aug, 2021 +KernelVersion: v5.15 +Contact: linux-ide@vger.kernel.org +Description: + (RO) This is the equivalent of the ncq_prio_supported attribute + file for SATA devices connected to a SAS host-bus-adapter + (HBA) implementing support for the SATA NCQ priority feature. + This file does not exist if the HBA driver does not implement + support for the SATA NCQ priority feature, regardless of the + device support for this feature. diff --git a/Documentation/ABI/testing/sysfs-block-dm b/Documentation/ABI/testing/sysfs-block-dm new file mode 100644 index 000000000..f9f2339b9 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-dm @@ -0,0 +1,47 @@ +What: /sys/block/dm-/dm/name +Date: January 2009 +KernelVersion: 2.6.29 +Contact: dm-devel@redhat.com +Description: Device-mapper device name. + Read-only string containing mapped device name. +Users: util-linux, device-mapper udev rules + +What: /sys/block/dm-/dm/uuid +Date: January 2009 +KernelVersion: 2.6.29 +Contact: dm-devel@redhat.com +Description: Device-mapper device UUID. + Read-only string containing DM-UUID or empty string + if DM-UUID is not set. +Users: util-linux, device-mapper udev rules + +What: /sys/block/dm-/dm/suspended +Date: June 2009 +KernelVersion: 2.6.31 +Contact: dm-devel@redhat.com +Description: Device-mapper device suspend state. + Contains the value 1 while the device is suspended. + Otherwise it contains 0. Read-only attribute. +Users: util-linux, device-mapper udev rules + +What: /sys/block/dm-/dm/rq_based_seq_io_merge_deadline +Date: March 2015 +KernelVersion: 4.1 +Contact: dm-devel@redhat.com +Description: Allow control over how long a request that is a + reasonable merge candidate can be queued on the request + queue. The resolution of this deadline is in + microseconds (ranging from 1 to 100000 usecs). + Setting this attribute to 0 (the default) will disable + request-based DM's merge heuristic and associated extra + accounting. This attribute is not applicable to + bio-based DM devices so it will only ever report 0 for + them. + +What: /sys/block/dm-/dm/use_blk_mq +Date: March 2015 +KernelVersion: 4.1 +Contact: dm-devel@redhat.com +Description: Request-based Device-mapper blk-mq I/O path mode. + Contains the value 1 if the device is using blk-mq. + Otherwise it contains 0. Read-only attribute. diff --git a/Documentation/ABI/testing/sysfs-block-loop b/Documentation/ABI/testing/sysfs-block-loop new file mode 100644 index 000000000..627f4eb87 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-loop @@ -0,0 +1,50 @@ +What: /sys/block/loopX/loop/autoclear +Date: Aug, 2010 +KernelVersion: v2.6.37 +Contact: linux-block@vger.kernel.org +Description: + (RO) Shows if the device is in autoclear mode or not ( "1" or + "0"). Autoclear (if set) indicates that the loopback device will + self-distruct after last close. + +What: /sys/block/loopX/loop/backing_file +Date: Aug, 2010 +KernelVersion: v2.6.37 +Contact: linux-block@vger.kernel.org +Description: + (RO) The path of the backing file that the loop device maps its + data blocks to. + +What: /sys/block/loopX/loop/offset +Date: Aug, 2010 +KernelVersion: v2.6.37 +Contact: linux-block@vger.kernel.org +Description: + (RO) Start offset (in bytes). + +What: /sys/block/loopX/loop/sizelimit +Date: Aug, 2010 +KernelVersion: v2.6.37 +Contact: linux-block@vger.kernel.org +Description: + (RO) The size (in bytes) that the block device maps, starting + from the offset. + +What: /sys/block/loopX/loop/partscan +Date: Aug, 2011 +KernelVersion: v3.10 +Contact: linux-block@vger.kernel.org +Description: + (RO) Shows if automatic partition scanning is enabled for the + device or not ("1" or "0"). This can be requested individually + per loop device during its setup by setting LO_FLAGS_PARTSCAN in + in the ioctl request. By default, no partition tables are + scanned. + +What: /sys/block/loopX/loop/dio +Date: Aug, 2015 +KernelVersion: v4.10 +Contact: linux-block@vger.kernel.org +Description: + (RO) Shows if direct IO is being used to access backing file or + not ("1 or "0"). diff --git a/Documentation/ABI/testing/sysfs-block-rnbd b/Documentation/ABI/testing/sysfs-block-rnbd new file mode 100644 index 000000000..80b420b5d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-rnbd @@ -0,0 +1,64 @@ +What: /sys/block/rnbd/rnbd/unmap_device +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: To unmap a volume, "normal" or "force" has to be written to: + /sys/block/rnbd/rnbd/unmap_device + + When "normal" is used, the operation will fail with EBUSY if any process + is using the device. When "force" is used, the device is also unmapped + when device is in use. All I/Os that are in progress will fail. + + Example:: + + # echo "normal" > /sys/block/rnbd0/rnbd/unmap_device + +What: /sys/block/rnbd/rnbd/state +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: The file contains the current state of the block device. The state file + returns "open" when the device is successfully mapped from the server + and accepting I/O requests. When the connection to the server gets + disconnected in case of an error (e.g. link failure), the state file + returns "closed" and all I/O requests submitted to it will fail with -EIO. + +What: /sys/block/rnbd/rnbd/session +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RNBD uses RTRS session to transport the data between client and + server. The entry "session" contains the name of the session, that + was used to establish the RTRS session. It's the same name that + was passed as server parameter to the map_device entry. + +What: /sys/block/rnbd/rnbd/mapping_path +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains the path that was passed as "device_path" to the map_device + operation. + +What: /sys/block/rnbd/rnbd/access_mode +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains the device access mode: ro, rw or migration. + +What: /sys/block/rnbd/rnbd/resize +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Write the number of sectors to change the size of the disk. + +What: /sys/block/rnbd/rnbd/remap_device +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Remap the disconnected device if the session is not destroyed yet. + +What: /sys/block/rnbd/rnbd/nr_poll_queues +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains the number of poll-mode queues diff --git a/Documentation/ABI/testing/sysfs-block-rssd b/Documentation/ABI/testing/sysfs-block-rssd new file mode 100644 index 000000000..beef30c04 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-rssd @@ -0,0 +1,5 @@ +What: /sys/block/rssd*/status +Date: April 2012 +KernelVersion: 3.4 +Contact: Asai Thambi S P +Description: This is a read-only file. Indicates the status of the device. diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram new file mode 100644 index 000000000..14b2bf2e5 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-block-zram @@ -0,0 +1,139 @@ +What: /sys/block/zram/disksize +Date: August 2010 +Contact: Nitin Gupta +Description: + The disksize file is read-write and specifies the disk size + which represents the limit on the *uncompressed* worth of data + that can be stored in this disk. + Unit: bytes + +What: /sys/block/zram/initstate +Date: August 2010 +Contact: Nitin Gupta +Description: + The initstate file is read-only and shows the initialization + state of the device. + +What: /sys/block/zram/reset +Date: August 2010 +Contact: Nitin Gupta +Description: + The reset file is write-only and allows resetting the + device. The reset operation frees all the memory associated + with this device. + +What: /sys/block/zram/max_comp_streams +Date: February 2014 +Contact: Sergey Senozhatsky +Description: + The max_comp_streams file is read-write and specifies the + number of backend's zcomp_strm compression streams (number of + concurrent compress operations). + +What: /sys/block/zram/comp_algorithm +Date: February 2014 +Contact: Sergey Senozhatsky +Description: + The comp_algorithm file is read-write and lets to show + available and selected compression algorithms, change + compression algorithm selection. + +What: /sys/block/zram/mem_used_max +Date: August 2014 +Contact: Minchan Kim +Description: + The mem_used_max file is write-only and is used to reset + the counter of maximum memory zram have consumed to store + compressed data. For resetting the value, you should write + "0". Otherwise, you could see -EINVAL. + Unit: bytes + +What: /sys/block/zram/mem_limit +Date: August 2014 +Contact: Minchan Kim +Description: + The mem_limit file is write-only and specifies the maximum + amount of memory ZRAM can use to store the compressed data. + The limit could be changed in run time and "0" means disable + the limit. No limit is the initial state. Unit: bytes + +What: /sys/block/zram/compact +Date: August 2015 +Contact: Minchan Kim +Description: + The compact file is write-only and trigger compaction for + allocator zrm uses. The allocator moves some objects so that + it could free fragment space. + +What: /sys/block/zram/io_stat +Date: August 2015 +Contact: Sergey Senozhatsky +Description: + The io_stat file is read-only and accumulates device's I/O + statistics not accounted by block layer. For example, + failed_reads, failed_writes, etc. File format is similar to + block layer statistics file format. + +What: /sys/block/zram/mm_stat +Date: August 2015 +Contact: Sergey Senozhatsky +Description: + The mm_stat file is read-only and represents device's mm + statistics (orig_data_size, compr_data_size, etc.) in a format + similar to block layer statistics file format. + +What: /sys/block/zram/debug_stat +Date: July 2016 +Contact: Sergey Senozhatsky +Description: + The debug_stat file is read-only and represents various + device's debugging info useful for kernel developers. Its + format is not documented intentionally and may change + anytime without any notice. + +What: /sys/block/zram/backing_dev +Date: June 2017 +Contact: Minchan Kim +Description: + The backing_dev file is read-write and set up backing + device for zram to write incompressible pages. + For using, user should enable CONFIG_ZRAM_WRITEBACK. + +What: /sys/block/zram/idle +Date: November 2018 +Contact: Minchan Kim +Description: + idle file is write-only and mark zram slot as idle. + If system has mounted debugfs, user can see which slots + are idle via /sys/kernel/debug/zram/zram/block_state + +What: /sys/block/zram/writeback +Date: November 2018 +Contact: Minchan Kim +Description: + The writeback file is write-only and trigger idle and/or + huge page writeback to backing device. + +What: /sys/block/zram/bd_stat +Date: November 2018 +Contact: Minchan Kim +Description: + The bd_stat file is read-only and represents backing device's + statistics (bd_count, bd_reads, bd_writes) in a format + similar to block layer statistics file format. + +What: /sys/block/zram/writeback_limit_enable +Date: November 2018 +Contact: Minchan Kim +Description: + The writeback_limit_enable file is read-write and specifies + eanbe of writeback_limit feature. "1" means eable the feature. + No limit "0" is the initial state. + +What: /sys/block/zram/writeback_limit +Date: November 2018 +Contact: Minchan Kim +Description: + The writeback_limit file is read-write and specifies the maximum + amount of writeback ZRAM can do. The limit could be changed + in run time. diff --git a/Documentation/ABI/testing/sysfs-bus-acpi b/Documentation/ABI/testing/sysfs-bus-acpi new file mode 100644 index 000000000..58abacf59 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-acpi @@ -0,0 +1,98 @@ +What: /sys/bus/acpi/devices/.../path +Date: December 2006 +Contact: Rafael J. Wysocki +Description: + This attribute indicates the full path of ACPI namespace + object associated with the device object. For example, + \_SB_.PCI0. + + This file is not present for device objects representing + fixed ACPI hardware features (like power and sleep + buttons). + +What: /sys/bus/acpi/devices/.../modalias +Date: July 2007 +Contact: Rafael J. Wysocki +Description: + This attribute indicates the PNP IDs of the device object. + That is acpi:HHHHHHHH:[CCCCCCC:]. Where each HHHHHHHH or + CCCCCCCC contains device object's PNPID (_HID or _CID). + +What: /sys/bus/acpi/devices/.../hid +Date: April 2005 +Contact: Rafael J. Wysocki +Description: + This attribute indicates the hardware ID (_HID) of the + device object. For example, PNP0103. + This file is present for device objects having the _HID + control method. + +What: /sys/bus/acpi/devices/.../description +Date: October 2012 +Contact: Rafael J. Wysocki +Description: + This attribute contains the output of the device object's + _STR control method, if present. + +What: /sys/bus/acpi/devices/.../adr +Date: October 2012 +Contact: Rafael J. Wysocki +Description: + This attribute contains the output of the device object's + _ADR control method, which is present for ACPI device + objects representing devices having standard enumeration + algorithms, such as PCI. + +What: /sys/bus/acpi/devices/.../uid +Date: October 2012 +Contact: Rafael J. Wysocki +Description: + This attribute contains the output of the device object's + _UID control method, if present. + +What: /sys/bus/acpi/devices/.../eject +Date: December 2006 +Contact: Rafael J. Wysocki +Description: + Writing 1 to this attribute will trigger hot removal of + this device object. This file exists for every device + object that has _EJ0 method. + +What: /sys/bus/acpi/devices/.../status +Date: Jan, 2014 +Contact: Rafael J. Wysocki +Description: + (RO) Returns the ACPI device status: enabled, disabled or + functioning or present, if the method _STA is present. + + The return value is a decimal integer representing the device's + status bitmap: + + =========== ================================================== + Bit [0] Set if the device is present. + Bit [1] Set if the device is enabled and decoding its + resources. + Bit [2] Set if the device should be shown in the UI. + Bit [3] Set if the device is functioning properly (cleared + if device failed its diagnostics). + Bit [4] Set if the battery is present. + Bits [31:5] Reserved (must be cleared) + =========== ================================================== + + If bit [0] is clear, then bit 1 must also be clear (a device + that is not present cannot be enabled). + + Bit 0 can be clear (not present) with bit [3] set (device is + functional). This case is used to indicate a valid device for + which no device driver should be loaded. + + More special cases are covered in the ACPI specification. + +What: /sys/bus/acpi/devices/.../hrv +Date: Apr, 2016 +Contact: Rafael J. Wysocki +Description: + (RO) Allows users to read the hardware version of non-PCI + hardware, if the _HRV control method is present. It is mostly + useful for non-PCI devices because lspci can list the hardware + version for PCI devices. diff --git a/Documentation/ABI/testing/sysfs-bus-amba b/Documentation/ABI/testing/sysfs-bus-amba new file mode 100644 index 000000000..e7b54677c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-amba @@ -0,0 +1,20 @@ +What: /sys/bus/amba/devices/.../driver_override +Date: September 2014 +Contact: Antonios Motakis +Description: + This file allows the driver for a device to be specified which + will override standard OF, ACPI, ID table, and name matching. + When specified, only a driver with a name matching the value + written to driver_override will have an opportunity to bind to + the device. The override is specified by writing a string to the + driver_override file (echo vfio-amba > driver_override) and may + be cleared with an empty string (echo > driver_override). + This returns the device to standard matching rules binding. + Writing to driver_override does not automatically unbind the + device from its current driver or make any attempt to + automatically load the specified driver. If no driver with a + matching name is currently loaded in the kernel, the device will + not bind to any driver. This also allows devices to opt-out of + driver binding using a driver_override name such as "none". + Only a single driver may be specified in the override, there is + no support for parsing delimiters. diff --git a/Documentation/ABI/testing/sysfs-bus-bcma b/Documentation/ABI/testing/sysfs-bus-bcma new file mode 100644 index 000000000..e93d3ddca --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-bcma @@ -0,0 +1,31 @@ +What: /sys/bus/bcma/devices/.../manuf +Date: May 2011 +KernelVersion: 3.0 +Contact: Rafał Miłecki +Description: + Each BCMA core has its manufacturer id. See + include/linux/bcma/bcma.h for possible values. + +What: /sys/bus/bcma/devices/.../id +Date: May 2011 +KernelVersion: 3.0 +Contact: Rafał Miłecki +Description: + There are a few types of BCMA cores, they can be identified by + id field. + +What: /sys/bus/bcma/devices/.../rev +Date: May 2011 +KernelVersion: 3.0 +Contact: Rafał Miłecki +Description: + BCMA cores of the same type can still slightly differ depending + on their revision. Use it for detailed programming. + +What: /sys/bus/bcma/devices/.../class +Date: May 2011 +KernelVersion: 3.0 +Contact: Rafał Miłecki +Description: + Each BCMA core is identified by few fields, including class it + belongs to. See include/linux/bcma/bcma.h for possible values. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-cti b/Documentation/ABI/testing/sysfs-bus-coresight-devices-cti new file mode 100644 index 000000000..bf2869c41 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-cti @@ -0,0 +1,241 @@ +What: /sys/bus/coresight/devices//enable +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Enable/Disable the CTI hardware. + +What: /sys/bus/coresight/devices//powered +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Indicate if the CTI hardware is powered. + +What: /sys/bus/coresight/devices//ctmid +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Display the associated CTM ID + +What: /sys/bus/coresight/devices//nr_trigger_cons +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Number of devices connected to triggers on this CTI + +What: /sys/bus/coresight/devices//triggers/name +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Name of connected device + +What: /sys/bus/coresight/devices//triggers/in_signals +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Input trigger signals from connected device + +What: /sys/bus/coresight/devices//triggers/in_types +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Functional types for the input trigger signals + from connected device + +What: /sys/bus/coresight/devices//triggers/out_signals +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Output trigger signals to connected device + +What: /sys/bus/coresight/devices//triggers/out_types +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Functional types for the output trigger signals + to connected device + +What: /sys/bus/coresight/devices//regs/inout_sel +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Select the index for inen and outen registers. + +What: /sys/bus/coresight/devices//regs/inen +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Read or write the CTIINEN register selected by inout_sel. + +What: /sys/bus/coresight/devices//regs/outen +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Read or write the CTIOUTEN register selected by inout_sel. + +What: /sys/bus/coresight/devices//regs/gate +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Read or write CTIGATE register. + +What: /sys/bus/coresight/devices//regs/asicctl +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Read or write ASICCTL register. + +What: /sys/bus/coresight/devices//regs/intack +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Write the INTACK register. + +What: /sys/bus/coresight/devices//regs/appset +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Set CTIAPPSET register to activate channel. Read back to + determine current value of register. + +What: /sys/bus/coresight/devices//regs/appclear +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Write APPCLEAR register to deactivate channel. + +What: /sys/bus/coresight/devices//regs/apppulse +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Write APPPULSE to pulse a channel active for one clock + cycle. + +What: /sys/bus/coresight/devices//regs/chinstatus +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Read current status of channel inputs. + +What: /sys/bus/coresight/devices//regs/choutstatus +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) read current status of channel outputs. + +What: /sys/bus/coresight/devices//regs/triginstatus +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) read current status of input trigger signals + +What: /sys/bus/coresight/devices//regs/trigoutstatus +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) read current status of output trigger signals. + +What: /sys/bus/coresight/devices//channels/trigin_attach +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Attach a CTI input trigger to a CTM channel. + +What: /sys/bus/coresight/devices//channels/trigin_detach +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Detach a CTI input trigger from a CTM channel. + +What: /sys/bus/coresight/devices//channels/trigout_attach +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Attach a CTI output trigger to a CTM channel. + +What: /sys/bus/coresight/devices//channels/trigout_detach +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Detach a CTI output trigger from a CTM channel. + +What: /sys/bus/coresight/devices//channels/chan_gate_enable +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Enable CTIGATE for single channel (Write) or list enabled + channels through the gate (R). + +What: /sys/bus/coresight/devices//channels/chan_gate_disable +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Disable CTIGATE for single channel. + +What: /sys/bus/coresight/devices//channels/chan_set +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Activate a single channel. + +What: /sys/bus/coresight/devices//channels/chan_clear +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Deactivate a single channel. + +What: /sys/bus/coresight/devices//channels/chan_pulse +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Pulse a single channel - activate for a single clock cycle. + +What: /sys/bus/coresight/devices//channels/trigout_filtered +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) List of output triggers filtered across all connections. + +What: /sys/bus/coresight/devices//channels/trig_filter_enable +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Enable or disable trigger output signal filtering. + +What: /sys/bus/coresight/devices//channels/chan_inuse +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) show channels with at least one attached trigger signal. + +What: /sys/bus/coresight/devices//channels/chan_free +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) show channels with no attached trigger signals. + +What: /sys/bus/coresight/devices//channels/chan_xtrigs_sel +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (RW) Write channel number to select a channel to view, read to + see selected channel number. + +What: /sys/bus/coresight/devices//channels/chan_xtrigs_in +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Read to see input triggers connected to selected view + channel. + +What: /sys/bus/coresight/devices//channels/chan_xtrigs_out +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Read) Read to see output triggers connected to selected view + channel. + +What: /sys/bus/coresight/devices//channels/chan_xtrigs_reset +Date: March 2020 +KernelVersion 5.7 +Contact: Mike Leach or Mathieu Poirier +Description: (Write) Clear all channel / trigger programming. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10 b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10 new file mode 100644 index 000000000..9a383f6a7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10 @@ -0,0 +1,82 @@ +What: /sys/bus/coresight/devices/.etb/enable_sink +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Add/remove a sink from a trace path. There can be multiple + source for a single sink. + + ex:: + + echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink + +What: /sys/bus/coresight/devices/.etb/trigger_cntr +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Disables write access to the Trace RAM by stopping the + formatter after a defined number of words have been stored + following the trigger event. The number of 32-bit words written + into the Trace RAM following the trigger event is equal to the + value stored in this register+1 (from ARM ETB-TRM). + +What: /sys/bus/coresight/devices/.etb/mgmt/rdp +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Defines the depth, in words, of the trace RAM in powers of + 2. The value is read directly from HW register RDP, 0x004. + +What: /sys/bus/coresight/devices/.etb/mgmt/sts +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB status register. The value + is read directly from HW register STS, 0x00C. + +What: /sys/bus/coresight/devices/.etb/mgmt/rrp +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB RAM Read Pointer register + that is used to read entries from the Trace RAM over the APB + interface. The value is read directly from HW register RRP, + 0x014. + +What: /sys/bus/coresight/devices/.etb/mgmt/rwp +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB RAM Write Pointer register + that is used to sets the write pointer to write entries from + the CoreSight bus into the Trace RAM. The value is read directly + from HW register RWP, 0x018. + +What: /sys/bus/coresight/devices/.etb/mgmt/trg +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Similar to "trigger_cntr" above except that this value is + read directly from HW register TRG, 0x01C. + +What: /sys/bus/coresight/devices/.etb/mgmt/ctl +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB Control register. The value + is read directly from HW register CTL, 0x020. + +What: /sys/bus/coresight/devices/.etb/mgmt/ffsr +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB Formatter and Flush Status + register. The value is read directly from HW register FFSR, + 0x300. + +What: /sys/bus/coresight/devices/.etb/mgmt/ffcr +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the ETB Formatter and Flush Control + register. The value is read directly from HW register FFCR, + 0x304. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x new file mode 100644 index 000000000..651602a61 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x @@ -0,0 +1,322 @@ +What: /sys/bus/coresight/devices/.[etm|ptm]/enable_source +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Enable/disable tracing on this specific trace entiry. + Enabling a source implies the source has been configured + properly and a sink has been identidifed for it. The path + of coresight components linking the source to the sink is + configured and managed automatically by the coresight framework. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_idx +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: Select which address comparator or pair (of comparators) to + work with. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_acctype +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with @addr_idx. Specifies + characteristics about the address comparator being configure, + for example the access type, the kind of instruction to trace, + processor contect ID to trigger on, etc. Individual fields in + the access type register may vary on the version of the trace + entity. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_range +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with @addr_idx. Specifies the range of + addresses to trigger on. Inclusion or exclusion is specificed + in the corresponding access type register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_single +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with @addr_idx. Specifies the single + address to trigger on, highly influenced by the configuration + options of the corresponding access type register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_start +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with @addr_idx. Specifies the single + address to start tracing on, highly influenced by the + configuration options of the corresponding access type register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/addr_stop +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with @addr_idx. Specifies the single + address to stop tracing on, highly influenced by the + configuration options of the corresponding access type register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cntr_idx +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Specifies the counter to work on. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cntr_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with cntr_idx, give access to the + counter event register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cntr_val +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with cntr_idx, give access to the + counter value register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cntr_rld_val +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with cntr_idx, give access to the + counter reload value register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cntr_rld_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used in conjunction with cntr_idx, give access to the + counter reload event register. + +What: /sys/bus/coresight/devices/.[etm|ptm]/ctxid_idx +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Specifies the index of the context ID register to be + selected. + +What: /sys/bus/coresight/devices/.[etm|ptm]/ctxid_mask +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Mask to apply to all the context ID comparator. + +What: /sys/bus/coresight/devices/.[etm|ptm]/ctxid_pid +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Used with the ctxid_idx, specify with context ID to trigger + on. + +What: /sys/bus/coresight/devices/.[etm|ptm]/enable_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines which event triggers a trace. + +What: /sys/bus/coresight/devices/.[etm|ptm]/etmsr +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Gives access to the ETM status register, which holds + programming information and status on certains events. + +What: /sys/bus/coresight/devices/.[etm|ptm]/fifofull_level +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Number of byte left in the fifo before considering it full. + Depending on the tracer's version, can also hold threshold for + data suppression. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mode +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Interface with the driver's 'mode' field, controlling + various aspect of the trace entity such as time stamping, + context ID size and cycle accurate tracing. Driver specific + and bound to change depending on the driver. + +What: /sys/bus/coresight/devices/.[etm|ptm]/nr_addr_cmp +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (Read) Provides the number of address comparators pairs accessible + on a trace unit, as specified by bit 3:0 of register ETMCCR. + +What: /sys/bus/coresight/devices/.[etm|ptm]/nr_cntr +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (Read) Provides the number of counters accessible on a trace unit, + as specified by bit 15:13 of register ETMCCR. + +What: /sys/bus/coresight/devices/.[etm|ptm]/nr_ctxid_cmp +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (Read) Provides the number of context ID comparator available on a + trace unit, as specified by bit 25:24 of register ETMCCR. + +What: /sys/bus/coresight/devices/.[etm|ptm]/reset +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (Write) Cancels all configuration on a trace unit and set it back + to its boot configuration. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_12_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 1 to state 2. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_13_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 1 to state 3. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_21_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 2 to state 1. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_23_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 2 to state 3. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_31_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 3 to state 1. + +What: /sys/bus/coresight/devices/.[etm|ptm]/seq_32_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines the event that causes the sequencer to transition + from state 3 to state 2. + +What: /sys/bus/coresight/devices/.[etm|ptm]/curr_seq_state +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (Read) Holds the current state of the sequencer. + +What: /sys/bus/coresight/devices/.[etm|ptm]/sync_freq +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Holds the trace synchronization frequency value - must be + programmed with the various implementation behavior in mind. + +What: /sys/bus/coresight/devices/.[etm|ptm]/timestamp_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines an event that requests the insertion of a timestamp + into the trace stream. + +What: /sys/bus/coresight/devices/.[etm|ptm]/traceid +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Holds the trace ID that will appear in the trace stream + coming from this trace entity. + +What: /sys/bus/coresight/devices/.[etm|ptm]/trigger_event +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Define the event that controls the trigger. + +What: /sys/bus/coresight/devices/.[etm|ptm]/cpu +Date: October 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Holds the cpu number this tracer is affined to. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmccr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Configuration Code register + (0x004). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmccer +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Configuration Code Extension + register (0x1e8). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmscr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM System Configuration + register (0x014). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmidr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM ID register (0x1e4). The + value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmcr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Main Control register (0x000). + The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmtraceidr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Trace ID register (0x200). + The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmteevr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Trace Enable Event register + (0x020). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmtsscr +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Trace Start/Stop Conrol + register (0x018). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmtecr1 +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Enable Conrol #1 + register (0x024). The value is read directly from the HW. + +What: /sys/bus/coresight/devices/.[etm|ptm]/mgmt/etmtecr2 +Date: September 2015 +KernelVersion: 4.4 +Contact: Mathieu Poirier +Description: (RO) Print the content of the ETM Enable Conrol #2 + register (0x01c). The value is read directly from the HW. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x new file mode 100644 index 000000000..08b1964f2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x @@ -0,0 +1,526 @@ +What: /sys/bus/coresight/devices/etm/enable_source +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Enable/disable tracing on this specific trace entiry. + Enabling a source implies the source has been configured + properly and a sink has been identidifed for it. The path + of coresight components linking the source to the sink is + configured and managed automatically by the coresight framework. + +What: /sys/bus/coresight/devices/etm/cpu +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) The CPU this tracing entity is associated with. + +What: /sys/bus/coresight/devices/etm/nr_pe_cmp +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of PE comparator inputs that are + available for tracing. + +What: /sys/bus/coresight/devices/etm/nr_addr_cmp +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of address comparator pairs that are + available for tracing. + +What: /sys/bus/coresight/devices/etm/nr_cntr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of counters that are available for + tracing. + +What: /sys/bus/coresight/devices/etm/nr_ext_inp +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates how many external inputs are implemented. + +What: /sys/bus/coresight/devices/etm/numcidc +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of Context ID comparators that are + available for tracing. + +What: /sys/bus/coresight/devices/etm/numvmidc +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of VMID comparators that are available + for tracing. + +What: /sys/bus/coresight/devices/etm/nrseqstate +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of sequencer states that are + implemented. + +What: /sys/bus/coresight/devices/etm/nr_resource +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of resource selection pairs that are + available for tracing. + +What: /sys/bus/coresight/devices/etm/nr_ss_cmp +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Indicates the number of single-shot comparator controls that + are available for tracing. + +What: /sys/bus/coresight/devices/etm/reset +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Write) Cancels all configuration on a trace unit and set it back + to its boot configuration. + +What: /sys/bus/coresight/devices/etm/mode +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls various modes supported by this ETM, for example + P0 instruction tracing, branch broadcast, cycle counting and + context ID tracing. + +What: /sys/bus/coresight/devices/etm/pe +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls which PE to trace. + +What: /sys/bus/coresight/devices/etm/event +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls the tracing of arbitrary events from bank 0 to 3. + +What: /sys/bus/coresight/devices/etm/event_instren +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls the behavior of the events in bank 0 to 3. + +What: /sys/bus/coresight/devices/etm/event_ts +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls the insertion of global timestamps in the trace + streams. + +What: /sys/bus/coresight/devices/etm/syncfreq +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls how often trace synchronization requests occur. + +What: /sys/bus/coresight/devices/etm/cyc_threshold +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Sets the threshold value for cycle counting. + +What: /sys/bus/coresight/devices/etm/bb_ctrl +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls which regions in the memory map are enabled to + use branch broadcasting. + +What: /sys/bus/coresight/devices/etm/event_vinst +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls instruction trace filtering. + +What: /sys/bus/coresight/devices/etm/s_exlevel_vinst +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) In Secure state, each bit controls whether instruction + tracing is enabled for the corresponding exception level. + +What: /sys/bus/coresight/devices/etm/ns_exlevel_vinst +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) In non-secure state, each bit controls whether instruction + tracing is enabled for the corresponding exception level. + +What: /sys/bus/coresight/devices/etm/addr_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which address comparator or pair (of comparators) to + work with. + +What: /sys/bus/coresight/devices/etm/addr_instdatatype +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls what type of comparison the trace unit performs. + +What: /sys/bus/coresight/devices/etm/addr_single +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Used to setup single address comparator values. + +What: /sys/bus/coresight/devices/etm/addr_range +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Used to setup address range comparator values. + +What: /sys/bus/coresight/devices/etm/seq_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which sequensor. + +What: /sys/bus/coresight/devices/etm/seq_state +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Use this to set, or read, the sequencer state. + +What: /sys/bus/coresight/devices/etm/seq_event +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Moves the sequencer state to a specific state. + +What: /sys/bus/coresight/devices/etm/seq_reset_event +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Moves the sequencer to state 0 when a programmed event + occurs. + +What: /sys/bus/coresight/devices/etm/cntr_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which counter unit to work with. + +What: /sys/bus/coresight/devices/etm/cntrldvr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) This sets or returns the reload count value of the + specific counter. + +What: /sys/bus/coresight/devices/etm/cntr_val +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) This sets or returns the current count value of the + specific counter. + +What: /sys/bus/coresight/devices/etm/cntr_ctrl +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls the operation of the selected counter. + +What: /sys/bus/coresight/devices/etm/res_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which resource selection unit to work with. + +What: /sys/bus/coresight/devices/etm/res_ctrl +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Controls the selection of the resources in the trace unit. + +What: /sys/bus/coresight/devices/etm/ctxid_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which context ID comparator to work with. + +What: /sys/bus/coresight/devices/etm/ctxid_pid +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Get/Set the context ID comparator value to trigger on. + +What: /sys/bus/coresight/devices/etm/ctxid_masks +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Mask for all 8 context ID comparator value + registers (if implemented). + +What: /sys/bus/coresight/devices/etm/vmid_idx +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Select which virtual machine ID comparator to work with. + +What: /sys/bus/coresight/devices/etm/vmid_val +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Get/Set the virtual machine ID comparator value to + trigger on. + +What: /sys/bus/coresight/devices/etm/vmid_masks +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (RW) Mask for all 8 virtual machine ID comparator value + registers (if implemented). + +What: /sys/bus/coresight/devices/etm/addr_exlevel_s_ns +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (RW) Set the Exception Level matching bits for secure and + non-secure exception levels. + +What: /sys/bus/coresight/devices/etm/vinst_pe_cmp_start_stop +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (RW) Access the start stop control register for PE input + comparators. + +What: /sys/bus/coresight/devices/etm/addr_cmp_view +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (Read) Print the current settings for the selected address + comparator. + +What: /sys/bus/coresight/devices/etm/sshot_idx +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (RW) Select the single shot control register to access. + +What: /sys/bus/coresight/devices/etm/sshot_ctrl +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (RW) Access the selected single shot control register. + +What: /sys/bus/coresight/devices/etm/sshot_status +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (Read) Print the current value of the selected single shot + status register. + +What: /sys/bus/coresight/devices/etm/sshot_pe_ctrl +Date: December 2019 +KernelVersion: 5.5 +Contact: Mathieu Poirier +Description: (RW) Access the selected single show PE comparator control + register. + +What: /sys/bus/coresight/devices/etm/mgmt/trcoslsr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the OS Lock Status Register (0x304). + The value it taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpdcr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Power Down Control Register + (0x310). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpdsr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Power Down Status Register + (0x314). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trclsr +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the SW Lock Status Register + (0xFB4). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcauthstatus +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Authentication Status Register + (0xFB8). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcdevid +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Device ID Register + (0xFC8). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcdevarch +Date: January 2021 +KernelVersion: 5.12 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Device Architecture Register + (offset 0xFBC). The value is taken directly read + from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcdevtype +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Device Type Register + (0xFCC). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpidr0 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Peripheral ID0 Register + (0xFE0). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpidr1 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Peripheral ID1 Register + (0xFE4). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpidr2 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Peripheral ID2 Register + (0xFE8). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcpidr3 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Print the content of the Peripheral ID3 Register + (0xFEC). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/mgmt/trcconfig +Date: February 2016 +KernelVersion: 4.07 +Contact: Mathieu Poirier +Description: (Read) Print the content of the trace configuration register + (0x010) as currently set by SW. + +What: /sys/bus/coresight/devices/etm/mgmt/trctraceid +Date: February 2016 +KernelVersion: 4.07 +Contact: Mathieu Poirier +Description: (Read) Print the content of the trace ID register (0x040). + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr0 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the tracing capabilities of the trace unit (0x1E0). + The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr1 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the tracing capabilities of the trace unit (0x1E4). + The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr2 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the maximum size of the data value, data address, + VMID, context ID and instuction address in the trace unit + (0x1E8). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr3 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the value associated with various resources + available to the trace unit. See the Trace Macrocell + architecture specification for more details (0x1E8). + The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr4 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns how many resources the trace unit supports (0x1F0). + The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr5 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns how many resources the trace unit supports (0x1F4). + The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr8 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the maximum speculation depth of the instruction + trace stream. (0x180). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr9 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the number of P0 right-hand keys that the trace unit + can use (0x184). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr10 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the number of P1 right-hand keys that the trace unit + can use (0x188). The value is taken directly from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr11 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the number of special P1 right-hand keys that the + trace unit can use (0x18C). The value is taken directly from + the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr12 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the number of conditional P1 right-hand keys that + the trace unit can use (0x190). The value is taken directly + from the HW. + +What: /sys/bus/coresight/devices/etm/trcidr/trcidr13 +Date: April 2015 +KernelVersion: 4.01 +Contact: Mathieu Poirier +Description: (Read) Returns the number of special conditional P1 right-hand keys + that the trace unit can use (0x194). The value is taken + directly from the HW. + +What: /sys/bus/coresight/devices/etm/ts_source +Date: October 2022 +KernelVersion: 6.1 +Contact: Mathieu Poirier or Suzuki K Poulose +Description: (Read) When FEAT_TRF is implemented, value of TRFCR_ELx.TS used for + trace session. Otherwise -1 indicates an unknown time source. Check + trcidr0.tssize to see if a global timestamp is available. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel b/Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel new file mode 100644 index 000000000..d75acda5e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel @@ -0,0 +1,12 @@ +What: /sys/bus/coresight/devices/.funnel/funnel_ctrl +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Enables the slave ports and defines the hold time of the + slave ports. + +What: /sys/bus/coresight/devices/.funnel/priority +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Defines input port priority order. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm b/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm new file mode 100644 index 000000000..53e1f4815 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm @@ -0,0 +1,53 @@ +What: /sys/bus/coresight/devices/.stm/enable_source +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Enable/disable tracing on this specific trace macrocell. + Enabling the trace macrocell implies it has been configured + properly and a sink has been identified for it. The path + of coresight components linking the source to the sink is + configured and managed automatically by the coresight framework. + +What: /sys/bus/coresight/devices/.stm/hwevent_enable +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Provides access to the HW event enable register, used in + conjunction with HW event bank select register. + +What: /sys/bus/coresight/devices/.stm/hwevent_select +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Gives access to the HW event block select register + (STMHEBSR) in order to configure up to 256 channels. Used in + conjunction with "hwevent_enable" register as described above. + +What: /sys/bus/coresight/devices/.stm/port_enable +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Provides access to the stimulus port enable register + (STMSPER). Used in conjunction with "port_select" described + below. + +What: /sys/bus/coresight/devices/.stm/port_select +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Used to determine which bank of stimulus port bit in + register STMSPER (see above) apply to. + +What: /sys/bus/coresight/devices/.stm/status +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) List various control and status registers. The specific + layout and content is driver specific. + +What: /sys/bus/coresight/devices/.stm/traceid +Date: April 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (RW) Holds the trace ID that will appear in the trace stream + coming from this trace entity. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc new file mode 100644 index 000000000..6aa527296 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc @@ -0,0 +1,93 @@ +What: /sys/bus/coresight/devices/.tmc/trigger_cntr +Date: November 2014 +KernelVersion: 3.19 +Contact: Mathieu Poirier +Description: (RW) Disables write access to the Trace RAM by stopping the + formatter after a defined number of words have been stored + following the trigger event. Additional interface for this + driver are expected to be added as it matures. + +What: /sys/bus/coresight/devices/.tmc/mgmt/rsz +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Defines the size, in 32-bit words, of the local RAM buffer. + The value is read directly from HW register RSZ, 0x004. + +What: /sys/bus/coresight/devices/.tmc/mgmt/sts +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC status register. The value + is read directly from HW register STS, 0x00C. + +What: /sys/bus/coresight/devices/.tmc/mgmt/rrp +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC RAM Read Pointer register + that is used to read entries from the Trace RAM over the APB + interface. The value is read directly from HW register RRP, + 0x014. + +What: /sys/bus/coresight/devices/.tmc/mgmt/rwp +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC RAM Write Pointer register + that is used to sets the write pointer to write entries from + the CoreSight bus into the Trace RAM. The value is read directly + from HW register RWP, 0x018. + +What: /sys/bus/coresight/devices/.tmc/mgmt/trg +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Similar to "trigger_cntr" above except that this value is + read directly from HW register TRG, 0x01C. + +What: /sys/bus/coresight/devices/.tmc/mgmt/ctl +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC Control register. The value + is read directly from HW register CTL, 0x020. + +What: /sys/bus/coresight/devices/.tmc/mgmt/ffsr +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC Formatter and Flush Status + register. The value is read directly from HW register FFSR, + 0x300. + +What: /sys/bus/coresight/devices/.tmc/mgmt/ffcr +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC Formatter and Flush Control + register. The value is read directly from HW register FFCR, + 0x304. + +What: /sys/bus/coresight/devices/.tmc/mgmt/mode +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Shows the value held by the TMC Mode register, which + indicate the mode the device has been configured to enact. The + The value is read directly from the MODE register, 0x028. + +What: /sys/bus/coresight/devices/.tmc/mgmt/devid +Date: March 2016 +KernelVersion: 4.7 +Contact: Mathieu Poirier +Description: (Read) Indicates the capabilities of the Coresight TMC. + The value is read directly from the DEVID register, 0xFC8, + +What: /sys/bus/coresight/devices/.tmc/buffer_size +Date: December 2018 +KernelVersion: 4.19 +Contact: Mathieu Poirier +Description: (RW) Size of the trace buffer for TMC-ETR when used in SYSFS + mode. Writable only for TMC-ETR configurations. The value + should be aligned to the kernel pagesize. diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe b/Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe new file mode 100644 index 000000000..ad3bbc6fa --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-trbe @@ -0,0 +1,14 @@ +What: /sys/bus/coresight/devices/trbe/align +Date: March 2021 +KernelVersion: 5.13 +Contact: Anshuman Khandual +Description: (Read) Shows the TRBE write pointer alignment. This value + is fetched from the TRBIDR register. + +What: /sys/bus/coresight/devices/trbe/flag +Date: March 2021 +KernelVersion: 5.13 +Contact: Anshuman Khandual +Description: (Read) Shows if TRBE updates in the memory are with access + and dirty flag updates as well. This value is fetched from + the TRBIDR register. diff --git a/Documentation/ABI/testing/sysfs-bus-counter b/Documentation/ABI/testing/sysfs-bus-counter new file mode 100644 index 000000000..ff83320b4 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-counter @@ -0,0 +1,382 @@ +What: /sys/bus/counter/devices/counterX/countY/count +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Count data of Count Y represented as a string. + +What: /sys/bus/counter/devices/counterX/countY/capture +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Historical capture of the Count Y count data. + +What: /sys/bus/counter/devices/counterX/countY/ceiling +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Count value ceiling for Count Y. This is the upper limit for the + respective counter. + +What: /sys/bus/counter/devices/counterX/countY/floor +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Count value floor for Count Y. This is the lower limit for the + respective counter. + +What: /sys/bus/counter/devices/counterX/countY/count_mode +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Count mode for channel Y. The ceiling and floor values for + Count Y are used by the count mode where required. The following + count modes are available: + + normal: + Counting is continuous in either direction. + + range limit: + An upper or lower limit is set, mimicking limit switches + in the mechanical counterpart. The upper limit is set to + the Count Y ceiling value, while the lower limit is set + to the Count Y floor value. The counter freezes at + count = ceiling when counting up, and at count = floor + when counting down. At either of these limits, the + counting is resumed only when the count direction is + reversed. + + non-recycle: + The counter is disabled whenever a counter overflow or + underflow takes place. The counter is re-enabled when a + new count value is loaded to the counter via a preset + operation or direct write. + + modulo-n: + A count value boundary is set between the Count Y floor + value and the Count Y ceiling value. The counter is + reset to the Count Y floor value at count = ceiling when + counting up, while the counter is set to the Count Y + ceiling value at count = floor when counting down; the + counter does not freeze at the boundary points, but + counts continuously throughout. + +What: /sys/bus/counter/devices/counterX/countY/count_mode_available +What: /sys/bus/counter/devices/counterX/countY/error_noise_available +What: /sys/bus/counter/devices/counterX/countY/function_available +What: /sys/bus/counter/devices/counterX/countY/prescaler_available +What: /sys/bus/counter/devices/counterX/countY/signalZ_action_available +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Discrete set of available values for the respective Count Y + configuration are listed in this file. Values are delimited by + newline characters. + +What: /sys/bus/counter/devices/counterX/countY/direction +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the count direction of Count + Y. Two count directions are available: forward and backward. + + Some counter devices are able to determine the direction of + their counting. For example, quadrature encoding counters can + determine the direction of movement by evaluating the leading + phase of the respective A and B quadrature encoding signals. + This attribute exposes such count directions. + +What: /sys/bus/counter/devices/counterX/countY/enable +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Whether channel Y counter is enabled. Valid attribute values are + boolean. + + This attribute is intended to serve as a pause/unpause mechanism + for Count Y. Suppose a counter device is used to count the total + movement of a conveyor belt: this attribute allows an operator + to temporarily pause the counter, service the conveyor belt, + and then finally unpause the counter to continue where it had + left off. + +What: /sys/bus/counter/devices/counterX/countY/error_noise +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates whether excessive noise is + present at the channel Y counter inputs. + +What: /sys/bus/counter/devices/counterX/countY/function +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Count function mode of Count Y; count function evaluation is + triggered by conditions specified by the Count Y signalZ_action + attributes. The following count functions are available: + + increase: + Accumulated count is incremented. + + decrease: + Accumulated count is decremented. + + pulse-direction: + Rising edges on signal A updates the respective count. + The input level of signal B determines direction. + + quadrature x1 a: + If direction is forward, rising edges on quadrature pair + signal A updates the respective count; if the direction + is backward, falling edges on quadrature pair signal A + updates the respective count. Quadrature encoding + determines the direction. + + quadrature x1 b: + If direction is forward, rising edges on quadrature pair + signal B updates the respective count; if the direction + is backward, falling edges on quadrature pair signal B + updates the respective count. Quadrature encoding + determines the direction. + + quadrature x2 a: + Any state transition on quadrature pair signal A updates + the respective count. Quadrature encoding determines the + direction. + + quadrature x2 b: + Any state transition on quadrature pair signal B updates + the respective count. Quadrature encoding determines the + direction. + + quadrature x4: + Any state transition on either quadrature pair signals + updates the respective count. Quadrature encoding + determines the direction. + +What: /sys/bus/counter/devices/counterX/countY/name +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the device-specific name of + Count Y. If possible, this should match the name of the + respective channel as it appears in the device datasheet. + +What: /sys/bus/counter/devices/counterX/countY/prescaler +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Configure the prescaler value associated with Count Y. + On the FlexTimer, the counter clock source passes through a + prescaler (i.e. a counter). This acts like a clock + divider. + +What: /sys/bus/counter/devices/counterX/countY/preset +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + If the counter device supports preset registers -- registers + used to load counter channels to a set count upon device-defined + preset operation trigger events -- the preset count for channel + Y is provided by this attribute. + +What: /sys/bus/counter/devices/counterX/countY/preset_enable +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Whether channel Y counter preset operation is enabled. Valid + attribute values are boolean. + +What: /sys/bus/counter/devices/counterX/countY/signalZ_action +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Action mode of Count Y for Signal Z. This attribute indicates + the condition of Signal Z that triggers the count function + evaluation for Count Y. The following action modes are + available: + + none: + Signal does not trigger the count function. In + Pulse-Direction count function mode, this Signal is + evaluated as Direction. + + rising edge: + Low state transitions to high state. + + falling edge: + High state transitions to low state. + + both edges: + Any state transition. + +What: /sys/bus/counter/devices/counterX/countY/num_overflows +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + This attribute indicates the number of overflows of count Y. + +What: /sys/bus/counter/devices/counterX/countY/capture_component_id +What: /sys/bus/counter/devices/counterX/countY/ceiling_component_id +What: /sys/bus/counter/devices/counterX/countY/floor_component_id +What: /sys/bus/counter/devices/counterX/countY/count_mode_component_id +What: /sys/bus/counter/devices/counterX/countY/direction_component_id +What: /sys/bus/counter/devices/counterX/countY/enable_component_id +What: /sys/bus/counter/devices/counterX/countY/error_noise_component_id +What: /sys/bus/counter/devices/counterX/countY/prescaler_component_id +What: /sys/bus/counter/devices/counterX/countY/preset_component_id +What: /sys/bus/counter/devices/counterX/countY/preset_enable_component_id +What: /sys/bus/counter/devices/counterX/countY/signalZ_action_component_id +What: /sys/bus/counter/devices/counterX/countY/num_overflows_component_id +What: /sys/bus/counter/devices/counterX/signalY/cable_fault_component_id +What: /sys/bus/counter/devices/counterX/signalY/cable_fault_enable_component_id +What: /sys/bus/counter/devices/counterX/signalY/filter_clock_prescaler_component_id +What: /sys/bus/counter/devices/counterX/signalY/index_polarity_component_id +What: /sys/bus/counter/devices/counterX/signalY/polarity_component_id +What: /sys/bus/counter/devices/counterX/signalY/synchronous_mode_component_id +What: /sys/bus/counter/devices/counterX/signalY/frequency_component_id +KernelVersion: 5.16 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the component ID of the + respective extension or Synapse. + +What: /sys/bus/counter/devices/counterX/countY/spike_filter_ns +KernelVersion: 5.14 +Contact: linux-iio@vger.kernel.org +Description: + If the counter device supports programmable spike filter this + attribute indicates the value in nanoseconds where noise pulses + shorter or equal to configured value are ignored. Value 0 means + filter is disabled. + +What: /sys/bus/counter/devices/counterX/events_queue_size +KernelVersion: 5.16 +Contact: linux-iio@vger.kernel.org +Description: + Size of the Counter events queue in number of struct + counter_event data structures. The number of elements will be + rounded-up to a power of 2. + +What: /sys/bus/counter/devices/counterX/name +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the device-specific name of + the Counter. This should match the name of the device as it + appears in its respective datasheet. + +What: /sys/bus/counter/devices/counterX/num_counts +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the total number of Counts + belonging to the Counter. + +What: /sys/bus/counter/devices/counterX/num_signals +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the total number of Signals + belonging to the Counter. + +What: /sys/bus/counter/devices/counterX/signalY/cable_fault +KernelVersion: 5.7 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates whether a differential + encoder cable fault (not connected or loose wires) is detected + for the respective channel of Signal Y. Valid attribute values + are boolean. Detection must first be enabled via the + corresponding cable_fault_enable attribute. + +What: /sys/bus/counter/devices/counterX/signalY/cable_fault_enable +KernelVersion: 5.7 +Contact: linux-iio@vger.kernel.org +Description: + Whether detection of differential encoder cable faults for the + respective channel of Signal Y is enabled. Valid attribute + values are boolean. + +What: /sys/bus/counter/devices/counterX/signalY/filter_clock_prescaler +KernelVersion: 5.7 +Contact: linux-iio@vger.kernel.org +Description: + Filter clock factor for input Signal Y. This prescaler value + affects the inputs of both quadrature pair signals. + +What: /sys/bus/counter/devices/counterX/signalY/index_polarity +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Active level of index input Signal Y; irrelevant in + non-synchronous load mode. + +What: /sys/bus/counter/devices/counterX/signalY/index_polarity_available +What: /sys/bus/counter/devices/counterX/signalY/synchronous_mode_available +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Discrete set of available values for the respective Signal Y + configuration are listed in this file. + +What: /sys/bus/counter/devices/counterX/signalY/polarity +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Active level of Signal Y. The following polarity values are + available: + + positive: + Signal high state considered active level (rising edge). + + negative: + Signal low state considered active level (falling edge). + +What: /sys/bus/counter/devices/counterX/signalY/name +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the device-specific name of + Signal Y. If possible, this should match the name of the + respective signal as it appears in the device datasheet. + +What: /sys/bus/counter/devices/counterX/signalY/signal +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Signal level state of Signal Y. The following signal level + states are available: + + low: + Low level state. + + high: + High level state. + +What: /sys/bus/counter/devices/counterX/signalY/synchronous_mode +KernelVersion: 5.2 +Contact: linux-iio@vger.kernel.org +Description: + Configure the counter associated with Signal Y for + non-synchronous or synchronous load mode. Synchronous load mode + cannot be selected in non-quadrature (Pulse-Direction) clock + mode. + + non-synchronous: + A logic low level is the active level at this index + input. The index function (as enabled via preset_enable) + is performed directly on the active level of the index + input. + + synchronous: + Intended for interfacing with encoder Index output in + quadrature clock mode. The active level is configured + via index_polarity. The index function (as enabled via + preset_enable) is performed synchronously with the + quadrature clock on the active level of the index input. + +What: /sys/bus/counter/devices/counterX/signalY/frequency +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Read-only attribute that indicates the signal Y frequency, in Hz. diff --git a/Documentation/ABI/testing/sysfs-bus-css b/Documentation/ABI/testing/sysfs-bus-css new file mode 100644 index 000000000..12a733fe3 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-css @@ -0,0 +1,61 @@ +What: /sys/bus/css/devices/.../type +Date: March 2008 +Contact: Cornelia Huck + linux-s390@vger.kernel.org +Description: Contains the subchannel type, as reported by the hardware. + This attribute is present for all subchannel types. + +What: /sys/bus/css/devices/.../modalias +Date: March 2008 +Contact: Cornelia Huck + linux-s390@vger.kernel.org +Description: Contains the module alias as reported with uevents. + It is of the format css:t and present for all + subchannel types. + +What: /sys/bus/css/drivers/io_subchannel/.../chpids +Date: December 2002 +Contact: Cornelia Huck + linux-s390@vger.kernel.org +Description: Contains the ids of the channel paths used by this + subchannel, as reported by the channel subsystem + during subchannel recognition. + + Note: This is an I/O-subchannel specific attribute. +Users: s390-tools, HAL + +What: /sys/bus/css/drivers/io_subchannel/.../pimpampom +Date: December 2002 +Contact: Cornelia Huck + linux-s390@vger.kernel.org +Description: Contains the PIM/PAM/POM values, as reported by the + channel subsystem when last queried by the common I/O + layer (this implies that this attribute is not necessarily + in sync with the values current in the channel subsystem). + + Note: This is an I/O-subchannel specific attribute. +Users: s390-tools, HAL + +What: /sys/bus/css/devices/.../driver_override +Date: June 2019 +Contact: Cornelia Huck + linux-s390@vger.kernel.org +Description: This file allows the driver for a device to be specified. When + specified, only a driver with a name matching the value written + to driver_override will have an opportunity to bind to the + device. The override is specified by writing a string to the + driver_override file (echo vfio-ccw > driver_override) and + may be cleared with an empty string (echo > driver_override). + This returns the device to standard matching rules binding. + Writing to driver_override does not automatically unbind the + device from its current driver or make any attempt to + automatically load the specified driver. If no driver with a + matching name is currently loaded in the kernel, the device + will not bind to any driver. This also allows devices to + opt-out of driver binding using a driver_override name such as + "none". Only a single driver may be specified in the override, + there is no support for parsing delimiters. + + Note that unlike the mechanism of the same name for pci, this + file does not allow to override basic matching rules. I.e., + the driver must still match the subchannel type of the device. diff --git a/Documentation/ABI/testing/sysfs-bus-cxl b/Documentation/ABI/testing/sysfs-bus-cxl new file mode 100644 index 000000000..8494ef27e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-cxl @@ -0,0 +1,390 @@ +What: /sys/bus/cxl/flush +Date: Januarry, 2022 +KernelVersion: v5.18 +Contact: linux-cxl@vger.kernel.org +Description: + (WO) If userspace manually unbinds a port the kernel schedules + all descendant memdevs for unbind. Writing '1' to this attribute + flushes that work. + + +What: /sys/bus/cxl/devices/memX/firmware_version +Date: December, 2020 +KernelVersion: v5.12 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) "FW Revision" string as reported by the Identify + Memory Device Output Payload in the CXL-2.0 + specification. + + +What: /sys/bus/cxl/devices/memX/ram/size +Date: December, 2020 +KernelVersion: v5.12 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) "Volatile Only Capacity" as bytes. Represents the + identically named field in the Identify Memory Device Output + Payload in the CXL-2.0 specification. + + +What: /sys/bus/cxl/devices/memX/pmem/size +Date: December, 2020 +KernelVersion: v5.12 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) "Persistent Only Capacity" as bytes. Represents the + identically named field in the Identify Memory Device Output + Payload in the CXL-2.0 specification. + + +What: /sys/bus/cxl/devices/memX/serial +Date: January, 2022 +KernelVersion: v5.18 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) 64-bit serial number per the PCIe Device Serial Number + capability. Mandatory for CXL devices, see CXL 2.0 8.1.12.2 + Memory Device PCIe Capabilities and Extended Capabilities. + + +What: /sys/bus/cxl/devices/memX/numa_node +Date: January, 2022 +KernelVersion: v5.18 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) If NUMA is enabled and the platform has affinitized the + host PCI device for this memory device, emit the CPU node + affinity for this device. + + +What: /sys/bus/cxl/devices/*/devtype +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL device objects export the devtype attribute which + mirrors the same value communicated in the DEVTYPE environment + variable for uevents for devices on the "cxl" bus. + + +What: /sys/bus/cxl/devices/*/modalias +Date: December, 2021 +KernelVersion: v5.18 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL device objects export the modalias attribute which + mirrors the same value communicated in the MODALIAS environment + variable for uevents for devices on the "cxl" bus. + + +What: /sys/bus/cxl/devices/portX/uport +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL port objects are enumerated from either a platform + firmware device (ACPI0017 and ACPI0016) or PCIe switch upstream + port with CXL component registers. The 'uport' symlink connects + the CXL portX object to the device that published the CXL port + capability. + + +What: /sys/bus/cxl/devices/portX/dportY +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL port objects are enumerated from either a platform + firmware device (ACPI0017 and ACPI0016) or PCIe switch upstream + port with CXL component registers. The 'dportY' symlink + identifies one or more downstream ports that the upstream port + may target in its decode of CXL memory resources. The 'Y' + integer reflects the hardware port unique-id used in the + hardware decoder target list. + + +What: /sys/bus/cxl/devices/decoderX.Y +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL decoder objects are enumerated from either a platform + firmware description, or a CXL HDM decoder register set in a + PCIe device (see CXL 2.0 section 8.2.5.12 CXL HDM Decoder + Capability Structure). The 'X' in decoderX.Y represents the + cxl_port container of this decoder, and 'Y' represents the + instance id of a given decoder resource. + + +What: /sys/bus/cxl/devices/decoderX.Y/{start,size} +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) The 'start' and 'size' attributes together convey the + physical address base and number of bytes mapped in the + decoder's decode window. For decoders of devtype + "cxl_decoder_root" the address range is fixed. For decoders of + devtype "cxl_decoder_switch" the address is bounded by the + decode range of the cxl_port ancestor of the decoder's cxl_port, + and dynamically updates based on the active memory regions in + that address space. + + +What: /sys/bus/cxl/devices/decoderX.Y/locked +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) CXL HDM decoders have the capability to lock the + configuration until the next device reset. For decoders of + devtype "cxl_decoder_root" there is no standard facility to + unlock them. For decoders of devtype "cxl_decoder_switch" a + secondary bus reset, of the PCIe bridge that provides the bus + for this decoders uport, unlocks / resets the decoder. + + +What: /sys/bus/cxl/devices/decoderX.Y/target_list +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) Display a comma separated list of the current decoder + target configuration. The list is ordered by the current + configured interleave order of the decoder's dport instances. + Each entry in the list is a dport id. + + +What: /sys/bus/cxl/devices/decoderX.Y/cap_{pmem,ram,type2,type3} +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) When a CXL decoder is of devtype "cxl_decoder_root", it + represents a fixed memory window identified by platform + firmware. A fixed window may only support a subset of memory + types. The 'cap_*' attributes indicate whether persistent + memory, volatile memory, accelerator memory, and / or expander + memory may be mapped behind this decoder's memory window. + + +What: /sys/bus/cxl/devices/decoderX.Y/target_type +Date: June, 2021 +KernelVersion: v5.14 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) When a CXL decoder is of devtype "cxl_decoder_switch", it + can optionally decode either accelerator memory (type-2) or + expander memory (type-3). The 'target_type' attribute indicates + the current setting which may dynamically change based on what + memory regions are activated in this decode hierarchy. + + +What: /sys/bus/cxl/devices/endpointX/CDAT +Date: July, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) If this sysfs entry is not present no DOE mailbox was + found to support CDAT data. If it is present and the length of + the data is 0 reading the CDAT data failed. Otherwise the CDAT + data is reported. + + +What: /sys/bus/cxl/devices/decoderX.Y/mode +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) When a CXL decoder is of devtype "cxl_decoder_endpoint" it + translates from a host physical address range, to a device local + address range. Device-local address ranges are further split + into a 'ram' (volatile memory) range and 'pmem' (persistent + memory) range. The 'mode' attribute emits one of 'ram', 'pmem', + 'mixed', or 'none'. The 'mixed' indication is for error cases + when a decoder straddles the volatile/persistent partition + boundary, and 'none' indicates the decoder is not actively + decoding, or no DPA allocation policy has been set. + + 'mode' can be written, when the decoder is in the 'disabled' + state, with either 'ram' or 'pmem' to set the boundaries for the + next allocation. + + +What: /sys/bus/cxl/devices/decoderX.Y/dpa_resource +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) When a CXL decoder is of devtype "cxl_decoder_endpoint", + and its 'dpa_size' attribute is non-zero, this attribute + indicates the device physical address (DPA) base address of the + allocation. + + +What: /sys/bus/cxl/devices/decoderX.Y/dpa_size +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) When a CXL decoder is of devtype "cxl_decoder_endpoint" it + translates from a host physical address range, to a device local + address range. The range, base address plus length in bytes, of + DPA allocated to this decoder is conveyed in these 2 attributes. + Allocations can be mutated as long as the decoder is in the + disabled state. A write to 'dpa_size' releases the previous DPA + allocation and then attempts to allocate from the free capacity + in the device partition referred to by 'decoderX.Y/mode'. + Allocate and free requests can only be performed on the highest + instance number disabled decoder with non-zero size. I.e. + allocations are enforced to occur in increasing 'decoderX.Y/id' + order and frees are enforced to occur in decreasing + 'decoderX.Y/id' order. + + +What: /sys/bus/cxl/devices/decoderX.Y/interleave_ways +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) The number of targets across which this decoder's host + physical address (HPA) memory range is interleaved. The device + maps every Nth block of HPA (of size == + 'interleave_granularity') to consecutive DPA addresses. The + decoder's position in the interleave is determined by the + device's (endpoint or switch) switch ancestry. For root + decoders their interleave is specified by platform firmware and + they only specify a downstream target order for host bridges. + + +What: /sys/bus/cxl/devices/decoderX.Y/interleave_granularity +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) The number of consecutive bytes of host physical address + space this decoder claims at address N before the decode rotates + to the next target in the interleave at address N + + interleave_granularity (assuming N is aligned to + interleave_granularity). + + +What: /sys/bus/cxl/devices/decoderX.Y/create_pmem_region +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Write a string in the form 'regionZ' to start the process + of defining a new persistent memory region (interleave-set) + within the decode range bounded by root decoder 'decoderX.Y'. + The value written must match the current value returned from + reading this attribute. An atomic compare exchange operation is + done on write to assign the requested id to a region and + allocate the region-id for the next creation attempt. EBUSY is + returned if the region name written does not match the current + cached value. + + +What: /sys/bus/cxl/devices/decoderX.Y/delete_region +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (WO) Write a string in the form 'regionZ' to delete that region, + provided it is currently idle / not bound to a driver. + + +What: /sys/bus/cxl/devices/regionZ/uuid +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Write a unique identifier for the region. This field must + be set for persistent regions and it must not conflict with the + UUID of another region. + + +What: /sys/bus/cxl/devices/regionZ/interleave_granularity +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Set the number of consecutive bytes each device in the + interleave set will claim. The possible interleave granularity + values are determined by the CXL spec and the participating + devices. + + +What: /sys/bus/cxl/devices/regionZ/interleave_ways +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Configures the number of devices participating in the + region is set by writing this value. Each device will provide + 1/interleave_ways of storage for the region. + + +What: /sys/bus/cxl/devices/regionZ/size +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) System physical address space to be consumed by the region. + When written trigger the driver to allocate space out of the + parent root decoder's address space. When read the size of the + address space is reported and should match the span of the + region's resource attribute. Size shall be set after the + interleave configuration parameters. Once set it cannot be + changed, only freed by writing 0. The kernel makes no guarantees + that data is maintained over an address space freeing event, and + there is no guarantee that a free followed by an allocate + results in the same address being allocated. + + +What: /sys/bus/cxl/devices/regionZ/resource +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RO) A region is a contiguous partition of a CXL root decoder + address space. Region capacity is allocated by writing to the + size attribute, the resulting physical address space determined + by the driver is reflected here. It is therefore not useful to + read this before writing a value to the size attribute. + + +What: /sys/bus/cxl/devices/regionZ/target[0..N] +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Write an endpoint decoder object name to 'targetX' where X + is the intended position of the endpoint device in the region + interleave and N is the 'interleave_ways' setting for the + region. ENXIO is returned if the write results in an impossible + to map decode scenario, like the endpoint is unreachable at that + position relative to the root decoder interleave. EBUSY is + returned if the position in the region is already occupied, or + if the region is not in a state to accept interleave + configuration changes. EINVAL is returned if the object name is + not an endpoint decoder. Once all positions have been + successfully written a final validation for decode conflicts is + performed before activating the region. + + +What: /sys/bus/cxl/devices/regionZ/commit +Date: May, 2022 +KernelVersion: v5.20 +Contact: linux-cxl@vger.kernel.org +Description: + (RW) Write a boolean 'true' string value to this attribute to + trigger the region to transition from the software programmed + state to the actively decoding in hardware state. The commit + operation in addition to validating that the region is in proper + configured state, validates that the decoders are being + committed in spec mandated order (last committed decoder id + + 1), and checks that the hardware accepts the commit request. + Reading this value indicates whether the region is committed or + not. diff --git a/Documentation/ABI/testing/sysfs-bus-dfl b/Documentation/ABI/testing/sysfs-bus-dfl new file mode 100644 index 000000000..b0265ab17 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-dfl @@ -0,0 +1,17 @@ +What: /sys/bus/dfl/devices/dfl_dev.X/type +Date: Aug 2020 +KernelVersion: 5.10 +Contact: Xu Yilun +Description: Read-only. It returns type of DFL FIU of the device. Now DFL + supports 2 FIU types, 0 for FME, 1 for PORT. + + Format: 0x%x + +What: /sys/bus/dfl/devices/dfl_dev.X/feature_id +Date: Aug 2020 +KernelVersion: 5.10 +Contact: Xu Yilun +Description: Read-only. It returns feature identifier local to its DFL FIU + type. + + Format: 0x%x diff --git a/Documentation/ABI/testing/sysfs-bus-dfl-devices-emif b/Documentation/ABI/testing/sysfs-bus-dfl-devices-emif new file mode 100644 index 000000000..817d14126 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-dfl-devices-emif @@ -0,0 +1,25 @@ +What: /sys/bus/dfl/devices/dfl_dev.X/infX_cal_fail +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. It indicates if the calibration failed on this + memory interface. "1" for calibration failure, "0" for OK. + Format: %u + +What: /sys/bus/dfl/devices/dfl_dev.X/infX_init_done +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. It indicates if the initialization completed on + this memory interface. "1" for initialization complete, "0" + for not yet. + Format: %u + +What: /sys/bus/dfl/devices/dfl_dev.X/infX_clear +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Write-only. Writing "1" to this file will zero out all memory + data in this memory interface. Writing of other values is + invalid. + Format: %u diff --git a/Documentation/ABI/testing/sysfs-bus-dfl-devices-n3000-nios b/Documentation/ABI/testing/sysfs-bus-dfl-devices-n3000-nios new file mode 100644 index 000000000..5335d742b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-dfl-devices-n3000-nios @@ -0,0 +1,47 @@ +What: /sys/bus/dfl/devices/dfl_dev.X/fec_mode +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. Returns the FEC mode of the 25G links of the + ethernet retimers configured by Nios firmware. "rs" for Reed + Solomon FEC, "kr" for Fire Code FEC, "no" for NO FEC. + "not supported" if the FEC mode setting is not supported, this + happens when the Nios firmware version major < 3, or no link is + configured to 25G. + Format: string + +What: /sys/bus/dfl/devices/dfl_dev.X/retimer_A_mode +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. Returns the enumeration value of the working mode of + the retimer A configured by the Nios firmware. The value is + read out from shared registers filled by the Nios firmware. Now + the values could be: + + - "0": Reset + - "1": 4x10G + - "2": 4x25G + - "3": 2x25G + - "4": 2x25G+2x10G + - "5": 1x25G + + If the Nios firmware is updated in future to support more + retimer modes, more enumeration value is expected. + Format: 0x%x + +What: /sys/bus/dfl/devices/dfl_dev.X/retimer_B_mode +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. Returns the enumeration value of the working mode of + the retimer B configured by the Nios firmware. The value format + is the same as retimer_A_mode. + +What: /sys/bus/dfl/devices/dfl_dev.X/nios_fw_version +Date: Oct 2020 +KernelVersion: 5.12 +Contact: Xu Yilun +Description: Read-only. Returns the version of the Nios firmware in the + FPGA. Its format is "major.minor.patch". + Format: %x.%x.%x diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-caps b/Documentation/ABI/testing/sysfs-bus-event_source-devices-caps new file mode 100644 index 000000000..8757dcf41 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-caps @@ -0,0 +1,18 @@ +What: /sys/bus/event_source/devices//caps +Date: May 2022 +KernelVersion: 5.19 +Contact: Linux kernel mailing list +Description: + Attribute group to describe the capabilities exposed + for a particular pmu. Each attribute of this group can + expose information specific to a PMU, say pmu_name, so that + userspace can understand some of the feature which the + platform specific PMU supports. + + One of the example available capability in supported platform + like Intel is pmu_name, which exposes underlying CPU name known + to the PMU driver. + + Example output in powerpc: + grep . /sys/bus/event_source/devices/cpu/caps/* + /sys/bus/event_source/devices/cpu/caps/pmu_name:POWER9 diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme b/Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme new file mode 100644 index 000000000..63a32ddcb --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme @@ -0,0 +1,104 @@ +What: /sys/bus/event_source/devices/dfl_fmeX/format +Date: April 2020 +KernelVersion: 5.8 +Contact: Wu Hao +Description: Read-only. Attribute group to describe the magic bits + that go into perf_event_attr.config for a particular pmu. + (See ABI/testing/sysfs-bus-event_source-devices-format). + + Each attribute under this group defines a bit range of the + perf_event_attr.config. All supported attributes are listed + below:: + + event = "config:0-11" - event ID + evtype = "config:12-15" - event type + portid = "config:16-23" - event source + + For example:: + + fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff" + + It shows this fab_mmio_read is a fabric type (0x02) event with + 0x06 local event id for overall monitoring (portid=0xff). + +What: /sys/bus/event_source/devices/dfl_fmeX/cpumask +Date: April 2020 +KernelVersion: 5.8 +Contact: Wu Hao +Description: Read-only. This file always returns cpu which the PMU is bound + for access to all fme pmu performance monitoring events. + +What: /sys/bus/event_source/devices/dfl_fmeX/events +Date: April 2020 +KernelVersion: 5.8 +Contact: Wu Hao +Description: Read-only. Attribute group to describe performance monitoring + events specific to fme. Each attribute in this group describes + a single performance monitoring event supported by this fme pmu. + The name of the file is the name of the event. + (See ABI/testing/sysfs-bus-event_source-devices-events). + + All supported performance monitoring events are listed below. + + Basic events (evtype=0x00):: + + clock = "event=0x00,evtype=0x00,portid=0xff" + + Cache events (evtype=0x01):: + + cache_read_hit = "event=0x00,evtype=0x01,portid=0xff" + cache_read_miss = "event=0x01,evtype=0x01,portid=0xff" + cache_write_hit = "event=0x02,evtype=0x01,portid=0xff" + cache_write_miss = "event=0x03,evtype=0x01,portid=0xff" + cache_hold_request = "event=0x05,evtype=0x01,portid=0xff" + cache_data_write_port_contention = + "event=0x06,evtype=0x01,portid=0xff" + cache_tag_write_port_contention = + "event=0x07,evtype=0x01,portid=0xff" + cache_tx_req_stall = "event=0x08,evtype=0x01,portid=0xff" + cache_rx_req_stall = "event=0x09,evtype=0x01,portid=0xff" + cache_eviction = "event=0x0a,evtype=0x01,portid=0xff" + + Fabric events (evtype=0x02):: + + fab_pcie0_read = "event=0x00,evtype=0x02,portid=0xff" + fab_pcie0_write = "event=0x01,evtype=0x02,portid=0xff" + fab_pcie1_read = "event=0x02,evtype=0x02,portid=0xff" + fab_pcie1_write = "event=0x03,evtype=0x02,portid=0xff" + fab_upi_read = "event=0x04,evtype=0x02,portid=0xff" + fab_upi_write = "event=0x05,evtype=0x02,portid=0xff" + fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff" + fab_mmio_write = "event=0x07,evtype=0x02,portid=0xff" + fab_port_pcie0_read = "event=0x00,evtype=0x02,portid=?" + fab_port_pcie0_write = "event=0x01,evtype=0x02,portid=?" + fab_port_pcie1_read = "event=0x02,evtype=0x02,portid=?" + fab_port_pcie1_write = "event=0x03,evtype=0x02,portid=?" + fab_port_upi_read = "event=0x04,evtype=0x02,portid=?" + fab_port_upi_write = "event=0x05,evtype=0x02,portid=?" + fab_port_mmio_read = "event=0x06,evtype=0x02,portid=?" + fab_port_mmio_write = "event=0x07,evtype=0x02,portid=?" + + VTD events (evtype=0x03):: + + vtd_port_read_transaction = "event=0x00,evtype=0x03,portid=?" + vtd_port_write_transaction = "event=0x01,evtype=0x03,portid=?" + vtd_port_devtlb_read_hit = "event=0x02,evtype=0x03,portid=?" + vtd_port_devtlb_write_hit = "event=0x03,evtype=0x03,portid=?" + vtd_port_devtlb_4k_fill = "event=0x04,evtype=0x03,portid=?" + vtd_port_devtlb_2m_fill = "event=0x05,evtype=0x03,portid=?" + vtd_port_devtlb_1g_fill = "event=0x06,evtype=0x03,portid=?" + + VTD SIP events (evtype=0x04):: + + vtd_sip_iotlb_4k_hit = "event=0x00,evtype=0x04,portid=0xff" + vtd_sip_iotlb_2m_hit = "event=0x01,evtype=0x04,portid=0xff" + vtd_sip_iotlb_1g_hit = "event=0x02,evtype=0x04,portid=0xff" + vtd_sip_slpwc_l3_hit = "event=0x03,evtype=0x04,portid=0xff" + vtd_sip_slpwc_l4_hit = "event=0x04,evtype=0x04,portid=0xff" + vtd_sip_rcc_hit = "event=0x05,evtype=0x04,portid=0xff" + vtd_sip_iotlb_4k_miss = "event=0x06,evtype=0x04,portid=0xff" + vtd_sip_iotlb_2m_miss = "event=0x07,evtype=0x04,portid=0xff" + vtd_sip_iotlb_1g_miss = "event=0x08,evtype=0x04,portid=0xff" + vtd_sip_slpwc_l3_miss = "event=0x09,evtype=0x04,portid=0xff" + vtd_sip_slpwc_l4_miss = "event=0x0a,evtype=0x04,portid=0xff" + vtd_sip_rcc_miss = "event=0x0b,evtype=0x04,portid=0xff" diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-dsa b/Documentation/ABI/testing/sysfs-bus-event_source-devices-dsa new file mode 100644 index 000000000..3c7d13228 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-dsa @@ -0,0 +1,30 @@ +What: /sys/bus/event_source/devices/dsa*/format +Date: April 2021 +KernelVersion: 5.13 +Contact: Tom Zanussi +Description: Read-only. Attribute group to describe the magic bits + that go into perf_event_attr.config or + perf_event_attr.config1 for the IDXD DSA pmu. (See also + ABI/testing/sysfs-bus-event_source-devices-format). + + Each attribute in this group defines a bit range in + perf_event_attr.config or perf_event_attr.config1. + All supported attributes are listed below (See the + IDXD DSA Spec for possible attribute values):: + + event_category = "config:0-3" - event category + event = "config:4-31" - event ID + + filter_wq = "config1:0-31" - workqueue filter + filter_tc = "config1:32-39" - traffic class filter + filter_pgsz = "config1:40-43" - page size filter + filter_sz = "config1:44-51" - transfer size filter + filter_eng = "config1:52-59" - engine filter + +What: /sys/bus/event_source/devices/dsa*/cpumask +Date: April 2021 +KernelVersion: 5.13 +Contact: Tom Zanussi +Description: Read-only. This file always returns the cpu to which the + IDXD DSA pmu is bound for access to all dsa pmu + performance monitoring events. diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events new file mode 100644 index 000000000..505f080d2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events @@ -0,0 +1,94 @@ +What: /sys/devices/cpu/events/ + /sys/devices/cpu/events/branch-misses + /sys/devices/cpu/events/cache-references + /sys/devices/cpu/events/cache-misses + /sys/devices/cpu/events/stalled-cycles-frontend + /sys/devices/cpu/events/branch-instructions + /sys/devices/cpu/events/stalled-cycles-backend + /sys/devices/cpu/events/instructions + /sys/devices/cpu/events/cpu-cycles + +Date: 2013/01/08 + +Contact: Linux kernel mailing list + +Description: Generic performance monitoring events + + A collection of performance monitoring events that may be + supported by many/most CPUs. These events can be monitored + using the 'perf(1)' tool. + + The contents of each file would look like: + + event=0xNNNN + + where 'N' is a hex digit and the number '0xNNNN' shows the + "raw code" for the perf event identified by the file's + "basename". + + +What: /sys/bus/event_source/devices//events/ +Date: 2014/02/24 +Contact: Linux kernel mailing list +Description: Per-pmu performance monitoring events specific to the running system + + Each file (except for some of those with a '.' in them, '.unit' + and '.scale') in the 'events' directory describes a single + performance monitoring event supported by the . The name + of the file is the name of the event. + + File contents: + + [=][,[=]]... + + Where is one of the terms listed under + /sys/bus/event_source/devices//format/ and is + a number is base-16 format with a '0x' prefix (lowercase only). + If a is specified alone (without an assigned value), it + is implied that 0x1 is assigned to that . + + Examples (each of these lines would be in a seperate file): + + event=0x2abc + event=0x423,inv,cmask=0x3 + domain=0x1,offset=0x8,starting_index=0xffff + domain=0x1,offset=0x8,core=? + + Each of the assignments indicates a value to be assigned to a + particular set of bits (as defined by the format file + corresponding to the ) in the perf_event structure passed + to the perf_open syscall. + + In the case of the last example, a value replacing "?" would + need to be provided by the user selecting the particular event. + This is referred to as "event parameterization". Event + parameters have the format 'param=?'. + +What: /sys/bus/event_source/devices//events/.unit +Date: 2014/02/24 +Contact: Linux kernel mailing list +Description: Perf event units + + A string specifying the English plural numerical unit that + (once multiplied by .scale) represents. + + Example: + + Joules + +What: /sys/bus/event_source/devices//events/.scale +Date: 2014/02/24 +Contact: Linux kernel mailing list +Description: Perf event scaling factors + + A string representing a floating point value expressed in + scientific notation to be multiplied by the event count + recieved from the kernel to match the unit specified in the + .unit file. + + Example: + + 2.3283064365386962890625e-10 + + This is provided to avoid performing floating point arithmetic + in the kernel. diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-format b/Documentation/ABI/testing/sysfs-bus-event_source-devices-format new file mode 100644 index 000000000..df7ccc1b2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-format @@ -0,0 +1,21 @@ +What: /sys/bus/event_source/devices//format +Date: January 2012 +KernelVersion: 3.3 +Contact: Jiri Olsa +Description: + Attribute group to describe the magic bits that go into + perf_event_attr::config[012] for a particular pmu. + Each attribute of this group defines the 'hardware' bitmask + we want to export, so that userspace can deal with sane + name/value pairs. + + Userspace must be prepared for the possibility that attributes + define overlapping bit ranges. For example:: + + attr1 = 'config:0-23' + attr2 = 'config:0-7' + attr3 = 'config:12-35' + + Example: 'config1:1,6-10,44' + Defines contents of attribute that occupies bits 1,6-10,44 of + perf_event_attr::config1. diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 new file mode 100644 index 000000000..de390a010 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 @@ -0,0 +1,98 @@ +What: /sys/bus/event_source/devices/hv_24x7/format +Date: September 2020 +Contact: Linux on PowerPC Developer List +Description: Read-only. Attribute group to describe the magic bits + that go into perf_event_attr.config for a particular pmu. + (See ABI/testing/sysfs-bus-event_source-devices-format). + + Each attribute under this group defines a bit range of the + perf_event_attr.config. All supported attributes are listed + below:: + + chip = "config:16-31" + core = "config:16-31" + domain = "config:0-3" + lpar = "config:0-15" + offset = "config:32-63" + vcpu = "config:16-31" + + For example:: + + PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0" + + In this event, '?' after chip specifies that + this value will be provided by user while running this event. + +What: /sys/bus/event_source/devices/hv_24x7/interface/catalog +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + Provides access to the binary "24x7 catalog" provided by the + hypervisor on POWER7 and 8 systems. This catalog lists events + available from the powerpc "hv_24x7" pmu. Its format is + documented here: + https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h + +What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + A number equal to the length in bytes of the catalog. This is + also extractable from the provided binary "catalog" sysfs entry. + +What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + Exposes the "version" field of the 24x7 catalog. This is also + extractable from the provided binary "catalog" sysfs entry. + +What: /sys/devices/hv_24x7/interface/sockets +Date: May 2020 +Contact: Linux on PowerPC Developer List +Description: read only + This sysfs interface exposes the number of sockets present in the + system. + +What: /sys/devices/hv_24x7/interface/chipspersocket +Date: May 2020 +Contact: Linux on PowerPC Developer List +Description: read only + This sysfs interface exposes the number of chips per socket + present in the system. + +What: /sys/devices/hv_24x7/interface/coresperchip +Date: May 2020 +Contact: Linux on PowerPC Developer List +Description: read only + This sysfs interface exposes the number of cores per chip + present in the system. + +What: /sys/devices/hv_24x7/cpumask +Date: July 2020 +Contact: Linux on PowerPC Developer List +Description: read only + This sysfs file exposes the cpumask which is designated to make + HCALLs to retrieve hv-24x7 pmu event counter data. + +What: /sys/bus/event_source/devices/hv_24x7/event_descs/ +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + Provides the description of a particular event as provided by + the firmware. If firmware does not provide a description, no + file will be created. + + Note that the event-name lacks the domain suffix appended for + events in the events/ dir. + +What: /sys/bus/event_source/devices/hv_24x7/event_long_descs/ +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + Provides the "long" description of a particular event as + provided by the firmware. If firmware does not provide a + description, no file will be created. + + Note that the event-name lacks the domain suffix appended for + events in the events/ dir. diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci new file mode 100644 index 000000000..12e2bf927 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci @@ -0,0 +1,82 @@ +What: /sys/bus/event_source/devices/hv_gpci/format +Date: September 2020 +Contact: Linux on PowerPC Developer List +Description: Read-only. Attribute group to describe the magic bits + that go into perf_event_attr.config for a particular pmu. + (See ABI/testing/sysfs-bus-event_source-devices-format). + + Each attribute under this group defines a bit range of the + perf_event_attr.config. All supported attributes are listed + below:: + + counter_info_version = "config:16-23" + length = "config:24-31" + partition_id = "config:32-63" + request = "config:0-31" + sibling_part_id = "config:32-63" + hw_chip_id = "config:32-63" + offset = "config:32-63" + phys_processor_idx = "config:32-63" + secondary_index = "config:0-15" + starting_index = "config:32-63" + + For example:: + + processor_core_utilization_instructions_completed = "request=0x94, + phys_processor_idx=?,counter_info_version=0x8, + length=8,offset=0x18" + + In this event, '?' after phys_processor_idx specifies this value + this value will be provided by user while running this event. + +What: /sys/bus/event_source/devices/hv_gpci/interface/collect_privileged +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + '0' if the hypervisor is configured to forbid access to event + counters being accumulated by other guests and to physical + domain event counters. + + '1' if that access is allowed. + +What: /sys/bus/event_source/devices/hv_gpci/interface/ga +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + 0 or 1. Indicates whether we have access to "GA" events (listed + in arch/powerpc/perf/hv-gpci.h). + +What: /sys/bus/event_source/devices/hv_gpci/interface/expanded +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + 0 or 1. Indicates whether we have access to "EXPANDED" events (listed + in arch/powerpc/perf/hv-gpci.h). + +What: /sys/bus/event_source/devices/hv_gpci/interface/lab +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + 0 or 1. Indicates whether we have access to "LAB" events (listed + in arch/powerpc/perf/hv-gpci.h). + +What: /sys/bus/event_source/devices/hv_gpci/interface/version +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + A number indicating the version of the gpci interface that the + hypervisor reports supporting. + +What: /sys/bus/event_source/devices/hv_gpci/interface/kernel_version +Date: February 2014 +Contact: Linux on PowerPC Developer List +Description: + A number indicating the latest version of the gpci interface + that the kernel is aware of. + +What: /sys/devices/hv_gpci/cpumask +Date: October 2020 +Contact: Linux on PowerPC Developer List +Description: read only + This sysfs file exposes the cpumask which is designated to make + HCALLs to retrieve hv-gpci pmu event counter data. diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-uncore b/Documentation/ABI/testing/sysfs-bus-event_source-devices-uncore new file mode 100644 index 000000000..b56e8f019 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-uncore @@ -0,0 +1,13 @@ +What: /sys/bus/event_source/devices/uncore_*/alias +Date: June 2021 +KernelVersion: 5.15 +Contact: Linux kernel mailing list +Description: Read-only. An attribute to describe the alias name of + the uncore PMU if an alias exists on some platforms. + The 'perf(1)' tool should treat both names the same. + They both can be used to access the uncore PMU. + + Example: + + $ cat /sys/devices/uncore_cha_2/alias + uncore_type_0_2 diff --git a/Documentation/ABI/testing/sysfs-bus-fcoe b/Documentation/ABI/testing/sysfs-bus-fcoe new file mode 100644 index 000000000..5a4f2091a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-fcoe @@ -0,0 +1,138 @@ +What: /sys/bus/fcoe/ +Date: August 2012 +KernelVersion: TBD +Contact: Robert Love , devel@open-fcoe.org +Description: The FCoE bus. Attributes in this directory are control interfaces. + +Attributes: + + ctlr_create: + 'FCoE Controller' instance creation interface. Writing an + to this file will allocate and populate sysfs with a + fcoe_ctlr_device (ctlr_X). The user can then configure any + per-port settings and finally write to the fcoe_ctlr_device's + 'start' attribute to begin the kernel's discovery and login + process. + + ctlr_destroy: + 'FCoE Controller' instance removal interface. Writing a + fcoe_ctlr_device's sysfs name to this file will log the + fcoe_ctlr_device out of the fabric or otherwise connected + FCoE devices. It will also free all kernel memory allocated + for this fcoe_ctlr_device and any structures associated + with it, this includes the scsi_host. + +What: /sys/bus/fcoe/devices/ctlr_X +Date: March 2012 +KernelVersion: TBD +Contact: Robert Love , devel@open-fcoe.org +Description: 'FCoE Controller' instances on the fcoe bus. + The FCoE Controller now has a three stage creation process. + 1) Write interface name to ctlr_create 2) Configure the FCoE + Controller (ctlr_X) 3) Enable the FCoE Controller to begin + discovery and login. The FCoE Controller is destroyed by + writing its name, i.e. ctlr_X to the ctlr_delete file. + +Attributes: + + fcf_dev_loss_tmo: + Device loss timeout period (see below). Changing + this value will change the dev_loss_tmo for all + FCFs discovered by this controller. + + mode: + Display or change the FCoE Controller's mode. Possible + modes are 'Fabric' and 'VN2VN'. If a FCoE Controller + is started in 'Fabric' mode then FIP FCF discovery is + initiated and ultimately a fabric login is attempted. + If a FCoE Controller is started in 'VN2VN' mode then + FIP VN2VN discovery and login is performed. A FCoE + Controller only supports one mode at a time. + + enabled: + Whether an FCoE controller is enabled or disabled. + 0 if disabled, 1 if enabled. Writing either 0 or 1 + to this file will enable or disable the FCoE controller. + + lesb/link_fail: + Link Error Status Block (LESB) link failure count. + + lesb/vlink_fail: + Link Error Status Block (LESB) virtual link + failure count. + + lesb/miss_fka: + Link Error Status Block (LESB) missed FCoE + Initialization Protocol (FIP) Keep-Alives (FKA). + + lesb/symb_err: + Link Error Status Block (LESB) symbolic error count. + + lesb/err_block: + Link Error Status Block (LESB) block error count. + + lesb/fcs_error: + Link Error Status Block (LESB) Fibre Channel + Services error count. + +Notes: ctlr_X (global increment starting at 0) + +What: /sys/bus/fcoe/devices/fcf_X +Date: March 2012 +KernelVersion: TBD +Contact: Robert Love , devel@open-fcoe.org +Description: 'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel + Forwarder, which is a FCoE switch that can accept FCoE + (Ethernet) packets, unpack them, and forward the embedded + Fibre Channel frames into a FC fabric. It can also take + outbound FC frames and pack them in Ethernet packets to + be sent to their destination on the Ethernet segment. + +Attributes: + + fabric_name: + Identifies the fabric that the FCF services. + + switch_name: + Identifies the FCF. + + priority: + The switch's priority amongst other FCFs on the same + fabric. + + selected: + 1 indicates that the switch has been selected for use; + 0 indicates that the switch will not be used. + + fc_map: + The Fibre Channel MAP + + vfid: + The Virtual Fabric ID + + mac: + The FCF's MAC address + + fka_period: + The FIP Keep-Alive period + + fabric_state: The internal kernel state + + - "Unknown" - Initialization value + - "Disconnected" - No link to the FCF/fabric + - "Connected" - Host is connected to the FCF + - "Deleted" - FCF is being removed from the system + + dev_loss_tmo: The device loss timeout period for this FCF. + +Notes: A device loss infrastructure similar to the FC Transport's + is present in fcoe_sysfs. It is nice to have so that a + link flapping adapter doesn't continually advance the count + used to identify the discovered FCF. FCFs will exist in a + "Disconnected" state until either the timer expires and the + FCF becomes "Deleted" or the FCF is rediscovered and becomes + "Connected." + + +Users: The first user of this interface will be the fcoeadm application, + which is commonly packaged in the fcoe-utils package. diff --git a/Documentation/ABI/testing/sysfs-bus-fsi b/Documentation/ABI/testing/sysfs-bus-fsi new file mode 100644 index 000000000..76e0caa0c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-fsi @@ -0,0 +1,46 @@ +What: /sys/bus/platform/devices/../fsi-master/fsi0/rescan +Date: May 2017 +KernelVersion: 4.12 +Contact: linux-fsi@lists.ozlabs.org +Description: + Initiates a FSI master scan for all connected slave devices + on its links. + +What: /sys/bus/platform/devices/../fsi-master/fsi0/break +Date: May 2017 +KernelVersion: 4.12 +Contact: linux-fsi@lists.ozlabs.org +Description: + Sends an FSI BREAK command on a master's communication + link to any connected slaves. A BREAK resets connected + device's logic and preps it to receive further commands + from the master. + +What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/term +Date: May 2017 +KernelVersion: 4.12 +Contact: linux-fsi@lists.ozlabs.org +Description: + Sends an FSI terminate command from the master to its + connected slave. A terminate resets the slave's state machines + that control access to the internally connected engines. In + addition the slave freezes its internal error register for + debugging purposes. This command is also needed to abort any + ongoing operation in case of an expired 'Master Time Out' + timer. + +What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/raw +Date: May 2017 +KernelVersion: 4.12 +Contact: linux-fsi@lists.ozlabs.org +Description: + Provides a means of reading/writing a 32 bit value from/to a + specified FSI bus address. + +What: /sys/bus/platform/devices/../cfam_reset +Date: Sept 2020 +KernelVersion: 5.10 +Contact: linux-fsi@lists.ozlabs.org +Description: + Provides a means of resetting the cfam that is attached to the + FSI device. diff --git a/Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo b/Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo new file mode 100644 index 000000000..c7393b4dd --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo @@ -0,0 +1,10 @@ +What: /sys/bus/fsi/devices/XX.XX.00:06/sbefifoX/timeout +KernelVersion: 5.15 +Contact: eajames@linux.ibm.com +Description: + Indicates whether or not this SBE device has experienced a + timeout; i.e. the SBE did not respond within the time allotted + by the driver. A value of 1 indicates that a timeout has + occurred and no transfers have completed since the timeout. A + value of 0 indicates that no timeout has occurred, or if one + has, more recent transfers have completed successfully. diff --git a/Documentation/ABI/testing/sysfs-bus-fsl-mc b/Documentation/ABI/testing/sysfs-bus-fsl-mc new file mode 100644 index 000000000..bf3c6af6a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-fsl-mc @@ -0,0 +1,25 @@ +What: /sys/bus/fsl-mc/drivers/.../bind +Date: December 2016 +Contact: stuart.yoder@nxp.com +Description: + Writing a device location to this file will cause + the driver to attempt to bind to the device found at + this location. The format for the location is Object.Id + and is the same as found in /sys/bus/fsl-mc/devices/. + + For example:: + + # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind + +What: /sys/bus/fsl-mc/drivers/.../unbind +Date: December 2016 +Contact: stuart.yoder@nxp.com +Description: + Writing a device location to this file will cause the + driver to attempt to unbind from the device found at + this location. The format for the location is Object.Id + and is the same as found in /sys/bus/fsl-mc/devices/. + + For example:: + + # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind diff --git a/Documentation/ABI/testing/sysfs-bus-hsi b/Documentation/ABI/testing/sysfs-bus-hsi new file mode 100644 index 000000000..1b1b282a9 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-hsi @@ -0,0 +1,19 @@ +What: /sys/bus/hsi +Date: April 2012 +KernelVersion: 3.4 +Contact: Carlos Chinea +Description: + High Speed Synchronous Serial Interface (HSI) is a + serial interface mainly used for connecting application + engines (APE) with cellular modem engines (CMT) in cellular + handsets. + The bus will be populated with devices (hsi_clients) representing + the protocols available in the system. Bus drivers implement + those protocols. + +What: /sys/bus/hsi/devices/.../modalias +Date: April 2012 +KernelVersion: 3.4 +Contact: Carlos Chinea +Description: Stores the same MODALIAS value emitted by uevent + Format: hsi: diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-bq32k b/Documentation/ABI/testing/sysfs-bus-i2c-devices-bq32k new file mode 100644 index 000000000..398b258fb --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-bq32k @@ -0,0 +1,7 @@ +What: /sys/bus/i2c/devices/.../trickle_charge_bypass +Date: Jan 2017 +KernelVersion: 4.11 +Contact: Enric Balletbo i Serra +Description: Attribute for enable/disable the trickle charge bypass + The trickle_charge_bypass attribute allows the userspace to + enable/disable the Trickle charge FET bypass. diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 new file mode 100644 index 000000000..42dfc9399 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 @@ -0,0 +1,27 @@ +What: /sys/bus/i2c/devices/.../device +Date: February 2011 +Contact: Minkyu Kang +Description: + show what device is attached + + ======= ====================== + NONE no device + USB USB device is attached + UART UART is attached + CHARGER Charger is attaced + JIG JIG is attached + ======= ====================== + +What: /sys/bus/i2c/devices/.../switch +Date: February 2011 +Contact: Minkyu Kang +Description: + show or set the state of manual switch + + ======= ============================== + VAUDIO switch to VAUDIO path + UART switch to UART path + AUDIO switch to AUDIO path + DHOST switch to DHOST path + AUTO switch automatically by device + ======= ============================== diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 new file mode 100644 index 000000000..4a251b7f1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 @@ -0,0 +1,21 @@ +What: /sys/bus/i2c/devices/.../heading0_input +Date: April 2010 +KernelVersion: 2.6.36? +Contact: alan.cox@intel.com +Description: Reports the current heading from the compass as a floating + point value in degrees. + +What: /sys/bus/i2c/devices/.../power_state +Date: April 2010 +KernelVersion: 2.6.36? +Contact: alan.cox@intel.com +Description: Sets the power state of the device. 0 sets the device into + sleep mode, 1 wakes it up. + +What: /sys/bus/i2c/devices/.../calibration +Date: April 2010 +KernelVersion: 2.6.36? +Contact: alan.cox@intel.com +Description: Sets the calibration on or off (1 = on, 0 = off). See the + chip data sheet. + diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 new file mode 100644 index 000000000..1b62230b3 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 @@ -0,0 +1,15 @@ +What: /sys/bus/i2c/devices/.../output_hvled[n] +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the controlling backlight device for high-voltage current + sink HVLED[n] (n = 1, 2) (0, 1). + +What: /sys/bus/i2c/devices/.../output_lvled[n] +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the controlling led device for low-voltage current sink + LVLED[n] (n = 1..5) (0..3). diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x b/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x new file mode 100644 index 000000000..b6c69eb80 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x @@ -0,0 +1,23 @@ +What: /sys/bus/i2c/.../idle_state +Date: January 2019 +KernelVersion: 5.2 +Contact: Robert Shearman +Description: + Value that exists only for mux devices that can be + written to control the behaviour of the multiplexer on + idle. Possible values: + + =========== =============================================== + -2 disconnect on idle, i.e. deselect the last used + channel, which is useful when there is a device + with an address that conflicts with another + device on another mux on the same parent bus. + -1 leave the mux as-is, which is the most optimal + setting in terms of I2C operations and is the + default mode. + 0.. set the mux to a predetermined channel, + which is useful if there is one channel that is + used almost always, and you want to reduce the + latency for normal operations after rare + transactions on other channels + =========== =============================================== diff --git a/Documentation/ABI/testing/sysfs-bus-i3c b/Documentation/ABI/testing/sysfs-bus-i3c new file mode 100644 index 000000000..1f4a26623 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i3c @@ -0,0 +1,148 @@ +What: /sys/bus/i3c/devices/i3c- +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + An I3C bus. This directory will contain one sub-directory per + I3C device present on the bus. + +What: /sys/bus/i3c/devices/i3c-/current_master +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + Expose the master that owns the bus (-) at + the time this file is read. Note that bus ownership can change + overtime, so there's no guarantee that when the read() call + returns, the value returned is still valid. + +What: /sys/bus/i3c/devices/i3c-/mode +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + I3C bus mode. Can be "pure", "mixed-fast" or "mixed-slow". See + the I3C specification for a detailed description of what each + of these modes implies. + +What: /sys/bus/i3c/devices/i3c-/i3c_scl_frequency +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + The frequency (expressed in Hz) of the SCL signal when + operating in I3C SDR mode. + +What: /sys/bus/i3c/devices/i3c-/i2c_scl_frequency +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + The frequency (expressed in Hz) of the SCL signal when + operating in I2C mode. + +What: /sys/bus/i3c/devices/i3c-/dynamic_address +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + Dynamic address assigned to the master controller. This + address may change if the bus is re-initialized. + +What: /sys/bus/i3c/devices/i3c-/bcr +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + BCR stands for Bus Characteristics Register and express the + device capabilities in term of speed, maximum read/write + length, etc. See the I3C specification for more details. + This entry describes the BCR of the master controller driving + the bus. + +What: /sys/bus/i3c/devices/i3c-/dcr +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + DCR stands for Device Characteristics Register and express the + device capabilities in term of exposed features. See the I3C + specification for more details. + This entry describes the DCR of the master controller driving + the bus. + +What: /sys/bus/i3c/devices/i3c-/pid +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + PID stands for Provisional ID and is used to uniquely identify + a device on a bus. This PID contains information about the + vendor, the part and an instance ID so that several devices of + the same type can be connected on the same bus. + See the I3C specification for more details. + This entry describes the PID of the master controller driving + the bus. + +What: /sys/bus/i3c/devices/i3c-/hdrcap +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + Expose the HDR (High Data Rate) capabilities of a device. + Returns a list of supported HDR mode, each element is separated + by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl". + See the I3C specification for more details about these HDR + modes. + + This entry describes the HDRCAP of the master controller + driving the bus. + +What: /sys/bus/i3c/devices/i3c-/- +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + An I3C device present on I3C bus identified by . Note + that all devices are represented including the master driving + the bus. + +What: /sys/bus/i3c/devices/i3c-/-/dynamic_address +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + Dynamic address assigned to device -. This + address may change if the bus is re-initialized. + +What: /sys/bus/i3c/devices/i3c-/-/bcr +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + BCR stands for Bus Characteristics Register and express the + device capabilities in term of speed, maximum read/write + length, etc. See the I3C specification for more details. + +What: /sys/bus/i3c/devices/i3c-/-/dcr +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + DCR stands for Device Characteristics Register and express the + device capabilities in term of exposed features. See the I3C + specification for more details. + +What: /sys/bus/i3c/devices/i3c-/-/pid +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + PID stands for Provisional ID and is used to uniquely identify + a device on a bus. This PID contains information about the + vendor, the part and an instance ID so that several devices of + the same type can be connected on the same bus. + See the I3C specification for more details. + +What: /sys/bus/i3c/devices/i3c-/-/hdrcap +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + Expose the HDR (High Data Rate) capabilities of a device. + Returns a list of supported HDR mode, each element is separated + by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl". + + See the I3C specification for more details about these HDR + modes. + +What: /sys/bus/i3c/devices/- +KernelVersion: 5.0 +Contact: linux-i3c@vger.kernel.org +Description: + These directories are just symbolic links to + /sys/bus/i3c/devices/i3c-/-. diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio new file mode 100644 index 000000000..6ba34c0d9 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio @@ -0,0 +1,2164 @@ +What: /sys/bus/iio/devices/iio:deviceX +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Hardware chip or device accessed by one communication port. + Corresponds to a grouping of sensor channels. X is the IIO + index of the device. + +What: /sys/bus/iio/devices/triggerX +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + An event driven driver of data capture to an in kernel buffer. + May be provided by a device driver that also has an IIO device + based on hardware generated events (e.g. data ready) or + provided by a separate driver for other hardware (e.g. + periodic timer, GPIO or high resolution timer). + + Contains trigger type specific elements. These do not + generalize well and hence are not documented in this file. + X is the IIO index of the trigger. + +What: /sys/bus/iio/devices/iio:deviceX/buffer +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Directory of attributes relating to the buffer for the device. + +What: /sys/bus/iio/devices/iio:deviceX/name +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Description of the physical chip / device for device X. + Typically a part number. + +What: /sys/bus/iio/devices/iio:deviceX/label +KernelVersion: 5.8 +Contact: linux-iio@vger.kernel.org +Description: + Optional symbolic label for a device. + This is useful for userspace to be able to better identify an + individual device. + + The contents of the label are free-form, but there are some + standardized uses: + + For proximity sensors which give the proximity (of a person) to + a certain wlan or wwan antenna the following standardized labels + are used: + + * "proximity-wifi" + * "proximity-lte" + * "proximity-wifi-lte" + * "proximity-wifi-left" + * "proximity-wifi-right" + + These are used to indicate to userspace that these proximity + sensors may be used to tune transmit power to ensure that + Specific Absorption Rate (SAR) limits are honored. + The "-left" and "-right" labels are for devices with multiple + antennas. + + In some laptops/tablets the standardized proximity sensor labels + instead indicate proximity to a specific part of the device: + + * "proximity-palmrest" indicates proximity to the keyboard's palmrest + * "proximity-palmrest-left" indicates proximity to the left part of the palmrest + * "proximity-palmrest-right" indicates proximity to the right part of the palmrest + * "proximity-lap" indicates the device is being used on someone's lap + + Note "proximity-lap" is special in that its value may be + calculated by firmware from other sensor readings, rather then + being a raw sensor reading. + + For accelerometers used in 2-in-1s with 360° (yoga-style) hinges, + which have an accelerometer in both their base and their display, + the following standardized labels are used: + + * "accel-base" + * "accel-display" + + For devices where an accelerometer is housed in the swivel camera subassembly + (for AR application), the following standardized label is used: + + * "accel-camera" + +What: /sys/bus/iio/devices/iio:deviceX/current_timestamp_clock +KernelVersion: 4.5 +Contact: linux-iio@vger.kernel.org +Description: + String identifying current posix clock used to timestamp + buffered samples and events for device X. + +What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency +What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency +What: /sys/bus/iio/devices/triggerX/sampling_frequency +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Some devices have internal clocks. This parameter sets the + resulting sampling frequency. In many devices this + parameter has an effect on input filters etc. rather than + simply controlling when the input is sampled. As this + affects data ready triggers, hardware buffers and the sysfs + direct access interfaces, it may be found in any of the + relevant directories. If it affects all of the above + then it is to be found in the base device directory. + + The stm32-timer-trigger has the additional characteristic that + a sampling_frequency of 0 is defined to stop sampling. + +What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency_available +What: /sys/bus/iio/devices/iio:deviceX/in_proximity_sampling_frequency_available +What: /sys/.../iio:deviceX/buffer/sampling_frequency_available +What: /sys/bus/iio/devices/triggerX/sampling_frequency_available +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + When the internal sampling clock can only take a specific set of + frequencies, we can specify the available values with: + + - a small discrete set of values like "0 2 4 6 8" + - a range with minimum, step and maximum frequencies like + "[min step max]" + +What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Hardware dependent ADC oversampling. Controls the sampling ratio + of the digital filter if available. + +What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Hardware dependent values supported by the oversampling filter. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_raw +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no bias removal etc.) voltage measurement from + channel Y. In special cases where the channel does not + correspond to externally available input one of the named + versions may be used. The number must always be specified and + unique to allow association with event codes. Units after + application of scale and offset are millivolts. + + Channels with 'i' and 'q' modifiers always exist in pairs and both + channels refer to the same signal. The 'i' channel contains the in-phase + component of the signal while the 'q' channel contains the quadrature + component. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled) differential voltage measurement equivalent to + channel Y - channel Z where these channel numbers apply to the + physically equivalent inputs when non differential readings are + separately available. In differential only parts, then all that + is required is a consistent labeling. Units after application + of scale and offset are millivolts. + +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_raw +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_raw +KernelVersion: 3.17 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no bias removal etc.) current measurement from + channel Y. In special cases where the channel does not + correspond to externally available input one of the named + versions may be used. The number must always be specified and + unique to allow association with event codes. Units after + application of scale and offset are milliamps. + +What: /sys/bus/iio/devices/iio:deviceX/in_powerY_raw +KernelVersion: 4.5 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no bias removal etc.) power measurement from + channel Y. The number must always be specified and + unique to allow association with event codes. Units after + application of scale and offset are milliwatts. + +What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw +KernelVersion: 3.2 +Contact: linux-iio@vger.kernel.org +Description: + Raw capacitance measurement from channel Y. Units after + application of scale and offset are nanofarads. + +What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_raw +KernelVersion: 3.2 +Contact: linux-iio@vger.kernel.org +Description: + Raw differential capacitance measurement equivalent to + channel Y - channel Z where these channel numbers apply to the + physically equivalent inputs when non differential readings are + separately available. In differential only parts, then all that + is required is a consistent labeling. Units after application + of scale and offset are nanofarads. + +What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_zeropoint +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + For differential channels, this an offset that is applied + equally to both inputs. As the reading is of the difference + between the two inputs, this should not be applied to the _raw + reading by userspace (unlike _offset) and unlike calibbias + it does not affect the differential value measured because + the effect of _zeropoint cancels out across the two inputs + that make up the differential pair. It's purpose is to bring + the individual signals, before the differential is measured, + within the measurement range of the device. The naming is + chosen because if the separate inputs that make the + differential pair are drawn on a graph in their + _raw units, this is the value that the zero point on the + measurement axis represents. It is expressed with the + same scaling as _raw. + +What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw +What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw +What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_temp_ambient_raw +What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no bias removal etc.) temperature measurement. + If an axis is specified it generally means that the temperature + sensor is associated with one part of a compound device (e.g. + a gyroscope axis). The ambient and object modifiers distinguish + between ambient (reference) and distant temperature for contact- + less measurements. Units after application of scale and offset + are milli degrees Celsius. + +What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Scaled temperature measurement in milli degrees Celsius. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Acceleration in direction x, y or z (may be arbitrarily assigned + but should match other such assignments on device). + Has all of the equivalent parameters as per voltageY. Units + after application of scale and offset are m/s^2. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_z_raw +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + As per in_accel_X_raw attributes, but minus the + acceleration due to gravity. + +What: /sys/bus/iio/devices/iio:deviceX/in_gravity_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_gravity_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_gravity_z_raw +KernelVersion: 4.11 +Contact: linux-iio@vger.kernel.org +Description: + Gravity in direction x, y or z (may be arbitrarily assigned + but should match other such assignments on device). + Units after application of scale and offset are m/s^2. + +What: /sys/bus/iio/devices/iio:deviceX/in_angl_raw +What: /sys/bus/iio/devices/iio:deviceX/in_anglY_raw +KernelVersion: 4.17 +Contact: linux-iio@vger.kernel.org +Description: + Angle of rotation. Units after application of scale and offset + are radians. + +What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_y_raw +KernelVersion: 4.19 +Contact: linux-iio@vger.kernel.org +Description: + Relative position in direction x or y on a pad (may be + arbitrarily assigned but should match other such assignments on + device). + Units after application of scale and offset are milli percents + from the pad's size in both directions. Should be calibrated by + the consumer. + +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Angular velocity about axis x, y or z (may be arbitrarily + assigned). Has all the equivalent parameters as per voltageY. + Units after application of scale and offset are radians per + second. + +What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Inclination raw reading about axis x, y or z (may be + arbitrarily assigned). Data converted by application of offset + and scale to degrees. + +What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Magnetic field along axis x, y or z (may be arbitrarily + assigned). Data converted by application of offset + then scale to Gauss. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw +KernelVersion: 2.6.36 +Contact: linux-iio@vger.kernel.org +Description: + Highest value since some reset condition. These + attributes allow access to this and are otherwise + the direct equivalent of the Y[_name]_raw attributes. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw +KernelVersion: 2.6.36 +Contact: linux-iio@vger.kernel.org +Description: + A computed peak value based on the sum squared magnitude of + the underlying value in the specified directions. + +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_raw +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_raw +KernelVersion: 3.8 +Contact: linux-iio@vger.kernel.org +Description: + Raw pressure measurement from channel Y. Units after + application of scale and offset are kilopascal. + +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_input +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_input +KernelVersion: 3.8 +Contact: linux-iio@vger.kernel.org +Description: + Scaled pressure measurement from channel Y, in kilopascal. + +What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_raw +KernelVersion: 3.14 +Contact: linux-iio@vger.kernel.org +Description: + Raw humidity measurement of air. Units after application of + scale and offset are milli percent. + +What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_input +KernelVersion: 3.14 +Contact: linux-iio@vger.kernel.org +Description: + Scaled humidity measurement in milli percent. + +What: /sys/bus/iio/devices/iio:deviceX/in_X_mean_raw +KernelVersion: 3.5 +Contact: linux-iio@vger.kernel.org +Description: + Averaged raw measurement from channel X. The number of values + used for averaging is device specific. The converting rules for + normal raw values also applies to the averaged raw values. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_offset +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_offset +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_offset +What: /sys/bus/iio/devices/iio:deviceX/in_current_offset +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_offset +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_offset +What: /sys/bus/iio/devices/iio:deviceX/in_current_q_offset +What: /sys/bus/iio/devices/iio:deviceX/in_current_i_offset +What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset +What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset +What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset +What: /sys/bus/iio/devices/iio:deviceX/in_magn_offset +What: /sys/bus/iio/devices/iio:deviceX/in_rot_offset +What: /sys/bus/iio/devices/iio:deviceX/in_angl_offset +What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceX_offset +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + If known for a device, offset to be added to [Y]_raw prior + to scaling by [Y]_scale in order to obtain value in the + units as specified in [Y]_raw documentation. + Not present if the offset is always 0 or unknown. If Y or + axis is not present, then the offset applies to all + in channels of . + May be writable if a variable offset can be applied on the + device. Note that this is different to calibbias which + is for devices (or drivers) that apply offsets to compensate + for variation between different instances of the part, typically + adjusted by using some hardware supported calibration procedure. + Calibbias is applied internally, offset is applied in userspace + to the _raw output. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_scale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_scale +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale +What: /sys/bus/iio/devices/iio:deviceX/in_current_scale +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_scale +What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_scale +What: /sys/bus/iio/devices/iio:deviceX/in_current_i_scale +What: /sys/bus/iio/devices/iio:deviceX/in_current_q_scale +What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale +What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale +What: /sys/bus/iio/devices/iio:deviceX/in_energy_scale +What: /sys/bus/iio/devices/iio:deviceX/in_distance_scale +What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale +What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale +What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale +What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_scale +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_scale +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_scale +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_scale +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale +What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale +What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale +What: /sys/bus/iio/devices/iio:deviceX/in_countY_scale +What: /sys/bus/iio/devices/iio:deviceX/in_angl_scale +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_scale +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_scale +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_scale +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_scale +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + If known for a device, scale to be applied to Y[_name]_raw + post addition of [Y][_name]_offset in order to obtain the + measured value in units as specified in + [Y][_name]_raw documentation. If shared across all in + channels then Y and are not present and the value is + called [Y][_name]_scale. The peak modifier means this + value is applied to Y[_name]_peak_raw values. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibbias +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibbias +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Hardware applied calibration offset (assumed to fix production + inaccuracies). + icm42600: For this device values are real physical offsets + expressed in SI units (m/s^2 for accelerometers and rad/s + for gyroscope)/ + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_calibbias_available +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_calibbias_available +KernelVersion: 5.8 +Contact: linux-iio@vger.kernel.org +Description: + Available values of calibbias. Maybe expressed as either of: + + - a small discrete set of values like "0 2 4 6 8" + - a range specified as "[min step max]" + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Hardware applied calibration scale factor (assumed to fix + production inaccuracies). If shared across all channels, + _calibscale is used. + +What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender +What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender +What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender +What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Gender of the user (e.g.: male, female) used by some pedometers + to compute the stride length, distance, speed and activity + type. + +What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available +What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available +What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available +What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available gender values (e.g.: male, female). + +What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibheight +What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibheight +What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibheight +What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibheight +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + Height of the user (in meters) used by some pedometers + to compute the stride length, distance, speed and activity + type. + +What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Weight of the user (in kg). It is needed by some pedometers + to compute the calories burnt by the user. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available +What: /sys/.../iio:deviceX/in_anglvel_scale_available +What: /sys/.../iio:deviceX/in_magn_scale_available +What: /sys/.../iio:deviceX/in_illuminance_scale_available +What: /sys/.../iio:deviceX/in_intensity_scale_available +What: /sys/.../iio:deviceX/in_proximity_scale_available +What: /sys/.../iio:deviceX/in_voltageX_scale_available +What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available +What: /sys/.../iio:deviceX/out_voltageX_scale_available +What: /sys/.../iio:deviceX/out_altvoltageX_scale_available +What: /sys/.../iio:deviceX/in_capacitance_scale_available +What: /sys/.../iio:deviceX/in_pressure_scale_available +What: /sys/.../iio:deviceX/in_pressureY_scale_available +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + If a discrete set of scale values is available, they + are listed in this attribute. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_red_hardwaregain +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_green_hardwaregain +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_blue_hardwaregain +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_clear_hardwaregain +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Hardware applied gain factor. If shared across all channels, + _hardwaregain is used. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain_available +KernelVersion: 5.10 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available hardware applied gain factors. Shared across all + channels. + +What: /sys/.../in_accel_filter_low_pass_3db_frequency +What: /sys/.../in_magn_filter_low_pass_3db_frequency +What: /sys/.../in_anglvel_filter_low_pass_3db_frequency +KernelVersion: 3.2 +Contact: linux-iio@vger.kernel.org +Description: + If a known or controllable low pass filter is applied + to the underlying data channel, then this parameter + gives the 3dB frequency of the filter in Hz. + +What: /sys/.../in_accel_filter_high_pass_3db_frequency +What: /sys/.../in_anglvel_filter_high_pass_3db_frequency +What: /sys/.../in_magn_filter_high_pass_3db_frequency +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + If a known or controllable high pass filter is applied + to the underlying data channel, then this parameter + gives the 3dB frequency of the filter in Hz. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled, no bias etc.) output voltage for + channel Y. The number must always be specified and + unique if the output corresponds to a single channel. + While DAC like devices typically use out_voltage, + a continuous frequency generating device, such as + a DDS or PLL should use out_altvoltage. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled, no bias etc.) output voltage for an aggregate of + channel Y, channel Z, etc. This interface is available in cases + where a single output sets the value for multiple channels + simultaneously. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode +What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the output powerdown mode. + DAC output stage is disconnected from the amplifier and + 1kohm_to_gnd: connected to ground via an 1kOhm resistor, + 2.5kohm_to_gnd: connected to ground via a 2.5kOhm resistor, + 6kohm_to_gnd: connected to ground via a 6kOhm resistor, + 20kohm_to_gnd: connected to ground via a 20kOhm resistor, + 90kohm_to_gnd: connected to ground via a 90kOhm resistor, + 100kohm_to_gnd: connected to ground via an 100kOhm resistor, + 125kohm_to_gnd: connected to ground via an 125kOhm resistor, + 500kohm_to_gnd: connected to ground via a 500kOhm resistor, + 640kohm_to_gnd: connected to ground via a 640kOhm resistor, + three_state: left floating. + For a list of available output power down options read + outX_powerdown_mode_available. If Y is not present the + mode is shared across all outputs. + +What: /sys/.../iio:deviceX/out_voltageY_powerdown_mode_available +What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available +What: /sys/.../iio:deviceX/out_altvoltageY_powerdown_mode_available +What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available output power down modes. + If Y is not present the mode is shared across all outputs. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown +What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + Writing 1 causes output Y to enter the power down mode specified + by the corresponding outY_powerdown_mode. DAC output stage is + disconnected from the amplifier. Clearing returns to normal + operation. Y may be suppressed if all outputs are controlled + together. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Output frequency for channel Y in Hz. The number must always be + specified and unique if the output corresponds to a single + channel. + Some drivers have additional constraints: + ADF4371 has an integrated VCO with fundamendal output + frequency ranging from 4000000000 Hz 8000000000 Hz. + + out_altvoltage0_frequency: + A divide by 1, 2, 4, 8, 16, 32 or circuit generates + frequencies from 62500000 Hz to 8000000000 Hz. + out_altvoltage1_frequency: + This channel duplicates the channel 0 frequency + out_altvoltage2_frequency: + A frequency doubler generates frequencies from + 8000000000 Hz to 16000000000 Hz. + out_altvoltage3_frequency: + A frequency quadrupler generates frequencies from + 16000000000 Hz to 32000000000 Hz. + + Note: writes to one of the channels will affect the frequency of + all the other channels, since it involves changing the VCO + fundamental output frequency. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Phase in radians of one frequency/clock output Y + (out_altvoltageY) relative to another frequency/clock output + (out_altvoltageZ) of the device X. The number must always be + specified and unique if the output corresponds to a single + channel. + +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set/get output current for channel Y. Units after application + of scale and offset are milliamps. + For some devices current channels are used to specify + current supplied to elements used in taking a measurement + of a different type. E.g. LED currents. + +What: /sys/bus/iio/devices/iio:deviceX/events +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + Configuration of which hardware generated events are passed up + to user-space. + +What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_voltageY_thresh_either_en +What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en +What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_rising_en +What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_falling_en +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Event generated when channel passes a threshold in the specified + (_rising|_falling) direction. If the direction is not specified, + then either the device will report an event which ever direction + a single threshold value is passed in (e.g. + [Y][_name]__thresh_value) or + [Y][_name]__thresh_rising_value and + [Y][_name]__thresh_falling_value may take + different values, but the device can only enable both thresholds + or neither. + + Note the driver will assume the last p events requested are + to be enabled where p is how many it supports (which may vary + depending on the exact set requested. So if you want to be + sure you have set what you think you have, check the contents of + these attributes after everything is configured. Drivers may + have to buffer any parameters so that they are consistent when + a given event type is enabled at a future point (and not those for + whatever event was previously enabled). + +What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en +What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en +What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en +What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en +What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en +What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en +What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en +What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en +What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en +What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en +What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en +What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en +What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en +What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_falling_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_rising_en +What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_falling_en +What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en +What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en +What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en +What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en +What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en +What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Event generated when channel passes a threshold on the rate of + change (1st differential) in the specified (_rising|_falling) + direction. If the direction is not specified, then either the + device will report an event which ever direction a single + threshold value is passed in (e.g. + [Y][_name]__roc_value) or + [Y][_name]__roc_rising_value and + [Y][_name]__roc_falling_value may take + different values, but the device can only enable both rate of + change thresholds or neither. + + Note the driver will assume the last p events requested are + to be enabled where p is however many it supports (which may + vary depending on the exact set requested. So if you want to be + sure you have set what you think you have, check the contents of + these attributes after everything is configured. Drivers may + have to buffer any parameters so that they are consistent when + a given event type is enabled a future point (and not those for + whatever event was previously enabled). + +What: /sys/.../events/in_capacitanceY_adaptive_thresh_rising_en +What: /sys/.../events/in_capacitanceY_adaptive_thresh_falling_en +KernelVersion: 5.13 +Contact: linux-iio@vger.kernel.org +Description: + Adaptive thresholds are similar to normal fixed thresholds + but the value is expressed as an offset from a value which + provides a low frequency approximation of the channel itself. + Thus these detect if a rapid change occurs in the specified + direction which crosses tracking value + offset. + Tracking value calculation is devices specific. + +What: /sys/.../in_capacitanceY_adaptive_thresh_rising_timeout +What: /sys/.../in_capacitanceY_adaptive_thresh_falling_timeout +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + When adaptive thresholds are used, the tracking signal + may adjust too slowly to step changes in the raw signal. + Thus these specify the time in seconds for which the + difference between the slow tracking signal and the raw + signal is allowed to remain out-of-range before a reset + event occurs in which the tracking signal is made equal + to the raw signal, allowing slow tracking to resume and the + adaptive threshold event detection to function as expected. + +What: /sys/.../events/in_accel_thresh_rising_value +What: /sys/.../events/in_accel_thresh_falling_value +What: /sys/.../events/in_accel_x_raw_thresh_rising_value +What: /sys/.../events/in_accel_x_raw_thresh_falling_value +What: /sys/.../events/in_accel_y_raw_thresh_rising_value +What: /sys/.../events/in_accel_y_raw_thresh_falling_value +What: /sys/.../events/in_accel_z_raw_thresh_rising_value +What: /sys/.../events/in_accel_z_raw_thresh_falling_value +What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value +What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value +What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value +What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value +What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value +What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value +What: /sys/.../events/in_magn_x_raw_thresh_rising_value +What: /sys/.../events/in_magn_x_raw_thresh_falling_value +What: /sys/.../events/in_magn_y_raw_thresh_rising_value +What: /sys/.../events/in_magn_y_raw_thresh_falling_value +What: /sys/.../events/in_magn_z_raw_thresh_rising_value +What: /sys/.../events/in_magn_z_raw_thresh_falling_value +What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_rising_value +What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_falling_value +What: /sys/.../events/in_rot_from_north_true_raw_thresh_rising_value +What: /sys/.../events/in_rot_from_north_true_raw_thresh_falling_value +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_rising_value +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_falling_value +What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_rising_value +What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_falling_value +What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value +What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value +What: /sys/.../events/in_voltageY_raw_thresh_rising_value +What: /sys/.../events/in_voltageY_raw_thresh_falling_value +What: /sys/.../events/in_tempY_raw_thresh_rising_value +What: /sys/.../events/in_tempY_raw_thresh_falling_value +What: /sys/.../events/in_illuminance0_thresh_falling_value +What: /sys/.../events/in_illuminance0_thresh_rising_value +What: /sys/.../events/in_proximity0_thresh_falling_value +What: /sys/.../events/in_proximity0_thresh_rising_value +What: /sys/.../events/in_illuminance_thresh_rising_value +What: /sys/.../events/in_illuminance_thresh_falling_value +What: /sys/.../events/in_capacitanceY_thresh_rising_value +What: /sys/.../events/in_capacitanceY_thresh_falling_value +What: /sys/.../events/in_capacitanceY_thresh_adaptive_rising_value +What: /sys/.../events/in_capacitanceY_thresh_falling_rising_value +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the value of threshold that the device is comparing + against for the events enabled by + Y[_name]_thresh[_rising|falling]_en. + + If separate attributes exist for the two directions, but + direction is not specified for this attribute, then a single + threshold value applies to both directions. + + The raw or input element of the name indicates whether the + value is in raw device units or in processed units (as _raw + and _input do on sysfs direct channel read attributes). + +What: /sys/.../events/in_accel_scale +What: /sys/.../events/in_accel_peak_scale +What: /sys/.../events/in_anglvel_scale +What: /sys/.../events/in_magn_scale +What: /sys/.../events/in_rot_from_north_magnetic_scale +What: /sys/.../events/in_rot_from_north_true_scale +What: /sys/.../events/in_voltage_scale +What: /sys/.../events/in_voltage_supply_scale +What: /sys/.../events/in_temp_scale +What: /sys/.../events/in_illuminance_scale +What: /sys/.../events/in_proximity_scale +KernelVersion: 3.21 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the conversion factor from the standard units + to device specific units used to set the event trigger + threshold. + +What: /sys/.../events/in_accel_x_thresh_rising_hysteresis +What: /sys/.../events/in_accel_x_thresh_falling_hysteresis +What: /sys/.../events/in_accel_x_thresh_either_hysteresis +What: /sys/.../events/in_accel_y_thresh_rising_hysteresis +What: /sys/.../events/in_accel_y_thresh_falling_hysteresis +What: /sys/.../events/in_accel_y_thresh_either_hysteresis +What: /sys/.../events/in_accel_z_thresh_rising_hysteresis +What: /sys/.../events/in_accel_z_thresh_falling_hysteresis +What: /sys/.../events/in_accel_z_thresh_either_hysteresis +What: /sys/.../events/in_anglvel_x_thresh_rising_hysteresis +What: /sys/.../events/in_anglvel_x_thresh_falling_hysteresis +What: /sys/.../events/in_anglvel_x_thresh_either_hysteresis +What: /sys/.../events/in_anglvel_y_thresh_rising_hysteresis +What: /sys/.../events/in_anglvel_y_thresh_falling_hysteresis +What: /sys/.../events/in_anglvel_y_thresh_either_hysteresis +What: /sys/.../events/in_anglvel_z_thresh_rising_hysteresis +What: /sys/.../events/in_anglvel_z_thresh_falling_hysteresis +What: /sys/.../events/in_anglvel_z_thresh_either_hysteresis +What: /sys/.../events/in_magn_x_thresh_rising_hysteresis +What: /sys/.../events/in_magn_x_thresh_falling_hysteresis +What: /sys/.../events/in_magn_x_thresh_either_hysteresis +What: /sys/.../events/in_magn_y_thresh_rising_hysteresis +What: /sys/.../events/in_magn_y_thresh_falling_hysteresis +What: /sys/.../events/in_magn_y_thresh_either_hysteresis +What: /sys/.../events/in_magn_z_thresh_rising_hysteresis +What: /sys/.../events/in_magn_z_thresh_falling_hysteresis +What: /sys/.../events/in_magn_z_thresh_either_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_thresh_either_hysteresis +What: /sys/.../events/in_rot_from_north_true_thresh_rising_hysteresis +What: /sys/.../events/in_rot_from_north_true_thresh_falling_hysteresis +What: /sys/.../events/in_rot_from_north_true_thresh_either_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_hysteresis +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_either_hysteresis +What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_hysteresis +What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_hysteresis +What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_either_hysteresis +What: /sys/.../events/in_voltageY_thresh_rising_hysteresis +What: /sys/.../events/in_voltageY_thresh_falling_hysteresis +What: /sys/.../events/in_voltageY_thresh_either_hysteresis +What: /sys/.../events/in_tempY_thresh_rising_hysteresis +What: /sys/.../events/in_tempY_thresh_falling_hysteresis +What: /sys/.../events/in_tempY_thresh_either_hysteresis +What: /sys/.../events/in_illuminance0_thresh_falling_hysteresis +What: /sys/.../events/in_illuminance0_thresh_rising_hysteresis +What: /sys/.../events/in_illuminance0_thresh_either_hysteresis +What: /sys/.../events/in_proximity0_thresh_falling_hysteresis +What: /sys/.../events/in_proximity0_thresh_rising_hysteresis +What: /sys/.../events/in_proximity0_thresh_either_hysteresis +KernelVersion: 3.13 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the hysteresis of threshold that the device is comparing + against for the events enabled by + Y[_name]_thresh[_(rising|falling)]_hysteresis. + If separate attributes exist for the two directions, but + direction is not specified for this attribute, then a single + hysteresis value applies to both directions. + + For falling events the hysteresis is added to the _value attribute for + this event to get the upper threshold for when the event goes back to + normal, for rising events the hysteresis is subtracted from the _value + attribute. E.g. if in_voltage0_raw_thresh_rising_value is set to 1200 + and in_voltage0_raw_thresh_rising_hysteresis is set to 50. The event + will get activated once in_voltage0_raw goes above 1200 and will become + deactivated again once the value falls below 1150. + +What: /sys/.../events/in_accel_x_raw_roc_rising_value +What: /sys/.../events/in_accel_x_raw_roc_falling_value +What: /sys/.../events/in_accel_y_raw_roc_rising_value +What: /sys/.../events/in_accel_y_raw_roc_falling_value +What: /sys/.../events/in_accel_z_raw_roc_rising_value +What: /sys/.../events/in_accel_z_raw_roc_falling_value +What: /sys/.../events/in_anglvel_x_raw_roc_rising_value +What: /sys/.../events/in_anglvel_x_raw_roc_falling_value +What: /sys/.../events/in_anglvel_y_raw_roc_rising_value +What: /sys/.../events/in_anglvel_y_raw_roc_falling_value +What: /sys/.../events/in_anglvel_z_raw_roc_rising_value +What: /sys/.../events/in_anglvel_z_raw_roc_falling_value +What: /sys/.../events/in_magn_x_raw_roc_rising_value +What: /sys/.../events/in_magn_x_raw_roc_falling_value +What: /sys/.../events/in_magn_y_raw_roc_rising_value +What: /sys/.../events/in_magn_y_raw_roc_falling_value +What: /sys/.../events/in_magn_z_raw_roc_rising_value +What: /sys/.../events/in_magn_z_raw_roc_falling_value +What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_rising_value +What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_falling_value +What: /sys/.../events/in_rot_from_north_true_raw_roc_rising_value +What: /sys/.../events/in_rot_from_north_true_raw_roc_falling_value +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_rising_value +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_falling_value +What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_rising_value +What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_falling_value +What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value +What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value +What: /sys/.../events/in_voltageY_raw_roc_rising_value +What: /sys/.../events/in_voltageY_raw_roc_falling_value +What: /sys/.../events/in_tempY_raw_roc_rising_value +What: /sys/.../events/in_tempY_raw_roc_falling_value +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the value of rate of change threshold that the + device is comparing against for the events enabled by + [Y][_name]_roc[_rising|falling]_en. + + If separate attributes exist for the two directions, + but direction is not specified for this attribute, + then a single threshold value applies to both directions. + The raw or input element of the name indicates whether the + value is in raw device units or in processed units (as _raw + and _input do on sysfs direct channel read attributes). + +What: /sys/.../events/in_accel_x_thresh_rising_period +What: /sys/.../events/in_accel_x_thresh_falling_period +What: /sys/.../events/in_accel_x_roc_rising_period +What: /sys/.../events/in_accel_x_roc_falling_period +What: /sys/.../events/in_accel_y_thresh_rising_period +What: /sys/.../events/in_accel_y_thresh_falling_period +What: /sys/.../events/in_accel_y_roc_rising_period +What: /sys/.../events/in_accel_y_roc_falling_period +What: /sys/.../events/in_accel_z_thresh_rising_period +What: /sys/.../events/in_accel_z_thresh_falling_period +What: /sys/.../events/in_accel_z_roc_rising_period +What: /sys/.../events/in_accel_z_roc_falling_period +What: /sys/.../events/in_anglvel_x_thresh_rising_period +What: /sys/.../events/in_anglvel_x_thresh_falling_period +What: /sys/.../events/in_anglvel_x_roc_rising_period +What: /sys/.../events/in_anglvel_x_roc_falling_period +What: /sys/.../events/in_anglvel_y_thresh_rising_period +What: /sys/.../events/in_anglvel_y_thresh_falling_period +What: /sys/.../events/in_anglvel_y_roc_rising_period +What: /sys/.../events/in_anglvel_y_roc_falling_period +What: /sys/.../events/in_anglvel_z_thresh_rising_period +What: /sys/.../events/in_anglvel_z_thresh_falling_period +What: /sys/.../events/in_anglvel_z_roc_rising_period +What: /sys/.../events/in_anglvel_z_roc_falling_period +What: /sys/.../events/in_magn_x_thresh_rising_period +What: /sys/.../events/in_magn_x_thresh_falling_period +What: /sys/.../events/in_magn_x_roc_rising_period +What: /sys/.../events/in_magn_x_roc_falling_period +What: /sys/.../events/in_magn_y_thresh_rising_period +What: /sys/.../events/in_magn_y_thresh_falling_period +What: /sys/.../events/in_magn_y_roc_rising_period +What: /sys/.../events/in_magn_y_roc_falling_period +What: /sys/.../events/in_magn_z_thresh_rising_period +What: /sys/.../events/in_magn_z_thresh_falling_period +What: /sys/.../events/in_magn_z_roc_rising_period +What: /sys/.../events/in_magn_z_roc_falling_period +What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_period +What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_period +What: /sys/.../events/in_rot_from_north_magnetic_roc_rising_period +What: /sys/.../events/in_rot_from_north_magnetic_roc_falling_period +What: /sys/.../events/in_rot_from_north_true_thresh_rising_period +What: /sys/.../events/in_rot_from_north_true_thresh_falling_period +What: /sys/.../events/in_rot_from_north_true_roc_rising_period +What: /sys/.../events/in_rot_from_north_true_roc_falling_period +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_period +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_period +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_rising_period +What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_falling_period +What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_period +What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_period +What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_rising_period +What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_falling_period +What: /sys/.../events/in_voltageY_supply_thresh_rising_period +What: /sys/.../events/in_voltageY_supply_thresh_falling_period +What: /sys/.../events/in_voltageY_supply_roc_rising_period +What: /sys/.../events/in_voltageY_supply_roc_falling_period +What: /sys/.../events/in_voltageY_thresh_rising_period +What: /sys/.../events/in_voltageY_thresh_falling_period +What: /sys/.../events/in_voltageY_roc_rising_period +What: /sys/.../events/in_voltageY_roc_falling_period +What: /sys/.../events/in_tempY_thresh_rising_period +What: /sys/.../events/in_tempY_thresh_falling_period +What: /sys/.../events/in_tempY_roc_rising_period +What: /sys/.../events/in_tempY_roc_falling_period +What: /sys/.../events/in_accel_x&y&z_mag_falling_period +What: /sys/.../events/in_intensity0_thresh_period +What: /sys/.../events/in_proximity0_thresh_period +What: /sys/.../events/in_activity_still_thresh_rising_period +What: /sys/.../events/in_activity_still_thresh_falling_period +What: /sys/.../events/in_activity_walking_thresh_rising_period +What: /sys/.../events/in_activity_walking_thresh_falling_period +What: /sys/.../events/in_activity_jogging_thresh_rising_period +What: /sys/.../events/in_activity_jogging_thresh_falling_period +What: /sys/.../events/in_activity_running_thresh_rising_period +What: /sys/.../events/in_activity_running_thresh_falling_period +What: /sys/.../events/in_illuminance_thresh_either_period +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Period of time (in seconds) for which the condition must be + met before an event is generated. If direction is not + specified then this period applies to both directions. + +What: /sys/.../events/in_accel_thresh_rising_low_pass_filter_3db +What: /sys/.../events/in_anglvel_thresh_rising_low_pass_filter_3db +What: /sys/.../events/in_magn_thresh_rising_low_pass_filter_3db +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + If a low pass filter can be applied to the event generation + this property gives its 3db frequency in Hz. + A value of zero disables the filter. + +What: /sys/.../events/in_accel_thresh_rising_high_pass_filter_3db +What: /sys/.../events/in_anglvel_thresh_rising_high_pass_filter_3db +What: /sys/.../events/in_magn_thresh_rising_high_pass_filter_3db +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + If a high pass filter can be applied to the event generation + this property gives its 3db frequency in Hz. + A value of zero disables the filter. + +What: /sys/.../events/in_activity_still_thresh_rising_en +What: /sys/.../events/in_activity_still_thresh_falling_en +What: /sys/.../events/in_activity_walking_thresh_rising_en +What: /sys/.../events/in_activity_walking_thresh_falling_en +What: /sys/.../events/in_activity_jogging_thresh_rising_en +What: /sys/.../events/in_activity_jogging_thresh_falling_en +What: /sys/.../events/in_activity_running_thresh_rising_en +What: /sys/.../events/in_activity_running_thresh_falling_en +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + Enables or disables activity events. Depending on direction + an event is generated when sensor ENTERS or LEAVES a given state. + +What: /sys/.../events/in_activity_still_thresh_rising_value +What: /sys/.../events/in_activity_still_thresh_falling_value +What: /sys/.../events/in_activity_walking_thresh_rising_value +What: /sys/.../events/in_activity_walking_thresh_falling_value +What: /sys/.../events/in_activity_jogging_thresh_rising_value +What: /sys/.../events/in_activity_jogging_thresh_falling_value +What: /sys/.../events/in_activity_running_thresh_rising_value +What: /sys/.../events/in_activity_running_thresh_falling_value +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + Confidence value (in units as percentage) to be used + for deciding when an event should be generated. E.g for + running: If the confidence value reported by the sensor + is greater than in_activity_running_thresh_rising_value + then the sensor ENTERS running state. Conversely, if the + confidence value reported by the sensor is lower than + in_activity_running_thresh_falling_value then the sensor + is LEAVING running state. + +What: /sys/.../iio:deviceX/events/in_accel_mag_en +What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en +What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en +What: /sys/.../iio:deviceX/events/in_accel_x_mag_en +What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en +What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en +What: /sys/.../iio:deviceX/events/in_accel_z_mag_en +What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en +What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en +What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en +What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + Similar to in_accel_x_thresh[_rising|_falling]_en, but here the + magnitude of the channel is compared to the threshold, not its + signed value. + +What: /sys/.../events/in_accel_raw_mag_value +What: /sys/.../events/in_accel_x_raw_mag_rising_value +What: /sys/.../events/in_accel_y_raw_mag_rising_value +What: /sys/.../events/in_accel_z_raw_mag_rising_value +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + The value to which the magnitude of the channel is compared. If + number or direction is not specified, applies to all channels of + this type. + +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_en +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_en +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_en +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_en +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Similar to in_accel_mag[_y][_rising|_falling]_en, but the event + value is relative to a reference magnitude. The reference magnitude + includes the graviational acceleration. + +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_value +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_value +What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_value +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_value +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_value +What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_value +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + The value to which the reference magnitude of the channel is + compared. If the axis is not specified, it applies to all channels + of this type. + +What: /sys/.../events/in_steps_change_en +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Event generated when channel passes a threshold on the absolute + change in value. E.g. for steps: a step change event is + generated each time the user takes N steps, where N is set using + in_steps_change_value. + +What: /sys/.../events/in_steps_change_value +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the value of change threshold that the + device is comparing against for the events enabled by + [Y][_name]_roc[_rising|falling|]_en. E.g. for steps: + if set to 3, a step change event will be generated every 3 + steps. + +What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger +KernelVersion: 2.6.35 +Contact: linux-iio@vger.kernel.org +Description: + The name of the trigger source being used, as per string given + in /sys/class/iio/triggerY/name. + +What: /sys/bus/iio/devices/iio:deviceX/bufferY/length +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + Number of scans contained by the buffer. + +What: /sys/bus/iio/devices/iio:deviceX/bufferY/enable +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + Actually start the buffer capture up. Will start trigger + if first device and appropriate. + + Note that it might be impossible to configure other attributes, + (e.g.: events, scale, sampling rate) if they impact the currently + active buffer capture session. + +What: /sys/bus/iio/devices/iio:deviceX/bufferY +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + Directory containing interfaces for elements that will be + captured for a single triggered sample set in the buffer. + + Since kernel 5.11 the scan_elements attributes are merged into + the bufferY directory, to be configurable per buffer. + +What: /sys/.../iio:deviceX/bufferY/in_accel_x_en +What: /sys/.../iio:deviceX/bufferY/in_accel_y_en +What: /sys/.../iio:deviceX/bufferY/in_accel_z_en +What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_en +What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_en +What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_en +What: /sys/.../iio:deviceX/bufferY/in_magn_x_en +What: /sys/.../iio:deviceX/bufferY/in_magn_y_en +What: /sys/.../iio:deviceX/bufferY/in_magn_z_en +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_en +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_en +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_en +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_en +What: /sys/.../iio:deviceX/bufferY/in_timestamp_en +What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_en +What: /sys/.../iio:deviceX/bufferY/in_voltageY_en +What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en +What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_en +What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_en +What: /sys/.../iio:deviceX/bufferY/in_voltage_i_en +What: /sys/.../iio:deviceX/bufferY/in_voltage_q_en +What: /sys/.../iio:deviceX/bufferY/in_incli_x_en +What: /sys/.../iio:deviceX/bufferY/in_incli_y_en +What: /sys/.../iio:deviceX/bufferY/in_pressureY_en +What: /sys/.../iio:deviceX/bufferY/in_pressure_en +What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_en +What: /sys/.../iio:deviceX/bufferY/in_proximity_en +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + Scan element control for triggered data capture. + +What: /sys/.../iio:deviceX/bufferY/in_accel_type +What: /sys/.../iio:deviceX/bufferY/in_anglvel_type +What: /sys/.../iio:deviceX/bufferY/in_magn_type +What: /sys/.../iio:deviceX/bufferY/in_incli_type +What: /sys/.../iio:deviceX/bufferY/in_voltageY_type +What: /sys/.../iio:deviceX/bufferY/in_voltage_type +What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_type +What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_type +What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_type +What: /sys/.../iio:deviceX/bufferY/in_voltage_i_type +What: /sys/.../iio:deviceX/bufferY/in_voltage_q_type +What: /sys/.../iio:deviceX/bufferY/in_timestamp_type +What: /sys/.../iio:deviceX/bufferY/in_pressureY_type +What: /sys/.../iio:deviceX/bufferY/in_pressure_type +What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_type +What: /sys/.../iio:deviceX/bufferY/in_proximity_type +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + Description of the scan element data storage within the buffer + and hence the form in which it is read from user-space. + Form is [be|le]:[s|u]bits/storagebits[>>shift]. + be or le specifies big or little endian. s or u specifies if + signed (2's complement) or unsigned. bits is the number of bits + of data and storagebits is the space (after padding) that it + occupies in the buffer. shift if specified, is the shift that + needs to be applied prior to masking out unused bits. Some + devices put their data in the middle of the transferred elements + with additional information on both sides. Note that some + devices will have additional information in the unused bits + so to get a clean value, the bits value must be used to mask + the buffer output value appropriately. The storagebits value + also specifies the data alignment. So s48/64>>2 will be a + signed 48 bit integer stored in a 64 bit location aligned to + a 64 bit boundary. To obtain the clean value, shift right 2 + and apply a mask to zero the top 16 bits of the result. + For other storage combinations this attribute will be extended + appropriately. + +What: /sys/.../iio:deviceX/scan_elements/in_accel_type_available +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + If the type parameter can take one of a small set of values, + this attribute lists them. + +What: /sys/.../iio:deviceX/bufferY/in_voltageY_index +What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_index +What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_index +What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_index +What: /sys/.../iio:deviceX/bufferY/in_voltage_i_index +What: /sys/.../iio:deviceX/bufferY/in_voltage_q_index +What: /sys/.../iio:deviceX/bufferY/in_accel_x_index +What: /sys/.../iio:deviceX/bufferY/in_accel_y_index +What: /sys/.../iio:deviceX/bufferY/in_accel_z_index +What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_index +What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_index +What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_index +What: /sys/.../iio:deviceX/bufferY/in_magn_x_index +What: /sys/.../iio:deviceX/bufferY/in_magn_y_index +What: /sys/.../iio:deviceX/bufferY/in_magn_z_index +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_index +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_index +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_index +What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_index +What: /sys/.../iio:deviceX/bufferY/in_incli_x_index +What: /sys/.../iio:deviceX/bufferY/in_incli_y_index +What: /sys/.../iio:deviceX/bufferY/in_timestamp_index +What: /sys/.../iio:deviceX/bufferY/in_pressureY_index +What: /sys/.../iio:deviceX/bufferY/in_pressure_index +What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_index +What: /sys/.../iio:deviceX/bufferY/in_proximity_index +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + A single positive integer specifying the position of this + scan element in the buffer. Note these are not dependent on + what is enabled and may not be contiguous. Thus for user-space + to establish the full layout these must be used in conjunction + with all _en attributes to establish which channels are present, + and the relevant _type attributes to establish the data storage + format. + +What: /sys/.../iio:deviceX/in_activity_still_input +What: /sys/.../iio:deviceX/in_activity_walking_input +What: /sys/.../iio:deviceX/in_activity_jogging_input +What: /sys/.../iio:deviceX/in_activity_running_input +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the confidence for an activity + expressed in units as percentage. + +What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the amount of quadrature error + present in the device at a given time. + +What: /sys/.../iio:deviceX/in_accelX_power_mode +KernelVersion: 3.11 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the chip power mode. + low_noise: reduce noise level from ADC, + low_power: enable low current consumption. + For a list of available output power modes read + in_accel_power_mode_available. + +What: /sys/.../iio:deviceX/in_energy_input +What: /sys/.../iio:deviceX/in_energy_raw +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the energy value reported by the + device (e.g.: human activity sensors report energy burnt by the + user). Units after application of scale are Joules. + +What: /sys/.../iio:deviceX/in_distance_input +What: /sys/.../iio:deviceX/in_distance_raw +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the measured distance to an object + or the distance covered by the user since the last reboot while + activated. Units after application of scale are meters. + +What: /sys/bus/iio/devices/iio:deviceX/store_eeprom +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Writing '1' stores the current device configuration into + on-chip EEPROM. After power-up or chip reset the device will + automatically load the saved configuration. + +What: /sys/.../iio:deviceX/in_proximity_raw +What: /sys/.../iio:deviceX/in_proximity_input +What: /sys/.../iio:deviceX/in_proximityY_raw +KernelVersion: 3.4 +Contact: linux-iio@vger.kernel.org +Description: + Proximity measurement indicating that some + object is near the sensor, usually by observing + reflectivity of infrared or ultrasound emitted. + + Often these sensors are unit less and as such conversion + to SI units is not possible. Higher proximity measurements + indicate closer objects, and vice versa. Units after + application of scale and offset are meters. + +What: /sys/.../iio:deviceX/in_illuminance_input +What: /sys/.../iio:deviceX/in_illuminance_raw +What: /sys/.../iio:deviceX/in_illuminanceY_input +What: /sys/.../iio:deviceX/in_illuminanceY_raw +What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw +What: /sys/.../iio:deviceX/in_illuminance_ir_raw +What: /sys/.../iio:deviceX/in_illuminance_clear_raw +KernelVersion: 3.4 +Contact: linux-iio@vger.kernel.org +Description: + Illuminance measurement, units after application of scale + and offset are lux. + +What: /sys/.../iio:deviceX/in_intensityY_raw +What: /sys/.../iio:deviceX/in_intensityY_ir_raw +What: /sys/.../iio:deviceX/in_intensityY_both_raw +What: /sys/.../iio:deviceX/in_intensityY_uv_raw +What: /sys/.../iio:deviceX/in_intensityY_duv_raw +KernelVersion: 3.4 +Contact: linux-iio@vger.kernel.org +Description: + Unit-less light intensity. Modifiers both and ir indicate + that measurements contain visible and infrared light + components or just infrared light, respectively. Modifier + uv indicates that measurements contain ultraviolet light + components. Modifier duv indicates that measurements + contain deep ultraviolet light components. + +What: /sys/.../iio:deviceX/in_uvindex_input +KernelVersion: 4.6 +Contact: linux-iio@vger.kernel.org +Description: + UV light intensity index measuring the human skin's response to + different wavelength of sunlight weighted according to the + standardised CIE Erythemal Action Spectrum. UV index values range + from 0 (low) to >=11 (extreme). + +What: /sys/.../iio:deviceX/in_intensity_integration_time +What: /sys/.../iio:deviceX/in_intensity_red_integration_time +What: /sys/.../iio:deviceX/in_intensity_green_integration_time +What: /sys/.../iio:deviceX/in_intensity_blue_integration_time +What: /sys/.../iio:deviceX/in_intensity_clear_integration_time +What: /sys/.../iio:deviceX/in_illuminance_integration_time +KernelVersion: 3.12 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to get/set the integration time in + seconds. If shared across all channels of a given type, + _integration_time is used. + +What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Number of seconds in which to compute speed. + +What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw +KernelVersion: 3.15 +Contact: linux-iio@vger.kernel.org +Description: + Raw value of quaternion components using a format + x y z w. Here x, y, and z component represents the axis about + which a rotation will occur and w component represents the + amount of rotation. + +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_raw +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_raw +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_raw +What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_raw +KernelVersion: 3.15 +Contact: linux-iio@vger.kernel.org +Description: + Raw value of rotation from true/magnetic north measured with + or without compensation from tilt sensors. + +What: /sys/bus/iio/devices/iio:deviceX/in_currentX_raw +What: /sys/bus/iio/devices/iio:deviceX/in_currentX_i_raw +What: /sys/bus/iio/devices/iio:deviceX/in_currentX_q_raw +KernelVersion: 3.18 +Contact: linux-iio@vger.kernel.org +Description: + Raw current measurement from channel X. Units are in milliamps + after application of scale and offset. If no offset or scale is + present, output should be considered as processed with the + unit in milliamps. + + Channels with 'i' and 'q' modifiers always exist in pairs and both + channels refer to the same signal. The 'i' channel contains the in-phase + component of the signal while the 'q' channel contains the quadrature + component. + +What: /sys/.../iio:deviceX/in_energy_en +What: /sys/.../iio:deviceX/in_distance_en +What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_en +What: /sys/.../iio:deviceX/in_steps_en +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + Activates a device feature that runs in firmware/hardware. + E.g. for steps: the pedometer saves power while not used; + when activated, it will count the steps taken by the user in + firmware and export them through in_steps_input. + +What: /sys/.../iio:deviceX/in_steps_input +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the number of steps taken by the user + since the last reboot while activated. + +What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_input +What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_raw +KernelVersion: 3.19 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to read the current speed value of the + user (which is the norm or magnitude of the velocity vector). + Units after application of scale are m/s. + +What: /sys/.../iio:deviceX/in_steps_debounce_count +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the number of steps that must occur within + in_steps_filter_debounce_time for the pedometer to decide the + consumer is making steps. + +What: /sys/.../iio:deviceX/in_steps_debounce_time +KernelVersion: 4.0 +Contact: linux-iio@vger.kernel.org +Description: + Specifies number of seconds in which we compute the steps + that occur in order to decide if the consumer is making steps. + +What: /sys/bus/iio/devices/iio:deviceX/bufferY/watermark +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + A single positive integer specifying the maximum number of scan + elements to wait for. + + Poll will block until the watermark is reached. + + Blocking read will wait until the minimum between the requested + read amount or the low water mark is available. + + Non-blocking read will retrieve the available samples from the + buffer even if there are less samples then watermark level. This + allows the application to block on poll with a timeout and read + the available samples after the timeout expires and thus have a + maximum delay guarantee. + +What: /sys/bus/iio/devices/iio:deviceX/bufferY/data_available +KernelVersion: 5.11 +Contact: linux-iio@vger.kernel.org +Description: + A read-only value indicating the bytes of data available in the + buffer. In the case of an output buffer, this indicates the + amount of empty space available to write data to. In the case of + an input buffer, this indicates the amount of data available for + reading. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + A read-only boolean value that indicates if the hardware fifo is + currently enabled or disabled. If the device does not have a + hardware fifo this entry is not present. + The hardware fifo is enabled when the buffer is enabled if the + current hardware fifo watermark level is set and other current + device settings allows it (e.g. if a trigger is set that samples + data differently that the hardware fifo does then hardware fifo + will not enabled). + + If the hardware fifo is enabled and the level of the hardware + fifo reaches the hardware fifo watermark level the device will + flush its hardware fifo to the device buffer. Doing a non + blocking read on the device when no samples are present in the + device buffer will also force a flush. + + When the hardware fifo is enabled there is no need to use a + trigger to use buffer mode since the watermark settings + guarantees that the hardware fifo is flushed to the device + buffer. + +What: /sys/bus/iio/devices/iio:device*/buffer/hwfifo_timeout +KernelVersion: 4.12 +Contact: linux-iio@vger.kernel.org +Description: + A read/write property to provide capability to delay reporting of + samples till a timeout is reached. This allows host processors to + sleep, while the sensor is storing samples in its internal fifo. + The maximum timeout in seconds can be specified by setting + hwfifo_timeout.The current delay can be read by reading + hwfifo_timeout. A value of 0 means that there is no timeout. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + Read-only entry that contains a single integer specifying the + current watermark level for the hardware fifo. If the device + does not have a hardware fifo this entry is not present. + The watermark level for the hardware fifo is set by the driver + based on the value set by the user in buffer/watermark but + taking into account hardware limitations (e.g. most hardware + buffers are limited to 32-64 samples, some hardware buffers + watermarks are fixed or have minimum levels). A value of 0 + means that the hardware watermark is unset. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_min +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + A single positive integer specifying the minimum watermark level + for the hardware fifo of this device. If the device does not + have a hardware fifo this entry is not present. + + If the user sets buffer/watermark to a value less than this one, + then the hardware watermark will remain unset. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_max +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + A single positive integer specifying the maximum watermark level + for the hardware fifo of this device. If the device does not + have a hardware fifo this entry is not present. + + If the user sets buffer/watermark to a value greater than this + one, then the hardware watermark will be capped at this value. + +What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_available +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + A list of positive integers specifying the available watermark + levels for the hardware fifo. This entry is optional and if it + is not present it means that all the values between + hwfifo_watermark_min and hwfifo_watermark_max are supported. + + If the user sets buffer/watermark to a value greater than + hwfifo_watermak_min but not equal to any of the values in this + list, the driver will chose an appropriate value for the + hardware fifo watermark level. + +What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibemissivity +What: /sys/bus/iio/devices/iio:deviceX/in_tempX_calibemissivity +What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibemissivity +What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibemissivity +KernelVersion: 4.1 +Contact: linux-iio@vger.kernel.org +Description: + The emissivity ratio of the surface in the field of view of the + contactless temperature sensor. Emissivity varies from 0 to 1, + with 1 being the emissivity of a black body. + +What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_oversampling_ratio +What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_oversampling_ratio +What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_oversampling_ratio +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + Hardware applied number of measurements for acquiring one + data point. The HW will do [_name]_oversampling_ratio + measurements and return the average value as output data. Each + value resulted from [_name]_oversampling_ratio measurements + is considered as one sample for [_name]_sampling_frequency. + +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_co2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_ethanol_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_ethanol_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_h2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_h2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_o2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_o2_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_voc_raw +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_voc_raw +KernelVersion: 4.3 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no offset etc.) reading of a substance. Units + after application of scale and offset are percents. + +What: /sys/bus/iio/devices/iio:deviceX/in_resistance_raw +What: /sys/bus/iio/devices/iio:deviceX/in_resistanceX_raw +What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw +What: /sys/bus/iio/devices/iio:deviceX/out_resistanceX_raw +KernelVersion: 4.3 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no offset etc.) resistance reading that can be processed + into an ohm value. + +What: /sys/bus/iio/devices/iio:deviceX/heater_enable +KernelVersion: 4.1.0 +Contact: linux-iio@vger.kernel.org +Description: + '1' (enable) or '0' (disable) specifying the enable + of heater function. Same reading values apply. + + This ABI is especially applicable for humidity sensors + to heatup the device and get rid of any condensation + in some humidity environment + +What: /sys/bus/iio/devices/iio:deviceX/in_ph_raw +KernelVersion: 4.5 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no offset etc.) pH reading of a substance as a negative + base-10 logarithm of hydrodium ions in a litre of water. + +What: /sys/bus/iio/devices/iio:deviceX/mount_matrix +What: /sys/bus/iio/devices/iio:deviceX/in_mount_matrix +What: /sys/bus/iio/devices/iio:deviceX/out_mount_matrix +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_mount_matrix +What: /sys/bus/iio/devices/iio:deviceX/in_accel_mount_matrix +KernelVersion: 4.6 +Contact: linux-iio@vger.kernel.org +Description: + Mounting matrix for IIO sensors. This is a rotation matrix which + informs userspace about sensor chip's placement relative to the + main hardware it is mounted on. + + Main hardware placement is defined according to the local + reference frame related to the physical quantity the sensor + measures. + + Given that the rotation matrix is defined in a board specific + way (platform data and / or device-tree), the main hardware + reference frame definition is left to the implementor's choice + (see below for a magnetometer example). + + Applications should apply this rotation matrix to samples so + that when main hardware reference frame is aligned onto local + reference frame, then sensor chip reference frame is also + perfectly aligned with it. + + Matrix is a 3x3 unitary matrix and typically looks like + [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix + [1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware + are perfectly aligned with each other. + + For example, a mounting matrix for a magnetometer sensor informs + userspace about sensor chip's ORIENTATION relative to the main + hardware. + + More specifically, main hardware orientation is defined with + respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where : + + * Y is in the ground plane and positive towards magnetic North ; + * X is in the ground plane, perpendicular to the North axis and + positive towards the East ; + * Z is perpendicular to the ground plane and positive upwards. + + An implementor might consider that for a hand-held device, a + 'natural' orientation would be 'front facing camera at the top'. + The main hardware reference frame could then be described as : + + * Y is in the plane of the screen and is positive towards the + top of the screen ; + * X is in the plane of the screen, perpendicular to Y axis, and + positive towards the right hand side of the screen ; + * Z is perpendicular to the screen plane and positive out of the + screen. + + Another example for a quadrotor UAV might be : + + * Y is in the plane of the propellers and positive towards the + front-view camera; + * X is in the plane of the propellers, perpendicular to Y axis, + and positive towards the starboard side of the UAV ; + * Z is perpendicular to propellers plane and positive upwards. + +What: /sys/bus/iio/devices/iio:deviceX/in_electricalconductivity_raw +KernelVersion: 4.8 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled no offset etc.) electric conductivity reading that + can be processed to siemens per meter. + +What: /sys/bus/iio/devices/iio:deviceX/in_countY_raw +KernelVersion: 4.10 +Contact: linux-iio@vger.kernel.org +Description: + This interface is deprecated; please use the Counter subsystem. + + Raw counter device counts from channel Y. For quadrature + counters, multiplication by an available [Y]_scale results in + the counts of a single quadrature signal phase from channel Y. + +What: /sys/bus/iio/devices/iio:deviceX/in_indexY_raw +KernelVersion: 4.10 +Contact: linux-iio@vger.kernel.org +Description: + This interface is deprecated; please use the Counter subsystem. + + Raw counter device index value from channel Y. This attribute + provides an absolute positional reference (e.g. a pulse once per + revolution) which may be used to home positional systems as + required. + +What: /sys/bus/iio/devices/iio:deviceX/in_count_count_direction_available +KernelVersion: 4.12 +Contact: linux-iio@vger.kernel.org +Description: + This interface is deprecated; please use the Counter subsystem. + + A list of possible counting directions which are: + + - "up" : counter device is increasing. + - "down": counter device is decreasing. + +What: /sys/bus/iio/devices/iio:deviceX/in_countY_count_direction +KernelVersion: 4.12 +Contact: linux-iio@vger.kernel.org +Description: + This interface is deprecated; please use the Counter subsystem. + + Raw counter device counters direction for channel Y. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_label +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_label +KernelVersion: 5.8 +Contact: linux-iio@vger.kernel.org +Description: + Optional symbolic label to a device channel. + If a label is defined for this channel add that to the channel + specific attributes. This is useful for userspace to be able to + better identify an individual channel. + +What: /sys/bus/iio/devices/iio:deviceX/in_phaseY_raw +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled) phase difference reading from channel Y + that can be processed to radians. + +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm1_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm1_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm2p5_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm2p5_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm4_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm4_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm10_input +What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm10_input +KernelVersion: 4.22 +Contact: linux-iio@vger.kernel.org +Description: + Mass concentration reading of particulate matter in ug / m3. + pmX consists of particles with aerodynamic diameter less or + equal to X micrometers. + +What: /sys/bus/iio/devices/iio:deviceX/events/in_illuminance_period_available +Date: November 2019 +KernelVersion: 5.4 +Contact: linux-iio@vger.kernel.org +Description: + List of valid periods (in seconds) for which the light intensity + must be above the threshold level before interrupt is asserted. + +What: /sys/bus/iio/devices/iio:deviceX/in_filter_notch_center_frequency +KernelVersion: 5.5 +Contact: linux-iio@vger.kernel.org +Description: + Center frequency in Hz for a notch filter. Used i.e. for line + noise suppression. + +What: /sys/bus/iio/devices/iio:deviceX/in_temp_thermocouple_type +KernelVersion: 5.5 +Contact: linux-iio@vger.kernel.org +Description: + One of the following thermocouple types: B, E, J, K, N, R, S, T. + +What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibambient +What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibambient +KernelVersion: 5.10 +Contact: linux-iio@vger.kernel.org +Description: + Calibrated ambient temperature for object temperature + calculation in milli degrees Celsius. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_raw +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_raw +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_raw +KernelVersion: 5.10 +Contact: linux-iio@vger.kernel.org +Description: + Unscaled light intensity according to CIE 1931/DIN 5033 color space. + Units after application of scale are nano nanowatts per square meter. + +What: /sys/bus/iio/devices/iio:deviceX/in_anglY_label +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Optional symbolic label for channel Y. + For Intel hid hinge sensor, the label values are: + hinge, keyboard, screen. It means the three channels + each correspond respectively to hinge angle, keyboard angle, + and screen angle. + +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_hysteresis_relative +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hysteresis_relative +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Specify the percent for light sensor relative to the channel + absolute value that a data field should change before an event + is generated. Units are a percentage of the prior reading. + +What: /sys/bus/iio/devices/iio:deviceX/calibration_auto_enable +Date: June 2020 +KernelVersion: 5.8 +Contact: linux-iio@vger.kernel.org +Description: + Some sensors have the ability to apply auto calibration at + runtime. For example, it may be necessary to compensate for + contaminant build-up in a measurement chamber or optical + element deterioration that would otherwise lead to sensor drift. + + Writing 1 or 0 to this attribute will respectively activate or + deactivate this auto calibration function. + + Upon reading, the current status is returned. + +What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value +Date: June 2020 +KernelVersion: 5.8 +Contact: linux-iio@vger.kernel.org +Description: + Some sensors have the ability to apply a manual calibration using + a known measurement value, perhaps obtained from an external + reference device. + + Writing a value to this function will force such a calibration + change. For the scd30 the value should be from the range + [400 1 2000]. + + Note for the scd30 that a valid value may only be obtained once + it is has been written. Until then any read back of this value + should be ignored. As for the scd4x an error will be returned + immediately if the manual calibration has failed. + +What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value_available +KernelVersion: 5.15 +Contact: linux-iio@vger.kernel.org +Description: + Available range for the forced calibration value, expressed as: + + - a range specified as "[min step max]" + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageX_sampling_frequency +What: /sys/bus/iio/devices/iio:deviceX/in_powerY_sampling_frequency +What: /sys/bus/iio/devices/iio:deviceX/in_currentZ_sampling_frequency +KernelVersion: 5.20 +Contact: linux-iio@vger.kernel.org +Description: + Some devices have separate controls of sampling frequency for + individual channels. If multiple channels are enabled in a scan, + then the sampling_frequency of the scan may be computed from the + per channel sampling frequencies. + +What: /sys/.../events/in_accel_gesture_singletap_en +What: /sys/.../events/in_accel_gesture_doubletap_en +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Device generates an event on a single or double tap. + +What: /sys/.../events/in_accel_gesture_singletap_value +What: /sys/.../events/in_accel_gesture_doubletap_value +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the threshold value that the device is comparing + against to generate the tap gesture event. The lower + threshold value increases the sensitivity of tap detection. + Units and the exact meaning of value are device-specific. + +What: /sys/.../events/in_accel_gesture_tap_value_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available threshold values which can be used to + modify the sensitivity of the tap detection. + +What: /sys/.../events/in_accel_gesture_singletap_reset_timeout +What: /sys/.../events/in_accel_gesture_doubletap_reset_timeout +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the timeout value in seconds for the tap detector + to not to look for another tap event after the event as + occurred. Basically the minimum quiet time between the two + single-tap's or two double-tap's. + +What: /sys/.../events/in_accel_gesture_tap_reset_timeout_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available tap reset timeout values. Units in seconds. + +What: /sys/.../events/in_accel_gesture_doubletap_tap2_min_delay +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the minimum quiet time in seconds between the two + taps of a double tap. + +What: /sys/.../events/in_accel_gesture_doubletap_tap2_min_delay_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available delay values between two taps in the double + tap. Units in seconds. + +What: /sys/.../events/in_accel_gesture_tap_maxtomin_time +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the maximum time difference allowed between upper + and lower peak of tap to consider it as the valid tap event. + Units in seconds. + +What: /sys/.../events/in_accel_gesture_tap_maxtomin_time_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Lists all available time values between upper peak to lower + peak. Units in seconds. + +What: /sys/bus/iio/devices/iio:deviceX/in_rot_yaw_raw +What: /sys/bus/iio/devices/iio:deviceX/in_rot_pitch_raw +What: /sys/bus/iio/devices/iio:deviceX/in_rot_roll_raw +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled) euler angles readings. Units after + application of scale are deg. + +What: /sys/bus/iio/devices/iio:deviceX/serialnumber +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + An example format is 16-bytes, 2-digits-per-byte, HEX-string + representing the sensor unique ID number. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 b/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 new file mode 100644 index 000000000..47e34f865 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 @@ -0,0 +1,7 @@ +What: /sys/bus/iio/devices/triggerX/name = "adxl372-devX-peak" +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + The adxl372 accelerometer kernel module provides an additional trigger, + which sets the device in a mode in which it will record only the peak acceleration + sensed over the set period of time in the events sysfs. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 b/Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 new file mode 100644 index 000000000..99847a913 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 @@ -0,0 +1,7 @@ +What: /sys/bus/iio/devices/triggerX/name = "bmc150_accel-any-motion-devX" +KernelVersion: 3.17 +Contact: linux-iio@vger.kernel.org +Description: + The BMC150 accelerometer kernel module provides an additional trigger, + which sets driver in a mode, where data is pushed to the buffer + only when there is any motion. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192 b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192 new file mode 100644 index 000000000..f8315202c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7192 @@ -0,0 +1,51 @@ +What: /sys/bus/iio/devices/iio:deviceX/ac_excitation_en +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + This attribute, if available, is used to enable the AC + excitation mode found on some converters. In ac excitation mode, + the polarity of the excitation voltage is reversed on + alternate cycles, to eliminate DC errors. + +What: /sys/bus/iio/devices/iio:deviceX/bridge_switch_en +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + This attribute, if available, is used to close or open the + bridge power down switch found on some converters. + In bridge applications, such as strain gauges and load cells, + the bridge itself consumes the majority of the current in the + system. To minimize the current consumption of the system, + the bridge can be disconnected (when it is not being used + using the bridge_switch_en attribute. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltagex_sys_calibration +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Initiates the system calibration procedure. This is done on a + single channel at a time. Write '1' to start the calibration. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage2-voltage2_shorted_raw +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Measure voltage from AIN2 pin connected to AIN(+) + and AIN(-) shorted. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltagex_sys_calibration_mode_available +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Reading returns a list with the possible calibration modes. + There are two available options: + "zero_scale" - calibrate to zero scale + "full_scale" - calibrate to full scale + +What: /sys/bus/iio/devices/iio:deviceX/in_voltagex_sys_calibration_mode +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Sets up the calibration mode used in the system calibration + procedure. Reading returns the current calibration mode. + Writing sets the system calibration mode. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a new file mode 100644 index 000000000..83b7efe6a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a @@ -0,0 +1,13 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_balance_switch_en +KernelVersion: 5.14 +Contact: linux-iio@vger.kernel.org +Description: + Used to enable an output for balancing cells for time + controlled via in_voltage_Y-voltageZ_balance_switch_timer. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_balance_switch_timer +KernelVersion: 5.14 +Contact: linux-iio@vger.kernel.org +Description: + Time in seconds for which balance switch will be turned on. + Multiple of 71.5 seconds. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector b/Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector new file mode 100644 index 000000000..1c2a07f7a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector @@ -0,0 +1,39 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_invert +Date: October 2016 +KernelVersion: 4.9 +Contact: Peter Rosin +Description: + The DAC is used to find the peak level of an alternating + voltage input signal by a binary search using the output + of a comparator wired to an interrupt pin. Like so:: + + _ + | \ + input +------>-------|+ \ + | \ + .-------. | }---. + | | | / | + | dac|-->--|- / | + | | |_/ | + | | | + | | | + | irq|------<-------' + | | + '-------' + + The boolean invert attribute (0/1) should be set when the + input signal is centered around the maximum value of the + dac instead of zero. The envelope detector will search + from below in this case and will also invert the result. + + The edge/level of the interrupt is also switched to its + opposite value. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_compare_interval +Date: October 2016 +KernelVersion: 4.9 +Contact: Peter Rosin +Description: + Number of milliseconds to wait for the comparator in each + step of the binary search for the input peak level. Needs + to relate to the frequency of the input signal. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 b/Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 new file mode 100644 index 000000000..4b01150af --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435 @@ -0,0 +1,48 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_sensing_mode +Date: August 2015 +KernelVersion: 4.2.0 +Contact: source@cogentembedded.com +Description: + Program sensor type for threshold detector inputs. + Could be either "GND-Open" or "Supply-Open" mode. Y is a + threshold detector input channel. Channels 0..7, 8..15, 16..23 + and 24..31 has common sensor types. + +What: /sys/bus/iio/devices/iio:deviceX/events/in_voltageY_thresh_falling_value +Date: August 2015 +KernelVersion: 4.2.0 +Contact: source@cogentembedded.com +Description: + Channel Y low voltage threshold. If sensor input voltage goes lower then + this value then the threshold falling event is pushed. + Depending on in_voltageY_sensing_mode the low voltage threshold + is separately set for "GND-Open" and "Supply-Open" modes. + Channels 0..31 have common low threshold values, but could have different + sensing_modes. + + The low voltage threshold range is between 2..21V. + Hysteresis between low and high thresholds can not be lower then 2 and + can not be odd. + + If falling threshold results hysteresis to odd value then rising + threshold is automatically subtracted by one. + +What: /sys/bus/iio/devices/iio:deviceX/events/in_voltageY_thresh_rising_value +Date: August 2015 +KernelVersion: 4.2.0 +Contact: source@cogentembedded.com +Description: + Channel Y high voltage threshold. If sensor input voltage goes higher then + this value then the threshold rising event is pushed. + Depending on in_voltageY_sensing_mode the high voltage threshold + is separately set for "GND-Open" and "Supply-Open" modes. + + Channels 0..31 have common high threshold values, but could have different + sensing_modes. + + The high voltage threshold range is between 3..22V. + Hysteresis between low and high thresholds can not be lower then 2 and + can not be odd. + + If rising threshold results hysteresis to odd value then falling + threshold is automatically appended by one. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-max9611 b/Documentation/ABI/testing/sysfs-bus-iio-adc-max9611 new file mode 100644 index 000000000..6d2d2b094 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-max9611 @@ -0,0 +1,17 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_power_shunt_resistor +Date: March 2017 +KernelVersion: 4.12 +Contact: linux-iio@vger.kernel.org +Description: The value of the shunt resistor used to compute power drain on + common input voltage pin (RS+). In Ohms. + +What: /sys/bus/iio/devices/iio:deviceX/in_current_shunt_resistor +Date: March 2017 +KernelVersion: 4.12 +Contact: linux-iio@vger.kernel.org +Description: The value of the shunt resistor used to compute current flowing + between RS+ and RS- voltage sense inputs. In Ohms. + +These attributes describe a single physical component, exposed as two distinct +attributes as it is used to calculate two different values: power load and +current flowing between RS+ and RS- inputs. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 b/Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 new file mode 100644 index 000000000..e5a7b1c7c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 @@ -0,0 +1,78 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_voltage0_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 USBID ADC which connected to connector ID pin. + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage1_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 VBUS ADC with lower accuracy(+-75mA) + higher measure range(1~22mV) + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage2_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 VBUS ADC with higher accuracy(+-30mA) + lower measure range(1~9.76V) + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage3_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 VSYS ADC + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage4_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 VBAT ADC + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_current5_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 IBUS ADC + Calculating with scale and offset returns voltage in uA + +What: /sys/bus/iio/devices/iio:deviceX/in_current6_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 IBAT ADC + Calculating with scale and offset returns voltage in uA + +What: /sys/bus/iio/devices/iio:deviceX/in_current7_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 CHG_VDDP ADC + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_temp8_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 IC junction temperature + Calculating with scale and offset returns temperature in degree + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage9_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 VREF_TS ADC + Calculating with scale and offset returns voltage in uV + +What: /sys/bus/iio/devices/iio:deviceX/in_voltage10_raw +KernelVersion: 5.8.0 +Contact: gene_chen@richtek.com +Description: + Indicated MT6360 TS ADC + Calculating with scale and offset returns voltage in uV diff --git a/Documentation/ABI/testing/sysfs-bus-iio-adc-stm32 b/Documentation/ABI/testing/sysfs-bus-iio-adc-stm32 new file mode 100644 index 000000000..1975c7a1a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-stm32 @@ -0,0 +1,21 @@ +What: /sys/bus/iio/devices/triggerX/trigger_polarity +KernelVersion: 4.11 +Contact: fabrice.gasnier@st.com +Description: + The STM32 ADC can be configured to use external trigger sources + (e.g. timers, pwm or exti gpio). Then, it can be tuned to start + conversions on external trigger by either: + + - "rising-edge" + - "falling-edge" + - "both-edges". + + Reading returns current trigger polarity. + + Writing value before enabling conversions sets trigger polarity. + +What: /sys/bus/iio/devices/triggerX/trigger_polarity_available +KernelVersion: 4.11 +Contact: fabrice.gasnier@st.com +Description: + List all available trigger_polarity settings. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-bno055 b/Documentation/ABI/testing/sysfs-bus-iio-bno055 new file mode 100644 index 000000000..f32b1644e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-bno055 @@ -0,0 +1,81 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_accel_raw_range +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Raw (unscaled) range for acceleration readings. Unit after + application of scale is m/s^2. Note that this doesn't affects + the scale (which should be used when changing the maximum and + minimum readable value affects also the reading scaling factor). + +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_raw_range +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Range for angular velocity readings in radians per second. Note + that this does not affects the scale (which should be used when + changing the maximum and minimum readable value affects also the + reading scaling factor). + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_raw_range_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + List of allowed values for in_accel_raw_range attribute + +What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_raw_range_available +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + List of allowed values for in_anglvel_raw_range attribute + +What: /sys/bus/iio/devices/iio:deviceX/in_magn_calibration_fast_enable +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Can be 1 or 0. Enables/disables the "Fast Magnetometer + Calibration" HW function. + +What: /sys/bus/iio/devices/iio:deviceX/fusion_enable +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Can be 1 or 0. Enables/disables the "sensor fusion" (a.k.a. + NDOF) HW function. + +What: /sys/bus/iio/devices/iio:deviceX/calibration_data +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Reports the binary calibration data blob for the IMU sensors. + +What: /sys/bus/iio/devices/iio:deviceX/in_accel_calibration_auto_status +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Reports the autocalibration status for the accelerometer sensor. + Can be 0 (calibration non even enabled) or 1 to 5 where the greater + the number, the better the calibration status. + +What: /sys/bus/iio/devices/iio:deviceX/in_gyro_calibration_auto_status +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Reports the autocalibration status for the gyroscope sensor. + Can be 0 (calibration non even enabled) or 1 to 5 where the greater + the number, the better the calibration status. + +What: /sys/bus/iio/devices/iio:deviceX/in_magn_calibration_auto_status +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Reports the autocalibration status for the magnetometer sensor. + Can be 0 (calibration non even enabled) or 1 to 5 where the greater + the number, the better the calibration status. + +What: /sys/bus/iio/devices/iio:deviceX/sys_calibration_auto_status +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Reports the status for the IMU overall autocalibration. + Can be 0 (calibration non even enabled) or 1 to 5 where the greater + the number, the better the calibration status. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746 b/Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746 new file mode 100644 index 000000000..02ca8941d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746 @@ -0,0 +1,11 @@ +What: /sys/.../iio:deviceX/in_capacitableY_calibbias_calibration +What: /sys/.../iio:deviceX/in_capacitableY_calibscale_calibration +KernelVersion: 6.1 +Contact: linux-iio@vger.kernel.org +Description: + Write 1 to trigger a calibration of the calibbias or + calibscale. For calibscale, a full scale capacitance should + be connected to the capacitance input and a + calibscale_calibration then started. For calibbias see + the device datasheet section on "capacitive system offset + calibration". diff --git a/Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40 b/Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40 new file mode 100644 index 000000000..469a7c00f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40 @@ -0,0 +1,31 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_temp_raw +Date: August 2021 +KernelVersion: 5.15 +Contact: Andreas Klinger +Description: + Set the temperature. This value is sent to the sensor for + temperature compensation. + Default value: 25000 (25 °C) + +What: /sys/bus/iio/devices/iio:deviceX/out_humidityrelative_raw +Date: August 2021 +KernelVersion: 5.15 +Contact: Andreas Klinger +Description: + Set the relative humidity. This value is sent to the sensor for + humidity compensation. + Default value: 50000 (50 % relative humidity) + +What: /sys/bus/iio/devices/iio:deviceX/in_resistance_calibbias +Date: August 2021 +KernelVersion: 5.15 +Contact: Andreas Klinger +Description: + Set the bias value for the resistance which is used for + calculation of in_concentration_input as follows: + + x = (in_resistance_raw - in_resistance_calibbias) * 0.65 + + in_concentration_input = 500 / (1 + e^x) + + Default value: 30000 diff --git a/Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2 b/Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2 new file mode 100644 index 000000000..ee7aeb117 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2 @@ -0,0 +1,38 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_factory +Date: August 2021 +KernelVersion: 5.16 +Contact: Jacopo Mondi +Description: + Writing '1' triggers a 'Factory' calibration cycle. + +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_background +Date: August 2021 +KernelVersion: 5.16 +Contact: Jacopo Mondi +Description: + Writing '1' triggers a 'Background' calibration cycle. + +What: /sys/bus/iio/devices/iio:deviceX/error_status_available +Date: August 2021 +KernelVersion: 5.16 +Contact: Jacopo Mondi +Description: + Reading returns the list of possible chip error status. + Available options are: + - 'error_fatal': Analog front-end initialization error + - 'error_i2c': Read/write to non-existing register + - 'error_algorithm': Corrupted parameters + - 'error_calibration': Calibration has failed + - 'error_self_diagnostic': Internal interface failure + - 'error_out_of_range': Measured concentration out of scale + - 'error_memory': Error during memory operations + - 'error_no_measurement': Cleared at first measurement + - 'error_low_voltage': Sensor regulated voltage too low + - 'error_measurement_timeout': Unable to complete measurement + +What: /sys/bus/iio/devices/iio:deviceX/error_status +Date: August 2021 +KernelVersion: 5.16 +Contact: Jacopo Mondi +Description: + Reading returns the current chip error status. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x b/Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x new file mode 100644 index 000000000..d512f8656 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x @@ -0,0 +1,7 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_concentration_VOC_short_raw +Date: September 2015 +KernelVersion: 4.3 +Contact: Matt Ranostay +Description: + Get the raw calibration VOC value from the sensor. + This value has little application outside of calibration. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-cros-ec b/Documentation/ABI/testing/sysfs-bus-iio-cros-ec new file mode 100644 index 000000000..adf24c401 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-cros-ec @@ -0,0 +1,28 @@ +What: /sys/bus/iio/devices/iio:deviceX/calibrate +Date: July 2015 +KernelVersion: 4.7 +Contact: linux-iio@vger.kernel.org +Description: + Writing '1' will perform a FOC (Fast Online Calibration). The + corresponding calibration offsets can be read from `*_calibbias` + entries. + +What: /sys/bus/iio/devices/iio:deviceX/location +Date: July 2015 +KernelVersion: 4.7 +Contact: linux-iio@vger.kernel.org +Description: + This attribute returns a string with the physical location where + the motion sensor is placed. For example, in a laptop a motion + sensor can be located on the base or on the lid. Current valid + values are 'base' and 'lid'. + +What: /sys/bus/iio/devices/iio:deviceX/id +Date: September 2017 +KernelVersion: 4.14 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is exposed by the CrOS EC sensors driver and + represents the sensor ID as exposed by the EC. This ID is used + by the Android sensor service hardware abstraction layer (sensor + HAL) through the Android container on ChromeOS. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 b/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 new file mode 100644 index 000000000..7fbcba15b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 @@ -0,0 +1,31 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_enable +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Dither enable. Write 1 to enable dither or 0 to disable it. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_invert +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Inverts the dither applied to the selected DAC channel. Dither is not + inverted by default. Write "1" to invert dither. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale_available +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Returns possible scalings available for the current channel. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Scales the dither before it is applied to the selected channel. + +What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_source +KernelVersion: 5.12 +Contact: linux-iio@vger.kernel.org +Description: + Selects dither source applied to the selected channel. Write "0" to + select N0 source, write "1" to select N1 source. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac b/Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac new file mode 100644 index 000000000..580e93f37 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac @@ -0,0 +1,8 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw_available +Date: October 2016 +KernelVersion: 4.9 +Contact: Peter Rosin +Description: + The range of available values represented as the minimum value, + the step and the maximum value, all enclosed in square brackets. + Example: [0 1 256] diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688 b/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688 new file mode 100644 index 000000000..1c3597127 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688 @@ -0,0 +1,86 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_en +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Dither enable. Write 1 to enable dither or 0 to disable it. This is useful + for changing the dither parameters. They way it should be done is: + + - disable dither operation; + - change dither parameters (eg: frequency, phase...); + - enabled dither operation + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + This raw, unscaled value refers to the dither signal amplitude. + The same scale as in out_voltageY_raw applies. However, the + offset might be different as it's always 0 for this attribute. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw_available +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Available range for dither raw amplitude values. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_offset +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Offset applied to out_voltageY_dither_raw. Read only attribute + always set to 0. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Sets the dither signal frequency. Units are in Hz. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency_available +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Returns the available values for the dither frequency. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Sets the dither signal phase. Units are in Radians. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase_available +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Returns the available values for the dither phase. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_toggle_en +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Toggle enable. Write 1 to enable toggle or 0 to disable it. This is + useful when one wants to change the DAC output codes. The way it should + be done is: + + - disable toggle operation; + - change out_voltageY_raw0 and out_voltageY_raw1; + - enable toggle operation. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw0 +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw1 +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + It has the same meaning as out_voltageY_raw. This attribute is + specific to toggle enabled channels and refers to the DAC output + code in INPUT_A (_raw0) and INPUT_B (_raw1). The same scale and offset + as in out_voltageY_raw applies. + +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_symbol +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Performs a SW toggle. This attribute is specific to toggle + enabled channels and allows to toggle between out_voltageY_raw0 + and out_voltageY_raw1 through software. Writing 0 will select + out_voltageY_raw0 while 1 selects out_voltageY_raw1. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 b/Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 new file mode 100644 index 000000000..91439d6d6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 @@ -0,0 +1,22 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_voltage_spi_clk_freq +KernelVersion: 4.14 +Contact: arnaud.pouliquen@st.com +Description: + For audio purpose only. + + Used by audio driver to set/get the spi input frequency. + + This is mandatory if DFSDM is slave on SPI bus, to + provide information on the SPI clock frequency during runtime + Notice that the SPI frequency should be a multiple of sample + frequency to ensure the precision. + + if DFSDM input is SPI master: + + Reading SPI clkout frequency, + error on writing + + If DFSDM input is SPI Slave: + + Reading returns value previously set. + Writing value before starting conversions. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08 b/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08 new file mode 100644 index 000000000..9dae94aa8 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-distance-srf08 @@ -0,0 +1,17 @@ +What: /sys/bus/iio/devices/iio:deviceX/sensor_max_range +Date: January 2017 +KernelVersion: 4.11 +Contact: linux-iio@vger.kernel.org +Description: + Show or set the maximum range between the sensor and the + first object echoed in meters. Default value is 6.020. + This setting limits the time the driver is waiting for a + echo. + + Showing the range of available values is represented as the + minimum value, the step and the maximum value, all enclosed + in square brackets. + + Example:: + + [0.043 0.043 11.008] diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dma-buffer b/Documentation/ABI/testing/sysfs-bus-iio-dma-buffer new file mode 100644 index 000000000..d526e6571 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-dma-buffer @@ -0,0 +1,19 @@ +What: /sys/bus/iio/devices/iio:deviceX/buffer/length_align_bytes +KernelVersion: 5.4 +Contact: linux-iio@vger.kernel.org +Description: + DMA buffers tend to have a alignment requirement for the + buffers. If this alignment requirement is not met samples might + be dropped from the buffer. + + This property reports the alignment requirements in bytes. + This means that the buffer size in bytes needs to be a integer + multiple of the number reported by this file. + + The alignment requirements in number of sample sets will depend + on the enabled channels and the bytes per channel. This means + that the alignment requirement in samples sets might change + depending on which and how many channels are enabled. Whereas + the alignment requirement reported in bytes by this property + will remain static and does not depend on which channels are + enabled. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818 b/Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818 new file mode 100644 index 000000000..f6c035752 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818 @@ -0,0 +1,16 @@ +What: /sys/bus/iio/devices/iio:deviceX/filter_mode_available +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Reading this returns the valid values that can be written to the + on_altvoltage0_mode attribute: + + - auto -> Adjust bandpass filter to track changes in input clock rate. + - manual -> disable/unregister the clock rate notifier / input clock tracking. + +What: /sys/bus/iio/devices/iio:deviceX/filter_mode +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + This attribute configures the filter mode. + Reading returns the actual mode. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 new file mode 100644 index 000000000..d065cda7d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 @@ -0,0 +1,31 @@ +What: /sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present +What: /sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present +What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present +What: /sys/bus/iio/devices/iio:deviceX/vcxo_clk_present +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Reading returns either '1' or '0'. + + '1' means that the clock in question is present. + + '0' means that the clock is missing. + +What: /sys/bus/iio/devices/iio:deviceX/pllY_locked +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Reading returns either '1' or '0'. '1' means that the + pllY is locked. + +What: /sys/bus/iio/devices/iio:deviceX/sync_dividers +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Writing '1' triggers the clock distribution synchronization + functionality. All dividers are reset and the channels start + with their predefined phase offsets (out_altvoltageY_phase). + Writing this file has the effect as driving the external + /SYNC pin low. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 new file mode 100644 index 000000000..1254457a7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 @@ -0,0 +1,21 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Stores channel Y frequency resolution/channel spacing in Hz. + The value given directly influences the MODULUS used by + the fractional-N PLL. It is assumed that the algorithm + that is used to compute the various dividers, is able to + generate proper values for multiples of channel spacing. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + Sets channel Y REFin frequency in Hz. In some clock chained + applications, the reference frequency used by the PLL may + change during runtime. This attribute allows the user to + adjust the reference frequency accordingly. + The value written has no effect until out_altvoltageY_frequency + is updated. Consider to use out_altvoltageY_powerdown to power + down the PLL and its RFOut buffers during REFin changes. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371 new file mode 100644 index 000000000..7fe6935d1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371 @@ -0,0 +1,11 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_name +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Reading returns the datasheet name for channel Y:: + + out_altvoltage0_name: RF8x + out_altvoltage1_name: RFAUX8x + out_altvoltage2_name: RF16x + out_altvoltage3_name: RF32x + diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013 new file mode 100644 index 000000000..de1e323e5 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013 @@ -0,0 +1,38 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0-1_i_calibphase +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write unscaled value for the Local Oscillatior path quadrature I phase shift. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0-1_q_calibphase +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write unscaled value for the Local Oscillatior path quadrature Q phase shift. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibbias +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the Local Oscillatior Feedthrough Offset Calibration I Positive + side. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibbias +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage1_i_calibbias +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write raw value for the Local Oscillatior Feedthrough Offset Calibration I Negative + side. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage1_q_calibbias +KernelVersion: +Contact: linux-iio@vger.kernel.org +Description: + Read/write raw value for the Local Oscillatior Feedthrough Offset Calibration Q Negative + side. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014 new file mode 100644 index 000000000..395010a0e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014 @@ -0,0 +1,23 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibscale_coarse +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the digital attenuator gain (IF_I) with coarse steps. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibscale_coarse +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the digital attenuator gain (IF_Q) with coarse steps. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibscale_fine +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the digital attenuator gain (IF_I) with fine steps. + +What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibscale_fine +KernelVersion: 5.18 +Contact: linux-iio@vger.kernel.org +Description: + Read/write value for the digital attenuator gain (IF_Q) with fine steps. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 b/Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 new file mode 100644 index 000000000..e98209c91 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 @@ -0,0 +1,7 @@ +What: /sys/bus/iio/devices/triggerX/name = "bmg160-any-motion-devX" +KernelVersion: 3.17 +Contact: linux-iio@vger.kernel.org +Description: + The BMG160 gyro kernel module provides an additional trigger, + which sets driver in a mode, where data is pushed to the buffer + only when there is any motion. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-health-afe440x b/Documentation/ABI/testing/sysfs-bus-iio-health-afe440x new file mode 100644 index 000000000..a8e04b41d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-health-afe440x @@ -0,0 +1,39 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_raw +Date: May 2016 +KernelVersion: +Contact: Andrew F. Davis +Description: + Get measured values from the ADC for these stages. Y is the + specific stage number corresponding to datasheet stage names + as follows: + + == ========== + 1 LED2 + 2 ALED2/LED3 + 3 LED1 + 4 ALED1/LED4 + == ========== + + Note that channels 5 and 6 represent LED2-ALED2 and LED1-ALED1 + respectively which simply helper channels containing the + calculated difference in the value of stage 1 - 2 and 3 - 4. + The values are expressed in 24-bit twos complement. + The LED current for the stage is controlled via + out_currentY_raw. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_offset +Date: May 2016 +KernelVersion: +Contact: Andrew F. Davis +Description: + Get and set the offset cancellation DAC setting for these + stages. The values are expressed in 5-bit sign-magnitude. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_resistance +What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_capacitance +Date: May 2016 +KernelVersion: +Contact: Andrew F. Davis +Description: + Get and set the resistance and the capacitance settings for the + Transimpedance Amplifier during the associated stage. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-humidity b/Documentation/ABI/testing/sysfs-bus-iio-humidity new file mode 100644 index 000000000..cb0d7e75d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-humidity @@ -0,0 +1,10 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw +What: /sys/bus/iio/devices/iio:deviceX/out_current_heater_raw_available +KernelVersion: 5.3.8 +Contact: linux-iio@vger.kernel.org +Description: + Controls the heater device within the humidity sensor to get + rid of excess condensation. + + In some devices, this is just a switch in which case 0 = OFF, + and 1 = ON. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-impedance-analyzer-ad5933 b/Documentation/ABI/testing/sysfs-bus-iio-impedance-analyzer-ad5933 new file mode 100644 index 000000000..0e86747c6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-impedance-analyzer-ad5933 @@ -0,0 +1,35 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_start +Date: March 2019 +KernelVersion: 3.1.0 +Contact: linux-iio@vger.kernel.org +Description: + Frequency sweep start frequency in Hz. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_increment +Date: March 2019 +KernelVersion: 3.1.0 +Contact: linux-iio@vger.kernel.org +Description: + Frequency increment in Hz (step size) between consecutive + frequency points along the sweep. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_points +Date: March 2019 +KernelVersion: 3.1.0 +Contact: linux-iio@vger.kernel.org +Description: + Number of frequency points (steps) in the frequency sweep. + This value, in conjunction with the + out_altvoltageY_frequency_start and the + out_altvoltageY_frequency_increment, determines the frequency + sweep range for the sweep operation. + +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_settling_cycles +Date: March 2019 +KernelVersion: 3.1.0 +Contact: linux-iio@vger.kernel.org +Description: + Number of output excitation cycles (settling time cycles) + that are allowed to pass through the unknown impedance, + after each frequency increment, and before the ADC is triggered + to perform a conversion sequence of the response signal. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc b/Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc new file mode 100644 index 000000000..8916f7ec6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc @@ -0,0 +1,24 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_allow_async_readout +Date: December 2015 +KernelVersion: 4.4 +Contact: linux-iio@vger.kernel.org +Description: + By default (value '0'), the capture thread checks for the Conversion + Ready Flag to being set prior to committing a new value to the sample + buffer. This synchronizes the in-chip conversion rate with the + in-driver readout rate at the cost of an additional register read. + + Writing '1' will remove the polling for the Conversion Ready Flags to + save the additional i2c transaction, which will improve the bandwidth + available for reading data. However, samples can be occasionally skipped + or repeated, depending on the beat between the capture and conversion + rates. + +What: /sys/bus/iio/devices/iio:deviceX/in_shunt_resistor +Date: December 2015 +KernelVersion: 4.4 +Contact: linux-iio@vger.kernel.org +Description: + The value of the shunt resistor may be known only at runtime fom an + eeprom content read by a client application. This attribute allows to + set its value in ohms. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-isl29501 b/Documentation/ABI/testing/sysfs-bus-iio-isl29501 new file mode 100644 index 000000000..d009cfbbd --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-isl29501 @@ -0,0 +1,47 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_agc_gain +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_agc_gain_bias +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + This sensor has an automatic gain control (agc) loop + which sets the analog signal levels at an optimum + level by controlling programmable gain amplifiers. The + criteria for optimal gain is determined by the sensor. + + Return the actual gain value as an integer in [0; 65536] + range when read from. + + The agc gain read when measuring crosstalk shall be + written into in_proximity0_agc_gain_bias. + +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calib_phase_temp_a +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calib_phase_temp_b +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calib_phase_light_a +What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calib_phase_light_b +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + The sensor is able to perform correction of distance + measurements due to changing temperature and ambient + light conditions. It can be programmed to correct for + a second order error polynomial. + + Phase data has to be collected when temperature and + ambient light are modulated independently. + + Then a least squares curve fit to a second order + polynomial has to be generated from the data. The + resultant curves have the form ax^2 + bx + c. + + From those two curves, a and b coefficients shall be + stored in in_proximity0_calib_phase_temp_a and + in_proximity0_calib_phase_temp_b for temperature and + in in_proximity0_calib_phase_light_a and + in_proximity0_calib_phase_light_b for ambient light. + + Those values must be integer in [0; 8355840] range. + + Finally, the c constant is set by the sensor + internally. + + The value stored in sensor is displayed when read from. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-isl29018 b/Documentation/ABI/testing/sysfs-bus-iio-light-isl29018 new file mode 100644 index 000000000..220206a20 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-isl29018 @@ -0,0 +1,21 @@ +What: /sys/bus/iio/devices/iio:deviceX/proximity_on_chip_ambient_infrared_suppression +Date: January 2011 +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + From ISL29018 Data Sheet (FN6619.4, Oct 8, 2012) regarding the + infrared suppression: + + Scheme 0, makes full n (4, 8, 12, 16) bits (unsigned) proximity + detection. The range of Scheme 0 proximity count is from 0 to + 2^n. Logic 1 of this bit, Scheme 1, makes n-1 (3, 7, 11, 15) + bits (2's complementary) proximity_less_ambient detection. The + range of Scheme 1 proximity count is from -2^(n-1) to 2^(n-1). + The sign bit is extended for resolutions less than 16. While + Scheme 0 has wider dynamic range, Scheme 1 proximity detection + is less affected by the ambient IR noise variation. + + == ============================================= + 0 Sensing IR from LED and ambient + 1 Sensing IR from LED with ambient IR rejection + == ============================================= diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als new file mode 100644 index 000000000..c476d48d0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als @@ -0,0 +1,56 @@ +What: /sys/.../events/in_illuminance0_thresh_either_en +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Event generated when channel passes one of the four thresholds + in each direction (rising|falling) and a zone change occurs. + The corresponding light zone can be read from + in_illuminance0_zone. + +What: /sys/.../events/in_illuminance0_threshY_hysteresis +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Get the hysteresis for thresholds Y, that is, + threshY_hysteresis = threshY_raising - threshY_falling + +What: /sys/.../events/illuminance_threshY_falling_value +What: /sys/.../events/illuminance_threshY_raising_value +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Specifies the value of threshold that the device is comparing + against for the events enabled by + in_illuminance0_thresh_either_en (0..255), where Y in 0..3. + + Note that threshY_falling must be less than or equal to + threshY_raising. + + These thresholds correspond to the eight zone-boundary + registers (boundaryY_{low,high}) and define the five light + zones. + +What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Get the current light zone (0..4) as defined by the + in_illuminance0_threshY_{falling,rising} thresholds. + +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_currentZ_raw +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the output current for channel out_currentY when in zone + Z (0..255), where Y in 0..2 and Z in 0..4. + + These values correspond to the ALS-mapper target registers for + ALS-mapper Y + 1. + + Note that out_currentY_raw provides the current for the + current zone. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-si1133 b/Documentation/ABI/testing/sysfs-bus-iio-light-si1133 new file mode 100644 index 000000000..6f130cdb2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-si1133 @@ -0,0 +1,22 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_ir_small_raw +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + Unit-less infrared intensity. The intensity is measured from 1 + dark photodiode. "small" indicate the surface area capturing + infrared. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_ir_large_raw +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + Unit-less infrared intensity. The intensity is measured from 4 + dark photodiodes. "large" indicate the surface area capturing + infrared. + +What: /sys/bus/iio/devices/iio:deviceX/in_intensity_large_raw +KernelVersion: 4.18 +Contact: linux-iio@vger.kernel.org +Description: + Unit-less light intensity with more diodes. + diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2583 b/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2583 new file mode 100644 index 000000000..a2e19964e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2583 @@ -0,0 +1,20 @@ +What: /sys/bus/iio/devices/device[n]/in_illuminance_calibrate +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + This property causes an internal calibration of the als gain trim + value which is later used in calculating illuminance in lux. + +What: /sys/bus/iio/devices/device[n]/in_illuminance_lux_table +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + This property gets/sets the table of coefficients + used in calculating illuminance in lux. + +What: /sys/bus/iio/devices/device[n]/in_illuminance_input_target +KernelVersion: 2.6.37 +Contact: linux-iio@vger.kernel.org +Description: + This property is the known externally illuminance (in lux). + It is used in the process of calibrating the device accuracy. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2772 b/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2772 new file mode 100644 index 000000000..b2798b258 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-tsl2772 @@ -0,0 +1,13 @@ +What: /sys/bus/iio/devices/device[n]/in_illuminance0_calibrate +KernelVersion: 3.3-rc1 +Contact: linux-iio@vger.kernel.org +Description: + Causes an internal calibration of the als gain trim + value which is later used in calculating illuminance in lux. + +What: /sys/bus/iio/devices/device[n]/in_proximity0_calibrate +KernelVersion: 3.3-rc1 +Contact: linux-iio@vger.kernel.org +Description: + Causes a recalculation and adjustment to the + proximity_thresh_rising_value. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-magnetometer-hmc5843 b/Documentation/ABI/testing/sysfs-bus-iio-magnetometer-hmc5843 new file mode 100644 index 000000000..13f099ef6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-magnetometer-hmc5843 @@ -0,0 +1,20 @@ +What: /sys/bus/iio/devices/iio:deviceX/meas_conf +What: /sys/bus/iio/devices/iio:deviceX/meas_conf_available +KernelVersion: 4.5 +Contact: linux-iio@vger.kernel.org +Description: + Current configuration and available configurations + for the bias current. + + ============ ============================================ + normal Normal measurement configurations (default) + positivebias Positive bias configuration + negativebias Negative bias configuration + disabled Only available on HMC5983. Disables magnetic + sensor and enables temperature sensor. + ============ ============================================ + + Note: + The effect of this configuration may vary + according to the device. For exact documentation + check the device's datasheet. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-meas-spec b/Documentation/ABI/testing/sysfs-bus-iio-meas-spec new file mode 100644 index 000000000..6d47e548e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-meas-spec @@ -0,0 +1,7 @@ +What: /sys/bus/iio/devices/iio:deviceX/battery_low +KernelVersion: 4.1.0 +Contact: linux-iio@vger.kernel.org +Description: + Reading returns either '1' or '0'. '1' means that the + battery level supplied to sensor is below 2.25V. + This ABI is available for tsys02d, htu21, ms8607 diff --git a/Documentation/ABI/testing/sysfs-bus-iio-mpu6050 b/Documentation/ABI/testing/sysfs-bus-iio-mpu6050 new file mode 100644 index 000000000..cb53737aa --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-mpu6050 @@ -0,0 +1,13 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_gyro_matrix +What: /sys/bus/iio/devices/iio:deviceX/in_accel_matrix +What: /sys/bus/iio/devices/iio:deviceX/in_magn_matrix +KernelVersion: 3.4.0 +Contact: linux-iio@vger.kernel.org +Description: + This is mounting matrix for motion sensors. Mounting matrix + is a 3x3 unitary matrix. A typical mounting matrix would look like + [0, 1, 0; 1, 0, 0; 0, 0, -1]. Using this information, it would be + easy to tell the relative positions among sensors as well as their + positions relative to the board that holds these sensors. Identity matrix + [1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and device are perfectly + aligned with each other. All axes are exactly the same. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-potentiometer-mcp4531 b/Documentation/ABI/testing/sysfs-bus-iio-potentiometer-mcp4531 new file mode 100644 index 000000000..2a91fbe39 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-potentiometer-mcp4531 @@ -0,0 +1,8 @@ +What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw_available +Date: October 2016 +KernelVersion: 4.9 +Contact: Peter Rosin +Description: + The range of available values represented as the minimum value, + the step and the maximum value, all enclosed in square brackets. + Example: [0 1 256] diff --git a/Documentation/ABI/testing/sysfs-bus-iio-proximity b/Documentation/ABI/testing/sysfs-bus-iio-proximity new file mode 100644 index 000000000..9b9d1cc9b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-proximity @@ -0,0 +1,24 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_proximity_nearlevel +Date: March 2020 +KernelVersion: 5.7 +Contact: linux-iio@vger.kernel.org +Description: + Near level for proximity sensors. This is a single integer + value that tells user space when an object should be + considered close to the device. If the value read from the + sensor is above or equal to the value in this file an object + should typically be considered near. + +What: /sys/bus/iio/devices/iio:deviceX/sensor_sensitivity +Date: March 2014 +KernelVersion: 3.15 +Contact: linux-iio@vger.kernel.org +Description: + Proximity sensors sometimes have a controllable amplifier + on the signal from which time of flight measurements are + taken. + The appropriate values to take is dependent on both the + sensor and its operating environment: + * as3935 (0-31 range) + 18 = indoors (default) + 14 = outdoors diff --git a/Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 b/Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 new file mode 100644 index 000000000..1e5c40775 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 @@ -0,0 +1,15 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_proximity_input +Date: March 2014 +KernelVersion: 3.15 +Contact: Matt Ranostay +Description: + Get the current distance in meters of storm (1km steps) + 1000-40000 = distance in meters + +What /sys/bus/iio/devices/iio:deviceX/noise_level_tripped +Date: May 2017 +KernelVersion: 4.13 +Contact: Matt Ranostay +Description: + When 1 the noise level is over the trip level and not reporting + valid data diff --git a/Documentation/ABI/testing/sysfs-bus-iio-sps30 b/Documentation/ABI/testing/sysfs-bus-iio-sps30 new file mode 100644 index 000000000..06e1c2725 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-sps30 @@ -0,0 +1,28 @@ +What: /sys/bus/iio/devices/iio:deviceX/start_cleaning +Date: December 2018 +KernelVersion: 5.0 +Contact: linux-iio@vger.kernel.org +Description: + Writing 1 starts sensor self cleaning. Internal fan accelerates + to its maximum speed and keeps spinning for about 10 seconds in + order to blow out accumulated dust. + +What: /sys/bus/iio/devices/iio:deviceX/cleaning_period +Date: January 2019 +KernelVersion: 5.1 +Contact: linux-iio@vger.kernel.org +Description: + Sensor is capable of triggering self cleaning periodically. + Period can be changed by writing a new value here. Upon reading + the current one is returned. Units are seconds. + + Writing 0 disables periodical self cleaning entirely. + +What: /sys/bus/iio/devices/iio:deviceX/cleaning_period_available +Date: January 2019 +KernelVersion: 5.1 +Contact: linux-iio@vger.kernel.org +Description: + The range of available values in seconds represented as the + minimum value, the step and the maximum value, all enclosed in + square brackets. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-sx9310 b/Documentation/ABI/testing/sysfs-bus-iio-sx9310 new file mode 100644 index 000000000..3ac775901 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-sx9310 @@ -0,0 +1,10 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_proximity3_comb_raw +Date: February 2019 +KernelVersion: 5.6 +Contact: Daniel Campello +Description: + Proximity measurement indicating that some object is + near the combined sensor. The combined sensor presents + proximity measurements constructed by hardware by + combining measurements taken from a given set of + physical sensors. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-sx9324 b/Documentation/ABI/testing/sysfs-bus-iio-sx9324 new file mode 100644 index 000000000..a8342770e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-sx9324 @@ -0,0 +1,29 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_proximity_setup +Date: November 2021 +KernelVersion: 5.17 +Contact: Gwendal Grignou +Description: + SX9324 has 3 inputs, CS0, CS1 and CS2. Hardware layout + defines if the input is + + + not connected (HZ), + + grounded (GD), + + connected to an antenna where it can act as a base + (DS - data shield), or measured input (MI). + + The sensor rotates measurement across 4 phases + (PH0, PH1, PH2, PH3), where the inputs are configured + and then measured. + + By default, during the first phase, [PH0], CS0 is measured, + while CS1 and CS2 are used as shields. + `cat in_proximity0_setup` returns "MI,DS,DS". + [PH1], CS1 is measured, CS0 and CS2 are shield: + `cat in_proximity1_setup` returns "DS,MI,DS". + [PH2], CS2 is measured, CS0 and CS1 are shield: + `cat in_proximity1_setup` returns "DS,DS,MI". + [PH3], CS1 and CS2 are measured (combo mode): + `cat in_proximity1_setup` returns "DS,MI,MI". + + Note, these are the chip default. Hardware layout will most + likely dictate different output. The entry is read-only. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-thermocouple b/Documentation/ABI/testing/sysfs-bus-iio-thermocouple new file mode 100644 index 000000000..01259df29 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-thermocouple @@ -0,0 +1,18 @@ +What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv +KernelVersion: 5.1 +Contact: linux-iio@vger.kernel.org +Description: + Overvoltage or Undervoltage Input Fault. The internal circuitry + is protected from excessive voltages applied to the thermocouple + cables. The device can also detect if such a condition occurs. + + Reading returns '1' if input voltage is negative or greater + than VDD, otherwise '0'. + +What: /sys/bus/iio/devices/iio:deviceX/fault_oc +KernelVersion: 5.1 +Contact: linux-iio@vger.kernel.org +Description: + Open-circuit fault. The detection of open-circuit faults, + such as those caused by broken thermocouple wires. + Reading returns '1' if fault, '0' otherwise. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 b/Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 new file mode 100644 index 000000000..05074c4a6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 @@ -0,0 +1,143 @@ +What: /sys/bus/iio/devices/triggerX/master_mode_available +KernelVersion: 4.11 +Contact: benjamin.gaignard@st.com +Description: + Reading returns the list possible master modes which are: + + + - "reset" + The UG bit from the TIMx_EGR register is + used as trigger output (TRGO). + - "enable" + The Counter Enable signal CNT_EN is used + as trigger output. + - "update" + The update event is selected as trigger output. + For instance a master timer can then be used + as a prescaler for a slave timer. + - "compare_pulse" + The trigger output send a positive pulse + when the CC1IF flag is to be set. + - "OC1REF" + OC1REF signal is used as trigger output. + - "OC2REF" + OC2REF signal is used as trigger output. + - "OC3REF" + OC3REF signal is used as trigger output. + - "OC4REF" + OC4REF signal is used as trigger output. + + Additional modes (on TRGO2 only): + + - "OC5REF" + OC5REF signal is used as trigger output. + - "OC6REF" + OC6REF signal is used as trigger output. + - "compare_pulse_OC4REF": + OC4REF rising or falling edges generate pulses. + - "compare_pulse_OC6REF": + OC6REF rising or falling edges generate pulses. + - "compare_pulse_OC4REF_r_or_OC6REF_r": + OC4REF or OC6REF rising edges generate pulses. + - "compare_pulse_OC4REF_r_or_OC6REF_f": + OC4REF rising or OC6REF falling edges generate + pulses. + - "compare_pulse_OC5REF_r_or_OC6REF_r": + OC5REF or OC6REF rising edges generate pulses. + - "compare_pulse_OC5REF_r_or_OC6REF_f": + OC5REF rising or OC6REF falling edges generate + pulses. + + :: + + +-----------+ +-------------+ +---------+ + | Prescaler +-> | Counter | +-> | Master | TRGO(2) + +-----------+ +--+--------+-+ |-> | Control +--> + | | || +---------+ + +--v--------+-+ OCxREF || +---------+ + | Chx compare +----------> | Output | ChX + +-----------+-+ | | Control +--> + . | | +---------+ + . | | . + +-----------v-+ OC6REF | . + | Ch6 compare +---------+> + +-------------+ + + Example with: "compare_pulse_OC4REF_r_or_OC6REF_r":: + + X + X X + X . . X + X . . X + X . . X + count X . . . . X + . . . . + . . . . + +---------------+ + OC4REF | . . | + +-+ . . +-+ + . +---+ . + OC6REF . | | . + +-------+ +-------+ + +-+ +-+ + TRGO2 | | | | + +-+ +---+ +---------+ + +What: /sys/bus/iio/devices/triggerX/master_mode +KernelVersion: 4.11 +Contact: benjamin.gaignard@st.com +Description: + Reading returns the current master modes. + Writing set the master mode + +What: /sys/bus/iio/devices/iio:deviceX/in_count0_preset +KernelVersion: 4.12 +Contact: benjamin.gaignard@st.com +Description: + Reading returns the current preset value. + Writing sets the preset value. + When counting up the counter starts from 0 and fires an + event when reach preset value. + When counting down the counter start from preset value + and fire event when reach 0. + +What: /sys/bus/iio/devices/iio:deviceX/in_count_enable_mode_available +KernelVersion: 4.12 +Contact: benjamin.gaignard@st.com +Description: + Reading returns the list possible enable modes. + +What: /sys/bus/iio/devices/iio:deviceX/in_count0_enable_mode +KernelVersion: 4.12 +Contact: benjamin.gaignard@st.com +Description: + Configure the device counter enable modes, in all case + counting direction is set by in_count0_count_direction + attribute and the counter is clocked by the internal clock. + + always: + Counter is always ON. + + gated: + Counting is enabled when connected trigger signal + level is high else counting is disabled. + + triggered: + Counting is enabled on rising edge of the connected + trigger, and remains enabled for the duration of this + selected mode. + +What: /sys/bus/iio/devices/iio:deviceX/in_count_trigger_mode_available +KernelVersion: 4.13 +Contact: benjamin.gaignard@st.com +Description: + Reading returns the list possible trigger modes. + +What: /sys/bus/iio/devices/iio:deviceX/in_count0_trigger_mode +KernelVersion: 4.13 +Contact: benjamin.gaignard@st.com +Description: + Configure the device counter trigger mode + counting direction is set by in_count0_count_direction + attribute and the counter is clocked by the connected trigger + rising edges. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs b/Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs new file mode 100644 index 000000000..04ac62305 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-trigger-sysfs @@ -0,0 +1,42 @@ +What: /sys/bus/iio/devices/triggerX/trigger_now +KernelVersion: 2.6.38 +Contact: linux-iio@vger.kernel.org +Description: + This file is provided by the iio-trig-sysfs stand-alone trigger + driver. Writing this file with any value triggers an event + driven driver, associated with this trigger, to capture data + into an in kernel buffer. This approach can be valuable during + automated testing or in situations, where other trigger methods + are not applicable. For example no RTC or spare GPIOs. + X is the IIO index of the trigger. + +What: /sys/bus/iio/devices/triggerX/name +KernelVersion: 2.6.39 +Contact: linux-iio@vger.kernel.org +Description: + The name attribute holds a description string for the current + trigger. In order to associate the trigger with an IIO device + one should write this name string to + /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger. + +What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger +KernelVersion: 2.6.39 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is provided by the iio-trig-sysfs stand-alone + driver and it is used to activate the creation of a new trigger. + In order to achieve this, one should write a positive integer + into the associated file, which will serve as the id of the + trigger. If the trigger with the specified id is already present + in the system, an invalid argument message will be returned. + +What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger +KernelVersion: 2.6.39 +Contact: linux-iio@vger.kernel.org +Description: + This attribute is used to unregister and delete a previously + created trigger from the list of available triggers. In order to + achieve this, one should write a positive integer into the + associated file, representing the id of the trigger that needs + to be removed. If the trigger can't be found, an invalid + argument message will be returned to the user. diff --git a/Documentation/ABI/testing/sysfs-bus-iio-vf610 b/Documentation/ABI/testing/sysfs-bus-iio-vf610 new file mode 100644 index 000000000..491ead804 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-iio-vf610 @@ -0,0 +1,16 @@ +What: /sys/bus/iio/devices/iio:deviceX/in_conversion_mode +KernelVersion: 4.2 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the hardware conversion mode used. The three + available modes are "normal", "high-speed" and "low-power", + where the last is the default mode. + + +What: /sys/bus/iio/devices/iio:deviceX/out_conversion_mode +KernelVersion: 4.6 +Contact: linux-iio@vger.kernel.org +Description: + Specifies the hardware conversion mode used within DAC. + The two available modes are "high-power" and "low-power", + where "low-power" mode is the default mode. diff --git a/Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth new file mode 100644 index 000000000..b7b2278fe --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth @@ -0,0 +1,52 @@ +What: /sys/bus/intel_th/devices/-gth/masters/* +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure output ports for STP masters. Writing -1 + disables a master; any + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_port +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RO) Output port type: + + == ========================= + 0 not present, + 1 MSU (Memory Storage Unit) + 2 CTP (Common Trace Port) + 4 PTI (MIPI PTI). + == ========================= + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_drop +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Data retention policy setting: keep (0) or drop (1) + incoming data while output port is in reset. + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_null +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) STP NULL packet generation: enabled (1) or disabled (0). + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_flush +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Force flush data from byte packing buffer for the output + port. + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_reset +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RO) Output port is in reset (1). + +What: /sys/bus/intel_th/devices/-gth/outputs/[0-7]_smcfreq +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) STP sync packet frequency for the port. Specifies the + number of clocks between mainenance packets. diff --git a/Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc new file mode 100644 index 000000000..a74252e58 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc @@ -0,0 +1,54 @@ +What: /sys/bus/intel_th/devices/-msc/wrap +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure MSC buffer wrapping. 1 == wrapping enabled. + +What: /sys/bus/intel_th/devices/-msc/mode +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure MSC operating mode: + + - "single", for contiguous buffer mode (high-order alloc); + - "multi", for multiblock mode; + - "ExI", for DCI handler mode; + - "debug", for debug mode; + - any of the currently loaded buffer sinks. + + If operating mode changes, existing buffer is deallocated, + provided there are no active users and tracing is not enabled, + otherwise the write will fail. + +What: /sys/bus/intel_th/devices/-msc/nr_pages +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure MSC buffer size for "single" or "multi" modes. + + In single mode, this is a single number of pages, has to be + power of 2. In multiblock mode, this is a comma-separated list + of numbers of pages for each window to be allocated. Number of + windows is not limited. + + Writing to this file deallocates existing buffer (provided + there are no active users and tracing is not enabled) and then + allocates a new one. + +What: /sys/bus/intel_th/devices/-msc/win_switch +Date: May 2019 +KernelVersion: 5.2 +Contact: Alexander Shishkin +Description: (RW) Trigger window switch for the MSC's buffer, in + multi-window mode. In "multi" mode, accepts writes of "1", thereby + triggering a window switch for the buffer. Returns an error in any + other operating mode or attempts to write something other than "1". + +What: /sys/bus/intel_th/devices/-msc/stop_on_full +Date: March 2020 +KernelVersion: 5.7 +Contact: Alexander Shishkin +Description: (RW) Configure whether trace stops when the last available window + becomes full (1/y/Y) or wraps around and continues until the next + window becomes available again (0/n/N). + diff --git a/Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti new file mode 100644 index 000000000..df0b24fd0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-intel_th-devices-pti @@ -0,0 +1,24 @@ +What: /sys/bus/intel_th/devices/-pti/mode +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure PTI output width. Currently supported values + are 4, 8, 12, 16. + +What: /sys/bus/intel_th/devices/-pti/freerunning_clock +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) 0: PTI trace clock acts as a strobe which only toggles + when there is trace data to send. 1: PTI trace clock is a + free-running clock. + +What: /sys/bus/intel_th/devices/-pti/clock_divider +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Configure PTI port clock divider: + - 0: Intel TH clock rate, + - 1: 1/2 Intel TH clock rate, + - 2: 1/4 Intel TH clock rate, + - 3: 1/8 Intel TH clock rate. diff --git a/Documentation/ABI/testing/sysfs-bus-intel_th-output-devices b/Documentation/ABI/testing/sysfs-bus-intel_th-output-devices new file mode 100644 index 000000000..d1f667104 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-intel_th-output-devices @@ -0,0 +1,15 @@ +What: /sys/bus/intel_th/devices/-/active +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RW) Writes of 1 or 0 enable or disable trace output to this + output device. Reads return current status. Requires that the + correstponding output port driver be loaded. + +What: /sys/bus/intel_th/devices/-msc/port +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: (RO) Port number, corresponding to this output device on the + switch (GTH) or "unassigned" if the corresponding output + port driver is not loaded. diff --git a/Documentation/ABI/testing/sysfs-bus-mcb b/Documentation/ABI/testing/sysfs-bus-mcb new file mode 100644 index 000000000..77947c509 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-mcb @@ -0,0 +1,29 @@ +What: /sys/bus/mcb/devices/mcb:X +Date: March 2016 +KernelVersion: 4.7 +Contact: Johannes Thumshirn +Description: Hardware chip or device hosting the MEN chameleon bus + +What: /sys/bus/mcb/devices/mcb:X/revision +Date: March 2016 +KernelVersion: 4.7 +Contact: Johannes Thumshirn +Description: The FPGA's revision number + +What: /sys/bus/mcb/devices/mcb:X/minor +Date: March 2016 +KernelVersion: 4.7 +Contact: Johannes Thumshirn +Description: The FPGA's minor number + +What: /sys/bus/mcb/devices/mcb:X/model +Date: March 2016 +KernelVersion: 4.7 +Contact: Johannes Thumshirn +Description: The FPGA's model number + +What: /sys/bus/mcb/devices/mcb:X/name +Date: March 2016 +KernelVersion: 4.7 +Contact: Johannes Thumshirn +Description: The FPGA's name diff --git a/Documentation/ABI/testing/sysfs-bus-mdio b/Documentation/ABI/testing/sysfs-bus-mdio new file mode 100644 index 000000000..38be04dfc --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-mdio @@ -0,0 +1,72 @@ +What: /sys/bus/mdio_bus/devices/.../statistics/ +What: /sys/class/mdio_bus/.../statistics/ +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + This folder contains statistics about global and per + MDIO bus address statistics. + +What: /sys/bus/mdio_bus/devices/.../statistics/transfers +What: /sys/class/mdio_bus/.../transfers +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of transfers for this MDIO bus. + +What: /sys/bus/mdio_bus/devices/.../statistics/errors +What: /sys/class/mdio_bus/.../statistics/errors +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of transfer errors for this MDIO bus. + +What: /sys/bus/mdio_bus/devices/.../statistics/writes +What: /sys/class/mdio_bus/.../statistics/writes +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of write transactions for this MDIO bus. + +What: /sys/bus/mdio_bus/devices/.../statistics/reads +What: /sys/class/mdio_bus/.../statistics/reads +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of read transactions for this MDIO bus. + +What: /sys/bus/mdio_bus/devices/.../statistics/transfers_ +What: /sys/class/mdio_bus/.../statistics/transfers_ +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of transfers for this MDIO bus address. + +What: /sys/bus/mdio_bus/devices/.../statistics/errors_ +What: /sys/class/mdio_bus/.../statistics/errors_ +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of transfer errors for this MDIO bus address. + +What: /sys/bus/mdio_bus/devices/.../statistics/writes_ +What: /sys/class/mdio_bus/.../statistics/writes_ +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of write transactions for this MDIO bus address. + +What: /sys/bus/mdio_bus/devices/.../statistics/reads_ +What: /sys/class/mdio_bus/.../statistics/reads_ +Date: January 2020 +KernelVersion: 5.6 +Contact: netdev@vger.kernel.org +Description: + Total number of read transactions for this MDIO bus address. diff --git a/Documentation/ABI/testing/sysfs-bus-media b/Documentation/ABI/testing/sysfs-bus-media new file mode 100644 index 000000000..7057e5741 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-media @@ -0,0 +1,6 @@ +What: /sys/bus/media/devices/.../model +Date: January 2011 +Contact: Laurent Pinchart + linux-media@vger.kernel.org +Description: Contains the device model name in UTF-8. The device version is + is not be appended to the model name. diff --git a/Documentation/ABI/testing/sysfs-bus-mei b/Documentation/ABI/testing/sysfs-bus-mei new file mode 100644 index 000000000..6e9a105fe --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-mei @@ -0,0 +1,56 @@ +What: /sys/bus/mei/devices/.../modalias +Date: March 2013 +KernelVersion: 3.10 +Contact: Samuel Ortiz + linux-mei@linux.intel.com +Description: Stores the same MODALIAS value emitted by uevent + Format: mei::: + +What: /sys/bus/mei/devices/.../name +Date: May 2015 +KernelVersion: 4.2 +Contact: Tomas Winkler +Description: Stores mei client device name + Format: string + +What: /sys/bus/mei/devices/.../uuid +Date: May 2015 +KernelVersion: 4.2 +Contact: Tomas Winkler +Description: Stores mei client device uuid + Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx + +What: /sys/bus/mei/devices/.../version +Date: Aug 2015 +KernelVersion: 4.3 +Contact: Tomas Winkler +Description: Stores mei client protocol version + Format: %d + +What: /sys/bus/mei/devices/.../max_conn +Date: Nov 2019 +KernelVersion: 5.5 +Contact: Tomas Winkler +Description: Stores mei client maximum number of connections + Format: %d + +What: /sys/bus/mei/devices/.../fixed +Date: Nov 2019 +KernelVersion: 5.5 +Contact: Tomas Winkler +Description: Stores mei client fixed address, if any + Format: %d + +What: /sys/bus/mei/devices/.../vtag +Date: Nov 2020 +KernelVersion: 5.9 +Contact: Tomas Winkler +Description: Stores mei client vtag support status + Format: %d + +What: /sys/bus/mei/devices/.../max_len +Date: Nov 2019 +KernelVersion: 5.5 +Contact: Tomas Winkler +Description: Stores mei client maximum message length + Format: %d diff --git a/Documentation/ABI/testing/sysfs-bus-mmc b/Documentation/ABI/testing/sysfs-bus-mmc new file mode 100644 index 000000000..519f028d1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-mmc @@ -0,0 +1,4 @@ +What: /sys/bus/mmc/devices/.../rev +Date: October 2017 +Contact: Jin Qian +Description: Extended CSD revision number diff --git a/Documentation/ABI/testing/sysfs-bus-most b/Documentation/ABI/testing/sysfs-bus-most new file mode 100644 index 000000000..38cc03e40 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-most @@ -0,0 +1,299 @@ +What: /sys/bus/most/devices//description +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Provides information about the physical location of the + device. Hardware attached via USB, for instance, + might return <1-1.1:1.0> +Users: + +What: /sys/bus/most/devices//interface +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the type of peripheral interface the device uses. +Users: + +What: /sys/bus/most/devices//dci +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + If the network interface controller is attached via USB, a dci + directory is created that allows applications to read and + write the controller's DCI registers. +Users: + +What: /sys/bus/most/devices//dci/arb_address +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to set an arbitrary DCI register address an + application wants to read from or write to. +Users: + +What: /sys/bus/most/devices//dci/arb_value +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to read and write the DCI register whose address + is stored in arb_address. +Users: + +What: /sys/bus/most/devices//dci/mep_eui48_hi +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MAC address. +Users: + +What: /sys/bus/most/devices//dci/mep_eui48_lo +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MAC address. +Users: + +What: /sys/bus/most/devices//dci/mep_eui48_mi +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MAC address. +Users: + +What: /sys/bus/most/devices//dci/mep_filter +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MEP filter address. +Users: + +What: /sys/bus/most/devices//dci/mep_hash0 +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MEP hash table. +Users: + +What: /sys/bus/most/devices//dci/mep_hash1 +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MEP hash table. +Users: + +What: /sys/bus/most/devices//dci/mep_hash2 +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MEP hash table. +Users: + +What: /sys/bus/most/devices//dci/mep_hash3 +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to check and configure the MEP hash table. +Users: + +What: /sys/bus/most/devices//dci/ni_state +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the current network interface state. +Users: + +What: /sys/bus/most/devices//dci/node_address +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the current node address. +Users: + +What: /sys/bus/most/devices//dci/node_position +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the current node position. +Users: + +What: /sys/bus/most/devices//dci/packet_bandwidth +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the configured packet bandwidth. +Users: + +What: /sys/bus/most/devices//dci/sync_ep +Date: June 2016 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Triggers the controller's synchronization process for a certain + endpoint. +Users: + +What: /sys/bus/most/devices/// +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + For every channel of the device a directory is created, whose + name is dictated by the HDM. This enables an application to + collect information about the channel's capabilities and + configure it. +Users: + +What: /sys/bus/most/devices///available_datatypes +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the data types the channel can transport. +Users: + +What: /sys/bus/most/devices///available_directions +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the directions the channel is capable of. +Users: + +What: /sys/bus/most/devices///number_of_packet_buffers +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the number of packet buffers the channel can + handle. +Users: + +What: /sys/bus/most/devices///number_of_stream_buffers +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the number of streaming buffers the channel can + handle. +Users: + +What: /sys/bus/most/devices///size_of_packet_buffer +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the size of a packet buffer the channel can + handle. +Users: + +What: /sys/bus/most/devices///size_of_stream_buffer +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates the size of a streaming buffer the channel can + handle. +Users: + +What: /sys/bus/most/devices///set_number_of_buffers +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured number of buffers of + the channel. +Users: + +What: /sys/bus/most/devices///set_buffer_size +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured buffer size of the channel. +Users: + +What: /sys/bus/most/devices///set_direction +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured direction of the channel. + The following strings will be accepted:: + + 'tx', + 'rx' +Users: + +What: /sys/bus/most/devices///set_datatype +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured data type of the channel. + The following strings will be accepted:: + + 'control', + 'async', + 'sync', + 'isoc_avp' +Users: + +What: /sys/bus/most/devices///set_subbuffer_size +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured subbuffer size of + the channel. +Users: + +What: /sys/bus/most/devices///set_packets_per_xact +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is to read back the configured number of packets per + transaction of the channel. This is only applicable when + connected via USB. +Users: + +What: /sys/bus/most/devices///channel_starving +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + Indicates whether channel ran out of buffers. +Users: + +What: /sys/bus/most/drivers/most_core/components +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to retrieve a list of registered components. +Users: + +What: /sys/bus/most/drivers/most_core/links +Date: March 2017 +KernelVersion: 4.15 +Contact: Christian Gromm +Description: + This is used to retrieve a list of established links. +Users: diff --git a/Documentation/ABI/testing/sysfs-bus-moxtet-devices b/Documentation/ABI/testing/sysfs-bus-moxtet-devices new file mode 100644 index 000000000..32dccc00d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-moxtet-devices @@ -0,0 +1,17 @@ +What: /sys/bus/moxtet/devices/moxtet-./module_description +Date: March 2019 +KernelVersion: 5.3 +Contact: Marek Behún +Description: (Read) Moxtet module description. Format: string + +What: /sys/bus/moxtet/devices/moxtet-./module_id +Date: March 2019 +KernelVersion: 5.3 +Contact: Marek Behún +Description: (Read) Moxtet module ID. Format: %x + +What: /sys/bus/moxtet/devices/moxtet-./module_name +Date: March 2019 +KernelVersion: 5.3 +Contact: Marek Behún +Description: (Read) Moxtet module name. Format: string diff --git a/Documentation/ABI/testing/sysfs-bus-nfit b/Documentation/ABI/testing/sysfs-bus-nfit new file mode 100644 index 000000000..e7282d184 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-nfit @@ -0,0 +1,233 @@ +For all of the nmem device attributes under ``nfit/*``, see the 'NVDIMM Firmware +Interface Table (NFIT)' section in the ACPI specification +(http://www.uefi.org/specifications) for more details. + +What: /sys/bus/nd/devices/nmemX/nfit/serial +Date: Jun, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Serial number of the NVDIMM (non-volatile dual in-line + memory module), assigned by the module vendor. + + +What: /sys/bus/nd/devices/nmemX/nfit/handle +Date: Apr, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) The address (given by the _ADR object) of the device on its + parent bus of the NVDIMM device containing the NVDIMM region. + + +What: /sys/bus/nd/devices/nmemX/nfit/device +Date: Apr, 2015 +KernelVersion: v4.1 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Device id for the NVDIMM, assigned by the module vendor. + + +What: /sys/bus/nd/devices/nmemX/nfit/rev_id +Date: Jun, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Revision of the NVDIMM, assigned by the module vendor. + + +What: /sys/bus/nd/devices/nmemX/nfit/phys_id +Date: Apr, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Handle (i.e., instance number) for the SMBIOS (system + management BIOS) Memory Device structure describing the NVDIMM + containing the NVDIMM region. + + +What: /sys/bus/nd/devices/nmemX/nfit/flags +Date: Jun, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) The flags in the NFIT memory device sub-structure indicate + the state of the data on the nvdimm relative to its energy + source or last "flush to persistence". + + The attribute is a translation of the 'NVDIMM State Flags' field + in section 5.2.25.3 'NVDIMM Region Mapping' Structure of the + ACPI specification 6.2. + + The health states are "save_fail", "restore_fail", "flush_fail", + "not_armed", "smart_event", "map_fail" and "smart_notify". + + +What: /sys/bus/nd/devices/nmemX/nfit/format +What: /sys/bus/nd/devices/nmemX/nfit/format1 +What: /sys/bus/nd/devices/nmemX/nfit/formats +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) The interface codes indicate support for persistent memory + mapped directly into system physical address space and / or a + block aperture access mechanism to the NVDIMM media. + The 'formats' attribute displays the number of supported + interfaces. + + This layout is compatible with existing libndctl binaries that + only expect one code per-dimm as they will ignore + nmemX/nfit/formats and nmemX/nfit/formatN. + + +What: /sys/bus/nd/devices/nmemX/nfit/vendor +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Vendor id of the NVDIMM. + + +What: /sys/bus/nd/devices/nmemX/nfit/dsm_mask +Date: May, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) The bitmask indicates the supported device specific control + functions relative to the NVDIMM command family supported by the + device + + +What: /sys/bus/nd/devices/nmemX/nfit/family +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Displays the NVDIMM family command sets. Values + 0, 1, 2 and 3 correspond to NVDIMM_FAMILY_INTEL, + NVDIMM_FAMILY_HPE1, NVDIMM_FAMILY_HPE2 and NVDIMM_FAMILY_MSFT + respectively. + + See the specifications for these command families here: + http://pmem.io/documents/NVDIMM_DSM_Interface-V1.6.pdf + https://github.com/HewlettPackard/hpe-nvm/blob/master/Documentation/ + https://msdn.microsoft.com/library/windows/hardware/mt604741" + + +What: /sys/bus/nd/devices/nmemX/nfit/id +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) ACPI specification 6.2 section 5.2.25.9, defines an + identifier for an NVDIMM, which refelects the id attribute. + + +What: /sys/bus/nd/devices/nmemX/nfit/subsystem_vendor +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Sub-system vendor id of the NVDIMM non-volatile memory + subsystem controller. + + +What: /sys/bus/nd/devices/nmemX/nfit/subsystem_rev_id +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Sub-system revision id of the NVDIMM non-volatile memory subsystem + controller, assigned by the non-volatile memory subsystem + controller vendor. + + +What: /sys/bus/nd/devices/nmemX/nfit/subsystem_device +Date: Apr, 2016 +KernelVersion: v4.7 +Contact: nvdimm@lists.linux.dev +Description: + (RO) Sub-system device id for the NVDIMM non-volatile memory + subsystem controller, assigned by the non-volatile memory + subsystem controller vendor. + + +What: /sys/bus/nd/devices/ndbusX/nfit/revision +Date: Jun, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) ACPI NFIT table revision number. + + +What: /sys/bus/nd/devices/ndbusX/nfit/scrub +Date: Sep, 2016 +KernelVersion: v4.9 +Contact: nvdimm@lists.linux.dev +Description: + (RW) This shows the number of full Address Range Scrubs (ARS) + that have been completed since driver load time. Userspace can + wait on this using select/poll etc. A '+' at the end indicates + an ARS is in progress + + Writing a value of 1 triggers an ARS scan. + + +What: /sys/bus/nd/devices/ndbusX/nfit/hw_error_scrub +Date: Sep, 2016 +KernelVersion: v4.9 +Contact: nvdimm@lists.linux.dev +Description: + (RW) Provides a way to toggle the behavior between just adding + the address (cache line) where the MCE happened to the poison + list and doing a full scrub. The former (selective insertion of + the address) is done unconditionally. + + This attribute can have the following values written to it: + + '0': Switch to the default mode where an exception will only + insert the address of the memory error into the poison and + badblocks lists. + '1': Enable a full scrub to happen if an exception for a memory + error is received. + + +What: /sys/bus/nd/devices/ndbusX/nfit/dsm_mask +Date: Jun, 2017 +KernelVersion: v4.13 +Contact: nvdimm@lists.linux.dev +Description: + (RO) The bitmask indicates the supported bus specific control + functions. See the section named 'NVDIMM Root Device _DSMs' in + the ACPI specification. + +What: /sys/bus/nd/devices/ndbusX/nfit/firmware_activate_noidle +Date: Apr, 2020 +KernelVersion: v5.8 +Contact: nvdimm@lists.linux.dev +Description: + (RW) The Intel platform implementation of firmware activate + support exposes an option let the platform force idle devices in + the system over the activation event, or trust that the OS will + do it. The safe default is to let the platform force idle + devices since the kernel is already in a suspend state, and on + the chance that a driver does not properly quiesce bus-mastering + after a suspend callback the platform will handle it. However, + the activation might abort if, for example, platform firmware + determines that the activation time exceeds the max PCI-E + completion timeout. Since the platform does not know whether the + OS is running the activation from a suspend context it aborts, + but if the system owner trusts driver suspend callback to be + sufficient then 'firmware_activation_noidle' can be + enabled to bypass the activation abort. + +What: /sys/bus/nd/devices/regionX/nfit/range_index +Date: Jun, 2015 +KernelVersion: v4.2 +Contact: nvdimm@lists.linux.dev +Description: + (RO) A unique number provided by the BIOS to identify an address + range. Used by NVDIMM Region Mapping Structure to uniquely refer + to this structure. Value of 0 is reserved and not used as an + index. diff --git a/Documentation/ABI/testing/sysfs-bus-nvdimm b/Documentation/ABI/testing/sysfs-bus-nvdimm new file mode 100644 index 000000000..1c1f5acbf --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-nvdimm @@ -0,0 +1,43 @@ +What: nvdimm +Date: July 2020 +KernelVersion: 5.8 +Contact: Dan Williams +Description: + +The libnvdimm sub-system implements a common sysfs interface for +platform nvdimm resources. See Documentation/driver-api/nvdimm/. + +What: /sys/bus/event_source/devices/nmemX/format +Date: February 2022 +KernelVersion: 5.18 +Contact: Kajol Jain +Description: (RO) Attribute group to describe the magic bits + that go into perf_event_attr.config for a particular pmu. + (See ABI/testing/sysfs-bus-event_source-devices-format). + + Each attribute under this group defines a bit range of the + perf_event_attr.config. Supported attribute is listed + below:: + event = "config:0-4" - event ID + + For example:: + ctl_res_cnt = "event=0x1" + +What: /sys/bus/event_source/devices/nmemX/events +Date: February 2022 +KernelVersion: 5.18 +Contact: Kajol Jain +Description: (RO) Attribute group to describe performance monitoring events + for the nvdimm memory device. Each attribute in this group + describes a single performance monitoring event supported by + this nvdimm pmu. The name of the file is the name of the event. + (See ABI/testing/sysfs-bus-event_source-devices-events). A + listing of the events supported by a given nvdimm provider type + can be found in Documentation/driver-api/nvdimm/$provider. + +What: /sys/bus/event_source/devices/nmemX/cpumask +Date: February 2022 +KernelVersion: 5.18 +Contact: Kajol Jain +Description: (RO) This sysfs file exposes the cpumask which is designated to + to retrieve nvdimm pmu event counter data. diff --git a/Documentation/ABI/testing/sysfs-bus-optee-devices b/Documentation/ABI/testing/sysfs-bus-optee-devices new file mode 100644 index 000000000..af31e5a22 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-optee-devices @@ -0,0 +1,17 @@ +What: /sys/bus/tee/devices/optee-ta-/ +Date: May 2020 +KernelVersion 5.8 +Contact: op-tee@lists.trustedfirmware.org +Description: + OP-TEE bus provides reference to registered drivers under this directory. The + matches Trusted Application (TA) driver and corresponding TA in secure OS. Drivers + are free to create needed API under optee-ta- directory. + +What: /sys/bus/tee/devices/optee-ta-/need_supplicant +Date: November 2023 +KernelVersion: 6.7 +Contact: op-tee@lists.trustedfirmware.org +Description: + Allows to distinguish whether an OP-TEE based TA/device requires user-space + tee-supplicant to function properly or not. This attribute will be present for + devices which depend on tee-supplicant to be running. diff --git a/Documentation/ABI/testing/sysfs-bus-papr-pmem b/Documentation/ABI/testing/sysfs-bus-papr-pmem new file mode 100644 index 000000000..4ac067390 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-papr-pmem @@ -0,0 +1,75 @@ +What: /sys/bus/nd/devices/nmemX/papr/flags +Date: Apr, 2020 +KernelVersion: v5.8 +Contact: linuxppc-dev , nvdimm@lists.linux.dev, +Description: + (RO) Report flags indicating various states of a + papr-pmem NVDIMM device. Each flag maps to a one or + more bits set in the dimm-health-bitmap retrieved in + response to H_SCM_HEALTH hcall. The details of the bit + flags returned in response to this hcall is available + at 'Documentation/powerpc/papr_hcalls.rst' . Below are + the flags reported in this sysfs file: + + * "not_armed" + Indicates that NVDIMM contents will not + survive a power cycle. + * "flush_fail" + Indicates that NVDIMM contents + couldn't be flushed during last + shut-down event. + * "restore_fail" + Indicates that NVDIMM contents + couldn't be restored during NVDIMM + initialization. + * "encrypted" + NVDIMM contents are encrypted. + * "smart_notify" + There is health event for the NVDIMM. + * "scrubbed" + Indicating that contents of the + NVDIMM have been scrubbed. + * "locked" + Indicating that NVDIMM contents cant + be modified until next power cycle. + +What: /sys/bus/nd/devices/nmemX/papr/perf_stats +Date: May, 2020 +KernelVersion: v5.9 +Contact: linuxppc-dev , nvdimm@lists.linux.dev, +Description: + (RO) Report various performance stats related to papr-scm NVDIMM + device. This attribute is only available for NVDIMM devices + that support reporting NVDIMM performance stats. Each stat is + reported on a new line with each line composed of a + stat-identifier followed by it value. Below are currently known + dimm performance stats which are reported: + + * "CtlResCt" : Controller Reset Count + * "CtlResTm" : Controller Reset Elapsed Time + * "PonSecs " : Power-on Seconds + * "MemLife " : Life Remaining + * "CritRscU" : Critical Resource Utilization + * "HostLCnt" : Host Load Count + * "HostSCnt" : Host Store Count + * "HostSDur" : Host Store Duration + * "HostLDur" : Host Load Duration + * "MedRCnt " : Media Read Count + * "MedWCnt " : Media Write Count + * "MedRDur " : Media Read Duration + * "MedWDur " : Media Write Duration + * "CchRHCnt" : Cache Read Hit Count + * "CchWHCnt" : Cache Write Hit Count + * "FastWCnt" : Fast Write Count + +What: /sys/bus/nd/devices/nmemX/papr/health_bitmap_inject +Date: Jan, 2022 +KernelVersion: v5.17 +Contact: linuxppc-dev , nvdimm@lists.linux.dev, +Description: + (RO) Reports the health bitmap inject bitmap that is applied to + bitmap received from PowerVM via the H_SCM_HEALTH. This is used + to forcibly set specific bits returned from Hcall. These is then + used to simulate various health or shutdown states for an nvdimm + and are set by user-space tools like ndctl by issuing a PAPR DSM. + diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci new file mode 100644 index 000000000..840727fc7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci @@ -0,0 +1,492 @@ +What: /sys/bus/pci/drivers/.../bind +What: /sys/devices/pciX/.../bind +Date: December 2003 +Contact: linux-pci@vger.kernel.org +Description: + Writing a device location to this file will cause + the driver to attempt to bind to the device found at + this location. This is useful for overriding default + bindings. The format for the location is: DDDD:BB:DD.F. + That is Domain:Bus:Device.Function and is the same as + found in /sys/bus/pci/devices/. For example:: + + # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind + + (Note: kernels before 2.6.28 may require echo -n). + +What: /sys/bus/pci/drivers/.../unbind +What: /sys/devices/pciX/.../unbind +Date: December 2003 +Contact: linux-pci@vger.kernel.org +Description: + Writing a device location to this file will cause the + driver to attempt to unbind from the device found at + this location. This may be useful when overriding default + bindings. The format for the location is: DDDD:BB:DD.F. + That is Domain:Bus:Device.Function and is the same as + found in /sys/bus/pci/devices/. For example:: + + # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind + + (Note: kernels before 2.6.28 may require echo -n). + +What: /sys/bus/pci/drivers/.../new_id +What: /sys/devices/pciX/.../new_id +Date: December 2003 +Contact: linux-pci@vger.kernel.org +Description: + Writing a device ID to this file will attempt to + dynamically add a new device ID to a PCI device driver. + This may allow the driver to support more hardware than + was included in the driver's static device ID support + table at compile time. The format for the device ID is: + VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, + Device ID, Subsystem Vendor ID, Subsystem Device ID, + Class, Class Mask, and Private Driver Data. The Vendor ID + and Device ID fields are required, the rest are optional. + Upon successfully adding an ID, the driver will probe + for the device and attempt to bind to it. For example:: + + # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id + +What: /sys/bus/pci/drivers/.../remove_id +What: /sys/devices/pciX/.../remove_id +Date: February 2009 +Contact: Chris Wright +Description: + Writing a device ID to this file will remove an ID + that was dynamically added via the new_id sysfs entry. + The format for the device ID is: + VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device + ID, Subsystem Vendor ID, Subsystem Device ID, Class, + and Class Mask. The Vendor ID and Device ID fields are + required, the rest are optional. After successfully + removing an ID, the driver will no longer support the + device. This is useful to ensure auto probing won't + match the driver to the device. For example:: + + # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id + +What: /sys/bus/pci/rescan +Date: January 2009 +Contact: Linux PCI developers +Description: + Writing a non-zero value to this attribute will + force a rescan of all PCI buses in the system, and + re-discover previously removed devices. + +What: /sys/bus/pci/devices/.../msi_bus +Date: September 2014 +Contact: Linux PCI developers +Description: + Writing a zero value to this attribute disallows MSI and + MSI-X for any future drivers of the device. If the device + is a bridge, MSI and MSI-X will be disallowed for future + drivers of all child devices under the bridge. Drivers + must be reloaded for the new setting to take effect. + +What: /sys/bus/pci/devices/.../msi_irqs/ +Date: September, 2011 +Contact: Neil Horman +Description: + The /sys/devices/.../msi_irqs directory contains a variable set + of files, with each file being named after a corresponding msi + irq vector allocated to that device. + +What: /sys/bus/pci/devices/.../msi_irqs/ +Date: September 2011 +Contact: Neil Horman +Description: + This attribute indicates the mode that the irq vector named by + the file is in (msi vs. msix) + +What: /sys/bus/pci/devices/.../irq +Date: August 2021 +Contact: Linux PCI developers +Description: + If a driver has enabled MSI (not MSI-X), "irq" contains the + IRQ of the first MSI vector. Otherwise "irq" contains the + IRQ of the legacy INTx interrupt. + + "irq" being set to 0 indicates that the device isn't + capable of generating legacy INTx interrupts. + +What: /sys/bus/pci/devices/.../remove +Date: January 2009 +Contact: Linux PCI developers +Description: + Writing a non-zero value to this attribute will + hot-remove the PCI device and any of its children. + +What: /sys/bus/pci/devices/.../pci_bus/.../rescan +Date: May 2011 +Contact: Linux PCI developers +Description: + Writing a non-zero value to this attribute will + force a rescan of the bus and all child buses, + and re-discover devices removed earlier from this + part of the device tree. + +What: /sys/bus/pci/devices/.../rescan +Date: January 2009 +Contact: Linux PCI developers +Description: + Writing a non-zero value to this attribute will + force a rescan of the device's parent bus and all + child buses, and re-discover devices removed earlier + from this part of the device tree. + +What: /sys/bus/pci/devices/.../reset_method +Date: August 2021 +Contact: Amey Narkhede +Description: + Some devices allow an individual function to be reset + without affecting other functions in the same slot. + + For devices that have this support, a file named + reset_method is present in sysfs. Reading this file + gives names of the supported and enabled reset methods and + their ordering. Writing a space-separated list of names of + reset methods sets the reset methods and ordering to be + used when resetting the device. Writing an empty string + disables the ability to reset the device. Writing + "default" enables all supported reset methods in the + default ordering. + +What: /sys/bus/pci/devices/.../reset +Date: July 2009 +Contact: Michael S. Tsirkin +Description: + Some devices allow an individual function to be reset + without affecting other functions in the same device. + For devices that have this support, a file named reset + will be present in sysfs. Writing 1 to this file + will perform reset. + +What: /sys/bus/pci/devices/.../vpd +Date: February 2008 +Contact: Ben Hutchings +Description: + A file named vpd in a device directory will be a + binary file containing the Vital Product Data for the + device. It should follow the VPD format defined in + PCI Specification 2.1 or 2.2, but users should consider + that some devices may have incorrectly formatted data. + If the underlying VPD has a writable section then the + corresponding section of this file will be writable. + +What: /sys/bus/pci/devices/.../virtfn +Date: March 2009 +Contact: Yu Zhao +Description: + This symbolic link appears when hardware supports the SR-IOV + capability and the Physical Function driver has enabled it. + The symbolic link points to the PCI device sysfs entry of the + Virtual Function whose index is N (0...MaxVFs-1). + +What: /sys/bus/pci/devices/.../dep_link +Date: March 2009 +Contact: Yu Zhao +Description: + This symbolic link appears when hardware supports the SR-IOV + capability and the Physical Function driver has enabled it, + and this device has vendor specific dependencies with others. + The symbolic link points to the PCI device sysfs entry of + Physical Function this device depends on. + +What: /sys/bus/pci/devices/.../physfn +Date: March 2009 +Contact: Yu Zhao +Description: + This symbolic link appears when a device is a Virtual Function. + The symbolic link points to the PCI device sysfs entry of the + Physical Function this device associates with. + +What: /sys/bus/pci/devices/.../modalias +Date: May 2005 +Contact: Greg Kroah-Hartman +Description: + This attribute indicates the PCI ID of the device object. + + That is in the format: + pci:vXXXXXXXXdXXXXXXXXsvXXXXXXXXsdXXXXXXXXbcXXscXXiXX, + where: + + - vXXXXXXXX contains the vendor ID; + - dXXXXXXXX contains the device ID; + - svXXXXXXXX contains the sub-vendor ID; + - sdXXXXXXXX contains the subsystem device ID; + - bcXX contains the device class; + - scXX contains the device subclass; + - iXX contains the device class programming interface. + +What: /sys/bus/pci/slots/.../module +Date: June 2009 +Contact: linux-pci@vger.kernel.org +Description: + This symbolic link points to the PCI hotplug controller driver + module that manages the hotplug slot. + +What: /sys/bus/pci/devices/.../label +Date: July 2010 +Contact: Narendra K , linux-bugs@dell.com +Description: + Reading this attribute will provide the firmware + given name (SMBIOS type 41 string or ACPI _DSM string) of + the PCI device. The attribute will be created only + if the firmware has given a name to the PCI device. + ACPI _DSM string name will be given priority if the + system firmware provides SMBIOS type 41 string also. +Users: + Userspace applications interested in knowing the + firmware assigned name of the PCI device. + +What: /sys/bus/pci/devices/.../index +Date: July 2010 +Contact: Narendra K , linux-bugs@dell.com +Description: + Reading this attribute will provide the firmware given instance + number of the PCI device. Depending on the platform this can + be for example the SMBIOS type 41 device type instance or the + user-defined ID (UID) on s390. The attribute will be created + only if the firmware has given an instance number to the PCI + device and that number is guaranteed to uniquely identify the + device in the system. +Users: + Userspace applications interested in knowing the + firmware assigned device type instance of the PCI + device that can help in understanding the firmware + intended order of the PCI device. + +What: /sys/bus/pci/devices/.../acpi_index +Date: July 2010 +Contact: Narendra K , linux-bugs@dell.com +Description: + Reading this attribute will provide the firmware + given instance (ACPI _DSM instance number) of the PCI device. + The attribute will be created only if the firmware has given + an instance number to the PCI device. ACPI _DSM instance number + will be given priority if the system firmware provides SMBIOS + type 41 device type instance also. +Users: + Userspace applications interested in knowing the + firmware assigned instance number of the PCI + device that can help in understanding the firmware + intended order of the PCI device. + +What: /sys/bus/pci/devices/.../d3cold_allowed +Date: July 2012 +Contact: Huang Ying +Description: + d3cold_allowed is bit to control whether the corresponding PCI + device can be put into D3Cold state. If it is cleared, the + device will never be put into D3Cold state. If it is set, the + device may be put into D3Cold state if other requirements are + satisfied too. Reading this attribute will show the current + value of d3cold_allowed bit. Writing this attribute will set + the value of d3cold_allowed bit. + +What: /sys/bus/pci/devices/.../sriov_totalvfs +Date: November 2012 +Contact: Donald Dutile +Description: + This file appears when a physical PCIe device supports SR-IOV. + Userspace applications can read this file to determine the + maximum number of Virtual Functions (VFs) a PCIe physical + function (PF) can support. Typically, this is the value reported + in the PF's SR-IOV extended capability structure's TotalVFs + element. Drivers have the ability at probe time to reduce the + value read from this file via the pci_sriov_set_totalvfs() + function. + +What: /sys/bus/pci/devices/.../sriov_numvfs +Date: November 2012 +Contact: Donald Dutile +Description: + This file appears when a physical PCIe device supports SR-IOV. + Userspace applications can read and write to this file to + determine and control the enablement or disablement of Virtual + Functions (VFs) on the physical function (PF). A read of this + file will return the number of VFs that are enabled on this PF. + A number written to this file will enable the specified + number of VFs. A userspace application would typically read the + file and check that the value is zero, and then write the number + of VFs that should be enabled on the PF; the value written + should be less than or equal to the value in the sriov_totalvfs + file. A userspace application wanting to disable the VFs would + write a zero to this file. The core ensures that valid values + are written to this file, and returns errors when values are not + valid. For example, writing a 2 to this file when sriov_numvfs + is not 0 and not 2 already will return an error. Writing a 10 + when the value of sriov_totalvfs is 8 will return an error. + +What: /sys/bus/pci/devices/.../driver_override +Date: April 2014 +Contact: Alex Williamson +Description: + This file allows the driver for a device to be specified which + will override standard static and dynamic ID matching. When + specified, only a driver with a name matching the value written + to driver_override will have an opportunity to bind to the + device. The override is specified by writing a string to the + driver_override file (echo pci-stub > driver_override) and + may be cleared with an empty string (echo > driver_override). + This returns the device to standard matching rules binding. + Writing to driver_override does not automatically unbind the + device from its current driver or make any attempt to + automatically load the specified driver. If no driver with a + matching name is currently loaded in the kernel, the device + will not bind to any driver. This also allows devices to + opt-out of driver binding using a driver_override name such as + "none". Only a single driver may be specified in the override, + there is no support for parsing delimiters. + +What: /sys/bus/pci/devices/.../numa_node +Date: Oct 2014 +Contact: Prarit Bhargava +Description: + This file contains the NUMA node to which the PCI device is + attached, or -1 if the node is unknown. The initial value + comes from an ACPI _PXM method or a similar firmware + source. If that is missing or incorrect, this file can be + written to override the node. In that case, please report + a firmware bug to the system vendor. Writing to this file + taints the kernel with TAINT_FIRMWARE_WORKAROUND, which + reduces the supportability of your system. + +What: /sys/bus/pci/devices/.../revision +Date: November 2016 +Contact: Emil Velikov +Description: + This file contains the revision field of the PCI device. + The value comes from device config space. The file is read only. + +What: /sys/bus/pci/devices/.../sriov_drivers_autoprobe +Date: April 2017 +Contact: Bodong Wang +Description: + This file is associated with the PF of a device that + supports SR-IOV. It determines whether newly-enabled VFs + are immediately bound to a driver. It initially contains + 1, which means the kernel automatically binds VFs to a + compatible driver immediately after they are enabled. If + an application writes 0 to the file before enabling VFs, + the kernel will not bind VFs to a driver. + + A typical use case is to write 0 to this file, then enable + VFs, then assign the newly-created VFs to virtual machines. + Note that changing this file does not affect already- + enabled VFs. In this scenario, the user must first disable + the VFs, write 0 to sriov_drivers_autoprobe, then re-enable + the VFs. + + This is similar to /sys/bus/pci/drivers_autoprobe, but + affects only the VFs associated with a specific PF. + +What: /sys/bus/pci/devices/.../p2pmem/size +Date: November 2017 +Contact: Logan Gunthorpe +Description: + If the device has any Peer-to-Peer memory registered, this + file contains the total amount of memory that the device + provides (in decimal). + +What: /sys/bus/pci/devices/.../p2pmem/available +Date: November 2017 +Contact: Logan Gunthorpe +Description: + If the device has any Peer-to-Peer memory registered, this + file contains the amount of memory that has not been + allocated (in decimal). + +What: /sys/bus/pci/devices/.../p2pmem/published +Date: November 2017 +Contact: Logan Gunthorpe +Description: + If the device has any Peer-to-Peer memory registered, this + file contains a '1' if the memory has been published for + use outside the driver that owns the device. + +What: /sys/bus/pci/devices/.../link/clkpm + /sys/bus/pci/devices/.../link/l0s_aspm + /sys/bus/pci/devices/.../link/l1_aspm + /sys/bus/pci/devices/.../link/l1_1_aspm + /sys/bus/pci/devices/.../link/l1_2_aspm + /sys/bus/pci/devices/.../link/l1_1_pcipm + /sys/bus/pci/devices/.../link/l1_2_pcipm +Date: October 2019 +Contact: Heiner Kallweit +Description: If ASPM is supported for an endpoint, these files can be + used to disable or enable the individual power management + states. Write y/1/on to enable, n/0/off to disable. + +What: /sys/bus/pci/devices/.../power_state +Date: November 2020 +Contact: Linux PCI developers +Description: + This file contains the current PCI power state of the device. + The value comes from the PCI kernel device state and can be one + of: "unknown", "error", "D0", D1", "D2", "D3hot", "D3cold". + The file is read only. + +What: /sys/bus/pci/devices/.../sriov_vf_total_msix +Date: January 2021 +Contact: Leon Romanovsky +Description: + This file is associated with a SR-IOV physical function (PF). + It contains the total number of MSI-X vectors available for + assignment to all virtual functions (VFs) associated with PF. + The value will be zero if the device doesn't support this + functionality. For supported devices, the value will be + constant and won't be changed after MSI-X vectors assignment. + +What: /sys/bus/pci/devices/.../sriov_vf_msix_count +Date: January 2021 +Contact: Leon Romanovsky +Description: + This file is associated with a SR-IOV virtual function (VF). + It allows configuration of the number of MSI-X vectors for + the VF. This allows devices that have a global pool of MSI-X + vectors to optimally divide them between VFs based on VF usage. + + The values accepted are: + * > 0 - this number will be reported as the Table Size in the + VF's MSI-X capability + * < 0 - not valid + * = 0 - will reset to the device default value + + The file is writable if the PF is bound to a driver that + implements ->sriov_set_msix_vec_count(). + +What: /sys/bus/pci/devices/.../resourceN_resize +Date: September 2022 +Contact: Alex Williamson +Description: + These files provide an interface to PCIe Resizable BAR support. + A file is created for each BAR resource (N) supported by the + PCIe Resizable BAR extended capability of the device. Reading + each file exposes the bitmap of available resource sizes: + + # cat resource1_resize + 00000000000001c0 + + The bitmap represents supported resource sizes for the BAR, + where bit0 = 1MB, bit1 = 2MB, bit2 = 4MB, etc. In the above + example the device supports 64MB, 128MB, and 256MB BAR sizes. + + When writing the file, the user provides the bit position of + the desired resource size, for example: + + # echo 7 > resource1_resize + + This indicates to set the size value corresponding to bit 7, + 128MB. The resulting size is 2 ^ (bit# + 20). This definition + matches the PCIe specification of this capability. + + In order to make use of resource resizing, all PCI drivers must + be unbound from the device and peer devices under the same + parent bridge may need to be soft removed. In the case of + VGA devices, writing a resize value will remove low level + console drivers from the device. Raw users of pci-sysfs + resourceN attributes must be terminated prior to resizing. + Success of the resizing operation is not guaranteed. diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-aer_stats b/Documentation/ABI/testing/sysfs-bus-pci-devices-aer_stats new file mode 100644 index 000000000..860db5303 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-aer_stats @@ -0,0 +1,119 @@ +PCIe Device AER statistics +-------------------------- + +These attributes show up under all the devices that are AER capable. These +statistical counters indicate the errors "as seen/reported by the device". +Note that this may mean that if an endpoint is causing problems, the AER +counters may increment at its link partner (e.g. root port) because the +errors may be "seen" / reported by the link partner and not the +problematic endpoint itself (which may report all counters as 0 as it never +saw any problems). + +What: /sys/bus/pci/devices//aer_dev_correctable +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: List of correctable errors seen and reported by this + PCI device using ERR_COR. Note that since multiple errors may + be reported using a single ERR_COR message, thus + TOTAL_ERR_COR at the end of the file may not match the actual + total of all the errors in the file. Sample output:: + + localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_correctable + Receiver Error 2 + Bad TLP 0 + Bad DLLP 0 + RELAY_NUM Rollover 0 + Replay Timer Timeout 0 + Advisory Non-Fatal 0 + Corrected Internal Error 0 + Header Log Overflow 0 + TOTAL_ERR_COR 2 + +What: /sys/bus/pci/devices//aer_dev_fatal +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: List of uncorrectable fatal errors seen and reported by this + PCI device using ERR_FATAL. Note that since multiple errors may + be reported using a single ERR_FATAL message, thus + TOTAL_ERR_FATAL at the end of the file may not match the actual + total of all the errors in the file. Sample output:: + + localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_fatal + Undefined 0 + Data Link Protocol 0 + Surprise Down Error 0 + Poisoned TLP 0 + Flow Control Protocol 0 + Completion Timeout 0 + Completer Abort 0 + Unexpected Completion 0 + Receiver Overflow 0 + Malformed TLP 0 + ECRC 0 + Unsupported Request 0 + ACS Violation 0 + Uncorrectable Internal Error 0 + MC Blocked TLP 0 + AtomicOp Egress Blocked 0 + TLP Prefix Blocked Error 0 + TOTAL_ERR_FATAL 0 + +What: /sys/bus/pci/devices//aer_dev_nonfatal +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: List of uncorrectable nonfatal errors seen and reported by this + PCI device using ERR_NONFATAL. Note that since multiple errors + may be reported using a single ERR_FATAL message, thus + TOTAL_ERR_NONFATAL at the end of the file may not match the + actual total of all the errors in the file. Sample output:: + + localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_nonfatal + Undefined 0 + Data Link Protocol 0 + Surprise Down Error 0 + Poisoned TLP 0 + Flow Control Protocol 0 + Completion Timeout 0 + Completer Abort 0 + Unexpected Completion 0 + Receiver Overflow 0 + Malformed TLP 0 + ECRC 0 + Unsupported Request 0 + ACS Violation 0 + Uncorrectable Internal Error 0 + MC Blocked TLP 0 + AtomicOp Egress Blocked 0 + TLP Prefix Blocked Error 0 + TOTAL_ERR_NONFATAL 0 + +PCIe Rootport AER statistics +---------------------------- + +These attributes show up under only the rootports (or root complex event +collectors) that are AER capable. These indicate the number of error messages as +"reported to" the rootport. Please note that the rootports also transmit +(internally) the ERR_* messages for errors seen by the internal rootport PCI +device, so these counters include them and are thus cumulative of all the error +messages on the PCI hierarchy originating at that root port. + +What: /sys/bus/pci/devices//aer_stats/aer_rootport_total_err_cor +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: Total number of ERR_COR messages reported to rootport. + +What: /sys/bus/pci/devices//aer_stats/aer_rootport_total_err_fatal +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: Total number of ERR_FATAL messages reported to rootport. + +What: /sys/bus/pci/devices//aer_stats/aer_rootport_total_err_nonfatal +Date: July 2018 +KernelVersion: 4.19.0 +Contact: linux-pci@vger.kernel.org, rajatja@google.com +Description: Total number of ERR_NONFATAL messages reported to rootport. diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-catpt b/Documentation/ABI/testing/sysfs-bus-pci-devices-catpt new file mode 100644 index 000000000..f85db86d6 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-catpt @@ -0,0 +1,17 @@ +What: /sys/devices/pci0000:00//fw_version +Date: September 2020 +Contact: Cezary Rojewski +Description: + Version of AudioDSP firmware ASoC catpt driver is + communicating with. + + Format: %d.%d.%d.%d, type:major:minor:build. + +What: /sys/devices/pci0000:00//fw_info +Date: September 2020 +Contact: Cezary Rojewski +Description: + Detailed AudioDSP firmware build information including + build hash and log-providers hash. This information is + obtained during initial handshake with firmware. + Format: %s. diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss new file mode 100644 index 000000000..92a94e106 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss @@ -0,0 +1,80 @@ +What: /sys/bus/pci/devices//ccissX/cXdY/model +Date: March 2009 +KernelVersion: 2.6.30 +Contact: iss_storagedev@hp.com +Description: Displays the SCSI INQUIRY page 0 model for logical drive + Y of controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/rev +Date: March 2009 +KernelVersion: 2.6.30 +Contact: iss_storagedev@hp.com +Description: Displays the SCSI INQUIRY page 0 revision for logical + drive Y of controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/unique_id +Date: March 2009 +KernelVersion: 2.6.30 +Contact: iss_storagedev@hp.com +Description: Displays the SCSI INQUIRY page 83 serial number for logical + drive Y of controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/vendor +Date: March 2009 +KernelVersion: 2.6.30 +Contact: iss_storagedev@hp.com +Description: Displays the SCSI INQUIRY page 0 vendor for logical drive + Y of controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/block:cciss!cXdY +Date: March 2009 +KernelVersion: 2.6.30 +Contact: iss_storagedev@hp.com +Description: A symbolic link to /sys/block/cciss!cXdY + +What: /sys/bus/pci/devices//ccissX/rescan +Date: August 2009 +KernelVersion: 2.6.31 +Contact: iss_storagedev@hp.com +Description: Kicks of a rescan of the controller to discover logical + drive topology changes. + +What: /sys/bus/pci/devices//ccissX/cXdY/lunid +Date: August 2009 +KernelVersion: 2.6.31 +Contact: iss_storagedev@hp.com +Description: Displays the 8-byte LUN ID used to address logical + drive Y of controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/raid_level +Date: August 2009 +KernelVersion: 2.6.31 +Contact: iss_storagedev@hp.com +Description: Displays the RAID level of logical drive Y of + controller X. + +What: /sys/bus/pci/devices//ccissX/cXdY/usage_count +Date: August 2009 +KernelVersion: 2.6.31 +Contact: iss_storagedev@hp.com +Description: Displays the usage count (number of opens) of logical drive Y + of controller X. + +What: /sys/bus/pci/devices//ccissX/resettable +Date: February 2011 +KernelVersion: 2.6.38 +Contact: iss_storagedev@hp.com +Description: Value of 1 indicates the controller can honor the reset_devices + kernel parameter. Value of 0 indicates reset_devices cannot be + honored. This is to allow, for example, kexec tools to be able + to warn the user if they designate an unresettable device as + a dump device, as kdump requires resetting the device in order + to work reliably. + +What: /sys/bus/pci/devices//ccissX/transport_mode +Date: July 2011 +KernelVersion: 3.0 +Contact: iss_storagedev@hp.com +Description: Value of "simple" indicates that the controller has been placed + in "simple mode". Value of "performant" indicates that the + controller has been placed in "performant mode". diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-pvpanic b/Documentation/ABI/testing/sysfs-bus-pci-devices-pvpanic new file mode 100644 index 000000000..4ec03cd36 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-pvpanic @@ -0,0 +1,26 @@ +What: /sys/devices/pci0000:00/*/QEMU0001:00/capability for MMIO + /sys/bus/pci/drivers/pvpanic-pci/0000:00:0*.0/capability for PCI +Date: Jan 2021 +Contact: zhenwei pi +Description: + Read-only attribute. Capabilities of pvpanic device which + are supported by QEMU. + + Format: %x. + + Detailed bit definition refers to section + from pvpanic device specification: + https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/specs/pvpanic.txt + +What: /sys/devices/pci0000:00/*/QEMU0001:00/events + /sys/bus/pci/drivers/pvpanic-pci/0000:00:0*.0/events for PCI +Date: Jan 2021 +Contact: zhenwei pi +Description: + RW attribute. Set/get which features in-use. This attribute + is used to enable/disable feature(s) of pvpanic device. + Notice that this value should be a subset of capability. + + Format: %x. + + Also refer to pvpanic device specification. diff --git a/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd b/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd new file mode 100644 index 000000000..c90d97a80 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd @@ -0,0 +1,46 @@ +What: /sys/bus/pci/drivers/ehci_hcd/.../companion + /sys/bus/usb/devices/usbN/../companion +Date: January 2007 +KernelVersion: 2.6.21 +Contact: Alan Stern +Description: + PCI-based EHCI USB controllers (i.e., high-speed USB-2.0 + controllers) are often implemented along with a set of + "companion" full/low-speed USB-1.1 controllers. When a + high-speed device is plugged in, the connection is routed + to the EHCI controller; when a full- or low-speed device + is plugged in, the connection is routed to the companion + controller. + + Sometimes you want to force a high-speed device to connect + at full speed, which can be accomplished by forcing the + connection to be routed to the companion controller. + That's what this file does. Writing a port number to the + file causes connections on that port to be routed to the + companion controller, and writing the negative of a port + number returns the port to normal operation. + + For example: To force the high-speed device attached to + port 4 on bus 2 to run at full speed:: + + echo 4 >/sys/bus/usb/devices/usb2/../companion + + To return the port to high-speed operation:: + + echo -4 >/sys/bus/usb/devices/usb2/../companion + + Reading the file gives the list of ports currently forced + to the companion controller. + + Note: Some EHCI controllers do not have companions; they + may contain an internal "transaction translator" or they + may be attached directly to a "rate-matching hub". This + mechanism will not work with such controllers. Also, it + cannot be used to force a port on a high-speed hub to + connect at full speed. + + Note: When this file was first added, it appeared in a + different sysfs directory. The location given above is + correct for 2.6.35 (and probably several earlier kernel + versions as well). + diff --git a/Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio b/Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio new file mode 100644 index 000000000..4d08f28dc --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio @@ -0,0 +1,8 @@ +What: /sys/bus/pci/drivers/janz-cmodio/.../modulbus_number +Date: May 2010 +KernelVersion: 2.6.35 +Contact: Ira W. Snyder +Description: + Value representing the HEX switch S2 of the janz carrier board CMOD-IO or CAN-PCI2 + + Read-only: value of the configuration switch (0..15) diff --git a/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd b/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd new file mode 100644 index 000000000..0088aba4c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd @@ -0,0 +1,25 @@ +What: /sys/bus/pci/drivers/xhci_hcd/.../dbc +Date: June 2017 +Contact: Lu Baolu +Description: + xHCI compatible USB host controllers (i.e. super-speed + USB3 controllers) are often implemented with the Debug + Capability (DbC). It can present a debug device which + is fully compliant with the USB framework and provides + the equivalent of a very high performance full-duplex + serial link for debug purpose. + + The DbC debug device shares a root port with xHCI host. + When the DbC is enabled, the root port will be assigned + to the Debug Capability. Otherwise, it will be assigned + to xHCI. + + Writing "enable" to this attribute will enable the DbC + functionality and the shared root port will be assigned + to the DbC device. Writing "disable" to this attribute + will disable the DbC functionality and the shared root + port will roll back to the xHCI. + + Reading this attribute gives the state of the DbC. It + can be one of the following states: disabled, enabled, + initialized, connected, configured and stalled. diff --git a/Documentation/ABI/testing/sysfs-bus-peci b/Documentation/ABI/testing/sysfs-bus-peci new file mode 100644 index 000000000..87454ec5d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-peci @@ -0,0 +1,16 @@ +What: /sys/bus/peci/rescan +Date: July 2021 +KernelVersion: 5.18 +Contact: Iwona Winiarska +Description: + Writing a non-zero value to this attribute will + initiate scan for PECI devices on all PECI controllers + in the system. + +What: /sys/bus/peci/devices/-/remove +Date: July 2021 +KernelVersion: 5.18 +Contact: Iwona Winiarska +Description: + Writing a non-zero value to this attribute will + remove the PECI device and any of its children. diff --git a/Documentation/ABI/testing/sysfs-bus-platform b/Documentation/ABI/testing/sysfs-bus-platform new file mode 100644 index 000000000..c4dfe7355 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-platform @@ -0,0 +1,56 @@ +What: /sys/bus/platform/devices/.../driver_override +Date: April 2014 +Contact: Kim Phillips +Description: + This file allows the driver for a device to be specified which + will override standard OF, ACPI, ID table, and name matching. + When specified, only a driver with a name matching the value + written to driver_override will have an opportunity to bind + to the device. The override is specified by writing a string + to the driver_override file (echo vfio-platform > \ + driver_override) and may be cleared with an empty string + (echo > driver_override). This returns the device to standard + matching rules binding. Writing to driver_override does not + automatically unbind the device from its current driver or make + any attempt to automatically load the specified driver. If no + driver with a matching name is currently loaded in the kernel, + the device will not bind to any driver. This also allows + devices to opt-out of driver binding using a driver_override + name such as "none". Only a single driver may be specified in + the override, there is no support for parsing delimiters. + +What: /sys/bus/platform/devices/.../numa_node +Date: June 2020 +Contact: Barry Song +Description: + This file contains the NUMA node to which the platform device + is attached. It won't be visible if the node is unknown. The + value comes from an ACPI _PXM method or a similar firmware + source. Initial users for this file would be devices like + arm smmu which are populated by arm64 acpi_iort. + +What: /sys/bus/platform/devices/.../msi_irqs/ +Date: August 2021 +Contact: Barry Song +Description: + The /sys/devices/.../msi_irqs directory contains a variable set + of files, with each file being named after a corresponding msi + irq vector allocated to that device. + +What: /sys/bus/platform/devices/.../msi_irqs/ +Date: August 2021 +Contact: Barry Song +Description: + This attribute will show "msi" if is a valid msi irq + +What: /sys/bus/platform/devices/.../modalias +Description: + Same as MODALIAS in the uevent at device creation. + + A platform device that it is exposed via devicetree uses: + + - of:N`of node name`T`type` + + Other platform devices use, instead: + + - platform:`driver name` diff --git a/Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon b/Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon new file mode 100644 index 000000000..b24d7ab02 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon @@ -0,0 +1,13 @@ +What: /sys/bus/platform/devices/occ-hwmon.X/ffdc +KernelVersion: 5.15 +Contact: eajames@linux.ibm.com +Description: + Contains the First Failure Data Capture from the SBEFIFO + hardware, if there is any from a previous transfer. Otherwise, + the file is empty. The data is cleared when it's been + completely read by a user. As the name suggests, only the data + from the first error is saved, until it's cleared upon read. The OCC hwmon driver, running on + a Baseboard Management Controller (BMC), communicates with + POWER9 and up processors over the Self-Boot Engine (SBE) FIFO. + In many error conditions, the SBEFIFO will return error data + indicating the type of error and system state, etc. diff --git a/Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub b/Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub new file mode 100644 index 000000000..42deb0552 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub @@ -0,0 +1,8 @@ +What: /sys/bus/platform/devices//always_powered_in_suspend +Date: June 2022 +KernelVersion: 5.20 +Contact: Matthias Kaehlcke + linux-usb@vger.kernel.org +Description: + (RW) Controls whether the USB hub remains always powered + during system suspend or not. \ No newline at end of file diff --git a/Documentation/ABI/testing/sysfs-bus-rapidio b/Documentation/ABI/testing/sysfs-bus-rapidio new file mode 100644 index 000000000..f8b6728da --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-rapidio @@ -0,0 +1,201 @@ +What: /sys/bus/rapidio/devices/:: +Description: + For each RapidIO device, the RapidIO subsystem creates files in + an individual subdirectory with the following name format of + device_name "nn:d:iiii", where: + + ==== ======================================================== + nn two-digit hexadecimal ID of RapidIO network where the + device resides + d device type: 'e' - for endpoint or 's' - for switch + iiii four-digit device destID for endpoints, or switchID for + switches + ==== ======================================================== + + For example, below is a list of device directories that + represents a typical RapidIO network with one switch, one host, + and two agent endpoints, as it is seen by the enumerating host + (with destID = 1):: + + /sys/bus/rapidio/devices/00:e:0000 + /sys/bus/rapidio/devices/00:e:0002 + /sys/bus/rapidio/devices/00:s:0001 + + NOTE: + An enumerating or discovering endpoint does not create a + sysfs entry for itself, this is why an endpoint with destID=1 + is not shown in the list. + +Attributes Common for All RapidIO Devices +----------------------------------------- + +What: /sys/bus/rapidio/devices/::/did +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns the device identifier + +What: /sys/bus/rapidio/devices/::/vid +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns the device vendor identifier + +What: /sys/bus/rapidio/devices/::/device_rev +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns the device revision level + +What: /sys/bus/rapidio/devices/::/asm_did +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns identifier for the assembly containing the device + +What: /sys/bus/rapidio/devices/::/asm_rev +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns revision level of the assembly containing the + device + +What: /sys/bus/rapidio/devices/::/asm_vid +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns vendor identifier of the assembly containing the + device + +What: /sys/bus/rapidio/devices/::/destid +Date: Mar, 2011 +KernelVersion: v2.6.3 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns device destination ID assigned by the enumeration + routine + +What: /sys/bus/rapidio/devices/::/lprev +Date: Mar, 2011 +KernelVersion: v2.6.39 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns name of previous device (switch) on the path to the + device that that owns this attribute + +What: /sys/bus/rapidio/devices/::/modalias +Date: Jul, 2013 +KernelVersion: v3.11 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns the device modalias + +What: /sys/bus/rapidio/devices/::/config +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RW) Binary attribute to read from and write to the device + configuration registers using the RapidIO maintenance + transactions. This attribute is similar in behaviour to the + "config" attribute of PCI devices and provides an access to the + RapidIO device registers using standard file read and write + operations. + +RapidIO Switch Device Attributes +-------------------------------- + +RapidIO switches have additional attributes in sysfs. RapidIO subsystem supports +common and device-specific sysfs attributes for switches. Because switches are +integrated into the RapidIO subsystem, it offers a method to create +device-specific sysfs attributes by specifying a callback function that may be +set by the switch initialization routine during enumeration or discovery +process. + +What: /sys/bus/rapidio/devices/::/routes +Date: Nov, 2005 +KernelVersion: v2.6.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) reports switch routing information in "destID port" format. + This attribute reports only valid routing table entries, one + line for each entry. + +What: /sys/bus/rapidio/devices/::/destid +Date: Mar, 2011 +KernelVersion: v2.6.3 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) device destination ID of the associated device that defines + a route to the switch + +What: /sys/bus/rapidio/devices/::/hopcount +Date: Mar, 2011 +KernelVersion: v2.6.39 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) number of hops on the path to the switch + +What: /sys/bus/rapidio/devices/::/lnext +Date: Mar, 2011 +KernelVersion: v2.6.39 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) returns names of devices linked to the switch except one of + a device linked to the ingress port (reported as "lprev"). This + is an array names with number of lines equal to number of ports + in switch. If a switch port has no attached device, returns + "null" instead of a device name. + +Device-specific Switch Attributes +--------------------------------- + +IDT_GEN2- + +What: /sys/bus/rapidio/devices/::/errlog +Date: Oct, 2010 +KernelVersion: v2.6.37 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) reads contents of device error log until it is empty. + +RapidIO Bus Attributes +---------------------- + +What: /sys/bus/rapidio/scan +Date: May, 2013 +KernelVersion: v3.11 +Contact: Matt Porter , + Alexandre Bounine +Description: + (WO) Allows to trigger enumeration discovery process from user + space. To initiate an enumeration or discovery process on + specific mport device, a user needs to write mport_ID (not + RapidIO destination ID) into this file. The mport_ID is a + sequential number (0 ... RIO_MAX_MPORTS) assigned to the mport + device. For example, for a machine with a single RapidIO + controller, mport_ID for that controller always will be 0. To + initiate RapidIO enumeration/discovery on all available mports a + user must write '-1' (or RIO_MPORT_ANY) into this attribute + file. diff --git a/Documentation/ABI/testing/sysfs-bus-rbd b/Documentation/ABI/testing/sysfs-bus-rbd new file mode 100644 index 000000000..417a2fe21 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-rbd @@ -0,0 +1,173 @@ +What: /sys/bus/rbd/add +Date: Oct, 2010 +KernelVersion: v2.6.37 +Contact: Sage Weil +Description: + (WO) Add rbd block device. + + Usage: [] + + Example:: + + $ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add + + The snapshot name can be "-" or omitted to map the image + read/write. A will be assigned for any registered block + device. If snapshot is used, it will be mapped read-only. + + +What: /sys/bus/rbd/remove +Date: Oct, 2010 +KernelVersion: v2.6.37 +Contact: Sage Weil +Description: + (WO) Remove rbd block device. + + Usage: [force] + + Example:: + + $ echo 2 > /sys/bus/rbd/remove + + Optional "force" argument which when passed will wait for + running requests and then unmap the image. Requests sent to the + driver after initiating the removal will be failed. (August + 2016, since 4.9.) + + +What: /sys/bus/rbd/add_single_major +Date: Dec, 2013 +KernelVersion: v3.14 +Contact: Sage Weil +Description: + (WO) Available only if rbd module is inserted with single_major + parameter set to true. + + Usage is the same as for /sys/bus/rbd/add. If present, this + should be used instead of the latter: any attempts to use + /sys/bus/rbd/add if /sys/bus/rbd/add_single_major is available + will fail for backwards compatibility reasons. + + +What: /sys/bus/rbd/remove_single_major +Date: Dec, 2013 +KernelVersion: v3.14 +Contact: Sage Weil +Description: + (WO) Available only if rbd module is inserted with single_major + parameter set to true. + + Usage is the same as for /sys/bus/rbd/remove. If present, this + should be used instead of the latter: any attempts to use + /sys/bus/rbd/remove if /sys/bus/rbd/remove_single_major is + available will fail for backwards compatibility reasons. + + +What: /sys/bus/rbd/supported_features +Date: Mar, 2017 +KernelVersion: v4.11 +Contact: Sage Weil +Description: + (RO) Displays the features supported by the rbd module so that + userspace can generate meaningful error messages and spell out + unsupported features that need to be disabled. + + +What: /sys/bus/rbd/devices//size +What: /sys/bus/rbd/devices//major +What: /sys/bus/rbd/devices//client_id +What: /sys/bus/rbd/devices//pool +What: /sys/bus/rbd/devices//name +What: /sys/bus/rbd/devices//refresh +What: /sys/bus/rbd/devices//current_snap +Date: Oct, 2010 +KernelVersion: v2.6.37 +Contact: Sage Weil +Description: + + ============== ================================================ + size (RO) The size (in bytes) of the mapped block + device. + + major (RO) The block device major number. + + client_id (RO) The ceph unique client id that was assigned + for this specific session. + + pool (RO) The name of the storage pool where this rbd + image resides. An rbd image name is unique + within its pool. + + name (RO) The name of the rbd image. + + refresh (WO) Writing to this file will reread the image + header data and set all relevant data structures + accordingly. + + current_snap (RO) The current snapshot for which the device + is mapped. + ============== ================================================ + + +What: /sys/bus/rbd/devices//pool_id +Date: Jul, 2012 +KernelVersion: v3.6 +Contact: Sage Weil +Description: + (RO) The unique identifier for the rbd image's pool. This is a + permanent attribute of the pool. A pool's id will never change. + + +What: /sys/bus/rbd/devices//image_id +What: /sys/bus/rbd/devices//features +Date: Oct, 2012 +KernelVersion: v3.7 +Contact: Sage Weil +Description: + ========= =============================================== + image_id (RO) The unique id for the rbd image. (For rbd + image format 1 this is empty.) + + features (RO) A hexadecimal encoding of the feature bits + for this image. + ========= =============================================== + + +What: /sys/bus/rbd/devices//parent +Date: Nov, 2012 +KernelVersion: v3.8 +Contact: Sage Weil +Description: + (RO) Information identifying the chain of parent images in a + layered rbd image. Entries are separated by empty lines. + + +What: /sys/bus/rbd/devices//minor +Date: Dec, 2013 +KernelVersion: v3.14 +Contact: Sage Weil +Description: + (RO) The block device minor number. + + +What: /sys/bus/rbd/devices//snap_id +What: /sys/bus/rbd/devices//config_info +What: /sys/bus/rbd/devices//cluster_fsid +What: /sys/bus/rbd/devices//client_addr +Date: Aug, 2016 +KernelVersion: v4.9 +Contact: Sage Weil +Description: + ============ ================================================ + snap_id (RO) The current snapshot's id. + + config_info (RO) The string written into + /sys/bus/rbd/add{,_single_major}. + + cluster_fsid (RO) The ceph cluster UUID. + + client_addr (RO) The ceph unique client + entity_addr_t (address + nonce). The format is +
:/: '1.2.3.4:1234/5678' or + '[1:2:3:4:5:6:7:8]:1234/5678'. + ============ ================================================ diff --git a/Documentation/ABI/testing/sysfs-bus-rpmsg b/Documentation/ABI/testing/sysfs-bus-rpmsg new file mode 100644 index 000000000..990fcc420 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-rpmsg @@ -0,0 +1,95 @@ +What: /sys/bus/rpmsg/devices/.../name +Date: June 2011 +KernelVersion: 3.3 +Contact: Ohad Ben-Cohen +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels are identified with a (textual) name, + which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in + rpmsg.h). + + This sysfs entry contains the name of this channel. + +What: /sys/bus/rpmsg/devices/.../src +Date: June 2011 +KernelVersion: 3.3 +Contact: Ohad Ben-Cohen +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels have a local ("source") rpmsg address, + and remote ("destination") rpmsg address. When an entity + starts listening on one end of a channel, it assigns it with + a unique rpmsg address (a 32 bits integer). This way when + inbound messages arrive to this address, the rpmsg core + dispatches them to the listening entity (a kernel driver). + + This sysfs entry contains the src (local) rpmsg address + of this channel. If it contains 0xffffffff, then an address + wasn't assigned (can happen if no driver exists for this + channel). + +What: /sys/bus/rpmsg/devices/.../dst +Date: June 2011 +KernelVersion: 3.3 +Contact: Ohad Ben-Cohen +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels have a local ("source") rpmsg address, + and remote ("destination") rpmsg address. When an entity + starts listening on one end of a channel, it assigns it with + a unique rpmsg address (a 32 bits integer). This way when + inbound messages arrive to this address, the rpmsg core + dispatches them to the listening entity. + + This sysfs entry contains the dst (remote) rpmsg address + of this channel. If it contains 0xffffffff, then an address + wasn't assigned (can happen if the kernel driver that + is attached to this channel is exposing a service to the + remote processor. This make it a local rpmsg server, + and it is listening for inbound messages that may be sent + from any remote rpmsg client; it is not bound to a single + remote entity). + +What: /sys/bus/rpmsg/devices/.../announce +Date: June 2011 +KernelVersion: 3.3 +Contact: Ohad Ben-Cohen +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels are identified by a textual name (see + /sys/bus/rpmsg/devices/.../name above) and have a local + ("source") rpmsg address, and remote ("destination") rpmsg + address. + + A channel is first created when an entity, whether local + or remote, starts listening on it for messages (and is thus + called an rpmsg server). + + When that happens, a "name service" announcement is sent + to the other processor, in order to let it know about the + creation of the channel (this way remote clients know they + can start sending messages). + + This sysfs entry tells us whether the channel is a local + server channel that is announced (values are either + true or false). + +What: /sys/bus/rpmsg/devices/.../driver_override +Date: April 2018 +KernelVersion: 4.18 +Contact: Bjorn Andersson +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels are identified by a textual name (see + /sys/bus/rpmsg/devices/.../name above) and have a local + ("source") rpmsg address, and remote ("destination") rpmsg + address. + + The listening entity (or client) which communicates with a + remote processor is referred as rpmsg driver. The rpmsg device + and rpmsg driver are matched based on rpmsg device name and + rpmsg driver ID table. + + This sysfs entry allows the rpmsg driver for a rpmsg device + to be specified which will override standard OF, ID table + and name matching. diff --git a/Documentation/ABI/testing/sysfs-bus-siox b/Documentation/ABI/testing/sysfs-bus-siox new file mode 100644 index 000000000..50e80238f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-siox @@ -0,0 +1,90 @@ +What: /sys/bus/siox/devices/siox-X/active +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + On reading represents the current state of the bus. If it + contains a "0" the bus is stopped and connected devices are + expected to not do anything because their watchdog triggered. + When the file contains a "1" the bus is operated and periodically + does a push-pull cycle to write and read data from the + connected devices. + + When writing a "0" or "1" the bus moves to the described state. + +What: /sys/bus/siox/devices/siox-X/device_add +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Write-only file. Write + + + + to add a new device dynamically. is the name that is used to match + to a driver (similar to the platform bus). and define + the length of the input and output shift register in bytes respectively. + + defines the 4 bit device type that is check to identify connection + problems. + + The new device is added to the end of the existing chain. + +What: /sys/bus/siox/devices/siox-X/device_remove +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Write-only file. A single write removes the last device in the siox chain. + +What: /sys/bus/siox/devices/siox-X/poll_interval_ns +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Defines the interval between two poll cycles in nano seconds. + Note this is rounded to jiffies on writing. On reading the current value + is returned. + +What: /sys/bus/siox/devices/siox-X-Y/connected +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value. "0" means the Yth device on siox bus X isn't "connected" i.e. + communication with it is not ensured. "1" signals a working connection. + +What: /sys/bus/siox/devices/siox-X-Y/inbytes +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value reporting the inbytes value provided to siox-X/device_add + +What: /sys/bus/siox/devices/siox-X-Y/status_errors +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Counts the number of time intervals when the read status byte doesn't yield the + expected value. + +What: /sys/bus/siox/devices/siox-X-Y/type +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value reporting the type value provided to siox-X/device_add. + +What: /sys/bus/siox/devices/siox-X-Y/watchdog +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value reporting if the watchdog of the siox device is + active. "0" means the watchdog is not active and the device is expected to + be operational. "1" means the watchdog keeps the device in reset. + +What: /sys/bus/siox/devices/siox-X-Y/watchdog_errors +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value reporting the number to time intervals when the + watchdog was active. + +What: /sys/bus/siox/devices/siox-X-Y/outbytes +KernelVersion: 4.16 +Contact: Thorsten Scherer , Uwe Kleine-König +Description: + Read-only value reporting the outbytes value provided to siox-X/device_add. diff --git a/Documentation/ABI/testing/sysfs-bus-soundwire-master b/Documentation/ABI/testing/sysfs-bus-soundwire-master new file mode 100644 index 000000000..d2342911f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-soundwire-master @@ -0,0 +1,23 @@ +What: /sys/bus/soundwire/devices/sdw-master-/revision + /sys/bus/soundwire/devices/sdw-master-/clk_stop_modes + /sys/bus/soundwire/devices/sdw-master-/clk_freq + /sys/bus/soundwire/devices/sdw-master-/clk_gears + /sys/bus/soundwire/devices/sdw-master-/default_col + /sys/bus/soundwire/devices/sdw-master-/default_frame_rate + /sys/bus/soundwire/devices/sdw-master-/default_row + /sys/bus/soundwire/devices/sdw-master-/dynamic_shape + /sys/bus/soundwire/devices/sdw-master-/err_threshold + /sys/bus/soundwire/devices/sdw-master-/max_clk_freq + +Date: April 2020 + +Contact: Pierre-Louis Bossart + Bard Liao + Vinod Koul + +Description: SoundWire Master-N DisCo properties. + These properties are defined by MIPI DisCo Specification + for SoundWire. They define various properties of the Master + and are used by the bus to configure the Master. clk_stop_modes + is a bitmask for simplifications and combines the + clock-stop-mode0 and clock-stop-mode1 properties. diff --git a/Documentation/ABI/testing/sysfs-bus-soundwire-slave b/Documentation/ABI/testing/sysfs-bus-soundwire-slave new file mode 100644 index 000000000..fbf55834d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-soundwire-slave @@ -0,0 +1,109 @@ +What: /sys/bus/soundwire/devices/sdw:.../status + /sys/bus/soundwire/devices/sdw:.../device_number + +Date: September 2020 + +Contact: Pierre-Louis Bossart + Bard Liao + Vinod Koul + +Description: SoundWire Slave status + + These properties report the Slave status, e.g. if it + is UNATTACHED or not, and in the latter case show the + device_number. This status information is useful to + detect devices exposed by platform firmware but not + physically present on the bus, and conversely devices + not exposed in platform firmware but enumerated. + +What: /sys/bus/soundwire/devices/sdw:.../dev-properties/mipi_revision + /sys/bus/soundwire/devices/sdw:.../dev-properties/wake_capable + /sys/bus/soundwire/devices/sdw:.../dev-properties/test_mode_capable + /sys/bus/soundwire/devices/sdw:.../dev-properties/clk_stop_mode1 + /sys/bus/soundwire/devices/sdw:.../dev-properties/simple_clk_stop_capable + /sys/bus/soundwire/devices/sdw:.../dev-properties/clk_stop_timeout + /sys/bus/soundwire/devices/sdw:.../dev-properties/ch_prep_timeout + /sys/bus/soundwire/devices/sdw:.../dev-properties/reset_behave + /sys/bus/soundwire/devices/sdw:.../dev-properties/high_PHY_capable + /sys/bus/soundwire/devices/sdw:.../dev-properties/paging_support + /sys/bus/soundwire/devices/sdw:.../dev-properties/bank_delay_support + /sys/bus/soundwire/devices/sdw:.../dev-properties/p15_behave + /sys/bus/soundwire/devices/sdw:.../dev-properties/master_count + /sys/bus/soundwire/devices/sdw:.../dev-properties/source_ports + /sys/bus/soundwire/devices/sdw:.../dev-properties/sink_ports + +Date: May 2020 + +Contact: Pierre-Louis Bossart + Bard Liao + Vinod Koul + +Description: SoundWire Slave DisCo properties. + These properties are defined by MIPI DisCo Specification + for SoundWire. They define various properties of the + SoundWire Slave and are used by the bus to configure + the Slave + + +What: /sys/bus/soundwire/devices/sdw:.../dp0/max_word + /sys/bus/soundwire/devices/sdw:.../dp0/min_word + /sys/bus/soundwire/devices/sdw:.../dp0/words + /sys/bus/soundwire/devices/sdw:.../dp0/BRA_flow_controlled + /sys/bus/soundwire/devices/sdw:.../dp0/simple_ch_prep_sm + /sys/bus/soundwire/devices/sdw:.../dp0/imp_def_interrupts + +Date: May 2020 + +Contact: Pierre-Louis Bossart + Bard Liao + Vinod Koul + +Description: SoundWire Slave Data Port-0 DisCo properties. + These properties are defined by MIPI DisCo Specification + for the SoundWire. They define various properties of the + Data port 0 are used by the bus to configure the Data Port 0. + + +What: /sys/bus/soundwire/devices/sdw:.../dp_src/max_word + /sys/bus/soundwire/devices/sdw:.../dp_src/min_word + /sys/bus/soundwire/devices/sdw:.../dp_src/words + /sys/bus/soundwire/devices/sdw:.../dp_src/type + /sys/bus/soundwire/devices/sdw:.../dp_src/max_grouping + /sys/bus/soundwire/devices/sdw:.../dp_src/simple_ch_prep_sm + /sys/bus/soundwire/devices/sdw:.../dp_src/ch_prep_timeout + /sys/bus/soundwire/devices/sdw:.../dp_src/imp_def_interrupts + /sys/bus/soundwire/devices/sdw:.../dp_src/min_ch + /sys/bus/soundwire/devices/sdw:.../dp_src/max_ch + /sys/bus/soundwire/devices/sdw:.../dp_src/channels + /sys/bus/soundwire/devices/sdw:.../dp_src/ch_combinations + /sys/bus/soundwire/devices/sdw:.../dp_src/max_async_buffer + /sys/bus/soundwire/devices/sdw:.../dp_src/block_pack_mode + /sys/bus/soundwire/devices/sdw:.../dp_src/port_encoding + + /sys/bus/soundwire/devices/sdw:.../dp_sink/max_word + /sys/bus/soundwire/devices/sdw:.../dp_sink/min_word + /sys/bus/soundwire/devices/sdw:.../dp_sink/words + /sys/bus/soundwire/devices/sdw:.../dp_sink/type + /sys/bus/soundwire/devices/sdw:.../dp_sink/max_grouping + /sys/bus/soundwire/devices/sdw:.../dp_sink/simple_ch_prep_sm + /sys/bus/soundwire/devices/sdw:.../dp_sink/ch_prep_timeout + /sys/bus/soundwire/devices/sdw:.../dp_sink/imp_def_interrupts + /sys/bus/soundwire/devices/sdw:.../dp_sink/min_ch + /sys/bus/soundwire/devices/sdw:.../dp_sink/max_ch + /sys/bus/soundwire/devices/sdw:.../dp_sink/channels + /sys/bus/soundwire/devices/sdw:.../dp_sink/ch_combinations + /sys/bus/soundwire/devices/sdw:.../dp_sink/max_async_buffer + /sys/bus/soundwire/devices/sdw:.../dp_sink/block_pack_mode + /sys/bus/soundwire/devices/sdw:.../dp_sink/port_encoding + +Date: May 2020 + +Contact: Pierre-Louis Bossart + Bard Liao + Vinod Koul + +Description: SoundWire Slave Data Source/Sink Port-N DisCo properties. + These properties are defined by MIPI DisCo Specification + for SoundWire. They define various properties of the + Source/Sink Data port N and are used by the bus to configure + the Data Port N. diff --git a/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor b/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor new file mode 100644 index 000000000..e9ef69aef --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor @@ -0,0 +1,34 @@ +What: /sys/bus/spi/devices/.../spi-nor/jedec_id +Date: April 2021 +KernelVersion: 5.14 +Contact: linux-mtd@lists.infradead.org +Description: (RO) The JEDEC ID of the SPI NOR flash as reported by the + flash device. + + The attribute is not present if the flash doesn't support + the "Read JEDEC ID" command (9Fh). This is the case for + non-JEDEC compliant flashes. + +What: /sys/bus/spi/devices/.../spi-nor/manufacturer +Date: April 2021 +KernelVersion: 5.14 +Contact: linux-mtd@lists.infradead.org +Description: (RO) Manufacturer of the SPI NOR flash. + + +What: /sys/bus/spi/devices/.../spi-nor/partname +Date: April 2021 +KernelVersion: 5.14 +Contact: linux-mtd@lists.infradead.org +Description: (RO) Part name of the SPI NOR flash. + + +What: /sys/bus/spi/devices/.../spi-nor/sfdp +Date: April 2021 +KernelVersion: 5.14 +Contact: linux-mtd@lists.infradead.org +Description: (RO) This attribute is only present if the SPI NOR flash + device supports the "Read SFDP" command (5Ah). + + If present, it contains the complete SFDP (serial flash + discoverable parameters) binary data of the flash. diff --git a/Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw b/Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw new file mode 100644 index 000000000..74cd9d754 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw @@ -0,0 +1,57 @@ +What: /sys/bus/surface_aggregator/devices/01:0e:01:00:01/state +Date: July 2022 +KernelVersion: 5.20 +Contact: Maximilian Luz +Description: + This attribute returns a string with the current type-cover + or device posture, as indicated by the embedded controller. + Currently returned posture states are: + + - "disconnected": The type-cover has been disconnected. + + - "closed": The type-cover has been folded closed and lies on + top of the display. + + - "laptop": The type-cover is open and in laptop-mode, i.e., + ready for normal use. + + - "folded-canvas": The type-cover has been folded back + part-ways, but does not lie flush with the back side of the + device. In general, this means that the kick-stand is used + and extended atop of the cover. + + - "folded-back": The type cover has been fully folded back and + lies flush with the back side of the device. + + - "": The current state is unknown to the driver, for + example due to newer as-of-yet unsupported hardware. + + New states may be introduced with new hardware. Users therefore + must not rely on this list of states being exhaustive and + gracefully handle unknown states. + +What: /sys/bus/surface_aggregator/devices/01:26:01:00:01/state +Date: July 2022 +KernelVersion: 5.20 +Contact: Maximilian Luz +Description: + This attribute returns a string with the current device posture, as indicated by the embedded controller. Currently + returned posture states are: + + - "closed": The lid of the device is closed. + + - "laptop": The lid of the device is opened and the device + operates as a normal laptop. + + - "slate": The screen covers the keyboard or has been flipped + back and the device operates mainly based on touch input. + + - "tablet": The device operates as tablet and exclusively + relies on touch input (or external peripherals). + + - "": The current state is unknown to the driver, for + example due to newer as-of-yet unsupported hardware. + + New states may be introduced with new hardware. Users therefore + must not rely on this list of states being exhaustive and + gracefully handle unknown states. diff --git a/Documentation/ABI/testing/sysfs-bus-thunderbolt b/Documentation/ABI/testing/sysfs-bus-thunderbolt new file mode 100644 index 000000000..76ab3e1fe --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-thunderbolt @@ -0,0 +1,370 @@ +What: /sys/bus/thunderbolt/devices/.../domainX/boot_acl +Date: Jun 2018 +KernelVersion: 4.17 +Contact: thunderbolt-software@lists.01.org +Description: Holds a comma separated list of device unique_ids that + are allowed to be connected automatically during system + startup (e.g boot devices). The list always contains + maximum supported number of unique_ids where unused + entries are empty. This allows the userspace software + to determine how many entries the controller supports. + If there are multiple controllers, each controller has + its own ACL list and size may be different between the + controllers. + + System BIOS may have an option "Preboot ACL" or similar + that needs to be selected before this list is taken into + consideration. + + Software always updates a full list in each write. + + If a device is authorized automatically during boot its + boot attribute is set to 1. + +What: /sys/bus/thunderbolt/devices/.../domainX/deauthorization +Date: May 2021 +KernelVersion: 5.12 +Contact: Mika Westerberg +Description: This attribute tells whether the system supports + de-authorization of devices. Value of 1 means user can + de-authorize PCIe tunnel by writing 0 to authorized + attribute under each device. + +What: /sys/bus/thunderbolt/devices/.../domainX/iommu_dma_protection +Date: Mar 2019 +KernelVersion: 4.21 +Contact: thunderbolt-software@lists.01.org +Description: This attribute tells whether the system uses IOMMU + for DMA protection. Value of 1 means IOMMU is used 0 means + it is not (DMA protection is solely based on Thunderbolt + security levels). + +What: /sys/bus/thunderbolt/devices/.../domainX/security +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute holds current Thunderbolt security level + set by the system BIOS. Possible values are: + + ======= ================================================== + none All devices are automatically authorized + user Devices are only authorized based on writing + appropriate value to the authorized attribute + secure Require devices that support secure connect at + minimum. User needs to authorize each device. + dponly Automatically tunnel Display port (and USB). No + PCIe tunnels are created. + usbonly Automatically tunnel USB controller of the + connected Thunderbolt dock (and Display Port). All + PCIe links downstream of the dock are removed. + nopcie USB4 system where PCIe tunneling is disabled from + the BIOS. + ======= ================================================== + +What: /sys/bus/thunderbolt/devices/.../authorized +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute is used to authorize Thunderbolt devices + after they have been connected. If the device is not + authorized, no PCIe devices are available to the system. + + Contents of this attribute will be 0 when the device is not + yet authorized. + + Possible values are supported: + + == =================================================== + 0 The device will be de-authorized (only supported if + deauthorization attribute under domain contains 1) + 1 The device will be authorized and connected + == =================================================== + + When key attribute contains 32 byte hex string the possible + values are: + + == ======================================================== + 0 The device will be de-authorized (only supported if + deauthorization attribute under domain contains 1) + 1 The 32 byte hex string is added to the device NVM and + the device is authorized. + 2 Send a challenge based on the 32 byte hex string. If the + challenge response from device is valid, the device is + authorized. In case of failure errno will be ENOKEY if + the device did not contain a key at all, and + EKEYREJECTED if the challenge response did not match. + == ======================================================== + +What: /sys/bus/thunderbolt/devices/.../boot +Date: Jun 2018 +KernelVersion: 4.17 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains 1 if Thunderbolt device was already + authorized on boot and 0 otherwise. + +What: /sys/bus/thunderbolt/devices/.../generation +Date: Jan 2020 +KernelVersion: 5.5 +Contact: Christian Kellner +Description: This attribute contains the generation of the Thunderbolt + controller associated with the device. It will contain 4 + for USB4. + +What: /sys/bus/thunderbolt/devices/.../key +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: When a devices supports Thunderbolt secure connect it will + have this attribute. Writing 32 byte hex string changes + authorization to use the secure connection method instead. + Writing an empty string clears the key and regular connection + method can be used again. + +What: /sys/bus/thunderbolt/devices/.../device +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains id of this device extracted from + the device DROM. + +What: /sys/bus/thunderbolt/devices/.../device_name +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains name of this device extracted from + the device DROM. + +What: /sys/bus/thunderbolt/devices/.../maxhopid +Date: Jul 2021 +KernelVersion: 5.13 +Contact: Mika Westerberg +Description: Only set for XDomains. The maximum HopID the other host + supports as its input HopID. + +What: /sys/bus/thunderbolt/devices/.../rx_speed +Date: Jan 2020 +KernelVersion: 5.5 +Contact: Mika Westerberg +Description: This attribute reports the device RX speed per lane. + All RX lanes run at the same speed. + +What: /sys/bus/thunderbolt/devices/.../rx_lanes +Date: Jan 2020 +KernelVersion: 5.5 +Contact: Mika Westerberg +Description: This attribute reports number of RX lanes the device is + using simultaneously through its upstream port. + +What: /sys/bus/thunderbolt/devices/.../tx_speed +Date: Jan 2020 +KernelVersion: 5.5 +Contact: Mika Westerberg +Description: This attribute reports the TX speed per lane. + All TX lanes run at the same speed. + +What: /sys/bus/thunderbolt/devices/.../tx_lanes +Date: Jan 2020 +KernelVersion: 5.5 +Contact: Mika Westerberg +Description: This attribute reports number of TX lanes the device is + using simultaneously through its upstream port. + +What: /sys/bus/thunderbolt/devices/.../vendor +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains vendor id of this device extracted + from the device DROM. + +What: /sys/bus/thunderbolt/devices/.../vendor_name +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains vendor name of this device extracted + from the device DROM. + +What: /sys/bus/thunderbolt/devices/.../unique_id +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: This attribute contains unique_id string of this device. + This is either read from hardware registers (UUID on + newer hardware) or based on UID from the device DROM. + Can be used to uniquely identify particular device. + +What: /sys/bus/thunderbolt/devices/.../nvm_version +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: If the device has upgradeable firmware the version + number is available here. Format: %x.%x, major.minor. + If the device is in safe mode reading the file returns + -ENODATA instead as the NVM version is not available. + +What: /sys/bus/thunderbolt/devices/.../nvm_authenticate +Date: Sep 2017 +KernelVersion: 4.13 +Contact: thunderbolt-software@lists.01.org +Description: When new NVM image is written to the non-active NVM + area (through non_activeX NVMem device), the + authentication procedure is started by writing to + this file. + If everything goes well, the device is + restarted with the new NVM firmware. If the image + verification fails an error code is returned instead. + + This file will accept writing values "1", "2" or "3". + + - Writing "1" will flush the image to the storage + area and authenticate the image in one action. + - Writing "2" will run some basic validation on the image + and flush it to the storage area. + - Writing "3" will authenticate the image that is + currently written in the storage area. This is only + supported with USB4 devices and retimers. + + When read holds status of the last authentication + operation if an error occurred during the process. This + is directly the status value from the DMA configuration + based mailbox before the device is power cycled. Writing + 0 here clears the status. + +What: /sys/bus/thunderbolt/devices/.../nvm_authenticate_on_disconnect +Date: Oct 2020 +KernelVersion: v5.9 +Contact: Mario Limonciello +Description: For supported devices, automatically authenticate the new Thunderbolt + image when the device is disconnected from the host system. + + This file will accept writing values "1" or "2" + + - Writing "1" will flush the image to the storage + area and prepare the device for authentication on disconnect. + - Writing "2" will run some basic validation on the image + and flush it to the storage area. + +What: /sys/bus/thunderbolt/devices/./key +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: This contains name of the property directory the XDomain + service exposes. This entry describes the protocol in + question. Following directories are already reserved by + the Apple XDomain specification: + + ======== =============================================== + network IP/ethernet over Thunderbolt + targetdm Target disk mode protocol over Thunderbolt + extdisp External display mode protocol over Thunderbolt + ======== =============================================== + +What: /sys/bus/thunderbolt/devices/./modalias +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: Stores the same MODALIAS value emitted by uevent for + the XDomain service. Format: tbtsvc:kSpNvNrN + +What: /sys/bus/thunderbolt/devices/./prtcid +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: This contains XDomain protocol identifier the XDomain + service supports. + +What: /sys/bus/thunderbolt/devices/./prtcvers +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: This contains XDomain protocol version the XDomain + service supports. + +What: /sys/bus/thunderbolt/devices/./prtcrevs +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: This contains XDomain software version the XDomain + service supports. + +What: /sys/bus/thunderbolt/devices/./prtcstns +Date: Jan 2018 +KernelVersion: 4.15 +Contact: thunderbolt-software@lists.01.org +Description: This contains XDomain service specific settings as + bitmask. Format: %x + +What: /sys/bus/thunderbolt/devices/usb4_portX/connector +Date: April 2022 +Contact: Heikki Krogerus +Description: + Symlink to the USB Type-C connector. This link is only + created when USB Type-C Connector Class is enabled, + and only if the system firmware is capable of + describing the connection between a port and its + connector. + +What: /sys/bus/thunderbolt/devices/usb4_portX/link +Date: Sep 2021 +KernelVersion: v5.14 +Contact: Mika Westerberg +Description: Returns the current link mode. Possible values are + "usb4", "tbt" and "none". + +What: /sys/bus/thunderbolt/devices/usb4_portX/offline +Date: Sep 2021 +KernelVersion: v5.14 +Contact: Rajmohan Mani +Description: Writing 1 to this attribute puts the USB4 port into + offline mode. Only allowed when there is nothing + connected to the port (link attribute returns "none"). + Once the port is in offline mode it does not receive any + hotplug events. This is used to update NVM firmware of + on-board retimers. Writing 0 puts the port back to + online mode. + + This attribute is only visible if the platform supports + powering on retimers when there is no cable connected. + +What: /sys/bus/thunderbolt/devices/usb4_portX/rescan +Date: Sep 2021 +KernelVersion: v5.14 +Contact: Rajmohan Mani +Description: When the USB4 port is in offline mode writing 1 to this + attribute forces rescan of the sideband for on-board + retimers. Each retimer appear under the USB4 port as if + the USB4 link was up. These retimers act in the same way + as if the cable was connected so upgrading their NVM + firmware can be done the usual way. + +What: /sys/bus/thunderbolt/devices/:./device +Date: Oct 2020 +KernelVersion: v5.9 +Contact: Mika Westerberg +Description: Retimer device identifier read from the hardware. + +What: /sys/bus/thunderbolt/devices/:./nvm_authenticate +Date: Oct 2020 +KernelVersion: v5.9 +Contact: Mika Westerberg +Description: When new NVM image is written to the non-active NVM + area (through non_activeX NVMem device), the + authentication procedure is started by writing 1 to + this file. If everything goes well, the device is + restarted with the new NVM firmware. If the image + verification fails an error code is returned instead. + + When read holds status of the last authentication + operation if an error occurred during the process. + Format: %x. + +What: /sys/bus/thunderbolt/devices/:./nvm_version +Date: Oct 2020 +KernelVersion: v5.9 +Contact: Mika Westerberg +Description: Holds retimer NVM version number. Format: %x.%x, major.minor. + +What: /sys/bus/thunderbolt/devices/:./vendor +Date: Oct 2020 +KernelVersion: v5.9 +Contact: Mika Westerberg +Description: Retimer vendor identifier read from the hardware. diff --git a/Documentation/ABI/testing/sysfs-bus-typec b/Documentation/ABI/testing/sysfs-bus-typec new file mode 100644 index 000000000..205d9c91e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-typec @@ -0,0 +1,51 @@ +What: /sys/bus/typec/devices/.../active +Date: July 2018 +Contact: Heikki Krogerus +Description: + Shows if the mode is active or not. The attribute can be used + for entering/exiting the mode. Entering/exiting modes is + supported as synchronous operation so write(2) to the attribute + does not return until the enter/exit mode operation has + finished. The attribute is notified when the mode is + entered/exited so poll(2) on the attribute wakes up. + Entering/exiting a mode will also generate uevent KOBJ_CHANGE. + + Valid values are boolean. + +What: /sys/bus/typec/devices/.../description +Date: July 2018 +Contact: Heikki Krogerus +Description: + Shows description of the mode. The description is optional for + the drivers, just like with the Billboard Devices. + +What: /sys/bus/typec/devices/.../mode +Date: July 2018 +Contact: Heikki Krogerus +Description: + The index number of the mode returned by Discover Modes USB + Power Delivery command. Depending on the alternate mode, the + mode index may be significant. + + With some alternate modes (SVIDs), the mode index is assigned + for specific functionality in the specification for that + alternate mode. + + With other alternate modes, the mode index values are not + assigned, and can not be therefore used for identification. When + the mode index is not assigned, identifying the alternate mode + must be done with either mode VDO or the description. + +What: /sys/bus/typec/devices/.../svid +Date: July 2018 +Contact: Heikki Krogerus +Description: + The Standard or Vendor ID (SVID) assigned by USB-IF for this + alternate mode. + +What: /sys/bus/typec/devices/.../vdo +Date: July 2018 +Contact: Heikki Krogerus +Description: + Shows the VDO in hexadecimal returned by Discover Modes command + for this mode. diff --git a/Documentation/ABI/testing/sysfs-bus-umc b/Documentation/ABI/testing/sysfs-bus-umc new file mode 100644 index 000000000..948fec412 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-umc @@ -0,0 +1,28 @@ +What: /sys/bus/umc/ +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + The Wireless Host Controller Interface (WHCI) + specification describes a PCI-based device with + multiple capabilities; the UWB Multi-interface + Controller (UMC). + + The umc bus presents each of the individual + capabilties as a device. + +What: /sys/bus/umc/devices/.../capability_id +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + The ID of this capability, with 0 being the radio + controller capability. + +What: /sys/bus/umc/devices/.../version +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + The specification version this capability's hardware + interface complies with. diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb new file mode 100644 index 000000000..568103d33 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-usb @@ -0,0 +1,584 @@ +What: /sys/bus/usb/devices//authorized +Date: August 2015 +Description: + This allows to authorize (1) or deauthorize (0) + individual interfaces instead a whole device + in contrast to the device authorization. + If a deauthorized interface will be authorized + so the driver probing must be triggered manually + by writing INTERFACE to /sys/bus/usb/drivers_probe + This allows to avoid side-effects with drivers + that need multiple interfaces. + + A deauthorized interface cannot be probed or claimed. + +What: /sys/bus/usb/devices/usbX/interface_authorized_default +Date: August 2015 +Description: + This is used as value that determines if interfaces + would be authorized by default. + The value can be 1 or 0. It's by default 1. + +What: /sys/bus/usb/device/.../authorized +Date: July 2008 +KernelVersion: 2.6.26 +Contact: David Vrabel +Description: + Authorized devices are available for use by device + drivers, non-authorized one are not. By default, wired + USB devices are authorized. + + Certified Wireless USB devices are not authorized + initially and should be (by writing 1) after the + device has been authenticated. + +What: /sys/bus/usb/device/.../wusb_cdid +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + For Certified Wireless USB devices only. + + A devices's CDID, as 16 space-separated hex octets. + +What: /sys/bus/usb/device/.../wusb_ck +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + For Certified Wireless USB devices only. + + Write the device's connection key (CK) to start the + authentication of the device. The CK is 16 + space-separated hex octets. + +What: /sys/bus/usb/device/.../wusb_disconnect +Date: July 2008 +KernelVersion: 2.6.27 +Contact: David Vrabel +Description: + For Certified Wireless USB devices only. + + Write a 1 to force the device to disconnect + (equivalent to unplugging a wired USB device). + +What: /sys/bus/usb/drivers/.../new_id +Date: October 2011 +Contact: linux-usb@vger.kernel.org +Description: + Writing a device ID to this file will attempt to + dynamically add a new device ID to a USB device driver. + This may allow the driver to support more hardware than + was included in the driver's static device ID support + table at compile time. The format for the device ID is: + idVendor idProduct bInterfaceClass RefIdVendor RefIdProduct + The vendor ID and device ID fields are required, the + rest is optional. The `Ref*` tuple can be used to tell the + driver to use the same driver_data for the new device as + it is used for the reference device. + Upon successfully adding an ID, the driver will probe + for the device and attempt to bind to it. For example:: + + # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id + + Here add a new device (0458:7045) using driver_data from + an already supported device (0458:704c):: + + # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id + + Reading from this file will list all dynamically added + device IDs in the same format, with one entry per + line. For example:: + + # cat /sys/bus/usb/drivers/foo/new_id + 8086 10f5 + dead beef 06 + f00d cafe + + The list will be truncated at PAGE_SIZE bytes due to + sysfs restrictions. + +What: /sys/bus/usb-serial/drivers/.../new_id +Date: October 2011 +Contact: linux-usb@vger.kernel.org +Description: + For serial USB drivers, this attribute appears under the + extra bus folder "usb-serial" in sysfs; apart from that + difference, all descriptions from the entry + "/sys/bus/usb/drivers/.../new_id" apply. + +What: /sys/bus/usb/drivers/.../remove_id +Date: November 2009 +Contact: CHENG Renquan +Description: + Writing a device ID to this file will remove an ID + that was dynamically added via the new_id sysfs entry. + The format for the device ID is: + idVendor idProduct. After successfully + removing an ID, the driver will no longer support the + device. This is useful to ensure auto probing won't + match the driver to the device. For example: + # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id + + Reading from this file will list the dynamically added + device IDs, exactly like reading from the entry + "/sys/bus/usb/drivers/.../new_id" + +What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm +Date: September 2011 +Contact: Andiry Xu +Description: + If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged + in to a xHCI host which support link PM, it will perform a LPM + test; if the test is passed and host supports USB2 hardware LPM + (xHCI 1.0 feature), USB2 hardware LPM will be enabled for the + device and the USB device directory will contain a file named + power/usb2_hardware_lpm. The file holds a string value (enable + or disable) indicating whether or not USB2 hardware LPM is + enabled for the device. Developer can write y/Y/1 or n/N/0 to + the file to enable/disable the feature. + +What: /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u1 + /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u2 +Date: November 2015 +Contact: Kevin Strasser + Lu Baolu +Description: + If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged + in to a xHCI host which supports link PM, it will check if U1 + and U2 exit latencies have been set in the BOS descriptor; if + the check is passed and the host supports USB3 hardware LPM, + USB3 hardware LPM will be enabled for the device and the USB + device directory will contain two files named + power/usb3_hardware_lpm_u1 and power/usb3_hardware_lpm_u2. These + files hold a string value (enable or disable) indicating whether + or not USB3 hardware LPM U1 or U2 is enabled for the device. + +What: /sys/bus/usb/devices/.../ltm_capable +Date: July 2012 +Contact: Sarah Sharp +Description: + USB 3.0 devices may optionally support Latency Tolerance + Messaging (LTM). They indicate their support by setting a bit + in the bmAttributes field of their SuperSpeed BOS descriptors. + If that bit is set for the device, ltm_capable will read "yes". + If the device doesn't support LTM, the file will read "no". + The file will be present for all speeds of USB devices, and will + always read "no" for USB 1.1 and USB 2.0 devices. + +What: /sys/bus/usb/devices/...//port +Date: August 2012 +Contact: Lan Tianyu +Description: + The /sys/bus/usb/devices/...//port + is usb port device's sysfs directory. + +What: /sys/bus/usb/devices/...//port/connect_type +Date: January 2013 +Contact: Lan Tianyu +Description: + Some platforms provide usb port connect types through ACPI. + This attribute is to expose these information to user space. + The file will read "hotplug", "hardwired" and "not used" if the + information is available, and "unknown" otherwise. + +What: /sys/bus/usb/devices/...//port/location +Date: October 2018 +Contact: Bjørn Mork +Description: + Some platforms provide usb port physical location through + firmware. This is used by the kernel to pair up logical ports + mapping to the same physical connector. The attribute exposes the + raw location value as a hex integer. + + +What: /sys/bus/usb/devices/...//port/quirks +Date: May 2018 +Contact: Nicolas Boichat +Description: + In some cases, we care about time-to-active for devices + connected on a specific port (e.g. non-standard USB port like + pogo pins), where the device to be connected is known in + advance, and behaves well according to the specification. + This attribute is a bit-field that controls the behavior of + a specific port: + + - Bit 0 of this field selects the "old" enumeration scheme, + as it is considerably faster (it only causes one USB reset + instead of 2). + + The old enumeration scheme can also be selected globally + using /sys/module/usbcore/parameters/old_scheme_first, but + it is often not desirable as the new scheme was introduced to + increase compatibility with more devices. + - Bit 1 reduces TRSTRCY to the 10 ms that are required by the + USB 2.0 specification, instead of the 50 ms that are normally + used to help make enumeration work better on some high speed + devices. + +What: /sys/bus/usb/devices/...//port/over_current_count +Date: February 2018 +Contact: Richard Leitner +Description: + Most hubs are able to detect over-current situations on their + ports and report them to the kernel. This attribute is to expose + the number of over-current situation occurred on a specific port + to user space. This file will contain an unsigned 32 bit value + which wraps to 0 after its maximum is reached. This file supports + poll() for monitoring changes to this value in user space. + + Any time this value changes the corresponding hub device will send a + udev event with the following attributes:: + + OVER_CURRENT_PORT=/sys/bus/usb/devices/...//port + OVER_CURRENT_COUNT=[current value of this sysfs attribute] + +What: /sys/bus/usb/devices/...//port/usb3_lpm_permit +Date: November 2015 +Contact: Lu Baolu +Description: + Some USB3.0 devices are not friendly to USB3 LPM. usb3_lpm_permit + attribute allows enabling/disabling usb3 lpm of a port. It takes + effect both before and after a usb device is enumerated. Supported + values are "0" if both u1 and u2 are NOT permitted, "u1" if only u1 + is permitted, "u2" if only u2 is permitted, "u1_u2" if both u1 and + u2 are permitted. + +What: /sys/bus/usb/devices/...//port/connector +Date: December 2021 +Contact: Heikki Krogerus +Description: + Link to the USB Type-C connector when available. This link is + only created when USB Type-C Connector Class is enabled, and + only if the system firmware is capable of describing the + connection between a port and its connector. + +What: /sys/bus/usb/devices/...//port/disable +Date: June 2022 +Contact: Michael Grzeschik +Description: + This file controls the state of a USB port, including + Vbus power output (but only on hubs that support + power switching -- most hubs don't support it). If + a port is disabled, the port is unusable: Devices + attached to the port will not be detected, initialized, + or enumerated. + +What: /sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout +Date: May 2013 +Contact: Mathias Nyman +Description: + USB 2.0 devices may support hardware link power management (LPM) + L1 sleep state. The usb2_lpm_l1_timeout attribute allows + tuning the timeout for L1 inactivity timer (LPM timer), e.g. + needed inactivity time before host requests the device to go to L1 sleep. + Useful for power management tuning. + Supported values are 0 - 65535 microseconds. + +What: /sys/bus/usb/devices/.../power/usb2_lpm_besl +Date: May 2013 +Contact: Mathias Nyman +Description: + USB 2.0 devices that support hardware link power management (LPM) + L1 sleep state now use a best effort service latency value (BESL) to + indicate the best effort to resumption of service to the device after the + initiation of the resume event. + If the device does not have a preferred besl value then the host can select + one instead. This usb2_lpm_besl attribute allows to tune the host selected besl + value in order to tune power saving and service latency. + + Supported values are 0 - 15. + More information on how besl values map to microseconds can be found in + USB 2.0 ECN Errata for Link Power Management, section 4.10) + +What: /sys/bus/usb/devices/.../rx_lanes +Date: March 2018 +Contact: Mathias Nyman +Description: + Number of rx lanes the device is using. + USB 3.2 adds Dual-lane support, 2 rx and 2 tx lanes over Type-C. + Inter-Chip SSIC devices support asymmetric lanes up to 4 lanes per + direction. Devices before USB 3.2 are single lane (rx_lanes = 1) + +What: /sys/bus/usb/devices/.../tx_lanes +Date: March 2018 +Contact: Mathias Nyman +Description: + Number of tx lanes the device is using. + USB 3.2 adds Dual-lane support, 2 rx and 2 tx -lanes over Type-C. + Inter-Chip SSIC devices support asymmetric lanes up to 4 lanes per + direction. Devices before USB 3.2 are single lane (tx_lanes = 1) + +What: /sys/bus/usb/devices/usbX/bAlternateSetting +Description: + The current interface alternate setting number, in decimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bcdDevice +Description: + The device's release number, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bConfigurationValue +Description: + While a USB device typically have just one configuration + setting, some devices support multiple configurations. + + This value shows the current configuration, in decimal. + + Changing its value will change the device's configuration + to another setting. + + The number of configurations supported by a device is at: + + /sys/bus/usb/devices/usbX/bNumConfigurations + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bDeviceClass +Description: + Class code of the device, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bDeviceProtocol +Description: + Protocol code of the device, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bDeviceSubClass +Description: + Subclass code of the device, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bInterfaceClass +Description: + Class code of the interface, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bInterfaceNumber +Description: + Interface number, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bInterfaceProtocol +Description: + Protocol code of the interface, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bInterfaceSubClass +Description: + Subclass code of the interface, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bmAttributes +Description: + Attributes of the current configuration, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bMaxPacketSize0 +Description: + Maximum endpoint 0 packet size, in decimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bMaxPower +Description: + Maximum power consumption of the active configuration of + the device, in miliamperes. + +What: /sys/bus/usb/devices/usbX/bNumConfigurations +Description: + Number of the possible configurations of the device, in + decimal. The current configuration is controlled via: + + /sys/bus/usb/devices/usbX/bConfigurationValue + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bNumEndpoints +Description: + Number of endpoints used on this interface, in hexadecimal. + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/bNumInterfaces +Description: + Number of interfaces on this device, in decimal. + +What: /sys/bus/usb/devices/usbX/busnum +Description: + Number of the bus. + +What: /sys/bus/usb/devices/usbX/configuration +Description: + Contents of the string descriptor associated with the + current configuration. It may include the firmware version + of a device and/or its serial number. + +What: /sys/bus/usb/devices/usbX/descriptors +Description: + Contains the interface descriptors, in binary. + +What: /sys/bus/usb/devices/usbX/idProduct +Description: + Product ID, in hexadecimal. + +What: /sys/bus/usb/devices/usbX/idVendor +Description: + Vendor ID, in hexadecimal. + +What: /sys/bus/usb/devices/usbX/devspec +Description: + Displays the Device Tree Open Firmware node of the interface. + +What: /sys/bus/usb/devices/usbX/avoid_reset_quirk +Description: + Most devices have this set to zero. + + If the value is 1, enable a USB quirk that prevents this + device to use reset. + + (read/write) + +What: /sys/bus/usb/devices/usbX/devnum +Description: + USB interface device number, in decimal. + +What: /sys/bus/usb/devices/usbX/devpath +Description: + String containing the USB interface device path. + +What: /sys/bus/usb/devices/usbX/manufacturer +Description: + Vendor specific string containing the name of the + manufacturer of the device. + +What: /sys/bus/usb/devices/usbX/maxchild +Description: + Number of ports of an USB hub + +What: /sys/bus/usb/devices/usbX/persist +Description: + Keeps the device even if it gets disconnected. + +What: /sys/bus/usb/devices/usbX/product +Description: + Vendor specific string containing the name of the + device's product. + +What: /sys/bus/usb/devices/usbX/speed +Description: + Shows the device's max speed, according to the USB version, + in Mbps. + Can be: + + ======= ==================== + Unknown speed unknown + 1.5 Low speed + 15 Full speed + 480 High Speed + 5000 Super Speed + 10000 Super Speed+ + 20000 Super Speed+ Gen 2x2 + ======= ==================== + +What: /sys/bus/usb/devices/usbX/supports_autosuspend +Description: + Returns 1 if the device doesn't support autosuspend. + Otherwise, returns 0. + +What: /sys/bus/usb/devices/usbX/urbnum +Description: + Number of URBs submitted for the whole device. + +What: /sys/bus/usb/devices/usbX/version +Description: + String containing the USB device version, as encoded + at the BCD descriptor. + +What: /sys/bus/usb/devices/usbX/power/autosuspend +Description: + Time in milliseconds for the device to autosuspend. If the + value is negative, then autosuspend is prevented. + + (read/write) + +What: /sys/bus/usb/devices/usbX/power/active_duration +Description: + The total time the device has not been suspended. + +What: /sys/bus/usb/devices/usbX/power/connected_duration +Description: + The total time (in msec) that the device has been connected. + +What: /sys/bus/usb/devices/usbX/power/level +Description: + +What: /sys/bus/usb/devices/usbX/ep_/bEndpointAddress +Description: + The address of the endpoint described by this descriptor, + in hexadecimal. The endpoint direction on this bitmapped field + is also shown at: + + /sys/bus/usb/devices/usbX/ep_/direction + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/ep_/bInterval +Description: + The interval of the endpoint as described on its descriptor, + in hexadecimal. The actual interval depends on the version + of the USB. Also shown in time units at + /sys/bus/usb/devices/usbX/ep_/interval. + +What: /sys/bus/usb/devices/usbX/ep_/bLength +Description: + Number of bytes of the endpoint descriptor, in hexadecimal. + +What: /sys/bus/usb/devices/usbX/ep_/bmAttributes +Description: + Attributes which apply to the endpoint as described on its + descriptor, in hexadecimal. The endpoint type on this + bitmapped field is also shown at: + + /sys/bus/usb/devices/usbX/ep_/type + + See USB specs for its meaning. + +What: /sys/bus/usb/devices/usbX/ep_/direction +Description: + Direction of the endpoint. Can be: + + - both (on control endpoints) + - in + - out + +What: /sys/bus/usb/devices/usbX/ep_/interval +Description: + Interval for polling endpoint for data transfers, in + milisseconds or microseconds. + +What: /sys/bus/usb/devices/usbX/ep_/type +Description: + Descriptor type. Can be: + + - Control + - Isoc + - Bulk + - Interrupt + - unknown + +What: /sys/bus/usb/devices/usbX/ep_/wMaxPacketSize +Description: + Maximum packet size this endpoint is capable of + sending or receiving, in hexadecimal. diff --git a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg new file mode 100644 index 000000000..2f86e4223 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg @@ -0,0 +1,46 @@ +What: /sys/bus/usb/.../powered +Date: August 2008 +KernelVersion: 2.6.26 +Contact: Harrison Metzger +Description: Controls whether the device's display will powered. + A value of 0 is off and a non-zero value is on. + +What: /sys/bus/usb/.../mode_msb +What: /sys/bus/usb/.../mode_lsb +Date: August 2008 +KernelVersion: 2.6.26 +Contact: Harrison Metzger +Description: Controls the devices display mode. + For a 6 character display the values are + + MSB 0x06; LSB 0x3F, and + + for an 8 character display the values are + + MSB 0x08; LSB 0xFF. + +What: /sys/bus/usb/.../textmode +Date: August 2008 +KernelVersion: 2.6.26 +Contact: Harrison Metzger +Description: Controls the way the device interprets its text buffer. + raw: each character controls its segment manually + hex: each character is between 0-15 + ascii: each character is between '0'-'9' and 'A'-'F'. + +What: /sys/bus/usb/.../text +Date: August 2008 +KernelVersion: 2.6.26 +Contact: Harrison Metzger +Description: The text (or data) for the device to display + +What: /sys/bus/usb/.../decimals +Date: August 2008 +KernelVersion: 2.6.26 +Contact: Harrison Metzger +Description: Controls the decimal places on the device. + To set the nth decimal place, give this field + the value of ``10 ** n``. Assume this field has + the value k and has 1 or more decimal places set, + to set the mth place (where m is not already set), + change this fields value to ``k + 10 ** m``. diff --git a/Documentation/ABI/testing/sysfs-bus-usb-lvstest b/Documentation/ABI/testing/sysfs-bus-usb-lvstest new file mode 100644 index 000000000..ee0046dc4 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-usb-lvstest @@ -0,0 +1,60 @@ +Link Layer Validation Device is a standard device for testing of Super +Speed Link Layer tests. These nodes are available in sysfs only when lvs +driver is bound with root hub device. + +What: /sys/bus/usb/devices/.../get_dev_desc +Date: March 2014 +Contact: Pratyush Anand +Description: + Write to this node to issue "Get Device Descriptor" + for Link Layer Validation device. It is needed for TD.7.06. + +What: /sys/bus/usb/devices/.../u1_timeout +Date: March 2014 +Contact: Pratyush Anand +Description: + Set "U1 timeout" for the downstream port where Link Layer + Validation device is connected. Timeout value must be between 0 + and 127. It is needed for TD.7.18, TD.7.19, TD.7.20 and TD.7.21. + +What: /sys/bus/usb/devices/.../u2_timeout +Date: March 2014 +Contact: Pratyush Anand +Description: + Set "U2 timeout" for the downstream port where Link Layer + Validation device is connected. Timeout value must be between 0 + and 127. It is needed for TD.7.18, TD.7.19, TD.7.20 and TD.7.21. + +What: /sys/bus/usb/devices/.../hot_reset +Date: March 2014 +Contact: Pratyush Anand +Description: + Write to this node to issue "Reset" for Link Layer Validation + device. It is needed for TD.7.29, TD.7.31, TD.7.34 and TD.7.35. + +What: /sys/bus/usb/devices/.../u3_entry +Date: March 2014 +Contact: Pratyush Anand +Description: + Write to this node to issue "U3 entry" for Link Layer + Validation device. It is needed for TD.7.35 and TD.7.36. + +What: /sys/bus/usb/devices/.../u3_exit +Date: March 2014 +Contact: Pratyush Anand +Description: + Write to this node to issue "U3 exit" for Link Layer + Validation device. It is needed for TD.7.36. + +What: /sys/bus/usb/devices/.../enable_compliance +Date: July 2017 +Description: + Write to this node to set the port to compliance mode to test + with Link Layer Validation device. It is needed for TD.7.34. + +What: /sys/bus/usb/devices/.../warm_reset +Date: July 2017 +Description: + Write to this node to issue "Warm Reset" for Link Layer Validation + device. It may be needed to properly reset an xHCI 1.1 host port if + compliance mode needed to be explicitly enabled. diff --git a/Documentation/ABI/testing/sysfs-bus-vdpa b/Documentation/ABI/testing/sysfs-bus-vdpa new file mode 100644 index 000000000..28a611120 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-vdpa @@ -0,0 +1,57 @@ +What: /sys/bus/vdpa/driver_autoprobe +Date: March 2020 +Contact: virtualization@lists.linux-foundation.org +Description: + This file determines whether new devices are immediately bound + to a driver after the creation. It initially contains 1, which + means the kernel automatically binds devices to a compatible + driver immediately after they are created. + + Writing "0" to this file disable this feature, any other string + enable it. + +What: /sys/bus/vdpa/driver_probe +Date: March 2020 +Contact: virtualization@lists.linux-foundation.org +Description: + Writing a device name to this file will cause the kernel binds + devices to a compatible driver. + + This can be useful when /sys/bus/vdpa/driver_autoprobe is + disabled. + +What: /sys/bus/vdpa/drivers/.../bind +Date: March 2020 +Contact: virtualization@lists.linux-foundation.org +Description: + Writing a device name to this file will cause the driver to + attempt to bind to the device. This is useful for overriding + default bindings. + +What: /sys/bus/vdpa/drivers/.../unbind +Date: March 2020 +Contact: virtualization@lists.linux-foundation.org +Description: + Writing a device name to this file will cause the driver to + attempt to unbind from the device. This may be useful when + overriding default bindings. + +What: /sys/bus/vdpa/devices/.../driver_override +Date: November 2021 +Contact: virtualization@lists.linux-foundation.org +Description: + This file allows the driver for a device to be specified. + When specified, only a driver with a name matching the value + written to driver_override will have an opportunity to bind to + the device. The override is specified by writing a string to the + driver_override file (echo vhost-vdpa > driver_override) and may + be cleared with an empty string (echo > driver_override). + This returns the device to standard matching rules binding. + Writing to driver_override does not automatically unbind the + device from its current driver or make any attempt to + automatically load the specified driver. If no driver with a + matching name is currently loaded in the kernel, the device will + not bind to any driver. This also allows devices to opt-out of + driver binding using a driver_override name such as "none". + Only a single driver may be specified in the override, there is + no support for parsing delimiters. diff --git a/Documentation/ABI/testing/sysfs-bus-vfio-mdev b/Documentation/ABI/testing/sysfs-bus-vfio-mdev new file mode 100644 index 000000000..59fc80426 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-vfio-mdev @@ -0,0 +1,113 @@ +What: /sys/...//mdev_supported_types/ +Date: October 2016 +Contact: Kirti Wankhede +Description: + This directory contains list of directories of currently + supported mediated device types and their details for + . Supported type attributes are defined by the + vendor driver who registers with Mediated device framework. + Each supported type is a directory whose name is created + by adding the device driver string as a prefix to the + string provided by the vendor driver. + +What: /sys/...//mdev_supported_types// +Date: October 2016 +Contact: Kirti Wankhede +Description: + This directory gives details of supported type, like name, + description, available_instances, device_api etc. + 'device_api' and 'available_instances' are mandatory + attributes to be provided by vendor driver. 'name', + 'description' and other vendor driver specific attributes + are optional. + +What: /sys/.../mdev_supported_types//create +Date: October 2016 +Contact: Kirti Wankhede +Description: + Writing UUID to this file will create mediated device of + type for parent device . This is a + write-only file. + For example:: + + # echo "83b8f4f2-509f-382f-3c1e-e6bfe0fa1001" > \ + /sys/devices/foo/mdev_supported_types/foo-1/create + +What: /sys/.../mdev_supported_types//devices/ +Date: October 2016 +Contact: Kirti Wankhede +Description: + This directory contains symbolic links pointing to mdev + devices sysfs entries which are created of this . + +What: /sys/.../mdev_supported_types//available_instances +Date: October 2016 +Contact: Kirti Wankhede +Description: + Reading this attribute will show the number of mediated + devices of type that can be created. This is a + readonly file. +Users: + Userspace applications interested in creating mediated + device of that type. Userspace application should check + the number of available instances could be created before + creating mediated device of this type. + +What: /sys/.../mdev_supported_types//device_api +Date: October 2016 +Contact: Kirti Wankhede +Description: + Reading this attribute will show VFIO device API supported + by this type. For example, "vfio-pci" for a PCI device, + "vfio-platform" for platform device. + +What: /sys/.../mdev_supported_types//name +Date: October 2016 +Contact: Kirti Wankhede +Description: + Reading this attribute will show human readable name of the + mediated device that will get created of type . + This is optional attribute. For example: "Grid M60-0Q" +Users: + Userspace applications interested in knowing the name of + a particular that can help in understanding the + type of mediated device. + +What: /sys/.../mdev_supported_types//description +Date: October 2016 +Contact: Kirti Wankhede +Description: + Reading this attribute will show description of the type of + mediated device that will get created of type . + This is optional attribute. For example: + "2 heads, 512M FB, 2560x1600 maximum resolution" +Users: + Userspace applications interested in knowing the details of + a particular that can help in understanding the + features provided by that type of mediated device. + +What: /sys/.../// +Date: October 2016 +Contact: Kirti Wankhede +Description: + This directory represents device directory of mediated + device. It contains all the attributes related to mediated + device. + +What: /sys/...///mdev_type +Date: October 2016 +Contact: Kirti Wankhede +Description: + This is symbolic link pointing to supported type, + directory of which this mediated device is created. + +What: /sys/...///remove +Date: October 2016 +Contact: Kirti Wankhede +Description: + Writing '1' to this file destroys the mediated device. The + vendor driver can fail the remove() callback if that device + is active and the vendor driver doesn't support hot unplug. + Example:: + + # echo 1 > /sys/bus/mdev/devices//remove diff --git a/Documentation/ABI/testing/sysfs-bus-vmbus b/Documentation/ABI/testing/sysfs-bus-vmbus new file mode 100644 index 000000000..91e6c0659 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-vmbus @@ -0,0 +1,21 @@ +What: /sys/bus/vmbus/devices/.../driver_override +Date: August 2019 +Contact: Stephen Hemminger +Description: + This file allows the driver for a device to be specified which + will override standard static and dynamic ID matching. When + specified, only a driver with a name matching the value written + to driver_override will have an opportunity to bind to the + device. The override is specified by writing a string to the + driver_override file (echo uio_hv_generic > driver_override) and + may be cleared with an empty string (echo > driver_override). + This returns the device to standard matching rules binding. + Writing to driver_override does not automatically unbind the + device from its current driver or make any attempt to + automatically load the specified driver. If no driver with a + matching name is currently loaded in the kernel, the device + will not bind to any driver. This also allows devices to + opt-out of driver binding using a driver_override name such as + "none". Only a single driver may be specified in the override, + there is no support for parsing delimiters. + diff --git a/Documentation/ABI/testing/sysfs-c2port b/Documentation/ABI/testing/sysfs-c2port new file mode 100644 index 000000000..f7b8cf6e4 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-c2port @@ -0,0 +1,81 @@ +What: /sys/class/c2port/ +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/ directory will contain files and + directories that will provide a unified interface to + the C2 port interface. + +What: /sys/class/c2port/c2portX +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/ directory is related to X-th + C2 port into the system. Each directory will contain files to + manage and control its C2 port. + +What: /sys/class/c2port/c2portX/access +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/access file enable the access + to the C2 port from the system. No commands can be sent + till this entry is set to 0. + +What: /sys/class/c2port/c2portX/dev_id +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/dev_id file show the device ID + of the connected micro. + +What: /sys/class/c2port/c2portX/flash_access +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/flash_access file enable the + access to the on-board flash of the connected micro. + No commands can be sent till this entry is set to 0. + +What: /sys/class/c2port/c2portX/flash_block_size +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/flash_block_size file show + the on-board flash block size of the connected micro. + +What: /sys/class/c2port/c2portX/flash_blocks_num +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/flash_blocks_num file show + the on-board flash blocks number of the connected micro. + +What: /sys/class/c2port/c2portX/flash_data +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/flash_data file export + the content of the on-board flash of the connected micro. + +What: /sys/class/c2port/c2portX/flash_erase +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/flash_erase file execute + the "erase" command on the on-board flash of the connected + micro. + +What: /sys/class/c2port/c2portX/reset +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/reset file execute a "reset" + command on the connected micro. + +What: /sys/class/c2port/c2portX/rev_id +Date: October 2008 +Contact: Rodolfo Giometti +Description: + The /sys/class/c2port/c2portX/rev_id file show the revision ID + of the connected micro. diff --git a/Documentation/ABI/testing/sysfs-cfq-target-latency b/Documentation/ABI/testing/sysfs-cfq-target-latency new file mode 100644 index 000000000..df0f7828c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-cfq-target-latency @@ -0,0 +1,8 @@ +What: /sys/block//iosched/target_latency +Date: March 2012 +contact: Tao Ma +Description: + The /sys/block//iosched/target_latency only exists + when the user sets cfq to /sys/block//scheduler. + It contains an estimated latency time for the cfq. cfq will + use it to calculate the time slice used for every task. diff --git a/Documentation/ABI/testing/sysfs-class b/Documentation/ABI/testing/sysfs-class new file mode 100644 index 000000000..676530fcf --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class @@ -0,0 +1,16 @@ +What: /sys/class/ +Date: Febuary 2006 +Contact: Greg Kroah-Hartman +Description: + The /sys/class directory will consist of a group of + subdirectories describing individual classes of devices + in the kernel. The individual directories will consist + of either subdirectories, or symlinks to other + directories. + + All programs that use this directory tree must be able + to handle both subdirectories or symlinks in order to + work properly. + +Users: + udev diff --git a/Documentation/ABI/testing/sysfs-class-backlight b/Documentation/ABI/testing/sysfs-class-backlight new file mode 100644 index 000000000..c453646b0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-backlight @@ -0,0 +1,186 @@ +What: /sys/class/backlight//scale +Date: July 2019 +KernelVersion: 5.4 +Contact: Daniel Thompson +Description: + Description of the scale of the brightness curve. + + The human eye senses brightness approximately logarithmically, + hence linear changes in brightness are perceived as being + non-linear. To achieve a linear perception of brightness changes + controls like sliders need to apply a logarithmic mapping for + backlights with a linear brightness curve. + + Possible values of the attribute are: + + unknown + The scale of the brightness curve is unknown. + + linear + The brightness changes linearly with each step. Brightness + controls should apply a logarithmic mapping for a linear + perception. + + non-linear + The brightness changes non-linearly with each step. Brightness + controls should use a linear mapping for a linear perception. + +What: /sys/class/backlight//ambient_light_level +Date: Apr, 2010 +KernelVersion: v2.6.35 +Contact: Michael Hennerich +Description: + (RO) Get conversion value of the light sensor. + + The value is automatically updated every 80 ms when the + light sensor is enabled. + + The value range is device-driver specific: + + For ADP8870: + + It returns integer between 0 (dark) and 8000 (max ambient + brightness). + + For ADP8860: + + It returns a 13-bits integer. + +What: /sys/class/backlight//ambient_light_zone +Date: Apr, 2010 +KernelVersion: v2.6.35 +Contact: Michael Hennerich , + device-drivers-devel@blackfin.uclinux.org + +Description: + (RW) Read or write the specific brightness level at which the + backlight operates. + + The value meaning is device-driver specific: + + For ADP8860: + + == ========================== + 0 Off: Backlight set to 0 mA + 1 Level 1: daylight + 2 Level 2: bright + 3 Level 3: dark + == ========================== + + For ADP8870: + + == ========================== + 0 Off: Backlight set to 0 mA + 1 Level 1: daylight + 2 Level 2: bright + 3 Level 3: office + 4 Level 4: indoor + 5 Level 5: dark + == ========================== + + Writing 0 returns to normal/automatic ambient light level + operation. + + It can be enabled by writing the value stored in + /sys/class/backlight//max_brightness to + /sys/class/backlight//brightness. + +What: /sys/class/backlight//_max +Date: Sep, 2009 +KernelVersion: v2.6.32 +Contact: device-drivers-devel@blackfin.uclinux.org +Description: + Control the maximum brightness for + on this . Values are between 0 and 127. This file + will also show the brightness level stored for this + . + + The is device-driver specific: + + For ADP5520 and ADP5501, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + daylight /sys/class/backlight//daylight_max + office /sys/class/backlight//office_max + dark /sys/class/backlight//dark_max + =========== ================================================ + + For ADP8860, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + l1_daylight /sys/class/backlight//l1_daylight_max + l2_office /sys/class/backlight//l2_office_max + l3_dark /sys/class/backlight//l3_dark_max + =========== ================================================ + + For ADP8870, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + l1_daylight /sys/class/backlight//l1_daylight_max + l2_bright /sys/class/backlight//l2_bright_max + l3_office /sys/class/backlight//l3_office_max + l4_indoor /sys/class/backlight//l4_indoor_max + l5_dark /sys/class/backlight//l5_dark_max + =========== ================================================ + + See also: /sys/class/backlight//ambient_light_zone. + +What: /sys/class/backlight//_dim +Date: Sep, 2009 +KernelVersion: v2.6.32 +Contact: device-drivers-devel@blackfin.uclinux.org +Description: + Control the dim brightness for + on this . Values are between 0 and 127, typically + set to 0. Full off when the backlight is disabled. + This file will also show the dim brightness level stored for + this . + + The is device-driver specific: + + For ADP5520 and ADP5501, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + daylight /sys/class/backlight//daylight_dim + office /sys/class/backlight//office_dim + dark /sys/class/backlight//dark_dim + =========== ================================================ + + For ADP8860, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + l1_daylight /sys/class/backlight//l1_daylight_dim + l2_office /sys/class/backlight//l2_office_dim + l3_dark /sys/class/backlight//l3_dark_dim + =========== ================================================ + + For ADP8870, can be: + + =========== ================================================ + Ambient sysfs entry + light zone + =========== ================================================ + l1_daylight /sys/class/backlight//l1_daylight_dim + l2_bright /sys/class/backlight//l2_bright_dim + l3_office /sys/class/backlight//l3_office_dim + l4_indoor /sys/class/backlight//l4_indoor_dim + l5_dark /sys/class/backlight//l5_dark_dim + =========== ================================================ + + See also: /sys/class/backlight//ambient_light_zone. + diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 b/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 new file mode 100644 index 000000000..8251e78ab --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 @@ -0,0 +1,54 @@ +What: /sys/class/backlight//als_channel +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Get the ALS output channel used as input in + ALS-current-control mode (0, 1), where: + + == ========================== + 0 out_current0 (backlight 0) + 1 out_current1 (backlight 1) + == ========================== + +What: /sys/class/backlight//als_en +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Enable ALS-current-control mode (0, 1). + +What: /sys/class/backlight//id +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Get the id of this backlight (0, 1). + +What: /sys/class/backlight//linear +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the brightness-mapping mode (0, 1), where: + + == ================ + 0 exponential mode + 1 linear mode + == ================ + +What: /sys/class/backlight//pwm +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the PWM-input control mask (5 bits), where: + + ===== =========================== + bit 5 PWM-input enabled in Zone 4 + bit 4 PWM-input enabled in Zone 3 + bit 3 PWM-input enabled in Zone 2 + bit 2 PWM-input enabled in Zone 1 + bit 1 PWM-input enabled in Zone 0 + bit 0 PWM-input enabled + ===== =========================== diff --git a/Documentation/ABI/testing/sysfs-class-backlight-lm3639 b/Documentation/ABI/testing/sysfs-class-backlight-lm3639 new file mode 100644 index 000000000..f7e92a82e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-backlight-lm3639 @@ -0,0 +1,11 @@ +sysfs interface for Texas Instruments lm3639 backlight + flash led driver chip +------------------------------------------------------------------------------ + +What: /sys/class/backlight//bled_mode +Date: Oct, 2012 +KernelVersion: v3.10 +Contact: dri-devel@lists.freedesktop.org +Description: + (WO) Write to the backlight mapping mode. The backlight current + can be mapped for either exponential (value "0") or linear + mapping modes (default). diff --git a/Documentation/ABI/testing/sysfs-class-bdi b/Documentation/ABI/testing/sysfs-class-bdi new file mode 100644 index 000000000..6d2a2fc18 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-bdi @@ -0,0 +1,66 @@ +What: /sys/class/bdi// +Date: January 2008 +Contact: Peter Zijlstra +Description: + +Provide a place in sysfs for the backing_dev_info object. This allows +setting and retrieving various BDI specific variables. + +The identifier can be either of the following: + +MAJOR:MINOR + + Device number for block devices, or value of st_dev on + non-block filesystems which provide their own BDI, such as NFS + and FUSE. + +MAJOR:MINOR-fuseblk + + Value of st_dev on fuseblk filesystems. + +default + + The default backing dev, used for non-block device backed + filesystems which do not provide their own BDI. + +What: /sys/class/bdi//read_ahead_kb +Date: January 2008 +Contact: Peter Zijlstra +Description: + Size of the read-ahead window in kilobytes + + (read-write) +What: /sys/class/bdi//min_ratio +Date: January 2008 +Contact: Peter Zijlstra +Description: + Under normal circumstances each device is given a part of the + total write-back cache that relates to its current average + writeout speed in relation to the other devices. + + The 'min_ratio' parameter allows assigning a minimum + percentage of the write-back cache to a particular device. + For example, this is useful for providing a minimum QoS. + + (read-write) + +What: /sys/class/bdi//max_ratio +Date: January 2008 +Contact: Peter Zijlstra +Description: + Allows limiting a particular device to use not more than the + given percentage of the write-back cache. This is useful in + situations where we want to avoid one device taking all or + most of the write-back cache. For example in case of an NFS + mount that is prone to get stuck, or a FUSE mount which cannot + be trusted to play fair. + + (read-write) +What: /sys/class/bdi//stable_pages_required +Date: January 2008 +Contact: Peter Zijlstra +Description: + If set, the backing device requires that all pages comprising a write + request must not be changed until writeout is complete. + + (read-only) diff --git a/Documentation/ABI/testing/sysfs-class-bsr b/Documentation/ABI/testing/sysfs-class-bsr new file mode 100644 index 000000000..7bf145d32 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-bsr @@ -0,0 +1,25 @@ +What: /sys/class/bsr/bsr*/bsr_size +Date: Jul, 2008 +KernelVersion: 2.6.27 +Contact: Arnd Bergmann , + Greg Kroah-Hartman +Description: + (RO) Size of the barrier-synchronization register (BSR) + register in bytes. + +What: /sys/class/bsr/bsr*/bsr_length +Date: Jul, 2008 +KernelVersion: 2.6.27 +Contact: Arnd Bergmann , + Greg Kroah-Hartman +Description: + (RO) The length of memory region that can be mapped in bytes. + +What: /sys/class/bsr/bsr*/bsr_stride +Date: Jul, 2008 +KernelVersion: 2.6.27 +Contact: Arnd Bergmann , + Greg Kroah-Hartman +Description: + (RO) The stride or the interval at which the allocated BSR bytes + repeat within the mapping. diff --git a/Documentation/ABI/testing/sysfs-class-chromeos b/Documentation/ABI/testing/sysfs-class-chromeos new file mode 100644 index 000000000..74ece9427 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-chromeos @@ -0,0 +1,33 @@ +What: /sys/class/chromeos//flashinfo +Date: August 2015 +KernelVersion: 4.2 +Description: + Show the EC flash information. + +What: /sys/class/chromeos//kb_wake_angle +Date: March 2018 +KernelVersion: 4.17 +Description: + Control the keyboard wake lid angle. Values are between + 0 and 360. This file will also show the keyboard wake lid + angle by querying the hardware. + +What: /sys/class/chromeos//reboot +Date: August 2015 +KernelVersion: 4.2 +Description: + Tell the EC to reboot in various ways. Options are: + + - "cancel": Cancel a pending reboot. + - "ro": Jump to RO without rebooting. + - "rw": Jump to RW without rebooting. + - "cold": Cold reboot. + - "disable-jump": Disable jump until next reboot. + - "hibernate": Hibernate the EC. + - "at-shutdown": Reboot after an AP shutdown. + +What: /sys/class/chromeos//version +Date: August 2015 +KernelVersion: 4.2 +Description: + Show the information about the EC software and hardware. diff --git a/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-lightbar b/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-lightbar new file mode 100644 index 000000000..57a037791 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-lightbar @@ -0,0 +1,74 @@ +What: /sys/class/chromeos//lightbar/brightness +Date: August 2015 +KernelVersion: 4.2 +Description: + Writing to this file adjusts the overall brightness of + the lightbar, separate from any color intensity. The + valid range is 0 (off) to 255 (maximum brightness). + +What: /sys/class/chromeos//lightbar/interval_msec +Date: August 2015 +KernelVersion: 4.2 +Description: + The lightbar is controlled by an embedded controller (EC), + which also manages the keyboard, battery charging, fans, + and other system hardware. To prevent unprivileged users + from interfering with the other EC functions, the rate at + which the lightbar control files can be read or written is + limited. + + Reading this file will return the number of milliseconds + that must elapse between accessing any of the lightbar + functions through this interface. Going faster will simply + block until the necessary interval has lapsed. The interval + applies uniformly to all accesses of any kind by any user. + +What: /sys/class/chromeos//lightbar/led_rgb +Date: August 2015 +KernelVersion: 4.2 +Description: + This allows you to control each LED segment. If the + lightbar is already running one of the automatic + sequences, you probably won’t see anything change because + your color setting will be almost immediately replaced. + To get useful results, you should stop the lightbar + sequence first. + + The values written to this file are sets of four integers, + indicating LED, RED, GREEN, BLUE. The LED number is 0 to 3 + to select a single segment, or 4 to set all four segments + to the same value at once. The RED, GREEN, and BLUE + numbers should be in the range 0 (off) to 255 (maximum). + You can update more than one segment at a time by writing + more than one set of four integers. + +What: /sys/class/chromeos//lightbar/program +Date: August 2015 +KernelVersion: 4.2 +Description: + This allows you to upload and run custom lightbar sequences. + +What: /sys/class/chromeos//lightbar/sequence +Date: August 2015 +KernelVersion: 4.2 +Description: + The Pixel lightbar has a number of built-in sequences + that it displays under various conditions, such as at + power on, shut down, or while running. Reading from this + file displays the current sequence that the lightbar is + displaying. Writing to this file allows you to change the + sequence. + +What: /sys/class/chromeos//lightbar/userspace_control +Date: August 2015 +KernelVersion: 4.2 +Description: + This allows you to take the control of the lightbar. This + prevents the kernel from going through its normal + sequences. + +What: /sys/class/chromeos//lightbar/version +Date: August 2015 +KernelVersion: 4.2 +Description: + Show the information about the lightbar version. diff --git a/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-vbc b/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-vbc new file mode 100644 index 000000000..38c5aaaaa --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-chromeos-driver-cros-ec-vbc @@ -0,0 +1,6 @@ +What: /sys/class/chromeos//vbc/vboot_context +Date: October 2015 +KernelVersion: 4.4 +Description: + Read/write the verified boot context data included on a + small nvram space on some EC implementations. diff --git a/Documentation/ABI/testing/sysfs-class-cxl b/Documentation/ABI/testing/sysfs-class-cxl new file mode 100644 index 000000000..594fda254 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-cxl @@ -0,0 +1,270 @@ +Please note that attributes that are shared between devices are stored in +the directory pointed to by the symlink device/. +For example, the real path of the attribute /sys/class/cxl/afu0.0s/irqs_max is +/sys/class/cxl/afu0.0s/device/irqs_max, i.e. /sys/class/cxl/afu0.0/irqs_max. + + +Slave contexts (eg. /sys/class/cxl/afu0.0s): + +What: /sys/class/cxl//afu_err_buf +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + AFU Error Buffer contents. The contents of this file are + application specific and depends on the AFU being used. + Applications interacting with the AFU can use this attribute + to know about the current error condition and take appropriate + action like logging the event etc. + + +What: /sys/class/cxl//irqs_max +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + Decimal value of maximum number of interrupts that can be + requested by userspace. The default on probe is the maximum + that hardware can support (eg. 2037). Write values will limit + userspace applications to that many userspace interrupts. Must + be >= irqs_min. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//irqs_min +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the minimum number of interrupts that + userspace must request on a CXL_START_WORK ioctl. Userspace may + omit the num_interrupts field in the START_WORK IOCTL to get + this minimum automatically. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//mmio_size +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the size of the MMIO space that may be mmaped + by userspace. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//modes_supported +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + List of the modes this AFU supports. One per line. + Valid entries are: "dedicated_process" and "afu_directed" +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//mode +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + The current mode the AFU is using. Will be one of the modes + given in modes_supported. Writing will change the mode + provided that no user contexts are attached. +Users: https://github.com/ibm-capi/libcxl + + +What: /sys/class/cxl//prefault_mode +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + Set the mode for prefaulting in segments into the segment table + when performing the START_WORK ioctl. Only applicable when + running under hashed page table mmu. + Possible values: + + ======================= ====================================== + none No prefaulting (default) + work_element_descriptor Treat the work element + descriptor as an effective address and + prefault what it points to. + all all segments process calling + START_WORK maps. + ======================= ====================================== + +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//reset +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: write only + Writing 1 here will reset the AFU provided there are not + contexts active on the AFU. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//api_version +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the current version of the kernel/user API. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//api_version_compatible +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the lowest version of the userspace API + this kernel supports. +Users: https://github.com/ibm-capi/libcxl + + +AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0): + +An AFU may optionally export one or more PCIe like configuration records, known +as AFU configuration records, which will show up here (if present). + +What: /sys/class/cxl//cr/vendor +Date: February 2015 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Hexadecimal value of the vendor ID found in this AFU + configuration record. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//cr/device +Date: February 2015 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Hexadecimal value of the device ID found in this AFU + configuration record. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//cr/class +Date: February 2015 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Hexadecimal value of the class code found in this AFU + configuration record. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//cr/config +Date: February 2015 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + This binary file provides raw access to the AFU configuration + record. The format is expected to match the either the standard + or extended configuration space defined by the PCIe + specification. +Users: https://github.com/ibm-capi/libcxl + + + +Master contexts (eg. /sys/class/cxl/afu0.0m) + +What: /sys/class/cxl/m/mmio_size +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the size of the MMIO space that may be mmaped + by userspace. This includes all slave contexts space also. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl/m/pp_mmio_len +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Decimal value of the Per Process MMIO space length. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl/m/pp_mmio_off +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + (not in a guest) + Decimal value of the Per Process MMIO space offset. +Users: https://github.com/ibm-capi/libcxl + + +Card info (eg. /sys/class/cxl/card0) + +What: /sys/class/cxl//caia_version +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Identifies the CAIA Version the card implements. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//psl_revision +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Identifies the revision level of the PSL. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//base_image +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + (not in a guest) + Identifies the revision level of the base image for devices + that support loadable PSLs. For FPGAs this field identifies + the image contained in the on-adapter flash which is loaded + during the initial program load. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//image_loaded +Date: September 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + (not in a guest) + Will return "user" or "factory" depending on the image loaded + onto the card. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//load_image_on_perst +Date: December 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + (not in a guest) + Valid entries are "none", "user", and "factory". + "none" means PERST will not cause image to be loaded to the + card. A power cycle is required to load the image. + "none" could be useful for debugging because the trace arrays + are preserved. + + "user" and "factory" means PERST will cause either the user or + user or factory image to be loaded. + Default is to reload on PERST whichever image the card has + loaded. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//reset +Date: October 2014 +Contact: linuxppc-dev@lists.ozlabs.org +Description: write only + Writing 1 will issue a PERST to card provided there are no + contexts active on any one of the card AFUs. This may cause + the card to reload the FPGA depending on load_image_on_perst. + Writing -1 will do a force PERST irrespective of any active + contexts on the card AFUs. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//perst_reloads_same_image +Date: July 2015 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + (not in a guest) + Trust that when an image is reloaded via PERST, it will not + have changed. + + == ================================================= + 0 don't trust, the image may be different (default) + 1 trust that the image will not change. + == ================================================= +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//psl_timebase_synced +Date: March 2016 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Returns 1 if the psl timebase register is synchronized + with the core timebase register, 0 otherwise. +Users: https://github.com/ibm-capi/libcxl + +What: /sys/class/cxl//tunneled_ops_supported +Date: May 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Returns 1 if tunneled operations are supported in capi mode, + 0 otherwise. +Users: https://github.com/ibm-capi/libcxl diff --git a/Documentation/ABI/testing/sysfs-class-devfreq b/Documentation/ABI/testing/sysfs-class-devfreq new file mode 100644 index 000000000..1e7e0bb4c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-devfreq @@ -0,0 +1,134 @@ +What: /sys/class/devfreq/.../ +Date: September 2011 +Contact: MyungJoo Ham +Description: + Provide a place in sysfs for the devfreq objects. + This allows accessing various devfreq specific variables. + The name of devfreq object denoted as ... is same as the + name of device using devfreq. + +What: /sys/class/devfreq/.../name +Date: November 2019 +Contact: Chanwoo Choi +Description: + The /sys/class/devfreq/.../name shows the name of device + of the corresponding devfreq object. + +What: /sys/class/devfreq/.../governor +Date: September 2011 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../governor show or set the name of the + governor used by the corresponding devfreq object. + +What: /sys/class/devfreq/.../cur_freq +Date: September 2011 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../cur_freq shows the current + frequency of the corresponding devfreq object. Same as + target_freq when get_cur_freq() is not implemented by + devfreq driver. + +What: /sys/class/devfreq/.../target_freq +Date: September 2012 +Contact: Rajagopal Venkat +Description: + The /sys/class/devfreq/.../target_freq shows the next governor + predicted target frequency of the corresponding devfreq object. + +What: /sys/class/devfreq/.../trans_stat +Date: October 2012 +Contact: MyungJoo Ham +Description: + This ABI shows or clears the statistics of devfreq behavior + on a specific device. It shows the time spent in each state + and the number of transitions between states. + In order to activate this ABI, the devfreq target device + driver should provide the list of available frequencies + with its profile. If need to reset the statistics of devfreq + behavior on a specific device, enter 0(zero) to 'trans_stat' + as following:: + + echo 0 > /sys/class/devfreq/.../trans_stat + + If the transition table is bigger than PAGE_SIZE, reading + this will return an -EFBIG error. + +What: /sys/class/devfreq/.../available_frequencies +Date: October 2012 +Contact: Nishanth Menon +Description: + The /sys/class/devfreq/.../available_frequencies shows + the available frequencies of the corresponding devfreq object. + This is a snapshot of available frequencies and not limited + by the min/max frequency restrictions. + +What: /sys/class/devfreq/.../available_governors +Date: October 2012 +Contact: Nishanth Menon +Description: + The /sys/class/devfreq/.../available_governors shows + currently available governors in the system. + +What: /sys/class/devfreq/.../min_freq +Date: January 2013 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../min_freq shows and stores + the minimum frequency requested by users. It is 0 if + the user does not care. min_freq overrides the + frequency requested by governors. + +What: /sys/class/devfreq/.../max_freq +Date: January 2013 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../max_freq shows and stores + the maximum frequency requested by users. It is 0 if + the user does not care. max_freq overrides the + frequency requested by governors and min_freq. + The max_freq overrides min_freq because max_freq may be + used to throttle devices to avoid overheating. + +What: /sys/class/devfreq/.../polling_interval +Date: September 2011 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../polling_interval shows and sets + the requested polling interval of the corresponding devfreq + object. The values are represented in ms. If the value is + less than 1 jiffy, it is considered to be 0, which means + no polling. This value is meaningless if the governor is + not polling. + + A list of governors that support the node: + - simple_ondmenad + - tegra_actmon + +What: /sys/class/devfreq/.../userspace/set_freq +Date: September 2011 +Contact: MyungJoo Ham +Description: + The /sys/class/devfreq/.../userspace/set_freq shows and + sets the requested frequency for the devfreq object if + userspace governor is in effect. + + A list of governors that support the node: + - userspace + +What: /sys/class/devfreq/.../timer +Date: July 2020 +Contact: Chanwoo Choi +Description: + This ABI shows and stores the kind of work timer by users. + This work timer is used by devfreq workqueue in order to + monitor the device status such as utilization. The user + can change the work timer on runtime according to their demand + as following:: + + echo deferrable > /sys/class/devfreq/.../timer + echo delayed > /sys/class/devfreq/.../timer + + A list of governors that support the node: + - simple_ondemand diff --git a/Documentation/ABI/testing/sysfs-class-devfreq-event b/Documentation/ABI/testing/sysfs-class-devfreq-event new file mode 100644 index 000000000..dbe48495e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-devfreq-event @@ -0,0 +1,25 @@ +What: /sys/class/devfreq-event/event/ +Date: January 2017 +Contact: Chanwoo Choi +Description: + Provide a place in sysfs for the devfreq-event objects. + This allows accessing various devfreq-event specific variables. + The name of devfreq-event object denoted as 'event' which + includes the unique number of 'x' for each devfreq-event object. + +What: /sys/class/devfreq-event/event/name +Date: January 2017 +Contact: Chanwoo Choi +Description: + The /sys/class/devfreq-event/event/name attribute contains + the name of the devfreq-event object. This attribute is + read-only. + +What: /sys/class/devfreq-event/event/enable_count +Date: January 2017 +Contact: Chanwoo Choi +Description: + The /sys/class/devfreq-event/event/enable_count attribute + contains the reference count to enable the devfreq-event + object. If the device is enabled, the value of attribute is + greater than zero. diff --git a/Documentation/ABI/testing/sysfs-class-devlink b/Documentation/ABI/testing/sysfs-class-devlink new file mode 100644 index 000000000..8a21ce515 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-devlink @@ -0,0 +1,130 @@ +What: /sys/class/devlink/.../ +Date: May 2020 +Contact: Saravana Kannan +Description: + Provide a place in sysfs for the device link objects in the + kernel at any given time. The name of a device link directory, + denoted as ... above, is of the form -- + where is the supplier bus:device name and + is the consumer bus:device name. + +What: /sys/class/devlink/.../auto_remove_on +Date: May 2020 +Contact: Saravana Kannan +Description: + This file indicates if the device link will ever be + automatically removed by the driver core when the consumer and + supplier devices themselves are still present. + + This will be one of the following strings: + + - 'consumer unbind' + - 'supplier unbind' + - 'never' + + 'consumer unbind' means the device link will be removed when + the consumer's driver is unbound from the consumer device. + + 'supplier unbind' means the device link will be removed when + the supplier's driver is unbound from the supplier device. + + 'never' means the device link will not be automatically removed + when as long as the supplier and consumer devices themselves + are still present. + +What: /sys/class/devlink/.../consumer +Date: May 2020 +Contact: Saravana Kannan +Description: + This file is a symlink to the consumer device's sysfs directory. + +What: /sys/class/devlink/.../runtime_pm +Date: May 2020 +Contact: Saravana Kannan +Description: + This file indicates if the device link has any impact on the + runtime power management behavior of the consumer and supplier + devices. For example: Making sure the supplier doesn't enter + runtime suspend while the consumer is active. + + This will be one of the following strings: + + === ======================================== + '0' Does not affect runtime power management + '1' Affects runtime power management + === ======================================== + +What: /sys/class/devlink/.../status +Date: May 2020 +Contact: Saravana Kannan +Description: + This file indicates the status of the device link. The status + of a device link is affected by whether the supplier and + consumer devices have been bound to their corresponding + drivers. The status of a device link also affects the binding + and unbinding of the supplier and consumer devices with their + drivers and also affects whether the software state of the + supplier device is synced with the hardware state of the + supplier device after boot up. + See also: sysfs-devices-state_synced. + + This will be one of the following strings: + + - 'not tracked' + - 'dormant' + - 'available' + - 'consumer probing' + - 'active' + - 'supplier unbinding' + - 'unknown' + + 'not tracked' means this device link does not track the status + and has no impact on the binding, unbinding and syncing the + hardware and software device state. + + 'dormant' means the supplier and the consumer devices have not + bound to their driver. + + 'available' means the supplier has bound to its driver and is + available to supply resources to the consumer device. + + 'consumer probing' means the consumer device is currently + trying to bind to its driver. + + 'active' means the supplier and consumer devices have both + bound successfully to their drivers. + + 'supplier unbinding' means the supplier devices is currently in + the process of unbinding from its driver. + + 'unknown' means the state of the device link is not any of the + above. If this is ever the value, there's a bug in the kernel. + +What: /sys/class/devlink/.../supplier +Date: May 2020 +Contact: Saravana Kannan +Description: + This file is a symlink to the supplier device's sysfs directory. + +What: /sys/class/devlink/.../sync_state_only +Date: May 2020 +Contact: Saravana Kannan +Description: + This file indicates if the device link is limited to only + affecting the syncing of the hardware and software state of the + supplier device. + + This will be one of the following strings: + + === ================================ + '0' + '1' Affects runtime power management + === ================================ + + '0' means the device link can affect other device behaviors + like binding/unbinding, suspend/resume, runtime power + management, etc. + + '1' means the device link will only affect the syncing of + hardware and software state of the supplier device after boot + up and doesn't not affect other behaviors of the devices. diff --git a/Documentation/ABI/testing/sysfs-class-extcon b/Documentation/ABI/testing/sysfs-class-extcon new file mode 100644 index 000000000..f8e705375 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-extcon @@ -0,0 +1,101 @@ +What: /sys/class/extcon/.../ +Date: February 2012 +Contact: MyungJoo Ham +Description: + Provide a place in sysfs for the extcon objects. + This allows accessing extcon specific variables. + The name of extcon object denoted as ... is the name given + with extcon_dev_register. + + One extcon device denotes a single external connector + port. An external connector may have multiple cables + attached simultaneously. Many of docks, cradles, and + accessory cables have such capability. For example, + the 30-pin port of Nuri board (/arch/arm/mach-exynos) + may have both HDMI and Charger attached, or analog audio, + video, and USB cables attached simultaneously. + + If there are cables mutually exclusive with each other, + such binary relations may be expressed with extcon_dev's + mutually_exclusive array. + +What: /sys/class/extcon/.../name +Date: February 2012 +Contact: MyungJoo Ham +Description: + The /sys/class/extcon/.../name shows the name of the extcon + object. If the extcon object has an optional callback + "show_name" defined, the callback will provide the name with + this sysfs node. + +What: /sys/class/extcon/.../state +Date: February 2012 +Contact: MyungJoo Ham +Description: + The /sys/class/extcon/.../state shows and stores the cable + attach/detach information of the corresponding extcon object. + If the extcon object has an optional callback "show_state" + defined, the showing function is overridden with the optional + callback. + + If the default callback for showing function is used, the + format is like this:: + + # cat state + USB_OTG=1 + HDMI=0 + TA=1 + EAR_JACK=0 + # + + In this example, the extcon device has USB_OTG and TA + cables attached and HDMI and EAR_JACK cables detached. + + In order to update the state of an extcon device, enter a hex + state number starting with 0x:: + + # echo 0xHEX > state + + This updates the whole state of the extcon device. + Inputs of all the methods are required to meet the + mutually_exclusive conditions if they exist. + + It is recommended to use this "global" state interface if + you need to set the value atomically. The later state + interface associated with each cable cannot update + multiple cable states of an extcon device simultaneously. + +What: /sys/class/extcon/.../cable.X/name +Date: February 2012 +Contact: MyungJoo Ham +Description: + The /sys/class/extcon/.../cable.X/name shows the name of cable + "X" (integer between 0 and 31) of an extcon device. + +What: /sys/class/extcon/.../cable.X/state +Date: February 2012 +Contact: MyungJoo Ham +Description: + The /sys/class/extcon/.../cable.X/state shows and stores the + state of cable "X" (integer between 0 and 31) of an extcon + device. The state value is either 0 (detached) or 1 + (attached). + +What: /sys/class/extcon/.../mutually_exclusive/... +Date: December 2011 +Contact: MyungJoo Ham +Description: + Shows the relations of mutually exclusiveness. For example, + if the mutually_exclusive array of extcon device is + {0x3, 0x5, 0xC, 0x0}, then the output is:: + + # ls mutually_exclusive/ + 0x3 + 0x5 + 0xc + # + + Note that mutually_exclusive is a sub-directory of the extcon + device and the file names under the mutually_exclusive + directory show the mutually-exclusive sets, not the contents + of the files. diff --git a/Documentation/ABI/testing/sysfs-class-fc b/Documentation/ABI/testing/sysfs-class-fc new file mode 100644 index 000000000..3057a6d3b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fc @@ -0,0 +1,27 @@ +What: /sys/class/fc/fc_udev_device/appid_store +Date: Aug 2021 +Contact: Muneendra Kumar +Description: + This interface allows an admin to set an FC application + identifier in the blkcg associated with a cgroup id. The + identifier is typically a UUID that is associated with + an application or logical entity such as a virtual + machine or container group. The application or logical + entity utilizes a block device via the cgroup id. + FC adapter drivers may query the identifier and tag FC + traffic based on the identifier. FC host and FC fabric + entities can utilize the application id and FC traffic + tag to identify traffic sources. + + The interface expects a string ":" where: + is inode of the cgroup in hexadecimal + is user provided string upto 128 characters + in length. + + If an appid_store is done for a cgroup id that already + has an appid set, the new value will override the + previous value. + + If an admin wants to remove an FC application identifier + from a cgroup, an appid_store should be done with the + following string: ":" diff --git a/Documentation/ABI/testing/sysfs-class-fc_host b/Documentation/ABI/testing/sysfs-class-fc_host new file mode 100644 index 000000000..0a696cbd8 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fc_host @@ -0,0 +1,23 @@ +What: /sys/class/fc_host/hostX/statistics/fpin_cn_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of congestion notification + events recorded by the F_Port, reported using fabric + performance impact notification (FPIN) event. + +What: /sys/class/fc_host/hostX/statistics/fpin_li_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of link integrity error + events recorded by the F_Port/Nx_Port, reported using fabric + performance impact notification (FPIN) event. + +What: /sys/class/fc_host/hostX/statistics/fpin_dn_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of delivery related errors + recorded by the F_Port/Nx_Port, reported using fabric + performance impact notification (FPIN) event. diff --git a/Documentation/ABI/testing/sysfs-class-fc_remote_ports b/Documentation/ABI/testing/sysfs-class-fc_remote_ports new file mode 100644 index 000000000..55a951529 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fc_remote_ports @@ -0,0 +1,23 @@ +What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_cn_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of congestion notification + events recorded by the F_Port/Nx_Port, reported using fabric + performance impact notification (FPIN) event. + +What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_li_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of link integrity error + events recorded by the F_Port/Nx_Port, reported using fabric + performance impact notification (FPIN) event. + +What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_dn_yyy +Date: July 2020 +Contact: Shyam Sundar +Description: + These files contain the number of delivery related errors + recorded by the F_Port/Nx_Port, reported using fabric + performance impact notification (FPIN) event. diff --git a/Documentation/ABI/testing/sysfs-class-firmware b/Documentation/ABI/testing/sysfs-class-firmware new file mode 100644 index 000000000..978d3d500 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-firmware @@ -0,0 +1,77 @@ +What: /sys/class/firmware/.../data +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: The data sysfs file is used for firmware-fallback and for + firmware uploads. Cat a firmware image to this sysfs file + after you echo 1 to the loading sysfs file. When the firmware + image write is complete, echo 0 to the loading sysfs file. This + sequence will signal the completion of the firmware write and + signal the lower-level driver that the firmware data is + available. + +What: /sys/class/firmware/.../cancel +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: Write-only. For firmware uploads, write a "1" to this file to + request that the transfer of firmware data to the lower-level + device be canceled. This request will be rejected (EBUSY) if + the update cannot be canceled (e.g. a FLASH write is in + progress) or (ENODEV) if there is no firmware update in progress. + +What: /sys/class/firmware/.../error +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: Read-only. Returns a string describing a failed firmware + upload. This string will be in the form of :, + where will be one of the status strings described + for the status sysfs file and will be one of the + following: "hw-error", "timeout", "user-abort", "device-busy", + "invalid-file-size", "read-write-error", "flash-wearout". The + error sysfs file is only meaningful when the current firmware + upload status is "idle". If this file is read while a firmware + transfer is in progress, then the read will fail with EBUSY. + +What: /sys/class/firmware/.../loading +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: The loading sysfs file is used for both firmware-fallback and + for firmware uploads. Echo 1 onto the loading file to indicate + you are writing a firmware file to the data sysfs node. Echo + -1 onto this file to abort the data write or echo 0 onto this + file to indicate that the write is complete. For firmware + uploads, the zero value also triggers the transfer of the + firmware data to the lower-level device driver. + +What: /sys/class/firmware/.../remaining_size +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: Read-only. For firmware upload, this file contains the size + of the firmware data that remains to be transferred to the + lower-level device driver. The size value is initialized to + the full size of the firmware image that was previously + written to the data sysfs file. This value is periodically + updated during the "transferring" phase of the firmware + upload. + Format: "%u". + +What: /sys/class/firmware/.../status +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: Read-only. Returns a string describing the current status of + a firmware upload. The string will be one of the following: + idle, "receiving", "preparing", "transferring", "programming". + +What: /sys/class/firmware/.../timeout +Date: July 2022 +KernelVersion: 5.19 +Contact: Russ Weight +Description: This file supports the timeout mechanism for firmware + fallback. This file has no affect on firmware uploads. For + more information on timeouts please see the documentation + for firmware fallback. diff --git a/Documentation/ABI/testing/sysfs-class-firmware-attributes b/Documentation/ABI/testing/sysfs-class-firmware-attributes new file mode 100644 index 000000000..4cdba3477 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-firmware-attributes @@ -0,0 +1,366 @@ +What: /sys/class/firmware-attributes/*/attributes/*/ +Date: February 2021 +KernelVersion: 5.11 +Contact: Divya Bharathi , + Prasanth KSR + Dell.Client.Kernel@dell.com +Description: + A sysfs interface for systems management software to enable + configuration capability on supported systems. This directory + exposes interfaces for interacting with configuration options. + + Unless otherwise specified in an attribute description all attributes are optional + and will accept UTF-8 input. + + type: + A file that can be read to obtain the type of attribute. + This attribute is mandatory. + + The following are known types: + + - enumeration: a set of pre-defined valid values + - integer: a range of numerical values + - string + + All attribute types support the following values: + + current_value: + A file that can be read to obtain the current + value of the . + + This file can also be written to in order to update the value of a + + + This attribute is mandatory. + + default_value: + A file that can be read to obtain the default + value of the + + display_name: + A file that can be read to obtain a user friendly + description of the at + + display_name_language_code: + A file that can be read to obtain + the IETF language tag corresponding to the + "display_name" of the + + "enumeration"-type specific properties: + + possible_values: + A file that can be read to obtain the possible + values of the . Values are separated using + semi-colon (``;``). + + "integer"-type specific properties: + + min_value: + A file that can be read to obtain the lower + bound value of the + + max_value: + A file that can be read to obtain the upper + bound value of the + + scalar_increment: + A file that can be read to obtain the scalar value used for + increments of current_value this attribute accepts. + + "string"-type specific properties: + + max_length: + A file that can be read to obtain the maximum + length value of the + + min_length: + A file that can be read to obtain the minimum + length value of the + + Dell specific class extensions + ------------------------------ + + On Dell systems the following additional attributes are available: + + dell_modifier: + A file that can be read to obtain attribute-level + dependency rule. It says an attribute X will become read-only or + suppressed, if/if-not attribute Y is configured. + + modifier rules can be in following format:: + + [ReadOnlyIf:=] + [ReadOnlyIfNot:=] + [SuppressIf:=] + [SuppressIfNot:=] + + For example:: + + AutoOnFri/dell_modifier has value, + [SuppressIfNot:AutoOn=SelectDays] + + This means AutoOnFri will be suppressed in BIOS setup if AutoOn + attribute is not "SelectDays" and its value will not be effective + through sysfs until this rule is met. + + Enumeration attributes also support the following: + + dell_value_modifier: + A file that can be read to obtain value-level dependency. + This file is similar to dell_modifier but here, an + attribute's current value will be forcefully changed based + dependent attributes value. + + dell_value_modifier rules can be in following format:: + + [ForceIf:=] + [ForceIfNot:=] + + For example:: + + LegacyOrom/dell_value_modifier has value: + Disabled[ForceIf:SecureBoot=Enabled] + + This means LegacyOrom's current value will be forced to + "Disabled" in BIOS setup if SecureBoot is Enabled and its + value will not be effective through sysfs until this rule is + met. + +What: /sys/class/firmware-attributes/*/authentication/ +Date: February 2021 +KernelVersion: 5.11 +Contact: Divya Bharathi , + Prasanth KSR + Dell.Client.Kernel@dell.com +Description: + Devices support various authentication mechanisms which can be exposed + as a separate configuration object. + + For example a "BIOS Admin" password and "System" Password can be set, + reset or cleared using these attributes. + + - An "Admin" password is used for preventing modification to the BIOS + settings. + - A "System" password is required to boot a machine. + + Change in any of these two authentication methods will also generate an + uevent KOBJ_CHANGE. + + is_enabled: + A file that can be read to obtain a 0/1 flag to see if + authentication is enabled. + This attribute is mandatory. + + role: + The type of authentication used. + This attribute is mandatory. + + Known types: + bios-admin: + Representing BIOS administrator password + power-on: + Representing a password required to use + the system + system-mgmt: + Representing System Management password. + See Lenovo extensions section for details + HDD: + Representing HDD password + See Lenovo extensions section for details + NVMe: + Representing NVMe password + See Lenovo extensions section for details + + mechanism: + The means of authentication. This attribute is mandatory. + Only supported type currently is "password". + + max_password_length: + A file that can be read to obtain the + maximum length of the Password + + min_password_length: + A file that can be read to obtain the + minimum length of the Password + + current_password: + A write only value used for privileged access such as + setting attributes when a system or admin password is set + or resetting to a new password + + This attribute is mandatory when mechanism == "password". + + new_password: + A write only value that when used in tandem with + current_password will reset a system or admin password. + + Note, password management is session specific. If Admin password is set, + same password must be written into current_password file (required for + password-validation) and must be cleared once the session is over. + For example:: + + echo "password" > current_password + echo "disabled" > TouchScreen/current_value + echo "" > current_password + + Drivers may emit a CHANGE uevent when a password is set or unset + userspace may check it again. + + On Dell and Lenovo systems, if Admin password is set, then all BIOS attributes + require password validation. + On Lenovo systems if you change the Admin password the new password is not active until + the next boot. + + Lenovo specific class extensions + -------------------------------- + + On Lenovo systems the following additional settings are available: + + role: system-mgmt This gives the same authority as the bios-admin password to control + security related features. The authorities allocated can be set via + the BIOS menu SMP Access Control Policy + + role: HDD & NVMe This password is used to unlock access to the drive at boot. Note see + 'level' and 'index' extensions below. + + lenovo_encoding: + The encoding method that is used. This can be either "ascii" + or "scancode". Default is set to "ascii" + + lenovo_kbdlang: + The keyboard language method that is used. This is generally a + two char code (e.g. "us", "fr", "gr") and may vary per platform. + Default is set to "us" + + level: + Available for HDD and NVMe authentication to set 'user' or 'master' + privilege level. + If only the user password is configured then this should be used to + unlock the drive at boot. If both master and user passwords are set + then either can be used. If a master password is set a user password + is required. + This attribute defaults to 'user' level + + index: + Used with HDD and NVME authentication to set the drive index + that is being referenced (e.g hdd0, hdd1 etc) + This attribute defaults to device 0. + + certificate, signature, save_signature: + These attributes are used for certificate based authentication. This is + used in conjunction with a signing server as an alternative to password + based authentication. + The user writes to the attribute(s) with a BASE64 encoded string obtained + from the signing server. + The attributes can be displayed to check the stored value. + + Some usage examples: + + Installing a certificate to enable feature:: + + echo "supervisor password" > authentication/Admin/current_password + echo "signed certificate" > authentication/Admin/certificate + + Updating the installed certificate:: + + echo "signature" > authentication/Admin/signature + echo "signed certificate" > authentication/Admin/certificate + + Removing the installed certificate:: + + echo "signature" > authentication/Admin/signature + echo "" > authentication/Admin/certificate + + Changing a BIOS setting:: + + echo "signature" > authentication/Admin/signature + echo "save signature" > authentication/Admin/save_signature + echo Enable > attribute/PasswordBeep/current_value + + You cannot enable certificate authentication if a supervisor password + has not been set. + Clearing the certificate results in no bios-admin authentication method + being configured allowing anyone to make changes. + After any of these operations the system must reboot for the changes to + take effect. + + certificate_thumbprint: + Read only attribute used to display the MD5, SHA1 and SHA256 thumbprints + for the certificate installed in the BIOS. + + certificate_to_password: + Write only attribute used to switch from certificate based authentication + back to password based. + Usage:: + + echo "signature" > authentication/Admin/signature + echo "password" > authentication/Admin/certificate_to_password + + +What: /sys/class/firmware-attributes/*/attributes/pending_reboot +Date: February 2021 +KernelVersion: 5.11 +Contact: Divya Bharathi , + Prasanth KSR + Dell.Client.Kernel@dell.com +Description: + A read-only attribute reads 1 if a reboot is necessary to apply + pending BIOS attribute changes. Also, an uevent_KOBJ_CHANGE is + generated when it changes to 1. + + == ========================================= + 0 All BIOS attributes setting are current + 1 A reboot is necessary to get pending BIOS + attribute changes applied + == ========================================= + + Note, userspace applications need to follow below steps for efficient + BIOS management, + + 1. Check if admin password is set. If yes, follow session method for + password management as briefed under authentication section above. + 2. Before setting any attribute, check if it has any modifiers + or value_modifiers. If yes, incorporate them and then modify + attribute. + + Drivers may emit a CHANGE uevent when this value changes and userspace + may check it again. + +What: /sys/class/firmware-attributes/*/attributes/reset_bios +Date: February 2021 +KernelVersion: 5.11 +Contact: Divya Bharathi , + Prasanth KSR + Dell.Client.Kernel@dell.com +Description: + This attribute can be used to reset the BIOS Configuration. + Specifically, it tells which type of reset BIOS configuration is being + requested on the host. + + Reading from it returns a list of supported options encoded as: + + - 'builtinsafe' (Built in safe configuration profile) + - 'lastknowngood' (Last known good saved configuration profile) + - 'factory' (Default factory settings configuration profile) + - 'custom' (Custom saved configuration profile) + + The currently selected option is printed in square brackets as + shown below:: + + # echo "factory" > /sys/class/firmware-attributes/*/device/attributes/reset_bios + # cat /sys/class/firmware-attributes/*/device/attributes/reset_bios + builtinsafe lastknowngood [factory] custom + + Note that any changes to this attribute requires a reboot + for changes to take effect. + +What: /sys/class/firmware-attributes/*/attributes/debug_cmd +Date: July 2021 +KernelVersion: 5.14 +Contact: Mark Pearson +Description: + This write only attribute can be used to send debug commands to the BIOS. + This should only be used when recommended by the BIOS vendor. Vendors may + use it to enable extra debug attributes or BIOS features for testing purposes. + + Note that any changes to this attribute requires a reboot for changes to take effect. diff --git a/Documentation/ABI/testing/sysfs-class-fpga-bridge b/Documentation/ABI/testing/sysfs-class-fpga-bridge new file mode 100644 index 000000000..312ae2c57 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fpga-bridge @@ -0,0 +1,11 @@ +What: /sys/class/fpga_bridge//name +Date: January 2016 +KernelVersion: 4.5 +Contact: Alan Tull +Description: Name of low level FPGA bridge driver. + +What: /sys/class/fpga_bridge//state +Date: January 2016 +KernelVersion: 4.5 +Contact: Alan Tull +Description: Show bridge state as "enabled" or "disabled" diff --git a/Documentation/ABI/testing/sysfs-class-fpga-manager b/Documentation/ABI/testing/sysfs-class-fpga-manager new file mode 100644 index 000000000..d78689c35 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fpga-manager @@ -0,0 +1,60 @@ +What: /sys/class/fpga_manager//name +Date: August 2015 +KernelVersion: 4.3 +Contact: Alan Tull +Description: Name of low level fpga manager driver. + +What: /sys/class/fpga_manager//state +Date: August 2015 +KernelVersion: 4.3 +Contact: Alan Tull +Description: Read fpga manager state as a string. + The intent is to provide enough detail that if something goes + wrong during FPGA programming (something that the driver can't + fix) then userspace can know, i.e. if the firmware request + fails, that could be due to not being able to find the firmware + file. + + This is a superset of FPGA states and fpga manager driver + states. The fpga manager driver is walking through these steps + to get the FPGA into a known operating state. It's a sequence, + though some steps may get skipped. Valid FPGA states will vary + by manufacturer; this is a superset. + + * unknown = can't determine state + * power off = FPGA power is off + * power up = FPGA reports power is up + * reset = FPGA held in reset state + * firmware request = firmware class request in progress + * firmware request error = firmware request failed + * write init = preparing FPGA for programming + * write init error = Error while preparing FPGA for programming + * write = FPGA ready to receive image data + * write error = Error while programming + * write complete = Doing post programming steps + * write complete error = Error while doing post programming + * operating = FPGA is programmed and operating + +What: /sys/class/fpga_manager//status +Date: June 2018 +KernelVersion: 4.19 +Contact: Wu Hao +Description: Read fpga manager status as a string. + If FPGA programming operation fails, it could be caused by crc + error or incompatible bitstream image. The intent of this + interface is to provide more detailed information for FPGA + programming errors to userspace. This is a list of strings for + the supported status. + + * reconfig operation error - invalid operations detected by + reconfiguration hardware. + e.g. start reconfiguration + with errors not cleared + * reconfig CRC error - CRC error detected by + reconfiguration hardware. + * reconfig incompatible image - reconfiguration image is + incompatible with hardware + * reconfig IP protocol error - protocol errors detected by + reconfiguration hardware + * reconfig fifo overflow error - FIFO overflow detected by + reconfiguration hardware diff --git a/Documentation/ABI/testing/sysfs-class-fpga-region b/Documentation/ABI/testing/sysfs-class-fpga-region new file mode 100644 index 000000000..bc7ec644a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-fpga-region @@ -0,0 +1,9 @@ +What: /sys/class/fpga_region//compat_id +Date: June 2018 +KernelVersion: 4.19 +Contact: Wu Hao +Description: FPGA region id for compatibility check, e.g. compatibility + of the FPGA reconfiguration hardware and image. This value + is defined or calculated by the layer that is creating the + FPGA region. This interface returns the compat_id value or + just error code -ENOENT in case compat_id is not used. diff --git a/Documentation/ABI/testing/sysfs-class-gnss b/Documentation/ABI/testing/sysfs-class-gnss new file mode 100644 index 000000000..9650f3a7f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-gnss @@ -0,0 +1,17 @@ +What: /sys/class/gnss/gnss/type +Date: May 2018 +KernelVersion: 4.18 +Contact: Johan Hovold +Description: + The GNSS receiver type. The currently identified types reflect + the protocol(s) supported by the receiver: + + ====== =========== + "NMEA" NMEA 0183 + "SiRF" SiRF Binary + "UBX" UBX + ====== =========== + + Note that also non-"NMEA" type receivers typically support a + subset of NMEA 0183 with vendor extensions (e.g. to allow + switching to a vendor protocol). diff --git a/Documentation/ABI/testing/sysfs-class-hwmon b/Documentation/ABI/testing/sysfs-class-hwmon new file mode 100644 index 000000000..7271781a2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-hwmon @@ -0,0 +1,949 @@ +What: /sys/class/hwmon/hwmonX/name +Description: + The chip name. + This should be a short, lowercase string, not containing + whitespace, dashes, or the wildcard character '*'. + This attribute represents the chip name. It is the only + mandatory attribute. + I2C devices get this attribute created automatically. + + RO + +What: /sys/class/hwmon/hwmonX/label +Description: + A descriptive label that allows to uniquely identify a + device within the system. + The contents of the label are free-form. + + RO + +What: /sys/class/hwmon/hwmonX/update_interval +Description: + The interval at which the chip will update readings. + Unit: millisecond + + RW + + Some devices have a variable update rate or interval. + This attribute can be used to change it to the desired value. + +What: /sys/class/hwmon/hwmonX/inY_min +Description: + Voltage min value. + + Unit: millivolt + + RW + +What: /sys/class/hwmon/hwmonX/inY_lcrit +Description: + Voltage critical min value. + + Unit: millivolt + + RW + + If voltage drops to or below this limit, the system may + take drastic action such as power down or reset. At the very + least, it should report a fault. + +What: /sys/class/hwmon/hwmonX/inY_max +Description: + Voltage max value. + + Unit: millivolt + + RW + +What: /sys/class/hwmon/hwmonX/inY_crit +Description: + Voltage critical max value. + + Unit: millivolt + + RW + + If voltage reaches or exceeds this limit, the system may + take drastic action such as power down or reset. At the very + least, it should report a fault. + +What: /sys/class/hwmon/hwmonX/inY_input +Description: + Voltage input value. + + Unit: millivolt + + RO + + Voltage measured on the chip pin. + + Actual voltage depends on the scaling resistors on the + motherboard, as recommended in the chip datasheet. + + This varies by chip and by motherboard. + Because of this variation, values are generally NOT scaled + by the chip driver, and must be done by the application. + However, some drivers (notably lm87 and via686a) + do scale, because of internal resistors built into a chip. + These drivers will output the actual voltage. Rule of + thumb: drivers should report the voltage values at the + "pins" of the chip. + +What: /sys/class/hwmon/hwmonX/inY_average +Description: + Average voltage + + Unit: millivolt + + RO + +What: /sys/class/hwmon/hwmonX/inY_lowest +Description: + Historical minimum voltage + + Unit: millivolt + + RO + +What: /sys/class/hwmon/hwmonX/inY_highest +Description: + Historical maximum voltage + + Unit: millivolt + + RO + +What: /sys/class/hwmon/hwmonX/inY_reset_history +Description: + Reset inX_lowest and inX_highest + + WO + +What: /sys/class/hwmon/hwmonX/in_reset_history +Description: + Reset inX_lowest and inX_highest for all sensors + + WO + +What: /sys/class/hwmon/hwmonX/inY_label +Description: + Suggested voltage channel label. + + Text string + + Should only be created if the driver has hints about what + this voltage channel is being used for, and user-space + doesn't. In all other cases, the label is provided by + user-space. + + RO + +What: /sys/class/hwmon/hwmonX/inY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/cpuY_vid +Description: + CPU core reference voltage. + + Unit: millivolt + + RO + + Not always correct. + +What: /sys/class/hwmon/hwmonX/vrm +Description: + Voltage Regulator Module version number. + + RW (but changing it should no more be necessary) + + Originally the VRM standard version multiplied by 10, but now + an arbitrary number, as not all standards have a version + number. + + Affects the way the driver calculates the CPU core reference + voltage from the vid pins. + +What: /sys/class/hwmon/hwmonX/inY_rated_min +Description: + Minimum rated voltage. + + Unit: millivolt + + RO + +What: /sys/class/hwmon/hwmonX/inY_rated_max +Description: + Maximum rated voltage. + + Unit: millivolt + + RO + +What: /sys/class/hwmon/hwmonX/fanY_min +Description: + Fan minimum value + + Unit: revolution/min (RPM) + + RW + +What: /sys/class/hwmon/hwmonX/fanY_max +Description: + Fan maximum value + + Unit: revolution/min (RPM) + + Only rarely supported by the hardware. + RW + +What: /sys/class/hwmon/hwmonX/fanY_input +Description: + Fan input value. + + Unit: revolution/min (RPM) + + RO + +What: /sys/class/hwmon/hwmonX/fanY_div +Description: + Fan divisor. + + Integer value in powers of two (1, 2, 4, 8, 16, 32, 64, 128). + + RW + + Some chips only support values 1, 2, 4 and 8. + Note that this is actually an internal clock divisor, which + affects the measurable speed range, not the read value. + +What: /sys/class/hwmon/hwmonX/fanY_pulses +Description: + Number of tachometer pulses per fan revolution. + + Integer value, typically between 1 and 4. + + RW + + This value is a characteristic of the fan connected to the + device's input, so it has to be set in accordance with the fan + model. + + Should only be created if the chip has a register to configure + the number of pulses. In the absence of such a register (and + thus attribute) the value assumed by all devices is 2 pulses + per fan revolution. + +What: /sys/class/hwmon/hwmonX/fanY_target +Description: + Desired fan speed + + Unit: revolution/min (RPM) + + RW + + Only makes sense if the chip supports closed-loop fan speed + control based on the measured fan speed. + +What: /sys/class/hwmon/hwmonX/fanY_label +Description: + Suggested fan channel label. + + Text string + + Should only be created if the driver has hints about what + this fan channel is being used for, and user-space doesn't. + In all other cases, the label is provided by user-space. + + RO + +What: /sys/class/hwmon/hwmonX/fanY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/pwmY +Description: + Pulse width modulation fan control. + + Integer value in the range 0 to 255 + + RW + + 255 is max or 100%. + +What: /sys/class/hwmon/hwmonX/pwmY_enable +Description: + Fan speed control method: + + - 0: no fan speed control (i.e. fan at full speed) + - 1: manual fan speed control enabled (using `pwmY`) + - 2+: automatic fan speed control enabled + + Check individual chip documentation files for automatic mode + details. + + RW + +What: /sys/class/hwmon/hwmonX/pwmY_mode +Description: + - 0: DC mode (direct current) + - 1: PWM mode (pulse-width modulation) + + RW + +What: /sys/class/hwmon/hwmonX/pwmY_freq +Description: + Base PWM frequency in Hz. + + Only possibly available when pwmN_mode is PWM, but not always + present even then. + + RW + +What: /sys/class/hwmon/hwmonX/pwmY_auto_channels_temp +Description: + Select which temperature channels affect this PWM output in + auto mode. + + Bitfield, 1 is temp1, 2 is temp2, 4 is temp3 etc... + Which values are possible depend on the chip used. + + RW + +What: /sys/class/hwmon/hwmonX/pwmY_auto_pointZ_pwm +What: /sys/class/hwmon/hwmonX/pwmY_auto_pointZ_temp +What: /sys/class/hwmon/hwmonX/pwmY_auto_pointZ_temp_hyst +Description: + Define the PWM vs temperature curve. + + Number of trip points is chip-dependent. Use this for chips + which associate trip points to PWM output channels. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_auto_pointZ_pwm +What: /sys/class/hwmon/hwmonX/tempY_auto_pointZ_temp +What: /sys/class/hwmon/hwmonX/tempY_auto_pointZ_temp_hyst +Description: + Define the PWM vs temperature curve. + + Number of trip points is chip-dependent. Use this for chips + which associate trip points to temperature channels. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_type +Description: + Sensor type selection. + + Integers 1 to 6 + + RW + + - 1: CPU embedded diode + - 2: 3904 transistor + - 3: thermal diode + - 4: thermistor + - 5: AMD AMDSI + - 6: Intel PECI + + Not all types are supported by all chips + +What: /sys/class/hwmon/hwmonX/tempY_max +Description: + Temperature max value. + + Unit: millidegree Celsius (or millivolt, see below) + + RW + +What: /sys/class/hwmon/hwmonX/tempY_min +Description: + Temperature min value. + + Unit: millidegree Celsius + + RW + +What: /sys/class/hwmon/hwmonX/tempY_max_hyst +Description: + Temperature hysteresis value for max limit. + + Unit: millidegree Celsius + + Must be reported as an absolute temperature, NOT a delta + from the max value. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_min_hyst +Description: + Temperature hysteresis value for min limit. + Unit: millidegree Celsius + + Must be reported as an absolute temperature, NOT a delta + from the min value. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_input +Description: + Temperature input value. + + Unit: millidegree Celsius + + RO + +What: /sys/class/hwmon/hwmonX/tempY_crit +Description: + Temperature critical max value, typically greater than + corresponding temp_max values. + + Unit: millidegree Celsius + + RW + +What: /sys/class/hwmon/hwmonX/tempY_crit_alarm +Description: + Critical high temperature alarm flag. + + - 0: OK + - 1: temperature has reached tempY_crit + + RW + + Contrary to regular alarm flags which clear themselves + automatically when read, this one sticks until cleared by + the user. This is done by writing 0 to the file. Writing + other values is unsupported. + +What: /sys/class/hwmon/hwmonX/tempY_crit_hyst +Description: + Temperature hysteresis value for critical limit. + + Unit: millidegree Celsius + + Must be reported as an absolute temperature, NOT a delta + from the critical value. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_emergency +Description: + Temperature emergency max value, for chips supporting more than + two upper temperature limits. Must be equal or greater than + corresponding temp_crit values. + + Unit: millidegree Celsius + + RW + +What: /sys/class/hwmon/hwmonX/tempY_emergency_hyst +Description: + Temperature hysteresis value for emergency limit. + + Unit: millidegree Celsius + + Must be reported as an absolute temperature, NOT a delta + from the emergency value. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_lcrit +Description: + Temperature critical min value, typically lower than + corresponding temp_min values. + + Unit: millidegree Celsius + + RW + +What: /sys/class/hwmon/hwmonX/tempY_lcrit_hyst +Description: + Temperature hysteresis value for critical min limit. + + Unit: millidegree Celsius + + Must be reported as an absolute temperature, NOT a delta + from the critical min value. + + RW + +What: /sys/class/hwmon/hwmonX/tempY_offset +Description: + Temperature offset which is added to the temperature reading + by the chip. + + Unit: millidegree Celsius + + Read/Write value. + +What: /sys/class/hwmon/hwmonX/tempY_label +Description: + Suggested temperature channel label. + + Text string + + Should only be created if the driver has hints about what + this temperature channel is being used for, and user-space + doesn't. In all other cases, the label is provided by + user-space. + + RO + +What: /sys/class/hwmon/hwmonX/tempY_lowest +Description: + Historical minimum temperature + + Unit: millidegree Celsius + + RO + +What: /sys/class/hwmon/hwmonX/tempY_highest +Description: + Historical maximum temperature + + Unit: millidegree Celsius + + RO + +What: /sys/class/hwmon/hwmonX/tempY_reset_history +Description: + Reset temp_lowest and temp_highest + + WO + +What: /sys/class/hwmon/hwmonX/temp_reset_history +Description: + Reset temp_lowest and temp_highest for all sensors + + WO + +What: /sys/class/hwmon/hwmonX/tempY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/tempY_rated_min +Description: + Minimum rated temperature. + + Unit: millidegree Celsius + + RO + +What: /sys/class/hwmon/hwmonX/tempY_rated_max +Description: + Maximum rated temperature. + + Unit: millidegree Celsius + + RO + +What: /sys/class/hwmon/hwmonX/currY_max +Description: + Current max value + + Unit: milliampere + + RW + +What: /sys/class/hwmon/hwmonX/currY_min +Description: + Current min value. + + Unit: milliampere + + RW + +What: /sys/class/hwmon/hwmonX/currY_lcrit +Description: + Current critical low value + + Unit: milliampere + + RW + +What: /sys/class/hwmon/hwmonX/currY_crit +Description: + Current critical high value. + + Unit: milliampere + + RW + +What: /sys/class/hwmon/hwmonX/currY_input +Description: + Current input value + + Unit: milliampere + + RO + +What: /sys/class/hwmon/hwmonX/currY_average +Description: + Average current use + + Unit: milliampere + + RO + +What: /sys/class/hwmon/hwmonX/currY_lowest +Description: + Historical minimum current + + Unit: milliampere + + RO + +What: /sys/class/hwmon/hwmonX/currY_highest +Description: + Historical maximum current + Unit: milliampere + RO + +What: /sys/class/hwmon/hwmonX/currY_reset_history +Description: + Reset currX_lowest and currX_highest + + WO + +What: /sys/class/hwmon/hwmonX/curr_reset_history +Description: + Reset currX_lowest and currX_highest for all sensors + + WO + +What: /sys/class/hwmon/hwmonX/currY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/currY_rated_min +Description: + Minimum rated current. + + Unit: milliampere + + RO + +What: /sys/class/hwmon/hwmonX/currY_rated_max +Description: + Maximum rated current. + + Unit: milliampere + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average +Description: + Average power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average_interval +Description: + Power use averaging interval. A poll + notification is sent to this file if the + hardware changes the averaging interval. + + Unit: milliseconds + + RW + +What: /sys/class/hwmon/hwmonX/powerY_average_interval_max +Description: + Maximum power use averaging interval + + Unit: milliseconds + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average_interval_min +Description: + Minimum power use averaging interval + + Unit: milliseconds + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average_highest +Description: + Historical average maximum power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average_lowest +Description: + Historical average minimum power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_average_max +Description: + A poll notification is sent to + `powerY_average` when power use + rises above this value. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_average_min +Description: + A poll notification is sent to + `powerY_average` when power use + sinks below this value. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_input +Description: + Instantaneous power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_input_highest +Description: + Historical maximum power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_input_lowest +Description: + Historical minimum power use + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_reset_history +Description: + Reset input_highest, input_lowest, + average_highest and average_lowest. + + WO + +What: /sys/class/hwmon/hwmonX/powerY_accuracy +Description: + Accuracy of the power meter. + + Unit: Percent + + RO + +What: /sys/class/hwmon/hwmonX/powerY_cap +Description: + If power use rises above this limit, the + system should take action to reduce power use. + A poll notification is sent to this file if the + cap is changed by the hardware. The `*_cap` + files only appear if the cap is known to be + enforced by hardware. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_cap_hyst +Description: + Margin of hysteresis built around capping and + notification. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_cap_max +Description: + Maximum cap that can be set. + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_cap_min +Description: + Minimum cap that can be set. + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_max +Description: + Maximum power. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_crit +Description: + Critical maximum power. + + If power rises to or above this limit, the + system is expected take drastic action to reduce + power consumption, such as a system shutdown or + a forced powerdown of some devices. + + Unit: microWatt + + RW + +What: /sys/class/hwmon/hwmonX/powerY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return + -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/powerY_rated_min +Description: + Minimum rated power. + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/powerY_rated_max +Description: + Maximum rated power. + + Unit: microWatt + + RO + +What: /sys/class/hwmon/hwmonX/energyY_input +Description: + Cumulative energy use + + Unit: microJoule + + RO + +What: /sys/class/hwmon/hwmonX/energyY_enable +Description: + Enable or disable the sensors. + + When disabled the sensor read will return + -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/humidityY_input +Description: + Humidity + + Unit: milli-percent (per cent mille, pcm) + + RO + + +What: /sys/class/hwmon/hwmonX/humidityY_enable +Description: + Enable or disable the sensors + + When disabled the sensor read will return + -ENODATA. + + - 1: Enable + - 0: Disable + + RW + +What: /sys/class/hwmon/hwmonX/humidityY_rated_min +Description: + Minimum rated humidity. + + Unit: milli-percent (per cent mille, pcm) + + RO + +What: /sys/class/hwmon/hwmonX/humidityY_rated_max +Description: + Maximum rated humidity. + + Unit: milli-percent (per cent mille, pcm) + + RO + + +What: /sys/class/hwmon/hwmonX/intrusionY_alarm +Description: + Chassis intrusion detection + + - 0: OK + - 1: intrusion detected + + RW + + Contrary to regular alarm flags which clear themselves + automatically when read, this one sticks until cleared by + the user. This is done by writing 0 to the file. Writing + other values is unsupported. + +What: /sys/class/hwmon/hwmonX/intrusionY_beep +Description: + Chassis intrusion beep + + - 0: disable + - 1: enable + + RW + +What: /sys/class/hwmon/hwmonX/device/pec +Description: + PEC support on I2C devices + + - 0, off, n: disable + - 1, on, y: enable + + RW diff --git a/Documentation/ABI/testing/sysfs-class-intel_pmt b/Documentation/ABI/testing/sysfs-class-intel_pmt new file mode 100644 index 000000000..ed4c886a2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-intel_pmt @@ -0,0 +1,119 @@ +What: /sys/class/intel_pmt/ +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + The intel_pmt/ class directory contains information for + devices that expose hardware telemetry using Intel Platform + Monitoring Technology (PMT) + +What: /sys/class/intel_pmt/telem +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + The telem directory contains files describing an instance of + a PMT telemetry device that exposes hardware telemetry. Each + telem directory has an associated telem file. This file + may be opened and mapped or read to access the telemetry space + of the device. The register layout of the telemetry space is + determined from an XML file that matches the PCI device id and + GUID for the device. + +What: /sys/class/intel_pmt/telem/telem +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + (RO) The telemetry data for this telemetry device. This file + may be mapped or read to obtain the data. + +What: /sys/class/intel_pmt/telem/guid +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + (RO) The GUID for this telemetry device. The GUID identifies + the version of the XML file for the parent device that is to + be used to get the register layout. + +What: /sys/class/intel_pmt/telem/size +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + (RO) The size of telemetry region in bytes that corresponds to + the mapping size for the telem file. + +What: /sys/class/intel_pmt/telem/offset +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + (RO) The offset of telemetry region in bytes that corresponds to + the mapping for the telem file. + +What: /sys/class/intel_pmt/crashlog +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + The crashlog directory contains files for configuring an + instance of a PMT crashlog device that can perform crash data + recording. Each crashlog device has an associated crashlog + file. This file can be opened and mapped or read to access the + resulting crashlog buffer. The register layout for the buffer + can be determined from an XML file of specified GUID for the + parent device. + +What: /sys/class/intel_pmt/crashlog/crashlog +Date: October 2020 +KernelVersion: 5.10 +Contact: David Box +Description: + (RO) The crashlog buffer for this crashlog device. This file + may be mapped or read to obtain the data. + +What: /sys/class/intel_pmt/crashlog/guid +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + (RO) The GUID for this crashlog device. The GUID identifies the + version of the XML file for the parent device that should be + used to determine the register layout. + +What: /sys/class/intel_pmt/crashlog/size +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + (RO) The length of the result buffer in bytes that corresponds + to the size for the crashlog buffer. + +What: /sys/class/intel_pmt/crashlog/offset +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + (RO) The offset of the buffer in bytes that corresponds + to the mapping for the crashlog device. + +What: /sys/class/intel_pmt/crashlog/enable +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + (RW) Boolean value controlling if the crashlog functionality + is enabled for the crashlog device. + +What: /sys/class/intel_pmt/crashlog/trigger +Date: October 2020 +KernelVersion: 5.10 +Contact: Alexander Duyck +Description: + (RW) Boolean value controlling the triggering of the crashlog + device node. When read it provides data on if the crashlog has + been triggered. When written to it can be used to either clear + the current trigger by writing false, or to trigger a new + event if the trigger is not currently set. diff --git a/Documentation/ABI/testing/sysfs-class-iommu b/Documentation/ABI/testing/sysfs-class-iommu new file mode 100644 index 000000000..6d0a1b4be --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-iommu @@ -0,0 +1,17 @@ +What: /sys/class/iommu//devices/ +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + IOMMU drivers are able to link devices managed by a + given IOMMU here to allow association of IOMMU to + device. + +What: /sys/devices/.../iommu +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + IOMMU drivers are able to link the IOMMU for a + given device here to allow association of device to + IOMMU. diff --git a/Documentation/ABI/testing/sysfs-class-iommu-amd-iommu b/Documentation/ABI/testing/sysfs-class-iommu-amd-iommu new file mode 100644 index 000000000..d6ba8e8a4 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-iommu-amd-iommu @@ -0,0 +1,14 @@ +What: /sys/class/iommu//amd-iommu/cap +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + IOMMU capability header as documented in the AMD IOMMU + specification. Format: %x + +What: /sys/class/iommu//amd-iommu/features +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + Extended features of the IOMMU. Format: %llx diff --git a/Documentation/ABI/testing/sysfs-class-iommu-intel-iommu b/Documentation/ABI/testing/sysfs-class-iommu-intel-iommu new file mode 100644 index 000000000..258cc246d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-iommu-intel-iommu @@ -0,0 +1,32 @@ +What: /sys/class/iommu//intel-iommu/address +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + Physical address of the VT-d DRHD for this IOMMU. + Format: %llx. This allows association of a sysfs + intel-iommu with a DMAR DRHD table entry. + +What: /sys/class/iommu//intel-iommu/cap +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + The cached hardware capability register value + of this DRHD unit. Format: %llx. + +What: /sys/class/iommu//intel-iommu/ecap +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + The cached hardware extended capability register + value of this DRHD unit. Format: %llx. + +What: /sys/class/iommu//intel-iommu/version +Date: June 2014 +KernelVersion: 3.17 +Contact: Alex Williamson +Description: + The architecture version as reported from the + VT-d VER_REG. Format: %d:%d, major:minor diff --git a/Documentation/ABI/testing/sysfs-class-lcd b/Documentation/ABI/testing/sysfs-class-lcd new file mode 100644 index 000000000..35906bf7a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-lcd @@ -0,0 +1,23 @@ +What: /sys/class/lcd//lcd_power +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Control LCD power, values are FB_BLANK_* from fb.h + - FB_BLANK_UNBLANK (0) : power on. + - FB_BLANK_POWERDOWN (4) : power off + +What: /sys/class/lcd//contrast +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Current contrast of this LCD device. Value is between 0 and + /sys/class/lcd//max_contrast. + +What: /sys/class/lcd//max_contrast +Date: April 2005 +KernelVersion: 2.6.12 +Contact: Richard Purdie +Description: + Maximum contrast for this LCD device. diff --git a/Documentation/ABI/testing/sysfs-class-led b/Documentation/ABI/testing/sysfs-class-led new file mode 100644 index 000000000..2e24ac3bd --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led @@ -0,0 +1,83 @@ +What: /sys/class/leds//brightness +Date: March 2006 +KernelVersion: 2.6.17 +Contact: Richard Purdie +Description: + Set the brightness of the LED. + + Most LEDs don't have hardware brightness support, so will + just be turned on for non-zero brightness settings. + + .. Note:: + + For multicolor LEDs, writing to this file will update all + LEDs within the group to a calculated percentage of what + each color LED intensity is set to. + + The percentage is calculated for each grouped LED via + the equation below:: + + led_brightness = brightness * multi_intensity/max_brightness + + For additional details please refer to + Documentation/leds/leds-class-multicolor.rst. + + The value is between 0 and + /sys/class/leds//max_brightness. + + Writing 0 to this file clears active trigger. + + Writing non-zero to this file while trigger is active changes the + top brightness trigger is going to use. + + + +What: /sys/class/leds//max_brightness +Date: March 2006 +KernelVersion: 2.6.17 +Contact: Richard Purdie +Description: + Maximum brightness level for this LED, default is 255 (LED_FULL). + + If the LED does not support different brightness levels, this + should be 1. + +What: /sys/class/leds//brightness_hw_changed +Date: January 2017 +KernelVersion: 4.11 +Description: + Last hardware set brightness level for this LED. Some LEDs + may be changed autonomously by hardware/firmware. Only LEDs + where this happens and the driver can detect this, will have + this file. + + This file supports poll() to detect when the hardware changes + the brightness. + + Reading this file will return the last brightness level set + by the hardware, this may be different from the current + brightness. Reading this file when no hw brightness change + event has happened will return an ENODATA error. + +What: /sys/class/leds//trigger +Date: March 2006 +KernelVersion: 2.6.17 +Contact: Richard Purdie +Description: + Set the trigger for this LED. A trigger is a kernel based source + of LED events. + + You can change triggers in a similar manner to the way an IO + scheduler is chosen. Trigger specific parameters can appear in + /sys/class/leds/ once a given trigger is selected. For + their documentation see `sysfs-class-led-trigger-*`. + +What: /sys/class/leds//inverted +Date: January 2011 +KernelVersion: 2.6.38 +Contact: Richard Purdie +Description: + Invert the LED on/off state. This parameter is specific to + gpio and backlight triggers. In case of the backlight trigger, + it is useful when driving a LED which is intended to indicate + a device in a standby like state. diff --git a/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 b/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 new file mode 100644 index 000000000..e38a835d0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 @@ -0,0 +1,73 @@ +What: /sys/class/leds//als_channel +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the ALS output channel to use as input in + ALS-current-control mode (1, 2), where: + + == ============ + 1 out_current1 + 2 out_current2 + == ============ + +What: /sys/class/leds//als_en +Date: May 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Enable ALS-current-control mode (0, 1). + +What: /sys/class/leds//falltime +What: /sys/class/leds//risetime +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the pattern generator fall and rise times (0..7), where: + + == ======= + 0 2048 us + 1 262 ms + 2 524 ms + 3 1.049 s + 4 2.097 s + 5 4.194 s + 6 8.389 s + 7 16.78 s + == ======= + +What: /sys/class/leds//id +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Get the id of this led (0..3). + +What: /sys/class/leds//linear +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the brightness-mapping mode (0, 1), where: + + == ================ + 0 exponential mode + 1 linear mode + == ================ + +What: /sys/class/leds//pwm +Date: April 2012 +KernelVersion: 3.5 +Contact: Johan Hovold +Description: + Set the PWM-input control mask (5 bits), where: + + ===== =========================== + bit 5 PWM-input enabled in Zone 4 + bit 4 PWM-input enabled in Zone 3 + bit 3 PWM-input enabled in Zone 2 + bit 2 PWM-input enabled in Zone 1 + bit 1 PWM-input enabled in Zone 0 + bit 0 PWM-input enabled + ===== =========================== diff --git a/Documentation/ABI/testing/sysfs-class-led-driver-turris-omnia b/Documentation/ABI/testing/sysfs-class-led-driver-turris-omnia new file mode 100644 index 000000000..c4d46970c --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-driver-turris-omnia @@ -0,0 +1,14 @@ +What: /sys/class/leds//device/brightness +Date: July 2020 +KernelVersion: 5.9 +Contact: Marek Behún +Description: (RW) On the front panel of the Turris Omnia router there is also + a button which can be used to control the intensity of all the + LEDs at once, so that if they are too bright, user can dim them. + + The microcontroller cycles between 8 levels of this global + brightness (from 100% to 0%), but this setting can have any + integer value between 0 and 100. It is therefore convenient to be + able to change this setting from software. + + Format: %i diff --git a/Documentation/ABI/testing/sysfs-class-led-flash b/Documentation/ABI/testing/sysfs-class-led-flash new file mode 100644 index 000000000..11e5677c3 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-flash @@ -0,0 +1,89 @@ +What: /sys/class/leds//flash_brightness +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read/write + Set the brightness of this LED in the flash strobe mode, in + microamperes. The file is created only for the flash LED devices + that support setting flash brightness. + + The value is between 0 and + /sys/class/leds//max_flash_brightness. + +What: /sys/class/leds//max_flash_brightness +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read only + Maximum brightness level for this LED in the flash strobe mode, + in microamperes. + +What: /sys/class/leds//flash_timeout +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read/write + Hardware timeout for flash, in microseconds. The flash strobe + is stopped after this period of time has passed from the start + of the strobe. The file is created only for the flash LED + devices that support setting flash timeout. + +What: /sys/class/leds//max_flash_timeout +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read only + Maximum flash timeout for this LED, in microseconds. + +What: /sys/class/leds//flash_strobe +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read/write + Flash strobe state. When written with 1 it triggers flash strobe + and when written with 0 it turns the flash off. + + On read 1 means that flash is currently strobing and 0 means + that flash is off. + +What: /sys/class/leds//flash_fault +Date: March 2015 +KernelVersion: 4.0 +Contact: Jacek Anaszewski +Description: read only + Space separated list of flash faults that may have occurred. + Flash faults are re-read after strobing the flash. Possible + flash faults: + + * led-over-voltage + flash controller voltage to the flash LED + has exceeded the limit specific to the flash controller + * flash-timeout-exceeded + the flash strobe was still on when + the timeout set by the user has expired; not all flash + controllers may set this in all such conditions + * controller-over-temperature + the flash controller has + overheated + * controller-short-circuit + the short circuit protection + of the flash controller has been triggered + * led-power-supply-over-current + current in the LED power + supply has exceeded the limit specific to the flash + controller + * indicator-led-fault + the flash controller has detected + a short or open circuit condition on the indicator LED + * led-under-voltage + flash controller voltage to the flash + LED has been below the minimum limit specific to + the flash + * controller-under-voltage + the input voltage of the flash + controller is below the limit under which strobing the + flash at full current will not be possible; + the condition persists until this flag is no longer set + * led-over-temperature + the temperature of the LED has exceeded + its allowed upper limit diff --git a/Documentation/ABI/testing/sysfs-class-led-multicolor b/Documentation/ABI/testing/sysfs-class-led-multicolor new file mode 100644 index 000000000..16fc827b1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-multicolor @@ -0,0 +1,24 @@ + +What: /sys/class/leds//multi_index +Date: March 2020 +KernelVersion: 5.9 +Contact: Dan Murphy +Description: read + The multi_index array, when read, will output the LED colors + as an array of strings as they are indexed in the + multi_intensity file. + + For additional details please refer to + Documentation/leds/leds-class-multicolor.rst. + +What: /sys/class/leds//multi_intensity +Date: March 2020 +KernelVersion: 5.9 +Contact: Dan Murphy +Description: read/write + This file contains array of integers. Order of components is + described by the multi_index array. The maximum intensity should + not exceed /sys/class/leds//max_brightness. + + For additional details please refer to + Documentation/leds/leds-class-multicolor.rst. diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-netdev b/Documentation/ABI/testing/sysfs-class-led-trigger-netdev new file mode 100644 index 000000000..646540950 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-netdev @@ -0,0 +1,52 @@ +What: /sys/class/leds//device_name +Date: Dec 2017 +KernelVersion: 4.16 +Contact: linux-leds@vger.kernel.org +Description: + Specifies the network device name to monitor. + +What: /sys/class/leds//interval +Date: Dec 2017 +KernelVersion: 4.16 +Contact: linux-leds@vger.kernel.org +Description: + Specifies the duration of the LED blink in milliseconds. + Defaults to 50 ms. + +What: /sys/class/leds//link +Date: Dec 2017 +KernelVersion: 4.16 +Contact: linux-leds@vger.kernel.org +Description: + Signal the link state of the named network device. + + If set to 0 (default), the LED's normal state is off. + + If set to 1, the LED's normal state reflects the link state + of the named network device. + Setting this value also immediately changes the LED state. + + +What: /sys/class/leds//tx +Date: Dec 2017 +KernelVersion: 4.16 +Contact: linux-leds@vger.kernel.org +Description: + Signal transmission of data on the named network device. + + If set to 0 (default), the LED will not blink on transmission. + + If set to 1, the LED will blink for the milliseconds specified + in interval to signal transmission. + +What: /sys/class/leds//rx +Date: Dec 2017 +KernelVersion: 4.16 +Contact: linux-leds@vger.kernel.org +Description: + Signal reception of data on the named network device. + + If set to 0 (default), the LED will not blink on reception. + + If set to 1, the LED will blink for the milliseconds specified + in interval to signal reception. diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-oneshot b/Documentation/ABI/testing/sysfs-class-led-trigger-oneshot new file mode 100644 index 000000000..378a3a4df --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-oneshot @@ -0,0 +1,36 @@ +What: /sys/class/leds//delay_on +Date: Jun 2012 +KernelVersion: 3.6 +Contact: linux-leds@vger.kernel.org +Description: + Specifies for how many milliseconds the LED has to stay at + LED_FULL brightness after it has been armed. + Defaults to 100 ms. + +What: /sys/class/leds//delay_off +Date: Jun 2012 +KernelVersion: 3.6 +Contact: linux-leds@vger.kernel.org +Description: + Specifies for how many milliseconds the LED has to stay at + LED_OFF brightness after it has been armed. + Defaults to 100 ms. + +What: /sys/class/leds//invert +Date: Jun 2012 +KernelVersion: 3.6 +Contact: linux-leds@vger.kernel.org +Description: + Reverse the blink logic. If set to 0 (default) blink on for + delay_on ms, then blink off for delay_off ms, leaving the LED + normally off. If set to 1, blink off for delay_off ms, then + blink on for delay_on ms, leaving the LED normally on. + Setting this value also immediately changes the LED state. + +What: /sys/class/leds//shot +Date: Jun 2012 +KernelVersion: 3.6 +Contact: linux-leds@vger.kernel.org +Description: + Write any non-empty string to signal an events, this starts a + blink sequence if not already running. diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern new file mode 100644 index 000000000..8c57d2780 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern @@ -0,0 +1,40 @@ +What: /sys/class/leds//pattern +Date: September 2018 +KernelVersion: 4.20 +Description: + Specify a software pattern for the LED, that supports altering + the brightness for the specified duration with one software + timer. It can do gradual dimming and step change of brightness. + + The pattern is given by a series of tuples, of brightness and + duration (ms). + + The exact format is described in: + Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt + +What: /sys/class/leds//hw_pattern +Date: September 2018 +KernelVersion: 4.20 +Description: + Specify a hardware pattern for the LED, for LED hardware that + supports autonomously controlling brightness over time, according + to some preprogrammed hardware patterns. It deactivates any active + software pattern. + + Since different LED hardware can have different semantics of + hardware patterns, each driver is expected to provide its own + description for the hardware patterns in their documentation + file at Documentation/leds/. + +What: /sys/class/leds//repeat +Date: September 2018 +KernelVersion: 4.20 +Description: + Specify a pattern repeat number. -1 means repeat indefinitely, + other negative numbers and number 0 are invalid. + + This file will always return the originally written repeat + number. + + It should be noticed that some leds, like EL15203000 may + only support indefinitely patterns, so they always store -1. diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-tty b/Documentation/ABI/testing/sysfs-class-led-trigger-tty new file mode 100644 index 000000000..2bf6b24e7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-tty @@ -0,0 +1,6 @@ +What: /sys/class/leds//ttyname +Date: Dec 2020 +KernelVersion: 5.10 +Contact: linux-leds@vger.kernel.org +Description: + Specifies the tty device name of the triggering tty diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-usbport b/Documentation/ABI/testing/sysfs-class-led-trigger-usbport new file mode 100644 index 000000000..eb81152b8 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-led-trigger-usbport @@ -0,0 +1,13 @@ +What: /sys/class/leds//ports/ +Date: September 2016 +KernelVersion: 4.9 +Contact: linux-leds@vger.kernel.org + linux-usb@vger.kernel.org +Description: + Every dir entry represents a single USB port that can be + selected for the USB port trigger. Selecting ports makes trigger + observing them for any connected devices and lighting on LED if + there are any. + + Echoing "1" value selects USB port. Echoing "0" unselects it. + Current state can be also read. diff --git a/Documentation/ABI/testing/sysfs-class-leds-gt683r b/Documentation/ABI/testing/sysfs-class-leds-gt683r new file mode 100644 index 000000000..b57ffb26e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-leds-gt683r @@ -0,0 +1,18 @@ +What: /sys/class/leds//gt683r/mode +Date: Jun 2014 +KernelVersion: 3.17 +Contact: Janne Kanniainen +Description: + Set the mode of LEDs. You should notice that changing the mode + of one LED will update the mode of its two sibling devices as + well. Possible values are: + + == ========= + 0 normal + 1 audio + 2 breathing + == ========= + + Normal: LEDs are fully on when enabled + Audio: LEDs brightness depends on sound level + Breathing: LEDs brightness varies at human breathing rate diff --git a/Documentation/ABI/testing/sysfs-class-mei b/Documentation/ABI/testing/sysfs-class-mei new file mode 100644 index 000000000..1db36ddf8 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-mei @@ -0,0 +1,105 @@ +What: /sys/class/mei/ +Date: May 2014 +KernelVersion: 3.17 +Contact: Tomas Winkler +Description: + The mei/ class sub-directory belongs to mei device class + + +What: /sys/class/mei/mei/ +Date: May 2014 +KernelVersion: 3.17 +Contact: Tomas Winkler +Description: + The /sys/class/mei/meiN directory is created for + each probed mei device + +What: /sys/class/mei/mei/fw_status +Date: Nov 2014 +KernelVersion: 3.19 +Contact: Tomas Winkler +Description: Display fw status registers content + + The ME FW writes its status information into fw status + registers for BIOS and OS to monitor fw health. + + The register contains running state, power management + state, error codes, and others. The way the registers + are decoded depends on PCH or SoC generation. + Also number of registers varies between 1 and 6 + depending on generation. + +What: /sys/class/mei/mei/hbm_ver +Date: Aug 2016 +KernelVersion: 4.9 +Contact: Tomas Winkler +Description: Display the negotiated HBM protocol version. + + The HBM protocol version negotiated + between the driver and the device. + +What: /sys/class/mei/mei/hbm_ver_drv +Date: Aug 2016 +KernelVersion: 4.9 +Contact: Tomas Winkler +Description: Display the driver HBM protocol version. + + The HBM protocol version supported by the driver. + +What: /sys/class/mei/mei/tx_queue_limit +Date: Jan 2018 +KernelVersion: 4.16 +Contact: Tomas Winkler +Description: Configure tx queue limit + + Set maximal number of pending writes + per opened session. + +What: /sys/class/mei/mei/fw_ver +Date: May 2018 +KernelVersion: 4.18 +Contact: Tomas Winkler +Description: Display the ME firmware version. + + The version of the platform ME firmware is in format: + :.... + There can be up to three such blocks for different + FW components. + +What: /sys/class/mei/mei/dev_state +Date: Mar 2019 +KernelVersion: 5.1 +Contact: Tomas Winkler +Description: Display the ME device state. + + The device state can have following values: + INITIALIZING + INIT_CLIENTS + ENABLED + RESETTING + DISABLED + POWER_DOWN + POWER_UP + +What: /sys/class/mei/mei/trc +Date: Nov 2019 +KernelVersion: 5.5 +Contact: Tomas Winkler +Description: Display trc status register content + + The ME FW writes Glitch Detection HW (TRC) + status information into trc status register + for BIOS and OS to monitor fw health. + +What: /sys/class/mei/mei/kind +Date: Jul 2020 +KernelVersion: 5.8 +Contact: Tomas Winkler +Description: Display kind of the device + + Generic devices are marked as "mei" + while special purpose have their own + names. + Available options: + - mei: generic mei device. + - itouch: itouch (ipts) mei device. diff --git a/Documentation/ABI/testing/sysfs-class-mic b/Documentation/ABI/testing/sysfs-class-mic new file mode 100644 index 000000000..5e5f36d10 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-mic @@ -0,0 +1,178 @@ +What: /sys/class/mic/ +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + The mic class directory belongs to Intel MIC devices and + provides information per MIC device. An Intel MIC device is a + PCIe form factor add-in Coprocessor card based on the Intel Many + Integrated Core (MIC) architecture that runs a Linux OS. + +What: /sys/class/mic/mic +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + The directories /sys/class/mic/mic0, /sys/class/mic/mic1 etc., + represent MIC devices (0,1,..etc). Each directory has + information specific to that MIC device. + +What: /sys/class/mic/mic/family +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + Provides information about the Coprocessor family for an Intel + MIC device. For example - "x100" + +What: /sys/class/mic/mic/stepping +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + Provides information about the silicon stepping for an Intel + MIC device. For example - "A0" or "B0" + +What: /sys/class/mic/mic/state +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + When read, this entry provides the current state of an Intel + MIC device in the context of the card OS. Possible values that + will be read are: + + + =============== =============================================== + "ready" The MIC device is ready to boot the card OS. + On reading this entry after an OSPM resume, + a "boot" has to be written to this entry if + the card was previously shutdown during OSPM + suspend. + "booting" The MIC device has initiated booting a card OS. + "online" The MIC device has completed boot and is online + "shutting_down" The card OS is shutting down. + "resetting" A reset has been initiated for the MIC device + "reset_failed" The MIC device has failed to reset. + =============== =============================================== + + When written, this sysfs entry triggers different state change + operations depending upon the current state of the card OS. + Acceptable values are: + + + ========== =================================================== + "boot" Boot the card OS image specified by the combination + of firmware, ramdisk, cmdline and bootmode + sysfs entries. + "reset" Initiates device reset. + "shutdown" Initiates card OS shutdown. + ========== =================================================== + +What: /sys/class/mic/mic/shutdown_status +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + An Intel MIC device runs a Linux OS during its operation. This + OS can shutdown because of various reasons. When read, this + entry provides the status on why the card OS was shutdown. + Possible values are: + + ========== =================================================== + "nop" shutdown status is not applicable, when the card OS + is "online" + "crashed" Shutdown because of a HW or SW crash. + "halted" Shutdown because of a halt command. + "poweroff" Shutdown because of a poweroff command. + "restart" Shutdown because of a restart command. + ========== =================================================== + +What: /sys/class/mic/mic/cmdline +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + An Intel MIC device runs a Linux OS during its operation. Before + booting this card OS, it is possible to pass kernel command line + options to configure various features in it, similar to + self-bootable machines. When read, this entry provides + information about the current kernel command line options set to + boot the card OS. This entry can be written to change the + existing kernel command line options. Typically, the user would + want to read the current command line options, append new ones + or modify existing ones and then write the whole kernel command + line back to this entry. + +What: /sys/class/mic/mic/firmware +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + When read, this sysfs entry provides the path name under + /lib/firmware/ where the firmware image to be booted on the + card can be found. The entry can be written to change the + firmware image location under /lib/firmware/. + +What: /sys/class/mic/mic/ramdisk +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + When read, this sysfs entry provides the path name under + /lib/firmware/ where the ramdisk image to be used during card + OS boot can be found. The entry can be written to change + the ramdisk image location under /lib/firmware/. + +What: /sys/class/mic/mic/bootmode +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + When read, this sysfs entry provides the current bootmode for + the card. This sysfs entry can be written with the following + valid strings: + a) linux - Boot a Linux image. + b) flash - Boot an image for flash updates. + +What: /sys/class/mic/mic/log_buf_addr +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + An Intel MIC device runs a Linux OS during its operation. For + debugging purpose and early kernel boot messages, the user can + access the card OS log buffer via debugfs. When read, this entry + provides the kernel virtual address of the buffer where the card + OS log buffer can be read. This entry is written by the host + configuration daemon to set the log buffer address. The correct + log buffer address to be written can be found in the System.map + file of the card OS. + +What: /sys/class/mic/mic/log_buf_len +Date: October 2013 +KernelVersion: 3.13 +Contact: Sudeep Dutt +Description: + An Intel MIC device runs a Linux OS during its operation. For + debugging purpose and early kernel boot messages, the user can + access the card OS log buffer via debugfs. When read, this entry + provides the kernel virtual address where the card OS log buffer + length can be read. This entry is written by host configuration + daemon to set the log buffer length address. The correct log + buffer length address to be written can be found in the + System.map file of the card OS. + +What: /sys/class/mic/mic/heartbeat_enable +Date: March 2015 +KernelVersion: 4.4 +Contact: Ashutosh Dixit +Description: + The MIC drivers detect and inform user space about card crashes + via a heartbeat mechanism (see the description of + shutdown_status above). User space can turn off this + notification by setting heartbeat_enable to 0 and enable it by + setting this entry to 1. If this notification is disabled it is + the responsibility of user space to detect card crashes via + alternative means such as a network ping. This setting is + enabled by default. diff --git a/Documentation/ABI/testing/sysfs-class-mtd b/Documentation/ABI/testing/sysfs-class-mtd new file mode 100644 index 000000000..3bc7c0a95 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-mtd @@ -0,0 +1,242 @@ +What: /sys/class/mtd/ +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + The mtd/ class subdirectory belongs to the MTD subsystem + (MTD core). + +What: /sys/class/mtd/mtdX/ +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + The /sys/class/mtd/mtd{0,1,2,3,...} directories correspond + to each /dev/mtdX character device. These may represent + physical/simulated flash devices, partitions on a flash + device, or concatenated flash devices. + +What: /sys/class/mtd/mtdXro/ +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + These directories provide the corresponding read-only device + nodes for /sys/class/mtd/mtdX/ . + +What: /sys/class/mtd/mtdX/dev +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + Major and minor numbers of the character device corresponding + to this MTD device (in : format). This is the + read-write device so will be even. + +What: /sys/class/mtd/mtdXro/dev +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + Major and minor numbers of the character device corresponding + to the read-only variant of thie MTD device (in + : format). In this case will be odd. + +What: /sys/class/mtd/mtdX/erasesize +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + "Major" erase size for the device. If numeraseregions is + zero, this is the eraseblock size for the entire device. + Otherwise, the MEMGETREGIONCOUNT/MEMGETREGIONINFO ioctls + can be used to determine the actual eraseblock layout. + +What: /sys/class/mtd/mtdX/flags +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + A hexadecimal value representing the device flags, ORed + together: + + 0x0400: MTD_WRITEABLE - device is writable + 0x0800: MTD_BIT_WRITEABLE - single bits can be flipped + 0x1000: MTD_NO_ERASE - no erase necessary + 0x2000: MTD_POWERUP_LOCK - always locked after reset + +What: /sys/class/mtd/mtdX/name +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + A human-readable ASCII name for the device or partition. + This will match the name in /proc/mtd . + +What: /sys/class/mtd/mtdX/numeraseregions +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + For devices that have variable eraseblock sizes, this + provides the total number of erase regions. Otherwise, + it will read back as zero. + +What: /sys/class/mtd/mtdX/oobsize +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + Number of OOB bytes per page. + +What: /sys/class/mtd/mtdX/size +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + Total size of the device/partition, in bytes. + +What: /sys/class/mtd/mtdX/type +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + One of the following ASCII strings, representing the device + type: + + absent, ram, rom, nor, nand, mlc-nand, dataflash, ubi, unknown + +What: /sys/class/mtd/mtdX/writesize +Date: April 2009 +KernelVersion: 2.6.29 +Contact: linux-mtd@lists.infradead.org +Description: + Minimal writable flash unit size. This will always be + a positive integer. + + In the case of NOR flash it is 1 (even though individual + bits can be cleared). + + In the case of NAND flash it is one NAND page (or a + half page, or a quarter page). + + In the case of ECC NOR, it is the ECC block size. + +What: /sys/class/mtd/mtdX/ecc_strength +Date: April 2012 +KernelVersion: 3.4 +Contact: linux-mtd@lists.infradead.org +Description: + Maximum number of bit errors that the device is capable of + correcting within each region covering an ECC step (see + ecc_step_size). This will always be a non-negative integer. + + In the case of devices lacking any ECC capability, it is 0. + +What: /sys/class/mtd/mtdX/bitflip_threshold +Date: April 2012 +KernelVersion: 3.4 +Contact: linux-mtd@lists.infradead.org +Description: + This allows the user to examine and adjust the criteria by which + mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the + maximum number of bit errors that were corrected on any single + region comprising an ecc step (as reported by the driver) equals + or exceeds this value, -EUCLEAN is returned. Otherwise, absent + an error, 0 is returned. Higher layers (e.g., UBI) use this + return code as an indication that an erase block may be + degrading and should be scrutinized as a candidate for being + marked as bad. + + The initial value may be specified by the flash device driver. + If not, then the default value is ecc_strength. + + The introduction of this feature brings a subtle change to the + meaning of the -EUCLEAN return code. Previously, it was + interpreted to mean simply "one or more bit errors were + corrected". Its new interpretation can be phrased as "a + dangerously high number of bit errors were corrected on one or + more regions comprising an ecc step". The precise definition of + "dangerously high" can be adjusted by the user with + bitflip_threshold. Users are discouraged from doing this, + however, unless they know what they are doing and have intimate + knowledge of the properties of their device. Broadly speaking, + bitflip_threshold should be low enough to detect genuine erase + block degradation, but high enough to avoid the consequences of + a persistent return value of -EUCLEAN on devices where sticky + bitflips occur. Note that if bitflip_threshold exceeds + ecc_strength, -EUCLEAN is never returned by the read operations. + Conversely, if bitflip_threshold is zero, -EUCLEAN is always + returned, absent a hard error. + + This is generally applicable only to NAND flash devices with ECC + capability. It is ignored on devices lacking ECC capability; + i.e., devices for which ecc_strength is zero. + +What: /sys/class/mtd/mtdX/ecc_step_size +Date: May 2013 +KernelVersion: 3.10 +Contact: linux-mtd@lists.infradead.org +Description: + The size of a single region covered by ECC, known as the ECC + step. Devices may have several equally sized ECC steps within + each writesize region. + + It will always be a non-negative integer. In the case of + devices lacking any ECC capability, it is 0. + +What: /sys/class/mtd/mtdX/ecc_failures +Date: June 2014 +KernelVersion: 3.17 +Contact: linux-mtd@lists.infradead.org +Description: + The number of failures reported by this device's ECC. Typically, + these failures are associated with failed read operations. + + It will always be a non-negative integer. In the case of + devices lacking any ECC capability, it is 0. + +What: /sys/class/mtd/mtdX/corrected_bits +Date: June 2014 +KernelVersion: 3.17 +Contact: linux-mtd@lists.infradead.org +Description: + The number of bits that have been corrected by means of the + device's ECC. + + It will always be a non-negative integer. In the case of + devices lacking any ECC capability, it is 0. + +What: /sys/class/mtd/mtdX/bad_blocks +Date: June 2014 +KernelVersion: 3.17 +Contact: linux-mtd@lists.infradead.org +Description: + The number of blocks marked as bad, if any, in this partition. + +What: /sys/class/mtd/mtdX/bbt_blocks +Date: June 2014 +KernelVersion: 3.17 +Contact: linux-mtd@lists.infradead.org +Description: + The number of blocks that are marked as reserved, if any, in + this partition. These are typically used to store the in-flash + bad block table (BBT). + +What: /sys/class/mtd/mtdX/offset +Date: March 2015 +KernelVersion: 4.1 +Contact: linux-mtd@lists.infradead.org +Description: + For a partition, the offset of that partition from the start + of the parent (another partition or a flash device) in bytes. + This attribute is absent on flash devices, so it can be used + to distinguish them from partitions. + +What: /sys/class/mtd/mtdX/oobavail +Date: April 2018 +KernelVersion: 4.16 +Contact: linux-mtd@lists.infradead.org +Description: + Number of bytes available for a client to place data into + the out of band area. diff --git a/Documentation/ABI/testing/sysfs-class-mux b/Documentation/ABI/testing/sysfs-class-mux new file mode 100644 index 000000000..c58b7b6e1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-mux @@ -0,0 +1,16 @@ +What: /sys/class/mux/ +Date: April 2017 +KernelVersion: 4.13 +Contact: Peter Rosin +Description: + The mux/ class sub-directory belongs to the Generic MUX + Framework and provides a sysfs interface for using MUX + controllers. + +What: /sys/class/mux/muxchip/ +Date: April 2017 +KernelVersion: 4.13 +Contact: Peter Rosin +Description: + A /sys/class/mux/muxchipN directory is created for each + probed MUX chip where N is a simple enumeration. diff --git a/Documentation/ABI/testing/sysfs-class-net b/Documentation/ABI/testing/sysfs-class-net new file mode 100644 index 000000000..1419103d1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net @@ -0,0 +1,354 @@ +What: /sys/class/net//name_assign_type +Date: July 2014 +KernelVersion: 3.17 +Contact: netdev@vger.kernel.org +Description: + Indicates the name assignment type. Possible values are: + + == ========================================================== + 1 enumerated by the kernel, possibly in an unpredictable way + 2 predictably named by the kernel + 3 named by userspace + 4 renamed + == ========================================================== + +What: /sys/class/net//addr_assign_type +Date: July 2010 +KernelVersion: 3.2 +Contact: netdev@vger.kernel.org +Description: + Indicates the address assignment type. Possible values are: + + == ============================= + 0 permanent address + 1 randomly generated + 2 stolen from another device + 3 set using dev_set_mac_address + == ============================= + +What: /sys/class/net//addr_len +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the hardware address size in bytes. + Values vary based on the lower-level protocol used by the + interface (Ethernet, FDDI, ATM, IEEE 802.15.4...). See + include/uapi/linux/if_*.h for actual values. + +What: /sys/class/net//address +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Hardware address currently assigned to this interface. + Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC + address. + +What: /sys/class/net//bridge/group_fwd_mask +Date: January 2012 +KernelVersion: 3.2 +Contact: netdev@vger.kernel.org +Description: + Bitmask to allow forwarding of link local frames with address + 01-80-C2-00-00-0X on a bridge device. Only values that set bits + not matching BR_GROUPFWD_RESTRICTED in net/bridge/br_private.h + allowed. + Default value 0 does not forward any link local frames. + + Restricted bits: + + == ======================================================== + 0 01-80-C2-00-00-00 Bridge Group Address used for STP + 1 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE + 2 01-80-C2-00-00-02 (Link Aggregation) 802.3ad + == ======================================================== + + Any values not setting these bits can be used. Take special + care when forwarding control frames e.g. 802.1X-PAE or LLDP. + +What: /sys/class/net//broadcast +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Hardware broadcast address for this interface. Format is a + string, e.g: ff:ff:ff:ff:ff:ff for an Ethernet broadcast MAC + address. + +What: /sys/class/net//carrier +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the current physical link state of the interface. + Posssible values are: + + == ===================== + 0 physical link is down + 1 physical link is up + == ===================== + + Note: some special devices, e.g: bonding and team drivers will + allow this attribute to be written to force a link state for + operating correctly and designating another fallback interface. + +What: /sys/class/net//dev_id +Date: April 2008 +KernelVersion: 2.6.26 +Contact: netdev@vger.kernel.org +Description: + Indicates the device unique identifier. Format is an hexadecimal + value. This is used to disambiguate interfaces which might be + stacked (e.g: VLAN interfaces) but still have the same MAC + address as their parent device. + +What: /sys/class/net//dev_port +Date: February 2014 +KernelVersion: 3.15 +Contact: netdev@vger.kernel.org +Description: + Indicates the port number of this network device, formatted + as a decimal value. Some NICs have multiple independent ports + on the same PCI bus, device and function. This attribute allows + userspace to distinguish the respective interfaces. + + Note: some device drivers started to use 'dev_id' for this + purpose since long before 3.15 and have not adopted the new + attribute ever since. To query the port number, some tools look + exclusively at 'dev_port', while others only consult 'dev_id'. + If a network device has multiple client adapter ports as + described in the previous paragraph and does not set this + attribute to its port number, it's a kernel bug. + +What: /sys/class/net//dormant +Date: March 2006 +KernelVersion: 2.6.17 +Contact: netdev@vger.kernel.org +Description: + Indicates whether the interface is in dormant state. Possible + values are: + 0: interface is not dormant + 1: interface is dormant + + This attribute can be used by supplicant software to signal that + the device is not usable unless some supplicant-based + authentication is performed (e.g: 802.1x). 'link_mode' attribute + will also reflect the dormant state. + +What: /sys/class/net//testing +Date: April 2002 +KernelVersion: 5.8 +Contact: netdev@vger.kernel.org +Description: + Indicates whether the interface is under test. Possible + values are: + + == ============================= + 0 interface is not being tested + 1 interface is being tested + == ============================= + + When an interface is under test, it cannot be expected + to pass packets as normal. + +What: /sys/class/net//duplex +Date: October 2009 +KernelVersion: 2.6.33 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface latest or current duplex value. Possible + values are: + + ==== =========== + half half duplex + full full duplex + ==== =========== + + Note: This attribute is only valid for interfaces that implement + the ethtool get_link_ksettings method (mostly Ethernet). + +What: /sys/class/net//flags +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface flags as a bitmask in hexadecimal. See + include/uapi/linux/if.h for a list of all possible values and + the flags semantics. + +What: /sys/class/net//ifalias +Date: September 2008 +KernelVersion: 2.6.28 +Contact: netdev@vger.kernel.org +Description: + Indicates/stores an interface alias name as a string. This can + be used for system management purposes. + +What: /sys/class/net//ifindex +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the system-wide interface unique index identifier as a + decimal number. This attribute is used for mapping an interface + identifier to an interface name. It is used throughout the + networking stack for specifying the interface specific + requests/events. + +What: /sys/class/net//iflink +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the system-wide interface unique index identifier a + the interface is linked to. Format is decimal. This attribute is + used to resolve interfaces chaining, linking and stacking. + Physical interfaces have the same 'ifindex' and 'iflink' values. + +What: /sys/class/net//link_mode +Date: March 2006 +KernelVersion: 2.6.17 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface link mode, as a decimal number. This + attribute should be used in conjunction with 'dormant' attribute + to determine the interface usability. Possible values: + + == ================= + 0 default link mode + 1 dormant link mode + == ================= + +What: /sys/class/net//mtu +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface currently configured MTU value, in + bytes, and in decimal format. Specific values depends on the + lower-level interface protocol used. Ethernet devices will show + a 'mtu' attribute value of 1500 unless changed. + +What: /sys/class/net//netdev_group +Date: January 2011 +KernelVersion: 2.6.39 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface network device group, as a decimal + integer. Default value is 0 which corresponds to the initial + network devices group. The group can be changed to affect + routing decisions (see: net/ipv4/fib_rules and + net/ipv6/fib6_rules.c). + +What: /sys/class/net//operstate +Date: March 2006 +KernelVersion: 2.6.17 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface RFC2863 operational state as a string. + + Possible values are: + + "unknown", "notpresent", "down", "lowerlayerdown", "testing", + "dormant", "up". + +What: /sys/class/net//phys_port_id +Date: July 2013 +KernelVersion: 3.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface unique physical port identifier within + the NIC, as a string. + +What: /sys/class/net//phys_port_name +Date: March 2015 +KernelVersion: 4.0 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface physical port name within the NIC, + as a string. + +What: /sys/class/net//speed +Date: October 2009 +KernelVersion: 2.6.33 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface latest or current speed value. Value is + an integer representing the link speed in Mbits/sec. + + Note: this attribute is only valid for interfaces that implement + the ethtool get_link_ksettings method (mostly Ethernet). + +What: /sys/class/net//tx_queue_len +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface transmit queue len in number of packets, + as an integer value. Value depend on the type of interface, + Ethernet network adapters have a default value of 1000 unless + configured otherwise + +What: /sys/class/net//type +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the interface protocol type as a decimal value. See + include/uapi/linux/if_arp.h for all possible values. + +What: /sys/class/net//phys_switch_id +Date: November 2014 +KernelVersion: 3.19 +Contact: netdev@vger.kernel.org +Description: + Indicates the unique physical switch identifier of a switch this + port belongs to, as a string. + +What: /sys/class/net//phydev +Date: May 2017 +KernelVersion: 4.13 +Contact: netdev@vger.kernel.org +Description: + Symbolic link to the PHY device this network device is attached + to. + +What: /sys/class/net//carrier_changes +Date: Mar 2014 +KernelVersion: 3.15 +Contact: netdev@vger.kernel.org +Description: + 32-bit unsigned integer counting the number of times the link has + seen a change from UP to DOWN and vice versa + +What: /sys/class/net//carrier_up_count +Date: Jan 2018 +KernelVersion: 4.16 +Contact: netdev@vger.kernel.org +Description: + 32-bit unsigned integer counting the number of times the link has + been up + +What: /sys/class/net//carrier_down_count +Date: Jan 2018 +KernelVersion: 4.16 +Contact: netdev@vger.kernel.org +Description: + 32-bit unsigned integer counting the number of times the link has + been down + +What: /sys/class/net//threaded +Date: Jan 2021 +KernelVersion: 5.12 +Contact: netdev@vger.kernel.org +Description: + Boolean value to control the threaded mode per device. User could + set this value to enable/disable threaded mode for all napi + belonging to this device, without the need to do device up/down. + + Possible values: + == ================================== + 0 threaded mode disabled for this dev + 1 threaded mode enabled for this dev + == ================================== diff --git a/Documentation/ABI/testing/sysfs-class-net-cdc_ncm b/Documentation/ABI/testing/sysfs-class-net-cdc_ncm new file mode 100644 index 000000000..06416d0e1 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-cdc_ncm @@ -0,0 +1,168 @@ +What: /sys/class/net//cdc_ncm/min_tx_pkt +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + The driver will pad NCM Transfer Blocks (NTBs) longer + than this to tx_max, allowing the device to receive + tx_max sized frames with no terminating short + packet. NTBs shorter than this limit are transmitted + as-is, without any padding, and are terminated with a + short USB packet. + + Padding to tx_max allows the driver to transmit NTBs + back-to-back without any interleaving short USB + packets. This reduces the number of short packet + interrupts in the device, and represents a tradeoff + between USB bus bandwidth and device DMA optimization. + + Set to 0 to pad all frames. Set greater than tx_max to + disable all padding. + +What: /sys/class/net//cdc_ncm/ndp_to_end +Date: Dec 2015 +KernelVersion: 4.5 +Contact: Bjørn Mork +Description: + Boolean attribute showing the status of the "NDP to + end" quirk. Defaults to 'N', except for devices + already known to need it enabled. + + The "NDP to end" quirk makes the driver place the NDP + (the packet index table) after the payload. The NCM + specification does not mandate this, but some devices + are known to be more restrictive. Write 'Y' to this + attribute for temporary testing of a suspect device + failing to work with the default driver settings. + + A device entry should be added to the driver if this + quirk is found to be required. + +What: /sys/class/net//cdc_ncm/rx_max +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + The maximum NTB size for RX. Cannot exceed the + maximum value supported by the device. Must allow at + least one max sized datagram plus headers. + + The actual limits are device dependent. See + dwNtbInMaxSize. + + Note: Some devices will silently ignore changes to + this value, resulting in oversized NTBs and + corresponding framing errors. + +What: /sys/class/net//cdc_ncm/tx_max +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + The maximum NTB size for TX. Cannot exceed the + maximum value supported by the device. Must allow at + least one max sized datagram plus headers. + + The actual limits are device dependent. See + dwNtbOutMaxSize. + +What: /sys/class/net//cdc_ncm/tx_timer_usecs +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + Datagram aggregation timeout in µs. The driver will + wait up to 3 times this timeout for more datagrams to + aggregate before transmitting an NTB frame. + + Valid range: 5 to 4000000 + + Set to 0 to disable aggregation. + +The following read-only attributes all represent fields of the +structure defined in section 6.2.1 "GetNtbParameters" of "Universal +Serial Bus Communications Class Subclass Specifications for Network +Control Model Devices" (CDC NCM), Revision 1.0 (Errata 1), November +24, 2010 from USB Implementers Forum, Inc. The descriptions are +quoted from table 6-3 of CDC NCM: "NTB Parameter Structure". + +What: /sys/class/net//cdc_ncm/bmNtbFormatsSupported +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + - Bit 0: 16-bit NTB supported (set to 1) + - Bit 1: 32-bit NTB supported + - Bits 2 – 15: reserved (reset to zero; must be ignored by host) + +What: /sys/class/net//cdc_ncm/dwNtbInMaxSize +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + IN NTB Maximum Size in bytes + +What: /sys/class/net//cdc_ncm/wNdpInDivisor +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + Divisor used for IN NTB Datagram payload alignment + +What: /sys/class/net//cdc_ncm/wNdpInPayloadRemainder +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + Remainder used to align input datagram payload within + the NTB: (Payload Offset) mod (wNdpInDivisor) = + wNdpInPayloadRemainder + +What: /sys/class/net//cdc_ncm/wNdpInAlignment +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + NDP alignment modulus for NTBs on the IN pipe. Shall + be a power of 2, and shall be at least 4. + +What: /sys/class/net//cdc_ncm/dwNtbOutMaxSize +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + OUT NTB Maximum Size + +What: /sys/class/net//cdc_ncm/wNdpOutDivisor +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + OUT NTB Datagram alignment modulus + +What: /sys/class/net//cdc_ncm/wNdpOutPayloadRemainder +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + Remainder used to align output datagram payload + offsets within the NTB: Padding, shall be transmitted + as zero by function, and ignored by host. (Payload + Offset) mod (wNdpOutDivisor) = wNdpOutPayloadRemainder + +What: /sys/class/net//cdc_ncm/wNdpOutAlignment +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + NDP alignment modulus for use in NTBs on the OUT + pipe. Shall be a power of 2, and shall be at least 4. + +What: /sys/class/net//cdc_ncm/wNtbOutMaxDatagrams +Date: May 2014 +KernelVersion: 3.16 +Contact: Bjørn Mork +Description: + Maximum number of datagrams that the host may pack + into a single OUT NTB. Zero means that the device + imposes no limit. diff --git a/Documentation/ABI/testing/sysfs-class-net-dsa b/Documentation/ABI/testing/sysfs-class-net-dsa new file mode 100644 index 000000000..e2da26b44 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-dsa @@ -0,0 +1,14 @@ +What: /sys/class/net//dsa/tagging +Date: August 2018 +KernelVersion: 4.20 +Contact: netdev@vger.kernel.org +Description: + On read, this file returns a string indicating the type of + tagging protocol used by the DSA network devices that are + attached to this master interface. + On write, this file changes the tagging protocol of the + attached DSA switches, if this operation is supported by the + driver. Changing the tagging protocol must be done with the DSA + interfaces and the master interface all administratively down. + See the "name" field of each registered struct dsa_device_ops + for a list of valid values. diff --git a/Documentation/ABI/testing/sysfs-class-net-grcan b/Documentation/ABI/testing/sysfs-class-net-grcan new file mode 100644 index 000000000..f418c92ca --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-grcan @@ -0,0 +1,35 @@ + +What: /sys/class/net//grcan/enable0 +Date: October 2012 +KernelVersion: 3.8 +Contact: Andreas Larsson +Description: + Hardware configuration of physical interface 0. This file reads + and writes the "Enable 0" bit of the configuration register. + Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP + core library documentation for details. The default value is 0 + or set by the module parameter grcan.enable0 and can be read at + /sys/module/grcan/parameters/enable0. + +What: /sys/class/net//grcan/enable1 +Date: October 2012 +KernelVersion: 3.8 +Contact: Andreas Larsson +Description: + Hardware configuration of physical interface 1. This file reads + and writes the "Enable 1" bit of the configuration register. + Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP + core library documentation for details. The default value is 0 + or set by the module parameter grcan.enable1 and can be read at + /sys/module/grcan/parameters/enable1. + +What: /sys/class/net//grcan/select +Date: October 2012 +KernelVersion: 3.8 +Contact: Andreas Larsson +Description: + Configuration of which physical interface to be used. Possible + values: 0 or 1. See the GRCAN chapter of the GRLIB IP core + library documentation for details. The default value is 0 or is + set by the module parameter grcan.select and can be read at + /sys/module/grcan/parameters/select. diff --git a/Documentation/ABI/testing/sysfs-class-net-janz-ican3 b/Documentation/ABI/testing/sysfs-class-net-janz-ican3 new file mode 100644 index 000000000..fdbc03a2b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-janz-ican3 @@ -0,0 +1,19 @@ +What: /sys/class/net//termination +Date: May 2010 +KernelVersion: 2.6.35 +Contact: Ira W. Snyder +Description: + Value representing the can bus termination + + Default: 1 (termination active) + Reading: get actual termination state + Writing: set actual termination state (0=no termination, 1=termination active) + +What: /sys/class/net//fwinfo +Date: May 2015 +KernelVersion: 3.19 +Contact: Andreas Gröger +Description: + Firmware stamp of ican3 module + Read-only: 32 byte string identification of the ICAN3 module + (known values: "JANZ-ICAN3 ICANOS 1.xx", "JANZ-ICAN3 CAL/CANopen 1.xx") diff --git a/Documentation/ABI/testing/sysfs-class-net-phydev b/Documentation/ABI/testing/sysfs-class-net-phydev new file mode 100644 index 000000000..ac722dd5e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-phydev @@ -0,0 +1,65 @@ +What: /sys/class/mdio_bus///attached_dev +Date: May 2017 +KernelVersion: 4.13 +Contact: netdev@vger.kernel.org +Description: + Symbolic link to the network device this PHY device is + attached to. + +What: /sys/class/mdio_bus///phy_has_fixups +Date: February 2014 +KernelVersion: 3.15 +Contact: netdev@vger.kernel.org +Description: + This attribute contains the boolean value whether a given PHY + device has had any "fixup" workaround running on it, encoded as + a boolean. This information is provided to help troubleshooting + PHY configurations. + +What: /sys/class/mdio_bus///phy_id +Date: November 2012 +KernelVersion: 3.8 +Contact: netdev@vger.kernel.org +Description: + This attribute contains the 32-bit PHY Identifier as reported + by the device during bus enumeration, encoded in hexadecimal. + This ID is used to match the device with the appropriate + driver. + +What: /sys/class/mdio_bus///phy_interface +Date: February 2014 +KernelVersion: 3.15 +Contact: netdev@vger.kernel.org +Description: + This attribute contains the PHY interface as configured by the + Ethernet driver during bus enumeration, encoded in string. + This interface mode is used to configure the Ethernet MAC with the + appropriate mode for its data lines to the PHY hardware. + + Possible values are: + + (not available), mii, gmii, sgmii, tbi, rev-mii, + rmii, rgmii, rgmii-id, rgmii-rxid, rgmii-txid, rtbi, smii + xgmii, moca, qsgmii, trgmii, 1000base-x, 2500base-x, rxaui, + xaui, 10gbase-kr, unknown + +What: /sys/class/mdio_bus///phy_standalone +Date: May 2019 +KernelVersion: 5.3 +Contact: netdev@vger.kernel.org +Description: + Boolean value indicating whether the PHY device is used in + standalone mode, without a net_device associated, by PHYLINK. + Attribute created only when this is the case. + +What: /sys/class/mdio_bus///phy_dev_flags +Date: March 2021 +KernelVersion: 5.13 +Contact: netdev@vger.kernel.org +Description: + 32-bit hexadecimal number representing a bit mask of the + configuration bits passed from the consumer of the PHY + (Ethernet MAC, switch, etc.) to the PHY driver. The flags are + only used internally by the kernel and their placement are + not meant to be stable across kernel versions. This is intended + for facilitating the debugging of PHY drivers. diff --git a/Documentation/ABI/testing/sysfs-class-net-qmi b/Documentation/ABI/testing/sysfs-class-net-qmi new file mode 100644 index 000000000..47e6b9732 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-qmi @@ -0,0 +1,76 @@ +What: /sys/class/net//qmi/raw_ip +Date: Dec 2015 +KernelVersion: 4.4 +Contact: Bjørn Mork +Description: + Boolean. Default: 'N' + + Set this to 'Y' to change the network device link + framing from '802.3' to 'raw-ip'. + + The netdev will change to reflect the link framing + mode. The netdev is an ordinary ethernet device in + '802.3' mode, and the driver expects to exchange + frames with an ethernet header over the USB link. The + netdev is a headerless p-t-p device in 'raw-ip' mode, + and the driver expects to echange IPv4 or IPv6 packets + without any L2 header over the USB link. + + Userspace is in full control of firmware configuration + through the delegation of the QMI protocol. Userspace + is responsible for coordination of driver and firmware + link framing mode, changing this setting to 'Y' if the + firmware is configured for 'raw-ip' mode. + +What: /sys/class/net//qmi/add_mux +Date: March 2017 +KernelVersion: 4.11 +Contact: Bjørn Mork +Description: + Unsigned integer. + + Write a number ranging from 1 to 254 to add a qmap mux + based network device, supported by recent Qualcomm based + modems. + + The network device will be called qmimux. + + Userspace is in charge of managing the qmux network device + activation and data stream setup on the modem side by + using the proper QMI protocol requests. + +What: /sys/class/net//qmi/del_mux +Date: March 2017 +KernelVersion: 4.11 +Contact: Bjørn Mork +Description: + Unsigned integer. + + Write a number ranging from 1 to 254 to delete a previously + created qmap mux based network device. + +What: /sys/class/net//qmap/mux_id +Date: January 2021 +KernelVersion: 5.12 +Contact: Daniele Palmas +Description: + Unsigned integer + + Indicates the mux id associated to the qmimux network interface + during its creation. + +What: /sys/class/net//qmi/pass_through +Date: January 2021 +KernelVersion: 5.12 +Contact: Subash Abhinov Kasiviswanathan +Description: + Boolean. Default: 'N' + + Set this to 'Y' to enable 'pass-through' mode, allowing packets + in MAP format to be passed on to the stack. + + Normally the rmnet driver (CONFIG_RMNET) is then used to process + and demultiplex these packets. + + 'Pass-through' mode can be enabled when the device is in + 'raw-ip' mode only. diff --git a/Documentation/ABI/testing/sysfs-class-net-queues b/Documentation/ABI/testing/sysfs-class-net-queues new file mode 100644 index 000000000..978b76358 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-queues @@ -0,0 +1,98 @@ +What: /sys/class//queues/rx-/rps_cpus +Date: March 2010 +KernelVersion: 2.6.35 +Contact: netdev@vger.kernel.org +Description: + Mask of the CPU(s) currently enabled to participate into the + Receive Packet Steering packet processing flow for this + network device queue. Possible values depend on the number + of available CPU(s) in the system. + +What: /sys/class//queues/rx-/rps_flow_cnt +Date: April 2010 +KernelVersion: 2.6.35 +Contact: netdev@vger.kernel.org +Description: + Number of Receive Packet Steering flows being currently + processed by this particular network device receive queue. + +What: /sys/class//queues/tx-/tx_timeout +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of transmit timeout events seen by this + network interface transmit queue. + +What: /sys/class//queues/tx-/tx_maxrate +Date: March 2015 +KernelVersion: 4.1 +Contact: netdev@vger.kernel.org +Description: + A Mbps max-rate set for the queue, a value of zero means disabled, + default is disabled. + +What: /sys/class//queues/tx-/xps_cpus +Date: November 2010 +KernelVersion: 2.6.38 +Contact: netdev@vger.kernel.org +Description: + Mask of the CPU(s) currently enabled to participate into the + Transmit Packet Steering packet processing flow for this + network device transmit queue. Possible vaules depend on the + number of available CPU(s) in the system. + +What: /sys/class//queues/tx-/xps_rxqs +Date: June 2018 +KernelVersion: 4.18.0 +Contact: netdev@vger.kernel.org +Description: + Mask of the receive queue(s) currently enabled to participate + into the Transmit Packet Steering packet processing flow for this + network device transmit queue. Possible values depend on the + number of available receive queue(s) in the network device. + Default is disabled. + +What: /sys/class//queues/tx-/byte_queue_limits/hold_time +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the hold time in milliseconds to measure the slack + of this particular network device transmit queue. + Default value is 1000. + +What: /sys/class//queues/tx-/byte_queue_limits/inflight +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of bytes (objects) in flight on this + network device transmit queue. + +What: /sys/class//queues/tx-/byte_queue_limits/limit +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the current limit of bytes allowed to be queued + on this network device transmit queue. This value is clamped + to be within the bounds defined by limit_max and limit_min. + +What: /sys/class//queues/tx-/byte_queue_limits/limit_max +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the absolute maximum limit of bytes allowed to be + queued on this network device transmit queue. See + include/linux/dynamic_queue_limits.h for the default value. + +What: /sys/class//queues/tx-/byte_queue_limits/limit_min +Date: November 2011 +KernelVersion: 3.3 +Contact: netdev@vger.kernel.org +Description: + Indicates the absolute minimum limit of bytes allowed to be + queued on this network device transmit queue. Default value is + 0. diff --git a/Documentation/ABI/testing/sysfs-class-net-statistics b/Documentation/ABI/testing/sysfs-class-net-statistics new file mode 100644 index 000000000..55db27815 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-net-statistics @@ -0,0 +1,217 @@ +What: /sys/class//statistics/collisions +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of collisions seen by this network device. + This value might not be relevant with all MAC layers. + +What: /sys/class//statistics/multicast +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of multicast packets received by this + network device. + +What: /sys/class//statistics/rx_bytes +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of bytes received by this network device. + See the network driver for the exact meaning of when this + value is incremented. + +What: /sys/class//statistics/rx_compressed +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of compressed packets received by this + network device. This value might only be relevant for interfaces + that support packet compression (e.g: PPP). + +What: /sys/class//statistics/rx_crc_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets received with a CRC (FCS) error + by this network device. Note that the specific meaning might + depend on the MAC layer used by the interface. + +What: /sys/class//statistics/rx_dropped +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets received by the network device + but dropped, that are not forwarded to the upper layers for + packet processing. See the network driver for the exact + meaning of this value. + +What: /sys/class//statistics/rx_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of receive errors on this network device. + See the network driver for the exact meaning of this value. + +What: /sys/class//statistics/rx_fifo_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of receive FIFO errors seen by this + network device. See the network driver for the exact + meaning of this value. + +What: /sys/class//statistics/rx_frame_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of received frames with error, such as + alignment errors. Note that the specific meaning depends on + on the MAC layer protocol used. See the network driver for + the exact meaning of this value. + +What: /sys/class//statistics/rx_length_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of received error packet with a length + error, oversized or undersized. See the network driver for the + exact meaning of this value. + +What: /sys/class//statistics/rx_missed_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of received packets that have been missed + due to lack of capacity in the receive side. See the network + driver for the exact meaning of this value. + +What: /sys/class//statistics/rx_nohandler +Date: February 2016 +KernelVersion: 4.6 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of received packets that were dropped on + an inactive device by the network core. + +What: /sys/class//statistics/rx_over_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of received packets that are oversized + compared to what the network device is configured to accept + (e.g: larger than MTU). See the network driver for the exact + meaning of this value. + +What: /sys/class//statistics/rx_packets +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the total number of good packets received by this + network device. + +What: /sys/class//statistics/tx_aborted_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets that have been aborted + during transmission by a network device (e.g: because of + a medium collision). See the network driver for the exact + meaning of this value. + +What: /sys/class//statistics/tx_bytes +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of bytes transmitted by a network + device. See the network driver for the exact meaning of this + value, in particular whether this accounts for all successfully + transmitted packets or all packets that have been queued for + transmission. + +What: /sys/class//statistics/tx_carrier_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets that could not be transmitted + because of carrier errors (e.g: physical link down). See the + network driver for the exact meaning of this value. + +What: /sys/class//statistics/tx_compressed +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of transmitted compressed packets. Note + this might only be relevant for devices that support + compression (e.g: PPP). + +What: /sys/class//statistics/tx_dropped +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets dropped during transmission. + See the driver for the exact reasons as to why the packets were + dropped. + +What: /sys/class//statistics/tx_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets in error during transmission by + a network device. See the driver for the exact reasons as to + why the packets were dropped. + +What: /sys/class//statistics/tx_fifo_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets having caused a transmit + FIFO error. See the driver for the exact reasons as to why the + packets were dropped. + +What: /sys/class//statistics/tx_heartbeat_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets transmitted that have been + reported as heartbeat errors. See the driver for the exact + reasons as to why the packets were dropped. + +What: /sys/class//statistics/tx_packets +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets transmitted by a network + device. See the driver for whether this reports the number of all + attempted or successful transmissions. + +What: /sys/class//statistics/tx_window_errors +Date: April 2005 +KernelVersion: 2.6.12 +Contact: netdev@vger.kernel.org +Description: + Indicates the number of packets not successfully transmitted + due to a window collision. The specific meaning depends on the + MAC layer used. On Ethernet this is usually used to report + late collisions errors. diff --git a/Documentation/ABI/testing/sysfs-class-ocxl b/Documentation/ABI/testing/sysfs-class-ocxl new file mode 100644 index 000000000..847a7edc3 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-ocxl @@ -0,0 +1,51 @@ +What: /sys/class/ocxl//afu_version +Date: January 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Version of the AFU, in the format : + Reflects what is read in the configuration space of the AFU + +What: /sys/class/ocxl//contexts +Date: January 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Number of contexts for the AFU, in the format / + where: + + ==== =============================================== + n number of currently active contexts, for debug + max maximum number of contexts supported by the AFU + ==== =============================================== + +What: /sys/class/ocxl//pp_mmio_size +Date: January 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Size of the per-process mmio area, as defined in the + configuration space of the AFU + +What: /sys/class/ocxl//global_mmio_size +Date: January 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read only + Size of the global mmio area, as defined in the + configuration space of the AFU + +What: /sys/class/ocxl//global_mmio_area +Date: January 2018 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + Give access the global mmio area for the AFU + +What: /sys/class/ocxl//reload_on_reset +Date: February 2020 +Contact: linuxppc-dev@lists.ozlabs.org +Description: read/write + Control whether the FPGA is reloaded on a link reset. Enabled + through a vendor-specific logic block on the FPGA. + + =========== =========================================== + 0 Do not reload FPGA image from flash + 1 Reload FPGA image from flash + unavailable The device does not support this capability + =========== =========================================== diff --git a/Documentation/ABI/testing/sysfs-class-pktcdvd b/Documentation/ABI/testing/sysfs-class-pktcdvd new file mode 100644 index 000000000..ba1ce6265 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-pktcdvd @@ -0,0 +1,97 @@ +sysfs interface +--------------- +The pktcdvd module (packet writing driver) creates the following files in the +sysfs: ( is in the format major:minor) + +What: /sys/class/pktcdvd/add +What: /sys/class/pktcdvd/remove +What: /sys/class/pktcdvd/device_map +Date: Oct. 2006 +KernelVersion: 2.6.20 +Contact: Thomas Maier +Description: + + ========== ============================================== + add (WO) Write a block device id (major:minor) to + create a new pktcdvd device and map it to the + block device. + + remove (WO) Write the pktcdvd device id (major:minor) + to remove the pktcdvd device. + + device_map (RO) Shows the device mapping in format: + pktcdvd[0-7] + ========== ============================================== + + +What: /sys/class/pktcdvd/pktcdvd[0-7]/dev +What: /sys/class/pktcdvd/pktcdvd[0-7]/uevent +Date: Oct. 2006 +KernelVersion: 2.6.20 +Contact: Thomas Maier +Description: + dev: (RO) Device id + + uevent: (WO) To send a uevent + + +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_started +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_finished +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_written +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read_gather +What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/reset +Date: Oct. 2006 +KernelVersion: 2.6.20 +Contact: Thomas Maier +Description: + packets_started: (RO) Number of started packets. + + packets_finished: (RO) Number of finished packets. + + kb_written: (RO) kBytes written. + + kb_read: (RO) kBytes read. + + kb_read_gather: (RO) kBytes read to fill write packets. + + reset: (WO) Write any value to it to reset + pktcdvd device statistic values, like + bytes read/written. + + +What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/size +What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/congestion_off +What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/congestion_on +Date: Oct. 2006 +KernelVersion: 2.6.20 +Contact: Thomas Maier +Description: + ============== ================================================ + size (RO) Contains the size of the bio write queue. + + congestion_off (RW) If bio write queue size is below this mark, + accept new bio requests from the block layer. + + congestion_on (RW) If bio write queue size is higher as this + mark, do no longer accept bio write requests + from the block layer and wait till the pktcdvd + device has processed enough bio's so that bio + write queue size is below congestion off mark. + A value of <= 0 disables congestion control. + ============== ================================================ + + +Example: +-------- +To use the pktcdvd sysfs interface directly, you can do:: + + # create a new pktcdvd device mapped to /dev/hdc + echo "22:0" >/sys/class/pktcdvd/add + cat /sys/class/pktcdvd/device_map + # assuming device pktcdvd0 was created, look at stat's + cat /sys/class/pktcdvd/pktcdvd0/stat/kb_written + # print the device id of the mapped block device + fgrep pktcdvd0 /sys/class/pktcdvd/device_map + # remove device, using pktcdvd0 device id 253:0 + echo "253:0" >/sys/class/pktcdvd/remove diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power new file mode 100644 index 000000000..e434fc523 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power @@ -0,0 +1,773 @@ +**General Properties** + +What: /sys/class/power_supply//manufacturer +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Reports the name of the device manufacturer. + + Access: Read + Valid values: Represented as string + +What: /sys/class/power_supply//model_name +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Reports the name of the device model. + + Access: Read + Valid values: Represented as string + +What: /sys/class/power_supply//serial_number +Date: January 2008 +Contact: linux-pm@vger.kernel.org +Description: + Reports the serial number of the device. + + Access: Read + Valid values: Represented as string + +What: /sys/class/power_supply//type +Date: May 2010 +Contact: linux-pm@vger.kernel.org +Description: + Describes the main type of the supply. + + Access: Read + Valid values: "Battery", "UPS", "Mains", "USB", "Wireless" + +**Battery and USB properties** + +What: /sys/class/power_supply//current_avg +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports an average IBAT current reading for the battery, over + a fixed period. Normally devices will provide a fixed interval + in which they average readings to smooth out the reported + value. + + USB: + + Reports an average IBUS current reading over a fixed period. + Normally devices will provide a fixed interval in which they + average readings to smooth out the reported value. + + Access: Read + + Valid values: Represented in microamps. Negative values are + used for discharging batteries, positive values for charging + batteries and for USB IBUS current. + +What: /sys/class/power_supply//current_max +Date: October 2010 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the maximum IBAT current allowed into the battery. + + USB: + + Reports the maximum IBUS current the supply can support. + + Access: Read + Valid values: Represented in microamps + +What: /sys/class/power_supply//current_now +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + + Battery: + + Reports an instant, single IBAT current reading for the + battery. This value is not averaged/smoothed. + + Access: Read + + USB: + + Reports the IBUS current supplied now. This value is generally + read-only reporting, unless the 'online' state of the supply + is set to be programmable, in which case this value can be set + within the reported min/max range. + + Access: Read, Write + + Valid values: Represented in microamps. Negative values are + used for discharging batteries, positive values for charging + batteries and for USB IBUS current. + +What: /sys/class/power_supply//temp +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the current TBAT battery temperature reading. + + USB: + + Reports the current supply temperature reading. This would + normally be the internal temperature of the device itself + (e.g TJUNC temperature of an IC) + + Access: Read + + Valid values: Represented in 1/10 Degrees Celsius + +What: /sys/class/power_supply//temp_alert_max +Date: July 2012 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Maximum TBAT temperature trip-wire value where the supply will + notify user-space of the event. + + USB: + + Maximum supply temperature trip-wire value where the supply + will notify user-space of the event. + + This is normally used for the charging scenario where + user-space needs to know if the temperature has crossed an + upper threshold so it can take appropriate action (e.g. warning + user that the temperature is critically high, and charging has + stopped). + + Access: Read + + Valid values: Represented in 1/10 Degrees Celsius + +What: /sys/class/power_supply//temp_alert_min +Date: July 2012 +Contact: linux-pm@vger.kernel.org +Description: + + Battery: + + Minimum TBAT temperature trip-wire value where the supply will + notify user-space of the event. + + USB: + + Minimum supply temperature trip-wire value where the supply + will notify user-space of the event. + + This is normally used for the charging scenario where user-space + needs to know if the temperature has crossed a lower threshold + so it can take appropriate action (e.g. warning user that + temperature level is high, and charging current has been + reduced accordingly to remedy the situation). + + Access: Read + + Valid values: Represented in 1/10 Degrees Celsius + +What: /sys/class/power_supply//temp_max +Date: July 2014 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the maximum allowed TBAT battery temperature for + charging. + + USB: + + Reports the maximum allowed supply temperature for operation. + + Access: Read + + Valid values: Represented in 1/10 Degrees Celsius + +What: /sys/class/power_supply//temp_min +Date: July 2014 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the minimum allowed TBAT battery temperature for + charging. + + USB: + + Reports the minimum allowed supply temperature for operation. + + Access: Read + + Valid values: Represented in 1/10 Degrees Celsius + +What: /sys/class/power_supply//voltage_max, +Date: January 2008 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the maximum safe VBAT voltage permitted for the + battery, during charging. + + USB: + + Reports the maximum VBUS voltage the supply can support. + + Access: Read + + Valid values: Represented in microvolts + +What: /sys/class/power_supply//voltage_min, +Date: January 2008 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports the minimum safe VBAT voltage permitted for the + battery, during discharging. + + USB: + + Reports the minimum VBUS voltage the supply can support. + + Access: Read + + Valid values: Represented in microvolts + +What: /sys/class/power_supply//voltage_now, +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Battery: + + Reports an instant, single VBAT voltage reading for the + battery. This value is not averaged/smoothed. + + Access: Read + + USB: + + Reports the VBUS voltage supplied now. This value is generally + read-only reporting, unless the 'online' state of the supply + is set to be programmable, in which case this value can be set + within the reported min/max range. + + Access: Read, Write + + Valid values: Represented in microvolts + +**Battery Properties** + +What: /sys/class/power_supply//capacity +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Fine grain representation of battery capacity. + + Access: Read + + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//capacity_alert_max +Date: July 2012 +Contact: linux-pm@vger.kernel.org +Description: + Maximum battery capacity trip-wire value where the supply will + notify user-space of the event. This is normally used for the + battery discharging scenario where user-space needs to know the + battery has dropped to an upper level so it can take + appropriate action (e.g. warning user that battery level is + low). + + Access: Read, Write + + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//capacity_alert_min +Date: July 2012 +Contact: linux-pm@vger.kernel.org +Description: + Minimum battery capacity trip-wire value where the supply will + notify user-space of the event. This is normally used for the + battery discharging scenario where user-space needs to know the + battery has dropped to a lower level so it can take + appropriate action (e.g. warning user that battery level is + critically low). + + Access: Read, Write + + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//capacity_error_margin +Date: April 2019 +Contact: linux-pm@vger.kernel.org +Description: + Battery capacity measurement becomes unreliable without + recalibration. This values provides the maximum error + margin expected to exist by the fuel gauge in percent. + Values close to 0% will be returned after (re-)calibration + has happened. Over time the error margin will increase. + 100% means, that the capacity related values are basically + completely useless. + + Access: Read + + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//capacity_level +Date: June 2009 +Contact: linux-pm@vger.kernel.org +Description: + Coarse representation of battery capacity. + + Access: Read + + Valid values: + "Unknown", "Critical", "Low", "Normal", "High", + "Full" + +What: /sys/class/power_supply//charge_control_limit +Date: Oct 2012 +Contact: linux-pm@vger.kernel.org +Description: + Maximum allowable charging current. Used for charge rate + throttling for thermal cooling or improving battery health. + + Access: Read, Write + + Valid values: Represented in microamps + +What: /sys/class/power_supply//charge_control_limit_max +Date: Oct 2012 +Contact: linux-pm@vger.kernel.org +Description: + Maximum legal value for the charge_control_limit property. + + Access: Read + + Valid values: Represented in microamps + +What: /sys/class/power_supply//charge_control_start_threshold +Date: April 2019 +Contact: linux-pm@vger.kernel.org +Description: + Represents a battery percentage level, below which charging will + begin. + + Access: Read, Write + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//charge_control_end_threshold +Date: April 2019 +Contact: linux-pm@vger.kernel.org +Description: + Represents a battery percentage level, above which charging will + stop. Not all hardware is capable of setting this to an arbitrary + percentage. Drivers will round written values to the nearest + supported value. Reading back the value will show the actual + threshold set by the driver. + + Access: Read, Write + + Valid values: 0 - 100 (percent) + +What: /sys/class/power_supply//charge_type +Date: July 2009 +Contact: linux-pm@vger.kernel.org +Description: + Represents the type of charging currently being applied to the + battery. "Trickle", "Fast", and "Standard" all mean different + charging speeds. "Adaptive" means that the charger uses some + algorithm to adjust the charge rate dynamically, without + any user configuration required. "Custom" means that the charger + uses the charge_control_* properties as configuration for some + different algorithm. "Long Life" means the charger reduces its + charging rate in order to prolong the battery health. "Bypass" + means the charger bypasses the charging path around the + integrated converter allowing for a "smart" wall adaptor to + perform the power conversion externally. + + Access: Read, Write + + Valid values: + "Unknown", "N/A", "Trickle", "Fast", "Standard", + "Adaptive", "Custom", "Long Life", "Bypass" + +What: /sys/class/power_supply//charge_term_current +Date: July 2014 +Contact: linux-pm@vger.kernel.org +Description: + Reports the charging current value which is used to determine + when the battery is considered full and charging should end. + + Access: Read + + Valid values: Represented in microamps + +What: /sys/class/power_supply//health +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Reports the health of the battery or battery side of charger + functionality. + + Access: Read + + Valid values: + "Unknown", "Good", "Overheat", "Dead", + "Over voltage", "Unspecified failure", "Cold", + "Watchdog timer expire", "Safety timer expire", + "Over current", "Calibration required", "Warm", + "Cool", "Hot", "No battery" + +What: /sys/class/power_supply//precharge_current +Date: June 2017 +Contact: linux-pm@vger.kernel.org +Description: + Reports the charging current applied during pre-charging phase + for a battery charge cycle. + + Access: Read + + Valid values: Represented in microamps + +What: /sys/class/power_supply//present +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Reports whether a battery is present or not in the system. + + Access: Read + + Valid values: + + == ======= + 0: Absent + 1: Present + == ======= + +What: /sys/class/power_supply//status +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Represents the charging status of the battery. Normally this + is read-only reporting although for some supplies this can be + used to enable/disable charging to the battery. + + Access: Read, Write + + Valid values: + "Unknown", "Charging", "Discharging", + "Not charging", "Full" + +What: /sys/class/power_supply//charge_behaviour +Date: November 2021 +Contact: linux-pm@vger.kernel.org +Description: + Represents the charging behaviour. + + Access: Read, Write + + Valid values: + ================ ==================================== + auto: Charge normally, respect thresholds + inhibit-charge: Do not charge while AC is attached + force-discharge: Force discharge while AC is attached + ================ ==================================== + +What: /sys/class/power_supply//technology +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Describes the battery technology supported by the supply. + + Access: Read + + Valid values: + "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe", + "NiCd", "LiMn" + + +What: /sys/class/power_supply//voltage_avg, +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Reports an average VBAT voltage reading for the battery, over a + fixed period. Normally devices will provide a fixed interval in + which they average readings to smooth out the reported value. + + Access: Read + + Valid values: Represented in microvolts + +What: /sys/class/power_supply//cycle_count +Date: January 2010 +Contact: linux-pm@vger.kernel.org +Description: + Reports the number of full charge + discharge cycles the + battery has undergone. + + Access: Read + + Valid values: + Integer > 0: representing full cycles + Integer = 0: cycle_count info is not available + +**USB Properties** + +What: /sys/class/power_supply//input_current_limit +Date: July 2014 +Contact: linux-pm@vger.kernel.org +Description: + Details the incoming IBUS current limit currently set in the + supply. Normally this is configured based on the type of + connection made (e.g. A configured SDP should output a maximum + of 500mA so the input current limit is set to the same value). + Use preferably input_power_limit, and for problems that can be + solved using power limit use input_current_limit. + + Access: Read, Write + + Valid values: Represented in microamps + +What: /sys/class/power_supply//input_voltage_limit +Date: May 2019 +Contact: linux-pm@vger.kernel.org +Description: + This entry configures the incoming VBUS voltage limit currently + set in the supply. Normally this is configured based on + system-level knowledge or user input (e.g. This is part of the + Pixel C's thermal management strategy to effectively limit the + input power to 5V when the screen is on to meet Google's skin + temperature targets). Note that this feature should not be + used for safety critical things. + Use preferably input_power_limit, and for problems that can be + solved using power limit use input_voltage_limit. + + Access: Read, Write + + Valid values: Represented in microvolts + +What: /sys/class/power_supply//input_power_limit +Date: May 2019 +Contact: linux-pm@vger.kernel.org +Description: + This entry configures the incoming power limit currently set + in the supply. Normally this is configured based on + system-level knowledge or user input. Use preferably this + feature to limit the incoming power and use current/voltage + limit only for problems that can be solved using power limit. + + Access: Read, Write + + Valid values: Represented in microwatts + +What: /sys/class/power_supply//online, +Date: May 2007 +Contact: linux-pm@vger.kernel.org +Description: + Indicates if VBUS is present for the supply. When the supply is + online, and the supply allows it, then it's possible to switch + between online states (e.g. Fixed -> Programmable for a PD_PPS + USB supply so voltage and current can be controlled). + + Access: Read, Write + + Valid values: + + == ================================================== + 0: Offline + 1: Online Fixed - Fixed Voltage Supply + 2: Online Programmable - Programmable Voltage Supply + == ================================================== + +What: /sys/class/power_supply//usb_type +Date: March 2018 +Contact: linux-pm@vger.kernel.org +Description: + Reports what type of USB connection is currently active for + the supply, for example it can show if USB-PD capable source + is attached. + + Access: Read-Only + + Valid values: + "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD", + "PD_DRP", "PD_PPS", "BrickID" + +**Device Specific Properties** + +What: /sys/class/power/ds2760-battery.*/charge_now +Date: May 2010 +KernelVersion: 2.6.35 +Contact: Daniel Mack +Description: + This file is writeable and can be used to set the current + coloumb counter value inside the battery monitor chip. This + is needed for unavoidable corrections of aging batteries. + A userspace daemon can monitor the battery charging logic + and once the counter drops out of considerable bounds, take + appropriate action. + +What: /sys/class/power/ds2760-battery.*/charge_full +Date: May 2010 +KernelVersion: 2.6.35 +Contact: Daniel Mack +Description: + This file is writeable and can be used to set the assumed + battery 'full level'. As batteries age, this value has to be + amended over time. + +What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer +Date: October 2014 +KernelVersion: 3.18.0 +Contact: Krzysztof Kozlowski +Description: + This entry shows and sets the maximum time the max14577 + charger operates in fast-charge mode. When the timer expires + the device will terminate fast-charge mode (charging current + will drop to 0 A) and will trigger interrupt. + + Valid values: + + - 5, 6 or 7 (hours), + - 0: disabled. + +What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer +Date: January 2015 +KernelVersion: 3.19.0 +Contact: Krzysztof Kozlowski +Description: + This entry shows and sets the maximum time the max77693 + charger operates in fast-charge mode. When the timer expires + the device will terminate fast-charge mode (charging current + will drop to 0 A) and will trigger interrupt. + + Valid values: + + - 4 - 16 (hours), step by 2 (rounded down) + - 0: disabled. + +What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current +Date: January 2015 +KernelVersion: 3.19.0 +Contact: Krzysztof Kozlowski +Description: + This entry shows and sets the charging current threshold for + entering top-off charging mode. When charging current in fast + charge mode drops below this value, the charger will trigger + interrupt and start top-off charging mode. + + Valid values: + + - 100000 - 200000 (microamps), step by 25000 (rounded down) + - 200000 - 350000 (microamps), step by 50000 (rounded down) + - 0: disabled. + +What: /sys/class/power_supply/max77693-charger/device/top_off_timer +Date: January 2015 +KernelVersion: 3.19.0 +Contact: Krzysztof Kozlowski +Description: + This entry shows and sets the maximum time the max77693 + charger operates in top-off charge mode. When the timer expires + the device will terminate top-off charge mode (charging current + will drop to 0 A) and will trigger interrupt. + + Valid values: + + - 0 - 70 (minutes), step by 10 (rounded down) + +What: /sys/class/power_supply/bq24257-charger/ovp_voltage +Date: October 2015 +KernelVersion: 4.4.0 +Contact: Andreas Dannenberg +Description: + This entry configures the overvoltage protection feature of bq24257- + type charger devices. This feature protects the device and other + components against damage from overvoltage on the input supply. See + device datasheet for details. + + Valid values: + + - 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000, + 10500000 (all uV) + +What: /sys/class/power_supply/bq24257-charger/in_dpm_voltage +Date: October 2015 +KernelVersion: 4.4.0 +Contact: Andreas Dannenberg +Description: + This entry configures the input dynamic power path management voltage of + bq24257-type charger devices. Once the supply drops to the configured + voltage, the input current limit is reduced down to prevent the further + drop of the supply. When the IC enters this mode, the charge current is + lower than the set value. See device datasheet for details. + + Valid values: + + - 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000, + 4760000 (all uV) + +What: /sys/class/power_supply/bq24257-charger/high_impedance_enable +Date: October 2015 +KernelVersion: 4.4.0 +Contact: Andreas Dannenberg +Description: + This entry allows enabling the high-impedance mode of bq24257-type + charger devices. If enabled, it places the charger IC into low power + standby mode with the switch mode controller disabled. When disabled, + the charger operates normally. See device datasheet for details. + + Valid values: + + - 1: enabled + - 0: disabled + +What: /sys/class/power_supply/bq24257-charger/sysoff_enable +Date: October 2015 +KernelVersion: 4.4.0 +Contact: Andreas Dannenberg +Description: + This entry allows enabling the sysoff mode of bq24257-type charger + devices. If enabled and the input is removed, the internal battery FET + is turned off in order to reduce the leakage from the BAT pin to less + than 1uA. Note that on some devices/systems this disconnects the battery + from the system. See device datasheet for details. + + Valid values: + + - 1: enabled + - 0: disabled + +What: /sys/class/power_supply//manufacture_year +Date: January 2020 +Contact: linux-pm@vger.kernel.org +Description: + Reports the year (following Gregorian calendar) when the device has been + manufactured. + + Access: Read + + Valid values: Reported as integer + +What: /sys/class/power_supply//manufacture_month +Date: January 2020 +Contact: linux-pm@vger.kernel.org +Description: + Reports the month when the device has been manufactured. + + Access: Read + + Valid values: 1-12 + +What: /sys/class/power_supply//manufacture_day +Date: January 2020 +Contact: linux-pm@vger.kernel.org +Description: + Reports the day of month when the device has been manufactured. + + Access: Read + Valid values: 1-31 diff --git a/Documentation/ABI/testing/sysfs-class-power-ltc4162l b/Documentation/ABI/testing/sysfs-class-power-ltc4162l new file mode 100644 index 000000000..ba30db930 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power-ltc4162l @@ -0,0 +1,82 @@ +What: /sys/class/power_supply/ltc4162-l/charge_status +Date: Januari 2021 +KernelVersion: 5.11 +Description: + Detailed charge status information as reported by the chip. + + Access: Read + + Valid values: + ilim_reg_active + thermal_reg_active + vin_uvcl_active + iin_limit_active + constant_current + constant_voltage + charger_off + +What: /sys/class/power_supply/ltc4162-l/ibat +Date: Januari 2021 +KernelVersion: 5.11 +Description: + Battery input current as measured by the charger. Negative value + means that the battery is discharging. + + Access: Read + + Valid values: Signed value in microamps + +What: /sys/class/power_supply/ltc4162-l/vbat +Date: Januari 2021 +KernelVersion: 5.11 +Description: + Battery voltage as measured by the charger. + + Access: Read + + Valid values: In microvolts + +What: /sys/class/power_supply/ltc4162-l/vbat_avg +Date: Januari 2021 +KernelVersion: 5.11 +Description: + Battery voltage, averaged over time, as measured by the charger. + + Access: Read + + Valid values: In microvolts + +What: /sys/class/power_supply/ltc4162-l/force_telemetry +Date: Januari 2021 +KernelVersion: 5.11 +Description: + To save battery current, the measurement system is disabled if + the battery is the only source of power. This affects all + voltage, current and temperature measurements. + Write a "1" to this to keep performing telemetry once every few + seconds, even when running on battery (as reported by the online + property, which is "1" when external power is available and "0" + when the system runs on battery). + + Access: Read, Write + + Valid values: 0 (disabled) or 1 (enabled) + +What: /sys/class/power_supply/ltc4162-l/arm_ship_mode +Date: Januari 2021 +KernelVersion: 5.11 +Description: + The charger will normally drain the battery while inactive, + typically drawing about 54 microamps. Write a "1" to this + property to arm a special "ship" mode that extends shelf life + by reducing the leakage to about 2.8 microamps. The chip will + remain in this mode (and no longer respond to I2C commands) + until some external power-supply is attached raising the input + voltage above 1V. It will then automatically revert to "0". + Writing a "0" to the property cancels the "ship" mode request. + The ship mode, when armed, activates once the input voltage + drops below 1V. + + Access: Read, Write + + Valid values: 0 (disable) or 1 (enable) diff --git a/Documentation/ABI/testing/sysfs-class-power-mp2629 b/Documentation/ABI/testing/sysfs-class-power-mp2629 new file mode 100644 index 000000000..914d67caa --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power-mp2629 @@ -0,0 +1,9 @@ +What: /sys/class/power_supply/mp2629_battery/batt_impedance_compen +Date: April 2020 +KernelVersion: 5.7 +Description: + Represents a battery impedance compensation to accelerate charging. + + Access: Read, Write + + Valid values: Represented in milli-ohms. Valid range is [0, 140]. diff --git a/Documentation/ABI/testing/sysfs-class-power-surface b/Documentation/ABI/testing/sysfs-class-power-surface new file mode 100644 index 000000000..79cde4dcf --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power-surface @@ -0,0 +1,15 @@ +What: /sys/class/power_supply//alarm +Date: April 2021 +KernelVersion: 5.13 +Contact: Maximilian Luz +Description: + Battery trip point. When the remaining battery capacity crosses this + value in either direction, the system will be notified and if + necessary woken. + + Set to zero to clear/disable. + + Access: Read, Write + + Valid values: In micro-Wh or micro-Ah, depending on the power unit + of the battery diff --git a/Documentation/ABI/testing/sysfs-class-power-twl4030 b/Documentation/ABI/testing/sysfs-class-power-twl4030 new file mode 100644 index 000000000..b52f7023f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power-twl4030 @@ -0,0 +1,33 @@ +What: /sys/class/power_supply/twl4030_usb/mode +Description: + Changing mode for USB port. + Writing to this can disable charging. + + Possible values are: + + ============= =========================================== + "auto" draw power as appropriate for detected + power source and battery status. + "off" do not draw any power. + "continuous" activate mode described as "linear" in + TWL data sheets. This uses whatever + current is available and doesn't switch off + when voltage drops. + + This is useful for unstable power sources + such as bicycle dynamo, but care should + be taken that battery is not over-charged. + ============= =========================================== + +What: /sys/class/power_supply/twl4030_ac/mode +Description: + Changing mode for 'ac' port. + Writing to this can disable charging. + + Possible values are: + + ====== =========================================== + "auto" draw power as appropriate for detected + power source and battery status. + "off" do not draw any power. + ====== =========================================== diff --git a/Documentation/ABI/testing/sysfs-class-power-wilco b/Documentation/ABI/testing/sysfs-class-power-wilco new file mode 100644 index 000000000..82af180fc --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-power-wilco @@ -0,0 +1,40 @@ +What: /sys/class/power_supply/wilco-charger/charge_type +Date: April 2019 +KernelVersion: 5.2 +Description: + What charging algorithm to use: + + Standard: + Fully charges battery at a standard rate. + Adaptive: + Battery settings adaptively optimized based on + typical battery usage pattern. + Fast: + Battery charges over a shorter period. + Trickle: + Extends battery lifespan, intended for users who + primarily use their Chromebook while connected to AC. + Custom: + A low and high threshold percentage is specified. + Charging begins when level drops below + charge_control_start_threshold, and ceases when + level is above charge_control_end_threshold. + Long Life: + Customized charge rate for last longer battery life. + On Wilco device this mode is pre-configured in the factory + through EC's private PID. Swiching to a different mode will + be denied by Wilco EC when Long Life mode is enabled. + +What: /sys/class/power_supply/wilco-charger/charge_control_start_threshold +Date: April 2019 +KernelVersion: 5.2 +Description: + Used when charge_type="Custom", as described above. Measured in + percentages. The valid range is [50, 95]. + +What: /sys/class/power_supply/wilco-charger/charge_control_end_threshold +Date: April 2019 +KernelVersion: 5.2 +Description: + Used when charge_type="Custom", as described above. Measured in + percentages. The valid range is [55, 100]. diff --git a/Documentation/ABI/testing/sysfs-class-powercap b/Documentation/ABI/testing/sysfs-class-powercap new file mode 100644 index 000000000..ca491ec4e --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-powercap @@ -0,0 +1,152 @@ +What: /sys/class/powercap/ +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + The powercap/ class sub directory belongs to the power cap + subsystem. Refer to + Documentation/power/powercap/powercap.rst for details. + +What: /sys/class/powercap/ +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + A is a unique name under /sys/class/powercap. + Here determines how the power is going to be + controlled. A can contain multiple power zones. + +What: /sys/class/powercap//enabled +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + This allows to enable/disable power capping for a "control type". + This status affects every power zone using this "control_type. + +What: /sys/class/powercap// +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + A power zone is a single or a collection of devices, which can + be independently monitored and controlled. A power zone sysfs + entry is qualified with the name of the . + E.g. intel-rapl:0:1:1. + +What: /sys/class/powercap/// +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Power zones may be organized in a hierarchy in which child + power zones provide monitoring and control for a subset of + devices under the parent. For example, if there is a parent + power zone for a whole CPU package, each CPU core in it can + be a child power zone. + +What: /sys/class/powercap/...//name +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Specifies the name of this power zone. + +What: /sys/class/powercap/...//energy_uj +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Current energy counter in micro-joules. Write "0" to reset. + If the counter can not be reset, then this attribute is + read-only. + +What: /sys/class/powercap/...//max_energy_range_uj +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Range of the above energy counter in micro-joules. + + +What: /sys/class/powercap/...//power_uw +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Current power in micro-watts. + +What: /sys/class/powercap/...//max_power_range_uw +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Range of the above power value in micro-watts. + +What: /sys/class/powercap/...//constraint_X_name +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Each power zone can define one or more constraints. Each + constraint can have an optional name. Here "X" can have values + from 0 to max integer. + +What: /sys/class/powercap/...//constraint_X_power_limit_uw +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Power limit in micro-watts should be applicable for + the time window specified by "constraint_X_time_window_us". + Here "X" can have values from 0 to max integer. + +What: /sys/class/powercap/...//constraint_X_time_window_us +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Time window in micro seconds. This is used along with + constraint_X_power_limit_uw to define a power constraint. + Here "X" can have values from 0 to max integer. + + +What: /sys/class/powercap//.../constraint_X_max_power_uw +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Maximum allowed power in micro watts for this constraint. + Here "X" can have values from 0 to max integer. + +What: /sys/class/powercap//.../constraint_X_min_power_uw +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Minimum allowed power in micro watts for this constraint. + Here "X" can have values from 0 to max integer. + +What: /sys/class/powercap/...//constraint_X_max_time_window_us +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Maximum allowed time window in micro seconds for this + constraint. Here "X" can have values from 0 to max integer. + +What: /sys/class/powercap/...//constraint_X_min_time_window_us +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + Minimum allowed time window in micro seconds for this + constraint. Here "X" can have values from 0 to max integer. + +What: /sys/class/powercap/...//enabled +Date: September 2013 +KernelVersion: 3.13 +Contact: linux-pm@vger.kernel.org +Description: + This allows to enable/disable power capping at power zone level. + This applies to current power zone and its children. diff --git a/Documentation/ABI/testing/sysfs-class-pwm b/Documentation/ABI/testing/sysfs-class-pwm new file mode 100644 index 000000000..0638c94d0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-pwm @@ -0,0 +1,88 @@ +What: /sys/class/pwm/ +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + The pwm/ class sub-directory belongs to the Generic PWM + Framework and provides a sysfs interface for using PWM + channels. + +What: /sys/class/pwm/pwmchip/ +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + A /sys/class/pwm/pwmchipN directory is created for each + probed PWM controller/chip where N is the base of the + PWM chip. + +What: /sys/class/pwm/pwmchip/npwm +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + The number of PWM channels supported by the PWM chip. + +What: /sys/class/pwm/pwmchip/export +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Exports a PWM channel from the PWM chip for sysfs control. + Value is between 0 and /sys/class/pwm/pwmchipN/npwm - 1. + +What: /sys/class/pwm/pwmchip/unexport +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Unexports a PWM channel. + +What: /sys/class/pwm/pwmchip/pwmX +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + A /sys/class/pwm/pwmchipN/pwmX directory is created for + each exported PWM channel where X is the exported PWM + channel number. + +What: /sys/class/pwm/pwmchip/pwmX/period +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Sets the PWM signal period in nanoseconds. + +What: /sys/class/pwm/pwmchip/pwmX/duty_cycle +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Sets the PWM signal duty cycle in nanoseconds. + +What: /sys/class/pwm/pwmchip/pwmX/polarity +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Sets the output polarity of the PWM signal to "normal" or + "inversed". + +What: /sys/class/pwm/pwmchip/pwmX/enable +Date: May 2013 +KernelVersion: 3.11 +Contact: H Hartley Sweeten +Description: + Enable/disable the PWM signal. + 0 is disabled + 1 is enabled + +What: /sys/class/pwm/pwmchip/pwmX/capture +Date: June 2016 +KernelVersion: 4.8 +Contact: Lee Jones +Description: + Capture information about a PWM signal. The output format is a + pair unsigned integers (period and duty cycle), separated by a + single space. diff --git a/Documentation/ABI/testing/sysfs-class-rapidio b/Documentation/ABI/testing/sysfs-class-rapidio new file mode 100644 index 000000000..81e091455 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rapidio @@ -0,0 +1,59 @@ +What: /sys/class/rapidio_port +Description: + On-chip RapidIO controllers and PCIe-to-RapidIO bridges + (referenced as "Master Port" or "mport") are presented in sysfs + as the special class of devices: "rapidio_port". + The /sys/class/rapidio_port subdirectory contains individual + subdirectories named as "rapidioN" where N = mport ID registered + with RapidIO subsystem. + + NOTE: An mport ID is not a RapidIO destination ID assigned to a + given local mport device. + +What: /sys/class/rapidio_port/rapidio/sys_size +Date: Apr, 2014 +KernelVersion: v3.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + (RO) reports RapidIO common transport system size: + + 0 = small (8-bit destination ID, max. 256 devices), + + 1 = large (16-bit destination ID, max. 65536 devices). + +What: /sys/class/rapidio_port/rapidio/port_destid +Date: Apr, 2014 +KernelVersion: v3.15 +Contact: Matt Porter , + Alexandre Bounine +Description: + +(RO) reports RapidIO destination ID assigned to the given +RapidIO mport device. If value 0xFFFFFFFF is returned this means +that no valid destination ID have been assigned to the mport +(yet). Normally, before enumeration/discovery have been executed +only fabric enumerating mports have a valid destination ID +assigned to them using "hdid=..." rapidio module parameter. + +After enumeration or discovery was performed for a given mport device, +the corresponding subdirectory will also contain subdirectories for each +child RapidIO device connected to the mport. + +The example below shows mport device subdirectory with several child RapidIO +devices attached to it:: + + [rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l + total 0 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0001 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0004 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0007 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0002 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0003 + drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0005 + lrwxrwxrwx 1 root root 0 Feb 11 15:11 device -> ../../../0000:01:00.0 + -r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid + drwxr-xr-x 2 root root 0 Feb 11 15:11 power + lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port + -r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size + -rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent diff --git a/Documentation/ABI/testing/sysfs-class-rc b/Documentation/ABI/testing/sysfs-class-rc new file mode 100644 index 000000000..84e46d70d --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rc @@ -0,0 +1,137 @@ +What: /sys/class/rc/ +Date: Apr 2010 +KernelVersion: 2.6.35 +Contact: Mauro Carvalho Chehab +Description: + The rc/ class sub-directory belongs to the Remote Controller + core and provides a sysfs interface for configuring infrared + remote controller receivers. + +What: /sys/class/rc/rc/ +Date: Apr 2010 +KernelVersion: 2.6.35 +Contact: Mauro Carvalho Chehab +Description: + A /sys/class/rc/rcN directory is created for each remote + control receiver device where N is the number of the receiver. + +What: /sys/class/rc/rc/protocols +Date: Jun 2010 +KernelVersion: 2.6.36 +Contact: Mauro Carvalho Chehab +Description: + Reading this file returns a list of available protocols, + something like:: + + "rc5 [rc6] nec jvc [sony]" + + Enabled protocols are shown in [] brackets. + + Writing "+proto" will add a protocol to the list of enabled + protocols. + + Writing "-proto" will remove a protocol from the list of enabled + protocols. + + Writing "proto" will enable only "proto". + + Writing "none" will disable all protocols. + + Write fails with EINVAL if an invalid protocol combination or + unknown protocol name is used. + +What: /sys/class/rc/rc/filter +Date: Jan 2014 +KernelVersion: 3.15 +Contact: Mauro Carvalho Chehab +Description: + Sets the scancode filter expected value. + + Use in combination with /sys/class/rc/rcN/filter_mask to set the + expected value of the bits set in the filter mask. + If the hardware supports it then scancodes which do not match + the filter will be ignored. Otherwise the write will fail with + an error. + + This value may be reset to 0 if the current protocol is altered. + +What: /sys/class/rc/rc/filter_mask +Date: Jan 2014 +KernelVersion: 3.15 +Contact: Mauro Carvalho Chehab +Description: + Sets the scancode filter mask of bits to compare. + Use in combination with /sys/class/rc/rcN/filter to set the bits + of the scancode which should be compared against the expected + value. A value of 0 disables the filter to allow all valid + scancodes to be processed. + + If the hardware supports it then scancodes which do not match + the filter will be ignored. Otherwise the write will fail with + an error. + + This value may be reset to 0 if the current protocol is altered. + +What: /sys/class/rc/rc/wakeup_protocols +Date: Feb 2017 +KernelVersion: 4.11 +Contact: Mauro Carvalho Chehab +Description: + Reading this file returns a list of available protocols to use + for the wakeup filter, something like:: + + "rc-5 nec nec-x rc-6-0 rc-6-6a-24 [rc-6-6a-32] rc-6-mce" + + Note that protocol variants are listed, so "nec", "sony", + "rc-5", "rc-6" have their different bit length encodings + listed if available. + + The enabled wakeup protocol is shown in [] brackets. + + Only one protocol can be selected at a time. + + Writing "proto" will use "proto" for wakeup events. + + Writing "none" will disable wakeup. + + Write fails with EINVAL if an invalid protocol combination or + unknown protocol name is used, or if wakeup is not supported by + the hardware. + +What: /sys/class/rc/rc/wakeup_filter +Date: Jan 2014 +KernelVersion: 3.15 +Contact: Mauro Carvalho Chehab +Description: + Sets the scancode wakeup filter expected value. + + Use in combination with /sys/class/rc/rcN/wakeup_filter_mask to + set the expected value of the bits set in the wakeup filter mask + to trigger a system wake event. + + If the hardware supports it and wakeup_filter_mask is not 0 then + scancodes which match the filter will wake the system from e.g. + suspend to RAM or power off. + + Otherwise the write will fail with an error. + + This value may be reset to 0 if the wakeup protocol is altered. + +What: /sys/class/rc/rc/wakeup_filter_mask +Date: Jan 2014 +KernelVersion: 3.15 +Contact: Mauro Carvalho Chehab +Description: + Sets the scancode wakeup filter mask of bits to compare. + + Use in combination with /sys/class/rc/rcN/wakeup_filter to set + the bits of the scancode which should be compared against the + expected value to trigger a system wake event. + + If the hardware supports it and wakeup_filter_mask is not 0 then + scancodes which match the filter will wake the system from e.g. + suspend to RAM or power off. + + Otherwise the write will fail with an error. + + This value may be reset to 0 if the wakeup protocol is altered. diff --git a/Documentation/ABI/testing/sysfs-class-rc-nuvoton b/Documentation/ABI/testing/sysfs-class-rc-nuvoton new file mode 100644 index 000000000..f7bad8ecd --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rc-nuvoton @@ -0,0 +1,15 @@ +What: /sys/class/rc/rc/wakeup_data +Date: Mar 2016 +KernelVersion: 4.6 +Contact: Mauro Carvalho Chehab +Description: + Reading this file returns the stored CIR wakeup sequence. + It starts with a pulse, followed by a space, pulse etc. + All values are in microseconds. + The same format can be used to store a wakeup sequence + in the Nuvoton chip by writing to this file. + + Note: Some systems reset the stored wakeup sequence to a + factory default on each boot. On such systems store the + wakeup sequence in a file and set it on boot using e.g. + a udev rule. diff --git a/Documentation/ABI/testing/sysfs-class-regulator b/Documentation/ABI/testing/sysfs-class-regulator new file mode 100644 index 000000000..475b9a372 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-regulator @@ -0,0 +1,453 @@ +What: /sys/class/regulator/.../state +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + state. This reports the regulator enable control, for + regulators which can report that input value. + + This will be one of the following strings: + + 'enabled' + 'disabled' + 'unknown' + + 'enabled' means the regulator output is ON and is supplying + power to the system (assuming no error prevents it). + + 'disabled' means the regulator output is OFF and is not + supplying power to the system (unless some non-Linux + control has enabled it). + + 'unknown' means software cannot determine the state, or + the reported state is invalid. + + NOTE: this field can be used in conjunction with microvolts + or microamps to determine configured regulator output levels. + + +What: /sys/class/regulator/.../status +Description: + Some regulator directories will contain a field called + "status". This reports the current regulator status, for + regulators which can report that output value. + + This will be one of the following strings: + + - off + - on + - error + - fast + - normal + - idle + - standby + + "off" means the regulator is not supplying power to the + system. + + "on" means the regulator is supplying power to the system, + and the regulator can't report a detailed operation mode. + + "error" indicates an out-of-regulation status such as being + disabled due to thermal shutdown, or voltage being unstable + because of problems with the input power supply. + + "fast", "normal", "idle", and "standby" are all detailed + regulator operation modes (described elsewhere). They + imply "on", but provide more detail. + + Note that regulator status is a function of many inputs, + not limited to control inputs from Linux. For example, + the actual load presented may trigger "error" status; or + a regulator may be enabled by another user, even though + Linux did not enable it. + + +What: /sys/class/regulator/.../type +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Each regulator directory will contain a field called + type. This holds the regulator type. + + This will be one of the following strings: + + - 'voltage' + - 'current' + - 'unknown' + + 'voltage' means the regulator output voltage can be controlled + by software. + + 'current' means the regulator output current limit can be + controlled by software. + + 'unknown' means software cannot control either voltage or + current limit. + + +What: /sys/class/regulator/.../microvolts +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + microvolts. This holds the regulator output voltage setting + measured in microvolts (i.e. E-6 Volts), for regulators + which can report the control input for voltage. + + NOTE: This value should not be used to determine the regulator + output voltage level as this value is the same regardless of + whether the regulator is enabled or disabled. + + +What: /sys/class/regulator/.../microamps +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + microamps. This holds the regulator output current limit + setting measured in microamps (i.e. E-6 Amps), for regulators + which can report the control input for a current limit. + + NOTE: This value should not be used to determine the regulator + output current level as this value is the same regardless of + whether the regulator is enabled or disabled. + + +What: /sys/class/regulator/.../opmode +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + opmode. This holds the current regulator operating mode, + for regulators which can report that control input value. + + The opmode value can be one of the following strings: + + - 'fast' + - 'normal' + - 'idle' + - 'standby' + - 'unknown' + + The modes are described in include/linux/regulator/consumer.h + + NOTE: This value should not be used to determine the regulator + output operating mode as this value is the same regardless of + whether the regulator is enabled or disabled. A "status" + attribute may be available to determine the actual mode. + + +What: /sys/class/regulator/.../min_microvolts +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + min_microvolts. This holds the minimum safe working regulator + output voltage setting for this domain measured in microvolts, + for regulators which support voltage constraints. + + NOTE: this will return the string 'constraint not defined' if + the power domain has no min microvolts constraint defined by + platform code. + + +What: /sys/class/regulator/.../max_microvolts +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + max_microvolts. This holds the maximum safe working regulator + output voltage setting for this domain measured in microvolts, + for regulators which support voltage constraints. + + NOTE: this will return the string 'constraint not defined' if + the power domain has no max microvolts constraint defined by + platform code. + + +What: /sys/class/regulator/.../min_microamps +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + min_microamps. This holds the minimum safe working regulator + output current limit setting for this domain measured in + microamps, for regulators which support current constraints. + + NOTE: this will return the string 'constraint not defined' if + the power domain has no min microamps constraint defined by + platform code. + + +What: /sys/class/regulator/.../max_microamps +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + max_microamps. This holds the maximum safe working regulator + output current limit setting for this domain measured in + microamps, for regulators which support current constraints. + + NOTE: this will return the string 'constraint not defined' if + the power domain has no max microamps constraint defined by + platform code. + + +What: /sys/class/regulator/.../name +Date: October 2008 +KernelVersion: 2.6.28 +Contact: Liam Girdwood +Description: + Each regulator directory will contain a field called + name. This holds a string identifying the regulator for + display purposes. + + NOTE: this will be empty if no suitable name is provided + by platform or regulator drivers. + + +What: /sys/class/regulator/.../num_users +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Each regulator directory will contain a field called + num_users. This holds the number of consumer devices that + have called regulator_enable() on this regulator. + + +What: /sys/class/regulator/.../requested_microamps +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + requested_microamps. This holds the total requested load + current in microamps for this regulator from all its consumer + devices. + + +What: /sys/class/regulator/.../parent +Date: April 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a link called parent. + This points to the parent or supply regulator if one exists. + +What: /sys/class/regulator/.../suspend_mem_microvolts +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_mem_microvolts. This holds the regulator output + voltage setting for this domain measured in microvolts when + the system is suspended to memory, for voltage regulators + implementing suspend voltage configuration constraints. + +What: /sys/class/regulator/.../suspend_disk_microvolts +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_disk_microvolts. This holds the regulator output + voltage setting for this domain measured in microvolts when + the system is suspended to disk, for voltage regulators + implementing suspend voltage configuration constraints. + +What: /sys/class/regulator/.../suspend_standby_microvolts +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_standby_microvolts. This holds the regulator output + voltage setting for this domain measured in microvolts when + the system is suspended to standby, for voltage regulators + implementing suspend voltage configuration constraints. + +What: /sys/class/regulator/.../suspend_mem_mode +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_mem_mode. This holds the regulator operating mode + setting for this domain when the system is suspended to + memory, for regulators implementing suspend mode + configuration constraints. + +What: /sys/class/regulator/.../suspend_disk_mode +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_disk_mode. This holds the regulator operating mode + setting for this domain when the system is suspended to disk, + for regulators implementing suspend mode configuration + constraints. + +What: /sys/class/regulator/.../suspend_standby_mode +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_standby_mode. This holds the regulator operating mode + setting for this domain when the system is suspended to + standby, for regulators implementing suspend mode + configuration constraints. + +What: /sys/class/regulator/.../suspend_mem_state +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_mem_state. This holds the regulator operating state + when suspended to memory, for regulators implementing suspend + configuration constraints. + + This will be one of the same strings reported by + the "state" attribute. + +What: /sys/class/regulator/.../suspend_disk_state +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_disk_state. This holds the regulator operating state + when suspended to disk, for regulators implementing + suspend configuration constraints. + + This will be one of the same strings reported by + the "state" attribute. + +What: /sys/class/regulator/.../suspend_standby_state +Date: May 2008 +KernelVersion: 2.6.26 +Contact: Liam Girdwood +Description: + Some regulator directories will contain a field called + suspend_standby_state. This holds the regulator operating + state when suspended to standby, for regulators implementing + suspend configuration constraints. + + This will be one of the same strings reported by + the "state" attribute. + +What: /sys/class/regulator/.../bypass +Date: September 2012 +KernelVersion: 3.7 +Contact: Mark Brown +Description: + Some regulator directories will contain a field called + bypass. This indicates if the device is in bypass mode. + + This will be one of the following strings: + + - 'enabled' + - 'disabled' + - 'unknown' + + 'enabled' means the regulator is in bypass mode. + + 'disabled' means that the regulator is regulating. + + 'unknown' means software cannot determine the state, or + the reported state is invalid. + +What: /sys/class/regulator/.../under_voltage +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + under_voltage. This indicates if the device reports an + under-voltage fault (1) or not (0). + +What: /sys/class/regulator/.../over_current +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + over_current. This indicates if the device reports an + over-current fault (1) or not (0). + +What: /sys/class/regulator/.../regulation_out +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + regulation_out. This indicates if the device reports an + out-of-regulation fault (1) or not (0). + +What: /sys/class/regulator/.../fail +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + fail. This indicates if the device reports an output failure + (1) or not (0). + +What: /sys/class/regulator/.../over_temp +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + over_temp. This indicates if the device reports an + over-temperature fault (1) or not (0). + +What: /sys/class/regulator/.../under_voltage_warn +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + under_voltage_warn. This indicates if the device reports an + under-voltage warning (1) or not (0). + +What: /sys/class/regulator/.../over_current_warn +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + over_current_warn. This indicates if the device reports an + over-current warning (1) or not (0). + +What: /sys/class/regulator/.../over_voltage_warn +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + over_voltage_warn. This indicates if the device reports an + over-voltage warning (1) or not (0). + +What: /sys/class/regulator/.../over_temp_warn +Date: April 2022 +KernelVersion: 5.18 +Contact: Zev Weiss +Description: + Some regulator directories will contain a field called + over_temp_warn. This indicates if the device reports an + over-temperature warning (1) or not (0). diff --git a/Documentation/ABI/testing/sysfs-class-remoteproc b/Documentation/ABI/testing/sysfs-class-remoteproc new file mode 100644 index 000000000..0c9ee5509 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-remoteproc @@ -0,0 +1,104 @@ +What: /sys/class/remoteproc/.../firmware +Date: October 2016 +Contact: Matt Redfearn +Description: Remote processor firmware + + Reports the name of the firmware currently loaded to the + remote processor. + + To change the running firmware, ensure the remote processor is + stopped (using /sys/class/remoteproc/.../state) and write a new filename. + +What: /sys/class/remoteproc/.../state +Date: October 2016 +Contact: Matt Redfearn +Description: Remote processor state + + Reports the state of the remote processor, which will be one of: + + - "offline" + - "suspended" + - "running" + - "crashed" + - "invalid" + + "offline" means the remote processor is powered off. + + "suspended" means that the remote processor is suspended and + must be woken to receive messages. + + "running" is the normal state of an available remote processor + + "crashed" indicates that a problem/crash has been detected on + the remote processor. + + "invalid" is returned if the remote processor is in an + unknown state. + + Writing this file controls the state of the remote processor. + The following states can be written: + + - "start" + - "stop" + + Writing "start" will attempt to start the processor running the + firmware indicated by, or written to, + /sys/class/remoteproc/.../firmware. The remote processor should + transition to "running" state. + + Writing "stop" will attempt to halt the remote processor and + return it to the "offline" state. + +What: /sys/class/remoteproc/.../name +Date: August 2019 +KernelVersion: 5.4 +Contact: Suman Anna +Description: Remote processor name + + Reports the name of the remote processor. This can be used by + userspace in exactly identifying a remote processor and ease + up the usage in modifying the 'firmware' or 'state' files. + +What: /sys/class/remoteproc/.../coredump +Date: July 2020 +Contact: Bjorn Andersson , Ohad Ben-Cohen +Description: Remote processor coredump configuration + + Reports the coredump configuration of the remote processor, + which will be one of: + + "disabled" + "enabled" + "inline" + + "disabled" means no dump will be collected. + + "enabled" means when the remote processor's coredump is + collected it will be copied to a separate buffer and that + buffer is exposed to userspace. + + "inline" means when the remote processor's coredump is + collected userspace will directly read from the remote + processor's device memory. Extra buffer will not be used to + copy the dump. Also recovery process will not proceed until + all data is read by usersapce. + +What: /sys/class/remoteproc/.../recovery +Date: July 2020 +Contact: Bjorn Andersson , Ohad Ben-Cohen +Description: Remote processor recovery mechanism + + Reports the recovery mechanism of the remote processor, + which will be one of: + + "enabled" + "disabled" + + "enabled" means, the remote processor will be automatically + recovered whenever it crashes. Moreover, if the remote + processor crashes while recovery is disabled, it will + be automatically recovered too as soon as recovery is enabled. + + "disabled" means, a remote processor will remain in a crashed + state if it crashes. This is useful for debugging purposes; + without it, debugging a crash is substantially harder. diff --git a/Documentation/ABI/testing/sysfs-class-rnbd-client b/Documentation/ABI/testing/sysfs-class-rnbd-client new file mode 100644 index 000000000..0b5997ab3 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rnbd-client @@ -0,0 +1,133 @@ +What: /sys/class/rnbd-client +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Provide information about RNBD-client. + All sysfs files that are not read-only provide the usage information on read: + + Example:: + + # cat /sys/class/rnbd-client/ctl/map_device + + > Usage: echo "sessname= path=<[srcaddr,]dstaddr> + > [path=<[srcaddr,]dstaddr>] device_path= + > [access_mode=] > map_device + > + > addr ::= [ ip: | ip: | gid: ] + +What: /sys/class/rnbd-client/ctl/map_device +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Expected format is the following:: + + sessname= + path=<[srcaddr,]dstaddr> [path=<[srcaddr,]dstaddr> ...] + device_path= + [access_mode=] + + Where: + + sessname: + accepts a string not bigger than 256 chars, which identifies + a given session on the client and on the server. + I.e. "clt_hostname-srv_hostname" could be a natural choice. + + path: + describes a connection between the client and the server by + specifying destination and, when required, the source address. + The addresses are to be provided in the following format:: + + ip: + ip: + gid: + + for example:: + + path=ip:10.0.0.66 + + The single addr is treated as the destination. + The connection will be established to this server from any client IP address. + + :: + + path=ip:10.0.0.66,ip:10.0.1.66 + + First addr is the source address and the second is the destination. + + If multiple "path=" options are specified multiple connection + will be established and data will be sent according to + the selected multipath policy (see RTRS mp_policy sysfs entry description). + + device_path: + Path to the block device on the server side. Path is specified + relative to the directory on server side configured in the + 'dev_search_path' module parameter of the rnbd_server. + The rnbd_server prepends the received from client + with and tries to open the + / block device. On success, + a /dev/rnbd device file, a /sys/block/rnbd/ + directory and an entry in /sys/class/rnbd-client/ctl/devices + will be created. + + If 'dev_search_path' contains '%SESSNAME%', then each session can + have different devices namespace, e.g. server was configured with + the following parameter "dev_search_path=/run/rnbd-devs/%SESSNAME%", + client has this string "sessname=blya device_path=sda", then server + will try to open: /run/rnbd-devs/blya/sda. + + access_mode: + the access_mode parameter specifies if the device is to be + mapped as "ro" read-only or "rw" read-write. The server allows + a device to be exported in rw mode only once. The "migration" + access mode has to be specified if a second mapping in read-write + mode is desired. + + By default "rw" is used. + + nr_poll_queues + specifies the number of poll-mode queues. If the IO has HIPRI flag, + the block-layer will send the IO via the poll-mode queue. + For fast network and device the polling is faster than interrupt-base + IO handling because it saves time for context switching, switching to + another process, handling the interrupt and switching back to the + issuing process. + + Set -1 if you want to set it as the number of CPUs + By default rnbd client creates only irq-mode queues. + + NOTICE: MUST make a unique session for a device using the poll-mode queues. + + Exit Codes: + + If the device is already mapped it will fail with EEXIST. If the input + has an invalid format it will return EINVAL. If the device path cannot + be found on the server, it will fail with ENOENT. + + Finding device file after mapping + --------------------------------- + + After mapping, the device file can be found by: + o The symlink /sys/class/rnbd-client/ctl/devices/@ + points to /sys/block/. The last part of the symlink destination + is the same as the device name. By extracting the last part of the + path the path to the device /dev/ can be build. + + * /dev/block/$(cat /sys/class/rnbd-client/ctl/devices/@/dev) + + How to find the of the device is described on the next + section. + +What: /sys/class/rnbd-client/ctl/devices/ +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: For each device mapped on the client a new symbolic link is created as + /sys/class/rnbd-client/ctl/devices/@, which points + to the block device created by rnbd (/sys/block/rnbd/). + The of each device is created as follows: + + - If the 'device_path' provided during mapping contains slashes ("/"), + they are replaced by exclamation mark ("!") and used as as the + . Otherwise, the will be the same as the + "device_path" provided. diff --git a/Documentation/ABI/testing/sysfs-class-rnbd-server b/Documentation/ABI/testing/sysfs-class-rnbd-server new file mode 100644 index 000000000..6c5996cd7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rnbd-server @@ -0,0 +1,58 @@ +What: /sys/class/rnbd-server +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: provide information about RNBD-server. + +What: /sys/class/rnbd-server/ctl/ +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: When a client maps a device, a directory entry with the name of the + block device is created under /sys/class/rnbd-server/ctl/devices/. + +What: /sys/class/rnbd-server/ctl/devices//block_dev +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Is a symlink to the sysfs entry of the exported device. + + Example: + block_dev -> ../../../../class/block/ram0 + +What: /sys/class/rnbd-server/ctl/devices//sessions/ +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: For each client a particular device is exported to, following directory will be + created: + + /sys/class/rnbd-server/ctl/devices//sessions// + + When the device is unmapped by that client, the directory will be removed. + +What: /sys/class/rnbd-server/ctl/devices//sessions//read_only +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains '1' if device is mapped read-only, otherwise '0'. + +What: /sys/class/rnbd-server/ctl/devices//sessions//mapping_path +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains the relative device path provided by the user during mapping. + +What: /sys/class/rnbd-server/ctl/devices//sessions//access_mode +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains the device access mode: ro, rw or migration. + +What: /sys/class/rnbd-server/ctl/devices//sessions//force_close +Date: Nov 2020 +KernelVersion: 5.10 +Contact: Jack Wang Danil Kipnis +Description: Write "1" to the file to close the device on server side. Please + note that the client side device will not be closed, read or + write to the device will get -ENOTCONN. diff --git a/Documentation/ABI/testing/sysfs-class-rtc b/Documentation/ABI/testing/sysfs-class-rtc new file mode 100644 index 000000000..95984289a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rtc @@ -0,0 +1,91 @@ +What: /sys/class/rtc/ +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + The rtc/ class subdirectory belongs to the RTC subsystem. + +What: /sys/class/rtc/rtcX/ +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + The /sys/class/rtc/rtc{0,1,2,3,...} directories correspond + to each RTC device. + +What: /sys/class/rtc/rtcX/date +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + (RO) RTC-provided date in YYYY-MM-DD format + +What: /sys/class/rtc/rtcX/hctosys +Date: September 2009 +KernelVersion: 2.6.32 +Contact: linux-rtc@vger.kernel.org +Description: + (RO) 1 if the RTC provided the system time at boot via the + CONFIG_RTC_HCTOSYS kernel option, 0 otherwise + +What: /sys/class/rtc/rtcX/max_user_freq +Date: October 2007 +KernelVersion: 2.6.24 +Contact: linux-rtc@vger.kernel.org +Description: + (RW) The maximum interrupt rate an unprivileged user may request + from this RTC. + +What: /sys/class/rtc/rtcX/name +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + (RO) The name of the RTC corresponding to this sysfs directory + +What: /sys/class/rtc/rtcX/range +Date: January 2018 +KernelVersion: 4.16 +Contact: linux-rtc@vger.kernel.org +Description: + Valid time range for the RTC, as seconds from epoch, formatted + as [min, max] + +What: /sys/class/rtc/rtcX/since_epoch +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + (RO) RTC-provided time as the number of seconds since the epoch + +What: /sys/class/rtc/rtcX/time +Date: March 2006 +KernelVersion: 2.6.17 +Contact: linux-rtc@vger.kernel.org +Description: + (RO) RTC-provided time in 24-hour notation (hh:mm:ss) + +What: /sys/class/rtc/rtcX/offset +Date: February 2016 +KernelVersion: 4.6 +Contact: linux-rtc@vger.kernel.org +Description: + (RW) The amount which the rtc clock has been adjusted in + firmware. Visible only if the driver supports clock offset + adjustment. The unit is parts per billion, i.e. The number of + clock ticks which are added to or removed from the rtc's base + clock per billion ticks. A positive value makes a day pass more + slowly, longer, and a negative value makes a day pass more + quickly. + +What: /sys/class/rtc/rtcX/wakealarm +Date: February 2007 +KernelVersion: 2.6.20 +Contact: linux-rtc@vger.kernel.org +Description: + (RW) The time at which the clock will generate a system wakeup + event. This is a one shot wakeup event, so must be reset after + wake if a daily wakeup is required. Format is seconds since the + epoch by default, or if there's a leading +, seconds in the + future, or if there is a leading +=, seconds ahead of the + current alarm. diff --git a/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration b/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration new file mode 100644 index 000000000..ee8ed6494 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration @@ -0,0 +1,14 @@ +What: /sys/class/rtc/rtc0/device/rtc_calibration +Date: Oct 2011 +KernelVersion: 3.0 +Contact: Mark Godfrey +Description: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock + The rtc_calibration attribute allows the userspace to + calibrate the AB8500.s 32KHz Real Time Clock. + Every 60 seconds the AB8500 will correct the RTC's value + by adding to it the value of this attribute. + + The range of the attribute is -127 to +127 in units of + 30.5 micro-seconds (half-parts-per-million of the 32KHz clock) +Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration + daemon uses this interface. diff --git a/Documentation/ABI/testing/sysfs-class-rtrs-client b/Documentation/ABI/testing/sysfs-class-rtrs-client new file mode 100644 index 000000000..fecc59d1b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rtrs-client @@ -0,0 +1,146 @@ +What: /sys/class/rtrs-client +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: When a user of RTRS API creates a new session, a directory entry with + the name of that session is created under /sys/class/rtrs-client// + +What: /sys/class/rtrs-client//add_path +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RW, adds a new path (connection) to an existing session. Expected format is the + following:: + + <[source addr,]destination addr> + *addr ::= [ ip: | gid: ] + +What: /sys/class/rtrs-client//max_reconnect_attempts +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Maximum number reconnect attempts the client should make before giving up + after connection breaks unexpectedly. + +What: /sys/class/rtrs-client//mp_policy +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Multipath policy specifies which path should be selected on each IO: + + round-robin (0): + select path in per CPU round-robin manner. + + min-inflight (1): + select path with minimum inflights. + + min-latency (2): + select path with minimum latency. + +What: /sys/class/rtrs-client//paths/ +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Each path belonging to a given session is listed here by its source and + destination address. When a new path is added to a session by writing to + the "add_path" entry, a directory is created. + +What: /sys/class/rtrs-client//paths//state +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains "connected" if the session is connected to the peer and fully + functional. Otherwise the file contains "disconnected" + +What: /sys/class/rtrs-client//paths//reconnect +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Write "1" to the file in order to reconnect the path. + Operation is blocking and returns 0 if reconnect was successful. + +What: /sys/class/rtrs-client//paths//disconnect +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Write "1" to the file in order to disconnect the path. + Operation blocks until RTRS path is disconnected. + +What: /sys/class/rtrs-client//paths//remove_path +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Write "1" to the file in order to disconnected and remove the path + from the session. Operation blocks until the path is disconnected + and removed from the session. + +What: /sys/class/rtrs-client//paths//hca_name +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the name of HCA the connection established on. + +What: /sys/class/rtrs-client//paths//hca_port +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the port number of active port traffic is going through. + +What: /sys/class/rtrs-client//paths//src_addr +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the source address of the path + +What: /sys/class/rtrs-client//paths//dst_addr +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the destination address of the path + +What: /sys/class/rtrs-client//paths//cur_latency +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the latency time calculated by the heart-beat messages. + Whenever the client sends heart-beat message, it checks the time gap + between sending the heart-beat message and receiving the ACK. + This value can be changed regularly. + +What: /sys/class/rtrs-client//paths//stats/reset_all +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RW, Read will return usage help, write 0 will clear all the statistics. + +What: /sys/class/rtrs-client//paths//stats/cpu_migration +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RTRS expects that each HCA IRQ is pinned to a separate CPU. If it's + not the case, the processing of an I/O response could be processed on a + different CPU than where it was originally submitted. This file shows + how many interrupts where generated on a non expected CPU. + + "from:" + is the CPU on which the IRQ was expected, but not generated. + "to:" + is the CPU on which the IRQ was generated, but not expected. + +What: /sys/class/rtrs-client//paths//stats/reconnects +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains 2 unsigned int values, the first one records number of successful + reconnects in the path lifetime, the second one records number of failed + reconnects in the path lifetime. + +What: /sys/class/rtrs-client//paths//stats/rdma +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains statistics regarding rdma operations and inflight operations. + The output consists of 6 values:: + + \ + diff --git a/Documentation/ABI/testing/sysfs-class-rtrs-server b/Documentation/ABI/testing/sysfs-class-rtrs-server new file mode 100644 index 000000000..b08601d80 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-rtrs-server @@ -0,0 +1,53 @@ +What: /sys/class/rtrs-server +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: When a user of RTRS API creates a new session on a client side, a + directory entry with the name of that session is created in here. + +What: /sys/class/rtrs-server//paths/ +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: When new path is created by writing to "add_path" entry on client side, + a directory entry named as @ is created + on server. + +What: /sys/class/rtrs-server//paths//disconnect +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: When "1" is written to the file, the RTRS session is being disconnected. + Operations is non-blocking and returns control immediately to the caller. + +What: /sys/class/rtrs-server//paths//hca_name +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the name of HCA the connection established on. + +What: /sys/class/rtrs-server//paths//hca_port +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the port number of active port traffic is going through. + +What: /sys/class/rtrs-server//paths//src_addr +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the source address of the path + +What: /sys/class/rtrs-server//paths//dst_addr +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: RO, Contains the destination address of the path + +What: /sys/class/rtrs-server//paths//stats/rdma +Date: Feb 2020 +KernelVersion: 5.7 +Contact: Jack Wang Danil Kipnis +Description: Contains statistics regarding rdma operations and inflight operations. + The output consists of 5 values: + diff --git a/Documentation/ABI/testing/sysfs-class-scsi_host b/Documentation/ABI/testing/sysfs-class-scsi_host new file mode 100644 index 000000000..7c98d8f43 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-scsi_host @@ -0,0 +1,119 @@ +What: /sys/class/scsi_host/hostX/isci_id +Date: June 2011 +Contact: Dave Jiang +Description: + This file contains the enumerated host ID for the Intel + SCU controller. The Intel(R) C600 Series Chipset SATA/SAS + Storage Control Unit embeds up to two 4-port controllers in + a single PCI device. The controllers are enumerated in order + which usually means the lowest number scsi_host corresponds + with the first controller, but this association is not + guaranteed. The 'isci_id' attribute unambiguously identifies + the controller index: '0' for the first controller, + '1' for the second. + +What: /sys/class/scsi_host/hostX/acciopath_status +Date: November 2013 +Contact: Stephen M. Cameron +Description: This file contains the current status of the "SSD Smart Path" + feature of HP Smart Array RAID controllers using the hpsa + driver. SSD Smart Path, when enabled permits the driver to + send i/o requests directly to physical devices that are part + of a logical drive, bypassing the controllers firmware RAID + stack for a performance advantage when possible. A value of + '1' indicates the feature is enabled, and the controller may + use the direct i/o path to physical devices. A value of zero + means the feature is disabled and the controller may not use + the direct i/o path to physical devices. This setting is + controller wide, affecting all configured logical drives on the + controller. This file is readable and writable. + +What: /sys/class/scsi_host/hostX/link_power_management_policy +Date: Oct, 2007 +KernelVersion: v2.6.24 +Contact: linux-ide@vger.kernel.org +Description: + (RW) This parameter allows the user to read and set the link + (interface) power management. + + There are four possible options: + + min_power: Tell the controller to try to make the link use the + least possible power when possible. This may sacrifice some + performance due to increased latency when coming out of lower + power states. + + max_performance: Generally, this means no power management. + Tell the controller to have performance be a priority over power + management. + + medium_power: Tell the controller to enter a lower power state + when possible, but do not enter the lowest power state, thus + improving latency over min_power setting. + + med_power_with_dipm: Identical to the existing medium_power + setting except that it enables dipm (device initiated power + management) on top, which makes it match the Windows IRST (Intel + Rapid Storage Technology) driver settings. This setting is also + close to min_power, except that: + + a) It does not use host-initiated slumber mode, but it does + allow device-initiated slumber + b) It does not enable low power device sleep mode (DevSlp). + +What: /sys/class/scsi_host/hostX/em_message +What: /sys/class/scsi_host/hostX/em_message_type +Date: Jun, 2008 +KernelVersion: v2.6.27 +Contact: linux-ide@vger.kernel.org +Description: + em_message: (RW) Enclosure management support. For the LED + protocol, writes and reads correspond to the LED message format + as defined in the AHCI spec. + + The user must turn sw_activity (under `/sys/block/*/device/`) + OFF it they wish to control the activity LED via the em_message + file. + + em_message_type: (RO) Displays the current enclosure management + protocol that is being used by the driver (for eg. LED, SAF-TE, + SES-2, SGPIO etc). + +What: /sys/class/scsi_host/hostX/ahci_port_cmd +What: /sys/class/scsi_host/hostX/ahci_host_caps +What: /sys/class/scsi_host/hostX/ahci_host_cap2 +Date: Mar, 2010 +KernelVersion: v2.6.35 +Contact: linux-ide@vger.kernel.org +Description: + [to be documented] + +What: /sys/class/scsi_host/hostX/ahci_host_version +Date: Mar, 2010 +KernelVersion: v2.6.35 +Contact: linux-ide@vger.kernel.org +Description: + (RO) Display the version of the AHCI spec implemented by the + host. + +What: /sys/class/scsi_host/hostX/em_buffer +Date: Apr, 2010 +KernelVersion: v2.6.35 +Contact: linux-ide@vger.kernel.org +Description: + (RW) Allows access to AHCI EM (enclosure management) buffer + directly if the host supports EM. + + For eg. the AHCI driver supports SGPIO EM messages but the + SATA/AHCI specs do not define the SGPIO message format of the EM + buffer. Different hardware(HW) vendors may have different + definitions. With the em_buffer attribute, this issue can be + solved by allowing HW vendors to provide userland drivers and + tools for their SGPIO initiators. + +What: /sys/class/scsi_host/hostX/em_message_supported +Date: Oct, 2009 +KernelVersion: v2.6.39 +Contact: linux-ide@vger.kernel.org +Description: + (RO) Displays supported enclosure management message types. diff --git a/Documentation/ABI/testing/sysfs-class-scsi_tape b/Documentation/ABI/testing/sysfs-class-scsi_tape new file mode 100644 index 000000000..9be398b87 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-scsi_tape @@ -0,0 +1,109 @@ +What: /sys/class/scsi_tape/*/stats/in_flight +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Show the number of I/Os currently in-flight between the st + module and the SCSI mid-layer. +Users: + + +What: /sys/class/scsi_tape/*/stats/io_ns +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total amount of time spent waiting for all I/O + to and from the tape drive to complete. This includes all + reads, writes, and other SCSI commands issued to the tape + drive. An example of other SCSI commands would be tape + movement such as a rewind when a rewind tape device is + closed. This item is measured in nanoseconds. + + To determine the amount of time spent waiting for other I/O + to complete subtract read_ns and write_ns from this value. +Users: + + +What: /sys/class/scsi_tape/*/stats/other_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + The number of I/O requests issued to the tape drive other + than SCSI read/write requests. +Users: + + +What: /sys/class/scsi_tape/*/stats/read_byte_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total number of bytes requested from the tape drive. + This value is presented in bytes because tape drives support + variable length block sizes. +Users: + + +What: /sys/class/scsi_tape/*/stats/read_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total number of read requests issued to the tape + drive. +Users: + + +What: /sys/class/scsi_tape/*/stats/read_ns +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total amount of time in nanoseconds waiting for + read I/O requests to complete. +Users: + + +What: /sys/class/scsi_tape/*/stats/write_byte_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total number of bytes written to the tape drive. + This value is presented in bytes because tape drives support + variable length block sizes. +Users: + + +What: /sys/class/scsi_tape/*/stats/write_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total number of write requests issued to the tape + drive. +Users: + + +What: /sys/class/scsi_tape/*/stats/write_ms +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the total amount of time in nanoseconds waiting for + write I/O requests to complete. +Users: + + +What: /sys/class/scsi_tape/*/stats/resid_cnt +Date: Apr 2015 +KernelVersion: 4.2 +Contact: Shane Seymour +Description: + Shows the number of times we found that a residual >0 + was found when the SCSI midlayer indicated that there was + an error. For reads this may be a case of someone issuing + reads greater than the block size. +Users: diff --git a/Documentation/ABI/testing/sysfs-class-spi-eeprom b/Documentation/ABI/testing/sysfs-class-spi-eeprom new file mode 100644 index 000000000..1ff757982 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-spi-eeprom @@ -0,0 +1,19 @@ +What: /sys/class/spi_master/spi/spi./fram +Date: June 2021 +KernelVersion: 5.14 +Contact: Jiri Prchal +Description: + Contains the FRAM binary data. Same as EEPROM, just another file + name to indicate that it employs ferroelectric process. + It performs write operations at bus speed - no write delays. + +What: /sys/class/spi_master/spi/spi./sernum +Date: May 2021 +KernelVersion: 5.14 +Contact: Jiri Prchal +Description: + Contains the serial number of the Cypress FRAM (FM25VN) if it is + present. It will be displayed as a 8 byte hex string, as read + from the device. + + This is a read-only attribute. diff --git a/Documentation/ABI/testing/sysfs-class-stm b/Documentation/ABI/testing/sysfs-class-stm new file mode 100644 index 000000000..77ed3da0f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-stm @@ -0,0 +1,24 @@ +What: /sys/class/stm//masters +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: + Shows first and last available to software master numbers on + this STM device. + +What: /sys/class/stm//channels +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: + Shows the number of channels per master on this STM device. + +What: /sys/class/stm//hw_override +Date: March 2016 +KernelVersion: 4.7 +Contact: Alexander Shishkin +Description: + Reads as 0 if master numbers in the STP stream produced by + this stm device will match the master numbers assigned by + the software or 1 if the stm hardware overrides software + assigned masters. diff --git a/Documentation/ABI/testing/sysfs-class-stm_source b/Documentation/ABI/testing/sysfs-class-stm_source new file mode 100644 index 000000000..57b8dd39b --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-stm_source @@ -0,0 +1,11 @@ +What: /sys/class/stm_source//stm_source_link +Date: June 2015 +KernelVersion: 4.3 +Contact: Alexander Shishkin +Description: + stm_source device linkage to stm device, where its tracing data + is directed. Reads return an existing connection or "" if + this stm_source is not connected to any stm device yet. + Write an existing (registered) stm device's name here to + connect that device. If a device is already connected to this + stm_source, it will first be disconnected. diff --git a/Documentation/ABI/testing/sysfs-class-switchtec b/Documentation/ABI/testing/sysfs-class-switchtec new file mode 100644 index 000000000..76c7a661a --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-switchtec @@ -0,0 +1,96 @@ +switchtec - Microsemi Switchtec PCI Switch Management Endpoint + +For details on this subsystem look at Documentation/driver-api/switchtec.rst. + +What: /sys/class/switchtec +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: The switchtec class subsystem folder. + Each registered switchtec driver is represented by a switchtecX + subfolder (X being an integer >= 0). + + +What: /sys/class/switchtec/switchtec[0-9]+/component_id +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Component identifier as stored in the hardware (eg. PM8543) + (read only) +Values: arbitrary string. + + +What: /sys/class/switchtec/switchtec[0-9]+/component_revision +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Component revision stored in the hardware (read only) +Values: integer. + + +What: /sys/class/switchtec/switchtec[0-9]+/component_vendor +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Component vendor as stored in the hardware (eg. MICROSEM) + (read only) +Values: arbitrary string. + + +What: /sys/class/switchtec/switchtec[0-9]+/device_version +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Device version as stored in the hardware (read only) +Values: integer. + + +What: /sys/class/switchtec/switchtec[0-9]+/fw_version +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Currently running firmware version (read only) +Values: integer (in hexadecimal). + + +What: /sys/class/switchtec/switchtec[0-9]+/partition +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Partition number for this device in the switch (read only) +Values: integer. + + +What: /sys/class/switchtec/switchtec[0-9]+/partition_count +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Total number of partitions in the switch (read only) +Values: integer. + + +What: /sys/class/switchtec/switchtec[0-9]+/product_id +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Product identifier as stored in the hardware (eg. PSX 48XG3) + (read only) +Values: arbitrary string. + + +What: /sys/class/switchtec/switchtec[0-9]+/product_revision +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Product revision stored in the hardware (eg. RevB) + (read only) +Values: arbitrary string. + + +What: /sys/class/switchtec/switchtec[0-9]+/product_vendor +Date: 05-Jan-2017 +KernelVersion: v4.11 +Contact: Logan Gunthorpe +Description: Product vendor as stored in the hardware (eg. MICROSEM) + (read only) +Values: arbitrary string. diff --git a/Documentation/ABI/testing/sysfs-class-thermal b/Documentation/ABI/testing/sysfs-class-thermal new file mode 100644 index 000000000..8eee37982 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-thermal @@ -0,0 +1,259 @@ +What: /sys/class/thermal/thermal_zoneX/type +Description: + Strings which represent the thermal zone type. + This is given by thermal zone driver as part of registration. + E.g: "acpitz" indicates it's an ACPI thermal device. + In order to keep it consistent with hwmon sys attribute; this + shouldbe a short, lowercase string, not containing spaces nor + dashes. + + RO, Required + +What: /sys/class/thermal/thermal_zoneX/temp +Description: + Current temperature as reported by thermal zone (sensor). + + Unit: millidegree Celsius + + RO, Required + +What: /sys/class/thermal/thermal_zoneX/mode +Description: + One of the predefined values in [enabled, disabled]. + This file gives information about the algorithm that is + currently managing the thermal zone. It can be either default + kernel based algorithm or user space application. + + enabled + enable Kernel Thermal management. + disabled + Preventing kernel thermal zone driver actions upon + trip points so that user application can take full + charge of the thermal management. + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/policy +Description: + One of the various thermal governors used for a particular zone. + + RW, Required + +What: /sys/class/thermal/thermal_zoneX/available_policies +Description: + Available thermal governors which can be used for a + particular zone. + + RO, Required + +What: /sys/class/thermal/thermal_zoneX/trip_point_Y_temp +Description: + The temperature above which trip point will be fired. + + Unit: millidegree Celsius + + RO, Optional + +What: /sys/class/thermal/thermal_zoneX/trip_point_Y_type +Description: + Strings which indicate the type of the trip point. + + E.g. it can be one of critical, hot, passive, `active[0-*]` + for ACPI thermal zone. + + RO, Optional + +What: /sys/class/thermal/thermal_zoneX/trip_point_Y_hyst +Description: + The hysteresis value for a trip point, represented as an + integer. + + Unit: Celsius + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/cdevY +Description: + Sysfs link to the thermal cooling device node where the sys I/F + for cooling device throttling control represents. + + RO, Optional + +What: /sys/class/thermal/thermal_zoneX/cdevY_trip_point +Description: + The trip point in this thermal zone which `cdev[0-*]` is + associated with; -1 means the cooling device is not + associated with any trip point. + + RO, Optional + +What: /sys/class/thermal/thermal_zoneX/cdevY_weight +Description: + The influence of `cdev[0-*]` in this thermal zone. This value + is relative to the rest of cooling devices in the thermal + zone. For example, if a cooling device has a weight double + than that of other, it's twice as effective in cooling the + thermal zone. + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/emul_temp +Description: + Interface to set the emulated temperature method in thermal zone + (sensor). After setting this temperature, the thermal zone may + pass this temperature to platform emulation function if + registered or cache it locally. This is useful in debugging + different temperature threshold and its associated cooling + action. This is write only node and writing 0 on this node + should disable emulation. + + Unit: millidegree Celsius + + WO, Optional + + WARNING: + Be careful while enabling this option on production systems, + because userland can easily disable the thermal policy by simply + flooding this sysfs node with low temperature values. + + +What: /sys/class/thermal/thermal_zoneX/k_d +Description: + The derivative term of the power allocator governor's PID + controller. For more information see + Documentation/driver-api/thermal/power_allocator.rst + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/k_i +Description: + The integral term of the power allocator governor's PID + controller. This term allows the PID controller to compensate + for long term drift. For more information see + Documentation/driver-api/thermal/power_allocator.rst + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/k_po +Description: + The proportional term of the power allocator governor's PID + controller during temperature overshoot. Temperature overshoot + is when the current temperature is above the "desired + temperature" trip point. For more information see + Documentation/driver-api/thermal/power_allocator.rst + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/k_pu +Description: + The proportional term of the power allocator governor's PID + controller during temperature undershoot. Temperature undershoot + is when the current temperature is below the "desired + temperature" trip point. For more information see + Documentation/driver-api/thermal/power_allocator.rst + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/integral_cutoff +Description: + Temperature offset from the desired temperature trip point + above which the integral term of the power allocator + governor's PID controller starts accumulating errors. For + example, if integral_cutoff is 0, then the integral term only + accumulates error when temperature is above the desired + temperature trip point. For more information see + Documentation/driver-api/thermal/power_allocator.rst + + Unit: millidegree Celsius + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/slope +Description: + The slope constant used in a linear extrapolation model + to determine a hotspot temperature based off the sensor's + raw readings. It is up to the device driver to determine + the usage of these values. + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/offset +Description: + The offset constant used in a linear extrapolation model + to determine a hotspot temperature based off the sensor's + raw readings. It is up to the device driver to determine + the usage of these values. + + RW, Optional + +What: /sys/class/thermal/thermal_zoneX/sustainable_power +Description: + An estimate of the sustained power that can be dissipated by + the thermal zone. Used by the power allocator governor. For + more information see + Documentation/driver-api/thermal/power_allocator.rst + + Unit: milliwatts + + RW, Optional + +What: /sys/class/thermal/cooling_deviceX/type +Description: + String which represents the type of device, e.g: + + - for generic ACPI: should be "Fan", "Processor" or "LCD" + - for memory controller device on intel_menlow platform: + should be "Memory controller". + + RO, Required + +What: /sys/class/thermal/cooling_deviceX/max_state +Description: + The maximum permissible cooling state of this cooling device. + + RO, Required + +What: /sys/class/thermal/cooling_deviceX/cur_state +Description: + The current cooling state of this cooling device. + The value can any integer numbers between 0 and max_state: + + - cur_state == 0 means no cooling + - cur_state == max_state means the maximum cooling. + + RW, Required + +What: /sys/class/thermal/cooling_deviceX/stats/reset +Description: + Writing any value resets the cooling device's statistics. + + WO, Required + +What: /sys/class/thermal/cooling_deviceX/stats/time_in_state_ms: +Description: + The amount of time spent by the cooling device in various + cooling states. The output will have "