Documentation: devicetree: Fix double words in Doumentation/devicetree
This patch fix multiple words such as "the the" and "which which" in Documentation/devicetree. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
633708a4a4
commit
ac3e8ea1d3
@ -8,7 +8,7 @@ Properties:
|
|||||||
"qcom,kpss-timer" - krait subsystem
|
"qcom,kpss-timer" - krait subsystem
|
||||||
"qcom,scss-timer" - scorpion subsystem
|
"qcom,scss-timer" - scorpion subsystem
|
||||||
|
|
||||||
- interrupts : Interrupts for the the debug timer, the first general purpose
|
- interrupts : Interrupts for the debug timer, the first general purpose
|
||||||
timer, and optionally a second general purpose timer in that
|
timer, and optionally a second general purpose timer in that
|
||||||
order.
|
order.
|
||||||
|
|
||||||
|
@ -9,7 +9,7 @@ Properties:
|
|||||||
|
|
||||||
Compatibility with many Cavium evaluation boards.
|
Compatibility with many Cavium evaluation boards.
|
||||||
|
|
||||||
- reg: The base address of the the CF chip select banks. Depending on
|
- reg: The base address of the CF chip select banks. Depending on
|
||||||
the device configuration, there may be one or two banks.
|
the device configuration, there may be one or two banks.
|
||||||
|
|
||||||
- cavium,bus-width: The width of the connection to the CF devices. Valid
|
- cavium,bus-width: The width of the connection to the CF devices. Valid
|
||||||
|
@ -12,7 +12,7 @@ configuration register for writes. These configuration register may be used to
|
|||||||
enable (and disable in some cases) SoC pin drivers, select peripheral clock
|
enable (and disable in some cases) SoC pin drivers, select peripheral clock
|
||||||
sources (internal or pin), etc. In some cases, a configuration register is
|
sources (internal or pin), etc. In some cases, a configuration register is
|
||||||
write once or the individual bits are write once. In addition to device config,
|
write once or the individual bits are write once. In addition to device config,
|
||||||
the DSCR block may provide registers which which are used to reset peripherals,
|
the DSCR block may provide registers which are used to reset peripherals,
|
||||||
provide device ID information, provide ethernet MAC addresses, as well as other
|
provide device ID information, provide ethernet MAC addresses, as well as other
|
||||||
miscellaneous functions.
|
miscellaneous functions.
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
* Renesas R-Car DMA Controller Device Tree bindings
|
* Renesas R-Car DMA Controller Device Tree bindings
|
||||||
|
|
||||||
Renesas R-Car Generation 2 SoCs have have multiple multi-channel DMA
|
Renesas R-Car Generation 2 SoCs have multiple multi-channel DMA
|
||||||
controller instances named DMAC capable of serving multiple clients. Channels
|
controller instances named DMAC capable of serving multiple clients. Channels
|
||||||
can be dedicated to specific clients or shared between a large number of
|
can be dedicated to specific clients or shared between a large number of
|
||||||
clients.
|
clients.
|
||||||
|
@ -39,7 +39,7 @@ Optional Properties:
|
|||||||
- lines-initial-states: Bitmask that specifies the initial state of each
|
- lines-initial-states: Bitmask that specifies the initial state of each
|
||||||
line. When a bit is set to zero, the corresponding line will be initialized to
|
line. When a bit is set to zero, the corresponding line will be initialized to
|
||||||
the input (pulled-up) state. When the bit is set to one, the line will be
|
the input (pulled-up) state. When the bit is set to one, the line will be
|
||||||
initialized the the low-level output state. If the property is not specified
|
initialized the low-level output state. If the property is not specified
|
||||||
all lines will be initialized to the input state.
|
all lines will be initialized to the input state.
|
||||||
|
|
||||||
The I/O expander can detect input state changes, and thus optionally act as
|
The I/O expander can detect input state changes, and thus optionally act as
|
||||||
|
@ -59,7 +59,7 @@ Optional properties:
|
|||||||
Each child node represents one channel and has the following
|
Each child node represents one channel and has the following
|
||||||
properties:
|
properties:
|
||||||
Required properties:
|
Required properties:
|
||||||
* reg: Pair of pins the the channel is connected to.
|
* reg: Pair of pins the channel is connected to.
|
||||||
0: VP/VN
|
0: VP/VN
|
||||||
1: VAUXP[0]/VAUXN[0]
|
1: VAUXP[0]/VAUXN[0]
|
||||||
2: VAUXP[1]/VAUXN[1]
|
2: VAUXP[1]/VAUXN[1]
|
||||||
|
@ -9,7 +9,7 @@ Required properties:
|
|||||||
Optional properties:
|
Optional properties:
|
||||||
- bank-width : Width (in bytes) of the device. If not present, the width
|
- bank-width : Width (in bytes) of the device. If not present, the width
|
||||||
defaults to 1 byte
|
defaults to 1 byte
|
||||||
- nand-skip-bbtscan: Indicates the the BBT scanning should be skipped
|
- nand-skip-bbtscan: Indicates the BBT scanning should be skipped
|
||||||
- timings: array of 6 bytes for NAND timings. The meanings of these bytes
|
- timings: array of 6 bytes for NAND timings. The meanings of these bytes
|
||||||
are:
|
are:
|
||||||
byte 0 TCLR : CLE to RE delay in number of AHB clock cycles, only 4 bits
|
byte 0 TCLR : CLE to RE delay in number of AHB clock cycles, only 4 bits
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
Required properties:
|
Required properties:
|
||||||
- compatible: should be one of "brcm,systemport-v1.00" or "brcm,systemport"
|
- compatible: should be one of "brcm,systemport-v1.00" or "brcm,systemport"
|
||||||
- reg: address and length of the register set for the device.
|
- reg: address and length of the register set for the device.
|
||||||
- interrupts: interrupts for the device, first cell must be for the the rx
|
- interrupts: interrupts for the device, first cell must be for the rx
|
||||||
interrupts, and the second cell should be for the transmit queues. An
|
interrupts, and the second cell should be for the transmit queues. An
|
||||||
optional third interrupt cell for Wake-on-LAN can be specified
|
optional third interrupt cell for Wake-on-LAN can be specified
|
||||||
- local-mac-address: Ethernet MAC address (48 bits) of this adapter
|
- local-mac-address: Ethernet MAC address (48 bits) of this adapter
|
||||||
|
@ -37,7 +37,7 @@ Required properties:
|
|||||||
|
|
||||||
|
|
||||||
You specify supplies using the standard regulator bindings by including
|
You specify supplies using the standard regulator bindings by including
|
||||||
a phandle the the relevant regulator. All specified supplies must be able
|
a phandle the relevant regulator. All specified supplies must be able
|
||||||
to report their voltage. The IO Voltage Domain for any non-specified
|
to report their voltage. The IO Voltage Domain for any non-specified
|
||||||
supplies will be not be touched.
|
supplies will be not be touched.
|
||||||
|
|
||||||
|
@ -10,7 +10,7 @@ How overlays work
|
|||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
A Device Tree's overlay purpose is to modify the kernel's live tree, and
|
A Device Tree's overlay purpose is to modify the kernel's live tree, and
|
||||||
have the modification affecting the state of the the kernel in a way that
|
have the modification affecting the state of the kernel in a way that
|
||||||
is reflecting the changes.
|
is reflecting the changes.
|
||||||
Since the kernel mainly deals with devices, any new device node that result
|
Since the kernel mainly deals with devices, any new device node that result
|
||||||
in an active device should have it created while if the device node is either
|
in an active device should have it created while if the device node is either
|
||||||
@ -80,7 +80,7 @@ result in foo+bar.dts
|
|||||||
};
|
};
|
||||||
---- foo+bar.dts -------------------------------------------------------------
|
---- foo+bar.dts -------------------------------------------------------------
|
||||||
|
|
||||||
As a result of the the overlay, a new device node (bar) has been created
|
As a result of the overlay, a new device node (bar) has been created
|
||||||
so a bar platform device will be registered and if a matching device driver
|
so a bar platform device will be registered and if a matching device driver
|
||||||
is loaded the device will be created as expected.
|
is loaded the device will be created as expected.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user