dt-bindings: Fix typos
Subsystems (9)
PATCH 1/1 dt-bindings: Fix typos
From: Bjorn Helgaas <[email protected]>
Fix typos in Documentation/devicetree/bindings. The changes are in descriptions or comments where they shouldn't affect functionality.
---
This is a follow-up to the patch at [1] for things that conflicted with other changes in linux-next, plus a couple that I missed before.
Based on next-20230821: 47d9bb711707 ("Add linux-next specific files for 20230821")
[1] https://lore.kernel.org/r/[email protected]
.../devicetree/bindings/leds/leds-group-multicolor.yaml | 2 +- Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml | 4 ++-- Documentation/devicetree/bindings/phy/apm-xgene-phy.txt | 2 +- .../devicetree/bindings/serial/nvidia,tegra20-hsuart.yaml | 2 +- .../devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-)
Documentation/devicetree/bindings/leds/leds-group-multicolor.yaml +1 -1
@@ -19,7 +19,7 @@ properties: leds: description: - An aray of monochromatic leds + An array of monochromatic LEDs $ref: /schemas/types.yaml#/definitions/phandle-array required:
Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml +2 -2
@@ -59,7 +59,7 @@ properties: be configured with hardware pull-up resistors to match the SOC voltage (usually 1.8V). The software can read the registers to obtain the LDO voltage and configure - the legal drive strength(curren). + the legal drive strength(current). ===================================================== | voltage | current Available (uA) | | 1.8v | 1200 2100 2700 2910 3110 3600 3970 4350 |
@@ -76,7 +76,7 @@ properties: be configured with hardware pull-up resistors to match the SOC voltage (usually 1.8V). The software can read the registers to obtain the LDO voltage and configure - the legal drive strength(curren). + the legal drive strength(current). ===================================================== | voltage | current Available (uA) | | 1.8v | 1200 2100 2700 2910 3110 3600 3970 4350 |
Documentation/devicetree/bindings/phy/apm-xgene-phy.txt +1 -1
@@ -36,7 +36,7 @@ Optional properties: 3-tuple setting for each (up to 3) supported link speed on the host. Range is 0 to 273000 in unit of uV. Default is 0. -- apm,tx-pre-cursor2 : 2st pre-cursor emphasis taps control. Two set of +- apm,tx-pre-cursor2 : 2nd pre-cursor emphasis taps control. Two set of 3-tuple setting for each (up to 3) supported link speed on the host. Range is 0 to 127400 in unit uV. Default is 0x0.
Documentation/devicetree/bindings/serial/nvidia,tegra20-hsuart.yaml +1 -1
@@ -78,7 +78,7 @@ properties: we use nvidia,adjust-baud-rates. As an example, consider there is deviation observed in TX for baud rates as listed below. 0 - to 9600 has 1% deviation 9600 to 115200 2% deviation. This slight deviation is expcted and + to 9600 has 1% deviation 9600 to 115200 2% deviation. 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/thermal/nvidia,tegra124-soctherm.yaml +1 -1
@@ -155,7 +155,7 @@ properties: 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 + by a temperature in milli Celsius. In the absence of this property the critical trip point will be used for thermtrip temperature. Note:
Signature · 1 line
2.34.1
Quoted 6 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]>
Hi,
One nit below. In any case:
Thanks.
Quoted 22 lines
---
This is a follow-up to the patch at [1] for things that conflicted with other changes in linux-next, plus a couple that I missed before.Based on next-20230821:
47d9bb711707("Add linux-next specific files for 20230821")[1] https://lore.kernel.org/r/[email protected]
.../devicetree/bindings/leds/leds-group-multicolor.yaml | 2 +- Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml | 4 ++-- Documentation/devicetree/bindings/phy/apm-xgene-phy.txt | 2 +- .../devicetree/bindings/serial/nvidia,tegra20-hsuart.yaml | 2 +- .../devicetree/bindings/thermal/nvidia,tegra124-soctherm.yaml | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-)Documentation/devicetree/bindings/phy/apm-xgene-phy.txt +0
-0
Documentation/devicetree/bindings/phy/apm-xgene-phy.txt Optional properties: · line 39
Quoted 5 lines
Documentation/devicetree/bindings/phy/apm-xgene-phy.txt +1
-1@@ -36,7 +36,7 @@ Optional properties: 3-tuple setting for each (up to 3) supported link speed on the host. Range is 0 to 273000 in unit of uV. Default is 0. -- apm,tx-pre-cursor2 : 2st pre-cursor emphasis taps control. Two set of +- apm,tx-pre-cursor2 : 2nd pre-cursor emphasis taps control. Two set of
s/set/sets/
Quoted 3 lines
Documentation/devicetree/bindings/phy/apm-xgene-phy.txt +0
-03-tuple setting for each (up to 3) supported link speed on the host. Range is 0 to 127400 in unit uV. Default is 0x0.
Signature · 1 line
~Randy