Remove trailing whitespace from devicetree binding documentation files: - regulator/regulator-max77620.txt - interrupt-controller/nvidia,tegra20-ictlr.txt - interrupt-controller/msi.txt No functional changes. Issues detected using checkpatch.pl script. Signed-off-by: Abhinav Saxena <xandfury@xxxxxxxxx> --- .../devicetree/bindings/interrupt-controller/msi.txt | 10 +++++----- .../interrupt-controller/nvidia,tegra20-ictlr.txt | 2 +- .../bindings/regulator/regulator-max77620.txt | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Documentation/devicetree/bindings/interrupt-controller/msi.txt b/Documentation/devicetree/bindings/interrupt-controller/msi.txt index c20b51df7138..2109a3454cf6 100644 --- a/Documentation/devicetree/bindings/interrupt-controller/msi.txt +++ b/Documentation/devicetree/bindings/interrupt-controller/msi.txt @@ -12,17 +12,17 @@ potentially including additional information. MSIs are distinguished by some combination of: - The doorbell (the MMIO address written to). - + Devices may be configured by software to write to arbitrary doorbells which they can address. An MSI controller may feature a number of doorbells. - The payload (the value written to the doorbell). - + Devices may be configured to write an arbitrary payload chosen by software. MSI controllers may have restrictions on permitted payloads. - Sideband information accompanying the write. - + Typically this is neither configurable nor probeable, and depends on the path taken through the memory system (i.e. it is a property of the combination of MSI controller and device rather than a property of either in isolation). @@ -48,7 +48,7 @@ Optional properties: not encode doorbells or payloads as these can be configured dynamically. The meaning of the msi-specifier is defined by the device tree binding of - the specific MSI controller. + the specific MSI controller. MSI clients @@ -117,7 +117,7 @@ Example reg = <0x1 0xf00>; compatible = "vendor-c,some-device"; - /* + /* * Can generate MSIs to either A or B. */ msi-parent = <&msi_a>, <&msi_b 0x17>; diff --git a/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt b/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt index 2ff356640100..0c37e569e6f3 100644 --- a/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt +++ b/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt @@ -12,7 +12,7 @@ Required properties: - compatible : should be: "nvidia,tegra<chip>-ictlr". The LIC on subsequent SoCs remained backwards-compatible with Tegra30, so on Tegra generations later than Tegra30 the compatible value should - include "nvidia,tegra30-ictlr". + include "nvidia,tegra30-ictlr". - reg : Specifies base physical address and size of the registers. Each controller must be described separately (Tegra20 has 4 of them, whereas Tegra30 and later have 5). diff --git a/Documentation/devicetree/bindings/regulator/regulator-max77620.txt b/Documentation/devicetree/bindings/regulator/regulator-max77620.txt index bcf788897e44..7484c0728e27 100644 --- a/Documentation/devicetree/bindings/regulator/regulator-max77620.txt +++ b/Documentation/devicetree/bindings/regulator/regulator-max77620.txt @@ -65,14 +65,14 @@ Following are additional properties: Valid values are 0 to 7. This is applicable if FPS source is selected as FPS0, FPS1 or FPS2. - + - maxim,active-fps-power-down-slot: Sequencing event slot number on which the regulator get disabled when master FPS input event set to LOW. Valid values are 0 to 7. This is applicable if FPS source is selected as FPS0, FPS1 or FPS2. - + - maxim,suspend-fps-source: This is same as property "maxim,active-fps-source" but value get configured when system enters in -- 2.34.1
