Documentation: Fix typos
Subsystems (162)
cover Documentation: Fix typos
From: Bjorn Helgaas <[email protected]>
Fix typos in Documentation. I split these into:
Documentation/ABI/
Documentation/devicetree/bindings/
<everything else>
If it would be better split more or differently, I'm happy to do that. These are strictly typo fixes, no clarification or rewording.
Bjorn Helgaas (3):
Documentation/ABI: Fix typos
dt-bindings: Fix typos
Documentation: Fix typos
Documentation/ABI/stable/sysfs-block | 2 +- .../ABI/stable/sysfs-class-infiniband | 2 +- .../ABI/stable/sysfs-platform-wmi-bmof | 2 +- .../ABI/testing/debugfs-driver-habanalabs | 2 +- Documentation/ABI/testing/procfs-diskstats | 2 +- Documentation/ABI/testing/sysfs-bus-coreboot | 2 +- .../testing/sysfs-bus-coresight-devices-etm3x | 8 +++--- .../testing/sysfs-bus-coresight-devices-etm4x | 2 +- .../sysfs-bus-event_source-devices-events | 4 +-- .../ABI/testing/sysfs-bus-fsi-devices-sbefifo | 4 +-- .../ABI/testing/sysfs-bus-i2c-devices-fsa9480 | 2 +- Documentation/ABI/testing/sysfs-bus-nfit | 2 +- Documentation/ABI/testing/sysfs-bus-papr-pmem | 2 +- Documentation/ABI/testing/sysfs-bus-umc | 2 +- Documentation/ABI/testing/sysfs-class | 2 +- Documentation/ABI/testing/sysfs-class-cxl | 4 +-- Documentation/ABI/testing/sysfs-class-mtd | 2 +- Documentation/ABI/testing/sysfs-class-net | 2 +- .../ABI/testing/sysfs-class-net-queues | 2 +- .../ABI/testing/sysfs-class-power-wilco | 2 +- .../ABI/testing/sysfs-class-remoteproc | 2 +- Documentation/ABI/testing/sysfs-class-thermal | 2 +- .../ABI/testing/sysfs-class-uwb_rc-wusbhc | 2 +- .../ABI/testing/sysfs-devices-online | 2 +- .../ABI/testing/sysfs-driver-ge-achc | 2 +- .../ABI/testing/sysfs-driver-tegra-fuse | 2 +- Documentation/ABI/testing/sysfs-firmware-acpi | 2 +- .../ABI/testing/sysfs-firmware-sgi_uv | 4 +-- Documentation/ABI/testing/sysfs-fs-f2fs | 8 +++--- .../ABI/testing/sysfs-kernel-mm-damon | 2 +- .../ABI/testing/sysfs-memory-page-offline | 4 +-- .../ABI/testing/sysfs-platform-dell-laptop | 2 +- .../ABI/testing/sysfs-platform-dfl-fme | 2 +- Documentation/ABI/testing/sysfs-platform-kim | 2 +- .../ABI/testing/sysfs-platform-sst-atom | 2 +- .../admin-guide/kernel-parameters.txt | 2 +- Documentation/admin-guide/mm/damon/usage.rst | 4 +-- .../admin-guide/mm/numa_memory_policy.rst | 2 +- Documentation/admin-guide/module-signing.rst | 2 +- Documentation/admin-guide/xfs.rst | 2 +- Documentation/arch/arm/arm.rst | 2 +- Documentation/arch/arm/ixp4xx.rst | 4 +-- Documentation/arch/arm/sunxi/clocks.rst | 2 +- Documentation/arch/arm/swp_emulation.rst | 2 +- Documentation/arch/arm/tcm.rst | 2 +- Documentation/arch/arm/vlocks.rst | 2 +- .../arch/arm64/acpi_object_usage.rst | 2 +- Documentation/arch/arm64/arm-acpi.rst | 2 +- Documentation/arch/openrisc/openrisc_port.rst | 4 +-- Documentation/arch/x86/boot.rst | 2 +- Documentation/arch/x86/buslock.rst | 2 +- Documentation/arch/x86/mds.rst | 2 +- Documentation/arch/x86/sgx.rst | 2 +- Documentation/arch/xtensa/atomctl.rst | 2 +- Documentation/block/data-integrity.rst | 2 +- Documentation/block/ublk.rst | 2 +- Documentation/bpf/cpumasks.rst | 2 +- Documentation/bpf/graph_ds_impl.rst | 2 +- .../devicetree/bindings/arm/fsl.yaml | 4 +-- .../arm/marvell/cp110-system-controller.txt | 8 +++--- .../bindings/arm/mediatek/mediatek,mipi0a.txt | 2 +- .../arm/mediatek/mediatek,vcodecsys.txt | 2 +- .../devicetree/bindings/arm/sunxi.yaml | 4 +-- .../devicetree/bindings/ata/pata-common.yaml | 2 +- .../bindings/bus/brcm,gisb-arb.yaml | 2 +- .../bus/nvidia,tegra210-aconnect.yaml | 4 +-- .../clock/allwinner,sun4i-a10-osc-clk.yaml | 2 +- .../bindings/clock/alphascale,acc.txt | 4 +-- .../bindings/clock/keystone-pll.txt | 2 +- .../devicetree/bindings/clock/lpc1850-ccu.txt | 2 +- .../bindings/clock/lpc1850-creg-clk.txt | 4 +-- .../bindings/clock/maxim,max9485.txt | 2 +- .../bindings/clock/qcom,gcc-sm8450.yaml | 2 +- .../bindings/clock/qcom,kpss-acc-v1.yaml | 2 +- .../bindings/clock/sprd,sc9863a-clk.yaml | 2 +- .../devicetree/bindings/clock/ti/mux.txt | 2 +- .../devicetree/bindings/clock/vf610-clock.txt | 2 +- .../bindings/clock/xlnx,zynqmp-clk.txt | 2 +- .../bindings/connector/usb-connector.yaml | 2 +- .../devfreq/event/samsung,exynos-ppmu.yaml | 2 +- .../bindings/display/atmel/hlcdc-dc.txt | 2 +- .../display/bridge/snps,dw-mipi-dsi.yaml | 2 +- .../bindings/display/cirrus,clps711x-fb.txt | 2 +- .../bindings/display/msm/qcom,mdss.yaml | 2 +- .../display/panel/olimex,lcd-olinuxino.yaml | 2 +- .../bindings/display/panel/panel-common.yaml | 2 +- .../display/tegra/nvidia,tegra124-sor.yaml | 2 +- .../devicetree/bindings/dma/ingenic,dma.yaml | 2 +- .../bindings/dma/nvidia,tegra20-apbdma.txt | 2 +- .../devicetree/bindings/dma/qcom,bam-dma.yaml | 2 +- .../bindings/dma/stericsson,dma40.yaml | 2 +- .../devicetree/bindings/fpga/fpga-region.txt | 4 +-- .../bindings/gpio/gpio-xgene-sb.txt | 2 +- .../bindings/gpio/snps,dw-apb-gpio.yaml | 2 +- .../bindings/gpio/ti,omap-gpio.yaml | 4 +-- .../bindings/hwmon/adi,adm1177.yaml | 2 +- .../bindings/hwmon/adi,axi-fan-control.yaml | 2 +- .../bindings/hwmon/adi,ltc2992.yaml | 2 +- .../bindings/hwmon/aspeed-pwm-tacho.txt | 2 +- .../devicetree/bindings/hwmon/lm87.txt | 2 +- .../devicetree/bindings/hwmon/ltq-cputemp.txt | 2 +- .../bindings/hwmon/moortec,mr75203.yaml | 2 +- .../bindings/hwmon/npcm750-pwm-fan.txt | 2 +- .../bindings/hwmon/sensirion,shtc1.yaml | 2 +- .../devicetree/bindings/hwmon/ti,tmp513.yaml | 2 +- .../bindings/hwmon/ti,tps23861.yaml | 2 +- .../devicetree/bindings/i2c/i2c-sprd.txt | 2 +- .../bindings/iio/adc/xlnx,zynqmp-ams.yaml | 2 +- .../bindings/iio/cdc/adi,ad7150.yaml | 2 +- .../devicetree/bindings/iio/common.yaml | 2 +- .../bindings/iio/frequency/adi,admv1014.yaml | 2 +- .../bindings/iio/humidity/ti,hdc2010.yaml | 2 +- .../iio/pressure/honeywell,mprls0025pa.yaml | 2 +- .../bindings/iio/proximity/ams,as3935.yaml | 2 +- .../bindings/iio/st,st-sensors.yaml | 2 +- .../bindings/input/rmi4/rmi_2d_sensor.txt | 4 +-- .../bindings/input/touchscreen/stmpe.txt | 2 +- .../bindings/input/touchscreen/tsc2007.txt | 2 +- .../interrupt-controller/arm,gic-v3.yaml | 2 +- .../brcm,bcm2835-armctrl-ic.txt | 2 +- .../brcm,bcm7120-l2-intc.yaml | 2 +- .../backlight/mediatek,mt6370-backlight.yaml | 2 +- .../devicetree/bindings/leds/leds-lp55xx.yaml | 4 +-- .../bindings/leds/leds-qcom-lpg.yaml | 2 +- .../mailbox/brcm,iproc-flexrm-mbox.txt | 2 +- .../bindings/mailbox/ti,omap-mailbox.yaml | 2 +- .../bindings/media/i2c/toshiba,tc358746.yaml | 2 +- .../devicetree/bindings/media/i2c/tvp5150.txt | 2 +- .../media/mediatek,vcodec-subdev-decoder.yaml | 2 +- .../memory-controllers/mediatek,smi-larb.yaml | 2 +- .../rockchip,rk3399-dmc.yaml | 4 +-- .../xlnx,zynq-ddrc-a05.yaml | 2 +- .../devicetree/bindings/mfd/aspeed-lpc.yaml | 2 +- .../bindings/mfd/rohm,bd9576-pmic.yaml | 4 +-- .../bindings/mfd/stericsson,ab8500.yaml | 16 ++++++------ .../bindings/mfd/stericsson,db8500-prcmu.yaml | 2 +- .../devicetree/bindings/mmc/pxa-mmc.txt | 2 +- .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 2 +- .../bindings/net/brcm,bcm7445-switch-v4.0.txt | 2 +- .../devicetree/bindings/net/can/cc770.txt | 2 +- .../devicetree/bindings/net/dsa/brcm,sf2.yaml | 2 +- .../devicetree/bindings/net/ethernet-phy.yaml | 2 +- .../bindings/net/mediatek-dwmac.yaml | 2 +- .../bindings/net/microchip,lan95xx.yaml | 2 +- .../bindings/net/nfc/marvell,nci.yaml | 4 +-- .../devicetree/bindings/net/samsung-sxgbe.txt | 4 +-- .../bindings/net/snps,dwc-qos-ethernet.txt | 2 +- .../devicetree/bindings/net/sti-dwmac.txt | 2 +- .../bindings/net/xilinx_gmii2rgmii.txt | 2 +- .../devicetree/bindings/nios2/nios2.txt | 2 +- .../nvmem/layouts/onie,tlv-layout.yaml | 2 +- .../bindings/phy/phy-hisi-inno-usb2.txt | 2 +- .../bindings/phy/pistachio-usb-phy.txt | 2 +- .../bindings/phy/pxa1928-usb-phy.txt | 2 +- .../bindings/phy/rockchip-inno-csi-dphy.yaml | 2 +- .../bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- .../devicetree/bindings/phy/ti-phy.txt | 2 +- .../pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 2 +- .../bindings/pinctrl/canaan,k210-fpioa.yaml | 2 +- .../pinctrl/mediatek,mt6779-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt6795-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt7981-pinctrl.yaml | 4 +-- .../pinctrl/mediatek,mt7986-pinctrl.yaml | 4 +-- .../pinctrl/mediatek,mt8183-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt8365-pinctrl.yaml | 2 +- .../bindings/pinctrl/pinctrl-max77620.txt | 2 +- .../bindings/pinctrl/pinctrl-rk805.txt | 2 +- .../bindings/pinctrl/sprd,pinctrl.txt | 2 +- .../devicetree/bindings/pmem/pmem-region.txt | 4 +-- .../bindings/power/renesas,sysc-rmobile.yaml | 2 +- .../power/supply/sbs,sbs-manager.yaml | 2 +- .../devicetree/bindings/powerpc/fsl/cpus.txt | 2 +- .../devicetree/bindings/powerpc/fsl/dcsr.txt | 4 +-- .../bindings/powerpc/fsl/raideng.txt | 2 +- .../bindings/powerpc/nintendo/gamecube.txt | 2 +- .../bindings/powerpc/nintendo/wii.txt | 2 +- .../bindings/pwm/snps,dw-apb-timers-pwm2.yaml | 2 +- .../bindings/regulator/regulator-max77620.txt | 2 +- .../bindings/regulator/regulator.yaml | 8 +++--- .../regulator/richtek,rt5190a-regulator.yaml | 2 +- .../devicetree/bindings/regulator/vctrl.txt | 2 +- .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 2 +- .../bindings/reset/ti-syscon-reset.txt | 2 +- .../devicetree/bindings/rng/omap_rng.yaml | 4 +-- .../devicetree/bindings/rtc/rtc-cmos.txt | 2 +- .../bindings/serial/nvidia,tegra20-hsuart.txt | 2 +- .../devicetree/bindings/serial/st-asc.txt | 2 +- .../soc/mediatek/mediatek,mt7986-wo-ccif.yaml | 2 +- .../microchip,mpfs-sys-controller.yaml | 2 +- .../bindings/soc/qcom/qcom,aoss-qmp.yaml | 2 +- .../bindings/sound/axentia,tse850-pcm5142.txt | 2 +- .../devicetree/bindings/sound/cs35l35.txt | 2 +- .../devicetree/bindings/sound/cs35l36.txt | 2 +- .../devicetree/bindings/sound/cs53l30.txt | 2 +- .../devicetree/bindings/sound/fsl,esai.txt | 2 +- .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- .../bindings/sound/mt2701-afe-pcm.txt | 2 +- .../bindings/sound/mt8195-afe-pcm.yaml | 4 +-- .../sound/qcom,msm8916-wcd-analog.txt | 2 +- .../bindings/sound/renesas,rsnd.txt | 2 +- .../sound/rockchip,rk3288-hdmi-analog.txt | 2 +- .../devicetree/bindings/sound/rt5663.txt | 2 +- .../bindings/sound/serial-midi.yaml | 2 +- .../devicetree/bindings/sound/sprd-pcm.txt | 2 +- .../bindings/sound/st,stm32-sai.yaml | 2 +- .../sound/ti,j721e-cpb-ivi-audio.yaml | 2 +- .../devicetree/bindings/sound/ti,tas2781.yaml | 2 +- .../bindings/sound/tlv320adcx140.yaml | 2 +- .../bindings/soundwire/qcom,soundwire.yaml | 4 +-- .../bindings/spi/brcm,bcm2835-aux-spi.txt | 4 +-- .../bindings/spi/brcm,spi-bcm-qspi.yaml | 4 +-- .../devicetree/bindings/spi/omap-spi.yaml | 2 +- .../thermal/nvidia,tegra124-soctherm.txt | 2 +- .../bindings/timer/snps,arc-timer.txt | 2 +- .../devicetree/bindings/trivial-devices.yaml | 8 +++--- .../devicetree/bindings/usb/ci-hdrc-usb2.yaml | 2 +- .../bindings/usb/fsl,imx8mp-dwc3.yaml | 2 +- .../devicetree/bindings/usb/msm-hsusb.txt | 2 +- .../bindings/usb/richtek,rt1719.yaml | 2 +- .../fault-injection/fault-injection.rst | 2 +- Documentation/fb/deferred_io.rst | 2 +- Documentation/fb/sm712fb.rst | 2 +- Documentation/fb/sstfb.rst | 2 +- .../core/thread-info-in-task/arch-support.txt | 2 +- Documentation/filesystems/9p.rst | 2 +- Documentation/filesystems/befs.rst | 4 +-- .../filesystems/caching/cachefiles.rst | 2 +- .../filesystems/caching/netfs-api.rst | 6 ++--- Documentation/filesystems/configfs.rst | 2 +- Documentation/filesystems/dax.rst | 2 +- Documentation/filesystems/devpts.rst | 4 +-- Documentation/filesystems/ext4/super.rst | 2 +- Documentation/filesystems/f2fs.rst | 6 ++--- Documentation/filesystems/gfs2-glocks.rst | 2 +- Documentation/filesystems/idmappings.rst | 14 +++++----- Documentation/filesystems/netfs_library.rst | 2 +- .../filesystems/nfs/client-identifier.rst | 2 +- Documentation/filesystems/nfs/rpc-cache.rst | 2 +- .../filesystems/nfs/rpc-server-gss.rst | 2 +- Documentation/filesystems/nilfs2.rst | 2 +- Documentation/filesystems/ntfs3.rst | 2 +- Documentation/filesystems/orangefs.rst | 2 +- Documentation/filesystems/overlayfs.rst | 4 +-- Documentation/filesystems/porting.rst | 6 ++--- Documentation/filesystems/proc.rst | 12 ++++----- Documentation/filesystems/qnx6.rst | 2 +- Documentation/filesystems/seq_file.rst | 4 +-- .../filesystems/ubifs-authentication.rst | 2 +- Documentation/filesystems/vfat.rst | 2 +- Documentation/filesystems/vfs.rst | 2 +- .../filesystems/xfs-online-fsck-design.rst | 20 +++++++------- Documentation/filesystems/zonefs.rst | 2 +- Documentation/firmware-guide/acpi/osi.rst | 2 +- .../gpu/amdgpu/display/mpo-overview.rst | 2 +- Documentation/gpu/drm-kms-helpers.rst | 2 +- Documentation/gpu/drm-kms.rst | 6 ++--- Documentation/gpu/drm-usage-stats.rst | 4 +-- Documentation/gpu/i915.rst | 4 +-- Documentation/gpu/kms-properties.csv | 2 +- Documentation/gpu/komeda-kms.rst | 4 +-- Documentation/gpu/msm-crash-dump.rst | 2 +- Documentation/gpu/rfc/i915_scheduler.rst | 2 +- Documentation/gpu/rfc/i915_vm_bind.rst | 2 +- Documentation/gpu/todo.rst | 8 +++--- Documentation/hwmon/pmbus-core.rst | 2 +- .../input/devices/iforce-protocol.rst | 2 +- Documentation/input/multi-touch-protocol.rst | 2 +- .../livepatch/reliable-stacktrace.rst | 2 +- Documentation/locking/lockdep-design.rst | 4 +-- Documentation/locking/locktorture.rst | 2 +- Documentation/locking/locktypes.rst | 2 +- Documentation/mm/hmm.rst | 2 +- Documentation/mm/hwpoison.rst | 2 +- Documentation/mm/page_migration.rst | 2 +- Documentation/mm/unevictable-lru.rst | 2 +- Documentation/mm/vmemmap_dedup.rst | 2 +- Documentation/netlink/genetlink-c.yaml | 2 +- Documentation/netlink/genetlink-legacy.yaml | 2 +- Documentation/networking/bonding.rst | 2 +- .../networking/devlink/devlink-port.rst | 6 ++--- Documentation/networking/packet_mmap.rst | 2 +- Documentation/power/energy-model.rst | 4 +-- Documentation/powerpc/dscr.rst | 2 +- Documentation/powerpc/kasan.txt | 2 +- Documentation/powerpc/papr_hcalls.rst | 2 +- Documentation/powerpc/qe_firmware.rst | 4 +-- Documentation/powerpc/vas-api.rst | 4 +-- Documentation/process/botching-up-ioctls.rst | 2 +- Documentation/process/kernel-docs.rst | 2 +- Documentation/riscv/hwprobe.rst | 4 +-- Documentation/riscv/vector.rst | 2 +- Documentation/s390/vfio-ap.rst | 2 +- Documentation/scheduler/sched-bwc.rst | 2 +- Documentation/scheduler/sched-energy.rst | 4 +-- Documentation/scsi/ChangeLog.lpfc | 2 +- Documentation/security/digsig.rst | 2 +- Documentation/security/keys/core.rst | 2 +- Documentation/security/secrets/coco.rst | 2 +- Documentation/sphinx/cdomain.py | 2 +- Documentation/spi/spi-lm70llp.rst | 2 +- .../tools/rtla/rtla-timerlat-top.rst | 2 +- .../coresight/coresight-etm4x-reference.rst | 2 +- Documentation/trace/events.rst | 6 ++--- Documentation/trace/fprobe.rst | 2 +- Documentation/trace/ftrace.rst | 2 +- Documentation/trace/hwlat_detector.rst | 2 +- .../trace/rv/da_monitor_synthesis.rst | 2 +- Documentation/trace/rv/monitor_wwnr.rst | 2 +- .../trace/rv/runtime-verification.rst | 2 +- Documentation/trace/uprobetracer.rst | 2 +- Documentation/trace/user_events.rst | 2 +- Documentation/usb/gadget_uvc.rst | 2 +- .../media/v4l/ext-ctrls-codec-stateless.rst | 2 +- .../userspace-api/media/v4l/metafmt-d4xx.rst | 2 +- Documentation/userspace-api/netlink/intro.rst | 2 +- Documentation/virt/hyperv/clocks.rst | 2 +- Documentation/virt/kvm/api.rst | 26 +++++++++---------- Documentation/virt/kvm/devices/vm.rst | 2 +- Documentation/virt/kvm/devices/xive.rst | 2 +- Documentation/virt/kvm/halt-polling.rst | 2 +- Documentation/virt/kvm/x86/mmu.rst | 2 +- .../virt/kvm/x86/running-nested-guests.rst | 2 +- .../virt/uml/user_mode_linux_howto_v2.rst | 2 +- Documentation/w1/slaves/w1_therm.rst | 2 +- Documentation/w1/w1-generic.rst | 2 +- Documentation/w1/w1-netlink.rst | 2 +- .../watchdog/watchdog-kernel-api.rst | 2 +- Documentation/wmi/devices/dell-wmi-ddv.rst | 4 +-- 328 files changed, 441 insertions(+), 441 deletions(-)
Signature · 1 line
2.34.1
PATCH 1/3 Documentation/ABI: Fix typos
From: Bjorn Helgaas <[email protected]>
Fix typos in Documentation/ABI. The changes are in descriptions or comments where they shouldn't affect use of the ABIs.
--- Documentation/ABI/stable/sysfs-block | 2 +- Documentation/ABI/stable/sysfs-class-infiniband | 2 +- Documentation/ABI/stable/sysfs-platform-wmi-bmof | 2 +- Documentation/ABI/testing/debugfs-driver-habanalabs | 2 +- Documentation/ABI/testing/procfs-diskstats | 2 +- Documentation/ABI/testing/sysfs-bus-coreboot | 2 +- .../ABI/testing/sysfs-bus-coresight-devices-etm3x | 8 ++++---- .../ABI/testing/sysfs-bus-coresight-devices-etm4x | 2 +- .../ABI/testing/sysfs-bus-event_source-devices-events | 4 ++-- Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo | 4 ++-- Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 | 2 +- Documentation/ABI/testing/sysfs-bus-nfit | 2 +- Documentation/ABI/testing/sysfs-bus-papr-pmem | 2 +- Documentation/ABI/testing/sysfs-bus-umc | 2 +- Documentation/ABI/testing/sysfs-class | 2 +- Documentation/ABI/testing/sysfs-class-cxl | 4 ++-- Documentation/ABI/testing/sysfs-class-mtd | 2 +- Documentation/ABI/testing/sysfs-class-net | 2 +- Documentation/ABI/testing/sysfs-class-net-queues | 2 +- Documentation/ABI/testing/sysfs-class-power-wilco | 2 +- Documentation/ABI/testing/sysfs-class-remoteproc | 2 +- Documentation/ABI/testing/sysfs-class-thermal | 2 +- Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc | 2 +- Documentation/ABI/testing/sysfs-devices-online | 2 +- Documentation/ABI/testing/sysfs-driver-ge-achc | 2 +- Documentation/ABI/testing/sysfs-driver-tegra-fuse | 2 +- Documentation/ABI/testing/sysfs-firmware-acpi | 2 +- Documentation/ABI/testing/sysfs-firmware-sgi_uv | 4 ++-- Documentation/ABI/testing/sysfs-fs-f2fs | 8 ++++---- Documentation/ABI/testing/sysfs-kernel-mm-damon | 2 +- Documentation/ABI/testing/sysfs-memory-page-offline | 4 ++-- Documentation/ABI/testing/sysfs-platform-dell-laptop | 2 +- Documentation/ABI/testing/sysfs-platform-dfl-fme | 2 +- Documentation/ABI/testing/sysfs-platform-kim | 2 +- Documentation/ABI/testing/sysfs-platform-sst-atom | 2 +- 35 files changed, 46 insertions(+), 46 deletions(-)
Documentation/ABI/stable/sysfs-block +1 -1
@@ -295,7 +295,7 @@ Description: 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. + correctly advertises the sector ranges of its actuators. The independent_access_ranges directory contains one directory per access range, with each range described using the sector
Documentation/ABI/stable/sysfs-class-infiniband +1 -1
@@ -356,7 +356,7 @@ Description: pkeys/<n>: (RO) Displays the contents of the physical key table n = 0..126 - mcgs/: (RO) Muticast group table + mcgs/: (RO) Multicast group table <m>/gid_idx/0: (RO) Display the GID mapping m = 1..2
Documentation/ABI/stable/sysfs-platform-wmi-bmof +1 -1
@@ -2,6 +2,6 @@ What: /sys/bus/wmi/devices/05901221-D566-11D1-B2F0-00A0C9062910[-X]/bmof Date: Jun 2017 KernelVersion: 4.13 Description: - Binary MOF metadata used to decribe the details of available ACPI WMI interfaces. + Binary MOF metadata used to describe the details of available ACPI WMI interfaces. See Documentation/wmi/devices/wmi-bmof.rst for details.
Documentation/ABI/testing/debugfs-driver-habanalabs +1 -1
@@ -95,7 +95,7 @@ What: /sys/kernel/debug/habanalabs/hl<n>/device_release_watchdog_timeo Date: Oct 2022 KernelVersion: 6.2 Contact: [email protected] -Description: The watchdog timeout value in seconds for a device relese upon +Description: The watchdog timeout value in seconds for a device release upon certain error cases, after which the device is reset. What: /sys/kernel/debug/habanalabs/hl<n>/dma_size
Documentation/ABI/testing/procfs-diskstats +1 -1
@@ -8,7 +8,7 @@ Description: == =================================== 1 major number - 2 minor mumber + 2 minor number 3 device name 4 reads completed successfully 5 reads merged
Documentation/ABI/testing/sysfs-bus-coreboot +1 -1
@@ -21,7 +21,7 @@ What: /sys/bus/coreboot/devices/cbmem-<id>/address Date: August 2022 Contact: Jack Rosenthal <[email protected]> Description: - This is the pyhsical memory address that the CBMEM entry's data + This is the physical memory address that the CBMEM entry's data begins at, in hexadecimal (e.g., ``0x76ffe000``). What: /sys/bus/coreboot/devices/cbmem-<id>/size
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x +4 -4
@@ -31,7 +31,7 @@ Date: November 2014 KernelVersion: 3.19 Contact: Mathieu Poirier <[email protected]> Description: (RW) Used in conjunction with @addr_idx. Specifies the range of - addresses to trigger on. Inclusion or exclusion is specificed + addresses to trigger on. Inclusion or exclusion is specified in the corresponding access type register. What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/addr_single
@@ -304,19 +304,19 @@ What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtsscr Date: September 2015 KernelVersion: 4.4 Contact: Mathieu Poirier <[email protected]> -Description: (RO) Print the content of the ETM Trace Start/Stop Conrol +Description: (RO) Print the content of the ETM Trace Start/Stop Control register (0x018). The value is read directly from the HW. What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtecr1 Date: September 2015 KernelVersion: 4.4 Contact: Mathieu Poirier <[email protected]> -Description: (RO) Print the content of the ETM Enable Conrol #1 +Description: (RO) Print the content of the ETM Enable Control #1 register (0x024). The value is read directly from the HW. What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/mgmt/etmtecr2 Date: September 2015 KernelVersion: 4.4 Contact: Mathieu Poirier <[email protected]> -Description: (RO) Print the content of the ETM Enable Conrol #2 +Description: (RO) Print the content of the ETM Enable Control #2 register (0x01c). The value is read directly from the HW.
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x +1 -1
@@ -446,7 +446,7 @@ Date: April 2015 KernelVersion: 4.01 Contact: Mathieu Poirier <[email protected]> Description: (Read) Returns the maximum size of the data value, data address, - VMID, context ID and instuction address in the trace unit + VMID, context ID and instruction address in the trace unit (0x1E8). The value is taken directly from the HW. What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr3
Documentation/ABI/testing/sysfs-bus-event_source-devices-events +2 -2
@@ -47,7 +47,7 @@ Description: Per-pmu performance monitoring events specific to the running syste If a <term> is specified alone (without an assigned value), it is implied that 0x1 is assigned to that <term>. - Examples (each of these lines would be in a seperate file): + Examples (each of these lines would be in a separate file): event=0x2abc event=0x423,inv,cmask=0x3
@@ -83,7 +83,7 @@ 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 + received from the kernel to match the unit specified in the <event>.unit file. Example:
Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo +2 -2
@@ -5,6 +5,6 @@ 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 - ocurred and no transfers have completed since the timeout. A - value of 0 indicates that no timeout has ocurred, or if one + 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 successful.
Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 +1 -1
@@ -8,7 +8,7 @@ Description: NONE no device USB USB device is attached UART UART is attached - CHARGER Charger is attaced + CHARGER Charger is attached JIG JIG is attached ======= ======================
Documentation/ABI/testing/sysfs-bus-nfit +1 -1
@@ -121,7 +121,7 @@ KernelVersion: v4.7 Contact: [email protected] Description: (RO) ACPI specification 6.2 section 5.2.25.9, defines an - identifier for an NVDIMM, which refelects the id attribute. + identifier for an NVDIMM, which reflects the id attribute. What: /sys/bus/nd/devices/nmemX/nfit/subsystem_vendor
Documentation/ABI/testing/sysfs-bus-papr-pmem +1 -1
@@ -30,7 +30,7 @@ Description: Indicating that contents of the NVDIMM have been scrubbed. * "locked" - Indicating that NVDIMM contents cant + Indicating that NVDIMM contents can't be modified until next power cycle. What: /sys/bus/nd/devices/nmemX/papr/perf_stats
Documentation/ABI/testing/sysfs-bus-umc +1 -1
@@ -9,7 +9,7 @@ Description: Controller (UMC). The umc bus presents each of the individual - capabilties as a device. + capabilities as a device. What: /sys/bus/umc/devices/.../capability_id Date: July 2008
Documentation/ABI/testing/sysfs-class +1 -1
@@ -1,5 +1,5 @@ What: /sys/class/ -Date: Febuary 2006 +Date: February 2006 Contact: Greg Kroah-Hartman <[email protected]> Description: The /sys/class directory will consist of a group of
Documentation/ABI/testing/sysfs-class-cxl +2 -2
@@ -42,7 +42,7 @@ What: /sys/class/cxl/<afu>/mmio_size Date: September 2014 Contact: [email protected] Description: read only - Decimal value of the size of the MMIO space that may be mmaped + Decimal value of the size of the MMIO space that may be mmapped by userspace. Users: https://github.com/ibm-capi/libcxl
@@ -155,7 +155,7 @@ What: /sys/class/cxl/<afu>m/mmio_size Date: September 2014 Contact: [email protected] Description: read only - Decimal value of the size of the MMIO space that may be mmaped + Decimal value of the size of the MMIO space that may be mmapped by userspace. This includes all slave contexts space also. Users: https://github.com/ibm-capi/libcxl
Documentation/ABI/testing/sysfs-class-mtd +1 -1
@@ -39,7 +39,7 @@ KernelVersion: 2.6.29 Contact: [email protected] Description: Major and minor numbers of the character device corresponding - to the read-only variant of thie MTD device (in + to the read-only variant of the MTD device (in <major>:<minor> format). In this case <minor> will be odd. What: /sys/class/mtd/mtdX/erasesize
Documentation/ABI/testing/sysfs-class-net +1 -1
@@ -82,7 +82,7 @@ KernelVersion: 2.6.12 Contact: [email protected] Description: Indicates the current physical link state of the interface. - Posssible values are: + Possible values are: == ===================== 0 physical link is down
Documentation/ABI/testing/sysfs-class-net-queues +1 -1
@@ -39,7 +39,7 @@ Contact: [email protected] 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 + network device transmit queue. Possible values depend on the number of available CPU(s) in the system. What: /sys/class/<iface>/queues/tx-<queue>/xps_rxqs
Documentation/ABI/testing/sysfs-class-power-wilco +1 -1
@@ -22,7 +22,7 @@ Description: 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 + through EC's private PID. Switching 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
Documentation/ABI/testing/sysfs-class-remoteproc +1 -1
@@ -81,7 +81,7 @@ Description: Remote processor coredump configuration 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. + all data is read by userspace. What: /sys/class/remoteproc/.../recovery Date: July 2020
Documentation/ABI/testing/sysfs-class-thermal +1 -1
@@ -4,7 +4,7 @@ Description: 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 + should be a short, lowercase string, not containing spaces nor dashes. RO, Required
Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc +1 -1
@@ -42,7 +42,7 @@ Date: June 2013 KernelVersion: 3.11 Contact: Thomas Pugliese <[email protected]> Description: - The device notification time slot (DNTS) count and inverval in + The device notification time slot (DNTS) count and interval in milliseconds that the WUSB host should use. This controls how often the devices will have the opportunity to send notifications to the host.
Documentation/ABI/testing/sysfs-devices-online +1 -1
@@ -17,4 +17,4 @@ Description: After a successful execution of the bus type's .offline() callback the device cannot be used for any purpose until either it is removed (i.e. device_del() is called for it), or its bus - type's .online() is exeucted successfully. + type's .online() is executed successfully.
Documentation/ABI/testing/sysfs-driver-ge-achc +1 -1
@@ -5,7 +5,7 @@ Description: Write 1 to this file to update the ACHC microcontroller firmware via the EzPort interface. For this the kernel will load "achc.bin" via the firmware API (so usually from /lib/firmware). The write will block until the FW - has either been flashed successfully or an error occured. + has either been flashed successfully or an error occurred. What: /sys/bus/spi/<dev>/reset Date: Jul 2021
Documentation/ABI/testing/sysfs-driver-tegra-fuse +1 -1
@@ -3,7 +3,7 @@ Date: February 2014 Contact: Peter De Schrijver <[email protected]> Description: read-only access to the efuses on Tegra20, Tegra30, Tegra114 and Tegra124 SoC's from NVIDIA. The efuses contain write once - data programmed at the factory. The data is layed out in 32bit + data programmed at the factory. The data is laid out in 32bit words in LSB first format. Each bit represents a single value as decoded from the fuse registers. Bits order/assignment exactly matches the HW registers, including any unused bits.
Documentation/ABI/testing/sysfs-firmware-acpi +1 -1
@@ -84,7 +84,7 @@ Description: hotplug events associated with the given class of devices and will allow those devices to be ejected with the help of the _EJ0 control method. Unsetting it - effectively disables hotplug for the correspoinding + effectively disables hotplug for the corresponding class of devices. ======== =======================================================
Documentation/ABI/testing/sysfs-firmware-sgi_uv +2 -2
@@ -102,12 +102,12 @@ Description: conn_port The conn_hub entry contains a value representing the unique - oridinal value of the hub on the other end of the fabric + ordinal value of the hub on the other end of the fabric cable plugged into the port. If the port is disconnected, the value returned will be -1. The conn_port entry contains a value representing the unique - oridinal value of the port on the other end of the fabric cable + ordinal value of the port on the other end of the fabric cable plugged into the port. If the port is disconnected, the value returned will be -1.
Documentation/ABI/testing/sysfs-fs-f2fs +4 -4
@@ -54,9 +54,9 @@ Description: Controls the in-place-update policy. 0x00 DISABLE disable IPU(=default option in LFS mode) 0x01 FORCE all the time 0x02 SSR if SSR mode is activated - 0x04 UTIL if FS utilization is over threashold + 0x04 UTIL if FS utilization is over threshold 0x08 SSR_UTIL if SSR mode is activated and FS utilization is over - threashold + threshold 0x10 FSYNC activated in fsync path only for high performance flash storages. IPU will be triggered only if the # of dirty pages over min_fsync_blocks.
@@ -117,7 +117,7 @@ Date: December 2021 Contact: "Konstantin Vyshetsky" <[email protected]> Description: Controls the number of discards a thread will issue at a time. Higher number will allow the discard thread to finish its work - faster, at the cost of higher latency for incomming I/O. + faster, at the cost of higher latency for incoming I/O. What: /sys/fs/f2fs/<disk>/min_discard_issue_time Date: December 2021
@@ -334,7 +334,7 @@ Description: This indicates how many GC can be failed for the pinned state. 2048 trials is set by default. What: /sys/fs/f2fs/<disk>/extension_list -Date: Feburary 2018 +Date: February 2018 Contact: "Chao Yu" <[email protected]> Description: Used to control configure extension list: - Query: cat /sys/fs/f2fs/<disk>/extension_list
Documentation/ABI/testing/sysfs-kernel-mm-damon +1 -1
@@ -152,7 +152,7 @@ Description: Writing to and reading from this file sets and gets the action What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/min Date: Mar 2022 Contact: SeongJae Park <[email protected]> -Description: Writing to and reading from this file sets and gets the mimimum +Description: Writing to and reading from this file sets and gets the minimum size of the scheme's target regions in bytes. What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/max
Documentation/ABI/testing/sysfs-memory-page-offline +2 -2
@@ -10,7 +10,7 @@ Description: dropping it if possible. The kernel will then be placed on the bad page list and never be reused. - The offlining is done in kernel specific granuality. + The offlining is done in kernel specific granularity. Normally it's the base page size of the kernel, but this might change.
@@ -35,7 +35,7 @@ Description: to access this page assuming it's poisoned by the hardware. - The offlining is done in kernel specific granuality. + The offlining is done in kernel specific granularity. Normally it's the base page size of the kernel, but this might change.
Documentation/ABI/testing/sysfs-platform-dell-laptop +1 -1
@@ -15,7 +15,7 @@ KernelVersion: 3.19 Contact: Gabriele Mazzotta <[email protected]>, Pali Rohár <[email protected]> Description: - This file allows to specifiy the on/off threshold value, + This file allows to specify the on/off threshold value, as reported by the ambient light sensor. What: /sys/class/leds/dell::kbd_backlight/start_triggers
Documentation/ABI/testing/sysfs-platform-dfl-fme +1 -1
@@ -90,7 +90,7 @@ KernelVersion: 5.4 Contact: Wu Hao <[email protected]> Description: Read-Write. Read this file to get errors detected on FME. Write this file to clear errors logged in fme_errors. Write - fials with -EINVAL if input parsing fails or input error code + fails with -EINVAL if input parsing fails or input error code doesn't match. What: /sys/bus/platform/devices/dfl-fme.0/errors/first_error
Documentation/ABI/testing/sysfs-platform-kim +1 -1
@@ -9,7 +9,7 @@ Description: The device name flows down to architecture specific board initialization file from the ATAGS bootloader firmware. The name exposed is read from the user-space - dameon and opens the device when install is requested. + daemon and opens the device when install is requested. What: /sys/devices/platform/kim/baud_rate Date: January 2010
Documentation/ABI/testing/sysfs-platform-sst-atom +1 -1
@@ -4,7 +4,7 @@ KernelVersion: 4.10 Contact: "Sebastien Guiriec" <[email protected]> Description: LPE Firmware version for SST driver on all atom - plaforms (BYT/CHT/Merrifield/BSW). + platforms (BYT/CHT/Merrifield/BSW). If the FW has never been loaded it will display:: "FW not yet loaded"
Signature · 1 line
2.34.1
Re: [PATCH 1/3] Documentation/ABI: Fix typos
Quoted 6 lines · Bjorn Helgaas
From: Bjorn Helgaas<[email protected]>
Fix typos in
Documentation/ABI. The changes are in descriptions or comments where they shouldn't affect use of the ABIs.Signed-off-by Bjorn Helgaas<[email protected]>
Thanks.
PATCH 2/3 dt-bindings: Fix typos
In reply to Bjorn HelgaasFrom: Bjorn Helgaas <[email protected]>
Fix typos in Documentation/devicetree/bindings. The changes are in descriptions or comments where they shouldn't affect functionality.
--- Documentation/devicetree/bindings/arm/fsl.yaml | 4 ++-- .../arm/marvell/cp110-system-controller.txt | 8 ++++---- .../bindings/arm/mediatek/mediatek,mipi0a.txt | 2 +- .../bindings/arm/mediatek/mediatek,vcodecsys.txt | 2 +- Documentation/devicetree/bindings/arm/sunxi.yaml | 4 ++-- .../devicetree/bindings/ata/pata-common.yaml | 2 +- .../devicetree/bindings/bus/brcm,gisb-arb.yaml | 2 +- .../bindings/bus/nvidia,tegra210-aconnect.yaml | 4 ++-- .../clock/allwinner,sun4i-a10-osc-clk.yaml | 2 +- .../devicetree/bindings/clock/alphascale,acc.txt | 4 ++-- .../devicetree/bindings/clock/keystone-pll.txt | 2 +- .../devicetree/bindings/clock/lpc1850-ccu.txt | 2 +- .../bindings/clock/lpc1850-creg-clk.txt | 4 ++-- .../devicetree/bindings/clock/maxim,max9485.txt | 2 +- .../bindings/clock/qcom,gcc-sm8450.yaml | 2 +- .../bindings/clock/qcom,kpss-acc-v1.yaml | 2 +- .../bindings/clock/sprd,sc9863a-clk.yaml | 2 +- .../devicetree/bindings/clock/ti/mux.txt | 2 +- .../devicetree/bindings/clock/vf610-clock.txt | 2 +- .../bindings/clock/xlnx,zynqmp-clk.txt | 2 +- .../bindings/connector/usb-connector.yaml | 2 +- .../devfreq/event/samsung,exynos-ppmu.yaml | 2 +- .../bindings/display/atmel/hlcdc-dc.txt | 2 +- .../display/bridge/snps,dw-mipi-dsi.yaml | 2 +- .../bindings/display/cirrus,clps711x-fb.txt | 2 +- .../bindings/display/msm/qcom,mdss.yaml | 2 +- .../display/panel/olimex,lcd-olinuxino.yaml | 2 +- .../bindings/display/panel/panel-common.yaml | 2 +- .../display/tegra/nvidia,tegra124-sor.yaml | 2 +- .../devicetree/bindings/dma/ingenic,dma.yaml | 2 +- .../bindings/dma/nvidia,tegra20-apbdma.txt | 2 +- .../devicetree/bindings/dma/qcom,bam-dma.yaml | 2 +- .../bindings/dma/stericsson,dma40.yaml | 2 +- .../devicetree/bindings/fpga/fpga-region.txt | 4 ++-- .../devicetree/bindings/gpio/gpio-xgene-sb.txt | 2 +- .../bindings/gpio/snps,dw-apb-gpio.yaml | 2 +- .../devicetree/bindings/gpio/ti,omap-gpio.yaml | 4 ++-- .../devicetree/bindings/hwmon/adi,adm1177.yaml | 2 +- .../bindings/hwmon/adi,axi-fan-control.yaml | 2 +- .../devicetree/bindings/hwmon/adi,ltc2992.yaml | 2 +- .../bindings/hwmon/aspeed-pwm-tacho.txt | 2 +- Documentation/devicetree/bindings/hwmon/lm87.txt | 2 +- .../devicetree/bindings/hwmon/ltq-cputemp.txt | 2 +- .../bindings/hwmon/moortec,mr75203.yaml | 2 +- .../bindings/hwmon/npcm750-pwm-fan.txt | 2 +- .../bindings/hwmon/sensirion,shtc1.yaml | 2 +- .../devicetree/bindings/hwmon/ti,tmp513.yaml | 2 +- .../devicetree/bindings/hwmon/ti,tps23861.yaml | 2 +- .../devicetree/bindings/i2c/i2c-sprd.txt | 2 +- .../bindings/iio/adc/xlnx,zynqmp-ams.yaml | 2 +- .../devicetree/bindings/iio/cdc/adi,ad7150.yaml | 2 +- .../devicetree/bindings/iio/common.yaml | 2 +- .../bindings/iio/frequency/adi,admv1014.yaml | 2 +- .../bindings/iio/humidity/ti,hdc2010.yaml | 2 +- .../iio/pressure/honeywell,mprls0025pa.yaml | 2 +- .../bindings/iio/proximity/ams,as3935.yaml | 2 +- .../devicetree/bindings/iio/st,st-sensors.yaml | 2 +- .../bindings/input/rmi4/rmi_2d_sensor.txt | 4 ++-- .../bindings/input/touchscreen/stmpe.txt | 2 +- .../bindings/input/touchscreen/tsc2007.txt | 2 +- .../interrupt-controller/arm,gic-v3.yaml | 2 +- .../brcm,bcm2835-armctrl-ic.txt | 2 +- .../brcm,bcm7120-l2-intc.yaml | 2 +- .../backlight/mediatek,mt6370-backlight.yaml | 2 +- .../devicetree/bindings/leds/leds-lp55xx.yaml | 4 ++-- .../devicetree/bindings/leds/leds-qcom-lpg.yaml | 2 +- .../bindings/mailbox/brcm,iproc-flexrm-mbox.txt | 2 +- .../bindings/mailbox/ti,omap-mailbox.yaml | 2 +- .../bindings/media/i2c/toshiba,tc358746.yaml | 2 +- .../devicetree/bindings/media/i2c/tvp5150.txt | 2 +- .../media/mediatek,vcodec-subdev-decoder.yaml | 2 +- .../memory-controllers/mediatek,smi-larb.yaml | 2 +- .../memory-controllers/rockchip,rk3399-dmc.yaml | 4 ++-- .../memory-controllers/xlnx,zynq-ddrc-a05.yaml | 2 +- .../devicetree/bindings/mfd/aspeed-lpc.yaml | 2 +- .../bindings/mfd/rohm,bd9576-pmic.yaml | 4 ++-- .../bindings/mfd/stericsson,ab8500.yaml | 16 ++++++++-------- .../bindings/mfd/stericsson,db8500-prcmu.yaml | 2 +- .../devicetree/bindings/mmc/pxa-mmc.txt | 2 +- .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 2 +- .../bindings/net/brcm,bcm7445-switch-v4.0.txt | 2 +- .../devicetree/bindings/net/can/cc770.txt | 2 +- .../devicetree/bindings/net/dsa/brcm,sf2.yaml | 2 +- .../devicetree/bindings/net/ethernet-phy.yaml | 2 +- .../devicetree/bindings/net/mediatek-dwmac.yaml | 2 +- .../bindings/net/microchip,lan95xx.yaml | 2 +- .../devicetree/bindings/net/nfc/marvell,nci.yaml | 4 ++-- .../devicetree/bindings/net/samsung-sxgbe.txt | 4 ++-- .../bindings/net/snps,dwc-qos-ethernet.txt | 2 +- .../devicetree/bindings/net/sti-dwmac.txt | 2 +- .../bindings/net/xilinx_gmii2rgmii.txt | 2 +- .../devicetree/bindings/nios2/nios2.txt | 2 +- .../bindings/nvmem/layouts/onie,tlv-layout.yaml | 2 +- .../bindings/phy/phy-hisi-inno-usb2.txt | 2 +- .../bindings/phy/pistachio-usb-phy.txt | 2 +- .../devicetree/bindings/phy/pxa1928-usb-phy.txt | 2 +- .../bindings/phy/rockchip-inno-csi-dphy.yaml | 2 +- .../bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- Documentation/devicetree/bindings/phy/ti-phy.txt | 2 +- .../pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 2 +- .../bindings/pinctrl/canaan,k210-fpioa.yaml | 2 +- .../pinctrl/mediatek,mt6779-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt6795-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt7981-pinctrl.yaml | 4 ++-- .../pinctrl/mediatek,mt7986-pinctrl.yaml | 4 ++-- .../pinctrl/mediatek,mt8183-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt8365-pinctrl.yaml | 2 +- .../bindings/pinctrl/pinctrl-max77620.txt | 2 +- .../bindings/pinctrl/pinctrl-rk805.txt | 2 +- .../devicetree/bindings/pinctrl/sprd,pinctrl.txt | 2 +- .../devicetree/bindings/pmem/pmem-region.txt | 4 ++-- .../bindings/power/renesas,sysc-rmobile.yaml | 2 +- .../bindings/power/supply/sbs,sbs-manager.yaml | 2 +- .../devicetree/bindings/powerpc/fsl/cpus.txt | 2 +- .../devicetree/bindings/powerpc/fsl/dcsr.txt | 4 ++-- .../devicetree/bindings/powerpc/fsl/raideng.txt | 2 +- .../bindings/powerpc/nintendo/gamecube.txt | 2 +- .../devicetree/bindings/powerpc/nintendo/wii.txt | 2 +- .../bindings/pwm/snps,dw-apb-timers-pwm2.yaml | 2 +- .../bindings/regulator/regulator-max77620.txt | 2 +- .../devicetree/bindings/regulator/regulator.yaml | 8 ++++---- .../regulator/richtek,rt5190a-regulator.yaml | 2 +- .../devicetree/bindings/regulator/vctrl.txt | 2 +- .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 2 +- .../bindings/reset/ti-syscon-reset.txt | 2 +- .../devicetree/bindings/rng/omap_rng.yaml | 4 ++-- .../devicetree/bindings/rtc/rtc-cmos.txt | 2 +- .../bindings/serial/nvidia,tegra20-hsuart.txt | 2 +- .../devicetree/bindings/serial/st-asc.txt | 2 +- .../soc/mediatek/mediatek,mt7986-wo-ccif.yaml | 2 +- .../microchip/microchip,mpfs-sys-controller.yaml | 2 +- .../bindings/soc/qcom/qcom,aoss-qmp.yaml | 2 +- .../bindings/sound/axentia,tse850-pcm5142.txt | 2 +- .../devicetree/bindings/sound/cs35l35.txt | 2 +- .../devicetree/bindings/sound/cs35l36.txt | 2 +- .../devicetree/bindings/sound/cs53l30.txt | 2 +- .../devicetree/bindings/sound/fsl,esai.txt | 2 +- .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- .../devicetree/bindings/sound/mt2701-afe-pcm.txt | 2 +- .../bindings/sound/mt8195-afe-pcm.yaml | 4 ++-- .../bindings/sound/qcom,msm8916-wcd-analog.txt | 2 +- .../devicetree/bindings/sound/renesas,rsnd.txt | 2 +- .../sound/rockchip,rk3288-hdmi-analog.txt | 2 +- .../devicetree/bindings/sound/rt5663.txt | 2 +- .../devicetree/bindings/sound/serial-midi.yaml | 2 +- .../devicetree/bindings/sound/sprd-pcm.txt | 2 +- .../devicetree/bindings/sound/st,stm32-sai.yaml | 2 +- .../bindings/sound/ti,j721e-cpb-ivi-audio.yaml | 2 +- .../devicetree/bindings/sound/ti,tas2781.yaml | 2 +- .../devicetree/bindings/sound/tlv320adcx140.yaml | 2 +- .../bindings/soundwire/qcom,soundwire.yaml | 4 ++-- .../bindings/spi/brcm,bcm2835-aux-spi.txt | 4 ++-- .../bindings/spi/brcm,spi-bcm-qspi.yaml | 4 ++-- .../devicetree/bindings/spi/omap-spi.yaml | 2 +- .../thermal/nvidia,tegra124-soctherm.txt | 2 +- .../devicetree/bindings/timer/snps,arc-timer.txt | 2 +- .../devicetree/bindings/trivial-devices.yaml | 8 ++++---- .../devicetree/bindings/usb/ci-hdrc-usb2.yaml | 2 +- .../devicetree/bindings/usb/fsl,imx8mp-dwc3.yaml | 2 +- .../devicetree/bindings/usb/msm-hsusb.txt | 2 +- .../devicetree/bindings/usb/richtek,rt1719.yaml | 2 +- 161 files changed, 199 insertions(+), 199 deletions(-)
Documentation/devicetree/bindings/arm/fsl.yaml +2 -2
@@ -1222,9 +1222,9 @@ properties: - description: Freescale Vybrid Platform Device Tree Bindings - For the Vybrid SoC familiy all variants with DDR controller are supported, + For the Vybrid SoC family all variants with DDR controller are supported, which is the VF5xx and VF6xx series. Out of historical reasons, in most - places the kernel uses vf610 to refer to the whole familiy. + places the kernel uses vf610 to refer to the whole family. The compatible string "fsl,vf610m4" is used for the secondary Cortex-M4 core support. items:
Documentation/devicetree/bindings/arm/marvell/cp110-system-controller.txt +4 -4
@@ -21,13 +21,13 @@ The Device Tree node representing this System Controller 0 provides a number of clocks: - a set of core clocks - - a set of gatable clocks + - a set of gateable clocks Those clocks can be referenced by other Device Tree nodes using two cells: - The first cell must be 0 or 1. 0 for the core clocks and 1 for the - gatable clocks. - - The second cell identifies the particular core clock or gatable + gateable clocks. + - The second cell identifies the particular core clock or gateable clocks. The following clocks are available:
@@ -38,7 +38,7 @@ The following clocks are available: - 0 3 Core - 0 4 NAND core - 0 5 SDIO core - - Gatable clocks + - Gateable clocks - 1 0 Audio - 1 1 Comm Unit - 1 2 NAND
Documentation/devicetree/bindings/arm/mediatek/mediatek,mipi0a.txt +1 -1
@@ -16,7 +16,7 @@ The available clocks are defined in dt-bindings/clock/mt*-clk.h. The mipi0a controller also uses the common power domain from Documentation/devicetree/bindings/soc/mediatek/scpsys.txt -The available power doamins are defined in dt-bindings/power/mt*-power.h. +The available power domains are defined in dt-bindings/power/mt*-power.h. Example:
Documentation/devicetree/bindings/arm/mediatek/mediatek,vcodecsys.txt +1 -1
@@ -15,7 +15,7 @@ The available clocks are defined in dt-bindings/clock/mt*-clk.h. The vcodecsys controller also uses the common power domain from Documentation/devicetree/bindings/soc/mediatek/scpsys.txt -The available power doamins are defined in dt-bindings/power/mt*-power.h. +The available power domains are defined in dt-bindings/power/mt*-power.h. Example:
Documentation/devicetree/bindings/arm/sunxi.yaml +2 -2
@@ -541,13 +541,13 @@ properties: - const: msi,primo81 - const: allwinner,sun6i-a31s - - description: Emlid Neutis N5 Developper Board + - description: Emlid Neutis N5 Developer Board items: - const: emlid,neutis-n5-devboard - const: emlid,neutis-n5 - const: allwinner,sun50i-h5 - - description: Emlid Neutis N5H3 Developper Board + - description: Emlid Neutis N5H3 Developer Board items: - const: emlid,neutis-n5h3-devboard - const: emlid,neutis-n5h3
Documentation/devicetree/bindings/ata/pata-common.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: | This document defines device tree properties common to most Parallel ATA (PATA, also known as IDE) AT attachment storage devices. - It doesn't constitue a device tree binding specification by itself but is + It doesn't constitute a device tree binding specification by itself but is meant to be referenced by device tree bindings. The PATA (IDE) controller-specific device tree bindings are responsible for
Documentation/devicetree/bindings/bus/brcm,gisb-arb.yaml +1 -1
@@ -43,7 +43,7 @@ properties: brcm,gisb-arb-master-names: $ref: /schemas/types.yaml#/definitions/string-array description: > - String list of the litteral name of the GISB masters. Should match the + String list of the literal name of the GISB masters. Should match the number of bits set in brcm,gisb-master-mask and the order in which they appear from MSB to LSB.
Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.yaml +2 -2
@@ -7,10 +7,10 @@ $schema: http://devicetree.org/meta-schemas/core.yaml# title: NVIDIA Tegra ACONNECT Bus description: | - The Tegra ACONNECT bus is an AXI switch which is used to connnect various + The Tegra ACONNECT bus is an AXI switch which is used to connect various components inside the Audio Processing Engine (APE). All CPU accesses to the APE subsystem go through the ACONNECT via an APB to AXI wrapper. All - devices accessed via the ACONNNECT are described by child-nodes. + devices accessed via the ACONNECT are described by child-nodes. maintainers: - Jon Hunter <[email protected]>
Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-osc-clk.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/allwinner,sun4i-a10-osc-clk.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Allwinner A10 Gatable Oscillator Clock +title: Allwinner A10 Gateable Oscillator Clock maintainers: - Chen-Yu Tsai <[email protected]>
Documentation/devicetree/bindings/clock/alphascale,acc.txt +2 -2
@@ -1,7 +1,7 @@ Alphascale Clock Controller -The ACC (Alphascale Clock Controller) is responsible of choising proper -clock source, setting deviders and clock gates. +The ACC (Alphascale Clock Controller) is responsible for choosing proper +clock source, setting dividers and clock gates. Required properties for the ACC node: - compatible: must be "alphascale,asm9260-clock-controller"
Documentation/devicetree/bindings/clock/keystone-pll.txt +1 -1
@@ -14,7 +14,7 @@ Required properties: - #clock-cells : from common clock binding; shall be set to 0. - compatible : shall be "ti,keystone,main-pll-clock" or "ti,keystone,pll-clock" - clocks : parent clock phandle -- reg - pll control0 and pll multipler registers +- reg - pll control0 and pll multiplier registers - reg-names : control, multiplier and post-divider. The multiplier and post-divider registers are applicable only for main pll clock - fixed-postdiv : fixed post divider value. If absent, use clkod register bits
Documentation/devicetree/bindings/clock/lpc1850-ccu.txt +1 -1
@@ -68,7 +68,7 @@ soc { "base_ssp0_clk", "base_sdio_clk"; }; - /* A user of CCU brach clocks */ + /* A user of CCU branch clocks */ uart1: serial@40082000 { ... clocks = <&ccu2 CLK_APB0_UART1>, <&ccu1 CLK_CPU_UART1>;
Documentation/devicetree/bindings/clock/lpc1850-creg-clk.txt +2 -2
@@ -5,8 +5,8 @@ control registers for two low speed clocks. One of the clocks is a 32 kHz oscillator driver with power up/down and clock gating. Next is a fixed divider that creates a 1 kHz clock from the 32 kHz osc. -These clocks are used by the RTC and the Event Router peripherials. -The 32 kHz can also be routed to other peripherials to enable low +These clocks are used by the RTC and the Event Router peripherals. +The 32 kHz can also be routed to other peripherals to enable low power modes. This binding uses the common clock binding:
Documentation/devicetree/bindings/clock/maxim,max9485.txt +1 -1
@@ -12,7 +12,7 @@ requests. Required properties: - compatible: "maxim,max9485" -- clocks: Input clock, must provice 27.000 MHz +- clocks: Input clock, must provide 27.000 MHz - clock-names: Must be set to "xclk" - #clock-cells: From common clock binding; shall be set to 1
Documentation/devicetree/bindings/clock/qcom,gcc-sm8450.yaml +1 -1
@@ -25,7 +25,7 @@ properties: - description: Sleep clock source - description: PCIE 0 Pipe clock source (Optional clock) - description: PCIE 1 Pipe clock source (Optional clock) - - description: PCIE 1 Phy Auxillary clock source (Optional clock) + - description: PCIE 1 Phy Auxiliary clock source (Optional clock) - description: UFS Phy Rx symbol 0 clock source (Optional clock) - description: UFS Phy Rx symbol 1 clock source (Optional clock) - description: UFS Phy Tx symbol 0 clock source (Optional clock)
Documentation/devicetree/bindings/clock/qcom,kpss-acc-v1.yaml +1 -1
@@ -14,7 +14,7 @@ description: There is one ACC register region per CPU within the KPSS remapped region as well as an alias register region that remaps accesses to the ACC associated with the CPU accessing the region. ACC v1 is currently used as a - clock-controller for enabling the cpu and hanling the aux clocks. + clock-controller for enabling the cpu and handling the aux clocks. properties: compatible:
Documentation/devicetree/bindings/clock/sprd,sc9863a-clk.yaml +1 -1
@@ -66,7 +66,7 @@ then: else: description: | Other SC9863a clock nodes should be the child of a syscon node in - which compatible string shoule be: + which compatible string should be: "sprd,sc9863a-glbregs", "syscon", "simple-mfd" The 'reg' property for the clock node is also required if there is a sub
Documentation/devicetree/bindings/clock/ti/mux.txt +1 -1
@@ -8,7 +8,7 @@ parents, one of which can be selected as output. This clock does not gate or adjust the parent rate via a divider or multiplier. By default the "clocks" property lists the parents in the same order -as they are programmed into the regster. E.g: +as they are programmed into the register. E.g: clocks = <&foo_clock>, <&bar_clock>, <&baz_clock>;
Documentation/devicetree/bindings/clock/vf610-clock.txt +1 -1
@@ -9,7 +9,7 @@ Optional properties: - clocks: list of clock identifiers which are external input clocks to the given clock controller. Please refer the next section to find the input clocks for a given controller. -- clock-names: list of names of clocks which are exteral input clocks to the +- clock-names: list of names of clocks which are external input clocks to the given clock controller. Input clocks for top clock controller:
Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt +1 -1
@@ -15,7 +15,7 @@ Required properties: clocks to the given clock controller. Please refer the next section to find the input clocks for a given controller. - - clock-names: List of clock names which are exteral input clocks + - clock-names: List of clock names which are external input clocks to the given clock controller. Please refer to the clock bindings for more details.
Documentation/devicetree/bindings/connector/usb-connector.yaml +1 -1
@@ -224,7 +224,7 @@ properties: state as defined in 7.4.2 Sink Electrical Parameters of USB Power Delivery Specification Revision 3.0, Version 1.2. When the property is set, the port requests pSnkStby(2.5W - 5V@500mA) upon entering SNK_DISCOVERY(instead of 3A or the 1.5A, Rp current advertised, during - SNK_DISCOVERY) and the actual currrent limit after reception of PS_Ready for PD link or during + SNK_DISCOVERY) and the actual current limit after reception of PS_Ready for PD link or during SNK_READY for non-pd link. type: boolean
Documentation/devicetree/bindings/devfreq/event/samsung,exynos-ppmu.yaml +1 -1
@@ -18,7 +18,7 @@ description: | each IP (DMC, CPU, RIGHTBUS, LEFTBUS, CAM interface, LCD, G3D, MFC). The Exynos PPMU driver uses the devfreq-event class to provide event data to various devfreq devices. The devfreq devices would use the event data when - derterming the current state of each IP. + determining the current state of each IP. properties: compatible:
Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt +1 -1
@@ -12,7 +12,7 @@ Required properties: Required children nodes: Children nodes are encoding available output ports and their connections - to external devices using the OF graph reprensentation (see ../graph.txt). + to external devices using the OF graph representation (see ../graph.txt). At least one port node is required. Optional properties in grandchild nodes:
Documentation/devicetree/bindings/display/bridge/snps,dw-mipi-dsi.yaml +1 -1
@@ -11,7 +11,7 @@ maintainers: description: | This document defines device tree properties for the Synopsys DesignWare MIPI - DSI host controller. It doesn't constitue a device tree binding specification + DSI host controller. It doesn't constitute a device tree binding specification by itself but is meant to be referenced by platform-specific device tree bindings.
Documentation/devicetree/bindings/display/cirrus,clps711x-fb.txt +1 -1
@@ -1,4 +1,4 @@ -* Currus Logic CLPS711X Framebuffer +* Cirrus Logic CLPS711X Framebuffer Required properties: - compatible: Shall contain "cirrus,ep7209-fb".
Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml +1 -1
@@ -11,7 +11,7 @@ maintainers: - Rob Clark <[email protected]> description: - This is the bindings documentation for the Mobile Display Subsytem(MDSS) that + This is the bindings documentation for the Mobile Display Subsystem(MDSS) that encapsulates sub-blocks like MDP5, DSI, HDMI, eDP, etc. properties:
Documentation/devicetree/bindings/display/panel/olimex,lcd-olinuxino.yaml +1 -1
@@ -20,7 +20,7 @@ description: | The panel itself contains: - AT24C16C EEPROM holding panel identification and timing requirements - AR1021 resistive touch screen controller (optional) - - FT5x6 capacitive touch screnn controller (optional) + - FT5x6 capacitive touch screen controller (optional) - GT911/GT928 capacitive touch screen controller (optional) The above chips share same I2C bus. The EEPROM is factory preprogrammed with
Documentation/devicetree/bindings/display/panel/panel-common.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: | This document defines device tree properties common to several classes of - display panels. It doesn't constitue a device tree binding specification by + display panels. It doesn't constitute a device tree binding specification by itself but is meant to be referenced by device tree bindings. When referenced from panel device tree bindings the properties defined in this
Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-sor.yaml +1 -1
@@ -97,7 +97,7 @@ properties: # optional when driving an eDP output nvidia,dpaux: - description: phandle to a DispayPort AUX interface + description: phandle to a DisplayPort AUX interface $ref: /schemas/types.yaml#/definitions/phandle allOf:
Documentation/devicetree/bindings/dma/ingenic,dma.yaml +1 -1
@@ -68,7 +68,7 @@ properties: $ref: /schemas/types.yaml#/definitions/uint32 description: > Bitmask of channels to reserve for devices that need a specific - channel. These channels will only be assigned when explicitely + channel. These channels will only be assigned when explicitly requested by a client. The primary use for this is channels 0 and 1, which can be configured to have special behaviour for NAND/BCH when using programmable firmware.
Documentation/devicetree/bindings/dma/nvidia,tegra20-apbdma.txt +1 -1
@@ -2,7 +2,7 @@ Required properties: - compatible: Should be "nvidia,<chip>-apbdma" -- reg: Should contain DMA registers location and length. This shuld include +- reg: Should contain DMA registers location and length. This should include all of the per-channel registers. - interrupts: Should contain all of the per-channel DMA interrupts. - clocks: Must contain one entry, for the module clock.
Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml +1 -1
@@ -48,7 +48,7 @@ properties: qcom,controlled-remotely: type: boolean description: - Indicates that the bam is controlled by remote proccessor i.e. execution + Indicates that the bam is controlled by remote processor i.e. execution environment. qcom,ee:
Documentation/devicetree/bindings/dma/stericsson,dma40.yaml +1 -1
@@ -148,7 +148,7 @@ properties: memcpy-channels: $ref: /schemas/types.yaml#/definitions/uint32-array description: Array of u32 elements indicating which channels on the DMA - engine are elegible for memcpy transfers + engine are eligible for memcpy transfers required: - "#dma-cells"
Documentation/devicetree/bindings/fpga/fpga-region.txt +2 -2
@@ -63,7 +63,7 @@ FPGA Bridge will be disabled. * During Partial Reconfiguration of a specific region, that region's bridge will be used to gate the busses. Traffic to other regions is not affected. - * In some implementations, the FPGA Manager transparantly handles gating the + * In some implementations, the FPGA Manager transparently handles gating the buses, eliminating the need to show the hardware FPGA bridges in the device tree. * An FPGA image may create a set of reprogrammable regions, each having its
@@ -466,7 +466,7 @@ It is beyond the scope of this document to fully describe all the FPGA design constraints required to make partial reconfiguration work[1] [2] [3], but a few deserve quick mention. -A persona must have boundary connections that line up with those of the partion +A persona must have boundary connections that line up with those of the partition or region it is designed to go into. During programming, transactions through those connections must be stopped and
Documentation/devicetree/bindings/gpio/gpio-xgene-sb.txt +1 -1
@@ -27,7 +27,7 @@ Required properties: - gpio-controller: Marks the device node as a GPIO controller. - interrupts: The EXT_INT_0 parent interrupt resource must be listed first. - interrupt-cells: Should be two. - - first cell is 0-N coresponding for EXT_INT_0 to EXT_INT_N. + - first cell is 0-N corresponding for EXT_INT_0 to EXT_INT_N. - second cell is used to specify flags. - interrupt-controller: Marks the device node as an interrupt controller. - apm,nr-gpios: Optional, specify number of gpios pin.
Documentation/devicetree/bindings/gpio/snps,dw-apb-gpio.yaml +1 -1
@@ -9,7 +9,7 @@ title: Synopsys DesignWare APB GPIO controller description: | Synopsys DesignWare GPIO controllers have a configurable number of ports, each of which are intended to be represented as child nodes with the generic - GPIO-controller properties as desribed in this bindings file. + GPIO-controller properties as described in this bindings file. maintainers: - Hoan Tran <[email protected]>
Documentation/devicetree/bindings/gpio/ti,omap-gpio.yaml +2 -2
@@ -58,14 +58,14 @@ properties: deprecated: true description: Name of the hwmod associated with the GPIO. Needed on some legacy OMAP - SoCs which have not been converted to the ti,sysc interconnect hierarachy. + SoCs which have not been converted to the ti,sysc interconnect hierarchy. ti,no-reset-on-init: $ref: /schemas/types.yaml#/definitions/flag deprecated: true description: Do not reset on init. Used with ti,hwmods on some legacy OMAP SoCs which - have not been converted to the ti,sysc interconnect hierarachy. + have not been converted to the ti,sysc interconnect hierarchy. patternProperties: "^(.+-hog(-[0-9]+)?)$":
Documentation/devicetree/bindings/hwmon/adi,adm1177.yaml +1 -1
@@ -27,7 +27,7 @@ properties: shunt-resistor-micro-ohms: description: - The value of curent sense resistor in microohms. If not provided, + The value of current sense resistor in microohms. If not provided, the current reading and overcurrent alert is disabled. adi,shutdown-threshold-microamp:
Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml +1 -1
@@ -11,7 +11,7 @@ maintainers: - Nuno Sá <[email protected]> description: |+ - Bindings for the Analog Devices AXI FAN Control driver. Spefications of the + Bindings for the Analog Devices AXI FAN Control driver. Specifications of the core can be found in: https://wiki.analog.com/resources/fpga/docs/axi_fan_control
Documentation/devicetree/bindings/hwmon/adi,ltc2992.yaml +1 -1
@@ -46,7 +46,7 @@ patternProperties: shunt-resistor-micro-ohms: description: - The value of curent sense resistor in microohms. + The value of current sense resistor in microohms. required: - compatible
Documentation/devicetree/bindings/hwmon/aspeed-pwm-tacho.txt +1 -1
@@ -45,7 +45,7 @@ Required properties for each child node: - aspeed,fan-tach-ch : should specify the Fan tach input channel. integer value in the range 0 through 15, with 0 indicating Fan tach channel 0 and 15 indicating Fan tach channel 15. - Atleast one Fan tach input channel is required. + At least one Fan tach input channel is required. Examples:
Documentation/devicetree/bindings/hwmon/lm87.txt +1 -1
@@ -18,7 +18,7 @@ optional properties: in7. Otherwise the pin is set as FAN2 input. - vcc-supply: a Phandle for the regulator supplying power, can be - cofigured to measure 5.0V power supply. Default is 3.3V. + configured to measure 5.0V power supply. Default is 3.3V. Example:
Documentation/devicetree/bindings/hwmon/ltq-cputemp.txt +1 -1
@@ -1,4 +1,4 @@ -Lantiq cpu temperatur sensor +Lantiq cpu temperature sensor Requires node properties: - compatible value :
Documentation/devicetree/bindings/hwmon/moortec,mr75203.yaml +1 -1
@@ -42,7 +42,7 @@ properties: reg: items: - description: PVT common registers - - description: PVT temprature sensor registers + - description: PVT temperature sensor registers - description: PVT process detector registers - description: PVT voltage monitor registers
Documentation/devicetree/bindings/hwmon/npcm750-pwm-fan.txt +1 -1
@@ -23,7 +23,7 @@ Required properties for pwm-fan node fan subnode format: =================== Under fan subnode can be upto 8 child nodes, each child node representing a fan. -Each fan subnode must have one PWM channel and atleast one Fan tach channel. +Each fan subnode must have one PWM channel and at least one Fan tach channel. For PWM channel can be configured cooling-levels to create cooling device. Cooling device could be bound to a thermal zone for the thermal control.
Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml +1 -1
@@ -13,7 +13,7 @@ description: | The SHTC1, SHTW1 and SHTC3 are digital humidity and temperature sensors designed especially for battery-driven high-volume consumer electronics applications. - For further information refere to Documentation/hwmon/shtc1.rst + For further information refer to Documentation/hwmon/shtc1.rst This binding document describes the binding for the hardware monitor portion of the driver.
Documentation/devicetree/bindings/hwmon/ti,tmp513.yaml +1 -1
@@ -33,7 +33,7 @@ properties: shunt-resistor-micro-ohms: description: | - If 0, the calibration process will be skiped and the current and power + If 0, the calibration process will be skipped and the current and power measurement engine will not work. Temperature and voltage measurement will continue to work. The shunt value also need to respect: rshunt <= pga-gain * 40 * 1000 * 1000.
Documentation/devicetree/bindings/hwmon/ti,tps23861.yaml +1 -1
@@ -26,7 +26,7 @@ properties: maxItems: 1 shunt-resistor-micro-ohms: - description: The value of curent sense resistor in microohms. + description: The value of current sense resistor in microohms. default: 255000 minimum: 250000 maximum: 255000
Documentation/devicetree/bindings/i2c/i2c-sprd.txt +1 -1
@@ -10,7 +10,7 @@ Required properties: "source" for I2C source (parent) clock, "enable" for I2C module enable clock. - clocks: Should contain a clock specifier for each entry in clock-names. -- clock-frequency: Constains desired I2C bus clock frequency in Hz. +- clock-frequency: Contains desired I2C bus clock frequency in Hz. - #address-cells: Should be 1 to describe address cells for I2C device address. - #size-cells: Should be 0 means no size cell for I2C device address.
Documentation/devicetree/bindings/iio/adc/xlnx,zynqmp-ams.yaml +1 -1
@@ -57,7 +57,7 @@ description: | |27 |FPD Internal voltage measurement, VCC_PSINTFP (supply5). |Voltage |28 |PS Auxiliary voltage measurement (supply6). |Voltage |29 |PL VCCADC voltage measurement (vccams). |Voltage - |30 |Differential analog input signal voltage measurment. |Voltage + |30 |Differential analog input signal voltage measurement. |Voltage |31 |VUser0 voltage measurement (supply7). |Voltage |32 |VUser1 voltage measurement (supply8). |Voltage |33 |VUser2 voltage measurement (supply9). |Voltage
Documentation/devicetree/bindings/iio/cdc/adi,ad7150.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/iio/cdc/adi,ad7150.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Analog device AD7150 and similar capacitance to digital convertors. +title: Analog device AD7150 and similar capacitance to digital converters. maintainers: - Jonathan Cameron <[email protected]>
Documentation/devicetree/bindings/iio/common.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: | This document defines device tree properties common to several iio - sensors. It doesn't constitue a device tree binding specification by itself but + sensors. It doesn't constitute a device tree binding specification by itself but is meant to be referenced by device tree bindings. When referenced from sensor tree bindings the properties defined in this
Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml +1 -1
@@ -33,7 +33,7 @@ properties: items: - const: lo_in description: - External clock that provides the Local Oscilator input. + External clock that provides the Local Oscillator input. vcm-supply: description:
Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml +1 -1
@@ -10,7 +10,7 @@ maintainers: - Eugene Zaikonnikov <[email protected]> description: | - Relative humidity and tempereature sensors on I2C bus + Relative humidity and temperature sensors on I2C bus Datasheets are available at: http://www.ti.com/product/HDC2010/datasheet
Documentation/devicetree/bindings/iio/pressure/honeywell,mprls0025pa.yaml +1 -1
@@ -47,7 +47,7 @@ properties: reset-gpios: description: Optional GPIO for resetting the device. - If not present the device is not resetted during the probe. + If not present the device is not reset during the probe. maxItems: 1 honeywell,pmin-pascal:
Documentation/devicetree/bindings/iio/proximity/ams,as3935.yaml +1 -1
@@ -10,7 +10,7 @@ maintainers: - Matt Ranostay <[email protected]> description: - This lightening distance sensor uses an I2C or SPI interface. The + This lightning distance sensor uses an I2C or SPI interface. The binding currently only covers the SPI option. properties:
Documentation/devicetree/bindings/iio/st,st-sensors.yaml +1 -1
@@ -97,7 +97,7 @@ properties: interrupts: description: interrupt line(s) connected to the DRDY line(s) and/or the - Intertial interrupt lines INT1 and INT2 if these exist. This means up to + Inertial interrupt lines INT1 and INT2 if these exist. This means up to three interrupts, and the DRDY must be the first one if it exists on the package. The trigger edge of the interrupts is sometimes software configurable in the hardware so the operating system should parse this
Documentation/devicetree/bindings/input/rmi4/rmi_2d_sensor.txt +2 -2
@@ -34,8 +34,8 @@ Optional Properties: mode. - syna,sensor-type: Set the sensor type. 1 for touchscreen 2 for touchpad. - syna,disable-report-mask: Mask for disabling posiiton reporting. Used to - disable reporing absolute position data. -- syna,rezero-wait-ms: Time in miliseconds to wait after issuing a rezero + disable reporting absolute position data. +- syna,rezero-wait-ms: Time in milliseconds to wait after issuing a rezero command.
Documentation/devicetree/bindings/input/touchscreen/stmpe.txt +1 -1
@@ -81,7 +81,7 @@ stmpe811@41 { st,mod-12b = <1>; /* internal ADC reference */ st,ref-sel = <0>; - /* ADC converstion time: 80 clocks */ + /* ADC conversion time: 80 clocks */ st,sample-time = <4>; stmpe_touchscreen {
Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt +1 -1
@@ -6,7 +6,7 @@ Required properties: - ti,x-plate-ohms: X-plate resistance in ohms. Optional properties: -- gpios: the interrupt gpio the chip is connected to (trough the penirq pin). +- gpios: the interrupt gpio the chip is connected to (through the penirq pin). The penirq pin goes to low when the panel is touched. (see GPIO binding[1] for more details). - interrupts: (gpio) interrupt to which the chip is connected
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml +1 -1
@@ -49,7 +49,7 @@ properties: The 2nd cell contains the interrupt number for the interrupt type. SPI interrupts are in the range [0-987]. PPI interrupts are in the - range [0-15]. Extented SPI interrupts are in the range [0-1023]. + range [0-15]. Extended SPI interrupts are in the range [0-1023]. Extended PPI interrupts are in the range [0-127]. The 3rd cell is the flags, encoded as follows:
Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt +1 -1
@@ -70,7 +70,7 @@ Bank 1: 25: DMA9 26: DMA10 27: DMA11-14 - shared interrupt for DMA 11 to 14 -28: DMAALL - triggers on all dma interrupts (including chanel 15) +28: DMAALL - triggers on all dma interrupts (including channel 15) 29: AUX 30: ARM 31: VPUDMA
Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7120-l2-intc.yaml +1 -1
@@ -59,7 +59,7 @@ description: > .. 31 ........................ X - The BCM3380 Level 1 / Level 2 interrrupt controller shows up in various forms + The BCM3380 Level 1 / Level 2 interrupt controller shows up in various forms on many BCM338x/BCM63xx chipsets. It has the following properties: - outputs a single interrupt signal to its interrupt controller parent
Documentation/devicetree/bindings/leds/backlight/mediatek,mt6370-backlight.yaml +1 -1
@@ -66,7 +66,7 @@ properties: mediatek,bled-ocp-shutdown: description: | - Enable the backlight shutdown when OCP level triggerred. + Enable the backlight shutdown when OCP level triggered. type: boolean mediatek,bled-ocp-microamp:
Documentation/devicetree/bindings/leds/leds-lp55xx.yaml +2 -2
@@ -106,7 +106,7 @@ patternProperties: max-cur: $ref: /schemas/types.yaml#/definitions/uint8 - description: Maximun current at each LED channel. + description: Maximum current at each LED channel. reg: maximum: 8
@@ -129,7 +129,7 @@ patternProperties: max-cur: $ref: /schemas/types.yaml#/definitions/uint8 - description: Maximun current at each LED channel. + description: Maximum current at each LED channel. reg: description: |
Documentation/devicetree/bindings/leds/leds-qcom-lpg.yaml +1 -1
@@ -56,7 +56,7 @@ properties: description: > A list of integer pairs, where each pair represent the dtest line the particular channel should be connected to and the flags denoting how the - value should be outputed, as defined in the datasheet. The number of + value should be outputted, as defined in the datasheet. The number of pairs should be the same as the number of channels. items: items:
Documentation/devicetree/bindings/mailbox/brcm,iproc-flexrm-mbox.txt +1 -1
@@ -29,7 +29,7 @@ Required properties: where N is the value specified by 2nd cell above. If FlexRM does not get required number of completion messages in time specified by this cell then it will inject one MSI interrupt - to CPU provided atleast one completion message is available. + to CPU provided at least one completion message is available. Optional properties: --------------------
Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml +1 -1
@@ -159,7 +159,7 @@ properties: a corresponding sysc interconnect node. This property is only needed on some legacy OMAP SoCs which have not - yet been converted to the ti,sysc interconnect hierarachy, but is + yet been converted to the ti,sysc interconnect hierarchy, but is otherwise considered obsolete. patternProperties:
Documentation/devicetree/bindings/media/i2c/toshiba,tc358746.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: |- The Toshiba TC358746 converts a parallel video stream into a MIPI CSI-2 stream. The direction can be either parallel-in -> csi-out or csi-in -> - parallel-out The chip is programmable trough I2C and SPI but the SPI + parallel-out The chip is programmable through I2C and SPI but the SPI interface is only supported in parallel-in -> csi-out mode. Note that the current device tree bindings only support the
Documentation/devicetree/bindings/media/i2c/tvp5150.txt +1 -1
@@ -53,7 +53,7 @@ Optional Connector Properties: ============================== - sdtv-standards: Set the possible signals to which the hardware tries to lock - instead of using the autodetection mechnism. Please look at + instead of using the autodetection mechanism. Please look at [1] for more information. [1] Documentation/devicetree/bindings/display/connector/analog-tv-connector.yaml.
Documentation/devicetree/bindings/media/mediatek,vcodec-subdev-decoder.yaml +1 -1
@@ -36,7 +36,7 @@ description: | controls the information of each hardware independent which include clk/power/irq. There are two workqueues in parent device: lat workqueue and core workqueue. They are used - to lat and core hardware deocder. Lat workqueue need to get input bitstream and lat buffer, + to lat and core hardware decoder. Lat workqueue need to get input bitstream and lat buffer, then enable lat to decode, writing the result to lat buffer, dislabe hardware when lat decode done. Core workqueue need to get lat buffer and output buffer, then enable core to decode, writing the result to output buffer, disable hardware when core decode done. These two
Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml +1 -1
@@ -67,7 +67,7 @@ properties: minimum: 0 maximum: 31 description: the hardware id of this larb. It's only required when this - hardward id is not consecutive from its M4U point of view. + hardware id is not consecutive from its M4U point of view. required: - compatible
Documentation/devicetree/bindings/memory-controllers/rockchip,rk3399-dmc.yaml +2 -2
@@ -152,7 +152,7 @@ properties: $ref: /schemas/types.yaml#/definitions/uint32 description: When the DRAM type is DDR3, this parameter defines the phy side CA line - (incluing command line, address line and clock line) drive strength. + (including command line, address line and clock line) drive strength. default: 40 rockchip,phy_ddr3_dq_drv:
@@ -305,7 +305,7 @@ properties: description: Defines the self-refresh power down idle period in which memories are placed into self-refresh power down mode if bus is idle for - srpd_lite_idle nanoseonds. This parameter is for LPDDR4 only. + srpd_lite_idle nanoseconds. This parameter is for LPDDR4 only. rockchip,standby-idle-ns: description:
Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: The Zynq DDR ECC controller has an optional ECC support in half-bus width - (16-bit) configuration. It is cappable of correcting single bit ECC errors + (16-bit) configuration. It is capable of correcting single bit ECC errors and detecting double bit ECC errors. properties:
Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml +1 -1
@@ -27,7 +27,7 @@ description: as LPC firmware hub cycles, configuration of the LPC-to-AHB mapping, UART management and bus snoop configuration. - * A set of SuperIO[3] scratch registers enableing implementation of e.g. custom + * A set of SuperIO[3] scratch registers enabling implementation of e.g. custom hardware management protocols for handover between the host and baseboard management controller.
Documentation/devicetree/bindings/mfd/rohm,bd9576-pmic.yaml +2 -2
@@ -34,7 +34,7 @@ properties: BD9576 and BD9573 VOUT1 regulator enable state can be individually controlled by a GPIO. This is dictated by state of vout1-en pin during the PMIC startup. If vout1-en is LOW during PMIC startup then the VOUT1 - enable sate is controlled via this pin. Set this property if vout1-en + enable state is controlled via this pin. Set this property if vout1-en is wired to be down at PMIC start-up. type: boolean
@@ -61,7 +61,7 @@ properties: rohm,hw-timeout-ms: maxItems: 2 description: - Watchog timeout in milliseconds. If single value is given it is + Watchdog timeout in milliseconds. If single value is given it is the maximum timeout. Eg. if pinging watchdog is not done within this time limit the watchdog will be triggered. If two values are given watchdog is configured in "window mode". Then first value is limit for short-ping
Documentation/devicetree/bindings/mfd/stericsson,ab8500.yaml +8 -8
@@ -313,7 +313,7 @@ properties: - const: audioclk stericsson,earpeice-cmv: - description: Earpeice voltage + description: Earpiece voltage $ref: /schemas/types.yaml#/definitions/uint32 enum: [ 950, 1100, 1270, 1580 ]
@@ -337,39 +337,39 @@ properties: with power. ab8500_ldo_aux1: - description: The voltage for the auxilary LDO regulator 1 + description: The voltage for the auxiliary LDO regulator 1 type: object $ref: ../regulator/regulator.yaml# unevaluatedProperties: false ab8500_ldo_aux2: - description: The voltage for the auxilary LDO regulator 2 + description: The voltage for the auxiliary LDO regulator 2 type: object $ref: ../regulator/regulator.yaml# unevaluatedProperties: false ab8500_ldo_aux3: - description: The voltage for the auxilary LDO regulator 3 + description: The voltage for the auxiliary LDO regulator 3 type: object $ref: ../regulator/regulator.yaml# unevaluatedProperties: false ab8500_ldo_aux4: - description: The voltage for the auxilary LDO regulator 4 + description: The voltage for the auxiliary LDO regulator 4 only present on AB8505 type: object $ref: ../regulator/regulator.yaml# unevaluatedProperties: false ab8500_ldo_aux5: - description: The voltage for the auxilary LDO regulator 5 + description: The voltage for the auxiliary LDO regulator 5 only present on AB8505 type: object $ref: ../regulator/regulator.yaml# unevaluatedProperties: false ab8500_ldo_aux6: - description: The voltage for the auxilary LDO regulator 6 + description: The voltage for the auxiliary LDO regulator 6 only present on AB8505 type: object $ref: ../regulator/regulator.yaml#
@@ -378,7 +378,7 @@ properties: # There is never any AUX7 regulator which is confusing ab8500_ldo_aux8: - description: The voltage for the auxilary LDO regulator 8 + description: The voltage for the auxiliary LDO regulator 8 only present on AB8505 type: object $ref: ../regulator/regulator.yaml#
Documentation/devicetree/bindings/mfd/stericsson,db8500-prcmu.yaml +1 -1
@@ -107,7 +107,7 @@ properties: $ref: ../regulator/regulator.yaml# db8500_vrf1: - description: RF transciever voltage regulator. + description: RF transceiver voltage regulator. type: object $ref: ../regulator/regulator.yaml#
Documentation/devicetree/bindings/mmc/pxa-mmc.txt +1 -1
@@ -9,7 +9,7 @@ Required properties: Optional properties: - marvell,detect-delay-ms: sets the detection delay timeout in ms. -In addition to the properties described in this docuent, the details +In addition to the properties described in this document, the details described in mmc.txt are supported. Examples:
Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt +1 -1
@@ -95,7 +95,7 @@ while in suspend. | card | -- CIRQ --> | hsmmc | -- IRQ --> | CPU | ------ ------- ----- -In suspend the fclk is off and the module is disfunctional. Even register reads +In suspend the fclk is off and the module is dysfunctional. Even register reads will fail. A small logic in the host will request fclk restore, when an external event is detected. Once the clock is restored, the host detects the event normally. Since am33xx doesn't have this line it never wakes from
Documentation/devicetree/bindings/net/brcm,bcm7445-switch-v4.0.txt +1 -1
@@ -1,4 +1,4 @@ -* Broadcom Starfighter 2 integrated swich +* Broadcom Starfighter 2 integrated switch See dsa/brcm,bcm7445-switch-v4.0.yaml for the documentation.
Documentation/devicetree/bindings/net/can/cc770.txt +1 -1
@@ -26,7 +26,7 @@ Optional properties: will be disabled. - bosch,slew-rate : slew rate of the CLKOUT signal. If not specified, - a resonable value will be calculated. + a reasonable value will be calculated. - bosch,disconnect-rx0-input : see data sheet.
Documentation/devicetree/bindings/net/dsa/brcm,sf2.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/net/dsa/brcm,sf2.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Broadcom Starfighter 2 integrated swich +title: Broadcom Starfighter 2 integrated switch maintainers: - Florian Fainelli <[email protected]>
Documentation/devicetree/bindings/net/ethernet-phy.yaml +1 -1
@@ -110,7 +110,7 @@ properties: $ref: /schemas/types.yaml#/definitions/flag description: If set, indicates that PHY will disable swap of the - TX/RX lanes. This property allows the PHY to work correcly after + TX/RX lanes. This property allows the PHY to work correctly after e.g. wrong bootstrap configuration caused by issues in PCB layout design.
Documentation/devicetree/bindings/net/mediatek-dwmac.yaml +1 -1
@@ -129,7 +129,7 @@ properties: type: boolean description: If present, indicates that MAC supports WOL(Wake-On-LAN), and MAC WOL will be enabled. - Otherwise, PHY WOL is perferred. + Otherwise, PHY WOL is preferred. required: - compatible
Documentation/devicetree/bindings/net/microchip,lan95xx.yaml +1 -1
@@ -33,7 +33,7 @@ properties: - usb424,9906 # SMSC9505A USB Ethernet Device (HAL) - usb424,9907 # SMSC9500 USB Ethernet Device (Alternate ID) - usb424,9908 # SMSC9500A USB Ethernet Device (Alternate ID) - - usb424,9909 # SMSC9512/9514 USB Hub & Ethernet Devic. ID) + - usb424,9909 # SMSC9512/9514 USB Hub & Ethernet Device ID) - usb424,9e00 # SMSC9500A USB Ethernet Device - usb424,9e01 # SMSC9505A USB Ethernet Device - usb424,9e08 # SMSC LAN89530 USB Ethernet Device
Documentation/devicetree/bindings/net/nfc/marvell,nci.yaml +2 -2
@@ -37,13 +37,13 @@ properties: type: boolean description: | For I2C type of connection. Specifies that the chip read event shall be - trigged on falling edge. + triggered on falling edge. i2c-int-rising: type: boolean description: | For I2C type of connection. Specifies that the chip read event shall be - trigged on rising edge. + triggered on rising edge. break-control: type: boolean
Documentation/devicetree/bindings/net/samsung-sxgbe.txt +2 -2
@@ -5,10 +5,10 @@ Required properties: - reg: Address and length of the register set for the device - interrupts: Should contain the SXGBE interrupts These interrupts are ordered by fixed and follows variable - trasmit DMA interrupts, receive DMA interrupts and lpi interrupt. + transmit DMA interrupts, receive DMA interrupts and lpi interrupt. index 0 - this is fixed common interrupt of SXGBE and it is always available. - index 1 to 25 - 8 variable trasmit interrupts, variable 16 receive interrupts + index 1 to 25 - 8 variable transmit interrupts, variable 16 receive interrupts and 1 optional lpi interrupt. - phy-mode: String, operation mode of the PHY interface. Supported values are: "sgmii", "xgmii".
Documentation/devicetree/bindings/net/snps,dwc-qos-ethernet.txt +1 -1
@@ -110,7 +110,7 @@ Optional properties: It depends on the SoC configuration. - snps,read-requests: Number of read requests that the AXI port can issue. It depends on the SoC configuration. -- snps,burst-map: Bitmap of allowed AXI burst lengts, with the LSB +- snps,burst-map: Bitmap of allowed AXI burst lengths, with the LSB representing 4, then 8 etc. - snps,txpbl: DMA Programmable burst length for the TX DMA - snps,rxpbl: DMA Programmable burst length for the RX DMA
Documentation/devicetree/bindings/net/sti-dwmac.txt +1 -1
@@ -21,7 +21,7 @@ Optional properties: MAC can generate it. - st,tx-retime-src: This specifies which clk is wired up to the mac for retimeing tx lines. This is totally board dependent and can take one of the - posssible values from "txclk", "clk_125" or "clkgen". + possible values from "txclk", "clk_125" or "clkgen". If not passed, the internal clock will be used by default. - sti-ethclk: this is the phy clock. - sti-clkconf: this is an extra sysconfig register, available in new SoCs,
Documentation/devicetree/bindings/net/xilinx_gmii2rgmii.txt +1 -1
@@ -7,7 +7,7 @@ Ethernet physical media devices (PHY) and the Gigabit Ethernet controller. This core can be used in all three modes of operation(10/100/1000 Mb/s). The Management Data Input/Output (MDIO) interface is used to configure the Speed of operation. This core can switch dynamically between the three -Different speed modes by configuring the conveter register through mdio write. +Different speed modes by configuring the converter register through mdio write. This converter sits between the ethernet MAC and the external phy. MAC <==> GMII2RGMII <==> RGMII_PHY
Documentation/devicetree/bindings/nios2/nios2.txt +1 -1
@@ -23,7 +23,7 @@ Required properties: - altr,tlb-num-ways: Specifies the number of set-associativity ways in the TLB. - altr,tlb-num-entries: Specifies the number of entries in the TLB. - altr,tlb-ptr-sz: Specifies size of TLB pointer. -- altr,has-mul: Specifies CPU hardware multipy support, should be 1. +- altr,has-mul: Specifies CPU hardware multiply support, should be 1. - altr,has-mmu: Specifies CPU support MMU support, should be 1. - altr,has-initda: Specifies CPU support initda instruction, should be 1. - altr,reset-addr: Specifies CPU reset address
Documentation/devicetree/bindings/nvmem/layouts/onie,tlv-layout.yaml +1 -1
@@ -14,7 +14,7 @@ description: infrastructure shall provide a non-volatile memory with a table whose the content is well specified and gives many information about the manufacturer (name, country of manufacture, etc) as well as device caracteristics (serial - number, hardware version, mac addresses, etc). The underlaying device type + number, hardware version, mac addresses, etc). The underlying device type (flash, EEPROM,...) is not specified. The exact location of each value is also dynamic and should be discovered at run time because it depends on the parameters the manufacturer decided to embed.
Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt +1 -1
@@ -14,7 +14,7 @@ Required properties: - #size-cells: Must be 0. The INNO USB2 PHY device should be a child node of peripheral controller that -contains the PHY configuration register, and each device suppports up to 2 PHY +contains the PHY configuration register, and each device supports up to 2 PHY ports which are represented as child nodes of INNO USB2 PHY device. Required properties for PHY port node:
Documentation/devicetree/bindings/phy/pistachio-usb-phy.txt +1 -1
@@ -8,7 +8,7 @@ Required properties: - clocks: Must contain an entry for each entry in clock-names. See ../clock/clock-bindings.txt for details. - clock-names: Must include "usb_phy". - - img,cr-top: Must constain a phandle to the CR_TOP syscon node. + - img,cr-top: Must contain a phandle to the CR_TOP syscon node. - img,refclk: Indicates the reference clock source for the USB PHY. See <dt-bindings/phy/phy-pistachio-usb.h> for a list of valid values.
Documentation/devicetree/bindings/phy/pxa1928-usb-phy.txt +1 -1
@@ -4,7 +4,7 @@ Required properties: - compatible: "marvell,pxa1928-usb-phy" or "marvell,pxa1928-hsic-phy" - reg: base address and length of the registers - clocks - A single clock. From common clock binding. -- #phys-cells: should be 0. From commmon phy binding. +- #phys-cells: should be 0. From common phy binding. - resets: reference to the reset controller Example:
Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml +1 -1
@@ -10,7 +10,7 @@ maintainers: - Heiko Stuebner <[email protected]> description: | - The Rockchip SoC has a MIPI CSI D-PHY based on an Innosilicon IP wich + The Rockchip SoC has a MIPI CSI D-PHY based on an Innosilicon IP which connects to the ISP1 (Image Signal Processing unit v1.0) for CSI cameras. properties:
Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml +1 -1
@@ -59,7 +59,7 @@ properties: description: GPIO to signal Type-C cable orientation for lane swap. If GPIO is active, lane 0 and lane 1 of SERDES will be swapped to - achieve the funtionality of an external type-C plug flip mux. + achieve the functionality of an external type-C plug flip mux. typec-dir-debounce-ms: minimum: 100
Documentation/devicetree/bindings/phy/ti-phy.txt +1 -1
@@ -62,7 +62,7 @@ Deprecated properties: - ctrl-module : phandle of the control module used by PHY driver to power on the PHY. -Recommended properies: +Recommended properties: - syscon-phy-power : phandle/offset pair. Phandle to the system control module and the register offset to power on/off the PHY.
Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml +1 -1
@@ -97,7 +97,7 @@ patternProperties: # It's pretty scary, but the basic idea is that: # - One node name can start with either s- or r- for PRCM nodes, # - Then, the name itself can be any repetition of <string>- (to - # accomodate with nodes like uart4-rts-cts-pins), where each + # accommodate with nodes like uart4-rts-cts-pins), where each # string can be either starting with 'p' but in a string longer # than 3, or something that doesn't start with 'p', # - Then, the bank name is optional and will be between pa and pg,
Documentation/devicetree/bindings/pinctrl/canaan,k210-fpioa.yaml +1 -1
@@ -11,7 +11,7 @@ maintainers: description: The Canaan Kendryte K210 SoC Fully Programmable IO Array (FPIOA) - controller allows assiging any of 256 possible functions to any of + controller allows assigning any of 256 possible functions to any of 48 IO pins of the SoC. Pin function configuration is performed on a per-pin basis.
Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml +1 -1
@@ -159,7 +159,7 @@ patternProperties: mediatek,pull-up-adv: description: | - Pull up setings for 2 pull resistors, R0 and R1. User can + Pull up settings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled.
Documentation/devicetree/bindings/pinctrl/mediatek,mt6795-pinctrl.yaml +1 -1
@@ -130,7 +130,7 @@ patternProperties: mediatek,pull-up-adv: description: | - Pull up setings for 2 pull resistors, R0 and R1. User can + Pull up settings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled.
Documentation/devicetree/bindings/pinctrl/mediatek,mt7981-pinctrl.yaml +2 -2
@@ -386,7 +386,7 @@ patternProperties: mediatek,pull-up-adv: description: | Valid arguments for 'mediatek,pull-up-adv' are '0', '1', '2', '3' - Pull up setings for 2 pull resistors, R0 and R1. Valid arguments + Pull up settings for 2 pull resistors, R0 and R1. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled.
@@ -398,7 +398,7 @@ patternProperties: mediatek,pull-down-adv: description: | Valid arguments for 'mediatek,pull-up-adv' are '0', '1', '2', '3' - Pull down setings for 2 pull resistors, R0 and R1. Valid arguments + Pull down settings for 2 pull resistors, R0 and R1. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled.
Documentation/devicetree/bindings/pinctrl/mediatek,mt7986-pinctrl.yaml +2 -2
@@ -332,7 +332,7 @@ patternProperties: mediatek,pull-up-adv: description: | Valid arguments for 'mediatek,pull-up-adv' are '0', '1', '2', '3' - Pull up setings for 2 pull resistors, R0 and R1. Valid arguments + Pull up settings for 2 pull resistors, R0 and R1. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled.
@@ -344,7 +344,7 @@ patternProperties: mediatek,pull-down-adv: description: | Valid arguments for 'mediatek,pull-up-adv' are '0', '1', '2', '3' - Pull down setings for 2 pull resistors, R0 and R1. Valid arguments + Pull down settings for 2 pull resistors, R0 and R1. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled.
Documentation/devicetree/bindings/pinctrl/mediatek,mt8183-pinctrl.yaml +1 -1
@@ -143,7 +143,7 @@ patternProperties: mediatek,pull-up-adv: description: | - Pull up setings for 2 pull resistors, R0 and R1. User can + Pull up settings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled.
Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml +1 -1
@@ -149,7 +149,7 @@ patternProperties: deprecated: true description: | DEPRECATED: Please use bias-pull-up instead. - Pull up setings for 2 pull resistors, R0 and R1. User can + Pull up settings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled.
Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt +1 -1
@@ -38,7 +38,7 @@ Valid values for function properties are: gpio, lpm-control-in, fps-out, 32k-out, sd0-dvs-in, sd1-dvs-in, reference-out -Theres is also customised properties for the GPIO1, GPIO2 and GPIO3. These +There are also customised properties for the GPIO1, GPIO2 and GPIO3. These customised properties are required to configure FPS configuration parameters of these GPIOs. Please refer <devicetree/bindings/mfd/max77620.txt> for more detail of Flexible Power Sequence (FPS).
Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt +1 -1
@@ -40,7 +40,7 @@ on default. Valid values for function properties are: gpio. -Theres is also not customised properties for any GPIO. +There are also not customised properties for any GPIO. Example: --------
Documentation/devicetree/bindings/pinctrl/sprd,pinctrl.txt +1 -1
@@ -8,7 +8,7 @@ to configure for some global common configuration, such as domain pad driving level, system control select and so on ("domain pad driving level": One pin can output 3.0v or 1.8v, depending on the related domain pad driving selection, if the related domain pad -slect 3.0v, then the pin can output 3.0v. "system control" is used +select 3.0v, then the pin can output 3.0v. "system control" is used to choose one function (like: UART0) for which system, since we have several systems (AP/CP/CM4) on one SoC.).
Documentation/devicetree/bindings/pmem/pmem-region.txt +2 -2
@@ -19,7 +19,7 @@ Required properties: - compatible = "pmem-region" - reg = <base, size>; - The reg property should specificy an address range that is + The reg property should specify an address range that is translatable to a system physical address range. This address range should be mappable as normal system memory would be (i.e cacheable).
@@ -30,7 +30,7 @@ Required properties: node implies no special relationship between the two ranges. Optional properties: - - Any relevant NUMA assocativity properties for the target platform. + - Any relevant NUMA associativity properties for the target platform. - volatile; This property indicates that this region is actually backed by non-persistent memory. This lets the OS know that it
Documentation/devicetree/bindings/power/renesas,sysc-rmobile.yaml +1 -1
@@ -58,7 +58,7 @@ $defs: pd-node: type: object description: - PM domain node representing a PM domain. This node hould be named by + PM domain node representing a PM domain. This node should be named by the real power area name, and thus its name should be unique. properties:
Documentation/devicetree/bindings/power/supply/sbs,sbs-manager.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/power/supply/sbs,sbs-manager.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: SBS compliant manger +title: SBS compliant manager maintainers: - Sebastian Reichel <[email protected]>
Documentation/devicetree/bindings/powerpc/fsl/cpus.txt +1 -1
@@ -28,6 +28,6 @@ PROPERTIES Snoop ID Port Mapping registers, which are part of the CoreNet Coherency fabric (CCF), provide a CoreNet Coherency Subdomain ID/CoreNet Snoop ID to cpu mapping functions. Certain bits from - these registers should be set if the coresponding CPU should be + these registers should be set if the corresponding CPU should be snooped. This property defines a bitmask which selects the bit that should be set if this cpu should be snooped.
Documentation/devicetree/bindings/powerpc/fsl/dcsr.txt +2 -2
@@ -185,10 +185,10 @@ PROPERTIES with distinct functionality. The first register range describes the CoreNet Debug Controller - functionalty to perform transaction and transaction attribute matches. + functionality to perform transaction and transaction attribute matches. The second register range describes the CoreNet Debug Controller - functionalty to trigger event notifications and debug traces. + functionality to trigger event notifications and debug traces. EXAMPLE dcsr-corenet {
Documentation/devicetree/bindings/powerpc/fsl/raideng.txt +1 -1
@@ -60,7 +60,7 @@ Optional property: - fsl,liodn: Specifies the LIODN to be used for Job Ring. This property is normally set by firmware. Value is of 12-bits which is the LIODN number for this JR. - This property is used by the IOMMU (PAMU) to distinquish + This property is used by the IOMMU (PAMU) to distinguish transactions from this JR and than be able to do address translation & protection accordingly.
Documentation/devicetree/bindings/powerpc/nintendo/gamecube.txt +1 -1
@@ -42,7 +42,7 @@ Nintendo GameCube device tree - compatible : should be "nintendo,flipper-pic" -1.c) The Digital Signal Procesor (DSP) node +1.c) The Digital Signal Processor (DSP) node Represents the digital signal processor interface, designed to offload audio related tasks.
Documentation/devicetree/bindings/powerpc/nintendo/wii.txt +1 -1
@@ -53,7 +53,7 @@ Nintendo Wii device tree - compatible : should be "nintendo,flipper-pic" - interrupt-controller -1.c) The Digital Signal Procesor (DSP) node +1.c) The Digital Signal Processor (DSP) node Represents the digital signal processor interface, designed to offload audio related tasks.
Documentation/devicetree/bindings/pwm/snps,dw-apb-timers-pwm2.yaml +1 -1
@@ -18,7 +18,7 @@ description: The IP block has a version register so this can be used for detection instead of having to encode the IP version number in the device tree - comaptible. + compatible. allOf: - $ref: pwm.yaml#
Documentation/devicetree/bindings/regulator/regulator-max77620.txt +1 -1
@@ -35,7 +35,7 @@ information for that regulator. The definition for each of these nodes is defined using the standard binding for regulators found at <Documentation/devicetree/bindings/regulator/regulator.txt>. -Theres are also additional properties for SD/LDOs. These additional properties +There are also additional properties for SD/LDOs. These additional properties are required to configure FPS configuration parameters for SDs and LDOs. Please refer <devicetree/bindings/mfd/max77620.txt> for more detail of Flexible Power Sequence (FPS).
Documentation/devicetree/bindings/regulator/regulator.yaml +4 -4
@@ -126,7 +126,7 @@ properties: regulator-oc-error-microamp: description: Set over current error limit. This is a limit where part of - the hardware propably is malfunctional and damage prevention is requested. + the hardware probably is malfunctional and damage prevention is requested. Zero can be passed to disable error detection and value '1' indicates that detection should be enabled but limit setting can be omitted.
@@ -146,7 +146,7 @@ properties: regulator-ov-error-microvolt: description: Set over voltage error limit. This is a limit where part of - the hardware propably is malfunctional and damage prevention is requested + the hardware probably is malfunctional and damage prevention is requested Zero can be passed to disable error detection and value '1' indicates that detection should be enabled but limit setting can be omitted. Limit is given as microvolt offset from voltage set to regulator.
@@ -168,7 +168,7 @@ properties: regulator-uv-error-microvolt: description: Set under voltage error limit. This is a limit where part of - the hardware propably is malfunctional and damage prevention is requested + the hardware probably is malfunctional and damage prevention is requested Zero can be passed to disable error detection and value '1' indicates that detection should be enabled but limit setting can be omitted. Limit is given as microvolt offset from voltage set to regulator.
@@ -189,7 +189,7 @@ properties: regulator-temp-error-kelvin: description: Set over temperature error limit. This is a limit where part of - the hardware propably is malfunctional and damage prevention is requested + the hardware probably is malfunctional and damage prevention is requested Zero can be passed to disable error detection and value '1' indicates that detection should be enabled but limit setting can be omitted.
Documentation/devicetree/bindings/regulator/richtek,rt5190a-regulator.yaml +1 -1
@@ -11,7 +11,7 @@ maintainers: description: | The RT5190A integrates 1 channel buck controller, 3 channels high efficiency - synchronous buck converters, 1 LDO, I2C control interface and peripherial + synchronous buck converters, 1 LDO, I2C control interface and peripheral logical control. It also supports mute AC OFF depop sound and quick setting storage while
Documentation/devicetree/bindings/regulator/vctrl.txt +1 -1
@@ -21,7 +21,7 @@ Optional properties: margin from the expected value for a given control voltage. On larger voltage decreases this can occur undesiredly since the output voltage does not adjust - inmediately to changes in the control voltage. To + immediately to changes in the control voltage. To avoid this situation the vctrl driver breaks down larger voltage decreases into multiple steps, where each step is within the OVP threshold.
Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml +1 -1
@@ -102,7 +102,7 @@ patternProperties: caches. Each of the TCMs can be enabled or disabled independently and either of them can be configured to appear at that R5F's address 0x0. - The cores do not use an MMU, but has a Region Address Translater + The cores do not use an MMU, but has a Region Address Translator (RAT) module that is accessible only from the R5Fs for providing translations between 32-bit CPU addresses into larger system bus addresses. Cache and memory access settings are provided through a
Documentation/devicetree/bindings/reset/ti-syscon-reset.txt +1 -1
@@ -43,7 +43,7 @@ Required properties: Cell #6 : bit position of the reset in the reset status register Cell #7 : Flags used to control reset behavior, - availible flags defined in the DT include + available flags defined in the DT include file <dt-bindings/reset/ti-syscon.h> SysCon Reset Consumer Nodes
Documentation/devicetree/bindings/rng/omap_rng.yaml +2 -2
@@ -30,8 +30,8 @@ properties: clocks: minItems: 1 items: - - description: EIP150 gatable clock - - description: Main gatable clock + - description: EIP150 gateable clock + - description: Main gateable clock clock-names: minItems: 1
Documentation/devicetree/bindings/rtc/rtc-cmos.txt +1 -1
@@ -10,7 +10,7 @@ Optional properties: - ctrl-reg : Contains the initial value of the control register also called "Register B". - freq-reg : Contains the initial value of the frequency register also - called "Regsiter A". + called "Register A". "Register A" and "B" are usually initialized by the firmware (BIOS for instance). If this is not done, it can be performed by the driver.
Documentation/devicetree/bindings/serial/nvidia,tegra20-hsuart.txt +1 -1
@@ -49,7 +49,7 @@ Baud Rate tolerance: listed below. 0 to 9600 has 1% deviation 9600 to 115200 2% deviation - This slight deviation is expcted and Tegra UART is expected to handle it. Due + This slight deviation is expected and Tegra UART is expected to handle it. Due to the issue stated above, baud rate on Tegra UART should be set equal to or above deviation observed for avoiding frame errors. Property should be set like this
Documentation/devicetree/bindings/serial/st-asc.txt +1 -1
@@ -8,7 +8,7 @@ Required properties: Optional properties: - st,hw-flow-ctrl bool flag to enable hardware flow control. -- st,force-m1 bool flat to force asc to be in Mode-1 recommeded +- st,force-m1 bool flat to force asc to be in Mode-1 recommended for high bit rates (above 19.2K) Example: serial@fe440000{
Documentation/devicetree/bindings/soc/mediatek/mediatek,mt7986-wo-ccif.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: The MediaTek wo-ccif provides a configuration interface for WED WO - controller used to perfrom offload rx packet processing (e.g. 802.11 + controller used to perform offload rx packet processing (e.g. 802.11 aggregation packet reordering or rx header translation) on MT7986 soc. properties:
Documentation/devicetree/bindings/soc/microchip/microchip,mpfs-sys-controller.yaml +1 -1
@@ -12,7 +12,7 @@ maintainers: description: | PolarFire SoC devices include a microcontroller acting as the system controller, which provides "services" to the main processor and to the FPGA fabric. These - services include hardware rng, reprogramming of the FPGA and verfification of the + services include hardware rng, reprogramming of the FPGA and verification of the eNVM contents etc. More information on these services can be found online, at https://onlinedocs.microchip.com/pr/GUID-1409CF11-8EF9-4C24-A94E-70979A688632-en-US-1/index.html
Documentation/devicetree/bindings/soc/qcom/qcom,aoss-qmp.yaml +1 -1
@@ -77,7 +77,7 @@ patternProperties: description: The AOSS side channel also provides the controls for three cooling devices, these are expressed as subnodes of the QMP node. The name of the node is - used to identify the resource and must therefor be "cx", "mx" or "ebi". + used to identify the resource and must therefore be "cx", "mx" or "ebi". properties: "#cooling-cells":
Documentation/devicetree/bindings/sound/axentia,tse850-pcm5142.txt +1 -1
@@ -29,7 +29,7 @@ The schematics explaining the gpios are as follows: IN2 +---o--+------------+--o---+ OUT2 loop2 relays -The 'loop1' gpio pin controlls two relays, which are either in loop position, +The 'loop1' gpio pin controls two relays, which are either in loop position, meaning that input and output are directly connected, or they are in mixer position, meaning that the signal is passed through the 'Sum' mixer. Similarly for 'loop2'.
Documentation/devicetree/bindings/sound/cs35l35.txt +1 -1
@@ -110,7 +110,7 @@ Optional Monitor Signal Format sub-node: See Sections 4.8.2 through 4.8.4 Serial-Port Control in the Datasheet - -cirrus,monitor-signal-format : Sub-node for the Monitor Signaling Formating + -cirrus,monitor-signal-format : Sub-node for the Monitor Signaling Formatting on the I2S Port. Each of the 3 8 bit values in the array contain the settings for depth, location, and frame.
Documentation/devicetree/bindings/sound/cs35l36.txt +1 -1
@@ -33,7 +33,7 @@ Optional properties: one amplifier in the system. If more than one it is best to Hi-Z the ASP port to prevent bus contention on the output signal - - cirrus,boost-ctl-select : Boost conerter control source selection. + - cirrus,boost-ctl-select : Boost converter control source selection. Selects the source of the BST_CTL target VBST voltage for the boost converter to generate. 0x00 - Control Port Value
Documentation/devicetree/bindings/sound/cs53l30.txt +1 -1
@@ -30,7 +30,7 @@ Optional properties: * frame using two different ways: * 1) Normal I2S mode on two data pins -- each SDOUT * carries 2-channel data in the same time. - * 2) TDM mode on one signle data pin -- SDOUT1 carries + * 2) TDM mode on one single data pin -- SDOUT1 carries * 4-channel data per frame. Example:
Documentation/devicetree/bindings/sound/fsl,esai.txt +1 -1
@@ -44,7 +44,7 @@ Required properties: - fsl,esai-synchronous: This is a boolean property. If present, indicating that ESAI would work in the synchronous mode, which means all the settings for Receiving would be - duplicated from Transmition related registers. + duplicated from Transmission related registers. Optional properties:
Documentation/devicetree/bindings/sound/mediatek,mt8188-afe.yaml +1 -1
@@ -135,7 +135,7 @@ patternProperties: maxItems: 16 description: This is a list of channel IDs which should be disabled. - By default, all data received from ETDM pins will be outputed to + By default, all data received from ETDM pins will be outputted to memory. etdm in supports disable_out in direct mode(w/o interconn), so user can disable the specified channels by the property. uniqueItems: true
Documentation/devicetree/bindings/sound/mt2701-afe-pcm.txt +1 -1
@@ -1,7 +1,7 @@ Mediatek AFE PCM controller for mt2701 Required properties: -- compatible: should be one of the followings. +- compatible: should be one of the following. - "mediatek,mt2701-audio" - "mediatek,mt7622-audio" - interrupts: should contain AFE and ASYS interrupts
Documentation/devicetree/bindings/sound/mt8195-afe-pcm.yaml +2 -2
@@ -111,7 +111,7 @@ patternProperties: $ref: /schemas/types.yaml#/definitions/uint32 description: | etdm modules can share the same external clock pin. Specify - which etdm clock source is required by this etdm in moudule. + which etdm clock source is required by this etdm in module. enum: - 0 # etdm1_in - 1 # etdm2_in
@@ -122,7 +122,7 @@ patternProperties: $ref: /schemas/types.yaml#/definitions/uint32 description: | etdm modules can share the same external clock pin. Specify - which etdm clock source is required by this etdm out moudule. + which etdm clock source is required by this etdm out module. enum: - 0 # etdm1_in - 1 # etdm2_in
Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-analog.txt +1 -1
@@ -35,7 +35,7 @@ Optional Properties: - qcom,mbhc-vthreshold-low: Array of 5 threshold voltages in mV for 5 buttons detection on headset when the mbhc is powered up by internal current source, this is a low power. - - qcom,mbhc-vthreshold-high: Array of 5 thresold voltages in mV for 5 buttons + - qcom,mbhc-vthreshold-high: Array of 5 threshold voltages in mV for 5 buttons detection on headset when mbhc is powered up from micbias. - qcom,micbias-lvl: Voltage (mV) for Mic Bias
Documentation/devicetree/bindings/sound/renesas,rsnd.txt +1 -1
@@ -94,7 +94,7 @@ see "Example: simple sound card for Asynchronous mode" [xx]ch [yy]ch ------> [CTU] --------> -CTU can convert [xx]ch to [yy]ch, or exchange outputed channel. +CTU can convert [xx]ch to [yy]ch, or exchange outputted channel. CTU conversion needs matrix settings. For more detail information, see below
Documentation/devicetree/bindings/sound/rockchip,rk3288-hdmi-analog.txt +1 -1
@@ -12,7 +12,7 @@ Required properties: source. For this driver the first string should always be "Analog". -Optionnal properties: +Optional properties: - rockchip,hp-en-gpios = The phandle of the GPIO that power up/down the headphone (when the analog output is an headphone). - rockchip,hp-det-gpios = The phandle of the GPIO that detects the headphone
Documentation/devicetree/bindings/sound/rt5663.txt +1 -1
@@ -28,7 +28,7 @@ Optional properties: If the value is 0, it means the impedance sensing is not supported. - "realtek,impedance_sensing_table" The matrix rows of the impedance sensing table are consisted by impedance - minimum, impedance maximun, volume, DC offset w/o and w/ mic of each L and + minimum, impedance maximum, volume, DC offset w/o and w/ mic of each L and R channel accordingly. Example is shown as following. < 0 300 7 0xffd160 0xffd1c0 0xff8a10 0xff8ab0 301 65535 4 0xffe470 0xffe470 0xffb8e0 0xffb8e0>
Documentation/devicetree/bindings/sound/serial-midi.yaml +1 -1
@@ -20,7 +20,7 @@ description: parent serial device. If the standard MIDI baud of 31.25 kBaud is needed (as would be the case if interfacing with arbitrary external MIDI devices), configure the clocks of the parent serial device so that a requested baud of 38.4 kBaud - resuts in the standard MIDI baud rate, and set the 'current-speed' property to 38400 (default) + results in the standard MIDI baud rate, and set the 'current-speed' property to 38400 (default) properties: compatible:
Documentation/devicetree/bindings/sound/sprd-pcm.txt +1 -1
@@ -1,4 +1,4 @@ -* Spreadtrum DMA platfrom bindings +* Spreadtrum DMA platform bindings Required properties: - compatible: Should be "sprd,pcm-platform".
Documentation/devicetree/bindings/sound/st,stm32-sai.yaml +1 -1
@@ -63,7 +63,7 @@ patternProperties: additionalProperties: false description: Two subnodes corresponding to SAI sub-block instances A et B - can be defined. Subnode can be omitted for unsused sub-block. + can be defined. Subnode can be omitted for unused sub-block. properties: compatible:
Documentation/devicetree/bindings/sound/ti,j721e-cpb-ivi-audio.yaml +1 -1
@@ -13,7 +13,7 @@ maintainers: description: | The Infotainment board plugs into the Common Processor Board, the support of the - extension board is extending the CPB audio support, decribed in: + extension board is extending the CPB audio support, described in: sound/ti,j721e-cpb-audio.txt The audio support on the Infotainment Expansion Board consists of McASP0
Documentation/devicetree/bindings/sound/ti,tas2781.yaml +1 -1
@@ -29,7 +29,7 @@ properties: reg: description: I2C address, in multiple tas2781s case, all the i2c address - aggreate as one Audio Device to support multiple audio slots. + aggregate as one Audio Device to support multiple audio slots. maxItems: 8 minItems: 1 items:
Documentation/devicetree/bindings/sound/tlv320adcx140.yaml +1 -1
@@ -32,7 +32,7 @@ properties: reg: maxItems: 1 description: | - I2C addresss of the device can be one of these 0x4c, 0x4d, 0x4e or 0x4f + I2C address of the device can be one of these 0x4c, 0x4d, 0x4e or 0x4f reset-gpios: maxItems: 1
Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml +2 -2
@@ -159,7 +159,7 @@ properties: qcom,ports-hstart: $ref: /schemas/types.yaml#/definitions/uint8-array description: - Identifying lowerst numbered coloum in SoundWire Frame, + Identifying lowerst numbered column in SoundWire Frame, i.e. left edge of the Transport sub-frame for each port. Out ports followed by In ports. Value of 0xff indicates that this option is not implemented
@@ -176,7 +176,7 @@ properties: qcom,ports-hstop: $ref: /schemas/types.yaml#/definitions/uint8-array description: - Identifying highest numbered coloum in SoundWire Frame, + Identifying highest numbered column in SoundWire Frame, i.e. the right edge of the Transport sub-frame for each port. Out ports followed by In ports. Value of 0xff indicates that this option is not implemented
Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt +2 -2
@@ -1,4 +1,4 @@ -Broadcom BCM2835 auxiliar SPI1/2 controller +Broadcom BCM2835 auxiliary SPI1/2 controller The BCM2835 contains two forms of SPI master controller, one known simply as SPI0, and the other known as the "Universal SPI Master"; part of the
@@ -9,7 +9,7 @@ Required properties: - reg: Should contain register location and length for the spi block - interrupts: Should contain shared interrupt of the aux block - clocks: The clock feeding the SPI controller - needs to - point to the auxiliar clock driver of the bcm2835, + point to the auxiliary clock driver of the bcm2835, as this clock will enable the output gate for the specific clock. - cs-gpios: the cs-gpios (native cs is NOT supported)
Documentation/devicetree/bindings/spi/brcm,spi-bcm-qspi.yaml +2 -2
@@ -12,7 +12,7 @@ maintainers: description: | The Broadcom SPI controller is a SPI master found on various SOCs, including - BRCMSTB (BCM7XXX), Cygnus, NSP and NS2. The Broadcom Master SPI hw IP consits + BRCMSTB (BCM7XXX), Cygnus, NSP and NS2. The Broadcom Master SPI hw IP consists of: MSPI : SPI master controller can read and write to a SPI slave device BSPI : Broadcom SPI in combination with the MSPI hw IP provides acceleration
@@ -20,7 +20,7 @@ description: | io with 3-byte and 4-byte addressing support. Supported Broadcom SoCs have one instance of MSPI+BSPI controller IP. - MSPI master can be used wihout BSPI. BRCMSTB SoCs have an additional instance + MSPI master can be used without BSPI. BRCMSTB SoCs have an additional instance of a MSPI master without the BSPI to use with non flash slave devices that use SPI protocol.
Documentation/devicetree/bindings/spi/omap-spi.yaml +1 -1
@@ -68,7 +68,7 @@ properties: dma-names: description: List of DMA request names. These strings correspond 1:1 with - the DMA sepecifiers listed in dmas. The string names is to be + the DMA specifiers listed in dmas. The string names is to be "rxN" and "txN" for RX and TX requests, respectively. Where N is the chip select number. minItems: 1
Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt +1 -1
@@ -85,7 +85,7 @@ Optional properties: which the soctherm hardware will assert the thermal trigger signal to the Power Management IC, which can be configured to reset or shutdown the device. It is an array of pairs where each pair represents a tsensor id followed by a - temperature in milli Celcius. In the absence of this property the critical + temperature in milli Celsius. In the absence of this property the critical trip point will be used for thermtrip temperature. Note:
Documentation/devicetree/bindings/timer/snps,arc-timer.txt +1 -1
@@ -1,7 +1,7 @@ Synopsys ARC Local Timer with Interrupt Capabilities - Found on all ARC CPUs (ARC700/ARCHS) - Can be optionally programmed to interrupt on Limit -- Two idential copies TIMER0 and TIMER1 exist in ARC cores and historically +- Two identical copies TIMER0 and TIMER1 exist in ARC cores and historically TIMER0 used as clockevent provider (true for all ARC cores) TIMER1 used for clocksource (mandatory for ARC700, optional for ARC HS)
Documentation/devicetree/bindings/trivial-devices.yaml +4 -4
@@ -193,13 +193,13 @@ properties: - maxim,max1237 # Temperature Sensor, I2C interface - maxim,max1619 - # 10-bit 10 kOhm linear programable voltage divider + # 10-bit 10 kOhm linear programmable voltage divider - maxim,max5481 - # 10-bit 50 kOhm linear programable voltage divider + # 10-bit 50 kOhm linear programmable voltage divider - maxim,max5482 - # 10-bit 10 kOhm linear programable variable resistor + # 10-bit 10 kOhm linear programmable variable resistor - maxim,max5483 - # 10-bit 50 kOhm linear programable variable resistor + # 10-bit 50 kOhm linear programmable variable resistor - maxim,max5484 # PECI-to-I2C translator for PECI-to-SMBus/I2C protocol conversion - maxim,max6621
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.yaml +1 -1
@@ -167,7 +167,7 @@ properties: at RTL is 0, so this property only affects siTD. If this property is not set, the max packet size is 1023 bytes, and - if the total of packet size for pervious transactions are more than + if the total of packet size for previous transactions are more than 256 bytes, it can't accept any transactions within this frame. The use case is single transaction, but higher frame rate.
Documentation/devicetree/bindings/usb/fsl,imx8mp-dwc3.yaml +1 -1
@@ -52,7 +52,7 @@ properties: fsl,permanently-attached: type: boolean description: - Indicates if the device atached to a downstream port is + Indicates if the device attached to a downstream port is permanently attached. fsl,disable-port-power-control:
Documentation/devicetree/bindings/usb/msm-hsusb.txt +1 -1
@@ -53,7 +53,7 @@ Optional properties: - dr_mode: One of "host", "peripheral" or "otg". Defaults to "otg" - switch-gpio: A phandle + gpio-specifier pair. Some boards are using Dual - SPDT USB Switch, witch is cotrolled by GPIO to de/multiplex + SPDT USB Switch, witch is controlled by GPIO to de/multiplex D+/D- USB lines between connectors. - qcom,phy-init-sequence: PHY configuration sequence values. This is related to Device
Documentation/devicetree/bindings/usb/richtek,rt1719.yaml +1 -1
@@ -10,7 +10,7 @@ maintainers: - ChiYuan Huang <[email protected]> description: | - The RT1719 is a sink-only USB Type-C contoller that complies with the latest + The RT1719 is a sink-only USB Type-C controller that complies with the latest USB Type-C and PD standards. It does the USB Type-C detection including attach and orientation. It integrates the physical layer of the USB BMC power delivery protocol to allow up to 100W of power. The BMC PD block enables full
Signature · 1 line
2.34.1
Re: [PATCH 2/3] dt-bindings: Fix typos
Quoted 161 lines · Bjorn Helgaas
From: Bjorn Helgaas <[email protected]>
Fix typos in
Documentation/devicetree/bindings. The changes are in descriptions or comments where they shouldn't affect functionality.Signed-off-by Bjorn Helgaas <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 4 ++-- .../arm/marvell/cp110-system-controller.txt | 8 ++++---- .../bindings/arm/mediatek/mediatek,mipi0a.txt | 2 +- .../bindings/arm/mediatek/mediatek,vcodecsys.txt | 2 +- Documentation/devicetree/bindings/arm/sunxi.yaml | 4 ++-- .../devicetree/bindings/ata/pata-common.yaml | 2 +- .../devicetree/bindings/bus/brcm,gisb-arb.yaml | 2 +- .../bindings/bus/nvidia,tegra210-aconnect.yaml | 4 ++-- .../clock/allwinner,sun4i-a10-osc-clk.yaml | 2 +- .../devicetree/bindings/clock/alphascale,acc.txt | 4 ++-- .../devicetree/bindings/clock/keystone-pll.txt | 2 +- .../devicetree/bindings/clock/lpc1850-ccu.txt | 2 +- .../bindings/clock/lpc1850-creg-clk.txt | 4 ++-- .../devicetree/bindings/clock/maxim,max9485.txt | 2 +- .../bindings/clock/qcom,gcc-sm8450.yaml | 2 +- .../bindings/clock/qcom,kpss-acc-v1.yaml | 2 +- .../bindings/clock/sprd,sc9863a-clk.yaml | 2 +- .../devicetree/bindings/clock/ti/mux.txt | 2 +- .../devicetree/bindings/clock/vf610-clock.txt | 2 +- .../bindings/clock/xlnx,zynqmp-clk.txt | 2 +- .../bindings/connector/usb-connector.yaml | 2 +- .../devfreq/event/samsung,exynos-ppmu.yaml | 2 +- .../bindings/display/atmel/hlcdc-dc.txt | 2 +- .../display/bridge/snps,dw-mipi-dsi.yaml | 2 +- .../bindings/display/cirrus,clps711x-fb.txt | 2 +- .../bindings/display/msm/qcom,mdss.yaml | 2 +- .../display/panel/olimex,lcd-olinuxino.yaml | 2 +- .../bindings/display/panel/panel-common.yaml | 2 +- .../display/tegra/nvidia,tegra124-sor.yaml | 2 +- .../devicetree/bindings/dma/ingenic,dma.yaml | 2 +- .../bindings/dma/nvidia,tegra20-apbdma.txt | 2 +- .../devicetree/bindings/dma/qcom,bam-dma.yaml | 2 +- .../bindings/dma/stericsson,dma40.yaml | 2 +- .../devicetree/bindings/fpga/fpga-region.txt | 4 ++-- .../devicetree/bindings/gpio/gpio-xgene-sb.txt | 2 +- .../bindings/gpio/snps,dw-apb-gpio.yaml | 2 +- .../devicetree/bindings/gpio/ti,omap-gpio.yaml | 4 ++-- .../devicetree/bindings/hwmon/adi,adm1177.yaml | 2 +- .../bindings/hwmon/adi,axi-fan-control.yaml | 2 +- .../devicetree/bindings/hwmon/adi,ltc2992.yaml | 2 +- .../bindings/hwmon/aspeed-pwm-tacho.txt | 2 +- Documentation/devicetree/bindings/hwmon/lm87.txt | 2 +- .../devicetree/bindings/hwmon/ltq-cputemp.txt | 2 +- .../bindings/hwmon/moortec,mr75203.yaml | 2 +- .../bindings/hwmon/npcm750-pwm-fan.txt | 2 +- .../bindings/hwmon/sensirion,shtc1.yaml | 2 +- .../devicetree/bindings/hwmon/ti,tmp513.yaml | 2 +- .../devicetree/bindings/hwmon/ti,tps23861.yaml | 2 +- .../devicetree/bindings/i2c/i2c-sprd.txt | 2 +- .../bindings/iio/adc/xlnx,zynqmp-ams.yaml | 2 +- .../devicetree/bindings/iio/cdc/adi,ad7150.yaml | 2 +- .../devicetree/bindings/iio/common.yaml | 2 +- .../bindings/iio/frequency/adi,admv1014.yaml | 2 +- .../bindings/iio/humidity/ti,hdc2010.yaml | 2 +- .../iio/pressure/honeywell,mprls0025pa.yaml | 2 +- .../bindings/iio/proximity/ams,as3935.yaml | 2 +- .../devicetree/bindings/iio/st,st-sensors.yaml | 2 +- .../bindings/input/rmi4/rmi_2d_sensor.txt | 4 ++-- .../bindings/input/touchscreen/stmpe.txt | 2 +- .../bindings/input/touchscreen/tsc2007.txt | 2 +- .../interrupt-controller/arm,gic-v3.yaml | 2 +- .../brcm,bcm2835-armctrl-ic.txt | 2 +- .../brcm,bcm7120-l2-intc.yaml | 2 +- .../backlight/mediatek,mt6370-backlight.yaml | 2 +- .../devicetree/bindings/leds/leds-lp55xx.yaml | 4 ++-- .../devicetree/bindings/leds/leds-qcom-lpg.yaml | 2 +- .../bindings/mailbox/brcm,iproc-flexrm-mbox.txt | 2 +- .../bindings/mailbox/ti,omap-mailbox.yaml | 2 +- .../bindings/media/i2c/toshiba,tc358746.yaml | 2 +- .../devicetree/bindings/media/i2c/tvp5150.txt | 2 +- .../media/mediatek,vcodec-subdev-decoder.yaml | 2 +- .../memory-controllers/mediatek,smi-larb.yaml | 2 +- .../memory-controllers/rockchip,rk3399-dmc.yaml | 4 ++-- .../memory-controllers/xlnx,zynq-ddrc-a05.yaml | 2 +- .../devicetree/bindings/mfd/aspeed-lpc.yaml | 2 +- .../bindings/mfd/rohm,bd9576-pmic.yaml | 4 ++-- .../bindings/mfd/stericsson,ab8500.yaml | 16 ++++++++-------- .../bindings/mfd/stericsson,db8500-prcmu.yaml | 2 +- .../devicetree/bindings/mmc/pxa-mmc.txt | 2 +- .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 2 +- .../bindings/net/brcm,bcm7445-switch-v4.0.txt | 2 +- .../devicetree/bindings/net/can/cc770.txt | 2 +- .../devicetree/bindings/net/dsa/brcm,sf2.yaml | 2 +- .../devicetree/bindings/net/ethernet-phy.yaml | 2 +- .../devicetree/bindings/net/mediatek-dwmac.yaml | 2 +- .../bindings/net/microchip,lan95xx.yaml | 2 +- .../devicetree/bindings/net/nfc/marvell,nci.yaml | 4 ++-- .../devicetree/bindings/net/samsung-sxgbe.txt | 4 ++-- .../bindings/net/snps,dwc-qos-ethernet.txt | 2 +- .../devicetree/bindings/net/sti-dwmac.txt | 2 +- .../bindings/net/xilinx_gmii2rgmii.txt | 2 +- .../devicetree/bindings/nios2/nios2.txt | 2 +- .../bindings/nvmem/layouts/onie,tlv-layout.yaml | 2 +- .../bindings/phy/phy-hisi-inno-usb2.txt | 2 +- .../bindings/phy/pistachio-usb-phy.txt | 2 +- .../devicetree/bindings/phy/pxa1928-usb-phy.txt | 2 +- .../bindings/phy/rockchip-inno-csi-dphy.yaml | 2 +- .../bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- Documentation/devicetree/bindings/phy/ti-phy.txt | 2 +- .../pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 2 +- .../bindings/pinctrl/canaan,k210-fpioa.yaml | 2 +- .../pinctrl/mediatek,mt6779-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt6795-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt7981-pinctrl.yaml | 4 ++-- .../pinctrl/mediatek,mt7986-pinctrl.yaml | 4 ++-- .../pinctrl/mediatek,mt8183-pinctrl.yaml | 2 +- .../pinctrl/mediatek,mt8365-pinctrl.yaml | 2 +- .../bindings/pinctrl/pinctrl-max77620.txt | 2 +- .../bindings/pinctrl/pinctrl-rk805.txt | 2 +- .../devicetree/bindings/pinctrl/sprd,pinctrl.txt | 2 +- .../devicetree/bindings/pmem/pmem-region.txt | 4 ++-- .../bindings/power/renesas,sysc-rmobile.yaml | 2 +- .../bindings/power/supply/sbs,sbs-manager.yaml | 2 +- .../devicetree/bindings/powerpc/fsl/cpus.txt | 2 +- .../devicetree/bindings/powerpc/fsl/dcsr.txt | 4 ++-- .../devicetree/bindings/powerpc/fsl/raideng.txt | 2 +- .../bindings/powerpc/nintendo/gamecube.txt | 2 +- .../devicetree/bindings/powerpc/nintendo/wii.txt | 2 +- .../bindings/pwm/snps,dw-apb-timers-pwm2.yaml | 2 +- .../bindings/regulator/regulator-max77620.txt | 2 +- .../devicetree/bindings/regulator/regulator.yaml | 8 ++++---- .../regulator/richtek,rt5190a-regulator.yaml | 2 +- .../devicetree/bindings/regulator/vctrl.txt | 2 +- .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 2 +- .../bindings/reset/ti-syscon-reset.txt | 2 +- .../devicetree/bindings/rng/omap_rng.yaml | 4 ++-- .../devicetree/bindings/rtc/rtc-cmos.txt | 2 +- .../bindings/serial/nvidia,tegra20-hsuart.txt | 2 +- .../devicetree/bindings/serial/st-asc.txt | 2 +- .../soc/mediatek/mediatek,mt7986-wo-ccif.yaml | 2 +- .../microchip/microchip,mpfs-sys-controller.yaml | 2 +- .../bindings/soc/qcom/qcom,aoss-qmp.yaml | 2 +- .../bindings/sound/axentia,tse850-pcm5142.txt | 2 +- .../devicetree/bindings/sound/cs35l35.txt | 2 +- .../devicetree/bindings/sound/cs35l36.txt | 2 +- .../devicetree/bindings/sound/cs53l30.txt | 2 +- .../devicetree/bindings/sound/fsl,esai.txt | 2 +- .../bindings/sound/mediatek,mt8188-afe.yaml | 2 +- .../devicetree/bindings/sound/mt2701-afe-pcm.txt | 2 +- .../bindings/sound/mt8195-afe-pcm.yaml | 4 ++-- .../bindings/sound/qcom,msm8916-wcd-analog.txt | 2 +- .../devicetree/bindings/sound/renesas,rsnd.txt | 2 +- .../sound/rockchip,rk3288-hdmi-analog.txt | 2 +- .../devicetree/bindings/sound/rt5663.txt | 2 +- .../devicetree/bindings/sound/serial-midi.yaml | 2 +- .../devicetree/bindings/sound/sprd-pcm.txt | 2 +- .../devicetree/bindings/sound/st,stm32-sai.yaml | 2 +- .../bindings/sound/ti,j721e-cpb-ivi-audio.yaml | 2 +- .../devicetree/bindings/sound/ti,tas2781.yaml | 2 +- .../devicetree/bindings/sound/tlv320adcx140.yaml | 2 +- .../bindings/soundwire/qcom,soundwire.yaml | 4 ++-- .../bindings/spi/brcm,bcm2835-aux-spi.txt | 4 ++-- .../bindings/spi/brcm,spi-bcm-qspi.yaml | 4 ++-- .../devicetree/bindings/spi/omap-spi.yaml | 2 +-
Quoted 9 lines
.../thermal/nvidia,tegra124-soctherm.txt | 2 +- .../devicetree/bindings/timer/snps,arc-timer.txt | 2 +- .../devicetree/bindings/trivial-devices.yaml | 8 ++++---- .../devicetree/bindings/usb/ci-hdrc-usb2.yaml | 2 +- .../devicetree/bindings/usb/fsl,imx8mp-dwc3.yaml | 2 +- .../devicetree/bindings/usb/msm-hsusb.txt | 2 +- .../devicetree/bindings/usb/richtek,rt1719.yaml | 2 +- 161 files changed, 199 insertions(+), 199 deletions(-)
Applied, thanks!
These conflict with linux-next as presumably because they've been converted to schema. So I've just dropped them:
* Unmerged path Documentation/devicetree/bindings/clock/xlnx,zynqmp-clk.txt
* Unmerged path Documentation/devicetree/bindings/input/touchscreen/stmpe.txt
* Unmerged path Documentation/devicetree/bindings/serial/nvidia,tegra20-hsuart.txt
* Unmerged path Documentation/devicetree/bindings/sound/qcom,msm8916-wcd-analog.txt
* Unmerged path Documentation/devicetree/bindings/thermal/nvidia,tegra124-soctherm.txt
PATCH 3/3 Documentation: Fix typos
In reply to Bjorn HelgaasFrom: Bjorn Helgaas <[email protected]>
Fix typos in Documentation.
--- .../admin-guide/kernel-parameters.txt | 2 +- Documentation/admin-guide/mm/damon/usage.rst | 4 +-- .../admin-guide/mm/numa_memory_policy.rst | 2 +- Documentation/admin-guide/module-signing.rst | 2 +- Documentation/admin-guide/xfs.rst | 2 +- Documentation/arch/arm/arm.rst | 2 +- Documentation/arch/arm/ixp4xx.rst | 4 +-- Documentation/arch/arm/sunxi/clocks.rst | 2 +- Documentation/arch/arm/swp_emulation.rst | 2 +- Documentation/arch/arm/tcm.rst | 2 +- Documentation/arch/arm/vlocks.rst | 2 +- .../arch/arm64/acpi_object_usage.rst | 2 +- Documentation/arch/arm64/arm-acpi.rst | 2 +- Documentation/arch/openrisc/openrisc_port.rst | 4 +-- Documentation/arch/x86/boot.rst | 2 +- Documentation/arch/x86/buslock.rst | 2 +- Documentation/arch/x86/mds.rst | 2 +- Documentation/arch/x86/sgx.rst | 2 +- Documentation/arch/xtensa/atomctl.rst | 2 +- Documentation/block/data-integrity.rst | 2 +- Documentation/block/ublk.rst | 2 +- Documentation/bpf/cpumasks.rst | 2 +- Documentation/bpf/graph_ds_impl.rst | 2 +- .../fault-injection/fault-injection.rst | 2 +- Documentation/fb/deferred_io.rst | 2 +- Documentation/fb/sm712fb.rst | 2 +- Documentation/fb/sstfb.rst | 2 +- .../core/thread-info-in-task/arch-support.txt | 2 +- Documentation/filesystems/9p.rst | 2 +- Documentation/filesystems/befs.rst | 4 +-- .../filesystems/caching/cachefiles.rst | 2 +- .../filesystems/caching/netfs-api.rst | 6 ++--- Documentation/filesystems/configfs.rst | 2 +- Documentation/filesystems/dax.rst | 2 +- Documentation/filesystems/devpts.rst | 4 +-- Documentation/filesystems/ext4/super.rst | 2 +- Documentation/filesystems/f2fs.rst | 6 ++--- Documentation/filesystems/gfs2-glocks.rst | 2 +- Documentation/filesystems/idmappings.rst | 14 +++++----- Documentation/filesystems/netfs_library.rst | 2 +- .../filesystems/nfs/client-identifier.rst | 2 +- Documentation/filesystems/nfs/rpc-cache.rst | 2 +- .../filesystems/nfs/rpc-server-gss.rst | 2 +- Documentation/filesystems/nilfs2.rst | 2 +- Documentation/filesystems/ntfs3.rst | 2 +- Documentation/filesystems/orangefs.rst | 2 +- Documentation/filesystems/overlayfs.rst | 4 +-- Documentation/filesystems/porting.rst | 6 ++--- Documentation/filesystems/proc.rst | 12 ++++----- Documentation/filesystems/qnx6.rst | 2 +- Documentation/filesystems/seq_file.rst | 4 +-- .../filesystems/ubifs-authentication.rst | 2 +- Documentation/filesystems/vfat.rst | 2 +- Documentation/filesystems/vfs.rst | 2 +- .../filesystems/xfs-online-fsck-design.rst | 20 +++++++------- Documentation/filesystems/zonefs.rst | 2 +- Documentation/firmware-guide/acpi/osi.rst | 2 +- .../gpu/amdgpu/display/mpo-overview.rst | 2 +- Documentation/gpu/drm-kms-helpers.rst | 2 +- Documentation/gpu/drm-kms.rst | 6 ++--- Documentation/gpu/drm-usage-stats.rst | 4 +-- Documentation/gpu/i915.rst | 4 +-- Documentation/gpu/kms-properties.csv | 2 +- Documentation/gpu/komeda-kms.rst | 4 +-- Documentation/gpu/msm-crash-dump.rst | 2 +- Documentation/gpu/rfc/i915_scheduler.rst | 2 +- Documentation/gpu/rfc/i915_vm_bind.rst | 2 +- Documentation/gpu/todo.rst | 8 +++--- Documentation/hwmon/pmbus-core.rst | 2 +- .../input/devices/iforce-protocol.rst | 2 +- Documentation/input/multi-touch-protocol.rst | 2 +- .../livepatch/reliable-stacktrace.rst | 2 +- Documentation/locking/lockdep-design.rst | 4 +-- Documentation/locking/locktorture.rst | 2 +- Documentation/locking/locktypes.rst | 2 +- Documentation/mm/hmm.rst | 2 +- Documentation/mm/hwpoison.rst | 2 +- Documentation/mm/page_migration.rst | 2 +- Documentation/mm/unevictable-lru.rst | 2 +- Documentation/mm/vmemmap_dedup.rst | 2 +- Documentation/netlink/genetlink-c.yaml | 2 +- Documentation/netlink/genetlink-legacy.yaml | 2 +- Documentation/networking/bonding.rst | 2 +- .../networking/devlink/devlink-port.rst | 6 ++--- Documentation/networking/packet_mmap.rst | 2 +- Documentation/power/energy-model.rst | 4 +-- Documentation/powerpc/dscr.rst | 2 +- Documentation/powerpc/kasan.txt | 2 +- Documentation/powerpc/papr_hcalls.rst | 2 +- Documentation/powerpc/qe_firmware.rst | 4 +-- Documentation/powerpc/vas-api.rst | 4 +-- Documentation/process/botching-up-ioctls.rst | 2 +- Documentation/process/kernel-docs.rst | 2 +- Documentation/riscv/hwprobe.rst | 4 +-- Documentation/riscv/vector.rst | 2 +- Documentation/s390/vfio-ap.rst | 2 +- Documentation/scheduler/sched-bwc.rst | 2 +- Documentation/scheduler/sched-energy.rst | 4 +-- Documentation/scsi/ChangeLog.lpfc | 2 +- Documentation/security/digsig.rst | 2 +- Documentation/security/keys/core.rst | 2 +- Documentation/security/secrets/coco.rst | 2 +- Documentation/sphinx/cdomain.py | 2 +- Documentation/spi/spi-lm70llp.rst | 2 +- .../tools/rtla/rtla-timerlat-top.rst | 2 +- .../coresight/coresight-etm4x-reference.rst | 2 +- Documentation/trace/events.rst | 6 ++--- Documentation/trace/fprobe.rst | 2 +- Documentation/trace/ftrace.rst | 2 +- Documentation/trace/hwlat_detector.rst | 2 +- .../trace/rv/da_monitor_synthesis.rst | 2 +- Documentation/trace/rv/monitor_wwnr.rst | 2 +- .../trace/rv/runtime-verification.rst | 2 +- Documentation/trace/uprobetracer.rst | 2 +- Documentation/trace/user_events.rst | 2 +- Documentation/usb/gadget_uvc.rst | 2 +- .../media/v4l/ext-ctrls-codec-stateless.rst | 2 +- .../userspace-api/media/v4l/metafmt-d4xx.rst | 2 +- Documentation/userspace-api/netlink/intro.rst | 2 +- Documentation/virt/hyperv/clocks.rst | 2 +- Documentation/virt/kvm/api.rst | 26 +++++++++---------- Documentation/virt/kvm/devices/vm.rst | 2 +- Documentation/virt/kvm/devices/xive.rst | 2 +- Documentation/virt/kvm/halt-polling.rst | 2 +- Documentation/virt/kvm/x86/mmu.rst | 2 +- .../virt/kvm/x86/running-nested-guests.rst | 2 +- .../virt/uml/user_mode_linux_howto_v2.rst | 2 +- Documentation/w1/slaves/w1_therm.rst | 2 +- Documentation/w1/w1-generic.rst | 2 +- Documentation/w1/w1-netlink.rst | 2 +- .../watchdog/watchdog-kernel-api.rst | 2 +- Documentation/wmi/devices/dell-wmi-ddv.rst | 4 +-- 132 files changed, 196 insertions(+), 196 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +1 -1
@@ -2624,7 +2624,7 @@ kvm-intel.flexpriority= [KVM,Intel] Control KVM's use of FlexPriority feature - (TPR shadow). Default is 1 (enabled). Disalbe by KVM if + (TPR shadow). Default is 1 (enabled). Disable by KVM if hardware lacks support for it. kvm-intel.nested=
Documentation/admin-guide/mm/damon/usage.rst +2 -2
@@ -99,7 +99,7 @@ Root The root of the DAMON sysfs interface is ``<sysfs>/kernel/mm/damon/``, and it has one directory named ``admin``. The directory contains the files for -privileged user space programs' control of DAMON. User space tools or deamons +privileged user space programs' control of DAMON. User space tools or daemons having the root permission could use this directory. kdamonds/
@@ -397,7 +397,7 @@ be used for online analysis or tuning of the schemes. The statistics can be retrieved by reading the files under ``stats`` directory (``nr_tried``, ``sz_tried``, ``nr_applied``, ``sz_applied``, and ``qt_exceeds``), respectively. The files are not updated in real time, so you -should ask DAMON sysfs interface to updte the content of the files for the +should ask DAMON sysfs interface to update the content of the files for the stats by writing a special keyword, ``update_schemes_stats`` to the relevant ``kdamonds/<N>/state`` file.
Documentation/admin-guide/mm/numa_memory_policy.rst +1 -1
@@ -109,7 +109,7 @@ VMA Policy * A task may install a new VMA policy on a sub-range of a previously mmap()ed region. When this happens, Linux splits the existing virtual memory area into 2 or 3 VMAs, each with - it's own policy. + its own policy. * By default, VMA policy applies only to pages allocated after the policy is installed. Any pages already faulted into the
Documentation/admin-guide/module-signing.rst +1 -1
@@ -266,7 +266,7 @@ for which it has a public key. Otherwise, it will also load modules that are unsigned. Any module for which the kernel has a key, but which proves to have a signature mismatch will not be permitted to load. -Any module that has an unparseable signature will be rejected. +Any module that has an unparsable signature will be rejected. =========================================
Documentation/admin-guide/xfs.rst +1 -1
@@ -192,7 +192,7 @@ When mounting an XFS filesystem, the following options are accepted. are any integer multiple of a valid ``sunit`` value. Typically the only time these mount options are necessary if - after an underlying RAID device has had it's geometry + after an underlying RAID device has had its geometry modified, such as adding a new disk to a RAID5 lun and reshaping it.
Documentation/arch/arm/arm.rst +1 -1
@@ -141,7 +141,7 @@ ST506 hard drives `*configure` harddrive set to 2). I've got an internal 20MB and a great big external 5.25" FH 64MB drive (who could ever want more :-) ). - I've just got 240K/s off it (a dd with bs=128k); thats about half of what + I've just got 240K/s off it (a dd with bs=128k); that's about half of what RiscOS gets; but it's a heck of a lot better than the 50K/s I was getting last week :-)
Documentation/arch/arm/ixp4xx.rst +2 -2
@@ -78,9 +78,9 @@ IXP4xx provides two methods of accessing PCI memory space: 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB). To access PCI via this space, we simply ioremap() the BAR into the kernel and we can use the standard read[bwl]/write[bwl] - macros. This is the preffered method due to speed but it + macros. This is the preferred method due to speed but it limits the system to just 64MB of PCI memory. This can be - problamatic if using video cards and other memory-heavy devices. + problematic if using video cards and other memory-heavy devices. 2) If > 64MB of memory space is required, the IXP4xx can be configured to use indirect registers to access PCI This allows
Documentation/arch/arm/sunxi/clocks.rst +1 -1
@@ -5,7 +5,7 @@ Frequently asked questions about the sunxi clock system This document contains useful bits of information that people tend to ask about the sunxi clock system, as well as accompanying ASCII art when adequate. -Q: Why is the main 24MHz oscillator gatable? Wouldn't that break the +Q: Why is the main 24MHz oscillator gateable? Wouldn't that break the system? A: The 24MHz oscillator allows gating to save power. Indeed, if gated
Documentation/arch/arm/swp_emulation.rst +1 -1
@@ -1,7 +1,7 @@ Software emulation of deprecated SWP instruction (CONFIG_SWP_EMULATE) --------------------------------------------------------------------- -ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommeds +ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommends moving to the load-locked/store-conditional instructions LDREX and STREX. ARMv7 multiprocessing extensions introduce the ability to disable these
Documentation/arch/arm/tcm.rst +1 -1
@@ -71,7 +71,7 @@ in <asm/tcm.h>. Using this interface it is possible to: - Have the remaining TCM RAM added to a special allocation pool with gen_pool_create() and gen_pool_add() - and provice tcm_alloc() and tcm_free() for this + and provide tcm_alloc() and tcm_free() for this memory. Such a heap is great for things like saving device state when shutting off device power domains.
Documentation/arch/arm/vlocks.rst +1 -1
@@ -155,7 +155,7 @@ the basic algorithm: optimisation. If there are too many CPUs to read the currently_voting array in - one transaction then multiple transations are still required. The + one transaction then multiple transactions are still required. The implementation uses a simple loop of word-sized loads for this case. The number of transactions is still fewer than would be required if bytes were loaded individually.
Documentation/arch/arm64/acpi_object_usage.rst +1 -1
@@ -45,7 +45,7 @@ APMT Signature Reserved (signature == "APMT") **Arm Performance Monitoring Table** - This table describes the properties of PMU support implmented by + This table describes the properties of PMU support implemented by components in the system. BERT Section 18.3 (signature == "BERT")
Documentation/arch/arm64/arm-acpi.rst +1 -1
@@ -99,7 +99,7 @@ to replace the kernel. When a Linux driver or subsystem is first implemented using ACPI, it by definition ends up requiring a specific version of the ACPI specification --- it's baseline. ACPI firmware must continue to work, even though it may +-- its baseline. ACPI firmware must continue to work, even though it may not be optimal, with the earliest kernel version that first provides support for that baseline version of ACPI. There may be a need for additional drivers, but adding new functionality (e.g., CPU power management) should not break
Documentation/arch/openrisc/openrisc_port.rst +2 -2
@@ -106,7 +106,7 @@ History a much improved version with changes all around. 10-04-2004 Matjaz Breskvar ([email protected]) - alot of bugfixes all over. + a lot of bugfixes all over. ethernet support, functional http and telnet servers. running many standard linux apps.
@@ -114,7 +114,7 @@ History port to 2.6.x 30-11-2004 Matjaz Breskvar ([email protected]) - lots of bugfixes and enhancments. + lots of bugfixes and enhancements. added opencores framebuffer driver. 09-10-2010 Jonas Bonn ([email protected])
Documentation/arch/x86/boot.rst +1 -1
@@ -1105,7 +1105,7 @@ The kernel command line should not be located below the real-mode code, nor should it be located in high memory. -Sample Boot Configuartion +Sample Boot Configuration ========================= As a sample configuration, assume the following layout of the real
Documentation/arch/x86/buslock.rst +1 -1
@@ -32,7 +32,7 @@ mechanisms to detect split locks and bus locks. -------------------------------------- Beginning with the Tremont Atom CPU split lock operations may raise an -Alignment Check (#AC) exception when a split lock operation is attemped. +Alignment Check (#AC) exception when a split lock operation is attempted. #DB exception for bus lock detection ------------------------------------
Documentation/arch/x86/mds.rst +1 -1
@@ -60,7 +60,7 @@ needed for exploiting MDS requires: data The existence of such a construct in the kernel cannot be excluded with -100% certainty, but the complexity involved makes it extremly unlikely. +100% certainty, but the complexity involved makes it extremely unlikely. There is one exception, which is untrusted BPF. The functionality of untrusted BPF is limited, but it needs to be thoroughly investigated
Documentation/arch/x86/sgx.rst +1 -1
@@ -245,7 +245,7 @@ SGX will likely become unusable because the memory available to SGX is limited. However, while this may be fatal to SGX, the rest of the kernel is unlikely to be impacted and should continue to work. -As a result, when this happpens, user should stop running any new +As a result, when this happens, user should stop running any new SGX workloads, (or just any new workloads), and migrate all valuable workloads. Although a machine reboot can recover all EPC memory, the bug should be reported to Linux developers.
Documentation/arch/xtensa/atomctl.rst +1 -1
@@ -23,7 +23,7 @@ doing a Cached (WB) transaction and use the Memory RCW for un-cached operations. For systems without an coherent cache controller, non-MX, we always -use the memory controllers RCW, thought non-MX controlers likely +use the memory controllers RCW, though non-MX controllers likely support the Internal Operation. CUSTOMER-WARNING:
Documentation/block/data-integrity.rst +1 -1
@@ -209,7 +209,7 @@ will require extra work due to the application tag. sector must be set, and the bio should have all data pages added. It is up to the caller to ensure that the bio does not change while I/O is in progress. - Complete bio with error if prepare failed for some reson. + Complete bio with error if prepare failed for some reason. 5.3 Passing Existing Integrity Metadata
Documentation/block/ublk.rst +1 -1
@@ -238,7 +238,7 @@ The's IO is assigned by a unique tag, which is 1:1 mapping with IO request of ``/dev/ublkb*``. UAPI structure of ``ublksrv_io_desc`` is defined for describing each IO from -the driver. A fixed mmaped area (array) on ``/dev/ublkc*`` is provided for +the driver. A fixed mmapped area (array) on ``/dev/ublkc*`` is provided for exporting IO info to the server; such as IO offset, length, OP/flags and buffer address. Each ``ublksrv_io_desc`` instance can be indexed via queue id and IO tag directly.
Documentation/bpf/cpumasks.rst +1 -1
@@ -364,7 +364,7 @@ can be used to query the contents of cpumasks. ---- Some example usages of these querying kfuncs were shown above. We will not -replicate those exmaples here. Note, however, that all of the aforementioned +replicate those examples here. Note, however, that all of the aforementioned kfuncs are tested in `tools/testing/selftests/bpf/progs/cpumask_success.c`_, so please take a look there if you're looking for more examples of how they can be used.
Documentation/bpf/graph_ds_impl.rst +1 -1
@@ -23,7 +23,7 @@ Introduction The BPF map API has historically been the main way to expose data structures of various types for use within BPF programs. Some data structures fit naturally -with the map API (HASH, ARRAY), others less so. Consequentially, programs +with the map API (HASH, ARRAY), others less so. Consequently, programs interacting with the latter group of data structures can be hard to parse for kernel programmers without previous BPF experience.
Documentation/fault-injection/fault-injection.rst +1 -1
@@ -243,7 +243,7 @@ proc entries Error Injectable Functions -------------------------- -This part is for the kenrel developers considering to add a function to +This part is for the kernel developers considering to add a function to ALLOW_ERROR_INJECTION() macro. Requirements for the Error Injectable Functions
Documentation/fb/deferred_io.rst +1 -1
@@ -9,7 +9,7 @@ works: - userspace app like Xfbdev mmaps framebuffer - deferred IO and driver sets up fault and page_mkwrite handlers -- userspace app tries to write to mmaped vaddress +- userspace app tries to write to mmapped vaddress - we get pagefault and reach fault handler - fault handler finds and returns physical page - we get page_mkwrite where we add this page to a list
Documentation/fb/sm712fb.rst +1 -1
@@ -31,5 +31,5 @@ Missing Features ================ (alias TODO list) - * 2D acceleratrion + * 2D acceleration * dual-head support
Documentation/fb/sstfb.rst +1 -1
@@ -73,7 +73,7 @@ Module insertion the device will be /dev/fb0. You can check this by doing a cat /proc/fb. You can find a copy of con2fb in tools/ directory. if you don't have another fb device, this step is superfluous, - as the console subsystem automagicaly binds ttys to the fb. + as the console subsystem automagically binds ttys to the fb. #. switch to the virtual console you just mapped. "tadaaa" ... Module removal
Documentation/features/core/thread-info-in-task/arch-support.txt +1 -1
@@ -1,7 +1,7 @@ # # Feature name: thread-info-in-task # Kconfig: THREAD_INFO_IN_TASK -# description: arch makes use of the core kernel facility to embedd thread_info in task_struct +# description: arch makes use of the core kernel facility to embed thread_info in task_struct # ----------------------- | arch |status|
Documentation/filesystems/9p.rst +1 -1
@@ -79,7 +79,7 @@ Options cache=mode specifies a caching policy. By default, no caches are used. The mode can be specified as a bitmask or by using one of the - prexisting common 'shortcuts'. + preexisting common 'shortcuts'. The bitmask is described below: (unspecified bits are reserved) ========== ====================================================
Documentation/filesystems/befs.rst +2 -2
@@ -106,8 +106,8 @@ iocharset=xxx Use xxx as the name of the NLS translation table. debug The driver will output debugging information to the syslog. ============= =========================================================== -How to Get Lastest Version -========================== +How to Get Latest Version +========================= The latest version is currently available at: <http://befs-driver.sourceforge.net/>
Documentation/filesystems/caching/cachefiles.rst +1 -1
@@ -416,7 +416,7 @@ process is the target of an operation by some other process (SIGKILL for example). The subjective security holds the active security properties of a process, and -may be overridden. This is not seen externally, and is used whan a process +may be overridden. This is not seen externally, and is used when a process acts upon another object, for example SIGKILLing another process or opening a file.
Documentation/filesystems/caching/netfs-api.rst +3 -3
@@ -59,7 +59,7 @@ A filesystem would typically have a volume cookie for each superblock. The filesystem then acquires a cookie for each file within that volume using an object key. Object keys are binary blobs and only need to be unique within -their parent volume. The cache backend is reponsible for rendering the binary +their parent volume. The cache backend is responsible for rendering the binary blob into something it can use and may employ hash tables, trees or whatever to improve its ability to find an object. This is transparent to the network filesystem.
@@ -91,7 +91,7 @@ actually required and it can use the fscache I/O API directly. Volume Registration =================== -The first step for a network filsystem is to acquire a volume cookie for the +The first step for a network filesystem is to acquire a volume cookie for the volume it wants to access:: struct fscache_volume *
@@ -119,7 +119,7 @@ is provided. If the coherency data doesn't match, the entire cache volume will be invalidated. This function can return errors such as EBUSY if the volume key is already in -use by an acquired volume or ENOMEM if an allocation failure occured. It may +use by an acquired volume or ENOMEM if an allocation failure occurred. It may also return a NULL volume cookie if fscache is not enabled. It is safe to pass a NULL cookie to any function that takes a volume cookie. This will cause that function to do nothing.
Documentation/filesystems/configfs.rst +1 -1
@@ -253,7 +253,7 @@ to be used. If binary attribute is readable and the config_item provides a ct_item_ops->read_bin_attribute() method, that method will be called whenever userspace asks for a read(2) on the attribute. The converse -will happen for write(2). The reads/writes are bufferred so only a +will happen for write(2). The reads/writes are buffered so only a single read/write will occur; the attributes' need not concern itself with it.
Documentation/filesystems/dax.rst +1 -1
@@ -291,7 +291,7 @@ The DAX code does not work correctly on architectures which have virtually mapped caches such as ARM, MIPS and SPARC. Calling :c:func:`get_user_pages()` on a range of user memory that has been -mmaped from a `DAX` file will fail when there are no 'struct page' to describe +mmapped from a `DAX` file will fail when there are no 'struct page' to describe those pages. This problem has been addressed in some device drivers by adding optional struct page support for pages under the control of the driver (see `CONFIG_NVDIMM_PFN` in ``drivers/nvdimm`` for an example of
Documentation/filesystems/devpts.rst +2 -2
@@ -5,8 +5,8 @@ The Devpts Filesystem ===================== Each mount of the devpts filesystem is now distinct such that ptys -and their indicies allocated in one mount are independent from ptys -and their indicies in all other mounts. +and their indices allocated in one mount are independent from ptys +and their indices in all other mounts. All mounts of the devpts filesystem now create a ``/dev/pts/ptmx`` node with permissions ``0000``.
Documentation/filesystems/ext4/super.rst +1 -1
@@ -772,7 +772,7 @@ The ``s_default_mount_opts`` field is any combination of the following: * - 0x0010 - Do not support 32-bit UIDs. (EXT4_DEFM_UID16) * - 0x0020 - - All data and metadata are commited to the journal. + - All data and metadata are committed to the journal. (EXT4_DEFM_JMODE_DATA) * - 0x0040 - All data are flushed to the disk before metadata are committed to the
Documentation/filesystems/f2fs.rst +3 -3
@@ -359,7 +359,7 @@ errors=%s Specify f2fs behavior on critical errors. This supports modes: ====================== =============== =============== ======== mode continue remount-ro panic ====================== =============== =============== ======== - access ops normal noraml N/A + access ops normal normal N/A syscall errors -EIO -EROFS N/A mount option rw ro N/A pending dir write keep keep N/A
@@ -480,7 +480,7 @@ Note: please refer to the manpage of dump.f2fs(8) to get full option list. sload.f2fs ---------- -The sload.f2fs gives a way to insert files and directories in the exisiting disk +The sload.f2fs gives a way to insert files and directories in the existing disk image. This tool is useful when building f2fs images given compiled files. Note: please refer to the manpage of sload.f2fs(8) to get full option list.
@@ -792,7 +792,7 @@ Allocating disk space as a method of optimally implementing that function. However, once F2FS receives ioctl(fd, F2FS_IOC_SET_PIN_FILE) in prior to -fallocate(fd, DEFAULT_MODE), it allocates on-disk block addressess having +fallocate(fd, DEFAULT_MODE), it allocates on-disk block addresses having zero or random data, which is useful to the below scenario where: 1. create(fd)
Documentation/filesystems/gfs2-glocks.rst +1 -1
@@ -78,7 +78,7 @@ The minimum hold time for each lock is the time after a remote lock grant for which we ignore remote demote requests. This is in order to prevent a situation where locks are being bounced around the cluster from node to node with none of the nodes making any progress. This -tends to show up most with shared mmaped files which are being written +tends to show up most with shared mmapped files which are being written to by multiple nodes. By delaying the demotion in response to a remote callback, that gives the userspace program time to make some progress before the pages are unmapped.
Documentation/filesystems/idmappings.rst +7 -7
@@ -36,7 +36,7 @@ and write down the mappings it will generate:: From a mathematical viewpoint ``U`` and ``K`` are well-ordered sets and an idmapping is an order isomorphism from ``U`` into ``K``. So ``U`` and ``K`` are order isomorphic. In fact, ``U`` and ``K`` are always well-ordered subsets of -the set of all possible ids useable on a given system. +the set of all possible ids usable on a given system. Looking at this mathematically briefly will help us highlight some properties that make it easier to understand how we can translate between idmappings. For
@@ -47,7 +47,7 @@ example, we know that the inverse idmapping is an order isomorphism as well:: k10002 -> u24 Given that we are dealing with order isomorphisms plus the fact that we're -dealing with subsets we can embedd idmappings into each other, i.e. we can +dealing with subsets we can embed idmappings into each other, i.e. we can sensibly translate between different idmappings. For example, assume we've been given the three idmappings::
@@ -60,7 +60,7 @@ and id ``k11000`` which has been generated by the first idmapping by mapping Because we're dealing with order isomorphic subsets it is meaningful to ask what id ``k11000`` corresponds to in the second or third idmapping. The -straightfoward algorithm to use is to apply the inverse of the first idmapping, +straightforward algorithm to use is to apply the inverse of the first idmapping, mapping ``k11000`` up to ``u1000``. Afterwards, we can map ``u1000`` down using either the second idmapping mapping or third idmapping mapping. The second idmapping would map ``u1000`` down to ``21000``. The third idmapping would map
@@ -367,7 +367,7 @@ So with the second step the kernel guarantees that a valid userspace id can be written to disk. If it can't the kernel will refuse the creation request to not even remotely risk filesystem corruption. -The astute reader will have realized that this is simply a varation of the +The astute reader will have realized that this is simply a variation of the crossmapping algorithm we mentioned above in a previous section. First, the kernel maps the caller's userspace id down into a kernel id according to the caller's idmapping and then maps that kernel id up according to the
@@ -458,7 +458,7 @@ the kernel id that was created in the caller's idmapping. This has mainly two consequences. First, that we can't allow a caller to ultimately write to disk with another -userspace id. We could only do this if we were to mount the whole fileystem +userspace id. We could only do this if we were to mount the whole filesystem with the caller's or another idmapping. But that solution is limited to a few filesystems and not very flexible. But this is a use-case that is pretty important in containerized workloads.
@@ -589,7 +589,7 @@ on their work machine. In both cases changing ownership recursively has grave implications. The most obvious one is that ownership is changed globally and permanently. In the home -directory case this change in ownership would even need to happen everytime the +directory case this change in ownership would even need to happen every time the user switches from their home to their work machine. For really large sets of files this becomes increasingly costly.
@@ -662,7 +662,7 @@ use the ``vfsuid_into_kuid()`` and ``vfsgid_into_kgid()`` helpers. To illustrate why this helper currently exists, consider what happens when we change ownership of an inode from an idmapped mount. After we generated a ``vfsuid_t`` or ``vfsgid_t`` based on the mount idmapping we later commit to -this ``vfsuid_t`` or ``vfsgid_t`` to become the new filesytem wide ownership. +this ``vfsuid_t`` or ``vfsgid_t`` to become the new filesystem wide ownership. Thus, we are turning the ``vfsuid_t`` or ``vfsgid_t`` into a global ``kuid_t`` or ``kgid_t``. And this can be done by using ``vfsuid_into_kuid()`` and ``vfsgid_into_kgid()``.
Documentation/filesystems/netfs_library.rst +1 -1
@@ -155,7 +155,7 @@ conflicting writes or track dirty data and needs to put the acquired folio if an error occurs after calling the helper. The helpers manage the read request, calling back into the network filesystem -through the suppplied table of operations. Waits will be performed as +through the supplied table of operations. Waits will be performed as necessary before returning for helpers that are meant to be synchronous. If an error occurs, the ->free_request() will be called to clean up the
Documentation/filesystems/nfs/client-identifier.rst +1 -1
@@ -131,7 +131,7 @@ deployments, this construction is usually adequate. Often, however, the node name by itself is not adequately unique, and can change unexpectedly. Problematic situations include: - - NFS-root (diskless) clients, where the local DCHP server (or + - NFS-root (diskless) clients, where the local DHCP server (or equivalent) does not provide a unique host name. - "Containers" within a single Linux host. If each container has
Documentation/filesystems/nfs/rpc-cache.rst +1 -1
@@ -78,7 +78,7 @@ Creating a Cache include taking references to shared objects. void update(struct cache_head \*orig, struct cache_head \*new) - Set the 'content' fileds in 'new' from 'orig'. + Set the 'content' fields in 'new' from 'orig'. int cache_show(struct seq_file \*m, struct cache_detail \*cd, struct cache_head \*h) Optional. Used to provide a /proc file that lists the
Documentation/filesystems/nfs/rpc-server-gss.rst +1 -1
@@ -29,7 +29,7 @@ The Linux kernel, at the moment, supports only the KRB5 mechanism, and depends on GSSAPI extensions that are KRB5 specific. GSSAPI is a complex library, and implementing it completely in kernel is -unwarranted. However GSSAPI operations are fundementally separable in 2 +unwarranted. However GSSAPI operations are fundamentally separable in 2 parts: - initial context establishment
Documentation/filesystems/nilfs2.rst +1 -1
@@ -231,7 +231,7 @@ file structures (nilfs_finfo), and per block structures (nilfs_binfo):: The logs include regular files, directory files, symbolic link files -and several meta data files. The mata data files are the files used +and several meta data files. The meta data files are the files used to maintain file system meta data. The current version of NILFS2 uses the following meta data files::
Documentation/filesystems/ntfs3.rst +1 -1
@@ -112,7 +112,7 @@ this table marked with no it means default is without **no**. Todo list ========= - Full journaling support over JBD. Currently journal replaying is supported - which is not necessarily as effectice as JBD would be. + which is not necessarily as effective as JBD would be. References ==========
Documentation/filesystems/orangefs.rst +1 -1
@@ -274,7 +274,7 @@ then contains: of kcalloced memory. This memory is used as an array of pointers to each of the pages in the IO buffer through a call to get_user_pages. * desc_array - a pointer to ``desc_count * (sizeof(struct orangefs_bufmap_desc))`` - bytes of kcalloced memory. This memory is further intialized: + bytes of kcalloced memory. This memory is further initialized: user_desc is the kernel's copy of the IO buffer's ORANGEFS_dev_map_desc structure. user_desc->ptr points to the IO buffer.
Documentation/filesystems/overlayfs.rst +2 -2
@@ -195,7 +195,7 @@ handle it in two different ways: 1. return EXDEV error: this error is returned by rename(2) when trying to move a file or directory across filesystem boundaries. Hence - applications are usually prepared to hande this error (mv(1) for example + applications are usually prepared to handle this error (mv(1) for example recursively copies the directory tree). This is the default behavior. 2. If the "redirect_dir" feature is enabled, then the directory will be
@@ -235,7 +235,7 @@ Mount options: Redirects are not created and not followed. - "redirect_dir=off": If "redirect_always_follow" is enabled in the kernel/module config, - this "off" traslates to "follow", otherwise it translates to "nofollow". + this "off" translates to "follow", otherwise it translates to "nofollow". When the NFS export feature is enabled, every copied up directory is indexed by the file handle of the lower inode and a file handle of the
Documentation/filesystems/porting.rst +3 -3
@@ -177,7 +177,7 @@ settles down a bit. **mandatory** s_export_op is now required for exporting a filesystem. -isofs, ext2, ext3, resierfs, fat +isofs, ext2, ext3, reiserfs, fat can be used as examples of very different filesystems. ---
@@ -470,7 +470,7 @@ has been taken to VFS and filesystems need to provide a non-NULL **mandatory** If you implement your own ->llseek() you must handle SEEK_HOLE and -SEEK_DATA. You can hanle this by returning -EINVAL, but it would be nicer to +SEEK_DATA. You can handle this by returning -EINVAL, but it would be nicer to support it in some way. The generic handler assumes that the entire file is data and there is a virtual hole at the end of the file. So if the provided offset is less than i_size and SEEK_DATA is specified, return the same offset.
@@ -517,7 +517,7 @@ The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and ->create() doesn't take ``struct nameidata *``; unlike the previous two, it gets "is it an O_EXCL or equivalent?" boolean argument. Note that -local filesystems can ignore tha argument - they are guaranteed that the +local filesystems can ignore this argument - they are guaranteed that the object doesn't exist. It's remote/distributed ones that might care... ---
Documentation/filesystems/proc.rst +6 -6
@@ -507,12 +507,12 @@ pressure if the memory is clean. Please note that the printed value might be lower than the real value due to optimizations used in the current implementation. If this is not desirable please file a bug report. -"AnonHugePages" shows the ammount of memory backed by transparent hugepage. +"AnonHugePages" shows the amount of memory backed by transparent hugepage. -"ShmemPmdMapped" shows the ammount of shared (shmem/tmpfs) memory backed by +"ShmemPmdMapped" shows the amount of shared (shmem/tmpfs) memory backed by huge pages. -"Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by +"Shared_Hugetlb" and "Private_Hugetlb" show the amounts of memory backed by hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical reasons. And these are not included in {Shared,Private}_{Clean,Dirty} field.
@@ -561,7 +561,7 @@ encoded manner. The codes are the following: mm mixed map area hg huge page advise flag nh no huge page advise flag - mg mergable advise flag + mg mergeable advise flag bt arm64 BTI guarded page mt arm64 MTE allocation tags are enabled um userfaultfd missing tracking
@@ -1081,7 +1081,7 @@ Writeback AnonPages Non-file backed pages mapped into userspace page tables Mapped - files which have been mmaped, such as libraries + files which have been mmapped, such as libraries Shmem Total memory used by shared memory (shmem) and tmpfs KReclaimable
@@ -2229,7 +2229,7 @@ are not related to tasks. Chapter 5: Filesystem behavior ============================== -Originally, before the advent of pid namepsace, procfs was a global file +Originally, before the advent of pid namespace, procfs was a global file system. It means that there was only one procfs instance in the system. When pid namespace was added, a separate procfs instance was mounted in
Documentation/filesystems/qnx6.rst +1 -1
@@ -135,7 +135,7 @@ inode. Character and block special devices do not exist in QNX as those files are handled by the QNX kernel/drivers and created in /dev independent of the -underlaying filesystem. +underlying filesystem. Long filenames --------------
Documentation/filesystems/seq_file.rst +2 -2
@@ -130,7 +130,7 @@ called SEQ_START_TOKEN; it can be used if you wish to instruct your show() function (described below) to print a header at the top of the output. SEQ_START_TOKEN should only be used if the offset is zero, however. SEQ_START_TOKEN has no special meaning to the core seq_file -code. It is provided as a convenience for a start() funciton to +code. It is provided as a convenience for a start() function to communicate with the next() and show() functions. The next function to implement is called, amazingly, next(); its job is to
@@ -217,7 +217,7 @@ between the calls to start() and stop(), so holding a lock during that time is a reasonable thing to do. The seq_file code will also avoid taking any other locks while the iterator is active. -The iterater value returned by start() or next() is guaranteed to be +The iterator value returned by start() or next() is guaranteed to be passed to a subsequent next() or stop() call. This allows resources such as locks that were taken to be reliably released. There is *no* guarantee that the iterator will be passed to show(), though in practice
Documentation/filesystems/ubifs-authentication.rst +1 -1
@@ -130,7 +130,7 @@ marked as dirty are written to the flash to update the persisted index. Journal ~~~~~~~ -To avoid wearing out the flash, the index is only persisted (*commited*) when +To avoid wearing out the flash, the index is only persisted (*committed*) when certain conditions are met (eg. ``fsync(2)``). The journal is used to record any changes (in form of inode nodes, data nodes etc.) between commits of the index. During mount, the journal is read from the flash and replayed
Documentation/filesystems/vfat.rst +1 -1
@@ -50,7 +50,7 @@ VFAT MOUNT OPTIONS Normally utime(2) checks current process is owner of the file, or it has CAP_FOWNER capability. But FAT filesystem doesn't have uid/gid on disk, so normal - check is too unflexible. With this option you can + check is too inflexible. With this option you can relax it. **codepage=###**
Documentation/filesystems/vfs.rst +1 -1
@@ -761,7 +761,7 @@ is an error during writeback, they expect that error to be reported when a file sync request is made. After an error has been reported on one request, subsequent requests on the same file descriptor should return 0, unless further writeback errors have occurred since the previous file -syncronization. +synchronization. Ideally, the kernel would report errors only on file descriptions on which writes were done that subsequently failed to be written back. The
Documentation/filesystems/xfs-online-fsck-design.rst +10 -10
@@ -293,7 +293,7 @@ The seven phases are as follows: Before starting repairs, the summary counters are checked and any necessary repairs are performed so that subsequent repairs will not fail the resource reservation step due to wildly incorrect summary counters. - Unsuccesful repairs are requeued as long as forward progress on repairs is + Unsuccessful repairs are requeued as long as forward progress on repairs is made somewhere in the filesystem. Free space in the filesystem is trimmed at the end of phase 4 if the filesystem is clean.
@@ -542,7 +542,7 @@ ondisk structure. Inspiration for quota and file link count repair strategies were drawn from sections 2.12 ("Online Index Operations") through 2.14 ("Incremental View -Maintenace") of G. Graefe, `"Concurrent Queries and Updates in Summary Views +Maintenance") of G. Graefe, `"Concurrent Queries and Updates in Summary Views and Their Indexes" <http://www.odbms.org/wp-content/uploads/2014/06/Increment-locks.pdf>`_, 2011.
@@ -605,7 +605,7 @@ functionality. The cron job does not have this protection. - **Fuzz Kiddiez**: There are many people now who seem to think that running - automated fuzz testing of ondisk artifacts to find mischevious behavior and + automated fuzz testing of ondisk artifacts to find mischievous behavior and spraying exploit code onto the public mailing list for instant zero-day disclosure is somehow of some social benefit. In the view of this author, the benefit is realized only when the fuzz
@@ -1351,7 +1351,7 @@ If the leaf information exceeds a single filesystem block, a dabtree (also rooted at block 0) is created to map hashes of the attribute names to leaf blocks in the attr fork. -Checking an extended attribute structure is not so straightfoward due to the +Checking an extended attribute structure is not so straightforward due to the lack of separation between attr blocks and index blocks. Scrub must read each block mapped by the attr fork and ignore the non-leaf blocks:
@@ -1401,7 +1401,7 @@ If the free space has been separated and the second partition grows again beyond one block, then a dabtree is used to map hashes of dirent names to directory data blocks. -Checking a directory is pretty straightfoward: +Checking a directory is pretty straightforward: 1. Walk the dabtree in the second partition (if present) to ensure that there are no irregularities in the blocks or dabtree mappings that do not point to
@@ -1524,7 +1524,7 @@ Only online fsck has this requirement of total consistency of AG metadata, and should be relatively rare as compared to filesystem change operations. Online fsck coordinates with transaction chains as follows: -* For each AG, maintain a count of intent items targetting that AG. +* For each AG, maintain a count of intent items targeting that AG. The count should be bumped whenever a new item is added to the chain. The count should be dropped when the filesystem has locked the AG header buffers and finished the work.
@@ -2102,7 +2102,7 @@ quicksort and a heapsort subalgorithm in the spirit of kernel. To sort records in a reasonably short amount of time, ``xfarray`` takes advantage of the binary subpartitioning offered by quicksort, but it also uses -heapsort to hedge aginst performance collapse if the chosen quicksort pivots +heapsort to hedge against performance collapse if the chosen quicksort pivots are poor. Both algorithms are (in general) O(n * lg(n)), but there is a wide performance gulf between the two implementations.
@@ -2566,8 +2566,8 @@ old metadata blocks: The transaction rolling in steps 2c and 3 represent a weakness in the repair algorithm, because a log flush and a crash before the end of the reap step can result in space leaking. -Online repair functions minimize the chances of this occuring by using very -large transactions, which each can accomodate many thousands of block freeing +Online repair functions minimize the chances of this occurring by using very +large transactions, which each can accommodate many thousands of block freeing instructions. Repair moves on to reaping the old blocks, which will be presented in a subsequent :ref:`section<reaping>` after a few case studies of bulk loading.
@@ -5090,7 +5090,7 @@ This scan after validation of all filesystem metadata (except for the summary counters) as phase 6. The scan starts by calling ``FS_IOC_GETFSMAP`` to scan the filesystem space map to find areas that are allocated to file data fork extents. -Gaps betweeen data fork extents that are smaller than 64k are treated as if +Gaps between data fork extents that are smaller than 64k are treated as if they were data fork extents to reduce the command setup overhead. When the space map scan accumulates a region larger than 32MB, a media verification request is sent to the disk as a directio read of the raw block
Documentation/filesystems/zonefs.rst +1 -1
@@ -378,7 +378,7 @@ The attributes defined are as follows. sequential zone files. Failure to do so can result in write errors. * **max_active_seq_files**: This attribute reports the maximum number of sequential zone files that are in an active state, that is, sequential zone - files that are partially writen (not empty nor full) or that have a zone that + files that are partially written (not empty nor full) or that have a zone that is explicitly open (which happens only if the *explicit-open* mount option is used). This number is always equal to the maximum number of active zones that the device supports. A value of 0 means that the mounted device has no limit
Documentation/firmware-guide/acpi/osi.rst +1 -1
@@ -55,7 +55,7 @@ quirk, a bug, or a bug-fix. However this was discovered to be abused by other BIOS vendors to change completely unrelated code on completely unrelated systems. This prompted -an evaluation of all of it's uses. This uncovered that they aren't needed +an evaluation of all of its uses. This uncovered that they aren't needed for any of the original reasons. As such, the kernel will not respond to any custom Linux-* strings by default.
Documentation/gpu/amdgpu/display/mpo-overview.rst +1 -1
@@ -178,7 +178,7 @@ Multiple Display MPO AMDGPU supports display MPO when using multiple displays; however, this feature behavior heavily relies on the compositor implementation. Keep in mind that -usespace can define different policies. For example, some OSes can use MPO to +userspace can define different policies. For example, some OSes can use MPO to protect the plane that handles the video playback; notice that we don't have many limitations for a single display. Nonetheless, this manipulation can have many more restrictions for a multi-display scenario. The below example shows a
Documentation/gpu/drm-kms-helpers.rst +1 -1
@@ -378,7 +378,7 @@ SCDC Helper Functions Reference HDMI Infoframes Helper Reference ================================ -Strictly speaking this is not a DRM helper library but generally useable +Strictly speaking this is not a DRM helper library but generally usable by any driver interfacing with HDMI outputs like v4l or alsa drivers. But it nicely fits into the overall topic of mode setting helper libraries and hence is also included here.
Documentation/gpu/drm-kms.rst +3 -3
@@ -66,11 +66,11 @@ Composition Properties`_ and related chapters. For the output routing the first step is encoders (represented by :c:type:`struct drm_encoder <drm_encoder>`, see `Encoder Abstraction`_). Those are really just internal artifacts of the helper libraries used to implement KMS -drivers. Besides that they make it unecessarily more complicated for userspace +drivers. Besides that they make it unnecessarily more complicated for userspace to figure out which connections between a CRTC and a connector are possible, and what kind of cloning is supported, they serve no purpose in the userspace API. Unfortunately encoders have been exposed to userspace, hence can't remove them -at this point. Futhermore the exposed restrictions are often wrongly set by +at this point. Furthermore the exposed restrictions are often wrongly set by drivers, and in many cases not powerful enough to express the real restrictions. A CRTC can be connected to multiple encoders, and for an active CRTC there must be at least one encoder.
@@ -260,7 +260,7 @@ Taken all together there's two consequences for the atomic design: drm_crtc_state <drm_crtc_state>` for CRTCs and :c:type:`struct drm_connector_state <drm_connector_state>` for connectors. These are the only objects with userspace-visible and settable state. For internal state drivers - can subclass these structures through embeddeding, or add entirely new state + can subclass these structures through embedding, or add entirely new state structures for their globally shared hardware functions, see :c:type:`struct drm_private_state<drm_private_state>`.
Documentation/gpu/drm-usage-stats.rst +2 -2
@@ -8,7 +8,7 @@ DRM drivers can choose to export partly standardised text output via the `fops->show_fdinfo()` as part of the driver specific file operations registered in the `struct drm_driver` object registered with the DRM core. -One purpose of this output is to enable writing as generic as practicaly +One purpose of this output is to enable writing as generic as practically feasible `top(1)` like userspace monitoring tools. Given the differences between various DRM drivers the specification of the
@@ -119,7 +119,7 @@ drm-engine-<keystr> tag and shall contain the maximum frequency for the given engine. Taken together with drm-cycles-<keystr>, this can be used to calculate percentage utilization of the engine, whereas drm-engine-<keystr> only reflects time active without considering what frequency the engine is operating as a -percentage of it's maximum frequency. +percentage of its maximum frequency. Memory ^^^^^^
Documentation/gpu/i915.rst +2 -2
@@ -304,10 +304,10 @@ reads of following commands. Actions issued between different contexts and the only way to synchronize across contexts (even from the same file descriptor) is through the use of fences. At least as far back as Gen4, also have that a context carries with it a GPU HW context; -the HW context is essentially (most of atleast) the state of a GPU. +the HW context is essentially (most of at least) the state of a GPU. In addition to the ordering guarantees, the kernel will restore GPU state via HW context when commands are issued to a context, this saves -user space the need to restore (most of atleast) the GPU state at the +user space the need to restore (most of at least) the GPU state at the start of each batchbuffer. The non-deprecated ioctls to submit batchbuffer work can pass that ID (in the lower bits of drm_i915_gem_execbuffer2::rsvd1) to identify what context to use with the command.
Documentation/gpu/kms-properties.csv +1 -1
@@ -17,7 +17,7 @@ Owner Module/Drivers,Group,Property Name,Type,Property Values,Object attached,De ,Virtual GPU,“suggested X”,RANGE,"Min=0, Max=0xffffffff",Connector,property to suggest an X offset for a connector ,,“suggested Y”,RANGE,"Min=0, Max=0xffffffff",Connector,property to suggest an Y offset for a connector ,Optional,"""aspect ratio""",ENUM,"{ ""None"", ""4:3"", ""16:9"" }",Connector,TDB -i915,Generic,"""Broadcast RGB""",ENUM,"{ ""Automatic"", ""Full"", ""Limited 16:235"" }",Connector,"When this property is set to Limited 16:235 and CTM is set, the hardware will be programmed with the result of the multiplication of CTM by the limited range matrix to ensure the pixels normaly in the range 0..1.0 are remapped to the range 16/255..235/255." +i915,Generic,"""Broadcast RGB""",ENUM,"{ ""Automatic"", ""Full"", ""Limited 16:235"" }",Connector,"When this property is set to Limited 16:235 and CTM is set, the hardware will be programmed with the result of the multiplication of CTM by the limited range matrix to ensure the pixels normally in the range 0..1.0 are remapped to the range 16/255..235/255." ,,“audio”,ENUM,"{ ""force-dvi"", ""off"", ""auto"", ""on"" }",Connector,TBD ,SDVO-TV,“mode”,ENUM,"{ ""NTSC_M"", ""NTSC_J"", ""NTSC_443"", ""PAL_B"" } etc.",Connector,TBD ,,"""left_margin""",RANGE,"Min=0, Max= SDVO dependent",Connector,TBD
Documentation/gpu/komeda-kms.rst +2 -2
@@ -328,7 +328,7 @@ of course we’d better share as much as possible between different products. To achieve this, split the komeda device into two layers: CORE and CHIP. - CORE: for common features and capabilities handling. -- CHIP: for register programing and HW specific feature (limitation) handling. +- CHIP: for register programming and HW specific feature (limitation) handling. CORE can access CHIP by three chip function structures:
@@ -481,7 +481,7 @@ Build komeda to be a Linux module driver Now we have two level devices: - komeda_dev: describes the real display hardware. -- komeda_kms_dev: attachs or connects komeda_dev to DRM-KMS. +- komeda_kms_dev: attaches or connects komeda_dev to DRM-KMS. All komeda operations are supplied or operated by komeda_dev or komeda_kms_dev, the module driver is only a simple wrapper to pass the Linux command
Documentation/gpu/msm-crash-dump.rst +1 -1
@@ -23,7 +23,7 @@ module The module that generated the crashdump. time - The kernel time at crash formated as seconds.microseconds. + The kernel time at crash formatted as seconds.microseconds. comm Comm string for the binary that generated the fault.
Documentation/gpu/rfc/i915_scheduler.rst +1 -1
@@ -37,7 +37,7 @@ i915 with the DRM scheduler is: * Watchdog hooks into DRM scheduler * Lots of complexity of the GuC backend can be pulled out once integrated with DRM scheduler (e.g. state machine gets - simplier, locking gets simplier, etc...) + simpler, locking gets simpler, etc...) * Execlists backend will minimum required to hook in the DRM scheduler * Legacy interface * Features like timeslicing / preemption / virtual engines would
Documentation/gpu/rfc/i915_vm_bind.rst +1 -1
@@ -90,7 +90,7 @@ submission, they need only one dma-resv fence list updated. Thus, the fast path (where required mappings are already bound) submission latency is O(1) w.r.t the number of VM private BOs. -VM_BIND locking hirarchy +VM_BIND locking hierarchy ------------------------- The locking design here supports the older (execlist based) execbuf mode, the newer VM_BIND mode, the VM_BIND mode with GPU page faults and possible future
Documentation/gpu/todo.rst +4 -4
@@ -65,7 +65,7 @@ Clean up the clipped coordination confusion around planes --------------------------------------------------------- We have a helper to get this right with drm_plane_helper_check_update(), but -it's not consistently used. This should be fixed, preferrably in the atomic +it's not consistently used. This should be fixed, preferably in the atomic helpers (and drivers then moved over to clipped coordinates). Probably the helper should also be moved from drm_plane_helper.c to the atomic helpers, to avoid confusion - the other helpers in that file are all deprecated legacy
@@ -181,13 +181,13 @@ reversed. To solve this we need one standard per-object locking mechanism, which is dma_resv_lock(). This lock needs to be called as the outermost lock, with all -other driver specific per-object locks removed. The problem is tha rolling out +other driver specific per-object locks removed. The problem is that rolling out the actual change to the locking contract is a flag day, due to struct dma_buf buffer sharing. Level: Expert -Convert logging to drm_* functions with drm_device paramater +Convert logging to drm_* functions with drm_device parameter ------------------------------------------------------------ For drivers which could have multiple instances, it is necessary to
@@ -244,7 +244,7 @@ Level: Advanced Benchmark and optimize blitting and format-conversion function -------------------------------------------------------------- -Drawing to dispay memory quickly is crucial for many applications' +Drawing to display memory quickly is crucial for many applications' performance. On at least x86-64, sys_imageblit() is significantly slower than
Documentation/hwmon/pmbus-core.rst +1 -1
@@ -345,7 +345,7 @@ PMBUS_NO_CAPABILITY Some PMBus chips don't respond with valid data when reading the CAPABILITY register. For such chips, this flag should be set so that the PMBus core -driver doesn't use CAPABILITY to determine it's behavior. +driver doesn't use CAPABILITY to determine its behavior. PMBUS_READ_STATUS_AFTER_FAILED_CHECK
Documentation/input/devices/iforce-protocol.rst +1 -1
@@ -49,7 +49,7 @@ OP DATA == ==== The 2B, LEN and CS fields have disappeared, probably because USB handles -frames and data corruption is handled or unsignificant. +frames and data corruption is handled or insignificant. First, I describe effects that are sent by the device to the computer
Documentation/input/multi-touch-protocol.rst +1 -1
@@ -383,7 +383,7 @@ Finger Tracking --------------- The process of finger tracking, i.e., to assign a unique trackingID to each -initiated contact on the surface, is a Euclidian Bipartite Matching +initiated contact on the surface, is a Euclidean Bipartite Matching problem. At each event synchronization, the set of actual contacts is matched to the set of contacts from the previous synchronization. A full implementation can be found in [#f3]_.
Documentation/livepatch/reliable-stacktrace.rst +1 -1
@@ -40,7 +40,7 @@ Principally, the reliable stacktrace function must ensure that either: .. note:: In some cases it is legitimate to omit specific functions from the trace, but all other functions must be reported. These cases are described in - futher detail below. + further detail below. Secondly, the reliable stacktrace function must be robust to cases where the stack or other unwind state is corrupt or otherwise unreliable. The
Documentation/locking/lockdep-design.rst +2 -2
@@ -29,7 +29,7 @@ the validator will shoot a splat if incorrect. A lock-class's behavior is constructed by its instances collectively: when the first instance of a lock-class is used after bootup the class gets registered, then all (subsequent) instances will be mapped to the -class and hence their usages and dependecies will contribute to those of +class and hence their usages and dependencies will contribute to those of the class. A lock-class does not go away when a lock instance does, but it can be removed if the memory space of the lock class (static or dynamic) is reclaimed, this happens for example when a module is
@@ -105,7 +105,7 @@ exact case is for the lock as of the reporting time. +--------------+-------------+--------------+ The character '-' suggests irq is disabled because if otherwise the -charactor '?' would have been shown instead. Similar deduction can be +character '?' would have been shown instead. Similar deduction can be applied for '+' too. Unused locks (e.g., mutexes) cannot be part of the cause of an error.
Documentation/locking/locktorture.rst +1 -1
@@ -113,7 +113,7 @@ stutter without pausing. shuffle_interval - The number of seconds to keep the test threads affinitied + The number of seconds to keep the test threads affinitized to a particular subset of the CPUs, defaults to 3 seconds. Used in conjunction with test_no_idle_hz.
Documentation/locking/locktypes.rst +1 -1
@@ -500,7 +500,7 @@ caveats also apply to bit spinlocks. Some bit spinlocks are replaced with regular spinlock_t for PREEMPT_RT using conditional (#ifdef'ed) code changes at the usage site. In contrast, usage-site changes are not needed for the spinlock_t substitution. -Instead, conditionals in header files and the core locking implemementation +Instead, conditionals in header files and the core locking implementation enable the compiler to do the substitution transparently.
Documentation/mm/hmm.rst +1 -1
@@ -417,7 +417,7 @@ entries. Any attempt to access the swap entry results in a fault which is resovled by replacing the entry with the original mapping. A driver gets notified that the mapping has been changed by MMU notifiers, after which point it will no longer have exclusive access to the page. Exclusive access is -guranteed to last until the driver drops the page lock and page reference, at +guaranteed to last until the driver drops the page lock and page reference, at which point any CPU faults on the page may proceed as described. Memory cgroup (memcg) and rss accounting
Documentation/mm/hwpoison.rst +1 -1
@@ -48,7 +48,7 @@ of applications. KVM support requires a recent qemu-kvm release. For the KVM use there was need for a new signal type so that KVM can inject the machine check into the guest with the proper address. This in theory allows other applications to handle -memory failures too. The expection is that near all applications +memory failures too. The expectation is that most applications won't do that, but some very specialized ones might. Failure recovery modes
Documentation/mm/page_migration.rst +1 -1
@@ -180,7 +180,7 @@ The following events (counters) can be used to monitor page migration. 4. THP_MIGRATION_FAIL: A THP could not be migrated nor it could be split. 5. THP_MIGRATION_SPLIT: A THP was migrated, but not as such: first, the THP had - to be split. After splitting, a migration retry was used for it's sub-pages. + to be split. After splitting, a migration retry was used for its sub-pages. THP_MIGRATION_* events also update the appropriate PGMIGRATE_SUCCESS or PGMIGRATE_FAIL events. For example, a THP migration failure will cause both
Documentation/mm/unevictable-lru.rst +1 -1
@@ -463,7 +463,7 @@ can request that a region of memory be mlocked by supplying the MAP_LOCKED flag to the mmap() call. There is one important and subtle difference here, though. mmap() + mlock() will fail if the range cannot be faulted in (e.g. because mm_populate fails) and returns with ENOMEM while mmap(MAP_LOCKED) will not fail. -The mmaped area will still have properties of the locked area - pages will not +The mmapped area will still have properties of the locked area - pages will not get swapped out - but major page faults to fault memory in might still happen. Furthermore, any mmap() call or brk() call that expands the heap by a task
Documentation/mm/vmemmap_dedup.rst +1 -1
@@ -10,7 +10,7 @@ HugeTLB This section is to explain how HugeTLB Vmemmap Optimization (HVO) works. The ``struct page`` structures are used to describe a physical page frame. By -default, there is a one-to-one mapping from a page frame to it's corresponding +default, there is a one-to-one mapping from a page frame to its corresponding ``struct page``. HugeTLB pages consist of multiple base page size pages and is supported by many
Documentation/netlink/genetlink-c.yaml +1 -1
@@ -41,7 +41,7 @@ properties: description: Name of the define for the family name. type: string c-version-name: - description: Name of the define for the verion of the family. + description: Name of the define for the version of the family. type: string max-by-define: description: Makes the number of attributes and commands be specified by a define, not an enum value.
Documentation/netlink/genetlink-legacy.yaml +1 -1
@@ -41,7 +41,7 @@ properties: description: Name of the define for the family name. type: string c-version-name: - description: Name of the define for the verion of the family. + description: Name of the define for the version of the family. type: string max-by-define: description: Makes the number of attributes and commands be specified by a define, not an enum value.
Documentation/networking/bonding.rst +1 -1
@@ -1636,7 +1636,7 @@ your init script:: ----------------------------------------- This section applies to distros which use /etc/network/interfaces file -to describe network interface configuration, most notably Debian and it's +to describe network interface configuration, most notably Debian and its derivatives. The ifup and ifdown commands on Debian don't support bonding out of
Documentation/networking/devlink/devlink-port.rst +3 -3
@@ -321,9 +321,9 @@ API allows to configure following rate object's parameters: Allows for usage of Weighted Fair Queuing arbitration scheme among siblings. This arbitration scheme can be used simultaneously with the strict priority. As a node is configured with a higher rate it gets more - BW relative to it's siblings. Values are relative like a percentage + BW relative to its siblings. Values are relative like a percentage points, they basically tell how much BW should node take relative to - it's siblings. + its siblings. ``parent`` Parent node name. Parent node rate limits are considered as additional limits
@@ -343,7 +343,7 @@ Arbitration flow from the high level: #. If group of nodes have the same priority perform WFQ arbitration on that subgroup. Use ``tx_weight`` as a parameter for this arbitration. -#. Select the winner node, and continue arbitration flow among it's children, +#. Select the winner node, and continue arbitration flow among its children, until leaf node is reached, and the winner is established. #. If all the nodes from the highest priority sub-group are satisfied, or
Documentation/networking/packet_mmap.rst +1 -1
@@ -755,7 +755,7 @@ AF_PACKET TPACKET_V3 example ============================ AF_PACKET's TPACKET_V3 ring buffer can be configured to use non-static frame -sizes by doing it's own memory management. It is based on blocks where polling +sizes by doing its own memory management. It is based on blocks where polling works on a per block basis instead of per ring as in TPACKET_V2 and predecessor. It is said that TPACKET_V3 brings the following benefits:
Documentation/power/energy-model.rst +2 -2
@@ -87,9 +87,9 @@ CONFIG_ENERGY_MODEL must be enabled to use the EM framework. Registration of 'advanced' EM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The 'advanced' EM gets it's name due to the fact that the driver is allowed +The 'advanced' EM gets its name due to the fact that the driver is allowed to provide more precised power model. It's not limited to some implemented math -formula in the framework (like it's in 'simple' EM case). It can better reflect +formula in the framework (like it is in 'simple' EM case). It can better reflect the real power measurements performed for each performance state. Thus, this registration method should be preferred in case considering EM static power (leakage) is important.
Documentation/powerpc/dscr.rst +1 -1
@@ -6,7 +6,7 @@ DSCR register in powerpc allows user to have some control of prefetch of data stream in the processor. Please refer to the ISA documents or related manual for more detailed information regarding how to use this DSCR to attain this control of the prefetches . This document here provides an overview of kernel -support for DSCR, related kernel objects, it's functionalities and exported +support for DSCR, related kernel objects, its functionalities and exported user interface. (A) Data Structures:
Documentation/powerpc/kasan.txt +1 -1
@@ -40,7 +40,7 @@ checks can be delayed until after the MMU is set is up, and we can just not instrument any code that runs with translations off after booting. This is the current approach. -To avoid this limitiation, the KASAN shadow would have to be placed inside the +To avoid this limitation, the KASAN shadow would have to be placed inside the linear mapping, using the same high-bits trick we use for the rest of the linear mapping. This is tricky:
Documentation/powerpc/papr_hcalls.rst +1 -1
@@ -22,7 +22,7 @@ privileged operations. Currently there are two PAPR compliant hypervisors: On PPC64 arch a guest kernel running on top of a PAPR hypervisor is called a *pSeries guest*. A pseries guest runs in a supervisor mode (HV=0) and must issue hypercalls to the hypervisor whenever it needs to perform an action -that is hypervisor priviledged [3]_ or for other services managed by the +that is hypervisor privileged [3]_ or for other services managed by the hypervisor. Hence a Hypercall (hcall) is essentially a request by the pseries guest
Documentation/powerpc/qe_firmware.rst +2 -2
@@ -232,11 +232,11 @@ For example, to match the 8323, revision 1.0:: 'extended_modes' is a bitfield that defines special functionality which has an impact on the device drivers. Each bit has its own impact and has special instructions for the driver associated with it. This field is stored in -the QE library and available to any driver that calles qe_get_firmware_info(). +the QE library and available to any driver that calls qe_get_firmware_info(). 'vtraps' is an array of 8 words that contain virtual trap values for each virtual traps. As with 'extended_modes', this field is stored in the QE -library and available to any driver that calles qe_get_firmware_info(). +library and available to any driver that calls qe_get_firmware_info(). 'microcode' (type: struct qe_microcode): For each RISC processor there is one 'microcode' structure. The first
Documentation/powerpc/vas-api.rst +2 -2
@@ -46,7 +46,7 @@ request queue into the application's virtual address space. The application can then submit one or more requests to the engine by using copy/paste instructions and pasting the CRBs to the virtual address (aka paste_address) returned by mmap(). User space can close the -established connection or send window by closing the file descriptior +established connection or send window by closing the file descriptor (close(fd)) or upon the process exit. Note that applications can send several requests with the same window or
@@ -240,7 +240,7 @@ issued. This signal returns with the following siginfo struct:: siginfo.si_signo = SIGSEGV; siginfo.si_errno = EFAULT; siginfo.si_code = SEGV_MAPERR; - siginfo.si_addr = CSB adress; + siginfo.si_addr = CSB address; In the case of multi-thread applications, NX send windows can be shared across all threads. For example, a child thread can open a send window,
Documentation/process/botching-up-ioctls.rst +1 -1
@@ -208,7 +208,7 @@ Not every problem needs a new ioctl: it's much quicker to push a driver-private interface than engaging in lengthy discussions for a more generic solution. And occasionally doing a private interface to spearhead a new concept is what's required. But in the - end, once the generic interface comes around you'll end up maintainer two + end, once the generic interface comes around you'll end up maintaining two interfaces. Indefinitely. * Consider other interfaces than ioctls. A sysfs attribute is much better for
Documentation/process/kernel-docs.rst +1 -1
@@ -29,7 +29,7 @@ All documents are cataloged with the following fields: the document's The documents on each section of this document are ordered by its published date, from the newest to the oldest. The maintainer(s) should - periodically retire resources as they become obsolte or outdated; with + periodically retire resources as they become obsolete or outdated; with the exception of foundational books. Docs at the Linux Kernel tree
Documentation/riscv/hwprobe.rst +2 -2
@@ -88,11 +88,11 @@ The following keys are defined: always extremely slow. * :c:macro:`RISCV_HWPROBE_MISALIGNED_SLOW`: Misaligned accesses are supported - in hardware, but are slower than the cooresponding aligned accesses + in hardware, but are slower than the corresponding aligned accesses sequences. * :c:macro:`RISCV_HWPROBE_MISALIGNED_FAST`: Misaligned accesses are supported - in hardware and are faster than the cooresponding aligned accesses + in hardware and are faster than the corresponding aligned accesses sequences. * :c:macro:`RISCV_HWPROBE_MISALIGNED_UNSUPPORTED`: Misaligned accesses are
Documentation/riscv/vector.rst +1 -1
@@ -13,7 +13,7 @@ order to support the use of the RISC-V Vector Extension. Two new prctl() calls are added to allow programs to manage the enablement status for the use of Vector in userspace. The intended usage guideline for these interfaces is to give init systems a way to modify the availability of V -for processes running under its domain. Calling thess interfaces is not +for processes running under its domain. Calling these interfaces is not recommended in libraries routines because libraries should not override policies configured from the parant process. Also, users must noted that these interfaces are not portable to non-Linux, nor non-RISC-V environments, so it is discourage
Documentation/s390/vfio-ap.rst +1 -1
@@ -422,7 +422,7 @@ Configure the guest's AP resources Configuring the AP resources for a KVM guest will be performed when the VFIO_GROUP_NOTIFY_SET_KVM notifier callback is invoked. The notifier function is called when userspace connects to KVM. The guest's AP resources are -configured via it's APCB by: +configured via its APCB by: * Setting the bits in the APM corresponding to the APIDs assigned to the vfio_ap mediated device via its 'assign_adapter' interface.
Documentation/scheduler/sched-bwc.rst +1 -1
@@ -186,7 +186,7 @@ average usage, albeit over a longer time window than a single period. This also limits the burst ability to no more than 1ms per cpu. This provides better more predictable user experience for highly threaded applications with small quota limits on high core count machines. It also eliminates the -propensity to throttle these applications while simultanously using less than +propensity to throttle these applications while simultaneously using less than quota amounts of cpu. Another way to say this, is that by allowing the unused portion of a slice to remain valid across periods we have decreased the possibility of wastefully expiring quota on cpu-local silos that don't need a
Documentation/scheduler/sched-energy.rst +2 -2
@@ -82,7 +82,7 @@ through the arch_scale_cpu_capacity() callback. The rest of platform knowledge used by EAS is directly read from the Energy Model (EM) framework. The EM of a platform is composed of a power cost table per 'performance domain' in the system (see Documentation/power/energy-model.rst -for futher details about performance domains). +for further details about performance domains). The scheduler manages references to the EM objects in the topology code when the scheduling domains are built, or re-built. For each root domain (rd), the
@@ -281,7 +281,7 @@ mechanism called 'over-utilization'. From a general standpoint, the use-cases where EAS can help the most are those involving a light/medium CPU utilization. Whenever long CPU-bound tasks are being run, they will require all of the available CPU capacity, and there isn't -much that can be done by the scheduler to save energy without severly harming +much that can be done by the scheduler to save energy without severely harming throughput. In order to avoid hurting performance with EAS, CPUs are flagged as 'over-utilized' as soon as they are used at more than 80% of their compute capacity. As long as no CPUs are over-utilized in a root domain, load balancing
Documentation/scsi/ChangeLog.lpfc +1 -1
@@ -427,7 +427,7 @@ Changes from 20041207 to 20041213 * Changed version number to 8.0.17 * Fix sparse warnings by adding __iomem markers to lpfc_compat.h. * Fix some sparse warnings -- 0 used as NULL pointer. - * Make sure there's a space between every if and it's (. + * Make sure there's a space between every if and its (. * Fix some overly long lines and make sure hard tabs are used for indentation. * Remove all trailing whitespace.
Documentation/security/digsig.rst +1 -1
@@ -82,7 +82,7 @@ The signing and key management utilities evm-utils provide functionality to generate signatures, to load keys into the kernel keyring. Keys can be in PEM or converted to the kernel format. When the key is added to the kernel keyring, the keyid defines the name -of the key: 5D2B05FC633EE3E8 in the example bellow. +of the key: 5D2B05FC633EE3E8 in the example below. Here is example output of the keyctl utility::
Documentation/security/keys/core.rst +1 -1
@@ -869,7 +869,7 @@ The keyctl syscall functions are: - ``char *hashname`` specifies the NUL terminated string identifying the hash used from the kernel crypto API and applied for the KDF - operation. The KDF implemenation complies with SP800-56A as well + operation. The KDF implementation complies with SP800-56A as well as with SP800-108 (the counter KDF). - ``char *otherinfo`` specifies the OtherInfo data as documented in
Documentation/security/secrets/coco.rst +1 -1
@@ -34,7 +34,7 @@ be use it for its own purposes. During the VM's launch, the virtual machine manager may inject a secret to that area. In AMD SEV and SEV-ES this is performed using the -``KVM_SEV_LAUNCH_SECRET`` command (see [sev]_). The strucutre of the injected +``KVM_SEV_LAUNCH_SECRET`` command (see [sev]_). The structure of the injected Guest Owner secret data should be a GUIDed table of secret values; the binary format is described in ``drivers/virt/coco/efi_secret/efi_secret.c`` under "Structure of the EFI secret area".
Documentation/sphinx/cdomain.py +1 -1
@@ -178,7 +178,7 @@ class CObject(Base_CObject): if len(arglist[0].split(" ")) > 1: return False - # This is a function-like macro, it's arguments are typeless! + # This is a function-like macro, its arguments are typeless! signode += addnodes.desc_name(fullname, fullname) paramlist = addnodes.desc_parameterlist() signode += paramlist
Documentation/spi/spi-lm70llp.rst +1 -1
@@ -69,7 +69,7 @@ Interpreting this circuit, when the LM70 SI/O line is High (or tristate and not grounded by the host via D7), the transistor conducts and switches the collector to zero, which is reflected on pin 13 of the DB25 parport connector. When SI/O is Low (driven by the LM70 or the host) on the other -hand, the transistor is cut off and the voltage tied to it's collector is +hand, the transistor is cut off and the voltage tied to its collector is reflected on pin 13 as a High level. So: the getmiso inline routine in this driver takes this fact into account,
Documentation/tools/rtla/rtla-timerlat-top.rst +1 -1
@@ -117,7 +117,7 @@ syscall in a btrfs file system. The raw trace is saved in the **timerlat_trace.txt** file for further analysis. Note that **rtla timerlat** was dispatched without changing *timerlat* tracer -threads' priority. That is generally not needed because these threads hava +threads' priority. That is generally not needed because these threads have priority *FIFO:95* by default, which is a common priority used by real-time kernel developers to analyze scheduling delays.
Documentation/trace/coresight/coresight-etm4x-reference.rst +1 -1
@@ -675,7 +675,7 @@ Bit assignments shown below:- reconstructed using only conditional branches. There is currently no support in Perf for supplying modified binaries to the decoder, so this - feature is only inteded to be used for debugging purposes or with a 3rd party tool. + feature is only intended to be used for debugging purposes or with a 3rd party tool. Choosing this option will result in a significant increase in the amount of trace generated - possible danger of overflows, or fewer instructions covered. Note, that this option also
Documentation/trace/events.rst +3 -3
@@ -915,7 +915,7 @@ functions can be used. To create a kprobe event, an empty or partially empty kprobe event should first be created using kprobe_event_gen_cmd_start(). The name -of the event and the probe location should be specfied along with one +of the event and the probe location should be specified along with one or args each representing a probe field should be supplied to this function. Before calling kprobe_event_gen_cmd_start(), the user should create and initialize a dynevent_cmd object using
@@ -995,7 +995,7 @@ The basic idea is simple and amounts to providing a general-purpose layer that can be used to generate trace event commands. The generated command strings can then be passed to the command-parsing and event creation code that already exists in the trace event -subystem for creating the corresponding trace events. +subsystem for creating the corresponding trace events. In a nutshell, the way it works is that the higher-level interface code creates a struct dynevent_cmd object, then uses a couple
@@ -1068,7 +1068,7 @@ to add an operator between the pair (here none) and a separator to be appended onto the end of the arg pair (here ';'). There's also a dynevent_str_add() function that can be used to simply -add a string as-is, with no spaces, delimeters, or arg check. +add a string as-is, with no spaces, delimiters, or arg check. Any number of dynevent_*_add() calls can be made to build up the string (until its length surpasses cmd->maxlen). When all the arguments have
Documentation/trace/fprobe.rst +1 -1
@@ -113,7 +113,7 @@ If the entry callback function returns !0, the corresponding exit callback will the instruction pointer of @regs may be different from the @entry_ip in the entry_handler. If you need traced instruction pointer, you need to use @entry_ip. On the other hand, in the exit_handler, the instruction - pointer of @regs is set to the currect return address. + pointer of @regs is set to the current return address. @entry_data This is a local storage to share the data between entry and exit handlers.
Documentation/trace/ftrace.rst +1 -1
@@ -2725,7 +2725,7 @@ It is default disabled. The return value of each traced function can be displayed after an equal sign "=". When encountering system call failures, it -can be verfy helpful to quickly locate the function that first +can be very helpful to quickly locate the function that first returns an error code. - hide: echo nofuncgraph-retval > trace_options
Documentation/trace/hwlat_detector.rst +1 -1
@@ -14,7 +14,7 @@ originally written for use by the "RT" patch since the Real Time kernel is highly latency sensitive. SMIs are not serviced by the Linux kernel, which means that it does not -even know that they are occuring. SMIs are instead set up by BIOS code +even know that they are occurring. SMIs are instead set up by BIOS code and are serviced by BIOS code, usually for "critical" events such as management of thermal sensors and fans. Sometimes though, SMIs are used for other tasks and those tasks can spend an inordinate amount of time in the
Documentation/trace/rv/da_monitor_synthesis.rst +1 -1
@@ -1,7 +1,7 @@ Deterministic Automata Monitor Synthesis ======================================== -The starting point for the application of runtime verification (RV) technics +The starting point for the application of runtime verification (RV) techniques is the *specification* or *modeling* of the desired (or undesired) behavior of the system under scrutiny.
Documentation/trace/rv/monitor_wwnr.rst +1 -1
@@ -26,7 +26,7 @@ definition:: | running | -+ +-------------+ -This model is borken, the reason is that a task can be running +This model is broken, the reason is that a task can be running in the processor without being set as RUNNABLE. Think about a task about to sleep::
Documentation/trace/rv/runtime-verification.rst +1 -1
@@ -31,7 +31,7 @@ In Linux terms, the runtime verification monitors are encapsulated inside the *RV monitor* abstraction. A *RV monitor* includes a reference model of the system, a set of instances of the monitor (per-cpu monitor, per-task monitor, and so on), and the helper functions that glue the monitor to the system via -trace, as depicted bellow:: +trace, as depicted below:: Linux +---- RV Monitor ----------------------------------+ Formal Realm | | Realm
Documentation/trace/uprobetracer.rst +1 -1
@@ -55,7 +55,7 @@ Synopsis of uprobe_tracer (\*1) only for return probe. (\*2) this is useful for fetching a field of data structures. - (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe + (\*3) Unlike kprobe event, "u" prefix will just be ignored, because uprobe events can access only user-space memory. Types
Documentation/trace/user_events.rst +1 -1
@@ -93,7 +93,7 @@ or perf record -e user_events:[name] when attaching/recording. **NOTE:** The event subsystem name by default is "user_events". Callers should not assume it will always be "user_events". Operators reserve the right in the -future to change the subsystem name per-process to accomodate event isolation. +future to change the subsystem name per-process to accommodate event isolation. Command Format ^^^^^^^^^^^^^^
Documentation/usb/gadget_uvc.rst +1 -1
@@ -168,7 +168,7 @@ Header linking The UVC specification requires that Format and Frame descriptors be preceded by Headers detailing things such as the number and cumulative size of the different -Format descriptors that follow. This and similar operations are acheived in +Format descriptors that follow. This and similar operations are achieved in configfs by linking between the configfs item representing the header and the config items representing those other descriptors, in this manner:
Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst +1 -1
@@ -3293,7 +3293,7 @@ AV1 Frame Restoration Type. .. c:type:: v4l2_av1_loop_restoration -AV1 Loop Restauration as described in section 6.10.15 "Loop restoration params +AV1 Loop Restoration as described in section 6.10.15 "Loop restoration params semantics" of :ref:`av1`. .. cssclass:: longtable
Documentation/userspace-api/media/v4l/metafmt-d4xx.rst +1 -1
@@ -237,7 +237,7 @@ Fish Eye sensor: :: camera projectors. As we have another field for "Laser Power" we introduced "LED Power" for extra emitter. -The "Laser mode" __u32 fiels has been split into: :: +The "Laser mode" __u32 fields has been split into: :: 1 __u8 Emitter mode 2 __u8 RFU byte 3 __u16 LED Power
Documentation/userspace-api/netlink/intro.rst +1 -1
@@ -615,7 +615,7 @@ and ``SET``. Each object can handle all or some of those requests is defined by the 2 lowest bits of the message type, so commands for new objects would always be allocated with a stride of 4. -Each object would also have it's own fixed metadata shared by all request +Each object would also have its own fixed metadata shared by all request types (e.g. struct ifinfomsg for netdev requests, struct ifaddrmsg for address requests, struct tcmsg for qdisc requests).
Documentation/virt/hyperv/clocks.rst +1 -1
@@ -60,7 +60,7 @@ vDSO, and gettimeofday() and related system calls can execute entirely in user space. The vDSO is implemented by mapping the shared page with scale and offset values into user space. User space code performs the same algorithm of reading the TSC and -appying the scale and offset to get the constant 10 MHz clock. +applying the scale and offset to get the constant 10 MHz clock. Linux clockevents are based on Hyper-V synthetic timer 0. While Hyper-V offers 4 synthetic timers for each CPU, Linux only uses
Documentation/virt/kvm/api.rst +13 -13
@@ -578,7 +578,7 @@ This is an asynchronous vcpu ioctl and can be invoked from any thread. RISC-V: ^^^^^^^ -Queues an external interrupt to be injected into the virutal CPU. This ioctl +Queues an external interrupt to be injected into the virtual CPU. This ioctl is overloaded with 2 different irq values: a) KVM_INTERRUPT_SET
@@ -2722,7 +2722,7 @@ The isa config register can be read anytime but can only be written before a Guest VCPU runs. It will have ISA feature bits matching underlying host set by default. -RISC-V core registers represent the general excution state of a Guest VCPU +RISC-V core registers represent the general execution state of a Guest VCPU and it has the following id bit patterns:: 0x8020 0000 02 <index into the kvm_riscv_core struct:24> (32bit Host)
@@ -5232,7 +5232,7 @@ KVM_PV_DISABLE Deregister the VM from the Ultravisor and reclaim the memory that had been donated to the Ultravisor, making it usable by the kernel again. All registered VCPUs are converted back to non-protected ones. If a - previous protected VM had been prepared for asynchonous teardown with + previous protected VM had been prepared for asynchronous teardown with KVM_PV_ASYNC_CLEANUP_PREPARE and not subsequently torn down with KVM_PV_ASYNC_CLEANUP_PERFORM, it will be torn down in this call together with the current protected VM.
@@ -5692,7 +5692,7 @@ flags values for ``kvm_sregs2``: ``KVM_SREGS2_FLAGS_PDPTRS_VALID`` - Indicates thats the struct contain valid PDPTR values. + Indicates that the struct contains valid PDPTR values. 4.132 KVM_SET_SREGS2
@@ -6263,7 +6263,7 @@ to the byte array. It is strongly recommended that userspace use ``KVM_EXIT_IO`` (x86) or ``KVM_EXIT_MMIO`` (all except s390) to implement functionality that -requires a guest to interact with host userpace. +requires a guest to interact with host userspace. .. note:: KVM_EXIT_IO is significantly faster than KVM_EXIT_MMIO.
@@ -6336,7 +6336,7 @@ s390 specific. } s390_ucontrol; s390 specific. A page fault has occurred for a user controlled virtual -machine (KVM_VM_S390_UNCONTROL) on it's host page table that cannot be +machine (KVM_VM_S390_UNCONTROL) on its host page table that cannot be resolved by the kernel. The program code and the translation exception code that were placed in the cpu's lowcore are presented here as defined by the z Architecture
@@ -7510,7 +7510,7 @@ APIC/MSRs/etc). attribute is not supported by KVM. KVM_CAP_SGX_ATTRIBUTE enables a userspace VMM to grant a VM access to one or -more priveleged enclave attributes. args[0] must hold a file handle to a valid +more privileged enclave attributes. args[0] must hold a file handle to a valid SGX attribute file corresponding to an attribute that is supported/restricted by KVM (currently only PROVISIONKEY).
@@ -7928,7 +7928,7 @@ writing to the respective MSRs. This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its value is used to denote the target vcpu for a SynIC interrupt. For -compatibilty, KVM initializes this msr to KVM's internal vcpu index. When this +compatibility, KVM initializes this msr to KVM's internal vcpu index. When this capability is absent, userspace can still query this msr's value. 8.13 KVM_CAP_S390_AIS_MIGRATION
@@ -8118,10 +8118,10 @@ regardless of what has actually been exposed through the CPUID leaf. :Parameters: args[0] - size of the dirty log ring KVM is capable of tracking dirty memory using ring buffers that are -mmaped into userspace; there is one dirty ring per vcpu. +mmapped into userspace; there is one dirty ring per vcpu. The dirty ring is available to userspace as an array of -``struct kvm_dirty_gfn``. Each dirty entry it's defined as:: +``struct kvm_dirty_gfn``. Each dirty entry is defined as:: struct kvm_dirty_gfn { __u32 flags;
@@ -8160,7 +8160,7 @@ state machine for the entry is as follows:: | | +------------------------------------------+ -To harvest the dirty pages, userspace accesses the mmaped ring buffer +To harvest the dirty pages, userspace accesses the mmapped ring buffer to read the dirty GFNs. If the flags has the DIRTY bit set (at this stage the RESET bit must be cleared), then it means this GFN is a dirty GFN. The userspace should harvest this GFN and mark the flags from state
@@ -8286,7 +8286,7 @@ the KVM_XEN_ATTR_TYPE_RUNSTATE_UPDATE_FLAG attribute in the KVM_XEN_SET_ATTR and KVM_XEN_GET_ATTR ioctls. This controls whether KVM will set the XEN_RUNSTATE_UPDATE flag in guest memory mapped vcpu_runstate_info during updates of the runstate information. Note that versions of KVM which support -the RUNSTATE feature above, but not thie RUNSTATE_UPDATE_FLAG feature, will +the RUNSTATE feature above, but not the RUNSTATE_UPDATE_FLAG feature, will always set the XEN_RUNSTATE_UPDATE flag when updating the guest structure, which is perhaps counterintuitive. When this flag is advertised, KVM will behave more correctly, not using the XEN_RUNSTATE_UPDATE flag until/unless
@@ -8335,7 +8335,7 @@ Architectures: x86 When enabled, KVM will disable emulated Hyper-V features provided to the guest according to the bits Hyper-V CPUID feature leaves. Otherwise, all -currently implmented Hyper-V features are provided unconditionally when +currently implemented Hyper-V features are provided unconditionally when Hyper-V identification is set in the HYPERV_CPUID_INTERFACE (0x40000001) leaf.
Documentation/virt/kvm/devices/vm.rst +1 -1
@@ -92,7 +92,7 @@ Allows user space to retrieve or request to change cpu related information for a KVM does not enforce or limit the cpu model data in any form. Take the information retrieved by means of KVM_S390_VM_CPU_MACHINE as hint for reasonable configuration setups. Instruction interceptions triggered by additionally set facility bits that -are not handled by KVM need to by imlemented in the VM driver code. +are not handled by KVM need to by implemented in the VM driver code. :Parameters: address of buffer to store/set the processor related cpu data of type struct kvm_s390_vm_cpu_processor*.
Documentation/virt/kvm/devices/xive.rst +1 -1
@@ -50,7 +50,7 @@ the legacy interrupt mode, referred as XICS (POWER7/8). When a device is passed-through into the guest, the source interrupts are from a different HW controller (PHB4) and the ESB - pages exposed to the guest should accommadate this change. + pages exposed to the guest should accommodate this change. The passthru_irq helpers, kvmppc_xive_set_mapped() and kvmppc_xive_clr_mapped() are called when the device HW irqs are
Documentation/virt/kvm/halt-polling.rst +1 -1
@@ -14,7 +14,7 @@ before giving up the cpu to the scheduler in order to let something else run. Polling provides a latency advantage in cases where the guest can be run again very quickly by at least saving us a trip through the scheduler, normally on the order of a few micro-seconds, although performance benefits are workload -dependant. In the event that no wakeup source arrives during the polling +dependent. In the event that no wakeup source arrives during the polling interval or some other task on the runqueue is runnable the scheduler is invoked. Thus halt polling is especially useful on workloads with very short wakeup periods where the time spent halt polling is minimised and the time
Documentation/virt/kvm/x86/mmu.rst +1 -1
@@ -245,7 +245,7 @@ Shadow pages contain the following information: unsynchronized children). unsync_child_bitmap: A bitmap indicating which sptes in spt point (directly or indirectly) at - pages that may be unsynchronized. Used to quickly locate all unsychronized + pages that may be unsynchronized. Used to quickly locate all unsynchronized pages reachable from a given page. clear_spte_count: Only present on 32-bit hosts, where a 64-bit spte cannot be written
Documentation/virt/kvm/x86/running-nested-guests.rst +1 -1
@@ -169,7 +169,7 @@ Enabling "nested" (s390x) $ modprobe kvm nested=1 .. note:: On s390x, the kernel parameter ``hpage`` is mutually exclusive - with the ``nested`` paramter — i.e. to be able to enable + with the ``nested`` parameter — i.e. to be able to enable ``nested``, the ``hpage`` parameter *must* be disabled. 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU
Documentation/virt/uml/user_mode_linux_howto_v2.rst +1 -1
@@ -1224,7 +1224,7 @@ between a driver and the host at the UML command line is OK security-wise. Allowing it as a loadable module parameter isn't. -If such functionality is desireable for a particular application +If such functionality is desirable for a particular application (e.g. loading BPF "firmware" for raw socket network transports), it should be off by default and should be explicitly turned on as a command line parameter at startup.
Documentation/w1/slaves/w1_therm.rst +1 -1
@@ -58,7 +58,7 @@ A strong pullup will be applied during the conversion if required. ``conv_time`` is used to get current conversion time (read), and adjust it (write). A temperature conversion time depends on the device type and -it's current resolution. Default conversion time is set by the driver according +its current resolution. Default conversion time is set by the driver according to the device datasheet. A conversion time for many original device clones deviate from datasheet specs. There are three options: 1) manually set the correct conversion time by writing a value in milliseconds to ``conv_time``; 2)
Documentation/w1/w1-generic.rst +1 -1
@@ -101,7 +101,7 @@ w1_master_search (rw) the number of searches left to do, w1_master_slave_count (ro) the number of slaves found w1_master_slaves (ro) the names of the slaves, one per line w1_master_timeout (ro) the delay in seconds between searches -w1_master_timeout_us (ro) the delay in microseconds beetwen searches +w1_master_timeout_us (ro) the delay in microseconds between searches ========================= ===================================================== If you have a w1 bus that never changes (you don't add or remove devices),
Documentation/w1/w1-netlink.rst +1 -1
@@ -66,7 +66,7 @@ Each connector message can include one or more w1_netlink_msg with zero or more attached w1_netlink_cmd messages. For event messages there are no w1_netlink_cmd embedded structures, -only connector header and w1_netlink_msg strucutre with "len" field +only connector header and w1_netlink_msg structure with "len" field being zero and filled type (one of event types) and id: either 8 bytes of slave unique id in host order, or master's id, which is assigned to bus master device
Documentation/watchdog/watchdog-kernel-api.rst +1 -1
@@ -77,7 +77,7 @@ It contains following fields: * groups: List of sysfs attribute groups to create when creating the watchdog device. * info: a pointer to a watchdog_info structure. This structure gives some - additional information about the watchdog timer itself. (Like it's unique name) + additional information about the watchdog timer itself. (Like its unique name) * ops: a pointer to the list of watchdog operations that the watchdog supports. * gov: a pointer to the assigned watchdog device pretimeout governor or NULL. * timeout: the watchdog timer's timeout value (in seconds).
Documentation/wmi/devices/dell-wmi-ddv.rst +2 -2
@@ -185,7 +185,7 @@ Performs an analysis of the battery and returns a status code: WMI method BatteryeRawAnalytics() --------------------------------- -Returns a buffer usually containg 12 blocks of analytics data. +Returns a buffer usually containing 12 blocks of analytics data. Those blocks contain: - block number starting with 0 (u8) - 31 bytes of unknown data
@@ -217,7 +217,7 @@ Returns the WMI interface version as an u32. WMI method FanSensorInformation() --------------------------------- -Returns a buffer containg fan sensor entries, terminated +Returns a buffer containing fan sensor entries, terminated with a single ``0xff``. Those entries contain:
Signature · 1 line
2.34.1
Quoted 8 lines · Bjorn Helgaas
From: Bjorn Helgaas <[email protected]>
Fix typos in Documentation. I split these into:
Documentation/ABI/
Documentation/devicetree/bindings/
<everything else>
Quoted 9 lines
If it would be better split more or differently, I'm happy to do that. These are strictly typo fixes, no clarification or rewording.
Bjorn Helgaas (3):
Documentation/ABI: Fix typos
dt-bindings: Fix typos
Documentation: Fix typos
I've applied parts 1 and 3, thanks.
jon